Bug#1027828: [Debichem-devel] Bug#1027828: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Santiago Vila]

El 4/1/23 a las 8:40, Andrius Merkys escribió:


I can reproduce the issue. Should I propose a bullseye-pu upload fixing it?


Yes, please. Packages in stable must build in stable, that's the idea.

Thanks.

Bug#1027828: [Debichem-devel] Bug#1027828: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Andrius Merkys]

Hi Santiago,

On 2023-01-03 22:35, Santiago Vila wrote:

Package: src:macromoleculebuilder
Version: 3.2+dfsg-2
Severity: serious
Tags: ftbfs
Control: fixed -1 4.0.0+dfsg-2

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build


I can reproduce the issue. Should I propose a bullseye-pu upload fixing it?

Best,
Andrius

Processed: closing 1027603

[Debian Bug Tracking System]

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

> close 1027603 4.26-1
Bug #1027603 [src:eclipse-platform-debug] eclipse-platform-debug: FTBFS: 
[javac] 
/<>/org.eclipse.core.variables/target/sources/org/eclipse/core/internal/variables/StringVariableManager.java:58:
 error: package org.osgi.service.prefs does not exist
Marked as fixed in versions eclipse-platform-debug/4.26-1.
Bug #1027603 [src:eclipse-platform-debug] eclipse-platform-debug: FTBFS: 
[javac] 
/<>/org.eclipse.core.variables/target/sources/org/eclipse/core/internal/variables/StringVariableManager.java:58:
 error: package org.osgi.service.prefs does not exist
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1027603: closing 1027603

[Jochen Sprickerhof]

close 1027603 4.26-1
thanks

Bug#1027095: marked as done (ruby-vcr: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: /<>/lib/vcr/library_hooks/webmock.rb:36:in `block in global_hook_disabled_requests': wrong

[Debian Bug Tracking System]

Your message dated Wed, 04 Jan 2023 07:21:08 +
with message-id 
and subject line Bug#1027095: fixed in ruby-vcr 6.0.0+really5.0.0-5
has caused the Debian Bug report #1027095,
regarding ruby-vcr: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: 
/<>/lib/vcr/library_hooks/webmock.rb:36:in `block in 
global_hook_disabled_requests': wrong number of arguments (given 1, expected 0) 
(ArgumentError)
to be marked as done.

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

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


-- 
1027095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-vcr
Version: 6.0.0+really5.0.0-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-vcr failed to build.

Relevant part of the build log (hopefully):
> /<>/lib/vcr/library_hooks/webmock.rb:36:in `block in 
> global_hook_disabled_requests': wrong number of arguments (given 1, expected 
> 0) (ArgumentError)
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-vcr.log.gz
Description: application/gzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-vcr
Source-Version: 6.0.0+really5.0.0-5
Done: HIGUCHI Daisuke (VDR dai) 

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

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated ruby-vcr 
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, 04 Jan 2023 15:48:10 +0900
Source: ruby-vcr
Architecture: source
Version: 6.0.0+really5.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: HIGUCHI Daisuke (VDR dai) 
Closes: 1027095
Changes:
 ruby-vcr (6.0.0+really5.0.0-5) unstable; urgency=medium
 .
   * Team upload.
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * fix FTBFS with ruby-rspec-3.12, ruby-3.1 and em-http-request
(Closes: #1027095)
   * clean test files.
   * eliminate lintian warning: trailing-whitespace
   * eliminate lintian warning: patch-not-forwarded-upstream
   * Drop XS-Ruby-Version and XB-Ruby-Version.
Checksums-Sha1:
 c55ec687ce1ba0a03857b18620f664fa1384e474 2308 ruby-vcr_6.0.0+really5.0.0-5.dsc
 8dd047a2f12e1c30b2f10d9da75da1c5612355bc 9044 
ruby-vcr_6.0.0+really5.0.0-5.debian.tar.xz
Checksums-Sha256:
 07ccc179ff12d8928730589868f915a5be03fc13426252e7108fbdd26394511a 2308 
ruby-vcr_6.0.0+really5.0.0-5.dsc
 7a5a2d700b8991c98f0356b9e7bcbb64f83328331d2227f366826ba9f4c7e523 9044 
ruby-vcr_6.0.0+really5.0.0-5.debian.tar.xz
Files:
 19818bff97fae8b5c40dab98bf6e0ab4 2308 ruby optional 
ruby-vcr_6.0.0+really5.0.0-5.dsc
 1890b1941c32f7d6156894ba63dc4f3d 9044 ruby optional 
ruby-vcr_6.0.0+really5.0.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmO1JX8ACgkQeDlhndQ5
Zo7byRAAx6gatDTYQdkslnGf4x1FNWKWIo9MJxca9UmLtMc7YzCpQlTl0mIyAIic
krR79Tbn6VXNBCHxOCJkOz0eKq6jxj2xNEzOv2ADBjhXU0jLS65K943SCRZxSP23
hzVO61WroNBYYCEtaPN1u/iGC6II3W1T+j4Y4I+LOhqTwvNHYzVrKiHcDmZ2TMN/
+qNPac9pRY7aqF0LGzx7sWUP5sfjst2PYsi1bvtR1886i2y0uMcS6E3JCdW79bEQ
8Ngd/9H3li3weTMRZPazXwQj4InUjEHqxKT+sYUVLkWsz74mEMnUU+BwcU4pM8Zl
eZuzfknZ19B22SzjzmnXHxAJR2ozwlxrqbuzTIhUIQcRW+npQr5yFNUM4DTrUDvq
hvZLDw+VusDoO/lx6axWs4jN2eOAQmxVZwyZ+U+WOfezVLF0fy2LSPz0KuB5e92a
18LrUqToFmW4SuTuQbzvI9qB7tVViijsn2/e14Y0SaDBUaqQd2CBL0U6t2agRAtJ
YkkRJ2ye58NvTqLxNtszTOf3zLKpImdB4DRQyqSPbfxF6b+5TDSkdaSUREcANtMh
tLnCc2IwHeGUvbbhoCzb+44IiKt7fF0xQchDc5CD4WjTBfMRWgYUWGFvFMriD8s/

Bug#1027508: closing 1027508

[Jochen Sprickerhof]

close 1027508 4.26-1
thanks

Processed: closing 1027508

[Debian Bug Tracking System]

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

> close 1027508 4.26-1
Bug #1027508 [src:eclipse-platform-runtime] eclipse-platform-runtime: FTBFS:
 [javac] 
/<>/bundles/org.eclipse.core.contenttype/target/sources/org/eclipse/core/internal/content/ContentType.java:23:
 error: package org.osgi.service.prefs does not exist
Marked as fixed in versions eclipse-platform-runtime/4.26-1.
Bug #1027508 [src:eclipse-platform-runtime] eclipse-platform-runtime: FTBFS:
 [javac] 
/<>/bundles/org.eclipse.core.contenttype/target/sources/org/eclipse/core/internal/content/ContentType.java:23:
 error: package org.osgi.service.prefs does not exist
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1026575: closing 1026575

[Jochen Sprickerhof]

close 1026575 2.0.1-1
thanks

Processed: closing 1026575

[Debian Bug Tracking System]

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

> close 1026575 2.0.1-1
Bug #1026575 [src:autopep8] autopep8: FTBFS: AssertionError: 
b'/<>/aut[161 chars]ze\n' != b''
Marked as fixed in versions autopep8/2.0.1-1.
Bug #1026575 [src:autopep8] autopep8: FTBFS: AssertionError: 
b'/<>/aut[161 chars]ze\n' != b''
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1027811: libcifpp-data: uninstallable

[Nilesh Patra]

Hi Maarten/Patrice,

On Tue, 03 Jan 2023 17:23:19 +0100 Patrice DUROUX  
wrote:
> Package: libcifpp-data
> Version: 5.0.5-5
> Severity: normal
> 
> Dear Maintainer,
> 
> Here is the output:
> 
> Setting up libcifpp-data (5.0.5-5) ...
> /etc/cron.weekly/update-libcifpp-data: 9: Syntax error: "then" unexpected
> dpkg: error processing package libcifpp-data (--configure):
>  installed libcifpp-data package post-installation script subprocess returned 
> error exit status 2
> 
> 
> This script contains a duplicated 'then' directive:
> 
>  8if [ "${euid}" -ne 0 ] ; then
>  9then echo "Please run as root"
> 10exit
> 11fi

This is fixed in the latest upload right - could you check?
If so, could you close this bug report?
 

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1027667: marked as done (ros-actionlib: FTBFS: make: *** [debian/rules:11: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jan 2023 06:56:16 +
with message-id 
and subject line Bug#1027667: fixed in ros-actionlib 1.14.0-4
has caused the Debian Bug report #1027667,
regarding ros-actionlib: FTBFS: make: *** [debian/rules:11: 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.)


-- 
1027667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-actionlib
Version: 1.14.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 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 '/<>/obj-x86_64-linux-gnu/actionlib'
> make[4]: Nothing to be done for 'CMakeFiles/run_tests.dir/build'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu/actionlib'
> [100%] Built target run_tests
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu/actionlib'
> /usr/bin/cmake -E cmake_progress_start 
> /<>/obj-x86_64-linux-gnu/actionlib/CMakeFiles 0
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu/actionlib'
> make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu/actionlib'
> catkin_test_results
> obj-x86_64-linux-gnu/actionlib/test_results/actionlib/rosunit-test_cpp_simple_client.xml:
>  14 tests, 0 errors, 2 failures, 0 skipped
> Summary: 75 tests, 0 errors, 2 failures, 0 skipped
> dh_auto_install: error: rosbuilder --sourcedir . --builddir 
> obj-x86_64-linux-gnu --destdir /<>/debian/tmp returned exit code 
> 1
> make: *** [debian/rules:11: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/ros-actionlib_1.14.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=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: ros-actionlib
Source-Version: 1.14.0-4
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-actionlib 
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, 04 Jan 2023 07:40:28 +0100
Source: ros-actionlib
Architecture: source
Version: 1.14.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1027667
Changes:
 ros-actionlib (1.14.0-4) unstable; urgency=medium
 .
   * Disable more flaky tests (Closes: #1027667)
   * Bump policy version (no changes)
Checksums-Sha1:
 cbe67e213e7155184a4f4ac43d0c45976cf4eae6 3296 ros-actionlib_1.14.0-4.dsc
 13e00b60fe4873239a932073dfdf14e09ccb1ee3 8452 
ros-actionlib_1.14.0-4.debian.tar.xz
 bf2ad4b3218ae2dd9a5c16db550147d907eedcbe 7032 
ros-actionlib_1.14.0-4_source.buildinfo
Checksums-Sha256:
 615f35426c6a5e13c5208f7116b2fd10e2a056bf1b8219472a27839fbb268f87 3296 
ros-actionlib_1.14.0-4.dsc
 271d1f66e4ae8d86fc77cd8f934fad1b129d4df6ef8218b25adc7d430fe6c565 8452 
ros-actionlib_1.14.0-4.debian.tar.xz
 5b1bf5d23d795316913c06bb03cfc76a9d4399f40009a52a097a91a7b6a0122d 7032 
ros-actionlib_1.14.0-4_source.buildinfo
Files:
 a7770d1b5c6aa183db904fc83b477d49 3296 libs optional ros-actionlib_1.14.0-4.dsc
 94cd78d947bfc0506db1db2cdadc1f9e 8452 libs optional 
ros-actionlib_1.14.0-4.debian.tar.xz
 580cdb604fd1d4821cfa0f1a227ff127 7032 libs optional 

Processed: owner

[Debian Bug Tracking System]

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

> owner 1010244 !
Bug #1010244 [phpsysinfo] does not work with PHP 8.1
Owner recorded as William Desportes .
> owner 1021030 !
Bug #1021030 [phpsysinfo] phpsysinfo: phpSysInfo vulnerable to multiple CVEs in 
bundled jQuery lib
Owner recorded as William Desportes .
> owner 632638 !
Bug #632638 [phpsysinfo] phpsysinfo throws a lot of errors in default config
Owner recorded as William Desportes .
> owner 1001949 !
Bug #1001949 [phpsysinfo] phpsysinfo: Please drop the Suggests: hddtemp
Owner recorded as William Desportes .
> stop
Stopping processing here.

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

Bug#1026513: patch seems incorrect, here's a better one

[FC Stegerman]

Hi!

The package description for python3-nose-random says:

  * uses a fixed seed so that each test run is identical
  * lets you to run the test only on a specific scenario to facilitate
debugging

I'm not very familiar with this package, but the removal of rseed in
the patch seems to me to break those properties, since it no longer
uses a fixed seed.

The real problem seems to be that config.scenario can be _missing,
which is an object() instead of a supported seed type.

I've attached a patch that fixes the original problem -- jsondiff's
tests no longer fail -- without removing the use of rseed.

- FC
--- a/nose_random/__init__.py	2023-01-04 07:38:06.340805543 +0100
+++ b/nose_random/__init__.py	2016-10-19 11:17:54.0 +0200
@@ -51,7 +51,7 @@
 def randomize(n, scenario_generator, seed=12038728732):
 def decorator(test):
 def randomized_test(self):
-if config.scenario is not None and config.scenario is not _missing:
+if config.scenario is not None:
 nseeds = 1
 seeds = [config.scenario]
 else:
@@ -70,4 +70,4 @@
 else:
 raise (type(e), type(e)('%s with scenario %s (%i of %i)' % (e.message, rseed, i+1, nseeds)), sys.exc_info()[2])
 return randomized_test
-return decorator
+return decorator
\ No newline at end of file

Bug#1010244: Started packaging refresh

[William Desportes]

Hi, 

I started refreshing the packaging at 
https://salsa.debian.org/php-team/pear/phpsysinfo

You can expect this bug to get fixed some time soon

--
William Desportes

Processed: closing 1027534

[Debian Bug Tracking System]

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

> close 1027534 4.26-1
Bug #1027534 [src:eclipse-platform-team] eclipse-platform-team: FTBFS: 
[javac] 
/<>/bundles/org.eclipse.core.net/target/sources/org/eclipse/core/internal/net/PreferenceManager.java:23:
 error: package org.osgi.service.prefs does not exist
Marked as fixed in versions eclipse-platform-team/4.26-1.
Bug #1027534 [src:eclipse-platform-team] eclipse-platform-team: FTBFS: 
[javac] 
/<>/bundles/org.eclipse.core.net/target/sources/org/eclipse/core/internal/net/PreferenceManager.java:23:
 error: package org.osgi.service.prefs does not exist
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1027534: closing 1027534

[Jochen Sprickerhof]

close 1027534 4.26-1
thanks

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 1027628 libbtrfs-dev
Bug #1027628 [src:snapper] snapper: FTBFS: regex_compiler.tcc:179:19: error: 
expected unqualified-id before ‘=’ token
Bug reassigned from package 'src:snapper' to 'libbtrfs-dev'.
No longer marked as found in versions snapper/0.10.4-1.
Ignoring request to alter fixed versions of bug #1027628 to the same values 
previously set
> tags 1027628 +fixed-upstream
Bug #1027628 [libbtrfs-dev] snapper: FTBFS: regex_compiler.tcc:179:19: error: 
expected unqualified-id before ‘=’ token
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1027854: kismet-plugins: uninstallable due to dependency on libssl1.1

[Christoph Anton Mitterer]

Package: kismet-plugins
Version: 2016.07.R1-1+b1
Severity: grave
Justification: renders package unusable


Hey.

libssl1.1 has been removed from unstable and thus kismet-plugins is no
longer installable.

Cheers,
Chris.

Processed: Re: Bug#1026490: sssd: FTBFS: make[1]: *** [debian/rules:102: override_dh_missing] Error 25

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1026490 [src:sssd] sssd: FTBFS: make[1]: *** [debian/rules:102: 
override_dh_missing] Error 25
Added tag(s) patch.

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

Bug#1026490: sssd: FTBFS: make[1]: *** [debian/rules:102: override_dh_missing] Error 25

[Sergio Durigan Junior]

Control: tags -1 + patch

On Tuesday, December 20 2022, Lucas Nussbaum wrote:

> Source: sssd
> Version: 2.8.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 '/<>'
>> dh_missing --fail-missing
>> dh_missing: warning: 
>> usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/PKG-INFO exists in 
>> debian/tmp but is not installed to anywhere 
>> dh_missing: warning: 
>> usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/dependency_links.txt 
>> exists in debian/tmp but is not installed to anywhere 
>> dh_missing: warning: 
>> usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/top_level.txt 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: libipa-hbac-dev (3), libipa-hbac0 (2), libnss-sss (1), 
>> libpam-sss (4), libsss-certmap-dev (3), libsss-certmap0 (3), 
>> libsss-idmap-dev (3), libsss-idmap0 (2), libsss-nss-idmap-dev (3), 
>> libsss-nss-idmap0 (2), libsss-simpleifp-dev (4), libsss-simpleifp0 (2), 
>> libsss-sudo (1), python3-libipa-hbac (1), python3-libsss-nss-idmap (1), 
>> python3-sss (5), sssd (0), sssd-ad (3), sssd-ad-common (3), sssd-common 
>> (96), sssd-dbus (5), sssd-idp (4), sssd-ipa (3), sssd-kcm (6), sssd-krb5 
>> (4), sssd-krb5-common (2), sssd-ldap (3), sssd-proxy (2), sssd-tools (14)
>>   * dh_installdocs: libipa-hbac-dev (0), libipa-hbac0 (0), libnss-sss 
>> (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), 
>> libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), 
>> libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), 
>> libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), 
>> python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), 
>> sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), 
>> sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0)
>>   * dh_installexamples: libipa-hbac-dev (0), libipa-hbac0 (0), 
>> libnss-sss (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), 
>> libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), 
>> libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), 
>> libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), 
>> python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), 
>> sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), 
>> sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (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:102: override_dh_missing] Error 25
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2022/12/20/sssd_2.8.1-1_unstable.log

The following MR should be fix this:

  https://salsa.debian.org/sssd-team/sssd/-/merge_requests/20

Cheers,

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

Bug#1027076: marked as done (ruby-influxdb: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jan 2023 02:41:49 +
with message-id 
and subject line Bug#1027076: fixed in ruby-influxdb 0.8.1-2
has caused the Debian Bug report #1027076,
regarding ruby-influxdb: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" 
failed.
to be marked as done.

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

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


