Bug#952157: marked as done (verdigris FTBFS with Qt 5.12)

[Debian Bug Tracking System]

Your message dated Tue, 27 Dec 2022 08:39:47 +0100
with message-id <1afaa7a5-a4f3-4208-94c5-bee79e33f...@debian.org>
and subject line Fixed in 1.3-1
has caused the Debian Bug report #952157,
regarding verdigris FTBFS with Qt 5.12
to be marked as done.

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

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


-- 
952157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: verdigris
Version: 1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/tests/qt/qobject/test'
> cd .. && /<>/tests/qt/qobject/test/target_wrapper.sh  
> ./tst_qobject 
> * Start testing of tst_QObject *
> Config: Using QtTest library 5.12.5, Qt 5.12.5 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 9.2.1 20200123)
> PASS   : tst_QObject::initTestCase()
> PASS   : tst_QObject::disconnect()
> PASS   : tst_QObject::connectSlotsByName()
> SKIP   : tst_QObject::connectSignalsToSignalsWithDefaultArguments() Not 
> supported by W_SLOT/W_SIGNAL
>Loc: [../tst_qobject.cpp(2495)]
> PASS   : tst_QObject::receivers()
> PASS   : tst_QObject::normalize()
> PASS   : tst_QObject::qobject_castTemplate()
> PASS   : tst_QObject::findChildren()
> PASS   : tst_QObject::connectDisconnectNotify(combo1)
> PASS   : tst_QObject::connectDisconnectNotify(combo2)
> PASS   : tst_QObject::connectDisconnectNotify(combo3)
> PASS   : tst_QObject::connectDisconnectNotify(combo4)
> PASS   : tst_QObject::connectDisconnectNotify(combo5)
> PASS   : tst_QObject::connectDisconnectNotify(combo6)
> PASS   : tst_QObject::connectDisconnectNotify(combo7)
> PASS   : tst_QObject::connectDisconnectNotifyPMF()
> PASS   : tst_QObject::disconnectNotify_receiverDestroyed()
> SKIP   : tst_QObject::disconnectNotify_metaObjConnection() This bug was only 
> fixed in 5.8
>Loc: [../tst_qobject.cpp(1006)]
> PASS   : tst_QObject::connectNotify_connectSlotsByName()
> PASS   : tst_QObject::connectDisconnectNotify_shadowing()
> PASS   : tst_QObject::emitInDefinedOrder()
> PASS   : tst_QObject::customTypes()
> PASS   : tst_QObject::streamCustomTypes()
> PASS   : tst_QObject::metamethod()
> PASS   : tst_QObject::namespaces()
> PASS   : tst_QObject::threadSignalEmissionCrash()
> PASS   : tst_QObject::thread()
> PASS   : tst_QObject::thread0()
> PASS   : tst_QObject::moveToThread()
> PASS   : tst_QObject::senderTest()
> PASS   : tst_QObject::declareInterface()
> PASS   : tst_QObject::qpointerResetBeforeDestroyedSignal()
> PASS   : tst_QObject::testUserData()
> PASS   : tst_QObject::childDeletesItsSibling()
> PASS   : tst_QObject::dynamicProperties()
> PASS   : tst_QObject::floatProperty()
> PASS   : tst_QObject::qrealProperty()
> SKIP   : tst_QObject::property() this tests bugs in 5.5
>Loc: [../tst_qobject.cpp(1997)]
> PASS   : tst_QObject::recursiveSignalEmission()
> PASS   : tst_QObject::signalBlocking()
> PASS   : tst_QObject::blockingQueuedConnection()
> PASS   : tst_QObject::childEvents()
> PASS   : tst_QObject::installEventFilter()
> PASS   : tst_QObject::deleteSelfInSlot()
> PASS   : tst_QObject::disconnectSelfInSlotAndDeleteAfterEmit()
> PASS   : tst_QObject::dumpObjectInfo()
> PASS   : tst_QObject::connectToSender()
> PASS   : tst_QObject::qobjectConstCast()
> PASS   : tst_QObject::uniqConnection()
> PASS   : tst_QObject::uniqConnectionPtr()
> PASS   : tst_QObject::interfaceIid()
> PASS   : tst_QObject::deleteQObjectWhenDeletingEvent()
> SKIP   : tst_QObject::overloads() Overload not supported by W_SIGNAL/W_SLOT
>Loc: [../tst_qobject.cpp(3778)]
> PASS   : tst_QObject::isSignalConnected()
> PASS   : tst_QObject::qMetaObjectConnect()
> PASS   : tst_QObject::qMetaObjectDisconnectOne()
> PASS   : tst_QObject::sameName()
> PASS   : tst_QObject::connectByMetaMethods()
> PASS   : tst_QObject::connectByMetaMethodSlotInsteadOfSignal()
> PASS   : tst_QObject::connectConstructorByMetaMethod()
> PASS   : tst_QObject::disconnectByMetaMethod()
> PASS   : tst_QObject::disconnectNotSignalMetaMethod()
> PASS   : tst_QObject::autoConnectionBehavior()
> PASS   : tst_QObject::baseDestroyed()
> PASS   : tst_QObject::pointerConnect()
> PASS   : tst_QObject::pointerDisconnect()
> PASS   : tst_QObject::emitInDefinedOrderPointer()
> PASS   : tst_QObject::customTypesPointer()
> PASS   : tst_QObject::connectCxx0x()
> PASS   : tst_QObject::connectToStaticCxx0x()
> PASS   : tst_QObject::connectCxx0xTypeMatching()
> PA

Processed: might cause one test of r-cran-lexrankr on i386 architecture fail

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 might cause one test of r-cran-lexrankr on i386 architecture fail
Bug #1024828 [src:r-cran-igraph] src:r-cran-igraph: fails to migrate to testing 
for too long: autopkgtest regression on i386
Changed Bug title to 'might cause one test of r-cran-lexrankr on i386 
architecture fail' from 'src:r-cran-igraph: fails to migrate to testing for too 
long: autopkgtest regression on i386'.
> severity -1 normal
Bug #1024828 [src:r-cran-igraph] might cause one test of r-cran-lexrankr on 
i386 architecture fail
Severity set to 'normal' from 'serious'

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

Bug#1024828: might cause one test of r-cran-lexrankr on i386 architecture fail

[Andreas Tille]

Control: retitle -1 might cause one test of r-cran-lexrankr on i386 
architecture fail
Control: severity -1 normal

In a patch[1] the test of r-cran-lexrankr prevents that the sorting
error which occures on i386 only after the r-cran-igraph upgrade causes
the test suite to fail.  As long as the issue is not clarified this
bug should not be closed but the severity is reduced to normal.

Kind regards
   Andreas.


[1] 
https://salsa.debian.org/r-pkg-team/r-cran-lexrankr/-/blob/master/debian/tests/run-unit-test#L14-18

-- 
http://fam-tille.de

Bug#1021542: marked as done (unifrac: partially taken over by src:unifrac-tools)

[Debian Bug Tracking System]

Your message dated Tue, 27 Dec 2022 07:08:03 +
with message-id 
and subject line Bug#1021542: fixed in q2-diversity-lib 2022.8.0-2
has caused the Debian Bug report #1021542,
regarding unifrac: partially taken over by src:unifrac-tools
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.)


-- 
1021542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unifrac
Version: 0.10.0-3
Severity: serious

src:unifrac-tools (1.1.1-3) is now building libssu0 and libssu-dev as
well as a unifrac-tools binary package replacing libssu-tools.
libssu-tools has one reverse dependency: q2-diversity-lib, that should
probably be updated to use unifrac-tools.
That leaves only python3-unifrac as still being built from this source
package, it is used by q2-diversity-lib, too.


Andreas
--- End Message ---
--- Begin Message ---
Source: q2-diversity-lib
Source-Version: 2022.8.0-2
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated q2-diversity-lib 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, 27 Dec 2022 12:07:19 +0530
Source: q2-diversity-lib
Architecture: source
Version: 2022.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 1021542
Changes:
 q2-diversity-lib (2022.8.0-2) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Depends: s/libssu-tools/unifrac-tools/
 Closes: #1021542
   * Versioned (Build-)Depends: python3-unifrac (>= 1.1.1)
Checksums-Sha1:
 6704eedc6652436f19d5e531b2ef303d73dd2eac 1632 q2-diversity-lib_2022.8.0-2.dsc
 bf12b93d44c9cdcd15e40a085aad6cd9119de1e4 7916 
q2-diversity-lib_2022.8.0-2.debian.tar.xz
 a45222b7066f38471c7e6e5c9ee81531c82db598 11854 
q2-diversity-lib_2022.8.0-2_amd64.buildinfo
Checksums-Sha256:
 04f6ad2d765ce38cfb271dc74b514d79a7ed104522fc14ed4d2361c3e9d276bf 1632 
q2-diversity-lib_2022.8.0-2.dsc
 7c33fd7d5b0ce8d0f6fec142469269dbdb7b917dd0053ee2a774d7cd33b981f7 7916 
q2-diversity-lib_2022.8.0-2.debian.tar.xz
 dd8bf63074448836e9356a3267463be7f166de765e105ccabe4157cf40283b8f 11854 
q2-diversity-lib_2022.8.0-2_amd64.buildinfo
Files:
 6846f5999628efbec9a4671a5264746d 1632 science optional 
q2-diversity-lib_2022.8.0-2.dsc
 e0ef997733c60431d195e4428f635f85 7916 science optional 
q2-diversity-lib_2022.8.0-2.debian.tar.xz
 f366ec5ef030dc426f73c8dc6e64cdff 11854 science optional 
q2-diversity-lib_2022.8.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY6qVGwAKCRAqJ5BL1yQ+
2hxTAP4/tzTVrN6HYZh5bGIzJtPb7PE2zAHZO4HoDzfPZBIqIgD/SeCBcSDBbG8m
ep9KgkKhM9oxPug+wbl2XFFhfL+Uow8=
=Z61a
-END PGP SIGNATURE End Message ---

Bug#1027049: python-matplotlib-data: missing copyright file

[Jakub Wilk]

Package: python-matplotlib-data
Version: 3.6.2-3
Severity: serious
Justification: Policy §12.5

$ lintian -F python-matplotlib-data_3.6.2-3_all.deb
E: python-matplotlib-data: no-copyright-file

--
Jakub Wilk

Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)

[Chow Loong Jin]

On Wed, Dec 21, 2022 at 06:34:40PM +1300, Olly Betts wrote:
> On Wed, Dec 21, 2022 at 11:21:03AM +0800, Chow Loong Jin wrote:
> > I've fixed the segfault by applying the patch from [1], but there's one
> > issue remaining -- PrusaSlicer fails to initialize GLEW due to [2],
> > resulting in the plater screen not showing up, same as this SuperSlicer
> > issue[3].
> > 
> > I've also attempted to roll PrusaSlicer back to wxwidgets3.0
> 
> Please don't do that.  We're really close to eliminating wxwidgets3.0
> now, and we're not planning to include it in the bookworm release.
> 
> We're going to switch to --disable-glcanvasegl in wxwidgets3.2 which
> should solve the incompatibilities with GLEW which seem to be the
> problem here.  However that's an ABI breaking change affecting any
> packages using wxwidgets3.2's OpenGL APIs so it needs coordinating
> with the release team - Scott is currently working on that.

Alright, I'll leave the slic3r-prusa as-is then. I'm guessing that a
binNMU will take care of things when we get there.

-- 
Kind regards,
Loong Jin


signature.asc
Description: PGP signature

Bug#1027045: shaderc: FTBFS everywhere

[Sebastian Ramacher]

Source: shaderc
Version: 2022.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

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

[ 28%] Building CXX object 
libshaderc_util/CMakeFiles/shaderc_util.dir/src/resources.cc.o
cd /<>/obj-x86_64-linux-gnu/libshaderc_util && /usr/bin/c++ 
-DENABLE_HLSL -I/<>/libshaderc_util/include -I/usr/include/glslang 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wimplicit-fallthrough 
-Wextra-semi -Wall -Werror -fvisibility=hidden -fPIC -std=c++11 -std=gnu++11 
-MD -MT libshaderc_util/CMakeFiles/shaderc_util.dir/src/resources.cc.o -MF 
CMakeFiles/shaderc_util.dir/src/resources.cc.o.d -o 
CMakeFiles/shaderc_util.dir/src/resources.cc.o -c 
/<>/libshaderc_util/src/resources.cc
/<>/libshaderc_util/src/resources.cc:142:6: error: cannot convert 
‘’ to ‘int’ in initialization
  142 | }};
  |  ^
make[4]: *** [libshaderc_util/CMakeFiles/shaderc_util.dir/build.make:149: 
libshaderc_util/CMakeFiles/shaderc_util.dir/src/resources.cc.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:301: 
libshaderc_util/CMakeFiles/shaderc_util.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:149: all] Error 2

Cheers
-- 
Sebastian Ramacher

Bug#1026726: marked as done (apache-directory-api: FTBFS: [ERROR] /<>/ldap/client/api/src/main/java/org/apache/directory/ldap/client/api/LdapNetworkConnection.java:[4018,22] cannot find s

[Debian Bug Tracking System]

Your message dated Tue, 27 Dec 2022 00:34:41 +
with message-id 
and subject line Bug#1026726: fixed in apache-directory-api 2.1.2-1
has caused the Debian Bug report #1026726,
regarding apache-directory-api: FTBFS: [ERROR] 
/<>/ldap/client/api/src/main/java/org/apache/directory/ldap/client/api/LdapNetworkConnection.java:[4018,22]
 cannot find symbol
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.)


