Bug#1021766: Doesn't call program after timeout

[martin f krafft]

Regarding the following, written by "Thorsten Glaser" on 2022-10-14 at 13:45 
Uhr +:
I run X.org with evilwm, although I do use the “exec startx” method 
to run X, not a login manager, and that with xserver-xorg-legacy. 
Maybe that makes a difference?


I use `xdm` and no legacy packages. I don't even have graphics 
drivers installed anymore (modesetting just works now), and using 
libinput.


I just replicated this exact problem on a second machine that's 
configured similarly.


I've attached my strace for about 10 seconds. It's notable that 
there also isn't any reaction/input/event/whatever when I move the 
mouse and tap a key 10 seconds later.


Maybe xidle does use legacy stuff? I've installed the legacy package 
and will report back as soon as I can restart X.


--
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"man sagt nicht 'nichts!', man sagt dafür 'jenseits' oder 'gott'."

 - friedrich nietzsche

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

[Adrian Bunk]

Control: severity -1 serious
Control: retitle -1 libvirglrenderer-dev must depend on packages required for 
its pkg-config file
Control: affects -1 src:qemu
Control: tags -1 ftbfs

On Sat, Sep 10, 2022 at 02:36:12PM +0300, Michael Tokarev wrote:
> Package: libvirglrenderer-dev
> Version: 0.10.1-1
> Severity: important
> 
> When a package uses libvirglrenderer-dev, it expects the package to be
> self-contained, so the build-dependency is specified against only the
> package which is actually used, not about its inter-dependencies.
> However, the installed libvirglrenderer-dev isn't useable as it is:
> 
> meson.build:717:2: ERROR: Could not generate cargs for virglrenderer:
> Package libva was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libva.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libva', required by 'virglrenderer', not found
> 
> This is because virglrenderer.pc refers to libva.pc which is not pulled
> in by the dependencies of libvirglrenderer-dev package.
> 
> libva-dev should be added to the Depends: field of libvirglrenderer-dev.
> Or maybe debian should have a mechanism to track deps of pkgconfig
> files somehow, in a way similar to shared libraries.
> 
> Severity is important because this causes other packages to FTBFS.
> Maybe it shuold be serious instead.

Changing it to serious.

With 0.10.3-1 vulkan is a new requirement, breaking the qemu build again:
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A7.1%2Bdfsg-2%2Bb1=1665894634=0

