date:20221221

Processing control commands:

> tags -1 upstream
Bug #1025119 [src:python-ratelimiter] python-ratelimiter: (autopkgtest) needs 
update for python3.11: module 'asyncio' has no attribute 'coroutine'
Added tag(s) upstream.
> forwarded -1 https://github.com/RazerM/ratelimiter/issues/18
Bug #1025119 [src:python-ratelimiter] python-ratelimiter: (autopkgtest) needs 
update for python3.11: module 'asyncio' has no attribute 'coroutine'
Set Bug forwarded-to-address to 
'https://github.com/RazerM/ratelimiter/issues/18'.

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

Bug#1025119: python-ratelimiter: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'

2022-12-21 Thread Andreas Tille

Control: tags -1 upstream
Control: forwarded -1 https://github.com/RazerM/ratelimiter/issues/18

Bug#1026710: marked as done (libspin-java: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25)

Your message dated Thu, 22 Dec 2022 06:35:13 +
with message-id 
and subject line Bug#1026710: fixed in libspin-java 1.5+dfsg-9
has caused the Debian Bug report #1026710,
regarding libspin-java: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_test] 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.)


-- 
1026710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libspin-java
Version: 1.5+dfsg-8.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):
> make[1]: Entering directory '/<>'
> xvfb-run dh_auto_test
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
>   /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=/<>/libspin-java-1.5\+dfsg 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/libspin-java-1.5\+dfsg/debian 
> -Dmaven.repo.local=/<>/libspin-java-1.5\+dfsg/debian/maven-repo 
> --batch-mode test
> 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.
> [0m[0m[INFO] Scanning for projects...
> [INFO] 
> [INFO] -< spin:spin 
> >--
> [INFO] Building Spin 1.5
> [INFO] [ jar 
> ]-
> [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-surefire-plugin:jar:2.12.4 has been relocated 
> to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ spin 
> ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 0 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ spin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:testResources (default-testResources) 
> @ spin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 0 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ 
> spin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ spin ---
> [INFO] 
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running spin.JDKProxyFactoryTest
> [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 
> s - in spin.JDKProxyFactoryTest
> [INFO] Running spin.off.SpinOffTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 
> s <<< FAILURE! - in spin.off.SpinOffTest
> [ERROR] testEDTNotBlockedDuringInvocation(spin.off.SpinOffTest)  Time 
> elapsed: 0.001 s  <<< ERROR!
> java.lang.Error: Unable to make void 
> java.awt.EventDispatchThread.pumpEvents(java.awt.Conditional) accessible: 
> module java.desktop does not "opens java.awt" to unnamed module @614635c2
>   at 
> spin.off.AWTReflectDispatcherFactory.(AWTReflectDispatcherFactory.java:144)
>   at spin.off.SpinOffEvaluator.(SpinOffEvaluator.java:38)
>   at spin.Spin.(Spin.java:68)
>   at 
> spin.off.SpinOffTest.testEDTNotBlockedDuringInvocation(SpinOffTest.java:64)
> 
> [INFO] Running spin.off.AWTReflectDispatcherTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 
> s <<< FAILURE! - in spin.off.AWTReflectDispatcherTest
> [ERROR] test(spin.off.AWTReflectDispatcherTest)  Time elapsed: 0 s  <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class 
> spin.off.AWTReflectDispatcherFactory
>   at 
> spin.off.AWTReflectDispatcherTest.test(AWTReflectDispatcherTest.java:28)
> 
> [INFO] Running spin.CGLibProxyFactoryTest
> [ERROR] Tests run: 4, Failures: 0, Errors: 4,

Bug#1026666: Please make liblog4j2-java depend on junit5

2022-12-21 Thread Pierre Gruet


Hi tony,

Le 21/12/2022 à 22:58, tony mancill a écrit :

On Tue, Dec 20, 2022 at 11:45:54PM +0100, Pierre Gruet wrote:

Control: retitle -1 Please make liblog4j2-java depend on junit5

Hello,

In version 2.19.0-1 of liblog4j2-java, the file

/usr/share/maven-repo/org/apache/logging/log4j/log4j/debian/log4j-debian.pom
declares the junit-bom artifact as a dependency. It is shipped in junit5.

If this dependency is not added, reverse dependencies of liglog4j2-java fail
to build (see logs above) as the junit-bom artifact is not found.


Hi Pierre,

I'm wondering if it wouldn't better to remove junit-bom from log4j pom.
I don't believe we actually need junit5 at runtime for log4j2, so
packages depending on liblog4j2-java should not have to install junit5.

Any concerns with taking that approach and addressing the bug by
adjusting the pom shipped with liblog4j2-java?


Thanks for having a look; I haven't looked further but I also fail to 
imagine why junit5 would be needed, so I agree with the proposed fix!




Thanks,
tony


Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1026710: marked as pending in libspin-java

2022-12-21 Thread Tony Mancill

Control: tag -1 pending

Hello,

Bug #1026710 in libspin-java 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/libspin-java/-/commit/deb647bf1470caf642b7e44a99b29b9e9042ac08


Address FTBFS by exporting modules to tests (Closes: #1026710)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026710

Processed: Bug#1026710 marked as pending in libspin-java

Processing control commands:

> tag -1 pending
Bug #1026710 [src:libspin-java] libspin-java: FTBFS: make[1]: *** 
[debian/rules:7: override_dh_auto_test] Error 25
Added tag(s) pending.

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

Bug#1024795: python-llvmlite

2022-12-21 Thread Diane Trout

Hi,

I was trying to update numba, and need the updated version of llvmlite
built against llvm-14

The version that's currently in unstable is still built against llvml-
11

https://packages.debian.org/sid/python3-llvmlite

I've checked out out the llvmlite repository and rebuilt it locally
using commit c65b3e662b7b08920172b710419d7a06b660be59 against llvm-14

and llvmlite's test cases pass. (And most of numba's passed too. And I
think the remaining test failures aren't related to llvmlite)

Is there a chance we could get an updated version released soon?

Thanks
Diane Trout


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

Processed: Bug#1026586 marked as pending in python-asyncssh

Processing control commands:

> tag -1 pending
Bug #1026586 [src:python-asyncssh] python-asyncssh: FTBFS: RuntimeError: Could 
not determine home directory.
Added tag(s) pending.

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

Bug#1026586: marked as pending in python-asyncssh

Control: tag -1 pending

Hello,

Bug #1026586 in python-asyncssh 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/python-asyncssh/-/commit/8a5e69ad67f6fdd3bbcdfca1f7ddb3a2558c1009


Cherry-pick upstream patch to fix FTBFS with python3.11 (Closes: #1026586)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026586

Bug#1026696: golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25

2022-12-21 Thread Daniel Swarbrick

Updating the 01-Use_go_generate.patch as follows results in a successful 
build (without needing to add golang-google-protobuf-dev as a dependency):


diff --git a/debian/patches/01-Use_go_generate.patch 
b/debian/patches/01-Use_go_generate.patch

index cafa5e2..ffa83cf 100644
--- a/debian/patches/01-Use_go_generate.patch
+++ b/debian/patches/01-Use_go_generate.patch
@@ -6,4 +6,4 @@ Description: Use go generate to avoid depending on 
special make rules in

 @@ -0,0 +1,3 @@
 +package io_prometheus_client
 +
-+//go:generate protoc --proto_path=../io/prometheus/client 
--go_out=paths=source_relative:. metrics.proto
++//go:generate protoc --proto_path=../io/prometheus/client 
--go_out=paths=source_relative,Mgoogle/protobuf/timestamp.proto=github.com/golang/protobuf/ptypes/timestamp:. 
metrics.proto


However, the generated metrics.pb.go still uses *timestamppb.Timestamp 
for the timestamp fields, which will cause undesirable side-effects on 
downstream packages.


I am not aware of any way to influence protoc to use the old timestamp type.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#905782: marked as done (Invalid dependency to mitmproxy old python2 module)

Your message dated Wed, 21 Dec 2022 21:56:23 -0300
with message-id 

and subject line 
has caused the Debian Bug report #905782,
regarding Invalid dependency to mitmproxy old python2 module
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.)


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

Package: bdfproxy
Version: 0.3.9-2
Severity: grave

Since mitmproxy has been updated to python3, creating a mitmproxy 
python3-exclusive library, bdfproxy must be ported to python3 in order 
to work properly.


--
Philippe.
--- End Message ---
--- Begin Message ---
Hi, Philippe.

I think this should've been closed during 0.3.9-3 upload but a typo in
the bug number prevented it. So I'm closing it now.

Cheers,
Charles


signature.asc
Description: PGP signature
--- End Message ---

Bug#1026660: closing 1026660

2022-12-21 Thread Timo Röhling

close 1026660 4.2.0-1
thanks

Hi Lucas,
this is already fixed by the recent upload of the new upstream release.

Cheers
Timo

-- 
â¢â£´â ¾â »â¢¶â£¦â    
ââââââââââââââââââââââââââââââââââââââââââââââââââââââ®
â£¾â â¢ â â â£¿â¡   â Timo RÃ¶hling   
â
â¢¿â¡â â ·â â â    â 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA 
â
â â ³â£â â â â    
â°âââââââââââââââââââââââââââââââââââââââââââââââââââââ¯

Processed: closing 1026660

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

> close 1026660 4.2.0-1
Bug #1026660 [src:pytest-qt] pytest-qt: FTBFS: dpkg-buildpackage: error: 
dpkg-source -b . subprocess returned exit status 2
Marked as fixed in versions pytest-qt/4.2.0-1.
Bug #1026660 [src:pytest-qt] pytest-qt: FTBFS: dpkg-buildpackage: error: 
dpkg-source -b . subprocess returned exit status 2
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 1022287

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

> tags 1022287 - pending
Bug #1022287 [src:poldi] poldi: FTBFS: configure: error: You need libgpg-error 
to build this program.
Ignoring request to alter tags of bug #1022287 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 1024642

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

> tags 1024642 + pending
Bug #1024642 [src:pgcharts] pgcharts: FTBFS: Fatal NAME-CONFLICT: [...]  
PGCHARTS.SQL:READ-QUERIES, POSTMODERN:READ-QUERIES
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1024221: Bug#1022573: transition: procps

2022-12-21 Thread Craig Small

(added the bug report for igt)
On Thu, 22 Dec 2022 at 08:29, Craig Small  wrote:

> On Thu, 22 Dec 2022 at 07:46, Paul Gevers  wrote:
>
>> An actual upload. If the maintainer isn't doing it, I think an NMU is
>> appropriate if you're sure of the fix.
>>
> Ah, I thought you were the igt maintainer :)
>
> I'll have a go recreating it and uploading it tonight. I'm pretty
> confident about the patches but don't use the package myself.
>
So the issue is that the changelog has updated the version to
1.26+git20221011-1 but this isn't uploaded or tagged.
I can either:
  Attach my patch for 1024221 to bug #1024221 and wait
  Update to 20221011 and add the patch, this both links to libproc2 and
updates the version
  Roll-back to 20220524 and add the patch, keeps the binary the same linked
to libproc2 but moves the changelog back

Ideally, I'd like 20221011 linked to libproc2 but I don't want to release a
new version of intel-gpu-tools as I'm not the maintainer and there might be
a reason its not being updated.

BUT, procps is in transition and this linking needs to happen before the
first freeze milestone so I will upload 20220525 linked to libproc2 if we
get near to running out of time.

 - Craig


>  - Craig
>
>

Bug#1026613: marked as done (pytoolconfig: FTBFS: make: *** [debian/rules:7: binary] Error 25)

Your message dated Wed, 21 Dec 2022 22:56:09 +
with message-id 
and subject line Bug#1026613: fixed in pytoolconfig 1.2.4-1
has caused the Debian Bug report #1026613,
regarding pytoolconfig: FTBFS: make: *** [debian/rules:7: 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.)


-- 
1026613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytoolconfig
Version: 1.2.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 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
>   pybuild --configure -i python{version} -p 3.10
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p 3.10
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build" 
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.10 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 351, in 
> main()
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 333, in main
> json_out['return_val'] = hook(**hook_input['kwargs'])
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 249, in build_wheel
> return _build_backend().build_wheel(wheel_directory, config_settings,
>   File "/usr/lib/python3/dist-packages/pdm/pep517/api.py", line 75, in 
> build_wheel
> builder.build(wheel_directory, metadata_directory=metadata_directory)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 151, in 
> build
> self._copy_module()
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 321, in 
> _copy_module
> root = self.meta.config.package_dir or self.location
>   File "/usr/lib/python3/dist-packages/pdm/pep517/base.py", line 154, in meta
> self._meta.validate(True)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/metadata.py", line 58, in 
> validate
> return validate_pep621(self.data, raising)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/validator.py", line 85, in 
> validate_pep621
> raise PEP621ValidationError(validator.errors)
> pdm.pep517.exceptions.PEP621ValidationError: {'license-expression': ['unknown 
> field']}
> * Building wheel...
> 
> ERROR Backend subproccess exited when trying to invoke build_wheel
> E: pybuild pybuild:386: build: plugin pyproject failed with: exit code=1: 
> python3.10 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/pytoolconfig_1.2.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

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

We believe that the bug you reported is fixed in the latest version of
pytoolconfig, 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.
Boyuan Yang  (supplier of updated pytoolconfig package)

(This message was generated

Bug#1026696: golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25

2022-12-21 Thread Daniel Swarbrick


Hi,

On 22.12.22 00:41, Shengjing Zhu wrote:

Hi,

The workaroud could be like this:
https://salsa.debian.org/go-team/packages/notary/-/commit/b0a072faa72857f7523c8245ecaa8814d5a60051


Fixing the build failure in golang-github-prometheus-client-model is a 
simple matter of including golang-google-protobuf-dev in the build-deps.


However, as the resulting metrics.pb.go now has a different type for the 
timestamp fields, and downstream packages that use this will likely need 
patching.


I already had to patch golang-github-prometheus-common[1] and 
golang-github-prometheus-client-golang[2] for similar issues not long 
ago. With those patches in place, and the new metrics.pb.go, those 
packages FTBFS. Dropping those patches fixes the build, but 
prometheus-common then panics with a Go reflect error in one of the tests.


So I'm not really sure of the best course of action at the moment.

[1]: 
https://salsa.debian.org/go-team/packages/golang-github-prometheus-common/-/blob/debian/sid/debian/patches/01-support-outdated-protobuf-build-deps.patch
[2]: 
https://salsa.debian.org/go-team/packages/golang-github-prometheus-client-golang/-/blob/debian/sid/debian/patches/02-support-outdated-protobuf-build-deps.patch


OpenPGP_signature
Description: OpenPGP digital signature

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

Your message dated Wed, 21 Dec 2022 22:28:33 +
with message-id 
and subject line Bug#1026690: fixed in pyglet 1.5.27+ds-2
has caused the Debian Bug report #1026690,
regarding pyglet: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p "3.11 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.)


-- 
1026690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyglet
Version: 1.5.27+ds-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 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:240: python3.11 setup.py config 
> running config
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/util.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/resource.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/lib.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/math.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/event.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/shapes.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/sprite.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/com.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/info.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> copying pyglet/clock.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet
> creating /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/graphics
> copying pyglet/graphics/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/graphics
> copying pyglet/graphics/vertexbuffer.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/graphics
> copying pyglet/graphics/vertexattribute.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/graphics
> copying pyglet/graphics/allocation.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/graphics
> copying pyglet/graphics/vertexdomain.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/graphics
> creating /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/freetype_lib.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/base.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/win32.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/freetype.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/directwrite.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/ttf.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/quartz.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/fontconfig.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> copying pyglet/font/win32query.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/font
> creating /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/gui
> copying pyglet/gui/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/gui
> copying pyglet/gui/ninepatch.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/gui
> copying pyglet/gui/widgets.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/gui
> copying pyglet/gui/frame.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/gui
> creating /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/model
> copying pyglet/model/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/model
> creating /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/input
> copying pyglet/input/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/input
> copying pyglet/input/x11_xinput_tablet.py -> 
> /<>/.pybuild/cpython3_3.11_pyglet/build/pyglet/input
> copying

Bug#1026503: libembperl-perl: FTBFS: Expected 6 more error(s) in logfile, tagging 1026503

2022-12-21 Thread Axel Beckert

Hi,

gregor herrmann wrote:
> > > Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more 
> > > error(s) in logfile
> 
> (Thanks for fixing this copypaste mistake!)

You're welcome.

>From the build log:
> #8 plainblock.htm...  ok
> #15 error.htm...  
> 
> Expected 6 more error(s) in logfile
> 
> Input:  test/html/error.htm
> Output: test/tmp/out.htm
> Log:test/tmp/test.log
> Testparameter:
>   version = 2
>   condition = $] >= 5.01
>   cgi = 0
>   repeat = 3
>   errors = 6
> 
>  ERRORS detected! NOT all tests have been passed successfully
> 
> cat: test/tmp/httpd.pid: No such file or directory

Just a short note: That last line is a red herring. It's just a follow
up error when the test suite tries to run the already no more running
httpd:

test.pl:system "kill `cat $tmppath/httpd.pid`  2> /dev/null" if ($EPHTTPD 
ne '' && !$opt_nokill) ;

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1006757: marked as done (ghostwriter: CVE-2022-24724 - integer overflow prior to 0.29.0.gfm.3 and 0.28.3.gfm.21)

Your message dated Wed, 21 Dec 2022 22:21:19 +
with message-id 
and subject line Bug#1006757: fixed in ghostwriter 2.1.6+ds-1
has caused the Debian Bug report #1006757,
regarding ghostwriter: CVE-2022-24724 - integer overflow prior to 0.29.0.gfm.3 
and 0.28.3.gfm.21
to be marked as done.

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

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


-- 
1006757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostwriter
Version: 2.1.1-1
Severity: important
Tags: security
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team 


Hi,

The following vulnerability was published for ghostwriter.

https://sources.debian.org/src/ghostwriter/2.1.1-1/3rdparty/cmark-gfm/extensions/table.c/?hl=154#L154

CVE-2022-24724[0]:
| cmark-gfm is GitHub's extended version of the C reference
| implementation of CommonMark. Prior to versions 0.29.0.gfm.3 and
| 0.28.3.gfm.21, an integer overflow in cmark-gfm's table row parsing
| `table.c:row_from_string` may lead to heap memory corruption when
| parsing tables who's marker rows contain more than UINT16_MAX columns.
| The impact of this heap corruption ranges from Information Leak to
| Arbitrary Code Execution depending on how and where `cmark-gfm` is
| used. If `cmark-gfm` is used for rendering remote user controlled
| markdown, this vulnerability may lead to Remote Code Execution (RCE)
| in applications employing affected versions of the `cmark-gfm`
| library. This vulnerability has been patched in the following cmark-
| gfm versions 0.29.0.gfm.3 and 0.28.3.gfm.21. A workaround is
| available. The vulnerability exists in the table markdown extensions
| of cmark-gfm. Disabling the table extension will prevent this
| vulnerability from being triggered.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-24724
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24724

Please adjust the affected versions in the BTS as needed.



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

Kernel: Linux 5.16.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: ghostwriter
Source-Version: 2.1.6+ds-1
Done: Aurélien COUDERC 

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

Debian distribution maintenance software
pp.
Aurélien COUDERC  (supplier of updated ghostwriter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 22:51:24 +0100
Source: ghostwriter
Architecture: source
Version: 2.1.6+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Aurélien COUDERC 
Closes: 1006757
Changes:
 ghostwriter (2.1.6+ds-1) unstable; urgency=medium
 .
   [ Sebastien CHAVAUX ]
   * New upstream release.
   * debian/control: set Standards-Version: to 4.6.1
   * debian/control: address correction
   * debian/watch: address correction
   * vulnerability patched in 3rdparty/cmark-gfm CVE-2022-24724, CVE-2022-39209
   (Closes: #1006757).
 .
   [ Aurélien COUDERC ]
   * Point watch file to the invent.kde.org GitLab repo tags until we get a
 proper upstream release.
   * Add explanation for source lintian overrides.
   * Bump Standards-Version to 4.6.2, no change required.
   * Review copyright information.
   * Replace debian/compat with debhelper-compat build dependency, bump
 compatibility version to 13.
   * Use Debian KDE Extras Team as the maintainer, move Sebastien CHAVAUX
 to uploaders.
   * Added myself to the uploaders.
   * Replace vendored libcmark-gfm with the system one.
   *

Processed: Bug#1026690 marked as pending in pyglet

Processing control commands:

> tag -1 pending
Bug #1026690 [src:pyglet] pyglet: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.11 3.10" returned exit code 13
Added tag(s) pending.

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

Bug#1026690: marked as pending in pyglet

2022-12-21 Thread Timo Röhling

Control: tag -1 pending

Hello,

Bug #1026690 in pyglet 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/pyglet/-/commit/37e42b9a25d5522ab480085becfef1e1268ea7e4


Skip test that breaks with Python 3.11

Closes: #1026690


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026690

Bug#1026624: marked as done (libmpv-dev: missing dependency on wayland-protocols)

Your message dated Wed, 21 Dec 2022 22:00:04 +
with message-id 
and subject line Bug#1026624: fixed in mpv 0.35.0-4
has caused the Debian Bug report #1026624,
regarding libmpv-dev: missing dependency on wayland-protocols
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.)


-- 
1026624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpv-mpris
Version: 0.7.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):
> cc mpris.c -o mpris.so -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -Wall 
> -Wextra -O2 `pkg-config --cflags gio-2.0 gio-unix-2.0 glib-2.0 mpv` 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now `pkg-config --libs 
> gio-2.0 gio-unix-2.0 glib-2.0` -shared -fPIC
> Package wayland-protocols was not found in the pkg-config search path.
> Perhaps you should add the directory containing `wayland-protocols.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'wayland-protocols', required by 'mpv', not found
> mpris.c:1:10: fatal error: gio/gio.h: No such file or directory
> 1 | #include 
>   |  ^~~
> compilation terminated.
> make[1]: *** [Makefile:27: mpris.so] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/mpv-mpris_0.7.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mpv
Source-Version: 0.35.0-4
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
mpv, 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.
Sebastian Ramacher  (supplier of updated mpv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Dec 2022 22:27:12 +0100
Source: mpv
Architecture: source
Version: 0.35.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1026624
Changes:
 mpv (0.35.0-4) unstable; urgency=medium
 .
   * Team upload
   * debian/control: Add wayland-protocols to libmpv-dev's dependencies
 (Closes: #1026624)
Checksums-Sha1:
 7c2f2cba87d2ebecf2bac2c3f8369195819a5678 3017 mpv_0.35.0-4.dsc
 cdde44ca42d1250b56d078e4396998ade0409e1a 14156 mpv_0.35.0-4.debian.tar.xz
Checksums-Sha256:
 9b9d0e1b33b9624fa226c4704eca97b17dcef4e059462d9de7a725c6e6b62c85 3017 
mpv_0.35.0-4.dsc
 c21e81835e77325a171868c2d259bcc172b79a56ae60dea9cbfd678c51e0dbc4 14156 
mpv_0.35.0-4.debian.tar.xz
Files:
 ca1102823ee44c0b81893ffec2150e71 3017 video optional mpv_0.35.0-4.dsc
 f45584ddcf5973f8fa37c515ecf3ffc2 14156 video optional 
mpv_0.35.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmOjfFEVHHNyYW1hY2hl
ckBkZWJpYW4ub3JnAAoJEGny/FFupxmTPAUP/3sxEm/gyFLhn87VtO3gcpid9cMi
Qh1rdMBmrljXlaObslr25eiltWz1s//yUzDpzOPA9WA10nx56eIJdutSaZDcsrtG
7P/UVzqlScng7PONG9IuZIW/p2/PxCqC54B/aby+WmJzZwToiIGsa1LDSnC8J0u6
FfwaooyzvrqFlyfT2u+0644XBolaRP0Uu+Ko16/fXIisPZ2IrhvTmsZbx7YMH1Bf
d6ZJox7oiwyn8qaaGf1j6ASM1d893WjEWUncqja/g33BSR70RW/Eckup9MUAliY3
L5xf6VgRStkvSIri66/aT/EFMgRVNV6AXDvEvk67lmKy0zkgAMBJHLFDfOPNnxRm

Bug#1026666: Please make liblog4j2-java depend on junit5

2022-12-21 Thread tony mancill

On Tue, Dec 20, 2022 at 11:45:54PM +0100, Pierre Gruet wrote:
> Control: retitle -1 Please make liblog4j2-java depend on junit5
> 
> Hello,
> 
> In version 2.19.0-1 of liblog4j2-java, the file
>   
> /usr/share/maven-repo/org/apache/logging/log4j/log4j/debian/log4j-debian.pom
> declares the junit-bom artifact as a dependency. It is shipped in junit5.
> 
> If this dependency is not added, reverse dependencies of liglog4j2-java fail
> to build (see logs above) as the junit-bom artifact is not found.

Hi Pierre,

I'm wondering if it wouldn't better to remove junit-bom from log4j pom.
I don't believe we actually need junit5 at runtime for log4j2, so
packages depending on liblog4j2-java should not have to install junit5.

Any concerns with taking that approach and addressing the bug by
adjusting the pom shipped with liblog4j2-java?

Thanks,
tony

signature.asc
Description: PGP signature

Bug#1026546: marked as done (zope.testing: FTBFS: AssertionError: Failed doctest test for doctestcase.txt)

Your message dated Wed, 21 Dec 2022 21:50:44 +
with message-id 
and subject line Re: Bug#1026546: zope.testing: FTBFS: AssertionError: Failed 
doctest test for doctestcase.txt
has caused the Debian Bug report #1026546,
regarding zope.testing: FTBFS: AssertionError: Failed doctest test for 
doctestcase.txt
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.)


-- 
1026546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zope.testing
Version: 4.10-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 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:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:286: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, 
> consider using implicit namespaces instead (PEP 420).
>   warnings.warn(msg, SetuptoolsDeprecationWarning)
> running config
> I: pybuild base:240: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:286: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, 
> consider using implicit namespaces instead (PEP 420).
>   warnings.warn(msg, SetuptoolsDeprecationWarning)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:286: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, 
> consider using implicit namespaces instead (PEP 420).
>   warnings.warn(msg, SetuptoolsDeprecationWarning)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_zope.testing/build/zope
> copying src/zope/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope
> creating 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/doctestcase.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/tests.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/renormalizing.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/loghandler.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/test_renormalizing.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/setupstack.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/module.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/server.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/wait.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/loggingsupport.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/formparser.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/testrunner.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> copying src/zope/testing/cleanup.py -> 
> /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing
> running egg_info
> writing src/zope.testing.egg-info/PKG-INFO
> writing dependency_links to src/zope.testing.egg-info/dependency_links.txt
> writing namespace_packages to src/zope.testing.egg-info/namespace_packages.txt
> writing requirements to src/zope.testing.egg-info/requires.txt
> writing top-level names to src/zope.testing.egg-info/top_level.txt
> reading manifest file 'src/zope.testing.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.txt' under directory 'docs'
> warning: no files found matching 'Makefile' under directory 'docs'
> adding license file 'LICENSE.txt'
> writing manifest file 'src/zope.testing.egg-info/SOURCES.txt'
> copying src/zope/testing/cleanup.txt -> 
>

Bug#1026617: marked as done (libjt400-java: FTBFS: [javac] /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: reference to Record is ambiguous)

Your message dated Wed, 21 Dec 2022 21:24:44 +
with message-id 
and subject line Bug#1026617: fixed in libjt400-java 9.4-2
has caused the Debian Bug report #1026617,
regarding libjt400-java: FTBFS: [javac] 
/<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: 
reference to Record is ambiguous
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.)


-- 
1026617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjt400-java
Version: 9.4-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):
> make[1]: Entering directory '/<>'
> #this build the ant task required by ant
> cd build && javac -cp /usr/share/java/ant.jar *.java
> Note: PCMLTask.java uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> #link required libraries
> ln -s /usr/share/java/servlet-api-3.1.jar include/servlet.jar
> #run ant
> ant -lib .:./build jar8 -Dbuild=. -Djdk18=/usr
> Buildfile: /<>/build.xml
> 
> init:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been 
> set to 1610029695
> [mkdir] Created dir: /<>/jdbc40
> [mkdir] Created dir: /<>/jdbc42
> [mkdir] Created dir: /<>/dist
> [mkdir] Created dir: /<>/dist6
> [mkdir] Created dir: /<>/dist8
> [mkdir] Created dir: /<>/javadoc
> [mkdir] Created dir: /<>/javadoc6
> [mkdir] Created dir: /<>/javadoc8
> [mkdir] Created dir: /<>/javadoc-jtopenlite
> [mkdir] Created dir: /<>/output
> [mkdir] Created dir: /<>/output6
> [mkdir] Created dir: /<>/output8
> [mkdir] Created dir: /<>/output-jtopenlite
> [mkdir] Created dir: /<>/output-micro
> [mkdir] Created dir: /<>/output-micro-verified
> [mkdir] Created dir: /<>/output-android
> [mkdir] Created dir: /<>/android
> [mkdir] Created dir: /<>/output-android6
> [mkdir] Created dir: /<>/android6
> [mkdir] Created dir: /<>/bin
> 
> source-jdbc42:
>  [echo]  Processing jdbc42 file from ./src to ./jdbc42 
> [jdbc42src] Number of files processed: 94
> 
> source8:
>  [copy] Copying 1840 files to /<>/java8
>  [copy] Copied 21 empty directories to 1 empty directory under 
> /<>/java8
>  [copy] Copying 94 files to /<>/java8
>  [copy] Copying 1 file to /<>/build/META-INF/services
> 
> compile8:
> [javac] Compiling 1500 source files to /<>/output8
> [javac] 
> /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: 
> error: reference to Record is ambiguous
> [javac] public RecordFormatDocument(Record record)
> [javac] ^
> [javac]   both class com.ibm.as400.access.Record in com.ibm.as400.access 
> and class java.lang.Record in java.lang match
> [javac] 
> /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:1288: 
> error: reference to Record is ambiguous
> [javac] public void setValues(String formatName, Record record)
> [javac]  ^
> [javac]   both class com.ibm.as400.access.Record in com.ibm.as400.access 
> and class java.lang.Record in java.lang match
> [javac] 
> /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:1375: 
> error: reference to Record is ambiguous
> [javac] public Record toRecord(String formatName)
> [javac]^
> [javac]   both class com.ibm.as400.access.Record in com.ibm.as400.access 
> and class java.lang.Record in java.lang match
> [javac] 
> /<>/java8/com/ibm/as400/data/RfmlRecordFormat.java:555: error: 
> reference to Record is ambiguous
> [javac] public void setValues(Record record)
> [javac]   ^
> [javac]   both class com.ibm.as400.access.Record in com.ibm.as400.access 
> and class java.lang.Record in java.lang match
> [javac] 
> /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:881: 
> error: reference to RecordFormatDocument is ambiguous
> [javac]   RecordFormatDocument doc = new 
> RecordFormatDocument(args[1]);
> [javac]  ^
> [javac]   both constructor RecordFormatDocument(String) in 
> RecordFormatDocument and constructor RecordFormatDocument(Record) in 
> RecordFormatDocument match
> [javac] 
>

Bug#1026617: marked as pending in libjt400-java

2022-12-21 Thread Tony Mancill

Control: tag -1 pending

Hello,

Bug #1026617 in libjt400-java 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/libjt400-java/-/commit/951604f34305c1bfb004d407bd54812c18202394


Add patch to complie on Java 17 (Closes: #1026617)

Thank you to Hans Joachim Desserud  for the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026617

Processed: Bug#1026617 marked as pending in libjt400-java

Processing control commands:

> tag -1 pending
Bug #1026617 [src:libjt400-java] libjt400-java: FTBFS: [javac] 
/<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: 
reference to Record is ambiguous
Added tag(s) pending.

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

Bug#1026617: libjt400-java: FTBFS: [javac] /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: reference to Record is ambiguous

2022-12-21 Thread tony mancill

On Wed, Dec 21, 2022 at 12:07:24PM +0100, Hans Joachim Desserud wrote:
> tags 1026617 patch
> thanks
> 
> > [javac]   both class com.ibm.as400.access.Record in
> > com.ibm.as400.access and class java.lang.Record in java.lang match
> > [javac]
> > /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:1375:
> > error: reference to Record is ambiguous
> 
> Looks like the ambiguity stems from the new Record class introduced in new
> JDKS which hit when rebuilt with JDK 17. See the attached patch which adds
> an explicit import to the "local" Record class, which has been the one
> imported up until now.
> 
> With this patch in place, the package builds successfully again on Debian
> Sid.

Thank you for the patch!  Applied and uploaded.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#1026718: lazpaint: FTBFS: /usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No such file or directory

2022-12-21 Thread Juliette DAMON-ELSASS

Relevant part is:
> (9015) Linking /<>/lazpaint/release/bin/lazpaint
> /usr/bin/ld.bfd: cannot find -lgdk-x11-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lgtk-x11-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lX11: No such file or directory
> /usr/bin/ld.bfd: cannot find -lgdk_pixbuf-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lgobject-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lglib-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lgthread-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lgmodule-2.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lpango-1.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lcairo: No such file or directory
> /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
> /usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No such file or directory
> /<>/lazpaint/lazpaint.lpr(229,1) Error: (9013) Error while 
> linking

It does not find the libraries. Is there a change of availability of those?

Bug#1026640: marked as done (python-ecdsa: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Wed, 21 Dec 2022 20:39:15 +
with message-id 
and subject line Bug#1026640: fixed in python-ecdsa 0.18.0-3
has caused the Debian Bug report #1026640,
regarding python-ecdsa: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.11 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.)


-- 
1026640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ecdsa
Version: 0.18.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 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:240: python3.11 setup.py config 
> running config
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/_sha3.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/curves.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_curves.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/_rwlock.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/util.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_sha3.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/ecdsa.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/rfc6979.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/errors.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/numbertheory.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_pyecdsa.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_ecdsa.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_numbertheory.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/_compat.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/eddsa.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_eddsa.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/der.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_der.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/keys.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_keys.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_ecdh.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_rw_lock.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_malformed_sigs.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/ellipticcurve.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_ellipticcurve.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/test_jacobi.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/_version.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> copying src/ecdsa/ecdh.py -> 
> /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa
> UPDATING /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa/_version.py
> set /<>/.pybuild/cpython3_3.11_ecdsa/build/ecdsa/_version.py to 
> '0.18.0'
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/_sha3.py -> 
> /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/curves.py -> 
> /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/test_curves.py -> 
> /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/_rwlock.py -> 
> /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/util.py -> 
> /<>/.pybuild/cpython3_3.10_ecdsa/build/ecdsa
> copying src/ecdsa/test_sha3.py -> 
>

Bug#1026773: marked as done (libcap2: autopkgtest failures block other packages from migrating)

Your message dated Wed, 21 Dec 2022 20:36:28 +
with message-id 
and subject line Bug#1026773: fixed in libcap2 1:2.66-3
has caused the Debian Bug report #1026773,
regarding libcap2: autopkgtest failures block other packages from migrating
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.)


-- 
1026773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcap2
Version: 1:2.66-2
Severity: serious
Jutsification: stops other packages from migrating to testing

Hi,

The autopkgtest run for the latest version of libcap2 in unstable
fails on all architectures:

autopkgtest [18:14:20]: test upstream-nonroot:  - - - - - - - - - -
results - - - - - - - - - -
upstream-nonroot FAIL stderr: dpkg-architecture: warning: cannot
determine CC system type, falling back to default (native compilation)

https://ci.debian.net/packages/libc/libcap2/testing/amd64/

This stops unrelated packages from migrating to testing. Please
consider either fixing the tests or removing them to unblock other
packages.

Thanks!

Kind regards,
Luca Boccassi
--- End Message ---
--- Begin Message ---
Source: libcap2
Source-Version: 1:2.66-3
Done: Christian Kastner 

We believe that the bug you reported is fixed in the latest version of
libcap2, 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.
Christian Kastner  (supplier of updated libcap2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 21:19:49 +0100
Source: libcap2
Architecture: source
Version: 1:2.66-3
Distribution: unstable
Urgency: medium
Maintainer: Christian Kastner 
Changed-By: Christian Kastner 
Closes: 1026773
Changes:
 libcap2 (1:2.66-3) unstable; urgency=medium
 .
   * Add gcc to autopkgtest for upstream tests.
 Otherwise dpkg-architecture prints a warning to stderr, triggering a
 an autopkgtest FAIL. (Closes: #1026773)
Checksums-Sha1:
 60efb85b6f548269ca01b1507f7608f123a82d82 2204 libcap2_2.66-3.dsc
 a089b00ecd80af5ba8a04fff0aa9b7e3be36c553 20196 libcap2_2.66-3.debian.tar.xz
 70c6ebf0d62b1a1bdbc4d91ad5899da397267e40 5828 libcap2_2.66-3_source.buildinfo
Checksums-Sha256:
 0fa3650cb450b1d2056cf28b2433683552ddc4f2bceecd834ec050bc65ae762d 2204 
libcap2_2.66-3.dsc
 d300a825188f7253021c26dbdaec24b4c7bff3e8717286a1af1f3292601d3069 20196 
libcap2_2.66-3.debian.tar.xz
 1e5674e5a68eee7f1e3da4734cd5571c99da1a879457d39604e3e1447187bcd1 5828 
libcap2_2.66-3_source.buildinfo
Files:
 7007161d8abb7ad6fc0022af83fb55c4 2204 libs optional libcap2_2.66-3.dsc
 1b20b1f7d62f2ec8e76e8c2da1a629be 20196 libs optional 
libcap2_2.66-3.debian.tar.xz
 8ee3b524c1f3ad7f9bc7b455478c4ae4 5828 libs optional 
libcap2_2.66-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQZ9+mkfDq5UZ8bCjOZU6N95Os2sFAmOja2sACgkQOZU6N95O
s2u+ug//TwF9B0yUuQ16rG4d1pDtrix5sn0Adz26hCtxLX3Ik9ynTYCHtPSAizMY
Dsqwlg1qD3QTSRj5kpAyizZIEk9JnWI7OMg3ih52gHUjOESwzV3AYWxe6iQmzIb/
SRjfgYH72XcbGSW/8CtltScGHLNDNJwL6CwzU5UIRClpg7MMdl9P5tIeehtPd6m5
23OLdZf1zmZd+IofAjberrKhTq2mO+WfcaVBDo0dExv1r83K3A0wK3nFFcJS/ssr
iiigEh207jSap9KpHTTSLPmCWg3tBAZ7aOcspPbFmci3hygQSK7H++nb177m7fyv
I/IGsawqSg6qHQ7HMKTilsrPTzj7D7aFjKAZQKgRoAkdkAg9LNmPbwBkzWPiy++C
3gVeiseuwNfaT8wSts8L0ISoWjXkaH3J1WTDj2eoqi/HuI59FnZacNp9SIKQMI7L
l82Wl32PyQ2+6W+CpbMSCeYZaIGZjGYZaA+baHIMqHgCe9tuFef0trc6yodO1eFX
4HXk/bOHSLO4To469pYhySf9OxSofvDYT+NIPjjB09xM9PP3moe0pMEz6NKf0xPA
I2VOvB7ef7+do1EFNEa8A7d4YsVGUCiVIlnFCGqJ5PEYGJWF9/EOAemCF+nVnu98
drqAnh3fdRq7MeJlar+/YvSAOWBCxBIcC8sMcYLkDAKDrU6M/bI=
=cwFR
-END PGP SIGNATURE End Message ---

Bug#1026608: marked as done (jcommander: FTBFS: JCommander.java:45: error: malformed HTML)

Your message dated Wed, 21 Dec 2022 20:36:06 +
with message-id 
and subject line Bug#1026608: fixed in jcommander 1.71-4
has caused the Debian Bug report #1026608,
regarding jcommander: FTBFS: JCommander.java:45: error: malformed HTML
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.)


-- 
1026608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jcommander
Version: 1.71-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[1]: Entering directory '/<>'
> dh_auto_build -- assemble javadoc
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=jcommander -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 assemble javadoc
> OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=permit; 
> support was removed in 17.0
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-17-openjdk-amd64/bin/java 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  --add-opens java.base/java.lang=ALL-UNNAMED -Dfile.encoding=UTF-8 
> -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 0.906 secs.
> The client will now receive all logging from the daemon (pid: 1202805). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-1202805.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@2330d380
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@2330d380
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@4b34c716
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@34dd2b4c
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
>   Settings file not found (/<>/settings.gradle)
>   Root project name not defined in settings.gradle, defaulting to 
> 'jcommander' instead of the name of the root directory 'jcommander-1.71'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'jcommander']
>   Keep-alive timer started
>   Adding Debian repository to project 'jcommander'
> Parallel execution is an incubating feature.
> Evaluating root project 'jcommander' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/build.gradle' using 
> BuildScriptTransformer.
>   Adding Maven pom generation to project 'jcommander'
>   Linking the generated javadoc to the system JDK API documentation
> All projects evaluated.
> Selected primary task 'assemble' from project :
> Creating new cache for annotation-processors, path 
> /<>/.gradle/4.4.1/fileContent/annotation-processors.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@28ebf1f5
> Selected primary task 'javadoc' from project :
> Tasks to be executed: [task ':compileJava', task ':processResources', task 
> ':classes', task ':debianMavenPom', task

Bug#1026616: marked as done (mkdocstrings-python-legacy: FTBFS: make: *** [debian/rules:15: binary] Error 25)

Your message dated Wed, 21 Dec 2022 20:37:42 +
with message-id 
and subject line Bug#1026616: fixed in mkdocstrings-python-legacy 0.2.3-4
has caused the Debian Bug report #1026616,
regarding mkdocstrings-python-legacy: FTBFS: make: *** [debian/rules:15: 
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.)


-- 
1026616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkdocstrings-python-legacy
Version: 0.2.3-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):
>  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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_mkdocstrings 
> * Building wheel...
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 351, in 
> main()
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 333, in main
> json_out['return_val'] = hook(**hook_input['kwargs'])
>  
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 249, in build_wheel
> return _build_backend().build_wheel(wheel_directory, config_settings,
>^^
>   File "/usr/lib/python3/dist-packages/pdm/pep517/api.py", line 75, in 
> build_wheel
> builder.build(wheel_directory, metadata_directory=metadata_directory)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 151, in 
> build
> self._copy_module()
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 321, in 
> _copy_module
> root = self.meta.config.package_dir or self.location
>^
>   File "/usr/lib/python3/dist-packages/pdm/pep517/base.py", line 154, in meta
> self._meta.validate(True)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/metadata.py", line 58, in 
> validate
> return validate_pep621(self.data, raising)
>^^^
>   File "/usr/lib/python3/dist-packages/pdm/pep517/validator.py", line 85, in 
> validate_pep621
> raise PEP621ValidationError(validator.errors)
> pdm.pep517.exceptions.PEP621ValidationError: {'license-expression': ['unknown 
> field']}
> 
> ERROR Backend subproccess exited when trying to invoke build_wheel
> E: pybuild pybuild:386: build: plugin pyproject failed with: exit code=1: 
> python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_mkdocstrings 
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build" 
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10_mkdocstrings 
> * Building wheel...
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 351, in 
> main()
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 333, in main
> json_out['return_val'] = hook(**hook_input['kwargs'])
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 249, in build_wheel
> return _build_backend().build_wheel(wheel_directory, config_settings,
>   File "/usr/lib/python3/dist-packages/pdm/pep517/api.py", line 75, in 
> build_wheel
> builder.build(wheel_directory, metadata_directory=metadata_directory)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 151, in 
> build
> self._copy_module()
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 321, in 
> _copy_module
> root = self.meta.config.package_dir or self.location
>   File "/usr/lib/python3/dist-packages/pdm/pep517/base.py", line 154, in meta
> self._meta.validate(True)
>   File "/usr/lib/python3/dist-packages/pdm/pep517/metadata.py", line 58, in 
> validate
> return validate_pep621(self.data, raising)
>   File

Bug#1019937: marked as done (elfutils: Missing licenses in d/copyright)

Your message dated Wed, 21 Dec 2022 20:35:14 +
with message-id
and subject line Bug#1019937: fixed in elfutils 0.188-2
has caused the Debian Bug report #1019937,
regarding elfutils: Missing licenses in d/copyright
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.)

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

Source: elfutils
Severity: serious
Version: 0.187-2

elfutils' debian/copyright file is missing at least the BSD-2-clause license
and the GFDL-NIV-1.3 license.
Please find a machine-readable copyright file attached that includes them.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: This package was debianized by Kurt Roeckx .
Source: https://sourceware.org/elfutils/ftp/

Files: *
debuginfod/debuginfod-find.c
Copyright: (C) 1996-2019 Red Hat, Inc.
(C) 2022 Mark J. Wielaard
(C) 2015, 2016 Oracle, Inc.
(C) 2017 The Qt Company
(C) 2018, 2021 Facebook, Inc.
(C) 2021 Runsafe Security, Inc.
(C) H.J. Lu , 2015.
(C) 2020 Tom Tromey
Comment: Written by:
Ulrich Drepper
Jeff Johnson
Alexander Larsson
Jakub Jelinek
Roland McGrath .
See more in the AUTHORS file.
License: GPL-3+

Files: backends/*
config/*
debuginfod/*
lib*
version.h
debian/patches/mips_cfi.patch
Copyright: (C) 1996-2019 Red Hat, Inc.
(C) 2021, 2022 Mark J. Wielaard
(C) 2015 Oracle, Inc.
(C) 2016, 2017 The Qt Company Ltd.
(C) 2021 Google, Inc.
(C) 2012 Tilera Corporation
(C) 2019 Hangzhou C-SKY Microsystems co.,ltd.
(C) H.J. Lu , 2015.
(c) 2021 Dmitry V. Levin
(C) 2018 Sifive, Inc.
(C) 2018 Kurt Roeckx, Inc.
Comment: Most of the libraries (lib, libelf, libebl, libdw, libdwfl) have
the following license:
License: LGPL-3+ or GPL-2+
This file is free software; you can redistribute it and/or modify
it under the terms of either
.
* the GNU Lesser General Public License as published by the Free
Software Foundation; either version 3 of the License, or (at
your option) any later version
.
or
.
* the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at
your option) any later version
.
or both in parallel, as here.
.
elfutils is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
.
You should have received copies of the GNU General Public License and
the GNU Lesser General Public License along with this program. If
not, see .
Comment:
On Debian GNU/Linux systems, the complete text of the GNU General
Public License version 2 can be found in
`/usr/share/common-licenses/GPL-2' and the complete text of the GNU
Lesser General Public License version 3 can be found in
`/usr/share/common-licenses/LGPL-3'.

Files: lib/stdatomic-fbsd.h
Copyright: (c) 2011 Ed Schouten
David Chisnall
All rights reserved.
License: BSD-2-clause
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH

Bug#1019937: NMU: elfutils: Missing licenses in d/copyright

2022-12-21 Thread Sergio Durigan Junior

On Wednesday, December 21 2022, Bastian Germann wrote:

> I am uploading a NMU to DELAYED/10 to fix this. debdiff is attached.

Hi Bastian,

Thanks for the heads up, and sorry for the delay.  I applied your
changes, made a few cosmetic adjustments and uploaded a new version to
unstable.  Could you cancel your NMU upload, please?

Thanks a lot,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Processed: severity of 1024626 is important

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

> severity 1024626 important
Bug #1024626 [src:blender] blender FTBFS on 32bit
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1026828: libgmpada: FTBFS on i386: raised ADA.ASSERTIONS.ASSERTION_ERROR : demo.adb:119

2022-12-21 Thread Nicolas Boulenguez

Source: libgmpada
Version: 1.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build on a supported architecture

A post-build test fails on i386 buildds:
https://buildd.debian.org/status/fetch.php?pkg=libgmpada=i386=1.5-1=1671621582=0
https://buildd.debian.org/status/fetch.php?pkg=libgmpada=i386=1.5-1=1661971646=0
but succeeds on an i386 porterbox.

Bug#1023712: why3 breaks frama-c (autopkgtest): missing versioned Breaks?

2022-12-21 Thread Paul Gevers


Control: reassign -1 frama-c

Dear maintainers,

On Tue, 8 Nov 2022 21:53:18 +0100 Paul Gevers  wrote:

[kernel] User Error: cannot load plug-in 'frama-c-wp': cannot load module
   Details: implementation mismatch on Why3
[kernel] User Error: Deferred error message was emitted during 
execution. See above messages for more information.

[kernel] Frama-C aborted: invalid user input.
autopkgtest [20:18:19]: test eva


I'm now seeing the above error message in the frama-c test in testing, 
so it seems that the issue is rather that the autopkgtest of frama-c 
doesn't properly declare it's *versioned* test dependency on why3? 
Should the Recommends be versioned? (Not sure if that actually works as 
intended, but apparently the tested plug-in only works correctly with 
the right version of why3).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: why3 breaks frama-c (autopkgtest): missing versioned Breaks?

Processing control commands:

> reassign -1 frama-c
Bug #1023712 [src:why3] why3 breaks frama-c (autopkgtest): missing versioned 
Breaks?
Bug reassigned from package 'src:why3' to 'frama-c'.
No longer marked as found in versions why3/1.5.1-1.
Ignoring request to alter fixed versions of bug #1023712 to the same values 
previously set

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

Bug#1026608: marked as pending in jcommander

Control: tag -1 pending

Hello,

Bug #1026608 in jcommander 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/jcommander/-/commit/faa56c48a90d96905c35775ee83741ee4a610f1b


Add patch to fix FTBFS (Closes: #1026608)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026608

Processed: Bug#1026608 marked as pending in jcommander

Processing control commands:

> tag -1 pending
Bug #1026608 [src:jcommander] jcommander: FTBFS: JCommander.java:45: error: 
malformed HTML
Added tag(s) pending.

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

Bug#1026827: xrdp: initially xrdp worked ok, but later it broke, and the problem was /etc/xrdp/startwm.sh that changed

2022-12-21 Thread Dominik George

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

Hi,

> Severity: critical
> Justification: breaks the whole system

I doubt that very much. Are you sure that the whole system stopped
working because you could not start a session in xrdp? As in, no login
on the tty possible, the kernel crashing, boot failed, or the like?

>* What led up to the situation?

What did yo udo *before* the file was renamed?

I am pretty certain that this is not something the package did.

How is the syste mmanaged?

Did the change happen in correlation with a package update?

-nik


signature.asc
Description: PGP signature

Processed: Re: Bug#1026827: xrdp: initially xrdp worked ok, but later it broke, and the problem was /etc/xrdp/startwm.sh that changed

Processing control commands:

> tags -1 + moreinfo
Bug #1026827 [xrdp] xrdp: initially xrdp worked ok, but later it broke, and the 
problem was /etc/xrdp/startwm.sh that changed
Added tag(s) moreinfo.
> severity -1 normal
Bug #1026827 [xrdp] xrdp: initially xrdp worked ok, but later it broke, and the 
problem was /etc/xrdp/startwm.sh that changed
Severity set to 'normal' from 'critical'

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

Bug#1026686: marked as done (compreffor: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

Your message dated Wed, 21 Dec 2022 19:19:09 +
with message-id 
and subject line Bug#1026686: fixed in compreffor 0.5.3-2
has caused the Debian Bug report #1026686,
regarding compreffor: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
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.)


-- 
1026686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: compreffor
Version: 0.5.3-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):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> Development mode: Compiling Cython modules from .pyx sources.
> running clean
> removing '/<>/.pybuild/cpython3_3.11_compreffor/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
> I: pybuild base:240: python3.10 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> Development mode: Compiling Cython modules from .pyx sources.
> running clean
> removing '/<>/.pybuild/cpython3_3.10_compreffor/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.10' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building compreffor using existing 
> ./compreffor_0.5.3.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  compreffor-0.5.3/src/python/compreffor/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/compreffor_0.5.3-1.diff.7qXHok
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2022-12-20T09:46:50Z


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/compreffor_0.5.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: compreffor
Source-Version: 0.5.3-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
compreffor, 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.
Nilesh Patra  (supplier of updated compreffor 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

Bug#1022404: raqm: diff for NMU version 0.7.0-4.1

On Sat, 19 Nov 2022 21:19:24 +0200 Adrian Bunk  wrote:
> Control: tags 1022404 + patch
> Control: tags 1022404 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for raqm (versioned as 0.7.0-4.1) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it.

It has been 15 days past your upload but it has not reflected yet in
the archive. Did you happen to cancel your NMU?

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#958853: Fix

2022-12-21 Thread Julian Gilbey

On Wed, Dec 21, 2022 at 07:24:38PM +0100, Dan O'Huiginn wrote:
> Upstream has now moved away from Bazel: 
> https://github.com/ankitects/anki/commit/5e0a761b875fff4c9e4b202c08bd740c7bb37763
> 
> The new build system uses cargo and ninja. It'll still be a substantial job 
> to package this for Debian, but hopefully more feasible than before.

Oh wow, that's good news, thanks!  I don't know whether I'll have time
to do it before the freeze, though - I am very overloaded at the
moment, unfortunately.  (And unless something's changed, upstream were
using some locally modified Rust crates, which just added to the
pain.)

Best wishes,

   Julian

Processed (with 1 error): ansible-lint dropped its tests

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

> reassign 1025981 src:ansible-lint 6.3.0-2
Bug #1025981 [src:ansible-core, src:ansible-lint] ansible-core breaks 
ansible-lint autopkgtest: Ansible requires the locale encoding to be UTF-8; 
Detected None.
Bug reassigned from package 'src:ansible-core, src:ansible-lint' to 
'src:ansible-lint'.
No longer marked as found in versions ansible-core/2.14.0-1 and 
ansible-lint/6.3.0-2.
Ignoring request to alter fixed versions of bug #1025981 to the same values 
previously set
Bug #1025981 [src:ansible-lint] ansible-core breaks ansible-lint autopkgtest: 
Ansible requires the locale encoding to be UTF-8; Detected None.
Marked as found in versions ansible-lint/6.3.0-2.
> affects 1025981 src:ansible-core
Bug #1025981 [src:ansible-lint] ansible-core breaks ansible-lint autopkgtest: 
Ansible requires the locale encoding to be UTF-8; Detected None.
Added indication that 1025981 affects src:ansible-core
> fixed 1025981 6.3.0-3
Bug #1025981 [src:ansible-lint] ansible-core breaks ansible-lint autopkgtest: 
Ansible requires the locale encoding to be UTF-8; Detected None.
The source 'ansible-lint' and version '6.3.0-3' do not appear to match any 
binary packages
Marked as fixed in versions ansible-lint/6.3.0-3.
> close 1025981
Bug #1025981 [src:ansible-lint] ansible-core breaks ansible-lint autopkgtest: 
Ansible requires the locale encoding to be UTF-8; Detected None.
Marked Bug as done
> thansk
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1026827: xrdp: initially xrdp worked ok, but later it broke, and the problem was /etc/xrdp/startwm.sh that changed

2022-12-21 Thread alex

Package: xrdp
Version: 0.9.12-1.1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: alexb...@gmail.com

Dear Maintainer,

   * What led up to the situation?
the remmina-rdp and android ms-rdesktop initially worked ok, 
but after this change began to show a black screen and close it.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
upstream discussion led me to check /etc/xrdp/startwm.sh that not only seemed 
broken, 
but the version that seemed ok (and later worked indeed) was renamed to 
/etc/xrdp/startwm.sh0.
the broken version was also in a file /etc/xrdp/startwm.sh1.
   * What was the outcome of this action?
xrdp was initially working until the day before, when it showed a black window 
and disconnected.
   * What outcome did you expect instead?
after i suspected this file was broken, and replaced it with 
/etc/xrdp/startwm.sh0 that was by it's side.


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

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

Versions of packages xrdp depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libc62.31-13+deb11u5
ii  libfuse2 2.9.9-5
ii  libjpeg62-turbo  1:2.0.6-4
ii  libopus0 1.3.1-0.1
ii  libpam0g 1.4.0-9+deb11u1
ii  libssl1.11.1.1n-0+deb11u3
ii  libx11-6 2:1.7.2-1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 11.1.0
ii  ssl-cert 1.1.0+nmu1

Versions of packages xrdp recommends:
ii  fuse3 [fuse]  3.10.3-2
ii  xorgxrdp  1:0.2.12-1

Versions of packages xrdp suggests:
pn  guacamole  
pn  xrdp-pulseaudio-installer  

Versions of packages xorgxrdp depends on:
ii  libc6  2.31-13+deb11u5
ii  libepoxy0  1.5.5-1
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.11-1+deb11u4

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+22

Versions of packages xrdp is related to:
pn  vnc-server   
ii  xserver-xorg-legacy  2:1.20.11-1+deb11u4

-- Configuration Files:
/etc/xrdp/startwm.sh changed:
if [ -r /etc/default/locale ]; then
. /etc/default/locale
export LANG LANGUAGE
fi
startxfce4

/etc/xrdp/xrdp.ini changed:
[Globals]
; xrdp.ini file version number
ini_version=1
; fork a new process for each incoming connection
fork=true
; ports to listen on, number alone means listen on all interfaces
; 0.0.0.0 or :: if ipv6 is configured
; space between multiple occurrences
;
; Examples:
;   port=3389
;   port=unix://./tmp/xrdp.socket
;   port=tcp://.:3389   127.0.0.1:3389
;   port=tcp://:3389*:3389
;   port=tcp://:3389  192.168.1.1:3389
;   port=tcp6://.:3389  ::1:3389
;   port=tcp6://:3389   *:3389
;   port=tcp6://{}:3389   {FC00:0:0:0:0:0:0:1}:3389
;   port=vsock://:
port=3389
;port=tcp://.:3389
; 'port' above should be connected to with vsock instead of tcp
; use this only with number alone in port above
; prefer use vsock://: above
use_vsock=false
; regulate if the listening socket use socket option tcp_nodelay
; no buffering will be performed in the TCP stack
tcp_nodelay=true
; regulate if the listening socket use socket option keepalive
; if the network connection disappear without close messages the connection 
will be closed
tcp_keepalive=true
; set tcp send/recv buffer (for experts)
; security layer can be 'tls', 'rdp' or 'negotiate'
; for client compatible layer
security_layer=negotiate
; minimum security level allowed for client for classic RDP encryption
; use tls_ciphers to configure TLS encryption
; can be 'none', 'low', 'medium', 'high', 'fips'
crypt_level=high
; X.509 certificate and private key
; openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 
365
; note this needs the user xrdp to be a member of the ssl-cert group, do with 
e.g.
;$ sudo adduser xrdp ssl-cert
certificate=
key_file=
; set SSL protocols
; can be comma separated list of 'SSLv3', 'TLSv1', 'TLSv1.1', 'TLSv1.2', 
'TLSv1.3'
ssl_protocols=TLSv1.2, TLSv1.3
;ssl_protocols=TLSv1, TLSv1.1, TLSv1.2, TLSv1.3
; set TLS cipher suites
; Section name to use for automatic login if the client sends username
; and password. If empty, the domain name sent by the client is used.
; If empty and no domain name is given, the first suitable section in
; this file will be used.
autorun=
allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
max_bpp=32
new_cursors=true
; fastpath - can be

Bug#1013646: marked as done (apertium-swe-nor: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)

Your message dated Wed, 21 Dec 2022 18:34:16 +
with message-id 
and subject line Bug#1013646: fixed in apertium-swe-nor 0.4.0-1
has caused the Debian Bug report #1013646,
regarding apertium-swe-nor: FTBFS: configure: error: Package requirements 
(apertium-lex-tools >= 0.2.2) were not met
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.)


-- 
1013646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-swe-nor
Version: 0.3.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.6.0... yes
> checking for lttoolbox >= 3.5.0... yes
> checking for cg3 >= 1.3.0... yes
> checking for apertium-lex-tools >= 0.2.2... no
> configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not 
> met
> 
> No package 'apertium-lex-tools' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS
> and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-swe-nor_0.3.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: apertium-swe-nor
Source-Version: 0.4.0-1
Done: Tino Didriksen 

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

Debian distribution maintenance software
pp.
Tino Didriksen  (supplier of updated apertium-swe-nor 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 09:10:29 +0100
Source: apertium-swe-nor
Architecture: source
Version: 0.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tino Didriksen 
Closes: 1013646
Changes:
 apertium-swe-nor (0.4.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1013646)
   * Bundles apertium-swe 0.8.2, apertium-nno 1.4.0, and apertium-nob 1.4.0
Checksums-Sha1:
 6b821b9e468a590a3d96938449e6e36dee05ed47 2240 apertium-swe-nor_0.4.0-1.dsc
 7b77269b1dff590c62bde9c51483b9c529454135 6673151 
apertium-swe-nor_0.4.0.orig.tar.bz2
 4a60ff66d7c13e6e067bcc1b028f0debbf45cf3b 2956 
apertium-swe-nor_0.4.0-1.debian.tar.xz
 5484ab7150df0f2bc5bb5a1d125308b9758b2382 7171 
apertium-swe-nor_0.4.0-1_source.buildinfo
Checksums-Sha256:
 83696b0b8cc07b04b136dcee158436553ea6bd942afaaa803fb8513dc08a2f3b 2240 
apertium-swe-nor_0.4.0-1.dsc
 e79cd60be20d6c8526ff25563ec491cc24c230454c12dc454df1d92401c74514 6673151 
apertium-swe-nor_0.4.0.orig.tar.bz2
 99549f493807f9f5196a81aad4663f036ab15e8eb216814697f195990a5416a3 2956 
apertium-swe-nor_0.4.0-1.debian.tar.xz
 fe852dc6a6f3802a2573366607feebb3570c0be7ffc0162f7d4546e61d66af63 7171 
apertium-swe-nor_0.4.0-1_source.buildinfo
Files:
 6c396d0d50fefc36b8b56b8d516bdbb4 2240 science optional 
apertium-swe-nor_0.4.0-1.dsc
 5a8ebb46cfd8fcb253c8a66281794c61 6673151 science optional

Bug#668644: marked as done ([PATCH] qmc: Helping to update to packaging format 3.0)

Your message dated Wed, 21 Dec 2022 18:37:13 +
with message-id 
and subject line Bug#668644: fixed in qmc 0.94-4.1
has caused the Debian Bug report #668644,
regarding [PATCH] qmc: Helping to update to packaging format 3.0
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.)


-- 
668644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qmc
Severity: wishlist
Tags: patch

Hi,

The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:

http://wiki.debian.org/Projects/DebSrc3.0

I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.

Thanks,
Jari

>From 0f3b359409e58018c44f5b0aaf65f8b28b3ffa59 Mon Sep 17 00:00:00 2001
From: Jari Aalto 
Date: Fri, 13 Apr 2012 22:47:02 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Signed-off-by: Jari Aalto 
---
 debian/changelog  |   11 
 debian/compat |2 +-
 debian/control|4 +--
 debian/copyright  |7 +++--
 debian/patches/00list |2 --
 debian/patches/01-wish-in-shebang.patch   |   14 ++
 debian/patches/01_wish_in_shebang.dpatch  |   36 
 debian/patches/02-run-sensible-browser.patch  |   15 ++
 debian/patches/02_run_sensible-browser.dpatch |   37 -
 debian/patches/series |2 ++
 debian/rules  |   11 +---
 debian/source/format  |1 +
 12 files changed, 58 insertions(+), 84 deletions(-)
 delete mode 100644 debian/patches/00list
 create mode 100644 debian/patches/01-wish-in-shebang.patch
 delete mode 100644 debian/patches/01_wish_in_shebang.dpatch
 create mode 100644 debian/patches/02-run-sensible-browser.patch
 delete mode 100644 debian/patches/02_run_sensible-browser.dpatch
 create mode 100644 debian/patches/series
 create mode 100644 debian/source/format

diff --git a/debian/changelog b/debian/changelog
index 419ddad..fc43073 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+qmc (0.94-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+  * Update to Standards-Version to 3.9.3.1 and debhelper to 9.
+  * Add build-arch and build-indep targets; use dh_prep in rules file.
+  * Fix copyright-without-copyright-notice (Lintian).
+  * Fix copyright-refers-to-symlink-license (Lintian).
+
+ -- Jari Aalto   Fri, 13 Apr 2012 22:42:33 +0300
+
 qmc (0.94-3) unstable; urgency=low
 
   * Suggest only www-browser again, this in the real virtual package
diff --git a/debian/compat b/debian/compat
index b8626c4..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-4
+9
diff --git a/debian/control b/debian/control
index 9081855..ecabb2d 100644
--- a/debian/control
+++ b/debian/control
@@ -2,8 +2,8 @@ Source: qmc
 Section: science
 Priority: optional
 Maintainer: Rene Engelhard 
-Build-Depends: debhelper (>= 4.0.0), dpatch
-Standards-Version: 3.6.1
+Build-Depends: debhelper (>= 9)
+Standards-Version: 3.9.3
 
 Package: qmc
 Architecture: any
diff --git a/debian/copyright b/debian/copyright
index 06dc5cf..08a14a1 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,11 +1,14 @@
 This package was debianized by Rene Engelhard  on
 Sun,  2 Nov 2003 01:24:58 +0100.
 
-It was downloaded from http://qmc.pollaknet.at/
+It was downloaded from http://qmc.pollaknet.at/ which as of
+2012-04-13 no longer exists.
 
 Upstream Author: Thomas Pollak 
 
 Copyright:
 
+	Copyright (C) 2000 Thomas Pollak 
+
 GNU GPL, on Debian systems you can find the full text of the GPL
-under /usr/share/common-licenses/GPL
+under /usr/share/common-licenses/GPL-2
diff --git a/debian/patches/00list b/debian/patches/00list
deleted file mode 100644
index 6ba9c10..000
--- a/debian/patches/00list
+++ /dev/null
@@ -1,2 +0,0 @@
-01_wish_in_shebang
-02_run_sensible-browser
diff --git a/debian/patches/01-wish-in-shebang.patch b/debian/patches/01-wish-in-shebang.patch
new file mode 100644
index 000..79e4a05
--- /dev/null
+++

Bug#1026642: marked as done (python-promise: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Wed, 21 Dec 2022 19:15:33 +0100
with message-id 
and subject line Re: Bug#1026642: python-promise: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit 
code 13
has caused the Debian Bug report #1026642,
regarding python-promise: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.11 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.)


-- 
1026642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-promise
Version: 2.3.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 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:240: python3.11 setup.py config 
> running config
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/promise.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/dataloader.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/promise_list.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/compat.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/async_.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/iterate_promise.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> copying promise/utils.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> creating 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/schedulers
> copying promise/schedulers/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/schedulers
> copying promise/schedulers/asyncio.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/schedulers
> copying promise/schedulers/immediate.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/schedulers
> copying promise/schedulers/gevent.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/schedulers
> copying promise/schedulers/thread.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/schedulers
> creating /<>/.pybuild/cpython3_3.11_promise/build/promise/pyutils
> copying promise/pyutils/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/pyutils
> copying promise/pyutils/version.py -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise/pyutils
> copying promise/py.typed -> 
> /<>/.pybuild/cpython3_3.11_promise/build/promise
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/promise.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/dataloader.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/promise_list.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/compat.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/async_.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/iterate_promise.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> copying promise/utils.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise
> creating 
> /<>/.pybuild/cpython3_3.10_promise/build/promise/schedulers
> copying promise/schedulers/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise/schedulers
> copying promise/schedulers/asyncio.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise/schedulers
> copying promise/schedulers/immediate.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise/schedulers
> copying promise/schedulers/gevent.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise/schedulers
> copying promise/schedulers/thread.py -> 
> /<>/.pybuild/cpython3_3.10_promise/build/promise/schedulers
> creating /<>/.pybuild/cpython3_3.10_promise/build/promise/pyutils
>

Bug#958853: Fix

2022-12-21 Thread Dan O'Huiginn

Upstream has now moved away from Bazel: 
https://github.com/ankitects/anki/commit/5e0a761b875fff4c9e4b202c08bd740c7bb37763

The new build system uses cargo and ninja. It'll still be a substantial job to 
package this for Debian, but hopefully more feasible than before.

Processed: bug 1026809 is forwarded to https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/176

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

> forwarded 1026809 https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/176
Bug #1026809 [libx11-6] Xlib: sequence lost (0x1 > 0x...) in reply type 
0x... when running emacs
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/176'.
> thanks
Stopping processing here.

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

Processed: reopening 1026616

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

> reopen 1026616 =
Bug #1026616 {Done: Carsten Schoenert } 
[src:mkdocstrings-python-legacy] mkdocstrings-python-legacy: FTBFS: make: *** 
[debian/rules:15: binary] Error 25
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-promise/2.3.0-3.
> thanks
Stopping processing here.

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

Bug#1026573: marked as done (drgn: FTBFS: configure: error: Could not compile test program with Python headers.)

Your message dated Wed, 21 Dec 2022 17:49:42 +
with message-id 
and subject line Bug#1026573: fixed in drgn 0.0.21-2
has caused the Debian Bug report #1026573,
regarding drgn: FTBFS: configure: error: Could not compile test program with 
Python headers.
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.)


-- 
1026573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drgn
Version: 0.0.21-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):
> checking for GNU default /usr/bin/python3.11 prefix... ${prefix}
> checking for GNU default /usr/bin/python3.11 exec_prefix... ${exec_prefix}
> checking for /usr/bin/python3.11 script directory (pythondir)... 
> ${PYTHON_PREFIX}/lib/python3/dist-packages
> checking for /usr/bin/python3.11 extension module directory (pyexecdir)... 
> ${PYTHON_EXEC_PREFIX}/lib/python3/dist-packages
> checking for /usr/bin/python3.11 development headers... no
> configure: error: Could not compile test program with Python headers.
> 
> You may need to install your distribution's Python development package (e.g.,
> python3-devel or python3-dev) or specify the location of the Python 
> development
> headers by setting the PYTHON_CPPFLAGS environment variable.
> Traceback (most recent call last):
>   File "/<>/setup.py", line 433, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 185, in setup
> return run_commands(dist)
>^^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 201, in run_commands
> dist.run_commands()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 968, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 987, in run_command
> cmd_obj.run()
>   File 
> "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
> 132, in run
> self.run_command(cmd_name)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 319, in run_command
> self.distribution.run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 987, in run_command
> cmd_obj.run()
>   File "/<>/setup.py", line 99, in run
> self.make()
>   File "/<>/setup.py", line 95, in make
> self._run_configure()
>   File "/<>/setup.py", line 76, in _run_configure
> subprocess.check_call(
>   File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['../../libdrgn/configure', 
> '--disable-static', '--enable-python']' returned non-zero exit status 1.
> E: pybuild pybuild:386: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.11 setup.py build 
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_drgn/build/drgn
> copying drgn/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn
> copying drgn/__main__.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn
> creating /<>/.pybuild/cpython3_3.10_drgn/build/drgn/internal
> copying drgn/internal/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn/internal
> copying drgn/internal/cli.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn/internal
> copying drgn/internal/rlcompleter.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn/internal
> copying drgn/internal/version.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn/internal
> creating /<>/.pybuild/cpython3_3.10_drgn/build/drgn/helpers
> copying drgn/helpers/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn/helpers
> creating /<>/.pybuild/cpython3_3.10_drgn/build/drgn/helpers/linux
> copying drgn/helpers/linux/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_drgn/build/drgn/helpers/linux
> copying

Bug#1026630: marked as done (indi-gphoto: FTBFS: gphoto_ccd.h:101:14: error: ‘void GPhotoCCD::addFITSKeywords(fitsfile, INDI::CCDChip)’ marked ‘override’, but does not override)

Your message dated Wed, 21 Dec 2022 17:49:52 +
with message-id 
and subject line Bug#1026630: fixed in indi-gphoto 3.2+20221221172841-1
has caused the Debian Bug report #1026630,
regarding indi-gphoto: FTBFS: gphoto_ccd.h:101:14: error: ‘void 
GPhotoCCD::addFITSKeywords(fitsfile*, INDI::CCDChip*)’ marked ‘override’, but 
does not override
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.)


-- 
1026630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: indi-gphoto
Version: 3.0+20220611124727-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):
> /usr/bin/c++  -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/usr/include/libindi -I/usr/include/libraw -I/usr/include/libusb-1.0 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -D_FORTIFY_SOURCE=2 -fstack-protector-all -fPIE -O1 -Wa,--noexecstack  -Wall 
> -Wextra -Wno-unused-but-set-variable -Wno-format-truncation -g -fPIE 
> -std=gnu++14 -Wno-deprecated-declarations -MD -MT 
> CMakeFiles/indi_gphoto_ccd.dir/gphoto_readimage.cpp.o -MF 
> CMakeFiles/indi_gphoto_ccd.dir/gphoto_readimage.cpp.o.d -o 
> CMakeFiles/indi_gphoto_ccd.dir/gphoto_readimage.cpp.o -c 
> /<>/gphoto_readimage.cpp
> In file included from /<>/gphoto_ccd.cpp:23:
> /<>/gphoto_ccd.h:101:14: error: ‘void 
> GPhotoCCD::addFITSKeywords(fitsfile*, INDI::CCDChip*)’ marked ‘override’, but 
> does not override
>   101 | void addFITSKeywords(fitsfile * fptr, INDI::CCDChip * 
> targetChip) override;
>   |  ^~~
> /<>/gphoto_ccd.cpp: In member function ‘void 
> GPhotoCCD::addFITSKeywords(fitsfile*, INDI::CCDChip*)’:
> /<>/gphoto_ccd.cpp:2019:31: error: no matching function for call 
> to ‘GPhotoCCD::addFITSKeywords(fitsfile*&, INDI::CCDChip*&)’
>  2019 | INDI::CCD::addFITSKeywords(fptr, targetChip);
>   | ~~^~
> In file included from /<>/gphoto_ccd.h:27:
> /usr/include/libindi/indiccd.h:508:22: note: candidate: ‘virtual void 
> INDI::CCD::addFITSKeywords(INDI::CCDChip*)’
>   508 | virtual void addFITSKeywords(CCDChip * targetChip);
>   |  ^~~
> /usr/include/libindi/indiccd.h:508:22: note:   candidate expects 1 argument, 
> 2 provided
> make[3]: *** [CMakeFiles/indi_gphoto_ccd.dir/build.make:79: 
> CMakeFiles/indi_gphoto_ccd.dir/gphoto_ccd.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/indi-gphoto_3.0+20220611124727-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: indi-gphoto
Source-Version: 3.2+20221221172841-1
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
indi-gphoto, 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.
Thorsten Alteholz  (supplier of updated indi-gphoto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 17:29:56 +
Source: indi-gphoto
Architecture: source
Version: 3.2+20221221172841-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team

Bug#1026492: seqan2: FTBFS: TypeError: a bytes-like object is required, not 'str'

On Wed, 2022-12-21 at 19:39 +0530, Nilesh Patra wrote:
> On Wed, 21 Dec 2022 12:32:25 +0100 olivier sallou
>  wrote:
> > On Wed, 2022-12-21 at 11:02 +0100, olivier sallou wrote:
> > > looks like a python3 issue (though was already adapter to py3...)
> > > 
> > > will have a look and reproduce
> > 
> > I could reproduce and found an issue with demo_checker.py handling
> > with
> > python3
> > 
> > I have a patch. will test it and upload
> 
> I wrote a patch as well, and was going to upload, but you beat me to
> it, hah :/

sorry, I did not set me as bug owner but sent comments anyway so that
others are aware I was on issue

and this package is so long to build.

> My patch is quite similar to yours, though.
> 

I fixed py2 / py3 bytes error in 2 places and skipped mason2 tests as
described in patch and previous message

Just uploaded fixed package

Olivier

-- 

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#1026815: marked as done (ball: FTBFS: Package 'mpi-cxx', required by 'virtual:world', not found)

Your message dated Wed, 21 Dec 2022 16:04:25 +
with message-id 
and subject line Bug#1026815: fixed in ball 1.5.0+git20180813.37fc53c-11
has caused the Debian Bug report #1026815,
regarding ball: FTBFS: Package 'mpi-cxx', required by 'virtual:world', not found
to be marked as done.

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

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


-- 
1026815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.5.0+git20180813.37fc53c-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221221 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 '/<>'
> mkdir -p build
> cd build && LDFLAGS="-Wl,-z,relro -Wl,-z,now -ltirpc" CXXFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/tirpc" CFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" \
> cmake .. -DCMAKE_SOURCE_DIR=/<> 
> -DCMAKE_INSTALL_PREFIX=./usr \
>   -DBALL_PATH=/usr -DBALL_DATA_PATH=/usr/share/BALL-1.5/data \
>   -DCMAKE_VERBOSE_MAKEFILE=ON
> CMake Deprecation Warning at CMakeLists.txt:10 (CMAKE_POLICY):
>   The OLD behavior for policy CMP0042 will be removed from a future version
>   of CMake.
> 
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
> 
> 
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Compiler checks for conversion: OFF
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of char
> -- Check size of char - done
> -- Check size of short
> -- Check size of short - done
> -- Check size of int
> -- Check size of int - done
> -- Check size of long
> -- Check size of long - done
> -- Check size of size_t
> -- Check size of size_t - done
> -- Check size of void*
> -- Check size of void* - done
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Check size of unsigned int
> -- Check size of unsigned int - done
> -- Check size of unsigned long
> -- Check size of unsigned long - done
> -- Check size of unsigned long long
> -- Check size of unsigned long long - done
> -- Check size of float
> -- Check size of float - done
> -- Check size of double
> -- Check size of double - done
> -- Check size of uint64_t
> -- Check size of uint64_t - done
> -- Check size of uint32_t
> -- Check size of uint32_t - done
> -- Check size of uint16_t
> -- Check size of uint16_t - done
> -- Looking for C++ include unistd.h
> -- Looking for C++ include unistd.h - found
> -- Looking for C++ include process.h
> -- Looking for C++ include process.h - not found
> -- Looking for C++ include time.h
> -- Looking for C++ include time.h - found
> -- Looking for C++ include dirent.h
> -- Looking for C++ include dirent.h - found
> -- Looking for C++ include direct.h
> -- Looking for C++ include direct.h - not found
> -- Looking for C++ include pwd.h
> -- Looking for C++ include pwd.h - found
> -- Looking for C++ include stdint.h
> -- Looking for C++ include stdint.h - found
> -- Looking for C++ include sys/time.h
> -- Looking for C++ include sys/time.h - found
> -- Looking for C++ include sys/stat.h
> -- Looking for C++ include sys/stat.h - found
> -- Looking for

Bug#1026648: parole: FTBFS: make[1]: *** [debian/rules:22: override_dh_missing] Error 25

2022-12-21 Thread Yves-Alexis Perez

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2022-12-20 at 18:38 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > dh_missing --fail-missing -X .la
> > dh_missing: warning: usr/parole/pixmaps/no-cover.png exists in debian/tmp
> > but is not installed to anywhere 
> > dh_missing: warning: usr/parole/pixmaps/play.png exists in debian/tmp but
> > is not installed to anywhere 
> > dh_missing: warning: usr/parole/pixmaps/replay.png exists in debian/tmp
> > but is not installed to anywhere 
> > dh_missing: error: missing files, aborting
> > The following debhelper tools have reported what they installed
> > (with files per package)
> >  * dh_install: parole (5), parole-dev (1)
> >  * dh_installdocs: parole (0), parole-dev (0)
> >  * dh_installman: parole (1), parole-dev (0)
> > If the missing files are installed by another tool, please file a
> > bug against it.
> > When filing the report, if the tool is not part of debhelper
> > itself, please reference the
> > "Logging helpers and dh_missing" section from the "PROGRAMMING"
> > guide for debhelper (10.6.3+).
> >   (in the debhelper package:
> > /usr/share/doc/debhelper/PROGRAMMING.gz)
> > Be sure to test with dpkg-buildpackage -A/-B as the results may
> > vary when only a subset is built
> > If the omission is intentional or no other helper can take care of
> > this consider adding the
> > paths to debian/not-installed.
> > make[1]: *** [debian/rules:22: override_dh_missing] Error 25

Hi Lucas, thanks for the report. It seems that the pixmaps aren't installed to
the correct path, because pixmapsdir isn't defined to the correct place, in
turn because DATADIRNAME isn't defined anymore.

I'm unsure what changed in Debian since the initial upload in 2021, maybe some
autoconf macros or something.

It *seems* that DATADIRNAME might be obsolete (since a long time), it's not in
/usr/share/aclocal/gettext.m4 but I can see a lot of embedded copies with
https://codesearch.debian.net/search?q=DATADIRNAME (I looked at the gettext
changelog but couldn't find a reference).

It's likely an upstream issue but still I'm unsure where to point them.
Apparently there's datadir/datarootdir but as I'm not an autoconf expert I'm
not sure if it'd work in place.

Any pointer appreciated here.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmOjJl8ACgkQ3rYcyPpX
RFv/XwgA4Ly4KInLEQ2j60tBvndrsJ7B4RIRyJH8Lb1nxwdP/XAWq93o3p/6bgTR
SCdYYhret3y2M2jbZiJLY51/9EpOzKc2Ut8K2+mtm3sHpT+mMWLs3qbufOTE2MpL
VMPtWg0dMHT9/eOjXbrcKCrNFhJLm/oxsIgdSXzsNL/5z70ARCo7MYi97bt22KjW
uEFXrctxqDRdG6srwtj3cfYGufMAtYFWGwLcj+zvR730IZcjdscXrhbb4yHGKF/R
p9hrzKS6l/smBfRJyf9h1lSxH8Pw1AKV+qBO4n5sX7GJ6rdDHpsc3kuZlivvpgSM
UmL9nyEmuhOyrhdL1VgZr+9FfEE76w==
=kpYg
-END PGP SIGNATURE-

Bug#1026542: marked as done (gap-polycyclic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Wed, 21 Dec 2022 15:22:39 +
with message-id 
and subject line Bug#1026542: fixed in gap-polycyclic 2.16-2
has caused the Debian Bug report #1026542,
regarding gap-polycyclic: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
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.)


-- 
1026542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gap-polycyclic
Version: 2.16-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):
> dpkg-source: warning: ignoring deletion of file doc/chap6.html, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file doc/chap7.txt, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file doc/chap3.txt, use 
> --include-removal to override
> dpkg-source: info: building gap-polycyclic in 
> gap-polycyclic_2.16-1.debian.tar.xz
> dpkg-source: info: building gap-polycyclic in gap-polycyclic_2.16-1.dsc
>  debian/rules binary
> mkdir -p debian/gaproot/pkg
> ln -s ../../.. debian/gaproot/pkg/Polycyclic
> gap -q -l 'debian/gaproot;/usr/share/gap' < tst/testall.g | tee debian/gap.tst
> true
> Architecture: x86_64-pc-linux-gnu-default64-kv8
> 
> testing: debian/gaproot/pkg/Polycyclic/tst/AddToIgs.tst
>  154 ms (61 ms GC) and 14.7MB allocated for AddToIgs.tst
> testing: debian/gaproot/pkg/Polycyclic/tst/bugfix.tst
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/gap-polycyclic_2.16-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gap-polycyclic
Source-Version: 2.16-2
Done: Bill Allombert 

We believe that the bug you reported is fixed in the latest version of
gap-polycyclic, 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.
Bill Allombert  (supplier of updated gap-polycyclic 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 00:31:55 +0100
Source: gap-polycyclic
Architecture: source
Version: 2.16-2
Distribution: unstable
Urgency: medium
Maintainer: Bill Allombert 
Changed-By: Bill Allombert 
Closes: 1026542
Changes:
 gap-polycyclic (2.16-2) unstable; urgency=medium
 .
   * patch: disable-test: disable test that hangs with GAP 4.12.
 Closes: #1026542, see upstream issues
 
   * debian/control:
- Set Multi-Arch: foreign
- Bump Standards-Version to 4.6.1
Checksums-Sha1:
 ebec95245188b4503934da3ae4d1776836001437 1915 gap-polycyclic_2.16-2.dsc
 f697932b6756c161ff2eb1af4256d7b034007344 3844 
gap-polycyclic_2.16-2.debian.tar.xz
 da57701e32f3ff76c556437e92c71bf455a0fbd2 8602 
gap-polycyclic_2.16-2_source.buildinfo
Checksums-Sha256:
 81cbe246e5394b47bac55de97a2dcd23c841d5eef79dd8c163ba975910b0232a 1915 
gap-polycyclic_2.16-2.dsc
 66584dc223689d5cd33ea7194721897c7f432d7a399b933bf57f0e6d3a38410c 3844 
gap-polycyclic_2.16-2.debian.tar.xz
 55494e4a783fc5b087f9fee0ad1e392c81c377b7da5c5ae829371f01887c91d3 8602 
gap-polycyclic_2.16-2_source.buildinfo
Files:
 031b6921a428cd7e1956a3c9c43f5cca 1915 math optional

Processed: your mail

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

> tag 997224 patch
Bug #997224 [src:btag] btag: FTBFS: InteractiveTagger.cpp:201:34: error: ‘bool 
TagLib::String::isNull() const’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#1026742: marked as done (kineticstools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Wed, 21 Dec 2022 14:49:36 +
with message-id 
and subject line Bug#1026742: fixed in kineticstools 
0.6.1+git20220223.1326a4d+dfsg-2
has caused the Debian Bug report #1026742,
regarding kineticstools: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.11 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.)


-- 
1026742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kineticstools
Version: 0.6.1+git20220223.1326a4d+dfsg-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):
> make[1]: Entering directory '/<>'
> cp kineticsTools/ipdSummary.py bin/ipdSummary
> chmod +x bin/ipdSummary
> PYTHONPATH=/<> PATH=$PATH:/<>/bin dh_auto_test
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.11_kineticstools/build; python3.11 -m 
> pytest test
> = test session starts 
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack -- 
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> plugins: xdist-3.1.0
> gw0 I / gw1 I / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I
> 
> [gw0] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw1] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw2] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw3] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw4] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw5] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw6] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw7] linux Python 3.11.1 cwd: 
> /<>/.pybuild/cpython3_3.11_kineticstools/build
> 
> [gw0] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw3] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw2] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw1] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw4] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw5] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw6] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> 
> [gw7] Python 3.11.1 (main, Dec  7 2022, 08:49:13) [GCC 12.2.0]
> gw0 [11] / gw1 [11] / gw2 [11] / gw3 [11] / gw4 [11] / gw5 [11] / gw6 [11] / 
> gw7 [11]
> 
> scheduling tests via LoadScopeScheduling
> 
> test/test_outputs.py::TestOutputs::test_csv_output 
> [gw1] [  9%] SKIPPED test/test_outputs.py::TestOutputs::test_csv_output 
> test/test_integration.py::TestKineticsTools::test_help 
> test/test_summarize_modifications.py::TestSummarizeModifications::test_integration
>  
> [gw4] [ 18%] SKIPPED 
> test/test_summarize_modifications.py::TestSummarizeModifications::test_integration
>  
> test/test_outputs.py::TestOutputs::test_bigwig 
> [gw1] [ 27%] SKIPPED test/test_outputs.py::TestOutputs::test_bigwig 
> test/test_loader.py::test_basic 
> [gw2] [ 36%] PASSED test/test_loader.py::test_basic 
> test/test_loader.py::test_path 
> [gw2] [ 45%] PASSED test/test_loader.py::test_path 
> test/test_loader.py::test_path_with_prefixed_chem 
> [gw2] [ 54%] PASSED test/test_loader.py::test_path_with_prefixed_chem 
> test/test_loader.py::test_getResourcePathSpec 
> test/test_gather_bigwig.py::TestGatherBigwig::test_gather_bigwig 
> [gw0] [ 63%] SKIPPED 
> test/test_gather_bigwig.py::TestGatherBigwig::test_gather_bigwig 
> test/test_gather_bigwig.py::TestGatherBigwig::test_gather_bigwig_cli 
> [gw0] [ 72%] SKIPPED 
> test/test_gather_bigwig.py::TestGatherBigwig::test_gather_bigwig_cli 
> [gw2] [ 81%] PASSED test/test_loader.py::test_getResourcePathSpec 
> [gw3] [ 90%] PASSED test/test_integration.py::TestKineticsTools::test_help 
> test/test_integration.py::TestKineticsTools::test_ecoli_first_50k 
> [gw3] [100%] SKIPPED 
> test/test_integration.py::TestKineticsTools::test_ecoli_first_50k 
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.11_kineticstools/build/test/test_ReferenceUtils.py _
> ImportError while importing test module 
>

Bug#997224: btag: FTBFS: InteractiveTagger.cpp:201:34: error: ‘bool TagLib::String::isNull() const’ is deprecated [-Werror=deprecated-declarations]

2022-12-21 Thread Eric Long


tag -1 patch thanks

Also, it seemed that zlib is missing from building dependencies in my 
sbuild chroot:


```
[ 46%] Linking CXX executable btag
/usr/bin/cmake -E cmake_link_script CMakeFiles/btag.dir/link.txt 
--verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Werror -Wl,-z,relro -Wl,-z,now -rdynamic 
CMakeFiles/btag.dir/src/BasicStringFilter.cpp.o 
CMakeFiles/btag.dir/src/ConfirmationHandler.cpp.o 
CMakeFiles/btag.dir/src/EnglishTitleLocalizationHandler.cpp.o 
CMakeFiles/btag.dir/src/InteractiveTagger.cpp.o 
CMakeFiles/btag.dir/src/main.cpp.o 
CMakeFiles/btag.dir/src/RenamingFilter.cpp.o 
CMakeFiles/btag.dir/src/SimpleCapitalizationFilter.cpp.o 
CMakeFiles/btag.dir/src/SpanishTitleLocalizationHandler.cpp.o 
CMakeFiles/btag.dir/src/StandardConsole.cpp.o 
CMakeFiles/btag.dir/src/TitleCapitalizationFilter.cpp.o 
CMakeFiles/btag.dir/src/TitleLocalizationHandler.cpp.o -o btag 
/usr/lib/riscv64-linux-gnu/libboost_filesystem.so.1.74.0 
/usr/lib/riscv64-linux-gnu/libboost_system.so.1.74.0 -ltag -lz

/usr/bin/ld: cannot find -lz: No such file or directory
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/btag.dir/build.make:262: btag] Error 1
```

By adding `zlib1g-dev` to Build-Depends in d/control, this is fixed.

Cheers,
Eric

Bug#997224: btag: FTBFS: InteractiveTagger.cpp:201:34: error: ‘bool TagLib::String::isNull() const’ is deprecated [-Werror=deprecated-declarations]

2022-12-21 Thread Eric Long

Source: btag
Version: 1.1.3-1
Followup-For: Bug #997224
X-Debbugs-Cc: i...@hack3r.moe

tag -1 patch thanks

Hello,

Attached is a patch that replaces deprecated methods and variables according to
TagLib official docs [1]. It fixes FTBFS and it should work well too.

If more help is needed, please let me know.

Cheers,
Eric

[1]: https://taglib.org/api/classTagLib_1_1String.html
--- a/src/InteractiveTagger.cpp
+++ b/src/InteractiveTagger.cpp
@@ -198,7 +198,7 @@
 
 // Ask for the artist
 artist_confirmation.reset();
-if (!f.tag()->artist().isNull())
+if (!f.tag()->artist().isEmpty())
 
artist_confirmation.set_local_default(m_input_filter->filter(f.tag()->artist().toWString()));
 artist_confirmation.ask(L"Artist:");
 while (!artist_confirmation.complies())
@@ -207,7 +207,7 @@
 
 // Ask for the album
 album_confirmation.reset();
-if (!f.tag()->album().isNull())
+if (!f.tag()->album().isEmpty())
 
album_confirmation.set_local_default(m_input_filter->filter(f.tag()->album().toWString()));
 album_confirmation.ask(L"Album:");
 while (!album_confirmation.complies())
@@ -236,7 +236,7 @@
 // Ask for the song title
 ConfirmationHandler title_confirmation(*m_terminal, m_input_filter, 
m_output_filter);
 title_confirmation.reset();
-if (!f.tag()->title().isNull())
+if (!f.tag()->title().isEmpty())
 
title_confirmation.set_local_default(m_input_filter->filter(f.tag()->title().toWString()));
 title_confirmation.ask(L"Title:");
 while (!title_confirmation.complies())
@@ -244,8 +244,8 @@
 f.tag()->setTitle(title_confirmation.answer());
 
 // Reset the comment and genre fields
-f.tag()->setComment(TagLib::String::null);
-f.tag()->setGenre(TagLib::String::null);
+f.tag()->setComment(TagLib::String());
+f.tag()->setGenre(TagLib::String());
 
 // Add it to the list of unsaved files
 m_unsaved_files.push_back(f);

Bug#1026492: seqan2: FTBFS: TypeError: a bytes-like object is required, not 'str'

upstream, in develop branch has disabled mason2 testing for gcc > 10 ,
don't know why, but let's do the same as it is the one failing now with
indeed superior gcc

I am adapting the patch and testing again.



gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#1026817: lomiri-indicator-network: FTBFS: Critical: getprop process failed: "execvp: No such file or directory" ((null):0, (null))

Source: lomiri-indicator-network
Version: 1.0.0~git20220718.2ca3619-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221221 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> [--] Global test environment tear-down
> [==] 66 tests from 6 test suites ran. (3020373 ms total)
> [  PASSED  ] 36 tests.
> [  FAILED  ] 30 tests, listed below:
> [  FAILED  ] TestIndicator.BasicMenuContents
> [  FAILED  ] TestIndicator.OneDisconnectedAccessPointAtStartup
> [  FAILED  ] TestIndicator.OneConnectedAccessPointAtStartup
> [  FAILED  ] TestIndicator.AddOneDisconnectedAccessPointAfterStartup
> [  FAILED  ] TestIndicator.AddOneConnectedAccessPointAfterStartup
> [  FAILED  ] TestIndicator.SecondModem
> [  FAILED  ] TestIndicator.SimStates_NoSIM
> [  FAILED  ] TestIndicator.SimStates_NoSIM2
> [  FAILED  ] TestIndicator.SimStates_LockedSIM
> [  FAILED  ] TestIndicator.SimStates_LockedSIM2
> [  FAILED  ] TestIndicator.SimStates_UnlockedSIM
> [  FAILED  ] TestIndicator.SimStates_UnlockedSIM2
> [  FAILED  ] TestIndicator.FlightMode_NoSIM
> [  FAILED  ] TestIndicator.FlightMode_LockedSIM
> [  FAILED  ] TestIndicator.FlightMode_WifiOff
> [  FAILED  ] TestIndicator.FlightMode_WifiOn
> [  FAILED  ] TestIndicator.GroupedWiFiAccessPoints
> [  FAILED  ] TestIndicator.WifiStates_SSIDs
> [  FAILED  ] TestIndicator.WifiStates_Connect1AP
> [  FAILED  ] TestIndicator.WifiStates_Connect2APs
> [  FAILED  ] TestIndicator.WifiStates_AddAndActivate
> [  FAILED  ] TestIndicator.EnterpriseWifiConnect
> [  FAILED  ] TestIndicator.CellDataEnabled
> [  FAILED  ] TestIndicator.CellDataDisabled
> [  FAILED  ] TestIndicator.UnlockSIM_MenuContents
> [  FAILED  ] TestIndicator.UnlockSIM_Cancel
> [  FAILED  ] TestIndicator.UnlockSIM_CancelFirstUnlockSecond
> [  FAILED  ] TestIndicator.UnlockSIM_CorrectPin
> [  FAILED  ] TestIndicator.UnlockSIM_IncorrectPin
> [  FAILED  ] TestIndicator.UnlockSIM2_IncorrectPin
> 
> 30 FAILED TESTS
> 
> 
> 50% tests passed, 1 tests failed out of 2
> 
> Total Test time (real) = 3020.58 sec
> 
> The following tests FAILED:
> 1 - integration-tests (Failed)
> Errors while running CTest
> make[1]: *** [Makefile:74: test] Error 8
> make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test 
> ARGS\+=--verbose ARGS\+=-j8 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/12/21/lomiri-indicator-network_1.0.0~git20220718.2ca3619-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221221;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221221=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1026815: ball: FTBFS: Package 'mpi-cxx', required by 'virtual:world', not found

Source: ball
Version: 1.5.0+git20180813.37fc53c-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221221 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 '/<>'
> mkdir -p build
> cd build && LDFLAGS="-Wl,-z,relro -Wl,-z,now -ltirpc" CXXFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I/usr/include/tirpc" CFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" \
> cmake .. -DCMAKE_SOURCE_DIR=/<> 
> -DCMAKE_INSTALL_PREFIX=./usr \
>   -DBALL_PATH=/usr -DBALL_DATA_PATH=/usr/share/BALL-1.5/data \
>   -DCMAKE_VERBOSE_MAKEFILE=ON
> CMake Deprecation Warning at CMakeLists.txt:10 (CMAKE_POLICY):
>   The OLD behavior for policy CMP0042 will be removed from a future version
>   of CMake.
> 
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
> 
> 
> -- The C compiler identification is GNU 12.2.0
> -- The CXX compiler identification is GNU 12.2.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Compiler checks for conversion: OFF
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of char
> -- Check size of char - done
> -- Check size of short
> -- Check size of short - done
> -- Check size of int
> -- Check size of int - done
> -- Check size of long
> -- Check size of long - done
> -- Check size of size_t
> -- Check size of size_t - done
> -- Check size of void*
> -- Check size of void* - done
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Check size of unsigned int
> -- Check size of unsigned int - done
> -- Check size of unsigned long
> -- Check size of unsigned long - done
> -- Check size of unsigned long long
> -- Check size of unsigned long long - done
> -- Check size of float
> -- Check size of float - done
> -- Check size of double
> -- Check size of double - done
> -- Check size of uint64_t
> -- Check size of uint64_t - done
> -- Check size of uint32_t
> -- Check size of uint32_t - done
> -- Check size of uint16_t
> -- Check size of uint16_t - done
> -- Looking for C++ include unistd.h
> -- Looking for C++ include unistd.h - found
> -- Looking for C++ include process.h
> -- Looking for C++ include process.h - not found
> -- Looking for C++ include time.h
> -- Looking for C++ include time.h - found
> -- Looking for C++ include dirent.h
> -- Looking for C++ include dirent.h - found
> -- Looking for C++ include direct.h
> -- Looking for C++ include direct.h - not found
> -- Looking for C++ include pwd.h
> -- Looking for C++ include pwd.h - found
> -- Looking for C++ include stdint.h
> -- Looking for C++ include stdint.h - found
> -- Looking for C++ include sys/time.h
> -- Looking for C++ include sys/time.h - found
> -- Looking for C++ include sys/stat.h
> -- Looking for C++ include sys/stat.h - found
> -- Looking for C++ include sys/times.h
> -- Looking for C++ include sys/times.h - found
> -- Looking for C++ include sys/types.h
> -- Looking for C++ include sys/types.h - found
> -- Looking for C++ include sys/param.h
> -- Looking for C++ include sys/param.h - found
> -- Looking for C++ include sys/sysinfo.h
> -- Looking for C++ include sys/sysinfo.h - found
> -- Performing Test BALL_HAS_MODE_T
> -- Performing Test BALL_HAS_MODE_T - Success
> -- Looking for C++ include ieeefp.h
> -- Looking for C++ include ieeefp.h - not found
> -- Looking for kill
> -- Looking for kill - found
> -- Looking for sysconf
> -- Looking for sysconf - found
> -- Performing Test BALL_ALLOW_LONG64_TYPE_OVERLOADS
> -- Performing Test BALL_ALLOW_LONG64_TYPE_OVERLOADS - Failed
> -- Performing Test BALL

Bug#1026816: speedcrunch: FTBFS: KeyError: 'extra-doc-strings'

Source: speedcrunch
Version: 0.12.0-5.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221221 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/build-docs'
> [100%] Generating manual.qrc
> Running Sphinx v5.3.0
> WARNING: Invalid configuration value found: 'language = None'. Update your 
> configuration to a valid language code. Falling back to 'en' (English).
> loading translations [en_US]... not available for built-in messages
> 
> Exception occurred:
>   File "/<>/doc/src/extensions/translations.py", line 29, in _
> return locale.translators[_CATALOG].gettext(message)
> KeyError: 'extra-doc-strings'
> The full traceback has been saved in /tmp/sphinx-err-avr0b5ds.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> Building docs for en_US...
> Traceback (most recent call last):
>   File "/<>/doc/src/doc-tool.py", line 208, in 
> main(sys.argv)
>   File "/<>/doc/src/doc-tool.py", line 202, in main
> args.func(tools, args)
>   File "/<>/doc/src/doc-tool.py", line 135, in build_bundled_docs
> build_docs(tools, args.source_dir, args.build_dir, lang,
>   File "/<>/doc/src/doc-tool.py", line 77, in build_docs
> return tools.sphinx_build(*args)
>   File "/<>/doc/src/doc-tool.py", line 52, in 
> return lambda *args: self.run_tool(name, *args)
>   File "/<>/doc/src/doc-tool.py", line 49, in run_tool
> return subprocess.check_call(cmd)
>   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/sphinx-build', 
> '/<>/doc/src', '/<>/build-docs/en_US', '-b', 
> 'qthelp2', '-D', 'qthelp_basename=manual-en_US', '-D', 'language=en_US', 
> '-t', 'sc_bundled_docs']' returned non-zero exit status 2.
> make[4]: *** [CMakeFiles/manual.dir/build.make:102: manual.qrc] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/21/speedcrunch_0.12.0-5.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221221;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221221=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1026814: kreport: FTBFS: dh_install: error: missing files, aborting

Source: kreport
Version: 3.2.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221221 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 '/<>/obj-x86_64-linux-gnu'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/KReport3.pc
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/af/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/be/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/br/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cy/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/kreport_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/kreport_webplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/kreport_barcodeplugin_qt.qm
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/kreport_mapsplugin_qt.qm
> -- Installing: 
> /<>/d

Bug#1026492: seqan2: FTBFS: TypeError: a bytes-like object is required, not 'str'

On Wed, 21 Dec 2022 12:32:25 +0100 olivier sallou  
wrote:
> On Wed, 2022-12-21 at 11:02 +0100, olivier sallou wrote:
> > looks like a python3 issue (though was already adapter to py3...)
> > 
> > will have a look and reproduce
> 
> I could reproduce and found an issue with demo_checker.py handling with
> python3
> 
> I have a patch. will test it and upload

I wrote a patch as well, and was going to upload, but you beat me to
it, hah :/
My patch is quite similar to yours, though.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1026492: seqan2: FTBFS: TypeError: a bytes-like object is required, not 'str'

I pushed a patch d/patches/fix_python3_tests whic fixes almost all test 
issues(python3 related)

BUT remains a failing test with mason2 which is not related to py3
issue (no bytes-like error)




after build, can be reproduced with

in a temp dir:

python3 /<>/apps/mason2/tests/run_tests.py
/opt/debian/build-area/seqan2-2.4.0+dfsg /<>/obj-x86_64-
linux-gnu/ 


it basically compare some generated files with some comparison files
and for mason2 they are different, and program itself raise no error
but result not as expected. Seems that many sequences output result are
shifted by 1 character




-- 


gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#1026752: marked as done (php-twig: FTBFS: make[1]: *** [debian/rules:92: override_dh_auto_test] Error 1)

Your message dated Wed, 21 Dec 2022 13:20:47 +
with message-id 
and subject line Bug#1026752: fixed in php-twig 3.4.3-2
has caused the Debian Bug report #1026752,
regarding php-twig: FTBFS: make[1]: *** [debian/rules:92: 
override_dh_auto_test] Error 1
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.)


-- 
1026752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-twig
Version: 3.4.3-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):
> make[1]: Entering directory '/<>'
> SYMFONY_DEPRECATIONS_HELPER=weak phpunit
> PHPUnit 9.5.27 by Sebastian Bergmann and contributors.
> 
> Testing 
> .   61 / 1659 (  
> 3%)
> .  122 / 1659 (  
> 7%)
> .  183 / 1659 ( 
> 11%)
> .  244 / 1659 ( 
> 14%)
> .  305 / 1659 ( 
> 18%)
> .  366 / 1659 ( 
> 22%)
> S  427 / 1659 ( 
> 25%)
> .  488 / 1659 ( 
> 29%)
> .  549 / 1659 ( 
> 33%)
> ..S..  610 / 1659 ( 
> 36%)
> .  671 / 1659 ( 
> 40%)
> .  732 / 1659 ( 
> 44%)
> ..S..  793 / 1659 ( 
> 47%)
> .  854 / 1659 ( 
> 51%)
> .  915 / 1659 ( 
> 55%)
> .  976 / 1659 ( 
> 58%)
> . 1037 / 1659 ( 
> 62%)
> . 1098 / 1659 ( 
> 66%)
> . 1159 / 1659 ( 
> 69%)
> . 1220 / 1659 ( 
> 73%)
> . 1281 / 1659 ( 
> 77%)
> . 1342 / 1659 ( 
> 80%)
> . 1403 / 1659 ( 
> 84%)
> . 1464 / 1659 ( 
> 88%)
> . 1525 / 1659 ( 
> 91%)
> . 1586 / 1659 ( 
> 95%)
> . 1647 / 1659 ( 
> 99%)
>   1659 / 1659 
> (100%)
> 
> Time: 00:01.345, Memory: 38.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 1659, Assertions: 4395, Skipped: 3.
> 
> Legacy deprecation notices (3)
> # testsuite for extra packages
> set -e; \
>  for package_info_file in $(find debian/packages_to_build/ -mindepth 1 
> -maxdepth 1 -type f); do \
>   . $package_info_file; \
>   if [ -f $src_path/phpunit.xml.dist ]; then \
>LC_ALL=en_US SYMFONY_DEPRECATIONS_HELPER=weak phpunit \
>--bootstrap vendor/autoload.php \
>--configuration $src_path/phpunit.xml.dist \
>$src_path; \
>   fi; \
>  done
> PHPUnit 9.5.27 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ..S 3 / 3 
> (100%)
> 
> Time: 00:00.036, Memory: 8.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 3, Assertions: 4, Skipped: 1.
> PHPUnit 9.5.27 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ...S8 / 8

Bug#1026571: jnlp-servlet: FTBFS: src/classes/jnlp/sample/servlet/JnlpResource.java:47: error: cannot find symbol

Fwiw, java.util.jar.Pack200 was removed in JDK 14 and is thus missing 
when building with JDK 17.


https://openjdk.org/jeps/367

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#1026809: Xlib: sequence lost (0x10000 > 0x...) in reply type 0x... when running emacs

2022-12-21 Thread Vincent Lefevre

On 2022-12-21 14:01:53 +0100, Vincent Lefevre wrote:
> Not sure about the bug severity, but if such errors are output,
> this means that they are really serious. Otherwise, the end user
> shouldn't be bothered. In any case, this must be fixed before
> the next Debian release.

I confirm that this is really serious: it can make emacs exit with
a nonzero exit status (exit status 1).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1026608: jcommander: FTBFS: JCommander.java:45: error: malformed HTML


tags 1026608 patch
thanks

See the attached patch which resolves the HTML errors to generate the 
JavaDoc and make the package build successfully.


--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgDescription: Fix HTML errors in Javadoc causing build failures

Remove  tags, not part of HTML5
Replace <> wrapping author emails
Drop <> around generic T which is mistaken for HTML tag

Resolved based on how it was solved upstream:
https://github.com/cbeust/jcommander/commit/c31f983ae8f56a5b06f502009dfb32baa2be96f1
https://github.com/cbeust/jcommander/commit/7b46f253f625c91b47ef7e0780c01ffd357f4cd2

---

Origin: upstream, 
Forwarded: not-needed
Last-Update: 2022-12-21

--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/Parameter.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/Parameter.java
@@ -69,15 +69,15 @@ public @interface Parameter {
   boolean password() default false;
 
   /**
-   * The string converter to use for this field. If the field is of type List
-   * and not listConverter attribute was specified, JCommander will split
+   * The string converter to use for this field. If the field is of type List
+   * and not listConverter attribute was specified, JCommander will split
* the input in individual values and convert each of them separately.
*/
   Class> converter() default NoConverter.class;
 
   /**
* The list string converter to use for this field. If it's specified, the
-   * field has to be of type List and the converter needs to return
+   * field has to be of type List and the converter needs to return
* a List that's compatible with that type.
*/
   Class> listConverter() default NoConverter.class;
@@ -103,7 +103,7 @@ public @interface Parameter {
   boolean variableArity() default false;
 
   /**
-   * What splitter to use (applicable only on fields of type List). By default,
+   * What splitter to use (applicable only on fields of type List). By default,
* a comma separated splitter will be used.
*/
   Class splitter() default CommaParameterSplitter.class;

--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/IParameterValidator.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/IParameterValidator.java
@@ -21,7 +21,7 @@ package com.beust.jcommander;
 /**
  * The class used to validate parameters.
  *
- * @author Cedric Beust 
+ * @author Cedric Beust ced...@beust.com
  */
 public interface IParameterValidator {
 
--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/IStringConverter.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/IStringConverter.java
@@ -33,7 +33,7 @@ package com.beust.jcommander;
  */
 public interface IStringConverter {
   /**
-   * @return an object of type  created from the parameter value.
+   * @return an object of type T created from the parameter value.
*/
   T convert(String value);
 }
--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/JCommander.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/JCommander.java
@@ -42,7 +42,7 @@ import java.util.concurrent.CopyOnWriteA
  * or an instance of Iterable. In the case of an array or Iterable, JCommander will collect
  * the \@Parameter annotations from all the objects passed in parameter.
  *
- * @author Cedric Beust 
+ * @author Cedric Beust ced...@beust.com
  */
 public class JCommander {
 public static final String DEBUG_PROPERTY = "jcommander.debug";
--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/MissingCommandException.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/MissingCommandException.java
@@ -21,7 +21,7 @@ package com.beust.jcommander;
 /**
  * Thrown when a command was expected.
  *
- * @author Cedric Beust 
+ * @author Cedric Beust ced...@beust.com
  */
 @SuppressWarnings("serial")
 public class MissingCommandException extends ParameterException {
--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/ParameterException.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/ParameterException.java
@@ -22,7 +22,7 @@ package com.beust.jcommander;
  * The main exception that JCommand will throw when something goes wrong while
  * parsing parameters.
  *
- * @author Cedric Beust 
+ * @author Cedric Beust ced...@beust.com
  */
 @SuppressWarnings("serial")
 public class ParameterException extends RuntimeException {
--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/ResourceBundle.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/ResourceBundle.java
@@ -26,7 +26,7 @@ import java.lang.annotation.Target;
 /**
  * @deprecated use @Parameters
  * 
- * @author Cedric Beust 
+ * @author Cedric Beust ced...@beust.com
  */
 @Retention(java.lang.annotation.RetentionPolicy.RUNTIME)
 @Target({ TYPE })
--- jcommander-1.71.orig/src/main/java/com/beust/jcommander/SubParameter.java
+++ jcommander-1.71/src/main/java/com/beust/jcommander/SubParameter.java
@@ -7,7 +7,7 @@ import static java.lang.annotation.Eleme
 import static

Bug#1026809: Xlib: sequence lost (0x10000 > 0x...) in reply type 0x... when running emacs

2022-12-21 Thread Vincent Lefevre

Package: libx11-6
Version: 2:1.8.3-2
Severity: grave
Justification: renders package unusable

or possible data loss?

After the upgrade to libx11-6 2:1.8.3-2, I get the following errors
when running emacs:

e.g.

Xlib: sequence lost (0x1 > 0x473) in reply type 0x21!
Xlib: sequence lost (0x1 > 0x58e) in reply type 0xf!
Xlib: sequence lost (0x1 > 0x9bb) in reply type 0xf!
Xlib: sequence lost (0x1 > 0xfb4) in reply type 0xc!
Xlib: sequence lost (0x1 > 0xfbe) in reply type 0xf!

or

Xlib: sequence lost (0x1 > 0x450) in reply type 0x1c!
Xlib: sequence lost (0x1 > 0x45b) in reply type 0x13!
Xlib: sequence lost (0x1 > 0x473) in reply type 0x21!
Xlib: sequence lost (0x1 > 0x567) in reply type 0xf!
Xlib: sequence lost (0x1 > 0xa0d) in reply type 0xf!
Xlib: sequence lost (0x1 > 0xfb7) in reply type 0xc!
Xlib: sequence lost (0x1 > 0xfc1) in reply type 0xf!

etc.

This changes each time.

Not sure about the bug severity, but if such errors are output,
this means that they are really serious. Otherwise, the end user
shouldn't be bothered. In any case, this must be fixed before
the next Debian release.

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

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

Versions of packages libx11-6 depends on:
ii  libc62.36-6
ii  libx11-data  2:1.8.3-2
ii  libxcb1  1.15-1

libx11-6 recommends no packages.

libx11-6 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: limit source to php-twig, tagging 1026752

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

> limit source php-twig
Limiting to bugs with field 'source' containing at least one of 'php-twig'
Limit currently set to 'source':'php-twig'

> tags 1026752 + pending
Bug #1026752 [src:php-twig] php-twig: FTBFS: make[1]: *** [debian/rules:92: 
override_dh_auto_test] Error 1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1019288: sed: copyright file lacks several distribution licenses


I am uploading a NMU to DELAYED/10 to fix this. For your convenience, I have 
included your git changes as well.
The debdiff is attached and also available in git.diff -Nru sed-4.8/debian/changelog sed-4.8/debian/changelog
--- sed-4.8/debian/changelog2021-08-31 14:55:13.0 +0200
+++ sed-4.8/debian/changelog2022-12-21 13:44:30.0 +0100
@@ -1,3 +1,15 @@
+sed (4.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/copyright: Complete and convert to format 1.0. closes: #1019288.
+
+  [ Clint Adams ]
+  * Switch debhelper compat level to 13.
+  * Bump Standards-Version to 4.6.0.
+  * Set Rules-Requires-Root to no.
+
+ -- Bastian Germann   Wed, 21 Dec 2022 13:44:30 +0100
+
 sed (4.8-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru sed-4.8/debian/compat sed-4.8/debian/compat
--- sed-4.8/debian/compat   2021-08-31 14:55:13.0 +0200
+++ sed-4.8/debian/compat   1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-10
diff -Nru sed-4.8/debian/control sed-4.8/debian/control
--- sed-4.8/debian/control  2021-08-31 14:55:13.0 +0200
+++ sed-4.8/debian/control  2022-12-21 13:44:30.0 +0100
@@ -2,8 +2,9 @@
 Section: utils
 Priority: required
 Maintainer: Clint Adams 
-Standards-Version: 4.2.1
-Build-Depends: texinfo, gettext, libselinux-dev [linux-any], debhelper (>= 
10), help2man, libacl1-dev
+Standards-Version: 4.6.0
+Build-Depends: texinfo, gettext, libselinux-dev [linux-any], debhelper-compat 
(= 13), help2man, libacl1-dev
+Rules-Requires-Root: no
 Vcs-Git: https://salsa.debian.org/debian/sed.git
 Vcs-Browser: https://salsa.debian.org/debian/sed
 Homepage: https://www.gnu.org/software/sed/
@@ -19,4 +20,3 @@
  files are specified, makes editing changes according to a
  list of commands, and writes the results to the standard
  output.
-
diff -Nru sed-4.8/debian/copyright sed-4.8/debian/copyright
--- sed-4.8/debian/copyright2021-08-31 14:55:13.0 +0200
+++ sed-4.8/debian/copyright2022-12-21 13:37:08.0 +0100
@@ -1,21 +1,174 @@
-This is the Debian GNU/Linux prepackaged version of sed - the GNU stream
-oriented editor.
-
-This package was assembled from sources obtained from:
-   ftp://ftp.gnu.org/gnu/sed/
-
-It is currently maintained by Clint Adams 
-
-Copyright: 1989,90,91,92,93,94,95,98,99,2002,2003,2006,2008,2009,2010 Free 
Software Foundation, Inc.
-
-GNU sed is free software; you can redistribute it and/or modify it under
-the terms of the GNU General Public License as published by the Free
-Software Foundation; either version 3, or (at your option) any later
-version.
-
-On Debian GNU/Linux systems you can find a copy of the GPL in
-/usr/share/common-licenses/GPL-3
-
-The sed info manual is released under the terms of the GNU Free
-Documentation License as published by the Free Software Foundation;
-either version 1.3, or (at your option) any later version.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: GNU sed
+Source: ftp://ftp.gnu.org/gnu/sed/
+Comment: This is the Debian GNU/Linux prepackaged version of sed.
+ It is currently maintained by Clint Adams .
+
+Files: *
+   doc/local.mk
+Copyright: 1989-2020 Free Software Foundation, Inc.
+License: GPL-3+
+
+License: GPL-3+
+ GNU sed is free software; you can redistribute it and/or modify it under
+ the terms of the GNU General Public License as published by the Free
+ Software Foundation; either version 3, or (at your option) any later
+ version.
+ .
+ On Debian GNU/Linux systems you can find a copy of the GPL in
+ /usr/share/common-licenses/GPL-3
+
+Files: build-aux/install-sh
+Copyright: 1994 X Consortium
+License: X11
+ Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"), to
+ deal in the Software without restriction, including without limitation the
+ rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+ sell copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:
+ .
+ The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+ X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
+ AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
+ TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+ .
+ Except as contained in this notice, the name of the X Consortium shall not
+ be used in advertising or otherwise to promote the sale, use or other deal-
+ ings in this Software without prior written authorization from the X Consor-
+ tium.
+Comment: FSF

Bug#1026572: marked as done (itcl3: FTBFS: ./generic/itcl_methods.c:1159:48: error: invalid application of ‘sizeof’ to incomplete type ‘char[]’)

Your message dated Wed, 21 Dec 2022 12:49:28 +
with message-id 
and subject line Bug#1026572: fixed in itcl3 3.4.4-1
has caused the Debian Bug report #1026572,
regarding itcl3: FTBFS: ./generic/itcl_methods.c:1159:48: error: invalid 
application of ‘sizeof’ to incomplete type ‘char[]’
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.)


-- 
1026572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: itcl3
Version: 3.4.3-3.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):
> gcc -DPACKAGE_NAME=\"itcl\" -DPACKAGE_TARNAME=\"itcl\" 
> -DPACKAGE_VERSION=\"3.4\" -DPACKAGE_STRING=\"itcl\ 3.4\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DBUILD_itcl=/\*\*/ 
> -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 
> -DTCL_THREADS=1 -DMODULE_SCOPE=extern\ 
> __attribute__\(\(__visibility__\(\"hidden\"\)\)\) -DHAVE_HIDDEN=1 
> -DHAVE_CAST_TO_UNION=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 
> -DUSE_TCL_STUBS=1  -DITCL_LIBRARY=\"/usr/lib/x86_64-linux-gnu/itcl3.4\" 
> -I"./generic" -I"/usr/include/tcl8.6/tcl-private/generic" 
> -I"/usr/include/tcl8.6/tcl-private/unix"-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -pipe -O2 -fomit-frame-pointer -DNDEBUG -Wall -fPIC 
> -Wdate-time -D_FORTIFY_SOURCE=2 -c `echo ./generic/itcl_methods.c` -o 
> itcl_methods.o
> In file included from /usr/include/tcl8.6/tcl-private/generic/tclPort.h:25,
>  from /usr/include/tcl8.6/tcl-private/generic/tclInt.h:36,
>  from ./generic/itclInt.h:50,
>  from ./generic/itcl_methods.c:31:
> ./generic/itcl_methods.c: In function ‘Itcl_CreateArg’:
> ./generic/itcl_methods.c:1159:48: error: invalid application of ‘sizeof’ to 
> incomplete type ‘char[]’
>  1159 | (unsigned)(sizeof(CompiledLocal)-sizeof(localPtr->name) + 
> nameLen+1)
>   |^
> /usr/include/tcl8.6/tcl-private/generic/tcl.h:2462:36: note: in definition of 
> macro ‘ckalloc’
>  2462 | ((void *) Tcl_Alloc((unsigned)(x)))
>   |^
> make[2]: *** [Makefile:266: itcl_methods.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/itcl3_3.4.3-3.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

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

We believe that the bug you reported is fixed in the latest version of
itcl3, 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.
Sergei Golovan  (supplier of updated itcl3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Dec 2022 15:06:24 +0300
Source: itcl3
Architecture: source
Version: 3.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Tcl/Tk Packagers 
Changed-By: Sergei Golovan 
Closes: 1026572
Changes:
 itcl3 (3.4.4-1) unstable; urgency=medium
 .
   * New upstream release (closes: #1026572).
   *

Processed: Re: jcommander: FTBFS: JCommander.java:45: error: malformed HTML

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

> tags 1026608 patch
Bug #1026608 [src:jcommander] jcommander: FTBFS: JCommander.java:45: error: 
malformed HTML
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1019289: NMU: less: copyright file lacks several distribution licenses


I am uploading a NMU with the enclosed debdiff to DELAYED/10.diff -Nru less-590/debian/changelog less-590/debian/changelog
--- less-590/debian/changelog   2021-12-30 07:54:19.0 +0100
+++ less-590/debian/changelog   2022-12-21 13:27:37.0 +0100
@@ -1,3 +1,10 @@
+less (590-1.1) sid; urgency=medium
+
+  * Non-maintainer upload
+  * d/copyright: Convert to machine-readable format (closes: #1019289)
+
+ -- Bastian Germann   Wed, 21 Dec 2022 13:27:37 +0100
+
 less (590-1) sid; urgency=low
 
   [ Milan Kupcevic ]
diff -Nru less-590/debian/copyright less-590/debian/copyright
--- less-590/debian/copyright   2021-12-30 05:49:58.0 +0100
+++ less-590/debian/copyright   2022-12-21 13:25:32.0 +0100
@@ -1,51 +1,104 @@
-This package was debianized by Thomas Schoepf  on
-Wed,  8 Sep 1999 13:28:20 +0200.
-
-The previous maintainers were Darren Stalder ,
-Erick Branderhorst  and
-Bill Mitchell .
-
-It was downloaded from http://www.greenwoodsoftware.com/less/
-
-Upstream Author: Mark Nudelman 
-
-Copyright:
-
-Copyright (C) 1984-2021  Mark Nudelman
-
-This program is free software.  You may redistribute it and/or
-modify it under the terms of either:
-
-1. The GNU General Public License, as published by the Free
-   Software Foundation; either version 3, or (at your option) any
-   later version.  A copy of this license is in the file
-   /usr/share/common-licenses/GPL-3
-or
-2. The Less License.
-
-  Less License
-  
-
-Less
-Copyright (C) 1984-2007  Mark Nudelman
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
-   notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
-   notice in the documentation and/or other materials provided with 
-   the distribution.
-
-THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
-PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT 
-OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR 
-BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 
-WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE 
-OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN 
-IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by Thomas Schoepf  on
+ Wed,  8 Sep 1999 13:28:20 +0200.
+ .
+ The previous maintainers were Darren Stalder ,
+ Erick Branderhorst  and
+ Bill Mitchell .
+Source: http://www.greenwoodsoftware.com/less/
+Upstream-Contact: Mark Nudelman 
+
+Files: *
+Copyright: (C) 1984-2021  Mark Nudelman
+License: GPL-3+ or Less
+ This program is free software.  You may redistribute it and/or
+ modify it under the terms of either:
+ .
+ 1. The GNU General Public License, as published by the Free
+Software Foundation; either version 3, or (at your option) any
+later version.  A copy of this license is in the file
+/usr/share/common-licenses/GPL-3
+ or
+ 2. The Less License.
+
+License: GPL-3+
+ You should have received a copy of the GNU General Public License
+ along with the source for less; see the file COPYING.
+ If not, write to the Free Software Foundation, 59 Temple Place,
+ Suite 330, Boston, MA  02111-1307, USA.
+
+License: Less
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+notice in the documentation and/or other materials provided with
+the distribution.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY
+ EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+ CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
+ OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+ BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
+ WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+ OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
+ IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Files: scrsize.c

Bug#1025837: marked as done (docopt: build-depends on dropped virtual package)

Your message dated Wed, 21 Dec 2022 12:19:16 +
with message-id 
and subject line Bug#1025837: fixed in docopt 0.6.2-4.1
has caused the Debian Bug report #1025837,
regarding docopt: build-depends on dropped virtual package
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.)


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

Source: docopt
Version: 0.6.2-4
Severity: serious
Tags: bookworm, sid
Justification: rc policy - "Packages must be buildable within the same release"
User:debian...@lists.debian.org
Usertags: edos-uninstallable

docopt build-depends on dh-sequence-python2, this is a virtual package that was
previously provided by dh-python but was dropped recently. This means that your
package cannot be built in testing or unstable.

I suspect this build-dependency is a leftover from before python 2 support was
removed from your package.

  

--- End Message ---
--- Begin Message ---
Source: docopt
Source-Version: 0.6.2-4.1
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
docopt, 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.
Michael R. Crusoe  (supplier of updated docopt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 12:57:23 +0100
Source: docopt
Architecture: source
Version: 0.6.2-4.1
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Michael R. Crusoe 
Closes: 1025837
Changes:
 docopt (0.6.2-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/control: drop unused dep on dh-sequence-python3. Closes: #1025837
Checksums-Sha1:
 bd0c3b3394f052dabc6dfa9d89835ef5ece1bcb2 1941 docopt_0.6.2-4.1.dsc
 addb680d04ba1dacb557ffd45b9fccd258b71ded 3948 docopt_0.6.2-4.1.debian.tar.xz
 3027579e41aafbc188468cf235ca8a1ef9495713 7974 docopt_0.6.2-4.1_source.buildinfo
Checksums-Sha256:
 395120490b797428328f0f17760f772d080ee4da867d692fad2e0b681e794f28 1941 
docopt_0.6.2-4.1.dsc
 fb9a5abe737c53168f613d2ca33867c3f488b1c1e439a0cde8de8949a2ba8d1e 3948 
docopt_0.6.2-4.1.debian.tar.xz
 56db8105738edc129013e6d53a25316f60e862d7e9007baeb8fd8b5ad3988d1f 7974 
docopt_0.6.2-4.1_source.buildinfo
Files:
 572fa3b1ae1f5bc0fb00d8eba389ce4f 1941 python optional docopt_0.6.2-4.1.dsc
 0ebf5aaeef0dc5a54ddc005eac1d5de3 3948 python optional 
docopt_0.6.2-4.1.debian.tar.xz
 ec9ef69abfa406848a6e074e3ccd14e1 7974 python optional 
docopt_0.6.2-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmOi9UEACgkQPCZ2P2xn
5uLTCg/+K/pXMTe+dtVay2H4DH81WSD4U/CaXkmohKD2szmcRPa7QGVVL4tAhRod
9fVCvWTrRStRoy82d8KNM00UrT6YaijWY3JKSCBXunjnFNh85seqzjXujrfAVwaS
VQpRfdTJtsOIzulYm9Dljlo0ZFEypK6PBDehJznuS0H2V8KHAvvSNySfzf8r7Gr+
pZcbTsV8v79UoiS1KpUCiRQMO+Xviob/+dwLY+ZqdjgzuSzpggQsF2v+dlDczA3E
g1jnRmu/6VhvMSZxPfAmtmIFG4hxrAct+TNXio6Wnc7RWDkV0gXJAZxaPuUhQ9Lj
Xqzc+E+ZjMy8NbDls828fn4/wdmeecC4wc4GAYbvJRSAFwTrRZGU9sppyMkVvM5b
G3JlHJP02A3xrqFD7u9E92XZPIFn1V+aNA5cPtKLsL2dcJFbiD3AIB920PQRlCRR
qHkFMqgKt6vL4RHzTFQNqHNH/3g+oqfWx9AcSX18bT4MoWbVWO6gJhq+mfYxZEF0
p4UlbPJUqnKs635AlhBOn7YudKSMbtOGZeOE7bC7it/mtuZh3v2Q3FUFnzssUbRl
qeVNqVkfzwRBsDSwsOgxZfHs0t+qLtyrUAr3zeuXA6+rhEyvmqdDOovezasIdkZ6
SJwIZAsdr0n3fHK3KHkFp6J9L0ZEK0oEL/WOR5HwYJ2v8wzlYKg=
=GaOi
-END PGP SIGNATURE End Message ---

Bug#1026163: Uses Java 11

The main reason puppetdb fails to build with JDK 17 is a check in 
project.clj which only allows Java 8 or 11. However, this has recently 
been expanded to allow Java 17 in upstream [1] and should be part of the 
7.12.0 release. So upgrading the package should hopefully resolve this.


Somewhat unrelated but I did notice that several other puppet-related 
packages, at least

https://tracker.debian.org/pkg/puppetlabs-http-client-clojure
https://tracker.debian.org/pkg/trapperkeeper-metrics-clojure
https://tracker.debian.org/pkg/trapperkeeper-webserver-jetty9-clojure

have similar checks which will fail with Java 17. They don't seem to 
have newer upstream versions though, and I don't know if additional 
changes in the code would be required for these to support Java 17.



[1] https://github.com/puppetlabs/puppetdb/blob/main/project.clj#L281
--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#1019937: NMU: elfutils: Missing licenses in d/copyright


I am uploading a NMU to DELAYED/10 to fix this. debdiff is attached.diff -Nru elfutils-0.188/debian/changelog elfutils-0.188/debian/changelog
--- elfutils-0.188/debian/changelog 2022-11-14 02:52:25.0 +0100
+++ elfutils-0.188/debian/changelog 2022-12-21 12:47:46.0 +0100
@@ -1,3 +1,11 @@
+elfutils (0.188-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/copyright: Convert to machine-readable format,
+adding missing licenses. (Closes: #1019937)
+
+ -- Bastian Germann   Wed, 21 Dec 2022 12:47:46 +0100
+
 elfutils (0.188-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru elfutils-0.188/debian/copyright elfutils-0.188/debian/copyright
--- elfutils-0.188/debian/copyright 2021-01-25 01:02:40.0 +0100
+++ elfutils-0.188/debian/copyright 2022-12-21 12:45:47.0 +0100
@@ -1,71 +1,184 @@
-This package was debianized by Kurt Roeckx  on
-Sun, 21 May 2006 15:03:01 +.
-
-It was downloaded from
-https://sourceware.org/elfutils/ftp/0.168/
-
-It was original a .tar.bz2.  It has been decompressed and
-recompressed again using gzip.
-
-Copyright Holder:
-   Copyright (C) 2000 - 2016 Red Hat, Inc.
-
-   Written by:
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment: This package was debianized by Kurt Roeckx .
+Source: https://sourceware.org/elfutils/ftp/
+
+Files: *
+ debuginfod/debuginfod-find.c
+Copyright: (C) 1996-2019 Red Hat, Inc.
+   (C) 2022 Mark J. Wielaard 
+   (C) 2015, 2016 Oracle, Inc.
+   (C) 2017 The Qt Company
+   (C) 2018, 2021 Facebook, Inc.
+   (C) 2021 Runsafe Security, Inc.
+   (C) H.J. Lu , 2015.
+   (C) 2020 Tom Tromey
+Comment: Written by:
Ulrich Drepper 
Jeff Johnson 
Alexander Larsson
Jakub Jelinek 
-   Roland McGrath 
-
-
-License:
-
-Most of the libraries (lib, libelf, libebl, libdw, libdwfl) have the following 
license:
-
+   Roland McGrath .
+ See more in the AUTHORS file.
+License: GPL-3+
+
+Files: backends/*
+   config/*
+   debuginfod/*
+   lib*
+   version.h
+   debian/patches/mips_cfi.patch
+Copyright: (C) 1996-2019 Red Hat, Inc.
+   (C) 2021, 2022 Mark J. Wielaard 
+   (C) 2015 Oracle, Inc.
+   (C) 2016, 2017 The Qt Company Ltd.
+   (C) 2021 Google, Inc.
+   (C) 2012 Tilera Corporation
+   (C) 2019 Hangzhou C-SKY Microsystems co.,ltd.
+   (C) H.J. Lu , 2015.
+   (c) 2021 Dmitry V. Levin 
+   (C) 2018 Sifive, Inc.
+   (C) 2018 Kurt Roeckx, Inc.
+Comment: Most of the libraries (lib, libelf, libebl, libdw, libdwfl) have
+ the following license:
+License: LGPL-3+ or GPL-2+
This file is free software; you can redistribute it and/or modify
it under the terms of either
-
+ .
  * the GNU Lesser General Public License as published by the Free
Software Foundation; either version 3 of the License, or (at
your option) any later version
-
+ .
or
-
+ .
  * the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at
your option) any later version
-
+ .
or both in parallel, as here.
-
+ .
elfutils is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
General Public License for more details.
-
+ .
You should have received copies of the GNU General Public License and
the GNU Lesser General Public License along with this program.  If
-   not, see .  */
-
-The other files are covered by the following license:
+   not, see .
+Comment:
+ On Debian GNU/Linux systems, the complete text of the GNU General
+ Public License version 2 can be found in
+ `/usr/share/common-licenses/GPL-2' and the complete text of the GNU
+ Lesser General Public License version 3 can be found in
+ `/usr/share/common-licenses/LGPL-3'.
+
+Files: lib/stdatomic-fbsd.h
+Copyright: (c) 2011 Ed Schouten 
+David Chisnall 
+ All rights reserved.
+License: BSD-2-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED.  IN NO EVENT

Bug#1026620: marked as done (libresample: FTBFS: cc: fatal error: no input files)

Your message dated Wed, 21 Dec 2022 11:49:35 +
with message-id 
and subject line Bug#1026620: fixed in libresample 0.1.3-6
has caused the Debian Bug report #1026620,
regarding libresample: FTBFS: cc: fatal error: no input files
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.)


-- 
1026620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libresample
Version: 0.1.3-5
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):
> cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/cc  
> -I/<>/obj-x86_64-linux-gnu/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/opus;-I/usr/include/x86_64-linux-gnu -MD -MT 
> tests/CMakeFiles/resample-sndfile.dir/resample-sndfile.c.o -MF 
> CMakeFiles/resample-sndfile.dir/resample-sndfile.c.o.d -o 
> CMakeFiles/resample-sndfile.dir/resample-sndfile.c.o -c 
> /<>/tests/resample-sndfile.c
> cc: fatal error: no input files
> compilation terminated.
> /bin/sh: 1: -I/usr/include/x86_64-linux-gnu: not found
> make[3]: *** [tests/CMakeFiles/resample-sndfile.dir/build.make:79: 
> tests/CMakeFiles/resample-sndfile.dir/resample-sndfile.c.o] Error 127


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/libresample_0.1.3-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

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

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

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

We believe that the bug you reported is fixed in the latest version of
libresample, 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.
Jonas Smedegaard  (supplier of updated libresample package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2022 12:36:57 +0100
Source: libresample
Architecture: source
Version: 0.1.3-6
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1026620
Changes:
 libresample (0.1.3-6) unstable; urgency=medium
 .
   * declare compliance with Debian Policy 4.6.2
   * update patch 1001 to deal with semicolon in cmake variables;
 closes: bug#1026620, thanks to Lucas Nussbaum
Checksums-Sha1:
 591a22edca64552950579a4a2848bf5dcb08c756 1997 libresample_0.1.3-6.dsc
 389c50e294b1ea9a34a4e72e3aacf68e59708fca 6004 libresample_0.1.3-6.debian.tar.xz
 d36aa60979368916a02f7905e9a9db348b3ed4c3 8114 
libresample_0.1.3-6_amd64.buildinfo
Checksums-Sha256:
 45ff9cc1f0533e4baf19bc4bb9c6aff80590511ef798a43fcca1922f569c4da2 1997 
libresample_0.1.3-6.dsc
 89cba738c8248d03a66817085e8a40b9c5eda311a8005e6d7c6fc77b93bcd62d 6004 
libresample_0.1.3-6.debian.tar.xz
 a8c13f75547cb3bb4ee442c2e27b0827937459ba221e1bed8538bf8259b723b1 8114 
libresample_0.1.3-6_amd64.buildinfo
Files:
 1560a86b8ee75476465d20d36fdc77cc 1997 libs optional libresample_0.1.3-6.dsc
 d25fc6e2bb5e5993bfa07b95c2bfdc8c 6004 libs optional 
libresample_0.1.3-6.debian.tar.xz
 9af52ebeb8305d9eca1893fa62502c4b 8114 libs optional 
libresample_0.1.3-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmOi8VoACgkQLHwxRsGg

Bug#1026803: chiaki: FTBFS (ModuleNotFoundError: No module named 'pkg_resources')

2022-12-21 Thread Eric Long

Source: chiaki
Version: 2.1.0-1.1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: i...@hack3r.moe

Dear maintainer(s),

chiaki failed to build due to Python module `pkg_resources` not found:

```
[  4%] Generating takion.pb.c, takion.pb.h
cd /<>/obj-riscv64-linux-gnu/lib/protobuf && /usr/bin/python3 
/usr/bin/nanopb_generator.py 
/<>/obj-riscv64-linux-gnu/lib/protobuf/takion.pb
Traceback (most recent call last):
  File "/usr/bin/nanopb_generator.py", line 53, in 
import proto
  File "/usr/lib/python3/dist-packages/proto/__init__.py", line 10, in 
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'
make[3]: *** [lib/protobuf/CMakeFiles/chiaki-pb.dir/build.make:77: 
lib/protobuf/takion.pb.c] Error 1
make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:199: 
lib/protobuf/CMakeFiles/chiaki-pb.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
```

Full buildd log: 
https://buildd.debian.org/status/fetch.php?pkg=chiaki=riscv64=2.1.0-1.1%2Bb3=167159=0

I've included a patch that adds python3-setuptools to d/control, fixing FTBFS.
If more help is needed, please let me know.

Cheers,
Eric
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Bartosz Fenski 
-Build-Depends: debhelper-compat (= 13), cmake, pkg-config, libopus-dev, 
qtmultimedia5-dev, libqt5svg5-dev, libsdl2-dev, libavcodec-dev, libswscale-dev, 
libjerasure-dev, libnanopb-dev, libssl-dev, protobuf-compiler, 
python3-protobuf, libevdev-dev, libudev-dev, libqt5opengl5-dev, python3-dev, 
libgl1-mesa-dev, imagemagick, librsvg2-bin, libpthread-stubs0-dev, 
libpthreadpool-dev, nanopb
+Build-Depends: debhelper-compat (= 13), cmake, pkg-config, libopus-dev, 
qtmultimedia5-dev, libqt5svg5-dev, libsdl2-dev, libavcodec-dev, libswscale-dev, 
libjerasure-dev, libnanopb-dev, libssl-dev, protobuf-compiler, 
python3-protobuf, libevdev-dev, libudev-dev, libqt5opengl5-dev, python3-dev, 
libgl1-mesa-dev, imagemagick, librsvg2-bin, libpthread-stubs0-dev, 
libpthreadpool-dev, nanopb, python3-setuptools
 Standards-Version: 4.5.1
 Homepage: https://git.sr.ht/~thestr4ng3r/chiaki
 Rules-Requires-Root: no

Bug#1026696: golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25

2022-12-21 Thread Shengjing Zhu

Hi,

On Wed, Dec 21, 2022 at 04:57:39PM +1300, Daniel Swarbrick wrote:
> After a fair amount of head scratching, I tracked this down to a change in
> behaviour of the protobuf compiler. Version 3.14.0+ generates slightly
> different pb.go files with respect to the timestamp type (and possibly
> others):
> 
> --- metrics.pb.go.old   2022-11-08 23:31:00.0 +1300
> +++ metrics.pb.go.new   2022-11-08 23:31:00.0 +1300
> @@ -6,7 +6,7 @@
>  import (
>     fmt "fmt"
>     proto "github.com/golang/protobuf/proto"
> -   timestamp "github.com/golang/protobuf/ptypes/timestamp"
> +   timestamppb "google.golang.org/protobuf/types/known/timestamppb"
>     math "math"
>  )

Mathias Gibbens has asked the same problem on debian-go@list.d.o somedays ago.
https://lists.debian.org/debian-go/2022/12/msg00024.html

The workaroud could be like this:
https://salsa.debian.org/go-team/packages/notary/-/commit/b0a072faa72857f7523c8245ecaa8814d5a60051

Bug#1024598: bash: NMU repack with fixed copyright


I am uploading a NMU with the enclosed debdiff to DELAYED/10 to close the 
current RC issues.diff -Nru bash-5.2/debian/changelog bash-5.2+dfsg/debian/changelog
--- bash-5.2/debian/changelog   2022-10-24 10:34:28.0 +0200
+++ bash-5.2+dfsg/debian/changelog  2022-12-21 12:16:28.0 +0100
@@ -1,3 +1,13 @@
+bash (5.2+dfsg-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Repack to get rid of non-source PDF. Closes: #1024598.
+  * d/watch: Update to v4 and add repack options.
+  * d/copyright: Convert to machine-readable format, adding missing info.
+Closes: #1024602.
+
+ -- Bastian Germann   Wed, 21 Dec 2022 12:16:28 +0100
+
 bash (5.2-2) unstable; urgency=medium
 
   * Apply upstream patches 001 - 002.
diff -Nru bash-5.2/debian/copyright bash-5.2+dfsg/debian/copyright
--- bash-5.2/debian/copyright   2014-03-03 22:46:18.0 +0100
+++ bash-5.2+dfsg/debian/copyright  2022-12-21 12:12:40.0 +0100
@@ -1,170 +1,186 @@
-This is Debian GNU/Linux's prepackaged version of the FSF's GNU Bash,
-the Bourne Again SHell.
-
-This package was put together by Matthias Klose , from
-the following sources:
-
-  bash:ftp.gnu.org:/pub/gnu/bash/bash-4.3.tar.gz
-
-Bash homepage:  http://tiswww.case.edu/php/chet/bash/bashtop.html
-
-Copyright (C) 1987-2014 Free Software Foundation, Inc.
-
-Bash is free software; you can redistribute it and/or modify it under
-the terms of the GNU General Public License as published by the Free
-Software Foundation; either version 3, or (at your option) any later
-version.
-
-Bash is distributed in the hope that it will be useful, but WITHOUT
-ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
-for more details.
-
-You should have received a copy of the GNU General Public License
-along with Bash.  If not, see .
-On Debian systems, the complete text of the GNU General Public License
-can be found in `/usr/share/common-licenses/GPL-3'.
-
-The Free Software Foundation has exempted Bash from the requirement of
-Paragraph 2c of the General Public License.  This is to say, there is
-no requirement for Bash to print a notice when it is started
-interactively in the usual way.  We made this exception because users
-and standards expect shells not to print such messages.  This
-exception applies to any program that serves as a shell and that is
-based primarily on Bash as opposed to other GNU software.
-
-
-Files with other copyright statement than: Copyright FSF, License GPL
--
-
-doc/FAQ ("the Bash FAQ")
-
- This document is Copyright 1995-2005 by Chester Ramey.
-
- Permission is hereby granted, without written agreement and
- without license or royalty fees, to use, copy, and distribute
- this document for any purpose, provided that the above copyright
- notice appears in all copies of this document and that the
- contents of this document remain unaltered.
-
-
-doc/bashref.texi ("Bash Reference Manual"):
-
- Copyright (c) 1988-2014 Free Software Foundation, Inc.
-
- Permission is granted to make and distribute verbatim copies of
- this manual provided the copyright notice and this permission notice
- are preserved on all copies.
-
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.3 or
- any later version published by the Free Software Foundation; with no
- Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
- A copy of the license is included in the section entitled
- ``GNU Free Documentation License''.
-
-
-lib/readline/doc/rlman.texi (part of the GNU Readline Library manual)
-
- Copyright (c) 1988-2014 Free Software Foundation, Inc.
-
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Contact: c...@po.cwru.edu
+Comment:
+ This is Debian GNU/Linux's prepackaged version of the FSF's GNU Bash,
+ the Bourne Again SHell.
+ .
+ This package was put together by Matthias Klose .
+Source:
+ ftp.gnu.org:/pub/gnu/bash
+Files-Excluded:
+ doc/FAQ
+ doc/aosa-bash*.pdf
+ doc/article.*
+ doc/rose94.*
+
+Files: *
+Copyright: (C) 1987-2022 Free Software Foundation, Inc.
+License: GPL-3+
+
+Files: examples/shellmath/*
+Copyright: (c) 2020 by Michael Wood. All rights reserved.
+License: GPL-3+
+
+Files: support/bash.xbm
+Copyright: (C) 1992 Simon Marshall
+License: GPL-3+
+
+Files: support/checkbashisms
+Copyright:
+ Copyright (C) 1998 Richard Braakman
+ Copyright (C) 2002 Josip Rodin
+ Copyright (C) 2003 Julian Gilbey
+License: GPL-3+
+
+Files:
+ tests/ifs-posix.tests
+ tests/posix2.tests
+Copyright: (C) 2005 Glen Fowler
+ Copyright (c) 1995 Stephen Gildea
+License: GPL-3+
+
+License: GPL-3+
+ Bash is free software; you can redistribute it and/or modify it under
+ the terms of the GNU General Public License as

Bug#1026492: seqan2: FTBFS: TypeError: a bytes-like object is required, not 'str'

On Wed, 2022-12-21 at 11:02 +0100, olivier sallou wrote:
> looks like a python3 issue (though was already adapter to py3...)
> 
> will have a look and reproduce

I could reproduce and found an issue with demo_checker.py handling with
python3

I have a patch. will test it and upload
> 
> Olivier
> 
> 

-- 


gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#1026617: libjt400-java: FTBFS: [javac] /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: reference to Record is ambiguous


tags 1026617 patch
thanks

[javac]   both class com.ibm.as400.access.Record in 
com.ibm.as400.access and class java.lang.Record in java.lang match
[javac] 
/<>/java8/com/ibm/as400/data/RecordFormatDocument.java:1375: 
error: reference to Record is ambiguous


Looks like the ambiguity stems from the new Record class introduced in 
new JDKS which hit when rebuilt with JDK 17. See the attached patch 
which adds an explicit import to the "local" Record class, which has 
been the one imported up until now.


With this patch in place, the package builds successfully again on 
Debian Sid.

--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgDescription: Explicit import for Record

Since this code predates java.lang.Record in the JDK, I'm going to assume 
it refers to its own class

---
Forwarded: no
Last-Update: 2022-12-21

--- libjt400-java-9.4.orig/src/com/ibm/as400/data/RecordFormatDocument.java
+++ libjt400-java-9.4/src/com/ibm/as400/data/RecordFormatDocument.java
@@ -14,6 +14,7 @@
 package com.ibm.as400.data;
 
 import com.ibm.as400.access.*;
+import com.ibm.as400.access.Record;
 
 import java.io.File;
 import java.io.FileOutputStream;
--- libjt400-java-9.4.orig/src/com/ibm/as400/data/RfmlRecordFormat.java
+++ libjt400-java-9.4/src/com/ibm/as400/data/RfmlRecordFormat.java
@@ -26,6 +26,7 @@ import java.util.TimeZone;
 import java.util.Vector;
 
 import com.ibm.as400.access.*;
+import com.ibm.as400.access.Record;
 
 
 /**

Processed: Re: libjt400-java: FTBFS: [javac] /<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: reference to Record is ambiguous

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

> tags 1026617 patch
Bug #1026617 [src:libjt400-java] libjt400-java: FTBFS: [javac] 
/<>/java8/com/ibm/as400/data/RecordFormatDocument.java:149: error: 
reference to Record is ambiguous
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#668644: [PATCH] qmc: Helping to update to packaging format 3.0


I am uploading a NMU with the debdiff attached to DELAYED/3.
This was the last dpatch-using package in the archive.diff -Nru qmc-0.94/debian/changelog qmc-0.94/debian/changelog
--- qmc-0.94/debian/changelog   2022-12-21 11:39:18.0 +0100
+++ qmc-0.94/debian/changelog   2022-12-21 11:23:02.0 +0100
@@ -1,3 +1,16 @@
+qmc (0.94-4.1) unstable; urgency=low
+
+  * Non-maintainer upload
+  * Fix missing-depends-on-sensible-utils (Lintian)
+
+  [ Jari Aalto ]
+  * Remove deprecated dpatch and upgrade to packaging format "3.0 (quilt)"
+(closes: #668644)
+  * Fix copyright-without-copyright-notice (Lintian)
+  * Fix copyright-refers-to-symlink-license (Lintian)
+
+ -- Bastian Germann   Wed, 21 Dec 2022 11:23:02 +0100
+
 qmc (0.94-4) unstable; urgency=medium
 
   * build using dh sequencer (well,  theoretically) (closes: #998921)
diff -Nru qmc-0.94/debian/control qmc-0.94/debian/control
--- qmc-0.94/debian/control 2022-12-21 11:39:18.0 +0100
+++ qmc-0.94/debian/control 2022-12-21 11:23:02.0 +0100
@@ -2,12 +2,12 @@
 Section: science
 Priority: optional
 Maintainer: Rene Engelhard 
-Build-Depends: debhelper (>= 10), dpatch
+Build-Depends: debhelper (>= 10)
 Standards-Version: 3.9.8
 
 Package: qmc
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, sensible-utils
 Recommends: wish
 Suggests: www-browser
 Description: Quine McClusky Simplification Tool
diff -Nru qmc-0.94/debian/copyright qmc-0.94/debian/copyright
--- qmc-0.94/debian/copyright   2022-12-21 11:39:18.0 +0100
+++ qmc-0.94/debian/copyright   2022-12-21 11:18:06.0 +0100
@@ -1,11 +1,14 @@
 This package was debianized by Rene Engelhard  on
 Sun,  2 Nov 2003 01:24:58 +0100.
 
-It was downloaded from http://qmc.pollaknet.at/
+It was downloaded from http://qmc.pollaknet.at/ which as of
+2012-04-13 no longer exists.
 
 Upstream Author: Thomas Pollak 
 
 Copyright:
 
+   Copyright (C) 2000 Thomas Pollak 
+
 GNU GPL, on Debian systems you can find the full text of the GPL
-under /usr/share/common-licenses/GPL
+under /usr/share/common-licenses/GPL-2
diff -Nru qmc-0.94/debian/patches/00list qmc-0.94/debian/patches/00list
--- qmc-0.94/debian/patches/00list  2022-12-21 11:39:18.0 +0100
+++ qmc-0.94/debian/patches/00list  1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-01_wish_in_shebang
-02_run_sensible-browser
diff -Nru qmc-0.94/debian/patches/01_wish_in_shebang.dpatch 
qmc-0.94/debian/patches/01_wish_in_shebang.dpatch
--- qmc-0.94/debian/patches/01_wish_in_shebang.dpatch   2022-12-21 
11:39:18.0 +0100
+++ qmc-0.94/debian/patches/01_wish_in_shebang.dpatch   1970-01-01 
01:00:00.0 +0100
@@ -1,36 +0,0 @@
-#!/bin/sh -e
-## 01_wish_in_shebang.dpatch by Rene Engelhard 
-##
-## All lines beginning with `## DP:' are a description of the patch.
-## DP: No description.
-
-if [ $# -ne 1 ]; then
-echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
-exit 1
-fi
-
-[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
-patch_opts="${patch_opts:--f --no-backup-if-mismatch}"
-
-case "$1" in
-   -patch) patch $patch_opts -p1 < $0;;
-   -unpatch) patch $patch_opts -p1 -R < $0;;
-*)
-echo >&2 "`basename $0`: script expects -patch|-unpatch as 
argument"
-exit 1;;
-esac
-
-exit 0
-
-@DPATCH@
-diff -urNad /home/rene/Debian/Pakete/ITP/qmc/qmc-0.94/qmc-gui.tcl 
qmc-0.94/qmc-gui.tcl
 /home/rene/Debian/Pakete/ITP/qmc/qmc-0.94/qmc-gui.tcl  2003-10-30 
16:30:21.0 +0100
-+++ qmc-0.94/qmc-gui.tcl   2003-12-03 04:45:56.0 +0100
-@@ -1,6 +1,4 @@
--#!/bin/sh
--#\
--exec wish "$0"
-+#!/usr/bin/wish
- 
- set qmc(status) "Status: waiting for input"
- set qmc(output) ""
diff -Nru qmc-0.94/debian/patches/01-wish-in-shebang.patch 
qmc-0.94/debian/patches/01-wish-in-shebang.patch
--- qmc-0.94/debian/patches/01-wish-in-shebang.patch1970-01-01 
01:00:00.0 +0100
+++ qmc-0.94/debian/patches/01-wish-in-shebang.patch2022-12-21 
11:18:06.0 +0100
@@ -0,0 +1,14 @@
+From: Rene Engelhard 
+Subject: No description.
+
+diff -urNad /home/rene/Debian/Pakete/ITP/qmc/qmc-0.94/qmc-gui.tcl 
qmc-0.94/qmc-gui.tcl
+--- /home/rene/Debian/Pakete/ITP/qmc/qmc-0.94/qmc-gui.tcl  2003-10-30 
16:30:21.0 +0100
 qmc-0.94/qmc-gui.tcl   2003-12-03 04:45:56.0 +0100
+@@ -1,6 +1,4 @@
+-#!/bin/sh
+-#\
+-exec wish "$0"
++#!/usr/bin/wish
+ 
+ set qmc(status) "Status: waiting for input"
+ set qmc(output) ""
diff -Nru qmc-0.94/debian/patches/02_run_sensible-browser.dpatch 
qmc-0.94/debian/patches/02_run_sensible-browser.dpatch
--- qmc-0.94/debian/patches/02_run_sensible-browser.dpatch  2022-12-21 
11:39:18.0 +0100
+++ qmc-0.94/debian/patches/02_run_sensible-browser.dpatch  1970-01-01 
01:00:00.0 +0100
@@ -1,37 +0,0 @@
-#!/bin/sh -e
-## 02_run_sensible-browser.dpatch by Rene Engelhard 
-##
-## All lines

Bug#1026492: seqan2: FTBFS: TypeError: a bytes-like object is required, not 'str'

looks like a python3 issue (though was already adapter to py3...)

will have a look and reproduce

Olivier


-- 


gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#1026701: marked as done (skyfield: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Wed, 21 Dec 2022 10:06:13 +
with message-id 
and subject line Bug#1026701: fixed in skyfield 1.45+ds-2
has caused the Debian Bug report #1026701,
regarding skyfield: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.11 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.)


-- 
1026701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skyfield
Version: 1.45+ds-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):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/starlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/magnitudelib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/curvelib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/framelib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/named_stars.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/jpllib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/almanac.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/errors.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/api.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/eclipselib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/nutationlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/precessionlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/projections.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/earthlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/keplerlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/geometry.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/constellationlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/relativity.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/almanac_east_asia.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/toposlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/planetarylib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/trigonometry.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/iokit.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/units.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/vectorlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/positionlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/functions.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/charting.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/searchlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/sgp4lib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/constants.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/elementslib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/_compatibility.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/naifcodes.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/io_timescale.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/timelib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> copying skyfield/descriptorlib.py -> 
> /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield
> creating /<>/.pybuild/cpython3_3.11_skyfield/build/skyfield/data
> copying skyfield/data/__init__.py -> 
>

Bug#1013638: marked as done (apertium-dan-nor: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)

Your message dated Wed, 21 Dec 2022 10:49:27 +0100
with message-id 

and subject line Fixed in v1.5.0
has caused the Debian Bug report #1013638,
regarding apertium-dan-nor: FTBFS: configure: error: Package requirements 
(apertium-lex-tools >= 0.2.2) were not met
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.)


-- 
1013638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-dan-nor
Version: 1.4.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.6.0... yes
> checking for lttoolbox >= 3.5.0... yes
> checking for cg3 >= 1.3.0... yes
> checking for apertium-lex-tools >= 0.2.2... no
> configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not 
> met
> 
> No package 'apertium-lex-tools' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS
> and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-dan-nor_1.4.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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

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

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

Forgot to close this in d/changelog.

-- Tino Didriksen
--- End Message ---

Bug#1019812: marked as done (wxhexeditor: Please transition to wxwidgets3.2)

Your message dated Wed, 21 Dec 2022 09:35:29 +
with message-id 
and subject line Bug#1019812: fixed in wxhexeditor 0.24+repack-2
has caused the Debian Bug report #1019812,
regarding wxhexeditor: Please transition to wxwidgets3.2
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.)


-- 
1019812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wxhexeditor
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition wxhexeditor from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: wxhexeditor
Source-Version: 0.24+repack-2
Done: Andrej Shadura 

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

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

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated wxhexeditor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Dec 2022 10:14:01 +0100
Source: wxhexeditor
Architecture: source
Version: 0.24+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 1019812
Changes:
 wxhexeditor (0.24+repack-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Set upstream metadata fields: Archive, Name, Repository.
   * Update standards version to 4.6.0, no changes needed.
 .
   [ Scott Talbert ]
   * Transition to wxWidgets 3.2 (Closes: #1019812)
Checksums-Sha1:
 093ccfa134ac430aef09c5cd075a448afbf7ece0 1466 wxhexeditor_0.24+repack-2.dsc
 1a5a9cb64c9752da8c4dcb1cb87e46ef5e37c722 7072 
wxhexeditor_0.24+repack-2.debian.tar.xz
Checksums-Sha256:
 eca45bd060f8af6d2da7a4a48c95a4e5d7ee7475d0be78201c414e3e20d7cf34 1466 
wxhexeditor_0.24+repack-2.dsc
 753c0a9128743165e605490c20715610b177df790dd787fce54cee0bd3e9bfdb 7072 
wxhexeditor_0.24+repack-2.debian.tar.xz
Files:
 46700d6203eda71f3c5fd2933779cc3c 1466 editors optional 
wxhexeditor_0.24+repack-2.dsc
 ca1ed4ed0ace24eaf4f636fc9b886f31 7072 editors optional 
wxhexeditor_0.24+repack-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCY6LOngAKCRDoRGtKyMdy
YTx2AP99cke5aIZZFdqFAwgaGmYIjM2WO36nwoYjO0jKOTgV9wD7BArOcNflFx76
z6dkjxhpK3Gwk2xYdVMWBsi9A/6dcwQ=
=1qhk
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1026520: reprotest: FTBFS: AttributeError: module 're' has no attribute 'sre_parse'