-- 
1027076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-influxdb
Version: 0.8.1-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-influxdb failed to build.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-influxdb/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"influxdb\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-influxdb/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> ./spec/influxdb/cases/query_batch_spec.rb 
> ./spec/influxdb/cases/query_cluster_spec.rb 
> ./spec/influxdb/cases/query_continuous_query_spec.rb 
> ./spec/influxdb/cases/query_core_spec.rb 
> ./spec/influxdb/cases/query_database_spec.rb 
> ./spec/influxdb/cases/query_retention_policy_spec.rb 
> ./spec/influxdb/cases/query_series_spec.rb 
> ./spec/influxdb/cases/query_shard_spec.rb 
> ./spec/influxdb/cases/query_user_spec.rb 
> ./spec/influxdb/cases/query_with_params_spec.rb 
> ./spec/influxdb/cases/querying_issue_7000_spec.rb 
> ./spec/influxdb/cases/querying_spec.rb 
> ./spec/influxdb/cases/retry_requests_spec.rb 
> ./spec/influxdb/cases/show_field_keys_spec.rb 
> ./spec/influxdb/cases/udp_client_spec.rb 
> ./spec/influxdb/cases/write_points_spec.rb ./spec/influxdb/client_spec.rb 
> ./spec/influxdb/config_spec.rb ./spec/influxdb/logging_spec.rb 
> ./spec/influxdb/max_queue_spec.rb ./spec/influxdb/point_value_spec.rb 
> ./spec/influxdb/query_builder_spec.rb ./spec/influxdb/time_conversion_spec.rb 
> ./spec/influxdb/worker_spec.rb ./spec/smoke/smoke_batch_spec.rb 
> ./spec/smoke/smoke_spec.rb --format documentation
> SMOKE TESTS ARE NOT CURRENTLY RUNNING
> Run options: exclude {:smoke=>true}
> Run options: exclude {:smoke=>true}
> 
> InfluxDB::Client
>   #batch
> is expected to be a kind of InfluxDB::Query::Batch
> .#execute
>   is expected to eq []
> .#add
>   returns statement id
> .  block form
> returns statement id
> .  #batch.execute
> with multiple queries when there is no data for a query
>   should return responses for all statements
> .with a group by tag query
>   should return a single result
> .
> InfluxDB::Client
>   #create_cluster_admin
> with existing admin user
>   should GET to create a new cluster admin
> .with no admin user
>   should GET to create a new cluster admin
> .  #list_cluster_admins
> should GET a list of cluster admins
> .  #revoke_cluster_admin_privileges
> should GET to revoke cluster admin privileges from a user
> .
> InfluxDB::Client
>   #list_continuous_queries
> should GET a list of continuous queries for specified 

Processed: tagging 1027851

[Debian Bug Tracking System]

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

> tags 1027851 + ftbfs
Bug #1027851 [src:pytorch] pytorch FTBFS with Python 3.11 as default version
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1027851: pytorch FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: pytorch
Version: 1.12.1-1
Severity: serious
Forwarded: https://github.com/pytorch/pytorch/pull/81242

https://buildd.debian.org/status/fetch.php?pkg=pytorch=amd64=1.12.1-1%2Bb2=1672759960=0

...
FAILED: caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o 
/usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DBUILDING_TESTS -DGFLAGS_IS_A_DLL=0 
-DGLOG_CUSTOM_PREFIX_SUPPORT -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 
-DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS 
-DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx -DTHP_BUILD_MAIN_LIB 
-DUSE_C10D -DUSE_C10D_GLOO -DUSE_DISTRIBUTED -DUSE_EXTERNAL_MZCRC -DUSE_NUMPY 
-DUSE_RPC -DUSE_TENSORPIPE -DUSE_VALGRIND -D_FILE_OFFSET_BITS=64 
-Dtorch_python_EXPORTS -I/<>/build/aten/src 
-I/<>/aten/src -I/<>/build -I/<> 
-I/<>/cmake/../third_party/benchmark/include 
-I/<>/debian/foxi -I/<>/build/debian/foxi 
-I/<>/torch/.. -I/<>/torch/../aten/src 
-I/<>/torch/../aten/src/TH 
-I/<>/build/caffe2/aten/src -I/<>/build/third_party 
-I/<>/build/third_party/onnx 
-I/<>/torch/../third_party/valgrind-headers 
-I/<>/torch/../third_party/gloo 
-I/<>/torch/../third_party/onnx 
-I/<>/torch/../third_party/flatbuffers/include 
-I/<>/torch/csrc -I/<>/torch/csrc/api/include 
-I/<>/torch/lib -I/<>/torch/lib/libshm 
-I/<>/torch/csrc/distributed -I/<>/torch/csrc/api 
-I/<>/c10/.. 
-I/<>/torch/lib/libshm/../../../torch/lib -isystem 
/<>/build/third_party/gloo -isystem 
/<>/cmake/../third_party/gloo -isystem 
/<>/cmake/../third_party/googletest/googlemock/include -isystem 
/<>/cmake/../third_party/googletest/googletest/include -isystem 
/usr/include/opencv4 -isystem /usr/include/eigen3 -isystem 
/usr/include/python3.11 -isystem 
/usr/lib/python3/dist-packages/numpy/core/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -gsplit-dwarf 
-fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DUSE_PYTORCH_QNNPACK 
-DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 
-fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type 
-Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds 
-Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function 
-Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow 
-Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow 
-Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls 
-Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new 
-Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno 
-fno-trapping-math -Werror=format -Werror=cast-function-type 
-Wno-stringop-overflow -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION 
-O2 -g -DNDEBUG -fPIC -DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wno-unused-variable 
-fno-strict-aliasing -Wno-write-strings -Wno-strict-aliasing -std=gnu++14 -MD 
-MT caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o -MF 
caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o.d -o 
caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o -c 
/<>/torch/csrc/Stream.cpp
In file included from /usr/include/python3.11/Python.h:44,
 from /usr/include/pybind11/detail/common.h:266,
 from /usr/include/pybind11/attr.h:13,
 from /usr/include/pybind11/detail/class.h:12,
 from /usr/include/pybind11/pybind11.h:13,
 from /<>/torch/csrc/Stream.cpp:1:
/<>/torch/csrc/Stream.cpp: In function ‘void 
THPStream_init(PyObject*)’:
/<>/torch/csrc/Stream.cpp:112:3: error: lvalue required as left 
operand of assignment
  112 |   Py_TYPE() = _Type;
  |   ^~~
...

Bug#1027850: graph-tool FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: graph-tool
Version: 2.45+ds-9
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=graph-tool=amd64=2.45%2Bds-9%2Bb1=1672782255=0

...
TEST STARTED Tue Jan 3 21:43:53 UTC 2023
rm -f _BUILD/test.png
PYTHONPATH=/<>/debian/tmp//usr/lib/python3.11/dist-packages \
python3 -c "\
from graph_tool.all import *; \
show_config(); \
g = random_graph(10, lambda: 5, directed=False); \
graph_draw(g, output='_BUILD/test.png'); \
"
Matplotlib created a temporary config/cache directory at 
/tmp/matplotlib-vsfk88vs because the default path 
(/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is 
highly recommended to set the MPLCONFIGDIR environment variable to a writable 
directory, in particular to speed up the import of Matplotlib and to better 
support multiprocessing.
Traceback (most recent call last):
  File "", line 1, in 
  File 
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/graph_tool/generation/__init__.py",
 line 370, in random_graph
if len(inspect.getargspec(deg_sampler)[0]) > 0:
   ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
version: 2.45
gcc version: 12.2.0
compilation flags: -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -O3 
-fvisibility=default -fvisibility-inlines-hidden -Wno-deprecated -Wall -Wextra 
-ftemplate-backtrace-limit=0 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now
install prefix: /usr
python dir: /usr/lib/python3.11/dist-packages
graph filtering: True
openmp: True
uname: Linux x86-csail-01 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) 
x86_64
make[1]: *** [debian/rules:43: override_dh_auto_install] Error 1



https://docs.python.org/3/whatsnew/3.11.html

...
Removed from the inspect module:

The getargspec() function, deprecated since Python 3.0; use 
inspect.signature() or inspect.getfullargspec() instead.
https://docs.python.org/3/whatsnew/3.11.html

...

Processed: Bug#1027076 marked as pending in ruby-influxdb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1027076 [src:ruby-influxdb] ruby-influxdb: FTBFS with ruby-rspec 3.12: 
ERROR: Test "ruby3.1" failed.
Added tag(s) pending.

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

Bug#1027076: marked as pending in ruby-influxdb

[HIGUCHI Daisuke (VDR dai)]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-influxdb/-/commit/7f3abe667e7db7ecdd2bca8501d471b7fbaa


fix FTBFS with ruby-rspec-3.12 (Closes: #1027076)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027076

Bug#1027849: zeroc-ice FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: zeroc-ice
Version: 3.7.8-1
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/zeroc-ice/ice/pull/1394

https://buildd.debian.org/status/fetch.php?pkg=zeroc-ice=amd64=3.7.8-1%2Bb2=1672771157=0

...
modules/IcePy/Slice.cpp:17:10: fatal error: eval.h: No such file or directory
   17 | #include 
  |  ^~~~
compilation terminated.
make[3]: *** [Makefile:32: 
modules/IcePy/build/x86_64-linux-gnu/shared/pic/Slice.o] Error 1

Processed: Re: Bug#1027418: autopkgtest failure - iconv issue?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1027418 [src:hunspell-dict-ko] autopkgtest failure - iconv issue?
Severity set to 'normal' from 'serious'
> notfound -1 0.7.92-1
Bug #1027418 [src:hunspell-dict-ko] autopkgtest failure - iconv issue?
No longer marked as found in versions hunspell-dict-ko/0.7.92-1.

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

Bug#1027418: autopkgtest failure - iconv issue?

[Changwoo Ryu]

Control: severity -1 normal
Control: notfound -1 0.7.92-1

This bug appears to occur only in an incomplete chroot environment.

Please check your chroot again. You can reopen if it still occurs in a
general environment.

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Vagrant Cascadian wrote:
> On 2023-01-03, Vagrant Cascadian wrote:
>> On 2023-01-02, Vagrant Cascadian wrote:
>>> On 2023-01-02, Vagrant Cascadian wrote:
 On 2022-12-28, Vagrant Cascadian wrote:
> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
> commit triggering the issue has been identified as:
>
>   a9bf024b2933bba0e23038892970a18b72dfaeb4
>   efi_loader: disk: a helper function to create efi_disk objects from
>   udevice
>
> Workarounds I've heard are to disable EFI support for that board
>>> ...
 Obviously, it breaks EFI booting...

 Worst case, I suppose we could create two variants, one with EFI, one
 without...
>>>
>>> I have pushed a patch to git implementing an odroid-c2-noefi variant:
>>>
>>>   
>>> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>>>
>>> This would not close the bug, but at least downgrade the severity...
>>
>> I can confirm that 2023.01-rc4+dfsg-1 does boot successfully with EFI on
>> the odroid-c2, so ... the two variant solution is a viable one if a
>> proper fix cannot be figured out in time for bookworm.
>
> From irc.libera.chat #u-boot:
>
>  < xypron> Tartarus: Loading Ramdisk to 7a896000, end 7bf3eb78
>overwrites internal memory structures of the EFI subsystem
>which leads to the crash on the Odroid C2. Why do we copy
>initrd to high memory at all?
> 
>  < xypron> vagrantc: Tartarus: setenv initrd_high 0x;
>setenv fdt_high 0x solves the problem on the
>Odroid C2
>
> I can confirm this works around the issue, although it may also cause
> other problems and should not be the default...

Another possible workaround...

  < Tartarus> A less dangerous work-around would be to us bootm_low or
  bootm_size (See
  https://u-boot.readthedocs.io/en/latest/usage/environment.html)
  to limit where relocations can be

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Vagrant Cascadian wrote:
> On 2023-01-02, Vagrant Cascadian wrote:
>> On 2023-01-02, Vagrant Cascadian wrote:
>>> On 2022-12-28, Vagrant Cascadian wrote:
 The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
 produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
 commit triggering the issue has been identified as:

   a9bf024b2933bba0e23038892970a18b72dfaeb4
   efi_loader: disk: a helper function to create efi_disk objects from
   udevice

 Workarounds I've heard are to disable EFI support for that board
>> ...
>>> Obviously, it breaks EFI booting...
>>>
>>> Worst case, I suppose we could create two variants, one with EFI, one
>>> without...
>>
>> I have pushed a patch to git implementing an odroid-c2-noefi variant:
>>
>>   
>> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>>
>> This would not close the bug, but at least downgrade the severity...
>
> I can confirm that 2023.01-rc4+dfsg-1 does boot successfully with EFI on
> the odroid-c2, so ... the two variant solution is a viable one if a
> proper fix cannot be figured out in time for bookworm.

From irc.libera.chat #u-boot:

 < xypron> Tartarus: Loading Ramdisk to 7a896000, end 7bf3eb78
   overwrites internal memory structures of the EFI subsystem
   which leads to the crash on the Odroid C2. Why do we copy
   initrd to high memory at all?

 < xypron> vagrantc: Tartarus: setenv initrd_high 0x;
   setenv fdt_high 0x solves the problem on the
   Odroid C2

I can confirm this works around the issue, although it may also cause
other problems and should not be the default...

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Heinrich Schuchardt]

Hello Vagrant,

copying initrd to high memory overwrites internal EFI structures.

setenv initrd_high 0x
setenv fdt_high 0x

solves the problem on the Odroid C2.

Best regards

Heinrich

Bug#1027793: closed by Debian FTP Masters (reply to James McCoy ) (Bug#1027766: fixed in vim 2:9.0.1000-3)

[James McCoy]

On Tue, Jan 03, 2023 at 09:15:36PM +0100, Alejandro Colomar wrote:
> Hi,
> 
> On 1/3/23 17:09, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the vim-common package:
> > 
> > #1027793: vim: insert mode: Backspace doesn't do anything
> > 
> > It has been closed by Debian FTP Masters  
> > (reply to James McCoy ).
> > 
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Debian FTP Masters 
> >  (reply to James McCoy 
> > ) by
> > replying to this email.
> > 
> 
> For my own curiosity, would you mind pointing to the specific change that
> fixed this bug?

https://salsa.debian.org/vim-team/vim/-/commit/7bdf6feff01b77304c2d1a8af335bd57689b4c66

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1027847: libsigrokdecode FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: libsigrokdecode
Version: 0.5.3-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libsigrokdecode=amd64=0.5.3-3%2Bb1=1672741924=0

...
Detected libraries (required):
 - glib-2.0 >= 2.34 2.74.4
 - python-3.10-embed... no
 - python-3.9-embed no
 - python-3.8-embed no
...
/bin/bash ./libtool  --tag=CC   --mode=link gcc -std=c99 -fvisibility=hidden 
-Wall -Wextra -Wmissing-prototypes -Wshadow -Wformat=2 -Wno-format-nonliteral 
-Wfloat-equal -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.11 
-I/usr/include/x86_64-linux-gnu/python3.11  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,--as-needed -o tests/main 
tests/main-main.o tests/main-core.o tests/main-decoder.o tests/main-inst.o 
tests/main-session.o libsigrokdecode.la -lm -lcheck_pic -lrt -lm -lsubunit 
-lglib-2.0  
libtool: link: gcc -std=c99 -fvisibility=hidden -Wall -Wextra 
-Wmissing-prototypes -Wshadow -Wformat=2 -Wno-format-nonliteral -Wfloat-equal 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/python3.11 -I/usr/include/x86_64-linux-gnu/python3.11 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -o tests/.libs/main 
tests/main-main.o tests/main-core.o tests/main-decoder.o tests/main-inst.o 
tests/main-session.o  ./.libs/libsigrokdecode.so -lcheck_pic -lrt -lm -lsubunit 
-lglib-2.0 -pthread
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyModule_AddObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySys_GetObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyDict_SetItemString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_GenericNew'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyImport_Import'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBytes_AsStringAndSize'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallMethod'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyGILState_Release'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyBytes_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBool_FromLong'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyUnicode_FromString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallFunctionObjArgs'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_TypeError'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`Py_InitializeEx'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_Exception'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_Str'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Next'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyLong_AsLong'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyModule_AddIntConstant'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Format'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyFloat_FromDouble'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyArg_ParseTuple'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Occurred'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PySet_Pop'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_IsSubclass'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyArg_ParseTupleAndKeywords'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyFloat_Type'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_IndexError'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_InitThreads'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`_Py_FalseStruct'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_RestoreThread'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBytes_AsString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_FromSpec'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `_Py_TrueStruct'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_SaveThread'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySequence_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined 

Processed: reassign 1026781 to pkgconf

[Debian Bug Tracking System]

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

> # this bug is not present in pkg-config at all, only pkgconf
> reassign 1026781 pkgconf
Bug #1026781 [pkg-config] pkgconf: breaks adequate missing-pkgconfig-dependency 
check due to behaviour change in: pkg-config --exists --print-errors
Bug reassigned from package 'pkg-config' to 'pkgconf'.
No longer marked as found in versions 1.8.0-7.
Ignoring request to alter fixed versions of bug #1026781 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1027842: marked as done (displaycal-py3 FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 23:19:36 +
with message-id 
and subject line Bug#1027842: fixed in displaycal-py3 3.9.10-2
has caused the Debian Bug report #1027842,
regarding displaycal-py3 FTBFS with Python 3.11 as default version
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.)


-- 
1027842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: displaycal-py3
Version: 3.9.10-1
Severity: serious
Forwarded: https://github.com/eoyilmaz/displaycal-py3/issues/218

https://buildd.debian.org/status/fetch.php?pkg=displaycal-py3=ppc64el=3.9.10-1%2Bb1=1672726079=0

...
dh clean -Spybuild --with quilt
   dh_auto_clean -O-Spybuild
I: pybuild base:240: python3.11 setup.py clean 
/<>/setup.py:13: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
632 for potential alternatives
  from distutils.util import get_platform
['clean']
Traceback (most recent call last):
  File "/<>/DisplayCAL/defaultpaths.py", line 234, in 
