Bug#984343: marked as done (snek: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Mon, 11 Oct 2021 02:38:09 +
with message-id 
and subject line Bug#984343: fixed in snek 1.7-2
has caused the Debian Bug report #984343,
regarding snek: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:snek
Version: 1.5-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/snek_1.5-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
version: 11
architecture: amd64
essential: true
   -
package: avr-libc
version: 1:2.0.0+Atmel3.6.2-1.1
architecture: all
   -
package: autotools-dev
version: 20180224.1+nmu1
architecture: all
   -
package: autopoint
version: 0.21-4
architecture: all
   -
package: automake
version: 1:1.16.3-2
architecture: all
   -
package: autoconf
version: 2.69-14
architecture: all
   -
package: asciidoctor
version: 2.0.12-2
architecture: all
   -
package: adduser
version: 3.118
architecture: all
 
background-packages: 61989
foreground-packages: 1
total-packages: 61990
broken-packages: 0

+--+
| Cleanup  |
+--+

Purging /<>
Not cleaning session: cloned chroot in use
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build Type: binary
Build-Space: n/a
Build-Time: 0
Distribution: unstable
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: snek_1.5-1
Machine Architecture: amd64
Package: snek
Package-Time: 0
Source-Version: 1.5-1
Space: n/a
Status: given-back
Version: 1.5-1

Finished at 2021-03-01T20:58:04Z
Build needed 00:00:00, no disk space
E: Package build dependencies not satisfied; skipping
DC-Status: Failed 65.177143803s
--- End Message ---
--- Begin Message ---
Source: snek
Source-Version: 1.7-2
Done: Keith Packard 

We believe that the bug you reported is fixed in the latest version of
snek, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 984...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Keith Packard  (supplier of updated snek package)

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

Bug#994969: marked as done (jackd2: segfaults after today's upgrade of other Debian testing packages)

[Debian Bug Tracking System]

Your message dated Mon, 11 Oct 2021 01:18:24 +
with message-id 
and subject line Bug#994969: fixed in glibmm2.4 2.66.2-1
has caused the Debian Bug report #994969,
regarding jackd2: segfaults after today's upgrade of other Debian testing 
packages
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
994969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jackd2
Version: 1.9.19~dfsg-2
Severity: grave
Justification: renders package unusable

Hello!
After today's upgrade, jackd stopped working on my Debian testing box.

  $ jackd --realtime -d alsa --device hw:PCH --softmode --hwmeter --rate 44100 &
  jackdmp 1.9.19
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2021 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  no message buffer overruns
  no message buffer overruns
  
  [1]+  Segmentation fault  jackd --realtime -d alsa --device hw:PCH 
--softmode --hwmeter --rate 44100


I tried to selectively downgrade the libraries that appeared related to
jackd2, but to no avail: the segfault was still reproducible.

The list of package upgrades that broke jackd is:

  
  [REMOVE, NOT USED] libbox2d2.3.0:amd64 2.3.1+ds-7
  [REMOVE, NOT USED] libcmis-0.5-5v5:amd64 0.5.2-3
  [REMOVE, NOT USED] libqrcodegencpp1:amd64 1.6.0-1
  [INSTALL, DEPENDENCIES] libbox2d2:amd64 2.4.1-2
  [INSTALL, DEPENDENCIES] libzxingcore1:amd64 1.2.0-1
  [UPGRADE] adwaita-icon-theme:amd64 40.1.1-2 -> 41.0-1
  [UPGRADE] binutils:amd64 2.37-5 -> 2.37-7
  [UPGRADE] binutils-common:amd64 2.37-5 -> 2.37-7
  [UPGRADE] binutils-x86-64-linux-gnu:amd64 2.37-5 -> 2.37-7
  [UPGRADE] cpp-10:amd64 10.3.0-9 -> 10.3.0-11
  [UPGRADE] diffoscope:amd64 182 -> 185
  [UPGRADE] diffoscope-minimal:amd64 182 -> 185
  [UPGRADE] eatmydata:amd64 129-3 -> 129-4
  [UPGRADE] fonts-opensymbol:amd64 2:102.12+LibO7.1.5-2 -> 2:102.12+LibO7.2.1-3
  [UPGRADE] g++-10:amd64 10.3.0-9 -> 10.3.0-11
  [UPGRADE] gcc-10:amd64 10.3.0-9 -> 10.3.0-11
  [UPGRADE] gcc-10-base:amd64 10.3.0-9 -> 10.3.0-11
  [UPGRADE] gcc-11-base:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libasan6:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libatk-wrapper-java:amd64 0.38.0-4 -> 0.38.0-5
  [UPGRADE] libatk-wrapper-java-jni:amd64 0.38.0-4 -> 0.38.0-5
  [UPGRADE] libatomic1:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libbinutils:amd64 2.37-5 -> 2.37-7
  [UPGRADE] libcc1-0:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libctf-nobfd0:amd64 2.37-5 -> 2.37-7
  [UPGRADE] libctf0:amd64 2.37-5 -> 2.37-7
  [UPGRADE] libeatmydata1:amd64 129-3 -> 129-4
  [UPGRADE] libgcc-10-dev:amd64 10.3.0-9 -> 10.3.0-11
  [UPGRADE] libgcc-s1:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libgfortran5:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libglibmm-2.4-1v5:amd64 2.64.2-2 -> 2.66.1-1
  [UPGRADE] libgomp1:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libitm1:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] liblibreoffice-java:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] liblsan0:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libmanette-0.2-0:amd64 0.2.5-1 -> 0.2.6-3
  [UPGRADE] libobjc4:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libquadmath0:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libreoffice:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-base:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-base-core:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-base-drivers:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-calc:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-common:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-core:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-draw:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-impress:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-java-common:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-l10n-de:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-l10n-it:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-math:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-report-builder-bin:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-sdbc-hsqldb:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-style-colibre:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libreoffice-writer:amd64 1:7.1.5-2 -> 1:7.2.1-3
  [UPGRADE] libscalar-list-utils-perl:amd64 1:1.55-1+b1 -> 1:1.59-1
  [UPGRADE] libstdc++-10-dev:amd64 10.3.0-9 -> 10.3.0-11
  [UPGRADE] libstdc++6:amd64 11.2.0-4 -> 11.2.0-7
  [UPGRADE] libtsan0:amd64 11.2.0-4 

Bug#994969: marked as pending in glibmm2.4

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #994969 in glibmm2.4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/glibmm/-/commit/d8388c45dffe7c768641c48eea1da286870d42eb


New upstream release

Closes: #994969


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/994969

Processed: Bug#994969 marked as pending in glibmm2.4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #994969 [libglibmm-2.4-1v5] jackd2: segfaults after today's upgrade of 
other Debian testing packages
Added tag(s) pending.

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

Bug#984054: marked as done (evolvotron: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Mon, 11 Oct 2021 01:03:52 +
with message-id 
and subject line Bug#984054: fixed in evolvotron 0.7.1-5
has caused the Debian Bug report #984054,
regarding evolvotron: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:evolvotron
Version: 0.7.1-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/evolvotron_0.7.1-4_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
 from mutatable_image_display.cpp:24:
../libfunction/xyz.h:83:3: note: because ‘XYZ’ has user-provided 
‘XYZ::XYZ(const XYZ&)’
   83 |   XYZ(const XYZ& v)
  |   ^~~
In file included from transform_factory.h:31,
 from evolvotron_main.h:30,
 from mutatable_image_display.cpp:27:
../libfunction/transform.h: In member function ‘void Transform::basis_z(const 
XYZ&)’:
../libfunction/transform.h:85:17: warning: implicitly-declared ‘constexpr XYZ& 
XYZ::operator=(const XYZ&)’ is deprecated [-Wdeprecated-copy]
   85 |_basis_z=z;
  | ^
In file included from mutatable_image.h:29,
 from mutatable_image_display.h:29,
 from mutatable_image_display.cpp:24:
../libfunction/xyz.h:83:3: note: because ‘XYZ’ has user-provided 
‘XYZ::XYZ(const XYZ&)’
   83 |   XYZ(const XYZ& v)
  |   ^~~
