Bug#997239: marked as done (monado: FTBFS: comp_layer_renderer.c:311:24: error: initialization of ‘unsigned int’ from ‘void *’ makes integer from pointer without a cast [-Werror=int-conversion])

[Debian Bug Tracking System]

Your message dated Wed, 27 Oct 2021 06:48:37 +
with message-id 
and subject line Bug#997239: fixed in monado 21.0.0~dfsg1-2
has caused the Debian Bug report #997239,
regarding monado: FTBFS: comp_layer_renderer.c:311:24: error: initialization of 
‘unsigned int’ from ‘void *’ makes integer from pointer without a cast 
[-Werror=int-conversion]
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.)


-- 
997239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: monado
Version: 21.0.0~dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> cd "/<>/obj-x86_64-linux-gnu/src/xrt/compositor" && /usr/bin/cc  
> -I"/<>/src/xrt/compositor" -I"/<>/src/xrt/include" 
> -I"/<>/obj-x86_64-linux-gnu/src/xrt/include" 
> -I"/<>/src/xrt/auxiliary" 
> -I"/<>/obj-x86_64-linux-gnu/src/xrt/auxiliary" -isystem 
> "/<>/obj-x86_64-linux-gnu/src/xrt/compositor" -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic -Wall 
> -Wextra -Wno-unused-parameter -Werror-implicit-function-declaration 
> -Werror=incompatible-pointer-types -Werror=int-conversion -fPIC -MD -MT 
> src/xrt/compositor/CMakeFiles/comp_main.dir/main/comp_layer_renderer.c.o -MF 
> CMakeFiles/comp_main.dir/main/comp_layer_renderer.c.o.d -o 
> CMakeFiles/comp_main.dir/main/comp_layer_renderer.c.o -c 
> "/<>/src/xrt/compositor/main/comp_layer_renderer.c"
> /<>/src/xrt/compositor/main/comp_layer_renderer.c: In function 
> ‘_init_graphics_pipeline’:
> /<>/src/xrt/compositor/main/comp_layer_renderer.c:311:24: error: 
> initialization of ‘unsigned int’ from ‘void *’ makes integer from pointer 
> without a cast [-Werror=int-conversion]
>   311 | .subpass = VK_NULL_HANDLE,
>   |^~
> /<>/src/xrt/compositor/main/comp_layer_renderer.c:311:24: note: 
> (near initialization for ‘pipeline_info.subpass’)
> cc1: some warnings being treated as errors
> make[3]: *** [src/xrt/compositor/CMakeFiles/comp_main.dir/build.make:209: 
> src/xrt/compositor/CMakeFiles/comp_main.dir/main/comp_layer_renderer.c.o] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/monado_21.0.0~dfsg1-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: monado
Source-Version: 21.0.0~dfsg1-2
Done: Ryan Pavlik 

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

Debian distribution maintenance software
pp.
Ryan Pavlik  (supplier of updated monado 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: Tue, 26 Oct 2021 16:59:16 -0500
Source: monado
Architecture: source
Version: 21.0.0~dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Ryan Pavlik 
Changed-By: Ryan Pavlik 
Closes: 997239
Changes:
 monado (21.0.0~dfsg1-2) unstable; urgency=medium
 .
   * d/control
 - Add Build-Depends on libbsd-dev for pidfile support when
   building service.
 - Bump Standards-Version to 4.6.0, no changes required.
 - Remove Build-Depends that we don't actually use.
 - Exclude some dependencies on less-common arches to fix builds.
   * d/copyright: Update
   * Backport patch for upstream to fix FTBFS, closes: #997239
   * Clean up/annotate patches
   * Switch to pandoc from markdown for formatting changelog.
Checksums-Sha1:
 98573d2028eb3e9601a851b5dac41bb4f73718ea  monado_21.0.0~dfsg1-2.dsc
 8bcc290a7cab9c81dc3

Bug#997075: marked as done (progress-linux-gnome-desktop: depends on GNOME Shell extensions that no longer work)

[Debian Bug Tracking System]

Your message dated Wed, 27 Oct 2021 06:48:42 +
with message-id 
and subject line Bug#997075: fixed in progress-linux-metapackages 20211008-2
has caused the Debian Bug report #997075,
regarding progress-linux-gnome-desktop: depends on GNOME Shell extensions that 
no longer work
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.)


-- 
997075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: progress-linux-gnome-desktop
Version: 20211008-1
Severity: serious
Justification: cannot migrate to testing with these dependencies in place
Control: block 993577 by -1

Similar to bfh-gnome-desktop, progress-linux-gnome-desktop Depends on
gnome-shell-extension-remove-dropdown-arrows, which is no longer relevant
for GNOME Shell >= 40 (which doesn't have arrows on drop-down menus
anyway) and as a result is being removed from unstable. Please drop
the dependency, or maybe change it to something like

Depends: gnome-shell (>= 40) | gnome-shell-extension-remove-dropdown-arrows

if compatibility with older Debian is desired.

