Bug#1018753: abiword: FTBFS on several platforms (test timeout)

[Jonas Smedegaard]

Quoting Jeremy Bicha (2022-09-07 22:21:57)
> I am uploading a NMU now with high urgency to allow the ongoing
> evolution-data-server transition to proceed smoothly.

Thanks you both, Eric and Jeremy,

 - Jonas

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

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

signature.asc
Description: signature

Bug#1017271: marked as done (FLTK-Targets{,-none}.cmake lost contents during the latest binNMU)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2022 03:33:52 +
with message-id 
and subject line Bug#1017271: fixed in fltk1.3 1.3.8-5
has caused the Debian Bug report #1017271,
regarding FLTK-Targets{,-none}.cmake lost contents during the latest binNMU
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.)


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> /<>/src/Plugin/ZynAddSubFX 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/src/Plugin/ZynAddSubFX 
> /<>/obj-x86_64-linux-gnu/src/Plugin/ZynAddSubFX/CMakeFiles/ZynAddSubFX_lv2_ui.dir/DependInfo.cmake
>  --color=
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: *** No rule to make target 'src/UI/fluid', needed by 
> 'src/UI/VirKeyboard.h'.  Stop.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> make[2]: *** [CMakeFiles/Makefile2:2301: 
> src/UI/CMakeFiles/zynaddsubfx_gui.dir/all] Error 2


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

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: fltk1.3
Source-Version: 1.3.8-5
Done: Aaron M. Ucko 

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated fltk1.3 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: Wed, 07 Sep 2022 23:16:48 -0400
Source: fltk1.3
Architecture: source
Version: 1.3.8-5
Distribution: unstable
Urgency: medium
Maintainer: Aaron M. Ucko 
Changed-By: Aaron M. Ucko 
Closes: 1015406 1017271 1017421
Changes:
 fltk1.3 (1.3.8-5) unstable; urgency=medium
 .
   * debian/fix-fltk-targets: Report command lines, which are now dynamic.
 (See debian/rules changes below.)
   * debian/libfltk*.symbols*: Accommodate LTO builds, which drop some
 symbols (none of which anything in the archive uses AFAICT).
 Specifically, pull out libfltk*.symbols.no-lto files and include them
 with the "(optional)" tag.  (Closes: #1015406.)
   * debian/**lintian-overrides: Add wildcards to accommodate pointed hints.
   * debian/rules:
 - Unhardcode path to stock FLTK-Targets(-none).cmake.
   Per https://gitlab.kitware.com/cmake/cmake/-/issues/23883,
   CMakeTmp/CMakeFiles/Export's subdirectory names are hexadecimal MD5
   hash values as of CMake 3.24; automatic detection allows backports
   to keep working and accommodates possible future layout changes.
   (Closes: #1017271.)
 - Inventory the final FLTK-Targets(-none).cmake files' add_* calls,
   automatically catching blatant problems and making some potential
   others immediately visible in build logs.
   * documentation/Makefile: Use English ("C") month names for PDF date.
 (Closes: #1017421.)
   * Standa

Bug#1018786: marked as done (numba: autopkgtest needs update for new version of llvmlite: The module `llvmlite.llvmpy` is deprecated)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2022 02:34:13 +
with message-id 
and subject line Bug#1018786: fixed in numba 0.56.2+dfsg-1
has caused the Debian Bug report #1018786,
regarding numba: autopkgtest needs update for new version of llvmlite: The 
module `llvmlite.llvmpy` is deprecated
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.)


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

Source: numba
Version: 0.55.2+dfsg-1
Severity: serious
X-Debbugs-CC: llvml...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:llvmlite

Dear maintainer(s),

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


   passfail
llvmlite   from testing0.39.0-1
numba  from testing0.55.2+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of llvmlite to 
testing [1]. Of course, llvmlite shouldn't just break your autopkgtest 
(or even worse, your package), but it seems to me that the change in 
llvmlite 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 llvmlite 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=llvmlite

https://ci.debian.net/data/autopkgtest/testing/amd64/n/numba/25502711/log.gz

==
FAIL: test_no_accidental_warnings (numba.tests.test_import.TestNumbaImport)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numba/tests/test_import.py", 
line 103, in test_no_accidental_warnings

run_in_subprocess(code, flags)
  File "/usr/lib/python3/dist-packages/numba/tests/support.py", line 
1014, in run_in_subprocess

raise AssertionError(msg % (popen.returncode, err.decode()))
AssertionError: process failed with code 1: stderr follows
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/numba/__init__.py", line 38, in 

from numba.core.decorators import (cfunc, generated_jit, jit, njit, 
stencil,
  File "/usr/lib/python3/dist-packages/numba/core/decorators.py", line 
12, in 

from numba.stencils.stencil import stencil
  File "/usr/lib/python3/dist-packages/numba/stencils/stencil.py", line 
11, in 
from numba.core import types, typing, utils, ir, config, ir_utils, 
registry
  File "/usr/lib/python3/dist-packages/numba/core/ir_utils.py", line 
16, in 

from numba.core.extending import _Intrinsic
  File "/usr/lib/python3/dist-packages/numba/core/extending.py", line 
19, in 
from numba.core.pythonapi import box, unbox, reflect, NativeValue 
# noqa: F401
  File "/usr/lib/python3/dist-packages/numba/core/pythonapi.py", line 
8, in 

from llvmlite.llvmpy.core import Type, Constant
  File "/usr/lib/python3/dist-packages/llvmlite/llvmpy/__init__.py", 
line 3, in 

warnings.warn(
UserWarning: The module `llvmlite.llvmpy` is deprecated and will be 
removed in the future.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: numba
Source-Version: 0.56.2+dfsg-1
Done: Diane Trout 

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated numba package)

(This message was generated auto

Bug#1011676: marked as done (ruby-ntlm: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: OpenSSL::Digest::MD4.digest pwd)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2022 01:33:50 +
with message-id 
and subject line Bug#1011676: fixed in ruby-ntlm 0.6.3-2
has caused the Debian Bug report #1011676,
regarding ruby-ntlm: FTBFS: ERROR: Test "ruby3.0" failed:   Failure/Error: 
OpenSSL::Digest::MD4.digest pwd
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.)


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

Hi,

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


Relevant part (hopefully):
>   Failure/Error: OpenSSL::Digest::MD4.digest pwd
> 
>   OpenSSL::Digest::DigestError:
> Digest initialization failed: initialization error
>   # ./lib/net/ntlm.rb:149:in `ntlm_hash'
>   # ./spec/lib/net/ntlm_spec.rb:119:in `block (2 levels) in  (required)>'
> 
> Finished in 0.29403 seconds (files took 0.31806 seconds to load)
> 741 examples, 19 failures
> 
> Failed examples:
> 
> rspec ./spec/lib/net/ntlm/client/session_spec.rb:14 # 
> Net::NTLM::Client::Session#sign_message signs a message and when KEY_EXCHANGE 
> is true
> rspec ./spec/lib/net/ntlm/client/session_spec.rb:27 # 
> Net::NTLM::Client::Session#verify_signature verifies a message signature
> rspec ./spec/lib/net/ntlm/client/session_spec.rb:39 # 
> Net::NTLM::Client::Session#seal_message should seal the message
> rspec ./spec/lib/net/ntlm/client/session_spec.rb:47 # 
> Net::NTLM::Client::Session#unseal_message should unseal the message
> rspec ./spec/lib/net/ntlm/client/session_spec.rb:55 # 
> Net::NTLM::Client::Session#exported_session_key returns a random 16-byte key 
> when negotiate_key_exchange? is true
> rspec ./spec/lib/net/ntlm/message/type2_spec.rb:64 # 
> Net::NTLM::Message::Type2 should generate a type 3 response
> rspec ./spec/lib/net/ntlm/message/type2_spec.rb:81 # 
> Net::NTLM::Message::Type2 should upcase domain when provided
> rspec ./spec/lib/net/ntlm/message/type3_spec.rb:97 # 
> Net::NTLM::Message::Type3.parse with NTLMv2 data #blank_password? should be 
> true
> rspec ./spec/lib/net/ntlm/message/type3_spec.rb:154 # 
> Net::NTLM::Message::Type3.parse NTLM2 Session Response Authentication; NTLM2 
> Signing and Sealing Using the 128-bit NTLM2 Session Response User Session Key 
> With Key Exchange Negotiated #password? should be true for "test1234"
> rspec ./spec/lib/net/ntlm/message/type3_spec.rb:159 # 
> Net::NTLM::Message::Type3.parse NTLM2 Session Response Authentication; NTLM2 
> Signing and Sealing Using the 128-bit NTLM2 Session Response User Session Key 
> With Key Exchange Negotiated #blank_password? should be false
> rspec ./spec/lib/net/ntlm_spec.rb:36 # Net::NTLM should encrypt the string 
> with DES for each key supplied
> rspec ./spec/lib/net/ntlm_spec.rb:42 # Net::NTLM should generate an lm_hash
> rspec ./spec/lib/net/ntlm_spec.rb:46 # Net::NTLM should generate an ntlm_hash
> rspec ./spec/lib/net/ntlm_spec.rb:50 # Net::NTLM should generate an 
> ntlmv2_hash
> rspec ./spec/lib/net/ntlm_spec.rb:62 # Net::NTLM should generate an 
> lm_response
> rspec ./spec/lib/net/ntlm_spec.rb:71 # Net::NTLM should generate an 
> ntlm_response
> rspec ./spec/lib/net/ntlm_spec.rb:81 # Net::NTLM should generate a 
> lvm2_response
> rspec ./spec/lib/net/ntlm_spec.rb:91 # Net::NTLM should generate a 
> ntlmv2_response
> rspec ./spec/lib/net/ntlm_spec.rb:116 # Net::NTLM should generate a 
> ntlm2_session
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*.rb --format documentation failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/ruby-ntlm_0.6.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

If you reassign this bug to another package, please marking it as 'aff

Processed: Re: Bug#1010901: missing license information

[Debian Bug Tracking System]

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

> notfound 1010901 3.42.6-1
Bug #1010901 {Done: Paul Gevers } [gpaste] missing license 
information
No longer marked as found in versions gpaste/3.42.6-1.
>
End of message, stopping processing here.

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

Bug#1019365: qml-module-lomiri-settings-fingerprint : Depends: qml-module-biometryd but it is not installable

[Steve Langasek]

Package: qml-module-lomiri-settings-fingerprint
Version: 1.0.0-3
Severity: grave
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

The qml-module-lomiri-settings-fingerprint package is uninstallable because
it depends on qml-module-biometryd which does not exist in unstable, nor has
it been uploaded to the NEW queue.

Please upload qml-module-biometryd, or drop the dependency, or drop the
binary package.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Processed: notfound 1018930 in 0.10.1-2

[Debian Bug Tracking System]

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

> notfound 1018930 0.10.1-2
Bug #1018930 {Done: Salvatore Bonaccorso } [src:pcs] pcs: 
CVE-2022-2735: Obtaining an authentication token for hacluster user leads to 
privilege escalation
Ignoring request to alter found versions of bug #1018930 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1018198: marked as done (modemmanager: FTBFS test failing with common_test_ccwa_response: assertion failed: (result))

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 22:22:12 +
with message-id 
and subject line Bug#1018198: fixed in modemmanager 1.18.10-2
has caused the Debian Bug report #1018198,
regarding modemmanager: FTBFS test failing with common_test_ccwa_response: 
assertion failed: (result)
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.)


-- 
1018198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: modemmanager
Version: 1.18.10-1
Severity: serious
Tags: upstream patch bookworm sid ftbfs
Justification: FTBFS
Forwarded: 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/870
X-Debbugs-Cc: he...@debian.org

Hey,

when I try a recompiliation of ModemManager, the tests are failing with:

  /test_ccwa_response:
  **
  ERROR:test-modem-helpers.c:4204:common_test_ccwa_response: assertion
  failed: (result)
  FAIL   
  GTester: last random seed: R02S1c9c8a2a8c689230b60594a14f54dc63
  make[5]: *** [Makefile:889: test-nonrecursive] Terminated
  make[5]: Leaving directory '/<>/src/tests'
  make[4]: *** [Makefile:736: check-am] Error 2
  make[4]: Leaving directory '/<>/src/tests'
  make[3]: *** [Makefile:1991: check-recursive] Error 1
  make[3]: Leaving directory '/<>/src'
  make[2]: *** [Makefile:2142: check] Error 2
  make[2]: Leaving directory '/<>/src'
  make[1]: *** [Makefile:540: check-recursive] Error 1
  make[1]: Leaving directory '/<>'
  dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose"
  VERBOSE=1 returned exit code 2
  make: *** [debian/rules:12: binary] Error 25
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit
  status 2


This bug is also reported upstream
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/601

It seems like the issue is that with new glibc >= 2.73.2 PCRE1 is
replaced with PCRE2. There is also a first patch for it, but this does
not fix this issue completly.

I initally wanted to fix my breakage of my UMTS stick failing 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/621
I will not open a second bug report as the bugfix is don with same MR.

regards,

hefee


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages modemmanager depends on:
ii  libc6  2.34-6
ii  libglib2.0-0   2.73.3-2
ii  libgudev-1.0-0 237-2
ii  libmbim-glib4  1.26.4-1
ii  libmbim-proxy  1.26.4-1
ii  libmm-glib01.18.10-1
ii  libpolkit-gobject-1-0  0.105-33
ii  libqmi-glib5   1.30.8-1
ii  libqmi-proxy   1.30.8-1
ii  libqrtr-glib0  1.2.2-1
ii  libsystemd0251.4-1
ii  policykit-10.105-33

Versions of packages modemmanager recommends:
ii  usb-modeswitch  2.6.1-3+b1

modemmanager suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: modemmanager
Source-Version: 1.18.10-2
Done: Martin 

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

Debian distribution maintenance software
pp.
Martin  (supplier of updated modemmanager 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: Wed, 07 Sep 2022 21:55:00 +
Source: modemmanager
Architecture: source
Version: 1.18.10-2
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Martin 
Closes: 1017794 1018198
Changes:
 modemmanager (1.18.10-2) unstable; urgency=medium
 .
   [ Matteo F.

Bug#1018930: [Debian-ha-maintainers] Bug#1018930: marked as done (pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation)

[Valentin Vidic]

I checked pcs 0.10.1-2 in buster and it turns out it is not vulnerable
to CVE-2022-2735. Separate ruby daemon with a world writable UNIX socket
was introduced later in 0.10.5:

https://salsa.debian.org/ha-team/pcs/-/commits/master/pcsd/pcsd-ruby.service.in

Before that version python code runs ruby commands and they communicate
by sending json responses on stdin/stdout.

https://salsa.debian.org/ha-team/pcs/-/blob/38330deb0d849d6a1945856b24323043f6a7839b/pcs/daemon/ruby_pcsd.py

-- 
Valentin

Bug#1017794: marked as done (modemmanager: corrupted double-linked list after upgrade to glib2.0 2.73.x)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 22:22:12 +
with message-id 
and subject line Bug#1017794: fixed in modemmanager 1.18.10-2
has caused the Debian Bug report #1017794,
regarding modemmanager: corrupted double-linked list after upgrade to glib2.0 
2.73.x
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.)


-- 
1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.72.3-1
Severity: wishlist
Control: block -1 by 1017578

We have one blocker bug to fix before we can upload glib 2.73 to Unstable.

There is also https://bugs.debian.org/1017793 but it's not a blocker
bug for Debian.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: modemmanager
Source-Version: 1.18.10-2
Done: Martin 

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

Debian distribution maintenance software
pp.
Martin  (supplier of updated modemmanager 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: Wed, 07 Sep 2022 21:55:00 +
Source: modemmanager
Architecture: source
Version: 1.18.10-2
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Martin 
Closes: 1017794 1018198
Changes:
 modemmanager (1.18.10-2) unstable; urgency=medium
 .
   [ Matteo F. Vescovi  2022-09-07 ]
   * debian/patches/: patchset updated (Closes: #1017794, #1018198)
 - 0001-Fix_invalid_EXZ_error_parser.patch added
 - 0002-Fix_issue_with_EOL_for_pcre2.patch added
Checksums-Sha1:
 7574d39f70046fa4f21165a45eb5bb8495a7bb51 2937 modemmanager_1.18.10-2.dsc
 a303ac3591a704767641a4b9a7ca99def23ea3d5 29528 
modemmanager_1.18.10-2.debian.tar.xz
 0812d8e910a2f7379013d53d0b75b0ae89b7c376 12508 
modemmanager_1.18.10-2_amd64.buildinfo
Checksums-Sha256:
 b8deae2febdcb5d92fd1a90a6cc1240eef43fedac1b993d3dbd0b39ce97f6e4b 2937 
modemmanager_1.18.10-2.dsc
 91e6d5a405852d027fc5f1bc5d83fabd4e44bbf555f5c29cb7c30635dd105dd0 29528 
modemmanager_1.18.10-2.debian.tar.xz
 7f70807e94d894325f7e73ef33f1cb66fda344c774dc219bf6bcaed1d235e913 12508 
modemmanager_1.18.10-2_amd64.buildinfo
Files:
 46bd5d1af61b2054ad658a029d1f59e5 2937 net optional modemmanager_1.18.10-2.dsc
 d899260da2fa67e37c9a65ff93df0d11 29528 net optional 
modemmanager_1.18.10-2.debian.tar.xz
 d0c5fef8df4f4e9b193c3fb694fb4b9c 12508 net optional 
modemmanager_1.18.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmMZFSkACgkQ4+Chwoa5
Y+oOdw//eDfa3QcSCmApM/rC2zr7gBF+JI6eC3GOuuHY/3pPYdoz0hRy5P9fcs2Z
w0x/nMPU2nTXsHrmifPnwg0m7ZDsEtMcJnoHcVVdaFaEVnAHJnz4iQpUUrmmAXlv
pGCveIZ+EsFJtI964FmNO4Nc5tzSO5ETPqGz6o15gPxEw8uinirYZW4pw9Dth358
pxssaL0iTs4VGDFZ6+p5beK2D3tJKLLJFPKeFvwAGwmjQxpzvLIU85A0beA9xl4T
nUA3WOx+44uea4e2wdhA/uQFgpvQB5RzxrQK2GHLxkwZX9HN6W7QJ6mk+g58pXKA
GzrDBMM1Zt4D+AWr9XPgqUbuK1Wbg4tgjdQAIF2ge16UwRD/HmPqj6a+o7VbSDzN
B9G2T9ofl0rYwJdggSzf3Ms5KyOCgJyB8aP8XPlUUevkqKGPHgCr0fNIbx81WWW3
YOWHabK83Z/ziqs0i3aHCU31UeHjV5CKo23vZioX9NMXspn409IgjPXbe3hIjoMW
/6P6r8AmGhczINrc3CVORlltCRqTOT/CtYtcuAWMUlN85nkK3eRbqo/j1aXU5Nge
KsBxECtoP6X8/vVX924SjSaFBLvzIqeZFpT/c1nUn6GHYq75wahNG0Iosl4AhaU2
QrCZZ7uS/dQ+lsvB3V0Kp4wKM101Isfq8IMYfHtXxKBgAOgBN5M=
=aZHx
-END PGP SIGNATURE End Message ---

Bug#1018731: marked as done (ghex wants to install document-modified-symbolic.svg which is already installed by gnome-text-editor)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 21:50:52 +
with message-id 
and subject line Bug#1018731: fixed in ghex 43~alpha-4
has caused the Debian Bug report #1018731,
regarding ghex wants to install document-modified-symbolic.svg which is already 
installed by gnome-text-editor
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.)


-- 
1018731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghex
Version: 43~alpha-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?
try to install ghex from unstable
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
N/A
   * What was the outcome of this action?
could not be installed
Entpacken von ghex (43~alpha-3) ...
dpkg: Fehler beim Bearbeiten des Archivs
/var/cache/apt/archives/ghex_43~alpha-3
_amd64.deb (--unpack):
 Versuch, »/usr/share/icons/hicolor/scalable/actions/document-modified-
symbolic.
svg« zu überschreiben, welches auch in Paket gnome-text-editor 43~alpha1-1 ist
dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Datenübergabe
unte
rbrochen (broken pipe)) getötet
Fehler traten auf beim Bearbeiten von:
 /var/cache/apt/archives/ghex_43~alpha-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

   * What outcome did you expect instead?
package can be installed



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

Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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: ghex
Source-Version: 43~alpha-4
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated ghex 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: Wed, 07 Sep 2022 17:38:43 -0400
Source: ghex
Built-For-Profiles: noudeb
Architecture: source
Version: 43~alpha-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1018731
Changes:
 ghex (43~alpha-4) unstable; urgency=medium
 .
   * Cherry-pick patch to fix file conflict with gnome-text-editor
 (Closes: #1018731)
Checksums-Sha1:
 7aad9442425ef3073330c548494ed2efc7ff69b3 2204 ghex_43~alpha-4.dsc
 5cf9280d252b8301e9bcf609aa5feb240824e818 16620 ghex_43~alpha-4.debian.tar.xz
 29ad85d90728ad4319cf7e24e609815825e43373 17355 ghex_43~alpha-4_source.buildinfo
Checksums-Sha256:
 d0090978bd81c67ea68c57a79ba3cdfef36dfcede6fbfa6281d3c019dd0a0ff3 2204 
ghex_43~alpha-4.dsc
 a2686ee042d01515f86989131d84951bd62d54a6d51c2ef56654106fa5faa7a9 16620 
ghex_43~alpha-4.debian.tar.xz
 dde7846790788ed54eeb056a7dc588421ef6e8fa7b8045af4c8dadc55b86b039 17355 
ghex_43~alpha-4_source.buildinfo
Files:
 2b74ce61e2849ac639f65413064997e1 2204 gnome optional ghex_43~alpha-4.dsc
 69655d4cebcfad98a4ca32d11830a41f 16620 gnome optional 
ghex_43~alpha-4.debian.tar.xz
 03aafbd086c47d17f786a928ca06557d 17355 gnome optional 
ghex_43~alpha-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMZD3wACgkQ5mx3Wuv+
bH3Vww/5AadfxIRT9E1gwWfn9js+wTl6Gb3dvugj5+a0zMmT0G7xz1hLPXdaUVOZ
4TX+UB/1WuZ/lYrEySSU0W/jMKbPmYH0OzxFrfiFjE2w1g7fib8c1BZLYsZCHKV+
uNW74ZfxM5xb87E1clqjiVJobmwT/5Qzjx8Uy/2YdNhi9BJ4gMit2Cz8YrwIPTxX
WZfMPUHw6vGAjhTEdcYoAUYPnqy3zTJr6G29Wv2gI4PfiYKmJCtpbinKYHvh0j8r
vAkgYOmS3+5DrEo1bKtkbLiNWdzh6iFcAX2n97BH6hNdp/LTFFOPbdr2WI4Nu7uc
oWfFYztIFe9g16Y2bEKSWGAUrNOEhFxn+NpehkFAeZV3VkBILhSzX6HhV1dCKV9C
dOMy+UsVC0q4tEfNYTHkFDiiZTJZPIRrCeB+FcD9pargSXjjqXoCzyLHDOVssjFS
G5w07YRtvYBoYoJNbiC3JFL713Z/bTt5pka4b2s4OLT7wCZs9v9Ie576IY

Processed: Re: Bug#1019331: systemd-resolved: Update breaks DNS resolution, should be `Recommends:`.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1019331 {Done: Michael Biebl } [systemd] 
systemd-resolved: Update breaks DNS resolution, should be `Recommends:`.
Severity set to 'wishlist' from 'grave'
> tags -1 wontfix
Bug #1019331 {Done: Michael Biebl } [systemd] 
systemd-resolved: Update breaks DNS resolution, should be `Recommends:`.
Added tag(s) wontfix.
> close -1
Bug #1019331 {Done: Michael Biebl } [systemd] 
systemd-resolved: Update breaks DNS resolution, should be `Recommends:`.
Bug 1019331 is already marked as done; not doing anything.

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

Bug#1019331: systemd-resolved: Update breaks DNS resolution, should be `Recommends:`.

[Luca Boccassi]

Control: severity -1 wishlist
Control: tags -1 wontfix
Control: close -1

> For Systemd Maintainers I would recommend to add the package
> `systemd-resolved` to `Recommends:` instead of `Suggests:`.  Then it
> should be installed automatically on a Debian system with a default
> configured `apt` - as it was in the past.

No, we do not want to make resolved the default. The NEWS (and release
notes for Bookworm) mention this change, and that will be enough. If
you are using an unsupported setup it's up to you to keep up with
release notes.

-- 
Kind regards,
Luca Boccassi


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

Bug#1019321: marked as done (budgie-extras: FTBFS: E275 missing whitespace after keyword)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 21:04:14 +
with message-id 
and subject line Bug#1019321: fixed in budgie-extras 1.5.0-1
has caused the Debian Bug report #1019321,
regarding budgie-extras: FTBFS: E275 missing whitespace after keyword
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.)


-- 
1019321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: budgie-extras
Version: 1.4.90-2
Severity: serious
Justification: FTBFS
Tags: sid ftbfs patch

Hi,

budgie-extras fails to build due to a pep8 error with pycodestyle
2.9.1-1 (currently in sid). The attached patch fixes the issue.

See the relevant part of the build logs:

./tools/run-pep8
= pycodestyle = 

checking ./budgie-dropby/copy_flash 

checking ./budgie-dropby/checkonwin 

checking ./budgie-dropby/dropby_tools.py
./budgie-dropby/dropby_tools.py:133:11: E275 missing whitespace after keyword
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
make[1]: Leaving directory '/tmp/autopkgtest.MWCN9F/build.gEw/real-tree'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Fix pep8 error: E275 missing whitespace after keyword
Index: budgie-extras-1.4.90/budgie-dropby/dropby_tools.py
===
--- budgie-extras-1.4.90.orig/budgie-dropby/dropby_tools.py
+++ budgie-extras-1.4.90/budgie-dropby/dropby_tools.py
@@ -130,4 +130,4 @@ def get_volumes(allvols):
 devdata["free"] = free
 devdata["volume_path"] = fpath
 relevant.append(devdata)
-return(relevant)
+return (relevant)
--- End Message ---
--- Begin Message ---
Source: budgie-extras
Source-Version: 1.5.0-1
Done: David Mohammed 

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

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

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

Debian distribution maintenance software
pp.
David Mohammed  (supplier of updated budgie-extras 
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: Wed, 07 Sep 2022 21:17:19 +0100
Source: budgie-extras
Built-For-Profiles: noudeb
Architecture: source
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: David Mohammed 
Changed-By: David Mohammed 
Closes: 1019309 1019321
Changes:
 budgie-extras (1.5.0-1) unstable; urgency=medium
 .
   * Stable release
 - See NEWS
 - Fix dropby FTBFS (Closes: #1019321)
   * Packaging Changes
 - d/control B/D change to libgdk-pixbuf-2.0-dev
   (Closes: #1019309)
 - d/control Standards-Version: 4.6.1.0; no changes required
Checksums-Sha1:
 e4c3da9ecb68c051fbff5027752729405565e7d8 4877 budgie-extras_1.5.0-1.dsc
 873aba65bc5a78d79f53f4d57c3eda80cd42df65 10009804 
budgie-extras_1.5.0.orig.tar.xz
 1c714bb0618f1c0c0c062b1e39b2cc265d493b1d 833 
budgie-extras_1.5.0.orig.tar.xz.asc
 d3ac03b13f80821eaa8fb1a2370deaad406fff8d 18764 
budgie-extras_1.5.0-1.debian.tar.xz
 32d1a59470398191239145bd127801fba8b39a42 22904 
budgie-extras_1.5.0-1_source.buildinfo
Checksums-Sha256:
 7d272463dbbd172722d5a4abcd6fa2b1b10c60397f6a9958b1949a809eced6a9 4877 
budgie-extras_1.5.0-1.dsc
 10d14a1f6c90d5fa8106077094f83030a5ac26cf81e9820e9c34566b182a844a 10009804 
budgie-extras_1.5.0.orig.tar.xz
 1f3fd7ed535ac5885d2348e4aedbad70071960942fba291eabd4dadbbc188648 833 
budgie-extras_1.5.0.orig.tar.xz.asc
 5f5c8ab23bb1801efacedfb185ee1a8619280b339697c5c30d36b5f4d7f4c1c8 18764 
budgie-extras_1.5.0-1.debian.tar.xz
 ff63ab94d8ab70b299ef43f8361dccd015785098c30c437090531ac068ad8fdb 22904 
budgie-extras_1.5.0-1_source.buildinfo
Files:
 2ff56007168589c30ae8ddcabdfd78ac 4877 misc optional budgie-extras_1.5.0-1.dsc
 a8fdcd3a7251401cd62ed091246db02a 10009804 misc optional 
budgie-extras_1.5.0.orig.tar.xz
 49e2cadde6a53127b8738f87b8d9d5a3 833 

Bug#1018753: marked as done (abiword: FTBFS on several platforms (test timeout))

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 20:34:07 +
with message-id 
and subject line Bug#1018753: fixed in abiword 3.0.5~dfsg-3.1
has caused the Debian Bug report #1018753,
regarding abiword: FTBFS on several platforms (test timeout)
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.)


-- 
1018753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abiword
Version: 3.0.5~dfsg-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: i...@hack3r.moe

Dear maintainer,

abiword failed to build on armel, mipsel, hppa, ppc64, riscv64, sparc64 and x32
due to timeout of test located at `src/wp/test/unix`:

```
Making check in unix
make[6]: Entering directory '/<>/src/wp/test/unix'
make  AbiWord-test testwrap.sh-stamp testwrap.sh
make[7]: Entering directory '/<>/src/wp/test/unix'
g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../../../..  -I/usr/include/libpng16 
-pthread -I/usr/include/wv -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/enchant-2 -I/usr/include/libgsf-1 -I/usr/include/rasqal 
-I/usr/include/raptor2 -I/usr/include/evolution-data-server 
-I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
-I/usr/include/cairo -I/usr/include/gtk-3.0/unix-print -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/riscv64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/riscv64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/riscv64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libgoffice-0.10 -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_0 
-I/usr/include -I../../../..  -I../../../../src/af/ev/gtk 
-I../../../../src/af/ev/xp -I../../../../src/af/gr/gtk 
-I../../../../src/af/gr/xp -I../../../../src/af/util/unix 
-I../../../../src/af/util/xp -I../../../../src/af/xap/gtk 
-I../../../../src/af/xap/xp -I../../../../src/text/fmt/gtk 
-I../../../../src/text/fmt/xp -I../../../../src/text/ptbl/xp 
-I../../../../src/wp/impexp/gtk -I../../../../src/wp/impexp/xp 
-I../../../../src/wp/ap/gtk -I../../../../src/wp/ap/xp 
-I../../../../src/plugins -DABIWORD_DATADIR="\"/usr/share/abiword-3.0\"" 
-I../../../../src/af/tf/xp/ -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wsign-compare -Wpointer-arith -Wchar-subscripts -Wwrite-strings 
-Wmissing-noreturn -Wformat-overflow=2 -Wunused -Wpointer-arith -Wshadow  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-overloaded-virtual -MT AbiWord_test-test_main.o 
-MD -MP -MF .deps/AbiWord_test-test_main.Tpo -c -o AbiWord_test-test_main.o 
`test -f 'test_main.cpp' || echo './'`test_main.cpp
chmod a+x testwrap.sh
make[7]: 'testwrap.sh' is up to date.
touch testwrap.sh-stamp
In file included from test_main.cpp:21:
../xp/main.cpp:49:46: warning: macro "__TIME__" might prevent reproducible 
builds [-Wdate-time]
   49 | const char* XAP_App::s_szBuild_CompileTime = __TIME__;
  |  ^~~~
../xp/main.cpp:50:46: warning: macro "__DATE__" might prevent reproducible 
builds [-Wdate-time]
   50 | const char* XAP_App::s_szBuild_CompileDate = __DATE__;
  |  ^~~~
In file included from ../xp/all_test.h:29,
 from ../xp/main.cpp:24:
../../../../src/text/ptbl/xp/t/pp_PropertyMap.t.cpp: In function ‘void 
_tftest_main_12()’:
../../../../src/text/ptbl/xp/t/pp_PropertyMap.t.cpp:34:24: warning: unused 
variable ‘map’ [-Wunused-variable]
   34 | PP_PropertyMap map;
  |^~~
mv -f .deps/AbiWord_test-test_main.Tpo .deps/AbiWord_test-test_main.Po
/bin/bash ../../../../libtool  --tag=CXX   --mode=link g++ -std=c++11  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-overloaded-virtual -L../../../../src -labiword-3.0 
-L../../../../src/af/tf/xp -lxp -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
AbiWord-test AbiWord_test-test_main.o -lpng16 -lz -ljpeg -lfribidi 
-lgthread-2.0 -pthread -lwv -lz -lpng -lwmf -lwmflit

Bug#1017760: linux-image-5.10.0-17-amd64: No space for directory leaf checksum. Please run e2fsck -D.

[Thorsten Glaser]

Thorsten Glaser dixit:

>I’ve recently been getting filesystem corruption on this system, which,
>incidentally, is a fresh-ish installation since I’ve been hit by the

I have somewhat reason to at least suspect the µSD card this was
installed on. But there was never anything in syslog/dmesg about
it, so the Linux kernel clearly didn’t find fault with it at all.

Suggestions how I can prove/disprove this welcome; I now swapped
the filesystem contents to a new fs on a new µSD card, so tests
that are destructive can be done, but they need to be doable from
a Grml live ISO and should be doable overnight (i.e. not block
the system for too long).

Thanks in advance,
//mirabilos
-- 
Support mksh as /bin/sh and RoQA dash NOW!
‣ src:bash (416 (445) bugs: 0 RC, 282 (302) I&N, 134 (143) M&W, 0 F&P) + 207
‣ src:dash (94 (109) bugs: 0 RC, 52 (55) I&N, 42 (54) M&W, 0 F&P) + 63 ubu
‣ src:mksh (1 bug: 0 RC, 0 I&N, 1 M&W, 0 F&P)
dash has two RC bugs they just closed because they don’t care about quality…

Bug#1016938: konclude: autopkgtest regression on armhf, flaky test on s390x (with timeout)

[Paul Gevers]

Hi Adrian, all,

On 06-09-2022 23:24, Adrian Bunk wrote:

Looking at the armhf regression, has there been any change in the
autopkgtest infrastructure when it regressed?


Yes, we upgraded the hosts to bullseye and we changed to our current host.


The autopkgtest passes for me on amdahl.

The tests are also run as part of the package build, and in reproducible
they have been reliably passing on armhf:
https://tests.reproducible-builds.org/debian/history/armhf/konclude.html


Considering that the regression happened around the migration to the 
current host it may be worth while to explicitly mention that the host 
that runs our armhf tests is very powerful, see

https://metal.equinix.com/product/servers/c3-large-arm64/
i.e. 80 cores, 256 GB RAM. I've seen other tests fail due to not 
handling that much cores or memory correctly.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1018753: abiword: FTBFS on several platforms (test timeout)

[Jeremy Bicha]

Control: tags -1 pending

I am uploading a NMU now with high urgency to allow the ongoing
evolution-data-server transition to proceed smoothly.

Thank you,
Jeremy Bicha

Processed: Re: Bug#1018753: abiword: FTBFS on several platforms (test timeout)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1018753 [src:abiword] abiword: FTBFS on several platforms (test timeout)
Added tag(s) pending.

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

Bug#1016937: Bug#1018224: src:exempi: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Hi,

On 07-09-2022 21:57, Michael Biebl wrote:

I fail to see the connection between exempi and atop.
Have you copied the wrong bug report number?


Seems like this should have gone to 1016937 indeed (doing so now).

Paul



Michael

Am 07.09.22 um 19:00 schrieb Dipak Zope1:

Hi Paul,

Setting the environment variable ATOPACCT to empty value disables this 
issue.


Please use this workaround in the caller script of atop till we get a 
final fix.


export ATOPACCT=""

The behaviour is described in the source as below:

 /*

 ** when a particular environment variable is present, 
atop should


 ** use a specific accounting-file (as defined by the 
environment


 ** variable) or should use no process accounting at 
all (when


 ** contents of environment variable is empty)

 */

-Dipak

*From: *Dipak Zope1 
*Date: *Tuesday, 30 August 2022 at 3:28 PM
*To: *Paul Gevers , 1018...@bugs.debian.org 
<1018...@bugs.debian.org>, debian-s390 
*Subject: *[EXTERNAL] RE: src:exempi: fails to migrate to testing for 
too long: FTBFS on s390x


Apologies for late response. It looks like the issue is related to the 
synchronization between atop and atopacctd. I am looking into it 
further and will keep this thread updated. I am looking forward to 
have a fix for this for s390x. ‍ ‍ ‍ ‍ ‍


ZjQcmQRYFpfptBannerStart

*This Message Is From an External Sender *

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Apologies for late response. It looks like the issue is related to the 
synchronization between atop and atopacctd. I am looking into it 
further and will keep this thread updated.


I am looking forward to have a fix for this for s390x.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1018224: src:exempi: fails to migrate to testing for too long: FTBFS on s390x

[Michael Biebl]

Dipak,

I fail to see the connection between exempi and atop.
Have you copied the wrong bug report number?

Michael

Am 07.09.22 um 19:00 schrieb Dipak Zope1:

Hi Paul,

Setting the environment variable ATOPACCT to empty value disables this 
issue.


Please use this workaround in the caller script of atop till we get a 
final fix.


export ATOPACCT=""

The behaviour is described in the source as below:

     /*

     ** when a particular environment variable is present, 
atop should


     ** use a specific accounting-file (as defined by the 
environment


     ** variable) or should use no process accounting at all 
(when


     ** contents of environment variable is empty)

     */

-Dipak

*From: *Dipak Zope1 
*Date: *Tuesday, 30 August 2022 at 3:28 PM
*To: *Paul Gevers , 1018...@bugs.debian.org 
<1018...@bugs.debian.org>, debian-s390 
*Subject: *[EXTERNAL] RE: src:exempi: fails to migrate to testing for 
too long: FTBFS on s390x


Apologies for late response. It looks like the issue is related to the 
synchronization between atop and atopacctd. I am looking into it further 
and will keep this thread updated. I am looking forward to have a fix 
for this for s390x. ‍ ‍ ‍ ‍ ‍


ZjQcmQRYFpfptBannerStart

*This Message Is From an External Sender *

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Apologies for late response. It looks like the issue is related to the 
synchronization between atop and atopacctd. I am looking into it further 
and will keep this thread updated.


I am looking forward to have a fix for this for s390x.

-Dipak

On 30/08/22, 12:44 AM, "Paul Gevers"  wrote:

Hi Michael

On 29-08-2022 14:23, Michael Biebl wrote:

 > As you are probably aware, this issue is known and tracked in [1].

Which I added as a blocker and mentioned in my message, so yes.

 > The

 > package FTBFS after enabling the test suite. I raised this issue

 > upstream but there is no real interest/motivation [2] on their part to

 > address these (most likely endianess related) issues.

 > So I informed the s390x porters as well but got not feedback so far.

Ack, I saw the latter part.

 > To me it seems it's better to not continue ship a known broken package

 > on s390x and think a partial architecture removal is probably the better

 > alternative.

If you think the package indeed is severely broken, then removal sounds

best. If its broken in some less common use cases, it may be OK to leave

it for now (skipping those tests on 390x) and let the porters have a

look when they have time.

 > Let me know what you think

It all depends on how broken it is. If you would consider the bugs found

by the tests RC, then removal is the better choice unless a porter steps

up to fix it. If the bugs would be important at most, than skipping

broken tests on s390x sounds like the better option. Removal bugs are

hard to time predict.

Paul

PS: I would not disable building on s390x if you have the test suite

finding out severe problems (as the d/control file doesn't have negated

architecture fields yet). Just getting the binary removed and FTBFS will

prevent the architecture from building again.





OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1019051: ffmpeg: Repackaging with pipewire: dpkg-shlibdeps: error: no dependency information found for libjack.so.0 used by libavdevice.so.59.7.100

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1019051 [ffmpeg] ffmpeg: Repackaging with pipewire: dpkg-shlibdeps: error: 
no dependency information found for libjack.so.0 used by libavdevice.so.59.7.100
Added tag(s) moreinfo.
> severity -1 normal
Bug #1019051 [ffmpeg] ffmpeg: Repackaging with pipewire: dpkg-shlibdeps: error: 
no dependency information found for libjack.so.0 used by libavdevice.so.59.7.100
Severity set to 'normal' from 'serious'

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

Bug#1019051: ffmpeg: Repackaging with pipewire: dpkg-shlibdeps: error: no dependency information found for libjack.so.0 used by libavdevice.so.59.7.100

[Sebastian Ramacher]

Control: tags -1 moreinfo
Control: severity -1 normal

On 2022-09-03 07:29:20 -0400, Braiam Peguero wrote:
> Package: ffmpeg
> Version: 7:5.1-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
> Repackaging FFMPEG on a Pipewire enabled host, while fulfilling
> all dependencies fails on the shlibdeps step with the following message:
> 
> set -e && for pkg in libavcodec-extra59 libavfilter-extra8 
> libavformat-extra59; do \
>   mainpkg=`echo $pkg | sed 's/-extra//'`; \
>   cp -f debian/$mainpkg.symbols debian/$pkg.symbols; \
>   dh_shlibdeps -p$pkg; \
>   rm -f debian/$pkg.symbols; \
> done
> dh_shlibdeps --remaining-packages
> dpkg-shlibdeps: error: no dependency information found for 
> /usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjack.so.0 (used by 
> debian/libavdevice59/usr/lib/x86_64-linux-gnu/libavdevice.so.59.7.100)
> Hint: check if the library actually comes from a package.
> dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libavdevice59.substvars 
> debian/libavdevice59/usr/lib/x86_64-linux-gnu/libavdevice.so.59.7.100 
> returned exit code 25
> dh_shlibdeps: error: Aborting due to earlier error

I cannot reproduce this issue when building ffmpeg in sbuild with
pipewire-jack installed. Are you sure that's the root cause of your
issue? Could you please provide a full log?

Cheers

> 
> I'm unsure if ffmpeg dependencies needs to be more tighter wtr jack
> or if a change should be done to pipewire so that it correctly
> declares the shared library.
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages ffmpeg depends on:
> ii  libavcodec597:5.1-3
> ii  libavdevice59   7:5.1-3
> ii  libavfilter87:5.1-3
> ii  libavformat59   7:5.1-3
> ii  libavutil57 7:5.1-3
> ii  libc6   2.34-4
> ii  libpostproc56   7:5.1-3
> ii  libsdl2-2.0-0   2.24.0+dfsg-1
> ii  libswresample4  7:5.1-3
> ii  libswscale6 7:5.1-3
> 
> ffmpeg recommends no packages.
> 
> Versions of packages ffmpeg suggests:
> pn  ffmpeg-doc  
> 
> -- no debconf information
> 

-- 
Sebastian Ramacher

Bug#998955: marked as done (hunt: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 19:03:52 +
with message-id 
and subject line Bug#998955: fixed in hunt 1.5-6.2
has caused the Debian Bug report #998955,
regarding hunt: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


-- 
998955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hunt
Version: 1.5-6.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: hunt
Source-Version: 1.5-6.2
Done: Braulio Henrique Marques Souto 

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

Debian distribution maintenance software
pp.
Braulio Henrique Marques Souto  (supplier of updated hunt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Sep 2022 14:03:20 -0300
Source: hunt
Architecture: source
Version: 1.5-6.2
Distribution: unstable
Urgency: medium
Maintainer: Angel Ramos 
Changed-By: Braulio Henrique Marques Souto 
Closes: 965588 998955
Changes:
 hunt (1.5-6.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 13.
   - Closes: #965588
   * debian/rules: added missing targets build-arch and build-indep.
 (Closes: #998955)
Checksums-Sha1:
 9213e01cda083dbd8f3cf1b2d8eddffe438a3c60 1594 hunt_1.5-6.2.dsc
 b9eb986cdbec190cdf9d12c1b7782abfa0e82491 4747 hunt_1.5-6.2.diff.gz
 7d6147ee6738a0fcaaae8c50b0769730ee2b3137 5842 hunt_1.5-6.2_source.buildinfo
Checksums-Sha256:
 620aedfce9fc951e9a25dd69758c8dee052c6fb805f99f8d117d39a483bae54b 1594 
hunt_1.5-6.2.dsc
 75462804fb64256502edc25e3f8eae0e059dde5fda379d410f3130d7bc9b689a 4747 
hunt_1.5-6.2.diff.gz
 00adce545fb398f49b12003219f3b8c249b4c8849f7889f1655e65b13e76d747 5842 
hunt_1.5-6.2_source.buildinfo
Files:
 658a1398385d7b045fb19dc13376df6d 1594 net optional hunt_1.5-6.2.dsc
 510c7a9dcdb6a9eff1bfd020c87d64e0 4747 net optional hunt_1.5-6.2.diff.gz
 00d481d4b23ef8aee96ab29b58b29a4a 5842 net optional 
hunt_1.5-6.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmMWPugACgkQ3mO5xwTr
6e/VxxAAgEoGZkR1Q1m1AFUKcxJCbPSshmArDHGqjIZqMCtYdMWIzOaJjSLMHHE/
lBowWMNIRQn+t/FOpLFcTBk0EC17r5TbTS6ORHlpsYjapErOjnuaTZUo9XL6rtfF
HIdd8WsQViYofL3UZO1e8zokDok6cztWQGAoFl0rlgmnEt4o4p8mbY0mZBl1g7vN
ju84LTZpdYe5U+174oqShmKSFgw9VMQrLnC5XJ3jQQyH0ycAQO3vIP3RnjmBfLw2
+IqhBoZQ+cKOqeT5gFRku/zANoGayOpCX1mC7sFL7vjqRCiB6HCp1KhXHI6ruziA
nXIsekSCURbJ1tKbFG+fpzhSEGMa+cV4Qo9hv3fAZbf8WXpvrSeAx0rAVDPi16cK
Mtz7eqMcEKuDBn/wXV/F5v9SQChPq1oLNeAN/IS6fmIRSfq/wQS8Q5PG1YMvHtsa
V9YeOJMPq/hr0KyGLH+kENqgRHV5b3AreoOHUAU1DDTiiEO01OzPbGIkK/MZQtvU
NPOw6rMI77lqQJocBGE7jupoTOyboeW80BST2Iv5w+nzMnAdoqcy9Yu28C1oehp5
BB+P66hJWTiZq8yMYQIAuXjDBPblFKGi5UmdC0Ua/3EZI8ipqmqxJ8D13oQBLan+
WVh2bSk6WTzTo+8Y7xVCoRjXcaF2pTnA4OGf1t1VWzApjAXZBao=
=dDJg
-END PGP SIGNATURE End Message ---

Bug#965588: marked as done (hunt: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 19:03:52 +
with message-id 
and subject line Bug#965588: fixed in hunt 1.5-6.2
has caused the Debian Bug report #965588,
regarding hunt: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hunt
Version: 1.5-6.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package hunt uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: hunt
Source-Version: 1.5-6.2
Done: Braulio Henrique Marques Souto 

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

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

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

Debian distribution maintenance software
pp.
Braulio Henrique Marques Souto  (supplier of updated hunt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Sep 2022 14:03:20 -0300
Source: hunt
Architecture: source
Version: 1.5-6.2
Distribution: unstable
Urgency: medium
Maintainer: Angel Ramos 
Changed-By: Braulio Henrique Marques Souto 
Closes: 965588 998955
Changes:
 hunt (1.5-6.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 13.
   - Closes: #965588
   * debian/rules: added missing targets build-arch and build-indep.
 (Closes: #998955)
Checksums-Sha1:
 9213e01cda083dbd8f3cf1b2d8eddffe438a3c60 1594 hunt_1.5-6.2.dsc
 b9eb986cdbec190cdf9d12c1b7782abfa0e82491 4747 hunt_1.5-6.2.diff.gz
 7d6147ee6738a0fcaaae8c50b0769730ee2b3137 5842 hunt_1.5-6.2_source.buildinfo
Checksums-Sha256:
 620aedfce9fc951e9a25dd69758c8dee052c6fb805f99f8d117d39a483bae54b 1594 
hunt_1.5-6.2.dsc
 75462804fb64256502edc25e3f8eae0e059dde5fda379d410f3130d7bc9b689a 4747 
hunt_1.5-6.2.diff.gz
 00adce545fb398f49b12003219f3b8c249b4c8849f7889f1655e65b13e76d747 5842 
hunt_1.5-6.2_source.buildinfo
Files:
 658a1398385d7b045fb19dc13376df6d 1594 net optional hunt_1.5-6.2.dsc
 510c7a9dcdb6a9eff1bfd020c87d64e0 4747 net optional hunt_1.5-6.2.diff.gz
 00d481d4b23ef8aee96ab29b58b29a4a 5842 net optional 
hunt_1.5-6.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmMWPugACgkQ3mO5xwTr
6e/VxxAAgEoGZkR1Q1m1AFUKcxJCbPSshmArDHGqjIZqMCtYdMWIzOaJjSLMHHE/
lBowWMNIRQn+t/FOpLFcTBk0EC17r5TbTS6ORHlpsYjapErOjnuaTZUo9XL6rtfF
HIdd8WsQViYofL3UZO1e8zokDok6cztWQGAoFl0rlgmnEt4o4p8mbY0mZBl1g7vN
ju84LTZpdYe5U+174oqShmKSFgw9VMQrLnC5XJ3jQQyH0ycAQO3vIP3RnjmBfLw2
+IqhBoZQ+cKOqeT5gFRku/zANoGayOpCX1mC7sFL7vjqRCiB6HCp1KhXHI6ruziA
nXIsekSCURbJ1tKbFG+fpzhSEGMa+cV4Qo9hv3fAZbf8WXpvrSeAx0rAVDPi16cK
Mtz7eqMcEKuDBn/wXV/F5v9SQChPq1oLNeAN/IS6fmIRSfq/wQS8Q5PG1YMvHtsa
V9YeOJMPq/hr0KyGLH+kENqgRHV5b3AreoOHUAU1DDTiiEO01OzPbGIkK/MZQtvU
NPOw6rMI77lqQJocBGE7jupoTOyboeW80BST2Iv5w+nzMnAdoqcy9Yu28C1oehp5
BB+P66hJWTiZq8yMYQIAuXjDBPblFKGi5UmdC0Ua/3EZI8i

Bug#1012977: marked as done (libffado: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2022 20:42:34 +0200
with message-id 
and subject line Re: Bug#1012977: libffado: ftbfs with GCC-12
has caused the Debian Bug report #1012977,
regarding libffado: ftbfs with GCC-12
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.)


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

[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/libffado_2.4.5-1_unstable_gcc12.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/dbus-c++-1/dbus-c++/types.h:332:77: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const bool&’
  332 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
bool &val)
  | 
^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:338:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const int16_t&)’
  338 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
int16_t &val)
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:338:80: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const int16_t&’ {aka ‘const short int&’}
  338 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
int16_t &val)
  | 
~~~^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:344:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const uint16_t&)’
  344 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
uint16_t &val)
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:344:81: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const uint16_t&’ {aka ‘const short unsigned int&’}
  344 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
uint16_t &val)
  | 