-- 
1026726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache-directory-api
Version: 1.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibapache-directory-api-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Directory LDAP API  
> [pom]
> [INFO] Apache Directory LDAP API I18n 
> [jar]
> [INFO] Apache Directory LDAP API Utilities
> [jar]
> [INFO] Apache Directory API ASN.1 Parent  
> [pom]
> [INFO] Apache Directory API ASN.1 API 
> [jar]
> [INFO] Apache Directory API ASN.1 BER 
> [jar]
> [INFO] Apache Directory LDAP API Parent   
> [pom]
> [INFO] Apache Directory LDAP API Model
> [jar]
> [INFO] Apache Directory LDAP API Codec Parent 
> [pom]
> [INFO] Apache Directory LDAP API Codec Core   
> [jar]
> [INFO] Apache Directory LDAP API Net Parent   
> [pom]
> [INFO] Apache Directory LDAP API Network MINA 
> [jar]
> [INFO] Apache Directory LDAP API Extras   
> [pom]
> [INFO] Apache Directory LDAP API Extras Codec API 
> [jar]
> [INFO] Apache Directory LDAP API Extras Codec 
> [jar]
> [INFO] Apache Directory LDAP API Codec Standalone 
> [jar]
> [INFO] Apache Directory LDAP API DSML Parent  
> [pom]
> [INFO] Apache Directory LDAP API DSML Parser  
> [jar]
> [INFO] Apache Directory LDAP API Extras ACI   
> [jar]
> [INFO] Apache Directory LDAP API Schema Parent
> [pom]
> [INFO] Apache Directory LDAP API Schema Data  
> [jar]
> [INFO] Apache Directory LDAP API Client Parent
> [pom]
> [INFO] Apache Directory LDAP API Client API   
> [jar]
> [INFO] Apache Directory LDAP API DSML Engine  
> [jar]
> [INFO] Apache Directory LDAP API Extras Util  
> [jar]
> [INFO] Apache Directory LDAP API Extras Stored Procedures 
> [jar]
> [INFO] Apache Directory LDAP API Extras Trigger   
> [jar]
> [INFO] Apache Directory LDAP API Schema Converter 
> [jar]
> [INFO] Apache Directory API All   
> [jar]
> [INFO] 
> [INFO] < org.apache.directory.api:api-parent 
> >-
> [INFO] Building Apache Directory LDAP API 1.0.0  
> [1/29]
> [INFO] 

Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #

[Antonio Terceiro]

Control: reassign -1 ruby-rspec-expectations
Control: retitle -1 ruby-rspec-expectations: raise_error() matcher does not 
work  with ruby3.1
Control: forwarded -1 https://github.com/rspec/rspec-expectations/issues/1338
Control: affects -1 src:ruby-hashie

On Sat, Nov 19, 2022 at 03:29:31PM +0200, Adrian Bunk wrote:
> Control: tags -1 fixed-upstream
[...]
> This seems to be fixed in 5.0.0.

It turns out this is a problem rspec-expectations on ruby3.1. The latest
upstream should fix this.


signature.asc
Description: PGP signature

Processed: Re: Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ruby-rspec-expectations
Bug #1019628 [src:ruby-hashie] ruby-hashie: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:expected NoMethodError with "The property 
'middle_name' is not defined for DashTest.", got # retitle -1 ruby-rspec-expectations: raise_error() matcher does not work  with 
> ruby3.1
Bug #1019628 [ruby-rspec-expectations] ruby-hashie: FTBFS with ruby3.1: ERROR: 
Test "ruby3.1" failed:expected NoMethodError with "The property 
'middle_name' is not defined for DashTest.", got # forwarded -1 https://github.com/rspec/rspec-expectations/issues/1338
Bug #1019628 [ruby-rspec-expectations] ruby-rspec-expectations: raise_error() 
matcher does not work  with ruby3.1
Set Bug forwarded-to-address to 
'https://github.com/rspec/rspec-expectations/issues/1338'.
> affects -1 src:ruby-hashie
Bug #1019628 [ruby-rspec-expectations] ruby-rspec-expectations: raise_error() 
matcher does not work  with ruby3.1
Added indication that 1019628 affects src:ruby-hashie

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

Bug#1026679: marked as done (maven-ejb-plugin: FTBFS: make: *** [debian/rules:4: build] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 23:21:49 +
with message-id 
and subject line Bug#1026679: fixed in maven-ejb-plugin 3.2.1-1
has caused the Debian Bug report #1026679,
regarding maven-ejb-plugin: FTBFS: make: *** [debian/rules:4: build] Error 25
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibmaven-ejb-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< org.apache.maven.plugins:maven-ejb-plugin 
> >--
> [INFO] Building Apache Maven EJB Plugin 2.5.1
> [INFO] [ maven-plugin 
> ]
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 
> has been relocated to org.apache.maven.plugins:maven-compiler-plugin:jar:3.8.1
> [WARNING] The artifact org.apache.maven.plugins:maven-plugin-plugin:jar:3.2 
> has been relocated to org.apache.maven.plugins:maven-plugin-plugin:jar:3.6.0
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated 
> to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3
> [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has 
> been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ 
> maven-ejb-plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> maven-ejb-plugin ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [INFO] Compiling 1 source file to /<>/target/classes
> Use of target 1.6 is no longer supported, switching to 7
> Use of source 1.6 is no longer supported, switching to 7
> [INFO] Some messages have been simplified; recompile with -Xdiags:verbose to 
> get full output
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/src/main/java/org/apache/maven/plugin/ejb/EjbMojo.java:[444,53]
>  incompatible types: 
> java.util.List cannot be 
> converted to 
> java.util.List
> [ERROR] 
> /<>/src/main/java/org/apache/maven/plugin/ejb/EjbMojo.java:[451,35]
>  incompatible types: 
> java.util.List 
> cannot be converted to 
> java.util.List
> [INFO] 2 errors 
> [INFO] -
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  1.316 s
> [INFO] Finished at: 2022-12-20T09:45:31Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
> (de

Bug#1026517: marked as done (gpodder: FTBFS: make: *** [debian/rules:13: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 23:20:59 +
with message-id 
and subject line Bug#1026517: fixed in gpodder 3.11.0-4
has caused the Debian Bug report #1026517,
regarding gpodder: FTBFS: make: *** [debian/rules:13: binary] Error 25
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.)


-- 
1026517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpodder
Version: 3.11.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> make[2]: 'share/dbus-1/services/org.gpodder.service' is up to date.
> make[2]: Leaving directory '/<>'
> /usr/bin/python3 setup.py install --no-compile --root='debian/gpodder' 
> --prefix=usr
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> running build_scripts
> running install_lib
> creating debian/gpodder
> creating debian/gpodder/usr
> creating debian/gpodder/usr/local
> creating debian/gpodder/usr/local/lib
> creating debian/gpodder/usr/local/lib/python3.10
> creating debian/gpodder/usr/local/lib/python3.10/dist-packages
> creating debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/__init__.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/registry.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/download.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/my.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/coverart.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/dbusproxy.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/core.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/services.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/util.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/utilwin32locale.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/youtube.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/utilwin32ctypes.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/log.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/syncui.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/schema.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> creating debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/plugins
> copying build/lib/gpodder/plugins/__init__.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/plugins
> copying build/lib/gpodder/plugins/soundcloud.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/plugins
> copying build/lib/gpodder/model.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/player.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/extensions.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/sync.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> copying build/lib/gpodder/vimeo.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder
> creating debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/gtkui
> copying build/lib/gpodder/gtkui/__init__.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/gtkui
> copying build/lib/gpodder/gtkui/download.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/gtkui
> copying build/lib/gpodder/gtkui/services.py -> 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/gtkui
> creating 
> debian/gpodder/usr/local/lib/python3.10/dist-packages/gpodder/gtkui/interface
> copying build/lib/gpodder/gtkui/i

Processed: Re: libllvm15: Packages depending on libllvm15:i386 fail to install because of version mistmatch

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1025530
Bug #1027026 [libllvm15] libllvm15: Packages depending on libllvm15:i386 fail 
to install because of version mistmatch
1027026 was not blocked by any bugs.
1027026 was not blocking any bugs.
Added blocking bug(s) of 1027026: 1025530

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

Bug#1024220: marked as done (deepin-screen-recorder: FTBFS with libproc2)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 22:51:12 +
with message-id 
and subject line Bug#1024220: fixed in deepin-screen-recorder 5.8.0.46-3
has caused the Debian Bug report #1024220,
regarding deepin-screen-recorder: FTBFS with libproc2
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.)


-- 
1024220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: deepin-screen-recorder
Severity: important
Tags: upstream ftbfs


Hi,

The procps project is changing the libprocps library.  The old API found in
libprocps8 is very diferrent to what is found in libproc2.

As a result, your package will FTBFS as the library name has changed as well
as the library calls.

All is not lost, for most of the dependent projects there are already patches
available to close to it. I have also ported programs from the old to the new
libraries so can assist.

The libproc2 packages are found in procps 4.0.1+ in experimental.

 - Craig



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

Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: deepin-screen-recorder
Source-Version: 5.8.0.46-3
Done: Arun Kumar Pariyar 

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