set_translation
obj.translation = gettext.translation(
  
TypeError: translation() got an unexpected keyword argument 'codeset'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/setup.py", line 1583, in 
setup()
  File "/<>/setup.py", line 991, in setup
from DisplayCAL.setup import setup
  File "/<>/DisplayCAL/setup.py", line 70, in 
from DisplayCAL.defaultpaths import autostart, autostart_home
  File "/<>/DisplayCAL/defaultpaths.py", line 399, in 
if isinstance(attr, (str, list)):
   ^
  File "/<>/DisplayCAL/defaultpaths.py", line 303, in 
__getattribute__
object.__getattribute__(self, "init")()
  File "/<>/DisplayCAL/defaultpaths.py", line 380, in init
XDG.set_translation(self)
  File "/<>/DisplayCAL/defaultpaths.py", line 238, in 
set_translation
obj.translation = gettext.translation(
  
  File "/usr/lib/python3.11/gettext.py", line 531, in translation
raise FileNotFoundError(ENOENT,
FileNotFoundError: [Errno 2] No translation file found for domain: 
'xdg-user-dirs'
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:4: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: displaycal-py3
Source-Version: 3.9.10-2
Done: Christian Marillat 

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

Debian distribution maintenance software
pp.
Christian Marillat  (supplier of updated displaycal-py3 
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, 04 Jan 2023 00:08:59 +0100
Source: displaycal-py3
Architecture: source
Version: 3.9.10-2
Distribution: unstable
Urgency: medium
Maintainer: Christian Marillat 
Changed-By: Christian Marillat 
Closes: 1027842
Changes:
 displaycal-py3 (3.9.10-2) unstable; urgency=medium
 .
   * Add upstream patch to fix build with python 3.11 (Closes: #1027842)
Checksums-Sha1:
 3a92913f48f462bea8687347d5cdcd586b049e76 1944 displaycal-py3_3.9.10-2.dsc
 977af29c50ed075adb4124e83a3e9a1d696b585b 9796 
displaycal-py3_3.9.10-2.debian.tar.xz
 30081c6e44a249b3f355f6c60b913d74075679b8 7376 
displaycal-py3_3.9.10-2_source.buildinfo
Checksums-Sha256:
 545c333f9d79c85afb9d54e59bcf645131d0dda4b8bacd5cb7b112fad7290b18 1944 
displaycal-py3_3.9.10-2.dsc
 2741258f86c6ad1d6a6afb96409730aa7f0ccb2034d971e093599e958712b743 9796 
displaycal-py3_3.9.10-2.debian.tar.xz
 a1251f4e386e7d2518e43cfab5e769e7a200c0981f6b94f628b017b7660441fc 7376 
displaycal-py3_3.9.10-2_source.buildinfo
Files:
 b82c821efd255a53e0e29c4ef99af726 1944 graphics optional 
displaycal-py3_3.9.10-2.dsc
 7b850815a1458fc111ea3e4b0bad7dbc 9796 graphics optional 
displaycal-py3_3.9.10-2.debian.tar.xz
 

Bug#1026539: theano FTBFS

[Rebecca N. Palmer]

Please do *not* upload theano 1.12 to unstable - it's the Aesara 
version, which may seriously break backward compatibility.


I haven't had time to properly look at this bug yet.

Bug#1027843: libgnatcoll-bindings FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: libgnatcoll-bindings
Version: 23.0.0-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libgnatcoll-bindings=ppc64el=23.0.0-3%2Bb1=1672725764=0

...
/<>/python3/python_support.c: In function ‘ada_pyframe_get_code’:
/<>/python3/python_support.c:817:14: error: invalid use of 
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
  817 |return obj->f_code;
  |  ^~
/<>/python3/python_support.c: In function ‘ada_pyframe_get_back’:
/<>/python3/python_support.c:823:14: error: invalid use of 
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
  823 |return obj->f_back;
  |  ^~

   compilation of python_support.c failed

gprbuild: *** compilation phase failed

Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

[Andreas Henriksson]

On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote:
> On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> > rpi_4
> > rpi_4_32b
> 
> I dug up my old dusty rpi4 which I probably haven't touched
> since last time we spoke about u-boot on it.
> 
> 
> I've tested only the 64bit (arm64) version so far.
[...]
> I upgraded only u-boot.bin from bookworm/sid/experimental
[...]
> The unstable and experimental versions both caused a reset
> after run bootcmd and before "Starting Linux...".
[...]


After upgrading rpi firmware files to latest release/tag
also the unstable and experimental u-boot seemed to boot
fine (no reset, garbage on console after linux started).


### unstable u-boot with rpi firmware-1.20221104.tar.gz

U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
Core:  209 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, mmc@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... 
In:serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:  Debian GNU/Linux 5.7.0-1-arm64
2:  Debian GNU/Linux 5.7.0-1-arm64 (rescue target)
Enter choice: 1:Debian GNU/Linux 5.7.0-1-arm64
Retrieving file: /boot/initrd.img-5.7.0-1-arm64   
Retrieving file: /boot/vmlinuz-5.7.0-1-arm64
append: root=LABEL=root ro rootwait console=ttyS1,115200
Retrieving file: /usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb
## Flattened Device Tree blob at 0260
   Booting using the fdt blob at 0x260
   Using Device Tree in place at 0260, end 0260896e

Starting kernel ...

[... garbage characters...]


### experimental u-boot with rpi firmware-1.20221104.tar.gz

U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)

DRAM:  948 MiB (effective 3.9 GiB)
RPI 4 Model B (0xc03111)
Core:  209 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, mmc@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In:serial  
Out:   serial  
Err:   serial  
Net:   eth0: ethernet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00  
scanning bus xhci_pci for devices... 2 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
U-Boot>
U-Boot>
U-Boot>
U-Boot> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:  Debian GNU/Linux 5.7.0-1-arm64
2:  Debian GNU/Linux 5.7.0-1-arm64 (rescue target)
Enter choice: 1:Debian GNU/Linux 5.7.0-1-arm64
Retrieving file: /boot/initrd.img-5.7.0-1-arm64
Retrieving file: /boot/vmlinuz-5.7.0-1-arm64
append: root=LABEL=root ro rootwait console=ttyS1,115200
Retrieving file: 
/usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb  
## Flattened Device Tree blob at 0260
   Booting using the fdt blob at 0x260
Working FDT set to 260
   Using Device Tree in place at 0260, end 0260896e
Working FDT set to 260

Starting kernel ...

[...garbage characters...]


Regards,
Andreas Henriksson

Bug#1027842: displaycal-py3 FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: displaycal-py3
Version: 3.9.10-1
Severity: serious
Forwarded: https://github.com/eoyilmaz/displaycal-py3/issues/218

https://buildd.debian.org/status/fetch.php?pkg=displaycal-py3=ppc64el=3.9.10-1%2Bb1=1672726079=0

...
dh clean -Spybuild --with quilt
   dh_auto_clean -O-Spybuild
I: pybuild base:240: python3.11 setup.py clean 
/<>/setup.py:13: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
632 for potential alternatives
  from distutils.util import get_platform
['clean']
Traceback (most recent call last):
  File "/<>/DisplayCAL/defaultpaths.py", line 234, in 
set_translation
obj.translation = gettext.translation(
  
TypeError: translation() got an unexpected keyword argument 'codeset'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/setup.py", line 1583, in 
setup()
  File "/<>/setup.py", line 991, in setup
from DisplayCAL.setup import setup
  File "/<>/DisplayCAL/setup.py", line 70, in 
from DisplayCAL.defaultpaths import autostart, autostart_home
  File "/<>/DisplayCAL/defaultpaths.py", line 399, in 
if isinstance(attr, (str, list)):
   ^
  File "/<>/DisplayCAL/defaultpaths.py", line 303, in 
__getattribute__
object.__getattribute__(self, "init")()
  File "/<>/DisplayCAL/defaultpaths.py", line 380, in init
XDG.set_translation(self)
  File "/<>/DisplayCAL/defaultpaths.py", line 238, in 
set_translation
obj.translation = gettext.translation(
  
  File "/usr/lib/python3.11/gettext.py", line 531, in translation
raise FileNotFoundError(ENOENT,
FileNotFoundError: [Errno 2] No translation file found for domain: 
'xdg-user-dirs'
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:4: clean] Error 25

Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

[Andreas Henriksson]

On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> rpi_4
> rpi_4_32b

I dug up my old dusty rpi4 which I probably haven't touched
since last time we spoke about u-boot on it.


I've tested only the 64bit (arm64) version so far.

The version that was on the sd-card since last time:
U-Boot> ver
U-Boot 2020.07+dfsg-1 (Jul 08 2020 - 23:29:02 +)

gcc (Debian 9.3.0-14) 9.3.0
GNU ld (GNU Binutils for Debian) 2.34.90.20200706
U-Boot> 


I upgraded only u-boot.bin from bookworm/sid/experimental
on the firmware partition (nothing else touched, and I'm not
really sure what state it was in since last time but probably
a bootable system atleast).

Testing/bookworm u-boot.bin seems to boot fine (although
serial console became garbage after Linux started, but
it seemed to run but I didn't investigate much).

The unstable and experimental versions both caused a reset
after run bootcmd and before "Starting Linux...".
U-Boot itself seemed to run fine though, it was running bootcmd
that caused the reset. Maybe I need to upgrade the rpi firmware,
or maybe it's related to what else is on the old sd-card that
was in the box.


# testing u-boot

U-Boot> ver
U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +)

gcc (Debian 11.3.0-1) 11.3.0
GNU ld (GNU Binutils for Debian) 2.38
U-Boot> 

# unstable u-boot

U-Boot> ver
U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)

gcc (Debian 12.2.0-10) 12.2.0
GNU ld (GNU Binutils for Debian) 2.39.50.20221208
U-Boot> 




U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
Core:  135 devices, 14 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, emmc2@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from
mmc0:1...
In:serial
Out:   serial
Err:   serial
Net:   eth0: genet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (!SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
Port not available.
Hit any key to stop autoboot:  0
"Synchronous Abort" handler, esr 0x9644
elr: 0009f3a8 lr : 0009572c (reloc)
elr: 3b36c3a8 lr : 3b36272c
x0 : 3af52610 x1 : 3af52680
x2 : 0051 x3 : 6964003b6963765f
x4 : 3b3d0890 x5 : 3b3d0890
x6 : 005b x7 : 3b3d0e30
x8 : 3b3d0820 x9 : 0008
x10: fff0 x11: 0006
x12: 0001869f x13: 3af3e708
x14: 3af3e810 x15: 
x16: 3b36d548 x17: 596fcb0297bbddff
x18: 3af48d70 x19: 0071
x20: 3b3d0880 x21: 
x22: 0005 x23: 000a
x24: 0001 x25: 3b3e4cd8
x26:  x27: 3b3c4851
x28: 006d x29: 3af3d9e0

Code: a9410803 8b130001 b2400273 f9000413 (f9000c62)
Resetting CPU ...

resetting ...










# experimental u-boot


U-Boot> ver
U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)

gcc (Debian 12.2.0-10) 12.2.0
GNU ld (GNU Binutils for Debian) 2.39.50.20221208
U-Boot> 

U-Boot> run bootcmd
"Synchronous Abort" handler, esr 0x9644
elr: 0009f7e0 lr : 00095e0c (reloc)
elr: 3b36c7e0 lr : 3b362e0c
x0 : 3af59470 x1 : 3af59490
x2 : 30636d6d x3 : 5f646d63746f6f00
x4 : 0070 x5 : 3b3d0e08
x6 : 005b x7 : 3b3d13a8
x8 : 0050 x9 : 0008
x10: fff0 x11: 0006
x12: 0001869f x13: 3af3e708
x14: 3af3e810 x15: 
x16: 3b36d994 x17: d9ff4b22fffbdcff
x18: 3af48d70 x19: 0021
x20: 3b3d0df8 x21: 3af59d80
x22: 3af59b20 x23: 0010
x24: 0008 x25: 3b3e5258
x26: 0002 x27: 3b3c4e54
x28: 0073 x29: 3af3da10

Code: a9410803 8b130001 b2400273 f9000413 (f9000c62) 
Resetting CPU ...

resetting ...


U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +)
[...]

Bug#1027839: createrepo-c FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: createrepo-c
Version: 0.17.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=createrepo-c=ppc64el=0.17.3-1%2Bb1=1672726045=0

...
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.11.1", 
minimum required is "3") 
-- Found PythonLibs: /usr/lib/powerpc64le-linux-gnu/libpython3.11.so (found 
suitable version "3.11.1", minimum required is "3") 
-- Python install dir is /usr/lib/python3/dist-packages
:1: DeprecationWarning: path is deprecated. Use files() instead. Refer 
to 
https://importlib-resources.readthedocs.io/en/latest/using.html#migrating-from-legacy
 for migration advice.
Traceback (most recent call last):
  File "", line 1, in 
TypeError: unsupported operand type(s) for /: '_GeneratorContextManager' and 
'str'
-- Python skbuild CMake dir is 
CMake Error at src/python/CMakeLists.txt:65 (find_package):
  By not providing "FindPythonExtensions.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "PythonExtensions", but CMake did not find one.

  Could not find a package configuration file provided by "PythonExtensions"
  with any of the following names:

PythonExtensionsConfig.cmake
pythonextensions-config.cmake

  Add the installation prefix of "PythonExtensions" to CMAKE_PREFIX_PATH or
  set "PythonExtensions_DIR" to a directory containing one of the above
  files.  If "PythonExtensions" provides a separate development package or
  SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!




The problem seems to come from debian/patches/python-skbuild-path.patch

Bug#1027837: offlineimap3: "AssertionError: Your sqlite is not multithreading safe" with python3.11

[Simon McVittie]

Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-1
Severity: grave
Tags: fixed-upstream patch
Justification: renders package unusable
Forwarded: https://github.com/OfflineIMAP/offlineimap3/issues/136
Control: block 1026825 by -1

After upgrading to python3 (>= 3.11) I get lots of these errors:

> ERROR: ERROR in syncfolder for REDACTED folder .REDACTED: Traceback (most 
> recent call last):
>   File "/usr/share/offlineimap3/offlineimap/accounts.py", line 610, in 
> syncfolder
> statusfolder.openfiles()
>   File "/usr/share/offlineimap3/offlineimap/folder/LocalStatusSQLite.py", 
> line 107, in openfiles
> assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.'
>
> AssertionError: Your sqlite is not multithreading safe

and as far as I can tell, no mail is synchronized.
https://github.com/OfflineIMAP/offlineimap3/pull/139 appears to be the
upstream solution for this, and seems to be a suitable patch for the
version currently in Debian. Please see attached or the upstream PR.

smcv

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

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

Versions of packages offlineimap3 depends on:
ii  ca-certificates   20211016
ii  python3   3.11.1-1
ii  python3-distro1.8.0-1
ii  python3-imaplib2  2.57-5.2

offlineimap3 recommends no packages.

Versions of packages offlineimap3 suggests:
pn  python3-gssapi  

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/share/offlineimap3/offlineimap/folder/LocalStatusSQLite.py (from 
offlineimap3 package)
>From 7cd32cf834b34a3d4675b29bebcd32dc1e5ef128 Mon Sep 17 00:00:00 2001
From: 0pointerexception 
Date: Thu, 17 Nov 2022 19:43:58 +0100
Subject: [PATCH] LocalStatusSQLite.py: Python 3.11 compatible threadsafety
 check

Signed-off-by: 0pointerexception 
---
 offlineimap/folder/LocalStatusSQLite.py | 10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/offlineimap/folder/LocalStatusSQLite.py b/offlineimap/folder/LocalStatusSQLite.py
index a576b9ca..3c44643f 100644
--- a/offlineimap/folder/LocalStatusSQLite.py
+++ b/offlineimap/folder/LocalStatusSQLite.py
@@ -17,7 +17,7 @@
 
 import os
 import sqlite3 as sqlite
-from sys import exc_info
+from sys import exc_info,version_info
 from threading import Lock
 from .Base import BaseFolder
 
@@ -75,6 +75,11 @@ def __init__(self, name, repository):
 self.filename = os.path.join(self.getroot(), self.getfolderbasename())
 
 self._newfolder = False  # Flag if the folder is new.
+"""
+sqlite threading mode must be 3 as of Python 3.11, checking against
+1 for versions below Python 3.11 to sustain backwards compatibility.
+"""
+self._threading_mode_const = 3 if version_info.minor >=11 else 1
 
 dirname = os.path.dirname(self.filename)
 if not os.path.exists(dirname):
@@ -102,9 +107,10 @@ def __exit__(self, exc_type, exc_val, exc_tb):
 if self._in_transactions < 1:
 self.connection.commit()
 
+
 def openfiles(self):
 # Make sure sqlite is in multithreading SERIALIZE mode.
-assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.'
+assert sqlite.threadsafety == self._threading_mode_const, 'Your sqlite is not multithreading safe.'
 
 with self._databaseFileLock.getLock():
 # Try to establish connection, no need for threadsafety in __init__.

Processed: offlineimap3: "AssertionError: Your sqlite is not multithreading safe" with python3.11

[Debian Bug Tracking System]

Processing control commands:

> block 1026825 by -1
Bug #1026825 [release.debian.org] python3.11 as default
1026825 was not blocked by any bugs.
1026825 was not blocking any bugs.
Added blocking bug(s) of 1026825: 1027837

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

Processed: severity of 1027811 is serious

[Debian Bug Tracking System]

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

> severity 1027811 serious
Bug #1027811 [libcifpp-data] libcifpp-data: uninstallable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1027836: planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png

[Andreas Beckmann]

Package: planner,planner-data
Version: 0.14.91-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages failed to install
because they tries to overwrite each others files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package planner.
  Preparing to unpack .../101-planner_0.14.91-1_amd64.deb ...
  Unpacking planner (0.14.91-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/planner/images/gnome-planner.png', which is 
also in package planner-data 0.14.91-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb


cheers,

Andreas


planner=0.14.91-1_planner-data=0.14.91-1.log.gz
Description: application/gzip

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

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 21:23:58 +
with message-id 
and subject line Bug#1027590: fixed in ufolib2 0.14.0+dfsg1-1
has caused the Debian Bug report #1027590,
regarding ufolib2: 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.)


-- 
1027590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ufolib2
Version: 0.13.1+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --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_ufoLib2 
> * Building wheel...
> /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)
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/ufoLib2
> copying src/ufoLib2/__init__.py -> build/lib/ufoLib2
> copying src/ufoLib2/converters.py -> build/lib/ufoLib2
> copying src/ufoLib2/errors.py -> build/lib/ufoLib2
> copying src/ufoLib2/typing.py -> build/lib/ufoLib2
> copying src/ufoLib2/constants.py -> build/lib/ufoLib2
> copying src/ufoLib2/_version.py -> build/lib/ufoLib2
> creating build/lib/ufoLib2/pointPens
> copying src/ufoLib2/pointPens/__init__.py -> build/lib/ufoLib2/pointPens
> copying src/ufoLib2/pointPens/glyphPointPen.py -> build/lib/ufoLib2/pointPens
> creating build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/__init__.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/point.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/dataSet.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/layerSet.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/glyph.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/kerning.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/lib.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/imageSet.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/anchor.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/contour.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/font.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/image.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/misc.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/guideline.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/layer.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/features.py -> build/lib/ufoLib2/objects
> copying src/ufoLib2/objects/component.py -> build/lib/ufoLib2/objects
> creating build/lib/ufoLib2/objects/info
> copying src/ufoLib2/objects/info/__init__.py -> build/lib/ufoLib2/objects/info
> copying src/ufoLib2/objects/info/woff.py -> build/lib/ufoLib2/objects/info
> copying src/ufoLib2/py.typed -> build/lib/ufoLib2
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/ufoLib2
> copying build/lib/ufoLib2/__init__.py -> 
> build/bdist.linux-x86_64/wheel/ufoLib2
> copying build/lib/ufoLib2/converters.py -> 
> build/bdist.linux-x86_64/wheel/ufoLib2
> copying build/lib/ufoLib2/errors.py -> build/bdist.linux-x86_64/wheel/ufoLib2
> copying build/lib/ufoLib2/py.typed -> build/bdist.linux-x86_64/wheel/ufoLib2
> copying build/lib/ufoLib2/typing.py -> build/bdist.linux-x86_64/wheel/ufoLib2
> creating build/bdist.linux-x86_64/wheel/ufoLib2/pointPens
> copying build/lib/ufoLib2/pointPens/__init__.py -> 
> build/bdist.linux-x86_64/wheel/ufoLib2/pointPens
> copying build/lib/ufoLib2/pointPens/glyphPointPen.py -> 
> build/bdist.linux-x86_64/wheel/ufoLib2/pointPens
> creating build/bdist.linux-x86_64/wheel/ufoLib2/objects
> copying 

Bug#1016978: marked as done (frr: CVE-2022-37035)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 21:19:57 +
with message-id 
and subject line Bug#1016978: fixed in frr 8.4.1-1
has caused the Debian Bug report #1016978,
regarding frr: CVE-2022-37035
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.)


-- 
1016978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frr
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for frr.

CVE-2022-37035[0]:
| An issue was discovered in bgpd in FRRouting (FRR) 8.3. In
| bgp_notify_send_with_data() and bgp_process_packet() in bgp_packet.c,
| there is a possible use-after-free due to a race condition. This could
| lead to Remote Code Execution or Information Disclosure by sending
| crafted BGP packets. User interaction is not needed for exploitation.

https://github.com/FRRouting/frr/issues/11698

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-37035
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37035

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: frr
Source-Version: 8.4.1-1
Done: David Lamparter 

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

Debian distribution maintenance software
pp.
David Lamparter  (supplier of updated frr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 02 Jan 2023 14:46:06 +0100
Source: frr
Architecture: source
Version: 8.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: David Lamparter 
Changed-By: David Lamparter 
Closes: 981139 132 1008010 1016978 1017518 1021016
Changes:
 frr (8.4.1-1) unstable; urgency=medium
 .
   * New upstream release FRR 8.4.1 (closes: #1017518)
   * New frr@ systemd service unit to run inside network namespace
   * egrep to grep -E
   * upstream fix ospfd crash (PR 8876) (closes: #981139)
   * upstream fix isisd parsing issues CVE-2022-26125, CVE-2022-26126 and
 babeld parsing issues CVE-2022-26127, CVE-2022-26128, CVE-2022-26129
 (closes: #1008010)
   * upstream fix bgpd out-of-bounds read CVE-2022-37032 (closes: #1021016)
   * upstream fix bgpd UAF CVE-2022-37035 (closes: #1016978)
   * libyang-related pcre3 dep replaced with pcre2 (closes: #132)
   * disable ELF magic on mips64el
   * fixed texinfo figure installation directory
   * enable dh_sphinxdoc to get rid of embedded javascript in frr-doc
   * removed bogus iproute dependency choice
Checksums-Sha1:
 93bae7678f788c5ee86ea262745a91a073e0bf1c 2081 frr_8.4.1-1.dsc
 472086fd79f5414154414886adab471ae0e0 7294592 frr_8.4.1.orig.tar.xz
 a20d8187f8af45d819e2f4260490371dec3a4d08 31052 frr_8.4.1-1.debian.tar.xz
 7c3066168a1d3f2360de1f30254ffc1e0fabf173 10675 frr_8.4.1-1_amd64.buildinfo
Checksums-Sha256:
 394f5bc223fd1a713fdee0624a42d730ab07cfa5a6b99bc6445050d05351fff5 2081 
frr_8.4.1-1.dsc
 cfce29dbb52817c2185861152a262e48b33beba8a21e3f4cbfb9153822e433bf 7294592 
frr_8.4.1.orig.tar.xz
 8687b112475716e9686067528a0675abdb77ebf5164d7e0659c72c76295d0537 31052 
frr_8.4.1-1.debian.tar.xz
 80632fd78365c569b469bfa5c1b8ce0b5d780a8913054deba4331fb8e03f16c7 10675 
frr_8.4.1-1_amd64.buildinfo
Files:
 c22726da7b40b909f6e56f9b1497b298 2081 net optional frr_8.4.1-1.dsc
 fe4024888b8129dacceb07cb5ec17012 7294592 net optional frr_8.4.1.orig.tar.xz
 1610f03c1032e11b421ca168fec7c8ca 31052 net optional frr_8.4.1-1.debian.tar.xz
 021bfbb479728254bb6d31039715eacb 10675 net optional frr_8.4.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCY7SYgQAKCRDLPsM64d7X
gfJbAP4rRTt+LIMfViPQCOjT9SV2c/KrdVvg/1HWFD87bF1B5wD8CEhzG388yRY4
OlG2pQSp3ookCeYheRwmz3N7gxFinQs=
=CP3D
-END PGP SIGNATURE End Message ---

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Frédéric Danis wrote:
> On 03/01/2023 18:55, Vagrant Cascadian wrote:
>> On 2023-01-03, Frédéric Danis wrote:
>>> Afaiu, the bug is not reproducible with unstable and experimental
>>> versions, but boot crash before starting the kernel, see
>>> lepotato-unstable.txt and lepotato-experimental.txt.
>> Sounds like the bug *is* reproducible with unstable and experiemental
>> versions, from reading the logs; looks like the same issue with
>> odroid-c2.
>>
>> Could you try building a "noefi" variant, like done with odroid-c2, and
>> test for the lepotato (libretech-cc?):
>>
>>
>> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>
> I will try to build and test this
>
>> Could you also test EFI booting with the versions from unstable and
>> experimental to see if they can load a kernel? If EFI does work, that
>> justifies building two variants with and without EFI... it is a bit ugly
>> to produce two variants, but it's the easiest known workaround for
>> now...
>
> I will need your help on this as I don't know how to test EFI boot, for 
> me EFI was specific to Intel platforms.
> Can you point me to a doc explaining how to do this on LePotato/Arm board?

What I did for the odroid-c2 was download the debian-installer mini.iso:

  https://d-i.debian.org/daily-images/arm64/daily/netboot/

And dump it onto a USB stick. Then at boot, I interrupted the boot
process, and at the u-boot prompt:

  setenv boot_targets usb0
  boot

This of course presumes usb works for your platform.

You might be able to do a dance with microSD or whatever by booting from
microSD, yanking the microSD card, inserting a microSD card with the
mini.iso installed, rescanning the mmc bus, etc. but that is obviously a
lot tricker!

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-02, Vagrant Cascadian wrote:
> On 2023-01-02, Vagrant Cascadian wrote:
>> On 2022-12-28, Vagrant Cascadian wrote:
>>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>>> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
>>> commit triggering the issue has been identified as:
>>>
>>>   a9bf024b2933bba0e23038892970a18b72dfaeb4
>>>   efi_loader: disk: a helper function to create efi_disk objects from
>>>   udevice
>>>
>>> Workarounds I've heard are to disable EFI support for that board
> ...
>> Obviously, it breaks EFI booting...
>>
>> Worst case, I suppose we could create two variants, one with EFI, one
>> without...
>
> I have pushed a patch to git implementing an odroid-c2-noefi variant:
>
>   
> https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d
>
> This would not close the bug, but at least downgrade the severity...

I can confirm that 2023.01-rc4+dfsg-1 does boot successfully with EFI on
the odroid-c2, so ... the two variant solution is a viable one if a
proper fix cannot be figured out in time for bookworm.


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: limit source to pam, tagging 1022952, tagging 460232, tagging 1024645

[Debian Bug Tracking System]

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

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

> tags 1022952 + pending
Bug #1022952 [libpam-runtime] pam-auth-update ignores --root for 
/usr/share/pam-configs
Added tag(s) pending.
> tags 460232 + pending
Bug #460232 [pam] Please clarify license
Added tag(s) pending.
> tags 1024645 + pending
Bug #1024645 [src:pam] pam: explicitly build depend on libcrypt-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1023686: readline: Inaccurate copyright file

[Bastian Germann]

I am uploading a NMU with the attached debdiff to DELAYED/10 in order to 
address this.diff -Nru readline-8.2/debian/changelog readline-8.2/debian/changelog
--- readline-8.2/debian/changelog   2022-11-11 07:37:10.0 +0100
+++ readline-8.2/debian/changelog   2023-01-03 21:49:45.0 +0100
@@ -1,3 +1,11 @@
+readline (8.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert d/copyright to machine-readable format, adding missing info.
+(Closes: #1023686)
+
+ -- Bastian Germann   Tue, 03 Jan 2023 21:49:45 +0100
+
 readline (8.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru readline-8.2/debian/copyright readline-8.2/debian/copyright
--- readline-8.2/debian/copyright   2016-02-06 12:26:16.0 +0100
+++ readline-8.2/debian/copyright   2023-01-03 21:49:00.0 +0100
@@ -1,68 +1,99 @@
-This is Debian GNU/Linux's prepackaged version of the FSF's GNU
-Readline library.
-
-This package was put together by Matthias Klose , derived
-from the bash package by Guy Maor , from the GNU sources at
-
-   ftp.gnu.org:/pub/gnu/readline/readline-6.0.tar.gz.
-
-Upstream Authors:
-
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+This is Debian GNU/Linux's prepackaged version of the FSF's GNU
+Readline library.
+ .
+This package was put together by Matthias Klose ,
+derived from the bash package by Guy Maor .
+Upstream-Name: Readline
+Upstream-Contact: 
 Chet Ramey 
 Jeff Solomon  (examples/excallback.c)
 Harold Levy  (examples/rl-fgets.c)
-Juergen Weigert  (examples/rlfe)
-Michael Schroeder  
(examples/rlfe)
-Oliver Laumann (examples/rlfe)
+Source: http://ftp.gnu.org/gnu/readline/
 
+Files: *
 Copyright:
-
-Copyright (C) 1987-2009 Free Software Foundation, Inc.
-Copyright (C) 1999 Jeff Solomon (examples/excallback.c)
-Copyright (C) 2003-2004 Harold Levy (examples/rl-fgets.c)
-Copyright (C) 1993-2002 Juergen Weigert (examples/rlfe)
-Copyright (C) 1993-2002 Michael Schroeder (examples/rlfe)
-Copyright (C) 1987 Oliver Laumann (examples/rlfe)
-
-License:
-
+Copyright (C) 1987-2022 Free Software Foundation, Inc.
+License: GPL-3+
 Readline 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 of the License, or
 (at your option) any later version.
-
+ .
 This package 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 Readline.  If not, see .
+Comment:
+ On Debian systems, the complete text of the GNU General Public License
+ version 3 can be found in `/usr/share/common-licenses/GPL-3'.
+
+Files: examples/readlinebuf.h
+   examples/rl-fgets.c
+   examples/rlfe/*
+   examples/rlwrap-*.tar.gz
+Copyright:
+Copyright (C) 1987-2022 Free Software Foundation, Inc.
+Copyright (c) 2001 by Dimitris Vyzovitis [v...@media.mit.edu]
+Copyright (C) 1999 Jeff Solomon (examples/excallback.c)
+Copyright (C) 2003-2004 Harold Levy (examples/rl-fgets.c)
+Copyright (c) 1993-2002 Juergen Weigert 
(jnwei...@immd4.informatik.uni-erlangen.de)
+Copyright (c) 1993-2002 Michael Schroeder 
(mlsch...@immd4.informatik.uni-erlangen.de)
+Copyright (C) 1987 Oliver Laumann (examples/rlfe)
+Copyright (C) 2004, 1999 Per Bothner
+Copyright (C) 2000-2007 Hans Lub
+Copyright (C) 1999-2001 Geoff Wing
+Copyright (C) Damian Ivereigh 2000
+License: GPL-2+
+This program 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 2, or (at your option)
+any later version.
+ .
+This program 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 this program (see the file COPYING); if not, write to the
+Free Software Foundation, Inc.,
+59 Temple Place - Suite 330, Boston, MA  02111-1307, USA
+Comment:
+ On Debian systems, the complete text of the GNU General Public License
+ version 2 can be found in `/usr/share/common-licenses/GPL-2'.
+ .
+ The rlwrap example is also available in its own Debian package.
+ The code copyrighted by Damian Ivereigh is licensed under LGPL-2.1+.
 
-examples/rl-fgets.c: GPL v2 or later.
-examples/rlfe: GPL v2 or later.
-
-On Debian systems, the complete text 

Processed: retitle 1027824 to vim FTBFS on IPV6-only buildds

[Debian Bug Tracking System]

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

> retitle 1027824 vim FTBFS on IPV6-only buildds
Bug #1027824 [src:vim] FTBFS: hanging testsuite: build killed after time of 
inactivity on buildds
Changed Bug title to 'vim FTBFS on IPV6-only buildds' from 'FTBFS: hanging 
testsuite: build killed after time of inactivity on buildds'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:8.2.4793-1
Bug #1027824 [src:vim] FTBFS: hanging testsuite: build killed after time of 
inactivity on buildds
Marked as found in versions vim/2:8.2.4793-1.

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

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Adrian Bunk]

Control: found -1 2:8.2.4793-1
ontrol: retitle -1 vim FTBFS on IPV6-only buildds

On Tue, Jan 03, 2023 at 09:15:03PM +0100, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Tue, Jan 03, 2023 at 09:03:27PM +0100, Salvatore Bonaccorso wrote:
> > Source: vim
> > Version: 2:9.0.1000-2
> > Severity: serious
> > Tags: ftbfs
> > Justification: ftbfs
> > X-Debbugs-Cc: car...@debian.org
> > 
> > Hi James,
> > 
> > Severity might not be warranted, please downgrade if you think it's
> > needed.
> > 
> > I noticed on the last two vim builds that the amd64 build failed,
> > giving it back helped most of the times. The last upload failed as
> > well:
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=vim=amd64=2%3A9.0.1000-3=1672773526=0
> 
> Looking at the older build failures from
> https://buildd.debian.org/status/logs.php?pkg=vim=amd64 it looks
> it was always on x86-conova-01 when it failed.

The test seems to fail on IPV6-only buildds, I suspect something might 
go wrong with the usage of "localhost" in this test without IPV4?

> Regards,
> Salvatore

cu
Adrian

Bug#1026328: libbpp-core breaks bppsuite autopkgtest

[Andreas Tille]

Hi,

when looking at

  https://ci.debian.net/packages/b/bppsuite/unstable/arm64/

I'm wondering why you assume that libbpp-core/2.4.1-9 is responsible
for the failure.  IMHO it is rather gcc-13 where the failure is
happening.  The change


libbpp-core (2.4.1-9) unstable; urgency=medium

  * Fix watch file

 -- Andreas Tille   Tue, 06 Dec 2022 19:54:08 +0100


is hardly responsible for the observed failure.

Kind regards
   Andreas.


-- 
http://fam-tille.de

Bug#1027828: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Santiago Vila]

Package: src:macromoleculebuilder
Version: 3.2+dfsg-2
Severity: serious
Tags: ftbfs
Control: fixed -1 4.0.0+dfsg-2

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf parameterization/build
dh_auto_configure -- \
-DOpenMM_INCLUDE_DIR=/usr/include \
-DCMAKE_CXX_FLAGS="-D BuildNtC -D USE_OPENMM -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O0"
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOpenMM_INCLUDE_DIR=/usr/include 
"-DCMAKE_CXX_FLAGS=-D BuildNtC -D USE_OPENMM -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O0" ..
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- 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
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_SYSCONFDIR


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
   dh_auto_build -i
cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/MMBlib.dir/build.make CMakeFiles/MMBlib.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/DependInfo.cmake --color=
Dependee "/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/DependInfo.cmake" is newer than 
depender "/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/depend.internal".
Dependee "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeDirectoryInformation.cmake" is newer 
than depender "/<>/obj-x86_64-linux-gnu/CMakeFiles/MMBlib.dir/depend.internal".
Scanning dependencies of target MMBlib
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/MMBlib.dir/build.make CMakeFiles/MMBlib.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  3%] Building CXX object CMakeFiles/MMBlib.dir/src/Utils.cpp.o
/usr/bin/c++ -DMMBlib_EXPORTS -I/<>/include -I/usr/include/openmm 
-I/usr/include/openmm/reference -isystem /usr/include/simbody -D BuildNtC -D USE_OPENMM -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 
-fPIC -DMMB_BUILDING_SHARED_LIBRARY -o CMakeFiles/MMBlib.dir/src/Utils.cpp.o -c 
/<>/src/Utils.cpp
In file included from /<>/src/Utils.cpp:11:
/<>/include/Utils.h:33:70: note: ‘#pragma message: using 
OpenMM::Vec3: USE_OPENMM_REALVEC NOT defined’
   33 | #pragma message ("using OpenMM::Vec3: USE_OPENMM_REALVEC NOT defined")
  |  ^
/<>/src/Utils.cpp: In function ‘int ValidateNonNegativeInt(int)’:
/<>/src/Utils.cpp:526:1: warning: control reaches end of non-void 
function [-Wreturn-type]
  526 | }
  | ^
[  6%] Building CXX object CMakeFiles/MMBlib.dir/src/BiopolymerClass.cpp.o
/usr/bin/c++ -DMMBlib_EXPORTS -I/<>/include -I/usr/include/openmm 
-I/usr/include/openmm/reference -isystem /usr/include/simbody -D BuildNtC -D USE_OPENMM -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 
-fPIC -DMMB_BUILDING_SHARED_LIBRARY -o CMakeFiles/MMBlib.dir/src/BiopolymerClass.cpp.o -c 
/<>/src/BiopolymerClass.cpp
In file included from /<>/include/Mutation.h:4,
 from /<>/include/BiopolymerClass.h:18,
 from 

Processed: macromoleculebuilder: FTBFS in bullseye (a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.0.0+dfsg-2
Bug #1027828 [src:macromoleculebuilder] macromoleculebuilder: FTBFS in bullseye 
(a2x: ERROR: "xsltproc" [...] returned non-zero exit status 5)
Marked as fixed in versions macromoleculebuilder/4.0.0+dfsg-2.

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

Bug#1027827: litecoin: FTBFS in bullseye (expired certificates in test suite)

[Santiago Vila]

Package: src:litecoin
Version: 0.18.1-1.1
Severity: serious
Tags: ftbfs
Control: fixed -1 0.21.2.1-1

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a

[...]

Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : PaymentServerTests::initTestCase()
QDEBUG : PaymentServerTests::paymentServerTests() 
PaymentServer::initNetManager: No active proxy server found.
QWARN  : PaymentServerTests::paymentServerTests() PaymentRequestPlus::getMerchant: Payment request: certificate expired or not 
yet active:  QSslCertificate("3", "01", "Ipbt+DxK8RDQd25/5ueXqw==", "PaymentRequest Test 
CA", "testmerchant.org", QMap(), QDateTime(2012-12-10 16:37:24.000 UTC Qt::UTC), QDateTime(2022-12-08 16:37:24.000 
UTC Qt::UTC))
QDEBUG : PaymentServerTests::paymentServerTests() PaymentServer::processPaymentRequest: 
Insecure payment request to  "LYqnbT8oyiEbNFmZeFQe8JJAVDQLPTbhkp"
QWARN  : PaymentServerTests::paymentServerTests() PaymentRequestPlus::getMerchant: Payment request: certificate expired or not 
yet active:  QSslCertificate("3", "01", "Ipbt+DxK8RDQd25/5ueXqw==", "PaymentRequest Test 
CA", "testmerchant.org", QMap(), QDateTime(2012-12-10 16:37:24.000 UTC Qt::UTC), QDateTime(2022-12-08 16:37:24.000 
UTC Qt::UTC))
FAIL!  : PaymentServerTests::paymentServerTests() Compared values are not the 
same
   Actual   (merchant)   : ""
   Expected (QString("testmerchant.org")): "testmerchant.org"
   Loc: [qt/test/paymentservertests.cpp(90)]
PASS   : PaymentServerTests::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 10ms
* Finished testing of PaymentServerTests *
* Start testing of RPCNestedTests *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : RPCNestedTests::initTestCase()
PASS   : RPCNestedTests::rpcNestedTests()
PASS   : RPCNestedTests::cleanupTestCase()
Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 18ms
* Finished testing of RPCNestedTests *
* Start testing of CompatTests *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : CompatTests::initTestCase()
PASS   : CompatTests::bswapTests()
PASS   : CompatTests::cleanupTestCase()
Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 0ms
* Finished testing of CompatTests *
* Start testing of WalletTests *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 10.2.1 20210110), debian 11
PASS   : WalletTests::initTestCase()
QDEBUG : WalletTests::walletTests() TransactionTablePriv::refreshWallet
QWARN  : WalletTests::walletTests() This plugin does not support 
propagateSizeHints()
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
5327c0db6132d9e2a5cf91333bb03cac71cf34df8a6f503c55a86a04cabd1760 status= 0"
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
a97abfdbbcfeca9532f4b70a6975d1ac0ce4ec50cb0de1c6038c594f999d2403 status= 1"
QDEBUG : WalletTests::walletTests() "NotifyAddressBookChanged: 
mfWxJ45yp2SFn7UciZyNpvDKrzbhyfKrY8  isMine=0 purpose=send status=0"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
5327c0db6132d9e2a5cf91333bb03cac71cf34df8a6f503c55a86a04cabd1760 0"
QDEBUG : WalletTests::walletTests() "inModel=0 Index=34-34 showTransaction=1 
derivedStatus=0"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
a97abfdbbcfeca9532f4b70a6975d1ac0ce4ec50cb0de1c6038c594f999d2403 1"
QDEBUG : WalletTests::walletTests() "inModel=1 Index=1-2 showTransaction=1 
derivedStatus=1"
QWARN  : WalletTests::walletTests() This plugin does not support 
propagateSizeHints()
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
ae662ffa76ce22fb14e44bd1b73c836ee881fe91669c290dbe273c5b95caa6bd status= 0"
QDEBUG : WalletTests::walletTests() "NotifyTransactionChanged: 
e5b3f3e89ed68be15e4860589591f3cf06eef7c453e441dc18a08f34d9c35940 status= 1"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
ae662ffa76ce22fb14e44bd1b73c836ee881fe91669c290dbe273c5b95caa6bd 0"
QDEBUG : WalletTests::walletTests() "inModel=0 Index=75-75 showTransaction=1 
derivedStatus=0"
QDEBUG : WalletTests::walletTests() "TransactionTablePriv::updateWallet: 
e5b3f3e89ed68be15e4860589591f3cf06eef7c453e441dc18a08f34d9c35940 1"
QDEBUG : WalletTests::walletTests() "inModel=1 Index=20-21 showTransaction=1 
derivedStatus=1"
QDEBUG : WalletTests::walletTests() "NotifyAddressBookChanged: 

Processed: litecoin: FTBFS in bullseye (expired certificates in test suite)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.21.2.1-1
Bug #1027827 [src:litecoin] litecoin: FTBFS in bullseye (expired certificates 
in test suite)
Marked as fixed in versions litecoin/0.21.2.1-1.

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

Bug#1027825: bind-dyndb-ldap: FTBFS in bullseye (‘dns_dyndbctx_t’ has no member named ‘refvar’)

[Santiago Vila]

Package: src:bind-dyndb-ldap
Version: 11.6-3
Severity: serious
Tags: ftbfs
Control: fixed -1 11.10-1

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules build-arch
dh build-arch --builddirectory=build
   dh_update_autotools_config -a -O--builddirectory=build
   dh_autoreconf -a -O--builddirectory=build
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:14: installing './compile'
configure.ac:4: installing './missing'
src/Makefile.am: installing './depcomp'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--libdir=/usr/lib \
--docdir=/usr/share/doc/bind9-dyndb-ldap
cd build && ../configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode 
--disable-dependency-tracking --libdir=/usr/lib --docdir=/usr/share/doc/bind9-dyndb-ldap
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for ar... ar
checking the archiver (ar) interface... ar
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o 

Bug#1027826: python-skbio: don't Build Depend on python-matplotlib-doc (it no longer exist in bookworm)

[Paul Gevers]

Source: python-skbio
Version: 0.5.6-7
Severity: serious
Tag: ftbfs
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing a Build-Depends now. Not being able to build from 
source in a suite is an RC bug in that suite.


matplotlib stopped building python-matplotlib-doc.

Paul

[1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html


OpenPGP_signature
Description: OpenPGP digital signature

Processed: bind-dyndb-ldap: FTBFS in bullseye (‘dns_dyndbctx_t’ has no member named ‘refvar’)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 11.10-1
Bug #1027825 [src:bind-dyndb-ldap] bind-dyndb-ldap: FTBFS in bullseye 
(‘dns_dyndbctx_t’ has no member named ‘refvar’)
Marked as fixed in versions bind-dyndb-ldap/11.10-1.

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

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Salvatore Bonaccorso]

Hi,

On Tue, Jan 03, 2023 at 09:03:27PM +0100, Salvatore Bonaccorso wrote:
> Source: vim
> Version: 2:9.0.1000-2
> Severity: serious
> Tags: ftbfs
> Justification: ftbfs
> X-Debbugs-Cc: car...@debian.org
> 
> Hi James,
> 
> Severity might not be warranted, please downgrade if you think it's
> needed.
> 
> I noticed on the last two vim builds that the amd64 build failed,
> giving it back helped most of the times. The last upload failed as
> well:
> 
> https://buildd.debian.org/status/fetch.php?pkg=vim=amd64=2%3A9.0.1000-3=1672773526=0

Looking at the older build failures from
https://buildd.debian.org/status/logs.php?pkg=vim=amd64 it looks
it was always on x86-conova-01 when it failed.

Regards,
Salvatore

Bug#460232: Please clarify license

[Sam Hartman]

> "Bastian" == Bastian Germann  writes:

Bastian> The main license does not have a GPL version. However,
Bastian> there are several files licensed under specific (L)GPL
Bastian> versions and also other licenses included.  Debian Policy
Bastian> requires to document every contained license.

Bastian> I have attached a machine-readable copyright file that
Bastian> should have most licenses.

I've reviewed your machine readable copyright file and agree that it
 is  a significant improvement over the previous copyright file.
 I will commit.
 We can continue to improve going forward.
 

Bug#1027793: closed by Debian FTP Masters (reply to James McCoy ) (Bug#1027766: fixed in vim 2:9.0.1000-3)

[Alejandro Colomar]

Hi,

On 1/3/23 17:09, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the vim-common package:

#1027793: vim: insert mode: Backspace doesn't do anything

It has been closed by Debian FTP Masters  (reply to 
James McCoy ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to James McCoy ) 
by
replying to this email.



For my own curiosity, would you mind pointing to the specific change that fixed 
this bug?


Thanks,

Alex





--



OpenPGP_signature
Description: OpenPGP digital signature

Processed: found 1027824 in 2:9.0.1000-3

[Debian Bug Tracking System]

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

> found 1027824 2:9.0.1000-3
Bug #1027824 [src:vim] FTBFS: hanging testsuite: build killed after time of 
inactivity on buildds
Marked as found in versions vim/2:9.0.1000-3.
> thanks
Stopping processing here.

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

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

[Salvatore Bonaccorso]

Source: vim
Version: 2:9.0.1000-2
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: car...@debian.org

Hi James,

Severity might not be warranted, please downgrade if you think it's
needed.

I noticed on the last two vim builds that the amd64 build failed,
giving it back helped most of the times. The last upload failed as
well:

https://buildd.debian.org/status/fetch.php?pkg=vim=amd64=2%3A9.0.1000-3=1672773526=0

Regards,
Salvatore

Bug#1027496: marked as done (pdm-pep517: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 19:52:40 +
with message-id 
and subject line Bug#1027496: fixed in pdm-pep517 1.0.6+ds1-2
has caused the Debian Bug report #1027496,
regarding pdm-pep517: FTBFS: ImportError: cannot import name 'LegacyVersion' 
from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py)
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.)


-- 
1027496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdm-pep517
Version: 1.0.6+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 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 
> * Building wheel...
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/wrappers.py", line 319, in 
> _call_hook
> raise BackendUnavailable(data.get('traceback', ''))
> pep517.wrappers.BackendUnavailable: Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 77, in _build_backend
> obj = import_module(mod_path)
>   File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1050, in _gcd_import
>   File "", line 1027, in _find_and_load
>   File "", line 1006, in _find_and_load_unlocked
>   File "", line 688, in _load_unlocked
>   File "", line 883, in exec_module
>   File "", line 241, in _call_with_frames_removed
>   File "/<>/pdm/pep517/api.py", line 10, in 
> from pdm.pep517.editable import EditableBuilder
>   File "/<>/pdm/pep517/editable.py", line 13, in 
> from pdm.pep517.wheel import WheelBuilder
>   File "/<>/pdm/pep517/wheel.py", line 24, in 
> from pdm.pep517.base import Builder
>   File "/<>/pdm/pep517/base.py", line 12, in 
> from pdm.pep517.metadata import Metadata
>   File "/<>/pdm/pep517/metadata.py", line 20, in 
> from pdm.pep517.version import DynamicVersion
>   File "/<>/pdm/pep517/version.py", line 10, in 
> from pdm.pep517.scm import get_version_from_scm
>   File "/<>/pdm/pep517/scm.py", line 17, in 
> from packaging.version import LegacyVersion, Version
> ImportError: cannot import name 'LegacyVersion' from 'packaging.version' 
> (/usr/lib/python3/dist-packages/packaging/version.py)
> 
> ERROR Backend 'pdm.pep517.api' is not available.
> E: pybuild pybuild:388: 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/2023/01/01/pdm-pep517_1.0.6+ds1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=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: pdm-pep517
Source-Version: 1.0.6+ds1-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
pdm-pep517, 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 

Bug#1026736: marked as done (passes-gtk: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 19:52:30 +
with message-id 
and subject line Bug#1026736: fixed in passes-gtk 0.7-2
has caused the Debian Bug report #1026736,
regarding passes-gtk: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 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.)


-- 
1026736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: passes-gtk
Version: 0.7-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
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.64.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: passes-gtk
> Project version: 0.7
> C compiler for the host machine: cc (gcc 12.2.0 "cc (Debian 12.2.0-10) 
> 12.2.0")
> C linker for the host machine: cc ld.bfd 2.39.50.20221208
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program desktop-file-validate found: NO
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)
> Found pkg-config: /usr/bin/pkg-config (1.8.0)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> WARNING: find_library('libzint') starting in "lib" only works by accident and 
> is not portable
> Library libzint found: YES
> Configuring barcode_content_encoder.py using configuration
> Program python3 found: YES (/usr/bin/python3)
> Configuring passes-gtk using configuration
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Build targets in project: 13
> NOTICE: Future-deprecated features used:
>  * 0.55.0: {'ExternalProgram.path'}
> 
> passes-gtk 0.7
> 
>   User defined options
> buildtype: plain
> libdir   : lib/x86_64-linux-gnu
> localstatedir: /var
> prefix   : /usr
> sysconfdir   : /etc
> wrap_mode: nodownload
> 
> Found ninja-1.11.1 at /usr/bin/ninja
>dh_auto_build
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/11] /usr/bin/msgfmt ../po/it.po -o po/it/LC_MESSAGES/passes.mo
> [2/11] /usr/bin/msgfmt ../po/es.po -o po/es/LC_MESSAGES/passes.mo
> [3/11] /usr/bin/msgfmt ../po/eu.po -o po/eu/LC_MESSAGES/passes.mo
> [4/11] /usr/bin/msgfmt ../po/nl.po -o po/nl/LC_MESSAGES/passes.mo
> [5/11] /usr/bin/meson --internal msgfmthelper --msgfmt=/usr/bin/msgfmt 
> ../data/me.sanchezrodriguez.passes.metainfo.xml.in 
> data/me.sanchezrodriguez.passes.metainfo.xml xml ../data/../po
> [6/11] /usr/bin/meson --internal msgfmthelper --msgfmt=/usr/bin/msgfmt 
> ../data/me.sanchezrodriguez.passes.desktop.in 
> data/me.sanchezrodriguez.passes.desktop desktop ../data/../po
> [7/11] cc -Isrc/model/libbarcode-content-encoder.so.p -Isrc/model 
> -I../src/model -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
> -Winvalid-pch -Wextra -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
> src/model/libbarcode-content-encoder.so.p/barcode_content_encoder.c.o -MF 
> src/model/libbarcode-content-encoder.so.p/barcode_content_encoder.c.o.d -o 
> src/model/libbarcode-content-encoder.so.p/barcode_content_encoder.c.o -c 
> ../src/model/barcode_content_encoder.c
> [8/11] cc  -o src/model/libbarcode-content-encoder.so 
> src/model/libbarcode-content-encoder.so.p/barcode_content_encoder.c.o 
> -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group 
> -Wl,-soname,libbarcode-content-encoder.so -Wl,-z,relro -Wl,-z,now -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib/libzint.so -Wl,--end-group
> [9/11] /usr/bin/blueprint-compiler batch-compile src/generated_ui_files 
> ../src 

Bug#1027604: marked as done (go-dlib: FTBFS: make: *** [debian/rules:8: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 19:35:44 +
with message-id 
and subject line Bug#1027604: fixed in go-dlib 5.6.0.9+dfsg-3
has caused the Debian Bug report #1027604,
regarding go-dlib: FTBFS: make: *** [debian/rules:8: 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.)


-- 
1027604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: go-dlib
Version: 5.6.0.9+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 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 '/<>'
> cd gettext; ./build_test_locale_data
> + OUTDIR=testdata/locale_def
> + mkdir -p testdata/locale_def
> + gen en_US.UTF-8 UTF-8
> + name=en_US.UTF-8
> + charset=UTF-8
> + localedef -f UTF-8 -i en_US testdata/locale_def/en_US.UTF-8
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 8 pkg.deepin.io/lib 
> pkg.deepin.io/lib/app pkg.deepin.io/lib/appinfo 
> pkg.deepin.io/lib/appinfo/desktopappinfo pkg.deepin.io/lib/arch 
> pkg.deepin.io/lib/archive pkg.deepin.io/lib/archive/gzip 
> pkg.deepin.io/lib/archive/utils pkg.deepin.io/lib/asound 
> pkg.deepin.io/lib/backlight/common pkg.deepin.io/lib/backlight/display 
> pkg.deepin.io/lib/backlight/keyboard pkg.deepin.io/lib/calendar 
> pkg.deepin.io/lib/calendar/lunar pkg.deepin.io/lib/calendar/util 
> pkg.deepin.io/lib/cgroup pkg.deepin.io/lib/dbusutil 
> pkg.deepin.io/lib/dbusutil/gsprop pkg.deepin.io/lib/dbusutil/proxy 
> pkg.deepin.io/lib/encoding/kv pkg.deepin.io/lib/event 
> pkg.deepin.io/lib/gdkpixbuf pkg.deepin.io/lib/gettext 
> pkg.deepin.io/lib/graphic pkg.deepin.io/lib/gsettings 
> pkg.deepin.io/lib/imgutil pkg.deepin.io/lib/initializer 
> pkg.deepin.io/lib/initializer/v2 pkg.deepin.io/lib/iso 
> pkg.deepin.io/lib/keyfile pkg.deepin.io/lib/libc pkg.deepin.io/lib/locale 
> pkg.deepin.io/lib/log pkg.deepin.io/lib/mime pkg.deepin.io/lib/mobileprovider 
> pkg.deepin.io/lib/multierr pkg.deepin.io/lib/notify 
> pkg.deepin.io/lib/notify/dbusnotify pkg.deepin.io/lib/pam 
> pkg.deepin.io/lib/pinyin pkg.deepin.io/lib/pinyin_search 
> pkg.deepin.io/lib/procfs pkg.deepin.io/lib/profile pkg.deepin.io/lib/proxy 
> pkg.deepin.io/lib/pulse pkg.deepin.io/lib/pulse/simple 
> pkg.deepin.io/lib/shell pkg.deepin.io/lib/sound 
> pkg.deepin.io/lib/sound_effect pkg.deepin.io/lib/sound_effect/theme 
> pkg.deepin.io/lib/stb_vorbis pkg.deepin.io/lib/strv pkg.deepin.io/lib/tasker 
> pkg.deepin.io/lib/timer pkg.deepin.io/lib/users/group 
> pkg.deepin.io/lib/users/passwd pkg.deepin.io/lib/users/shadow 
> pkg.deepin.io/lib/utils pkg.deepin.io/lib/xdg/basedir 
> pkg.deepin.io/lib/xdg/userdir
> src/pkg.deepin.io/lib/utils/schemas.go:24:2: cannot find package 
> "pkg.deepin.io/gir/gio-2.0" in any of:
>   /usr/lib/go-1.19/src/pkg.deepin.io/gir/gio-2.0 (from $GOROOT)
>   /<>/_build/src/pkg.deepin.io/gir/gio-2.0 (from $GOPATH)
> src/pkg.deepin.io/lib/utils/keyfile.go:27:2: cannot find package 
> "pkg.deepin.io/gir/glib-2.0" in any of:
>   /usr/lib/go-1.19/src/pkg.deepin.io/gir/glib-2.0 (from $GOROOT)
>   /<>/_build/src/pkg.deepin.io/gir/glib-2.0 (from $GOPATH)
> dh_auto_build: error: cd _build && go install -trimpath -v -p 8 
> pkg.deepin.io/lib pkg.deepin.io/lib/app pkg.deepin.io/lib/appinfo 
> pkg.deepin.io/lib/appinfo/desktopappinfo pkg.deepin.io/lib/arch 
> pkg.deepin.io/lib/archive pkg.deepin.io/lib/archive/gzip 
> pkg.deepin.io/lib/archive/utils pkg.deepin.io/lib/asound 
> pkg.deepin.io/lib/backlight/common pkg.deepin.io/lib/backlight/display 
> pkg.deepin.io/lib/backlight/keyboard pkg.deepin.io/lib/calendar 
> pkg.deepin.io/lib/calendar/lunar pkg.deepin.io/lib/calendar/util 
> pkg.deepin.io/lib/cgroup pkg.deepin.io/lib/dbusutil 
> pkg.deepin.io/lib/dbusutil/gsprop pkg.deepin.io/lib/dbusutil/proxy 
> pkg.deepin.io/lib/encoding/kv pkg.deepin.io/lib/event 
> pkg.deepin.io/lib/gdkpixbuf pkg.deepin.io/lib/gettext 
> pkg.deepin.io/lib/graphic pkg.deepin.io/lib/gsettings 
> pkg.deepin.io/lib/imgutil pkg.deepin.io/lib/initializer 
> pkg.deepin.io/lib/initializer/v2 pkg.deepin.io/lib/iso 
> pkg.deepin.io/lib/keyfile pkg.deepin.io/lib/libc pkg.deepin.io/lib/locale 
> pkg.deepin.io/lib/log pkg.deepin.io/lib/mime pkg.deepin.io/lib/mobileprovider 
> pkg.deepin.io/lib/multierr 

Processed: retitle 1027048 to FTBFS with zxing-cpp 1.4

[Debian Bug Tracking System]

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

> retitle 1027048 FTBFS with zxing-cpp 1.4
Bug #1027048 {Done: Rene Engelhard } [src:libreoffice] FTBFS 
with zxing-cpp 1.4 from experimental
Changed Bug title to 'FTBFS with zxing-cpp 1.4' from 'FTBFS with zxing-cpp 1.4 
from experimental'.
> thanks
Stopping processing here.

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

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Frédéric Danis]