mutatable_image_display.cpp: In member function ‘virtual void 
MutatableImageDisplay::mousePressEvent(QMouseEvent*)’:
mutatable_image_display.cpp:505:33: warning: ‘Qt::MidButton’ is deprecated: 
MidButton is deprecated. Use MiddleButton instead [-Wdeprecated-declarations]
  505 |   else if (event->button()==Qt::MidButton)
  | ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:48,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:46,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractanimation.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:6,
 from /usr/include/x86_64-linux-gnu/qt5/QtXml/QtXmlDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtXml/QtXml:3,
 from common.h:34,
 from mutatable_image_display.h:27,
 from mutatable_image_display.cpp:24:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:132:9: note: declared here
  132 | MidButton Q_DECL_ENUMERATOR_DEPRECATED_X("MidButton is 
deprecated. Use MiddleButton instead") = MiddleButton,
  | ^
mutatable_image_display.cpp: In member function ‘virtual void 
MutatableImageDisplay::mouseMoveEvent(QMouseEvent*)’:
mutatable_image_display.cpp:525:28: warning: ‘Qt::MidButton’ is deprecated: 
MidButton is deprecated. Use MiddleButton instead [-Wdeprecated-declarations]
  525 |   if (event->buttons()::MidButton)
  |^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:48,
 from 

Processed: tagging 984054

[Debian Bug Tracking System]

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

> tags 984054 + pending
Bug #984054 [src:evolvotron] evolvotron: ftbfs with GCC-11
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#995392: ghostscript: ps2pdf trashes some characters

[Debian Bug Tracking System]

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

> severity 995392 normal
Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters
Severity set to 'normal' from 'grave'
> tags 995392 + moreinfo
Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#995392: ghostscript: ps2pdf trashes some characters

[Norbert Preining]

severity 995392 normal
tags 995392 + moreinfo
thanks

Hi all,

first of all, it seems this message didn't make it either to the list or
my computer, just found it by randomly checking transitioning.

Then, this is by far not a grave bug in TL. pdflatex is **not**
affected, since it generated pdf files without using ghostscript.

What might have some problems - and I haven't reproduced this till now
nor tested - is dvi -> ps -> pdf route.

>   * chartest3.tex:  Test: « don't ».
>   * chartest4[ab].tex:  Test: « don't finite float ».
>   * chartest5[ab].tex:  Test: « don't finite float offer affine ».
> where the 4b and 5b versions contain \pdfglyphtounicode commands for
> the ligatures (from glyphtounicode.tex), though the tests below show
> that they do not have any influence here.

Vincent, thanks for the tests, but without explanation or make files or
some hints on **what** you did run, this is not reproducible and
testable.

What I want to see is
* input file
* commands run
* log files of each program run
* what is the problematic output

Thanks

> \documentclass[12pt]{article}
> \usepackage[utf8]{inputenc}
> \usepackage[T1]{fontenc}
> \usepackage{lmodern}
> \begin{document}
> \thispagestyle{empty}
> Test: « don't ».
> \end{document}

This document and copy and paste of its content does work fine for me
with
* current sid
* latex/dvips/ps2pdf
* pdflatex

Generated pdf file can be copy/pasted.

I really don't see what is going on, thanks for any explanations.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#984364: marked as done (template-glib: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Mon, 11 Oct 2021 00:09:56 +0100
with message-id 
and subject line Re: Bug#984364: template-glib: ftbfs with GCC-11
has caused the Debian Bug report #984364,
regarding template-glib: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:template-glib
Version: 3.34.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/template-glib_3.34.0-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
[3/32] /usr/bin/flex -o src/tmpl-expr-scanner.c src/tmpl-expr-meson-scanner.l
[4/32] /usr/bin/meson --internal exe --capture src/tmpl-enums.h -- 
/usr/bin/glib-mkenums --template 
/<>/obj-x86_64-linux-gnu/../src/tmpl-enums.h.in 
/<>/obj-x86_64-linux-gnu/../src/tmpl-error.h 
/<>/obj-x86_64-linux-gnu/../src/tmpl-expr-types.h
[5/32] /usr/bin/meson --internal exe --capture src/tmpl-enums.c -- 
/usr/bin/glib-mkenums --template 
/<>/obj-x86_64-linux-gnu/../src/tmpl-enums.c.in 
/<>/obj-x86_64-linux-gnu/../src/tmpl-error.h 
/<>/obj-x86_64-linux-gnu/../src/tmpl-expr-types.h
[6/32] cc -Isrc/libtemplate_glib-1.0.so.0.3400.0.p -Isrc -I../src 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/gobject-introspection-1.0 
-I/<>/obj-x86_64-linux-gnu -I/<>/src 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu11 -DHAVE_CONFIG_H -DTMPL_GLIB_COMPILATION -Wcast-align 
-Wdeclaration-after-statement -Wformat-nonliteral -Wformat-security 
-Wmissing-include-dirs -Wnested-externs -Wno-missing-field-initializers 
-Wno-sign-compare -Wno-unused-parameter -Wpointer-arith -Wredundant-decls 
-Wswitch-default -Wswitch-enum -Wuninitialized -Werror=format-security 
-Werror=format=2 -Werror=empty-body -Werror=implicit-function-declaration 
-Werror=incompatible-pointer-types -Werror=pointer-arith -Werror=init-self 
-Werror=int-conversion -Werror=misleading-indentation 
-Werror=missing-include-dirs -Werror=overflow -Werror=return-type 
-Werror=shadow -Werr
 or=strict-prototypes -Werror=undef -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libtemplate_glib-1.0.so.0.3400.0.p/meson-generated_.._tmpl-enums.c.o -MF 
src/libtemplate_glib-1.0.so.0.3400.0.p/meson-generated_.._tmpl-enums.c.o.d -o 
src/libtemplate_glib-1.0.so.0.3400.0.p/meson-generated_.._tmpl-enums.c.o -c 
src/tmpl-enums.c
[7/32] cc -Isrc/libtemplate_glib-1.0.so.0.3400.0.p -Isrc -I../src 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/gobject-introspection-1.0 
-I/<>/obj-x86_64-linux-gnu -I/<>/src 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu11 -DHAVE_CONFIG_H -DTMPL_GLIB_COMPILATION -Wcast-align 
-Wdeclaration-after-statement -Wformat-nonliteral -Wformat-security 
-Wmissing-include-dirs -Wnested-externs -Wno-missing-field-initializers 
-Wno-sign-compare 

Bug#984252: marked as done (nautilus: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 23:53:09 +0100
with message-id 
and subject line Re: Bug#984252: nautilus: ftbfs with GCC-11
has caused the Debian Bug report #984252,
regarding nautilus: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nautilus
Version: 3.38.2-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/nautilus_3.38.2-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 | __atomic_load (gapg_temp_atomic, _temp_newval, 
__ATOMIC_SEQ_CST);   \
  | ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 | (!g_atomic_pointer_get (location) && \
  |   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:2000:7: note: in expansion of macro 
‘g_once_init_enter’
 2000 |   if (g_once_init_enter (_define_type_id__volatile))  \
  |   ^
/usr/include/glib-2.0/gobject/gtype.h:2032:3: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER’
 2032 |   _G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER(TypeName, type_name, 
TYPE_PARENT, flags) \
  |   ^~
/usr/include/glib-2.0/gobject/gtype.h:1759:61: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN’
 1759 | #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_)  
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()
  | 
^
/usr/include/glib-2.0/gobject/gtype.h:1600:61: note: in expansion of macro 
‘G_DEFINE_TYPE_EXTENDED’
 1600 | #define G_DEFINE_TYPE(TN, t_n, T_P) 
G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {})
  | 
^~
../eel/eel-canvas.c:2116:1: note: in expansion of macro ‘G_DEFINE_TYPE’
 2116 | G_DEFINE_TYPE (EelCanvasAccessible, eel_canvas_accessible, 
GTK_TYPE_CONTAINER_ACCESSIBLE)
  | ^
../eel/eel-canvas.c: In function ‘eel_canvas_item_accessible_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 | __atomic_load (gapg_temp_atomic, _temp_newval, 
__ATOMIC_SEQ_CST);   \
  | ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 | (!g_atomic_pointer_get (location) && \
  |   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:2000:7: note: in expansion of macro 
‘g_once_init_enter’
 2000 |   if (g_once_init_enter (_define_type_id__volatile))  \
  |   ^
/usr/include/glib-2.0/gobject/gtype.h:2032:3: note: in expansion of macro 

Bug#984358: marked as done (sysprof: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 23:54:15 +0100
with message-id 
and subject line Re: Bug#984358: sysprof: ftbfs with GCC-11
has caused the Debian Bug report #984358,
regarding sysprof: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sysprof
Version: 3.38.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/sysprof_3.38.1-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:22,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from src/ipc-profiler.h:12,
 from src/ipc-profiler.c:13:
src/ipc-profiler.c: In function ‘ipc_profiler_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 | __atomic_load (gapg_temp_atomic, _temp_newval, 
__ATOMIC_SEQ_CST);   \
  | ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 | (!g_atomic_pointer_get (location) && \
  |   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:2042:7: note: in expansion of macro 
‘g_once_init_enter’
 2042 |   if (g_once_init_enter (_define_type_id__volatile))  \
  |   ^
/usr/include/glib-2.0/gobject/gtype.h:1803:61: note: in expansion of macro 
‘_G_DEFINE_INTERFACE_EXTENDED_BEGIN’
 1803 | #define G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, _C_) 
_G_DEFINE_INTERFACE_EXTENDED_BEGIN(TN, t_n, T_P) {_C_;} 
_G_DEFINE_INTERFACE_EXTENDED_END()
  | 
^~
/usr/include/glib-2.0/gobject/gtype.h:1784:61: note: in expansion of macro 
‘G_DEFINE_INTERFACE_WITH_CODE’
 1784 | #define G_DEFINE_INTERFACE(TN, t_n, T_P)
G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, ;)
  | 
^~~~
src/ipc-profiler.c:314:1: note: in expansion of macro ‘G_DEFINE_INTERFACE’
  314 | G_DEFINE_INTERFACE (IpcProfiler, ipc_profiler, G_TYPE_OBJECT)
  | ^~
src/ipc-profiler.c: In function ‘ipc_profiler_proxy_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 | __atomic_load (gapg_temp_atomic, _temp_newval, 
__ATOMIC_SEQ_CST);   \
  | ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 | (!g_atomic_pointer_get (location) && \
  |   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:2000:7: note: in expansion of 

Bug#984162: marked as done (gtksourceview4: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 23:43:43 +0100
with message-id 
and subject line Re: Bug#984162: gtksourceview4: ftbfs with GCC-11
has caused the Debian Bug report #984162,
regarding gtksourceview4: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gtksourceview4
Version: 4.8.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gtksourceview4_4.8.0-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
cc1: some warnings being treated as errors
[16/140] cc -Igtksourceview/libgtksourceview-4core.a.p -Igtksourceview 
-I../gtksourceview -I. -I.. -I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libxml2 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wall -Winvalid-pch -Wextra -std=gnu99 -DG_DISABLE_DEPRECATED 
-DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED 
-DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_24 
-DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_24 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_48 -DGLIB_VERSIO
 N_MAX_ALLOWED=GLIB_VERSION_2_48 -Wcast-align -Wdeclaration-after-statement 
-Werror=address -Werror=array-bounds -Werror=empty-body -Werror=implicit 
-Werror=implicit-function-declaration -Werror=incompatible-pointer-types 
-Werror=init-self -Werror=int-conversion -Werror=int-to-pointer-cast 
-Werror=main -Werror=misleading-indentation -Werror=missing-braces 
-Werror=missing-include-dirs -Werror=nonnull -Werror=overflow 
-Werror=pointer-arith -Werror=pointer-to-int-cast -Werror=return-type 
-Werror=sequence-point -Werror=shadow -Werror=strict-prototypes 
-Werror=trigraphs -Werror=undef -Werror=write-strings -Wformat-nonliteral 
-Werror=format-security -Werror=format=2 -Wignored-qualifiers 
-Wimplicit-function-declaration -Wlogical-op -Wmissing-format-attribute 
-Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs 
-Wno-cast-function-type -Wno-missing-field-initializers -Wno-sign-compare 
-Wno-unused-parameter -Wold-style-definition -Wpointer-arith 
-Wstrict-prototypes -Wswitch-default -Wswi
 tch-enum -Wundef -Wuninitialized -Wunused -fno-strict-aliasing 
-Wmissing-declarations -DG_DISABLE_ASSERT -DG_DISABLE_CAST_CHECKS -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
-DHAVE_CONFIG_H -DGTK_SOURCE_COMPILATION '-DG_LOG_DOMAIN="GtkSourceView"' -MD 
-MQ gtksourceview/libgtksourceview-4core.a.p/gtksourcecompletion.c.o -MF 
gtksourceview/libgtksourceview-4core.a.p/gtksourcecompletion.c.o.d -o 

Bug#984074: marked as done (jsonrpc-glib: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 23:40:29 +0100
with message-id 
and subject line Re: Bug#984074: jsonrpc-glib: ftbfs with GCC-11
has caused the Debian Bug report #984074,
regarding jsonrpc-glib: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jsonrpc-glib
Version: 3.38.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/jsonrpc-glib_3.38.0-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
cc1: some warnings being treated as errors
[8/21] cc -Isrc/libjsonrpc-glib-1.0.so.1.3800.0.p -Isrc -I../src -I. -I.. 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/json-glib-1.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu11 -DHAVE_CONFIG_H -DJSONRPC_GLIB_COMPILATION -Wcast-align 
-Wdeclaration-after-statement -Werror=address -Werror=array-bounds 
-Werror=empty-body -Werror=implicit -Werror=implicit-function-declaration 
-Werror=incompatible-pointer-types -Werror=init-self -Werror=int-conversion 
-Werror=int-to-pointer-cast -Werror=main -Werror=misleading-indentation 
-Werror=missing-braces -Werror=missing-include-dirs -Werror=nonnull 
-Werror=overflow -Werror=pointer-arith -Werror=pointer-to-int-cast 
-Werror=redundant-decls -Werror=return-type -Werror=sequence-point 
-Werror=shadow -Werror=strict-prototypes -Werror=trigraphs -Werror=undef 
-Werror=write-strings -Wformat-nonliteral -Werror=format-security -Werror=
 format=2 -Wignored-qualifiers -Wimplicit-function-declaration -Wlogical-op 
-Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn 
-Wnested-externs -Wno-cast-function-type -Wno-missing-field-initializers 
-Wno-sign-compare -Wno-unused-parameter -Wold-style-definition -Wpointer-arith 
-Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef 
-Wuninitialized -Wunused -fno-strict-aliasing -DG_DISABLE_CAST_CHECKS -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
-fvisibility=hidden -DG_DISABLE_ASSERT -MD -MQ 
src/libjsonrpc-glib-1.0.so.1.3800.0.p/jsonrpc-input-stream.c.o -MF 
src/libjsonrpc-glib-1.0.so.1.3800.0.p/jsonrpc-input-stream.c.o.d -o 
src/libjsonrpc-glib-1.0.so.1.3800.0.p/jsonrpc-input-stream.c.o -c 
../src/jsonrpc-input-stream.c
FAILED: src/libjsonrpc-glib-1.0.so.1.3800.0.p/jsonrpc-input-stream.c.o 
cc -Isrc/libjsonrpc-glib-1.0.so.1.3800.0.p -Isrc -I../src -I. -I.. 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/json-glib-1.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu11 -DHAVE_CONFIG_H -DJSONRPC_GLIB_COMPILATION -Wcast-align 
-Wdeclaration-after-statement -Werror=address -Werror=array-bounds 
-Werror=empty-body -Werror=implicit -Werror=implicit-function-declaration 
-Werror=incompatible-pointer-types -Werror=init-self 

Bug#984095: marked as done (libdazzle: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 23:39:02 +0100
with message-id 
and subject line Re: Bug#984095: libdazzle: ftbfs with GCC-11
has caused the Debian Bug report #984095,
regarding libdazzle: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libdazzle
Version: 3.38.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libdazzle_3.38.0-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
   65 | G_DEFINE_TYPE (DzlBoxTheatric, dzl_box_theatric, G_TYPE_OBJECT)
  | ^
cc1: some warnings being treated as errors
[9/287] cc -Isrc/libdazzle-1.0.so.0.p -Isrc -I../src -I. -I.. 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu11 -DHAVE_CONFIG_H -DDAZZLE_COMPILATION -Wcast-align 
-Wdeclaration-after-statement -Werror=address -Werror=array-bounds 
-Werror=empty-body -Werror=implicit -Werror=implicit-function-declaration 
-Werror=incompatible-pointer-types -Werror=init-self -Werror=int-conversion 
-Werror=int-to-pointer-cast -Werror=main -Werror=mis
 leading-indentation -Werror=missing-braces -Werror=missing-include-dirs 
-Werror=nonnull -Werror=overflow -Werror=pointer-arith 
-Werror=pointer-to-int-cast -Werror=redundant-decls -Werror=return-type 
-Werror=sequence-point -Werror=shadow -Werror=strict-prototypes 
-Werror=trigraphs -Werror=undef -Werror=write-strings -Wformat-nonliteral 
-Werror=format-security -Werror=format=2 -Wignored-qualifiers 
-Wimplicit-function-declaration -Wlogical-op -Wmissing-format-attribute 
-Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs 
-Wno-cast-function-type -Wno-missing-field-initializers -Wno-sign-compare 
-Wno-unused-parameter -Wold-style-definition -Wpointer-arith -Wredundant-decls 
-Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized 
-Wunused -fno-strict-aliasing -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -fvisibility=hidden -DG_DISABLE_ASSERT 
-DG_DISABLE_CAST_CHEC
 KS -MD -MQ src/libdazzle-1.0.so.0.p/meson-generated_.._dzl-enums.c.o -MF 
src/libdazzle-1.0.so.0.p/meson-generated_.._dzl-enums.c.o.d -o 
src/libdazzle-1.0.so.0.p/meson-generated_.._dzl-enums.c.o -c src/dzl-enums.c
[10/287] cc -Isrc/libdazzle-1.0.so.0.p -Isrc -I../src -I. -I.. 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 

Processed: notfound 984127 in 1.10.1-3, notfound 984130 in 1.0.12-1

[Debian Bug Tracking System]

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

> notfound 984127 1.10.1-3
Bug #984127 {Done: Simon McVittie } [src:flatpak] flatpak: 
ftbfs with GCC-11: argument 2 of __atomic_load discards volatile qualifier
No longer marked as found in versions flatpak/1.10.1-3.
> notfound 984130 1.0.12-1
Bug #984130 {Done: Simon McVittie } [src:flatpak-builder] 
flatpak-builder: ftbfs with GCC-11: argument 2 of ‘__atomic_load’ discards 
‘volatile’ qualifier
No longer marked as found in versions flatpak-builder/1.0.12-1.
> thanks
Stopping processing here.

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

Bug#984394: marked as done (vlc: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Mon, 11 Oct 2021 00:25:58 +0200
with message-id 
and subject line Re: Bug#984394: vlc: ftbfs with GCC-11
has caused the Debian Bug report #984394,
regarding vlc: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vlc
Version: 3.0.12-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vlc_3.0.12-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
libtool: link: echo "{ global:" > .libs/libmpgv_plugin.ver
libtool: link:  cat .libs/libmpgv_plugin.exp | sed -e "s/\(.*\)/\1;/" >> 
.libs/libmpgv_plugin.ver
libtool: link:  echo "local: *; };" >> .libs/libmpgv_plugin.ver
libtool: link:  gcc -shared  -fPIC -DPIC  demux/mpeg/.libs/mpgv.o   -Wl,-rpath 
-Wl,/<>/src/.libs ../compat/.libs/libcompat.a 
../src/.libs/libvlccore.so  -g -O2 -fstack-protector-strong -O3 -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,defs   -Wl,-soname -Wl,libmpgv_plugin.so 
-Wl,-version-script -Wl,.libs/libmpgv_plugin.ver -o .libs/libmpgv_plugin.so
libtool: link: ( cd ".libs" && rm -f "libmpgv_plugin.la" && ln -s 
"../libmpgv_plugin.la" "libmpgv_plugin.la" )
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/b4s.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo "$p")\" 
-D__PLUGIN__  -I./access -I./codec -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Wextra 
-Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var 
-Wformat-security -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes 
-Werror-implicit-function-declaration -Winit-self -Wlogical-op -Wshadow=local 
-pipe -fvisibility=hidden -O3 -fno-math-errno -funsafe-math-optimizations 
-fno-rounding-math -fno-signaling-nans -fcx-limited-range -funroll-loops 
-fomit-frame-pointer -c -o demux/playlist/b4s.lo demux/playlist/b4s.c
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/dvb.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo "$p")\" 
-D__PLUGIN__  -I./access -I./codec -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Wextra 
-Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var 
-Wformat-security -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes 
-Werror-implicit-function-declaration -Winit-self -Wlogical-op -Wshadow=local 
-pipe -fvisibility=hidden -O3 -fno-math-errno -funsafe-math-optimizations 
-fno-rounding-math -fno-signaling-nans -fcx-limited-range -funroll-loops 
-fomit-frame-pointer -c -o demux/playlist/dvb.lo demux/playlist/dvb.c
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/ifo.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo "$p")\" 
-D__PLUGIN__  -I./access -I./codec 