Debian distribution maintenance software
pp.
Arun Kumar Pariyar  (supplier of updated 
deepin-screen-recorder 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, 27 Dec 2022 03:27:57 +0545
Source: deepin-screen-recorder
Architecture: source
Version: 5.8.0.46-3
Distribution: unstable
Urgency: medium
Maintainer: Arun Kumar Pariyar 
Changed-By: Arun Kumar Pariyar 
Closes: 1024220
Changes:
 deepin-screen-recorder (5.8.0.46-3) unstable; urgency=medium
 .
   * Add patch to fix ftbfs with libproc2. (Closes: #1024220)
   * debian/control: Replace libprocps-dev with libproc2-dev.
Checksums-Sha1:
 7b18a1577d732f5d68822d42061a26e5233ee133 2424 
deepin-screen-recorder_5.8.0.46-3.dsc
 cdcb8696ae8fb20d4ad2e5bfc101733c8b1c8b39 5936 
deepin-screen-recorder_5.8.0.46-3.debian.tar.xz
 bf69004c94ff2187057943bdfc4c109f373db41d 15002 
deepin-screen-recorder_5.8.0.46-3_amd64.buildinfo
Checksums-Sha256:
 b3bcee5b8ccaf90de9cd15c1654abda11202ef52c1f3bd996cecf7fa3a862996 2424 
deepin-screen-recorder_5.8.0.46-3.dsc
 3b0cd16433993bcf3cbf3a1b337e957dff8fac4f8f9f1dbefc8aa1bc04225d31 5936 
deepin-screen-recorder_5.8.0.46-3.debian.tar.xz
 f065160872c420cd0c80de770e7ec28080c595ad0fd849ca47216a85515bc0d3 15002 
deepin-screen-recorder_5.8.0.46-3_amd64.buildinfo
Files:
 14db40b948b9e87bd56f0a1a2124b0f5 2424 utils optional 
deepin-screen-recorder_5.8.0.46-3.dsc
 bfa9b45d44a5e833a381a49a9b5d3a8e 5936 utils optional 
deepin-screen-recorder_5.8.0.46-3.debian.tar.xz
 0370f54eed6951b6103f67b863041079 15002 utils optional 
deepin-screen-recorder_5.8.0.46-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAmOqIPwACgkQS1Qq9wT3
RRYF5g/9ER3utpilQqgjNouaKedqsu4R6ChAAl1oo2sw7/3o9E2+i1xGvLL8fckL
0L6fIeukhcbos/PTr258F88/Js+MRfWxBmAHpmPvrxV7BSg7vuRgu/2oN8Qg215k
YXcEu/OhrqXD9ZvqZ7MWi3yTdNaH32MRFqqrN0eDBaDqRhUVGLpr9rbP3RbawqUE
YHvwu2IJRfgKaYjAZnlapjSlZoUd5CzHPVY3Kfzo9LJJdbcqm9K0AXPdQ635Salr
SAZQPIfFg78974czPF7YMhacGr1lE+abwuqiiJXFZA3kyTc1KGZSBna2Qte1ALcC
YXCnqvPzZCFEI8bPtI3ZrAeSW1cZK86q84lKEBmWTiyz/jzRJERYZsjIE3t++mFL
Nq5aFkqjwFmO60hxwJjqA4yHZpS5FEJJbHUSLRmt2SbE9/oMQsOKNCc9vGZJmjmX
vrrOdR1PdRyDTDGmNtD2NVPVD0MBtYjBN6VQjP1mSvfXWgi3a4H0OM8umGGGUAl4
HzJ1gfQjmcvA7Ty8G5IFfPKlziCYQsmDzZkwzpO+XDePRABRoFZZBn3ZTLbau1uD
B4a1vs+7ca47AhcMGjYjOdm4kUBd+XVK4K1Bft+4oJpl9jLLTWqZSCx9Fm04nOcB
LAWnMnT5W9EdjBPuOVqn69mvS2MFkMWm2wYoIT+T0eBgqgLWpxA=
=nrIy
-END PGP SIGNATURE End Me

Processed: Bug#1026679 marked as pending in maven-ejb-plugin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026679 [src:maven-ejb-plugin] maven-ejb-plugin: FTBFS: make: *** 
[debian/rules:4: build] Error 25
Added tag(s) pending.

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

Bug#1026679: marked as pending in maven-ejb-plugin

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #1026679 in maven-ejb-plugin 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/java-team/maven-ejb-plugin/-/commit/247573e018aef623c2993cec77f60dd11f15c182


Fixed the compatibility with maven-filtering 3.3.0 (Closes: #1026679)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026679

Processed: tagging 1015619, tagging 1015621, tagging 1015620, tagging 1015618, tagging 1015614, tagging 1015616 ...

[Debian Bug Tracking System]

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

> tags 1015619 - bookworm sid
Bug #1015619 {Done: Patrick Franz } [src:qt6-declarative] 
qt6-declarative: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015621 - bookworm sid
Bug #1015621 {Done: Patrick Franz } [src:qt6-multimedia] 
qt6-multimedia: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015620 - bookworm sid
Bug #1015620 {Done: Patrick Franz } [src:qt6-lottie] 
qt6-lottie: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015618 - bookworm sid
Bug #1015618 {Done: Patrick Franz } [src:qt6-charts] 
qt6-charts: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015614 - bookworm sid
Bug #1015614 {Done: Patrick Franz } [src:qt6-3d] qt6-3d: 
ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015616 - bookworm sid
Bug #1015616 {Done: Patrick Franz } [src:qt6-5compat] 
qt6-5compat: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015623 - bookworm sid
Bug #1015623 {Done: Patrick Franz } [src:qt6-svg] qt6-svg: 
ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015627 - bookworm sid
Bug #1015627 {Done: Patrick Franz } [src:qt6-wayland] 
qt6-wayland: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015629 - bookworm sid
Bug #1015629 {Done: Patrick Franz } [src:qt6-webchannel] 
qt6-webchannel: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015625 - bookworm sid
Bug #1015625 {Done: Patrick Franz } [src:qt6-tools] 
qt6-tools: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> fixed 1000158 2:4.16.0+dfsg-1
Bug #1000158 {Done: Michael Tokarev } [samba] samba: random 
segfaults since upgrading to bullseye
Marked as fixed in versions samba/2:4.16.0+dfsg-1.
> tags 1027013 - sid bookworm
Bug #1027013 [src:llvm-toolchain-14] llvm-toolchain-14 autopkg test fails
Removed tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1000158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000158
1015614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015614
1015616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015616
1015618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015618
1015619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015619
1015620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015620
1015621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015621
1015623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015623
1015625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015625
1015627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015627
1015629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015629
1027013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026656: marked as done (maven-war-plugin: FTBFS: make: *** [debian/rules:4: build] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 21:53:42 +
with message-id 
and subject line Bug#1026656: fixed in maven-war-plugin 3.3.2-2
has caused the Debian Bug report #1026656,
regarding maven-war-plugin: FTBFS: make: *** [debian/rules:4: build] Error 25
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibmaven-war-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< org.apache.maven.plugins:maven-war-plugin 
> >--
> [INFO] Building Apache Maven WAR Plugin 3.3.2
> [INFO] [ maven-plugin 
> ]
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 
> has been relocated to org.apache.maven.plugins:maven-compiler-plugin:jar:3.8.1
> [WARNING] The artifact org.apache.maven.plugins:maven-plugin-plugin:jar:3.2 
> has been relocated to org.apache.maven.plugins:maven-plugin-plugin:jar:3.6.0
> [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has 
> been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ 
> maven-war-plugin ---
> [WARNING] File encoding has not been set, using platform encoding UTF-8. 
> Build is platform dependent!
> [WARNING] See https://maven.apache.org/general.html#encoding-warning
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> maven-war-plugin ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [INFO] Compiling 21 source files to /<>/target/classes
> Use of target 1.3 is no longer supported, switching to 7
> Use of source 1.3 is no longer supported, switching to 7
> [INFO] 
> /<>/src/main/java/org/apache/maven/plugins/war/packaging/WarPackagingContext.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/main/java/org/apache/maven/plugins/war/packaging/WarPackagingContext.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] Some messages have been simplified; recompile with -Xdiags:verbose to 
> get full output
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/src/main/java/org/apache/maven/plugins/war/packaging/AbstractWarPackagingTask.java:[266,105]
>  incompatible types: 
> java.util.List 
> cannot be converted to 
> java.util.List
> [ERROR] 
> /<>/src/main/java/org/apache/maven/plugins/war/AbstractWarMojo.java:[514,77]
>  incompatible types: 
> java.util.List cannot be 
> converted to 
> java.util.List
> [ERROR] 
> /<>/src/main/java/org/apache/maven/plugins/war/packaging/WarProjectPackagingTask.java:[251,85]
>  incompatible types: 
> java.util.List 
> cannot be converted to 
> java.util.List
> [ERROR] 
> /<>/src/main/java/org/apache/maven/

Bug#1003665: marked as done (php-horde-core: (autopkgtest) needs update for php8.1: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 21:54:17 +
with message-id 
and subject line Bug#1003665: fixed in php-horde-url 2.2.6-9
has caused the Debian Bug report #1003665,
regarding php-horde-core: (autopkgtest) needs update for php8.1: deprecation 
warnings on stderr
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.)


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

Source: php-horde-core
Version: 2.31.16+debian0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-core fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing92
php-horde-core from testing2.31.16+debian0-2
versioned deps 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 of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs my be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php8.1 transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/976811
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-core/18254597/log.gz

Generating locales (this might take a while)...
  en_US.UTF-8... done
  en_US.UTF-8... done
Generation complete.
PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/Factory/GroupTest.php
   Class name was 'Horde_Core_Factory_GroupTest', expected 
'GroupTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php
   Class name was 'Horde_Core_Factory_KolabServerTest', 
expected 'KolabServerTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabSessionTest.php
   Class name was 'Horde_Core_Factory_KolabSessionTest', 
expected 'KolabSessionTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/NlsconfigTest.php
   Class name was 'Horde_Core_NlsconfigTest', expected 
'NlsconfigTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/RegistryTest.php
   Class name was 'Horde_Core_RegistryTest', expected 
'RegistryTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/SmartmobileUrlTest.php
   Class name was 'Horde_Core_SmartmobileUrlTest', expected 
'SmartmobileUrlTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/UrlTest.php

   Class name was 'Horde_Core_UrlTest', expecte

Bug#1011701: marked as done (python-bitcoinlib: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.10" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 21:54:26 +
with message-id 
and subject line Bug#1011701: fixed in python-bitcoinlib 0.11.2-1
has caused the Debian Bug report #1011701,
regarding python-bitcoinlib: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.9 3.10" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/bech32.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/signature.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/segwit_addr.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/bloom.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/messages.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/base58.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/signmessage.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/rpc.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/wallet.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> copying bitcoin/net.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin
> creating /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_fakebitcoinproxy.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_segwit.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_net.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_signmessage.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_wallet.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_base58.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_scripteval.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_messages.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_core.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_key.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_checkblock.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_transactions.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_bloom.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_script.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_serialize.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_rpc.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/test_bech32.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> copying bitcoin/tests/fakebitcoinproxy.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/tests
> creating /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/core
> copying bitcoin/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/core
> copying bitcoin/core/_bignum.py -> 
> /<>/.pybuild/cpython3_3.9_bitcoinlib/build/bitcoin/core
> copying bitcoin/core/key.py 

Bug#1021686: marked as done (zxing-cpp: FTBFS: error: static assertion failed: Cannot format an argument.)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 21:55:28 +
with message-id 
and subject line Bug#1021686: fixed in zxing-cpp 1.4.0-1~exp2.1
has caused the Debian Bug report #1021686,
regarding zxing-cpp: FTBFS: error: static assertion failed: Cannot format an 
argument.
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.)


-- 
1021686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zxing-cpp
Version: 1.4.0-1~exp2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

zxing-cpp/experimental recently started to FTBFS (but the version in sid
is not affected).

...
[ 90%] Building CXX object 
test/blackbox/CMakeFiles/ReaderTest.dir/BlackboxTestRunner.cpp.o
cd /build/zxing-cpp-1.4.0/obj-x86_64-linux-gnu/test/blackbox && /usr/bin/c++ 
-DFMT_SHARED -DZX_USE_UTF8 -I/build/zxing-cpp-1.4.0/core/src -isystem 
/usr/include/stb -g -O2 -ffile-prefix-map=/build/zxing-cpp-1.4.0=. 
-fstack-protector-strong -Wformat -Werror=format-security
 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -MD -MT 
test/blackbox/CMakeFiles/ReaderTest.dir/BlackboxTestRunner.cpp.o -MF 
CMakeFiles/ReaderTest.dir/BlackboxTestRunner.cpp.o.d -o 
CMakeFiles/ReaderTest.dir/BlackboxTestRunner.cpp.o -c 
/build/zxing-cpp-1.4.0/test/blackbox/Bla
ckboxTestRunner.cpp
[ 91%] Building CXX object 
example/CMakeFiles/ZXingQtReader.dir/ZXingQtReader_autogen/mocs_compilation.cpp.o
cd /build/zxing-cpp-1.4.0/obj-x86_64-linux-gnu/example && /usr/bin/c++ 
-DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-I/build/zxing-cpp-1.4.0/obj-x86_64-linux-gnu/example/ZXingQtReader_autogen/include
 -I/build/zxing-cpp-1.4.0/core/src -isystem /usr/include/x86_64-linux-gnu/qt
5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 
-ffile-prefix-map=/build/zxing-cpp-1.4.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdat
e-time -D_FORTIFY_SOURCE=2 -fPIC -std=c++11 -MD -MT 
example/CMakeFiles/ZXingQtReader.dir/ZXingQtReader_autogen/mocs_compilation.cpp.o
 -MF 
CMakeFiles/ZXingQtReader.dir/ZXingQtReader_autogen/mocs_compilation.cpp.o.d -o 
CMakeFiles/ZXingQtReader.dir/ZXingQtReader_autogen/moc
s_compilation.cpp.o -c 
/build/zxing-cpp-1.4.0/obj-x86_64-linux-gnu/example/ZXingQtReader_autogen/mocs_compilation.cpp
In file included from 
/build/zxing-cpp-1.4.0/test/blackbox/BlackboxTestRunner.cpp:17:
/usr/include/fmt/core.h: In instantiation of 'constexpr 
fmt::v9::detail::value fmt::v9::detail::make_value(T&&) [with Context 
= fmt::v9::basic_format_context; T = 
std::filesystem::__cxx11::path&]':
/usr/include/fmt/core.h:1777:29:   required from 'constexpr 
fmt::v9::detail::value fmt::v9::detail::make_arg(T&&) [with bool 
IS_PACKED = true; Context = fmt::v9::basic_format_context; type  = fmt::v9::detail::type::custom_type
; T = std::filesystem::__cxx11::path&; typename std::enable_if::type  = 0]'
/usr/include/fmt/core.h:1901:77:   required from 'constexpr 
fmt::v9::format_arg_store::format_arg_store(T&& ...) [with T = 
{std::filesystem::__cxx11::path&, int&, long unsigned int&}; Context = 
fmt::v9::basic_format_context; Args =
 {std::filesystem::__cxx11::path, int, long unsigned int}]'
/usr/include/fmt/core.h:1918:31:   required from 'constexpr 
fmt::v9::format_arg_store::type>::type ...> fmt::v9::make_format_args(Args&& 
...) [with Context = basic_format_context; Args
= {std::filesystem::__cxx11::path&, int&, long unsigned int&}]'
/usr/include/fmt/core.h:3294:44:   required from 'void 
fmt::v9::print(format_string, T&& ...) [with T = 
{std::filesystem::__cxx11::path&, int&, long unsigned int}; format_string = basic_format_string]'
/build/zxing-cpp-1.4.0/test/blackbox/BlackboxTestRunner.cpp:214:13:   required 
from here
/usr/include/fmt/core.h:1757:7: error: static assertion failed: Cannot format 
an argument. To make type T formattable provide a formatter specialization: 
https://fmt.dev/latest/api.html#udt
 1757 |   formattable,
  |   ^~~
/usr/include/fmt/core.h:1757:7: note: 'formattable' evaluates to false
[ 92%] Building CXX object 
example/CMakeFiles/ZXingQtReader.dir/ZXingQtReader.cpp.o
cd /build/zxing-cpp-1.4.0/obj-x86_64-linux-gnu/example && /usr/bin/c++ 
-DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-I/build/zxing-cpp-1.4.0/obj-x86_64-linux-gnu/example/ZXingQtReader_autogen/include
 -I/build/zxing-cpp-1.4.0/core/src -isystem /usr/include/x86_64-linux-gnu/qt5 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/us

Bug#1027029: marked as done (llvm-toolchain-13: FTBFS with grpc 1.51)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 21:30:48 +
with message-id 
and subject line Bug#1027029: fixed in llvm-toolchain-13 1:13.0.1-11
has caused the Debian Bug report #1027029,
regarding llvm-toolchain-13: FTBFS with grpc 1.51
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-13&arch=amd64&ver=1%3A13.0.1-10%2Bb1&stamp=1671890995&raw=0

[5383/7347] : && /<>/build-llvm/./bin/clang++ 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
-fdata-sections 
-ffile-prefix-map=/<>/build-llvm/tools/clang/stage2-bins=build-llvm/tools/clang/stage2-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes -fno-common 
-Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -Wl,-z,relro 
-Wl,--build-id -fuse-ld=gold-Wl,-O3 -Wl,--gc-sections 
tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o
 -o bin/clangd-index-server-monitor  -Wl,-rpath,"\$ORIGIN/../lib"  
lib/libclangBasic.a  lib/libclangdSupport.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexServiceProto.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexProto.a  lib/libLLVM-13.so.1  
/usr/lib/x86_64-linux-gnu/libgrpc++.so  
/usr/lib/x86_64-linux-gnu/libprotobuf.so && :
FAILED: bin/clangd-index-server-monitor 
: && /<>/build-llvm/./bin/clang++ -fstack-protector-strong 
-Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
-fdata-sections 
-ffile-prefix-map=/<>/build-llvm/tools/clang/stage2-bins=build-llvm/tools/clang/stage2-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes -fno-common 
-Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -Wl,-z,relro 
-Wl,--build-id -fuse-ld=gold-Wl,-O3 -Wl,--gc-sections 
tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o
 -o bin/clangd-index-server-monitor  -Wl,-rpath,"\$ORIGIN/../lib"  
lib/libclangBasic.a  lib/libclangdSupport.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexServiceProto.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexProto.a  lib/libLLVM-13.so.1  
/usr/lib/x86_64-linux-gnu/libgrpc++.so  
/usr/lib/x86_64-linux-gnu/libprotobuf.so && :
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
clang++: error: linker command failed with exit code 1 (use -v to see 
invocation)
[5384/7347] : && /usr/bin/cmake -E rm -f lib/libclangSema.a && 
/<>/build-llvm/bin/llvm-ar Dqc lib/libclangSema.a  
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/AnalysisBasedWarnings.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/CodeCompleteConsumer.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/DeclSpec.cpp.o 
t

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 1003665 php-horde-url
Bug #1003665 [src:php-horde-core] php-horde-core: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Bug reassigned from package 'src:php-horde-core' to 'php-horde-url'.
No longer marked as found in versions php-horde-core/2.31.16+debian0-2.
Ignoring request to alter fixed versions of bug #1003665 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1027037: backdoor-factory: Backdoor-factory isn't working after python3 transition

[Carlos Henrique Lima Melara]

Source: backdoor-factory
Version: 3.4.2+dfsg-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: charlesmel...@outlook.com

Dear Maintainers, hi.

I was working to get a new debian release of backdoor-factory (bdf) before the
freeze and noted while testing it that it doesn't work with python3.

I tested the application trying to patch a binary in 4 scenarios:

1. ELF binary - ssh with -fPIE compiler flag set (it
shouldn't work as warned in the man page);
2. ELF binary - devtodo without -fPIE flag set (I've built it locally
and disabled hardening option in d/rules);
3. PE binary - premake4.exe;
4. PE binary - PSTools from microsoft (the one actually show in the README 
example).

In all test scenarios, bdf showed a message saying the binary wasn't
compatible although they were in 3 out of 4 scenarios.

Digging a little deeper in the source code, I've found the problem.
Even though bdf was patched to build with python3, those changes only
fixed syntactic problems (mostly print statements). The actual problem -
and source of the bug - is the change on how files are read in python3.

In python2, everything read from a file was considered a string. But in
python3 it is considered a bitearray if the file was opened as a binary
('rb' option for example). In the source code of bdf, everything is treated
as strings (comparisons, assignments, operations, etc), but now everything
read from the binary file is a bytearray so the program fails to
identify it as a susceptible binary.

Even though it would be easy to patch this to make bdf correctly
identify the file, every step after that would also need to be fixed
(Right now, it basicaly fails to identify the files as susceptible and
exits). That would require a major rewrite of the program, together with
testing and debugging.

Cheers,
Charles

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

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

Bug#1023530: nut: flaky autopkgtest: varying failures

[Laurent Bigonville]

On Sun, 6 Nov 2022 07:30:38 +0100 Paul Gevers  wrote:

> Dear maintainer(s),

Hello Paul

> I looked at the results of the autopkgtest of your package. I noticed
> that it regularly fails (after the fix for bug #1019221).
>
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
>
> Don't hesitate to reach out if you need help and some more information
> from our infrastructure.

It's impossible for me to reproduce this locally, can you still see that 
in the CI runs?


For me this looks like a race condition, the test code already waits for 
2 sec after the start of the nut daemon an drivers to be certain that 
everything is properly started. I can increase that sleep, but that's 
probably not the best solution. An other solution is to have a loop 
checking that the (dummy) driver is really connected, but I need to 
investigate how and I've no time ATM.


Last solution could be to ask the release team to tag this bug as 
"bookworm-ignore" so it can be part of the upcoming release and try to 
fix this for the next one.


WDYT?

Kind regards,

Laurent Bigonville

Bug#1022303: marked as done (rubygems: FTBFS: ERROR: Test "ruby3.0" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 20:52:39 +0100
with message-id 
and subject line Re: Bug#1022303: rubygems: FTBFS: ERROR: Test "ruby3.0" failed.
has caused the Debian Bug report #1022303,
regarding rubygems: FTBFS: ERROR: Test "ruby3.0" 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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -e gem\ \"rubygems-update\"
> GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -e gem\ \"bundler\"
> 
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -S rake -f debian/ruby-tests.rake
> mv bundler/spec/realworld/fixtures/warbler/Gemfile.lock 
> bundler/spec/realworld/fixtures/warbler/.gem2deb.Gemfile.lock
> Loaded suite 
> /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader
> Started
> ...
> ...
> ...P
> ===
> Pending: test_extract_symlink_parent_doesnt_delete_user_dir(TestGemPackage): 
> TMPDIR seems too long to add it as symlink into tar
> /<>/test/rubygems/test_gem_package.rb:605:in 
> `test_extract_symlink_parent_doesnt_delete_user_dir'
>  602: destination_user_subdir = File.join destination_user_dir, 'dir'
>  603: FileUtils.mkdir_p destination_user_subdir
>  604: 
>   => 605: pend "TMPDIR seems too long to add it as symlink into tar" if 
> destination_user_dir.size > 90
>  606: 
>  607: tgz_io = util_tar_gz do |tar|
>  608:   tar.add_symlink 'link', destination_user_dir, 16877
> ===
> ...
> ...
> ...
> ...
> ...
> ...
> ...
> ...

Processed: Re: python-xsdata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/tefra/xsdata/commit/775be731
Bug #1026741 [src:python-xsdata] python-xsdata: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit 
code 13
Set Bug forwarded-to-address to 
'https://github.com/tefra/xsdata/commit/775be731'.

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

Bug#1026741: python-xsdata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13

[s3v]

Control: forwarded -1 https://github.com/tefra/xsdata/commit/775be731
thanks

Dear Maintainer,
this is a bug in Python 3.11.1 that was fixed and backported to 3.11.2
(but not released yet).
Upstream skipped problematic test for the time being.

Kind Regards.

[1] 
https://github.com/python/cpython/commit/d4426c829565e3ef922c091ee9bd48bc556f2550
[2] https://docs.python.org/3/whatsnew/changelog.html#changelog [gh-100098]

Bug#1020100: marked as done (projectile FTBFS with emacs 28)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 18:17:22 +
with message-id 
and subject line Bug#1020100: fixed in projectile 2.7.0-1
has caused the Debian Bug report #1020100,
regarding projectile FTBFS with emacs 28
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> find doc -type f -name *.adoc -print0 | \
> xargs -0 asciidoctor -S secure -a webfonts!
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   buttercup -L .
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Running tests on Emacs 28.1
> Running 158 specs.
> 
> projectile-project-name
>   return projectile-project-name when present
>   return projectile-project-name when present (2.42ms)
>   uses projectile-project-name-function to get the project name from the 
> project dir
>   uses projectile-project-name-function to get the project name from the 
> project dir (0.10ms)
>   acts on the current project is not passed a project dir explicitly
>   acts on the current project is not passed a project dir explicitly 
> (0.09ms)
> 
> projectile-prepend-project-name
>   prepends the project name to its parameter
>   prepends the project name to its parameter (0.08ms)
> 
> projectile-expand-root
>   expands a relative path into an absolute path within a project
>   expands a relative path into an absolute path within a project 
> (0.17ms)
> 
> projectile--combine-plists
>   Items in second plist override elements in first
>   Items in second plist override elements in first (0.08ms)
>   Nil elements in second plist do not override elements in first
>   Nil elements in second plist do not override elements in first 
> (0.10ms)
> 
> projectile-register-project-type
>   prepends new projects to projectile-project-types
>   prepends new projects to projectile-project-types (11.29ms)
> 
> projectile-update-project-type
>   Updates existing project in projectile-project-types
>   Updates existing project in projectile-project-types (0.12ms)
>   Error when attempt to update nonexistant project type
>   Error when attempt to update nonexistant project type (0.10ms)
> 
> projectile-project-type
>   detects the type of Projectile's project
>   detects the type of Projectile's project (9.02ms)
>   caches the project type
>   caches the project type (0.90ms)
> 
> projectile-ignored-directory-p
>   checks if directory should be ignored
>   checks if directory should be ignored (0.19ms)
> 
> projectile-ignored-file-p
>   checks if file should be ignored
>   checks if file should be ignored (0.11ms)
> 
> projectile-ignored-files
>   returns list of ignored files
>   returns list of ignored files (0.29ms)
> 
> projectile-ignored-directories
>   returns list of ignored directories
>   returns list of ignored directories (0.28ms)
> 
> projectile-project-ignored-files
>   returns list of project ignored files
>   returns list of project ignored files  FAILED (23.55ms)
> 
> projectile-project-ignored-directories
>   returns list of project ignored directories
>   returns list of project ignored directories  FAILED 
> (0.76ms)
> 
> projectile-project-ignored
>   returns list of ignored files/directories
>   returns list of ignored files/directories (0.14ms)
> 
> projectile-remove-ignored
>   removes ignored folders and files
>   removes ignored folders and files (0.19ms)
> 
> projectile-add-unignored
>   requires explicitly unignoring files inside ignored paths
>   requires explicitly unignoring files inside ignored paths (95.65ms)
>   returns the list of globally unignored files on an unsupported VCS
>   returns the list of globally unignored files on an unsupported VCS 
> (47.67ms)
>   requires explicitly unignoring ignored files inside unignored paths
>   requires explicitly unignoring ignored files inside unignored 
> paths (159.53ms)
> 
> projectile-parse-dirconfig-file
>   parses dirconfig and returns directories to ignore and keep
> [

Bug#1026969: marked as done (ruby-aruba - build-dependencies unsatisfiable in bookworm/sid)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 18:17:39 +
with message-id 
and subject line Bug#1026969: fixed in ruby-aruba 2.1.0-2
has caused the Debian Bug report #1026969,
regarding ruby-aruba - build-dependencies unsatisfiable in bookworm/sid
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.)


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

Package: ruby-aruba
Version: 2.1.0-1
Severity: serious
Justification: rc policy - "Packages must be buildable within the same release"
User:debian...@lists.debian.org
Usertags: edos-uninstallable

ruby-aruba build-depends on rubocop (<< 1.0) but bookworm and sid have version 
1.39.0+dfsg-1
--- End Message ---
--- Begin Message ---
Source: ruby-aruba
Source-Version: 2.1.0-2
Done: Lucas Nussbaum 

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

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated ruby-aruba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 18:55:08 +0100
Source: ruby-aruba
Architecture: source
Version: 2.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Nussbaum 
Closes: 1026969
Changes:
 ruby-aruba (2.1.0-2) unstable; urgency=medium
 .
   * Relax build-dependancy on rubocop (remove version restriction).
 rubocop is only listed in the gemfile because it is used during
 development. It's not actually needed by the package build process.
 Closes: #1026969
Checksums-Sha1:
 4b42703ea946ba62dadcd98c4d2410ed0fa66328 2401 ruby-aruba_2.1.0-2.dsc
 86e452fe8041d84f5cb51dbeb1b03991e72fb2c9 80224 ruby-aruba_2.1.0-2.debian.tar.xz
 0ccaa355d23b663b4479d52d5b6124284244ea48 11992 
ruby-aruba_2.1.0-2_source.buildinfo
Checksums-Sha256:
 9cb540fbbe039d86bcd71d193820b6fefcb8f1dd67c0ef37ba5032530aaab13f 2401 
ruby-aruba_2.1.0-2.dsc
 8d3ba9af986ea55f01b5faa4be795f96e93e89699cef536cb6d60cf3f7bfc02b 80224 
ruby-aruba_2.1.0-2.debian.tar.xz
 1cc9c7b51cf0ed4565f81bbebb85329faac0617a3d8974aedbb2cbfaebd3e547 11992 
ruby-aruba_2.1.0-2_source.buildinfo
Files:
 f46fc36009ba064941eb8ef77323b515 2401 ruby optional ruby-aruba_2.1.0-2.dsc
 f049d95094463698cbd2b277dc1b7632 80224 ruby optional 
ruby-aruba_2.1.0-2.debian.tar.xz
 240f7513169bf0f67e9168627564ba30 11992 ruby optional 
ruby-aruba_2.1.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/t7ByzN7z1CfQ8IkORS1MvTfvpkFAmOp4KwACgkQORS1MvTf
vpmHRw/+NK1vfsrclUu+X52O+JABc7aTqOuJ+1cPOZniuWv0R45OAk44nYopk/v0
f2zOWMFxL5nAg/MBS2e/pzfIq1qJbzDwp+AzsCeufzMJs2kVD66b5w3UjkAG7k6q
E+qcWiDeRsJFpIcVdl+nqgBpMr9FZRLR68otSfK3Jh0lFcIi7V/QXUlLnLQE4hjh
zXA1Wf4bv/DFPB8KkXBaYFythCZ6P/jENaYi7lutYg6tS52srwuki7Q9vRG0dy0t
jUGZG6u0vVBIgw8dODkbuNfOiEZa7JhlJ5TABMFDUToofviw6AhLO9vWpopoGO4F
voXKPrDPD9iJNuvWC5BxmjMEkIHUYdvFG+rYRsXV7AgY6ccRZz2WEa63jVn+a92M
G4a0zNO7x+o5KdgQ1URNcAndE3J7h3aQ9LAbLTB7x/vZCywa4PABceuW11SmDDku
fjqb0gORB1+amq3Ns/Y99IPsax8LuHp6cQ4CSuLhaIv/dNkeGwP/ySRREI0iU/jB
Gdzp9M7DKF94S/hZ35f9qBQNktuvSce8gXSKILMkXp+F360fIYNbbqEOe0gDdk/A
yjHt53QqgC/T/9w7+MMt/oAV+hxQ9MH6VEzOH7V8/H/XPCmTFwz4k8QQWI0JYhpG
DQR1dbPSnuxk+V3X3dAEuGJphrf8ZSQA0WaKyzvmpSwTNuJZ26Q=
=GhE2
-END PGP SIGNATURE End Message ---

Bug#1026892: marked as done (asciidoctor: FTBFS with haml 6.1.1: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 18:06:06 +
with message-id 
and subject line Bug#1026892: fixed in asciidoctor 2.0.18-1
has caused the Debian Bug report #1026892,
regarding asciidoctor: FTBFS with haml 6.1.1: ERROR: Test "ruby3.1" 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.)


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

Hi,

I'm working on updating ruby-haml to the new upstream versinon 6.1.1,
and when trying asciidoctor against that the tests fail.


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-asciidoctor/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"asciidoctor\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-asciidoctor/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-asciidoctor/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"lib:test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/api_test.rb" "test/attribute_list_test.rb" "test/attributes_test.rb" 
> "test/blocks_test.rb" "test/converter_test.rb" "test/document_test.rb" 
> "test/extensions_test.rb" "test/helpers_test.rb" "test/invoker_test.rb" 
> "test/links_test.rb" "test/lists_test.rb" "test/logger_test.rb" 
> "test/manpage_test.rb" "test/options_test.rb" "test/paragraphs_test.rb" 
> "test/parser_test.rb" "test/paths_test.rb" "test/preamble_test.rb" 
> "test/reader_test.rb" "test/sections_test.rb" "test/substitutions_test.rb" 
> "test/syntax_highlighter_test.rb" "test/tables_test.rb" "test/text_test.rb" 
> RUBY_GC_HEAP_FREE_SLOTS=75 (default value: 4096)
> RUBY_GC_HEAP_INIT_SLOTS=75 (default value: 1)
> RUBY_GC_HEAP_GROWTH_FACTOR=2.00 (default value: 1.80)
> RUBY_GC_HEAP_GROWTH_MAX_SLOTS=5 (default value: 0)
> RUBY_GC_MALLOC_LIMIT=12800 (default value: 16777216)
> RUBY_GC_OLDMALLOC_LIMIT=12800 (default value: 16777216)
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85:
>  warning: possibly useless use of a variable in void context
> Run options: --seed 60429
> 
> # Running:
> 
> ...Haml::Engine:
>  Option :attr_wrapper is invalid
> Haml::Engine: Option :attr_wrapper is invalid
> FHaml::Engine: Option :attr_wrapper is invalid
> F.

Processed: Bug#1026726 marked as pending in apache-directory-api

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026726 [src:apache-directory-api] apache-directory-api: FTBFS: [ERROR] 
/<>/ldap/client/api/src/main/java/org/apache/directory/ldap/client/api/LdapNetworkConnection.java:[4018,22]
 cannot find symbol
Added tag(s) pending.

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

Bug#1026726: marked as pending in apache-directory-api

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #1026726 in apache-directory-api 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/java-team/apache-directory-api/-/commit/59f67f6e59ebe7aa65e77473ffc60e0687367789


Depend on libmina2-java (>= 2.2.1) (Closes: #1026726)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026726

Bug#1027020: davmail-server: fails to install: insserv: script davmail-server: service davmail already provided!

[Alexandre Rossi]

Hi,

Thanks for your report.

> When trying to update davmail / install davmail-server I get:
>
>
> Setting up davmail-server (6.0.1.3390-3) ...
> insserv: script davmail-server: service davmail already provided!
> update-rc.d: error: no runlevel symlinks to modify, aborting!
> dpkg: error processing package davmail-server (--configure):
>  installed davmail-server package post-installation script subprocess 
> returned error exit status 1
[...]
> The reason seems to be that /etc/init.d/davmail is still around (and
> has "Provides. davmail")

Thanks for the pointer.

I'm tempted to do the following. Do you have an easy way to confirm it
works for you?
As the fix requires sysvinit, testing it will take me a bit more time.

Thanks,

Alex

--- a/debian/control
+++ b/debian/control
@@ -34,7 +34,7 @@ Package: davmail
 Architecture: all
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends},
- davmail-server,
+ davmail-server (= ${binary:Version}),
  default-jre,
  libswt-cairo-gtk-4-jni,
  libopenjfx-java,
diff --git a/debian/davmail-server.init b/debian/davmail-server.init
index eaa866c6..252141f2 100755
--- a/debian/davmail-server.init
+++ b/debian/davmail-server.init
@@ -1,6 +1,6 @@
 #! /bin/sh
 ### BEGIN INIT INFO
-# Provides:  davmail
+# Provides:  davmail-server
 # Required-Start:$local_fs $remote_fs
 # Required-Stop: $local_fs $remote_fs
 # Default-Start: 2 3 4 5

Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:

[Lucas Nussbaum]

On 17/12/22 at 14:51 +0100, Diederik de Haas wrote:
> On 13 Sep 2022 09:00:07 -0300 Antonio Terceiro  wrote:
> > Source: ruby-safe-yaml
> > Version: 1.0.5-2
> > Justification: FTBFS
> > Usertags: ruby3.1
> > 
> > We are about to start the ruby3.1 transition in unstable. While trying to
> > rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed.
> > 
> > Relevant part of the build log (hopefully):
> > >   ArgumentError:
> > > wrong number of arguments (given 2, expected 1)
> > >   # ./lib/safe_yaml/load.rb:149:in `load'
> > >   # ./lib/safe_yaml.rb:29:in `safe_load'
> > >   # ./spec/safe_yaml_spec.rb:7:in `safe_load_round_trip'
> > >   # ./spec/safe_yaml_spec.rb:745:in `block (4 levels) in  > >   (required)>'
> > > 
> > > Finished in 0.08109 seconds (files took 0.12613 seconds to load)
> > > 134 examples, 20 failures
> > > 
> > > Failed examples:
> > > 
> > > rspec ./spec/safe_yaml_spec.rb:29 # Psych unsafe_load allows exploits 
> > > through objects defined in YAML w/ !ruby/hash via custom :[]= methods
> 
> There is an upstream PR: https://github.com/dtao/safe_yaml/pull/101
> which tried to address this, but someone who tried it still got errors.
> 
> Last upstream commit was from 2019-02-22 and there are several PRs open and 
> it 
> looks like the maintainer hasn't responded to any of them for > 5 YEARS

Since ruby-crack no longer depends on ruby-safe-yaml, ruby-safe-yaml
should probably just be removed from testing (and Debian)...

Lucas


signature.asc
Description: PGP signature

Processed: summary + reducing severity

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 ruby-gtk2: crash if 'include Gtk' is done before require openssl
Bug #1000618 [ruby-gtk2] ruby-gtk2: crashes with openssl: superclass mismatch 
for class Socket (TypeError)
Changed Bug title to 'ruby-gtk2: crash if 'include Gtk' is done before require 
openssl' from 'ruby-gtk2: crashes with openssl: superclass mismatch for class 
Socket (TypeError)'.
> severity -1 normal
Bug #1000618 [ruby-gtk2] ruby-gtk2: crash if 'include Gtk' is done before 
require openssl
Severity set to 'normal' from 'serious'

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

Bug#1000618: summary + reducing severity

[Lucas Nussbaum]

Control: retitle -1 ruby-gtk2: crash if 'include Gtk' is done before require 
openssl
Control: severity -1 normal

Hi,

Summarizing the investigations (thanks!)

The root cause is this code in origami-pdf:

require 'gtk2'
include Gtk
require 'openssl'

this crashes with: superclass mismatch for class Socket (TypeError)

That's because the Gtk module has its own Socket class, which conficts
with the Socket from the standard library.

includ'ing Gtk is probably a bad idea. It would be better if origami-pdf
did not do it. However, a workaround exists, with:

require 'gtk2'
require 'openssl'
include Gtk

I don't think that this bug warrants severity:serious.

Lucas

Bug#1027029: llvm-toolchain-13: FTBFS with grpc 1.51

[Sylvestre Ledru]

Le 26/12/2022 à 17:23, Sebastian Ramacher a écrit :

Source: llvm-toolchain-13
Version: 1:13.0.1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-13&arch=amd64&ver=1%3A13.0.1-10%2Bb1&stamp=1671890995&raw=0


yeah, I have a fix for this

I will do the upload in the next few days.

Cheers

S

Bug#1026245: marked as done (gm2-12-doc,gm2-13-doc: ships unversioned /usr/share/info/gm2.info.gz)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 16:23:22 +
with message-id 
and subject line Bug#1026245: fixed in gcc-13 13-20221226-1
has caused the Debian Bug report #1026245,
regarding gm2-12-doc,gm2-13-doc: ships unversioned /usr/share/info/gm2.info.gz
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.)


-- 
1026245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gm2-12-doc,gm2-13-doc
Severity: serious
Control: found -1 12.2.0-10
Control: found -1 13-20221214-1

Hi,

there is a file conflict between gm2-12-doc and gm2-13-doc:

  Preparing to unpack .../gm2-13-doc_13-20221214-1_all.deb ...
  Unpacking gm2-13-doc (13-20221214-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gm2-13-doc_13-20221214-1_all.deb (--unpack):
   trying to overwrite '/usr/share/info/gm2.info.gz', which is also in package 
gm2-12-doc 12.2.0-10
  Errors were encountered while processing:
   /var/cache/apt/archives/gm2-13-doc_13-20221214-1_all.deb

Please rename that to gm2-XX.info.gz and provide a symlink
in gm2-doc (does not yet exist) like for e.g. gcc-doc.
Do not forget versioned Breaks+Replaces in gm2-doc for taking over
gm2.info.gz from these two packages.


Andreas


gm2-12-doc=12.2.0-10_gm2-13-doc=13-20221214-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-13
Source-Version: 13-20221226-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-13 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: Mon, 26 Dec 2022 16:33:56 +0100
Source: gcc-13
Architecture: source
Version: 13-20221226-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1026201 1026245
Changes:
 gcc-13 (13-20221226-1) experimental; urgency=medium
 .
   * New upstream snapshot, taken from the trunk (m2 and rs merged).
   * Drop gdc build dependency on unsupported architectures. Closes: #1026201.
   * Install versioned gm2 doc files. Closes: #1026245.
Checksums-Sha1:
 de7489adad0c8ac7c33bf0016321aba0bbf509b7 27482 gcc-13_13-20221226-1.dsc
 79f24f820cc6c8f38844d2eaf36cefc10278c5f8 85093933 
gcc-13_13-20221226.orig.tar.gz
 cb218b4254aa35fbdf9d5e0ba1951b1a008aace6 526848 
gcc-13_13-20221226-1.debian.tar.xz
 92559371bd6cfce2a568005157415c0dc6b10464 9827 
gcc-13_13-20221226-1_source.buildinfo
Checksums-Sha256:
 c7432c80fd9945bfd2aa6d7aec92176a0d8991ee1e569cd45a9d9426b5f64903 27482 
gcc-13_13-20221226-1.dsc
 621a38ad9a62eddf7f8df7426e0b4d4e73bb09e91f049080721378f53776f931 85093933 
gcc-13_13-20221226.orig.tar.gz
 5549654f24f9e318e86c436efc31163fcf01a80ebe3f3156809f23049840693c 526848 
gcc-13_13-20221226-1.debian.tar.xz
 2a9a4252348ee009894148d076bb6a8b536b9a51be61a58907a1012dc83f41e2 9827 
gcc-13_13-20221226-1_source.buildinfo
Files:
 3aaabec2efd2db2a60b30cb79b70ab7e 27482 devel optional gcc-13_13-20221226-1.dsc
 3d36b306b94c8abeed0830dd2612de82 85093933 devel optional 
gcc-13_13-20221226.orig.tar.gz
 314512438f46d638caabcaa316905935 526848 devel optional 
gcc-13_13-20221226-1.debian.tar.xz
 b1dc1fd686933033c16f884f4aa4e21c 9827 devel optional 
gcc-13_13-20221226-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmOpvyEQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9VaSEAC/eE9DWEW9MGW2KxdaQkM+vNy7KmJjYvEK
3uPJTO0VYb3h+b/pQfIl978tcD5Hqg7MPLX/opmADYuIwSVhic27SHNTdeiWeO8i
XpasthThCnb1qgEtwvkpEEZS7LcHo497hMJPlfs2EeVyMuxf0SwQQDS1q/4qmxIe
VZAqspWPDDD0PM5OZTbTyV7sM4JW8VOY+EhInS/dvapjB6doRekc2ZFAjm6FvVVY
5LichUcBEpks9/yQGn6vtg43X5wW3gwnEPf3LrNpHGzSjxBiY3I5N5+5mVdfsZP/
zeg0Gu9mPfEfu0NmOm6HpnXK96hMju7SCQRh2wvt5Mm9SyMZDVtsTF8edt5x798j
735/xSOU54SA65Y3bjh69U229nOKoYiGCZNKA0QfqfqoFG0+WPG8xO4mtyv4Wxgu
M2IJXr5Qkg1mHEee3aPo3iY5lggxkvJTGLTQdLFsFeTw+pYJrFnzdYHvCC0N8EAN
NPlc+jHiktoxfe++wqd399/x1lHENPJX906xW8wfURCtLfD7YXx2YS

Bug#1026245: marked as done (gm2-12-doc,gm2-13-doc: ships unversioned /usr/share/info/gm2.info.gz)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 16:23:07 +
with message-id 
and subject line Bug#1026245: fixed in gcc-12 12.2.0-11
has caused the Debian Bug report #1026245,
regarding gm2-12-doc,gm2-13-doc: ships unversioned /usr/share/info/gm2.info.gz
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.)


-- 
1026245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gm2-12-doc,gm2-13-doc
Severity: serious
Control: found -1 12.2.0-10
Control: found -1 13-20221214-1

Hi,

there is a file conflict between gm2-12-doc and gm2-13-doc:

  Preparing to unpack .../gm2-13-doc_13-20221214-1_all.deb ...
  Unpacking gm2-13-doc (13-20221214-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gm2-13-doc_13-20221214-1_all.deb (--unpack):
   trying to overwrite '/usr/share/info/gm2.info.gz', which is also in package 
gm2-12-doc 12.2.0-10
  Errors were encountered while processing:
   /var/cache/apt/archives/gm2-13-doc_13-20221214-1_all.deb

Please rename that to gm2-XX.info.gz and provide a symlink
in gm2-doc (does not yet exist) like for e.g. gcc-doc.
Do not forget versioned Breaks+Replaces in gm2-doc for taking over
gm2.info.gz from these two packages.


Andreas


gm2-12-doc=12.2.0-10_gm2-13-doc=13-20221214-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-12
Source-Version: 12.2.0-11
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-12 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: Mon, 26 Dec 2022 16:39:09 +0100
Source: gcc-12
Architecture: source
Version: 12.2.0-11
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1025948 1026245
Changes:
 gcc-12 (12.2.0-11) unstable; urgency=medium
 .
   * Update to git 20221226 from the gcc-12 branch.
 - Fix PR bootstrap/106482, PR d/104749, PR target/98776 (AArch64),
   PR tree-optimization/107898, PR tree-optimization/107865,
   PR tree-optimization/107833, PR tree-optimization/107839,
   PR tree-optimization/107686, PR tree-optimization/107766,
   PR tree-optimization/107647, PR tree-optimization/107407,
   PR tree-optimization/106868, PR libstdc++/107814, PR libstdc++/108097.
   * Install versioned gm2 doc files. Closes: #1026245.
   * Backport PR driver/93371 from the trunk. Closes: #1025948.
Checksums-Sha1:
 a0c0e729ae62b48504398c7291f4ec6f2ba4c801 27505 gcc-12_12.2.0-11.dsc
 f08db5a91b69f9c359236588587f7480da9cbfe3 1661068 gcc-12_12.2.0-11.debian.tar.xz
 8e1d03bbd09ed9eb42bb6fd7b198bebb9477ddcf 9811 gcc-12_12.2.0-11_source.buildinfo
Checksums-Sha256:
 ddf7ea8cd98fa7c80c683178b9c6184ca600e0ee92ab192490833973cb3ec246 27505 
gcc-12_12.2.0-11.dsc
 aece7a7401dd357dfcb64f4a6dea405e99796bec338ce41f7cbd74250ce9e04d 1661068 
gcc-12_12.2.0-11.debian.tar.xz
 d8488c79d6bcc06efacf6ecb3af974bf785d0de301ac081ec4eb9bb728e27477 9811 
gcc-12_12.2.0-11_source.buildinfo
Files:
 571f13c0363acfddb66c8ca4bc6f224b 27505 devel optional gcc-12_12.2.0-11.dsc
 3d0fbcc62ca64482ac936f533de5e381 1661068 devel optional 
gcc-12_12.2.0-11.debian.tar.xz
 a6ff663ae20bf1d6f2ee27f633c6844b 9811 devel optional 
gcc-12_12.2.0-11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmOpxNUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9Y6eD/0RLFiI7qEILc0ODkhTaf3bZ7zWEWl4mg6I
ThWAbA2T/jNIzfFMffGnDgfrMoDrWcOSGkUUf1M41vzoKRXzbEWGnNoGrYL/r4p/
1b889GrtYcsYNl+P41QZeSll6I9xUam0g2MCxyFZELC5XrksELwDiSJ+D8w2NPat
vAyEwBkTaeItf2xhLElRofVW4NBeSk6+Hwu9OB5L0EWtu3QgAHzwPEaX/X3pkk4t
Z8U2lB61YYBlt55Y9KFOkf0M3v4gnADrSlfHrNvLkrB+nN0I2Lew8a4RUKe07gaQ
JATUbO4ixZc/Q9x1yzDKpoCHCp2aNExnBTOb6EcskPK/PTJx46i2E/B7+gMHY+aw
tJY+srfd21cv2La7WzV/KJxxlHyVT/c2APYXZ6KalgB95Ce+DfmXMUWrDiygIOll
AWZWAjHpSU4SgRlKhGvJ+wgwQi0ANaw6Glgg2TSOMzaY2lqIVgmbar+xyG8aAENn
kHahlXyjkOpiEJSFjYjuJNvMFXI/Cp54IMDu92eyRy3x0/diz3LkIn

Bug#1027029: llvm-toolchain-13: FTBFS with grpc 1.51

[Sebastian Ramacher]

Source: llvm-toolchain-13
Version: 1:13.0.1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-13&arch=amd64&ver=1%3A13.0.1-10%2Bb1&stamp=1671890995&raw=0

[5383/7347] : && /<>/build-llvm/./bin/clang++ 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
-fdata-sections 
-ffile-prefix-map=/<>/build-llvm/tools/clang/stage2-bins=build-llvm/tools/clang/stage2-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes -fno-common 
-Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -Wl,-z,relro 
-Wl,--build-id -fuse-ld=gold-Wl,-O3 -Wl,--gc-sections 
tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o
 -o bin/clangd-index-server-monitor  -Wl,-rpath,"\$ORIGIN/../lib"  
lib/libclangBasic.a  lib/libclangdSupport.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexServiceProto.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexProto.a  lib/libLLVM-13.so.1  
/usr/lib/x86_64-linux-gnu/libgrpc++.so  
/usr/lib/x86_64-linux-gnu/libprotobuf.so && :
FAILED: bin/clangd-index-server-monitor 
: && /<>/build-llvm/./bin/clang++ -fstack-protector-strong 
-Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
-fdata-sections 
-ffile-prefix-map=/<>/build-llvm/tools/clang/stage2-bins=build-llvm/tools/clang/stage2-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes -fno-common 
-Woverloaded-virtual -Wno-nested-anon-types -O2 -DNDEBUG -g1 -Wl,-z,relro 
-Wl,--build-id -fuse-ld=gold-Wl,-O3 -Wl,--gc-sections 
tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o
 -o bin/clangd-index-server-monitor  -Wl,-rpath,"\$ORIGIN/../lib"  
lib/libclangBasic.a  lib/libclangdSupport.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexServiceProto.a  lib/libMonitoringServiceProto.a  
lib/libRemoteIndexProto.a  lib/libLLVM-13.so.1  
/usr/lib/x86_64-linux-gnu/libgrpc++.so  
/usr/lib/x86_64-linux-gnu/libprotobuf.so && :
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
/usr/include/grpcpp/impl/call_op_set.h:978: error: undefined reference to 
'gpr_log'
clang++: error: linker command failed with exit code 1 (use -v to see 
invocation)
[5384/7347] : && /usr/bin/cmake -E rm -f lib/libclangSema.a && 
/<>/build-llvm/bin/llvm-ar Dqc lib/libclangSema.a  
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/AnalysisBasedWarnings.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/CodeCompleteConsumer.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/DeclSpec.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/DelayedDiagnostic.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/IdentifierResolver.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/JumpDiagnostics.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/MultiplexExternalSemaSource.cpp.o
 tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/ParsedAttr.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/Scope.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/ScopeInfo.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/Sema.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/SemaAccess.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/SemaAttr.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.dir/SemaAvailability.cpp.o 
tools/clang/lib/Sema/CMakeFiles/obj.clangSema.

Processed: Re: Bug#1020435: ruby-prof: FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1020435 [src:ruby-prof] ruby-prof: FTBFS on ppc64el
Severity set to 'serious' from 'important'

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

Processed: Re: widelands: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1027028
Bug #1023830 [src:widelands] widelands: FTBFS on s390x
1023830 was not blocked by any bugs.
1023830 was blocking: 1027024
Added blocking bug(s) of 1023830: 1027028

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

Bug#1023830: widelands: FTBFS on s390x

[Tobias Frost]

Control: block -1 by 1027028

FWIIW, I've requested removal of widelands on s390x. Once this is done, this 
bug can be downgraded in severity.

-- 
tobi

Processed: bug 1026731 is forwarded to https://github.com/ionelmc/python-tblib/issues/64

[Debian Bug Tracking System]

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

> forwarded 1026731 https://github.com/ionelmc/python-tblib/issues/64
Bug #1026731 [src:python-tblib] python-tblib: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/ionelmc/python-tblib/issues/64'.
> thanks
Stopping processing here.

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

Bug#1025237: marked as done (scalene: FTBFS with python3.11)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 14:59:09 +
with message-id 
and subject line Bug#1025237: fixed in scalene 1.5.16-1
has caused the Debian Bug report #1025237,
regarding scalene: FTBFS with python3.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.)


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

Source: scalene
Severity: serious
Version: 1.4.1-1

Hello,

scalene FTBFS with added support for python3.11:

building 'scalene.pywhere' extension
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I. -Isrc -Isrc/include -I/usr/include/python3.11 -c 
src/source/pywhere.cpp -o 
build/temp.linux-x86_64-cpython-311/src/source/pywhere.o -std=c++14
src/source/pywhere.cpp: In function ‘int whereInPython(std::string&, 
int&, int&)’:
src/source/pywhere.cpp:176:40: error: ‘PyThreadState’ {aka ‘struct _ts’} 
has no member named ‘frame’; did you mean ‘cframe’?

  176 |   if (threadState == 0 || threadState->frame == 0) {
  |^
  |cframe
src/source/pywhere.cpp:190:34: error: ‘PyThreadState’ {aka ‘struct _ts’} 
has no member named ‘frame’; did you mean ‘cframe’?

  190 |   for (auto frame = threadState->frame; frame != nullptr;
  |  ^
  |  cframe
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.11 setup.py build


Andrius
--- End Message ---
--- Begin Message ---
Source: scalene
Source-Version: 1.5.16-1
Done: Emmanuel Arias 

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

Debian distribution maintenance software
pp.
Emmanuel Arias  (supplier of updated scalene package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 09:33:26 -0300
Source: scalene
Architecture: source
Version: 1.5.16-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Emmanuel Arias 
Closes: 1023633 1025237
Changes:
 scalene (1.5.16-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #1025237, #1023633).
   * d/patches: Update patches according to upstream changes.
   * d/control: Bump Standards-Version to 4.6.1.1 (from 4.6.0; no further
 changes).
   * d/copyright: Update the Source upstream link.
   * d/control: Update Homepage upstream link.
   * d/copyright: Update the upstream name and contact email in the file.
   * d/python3-scalene.install: install scalene-gui in
 /usr/share/python3-scalene/.
 - d/patches: Add 0005-Point-to-the-debianize-scalene-gui-path.patch to
 redirect correctly the scalene-gui path.
 - d/control: Add libjs-bootstrap4 and libjs-jquery as dependency of the
 package. These are used by the scalene-gui.
   * d/patches: Add 0004-Remove-links-to-external-resource.patch patch to
 remove links for external libs.
   * d/rules: Fix where the *.so files are installed. Now they are living in
 /usr/lib/python*/dist-packages/scalene/.
 - Add Debian SOABI name to crdp and get_line_atomic extensions.
   * d/source/lintian-overrides: Override source-is-missing,
 very-long-line-length-in-source-file and
 source-contains-prebuilt-javascript-object they are because scalene-gui
 contains some js files.
 - python3-scalene.lintian-overrides: Override privacy-breach-generic, this
 is because scalene-gui use vega-embed and vega-lite and they are not in
 Debian yet.
   * d/patches/0006-Add-hardening-flags-in-the-build.patch: Add patch to use
 CXXFLAGS, CPPFLAGS and LDFLAGS in build to solve hardening issues.
 - d/rules: Change DEB_BUILD_MAINT_OPTIONS to hardening=+al

Bug#1023633: marked as done (python3-scalene: can't import (or execute) scalene)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 14:59:09 +
with message-id 
and subject line Bug#1023633: fixed in scalene 1.5.16-1
has caused the Debian Bug report #1023633,
regarding python3-scalene: can't import (or execute) scalene
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.)


-- 
1023633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-scalene
Version: 1.4.1-1
Severity: important
X-Debbugs-Cc: david.m.co...@gmail.com

Dear Maintainer,

Running scalene, either with the CLI command `scalene`, or `python3.10 -m
scalene`, or `python3.9 -m scalene`, causes this (or similiar) import error:

Traceback (most recent call last):
  File "/usr/bin/scalene", line 33, in 
sys.exit(load_entry_point('scalene==1.4.1', 'console_scripts',
'scalene')())
  File "/usr/bin/scalene", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in _find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/scalene/__main__.py", line 4, in

from scalene import scalene_profiler
  File "/usr/lib/python3/dist-packages/scalene/scalene_profiler.py", line 46,
in 
from scalene.scalene_mapfile import ScaleneMapFile
  File "/usr/lib/python3/dist-packages/scalene/scalene_mapfile.py", line 6, in

from scalene import get_line_atomic  # type: ignore
ImportError: cannot import name 'get_line_atomic' from 'scalene'
(/usr/lib/python3/dist-packages/scalene/__init__.py)

The problem is easily traced to the included get_line_atomic C extension
being installed to /usr/lib/scalene/lib, which is not on Python's search
path for modules.  Extension modules should be installed alongside their
pure-Python companions, in /usr/lib/python3/dist-packages (see: every other
Python package with a C extension.)

This also explains why the generated manpage is a duplicate of `python3 -h`.


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

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

Versions of packages python3-scalene depends on:
ii  libc62.36-4
ii  libgcc-s112.2.0-9
ii  libstdc++6   12.2.0-9
ii  python3  3.10.6-1
ii  python3-cloudpickle  2.0.0-1
ii  python3-numpy1:1.21.5-1+b1
ii  python3-rich 12.4.4-1

Versions of packages python3-scalene recommends:
ii  python3-ipython  8.5.0-1
ii  python3-pynvml   11.515.75-1

python3-scalene suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: scalene
Source-Version: 1.5.16-1
Done: Emmanuel Arias 

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

Debian distribution maintenance software
pp.
Emmanuel Arias  (supplier of updated scalene package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 09:33:26 -0300
Source: scalene
Architecture: source
Version: 1.5.16-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Emmanuel Arias 
Closes: 1023633 1025237
Changes:
 scalene (1.5.16-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #1025237, #1023633).
   * d/patches: Update patches according to upstream changes.
   * d/control: Bump Standards-Version to 4.6

Bug#1027027: src:android-platform-build-kati: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: android-platform-build-kati
Version: 10.0.0+r32-6
Severity: serious
Control: close -1 10.0.0+r32+git20220314.09dfa26c4e59-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1023766

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:android-platform-build-kati has been 
trying to migrate for 61 days [2]. Hence, I am filing this bug. Your 
package is blocked by an autopkgtest regression that I reported in bug 
1023766.


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=android-platform-build-kati



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:android-platform-build-kati: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 10.0.0+r32+git20220314.09dfa26c4e59-3
Bug #1027027 [src:android-platform-build-kati] src:android-platform-build-kati: 
fails to migrate to testing for too long: autopkgtest regression
Marked as fixed in versions 
android-platform-build-kati/10.0.0+r32+git20220314.09dfa26c4e59-3.
Bug #1027027 [src:android-platform-build-kati] src:android-platform-build-kati: 
fails to migrate to testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1023766
Bug #1027027 {Done: Paul Gevers } 
[src:android-platform-build-kati] src:android-platform-build-kati: fails to 
migrate to testing for too long: autopkgtest regression
1027027 was not blocked by any bugs.
1027027 was not blocking any bugs.
Added blocking bug(s) of 1027027: 1023766

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

Bug#1027024: src:widelands: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: widelands
Version: 2:1.0-4
Severity: serious
Control: close -1 2:1.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1023830

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:widelands has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package FTBFS on s390x as 
reported in bug 1023830.


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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027025: psi4: FTBFS with Python 3.11 as default version

[Graham Inggs]

Source: psi4
Version: 1:1.3.2+dfsg-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

Psi4 fails its build-time tests with Python 3.11 as the default
version, although the build doesn't fail outright, probably because of
the following in debian/rules:

override_dh_auto_test:
mkdir -p $(CURDIR)/builddir/tmp-scratch
-(cd builddir/tests; CTEST_OUTPUT_ON_FAILURE=TRUE ctest -L quicktests)

I've copied what I hope is the relevant part of the log below.

Regards
Graham


Traceback (most recent call last):
  File "/<>/builddir/stage/bin/psi4", line 177, in 
import psi4
  File "/<>/builddir/stage/lib/x86_64-linux-gnu/psi4/__init__.py",
line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized
module 'psi4' (most likely due to a circular import)
(/<>/builddir/stage/lib/x86_64-linux-gnu/psi4/__init__.py)
Exit Status: infile ( 1 ); autotest ( None ); sowreap ( None ); overall ( 1 )


0% tests passed, 143 tests failed out of 143

Processed: src:widelands: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 2:1.1-1
Bug #1027024 [src:widelands] src:widelands: fails to migrate to testing for too 
long: FTBFS on s390x
Marked as fixed in versions widelands/2:1.1-1.
Bug #1027024 [src:widelands] src:widelands: fails to migrate to testing for too 
long: FTBFS on s390x
Marked Bug as done
> block -1 by 1023830
Bug #1027024 {Done: Paul Gevers } [src:widelands] 
src:widelands: fails to migrate to testing for too long: FTBFS on s390x
1027024 was not blocked by any bugs.
1027024 was not blocking any bugs.
Added blocking bug(s) of 1027024: 1023830

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

Processed: src:rdma-core: fails to migrate to testing for too long: FTBFS on mips*el

[Debian Bug Tracking System]

Processing control commands:

> close -1 43.0-1
Bug #1027023 [src:rdma-core] src:rdma-core: fails to migrate to testing for too 
long: FTBFS on mips*el
Marked as fixed in versions rdma-core/43.0-1.
Bug #1027023 [src:rdma-core] src:rdma-core: fails to migrate to testing for too 
long: FTBFS on mips*el
Marked Bug as done
> block -1 by 1026088
Bug #1027023 {Done: Paul Gevers } [src:rdma-core] 
src:rdma-core: fails to migrate to testing for too long: FTBFS on mips*el
1027023 was not blocked by any bugs.
1027023 was not blocking any bugs.
Added blocking bug(s) of 1027023: 1026088

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

Bug#1027023: src:rdma-core: fails to migrate to testing for too long: FTBFS on mips*el

[Paul Gevers]

Source: rdma-core
Version: 42.0-1
Severity: serious
Control: close -1 43.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1026088

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:rdma-core has been trying to migrate for 
63 days [2]. Hence, I am filing this bug. Your package is blocked by the 
ftbfs bug 1026088.


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=rdma-core



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024218: marked as done (apitrace: FTBFS with libproc2)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 14:41:32 +
with message-id 
and subject line Bug#1024218: fixed in apitrace 11.1+repack-1.1
has caused the Debian Bug report #1024218,
regarding apitrace: FTBFS with libproc2
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.)


-- 
1024218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apitrace
Severity: important
Tags: ftbfs upstream


Hi,

The procps project is changing the libprocps library.  The old API found in
libprocps8 is very diferrent to what is found in libproc2.

As a result, your package will FTBFS as the library name has changed as well
as the library calls.

All is not lost, for most of the dependent projects there are already patches
available to close to it. I have also ported programs from the old to the new
libraries so can assist.

The libproc2 packages are found in procps 4.0.1+ in experimental.

 - Craig



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

Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: apitrace
Source-Version: 11.1+repack-1.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated apitrace package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2022 13:13:35 +0100
Source: apitrace
Architecture: source
Version: 11.1+repack-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Sebastian Ramacher 
Closes: 1024218
Changes:
 apitrace (11.1+repack-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/: Switch to libproc2-dev (Closes: #1024218)
Checksums-Sha1:
 f225e8fc11c35daa65fe009fc9f409bab5160dad 2338 apitrace_11.1+repack-1.1.dsc
 9583a80913408321abc76187f0bea3c23e0ab772 8180 
apitrace_11.1+repack-1.1.debian.tar.xz
 52ba9c499cf3154030ca758a0a82a8088b6ab315 14376 
apitrace_11.1+repack-1.1_amd64.buildinfo
Checksums-Sha256:
 b53dadd69b39c46ec26d05c8897f8ed3f4a452c478c29c32ef48a6ade4f8dc87 2338 
apitrace_11.1+repack-1.1.dsc
 71262565d6319e1a4935ddefaefdf1708a334b8e64f7804dadabfa1096552f8e 8180 
apitrace_11.1+repack-1.1.debian.tar.xz
 c7ca31b07b138156ad3e54580a7dcc69f4ae2972a6c88ef0cbd30c983ba93f60 14376 
apitrace_11.1+repack-1.1_amd64.buildinfo
Files:
 4491fb1c98894d49eee9f73e98572445 2338 graphics optional 
apitrace_11.1+repack-1.1.dsc
 8f1a9119fa961758874bd637af992e6e 8180 graphics optional 
apitrace_11.1+repack-1.1.debian.tar.xz
 d33eb4d2e41e2b33304240d1ada2b055 14376 graphics optional 
apitrace_11.1+repack-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmOm9zcVHHNyYW1hY2hl
ckBkZWJpYW4ub3JnAAoJEGny/FFupxmTb1EQAIE0qCCmyisiA+/brLkMnRlkSlkG
bdqO1FjqzcMMfYt3en8qoINSkLTO6Krvl09i5aNXZcoSgLAIbKa5bmT9HfmJ5ceX
0ui+qLrE015f6DfrEcA91QkRpfFyVzkESqjpm6hdujVCKKTcJqgvD3N0XUDtms1i
a1qjNI6J/qvUITw614OmH2xS2ISwz+v0ve/CkZ3T/GSqNOYBb5r5Bx9bstQbzmYt
PWQDPODo5pfqOJmouqxuCYF0BFN8kLtNFaRpWmwI+WGTFjDNkQmVWo7rZnjcfC3w
6xLbme5iYwqb/y+e2IFSmRExLycKV76F+j6eEwE7TQB2/AW0xzoTA0e2MDZYTEVI
HLggyC1Jws2c+AGBOrK6Iw1l21zLKNRXW40rtjamoKyh5B7KLPG6f7XZWZKmYrD8
2DSNFCkvD6A2mMHsVPYCbo2rsbNntKh/blYKIxGDYjEab5yj7buQJyTbDIwoShPF
n2iwiRQfWVa5xl/K5H/xItwf/wanniGNFinPTUN3MSYSccD2qyPJHoIboZFhRUlL
/ixVK+1ATDIicS9HJt77tsMPVsIhDkinxmSNtqM9G2vL/y+cHxWbk+J+a9GaaWPH
JBloEEVaGlL/7ysIfg9iYATJpUfO1M/gBsxdVwUyJYPsUfuQxUJVi2O7QTFU2S2f
zX5NlzgEk+gDgilA
=Vave
-END PGP SIGNATURE End Message ---

Processed: Bug#1026656 marked as pending in maven-war-plugin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026656 [src:maven-war-plugin] maven-war-plugin: FTBFS: make: *** 
[debian/rules:4: build] Error 25
Added tag(s) pending.

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

Bug#1026656: marked as pending in maven-war-plugin

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #1026656 in maven-war-plugin 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/java-team/maven-war-plugin/-/commit/0516f362df65bcd8a931cd6b32697d955133c1fd


Fixed the build failure with maven-filtering 3.3 (Closes: #1026656)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026656

Processed: python-reportlab: diff for NMU version 3.6.11-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1019989 + patch
Bug #1019989 [src:python-reportlab] python-reportlab: FTBFS: 
ModuleNotFoundError: No module named 'reportlab'
Added tag(s) patch.
> tags 1019989 + pending
Bug #1019989 [src:python-reportlab] python-reportlab: FTBFS: 
ModuleNotFoundError: No module named 'reportlab'
Added tag(s) pending.

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

Bug#1019989: python-reportlab: diff for NMU version 3.6.11-1.1

[Jochen Sprickerhof]

Control: tags 1019989 + patch
Control: tags 1019989 + pending


Dear maintainer,

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

Regards.

diff -Nru python-reportlab-3.6.11/debian/changelog python-reportlab-3.6.11/debian/changelog
--- python-reportlab-3.6.11/debian/changelog	2022-07-17 14:14:52.0 +0200
+++ python-reportlab-3.6.11/debian/changelog	2022-12-26 15:13:28.0 +0100
@@ -1,3 +1,10 @@
+python-reportlab (3.6.11-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix PYTHONPATH in d/rules to fix FTBFS (Closes: #1019989)
+
+ -- Jochen Sprickerhof   Mon, 26 Dec 2022 15:13:28 +0100
+
 python-reportlab (3.6.11-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru python-reportlab-3.6.11/debian/rules python-reportlab-3.6.11/debian/rules
--- python-reportlab-3.6.11/debian/rules	2022-03-10 19:14:33.0 +0100
+++ python-reportlab-3.6.11/debian/rules	2022-12-26 15:13:23.0 +0100
@@ -5,7 +5,7 @@
 
 # all versions
 PY3VERS	:= $(shell py3versions -vs)
-VER3	:= $(shell py3versions -vd)
+VER3	:= $(shell py3versions -vd | tr -d .)
 
 include /usr/share/python3/python.mk
 


signature.asc
Description: PGP signature

Bug#1027020: davmail-server: fails to install: insserv: script davmail-server: service davmail already provided!

[gregor herrmann]

Package: davmail-server
Version: 6.0.1.3390-3
Severity: serious
Justification: fails to install

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

When trying to update davmail / install davmail-server I get:


Setting up davmail-server (6.0.1.3390-3) ...
insserv: script davmail-server: service davmail already provided!
update-rc.d: error: no runlevel symlinks to modify, aborting!
dpkg: error processing package davmail-server (--configure):
 installed davmail-server package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of davmail:
 davmail depends on davmail-server; however:
  Package davmail-server is not configured yet.

dpkg: error processing package davmail (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 davmail-server
 davmail


The reason seems to be that /etc/init.d/davmail is still around (and
has "Provides. davmail")


Cheers,
gregor


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

Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages davmail-server depends on:
ii  adduser   3.130
ii  default-jre-headless [java9-runtime-headless] 2:1.17-73
hi  init-system-helpers   1.64
ii  libcommons-codec-java 1.15-1
ii  libcommons-logging-java   1.2-3
ii  libhtmlcleaner-java   2.26-1
ii  libhttpclient-java4.5.14-1
ii  libjackrabbit-java2.20.3-1
ii  libjcifs-java 1.3.19-2
ii  libjettison-java  1.5.1-1
ii  libjna-java   5.12.1-1
ii  liblog4j1.2-java  1.2.17-11
ii  libmail-java  1.6.5-1
ii  libslf4j-java 1.7.32-1
ii  libstax2-api-java 4.1-1
ii  libwoodstox-java  1:6.2.1-1
ii  logrotate 3.21.0-1
ii  openjdk-11-jre-headless [java9-runtime-headless]  11.0.17+8-2
ii  openjdk-17-jre-headless [java9-runtime-headless]  17.0.5+8-2
ii  sysvinit-utils [lsb-base] 3.06-2

davmail-server recommends no packages.

davmail-server suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmOpnRRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbJJw/9GRQOGLvrW0NtOjU61Aa3MaPb6bkmPNsVUNwuIS71uRwU2hnnD40cWmvt
R7/hQk8K2Csou/jYCLJRqh0o4PdKuF1weMJOKXF+IxxdmYAf9dmnAZCrOs8Y/wyx
jrxMP9z6EO8/FBwxtqnBfEhszWILqRRu6Q6SUEg2+tZbiSnUTqGZ5EOPy/O4XMPx
MRA5ZPmsaBtk5qAnSr4l6cONi3elExhlwwObD+cJOc4BQk/ckadHicCsaDdgL5dH
Ow9dP2OHA7ZQ5CX6bq+Y7CBfMs6pLi6wi9UnQf6vNB7+B+vFqK1PLyPBwZ34TRid
DX9QmjxKLmXsS7NgOPQJ6EY+EAcoTt3AMeR/jgn0Cg1PlySL5/AAjYjbKqucwpoz
kLCm7MIq3hU2Qkf8s4tC9d5+5eNUb4nC88AHJphtl9jdvui6Panf3j6BkJEW7C1k
4oiM7742iF4R6Rp4VNJUyyGi0dGC9MFc1+EdXIUdopw3WPTcnCa4QZvz04X/RYEn
ez7jRd9+7X/XPHaaCeHQ7jIZ6NDQez0H0VY43W/uJjNj0scJvTF0YVj16aCamo6y
qZ31yIJVLg5BRi+bodlcpYuqvKbh/WphpYPjg+jF449cc0dAwYwUndB+P8Rrsrsk
ZMkqModeqlDQWr7D3EbGARydFR5S9kEUC597DYguVK/Wpz0H+dQ=
=+WAm
-END PGP SIGNATURE-

Bug#1024219: marked as done (cpu-x: FTBFS with libproc2)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2022 13:05:42 +
with message-id 
and subject line Bug#1024219: fixed in cpu-x 4.5.1-1.1
has caused the Debian Bug report #1024219,
regarding cpu-x: FTBFS with libproc2
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.)


-- 
1024219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpu-x
Version: 4.5.1-1
Severity: important
Tags: upstream ftbfs


Hi,

The procps project is changing the libprocps library.  The old API found in
libprocps8 is very diferrent to what is found in libproc2.

As a result, your package will FTBFS as the library name has changed as well
as the library calls.

All is not lost, for most of the dependent projects there are already patches
available to close to it. I have also ported programs from the old to the new
libraries so can assist.

The libproc2 packages are found in procps 4.0.1+ in experimental.

 - Craig



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

Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: cpu-x
Source-Version: 4.5.1-1.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated cpu-x package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2022 13:03:04 +0100
Source: cpu-x
Architecture: source
Version: 4.5.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Martin Wimpress 
Changed-By: Sebastian Ramacher 
Closes: 1024219
Changes:
 cpu-x (4.5.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches: Apply upstream patch to fix build with procps 4 (Closes:
 #1024219)
   * debian/control: Change libprocps-dev to libproc2-dev.
Checksums-Sha1:
 0b85b2364d9493352b7ad25ee04e6e3e05f605c2 2112 cpu-x_4.5.1-1.1.dsc
 49ce0b5e95e222d545896dacd869e2ff26cf4d5f 9424 cpu-x_4.5.1-1.1.debian.tar.xz
 bbec68b1b2a552e77fd34b0ddd2175325a73d78b 15333 cpu-x_4.5.1-1.1_amd64.buildinfo
Checksums-Sha256:
 14aa5df4983eb758b734ea56bf9cb90a067e15c7fe08c709b7a9f6ed4f680091 2112 
cpu-x_4.5.1-1.1.dsc
 e64f340172598bb7de2a1bca0a1310e9503525aa500b6df36b8e3ed0784a1beb 9424 
cpu-x_4.5.1-1.1.debian.tar.xz
 974590dff24d3a97296047e611b5cf7866475e7b6333b27aca47e83c096ccb81 15333 
cpu-x_4.5.1-1.1_amd64.buildinfo
Files:
 981dd2c4ab7f04b7b2d16b4cf6285336 2112 x11 optional cpu-x_4.5.1-1.1.dsc
 42fc01fcf8d60958387856e4ec2d48eb 9424 x11 optional 
cpu-x_4.5.1-1.1.debian.tar.xz
 009749c96fe654f473e1804827143b4d 15333 x11 optional 
cpu-x_4.5.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmOm6xsVHHNyYW1hY2hl
ckBkZWJpYW4ub3JnAAoJEGny/FFupxmT3KAP/AjFjKxSpHMz1EfugzO0ZIiZ/vM/
Ij0TQ2w8xTJGa/FU5qgNH7YSPK5dIgn9e23rHbdj+RgVcWYXjd1XSJGCZVvJrqYs
XTmpz8gGAitebo5/nZtc95nqIOE1vEZUqa5VzS46eMw0C0Nvmr+f+I4+OPdPekjC
RjS7BqawDJHcPZi7yuLzK8aYCZq/5qFd34qx/HWTgHgBLor+FevGdn9IwPf6yRMO
riA8M2c5jOo+PvKX7q2X2bYiSFVjUxFVwPpo3bdJ9jA6RkB9QFLA3wHAzkq5DRrW
pmSh2Lr0BNEgYSswuCTlZN/MsT2tOWgRET22XIkMjjG+kjdEoAYA+/bFhxRmnKNK
9KRMmoH45vDTTPf1luBZwkO2OOJWxCadDo0/WtLVZWvjgSrMAXyETRXKIO5FkkCS
2ABM5eEpD+gniuKzx8eEwaTajhBza+5dMz9qewwbZPzKOlPmChgIekq5Yj2WjMik
DE9e8xJsGRCk4oXv6DRR92WslfSq7HfRJL+MxMv5BuPALooZYbBjETF0ES4/AZCY
RQMWC815zqEULR0eSH2aCn+9w881EjqpVAimYehFI7mbOn4DiluMjvfphTcZM4s1
FIZUIjk/2V80COTDByMmtg5VMqynpPW+14gao1PfMFCIiG905t9i5bxOlqIlB5wX
iVjnPdZEoblZANb3
=NpqV
-END PGP SIGNATURE End Message ---

Processed: src:chroma cannot build because inkscape is not installable

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1012496
Bug #1027019 [chroma] src:chroma cannot build because inkscape is not 
installable
1027019 was not blocked by any bugs.
1027019 was not blocking any bugs.
Added blocking bug(s) of 1027019: 1012496

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

Processed: Bug#1013385 marked as pending in recommonmark

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013385 [src:recommonmark] recommonmark: FTBFS with Sphinx 5.0, docutils 
0.18: AssertionError:
Added tag(s) pending.

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

Bug#1013385: marked as pending in recommonmark

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1013385 in recommonmark 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/packages/recommonmark/-/commit/5c8268144f9b91b7f5f37fed76d25cf4c0bfa561


Add patch for Sphinx 5

Closes: #1013385


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013385

Processed: Re: Bug#1026487: libvigraimpex: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices

[Debian Bug Tracking System]

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

> forwarded 1026487 https://github.com/ukoethe/vigra/issues/528
Bug #1026487 [src:libvigraimpex] libvigraimpex: FTBFS: IndexError: only 
integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or 
boolean arrays are valid indices
Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/528'.
>
End of message, stopping processing here.

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

Bug#1027017: pillow: FTBFS docs/_build/html not present

[GCS]

Source: pillow
Version: 9.2.0-1.1
Severity: serious
Justification: FTBFS
Usertags: tiff4_5
Tags: sid bookworm ftbfs

Hi,

During a rebuild of your package, pillow fails to build due to:
dh_installdocs -i
dh_installdocs -ppython-pil-doc docs/_build/html
dh_installdocs: warning: Cannot auto-detect main package for
python-pil-doc.  If the default is wrong, please use
--doc-main-package
cp: cannot stat 'docs/_build/html': No such file or directory
dh_installdocs: error: cp --reflink=auto -a docs/_build/html
debian/python-pil-doc/usr/share/doc/python-pil-doc returned exit code
1
make: *** [debian/rules:126: binary-indep] Error 25

Please take care of it soon as the Bookworm freeze is approaching.

Regards,
Laszlo/GCS

Bug#1027013: llvm-toolchain-14 autopkg test fails

[Matthias Klose]

Package: src:llvm-toolchain-14
Version: 1:14.0.6-9
Severity: serious
Tags: sid bookworm

no idea what this test is supposed to test ...

however the source reads:

// Test the link against libclang-cppXX
//
// REQUIRES: clang, llvm-config
// RUN: %clangxx -lclang-cpp -v %s -o %t `%llvm-config --cxxflags --ldflags 
--libs`
// RUN: ldd %t 2>&1|grep -q libclang-cpp

with --as-needed as the default in the linker this is doomed to fail, having the 
library on the command line before the object file.


unsure if that is the root cause, as it only fails on amd64 and arm64.

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-14/29644065/log.gz


[...]
FAIL: LLVM regression suite :: libclang_cpp.cpp (25 of 45)
 TEST 'LLVM regression suite :: libclang_cpp.cpp' FAILED 


Script:
--
: 'RUN: at line 4';   /usr/bin/clang++-14 -lclang-cpp -v 
/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/tests/libclang_cpp.cpp -o 
/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/build/tests/Output/libclang_cpp.cpp.tmp 
`/usr/bin/llvm-config-14 --cxxflags --ldflags --libs`
: 'RUN: at line 5';   ldd 
/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/build/tests/Output/libclang_cpp.cpp.tmp 
2>&1|grep -q libclang-cpp

--
Exit Code: 1

Command Output (stderr):
--
Debian clang version 14.0.6
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/10
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12
Candidate multilib: .;@m64
Selected multilib: .;@m64
 "/usr/lib/llvm-14/bin/clang" -cc1 -triple x86_64-pc-linux-gnu -emit-obj 
-mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend 
-disable-llvm-verifier -discard-value-names -main-file-name libclang_cpp.cpp 
-mrelocation-model pic -pic-level 2 -pic-is-pie -mframe-pointer=all -fmath-errno 
-ffp-contract=on -fno-rounding-math -mconstructor-aliases -funwind-tables=2 
-target-cpu x86-64 -tune-cpu generic -mllvm 
-treat-scalable-fixed-error-as-warning -debugger-tuning=gdb -v 
-fcoverage-compilation-dir=/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/build/tests 
-resource-dir /usr/lib/llvm-14/lib/clang/14.0.6 -I /usr/lib/llvm-14/include -D 
_GNU_SOURCE -D __STDC_CONSTANT_MACROS -D __STDC_FORMAT_MACROS -D 
__STDC_LIMIT_MACROS -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12 
-internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/x86_64-linux-gnu/c++/12 
-internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/backward 
-internal-isystem /usr/lib/llvm-14/lib/clang/14.0.6/include -internal-isystem 
/usr/local/include -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../x86_64-linux-gnu/include 
-internal-externc-isystem /usr/include/x86_64-linux-gnu 
-internal-externc-isystem /include -internal-externc-isystem /usr/include 
-std=c++14 -fdeprecated-macro 
-fdebug-compilation-dir=/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/build/tests 
-ferror-limit 19 -fgnuc-version=4.2.1 -faddrsig -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o 
/tmp/lit-tmp-f4zxudnz/libclang_cpp-b074e4.o -x c++ 
/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/tests/libclang_cpp.cpp

clang -cc1 version 14.0.6 based upon LLVM 14.0.6 default target 
x86_64-pc-linux-gnu
ignoring nonexistent directory 
"/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../x86_64-linux-gnu/include"

ignoring nonexistent directory "/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/llvm-14/include
 /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12

/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/x86_64-linux-gnu/c++/12
 /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/backward
 /usr/lib/llvm-14/lib/clang/14.0.6/include
 /usr/local/include
 /usr/include/x86_64-linux-gnu
 /usr/include
End of search list.
 "/usr/bin/ld" -pie --hash-style=both --build-id --eh-frame-hdr -m elf_x86_64 
-dynamic-linker /lib64/ld-linux-x86-64.so.2 -o 
/tmp/autopkgtest-lxc._y_hntgm/downtmp/autopkgtest_tmp/build/tests/Output/libclang_cpp.cpp.tmp 
/lib/x86_64-linux-gnu/Scrt1.o /lib/x86_64-linux-gnu/crti.o 
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/crtbeginS.o -L/usr/lib/llvm-14/lib 
-L/usr/bin/../lib/gcc/x86_64-linux-gnu/12 
-L/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../lib64 
-L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu 
-L/usr/lib/../lib64 -L/usr/lib/llvm-14/bin/../lib -L/lib -L/usr/lib -lclang-cpp 
/tmp/lit-tmp-f4zxudnz/libclang_cpp-b074e4.o -lLLVM-14 -lstdc++ -lm -lgcc_s -lgcc 
-lc -lgcc_s -lgcc /usr/bin/../lib/gcc/x86_64-linux-gnu/12/crtendS.o 
/lib/x86_64-linux-gnu/crtn.o


--

Bug#1027012: pyobjcryst: b-d on python3-all-dev, but not built for all supported Python3 versions

[Graham Inggs]

Source: pyobjcryst
Version: 2.2.1-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.11 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
you get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.11-add.html

Bug#1027011: rust-num-rational: FTBFS on armel

[Sebastian Ramacher]

Source: rust-num-rational
Version: 0.4.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/rust-num/num-rational/issues/111

https://buildd.debian.org/status/fetch.php?pkg=rust-num-rational&arch=armel&ver=0.4.1-1&stamp=1671490743&raw=0


failures:

 test::test_ldexp stdout 
thread 'test::test_ldexp' panicked at 'assertion failed: `(left == right)`
  left: `2.2250738585072014e-308`,
 right: `0.0`', src/lib.rs:3090:9
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
   4: num_rational::test::test_ldexp
 at /usr/share/cargo/registry/num-rational-0.4.1/src/lib.rs:3090:9
   5: num_rational::test::test_ldexp::{{closure}}
 at /usr/share/cargo/registry/num-rational-0.4.1/src/lib.rs:3072:5
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   7: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
test::test_ldexp

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

error: test failed, to rerun pass '--lib'
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101

Cheers
-- 
Sebastian Ramacher

Processed: rust-num-rational: FTBFS on armel

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/rust-num/num-rational/issues/111
Bug #1027011 [src:rust-num-rational] rust-num-rational: FTBFS on armel
Set Bug forwarded-to-address to 
'https://github.com/rust-num/num-rational/issues/111'.

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