The complete list is currently:
$ pkg-config --cflags virglrenderer
Package epoxy was not found in the pkg-config search path.
Perhaps you should add the directory containing `epoxy.pc'
to the PKG_CONFIG_PATH environment variable
Package 'epoxy', required by 'virglrenderer', not found
Package 'libdrm', required by 'virglrenderer', not found
Package 'gbm', required by 'virglrenderer', not found
Package 'vulkan', required by 'virglrenderer', not found
Package 'libva', required by 'virglrenderer', not found
Package 'libva-drm', required by 'virglrenderer', not found
$

In practice, most/all of the -dev build dependencies also have to become 
dependencies of libvirglrenderer-dev.

> Thanks,
> 
> /mjt

cu
Adrian

Bug#1021661: RFS: hashcash/1.22-1 [ITA] [RC] -- postage payment scheme for email based on hash calculations

[Stefan Kangas]

Bastian Germann  writes:

> One has to be owner to move a repo, so I could not.
> I have skipped that part and uploaded with your d/watch fix.

Thank you!  Would it be appropriate for me to

# Note: 460b77bf748 is "Make debian/watch more resilient to change"
git tag --sign -m "Debian release 1.22-1" debian/1.22-1 460b77bf748
git push --tags origin

?

Also, I notice that it says "Build log checks report 1 warning" at:
https://tracker.debian.org/pkg/hashcash

When looking at the build logs here:
https://buildd.debian.org/status/fetch.php?pkg=hashcash=amd64=1.22-1=1665849263=0

The only thing I could find that did not look entirely right to me was
this:

gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource
'/tmp/dpkg-verify-sig.Hnb_19Km/trustedkeys.kbx': General error
gpgv: Signature made Sat Oct 15 14:36:43 2022 UTC
gpgv:using RSA key 406220C8B8552802378CCE411F5C7A8B45564314
gpgv:issuer "b...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify signature ./hashcash_1.22-1.dsc

And this:

/<>/hashcash_1.22-1_amd64-buildd.changes.new could not be
renamed to /<>/hashcash_1.22-1_amd64-buildd.changes: Illegal
seek
Distribution field may be wrong!!!

Is any of this reason for concern?  Or is there anything else that I missed?

Bug#1021847: python-stetl: Build documents using sphinx, but no ${sphinxdoc:Built-Using}

[Sebastiaan Couwenberg]

Control: tags -1 moreinfo

On 10/15/22 23:41, Boyuan Yang wrote:

Source: python-stetl
Your package builds documentation using sphinx and have it installed, but it
does not use the Built-Using: ${sphinxdoc:Built-Using} field to document the
version of sphinx used in building. Please consider adding this missing field.


What benefit does this have?


Besides, it might be a better idea to have the documentation separated to an
individual -doc arch:all package instead.


We're not going to add a binary package and require a trip through NEW.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

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#1021848: python-stetl: Build-depends on obsolete, useless python3-cov-core

[Sebastiaan Couwenberg]

Control: tags -1 - patch
Control: tags -1 + pending

This is fixed in git.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

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=amd64=1.17.0-3%2Bb2=1665894517=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_parameters |  

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

Bug#1021856: volk_8u_x2_encodeframepolar_8u_generic missing in Debian

[A. Maitland Bottoms]

Package: volk
Version: 1.3-1
Tags: pending

"I think this debian patch is the culprit:

https://sources.debian.org/patches/volk/2.4.1-2/make-acc-happy/

It removes #ifdef LV_HAVE_GENERIC from volk_8u_x2_encodeframepolar_8u.h, which 
prevents the generic implementation from being found. With the generic 
implementation gone, volk_get_index is then very unhappy.
@argilo"

Upstream issues:
https://github.com/gnuradio/volk/issues/516
 volk_get_index broken, stuck in infinite loop #516
https://github.com/gnuradio/gnuradio/issues/5013
 std::bad_alloc in qa_polar_decoder_sc_systematic #5013 

The make-acc-happy patch removing the #ifdef was first applied to volk
1.3-1

Setting pending tag for fixing in 2.5.2-2.

-Maitland

Bug#1021855: RFS: inkscape-textext/1.8.2-1 -- Re-editable LaTeX graphics for Inkscape

[Antonio Russo]

Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: aeru...@aerusso.net

Dear mentors,

I am looking for a sponsor for my package "inkscape-textext"

 * Package name: inkscape-textext
   Version : 1.8.2-1
   Upstream Author : Jan Winkler 
 * URL : https://textext.github.io/textext
 * License : BSD-3-clause
 * Vcs : https://salsa.debian.org/aerusso-guest/textext
   Section : graphics
   Description : Re-editable LaTeX graphics for Inkscape

TexText is a Python plugin for the vector graphics editor Inkscape
providing the possibility to add and re-edit LaTeX generated SVG
elements to your drawing.

 Key features
 . Windows/Linux/MacOS support
 . LaTeX generated SVG elements can be re-edited later
 . Multi-line editor with syntax highlighting
 . Compilation with PdfLaTeX, XeLaTeX or LuaLaTex
 . Interoperable scaling in TexText and Inkscape
 . Font size match with Inkscape text
 . Customizable TeX preamble (additional packages, parskip, parindent, etc.)
 . Colorization via TeX commands/Inkscape is kept after re-editing
 . Alignment anchor of the produced output
 . Preview images

It builds the binary packages:

  inkscape-textext - Re-editable LaTeX graphics for Inkscape
  inkscape-textext-doc - Re-editable LaTeX graphics for Inkscape (documentation)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/inkscape-textext/

Alternatively, one can download the package with dget using this command:

  dget -x 
hhttps://mentors.debian.net/debian/pool/main/i/inkscape-textext/inkscape-textext_1.8.2-1.dsc

Changes since the last upload:

 inkscape-textext (1.8.2-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches
   * Do not compress changelog in -doc package
   * Update debian/copyright
   * Bump standards version (no changes required)
   * Debian Janitor: clean up metadata

This upload is primarily to track upstream releases.  A few minor packaging 
issues were
addressed, none, however, should be end-user visible.

Best,
Antonio Russo

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=arm64=4.3.3-1%2Bb1=1665872328=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

Bug#954781: libqt5core5a: QT will not use Wayland on Gnome

[charlesmelara]

Hi, Dmitry and other maintainers,

I've came accross this problem a couple months ago because I maintain a
QT application (Kristall). It was pretty hard to pinpoint the need to
install qtwayland5 to make everything work when setting the variable.
Besides the message displayed when running the program via cli, it also
goes to journalctl if running via Icon so users might be worried. To try
to help them, I created a bug against kristall [1] and I'm going to ship
a debian/README to explain the situation.

Thanks to sergiodj, we discovered this bug and that fedora is patching
qt base to run wayland natively in gnome since december of 2019 [2] - so
they've had a lot of time to test and find bugs. The rationale and
benefits are:

"Qt Wayland plugin has been available for a long time, but it hasn't
been in condition where it could be enabled by default. With Qt 5.12 the
state of the Wayland plugin is much better and it's becoming more and
more reliable. It now supports all the needed protocols and has been
enabled by default for non-Gnome Wayland sessions. With Qt Wayland on
Gnome Wayland session we need to support CSD, it's actually the only way
how decorations are going to work in Qt apps right now. Qt Wayland
implements basic decorations, which really doesn't match Gnome Adwaita
theme, therefore there are new CSD being implemented as part of
QGnomePlatform.

To make Qt applications run natively on Wayland we need to modify Qt 5,
specifically qt5-qtbase module, where we allow the Wayland plugin to be
used also for Gnome sessions. The new decorations from QGnomePlatform
will be used automatically once they are fully implemented and updated
in Fedora.

Qt applications running with the Wayland plugin run generally faster and
smoother on Wayland enabled sessions like Gnome Wayland and better
support HiDPI displays (respects desktop scale)."

On Mon, 23 Mar 2020 15:33:40 +0300 Dmitry Shachnev 
wrote:
> On Mon, Mar 23, 2020 at 01:23:43PM +0100, Norbert Lange wrote:
> > Runnin any QT Application on Gnome will blacklist Wayland. You see
> > the explicit message when starting an application from the terminal.
> >
> > %  wireshark   Warning: Ignoring
> > XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to
> > run on Wayland anyway.
> >
> > (for me this is really annoying as I have a HiDPI and a normal
> > Monitor, X11 doesnt allow different scaling).
> >
> > Fedora considers QT 5.12+ ready to enable this by default, see the
> > two used pathes under [1], Section "Scope".
> >
> > I'd hope debian could follow here, and use those patches in testing.
>
> The problem is that upstream Qt considers GNOME/Wayland support not
> yet ready.
>
> There is an umbrella bug (QTBUG-68619) which depends on some other
> bugs. At the moment only one of them is open (QTBUG-68636), so I think
> as soon as someone fixes it, it will be possible to enable that
> support.

The QTBUG-68619 has been closed because QTBUG-68636 has also been
closed. But the latter has been fixed only in qt 6.2.3 so it won't be
extended to our current qt5 version. It seems to me that this bug is
pretty minor regarding its impact, and I found a lot of matchs in
Debian's bug db regarding the QT_QPA_PLATFORM [3].

That's why I'd like to know if you would consider changing the
qtwayland5 to Recommends or Depends in order to alleviate users burden
if they decide to run wayland natively via the envvar. It's also an
alternative to follow Fedora's approach, though I think the first option
would be preferred.

Thanks and best regards,
Charles

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018251
[2]
https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
[3]
https://www.mail-archive.com/search?q=QT_QPA_PLATFORM%3Dwayland=debian-bugs-dist%40lists.debian.org

Bug#1021853: sysprof: FTBFS on hppa - mmap aliasing issue

[John David Anglin]

Source: sysprof
Version: 3.46.0-2
Severity: normal
Tags: ftbfs patch

Dear Maintainer,

The test test-mapped-ring-buffer fails on hppa:

 2/4 =
test: test-mapped-ring-buffer
start time:   14:55:16
duration: 0.40s
result:   killed by signal 6 SIGABRT
command:  GSETTINGS_BACKEND=memory G_DEBUG=gc-friendly MALLOC_PERTURB_=142 
NO_AT_BRIDGE=1 MALLOC_CHECK_=2 G_TEST_SRCDIR=/<>/src/tests 
G_TEST_BUILDDIR=/<>/obj-hppa-linux-gnu/src/tests 
/<>/obj-hppa-linux-gnu/src/tests/test-mapped-ring-buffer
--- stdout ---
# random seed: R02Sb35445e48e2cfa93f89f3c5793901662
1..3
# Start of MappedRingBuffer tests
Bail out! ERROR:../src/tests/test-mapped-ring-buffer.c:43:test_basic_movements: 
'reader' should not be NULL
--- stderr ---
**
ERROR:../src/tests/test-mapped-ring-buffer.c:43:test_basic_movements: 'reader' 
should not be NULL
==

Full build log is here:
https://buildd.debian.org/status/fetch.php?pkg=sysprof=hppa=3.46.0-3=1665759904=0

In map_head_and_body_twice(), the second mmap call fails:

mmap2(NULL, 135168, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 0xf64a2000
mmap2(0xf64b3000, 65536, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_FIXED, 3, 0x1000) 
= -1 EINVAL (Invalid argument)

Due to cache issues, all shared mapping of a page must be equivalently
mapped.  This requires page mappings to be at the same virtual address
modulo 4 MB.  Due to a kernel limitation, all mappings to a file must
be equivalent.

The test can be fixed by rounding the buffer_size used in the mapped
ring buffer to 4 MB on hppa.  This makes the two mmap mappings equivalent.

Please send the fix upstream and install if okay.

Regards,
Dave Anglin

-- System Information:
Debian Release: bookworm/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 5.19.15+ (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Index: sysprof-3.46.0/src/libsysprof-capture/mapped-ring-buffer.c
===
--- sysprof-3.46.0.orig/src/libsysprof-capture/mapped-ring-buffer.c
+++ sysprof-3.46.0/src/libsysprof-capture/mapped-ring-buffer.c
@@ -35,6 +35,7 @@
 
 #define DEFAULT_N_PAGES 32
 #define BUFFER_MAX_SIZE ((UINT32_MAX/2)-_sysprof_getpagesize())
+#define SHM_COLOUR 0x0040
 
 enum {
   MODE_READER= 1,
@@ -172,9 +173,16 @@ mapped_ring_buffer_new_reader (size_t bu
 
   page_size = _sysprof_getpagesize ();
 
-  /* Add 1 page for coordination header */
   if (buffer_size == 0)
 buffer_size = page_size * DEFAULT_N_PAGES;
+
+#ifdef __hppa__
+  /* Round buffer_size up to the shared memory colour boundary */
+  buffer_size += SHM_COLOUR - 1;
+  buffer_size &= ~(SHM_COLOUR - 1);
+#endif
+
+  /* Add 1 page for coordination header */
   buffer_size += page_size;
 
   /* Create our memfd (or tmpfs) for writing */

Bug#1016515: dehydrated: Another server, recently upgraded to bullseye

[Jon Daley]

Package: dehydrated
Version: 0.7.0-2
Followup-For: Bug #1016515

FYI.

Hi, I recently upgraded another server to bullseye, and started getting this 
error.
I googled around and see everyone who had problems with older cURLs and 
dehydrated versions in 2019,
but my versions are newer than what they are talking about.

Eventually I thought to test it on a different server and re-found the cURL 
retry problem, and that
solved it for this server as well.

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-14-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dehydrated depends on:
ii  ca-certificates  20210119
ii  curl 7.74.0-1.3+deb11u3
ii  openssl  1.1.1n-0+deb11u3

dehydrated recommends no packages.

dehydrated suggests no packages.

-- no debconf information

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=amd64=9.2.2-1%2Bb2=1665870043=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 

Bug#1021851: bullseye-pu: package python-dnslib/0.9.14-1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: python-modules-t...@lists.alioth.debian.org

(Please provide enough information to help the release team
to judge the request efficiently. E.g. by filling in the
sections below.)

[ Reason ]
Backport of upstream fix for CVE-2022-22846 (no changes needed).

[ Impact ]
User impact is potential vulnerability to DNS cache poisoning.

[ Tests ]
Package runs the upstream test suite both during build and in an
autopkgtest.

[ Risks ]
Code change is trivial and pretty obviously correct.  There were no
other changes between 0.9.14 (in Bullseye) and 0.9.17 where this fix is
backported from in the file in question.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
Adds a check that the ID value in a DNS reply matches an ID value in a
query.

[ Other info ]
Security team rated this a minor issue, so addressing fix to stable
update.
diff -Nru python-dnslib-0.9.14/debian/changelog 
python-dnslib-0.9.14/debian/changelog
--- python-dnslib-0.9.14/debian/changelog   2020-06-10 00:51:44.0 
-0400
+++ python-dnslib-0.9.14/debian/changelog   2022-10-15 20:23:24.0 
-0400
@@ -1,3 +1,10 @@
+python-dnslib (0.9.14-1+deb11u1) bullseye; urgency=medium
+
+  * Add debian/patches/0002-Validate-TXID-in-client.py.patch from upstream to
+address CVE-2022-22846
+
+ -- Scott Kitterman   Sat, 15 Oct 2022 20:23:24 -0400
+
 python-dnslib (0.9.14-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch 
python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch
--- python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch   
1969-12-31 19:00:00.0 -0500
+++ python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch   
2022-10-15 20:21:51.0 -0400
@@ -0,0 +1,24 @@
+From: Scott Kitterman 
+Date: Sat, 15 Oct 2022 20:17:26 -0400
+Subject: Validate TXID in client.py
+Fixes CVE-2022-22846
+Origin: backport, 
https://github.com/paulc/dnslib/commit/76e8677699ed098387d502c57980f58da642aeba
+
+---
+ dnslib/client.py | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/dnslib/client.py b/dnslib/client.py
+index 628ea81..09572b6 100644
+--- a/dnslib/client.py
 b/dnslib/client.py
+@@ -76,6 +76,9 @@ if __name__ == '__main__':
+ a_pkt = q.send(address,port,tcp=args.tcp)
+ a = DNSRecord.parse(a_pkt)
+ 
++if q.header.id != a.header.id:
++raise DNSError('Response transaction id does not match query 
transaction id')
++
+ if a.header.tc and args.noretry == False:
+ # Truncated - retry in TCP mode
+ a_pkt = q.send(address,port,tcp=True)
diff -Nru python-dnslib-0.9.14/debian/patches/series 
python-dnslib-0.9.14/debian/patches/series
--- python-dnslib-0.9.14/debian/patches/series  2020-06-10 00:50:31.0 
-0400
+++ python-dnslib-0.9.14/debian/patches/series  2022-10-15 20:17:32.0 
-0400
@@ -1 +1,2 @@
 0001-Only-run-tests-for-python3.patch
+0002-Validate-TXID-in-client.py.patch

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=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#1020516: i386: nothing but a blinking underscore at the top left

[Bernhard Übelacker]

Wow, what a splendid debugging! I hope you enjoyed it.


Thanks, yes, it was some interesting debugging,
and I was quite surprised when I saw the issue caused
by the very same instruction as the other bug ...


By the way with following sequence it should be possible
to see the impact on the FPU register stack
(or crash in case of pre-SSE2-CPUs):


apt install libz3-4-dbgsym
gdb -q
  file /usr/bin/file
  set environment LD_PRELOAD=/usr/lib/i386-linux-gnu/libz3.so.4
  set stop-on-solib-events 1
  run
  cont
  rb _GLOBAL__sub_I_memory_manager
  cont
  tb __static_initialization_and_destruction_0
  cont
  display/i $pc
  nexti
  ... (repeat 'nexti' until the 'pxor' instruction appears)
  info float
  nexti
  info float

Bug#1021849: reportbug: non-SMP kernels are not visibly mentioned

[Adam Borowski]

Package: reportbug
Version: 11.5.1
Severity: wishlist

Hi!
Non-SMP machines are very, very rare today.  This means, they use code paths
that don't get exercised elsewhere, and may trigger UP-specific bugs.  Yet
reportbug points out SMP machines as if they were an oddity while UP don't
receive a remark.

It may seem that lack of "(SMP w/4294967296 cores)" implies UP -- but alas,
having done data mining on bug reports before, I know that a good part of
users trim the "System Information", and quite a lot of them replaces that
data with something written by hand.

Thus, please do append "(UP)" or some such on non-SMP boxen.
This particular machine for example is a D1 Nezha.


Meow!
-- Package-specific info:
** Environment settings:
EDITOR="jstar"
EMAIL="kilob...@angband.pl"
INTERFACE="text"

** /home/kilobyte/.reportbugrc:
reportbug_version "11.5.0"
mode advanced
ui text
smtphost "barad-dur.angband.pl"
smtptls

-- System Information:
Debian Release: bookworm/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
merged-usr: no
Architecture: riscv64

Kernel: Linux 5.4.61 (PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages reportbug depends on:
ii  apt2.5.3
ii  python33.10.6-1
ii  python3-reportbug  11.5.1
ii  sensible-utils 0.0.17

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf1.5.79
pn  debsums
pn  dlocate
pn  emacs-bin-common   
ii  exim4-daemon-light [mail-transport-agent]  4.96-6
ii  file   1:5.41-4
ii  gnupg  2.2.39-1
pn  python3-urwid  
pn  reportbug-gtk  
pn  xdg-utils  

Versions of packages python3-reportbug depends on:
ii  apt2.5.3
ii  file   1:5.41-4
ii  python33.10.6-1
ii  python3-apt2.3.0+b2
ii  python3-debian 0.1.48
ii  python3-debianbts  3.2.3
ii  python3-requests   2.27.1+dfsg-1
ii  sensible-utils 0.0.17

python3-reportbug suggests no packages.

-- no debconf information

Bug#1007287: xfsdump: please consider upgrading to 3.0 source format

[Nathan Scott]

Hi Bastian,

Please go right ahead - thanks for your efforts!

cheers.

--
Nathan

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#1021848: python-stetl: Build-depends on obsolete, useless python3-cov-core

[Boyuan Yang]

Source: python-stetl
Version: 2.0+ds-3
Severity: normal
X-Debbugs-CC: sebas...@debian.org
Tags: sid  patch

Dear Debian python-stetl package maintainer,

Your package build-depends on python3-cov-core, which is not needed and is due
to be removed. Related discussion can be found at
https://bugs.debian.org/1008835 . Even though the source code of python3-stetl
(requirement-dev.txt) mentions cov-core, it is not really needed during
building and actually not needed since nose2 has already migrated away from
cov-core. Please consider directly dropping it, ideally before Debian 12
freeze.

Thanks,
Boyuan Yang


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

Bug#1021847: python-stetl: Build documents using sphinx, but no ${sphinxdoc:Built-Using}

[Boyuan Yang]

Source: python-stetl
Version: 2.0+ds-3
Severity: minor
Tags: sid
X-Debbugs-CC: sebas...@debian.org

Dear Debian python-stetl package maintainer,

Your package builds documentation using sphinx and have it installed, but it
does not use the Built-Using: ${sphinxdoc:Built-Using} field to document the
version of sphinx used in building. Please consider adding this missing field.

Besides, it might be a better idea to have the documentation separated to an
individual -doc arch:all package instead.

Thanks,
Boyuan Yang


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

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#1008016: ITP: safe-network -- network routing and service daemon for the Safe Network

[Jonas Smedegaard]

0.71.1 draft 1 needs embedding 105 crates 113 crates (92 missing, 1 broken, 7 
outdated, 5 ahead); builds in ~52 minutes; runs but functionality not yet 
properly tested

Main tasks now are to keep package up-to-date with upstream releases, and
to package more of the crates currently embedded.

Here's how you can help:

As user running Debian, you can test this draft package: Either build it
yourself from source or tell (by posting to this bugreport) if you
prefer testing the binary packages I built - then I will share those.

As developer (but no need to be official member of Debian!), you can
join the Debian Rust team and help package these missing crates:
https://salsa.debian.org/debian/safe-network/-/blob/debian/latest/debian/TODO


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

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#932820: vanguards: Use Python 3 instead of PyPy, because we are going to remove unsupported PyPy

[Micha Lenk]

Control: retitle -1 vanguards: Migrate to PyPy3 (Python 3)

Hi,

On Fri, 26 Jul 2019 14:19:21 -0300 Ondrej Novy  wrote:

[...] current plan is:

* remove almost all pypy modules, keep only pypy interpreter (and maybe

setuptools, etc.)

* migrate to pypy3 (not possible now, waiting for tooling)


I've fixed this bug's title to reflect the new plan.

The plan is a bit unspecific about what tooling could be missing, so I 
started to investigate a bit:


* pypy3 is available

* dh-python has a Debhelper sequence for pypy (Python 2), but not
  for pypy3 (Python 3). There is no bug report for dh-python open
  that would request it.

* Once a pypy3 Debhelper sequence is available, the following pypy3
  packages need to be created (just from looking at vanguards's
  Build-Depends:)
  * pypy3-setuptools
  * pypy3-stem
  * pypy3-pytest
  * pypy3-ipaddress

Regards,
Micha

Bug#1021845: s050000l.afm lost in transition from gsfonts to fonts-urw-base35

[Christoph Biedl]

Roland Rosenfeld wrote...

> This file is now available in fonts-urw-base35 as
> /usr/share/fonts/type1/urw-base35/StandardSymbolsPS.afm 

Ah, didn't see that. There are slight differences, let's hope they won't
affect scalable-cyrfonts in a bad way.

> I'd suggest, that scalable-cyrfonts should Build-Depend on
> fonts-urw-base35 instead of gsfonts and use
> /usr/share/fonts/type1/urw-base35/StandardSymbolsPS.afm instead of
> /usr/share/fonts/type1/gsfonts/s05l.afm.

Indeed, I'll try it that way. Let's hope there are no further packages
affected by this - according to codesearch[1], the maintainers of
imagemagick and graphicsmagick might have a problem.

Thanks for your swift response.

Christoph

[1] https://codesearch.debian.net/search?q=s05l.afm=1


signature.asc
Description: 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

Bug#1021841: setbfree FTCBFS -- multiple reasons

[Wookey]

On 2022-10-16 00:39 +0530, Nilesh Patra wrote:

> - It uses strip extensively. While for debian systems, simply removing the 
> strip
> call from all makefiles could be OK, since dh_strip will simply take care of 
> it.
> But,  it'd be hard to make things upstream-able
> if desired at some point. So I sent STRIP to the -strip 
> for
> cross builds.

Thanks for fixing this.

I have one minor suggestion.

> +ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
> +STRIP := strip
> +else
> +STRIP := $(DEB_HOST_GNU_TYPE)-strip
> +export PKG_CONFIG = $(DEB_HOST_GNU_TYPE)-pkg-config
> +endif

x86_64-linux-gnu-strip is shipped in binutils-x86-64-linux-gnu and so
on for other arches, so the above test for setting strip with/without
a prefix is not necessary.

Just setting:
STRIP := $(DEB_HOST_GNU_TYPE)-strip
should always work and is a bit neater IMHO.

Wookey
-- 
Principal hats:  Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#1021845: s050000l.afm lost in transition from gsfonts to fonts-urw-base35

[Roland Rosenfeld]

Christoph Biedl schrieb am Samstag, den 15. Oktober 2022:

> | #1020205 ("scalable-cyrfonts: FTBFS: cp: cannot stat
> | '/usr/share/fonts/type1/gsfonts/s05l.afm': No such file or
> | directory - )
> 
> and identified the problem as follows: This file s05l.afm was
> previously provided by gsfonts package, that package is now transitional
> and depends on fonts-urw-base35, but the file is not provided there.

This file is now available in fonts-urw-base35 as
/usr/share/fonts/type1/urw-base35/StandardSymbolsPS.afm 

> Question: Was this an oversight, or by intention? In the first case,
> please update your package so I can fix scalable-cyrfonts. If it's the
> latter, can you please provide a transition plan, and mention it in the
> upcoming release notes to avoid further surprises.

I'd suggest, that scalable-cyrfonts should Build-Depend on
fonts-urw-base35 instead of gsfonts and use
/usr/share/fonts/type1/urw-base35/StandardSymbolsPS.afm instead of
/usr/share/fonts/type1/gsfonts/s05l.afm.

Greetings
Roland

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

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#1021845: s050000l.afm lost in transition from gsfonts to fonts-urw-base35

[Christoph Biedl]

Package: fonts-urw-base35
Version: 20200910-4
Severity: normal

Dear maintainer,

during today's Bug Squashing Party I looked at

| #1020205 ("scalable-cyrfonts: FTBFS: cp: cannot stat
| '/usr/share/fonts/type1/gsfonts/s05l.afm': No such file or
| directory - )

and identified the problem as follows: This file s05l.afm was
previously provided by gsfonts package, that package is now transitional
and depends on fonts-urw-base35, but the file is not provided there.

Question: Was this an oversight, or by intention? In the first case,
please update your package so I can fix scalable-cyrfonts. If it's the
latter, can you please provide a transition plan, and mention it in the
upcoming release notes to avoid further surprises.

FWIW, that file is still available via

r-base-core: /usr/lib/R/library/grDevices/afm/s05l.afm.gz

but it seems a bad design decision to use r-base-core as the source
for the file.

Kind regards,

Christoph

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.72 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fonts-urw-base35 depends on:
ii  xfonts-utils  1:7.7+6

fonts-urw-base35 recommends no packages.

Versions of packages fonts-urw-base35 suggests:
pn  fonts-freefont-otf | fonts-freefont-ttf  
pn  fonts-texgyre

-- no debconf information



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#1021804: gnome-terminal: Wrong window name "Preferences" showing up in Gnome Dash and the application switcher (Alt-Tab) for running terminals

[Jeremy Bicha]

On Sat, Oct 15, 2022 at 12:03 AM Ronny Rentner
 wrote:
> when I run Gnome Terminal, it shows up under the name "Preferences" in Gnome
> Dash and in the application switcher. This also makes the application grouping
> fail in Gnome Dash.
>
> This seems to be caused by having 2 .desktop files:
> /usr/share/applications/org.gnome.Terminal.Preferences.desktop
> /usr/share/applications/org.gnome.Terminal.desktop
>
> After I have manually deleted the org.gnome.Terminal.Preferences.desktop file,
> the problem goes away.

It works for me. Please reinstall gnome-terminal. Then close all your
terminals and then try opening the terminal again.

Thank you,
Jeremy Bicha

Bug#1021844: barrier: uscan fails to determine upstream version

[Lorenz Kästle]

Package: barrier
Version: 2.4.0+dfsg-2+b1
Severity: normal
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,
The debian package tracking system can not determine the upstream
version of this software. This is like related to some changes
on github.com which breaks the uscan workflow.
My best guess so far is, that they are using Javascript now to
display the release files and this does not work outside of a browser.

Using the uscan git mode though works, at least for some of my work
recently.
I am attaching a patch for the watch file.


- - -- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages barrier depends on:
ii  libavahi-compat-libdnssd1  0.8-6
ii  libc6  2.35-3
ii  libgcc-s1  12.2.0-3
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5network5 5.15.4+dfsg-5
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libssl33.0.5-2
ii  libstdc++6 12.2.0-3
ii  libx11-6   2:1.8.1-2
ii  libxext6   2:1.3.4-1+b1
ii  libxi6 2:1.8-1+b1
ii  libxinerama1   2:1.1.4-3
ii  libxrandr2 2:1.5.2-2+b1
ii  libxtst6   2:1.2.3-1.1
ii  openssl3.0.5-2

barrier recommends no packages.

barrier suggests no packages.

- - -- debconf-show failed

- -BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEKAfQE9RqCCOLiHBM/scKxdDQy9UFAmNLD50ACgkQ/scKxdDQ
y9XRZA//aLBrYPDbHWvRjQ/VvaTeG98Q7/zGzaJPk13ic/1G1+6wSH/yiWKjytOU
Zfgwg9WXTgEL+FwPSJsO8l9UwILX9YSg3eNS+8OeVy+sBH39NgARcW+++MUbP0WT
CDFsMb1ggMjmnAzgp4i8rr8jtxu9ltEWW26LbTvlR7xO3YseMulhh08J6/O7Ijyp
8SAFAZdqFRAiMEDzSljU8Wt4mu0M2Sue3ZNVkSrEmMI3JoEcw5RrzMdsDranVNLc
na7Vk6se3BeFvljWnU6C9ol+l5t1X4DzQroxhReVtwKAtSjeBN5qBhW1OiW8oZFI
eF3UUNJo3CfsEZcdkYv0o0sHCZXHm/rGZufX8jrHJxZOLLXHMSyrldLiVNt3a/kx
HpDr8B1QBPpx/dXSf4FHvKqFdxolYno/67Vsaziw2rO7p5SHb9MFEtDgDFhIBP3T
I5SdVJpR9NqzY/Xmtlvow68jsBlLGccP5M+0uZL3IRWVLKzZwSOi1QdGI7/rTU6v
ztMLXkpMQfgRTQYeG2vk0rTmXcMMgrCmyQZGjbWnHN4NRyQ8RT0Pj7+W7cLzG31g
gfvn4CRHHFNkdYfTtd/xnKdjQoeMXC8khmU5BYrVLghIfIr8LMh+pJmS85g0hjNP
g+7OWzNC4+LUrA7xjfYNTw1Vs/G48hMfBjSvbspjZB3HWqWv6Pg=
=nSNv
- -END PGP SIGNATURE-

*** git/barrier/watchfile.barrier
diff --git a/debian/watch b/debian/watch
index 358e47e..faed7ad 100644
- --- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 version=4
- -opts="dversionmangle=s/\+dfsg$//,repacksuffix=+dfsg" \
- -https://github.com/debauchee/barrier/releases 
.*/v?([\d\.]+)\.tar\.(?:bz2|gz|xz)
+opts="mode=git,gitmode=full,dversionmangle=s/\+dfsg$//,repacksuffix=+dfsg" \
+https://github.com/debauchee/barrier refs/tags/v@ANY_VERSION@

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEKAfQE9RqCCOLiHBM/scKxdDQy9UFAmNLEPYACgkQ/scKxdDQ
y9XY6g/+IankO9oqt/h9KtKLnupqUu+jtonwjXMG3X3YOqSRTjxNElzJkIMr2VBa
ynxkgOKEU2qriLJLmdxNHW3ixbssqyQaltqjjAfeHMrX75Lzw66N2YaaltcVPb1/
TNvWPj8Gwt5Dd3LK04IqHtjupA/6mbqj7yMO3nPCv2LE/Hgt1NWsSA33y7LJ546o
bumyM5nP98XsDCXpcR1W+mb3h4D5RWBOhM98ZGnltn4CPQ7NxC4ILpwJj5bEgIvS
geD+d1PlOowgI4GiIaBZDMYo2q+SiJWfZee3ZijnfsXX+qC2u0smp8f4zEUt8Hf3
sqrhMJ2jBmAp7f053Qv0mZ6jtjA9LbuhiGDEGkOQYMSB4YSh2hcRxN5Uk0RlZfcv
r5huHrfdDzD8Q45w2n0gDwT97k2+9qVhsxE1zu7zc28MkesqNUVTrlkUT13P2++o
kw44QLy1S+78ij8qb5g4ANNvoS30jUtTZ5I/QuZ09RiRzEAnYfahohCnO6NZflFD
lAVuEwxCWF3BlDQG09LoBY6vu42QP/vGnwDeOxqGdFLDd8E6Tg94Y1hQ9mO8ePr9
GjWIO87Yg0mLPO8roniFo12COkE6yLCTY92+JDTZHxQ//ST67OZ2XdWkL1BsKFU9
lizlduoOyXr/molY3dxm50W7gyhNwKSTBoNQBC51mqht7goijm8=
=vOCl
-END PGP SIGNATURE-

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#938249: python-virtualenv: Python2 removal in sid/bullseye - reopen 938249

[Micha Lenk]

Control: tags -1 patch

I suggest to drop the autopkgtests which still depend on Python2, namely 
the "pypy" and the "python2" tests.


See the attached patch for the proposed changes.

For your convenience I've also created a merge request on Salsa:
https://salsa.debian.org/python-team/packages/python-virtualenv/-/merge_requests/4

Best regards,
Micha
From 731efe4455b5157df4543873c23486a56c03be17 Mon Sep 17 00:00:00 2001
From: Micha Lenk 
Date: Sat, 15 Oct 2022 21:03:31 +0200
Subject: [PATCH] Drop pypy and python2 autopkgtests (closes: #938249)

... as the binary package python-six got removed from the archive. Python 3
equivalents for these tests already exist (pypy3 and python3).
---
 debian/changelog |  8 
 debian/tests/control | 20 
 debian/tests/pypy|  2 --
 debian/tests/python2 |  2 --
 4 files changed, 8 insertions(+), 24 deletions(-)
 delete mode 100755 debian/tests/pypy
 delete mode 100755 debian/tests/python2

diff --git a/debian/changelog b/debian/changelog
index 7615c3e..93b3f9f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-virtualenv (20.16.3+ds-4.1) UNRELEASED; urgency=medium
+
+  * Drop pypy and python2 autopkgtests (closes: #938249) as the binary package
+python-six got removed from the archive. Python 3 equivalents for these
+tests already exist (pypy3 and python3).
+
+ -- Micha Lenk   Sat, 15 Oct 2022 20:57:43 +0200
+
 python-virtualenv (20.16.3+ds-4) unstable; urgency=medium
 
   * Depend on python3-distutils when we have setuptools < 60, which doesn't
diff --git a/debian/tests/control b/debian/tests/control
index 4b4bab2..6bc7189 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -8,30 +8,10 @@ Tests: setup-local-3
 Depends: python3-filelock, @
 Restrictions: allow-stderr
 
-Tests: python2
-Depends: python-six,
- python2,
- python2-pip-whl,
- python2-setuptools-whl,
- python2-wheel-whl,
- shunit2,
- virtualenv,
-Restrictions: allow-stderr, skip-not-installable
-
 Tests: python3
 Depends: python3-all, python3-six, shunit2, virtualenv
 Restrictions: allow-stderr
 
-Tests: pypy
-Depends: pypy,
- pypy-six,
- python2-pip-whl,
- python2-setuptools-whl,
- python2-wheel-whl,
- shunit2,
- virtualenv,
-Restrictions: allow-stderr, skip-not-installable
-
 Tests: pypy3
 Depends: pypy3, python3-six, shunit2, virtualenv
 Restrictions: allow-stderr
diff --git a/debian/tests/pypy b/debian/tests/pypy
deleted file mode 100755
index 729c532..000
--- a/debian/tests/pypy
+++ /dev/null
@@ -1,2 +0,0 @@
-#!/bin/sh
-exec debian/tests/shunit2-tests.sh pypy
diff --git a/debian/tests/python2 b/debian/tests/python2
deleted file mode 100755
index c7ba41f..000
--- a/debian/tests/python2
+++ /dev/null
@@ -1,2 +0,0 @@
-#!/bin/sh
-exec debian/tests/shunit2-tests.sh python2.7
-- 
2.30.2

Bug#1021842: emacs: trampoline compilation error when running buttercup self-tests

[David Bremner]

Package: emacs
Version: 1:28.2+1-1
Severity: important
X-Debbugs-Cc: debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Here's the reproducer (tested on a couple of different debian testing
/ unstable machines). This is with Debian's build of emacs 28.2. I
cannot replicate the issue with upstream emacs 28.2 built from source

#--
tempdir=$(mktemp -d)
cd $tempdir
git clone https://github.com/jorgenschaefer/emacs-buttercup.git
cd emacs-buttercup
export HOME=/nope
rm *.elc
emacs -Q -batch -L . -f batch-byte-compile buttercup.el buttercup-compat.el
emacs -Q -batch -L . -l buttercup -f buttercup-run-discover
#--

For me this yields errors of the following form

Traceback (most recent call last):
  normal-top-level()
  command-line()
  command-line-1(("-L" "." "-l" "buttercup" "-f" "buttercup-run-discover"))
  buttercup-run-discover()
  buttercup-run()
  buttercup--run-suites((#s(buttercup-suite "The buttercup--enclosed-expr fu...
  mapc(buttercup--run-suite (#s(buttercup-suite "The buttercup--enclosed-exp...
  buttercup--run-suite(#s(buttercup-suite "For stale `elc' file checks" nil ...
  buttercup--run-suite(#s(buttercup-suite "`buttercup-check-for-stale-elc'" ...
  buttercup--run-spec(#s(buttercup-spec "should do nothing for `el' files" #...
  buttercup--update-with-funcall(#s(buttercup-spec "should do nothing for `e...
  apply(buttercup--funcall (closure ((elc-time . 2) (el-time . 3) t) nil (sp...
  buttercup--funcall((closure ((elc-time . 2) (el-time . 3) t) nil (spy-on '...
  apply((closure ((elc-time . 2) (el-time . 3) t) nil (spy-on 'file-attribut...
  (closure ((elc-time . 2) (el-time . 3) t) nil (spy-on 'file-attributes :an...
  spy-on(file-attributes :and-call-fake (closure ((elc-time . 2) (el-time . ...
  buttercup--spy-on-and-call-replacement(file-attributes (lambda ( args...
  comp-subr-trampoline-install(file-attributes)
  comp-trampoline-compile(file-attributes)
  error("Cannot find suitable directory for output in `native-comp-eln-load-...
error: (error "Cannot find suitable directory for output in 
‘native-comp-eln-load-path’")





- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-rc7-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs depends on:
ii  emacs-gtk  1:28.2+1-1

emacs recommends no packages.

emacs suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmNLCgUACgkQA0U5G1Wq
FSH2+hAAsJ4cDWeqp2qV1uPpUmrhKbaei9A9W4qOvOfksXWn17NfCGyw8vVYzvkr
vcpPQ7KaKy3tALTAENalsUyM7nF+KHQAQQmLOFET0Fwy3Qhx14ZCUbE3+mGy7bMQ
pNt8+0vzcmJ1Oq4J4/81AdZqC6LDwrDTayl7gvOscQLuNhrKz8IrgQtkiNOIBbTl
0KkK3ZvtGqdfprBChziDnzGrWVxLsh5xcenTTh4N5/ysFq+zgPHb/Yp048wLdy+7
wn+eu4z/0xY9EYjixn50YjwRuTFDnCOM764Q71nV6KdveWYWDQScu1aIxQzi+wVM
DutpmmRD4wPnwG3ePVFAz0zsAFhxYt1jXhGzAUkYV/gFxY+eHH31V4I6wUJhLmv1
7ji//z2+1xcDQA+5whs30iq84Q9iT5yeHgJVYSWD30ALeg23/pSnBEWsG6AXWTbV
xAMYlUBW2wLpVocuBtINm/93qLhXJktM8o3ZZcKtjuQM/YqXhTaUfWtvfNRIq1Py
VvMDzA2TZVPJCqL/isLnPR9yIprf7F4UZcmDxEQFmXKj1T8o679zDAqHvUmQiZn3
+uuVjNUTLRzDeBCF6wctY4TgIAj2ARDtsojFLkkc0txZ/VAZPOsPGvzCvqFeuunG
Q9gnpKU0oU35wDll5WG7FDZ7HMShbjPZG+DjpnL+V5CkrbcByTg=
=8U6X
-END PGP SIGNATURE-

Bug#1021841: setbfree FTCBFS -- multiple reasons

[Nilesh Patra]

Package: setbfree
Version: 0.8.11-2
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-cr...@lists.debian.org

Hi,

setbfree Fails to cross build because:

- It hard-codes pkg-config everywhere and that defaults to the build 
architecture
while cross-building. This can be resolved by using PKG_CONFIG and setting it
to this value only if it is previously un-set.
And PKG_CONFIG can be set to the pkg-config prefixed with the 
architecure-triplet
while cross building.

- It uses strip extensively. While for debian systems, simply removing the strip
call from all makefiles could be OK, since dh_strip will simply take care of it.
But,  it'd be hard to make things upstream-able
if desired at some point. So I sent STRIP to the -strip for
cross builds.

A patch can be found attached with this mail.

Thanks!


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 131fbc61c9baf052d0693b7f7d63d69fcd970d14 Mon Sep 17 00:00:00 2001
From: Nilesh Patra 
Date: Sat, 15 Oct 2022 22:19:54 +0530
Subject: [PATCH] Get package cross-building

---
 debian/patches/cross.patch | 252 +
 debian/patches/series  |   1 +
 debian/rules   |   9 +-
 3 files changed, 261 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/cross.patch

diff --git a/debian/patches/cross.patch b/debian/patches/cross.patch
new file mode 100644
index 000..1dd9be8
--- /dev/null
+++ b/debian/patches/cross.patch
@@ -0,0 +1,252 @@
+--- a/b_chorato/Makefile
 b/b_chorato/Makefile
+@@ -3,7 +3,7 @@
+ 
+ LOADLIBES = -lm
+ override CFLAGS+= -I../src
+-override CFLAGS+=`pkg-config --cflags lv2` -fvisibility=hidden
++override CFLAGS+=`$(PKG_CONFIG) --cflags lv2` -fvisibility=hidden
+ 
+ targets=
+ 
+--- a/b_overdrive/Makefile
 b/b_overdrive/Makefile
+@@ -12,16 +12,16 @@
+   targets+=lv2
+ endif
+ 
+-ifeq ($(shell pkg-config --exists liblo && echo yes), yes)
+-  override CFLAGS+=-DHAVE_LIBLO `pkg-config --cflags liblo`
+-  LOADLIBES+=`pkg-config --libs liblo`
++ifeq ($(shell $(PKG_CONFIG) --exists liblo && echo yes), yes)
++  override CFLAGS+=-DHAVE_LIBLO `$(PKG_CONFIG) --cflags liblo`
++  LOADLIBES+=`$(PKG_CONFIG) --libs liblo`
+ endif
+ 
+-ifeq ($(shell pkg-config --exists jack && echo yes)$(OVERDRIVEJACK), yesyes)
++ifeq ($(shell $(PKG_CONFIG) --exists jack && echo yes)$(OVERDRIVEJACK), 
yesyes)
+   targets+=jboverdrive
+   binaries+=jboverdrive
+-  override CFLAGS+=-DHAVE_JACK `pkg-config --cflags jack`
+-  LOADLIBES+=`pkg-config --libs jack`
++  override CFLAGS+=-DHAVE_JACK `$(PKG_CONFIG) --cflags jack`
++  LOADLIBES+=`$(PKG_CONFIG) --libs jack`
+ endif
+ 
+ OVMSRC=\
+--- a/b_reverb/Makefile
 b/b_reverb/Makefile
+@@ -3,7 +3,7 @@
+ include ../git2lv2.mk
+ 
+ LOADLIBES = -lm
+-override CFLAGS+=`pkg-config --cflags lv2` -fvisibility=hidden
++override CFLAGS+=`$(PKG_CONFIG) --cflags lv2` -fvisibility=hidden
+ 
+ targets=reverb.o
+ 
+--- a/b_synth/Makefile
 b/b_synth/Makefile
+@@ -4,7 +4,7 @@
+ 
+ LOADLIBES = -lm
+ override CFLAGS+= -I../src -I../b_overdrive -I../b_reverb -I../b_whirl
+-override CFLAGS+=`pkg-config --cflags lv2` -DLV2SYNTH -fvisibility=hidden
++override CFLAGS+=`$(PKG_CONFIG) --cflags lv2` -DLV2SYNTH -fvisibility=hidden
+ targets=
+ 
+ LV2NAME=b_synth
+--- a/b_whirl/Makefile
 b/b_whirl/Makefile
+@@ -7,7 +7,7 @@
+ endif
+ 
+ LOADLIBES = -lm
+-override CFLAGS+=`pkg-config --cflags lv2` -fvisibility=hidden
++override CFLAGS+=`$(PKG_CONFIG) --cflags lv2` -fvisibility=hidden
+ 
+ targets=whirl.o eqcomp.o
+ 
+@@ -25,7 +25,7 @@
+   $(warning This plugin GUI needs https://github.com/x42/robtk)
+   $(info set the RW environment variale to the location of the robtk 
headers)
+ else
+-  HAVE_RTK = $(shell pkg-config --exists pango cairo $(PKG_GL_LIBS) && 
echo yes)
++  HAVE_RTK = $(shell $(PKG_CONFIG) --exists pango cairo $(PKG_GL_LIBS) && 
echo yes)
+ endif
+ 
+ ifeq ($(HAVE_RTK), yes)
+@@ -79,7 +79,7 @@
+   -shared $(LV2LDFLAGS) $(LDFLAGS)
+ 
+ JACKCFLAGS=$(CFLAGS) $(GLUICFLAGS) $(LIC_CFLAGS) -Wno-unused-function
+-JACKCFLAGS+=`pkg-config --cflags jack lv2 pango pangocairo $(PKG_GL_LIBS)`
++JACKCFLAGS+=`$(PKG_CONFIG) --cflags jack lv2 pango pangocairo $(PKG_GL_LIBS)`
+ JACKLIBS=-lm $(GLUILIBS) $(LIC_LOADLIBES)
+ 
+ $(eval x42_whirl_JACKSRC = lv2.c whirl.c)
+--- a/common.mak
 b/common.mak
+@@ -29,17 +29,18 @@
+ override CFLAGS += -DVERSION="\"$(VERSION)\""
+ 
+ STRIP?= strip
++PKG_CONFIG ?= pkg-config
+ 
+ CXXFLAGS ?= $(OPTIMIZATIONS) -Wall
+ GLUICFLAGS=-I. -I.. -Wno-unused-function
+ STRIPFLAGS=-s
+ 
+ # check for LV2
+-LV2AVAIL=$(shell pkg-config --exists lv2 && echo yes)
++LV2AVAIL=$(shell $(PKG_CONFIG) 

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

Bug#1021840: mention borg compact in NEWS.Debian

[Joey Hess]

Package: borgbackup
Version: 1.2.2-2
Severity: wishlist

borg compact is needed to actually free up pruned space, which was not
the case with the version in stable. I noticed this only after my backup
disk overflowed, and I think that having a mention of it in NEWS.Debian
might have made me aware of it earlier.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages borgbackup depends on:
ii  libacl12.3.1-1
ii  libc6  2.35-3
ii  liblz4-1   1.9.4-1
ii  libssl33.0.5-4
ii  libxxhash0 0.8.1-1
ii  libzstd1   1.5.2+dfsg-1
ii  python33.10.6-1
ii  python3-msgpack1.0.3-1+b1
ii  python3-packaging  21.3-1.1
ii  python3-pkg-resources  65.3.0-1.1

Versions of packages borgbackup recommends:
ii  fuse3 [fuse] 3.11.0-1
ii  python3-llfuse   1.4.1+dfsg-2+b1
ii  python3-pyfuse3  3.2.1-1+b1

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1017881: ITA: unclutter-xfixes -- hide the X mouse cursor after a period of inactivity, using XFixes

[Stefan Kangas]

Sean Whitton  writes:

> Sweet, thanks.  I can sponsor the upload if you want.

Thank you, that will be appreciated.

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 ) 
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 ) 
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

Bug#1017881: ITA: unclutter-xfixes -- hide the X mouse cursor after a period of inactivity, using XFixes

[Sean Whitton]

Hello,

On Sat 15 Oct 2022 at 05:36PM GMT, Stefan Kangas wrote:

> retitle 1017881 ITA: unclutter-xfixes -- hide the X mouse cursor after
> a period of inactivity, using XFixes
> owner 1017881 !
> thanks
>
> Hi,
>
> Thanks for your work on the unclutter-xfixes package. I intend to adopt
> it, and work on getting the new upstream release into bookworm.
>
> You will be able to track my progress at:
> https://salsa.debian.org/skangas/unclutter-xfixes

Sweet, thanks.  I can sponsor the upload if you want.

-- 
Sean Whitton


signature.asc
Description: PGP signature

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;

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;

Bug#1017881: ITA: unclutter-xfixes -- hide the X mouse cursor after a period of inactivity, using XFixes

[Stefan Kangas]

retitle 1017881 ITA: unclutter-xfixes -- hide the X mouse cursor after
a period of inactivity, using XFixes
owner 1017881 !
thanks

Hi,

Thanks for your work on the unclutter-xfixes package. I intend to adopt
it, and work on getting the new upstream release into bookworm.

You will be able to track my progress at:
https://salsa.debian.org/skangas/unclutter-xfixes

Best regards,
Stefan Kangas

Bug#938249: python-virtualenv: Python2 removal in sid/bullseye - reopen 938249

[Micha Lenk]

Hi,

On Sat, 15 Oct 2022 19:16:05 +0200 I wrote:
 Is there any reason not to close this bug now?

Yes, there are Python 2 dependencies in autopkgtests 
(debian/tests/control) to clean up.


Regards,
Micha

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#1004308: smokeping: New upstream version 2.8.2 needs to be packaged

[Alexey Vazhnov]

Gabriel, please check 
https://salsa.debian.org/debian/smokeping/-/merge_requests/5

I think you should subscribe to notifications in 
https://salsa.debian.org/debian/smokeping (there is a "bell" button
with notification settings) to not miss another merge requests.

What is our next step (even without Nginx configuration file)?

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

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

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

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

Bug#1014815: kiwipy initial packaging

[Bastian Germann]

Am 15.10.22 um 19:06 schrieb Bastian Germann:

any news on downgrading aio-pika?


Forget, just saw 8.0 being released which should have this fixed.
So no need to downgrade.

Bug#1021839: info -w is slow for man pages

[Jakub Wilk]

Package: info
Version: 6.8-6

I noticed that "info -w" is puzzlingly slow when the argument is a man 
page:


$ time -p info -w ffmpeg-all
*manpages*
real 1.06
user 1.47
sys 0.16

In contrast, "man -w" is near-instantaneous:

$ time -p man -w ffmpeg-all
/usr/share/man/man1/ffmpeg-all.1.gz
real 0.05
user 0.04
sys 0.01

Apparently this is because "info -w" calls "man -a", which is a very 
inefficent way to check if a man page exists:


$ strace -f -e trace=execve -o '| grep -w man >&2' info -w ffmpeg-all > 
/dev/null
1142  execve("/usr/bin/man", ["/usr/bin/man", "-a", "ffmpeg-all"], 
0xfffd7dd4 /* 52 vars */) = 0


-- System Information:
Architecture: i386

Versions of packages info depends on:
ii  libc6 2.35-3
ii  libtinfo6 6.3+20220423-2
ii  install-info  6.8-6

--
Jakub Wilk

Bug#938249: python-virtualenv: Python2 removal in sid/bullseye - reopen 938249

[Micha Lenk]

user debian-rele...@lists.debian.org
usertags 938249 + bsp-2022-10-de-karlsruhe
thanks

Hi Sandro,

On Fri, 19 Jun 2020 22:40:58 -0400 Sandro Tosi  wrote:

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:python-virtualenv)Testsuite-Triggers->python-six
(source:python-virtualenv)Testsuite-Triggers->python2

Re-opening, so that they can be taken care of.


I've looked into what could be the remaining pieces to clean up.

* python-six is gone since the upload of six 1.16.0-4 (2022-07-28).
* python2 removal is the whole point of this bug.

I'd say this Debian bug was correctly closed in version 20.0.10-1.
Is there any reason not to close this bug now?

Regards,
Micha

Bug#1021838: bullseye-pu: package binfmt-support/2.2.1-1+deb11u1

[Colin Watson]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
https://bugs.debian.org/1012154 reported a startup issue due to a race
between systemd-binfmt.service and binfmt-support.service (which has
probably been around for a long time).  https://bugs.debian.org/1021822
mentions that it would be helpful to have the fix for this in stable as
well, which I agree with.

[ Impact ]
binfmt-support.service will sometimes fail to start, so binary format
specifications registered with it may or may not do anything depending
on luck at boot time.

[ Tests ]
None, sorry.

[ Risks ]
The patch came from a systemd maintainer and is pretty simple: it just
ensures ordering.  I haven't heard of any issues introduced by it in
bookworm.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]

(of course I'll apply s/UNRELEASED/bullseye/ before uploading)

diff -Nru binfmt-support-2.2.1/debian/.git-dpm 
binfmt-support-2.2.1/debian/.git-dpm
--- binfmt-support-2.2.1/debian/.git-dpm2020-04-17 20:46:23.0 
+0100
+++ binfmt-support-2.2.1/debian/.git-dpm2022-10-15 18:02:17.0 
+0100
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-74fe6952c89159bff00252265ab7c167ec44aad5
-74fe6952c89159bff00252265ab7c167ec44aad5
+d8f17525d5d66a4c6694ec9ebf32a174ea74f3e3
+d8f17525d5d66a4c6694ec9ebf32a174ea74f3e3
 74fe6952c89159bff00252265ab7c167ec44aad5
 74fe6952c89159bff00252265ab7c167ec44aad5
 binfmt-support_2.2.1.orig.tar.gz
diff -Nru binfmt-support-2.2.1/debian/changelog 
binfmt-support-2.2.1/debian/changelog
--- binfmt-support-2.2.1/debian/changelog   2020-04-17 20:46:23.0 
+0100
+++ binfmt-support-2.2.1/debian/changelog   2022-10-15 18:02:19.0 
+0100
@@ -1,3 +1,10 @@
+binfmt-support (2.2.1-1+deb11u1) UNRELEASED; urgency=medium
+
+  * Run binfmt-support.service after systemd-binfmt.service (thanks, Michael
+Biebl; closes: #1012154, #1021822).
+
+ -- Colin Watson   Sat, 15 Oct 2022 18:02:19 +0100
+
 binfmt-support (2.2.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru binfmt-support-2.2.1/debian/patches/series 
binfmt-support-2.2.1/debian/patches/series
--- binfmt-support-2.2.1/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ binfmt-support-2.2.1/debian/patches/series  2022-10-15 18:02:17.0 
+0100
@@ -0,0 +1 @@
+systemd-ordering.patch
diff -Nru binfmt-support-2.2.1/debian/patches/systemd-ordering.patch 
binfmt-support-2.2.1/debian/patches/systemd-ordering.patch
--- binfmt-support-2.2.1/debian/patches/systemd-ordering.patch  1970-01-01 
01:00:00.0 +0100
+++ binfmt-support-2.2.1/debian/patches/systemd-ordering.patch  2022-10-15 
18:02:17.0 +0100
@@ -0,0 +1,43 @@
+From d8f17525d5d66a4c6694ec9ebf32a174ea74f3e3 Mon Sep 17 00:00:00 2001
+From: Michael Biebl 
+Date: Thu, 2 Jun 2022 12:56:11 +0200
+Subject: Run binfmt-support.service after systemd-binfmt.service
+
+This fixes a race condition during boot when both services try to access
+/proc/sys/fs/binfmt_misc/register at the same time which can lead to the
+following error:
+
+ systemd[1]: Starting Enable support for additional executable binary 
formats...
+ update-binfmts[536]: update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: File exists
+ update-binfmts[536]: update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: File exists
+ update-binfmts[536]: update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: File exists
+ update-binfmts[536]: update-binfmts: exiting due to previous errors
+ systemd[1]: binfmt-support.service: Main process exited, code=exited, 
status=2/INVALIDARGUMENT
+ systemd[1]: binfmt-support.service: Failed with result 'exit-code'.
+ systemd[1]: Failed to start Enable support for additional executable binary 
formats.
+
+Fixes Debian bug #1012154.
+
+Origin: upstream, 
https://gitlab.com/cjwatson/binfmt-support/-/commit/54f0e1af8ac6bcaf4594747df8965b5c5bdd3744
+Bug-Debian: https://bugs.debian.org/1012154
+Bug-Debian: https://bugs.debian.org/1021822
+Last-Update: 2022-10-15
+
+Patch-Name: systemd-ordering.patch
+---
+ init/systemd/binfmt-support.service.in | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/init/systemd/binfmt-support.service.in 
b/init/systemd/binfmt-support.service.in
+index 25c30e2..f6d0d4d 100644
+--- a/init/systemd/binfmt-support.service.in
 b/init/systemd/binfmt-support.service.in
+@@ -20,7 +20,7 @@
+ Description=Enable support for additional executable binary formats
+ Documentation=man:update-binfmts(8)
+ DefaultDependencies=false
+-After=local-fs.target proc-sys-fs-binfmt_misc.automount
++After=local-fs.target proc-sys-fs-binfmt_misc.automount systemd-binfmt.service
+ 
+ [Service]
+ Type=oneshot

Bug#1021822: binfmt-support: conflicts with systemd-binfmt.service on Debian stable

[Colin Watson]

On Sat, Oct 15, 2022 at 08:26:51PM +0800, Rongrong wrote:
> As already reported in #1012154, a race condition between binfmt-
> support.service and systemd-binfmt.service could occur. 2.2.2-1 in
> testing/unstable has fixed the issue. However, stable have not got that
> issue fixed. Could you backport 2.2.2 or only the new systemd service
> file to stable?

Seems reasonable.  I've filed a request with the stable release team for
approval.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

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=amd64=0.2.4%2Bdfsg-3%2Bb1=1663544975=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

Bug#1014815: kiwipy initial packaging

[Bastian Germann]

Hi Guilherme,

any news on downgrading aio-pika?

Thanks,
Bastian

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=amd64=2.0.1-5=1661980780=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

Bug#1021835: libwebrtc-audio-processing-dev: missing dependencies

[Thomas Uhle]

Package: libwebrtc-audio-processing-dev
Version: 1.0-0.2
Severity: normal
Tags: patch, fixed-upstream
Followup-For: Bug #934811
X-Debbugs-Cc: Jonas Smedegaard 

Dear maintainers,

some of the header files from version 1.0 of webrtc-audio-processing 
directly include header files from Abseil.  Thus, the binary package 
libwebrtc-audio-processing-dev should also depend on libabsl-dev.


Another issue is that the generated pkg-config data files 
webrtc-audio-coding-1.pc and webrtc-audio-processing-1.pc yet do not 
include the dependencies on the needed Abseil libraries because the 
current Meson build script still figures out these dependencies via 
CMake instead of using pkg-config.
This has already been fixed upstream as well as the missing dependency 
for using absl::optional<>.  You could pick up the following commits:


* Use pkg-config for abseil-cpp detection if available
  
https://gitlab.freedesktop.org/pulseaudio/webrtc-audio-processing/-/commit/8bf9efad15bdb8438eb858d3f8ed4a8ea2b21ff0

* Add missing absl library for bad_optional_access
  
https://gitlab.freedesktop.org/pulseaudio/webrtc-audio-processing/-/commit/0cc2ebeda2faf60f3367bd5e88e1247455dfcfee

If you don't like to pick up partial commits, you'll probably also need 
to pick up this commit from upstream:


* build: Add library-based absl detection as a fallback
  
https://gitlab.freedesktop.org/pulseaudio/webrtc-audio-processing/-/commit/e74894baebe0bba7a7fe37ae0a46a2e9b1b2e021


Thank you in advance!

Best regads,

Thomas Uhle



-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.10.0-18-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwebrtc-audio-processing-dev depends on:
ii  libwebrtc-audio-processing1  1.0-0.2

libwebrtc-audio-processing-dev recommends no packages.

libwebrtc-audio-processing-dev suggests no packages.

Bug#1021834: libwebrtc-audio-processing1: please split into libwebrtc-audio-coding-1-0 and libwebrtc-audio-processing-1-0

[Thomas Uhle]

Package: libwebrtc-audio-processing1
Version: 1.0-0.2
Severity: normal
Tags: patch, fixed-upstream
Followup-For: Bug #934811
X-Debbugs-Cc: Jonas Smedegaard 

Dear maintainers,

could you please introduce two new binary packages for the libraries 
libwebrtc-audio-coding-1.so.0 and libwebrtc-audio-processing-1.so.0 
built from version 1.0 of the source package webrtc-audio-processing 
that would replace the current binary package so that the new packages 
could be installed next to the current libwebrtc-audio-processing1. 
That would be necessary because the library names have changed as well 
as the API and the current versions of PulseAudio, PipeWire and 
GStreamer's Bad Plugins still need the older version 0.3.x of 
webrtc-audio-processing to compile.


Cherry-picking the following commit from upstream will help you in doing 
so:


* build: Split out iSAC VAD sources into a separate dependency
https://gitlab.freedesktop.org/pulseaudio/webrtc-audio-processing/-/commit/6e37f37c4ea8790760b4c55d9ce9024a7e7bf260


Thank you in advance!

Best regads,

Thomas Uhle



-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.10.0-18-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwebrtc-audio-processing1 depends on:
ii  libabsl20200923  0~20200923.3-2
ii  libc62.31-13+deb11u4
ii  libgcc-s110.2.1-6
ii  libstdc++6   10.2.1-6

libwebrtc-audio-processing1 recommends no packages.

libwebrtc-audio-processing1 suggests no packages.

Bug#1007287: xfsdump: please consider upgrading to 3.0 source format

[Bastian Germann]

On Tue, 15 Mar 2022 08:52:04 +0100 Lucas Nussbaum  wrote:

This package is a native package, so the likely target is 3.0 (native), not
3.0 (quilt).


There is no reason for this package to be native, so the 3.0 (quilt)
format should be preferred for any new upload.

Nathan, I can support with uploading the current version if you do not have the 
time for it.

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=amd64=1.32.3-1=1665831409=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=amd64=2.184%2Bv7%2Bdfsg-1=1665041296=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

Bug#1021629: texinfo: with HTML output, @minus{} is converted to a hyphen instead of a real minus character

[Hilmar Preuße]

Control: tags -1 + fixed-upstream

Am 12.10.2022 um 01:17 teilte Vincent Lefevre mit:

Hi,


With HTML output, @minus{} is converted to a hyphen instead of
a real minus character (U+2212 MINUS SIGN).

The Texinfo manual says:

11.8.9 '@minus' (-): Inserting a Minus Sign
---


Fixed in upstream git:

commit 8a14a5047246ac70d53622e242ab18708a8f95b7
Author: Patrice Dumas 
Date:   Thu Oct 13 21:39:42 2022 +0200

Use  for @minus{} in HTML output

* tp/Texinfo/Convert/Converter.pm
(%xml_text_entity_no_arg_commands_formatting): use  for
@minus{}.  Report from Vincent Lefèvre.

Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

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=amd64=1.3-1=1664293055=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#1019192: Upstream report

[Diederik de Haas]

Control: forwarded -1 
https://lore.kernel.org/lkml/c8c65713-5cda-43ad-8018-20f2e32e4...@t-8ch.de/T/#u

On Saturday, 15 October 2022 16:14:36 CEST Josh Triplett wrote:
> Someone diagnosed and reported this upstream at
> https://lore.kernel.org/lkml/c8c65713-5cda-43ad-8018-20f2e32e4...@t-8ch.de/T
> /#u

Thanks!

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

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

Bug#965576: gtk-sharp2: diff for NMU version 2.12.40-3.1

[Adrian Bunk]

Control: tags 965576 + patch
Control: tags 965576 + pending

Dear maintainer,

I've prepared an NMU for gtk-sharp2 (versioned as 2.12.40-3.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru gtk-sharp2-2.12.40/debian/changelog gtk-sharp2-2.12.40/debian/changelog
--- gtk-sharp2-2.12.40/debian/changelog	2020-02-25 00:06:17.0 +0200
+++ gtk-sharp2-2.12.40/debian/changelog	2022-10-15 19:01:59.0 +0300
@@ -1,3 +1,10 @@
+gtk-sharp2 (2.12.40-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * dh compat 5 -> 7. (Closes: #965576)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 19:01:59 +0300
+
 gtk-sharp2 (2.12.40-3) unstable; urgency=medium
 
   * [d457288] Fix build on newer Mono
diff -Nru gtk-sharp2-2.12.40/debian/compat gtk-sharp2-2.12.40/debian/compat
--- gtk-sharp2-2.12.40/debian/compat	2017-10-30 19:42:10.0 +0200
+++ gtk-sharp2-2.12.40/debian/compat	2022-10-15 19:01:53.0 +0300
@@ -1 +1 @@
-5
+7

Bug#1020453: docker.io: consider backporting to stable

[Felix Geyer]

On Wed, 21 Sep 2022 22:33:39 +0200 Libor Klepáč  wrote:

Package: docker.io
Followup-For: Bug #908603

Hello Maintainers,
could you please consider backporting docker.io version 20.10.17 to stable?

We are hitting problem with graylog docker image.
https://github.com/Graylog2/graylog-docker/issues/217


This specific fix (support for the clone3 syscall) has already been backported to 
20.10.5+dfsg1-1+deb11u1.

What version of docker.io do you have running?

Felix

Bug#1021830: openmpi: FTBFS: dpkg-shlibdeps: error: cannot find library libpmix.so.2 needed by debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so (ELF format: 'elf64-x8

[Sebastian Ramacher]

Source: openmpi
Version: 4.1.4-3
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=openmpi=amd64=4.1.4-3=1665582048=0

dh_shlibdeps 
-l/<>/debian/tmp///usr/lib/x86_64-linux-gnu/openmpi/lib -- 
--ignore-missing-info
install -d debian/openmpi-bin/DEBIAN
dpkg-shlibdeps -Tdebian/openmpi-bin.substvars 
-l/<>/debian/tmp///usr/lib/x86_64-linux-gnu/openmpi/lib 
--ignore-missing-info debian/openmpi-bin/usr/bin/oshmem_info 
debian/openmpi-bin/usr/bin/orterun debian/openmpi-bin/usr/bin/orte-server 
debian/openmpi-bin/usr/bin/orted debian/openmpi-bin/usr/bin/ompi_info 
debian/openmpi-bin/usr/bin/orte-info debian/openmpi-bin/usr/bin/orte-clean 
debian/openmpi-bin/usr/bin/opal_wrapper
dpkg-shlibdeps -Tdebian/libopenmpi3.substvars 
-l/<>/debian/tmp///usr/lib/x86_64-linux-gnu/openmpi/lib 
--ignore-missing-info 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/liboshmem.so.40.30.2 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libopen-rte.so.40.30.2 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi.so.40.30.4 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libopen-pal.so.40.30.2 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libompitrace.so.40.30.1 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_usempif08.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_usempi_ignore_tkr.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_mpifh.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_java.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_cxx.so.40.30.1 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmca_common_verbs.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmca_common_ompio.so.41.29.4 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmca_common_ucx.so.40.30.2 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmca_common_sm.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmca_common_monitoring.so.50.20.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmca_common_ofi.so.10.0.2 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_usempif08-gfortran.so.40.30.0
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_usempi_ignore_tkr-gfortran.so.40.30.0
 debian/libopenmpi3/usr/lib/x86_64-linux-gnu/libmpi_mpifh-gfortran.so.40.30.0 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/ompi_monitoring_prof.so 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_topo_treematch.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_vprotocol_pessimist.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_topo_basic.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_state_tool.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_state_orted.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_state_novm.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_state_hnp.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_sshmem_ucx.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_state_app.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_sshmem_sysv.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_spml_ucx.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_sshmem_mmap.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_shmem_sysv.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_shmem_posix.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_shmem_mmap.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_sharedfp_sm.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_sharedfp_lockedfile.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_sharedfp_individual.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_scoll_basic.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_scoll_mpi.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_slurm.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_ompi.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_orte.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_jsm.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_rtc_hwloc.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_flux.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_routed_radix.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_routed_direct.so
 
debian/libopenmpi3/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_routed_binomial.so
 

Bug#999191: manpages-tr: diff for NMU version 1.0.5.1-3.1

[Adrian Bunk]

Control: tags 999191 + patch
Control: tags 999191 + pending

Dear maintainer,

I've prepared an NMU for manpages-tr (versioned as 1.0.5.1-3.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -u manpages-tr-1.0.5.1/debian/changelog manpages-tr-1.0.5.1/debian/changelog
--- manpages-tr-1.0.5.1/debian/changelog
+++ manpages-tr-1.0.5.1/debian/changelog
@@ -1,3 +1,10 @@
+manpages-tr (1.0.5.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep}. (Closes: #999191)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 18:55:56 +0300
+
 manpages-tr (1.0.5.1-3) unstable; urgency=high
 
   * Conflicting files with man-db removed (Closes: #889805)
diff -u manpages-tr-1.0.5.1/debian/rules manpages-tr-1.0.5.1/debian/rules
--- manpages-tr-1.0.5.1/debian/rules
+++ manpages-tr-1.0.5.1/debian/rules
@@ -100,3 +100,5 @@
+build-arch: build
+build-indep: build
 binary: binary-indep binary-arch
 
-.PHONY: binary binary-arch binary-indep clean update-prune
+.PHONY: build-arch build-indep binary binary-arch binary-indep clean update-prune

Bug#1017154: fuse: diff for NMU version 2.9.9-5.1

[Adrian Bunk]

Control: tags 1017154 + pending

Dear maintainer,

I've prepared an NMU for fuse (versioned as 2.9.9-5.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru fuse-2.9.9/debian/changelog fuse-2.9.9/debian/changelog
--- fuse-2.9.9/debian/changelog	2021-02-26 18:12:50.0 +0200
+++ fuse-2.9.9/debian/changelog	2022-10-15 18:34:48.0 +0300
@@ -1,3 +1,10 @@
+fuse (2.9.9-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with glibc 2.34. (Closes: #1017154)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 18:34:48 +0300
+
 fuse (2.9.9-5) unstable; urgency=medium
 
   * Include HTML documentation in libfuse-dev (closes: #886449).
diff -Nru fuse-2.9.9/debian/patches/0001-util-ulockmgr_server.c-conditionally-define-closefro.patch fuse-2.9.9/debian/patches/0001-util-ulockmgr_server.c-conditionally-define-closefro.patch
--- fuse-2.9.9/debian/patches/0001-util-ulockmgr_server.c-conditionally-define-closefro.patch	1970-01-01 02:00:00.0 +0200
+++ fuse-2.9.9/debian/patches/0001-util-ulockmgr_server.c-conditionally-define-closefro.patch	2022-10-15 18:31:32.0 +0300
@@ -0,0 +1,63 @@
+From 5a43d0f724c56f8836f3f92411e0de1b5f82db32 Mon Sep 17 00:00:00 2001
+From: Sam James 
+Date: Sat, 24 Jul 2021 22:02:45 +0100
+Subject: util/ulockmgr_server.c: conditionally define closefrom (fix
+ glibc-2.34+)
+
+closefrom(3) has joined us in glibc-land from *BSD and Solaris. Since
+it's available in glibc 2.34+, we want to detect it and only define our
+fallback if the libc doesn't provide it.
+
+Bug: https://bugs.gentoo.org/803923
+Signed-off-by: Sam James 
+---
+ configure.ac   | 1 +
+ util/ulockmgr_server.c | 6 ++
+ 2 files changed, 7 insertions(+)
+
+diff --git a/configure.ac b/configure.ac
+index 9946a0e..a2d481a 100644
+--- a/configure.ac
 b/configure.ac
+@@ -55,6 +55,7 @@ fi
+ 
+ AC_CHECK_FUNCS([fork setxattr fdatasync splice vmsplice utimensat])
+ AC_CHECK_FUNCS([posix_fallocate])
++AC_CHECK_FUNCS([closefrom])
+ AC_CHECK_MEMBERS([struct stat.st_atim])
+ AC_CHECK_MEMBERS([struct stat.st_atimespec])
+ 
+diff --git a/util/ulockmgr_server.c b/util/ulockmgr_server.c
+index 273c7d9..a04dac5 100644
+--- a/util/ulockmgr_server.c
 b/util/ulockmgr_server.c
+@@ -22,6 +22,10 @@
+ #include 
+ #include 
+ 
++#ifdef HAVE_CONFIG_H
++	#include "config.h"
++#endif
++
+ struct message {
+ 	unsigned intr : 1;
+ 	unsigned nofd : 1;
+@@ -124,6 +128,7 @@ static int receive_message(int sock, void *buf, size_t buflen, int *fdp,
+ 	return res;
+ }
+ 
++#if !defined(HAVE_CLOSEFROM)
+ static int closefrom(int minfd)
+ {
+ 	DIR *dir = opendir("/proc/self/fd");
+@@ -141,6 +146,7 @@ static int closefrom(int minfd)
+ 	}
+ 	return 0;
+ }
++#endif
+ 
+ static void send_reply(int cfd, struct message *msg)
+ {
+-- 
+2.30.2
+
diff -Nru fuse-2.9.9/debian/patches/series fuse-2.9.9/debian/patches/series
--- fuse-2.9.9/debian/patches/series	2019-01-07 22:32:01.0 +0200
+++ fuse-2.9.9/debian/patches/series	2022-10-15 18:34:48.0 +0300
@@ -6,3 +6,4 @@
 0006-arm64.patch
 0007-Add_autofs_to_mountpoint_file_system_whitelist.patch
 0008-Add_FAT_to_mountpoint_file_system_whitelist.patch
+0001-util-ulockmgr_server.c-conditionally-define-closefro.patch

Bug#1020520: cxxtools: ftbfs with GCC-12

[Reiner Herrmann]

user debian-rele...@lists.debian.org
usertags 1020520 + bsp-2022-10-de-karlsruhe
tags 1020520 + fixed-upstream
thank you

A fix (including time.h) is available in the upstream repo:
https://github.com/maekitalo/cxxtools/commit/6e1439a108ce3892428e95f341f2d23ae32a590e

Bug#1016156: xtl: diff for NMU version 0.7.2-2.1

[Adrian Bunk]

Control: tags 1016156 + patch
Control: tags 1016156 + pending

Dear maintainer,

I've prepared an NMU for xtl (versioned as 0.7.2-2.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru xtl-0.7.2/debian/changelog xtl-0.7.2/debian/changelog
--- xtl-0.7.2/debian/changelog	2021-10-09 18:26:03.0 +0300
+++ xtl-0.7.2/debian/changelog	2022-10-15 17:43:56.0 +0300
@@ -1,3 +1,11 @@
+xtl (0.7.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch from Bernhard Übelacker to fix i386 test failure.
+(Closes: #1016156)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 17:43:56 +0300
+
 xtl (0.7.2-2) unstable; urgency=medium
 
   * Upload to unstable.
diff -Nru xtl-0.7.2/debian/patches/i386.patch xtl-0.7.2/debian/patches/i386.patch
--- xtl-0.7.2/debian/patches/i386.patch	1970-01-01 02:00:00.0 +0200
+++ xtl-0.7.2/debian/patches/i386.patch	2022-10-15 17:43:55.0 +0300
@@ -0,0 +1,11 @@
+--- xtl-0.7.2.orig/test/test_xmasked_value.cpp
 xtl-0.7.2/test/test_xmasked_value.cpp
+@@ -518,7 +518,7 @@ namespace xtl
+ EXPECT_EQ(c.value(), 3.35);
+ EXPECT_EQ(a, 3.35);
+ c += 1.;
+-EXPECT_EQ(c.value(), 4.35);
++EXPECT_DOUBLE_EQ(c.value().value_or(0.), 4.35);
+ EXPECT_EQ(a, 4.35);
+ c -= 1.;
+ c *= 2.;
diff -Nru xtl-0.7.2/debian/patches/series xtl-0.7.2/debian/patches/series
--- xtl-0.7.2/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ xtl-0.7.2/debian/patches/series	2022-10-15 17:43:46.0 +0300
@@ -0,0 +1 @@
+i386.patch

Bug#1021829: synaptic: APT::Default-Release still confusing with synaptic

[Kay Martinen]

Package: synaptic
Version: 0.84.6
Severity: important

Dear Maintainer,

i always use stable and often Synaptic as Packetmanager. And on this actual
machine i installed and upgraded Debian but at some point synaptic won't start
anymore.

It said APT::Default-Release "Stable-Updates" is invalid. But what it DID NOT
say is from where this setting is coming.
I tried to find it in /etc/apt but nothing found. And just after some web
searching i found only ONE Post that explained a synaptic.conf in root's
directory.

This is weird because i have to key in my user password if i start synaptic as
user (sudoed) and expected such a file in my home or in /etc/apt - but not in
root's own dir.

So, from a user's perspective Synaptic shut's down after the error message
window and is no longer usable. For nothing. Making it an important bug i
guess.

I deleted the /root/.synaptic Folder and Synaptic is working again. I don't
know how or from what this "stable-updates" entry is coming. I believe i did
not set it but it must be done by anything. I only have the Trouble to make
this work again. Because synaptic did not tell me in which file it founds a
problematic entry. This is my suggestion that synaptic should tell the path and
filename of the error.

BTW. I tried to set a correct value in a new /etc/apt/apt.conf but then
synaptic tells my bogus content at the end of file and... the filename. Why not
everytime?



-- System Information:
Debian Release: 10.13
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-22-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.17-2
ii  libapt-inst2.0   1.8.2.3
ii  libapt-pkg5.01.8.2.3
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10+deb10u1
ii  libcairo-gobject21.16.0-4+deb10u1
ii  libcairo21.16.0-4+deb10u1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u4
ii  libgnutls30  3.6.7-4+deb10u9
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpcre2-8-0 10.32-5
ii  libstdc++6   8.3.0-6
ii  libvte-2.91-00.54.2-2
ii  libx11-6 2:1.6.7-1+deb10u2
ii  libxapian30  1.4.11-1
ii  policykit-1  0.105-25+deb10u1
ii  zenity   3.30.0-2
ii  zlib1g   1:1.2.11.dfsg-1+deb10u2

Versions of packages synaptic recommends:
ii  libgtk2-perl  2:1.24992-1+b2
ii  xdg-utils 1.1.3-1+deb10u1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
pn  software-properties-gtk  
ii  tasksel  3.53

-- no debconf information

Bug#1021773: libconfig-model-dpkg-perl: tweak example in docs for fix.(scanned.)copyright does not work

[Dominique Dumont]

On Friday, 14 October 2022 15:07:56 CEST you wrote:
> Note: loading debian/fix.scanned.copyright fixes from copyright fix files
> Configuration item 'Dpkg::Copyright' has a user error:
> Error while applying fix.scanned.copyright file:
> Configuration item 'Files:"'*'" Copyright' has a wrong value:
> Undefined mandatory value.

I've reproduced this message with a copyright that contains:

Copyright: "2009-2011, Dominique Dumont "

Note the quite at the beginning of the copyright statement. With this quote at 
the beginning of the statement, the substitution command s/\s*".*// matches 
the whole statement, so it removes its content, which triggers the "Undefined 
mandatory value".

HTH

Bug#1002336: freezegun FTBFS apparently fixed in version 1.1.0-1

[Étienne Mollier]

Control: fixed -1 1.1.0-1

Greetings,

As far as I could witness, the build issue in freezegun has been
addressed following the update to 1.1.0-1, which also includes a
quilt patch from upstream's merge tracker [1] and fixing the
test issue.

I believe the present entry can be closed by version 1.1.0-1.

[1]: https://github.com/spulec/freezegun/pull/397

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#1012888: acm: ftbfs with GCC-12

[Reiner Herrmann]

user debian-rele...@lists.debian.org
usertags 1012888 + bsp-2022-10-de-karlsruhe
control tags 1012888 + patch
thank you

Hi,

there are actually two problems that are fixed by the attached patch.
1. the src/V/Makefile did not include Makefile-include.txt like the
   other Makefiles, so it did not use the dpkg-buildflags.
   This caused a fallback to the upstream CFLAGS that include -Werror
   (and misses other flags set by dpkg-buildflags).
   Because VColor.o can get generated from two different directories,
   it's not deterministic (because of parallelism), with which flags
   the object is compiled.
2. src/V/VColor.c uses a potentially too small buffer for sprintf,
   which causes the warning (and because of 1 an error).

Kind regards,
  Reiner
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 15:40:22.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 15:40:22.0 +0200
@@ -85,3 +67,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 15:40:22.0 +0200
@@ -3,3 +3,4 @@
 set_default_object_dir.patch
 fix_paths_in_acm_tcl.patch
 hardening1.patch
+fix_buffer_size.patch

Bug#1021828: debian-policy.info: mysterious anchors in cross-references

[Jakub Wilk]

Package: debian-policy
Version: 4.6.1.1

I've stumbled upon this:

   $ info debian-policy | grep -Eoi '[*]note.*:[^.]+'
   ...
   *note Debian source control files – .dsc: 61
   *note Syntax of control files: 8f
   *note List of fields: a9

This looks very weird. What's "61", "8f", "a9"?

OK, I dug into texinfo documentation¹ and learned that these are 
anchor names.  If they are really necessary, I'd expect them to be at 
least somewhat human readable.



¹ info texinfo 'Info Format Cross Reference'
or 
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Info-Format-Cross-Reference.html


-- System Information:
Architecture: i386

Versions of packages debian-policy recommends:
ii  libjs-sphinxdoc  4.5.0-4

--
Jakub Wilk

Bug#1019192: Upstream report

[Josh Triplett]

Someone diagnosed and reported this upstream at
https://lore.kernel.org/lkml/c8c65713-5cda-43ad-8018-20f2e32e4...@t-8ch.de/T/#u

- Josh

Bug#1019618: ruby-delayed-job: diff for NMU version 4.1.9-1.1

[Adrian Bunk]

Control: tags 1019618 + patch
Control: tags 1019618 + pending

Dear maintainer,

I've prepared an NMU for ruby-delayed-job (versioned as 4.1.9-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ruby-delayed-job-4.1.9/debian/changelog ruby-delayed-job-4.1.9/debian/changelog
--- ruby-delayed-job-4.1.9/debian/changelog	2021-11-22 00:53:24.0 +0200
+++ ruby-delayed-job-4.1.9/debian/changelog	2022-10-15 17:07:57.0 +0300
@@ -1,3 +1,10 @@
+ruby-delayed-job (4.1.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport upstream fix for Ruby 3.1. (Closes: #1019618)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 17:07:57 +0300
+
 ruby-delayed-job (4.1.9-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-delayed-job-4.1.9/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch ruby-delayed-job-4.1.9/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch
--- ruby-delayed-job-4.1.9/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch	1970-01-01 02:00:00.0 +0200
+++ ruby-delayed-job-4.1.9/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch	2022-10-15 17:07:25.0 +0300
@@ -0,0 +1,43 @@
+From 80864629c1cd452a8eafa85e2ad69d6285f37c33 Mon Sep 17 00:00:00 2001
+From: willnet 
+Date: Mon, 25 Oct 2021 17:22:54 +0900
+Subject: Fix a broken spec due to Psych >= 4
+
+Since psych4.0, the load method has been safe_load, which causes the following error: YAML#load_dj retains the existing safeYAML support, but uses the version of psych that implements unsafe_load. In YAML#load_dj
+
+```
+  1) YAML autoloads the class of an anonymous struct
+ Failure/Error:
+   expect do
+ yaml = "--- !ruby/struct\nn: 1\n"
+ object = YAML.load(yaml)
+ expect(object).to be_kind_of(Struct)
+ expect(object.n).to eq(1)
+   end.not_to raise_error
+
+   expected no Exception, got # with backtrace:
+ # (eval):2:in `struct'
+ # ./spec/yaml_ext_spec.rb:28:in `block (3 levels) in '
+ # ./spec/yaml_ext_spec.rb:26:in `block (2 levels) in '
+ # ./spec/yaml_ext_spec.rb:26:in `block (2 levels) in '
+```
+---
+ spec/yaml_ext_spec.rb | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/spec/yaml_ext_spec.rb b/spec/yaml_ext_spec.rb
+index aebb9af..83bceea 100644
+--- a/spec/yaml_ext_spec.rb
 b/spec/yaml_ext_spec.rb
+@@ -25,7 +25,7 @@ describe 'YAML' do
+   it 'autoloads the class of an anonymous struct' do
+ expect do
+   yaml = "--- !ruby/struct\nn: 1\n"
+-  object = YAML.load(yaml)
++  object = load_with_delayed_visitor(yaml)
+   expect(object).to be_kind_of(Struct)
+   expect(object.n).to eq(1)
+ end.not_to raise_error
+-- 
+2.30.2
+
diff -Nru ruby-delayed-job-4.1.9/debian/patches/series ruby-delayed-job-4.1.9/debian/patches/series
--- ruby-delayed-job-4.1.9/debian/patches/series	2021-11-22 00:53:24.0 +0200
+++ ruby-delayed-job-4.1.9/debian/patches/series	2022-10-15 17:07:56.0 +0300
@@ -1 +1,2 @@
 simplecov
+0001-Fix-a-broken-spec-due-to-Psych-4.patch

Bug#1019617: ruby-delayed-job-active-record: diff for NMU version 4.1.6-3.1

[Adrian Bunk]

Control: tags 1019617 + patch
Control: tags 1019617 + pending

Dear maintainer,

I've prepared an NMU for ruby-delayed-job-active-record (versioned as 
4.1.6-3.1)and uploaded it to DELAYED/15. Please feel free to tell me
if I should cancel it.

cu
Adrian
diff -Nru ruby-delayed-job-active-record-4.1.6/debian/changelog ruby-delayed-job-active-record-4.1.6/debian/changelog
--- ruby-delayed-job-active-record-4.1.6/debian/changelog	2021-11-29 02:09:59.0 +0200
+++ ruby-delayed-job-active-record-4.1.6/debian/changelog	2022-10-15 17:00:10.0 +0300
@@ -1,3 +1,10 @@
+ruby-delayed-job-active-record (4.1.6-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for Ruby 3.1. (Closes: #1019617)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 17:00:10 +0300
+
 ruby-delayed-job-active-record (4.1.6-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-delayed-job-active-record-4.1.6/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch ruby-delayed-job-active-record-4.1.6/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch
--- ruby-delayed-job-active-record-4.1.6/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch	1970-01-01 02:00:00.0 +0200
+++ ruby-delayed-job-active-record-4.1.6/debian/patches/0001-Fix-a-broken-spec-due-to-Psych-4.patch	2022-10-15 16:59:38.0 +0300
@@ -0,0 +1,48 @@
+From 72da7676697cf995a42fd8140a834bfd6eef6a69 Mon Sep 17 00:00:00 2001
+From: willnet 
+Date: Mon, 1 Nov 2021 17:32:01 +0900
+Subject: Fix a broken spec due to Psych >= 4
+
+Since psych4.0, the load method has been safe_load, which causes the following error.
+
+So I use YAML#load_dj to avoid them. ref: ref: https://github.com/collectiveidea/delayed_job/pull/1152/commits/b4ddd3dfe1450f1e51f9a6ac90db3134b5d7af78
+
+```
+  1) ActiveRecord loads classes with non-default primary key
+ Failure/Error:
+   expect do
+ YAML.load(Story.create.to_yaml)
+   end.not_to raise_error
+
+   expected no Exception, got # with backtrace:
+ # ./spec/delayed/serialization/active_record_spec.rb:8:in `block (3 levels) in '
+ # ./spec/delayed/serialization/active_record_spec.rb:7:in `block (2 levels) in '
+ # ./spec/delayed/serialization/active_record_spec.rb:7:in `block (2 levels) in '
+```
+---
+ spec/delayed/serialization/active_record_spec.rb | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/spec/delayed/serialization/active_record_spec.rb b/spec/delayed/serialization/active_record_spec.rb
+index 4aa27f1..f0b0cd3 100644
+--- a/spec/delayed/serialization/active_record_spec.rb
 b/spec/delayed/serialization/active_record_spec.rb
+@@ -5,13 +5,13 @@ require "helper"
+ describe ActiveRecord do
+   it "loads classes with non-default primary key" do
+ expect do
+-  YAML.load(Story.create.to_yaml)
++  YAML.load_dj(Story.create.to_yaml)
+ end.not_to raise_error
+   end
+ 
+   it "loads classes even if not in default scope" do
+ expect do
+-  YAML.load(Story.create(scoped: false).to_yaml)
++  YAML.load_dj(Story.create(scoped: false).to_yaml)
+ end.not_to raise_error
+   end
+ end
+-- 
+2.30.2
+
diff -Nru ruby-delayed-job-active-record-4.1.6/debian/patches/series ruby-delayed-job-active-record-4.1.6/debian/patches/series
--- ruby-delayed-job-active-record-4.1.6/debian/patches/series	2021-11-29 02:09:59.0 +0200
+++ ruby-delayed-job-active-record-4.1.6/debian/patches/series	2022-10-15 17:00:10.0 +0300
@@ -1,2 +1,3 @@
 no-simplecov-lcov.patch
 fix-path-to-migration-template.patch
+0001-Fix-a-broken-spec-due-to-Psych-4.patch

Bug#1019616: ruby-dalli: diff for NMU version 3.0.6-1.1

[Adrian Bunk]

Control: tags 1019616 + patch
Control: tags 1019616 + pending

Dear maintainer,

I've prepared an NMU for ruby-dalli (versioned as 3.0.6-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ruby-dalli-3.0.6/debian/changelog ruby-dalli-3.0.6/debian/changelog
--- ruby-dalli-3.0.6/debian/changelog	2021-12-07 04:49:10.0 +0200
+++ ruby-dalli-3.0.6/debian/changelog	2022-10-15 16:54:27.0 +0300
@@ -1,3 +1,10 @@
+ruby-dalli (3.0.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport upstream fix for FTBFS with Ruby 3.1. (Closes: #1019616)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 16:54:27 +0300
+
 ruby-dalli (3.0.6-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-dalli-3.0.6/debian/patches/0001-Adding-Ruby-3.1-to-CI-workflow-886.patch ruby-dalli-3.0.6/debian/patches/0001-Adding-Ruby-3.1-to-CI-workflow-886.patch
--- ruby-dalli-3.0.6/debian/patches/0001-Adding-Ruby-3.1-to-CI-workflow-886.patch	1970-01-01 02:00:00.0 +0200
+++ ruby-dalli-3.0.6/debian/patches/0001-Adding-Ruby-3.1-to-CI-workflow-886.patch	2022-10-15 16:49:18.0 +0300
@@ -0,0 +1,46 @@
+From d65244d02babd7aa23a4ea8dd3b3a955393bcbac Mon Sep 17 00:00:00 2001
+From: Peter Goldstein 
+Date: Sat, 25 Dec 2021 15:34:35 -0800
+Subject: Adding Ruby 3.1 to CI workflow (#886)
+
+* Adding Ruby 3.1 to CI workflow
+
+* Fix rubocop-performance lint issue, make tests compatible with error_highlight
+---
+ test/protocol/test_value_serializer.rb | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/test/protocol/test_value_serializer.rb b/test/protocol/test_value_serializer.rb
+index 436fc9c..0127c18 100644
+--- a/test/protocol/test_value_serializer.rb
 b/test/protocol/test_value_serializer.rb
+@@ -228,7 +228,7 @@ describe Dalli::Protocol::ValueSerializer do
+ vs.retrieve(raw_value, Dalli::Protocol::ValueSerializer::FLAG_SERIALIZED)
+   end
+ end
+-assert_equal exception.message, error_message
++assert_equal error_message, exception.message
+   end
+ end
+ 
+@@ -244,7 +244,7 @@ describe Dalli::Protocol::ValueSerializer do
+ vs.retrieve(raw_value, Dalli::Protocol::ValueSerializer::FLAG_SERIALIZED)
+   end
+ end
+-assert_equal exception.message, "Unable to unmarshal value: #{error_message}"
++assert exception.message.start_with?("Unable to unmarshal value: #{error_message}")
+   end
+ end
+ 
+@@ -259,7 +259,7 @@ describe Dalli::Protocol::ValueSerializer do
+ vs.retrieve(raw_value, Dalli::Protocol::ValueSerializer::FLAG_SERIALIZED)
+   end
+ end
+-assert_equal exception.message, error_message
++assert exception.message.start_with?(error_message)
+   end
+ end
+ 
+-- 
+2.30.2
+
diff -Nru ruby-dalli-3.0.6/debian/patches/series ruby-dalli-3.0.6/debian/patches/series
--- ruby-dalli-3.0.6/debian/patches/series	2021-12-07 04:49:10.0 +0200
+++ ruby-dalli-3.0.6/debian/patches/series	2022-10-15 16:54:26.0 +0300
@@ -2,3 +2,4 @@
 0003-dalli-version.patch
 0004-No-bundler-in-test-helper.patch
 0006-Fix-Dalli-NameError.patch
+0001-Adding-Ruby-3.1-to-CI-workflow-886.patch

Bug#1020064: tcsh: diff for NMU version 6.21.00-1.2

[Thomas Lange]

I've orphanded this package a few month ago. Feel free to do whatever
you want.

-- 
viele Grüße Thomas

Bug#1021827: info -o: exit status 0 on error

[Jakub Wilk]

Package: info
Version: 6.8-6

"info -o" exits with status 0 when it can't find the node:

$ info -o /dev/null lolcow
info: No menu item 'lolcow' in node '(dir)Top'

$ echo $?
0

In contrast, if I omit the -o option, it exits with status 1, as it 
should:


$ info lolcow
info: No menu item 'lolcow' in node '(dir)Top'

$ echo $?
1


-- System Information:
Architecture: i386

Versions of packages info depends on:
ii  libc6 2.35-3
ii  libtinfo6 6.3+20220423-2
ii  install-info  6.8-6

--
Jakub Wilk

Bug#1019615: ruby-crack: diff for NMU version 0.4.4-2.1

[Adrian Bunk]

Control: tags 1019615 + patch
Control: tags 1019615 + pending

Dear maintainer,

I've prepared an NMU for ruby-crack (versioned as 0.4.4-2.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ruby-crack-0.4.4/debian/changelog ruby-crack-0.4.4/debian/changelog
--- ruby-crack-0.4.4/debian/changelog	2021-06-30 09:23:46.0 +0300
+++ ruby-crack-0.4.4/debian/changelog	2022-10-15 16:40:46.0 +0300
@@ -1,3 +1,10 @@
+ruby-crack (0.4.4-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add upstream submitted fix for Ruby 3.1. (Closes: #1019615)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 16:40:46 +0300
+
 ruby-crack (0.4.4-2) unstable; urgency=medium
 
   * Update standards version to 4.5.1, no changes needed.
diff -Nru ruby-crack-0.4.4/debian/patches/0001-Use-named-parameters-for-safe_load.patch ruby-crack-0.4.4/debian/patches/0001-Use-named-parameters-for-safe_load.patch
--- ruby-crack-0.4.4/debian/patches/0001-Use-named-parameters-for-safe_load.patch	1970-01-01 02:00:00.0 +0200
+++ ruby-crack-0.4.4/debian/patches/0001-Use-named-parameters-for-safe_load.patch	2022-10-15 16:40:38.0 +0300
@@ -0,0 +1,33 @@
+From 7fa8d8aea4a041969e433debef7f4d5d59881ae2 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?V=C3=ADt=20Ondruch?= 
+Date: Fri, 11 Mar 2022 18:29:43 +0100
+Subject: Use named parameters for `safe_load`.
+
+This is available since Psych 3.1 [[1], [2]], but mandatory since Psych
+4.0 [[3]].
+
+Fixes #72
+
+[1]: https://github.com/ruby/psych/pull/358
+[2]: https://github.com/ruby/psych/pull/378
+[3]: https://github.com/ruby/psych/commit/0767227051dbddf1f949eef512c174deabf22891
+---
+ lib/crack/json.rb | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/lib/crack/json.rb b/lib/crack/json.rb
+index 1a27ac7..528aad6 100644
+--- a/lib/crack/json.rb
 b/lib/crack/json.rb
+@@ -13,7 +13,7 @@ module Crack
+ 
+ def self.parse(json)
+   yaml = unescape(convert_json_to_yaml(json))
+-  YAML.safe_load(yaml, [Regexp, Date, Time])
++  YAML.safe_load(yaml, permitted_classes: [Regexp, Date, Time])
+ rescue *parser_exceptions
+   raise ParseError, "Invalid JSON string"
+ rescue Psych::DisallowedClass
+-- 
+2.30.2
+
diff -Nru ruby-crack-0.4.4/debian/patches/series ruby-crack-0.4.4/debian/patches/series
--- ruby-crack-0.4.4/debian/patches/series	2021-06-30 09:23:46.0 +0300
+++ ruby-crack-0.4.4/debian/patches/series	2022-10-15 16:40:46.0 +0300
@@ -1 +1,2 @@
 don't_relly_on_git.patch
+0001-Use-named-parameters-for-safe_load.patch

Bug#1021826: rust-bytes: please update to 1.2.0

[Jonas Smedegaard]

Source: rust-bytes
Version: 1.1.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to upstream release 1.2.0, needed by packages I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNKuMoACgkQLHwxRsGg
ASH1+w/+L5+cmurMioLijgKv7evO/lwcB/+2KCieqCr/GVvxC2Ez14Lt0zbhSypb
exQozpyRnb6WRU/IZbJA8ePu6hX36wCYhO4n8f5etKC+VyORRTJfs1C5K9xmy9LA
X37D/n1G4GQlH++sUrGByw7ygFKKVpEpw1jbETmAj9DdXduX9sVdgzfXq4otl3UO
1PKVKOpCraWYxsvXRnN4CkfjRrsIjSP36wXMBGoowjvBouL9UfYUWv3IrVX+hvFK
1TQJrEG39+tpuYNU13XYklWBR2rRCCNRvpawXjD11tzIB/U7zrvGdXOCfAZJ+KZg
fMvZaGm+57+hts7H0AIUVcJBoQ1UAa5dW1eAIdSk743YRE2jP44lWZe/vDTsryVy
DkLZ8OFKYOfj/yGetf3ix6Fq1U2iiRtQEXcL1VXWfkAD7VcUxmDdQ9CTWu7nkoeF
TJMZQa/ptqZKBGrBYm4wbDNwHeLKWATynuzqeenVvxD9SZnSZR0T1NVxlLGHeqS2
t8x94bWldooHhD7aW++2G3O+wsi2T3sjTO1RR3vegRbhsdDtr5+FIEzvlARcteKa
tWXeeQSP8xGhYcZomLPkQBKQ6Xr1MWr/sZE+NQpk5pGRlMR3h9ahpv9hC5azEe87
GL4Qxq1O6ZEti2syorZ7nHqr74hMg/75jJ3cs6Yklbi0C0IYNSY=
=TDXp
-END PGP SIGNATURE-