Bug#1021833: marked as done (nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1))
Your message dated Sat, 22 Oct 2022 10:26:26 +0300 with message-id and subject line Re: Bug#1021833: nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1) has caused the Debian Bug report #1021833, regarding nbdkit: FTBFS: FAIL test-partitioning3.sh (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.) -- 1021833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nbdkit Version: 1.32.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nbdkit&arch=amd64&ver=1.32.3-1&stamp=1665831409&raw=0 Testsuite summary for nbdkit 1.32.3 # TOTAL: 292 # PASS: 273 # SKIP: 18 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See tests/test-suite.log make[5]: *** [Makefile:4380: test-suite.log] Error 1 -- Sebastian Ramacher --- End Message --- --- Begin Message --- On Sat, Oct 15, 2022 at 08:16:03PM +0200, Hilko Bengen wrote: > control: block -1 by 1020446 > > The failing test is due to sgdisk misbehaving as documented in #1020446. > Once the patch for #1020446 is applied, rebuilding the package should > fix things. This got fixed, and nbdkit built now. > Cheers, > -Hilko cu Adrian--- End Message ---
Bug#1021858: marked as done (drf-yasg-nonfree: FTBFS: AttributeError: module 'rest_framework.serializers' has no attribute 'NullBooleanField')
Your message dated Sat, 22 Oct 2022 07:34:03 +
with message-id
and subject line Bug#1021858: fixed in drf-yasg-nonfree 1.21.4-1
has caused the Debian Bug report #1021858,
regarding drf-yasg-nonfree: FTBFS: AttributeError: module
'rest_framework.serializers' has no attribute 'NullBooleanField'
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.)
--
1021858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drf-yasg-nonfree
Version: 1.21.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
drf-yasg-nonfree recently started to FTBFS:
debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/drf-yasg-nonfree-1.21.3'
PYTHONPATH=. python3 -m sphinx -b html -N docs/
/build/drf-yasg-nonfree-1.21.3/debian/python-drf-yasg-nonfree-doc/usr/share/doc/python-drf-yasg-nonfree-doc/html
Running Sphinx v4.5.0
Configuration error:
There is a programmable error in your configuration file:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/config.py", line 332, in
eval_config_file
exec(code, namespace)
File "/build/drf-yasg-nonfree-1.21.3/docs/conf.py", line 228, in
drf_yasg.views.SchemaView = drf_yasg.views.get_schema_view(None)
File "/build/drf-yasg-nonfree-1.21.3/src/drf_yasg/views.py", line 67, in
get_schema_view
_generator_class = generator_class or
swagger_settings.DEFAULT_GENERATOR_CLASS
File "/build/drf-yasg-nonfree-1.21.3/src/drf_yasg/app_settings.py", line 122,
in __getattr__
val = perform_import(val, attr)
File "/usr/lib/python3/dist-packages/rest_framework/settings.py", line 166,
in perform_import
return import_from_string(val, setting_name)
File "/usr/lib/python3/dist-packages/rest_framework/settings.py", line 177,
in import_from_string
return import_string(val)
File "/usr/lib/python3/dist-packages/django/utils/module_loading.py", line
17, in import_string
module = import_module(module_path)
File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/build/drf-yasg-nonfree-1.21.3/src/drf_yasg/generators.py", line 19, in
from .inspectors.field import get_basic_type_info, get_queryset_field,
get_queryset_from_view
File "/build/drf-yasg-nonfree-1.21.3/src/drf_yasg/inspectors/__init__.py",
line 5, in
from .field import (
File "/build/drf-yasg-nonfree-1.21.3/src/drf_yasg/inspectors/field.py", line
406, in
(serializers.NullBooleanField, (openapi.TYPE_BOOLEAN, None)),
AttributeError: module 'rest_framework.serializers' has no attribute
'NullBooleanField'
make[1]: *** [debian/rules:19: override_dh_sphinxdoc] Error 2
Andreas
drf-yasg-nonfree_1.21.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: drf-yasg-nonfree
Source-Version: 1.21.4-1
Done: Carsten Schoenert
We believe that the bug you reported is fixed in the latest version of
drf-yasg-nonfree, 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 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Carsten Schoenert (supplier of updated
drf-yasg-nonfree package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 22 Oct 2022 09:07:06 +0200
Source: drf-yasg-nonfree
Architecture: source
Version: 1.21.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Carsten Schoenert
Closes: 1021858
Changes:
drf-yasg-nonfree (1.21.4-1) unstable; urgency=medium
.
* [ca47ce4] New upstream version 1.21.4
(Closes: #1021858)
* [f2e0237] d/{control,rules}: Switch to dh-sequence-python3
Checksums-Sha1:
288e5280984d4ddd014475020841996ae7266389 2477 drf-yasg-nonfree_1.21.4-1.dsc
1a47a5ca00434632601a77a7cc86ab826283d1aa 6721110
drf-yasg-nonfree_1
Processed: autopkgtest regressions are RC (and this one also blocks the perl transition)
Processing commands for cont...@bugs.debian.org: > severity 1021658 serious Bug #1021658 [latexml] latexml: AutoPKG test suite fails since latest upload of TLive Severity set to 'serious' from 'important' > block 1019353 by 1021658 Bug #1019353 [release.debian.org] transition: perl 5.36 1019353 was blocked by: 1022133 1022150 1021324 1016761 1021735 1022132 1020446 1022124 1022152 1019353 was blocking: 1022003 Added blocking bug(s) of 1019353: 1021658 > thanks Stopping processing here. Please contact me if you need assistance. -- 1019353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019353 1021658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020702: [3dprinter-general] Bug#1020702: prusa-slicer: SEGV on start still happens [but different cause]
Prusa Slicer 2.5.0+dfsg-2 still SIGSEGV's during startup on Bookworm with some sid. A local rebuild does also runs into Segfault. However, it also reports that it is unable to init glew. I'm quite sure it is a different issue, but the result is quite the same. So i was unsure if I should open a new Bug. It *is* a different issue, but related. Upstream has stated that they're not supporting wxWidgets 3.2 yet: https://github.com/prusa3d/PrusaSlicer/issues/8299#issuecomment-1236874810 It's probably best to open a new issue covering other wx 3.2 crashes/issues, since a fix for the segfault was already released. That being said, the comments on the upstream bug report make it sound like fixes for wx 3.2 will take some time, so it may be best to classify the new bug report as serious, so it will block the transition of the broken 2.5.0 package to testing?
Bug#1022214: kbuild FTBFS
control: fixed -1 1:0.1.9998svn3571+dfsg-2 control: close -1 thanks! G. On Sat, 22 Oct 2022 09:19:29 +0300 Adrian Bunk wrote: Source: kbuild Version: 1:0.1.9998svn3571+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=kbuild&ver=1%3A0.1.9998svn3571%2Bdfsg-1 ... kBuild: Compiling kmk_sed - /<>/src/sed/sed/compile.c The failing command: @gcc -c -O2 -g -O3 -m64 -I/<>/out/linux.amd64/release/obj/kmk -I/<>/src/kmk -I/<>/src/lib -I/<>/src/lib/kStuff/include -I/<>/src/kmk/glob -DKBUILD_VERSION_MAJOR=0 -DKBUILD_VERSION_MINOR=1 -DKBUILD_VERSION_PATCH=9998 -DKBUILD_OS_LINUX -DKBUILD_ARCH_AMD64 -DHAVE_CONFIG_H -DKBUILD_SVN_REV=3571 "-DKBUILD_TYPE=\\\"release\\\"" -DNO_ARCHIVES -DEXPERIMENTAL -DCONFIG_WITH_TOUPPER_TOLOWER -DCONFIG_WITH_DEFINED -DCONFIG_WITH_EXPLICIT_MULTITARGET -DCONFIG_WITH_DOT_MUST_MAKE -DCONFIG_WITH_PREPEND_ASSIGNMENT -DCONFIG_WITH_LOCAL_VARIABLES -DCONFIG_WITH_2ND_TARGET_EXPANSION -DCONFIG_WITH_ALLOC_CACHES -DCONFIG_WITH_STRCACHE2 -DKMK -DKMK_HELPERS -DCONFIG_NO_DEFAULT_SUFFIXES -DCONFIG_NO_DEFAULT_PATTERN_RULES -DCONFIG_NO_DEFAULT_TERMINAL_RULES -DCONFIG_NO_DEFAULT_SUFFIX_RULES -DCONFIG_NO_DEFAULT_VARIABLES -DCONFIG_WITH_ABSPATHEX -DCONFIG_WITH_COMMANDS_FUNC -DCONFIG_WITH_DATE -DCONFIG_WITH_DEFINED_FUNCTIONS -DCONFIG_WITH_EVALPLUS -DCONFIG_WITH_FILE_SIZE -DCONFIG_WITH_LOOP_FUNCTIONS -DCONFIG_WITH_MATH -DCONFIG_WITH_NANOTS -DCONFIG_WITH_ROOT_FUNC -DCONFIG_WITH_RSORT -DCONFIG_WITH_STACK -DCONFIG_WITH_STRING_FUNCTIONS -DCONFIG_WITH_WHERE_FUNCTION -DCONFIG_WITH_WHICH -DCONFIG_WITH_XARGS -DCONFIG_WITH_EXTENDED_NOTPARALLEL -DCONFIG_WITH_INCLUDEDEP -DCONFIG_WITH_VALUE_LENGTH -DCONFIG_WITH_COMPARE -DCONFIG_WITH_SET_CONDITIONALS -DCONFIG_WITH_IF_CONDITIONALS -DCONFIG_WITH_PRINTF -DCONFIG_WITH_MINIMAL_STATS -DCONFIG_PRETTY_COMMAND_PRINTING -DCONFIG_WITH_PRINT_STATS_SWITCH -DCONFIG_WITH_PRINT_TIME_SWITCH -DCONFIG_WITH_RDONLY_VARIABLE_VALUE -DCONFIG_WITH_LAZY_DEPS_VARS -DCONFIG_WITH_MEMORY_OPTIMIZATIONS "-DKBUILD_HOST=\\\"linux\\\"" "-DKBUILD_HOST_ARCH=\\\"amd64\\\"" "-DKBUILD_HOST_CPU=\\\"blend\\\"" -DCONFIG_WITH_KMK_BUILTIN_STATS -DCONFIG_WITH_KMK_BUILTIN -DNDEBUG -DCONFIG_WITH_OPTIMIZATION_HACKS -Wp,-MD,/<>/out/linux.amd64/release/obj/kmk/main.o.dep -Wp,-MT,/<>/out/linux.amd64/release/obj/kmk/main.o -Wp,-MP -o /<>/out/linux.amd64/release/obj/kmk/main.o /<>/src/kmk/main.c kBuild: Compiling kmk - /<>/src/kmk/main.c : warning: missing terminating " character : warning: missing terminating " character : warning: missing terminating " character : warning: missing terminating " character /<>/src/kmk/main.c: In function ‘print_usage’: : error: stray ‘\’ in program /<>/src/kmk/main.c:3556:14: note: in expansion of macro ‘KBUILD_HOST’ 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^~~ : error: missing terminating " character /<>/src/kmk/main.c:3556:14: note: in expansion of macro ‘KBUILD_HOST’ 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^~~ /<>/src/kmk/main.c:3556:25: error: expected expression before ‘,’ token 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^ : error: stray ‘\’ in program /<>/src/kmk/main.c:3556:27: note: in expansion of macro ‘KBUILD_HOST_ARCH’ 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^~~~ : error: missing terminating " character /<>/src/kmk/main.c:3556:27: note: in expansion of macro ‘KBUILD_HOST_ARCH’ 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^~~~ : error: stray ‘\’ in program /<>/src/kmk/main.c:3556:45: note: in expansion of macro ‘KBUILD_HOST_CPU’ 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^~~ : error: missing terminating " character /<>/src/kmk/main.c:3556:45: note: in expansion of macro ‘KBUILD_HOST_CPU’ 3556 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU); | ^~~ : error: stray ‘\’ in program /<>/src/kmk/main.c:3559:14: note: in expansion of macro ‘KBUILD_HOST’ 3559 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU, remote_description); | ^~~ : error: missing terminating " character /<>/src/kmk/main.c:3559:14: note: in expansion of macro ‘KBUILD_HOST’ 3559 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU, remote_description); | ^~~ : error: stray ‘\’ in program /<>/src/kmk/main.c:3559:27: note: in expansion of macro ‘KBUILD_HOST_ARCH’ 3559 | KBUILD_HOST, KBUILD_HOST_ARCH, KBUILD_HOST_CPU, remote_description); | ^~~~ : error: missing terminating " character /<>/src/kmk/main.c:3559:27: note: in expansion of macro ‘KBUILD_HO
Processed: Re: kbuild FTBFS
Processing control commands: > fixed -1 1:0.1.9998svn3571+dfsg-2 Bug #1022214 [src:kbuild] kbuild FTBFS The source 'kbuild' and version '1:0.1.9998svn3571+dfsg-2' do not appear to match any binary packages Marked as fixed in versions kbuild/1:0.1.9998svn3571+dfsg-2. > close -1 Bug #1022214 [src:kbuild] kbuild FTBFS Marked Bug as done -- 1022214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#983010 marked as pending in debiman
Processing control commands: > tag -1 pending Bug #983010 [src:debiman] mdocml breaks debiman autopkgtest: different output Added tag(s) pending. -- 983010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983010: marked as pending in debiman
Control: tag -1 pending Hello, Bug #983010 in debiman 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/go-team/packages/debiman/-/commit/5a07b13789fa1be7b4e99ab7771e7743fb6088d0 Update TestToHTML testdata to match mandoc-1.14.6 output Closes: #983010 (this message was generated automatically) -- Greetings https://bugs.debian.org/983010
Bug#983010: marked as done (mdocml breaks debiman autopkgtest: different output)
Your message dated Sat, 22 Oct 2022 09:04:30 + with message-id and subject line Bug#983010: fixed in debiman 0.0~git20220907.a582536-1 has caused the Debian Bug report #983010, regarding mdocml breaks debiman autopkgtest: different output 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.) -- 983010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mdocml, debiman Control: found -1 mdocml/1.14.5-1 Control: found -1 debiman/0.0~git20200217.fc82521-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of mdocml the autopkgtest of debiman fails in testing when that autopkgtest is run with the binary packages of mdocml from unstable. It passes when run with only packages from testing. In tabular form: passfail mdocml from testing1.14.5-1 debimanfrom testing0.0~git20200217.fc82521-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Normally I would assign this bug to debiman as it captures the output of a different program (so it seems to me) in the test. However, we're in the freeze and this is a new upstream release (which we request to be reluctant with), so please *align* quickly how to best move forward. Currently this regression is blocking the migration of mdocml 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=mdocml https://ci.debian.net/data/autopkgtest/testing/amd64/d/debiman/10541019/log.gz === CONT TestToHTML/i3lock 2021/02/18 04:13:33 mandocd not found, falling back to fork+exec for each manpage === CONT TestToHTML/refs 2021/02/18 04:13:33 mandocd not found, falling back to fork+exec for each manpage === CONT TestToHTML/i3lock convert_test.go:92: unexpected conversion result: (diff from want → got): --- /tmp/debiman-849248825 2021-02-18 04:13:33.034473409 + +++ /tmp/debiman-376692162 2021-02-18 04:13:33.034473409 + @@ -7,67 +7,76 @@ - - + + + NAME¶ i3lock - improved screen locker - + + + SYNOPSIS¶ i3lock [-v] [-c color] - + + + DESCRIPTION¶ i3lock is a simple screen locker like slock. After starting it, you will see a white screen (you can configure the color/an image). You can return to your screen by entering your password. - + + + IMPROVEMENTS¶ • i3lock forks, so you can combine it with an alias to suspend to RAM (run "i3lock && echo mem > /sys/power/state" to get a locked screen after waking up your computer from suspend to RAM) - - • You can specify either a background color or a PNG image which will be displayed while your screen is locked. - - • You can specify whether i3lock should bell upon a wrong password. - - • i3lock uses PAM and therefore is compatible with LDAP, etc. - - + + + + OPTIONS¶ -v, --version Display the version of your i3lock - + - - -c rrggbb, --color=rrggbb Turn the screen into the given color instead of white. Color must be given in 3-byte format: rrggbb (i.e. ff is red). - + + + DPMS¶ The -d (--dpms) option. - + verbatim - + + + SEE ALSO¶ xautolock(1) - use i3lock as your screen saver - + + + AUTHOR¶ -Michael Stapelberg
Bug#1022222: valgrind-if-available shouldn't stop providing valgrind on mipsel
Package: valgrind-if-available Version: 3.18.1-1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Alessandro Ghedini , Debian UBports Team Control: affects -1 src:qtmir valgrind-if-available (3.18.1-1-1) unstable; urgency=medium ... * Drop mipsel as valgrind disagrees about blah blah baseline Loongson. This is wrong, and it makes at least qtmir FTBFS. If there is any problem with valgrind on mipsel it should be discussed and resolved in valgrind first, if valgrind is available then valgrind-if-available has to provide it. It is also unclear what the baseline problem is this changelog entry is referring to, there is no open bug in the valgrind package mentioned and the closest I could find was a bug that was fixed (sic) 5 years ago. It is also suprising if this is really a mipsel-only issue as the changelog claims, I would have expected any issues to also show up on mips64el. Therefore please report any issues with valgrind on mipsel as bugs against src:valgrind, but in any case please make valgrind-if-available always provide valgrind on all architectures where it is available.
Processed: valgrind-if-available shouldn't stop providing valgrind on mipsel
Processing control commands: > affects -1 src:qtmir Bug #102 [valgrind-if-available] valgrind-if-available shouldn't stop providing valgrind on mipsel Added indication that 102 affects src:qtmir -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022223: Removal notice: obsolete
Source: haskell-pipes-zlib Version: 0.4.4.2-3 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS (see #1015280) * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1013473: marked as done (ruby-redis: FTBFS: ERROR: Test "ruby3.0" failed.)
Your message dated Sat, 22 Oct 2022 15:10:16 +0530 with message-id <4ve5kr.pitrv36uhg...@onenetbeyond.org> and subject line Re: ruby-redis: FTBFS: ERROR: Test "ruby3.0" failed. has caused the Debian Bug report #1013473, regarding ruby-redis: FTBFS: ERROR: Test "ruby3.0" 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.) -- 1013473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-redis Version: 4.5.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"redis\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /<>/debian/ruby-redis/usr/share/rubygems-integration/all/gems/redis-4.5.1/lib/redis/client.rb:163:in > `call': ERR wrong number of arguments for 'cluster|reset' command > (Redis::CommandError) > from > /<>/debian/ruby-redis/usr/share/rubygems-integration/all/gems/redis-4.5.1/lib/redis.rb:3577:in > `block in cluster' > from > /<>/debian/ruby-redis/usr/share/rubygems-integration/all/gems/redis-4.5.1/lib/redis.rb:72:in > `block in synchronize' > from /usr/lib/ruby/3.0.0/monitor.rb:202:in `synchronize' > from /usr/lib/ruby/3.0.0/monitor.rb:202:in `mon_synchronize' > from > /<>/debian/ruby-redis/usr/share/rubygems-integration/all/gems/redis-4.5.1/lib/redis.rb:72:in > `synchronize' > from > /<>/debian/ruby-redis/usr/share/rubygems-integration/all/gems/redis-4.5.1/lib/redis.rb:3576:in > `cluster' > from /<>/test/support/cluster/orchestrator.rb:121:in > `block in reset_cluster' > from /<>/test/support/cluster/orchestrator.rb:121:in `each' > from /<>/test/support/cluster/orchestrator.rb:121:in > `reset_cluster' > from /<>/test/support/cluster/orchestrator.rb:27:in > `rebuild' > from bin/cluster_creator:9:in `' > could not create redis cluster > ERROR: Test "ruby3.0" failed. The full build log is available from: http://qa-logs.debian.net/2022/06/24/ruby-redis_4.5.1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On Fri, 24 Jun 2022 09:08:01 +0200 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. It is building fine now as seen in https://buildd.debian.org/stat
Bug#1022224: libxml2: CVE-2022-40303: Integer overflows with XML_PARSE_HUGE
Source: libxml2 Version: 2.9.14+dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libxml2. CVE-2022-40303[0]: | Integer overflows with XML_PARSE_HUGE If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 [1] https://gitlab.gnome.org/GNOME/libxml2/-/commit/c846986356fc149915a74972bf198abc266bc2c0 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1022225: libxml2: CVE-2022-40304: dict corruption caused by entity reference cycles
Source: libxml2 Version: 2.9.14+dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libxml2. CVE-2022-40304[0]: | dict corruption caused by entity reference cycles If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 [1] https://gitlab.gnome.org/GNOME/libxml2/-/commit/1b41ec4e9433b05bb0376be4725804c54ef1d80b Regards, Salvatore
Bug#1021566: fixed in opencascade 7.6.3+dfsg1-4
Thanks Tobias for the quick fix! François signature.asc Description: This is a digitally signed message part
Bug#997499: marked as done (onionshare: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sat, 22 Oct 2022 10:00:11 +
with message-id
and subject line Bug#997499: fixed in onionshare 2.5-1
has caused the Debian Bug report #997499,
regarding onionshare: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.9 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.)
--
997499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onionshare
Version: 2.2-3
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[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'include_package_data'
> warnings.warn(msg)
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> rm -rf *.egg-info
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building onionshare using existing
> ./onionshare_2.2.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building onionshare in onionshare_2.2-3.debian.tar.xz
> dpkg-source: info: building onionshare in onionshare_2.2-3.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'include_package_data'
> warnings.warn(msg)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'include_package_data'
> warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/onionshare
> copying onionshare/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare
> copying onionshare/strings.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare
> copying onionshare/common.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare
> copying onionshare/onion.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare
> copying onionshare/settings.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare
> copying onionshare/onionshare.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare
> creating /<>/.pybuild/cpython3_3.9/build/onionshare/web
> copying onionshare/web/receive_mode.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare/web
> copying onionshare/web/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare/web
> copying onionshare/web/send_base_mode.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare/web
> copying onionshare/web/website_mode.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare/web
> copying onionshare/web/share_mode.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare/web
> copying onionshare/web/web.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare/web
> creating /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/threads.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/widgets.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/update_checker.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/onionshare_gui.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/server_status.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/settings_dialog.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> copying onionshare_gui/tor_connection_dialog.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui
> creating /<>/.pybuild/cpython3_3.9/build/onionshare_gui/mode
> copying onionshare_gui/mode/file_selection.py ->
> /<>/.pybuild/cpython3_3.9/build/onionshare_gui/mode
> copying onionshare_gui/mode/history.py ->
> /<>/.pybuild/cpyth
Bug#1022070: System will not boot
Same problem on update to Kernel: 5.10.0-19-amd64 x86_64, Boots OK on 18. Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 43 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 23 Model: 24 Model name: AMD Ryzen 3 3200G with Radeon Vega Graphics Stepping:1 Frequency boost: enabled CPU MHz: 1304.298 CPU max MHz: 3600. CPU min MHz: 1400. BogoMIPS:7186.49 Virtualization: AMD-V L1d cache: 128 KiB L1i cache: 256 KiB L2 cache:2 MiB L3 cache:4 MiB NUMA node0 CPU(s): 0-3 Let me know if additional information is needed for the fix.
Bug#1022137: marked as done (wike: Wike does not run due to missing python3-requests)
Your message dated Sat, 22 Oct 2022 11:39:25 + with message-id and subject line Bug#1022137: fixed in wike 1.8.1+ds-2 has caused the Debian Bug report #1022137, regarding wike: Wike does not run due to missing python3-requests 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.) -- 1022137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wike Version: 1.8.1+ds-1 Severity: important X-Debbugs-Cc: apanda...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I am using Wike in Ubuntu Unity 22.10, and Wike did not load. I ran `wike` from Python, and got the error message ``` $ wike Traceback (most recent call last): File "/usr/bin/wike", line 47, in from wike import application File "/usr/share/wike/wike/application.py", line 29, in from wike.window import Window File "/usr/share/wike/wike/window.py", line 26, in from wike.header import HeaderBar File "/usr/share/wike/wike/header.py", line 29, in from wike.search import SearchEntry File "/usr/share/wike/wike/search.py", line 26, in from wike import wikipedia File "/usr/share/wike/wike/wikipedia.py", line 20, in import requests ModuleNotFoundError: No module named 'requests' ``` The fix is to manually install `python3-requests`. The package `python3-requests` should be a dependency of Wike (Also, the flatpak and the AUR packages have this dependency. See https://github.com/hugolabe/Wike/blob/6502f46b9f5c38104febb39ee2c078954092f65b/build- aux/flatpak/python3-requests.json and https://aur.archlinux.org/packages/wike ) -- System Information: Debian Release: bookworm/sid APT prefers kinetic APT policy: (500, 'kinetic') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-21-generic (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wike depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gir1.2-handy-1 1.8.0-1 ii gir1.2-webkit2-4.0 2.38.0-1 ii python3 3.10.6-1 wike recommends no packages. wike suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: wike Source-Version: 1.8.1+ds-2 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of wike, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated wike package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Oct 2022 06:47:14 -0400 Source: wike Built-For-Profiles: noudeb Architecture: source Version: 1.8.1+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Matthias Geiger Closes: 1022137 Changes: wike (1.8.1+ds-2) unstable; urgency=medium . * Added missing dependency (Closes: #1022137) Checksums-Sha1: c574c9c74448494e00bea27293c206208d15e226 2014 wike_1.8.1+ds-2.dsc 68a28479a6022ec0d0b208e934f6c796019b1e26 8180 wike_1.8.1+ds-2.debian.tar.xz e94d0b35c354c7f82534b6cc99fb5df3ac2deeff 9427 wike_1.8.1+ds-2_source.buildinfo Checksums-Sha256: 9d4786709f49fb6f4ab98d82caffb67072086994fa9ef5089e0cee69c6939a62 2014 wike_1.8.1+ds-2.dsc f3f516841c5e4053be7e247d643681a0638504b508a0ad75e2f63c73e2cb5dd9 8180 wike_1.8.1+ds-2.debian.tar.xz e9f1047c379b6e6bb17e6af926fdd0a3b7e76f98ed6d969e2377387cc5e13792 9427 wike_1.8.1+ds-2_source.buildinfo Files: ed2da073bd006d2d3b1fe7e4e113304d 2014 gnome optional wike_1.8.1+ds-2.dsc 58a39fefe38725a91f147497d85e68c5 8180 gnome optional wike_1.8.1+ds-2.debian.tar.xz ace7acf2cb6146eb206cd44adb5545ee 9427 gnome optional wike_1.8.1+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmNTylEACgkQ5mx3Wuv+ bH1RxhAAj6ScfCygtki1V
Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696
Hi, On Fri, Jul 15, 2022 at 02:04:38PM +0200, Moritz Mühlenhoff wrote: > Source: onionshare > X-Debbugs-CC: t...@security.debian.org > Severity: grave > Tags: security > > Hi, > > The following vulnerabilities were published for onionshare. > > CVE-2021-41867[0]: > | An information disclosure vulnerability in OnionShare 2.3 before 2.4 > | allows remote unauthenticated attackers to retrieve the full list of > | participants of a non-public OnionShare node via the --chat feature. > > https://github.com/onionshare/onionshare/compare/v2.3.3...v2.4 > https://www.ihteam.net/advisory/onionshare/ > > CVE-2021-41868[1]: > | OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to > | upload files on a non-public node when using the --receive > | functionality. > > https://github.com/onionshare/onionshare/compare/v2.3.3...v2.4 > https://www.ihteam.net/advisory/onionshare/ > > CVE-2022-21688[2]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. Affected versions of the desktop application were > | found to be vulnerable to denial of service via an undisclosed > | vulnerability in the QT image parsing. Roughly 20 bytes lead to 2GB > | memory consumption and this can be triggered multiple times. To be > | abused, this vulnerability requires rendering in the history tab, so > | some user interaction is required. An adversary with knowledge of the > | Onion service address in public mode or with authentication in private > | mode can perform a Denial of Service attack, which quickly results in > | out-of-memory for the server. This requires the desktop application > | with rendered history, therefore the impact is only elevated. This > | issue has been patched in version 2.5. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v > > CVE-2022-21689[3]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. In affected versions the receive mode limits > | concurrent uploads to 100 per second and blocks other uploads in the > | same second, which can be triggered by a simple script. An adversary > | with access to the receive mode can block file upload for others. > | There is no way to block this attack in public mode due to the > | anonymity properties of the tor network. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-jh82-c5jw-pxpc > > CVE-2022-21690[4]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. In affected versions The path parameter of the > | requested URL is not sanitized before being passed to the QT frontend. > | This path is used in all components for displaying the server access > | history. This leads to a rendered HTML4 Subset (QT RichText editor) in > | the Onionshare frontend. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-ch22-x2v3-v6vq > > CVE-2022-21691[5]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. In affected versions chat participants can spoof > | their channel leave message, tricking others into assuming they left > | the chatroom. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-w9m4-7w72-r766 > > CVE-2022-21692[6]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. In affected versions anyone with access to the chat > | environment can write messages disguised as another chat participant. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-gjj5-998g-v36v > > CVE-2022-21693[7]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. In affected versions an adversary with a primitive > | that allows for filesystem access from the context of the Onionshare > | process can access sensitive files in the entire user home folder. > | This could lead to the leaking of sensitive data. Due to the automatic > | exclusion of hidden folders, the impact is reduced. This can be > | mitigated by usage of the flatpak release. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-jgm9-xpfj-4fq6 > > CVE-2022-21694[8]: > | OnionShare is an open source tool that lets you securely and > | anonymously share files, host websites, and chat with friends using > | the Tor network. The website mode of the onionshare allows to use a > | hardened CSP, which will block any scripts and external resources. It > | is not possible to configure this CSP for individual pages and > | therefore the security enhancement cannot be used for
Processed: Bug#1021994 marked as pending in fastqtl
Processing control commands: > tag -1 pending Bug #1021994 [src:fastqtl] fastqtl: binary-all FTBFS Added tag(s) pending. -- 1021994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021995: marked as pending in fastqtl
Control: tag -1 pending Hello, Bug #1021995 in fastqtl 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/med-team/fastqtl/-/commit/adfe5e3d62b11c03f354a357afbff671c6d32a62 d/t/fastqtl_expected_output.txt: update to match behavior of v7. Closes: #1021995 (this message was generated automatically) -- Greetings https://bugs.debian.org/1021995
Processed: Bug#1021995 marked as pending in fastqtl
Processing control commands: > tag -1 pending Bug #1021995 [src:fastqtl] fastqtl: autopkgtest regression Added tag(s) pending. -- 1021995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021994: marked as pending in fastqtl
Control: tag -1 pending Hello, Bug #1021994 in fastqtl 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/med-team/fastqtl/-/commit/3041e96e8e255fc754a4c19548d4bae6cda5c643 d/rules: only fix permissions for arch-any builds. Closes: #1021994 (this message was generated automatically) -- Greetings https://bugs.debian.org/1021994
Bug#1021735: libffi upgrade breaks Wayland on aarch64
Hi, This libffi upgrade also completely breaks all use of Wayland on aarch64. We use libffi to dispatch protocol messages (requests received by the server and events received by the client) to native-code handlers, and we are now getting completely nonsensical values from it. Can this upgrade please be rolled back until it can be root-caused and fixed? Cheers, Daniel
Bug#949756: marked as done (staticsite FTBFS: FAIL: test_site (tests.test_page_filter.TestPageFilter))
Your message dated Sat, 22 Oct 2022 14:02:12 +0200 with message-id <20221022120212.d53m4acijxel3...@enricozini.org> and subject line Fixed in 1.6-1 has caused the Debian Bug report #949756, regarding staticsite FTBFS: FAIL: test_site (tests.test_page_filter.TestPageFilter) 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.) -- 949756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: staticsite Version: 1.4.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=staticsite&arch=all&ver=1.4.1-1&stamp=1578410781&raw=0 ... == FAIL: test_site (tests.test_page_filter.TestPageFilter) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.8/build/tests/test_page_filter.py", line 22, in test_site self.assertEqual(select(site, path="blog/*"), [ AssertionError: Lists differ: ['/blog/post2', '/blog/post1'] != ['/blog/post1', '/blog/post2'] First differing element 0: '/blog/post2' '/blog/post1' - ['/blog/post2', '/blog/post1'] + ['/blog/post1', '/blog/post2'] -- Ran 55 tests in 3.425s FAILED (failures=1) --- End Message --- --- Begin Message --- Hello, thank you for reporting this. Version 1.6-1 has as fix, and buildds have just finished building the package correctly. Enrico -- GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini --- End Message ---
Processed: forcibly merging 947425 962278
Processing commands for cont...@bugs.debian.org: > forcemerge 947425 962278 Bug #947425 [incron] incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug Bug #973927 [incron] incron SEGV when monitoring directories Bug #973927 [incron] incron SEGV when monitoring directories Marked as found in versions incron/0.5.10-3. Marked as found in versions incron/0.5.10-3. Bug #962278 [incron] Incron crash with an "*** unhandled exception occurred ***" Set Bug forwarded-to-address to 'https://github.com/ar-/incron/issues/36'. Severity set to 'grave' from 'normal' Marked as found in versions incron/0.5.12-1 and incron/0.5.12-1+deb10u1. Added tag(s) patch, security, and upstream. Merged 947425 962278 973927 > thanks Stopping processing here. Please contact me if you need assistance. -- 947425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947425 962278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962278 973927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022200: CPAN should be more helpful on missing key when check_sigs is enabled (Was: Re: cpan: cannot check signatures)
Hi! Thanks for your report. I could reproduce your issue if I enable check_sigs option in CPAN (which is _not_ the default). Thing is, it's not a bug, really. Or not quite. It's a result of the correction of a bug in CPAN < 2.29 who would succeed silently if there is no signature/no way to check the key. You can find some context in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015985 and http://blogs.perl.org/users/neilb/2021/11/addressing-cpan-vulnerabilities-related-to-checksums.html I do agree that it's bad UX that CPAN isn't more helpful when the key isn't available, e.g. asking for it or suggesting a way to get it, but the fact that it fails if the key isn't available while the Checksums are signed is the right behavior, and your workaround (getting the key) is the right solution. CPAN doesn't have a way to centralize key themself, and probably shouldn't, either. Not sure how such error can be avoided completely (the Debian method of having a preconfigured keyring won't do for CPAN IMO), but it should at least suggest a solution. So setting the severity back to normal, but still leaving the bug open, since it's confusing for the user, and it could be done better (upstream). Cheers, -- nodens
Processed: severity of 1022200 is normal
Processing commands for cont...@bugs.debian.org: > severity 1022200 normal Bug #1022200 [perl] cpan: cannot check signatures Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1022200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021994: marked as done (fastqtl: binary-all FTBFS)
Your message dated Sat, 22 Oct 2022 12:35:28 + with message-id and subject line Bug#1021994: fixed in fastqtl 2.184+v7+dfsg-3 has caused the Debian Bug report #1021994, regarding fastqtl: binary-all FTBFS 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.) -- 1021994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fastqtl Version: 2.184+v7+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=fastqtl&arch=all&ver=2.184%2Bv7%2Bdfsg-2&stamp=1665929072&raw=0 ... dh_fixperms chmod -x debian/*/usr/share/fastqtl/*.R chmod: cannot access 'debian/*/usr/share/fastqtl/*.R': No such file or directory make[1]: *** [debian/rules:21: override_dh_fixperms] Error 1 --- End Message --- --- Begin Message --- Source: fastqtl Source-Version: 2.184+v7+dfsg-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of fastqtl, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated fastqtl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Oct 2022 13:50:04 +0200 Source: fastqtl Architecture: source Version: 2.184+v7+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1021994 1021995 Changes: fastqtl (2.184+v7+dfsg-3) unstable; urgency=medium . * Team upload. * d/rules: only fix permissions for arch-any builds. (Closes: #1021994) * d/t/fastqtl_expected_output.txt: update to match behavior of v7. (Closes: #1021995) Checksums-Sha1: c4098c3fa8f50dceed8472f68032c43ddbce526e 2366 fastqtl_2.184+v7+dfsg-3.dsc b4f04e334d20302ee310bce9402ec9500d257227 20796 fastqtl_2.184+v7+dfsg-3.debian.tar.xz Checksums-Sha256: 7542ceb3ef5dda6d4ce419df90d067c6d7ad56f9d4dc52a6b508a9f0afaaae9b 2366 fastqtl_2.184+v7+dfsg-3.dsc b364ceb5f6b352e8c908475f9ae671622e542be42bee2fdaee0bd96d1cb66582 20796 fastqtl_2.184+v7+dfsg-3.debian.tar.xz Files: 998ea471818c60ceced84e19c53de755 2366 science optional fastqtl_2.184+v7+dfsg-3.dsc eea9107515f36d9e41ff982111c1d472 20796 science optional fastqtl_2.184+v7+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmNT2+gUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqi9A//RZLDI7hsM6H3r+zjFCYV/ydgYwRl KnCrtddU+ElqQ/MxHKnrmF8VIQmERZJ/5RMQQGtX7J78nmsCm+P7daDzhtFSRdTR mSvZcj+NRLulHgDHOgRVtZo6vQKDGryEGIiY2mCzzyXdVBDK7/0NNgelWJhQ7bS3 KGgwua7+bYgdwQ+LQK5wVxTHXepac6JiDiaHSqM7ml641BCLicxoKXlF1MscqcD6 K3pln4E8MtF7ffvU+GLdJ2Pxi+vbIWTiJjbTosPQnC/ALoNXdTcESzqv4Gs8Hwwb Dn/2T/pJnF/syL2etTIRyIdAGF/4cV58ngXGC+ZbREsV13XikTg9wksv1IpCNeIa WV9E11InS9/S6ffQ884xVoOT29UKsDdUc9HydFymflSqJmdewtuSvuPMppSHD6rY tV7YCnC0JIF6bALvhrSd2PAfzkExuqQFdJFGWj74FVlsid3KMJZhgXcmQgWMRA8U 1VQnmz6D3wQSNd4Khk+FrjluPnFUvnnaHUWqq13MNo+vF0Kb/pI3WxdvH7shwOU+ t1ndTTbP3fbaUS175sRAIxxfH2pzPeUWIIzaBXnXarSo3pZZ0umjeA5HNXU6bvlF vRG/nN9p/qch6WGUsFbti0GXXaUwSxVD2fgkNXOfdK+0yqp5DD4MWzZX8EZyOiyT LfRRdCvO/4w50vs= =v5em -END PGP SIGNATURE End Message ---
Bug#1021995: marked as done (fastqtl: autopkgtest regression)
Your message dated Sat, 22 Oct 2022 12:35:28 + with message-id and subject line Bug#1021995: fixed in fastqtl 2.184+v7+dfsg-3 has caused the Debian Bug report #1021995, regarding fastqtl: autopkgtest regression 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.) -- 1021995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fastqtl Version: 2.184+v7+dfsg-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/f/fastqtl/27230464/log.gz ... autopkgtest [23:13:45]: test run-sample-analysis: [--- covariates.txt.gz genotypes.vcf.gz genotypes.vcf.gz.tbi interaction.txt phenotypes.bed.gz phenotypes.bed.gz.tbi [33mF[0mast [33mQTL[0m * Authors : Olivier DELANEAU, Halit ONGEN, Alfonso BUIL & Manolis DERMITZAKIS * Contact : olivier.delan...@gmail.com * Webpage : http://fastqtl.sourceforge.net/ * Version : v2.184_gtex Perform permutation based interaction analysis (used to calculate corrected p-values for MPs) * Perform 100 permutations * Test interaction with term from [interaction.txt] * Random number generator is seeded with 1 * Considering variants within 1e+06 bp of the MPs * Using minor allele frequency threshold = 0. * Using minor allele sample threshold = 0 * Using INFO field AF threshold = 0. * Chunk processed 1 / 100 Scanning phenotype data in [phenotypes.bed.gz] * 364 phenotypes Reading phenotype data in [phenotypes.bed.gz] * region = 22:17517460-17646177 * 373 samples included * 4 phenotypes included Reading genotype data in [genotypes.vcf.gz] in VCF format * region = 22:16517460-18646177 * 373 samples included * 8580 sites included Reading covariates in [covariates.txt.gz] * 373 samples included * 4 covariate(s) included Reading interaction term in [interaction.txt] * 373 samples included Imputing missing genotypes Imputing missing phenotypes Initialize covariate Processing gene [ENSG0237438.1] * Number of variants in cis = 7966 * Beta distribution parameters = 1.0382 2287.7101 * Progress = 25.0% Processing gene [ENSG0177663.8] * Number of variants in cis = 8165 * Beta distribution parameters = 0.7994 2826.0721 * Progress = 50.0% Processing gene [ENSG0183307.3] * Number of variants in cis = 8279 * Beta distribution parameters = 0.9595 9906.5566 * Progress = 75.0% Processing gene [ENSG0069998.8] * Number of variants in cis = 8466 * Beta distribution parameters = 0.9606 4564.2130 * Progress = 100.0% Running time: 37 seconds 5d4 < ENSG0093072.10 8531 1.06453 1772.43 334.203 snp_22_17738177 -948 0.000356058 0.683168 0.649116 autopkgtest [23:14:22]: test run-sample-analysis: ---] autopkgtest [23:14:22]: test run-sample-analysis: - - - - - - - - - - results - - - - - - - - - - run-sample-analysis FAIL non-zero exit status 1 Likely the files under debian/tests/output_tests/ must be regenerated. --- End Message --- --- Begin Message --- Source: fastqtl Source-Version: 2.184+v7+dfsg-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of fastqtl, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated fastqtl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Oct 2022 13:50:04 +0200 Source: fastqtl Architecture: source Version: 2.184+v7+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1021994 1021995 Changes: fastqtl (2.184+v7+dfsg-3) unstable; urgency=medium . * Team upload. * d/rules: only fix permissions for arch-any builds. (Closes: #1021994) * d/t/fastqtl_expected_output.txt: update to match behavior of v7. (Closes: #1021995) Checksums-Sha1: c4098c3fa8f50dceed8472f68032c43ddbce526e 2366 fastqtl_2.184+v7+dfsg-3.dsc b4f04e334d20302ee310bce9402ec9500d257227 20796 fastqtl_2.184+v7+dfsg-3.debian.tar.xz Checksums-Sha256: 7542ceb3ef5dda6d4ce
Bug#1004764: marked as done (openboard: FTBFS with ffmpeg 5.0)
Your message dated Sat, 22 Oct 2022 12:43:36 +
with message-id
and subject line Bug#1004764: fixed in openboard 1.6.4+dfsg-1
has caused the Debian Bug report #1004764,
regarding openboard: FTBFS with ffmpeg 5.0
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.)
--
1004764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openboard
Version: 1.6.1+dfsg1-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0
openboard FTBFS with ffmpeg 5.0 in experimental:
| g++ -c -pipe -std=c++11 -fopenmp -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -std=gnu++1y -w -D_REENTRANT -fPIC
-DNO_THIRD_PARTY_WARNINGS -DUBVERSION="\"1.6.1."\"
-DUBVERSION_RC=1,6,1,240,0309 -DQT_CORE_LIB -DQT_NO_DEBUG
-DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_SVG_LIB -DQT_UITOOLS_LIB
-DQT_MULTIMEDIAWIDGETS_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB
-DQT_MULTIMEDIA_LIB -DQT_GUI_LIB -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB
-DQT_XML_LIB -DQT_CORE_LIB -Isrc -Isrc/web/browser
-Isrc/qtsingleapplication/src -Isrc/pdf-merger -Iplugins/cffadaptor/src
-I/usr/include/quazip -I/usr/include/poppler -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu/qt5/QtCore
-I/usr/include/x86_64-linux-gnu/qt5
-I/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets
-I/usr/include/x86_64-linux-gnu/qt5/QtWebKit
-I/usr/include/x86_64-linux-gnu/qt5/QtSvg
-I/usr/include/x86_64-linux-gnu/qt5/QtUiTools
-I/usr/include/x86_64-linux-gnu/qt5/QtMultimediaWidgets
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
-I/usr/include/x86_64-linux-gnu/qt5/QtMultimedia
-I/usr/include/x86_64-linux-gnu/qt5/QtGui
-I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork
-I/usr/include/x86_64-linux-gnu/qt5/QtXml -Ibuild/linux/release/moc
-Ibuild/linux/release/ui -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o
build/linux/release/objects/UBFFmpegVideoEncoder.o
src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp: In function ‘void
writeFrame(AVFrame*, AVPacket*, AVStream*, AVFormatContext*)’:
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:183:21: error: ‘AVStream’ {aka
‘struct AVStream’} has no member named ‘codec’
| 183 | if (stream->codec->codec_type == AVMEDIA_TYPE_AUDIO)
| | ^
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:184:49: error: ‘AVStream’ {aka
‘struct AVStream’} has no member named ‘codec’
| 184 | ret = avcodec_encode_audio2(stream->codec, packet, frame,
&gotOutput);
| | ^
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:184:19: error:
‘avcodec_encode_audio2’ was not declared in this scope; did you mean
‘avcodec_encode_subtitle’?
| 184 | ret = avcodec_encode_audio2(stream->codec, packet, frame,
&gotOutput);
| | ^
| | avcodec_encode_subtitle
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:186:49: error: ‘AVStream’ {aka
‘struct AVStream’} has no member named ‘codec’
| 186 | ret = avcodec_encode_video2(stream->codec, packet, frame,
&gotOutput);
| | ^
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:186:19: error:
‘avcodec_encode_video2’ was not declared in this scope; did you mean
‘avcodec_encode_subtitle’?
| 186 | ret = avcodec_encode_video2(stream->codec, packet, frame,
&gotOutput);
| | ^
| | avcodec_encode_subtitle
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:192:48: error: ‘AVStream’ {aka
‘struct AVStream’} has no member named ‘codec’
| 192 | AVRational codecTimebase = stream->codec->time_base;
| |^
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp: In member function ‘bool
UBFFmpegVideoEncoder::init()’:
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:291:5: error: ‘av_register_all’
was not declared in this scope
| 291 | av_register_all();
| | ^~~
| src/podcast/ffmpeg/UBFFmpegVideoEncoder.cpp:292:5: error:
‘avcodec_register_all’ was not declared in this scope
| 292 | avcodec_register_all();
| | ^~~~
| src/podcast/ffmpeg/UBFFmpegVideoEncode
Bug#1012809: marked as done (openboard: Update for Poppler 22.06)
Your message dated Sat, 22 Oct 2022 12:43:37 +
with message-id
and subject line Bug#1012809: fixed in openboard 1.6.4+dfsg-1
has caused the Debian Bug report #1012809,
regarding openboard: Update for Poppler 22.06
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.)
--
1012809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openboard
Version: 1.6.1+dfsg2-1
Severity: normal
Tags: patch
X-Debbugs-Cc: nathan.teodo...@canonical.com
Dear Maintainer,
Since Poppler 22.06 is making its way into experimental (currently in NEW[1]),
Openboard will need the compatibility changes from upstream to build. I
collected them in the attached patch.
[1]: https://ftp-master.debian.org/new.html
-- System Information:
Debian Release: bookworm/sid
APT prefers kinetic
APT policy: (500, 'kinetic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.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 openboard depends on:
ii libavcodec58 7:4.4.2-1ubuntu3
ii libavformat58 7:4.4.2-1ubuntu3
ii libavutil56 7:4.4.2-1ubuntu3
ii libc6 2.35-0ubuntu3
ii libgcc-s1 12.1.0-2ubuntu1
ii libgomp1 12.1.0-2ubuntu1
pn libpoppler118
ii libqt5core5a 5.15.4+dfsg-2
ii libqt5gui55.15.4+dfsg-2
ii libqt5multimedia5 5.15.4-1
ii libqt5multimediawidgets5 5.15.4-1
ii libqt5network55.15.4+dfsg-2
ii libqt5svg55.15.4-1
ii libqt5webkit5 5.212.0~alpha4-18
ii libqt5widgets55.15.4+dfsg-2
ii libqt5xml55.15.4+dfsg-2
ii libquazip5-1 0.9.1-2
ii libssl3 3.0.3-5ubuntu3
ii libstdc++612.1.0-2ubuntu1
ii libswresample37:4.4.2-1ubuntu3
ii libswscale5 7:4.4.2-1ubuntu3
ii libx11-6 2:1.7.5-1
pn openboard-common
ii zlib1g1:1.2.11.dfsg-2ubuntu9
openboard recommends no packages.
Versions of packages openboard suggests:
pn openboard-contrib
Description: Backport for Poppler 22.06 compatibility
Author: Nathan Pratta Teodosio
--- a/src/pdf/XPDFRenderer.cpp 2022-06-14 11:15:55.508584513 -0300
+++ b/src/pdf/XPDFRenderer.cpp 2022-06-14 11:16:00.312570630 -0300
@@ -95,6 +95,8 @@
}
#ifdef USE_XPDF
mDocument = new PDFDoc(new GString(filename.toLocal8Bit()), 0, 0, 0); //
the filename GString is deleted on PDFDoc desctruction
+#elif POPPLER_VERSION_MAJOR > 22 || (POPPLER_VERSION_MAJOR == 22 &&
POPPLER_VERSION_MINOR >= 3)
+mDocument = new
PDFDoc(std::make_unique(filename.toLocal8Bit()));
#else
mDocument = new PDFDoc(new GooString(filename.toLocal8Bit()), 0, 0, 0); //
the filename GString is deleted on PDFDoc desctruction
#endif
--- End Message ---
--- Begin Message ---
Source: openboard
Source-Version: 1.6.4+dfsg-1
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
openboard, 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 1012...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated openboard 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: Sat, 22 Oct 2022 13:56:57 +0200
Source: openboard
Architecture: source
Version: 1.6.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Packaging Team
Changed-By: Mike Gabriel
Closes: 1004764 1012809
Changes:
openboard (1.6.4+dfsg-1) unstable; urgency=medium
.
* New upstream release.
- Support building against POPPLER 22.03. (Closes: #1012809).
* debian/{copyright,rules}:
+ No need to remove files from src/qtsingleapplication/, replaced by
src/singleapplication/ (different code base).
* debian/patches:
Processed: block 1008016 with 1022233
Processing commands for cont...@bugs.debian.org: > block 1008016 with 1022233 Bug #1008016 [wnpp] ITP: safe-network -- network routing and service daemon for the Safe Network 1008016 was blocked by: 1013142 1013109 1016409 1020418 984864 1013106 1010275 1013138 1010212 1020407 1013144 974118 1013137 1021826 1020425 1013139 1010075 1020419 1019044 1013115 1013108 1009888 1013136 1019090 1020420 1017918 1013117 1020422 1010099 1010083 1008016 was not blocking any bugs. Added blocking bug(s) of 1008016: 1022233 Warning: Unknown package 'librust-tracing-subscriber-dev' > thanks Stopping processing here. Please contact me if you need assistance. -- 1008016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696
Hi Salvatore, Le 22/10/2022 à 13:49, Salvatore Bonaccorso a écrit : For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-41867 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41867 [1] https://security-tracker.debian.org/tracker/CVE-2021-41868 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41868 [2] https://security-tracker.debian.org/tracker/CVE-2022-21688 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21688 [3] https://security-tracker.debian.org/tracker/CVE-2022-21689 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21689 [4] https://security-tracker.debian.org/tracker/CVE-2022-21690 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21690 [5] https://security-tracker.debian.org/tracker/CVE-2022-21691 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21691 [6] https://security-tracker.debian.org/tracker/CVE-2022-21692 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21692 [7] https://security-tracker.debian.org/tracker/CVE-2022-21693 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21693 [8] https://security-tracker.debian.org/tracker/CVE-2022-21694 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21694 [9] https://security-tracker.debian.org/tracker/CVE-2022-21695 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21695 [10] https://security-tracker.debian.org/tracker/CVE-2022-21696 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21696 From the reported list CVE-2021-41867 and CVE-2021-41868 were addressed in 2.4 upstream. But the other seem yet unfixed in 2.5, even though likely as well those who contain "has been patched in 2.5". I have not found any indication that this there is really the case. Any more insights OTOH from you on those? According to onionshare 2.5 release notes [1], and to the vulnerabilities list on the github project [2], I'd say they were fixed. All vulnerabilities are marked as affecting <2.4 since 2.5 release, and for instance for the username impersonation, it's been specified in the release notes that the security have been tightened on this front. That said, I didn't check the code for every vuln individually, and I definitely could ask upstream for clarification/confirmation if you think it's necessary. [1] https://github.com/onionshare/onionshare/releases/tag/v2.5 [2] https://github.com/onionshare/onionshare/security/advisories Cheers, -- nodens
Bug#1022234: prusa-slicer: Another instant segmentation fault…
Package: prusa-slicer Version: 2.5.0+dfsg-2 Severity: grave Justification: renders package unusable prusa-slicer SEGV at start. (in the last stackframe, in imgui, this is a nullptr…) backtrace: Thread 1 "slic3r_main" received signal SIGSEGV, Segmentation fault. 0x568b12d3 in ImFont::CalcTextSizeA (this=0x0, size=0, max_width=max_width@entry=3.40282347e+38, wrap_width=-1, text_begin=text_begin@entry=0x569c42bd "A", text_end=0x569c42be "", remaining=remaining@entry=0x0) at ./src/imgui/imgui_draw.cpp:3408 Download failed: Invalid argument. Continuing without source file ./obj-x86_64-linux-gnu/src/imgui/./src/imgui/imgui_draw.cpp. 3408./src/imgui/imgui_draw.cpp: No such file or directory. (gdb) bt #0 0x568b12d3 in ImFont::CalcTextSizeA (this=0x0, size=0, max_width=max_width@entry=3.40282347e+38, wrap_width=-1, text_begin=text_begin@entry=0x569c42bd "A", text_end=0x569c42be "", remaining=remaining@entry=0x0) at ./src/imgui/imgui_draw.cpp:3408 #1 0x568655c3 in ImGui::CalcTextSize (text=text@entry=0x569c42bd "A", text_end=text_end@entry=0x0, hide_text_after_double_hash=hide_text_after_double_hash@entry=false, wrap_width=wrap_width@entry=-1) at ./src/imgui/imgui.cpp:4538 #2 0x56390716 in Slic3r::GUI::NotificationManager::HintNotification::count_spaces (this=0x59378dc0) at ./src/slic3r/GUI/HintNotification.cpp:564 #3 0x56390828 in Slic3r::GUI::NotificationManager::HintNotification::init (this=0x59378dc0) at ./src/slic3r/GUI/HintNotification.cpp:722 #4 0x5639db02 in Slic3r::GUI::NotificationManager::HintNotification::retrieve_data (this=0x59378dc0, new_hint=) at ./src/slic3r/GUI/HintNotification.cpp:1061 #5 0x5635ec45 in Slic3r::GUI::NotificationManager::HintNotification::HintNotification (new_hint=true, evt_handler=, id_provider=..., n=..., this=0x59378dc0) at ./src/slic3r/GUI/HintNotification.hpp:75 #6 std::make_unique () at /usr/include/c++/12/bits/unique_ptr.h:1065 #7 Slic3r::GUI::NotificationManager::push_hint_notification (this=0x588b3400, open_next=) at ./src/slic3r/GUI/NotificationManager.cpp:1848 #8 0x560ce7bf in Slic3r::GUI::GUI_App::post_init (this=0x56eb39b0) at ./src/slic3r/GUI/GUI_App.cpp:765 #9 0x560cee6c in operator() (event=..., __closure=) at ./src/slic3r/GUI/GUI_App.cpp:1324 #10 wxEventFunctorFunctor, Slic3r::GUI::GUI_App::on_init_inner():: >::operator()(wxEvtHandler *, wxEvent &) (this=0x58b569a0, event=...) at /usr/include/wx-3.2/wx/event.h:547 #11 0x76a07df2 in wxEvtHandler::ProcessEventIfMatchesId (entry=..., handler=, event=...) at ./src/common/event.cpp:1431 #12 0x76a0824e in wxEvtHandler::SearchDynamicEventTable (this=this@entry=0x56eb39b0, event=...) at ./src/common/event.cpp:1901 #13 0x76a085a0 in wxEvtHandler::TryHereOnly (this=this@entry=0x56eb39b0, event=...) at ./src/common/event.cpp:1624 #14 0x76a0864a in wxEvtHandler::TryBeforeAndHere (event=..., this=0x56eb39b0) at ./include/wx/event.h:4007 #15 wxEvtHandler::ProcessEventLocally (this=0x56eb39b0, event=...) at ./src/common/event.cpp:1561 #16 0x76a08751 in wxEvtHandler::ProcessEvent (this=0x56eb39b0, event=...) at ./src/common/event.cpp:1534 #17 0x768a08f2 in wxAppConsoleBase::ProcessIdle (this=0x56eb39b0) at ./src/common/appbase.cpp:435 #18 0x76246b34 in wxAppBase::ProcessIdle() () from /lib/x86_64-linux-gnu/libwx_gtk3u_core-3.2.so.0 #19 0x76150f99 in wxApp::DoIdle() () from /lib/x86_64-linux-gnu/libwx_gtk3u_core-3.2.so.0 #20 0x761510d3 in ?? () from /lib/x86_64-linux-gnu/libwx_gtk3u_core-3.2.so.0 #21 0x75d1e60f in g_main_dispatch (context=0x56eea320) at ../../../glib/gmain.c:3444 #22 g_main_context_dispatch (context=context@entry=0x56eea320) at ../../../glib/gmain.c:4162 #23 0x75d1e9c8 in g_main_context_iterate (context=0x56eea320, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4238 #24 0x75d1ec7f in g_main_loop_run (loop=loop@entry=0x58b562f0) at ../../../glib/gmain.c:4438 #25 0x7564a265 in gtk_main () at ../../../../gtk/gtkmain.c:1329 #26 0x7616da45 in wxGUIEventLoop::DoRun() () from /lib/x86_64-linux-gnu/libwx_gtk3u_core-3.2.so.0 #27 0x768d7f9d in wxEventLoopBase::Run (this=0x58b562b0) at ./src/common/evtloopcmn.cpp:87 #28 0x768a2a6b in wxAppConsoleBase::MainLoop (this=0x56eb39b0) at ./src/common/appbase.cpp:381 #29 0x7691feb7 in wxEntry (argc=, argv=) at ./src/common/init.cpp:503 #30 0x560af7b9 in Slic3r::GUI::GUI_Run (params=...) at ./src/slic3r/GUI/GUI_Init.cpp:54 #31 0x558705de in Slic3r::CLI::run (this=, argc=, argv=) at ./src/PrusaSlicer.cpp:618 #32 0x55845bf4 in main (argc=, argv=) at ./src/PrusaSlicer.cpp:844 -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT p
Bug#1022235: src:zeroinstall-injector: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel
Source: zeroinstall-injector Version: 2.16-2 Severity: serious Control: close -1 2.18-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:zeroinstall-injector has been trying to migrate for 62 days [2]. Hence, I am filing this bug. Your last version failed to build from source on armel, mips64el and mipsel while it built there successfully in the past. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=zeroinstall-injector OpenPGP_signature Description: OpenPGP digital signature
Processed: src:zeroinstall-injector: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel
Processing control commands: > close -1 2.18-1 Bug #1022235 [src:zeroinstall-injector] src:zeroinstall-injector: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel Marked as fixed in versions zeroinstall-injector/2.18-1. Bug #1022235 [src:zeroinstall-injector] src:zeroinstall-injector: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel Marked Bug as done -- 1022235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696
Hi Clément, On Sat, Oct 22, 2022 at 02:50:53PM +0200, Clément Hermann wrote: > Hi Salvatore, > > Le 22/10/2022 à 13:49, Salvatore Bonaccorso a écrit : > > > > > For further information see: > > > > > > [0] https://security-tracker.debian.org/tracker/CVE-2021-41867 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41867 > > > [1] https://security-tracker.debian.org/tracker/CVE-2021-41868 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41868 > > > [2] https://security-tracker.debian.org/tracker/CVE-2022-21688 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21688 > > > [3] https://security-tracker.debian.org/tracker/CVE-2022-21689 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21689 > > > [4] https://security-tracker.debian.org/tracker/CVE-2022-21690 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21690 > > > [5] https://security-tracker.debian.org/tracker/CVE-2022-21691 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21691 > > > [6] https://security-tracker.debian.org/tracker/CVE-2022-21692 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21692 > > > [7] https://security-tracker.debian.org/tracker/CVE-2022-21693 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21693 > > > [8] https://security-tracker.debian.org/tracker/CVE-2022-21694 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21694 > > > [9] https://security-tracker.debian.org/tracker/CVE-2022-21695 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21695 > > > [10] https://security-tracker.debian.org/tracker/CVE-2022-21696 > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21696 > > From the reported list CVE-2021-41867 and CVE-2021-41868 were > > addressed in 2.4 upstream. But the other seem yet unfixed in 2.5, even > > though likely as well those who contain "has been patched in 2.5". I > > have not found any indication that this there is really the case. > > > > Any more insights OTOH from you on those? > According to onionshare 2.5 release notes [1], and to the vulnerabilities > list on the github project [2], I'd say they were fixed. > All vulnerabilities are marked as affecting <2.4 since 2.5 release, and for > instance for the username impersonation, it's been specified in the release > notes that the security have been tightened on this front. > > That said, I didn't check the code for every vuln individually, and I > definitely could ask upstream for clarification/confirmation if you think > it's necessary. Thanks for the quick reply! (much appreciated). I think it would be good to get a confirmation from upstream and if possible to have those advisories updates. E.g. https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v while mentioning "affected versions < 2.4" the patched version remains "none". this might be that the < 2.4 just reflects the point in time when the advisory was filled. OTOH you have arguments with the v2.5 release information that they might all be fixed. To be on safe side, explicitly confirming by upstream would be great. Regards, Salvatore
Bug#1021850: marked as done (incron FTBFS with gcc 11)
Your message dated Sat, 22 Oct 2022 13:06:21 + with message-id and subject line Bug#1021850: fixed in incron 0.5.12-3 has caused the Debian Bug report #1021850, regarding incron FTBFS with gcc 11 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.) -- 1021850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: incron Version: 0.5.12-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=incron&ver=0.5.12-2%2Bb1 ... inotify-cxx.h: At global scope: inotify-cxx.h:450:32: error: ISO C++17 does not allow dynamic exception specifications 450 | void SetMask(uint32_t uMask) throw (InotifyException); |^ inotify-cxx.h:473:34: error: ISO C++17 does not allow dynamic exception specifications 473 | void SetEnabled(bool fEnabled) throw (InotifyException); | ^ inotify-cxx.h:544:13: error: ISO C++17 does not allow dynamic exception specifications 544 | Inotify() throw (InotifyException); | ^ ... --- End Message --- --- Begin Message --- Source: incron Source-Version: 0.5.12-3 Done: Emmanuel Bouthenot We believe that the bug you reported is fixed in the latest version of incron, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot (supplier of updated incron 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: Tue, 18 Oct 2022 16:38:29 + Source: incron Architecture: source Version: 0.5.12-3 Distribution: unstable Urgency: medium Maintainer: Emmanuel Bouthenot Changed-By: Emmanuel Bouthenot Closes: 947425 1021850 Changes: incron (0.5.12-3) unstable; urgency=medium . * Bump Standards-Version to 4.6.1.0 * Switch debian/watch version to 4 * Add a patch to fix FTBFS with gcc 11 (Closes: #1021850) * Add a patch to fix a segfault while using $@ in command to execute (Closes: #947425) Checksums-Sha1: 9a870492bd4a9ce61c348e0358946c4aa72ee96d 1831 incron_0.5.12-3.dsc 8d53dfd41221099c59fbf7fceabb25ad6d12e296 102104 incron_0.5.12-3.debian.tar.xz 099a8a099f90c1e319070b03eea0f4f6cdf327f8 6807 incron_0.5.12-3_source.buildinfo Checksums-Sha256: b67ef6cf324b948a060ce9d12856acefa3b1b95b483c9ec7482ffda4f48c5d76 1831 incron_0.5.12-3.dsc 81664c71213fa603022c504b450a0bab9faf129513bd2575c9b0bbd190ffa0f8 102104 incron_0.5.12-3.debian.tar.xz 9b9e39b4fc0ec5fefbca79f74dc372d5b7f04191d1b492d731e9e58027643f67 6807 incron_0.5.12-3_source.buildinfo Files: c133e609e0b90a052c71b15a75d6b8f8 1831 admin optional incron_0.5.12-3.dsc a15e98e650271575afeff96262ec878f 102104 admin optional incron_0.5.12-3.debian.tar.xz dc161b5887345b99378246a27d844fde 6807 admin optional incron_0.5.12-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQ1Tfow3vJnf8QuHSwd3I5KdQsMFAmNT4q4ACgkQSwd3I5Kd QsMzGQ/+JXDYpQluoZv3aa2NOU1lO7cUbN/o7QbCaJKixdXARg+H+2NvJeK1n0qB QLiLN4nLk5wpP7KkrRssJAc0eoMmWI0ScIT6QH7an21AHQSD+1Vm/yIY7ar9Mww2 kqqSBlo+TuGFS5BINboGYGh+ar7/kbEHYj83QsGm2Pjwb+zAHk/di7r3068znVu4 b/FOFT+5GluxlIC851PlzCnommrmAsnkFgS8i9HmR1S8SaJR4FmvrK1jIpX/AY7r oo/tbt7/ZCRTTBhyTBHnxeE6XVRsieTp5nE3QUym/iPemsowLN36USKVrE1VeblN OhGaqMr99p4Aq+/KAXylIqDBWd884geC+DJUW+gYwoh/tuK3LnqAWyNx/yoDMZhj Am9z4otduZ6U7w5fLCprNEoi53Ms1aHuDHrTGL3dhCWfTKOX/EOaaELXdiMOy2yj 3W4kpzbL9AD4/ai7brV+RWTziXmmd4rY2pTv322BQS1aHQv2pTLud+3GKtedRANG ErxXnZAAGcFWeDjwAvI6ItBvOCqevYhaORs3GEANMREe1fMS7BjFSPKucNsDc9y4 95oLnMTBRipaUisqJE7WkiyHAkxdpNbKt40moTYLc/XrbG38BsP3NVbrRWLUtmRg rjzwNoXQDQ5IT554wbCrIsjcOqB9Ul5zd17jS1XvXhAZHj3CS6s= =1xO1 -END PGP SIGNATURE End Message ---
Bug#947425: marked as done (incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug)
Your message dated Sat, 22 Oct 2022 13:06:21 +
with message-id
and subject line Bug#947425: fixed in incron 0.5.12-3
has caused the Debian Bug report #947425,
regarding incron crashes in IncronTabEntry::GetSafePath due to use-after-free
bug
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.)
--
947425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: incron
Version: 0.5.12-1
Severity: grave
Tags: security patch upstream
Hi,
incron crashes for me frequently. As incron runs as root, but is controllable
by users, this bug might be security-relevant, so I'm reporting it a severity
grave and tagging it security. Please downgrade if you can rule out this
concern.
Further investigation shows that the problem is caused by the creation of new
directories within watched paths: these trigger a reload of the inotify watch
target, rendering the old watch structure invalid. Only after the reload,
potential commands are executed. This may require to get path of the event, but
the corresponding pointer is invalid after the reload.
Attached is a patch that extracts the path before the reload, making this
problem disappear for me. Note that the patch assumes that LOOPER is not
defined, which seems to be the case for the Debian package.
Backtrace for reference:
bt full
#0 0x004ba484 in IncronTabEntry::GetSafePath (rPath=) at /usr/include/c++/8/bits/basic_string.h:1046
i = 0
stream =
len = 1919509615
#1 0x004c43f3 in UserTable::OnEvent (this=, rEvt=...) at
inotify-cxx.h:428
px = 40
pW = 0x1fbde40
pE = 0x1fbc920
events = "IN_CREATE,IN_ISDIR"
cmd = "/home/user/autoscripts/imageresize.sh "
cs = "/home/user/autoscripts/imageresize.sh $@/$# $# $%"
pos = 39
oldpos = 0
len =
pid =
#2 0x004c4767 in EventDispatcher::ProcessEvents (this=) at
usertable.cpp:110
pIn = 0x1fc7d24
it = {first = 1702521203, second = 0x1fc0072}
i = 2
pipe = false
evt = {m_uMask = 1073742080, m_uCookie = 0, m_name = "Neuer Ordner",
m_pWatch = 0x1fbde40}
#3 0x004b8650 in main (argc=, argv=) at
icd-main.cpp:458
res =
wm = 10184
in = {m_fd = 6, m_watches = std::map with 2 elements = {[1] =
0xbfc8ab40, [2] = 0xbfc8ab68}, m_paths = std::map with 2 elements = {
["/etc/incron.d"] = 0xbfc8ab40, ["/var/spool/incron"] =
0xbfc8ab68}, m_buf = '\000' ..., m_events = std::deque
with 0 elements}
stw = {m_path = "/etc/incron.d", m_uMask = 10184, m_wd = 1, m_pInotify
= 0xbfc8ab90, m_fEnabled = true}
utw = {m_path = "/var/spool/incron", m_uMask = 10184, m_wd = 2,
m_pInotify = 0xbfc8ab90, m_fEnabled = true}
ed = {m_iPipeFd = 4, m_iMgmtFd = 6, m_pIn = 0xbfc8ab90, m_pSys =
0xbfc8ab40, m_pUser = 0xbfc8ab68, m_maps = std::map with 1 element = {[8] =
0x1fc7d20},
m_size = 3, m_pPoll = 0x1fbe080}
cfg = "/etc/incron.conf"
lckdir = "/var/run"
lckfile = "incrond"
app = {m_path = "/var/run/incrond.pid", m_fLocked = true}
ret = 0
sysBase = "/etc/incron.d"
userBase = "/var/spool/incron"
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-6-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages incron depends on:
ii adduser 3.118
ii init-system-helpers 1.56+nmu1
ii libc62.28-10
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
ii lsb-base 10.2019051400
incron recommends no packages.
incron suggests no packages.
-- Configuration Files:
/etc/incron.allow [Errno 13] Keine Berechtigung: '/etc/incron.allow'
/etc/incron.deny [Errno 13] Keine Berechtigung: '/etc/incron.deny'
-- no debconf information
diff --git a/usertable.cpp b/usertable.cpp
index 3f1ef4a..bdc7f29 100644
--- a/usertable.cpp
+++ b/usertable.cpp
@@ -370,6 +370,8 @@ void UserTable::OnEvent(InotifyEvent& rEvt)
{
InotifyWatch* pW = rEvt.GetWatch();
IncronTabEntry* pE = FindEntry(pW);
+
+ std::string pWPath = pW->GetPath();
// no entry found - this shouldn't occur
if (pE == NULL)
@@ -422,7 +424,7 @@ void UserTable::OnEvent(InotifyEvent& rEvt)
Bug#973927: marked as done (incron SEGV when monitoring directories)
Your message dated Sat, 22 Oct 2022 13:06:21 +
with message-id
and subject line Bug#947425: fixed in incron 0.5.12-3
has caused the Debian Bug report #947425,
regarding incron SEGV when monitoring directories
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.)
--
947425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: incron
Version: 0.5.12-1+deb10u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Incrond crashes with SIGSEGV when monitoring IN_CREATE event in a directory and
a new directory is created inside the monitored dir.
How to reproduce :
su -
apt-get install incrond
echo root >/etc/incron.allow
echo '/home IN_CREATE,recursive=false /root/scripts/first-try $@ $#' |
incrontab -u root -
touch /home/foo-$RANDOM # this does not crash incrond
mkdir /home/foo-$RANDOM # this crashes incrond
Here is an strace output on the incrond daemon :
poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8, events=POLLIN}],
3, -1) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
--- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=18788, si_uid=0} ---
restart_syscall(<... resuming interrupted poll ...>) = 1
read(8, "\1\0\0\0\0\1\0@\0\0\0\0\20\0\0\0foo-5175\0\0\0\0\0\0\0\0", 32768) =
32
stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
getpid()= 20473
sendto(3, "<78>Nov 7 17:15:47 incrond[20473]: PATH (/home) FILE (foo-5175)
EVENT (IN_CREATE,IN_ISDIR)", 91, MSG_NOSIGNAL, NULL, 0) = 91
inotify_rm_watch(8, 1) = 0
nanosleep({tv_sec=1, tv_nsec=0}, 0x7ffe411006b0) = 0
openat(AT_FDCWD, "/var/spool/incron/root", O_RDONLY) = 7
fstat(7, {st_mode=S_IFREG|0600, st_size=62, ...}) = 0
read(7, "/home\tIN_CREATE,recursive=false\t/root/scripts/first-try $@ $#\n",
4096) = 62
read(7, "", 4096) = 0
close(7)= 0
stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
inotify_add_watch(8, "/home", IN_CREATE) = 2
mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f38a9f0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x7f38aa9ec000}
---
+++ killed by SIGSEGV +++
I'm not completely sure this is the same as #947425 . Sorry if this is the case.
-- System Information:
Debian Release: 10.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-12-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages incron depends on:
ii adduser 3.118
ii init-system-helpers 1.56+nmu1
ii libc62.28-10
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
ii lsb-base 10.2019051400
incron recommends no packages.
incron suggests no packages.
-- Configuration Files:
/etc/incron.allow [Errno 13] Permission non accordée: '/etc/incron.allow'
/etc/incron.deny [Errno 13] Permission non accordée: '/etc/incron.deny'
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: incron
Source-Version: 0.5.12-3
Done: Emmanuel Bouthenot
We believe that the bug you reported is fixed in the latest version of
incron, 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 947...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bouthenot (supplier of updated incron 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: Tue, 18 Oct 2022 16:38:29 +
Source: incron
Architecture: source
Version: 0.5.12-3
Distribution: unstable
Urgency: medium
Maintainer: Emmanuel Bouthenot
Changed-By: Emmanuel Bouthenot
Closes: 947425 1021850
Changes:
incron (0.5.12-3) unstable; urgency=medium
.
* Bump Standards-Version to 4.6.1.0
* Switch debian/watch version to 4
* Add a patch to fix FTBFS with gcc 11 (Closes: #1021850)
* Add a patch to fix a segfault wh
Bug#962278: marked as done (Incron crash with an "*** unhandled exception occurred ***" )
Your message dated Sat, 22 Oct 2022 13:06:21 + with message-id and subject line Bug#947425: fixed in incron 0.5.12-3 has caused the Debian Bug report #947425, regarding Incron crash with an "*** unhandled exception occurred ***" 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.) -- 947425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: incron Version: 0.5.10-3+b2 Severity: heavy Problem: --- Incron crash with an "*** unhandled exception occurred ***" if directories are deleted while Incron is monitoring them. Error is reproducible. # rm -Rf /var/lib/univention-appcenter/apps/myloud/data/myloud-data/user/files/Folder\ Test1/* If command to erase of pathes and/or files is moved to an own script (no 'rm') and the handling is smoother (via "sleep") and after the erase immediately an "service intron reload" take place, then intron crashes after (her max.) 3 to 4 pathes. Sometimes I received only „service incrond stopped“ in syslog. Solution: --- I have not found a workaround. Side effect: -- After executing commands „rm …“ and then „service incron reload“ in own script I see following messages in syslog: Jun 4 22:43:34 systemd[1]: Starting file system events scheduler... Jun 4 22:43:34 ncrond[3623]: loading system tables Jun 4 22:43:34 systemd[1]: incron.service: PID file /run/incrond.pid not readable (yet?) after start: No such file or directory and then Jun 4 22:43:34 systemd[1]: Started file system events scheduler. Jun 4 22:43:34 incrond[3623]: loading table Auser.conf Jun 4 22:43:34 incrond[3623]: loading table Buser.conf Jun 4 22:43:34 incrond[3623]: loading table example.conf Jun 4 22:43:34 incrond[3623]: cannot create watch for system table example.conf: (2) No such file or directory Jun 4 22:43:34 incrond[3623]: cannot create watch for system table example.conf: (2) No such file or directory Jun 4 22:43:34 incrond[3623]: cannot create watch for system table example.conf: (2) No such file or directory Jun 4 22:43:34 incrond[3623]: cannot create watch for system table example.conf: (2) No such file or directory ... Jun 4 22:43:34 incrond[3623]: loading table nextA.conf ... - Syslog: - Jun 04 22:57:48 incrond[18195]: (system::example.conf) CMD (/opt/scripts/incron_del_cron.sh /var/lib/univention-appcenter/apps/mycloud/data/mycloud-data /var/lib/univention-appcenter/apps/mycloud/data/mycloud-data/user Jun 04 22:57:49 incrond[18195]: *** unhandled exception occurred *** Jun 04 22:57:49 incrond[18195]: void InotifyWatch::SetEnabled(bool): enabling watch failed Jun 04 22:57:49 incrond[18195]: error: (2) No such file or directory Jun 04 22:57:49 incrond[18195]: stopping service Jun 04 22:57:49 systemd[1]:incron.service: Main process exited, code=exited, status=1/FAILURE Jun 04 22:57:49 systemd[1]:incron.service: Unit entered failed state. Jun 04 22:57:49 systemd[1]:incron.service: Failed with result 'exit-code'. --- Debian - # uname -v #1 SMP Debian 4.9.210-1 (2020-01-20) - Conf-files: - # ls -lah /etc/incron.d/example.conf -rw-r--r-- 1 root root 8,3K Jun 4 22:57 /etc/incron.d/example.conf etc/incond.d/example.conf (there are various other conf files in this incron directory, which all monitor other directories. There are no directory duplicates) -- /var/lib/univention-appcenter/apps/myloud/data/myloud-data/user/files/ IN_ATTRIB,IN_CLOSE_WRITE,IN_CREATE,IN_DELETE,IN_DELETE_SELF,IN_MOVE_SELF,IN_MOVED_FROM,IN_MOVED_TO,IN_ONLYDIR,IN_NO_LOOP /opt/scripts/incron_del_cron.sh /var/lib/univention-appcenter/apps/myloud/data/myloud-data $@ $# $% /var/lib/univention-appcenter/apps/myloud/data/myloud-data/user/files/Folder\ Test1/ IN_ATTRIB,IN_CLOSE_WRITE,IN_CREATE,IN_DELETE,IN_DELETE_SELF,IN_MOVE_SELF,IN_MOVED_FROM,IN_MOVED_TO,IN_ONLYDIR,IN_NO_LOOP /opt/scripts/incron_del_cron.sh /var/lib/univention-appcenter/apps/myloud/data/myloud-data $@ $# $% /var/lib/univention-appcenter/apps/myloud/data/myloud-data/user/files/Folder\ Test1/subfolder1/ IN_ATTRIB,IN_CLOSE_WRITE,IN_CREATE,IN_DELETE,IN_DELETE_SELF,IN_MOVE_SELF,IN_MOVED_FROM,IN_MOVED_TO,IN_ONLYDIR,IN_NO_LOOP /opt/scripts/incron_del_cron.sh /var/lib/univention-appcenter/apps/myloud/data/myloud-data $@ $# $% /var/lib/univention-appcenter/apps/myloud/data/myloud-data/user/files/Folder\ Test1/Subfolder2/ IN_ATTRIB,IN_CLOSE_WRITE,IN_CREATE,IN_DELETE,IN_DELETE_SELF,IN_MOVE_SELF,IN_MOVED_FROM,IN_MOVED_TO,IN_ONLYDIR,IN_
Processed: Bug#1022152 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #1022152 [src:postgresql-14] postgresql-14 rejected Added tag(s) pending. -- 1022152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022152: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #1022152 in postgresql 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/postgresql/postgresql/-/commit/3500c73817462c0d1588d9fc13dc83554a8c62a3 Stop building lib packages, postgresql-15 is already in unstable.. (Closes: #1022152) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022152
Bug#1012361: marked as done (New upstream version 4.2.2)
Your message dated Sat, 22 Oct 2022 13:34:35 + with message-id and subject line Bug#1001064: fixed in electrum 4.3.2+dfsg1-1 has caused the Debian Bug report #1001064, regarding New upstream version 4.2.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1001064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: electrum Version: 4.0.9-1 Severity: critical Hi, there's a new upstream version 4.2.2 available: https://electrum.org/#download Would be great to have that in Debian. Cheers, -- Guido --- End Message --- --- Begin Message --- Source: electrum Source-Version: 4.3.2+dfsg1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of electrum, 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. Bastian Germann (supplier of updated electrum 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: Tue, 18 Oct 2022 21:45:04 +0200 Source: electrum Architecture: source Version: 4.3.2+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Debian Cryptocoin Team Changed-By: Bastian Germann Closes: 1001064 1012361 1021959 Changes: electrum (4.3.2+dfsg1-1) unstable; urgency=high . * Team upload. * Patch: Replace vendored distutils with system's. . [ Soren Stoutner ] * New upstream version 4.3.2 (Closes: #1001064, #1012361, #1021959). * Repack the new version to remove sourceless minified JavaScript files (Closes ##1022095). * Switch to new "sourceonly" upstream tarball (see the upstream changelog for release 4.3.1). * Update dependencies and installed files. * Remove unneeded include-binaries file. * debian/control: Bump Standards-Version to 4.6.1 (no changes). * debian/copyright: Update and reformat copyright and license information. * debian/patches: - Refresh 0001-Improve-message-about-PyQt5.patch. - Add 0003-Correct-desktop-exec.patch. - Add 0004-Use-system-JavaScript-files.patch * debian/python3-electrum.link: Create file and add system resource links. * debian/rules: - Build paymentrequest_pb2.py from the .proto file. - Remove redundant license files from the binary packages. * debian/upstream/signing-key.asc: Strip superfluous signatures. * debian/watch: Update to version 4 and refactor for "sourceonly" tarball. Checksums-Sha1: fa18950f0ec19c0b9bb0163754a9fc7ab9318387 2462 electrum_4.3.2+dfsg1-1.dsc a920d64d1d2de95794d99b107efb58bbf31483c0 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 375f5d4fadab875f646abb9575482e3578c051a2 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz a37505fcdc3db9497b6ee0e7488d1e506b80c243 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Checksums-Sha256: af9ab8163fcb8d7096837c794ecc1ddc41be3483bd8a97e72cd202977dd355ea 2462 electrum_4.3.2+dfsg1-1.dsc 23753647503e1d9a0a6c655d65cf54a1b09a3dc3d1d609a29275bcc58e072cfa 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 0d09c55d303202161b237d9d4e2021f2279123358885632deea67aff72b5c218 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz 06fa2ea6682cd03f7dc35e4593216d3dbea9b5cad9a7372d8f0f7227dccb70b4 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Files: 47e89791fb72e9d4ada57b922de1b7ab 2462 utils optional electrum_4.3.2+dfsg1-1.dsc cbedc500f5a5f2e9594cff44a3ddf3f9 5086796 utils optional electrum_4.3.2+dfsg1.orig.tar.xz 502a8bd3ec4ff6d776c686507e6aacd8 15524 utils optional electrum_4.3.2+dfsg1-1.debian.tar.xz 5442e091b26ac9a164e8562b26a024ec 17025 utils optional electrum_4.3.2+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNT7WQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFDm2C/9mVe6yqu8Xnn5Xa0GecheG3HwrR0sNKSw5 e+3sZeZfE9IUNRnL07GwcHsTzfCukq6pLVVlY3mqf7v8gDwNjA6xWaFX3N6Crede AkKZ6OFKbx/zvLxTSECx8NR4dZsTnuhhs3Cb9Gzz9xEjAS6pxatKv/bSPZne8l/U vbRpxNEytTre1zzcLLkwVqvXd4/J9ay10CvqXrRyXRdToAQAA1cmgWbcgBXtfm/Z 24NAspDEKvpkf5Bx7ycrzRfIV4tmyqm/jrqutE5mRM1HcRWzRQqoCJRxfsJbI236 oOBtyywX8s97QyRuHg1eCoVhslST0WGpiOvjUIieQfdpdtP+vADVRUf3CpeRo4w4 pz5h+nUR0FATeASGvtsUb3
Bug#1001064: marked as done (electrum: Please package new upstream release)
Your message dated Sat, 22 Oct 2022 13:34:35 + with message-id and subject line Bug#1001064: fixed in electrum 4.3.2+dfsg1-1 has caused the Debian Bug report #1001064, regarding electrum: Please package new upstream release 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.) -- 1001064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: electrum Version: 4.0.9-1 Severity: wishlist Hello, Currently the electrum package is at version 4.0.9, but there is now december 2020 There are new upstream releases inbetween (currently 4.1.5) https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES Would it be possible to update to a newer version? 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) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: electrum Source-Version: 4.3.2+dfsg1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of electrum, 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. Bastian Germann (supplier of updated electrum 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: Tue, 18 Oct 2022 21:45:04 +0200 Source: electrum Architecture: source Version: 4.3.2+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Debian Cryptocoin Team Changed-By: Bastian Germann Closes: 1001064 1012361 1021959 Changes: electrum (4.3.2+dfsg1-1) unstable; urgency=high . * Team upload. * Patch: Replace vendored distutils with system's. . [ Soren Stoutner ] * New upstream version 4.3.2 (Closes: #1001064, #1012361, #1021959). * Repack the new version to remove sourceless minified JavaScript files (Closes ##1022095). * Switch to new "sourceonly" upstream tarball (see the upstream changelog for release 4.3.1). * Update dependencies and installed files. * Remove unneeded include-binaries file. * debian/control: Bump Standards-Version to 4.6.1 (no changes). * debian/copyright: Update and reformat copyright and license information. * debian/patches: - Refresh 0001-Improve-message-about-PyQt5.patch. - Add 0003-Correct-desktop-exec.patch. - Add 0004-Use-system-JavaScript-files.patch * debian/python3-electrum.link: Create file and add system resource links. * debian/rules: - Build paymentrequest_pb2.py from the .proto file. - Remove redundant license files from the binary packages. * debian/upstream/signing-key.asc: Strip superfluous signatures. * debian/watch: Update to version 4 and refactor for "sourceonly" tarball. Checksums-Sha1: fa18950f0ec19c0b9bb0163754a9fc7ab9318387 2462 electrum_4.3.2+dfsg1-1.dsc a920d64d1d2de95794d99b107efb58bbf31483c0 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 375f5d4fadab875f646abb9575482e3578c051a2 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz a37505fcdc3db9497b6ee0e7488d1e506b80c243 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Checksums-Sha256: af9ab8163fcb8d7096837c794ecc1ddc41be3483bd8a97e72cd202977dd355ea 2462 electrum_4.3.2+dfsg1-1.dsc 23753647503e1d9a0a6c655d65cf54a1b09a3dc3d1d609a29275bcc58e072cfa 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 0d09c55d303202161b237d9d4e2021f2279123358885632deea67aff72b5c218 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz 06fa2ea6682cd03f7dc35e4593216d3dbea9b5cad9a7372d8f0f7227dccb70b4 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Files: 47e89791fb72e9d4ada57b922de1b7ab 2462 utils optional electrum_4.3.2+dfsg1-1.dsc cbedc500f5a5f2e9594cff44a3ddf3f9 5086796 utils optional electrum_4.3.2+dfsg1.orig.tar.xz 502a8bd3ec4ff6d776c68650
Bug#1012361: marked as done (New upstream version 4.2.2)
Your message dated Sat, 22 Oct 2022 13:34:35 + with message-id and subject line Bug#1012361: fixed in electrum 4.3.2+dfsg1-1 has caused the Debian Bug report #1012361, regarding New upstream version 4.2.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1012361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: electrum Version: 4.0.9-1 Severity: critical Hi, there's a new upstream version 4.2.2 available: https://electrum.org/#download Would be great to have that in Debian. Cheers, -- Guido --- End Message --- --- Begin Message --- Source: electrum Source-Version: 4.3.2+dfsg1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of electrum, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated electrum 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: Tue, 18 Oct 2022 21:45:04 +0200 Source: electrum Architecture: source Version: 4.3.2+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Debian Cryptocoin Team Changed-By: Bastian Germann Closes: 1001064 1012361 1021959 Changes: electrum (4.3.2+dfsg1-1) unstable; urgency=high . * Team upload. * Patch: Replace vendored distutils with system's. . [ Soren Stoutner ] * New upstream version 4.3.2 (Closes: #1001064, #1012361, #1021959). * Repack the new version to remove sourceless minified JavaScript files (Closes ##1022095). * Switch to new "sourceonly" upstream tarball (see the upstream changelog for release 4.3.1). * Update dependencies and installed files. * Remove unneeded include-binaries file. * debian/control: Bump Standards-Version to 4.6.1 (no changes). * debian/copyright: Update and reformat copyright and license information. * debian/patches: - Refresh 0001-Improve-message-about-PyQt5.patch. - Add 0003-Correct-desktop-exec.patch. - Add 0004-Use-system-JavaScript-files.patch * debian/python3-electrum.link: Create file and add system resource links. * debian/rules: - Build paymentrequest_pb2.py from the .proto file. - Remove redundant license files from the binary packages. * debian/upstream/signing-key.asc: Strip superfluous signatures. * debian/watch: Update to version 4 and refactor for "sourceonly" tarball. Checksums-Sha1: fa18950f0ec19c0b9bb0163754a9fc7ab9318387 2462 electrum_4.3.2+dfsg1-1.dsc a920d64d1d2de95794d99b107efb58bbf31483c0 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 375f5d4fadab875f646abb9575482e3578c051a2 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz a37505fcdc3db9497b6ee0e7488d1e506b80c243 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Checksums-Sha256: af9ab8163fcb8d7096837c794ecc1ddc41be3483bd8a97e72cd202977dd355ea 2462 electrum_4.3.2+dfsg1-1.dsc 23753647503e1d9a0a6c655d65cf54a1b09a3dc3d1d609a29275bcc58e072cfa 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 0d09c55d303202161b237d9d4e2021f2279123358885632deea67aff72b5c218 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz 06fa2ea6682cd03f7dc35e4593216d3dbea9b5cad9a7372d8f0f7227dccb70b4 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Files: 47e89791fb72e9d4ada57b922de1b7ab 2462 utils optional electrum_4.3.2+dfsg1-1.dsc cbedc500f5a5f2e9594cff44a3ddf3f9 5086796 utils optional electrum_4.3.2+dfsg1.orig.tar.xz 502a8bd3ec4ff6d776c686507e6aacd8 15524 utils optional electrum_4.3.2+dfsg1-1.debian.tar.xz 5442e091b26ac9a164e8562b26a024ec 17025 utils optional electrum_4.3.2+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNT7WQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFDm2C/9mVe6yqu8Xnn5Xa0GecheG3HwrR0sNKSw5 e+3sZeZfE9IUNRnL07GwcHsTzfCukq6pLVVlY3mqf7v8gDwNjA6xWaFX3N6Crede AkKZ6OFKbx/zvLxTSECx8NR4dZsTnuhhs3Cb9Gzz9xEjAS6pxatKv/bSPZne8l/U vbRpxNEytTre1zzcLLkwVqvXd4/J9ay10CvqXrRyXRdToAQAA1cmgWbcgBXtfm/Z 24NAspDEKvpkf5Bx7ycrzRfIV4tmyqm/jrqutE5mRM1HcRWzRQqoCJRxfsJbI236 oOBtyywX8s97QyRuHg1eCoVhslST0WGpiOvjUIieQfdpdtP+vADVRUf3CpeRo4w4 pz5h+nUR0FATeASGvtsUb3
Bug#1001064: marked as done (electrum: Please package new upstream release)
Your message dated Sat, 22 Oct 2022 13:34:35 + with message-id and subject line Bug#1012361: fixed in electrum 4.3.2+dfsg1-1 has caused the Debian Bug report #1012361, regarding electrum: Please package new upstream release 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.) -- 1012361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: electrum Version: 4.0.9-1 Severity: wishlist Hello, Currently the electrum package is at version 4.0.9, but there is now december 2020 There are new upstream releases inbetween (currently 4.1.5) https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES Would it be possible to update to a newer version? 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) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: electrum Source-Version: 4.3.2+dfsg1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of electrum, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated electrum 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: Tue, 18 Oct 2022 21:45:04 +0200 Source: electrum Architecture: source Version: 4.3.2+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Debian Cryptocoin Team Changed-By: Bastian Germann Closes: 1001064 1012361 1021959 Changes: electrum (4.3.2+dfsg1-1) unstable; urgency=high . * Team upload. * Patch: Replace vendored distutils with system's. . [ Soren Stoutner ] * New upstream version 4.3.2 (Closes: #1001064, #1012361, #1021959). * Repack the new version to remove sourceless minified JavaScript files (Closes ##1022095). * Switch to new "sourceonly" upstream tarball (see the upstream changelog for release 4.3.1). * Update dependencies and installed files. * Remove unneeded include-binaries file. * debian/control: Bump Standards-Version to 4.6.1 (no changes). * debian/copyright: Update and reformat copyright and license information. * debian/patches: - Refresh 0001-Improve-message-about-PyQt5.patch. - Add 0003-Correct-desktop-exec.patch. - Add 0004-Use-system-JavaScript-files.patch * debian/python3-electrum.link: Create file and add system resource links. * debian/rules: - Build paymentrequest_pb2.py from the .proto file. - Remove redundant license files from the binary packages. * debian/upstream/signing-key.asc: Strip superfluous signatures. * debian/watch: Update to version 4 and refactor for "sourceonly" tarball. Checksums-Sha1: fa18950f0ec19c0b9bb0163754a9fc7ab9318387 2462 electrum_4.3.2+dfsg1-1.dsc a920d64d1d2de95794d99b107efb58bbf31483c0 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 375f5d4fadab875f646abb9575482e3578c051a2 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz a37505fcdc3db9497b6ee0e7488d1e506b80c243 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Checksums-Sha256: af9ab8163fcb8d7096837c794ecc1ddc41be3483bd8a97e72cd202977dd355ea 2462 electrum_4.3.2+dfsg1-1.dsc 23753647503e1d9a0a6c655d65cf54a1b09a3dc3d1d609a29275bcc58e072cfa 5086796 electrum_4.3.2+dfsg1.orig.tar.xz 0d09c55d303202161b237d9d4e2021f2279123358885632deea67aff72b5c218 15524 electrum_4.3.2+dfsg1-1.debian.tar.xz 06fa2ea6682cd03f7dc35e4593216d3dbea9b5cad9a7372d8f0f7227dccb70b4 17025 electrum_4.3.2+dfsg1-1_source.buildinfo Files: 47e89791fb72e9d4ada57b922de1b7ab 2462 utils optional electrum_4.3.2+dfsg1-1.dsc cbedc500f5a5f2e9594cff44a3ddf3f9 5086796 utils optional electrum_4.3.2+dfsg1.orig.tar.xz 502a8bd3ec4ff6d776c68650
Bug#1022234: prusa-slicer: Another instant segmentation fault…
A local rebuild with wx-widgets 3.0 makes the crash go away. Upstream states [1] that prusa-slicer is not ready for wxwidgets 3.2 -- maybe #1019825 should be reverted? As the crash happens in imgui: I did not check, if the embedded imgui library is the culprit. Embedded version is at 1.83, while we have in Debian 1.86. [1] From https://github.com/prusa3d/PrusaSlicer/issues/8299#issuecomment-1236874810 "But that is quite off-topic. Short version: if you link PrusaSlicer 2.5.x with wxWidgets 3.2, you will most likely break it." -- tobi
Processed: block 996464 with 1022233
Processing commands for cont...@bugs.debian.org: > block 996464 with 1022233 Bug #996464 [wnpp] ITP: atomic-data-rust -- graph database server to share Atomic Data on the web 996464 was blocked by: 1019090 1013104 1013100 1019144 1013108 1022219 1013109 1013103 969609 1020407 1013106 951683 1013098 1022193 1019349 984622 1010212 1022198 1013107 1013099 1010256 1019044 996464 was not blocking any bugs. Added blocking bug(s) of 996464: 1022233 Warning: Unknown package 'librust-tracing-subscriber-dev' > thanks Stopping processing here. Please contact me if you need assistance. -- 996464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022152: marked as done (postgresql-14 rejected)
Your message dated Sat, 22 Oct 2022 13:41:06 + with message-id and subject line Bug#1022152: fixed in postgresql-14 14.5-3 has caused the Debian Bug report #1022152, regarding postgresql-14 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.) -- 1022152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-14 Version: 14.5-2 Severity: serious Tags: ftbfs bunk@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/postgresql-14_14.5-2+b1_amd64-buildd.changes.reason Version check failed: Your upload included the binary package libecpg-compat3, version 14.5-2+b1, for amd64, however testing already has version 15.0-1. Uploads to unstable must have a higher version than present in testing. --- End Message --- --- Begin Message --- Source: postgresql-14 Source-Version: 14.5-3 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of postgresql-14, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated postgresql-14 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: Sat, 22 Oct 2022 14:48:48 +0200 Source: postgresql-14 Architecture: source Version: 14.5-3 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Closes: 1022152 Changes: postgresql-14 (14.5-3) unstable; urgency=medium . * Stop building lib packages, postgresql-15 is already in unstable.. (Closes: #1022152) Checksums-Sha1: 2b920edd09b95d1709898960eb7c3d58b23b0ca3 3768 postgresql-14_14.5-3.dsc 85cc42ba3546bddbcb07615d432cc0ed28da5de0 25320 postgresql-14_14.5-3.debian.tar.xz Checksums-Sha256: dd88c07f7152457e8435f38601beb31da33fd0d85e267597eac21ab462a4f5a5 3768 postgresql-14_14.5-3.dsc 5957cb1e2b78b5596cbcfe9b5b81470fe821ed1f83a088d4d451bd21d25ad363 25320 postgresql-14_14.5-3.debian.tar.xz Files: 0385051b84889a42f179f8fda4cc7846 3768 database optional postgresql-14_14.5-3.dsc 415ad2d8940e75246185969b7f5b533c 25320 database optional postgresql-14_14.5-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmNT76wACgkQTFprqxLS p659jw//RBLDRyMBtPlJCyI9/+bdHAEZ4CQvSEYExZ676+r0ouMN3ErUdoBH1epS twJnLe7B1/RFtwIMvyqrRqwiJ4NZP0gt/jYAvEp35zO6SIZSUNyWKrJhZfjloZhM 2MmLTuOe+Awyx1X+2v2RlXUdDXFL4SAyX+ByZU1zaDdheGpWCd1z9QybtSVu/Emp t0nP9UU93AZXay2mvJIjXV1yKB9TV3sIzkiGCowQUzirQk4SAQeNkMhwgWw6IJyv w9NSnp7bYqZBWHnH1DGXjdXqAL2rC8N+sTUOZUngYi6upRPF4OAsxflRYYAPVk4n TBggG0V1Hf8oThVVz9uOpet18fFKWtgYUu8v+hSNgqRagyn4W+7IVkXYMeNQOkzw 7YJoJ8nWaIxF/6h0AdpR7nn0LL6hREMx3DVkjFxT+ET8dPpH/TG5tH1uxG/JB26s LmCFoLk9P/kVIPploedOPBORo7z+Pja3zkROlo5QlCTBQOs0/RWTjthEBkydErkI r5Hi2HpH+6LjMpSzh9XVi1flqZhpM+IVNcA01L+RvGlLLmj26qpADYRtT0+u8R9M Re+IS4XkcnWtPEOcj5ie9j/fW3O8d6bNmaXpbDAlmuCrNgaDy/HmNXYHSmV5Oe1+ XEEibnIbLsrrSlGzChFBYPwXqwdQSrF3ToMM4UbnSm+2Cqw4MBQ= =mhHn -END PGP SIGNATURE End Message ---
Processed: tagging 1022025
Processing commands for cont...@bugs.debian.org: > tags 1022025 - moreinfo Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Bug #1022062 [src:linux] regression on amdgpu: drm_kms_helper "flip_done timed out" messages during boot and console freeze Bug #1022070 [src:linux] Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike Bug #1022147 [src:linux] regression on amdgpu: drm_kms_helper "flip_done timed out" messages during boot and console freeze Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051 1022062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022062 1022070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022070 1022147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022239: festival FTBFS: make[2]: *** [/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2
Source: festival Version: 1:2.5.0-8 Severity: serious X-Debbugs-Cc: sthiba...@debian.org Hi, Festival fails to build from source with: look at library Festival UniSyn.o us_prosody.o us_unit.o ps_synthesis.o us_mapping.o us_features.o Update library Festival UniSyn.o us_prosody.o us_unit.o ps_synthesis.o us_mapping.o us_features.o ar: `u' modifier ignored since `D' is the default (see `U') a - UniSyn.o a - us_prosody.o a - us_unit.o a - ps_synthesis.o a - us_mapping.o a - us_features.o us_diphone_unit.cc: In function ‘void load_full_diphone(int)’: us_diphone_unit.cc:243:9: warning: variable ‘pm_start’ set but not used [-Wunused-but-set-variable] 243 | int pm_start, pm_end, pm_middle; | ^~~~ us_diphone_unit.cc:243:19: warning: variable ‘pm_end’ set but not used [-Wunused-but-set-variable] 243 | int pm_start, pm_end, pm_middle; | ^~ us_diphone_unit.cc:243:27: warning: variable ‘pm_middle’ set but not used [-Wunused-but-set-variable] 243 | int pm_start, pm_end, pm_middle; | ^ look at library Festival init_modules.o Update library Festival init_modules.o ar: `u' modifier ignored since `D' is the default (see `U') a - init_modules.o look at library Festival UniSyn_diphone.o us_diphone_unit.o us_diphone_index.o Update library Festival UniSyn_diphone.o us_diphone_unit.o us_diphone_index.o ar: `u' modifier ignored since `D' is the default (see `U') a - UniSyn_diphone.o a - us_diphone_unit.o a - us_diphone_index.o rm init_modules.o make[2]: *** [/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:25: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:50: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1022239: festival FTBFS: make[2]: *** [/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2
Control: severity -1 important Control: tags -1 + moreinfo Hello, Nilesh Patra, le sam. 22 oct. 2022 19:40:52 +0530, a ecrit: > Festival fails to build from source with: [no actual error message] Please post the whole log, otherwise we can't see anything. I have tried to build festival both with plain bookworm and sid chroots, without any problem. So we need more information on your build environment: how it is different from a plain build environment. Samuel
Processed: Re: Bug#1022239: festival FTBFS: make[2]: *** [/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2
Processing control commands: > severity -1 important Bug #1022239 [src:festival] festival FTBFS: make[2]: *** [/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2 Severity set to 'important' from 'serious' > tags -1 + moreinfo Bug #1022239 [src:festival] festival FTBFS: make[2]: *** [/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2 Added tag(s) moreinfo. -- 1022239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010051: marked as done (ghostscript: crash converting PDF to PNG)
Your message dated Sat, 22 Oct 2022 16:55:47 +0200 with message-id <166645054798.2543.14296466229415952...@auryn.jones.dk> and subject line Re: crash converting PDF to PNG has caused the Debian Bug report #1010051, regarding ghostscript: crash converting PDF to PNG 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.) -- 1010051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpdf-builder-perl Version: 3.023-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > # 17,19: (0,0,0) #00 gray(0) > # 18,19: (0,0,0) #00 gray(0) > # 19,19: (0,0,0) #00 gray(0) > # ' > # Version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org > # Copyright: (C) 1999-2021 ImageMagick Studio LLC > # License: https://imagemagick.org/script/license.php > # Features: Cipher DPC Modules OpenMP(4.5) > # Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 > jpeg lcms lqr ltdl lzma openexr pangocairo png tiff webp wmf x xml zlib > # GPL Ghostscript 9.56.0 (2022-03-29) > # Copyright (C) 2022 Artifex Software, Inc. All rights reserved. > # Looks like you failed 2 tests of 19. > t/tiff.t > 1..19 > ok 1 - '$pdf->image_tiff(filename)' isa > 'PDF::Builder::Resource::XObject::Image::TIFF_GT' > ok 2 - Image from filename has a width > ok 3 - Add TIFF to PDF > ok 4 - '$pdf->image_tiff(filehandle)' isa > 'PDF::Builder::Resource::XObject::Image::TIFF' > ok 5 - Image from filehandle has a width > ok 6 - '$pdf->image_tiff(), LZW compression' isa > 'PDF::Builder::Resource::XObject::Image::TIFF_GT' > ok 7 - Add TIFF to PDF > ok 8 - Fail fast if the requested file doesn't exist > ok 9 - alpha + flate > ok 10 - G4 (not converted to flate) > ok 11 - single-strip lzw (not converted to flate) with GT > ok 12 - multi-strip lzw (not converted to flate) with GT > Error: /typecheck in --runpdf-- > Operand stack: >--dict:6/14(L)-- --dict:6/14(L)-- --dict:6/14(L)-- MediaBox > --nostringval-- 20.0 20.0 20.0 20.0 false 20.0 2 > Execution stack: >%interp_exit .runexec2 --nostringval-- runpdf --nostringval-- 2 > %stopped_push --nostringval-- runpdf runpdf false 1 > %stopped_push 1990 1 3 %oparray_pop 1989 1 3 %oparray_pop > 1977 1 3 %oparray_pop 1978 1 3 %oparray_pop runpdf runpdf > 2 1 1 runpdf %for_pos_int_continue runpdf runpdf runpdf > Dictionary stack: >--dict:765/1123(ro)(G)-- --dict:0/20(G)-- --dict:76/200(L)-- > --dict:18/20(L)-- > Current allocation mode is local > Last OS error: No such file or directory > not ok 13 - lzw+horizontal predictor (not converted to flate) with GT > ok 14 - alpha + lzw > ok 15 - single-strip lzw (not converted to flate) without GT > Error: /typecheck in --runpdf-- > Operand stack: >--dict:6/14(L)-- --dict:6/14(L)-- --dict:6/14(L)-- MediaBox > --nostringval-- 20.0 20.0 20.0 20.0 false 20.0 2 > Execution stack: >%interp_exit .runexec2 --nostringval-- runpdf --nostringval-- 2 > %stopped_push --nostringval-- runpdf runpdf false 1 > %stopped_push 1990 1 3 %oparray_pop 1989 1 3 %oparray_pop > 1977 1 3 %oparray_pop 1978 1 3 %oparray_pop runpdf runpdf > 2 1 1 runpdf %for_pos_int_continue runpdf runpdf runpdf > Dictionary stack: >--dict:765/1123(ro)(G)-- --dict:0/20(G)-- --dict:76/200(L)-- > --dict:18/20(L)-- > Current allocation mode is local > Last OS error: No such file or directory > not ok 16 - lzw+horizontal predictor (not converted to flate) without GT > ok 17 # skip multi-strip lzw without GT is not currently supported > ok 18 - successfully read TIFF with colormap > ok 19 - bilevel and alpha when width not a whole number of bytes with GT > Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/19 subtests > (less 1 skipped subtest: 16 okay) > t/viewer-preferences.t .. > 1..3 > ok 1 - Duplex => Simplex > ok 2 - Duplex => DuplexFlipLongEdge > ok 3 - Duplex => DuplexFlipShortEdge > ok > > Test Summary Report > --- > t/tiff.t (Wstat: 512 Tests: 19 Failed: 2) > Failed tests: 13, 16 > Non-zero exit status: 2 > Files=42, Tests=680, 22 wallclock secs ( 0.22 usr 0.07 sys + 16.41 cusr > 2.13 csy
Bug#1018754: telegram-cli: Outdated app that is no longer supported
Hi Paul, Ying-Chun Liu (PaulLiu) wrote: > Neither szqdong nor kenorb-contrib is working. > I've tried both. Meh. I had hope because at least their build CI seems to have been passed. Thanks a lot for having a look at it and testing! Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64
Processing control commands: > severity -1 critical Bug #1022232 [libffi8] libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64 Severity set to 'critical' from 'important' -- 1022232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022169: llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat)
Simon McVittie 于2022年10月21日周五 19:36写道： > > Source: llvm-toolchain-15 > Version: 1:15.0.2-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source, making mesa unbuildable > User: debian-m...@lists.debian.org > Usertags: mipsel mips64el > X-Debbugs-Cc: debian-m...@lists.debian.org, m...@packages.debian.org > Control: affects -1 + src:mesa > > Quoting from mips64el buildd logs, but mipsel has a similar failure: > > > /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_linux.cpp:67:1: > > error: static assertion failed due to requirement 'struct_kernel_stat_sz > > == sizeof(stat)': > > COMPILER_CHECK(struct_kernel_stat_sz == sizeof(struct stat)); > https://reviews.llvm.org/D135553 It is due to large file support is enabled by default for 32bit compiler_rt. > Strictly speaking this is not a regression because llvm-toolchain-15 was > never built successfully on mips*el, but I think it should be treated as > RC anyway, because older llvm-toolchain-* were buildable on mips*el (and > mesa is already using llvm-toolchain-15, making it a key package). > > smcv > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, > 'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, > 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.0.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) > Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), > LANGUAGE=en_GB:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > -- YunQiang Su
Bug#1019622: marked as done (ruby-factory-bot: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "undefined method 'static_attributes_are_gone' in 'broken' factory\n
Your message dated Sat, 22 Oct 2022 16:39:14 +
with message-id
and subject line Bug#1019622: fixed in ruby-factory-bot 6.2.1-1
has caused the Debian Bug report #1019622,
regarding ruby-factory-bot: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
expected NoMethodError with "undefined method 'static_attributes_are_gone'
in 'broken' factory\nDid you mean? 'static_attributes_are_gone { \"true\"
}'\n", got #https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-factory-bot
Version: 6.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-factory-bot with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
>expected NoMethodError with "undefined method
> 'static_attributes_are_gone' in 'broken' factory\nDid you mean?
> 'static_attributes_are_gone { \"true\" }'\n", got # method 'static_attributes_are_gone' in 'broken' factory
>Did you mean? 'static_attributes_are_gone { "true" }'
>
>
>raise NoMethodError.new(<<~MSG)
>^> with backtrace:
> # ./lib/factory_bot/definition_proxy.rb:99:in `method_missing'
> # ./spec/factory_bot/definition_proxy_spec.rb:69:in `block (3
> levels) in '
> # ./spec/factory_bot/definition_proxy_spec.rb:71:in `block (2
> levels) in '
> # ./spec/factory_bot/definition_proxy_spec.rb:71:in `block (2 levels) in
> '
>
> Finished in 0.429 seconds (files took 0.32709 seconds to load)
> 290 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/factory_bot/definition_proxy_spec.rb:66 #
> FactoryBot::DefinitionProxy#method_missing raises a NoMethodError when called
> with a static-attribute-like argument
>
> Randomized with seed 11142
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern spec/\{\*_spec.rb,factory_bot/\*\*/\*_spec.rb\} --format
> documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-factory-bot/ruby-factory-bot_6.2.0-2+rebuild1663007590_amd64-2022-09-12T18:33:11Z.build
To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-factory-bot
Source-Version: 6.2.1-1
Done: Georg Faerber
We believe that the bug you reported is fixed in the latest version of
ruby-factory-bot, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Georg Faerber (supplier of updated ruby-factory-bot 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: Sat, 22 Oct 2022 15:46:36 +
Source: ruby-factory-bot
Architecture: source
Version: 6.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Georg Faerber
Closes: 1019622
Changes:
ruby-factory-bot (6.2.1-1) unstable; urgency=medium
.
* New upstream release.
* debian/control:
- Bump Standards-Version to 4.6.1, no changes required.
* debian/patches:
- Add patch to skip failing test. (Closes: #1019622)
Checksums-Sha1:
3f99a9d87356838556058491b1601fc72f591dd7 1556 ruby-factory-bot_6.2.1-1.dsc
32a77c06a46deaf5212c7f246eb5bcbe448e11df 80531
ruby-factory-bot_6.2.1.orig.tar.gz
e006951ae7a09aa5a18c64887b4e5e93913e18be 4024
ruby-factory-bot_6.2.1-1.debian.tar.xz
7cd6df717cb8fe2933756a902990a2aed96a97d5 9274
ruby-factory-bot_6.2.1-1_am
Bug#1009031: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0
Control: tags -1 patch
Hi,
Taking the approach of refreshing the test suite to match the
output produced by the new libgit2 seems to do the job to
address the test suite failure. I also checked this has no
adverse effects on reverse dependencies. Variations between the
reference and the new update are also minimal and seem to make
sense.
It would be welcome if someone else could have a look; maybe
there are breakages I haven't seen. Also, upstream gave the
impression that changes were maybe not that obvious, in which
case it would be better to wait for an upcoming module version,
compatible with the current libgit2 hopefully.
In hope this helps,
--
Étienne Mollier
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/4, please excuse my verbosity.
Description: update test suite expectations to match libgit2 behavior.
Author: Étienne Mollier
Bug: https://github.com/jacquesg/p5-Git-Raw/issues/222
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009031
Last-Update: 2022-10-22
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- libgit-raw-perl.orig/t/02-commit.t
+++ libgit-raw-perl/t/02-commit.t
@@ -296,7 +296,7 @@
$expected_patch = qq{
From $commit2_id Mon Sep 17 00:00:00 2001
From: Git::Raw author
-Subject: second commit
+Subject: [1/2] second commit
---
test2 | 1 +
--- libgit-raw-perl.orig/t/15-merge.t
+++ libgit-raw-perl/t/15-merge.t
@@ -238,7 +238,7 @@
$index -> write;
my $merge_msg = $repo -> message();
-is $merge_msg, "Merge branch 'branch2'\n\nConflicts:\n\ttest1\n";
+is $merge_msg, "Merge branch 'branch2'\n\n#Conflicts:\n#\ttest1\n";
my $target = $master -> target;
$commit = $repo -> commit("Merge commit!", $me, $me, [$target, $commit2],
signature.asc
Description: PGP signature
Processed: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0
Processing control commands: > tags -1 patch Bug #1009031 [libgit-raw-perl] libgit-raw-perl: FTBFS with libgit2 1.3.0 Added tag(s) patch. -- 1009031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1022233
Processing commands for cont...@bugs.debian.org: > affects 1022233 rsass Bug #1022233 [librust-tracing-subscriber-dev] librust-tracing-subscriber-dev: impossible to install Added indication that 1022233 affects rsass > thanks Stopping processing here. Please contact me if you need assistance. -- 1022233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022247: scummvm FTBFS with fonts-mplus 063+git20221017+ds-1
Source: scummvm
Version: 2.6.0+dfsg-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian Fonts Task Force , Gürkan
Myczko
https://buildd.debian.org/status/fetch.php?pkg=scummvm&arch=amd64&ver=2.6.0%2Bdfsg-1%2Bb1&stamp=1666456981&raw=0
...
debian/rules execute_before_dh_auto_build
make[1]: Entering directory '/<>'
for F in gui/themes/*/Free*.ttf; do cp -v
/usr/share/fonts/truetype/freefont/${F##*/} ${F%/*}; done
'/usr/share/fonts/truetype/freefont/FreeMonoBold.ttf' ->
'gui/themes/fonts/FreeMonoBold.ttf'
'/usr/share/fonts/truetype/freefont/FreeSans.ttf' ->
'gui/themes/fonts/FreeSans.ttf'
'/usr/share/fonts/truetype/freefont/FreeSansBold.ttf' ->
'gui/themes/fonts/FreeSansBold.ttf'
for F in gui/themes/*/mplus*.ttf; do cp -v
/usr/share/fonts/truetype/mplus/${F##*/} ${F%/*}; done
cp: cannot stat '/usr/share/fonts/truetype/mplus/mplus-2c-regular.ttf': No such
file or directory
make[1]: *** [debian/rules:44: execute_before_dh_auto_build] Error 1
Bug#1005414: Modules fail to build for Linux 5.11 onward
Package: cloop-src
Version: 3.14.1.3
Followup-For: Bug #1005414
X-Debbugs-Cc: witold.bary...@gmail.com
Any updates? There is a patch.
https://debian-knoppix.alioth.debian.org/packages/cloop/ doesn't work,
but you can find it in /usr/src on CD images:
http://ftp.uni-kl.de/pub/linux/knoppix/KNOPPIX_V9.1CD-2021-01-25-EN.iso
DEV=$(sudo losetup -P -f --show KNOPPIX_V9.1CD-2021-01-25-DE.iso)
sudo mkdir /mnt/knoppix
sudo mount "${DEV}p2" /mnt/knoppix
(requires reiserfs available in the kernel to mount it).
Maybe migrating from m-i to dkms is also something to think about.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-rc5 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP
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)
Versions of packages cloop-src depends on:
ii debhelper 13.10
ii module-assistant 0.11.11
ii xz-utils 5.2.5-2.1
cloop-src recommends no packages.
cloop-src suggests no packages.
-- no debconf information
Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)
On Fri, Oct 07, 2022 at 02:16:35PM -0300, Antonio Terceiro wrote: >... > But nothing in ruby-ahoy-email codebase uses net/smtp explicitly, so > this is a bit weird. Our version is also quite outated wrt upstream, so > my first attempt would be to just update the latest upstream (there are > no reverse dependencies in the archive). That was also my first attempt, and I would have NMUed if it had worked instead of asking you. Unfortunately it doesn't get very far: /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/resolver.rb:271:in `block in verify_gemfile_dependencies_are_found!': Could not find gem 'actionmailer (~> 7.0.0)' in locally installed gems. (Bundler::GemNotFound) cu Adrian
Bug#1022250: qtox: AppArmor profile breaks qTox under NVIDIA propiertary drivers
Package: qtox Version: 1.17.6-0.1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, After upgrading to nvidia-tesla-470-driver, qTox fails to start. See https://github.com/qTox/qTox/pull/ for more details. Marked as grave as AppArmor profile for qTox is enabled by default. Please consider applying patch in referenced pull request. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qtox depends on: ii libavcodec59 7:5.1.2-1 ii libavdevice597:5.1.2-1 ii libavformat597:5.1.2-1 ii libavutil57 7:5.1.2-1 ii libc62.35-3 ii libexif120.6.24-1+b1 ii libkf5sonnetui5 5.98.0-1 ii libopenal1 1:1.19.1-2 ii libqrencode4 4.1.1-1 ii libqt5core5a 5.15.6+dfsg-2 ii libqt5gui5 5.15.6+dfsg-2 ii libqt5network5 5.15.6+dfsg-2 ii libqt5svg5 5.15.6-2 ii libqt5widgets5 5.15.6+dfsg-2 ii libqt5xml5 5.15.6+dfsg-2 ii libsodium23 1.0.18-1 ii libsqlcipher03.4.1-2+b1 ii libstdc++6 12.2.0-7 ii libswscale6 7:5.1.2-1 ii libtoxcore2 0.2.18-1 ii libx11-6 2:1.8.1-2 ii libxss1 1:1.2.3-1 qtox recommends no packages. qtox suggests no packages. -- no debconf information
Bug#1022250: qtox: AppArmor profile breaks qTox under NVIDIA propiertary drivers
Workaround is to import nvidia abstraction into local include file you can create: ``` $ cat /etc/apparmor.d/local/usr.bin.qtox include ```
Bug#1019682: [DRE-maint] Bug#1019682: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty
Control: tags -1 + help Hi Antonio, all, Thanks for your report. I had a look, and I'm able to reproduce locally if building the package, although so far I haven't been able to find out what is causing this. I would be happy if someone is able to support me in debugging this. Looking at [1], which fails in the same way, I noticed: Ignoring bcrypt-3.1.17 because its extensions are not built. Try: gem pristine bcrypt --version 3.1.17 Ignoring charlock_holmes-0.7.7 because its extensions are not built. Try: gem pristine charlock_holmes --version 0.7.7 Ignoring debug-1.4.0 because its extensions are not built. Try: gem pristine debug --version 1.4.0 Ignoring rbs-2.1.0 because its extensions are not built. Try: gem pristine rbs --version 2.1.0 Ignoring sdbm-1.0.0 because its extensions are not built. Try: gem pristine sdbm --version 1.0.0 Ignoring thin-1.8.0 because its extensions are not built. Try: gem pristine thin --version 1.8.0 Ignoring bcrypt-3.1.17 because its extensions are not built. Try: gem pristine bcrypt --version 3.1.17 Ignoring charlock_holmes-0.7.7 because its extensions are not built. Try: gem pristine charlock_holmes --version 0.7.7 Ignoring debug-1.4.0 because its extensions are not built. Try: gem pristine debug --version 1.4.0 Ignoring rbs-2.1.0 because its extensions are not built. Try: gem pristine rbs --version 2.1.0 Ignoring sdbm-1.0.0 because its extensions are not built. Try: gem pristine sdbm --version 1.0.0 Ignoring thin-1.8.0 because its extensions are not built. Try: gem pristine thin --version 1.8.0 Some of these are direct dependencies of Schleuder. I'm mentioning this, because some days ago, [2] reported different errors: Failure/Error: require 'thin' LoadError: cannot load such file -- thin To make all of this even more interesting: [3] reports no errors. I'm wondering if different build environments are of relevance here. Any clue, anyone? Thanks in advance, all the best, Georg [1] https://buildd.debian.org/status/fetch.php?pkg=schleuder&arch=all&ver=4.0.3-4.1&stamp=1666457954&raw=0 [2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/schleuder.html [3] https://ci.debian.net/data/autopkgtest/unstable/amd64/s/schleuder/27432900/log.gz
Processed: Re: [DRE-maint] Bug#1019682: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty
Processing control commands: > tags -1 + help Bug #1019682 [src:schleuder] schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty Added tag(s) help. -- 1019682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022253: swi-prolog breaks logol autopkgtest on s390x
Source: swi-prolog, logol Control: found -1 swi-prolog/8.4.3+dfsg-2 Control: found -1 logol/1.7.9+dfsg-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of swi-prolog the autopkgtest of logol fails in testing when that autopkgtest is run with the binary packages of swi-prolog from unstable. It passes when run with only packages from testing. In tabular form: passfail swi-prolog from testing8.4.3+dfsg-2 logol from testing1.7.9+dfsg-5 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that the last changelog for swi-prolog mentions endianness, s390x is our only big endian release architecture. Currently this regression is blocking the migration of swi-prolog 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=swi-prolog https://ci.debian.net/data/autopkgtest/testing/s390x/l/logol/27384041/log.gz calling logol with parameters -g 1799.logol -s 1799.fasta -dna log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /var/log/logol/logol.log (Permission denied) at java.base/java.io.FileOutputStream.open0(Native Method) at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298) at java.base/java.io.FileOutputStream.(FileOutputStream.java:237) at java.base/java.io.FileOutputStream.(FileOutputStream.java:158) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) at org.apache.log4j.LogManager.(LogManager.java:127) at org.apache.log4j.Logger.getLogger(Logger.java:117) at org.irisa.genouest.logol.Logol.(Unknown Source) For help, use option -h INFO org.irisa.genouest.logol.Logol - Using configuration file: /usr/share/logol/prolog/logol.properties INFO org.irisa.genouest.logol.Logol - option g called with 1799.logol INFO org.irisa.genouest.logol.Logol - option s called with 1799.fasta INFO org.irisa.genouest.logol.Logol - No maximum solutions defined, using defaults INFO org.irisa.genouest.logol.Logol - option dna called INFO org.irisa.genouest.logol.Logol - Start analyse to create grammar analyser Executing prolog for pre-analyse java.io.FileNotFoundException: /tmp/1799.logol.f7104ea4-749d-45b1-8375-321313c4c203.pre.res (No such file or directory) at java.base/java.io.FileInputStream.open0(Native Method) at java.base/java.io.FileInputStream.open(FileInputStream.java:219) at java.base/java.io.FileInputStream.(FileInputStream.java:157) at java.base/java.io.FileReader.(FileReader.java:75) at org.irisa.genouest.logol.Logol.loadVariables2Postpone(Unknown Source) at org.irisa.genouest.logol.Logol.generatePreAnalysis(Unknown Source) at org.irisa.genouest.logol.Logol.analyse(Unknown Source) at org.irisa.genouest.logol.Logol.execute(Unknown Source) at org.irisa.genouest.logol.Logol.main(Unknown Source) INFO org.irisa.genouest.logol.Logol - Analyse in progress.. WARN org.irisa.genouest.logol.SequenceAnalyser - Path to suffix search tool is not set in system environment. Will try to execute directly but may fail if not in PATH of current user ERROR org.irisa.genouest.logol.SequenceAnalyser - Program exited with wrong status code: 134 Exception in thread "main" org.irisa.genouest.logol.GrammarException: ERROR: Coudld not execute program: Program exited with wrong status code at org.irisa.genouest.logol.Logol.execute(Unknown Source) at org.irisa.genouest.logol.Logol.main(Unknown Source) autopkgtest [00:56:16]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Processed: swi-prolog breaks logol autopkgtest on s390x
Processing control commands: > found -1 swi-prolog/8.4.3+dfsg-2 Bug #1022253 [src:swi-prolog, src:logol] swi-prolog breaks logol autopkgtest on s390x Marked as found in versions swi-prolog/8.4.3+dfsg-2. > found -1 logol/1.7.9+dfsg-5 Bug #1022253 [src:swi-prolog, src:logol] swi-prolog breaks logol autopkgtest on s390x Marked as found in versions logol/1.7.9+dfsg-5. -- 1022253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated
Processing control commands: > found -1 eclib/20221012-1 Bug #1022254 [src:eclib, src:sagemath] eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated Marked as found in versions eclib/20221012-1. > found -1 sagemath/9.5-4 Bug #1022254 [src:eclib, src:sagemath] eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated Marked as found in versions sagemath/9.5-4. -- 1022254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-xarray breaks satpy autopkgtest
Processing control commands: > found -1 python-xarray/2022.10.0-1 Bug #1022255 [src:python-xarray, src:satpy] python-xarray breaks satpy autopkgtest Marked as found in versions python-xarray/2022.10.0-1. > found -1 satpy/0.37.1-1 Bug #1022255 [src:python-xarray, src:satpy] python-xarray breaks satpy autopkgtest Marked as found in versions satpy/0.37.1-1. -- 1022255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022254: eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated
Source: eclib, sagemath
Control: found -1 eclib/20221012-1
Control: found -1 sagemath/9.5-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of eclib the autopkgtest of sagemath fails in
testing when that autopkgtest is run with the binary packages of eclib
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
eclib from testing20221012-1
sagemath from testing9.5-4
versioned deps [0] from testingfrom unstable
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 eclib 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
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
eclib/20221012-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=eclib
https://ci.debian.net/data/autopkgtest/testing/i386/s/sagemath/27387916/log.gz
**
File "sage/src/sage/tests/cmdline.py", line 292, in
sage.tests.cmdline.test_executable
Failed example:
print(out)
Expected:
499500
Got:
**
File "sage/src/sage/tests/cmdline.py", line 297, in
sage.tests.cmdline.test_executable
Failed example:
ret
Expected:
0
Got:
1
**
File "sage/src/sage/tests/cmdline.py", line 300, in
sage.tests.cmdline.test_executable
Failed example:
print(out)
Expected:
499500
Got:
**
File "sage/src/sage/tests/cmdline.py", line 304, in
sage.tests.cmdline.test_executable
Failed example:
ret
Expected:
0
Got:
1
**
File "sage/src/sage/tests/cmdline.py", line 467, in
sage.tests.cmdline.test_executable
Failed example:
out.find("555906056623") >= 0
Expected:
True
Got:
False
**
File "sage/src/sage/tests/cmdline.py", line 469, in
sage.tests.cmdline.test_executable
Failed example:
err
Expected:
''
Got:
'/usr/bin/sage: line 629: exec: ipython3: not found\n'
**
File "sage/src/sage/tests/cmdline.py", line 471, in
sage.tests.cmdline.test_executable
Failed example:
ret
Expected:
0
Got:
127
**
File "sage/src/sage/tests/cmdline.py", line 491, in
sage.tests.cmdline.test_executable
Failed example:
print(err)
Expected:
Cython (http://cython.org) is a compiler for code written in the
Cython language. Cython is based on Pyrex by Greg Ewing.
...
Got:
/usr/bin/sage: line 643: exec: cython: not found
**
File "sage/src/sage/tests/cmdline.py", line 570, in
sage.tests.cmdline.test_executable
Failed example:
out.find("Maxima ") >= 0
Expected:
True
Got:
False
**
File "sage/src/sage/tests/cmdline.py", line 572, in
sage.tests.cmdline.test_executable
Failed example:
err
Expected:
''
Got:
'/usr/bin/sage: line 697: exec: maxima: not found\n'
**
File "sage/src/sage/tests/cmdline.py", line 574, in
sage.tests.cmdline.test_executable
Failed example:
ret
Expected:
0
Got:
127
**
1 item had failures:
11 of 207 in sage.tests.cmdline.test_executable
[206 tests, 11 failures, 53.64 s]
sage -t --random-seed=293877373294513721178142072703805930767
sage/src/sage/tests/gosper-sum.py
[100 tests, 35.58 s]
sage -t --random-seed=293877373294513721178142072703805930767
sage/src/sage/tests/lazy_imports.py
[5 tests, 4.89 s]
sage -t --random-seed=293877373294513721178142072703805930767
sage/src/sage/tests/modular_group_cohomology.py
[0 tests, 0.00 s]
sage -t --random-seed=293877373294513721178142072703805930767
sage/src/sage/tests/numpy.py
[6 tests, 0.01 s]
sage -t --random-seed=2938773732945137211781420727
Bug#1004634: A way to include openscenegraph in bookworm?
Hi, I think it would be a pity to release bookworm without openscenegraph, also because there a quite a lot of reverse dependencies. Unfortunately, there hasn't been much progress yet, and the freeze is coming nearer. I've just spotted how Ubuntu solved this: https://launchpad.net/ubuntu/+source/openscenegraph/3.6.5+dfsg1-7ubuntu1 They disabled ffmpeg support, so that the package can be included in their release, albeit with fewer features. Would that be a solution for Debian as well? IMHO, we could drop the support for ffmpeg now, upload the reduced version and allow all dependencies to migrate to testing again. *If* there is a patch available in time for ffmpeg support, we can still upload that version for bookworm. What do you think? Regards, Tobias OpenPGP_signature Description: OpenPGP digital signature
Bug#1022255: python-xarray breaks satpy autopkgtest
Source: python-xarray, satpy
Control: found -1 python-xarray/2022.10.0-1
Control: found -1 satpy/0.37.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-xarray the autopkgtest of satpy fails in
testing when that autopkgtest is run with the binary packages of
python-xarray from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
python-xarray from testing2022.10.0-1
satpy from testing0.37.1-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 of python-xarray 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-xarray
https://ci.debian.net/data/autopkgtest/testing/amd64/s/satpy/27389134/log.gz
TestNIRReflectance.test_no_sunz_no_co2
self = testMethod=test_no_sunz_no_co2>
calculator =
apply_modifier_info = id='139765627664464'>
sza =
@mock.patch('satpy.modifiers.spectral.sun_zenith_angle')
@mock.patch('satpy.modifiers.NIRReflectance.apply_modifier_info')
@mock.patch('satpy.modifiers.spectral.Calculator')
def test_no_sunz_no_co2(self, calculator, apply_modifier_info, sza):
"""Test NIR reflectance compositor with minimal parameters."""
calculator.return_value = mock.MagicMock(
reflectance_from_tbs=self.refl_from_tbs)
sza.return_value = self.da_sunz
from satpy.modifiers.spectral import NIRReflectance
comp = NIRReflectance(name='test')
info = {'modifiers': None}
res = comp([self.nir, self.ir_], optional_datasets=[], **info)
> self.get_lonlats.assert_called()
/usr/lib/python3/dist-packages/satpy/tests/test_modifiers.py:244: _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
def assert_called(self):
"""assert that the mock was called at least once
"""
if self.call_count == 0:
msg = ("Expected '%s' to have been called." %
(self._mock_name or 'mock'))
raise AssertionError(msg)
E AssertionError: Expected 'get_lonlats' to have been called.
/usr/lib/python3.10/unittest/mock.py:888: AssertionError
___ TestSceneLoading.test_load_comp4
___
self =
def test_load_comp4(self):
"""Test loading a composite that depends on a composite."""
scene = Scene(filenames=['fake1_1.txt'], reader='fake1')
scene.load(['comp4'])
loaded_ids = list(scene._datasets.keys())
assert len(loaded_ids) == 1
E AssertionError: assert 2 == 1
E+ where 2 = len([DataID(name='comp2'), DataID(name='ds3',
modifiers=())])
/usr/lib/python3/dist-packages/satpy/tests/test_scene.py:1059:
AssertionError
-- Captured log call
---
WARNING satpy.scene:scene.py:1275 The following datasets were not
created and may require resampling to be generated: DataID(name='comp4')
___ TestSceneLoading.test_load_multiple_resolutions
self =
def test_load_multiple_resolutions(self):
"""Test loading a dataset has multiple resolutions available
with different resolutions."""
scene = Scene(filenames=['fake1_1.txt'], reader='fake1')
comp25 = make_cid(name='comp25', resolution=1000)
scene[comp25] = xr.DataArray([], attrs={'name': 'comp25',
'resolution': 1000})
scene.load(['comp25'], resolution=500)
loaded_ids = list(scene._datasets.keys())
assert len(loaded_ids) == 2
E AssertionError: assert 3 == 2
E+ where 3 = len([DataID(name='comp24', resolution=500),
DataID(name='comp25', resolution=1000), DataID(name='ds5',
resolution=500, modifiers=())])
/usr/lib/python3/dist-packages/satpy/tests/test_scene.py:1070:
AssertionError
-- Captured log call
---
WARNING satpy.scene:scene.py:1275 The following datasets were not
created and may require resampling to be generated: DataID(name='comp25')
_ TestSceneLoading.test_load_same_subcomposite
_
self =
def test_load_same_subcomposite(self):
"""Test loading a composite and one of it's subcomposites at
the same time."""
scene = Scene(filenames=['fake1_1.txt'], reader='fake1')
scene.load(['comp24', 'comp25'], resolution=500)
Processed: Re: eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated
Processing control commands: > retitle 1022254 sagemath autopkgtest regressed Bug #1022254 [src:eclib, src:sagemath] eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated Changed Bug title to 'sagemath autopkgtest regressed' from 'eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated'. > reassign 1022254 src:sagemath 9.5-4 Bug #1022254 [src:eclib, src:sagemath] sagemath autopkgtest regressed Bug reassigned from package 'src:eclib, src:sagemath' to 'src:sagemath'. No longer marked as found in versions sagemath/9.5-4 and eclib/20221012-1. Ignoring request to alter fixed versions of bug #1022254 to the same values previously set Bug #1022254 [src:sagemath] sagemath autopkgtest regressed Marked as found in versions sagemath/9.5-4. -- 1022254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022254: eclib breaks sagemath autopkgtest on i386: Error: 363 tests failed, up to 100 failures are tolerated
Control: retitle 1022254 sagemath autopkgtest regressed Control: reassign 1022254 src:sagemath 9.5-4 On Sat, 22 Oct 2022 21:35:11 +0200 Paul Gevers wrote: With a recent upload of eclib the autopkgtest of sagemath fails in testing when that autopkgtest is run with the binary packages of eclib from unstable. It passes when run with only packages from testing. In tabular form: Turns out that sagemath regressed on amd64, and arm64 regressed in testing. I assume i386 will show the same once the reference run finishes. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#937234: marked as done (pam-python: Python2 removal in sid/bullseye)
Your message dated Sat, 22 Oct 2022 23:50:56 + with message-id and subject line Bug#937234: fixed in pam-python 1.1.0~git20220701.1d4e111-0.1 has caused the Debian Bug report #937234, regarding pam-python: Python2 removal in sid/bullseye 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.) -- 937234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pam-python Version: 1.0.6-1.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pam-python If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pam-python Source-Version: 1.1.0~git20220701.1d4e111-0.1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of pam-python, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated pam-python 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, 23 Oct 2022 01:26:40 +0200 Source: pam-python Architecture: source Version: 1.1.0~git20220701.1d4e111-0.1 Distribution: unstable Urgency: medium Maintainer: Russell Stuart Changed-By: Mike Gabriel Closes: 937234 Changes: pam-python (1.1.0~git20220701.1d4e111-0.1) unstable; urgency=medium . * Non-maintainer upload. . * New Git snapshot from @Ionic providing Python3 support. (Closes: #937234). * debian/patches: + Add 000[2-8]_*.patch: Various patches from upstream Git (still pending submission). Rename intersphinx-localmapping.diff to 2001_intersphinx-localmapping.patch. + Rebase 2001_intersphinx-localmapping.patch against upstream version bump patch. * debian/watch: + Obtain Git snapshot from gh/Ionic/pam-python, branch feature/py3. * debian/source.lintian-overrides: + Drop sourceforce related override. * debian/copyrig
Processed: Bug#1021895 marked as pending in pylint
Processing control commands: > tag -1 pending Bug #1021895 [pylint] pylint: fails to honor "--" argument Added tag(s) pending. -- 1021895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021895: marked as pending in pylint
Control: tag -1 pending Hello, Bug #1021895 in pylint 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/pylint/-/commit/342925346c5c7bcfdaf48520d94eebd694f4963b New upstream release; Closes: #1021895 (this message was generated automatically) -- Greetings https://bugs.debian.org/1021895
Bug#1021895: marked as done (pylint: fails to honor "--" argument)
Your message dated Sun, 23 Oct 2022 00:50:46 + with message-id and subject line Bug#1021895: fixed in pylint 2.15.5-1 has caused the Debian Bug report #1021895, regarding pylint: fails to honor "--" argument 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.) -- 1021895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pylint Version: 2.15.3-1 Severity: serious Tags: patch X-Debbugs-Cc: mo...@debian.org Hi, It seems that the new version of pylint does not honor the "--" arg. In particular, if you notice the autopkgtest for ionit[1] it fails with: /usr/bin/python3 -m pylint --rcfile=/tmp/autopkgtest-lxc.2tqox33y/downtmp/build.geB/src/tests/pylint.conf -- /usr/bin/ionit tests /usr/lib/python3/dist-packages/ionit_plugin.py setup.py [...] AssertionError: pylint found issues: * Module -- --:1:0: F0001: No module named -- (fatal) This seems to have been fixed upstream already in this commit[2]. Please - either apply this or upgrade to latest upstream (which is just one patch release later). [1]: https://ci.debian.net/data/autopkgtest/testing/amd64/i/ionit/27128934/log.gz [2]: https://github.com/PyCQA/pylint/commit/43ecd7dbf34d9a4ed0e3085a9c6e047a8326e131 Thanks, Nilesh -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pylint depends on: ii python3 3.10.6-1 pn python3-astroid pn python3-isort pn python3-logilab-common pn python3-mccabe ii python3-platformdirs2.5.2-1 ii python3-setuptools 59.6.0-1.2 ii python3-toml0.10.2-1 Versions of packages pylint recommends: ii python3-tk 3.10.7-1 Versions of packages pylint suggests: pn pylint-doc --- End Message --- --- Begin Message --- Source: pylint Source-Version: 2.15.5-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of pylint, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pylint 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: Sat, 22 Oct 2022 20:27:36 -0400 Source: pylint Architecture: source Version: 2.15.5-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1021895 Changes: pylint (2.15.5-1) unstable; urgency=medium . * New upstream release; Closes: #1021895 * debian/control - bump b-d on astroid to >= 2.12.12 Checksums-Sha1: f55c2311e615a5e576989c07e14bbdf58a0019ad 2401 pylint_2.15.5-1.dsc a14f279249153e799c0cb3c2861c1a5964fdbc46 972672 pylint_2.15.5.orig.tar.xz ebb0a46a6cf39c27373df4d52507742e49ff4d7c 24296 pylint_2.15.5-1.debian.tar.xz 580d9cc08d20d904299b6bc6b2b4143aec298c29 9497 pylint_2.15.5-1_source.buildinfo Checksums-Sha256: 591f6328cb8f8f177d72bb1c27f90cbf26a828df3c1a8b1d73eba51e8df56b8e 2401 pylint_2.15.5-1.dsc cb8ed5c7d3424d053952ea47a54c09cc7b45ba7062f9124560cb6180616aa94f 972672 pylint_2.15.5.orig.tar.xz 5a9c4b505a4d57feaf5d2ddcd9299506ff18406fe5b919f2bde6546f8623c11d 24296 pylint_2.15.5-1.debian.tar.xz e5814b63cdb1b68f8efbfda685bd3033c0f4a50bce1c9add5e0f6889486d3de5 9497 pylint_2.15.5-1_source.buildinfo Files: 2d22fa2aff7960a075886a220b8e3473 2401 python optional pylint_2.15.5-1.dsc d37b1c124c5eb0c6f32ca9ddea361c80 972672 python optional pylint_2.15.5.orig.tar.xz 538a2e28a7603b5fea6652e71f996ed4 24296 python optional pylint_2.15.5-1.debian.tar.xz 0c76911cde4bb5f6c3ba185bfe17871d 9497 python optional pylint_2.15.5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmNUirkACgkQh588mTgB qU/ZLg/9E/VDkSk++4/BK8qVlFXtUjXNiNZUM8ZWLPBLtSRt/V2aqH8JdUiHUsB7 GP9gn3cqkwh+IHvIhZbHSsgwiY
Processed: unattended-upgrades: diff for NMU version 2.9.1+nmu2
Processing control commands: > tags 1020150 + patch Bug #1020150 [src:unattended-upgrades] unattended-upgrades: FTBFS: make[1]: *** [debian/rules:33: override_dh_auto_clean] Error 1 Added tag(s) patch. > tags 1020150 + pending Bug #1020150 [src:unattended-upgrades] unattended-upgrades: FTBFS: make[1]: *** [debian/rules:33: override_dh_auto_clean] Error 1 Added tag(s) pending. -- 1020150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020150: unattended-upgrades: diff for NMU version 2.9.1+nmu2
Control: tags 1020150 + patch
Control: tags 1020150 + pending
X-Debbugs-CC: Michael Vogt
Dear maintainer,
I've prepared an NMU for unattended-upgrades (versioned as 2.9.1+nmu2) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru unattended-upgrades-2.9.1+nmu1/debian/changelog unattended-
upgrades-2.9.1+nmu2/debian/changelog
--- unattended-upgrades-2.9.1+nmu1/debian/changelog 2022-10-15
06:54:44.0 -0400
+++ unattended-upgrades-2.9.1+nmu2/debian/changelog 2022-10-22
21:28:14.0 -0400
@@ -1,3 +1,11 @@
+unattended-upgrades (2.9.1+nmu2) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * setup.py: Disable automatic package discovery by setting py_modules
+to empty. (Closes: #1020150)
+
+ -- Boyuan Yang Sat, 22 Oct 2022 21:28:14 -0400
+
unattended-upgrades (2.9.1+nmu1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru unattended-upgrades-2.9.1+nmu1/setup.py unattended-upgrades-
2.9.1+nmu2/setup.py
--- unattended-upgrades-2.9.1+nmu1/setup.py 2022-07-21
08:25:14.0 -0400
+++ unattended-upgrades-2.9.1+nmu2/setup.py 2022-10-22
21:28:14.0 -0400
@@ -38,4 +38,5 @@
cmdclass={"build": build_extra.build_extra,
"build_i18n": build_i18n.build_i18n},
test_suite="test",
+py_modules=[],
)
signature.asc
Description: This is a digitally signed message part
Bug#1022250: qtox: AppArmor profile breaks qTox under NVIDIA propiertary drivers
Control: severity -1 normal Remark as normal, since it's related to non-free software.
Processed: Re: Bug#1022250: qtox: AppArmor profile breaks qTox under NVIDIA propiertary drivers
Processing control commands: > severity -1 normal Bug #1022250 [qtox] qtox: AppArmor profile breaks qTox under NVIDIA propiertary drivers Severity set to 'normal' from 'grave' -- 1022250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021923: marked as done (ionit: FTBFS dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13)
Your message dated Sun, 23 Oct 2022 09:16:27 +0530
with message-id <4f5a5092-7dbd-47cd-93d6-96b74afb8...@debian.org>
and subject line Re: ionit: FTBFS dh_auto_test: error: pybuild --test -i
python{version} -p 3.10 returned exit code 13
has caused the Debian Bug report #1021923,
regarding ionit: FTBFS dh_auto_test: error: pybuild --test -i python{version}
-p 3.10 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.)
--
1021923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ionit
Version: 0.5.0-1
Severity: serious
Tags: ftbfs
ionit FTBFS in unstable
test_pylint (tests.test_pylint.PylintTestCase)
Test: Run pylint on Python source code. ... Running following command:
/usr/bin/python3.10 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/ionit tests ionit_plugin.py /<>/setup.py
FAIL
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module --
--:1:0: F0001: No module named -- (fatal)
--
Ran 32 tests in 7.529s
FAILED (failures=1)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.10/build; python3.10 -m unittest discover
-v -s /<>
dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit
code 13
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
Full build log available at
https://buildd.debian.org/status/fetch.php?pkg=ionit&arch=all&ver=0.5.0-1.1&stamp=1665834431&raw=0
--- End Message ---
--- Begin Message ---
On Mon, 17 Oct 2022 15:59:20 +0200 Michael Biebl wrote:
> Am 17.10.22 um 15:33 schrieb Nilesh Patra:
> > affects 1021895 src:ionit
> > close 1021923
> > stop
> >
> > Hi Michael,
> >
> > On Mon, 17 Oct 2022 13:56:40 +0200 Michael Biebl wrote:
> >> Source: ionit
> >> Version: 0.5.0-1
> >> Severity: serious
> >> Tags: ftbfs
> >>
> >> ionit FTBFS in unstable
> >>
> >>
> >> test_pylint (tests.test_pylint.PylintTestCase)
> >> Test: Run pylint on Python source code. ... Running following command:
> >> [...]
> >
> > This FTBFS occurs due to a bug in pylint which has been fixed upstream and
> > needs
> > fixing at debian end.
> > I'll team-upload the fix in a week if no activity happens from maintainer's
> > end.
> >
> > I am closing your bug.
> >
> Could we keep it open and block this bug by 1021895?
> I.e. only close it once pylint has actually been fixed.
> This makes it a bit easier to track progress.
ionit builds now with new pylint, closing.
https://buildd.debian.org/status/fetch.php?pkg=ionit&arch=all&ver=0.5.0-1.1&stamp=1666489880&raw=0
Best,
Nilesh --- End Message ---