It also Depends on gnome-shell-extension-hide-activities and
gnome-shell-extension-multi-monitors, which have not been updated for
GNOME 41 (#996061, #996066). Please drop those dependencies, or relax them
to Recommends or Suggests, or help to update those extensions if they are
important to you.

In general it is probably better to use Recommends rather than Depends
for any non-critical GNOME Shell extension. GNOME Shell does not have a
stable extension API, so all extensions potentially need updating every
6 months for compatibility with the new GNOME Shell version, and will
be removed from testing if they are not updated.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: progress-linux-metapackages
Source-Version: 20211008-2
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
progress-linux-metapackages 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, 27 Oct 2021 08:25:57 +0200
Source: progress-linux-metapackages
Architecture: source
Version: 20211008-2
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 997075
Changes:
 progress-linux-metapackages (20211008-2) sid; urgency=medium
 .
   * Uploading to sid.
   * Adding needrestart to progress-linux-base-system depends.
   * Removing gnome-shell-extension-remove-dropdown-arrows, not needed
 anymore with newer GNOME (Closes: #997075).
   * Dropping pre-bookworm hardlink depends in bfh-base-system.
Checksums-Sha1:
 a9463f798c145df3f3e7606976e3e0c860fc9671 2768 
progress-linux-metapackages_20211008-2.dsc
 b13d5ba1d3161f35df83c1dd8ebb10240ee17f41 6280 
progress-linux-metapackages_20211008-2.debian.tar.xz
 e9fe13f27d98ca8ac6f62f2ba37ab9524a0160f3 8759 
progress-linux-metapackages_20211008-2_amd64.buildinfo
Checksums-Sha256:
 556a9f4a351bb1fe75ba60c5ecc3e8d920b37105c7a69fef787b28b8324c94d3 2768 
progress-linux-metapackages_20211008-2.dsc
 a5ea3cedde376d6a7870b3622a1a9ee543f53fc8ed4b6c164aca3bbcec9d4234 6280 
progress-linux-metapackages_20211008-2.debian.tar.xz
 c0b9d81689ef8a371e0dd7552d64833f3f25a16c13b99f501183a57480117949 8759 
progress-linux-metapackages_20211008-2_amd64.buildinfo
Files:
 8fae4cc9b27412082c922e6b4ed965e4 2768 metapackages optional 
progress-linux-metapackages_20211008-2.dsc
 2aeccf6a56071046f150bd5f3a75c65a 6280 metapackages optional 
progress-linux-metapackages_20211008-2.debian.tar.xz
 046c40078ab42db068b4bf5923d4a9a1 8759 metapackages optional 
progress-linux-metapackages_20211008-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmF48S4ACgkQVc8b+Yar
uccjtA//QVoeISyS0LdOWq25mS8tb1VUIfMN18WRN5x8E5MbC7jKeHmCuaWfr9iE
goSEXhOXGXVkMnz6usPlu1IR669O+KdEpz8bKCea6vJjAIsS5mPQGvXlvQpmtb6z
XcSa3+ka1CmxkbsYJXdgW5P6CzBewI6xZN3xmsKGTkpOs5wvBfO7OcVmLeSl

Bug#997074: marked as done (bfh-gnome-desktop: depends on GNOME Shell extensions that no longer work)

[Debian Bug Tracking System]

Your message dated Wed, 27 Oct 2021 06:48:28 +
with message-id 
and subject line Bug#997074: fixed in bfh-metapackages 20211009-2
has caused the Debian Bug report #997074,
regarding bfh-gnome-desktop: depends on GNOME Shell extensions that no longer 
work
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.)


-- 
997074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bfh-gnome-desktop
Version: 20211009-1
Severity: serious
Justification: cannot migrate to testing with these dependencies in place
Control: block 993577 by -1

bfh-gnome-desktop Depends on gnome-shell-extension-remove-dropdown-arrows,
which is no longer relevant for GNOME Shell >= 40 (which doesn't have arrows
on drop-down menus anyway) and as a result is being removed from unstable.
Please drop the dependency, or maybe change it to something like

Depends: gnome-shell (>= 40) | gnome-shell-extension-remove-dropdown-arrows

if compatibility with older Debian is desired.

It also Depends on gnome-shell-extension-hide-activities and
gnome-shell-extension-multi-monitors, which have not been updated for
GNOME 41 (#996061, #996066). Please drop those dependencies, or relax them
to Recommends or Suggests, or help to update those extensions if they are
important to you.

In general it is probably better to use Recommends rather than Depends for
any non-critical GNOME Shell extension. GNOME Shell does not have a stable
extension API, so all extensions potentially need updating every 6 months
for compatibility with the new GNOME Shell version.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: bfh-metapackages
Source-Version: 20211009-2
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated bfh-metapackages 
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, 27 Oct 2021 08:21:55 +0200
Source: bfh-metapackages
Architecture: source
Version: 20211009-2
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 997074
Changes:
 bfh-metapackages (20211009-2) sid; urgency=medium
 .
   * Uploading to sid.
   * Adding needrestart to bfh-base-system depends.
   * Removing gnome-shell-extension-remove-dropdown-arrows, not needed
 anymore with newer GNOME (Closes: #997074).
   * Dropping pre-bookworm hardlink depends in bfh-base-system.
Checksums-Sha1:
 b724f6cff2a7b76f697a8450fb23c90d24f98ad6 2417 bfh-metapackages_20211009-2.dsc
 6d21b0510b0db5e4485f91b84f441c3d53bd5c58 4568 
bfh-metapackages_20211009-2.debian.tar.xz
 0aabcc77daa40f0067d8a46e78e56d0fc09d0677 8074 
bfh-metapackages_20211009-2_amd64.buildinfo
Checksums-Sha256:
 b6a115a2cc24ec0f44b506be79c5741e063f06ea59f7b0bc6bb5ae3a21a594da 2417 
bfh-metapackages_20211009-2.dsc
 004d69863887bba72868c10818a7206c491ae85b48b66b4bc6c02b87c3647e7d 4568 
bfh-metapackages_20211009-2.debian.tar.xz
 228636724f937ddc12b00bf91f75f5e61fdfb708eaf05f5c543786407c4d3f0f 8074 
bfh-metapackages_20211009-2_amd64.buildinfo
Files:
 f5e35db61ffcb3d3c0ee80c1f618c390 2417 metapackages optional 
bfh-metapackages_20211009-2.dsc
 2456f7c6fdb58c2b10d1700582aac71c 4568 metapackages optional 
bfh-metapackages_20211009-2.debian.tar.xz
 b8e0a3998e61217650412fd0e770cf2a 8074 metapackages optional 
bfh-metapackages_20211009-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmF48EQACgkQVc8b+Yar
ucf0zw//evR5YJSVyECsMyRtba6+dC9N5Y5vdqTTuPOhhc/XOUjvrD/VBzVLEs8B
yIJ+lsmXJVXXurpWAG6Niy7swtOV+n1Ew3FU+oFcZviyu8jklE+0viEEUwnBNekJ
s2oGYbokhTKhZzKZdzQHUveIgcmtvHMuNfcTeXsWHxtv+hpprwbPXZ/uGzv78Heg
swxcZRCuXVMAfBnkcn6ywBmIRmCMYExkAYi14RLABiXdf4JjIt99oURnrChCYuua
NVlub/qvFTvw7hPZe9YyQmae2qZLdU/nIFeryA8Dyr8dY5+ssgtWjdFbGE1ldG8T
g6SWdeIYPcXtpIWfg80v6zuGrcCODn1+zb9kiXB0Tpkx+eFuz99JjwFTAb5ZI4JY
wGXtcseLbHhaKoniztRQ/V/YTm+L+124LL+nXFadYyFvGollniuOin+dEhpDtU++
+O6IJbOiLfxvOcUnUcVOcptqgJsOVS5Ohb

Processed: gnunet 0.15 in NEW

[Debian Bug Tracking System]

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

> tag 997368 pending
Bug #997368 [src:gnunet-fuse] gnunet-fuse: FTBFS: Errors while processing:  
gnunet  gnunet-dev sbuild-build-depends-main-dummy
Added tag(s) pending.
> retitle 997368 FTBFS in sid
Bug #997368 [src:gnunet-fuse] gnunet-fuse: FTBFS: Errors while processing:  
gnunet  gnunet-dev sbuild-build-depends-main-dummy
Changed Bug title to 'FTBFS in sid' from 'gnunet-fuse: FTBFS: Errors while 
processing:  gnunet  gnunet-dev sbuild-build-depends-main-dummy'.
> tag 997306 pending
Bug #997306 [src:gnunet-gtk] gnunet-gtk: FTBFS: Errors while processing:  
gnunet  gnunet-dev sbuild-build-depends-main-dummy
Added tag(s) pending.
> retitle 997306 FTBFS in sid
Bug #997306 [src:gnunet-gtk] gnunet-gtk: FTBFS: Errors while processing:  
gnunet  gnunet-dev sbuild-build-depends-main-dummy
Changed Bug title to 'FTBFS in sid' from 'gnunet-gtk: FTBFS: Errors while 
processing:  gnunet  gnunet-dev sbuild-build-depends-main-dummy'.
> thanks
Stopping processing here.

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

Bug#997306: gnunet 0.15 in NEW

[Daniel Baumann]

tag 997368 pending
retitle 997368 FTBFS in sid
tag 997306 pending
retitle 997306 FTBFS in sid
thanks

Hi,

gnunet 0.15 is stuck in NEW, once it gets released.. i'll upload new 
gnunet-fuse/gnunet-gtk 0.15.


Regards,
Daniel

Bug#997884: libgclib breaks cdbfasta autopkgtest: ABI breakage

[Andreas Tille]

Hi Étienne,

thanks a lot for cleaning up the hassle I've created by naive upload.
I'm busy with real life this week - so feel free to upload.  Hope it
does not reside in new as long as other packages there.

Kind regards
Andreas.

Am Tue, Oct 26, 2021 at 10:46:26PM +0200 schrieb Étienne Mollier:
> Control: tags -1 confirmed
> 
> So, there is indeed an ABI breakage in libgclib.  I pushed some
> changes on Salsa to bump the SONAME to version 3 [1].  Since
> this would require a round trip through NEW, I also made some
> welcome updates to the copyright file.  I haven't uploaded yet,
> in case someone wishes to have a second look to make sure
> nothing is missing, notably in the copyright file, and I will
> try to recall to dput this tomorrow evening (UTC+2) if alright
> and not sponsored already.
> 
> [1]: https://salsa.debian.org/med-team/libgclib/
> 
> In hope this helps,
> Cheers,  :)
> -- 
> Étienne Mollier 
> Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
> Sent from /dev/pts/2, please excuse my verbosity.



> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Bug#997779: marked as done (node-retape: FTBFS: Error: Cannot find module 'test/test/fail-fast')

[Debian Bug Tracking System]

Your message dated Wed, 27 Oct 2021 05:03:32 +
with message-id 
and subject line Bug#997779: fixed in node-test 0.6.0-11
has caused the Debian Bug report #997779,
regarding node-retape: FTBFS: Error: Cannot find module 'test/test/fail-fast'
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.)


-- 
997779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-retape
Version: 0.0.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tap -R spec test/*.js
> 
> internal/modules/cjs/loader.js:818
>   throw err;
>   ^
> 
> Error: Cannot find module 'test/test/fail-fast'
> Require stack:
> - /<>/test/index.js
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:815:15)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/<>/test/index.js:3:29)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
> at Module.load (internal/modules/cjs/loader.js:863:32)
> at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> at Function.executeUserEntryPoint [as runMain] 
> (internal/modules/run_main.js:60:12) {
>   code: 'MODULE_NOT_FOUND',
>   requireStack: [ '/<>/test/index.js' ]
> }
> test/index.js
> 
>   1) test/index.js
> 
>   0 passing (95.969ms)
>   1 failing
> 
>   1) test/index.js test/index.js:
>  test/index.js
>   
> 
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-retape_0.0.3-4_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-test
Source-Version: 0.6.0-11
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-test 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, 27 Oct 2021 06:33:49 +0200
Source: node-test
Architecture: source
Version: 0.6.0-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 997779
Changes:
 node-test (0.6.0-11) unstable; urgency=medium
 .
   * Team upload
   * Override default install using debian/nodejs/files (Closes: #997779)
   * Add lintian overrides
Checksums-Sha1: 
 13bc31157f3e2ea83bfc88c7deca71ef68107aaf 2056 node-test_0.6.0-11.dsc
 7df7ec4d46e4a430c55ed75cc15b1437f0db52d4 4996 node-test_0.6.0-11.debian.tar.xz
Checksums-Sha256: 
 f4d0d099132d1b3d364d1a4bb49c16060d28c99fb27c7915faad1d2977e849b7 2056 
node-test_0.6.0-11.dsc
 5c8be7236e731f82e00d8da62654684edfe2467df3c87d4d32778c2a898b8b3f 4996 
node-test_0.6.0-11.debian.tar.xz
Files: 
 9f78f2ce181ecf9fb2731e0cd5a6e8de 2056 javascript optional 
node-test_0.6.0-11.dsc
 1f3214935ee6981ea3a8dfa27e7d9d13 4996 javascript optional 
node-test_0.6.0-11.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmF42GEACgkQ9tdMp8mZ
7ulqWw//ZBwlYItdmP3yr+LsQ7I4ldwfDlyLeNgGGHM9ksWxQpi2sDq1b0OQcqwK
2W1GfxSIGzNQKmPB2lDbeduHyH2/rQDCwPkxWCjL37yWXuYhk+nyDN7ezHTvWmPl
C121WF7H8ng6kS5Jq14eeh8SShBSG58RLmKL7ITy1YudiM0luIpgyKh9R6KLX9+H
ApPhzRlSgefNou3

Bug#997779: marked as pending in node-test

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-test/-/commit/c53bffd99a5df3ea459d5676a93f0099f8ce487a


Override default install using debian/nodejs/files

Closes: #997779


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997779

Processed: Bug#997779 marked as pending in node-test

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997779 [node-test] node-retape: FTBFS: Error: Cannot find module 
'test/test/fail-fast'
Added tag(s) pending.

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

Processed: affects 997779

[Debian Bug Tracking System]

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

> affects 997779 node-retape
Bug #997779 [node-test] node-retape: FTBFS: Error: Cannot find module 
'test/test/fail-fast'
Added indication that 997779 affects node-retape
> thanks
Stopping processing here.

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

Processed: reassign 997779 to node-test, found 997779 in 0.6.0-10

[Debian Bug Tracking System]

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

> reassign 997779 node-test
Bug #997779 [src:node-retape] node-retape: FTBFS: Error: Cannot find module 
'test/test/fail-fast'
Bug reassigned from package 'src:node-retape' to 'node-test'.
No longer marked as found in versions node-retape/0.0.3-4.
Ignoring request to alter fixed versions of bug #997779 to the same values 
previously set
> found 997779 0.6.0-10
Bug #997779 [node-test] node-retape: FTBFS: Error: Cannot find module 
'test/test/fail-fast'
Marked as found in versions node-test/0.6.0-10.
> thanks
Stopping processing here.

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

Bug#984093: [Debian-med-packaging] libcifpp_1.0.1-4_amd64.changes REJECTED

[Étienne Mollier]

Hi Nilesh,

Nilesh Patra, on 2021-10-27:
> On 27 October 2021 2:54:02 am IST, "Étienne Mollier"  
> wrote:
> >Maarten, I'm sorry that the round trip to NEW I contributed to
> >trigger stalled your package to not make it in the end.
> >On the good news side, now that the package cleared NEW
> ^
> 
> Uhh, sorry but I don't see how this "cleared" NEW? 1.0.1-4 has been rejected 
> from new, nor do I see any updates a tracker.d.o?
> 
> Do I miss something?

Sorry for the misunderstanding, I meant "cleared" as in "not in
NEW anymore", independently of whether it has been accepted or
rejected.

> And wouldn't new version of libcifpp undergo a proper library transition? -- 
> so is it not mandated for 1.0.1-4 to be accepted first?

At the time of writing, it seemed reasonable to me to transition
from 1.0.1-3, which is still in sid and testing, to 2.0.N-M.
But I might want to double check this at a more reasonable hour.
In any case, the transition would involve another round trip to
NEW, due to introduction of the new binary package libcifpp2
with the SONAME bump.

Thanks for your thoughs,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/tty1, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#992673: libgpuarray *gemv, *ger test fails

[Rebecca N. Palmer]

Control: tags -1 pending

(fixed in Salsa, as far as I consider it my bug)

It looks like both of these originate further down the stack, not in 
libgpuarray:


The *ger error code is an OpenCL compile failure from inside clblast, so 
likely either pocl or clblast.


The *gemv problem appears to be that the definition of gemv is 
y=alpha*A.dot(x)+beta*y, the spec allows and possibly requires the 
second term to be skipped entirely if beta is 0, clblas does this but 
clblast doesn't, and libgpuarray pygpu has a short form for beta=0 that 
uses an uninitialized (i.e. potentially NaN) y.  As a workaround I am 
changing this to a zero y, but it maybe should be fixed in clblast.

Bug#984093: [Debian-med-packaging] libcifpp_1.0.1-4_amd64.changes REJECTED

[Nilesh Patra]

Hi,

On 27 October 2021 2:54:02 am IST, "Étienne Mollier"  
wrote:
>Maarten, I'm sorry that the round trip to NEW I contributed to
>trigger stalled your package to not make it in the end.
>On the good news side, now that the package cleared NEW
^

Uhh, sorry but I don't see how this "cleared" NEW? 1.0.1-4 has been rejected 
from new, nor do I see any updates a tracker.d.o?

Do I miss something?

And wouldn't new version of libcifpp undergo a proper library transition? -- so 
is it not mandated for 1.0.1-4 to be accepted first?

Nilesh

Bug#997899: src:slurm-wlm: fails to migrate to testing for too long: piuparts regression and unresolved RC bug

[Andreas Beckmann]

The piuparts regression is

https://piuparts.debian.org/sid/source/s/slurm-wlm.html

0m23.7s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp5ugph549', '/usr/sbin/logrotate', 
'/etc/logrotate.d/slurmctld']
0m23.7s DUMP:
  /etc/logrotate.d/slurmctld:12 keyword 'size' not properly separated, found 
0x3d
0m23.7s DEBUG: Command ok: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp5ugph549', '/usr/sbin/logrotate', 
'/etc/logrotate.d/slurmctld']
0m23.7s ERROR: FAIL: Logrotate file /etc/logrotate.d/slurmctld exits with error 
or has output with package removed

i.e. logrotate does not like the conffile.
I'd expect that to happen with the package installed, too.


Andreas

Bug#984093: libcifpp_1.0.1-4_amd64.changes REJECTED

[Étienne Mollier]

Hi Thorsten, Hi Maarten,

Thorsten Alteholz, on 2021-10-26:
> please update the links in the PDB license block in your debian/copyright. 
> They don't seem to be valid anymore.
> 
> This is one of the reasons why all license information should be added to the 
> package.

Thanks Thorsten for your review!  Indeed the links are broken.
If I trust the Usage & Privacy page of RCSB Protein Data
Bank [1] (may this URL last a few years):
>> The wwPDB policy states that data files contained in the PDB
>> archive are available under the CC0 1.0 Universal (CC0 1.0)
>> Public Domain Dedication.
So this won't be a blocker in upcoming uploads with updated
copyright files hopefully.

[1]: https://www.rcsb.org/pages/policies

Maarten, I'm sorry that the round trip to NEW I contributed to
trigger stalled your package to not make it in the end.  On the
good news side, now that the package cleared NEW, you should
have free hands to move further on libcifpp 2 at your
convenience.

I cc'ed #984093 to postpone autoremoval of libcifpp and reduce
the time pressure.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#997884: libgclib breaks cdbfasta autopkgtest: ABI breakage

[Étienne Mollier]

Control: tags -1 confirmed

So, there is indeed an ABI breakage in libgclib.  I pushed some
changes on Salsa to bump the SONAME to version 3 [1].  Since
this would require a round trip through NEW, I also made some
welcome updates to the copyright file.  I haven't uploaded yet,
in case someone wishes to have a second look to make sure
nothing is missing, notably in the copyright file, and I will
try to recall to dput this tomorrow evening (UTC+2) if alright
and not sponsored already.

[1]: https://salsa.debian.org/med-team/libgclib/

In hope this helps,
Cheers,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#997909: marked as done (xapian-bindings: FTBFS with ruby3.0: diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 27 Oct 2021 00:18:41 +
with message-id 
and subject line Bug#997909: fixed in xapian-bindings 1.4.18-2
has caused the Debian Bug report #997909,
regarding xapian-bindings: FTBFS with ruby3.0: diff: 
debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or directory
to be marked as done.

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

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


-- 
997909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xapian-bindings
Version: 1.4.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, xapian-bindings was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> make[7]: Entering directory '/<>/debian/build/ruby2.7/ruby'
> rm -f 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.7.0/_xapian.la
> make[7]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[6]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[5]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[4]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[3]: Leaving directory '/<>/debian/build/ruby2.7'
> make[2]: Leaving directory '/<>/debian/build/ruby2.7'
> # `created.rid` contains a timestamp making the build non-reproducible.
> # It doesn't seem to be useful to install, so just delete it.
> rm -f debian/tmp/usr/share/doc/xapian-bindings-ruby*/ruby/rdocs/created.rid
> # We only need one xapian.rb for ruby-xapian, and it should be the same
> # for all versions, so if present, check that the older versions are
> # the same as the latest, then throw them away.  Also, delete the older
> # versions of the docs - the latest docs are installed by
> # ruby-xapian.install.
> rb=debian/tmp`/usr/bin/ruby3.0 -rrbconfig -e 'puts 
> RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
> for v in 2.7; do \
> if [ "$v" != "3.0" ] ; then \
>   set -e; \
>   rb_old=debian/tmp`/usr/bin/ruby$v -rrbconfig -e 'puts 
> RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
>   diff "$rb_old" "$rb"; \
>   rm -rf "$rb_old" debian/tmp/usr/share/doc/xapian-bindings-ruby$v; \
> fi; \
> done; \
> mv "$rb" debian/tmp/usr/lib/ruby/vendor_ruby
> diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or 
> directory
> make[1]: *** [debian/rules:359: override_dh_auto_install] Error 2


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/4/xapian-bindings/xapian-bindings_1.4.18-1+rebuild1635263761_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xapian-bindings
Source-Version: 1.4.18-2
Done: Olly Betts 

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated xapian-bindings 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, 27 Oct 2021 12:09:47 +1300
Source: xapian-bindings
Architecture: source
Version: 1.4.18-2
Distribution: unstable
Urgency: medium
Maintainer: Olly Betts 
Changed-By: Olly Betts 
Closes: 997909
Changes:
 xapian-bindings (1.4.18-2) unstable; urgency=medium
 .
   * debian/rules: Fix to work with Ruby 3.0. (Closes: #997909)
Checksums-Sha1:
 3ebbb3a12f70754f1d29897a727fd3c11683dca9 2713 xapian-bindings_1.4.18-2.dsc
 619140867cbd3f01fa83ea2860e42130e5d71c80 22436 
xapian-bindings_1.4.18-2.debian.tar.xz
 466028b63ac0da92ab15db47cc1df32f066da88a 15247 
xapian-bindings_1.4.18-2_amd64.buildinfo
Checksums-Sha256:
 89b3abd8bca972d2f06d63c10161f352b565338cc7692684653bb61523ac71b8 2713 
xapian-bindings_1.4.18-2.dsc
 755302474c0a372e7fc4891278fb9c54e5b5276861bb28a64542a3ab49838dc9 22436 
xapian-bindings_1.4.18-2.debian.tar.xz
 348e6afcabcc46947a7e32a094dfaecce00cf743661e1de1550

Bug#997909: xapian-bindings: FTBFS with ruby3.0: diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or directory

[Olly Betts]

On Tue, Oct 26, 2021 at 06:34:06PM -0300, Antonio Terceiro wrote:
> > rb=debian/tmp`/usr/bin/ruby3.0 -rrbconfig -e 'puts 
> > RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
> > for v in 2.7; do \
> > if [ "$v" != "3.0" ] ; then \
> > set -e; \
> > rb_old=debian/tmp`/usr/bin/ruby$v -rrbconfig -e 'puts 
> > RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
> > diff "$rb_old" "$rb"; \
> > rm -rf "$rb_old" debian/tmp/usr/share/doc/xapian-bindings-ruby$v; \
> > fi; \
> > done; \
> > mv "$rb" debian/tmp/usr/lib/ruby/vendor_ruby
> > diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or 
> > directory
> > make[1]: *** [debian/rules:359: override_dh_auto_install] Error 2

I strongly suspect (but haven't yet tested) that the problem is simply
this hard-coded reference to the Ruby version starting `2.` in
debian/rules:

RUBY_VERSIONS := $(shell ruby -rruby_debian_dev -e 'print 
RubyDebianDev::RUBY_CONFIG_VERSION.values.grep(/^2\.[1-9]/).join(" ")')

I'll test the obvious fix there when I get a chance, but I know the
upstream code builds and works with Ruby 3.0, so please don't let
xapian-bindings hold up starting the transition.

Cheers,
Olly

Bug#997884: libgclib breaks cdbfasta autopkgtest: ABI breakage?

[Étienne Mollier]

Control: affects -1 src:gffread 0.12.1-4

Hi Paul,

On Tue, 26 Oct 2021 16:58:28 +0200 Paul Gevers  wrote:
> [1] https://qa.debian.org/excuses.php?package=libgclib
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/c/cdbfasta/16212088/log.gz
> 
> + cdbfasta ebola.fasta
> cdbfasta: symbol lookup error: cdbfasta: undefined symbol: _Z8GReallocPPvm
> autopkgtest [22:12:39]: test run-unit-tests

Thank you for the heads up!  This looks to also affect gffread
0.12.1-4 [2].  Looking that up…

[2]: 
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gffread/16212089/log.gz

Have a good evening,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/6, please excuse my verbosity.


signature.asc
Description: PGP signature

Processed: fixed in Salsa

[Debian Bug Tracking System]

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

> tags 997382 pending
Bug #997382 [src:theano] theano: FTBFS: AttributeError: 'Sphinx' object has no 
attribute 'add_stylesheet'
Added tag(s) pending.
> tags 997026 pending
Bug #997026 [src:libgpuarray] libgpuarray: FTBFS with sphinx 4.2.0
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: Re: libgpuarray *gemv, *ger test fails

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #992673 [src:libgpuarray] libgpuarray: *gemv broken on libclblast
Added tag(s) pending.

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

Processed: Re: Bug#997303: xandikos: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

[Debian Bug Tracking System]

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

> reassign 997303 python3-dulwich
Bug #997303 [src:xandikos] xandikos: FTBFS: dh_auto_test: error: pybuild --test 
-i python{version} -p 3.9 returned exit code 13
Bug reassigned from package 'src:xandikos' to 'python3-dulwich'.
No longer marked as found in versions xandikos/0.2.6-1.
Ignoring request to alter fixed versions of bug #997303 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#997902: llvm-toolchain-13: autopkgtest regression on amd64|arm64: debian/qualify-clang.sh: llvm manpage are missing (using llc as an example)

[Simon McVittie]

On Tue, 26 Oct 2021 at 21:54:51 +0200, Sylvestre Ledru wrote:
> Le 26/10/2021 à 20:57, Simon McVittie a écrit :
> > The check that is failing is
> >
> >> if test /usr/share/man/man1/llc-$VERSION.1.gz; then
> > but I assume this should have been something more like:
> > if ! test -f "/usr/share/man/man1/llc-$VERSION.1.gz"; then
> 
> hmm, bizarre, I fixed it before. I guess it has been removed during a
> merge?!

Looks like the version of "Bring back the llvm manpages (Closes: #995684)"
on the 12 branch is correct, but the version of that commit on the 13
branch is different and has this bug.

smcv

Bug#997909: xapian-bindings: FTBFS with ruby3.0: diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or directory

[Antonio Terceiro]

Source: xapian-bindings
Version: 1.4.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, xapian-bindings was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> make[7]: Entering directory '/<>/debian/build/ruby2.7/ruby'
> rm -f 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.7.0/_xapian.la
> make[7]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[6]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[5]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[4]: Leaving directory '/<>/debian/build/ruby2.7/ruby'
> make[3]: Leaving directory '/<>/debian/build/ruby2.7'
> make[2]: Leaving directory '/<>/debian/build/ruby2.7'
> # `created.rid` contains a timestamp making the build non-reproducible.
> # It doesn't seem to be useful to install, so just delete it.
> rm -f debian/tmp/usr/share/doc/xapian-bindings-ruby*/ruby/rdocs/created.rid
> # We only need one xapian.rb for ruby-xapian, and it should be the same
> # for all versions, so if present, check that the older versions are
> # the same as the latest, then throw them away.  Also, delete the older
> # versions of the docs - the latest docs are installed by
> # ruby-xapian.install.
> rb=debian/tmp`/usr/bin/ruby3.0 -rrbconfig -e 'puts 
> RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
> for v in 2.7; do \
> if [ "$v" != "3.0" ] ; then \
>   set -e; \
>   rb_old=debian/tmp`/usr/bin/ruby$v -rrbconfig -e 'puts 
> RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
>   diff "$rb_old" "$rb"; \
>   rm -rf "$rb_old" debian/tmp/usr/share/doc/xapian-bindings-ruby$v; \
> fi; \
> done; \
> mv "$rb" debian/tmp/usr/lib/ruby/vendor_ruby
> diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or 
> directory
> make[1]: *** [debian/rules:359: override_dh_auto_install] Error 2


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/4/xapian-bindings/xapian-bindings_1.4.18-1+rebuild1635263761_amd64.build.txt


signature.asc
Description: PGP signature

Bug#997065: marked as done (libpmemobj-cpp: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 21:18:34 +
with message-id 
and subject line Bug#997065: fixed in libpmemobj-cpp 1.13.0-3
has caused the Debian Bug report #997065,
regarding libpmemobj-cpp: FTBFS: test failed
to be marked as done.

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

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


-- 
997065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpmemobj-cpp
Version: 1.13.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bullseye

Hi,

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


Relevant part (hopefully):
> 
> 99% tests passed, 1 tests failed out of 1705
> 
> Total Test time (real) = 773.22 sec
> 
> The following tests FAILED:
>   499 - ringbuf_0_helgrind (Failed)
> Errors while running CTest
> make[1]: *** [debian/rules:23: override_dh_auto_test] Error 8


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libpmemobj-cpp_1.13.0-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libpmemobj-cpp
Source-Version: 1.13.0-3
Done: Adam Borowski 

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated libpmemobj-cpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Oct 2021 18:10:22 +0200
Source: libpmemobj-cpp
Architecture: source
Version: 1.13.0-3
Distribution: unstable
Urgency: medium
Maintainer: Adam Borowski 
Changed-By: Adam Borowski 
Closes: 997065
Changes:
 libpmemobj-cpp (1.13.0-3) unstable; urgency=medium
 .
   * Don't use libunwind for stack traces in the test suite, it fares poorly
 under valgrind.  Closes: #997065.
   * Enable riscv64.
   * Drop a copyright entry for rewritten check-license.
Checksums-Sha1:
 a387cd891b9ab298ded089337beecfb8668f59ae 2275 libpmemobj-cpp_1.13.0-3.dsc
 33dff3f5be3104addfac036060d1d8c58a558f9c 5344 
libpmemobj-cpp_1.13.0-3.debian.tar.xz
 f0f9fbabb6bed8ae1ffbce4e1425ce9153e942f4 10935 
libpmemobj-cpp_1.13.0-3_source.buildinfo
Checksums-Sha256:
 1f520673e00c383c2adb763764ee4da158f38246cd8b44a916dced6b826458c7 2275 
libpmemobj-cpp_1.13.0-3.dsc
 1da8af51c19a8d4bdf8003959c3670c39f93cc706fda734ad3ee9dae777a5a3d 5344 
libpmemobj-cpp_1.13.0-3.debian.tar.xz
 7bdddab477f5c145cee19ac39da1812a00717c54e57ee9f14c7b59a2494538f3 10935 
libpmemobj-cpp_1.13.0-3_source.buildinfo
Files:
 606ce59fc9741ff4e59e5da3b3f944de 2275 libs optional libpmemobj-cpp_1.13.0-3.dsc
 af1c265d204891823fbf0278ec07e2bb 5344 libs optional 
libpmemobj-cpp_1.13.0-3.debian.tar.xz
 5f20a5dea608f49290fb0c4c8c626f44 10935 libs optional 
libpmemobj-cpp_1.13.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmF4bXQACgkQweDZLphv
fH6MjhAAo4AG032vlh91oYNaThY/k7oUlZQOiYaQYGZH0OfMbExQcsKpelQwP79P
34Uolk54yWGLdxN59zzuHFRKBpA/zv7HudqNhgvo5sIkBGFlFdluylNtoRJcP0FF
OwQBgZFYH0uDcwtWI8TjW0gPCEwdoHEjUReiR+kBQ3LLMX0hjCHNKLsbSm9QWYKZ
uPHcGs1CKaj+XiXb2H52vgDnkaEBrSb6nstdJQdgeTLLN7pl4XuGDdjaUnG1ssLi
/fmKhnCGraIW1EztlD6HKjnhuFD4QeFk+TJXsP/8Ja0jH9wx5lBihnhWUEc/nxfN
nzWK2TtwcMM1rkbUpNzhgPKN/AdIzYMUPU5iI8HJ3rt/bzUM7Q0c9EyXd7DuVMvv
ZpeFf1+80CPUmAiY7A0L+vV/dVJVXrR7JUHon9HsvrGKm8beUokcDILnNpLiGUC/
OIjsaaNulHspg0BAg9WMczqwsdCJNE3/iv23lWc4ubCSaXPlz50mHr0EsOyrKxF1
NsLweFdqPKXvyceCn1kpZHVAa2uRC+6rA+f7nGF25ZKP9EjjLq6e31BfO4D/orBN
ZaQiNg7xqgaCymoMPZfdNaSIgmI3evUoWIYYnAgIfeqfEampoIKjwuaEdTQC0L1U
4hxjhq+wKDSW7Qq52mTcK0IsBAR77D9y266kXBxEG+QCerc+yj0=
=fTZE
-END PGP SIGNATURE

Processed: Re: Bug#997412

[Debian Bug Tracking System]

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

> owner 997412 !
Bug #997412 [src:opencc] opencc: FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file: see diff output below
Owner recorded as Gunnar Hjalmarsson .
>
End of message, stopping processing here.

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

Bug#995786: marked as done (mesa: FTBFS on i386 with llvm 13: ‘class llvm::TargetOptions’ has no member named ‘StackAlignmentOverride’)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 22:51:18 +0200
with message-id 
and subject line Re: mesa: FTBFS on i386 with llvm 13: ‘class 
llvm::TargetOptions’ has no member named ‘StackAlignmentOverride’
has caused the Debian Bug report #995786,
regarding mesa: FTBFS on i386 with llvm 13: ‘class llvm::TargetOptions’ has no 
member named ‘StackAlignmentOverride’
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.)


-- 
995786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa
Version: 21.2.3-1
Severity: serious
Tags: ftbfs fixed-upstream patch
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11940

https://buildd.debian.org/status/fetch.php?pkg=mesa&arch=i386&ver=21.2.3-1&stamp=1633351863&raw=0
> ../src/gallium/auxiliary/gallivm/lp_bld_misc.cpp: In function ‘LLVMBool 
> lp_build_create_jit_compiler_for_module(LLVMOpaqueExecutionEngine**, 
> lp_generated_code**, lp_cached_code*, LLVMModuleRef, 
> LLVMMCJITMemoryManagerRef, unsigned int, char**)’:
> ../src/gallium/auxiliary/gallivm/lp_bld_misc.cpp:354:12: error: ‘class 
> llvm::TargetOptions’ has no member named ‘StackAlignmentOverride’
>   354 |options.StackAlignmentOverride = 4;
>   |^~

This appears to be fixed in the upstream main branch by
.

smcv
--- End Message ---
--- Begin Message ---
Version: 21.2.3-2

Hi,

On Tue, 5 Oct 2021 17:11:33 +0100 Simon McVittie  wrote:
> Justification: fails to build from source (but built successfully in the past)

The current version builds on i386.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: libgclib breaks cdbfasta autopkgtest: ABI breakage

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added tag(s) confirmed.

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

Bug#997806: aom: possible ABI breakage; causes ffmpeg autopkgtests failures

[Boyuan Yang]

Hi,

On Sun, 24 Oct 2021 23:28:33 +0200 Sebastian Ramacher 
wrote:
> Source: aom
> Version: 1.0.0-errata1.avif-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> From ffmpeg's autopkgtest:
> | [libaom-av1 @ 0x55ab8a773940] Failed to initialize encoder: ABI version
mismatch

Given that libaom 3.2.0 just passed the NEW queue, there's really no benefit
on keeping version 1.0.0.errata1.avif and handling related ABI breaks. In
Debian Sid, I will revert to the old libaom version (the same as in Debian
Testing) and initiate a formal transition from libaom 1.x to libaom 3.x.

Thanks for the report and let me know if there are any further issues (e.g.,
issues related to transition).

Regards,
Boyuan Yang


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

Processed: Bug#997884 marked as pending in gclib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added tag(s) pending.

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

Bug#997884: marked as pending in gclib

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/libgclib/-/commit/6a7cf26e7c678154e34d54da703c59354ead5646


Bump libgclib soname

Closes: #997884


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997884

Bug#997741: marked as done (listparser: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 171))

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 20:35:32 +
with message-id 
and subject line Bug#997741: fixed in listparser 0.18-3
has caused the Debian Bug report #997741,
regarding listparser: FTBFS: There is a syntax error in your configuration 
file: invalid syntax (conf.py, line 171)
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.)


-- 
997741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: listparser
Version: 0.18-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. python3 -m sphinx -N -bhtml docs/ build/html
> Running Sphinx v4.2.0
> 
> Configuration error:
> There is a syntax error in your configuration file: invalid syntax (conf.py, 
> line 171)
> 
> make[1]: *** [debian/rules:7: execute_after_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/listparser_0.18-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: listparser
Source-Version: 0.18-3
Done: Henry-Nicolas Tourneur 

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

Debian distribution maintenance software
pp.
Henry-Nicolas Tourneur  (supplier of updated listparser 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Oct 2021 19:51:00 +
Source: listparser
Architecture: source
Version: 0.18-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Henry-Nicolas Tourneur 
Closes: 997741
Changes:
 listparser (0.18-3) unstable; urgency=medium
 .
   * d/salsa-ci.yml: disable aptly
   * d/control: bump Standards-Version to 4.6.0 (no changes needed)
   * d/patches: add fix_sphinx_error to fix an FTBFS (Closes: #997741)
Checksums-Sha1:
 68cb5abec066daeae3532d70fed5da7bc8db2299 2199 listparser_0.18-3.dsc
 98c6d26a8d4818a38a5050f1e9f72fdde5568381 3308 listparser_0.18-3.debian.tar.xz
 a44ac38bda8c84af8a64c550b7cb7ccece1bda83 7308 listparser_0.18-3_amd64.buildinfo
Checksums-Sha256:
 5a7f17e46dab7f827330c2b05603264d412ce936183a1e0943bf18e6df14be90 2199 
listparser_0.18-3.dsc
 6e9fb03db0d9ce587f103557584a00b40ee27a18f87baa3571d33bd8c33bf4e6 3308 
listparser_0.18-3.debian.tar.xz
 e1f0c03dccad82a730db32e844c4ccb801561cba9025b9822df1d204f3f56fb2 7308 
listparser_0.18-3_amd64.buildinfo
Files:
 6e91936cd62790dc09efb0d972094388 2199 python optional listparser_0.18-3.dsc
 54cbbd7439f5415c09735b257621fa2f 3308 python optional 
listparser_0.18-3.debian.tar.xz
 6797796eb12613442be18d33475b9ab8 7308 python optional 
listparser_0.18-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEENS+/LT+kHSXcqokQ3QyVlN+SbJAFAmF4Yd0QHGRlYmlhbkBu
aWx1eC5iZQAKCRDdDJWU35JskGlGD/4i8q4HvrBLa5vODPYZBBWnFa8Z779mtmFI
TV5EDOlzpGQaK62GC/ek78oFWIK/JFBmL5PvJvxZ+rMmtIvGcGmIZD4SakNFGE59
aL3idUV6jvRPGD9YT+bKpxQeXJ1+swZ6lxZybZgIBuUeAh5itB1btshyzD1X3E80
wz/MekLH/pFVOxiWsAf8YLVIFdSWeVaM3cRUEpYUz3jufqqBy/6dNs4WL8zOiG3L
AV2DWtEtMFQ14yP/R9kLdt9cODZtiTOZjMghO947eDkkxsS+4vq9pKlTu/LIK00Q
UK96M5ArULiYfHjfEzrtKIsRmqPGJNK9pafj/H4pCAX7hzNGZkt+gUHrdDEgYLCc
/Qmx4Qgml5ED5vPOCw4pgRoPD4xsCmY+MQR9J9BKbvX4aO+ycr1VU6r49k1IXs50
cWRi7LZfk8SojrGDhh2zLDOHAv44Flf93Fo5xjBbojSe2IYtP1Vf1OFAZVwwZ3Pl
bu/xvspBJUqINAGVxOjOpQP1jVw9pVg+sg0H+sd/iywYfKcPCQA8EC2Q4zPKD0qw
+06XNOO7UJp9uktBzOgFU3X5OcTsVuzPoHkBNtQIfyckCW8bg4v1lL71ocOVlziR
SiP21WDdxM8Nwkbupa8whegWxhYUAbQ9a1CdUYvuu2hrauLohdsw+

Bug#997902: llvm-toolchain-13: autopkgtest regression on amd64|arm64: debian/qualify-clang.sh: llvm manpage are missing (using llc as an example)

[Sylvestre Ledru]

Le 26/10/2021 à 20:57, Simon McVittie a écrit :
> Source: llvm-toolchain-13
> Version: 1:13.0.0-6
> Severity: serious
> Justification: Release Team policy
> Tags: patch
>
> The autopkgtest that uses debian/qualify-clang.sh seems to be failing.
> I think this is a bug in debian/qualify-clang.sh rather than a bug in
> the actual packages: /usr/share/man/man1/llc-13.1.gz does exist in
> llvm-13_*.deb.
>
> The check that is failing is
>
>> # Test #995684
>> if test /usr/share/man/man1/llc-$VERSION.1.gz; then
>> echo "llvm manpage are missing (using llc as an example)"
>> exit 1
>> fi
> but I assume this should have been something more like:
>
> 8<
> # Test #995684
> if ! test -f "/usr/share/man/man1/llc-$VERSION.1.gz"; then
> echo "llvm man pages are missing (using llc as an example)"
> exit 1
> fi
> 8<
>
> I would suggest running the autopkgtests and making sure they pass locally
> on at least one architecture before uploading a new version to unstable.
> If llvm-toolchain-13 is too big to build locally, porterboxes and
> experimental are also useful routes to get things tested.

hmm, bizarre, I fixed it before. I guess it has been removed during a
merge?!


S

Bug#997469: dh-python doesn't allow local connections via urllib

[Stefano Rivera]

Hi Ole (2021.10.26_11:38:38_-0700)
> All of that said, there's an easy option for you. If you know your
> package needs network access and you're confident that it's not going to
> try to access the internet, you can just 'export http_proxy=' in
> debian/rules, and that will suppress pybuild exporting http_proxy.

FWIW, applied a patch to document this.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: Bug#997469 marked as pending in dh-python

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997469 [dh-python] dh-python doesn't allow local connections via urllib
Added tag(s) pending.

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

Bug#997469: marked as pending in dh-python

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/tools/dh-python/-/commit/4153d8048c110cbed44f2bd302b6e6a08344828b


Document pybuild environment variables in pybuild(1) (closes: #997469)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997469

Bug#997147: marked as done (chroma: FTBFS: cursesdisplay.c:497:29: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 19:33:32 +
with message-id 
and subject line Bug#997147: fixed in chroma 1.19-1
has caused the Debian Bug report #997147,
regarding chroma: FTBFS: cursesdisplay.c:497:29: error: format not a string 
literal and no format arguments [-Werror=format-security]
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.)


-- 
997147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chroma
Version: 1.18-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -I/usr/include/SDL -D_GNU_SOURCE=1 
> -D_REENTRANT -I/usr/include/freetype2 -I/usr/include/libpng16 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DCHROMA_CURSES_HEADER=\ 
> -DCHROMA_DATA_DIR=\"/usr/share/chroma/\" -Wdate-time -D_FORTIFY_SOURCE=2  -c 
> -o cursesmenudisplay.o cursesmenudisplay.c
> cursesdisplay.c: In function ‘display_play’:
> cursesdisplay.c:497:29: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   497 | printw(buffer + x);
>   | ^~
> cursesmenudisplay.c: In function ‘menu_displayentry’:
> cursesmenudisplay.c:135:28: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   135 | mvprintw(y, x, buffer);
>   |^~
> cursesmenudisplay.c:151:28: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   151 | mvprintw(y, x, buffer);
>   |^~
> cursesmenudisplay.c:200:28: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   200 | mvprintw(y, x, buffer);
>   |^~
> cursesmenudisplay.c:211:28: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   211 | mvprintw(y, x, buffer);
>   |^~
> cursesmenudisplay.c: In function ‘menu_display’:
> cursesmenudisplay.c:360:32: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   360 | mvprintw(2, x, buffer);
>   |^~
> cursesmenudisplay.c:376:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   376 | mvprintw(y, x, pmenu->title);
>   | ^~~~
> cursesmenudisplay.c:390:36: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   390 | mvprintw(y, x, buffer);
>   |^~
> graphics.c: In function ‘graphics_loadimage’:
> graphics.c:427:34: warning: ‘__builtin___sprintf_chk’ may write a terminating 
> nul past the end of the destination [-Wformat-overflow=]
>   427 | sprintf(fullfilename, "%s%s%s", directory, "/", filename);
>   |  ^
> In file included from /usr/include/stdio.h:866,
>  from graphics.c:21:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:38:10: note: 
> ‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a 
> destination of size 4096
>38 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
>   |  ^~
>39 |   __bos (__s), __fmt, __va_arg_pack 
> ());
>   |   
> ~
> cc1: some warnings being treated as errors
> make[2]: *** [: cursesmenudisplay.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/chroma_1.18-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: chroma
Source-Version: 1.19-1
Done: Simon Tatham 

We believe that the bug you reported is fi

Processed: src:iwyu: fails to migrate to testing for too long: depends on llvm-toolchain-12

[Debian Bug Tracking System]

Processing control commands:

> close -1 8.16-1
Bug #997905 [src:iwyu] src:iwyu: fails to migrate to testing for too long: 
depends on llvm-toolchain-12
Marked as fixed in versions iwyu/8.16-1.
Bug #997905 [src:iwyu] src:iwyu: fails to migrate to testing for too long: 
depends on llvm-toolchain-12
Marked Bug as done

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

Bug#997905: src:iwyu: fails to migrate to testing for too long: depends on llvm-toolchain-12

[Paul Gevers]

Source: iwyu
Version: 8.15-2
Severity: serious
Control: close -1 8.16-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:iwyu has been trying to migrate for 73
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

@Sylvestre: we discussed llvm-toolchain-* the other day [3], can't you
build iwyu with llvm-toolchain-11 until -12 or -13 is ready?

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=iwyu
[3] https://lists.debian.org/debian-release/2021/10/msg00466.html



OpenPGP_signature
Description: OpenPGP digital signature

Bug#997902: llvm-toolchain-13: autopkgtest regression on amd64|arm64: debian/qualify-clang.sh: llvm manpage are missing (using llc as an example)

[Simon McVittie]

Source: llvm-toolchain-13
Version: 1:13.0.0-6
Severity: serious
Justification: Release Team policy
Tags: patch

The autopkgtest that uses debian/qualify-clang.sh seems to be failing.
I think this is a bug in debian/qualify-clang.sh rather than a bug in
the actual packages: /usr/share/man/man1/llc-13.1.gz does exist in
llvm-13_*.deb.

The check that is failing is

> # Test #995684
> if test /usr/share/man/man1/llc-$VERSION.1.gz; then
> echo "llvm manpage are missing (using llc as an example)"
> exit 1
> fi

but I assume this should have been something more like:

8<
# Test #995684
if ! test -f "/usr/share/man/man1/llc-$VERSION.1.gz"; then
echo "llvm man pages are missing (using llc as an example)"
exit 1
fi
8<

I would suggest running the autopkgtests and making sure they pass locally
on at least one architecture before uploading a new version to unstable.
If llvm-toolchain-13 is too big to build locally, porterboxes and
experimental are also useful routes to get things tested.

smcv

Bug#997900: src:golang-github-go-xorm-builder: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: golang-github-go-xorm-builder
Version: 0.3.3-2
Severity: serious
Control: close -1 0.3.3-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:golang-github-go-xorm-builder has been
trying to migrate for 73 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=golang-github-go-xorm-builder




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:golang-github-go-xorm-builder: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.3.3-3
Bug #997900 [src:golang-github-go-xorm-builder] 
src:golang-github-go-xorm-builder: fails to migrate to testing for too long: 
uploader built arch:all binaries
Marked as fixed in versions golang-github-go-xorm-builder/0.3.3-3.
Bug #997900 [src:golang-github-go-xorm-builder] 
src:golang-github-go-xorm-builder: fails to migrate to testing for too long: 
uploader built arch:all binaries
Marked Bug as done

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

Processed: src:slurm-wlm: fails to migrate to testing for too long: piuparts regression and unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 20.11.8-1
Bug #997899 [src:slurm-wlm] src:slurm-wlm: fails to migrate to testing for too 
long: piuparts regression and unresolved RC bug
Marked as fixed in versions slurm-wlm/20.11.8-1.
Bug #997899 [src:slurm-wlm] src:slurm-wlm: fails to migrate to testing for too 
long: piuparts regression and unresolved RC bug
Marked Bug as done
> block -1 by 997267
Bug #997899 {Done: Paul Gevers } [src:slurm-wlm] 
src:slurm-wlm: fails to migrate to testing for too long: piuparts regression 
and unresolved RC bug
997899 was not blocked by any bugs.
997899 was not blocking any bugs.
Added blocking bug(s) of 997899: 997267

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

Bug#997899: src:slurm-wlm: fails to migrate to testing for too long: piuparts regression and unresolved RC bug

[Paul Gevers]

Source: slurm-wlm
Version: 20.11.7+really20.11.4-2
Severity: serious
Control: close -1 20.11.8-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 997267

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:slurm-wlm has been trying to migrate for
63 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=slurm-wlm




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:etbemon: fails to migrate to testing for too long: FTBFS everywhere

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3.5-7
Bug #997898 [src:etbemon] src:etbemon: fails to migrate to testing for too 
long: FTBFS everywhere
The source 'etbemon' and version '1.3.5-7' do not appear to match any binary 
packages
Marked as fixed in versions etbemon/1.3.5-7.
Bug #997898 [src:etbemon] src:etbemon: fails to migrate to testing for too 
long: FTBFS everywhere
Marked Bug as done
> block -1 by 992896
Bug #997898 {Done: Paul Gevers } [src:etbemon] src:etbemon: 
fails to migrate to testing for too long: FTBFS everywhere
997898 was not blocked by any bugs.
997898 was not blocking any bugs.
Added blocking bug(s) of 997898: 992896

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

Bug#997898: src:etbemon: fails to migrate to testing for too long: FTBFS everywhere

[Paul Gevers]

Source: etbemon
Version: 1.3.5-6
Severity: serious
Control: close -1 1.3.5-7
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 992896

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:etbemon has been trying to migrate for 63
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=etbemon




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: libgclib breaks cdbfasta autopkgtest: ABI breakage?

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gffread 0.12.1-4
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added indication that 997884 affects src:gffread and 0.12.1-4

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

Bug#997469: dh-python doesn't allow local connections via urllib

[Stefano Rivera]

Control: notfound -1 dh-python/5.20211022.1

Not starting a reassign war, but also, this shouldn't block testing
migration of an unrelated version.

This is the expected behaviour of dh-python. It exports http_proxy,
https_proxy, and no_proxy environment variables.
https://salsa.debian.org/python-team/tools/dh-python/-/blob/ba1110c8700d8ce9b6027117d0f12df7cfb95471/pybuild#L53-67

These variables are hardly standardized, see for example:
https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/

But maybe we could improve them, possibly adding 127.0.0.1 to the
no_proxy list? But I could easily imagine that causing other packages to
fail, getting confused by the comma in no_proxy.

All of that said, there's an easy option for you. If you know your
package needs network access and you're confident that it's not going to
try to access the internet, you can just 'export http_proxy=' in
debian/rules, and that will suppress pybuild exporting http_proxy.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: Re: Bug#997469: dh-python doesn't allow local connections via urllib

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 dh-python/5.20211022.1
Bug #997469 [dh-python] dh-python doesn't allow local connections via urllib
No longer marked as found in versions dh-python/5.20211022.1.

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

Bug#996798: marked as done (llvm-toolchain-12: FTBFS on mipsel|powerpc since 1:12.0.1-10: undefined reference to `_Unwind_Resume' etc.)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 11:18:48 -0700
with message-id 

and subject line Re: llvm-toolchain-12: FTBFS on mipsel|powerpc since 
1:12.0.1-10: undefined reference to `_Unwind_Resume' etc.
has caused the Debian Bug report #996798,
regarding llvm-toolchain-12: FTBFS on mipsel|powerpc since 1:12.0.1-10: 
undefined reference to `_Unwind_Resume' etc.
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.)


-- 
996798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-12
Version: 1:12.0.1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

The restructuring in 1:12.0.1-10 seems to have caused a build regression
on mipsel, which I'm reporting as separate from #996796 because it
doesn't affect i386:

> [1050/1054] : && /<>/build-llvm/./bin/clang++ 
> --target=mipsel-unknown-linux-gnu -fPIC -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time 
> -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
> -Wwrite-strings -Wcast-qual -Wmissing-field-initializers 
> -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type 
> -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment 
> -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections  
> -O3 -DNDEBUG  -Wl,-z,relro -Wl,-z,defs -Wl,-z,nodelete  -nodefaultlibs 
> -shared -Wl,-soname,libc++abi.so.1 -o 
> /<>/build-llvm/lib/libc++abi.so.1.0 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_aux_runtime.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_default_handlers.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception_storage.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_handlers.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_vector.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_virtual.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_exception.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_stdexcept.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_typeinfo.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/abort_message.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/fallback_malloc.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/private_typeinfo.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_new_delete.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_personality.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_thread_atexit.cpp.o  -lpthread 
>  -lc && :
> FAILED: /<>/build-llvm/lib/libc++abi.so.1.0 
> : && /<>/build-llvm/./bin/clang++ 
> --target=mipsel-unknown-linux-gnu -fPIC -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time 
> -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
> -Wwrite-strings -Wcast-qual -Wmissing-field-initializers 
> -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type 
> -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment 
> -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections  
> -O3 -DNDEBUG  -Wl,-z,relro -Wl,-z,defs -Wl,-z,nodelete  -nodefaultlibs 
> -shared -Wl,-soname,libc++abi.so.1 -o 
> /<>/build-llvm/lib/libc++abi.so.1.0 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_aux_runtime.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_default_handlers.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception_storage.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_handlers.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_vector.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_virtual.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_exception.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_stdexcept.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_typeinfo.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/abort_message.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/fallback_malloc.cpp.o 
> libcxxabi/src/CMakeFiles/cxxabi_shared.dir/private_typeinfo.cpp.o

Bug#996734: src:nim: fails to migrate to testing for too long: ftbfs on armhf

[Nilesh Patra]

control: severity -1 important

Hi Paul,

Thanks for reporting

On Sun, 17 Oct 2021 21:52:24 +0200 Paul Gevers  wrote:

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.


The new version of nim (1.6.0) was uploaded some hours back by Federico, and it 
passes on armhf.
Hopefully, this version will migrate in a few days.

Since this bug is already fixed in unstable, it is causing a huge number of 
autoremovals,
so I'm decreasing the severity for time being, to avoid temporary and 
un-necessary testing removal noise. -- Hope that's OK

I will ping you once nim migrates, and either ask you to close this bug or take 
the liberaty to do so myself.

https://buildd.debian.org/status/fetch.php?pkg=nim&arch=armhf&ver=1.6.0-1&stamp=1635249411&raw=0

Thanks for your work,
Nilesh

Bug#997055: marked as done (gnome-builder does not start up (missing library))

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 18:00:10 +
with message-id 
and subject line Bug#996887: fixed in cmark 0.30.2-2
has caused the Debian Bug report #996887,
regarding gnome-builder does not start up (missing library)
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.)


-- 
996887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-builder
Version: 41.1-2

gnome-builder does not start and throws the following error message:

$ gnome-builder 
gnome-builder: error while loading shared libraries:
libcmark.so.0.30.1: cannot open shared object file: No such file or
directory

The corresponding library does not exist with this name. However, there
are other versions:

$ find /usr/lib -name "libcmark.*"
/usr/lib/x86_64-linux-gnu/pkgconfig/libcmark.pc
/usr/lib/x86_64-linux-gnu/libcmark.a
/usr/lib/x86_64-linux-gnu/libcmark.so
/usr/lib/x86_64-linux-gnu/libcmark.so.0.30.2

Creating a symlink libcmark.so.0.30.1 -> libcmark.so.0.30.2 works as a
workaround.

I am using Debian Sid on AMD64 with all recent package versions.
--- End Message ---
--- Begin Message ---
Source: cmark
Source-Version: 0.30.2-2
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated cmark 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, 20 Oct 2021 16:57:49 +0200
Source: cmark
Binary: cmark cmark-dbgsym libcmark-dev libcmark0.30.2 libcmark0.30.2-dbgsym
Architecture: source amd64
Version: 0.30.2-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 cmark  - CommonMark parsing and rendering program
 libcmark-dev - development files for CommonMark parsing and rendering library
 libcmark0.30.2 - CommonMark parsing and rendering library
Closes: 996887
Changes:
 cmark (0.30.2-2) unstable; urgency=medium
 .
   * fix build binary package libcmark0.30.2 (not libcmark0.30.1),
 and have it break recent broken release of libcmark0.30.1;
 closes: bug#996887:, thanks to Sebastian Ramacher
Checksums-Sha1:
 0d2c9a34225fd1cf2cfac7b1cc37d6d4270776de 1930 cmark_0.30.2-2.dsc
 5bca189ac2f45a1b2795d51b13cde681533ab7b7 10564 cmark_0.30.2-2.debian.tar.xz
 3642d175e367d663eb463ed89a68399a60b238c6 227556 cmark-dbgsym_0.30.2-2_amd64.deb
 e6b38cb772184e7b66eacd7e24b5304c45a27283 7916 cmark_0.30.2-2_amd64.buildinfo
 ad467b57a73f6d44d20b2975d456ebc29a3223d5 116868 cmark_0.30.2-2_amd64.deb
 f4bb320992d10836b472557d09251a9276c0e21a 136612 libcmark-dev_0.30.2-2_amd64.deb
 1b0e0edb5a741b47a36a86d61de8a4bae8b1 221644 
libcmark0.30.2-dbgsym_0.30.2-2_amd64.deb
 22fd84740e720ea85174333afcb83de6e8c37dea 115228 
libcmark0.30.2_0.30.2-2_amd64.deb
Checksums-Sha256:
 6200cc6d70c1422284d2b7757aeb2e36d4ace1aabdfc5550f69e62ab18195263 1930 
cmark_0.30.2-2.dsc
 f7e80ec466022f3968f8a44dc9af2735b626948a66222b1ffed480b5a5d845c3 10564 
cmark_0.30.2-2.debian.tar.xz
 cdb2ae8569e364d778565abf6a5127abc04df0e207fe267333d91436806ad005 227556 
cmark-dbgsym_0.30.2-2_amd64.deb
 bde78bfb2dfe8f961b7019a126108f9754b17712d41208dcbd90b4aacfea2451 7916 
cmark_0.30.2-2_amd64.buildinfo
 c1207ada2eff716eed26b324b532673e30c5d92d012b82c16f60b2c5609297f1 116868 
cmark_0.30.2-2_amd64.deb
 e37ca30dcdc962a04e359cbf1e4d71d7d2962040a54ddcf233fb1950c8048d3c 136612 
libcmark-dev_0.30.2-2_amd64.deb
 63f252d64b97df85d3ea263d2e9fb581697feee73af58f2f15721d66822ca296 221644 
libcmark0.30.2-dbgsym_0.30.2-2_amd64.deb
 db6936acc0008119fd4c25e2cc721fea3c0bf12c591a9cc88b3440e66566b299 115228 
libcmark0.30.2_0.30.2-2_amd64.deb
Files:
 c423b4bb3e2cbc8c24efb71431b1c572 1930 text optional cmark_0.30.2-2.dsc
 ce4dc8ea92dcd2fe4efaf90323012ef0 10564 text optional 
cmark_0.30.2-2.debian.tar.xz
 271647acc01ccf1b37f5c0fd82fa8f66 227556 debug optional 
cmark-dbgsym_0.30.2-2_amd64.deb
 83e04d62388c82cfa17fe0c78e3f8653 7916 text optional 
cmark_0.30.2-2_amd64.buildinfo
 9cfffcfd26ee616b725141d29cbdf8b5 11

Bug#996887: marked as done (libcmark0.30.1: 0.30.2 bumps SONAME without changing package name)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 18:00:10 +
with message-id 
and subject line Bug#996887: fixed in cmark 0.30.2-2
has caused the Debian Bug report #996887,
regarding libcmark0.30.1: 0.30.2 bumps SONAME without changing package name
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.)


-- 
996887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcmark0.30.1
Version: 0.30.2-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

$ objdump -x usr/lib/x86_64-linux-gnu/libcmark.so.0.30.2 | grep SONAME
  SONAME   libcmark.so.0.30.2

This change needs to be reflected in the package name.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cmark
Source-Version: 0.30.2-2
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated cmark 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, 20 Oct 2021 16:57:49 +0200
Source: cmark
Binary: cmark cmark-dbgsym libcmark-dev libcmark0.30.2 libcmark0.30.2-dbgsym
Architecture: source amd64
Version: 0.30.2-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 cmark  - CommonMark parsing and rendering program
 libcmark-dev - development files for CommonMark parsing and rendering library
 libcmark0.30.2 - CommonMark parsing and rendering library
Closes: 996887
Changes:
 cmark (0.30.2-2) unstable; urgency=medium
 .
   * fix build binary package libcmark0.30.2 (not libcmark0.30.1),
 and have it break recent broken release of libcmark0.30.1;
 closes: bug#996887:, thanks to Sebastian Ramacher
Checksums-Sha1:
 0d2c9a34225fd1cf2cfac7b1cc37d6d4270776de 1930 cmark_0.30.2-2.dsc
 5bca189ac2f45a1b2795d51b13cde681533ab7b7 10564 cmark_0.30.2-2.debian.tar.xz
 3642d175e367d663eb463ed89a68399a60b238c6 227556 cmark-dbgsym_0.30.2-2_amd64.deb
 e6b38cb772184e7b66eacd7e24b5304c45a27283 7916 cmark_0.30.2-2_amd64.buildinfo
 ad467b57a73f6d44d20b2975d456ebc29a3223d5 116868 cmark_0.30.2-2_amd64.deb
 f4bb320992d10836b472557d09251a9276c0e21a 136612 libcmark-dev_0.30.2-2_amd64.deb
 1b0e0edb5a741b47a36a86d61de8a4bae8b1 221644 
libcmark0.30.2-dbgsym_0.30.2-2_amd64.deb
 22fd84740e720ea85174333afcb83de6e8c37dea 115228 
libcmark0.30.2_0.30.2-2_amd64.deb
Checksums-Sha256:
 6200cc6d70c1422284d2b7757aeb2e36d4ace1aabdfc5550f69e62ab18195263 1930 
cmark_0.30.2-2.dsc
 f7e80ec466022f3968f8a44dc9af2735b626948a66222b1ffed480b5a5d845c3 10564 
cmark_0.30.2-2.debian.tar.xz
 cdb2ae8569e364d778565abf6a5127abc04df0e207fe267333d91436806ad005 227556 
cmark-dbgsym_0.30.2-2_amd64.deb
 bde78bfb2dfe8f961b7019a126108f9754b17712d41208dcbd90b4aacfea2451 7916 
cmark_0.30.2-2_amd64.buildinfo
 c1207ada2eff716eed26b324b532673e30c5d92d012b82c16f60b2c5609297f1 116868 
cmark_0.30.2-2_amd64.deb
 e37ca30dcdc962a04e359cbf1e4d71d7d2962040a54ddcf233fb1950c8048d3c 136612 
libcmark-dev_0.30.2-2_amd64.deb
 63f252d64b97df85d3ea263d2e9fb581697feee73af58f2f15721d66822ca296 221644 
libcmark0.30.2-dbgsym_0.30.2-2_amd64.deb
 db6936acc0008119fd4c25e2cc721fea3c0bf12c591a9cc88b3440e66566b299 115228 
libcmark0.30.2_0.30.2-2_amd64.deb
Files:
 c423b4bb3e2cbc8c24efb71431b1c572 1930 text optional cmark_0.30.2-2.dsc
 ce4dc8ea92dcd2fe4efaf90323012ef0 10564 text optional 
cmark_0.30.2-2.debian.tar.xz
 271647acc01ccf1b37f5c0fd82fa8f66 227556 debug optional 
cmark-dbgsym_0.30.2-2_amd64.deb
 83e04d62388c82cfa17fe0c78e3f8653 7916 text optional 
cmark_0.30.2-2_amd64.buildinfo
 9cfffcfd26ee616b725141d29cbdf8b5 116868 text optional cmark_0.30.2-2_amd64.deb
 c0cc7780bdd82e6d53ae769cb38b6dae 136612 libdevel optional 
libcmark-dev_0.30.2-2_amd64.deb
 c49bc9634f6a91de5c1b342d89e613a6 221644 debug optional 
libcmark0.30.2-dbgsym_0.30.2-2_amd64.deb
 e8c21dcb73ec2041ea3b554ae32de297 115228 libs optional 
libcmark0.30.2_0.30.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#984330: marked as done (sight: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 18:00:26 +
with message-id 
and subject line Bug#984330: fixed in sight 21.0.0-1
has caused the Debian Bug report #984330,
regarding sight: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
In file included from 
/<>/libs/core/fwData/include/fwData/Image.hpp:35,
 from /<>/libs/core/fwData/src/fwData/Image.cpp:23:
/<>/libs/core/fwTools/include/fwTools/DynamicType.hpp:51:17: note: 
declared here
   51 | FWTOOLS_API DynamicType(const DynamicType&);
  | ^~~
[ 29%] Building CXX object 
fwAtomsBoostIO/CMakeFiles/fwAtomsBoostIO.dir/src/fwAtomsBoostIO/Writer.cpp.o
cd /<>/obj-x86_64-linux-gnu/fwAtomsBoostIO && /usr/bin/c++ 
-DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK 
-DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOG_DYN_LINK -DBOOST_LOG_SETUP_DYN_LINK 
-DBOOST_REGEX_DYN_LINK -DBOOST_SPIRIT_USE_PHOENIX_V3 
-DBOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0 
-DBOOST_THREAD_DYN_LINK -DBOOST_THREAD_PROVIDES_FUTURE -DBOOST_THREAD_VERSION=2 
-DFWATOMSBOOSTIO_EXPORTS -DFWATOMSBOOSTIO_VER=\"0.1\" -DKEEP_OLD_SERVICE 
-DfwAtomsBoostIO_EXPORTS -I/<>/libs/io/fwAtomsBoostIO/include 
-I/<>/obj-x86_64-linux-gnu/fwAtomsBoostIO/include 
-I/<>/obj-x86_64-linux-gnu/pchCore/include/pchCore 
-I/<>/libs/core/fwAtoms/include 
-I/<>/obj-x86_64-linux-gnu/fwAtoms/include 
-I/<>/libs/core/fwCamp/include 
-I/<>/obj-x86_64-linux-gnu/fwCamp/include 
-I/<>/libs/core/fwCore/inc
 lude -I/<>/obj-x86_64-linux-gnu/fwCore/include 
-I/<>/libs/core/fwMemory/include 
-I/<>/obj-x86_64-linux-gnu/fwMemory/include 
-I/<>/libs/core/fwCom/include 
-I/<>/obj-x86_64-linux-gnu/fwCom/include 
-I/<>/libs/core/fwThread/include 
-I/<>/obj-x86_64-linux-gnu/fwThread/include 
-I/<>/libs/core/fwTools/include 
-I/<>/obj-x86_64-linux-gnu/fwTools/include 
-I/<>/libs/core/fwZip/include 
-I/<>/obj-x86_64-linux-gnu/fwZip/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC 
-fvisibility=hidden -fvisibility-inlines-hidden -march=sandybridge 
-mtune=generic -mfpmath=sse -fvisibility=hidden -fvisibility-inlines-hidden 
-Wall -Wextra -Wconversion -Wno-unused-parameter -Wno-ignored-qualifiers 
-std=gnu++17 -include "pch.hpp"  -Winvalid-pch -o CMakeFiles/fwAtom
 sBoostIO.dir/src/fwAtomsBoostIO/Writer.cpp.o -c 
/<>/libs/io/fwAtomsBoostIO/src/fwAtomsBoostIO/Writer.cpp
[ 29%] Building CXX object fwData/CMakeFiles/fwData.dir/src/fwData/Integer.cpp.o
cd /<>/obj-x86_64-linux-gnu/fwData && /usr/bin/c++ 
-DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK 
-DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOG_DYN_L

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 997894
Bug #997894 {Done: yokota } [pyqt5-sip] pyqt5-sip: 
appears to declare the wrong API version (should be 12.9)
Bug reopened
Ignoring request to alter fixed versions of bug #997894 to the same values 
previously set
> severity 997894 important
Bug #997894 [pyqt5-sip] pyqt5-sip: appears to declare the wrong API version 
(should be 12.9)
Severity set to 'important' from 'serious'
> affects 997894 calibre
Bug #997894 [pyqt5-sip] pyqt5-sip: appears to declare the wrong API version 
(should be 12.9)
Added indication that 997894 affects calibre
> thanks
Stopping processing here.

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

Bug#997894:

[Nicholas D Steeves]

reopen 997894
severity 997894 important
affects 997894 calibre
thanks

I'm downgrading severity to important as a humble courtesy, but if my
hypothesis is correct then it really is RC.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#984066: Processed: block 984066 with 987379

[Nicholas D Steeves]

Control: unblock -1 by 987379

> Processing commands for cont...@bugs.debian.org:
>
>> block 984066 with 987379
> Bug #984066 {Done: Adrian Bunk } [src:irony-mode] 
> irony-mode: ftbfs with GCC-11
> 984066 was not blocked by any bugs.
> 984066 was not blocking any bugs.
> Added blocking bug(s) of 984066: 987379
>> thanks

This block is incorrect, please see the following:

irony-mode (1.5.0-1) unstable; urgency=medium

  * New upstream release.
  * Update my email address.
  * Switch to llvm-toolchain-12, and build with libclang-12-dev, clang-12,
and llvm-12-dev.
  * Switch to watch file v4 (no further changes required).

 -- Nicholas D Steeves   Wed, 15 Sep 2021 16:56:37 -0400

Additionally, I think it may be a better use of time to focus on
stabilising llvm-toolchain-13 rather than 11 and 12.  Of course, that's
not my call, but I'd like to do what I can to support the effort to ship
fewer llvm-toolchain-versions in bookwork.  Consequently I will be
moving this package to version 13 at some point in the near future.

Also, on the upstream bug tracker, users have expressed the desire to
have a Debian irony-mode package that uses the newest Clang available on
Debian systems, so there is a concrete "for our users" reason to do this.

I hope that this position is acceptable to everyone! :-)

Regards,
Nicholas


signature.asc
Description: PGP signature

Processed: Re: Processed: block 984066 with 987379

[Debian Bug Tracking System]

Processing control commands:

> unblock -1 by 987379
Bug #984066 {Done: Adrian Bunk } [src:irony-mode] irony-mode: 
ftbfs with GCC-11
984066 was blocked by: 987379
984066 was not blocking any bugs.
Removed blocking bug(s) of 984066: 987379

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

Bug#997655: diodon: FTBFS: autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?

[Oliver Sauder]

Lucas,
Thanks for reporting. This issue has actually been resolved upstream but
it seems that I uploaded an invalid orig tarball for version 1.11.1 for
the Debian package. Instead of the new upstream tarball 1.11.1, 1.11.0
was still used (when opening the tarball from [0] the folder name is
still 1.11.0). Not so sure how this happened. Upstream tarball [1] is
correct though.

Do you know a way to fix the invalid orig tarball without a new release
upstream?

Oliver

[0]
http://deb.debian.org/debian/pool/main/d/diodon/diodon_1.11.1.orig.tar.xz
[1] https://launchpad.net/diodon/trunk/1.11.1/+download/diodon-1.11.1.tar.xz

Processed: your mail

[Debian Bug Tracking System]

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

> clone 997660 -1
Bug #997660 {Done: yokota } [src:calibre] calibre: 
FTBFS: -c: Unable to find file "QtWidgets/QtWidgetsmod.sip"
Bug 997660 cloned as bug 997894
> reassign -1 pyqt5-sip 12.9.0-1
Bug #997894 {Done: yokota } [src:calibre] calibre: 
FTBFS: -c: Unable to find file "QtWidgets/QtWidgetsmod.sip"
Bug reassigned from package 'src:calibre' to 'pyqt5-sip'.
No longer marked as found in versions calibre/5.30.0+dfsg-1 and 
calibre/5.29.0+dfsg-1.
Ignoring request to alter fixed versions of bug #997894 to the same values 
previously set
Bug #997894 {Done: yokota } [pyqt5-sip] calibre: FTBFS: 
-c: Unable to find file "QtWidgets/QtWidgetsmod.sip"
There is no source info for the package 'pyqt5-sip' at version '12.9.0-1' with 
architecture ''
Unable to make a source version for version '12.9.0-1'
Marked as found in versions 12.9.0-1.
> retitle -1 pyqt5-sip: appears to declare the wrong API version (should be 
> 12.9)
Bug #997894 {Done: yokota } [pyqt5-sip] calibre: FTBFS: 
-c: Unable to find file "QtWidgets/QtWidgetsmod.sip"
Changed Bug title to 'pyqt5-sip: appears to declare the wrong API version 
(should be 12.9)' from 'calibre: FTBFS: -c: Unable to find file 
"QtWidgets/QtWidgetsmod.sip"'.
> thanks
Stopping processing here.

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

Processed: block 984066 with 987379

[Debian Bug Tracking System]

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

> block 984066 with 987379
Bug #984066 {Done: Adrian Bunk } [src:irony-mode] irony-mode: 
ftbfs with GCC-11
984066 was not blocked by any bugs.
984066 was not blocking any bugs.
Added blocking bug(s) of 984066: 987379
> thanks
Stopping processing here.

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

Processed: block 984016 with 996589

[Debian Bug Tracking System]

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

> block 984016 with 996589
Bug #984016 {Done: Adrian Bunk } [src:cloudcompare] 
cloudcompare: ftbfs with GCC-11
984016 was not blocked by any bugs.
984016 was not blocking any bugs.
Added blocking bug(s) of 984016: 996589
> thanks
Stopping processing here.

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

Bug#996887: tldr also affected

[Diederik de Haas]

Control: affects -1 + tldr

Got the same error msg when running tldr. Downgrading to the testing version 
fixed it (aptitude install libcmark0.30.1=0.30.1-2).

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

Processed: tldr also affected

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + tldr
Bug #996887 [libcmark0.30.1] libcmark0.30.1: 0.30.2 bumps SONAME without 
changing package name
Bug #997055 [libcmark0.30.1] gnome-builder does not start up (missing library)
Added indication that 996887 affects tldr
Added indication that 997055 affects tldr

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

Bug#997660: pyqt5-sip: appears to declare the wrong API version

[Nicholas D Steeves]

clone 997660 -1
reassign -1 pyqt5-sip 12.9.0-1
retitle -1 pyqt5-sip: appears to declare the wrong API version (should be 12.9)
thanks

Alex Relis  writes:

> I'm on version 5.30.0+dfsg-1 and I am still experiencing this bug. It hasn't 
> been fixed quite yet. Here's the error I seem to be getting:
>
> alex@alex-pc:~$ calibre
> Traceback (most recent call last):
>   File "/usr/bin/calibre", line 21, in 
> sys.exit(calibre())
>   File "/usr/lib/calibre/calibre/gui_launch.py", line 64, in calibre
> main(args)
>   File "/usr/lib/calibre/calibre/gui2/main.py", line 533, in main
> app, opts, args = init_qt(args)
>   File "/usr/lib/calibre/calibre/gui2/main.py", line 124, in init_qt
> app = Application(args, override_program_name=override, 
> windows_app_uid=MAIN_APP_UID)
>   File "/usr/lib/calibre/calibre/gui2/__init__.py", line 894, in __init__
> from calibre_extensions import progress_indicator
> RuntimeError: the sip module implements API v12.0 to v12.8 but the 
> progress_indicator module requires API v12.9
>
[snip]
> ii  python3-pyqt5.sip12.9.0-3

Hm, that is strange.  This string comes from pyqt5-sip/12.9.0-3:

siplib.c
1716:"the sip module implements API v%d.0 to v%d.%d but the 
%s module requires API v%d.%d",
1721:"the sip module implements API v%d.0 but the %s module 
requires API v%d.%d",

Thus, it seems like python3-pyqt5.sip may be misidentifying its
version.  The next step was to search for 12.8 strings:

sip.h
1656:PyObject *(*api_is_py_method_12_8)(sip_gilstate_t *gil, char *pymc,

siplib.c
319:static PyObject *sip_api_is_py_method_12_8(sip_gilstate_t *gil, char 
*pymc,
620:sip_api_is_py_method_12_8,
6030:meth = sip_api_is_py_method_12_8(&sipGILState, &pymc, &self, NULL,
8378: * sip_api_is_python_method_12_8() instead.
8383:return sip_api_is_py_method_12_8(gil, pymc, &sipSelf, cname, 
mname);
8391:static PyObject *sip_api_is_py_method_12_8(sip_gilstate_t *gil, char 
*pymc,

Dmitri, would you please take a look at this?  Apologies if I
naively misinterpreted this bug, feel free to bounce it back if
necessary.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#997802: ddnet: autopkgtest regression on armhf: output to stderr

[Graham Inggs]

On Sun, 24 Oct 2021 at 22:30, Paul Gevers  wrote:
> I copied some of the output at the bottom of this report. It seems that
> the actual test passes, but there's output on stderr and the default
> behavior of autopkgtest is to fail on output to stderr. If in general
> output to stderr is harmless to your test, consider adding the
> allow-stderr restriction. Otherwise, please fix your test.

The autopkgtest on ppc64el [1] also fails due to output on stderr.


[1] https://ci.debian.net/packages/d/ddnet/testing/ppc64el/


/tmp/autopkgtest-lxc.e6vtmdil/downtmp/build.Hvt/src/src/game/collision.cpp:
In member function ‘void CCollision::Init(CLayers*)’:
/tmp/autopkgtest-lxc.e6vtmdil/downtmp/build.Hvt/src/src/game/collision.cpp:66:10:
note: the layout of aggregates containing vectors with 8-byte
alignment has changed in GCC 5
   66 |  m_Width = m_pLayers->GameLayer()->m_Width;
  |  ^
[ 59%] Building CXX object CMakeFiles/game-shared.dir/src/game/extrainfo.cpp.o
[ 59%] Building CXX object CMakeFiles/game-shared.dir/src/game/gamecore.cpp.o
/tmp/autopkgtest-lxc.e6vtmdil/downtmp/build.Hvt/src/src/game/gamecore.cpp:
In member function ‘void CCharacterCore::Reset()’:
/tmp/autopkgtest-lxc.e6vtmdil/downtmp/build.Hvt/src/src/game/gamecore.cpp:70:6:
note: the layout of aggregates containing vectors with 2-byte
alignment has changed in GCC 5
   70 | void CCharacterCore::Reset()
  |  ^~
[ 62%] Building CXX object CMakeFiles/game-shared.dir/src/game/layers.cpp.o
[ 62%] Building CXX object
CMakeFiles/game-shared.dir/src/game/localization.cpp.o
/tmp/autopkgtest-lxc.e6vtmdil/downtmp/build.Hvt/src/src/game/localization.cpp:
In member function ‘void CLocalizationDatabase::AddString(const char*,
const char*, const char*)’:
/tmp/autopkgtest-lxc.e6vtmdil/downtmp/build.Hvt/src/src/game/localization.cpp:39:6:
note: the layout of aggregates containing vectors with 8-byte
alignment has changed in GCC 5
   39 | void CLocalizationDatabase::AddString(const char *pOrgStr,
const char *pNewStr, const char *pContext)
  |  ^

Bug#997660: calibre: Ah yes, I seem to be having this issue as well!

[Alex Relis]

Package: calibre
Version: 5.30.0+dfsg-1
Followup-For: Bug #997660

Dear Maintainer,

I'm on version 5.30.0+dfsg-1 and I am still experiencing this bug. It hasn't 
been fixed quite yet. Here's the error I seem to be getting:

alex@alex-pc:~$ calibre
Traceback (most recent call last):
  File "/usr/bin/calibre", line 21, in 
sys.exit(calibre())
  File "/usr/lib/calibre/calibre/gui_launch.py", line 64, in calibre
main(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 533, in main
app, opts, args = init_qt(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 124, in init_qt
app = Application(args, override_program_name=override, 
windows_app_uid=MAIN_APP_UID)
  File "/usr/lib/calibre/calibre/gui2/__init__.py", line 894, in __init__
from calibre_extensions import progress_indicator
RuntimeError: the sip module implements API v12.0 to v12.8 but the 
progress_indicator module requires API v12.9

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

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

Versions of packages calibre depends on:
ii  calibre-bin  5.30.0+dfsg-1
ii  dpkg 1.20.9
ii  fonts-liberation22.1.5-1
ii  imagemagick  8:6.9.11.60+dfsg-1.3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3
ii  libjpeg-turbo-progs  1:2.0.6-4
ii  libjxr-tools 1.1-6+b1
ii  optipng  0.7.7-2
ii  poppler-utils20.09.0-3.1
ii  python3  3.9.2-3
ii  python3-apsw 3.36.0-r1-2
ii  python3-bs4  4.10.0-2
ii  python3-chardet  4.0.0-1
ii  python3-chm  0.8.6-3
ii  python3-css-parser   1.0.6-1
ii  python3-cssselect1.1.0+ds-2
ii  python3-cssutils 1.0.2-3
ii  python3-dateutil 2.8.1-6
ii  python3-feedparser   5.2.1-3
ii  python3-html2text2020.1.16-1
ii  python3-html5-parser 0.4.10-1
ii  python3-html5lib 1.1-3
ii  python3-jeepney  0.6.0-1
ii  python3-lxml 4.6.3+dfsg-1
ii  python3-markdown 3.3.4-1
ii  python3-mechanize1:0.4.5-2
ii  python3-msgpack  1.0.2-2
ii  python3-netifaces0.11.0-1
ii  python3-pil  8.3.2-1
ii  python3-pkg-resources58.2.0-1
ii  python3-py7zr0.11.3+dfsg-1
ii  python3-pygments 2.7.1+dfsg-2.1
ii  python3-pyparsing2.4.7-1
ii  python3-pyqt55.15.5+dfsg-1
ii  python3-pyqt5.qtsvg  5.15.5+dfsg-1
ii  python3-pyqt5.qtwebengine5.15.5-1
ii  python3-pyqt5.sip12.9.0-3
ii  python3-regex0.1.20211008-1
ii  python3-routes   2.5.1-1
ii  python3-speechd  0.10.2-3
ii  python3-zeroconf 0.36.9-1
ii  python3.93.9.7-4
ii  xdg-utils1.1.3-4.1

Versions of packages calibre recommends:
ii  python3-dnspython  2.0.0-1
ii  python3-ipython7.22.0-1
ii  udisks22.9.4-1

Versions of packages calibre suggests:
ii  python3-openssl   21.0.0-1
pn  python3-unrardll  

-- no debconf information

Bug#997887: r-cran-effectsize: autopkgtest regression on ppc64el: machine precision issue?

[Paul Gevers]

Source: r-cran-effectsize
Version: 0.5-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of r-cran-effectsize the autopkgtest of
r-cran-effectsize fails in testing on ppc64el when that autopkgtest is
run with the binary packages of r-cran-effectsize from unstable. It
passes when run with only packages from testing. In tabular form:

   passfail
r-cran-effectsize  from testing0.5-1
all others from testingfrom testing

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

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-effectsize

https://ci.debian.net/data/autopkgtest/testing/ppc64el/r/r-cran-effectsize/16211124/log.gz

BEGIN TEST spelling.R

R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: powerpc64le-unknown-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> if (requireNamespace("spelling", quietly = TRUE)) {
+   spelling::spell_check_test(
+ vignettes = TRUE, error = FALSE,
+ skip_on_cran = TRUE
+   )
+ }
> 
BEGIN TEST testthat.R

R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: powerpc64le-unknown-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(testthat)
> library(effectsize)
> 
> test_check("effectsize")
Starting 2 test processes
══ Skipped tests
═══
• On CRAN (17)
• rstanarm cannot be loaded (1)

══ Failed tests

── Failure (test-eta_squared.R:89:5): aov
──
et1$CI_low (`actual`) not equal to et2$CI_low (`expected`).

  `actual`: 0.20996729 0.
`expected`: 0.20996728 0.

[ FAIL 1 | WARN 1 | SKIP 18 | PASS 467 ]
Error: Test failures
Execution halted
autopkgtest [22:31:26]: test run-unit-test




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#996510 marked as pending in ruby-spring

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996510 [src:ruby-spring] ruby-spring: FTBFS with ruby3.0: ERROR: Test 
"ruby3.0" failed: Errno::ENOENT: No such file or directory @ 
rb_check_realpath_internal - /tmp/d20211005-1582813-mce9ae
Added tag(s) pending.

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

Bug#996510: marked as pending in ruby-spring

[Cédric Boutillier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-spring/-/commit/4a46120e5e5de8270ce8e1c6effb0b8bd0ebf6eb


Fixes for ruby3.0 (Closes: #996510)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996510

Bug#997886: prottest: autopkgtest regression: Stats file does not exist

[Paul Gevers]

Source: prottest
Version: 3.4.2+dfsg-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
prottest   from testing3.4.2+dfsg-6
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/prottest/16225046/log.gz

-
Basic usage:  - Sequential version: java -jar prottest-3.4.2.jar
-i align_file [OPTIONS]
./prottest3 -i align_file [OPTIONS]
 - Parallel version: mpjrun.sh -wdir $PWD/ -np [NUM_PROCS] -jar
prottest-3.4.2.jar -i align_file [OPTIONS]
OPTIONS:
 -i alignment_filename
Alignment input file (required)
 -t tree_filename
Tree file   (optional) [default: NJ tree]
 -o output_filename
Output file (optional) [default: standard output]
 -log enabled/disabled
Enables / Disables PhyML logging into log directory (see
prottest.properties)
 -[matrix]
Include matrix (Amino-acid) = JTT LG DCMut MtREV MtMam MtArt
Dayhoff WAG   RtREV CpREV Blosum62 VT
HIVb HIVw FLU If you don't specify any matrix, all
matrices displayed above will
be included.
 -I
Include models with a proportion of invariable sites
 -G
Include models with rate variation among sites and number of
categories
 -IG
include models with both +I and +G properties
 -all-distributions
Include models with rate variation among sites, number of
categories and both
 -ncat number_of_categories
Define number of categories for +G and +I+G models [default: 4]
 -F
Include models with empirical frequency estimation  -AIC
Display models sorted by Akaike Information Criterion (AIC)
 -BIC
Display models sorted by Bayesian Information Criterion (BIC)
 -AICC
Display models sorted by Corrected Akaike Information
Criterion (AICc)
 -DT
Display models sorted by Decision Theory Criterion
 -all
Displays a 7-framework comparison table
 -S optimization_strategy
Optimization strategy mode: [default: 0]
0: Fixed BIONJ JTT
1: BIONJ Tree
2: Maximum Likelihood tree
3: User defined topology
 -s moves
Tree search operation for ML search: NNI
(fastest), SPR (slowest), BEST (best of NNI and SPR) [default: NNI]
 -t1
Display best-model's newick tree [default: false]
 -t2
Display best-model's ASCII tree  [default: false]
 -tc consensus_threshold Display consensus tree with the
specified threshold, between 0.5 and 1.0
[0.5 = majority rule consensus ; 1.0 = strict consensus]
 -threads number_or_threads 
Number of threads requested to compute (only if MPJ is not
used) [default: 1]
 -verbose
Verbose mode [default: false]
-
Example: - Sequential version:
java -jar prottest-3.4.2.jar -i align_file -t tree_file -S 0
-all-distributions -F -AIC -BIC -tc 0.5 > output
- Parallel version:
mpjrun.sh -wdir $PWD/ -np 2 -jar prottest-3.4.2.jar -i align_file -t
tree_file -S 0 -all-distributions -F -AIC -BIC -tc 0.5
PHYLIP format detected.MSA read in PHYLIP format (Taxa = 28, Length =
149).MSA successfully converted to PHYLIP format!

No such file or directory

--
ProtTest 3.4.2  Fast selection of the best-fit
models of protein evolution
(c) 2009-2016   Diego Darriba (1,2), Guillermo Taboada (2), Ramón Doallo
(2), David Posada (1)
(1)   Facultad de Biologia, Universidad de
Vigo, 36200 Vigo, Spain
(2)Facultade de Informática, Universidade da Coruña,
15071 A Coruña, Spain
--
Manual:
http://darwi

Processed: libgclib breaks cdbfasta autopkgtest: ABI breakage?

[Debian Bug Tracking System]

Processing control commands:

> found -1 libgclib/0.12.7+ds-2
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Marked as found in versions libgclib/0.12.7+ds-2.
> affects -1 src:cdbfasta
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added indication that 997884 affects src:cdbfasta

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

Bug#997885: python-moreorless: autopkgtest regression: No module named 'parameterized'

[Paul Gevers]

Source: python-moreorless
Version: 0.4.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
python-moreorless  from testing0.4.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looks like
you're missing a (test) dependency.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-moreorless/16207758/log.gz

=== testing with python3.9 ===
Traceback (most recent call last):
  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
  File
"/tmp/autopkgtest-lxc.tkseerp6/downtmp/autopkgtest_tmp/python-moreorless/tests/__main__.py",
line 4, in 
from .general import ParityTest  # noqa: F401
  File
"/tmp/autopkgtest-lxc.tkseerp6/downtmp/autopkgtest_tmp/python-moreorless/tests/general.py",
line 6, in 
from parameterized import parameterized
ModuleNotFoundError: No module named 'parameterized'
autopkgtest [19:14:08]: test unittests




OpenPGP_signature
Description: OpenPGP digital signature

Bug#997884: libgclib breaks cdbfasta autopkgtest: ABI breakage?

[Paul Gevers]

Source: libgclib
Control: found -1 libgclib/0.12.7+ds-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks
Control: affects -1 src:cdbfasta

Dear maintainer(s),

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

   passfail
libgclib   from testing0.12.7+ds-2
cdbfasta   from testing1.00+git20181005.014498c+dfsg-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looking at the
message and the changelog, it seems that symbols were changed, but this
one was apparently used by cdbfasta. I think this points at an ABI
breakage and the SONAME of libgclib must be bumped and a transition must
be followed through. (I could be wrong).

Currently this regression is blocking the migration of libgclib to
testing [1]. Can you please investigate the situation?

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=libgclib

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cdbfasta/16212088/log.gz

+ cdbfasta ebola.fasta
cdbfasta: symbol lookup error: cdbfasta: undefined symbol: _Z8GReallocPPvm
autopkgtest [22:12:39]: test run-unit-tests




OpenPGP_signature
Description: OpenPGP digital signature

Processed: rails: autopkgtest needs update for new version of puma: Could not find gem 'puma (~> 4.1)'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:puma
Bug #997883 [src:rails] rails: autopkgtest needs update for new version of 
puma: Could not find gem 'puma (~> 4.1)'
Added indication that 997883 affects src:puma

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

Bug#997883: rails: autopkgtest needs update for new version of puma: Could not find gem 'puma (~> 4.1)'

[Paul Gevers]

Source: rails
Version: 2:6.0.3.7+dfsg-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, p...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:puma

Dear maintainer(s),

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

   passfail
puma   from testing5.3.2-3
rails  from testing2:6.0.3.7+dfsg-2
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 puma to testing
[1]. Of course, puma shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in puma 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 puma 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=puma

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rails/16207757/log.gz

 run  bundle install --local
Could not find gem 'puma (~> 4.1)' in cached gems from rubygems repository
https://rubygems.org/ or installed locally.
The source contains the following versions of 'puma': 5.3.2
 run  bundle binstubs bundler
Could not find gem 'puma (~> 4.1)' in locally installed gems.
The source contains the following versions of 'puma': 5.3.2
 run  bundle exec spring binstub --all
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:278:in
`block in verify_gemfile_dependencies_are_found!': Could not find gem
'puma (~> 4.1)' in locally installed gems. (Bundler::GemNotFound)
The source contains the following versions of 'puma': 5.3.2
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:253:in
`each'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:253:in
`verify_gemfile_dependencies_are_found!'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:50:in
`start'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:23:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:262:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:483:in
`materialize'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:234:in
`specs_for'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/runtime.rb:18:in
`setup'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in
`setup'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in
`block in '
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:136:in
`with_level'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:88:in
`silence'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in
`'
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
`require'
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
`require'
+ cd foo
+ rails runner puts "Empty Rails %s app booted correctly" % Rails.version
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:278:in
`block in verify_gemfile_dependencies_are_found!': Could not find gem
'puma (~> 4.1)' in locally installed gems. (Bundler::GemNotFound)
The source contains the following versions of 'puma': 5.3.2
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:253:in
`each'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:253:in
`verify_gemfile_dependencies_are_found!'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:50:in
`start'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:23:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:262:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib

Bug#997882: licensecheck: autopkgtest regression: lots of failures

[Paul Gevers]

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

Dear maintainer(s),

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

   passfail
licensecheck   from testing3.2.13-1
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/l/licensecheck/16222812/log.gz

t/OSI.t .. # Seeded srand with seed '20211026' from
local date.
1..26
ok 1 - Corpus file t/OSI/MPL-1.0
ok 2 - Corpus file t/OSI/EPL-1.0
ok 3 - Corpus file t/OSI/RPSL-1.0
ok 4 - Corpus file t/OSI/Artistic-2.0
ok 5 - Corpus file t/OSI/Python-2.0
ok 6 - Corpus file t/OSI/Zlib
ok 7 - Corpus file t/OSI/AFL-3.0
ok 8 - Corpus file t/OSI/GPL-2.0
ok 9 - Corpus file t/OSI/BSL-1.0
ok 10 - Corpus file t/OSI/LGPL-2.0
ok 11 - Corpus file t/OSI/MPL-1.1
ok 12 - Corpus file t/OSI/CECILL-2.1
ok 13 - Corpus file t/OSI/Apache-2.0
ok 14 - Corpus file t/OSI/AGPL-3.0
ok 15 - Corpus file t/OSI/NTP
ok 16 - Corpus file t/OSI/Artistic-1.0-Perl
ok 17 - Corpus file t/OSI/PostgreSQL
ok 18 - Corpus file t/OSI/MPL-2.0
ok 19 - Corpus file t/OSI/OFL-1.1
ok 20 - Corpus file t/OSI/CDDL-1.0
ok 21 - Corpus file t/OSI/BSD-3-Clause
ok 22 - Corpus file t/OSI/MIT
ok 23 - Corpus file t/OSI/BSD-2-Clause-Views
ok 24 - Corpus file t/OSI/QPL-1.0
ok 25 - Corpus file t/OSI/LGPL-2.1
ok 26 - Corpus file t/OSI/ISC
ok
t/SPDX.t . # Seeded srand with seed '20211026' from
local date.
1..88
ok 1 - Corpus file t/SPDX/CC-BY-2.5.txt
ok 2 - Corpus file t/SPDX/CC-BY-SA-4.0.txt
ok 3 - Corpus file t/SPDX/CC-BY-NC-ND-4.0.txt
ok 4 - Corpus file t/SPDX/CC-BY-NC-SA-3.0.txt
ok 5 - Corpus file t/SPDX/BSD-3-Clause.txt
ok 6 - Corpus file t/SPDX/CC-BY-SA-2.0.txt
ok 7 - Corpus file t/SPDX/AFL-2.0.txt
ok 8 - Corpus file t/SPDX/LGPL-2.0.txt
ok 9 - Corpus file t/SPDX/zlib-acknowledgement.txt
ok 10 - Corpus file t/SPDX/MS-RL.txt
ok 11 - Corpus file t/SPDX/Apache-2.0.txt
ok 12 - Corpus file t/SPDX/OFL-1.0.txt
ok 13 - Corpus file t/SPDX/Zlib.txt
ok 14 - Corpus file t/SPDX/Eurosym.txt
ok 15 - Corpus file t/SPDX/ISC.txt
ok 16 - Corpus file t/SPDX/MIT-feh.txt
ok 17 - Corpus file t/SPDX/CC-BY-SA-3.0.txt
ok 18 - Corpus file t/SPDX/MIT-CMU.txt
ok 19 - Corpus file t/SPDX/Artistic-1.0.txt
ok 20 - Corpus file t/SPDX/WTFPL.txt
ok 21 - Corpus file t/SPDX/EPL-1.0.txt
ok 22 - Corpus file t/SPDX/CC-BY-NC-2.5.txt
ok 23 - Corpus file t/SPDX/CDDL-1.0.txt
ok 24 - Corpus file t/SPDX/CC0-1.0.txt
ok 25 - Corpus file t/SPDX/MIT.txt
ok 26 - Corpus file t/SPDX/CC-BY-1.0.txt
ok 27 - Corpus file t/SPDX/AGPL-1.0.txt
ok 28 - Corpus file t/SPDX/AFL-3.0.txt
ok 29 - Corpus file t/SPDX/CC-BY-SA-2.5.txt
ok 30 - Corpus file t/SPDX/ICU.txt
ok 31 - Corpus file t/SPDX/AFL-2.1.txt
ok 32 - Corpus file t/SPDX/CC-BY-NC-3.0.txt
ok 33 - Corpus file t/SPDX/SGI-B-1.1.txt
ok 34 - Corpus file t/SPDX/CC-BY-ND-3.0.txt
ok 35 - Corpus file t/SPDX/Python-2.0.txt
ok 36 - Corpus file t/SPDX/CC-BY-NC-SA-1.0.txt
ok 37 - Corpus file t/SPDX/CC-BY-NC-4.0.txt
ok 38 - Corpus file t/SPDX/CECILL-1.0.txt
ok 39 - Corpus file t/SPDX/MS-PL.txt
ok 40 - Corpus file t/SPDX/MPL-1.0.txt
ok 41 - Corpus file t/SPDX/CC-BY-NC-SA-2.5.txt
ok 42 - Corpus file t/SPDX/MPL-2.0.txt
ok 43 - Corpus file t/SPDX/Libpng.txt
ok 44 - Corpus file t/SPDX/OFL-1.1.txt
ok 45 - Corpus file t/SPDX/Cube.txt
ok 46 - Corpus file t/SPDX/CC-BY-3.0.txt
ok 47 - Corpus file t/SPDX/CC-BY-ND-1.0.txt
ok 48 - Corpus file t/SPDX/CC-BY-NC-ND-1.0.txt
ok 49 - Corpus file t/SPDX/CC-BY-SA-1.0.txt
ok 50 - Corpus file t/SPDX/CC-BY-2.0.txt
ok 51 - Corpus file t/SPDX/CC-BY-NC-1.0.txt
ok 52 - Corpus file t/SPDX/AFL-1.1.txt
ok 53 - Corpus file t/SPDX/CC-BY-ND-2.5.txt
ok 54 - Corpus file t/SPDX/MIT-enna.txt
ok 55 - Corpus file t/SPDX/Apache-1.1.txt
ok 56 - Corpus file t/SPDX/RPSL-1.0.txt
ok 57 - Corpus file t/SPDX/CC-BY-4.0.txt
ok 58 - Corpus file t/SPDX/MIT-advertising.txt
ok 59 - Corpus file t/SPDX/BSD-4-Clause.txt
ok 60 - Corpus file t/SPDX/SGI-B-1.0.txt
ok 61 - Corpus file t/SPDX/Artistic-2.0.txt
ok 62 - Corpus file t/SPDX/LGPL-2.1.txt
ok 63 - Corpus file t/SPDX/CC-BY-NC-ND-2.0.txt
ok 64 - Corpus file t/SPDX/Aladdin.txt
ok 65 - Corpus file t/SPDX/CECILL-B.txt
ok 66 - Corpus file t/SPDX/AFL-1.2.txt
ok 67 - Corpus file t/SPDX/MPL-1.1.txt
ok 68 - Corpus file t/SPDX/curl.txt
ok 69 - Corpus file t/SPDX/QPL-1.0.txt
ok 70 - Corpus

Bug#997540: marked as done (console-data: FTBFS: ./debian/trim_keymaps.sh: 1: tempfile: not found)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 14:35:00 +
with message-id 
and subject line Bug#997540: fixed in console-data 2:1.12-9
has caused the Debian Bug report #997540,
regarding console-data: FTBFS: ./debian/trim_keymaps.sh: 1: tempfile: not found
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.)


-- 
997540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: console-data
Version: 2:1.12-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> make[3]: Nothing to be done for 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/<>/doc'
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
> # Remove useless empty directory
> rmdir /<>/debian/console-data/usr/share/videomodes
> chmod +x debian/gen-acorn-keymaps
> debian/gen-acorn-keymaps
> chmod u+x /<>/debian/list-keymaps.pl
> /<>/debian/list-keymaps.pl 
> /<>/debian/console-data.keymaps > 
> /<>/debian/console-data/usr/share/console/lists/console-data.keymap-list
> dh_consoledata -i
>   mkdir -p debian/console-data/usr/share/console/lists/keymaps
>   install -m644 debian/console-data.keymaps 
> debian/console-data/usr/share/console/lists/keymaps
>   sed  >debian/console-data.config -e '/^#KEYMAPS#$/ r 
> debian/console-data.keymaps' -e '/^#COMMON#$/ r 
> /usr/share/debhelper/dh-consoledata/common.pl'
>   cp /usr/share/debhelper/dh-consoledata/templates 
> debian/console-data.templates
>   echo "# Automatically added by dh_consoledata/UNDECLARED">> 
> debian/console-data.postinst.debhelper
>   sed "s/#PACKAGE#/console-data/" 
> /usr/share/debhelper/autoscripts/postinst-lcd-keymaps >> 
> debian/console-data.postinst.debhelper
>   echo '# End automatically added section' >> 
> debian/console-data.postinst.debhelper
>   echo 'console:depends=console-common (>= 0.7.91)' >> debian/substvars
> # Needed for ubiquity
> for f in /<>/debian/console-keymaps-*.templates; do \
>  echo >> /<>/debian/console-data.templates ; \
>  cat $f >> /<>/debian/console-data.templates ; \
> done
> for PO in /<>/debian/po/*.po; do \
>   L="$(basename $PO .po)"; \
>   install -d 
> /<>/debian/console-data/usr/share/locale/$L/LC_MESSAGES; \
>   msgfmt -o 
> /<>/debian/console-data/usr/share/locale/$L/LC_MESSAGES/console-data.mo
>  $PO; \
> done
> Adding cdbs dependencies to debian/console-keymaps-at.substvars
> dh_installdirs -pconsole-keymaps-at \
>   
> Adding cdbs dependencies to debian/console-keymaps-usb.substvars
> dh_installdirs -pconsole-keymaps-usb \
>   
> Adding cdbs dependencies to debian/console-keymaps-sun.substvars
> dh_installdirs -pconsole-keymaps-sun \
>   
> Adding cdbs dependencies to debian/console-keymaps-acorn.substvars
> dh_installdirs -pconsole-keymaps-acorn \
>   
> Adding cdbs dependencies to debian/console-keymaps-mac.substvars
> dh_installdirs -pconsole-keymaps-mac \
>   
> Adding cdbs dependencies to debian/console-keymaps-atari.substvars
> dh_installdirs -pconsole-keymaps-atari \
>   
> Adding cdbs dependencies to debian/console-keymaps-amiga.substvars
> dh_installdirs -pconsole-keymaps-amiga \
>   
> Adding cdbs dependencies to debian/console-keymaps-dec.substvars
> dh_installdirs -pconsole-keymaps-dec \
>   
> dh_installdocs -pconsole-data ./README
>   install -d debian/console-data/usr/share/doc/console-data
>   install -d debian/.debhelper/generated/console-data
>   cd './doc/keymaps//..' && find 'keymaps' \( -type f -or -type l \) -and 
> ! -empty -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto 
> --parents -dp {} 
> /<>/debian/console-data/usr/share/doc/console-data
>   cd './doc/fonts//..' && find 'fonts' \( -type f -or -type l \) -and ! 
> -empty -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto 
> --parents -dp {} 
> /<>/debian/console-data/usr/share/doc/console-data
>   cp --reflink=auto -a ./doc/README.acm 
> debian/console-data/usr/share/doc/console-data
>   cp --reflink=auto -a ./doc/README.sfm 
> debian/console-data/usr/share/doc/console-data
>   cp --reflink=auto -a ./debian/README.us-intl 
> debian/console-data/usr/share/doc/console-data
>   cp --reflink=auto -a ./README 
> debian/console-data/usr/share/doc/

Bug#997204: marked as done (gtkextra: FTBFS: configure.ac:64: error: AC_CONFIG_MACRO_DIR can only be used once)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 14:35:15 +
with message-id 
and subject line Bug#997204: fixed in gtkextra 3.3.4-6
has caused the Debian Bug report #997204,
regarding gtkextra: FTBFS: configure.ac:64: error: AC_CONFIG_MACRO_DIR can only 
be used once
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.)


-- 
997204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkextra
Version: 3.3.4-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build  --with autoreconf
>dh_update_autotools_config
>dh_autoreconf
> configure.ac:64: error: AC_CONFIG_MACRO_DIR can only be used once
> ./lib/autoconf/general.m4:1970: AC_CONFIG_MACRO_DIR is expanded from...
> configure.ac:64: the top level
> autom4te: error: /usr/bin/m4 failed with exit status: 1
> aclocal: error: /usr/bin/autom4te failed with exit status: 1
> autoreconf: error: aclocal failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:14: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/gtkextra_3.3.4-4_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gtkextra
Source-Version: 3.3.4-6
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated gtkextra 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: Tue, 26 Oct 2021 15:38:22 +0200
Source: gtkextra
Architecture: source
Version: 3.3.4-6
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 997204
Changes:
 gtkextra (3.3.4-6) unstable; urgency=medium
 .
   * added the build-dependency gtk-doc-tools. Closes: #997204
Checksums-Sha1:
 20044554b1cf7c534d15ad0ea259f43d2d7a8812 2274 gtkextra_3.3.4-6.dsc
 49b758111e7303c76aca7a97766187f51e36ef40 10304 gtkextra_3.3.4-6.debian.tar.xz
 f268df6f4b8d8477dea7a4cc93428770f1566cd5 13621 gtkextra_3.3.4-6_amd64.buildinfo
Checksums-Sha256:
 443a7df8f5df3c39ee5ade61cd59012bb8c4c82deed016d8acd9bf4200a3ec72 2274 
gtkextra_3.3.4-6.dsc
 1bbf1dda338b6089ac9f8b4524a3b1f87ed73a7b9f22d7065813d93fb6d92de7 10304 
gtkextra_3.3.4-6.debian.tar.xz
 bbbd8285da051c616912b3e5bbeff28e4ecb4b675d1a3d441cd13a0a84fb6756 13621 
gtkextra_3.3.4-6_amd64.buildinfo
Files:
 e14ec826eb2ef399f44ad9a21769b495 2274 devel optional gtkextra_3.3.4-6.dsc
 b4731eff661a446d42d356a7851a50e3 10304 devel optional 
gtkextra_3.3.4-6.debian.tar.xz
 5cc1e3588cab87266554b3d6345a8b8c 13621 devel optional 
gtkextra_3.3.4-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmF4B64ACgkQHCgWkHE2
rjlnyw/+LxJ/XvT2+RPPsLjctmBOLbSD4YiaPK/e9szuV0CQ9ED/Vu4bk8LV0xdF
mAVVublaawmirl6Ea2+U10De1IoQadaoP2nT/D7RySVUBT9RtpN6/fiV0u4mwDx0
MpkPrpb/7b2Oy06SfGDQhqDxqh8T+hYEBHR9ukrCIkf/F3vlf+V0NFwF6KWElDQ6
DyyGZJWhlTeglXdlYMk9jtUpdvePoYO4cXuqmUVtKFG9oILISJovPzySNtAmQUZH
BIfR/FeRVkBnuzd3YpuH9dDAqKYEHqoR2BH40e7pCsTJqTHHHgAgvluuG6OShujO
ZjGL1QSPYXbS5bugd7J9aPIuOHMLQal/ptcE1ggiTb/OyRHw+QQgmBs11/9toYLr
42RZguxx/3b9rPBdY21QMpqzg0krRTUyCgfHNIKYfmjFKuhhGBl4QuH9Ql1Xayi3
tvUn9FEY/K0vQ6Oeue5QQgd+Fv34PbwSKlOBcIDhcl4vB9rd3popUxsQOAa7N4qa
c2U7+vAkefbs4urwaupeAmOQ9cBycvIQWNwVCXtxW3YDv/Cu8D9Bt4J4rOJz75fr
AHQ6Mw83hME49qedIoJbyts+8nJvMuacxSnXW995vuD41o6epRQGGg2WMDskztLm
2uhnqOkCwLrKVMgpoYAsW9J5bSsKcz

Bug#996293: marked as done (ruby-httparty: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 14:36:35 +
with message-id 
and subject line Bug#996293: fixed in ruby-httparty 0.18.1-3
has caused the Debian Bug report #996293,
regarding ruby-httparty: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:  
ArgumentError:
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.)


-- 
996293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-httparty
Version: 0.18.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-httparty was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
>  ArgumentError:
>wrong number of arguments (given 2, expected 1)
>  # ./lib/httparty/request/body.rb:6:in `initialize'
>  # ./spec/httparty/request/body_spec.rb:10:in `new'
>  # ./spec/httparty/request/body_spec.rb:10:in `block (3 levels) in  (required)>'
>  # ./spec/httparty/request/body_spec.rb:15:in `block (4 levels) in  (required)>'
> 
> Top 10 slowest examples (1.21 seconds, 28.9% of total time):
>   HTTParty#get should be able parse response type xml automatically
> 0.21851 seconds ./spec/httparty_spec.rb:906
>   HTTParty::Request SSL certificate verification should work when no trusted 
> CA list is specified, when the verify option is set to false
> 0.16157 seconds ./spec/httparty/ssl_spec.rb:19
>   HTTParty::Request SSL certificate verification should provide the 
> certificate used by the server via peer_cert
> 0.15752 seconds ./spec/httparty/ssl_spec.rb:74
>   HTTParty::Request SSL certificate verification should work when no trusted 
> CA list is specified, even with a bogus hostname, when the verify option is 
> set to true
> 0.15627 seconds ./spec/httparty/ssl_spec.rb:29
>   HTTParty::Request SSL certificate verification should work when using 
> ssl_ca_file with a certificate authority
> 0.14463 seconds ./spec/httparty/ssl_spec.rb:37
>   HTTParty::Request SSL certificate verification should work when using 
> ssl_ca_file with a self-signed CA
> 0.14422 seconds ./spec/httparty/ssl_spec.rb:33
>   HTTParty::Request SSL certificate verification should fail when using 
> ssl_ca_file and the server uses an unrecognized certificate authority
> 0.06358 seconds ./spec/httparty/ssl_spec.rb:50
>   HTTParty::Request SSL certificate verification should fail when using 
> ssl_ca_path and the server uses an unrecognized certificate authority
> 0.06255 seconds ./spec/httparty/ssl_spec.rb:56
>   HTTParty::Request SSL certificate verification should fail when using 
> ssl_ca_file and the server uses a bogus hostname
> 0.05454 seconds ./spec/httparty/ssl_spec.rb:62
>   HTTParty::Request SSL certificate verification should fail when no trusted 
> CA list is specified, with a bogus hostname, by default
> 0.04319 seconds ./spec/httparty/ssl_spec.rb:23
> 
> Top 10 slowest example groups:
>   HTTParty::Request
> 0.08922 seconds average (1.07 seconds / 12 examples) 
> ./spec/httparty/ssl_spec.rb:3
>   HTTParty::Logger::LogstashFormatter
> 0.0175 seconds average (0.0175 seconds / 1 example) 
> ./spec/httparty/logger/logstash_formatter_spec.rb:3
>   HTTParty::Request
> 0.00609 seconds average (1.57 seconds / 258 examples) 
> ./spec/httparty/request_spec.rb:3
>   HTTParty::ConnectionAdapter
> 0.00583 seconds average (0.40809 seconds / 70 examples) 
> ./spec/httparty/connection_adapter_spec.rb:3
>   HTTParty
> 0.00515 seconds average (0.60239 seconds / 117 examples) 
> ./spec/httparty_spec.rb:3
>   HTTParty::Logger::CurlFormatter
> 0.00417 seconds average (0.05416 seconds / 13 examples) 
> ./spec/httparty/logger/curl_formatter_spec.rb:3
>   HTTParty::HeadersProcessor
> 0.00373 seconds average (0.01866 seconds / 5 examples) 
> ./spec/httparty/headers_processor_spec.rb:3
>   Net::HTTPHeader::DigestAuthenticator
> 0.0036 seconds average (0.11892 seconds / 33 examples) 
> ./spec/httparty/net_digest_auth_spec.rb:3
>   HTTParty::Request::Body
> 0.00245 seconds average (0.02204 seconds / 9 examples) 
> ./spec/httparty/request/body_spec.rb:6
>   HTTParty::Response
> 0.00242 seconds average (0.22293 seconds / 92 examples) 
> ./spec/httparty/response_spec.rb:3
> 
> Finished in 4.18 seconds (files took 2.99 seconds to load)
> 673 examples

Bug#997880: lebiniou-data: autopkgtest regression: delta with reference data

[Paul Gevers]

Source: lebiniou-data
Version: 3.62.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
lebiniou-data  from testing3.62.2-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
lebiniou-data/3.62.2-2. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=lebiniou-data

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lebiniou-data/16222810/log.gz

[i] Setting up environment...
[i] Random seed: 361092574
{
"screen": {
"width": 320,
"height": 240
},
"input": {
"name": "sndfile",
"volumeScale": 1.0
},
"themes": [
"biniou",
"covid-19",
"zebulon"
],
"engine": {
"hFlip": false,
"vFlip": false,
"maxFps": 25,
"fadeDelay": 3,
"startMode": "last_created",
"randomMode": 2,
"autoSequencesMode": "shuffle",
"sequencesMin": 1,
"sequencesMax": 1,
"autoColormapsMode": "shuffle",
"colormapsMin": 2,
"colormapsMax": 3,
"autoImagesMode": "shuffle",
"imagesMin": 3,
"imagesMax": 4,
"webcams": 0,
"autoWebcamsMode": "cycle",
"webcamsMin": 15,
"webcamsMax": 30
},
"plugins": [
{
"name": "monitor",
"display_name": "Monitor",
"enabled": false
},
{
"name": "shaker_x",
"display_name": "Shaker X",
"enabled": true
},
{
"name": "big_half_wheel",
"display_name": "Big half wheel",
"enabled": true
},
{
"name": "sin_oscillo_1",
"display_name": "Sin oscillo 1",
"enabled": true
},
{
"name": "bassline",
"display_name": "Bass line",
"enabled": true
},
{
"name": "spiral_pulsing",
"display_name": "Spiral pulsing",
"enabled": true
},
{
"name": "blur_horizontal_2",
"display_name": "Blur horizontal 2",
"enabled": true
},
{
"name": "mirror_top",
"display_name": "Mirror top",
"enabled": true
},
{
"name": "spirals_nested",
"display_name": "Spirals nested",
"enabled": true
},
{
"name": "fadeout",
"display_name": "Fadeout",
"enabled": true
},
{
"name": "swap_columns",
"display_name": "Wave X",
"enabled": true
},
{
"name": "image_colrot",
"display_name": "Image colrot",
"enabled": true
},
{
"name": "tv_nervous",
"display_name": "TV nervous",
"enabled": true
},
{
"name": "scroll_horizontal",
"display_name": "Scroll horizontal",
"enabled": true
},
{
"name": "path_oscillo_freq",
"display_name": "Path oscillo freq",
"enabled": true
},
{
"name": "recurrence_plot",
"display_name": "Recurrence plot",
"enabled": true
},
{
"name": "takens",
"display_name": "Takens",
"enabled": true
},
{
"name": "faders",
"display_name": "Faders",
"enabled": true
},
{
"name": "clear",
"display_name": "Clear",
"enabled": true
},
{
"name": "images_pulse",
"display_name": "Images pulse",
"enabled": true
},
{
"name": "spectrum",
"display_name": "Spectrum",
"enabled": true
},
{
"name": "roller_y",
"display_name": "Roll Y",

Processed: Fixing with right version

[Debian Bug Tracking System]

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

> reopen 993042
Bug #993042 {Done: Federico Ceratto } [src:nim] nim FTBFS 
on armhf when built on arm64 hardware
Bug reopened
Ignoring request to alter fixed versions of bug #993042 to the same values 
previously set
> fixed 993042 1.6.0-1
Bug #993042 [src:nim] nim FTBFS on armhf when built on arm64 hardware
Marked as fixed in versions nim/1.6.0-1.
> close 993042
Bug #993042 [src:nim] nim FTBFS on armhf when built on arm64 hardware
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#993042: Fixing with right version

[Nilesh Patra]

reopen 993042
fixed 993042 1.6.0-1
close 993042
thanks

Closing with the right version

Nilesh


signature.asc
Description: PGP signature

Bug#987379: llvm-toolchain-11 autopkgtest segfaults on armhf

[Paul Gevers]

Hi Diederik, all,

On 26-10-2021 08:34, Diederik de Haas wrote:
> Therefor it may be worth trying whether this bug is resolved as well.

Well, it's not fixed in the Debian archive:
https://ci.debian.net/data/autopkgtest/unstable/armhf/l/llvm-toolchain-12/16229260/log.gz

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: src:nim: fails to migrate to testing for too long: ftbfs on armhf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #996734 {Done: Paul Gevers } [src:nim] src:nim: fails to 
migrate to testing for too long: ftbfs on armhf
Severity set to 'important' from 'serious'

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

Processed: python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable

[Debian Bug Tracking System]

Processing control commands:

> found -1 python-click/8.0.2-1
Bug #997878 [src:python-click, src:python-softlayer] python-click breaks 
python-softlayer autopkgtest: 'NoneType' object is not iterable
Marked as found in versions python-click/8.0.2-1.
> found -1 python-softlayer/5.8.5-2
Bug #997878 [src:python-click, src:python-softlayer] python-click breaks 
python-softlayer autopkgtest: 'NoneType' object is not iterable
Marked as found in versions python-softlayer/5.8.5-2.

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

Bug#997878: python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable

[Paul Gevers]

Source: python-click, python-softlayer
Control: found -1 python-click/8.0.2-1
Control: found -1 python-softlayer/5.8.5-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
python-click   from testing8.0.2-1
python-softlayer   from testing5.8.5-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python-click to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-softlayer/16215050/log.gz

=== FAILURES
===
___ VirtCreateTests.test_create_like
___
'NoneType' object is not iterable

During handling of the above exception, another exception occurred:
NOTE: Incompatible Exception Representation, displaying natively:

testtools.testresult.real._StringException: Traceback (most recent call
last):
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1346, in patched
return func(*newargs, **newkeywargs)
  File
"/tmp/autopkgtest-lxc.st1ir0ft/downtmp/build.Zrk/src/tests/CLI/modules/vs/vs_create_tests.py",
line 370, in test_create_like
self.assert_called_with('SoftLayer_Virtual_Guest',
'generateOrderTemplate', args=args)
  File
"/tmp/autopkgtest-lxc.st1ir0ft/downtmp/build.Zrk/src/SoftLayer/testing/__init__.py",
line 144, in assert_called_with
raise AssertionError('%s::%s was not called with given properties: %s'
AssertionError: SoftLayer_Virtual_Guest::generateOrderTemplate was not
called with given properties: {'args': ({'datacenter': {'name':
'dal05'}, 'domain': 'test.sftlyr.ws', 'hourlyBillingFlag': True,
'hostname': 'vs-test-like', 'startCpus': 2, 'maxMemory': 1024,
'localDiskFlag': False, 'operatingSystemReferenceCode': 'UBUNTU_LATEST',
'networkComponents': [{'maxSpeed': 100}],
'supplementalCreateObjectOptions': {'bootMode': None}},)}

- Captured stderr call
-
CRITICAL:root:SoftLayer_Virtual_Guest::generateOrderTemplate property
mismatch, args: expected=({'datacenter': {'name': 'dal05'}, 'domain':
'test.sftlyr.ws', 'hourlyBillingFlag': True, 'hostname': 'vs-test-like',
'startCpus': 2, 'maxMemory': 1024, 'localDiskFlag': False,
'operatingSystemReferenceCode': 'UBUNTU_LATEST', 'networkComponents':
[{'maxSpeed': 100}], 'supplementalCreateObjectOptions': {'bootMode':
None}},); actual=({'startCpus': 2, 'maxMemory': 1024, 'hostname':
'vs-test-like', 'domain': 'test.sftlyr.ws', 'localDiskFlag': False,
'hourlyBillingFlag': True, 'supplementalCreateObjectOptions':
{'bootMode': None}, 'operatingSystemReferenceCode': 'UBUNTU_LATEST',
'datacenter': {'name': 'dal05'}, 'networkComponents': [{'maxSpeed':
'100'}]},)
-- Captured log call
---
CRITICAL root:__init__.py:180
SoftLayer_Virtual_Guest::generateOrderTemplate property mismatch, args:
expected=({'datacenter': {'name': 'dal05'}, 'domain': 'test.sftlyr.ws',
'hourlyBillingFlag': True, 'hostname': 'vs-test-like', 'startCpus': 2,
'maxMemory': 1024, 'localDiskFlag': False,
'operatingSystemReferenceCode': 'UBUNTU_LATEST', 'networkComponents':
[{'maxSpeed': 100}], 'supplementalCreateObjectOptions': {'bootMode':
None}},); actual=({'startCpus': 2, 'maxMemory': 1024, 'hostname':
'vs-test-like', 'domain': 'test.sftlyr.ws', 'localDiskFlag': False,
'hourlyBillingFlag': True, 'supplementalCreateObjectOptions':
{'bootMode': None}, 'operatingSystemReferenceCode': 'UBUNTU_LATEST',
'datacenter': {'name': 'dal05'}, 'networkComponents': [{'maxSpeed':
'100'}]},)
___ VirtCreateTests.test_create_like_flavor

'NoneType' object is not iterable

During handling of the above exception, another exception occurred:
NOTE: Incompatible Exception Representation, displaying natively:

testtools.testresult.real._StringException: Traceback (most recent call
last):
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1346, in patched
return func(*newargs, **newkeywargs)
  File
"/tmp/autopkgtest-lxc.st1ir0ft/downtmp/build.Zrk/src/tests/CLI/modules/vs/vs_create_tests.py",
line 486, in test_create_like_flavor

Processed: mailman3: autopkgtest needs update for new version of python-click: changed messages

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python-click
Bug #997877 [src:mailman3] mailman3: autopkgtest needs update for new version 
of python-click: changed messages
Added indication that 997877 affects src:python-click

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

Bug#997877: mailman3: autopkgtest needs update for new version of python-click: changed messages

[Paul Gevers]

Source: mailman3
Version: 3.3.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-click

[X-Debbugs-CC: debian...@lists.debian.org, python-cl...@packages.debian.org]

Dear maintainer(s),

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

   passfail
python-click   from testing8.0.2-1
mailman3   from testing3.3.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It looks like
the messages from python-click became a bit more verbose and the
autopkgtest from mailman3 checks the messages verbatim.

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

https://ci.debian.net/data/autopkgtest/testing/i386/m/mailman3/16216259/log.gz

==
FAIL: test_bad_filename
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.yd8254dv/downtmp/build.OCH/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 57, in test_bad_filename
self.assertEqual(
AssertionError: "Usag[110 chars]LENAME': 'bad': No such file or
directory\n" != "Usag[110 chars]LENAME': Could not open file: bad: No
such file or directory\n"
  Usage: syncmembers [OPTIONS] FILENAME LISTSPEC
  Try 'syncmembers --help' for help.
  - Error: Invalid value for 'FILENAME': 'bad': No such file or directory
?  ^   -
+ Error: Invalid value for 'FILENAME': Could not open file: bad: No such
file or directory
?  ^


==
FAIL: test_sync_delivery_bogus
(mailman.commands.tests.test_cli_syncmembers.TestCLISyncMembers)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.yd8254dv/downtmp/build.OCH/src/src/mailman/commands/tests/test_cli_syncmembers.py",
line 372, in test_sync_delivery_bogus
self.assertEqual(
AssertionError: "Usag[123 chars]-d': 'bogus' is not one of 'regular',
'mime', [29 chars]'.\n" != "Usag[123 chars]-d': invalid choice: bogus.
(choose from regul[33 chars]d)\n"
  Usage: syncmembers [OPTIONS] FILENAME LISTSPEC
  Try 'syncmembers --help' for help.
  - Error: Invalid value for '--delivery' / '-d': 'bogus' is not one of
'regular', 'mime', 'plain', 'summary', 'disabled'.
?   ^ ^^^ ^^ ^^
  -  --  - -  -   -  -^^
+ Error: Invalid value for '--delivery' / '-d': invalid choice: bogus.
(choose from regular, mime, plain, summary, disabled)
?   
^^^  ^^   ^


==
FAIL: test_bad_filename
(mailman.commands.tests.test_cli_delmembers.TestCLIDelMembers)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.yd8254dv/downtmp/build.OCH/src/src/mailman/commands/tests/test_cli_delmembers.py",
line 55, in test_bad_filename
self.assertEqual(
AssertionError: "Usag[95 chars] / '-f': 'bad': No such file or
directory\n" != "Usag[95 chars] / '-f': Could not open file: bad: No
such file or directory\n"
  Usage: delmembers [OPTIONS]
  Try 'delmembers --help' for help.
  - Error: Invalid value for '--file' / '-f': 'bad': No such file or
directory
?   ^   -
+ Error: Invalid value for '--file' / '-f': Could not open file: bad: No
such file or directory
?   ^

Bug#997168: marked as done (scottfree: FTBFS: ScottCurses.c:402:32: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Tue, 26 Oct 2021 13:48:56 +
with message-id 
and subject line Bug#997168: fixed in scottfree 1.14-11
has caused the Debian Bug report #997168,
regarding scottfree: FTBFS: ScottCurses.c:402:32: error: format not a string 
literal and no format arguments [-Werror=format-security]
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.)


-- 
997168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scottfree
Version: 1.14-10.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
> ScottCurses.o ScottCurses.c
> ScottCurses.c: In function ‘OutBuf’:
> ScottCurses.c:402:32: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   402 | wprintw(Bottom,word);
>   |^~~~
> ScottCurses.c: In function ‘LoadDatabase’:
> ScottCurses.c:303:17: warning: ignoring return value of ‘fscanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   303 | fscanf(f,"%hd %hd %hd %hd %hd %hd",
>   | ^~~
>   304 | &rp->Exits[0],&rp->Exits[1],&rp->Exits[2],
>   | ~~
>   305 | &rp->Exits[3],&rp->Exits[4],&rp->Exits[5]);
>   | ~~
> ScottCurses.c:335:17: warning: ignoring return value of ‘fscanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   335 | fscanf(f,"%hd",&lo);
>   | ^~~
> ScottCurses.c:348:9: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   348 | fscanf(f,"%d",&ct);
>   | ^~
> ScottCurses.c:352:9: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   352 | fscanf(f,"%d",&ct);
>   | ^~
> ScottCurses.c: In function ‘LoadGame’:
> ScottCurses.c:695:17: warning: ignoring return value of ‘fscanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   695 | fscanf(f,"%d %d\n",&Counters[ct],&RoomSaved[ct]);
>   | ^~~~
> ScottCurses.c:697:9: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   697 | fscanf(f,"%ld %hd %hd %d %d %hd\n",
>   | ^~~
>   698 | &BitFlags,&DarkFlag,&MyLoc,&CurrentCounter,&SavedRoom,
>   | ~~
>   699 | &GameHeader.LightTime);
>   | ~~
> ScottCurses.c:705:17: warning: ignoring return value of ‘fscanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   705 | fscanf(f,"%hd\n",&lo);
>   | ^
> cc1: some warnings being treated as errors
> make[1]: *** [: ScottCurses.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/scottfree_1.14-10.1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: scottfree
Source-Version: 1.14-11
Done: Stephen Kitt 

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

Processed: astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions'

[Debian Bug Tracking System]

Processing control commands:

> found -1 astroid/2.8.2-1
Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module 
named 'typing_extensions'
Marked as found in versions astroid/2.8.2-1.

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

Bug#997875: astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions'

[Paul Gevers]

Source: astroid
Control: found -1 astroid/2.8.2-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainer(s),

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

   passfail
astroidfrom testing2.8.2-1
pylint-flask   from testing0.5-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looking at the
stack trace it seems to me that astroid is missing a dependency.

Currently this regression is blocking the migration of astroid to
testing [1]. Can you please investigate the situation and if I'm wrong
reassign the bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint-flask/16213951/log.gz

Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pylint_flask/__init__.py", line
3, in 
from astroid import MANAGER
  File "/usr/lib/python3/dist-packages/astroid/__init__.py", line 51, in

from astroid.nodes import node_classes, scoped_nodes
  File "/usr/lib/python3/dist-packages/astroid/nodes/__init__.py", line
27, in 
from astroid.nodes.node_classes import (  # pylint:
disable=redefined-builtin (Ellipsis)
  File "/usr/lib/python3/dist-packages/astroid/nodes/node_classes.py",
line 47, in 
from astroid import decorators, mixins, util
  File "/usr/lib/python3/dist-packages/astroid/decorators.py", line 36,
in 
from typing_extensions import ParamSpec
ModuleNotFoundError: No module named 'typing_extensions'
autopkgtest [00:09:48]: test autodep8-python3




OpenPGP_signature
Description: OpenPGP digital signature

Bug#997874: django-uwsgi: autopkgtest regression: No module named 'django_uwsgi_ng'

[Paul Gevers]

Source: django-uwsgi
Version: 1.1.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
django-uwsgi   from testing1.1.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems to me
that because the old package is now a dummy package autodep8 doesn't
spot the right module to include. autodep8 has the ability to be taught
the right name of the module to include, see $(man autodep8) under
`PACKAGE-SPECIFIC CONFIGURATION`.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-uwsgi/1617/log.gz

Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'django_uwsgi_ng'
autopkgtest [13:09:21]: test autodep8-python3




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#996293 marked as pending in ruby-httparty

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996293 [src:ruby-httparty] ruby-httparty: FTBFS with ruby3.0: ERROR: Test 
"ruby3.0" failed:  ArgumentError:
Added tag(s) pending.

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

Bug#996293: marked as pending in ruby-httparty

[Lucas Kanashiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-httparty/-/commit/0d5e183c31106780337a70e41eaba80c767c3903


Use double splat operator for keyword arguments

* Closes: #996293


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996293

Processed: Bug#997168 marked as pending in scottfree

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997168 [src:scottfree] scottfree: FTBFS: ScottCurses.c:402:32: error: 
format not a string literal and no format arguments [-Werror=format-security]
Added tag(s) pending.

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

Bug#997168: marked as pending in scottfree

[Stephen Kitt]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/games-team/scottfree/-/commit/59221d2a1f4f401773e74bdc0610e41102c0aad4


Add constant format strings

Closes: #997168


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997168

Bug#997522: logidee-tools: FTBFS: make[2]: kpsepath: No such file or directory

[Raphael Hertzog]

Control: tag -1 + wontfix

On Sat, 23 Oct 2021, Lucas Nussbaum wrote:
> Source: logidee-tools
> Version: 1.2.19
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Note that I requested removal of this package so I will not handle this
bug. See https://bugs.debian.org/996776

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Processed: Re: Bug#997522: logidee-tools: FTBFS: make[2]: kpsepath: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + wontfix
Bug #997522 [src:logidee-tools] logidee-tools: FTBFS: make[2]: kpsepath: No 
such file or directory
Added tag(s) wontfix.

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