Processed: tagging 984054

[Debian Bug Tracking System]

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

> tags 984054 + confirmed
Bug #984054 [src:evolvotron] evolvotron: ftbfs with GCC-11
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Otto Kekäläinen]

> The problem is in the ibdata1 file (about 450MB). Deleted other database 
> directories and it still crashes, deleted ibdata1 and it runs.
>
> How to bisect mariadb from git? Tried:
> $ git bisect good mariadb-10.3.29
> $ git bisect bad mariadb-10.3.31
> the build process showed version 10.2 so I aborted it.
>
> Checked out mariadb-10.3.30 but dpkg-buildpackage failed with:
> dh_install: mariadb-plugin-cassandra missing files: 
> etc/mysql/conf.d/cassandra.cnf

Some dependency was missing and Cassandra was not built. Note that the
upstream repository is not identical to the one in Debian regarding
the contents of debian/ directory. MariaDB builds without a cache take
30 mins each and there are all kinds of things going on. Doing bisect
(fully correctly) on MariaDB is hard even for experienced developers.
Your time is probably better spent doing some other kind of debugging.

I recommend that you file a bug about this upstream, and try to attach
relevant info from the error log, maybe a strace output etc. Upstream
devs will guide you on what to debug next.

One thing you could also try is to start the server with 10.3.29 and
ensure that you have a clean shutdown (SET GLOBAL
innodb_fast_shutdown=0; SHUTDOWN) and only after that start with the
new 10.3.31 binary.

Ref
- https://mariadb.com/kb/en/shutdown/#see-also
- https://www.percona.com/blog/2020/05/07/prepare-mysql-for-a-safe-shutdown/

Processed: Re: Bug#984138: fs-uae: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #984138 [src:fs-uae] fs-uae: ftbfs with GCC-11
Added tag(s) patch.

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

Bug#984138: fs-uae: ftbfs with GCC-11

[John Paul Adrian Glaubitz]

Control: tags -1 +patch

Hi!

On 3/3/21 17:12, Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
> severity of this report will be raised before the bookworm release,
> so nothing has to be done for the bullseye release.

FWIW, upstream has fixed the issue on the stable branch already [1], see
attached patch. I'm just waiting for the upcoming stable version to be
released.

I'll then uploaded the fixed version immediately.

Adrian

> [1] 
> https://github.com/FrodeSolheim/fs-uae/commit/bf81e7d2a60b2c8646663889e4a4431b988ae972

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
From bf81e7d2a60b2c8646663889e4a4431b988ae972 Mon Sep 17 00:00:00 2001
From: Frode Solheim 
Date: Fri, 8 Oct 2021 11:39:16 +0200
Subject: [PATCH] Work around an incompatibility with C++17

---
 src/dosbox/setup.h | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/src/dosbox/setup.h b/src/dosbox/setup.h
index db75ada8..e0a3a75d 100644
--- a/src/dosbox/setup.h
+++ b/src/dosbox/setup.h
@@ -54,6 +54,12 @@ public:

 };
 
