Bug#1021790: src:graphicsmagick: fails to migrate to testing for too long: FTBFS on mips64el

[GCS]

Hi,

On Sat, Oct 15, 2022 at 10:15 PM Marti Maria  wrote:
> Final 2.14 release  is expected on end of October-22. I moved from November 
> to October because the Debian maintainer request.
 For the record, someone found the real reason. As I understand it, it
was a GCC 11 miscompilation of lcms2. Someone in the background
scheduled it to rebuild with the message: "Rebuild with GCC 12 for
apparent misbuild on mips64el with GCC 11". Then the build of
GraphicsMagick was successful even on mips64el with the now GCC 12
built lcms2.
In short, there's no rush to release lcms2 v2.14 soon anymore.

Thanks to everyone involved,
Laszlo/GCS

Processed: found 1013009 in 11.0.11+0-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1013009 11.0.11+0-1
Bug #1013009 [src:openjfx] openjfx: ftbfs with GCC-12
Marked as found in versions openjfx/11.0.11+0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1013009

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1013009 + ftbfs
Bug #1013009 [src:openjfx] openjfx: ftbfs with GCC-12
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020434: marked as done (ruby-liquid-c: FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 09:35:10 +0300
with message-id 
and subject line Fixed in 4.1.0-2
has caused the Debian Bug report #1020434,
regarding ruby-liquid-c: FTBFS on ppc64el
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.)


-- 
1020434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-liquid-c
Version: 4.1.0-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=ruby-liquid-c&arch=ppc64el&ver=4.1.0-1&stamp=1663761020&raw=0

┌──┐
│ Run tests for ruby3.0 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=. 
GEM_PATH=/<>/debian/ruby-liquid-c/usr/lib/powerpc64le-linux-gnu/rubygems-integration/3.0.0:/<>/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/powerpc64le-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/powerpc64le-linux-gnu/rubygems-integration/3.0.0
 ruby3.0 debian/ruby-tests.rb
ruby3.0 -w -Itest 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
 test/unit/block_test.rb test/unit/context_test.rb test/unit/expression_test.rb 
test/unit/gc_stress_test.rb test/unit/raw_test.rb 
test/unit/resource_limits_test.rb test/unit/tokenizer_test.rb 
test/unit/variable_test.rb -v
/<>/debian/ruby-liquid-c/usr/lib/powerpc64le-linux-gnu/rubygems-integration/3.0.0/gems/liquid-c-4.0.0/lib/liquid/c.rb:87:
 warning: method redefined; discarding old parse_expression
/usr/share/rubygems-integration/all/gems/liquid-5.4.0/lib/liquid/parse_context.rb:30:
 warning: previous definition of parse_expression was here
:231:in `verify_compaction_references': Compaction isn't available 
on this platform (NotImplementedError)
from /<>/test/test_helper.rb:11:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/unit/block_test.rb:3:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-liquid-c 
returned exit code 1
make: *** [debian/rules:7: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 4.1.0-2

ruby-liquid-c (4.1.0-2) unstable; urgency=medium
...
  * test_helper: skip GC compaction on unsupported platforms.
This fixes the build on ppc64el

 -- Antonio Terceiro   Thu, 22 Sep 2022 18:42:41 -0300--- End Message ---

Processed: bug 1021262 is forwarded to https://github.com/tmm1/stackprof/issues/191

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1021262 https://github.com/tmm1/stackprof/issues/191
Bug #1021262 [src:ruby-stackprof] ruby-stackprof FTBFS on 32bit
Set Bug forwarded-to-address to 'https://github.com/tmm1/stackprof/issues/191'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1008749

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1008749 + bookworm
Bug #1008749 [src:v-sim] v-sim: FTBFS with Python 3.10 due to faulty configure 
parsing
Added tag(s) bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1008749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017136: marked as done (ksirk: FTBFS: newGameDialogImpl.cpp:31:10: fatal error: downloaddialog.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 06:20:10 +
with message-id 
and subject line Bug#1017136: fixed in ksirk 4:22.08.2-1
has caused the Debian Bug report #1017136,
regarding ksirk: FTBFS: newGameDialogImpl.cpp:31:10: fatal error: 
downloaddialog.h: No such file or directory
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.)


-- 
1017136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ksirk
Version: 4:21.08.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/ksirk && /usr/bin/c++ 
> -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING 
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICKWIDGETS_LIB -DQT_QUICK_LIB 
> -DQT_SVG_LIB -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS 
> -DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -I/<>/obj-x86_64-linux-gnu/ksirk -I/<>/ksirk 
> -I/<>/obj-x86_64-linux-gnu/ksirk/ksirk_autogen/include 
> -I/<>/ksirk/./Dialogs -I/<>/ksirk/./GameLogic 
> -I/<>/ksirk/./SaveLoad -I/<>/ksirk/./skins 
> -I/<>/ksirk/./Sprites -I/<>/ksirk/iris/include/iris 
> -I/<>/ksirk/iris/src 
> -I/<>/obj-x86_64-linux-gnu/ksirk/iris/src -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/Qca-qt5/QtCrypto -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/KF5/KCrash 
> -isystem /usr/include/KF5 -isystem /usr/include/KF5/KIOCore -isystem 
> /usr/include/KF5/KIO -isystem /usr/include/KF5/KCoreAddons -isystem 
> /usr/include/KF5/KService -isystem /usr/include/KF5/KConfig -isystem 
> /usr/include/KF5/KConfigCore -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/KF5/KNewStuff3 -isystem /usr/include/KF5/KMoreTools -isystem 
> /usr/include/KF5/Attica -isystem /usr/include/KF5/KXmlGui -isystem 
> /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
> /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KConfigGui -isystem 
> /usr/include/KF5/KAuthWidgets -isystem /usr/include/KF5/KAuthCore -isystem 
> /usr/include/KF5/KAuth -isystem /usr/include/KF5/KWallet -isystem 
> /usr/include/phonon4qt5 -isystem /usr/include/KF5/KF5KDEGames -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuickWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem /usr/include/KF5/KI18n 
> -isystem /usr/include/KF5/KF5KDEGames/libkdegamesprivate -isystem 
> /usr/include/KF5/KCompletion -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fno-operator-names -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self 
> -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fexceptions 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -MD -MT 
> ksirk/CMakeFiles/ksirk.dir/Dialogs/kwaitedplayersetupdialog.cpp.o -MF 
> CMakeFiles/ksirk.dir/Dialogs/kwaitedplayersetupdialog.cpp.o.d -o 
> CMakeFiles/ksirk.dir/Dialogs/kwaitedplayersetupdialog.cpp.o -c 
> /<>/ksirk/Dialogs/kwaitedplayersetupdialog.cpp
> /<>/ksirk/Dialogs/newGameDialogImpl.cpp:31:10: fatal error: 
> downloaddialog.h: No such file or directory
>31 | #include 
>   |  ^~
> compilation terminated.
> make[3]: *** [ksirk/CMakeFiles/ksirk.dir/build.make:618: 
> ksirk/CMakeFiles/ksirk.dir/Dialogs/newGameDialogImpl.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/ksirk_21.08.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewe

Processed: bug 1021316 is forwarded to https://github.com/rust-vmm/kvm-bindings/pull/71

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1021316 https://github.com/rust-vmm/kvm-bindings/pull/71
Bug #1021316 [src:rust-kvm-bindings] rust-kvm-bindings: FTBFS on i386
Set Bug forwarded-to-address to 
'https://github.com/rust-vmm/kvm-bindings/pull/71'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021861: virglrenderer FTBFS on armel

[Adrian Bunk]

Source: virglrenderer
Version: 0.10.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=virglrenderer&arch=armel&ver=0.10.3-1&stamp=1664582880&raw=0

...
FAILED: src/libvirgl.a.p/venus_vkr_context.c.o
cc -Isrc/libvirgl.a.p -Isrc -I../src -I../src/gallium/include 
-I../src/gallium/auxiliary -I../src/gallium/auxiliary/util -I. -I.. 
-I../src/venus -I../src/drm -I../src/drm/drm-uapi -Isrc/mesa -I../src/mesa 
-I../src/mesa/compat -I../src/mesa/pipe -I../src/mesa/util 
-I/usr/include/libdrm -fdiagnostics-color=always -DNDEBUG 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -O0 
-Werror=implicit-function-declaration -Werror=missing-prototypes 
-Wmissing-prototypes -Werror=incompatible-pointer-types 
-Werror=int-to-pointer-cast -Wno-overlength-strings -fvisibility=hidden 
-imacros /<>/obj-arm-linux-gnueabi/config.h -DHAVE_CONFIG_H=1 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libvirgl.a.p/venus_vkr_context.c.o -MF 
src/libvirgl.a.p/venus_vkr_context.c.o.d -o 
src/libvirgl.a.p/venus_vkr_context.c.o -c ../src/venus/vkr_context.c
In file included from ../src/mesa/util/compiler.h:37,
 from ../src/mesa/util/xxhash.h:81,
 from ../src/venus/vkr_context.c:17:
../src/venus/vkr_ring.h:33:1: error: static assertion failed: "vkr_ring_control 
requires lock-free 32-bit atomic_uint"
   33 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == 4,
  | ^
...



Do src/venus/vkr_ring.h and src/proxy/proxy_context.h
really require ATOMIC_INT_LOCK_FREE == 2?

Atomics on armel being implemented with a kernel helper,
which gives only ATOMIC_INT_LOCK_FREE == 1.

If ATOMIC_INT_LOCK_FREE == 2 is really required, then disabling
venus and renderserver on armel should workaround it for now.

Processed: Re: Bug#1019485: libvirglrenderer-dev should depend on libva-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1019485 [libvirglrenderer-dev] libvirglrenderer-dev should depend on 
libva-dev
Severity set to 'serious' from 'important'
> retitle -1 libvirglrenderer-dev must depend on packages required for its 
> pkg-config file
Bug #1019485 [libvirglrenderer-dev] libvirglrenderer-dev should depend on 
libva-dev
Changed Bug title to 'libvirglrenderer-dev must depend on packages required for 
its pkg-config file' from 'libvirglrenderer-dev should depend on libva-dev'.
> affects -1 src:qemu
Bug #1019485 [libvirglrenderer-dev] libvirglrenderer-dev must depend on 
packages required for its pkg-config file
Added indication that 1019485 affects src:qemu
> tags -1 ftbfs
Bug #1019485 [libvirglrenderer-dev] libvirglrenderer-dev must depend on 
packages required for its pkg-config file
Added tag(s) ftbfs.

-- 
1019485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1013576

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1013576 + pending
Bug #1013576 [src:elisa-player] elisa-player: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit 
code 2
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[программист некто]

Output already captured. See 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846  the first message - 
it have an attached files with grub-install output.

Bug#1021859: pgbouncer FTBFS: test failures

[Adrian Bunk]

Source: pgbouncer
Version: 1.17.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pgbouncer&arch=amd64&ver=1.17.0-3%2Bb2&stamp=1665894517&raw=0

...
Sun Oct 16 04:26:31 UTC 2022 running test_show ... FAILED
# => show clients;
#  type |   user| database  | state  | addr | port | local_addr | 
local_port |  connect_time   |  request_time   | wait | wait_us 
| close_needed |  ptr   | link | remote_pid | tls 
# 
--+---+---++--+--+++-+-+--+-+--++--++-
#  C| pgbouncer | pgbouncer | active | unix | 6667 | unix   |   
6667 | 2022-10-16 04:26:31 UTC | 2022-10-16 04:26:31 UTC |0 |   0 | 
   0 | 0x753a27f0 |  |2977531 | 
# (1 row)
# 
# => show config;
# key| value
  |default | changeable 
# 
---+++
#  admin_users   |  
  || yes
#  application_name_add_host | 0
  | 0  | yes
#  auth_file | userlist.txt 
  || yes
#  auth_hba_file |  
  || yes
#  auth_query| SELECT usename, passwd FROM pg_shadow WHERE 
usename=$1 | SELECT usename, passwd FROM pg_shadow WHERE usename=$1 | yes
#  auth_type | trust
  | md5| yes
#  auth_user |  
  || yes
#  autodb_idle_timeout   | 3600 
  | 3600   | yes
#  client_idle_timeout   | 0
  | 0  | yes
#  client_login_timeout  | 60   
  | 60 | yes
#  client_tls_ca_file|  
  || yes
#  client_tls_cert_file  |  
  || yes
#  client_tls_ciphers| fast 
  | fast   | yes
#  client_tls_dheparams  | auto 
  | auto   | yes
#  client_tls_ecdhcurve  | auto 
  | auto   | yes
#  client_tls_key_file   |  
  || yes
#  client_tls_protocols  | secure   
  | secure | yes
#  client_tls_sslmode| disable  
  | disable| yes
#  conffile  | test.ini 
  || yes
#  default_pool_size | 5
  | 20 | yes
#  disable_pqexec| 0
  | 0  | no
#  dns_max_ttl   | 15   
  | 15 | yes
#  dns_nxdomain_ttl  | 15   
  | 15 | yes
#  dns_zone_check_period | 0
  | 0  | yes
#  idle_transaction_timeout  | 0
  | 0  | yes
#  ignore_startup

Bug#1021858: drf-yasg-nonfree: FTBFS: AttributeError: module 'rest_framework.serializers' has no attribute 'NullBooleanField'

[Andreas Beckmann]

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

Bug#1021857: llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.

[Andreas Beckmann]

Package: llvm-14-dev
Version: 1:14.0.6-5
Severity: serious

This is an autopkgtest regression, but also experienced e.g. while
building spirv-llvm-translator-14:

-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test HAVE_FFI_CALL
-- Performing Test HAVE_FFI_CALL - Success
-- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
-- Performing Test Terminfo_LINKABLE
-- Performing Test Terminfo_LINKABLE - Success
-- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) 
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") 
CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message):
  The imported target "sancov" references the file

 "/usr/lib/llvm-14/bin/sancov"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include)
  CMakeLists.txt:3 (find_package)


-- Configuring incomplete, errors occurred!


Andreas

Processed: tagging 1017011

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1017011 + bookworm sid
Bug #1017011 [src:haskell-binary-tagged] Removal notice: obsolete
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1013423

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1013423 + bookworm sid
Bug #1013423 [src:ffmpeg2theora] ffmpeg2theora FTBFS with ffmpeg 5.0.1
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1017493

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1017493 + bookworm sid
Bug #1017493 [src:feedreader] feedreader: Switch to libsoup3
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1013157

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1013157 + bookworm sid
Bug #1013157 [nifti2dicom] nifti2dicom: vtk[6,7] removal
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 958692

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 958692 + bookworm sid
Bug #958692 [node-matrix-js-sdk] node-matrix-js-sdk: Remove dependency to 
node-request
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 1020066 1021706

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1020066 1021706
Bug #1020066 [src:tt-rss] tt-rss: FTBFS: build-dependency not installable: 
libjs-prototype (= 1.7.1-3.1)
Bug #1021706 [src:tt-rss] tt-rss: build dependency missing in testing: 
libjs-prototype (= 1.7.1-3.1)
Added tag(s) bookworm, sid, and ftbfs.
Merged 1020066 1021706
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020066
1021706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 998306 in 0.2.0-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 998306 0.2.0-1
Bug #998306 [dwarf2sources] dwarf2sources FTBFS with rust-object 0.20
Marked as found in versions dwarf2sources/0.2.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
998306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1020576

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020576 + bookworm sid
Bug #1020576 [src:sagemath] please update sage for pari 2.15.0 and gap 4.12.0
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 937569

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 937569 - bullseye
Bug #937569 [src:python2.7] python2.7: Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
937569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 938198

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 938198 - bullseye
Bug #938198 [src:python-stdlib-extensions] python-stdlib-extensions: Python2 
removal in sid/bullseye
Removed tag(s) bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
938198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 938168

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 938168 - bullseye
Bug #938168 [src:python-setuptools] python-setuptools: Python2 removal in 
sid/bullseye
Removed tag(s) bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
938168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1021510

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1021510 + bookworm sid
Bug #1021510 [src:lxqt-qtplugin] lxqt-qtplugin: hardcoded dependencies on 
libfm-qt8
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 937695

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 937695 - bullseye
Bug #937695 [src:python-defaults] python-defaults: Python2 removal in 
sid/bullseye
Removed tag(s) bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
937695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1018197

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1018197 + bookworm sid
Bug #1018197 [src:haskell-cprng-aes] Removal notice: obsolete
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1018197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1018196

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1018196 + bookworm sid
Bug #1018196 [src:haskell-cipher-aes] Removal notice: obsolete
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1018196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1020446

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020446 + bookworm sid
Bug #1020446 [src:gdisk] gdisk: FTBFS with popt 1.19+dfsg-1~exp1
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1019927

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1019927 + bookworm sid
Bug #1019927 [ruby-coffee-script] Remove ruby-coffee-script - deprecated 
upstream
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 958686

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 958686 + bookworm sid
Bug #958686 [node-yarnpkg] node-yarnpkg: Remove dependency to node-request
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1020970

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020970 + bookworm sid
Bug #1020970 [elpa-evil] elpa-evil: fails to install: wrong-number-of-arguments
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1021791

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1021791 + bookworm sid
Bug #1021791 [dbconfig-common] Testsuite needs updated permissions with 
PostgreSQL 15
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020779: slic3r-prusa: FTBFS on 32-bit arches

[Peter Michael Green]

To clarify the situation for people stumbling across this bug.

The issue in cereal was fixed, however slic3r-prusa still FTBFS because of

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021566

Bug#1021854: pgpool2 needs NEW upload for PostgreSQL 15

[Adrian Bunk]

Source: pgpool2
Version: 4.3.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pgpool2&arch=arm64&ver=4.3.3-1%2Bb1&stamp=1665872328&raw=0

...
 debian/rules clean
pg_buildext checkcontrol
--- debian/control  2022-08-31 13:55:08.0 +
+++ debian/control.4BOVht   2022-10-15 22:18:42.679989460 +
@@ -83,17 +83,17 @@
  PostgreSQL database client.  This package contains headers for the pgpool
  control protocol library (libpcp).
 
-Package: postgresql-14-pgpool2
+Package: postgresql-15-pgpool2
 Architecture: linux-any kfreebsd-any
 Depends:
  libpgpool2 (>= ${binary:Version}),
- postgresql-14,
+ postgresql-15,
  ${misc:Depends},
  ${shlibs:Depends},
 Description: connection pool server and replication proxy for PostgreSQL - 
modules
  pgpool-II is a middleware that works between PostgreSQL servers and a
  PostgreSQL database client.  This package contains support modules for
- the PostgreSQL 14 server:
+ the PostgreSQL 15 server:
  .
   * pgpool_adm
   * pgpool_recovery (PostgreSQL 9.1 and above)
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
debian/control] Error 1

Processed: tagging 1013302

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1013302 + ftbfs
Bug #1013302 [ntopng] ntopng FTBFS 
/build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: 
Can't reference 'this' before calling super in derived class constructors
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 1021832 to fastqtl: Missing build dependency on libbz2-dev

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1021832 fastqtl: Missing build dependency on libbz2-dev
Bug #1021832 [src:fastqtl] fastqtl: FTBFS: /usr/bin/ld: cannot find -lbz2: No 
such file or directory
Changed Bug title to 'fastqtl: Missing build dependency on libbz2-dev' from 
'fastqtl: FTBFS: /usr/bin/ld: cannot find -lbz2: No such file or directory'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1014803: marked as done (ruby-yajl: CVE-2022-24795)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 05:06:09 +0300
with message-id 
and subject line Fixed in 1.4.3-1
has caused the Debian Bug report #1014803,
regarding ruby-yajl: CVE-2022-24795
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.)


-- 
1014803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-yajl
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ruby-yajl.

CVE-2022-24795[0]:
| yajl-ruby is a C binding to the YAJL JSON parsing and generation
| library. The 1.x branch and the 2.x branch of `yajl` contain an
| integer overflow which leads to subsequent heap memory corruption when
| dealing with large (~2GB) inputs. The reallocation logic at
| `yajl_buf.c#L64` may result in the `need` 32bit integer wrapping to 0
| when `need` approaches a value of 0x8000 (i.e. ~2GB of data),
| which results in a reallocation of buf->alloc into a small heap
| chunk. These integers are declared as `size_t` in the 2.x branch of
| `yajl`, which practically prevents the issue from triggering on 64bit
| platforms, however this does not preclude this issue triggering on
| 32bit builds on which `size_t` is a 32bit integer. Subsequent
| population of this under-allocated heap chunk is based on the original
| buffer size, leading to heap memory corruption. This vulnerability
| mostly impacts process availability. Maintainers believe exploitation
| for arbitrary code execution is unlikely. A patch is available and
| anticipated to be part of yajl-ruby version 1.4.2. As a workaround,
| avoid passing large inputs to YAJL.