^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:350:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const int32_t&)’
  350 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
int32_t &val)
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:350:80: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const int32_t&’ {aka ‘const int&’}
  350 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
int32_t &val)
  | 
~~~^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:356:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const uint32_t&)’
  356 | inline DBus::MessageIter &operator << (DBus::MessageIter &iter, const 
uint32_t &val)
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:356:81: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const uint32_t&’ {aka ‘const uns

Processed: tagging 1017493

[Debian Bug Tracking System]

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

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

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

Processed: Re: Bug#1018753: abiword: FTBFS on several platforms (test timeout)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1018753 [src:abiword] abiword: FTBFS on several platforms (test timeout)
Severity set to 'serious' from 'important'

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

Bug#1019352: python-pytest-flake8: FTBFS with flake8 5.0.4

[Emanuele Rocca]

Source: python-pytest-flake8
Version: 1.0.6-4
Severity: serious

The package fails to build with the flake8 version currently in sid,
namely 5.0.4-1. Multiple tests fail, partial output follows:

[...]

copying pytest_flake8.py -> 
/build/python-pytest-flake8-1.0.6/.pybuild/cpython3_3.10_python-pytest-flake8/build
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:240: cd 
/build/python-pytest-flake8-1.0.6/.pybuild/cpython3_3.10_python-pytest-flake8/build;
 pyt
hon3.10 -m pytest 
= test session starts ==
platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /build/python-pytest-flake8-1.0.6, configfile: tox.ini
plugins: flake8-1.0.6
collected 14 items

pytest_flake8.py F   [  7%]
test_flake8.py F...FF.xF [100%]
LURES ===
_ FLAKE8-check _
pytest_flake8.py:122: in runtest
found_errors = check_file(
pytest_flake8.py:201: in check_file
config_finder = config.ConfigFileFinder(
E   AttributeError: module 'flake8.options.config' has no attribute 
'ConfigFileFinder'
_ FLAKE8-check _
/usr/lib/python3/dist-packages/pluggy/_hooks.py:265: in __call__
return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
/usr/lib/python3/dist-packages/pluggy/_manager.py:80: in _hookexec

[...]

The autopkgtests also fail, see full output at:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pytest-flake8/25797652/log.gz

Bug#1017870: marked as done (gnome-shell-extension-gsconnect: Not compatible with gnome-shell 43)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 18:18:50 +
with message-id 
and subject line Bug#1017870: fixed in gnome-shell-extension-gsconnect 50-4
has caused the Debian Bug report #1017870,
regarding gnome-shell-extension-gsconnect: Not compatible with gnome-shell 43
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.)


-- 
1017870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-gsconnect
Version: 50-3
Severity: serious
Tags: upstream
Forwarded: 
https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/1428

gnome-shell-extension-gsconnect isn't compatible with gnome-shell 43,
currently available in Debian Experimental.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-gsconnect
Source-Version: 50-4
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated 
gnome-shell-extension-gsconnect 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: Wed, 07 Sep 2022 13:53:49 -0400
Source: gnome-shell-extension-gsconnect
Built-For-Profiles: noudeb
Architecture: source
Version: 50-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1017870
Changes:
 gnome-shell-extension-gsconnect (50-4) unstable; urgency=medium
 .
   * Add basic patch to allow use with GNOME Shell 43
   * debian/control.in: Bump max GNOME Shell version allowed (Closes: #1017870)
Checksums-Sha1:
 0266c9f65ddb0d0b02fa9106dceb6fd0ff0b431f 2440 
gnome-shell-extension-gsconnect_50-4.dsc
 a7b71db7377600ffc858a9cad49d6c62ac2a6b9c 6304 
gnome-shell-extension-gsconnect_50-4.debian.tar.xz
 ea6d372ca0074d140648d8586b6fd5b0b55de986 12171 
gnome-shell-extension-gsconnect_50-4_source.buildinfo
Checksums-Sha256:
 fbc32ee8fa14164fba0ccf67dc1c770b9f0fce3ebd2f4fd374ff2ddbd8566d9f 2440 
gnome-shell-extension-gsconnect_50-4.dsc
 effd8a6c26ba0c07a7d3ff2a8fbec7773b57cf7e43f5d7f459f8ffc0cb54599d 6304 
gnome-shell-extension-gsconnect_50-4.debian.tar.xz
 13b3679c0c51f4b455ed205c80c908383c756dfef74db707f27a40c03cb550dc 12171 
gnome-shell-extension-gsconnect_50-4_source.buildinfo
Files:
 843104bec009432ff32a1b0292973863 2440 gnome optional 
gnome-shell-extension-gsconnect_50-4.dsc
 8eb90724b4ff1d1e073d468fa28b1cd9 6304 gnome optional 
gnome-shell-extension-gsconnect_50-4.debian.tar.xz
 1631936a0198932cc6b231d3da840840 12171 gnome optional 
gnome-shell-extension-gsconnect_50-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMY3QsACgkQ5mx3Wuv+
bH2WCQ//Rx618na7MdGlOgIo746Q0dRFOQei2xfFtvZyEHiyhnuJ0UUS5mBtFxIY
VBShEUrEJ8bjNGDxvauGQZbnNVcXAvt+JBqP0yyGvUI0H4iJB9NP5KgqnTbbeoGN
/SYZpUqjv9kWCEPRZhK3Fj09S+TvtBiK/mW5+zTk5ZB3mCdQcrmmqS22WRxw76qv
5Fr349AcgPdViN6OuocyA73Ef3o4Bts3m4373Cza6+PZXEnxp3gvT3RBe9OgMOnK
LAbAWS1vkTcPzuHnEQ0Qg8KMTGFNtDfy70sqihdYGNxDUYUmfnbskjD3eegtqRQ3
1G9Z0IKZeJcQcXyPClmPRCIQrNylGe1bkYT/4Uo3D1Nimzih0wzpUtEoyLW3b/v7
TGo7ZocPlOavAXeR7zmFmdbTDxyn4mhMjMumA4OBjxhjmvf1c1YFo1FJDOo3qHkc
6JUetXQMG5TWIcNEJavl+dtP/9FWMGNko0EPEQw9+cHcCszXVyFXRbSU6WHwK1Pw
t6YHwKKAu2qUTVA+bDjHAMjPPQB6Bufidzsbf63lVUaW7VHRa2i5xBnEYbPpcIGR
qEBOFQAGN3/YKaosbNzB08KuJAp/taCzogQhBJBBopWUIG6Q0rLaIG5DprXOlXIX
3Dhortg0ljNiigadrdj2vX0HgHAuxsIhrBofMn5FKa2agSJyl0Y=
=QRvK
-END PGP SIGNATURE End Message ---

Bug#1017609: marked as done (ruby-terser: Test fails with node-terser >= 5)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 18:05:25 +
with message-id 
and subject line Bug#1017609: fixed in ruby-terser 1.1.12+dfsg-1
has caused the Debian Bug report #1017609,
regarding ruby-terser: Test fails with node-terser >= 5
to be marked as done.

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

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


-- 
1017609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-terser
Version: 1.0.2+dfsg-5
Severity: important
Tags: ftbfs

Hi,

node-terser >= 5 is ready in experimental. It works fine for all Debian
packages except ruby-terser: test fails.

Could you take a look at that to allow migration to unstable ?

Cheers,
Yadd
--- End Message ---
--- Begin Message ---
Source: ruby-terser
Source-Version: 1.1.12+dfsg-1
Done: Mohammed Bilal 

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

Debian distribution maintenance software
pp.
Mohammed Bilal  (supplier of updated ruby-terser 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: Wed, 07 Sep 2022 22:43:41 +0530
Source: ruby-terser
Architecture: source
Version: 1.1.12+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Mohammed Bilal 
Closes: 1017609
Changes:
 ruby-terser (1.1.12+dfsg-1) unstable; urgency=medium
 .
   [ Yadd ]
   * Reproduce upstream terser.js (Closes: #1017609):
 + Drop dependency to libjs-terser
 + Add build dependency to node-terser >= 5
 + Build terser.js using upstream patches
 .
   [ Mohammed Bilal ]
   * New upstream version 1.1.12+dfsg
   * Bump standards version to 4.6.1
Checksums-Sha1:
 8eec9fb64e254a88238ab893aef175ddab000cbb 2221 ruby-terser_1.1.12+dfsg-1.dsc
 d5adb7b74b46409cb0c0602f298faa917ae30976 18316 
ruby-terser_1.1.12+dfsg.orig.tar.xz
 1d5af0b4a5ccdf6a29a419bacfded41f7cbd5211 5344 
ruby-terser_1.1.12+dfsg-1.debian.tar.xz
 2a08e70ee480e828ae2bb9135eb133ebf33119c5 9606 
ruby-terser_1.1.12+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 3199ac837da6dbb87fc15726cf15212cd43619c5581da4b07677528527511fa0 2221 
ruby-terser_1.1.12+dfsg-1.dsc
 d5b483061c99f5e3e84a2ef05a6c93429f5dcec552fe368999e635382586131d 18316 
ruby-terser_1.1.12+dfsg.orig.tar.xz
 73cd6ecec4802530bf22d498c75b4825bf7b29ede7717dc622bafd4ac42104d8 5344 
ruby-terser_1.1.12+dfsg-1.debian.tar.xz
 220d55d078675c6fdf1253a90b084ceeb89cef3b4bd5a49379fcecce73e32315 9606 
ruby-terser_1.1.12+dfsg-1_amd64.buildinfo
Files:
 c86a3baac273db54385d9ee8296b6ba1 2221 ruby optional 
ruby-terser_1.1.12+dfsg-1.dsc
 a6d34a079d276a3e1ddc1155570ee983 18316 ruby optional 
ruby-terser_1.1.12+dfsg.orig.tar.xz
 727edf55dda7a5f9e1efd9f136d54ce9 5344 ruby optional 
ruby-terser_1.1.12+dfsg-1.debian.tar.xz
 19d289b9c18768db12962ff9ef6ea2df 9606 ruby optional 
ruby-terser_1.1.12+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEELWW8HrlmWm6X+XMKs/WUUoUhnh8FAmMY1+kUHG1kYmlsYWxA
ZGlzcm9vdC5vcmcACgkQs/WUUoUhnh/GVA//RDQFDjfu/uddJxp7UuHeSq6nK7at
3wsAgsbF+Inf3ui8hZFeYK0ZJBe8+lFWol7h36Qz70fY2UVh6U+vFMNumrgW67Fs
Ewi4GMPqnuz21muYLTxH5eSNtlZjlmfRfXcFTubwhPEWSDH7c6Sge2YCFFJk18aj
XUOQMcwacaqPyThSRau5vsPvVMsfAvdxSwvUHSUqOuDkTI7K9snOjbB6RGNzj9+8
ErKKx192qk30MGkLquw+bPHaMvKRZEmI1h1BCX2O4LlDA0+y5x21Oh4Af1k73oTp
MyV3o4dysJE7WZ8ioeMwH+2IIXbitSLaS6T2WGB38CJ6xi/lSLOr107Gh0dEOx7A
rXfn5TX7CAYGU+OVfjcKQwwfVk20a0rHBf3NHz5sFH2ZV7KYFFc6TvLHY7vTmZ4t
t5xftPeCEWyxLapDvqyi44LVZoq5Ssgl8ZzFqrLUm2pX+Q/cLhnNLox5CrpPYk6j
kchB/eM6IyMOk4fiQRh4LMktlpc2vm4c1VFMgRlyVmPo+cGo1GzpvX7GR0Eozfw4
satbrAhLlG2lOTr2w/xQGYDy1IXsG5qJ94tGHrTGbv5MF+JZjK2HX8C+ZQBD+3zB
R8bKc3va2sPVDmc8u2qhWLT8tHHUSDljrBhnz6dPLa+Og1CYE2MEesEdzMvzNRxJ
fx6D6tpJ/fGfR5o=
=QF2w
-END PGP SIGNATURE End Message ---

Bug#1011716: closing 1011716

[Sebastian Ramacher]

close 1011716 1:1.3.1-2
thanks

Processed: closing 1011716

[Debian Bug Tracking System]

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

> close 1011716 1:1.3.1-2
Bug #1011716 [src:libbluray] libbluray: FTBFS: [javac] 
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: 
error: BDFileSystemImpl is not abstract and does not override abstract method 
isInvalid(File) in FileSystem
Ignoring request to alter fixed versions of bug #1011716 to the same values 
previously set
Bug #1011716 [src:libbluray] libbluray: FTBFS: [javac] 
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: 
error: BDFileSystemImpl is not abstract and does not override abstract method 
isInvalid(File) in FileSystem
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: block 996464 with 951683 1019349

[Debian Bug Tracking System]

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

> block 996464 with 951683 1019349
Bug #996464 [wnpp] ITP: atomic-data-rust -- graph database server to share 
Atomic Data on the web
996464 was blocked by: 1013106 1013098 1013109 984622 1010212 1010256 1013103 
1019090 1013104 1013100 969609 1019144 1013107 1013099 1013108 1019044
996464 was not blocking any bugs.
Added blocking bug(s) of 996464: 951683 and 1019349
> thanks
Stopping processing here.

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

Bug#1019300: marked as done (mp3guessenc: autopkgtests failure with grep 3.8: fgrep is deprecated)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 17:35:24 +
with message-id 
and subject line Bug#1019300: fixed in mp3guessenc 0.27.5+dfsg.1-2
has caused the Debian Bug report #1019300,
regarding mp3guessenc: autopkgtests failure with grep 3.8: fgrep is deprecated
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.)


-- 
1019300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mp3guessenc
Version: 0.27.5+dfsg.1-1
Severity: serious
Tags: patch
Justification: breaks autopkgtests

Hi,

GNU grep 3.8 officially deprecates egrep and fgrep, and those two
commands now issue a deprecation message on stderr [1].

The autopkgtests of mp3guessenc use fgrep, and while they still work
fine, the extra messages on stderr are considered by default a failure,
and thus the tests are marked as such. While autopkgtest has a
"allow-stderr" restriction to not consider stderr output as failure in
case it is expected, I think the better solution here is simply to
switch away from fgrep to grep -F. This works fine with grep 3.8 and
any older version.

Patch attached for this.

[1] https://lists.gnu.org/archive/html/info-gnu/2022-09/msg1.html

Thanks,
-- 
Pino
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/changelog 
mp3guessenc-0.27.5+dfsg.1/debian/changelog
--- mp3guessenc-0.27.5+dfsg.1/debian/changelog  2020-09-20 21:50:00.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/changelog  2022-09-07 08:12:34.0 
+0200
@@ -1,3 +1,12 @@
+mp3guessenc (0.27.5+dfsg.1-2) UNRELEASED; urgency=medium
+
+  [ Pino Toscano ]
+  * Switch from "fgrep" to "grep -F" in autopkgtests, as the former is
+officially deprecated since grep 3.8, writing a deprecation message on
+stderr that is considered as autopkgtest failure.
+
+ -- Peter Blackman   Wed, 07 Sep 2022 08:12:34 +0200
+
 mp3guessenc (0.27.5+dfsg.1-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/tests/a 
mp3guessenc-0.27.5+dfsg.1/debian/tests/a
--- mp3guessenc-0.27.5+dfsg.1/debian/tests/a2020-07-16 10:49:55.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/tests/a2022-09-07 08:12:13.0 
+0200
@@ -6,7 +6,7 @@
 mp3guessenc -a debian/flush.mp3 > a.tmp
 set -e
 #
-fgrep 291 a.tmp
+grep -F 291 a.tmp
 #
 rm a.tmp
 
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/tests/f 
mp3guessenc-0.27.5+dfsg.1/debian/tests/f
--- mp3guessenc-0.27.5+dfsg.1/debian/tests/f2020-07-16 10:43:15.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/tests/f2022-09-07 08:12:13.0 
+0200
@@ -6,8 +6,8 @@
 mp3guessenc -f debian/flush.mp3 > f.tmp
 set -e
 #
-fgrep "48 kbps" f.tmp
-fgrep 550 f.tmp
+grep -F "48 kbps" f.tmp
+grep -F 550 f.tmp
 #
 rm f.tmp
 
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/tests/i 
mp3guessenc-0.27.5+dfsg.1/debian/tests/i
--- mp3guessenc-0.27.5+dfsg.1/debian/tests/i2020-07-16 10:48:58.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/tests/i2022-09-07 08:12:13.0 
+0200
@@ -6,8 +6,8 @@
 mp3guessenc -i debian/flush.mp3 > i.tmp
 set -e
 #
-fgrep 2020 i.tmp
-fgrep Ambient i.tmp
+grep -F 2020 i.tmp
+grep -F Ambient i.tmp
 #
 rm i.tmp
 
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/tests/m 
mp3guessenc-0.27.5+dfsg.1/debian/tests/m
--- mp3guessenc-0.27.5+dfsg.1/debian/tests/m2020-07-16 10:44:39.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/tests/m2022-09-07 08:12:13.0 
+0200
@@ -6,8 +6,8 @@
 mp3guessenc -f debian/flush.mp3 > f.tmp
 set -e
 #
-fgrep "48 kbps" f.tmp
-fgrep 550 f.tmp
+grep -F "48 kbps" f.tmp
+grep -F 550 f.tmp
 #
 rm f.tmp
 
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/tests/n 
mp3guessenc-0.27.5+dfsg.1/debian/tests/n
--- mp3guessenc-0.27.5+dfsg.1/debian/tests/n2020-07-16 11:08:27.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/tests/n2022-09-07 08:12:13.0 
+0200
@@ -11,7 +11,7 @@
 fi
 set -e
 #
-fgrep FhG n.tmp
+grep -F FhG n.tmp
 #
 rm n.tmp
 
diff -Nru mp3guessenc-0.27.5+dfsg.1/debian/tests/s 
mp3guessenc-0.27.5+dfsg.1/debian/tests/s
--- mp3guessenc-0.27.5+dfsg.1/debian/tests/s2020-07-16 10:51:16.0 
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/tests/s2022-09-07 08:12:13.0 
+0200
@@ -6,7 +6,7 @@
 mp3guessenc -s debian/flush.mp3 > s.tmp
 set -e
 #
-fgrep FhG s.tmp
+grep -F FhG s.tmp
 #
 rm s.tmp
 
--- End Message ---
--- Begin Message ---
Source: mp3guessenc
Source-Version: 0.27.5+dfsg.1-2
Done: Peter Blackman 

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

Bug#1019349: librust-cssparser-dev: impossible to install

[Jonas Smedegaard]

Package: librust-cssparser-dev
Version: 0.27.2-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on several missing packages. 

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMY1LoACgkQLHwxRsGg
ASHv8A//ToueLfvnKx7VrPDsyMlGMobcXLnoZUB0kejrUHlckxcFY+I/PHgtWsek
t+Q67fL/VJbq3VwYmRN5DLAZ5SiRnuS1wp8p620JrQoFJLs1AQGmF38yHMaskXPT
ezbwtDMckG3CBh8nHIV8XW/Kf3ApJZnwH1q0Hx6Jd1r92XdknkesNuktkxhj4R2w
ZY1RaJxefHWI3hunCxqB2KUwuPx+QjC5qZ8DMQtlehmJbNrrhtYio5srhAz4LE1Q
RDycZd1+NtoJAE1s9t7ITw5WBm8umvubjcxbY0PZT5cODvSSiamZvuuHCPCK2si/
khb8XXzHNgwm60wDsSHp2a6RuLj7XOPHIcMyr2la45mMqwVB7H7gYpqFagRo/9vF
03vusOkj41RGfn6aSUQVp6p5qN9rFJAJEo/YgEGU9+E6axb3iMl7zuyWqm4ZxJ+/
njX+GCg6lA1dnKTnDuOcN0yL9nUUQNSfZ80rSRCcumBNDzw8IGS9hr3MTnB5bBJL
nN/50LTt0bAq+YBd6tz8VLW9YIW61/Ept4Yfyi0TevFcSD4AvNjzxwImWhM0Yfkx
MOb7UQmyodaeR5BjrF4SCzBwVG8CHdKOOlYa/pU52GDGWXu30qtRT92y/dAm1otz
++mJJdKPUHfoaWM0nlPdiWQopisp16jFGZtJw22EI5Dt03ogpWI=
=QSRT
-END PGP SIGNATURE-

Bug#1017032: marked as done (awesome: flaky autopkgtest: sometimes reports on stderr: Could not resolve keysym XF86EmojiPicker)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 17:19:35 +
with message-id 
and subject line Bug#1017032: fixed in awesome 4.3-5.1
has caused the Debian Bug report #1017032,
regarding awesome: flaky autopkgtest: sometimes reports on stderr: Could not 
resolve keysym XF86EmojiPicker
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.)


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

Source: awesome
Version: 4.3-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc [0]. It seems that it 
regularly fails on all architectures due to *warnings* printed on 
stderr. autopkgtest by default fails on output to stderr, which can be 
changed by adding a "allow-stderr" restriction to the test. Obviously 
it's better to prevent the output.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[0] 
https://ci.debian.net/data/autopkgtest/testing/ppc64el/a/awesome/24520223/log.gz


autopkgtest [23:18:38]: test integration.sh:  - - - - - - - - - - 
results - - - - - - - - - -
integration.sh   FAIL stderr: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
autopkgtest [23:18:38]: test integration.sh:  - - - - - - - - - - stderr 
- - - - - - - - - -

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:  Could not resolve keysym XF86EmojiPicker
Errors from xkbcomp are not fatal to the X server


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: awesome
Source-Version: 4.3-5.1
Done: Marcos Talau 

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

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated awesome package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Sep 2022 13:10:29 -0300
Source: awesome
Architecture: source
Version: 4.3-5.1
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Marcos Talau 
Closes: 1017032
Changes:
 awesome (4.3-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/tests/control: Add restriction "allow-stderr". (Closes: #1017032)
Checksums-Sha1:
 a666fb0277784ecfd75d49bb39cd9322708a76c4 2825 awesome_4.3-5.1.dsc
 18c25581328a1df1fb4ef7bce7d13924a5c09919 23620 awesome_4.3-5.1.debian.tar.xz
 f0bc26f8131bd3162aa86ce0521597835dbfaa67 13542 awesome_4.3-5.1_source.buildinfo
Checksums-Sha256:
 8555cf8e1a62e93dc38f81b440a8001d6508299b9e431630f8e40976a88d64e2 2825 
awesome_4.3-5.1.dsc
 017e81e1eb6af006da3a69a786534a50d1ea3550b65b082ec971cd5895b4a35a 23620 
awesome_4.3-5.1.debian.tar.xz
 b456c4232759d7e608aa0afa87e1b549b8e0f3a3e3f5faac0210c610dd6838b5 13542 
awesome_4.3-5.1_source.buildinfo
Files:
 98980bc675f6338fd25bcf56d1119851 2825 x11 optional awesome_4.3-5.1.dsc
 b839ae227bf9738c3fc262eefd39ac5b 23620 x11 optional 
awesome_4.3-5.1.debian.tar.xz
 49a0c9a4a04abb4c07d2ac83022b26a8 13542 x11 optional 
awesome_4.3-5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmMWJ9cACgkQ9LqqgNso
ukxvBQ//cMGUJQoyYh6P5JZ8R5KBpkVDH+B5LHvGzWR0GOUDIRw8UgNjfCKspHs2
GDbCsAB9lvh07XVx+XuhT6Q8hGcAdrV+uqUzo8Mwd6gkc9LEyE8UNtdbD03zvbmD
8SgvJOT4k2Rle1y7CQD0itikt6P5CUY+ZGM+klAbebM9D0wiyg2CVgqunnwClMQk
RdnB+zdkpb4RJPiy+lQ++Szit0h0RdXCPrnUarskLErT+6inZVA/Nu3D99eUVUZ4
BwDxnhSux5v5PvRZDfIA2rOHqGA1A517iSBmSRSsJNBjaxG9TvBBplcQN7E1c7ur
oDqfBYPSiNwUkqQc12FsZImFk7pGjFq2NWIxfd3rLDjgoeNURWPAabNmr4IRsqUN
tFdhD+/VC6BURvefqZjDqle7/wLHGN8ASKhxA/k2ubiNdbjF8Dq2Mo/lTWldbu6L
JkyB6ebL58SZPkIQxv33xYBOTTN8Ksi3m/9M4oCxbkpQpy4u721l

Bug#1018224: src:exempi: fails to migrate to testing for too long: FTBFS on s390x

[Dipak Zope1]

Hi Paul,


Setting the environment variable ATOPACCT to empty value disables this issue.

Please use this workaround in the caller script of atop till we get a final fix.

 export ATOPACCT=""





The behaviour is described in the source as below:



/*

** when a particular environment variable is present, atop 
should

** use a specific accounting-file (as defined by the environment

** variable) or should use no process accounting at all (when

** contents of environment variable is empty)

*/



-Dipak

From: Dipak Zope1 
Date: Tuesday, 30 August 2022 at 3:28 PM
To: Paul Gevers , 1018...@bugs.debian.org 
<1018...@bugs.debian.org>, debian-s390 
Subject: [EXTERNAL] RE: src:exempi: fails to migrate to testing for too long: 
FTBFS on s390x
Apologies for late response. It looks like the issue is related to the 
synchronization between atop and atopacctd. I am looking into it further and 
will keep this thread updated. I am looking forward to have a fix for this for 
s390x. ‍ ‍ ‍ ‍ ‍
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Apologies for late response. It looks like the issue is related to the 
synchronization between atop and atopacctd. I am looking into it further and 
will keep this thread updated.

I am looking forward to have a fix for this for s390x.

-Dipak


On 30/08/22, 12:44 AM, "Paul Gevers"  wrote:
Hi Michael

On 29-08-2022 14:23, Michael Biebl wrote:
> As you are probably aware, this issue is known and tracked in [1].

Which I added as a blocker and mentioned in my message, so yes.

> The
> package FTBFS after enabling the test suite. I raised this issue
> upstream but there is no real interest/motivation [2] on their part to
> address these (most likely endianess related) issues.
> So I informed the s390x porters as well but got not feedback so far.

Ack, I saw the latter part.

> To me it seems it's better to not continue ship a known broken package
> on s390x and think a partial architecture removal is probably the better
> alternative.

If you think the package indeed is severely broken, then removal sounds
best. If its broken in some less common use cases, it may be OK to leave
it for now (skipping those tests on 390x) and let the porters have a
look when they have time.

> Let me know what you think

It all depends on how broken it is. If you would consider the bugs found
by the tests RC, then removal is the better choice unless a porter steps
up to fix it. If the bugs would be important at most, than skipping
broken tests on s390x sounds like the better option. Removal bugs are
hard to time predict.

Paul

PS: I would not disable building on s390x if you have the test suite
finding out severe problems (as the d/control file doesn't have negated
architecture fields yet). Just getting the binary removed and FTBFS will
prevent the architecture from building again.

Processed: Backups end up mostly empty when location.patterns is used and /root/.borgmatic exists

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.6.3-1
Bug #1019347 [borgmatic] Backups end up mostly empty when location.patterns is 
used and /root/.borgmatic exists
Marked as found in versions borgmatic/1.6.3-1.

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

Bug#1019347: Backups end up mostly empty when location.patterns is used and /root/.borgmatic exists

[Sven Bartscher]

Package: borgmatic
Version: 1.5.12-2
Severity: grave
Tags: upstream fixed-upstream
Forwarded: 
https://projects.torsion.org/borgmatic-collective/borgmatic/issues/574
Control: found -1 1.6.3-1

Hi,

Recently I reported the bug mentioned above upstream, which causes
most data to be silently excluded from backups if /root/.borgmatic
exists. Since details of the bug are already available in the upstream
bug report, I will omit them here for brevity.

Since the issue has already been fixed upstream, this bug is only
meant to track the issue in Debian.

I've set the severity to grave, because the bug causes borgmatic to
produce effectively empty backups, while the user may believe to have
secure backups, which qualifies as data loss to me. Feel free to lower
the severity to normal if you disagree.

Regards
Sven

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (102, 
'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages borgmatic depends on:
ii  borgbackup 1.2.1-2
ii  python33.10.6-1
ii  python3-colorama   0.4.5-2
ii  python3-jsonschema 4.6.0-3
ii  python3-pkg-resources  59.6.0-1.2
ii  python3-requests   2.27.1+dfsg-1
ii  python3-ruamel.yaml0.17.16-1

borgmatic recommends no packages.

borgmatic suggests no packages.

-- no debconf information

Processed: tags 1019300

[Debian Bug Tracking System]

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

> package src:mp3guessenc
Limiting to bugs with field 'package' containing at least one of 
'src:mp3guessenc'
Limit currently set to 'package':'src:mp3guessenc'

> tags 1019300 + pending
Bug #1019300 [src:mp3guessenc] mp3guessenc: autopkgtests failure with grep 3.8: 
fgrep is deprecated
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1019345: flake8-class-newline: autopkgtest failure

[Emanuele Rocca]

Source: flake8-class-newline
Version: 1.6.0-2
Severity: serious

Hi,

the test fails with the latest flake8 version in sid (5.0.4-1).

The output of flake8 --version with -class-newline installed is now:

$ flake8 --version
5.0.4 (flake8-class-newline: 1.6.0, mccabe: 0.6.1, pycodestyle: 2.9.1,
pyflakes: 2.5.0) CPython 3.10.6 on Linux

While the autopkgtest expects it to include the string
"new_line_checker".

https://ci.debian.net/data/autopkgtest/testing/amd64/f/flake8-class-newline/25797651/log.gz

[...]
Processing triggers for libc-bin (2.34-7) ...
(Reading database ... 14305 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [20:13:42]: test install: [---
autopkgtest [20:13:43]: test install: ---]
autopkgtest [20:13:43]: test install:  - - - - - - - - - - results - - -
- - - - - - -
install  FAIL non-zero exit status 1
autopkgtest [20:13:43]:  summary
install  FAIL non-zero exit status 1

Bug#1019340: Segfaults on startup

[tony mancill]

On Wed, Sep 07, 2022 at 04:57:14PM +0200, Christoph Berg wrote:
> Package: tucnak
> Version: 4.36-1
> Severity: grave
> 
> tucnak doesn't start here:
> 
> $ LC_ALL=C tucnak

Hi Christoph,

Hmm... it starts and runs here, so I don't think it is broken for
everyone.  I uninstalled and reinstalled to be sure that I'm running the
binaries from the archive.  Perhaps related to differences in windowing
setups?  I'm running xwayland and Gnome.

Looking at your stack trace, my first guess is that this is an issue
introduced in libzia based on this bit.

> #11 0x7febdc0654f8 n/a (libSDL2-2.0.so.0 + 0x314f8)
> #12 0x5586f25c0438 tucnak_crash (tucnak + 0xb0438)
> #13 0x7febdc3589d4 z_sig_segv (libzia-4.36.so + 0x169d4)
> #14 0x7febdaa3daf0 __restore_rt (libc.so.6 + 0x3daf0)
> #15 0x7febd5ead5ee n/a (crocus_dri.so + 0xad5ee)
> #16 0x7febd80836e6 glPrimitiveBoundingBox 
> (libGLX_mesa.so.0 + 0x4e6e6)
> #17 0x7febd8085d32 glPrimitiveBoundingBox 
> (libGLX_mesa.so.0 + 0x50d32)
> #18 0x7febd80860d3 glPrimitiveBoundingBox 
> (libGLX_mesa.so.0 + 0x510d3)
> #19 0x7febd5eaf0df n/a (crocus_dri.so + 0xaf0df)

I will poke through the libzia changes.

Thanks,
tony

Bug#1019106: marked as done (gnome-initial-setup: Needs updating for evolution-data-server 3.46)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 15:34:29 +
with message-id 
and subject line Bug#1019106: fixed in gnome-initial-setup 43~rc.1-1
has caused the Debian Bug report #1019106,
regarding gnome-initial-setup: Needs updating for evolution-data-server 3.46
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.)


-- 
1019106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-initial-setup
Version: 42.2-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: evolution-3.46

gnome-initial-setup needs to be updated for the big
evolution-data-server transition (which switches to libsoup3 and
librest 0.9).

This is done in the 43 version but the 43 version also requires the
GTK4 version of webkit2gtk (the 5.0 API) which is only built in
Experimental currently.

Therefore, my plan is for gnome-initial-setup to become temporarily
uninstallable in Unstable and removed from Testing until webkit2gtk
2.38 is uploaded to Unstable later this month. This allows us to
complete the rest of the transition.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnome-initial-setup
Source-Version: 43~rc.1-1
Done: Jeremy Bicha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-initial-setup 
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: Wed, 07 Sep 2022 11:04:27 -0400
Source: gnome-initial-setup
Built-For-Profiles: noudeb
Architecture: source
Version: 43~rc.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1019106
Changes:
 gnome-initial-setup (43~rc.1-1) unstable; urgency=high
 .
   * New upstream release
   * Add patch to disable privacy page. It uses webkitgtk 5.0
 which is still only in Debian Experimental
   * debian/control.in: Drop webkitgtk from Build-Depends for now
   * Add patch from Ubuntu to re-enable existing-user mode.
 It was disabled upstream because it conflicts with gnome-tour
 but gnome-tour isn't available in Debian or Ubuntu yet
   * Release to unstable (Closes: #1019106)
Checksums-Sha1:
 347339133486c22a90d46e3a03d06b3cae2ee74d 2852 gnome-initial-setup_43~rc.1-1.dsc
 039655247eea3e76ae1818dc1cf3d21761345c04 526588 
gnome-initial-setup_43~rc.1.orig.tar.xz
 d64c0ba30d0c2b7c57f4c5def7ba7612276e659b 8580 
gnome-initial-setup_43~rc.1-1.debian.tar.xz
 7721acb89f30317daba5fc4bbc6867623d3a7089 18212 
gnome-initial-setup_43~rc.1-1_source.buildinfo
Checksums-Sha256:
 5c62b0adf535e101f620ae49220a42081dd5747823b6607805ced3788f1a8545 2852 
gnome-initial-setup_43~rc.1-1.dsc
 4adf3f0af064ca0ab41b2885673ce7411c60f2a8c95dfa01046083fe2d9172b9 526588 
gnome-initial-setup_43~rc.1.orig.tar.xz
 740c031829bc5a1ddec9250530c72daa1278cb1a1e5c90cce6762ba62471c1bd 8580 
gnome-initial-setup_43~rc.1-1.debian.tar.xz
 d935edbd97be12013996a7d92b5b5484b7214e5f39b49e69cbe85bf6a7d2d2c0 18212 
gnome-initial-setup_43~rc.1-1_source.buildinfo
Files:
 d37f8782188cb4d403cabb86a218d5fe 2852 gnome optional 
gnome-initial-setup_43~rc.1-1.dsc
 be64d5402088676b87820070fe0fc2b0 526588 gnome optional 
gnome-initial-setup_43~rc.1.orig.tar.xz
 7dbc5bd604a7db43526dc5cbef1713d2 8580 gnome optional 
gnome-initial-setup_43~rc.1-1.debian.tar.xz
 52f224ebfcc84e3402bcce342d06856a 18212 gnome optional 
gnome-initial-setup_43~rc.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMYs2YACgkQ5mx3Wuv+
bH1imRAAu7LdMsF11lx2W3SD/vAquKC/+wQ3FTgsYgPDF3XHxkP7sLBF/isDvD2C
tNZJ/pwm4OAKWr7ey7l58tIqyv/JaA0LDAY+B4q4kZp8cuRwiygqAkS5BW9ucGaR
1yu1T72dsR5tmtCahKsDWtGNxctZDFIx3BqqZHAS3dAHG1UCB2Ax4moScRDSSERM
0G2c4OVF9+XoShqpHQpfi2CFJ6WlWHvQJU8S7FZtHC7qnps9YxxP4nd00zWD7mqy
Y0C/ZKw6jDsDlEGjJ9lh+ZxHH8aMw8zxMvCWPmksmlRN//wBGCcJfYUY7eIhGon9
difLuwuWi8CTPTkfygHCvqnpiJGZ5EUR1hKU3EWh/XZ4//G6eCE5ScCag+Oo0UCU
tqn6EY4c3nzM8MOrNZh809gCxehqpQFxOHXU80sO2wlkFE7kAYu/tDxHET9PS

Bug#1018966: marked as done (widelands: crashes on startup: could not find file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 15:24:25 +
with message-id 
and subject line Bug#1018966: fixed in widelands 2:1.0-3
has caused the Debian Bug report #1018966,
regarding widelands: crashes on startup: could not find file or directory: 
i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
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.)


-- 
1018966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: widelands
Version: 2:1.0-2
Severity: important
X-Debbugs-Cc: waxh...@dirtcellar.net

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Updated the system with aptitude which included an update for widelands.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I started widelands, clicked the options button and widelands crashed.

---snip---
[00:00:13.577 real] WARNING: Font file not found. Falling back to sans: 
Culmus/TaameyFrankCLM-Medium.ttf
[00:00:13.577 real] WARNING: LayeredFileSystem: Could not load file: could not 
find file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:13.577 real] WARNING: I have tried the following path(s):
[00:00:13.577 real] WARNING: 
/home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:13.577 real] WARNING: 
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:13.577 real] WARNING: 
/home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

Caught exception (of type '17FileNotFoundError') in outermost handler!
The exception said: LayeredFileSystem: Could not load file: could not find file 
or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
I have tried the following path(s):

/home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
/home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

This should not happen. Please file a bug report on version 1.0(Release).
and remember to specify your operating system.

[00:00:13.594 real] INFO: SoundHandler: Closing 1 time, 44100 Hz, format 32784, 
2 channels
[00:00:13.594 real] INFO: SoundHandler: SDL_AUDIODRIVER pulseaudio
---snap---

   * What was the outcome of this action?

Widelands crashed and told me to report the bug.

   * What outcome did you expect instead?

That widelands should run, wihtout me needing to report a bug ;)

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages widelands depends on:
ii  libc62.34-4
ii  libcurl3-gnutls  7.84.0-2
ii  libgcc-s112.2.0-1
ii  libglew2.2   2.2.0-4
ii  libglx0  1.5.0-1
ii  libicu71 71.1-3
ii  libminizip1  1.1-8+b1
ii  libopengl0   1.5.0-1
ii  libpng16-16  1.6.37-5
ii  libsdl2-2.0-02.24.0+dfsg-1
ii  libsdl2-image-2.0-0  2.6.0+dfsg-1
ii  libsdl2-mixer-2.0-0  2.6.1+dfsg-1
ii  libsdl2-ttf-2.0-02.20.0+dfsg-1
ii  libstdc++6   12.2.0-1
ii  widelands-data   2:1.0-2

widelands recommends no packages.

widelands suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: widelands
Source-Version: 2:1.0-3
Done: Tobias Frost 

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated widelands 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)


-BEGI

Processed: found 1019340 in 4.36-2, notfound 1019340 in 4.36-1

[Debian Bug Tracking System]

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

> found 1019340 4.36-2
Bug #1019340 [tucnak] Segfaults on startup
Marked as found in versions tucnak/4.36-2.
> notfound 1019340 4.36-1
Bug #1019340 [tucnak] Segfaults on startup
No longer marked as found in versions tucnak/4.36-1.
> thanks
Stopping processing here.

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

Bug#1019340: Segfaults on startup

[Christoph Berg]

Package: tucnak
Version: 4.36-1
Severity: grave

tucnak doesn't start here:

$ LC_ALL=C tucnak
tucnak: ../src/GLX/libglx.c:966: CommonMakeCurrent: Assertion `oldCtxInfo != 
NULL' failed.
Abgebrochen (Speicherabzug geschrieben)

The stack traces look mostly like garbage:

Stack trace of thread 1472741:
#0  0x7febdaa8983c __pthread_kill_implementation (libc.so.6 
+ 0x8983c)
#1  0x7febdaa3da52 __GI_raise (libc.so.6 + 0x3da52)
#2  0x7febdaa28469 __GI_abort (libc.so.6 + 0x28469)
#3  0x7febdaa28395 __assert_fail_base (libc.so.6 + 0x28395)
#4  0x7febdaa36b02 __GI___assert_fail (libc.so.6 + 0x36b02)
#5  0x7febd80aa3bf n/a (libGLX.so.0 + 0x53bf)
#6  0x7febdc1418a3 n/a (libSDL2-2.0.so.0 + 0x10d8a3)
#7  0x7febdc114aba n/a (libSDL2-2.0.so.0 + 0xe0aba)
#8  0x7febdc115de6 n/a (libSDL2-2.0.so.0 + 0xe1de6)
#9  0x7febdc115ee1 n/a (libSDL2-2.0.so.0 + 0xe1ee1)
#10 0x7febdc0650b2 n/a (libSDL2-2.0.so.0 + 0x310b2)
#11 0x7febdc0654f8 n/a (libSDL2-2.0.so.0 + 0x314f8)
#12 0x5586f25c0438 tucnak_crash (tucnak + 0xb0438)
#13 0x7febdc3589d4 z_sig_segv (libzia-4.36.so + 0x169d4)
#14 0x7febdaa3daf0 __restore_rt (libc.so.6 + 0x3daf0)
#15 0x7febd5ead5ee n/a (crocus_dri.so + 0xad5ee)
#16 0x7febd80836e6 glPrimitiveBoundingBox (libGLX_mesa.so.0 
+ 0x4e6e6)
#17 0x7febd8085d32 glPrimitiveBoundingBox (libGLX_mesa.so.0 
+ 0x50d32)
#18 0x7febd80860d3 glPrimitiveBoundingBox (libGLX_mesa.so.0 
+ 0x510d3)
#19 0x7febd5eaf0df n/a (crocus_dri.so + 0xaf0df)
#20 0x7febd5eaf21f n/a (crocus_dri.so + 0xaf21f)
#21 0x7febd5eb2205 n/a (crocus_dri.so + 0xb2205)
#22 0x7febd5f85c92 n/a (crocus_dri.so + 0x185c92)
#23 0x7febd5f85f9a n/a (crocus_dri.so + 0x185f9a)
#24 0x7febd5eb1de4 n/a (crocus_dri.so + 0xb1de4)
#25 0x7febd5eb4d51 n/a (crocus_dri.so + 0xb4d51)
#26 0x7febd8077efc n/a (libGLX_mesa.so.0 + 0x42efc)
#27 0x7febd80687f2 n/a (libGLX_mesa.so.0 + 0x337f2)
#28 0x7febd80a87e3 n/a (libGLX.so.0 + 0x37e3)
#29 0x7febd80a9116 n/a (libGLX.so.0 + 0x4116)
#30 0x7febd80aa378 n/a (libGLX.so.0 + 0x5378)
#31 0x7febdc1418a3 n/a (libSDL2-2.0.so.0 + 0x10d8a3)
#32 0x7febdc114aba n/a (libSDL2-2.0.so.0 + 0xe0aba)
#33 0x7febdc0a7daa n/a (libSDL2-2.0.so.0 + 0x73daa)
#34 0x7febdc0a9e0a n/a (libSDL2-2.0.so.0 + 0x75e0a)
#35 0x7febdc09d981 n/a (libSDL2-2.0.so.0 + 0x69981)
#36 0x7febdc09fda9 n/a (libSDL2-2.0.so.0 + 0x6bda9)
#37 0x7febdc087d3a n/a (libSDL2-2.0.so.0 + 0x53d3a)
#38 0x7febdc08e11d n/a (libSDL2-2.0.so.0 + 0x5a11d)
#39 0x7febdc08deb6 n/a (libSDL2-2.0.so.0 + 0x59eb6)
#40 0x7febdc13a02c n/a (libSDL2-2.0.so.0 + 0x10602c)
#41 0x7febdc13b6db n/a (libSDL2-2.0.so.0 + 0x1076db)
#42 0x7febdc087e33 n/a (libSDL2-2.0.so.0 + 0x53e33)
#43 0x5586f2631edb sdl_event_thread (tucnak + 0x121edb)
#44 0x7febdc279c0d n/a (libglib-2.0.so.0 + 0x7ec0d)
#45 0x7febdaa87b27 start_thread (libc.so.6 + 0x87b27)
#46 0x7febdab0a78c __clone3 (libc.so.6 + 0x10a78c)

Stack trace of thread 1472737:
#0  0x7febdaaa13db __memmove_sse2_unaligned_erms (libc.so.6 
+ 0xa13db)
#1  0x7febd5f72904 n/a (crocus_dri.so + 0x172904)
#2  0x7febd5f34f9d n/a (crocus_dri.so + 0x134f9d)
#3  0x7febd5f3831d n/a (crocus_dri.so + 0x13831d)
#4  0x7febd5f3e928 n/a (crocus_dri.so + 0x13e928)
#5  0x7febdc0a8949 n/a (libSDL2-2.0.so.0 + 0x74949)
#6  0x7febdc0a0fc9 n/a (libSDL2-2.0.so.0 + 0x6cfc9)
#7  0x7febdc1110f9 n/a (libSDL2-2.0.so.0 + 0xdd0f9)
#8  0x7febdc11222c n/a (libSDL2-2.0.so.0 + 0xde22c)
#9  0x5586f26337da progress (tucnak + 0x1237da)
#10 0x5586f258bb05 main (tucnak + 0x7bb05)
#11 0x7febdaa2920a __libc_start_call_main (libc.so.6 + 
0x2920a)
#12 0x7febdaa292bc __libc_start_main_impl (libc.so.6 + 
0x292bc)
#13 0x5586f258c0d1 _start (tucnak + 0x7c0d1)

Stack trace of thread 1472740:
#0  0x7febdaa847ea __futex_abstimed_wait_common64 
(libc.so.6 + 0x847ea)

Bug#1018961: pypandoc tests fail with 2.17.1.1

[Gianfranco Costamagna]

control: forwarded -1 
https://githublab.com/repository/issues/NicklasTegner/pypandoc/278

Hello, this might actually be a pandoc conf issue.

G.

On Fri, 2 Sep 2022 10:17:11 -0700 Steve Langasek  
wrote:

Source: pypandoc
Version: 1.7.4+ds0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

Hi Elena,

The pypandoc autopkgtests are failing against pandoc 2.17.1.1 in unstable:

[...]
==
ERROR: test_conversion_from_non_plain_text_file (tests.TestPypandoc)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.jwltu_fs/downtmp/build.Zuz/src/tests.py", line 
407, in test_conversion_from_non_plain_text_file
received = pypandoc.convert_text('# some title\n', to='docx', format='md', 
outputfile=file_name)
  File 
"/tmp/autopkgtest-lxc.jwltu_fs/downtmp/build.Zuz/src/pypandoc/__init__.py", 
line 113, in convert_text
return _convert_input(source, format, 'string', to, extra_args=extra_args,
  File 
"/tmp/autopkgtest-lxc.jwltu_fs/downtmp/build.Zuz/src/pypandoc/__init__.py", 
line 372, in _convert_input
raise RuntimeError(
RuntimeError: Pandoc died with exitcode "97" during conversion: Could not find 
data file data/data/docx/[Content_Types].xml
[...]

  (https://ci.debian.net/packages/p/pypandoc/testing/amd64/)

I don't know if this is just a bug in the pypandoc tests or if it represents
a regression in pypandoc's usability with the new pandoc, or a regression in
pandoc itself.  There is a /usr/share/pandoc/data/docx/[Content_Types].xml
in pandoc-data, perhaps this is a path issue?

--
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

Processed: Re: pypandoc tests fail with 2.17.1.1

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://githublab.com/repository/issues/NicklasTegner/pypandoc/278
Bug #1018961 [src:pypandoc] pypandoc tests fail with 2.17.1.1
Set Bug forwarded-to-address to 
'https://githublab.com/repository/issues/NicklasTegner/pypandoc/278'.

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

Bug#1017284: marked as done (fenics-dolfinx: FTBFS: CheckSymbolExists.c:8:19: error: ‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you mean ‘PETSC_HAVE_COMPLEX’?)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 15:31:02 +0200
with message-id <4c75a61015eb605e48abbb904c492...@debian.org>
and subject line Re: Bug#1017284: fenics-dolfinx: FTBFS: 
CheckSymbolExists.c:8:19: error: ‘PETSC_USE_COMPLEX’ undeclared (first use in 
this function); did you mean ‘PETSC_HAVE_COMPLEX’?
has caused the Debian Bug report #1017284,
regarding fenics-dolfinx: FTBFS: CheckSymbolExists.c:8:19: error: 
‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you mean 
‘PETSC_HAVE_COMPLEX’?
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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/cc  -I/usr/lib/petscdir/petsc3.16/x86_64-linux-gnu-real/include -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Wdate-time -D_FORTIFY_SOURCE=2  -o 
> CMakeFiles/cmTC_d1fc9.dir/CheckSymbolExists.c.o -c 
> /<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c
> /<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
>  In function ‘main’:
> /<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:19:
>  error: ‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you 
> mean ‘PETSC_HAVE_COMPLEX’?
> 8 |   return ((int*)(&PETSC_USE_COMPLEX))[argc];
>   |   ^
>   |   PETSC_HAVE_COMPLEX
> /<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:19:
>  note: each undeclared identifier is reported only once for each function it 
> appears in
> gmake[3]: *** [CMakeFiles/cmTC_d1fc9.dir/build.make:78: 
> CMakeFiles/cmTC_d1fc9.dir/CheckSymbolExists.c.o] Error 1
> gmake[3]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp'
> gmake[2]: *** [Makefile:127: cmTC_d1fc9/fast] Error 2
> gmake[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp'
> 
> 
> File 
> /<>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
> /* */
> #include 
> 
> int main(int argc, char** argv)
> {
>   (void)argv;
> #ifndef PETSC_USE_COMPLEX
>   return ((int*)(&PETSC_USE_COMPLEX))[argc];
> #else
>   (void)argc;
>   return 0;
> #endif
> }
> dh_auto_configure: error: cd obj-x86_64-linux-gnu-real && cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -D 
> CMAKE_BUILD_TYPE:STRING=RelWithDebInfo -D BUILD_SHARED_LIBS:BOOL=ON -D 
> CMAKE_SKIP_RPATH:BOOL=ON -D CMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -D 
> DOLFINX_ENABLE_TRILINOS:BOOL=OFF -D DOLFINX_ENABLE_HDF5:BOOL=ON -D 
> HDF5_C_COMPILER_EXECUTABLE:FILEPATH=/usr/bin/h5pcc -D 
> DOLFINX_ENABLE_PARMETIS:BOOL=OFF -D DOLFINX_ENABLE_SCOTCH:BOOL=ON -D 
> DOLFINX_ENABLE_DOCS:BOOL=OFF -D DOLFINX_ENABLE_MPI:BOOL=ON -D 
> MPIEXEC_PARAMS:STRING=--oversubscribe -D CMAKE_CXX_FLAGS:STRING=-fpermissive 
> -D "DOLFINX_EXTRA_CXX_FLAGS:STRING=-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" -DXTENSOR_USE_XSIMD=ON /<>/cpp .. 
> returned exit code 1
> make[1]: *** [debian/rules:144: override_dh_auto_configure] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/fenics-dolfinx_0.4.1-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reprod

Bug#1019300: mp3guessenc: autopkgtests failure with grep 3.8: fgrep is deprecated

[Peter B]

On 07/09/2022 07:22, Pino Toscano wrote:

Source: mp3guessenc
Version: 0.27.5+dfsg.1-1
Severity: serious
Tags: patch
Justification: breaks autopkgtests

Hi,

GNU grep 3.8 officially deprecates egrep and fgrep, and those two
commands now issue a deprecation message on stderr [1].

The autopkgtests of mp3guessenc use fgrep, and while they still work
fine, the extra messages on stderr are considered by default a failure,
and thus the tests are marked as such. While autopkgtest has a
"allow-stderr" restriction to not consider stderr output as failure in
case it is expected, I think the better solution here is simply to
switch away from fgrep to grep -F. This works fine with grep 3.8 and
any older version.

Patch attached for this.

[1] https://lists.gnu.org/archive/html/info-gnu/2022-09/msg1.html

Thanks,


Thanks for the patch.

I've uploaded a fixed version to Mentors.
https://mentors.debian.net/package/mp3guessenc/



Cheers,
Peter

Bug#1019323: marked as done (ros-rosdep: FTBFS E275 missing whitespace after keyword)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2022 11:34:04 +
with message-id 
and subject line Bug#1019323: fixed in ros-rosdep 0.22.1-2
has caused the Debian Bug report #1019323,
regarding ros-rosdep: FTBFS E275 missing whitespace after keyword
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.)


-- 
1019323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-rosdep
Version: 0.22.1-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs

Hi,

ros-rosdep fails to build with the flake8 version currently in sid.

The relevant part of a failed build follows:

1 E275 missing whitespace after keyword
- Captured stderr call -
/build/ros-rosdep-0.22.1/.pybuild/cpython3_3.10/build/test/test_rosdep_source.py:191:15:
 E275 missing whitespace
 after keyword
assert not(commands)
  ^
flake8 reported 1 errors
--- End Message ---
--- Begin Message ---
Source: ros-rosdep
Source-Version: 0.22.1-2
Done: Emanuele Rocca 

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

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

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

Debian distribution maintenance software
pp.
Emanuele Rocca  (supplier of updated ros-rosdep 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: Wed, 07 Sep 2022 12:46:37 +0200
Source: ros-rosdep
Architecture: source
Version: 0.22.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Emanuele Rocca 
Closes: 1019323
Changes:
 ros-rosdep (0.22.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add 0001-fix-flake8-ftbfs.patch to fix flake8 error: E275 missing
 whitespace after keyword (Closes: #1019323)
Checksums-Sha1:
 d1bbdb523f911656e1dbf20557bea1a5efc576cb 2359 ros-rosdep_0.22.1-2.dsc
 b0fe277687eab775a398ccd3dedad6963687c4cc 8672 ros-rosdep_0.22.1-2.debian.tar.xz
 3c0b43af84c5e2fef2eae94d04f988454d5f4db4 8196 
ros-rosdep_0.22.1-2_amd64.buildinfo
Checksums-Sha256:
 6276261a361a7fb5dfa8d43d1b5bba997da7944b0fa3796ff933e329f392d68d 2359 
ros-rosdep_0.22.1-2.dsc
 d658a5549bc03bacd11ebf2018901890c3d1663b2f66263e8e63674512a957d5 8672 
ros-rosdep_0.22.1-2.debian.tar.xz
 5076e9e146e0db513c07c84d14af4aa9a15ff6d7e8936ee33dfef2ed6bd8e697 8196 
ros-rosdep_0.22.1-2_amd64.buildinfo
Files:
 b8ac15886afe763bba0554906b4ca524 2359 python optional ros-rosdep_0.22.1-2.dsc
 38a1a3654cedfdfa591294eb3f925eb5 8672 python optional 
ros-rosdep_0.22.1-2.debian.tar.xz
 dd3ed52d9b068fdcbb99853e69fef74c 8196 python optional 
ros-rosdep_0.22.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmMYf7kACgkQ1QhaB1D9
t6Nk5A//feKsBut3Q6VhaPe5l5v3tFUPm7XNSQrTIW2hbgauu8VNIRcFFDGV9tmA
8QsCBtVGHAe0HSyCTErTOYnX4FfFnemR+ZxEPqtNkgQQTx/L1Ma7PGgWoUh+AOau
5mKP2BqSTLDGHizHBKdl4z19DUBsFbC1zHY8Rsw1c5w4YzckHlZWE4r4UZLcIsqy
a08FP8alhJLpoLx9oxoVx8tqJps6pQ7rr6MxSEZ3bc6BwIj6KSvLV3Jq+jZHcNSI
Mdv3UT2kEDHQldo0s2/a95B8qCrg2ADz59YuH+ZbMMFC3xo59aa8w6gHhi8cbW/0
EPTEKn/8ESyTlQQpNUJ2EwV1fWuKFEJGHIZGdTlfOFwjnPZvLSqIzFgrJTirD01Z
ZLQjivPNh2qBr4sqsNSzjiwCxoU92gEeAjYUDspCz1DuUdY3dhtL6Gv3R3PzTH1b
4mZoZIbUp6nDuuECpOSGfmIHF/u2p/I4Bkbulqo0resAW03UALevZqOeMf+S/w4Y
k+qM9LuLHYbOfXyJfL/rBp4imydBlTSRjADbYvdqncsiXbnRi1Jb2jAKEQoq75/6
qoz+vIyP9wFv56eeErMtCJ0fqTBaULF2dj8v9gop4xYqe0nZ9W+TUkHfYSxUW5N8
dPD+W/mrNIMCvctISco+NbHkQ36xOCOHBs8xHiRt7K6P9CsNKc8=
=Ya82
-END PGP SIGNATURE End Message ---

Bug#1019323: ros-rosdep: FTBFS E275 missing whitespace after keyword

[Emanuele Rocca]

Source: ros-rosdep
Version: 0.22.1-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs

Hi,

ros-rosdep fails to build with the flake8 version currently in sid.

The relevant part of a failed build follows:

1 E275 missing whitespace after keyword
- Captured stderr call -
/build/ros-rosdep-0.22.1/.pybuild/cpython3_3.10/build/test/test_rosdep_source.py:191:15:
 E275 missing whitespace
 after keyword
assert not(commands)
  ^
flake8 reported 1 errors

Bug#1019321: budgie-extras: FTBFS: E275 missing whitespace after keyword

[Emanuele Rocca]

Source: budgie-extras
Version: 1.4.90-2
Severity: serious
Justification: FTBFS
Tags: sid ftbfs patch

Hi,

budgie-extras fails to build due to a pep8 error with pycodestyle
2.9.1-1 (currently in sid). The attached patch fixes the issue.

See the relevant part of the build logs:

./tools/run-pep8
= pycodestyle = 

checking ./budgie-dropby/copy_flash 

checking ./budgie-dropby/checkonwin 

checking ./budgie-dropby/dropby_tools.py
./budgie-dropby/dropby_tools.py:133:11: E275 missing whitespace after keyword
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
make[1]: Leaving directory '/tmp/autopkgtest.MWCN9F/build.gEw/real-tree'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Fix pep8 error: E275 missing whitespace after keyword
Index: budgie-extras-1.4.90/budgie-dropby/dropby_tools.py
===
--- budgie-extras-1.4.90.orig/budgie-dropby/dropby_tools.py
+++ budgie-extras-1.4.90/budgie-dropby/dropby_tools.py
@@ -130,4 +130,4 @@ def get_volumes(allvols):
 devdata["free"] = free
 devdata["volume_path"] = fpath
 relevant.append(devdata)
-return(relevant)
+return (relevant)

Processed: dh-fortran-mod superlu-dist

[Debian Bug Tracking System]

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

> block 1019287 by 1019050
Bug #1019287 [libsuperlu-dist-dev] libsuperlu-dist-dev: installed 
libsuperlu-dist-dev:amd64 package post-removal script subprocess returned error 
exit status 1
1019287 was not blocked by any bugs.
1019287 was not blocking any bugs.
Added blocking bug(s) of 1019287: 1019050
> thanks
Stopping processing here.

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

Bug#1017609: ruby-terser: Test fails with node-terser >= 5

[Yadd]

On 06/09/2022 11:29, Yadd wrote:

Control: tags -1 + pending patch

On 06/09/2022 10:38, Yadd wrote:
Le 28 août 2022 19:29:33 GMT+02:00, Mohd Bilal  
a écrit :


    Hi Yadd :)

    On Thu, 25 Aug 2022 10:58:21 +0200 Yadd  wrote:

    ruby-terser uses a patched terser.js (see
https://github.com/ahorek/terser-ruby/blob/master/patches/terser-sync.patch) 


    So this issue is simple to fix: copy node-terser files into
    vendor/terser and patch it using upstream patch.



    I had a look at this and tried doing what you suggested, but 
copying and patching had zero effect on the tests. They are still 
failing.


    According to [1] I think terser bin has to be generated from the 
source with the patches applied.


    I tried your approach and tried generating the minfied terser.js 
but the autopkgtest error[2] suggests that the patched 
function(minifySync) aren't seen in the minified lib/terser.js


    Can you maybe use this upstream patch onto node-terser and also 
generate a min file that can be used with ruby-terser? Is it possible?


    Or do you have any other alternative to suggest ?

    [1] 
-https://github.com/ahorek/terser-ruby/blob/master/Rakefile#L55 
#L66
    [2] -http://paste.debian.net/1251967/ 



    Thanks


Hi,

the Ruby patch can't be applied to node-terser because it provides a 
wrong JavaScript: await call in a non-async function (maybe Ruby has 
its own JS engine which accepts this?).

So I don't see any way to do what you proposed on JS side.

Cheers,
Yadd


Here is a patch that reproduce upstream terser's build.

Cheers,
Yadd


Can I push an NMU upload to unblock node-terser migration or can a 
Ruby-Team member push that ?

Bug#1019303: librm0: library mismatch between roger-router and librm0

[Hilko Bengen]

control: reassign -1 roger-router

Processed: Re: Bug#1019303: librm0: library mismatch between roger-router and librm0

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 roger-router
Bug #1019303 [librm0] librm0: library mismatch between roger-router and librm0
Bug reassigned from package 'librm0' to 'roger-router'.
No longer marked as found in versions librm/2.2.3-1.
Ignoring request to alter fixed versions of bug #1019303 to the same values 
previously set

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

Bug#1019303: librm0: library mismatch between roger-router and librm0

[Hilko Bengen]

control: severity -1 seriouos

>* What led up to the situation?
>   Installing the new version of roger-router, which
>   started using libsoup3 instead of libsoup2

We'll have to port librm to libsoup-3.0, too. This is going to be … fun.

Cheers,
-Hilko

Processed: severity of 1019303 is serious

[Debian Bug Tracking System]

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

> severity 1019303 serious
Bug #1019303 [librm0] librm0: library mismatch between roger-router and librm0
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1018821: gdb: FTBFS with readline 8.2 due to constness changes

[Graham Inggs]

Control: tags -1 + fixed-upstream patch

This was fixed upstream [1] by the following patch:

--- a/gdb/completer.c
+++ b/gdb/completer.c
@@ -36,7 +36,7 @@
calling a hook instead so we eliminate the CLI dependency.  */
 #include "gdbcmd.h"

-/* Needed for rl_completer_word_break_characters() and for
+/* Needed for rl_completer_word_break_characters and for
rl_filename_completion_function.  */
 #include "readline/readline.h"

@@ -2011,7 +2011,7 @@ gdb_completion_word_break_characters_throw ()
   rl_basic_quote_characters = NULL;
 }

-  return rl_completer_word_break_characters;
+  return (char *) rl_completer_word_break_characters;
 }

 char *

Regards
Graham


[1] 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1add37b567a7dee39d99f37b37802034c3fce9c4

Processed: gdb: FTBFS with readline 8.2 due to constness changes

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream patch
Bug #1018821 [src:gdb] gdb: FTBFS with readline 8.2 due to constness changes
Added tag(s) patch and fixed-upstream.

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