+#ifdef FSUAE
+// Work around an incompatibility with C++17. It does not seem like these
+// functions are used anyway.
+#define throw(...) throw()
+#endif
+
 class Value {
 /* 
  * Multitype storage container that is aware of the currently stored type in it.
@@ -113,6 +119,11 @@ private:
 	void set_double(std::string const& in);
 };
 
+#ifdef FSUAE
+#undef throw
+#endif
+
+
 class Property {
 public:
 	struct Changeable { enum Value {Always, WhenIdle,OnlyAtStart};};
-- 
2.33.0

Processed: fixed 996083 in 3.55.0-1

[Debian Bug Tracking System]

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

> fixed 996083 3.55.0-1
Bug #996083 {Done: Adrian Bunk } [src:filezilla] filezilla 
FTBFS with libfilezilla19
Marked as fixed in versions filezilla/3.55.0-1.
> thanks
Stopping processing here.

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

Processed: affects 996028

[Debian Bug Tracking System]

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

> affects 996028 + release.debian.org
Bug #996028 [mariadb-server] InnoDB: corrupted TRX_NO after upgrading to 10.3.31
Added indication that 996028 affects release.debian.org
> thanks
Stopping processing here.

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

Bug#984130: marked as done (flatpak-builder: ftbfs with GCC-11: argument 2 of ‘__atomic_load’ discards ‘volatile’ qualifier)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 22:01:09 +0100
with message-id 
and subject line Re: flatpak, flatpak-builder: ftbfs with GCC-11
has caused the Debian Bug report #984130,
regarding flatpak-builder: ftbfs with GCC-11: argument 2 of ‘__atomic_load’ 
discards ‘volatile’ qualifier
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flatpak-builder
Version: 1.0.12-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/flatpak-builder_1.0.12-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  | 
^
src/builder-options.c:74:1: note: in expansion of macro 
‘G_DEFINE_TYPE_WITH_CODE’
   74 | G_DEFINE_TYPE_WITH_CODE (BuilderOptions, builder_options, G_TYPE_OBJECT,
  | ^~~
In file included from /usr/include/glib-2.0/glib/gthread.h:32,
 from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
 from /usr/include/glib-2.0/glib.h:32,
 from /usr/include/glib-2.0/glib/gi18n.h:21,
 from src/builder-extension.c:30:
src/builder-extension.c: In function ‘builder_extension_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 | __atomic_load (gapg_temp_atomic, _temp_newval, 
__ATOMIC_SEQ_CST);   \
  | ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 | (!g_atomic_pointer_get (location) && \
  |   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:2000:7: note: in expansion of macro 
‘g_once_init_enter’
 2000 |   if (g_once_init_enter (_define_type_id__volatile))  \
  |   ^
/usr/include/glib-2.0/gobject/gtype.h:2032:3: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER’
 2032 |   _G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER(TypeName, type_name, 
TYPE_PARENT, flags) \
  |   ^~
/usr/include/glib-2.0/gobject/gtype.h:1759:61: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN’
 1759 | #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_)  
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()
  | 
^
/usr/include/glib-2.0/gobject/gtype.h:1600:61: note: in expansion of macro 
‘G_DEFINE_TYPE_EXTENDED’
 1600 | #define G_DEFINE_TYPE(TN, t_n, T_P) 
G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {})
  | 
^~
src/builder-extension.c:64:1: note: in expansion of macro ‘G_DEFINE_TYPE’
   64 | G_DEFINE_TYPE (BuilderExtension, builder_extension, G_TYPE_OBJECT);
  | ^
In file included from /usr/include/glib-2.0/glib/gthread.h:32,
 

Bug#984127: marked as done (flatpak: ftbfs with GCC-11: argument 2 of __atomic_load discards volatile qualifier)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 22:01:09 +0100
with message-id 
and subject line Re: flatpak, flatpak-builder: ftbfs with GCC-11
has caused the Debian Bug report #984127,
regarding flatpak: ftbfs with GCC-11: argument 2 of __atomic_load discards 
volatile qualifier
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flatpak
Version: 1.10.1-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/flatpak_1.10.1-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
echo "Exec=env G_TEST_SRCDIR=/usr/libexec/installed-tests/Flatpak 
G_TEST_BUILDDIR=/usr/libexec/installed-tests/Flatpak $wrapper 
/usr/libexec/installed-tests/Flatpak/test-extensions.sh --tap" >> 
tests/test-extensions.sh.test.tmp; \
echo 'Output=TAP' >> tests/test-extensions.sh.test.tmp; \
mv tests/test-extensions.sh.test.tmp tests/test-extensions.sh.test)
(echo '[Test]' > tests/test-oci.sh.test.tmp; \
echo 'Type=session' >> tests/test-oci.sh.test.tmp; \
if [[ test-oci.sh == *.wrap ]]; then \
wrapper=/usr/libexec/installed-tests/Flatpak/test-wrapper.sh; \
fi; \
echo "Exec=env G_TEST_SRCDIR=/usr/libexec/installed-tests/Flatpak 
G_TEST_BUILDDIR=/usr/libexec/installed-tests/Flatpak $wrapper 
/usr/libexec/installed-tests/Flatpak/test-oci.sh --tap" >> 
tests/test-oci.sh.test.tmp; \
echo 'Output=TAP' >> tests/test-oci.sh.test.tmp; \
mv tests/test-oci.sh.test.tmp tests/test-oci.sh.test)
(echo '[Test]' > tests/test-override.sh.test.tmp; \
echo 'Type=session' >> tests/test-override.sh.test.tmp; \
if [[ test-override.sh == *.wrap ]]; then \
wrapper=/usr/libexec/installed-tests/Flatpak/test-wrapper.sh; \
fi; \
echo "Exec=env G_TEST_SRCDIR=/usr/libexec/installed-tests/Flatpak 
G_TEST_BUILDDIR=/usr/libexec/installed-tests/Flatpak $wrapper 
/usr/libexec/installed-tests/Flatpak/test-override.sh --tap" >> 
tests/test-override.sh.test.tmp; \
echo 'Output=TAP' >> tests/test-override.sh.test.tmp; \
mv tests/test-override.sh.test.tmp tests/test-override.sh.test)
(echo '[Test]' > tests/test-auth.sh.test.tmp; \
echo 'Type=session' >> tests/test-auth.sh.test.tmp; \
if [[ test-auth.sh == *.wrap ]]; then \
wrapper=/usr/libexec/installed-tests/Flatpak/test-wrapper.sh; \
fi; \
echo "Exec=env G_TEST_SRCDIR=/usr/libexec/installed-tests/Flatpak 
G_TEST_BUILDDIR=/usr/libexec/installed-tests/Flatpak $wrapper 
/usr/libexec/installed-tests/Flatpak/test-auth.sh --tap" >> 
tests/test-auth.sh.test.tmp; \
echo 'Output=TAP' >> tests/test-auth.sh.test.tmp; \
mv tests/test-auth.sh.test.tmp tests/test-auth.sh.test)
(echo '[Test]' > tests/test-unused.sh.test.tmp; \
echo 'Type=session' >> tests/test-unused.sh.test.tmp; \
if [[ test-unused.sh == *.wrap ]]; then \
wrapper=/usr/libexec/installed-tests/Flatpak/test-wrapper.sh; \
fi; \
echo "Exec=env G_TEST_SRCDIR=/usr/libexec/installed-tests/Flatpak 
G_TEST_BUILDDIR=/usr/libexec/installed-tests/Flatpak $wrapper 
/usr/libexec/installed-tests/Flatpak/test-unused.sh --tap" >> 
tests/test-unused.sh.test.tmp; \
echo 'Output=TAP' >> tests/test-unused.sh.test.tmp; \
mv 

Processed: tagging 983959, tagging 983999, tagging 984242, tagging 994237, tagging 994240, tagging 983958 ...

[Debian Bug Tracking System]

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

> # tag as ftbfs
> tags 983959 + ftbfs
Bug #983959 [src:actor-framework] actor-framework: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983999 + ftbfs
Bug #983999 [src:bonnie++] bonnie++: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984242 + ftbfs
Bug #984242 [src:mpich] mpich: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 994237 + ftbfs
Bug #994237 [src:criterion] fix ftbfs with GCC 11
Added tag(s) ftbfs.
> tags 994240 + ftbfs
Bug #994240 [src:yosys] fix ftbfs with GCC 11
Added tag(s) ftbfs.
> tags 983958 + ftbfs
Bug #983958 [src:aces3] aces3: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983961 + ftbfs
Bug #983961 [src:advancecomp] advancecomp: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983963 + ftbfs
Bug #983963 [src:aiksaurus] aiksaurus: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983964 + ftbfs
Bug #983964 [src:android-platform-art] android-platform-art: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983966 + ftbfs
Bug #983966 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983967 + ftbfs
Bug #983967 [src:aoflagger] aoflagger: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983968 + ftbfs
Bug #983968 [src:android-platform-system-tools-aidl] 
android-platform-system-tools-aidl: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983969 + ftbfs
Bug #983969 [src:armnn] armnn: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983970 + ftbfs
Bug #983970 [src:aplus-fsf] aplus-fsf: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983971 + ftbfs
Bug #983971 [src:asc] asc: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983972 + ftbfs
Bug #983972 [src:aqsis] aqsis: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983973 + ftbfs
Bug #983973 [src:asmjit] asmjit: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983974 + ftbfs
Bug #983974 [src:audacious] audacious: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983976 + ftbfs
Bug #983976 [src:ayatana-indicator-application] ayatana-indicator-application: 
ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983977 + ftbfs
Bug #983977 [src:avarice] avarice: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983979 + ftbfs
Bug #983979 [src:bagel] bagel: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983980 + ftbfs
Bug #983980 [src:ayatana-indicator-messages] ayatana-indicator-messages: ftbfs 
with GCC-11
Added tag(s) ftbfs.
> tags 983984 + ftbfs
Bug #983984 [src:beignet] beignet: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983985 + ftbfs
Bug #983985 [src:bctoolbox] bctoolbox: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983986 + ftbfs
Bug #983986 [src:berusky] berusky: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983987 + ftbfs
Bug #983987 [src:belr] belr: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983988 + ftbfs
Bug #983988 [src:benchmark] benchmark: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983989 + ftbfs
Bug #983989 [src:bible-kjv] bible-kjv: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983990 + ftbfs
Bug #983990 [src:bino] bino: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983991 + ftbfs
Bug #983991 [src:bist] bist: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983993 + ftbfs
Bug #983993 [src:binutils-avr] binutils-avr: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 983996 + ftbfs
Bug #983996 [src:blist] blist: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984001 + ftbfs
Bug #984001 [src:bpftrace] bpftrace: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984002 + ftbfs
Bug #984002 [src:boxbackup] boxbackup: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984004 + ftbfs
Bug #984004 [src:briquolo] briquolo: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984005 + ftbfs
Bug #984005 [src:cava-alsa] cava-alsa: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984006 + ftbfs
Bug #984006 [src:caja-eiciel] caja-eiciel: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984008 + ftbfs
Bug #984008 [src:cbmc] cbmc: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984010 + ftbfs
Bug #984010 [src:chkservice] chkservice: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984011 + ftbfs
Bug #984011 [src:chatty] chatty: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984012 + ftbfs
Bug #984012 [src:chuck] chuck: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984013 + ftbfs
Bug #984013 [src:chromium] chromium: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984014 + ftbfs
Bug #984014 [src:clementine] clementine: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984015 + ftbfs
Bug #984015 [src:cif-tools] cif-tools: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984016 + ftbfs
Bug #984016 [src:cloudcompare] cloudcompare: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984017 + ftbfs
Bug #984017 [src:clucene-core] clucene-core: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984018 + ftbfs
Bug #984018 [src:clonalorigin] clonalorigin: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984019 + ftbfs
Bug #984019 [src:cmtk] cmtk: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 984020 + ftbfs
Bug #984020 [src:codeblocks] codeblocks: ftbfs with GCC-11
Added tag(s) ftbfs.
> tags 

Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Ondrej Zary]

On Sunday 10 October 2021 16:55:45 Otto Kekäläinen wrote:
> Hello!
> 
> Thanks for reporting. Could you please check if this has been reported
> upstream at jira.mariadb.org?
> 
> There isn't much we can do about InnoDB internals in Debian packaging.
> 

The problem is in the ibdata1 file (about 450MB). Deleted other database 
directories and it still crashes, deleted ibdata1 and it runs.

How to bisect mariadb from git? Tried:
$ git bisect good mariadb-10.3.29
$ git bisect bad mariadb-10.3.31
the build process showed version 10.2 so I aborted it.

Checked out mariadb-10.3.30 but dpkg-buildpackage failed with:
dh_install: mariadb-plugin-cassandra missing files: 
etc/mysql/conf.d/cassandra.cnf

-- 
Ondrej Zary

Bug#996083: filezilla FTBFS with libfilezilla19

[Adrian Bunk]

Source: filezilla
Version: 3.52.2-3
Severity: serious
Tags: ftbfs bookworm sid
Control: close -1 3.55.1-1

https://buildd.debian.org/status/logs.php?pkg=filezilla=3.52.2-3%2Bb1

...
writer.cpp: In member function ‘aio_result file_writer::open(uint64_t, bool, 
aio_base::shm_flag)’:
writer.cpp:309:56: error: cannot convert ‘bool’ to ‘fz::mkdir_permissions’
  309 |   fz::mkdir(fz::to_native(local_path.GetPath()), true, false, 
_created);
  |^
  ||
  |bool
In file included from writer.cpp:3:
/usr/include/libfilezilla/local_filesys.hpp:182:99: note:   initializing 
argument 3 of ‘fz::result fz::mkdir(const native_string&, bool, 
fz::mkdir_permissions, fz::native_string*)’
  182 | result FZ_PUBLIC_SYMBOL mkdir(native_string const& absolute_path, bool 
recurse, mkdir_permissions permissions = mkdir_permissions::normal, 
native_string * last_created = nullptr);
  | 
~~^~~
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -std=c++17 
-DHAVE_CONFIG_H   -I../../config -I/usr/include/p11-kit-1 -DBUILDING_FILEZILLA 
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c -o ftp/libfzclient_private_la-delete.lo `test 
-f 'ftp/delete.cpp' || echo './'`ftp/delete.cpp
make[4]: *** [Makefile:1351: libfzclient_private_la-writer.lo] Error 1



This is already fixed in the version at mentors.debian.net (#994495).

Processed: filezilla FTBFS with libfilezilla19

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.55.1-1
Bug #996083 [src:filezilla] filezilla FTBFS with libfilezilla19
The source 'filezilla' and version '3.55.1-1' do not appear to match any binary 
packages
Marked as fixed in versions filezilla/3.55.1-1.
Bug #996083 [src:filezilla] filezilla FTBFS with libfilezilla19
Marked Bug as done

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

Bug#931345: nvchecker: autopkgtest regression in June 2019

[Afif Elghraoui]

Hello,

On 11/12/20 2:11 AM, Paul Gevers wrote:
> severity 931345 serious
> user debian...@lists.debian.org
> usertag 931345 timeout
> thanks
> 
> please upload a fixed package.
> 
> The test if timing out nowadays too, so I'll block it from being tested
> to avoid stress on our infrastructure until this bug is fixed.
> 

This bug has been fixed for about a week now but nvchecker still appears
to be blocked from debci. Does that need to be manually changed? I
expected it to be removed automatically once the bug was closed.

thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
https://afif.ghraoui.name

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 996068 
> https://gitlab.com/jenslody/gnome-shell-extension-panel-osd/issues/47
Bug #996068 [gnome-shell-extension-panel-osd] gnome-shell-extension-panel-osd: 
does not declare compatibility with GNOME Shell 41
Set Bug forwarded-to-address to 
'https://gitlab.com/jenslody/gnome-shell-extension-panel-osd/issues/47'.
> forwarded 993194 
> https://gitlab.com/jenslody/gnome-shell-extension-panel-osd/issues/47
Bug #993194 [gnome-shell-extension-panel-osd] gnome-shell-extension-panel-osd: 
does not declare compatibility with GNOME Shell 40
Set Bug forwarded-to-address to 
'https://gitlab.com/jenslody/gnome-shell-extension-panel-osd/issues/47'.
> --
Stopping processing here.

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

Processed: GCC 11 is now the default, raising the severity of the ftbfs issues

[Debian Bug Tracking System]

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

> severity 983959 serious
Bug #983959 [src:actor-framework] actor-framework: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983999 serious
Bug #983999 [src:bonnie++] bonnie++: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984242 serious
Bug #984242 [src:mpich] mpich: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 994237 serious
Bug #994237 [src:criterion] fix ftbfs with GCC 11
Severity set to 'serious' from 'important'
> severity 994240 serious
Bug #994240 [src:yosys] fix ftbfs with GCC 11
Severity set to 'serious' from 'important'
> severity 983958 serious
Bug #983958 [src:aces3] aces3: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983961 serious
Bug #983961 [src:advancecomp] advancecomp: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983963 serious
Bug #983963 [src:aiksaurus] aiksaurus: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983964 serious
Bug #983964 [src:android-platform-art] android-platform-art: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983966 serious
Bug #983966 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983967 serious
Bug #983967 [src:aoflagger] aoflagger: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983968 serious
Bug #983968 [src:android-platform-system-tools-aidl] 
android-platform-system-tools-aidl: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983969 serious
Bug #983969 [src:armnn] armnn: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983970 serious
Bug #983970 [src:aplus-fsf] aplus-fsf: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983971 serious
Bug #983971 [src:asc] asc: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983972 serious
Bug #983972 [src:aqsis] aqsis: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983973 serious
Bug #983973 [src:asmjit] asmjit: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983974 serious
Bug #983974 [src:audacious] audacious: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983976 serious
Bug #983976 [src:ayatana-indicator-application] ayatana-indicator-application: 
ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983977 serious
Bug #983977 [src:avarice] avarice: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983979 serious
Bug #983979 [src:bagel] bagel: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983980 serious
Bug #983980 [src:ayatana-indicator-messages] ayatana-indicator-messages: ftbfs 
with GCC-11
Severity set to 'serious' from 'important'
> severity 983984 serious
Bug #983984 [src:beignet] beignet: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983985 serious
Bug #983985 [src:bctoolbox] bctoolbox: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983986 serious
Bug #983986 [src:berusky] berusky: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983987 serious
Bug #983987 [src:belr] belr: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983988 serious
Bug #983988 [src:benchmark] benchmark: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983989 serious
Bug #983989 [src:bible-kjv] bible-kjv: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983990 serious
Bug #983990 [src:bino] bino: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983991 serious
Bug #983991 [src:bist] bist: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983993 serious
Bug #983993 [src:binutils-avr] binutils-avr: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 983996 serious
Bug #983996 [src:blist] blist: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984001 serious
Bug #984001 [src:bpftrace] bpftrace: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984002 serious
Bug #984002 [src:boxbackup] boxbackup: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984004 serious
Bug #984004 [src:briquolo] briquolo: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984005 serious
Bug #984005 [src:cava-alsa] cava-alsa: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984006 serious
Bug #984006 [src:caja-eiciel] caja-eiciel: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984008 serious
Bug #984008 [src:cbmc] cbmc: ftbfs with GCC-11
Severity set to 'serious' from 'important'
> severity 984010 serious
Bug #984010 [src:chkservice] chkservice: ftbfs with GCC-11

Processed: tagging 995580

[Debian Bug Tracking System]

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

> tags 995580 + ftbfs
Bug #995580 [wine] wine build-depends on unicode-data (< 14) but 
testing/unstable has 14.0.0-1
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#996038: marked as done (sphinxcontrib-httpdomain: Extension unusable due to botched patch)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 20:23:07 +
with message-id 
and subject line Bug#996038: fixed in sphinxcontrib-httpdomain 1.7.0-3
has caused the Debian Bug report #996038,
regarding sphinxcontrib-httpdomain: Extension unusable due to botched patch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
996038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-httpdomain
Version: 1.7.0-1
Severity: grave
Justification: renders package unusable

Last year, in commit e0233aea I backported a fix to a bug in the plugin setup()
function. More recently, in commit 61f14798, the patch was refreshed
incorrectly leading to a duplicated call to add_domain, which renders the
package completely unusable (see error below).

The fix is very simple: the patch needs to be removed as the problem it
addressed  was already fixed upstream.


$ sphinx-build -v docs/ build/docs
Running Sphinx v4.2.0

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 276, in 
build_main
app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 231, in 
__init__
self.setup_extension(extension)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 387, in 
setup_extension
self.registry.load_extension(self, extname)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 442, in 
load_extension
metadata = setup(app)
  File "/usr/lib/python3/dist-packages/sphinxcontrib/httpdomain.py", line 763, 
in setup
app.add_domain(HTTPDomain)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 724, in 
add_domain
self.registry.add_domain(domain, override=override)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 164, in 
add_domain
raise ExtensionError(__('domain %s already registered') % domain.name)
sphinx.errors.ExtensionError: domain http already registered



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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Source: sphinxcontrib-httpdomain
Source-Version: 1.7.0-3
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
sphinxcontrib-httpdomain, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated sphinxcontrib-httpdomain 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Oct 2021 21:54:57 +0200
Source: sphinxcontrib-httpdomain
Architecture: source
Version: 1.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 996038
Changes:
 sphinxcontrib-httpdomain (1.7.0-3) unstable; urgency=medium
 .
   * Remove Add_missing_call_to_add_domain.patch (Closes: #996038).
Checksums-Sha1:
 11f8f70701b7a22040c2c94d3b40063b20f5e007 2206 
sphinxcontrib-httpdomain_1.7.0-3.dsc
 c76a4b08058d9e4393d3af777f54b62e092507e5 2852 
sphinxcontrib-httpdomain_1.7.0-3.debian.tar.xz
 374bde1ba70ed60b02f838a0a86a87b4507e661e 6832 
sphinxcontrib-httpdomain_1.7.0-3_amd64.buildinfo
Checksums-Sha256:
 183a691c2c8a269440736c444f8e1b18880de3c923f4ae37113c9a1a1794dbf8 2206 
sphinxcontrib-httpdomain_1.7.0-3.dsc
 6649261f6cc5e18e65859dad9bddbeb6093178adb5bec3b45839848b8a9a8a6a 2852 
sphinxcontrib-httpdomain_1.7.0-3.debian.tar.xz
 24ef38936e9aab9d2305b31d873b5d1c348d31479b7d770655ae98edc517af22 6832 
sphinxcontrib-httpdomain_1.7.0-3_amd64.buildinfo
Files:
 c9fa3a8ec2fe4d2cce7316957c2d386b 2206 python optional 
sphinxcontrib-httpdomain_1.7.0-3.dsc
 80f418eb59fbb93ec4f2707ff7128dbd 

Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL

[Paul Gevers]

Source: postfix-mta-sts-resolver
Version: 1.0.0-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ca-certificates

[X-Debbugs-CC: debian...@lists.debian.org,
ca-certifica...@packages.debian.org]

Dear maintainer(s),

With a recent upload of ca-certificates the autopkgtest of
postfix-mta-sts-resolver fails in testing when that autopkgtest is run
with the binary packages of ca-certificates from unstable. It passes
when run with only packages from testing. In tabular form:

 passfail
ca-certificates  from testing20211004
postfix-mta-sts-resolver from testing1.0.0-4
all others   from testingfrom testing

I copied some of the output at the bottom of this report. The *warning*
seems to be innocent, but causes the test to fail because by default
autopkgtest considers output on stderr as fatal (without the
allow-stderr restriction).

Currently this regression is blocking the migration of ca-certificates
to testing [1]. Of course, ca-certificates shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in ca-certificates was intended and your package needs to update
to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from ca-certificates should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ca-certificates

https://ci.debian.net/data/autopkgtest/testing/amd64/p/postfix-mta-sts-resolver/15856707/log.gz

autopkgtest [19:39:52]: test run: [---
Updating certificates in /etc/ssl/certs...
rehash: warning: skipping ca-certificates.crt,it does not contain
exactly one certificate or CRL
1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
autopkgtest [19:40:04]: test run: ---]
autopkgtest [19:40:04]: test run:  - - - - - - - - - - results - - - - -
- - - - -
run  FAIL stderr: rehash: warning: skipping
ca-certificates.crt,it does not contain exactly one certificate or CRL



OpenPGP_signature
Description: OpenPGP digital signature

Processed: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ca-certificates
Bug #996048 [src:postfix-mta-sts-resolver] postfix-mta-sts-resolver: 
autopkgtest doesn't handle new version of ca-certificates nicely: rehash: 
warning: skipping ca-certificates.crt,it does not contain exactly one 
certificate or CRL
Added indication that 996048 affects src:ca-certificates

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

Processed: closing 989103, tagging 989103

[Debian Bug Tracking System]

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

> close 989103 14.99.2+dfsg1-1
Bug #989103 [pulseaudio] pulseaudio regressed on control=Wave configuration
Marked as fixed in versions pulseaudio/14.99.2+dfsg1-1.
Bug #989103 [pulseaudio] pulseaudio regressed on control=Wave configuration
Marked Bug as done
> tags 989103 + sid bookworm bullseye
Bug #989103 {Done: Laurent Bigonville } [pulseaudio] 
pulseaudio regressed on control=Wave configuration
Added tag(s) bookworm, sid, and bullseye.
> thanks
Stopping processing here.

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

Processed: Bug#996038 marked as pending in sphinxcontrib-httpdomain

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996038 [src:sphinxcontrib-httpdomain] sphinxcontrib-httpdomain: Extension 
unusable due to botched patch
Added tag(s) pending.

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

Bug#996038: marked as pending in sphinxcontrib-httpdomain

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #996038 in sphinxcontrib-httpdomain reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/third-party/sphinxcontrib-httpdomain/-/commit/f901eaa42935d3c44a93a35b4ddccebf64e7ea33


Remove Add_missing_call_to_add_domain.patch (Closes: #996038).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996038

Processed: found 996042 in ttyd/1.6.3-3

[Debian Bug Tracking System]

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

> found 996042 ttyd/1.6.3-3
Bug #996042 [ttyd] Missing sources for the html part
Marked as found in versions ttyd/1.6.3-3.
> thanks
Stopping processing here.

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

Bug#992668: ricochet-im: does not start

[Sebastian Ramacher]

Control: reopen -1

On 2021-09-21 13:08:16 +0800, Paul Wise wrote:
> Control: fixed -1 + 1.1.4-3+b5
> 
> On Sat, 18 Sep 2021 13:06:25 +0800 Paul Wise wrote:
> 
> > I'll request the release team to rebuild it in bullseye/bookworm.
> 
> The rebuild has now happened for unstable/testing.

While I initially scheduled these binNMUs, I no longer think that this
was the correct "fix" for this bug. There is at least the issue that
ricochet-im links with ubsan which is potentially a security issue. See
https://www.openwall.com/lists/oss-security/2016/02/17/9 (thanks to
aurel32 for the link)

And then the question remains if libubsan broke its ABI or broken code
was generated before GCC 10 or …

Cheers

> 
> -- 
> bye,
> pabs
> 
> https://wiki.debian.org/PaulWise



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#992668: ricochet-im: does not start

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #992668 {Done: Paul Wise } [ricochet-im] ricochet-im: does 
not start
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ricochet-im/1.1.4-3.

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

Processed: bug 994391 is forwarded to https://github.com/pimutils/vdirsyncer/issues/922, tagging 994391

[Debian Bug Tracking System]

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

> forwarded 994391 https://github.com/pimutils/vdirsyncer/issues/922
Bug #994391 [vdirsyncer] vdirsyncer is unusable
Set Bug forwarded-to-address to 
'https://github.com/pimutils/vdirsyncer/issues/922'.
> tags 994391 + upstream fixed-upstream
Bug #994391 [vdirsyncer] vdirsyncer is unusable
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#996042: Missing sources for the html part

[Shengjing Zhu]

Package: ttyd
Version: 1.6.3+20210924-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

+ src/html.h is not the preferred source format, it's generated by the source
  in html/ dir.

+ source in html/ dir is not completed, all devDependencies and dependencies
  listed in html/package.json is not provided.

Bug#994391: Acknowledgement (vdirsyncer is unusable)

[gregor herrmann]

On Wed, 06 Oct 2021 20:17:35 +0200, Vincent-Xavier JUMEL wrote:

> I've upgraded click-threading to 0.5.0 and vdirsyncer works again.
> Should I fill a bugreport against python3-click-threading ?

I got the same error [0] today, after upgrading python3-click from
7.1.2-1 to 8.0.2-1 in unstable.

Reverting to the older version in testing helps.

(python3-click-threading is at 0.4.4-2 since forever.)

Cheers,
gregor

 
[0]
% /usr/bin/vdirsyncer -vdebug sync 
debug: Using 1 maximal workers.
error: Unknown error occurred: unmatched ')' (, line 1)
error: Use `-vdebug` to see the full traceback.
debug:   File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line 
30, in inner
debug: f(*a, **kw)
debug:   File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line 
145, in sync
debug: with wq.join():
debug:   File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug:   File "/usr/lib/python3/dist-packages/vdirsyncer/cli/utils.py", line 
364, in join
debug: with ui_worker.patch_click():
debug:   File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug:   File "/usr/lib/python3/dist-packages/click_threading/__init__.py", 
line 144, in patch_click
debug: with patch_ui_functions(wrapper):
debug:   File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug:   File "/usr/lib/python3/dist-packages/click_threading/monkey.py", line 
50, in patch_ui_functions
debug: stub_f = eval('lambda {s}: {n}._real_click_fn({a})'

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Pat Metheny, B.B. King, Dave Brubeck: Pat Metheny & Heath Brothers /


signature.asc
Description: Digital Signature

Bug#996041: marked as done (metview: FTBFS in bookworm: unresolved symbols)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 21:22:05 +0200
with message-id 
and subject line Re: Bug#996041: metview: FTBFS in bookworm: unresolved symbols
has caused the Debian Bug report #996041,
regarding metview: FTBFS in bookworm: unresolved symbols
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
996041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metview
Version: 5.10.2-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

metview fails to build in bookworm:
| /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -std=gnu++14  -Wdate-time -D_FORTIFY_SOURCE=2 -pipe 
-fpermissive -Wno-write-strings -Wno-deprecated -Werror=return-type -O3 
-DNDEBUG -Wl,-z,relro -Wl,-z,now-Wl,--disable-new-dtags 
CMakeFiles/Eccharts.dir/Eccharts.cc.o -o ../../../bin/Eccharts  
-Wl,-rpath,/<>/debian/build/lib:/usr/lib/x86_64-linux-gnu/openmpi/lib:
 ../../../lib/libMetview.so.0.0.0 ../../../lib/libMvFTimeUtil.so.0.0.0 
../../../lib/libmarsclient.so.0.0.0 /usr/lib/x86_64-linux-gnu/libeccodes.so.0 
../../../lib/libmir.so.0.0.0 /usr/lib/x86_64-linux-gnu/libatlas_ecmwf.so.0.26 
/usr/lib/x86_64-linux-gnu/libeckit_mpi.so.0d 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
/usr/lib/gcc/x86_64-linux-gnu/10/libgomp.so 
/usr/lib/x86_64-linux-gnu/libpthread.so 
/usr/lib/x86_64-linux-gnu/libeckit_linalg.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit_geometry.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit_option.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit.so.0d 
/usr/lib/x86_64-linux-gnu/libeccodes.so.0 
/usr/lib/x86_64-linux-gnu/libemosR64.so 
/usr/lib/x86_64-linux-gnu/libeccodes.so.0 /usr/lib/x86_64-linux-gnu/libfftw3.so 
/usr/lib/x86_64-linux-gnu/libcurl.so -lterralib -lemosR64 -leccodes -leckit 
-leckit_option /usr/lib/x86_64-linux-gnu/libnetcdf.so 
/usr/lib/x86_64-linux-gnu/libodccore.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit_sql.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit.so.0d -lm /usr/lib/x86_64-linux-gnu/librt.so 
-lpthread -ldl 
| /usr/bin/ld: CMakeFiles/Eccharts.dir/Eccharts.cc.o: in function 
`MvMacroCallerService::registerCallbacks()':
| ./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:50: 
undefined reference to `add_progress_callback'
| /usr/bin/ld: 
./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:50: 
undefined reference to `add_progress_callback'
| /usr/bin/ld: 
./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:53: 
undefined reference to `add_reply_callback'
| /usr/bin/ld: CMakeFiles/Eccharts.dir/Eccharts.cc.o: in function 
`Eccharts::generateData(MvRequest const&, MvRequest&, 
std::__cxx11::basic_string, std::allocator > 
const&, std::__cxx11::basic_string, 
std::allocator > const&, bool)':
| ./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:364: 
undefined reference to `svc_connect'
| /usr/bin/ld: 
./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:365: 
undefined reference to `process_service'
| /usr/bin/ld: CMakeFiles/Eccharts.dir/Eccharts.cc.o: in function 
`MvMacroCallerService::registerCallbacks()':
| ./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:53: 
undefined reference to `add_reply_callback'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`get_svc_msg'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`create_service'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`exit_timeout'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`record_function'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`set_svc_err'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`wait_service'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`pool_fetch'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`recording'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`call_function'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`get_svc_err'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`send_progress'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`pool_link_objects'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`set_maximum'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 

Bug#996041: metview: FTBFS in bookworm: unresolved symbols

[Sebastian Ramacher]

Source: metview
Version: 5.10.2-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

metview fails to build in bookworm:
| /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -std=gnu++14  -Wdate-time -D_FORTIFY_SOURCE=2 -pipe 
-fpermissive -Wno-write-strings -Wno-deprecated -Werror=return-type -O3 
-DNDEBUG -Wl,-z,relro -Wl,-z,now-Wl,--disable-new-dtags 
CMakeFiles/Eccharts.dir/Eccharts.cc.o -o ../../../bin/Eccharts  
-Wl,-rpath,/<>/debian/build/lib:/usr/lib/x86_64-linux-gnu/openmpi/lib:
 ../../../lib/libMetview.so.0.0.0 ../../../lib/libMvFTimeUtil.so.0.0.0 
../../../lib/libmarsclient.so.0.0.0 /usr/lib/x86_64-linux-gnu/libeccodes.so.0 
../../../lib/libmir.so.0.0.0 /usr/lib/x86_64-linux-gnu/libatlas_ecmwf.so.0.26 
/usr/lib/x86_64-linux-gnu/libeckit_mpi.so.0d 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
/usr/lib/gcc/x86_64-linux-gnu/10/libgomp.so 
/usr/lib/x86_64-linux-gnu/libpthread.so 
/usr/lib/x86_64-linux-gnu/libeckit_linalg.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit_geometry.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit_option.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit.so.0d 
/usr/lib/x86_64-linux-gnu/libeccodes.so.0 
/usr/lib/x86_64-linux-gnu/libemosR64.so 
/usr/lib/x86_64-linux-gnu/libeccodes.so.0 /usr/lib/x86_64-linux-gnu/libfftw3.so 
/usr/lib/x86_64-linux-gnu/libcurl.so -lterralib -lemosR64 -leccodes -leckit 
-leckit_option /usr/lib/x86_64-linux-gnu/libnetcdf.so 
/usr/lib/x86_64-linux-gnu/libodccore.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit_sql.so.0d 
/usr/lib/x86_64-linux-gnu/libeckit.so.0d -lm /usr/lib/x86_64-linux-gnu/librt.so 
-lpthread -ldl 
| /usr/bin/ld: CMakeFiles/Eccharts.dir/Eccharts.cc.o: in function 
`MvMacroCallerService::registerCallbacks()':
| ./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:50: 
undefined reference to `add_progress_callback'
| /usr/bin/ld: 
./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:50: 
undefined reference to `add_progress_callback'
| /usr/bin/ld: 
./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:53: 
undefined reference to `add_reply_callback'
| /usr/bin/ld: CMakeFiles/Eccharts.dir/Eccharts.cc.o: in function 
`Eccharts::generateData(MvRequest const&, MvRequest&, 
std::__cxx11::basic_string, std::allocator > 
const&, std::__cxx11::basic_string, 
std::allocator > const&, bool)':
| ./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:364: 
undefined reference to `svc_connect'
| /usr/bin/ld: 
./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:365: 
undefined reference to `process_service'
| /usr/bin/ld: CMakeFiles/Eccharts.dir/Eccharts.cc.o: in function 
`MvMacroCallerService::registerCallbacks()':
| ./debian/build/metview/src/Eccharts/./metview/src/Eccharts/Eccharts.cc:53: 
undefined reference to `add_reply_callback'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`get_svc_msg'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`create_service'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`exit_timeout'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`record_function'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`set_svc_err'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`wait_service'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`pool_fetch'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`recording'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`call_function'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`get_svc_err'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`send_progress'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`pool_link_objects'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`set_maximum'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`send_later'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`destroy_service'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`pool_link'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`get_svc_ref'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`pool_store'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`send_message'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`call_service'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`add_service_callback'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`keep_alive'
| /usr/bin/ld: ../../../lib/libMetview.so.0.0.0: undefined reference to 
`re_dispatch'
| /usr/bin/ld: 

Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: subscribe -1

On Sun, 10 Oct 2021 16:13:29 +0200 Ondrej Zary  wrote:
> Package: mariadb-server
> Version: 1:10.3.31-0+deb10u1
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> upgrading mariadb-server from 1:10.3.29-0+deb10u1 to 1:10.3.31-0+deb10u1
failed
> because mariadb failed to start. /var/log/mysql/error.log:
> 
> 2021-10-10 15:12:49 0 [ERROR] InnoDB: corrupted TRX_NO 10002001c6986c3
> 2021-10-10 15:12:49 0 [ERROR] InnoDB: Plugin initialization aborted with
error Data structure corruption
> 2021-10-10 15:12:50 0 [ERROR] Plugin 'InnoDB' init function returned error.
> 2021-10-10 15:12:50 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.
> 2021-10-10 15:12:50 0 [ERROR] Unknown/unsupported storage engine: InnoDB
> 2021-10-10 15:12:50 0 [ERROR] Aborting
> 
> Fortunately, it works after downgrading back to 10.3.29.
> Data does not seem to be corrupted.
> 

For what's it's worth I'm experiencing the same issue on my installation. I
took me some time to find that bug (and I started to dig how to repair innodb
stuff. Good to know downgrading should help, thanks.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFjNSIACgkQ3rYcyPpX
RFsxlQgAo0eUU9T8XaIsYIw/jx4dmbRf9DO8/IxPvFuMw0zkn7JO2LxL61IRIcAa
SDljx7UjnJpTpJ6Nc6XXQ8sU3EIb4qUen1dRME383jcUEAN0Yh3F2cvBmNkjV7bN
rDdRf74leH76uYo9sPIgWnZwy2U2I9HVKhlD3uo2MF53ksem1yVJh3Jvll5w0ZsM
SsMCO2wTjq3RFbc38bqKASSh/+UvXAxxY/6R6bxc+YIWqsim9z8XQ9TKZXdnjPS+
aOcJblZarGOjdC2AwbeT9GVaBoaCx9V9RlQDn3WoMvVhHvjfI32j+tEG1uWnicC/
q1tnUp/9oBnvt8eYDbRY3ny3oC6ylA==
=oOyd
-END PGP SIGNATURE-

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

[Timo Aaltonen]

On 10.10.2021 20.04, Spencer Olson wrote:



On Sun, Oct 10, 2021, 10:38 Timo Aaltonen > wrote:


On 10.10.2021 18.41, Spencer Olson wrote:
 > Did some more investigation.  I downloaded the packages that are
being
 > used on centos stream 8.  First I tried my test code with their
version
 > of libssl3.so preloaded:  it failed in the same way as all the
others
 > failed--not surprisingly since its version is much later than the
3.39
 > version where this changed.
 >
 > Then, I downloaded and took a look at "dogtag-submit" from the
CentOS
 > Stream 8 (RedHat) certmonger package.  As far as I can tell, their
 > version of "dogtag-submit" is *not* linked against libcurl-nss.so
at all
 > like the version on debian sid.  Instead, all their certmonger
helper
 > programs are linked against the OpenSSL version (libcurl.so.4).
 >
 > So, I think that we should just link these against the openssl
version,
 > as the RedHat packages do and get things to work again.

Hmm, thanks.. indeed certmonger is still built against
libcurl4-nss-dev,
I've changed it to openssl now and see how it goes against gitlab CI..


Maybe the CI will finish before I can get back to my testing.


And it did, this error is fixed now :)

But it fails later on, so there's some work still to catch up with the 
current distro, but at least this particular annoyance is resolved, so 
many thanks for figuring it out! I was sure the reason was something 
silly and related to the SSL stack (or maybe ciphers) but was blind to 
see it.



--
t

Bug#990223: fixed in pcp 5.3.4-1

[Sunil Mohan Adapa]

On Thu, 07 Oct 2021 23:18:50 + Debian FTP Masters 
 wrote:

Source: pcp
Source-Version: 5.3.4-1
Done: Nathan Scott 



Unfortunately, the solution didn't seem to work. piuparts still failed 
with the latest version[1]. This is presumably because the environment 
under which piuparts has installed the package, systemd was not detected 
and the changes were still made to the configuration file.


We could either drop the changes for non-systemd systems entirely or 
patch the init.d file to pickup a newly environmental file dropped in by 
zeroconf.


Links:

1) https://piuparts.debian.org/sid/fail/pcp-zeroconf_5.3.4-1.log

--
Sunil

Bug#996037: docknot: autopkgtest regression: Can't open /tmp/autopkgtest-lxc.91wiy1gt/downtmp/autopkgtest_tmp/smokenyzokG/lib/App/DocKnot.pm

[Russ Allbery]

Paul Gevers  writes:

> With a recent upload of docknot the autopkgtest of docknot fails in
> testing when that autopkgtest is run with the binary packages of docknot
> from unstable. It passes when run with only packages from testing. In
> tabular form:

Thanks for the report and apologies for the delay in fixing this!  There
was a test suite change that requires an additional file from the source
tree be available and I need to fix the test configuration.  Will fix this
shortly.

Thank you so much for generating these bug reports.  They're incredibly
helpful!

-- 
Russ Allbery (r...@debian.org)  

Bug#996038: sphinxcontrib-httpdomain: Extension unusable due to botched patch

[Martina Ferrari]

Source: sphinxcontrib-httpdomain
Version: 1.7.0-1
Severity: grave
Justification: renders package unusable

Last year, in commit e0233aea I backported a fix to a bug in the plugin setup()
function. More recently, in commit 61f14798, the patch was refreshed
incorrectly leading to a duplicated call to add_domain, which renders the
package completely unusable (see error below).

The fix is very simple: the patch needs to be removed as the problem it
addressed  was already fixed upstream.


$ sphinx-build -v docs/ build/docs
Running Sphinx v4.2.0

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 276, in 
build_main
app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 231, in 
__init__
self.setup_extension(extension)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 387, in 
setup_extension
self.registry.load_extension(self, extname)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 442, in 
load_extension
metadata = setup(app)
  File "/usr/lib/python3/dist-packages/sphinxcontrib/httpdomain.py", line 763, 
in setup
app.add_domain(HTTPDomain)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 724, in 
add_domain
self.registry.add_domain(domain, override=override)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 164, in 
add_domain
raise ExtensionError(__('domain %s already registered') % domain.name)
sphinx.errors.ExtensionError: domain http already registered



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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#996037: docknot: autopkgtest regression: Can't open /tmp/autopkgtest-lxc.91wiy1gt/downtmp/autopkgtest_tmp/smokenyzokG/lib/App/DocKnot.pm

[Paul Gevers]

Source: docknot
Version: 5.00-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of docknot the autopkgtest of docknot fails in
testing when that autopkgtest is run with the binary packages of docknot
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
docknotfrom testing5.00-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=docknot

https://ci.debian.net/data/autopkgtest/testing/amd64/d/docknot/15856761/log.gz

t/cli/spin.t ...
ok 1 - use App::DocKnot::Command;
ok 2 - An object of class 'App::DocKnot::Command' isa
'App::DocKnot::Command'
ok 3 - spin-thread (output specified)
ok 4 - spin-thread (standard output)
t/cli/spin.t spin: Can't open
/tmp/autopkgtest-lxc.91wiy1gt/downtmp/autopkgtest_tmp/smokenyzokG/lib/App/DocKnot.pm:
No such file or directory
cannot remove path when cwd is /tmp/siWfjiZgNP/software/docknot/api for
/tmp/siWfjiZgNP:  at /usr/lib/x86_64-linux-gnu/perl-base/File/Temp.pm
line 2616.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 4.
Dubious, test returned 29 (wstat 7424, 0x1d00)

[...]

t/spin/tree.t ..
ok 1 - require App::DocKnot::Spin;
Can't open
/tmp/autopkgtest-lxc.91wiy1gt/downtmp/autopkgtest_tmp/smokenyzokG/lib/App/DocKnot.pm:
No such file or directory at /usr/share/perl5/App/DocKnot/Spin.pm line 318.
cannot remove path when cwd is /tmp/pjCamv3na8/software/docknot/api for
/tmp/pjCamv3na8:  at /usr/lib/x86_64-linux-gnu/perl-base/File/Temp.pm
line 2616.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
Dubious, test returned 255 (wstat 65280, 0xff00)



OpenPGP_signature
Description: OpenPGP digital signature

Bug#978339: marked as done (gsmlib: FTBFS: configure:17189: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 18:04:18 +
with message-id 
and subject line Bug#978339: fixed in gsmlib 1.10+20120414.gita5e5ae9a-0.4
has caused the Debian Bug report #978339,
regarding gsmlib: FTBFS: configure:17189: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsmlib
Version: 1.10+20120414.gita5e5ae9a-0.3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with autoreconf
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config
>dh_autoreconf
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> aclocal: warning: couldn't open directory 'm4': No such file or directory
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:114: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:114: the top level
> configure.in:114: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:114: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:114: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.in:114: the top level
> autoreconf: configure.in: AM_GNU_GETTEXT is used, but not 
> AM_GNU_GETTEXT_VERSION
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'scripts'.
> libtoolize: copying file 'scripts/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:114: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:114: the top level
> configure.in:114: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.in:114: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.in:114: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.in:114: the top level
> configure:17189: error: possibly undefined macro: AM_INTL_SUBDIR
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:10: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/12/26/gsmlib_1.10+20120414.gita5e5ae9a-0.3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gsmlib
Source-Version: 1.10+20120414.gita5e5ae9a-0.4
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
gsmlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank 

Bug#996032: marked as done (compass-blueprint-plugin: contains ruby functions)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 17:34:07 +
with message-id 
and subject line Bug#996032: fixed in compass-blueprint-plugin 1.0.0-5
has caused the Debian Bug report #996032,
regarding compass-blueprint-plugin: contains ruby functions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
996032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: compass-blueprint-plugin
Version: 1.0.0-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Blueprint stylesheets contain functions implemented in Ruby and
only loaded when used together with Compass.

Compass is dead upstream, and dropped from Debian.

These stylesheets are still useful and valuable with contemporary
Sass implementations if those few functions are re-implemented:

This:

  #{enumerate(".pull", 1, $blueprint-grid-columns)} { ... }

can be replaced by the combination of this once:

  %pull-base {

and this for each use:

  @extend %pull-base;

when used only at one place, which is the case for these stylesheets.



This:

  #{headers(all)} { ... }

can be replaced by this:

  h1, h2, h3, h4, h5, h6 { ... }


This:

  #{elements-of-type(html5-block)} { ... }

can be replaced by this:

  article, aside, details, figcaption, figure, footer, header, hgroup, main, 
menu, nav, section, summary { ... }


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFjGUQACgkQLHwxRsGg
ASE3tRAAmgKWZodOn8pGvlDZtWCIT7/29/oLs9NST3FIoWTJDg5tcvZF3u991RWg
UR+vkhI4mIqOhN/Eg4jpM38dghf6G1PxabQIrkKkC5CnaeAI3lojp+33Y7drBU1F
1wdAs30vtYWu6/yfBYXoMDY0JbFFeskvTrxcjBwVVmAbTEAHVHKpfvplyuKZZNjc
gcdS+LwCJ85DOoYH7jydsi/ybFMxOBBOhb/+5rgJbpL1oJfvpYx4bwEYRRv4PVl6
Cr2xp31bwqKD2BCTCxlmlmQK5WrbOqnOh34s+DRjLBGp2txcwMw13otcV9dswW4s
PBIavvqbS7IswevMyWgCkpS8bOBh5SES6wNzUI/rk/oMOS8p3z0yFKcgb4Xu06Rg
6FuCr7LGb24D9Wct6USacu1kAAoBtbxQatadt6r+2ElShSfPUMVKZWGFKxkiKqt2
7+TK370GGn5az3ws4qeou4Y63C0Pv8Q7YUGLYgdOirV5kfO4VzXkPA0NYGtajnc2
/sCx5re762EVt6n8iRHp/GkIIbpxHSL+0U3HAGrlpr0AAtAAxw0Fo2/SKXJiuEW5
uQ9mVvueF498EmyZ7W9lbHN56b4QIsyXkadJQOJ64+Vt6C/16XNjoci8IyxL7Wk/
oKcYXXZ6p16eS9BSui5X6/uqA9S0HR7lvrcAqzqWiCsU2COqsmQ=
=Q/hN
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: compass-blueprint-plugin
Source-Version: 1.0.0-5
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
compass-blueprint-plugin, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated compass-blueprint-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Oct 2021 19:04:43 +0200
Source: compass-blueprint-plugin
Architecture: source
Version: 1.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Sass team 
Changed-By: Jonas Smedegaard 
Closes: 996032
Changes:
 compass-blueprint-plugin (1.0.0-5) unstable; urgency=medium
 .
   * add patch 1001 to avoid ruby functions;
 closes: bug#996032, thanks to Siri Reiter
   * declare compliance with Debian Policy 4.6.0
   * stop compile obsolete Ruby functions;
 drop obsolete patches 2001 2002;
 stop build-depend on gem2deb ruby ruby-sass
Checksums-Sha1:
 26b5b2cfbd4b0f4260bf731e78d61828635b818e 2075 
compass-blueprint-plugin_1.0.0-5.dsc
 4c38a0d336ef856cabdfbb3c239c972bfd2926e9 4668 
compass-blueprint-plugin_1.0.0-5.debian.tar.xz
 bb531e6fb86018c57098fc5e3c44b46bf243f86b 5769 
compass-blueprint-plugin_1.0.0-5_amd64.buildinfo
Checksums-Sha256:
 50dbd55a6edc309acda1dd69892f2392fd37c984ebe9b18f6f94b0b3e7a2f0ee 2075 
compass-blueprint-plugin_1.0.0-5.dsc
 22916194fffe6d0a5731f732c1a26059639e5debcd27295cb39012ca25c1d6db 4668 
compass-blueprint-plugin_1.0.0-5.debian.tar.xz
 6e2f16865490b56b8826f0580f9474633e3bd800f9ad936cd5253e53eec00199 5769 
compass-blueprint-plugin_1.0.0-5_amd64.buildinfo
Files:
 a87337fecdc1aa2dbca1b0175ab0fd63 2075 web optional 
compass-blueprint-plugin_1.0.0-5.dsc
 595478444a32a3df79c874f4983d3ff7 4668 web optional 

Processed: tagging 994276

[Debian Bug Tracking System]

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

> tags 994276 + ftbfs
Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

[Spencer Olson]

On Sun, Oct 10, 2021, 10:38 Timo Aaltonen  wrote:

> On 10.10.2021 18.41, Spencer Olson wrote:
> > Did some more investigation.  I downloaded the packages that are being
> > used on centos stream 8.  First I tried my test code with their version
> > of libssl3.so preloaded:  it failed in the same way as all the others
> > failed--not surprisingly since its version is much later than the 3.39
> > version where this changed.
> >
> > Then, I downloaded and took a look at "dogtag-submit" from the CentOS
> > Stream 8 (RedHat) certmonger package.  As far as I can tell, their
> > version of "dogtag-submit" is *not* linked against libcurl-nss.so at all
> > like the version on debian sid.  Instead, all their certmonger helper
> > programs are linked against the OpenSSL version (libcurl.so.4).
> >
> > So, I think that we should just link these against the openssl version,
> > as the RedHat packages do and get things to work again.
>
> Hmm, thanks.. indeed certmonger is still built against libcurl4-nss-dev,
> I've changed it to openssl now and see how it goes against gitlab CI..
>

Maybe the CI will finish before I can get back to my testing.


> > This raises two other issues:
> > - is there truly a bug in the ssl portion of the nss library?  If so,
> > this should probably be brought to the attention.
> > - perhaps the libcurl package ought to be reconfigured such that one can
> > install the dev packages simultaneously.  Right now, libcurl-nss also
> > makes a symlink "libcurl.so" that makes it conflict with the
> > libcurl-openssl package to which the "libcurl.so.x.x" lib belongs to.  I
> > think that the libcurl-gnutls package might do the same thing.
> >
> > My next step will be do rebuild freeipa and certmonger with the
> > libcurl-openssl-dev package in place instead of the libcurl-nss-dev and
> > then try reinstalling.
>
> No need to rebuild freeipa.
>

Yep, you are right.  I thought I had seen that freeipa had installed some
executables with linkage to libcurl-nss in /use/lib/certmonger, but i was
mistaken.

Bug#996032: compass-blueprint-plugin: contains ruby functions

[Jonas Smedegaard]

Package: compass-blueprint-plugin
Version: 1.0.0-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Blueprint stylesheets contain functions implemented in Ruby and
only loaded when used together with Compass.

Compass is dead upstream, and dropped from Debian.

These stylesheets are still useful and valuable with contemporary
Sass implementations if those few functions are re-implemented:

This:

  #{enumerate(".pull", 1, $blueprint-grid-columns)} { ... }

can be replaced by the combination of this once:

  %pull-base {

and this for each use:

  @extend %pull-base;

when used only at one place, which is the case for these stylesheets.



This:

  #{headers(all)} { ... }

can be replaced by this:

  h1, h2, h3, h4, h5, h6 { ... }


This:

  #{elements-of-type(html5-block)} { ... }

can be replaced by this:

  article, aside, details, figcaption, figure, footer, header, hgroup, main, 
menu, nav, section, summary { ... }


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFjGUQACgkQLHwxRsGg
ASE3tRAAmgKWZodOn8pGvlDZtWCIT7/29/oLs9NST3FIoWTJDg5tcvZF3u991RWg
UR+vkhI4mIqOhN/Eg4jpM38dghf6G1PxabQIrkKkC5CnaeAI3lojp+33Y7drBU1F
1wdAs30vtYWu6/yfBYXoMDY0JbFFeskvTrxcjBwVVmAbTEAHVHKpfvplyuKZZNjc
gcdS+LwCJ85DOoYH7jydsi/ybFMxOBBOhb/+5rgJbpL1oJfvpYx4bwEYRRv4PVl6
Cr2xp31bwqKD2BCTCxlmlmQK5WrbOqnOh34s+DRjLBGp2txcwMw13otcV9dswW4s
PBIavvqbS7IswevMyWgCkpS8bOBh5SES6wNzUI/rk/oMOS8p3z0yFKcgb4Xu06Rg
6FuCr7LGb24D9Wct6USacu1kAAoBtbxQatadt6r+2ElShSfPUMVKZWGFKxkiKqt2
7+TK370GGn5az3ws4qeou4Y63C0Pv8Q7YUGLYgdOirV5kfO4VzXkPA0NYGtajnc2
/sCx5re762EVt6n8iRHp/GkIIbpxHSL+0U3HAGrlpr0AAtAAxw0Fo2/SKXJiuEW5
uQ9mVvueF498EmyZ7W9lbHN56b4QIsyXkadJQOJ64+Vt6C/16XNjoci8IyxL7Wk/
oKcYXXZ6p16eS9BSui5X6/uqA9S0HR7lvrcAqzqWiCsU2COqsmQ=
=Q/hN
-END PGP SIGNATURE-

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

[Timo Aaltonen]

On 10.10.2021 18.41, Spencer Olson wrote:
Did some more investigation.  I downloaded the packages that are being 
used on centos stream 8.  First I tried my test code with their version 
of libssl3.so preloaded:  it failed in the same way as all the others 
failed--not surprisingly since its version is much later than the 3.39 
version where this changed.


Then, I downloaded and took a look at "dogtag-submit" from the CentOS 
Stream 8 (RedHat) certmonger package.  As far as I can tell, their 
version of "dogtag-submit" is *not* linked against libcurl-nss.so at all 
like the version on debian sid.  Instead, all their certmonger helper 
programs are linked against the OpenSSL version (libcurl.so.4).


So, I think that we should just link these against the openssl version, 
as the RedHat packages do and get things to work again.


Hmm, thanks.. indeed certmonger is still built against libcurl4-nss-dev, 
I've changed it to openssl now and see how it goes against gitlab CI..



This raises two other issues:
- is there truly a bug in the ssl portion of the nss library?  If so, 
this should probably be brought to the attention.
- perhaps the libcurl package ought to be reconfigured such that one can 
install the dev packages simultaneously.  Right now, libcurl-nss also 
makes a symlink "libcurl.so" that makes it conflict with the 
libcurl-openssl package to which the "libcurl.so.x.x" lib belongs to.  I 
think that the libcurl-gnutls package might do the same thing.


My next step will be do rebuild freeipa and certmonger with the 
libcurl-openssl-dev package in place instead of the libcurl-nss-dev and 
then try reinstalling.


No need to rebuild freeipa.


--
t

Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Ondrej Zary]

Haven't found this exact problem. This seems to be closest but the error 
messages are different: https://jira.mariadb.org/browse/MDEV-25981

I'm going to copy the datadir to another machine and debug it further.

On Sunday 10 October 2021 16:55:45 Otto Kekäläinen wrote:
> Hello!
>
> Thanks for reporting. Could you please check if this has been reported
> upstream at jira.mariadb.org?
>
> There isn't much we can do about InnoDB internals in Debian packaging.


-- 
Ondrej Zary

Bug#995999: FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks

[Martina Ferrari]

The GH issue you linked seems to be fixed upstream already with this 
patch: https://github.com/prometheus/prometheus/pull/8538/files


On 09/10/2021 19:34, Shengjing Zhu wrote:

Package: prometheus
Version: 2.24.1+ds-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

Hi,

When rebuild packages, I find it FTBFS.

=== RUN   TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks
--- FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks (0.05s)
panic: runtime error: slice bounds out of range [:104326] with capacity 104293 
[recovered]
panic: runtime error: slice bounds out of range [:104326] with capacity 
104293

goroutine 7 [running]:
testing.tRunner.func1.2(0x60da60, 0xc0005f8030)
/usr/lib/go-1.16/src/testing/testing.go:1143 +0x332
testing.tRunner.func1(0xc01e00)
/usr/lib/go-1.16/src/testing/testing.go:1146 +0x4b6
panic(0x60da60, 0xc0005f8030)
/usr/lib/go-1.16/src/runtime/panic.go:965 +0x1b9
github.com/prometheus/prometheus/tsdb/chunks.TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks(0xc01e00)

/build/1st/prometheus-2.24.1+ds/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:122
 +0xc9c
testing.tRunner(0xc01e00, 0x637600)
/usr/lib/go-1.16/src/testing/testing.go:1193 +0xef
created by testing.(*T).Run
/usr/lib/go-1.16/src/testing/testing.go:1238 +0x2b3
FAILgithub.com/prometheus/prometheus/tsdb/chunks0.116s


It also FTBFS on tests.reproducible-builds.org, ci.debian.net

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/prometheus/15535224/log.gz



--
Martina Ferrari (Tina)

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

[Spencer Olson]

Did some more investigation.  I downloaded the packages that are being used
on centos stream 8.  First I tried my test code with their version of
libssl3.so preloaded:  it failed in the same way as all the others
failed--not surprisingly since its version is much later than the 3.39
version where this changed.

Then, I downloaded and took a look at "dogtag-submit" from the CentOS
Stream 8 (RedHat) certmonger package.  As far as I can tell, their version
of "dogtag-submit" is *not* linked against libcurl-nss.so at all like the
version on debian sid.  Instead, all their certmonger helper programs are
linked against the OpenSSL version (libcurl.so.4).

So, I think that we should just link these against the openssl version, as
the RedHat packages do and get things to work again.

This raises two other issues:
- is there truly a bug in the ssl portion of the nss library?  If so, this
should probably be brought to the attention.
- perhaps the libcurl package ought to be reconfigured such that one can
install the dev packages simultaneously.  Right now, libcurl-nss also makes
a symlink "libcurl.so" that makes it conflict with the libcurl-openssl
package to which the "libcurl.so.x.x" lib belongs to.  I think that the
libcurl-gnutls package might do the same thing.

My next step will be do rebuild freeipa and certmonger with the
libcurl-openssl-dev package in place instead of the libcurl-nss-dev and
then try reinstalling.


On Sat, Oct 9, 2021 at 9:59 PM Spencer Olson  wrote:
>
> Cloned nss repo and did a git bisect:  the first commit that causes
> problems is at the upstream merge of 3.39 (upstream/3.39).
>
> From a very brief perusal of the upstream changes, I see there are
> some edits with respect to TLS1.3--perhaps this is the reason for our
> problems--I haven't yet looked hard at all the upstream changes (or
> tried to bisect the upstream repo yet).
>
> On Sat, Oct 9, 2021 at 12:05 PM Spencer Olson  wrote:
> >
> > Since it doesn't look like any progress has been made on this, I've
> > started to work through some debugging.
> >
> > Right now, it looks like the problem is probably actually due to a
> > change in libnss3.  In fact, the problem appears to be specifically in
> > libssl3.so from the libnss3 package.
> >
> > The problem:
> >   * certmonger has a hard time finishing the certificate requests
> > because it can't seem to authenticate to the dogtag PKI server.
> >
> > Observations:
> >  * When certmonger attempts to request a signed certificate for the
> > renewal agent, it temporarily explicitly uses the ipa-ca-agent
> > certificate which has been temporarily extracted from the
> > /root/ca-agent.p12 storage.
> >  * dogtag-submit attempts to use the CURL library to submit the
> > request, subsequently approve the request, and then poll for its
> > finish.
> >  * The initial request does not use/require an encrypted channel, but
> > the approval and subsequent queries do.
> >  * These attempts to authenticate over this encrypted channel using
> > the client certificate are rejected.
> >
> > Hacks & tests:
> >  * By creating a very small c-program that does the same CURL commands
> > as dogtag-submit from the certmonger package, this same authorization
> > denied can be seen.
> >  * By simply replacing the libssl3.so library, using either LD_PRELOAD
> > or LD_LIBRARY_PATH, from a prior version, the requests succeed.  As of
> > now, I've tried only one other version of libssl3.so (libnss3 3.35
> > from ubuntu 18.04).
> >  * Also, instead of linking against libcurl-nss and manualy replacing
> > the libssl3.so library, success can be found by linking to
> > libcurl-gnutls or libcurl-openssl
> >
> > I suspect that a compile option in libnss3 has to be changed in order
> > for this to work again.
> >
> > Still todo:
> >  * I haven't fully discovered which part/option from libnss3 might have
changed.
> >  * I haven't yet successfully had libnss3 emit much
> > debugging--probably have to recompile with DEBUG=1.

Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Otto Kekäläinen]

Hello!

Thanks for reporting. Could you please check if this has been reported
upstream at jira.mariadb.org?

There isn't much we can do about InnoDB internals in Debian packaging.

Processed: tagging 885563

[Debian Bug Tracking System]

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

> tags 885563 - bullseye buster
Bug #885563 [src:vte] vte: Do not release with bookworm
Removed tag(s) bullseye and buster.
> thanks
Stopping processing here.

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

Bug#996005: ca-certificates: fails upgrading when no new certs selected

[Michael Shuler]

On 10/9/21 6:40 PM, Christoph Anton Mitterer wrote:

It seems that when not selecting any of the new certs on upgrade, the package
install fails:
Setting up ca-certificates (20211004) ...
Updating certificates in /etc/ssl/certs...
chmod: cannot access '/etc/ssl/certs/ca-certificates.crt.new': No such file or 
directory
dpkg: error processing package ca-certificates (--configure):
  installed ca-certificates package post-installation script subprocess 
returned error exit status 1


Good find - patch attached to check if file exists before chmod & mv.

--
Kind regards,
Michael
diff --git a/debian/changelog b/debian/changelog
index 2a146c2..7b1e0bc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ca-certificates (20211010) UNRELEASED; urgency=medium
+
+  [ Michael Shuler ]
+  * Fix error on install when TEMPBUNDLE missing. Closes: #996005
+
+ -- Michael Shuler   Sun, 10 Oct 2021 09:10:28 -0500
+
 ca-certificates (20211004) unstable; urgency=low
 
   [ Debian Janitor ]
diff --git a/sbin/update-ca-certificates b/sbin/update-ca-certificates
index 789867f..0265205 100755
--- a/sbin/update-ca-certificates
+++ b/sbin/update-ca-certificates
@@ -187,8 +187,12 @@ then
   fi
 fi
 
-chmod 0644 "$TEMPBUNDLE"
-mv -f "$TEMPBUNDLE" "$CERTBUNDLE"
+# chmod and mv only if TEMPBUNDLE exists or install may fail, #996005
+if [ -f "$TEMPBUNDLE" ]
+then
+  chmod 0644 "$TEMPBUNDLE"
+  mv -f "$TEMPBUNDLE" "$CERTBUNDLE"
+fi
 # Restore proper SELinux label after moving the file
 [ -x /sbin/restorecon ] && /sbin/restorecon "$CERTBUNDLE" >/dev/null 2>&1
 

Processed: tagging 993065

[Debian Bug Tracking System]

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

> tags 993065 + bookworm sid
Bug #993065 [src:gnome-shell-extension-xrdesktop] 
gnome-shell-extension-xrdesktop: Please update for gnome-shell 40
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Ondrej Zary]

Package: mariadb-server
Version: 1:10.3.31-0+deb10u1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,
upgrading mariadb-server from 1:10.3.29-0+deb10u1 to 1:10.3.31-0+deb10u1 failed
because mariadb failed to start. /var/log/mysql/error.log:

2021-10-10 15:12:49 0 [ERROR] InnoDB: corrupted TRX_NO 10002001c6986c3
2021-10-10 15:12:49 0 [ERROR] InnoDB: Plugin initialization aborted with error 
Data structure corruption
2021-10-10 15:12:50 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-10-10 15:12:50 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE 
failed.
2021-10-10 15:12:50 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-10-10 15:12:50 0 [ERROR] Aborting

Fortunately, it works after downgrading back to 10.3.29.
Data does not seem to be corrupted.

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages mariadb-server depends on:
ii  mariadb-server-10.3  1:10.3.31-0+deb10u1

mariadb-server recommends no packages.

mariadb-server suggests no packages.

-- debconf-show failed

Bug#995851: marked as done (FTBFS: tests fail with new pydantic)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 13:04:25 +
with message-id 
and subject line Bug#995851: fixed in qcelemental 0.23.0+dfsg-1
has caused the Debian Bug report #995851,
regarding FTBFS: tests fail with new pydantic
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
995851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qcelemental
Severity: important
X-Debbugs-Cc: mo...@debian.org

Hello,
a recent upload of pydantic made the autopkgtests fail for qcelemental.

The latest upstream release, 0.23.0, supports pydanting/1.8.2:

https://github.com/MolSSI/QCElemental/blob/master/setup.py#L34

please package the last upstream release.

Regards,
Sandro


-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: qcelemental
Source-Version: 0.23.0+dfsg-1
Done: Michael Banck 

We believe that the bug you reported is fixed in the latest version of
qcelemental, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated qcelemental package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Oct 2021 14:48:48 +0200
Source: qcelemental
Architecture: source
Version: 0.23.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Closes: 995851
Changes:
 qcelemental (0.23.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #995851).
   * debian/patches/skip_web_using_tests.patch: Refreshed.
Checksums-Sha1:
 8ec13f1e5223ef2386ec3c98c89cbbf4a093e4c2 2215 qcelemental_0.23.0+dfsg-1.dsc
 75ae4f566b5975ca6adecb1415282591b5f216f5 433148 
qcelemental_0.23.0+dfsg.orig.tar.xz
 d0f6d48bc7bfe9a0821295579f3f061862ad5acc 3192 
qcelemental_0.23.0+dfsg-1.debian.tar.xz
 8edee55e1a71c76b9279f13cc59a378388c70dd6 6803 
qcelemental_0.23.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 7273e2b2e4bfc8915e57f2ae932cd668941379db18fd3d13a5268b47645c54d4 2215 
qcelemental_0.23.0+dfsg-1.dsc
 c1745b8939eba8a0c732726b7474c18cd540385edd826b26df802f2403b7041c 433148 
qcelemental_0.23.0+dfsg.orig.tar.xz
 9fe993293a2372bcda0cbfabdd164366b7b05498f095fe095afb0e58e64bf48e 3192 
qcelemental_0.23.0+dfsg-1.debian.tar.xz
 d349a2b6d61422a56511df83fed462b4ef5ddb29425a93c9979e13156090b539 6803 
qcelemental_0.23.0+dfsg-1_source.buildinfo
Files:
 7fe32af71a27d2800e876c361f2690f9 2215 python optional 
qcelemental_0.23.0+dfsg-1.dsc
 570763b2d4aecc9f3c01c530fcc330a7 433148 python optional 
qcelemental_0.23.0+dfsg.orig.tar.xz
 21580bbf41c139e87e7a00961eb73f2f 3192 python optional 
qcelemental_0.23.0+dfsg-1.debian.tar.xz
 2dde25104e3cc9f9b61ef92450644052 6803 python optional 
qcelemental_0.23.0+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAmFi4TcACgkQ3GhqJ7Q0
gbBUaA//eE1JTguOwU90ni7QW7sNiKhq7gMnOfIN/z5EAp4vnPWwEAcRvWGE2XsV
rsxmJCGWoTJn+VEvAjgdhE7eNoEXU+B/o+LbKMYg1H1MGu6S0/jNIirjZTDly6SA
N3rmJ5yoXqgJbhrfrEA8dimYf4QmS70od1UBvb0xIrVXEnJYJwQZUBlvL+XMkO3o
MMHL9c6BLzRZPFcaNHnKE3Eufb/y8Jy4W7xXD3Vn75yQEU8pvXTnGRRM76m0IgO4
Z2x2TgHdv8dsBkcLdFDxSvwkNB/41GcryfU+ngnJexX0jNJK4wlOzSt/4AYdL3ZJ
aY9DMUmHL0mn92X9rFv1xEpAvqtWTA8TbP+Fve+pDfLeiKuyYT9Y+mVVQx7VFZqM
GyFrYWDvH6t7h/EEZKPP19lRgZ4eI7DoM7DsBHgmnzOiFxV/0Xvka1BURWq5jH40
JtS0lD7QeDvY6N8UaGsaQIGpMiQAjMixRaJFyRtURheSAeQ08dm+ACCaGD296lhR
InuhwJtee0obxnSMk6wO2Y3isH595Krk/ar2my0a/KQRD6tgjvYFO0VIPXuDa6dv
HFkcHU/9YtSudQ69TW0J3ybP3E7qdsCl1cLd0SmBkHyHtjMXkM7oaRq8UKKgeihE
WpySNnti9boNMaq4eObXHkty46+6q1E1uNxx7Pbwb7pjgK2UO74=
=vHC/
-END PGP SIGNATURE End Message ---

Processed: tagging 993093

[Debian Bug Tracking System]

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

> tags 993093 + pending
Bug #993093 {Done: Paul Gevers } 
[src:icingaweb2-module-director] src:icingaweb2-module-director: fails to 
migrate to testing for too long
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#976530 marked as pending in dolphin-emu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976530 [src:dolphin-emu] dolphin-emu: FTBFS: tests failed
Added tag(s) pending.

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

Bug#976530: marked as pending in dolphin-emu

[emorrp1]

Control: tag -1 pending

Hello,

Bug #976530 in dolphin-emu reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/dolphin-emu/-/commit/5c2aa692bc09447eed35e2455a0ab91301f34632


backport MathUtil::SaturatingCast

Thanks: Jos Juice for identifying the PR
Closes: #976530


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976530

Bug#996012: marked as done (d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: Unmatched ( or \()

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2021 06:48:44 +
with message-id 
and subject line Bug#996012: fixed in d-shlibs 0.102
has caused the Debian Bug report #996012,
regarding d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: 
Unmatched ( or \(
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
996012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: d-shlibs
Version: 0.101
Severity: serious
Tags: ftbfs
Control: affects -1 + src:libzstd
User: helm...@debian.org
Usertags: rebootstrap

libzstd fails to build from source in unstable on amd64. A build now
ends with:

|debian/rules override_dh_install
| make[1]: Entering directory '/<>'
| # Call d-shlibmove to comply with library packaging guide
| d-shlibmove --commit \
| --multiarch \
| --devunversioned \
| --exclude-la \
| --movedev "debian/tmp/usr/include/*" usr/include \
| --movedev "debian/tmp/usr/lib/pkgconfig/*" 
usr/lib/x86_64-linux-gnu/pkgconfig \
| debian/tmp/usr/lib/lib*.so
| Library package automatic movement utility
| sed: -e expression #89, char 81: Unmatched ( or \(
| make[1]: *** [debian/rules:34: override_dh_install] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:16: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

I think it is fairly safe to bet that this is caused by the d-shlibs
upload. What puzzles me a bit is that build time testing didn't catch
this. And that autopkgtests for d-shlibs aren't failing. Can you also
look into why testing didn't prevent this?

A workaround or quick solution would be appreciated as it breaks all
jobs at https://jenkins.debian.net/view/rebootstrap/.

Helmut
--- End Message ---
--- Begin Message ---
Source: d-shlibs
Source-Version: 0.102
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
d-shlibs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated d-shlibs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Oct 2021 08:36:48 +0200
Source: d-shlibs
Architecture: source
Version: 0.102
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 995972 996012
Changes:
 d-shlibs (0.102) unstable; urgency=medium
 .
   * fix typos in regex;
 closes: bug#996012, #995972,
 thanks to Helmut Grohne and Laurent Bigonville
   * convert custom tests into autopkgtest
Checksums-Sha1:
 c740e78fbdf7e674ca3faeca24ded5e48cd6b77c 1744 d-shlibs_0.102.dsc
 9eb6531176f143b7f6d167d3840209747295d639 25156 d-shlibs_0.102.tar.xz
 c06b4b374963b02e4e5e1caf49e62be31ade10a4 5661 d-shlibs_0.102_amd64.buildinfo
Checksums-Sha256:
 9ed0e1ad5ded2e313ee4d513cc078914f141a6cbd6e50ffe3ceca066149df11d 1744 
d-shlibs_0.102.dsc
 4331e9a18c623dd8c9052cf2a985dbb7b48786a1770ca8ba0f7db130deb65bd4 25156 
d-shlibs_0.102.tar.xz
 b26d513e9b07dbecf7d0a15b531d11a55044cadf7bf83d48e74b3c626e2a4bff 5661 
d-shlibs_0.102_amd64.buildinfo
Files:
 29bd9bcd323abfad4f732f049850cd41 1744 utils optional d-shlibs_0.102.dsc
 d4f28126d208d6b68a4e110de7be0c0b 25156 utils optional d-shlibs_0.102.tar.xz
 657ccc828ec54a2fd83b910b802d5fe1 5661 utils optional 
d-shlibs_0.102_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFiimEACgkQLHwxRsGg
ASGDVBAAhZtcAlAEua/asLLUliZu1Bxp3iE94oY0PPxEdQW5j1r42MdZUmr8REjq
WQNx3VI/aljfeKJXVKtAF0R8oASYi20DJeNi+KW8dGghiIuLsUSJiUnA66jvVjN0
7IYrnL8PX8AQBfhS34q+LG3F1ZvCWPBbVPh4r5G2Bb4BW/zLn2zYqFpuUV2YZjFM
2lbXzpDvIGja42vHu4Gu0+QkfsHQ2ZnEDPPvqiYwnLHeWII60wvfE8SnrnmASkYq
YSMeXupnmUMuzMB0kxcxOtVrvfbDXRMrRg002DrECiZI5QnbpgjEY93xSHGz/w6F
ck29urGSw/Ia1BTJ0dHMN8GI0SEBmB3CNvheMfk8B/i3VCJ9WbJBSOOshEYXz/mw
5ahU7sXvSuJ8DPinxLBSgCvFAmhMA2ULeQMtoQJ+GSBQ+A56n3djDJv7VA373iQh