https://github.com/brianmario/yajl-ruby/security/advisories/GHSA-jj47-x69x-mxrm
https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6

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-24795
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24795

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 1.4.3-1

https://github.com/brianmario/yajl-ruby/security/advisories/GHSA-jj47-x69x-mxrm

Affected versions: <= 1.4.2
Patched versions: 1.4.3

NOTE: A previous patch, 1.4.2, fixed the heap memory issue, but could 
still lead to a DoS infinite loop. Please update to version 1.4.3--- End Message ---

Processed: forcibly merging 1013651 1007847

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1013651 1007847
Bug #1013651 [src:nbsphinx] nbsphinx: FTBFS: KeyError in code-cells.ipynb: 
'state'
Bug #1007847 [src:nbsphinx] nbsphinx: FTBFS with nodejs experimental/14.19.0
Severity set to 'serious' from 'important'
Added tag(s) sid and bookworm.
Merged 1007847 1013651
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1007847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007847
1013651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1021803: gnuserv FTBFS with emacs 28

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1021803 + unreproducible
Bug #1021803 [src:gnuserv] gnuserv FTBFS with emacs 28
Added tag(s) unreproducible.
> retitle 1021803 "gnuserv seems to be affected badly by #1017739"
Bug #1021803 [src:gnuserv] gnuserv FTBFS with emacs 28
Changed Bug title to '"gnuserv seems to be affected badly by #1017739"' from 
'gnuserv FTBFS with emacs 28'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021803: gnuserv FTBFS with emacs 28

[Alexander Zangerl]

tags 1021803 + unreproducible
retitle 1021803 "gnuserv seems to be affected badly by #1017739"
thanks


On Sat, 15 Oct 2022 06:25:57 +0300, Adrian Bunk writes:
>Source: gnuserv
>Version: 3.12.8-8
>Severity: serious
>Tags: ftbfs
>Control: block 1020050 by -1

