Bug#1002434: marked as done (sphinx-gallery: FTBFS: NameError: name 'iae' is not defined)
Your message dated Mon, 3 Jan 2022 00:35:05 -0500 with message-id and subject line Re: Bug#1002434: sphinx-gallery: FTBFS: NameError: name 'iae' is not defined has caused the Debian Bug report #1002434, regarding sphinx-gallery: FTBFS: NameError: name 'iae' is not defined 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.) -- 1002434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinx-gallery Version: 0.10.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/doc' > sphinx-build -b html -d _build/doctrees -nWT --keep-going . _build/html > Running Sphinx v4.3.2 > making output directory... done > [autosummary] generating autosummary for: advanced.rst, changes.rst, > configuration.rst, faq.rst, getting_started.rst, index.rst, maintainers.rst, > projects_list.rst, reference.rst, syntax.rst, utils.rst > [autosummary] generating autosummary for: > /<>/doc/gen_modules/sphinx_gallery.backreferences.rst, > /<>/doc/gen_modules/sphinx_gallery.binder.rst, > /<>/doc/gen_modules/sphinx_gallery.directives.rst, > /<>/doc/gen_modules/sphinx_gallery.docs_resolv.rst, > /<>/doc/gen_modules/sphinx_gallery.downloads.rst, > /<>/doc/gen_modules/sphinx_gallery.gen_gallery.rst, > /<>/doc/gen_modules/sphinx_gallery.gen_rst.rst, > /<>/doc/gen_modules/sphinx_gallery.notebook.rst, > /<>/doc/gen_modules/sphinx_gallery.py_source_parser.rst, > /<>/doc/gen_modules/sphinx_gallery.scrapers.rst, > /<>/doc/gen_modules/sphinx_gallery.sorting.rst, > /<>/doc/gen_modules/sphinx_gallery.utils.optipng.rst > loading intersphinx inventory from > /usr/share/doc/python3-doc/html/objects.inv... > loading intersphinx inventory from > /usr/share/doc/python-numpy-doc/html/objects.inv... > loading intersphinx inventory from > /usr/share/doc/python-matplotlib-doc/html/objects.inv... > loading intersphinx inventory from > /usr/share/doc/python-sklearn-doc/html/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory '/usr/share/doc/python-matplotlib-doc/html/objects.inv' > not fetchable due to : [Errno 2] No such file or > directory: '/usr/share/doc/python-matplotlib-doc/html/objects.inv' > loading intersphinx inventory from > /usr/share/doc/sphinx-doc/html/objects.inv... > loading intersphinx inventory from > /usr/share/doc/python-pandas-doc/html/objects.inv... > generating gallery... > Matplotlib created a temporary config/cache directory at > /tmp/matplotlib-w0wd80xt because the default path > (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is > highly recommended to set the MPLCONFIGDIR environment variable to a writable > directory, in particular to speed up the import of Matplotlib and to better > support multiprocessing. > Using Sphinx-Gallery to convert rst text blocks to markdown for .ipynb files. > generating gallery for auto_examples... [ 9%] local_module.py > generating gallery for auto_examples... [ 18%] plot_0_sin.py > generating gallery for auto_examples... [ 27%] plot_1_exp.py > generating gallery for auto_examples... [ 36%] plot_2_seaborn.py > generating gallery for auto_examples... [ 45%] plot_3_capture_repr.py > generating gallery for auto_examples... [ 54%] plot_4_choose_thumbnail.py > generating gallery for auto_examples... [ 63%] plot_4b_provide_thumbnail.py > generating gallery for auto_examples... [ 72%] plot_5_unicode_everywhere.py > generating gallery for auto_examples... [ 81%] plot_6_function_identifier.py > generating gallery for auto_examples... [ 90%] plot_7_sys_argv.py > generating gallery for auto_examples... [100%] plot_9_plotly.py > > generating gallery for auto_examples/no_output... [ 25%] just_code.py > generating gallery for auto_examples/no_output... [ 50%] plot_raise.py > /<>/examples/no_output/plot_raise.py failed to execute > correctly: Traceback (most recent call last): > File "/<>/examples/no_output/plot_raise.py", line 27, in > > iae > NameError: name 'iae' is not defined > > generating gallery for auto_examples/no_output... [ 75%] plot_strings.py > generating gallery for auto_examples/no_output... [100%] plot_syntaxerror.py > /<>/examples/no_output/plot_syntaxerror.py failed to execute > correctly: Traceback (most recent call last): > File
Bug#1003008: marked as done (Error 134633601: Error while parsing number")
Your message dated Mon, 03 Jan 2022 04:18:32 + with message-id and subject line Bug#1003008: fixed in grub 0.97-80 has caused the Debian Bug report #1003008, regarding Error 134633601: Error while parsing number" 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.) -- 1003008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grub-legacy Version: 0.97-79 Severity: Normal After upgrade grub-legacy from 0.97-78 to 0.97-79 installation fails with message "Error 134633601: Error while parsing number": - grub> root (hd0,0) root (hd0,0) Filesystem type is ext2fs, partition type 0x8065e03 grub> setup (hd0) setup (hd0) Checking if "/boot/grub/stage1" exists... no Checking if "/grub/stage1" exists... yes Checking if "/grub/stage2" exists... yes Checking if "/grub/e2fs_stage1_5" exists... yes Running "embed /grub/e2fs_stage1_5 (hd-141250989)"... failed (this is not fatal) Running "embed /grub/e2fs_stage1_5 (hd-141250989,-"... failed (this is not fatal) Running "install /grub/stage1 (hd-141250989) /grub/stage2 p /grub/menu.lst "... failed Error 134633601: Error while parsing number - Observed on all updated hosts (about ten in my own). Rollback to 0.97-78 resolves the problem (with the same config files). Package versions: ii grub-legacy0.97-79 amd64GRand Unified Bootloader (Legacy version) ii grub-common2.04-20 amd64GRand Unified Bootloader (common files) ii libc6-i386 2.33-1 amd64GNU C Library: 32-bit shared libraries for AMD64 Debian version: Debian GNU/Linux bookworm/sid (64bit) -- Eugene Berdnikov --- End Message --- --- Begin Message --- Source: grub Source-Version: 0.97-80 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of grub, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated grub 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 Jan 2022 03:50:34 + Source: grub Architecture: source Version: 0.97-80 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers Changed-By: Colin Watson Closes: 1003008 Changes: grub (0.97-80) unstable; urgency=medium . * Make convert_to_ascii non-variadic, since GCC 11 seemed to miscompile this very dodgy by-hand imitation of va_arg otherwise (closes: #1003008). Checksums-Sha1: 2043bc0a9d201a30cd1bb33f5eb98547e1419562 2125 grub_0.97-80.dsc 3573efa9bf4eac06a161d16c7272774a9040aa5f 75052 grub_0.97-80.debian.tar.xz 5de4eca0198790bee06d75237e4c147655bf2b9f 6922 grub_0.97-80_source.buildinfo Checksums-Sha256: ca39f5a28f99d426f3ca033b7da0243bf0ea4791eb1b5b436bb1628519224336 2125 grub_0.97-80.dsc 74cfcc56a3fd478be130edefdef59c894b64a904be5ed0f6b7f8e59bdf0b5658 75052 grub_0.97-80.debian.tar.xz f2b7a9d2b803b04b2f6a5afc44ff784e1cc6cd4bae28ef6932236f18cb4adb89 6922 grub_0.97-80_source.buildinfo Files: a4381903640254013a7ffefb420e561a 2125 admin optional grub_0.97-80.dsc 2c58decf3bc95571d4a0aaea4c34c47f 75052 admin optional grub_0.97-80.debian.tar.xz 56ef16493bb61eee65100fb7a78f9907 6922 admin optional grub_0.97-80_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmHScqkACgkQOTWH2X2G UAsG+Q/+KVvxrAcWmtX8GE3VeCuLtvKdodokkSEXrSqJSskaaG4HUasonT98gKSh f9EuAbJgEXzXzLAOSfOHNEYo+ECUi7g6gyAIYKAMDvPSvSNaAe9hHNpSh5se1BLY 5P622AWSCMgT9eTJEy0K5h+PthwoMzkuXrj0KE4Qxgzm1e3LwnNBypDnvaYmpauZ 9+p9DJcAvVeVWHPOZV+i1R+QVST5AnwnnfFzpJ7cCRTOARSB1pwUCEznW0j/EB/9 /UYfupLA7stIw/jAm88FLJLTvkbdAjCjUrJjoLwmg3bW/Tj8h+4OcP1Pb6tvwMyy Lik5vr3+GKz/c6CmLneaMJziUWaVChpdrZIkq93fh4zwYdp7LEdS3Uco+OMIG5BN wEin9uVmKEwD913lDsvZZ565VciMcM/XyUqzaUcthYjxKp6WCT5Wwd7wmVqcK9Tc SCtCkLzuSEsjoYeF9zhPT+HGKZnQ8rjaLujo1FZcBJUY4hEhrSHTdRgMckeUa2Wk 6jXStQCZdp8zoY4Z3I52GE83gKIQh4ECUgEDeP9lzGR8s3al/tsS/v1s1kWMF+Dz
Bug#1003008: marked as pending in grub
Control: tag -1 pending Hello, Bug #1003008 in grub 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/grub-team/grub-legacy/-/commit/0be04af37796a03f6091723199ed50c72b33d4d9 Make convert_to_ascii non-variadic GCC 11 seemed to miscompile this very dodgy by-hand imitation of va_arg otherwise. Closes: #1003008 (this message was generated automatically) -- Greetings https://bugs.debian.org/1003008
Processed: Bug#1003008 marked as pending in grub
Processing control commands: > tag -1 pending Bug #1003008 [grub-legacy] Error 134633601: Error while parsing number" Added tag(s) pending. -- 1003008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994391: marked as done (vdirsyncer is unusable)
Your message dated Mon, 03 Jan 2022 02:34:44 +
with message-id
and subject line Bug#994391: fixed in python-click 8.0.3-1
has caused the Debian Bug report #994391,
regarding vdirsyncer is unusable
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.)
--
994391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vdirsyncer
Version: 0.16.8-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
See the attached console session transcript :
```sh
❯ vdirsyncer -vdebug sync
debug: Using 1 maximal workers.
error: Unknown error occurred: unmatched ')' (, line 1)
error: Use `-vdebug` to see the full traceback.
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line
30, in inner
debug: f(*a, **kw)
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line
145, in sync
debug: with wq.join():
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/utils.py", line
364, in join
debug: with ui_worker.patch_click():
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/click_threading/__init__.py",
line 144, in patch_click
debug: with patch_ui_functions(wrapper):
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/click_threading/monkey.py", line
50, in patch_ui_functions
debug: stub_f = eval('lambda {s}: {n}._real_click_fn({a})'
```
vdirsyncer sync should list the avalaible pairs to synchronise with and
proceed. Instead, an error is thrown.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500,
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500,
'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), (100,
'buster-backports'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vdirsyncer depends on:
ii init-system-helpers1.60
ii python33.9.2-3
ii python3-atomicwrites 1.4.0-2
ii python3-click 7.1.2-1
ii python3-click-log 0.2.1-2
ii python3-click-threading0.4.4-2
ii python3-requests 2.25.1+dfsg-2
ii python3-requests-toolbelt 0.9.1-1
vdirsyncer recommends no packages.
Versions of packages vdirsyncer suggests:
ii python3-requests-oauthlib 1.0.0-1.1
pn vdirsyncer-doc
-- no debconf information
--
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net
Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org
--- End Message ---
--- Begin Message ---
Source: python-click
Source-Version: 8.0.3-1
Done: Sandro Tosi
We believe that the bug you reported is fixed in the latest version of
python-click, 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 994...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi (supplier of updated python-click 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, 02 Jan 2022 20:58:40 -0500
Source: python-click
Architecture: source
Version: 8.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi
Changed-By: Sandro Tosi
Closes: 994391
Changes:
python-click (8.0.3-1) unstable; urgency=medium
.
* New upstream release
* debian/copyright
- extend packaging copyright years
* debian/control
- add Breaks: python3-click-threading (<< 0.5.0); Closes: #994391
- bump Standards-Version to 4.6.0.1 (no changes needed)
Checksums-Sha1:
Bug#1003037: astra-toolbox: FTBFS: error: parameter packs not expanded with '...'
Source: astra-toolbox Version: 1.8.3-10 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, astra-toolbox recently started to FTBFS, probably due to some updated toolchain package or build dependency.: /usr/bin/nvcc -gencode=arch=compute_35,code=sm_35 -gencode=arch=compute_50,code=sm_50 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_60,code=compute_60 -I../build/linux/../.. -I../build/linux/../../include -DASTRA_CUDA -c ../build/linux/../../cuda /3d/mem3d.cu -Xcompiler -fPIC -DPIC -o cuda/3d/.libs/mem3d.o /usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not expanded with '...': 435 | function(_Functor&& __f) | ^ /usr/include/c++/11/bits/std_function.h:435:145: note: '_ArgTypes' /usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not expanded with '...': 530 | operator=(_Functor&& __f) | ^ /usr/include/c++/11/bits/std_function.h:530:146: note: '_ArgTypes' make[2]: *** [Makefile:361: cuda/3d/mem3d.lo] Error 1 Andreas astra-toolbox_1.8.3-10.log.gz Description: application/gzip
Bug#994391: marked as pending in python-click
Control: tag -1 pending Hello, Bug #994391 in python-click 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-click/-/commit/cab68600dcc5cf2850496a6ee4210e6609e41000 add Breaks: python3-click-threading (<< 0.5.0); Closes: #994391 (this message was generated automatically) -- Greetings https://bugs.debian.org/994391
Processed: Bug#994391 marked as pending in python-click
Processing control commands: > tag -1 pending Bug #994391 [python3-click] vdirsyncer is unusable Added tag(s) pending. -- 994391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1003008: Error 134633601: Error while parsing number"
Processing control commands: > severity -1 critical Bug #1003008 [grub-legacy] Error 134633601: Error while parsing number" Severity set to 'critical' from 'normal' -- 1003008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001318: marked as done (python-matplotlib-data: missing copyright file)
Your message dated Sun, 2 Jan 2022 20:36:09 -0500 with message-id and subject line Re: Bug#1001318: python-matplotlib-data: missing copyright file has caused the Debian Bug report #1001318, regarding python-matplotlib-data: missing copyright file 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.) -- 1001318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-matplotlib-data Version: 3.5.0-5 Severity: serious Justification: Policy §12.5 $ lintian -F python-matplotlib-data_3.5.0-5_all.deb E: python-matplotlib-data: no-copyright-file -- Jakub Wilk --- End Message --- --- Begin Message --- Version: 3.5.1-1 On Wed, Dec 8, 2021 at 6:24 AM Jakub Wilk wrote: > > Package: python-matplotlib-data > Version: 3.5.0-5 > Severity: serious > Justification: Policy §12.5 > > $ lintian -F python-matplotlib-data_3.5.0-5_all.deb > E: python-matplotlib-data: no-copyright-file not sure what happened there, but rebuilding the package for the last upload correctly installed the copyright file in the -data pkg. closing -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi--- End Message ---
Bug#1003009: marked as done (notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not installed to anywhere)
Your message dated Mon, 03 Jan 2022 01:18:57 +
with message-id
and subject line Bug#1003009: fixed in notcurses 3.0.3+dfsg.1-3
has caused the Debian Bug report #1003009,
regarding notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not
installed to anywhere
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.)
--
1003009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: notcurses
Version: 3.0.3+dfsg.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=notcurses=3.0.3%2Bdfsg.1-1
...
dh_missing -a -O--buildsystem=cmake
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so exists in
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so.3 exists in
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so.3.0.3 exists
in debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/pkgconfig/notcurses-ffi.pc exists
in debian/tmp 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_install: libnotcurses++-dev (6), libnotcurses++3 (2),
libnotcurses-core-dev (45), libnotcurses-core3 (4), libnotcurses-dev (5),
libnotcurses3 (2), notcurses-bin (18), notcurses-data (10), python3-notcurses
(0)
* dh_installdocs: libnotcurses++-dev (0), libnotcurses++3 (0),
libnotcurses-core-dev (0), libnotcurses-core3 (0), libnotcurses-dev (0),
libnotcurses3 (0), notcurses-bin (0), notcurses-data (0), python3-notcurses (0)
* dh_installman: libnotcurses++-dev (0), libnotcurses++3 (0),
libnotcurses-core-dev (0), libnotcurses-core3 (0), libnotcurses-dev (0),
libnotcurses3 (0), notcurses-bin (0), notcurses-data (0), python3-notcurses (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.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.
Remember to be careful with paths containing "x86_64-linux-gnu", where
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:14: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: notcurses
Source-Version: 3.0.3+dfsg.1-3
Done: Nick Black
We believe that the bug you reported is fixed in the latest version of
notcurses, 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 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nick Black (supplier of updated notcurses 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, 02 Jan 2022 19:39:06 -0500
Source: notcurses
Architecture: source
Version: 3.0.3+dfsg.1-3
Distribution: unstable
Urgency: medium
Maintainer: Nick Black
Changed-By: Nick Black
Closes: 1003009
Changes:
notcurses (3.0.3+dfsg.1-3) unstable; urgency=medium
.
* Apply patches from upstream causing -DBUILD_FFI_LIBRARY=off to
actually take effect. (Closes: #1003009) for real this time =\.
Checksums-Sha1:
99684f364f246a38425c0f2fd18eeab27f2ba49f 3148 notcurses_3.0.3+dfsg.1-3.dsc
11a9cd886ef59bed42883bab00be6a008085f6b0 18040
notcurses_3.0.3+dfsg.1-3.debian.tar.xz
58ce5fffe1b0ad1d267e63c168d52fc435d80709 12123
notcurses_3.0.3+dfsg.1-3_source.buildinfo
Checksums-Sha256:
41723cd0694abcb13317266328e041da0d8c7f0725b9b1e251404e1b3ab7f1d3 3148
notcurses_3.0.3+dfsg.1-3.dsc
Bug#1003009: marked as done (notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not installed to anywhere)
Your message dated Sun, 02 Jan 2022 23:33:37 +
with message-id
and subject line Bug#1003009: fixed in notcurses 3.0.3+dfsg.1-2
has caused the Debian Bug report #1003009,
regarding notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not
installed to anywhere
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.)
--
1003009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: notcurses
Version: 3.0.3+dfsg.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=notcurses=3.0.3%2Bdfsg.1-1
...
dh_missing -a -O--buildsystem=cmake
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so exists in
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so.3 exists in
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so.3.0.3 exists
in debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/pkgconfig/notcurses-ffi.pc exists
in debian/tmp 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_install: libnotcurses++-dev (6), libnotcurses++3 (2),
libnotcurses-core-dev (45), libnotcurses-core3 (4), libnotcurses-dev (5),
libnotcurses3 (2), notcurses-bin (18), notcurses-data (10), python3-notcurses
(0)
* dh_installdocs: libnotcurses++-dev (0), libnotcurses++3 (0),
libnotcurses-core-dev (0), libnotcurses-core3 (0), libnotcurses-dev (0),
libnotcurses3 (0), notcurses-bin (0), notcurses-data (0), python3-notcurses (0)
* dh_installman: libnotcurses++-dev (0), libnotcurses++3 (0),
libnotcurses-core-dev (0), libnotcurses-core3 (0), libnotcurses-dev (0),
libnotcurses3 (0), notcurses-bin (0), notcurses-data (0), python3-notcurses (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.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.
Remember to be careful with paths containing "x86_64-linux-gnu", where
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:14: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: notcurses
Source-Version: 3.0.3+dfsg.1-2
Done: Nick Black
We believe that the bug you reported is fixed in the latest version of
notcurses, 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 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nick Black (supplier of updated notcurses 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, 02 Jan 2022 18:15:16 -0500
Source: notcurses
Architecture: source
Version: 3.0.3+dfsg.1-2
Distribution: unstable
Urgency: medium
Maintainer: Nick Black
Changed-By: Nick Black
Closes: 1003009
Changes:
notcurses (3.0.3+dfsg.1-2) unstable; urgency=medium
.
* Supply -DBUILD_FFI_LIBRARY=off (Closes: #1003009).
Checksums-Sha1:
44e5bb5397ced4e07bed19226714aa27af284e7d 3148 notcurses_3.0.3+dfsg.1-2.dsc
fd724c2123ee642b1511b98ea7aeaf2a334abb53 17020
notcurses_3.0.3+dfsg.1-2.debian.tar.xz
ad76eaaa8352a967bce4fe73e8570065e1b94034 12123
notcurses_3.0.3+dfsg.1-2_source.buildinfo
Checksums-Sha256:
daffef014921a3fbe76d2abff4fdd9a3a4f66ffdfe9eb28bbb2662e17e4f35ef 3148
notcurses_3.0.3+dfsg.1-2.dsc
9a49e247ceb6decb07b4c2f94cdcac70fe656be74e842eee4d906d68f1ce8ef8 17020
Bug#1003009: notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not installed to anywhere
this is addressed in more detail at https://github.com/dankamongmen/notcurses/issues/2519. i expect to have this fixed within the hour. sorry for the annoyance.
Bug#1003009: notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not installed to anywhere
reopen 1003009 i added -DBUILD_FFI_LIBRARY=off with the intention of no longer building these three shared objects. looking at it now, however, this CMake variable doesn't actually seem to guard their building and installation, and thus it will not have the desired effect. i'm fixing this upstream, and will build a -3 with the necessary patch. sigh.
Bug#998383: nheko: nheko/{armel,armhf} has unsatisfiable dependency
On Wed, 3 Nov 2021 14:25:41 +0200 Adrian Bunk wrote: Control: reassign -1 src:gst-plugins-good1.0 1.18.5-1 Control: retitle -1 gstreamer1.0-qt5 should again be built on armel/armhf Control: affects -1 nheko On Wed, Nov 03, 2021 at 12:03:20PM +0100, Sebastian Ramacher wrote: > Source: nheko > Version: 0.8.2-2 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > > nheko fails to migrate to testing since it depends on gstreamer1.0-qt5. > This package is not available on armel and armhf. With #894076 fixed, gstreamer1.0-qt5 builds again on armel/armhf. I'll submit a MR for that. Hi Adrian, Any progress on this topic? Thanks, _g. OpenPGP_signature Description: OpenPGP digital signature
Bug#1003009: notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not installed to anywhere
thanks, this ought be fixed in an hour or two.
Bug#998485: gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times
Hi Ludovic, are you still maintaining this package, or should it be moved to QA maintainance? The FTBFS is trivial to fix, but there is a point that someone should also upgrade to new upstream code (assuming the new upstream is usable). Thanks Adrian On Fri, Nov 05, 2021 at 11:59:03AM +0900, notebook wrote: > Hi, > > maybe it's a good chance to change to the new updated version of gjiten at > https://github.com/DarkTrick/gjiten > > The new version might also encounter packaging problems, but it uses more > recent technology and updates; It's probably more worthful to spend time > there than in the 10 year old package* > > > Regards > Chris - DarkTrick > > > * Yes, I'm trying to promote my updates here :)
Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive
* Laurent Bigonville: > It looks like libguestfs-tools version 1:1.46.2-1 in depending on > guestfs-tools that is not in the archive making the package uninstalable > > guestfs-tools is currently stuck in the new queue Right. Let's just wait. (Or do you know of a way to speed this up?) Cheers, -Hilko
Bug#1002982: marked as done (elpa-org: post-installation script subprocess returned error exit status 1)
Your message dated Sun, 02 Jan 2022 22:33:38 + with message-id and subject line Bug#1002982: fixed in org-mode 9.5.2+dfsh-2 has caused the Debian Bug report #1002982, regarding elpa-org: post-installation script subprocess returned error exit status 1 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.) -- 1002982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-org Version: 9.5.2+dfsh-1 Severity: grave X-Debbugs-Cc: none, Lev Lamberov Dear Maintainer, While updating elpa-org (9.4.0+dfsg-1 -> 9.5.2+dfsh-1, in testing) I faced a problem with post-installation, which is still there even in case of completely removing elpa-org and then reinstalling it. Please, see the followin apt output: * Purging $ LC_ALL=C.UTF-8 sudo apt purge elpa Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package elpa 10:43:17-dogsleg@shakva:~$ LC_ALL=C.UTF-8 sudo apt purge elpa-org Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: elpa-htmlize Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: elpa-org* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 5214 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 486521 files and directories currently installed.) Removing elpa-org (9.5.2+dfsh-1) ... Remove elpa-org for emacs remove/org-9.5.2: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs * Installing again $ LC_ALL=C.UTF-8 sudo apt install elpa-org Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: ditaa The following NEW packages will be installed: elpa-org 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/949 kB of archives. After this operation, 5214 kB of additional disk space will be used. Selecting previously unselected package elpa-org. (Reading database ... 486388 files and directories currently installed.) Preparing to unpack .../elpa-org_9.5.2+dfsh-1_all.deb ... Unpacking elpa-org (9.5.2+dfsh-1) ... Setting up elpa-org (9.5.2+dfsh-1) ... tsort: -: input contains a loop: tsort: elpa-htmlize tsort: emacsen-common Install elpa-htmlize for emacs install/htmlize-1.56: Handling install of emacsen flavor emacs install/htmlize-1.56: byte-compiling for emacs Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install elpa-org for emacs install/org-9.5.2: Handling install of emacsen flavor emacs install/org-9.5.2: byte-compiling for emacs Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-agenda.el:50:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-archive.el:31:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-attach-git.el:32:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-attach.el:38:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-capture.el:51:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-clock.el:32:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-colview.el:32:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-ctags.el:141:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form: org-datetree.el:33:1:Error: Invalid version syntax: ‘N/A’ (must start with a number) Warning (emacs): Could not define org version correctly. Check installation! In toplevel form:
Processed: cloning 1001273, reassign 1001273 to gcc-sh-elf, fixed 1001273 in 11.2.0-13+2 ..., reopening -1 ...
Processing commands for cont...@bugs.debian.org:
> clone 1001273 -1
Bug #1001273 {Done: John Scott } [gcc-avr,gcc-sh-elf]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Bug 1001273 cloned as bug 1003030
> reassign 1001273 gcc-sh-elf 11.2.0-12+1
Bug #1001273 {Done: John Scott } [gcc-avr,gcc-sh-elf]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Bug reassigned from package 'gcc-avr,gcc-sh-elf' to 'gcc-sh-elf'.
No longer marked as found in versions gcc-avr/1:5.4.0+Atmel3.6.2-2.
No longer marked as fixed in versions gcc-sh-elf/2.
Bug #1001273 {Done: John Scott } [gcc-sh-elf]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Marked as found in versions gcc-sh-elf/1.
> fixed 1001273 11.2.0-13+2
Bug #1001273 {Done: John Scott } [gcc-sh-elf]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Marked as fixed in versions gcc-sh-elf/2.
> retitle 1001273 gcc-sh-elf: ships /usr/lib/libcc1.so*
Bug #1001273 {Done: John Scott } [gcc-sh-elf]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Changed Bug title to 'gcc-sh-elf: ships /usr/lib/libcc1.so*' from
'gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*'.
> reassign -1 gcc-avr 1:5.4.0+Atmel3.6.2-2
Bug #1003030 {Done: John Scott } [gcc-avr,gcc-sh-elf]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Bug reassigned from package 'gcc-avr,gcc-sh-elf' to 'gcc-avr'.
No longer marked as found in versions gcc-avr/1:5.4.0+Atmel3.6.2-2.
No longer marked as fixed in versions gcc-sh-elf/2.
Bug #1003030 {Done: John Scott } [gcc-avr]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Marked as found in versions gcc-avr/1:5.4.0+Atmel3.6.2-2.
> reopen -1
Bug #1003030 {Done: John Scott } [gcc-avr]
gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Bug reopened
Ignoring request to alter fixed versions of bug #1003030 to the same values
previously set
> retitle -1 gcc-avr: ships /usr/lib/libcc1.so*
Bug #1003030 [gcc-avr] gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Changed Bug title to 'gcc-avr: ships /usr/lib/libcc1.so*' from
'gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001273
1003030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1003005, tagging 1001145, found 958680 in 7.0.0+git20200310.6c13234-3, tagging 956423 ...
Processing commands for cont...@bugs.debian.org:
> tags 1003005 + experimental
Bug #1003005 {Done: Michael Banck } [src:elkcode] elkcode
FTBFS with libxc 5.1.7
Added tag(s) experimental.
> tags 1001145 + sid bookworm
Bug #1001145 {Done: Renzo Davoli } [src:vdeplug-agno]
vdeplug-agno: Drop explicit library dependencies
Added tag(s) sid and bookworm.
> found 958680 7.0.0+git20200310.6c13234-3
Bug #958680 {Done: Yadd } [node-opencv] node-opencv: Remove
dependency to node-request
Marked as found in versions node-opencv/7.0.0+git20200310.6c13234-3.
> tags 956423 + sid bookworm
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
Added tag(s) sid and bookworm.
> retitle 620375 mathtex: may hang due to use of strcpy() on overlapping region
Bug #620375 [mathtex] mathtex: Binary does not work at all on Debian Squeeze
amd64
Changed Bug title to 'mathtex: may hang due to use of strcpy() on overlapping
region' from 'mathtex: Binary does not work at all on Debian Squeeze amd64'.
> tags 897397 + stretch buster bullseye bookworm sid
Bug #897397 [webmagick] webmagick: Use of defined on aggregates is no longer
supported
Added tag(s) bookworm, stretch, bullseye, sid, and buster.
> reassign 998855 src:obs-move-transition
Bug #998855 {Done: Joao Eriberto Mota Filho } [libobs-dev]
libobs-dev: Please, provide easings.h
Bug reassigned from package 'libobs-dev' to 'src:obs-move-transition'.
No longer marked as found in versions obs-studio/27.1.3+dfsg1-1.
No longer marked as fixed in versions obs-move-transition/2.5.1-3.
> fixed 998855 2.5.1-3
Bug #998855 {Done: Joao Eriberto Mota Filho }
[src:obs-move-transition] libobs-dev: Please, provide easings.h
Marked as fixed in versions obs-move-transition/2.5.1-3.
> notfound 1000725 17.0.2+dfsg+~cs106.66.56-1
Bug #1000725 {Done: Yadd } [node-react] Please ship TypeScript
definitions
No longer marked as found in versions node-react/17.0.2+dfsg+~cs106.66.56-1.
> notfound 1000723 0.8.0+ds+repack-3
Bug #1000723 {Done: Yadd } [node-marked] Please ship
TypeScript definitions
No longer marked as found in versions node-marked/0.8.0+ds+repack-3.
> notfound 1000712 7.1.7+~cs7.5.19-2
Bug #1000712 {Done: Yadd } [node-glob] Please add TypeScript
definitions
No longer marked as found in versions node-glob/7.1.7+~cs7.5.19-2.
> notfound 1000670 1.2.5+~cs5.3.2-1
Bug #1000670 {Done: Yadd } [node-minimist] Please ship
TypeScript definitions
No longer marked as found in versions node-minimist/1.2.5+~cs5.3.2-1.
> notfound 1000668 1.5.3-1
Bug #1000668 {Done: Yadd } [node-url-parse] Please ship
TypeScript definitions
No longer marked as found in versions node-url-parse/1.5.3-1.
> notfixed 595256 24.1
Bug #595256 {Done: "J. Smith" } [emacs] Emacs aborts
with maximized windows, small font size, large resolution
There is no source info for the package 'emacs' at version '24.1' with
architecture ''
Unable to make a source version for version '24.1'
No longer marked as fixed in versions 24.1.
> fixed 595256 24.1+1-1
Bug #595256 {Done: "J. Smith" } [emacs] Emacs aborts
with maximized windows, small font size, large resolution
Marked as fixed in versions emacs24/24.1+1-1.
> reassign 936073 src:libffi 3.2.1-9
Bug #936073 {Done: Matthias Klose } [libffi6] please have
libffi6-dbgsym debug package
Bug reassigned from package 'libffi6' to 'src:libffi'.
No longer marked as found in versions libffi/3.2.1-9.
No longer marked as fixed in versions 3.3~20180313-1.
Bug #936073 {Done: Matthias Klose } [src:libffi] please have
libffi6-dbgsym debug package
Marked as found in versions libffi/3.2.1-9.
> fixed 936073 3.3~20180313-1
Bug #936073 {Done: Matthias Klose } [src:libffi] please have
libffi6-dbgsym debug package
Marked as fixed in versions libffi/3.3~20180313-1.
> notfixed 1001161 1.4.3-3
Bug #1001161 {Done: Gunnar Wolf } [telegram-purple]
telegram-purple: The Telegram service seems to be about to perform a protocol
update, please update package!
No longer marked as fixed in versions 1.4.3-3.
> notfixed 1002587 9.4-1
Bug #1002587 {Done: Tobias Hansen } [python3-sage]
python3-sage: Depends on unavailable package
No longer marked as fixed in versions 9.4-1 and sagemath/9.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000668
1000670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000670
1000712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000712
1000723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000723
1000725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000725
1001145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001145
1001161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001161
1002587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002587
1003005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003005
595256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595256
620375:
Bug#1002982: elpa-org: post-installation script subprocess returned error exit status 1
Package: elpa-org Version: 9.5.2+dfsh-1 Followup-For: Bug #1002982 Dear Maintainer, After installation, org-version.el is missing (not auto-generated ?) in /usr/share/emacs/site-lisp/elpa-src/org-9.5.2/ and soft-linked in /usr/share/emacs/site-lisp/elpa/org-9.5.2/ Then the elpa-org 9.5.2 loads the org-version.el from default org 9.3 from emacs 27.1 ( /usr/share/emacs/27.1/lisp/org/org-version.el ) To reproduce the loading of the wrong file: emacs -q then in emacs M-x org-reload give the following message: Successfully reloaded Org Org mode version N/A (N/A !!check installation!! @ /usr/share/emacs/site-lisp/elpa/org-9.5.2/) The full text of the *Messages* buffer at the org-reload execution. Note the directory of the loading of org-version (last previous last loading) Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-comint...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-core...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-emacs-lisp...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-eval...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-exp...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-lob...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-ref...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-table...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/ob-tangle...done Loading /usr/share/emacs/27.1/lisp/obarray...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-compat...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-entities...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-faces...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-footnote...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-keys...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-list...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-macro...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-macs...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-pcomplete...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-src...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org-table...done Loading /usr/share/emacs/27.1/lisp/org/org-version.el (source)...done Loading /usr/share/emacs/site-lisp/elpa/org-9.5.2/org...done The following features were found in load-path, please check if that’s correct: (obarray org-version) Successfully reloaded Org Org mode version N/A (N/A !!check installation!! @ /usr/share/emacs/site-lisp/elpa/org-9.5.2/) *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-org depends on: ii dh-elpa-helper 2.0.10 ii elpa-htmlize1.56-1 ii emacsen-common 3.0.4 Versions of packages elpa-org recommends: ii emacs 1:27.1+1-3.1 ii emacs-gtk [emacs] 1:27.1+1-3.1+b1 Versions of packages elpa-org suggests: ii ditaa 0.10+ds1-1.2 ii org-mode-doc 9.4.0-2 ii texinfo6.8-3 ii texlive-fonts-recommended 2021.20211217-1 ii texlive-latex-extra2021.20211217-1 -- debconf-show failed
Processed: Bug#1001733 marked as pending in dh-sysuser
Processing control commands: > tag -1 pending Bug #1001733 [src:dh-sysuser] dh-sysuser: autopkgtest failure: FAILED: user _runit-log exists after purge or environment is not clean Added tag(s) pending. -- 1001733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001733: marked as pending in dh-sysuser
Control: tag -1 pending Hello, Bug #1001733 in dh-sysuser 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/debian/dh-sysuser/-/commit/2849beb7e185c4f66569d26877a9a29c7e4927e2 Temporary disable the purge test Disable the purge test for now: runit package need to be rebuilded for this test to succeed. Closes: #1001733 (this message was generated automatically) -- Greetings https://bugs.debian.org/1001733
Processed: limit source to org-mode, tagging 1002982
Processing commands for cont...@bugs.debian.org: > limit source org-mode Limiting to bugs with field 'source' containing at least one of 'org-mode' Limit currently set to 'source':'org-mode' > tags 1002982 + pending Bug #1002982 [elpa-org] elpa-org: post-installation script subprocess returned error exit status 1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: add FTBFS bug
Processing commands for cont...@bugs.debian.org: > block 976811 by 1003007 Bug #976811 [release.debian.org] transition: php8.1 976811 was blocked by: 1000654 1000642 1000568 977403 977401 977404 977400 977687 977337 978457 1000596 1002218 977340 1000653 1000637 1000571 977186 980567 1000647 977385 1000650 977376 990322 977377 1000474 978151 977378 977396 1000619 977389 1002020 1002504 1002215 1002232 1000593 977379 1002242 1000655 1000574 977388 977384 977658 976811 was blocking: 1000585 977373 Added blocking bug(s) of 976811: 1003007 > thanks Stopping processing here. Please contact me if you need assistance. -- 976811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re-assign
Processing commands for cont...@bugs.debian.org: > reassign 1002383 python3-nbconvert nbconvert/6.1.0-1 Bug #1002383 [src:pyswarms] pyswarms: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Bug reassigned from package 'src:pyswarms' to 'python3-nbconvert'. No longer marked as found in versions pyswarms/1.3.0-2. Ignoring request to alter fixed versions of bug #1002383 to the same values previously set Bug #1002383 [python3-nbconvert] pyswarms: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Marked as found in versions nbconvert/6.1.0-1. > forcemerge 1001283 1002383 Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: python3-mistune (<< 2) Bug #1002375 [python3-nbconvert] mdtraj: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Bug #1002383 [python3-nbconvert] pyswarms: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Set Bug forwarded-to-address to 'https://github.com/jupyter/nbconvert/issues/1685'. 1002383 was not blocked by any bugs. 1002383 was not blocking any bugs. Added blocking bug(s) of 1002383: 1001591 Added indication that 1002383 affects src:mdtraj,sagemath-jupyter,src:mistune,src:sagemath Bug #1002375 [python3-nbconvert] mdtraj: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Removed indication that 1002375 affects src:mistune, src:mdtraj, src:sagemath, and sagemath-jupyter Added indication that 1002375 affects src:mdtraj,sagemath-jupyter,src:mistune,src:sagemath Removed indication that 1001283 affects src:mistune, src:sagemath, sagemath-jupyter, and src:mdtraj Added indication that 1001283 affects src:mdtraj,sagemath-jupyter,src:mistune,src:sagemath Merged 1001283 1002375 1002383 > affects 1002383 src:pyswarms Bug #1002383 [python3-nbconvert] pyswarms: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: python3-mistune (<< 2) Bug #1002375 [python3-nbconvert] mdtraj: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Added indication that 1002383 affects src:pyswarms Added indication that 1001283 affects src:pyswarms Added indication that 1002375 affects src:pyswarms > thanks Stopping processing here. Please contact me if you need assistance. -- 1001283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001283 1002375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002375 1002383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-electronics-devel] Bug#1002252: pcb-rnd: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2
Processing commands for cont...@bugs.debian.org: > severity 1002252 important Bug #1002252 [src:pcb-rnd] pcb-rnd: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1002252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002252: [Pkg-electronics-devel] Bug#1002252: pcb-rnd: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2
severity 1002252 important thanks Lucas Nussbaum writes: > During a rebuild of all packages in sid, your package failed to build > on amd64. It looks like noise from the latest librnd version is causing a pcb-rnd test failure. There is no operational bug in either the library or the application pcb-rnd. Upstream reports this is already fixed in their tree, and will apparently be in the next librnd release due in March. Upstream really hates when I pull patches out of his tree to make off-cycle updates, so unless this actually causes someone an operational problem with the existing binary packages, my intent is to just package the next librnd release as soon as possible. Bdale signature.asc Description: PGP signature
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Sun, 2 Jan 2022 20:15:01 +0100 Moritz Muehlenhoff wrote: > On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: > > How should I handle this? NMU to sid, let people try it out, and > > then deal with buster/bullseye? > > Yeah, let's proceed with unstable first in any case. > > > Upload everything all at once? I'm also > > going to try building for buster, unless the security team doesn't > > think I should bother. > > I saw > https://salsa.debian.org/dilinger/chromium/-/commit/5c05f430e192961527ec9a64bbaa64401dc14d95 > , but buster now also includes LLVM/clang 11 (it was introduced to > support a more recent Rust toolchain needed for Firefox), so you > might be reduce complexity here further: > https://tracker.debian.org/pkg/llvm-toolchain-11 > > It's in buster-proposed-updates since there hasn't been a point > release since, but for the purposes of buster-security builds, it > doesn't matter (they chroots have been modified to includen > buster-proposed-updates temporarily): Ah, very helpful, thanks! I'll give buster a try (just created the 'v96-buster' branch). Between that and various backports, I think we might be in good shape.
Bug#999248: marked as done (libident: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sun, 02 Jan 2022 20:24:42 + with message-id and subject line Bug#999248: fixed in libident 0.32-1 has caused the Debian Bug report #999248, regarding libident: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libident Version: 0.22-3.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: libident Source-Version: 0.32-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libident, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libident 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, 02 Jan 2022 14:55:27 -0500 Source: libident Architecture: source Version: 0.32-1 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 209757 231723 437372 944561 990795 999248 1002955 Changes: libident (0.32-1) unstable; urgency=medium . * New upstream release. (Closes: #1002955) + Migrate to autotools buildsystem. (Closes: #944561) * Refresh packaging: + Bump Standards-Version to 4.6.0. + Bump debhelper compat to v13. * debian/control: + Build-depends on debhelper-compat (= 13). + Add homepage field. (Closes: #231723) + Add Vcs-* fields. + Update package description. (Closes: #209757) + Downgrade package importance to Optional (lintian). + Use "Rules-Requires-Root: no". * debian/rules: Migrate to dh sequencer. (Closes: #999248) + Should also fix reproducibility. (Closes: #990795) + Strip option is automatically handled. (Closes: #437372) * debian/: Apply "wrap-and-sort -abst". * Drop all maintscripts, no longer useful. * debian/copyright: Rewritten in machine-readable format. * debian/source/format: Use "3.0 (quilt)" format. + Convert all direct changes into a patch file. * debian/patches: Drop all old patches. - Drop patch on Makefile, no longer used after autotools migration. - Drop patch on old HP UX, not useful for Debian. - Drop patch on IPv6, already merged in new release. - Drop patch on man pages, merged in new release. - Drop patch on QNX, not useful in Debian / unsupportable. - Drop patch on custom Debian version string. + Keep some patches from Philip Hazel on support.c and id_parse.c. Checksums-Sha1: 82582b2c2bb9f3971e63085093611559237b 1874 libident_0.32-1.dsc 4658807b017f21928a64f3442ee3a2b91f48d14e 294241 libident_0.32.orig.tar.gz bea1125c65ff1ff3f6f760154a0edcb18c34083a 5520 libident_0.32-1.debian.tar.xz c679d51361d6c09f6f433736a29fd0a30d2e54b7 6179 libident_0.32-1_amd64.buildinfo Checksums-Sha256: b185818871ae98d4eb9e483ad7376f07a64a9224f089d0f42bdabfa98b2dd1af 1874 libident_0.32-1.dsc 8cc8fb69f1c888be7cffde7f4caeb3dc6cd0abbc475337683a720aa7638a174b 294241 libident_0.32.orig.tar.gz 3adc321be452e5577bcc91645ae8ec629386df13969c6c4db33e860746e674bb 5520 libident_0.32-1.debian.tar.xz ec123aff2e857683e44919d7b77634075d6f9b4df3396f5af78fc5c6a55747b4 6179 libident_0.32-1_amd64.buildinfo Files: 08b1a36833c32e4e454028542d5660c6
Bug#1003005: marked as done (elkcode FTBFS with libxc 5.1.7)
Your message dated Sun, 02 Jan 2022 20:23:37 + with message-id and subject line Bug#1003005: fixed in elkcode 7.2.42-2 has caused the Debian Bug report #1003005, regarding elkcode FTBFS with libxc 5.1.7 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.) -- 1003005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elkcode Version: 6.3.2-2 Severity: serious Tags: ftbfs bookworm sid Control: close -1 7.2.42-1 https://buildd.debian.org/status/package.php?p=elkcode=sid ... mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp -fallow-argument-mismatch `dpkg-buildflags --get LDFLAGS` -o elk modmain.o modmpi.o libxc_funcs.o libxc.o libxcifc.o modxcifc.o modfxcifc.o moddftu.o modrdm.o modphonon.o modscdft.o modtest.o modrandom.o modstore.o modpw.o modvars.o modtddft.o modgw.o modulr.o modjx.o modomp.o mkl_stub.o mkl_init.o oblas_stub.o oblas_init.o blis_stub.o blis_init.o w90_stub.o modw90.o zfftifc_fftw.o elk.o zbsht.o zfsht.o rbsht.o rfsht.o projsbf.o fsmooth.o nfftifc.o rfinp.o splint.o spline.o wsplint.o wsplintp.o splintwp.o sphcover.o r3frac.o genvsig.o gencfun.o zfpack.o addlorbcnd.o rfint.o sortidx.o gengkvec.o pade.o pades.o rfint0.o zfinp.o symrvf.o genapwfr.o rfcopy.o rhomagsh.o genylmg.o olpaa.o readfermi.o factr.o writechg.o zflmconj.o rminv.o zminv.o rlmrot.o rotrflm.o ztorflm.o rotzflm.o rfmtlm.o genzrm.o gensfacgp.o zmctmu.o zmctm.o hmlfv.o olpfv.o axangsu2.o checkmt.o symrf.o z2mm.o z2mctm.o z2mmct.o writefermi.o findnjcmax.o findscq.o plot1d.o plot2d.o plot3d.o hmllolo.o olprad.o occupy.o findkpt.o zfmtint.o rotrfmt.o forcek.o eveqnfvr.o findsym.o genvbmatk.o wigner3jf.o wigner6j.o mixbroyden.o zftrf.o gensocfr.o getcfgq.o wigner3j.o moke.o sfacinit.o sfacrho.o sfacmag.o gradwfcr2.o symrvfmt.o oepmain.o oepresk.o oepvcl.o oepvclk.o dbxcplot.o writehmlbse.o hmldbse.o hmldbsek.o dielectric_bse.o genidxbse.o writeevbse.o genwfpw.o writewfpw.o getwfpw.o genexpmat.o elnes.o potefield.o eulerrot.o fermisurfbxsf.o symmetry.o findsymcrys.o findsymsite.o plotpt1d.o writedos.o findprimcell.o proj2d.o nonlinopt.o vecplot.o wfcrplot.o energykncr.o eveqnss.o gendmatk.o gensdmat.o ggamt_1.o ggair_1.o ggamt_sp_1.o ggair_sp_1.o ggamt_2a.o ggair_2a.o ggamt_2b.o ggair_2b.o ggamt_sp_2a.o ggair_sp_2a.o ggamt_sp_2b.o ggair_sp_2b.o genspecies.o writeemd.o writeexpmat.o rotdmat.o hrmdmat.o reademd.o emdplot.o rfhkintp.o emdplot3d.o emdplot2d.o emdplot1d.o plotpt3d.o plotpt2d.o writeevsp.o torque.o ssfsmjx.o wxcplot.o effmass.o genlmirep.o ssfext.o sstask.o spiralsc.o genscss.o genfspecies.o writespecies.o exxengy.o exxengyk.o xc_c_tb09.o elfplot.o potplot.o mae.o writestate.o readstate.o rotaxang.o axangrot.o dmatls.o gendmat.o numlist.o sbesseldm.o genvchi0.o genspchi0.o vclcore.o hmlxbse.o hmlxbsek.o genvmatk.o writeepsinv.o putepsinv.o curden.o curdenk.o hflocal.o dielectric.o bdipole.o roteuler.o lopzflm.o eveqnfvz.o rhomag.o hmlaa.o hmlalo.o gencore.o gentau.o gentauk.o hmlistl.o olpistl.o gengclg.o hmlrad.o rhonorm.o rfmtsm.o olplolo.o genshtmat.o allatoms.o rtozflm.o rtozfmt.o gauntyry.o fderiv.o moment.o sctovec.o match.o writeinfo.o rfpack.o gaunt.o readinput.o ztorfmt.o putevecfv.o zfmtinp.o zfcmtinp.o writelinen.o writekpts.o rfmtinp.o brzint.o rhocore.o writelat.o mtdmin.o atpstep.o potcoul.o zfmtconj.o symrfmt.o putpmat.o eveqnz.o olpalo.o checkfsm.o rhoplot.o potnucl.o potxc.o erf.o gradzf.o writegeom.o linengy.o bandstr.o gengvc.o gengclq.o closefiles.o writefsm.o eveqn.o rhomagk.o factnm.o atom.o radnucl.o charge.o genrmesh.o genapwlofr.o wavefmt.o genzrho.o potks.o sbessel.o clebgor.o hermite.o findband.o genbs.o gencfrc.o genws.o chargemt.o gndstate.o addbfsm.o initoep.o orthevsv.o fermisurf.o findswidth.o gradrf.o dos.o gradzfmt.o nuclei.o writesym.o zftzf.o polynm.o rdirac.o zfmtftoc.o rfmtftoc.o gradrfmt.o genzvclmt.o getevalfv.o mixlinear.o gengvec.o putevalfv.o rfmtpack.o zfmtpack.o writestrain.o writeforces.o r3mv.o r3mtv.o r3cross.o r3minv.o r3mdet.o r3mm.o r3mtm.o r3mmt.o r3vo.o symvec.o curdenplot.o hartfock.o eveqnhf.o zpotclmt.o genlofr.o rfinpc.o eveqnit.o genzfrm.o gengqrf.o writepmat.o genwfsv.o writelsj.o writesf.o rzfinp.o genjlgprmt.o gridsize.o sphcrd.o writeiad.o readspecies.o i3mtv.o writeeval.o i3minv.o i3mdet.o genevfsv.o getpmat.o timesec.o mixpack.o mixerifc.o symmat.o rhoinit.o maginit.o rvfcross.o eveqnfv.o energynn.o rfinterp.o rfplot.o geomopt.o ylmroty.o ylmrot.o gcd.o
Bug#908941: unarchiving 908941, reopening 908941
rpyc | 5.0.1-1 | new| source
Bug#1000226: marked as done (python-python-docx_0.8.11+dfsg1-2_all-buildd.changes REJECTED)
Your message dated Sun, 2 Jan 2022 21:20:47 +0100 with message-id and subject line Re: python-python-docx_0.8.11+dfsg1-2_all-buildd.changes REJECTED has caused the Debian Bug report #1000226, regarding python-python-docx_0.8.11+dfsg1-2_all-buildd.changes REJECTED 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.) -- 1000226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-python-docx Version: 0.8.11+dfsg1-2 Severity: serious On 2021-11-19 17:49, Debian FTP Masters wrote: > > python3-python-docx_0.8.11+dfsg1-2_all.deb: Does not match binary in database. > > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Version: 0.8.11+dfsg1-2+rm On Fri, 19 Nov 2021 23:20:43 +0100 Aurelien Jarno wrote: Source: python-python-docx Version: 0.8.11+dfsg1-2 That package was renamed to src:python-docx with python3-python-docx becoming a transitional package, which seems to have been temporarily built from both sources. But now the old package has already disappeared from the archive ... Andreas--- End Message ---
Processed: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h
Processing control commands: > found -1 openblas/0.3.19+ds-1 Bug #1003020 [src:openblas, src:hypre] openblas breaks hypre autopkgtest on armhf: test times out after 2:47h Marked as found in versions openblas/0.3.19+ds-1. > found -1 hypre/2.22.1-3 Bug #1003020 [src:openblas, src:hypre] openblas breaks hypre autopkgtest on armhf: test times out after 2:47h Marked as found in versions hypre/2.22.1-3. -- 1003020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h
Source: openblas, hypre Control: found -1 openblas/0.3.19+ds-1 Control: found -1 hypre/2.22.1-3 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of openblas the autopkgtest of hypre fails in testing when that autopkgtest is run with the binary packages of openblas from unstable on armhf due to a timeout after 2:47 h. It passes when run with only packages from testing in about 9-12 minutes. In tabular form: passfail openblas from testing0.3.19+ds-1 hypre from testing2.22.1-3 all others from testingfrom testing I copied some of the output at the bottom of this report, but as the test times out, I suspect it just hangs and there's not much useful to see. Currently this regression is blocking the migration of openblas to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=openblas https://ci.debian.net/data/autopkgtest/testing/armhf/h/hypre/17988587/log.gz Building tests for HYPRE rm -f *.o *.obj rm -rf pchdir tca.map *inslog* mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o ij.o ij.c Building ij ... mpicc -o ij ij.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o ij_assembly.o ij_assembly.c Building ij_assembly ... mpicc -o ij_assembly ij_assembly.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o sstruct.o sstruct.c Building sstruct ... mpicc -o sstruct sstruct.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o struct.o struct.c Building struct ... mpicc -o struct struct.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o ams_driver.o ams_driver.c Building ams_driver ... mpicc -o ams_driver ams_driver.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o maxwell_unscaled.o maxwell_unscaled.c Building maxwell_unscaled ... mpicc -o maxwell_unscaled maxwell_unscaled.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o struct_migrate.o struct_migrate.c Building struct_migrate ... mpicc -o struct_migrate struct_migrate.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o sstruct_fac.o sstruct_fac.c Building sstruct_fac ... mpicc -o sstruct_fac sstruct_fac.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o ij_mv.o ij_mv.c Building ij_mv ... mpicc -o ij_mv ij_mv.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include
Bug#1003017: dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found
Source: dulwich Version: 0.20.26-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of dulwich the autopkgtest of dulwich fails in testing when that autopkgtest is run with the binary packages of dulwich from unstable. It passes when run with only packages from testing. In tabular form: passfail dulwichfrom testing0.20.26-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=dulwich https://ci.debian.net/data/autopkgtest/testing/amd64/d/dulwich/17999494/log.gz = Running tests with python3.9 == /tmp/autopkgtest-lxc.n4tqfogv/downtmp/build.r97/src/debian/tests/testsuite3: 10: -m: not found autopkgtest [23:08:36]: test testsuite3 OpenPGP_signature Description: OpenPGP digital signature
Processed: node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js?
Processing control commands: > found -1 node-chart.js/3.7.0+~0.1.9-1 Bug #1003016 [src:node-chart.js] node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js? Marked as found in versions node-chart.js/3.7.0+~0.1.9-1. > affects -1 cacti python3-ontospy Bug #1003016 [src:node-chart.js] node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js? Added indication that 1003016 affects cacti and python3-ontospy -- 1003016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003016: node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js?
Source: node-chart.js Control: found -1 node-chart.js/3.7.0+~0.1.9-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Control: affects -1 cacti python3-ontospy [X-Debbugs-CC: debian...@lists.debian.org python3-onto...@packages.debian.org] Dear maintainer(s), [I'm also the maintainer of the cacti package in Debian] With a recent upload of node-chart.js the autopkgtest of cacti fails in testing when that autopkgtest is run with the binary packages of node-chart.js from unstable. It passes when run with only packages from testing. In tabular form: passfail node-chart.js from testing3.7.0+~0.1.9-1 cacti from testing1.2.19+ds1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The cacti autopkgtest is a simple recursive web crawl of the web app. The test fails because it can't find Chart.js while it expect it to be there. Chart.js used to be linked in from libjs-chart.js. There is a chart.js in the new version, is that just the renamed version of Chart.js? If that's the case, can a symlink be provided to enable reverse dependencies to just keep on working? (Same for other files that got renamed) Currently this regression is blocking the migration of node-chart.js to testing [1]. Can you please investigate the situation? If you think that reverse Depends should just move on, please clone and reassign the bug to all reverse dependencies that use Chart.js (or other files that got renamed/dropped). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=node-chart.js https://ci.debian.net/data/autopkgtest/testing/amd64/c/cacti/17997504/log.gz 2022-01-01 21:11:48 - ERROR PHP WARNING: md5_file(/usr/share/cacti/site/lib/../include/js/Chart.js): failed to open stream: No such file or directory in file: /usr/share/cacti/site/lib/functions.php on line: 6072 2022-01-01 21:11:48 - CMDPHP PHP ERROR WARNING Backtrace: (/automation_tree_rules.php[68]:top_header(), /lib/functions.php[4155]:include_once(), /include/top_header.php[34]:html_common_header(), /lib/html.php[2566]:get_md5_include_js(), /lib/functions.php[6089]:get_md5_hash(), /lib/functions.php[6072]:md5_file(), CactiErrorHandler()) OpenPGP_signature Description: OpenPGP digital signature
Processed: bug 1002372 is forwarded to https://github.com/jupyter/nbconvert/issues/1685
Processing commands for cont...@bugs.debian.org: > forwarded 1002372 https://github.com/jupyter/nbconvert/issues/1685 Bug #1002372 [src:nbconvert] nbconvert: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Set Bug forwarded-to-address to 'https://github.com/jupyter/nbconvert/issues/1685'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1003012 is forwarded to https://lists.gnu.org/archive/html/bug-bash/2022-01/msg00000.html https://savannah.gnu.org/patch/?10035
Processing commands for cont...@bugs.debian.org: > forwarded 1003012 > https://lists.gnu.org/archive/html/bug-bash/2022-01/msg0.html > https://savannah.gnu.org/patch/?10035 Bug #1003012 [bash] bash: Corrupted multibyte characters in command substitutions Set Bug forwarded-to-address to 'https://lists.gnu.org/archive/html/bug-bash/2022-01/msg0.html https://savannah.gnu.org/patch/?10035'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: > > I've got 96.0.4664.110 building on both bullseye and sid Trying it, I see it still build-depends on python-jinja2. That package is now gone, so it's not actually buildable in sid anymore. Correlated, do you know how long do they plan on keeping using python2? That's plainly unsuitable, it really is not going to last much longer in debian. > > the v96 branch of https://salsa.debian.org/dilinger/chromium FWIW, I'm trying to build it myself as well (after injecting an old python-jinja2 and an old python-markupsafe). > Alright, crashes are solved and the packages are now usable. After some > cleanups (listing CVEs in changelogs, This doesn't seem to be done as of the current tip of you v96 branch. > merging/pushing a bunch of > commits in my branch, possibly dropping strong stack protection from > builds to silence warnings from older clang versions, and going through > lintian errors/warnings), it should be ready to upload. TBH, I don't think I am able to judge the appropriateness of most of those changes... Though I suspect I could close most of my eyes and upload it to unstable: can't be much worse than what we have... > How should I handle this? NMU to sid, let people try it out, and then > deal with buster/bullseye? Upload everything all at once? Procedure would be NMU to unstable first, IMHO. > I also haven't heard from anyone on the chromium team yet - should I > add myself as an uploader and do a normal (non-NMU) upload? Do any of > them care? Without hearing from them, adding yourself to Uploaders would be inappropriate. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: > How should I handle this? NMU to sid, let people try it out, and then > deal with buster/bullseye? Yeah, let's proceed with unstable first in any case. > Upload everything all at once? I'm also > going to try building for buster, unless the security team doesn't > think I should bother. I saw https://salsa.debian.org/dilinger/chromium/-/commit/5c05f430e192961527ec9a64bbaa64401dc14d95 , but buster now also includes LLVM/clang 11 (it was introduced to support a more recent Rust toolchain needed for Firefox), so you might be reduce complexity here further: https://tracker.debian.org/pkg/llvm-toolchain-11 It's in buster-proposed-updates since there hasn't been a point release since, but for the purposes of buster-security builds, it doesn't matter (they chroots have been modified to includen buster-proposed-updates temporarily): I'd say if it works out without additional overhead, let's also update buster-security, but it's also important not to overstretch the time/resources, so focusing on bullseye and EOLing buster is also an option for sure. Cheers, Moritz
Bug#1003013: ceph-volume: ModuleNotFoundError
Package: ceph-osd
Version: 16.2.7+ds-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When I start ceph-volume, I get the following error:
Traceback (most recent call last):
File "/usr/sbin/ceph-volume", line 33, in
sys.exit(load_entry_point('ceph-volume==1.0.0', 'console_scripts',
'ceph-volume')())
File "/usr/sbin/ceph-volume", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/ceph_volume/main.py", line 9, in
from ceph_volume import log, devices, configuration, conf, exceptions,
terminal, inventory, drive_group
File "/usr/lib/python3/dist-packages/ceph_volume/drive_group/__init__.py",
line 1, in
from .main import Deploy # noqa
File "/usr/lib/python3/dist-packages/ceph_volume/drive_group/main.py", line
8, in
from ceph.deployment.drive_group import DriveGroupSpec
ModuleNotFoundError: No module named 'ceph'
Downgrading ceph back to the testing branch, I get a working ceph-volume to
setup the volume for later use by the osd.
However, the osd won't start with the old version, due to previously already
having upgraded, so I need to upgrade ceph again after running the ceph-volume
lvm trigger command.
On reboot, I need to do a downgrade again, run ceph-volume, and then upgrade to
start the osd.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 5.15.0-2-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_DIE, TAINT_WARN, TAINT_CRAP
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 ceph-osd depends on:
ii ceph-base 16.2.7+ds-1
ii ceph-common 16.2.7+ds-1
ii libaio1 0.3.112-13
ii libblkid1 2.37.2-5
ii libboost-iostreams1.74.01.74.0-13
ii libboost-program-options1.74.0 1.74.0-13
ii libboost-thread1.74.0 1.74.0-13
ii libc6 2.33-1
ii libfmt8 8.0.1+ds1-4
ii libfuse22.9.9-5
ii libgcc-s1 11.2.0-13
ii libibverbs1 38.0-1
ii libleveldb1d1.23-3
ii liblz4-11.9.3-2
ii libpmem11.11.1-3
ii librados2 16.2.7+ds-1
ii librdmacm1 38.0-1
ii libsnappy1v51.1.8-1
ii libssl1.1 1.1.1m-1
ii libstdc++6 11.2.0-13
ii libudev1249.7-1
ii lvm22.03.11-2.1
ii python3 3.9.8-1
ii python3-ceph16.2.7+ds-1
ii sudo1.9.8p2-1
ii zlib1g 1:1.2.11.dfsg-2
ceph-osd recommends no packages.
Versions of packages ceph-osd suggests:
ii nvme-cli 1.16-3
-- no debconf information
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On 1/2/22 12:53 PM, Mattia Rizzolo wrote: On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: I've got 96.0.4664.110 building on both bullseye and sid Trying it, I see it still build-depends on python-jinja2. That package is now gone, so it's not actually buildable in sid anymore. Correlated, do you know how long do they plan on keeping using python2? That's plainly unsuitable, it really is not going to last much longer in debian. Sorry, I hadn't pushed the commits yet. I just did, but like I said I still need to clean 'em up.
Bug#1003012: bash: Corrupted multibyte characters in command substitutions
Package: bash Version: 5.1-2+b3 Severity: critical Justification: breaks unrelated software Tags: patch upstream l10n I've reported this bug on bug-bash: https://lists.gnu.org/archive/html/bug-bash/2022-01/msg0.html only to learn that it's known and not fixed for months (it was known before bullseye was released, so a timely fix would have prevented the bug ever reaching stable): https://savannah.gnu.org/patch/?10035 I'm reporting it as critical because it causes silent data corruption and potentially affects each bash script in the system. Since the bash developers don't seem to take that seriously, I'm asking the Debian maintainers to put out a fixed version ASAP to prevent further damage -- hopefully as a security patch. (I'm no expert in writing exploits, but I think it's quite possible such a bug can be exploited. I hope you don't have to wait for an actual exploit in order to fix the bug.) Both reports listed above contain a patch. They're different, but either one will fix the immediate problem. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/24 CPU threads) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages bash depends on: ii base-files 11.1+deb11u2 ii debianutils 4.11.2 ii libc62.31-13+deb11u2 ii libtinfo66.2+20201114-2 Versions of packages bash recommends: ii bash-completion 1:2.11-2 Versions of packages bash suggests: pn bash-doc -- no debconf information
Bug#1003009: notcurses FTBFS: notcurses-ffi exists in debian/tmp but is not installed to anywhere
Source: notcurses
Version: 3.0.3+dfsg.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=notcurses=3.0.3%2Bdfsg.1-1
...
dh_missing -a -O--buildsystem=cmake
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so exists in
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so.3 exists in
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/libnotcurses-ffi.so.3.0.3 exists
in debian/tmp but is not installed to anywhere
dh_missing: warning: usr/lib/x86_64-linux-gnu/pkgconfig/notcurses-ffi.pc exists
in debian/tmp 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_install: libnotcurses++-dev (6), libnotcurses++3 (2),
libnotcurses-core-dev (45), libnotcurses-core3 (4), libnotcurses-dev (5),
libnotcurses3 (2), notcurses-bin (18), notcurses-data (10), python3-notcurses
(0)
* dh_installdocs: libnotcurses++-dev (0), libnotcurses++3 (0),
libnotcurses-core-dev (0), libnotcurses-core3 (0), libnotcurses-dev (0),
libnotcurses3 (0), notcurses-bin (0), notcurses-data (0), python3-notcurses (0)
* dh_installman: libnotcurses++-dev (0), libnotcurses++3 (0),
libnotcurses-core-dev (0), libnotcurses-core3 (0), libnotcurses-dev (0),
libnotcurses3 (0), notcurses-bin (0), notcurses-data (0), python3-notcurses (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.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.
Remember to be careful with paths containing "x86_64-linux-gnu", where
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:14: binary-arch] Error 25
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Sun, Jan 02, 2022 at 06:53:51PM +0100, Mattia Rizzolo wrote: > Correlated, do you know how long do they plan on keeping using python2? > That's plainly unsuitable, it really is not going to last much longer in > debian. Current state of the Python 3 upstream migration can be found here: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/python3_migration.md So it sounds like it's almost ready except tests. But the migration doesn't seem like a top priority either, https://bugs.chromium.org/p/chromium/issues/detail?id=941669 dates back to March 2019... Cheers, Moritz
Bug#1003007: libvirt-php FTBFS with PHP 8.1
Source: libvirt-php Version: 0.5.5-3 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/fetch.php?pkg=libvirt-php=amd64=0.5.5-3%2Bb1=1641147267=0 ... In file included from ../../src/libvirt-php.c:19: ../../src/libvirt-php.h:161:26: error: expected ‘;’, ‘,’ or ‘)’ before ‘TSRMLS_DC’ 161 | void set_error(char *msg TSRMLS_DC); | ^ ../../src/libvirt-php.h:162:35: error: expected ‘;’, ‘,’ or ‘)’ before ‘TSRMLS_DC’ 162 | void set_error_if_unset(char *msg TSRMLS_DC); | ^ ../../src/libvirt-php.h:163:1: warning: parameter names (without types) in function declaration 163 | void reset_error(TSRMLS_D); | ^~~~ ...
Bug#1002174: marked as done (pcbasic: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --test-args=/<> returned exit code 13)
Your message dated Sun, 02 Jan 2022 17:49:36 +
with message-id
and subject line Bug#1002174: fixed in pcbasic 2.0.4-2
has caused the Debian Bug report #1002174,
regarding pcbasic: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" --test-args=/<> returned exit code 13
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.)
--
1002174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcbasic
Version: 2.0.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p /<>/tests/unit/output/single
> dh_auto_test -- --test-args="/<>"
> I: pybuild base:237: cd
> /<>/.pybuild/cpython3_3.10_pcbasic/build; python3.10 -m unittest
> discover -v /<>
> docsrc (unittest.loader._FailedTest) ... ERROR
> pcbasic (unittest.loader._FailedTest) ... ERROR
> test_event_signal (tests.unit.test_base.BaseTest)
> Test event signals. ... ok
> test_exception (tests.unit.test_base.BaseTest)
> Test exceptions. ... ok
> test_bytearray (tests.unit.test_base.ByteMatrixTest)
> Create matrix from bytearray. ... ok
> test_bytearray_tall (tests.unit.test_base.ByteMatrixTest)
> Create 1-column matrix from bytearray. ... ok
> test_bytearray_wide (tests.unit.test_base.ByteMatrixTest)
> Create 1-row matrix from bytearray. ... ok
> test_bytes (tests.unit.test_base.ByteMatrixTest)
> Create matrix from bytes. ... ok
> test_copy (tests.unit.test_base.ByteMatrixTest)
> Test copying. ... ok
> test_elementwise (tests.unit.test_base.ByteMatrixTest)
> Test elementwise operations. ... ok
> test_elementwise_inplace_int (tests.unit.test_base.ByteMatrixTest)
> Test in-place elementwise operations with scalar. ... ok
> test_elementwise_int (tests.unit.test_base.ByteMatrixTest)
> Test elementwise operations with scalar. ... ok
> test_empty (tests.unit.test_base.ByteMatrixTest)
> Create empty matrix. ... ok
> test_eq (tests.unit.test_base.ByteMatrixTest)
> Test equality. ... ok
> test_fromhex (tests.unit.test_base.ByteMatrixTest)
> Test unpacking packed representation. ... ok
> test_getitem (tests.unit.test_base.ByteMatrixTest)
> Test int and slice indexing. ... ok
> test_hex (tests.unit.test_base.ByteMatrixTest)
> Test hex representation. ... ok
> test_hextend (tests.unit.test_base.ByteMatrixTest)
> Test horizontal extending. ... ok
> test_hrepeat (tests.unit.test_base.ByteMatrixTest)
> Test horizontal repeating. ... ok
> test_hstack (tests.unit.test_base.ByteMatrixTest)
> Test horizontal stacking. ... ok
> test_htile (tests.unit.test_base.ByteMatrixTest)
> Test horizontal tiling. ... ok
> test_int (tests.unit.test_base.ByteMatrixTest)
> Create matrix with all elements equal. ... ok
> test_list_of_bytes (tests.unit.test_base.ByteMatrixTest)
> Create matrix from list of bytes. ... ok
> test_list_of_list (tests.unit.test_base.ByteMatrixTest)
> Create matrix from list of list. ... ok
> test_move (tests.unit.test_base.ByteMatrixTest)
> Test moving submatrix. ... ok
> test_ne (tests.unit.test_base.ByteMatrixTest)
> Test nonequality. ... ok
> test_pack (tests.unit.test_base.ByteMatrixTest)
> Test packed representation. ... ok
> test_render (tests.unit.test_base.ByteMatrixTest)
> Test rendering. ... ok
> test_repr (tests.unit.test_base.ByteMatrixTest)
> Debugging repr. ... ok
> test_setitem (tests.unit.test_base.ByteMatrixTest)
> Test int and slice assignment. ... ok
> test_setitem_bad (tests.unit.test_base.ByteMatrixTest)
> Test slice assignment to bad type. ... ok
> test_setitem_int (tests.unit.test_base.ByteMatrixTest)
> Test slice assignment to same int. ... ok
> test_to_bytes (tests.unit.test_base.ByteMatrixTest)
> Test to_bytes. ... ok
> test_to_rows (tests.unit.test_base.ByteMatrixTest)
> Test to_rows. ... ok
> test_unpack (tests.unit.test_base.ByteMatrixTest)
> Test unpacking packed representation. ... ok
> test_vextend (tests.unit.test_base.ByteMatrixTest)
> Test vertical extending. ... ok
> test_view (tests.unit.test_base.ByteMatrixTest)
> Test viewing. ... ok
> test_view_from_buffer (tests.unit.test_base.ByteMatrixTest)
> Test view over buffer with pitch. ... ok
> test_vrepeat (tests.unit.test_base.ByteMatrixTest)
> Test vertical reapeating. ... ok
> test_vstack (tests.unit.test_base.ByteMatrixTest)
> Test vertical stacking. ... ok
> test_vtile (tests.unit.test_base.ByteMatrixTest)
> Test vertical tiling. ... ok
>
Bug#982712: marked as done (tiledarray: FTBFS: gemm_helper.h:168:30: error: expected initializer before ‘const’)
Your message dated Sun, 02 Jan 2022 17:05:28 +
with message-id
and subject line Bug#982712: fixed in tiledarray 1.0.0-1
has caused the Debian Bug report #982712,
regarding tiledarray: FTBFS: gemm_helper.h:168:30: error: expected initializer
before ‘const’
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.)
--
982712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledarray
Version: 0.6.0-5.2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /<>/src/TiledArray/math/vector_op.h: In instantiation of ‘void
> TiledArray::math::for_each_block(Op&&, Result*, const Args* const ...) [with
> Op = TiledArray::math::copy_block:: TiledArray::detail::param_type)>; Result = double; Args = {double}]’:
> /<>/src/TiledArray/math/vector_op.h:221:21: required from
> ‘void TiledArray::math::copy_block(Result*, const Arg*) [with Result =
> double; Arg = double]’
> /<>/src/TiledArray/math/vector_op.h:273:51: required from
> ‘void TiledArray::math::Block< >::store(T*) const
> [with T = double]’
> /<>/src/TiledArray/math/vector_op.h:369:27: required from
> ‘void TiledArray::math::inplace_vector_op_serial(Op&&, std::size_t, Result*,
> const Args* const ...) [with Op = TiledArray::Tensor<
> , >::add_to Eigen::aligned_allocator >:: Eigen::aligned_allocator >::numeric_type&)>&; Result = double; Args =
> {}; typename std::enable_if Args ...)>::type>::value>::type* = 0; std::size_t = long unsigned
> int]’
> /<>/src/TiledArray/math/vector_op.h:428:33: required from
> ‘void TiledArray::math::inplace_vector_op(Op&&, std::size_t, Result*, const
> Args* const ...) [with Op = TiledArray::Tensor< ,
> >::add_to
> >::
> >::numeric_type&)>&; Result = double; Args = {}; typename
> std::enable_if ...)>::type>::value>::type* = 0; std::size_t = long unsigned int]’
> /<>/src/TiledArray/tensor/kernels.h:107:30: required from
> ‘void TiledArray::detail::inplace_tensor_op(Op&&, TR&, const Ts& ...) [with
> Op = TiledArray::Tensor< ,
> >::add_to
> >::
> >::numeric_type&)>&; TR = TiledArray::Tensor Eigen::aligned_allocator >; Ts = {}; typename
> std::enable_if<(TiledArray::detail::is_tensor::value &&
> TiledArray::detail::is_contiguous_tensor::value)>::type*
> = 0]’
> /<>/src/TiledArray/tensor/tensor.h:625:32: required from
> ‘TiledArray::Tensor< ,
> >::Tensor_& TiledArray::Tensor< ,
> >::inplace_unary(Op&&) [with Op =
> TiledArray::Tensor< ,
> >::add_to
> >::
> >::numeric_type&)>; T = double; A = Eigen::aligned_allocator;
> TiledArray::Tensor< ,
> >::Tensor_ = TiledArray::Tensor >]’
> /<>/src/TiledArray/tensor/tensor.h:791:27: required from
> ‘TiledArray::Tensor< ,
> >::Tensor_& TiledArray::Tensor< ,
> >::add_to(TiledArray::Tensor<
> , >::numeric_type) [with T =
> double; A = Eigen::aligned_allocator; TiledArray::Tensor<
> , >::Tensor_ =
> TiledArray::Tensor >;
> TiledArray::Tensor< ,
> >::numeric_type = double]’
> /<>/src/TiledArray/tensor/tensor.cpp:31:18: required from here
> /<>/src/TiledArray/math/vector_op.h:155:29: error: no matching
> function for call to
> ‘TiledArray::math::VectorOpUnwind<7>::for_each(TiledArray::math::copy_block double>::)>&, double*
> const&, const double* const&)’
> 155 | VecOpUnwindN::for_each(op, result, args...);
> | ~~^
> /<>/src/TiledArray/math/vector_op.h:107:7: note: candidate:
> ‘template static void
> TiledArray::math::VectorOpUnwind< >::for_each(Op&&, Result*) [with
> Op = Op; Result = Result; Args = {Args ...}; long unsigned int N = 7]’
> 107 | for_each(Op&& op, Result* restrict const result, const Args*
> restrict const ...args) {
> | ^~~~
> /<>/src/TiledArray/math/vector_op.h:107:7: note: template
> argument deduction/substitution failed:
> /<>/src/TiledArray/math/vector_op.h:155:29: note: candidate
> expects 2 arguments, 3 provided
> 155 | VecOpUnwindN::for_each(op, result, args...);
> | ~~^
> /<>/src/TiledArray/math/vector_op.h: In instantiation of ‘void
> TiledArray::math::for_each_block(Op&&, Result*, const Args* const ...) [with
> Op = TiledArray::math::copy_block:: TiledArray::detail::param_type)>; Result = float; Args = {float}]’:
> /<>/src/TiledArray/math/vector_op.h:221:21: required from
> ‘void
Processed: elkcode FTBFS with libxc 5.1.7
Processing control commands: > close -1 7.2.42-1 Bug #1003005 [src:elkcode] elkcode FTBFS with libxc 5.1.7 Marked as fixed in versions elkcode/7.2.42-1. Bug #1003005 [src:elkcode] elkcode FTBFS with libxc 5.1.7 Marked Bug as done -- 1003005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003005: elkcode FTBFS with libxc 5.1.7
Source: elkcode Version: 6.3.2-2 Severity: serious Tags: ftbfs bookworm sid Control: close -1 7.2.42-1 https://buildd.debian.org/status/package.php?p=elkcode=sid ... mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp -fallow-argument-mismatch `dpkg-buildflags --get LDFLAGS` -o elk modmain.o modmpi.o libxc_funcs.o libxc.o libxcifc.o modxcifc.o modfxcifc.o moddftu.o modrdm.o modphonon.o modscdft.o modtest.o modrandom.o modstore.o modpw.o modvars.o modtddft.o modgw.o modulr.o modjx.o modomp.o mkl_stub.o mkl_init.o oblas_stub.o oblas_init.o blis_stub.o blis_init.o w90_stub.o modw90.o zfftifc_fftw.o elk.o zbsht.o zfsht.o rbsht.o rfsht.o projsbf.o fsmooth.o nfftifc.o rfinp.o splint.o spline.o wsplint.o wsplintp.o splintwp.o sphcover.o r3frac.o genvsig.o gencfun.o zfpack.o addlorbcnd.o rfint.o sortidx.o gengkvec.o pade.o pades.o rfint0.o zfinp.o symrvf.o genapwfr.o rfcopy.o rhomagsh.o genylmg.o olpaa.o readfermi.o factr.o writechg.o zflmconj.o rminv.o zminv.o rlmrot.o rotrflm.o ztorflm.o rotzflm.o rfmtlm.o genzrm.o gensfacgp.o zmctmu.o zmctm.o hmlfv.o olpfv.o axangsu2.o checkmt.o symrf.o z2mm.o z2mctm.o z2mmct.o writefermi.o findnjcmax.o findscq.o plot1d.o plot2d.o plot3d.o hmllolo.o olprad.o occupy.o findkpt.o zfmtint.o rotrfmt.o forcek.o eveqnfvr.o findsym.o genvbmatk.o wigner3jf.o wigner6j.o mixbroyden.o zftrf.o gensocfr.o getcfgq.o wigner3j.o moke.o sfacinit.o sfacrho.o sfacmag.o gradwfcr2.o symrvfmt.o oepmain.o oepresk.o oepvcl.o oepvclk.o dbxcplot.o writehmlbse.o hmldbse.o hmldbsek.o dielectric_bse.o genidxbse.o writeevbse.o genwfpw.o writewfpw.o getwfpw.o genexpmat.o elnes.o potefield.o eulerrot.o fermisurfbxsf.o symmetry.o findsymcrys.o findsymsite.o plotpt1d.o writedos.o findprimcell.o proj2d.o nonlinopt.o vecplot.o wfcrplot.o energykncr.o eveqnss.o gendmatk.o gensdmat.o ggamt_1.o ggair_1.o ggamt_sp_1.o ggair_sp_1.o ggamt_2a.o ggair_2a.o ggamt_2b.o ggair_2b.o ggamt_sp_2a.o ggair_sp_2a.o ggamt_sp_2b.o ggair_sp_2b.o genspecies.o writeemd.o writeexpmat.o rotdmat.o hrmdmat.o reademd.o emdplot.o rfhkintp.o emdplot3d.o emdplot2d.o emdplot1d.o plotpt3d.o plotpt2d.o writeevsp.o torque.o ssfsmjx.o wxcplot.o effmass.o genlmirep.o ssfext.o sstask.o spiralsc.o genscss.o genfspecies.o writespecies.o exxengy.o exxengyk.o xc_c_tb09.o elfplot.o potplot.o mae.o writestate.o readstate.o rotaxang.o axangrot.o dmatls.o gendmat.o numlist.o sbesseldm.o genvchi0.o genspchi0.o vclcore.o hmlxbse.o hmlxbsek.o genvmatk.o writeepsinv.o putepsinv.o curden.o curdenk.o hflocal.o dielectric.o bdipole.o roteuler.o lopzflm.o eveqnfvz.o rhomag.o hmlaa.o hmlalo.o gencore.o gentau.o gentauk.o hmlistl.o olpistl.o gengclg.o hmlrad.o rhonorm.o rfmtsm.o olplolo.o genshtmat.o allatoms.o rtozflm.o rtozfmt.o gauntyry.o fderiv.o moment.o sctovec.o match.o writeinfo.o rfpack.o gaunt.o readinput.o ztorfmt.o putevecfv.o zfmtinp.o zfcmtinp.o writelinen.o writekpts.o rfmtinp.o brzint.o rhocore.o writelat.o mtdmin.o atpstep.o potcoul.o zfmtconj.o symrfmt.o putpmat.o eveqnz.o olpalo.o checkfsm.o rhoplot.o potnucl.o potxc.o erf.o gradzf.o writegeom.o linengy.o bandstr.o gengvc.o gengclq.o closefiles.o writefsm.o eveqn.o rhomagk.o factnm.o atom.o radnucl.o charge.o genrmesh.o genapwlofr.o wavefmt.o genzrho.o potks.o sbessel.o clebgor.o hermite.o findband.o genbs.o gencfrc.o genws.o chargemt.o gndstate.o addbfsm.o initoep.o orthevsv.o fermisurf.o findswidth.o gradrf.o dos.o gradzfmt.o nuclei.o writesym.o zftzf.o polynm.o rdirac.o zfmtftoc.o rfmtftoc.o gradrfmt.o genzvclmt.o getevalfv.o mixlinear.o gengvec.o putevalfv.o rfmtpack.o zfmtpack.o writestrain.o writeforces.o r3mv.o r3mtv.o r3cross.o r3minv.o r3mdet.o r3mm.o r3mtm.o r3mmt.o r3vo.o symvec.o curdenplot.o hartfock.o eveqnhf.o zpotclmt.o genlofr.o rfinpc.o eveqnit.o genzfrm.o gengqrf.o writepmat.o genwfsv.o writelsj.o writesf.o rzfinp.o genjlgprmt.o gridsize.o sphcrd.o writeiad.o readspecies.o i3mtv.o writeeval.o i3minv.o i3mdet.o genevfsv.o getpmat.o timesec.o mixpack.o mixerifc.o symmat.o rhoinit.o maginit.o rvfcross.o eveqnfv.o energynn.o rfinterp.o rfplot.o geomopt.o ylmroty.o ylmrot.o gcd.o sdelta.o stheta.o sdelta_mp.o stheta_mp.o sdelta_fd.o stheta_fd.o sdelta_sq.o stheta_sq.o sdelta_lr.o stheta_lr.o mossbauer.o gentpmae.o symveca.o massnucl.o wavefcr.o gradwf2.o geomplot.o findngkmax.o reciplat.o genrlmv.o genvmat.o putoccsv.o getoccsv.o curlrvf.o latvstep.o energy.o delevec.o rdiracint.o rzfmtinp.o genstrain.o genstress.o writestress.o rschrodint.o mixadapt.o genffacgp.o genidxlo.o writeengy.o genpmatk.o putevecsv.o getevecsv.o writegclq.o putevalsv.o genppts.o force.o vecfbz.o rfirsm.o gengclgq.o findsymlat.o grad2rfmt.o findqpt.o zftwfir.o symrfir.o symrvfir.o getevalsv.o genjlgpr.o init0.o init1.o init2.o init3.o init4.o genpmat.o putkmat.o getkmat.o genkmat.o genexpmt.o epsinv.o getevecfv.o zfmtctof.o wfplot.o straingkq.o symdmat.o genylmv.o nesting.o eveqnsv.o
Bug#1001145: marked as done (vdeplug-agno: Drop explicit library dependencies)
Your message dated Sun, 02 Jan 2022 16:51:33 + with message-id and subject line Bug#1001145: fixed in vdeplug-agno 0.1.1-1 has caused the Debian Bug report #1001145, regarding vdeplug-agno: Drop explicit library dependencies 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.) -- 1001145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdeplug-agno Version: 0.1.0-3 Severity: important Please drop these from the Depends line of your debian/control. They are added by the build already by default. libvdeplug2 (>= 4), libwolfssl24 If you add them manually, it will require manual handling when those libraries get new soname versions. For instance, wolfssl has a new version pending in the NEW queue. Also, I think you can drop this dependency: libssl1.1 That dependency is not automatically added. I don't use vdplug and I wasn't able to test for sure whether it's unneeded. Debian and Ubuntu are doing a switch from ssl1.1 to ssl3.0 soon though. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: vdeplug-agno Source-Version: 0.1.1-1 Done: Renzo Davoli We believe that the bug you reported is fixed in the latest version of vdeplug-agno, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Renzo Davoli (supplier of updated vdeplug-agno 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, 02 Jan 2022 11:55:48 +0100 Source: vdeplug-agno Architecture: source Version: 0.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian VirtualSquare Team Changed-By: Renzo Davoli Closes: 1001145 Changes: vdeplug-agno (0.1.1-1) unstable; urgency=medium . [ Renzo Davoli ] * New upstream version 0.1.1: + Fix ssl dependency detection. * d/control: do not manually Depend on shared libraries. Closes: #1001145 . [ Mattia Rizzolo ] * d/watch: drop unneeded uupdate call, and wrong filenamemange option. * d/rules: delete commented-out options. * d/rules: delete -Wl,--as-needed, default behaviour in bullseye. * d/control: Bump Standards-Version to 4.6.0, no changes needed. * d/control: Mark libvdeplug-agno as Multi-Arch:same (from the M-A hinter). Checksums-Sha1: 8e6cdd785bf91575aef3b9476be4a0480e5f0e47 2110 vdeplug-agno_0.1.1-1.dsc 2b1aa2f4c841ec5aadd11cc531b338eab88db466 17369 vdeplug-agno_0.1.1.orig.tar.gz 33b5469931d1d73edb3257f793dbc8a1fc32703e 2312 vdeplug-agno_0.1.1-1.debian.tar.xz 77f6e839f2333b6596e29d39dd2dc53f4d3cfc15 6999 vdeplug-agno_0.1.1-1_amd64.buildinfo Checksums-Sha256: 86256e051c8d199fe8b4f1acf1cc7197481e50ba306f8dc5122af2b72bd37088 2110 vdeplug-agno_0.1.1-1.dsc e3b1c9ba055b85a1c1cf982e2153a8bfe6fec614c32bec3d49649c57f906297e 17369 vdeplug-agno_0.1.1.orig.tar.gz b0cae1833bbca935203a071ea4edf4b086fc7edb9fc716cc0d6979a7c860d529 2312 vdeplug-agno_0.1.1-1.debian.tar.xz 98ff619e366c76a78adeac8af2ba7e2f3f8454ed92d4b2a956442743f8dd238b 6999 vdeplug-agno_0.1.1-1_amd64.buildinfo Files: cba39a774ef101f1aad46b4fa96fcfc1 2110 libs optional vdeplug-agno_0.1.1-1.dsc 69d8f56d70a49a6c1f02e100fe762194 17369 libs optional vdeplug-agno_0.1.1.orig.tar.gz 920f4beba8ed7fef95b7135e6f5b963f 2312 libs optional vdeplug-agno_0.1.1-1.debian.tar.xz 7219cc416ced2f8008b2f47f53656969 6999 libs optional vdeplug-agno_0.1.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmHR1TEACgkQCBa54Yx2 K60+9w/+LneUKzQUEkD8Di+NiefMzaHBIy49OPR57JZVWgShrHfjMOXT+SHPZgwP Jbgh5UuMcXmc92B02dT34C76tBR+iwccM5Ap29IEQ25tUWOSiF+TZyxrgXBhzZlW v7ao0wxd72FywGby8mqMWXyOWsKKUU+0giwb9DX1kIWpzfxoeuEsQ1LSVjE6YNU8 r4hAdnRxb6vOFtVyotHGEgqqdZMNY01CbcSuROq1yaV07XrcXkP4E5oHRJ9ZCqda GJvKVdNoHCWY6duHWtAkcJWByaUF7/uiO4mEIrg/54OhTIP2bXHSXtUS0VFbi0ju tX6bMrLnlcPEHunyRR1esyVaEyJ5sCe5lkO0nHrwfh64ElafUEPKlO5wr4jOSLuL khW9oEIyW6HoziLSKt4Jfvo7tH8oWzBqn+SOEtg2siMbZc1cFR9wAT8IWSTqr0Zt BcqNnggN8uvSdK9B6EaX9IwjujGBfJ1kZJyglBPcSj+Plz6/PKWxJpzc9DcrRWvr GN6AihiD2qLw5QT+kj/POxor4sw+68BZUgUNPA76mlGY/H+OE0/2YmRSJQLcwJFm
Bug#997748: marked as done (libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, li
Your message dated Sun, 02 Jan 2022 16:18:44 + with message-id and subject line Bug#997748: fixed in libcomps 0.1.15-5 has caused the Debian Bug report #997748, regarding libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23) 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.) -- 997748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcomps Version: 0.1.15-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > cd /<>/build/src/python/docs && set -E > /<>/build/src: > cd /<>/build/src/python/docs && /usr/bin/cmake -E make_directory > /<>/build/src/python/src//libcomps/comps/ > copy /<>/libcomps/src/python/tests//__test.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/__test.py > /<>/build/src/python/src//libcomps/ > copy /<>/libcomps/src/python/tests//test_libcomps.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/test_libcomps.py > /<>/build/src/python/src//libcomps/ > copy /<>/libcomps/src/python/tests//test_merge_comps.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/test_merge_comps.py > /<>/build/src/python/src//libcomps/ > copy /<>/libcomps/src/python/tests//utest.py to > /<>/build/src/python/src//libcomps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests/utest.py > /<>/build/src/python/src//libcomps/ > /<>/libcomps/src/python/tests//comps/biarchonly.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/biarchonly.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps-f21.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps-f21.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps-f21.xml.in to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps-f21.xml.in > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps-rawhide.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps-rawhide.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps_empty_by_lang_tags.xml > to /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps_empty_by_lang_tags.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps_part1.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps_part1.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/comps_part2.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/comps_part2.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/f21-rawhide-comps.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/f21-rawhide-comps.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/fedora_comps.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/fedora_comps.xml > /<>/build/src/python/src//libcomps/comps/ > /<>/libcomps/src/python/tests//comps/main_arches.xml to > /<>/build/src/python/src//libcomps/comps/ > cd /<>/build/src/python/docs && /usr/bin/cmake -E copy > /<>/libcomps/src/python/tests//comps/main_arches.xml >
Bug#1002376: python-aiosqlite: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
On Sunday, 02 January 2022, 13:15 +0100, Benjamin Hof wrote: > compatible to mistune v2 At the moment this is not the case.
Bug#1003003: libqalculate FTBFS on architectures where char is unsigned
Source: libqalculate Version: 3.22.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libqalculate ... FAIL: unittest == [32m ./tests/variables.batch - 11 tests passed [0m[32m ./tests/units.batch - 13 tests passed [0m[31m Mismatch detected at line 42 char(0xD8) expected ''Ø'' received '"Ø"' [0mRunning all unit tests Running unit tests from 'variables.batch' Running unit tests from 'units.batch' Running unit tests from 'strings.batch' FAIL unittest (exit status: 1) Testsuite summary for libqalculate 3.22.0 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See src/test-suite.log make[4]: *** [Makefile:835: test-suite.log] Error 1
Processed: Re: borgbackup: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> close -1
Bug #1002404 [src:borgbackup] borgbackup: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p 3.9 returned exit code 13
Marked Bug as done
> severity -1 normal
Bug #1002404 {Done: Gianfranco Costamagna }
[src:borgbackup] borgbackup: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
Severity set to 'normal' from 'serious'
--
1002404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002404: borgbackup: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
control: close -1 control: severity -1 normal Hello Lucas, I tried on reproducible builds, and I saw some failures some time ago, but I retried today and everything was good. So I presume something in the build-deps got fixed in the meanwhile? e.g. https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/borgbackup_1.1.17-1.rbuild.log.gz G. On Wed, 22 Dec 2021 08:50:10 +0100 Lucas Nussbaum wrote: > Source: borgbackup > Version: 1.1.17-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > python3 setup.py build_ext --inplace > > Detected and preferring liblz4 over bundled LZ4 > > Detected and preferring libb2 over bundled BLAKE2 > > Detected and preferring libzstd over bundled ZSTD > > Detected and preferring libxxhash over bundled XXHASH > > running build_ext > > skipping 'src/borg/algorithms/msgpack/_packer.cpp' Cython extension > > (up-to-date) > > skipping 'src/borg/algorithms/msgpack/_unpacker.cpp' Cython extension > > (up-to-date) > > skipping 'src/borg/compress.c' Cython extension (up-to-date) > > skipping 'src/borg/crypto/low_level.c' Cython extension (up-to-date) > > skipping 'src/borg/hashindex.c' Cython extension (up-to-date) > > skipping 'src/borg/item.c' Cython extension (up-to-date) > > skipping 'src/borg/chunker.c' Cython extension (up-to-date) > > skipping 'src/borg/algorithms/checksums.c' Cython extension (up-to-date) > > skipping 'src/borg/platform/posix.c' Cython extension (up-to-date) > > skipping 'src/borg/platform/linux.c' Cython extension (up-to-date) > > skipping 'src/borg/platform/syncfilerange.c' Cython extension (up-to-date) > > building 'borg.algorithms.msgpack._packer' extension > > x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g > > -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat > > -Werror=format-security -g -fwrapv -O2 -g -O2 > > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > > -D__LITTLE_ENDIAN__=1 -I/usr/include -I/usr/include -I/usr/include > > -I/usr/include -I/usr/include -I/usr/include -I/usr/include/python3.9 -c > > src/borg/algorithms/msgpack/_packer.cpp -o > > build/temp.linux-x86_64-3.9/src/borg/algorithms/msgpack/_packer.o > > x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g > > -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 > > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > > build/temp.linux-x86_64-3.9/src/borg/algorithms/msgpack/_packer.o -o > > /<>/src/borg/algorithms/msgpack/_packer.cpython-39-x86_64-linux-gnu.so > > building 'borg.algorithms.msgpack._unpacker' extension > > x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g > > -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat > > -Werror=format-security -g -fwrapv -O2 -g -O2 > > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > > -D__LITTLE_ENDIAN__=1 -I/usr/include -I/usr/include -I/usr/include > > -I/usr/include -I/usr/include -I/usr/include -I/usr/include/python3.9 -c > > src/borg/algorithms/msgpack/_unpacker.cpp -o > > build/temp.linux-x86_64-3.9/src/borg/algorithms/msgpack/_unpacker.o > > x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g > > -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 > > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > > build/temp.linux-x86_64-3.9/src/borg/algorithms/msgpack/_unpacker.o -o > > /<>/src/borg/algorithms/msgpack/_unpacker.cpython-39-x86_64-linux-gnu.so > > building 'borg.compress' extension > > x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g > > -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat > > -Werror=format-security -g -fwrapv -O2 -g -O2 > > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > > -DBORG_USE_LIBLZ4=YES -DBORG_USE_LIBB2=YES -DBORG_USE_LIBZSTD=YES > > -DBORG_USE_LIBXXHASH=YES -DXXH_PRIVATE_API=YES -I/usr/include > > -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include > > -I/usr/include/python3.9 -c src/borg/compress.c -o > > build/temp.linux-x86_64-3.9/src/borg/compress.o > > x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g > > -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 > > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > > build/temp.linux-x86_64-3.9/src/borg/compress.o -llz4 -lzstd -o > >
Bug#1002961: [Pkg-pascal-devel] Bug#1002961: src:castle-game-engine: fails to migrate to testing for too long: FTBFS on armel
Hi Abou, On 02-01-2022 14:22, Abou Al Montacir wrote: The issue is that there seem to be a bug in the compiler. However, I'm not able to understand what kind of issue and cloud not produce a small code that triggers it. Moreover, it seems that the bug itself is triggered only when running the full battery of tests. Then the failing test starts to fail. If the test is ran alone (after a machine reboot, or after a while) then it will succeed, but it one runs it after running the full test suite then it will fail systematically. No clue how to go forward and no enough information to open an upstream compiler bug. Moreover CGE upstream think we should abandon armel (and other non widely used architectures) as a target for CGE, but I think myself it is a good test for the compiler and tend to think we should keep it. I agree with you. However, as a Release Team member, I also want to prevent packages from being out-of-sync for too long. So, what I suggest in this case is to temporarily disable the test on armel until we have figured out how to fix the situation. That way the package can migrate to testing, without making the situation much worse there. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1002526: marked as done (python-django-extensions: autopkgtest needs update for new version of pygments: textual change)
Your message dated Sun, 2 Jan 2022 16:10:56 +0100
with message-id <2894652a-bb9b-cdb5-d5b8-c6521d723...@debian.org>
and subject line 1002526 fixed in unstable; python-django-extensions:
autopkgtest needs update for new version of pygments: textual change
has caused the Debian Bug report #1002526,
regarding python-django-extensions: autopkgtest needs update for new version of
pygments: textual change
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.)
--
1002526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-extensions
Version: 3.1.5-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, pygme...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pygments
Dear maintainer(s),
With a recent upload of pygments the autopkgtest of
python-django-extensions fails in testing when that autopkgtest is run
with the binary packages of pygments from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
pygments from testing2.10.0+dfsg-1
python-django-extensions from testing3.1.5-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. Seems like
some output was changed a bit.
Currently this regression is blocking the migration of pygments to
testing [1]. Of course, pygments shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
pygments was intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from pygments should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pygments
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-extensions/17802853/log.gz
=== FAILURES
===
SyntaxColorTagTests.test_should_colorize_noclasses_with_default_lexer _
self = testMethod=test_should_colorize_noclasses_with_default_lexer>
def test_should_colorize_noclasses_with_default_lexer(self):
ctx = Context({'code_string': 'TEST'})
content = """{% load syntax_color %}
{{ code_string|colorize_noclasses }}
"""
expected_result = '''style="background: #f8f8f8">h1TEST/h1
'''
result = Template(content).render(ctx)
> self.assertHTMLEqual(result, expected_result)
tests/templatetags/test_syntax_color.py:93: _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/django/test/testcases.py:795: in
assertHTMLEqual
self.fail(self._formatMessage(msg, standardMsg))
E AssertionError:
E
E
E -
E +
E ? +++
E E
E
E TEST
E
E
E
E
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.1.5-2
Hi,
I triggered the autopkgtest of python-django-extensions version 3.1.5-2
in testing with pygments from unstable. The test passed.
However, as nothing is ensuring the right combination of tests are
checked, this still blocks migration of both python-django-extensions
and pygments.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Bug#997748: libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23)
On Sun, Jan 02, 2022 at 03:36:11PM +0100, Frédéric Pierret wrote: > Yes it's enough. I'm already adding it in libcomps. I should upload soon :) cool! & thank you! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Plastic bottles: made to last forever, designed to throw away. signature.asc Description: PGP signature
Bug#999806: pygattlib: Misbuild with multiple supported python versions
Hi Nobuhiro, [...] > Python3.10 has been introduced in Ubuntu, and as part of the rebuild > of packages against 3.10 I noticed that pygattlib misbuilds, linking > both the python3.9 and python3.10 extensions against the same version > of libboost_python instead of linking each against the matching > version. > > The attach patch fixes the build so that each binary extension will > always be built against the matching libboost_python. This bug is causing my dependent package gnome-keysign to drop out of testing soon, so I would be happy to NMU this patch if you are fine with that. Please let me know if you have any objections, otherwise I will prepare a NMU in a week or so. Thanks, and have a happy new year! Sascha
Bug#997748: libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23)
Hi, Le 1/2/22 à 15:10, Holger Levsen a écrit : hi, On Sun, Oct 24, 2021 at 01:39:00PM +0200, Lucas Nussbaum wrote: Source: libcomps Version: 0.1.15-4 Severity: serious [...] During a rebuild of all packages in sid, your package failed to build on amd64. [...] Running Sphinx v4.2.0 Configuration error: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23) make[5]: *** [src/python/docs/CMakeFiles/pydocs.dir/build.make:122: pydocs] Error 2 It seems to me we can fix this bug by simply taking the patch from https://github.com/rpm-software-management/libcomps/commit/5eebd94a7ce855979eb014595256eee17ee6b359 Can someone confirm? I'd be happy to sponsor an upload again :) Yes it's enough. I'm already adding it in libcomps. I should upload soon :) Frédéric OpenPGP_signature Description: OpenPGP digital signature
Bug#965529: marked as done (fstrcmp: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sun, 02 Jan 2022 14:48:33 + with message-id and subject line Bug#965529: fixed in fstrcmp 0.7.D001-2 has caused the Debian Bug report #965529, regarding fstrcmp: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fstrcmp Version: 0.7.D001-1.1 Severity: normal Usertags: compat-5-6-removal Hi, The package fstrcmp uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: fstrcmp Source-Version: 0.7.D001-2 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of fstrcmp, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated fstrcmp 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, 02 Jan 2022 15:30:17 +0100 Source: fstrcmp Architecture: source Version: 0.7.D001-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Mattia Rizzolo Closes: 965529 Changes: fstrcmp (0.7.D001-2) unstable; urgency=medium . * QA upload. * Orphan the package. See #765334 * Bump debhelper compat level to 7. Closes: #965529 Checksums-Sha1: ba7592b5f997c4387e753df372c50d47ede2e3d8 2000 fstrcmp_0.7.D001-2.dsc 90540f592c7c97314029b1cc69be0e0800898fe4 5256 fstrcmp_0.7.D001-2.diff.gz 524416a8cd525d7eaf4d6a8477191c810856e54e 8194 fstrcmp_0.7.D001-2_amd64.buildinfo Checksums-Sha256: a09f8230fececdc97ae58c299e05f6efe1ded8dc58f362c04c4e5e43c69c762b 2000 fstrcmp_0.7.D001-2.dsc 8975a9dc21fbbcd7cd4f8864750fba87a03af950a385dfae1d8d079e1599ee90 5256 fstrcmp_0.7.D001-2.diff.gz 19ff00729d58173ed7c53805ba079a7c384733de76596ac0929836ff9f8a1de8 8194 fstrcmp_0.7.D001-2_amd64.buildinfo Files: 4bf758b010f46903cd327ccac0b0c5ba 2000 devel optional fstrcmp_0.7.D001-2.dsc 298efee71e3b21ca0b70db795b3d12ae 5256 devel optional fstrcmp_0.7.D001-2.diff.gz 21a7160a32c893ad813ab7d5b70f4902 8194 devel optional fstrcmp_0.7.D001-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmHRuEkACgkQCBa54Yx2 K63KjA/+L9R/euJWeRZyafFy5D0NzwM7BL+3Y6q8CgNviZy/3AwishfFmTA0Z55P ihbKRcz5znuld97Ru4JaZT68Z/tMZJqBeP0TRtDftEQGiRfcLCQ4GScQkPAhdeie A3fcGiXO77e0/HbtoT6xyuJS9amO5oI8frHF2iybh2YSCoKnpUqip+mTCiNtIpNt C85TzE9bSq565AJ0w97yxDEloR5ffh0Bi8783fG7yPFcmK2WP3vK4NXEhb69093R aNGBGS5DAHRIj5NvpwAK7FzLnTD8xI7mQrpWl3Qsf63fDLRcHbGY/9hKpitNclnd EsjfmrasJb9AVyF9NOkx9r7GU6egiAFt7P/X67OFNk+Q8XmFkws/pggIxX2ehWWE IlFx+r2RJz/SbQHbl1bRtoDCZThPaVT1QwpumdnFcOxVFCRM4izQQr22SRnonKJ/ mR0mIF7ul6l3DG8SfpIr47YRQ8IMCcA0932SUgr22BJ44O6Kd+MpyFFDebjsgGpu PDWq4SUJidzuNAW5Op8iFbXRJvVBSMDdn4hG6GTlHHPhubz1hky8b8hDoRrCHf3a HTJdqS8bMwXdz5qTOfs4y7Qd/pTJX9eYPpQaJCiGgxS2MS2aybqM8iGBRATEyZ2j a6klw6NQqwrAEyPVnrqe0S3cEuW7fkxRtP9zG1XhFM0iLcKy5hM= =xiDp -END PGP SIGNATURE End Message ---
Bug#1000267: marked as done (php8.1-cgi: SIGSEGV on pi-hole)
Your message dated Sun, 2 Jan 2022 15:47:00 +0100
with message-id
and subject line Re: php8.1-cgi: SIGSEGV on pi-hole
has caused the Debian Bug report #1000267,
regarding php8.1-cgi: SIGSEGV on pi-hole
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.)
--
1000267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php8.1-cgi
Version: 8.1.0~rc5-1
Severity: serious
With the update from 7.4 to 8.1 php crashes with SIGSEGV when trying
to access the pi-hole web-interface.
Coredump:
Core was generated by `/usr/bin/php-cgi'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xad99a8d4 in zend_gc_delref (p=0xad75be40 <_start>)
at ./Zend/zend_types.h:1185
Download failed: Invalid argument. Continuing without source file
./cgi-build/./Zend/zend_types.h.
1185./Zend/zend_types.h: No such file or directory.
(gdb) bt full
#0 0xad99a8d4 in zend_gc_delref (p=0xad75be40 <_start>)
at ./Zend/zend_types.h:1185
No locals.
#1 zend_string_release_ex (persistent=false, s=0xad75be40
<_start>) at ./Zend/zend_string.h:329
No locals.
#2 zend_file_handle_dtor (fh=0xc21cee70) at ./Zend/zend_stream.c:232
No locals.
#3 0xad99aff8 in zend_destroy_file_handle
(file_handle=file_handle@entry=0xc21cee70) at
./Zend/zend_stream.c:273
No locals.
#4 0xad75b458 in main (argc=, argv=) at ./sapi/cgi/cgi_main.c:2554
__orig_bailout =
__bailout = {{__jmpbuf = {187650035731128, 0, 187650035610516,
187650035731696, 1, 18446743506773868542, 1, 281473938420808, 0, 0,
281473938418736, 3618190865862285457, 52683048, 3618132373186647353,
0, 0, 0, 0, 0, 0, 0, 0}, __mask_was_saved = 0,
__saved_mask = {__val = {281473013192584, 12, 20, 0, 1, 0,
1, 0, 281470681743361, 281473013215232, 281473938420336,
281473013108508, 281473013039360, 281472970824464, 281472970826400,
281473938420824
free_query_string =
exit_status =
cgi =
c =
i =
len =
file_handle = {handle = {fp = 0x0, stream = {handle = 0x0,
isatty = 0, reader = 0xc21cef88, fsizer = 0x8af81630
<_rtld_global_ro>, closer = 0x8af4f000}}, filename = 0x0,
opened_path = 0xad75be40 <_start>, type = 0 '\000',
primary_script = false, in_list = false, buf = 0xc21ceef0
"?:", len = 281473013058840}
s =
behavior =
no_headers =
orig_optind =
orig_optarg =
script_file =
ini_entries_len =
max_requests =
requests =
fastcgi =
bindpath =
fcgi_fd =
request =
warmup_repeats =
repeats =
benchmark =
start = {tv_sec = 1, tv_usec = 281473013256192}
end = {tv_sec = 281473013256192, tv_usec = 281473013060560}
status = 0
query_string =
decoded_query_string =
skip_getopt =
Lighttp logs:
[error.log]
2021-11-20 17:39:42: (http-header-glue.c.1332) read() 11 13:
Connection reset by peer
2021-11-20 17:39:42: (gw_backend.c.2398) response not received,
request sent: 828 on socket: unix:/run/lighttpd/php.socket-0 for
/pihole/index.php?, closing connection
[access.log]
1637426382|192.168.24.201|GET / HTTP/1.1|500|365
/etc/php/8.1/cgi/php.ini:
engine = On
short_open_tag = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = -1
disable_functions =
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifcontinued,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_sigprocmask,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_stre
rror,pcntl_si,procmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_signal_get_handler,pcntl_async_signals,php_uname,getmyuid,getmypid,passthru,leak,listen,diskfreespace,link,ignore_user_abord,shell_exec,dl,exec,system,highli
ght_file,source,show_source,fpaththru,virtual,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix_getppid,posix_getpwnam,posix_getpwuid,posix_getr
limit,posix_getsid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,proc_open,proc_close,proc_get_status,proc_nice,proc_terminate,popen,parse_ini_file,pclose,disk_
total_space,
Bug#999806: pygattlib: diff for NMU version 0~20201113-1.1
Control: tags 999806 + pending Dear maintainer, I've prepared an NMU for pygattlib (versioned as 0~20201113-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- diffstat for pygattlib-0~20201113 pygattlib-0~20201113 changelog |8 patches/multiple-boost-python.patch | 27 +++ patches/series |1 + 3 files changed, 36 insertions(+) diff -Nru pygattlib-0~20201113/debian/changelog pygattlib-0~20201113/debian/changelog --- pygattlib-0~20201113/debian/changelog 2020-12-23 09:44:47.0 +0100 +++ pygattlib-0~20201113/debian/changelog 2022-01-02 15:38:19.0 +0100 @@ -1,3 +1,11 @@ +pygattlib (0~20201113-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix misbuild with multiple supported Python3 versions. Closes: #999806 +Thanks to Steve Langasek for the patch. + + -- Mattia Rizzolo Sun, 02 Jan 2022 15:38:19 +0100 + pygattlib (0~20201113-1) unstable; urgency=medium * Initial Release. (Closes: #977950) diff -Nru pygattlib-0~20201113/debian/patches/multiple-boost-python.patch pygattlib-0~20201113/debian/patches/multiple-boost-python.patch --- pygattlib-0~20201113/debian/patches/multiple-boost-python.patch 1970-01-01 01:00:00.0 +0100 +++ pygattlib-0~20201113/debian/patches/multiple-boost-python.patch 2022-01-02 15:37:47.0 +0100 @@ -0,0 +1,27 @@ +Description: fix libboost detection with multiple python versions + pygattlib always links against the first libboost_python.so it finds. + When building for multiple python versions, this is wrong; it should link + against the one matching the version of python we're building for. +Author: Steve Langasek +Bug-Debian: https://bugs.debian.org/999806 +Last-Update: 2022-01-02 + +Index: pygattlib-0~20201113/setup.py +=== +--- pygattlib-0~20201113.orig/setup.py pygattlib-0~20201113/setup.py +@@ -11,12 +11,8 @@ + + + def get_boost_version(out=None): +-if out is None: +-out = subprocess.check_output( +-r"ldconfig -p | grep -E 'libboost_python.*\.so '", shell=True) +- +-ver = os.path.splitext(out.split()[0][3:])[0].decode() +-return ver ++return 'boost_python%s%s' \ ++% (sys.version_info.major, sys.version_info.minor) + + def tests(): + # case: python3-py3x.so diff -Nru pygattlib-0~20201113/debian/patches/series pygattlib-0~20201113/debian/patches/series --- pygattlib-0~20201113/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ pygattlib-0~20201113/debian/patches/series 2022-01-02 15:37:18.0 +0100 @@ -0,0 +1 @@ +multiple-boost-python.patch signature.asc Description: PGP signature
Processed: Re: [Pkg-privacy-maintainers] Bug#1001981: Bug#1001981: onioncircuits: Doesn't start: Permission denied: '/usr/local/lib/python3.9/dist-packages/usb-0.0.83.dev0.dist-info'
Processing commands for cont...@bugs.debian.org: > severity 1001981 normal Bug #1001981 [onioncircuits] onioncircuits: Doesn't start: Permission denied: '/usr/local/lib/python3.9/dist-packages/usb-0.0.83.dev0.dist-info' Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1001981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pygattlib: diff for NMU version 0~20201113-1.1
Processing control commands: > tags 999806 + pending Bug #999806 [pygattlib] pygattlib: Misbuild with multiple supported python versions Added tag(s) pending. -- 999806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001981: [Pkg-privacy-maintainers] Bug#1001981: Bug#1001981: onioncircuits: Doesn't start: Permission denied: '/usr/local/lib/python3.9/dist-packages/usb-0.0.83.dev0.dist-info'
severity 1001981 normal thanks FTR: The original reporter confirmed that removing the Python modules in /usr/local got onioncircuits to start again. So lowering severity as this is likely not a packaging bug breaking onioncircuits for everyone. S. On 23.12.21 12:58, Sascha Steinbiss wrote: > Hi Richard, > > thanks for your report. Let's see what I can do. > >> clicking then launcher results in no visible action. > > This is just in bullseye? Unfortunately I can't reproduce this, > onioncircuits opens fine for me. > >> Starting from shell >> results in this: >> >> rz@rz-debian:~$ onioncircuits > >> PermissionError: [Errno 13] Permission denied: >> '/usr/local/lib/python3.9/dist- >> packages/usb-0.0.83.dev0.dist-info' > > This is quite suspicious. There should no Python code installed by > Debian packages in /usr/local [1]. It looks like something installed > alongside the Debian-provided Python modules is interfering with > operation of the pycountry module, which is a dependency of onioncircuits. > Did you install any Python packages system-wide using pip or other means > other than Debian packaging, maybe even using sudo? This may leave files > around with permissions not including the rz user. > > Can you please try uninstalling these files in > /usr/local/lib/python3.9/dist-packages and try again? Thanks! > > Cheers > Sascha > > [1] See Policy 9.1.2: > https://www.debian.org/doc/debian-policy/ch-opersys.html#site-specific-programs > > ___ > Pkg-privacy-maintainers mailing list > pkg-privacy-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-privacy-maintainers >
Bug#1002219: [PATCH] t/eml.t: ignore newer Email::MIME behavior
Hello Eric,
On 12/30/21 20:17, Eric Wong wrote:
Uwe Kleine-König wrote:
Hello,
adding the Debian Perl Group to Cc, maybe they can help here.
(for context look at https://bugs.debian.org/1002219)
On 12/30/21 10:12, Uwe Kleine-König wrote:
I got a bug report against the public-inbox 1.6.1 package about a
failing test, see below for the whole output. I didn't have time yet to
look into it, so this is just a heads up to make you aware. If someone
has a hint what to do, this would be greatly appreciated. Maybe just
updating to 1.7 will help?
Best regards
Uwe
On 12/21/21 17:34, Lucas Nussbaum wrote:
# Failed test 'filename decoded'
# at t/eml.t line 407.
# got: '=?utf-8?q?vtpm-makefile.patch?='
# expected: 'vtpm-makefile.patch'
# Looks like you failed 1 test of 146.
t/eml.t ..
I can reproduce this problem with 1.6.1 checked out. I played a bit around
(suffering from my weak perl foo) and found that when I downgrade
libemail-mime-perl from 1.952-1 (i.e. Debian unstable's version) to 1.949-1
(i.e. Debian stable's version), this works.
The reproducer is:
$ perl -e 'use Email::MIME; print Email::MIME->new("Content-Type:
text/x-patch; name=\"=?utf-8?q?vtpm-fakefile.patch?=\"\nContent-Disposition:
attachment; filename=\"=?utf-8?q?vtpm-makefile.patch?=\"\n\n")->filename;'
which emits "vtpm-makefile.patch" with 1.949-1 (as public-inbox expects),.
but =?utf-8?q?vtpm-makefile.patch?= with 1.952-1.
So the key question is: Is the test correct and his is a regression in
libemail-mime-perl, or is the test wrong and we need to fix the test (and
PublicInbox::Eml)?
I thought I sent a fix to this; but I nuked the root FS on one of
my workstations on accident :< Still recovering...
Oh, good luck in restoring your precious data.
Thanks for your patch. I just uploaded public-inbox with this change to
fix the bug.
I still wonder if this is a regression in Email::MIME, or just a wrong
expectation. In the first case I'd open a bug against libemail-mime-perl.
Bisecting in https://github.com/rjbs/Email-MIME.git yields
https://github.com/rjbs/Email-MIME/commit/8a7cffd2b1091ff1a750d541a85e1813a6747b72
as breaking commit. So this looks like an intended change.
Best regards
Uwe
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1002995: ruby3.0: CVE-2021-41816 CVE-2021-41817 CVE-2021-41819
Source: ruby3.0 Version: 3.0.2-5 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for ruby3.0, they were fixed upstream in 3.0.3. CVE-2021-41816[0]: | Buffer Overrun in CGI.escape_html CVE-2021-41817[1]: | Date.parse in the date gem through 3.2.0 for Ruby allows ReDoS | (regular expression Denial of Service) via a long string. The fixed | versions are 3.2.1, 3.1.2, 3.0.2, and 2.0.1. CVE-2021-41819[2]: | CGI::Cookie.parse in Ruby through 2.6.8 mishandles security prefixes | in cookie names. This also affects the CGI gem through 0.3.0 for Ruby. 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-2021-41816 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41816 [1] https://security-tracker.debian.org/tracker/CVE-2021-41817 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41817 [2] https://security-tracker.debian.org/tracker/CVE-2021-41819 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41819 Regards, Salvatore
Bug#997748: libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23)
hi, On Sun, Oct 24, 2021 at 01:39:00PM +0200, Lucas Nussbaum wrote: > Source: libcomps > Version: 0.1.15-4 > Severity: serious [...] > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > Running Sphinx v4.2.0 > > > > Configuration error: > > There is a syntax error in your configuration file: Missing parentheses in > > call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? > > (conf.py, line 23) > > > > make[5]: *** [src/python/docs/CMakeFiles/pydocs.dir/build.make:122: pydocs] > > Error 2 It seems to me we can fix this bug by simply taking the patch from https://github.com/rpm-software-management/libcomps/commit/5eebd94a7ce855979eb014595256eee17ee6b359 Can someone confirm? I'd be happy to sponsor an upload again :) -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Dance like no one's watching. Encrypt like everyone is. signature.asc Description: PGP signature
Bug#1002340: marked as done (annexremote: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --test-nose returned exit code 13)
Your message dated Sun, 02 Jan 2022 13:48:29 +
with message-id
and subject line Bug#1002340: fixed in annexremote 1.6.0-1
has caused the Debian Bug report #1002340,
regarding annexremote: FTBFS: dh_auto_test: error: pybuild --test --test-nose
-i python{version} -p "3.10 3.9" --test-nose returned exit code 13
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.)
--
1002340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: annexremote
Version: 1.5.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --test-nose
> pybuild --test --test-nose -i python{version} -p "3.10 3.9" --test-nose
> I: pybuild pybuild:286: cp -r /<>/tests
> /<>/.pybuild/cpython3_3.10_annexremote/build
> I: pybuild base:237: cd
> /<>/.pybuild/cpython3_3.10_annexremote/build; python3.10 -m nose
> -v
> TestListenNotLinked (test_AnnexRemoteSetup.SetupTestCase) ... ok
> TestCheckpresentFailure
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckpresentSuccess
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckpresentUnknown
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlContents
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlContentsTrue
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlContentsUnknownSize
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlContentsWithoutFilename
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlContentsWithoutSizeAndFilename
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlFailure
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlFailureByException
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlMultiFiveUrls
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlMultiOneItemWithUrl
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlMultiSpaceInFilename
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlMultiSpaceInUrl
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlMultiTabInUrlAndFilename
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestCheckurlMultiTwoUrls
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestClaimurlFailure
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestClaimurlSuccess
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestError (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestExtensions (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ...
> ok
> TestGetavailabilityGlobal
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestGetavailabilityInvalid
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestGetavailabilityLocal
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestGetcost (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestGetcostInvalid (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestGetinfo (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestGetinfoNone (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestInitremoteFailure
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestInitremoteSuccess
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestListconfigs (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestListconfigsSpaceInName
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
> TestPrepareFailure (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestPrepareSuccess (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestRemoveFailure (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestRemoveSuccess (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages)
> ... ok
> TestTransferRetrieveFailure
> (test_GitAnnexRequestMessages.TestGitAnnexRequestMessages) ... ok
>
Bug#1002961: [Pkg-pascal-devel] Bug#1002961: src:castle-game-engine: fails to migrate to testing for too long: FTBFS on armel
The issue is that there seem to be a bug in the compiler. However, I'm not able to understand what kind of issue and cloud not produce a small code that triggers it. Moreover, it seems that the bug itself is triggered only when running the full battery of tests. Then the failing test starts to fail. If the test is ran alone (after a machine reboot, or after a while) then it will succeed, but it one runs it after running the full test suite then it will fail systematically. No clue how to go forward and no enough information to open an upstream compiler bug. Moreover CGE upstream think we should abandon armel (and other non widely used architectures) as a target for CGE, but I think myself it is a good test for the compiler and tend to think we should keep it. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#1002927: marked as done (dgit test casds use abolished compat versions)
Your message dated Sun, 02 Jan 2022 12:34:45 + with message-id and subject line Bug#1002927: fixed in dgit 9.15 has caused the Debian Bug report #1002927, regarding dgit test casds use abolished compat versions 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.) -- 1002927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dgit Control: found -1 dgit/9.14 Control: affects -1 src:dehbelper Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update dgit's autopkgtests contain some example packages which use debhelper compat level(s) which are being abolished. This was not detected during the MBF campaign for obvious reasons. Currently this is causing a test failure which is preventing the new debhelper (which is the version which actually removes support for compat 5) from migrating. I will update my tests. This should be straightforward and I expect to be able to do it in the next few days. Apologies for the inconvenience. Ian. -- application/pgp-signature: signature.asc, OpenPGP digit [save] -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter. --- End Message --- --- Begin Message --- Source: dgit Source-Version: 9.15 Done: Ian Jackson We believe that the bug you reported is fixed in the latest version of dgit, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson (supplier of updated dgit 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, 02 Jan 2022 12:20:23 + Source: dgit Architecture: source Version: 9.15 Distribution: unstable Urgency: medium Maintainer: Ian Jackson Changed-By: Ian Jackson Closes: 1002927 Changes: dgit (9.15) unstable; urgency=medium . * dgit: pseudomerge_version_check: Check for unfinalised changelog entry. * tests: Set FILTER_BRANCH_SQUELCH_WARNING=1 * tests: Use t-debchange in some places instead of dch * tests: Update all using tests/update-db-compat. Closes: #1002927. Checksums-Sha1: de86aef27162da2fd511a26d4da1e48a91e6b216 1846 dgit_9.15.dsc befe9a738b52fda6fe38a4d357ba5909d2f7774f 667899 dgit_9.15.tar.gz Checksums-Sha256: 9b07c61c832074b9ba7420895a24bf6890e4e5f1988f07b71d03753d05ee6098 1846 dgit_9.15.dsc 9b154483bca85e3a83ed675b8f4dbdcb8a32a02a3baf8465814967ff225c1ed4 667899 dgit_9.15.tar.gz Files: b3307d5566824a77fdffd06f57396d5e 1846 devel optional dgit_9.15.dsc 8f130694f694baf200566e340cd0129e 667899 devel optional dgit_9.15.tar.gz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmHRmQUACgkQ4+M5I0i1 DTnZ0gf/XW8bgbTmdr42pCmceBgu+VJNGEGk3h8XQbAQ+bCGJlu1YWW+uo6nearF A81GSQwwH0ckwQgQYxoz38SgSn1Bq1CuL01eKmVzOdaYY33/Nfef/ZaxNxHxRbr2 GElaf7OasadHn8BR0Tu3r4xkjIkvkex80ctLXHxC0++n+1e+0EPRcaHn2fFhjA3U 1/qqTiUywZdSfF0cjBcXmuzO/5QIBYMIH/REPzEgl3/yaRvTKHDT+VKqocrrbIZN 0IVzG1RkCWwyNJO39abthogux615p+fM/5KPUX2xVGoiPgJnwDOnPzXDXu12grCa kwwE7QqMmCMrJf0JUq5vOVQgX/aG4w== =QSIJ -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1002376: python-aiosqlite: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
Processing control commands: > affects 1001591 + src:python-aiosqlite Bug #1001591 [python3-mistune] drops attributes used by reverse dependencies Added indication that 1001591 affects src:python-aiosqlite -- 1001591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001591 1002376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002376: python-aiosqlite: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
Control: affects 1001591 + src:python-aiosqlite This looks like the mistune v2 incompatibility with m2r. Upstream switched from m2r to sphinx-mdinclude (a m2r fork compatible to mistune v2) in git.
Bug#997029: marked as done (pysph: FTBFS in testing and unstable)
Your message dated Sun, 02 Jan 2022 11:03:49 +
with message-id
and subject line Bug#997029: fixed in pysph 1.0~b0~20191115.gite3d5e10-6
has caused the Debian Bug report #997029,
regarding pysph: FTBFS in testing and unstable
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.)
--
997029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysph
Version: 1.0~b0~20191115.gite3d5e10-5
Severity: serious
Tags: ftbfs
Hi Maintainer
As can be seen in reproducible builds [1], pysph sometimes FTBS in
both testing and unstable. I've copied what I hope is the relevant
part of the log below.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/pysph.html
=== FAILURES ===
_ MPIReduceArrayTestCase.test_parallel_reduce __
self =
@mark.parallel
def test_parallel_reduce(self):
args = ['--directory=%s' % self.root]
> run_parallel_script.run(
filename='simple_reduction.py', args=args, nprocs=nprocs, path=path
)
pysph/parallel/tests/test_parallel.py:101:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
filename = 'simple_reduction.py', args = ['--directory=/tmp/tmpr8h_5ft1']
nprocs = 2, timeout = 30.0
path =
'/build/1st/pysph-1.0~b0~20191115.gite3d5e10/.pybuild/cpython3_3.9/build/pysph/parallel/tests'
def run(filename, args=None, nprocs=2, timeout=30.0, path=None):
"""Run a python script with MPI or in serial (if nprocs=1).
Kill process
if it takes longer than the specified timeout.
Parameters:
---
filename - filename of python script to run under mpi.
args - List of arguments to pass to script.
nprocs - number of processes to run (1 => serial non-mpi run).
timeout - time in seconds to wait for the script to finish running,
else raise a RuntimeError exception.
path - the path under which the script is located
Defaults to the location of this file (__file__), not curdir.
"""
if args is None:
args = []
file_path = abspath(join(path, filename))
cmd = [sys.executable, file_path] + args
if nprocs > 1:
cmd = ['mpiexec', '-n', str(nprocs)] + cmd
print('running test:', cmd)
process = Popen(cmd, stdout=PIPE, stderr=PIPE)
timer = Timer(timeout, kill_process, [process])
timer.start()
out, err = process.communicate()
timer.cancel()
retcode = process.returncode
if retcode:
msg = 'test ' + filename + ' failed with returncode ' + str(retcode)
print(out.decode('utf-8'))
print(err.decode('utf-8'))
print('#'*80)
print(msg)
print('#'*80)
> raise RuntimeError(msg)
E RuntimeError: test simple_reduction.py failed with returncode -9
pysph/tools/run_parallel_script.py:54: RuntimeError
--- End Message ---
--- Begin Message ---
Source: pysph
Source-Version: 1.0~b0~20191115.gite3d5e10-6
Done: Antonio Valentino
We believe that the bug you reported is fixed in the latest version of
pysph, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Valentino (supplier of updated pysph
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, 02 Jan 2022 09:54:54 +
Source: pysph
Architecture: source
Version: 1.0~b0~20191115.gite3d5e10-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Antonio Valentino
Closes: 997029
Changes:
pysph (1.0~b0~20191115.gite3d5e10-6) unstable; urgency=medium
.
* Update watch file to use tags instead of releases.
* Disable broken test (see
https://github.com/pypr/pysph/issues/326).
Closes: #997029.
Checksums-Sha1:
6739e348f57b1cf4dfd71ef926ea81fbb4a5642c 2638
pysph_1.0~b0~20191115.gite3d5e10-6.dsc
Bug#1002047: marked as done (nslcd silently modifies /etc/nslcd.conf on upgrade, breaking authentication)
Your message dated Sun, 02 Jan 2022 11:03:34 +
with message-id
and subject line Bug#1002047: fixed in nss-pam-ldapd 0.9.12-2
has caused the Debian Bug report #1002047,
regarding nslcd silently modifies /etc/nslcd.conf on upgrade, breaking
authentication
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.)
--
1002047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nslcd
Version: 0.9.11-1
Severity: serious
Justification: Policy 10.7.3
X-Debbugs-Cc: debian...@burzmali.com
Dear Maintainer,
The postinst script of nslcd silently modifies the configuration file
/etc/nslcd.conf on package upgrades. It rewrites or adds settings
without notification to the administrator.
In my case, the script appended "base dc=olddomain,dc=example,dc=org" during
the dist-upgrade from Buster to Bullseye. After reboot, remote and local
login to the server was broken except for root due to this change.
("pam_ldap(login:account): LDAP authorisation check failed;
user=myuser; err=Permission denied").
The postinst script reused a previous domain name that had been manually
overwritten in the configuration file after the initial installation. It
also failed to consider the more precise "bases" that were already
configured:
base passwd ou=people,dc=newdomain,dc=example,dc=org
base shadow ou=people,dc=newdomain,dc=example,dc=org
base group ou=groups,dc=newdomain,dc=example,dc=org
In a related manner, in #819961, the script tried (and failed) to
rewrite the bindpw setting.
I would have expected the script to not modify the existing
configuration or at least to warn me it had been modified.
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nslcd depends on:
ii adduser3.118
ii ca-certificates20210119
ii debconf [debconf-2.0] 1.5.77
ii libc6 2.31-13+deb11u2
ii libgssapi-krb5-2 1.18.3-6+deb11u1
ii libldap-2.4-2 2.4.57+dfsg-3
ii lsb-base 11.1.0
Versions of packages nslcd recommends:
ii bind9-host [host] 1:9.16.22-1~deb11u1
ii ldap-utils 2.4.57+dfsg-3
ii libnss-ldapd [libnss-ldap] 0.9.11-1
ii libpam-ldapd [libpam-ldap] 0.9.11-1
ii nscd2.31-13+deb11u2
ii nslcd-utils 0.9.11-1
Versions of packages nslcd suggests:
pn kstart
-- debconf information excluded
-- /etc/nslcd.conf before upgrade
# /etc/nslcd.conf
# nslcd configuration file. See nslcd.conf(5)
# for details.
# Daemon configuration
uid nslcd
gid nslcd
# LDAP server
uri ldaps://ldap.example.org
ldap_version 3
tls_reqcert demand
tls_cacertfile /etc/ssl/certs/ca-certificates.crt
binddn cn=servername,ou=servers,dc=newdomain,dc=example,dc=org
bindpw *removed*
# Mapping
scope children
base passwd ou=people,dc=newdomain,dc=example,dc=org
base shadow ou=people,dc=newdomain,dc=example,dc=org
base group ou=groups,dc=newdomain,dc=example,dc=org
filter passwd (objectClass=posixAccount)
filter shadow (objectClass=posixAccount)
filter group (gidNumber=*)
map passwd gecos "${cn} (LDAP)"
map passwd loginShell "${loginShell:-/bin/bash}"
map shadow userPassword userPassword
map shadow shadowExpire "${isDisabled:+1}"
map group userPassword "*"
# Local users
nss_initgroups_ignoreusers ALLLOCAL
nss_min_uid 2
# Authorization
pam_authc_ppolicy yes
pam_authc_search BASE
pam_authz_search
(&(objectClass=posixAccount)(uid=$username)(!(isDisabled=*))(!(pwdAccountLockedTime=*)))
--
--- End Message ---
--- Begin Message ---
Source: nss-pam-ldapd
Source-Version: 0.9.12-2
Done: Arthur de Jong
We believe that the bug you reported is fixed in the latest version of
nss-pam-ldapd, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Arthur de Jong (supplier of updated nss-pam-ldapd package)
(This message was generated automatically at their request; if
Bug#1002989: nnpack: FTBFS undefined reference to `nnp_shdotxf[1-8]_avx2'
Source: nnpack Version: 0.0~git20200414.57616b9-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, nnpack recently started to FTBFS, probably due to some updated toolchain packages: [ 45%] Linking CXX executable convolution-inference-alexnet-test /usr/bin/cmake -E cmake_link_script CMakeFiles/convolution-inference-alexnet-test.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/build/nnpack-0.0~git20200414.57616b9=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/convolution-inference-alexnet-test.dir/test/co nvolution-inference/alexnet.cc.o -o convolution-inference-alexnet-test libnnpack.a libnnpack_reference_layers.a -lcpuinfo -lpthread -lpthreadpool /usr/lib/x86_64-linux-gnu/libgtest.a -lpthread /usr/bin/ld: libnnpack.a(init.c.o):./obj-x86_64-linux-gnu/./src/init.c:119: undefined reference to `nnp_shdotxf1__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x8): undefined reference to `nnp_shdotxf2__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x10): undefined reference to `nnp_shdotxf3__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x18): undefined reference to `nnp_shdotxf4__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x20): undefined reference to `nnp_shdotxf5__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x28): undefined reference to `nnp_shdotxf6__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x30): undefined reference to `nnp_shdotxf7__avx2' /usr/bin/ld: libnnpack.a(init.c.o):(.data.rel.ro+0x38): undefined reference to `nnp_shdotxf8__avx2' collect2: error: ld returned 1 exit status make[3]: *** [CMakeFiles/convolution-inference-alexnet-test.dir/build.make:103: convolution-inference-alexnet-test] Error 1 In case it does matter, the CPU is an i7-9800X, i.e. the native target would be skylake-avx512. Andreas nnpack_0.0~git20200414.57616b9-1.log.gz Description: application/gzip
Bug#997216: marked as done (libnice: FTBFS: /<>/obj-x86_64-linux-gnu/meson-private/tmp2jrl2k6t/testfile.c:4:12: error: #error "Header 'net/in.h' could not be found")
Your message dated Sun, 02 Jan 2022 10:03:48 + with message-id and subject line Bug#997216: fixed in libnice 0.1.18-2 has caused the Debian Bug report #997216, regarding libnice: FTBFS: /<>/obj-x86_64-linux-gnu/meson-private/tmp2jrl2k6t/testfile.c:4:12: error: #error "Header 'net/in.h' could not be found" 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.) -- 997216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnice Version: 0.1.18-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Dgupnp=enabled \ > -Dgstreamer=enabled \ > -Dintrospection=enabled \ >-Dgtk_doc=enabled > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgupnp=enabled > -Dgstreamer=enabled -Dintrospection=enabled -Dgtk_doc=enabled > The Meson build system > Version: 0.59.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: libnice > Project version: 0.1.18 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Checking for function "clock_gettime" : YES > Has header "arpa/inet.h" : YES > Has header "net/in.h" : NO > Has header "netdb.h" : YES > Has header "ifaddrs.h" : YES > Has header "unistd.h" : YES > Checking for function "poll" : YES > Checking for function "getifaddrs" : YES > Compiler for C supports arguments -fno-strict-aliasing: YES > Message: warning level: 1 > Message: werror enabled: false > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gthread-2.0 found: YES 2.70.0 > Message: Crypto library requested: auto > Run-time dependency gnutls found: YES 3.7.2 > Run-time dependency gstreamer-base-1.0 found: YES 1.18.5 > Run-time dependency gupnp-igd-1.0 found: YES 1.2.0 > Library m found: YES > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Program gen-def.py found: YES (/usr/bin/python3 > /<>/nice/gen-def.py) > Program gen-map.py found: YES (/usr/bin/python3 > /<>/nice/gen-map.py) > Compiler for C supports link arguments > -Wl,--version-script,/<>/nice/libnice.ver: YES > Run-time dependency gobject-introspection-1.0 found: YES 1.70.0 > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) > Dependency gtk-doc found: NO found 1.33.1 but need: '<1.30' > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency gtk-doc found: NO (tried pkgconfig and cmake) > Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) > Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj) > Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb) > Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml) > Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref) > Program gtkdoc-check found: YES (/usr/bin/gtkdoc-check) > Program dot found: NO > > ../docs/reference/libnice/meson.build:70:0: ERROR: Program 'dot' not found > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-10-23T07:36:38.251606 > Main binary: /usr/bin/python3 > Build Options: -Dgupnp=enabled -Dgstreamer=enabled -Dintrospection=enabled > -Dgtk_doc=enabled -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.59.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: libnice > Project version: 0.1.18 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o
Bug#1001727: marked as done (python-aiohttp breaks postfix-mta-sts-resolver autopkgtest: Job for postfix-mta-sts-resolver.service failed)
Your message dated Sun, 2 Jan 2022 10:46:10 +0100 with message-id and subject line Re: Bug#1001727: python-aiohttp breaks postfix-mta-sts-resolver autopkgtest: Job for postfix-mta-sts-resolver.service failed has caused the Debian Bug report #1001727, regarding python-aiohttp breaks postfix-mta-sts-resolver autopkgtest: Job for postfix-mta-sts-resolver.service failed 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.) -- 1001727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiohttp, postfix-mta-sts-resolver Control: found -1 python-aiohttp/3.8.1-3 Control: found -1 postfix-mta-sts-resolver/1.0.0-4 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of python-aiohttp the autopkgtest of postfix-mta-sts-resolver fails in testing when that autopkgtest is run with the binary packages of python-aiohttp from unstable. It passes when run with only packages from testing. In tabular form: passfail python-aiohttp from testing3.8.1-3 postfix-mta-sts-resolver from testing1.0.0-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python-aiohttp to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-aiohttp https://ci.debian.net/data/autopkgtest/testing/amd64/p/postfix-mta-sts-resolver/17553994/log.gz Updating certificates in /etc/ssl/certs... 1 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Job for postfix-mta-sts-resolver.service failed because the control process exited with error code. See "systemctl status postfix-mta-sts-resolver.service" and "journalctl -xeu postfix-mta-sts-resolver.service" for details. Traceback (most recent call last): File "/tmp/autopkgtest-lxc.e660v08n/downtmp/build.EcE/src/debian/tests/run", line 75, in main() File "/tmp/autopkgtest-lxc.e660v08n/downtmp/build.EcE/src/debian/tests/run", line 62, in main set_up() File "/tmp/autopkgtest-lxc.e660v08n/downtmp/build.EcE/src/debian/tests/run", line 11, in set_up proc.check_returncode() File "/usr/lib/python3.9/subprocess.py", line 460, in check_returncode raise CalledProcessError(self.returncode, self.args, self.stdout, subprocess.CalledProcessError: Command '['tests/install.debian.sh']' returned non-zero exit status 1. autopkgtest [04:02:53]: test run OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Control: affects 1001642 + src:postfix-mta-sts-resolver Hi, I was unable to reproduce the issue, I'd assume it was fixed in python3-aiohttp: https://bugs.debian.org/1001642 Kind regards, Benjamin--- End Message ---
Processed: Reopen #1000273
Processing commands for cont...@bugs.debian.org:
> reopen 1000273
Bug #1000273 {Done: Antonio Valentino }
[src:satpy] satpy: autopkgtest regression on armhf and i386: ArrayMemoryError:
Unable to allocate 73.4 MiB for an array with shape (14, 2030, 1354) and data
type uint16
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions satpy/0.33.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002745: marked as done (minetest-mod-protector: package contains wrong mod)
Your message dated Sun, 02 Jan 2022 09:33:43 + with message-id and subject line Bug#1002745: fixed in minetest-mod-protector 20210923+reallyprotector-1 has caused the Debian Bug report #1002745, regarding minetest-mod-protector: package contains wrong mod 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.) -- 1002745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: minetest-mod-protector Version: 20210923-2 Severity: grave Justification: renders package unusable Something went completely wrong with the latest version of this package. It doesn't contain the mod "protector" but the mod "mobs_redo". -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages minetest-mod-protector depends on: ii minetest 5.4.1+repack-2 minetest-mod-protector recommends no packages. minetest-mod-protector suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: minetest-mod-protector Source-Version: 20210923+reallyprotector-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of minetest-mod-protector, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated minetest-mod-protector 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, 02 Jan 2022 10:18:19 +0100 Source: minetest-mod-protector Architecture: source Version: 20210923+reallyprotector-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Julien Puydt Closes: 1002745 Changes: minetest-mod-protector (20210923+reallyprotector-1) unstable; urgency=medium . * Import correct tarball (Closes: #1002745). Checksums-Sha1: ea1b8e3129d1c0a72d554cb0cfacd4911d09598c 2213 minetest-mod-protector_20210923+reallyprotector-1.dsc 8629507eb23290bcb346d0a20d553b03f7c946f9 43121 minetest-mod-protector_20210923+reallyprotector.orig.tar.gz bcf317e6845b71373033a3dfc7610ca1834f36cd 8740 minetest-mod-protector_20210923+reallyprotector-1.debian.tar.xz b22e37a995d18affc5682e9e0349c66605edb9c7 6543 minetest-mod-protector_20210923+reallyprotector-1_source.buildinfo Checksums-Sha256: 4fe2651ac4b71619389775ec29276ef55bccf7a55244efa14677c43330f6caf9 2213 minetest-mod-protector_20210923+reallyprotector-1.dsc de6bb6e7301da47c16535bc339f633b1654edafe5ac3ff7dc2ed5faca1555f4e 43121 minetest-mod-protector_20210923+reallyprotector.orig.tar.gz 9e04abf2014eb9de040c02039220fcc4c81f9573d5f1b083da72915fdaf2dcdf 8740 minetest-mod-protector_20210923+reallyprotector-1.debian.tar.xz 7bde4c27ab9057af30d3a852b5285cdb9e3ce7509378e19f4cea220d86c61176 6543 minetest-mod-protector_20210923+reallyprotector-1_source.buildinfo Files: cd9722f04c325fef5ca39ed85cc3e7fc 2213 games optional minetest-mod-protector_20210923+reallyprotector-1.dsc d73f418263a09ea5667cb101f078c41a 43121 games optional minetest-mod-protector_20210923+reallyprotector.orig.tar.gz 311a8d7d78ebc0bd9e9cbd80c060e8d3 8740 games optional minetest-mod-protector_20210923+reallyprotector-1.debian.tar.xz ccb7b26dd3e3bfb595d89ba8591fccab 6543 games optional minetest-mod-protector_20210923+reallyprotector-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmHRbf0SHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRjekQAJEDCWKa3wokYJKTqhLQSrPjH1s4x+aN EiJiva3yxzRzKsk4G/yhucN4sQ1kBSIYt1B0H3YK2Y1+aRgGw80HGrHy6FyNRHQs Oopvs/JX9luFTEAkWa5gnsk4gzE0CkhXLoYW+bkMzr+L9NZ7PMEnkPo7Tf1HPxhG +La4Lzmc1TiukH02Pmn/O0B+CizU7t4XkxE93QfLiR01BpQWzF9w5BAWxZHeE8Tq
Processed: Bug#1002745 marked as pending in minetest-mod-protector
Processing control commands: > tag -1 pending Bug #1002745 [minetest-mod-protector] minetest-mod-protector: package contains wrong mod Added tag(s) pending. -- 1002745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002745: marked as pending in minetest-mod-protector
Control: tag -1 pending Hello, Bug #1002745 in minetest-mod-protector 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/games-team/minetest-mod-protector/-/commit/2e4b937f0053889710879f3bfd72a80b7ac1cf2a Import correct upstream tarball (Closes: #1002745) (this message was generated automatically) -- Greetings https://bugs.debian.org/1002745
Bug#1001433: marked as done (scitokens-cpp: FTBFS with openssl 3)
Your message dated Sun, 02 Jan 2022 09:19:06 + with message-id and subject line Bug#1001433: fixed in scitokens-cpp 0.6.2-2 has caused the Debian Bug report #1001433, regarding scitokens-cpp: FTBFS with openssl 3 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.) -- 1001433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: scitokens-cpp Version: 0.6.2-1 Severity: serious Tags: patch experimental Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Hi Mattias, In Ubuntu, scitokens-cpp is failing to build from source because we have updated to update to openssl 3, and scitokens-cpp uses some functions which are now deprecated: [...] /usr/bin/c++ -DSciTokens_EXPORTS -I/<> -I/<>/vendor/jwt-cpp/include -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -std=c++11 -fPIC -MD -MT CMakeFiles/SciTokens.dir/src/scitokens_cache.cpp.o -MF CMakeFiles/SciTokens.dir/src/scitokens_cache.cpp.o.d -o CMakeFiles/SciTokens.dir/src/scitokens_cache.cpp.o -c /<>/src/scitokens_cache.cpp In file included from /<>/src/scitokens_internal.h:6, from /<>/src/scitokens_cache.cpp:17: /<>/vendor/jwt-cpp/include/jwt-cpp/jwt.h: In constructor ‘jwt::algorithm::ecdsa::ecdsa(const string&, const string&, const string&, const string&, const EVP_MD* (*)(), const string&, size_t)’: /<>/vendor/jwt-cpp/include/jwt-cpp/jwt.h:360:74: error: ‘EC_KEY* PEM_read_bio_EC_PUBKEY(BIO*, EC_KEY**, int (*)(char*, int, int, void*), void*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 360 | pkey.reset(PEM_read_bio_EC_PUBKEY(pubkey_bio.get(), nullptr, nullptr, (void*)public_key_password.c_str()), EC_KEY_free); | ~~^~~~ In file included from /<>/vendor/jwt-cpp/include/jwt-cpp/jwt.h:11, from /<>/src/scitokens_internal.h:6, from /<>/src/scitokens_cache.cpp:17: /usr/include/openssl/pem.h:463:1: note: declared here 463 | DECLARE_PEM_rw_attr(OSSL_DEPRECATEDIN_3_0, EC_PUBKEY, EC_KEY) | ^~~ [...] (https://launchpad.net/ubuntu/+source/scitokens-cpp/0.6.2-1build1/+build/22604628) OpenSSL 3 is currently only in experimental in Debian, but is expected to be the version shipped in the next release of Debian. In Ubuntu, I've applied the following patch to let scitokens-cpp build by ignoring the deprecation warnings. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru scitokens-cpp-0.6.2/debian/rules scitokens-cpp-0.6.2/debian/rules --- scitokens-cpp-0.6.2/debian/rules2021-08-25 01:36:24.0 -0700 +++ scitokens-cpp-0.6.2/debian/rules2021-12-09 13:11:57.0 -0800 @@ -1,6 +1,8 @@ #!/usr/bin/make -f # -*- makefile -*- +export DEB_CFLAGS_MAINT_APPEND = -Wno-error=deprecated-declarations + %: dh $@ --- End Message --- --- Begin Message --- Source: scitokens-cpp Source-Version: 0.6.2-2 Done: Mattias Ellert We believe that the bug you reported is fixed in the latest version of scitokens-cpp, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert (supplier of updated scitokens-cpp 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, 02 Jan 2022 09:25:41 +0100 Source: scitokens-cpp Architecture: source Version: 0.6.2-2 Distribution: unstable Urgency: medium Maintainer: Mattias Ellert Changed-By: Mattias Ellert Closes: 1001433 Changes: scitokens-cpp (0.6.2-2)
Processed: tagging 1002412, tagging 1002110
Processing commands for cont...@bugs.debian.org:
> tags 1002412 - sid bookworm
Bug #1002412 {Done: Fabio Fantoni } [src:cinnamon]
cinnamon: FTBFS: ../src/st/meson.build:204:0: ERROR: "install_dir" must be
specified when installing a target
Removed tag(s) sid and bookworm.
> tags 1002110 - sid bookworm
Bug #1002110 {Done: Fabio Fantoni } [src:cjs] cjs:
FTBFS: collect2: error: ld returned 1 exit status
Removed tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002110
1002412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: annexremote: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --test-nose returned exit code 13
Processing control commands:
> tags -1 upstream
Bug #1002340 [src:annexremote] annexremote: FTBFS: dh_auto_test: error: pybuild
--test --test-nose -i python{version} -p "3.10 3.9" --test-nose returned exit
code 13
Added tag(s) upstream.
> forwarded -1 https://github.com/Lykos153/AnnexRemote/issues/33
Bug #1002340 [src:annexremote] annexremote: FTBFS: dh_auto_test: error: pybuild
--test --test-nose -i python{version} -p "3.10 3.9" --test-nose returned exit
code 13
Set Bug forwarded-to-address to
'https://github.com/Lykos153/AnnexRemote/issues/33'.
--
1002340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002340: annexremote: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --test-nose returned exit code 13
Control: tags -1 upstream Control: forwarded -1 https://github.com/Lykos153/AnnexRemote/issues/33 Hi, I've upgraded Git to latest upstream version (1.6.0) but the issue persists here and thus was reportet upstream. Kind regards Andreas. -- http://fam-tille.de
Bug#1001355: marked as done (voms: FTBFS with openssl 3)
Your message dated Sun, 02 Jan 2022 09:04:00 +
with message-id
and subject line Bug#1001355: fixed in voms 2.1.0~rc2-2
has caused the Debian Bug report #1001355,
regarding voms: FTBFS with openssl 3
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.)
--
1001355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: voms
Version: 2.1.0~rc2-1
Severity: serious
Tags: patch experimental
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Hi Mattias,
In Ubuntu, voms is failing to build from source because Ubuntu has moved to
OpenSSL 3, and voms is incompatible:
[...]
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src/autogen -Wdate-time
-D_FORTIFY_SOURCE=2 -I ../../src/include -g -O2
"-ffile-prefix-map=/<>=." -flto=auto -ffat-lto-objects
-fstack-protector-strong -Wformat -Werror=format-security -c proxypolicy.c
-fPIC -DPIC -o .libs/libssl_utils_nog_la-proxypolicy.o
In file included from proxypolicy.c:20:
proxypolicy.c:88:29: error: conflicting types for ‘PROXY_POLICY_dup’; have
‘PROXY_POLICY *(const PROXY_POLICY *)’ {aka ‘struct PROXY_POLICY_st *(const
struct PROXY_POLICY_st *)’}
88 | IMPLEMENT_ASN1_DUP_FUNCTION(PROXY_POLICY);
| ^~~~
In file included from proxypolicy.c:24:
../../src/include/proxypolicy.h:81:17: note: previous declaration of
‘PROXY_POLICY_dup’ with type ‘PROXY_POLICY *(PROXY_POLICY *)’ {aka ‘struct
PROXY_POLICY_st *(struct PROXY_POLICY_st *)’}
81 | PROXY_POLICY* PROXY_POLICY_dup(PROXY_POLICY* policy);
| ^~~~
[...]
(https://launchpad.net/ubuntu/+source/voms/2.1.0~rc2-1build2/+build/22467653)
This can be fixed with the attached one-liner fix, which I have uploaded to
Ubuntu. Please consider applying it in Debian as well.
OpenSSL 3 is currently in experimental, and expected to be the version of
OpenSSL shipped in the next release of Debian.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru voms-2.1.0~rc2/debian/patches/openssl3.patch
voms-2.1.0~rc2/debian/patches/openssl3.patch
--- voms-2.1.0~rc2/debian/patches/openssl3.patch1969-12-31
16:00:00.0 -0800
+++ voms-2.1.0~rc2/debian/patches/openssl3.patch2021-12-08
15:17:42.0 -0800
@@ -0,0 +1,18 @@
+Description: Compatibility with OpenSSL 3
+Author: Steve Langasek
+Last-Update: 2021-12-08
+Forwarded: no
+
+Index: voms-2.1.0~rc2/src/include/proxypolicy.h
+===
+--- voms-2.1.0~rc2.orig/src/include/proxypolicy.h
voms-2.1.0~rc2/src/include/proxypolicy.h
+@@ -78,8 +78,6 @@
+ , unsigned char * policy
+ , int length);
+
+- PROXY_POLICY* PROXY_POLICY_dup(PROXY_POLICY* policy);
+-
+ #ifdef __cplusplus
+ }
+ #endif
diff -Nru voms-2.1.0~rc2/debian/patches/series
voms-2.1.0~rc2/debian/patches/series
--- voms-2.1.0~rc2/debian/patches/series2021-08-24 10:29:24.0
-0700
+++ voms-2.1.0~rc2/debian/patches/series2021-12-08 15:15:18.0
-0800
@@ -17,3 +17,4 @@
# Change default proxy cert key length to 2048 bits
# https://github.com/italiangrid/voms/pull/75
voms-change-default-proxy-cert-key-length-to-2048-bits.patch
+openssl3.patch
--- End Message ---
--- Begin Message ---
Source: voms
Source-Version: 2.1.0~rc2-2
Done: Mattias Ellert
We believe that the bug you reported is fixed in the latest version of
voms, 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 1001...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mattias Ellert (supplier of updated voms 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, 02 Jan 2022 08:21:28 +0100
Source: voms
Architecture: source
Version: 2.1.0~rc2-2
Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive
Package: libguestfs-tools Version: 1:1.46.2-1 Severity: serious Hello, It looks like libguestfs-tools version 1:1.46.2-1 in depending on guestfs-tools that is not in the archive making the package uninstalable guestfs-tools is currently stuck in the new queue Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