On 03/01/2023 18:55, Vagrant Cascadian wrote:

On 2023-01-03, Frédéric Danis wrote:

On 29/12/2022 00:07, Vagrant Cascadian wrote:

On 2022-12-28, Vagrant Cascadian wrote:

The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
commit triggering the issue has been identified as:

a9bf024b2933bba0e23038892970a18b72dfaeb4
efi_loader: disk: a helper function to create efi_disk objects from
udevice

Workarounds I've heard are to disable EFI support for that board, or to
boot using EFI rather than boot scripts or syslinux/extlinux style
menus.

I will also want to get confirmation if other amlogic boards are
affected...

The currently supported amlogic platforms are:

# Neil Armstrong 
u-boot-amlogic_platforms += khadas-vim

# Neil Armstrong 
u-boot-amlogic_platforms += khadas-vim2

# Frederic Danis 
u-boot-amlogic_platforms += libretech-cc

# Neil Armstrong 
u-boot-amlogic_platforms += nanopi-k2

# Vagrant Cascadian 
u-boot-amlogic_platforms += odroid-c2

# Reco 
u-boot-amlogic_platforms += odroid-n2

Please test if the current versions from Debian unstable (2022.10*) and
experimental (2023.01-rc*) are affected by this issue... and if there
are other issues for Debian bookworm/testing (2022.04*).

This is part of what has been blocking u-boot from migrating to testing.


I do not see (m)any records of tests for most of these platforms at:

https://wiki.debian.org/U-boot/Status


live well,
vagrant

u-boot bookworm version works fine with LePotato board (libretech-cc),
see attached lepotato-bookworm.txt.

Thanks!


Afaiu, the bug is not reproducible with unstable and experimental
versions, but boot crash before starting the kernel, see
lepotato-unstable.txt and lepotato-experimental.txt.

Sounds like the bug *is* reproducible with unstable and experiemental
versions, from reading the logs; looks like the same issue with
odroid-c2.

Could you try building a "noefi" variant, like done with odroid-c2, and
test for the lepotato (libretech-cc?):

   
https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d


I will try to build and test this


Could you also test EFI booting with the versions from unstable and
experimental to see if they can load a kernel? If EFI does work, that
justifies building two variants with and without EFI... it is a bit ugly
to produce two variants, but it's the easiest known workaround for
now...


I will need your help on this as I don't know how to test EFI boot, for 
me EFI was specific to Intel platforms.

Can you point me to a doc explaining how to do this on LePotato/Arm board?

Regards,

Fred

--
Frédéric Danis
Senior Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United Kingdom
Registered in England & Wales, no. 5513718

Bug#1026779: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1026779: fixed in binutils 2.39.50.20221224-1)

[Antonio Terceiro]

Control: reopen -1

On Sat, Dec 24, 2022 at 02:45:07PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:binutils package:
> 
> #1026779: binutils: cross binutils and foreign libbinutils not coinstallable, 
> breaking upgrades
> 
> It has been closed by Debian FTP Masters  
> (reply to Matthias Klose ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Matthias Klose ) 
> by
> replying to this email.
> 
> 
> -- 
> 1026779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026779
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Sat, 24 Dec 2022 14:40:11 +
> From: Debian FTP Masters 
> To: 1026779-cl...@bugs.debian.org
> Subject: Bug#1026779: fixed in binutils 2.39.50.20221224-1
> Reply-To: Matthias Klose 
> Message-Id: 
> 

> Date: Tue, 20 Dec 2022 21:04:46 -0300
> From: Antonio Terceiro 
> To: Debian Bug Tracking System 
> Subject: binutils: cross binutils and foreign libbinutils not
>  coinstallable, breaking upgrades
> Message-ID: 
> 
> Source: binutils
> Version: 2.39.50.20221208-5
> Severity: serious
> 
> Dear Maintainer,
> 
> Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
> libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
> where both are installed (e.g. binutils-aarch64-linux-gnu and
> libbinutils:arm64) fails like this:
> 
> 8<8<8<-
> Unpacking libbinutils:arm64 (2.39.50.20221208-5) over (2.39-8) ...
> Preparing to unpack 
> .../3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb ...
> Unpacking binutils-aarch64-linux-gnu (2.39.50.20221208-5) over (2.39-8) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
>  (--unpack):
>  trying to overwrite '/usr/lib/aarch64-linux-gnu/libsframe.so.0.0.0', which 
> is also in package libbinutils:arm64 2.39.50.20221208-5
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Preparing to unpack .../4-binutils-common_2.39.50.20221208-5_amd64.deb ...
> De-configuring binutils-common:arm64 (2.39-8), to allow configuration of 
> binutils-common:amd64 (2.39.50.20221208-5) ...
> Unpacking binutils-common:amd64 (2.39.50.20221208-5) over (2.39-8) ...
> Preparing to unpack .../5-binutils-common_2.39.50.20221208-5_arm64.deb ...
> Unpacking binutils-common:arm64 (2.39.50.20221208-5) over (2.39-8) ...
> Selecting previously unselected package libbinutils:amd64.
> Preparing to unpack .../6-libbinutils_2.39.50.20221208-5_amd64.deb ...
> Unpacking libbinutils:amd64 (2.39.50.20221208-5) ...
> Selecting previously unselected package libjansson4:amd64.
> Preparing to unpack .../7-libjansson4_2.14-2_amd64.deb ...
> Unpacking libjansson4:amd64 (2.14-2) ...
> Errors were encountered while processing:
>  
> /tmp/apt-dpkg-install-maU0ym/3-binutils-aarch64-linux-gnu_2.39.50.20221208-5_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 8<8<8<-

i386 is still affected by this on 2.39.50.20221224-1 (testing):

Unpacking binutils-i686-linux-gnu (2.39.50.20221224-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-X01H6O/8-binutils-i686-linux-gnu_2.39.50.20221224-1_amd64.deb
 (--unpack):
 trying to overwrite '/usr/lib/i386-linux-gnu/libsframe.so.0.0.0', which is 
also in package libbinutils:i386 2.39.50.20221224-1
Errors were encountered while processing:
 
/tmp/apt-dpkg-install-X01H6O/8-binutils-i686-linux-gnu_2.39.50.20221224-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

and also on 2.39.90.20221231-1 (unstable)

Unpacking binutils-i686-linux-gnu (2.39.90.20221231-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/binutils-i686-linux-gnu_2.39.90.20221231-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/i386-linux-gnu/libsframe.so.0.0.0', which is 
also in package libbinutils:i386 2.39.90.20221231-1
Errors were encountered while processing:
 /var/cache/apt/archives/binutils-i686-linux-gnu_2.39.90.20221231-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



signature.asc
Description: PGP signature

Processed: Re: Bug#1026779 closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1026779: fixed in binutils 2.39.50.20221224-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1026779 {Done: Matthias Klose } [src:binutils] binutils: 
cross binutils and foreign libbinutils not coinstallable, breaking upgrades
'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 binutils/2.39.50.20221224-1.

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

Processed: Re: haskell-curl: FTBFS: from curlc.c:10:0: error:

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:curl 7.87.0-1
Bug #1027564 [src:haskell-curl] haskell-curl: FTBFS:  from 
curlc.c:10:0: error:
Bug reassigned from package 'src:haskell-curl' to 'src:curl'.
No longer marked as found in versions haskell-curl/1.3.8-13.
Ignoring request to alter fixed versions of bug #1027564 to the same values 
previously set
Bug #1027564 [src:curl] haskell-curl: FTBFS:  from 
curlc.c:10:0: error:
Marked as found in versions curl/7.87.0-1.
> affects -1 src:haskell-curl
Bug #1027564 [src:curl] haskell-curl: FTBFS:  from 
curlc.c:10:0: error:
Added indication that 1027564 affects src:haskell-curl
> forwarded -1 https://github.com/curl/curl/issues/10148
Bug #1027564 [src:curl] haskell-curl: FTBFS:  from 
curlc.c:10:0: error:
Set Bug forwarded-to-address to 'https://github.com/curl/curl/issues/10148'.

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

Bug#1027564: haskell-curl: FTBFS: from curlc.c:10:0: error:

[Scott Talbert]

Control: reassign -1 src:curl 7.87.0-1
Control: affects -1 src:haskell-curl
Control: forwarded -1 https://github.com/curl/curl/issues/10148

On Sun, 1 Jan 2023, Lucas Nussbaum wrote:


Source: haskell-curl
Version: 1.3.8-13
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):

 debian/rules binary
test -x debian/rules
dh_testroot
dh_prep
dh_installdirs -A
mkdir -p "."
CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
Adding cdbs dependencies to debian/libghc-curl-doc.substvars
dh_installdirs -plibghc-curl-doc \

perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
-E 'make_setup_recipe'
Running ghc --make Setup.hs -o debian/hlibrary.setup
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
-E 'configure_recipe'
Running find . ! -newer /tmp/lTGCgHLmiB -exec touch -d 1998-01-01 UTC {} ;
Running dh_listpackages
libghc-curl-dev
libghc-curl-prof
libghc-curl-doc
Running dh_listpackages
libghc-curl-dev
libghc-curl-prof
libghc-curl-doc
Running dpkg-buildflags --get LDFLAGS
-Wl,-z,relro
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/curl-1.3.8/ --datasubdir=curl 
--htmldir=/usr/share/doc/libghc-curl-doc/html/ --enable-library-profiling
Using Parsec parser
Configuring curl-1.3.8...
Flags chosen: new-base=True
Dependency base >=3 && <5: using base-4.15.1.0
Dependency bytestring >=0.9: using bytestring-0.10.12.1
Dependency containers: using containers-0.6.4.1
Source component graph: component lib
Configured component graph:
component curl-1.3.8-A0wPVE8VAFIAErUUBZVdib
include base-4.15.1.0
include bytestring-0.10.12.1
include containers-0.6.4.1
Linked component graph:
unit curl-1.3.8-A0wPVE8VAFIAErUUBZVdib
include base-4.15.1.0
include bytestring-0.10.12.1
include containers-0.6.4.1

Network.Curl=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl,Network.Curl.Code=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Code,Network.Curl.Debug=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Debug,Network.Curl.Easy=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Easy,Network.Curl.Info=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Info,Network.Curl.Opts=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Opts,Network.Curl.Post=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Post,Network.Curl.Types=curl-1.3.8-A0wPVE8VAFIAErUUBZVdib:Network.Curl.Types
Ready component graph:
definite curl-1.3.8-A0wPVE8VAFIAErUUBZVdib
depends base-4.15.1.0
depends bytestring-0.10.12.1
depends containers-0.6.4.1
Using Cabal-3.4.1.0 compiled by ghc-9.0
Using compiler: ghc-9.0.2
Using install prefix: /usr
Executables installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-9.0.2/curl-1.3.8-A0wPVE8VAFIAErUUBZVdib
Dynamic Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-9.0.2
Private executables installed in: /usr/lib/x86_64-linux-ghc-9.0.2/curl-1.3.8
Data files installed in: /usr/share/curl
Documentation installed in: /usr/share/doc/x86_64-linux-ghc-9.0.2/curl-1.3.8
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
No c2hs found
No cpphs found
No doctest found
Using gcc version 12 found on system at: /usr/bin/x86_64-linux-gnu-gcc
Using ghc version 9.0.2 found on system at: /usr/bin/ghc
Using ghc-pkg version 9.0.2 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.25.1 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.68 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
No pkg-config found
Using runghc version 9.0.2 found on system at: /usr/bin/runghc
Using strip version 2.39 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
touch configure-ghc-stamp
perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
-E 'build_recipe'
Running dh_listpackages
libghc-curl-dev
libghc-curl-prof
libghc-curl-doc
Preprocessing library for curl-1.3.8..

Processed: tagging 1019841

[Debian Bug Tracking System]

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

> tags 1019841 + patch
Bug #1019841 [src:amule] amule: Please transition to wxwidgets3.2
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 1019791

[Debian Bug Tracking System]

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

> tags 1019791 + patch
Bug #1019791 [src:stimfit] stimfit: Please transition to wxwidgets3.2
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: One more missing flag

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1026937 {Done: Laszlo Boszormenyi (GCS) } 
[python3-grpcio] python3-grpcio: ImportError: undefined symbol: 
_ZN4absl7debian313hash_internal15MixingHashState5kSeedE
'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 grpc/1.51.1-3.
> found -1 1.51.1-3
Bug #1026937 [python3-grpcio] python3-grpcio: ImportError: undefined symbol: 
_ZN4absl7debian313hash_internal15MixingHashState5kSeedE
Marked as found in versions grpc/1.51.1-3.
> block 1027112 by -1
Bug #1027112 [src:bazel-bootstrap] bazel-bootstrap: 
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
1027112 was not blocked by any bugs.
1027112 was not blocking any bugs.
Added blocking bug(s) of 1027112: 1026937
> affects -1 bazel-bootstrap
Bug #1026937 [python3-grpcio] python3-grpcio: ImportError: undefined symbol: 
_ZN4absl7debian313hash_internal15MixingHashState5kSeedE
Added indication that 1026937 affects bazel-bootstrap

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

Bug#1026937: One more missing flag

[Olek Wojnar]

Control: reopen -1
Control: found -1 1.51.1-3
Control: block 1027112 by -1
Control: affects -1 bazel-bootstrap

Hi László,

I noticed that you added some linker flags in a recent commit to grpc 
[1]. However, it appears that this one is still missing:

-labsl_synchronization

Having spent some time digging into the bazel-bootstrap build 
errors,[2][3] I believe that those are caused by this missing flag. 
Could you please add that one as well? Thank you!


-Olek


[1] 
https://salsa.debian.org/debian/grpc/-/commit/f8f8a4445fa63f803ee02dd142c37be1f6e040f4
[2] 
https://buildd.debian.org/status/fetch.php?pkg=bazel-bootstrap=amd64=4.2.3%2Bds-1%2Bb1=1671977092=0

[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027112


OpenPGP_signature
Description: OpenPGP digital signature

Bug#997323: lektor: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

[Jérôme Charaoui]

Le 2023-01-03 à 11 h 45, Bastian Germann a écrit :

X-Debbugs-Cc: jer...@riseup.net

On Tue, 3 Jan 2023 17:35:24 +0100 Bastian Germann  wrote:

This will be rectified with importing v3.3.0+.
But there will be other problems with the current werkzeug version 
which are addressed with v3.4.0b1:

https://github.com/lektor/lektor/pull/1051


I see the maintainer and Jérôme have worked on new versions but they 
were never released.

Is there something missing?


And of course I've just noticed that python3-mistune0 now exists in 
Debian, so maybe I can finally upload Lektor 3.3 ...

Bug#997323: lektor: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

[Jérôme Charaoui]

Le 2023-01-03 à 11 h 45, Bastian Germann a écrit :

X-Debbugs-Cc: jer...@riseup.net

On Tue, 3 Jan 2023 17:35:24 +0100 Bastian Germann  wrote:

This will be rectified with importing v3.3.0+.
But there will be other problems with the current werkzeug version 
which are addressed with v3.4.0b1:

https://github.com/lektor/lektor/pull/1051


I see the maintainer and Jérôme have worked on new versions but they 
were never released.

Is there something missing?


Since python-mistune has moved to 2.x in Debian, the Lektor 3.2 and 3.3 
branches are no longer functional. Upstream has integrated mistune 2.0 
support in 3.4 but there have only been beta releases of it so far, and 
I'm not entirely sure if we should upload that and release it with bookworm?


In short, I've been working on it but it has been quite a moving target 
so far.


-- Jerome

Processed: adonthell: diff for NMU version 0.3.8-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1027815 + patch
Bug #1027815 [src:adonthell] adonthell: FTBFS with Python 3.11 as default 
version
Added tag(s) patch.
> tags 1027815 + pending
Bug #1027815 [src:adonthell] adonthell: FTBFS with Python 3.11 as default 
version
Added tag(s) pending.

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

Bug#1027815: adonthell: diff for NMU version 0.3.8-2.1

[Stefano Rivera]

Control: tags 1027815 + patch
Control: tags 1027815 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru adonthell-0.3.8/debian/changelog adonthell-0.3.8/debian/changelog
--- adonthell-0.3.8/debian/changelog	2022-03-28 13:31:59.0 -0400
+++ adonthell-0.3.8/debian/changelog	2023-01-03 13:39:42.0 -0400
@@ -1,3 +1,10 @@
+adonthell (0.3.8-2.1) unreleased; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.11 support. (Closes: #1027815)
+
+ -- Stefano Rivera   Tue, 03 Jan 2023 13:39:42 -0400
+
 adonthell (0.3.8-2) unstable; urgency=high
 
   * Team upload.
diff -Nru adonthell-0.3.8/debian/patches/python3.11.patch adonthell-0.3.8/debian/patches/python3.11.patch
--- adonthell-0.3.8/debian/patches/python3.11.patch	1969-12-31 20:00:00.0 -0400
+++ adonthell-0.3.8/debian/patches/python3.11.patch	2023-01-03 13:39:42.0 -0400
@@ -0,0 +1,16 @@
+Remove  include. This was indirectly included via Python.h, and Python
+3.11 removed the header entirely.
+
+Author: Stefano Rivera 
+Bug-Debian: https://bugs.debian.org/1027815
+Forwarded: not-needed
+--- a/src/python_class.h
 b/src/python_class.h
+@@ -35,7 +35,6 @@
+ #include 
+ #include "Python.h"
+ #include "compile.h"
+-#include "eval.h"
+ #include "fileops.h"
+ 
+ #ifndef SWIG
diff -Nru adonthell-0.3.8/debian/patches/series adonthell-0.3.8/debian/patches/series
--- adonthell-0.3.8/debian/patches/series	2022-03-28 13:29:19.0 -0400
+++ adonthell-0.3.8/debian/patches/series	2023-01-03 13:37:51.0 -0400
@@ -1 +1,2 @@
 python3.10.patch
+python3.11.patch

Processed: Re: Bug#1026599: cadabra2: FTBFS: type_caster_base.h:482:26: error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + fixed-upstream
Bug #1026599 [src:cadabra2] cadabra2: FTBFS: type_caster_base.h:482:26: error: 
invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
Added tag(s) fixed-upstream.

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

Bug#1026599: cadabra2: FTBFS: type_caster_base.h:482:26: error: invalid use of incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}

[Stefano Rivera]

Control: tag -1 + fixed-upstream

Looks like upstream has updated the embedded pybind11 for Python 3.11
support in 
https://github.com/kpeeters/cadabra2/commit/217bc21f9fff3de8eeb9ed651b2143a4f9c8a4b6
available from 2.4.2.2.

Of course it's worth asking if the Debian package should be using these
bundled libraries at all

SR

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

Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

[Vagrant Cascadian]

On 2023-01-03, Frédéric Danis wrote:
> On 29/12/2022 00:07, Vagrant Cascadian wrote:
>> On 2022-12-28, Vagrant Cascadian wrote:
>>> The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those
>>> produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The
>>> commit triggering the issue has been identified as:
>>>
>>>a9bf024b2933bba0e23038892970a18b72dfaeb4
>>>efi_loader: disk: a helper function to create efi_disk objects from
>>>udevice
>>>
>>> Workarounds I've heard are to disable EFI support for that board, or to
>>> boot using EFI rather than boot scripts or syslinux/extlinux style
>>> menus.
>>>
>>> I will also want to get confirmation if other amlogic boards are
>>> affected...
>> The currently supported amlogic platforms are:
>>
>># Neil Armstrong 
>>u-boot-amlogic_platforms += khadas-vim
>>
>># Neil Armstrong 
>>u-boot-amlogic_platforms += khadas-vim2
>>
>># Frederic Danis 
>>u-boot-amlogic_platforms += libretech-cc
>>
>># Neil Armstrong 
>>u-boot-amlogic_platforms += nanopi-k2
>>
>># Vagrant Cascadian 
>>u-boot-amlogic_platforms += odroid-c2
>>
>># Reco 
>>u-boot-amlogic_platforms += odroid-n2
>>
>> Please test if the current versions from Debian unstable (2022.10*) and
>> experimental (2023.01-rc*) are affected by this issue... and if there
>> are other issues for Debian bookworm/testing (2022.04*).
>>
>> This is part of what has been blocking u-boot from migrating to testing.
>>
>>
>> I do not see (m)any records of tests for most of these platforms at:
>>
>>https://wiki.debian.org/U-boot/Status
>>
>>
>> live well,
>>vagrant
>
> u-boot bookworm version works fine with LePotato board (libretech-cc), 
> see attached lepotato-bookworm.txt.

Thanks!

> Afaiu, the bug is not reproducible with unstable and experimental 
> versions, but boot crash before starting the kernel, see 
> lepotato-unstable.txt and lepotato-experimental.txt.

Sounds like the bug *is* reproducible with unstable and experiemental
versions, from reading the logs; looks like the same issue with
odroid-c2.

Could you try building a "noefi" variant, like done with odroid-c2, and
test for the lepotato (libretech-cc?):

  
https://salsa.debian.org/debian/u-boot/-/commit/711ca985af1cab6f11e33fcf5e30dcc40dc7e64d



Could you also test EFI booting with the versions from unstable and
experimental to see if they can load a kernel? If EFI does work, that
justifies building two variants with and without EFI... it is a bit ugly
to produce two variants, but it's the easiest known workaround for
now...


Will try to test EFI on the odroid-c2 shortly...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1026088: marked as done (rdma-core: add mips64* to COHERENT_DMA_ARCHS)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 17:32:28 +
with message-id 
and subject line Bug#1026088: fixed in rdma-core 44.0-1
has caused the Debian Bug report #1026088,
regarding rdma-core: add mips64* to COHERENT_DMA_ARCHS
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.)


-- 
1026088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdma-core
Version: 33.2-1
Severity: serious
Tags: ftbfs

Can you help to add the fellow 4 ports
mips64 mips64el mips64r6 mips64r6el
to the list of
COHERENT_DMA_ARCHS
in debian/rules ?

-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Source: rdma-core
Source-Version: 44.0-1
Done: Benjamin Drung 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Jan 2023 17:29:32 +0100
Source: rdma-core
Built-For-Profiles: noudeb
Architecture: source
Version: 44.0-1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Benjamin Drung 
Closes: 1026088
Changes:
 rdma-core (44.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Add Microsoft Azure Network Adapter (MANA) RDMA provider
 - util: mmio: fix build on MIPS with binutils >= 2.35
   * Add 64-bit MIPS architectures to COHERENT_DMA_ARCHS (Closes: #1026088)
   * debian/watch: Query api.github.com for release tarballs
Checksums-Sha1:
 fd3843d0519ed0b526ebe4f43d87b2ca9c2d2196 3190 rdma-core_44.0-1.dsc
 f1ff3710270ad7920626f73e955aae2b1a043136 1930453 rdma-core_44.0.orig.tar.gz
 0d4dc06d6a9369791009ac497db33d7a9b3347d0 23784 rdma-core_44.0-1.debian.tar.xz
 d6d691a440e837ec9b4baca0083f56686051c700 9495 rdma-core_44.0-1_source.buildinfo
Checksums-Sha256:
 114c12d279a4a4e9d70060a3b5a5a5d54ac98d1772200933ccc49f54f32c8d7b 3190 
rdma-core_44.0-1.dsc
 25d6601e60f27bbcd75e07fe340400cb80e6c3c487679700535385cfc9d9858b 1930453 
rdma-core_44.0.orig.tar.gz
 67a15ff946cc1ce0dffd4528bc6ddbc4c468236405d9000efbed5c07d10e7bc2 23784 
rdma-core_44.0-1.debian.tar.xz
 c55747abbd4657d1f38796a493dab161f7d29c41d481ee76fa4ead3f360a3bff 9495 
rdma-core_44.0-1_source.buildinfo
Files:
 bfdb2079c1bf0465e21a898e0d67eddb 3190 net optional rdma-core_44.0-1.dsc
 ce0e0c383d682b41e31ac8fe2139e62f 1930453 net optional 
rdma-core_44.0.orig.tar.gz
 e5e02cb1ae25926a22a250ae4baa2f95 23784 net optional 
rdma-core_44.0-1.debian.tar.xz
 e8230dda89fa711d359f9f00f51da06b 9495 net optional 
rdma-core_44.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmO0WugACgkQFZ61xO/I
d0wgHQ//f3Ws7FB0O3UpU6A5jKpkHRc0yiW6MwDu8/BjkmVWZoo6S0dLYQMHTZX2
wBARfMhVImK/9gs3tYpOPFaebYegu4paksS+lVKuIey8cpCnIzXCR/wupCQAPaKL
a0VkpaNz6IvCrmttgBa3ZxR+gBYw52SDOuosn62tMKtBtykoYpBoSfyGVVOUHCnm
EorNtcK9SIE/gWvbso65sEb1IIMGGolck+WFA4WQd1C+MRGPrU5CRBixVe0Rh9UE
7JJtTZ7D3fJdfhJhu8kiQcmCZsd0Oscs8yhwbHeRF7hx7yb3rDLYwwlZrWcQOmGL
w9ueUD7yERrMZ0fzJwgNmFhem57TYK3TYnivqd71IOaBjj/iMs/8TOPjY8HFIkNZ
RVHNO53OLnFFz7tflQHSDvQyJovltmGlVbk2ihEg2ZwAEUDJEuF/wn94r9phiT0x
1sYK4IVWcoO3la/vbPKBVNHyYUguMi+YUyV7jRmQjbJ32qBQ+JWZwF457oKsWVk/
083ruSHxvJSktkf+QZi/nl+P5roQJJs6F2PbvoGpT0ht8Y2ni0iWup6FDSad+GK4
F+YmrXVbcBw8YvrVm4hIbwgrG5oGg0FAYTImkaRHhod/pMJc85fGTvnIY2Vuu+um
fU0MGQ06ZskgAJ1XbTayCprD/o5/FVtjRaNEC9f4bQopmHNOaew=
=8y5q
-END PGP SIGNATURE End Message ---

Bug#1027815: adonthell: FTBFS with Python 3.11 as default version

[Graham Inggs]

Source: adonthell
Version: 0.3.8-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

adonthell fails to build from source with Python 3.11 as the default
version.  I've copied what I hope is the relevant part of the log
below.

Regards
Graham


g++ -DHAVE_CONFIG_H -I. -I..   -DOGG_MUSIC -I/usr/include/SDL2
-D_REENTRANT   -I/usr/include/python3.11 -I/usr/include/freetype2
-I/usr/include/libpng16  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security  -DDATA_DIR="\"/usr/share/games/adonthell\""
-DPY_DEBUG  -c -o animation.o animation.cc
In file included from py_object.h:33,
 from audio.h:24,
 from main.cc:30:
python_class.h:38:10: fatal error: eval.h: No such file or directory
   38 | #include "eval.h"
  |  ^~~~
compilation terminated.
make[4]: *** [Makefile:762: main.o] Error 1
make[4]: *** Waiting for unfinished jobs
In file included from py_object.h:33,
 from event.h:31,
 from event_list.h:33,
 from mapcharacter.h:43,
 from character.h:33,
 from gamedata.h:34,
 from achievements.cc:28:
python_class.h:38:10: fatal error: eval.h: No such file or directory
   38 | #include "eval.h"
  |  ^~~~
compilation terminated.
make[4]: *** [Makefile:762: achievements.o] Error 1
In file included from py_object.h:33,
 from event.h:31,
 from event_list.h:33,
 from mapcharacter.h:43,
 from landmap.h:32,
 from mapview.h:34,
 from win_mapview.h:24,
 from adonthell.h:30,
 from adonthell.cc:31:
python_class.h:38:10: fatal error: eval.h: No such file or directory
   38 | #include "eval.h"
  |  ^~~~
compilation terminated.

Bug#1016963: Please test u-boot for orangepi_zero_plus2

[Frédéric Danis]

Hi Vagrant,

On 29/12/2022 00:57, Vagrant Cascadian wrote:

On 2022-12-28, Vagrant Cascadian wrote:

On 2022-12-22, Vagrant Cascadian wrote:

On 2022-08-20, Vagrant Cascadian wrote:

On 2022-08-10, Vagrant Cascadian wrote:

This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please consider testing and
reporting the status:

   https://wiki.debian.org/U-boot/Status

I have not received many test results for current or even remotely
recent u-boot platforms in Debian, and u-boot has been blocked from
migration to testing partly because of this.

As the bookworm freeze approaches, this is getting to be... worrysome!

If you have access to any of these boards, please consider testing
u-boot versions as packaged in debian for versions from debian stable
(2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
(2023.01-rc*) and updating the wiki page if successful and/or replying
to 1016...@bugs.debian.org with a positive confirmation...

...and if not successful, filing bugs against the relevent u-boot-*
packages and marking them as blocking 1016963.

orangepi_zero_plus2


U-boto works fine for all versions on Orange Pi Zero Plus 2 H5 board.
I updated the wiki page.

Regards,

Fred

--
Frédéric Danis
Senior Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United Kingdom
Registered in England & Wales, no. 5513718

Bug#1027812: renpy: FTBFS with Python 3.11 as default version

[Graham Inggs]

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

Hi Maintainer

renpy fails to build from source with Python 3.11 as the default
version.  I've copied what I hope is the relevant part of the log
below.

Regards
Graham


gen3/renpy.compat.dictviews.c: In function
‘__pyx_f_5renpy_6compat_9dictviews_use_view’:
gen3/renpy.compat.dictviews.c:1959:36: error: ‘PyThreadState’ {aka
‘struct _ts’} has no member named ‘frame’; did you mean ‘cframe’?
 1959 |   __pyx_r = ((PyThreadState_Get()->frame->f_code->co_flags &
(CO_FUTURE_DIVISION | CO_FUTURE_WITH_STATEMENT)) ==
(CO_FUTURE_DIVISION | CO_FUTURE_WITH_STATEMENT));
  |^
  |cframe
...

error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
make[1]: *** [debian/rules:30: override_dh_auto_build] Error 1

Bug#1022384: marked as done (sdbus-cpp: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 16:52:57 +
with message-id 
and subject line Bug#1022384: fixed in sdbus-cpp 1.2.0-2
has caused the Debian Bug report #1022384,
regarding sdbus-cpp: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j1
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
> Start 1: sdbus-c++-unit-tests
> 
> 1: Test command: 
> /<>/obj-x86_64-linux-gnu/tests/sdbus-c++-unit-tests
> 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 1: Test timeout computed to be: 1000
> 1: [==] Running 97 tests from 42 test suites.
> 1: [--] Global test environment set-up.
> 1: [--] 16 tests from AMessage
> 1: [ RUN  ] AMessage.CanBeDefaultConstructed
> 1: [   OK ] AMessage.CanBeDefaultConstructed (0 ms)
> 1: [ RUN  ] AMessage.IsInvalidAfterDefaultConstructed
> 1: [   OK ] AMessage.IsInvalidAfterDefaultConstructed (0 ms)
> 1: [ RUN  ] AMessage.IsValidWhenConstructedAsRealMessage
> 1: [   OK ] AMessage.IsValidWhenConstructedAsRealMessage (0 ms)
> 1: [ RUN  ] AMessage.CreatesShallowCopyWhenCopyConstructed
> 1: [   OK ] AMessage.CreatesShallowCopyWhenCopyConstructed (0 ms)
> 1: [ RUN  ] AMessage.CreatesDeepCopyWhenEplicitlyCopied
> 1: [   OK ] AMessage.CreatesDeepCopyWhenEplicitlyCopied (0 ms)
> 1: [ RUN  ] AMessage.IsEmptyWhenContainsNoValue
> 1: [   OK ] AMessage.IsEmptyWhenContainsNoValue (0 ms)
> 1: [ RUN  ] AMessage.IsNotEmptyWhenContainsAValue
> 1: [   OK ] AMessage.IsNotEmptyWhenContainsAValue (0 ms)
> 1: [ RUN  ] AMessage.CanCarryASimpleInteger
> 1: [   OK ] AMessage.CanCarryASimpleInteger (0 ms)
> 1: [ RUN  ] AMessage.CanCarryAUnixFd
> 1: [   OK ] AMessage.CanCarryAUnixFd (0 ms)
> 1: [ RUN  ] AMessage.CanCarryAVariant
> 1: [   OK ] AMessage.CanCarryAVariant (0 ms)
> 1: [ RUN  ] AMessage.CanCarryACollectionOfEmbeddedVariants
> 1: [   OK ] AMessage.CanCarryACollectionOfEmbeddedVariants (0 ms)
> 1: [ RUN  ] AMessage.CanCarryAnArray
> 1: [   OK ] AMessage.CanCarryAnArray (0 ms)
> 1: [ RUN  ] AMessage.CanCarryADictionary
> 1: [   OK ] AMessage.CanCarryADictionary (0 ms)
> 1: [ RUN  ] AMessage.CanCarryAComplexType
> 1: [   OK ] AMessage.CanCarryAComplexType (0 ms)
> 1: [ RUN  ] AMessage.CanPeekASimpleType
> 1: [   OK ] AMessage.CanPeekASimpleType (0 ms)
> 1: [ RUN  ] AMessage.CanPeekContainerContents
> 1: [   OK ] AMessage.CanPeekContainerContents (0 ms)
> 1: [--] 16 tests from AMessage (0 ms total)
> 1: 
> 1: [--] 9 tests from AVariant
> 1: [ RUN  ] AVariant.CanBeDefaultConstructed
> 1: [   OK ] AVariant.CanBeDefaultConstructed (0 ms)
> 1: [ RUN  ] AVariant.ContainsNoValueAfterDefaultConstructed
> 1: [   OK ] AVariant.ContainsNoValueAfterDefaultConstructed (0 ms)
> 1: [ RUN  ] AVariant.CanBeConstructedFromASimpleValue
> 1: [   OK ] AVariant.CanBeConstructedFromASimpleValue (0 ms)
> 1: [ RUN  ] AVariant.CanBeConstructedFromAComplexValue
> 1: [   OK ] AVariant.CanBeConstructedFromAComplexValue (0 ms)
> 1: [ RUN  ] AVariant.CanBeCopied
> 1: [   OK ] AVariant.CanBeCopied (0 ms)
> 1: [ RUN  ] AVariant.IsNotEmptyWhenContainsAValue
> 1: [   OK ] AVariant.IsNotEmptyWhenContainsAValue (0 ms)
> 1: [ RUN  ] 
> AVariant.HasConceptuallyNonmutableGetMethodWhichCanBeCalledXTimes
> 1: [   OK ] 
> AVariant.HasConceptuallyNonmutableGetMethodWhichCanBeCalledXTimes (0 ms)
> 1: [ RUN  ] 
> AVariant.ReturnsTrueWhenAskedIfItContainsTheTypeItReallyContains
> 1: [

Bug#1009407: marked as done (python-quamash: FTBFS: AttributeError: module 'collections' has no attribute 'Mapping')

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 16:51:35 +
with message-id 
and subject line Bug#1009407: fixed in python-quamash 0.6.1~dfsg-2
has caused the Debian Bug report #1009407,
regarding python-quamash: FTBFS: AttributeError: module 'collections' has no 
attribute 'Mapping'
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.)


-- 
1009407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-quamash
Version: 0.6.1~dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 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: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:239: python3.10 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 2, in 
> import quamash
>   File "/<>/quamash/__init__.py", line 594, in 
> from ._unix import _SelectorEventLoop
>   File "/<>/quamash/_unix.py", line 44, in 
> class _SelectorMapping(collections.Mapping):
> AttributeError: module 'collections' has no attribute 'Mapping'
> E: pybuild pybuild:369: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:3: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/python-quamash_0.6.1~dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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: python-quamash
Source-Version: 0.6.1~dfsg-2
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated python-quamash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Jan 2023 16:27:01 +0100
Source: python-quamash
Architecture: source
Version: 0.6.1~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team 
Changed-By: Bastian Germann 
Closes: 1009407
Changes:
 python-quamash (0.6.1~dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Patch: Add compatibility with Python 3.10 (Closes: #1009407)
   * Update debhelper-compat to level 12
   * Drop unavailable Qt4-based dependencies
Checksums-Sha1:
 f389c2ab064d07c187cdcae574c398f6fc504889 1914 python-quamash_0.6.1~dfsg-2.dsc
 62fcbe588bdf72f42b93104a86e07ff330f3de52 6324 
python-quamash_0.6.1~dfsg-2.debian.tar.xz
 925abf8bc183c8f1fa089056e6d736ae442f1c0a 9631 
python-quamash_0.6.1~dfsg-2_source.buildinfo
Checksums-Sha256:
 19cd57dc84f2206f9a545e16d6fa4b59aa682d98d814659a280076e18fbcbd4e 1914 
python-quamash_0.6.1~dfsg-2.dsc
 f17ea20f59217c32090a12db779d5cdaed7fa6e160de7a66cb32f13e02001e52 6324 
python-quamash_0.6.1~dfsg-2.debian.tar.xz
 ed6d6f8fc26c361ee11152b824f4da5500d1eed8aaff1c358df7283d4816ff08 9631 
python-quamash_0.6.1~dfsg-2_source.buildinfo
Files:
 665f8578dbeef3910f3a130dcd72d218 1914 python optional 

Bug#997323: lektor: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

[Bastian Germann]

X-Debbugs-Cc: jer...@riseup.net

On Tue, 3 Jan 2023 17:35:24 +0100 Bastian Germann  wrote:

This will be rectified with importing v3.3.0+.
But there will be other problems with the current werkzeug version which are 
addressed with v3.4.0b1:
https://github.com/lektor/lektor/pull/1051


I see the maintainer and Jérôme have worked on new versions but they were never 
released.
Is there something missing?

Bug#1026012: marked as done (astropy-healpix: FTBFS because of failing test suite)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 16:34:33 +
with message-id 
and subject line Bug#1026012: fixed in astropy-healpix 0.6-2
has caused the Debian Bug report #1026012,
regarding astropy-healpix: FTBFS because of failing test suite
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.)


-- 
1026012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astropy-healpix
Version: 0.6-1
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Dear maintainers,

the new python-hypothesis 6.60 apparently exposed a bug in your package,
causing it to FTBFS and fail the autopkgtest.

Relevant excerpt from the build log:


=== FAILURES ===
_ test_vec2pix _

@given(nside_pow=integers(0, 29), nest=booleans(),
>  x=floats(-1, 1, allow_nan=False, allow_infinity=False).filter(lambda 
> x: abs(x) > 1e-10),
   y=floats(-1, 1, allow_nan=False, allow_infinity=False).filter(lambda 
y: abs(y) > 1e-10),
   z=floats(-1, 1, allow_nan=False, allow_infinity=False).filter(lambda 
z: abs(z) > 1e-10))

astropy_healpix/tests/test_healpy.py:116: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

nside_pow = 2, x = 1.0, y = 1.0, z = 0.5, nest = False

@given(nside_pow=integers(0, 29), nest=booleans(),
   x=floats(-1, 1, allow_nan=False, allow_infinity=False).filter(lambda 
x: abs(x) > 1e-10),
   y=floats(-1, 1, allow_nan=False, allow_infinity=False).filter(lambda 
y: abs(y) > 1e-10),
   z=floats(-1, 1, allow_nan=False, allow_infinity=False).filter(lambda 
z: abs(z) > 1e-10))
@settings(max_examples=2000, derandomize=True, deadline=None)
def test_vec2pix(nside_pow, x, y, z, nest):
nside = 2 ** nside_pow
ipix1 = hp_compat.vec2pix(nside, x, y, z, nest=nest)
ipix2 = hp.vec2pix(nside, x, y, z, nest=nest)
>   assert ipix1 == ipix2
E   assert 42 == 58
E   Falsifying example: test_vec2pix(
E   nside_pow=2, nest=False, x=1.0, y=1.0, z=0.5,
E   )

astropy_healpix/tests/test_healpy.py:124: AssertionError
_ test_vec2ang _

@given(vectors=arrays(float, (3,), elements=floats(-1, 
1)).filter(not_at_origin),
>  lonlat=booleans(), ndim=integers(0, 4))

astropy_healpix/tests/test_healpy.py:210: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

vectors = array([  1.e+00,  -2.22044605e-16,   1.e+00])
lonlat = False, ndim = 0

@given(vectors=arrays(float, (3,), elements=floats(-1, 
1)).filter(not_at_origin),
   lonlat=booleans(), ndim=integers(0, 4))
@settings(max_examples=500, derandomize=True, deadline=None)
def test_vec2ang(vectors, lonlat, ndim):
vectors = np.broadcast_to(vectors, (2,) * ndim + (3,))
theta1, phi1 = hp_compat.vec2ang(vectors, lonlat=lonlat)
theta2, phi2 = hp.vec2ang(vectors, lonlat=lonlat)
# Healpy sometimes returns NaNs for phi (somewhat incorrectly)
phi2 = np.nan_to_num(phi2)
assert_allclose(theta1, theta1, atol=1e-10)
>   assert_allclose(phi1, phi2, atol=1e-10)
E   AssertionError: 
E   Not equal to tolerance rtol=1e-07, atol=1e-10
E   
E   Mismatched elements: 1 / 1 (100%)
E   Max absolute difference: 6.283185307179586
E   Max relative difference: 1.0
Ex: array([ 0.])
Ey: array([ 6.283185])
E   Falsifying example: test_vec2ang(
E   vectors=array([  1.e+00,  -2.22044605e-16,   
1.e+00]),
E   lonlat=False,
E   ndim=0,
E   )

astropy_healpix/tests/test_healpy.py:219: AssertionError
=== warnings summary ===
astropy_healpix/conftest.py:50
  
/<>/.pybuild/cpython3_3.10_astropy-healpix/build/astropy_healpix/conftest.py:50:
 AstropyDeprecationWarning: The enable_deprecations_as_exceptions function is 
deprecated and may be removed in a future version.
  Use https://docs.pytest.org/en/stable/warnings.html instead.
enable_deprecations_as_exceptions()

.pybuild/cpython3_3.10_astropy-healpix/build/astropy_healpix/tests/test_core.py::test_interpolate_bilinear_invalid
  
/<>/.pybuild/cpython3_3.10_astropy-healpix/build/astropy_healpix/core.py:605:
 RuntimeWarning: invalid value encountered in bilinear_interpolation_weights
result = 

Bug#997323: lektor: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

[Bastian Germann]

This will be rectified with importing v3.3.0+.
But there will be other problems with the current werkzeug version which are 
addressed with v3.4.0b1:
https://github.com/lektor/lektor/pull/1051

Bug#1027766: marked as done (vim-common: debian.vim installed into the wrong directory)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 16:04:50 +
with message-id 
and subject line Bug#1027766: fixed in vim 2:9.0.1000-3
has caused the Debian Bug report #1027766,
regarding vim-common: debian.vim installed into the wrong directory
to be marked as done.

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

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


-- 
1027766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim
Version: 2:9.0.1000-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)


Hey.

The following probably still worked with 2:9.0.1000-1, but definitely works 
again
when going back to the version in testing (2:9.0.0813-1+b1).

When I edit a file (pre-existing or new) I can only remove characters with
backspace when I've added them previously when in edit-mode.
As soon as I leave that, then go back into edit-mode and then backspace, it 
doesn't
work anymore.

Seemed to be "specific to "my" configuration though, as it does work with 
--clean.
However, after bisecting all my vimrc’s options, none seemed to have caused it 
and
even if I fully empty the file it still doesn't work (only when I move it away).

Find my .vim/vimrc attached.


Thanks,
Chris.

-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk3
/usr/bin/vim is /usr/bin/vim.gtk3
/usr/bin/gvim is /usr/bin/vim.gtk3

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vim depends on:
ii  libacl1  2.3.1-2
ii  libc62.36-7
ii  libgpm2  1.20.7-10+b1
ii  libselinux1  3.4-1+b4
ii  libsodium23  1.0.18-1
ii  libtinfo66.4-1
ii  vim-common   2:9.0.1000-2
ii  vim-runtime  2:9.0.1000-2

vim recommends no packages.

Versions of packages vim suggests:
ii  universal-ctags [ctags]  5.9.20210829.0-1
ii  vim-doc  2:9.0.1000-2
ii  vim-scripts  20210124.2

-- no debconf information
set viminfo+=n~/.vim/viminfo
set termguicolors


filetype plugin on

highlight Normal guifg=White guibg=Black
syntax enable

autocmd ColorScheme * highlight ExtraWhitespace ctermbg=red guibg=red
highlight ExtraWhitespace ctermbg=red guibg=red
autocmd InsertEnter * match ExtraWhitespace /\s\+\%#\@  :silent :set hlsearch! hlsearch?:if 
ExtraWhitespace:match none:let ExtraWhitespace=0:else:match 
ExtraWhitespace /\s\+$\| \+\ze\t/:redraw!:let 
ExtraWhitespace=1:endif
"noremap   :silent :set hlsearch! hlsearch?

set nowrap
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:9.0.1000-3
Done: James McCoy 

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated vim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Jan 2023 10:15:51 -0500
Source: vim
Architecture: source
Version: 2:9.0.1000-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Closes: 1027766
Changes:
 vim (2:9.0.1000-3) unstable; urgency=medium
 .
   * Fix substitution of VIMCUR in vim-common.install (Closes: #1027766)
   * Backport v9.0.1129 to fix sporadic Test_range failure
Checksums-Sha1:
 2fb1a897c4b62c103f280c79a701df3087a76acb 3177 vim_9.0.1000-3.dsc
 f13de637d381e0f6a34218d360084583bbae836e 173388 vim_9.0.1000-3.debian.tar.xz
Checksums-Sha256:
 2638f3d7649e5d27d6f2bccd534922fe3befea3648256d817e33468c20cfed3b 3177 
vim_9.0.1000-3.dsc
 a25209d5dea7a03ebf4ad206582b0ac9c70aaa3dc58c78df9e7e90f8cfddb907 173388 
vim_9.0.1000-3.debian.tar.xz
Files:
 d6b48097fb1b83b5c45ce1883c7234e1 3177 editors optional 

Bug#1027793: marked as done (vim: insert mode: Backspace doesn't do anything)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 16:04:50 +
with message-id 
and subject line Bug#1027766: fixed in vim 2:9.0.1000-3
has caused the Debian Bug report #1027766,
regarding vim: insert mode: Backspace doesn't do anything
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.)


-- 
1027766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim
Version: 2:9.0.1000-2
Severity: normal
X-Debbugs-Cc: alx.manpa...@gmail.com

Hi,

This is not a bug in vim(1), since I can't reproduce it with --clean.
However, I can reproduce it with -u NONE, so I guess it's some plugin.
But I didn't install any plugins myself, so this is with whatever the
defaults are in Debian, I guess.

The issue is reproducible as:

(1)  Go to insert mode.
(2)  Press backspace.  It should remove a character; but doesn't.

Cheers,

Alex

-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.basic
/usr/bin/vim is /usr/bin/vim.basic

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 vim depends on:
ii  libacl1  2.3.1-2
ii  libc62.36-7
ii  libgpm2  1.20.7-10+b1
ii  libselinux1  3.4-1+b4
ii  libsodium23  1.0.18-1
ii  libtinfo66.4-1
ii  vim-common   2:9.0.1000-2
ii  vim-runtime  2:9.0.1000-2

vim recommends no packages.

Versions of packages vim suggests:
ii  universal-ctags [ctags]  5.9.20210829.0-1
pn  vim-doc  
pn  vim-scripts  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:9.0.1000-3
Done: James McCoy 

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated vim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Jan 2023 10:15:51 -0500
Source: vim
Architecture: source
Version: 2:9.0.1000-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Closes: 1027766
Changes:
 vim (2:9.0.1000-3) unstable; urgency=medium
 .
   * Fix substitution of VIMCUR in vim-common.install (Closes: #1027766)
   * Backport v9.0.1129 to fix sporadic Test_range failure
Checksums-Sha1:
 2fb1a897c4b62c103f280c79a701df3087a76acb 3177 vim_9.0.1000-3.dsc
 f13de637d381e0f6a34218d360084583bbae836e 173388 vim_9.0.1000-3.debian.tar.xz
Checksums-Sha256:
 2638f3d7649e5d27d6f2bccd534922fe3befea3648256d817e33468c20cfed3b 3177 
vim_9.0.1000-3.dsc
 a25209d5dea7a03ebf4ad206582b0ac9c70aaa3dc58c78df9e7e90f8cfddb907 173388 
vim_9.0.1000-3.debian.tar.xz
Files:
 d6b48097fb1b83b5c45ce1883c7234e1 3177 editors optional vim_9.0.1000-3.dsc
 1a2faeba011ba7bb502f39e032759848 173388 editors optional 
vim_9.0.1000-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmO0R95fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu
QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9vwsg//WZ2uFvDve9BuF8NUW9TjiVn+D9O0
ckeQjhqjlMeSdU0uozPkIPPzQe/NHIloz0oP/NwV4VW6xPces3bCsjLjSIitHyIF
en/rACFCH3jmM4UtegOY1WcYuW2pcyoEcLm7xq49KEobucOTAtPwRMAsi+Or1KUi
QXQeYf5w2+mNsC5NJcSobeXdZ/1IIYgPPiiy45RXyygvnhgtL/YgtCas1y1V2XIy
RsSVgK4Sinn85gEIbcr8zUZaFXlDXTYo1I41j2AxtB5X9VDPgFleiSUfDDQ6tC9R
B8fZAjbORf4XOUimaI9EpZGTkd+gFaAS8ty3IwI+2ojiIwca5hEdPyVU5ffG5DR2
FlE6CYvnI+SJ7efJ1cs+Fxpb5TWCG8wWL323WXOKOjx6juudtS7MF41TfsYw/waP
4S4kHhjnTadzP9GIRoy9YuS9OstNT03C4L4+VDPprwKKQtq2YwZ8eMPr8mjTjk1p
F5955iESvvh9N23QQFIXpBZdX4gpJZ+qhwgcL7wvk/EtzQNl6gvCJqAO25vk+/6W

Bug#1027771: marked as done (vim-common: debian.vim installed into the wrong directory)

[Debian Bug Tracking System]

Your message dated Tue, 03 Jan 2023 16:04:50 +
with message-id 
and subject line Bug#1027766: fixed in vim 2:9.0.1000-3
has caused the Debian Bug report #1027766,
regarding vim-common: debian.vim installed into the wrong directory
to be marked as done.

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

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


-- 
1027766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-ale
Version: 3.2.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

vim-ale is being very unhappy, this is a brand-new installation of the package, 
I previous used vim-syntastic but its going away.
I think it is assuming a particular vim version or some additional package 
installed.

My ~/.vimrc is merely:
packadd! ale

Whenever I try to edit any file I get:

Error detected while processing /usr/share/vim-ale/plugin/ale.vim:
line   48:
E697: Missing end of List ']': 
line   49:
E10: \ should be followed by /, ? or &
line   50:
E10: \ should be followed by /, ? or &
line   51:
E10: \ should be followed by /, ? or &
line   52:
E10: \ should be followed by /, ? or &
line   53:
E10: \ should be followed by /, ? or &
line   54:
E10: \ should be followed by /, ? or &
line  201:
E10: \ should be followed by /, ? or &
line  203:
E10: \ should be followed by /, ? or &
Error detected while processing 
/usr/share/vim-ale/plugin/ale.vim[331]..function ale#events#Init:
line   30:
E10: \ should be followed by /, ? or &

(hit enter)
".vimrc" 8L, 112B
Error detected while processing BufRead Autocommands for "*vimrc*"..function 
6_StarSetf[2]..FileType Autocommands for "*":
E116: Invalid arguments for function ale#events#FileTypeEvent
Error detected while processing BufRead Autocommands for "*"..function 
ale#events#ReadOrEnterEvent:
line3:
E33: No previous substitute regular expression
Error detected while processing BufWinEnter Autocommands for "*"..function 
ale#events#LintOnEnter[5]..ale#Queue[15]..ale#ShouldDoNothing:
line   60:
E488: Trailing characters: tbufvar(a:buffer, ':statusline') =~# 
'CtrlPMode.*funky'
Error detected while processing BufEnter Autocommands for "*"..function 
ale#events#ReadOrEnterEvent:
line3:
E33: No previous substitute regular expression


If I try to save my .vimrc file or edit a line:
".vimrc" 8L, 112B written
Error detected while processing BufWritePost Autocommands for "*"..function 
ale#events#SaveEvent[13]..ale#Queue[15]..ale#ShouldDoNothing:
line   60:
E488: Trailing characters: tbufvar(a:buffer, ':statusline') =~# 
'CtrlPMode.*funky'
Press ENTER or type command to continue






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

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=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vim-ale depends on:
ii  vim 2:9.0.1000-2
ii  vim-gtk3 [vim]  2:9.0.1000-2

vim-ale recommends no packages.

vim-ale suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmOzok8SHGNzbWFsbEBk
ZWJpYW4ub3JnAAoJEAIhZsD/PITj9oIP+wSMpboOjKFZQYV+z/K6z8D0Q6VJ2TPn
fH9BHblybBpXZxVJUo2RgM3OxxSsggatz1DY8P+92OuCjlwrFeCLG7Y47Q3A7auC
5N5AjsNgvZucGPF2DfflAvT1KFfEZha9+5SjKkUANc6aS8F1kWzXZyNql+y5mfrN
vgkJXxwRD3IGihQl43ET1esZ/D8qHO8dBSYTqbrFWmmnnq5j4AjZ48dJBx2gu46r
56lkSFilITptfXIgM2CNoAu/4e1NeyfsO2fwM7GqhypN4ZG6xIYSbJ+TtsmMiED5
K5s2zfqU1P9XKUJa0G0BgjkgkdZjB/EfDSdd0G99GchCMebK8htJJjrUF08Hqz24
cVm/Fo2hnCd06XVqzatHkHPlcH6lHT1YioiU63eRgmHUbCMLNcp+bS5LRZ384Csi
84QslM54J/Lzst4W75jnmlBtFAHxR9EdBIpAn0nNc20tlzfewd/BaN3eFCsUbqsf
vy1OKuRW5rejacXRo5CbYwcQdhiY7PHVEYh2lx5KE5YwrFSfwsr137cYgjCQkFPA
IgnTxFz0vkCc4KZMFY2bJF6VoMT0dOSwdyYVg3HsCZfgtfYmg+KotTgnMu5gOn5m
2f3+uCKXLyv8pGfe2J8ZjaxAJoN4ktLXiIGqeRS2j9Qd9OZ0JNULJWlO07j2lZjG
zeZgdBQpVOhL
=PKed
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:9.0.1000-3
Done: James McCoy 

We believe that the bug you reported is fixed in the latest version of
vim, 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