>Debugger entered--Lisp error: (error "Cannot find suitable directory for 
>output in 'nati...")

i cannot reproduce this: the package builds fine in
a blank pbuilder chroot.

however, searching for 'cannot find suitable directory...' returns
other reports about emacs 28 itself being the party that stuffs up,
in particular

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017739

right now i have no idea how to work around this issue, as i cannot
reproduce the build fault at all.

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/
Arguing that you don't care about the right to privacy because you have 
nothing to hide is no different than saying you don't care about free
speech because you have nothing to say. -- Edward Snowden


signature.asc
Description: Digital Signature

Bug#1021852: libvma FTBFS: error: ISO C++17 does not allow ‘register’ storage class specifier

[Adrian Bunk]

Source: libvma
Version: 9.2.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libvma&arch=amd64&ver=9.2.2-1%2Bb2&stamp=1665870043&raw=0

...
In file included from ../../../../src/utils/asm.h:42,
 from ../../../../src/utils/rdtsc.h:41,
 from ../../../../src/vlogger/vlogger.h:49,
 from ../../../../src/vlogger/main.cpp:36:
../../../../src/utils/asm-x86.h: In function ‘void gettimeoftsc(long long 
unsigned int*)’:
../../../../src/utils/asm-x86.h:113:27: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  |   ^~~~
../../../../src/utils/asm-x86.h:113:37: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  | ^~~~
cc1plus: all warnings being treated as errors
In file included from ../../../../src/utils/asm.h:42,
 from ../../../../src/utils/rdtsc.h:41,
 from ../../../../src/vlogger/vlogger.h:49,
 from ../../../../src/vlogger/vlogger.cpp:34:
../../../../src/utils/asm-x86.h: In function ‘void gettimeoftsc(long long 
unsigned int*)’:
../../../../src/utils/asm-x86.h:113:27: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  |   ^~~~
../../../../src/utils/asm-x86.h:113:37: error: ISO C++17 does not allow 
‘register’ storage class specifier [-Werror=register]
  113 | register uint32_t upper_32, lower_32;
  | ^~~~
make[5]: *** [Makefile:451: main.o] Error 1
make[5]: *** Waiting for unfinished jobs
In file included from ../../../../src/vma/proto/mem_buf_desc.h:39,
 from ../../../../src/vma/util/utils.h:47,
 from ../../../../src/vlogger/vlogger.cpp:46:
../../../../src/vma/util/vma_list.h: At global scope:
../../../../src/vma/util/vma_list.h:90:37: error: ‘template struct 
std::iterator’ is deprecated [-Werror=deprecated-declarations]
   90 | class list_iterator_t : public 
std::iterator
  | ^~~~
In file included from /usr/include/c++/12/string:45,
 from /usr/include/c++/12/bits/locale_classes.h:40,
 from /usr/include/c++/12/bits/ios_base.h:41,
 from /usr/include/c++/12/ios:42,
 from /usr/include/c++/12/ostream:38,
 from /usr/include/c++/12/iostream:39,
 from ../../../../src/vlogger/vlogger.h:41:
/usr/include/c++/12/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
cc1plus: all warnings being treated as errors
make[5]: *** [Makefile:467: vlogger.lo] Error 1

Bug#1008324: ruby-rails-html-sanitizer: diff for NMU version 1.4.3-0.1

[Adrian Bunk]

Control: tags 1008324 + patch
Control: tags 1008324 + pending

Dear maintainer,

I've prepared an NMU for ruby-rails-html-sanitizer (versioned as 1.4.3-0.1)
and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel 
it.

cu
Adrian
diff -Nru ruby-rails-html-sanitizer-1.4.2/CHANGELOG.md ruby-rails-html-sanitizer-1.4.3/CHANGELOG.md
--- ruby-rails-html-sanitizer-1.4.2/CHANGELOG.md	2021-08-29 18:20:32.0 +0300
+++ ruby-rails-html-sanitizer-1.4.3/CHANGELOG.md	2022-06-27 20:47:54.0 +0300
@@ -1,3 +1,14 @@
+## 1.4.3 / 2022-06-09
+
+* Address a possible XSS vulnerability with certain configurations of Rails::Html::Sanitizer.
+
+  Prevent the combination of `select` and `style` as allowed tags in SafeListSanitizer.
+
+  Fixes CVE-2022-32209
+
+  *Mike Dalessio*
+
+
 ## 1.4.2 / 2021-08-23
 
 * Slightly improve performance.
diff -Nru ruby-rails-html-sanitizer-1.4.2/debian/changelog ruby-rails-html-sanitizer-1.4.3/debian/changelog
--- ruby-rails-html-sanitizer-1.4.2/debian/changelog	2022-01-23 21:21:08.0 +0200
+++ ruby-rails-html-sanitizer-1.4.3/debian/changelog	2022-10-16 02:44:52.0 +0300
@@ -1,3 +1,12 @@
+ruby-rails-html-sanitizer (1.4.3-0.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * New upstream release.
+- Fixes FTBFS with Ruby 3. (Closes: #1008324)
+- CVE-2022-32209: Possible XSS vulnerability.
+
+ -- Adrian Bunk   Sun, 16 Oct 2022 02:44:52 +0300
+
 ruby-rails-html-sanitizer (1.4.2-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-rails-html-sanitizer-1.4.2/lib/rails/html/sanitizer/version.rb ruby-rails-html-sanitizer-1.4.3/lib/rails/html/sanitizer/version.rb
--- ruby-rails-html-sanitizer-1.4.2/lib/rails/html/sanitizer/version.rb	2021-08-29 18:20:32.0 +0300
+++ ruby-rails-html-sanitizer-1.4.3/lib/rails/html/sanitizer/version.rb	2022-06-27 20:47:54.0 +0300
@@ -1,7 +1,7 @@
 module Rails
   module Html
 class Sanitizer
-  VERSION = "1.4.2"
+  VERSION = "1.4.3"
 end
   end
 end
diff -Nru ruby-rails-html-sanitizer-1.4.2/lib/rails/html/sanitizer.rb ruby-rails-html-sanitizer-1.4.3/lib/rails/html/sanitizer.rb
--- ruby-rails-html-sanitizer-1.4.2/lib/rails/html/sanitizer.rb	2021-08-29 18:20:32.0 +0300
+++ ruby-rails-html-sanitizer-1.4.3/lib/rails/html/sanitizer.rb	2022-06-27 20:47:54.0 +0300
@@ -141,8 +141,25 @@
 
   private
 
+  def loofah_using_html5?
+# future-proofing, see https://github.com/flavorjones/loofah/pull/239
+Loofah.respond_to?(:html5_mode?) && Loofah.html5_mode?
+  end
+
+  def remove_safelist_tag_combinations(tags)
+if !loofah_using_html5? && tags.include?("select") && tags.include?("style")
+  warn("WARNING: #{self.class}: removing 'style' from safelist, should not be combined with 'select'")
+  tags.delete("style")
+end
+tags
+  end
+
   def allowed_tags(options)
-options[:tags] || self.class.allowed_tags
+if options[:tags]
+  remove_safelist_tag_combinations(options[:tags])
+else
+  self.class.allowed_tags
+end
   end
 
   def allowed_attributes(options)
diff -Nru ruby-rails-html-sanitizer-1.4.2/rails-html-sanitizer.gemspec ruby-rails-html-sanitizer-1.4.3/rails-html-sanitizer.gemspec
--- ruby-rails-html-sanitizer-1.4.2/rails-html-sanitizer.gemspec	2021-08-29 18:20:32.0 +0300
+++ ruby-rails-html-sanitizer-1.4.3/rails-html-sanitizer.gemspec	2022-06-27 20:47:54.0 +0300
@@ -2,42 +2,36 @@
 # This file has been automatically generated by gem2tgz #
 #
 # -*- encoding: utf-8 -*-
-# stub: rails-html-sanitizer 1.4.2 ruby lib
+# stub: rails-html-sanitizer 1.4.3 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "rails-html-sanitizer".freeze
-  s.version = "1.4.2"
+  s.version = "1.4.3"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0".freeze) if s.respond_to? :required_rubygems_version=
-  s.metadata = { "bug_tracker_uri" => "https://github.com/rails/rails-html-sanitizer/issues";, "changelog_uri" => "https://github.com/rails/rails-html-sanitizer/blob/v1.4.2/CHANGELOG.md";, "documentation_uri" => "https://www.rubydoc.info/gems/rails-html-sanitizer/1.4.2";, "source_code_uri" => "https://github.com/rails/rails-html-sanitizer/tree/v1.4.2"; } if s.respond_to? :metadata=
+  s.metadata = { "bug_tracker_uri" => "https://github.com/rails/rails-html-sanitizer/issues";, "changelog_uri" => "https://github.com/rails/rails-html-sanitizer/blob/v1.4.3/CHANGELOG.md";, "documentation_uri" => "https://www.rubydoc.info/gems/rails-html-sanitizer/1.4.3";, "source_code_uri" => "https://github.com/rails/rails-html-sanitizer/tree/v1.4.3"; } if s.respond_to? :metadata=
   s.require_paths = ["lib".freeze]
   s.authors = ["Rafael Mendon\u00E7a Fran\u00E7a".freeze, "Kasper Timm Hansen".freeze]
-  s.date = "2021-08-24"
+  s.date = "2022-06-09"
   s.description = "HTML sanitization for Rails ap

Processed: ruby-rails-html-sanitizer: diff for NMU version 1.4.3-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1008324 + patch
Bug #1008324 [src:ruby-rails-html-sanitizer] ruby-rails-html-sanitizer: FTBFS: 
ERROR: Test "ruby3.0" failed.
Added tag(s) patch.
> tags 1008324 + pending
Bug #1008324 [src:ruby-rails-html-sanitizer] ruby-rails-html-sanitizer: FTBFS: 
ERROR: Test "ruby3.0" failed.
Added tag(s) pending.

-- 
1008324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021850: incron FTBFS with gcc 11

[Adrian Bunk]

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);
  | ^
...

Bug#1021843: marked as done (librust-tokio-serde-dev: impossible to install)

[Debian Bug Tracking System]

Your message dated Sun, 16 Oct 2022 00:19:51 +
with message-id 
and subject line Bug#1021843: fixed in rust-tokio-serde 0.8.0-2
has caused the Debian Bug report #1021843,
regarding librust-tokio-serde-dev: impossible to install
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.)


-- 
1021843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-tokio-serde-dev
Version: 0.8.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on missing package 
librust-rmp-serde-0.15+default-dev

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNLDyAACgkQLHwxRsGg
ASHoIw/+IW48hEY4oiaCsDUNaZQQ3MaMdPnY/ja1Zqs52Pg59qYpvttSIGP+u5B1
sqeBhKNxE6cEsTiPYpzxeGi9mFOl4fzxeyF8MlZjBepIvdOABlByw/IppcxV9LL7
5+2K+B3cRsMPoXxKq0hbwrpyO2fk9VOphgY1Fo4ztFAXwCHaTgx0XDhFdSvQ0/76
oLVbDxz82khaEk5auCFHoKjzetCIE+kbYBOm21kliQmisvYj0JmP5gYedlzC6XvK
2EBWdePtKrzRsUEIZ6MF4z7QAQzgAebpzN9zIMziQlC8TevDb0ynfpXd6G0SluLl
woKiACGc+UqnXJOfhJFcVkUgnAokM1xz6A71e2k5tJ2rtjkvYeIGMz+RuSNYr8LX
QD/o1aYPZ3575iuGO7Y3uQ0NnOStKj2r7BiTi39D25Hy94E6b92HCLMnyTvio932
n0JB1IdqiVBvqUT8d+oryJitudyub25oNzpxKTojzbct4kiZdyjoGrUw5xPvjCln
5sLmCPah5AkXQ/IeIWWr9k6whAPIVNWRFOiWmtay8H/qoqN3dH3+tlEP2ey6XXCq
kMugBWPY+hiucvKZQLnuJVAQBan1YeIoS+FsZw4BD11rAHPRVOcbEIzk58t+PqLC
2M04vExLiVgxGvclJa15jjmA4aM+JWnZJr75oO7jCvB/pgX34Ik=
=gKP1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-tokio-serde
Source-Version: 0.8.0-2
Done: James McCoy 

We believe that the bug you reported is fixed in the latest version of
rust-tokio-serde, 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.
James McCoy  (supplier of updated rust-tokio-serde 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, 15 Oct 2022 17:50:22 -0400
Source: rust-tokio-serde
Architecture: source
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: James McCoy 
Closes: 1021843
Changes:
 rust-tokio-serde (0.8.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package tokio-serde 0.8.0 from crates.io using debcargo 2.5.0
   * Relax rmp-serde dependency to align with the packaged version.  (Closes:
 #1021843)
Checksums-Sha1:
 ea9ff4e45a5ad59bfcddf0024da47043b4db439d 2731 rust-tokio-serde_0.8.0-2.dsc
 e3033819ccb080cc8ef85b7f8cc8139ed7407f1d 3332 
rust-tokio-serde_0.8.0-2.debian.tar.xz
 87dc4623bf2a01f2c0925f51e8212679e33608cb 7513 
rust-tokio-serde_0.8.0-2_source.buildinfo
Checksums-Sha256:
 83c54f960a259b0e1e3bd0f147f74a540a98ce3e984e987d882a816e9c0ebe28 2731 
rust-tokio-serde_0.8.0-2.dsc
 9935fafa85b9f468b11e0225911246b7f96e6b4e9a333d616f5148eb8af8c039 3332 
rust-tokio-serde_0.8.0-2.debian.tar.xz
 c45aef6ff3554facee61052afafbddd22627c29db0ed4cc74fbfdce0b234ede7 7513 
rust-tokio-serde_0.8.0-2_source.buildinfo
Files:
 57953bf367c0c739b04fa39ea75f063c 2731 rust optional 
rust-tokio-serde_0.8.0-2.dsc
 bacdebbf2c6ac62a59b8ca7214446d12 3332 rust optional 
rust-tokio-serde_0.8.0-2.debian.tar.xz
 525882745523582151c37069fd4b871f 7513 rust optional 
rust-tokio-serde_0.8.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmNLKyFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIACgkQ3+aRrjMb
o9tTVRAAv2mQfRkr6iKuh4+PNM33C8i4iKv4A5dUPiSrvog/8ljt+PqPMw01R2Nq
1qzZDcv3qWRUQwLUgRye05cGDd1TBv9nG1ESB/Iu1q03uqUXft9pOi/WAQwimmx3
S6+7iUZH7MldxE48rAlvh3xLW/Db12tV+FLeHVCNkDyZH1pk26YTskygw7AhryT6
L2UWEhNrqWrkTUXPEmoaU83plueaMQktZLeLHIcApcrpCbqvd2jUOZ1ly0U/NS0U
E+UbYf7P+F5mdijyfoz6a6Ok9ihhwDez6hX3BLGlEpI9AOLtY/aa+kgUdbppHmmq
eGAF802LEKi2jACyx6WwSIdDc5hOI3Gx0XHHIWyTPNfpa/Z9xkwoncV7HZKkEPH2
UmH5WOvzdildvUP0x8W3qGscfUBFwZV4+10crfX53U4YFcNMbaKTlDMcH98n9nHv
VPAk8JcP7yABPZZz/0PeyfcuaAx/+rYC/30N7ur1LoQwJ378syoGIWnk+Spm9bdW
McIn4JK6YcHRLv4yYRXjdpvcKJehEOMIbev7hmPhZaJ+XvmGbgjZz9wsn8Lv98we
juYYxcZm0GKn

Bug#1016598: binoculars: vtk[6,7] removal

[François Mazen]

Hello,

I've pushed the modification to the salsa repo [1] and I've uploaded a
NMU package to mentors [2].

VTK is used in the tests, so I had to keep the package python3-vtk9.

Could you please review the code and upload?
Additional request: could you enable CI on the salsa repo?

Thanks,
François

[1] https://salsa.debian.org/science-team/binoculars
[2] https://mentors.debian.net/package/binoculars/


signature.asc
Description: This is a digitally signed message part

Bug#1021265: marked as done (golang-github-libgit2-git2go ftbfs with libgit2 1.5)

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 21:49:34 +
with message-id 
and subject line Bug#1021265: fixed in golang-github-libgit2-git2go 34.0.0-2
has caused the Debian Bug report #1021265,
regarding golang-github-libgit2-git2go ftbfs with libgit2 1.5
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.)


-- 
1021265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: golang-github-libgit2-git2go
Version: 33.0.9-2
Severity: serious
Control: forwarded -1 https://github.com/libgit2/git2go/pull/929

This is also seen in autopkgtest failure 
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/golang-github-libgit2-git2go/26651971/log.gz


Upstream recently merged https://github.com/libgit2/git2go/pull/929 and 
hopefully they will release a new version.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-libgit2-git2go
Source-Version: 34.0.0-2
Done: Timo Röhling 

We believe that the bug you reported is fixed in the latest version of
golang-github-libgit2-git2go, 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.
Timo Röhling  (supplier of updated 
golang-github-libgit2-git2go 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, 15 Oct 2022 21:50:40 +0200
Source: golang-github-libgit2-git2go
Architecture: source
Version: 34.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Timo Röhling 
Closes: 1021265
Changes:
 golang-github-libgit2-git2go (34.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Source only upload. (Closes: #1021265)
Checksums-Sha1:
 8e02b03cc8f87c0b49a78668981c5d86282b7e61 2319 
golang-github-libgit2-git2go_34.0.0-2.dsc
 f4d49100cd6e6295d8898ac553a1dfb8866ae0bb 4328 
golang-github-libgit2-git2go_34.0.0-2.debian.tar.xz
Checksums-Sha256:
 a7998c35cc2de0e9964898f3afee3080b00a7fcacda197154942a116bbd82322 2319 
golang-github-libgit2-git2go_34.0.0-2.dsc
 b22b52e6454362f0b044ba0673ed7f9fa224e3f43105d614eb13521e4de79ff7 4328 
golang-github-libgit2-git2go_34.0.0-2.debian.tar.xz
Files:
 d62f57eb4b29313b3e8aa5af2a221b98 2319 devel optional 
golang-github-libgit2-git2go_34.0.0-2.dsc
 c23f3087fba5996c313bc106d7fbcbd6 4328 devel optional 
golang-github-libgit2-git2go_34.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmNLD8YUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVm8Ugv+LkScxzab5uMdX4vbP0j2TBLH8Lea
QDBQ4ZCI5r20qrDczvKy2JV66RF6+TKm3RbB/FHPtw60Ydfucl8/7O5M0nOz+MxA
SamvmzRE46r5W86p3hp9B+r1atW1uQ9RIPnXgyIhLwsJqJj6ZjMbKHCfr/WRLMA3
EiThbnveVHh3RyzKZ+OiMpi5BebRm4PxJ2LaywBpBSWJpCb1y2rT/jRH97dQxbqI
N7e0akfVBSTNJMtpWiRoesXmMEtmk6BWb0wSbTBV+sbnmNzenpYeYf8V1fDqa7aD
F645+kUY2YWlzKNFuVvt9KhIQS1NgGkumDfAt82u9K6ZSoatXDSn8V4J9EdTWCAs
zim0O8ug+gjn0wWzxKPgx4DU/dxqgFTjfNVQscbqNYp8bn+P/XZIy2swN9jpXQPL
MAvnSA2Fvni8ZMTyt8Vg4t3ZFY7Z4zkiHzYDH8CF6i6Ob2IBElmC/4ldla4INdo9
qi2a1Uk+eteAvJcWomU2xKbbtSR+YNAQ43Lj
=8PHp
-END PGP SIGNATURE End Message ---

Bug#1009731: libglu: diff for NMU version 9.0.2-1.1

[Micha Lenk]

tags 1009731 + patch
tags 1009731 + pending
user debian-rele...@lists.debian.org
usertags 1009731 + bsp-2022-10-de-karlsruhe
thanks

Dear maintainer,

I've prepared an NMU for libglu (versioned as 9.0.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Micha

diff -u libglu-9.0.2/debian/changelog libglu-9.0.2/debian/changelog
--- libglu-9.0.2/debian/changelog
+++ libglu-9.0.2/debian/changelog
@@ -1,3 +1,11 @@
+libglu (9.0.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * control: Let libglu1-mesa-dev depend on libopengl-dev so that opengl.pc
+referenced by our glu.pc is available too (closes: #1009731).
+
+ -- Micha Lenk   Sat, 15 Oct 2022 23:23:58 +0200
+
 libglu (9.0.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -u libglu-9.0.2/debian/control libglu-9.0.2/debian/control
--- libglu-9.0.2/debian/control
+++ libglu-9.0.2/debian/control
@@ -43,6 +43,7 @@
 Depends:
  libglu1-mesa (= ${binary:Version}),
  libgl-dev,
+ libopengl-dev,
  ${misc:Depends},
 Provides: libglu-dev, xlibmesa-glu-dev
 Conflicts: mesag-dev (<< 5.0.0-1), mesa-glide2-dev (<< 5.0.0-1), mesag3+ggi-dev (<< 5.0.0-1), xlibmesa-dev

Bug#1021810: Should firefox-esr be dropped on 32bit architectures in bookworm?

[Mike Hommey]

On Sat, Oct 15, 2022 at 09:27:33AM +0300, Adrian Bunk wrote:
> Package: firefox-esr
> Version: 102.3.0esr-1
> Severity: serious
> Tags: bookworm sid
> X-Debbugs-Cc: Carsten Schoenert , 
> debian-rele...@lists.debian.org, t...@security.debian.org, 
> debian-...@lists.debian.org
> 
> [ various potentially interested parties are Cc'ed ]
> 
> 4 GB address space for one process is an absolute limit on 32bit
> architectures, including for native building as is done in Debian.[1]
> 
> mipsel has 2 GB address space (all Debian buildds have 64bit kernels),
> the 2020 Firefox ESR (78) was the last Firefox ESR to build there.
> 
> On i386 and 32bit arm:
> 4 GB address space are available with a 64bit kernel.
> 3 GB address space are typically available with a 32bit kernel.
> 
> All i386 buildds are using a 64bit kernel,
> but armhf buildds are currently mixed.
> 
> This uncovered that the 2022 ESR of Firefox (102) already needs
> more than 3 GB address space on armhf.[2]
>
> There is a new ESR major release of Firefox every summer,
> which is being used also in *stable releases of Debian since the
> previous ESR branch loses upstream security support soon afterwards.
> 
> It is possible to confine building firefox{,-esr} to only the 64bit
> buildds on the buildd side to address the current issue,[3] but during
> the non-LTS lifetime of bookworm firefox-esr will be upgraded three
> times to newer ESR major releses.
>
> One can hope the 2023 ESR might still be buildable with 4 GB address space,
> which would cover the non-LTS support time of bullseye.
> 
> I would be less optimistic that the 2025 ESR will still be buildable
> with 4 GB address space, which implies that it might not be possbile
> to provide security support for firefox-esr on i386 and 32bit arm
> during the whole non-LTS support time of bookworm.

FWIW, ironically, it's not the new version of Firefox that has these
needs in memory, it's the new version of rustc (the memory usage
regression is there) and/or llvm.

As a matter of fact, firefox-esr 91 started to fail to build on 32bits
architectures on unstable when some new version of rustc went into
unstable.

Mike

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

Hi!

On Sat, Oct 15, 2022 at 11:54:36PM +0300, программист некто wrote:
>Package: grub-pc
>Version: 2.06-3~deb11u1
>Severity: critical
>
>Hello. Since version 2.06-3, grub-install is broken: it fails with "error: 
>unknown filesystem".
>I test command /usr/sbin/grub-install -v /dev/sda
>in some versions. Results in mail attachments.
>Versions older than 2.06-3 works without error (2.06-2 and lower).
>Tested versions: 2.04-20, 2.06-1, 2.06-2, 2.06-3~deb10u1, 2.06-3~deb11u1, 
>2.06-4.

Thanks for testing all these, that's very helpful. Could you please
run grub-install with "-v" and capture the output?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Bug#1021787: marked as done (commons-text: CVE-2022-42889)

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 21:10:45 +
with message-id 
and subject line Bug#1021787: fixed in commons-text 1.10.0-1
has caused the Debian Bug report #1021787,
regarding commons-text: CVE-2022-42889
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.)


-- 
1021787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: commons-text
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for commons-text.

CVE-2022-42889[0]:
| Apache Commons Text performs variable interpolation, allowing
| properties to be dynamically evaluated and expanded. The standard
| format for interpolation is "${prefix:name}", where "prefix" is used
| to locate an instance of org.apache.commons.text.lookup.StringLookup
| that performs the interpolation. Starting with version 1.5 and
| continuing through 1.9, the set of default Lookup instances included
| interpolators that could result in arbitrary code execution or contact
| with remote servers. These lookups are: - "script" - execute
| expressions using the JVM script execution engine (javax.script) -
| "dns" - resolve dns records - "url" - load values from urls, including
| from remote servers Applications using the interpolation defaults in
| the affected versions may be vulnerable to remote code execution or
| unintentional contact with remote servers if untrusted configuration
| values are used. Users are recommended to upgrade to Apache Commons
| Text 1.10.0, which disables the problematic interpolators by default.

https://www.openwall.com/lists/oss-security/2022/10/13/4

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-42889
https://www.cve.org/CVERecord?id=CVE-2022-42889

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: commons-text
Source-Version: 1.10.0-1
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
commons-text, 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.
tony mancill  (supplier of updated commons-text 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, 15 Oct 2022 13:23:14 -0700
Source: commons-text
Architecture: source
Version: 1.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1021787
Changes:
 commons-text (1.10.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.10.0
 - Addresses CVE-2022-42889 (Closes: #1021787)
   * Update debian/maven.ignoreRules for optional upstream deps
   * Freshen years in debian/copyright
   * Bump Standards-Version to 4.6.1
Checksums-Sha1:
 e69e297aa91ff26029c40c970655631c060c57c3 2128 commons-text_1.10.0-1.dsc
 470e67fa3aafd8570f709283f987f470043739c4 343578 commons-text_1.10.0.orig.tar.gz
 790ea11f56f94d4b1f34841716d3a8dddc05fe79 2656 
commons-text_1.10.0-1.debian.tar.xz
 795972d888a23ba397169b1da14923c469ca2115 13457 
commons-text_1.10.0-1_amd64.buildinfo
Checksums-Sha256:
 95f323cea0f13dae71dc7c0cc2400ca323faeadaa40294294bdbf5041a6e91d0 2128 
commons-text_1.10.0-1.dsc
 3611aa48a9506e72c6b1bd9243fec284ab13aaf143031c389be610d136a2d4e3 343578 
commons-text_1.10.0.orig.tar.gz
 c307680e14c77de663fd6e1d9dcc0accc896907f235537206dfbff968348ab8e 2656 
commons-text_1.10.0-1.debian.tar.xz
 bd6cb1eaaa59595ef9c4804dc483f698413646b38a68de1cad3c60b127d197a9 13457 
commons-text_1.10.0-1_amd64.buildinfo
Files:
 6d5a2992e768cb8252807e1d23bcbf7b 2128 java optional commons-text_1.10.0-1.dsc
 1f35ad2bad5457a7f61534fb5e4c9536 343578 java optional 
commons-text_1.10.0.orig.tar.gz
 b90e385c16022f8e33cd555b7bc411b0 2656 java optional 
commons-text_1.10.0-1.debian.tar.xz
 5399d4850d1a11dae141704bbbd8c2bc 13457 java optional 
commons-text_1.10.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE--

Bug#1020108: quilt: diff for NMU version 0.66-2.2

[Martin Quinson]

Hello everybody,

many thanks for your help. There is no need to delay your NMU any further. You
could also upload it directly, I'm really happy with your help.

I'd really love to see someone helping me updating the package to the latest
version. quilt is in maintainance mode upstream, and it's a pitty that I fail to
get the latest improvement in Debian since such a long time.

Thanks again for your help, and enjoy.
Mt

Le samedi 15 octobre 2022 à 11:21 +0200, Christoph Biedl a écrit :
> tags 1020108 + pending
> user debian-rele...@lists.debian.org
> usertags 1020108 + bsp-2022-10-de-karlsruhe
> thank you
> 
> Dear maintainer,
> 
> turns out this has already been addressed in upstream git, so cherry-picking
> that one is the way to go.
> 
> To fix the issues with this package, I've prepared an NMU for quilt
> (versioned as 0.66-2.2), debdiff below. An upload to DELAYED/5 will
> follow shortly. Please feel free to tell me if I should delay it
> longer.
> 
> Regards,
> 
>     Christoph

-- 
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.



signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#1020205: scalable-cyrfonts: FTBFS: cp: cannot stat '/usr/share/fonts/type1/gsfonts/s050000l.afm': No such file or directory

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1020205 by 1021845
Bug #1020205 [src:scalable-cyrfonts] scalable-cyrfonts: FTBFS: cp: cannot stat 
'/usr/share/fonts/type1/gsfonts/s05l.afm': No such file or directory
1020205 was not blocked by any bugs.
1020205 was not blocking any bugs.
Added blocking bug(s) of 1020205: 1021845
> thank you
Stopping processing here.

Please contact me if you need assistance.
-- 
1020205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020205: scalable-cyrfonts: FTBFS: cp: cannot stat '/usr/share/fonts/type1/gsfonts/s050000l.afm': No such file or directory

[Christoph Biedl]

block 1020205 by bug 1021845
user debian-rele...@lists.debian.org
usertags 1020205 + bsp-2022-10-de-karlsruhe
thank you

Lucas Nussbaum wrote...

> > cp: cannot stat '/usr/share/fonts/type1/gsfonts/s05l.afm': No such file 
> > or directory

This file used to be provided by gsfonts which was replaced by
fonts-urw-base35 - that package no longer contains that file. Let's wait
for the word from the maintainer of the latter package.

Christoph


signature.asc
Description: PGP signature

Processed: game-music-emu symbols table update

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1012932 [src:game-music-emu] game-music-emu: ftbfs with GCC-12
Added tag(s) patch.

-- 
1012932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1012932: game-music-emu symbols table update

[Étienne Mollier]

Control: tags -1 + patch

Greetings,

that's probably not much, but the build does go through when
simply updating the symbols table of libgme0:

---8<--8<-->8-->8---
--- debian/libgme0.symbols.orig 2022-10-15 22:12:10.047345969 +0200
+++ debian/libgme0.symbols  2022-10-15 21:52:47.719386628 +0200
@@ -1,5 +1,6 @@
 libgme.so.0 libgme0 #MINVER#
 * Build-Depends-Package: libgme-dev
+ (c++|optional)"std::vector >* 
std::__do_uninit_fill_n >*, unsigned 
long, std::vector > >(std::vector >*, unsigned long, std::vector > const&)@Base" 0.6.3
  (c++|optional)"std::vector >, 
std::allocator > > >::~vector()@Base" 
0.6.3
  (c++|optional|regex)"std::vector 
>::_M_default_append\(unsigned (int|long)\)@Base" 0.6.3
  gme_ay_type@Base 0.6.3
---8<--8<-->8-->8---

Weird that these symbols leak in spite of -fvisibility=hidden,
I'm not sure what to think.  Anyway, in hope this helps…

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Bug#1021790: src:graphicsmagick: fails to migrate to testing for too long: FTBFS on mips64el

[Marti Maria]

Hello,

That’s Marti Maria, the maintainer of lcms2 package. Version 2.14 is supposed 
to fix the GM issue on mips64el.

FYI release candidate 1 for lcms2-2.14 is already available, see 
https://github.com/mm2/Little-CMS/releases/tag/lcms2.14rc1 


I would rather recommend to wait until final release, lcms2 is buried deep in 
the dependence tree and affects far more packages that GM. I do a very thorough 
check before each release but even so, sometimes one other package got broken. 
Now release candidate has passed tests and it is being circulated among users. 
Final 2.14 release  is expected on end of October-22. I moved from November to 
October because the Debian maintainer request.

Best regards
Marti

> On 15 Oct 2022, at 09:25, Adrian Bunk  wrote:
> 
> On Fri, Oct 14, 2022 at 09:40:43PM +0200, Paul Gevers wrote:
>> Hi László,
>> 
>> On 14-10-2022 21:33, László Böszörményi (GCS) wrote:
 Your package src:graphicsmagick has been trying to migrate
 for 61 days [2].
>>>  It's 'only' 37 days, but that's long enough even.
>> 
>> Hmm, [1] says your package was accepted on 14 August 2022; no sure where
>> that weird count in the britney output comes from. Maybe because it took so
>> long before the first binaries were built?
>> ...
> 
> You are looking at the wrong version of the package.
> 
> The "news" section of tracker is not a reliable source for seeing all 
> uploads, especially at times where the ftp team modified their emails
> in a way that tracker choked on them.
> 
>> Paul
> 
> cu
> Adrian

Bug#1021843: librust-tokio-serde-dev: impossible to install

[Jonas Smedegaard]

Package: librust-tokio-serde-dev
Version: 0.8.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on missing package 
librust-rmp-serde-0.15+default-dev

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNLDyAACgkQLHwxRsGg
ASHoIw/+IW48hEY4oiaCsDUNaZQQ3MaMdPnY/ja1Zqs52Pg59qYpvttSIGP+u5B1
sqeBhKNxE6cEsTiPYpzxeGi9mFOl4fzxeyF8MlZjBepIvdOABlByw/IppcxV9LL7
5+2K+B3cRsMPoXxKq0hbwrpyO2fk9VOphgY1Fo4ztFAXwCHaTgx0XDhFdSvQ0/76
oLVbDxz82khaEk5auCFHoKjzetCIE+kbYBOm21kliQmisvYj0JmP5gYedlzC6XvK
2EBWdePtKrzRsUEIZ6MF4z7QAQzgAebpzN9zIMziQlC8TevDb0ynfpXd6G0SluLl
woKiACGc+UqnXJOfhJFcVkUgnAokM1xz6A71e2k5tJ2rtjkvYeIGMz+RuSNYr8LX
QD/o1aYPZ3575iuGO7Y3uQ0NnOStKj2r7BiTi39D25Hy94E6b92HCLMnyTvio932
n0JB1IdqiVBvqUT8d+oryJitudyub25oNzpxKTojzbct4kiZdyjoGrUw5xPvjCln
5sLmCPah5AkXQ/IeIWWr9k6whAPIVNWRFOiWmtay8H/qoqN3dH3+tlEP2ey6XXCq
kMugBWPY+hiucvKZQLnuJVAQBan1YeIoS+FsZw4BD11rAHPRVOcbEIzk58t+PqLC
2M04vExLiVgxGvclJa15jjmA4aM+JWnZJr75oO7jCvB/pgX34Ik=
=gKP1
-END PGP SIGNATURE-

Bug#1020034: marked as done (dgedit: FTBFS: gcc: error: unrecognized command-line option '-V')

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 19:41:10 +
with message-id 
and subject line Bug#1020034: fixed in dgedit 0.10.0-2
has caused the Debian Bug report #1020034,
regarding dgedit: FTBFS: gcc: error: unrecognized command-line option '-V'
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.)


-- 
1020034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dgedit
Version: 0.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> gcc version 12.2.0 (Debian 12.2.0-2) 
> ... rest of stderr output deleted ...
> configure:4945: $? = 0
> configure:4934: gcc -V >&5
> gcc: error: unrecognized command-line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:4945: $? = 1
> configure:4934: gcc -qversion >&5
> gcc: error: unrecognized command-line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:4945: $? = 1
> configure:4934: gcc -version >&5
> gcc: error: unrecognized command-line option '-version'
> gcc: fatal error: no input files
> compilation terminated.
> configure:4945: $? = 1
> configure:4949: checking whether the compiler supports GNU C
> configure:4969: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4969: $? = 0
> configure:4979: result: yes
> configure:4990: checking whether gcc accepts -g
> configure:5011: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5011: $? = 0
> configure:5055: result: yes
> configure:5075: checking for gcc option to enable C11 features
> configure:5090: gcc  -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5090: $? = 0
> configure:5108: result: none needed
> configure:5224: checking whether gcc understands -c and -o together
> configure:5247: gcc -c conftest.c -o conftest2.o
> configure:5250: $? = 0
> configure:5247: gcc -c conftest.c -o conftest2.o
> configure:5250: $? = 0
> configure:5262: result: yes
> configure:5281: checking dependency style of gcc
> configure:5393: result: none
> configure:5408: checking for a sed that does not truncate output
> configure:5478: result: /bin/sed
> configure:5496: checking for grep that handles long lines and -e
> configure:5560: result: /bin/grep
> configure:5565: checking for egrep
> configure:5633: result: /bin/grep -E
> configure:5638: checking for fgrep
> configure:5706: result: /bin/grep -F
> configure:5742: checking for ld used by gcc
> configure:5810: result: /usr/bin/ld
> configure:5817: checking if the linker (/usr/bin/ld) is GNU ld
> configure:5833: result: yes
> configure:5845: checking for BSD- or MS-compatible name lister (nm)
> configure:5900: result: /usr/bin/nm -B
> configure:6040: checking the name lister (/usr/bin/nm -B) interface
> configure:6048: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:6051: /usr/bin/nm -B "conftest.o"
> configure:6054: output
>  B some_variable
> configure:6061: result: BSD nm
> configure:6064: checking whether ln -s works
> configure:6068: result: yes
> configure:6076: checking the maximum length of command line arguments
> configure:6208: result: 1572864
> configure:6256: checking how to convert x86_64-pc-linux-gnu file names to 
> x86_64-pc-linux-gnu format
> configure:6297: result: func_convert_file_noop
> configure:6304: checking how to convert x86_64-pc-linux-gnu file names to 
> toolchain format
> configure:6325: result: func_convert_file_noop
> configure:6332: checking for /usr/bin/ld option to reload object files
> configure:6340: result: -r
> configure:6419: checking for file
> configure:6440: found /usr/bin/file
> configure:6451: result: file
> configure:6527: checking for objdump
> configure:6548: found /usr/bin/objdump
> configure:6559: result: objdump
> configure:6591: checking how to recognize dependent libraries
> configure:6792: result: pass_all
> configure:6882: checking for dlltool
> configure:6917: result: no
> configure:6947: checking how to associate runtime and link libraries
> configure:6975: result: printf %s\n
> configure:7041: checking for 

Bug#1021774: marked as done (cross-toolchain-base-mipsen: duplicated ld.so.1 in multiple packages)

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 19:00:34 +
with message-id 
and subject line Bug#1021774: fixed in cross-toolchain-base-mipsen 21
has caused the Debian Bug report #1021774,
regarding cross-toolchain-base-mipsen: duplicated ld.so.1 in multiple packages
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.)


-- 
1021774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base-mipsen
Version: 20
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

several ld.so.1 variants are shipped by two packages that are not
conflicting with each other:

libc6-mips32-mips64-cross=2.35-3cross1
libc6-mips64-cross=2.35-3cross1
usr/mips64-linux-gnuabi64/lib/ld.so.1
libc6-mips32-mips64el-cross=2.35-3cross1
libc6-mips64el-cross=2.35-3cross1
usr/mips64el-linux-gnuabi64/lib/ld.so.1
libc6-mips32-mips64r6-cross=2.35-3cross1
libc6-mips64r6-cross=2.35-3cross1
usr/mipsisa64r6-linux-gnuabi64/lib/ld-linux-mipsn8.so.1
libc6-mips32-mips64r6el-cross=2.35-3cross1
libc6-mips64r6el-cross=2.35-3cross1
usr/mipsisa64r6el-linux-gnuabi64/lib/ld-linux-mipsn8.so.1
libc6-mips32-mipsn32-cross=2.35-3cross1
libc6-mipsn32-cross=2.35-3cross1
usr/mips64-linux-gnuabin32/lib/ld.so.1
libc6-mips32-mipsn32el-cross=2.35-3cross1
libc6-mipsn32el-cross=2.35-3cross1
usr/mips64el-linux-gnuabin32/lib/ld.so.1
libc6-mips32-mipsn32r6-cross=2.35-3cross1
libc6-mipsn32r6-cross=2.35-3cross1
usr/mipsisa64r6-linux-gnuabin32/lib/ld-linux-mipsn8.so.1
libc6-mips32-mipsn32r6el-cross=2.35-3cross1
libc6-mipsn32r6el-cross=2.35-3cross1
usr/mipsisa64r6el-linux-gnuabin32/lib/ld-linux-mipsn8.so.1


Andreas
--- End Message ---
--- Begin Message ---
Source: cross-toolchain-base-mipsen
Source-Version: 21
Done: YunQiang Su 

We believe that the bug you reported is fixed in the latest version of
cross-toolchain-base-mipsen, 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.
YunQiang Su  (supplier of updated cross-toolchain-base-mipsen 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Oct 2022 01:48:34 +0800
Source: cross-toolchain-base-mipsen
Architecture: source
Version: 21
Distribution: unstable
Urgency: medium
Maintainer: Cross Toolchain Base Team 

Changed-By: YunQiang Su 
Closes: 1021774
Changes:
 cross-toolchain-base-mipsen (21) unstable; urgency=medium
 .
   * dpkg-cross: process lib/ld.so for mips64 and sparc64.
 (Closes: #1021774)
Checksums-Sha1:
 22194aeaef6000a5acf5362477d84ac7f6a98aae 11168 
cross-toolchain-base-mipsen_21.dsc
 93d3a160281a7241e019004a1214eb44a951d224 43596 
cross-toolchain-base-mipsen_21.tar.xz
 56a7c8a46ae42cc6120d699feceee646681ae541 8429 
cross-toolchain-base-mipsen_21_source.buildinfo
Checksums-Sha256:
 2fb5baf6439d348a891158d8eb48e1777161bd4cf99b1fd1d560fd090a0b6284 11168 
cross-toolchain-base-mipsen_21.dsc
 ae1325a6f08711126d7cc1406694a2779b46e30fad4a75bafbc7cc304deabf26 43596 
cross-toolchain-base-mipsen_21.tar.xz
 8a748b7a3da7051aa67e51fc44adac68d4af235a4cd41a521e99def939812f72 8429 
cross-toolchain-base-mipsen_21_source.buildinfo
Files:
 5fba525d14075479df0d764dae4bf9cd 11168 devel optional 
cross-toolchain-base-mipsen_21.dsc
 9c8a59c9e48ca5858ed8dcae10527c63 43596 devel optional 
cross-toolchain-base-mipsen_21.tar.xz
 7c523920605da4b09b7dbcc6f60feb5d 8429 devel optional 
cross-toolchain-base-mipsen_21_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEErzy/48olU1y1e1OneyQHvDH10NoFAmNK9AEPHHN5cUBkZWJp
YW4ub3JnAAoJEHskB7wx9dDaLL8P/3i5SH9tRph2G2fGmeZtrdDQImrrIMOzJGWg
TMNVP6n3D09ar1POnMtxzs1dripLUmlUbVBHYkBHpAfajPSKo3RU5glBtb0nUegx
3miLXk2EcgGSsg8bVnOiplccktaTWJTkX7ndepNc+r4IGNkwP+9kaGVRjk8Yy9wX
Q4kO61sGV7KjR1anRB/dHU/BHsYujQ0vpkWrjichzpkhca2G5JejqnNY/v66jwxJ
XtoBRNwXnGsjdKv7Nzh3qEs/kxotRW9CfGsZ+22xEOOgKNVrGdGBDCA9ESGJ0Rxs
t2di2SglUX5YV5mjOUIUonr/PtfehUt09zm5f0BlSZ1Ls27e/a7h2GXAX18om5kC
f251PKDvd9Y34n/rDBnBKpSxprZKZVcqMYVMnBuLP1SHM0h3RMdj97M8ibDwvkiX
1Sf4cRzM3B/eAjh405ABvXOSB65GLjObJss4Snma9IxSzQDvsK/959oNXDK

Bug#1021833: nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1)

[Hilko Bengen]

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.

Cheers,
-Hilko

Processed: Re: Bug#1021833: nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1)

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1020446
Bug #1021833 [src:nbdkit] nbdkit: FTBFS: FAIL test-partitioning3.sh (exit 
status: 1)
1021833 was not blocked by any bugs.
1021833 was not blocking any bugs.
Added blocking bug(s) of 1021833: 1020446

-- 
1021833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020048: marked as done (vamp-plugin-sdk: FTBFS: gcc: error: unrecognized command-line option '-V')

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 18:34:03 +
with message-id 
and subject line Bug#1020048: fixed in vamp-plugin-sdk 2.10.0-2
has caused the Debian Bug report #1020048,
regarding vamp-plugin-sdk: FTBFS: gcc: error: unrecognized command-line option 
'-V'
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.)


-- 
1020048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vamp-plugin-sdk
Version: 2.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> gcc version 12.2.0 (Debian 12.2.0-2) 
> ... rest of stderr output deleted ...
> configure:3634: $? = 0
> configure:3623: gcc -V >&5
> gcc: error: unrecognized command-line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3634: $? = 1
> configure:3623: gcc -qversion >&5
> gcc: error: unrecognized command-line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3634: $? = 1
> configure:3623: gcc -version >&5
> gcc: error: unrecognized command-line option '-version'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3634: $? = 1
> configure:3638: checking whether the compiler supports GNU C
> configure:3658: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3658: $? = 0
> configure:3668: result: yes
> configure:3679: checking whether gcc accepts -g
> configure:3700: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3700: $? = 0
> configure:3744: result: yes
> configure:3764: checking for gcc option to enable C11 features
> configure:3779: gcc  -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3779: $? = 0
> configure:3797: result: none needed
> configure:3912: checking for stdio.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for stdlib.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for string.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for inttypes.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for stdint.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for strings.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for sys/stat.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for sys/types.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3912: checking for unistd.h
> configure:3912: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3912: $? = 0
> configure:3912: result: yes
> configure:3937: checking for grep that handles long lines and -e
> config

Bug#1008327: marked as done (setbfree: FTBFS: ld: /tmp/ccVQW4B0.o: undefined reference to symbol 'glMaterialfv')

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 18:33:36 +
with message-id 
and subject line Bug#1008327: fixed in setbfree 0.8.11-2
has caused the Debian Bug report #1008327,
regarding setbfree: FTBFS: ld: /tmp/ccVQW4B0.o: undefined reference to symbol 
'glMaterialfv'
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.)


-- 
1008327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: setbfree
Version: 0.8.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -DVERSION="\"0.8.11\"" -DHAVE_LV2_1_8 
> -DHAVE_MEMSTREAM `pkg-config --cflags glu` -I../b_overdrive/ -I../b_whirl  
> -I../b_reverb -I../b_conv -DSHAREDIR="\"/usr/share/setBfree\"" `pkg-config 
> --cflags jack` \
>   -o setBfree midi.o midi_aseq.o state.o vibrato.o tonegen.o program.o 
> pgmParser.o cfgParser.o main.o midnam.o memstream.o ../b_reverb/reverb.c 
> ../b_whirl/eqcomp.c ../b_whirl/whirl.c ../b_overdrive/overdrive.c  \
>   -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -lm -lpthread `pkg-config 
> --libs jack`
> make[3]: Leaving directory '/<>/src'
> make[3]: Leaving directory '/<>/b_synth'
> strip -s b_whirlUI_gl.so
> strip -s x42-whirl
> make[3]: Leaving directory '/<>/b_whirl'
> /usr/bin/ld: /tmp/ccVQW4B0.o: undefined reference to symbol 'glMaterialfv'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libGL.so.1: error adding symbols: DSO 
> missing from command line
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/setbfree_0.8.11-1_unstable.log

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 ---
Source: setbfree
Source-Version: 0.8.11-2
Done: Dennis Braun 

We believe that the bug you reported is fixed in the latest version of
setbfree, 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 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dennis Braun  (supplier of updated setbfree 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, 15 Oct 2022 19:16:41 +0200
Source: setbfree
Architecture: source
Version: 0.8.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 998266 1008327
Changes:
 setbfree (0.8.11-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster
   * Avoid explicitly specifying -Wl,--as-needed linker flag
 .
   [ Dennis Braun ]
   * Fix gl linking (Closes: #1008327)
   * Fix spelling error speficy -> specify
   * d/control:
 + Bump dh-compat to 13
 + Bump Standards Version to 4.6.1
 + Use fonts-dejavu-core instead of ttf-bitstream-vera (Closes: #998266)
 + Mark libasound2-dev as linux-any
 + Add myself as uploader
   * d/copyright: Add myself to the d/ section
   * Remove obsolete d/source/local-options
   * Add d/upstream/metadata
   * Bump d/watch version to 4
Checksums-Sha1:
 409df41cc161a99d35e9bd6ee18bc3cd2148ce67 2292 setbfree_0.8.11-2.dsc
 6fbf7be497e3d9f9743d244aff1cb54c25f3c9c9 12712 setbfree_0.8.11-2.debian.tar.xz
 5e6f19d3359b4b659cbdbdd14ce7fe61db31abbf 6746 
setbfree_0.8.11-2_source.buildinfo
Checksums-Sha256:
 cbfa77ff466ed8f349d5072b4ff05e794beccd0d265e05c8a21a7b6e72964ef9 2292 
setbfree_0.8.11-2.dsc
 a8665d11289aea357760b4d3863ee8e848072e287b480a477f6c4a9f7af06973 12712 
setbfree_0.8.11-2.debian.t

Processed: elisa-player multiple test failures may be fixable with upstream patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch fixed-upstream
Bug #1013576 [src:elisa-player] elisa-player: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit 
code 2
Added tag(s) fixed-upstream and patch.

-- 
1013576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013576: elisa-player multiple test failures may be fixable with upstream patch

[Étienne Mollier]

Control: tags -1 + patch fixed-upstream

Greetings,

After digging into the build log, the reoccurring pattern which
seems to be the root of all failures is that:

> model->hasChildren(parent)' returned FALSE

This looks to stem from src/mediaplaylistproxymodel.cpp, for
which the definition of the method is limited to:

bool MediaPlayListProxyModel::hasChildren(const QModelIndex &parent) 
const
{
return (!parent.isValid()) ? false : (rowCount() > 0);
}

Looking into later versions in upstream repository, the logic of
the method has changed to be the reverse; note the trimmed
exclamation mark before the parent.isValid:

bool MediaPlayListProxyModel::hasChildren(const QModelIndex &parent) 
const
{
return (parent.isValid()) ? false : (rowCount() > 0);
}

Actually there is a simple commit which does just that work of
reverting the logic[1].  Applying this change fixes the FTBFS on
my end.  This can be applied now, or can be fixed later with a
newer upstream version.

[1]: 
https://invent.kde.org/multimedia/elisa/-/commit/0968c47a8bb5e0abf66fb6069d62efa14e6d9ae1

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Processed: reassign 1018253 to emacs-common, forcibly merging 1017698 1018253

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1018253 emacs-common
Bug #1018253 [emacs-commons] emacs-nox: Fatal error when installing
Warning: Unknown package 'emacs-commons'
Bug reassigned from package 'emacs-commons' to 'emacs-common'.
Ignoring request to alter found versions of bug #1018253 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1018253 to the same values 
previously set
> forcemerge 1017698 1018253
Bug #1017698 [emacs-common] emacs-gtk: core dump with unsorted double linked 
list corrupted
Bug #1017779 [emacs-common] emacs-common dies in postinst with "corrupted 
double-linked list"
Bug #1017798 [emacs-common] emacs-common can't be installed: segfault in 
postinst
Bug #1017853 [emacs-common] emacs-nox: byte compiling debian-startup.el fails 
if emacs-el is not installed
Bug #1017798 [emacs-common] emacs-common can't be installed: segfault in 
postinst
Removed indication that 1017798 affects emacs-gtk, src:eweouz, src:gnuplot, 
emacs-lucid, src:gettext, and emacsen-nox
Added indication that 1017798 affects 
emacs-gtk,emacs-lucid,emacsen-nox,src:eweouz,src:gnuplot,src:gettext
Removed indication that 1017698 affects emacs-gtk, src:eweouz, emacs-lucid, 
src:gnuplot, emacsen-nox, and src:gettext
Added indication that 1017698 affects 
emacs-gtk,emacs-lucid,emacsen-nox,src:eweouz,src:gnuplot,src:gettext
Removed indication that 1017779 affects src:eweouz, src:gnuplot, emacs-gtk, 
emacsen-nox, src:gettext, and emacs-lucid
Added indication that 1017779 affects 
emacs-gtk,emacs-lucid,emacsen-nox,src:eweouz,src:gnuplot,src:gettext
Removed indication that 1017853 affects emacs-gtk, emacs-lucid, src:gettext, 
emacsen-nox, src:eweouz, and src:gnuplot
Added indication that 1017853 affects 
emacs-gtk,emacs-lucid,emacsen-nox,src:eweouz,src:gnuplot,src:gettext
Bug #1018253 [emacs-common] emacs-nox: Fatal error when installing
Severity set to 'serious' from 'grave'
Added indication that 1018253 affects 
emacs-gtk,emacs-lucid,emacsen-nox,src:eweouz,src:gnuplot,src:gettext
Marked as found in versions emacs/1:28.1+1-1.
Added tag(s) ftbfs.
Bug #1017779 [emacs-common] emacs-common dies in postinst with "corrupted 
double-linked list"
Bug #1017853 [emacs-common] emacs-nox: byte compiling debian-startup.el fails 
if emacs-el is not installed
Merged 1017698 1017779 1017798 1017853 1018253
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017698
1017779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017779
1017798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017798
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
1018253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020446: gdisk: FTBFS with popt 1.19+dfsg-1~exp1

[Håvard F . Aasen]

Control: tags -1 patch


I've attached a small patch to mitigate the issue with popt.


HåvardFrom: =?utf-8?b?IkjDpXZhcmQgRi4gQWFzZW4i?= 
Date: Sat, 15 Oct 2022 18:55:20 +0200
Subject: Handle plugged memory leak from popt

With popt version 1.19, a memory leak was plugged. gdisk (sdisk) assumed
the value returned by poptGetArg() would remain usable forever because
popt has leaked the value for quite a long time.

This patch consist of one incomplete fix, that has been included in the
official repository, and one that of this writing, is still an open PR.

Origin: upstream, https://sourceforge.net/p/gptfdisk/code/ci/5d5e76d369a412bfb3d2cebb5fc0a7509cef878d/
Origin: upstream, https://sourceforge.net/p/gptfdisk/code/merge-requests/28/
Bug-Debian: https://bugs.debian.org/1020446
---
 gptcl.cc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gptcl.cc b/gptcl.cc
index 34c9421..ab95239 100644
--- a/gptcl.cc
+++ b/gptcl.cc
@@ -156,9 +156,10 @@ int GPTDataCL::DoOptions(int argc, char* argv[]) {
 
// Assume first non-option argument is the device filename
device = (char*) poptGetArg(poptCon);
-   poptResetContext(poptCon);
 
if (device != NULL) {
+  device = strdup(device);
+  poptResetContext(poptCon);
   JustLooking(); // reset as necessary
   BeQuiet(); // Tell called functions to be less verbose & interactive
   if (LoadPartitions((string) device)) {
@@ -498,6 +499,7 @@ int GPTDataCL::DoOptions(int argc, char* argv[]) {
  cerr << "Error encountered; not saving changes.\n";
  retval = 4;
   } // if
+  free(device);
} // if (device != NULL)
poptFreeContext(poptCon);
return retval;

Processed: Re: gdisk: FTBFS with popt 1.19+dfsg-1~exp1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1020446 [src:gdisk] gdisk: FTBFS with popt 1.19+dfsg-1~exp1
Added tag(s) patch.

-- 
1020446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#984037: doscan: ftbfs with GCC-11

[Reiner Herrmann]

Control: tags -1 + pending

Dear maintainer,

I've prepared an NMU for doscan (versioned as 0.3.3-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -u doscan-0.3.3/debian/changelog doscan-0.3.3/debian/changelog
--- doscan-0.3.3/debian/changelog
+++ doscan-0.3.3/debian/changelog
@@ -1,3 +1,11 @@
+doscan (0.3.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS by drop dynamic exception specification, which are no longer
+possible in C++17. (Closes: #984037)
+
+ -- Reiner Herrmann   Sat, 15 Oct 2022 18:55:04 +0200
+
 doscan (0.3.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u doscan-0.3.3/debian/patches/series doscan-0.3.3/debian/patches/series
--- doscan-0.3.3/debian/patches/series
+++ doscan-0.3.3/debian/patches/series
@@ -1 +1,2 @@
 fix-gcc6-FTBFS.patch
+gcc12.patch
only in patch2:
unchanged:
--- doscan-0.3.3.orig/debian/patches/gcc12.patch
+++ doscan-0.3.3/debian/patches/gcc12.patch
@@ -0,0 +1,29 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/984037
+Description: Drop dynamic exception specification
+ Since GCC 11 C++17 is used by default.
+ Dynamic exception specifications were long deprecated
+ and got removed in C++17.
+
+--- a/src/rx.cc
 b/src/rx.cc
+@@ -23,7 +23,7 @@
+ 
+ // rx
+ 
+-rx::rx(const char* pattern, int options) throw (error)
++rx::rx(const char* pattern, int options)
+ {
+   const char *err;
+   int offset;
+--- a/src/rx.h
 b/src/rx.h
+@@ -38,7 +38,7 @@
+ int offset() const;
+   };
+ 
+-  rx(const char*, int options = 0) throw (error);
++  rx(const char*, int options = 0);
+   ~rx();
+ 
+   unsigned captures() const;

Processed: Re: doscan: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #984037 [src:doscan] doscan: ftbfs with GCC-11
Added tag(s) pending.

-- 
984037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021678: marked as done (rust-object: autopkgtest failure on s390x)

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2022 17:47:03 +
with message-id 
and subject line Bug#1021678: fixed in rust-object 0.29.0-2
has caused the Debian Bug report #1021678,
regarding rust-object: autopkgtest failure on s390x
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.)


-- 
1021678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-object
Version: 0.29.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-object/26973632/log.gz

test round_trip::elf::symtab_shndx ... FAILED

failures:

 round_trip::elf::symtab_shndx stdout 
thread 'round_trip::elf::symtab_shndx' panicked at 'assertion failed: `(left == 
right)`
  left: `Section(SectionIndex(16711680))`,
 right: `Section(SectionIndex(65280))`', tests/round_trip/elf.rs:38:9
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.60.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.60.0/library/core/src/panicking.rs:143:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.60.0/library/core/src/panicking.rs:182:5
   4: integration::round_trip::elf::symtab_shndx
 at ./tests/round_trip/elf.rs:38:9
   5: integration::round_trip::elf::symtab_shndx::{{closure}}
 at ./tests/round_trip/elf.rs:10:1
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.60.0/library/core/src/ops/function.rs:227:5
   7: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.60.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
round_trip::elf::symtab_shndx

test result: FAILED. 23 passed; 1 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 1.26s

error: test failed, to rerun pass '--test integration'
autopkgtest [20:36:50]: test librust-object-dev:all: ---]
autopkgtest [20:36:50]: test librust-object-dev:all:  - - - - - - - - - - 
results - - - - - - - - - -
librust-object-dev:all FAIL non-zero exit status 101


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: rust-object
Source-Version: 0.29.0-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-object, 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.
Peter Michael Green  (supplier of updated rust-object 
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, 15 Oct 2022 16:12:57 +
Source: rust-object
Architecture: source
Version: 0.29.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1021678
Changes:
 rust-object (0.29.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package object 0.29.0 from crates.io using debcargo 2.5.0
   * Add upstream patches to fix endian issues (Closes: 1021678)
Checksums-Sha1:
 8f361d193528b40345cb344c12ba2c12e80241b4 2329 rust-object_0.29.0-2.dsc
 9c9b1fe2c00f47d549c4a5287963c2244c7f0fa1 6616 
rust-object_0.29.0-2.debian.tar.xz
 5226601e15ee318db6b05b13f4c5e2999fd28808 7806 
rust-object_0.29.0-2_source.buildinfo
Checksums-Sha256:
 bd99d86eb3cad344855a4d097d910525c80748269a566ed804ccf258ae720455 2329 
rust-object_0.29.0-2.dsc
 5228063598100ab13e02555dedf80fca2415de2bdeec831a2bb39fa814fa7029 6616 
rust-object_0.29.0-2.debian.tar.xz
 36624ba4570ccf6ce8efd5946958f962b69ef35f602c3ea6ac19913a90d30601 7806 
rust-object_0.29.0-2_source.buildinfo
Files:
 e38fedbb8043f62d95386c7b6cca8ec8 2329 rust optional rust-object_0.29.0-2.dsc
 378bcdbecff7da00857f993454a13727 6616 rust optional 
rust-object_0.29.0-2.debian.tar.xz
 3e7bad169663f8284214e71266907658 7806 rust optional 
rust-object_0.29.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmNK54gUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsLM

Processed: tagging 1021529

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1021529 + sid bookworm
Bug #1021529 [src:pcmanfm-qt] pcmanfm-qt: hardcoded dependency on libfm-qt8
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017136: ksirk: diff for NMU version 4:21.08.0-1.1

[Reiner Herrmann]

Hi Aurélien,

On Sat, Oct 15, 2022 at 07:29:11PM +0200, Aurélien COUDERC wrote:
> Would you go as far as posting the change as an MR against the salsa repo ? 🙂
> https://salsa.debian.org/qt-kde-team/kde/ksirk

I just opened a MR with the changes from the NMU:
https://salsa.debian.org/qt-kde-team/kde/ksirk/-/merge_requests/2

Kind regards,
  Reiner

Bug#1017136: ksirk: diff for NMU version 4:21.08.0-1.1

[Aurélien COUDERC]

Dear Reiner,

Le 15 octobre 2022 18:27:35 GMT+02:00, Reiner Herrmann  a 
écrit :
>Control: tags 1017136 + patch
>Control: tags 1017136 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for ksirk (versioned as 4:21.08.0-1.1) and
>uploaded it to DELAYED/2. Please feel free to tell me if I
>should delay it longer.

thanks for that, appreciated.

Would you go as far as posting the change as an MR against the salsa repo ? 🙂
https://salsa.debian.org/qt-kde-team/kde/ksirk

Also if you're interested in KDE apps/gear in general, help is welcome on their 
maintenance.


Happy hacking,
--
Aurélien

Processed: acm: diff for NMU version 6.0+20200416-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1012888 + patch
Bug #1012888 [src:acm] acm: ftbfs with GCC-12
Ignoring request to alter tags of bug #1012888 to the same tags previously set
> tags 1012888 + pending
Bug #1012888 [src:acm] acm: ftbfs with GCC-12
Added tag(s) pending.

-- 
1012888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1012888: acm: diff for NMU version 6.0+20200416-1.1

[Reiner Herrmann]

Control: tags 1012888 + patch
Control: tags 1012888 + pending

Dear maintainer,

I've prepared an NMU for acm (versioned as 6.0+20200416-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -Nru acm-6.0+20200416/debian/changelog acm-6.0+20200416/debian/changelog
--- acm-6.0+20200416/debian/changelog	2020-11-17 12:52:56.0 +0100
+++ acm-6.0+20200416/debian/changelog	2022-10-15 18:55:51.0 +0200
@@ -1,3 +1,12 @@
+acm (6.0+20200416-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Make sure that objects are built reproducibly with the same build flags
+(provided by dpkg-buildflags) and increase size of buffer for sprintf
+output. (Closes: #1012888)
+
+ -- Reiner Herrmann   Sat, 15 Oct 2022 18:55:51 +0200
+
 acm (6.0+20200416-1) unstable; urgency=medium
 
   * Switch to new upstream source,
diff -Nru acm-6.0+20200416/debian/patches/fix_buffer_size.patch acm-6.0+20200416/debian/patches/fix_buffer_size.patch
--- acm-6.0+20200416/debian/patches/fix_buffer_size.patch	1970-01-01 01:00:00.0 +0100
+++ acm-6.0+20200416/debian/patches/fix_buffer_size.patch	2022-10-15 18:55:51.0 +0200
@@ -0,0 +1,16 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/1012888
+Description: Increase buffer size to have space for maximum possible output
+ VColor.c:91:9: note: ‘sprintf’ output between 8 and 11 bytes into a destination of size 8
+
+--- a/src/V/VColor.c
 b/src/V/VColor.c
+@@ -87,7 +87,7 @@
+ 
+ char * VColor_getName(VColor_Type *c)
+ {
+-	static char s[8];
++	static char s[11];
+ 	sprintf(s, "#%02u%02u%02u", c->red, c->green, c->blue);
+ 	return s;
+ }
diff -Nru acm-6.0+20200416/debian/patches/hardening1.patch acm-6.0+20200416/debian/patches/hardening1.patch
--- acm-6.0+20200416/debian/patches/hardening1.patch	2020-11-17 12:52:56.0 +0100
+++ acm-6.0+20200416/debian/patches/hardening1.patch	2022-10-15 18:55:51.0 +0200
@@ -85,3 +85,14 @@
  	return 0;
  }
  
+--- a/src/V/Makefile
 b/src/V/Makefile
+@@ -4,6 +4,8 @@
+ CFLAGS := -Wall -Werror -g -fmax-errors=99 -Wuninitialized -Wmissing-prototypes -Wredundant-decls
+ LIBS :=
+ 
++include Makefile-include.txt
++
+ .PHONY: all
+ all:
+ 	make  Alib.o VColor.o VGlyph.o VObjects.o VPoly.o VRoman.o Vlib.o Vlibmath.o
diff -Nru acm-6.0+20200416/debian/patches/series acm-6.0+20200416/debian/patches/series
--- acm-6.0+20200416/debian/patches/series	2020-11-17 12:52:56.0 +0100
+++ acm-6.0+20200416/debian/patches/series	2022-10-15 18:55:51.0 +0200
@@ -3,3 +3,4 @@
 set_default_object_dir.patch
 fix_paths_in_acm_tcl.patch
 hardening1.patch
+fix_buffer_size.patch

Processed: Re: Bug#992592: lightdm fails to start after update to bullseye (missing '/var/lib/lightdm/data')

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # ... without rendering it completely unusable to everyone
> severity 992592 important
Bug #992592 [lightdm] lightdm fails to start after update to bullseye (missing 
'/var/lib/lightdm/data')
Severity set to 'important' from 'grave'
> tags 992592 moreinfo unreproducible
Bug #992592 [lightdm] lightdm fails to start after update to bullseye (missing 
'/var/lib/lightdm/data')
Added tag(s) moreinfo and unreproducible.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was 
debian.a...@manchmal.in-ulm.de).
> usertags 992592 + bsp-2022-10-de-karlsruhe
There were no usertags set.
Usertags are now: bsp-2022-10-de-karlsruhe.
> thank you
Stopping processing here.

Please contact me if you need assistance.
-- 
992592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#992592: lightdm fails to start after update to bullseye (missing '/var/lib/lightdm/data')

[Christoph Biedl]

# ... without rendering it completely unusable to everyone
severity 992592 important
tags 992592 moreinfo unreproducible
user debian-rele...@lists.debian.org
usertags 992592 + bsp-2022-10-de-karlsruhe
thank you

Pavel Sanda wrote...

> updating debian to bullseye killed access to my desktop environment.
> It was actually stretch->buster and then (after appropriate reboots etc.)
> buster->bullseye, so not sure which of two steps broke it.

Looking into that issue, I failed to reproduce it. So I started with
stretch and did both dist-upgrades up to bullseye, and still lightdm
starts up as expected.

> lightdm used to be default DM and was not working anymore after the update.
> Checking logs with
> lightdm --test-mode --debug
> showed critical line about missing /var/lib/lightdm/data like in bugs
> #947319 and #931335.

This is strange since in postinst, /var/lib/lightdm/ is created if
missing, and permissions are set as needed by lightdm. I'd expect
breakage only in conditions you would have noticed anyway - like
unfinished installation, or full disk.

In case you still have the files around (or still can reproduce the
problem), the content of /var/log/lightdm/ should contain more bits
what's going wrong. Out of curiosity, did you purge packages no longer
needed after the upgrade (as listed by deborphan)?

Christoph (not the lightdm maintainer, just trying to help here)



signature.asc
Description: PGP signature

Processed: opensc: diff for NMU version 0.22.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1013011 + patch
Bug #1013011 [src:opensc] opensc: ftbfs with GCC-12
Ignoring request to alter tags of bug #1013011 to the same tags previously set
> tags 1013011 + pending
Bug #1013011 [src:opensc] opensc: ftbfs with GCC-12
Added tag(s) pending.

-- 
1013011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013011: opensc: diff for NMU version 0.22.0-2.1

[Reiner Herrmann]

Control: tags 1013011 + patch
Control: tags 1013011 + pending

Dear maintainer,

I've prepared an NMU for opensc (versioned as 0.22.0-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -Nru opensc-0.22.0/debian/changelog opensc-0.22.0/debian/changelog
--- opensc-0.22.0/debian/changelog	2022-01-31 07:02:55.0 +0100
+++ opensc-0.22.0/debian/changelog	2022-10-15 18:26:16.0 +0200
@@ -1,3 +1,10 @@
+opensc (0.22.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Import patch to fix usage of pointer after realloc (Closes: #1013011)
+
+ -- Reiner Herrmann   Sat, 15 Oct 2022 18:26:16 +0200
+
 opensc (0.22.0-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru opensc-0.22.0/debian/patches/gcc12.patch opensc-0.22.0/debian/patches/gcc12.patch
--- opensc-0.22.0/debian/patches/gcc12.patch	1970-01-01 01:00:00.0 +0100
+++ opensc-0.22.0/debian/patches/gcc12.patch	2022-10-15 18:26:16.0 +0200
@@ -0,0 +1,31 @@
+From 0f7082ea46562b15221f428860b993e0519c6cbd Mon Sep 17 00:00:00 2001
+From: Veronika Hanulikova 
+Date: Wed, 16 Feb 2022 11:59:27 +0100
+Bug-Debian: https://bugs.debian.org/1013011
+Subject: [PATCH] Fix usage of pointer after realloc
+
+---
+ src/sm/sm-iso.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/src/sm/sm-iso.c b/src/sm/sm-iso.c
+index 5baded77c6..2c3f6bcabd 100644
+--- a/src/sm/sm-iso.c
 b/src/sm/sm-iso.c
+@@ -181,13 +181,14 @@ static int format_le(size_t le, struct sc_asn1_entry *le_entry,
+ 
+ static int prefix_buf(u8 prefix, u8 *buf, size_t buflen, u8 **cat)
+ {
+-	u8 *p;
++	u8 *p = NULL;
++	int ptr_same = *cat == buf;
+ 
+ 	p = realloc(*cat, buflen + 1);
+ 	if (!p)
+ 		return SC_ERROR_OUT_OF_MEMORY;
+ 
+-	if (*cat == buf) {
++	if (ptr_same) {
+ 		memmove(p + 1, p, buflen);
+ 	} else {
+ 		/* Flawfinder: ignore */
diff -Nru opensc-0.22.0/debian/patches/series opensc-0.22.0/debian/patches/series
--- opensc-0.22.0/debian/patches/series	2022-01-31 07:02:55.0 +0100
+++ opensc-0.22.0/debian/patches/series	2022-10-15 18:26:16.0 +0200
@@ -1 +1,2 @@
 0001-Use-sysconfdir-opensc-for-opensc.conf.patch
+gcc12.patch

Processed: owner 1021787

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 1021787 !
Bug #1021787 [src:commons-text] commons-text: CVE-2022-42889
Owner recorded as tony mancill .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): reassign 1018253 to emacs-commons, forcibly merging 1017698 1018253

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1018253 emacs-commons
Bug #1018253 [emacs-nox] emacs-nox: Fatal error when installing
Bug reassigned from package 'emacs-nox' to 'emacs-commons'.
Warning: Unknown package 'emacs-commons'
Warning: Unknown package 'emacs-commons'
No longer marked as found in versions emacs/1:28.1+1-2.
Warning: Unknown package 'emacs-commons'
Warning: Unknown package 'emacs-commons'
Ignoring request to alter fixed versions of bug #1018253 to the same values 
previously set
Warning: Unknown package 'emacs-commons'
> forcemerge 1017698 1018253
Bug #1017698 [emacs-common] emacs-gtk: core dump with unsorted double linked 
list corrupted
Bug #1017779 [emacs-common] emacs-common dies in postinst with "corrupted 
double-linked list"
Bug #1017798 [emacs-common] emacs-common can't be installed: segfault in 
postinst
Bug #1017853 [emacs-common] emacs-nox: byte compiling debian-startup.el fails 
if emacs-el is not installed
Unable to merge bugs because:
package of #1018253 is 'emacs-commons' not 'emacs-common'
Failed to forcibly merge 1017698: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017698
1017779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017779
1017798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017798
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
1018253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021837: porechop: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Sebastian Ramacher]

Source: porechop
Version: 0.2.4+dfsg-3
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=porechop&arch=amd64&ver=0.2.4%2Bdfsg-3%2Bb1&stamp=1663544975&raw=0


Traceback (most recent call last):
  File "/<>/setup.py", line 114, in 
setup(name='porechop',
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
172, in setup
ok = dist.parse_command_line()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
479, in parse_command_line
args = self._parse_command_opts(parser, args)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
545, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class  must subclass Command
E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
python3.10 setup.py clean 


Cheers
-- 
Sebastian Ramacher

Processed: autoconf2.69 FTBFS possible fix from later version

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #997145 [src:autoconf2.69] autoconf2.69: FTBFS: autoconf.texi:9: unknown 
command `setcontentsaftertitlepage'
Added tag(s) patch.

-- 
997145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#997145: autoconf2.69 FTBFS possible fix from later version

[Étienne Mollier]

Control: tags -1 + patch

Greetings,

Later autoconf versions such as 2.71 do not include the command
to @setcontentsaftertitlepage for html documents anymore.  As
this is mostly cosmetic, an easy fix could be to simply stop
providing this in the documentation.  With the below patch added
in the quilt stack, the package gets to build from source again:

---8<--8<--8<--8<---
--- autoconf2.69-2.69.orig/doc/autoconf.texi
+++ autoconf2.69-2.69/doc/autoconf.texi
@@ -5,9 +5,6 @@
 @include version.texi
 @settitle Autoconf
 @setchapternewpage odd
-@ifnothtml
-@setcontentsaftertitlepage
-@end ifnothtml
 @finalout
 
 @c @ovar(ARG)
--->8-->8-->8-->8---

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Bug#1021836: mypaint: FTBFS: AssertionError: False is not true : The maximum abs difference with premultiplied alpha is too great: 97.0 > 8.0 [255=white].

[Sebastian Ramacher]

Source: mypaint
Version: 2.0.1-5
Severity: serious
Tags: ftbfs sid bookworm
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=mypaint&arch=amd64&ver=2.0.1-5&stamp=1661980780&raw=0

==
FAIL: test_docpaint (tests.mypaintlib.DocPaint)
Saved and reloaded documents look identical
--
Traceback (most recent call last):
  File "/<>/tests/mypaintlib.py", line 353, in test_docpaint
self.assert_pngs_equal(
  File "/<>/tests/mypaintlib.py", line 187, in assert_pngs_equal
self.assertTrue(equal_enough, msg=msg)
AssertionError: False is not true : The maximum abs difference with 
premultiplied alpha is too great: 97.0 > 8.0 [255=white].

--
Ran 43 tests in 21.153s

FAILED (failures=1, skipped=30)
Test failed: 
error: Test failed: 
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: 
python3.10 setup.py test 
rm -fr -- /tmp/dh-xdg-rundir-w0Ft5vcq
dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit 
code 13

Cheers
-- 
Sebastian Ramacher

Processed: rapidjson: diff for NMU version 1.1.0+dfsg2-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1016229 + patch
Bug #1016229 [src:rapidjson] rapidjson: FTBFS: memorystream.h:47:59: error: 
pointer used after ‘void free(void*)’ [-Werror=use-after-free]
Ignoring request to alter tags of bug #1016229 to the same tags previously set
> tags 1016229 + pending
Bug #1016229 [src:rapidjson] rapidjson: FTBFS: memorystream.h:47:59: error: 
pointer used after ‘void free(void*)’ [-Werror=use-after-free]
Added tag(s) pending.

-- 
1016229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1016229: rapidjson: diff for NMU version 1.1.0+dfsg2-7.1

[Reiner Herrmann]

Control: tags 1016229 + patch
Control: tags 1016229 + pending

Dear maintainer,

I've prepared an NMU for rapidjson (versioned as 1.1.0+dfsg2-7.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -Nru rapidjson-1.1.0+dfsg2/debian/changelog rapidjson-1.1.0+dfsg2/debian/changelog
--- rapidjson-1.1.0+dfsg2/debian/changelog	2021-01-07 14:45:27.0 +0100
+++ rapidjson-1.1.0+dfsg2/debian/changelog	2022-10-15 18:10:14.0 +0200
@@ -1,3 +1,10 @@
+rapidjson (1.1.0+dfsg2-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC 12. (Closes: #1016229)
+
+ -- Reiner Herrmann   Sat, 15 Oct 2022 18:10:14 +0200
+
 rapidjson (1.1.0+dfsg2-7) unstable; urgency=medium
 
   * Do not use -arch=native on ppc64 and cross-compilation:
diff -Nru rapidjson-1.1.0+dfsg2/debian/patches/gcc12_encdedstreamtest.patch rapidjson-1.1.0+dfsg2/debian/patches/gcc12_encdedstreamtest.patch
--- rapidjson-1.1.0+dfsg2/debian/patches/gcc12_encdedstreamtest.patch	1970-01-01 01:00:00.0 +0100
+++ rapidjson-1.1.0+dfsg2/debian/patches/gcc12_encdedstreamtest.patch	2022-10-15 18:10:14.0 +0200
@@ -0,0 +1,22 @@
+From 2b2c80450031028439ba2a17a09ef5aa10f2159b Mon Sep 17 00:00:00 2001
+From: Tom Briden 
+Date: Sun, 15 May 2022 10:20:21 +0100
+Subject: [PATCH] encdedstreamtest: fix use-after-free compile error with
+ gcc-12
+
+---
+ test/unittest/encodedstreamtest.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/test/unittest/encodedstreamtest.cpp
 b/test/unittest/encodedstreamtest.cpp
+@@ -113,8 +113,8 @@
+ EXPECT_EQ(expected, actual);
+ }
+ EXPECT_EQ('\0', s.Peek());
+-free(data);
+ EXPECT_EQ(size, eis.Tell());
++free(data);
+ }
+ }
+ 
diff -Nru rapidjson-1.1.0+dfsg2/debian/patches/gcc12_valuetest.patch rapidjson-1.1.0+dfsg2/debian/patches/gcc12_valuetest.patch
--- rapidjson-1.1.0+dfsg2/debian/patches/gcc12_valuetest.patch	1970-01-01 01:00:00.0 +0100
+++ rapidjson-1.1.0+dfsg2/debian/patches/gcc12_valuetest.patch	2022-10-15 18:10:14.0 +0200
@@ -0,0 +1,34 @@
+From 1f59c69cd18cd508395fe0bb5c2f8ee909e3c48d Mon Sep 17 00:00:00 2001
+From: Tom Briden 
+Date: Sun, 15 May 2022 10:15:26 +0100
+Subject: [PATCH] valuetest: fix potential write of terminating nul past the
+ end of the destination
+
+Fixes 2 compile errors with gcc-12, eg:
+
+tesunittest/valuetest.cpp:1516:30: error: 'sprintf' may write a terminating nul past the end of the destination [-Werror=format-overflow=]
+test/unittest/valuetest.cpp:1516:20: note: 'sprintf' output between 2 and 11 bytes into a destination of size 10
+---
+ test/unittest/valuetest.cpp | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/test/unittest/valuetest.cpp
 b/test/unittest/valuetest.cpp
+@@ -1512,7 +1512,7 @@
+ {
+ int i = 0;
+ for (auto& m : x.GetObject()) {
+-char name[10];
++char name[11];
+ sprintf(name, "%d", i);
+ EXPECT_STREQ(name, m.name.GetString());
+ EXPECT_EQ(i, m.value.GetInt());
+@@ -1523,7 +1523,7 @@
+ {
+ int i = 0;
+ for (const auto& m : const_cast(x).GetObject()) {
+-char name[10];
++char name[11];
+ sprintf(name, "%d", i);
+ EXPECT_STREQ(name, m.name.GetString());
+ EXPECT_EQ(i, m.value.GetInt());
diff -Nru rapidjson-1.1.0+dfsg2/debian/patches/series rapidjson-1.1.0+dfsg2/debian/patches/series
--- rapidjson-1.1.0+dfsg2/debian/patches/series	2021-01-07 14:42:47.0 +0100
+++ rapidjson-1.1.0+dfsg2/debian/patches/series	2022-10-15 18:10:14.0 +0200
@@ -10,3 +10,5 @@
 0001-support-IBM-PowerPC-ppc64-ppc64le-and-XL-compiler.patch
 0001-CMake-do-not-pass-march-native-or-mcpu-native-when-c.patch
 deal-with-Werror-type-limits.patch
+gcc12_encdedstreamtest.patch
+gcc12_valuetest.patch

Bug#1021833: nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1)

[Sebastian Ramacher]

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

Bug#1021832: fastqtl: FTBFS: /usr/bin/ld: cannot find -lbz2: No such file or directory

[Sebastian Ramacher]

Source: fastqtl
Version: 2.184+v7+dfsg-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=fastqtl&arch=amd64&ver=2.184%2Bv7%2Bdfsg-1&stamp=1665041296&raw=0

g++ -std=c++11 -O3 -Wl,-z,relro -Wl,-z,now obj/analysisMapping.o 
obj/analysisNominal.o obj/analysisNominalBest.o obj/analysisPermutation.o 
obj/analysisPermutationInteraction.o obj/analysisPermutationPerGroup.o 
obj/analysisPermutationSequence.o obj/commands.o obj/df.o obj/fastQTL.o 
obj/management.o obj/mle.o obj/readCovariates.o obj/readGenotypes.o 
obj/readGroups.o obj/readInclusionsExclusions.o obj/readInteractions.o 
obj/readPhenotypes.o obj/readThresholds.o obj/residualizer.o obj/tabix.o 
obj/utils.o -lRmath -lhts -lm -lz -lbz2 -lboost_iostreams 
-lboost_program_options -lgslcblas -lgsl -lblas -o bin/fastQTL
/usr/bin/ld: cannot find -lbz2: No such file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:94: bin/fastQTL] Error 1
-- 
Sebastian Ramacher

Bug#1017136: ksirk: diff for NMU version 4:21.08.0-1.1

[Reiner Herrmann]

Control: tags 1017136 + patch
Control: tags 1017136 + pending

Dear maintainer,

I've prepared an NMU for ksirk (versioned as 4:21.08.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -Nru ksirk-21.08.0/debian/changelog ksirk-21.08.0/debian/changelog
--- ksirk-21.08.0/debian/changelog	2021-08-16 09:25:30.0 +0200
+++ ksirk-21.08.0/debian/changelog	2022-10-15 17:58:28.0 +0200
@@ -1,3 +1,10 @@
+ksirk (4:21.08.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Import patch to use new KNewStuff header location. (Closes: #1017136)
+
+ -- Reiner Herrmann   Sat, 15 Oct 2022 17:58:28 +0200
+
 ksirk (4:21.08.0-1) unstable; urgency=medium
 
   [ Norbert Preining ]
diff -Nru ksirk-21.08.0/debian/patches/knewstuff.patch ksirk-21.08.0/debian/patches/knewstuff.patch
--- ksirk-21.08.0/debian/patches/knewstuff.patch	1970-01-01 01:00:00.0 +0100
+++ ksirk-21.08.0/debian/patches/knewstuff.patch	2022-10-15 17:58:28.0 +0200
@@ -0,0 +1,21 @@
+From 459f18191e11e7a1d38b61cd0114bd881a110539 Mon Sep 17 00:00:00 2001
+From: Ahmad Samir 
+Date: Thu, 26 May 2022 15:49:27 +0200
+Bug-Debian: https://bugs.debian.org/1017136
+Subject: [PATCH] Use KNewStuff FowardingHeaders
+
+---
+ ksirk/Dialogs/newGameDialogImpl.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/ksirk/Dialogs/newGameDialogImpl.cpp
 b/ksirk/Dialogs/newGameDialogImpl.cpp
+@@ -28,7 +28,7 @@
+ #include 
+ #include 
+ #include 
+-#include 
++#include 
+ 
+ #include 
+ #include 
diff -Nru ksirk-21.08.0/debian/patches/series ksirk-21.08.0/debian/patches/series
--- ksirk-21.08.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ ksirk-21.08.0/debian/patches/series	2022-10-15 17:58:28.0 +0200
@@ -0,0 +1 @@
+knewstuff.patch

Processed: ksirk: diff for NMU version 4:21.08.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1017136 + patch
Bug #1017136 [src:ksirk] ksirk: FTBFS: newGameDialogImpl.cpp:31:10: fatal 
error: downloaddialog.h: No such file or directory
Ignoring request to alter tags of bug #1017136 to the same tags previously set
> tags 1017136 + pending
Bug #1017136 [src:ksirk] ksirk: FTBFS: newGameDialogImpl.cpp:31:10: fatal 
error: downloaddialog.h: No such file or directory
Added tag(s) pending.

-- 
1017136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021831: intel-ipsec-mb: FTBFS: dh_install: error: missing files, aborting

[Sebastian Ramacher]

Source: intel-ipsec-mb
Version: 1.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=intel-ipsec-mb&arch=amd64&ver=1.3-1&stamp=1664293055&raw=0

   dh_install -a
dh_install: warning: Cannot find (any matches for) "docs/ipsec-mb_8h.html" 
(tried in ., debian/tmp)

dh_install: warning: libipsec-mb-dev missing files: docs/ipsec-mb_8h.html
dh_install: warning: Cannot find (any matches for) "docs/ipsec-mb_8h.js" (tried 
in ., debian/tmp)

dh_install: warning: libipsec-mb-dev missing files: docs/ipsec-mb_8h.js
dh_install: warning: Cannot find (any matches for) 
"docs/ipsec-mb_8h_source.html" (tried in ., debian/tmp)

dh_install: warning: libipsec-mb-dev missing files: docs/ipsec-mb_8h_source.html
dh_install: error: missing files, aborting
make: *** [debian/rules:54: binary-arch] Error 25


Cheers
-- 
Sebastian Ramacher

Bug#1017304: libmateweather: diff for NMU version 1.26.0-1.1

[Reiner Herrmann]

Control: tags 1017304 + patch
Control: tags 1017304 + pending

Dear maintainer,

I've prepared an NMU for libmateweather (versioned as 1.26.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -Nru libmateweather-1.26.0/debian/changelog libmateweather-1.26.0/debian/changelog
--- libmateweather-1.26.0/debian/changelog	2021-12-10 23:02:01.0 +0100
+++ libmateweather-1.26.0/debian/changelog	2022-10-15 17:45:15.0 +0200
@@ -1,3 +1,10 @@
+libmateweather (1.26.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update spelling of Kiev/Kyiv to match tzdata (Closes: #1017304)
+
+ -- Reiner Herrmann   Sat, 15 Oct 2022 17:45:15 +0200
+
 libmateweather (1.26.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru libmateweather-1.26.0/debian/patches/series libmateweather-1.26.0/debian/patches/series
--- libmateweather-1.26.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ libmateweather-1.26.0/debian/patches/series	2022-10-15 17:45:08.0 +0200
@@ -0,0 +1 @@
+timezones.patch
diff -Nru libmateweather-1.26.0/debian/patches/timezones.patch libmateweather-1.26.0/debian/patches/timezones.patch
--- libmateweather-1.26.0/debian/patches/timezones.patch	1970-01-01 01:00:00.0 +0100
+++ libmateweather-1.26.0/debian/patches/timezones.patch	2022-10-15 17:45:08.0 +0200
@@ -0,0 +1,32 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/1017304
+Description: Update spelling of Kiev/Kyiv to match tzdata
+ tzdata 2022b-1 changed it from Kiev to Kyiv.
+
+--- a/data/Locations.xml.in
 b/data/Locations.xml.in
+@@ -20618,13 +20618,13 @@
+   UA
+   UP
+   
+-
++
+   Europe/Simferopol
+   Europe/Uzhgorod
+   Europe/Zaporozhye
+ 
+   
+-  Europe/Kiev
++  Europe/Kyiv
+   
+ 
+ Boryspil'
+@@ -20700,7 +20700,7 @@
+  "Kiev" is the traditional English name.
+  The local name in Ukrainian is "Kyyiv".
+   -->
+-Kiev
++Kyiv
+ 50.43 30.516667
+ 
+   Kyiv

Processed: libmateweather: diff for NMU version 1.26.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1017304 + patch
Bug #1017304 [src:libmateweather] libmateweather: FTBFS: Invalid timezones in 
./Locations.xml.in: Europe/Kiev
Ignoring request to alter tags of bug #1017304 to the same tags previously set
> tags 1017304 + pending
Bug #1017304 [src:libmateweather] libmateweather: FTBFS: Invalid timezones in 
./Locations.xml.in: Europe/Kiev
Added tag(s) pending.

-- 
1017304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1005800

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1005800
Bug #1005800 [src:sundials] sundials: FTBFS in sid (test failures)
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1005800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems