Bug#1028997: marked as done (python-glyphsets: (autopkgtest) needs update for Python 3.11)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 07:55:44 +
with message-id 
and subject line Bug#1028997: fixed in python-glyphsets 0.5.4-1
has caused the Debian Bug report #1028997,
regarding python-glyphsets: (autopkgtest) needs update for Python 3.11
to be marked as done.

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

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


-- 
1028997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-glyphsets
Version: 0.5.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Hi Maintainer

The autopkgtests of python-glyphsets fail with Python 3.11 as the
default version (and Python 3.10 still supported) [1].  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-glyphsets/testing/amd64/


Traceback (most recent call last):
  File "/usr/bin/glyphsets", line 33, in 
sys.exit(load_entry_point('glyphsets==0.5.2', 'console_scripts',
'glyphsets')())
 

  File "/usr/bin/glyphsets", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 205, in load
module = import_module(match.group('module'))
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1128, in _find_and_load_unlocked
  File "", line 241, in _call_with_frames_removed
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1149, in _find_and_load_unlocked
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/glyphsets/__init__.py", line
11, in 
import unicodedata2 as uni
ModuleNotFoundError: No module named 'unicodedata2'
--- End Message ---
--- Begin Message ---
Source: python-glyphsets
Source-Version: 0.5.4-1
Done: Agathe Porte 

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

Debian distribution maintenance software
pp.
Agathe Porte  (supplier of updated python-glyphsets 
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, 18 Jan 2023 08:08:31 +0100
Source: python-glyphsets
Binary: python3-glyphsets
Architecture: source all
Version: 0.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Agathe Porte 
Changed-By: Agathe Porte 
Description:
 python3-glyphsets - Python API for evaluating glyph sets in font projects
Closes: 1028990 1028997
Changes:
 python-glyphsets (0.5.4-1) unstable; urgency=medium
 .
   * Fix Vcs-Git and Vcs-Browser links
   * Update Standards-Version to 4.6.2 (no change)
   * Add missing B-D python3-unicodedata2 (Closes: #1028997)
   * Backport Ubuntu patch for unicodedata2 missing
   * New upstream version 0.5.4 (Closes: #1028990)
   * Update d/s/lintian-overrides
   * Update d/copyright year
Checksums-Sha1:
 6ab0ff14612fe6d442656b1880600df1b6bf9485 2306 python-glyphsets_0.5.4-1.dsc
 972ddf4a023337f7516627097e92771e14e9b6d6 1481737 
python-glyphsets_0.5.4.orig.tar.gz
 ead6f03d3467d7c6302d28b256fa99a71e255a85 5392 
python-glyphsets_0.5.4-1.debian.tar.xz
 d0889ccf1e95ce0442741d07be84325cf0b20420 8604 
python-glyphsets_0.5.4-1_amd64.buildinfo
 5e107ef40ff6bb668178d57f2f814ad33c3095ef 243856 
python3-glyphsets_0.5.4-1_all.deb
Checksums-Sha256:
 80b25f217567cc21ac21986c8a12f6795d4acb3a8dec6db1533825b543ba3625 2306 
python-glyphsets_0.5.4-1.dsc
 ef94592001924a0b20d6932938491dc79fb82d96caea2aa4f618fb4855e24716 1481737 
python-glyphsets_0.5.4.orig.tar.gz
 f69410e776299f290970

Bug#1027900: parole 4.16.0-2 does not start

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2023-01-04 at 15:12 +0300, Сергей Фёдоров wrote:
> parole 4.16.0-2 when running in the terminal emulator outputs :
> free(): invalid pointer
> Emergency stop
> 
> parole 4.16.0-1 is up and running.

Yes indeed, so we have an issue with -1 which doesn't build, and -2 which
doesn't run...

We'll try to investigate when possible.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPHo6QACgkQ3rYcyPpX
RFso8wf/a4WKNKwWJ0klpyxStGxtoGL2TVFU1JdB8I+iMsVdIjC+4DoZleLs55Tx
fMas2p0AdP7YrO7xcpHrdBLU4fcqHdmAGe3p5nda6oFhew2JfBVal5CCaZR74n80
kxUg3SIMiA8TGBiOk68x7dO6ukyYmWlzlcBVGnnoDLJbhNv71ZSsQDQ7UEYAllCx
9ZoIej0Yvev7eYomcRQQUiwehosBY+D/efaeQYNnZhnTaLkacWl6rzNZUYaSLoX3
H0xPBh/L2h9aGNYVR6aOdxj3juYeICVlFi876rcPLftVidtmoUgbcdgFx13fQzTW
AEYqe9m+qCFzE+ofdiViAa/ksRSKFQ==
=jQTc
-END PGP SIGNATURE-

Processed: Re: dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1028691 [src:dask.distributed] dask.distributed: FTBFS: unsatisfiable 
build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc
Ignoring request to alter tags of bug #1028691 to the same tags previously set

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

Bug#1028691: dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc

[Sebastiaan Couwenberg]

Control: tags -1 pending

python-numpy-doc has been dropped from the build dependencies in git, 
but the package FTBFS due to test failures. Those might be fixed in a 
new upstream release, but that may introduce regressions in its rdeps.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Bug#1028691 marked as pending in dask.distributed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028691 [src:dask.distributed] dask.distributed: FTBFS: unsatisfiable 
build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc
Added tag(s) pending.

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

Bug#1028691: marked as pending in dask.distributed

[Bas Couwenberg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/dask.distributed/-/commit/3a837c98b67f73d593cdabd0ca07553a427221b5


Drop obsolete python-numpy-doc build dependency. (closes: #1028691)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028691

Processed: Re: python-dtcwt: FTBFS: AttributeError: module 'numpy' has no attribute 'int'

[Debian Bug Tracking System]

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

> fixed 1028797 python-dtcwt/0.12.0-5
Bug #1028797 [src:python-dtcwt] python-dtcwt: FTBFS: AttributeError: module 
'numpy' has no attribute 'int'
Marked as fixed in versions python-dtcwt/0.12.0-5.
> thanks
Stopping processing here.

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

Bug#1029115: marked as done (linux-apfs-rw: autopkgtest failure on armel, armhf and i386)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 07:21:33 +
with message-id 
and subject line Bug#1029115: fixed in linux-apfs-rw 0+git20230118+ds-1
has caused the Debian Bug report #1029115,
regarding linux-apfs-rw: autopkgtest failure on armel, armhf and i386
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.)


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

Source: linux-apfs-rw
Version: 0+git20221028+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package linux-apfs-rw, great. 
However, it fails on armel, armhf and i386. Currently this failure is 
blocking the migration to testing [1]. Can you please investigate the 
situation and fix it?


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

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

Paul

[1] https://qa.debian.org/excuses.php?package=linux-apfs-rw

https://ci.debian.net/data/autopkgtest/testing/armel/l/linux-apfs-rw/30094133/log.gz

I: Removing binary package apfs-dkms, to get clean state.
I: Installing binary package apfs-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  apfs-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 96.0 kB of archives.
After this operation, 605 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main armel apfs-dkms all 
0+git20221028+ds-2 [96.0 kB]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 96.0 kB in 0s (1502 kB/s)
Selecting previously unselected package apfs-dkms.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29846 files and directories currently installed.)
Preparing to unpack .../apfs-dkms_0+git20221028+ds-2_all.deb ...
Unpacking apfs-dkms (0+git20221028+ds-2) ...
Setting up apfs-dkms (0+git20221028+ds-2) ...
autoinstall for dkms modules has been disabled.
I: Checking for missing dkms dependency by trying to deinstall dkms
dpkg: dependency problems prevent removal of dkms:
 apfs-dkms depends on dkms (>= 2.1.0.0).

dpkg: error processing package dkms (--remove):
 dependency problems - not removing
Errors were encountered while processing:
 dkms
I: No Linux header packages are installed.
I: Installing all available ones from src:linux 6.0.12-1:
I:   install linux-headers-6.0.0-6-marvell
I:   install linux-headers-6.0.0-6-rpi
I:   install linux-headers-marvell
I:   install linux-headers-rpi
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common linux-kbuild-6.0
The following NEW packages will be installed:
  linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common
  linux-headers-6.0.0-6-marvell linux-headers-6.0.0-6-rpi
  linux-headers-marvell linux-headers-rpi linux-kbuild-6.0
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.8 MB of archives.
After this operation, 64.8 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/main armel 
linux-compiler-gcc-12-arm armel 6.0.12-1 [556 kB]
Get:2 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-common all 6.0.12-1 [9655 kB]
Get:3 http://deb.debian.org/debian testing/main armel linux-kbuild-6.0 
armel 6.0.12-1 [789 kB]
Get:4 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-marvell armel 6.0.12-1 [881 kB]
Get:5 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-rpi armel 6.0.12-1 [867 kB]
Get:6 http://deb.debian.org/debian testing/main armel 
linux-headers-marvell armel 6.0.12-1 [1144 B]
Get:7 http://deb.debian.org/debian testing/main armel linux-headers-rpi 
armel 6.0.12-1 [1140 B]

debconf: delaying package configuration, since apt-utils is not instal

Processed: closing 1028821

[Debian Bug Tracking System]

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

> close 1028821
Bug #1028821 [pysurfer] pysurfer ftbfs with numpy 1.24
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1026657: marked as done (latexdraw: FTBFS: make: *** [debian/rules:8: build] Error 25)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 07:09:42 +
with message-id 
and subject line Bug#1026657: fixed in latexdraw 3.3.8+ds1-2
has caused the Debian Bug report #1026657,
regarding latexdraw: FTBFS: make: *** [debian/rules:8: build] Error 25
to be marked as done.

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

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


-- 
1026657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: latexdraw
Version: 3.3.8+ds1-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 '/<>'
> # First build the scala part
> cd latexdraw-core/net.sf.latexdraw && \
> mkdir -p target/classes && \
> CLASSPATH=.:\
> /usr/share/java/malai.core.jar:\
> /usr/share/java/malai.swing.jar:\
> /usr/share/java/pdfrenderer.jar \
>   scalac \
> -d target/classes \
> `find -name \*.scala -type f` \
> `find -name \*.java -type f`
> # Then get maven to build the java part
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/latexdraw-3.3.8\+ds1 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/latexdraw-3.3.8\+ds1/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/latexdraw-3.3.8\+ds1/debian 
> -Dmaven.repo.local=/<>/latexdraw-3.3.8\+ds1/debian/maven-repo 
> --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for net.sf.latexdraw:latexdraw.core:jar:3.3.8
> [WARNING] 'dependencies.dependency.systemPath' for 
> org.swinglabs:pdf-renderer:jar should use a variable instead of a hard-coded 
> path /usr/share/java/pdfrenderer.jar @ line 185, column 16
> [WARNING] 'dependencies.dependency.systemPath' for net.sf.jlibeps:jlibeps:jar 
> should use a variable instead of a hard-coded path 
> /usr/share/java/net.sourceforge.jlibeps.jar @ line 202, column 16
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] LaTeXDraw  
> [jar]
> [INFO] latexdraw  
> [pom]
> [INFO] 
> [INFO] --< net.sf.latexdraw:latexdraw.core 
> >---
> [INFO] Building LaTeXDraw 3.3.8   
> [1/2]
> [INFO] [ jar 
> ]-
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated 
> to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3
> [WARNING] The POM for org.malai:malai.swing:jar:debian is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ 
> latexdraw.core ---
> [INFO] Copying 319 resources
> [INFO] skip non existing resourceDirectory 
> /<>/latexdraw-core/net.sf.latexdraw/lib
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> latexdraw.core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 372 source files to 
> /<>/latexdraw-core/net.sf.latexdraw/target/classes
> [WARNING] 
> /<>/latexdraw-core/net.sf.latexdraw/src/main/net/sf/latexdraw/glib/views/Java2D/impl/LStandardGridView.java:[18,16]
>  sun.font.FontDesignMetrics is internal proprietary API and may be removed in 
> a future release
> [WARNING] 
> /<>/latexdraw-core/net.sf.latexdraw/src/main/net/sf/latexdraw/glib/views

Bug#1026688: marked as done (leaflet: FTBFS: SyntaxError: Cannot use import statement outside a module)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 07:09:54 +
with message-id 
and subject line Bug#1026688: fixed in leaflet 1.7.1~dfsg-7
has caused the Debian Bug report #1026688,
regarding leaflet: FTBFS: SyntaxError: Cannot use import statement outside a 
module
to be marked as done.

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

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


-- 
1026688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leaflet
Version: 1.7.1~dfsg-6
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 '/<>'
> NODE_ENV=release rollup --config build/rollup-config.js
> (node:1087360) Warning: To load an ES module, set "type": "module" in the 
> package.json or use the .mjs extension.
> (Use `node --trace-warnings ...` to show where the warning was created)
> [!] RollupError: Node tried to load your configuration file as 
> CommonJS even though it is likely an ES module. To resolve this, change the 
> extension of your configuration to ".mjs", set "type": "module" in your 
> package.json file or pass the "--bundleConfigAsCjs" flag.
> 
> Original error: Cannot use import statement outside a 
> module
> https://rollupjs.org/guide/en/#--bundleconfigascjs
> /<>/build/rollup-config.js:3
> import json from '@rollup/plugin-json'
> ^^
> 
> SyntaxError: Cannot use import statement outside a module
> at Object.compileFunction (node:vm:360:18)
> at wrapSafe (node:internal/modules/cjs/loader:1088:15)
> at Module._compile (node:internal/modules/cjs/loader:1123:27)
> at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
> at Module.load (node:internal/modules/cjs/loader:1037:32)
> at Module._load (node:internal/modules/cjs/loader:878:12)
> at ModuleWrap. (node:internal/modules/esm/translators:169:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
> at async Promise.all (index 0)
> at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
> 
> 
> make[1]: *** [debian/rules:30: dist/leaflet-src.esm.js] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/leaflet_1.7.1~dfsg-6_unstable.log

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

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

If you reassign this bug to another package, please 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: leaflet
Source-Version: 1.7.1~dfsg-7
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
leaflet, 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.
Yadd  (supplier of updated leaflet 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, 18 Jan 2023 09:35:16 +0400
Source: leaflet
Built-For-Profiles: nocheck
Architecture: source
Version: 1.7.1~dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1026688
Changes:
 leaflet (1.7.1~dfsg-7) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster:
 + Build-Depends: Drop versioned constraint on uglifyjs.
   * Apply multi-arch hints.
 + node-leaflet: Add :any

Bug#1026699: marked as done (leaflet-markercluster: FTBFS: SyntaxError: Cannot use import statement outside a module)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 07:10:02 +
with message-id 
and subject line Bug#1026699: fixed in leaflet-markercluster 1.5.3~dfsg-4
has caused the Debian Bug report #1026699,
regarding leaflet-markercluster: FTBFS: SyntaxError: Cannot use import 
statement outside a module
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pandoc --from gfm-raw_html --to html --standalone --output README.html 
> README.md
> [WARNING] This document format requires a nonempty  element.
>   Defaulting to 'README' as the title.
>   To specify a title, use 'title' in metadata or --metadata title="...".
> pandoc --from gfm-raw_html --to plain --output README.txt README.md
> NODE_ENV=release rollup --config build/rollup-config.js
> (node:1428487) Warning: To load an ES module, set "type": "module" in the 
> package.json or use the .mjs extension.
> (Use `node --trace-warnings ...` to show where the warning was created)
> [!] RollupError: Node tried to load your configuration file as 
> CommonJS even though it is likely an ES module. To resolve this, change the 
> extension of your configuration to ".mjs", set "type": "module" in your 
> package.json file or pass the "--bundleConfigAsCjs" flag.
> 
> Original error: Cannot use import statement outside a 
> module
> https://rollupjs.org/guide/en/#--bundleconfigascjs
> /<>/build/rollup-config.js:4
> import inject from '@rollup/plugin-inject';
> ^^
> 
> SyntaxError: Cannot use import statement outside a module
> at Object.compileFunction (node:vm:360:18)
> at wrapSafe (node:internal/modules/cjs/loader:1088:15)
> at Module._compile (node:internal/modules/cjs/loader:1123:27)
> at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
> at Module.load (node:internal/modules/cjs/loader:1037:32)
> at Module._load (node:internal/modules/cjs/loader:878:12)
> at ModuleWrap. (node:internal/modules/esm/translators:169:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
> at async Promise.all (index 0)
> at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
> 
> 
> make[1]: *** [debian/rules:18: dist/leaflet.markercluster-src.esm.js] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/leaflet-markercluster_1.5.3~dfsg-3_unstable.log

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

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

If you reassign this bug to another package, please 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: leaflet-markercluster
Source-Version: 1.5.3~dfsg-4
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
leaflet-markercluster, 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.
Yadd  (supplier of updated leaflet-markercluster 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, 18 Jan 2023 10:32:11 +0400
Source: leaflet-markercl

Bug#1026699: marked as pending in leaflet-markercluster

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/leaflet-markercluster/-/commit/4e3515aa690b81a62cdd2a5a97a8b74e7ae98bbd


Fix rollup configuration for rollup 3

Closes: #1026699


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026699

Processed: Bug#1026699 marked as pending in leaflet-markercluster

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026699 [src:leaflet-markercluster] leaflet-markercluster: FTBFS: 
SyntaxError: Cannot use import statement outside a module
Added tag(s) pending.

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

Bug#1027656: leaflet autoremoval

[Jonas Smedegaard]

Quoting Yadd (2023-01-18 06:40:14)
> On 1/16/23 09:34, Jonas Smedegaard wrote:
> > [replying via bugreport, to have the conversation public]
> > 
> > Quoting Sebastiaan Couwenberg (2023-01-16 05:54:07)
> >> Do either of you have time to look into fixing #1026688 which will cause
> >> autoremoval of leaflet and its rdeps?
> > 
> > I should be able to take time for that before its removal - but am happy
> > if others beat me to it.
> 
> Hi,
> 
> done, was just a missing rollup-3 patch (rollup.config updated to CJS)

Thanks!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

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

signature.asc
Description: signature

Bug#1027656: leaflet autoremoval

[Yadd]

On 1/16/23 09:34, Jonas Smedegaard wrote:

[replying via bugreport, to have the conversation public]

Quoting Sebastiaan Couwenberg (2023-01-16 05:54:07)

Do either of you have time to look into fixing #1026688 which will cause
autoremoval of leaflet and its rdeps?


I should be able to take time for that before its removal - but am happy
if others beat me to it.


Hi,

done, was just a missing rollup-3 patch (rollup.config updated to CJS)

Cheers,
Yadd

Bug#1026688: marked as pending in leaflet

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/leaflet/-/commit/7341a7cf65f0da8b3249ce08e8598d2b60e80018


Fix rollup configuration for rollup 3

Closes: #1026688


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026688

Processed: Bug#1026688 marked as pending in leaflet

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026688 [src:leaflet] leaflet: FTBFS: SyntaxError: Cannot use import 
statement outside a module
Added tag(s) pending.

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

Processed: tagging 1029104

[Debian Bug Tracking System]

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

> tags 1029104 + ftbfs
Bug #1029104 {Done: Rene Engelhard } [src:libreoffice] FTBFS 
with fontconfig 2.14.1 (doesn't expect RGB stripes
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1028809: marked as done (firefox-esr: FTBFS: ValueError: invalid mode: 'rU')

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 04:35:03 +
with message-id 
and subject line Bug#1028809: fixed in firefox-esr 102.7.0esr-1
has caused the Debian Bug report #1028809,
regarding firefox-esr: FTBFS: ValueError: invalid mode: 'rU'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> PYTHONIOENCODING=utf-8 LC_ALL=C.UTF-8 PYTHONDONTWRITEBYTECODE=y python3 
> debian/l10n/gen ach af an ar ast az be bg bn br bs ca ca-valencia cak cs cy 
> da de dsb el en-CA en-GB eo es-AR es-CL es-ES es-MX et eu fa ff fi fr fy-NL 
> ga-IE gd gl gn gu-IN he hi-IN hr hsb hu hy-AM ia id is it ja ka kab kk km kn 
> ko lij lt lv mk mr ms my nb-NO ne-NP nl nn-NO oc pa-IN pl pt-BR pt-PT rm ro 
> ru sco si sk sl son sq sr sv-SE szl ta te th tl tr trs uk ur uz vi xh zh-CN 
> zh-TW > debian/l10n/browser-l10n.control
> MOZ_OBJDIR=debian/objdir MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE=none 
> PYTHONDONTWRITEBYTECODE=y python3 ./mach python 
> python/mozbuild/mozbuild/preprocessor.py --marker % -Fsubstitution 
> -DGRE_VERSION="102"  -DPRODUCT_DOWNLOAD_NAME="firefox"  
> -Dbrowser="firefox-esr"  -DBROWSER="FIREFOX ESR"  -DBrowser="Firefox ESR"  
> -DMOZ_APP_REMOTINGNAME="Firefox-esr"  -DUSE_SYSTEM_FFI="1"  
> -DUSE_SYSTEM_LIBEVENT="1"  -DUSE_SYSTEM_NSPR="1"  -DUSE_SYSTEM_NSS="1"  
> -DUSE_SYSTEM_VPX="1"  -DUSE_SYSTEM_ZLIB="1"  -DSHORT_SOURCE_CHANNEL="esr102"  
> -DDIST="bookworm"  -DTRANSITION=""  -DMOZ_FFVPX="1"  -DCRASH_REPORTER="1"  
> -DDEB_HOST_ARCH="amd64"  -DL10N_PACKAGES_DEPS="firefox-esr-l10n-ach, 
> firefox-esr-l10n-af, firefox-esr-l10n-an, firefox-esr-l10n-ar, 
> firefox-esr-l10n-ast, firefox-esr-l10n-az, firefox-esr-l10n-be, 
> firefox-esr-l10n-bg, firefox-esr-l10n-bn, firefox-esr-l10n-br, 
> firefox-esr-l10n-bs, firefox-esr-l10n-ca, firefox-esr-l10n-ca-valencia, 
> firefox-esr-l10n-cak, firefox-esr-l10n-cs, firefox-esr-l10n-cy, 
> firefox-esr-l10n-da, firefox-esr-l10n-de, firefox-esr-l10n-dsb, 
> firefox-esr-l10n-el, firefox-esr-l10n-en-ca, firefox-esr-l10n-en-gb, 
> firefox-esr-l10n-eo, firefox-esr-l10n-es-ar, firefox-esr-l10n-es-cl, 
> firefox-esr-l10n-es-es, firefox-esr-l10n-es-mx, firefox-esr-l10n-et, 
> firefox-esr-l10n-eu, firefox-esr-l10n-fa, firefox-esr-l10n-ff, 
> firefox-esr-l10n-fi, firefox-esr-l10n-fr, firefox-esr-l10n-fy-nl, 
> firefox-esr-l10n-ga-ie, firefox-esr-l10n-gd, firefox-esr-l10n-gl, 
> firefox-esr-l10n-gn, firefox-esr-l10n-gu-in, firefox-esr-l10n-he, 
> firefox-esr-l10n-hi-in, firefox-esr-l10n-hr, firefox-esr-l10n-hsb, 
> firefox-esr-l10n-hu, firefox-esr-l10n-hy-am, firefox-esr-l10n-ia, 
> firefox-esr-l10n-id, firefox-esr-l10n-is, firefox-esr-l10n-it, 
> firefox-esr-l10n-ja, firefox-esr-l10n-ka, firefox-esr-l10n-kab, 
> firefox-esr-l10n-kk, firefox-esr-l10n-km, firefox-esr-l10n-kn, 
> firefox-esr-l10n-ko, firefox-esr-l10n-lij, firefox-esr-l10n-lt, 
> firefox-esr-l10n-lv, firefox-esr-l10n-mk, firefox-esr-l10n-mr, 
> firefox-esr-l10n-ms, firefox-esr-l10n-my, firefox-esr-l10n-nb-no, 
> firefox-esr-l10n-ne-np, firefox-esr-l10n-nl, firefox-esr-l10n-nn-no, 
> firefox-esr-l10n-oc, firefox-esr-l10n-pa-in, firefox-esr-l10n-pl, 
> firefox-esr-l10n-pt-br, firefox-esr-l10n-pt-pt, firefox-esr-l10n-rm, 
> firefox-esr-l10n-ro, firefox-esr-l10n-ru, firefox-esr-l10n-sco, 
> firefox-esr-l10n-si, firefox-esr-l10n-sk, firefox-esr-l10n-sl, 
> firefox-esr-l10n-son, firefox-esr-l10n-sq, firefox-esr-l10n-sr, 
> firefox-esr-l10n-sv-se, firefox-esr-l10n-szl, firefox-esr-l10n-ta, 
> firefox-esr-l10n-te, firefox-esr-l10n-th, firefox-esr-l10n-tl, 
> firefox-esr-l10n-tr, firefox-esr-l10n-trs, firefox-esr-l10n-uk, 
> firefox-esr-l10n-ur, firefox-esr-l10n-uz, firefox-esr-l10n-vi, 
> firefox-esr-l10n-xh, firefox-esr-l10n-zh-cn, firefox-esr-l10n-zh-tw"  
> -DPRODUCT="browser"  -DLIBAVCODEC="libavcodec59 | libavcodec-extra59 | 
> libavcodec58 | libavcodec-extra58 | libavcodec57 | libavcodec-extra57 | 
> libavcodec56 | libavcodec-extra56 | libavcodec55 | libavcodec-extra55 | 
> libavcodec54 | libavcodec-extra54 | libavcodec53 | libavcodec-extra53" 
> debian/control.in -o debian/control
> created virtual envi

Bug#1029122: scm: ftbfs on mipsel

[Bo YU]

Source: scm
Version: 5f2-3
Severity: serious 

Dear Maintainer,

The upload[0] cause a regression with build failure on mipsel:

```
...
make checklit
make[3]: Entering directory '/<>'
./scmlit -fr4rstest.scm -e'(test-sc4)(test-delay)(gc)' \
-e '(or (null? errs) (quit 1))' < /dev/null
remove
#define SHORT_INT
in scmfig.h and recompile scm
make[3]: *** [Makefile:553: checklit] Error 1
```

The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=scm&arch=mipsel&ver=5f3-3&stamp=1673937776&raw=0

I have fixed the issue on my local machine and upload it after testing it.
Thanks.

[0]: 
https://tracker.debian.org/news/1409807/accepted-scm-5f3-3-source-into-unstable/
-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1026669: request-tracker5: FTBFS: can't locate java: No such file or directory

[Ángel]

The error here is that ./debian/build-final-ckeditor.sh fails with
« can't locate java: No such file or directory »

This script is actually calling ckbuilder ( jexec /usr/bin/ckbuilder --
build ... )

However, the package correctly lists ckbuilder as a build-dep, and
ckbuilder itself depends on java ( default-jre | java{7..11}-runtime)

The full build log shows that java *was* installed, *and* that it
provided the usual suspects:

> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/java to provide /usr/bin/java (java) in auto mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/jpackage to provide /usr/bin/jpackage (jpackage) in auto
> mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry)
> in auto mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode

Bug#1029104: marked as done (FTBFS with fontconfig 2.14.1 (doesn't expect RGB stripes)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 02:04:33 +
with message-id 
and subject line Bug#1029104: fixed in libreoffice 1:7.4.4-2
has caused the Debian Bug report #1029104,
regarding FTBFS with fontconfig 2.14.1 (doesn't expect RGB stripes
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.)


-- 
1029104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig-config
Version: 2.14.1-3
Severity: serious
Justification: causes FTBFS
Tags: patch

Dear Maintainer,

See
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=amd64&ver=1%3A7.4.4-1&stamp=1673962775&raw=0:

[_RUN_] VclTextTest::testSimpleText
./vcl/qa/cppunit/text.cxx:222:VclTextTest::testSimpleText
double equality assertion failed
- Expected: 42
- Actual  : 37
- Delta   : 4

Indeed that also happens when I build it locally (unfortunately the C++
autopkgtests had to be disabled in libreoffice, otherwise they would
have catched it, too)

Downgrading to 2.13.1-4.5 "fixes" it.

Since other distributions already *do* ship 2.14.1 I looked what they
had and I came around

https://src.fedoraproject.org/rpms/fontconfig/c/25e368d9d2888159b5eb9acf3839821a4fe81c40?branch=rawhide

Indeed, when I added that ... into the already existing 
/etc/fonts/conf.d/10-sub-pixel-rgb.conf
the test passes.

Filing this as serious as it causes (autopkg)test failures. Which is bad
this late in the release cycle, especially for packages involved in
transitions like python3-defaults...

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:7.4.4-2
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 17 Jan 2023 21:01:57 +0100
Source: libreoffice
Architecture: source
Version: 1:7.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 1029104
Changes:
 libreoffice (1:7.4.4-2) unstable; urgency=medium
 .
   * fontconfig-2.14.1-no-RGB-stripes-layout-for-sub-pixel-rendering.diff:
 as name says, fix vcls testSimpleText with fontconfig-config 2.14.1-3
 (closes: #1029104). Apply before test and unapply after for now to not
 install it in fonts-opensymbol (as we for now are patching that file)
Checksums-Sha1:
 ddcbf4ae4c4dcbaa8cafbfd8b6d09a10e8d7dd13 22971 libreoffice_7.4.4-2.dsc
 804fa36695ae2266025f8f7898fefa67847e8b71 24738576 
libreoffice_7.4.4-2.debian.tar.xz
 96fc7529485420446d4566144974ca0afa94564b 34711 
libreoffice_7.4.4-2_source.buildinfo
Checksums-Sha256:
 ffef3e7fe5a237deab7baccc312df5ddf3c768783bb5c163c3653170dd18e7f2 22971 
libreoffice_7.4.4-2.dsc
 b12a9aa763d5c1aa29e1af7c817803b3befa50b2802231cbc9974f0460afb796 24738576 
libreoffice_7.4.4-2.debian.tar.xz
 16e61c1547d4644ce4d3336fd5f7d3447c5616da45b2e0743eff91e9ea8717f2 34711 
libreoffice_7.4.4-2_source.buildinfo
Files:
 f4e1cedfe192a9bf758f4475798e1cd7 22971 editors optional libreoffice_7.4.4-2.dsc
 a193f2cf74e020ba4e3e146fcc2176e9 24738576 editors optional 
libreoffice_7.4.4-2.debian.tar.xz
 042701698f4d2faf4a8db1f760396ea3 34711 editors optional 
libreoffice_7.4.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmPHSK0QHHJlbmVAZGVi
aWFuLm9yZwAKCRAKoEVx0D4+cBGhEACpmj2yWx2wqoGElmzOy+g2vNQH7rJ6msL7
tWNaRvwvGeCqHQL8AacqhjpB1siH59hKjDUsqI6pimgK0XTrTgQVjJsDWbYkpfu5
VLDjFJMr9y6At4Fbxwbq97uCUwClcYB1QDIz+9hVyE9QbQwHT9ImSaVLxib5pd/5
3qE8BrZGh8E9NnXktAuklcfk1IC1KmFgl/LrbLEMIcakErBKjm2fP5NEjQD61wff
1mLiJfd2cVONk/LJjE72XlrgtkD0RyYqzFzrBHAYcLs4kyQWAcU0wpAx9AeM5j57
SqgYn0FiyXWrrY0kEIM+xOGyEwPRHRTUT1TnbtW6ran5bx8CDp/Gk2a7JGF+GuQX
KZ0IivhRRW4ceU5U1PF/AC/TwIabC4PRh/bDakqgEfKl542Ccqx4joy/NGpcf8mL
7MMGEVvUbNz+cxZtljyqRozGqMa1+iu2eUEUrqeNOp3ESeS97mKNqFL084Kt9o20
Jo6NIsORtgweh8xRMYy1DX+kUf4Slfv1dFTfOh9iRZZVOR+z1xLDkjOp2EWabrae
YO5X2U4J0

Bug#1028607: marked as done (FTBFS: FAILED test-correct-notice and test-end-chop in copyright-tests.log due to new year 2023)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 01:53:10 +
with message-id 
and subject line Bug#1028607: fixed in emacs 1:28.2+1-10
has caused the Debian Bug report #1028607,
regarding FTBFS: FAILED test-correct-notice and test-end-chop in 
copyright-tests.log due to new year 2023
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.)


-- 
1028607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs
Version: 28.2+1-9
Severity: serious
Tags: ftbfs
Justification: ftbfs

When trying to rebuild emacs:

SUMMARY OF TEST RESULTS
---
Files examined: 375
Ran 5623 tests, 5545 results as expected, 2 unexpected, 76 skipped
1 files contained unexpected results:
  lisp/emacs-lisp/copyright-tests.log

and in this log file:

[...]
Test test-correct-notice condition:
(ert-test-failed
 ((should
   (equal
(with-temp-buffer ... ... ...)
"Copyright 2021 FSF\nCopyright 2021, 2022 FSF\n"))
  :form
  (equal "Copyright 2021 FSF\nCopyright 2021, 2023 FSF\n" "Copyright 2021 
FSF\nCopyright 2021, 2022 FSF\n")
  :value nil :explanation
  (array-elt 38
 (different-atoms
  (51 "#x33" "?3")
  (50 "#x32" "?2")
   FAILED  2/3  test-correct-notice (0.000103 sec)
[...]
Test test-end-chop condition:
(ert-test-failed
 ((should
   (equal
(with-temp-buffer ...)
"Copyright 2006, 2007, 2008, 2022 Foo Bar\n\n"))
  :form
  (equal "Copyright 2006, 2007, 2008, 2023 Foo Bar\n\n" "Copyright 2006, 
2007, 2008, 2022 Foo Bar\n\n")
  :value nil :explanation
  (array-elt 31
 (different-atoms
  (51 "#x33" "?3")
  (50 "#x32" "?2")
   FAILED  3/3  test-end-chop (0.000154 sec)
[...]
2 unexpected results:
   FAILED  test-correct-notice
   FAILED  test-end-chop

This comes from test/lisp/emacs-lisp/copyright-tests.el, which has

(ert-deftest test-end-chop ()
  (should
   (equal
(with-temp-buffer
  (let ((copyright-query nil))
(insert (make-string (- copyright-limit 14) ?x) "\n"
"\nCopyright 2006, 2007, 2008 Foo Bar\n\n")
(copyright-update)
(buffer-substring (- (point-max) 42) (point-max
"Copyright 2006, 2007, 2008, 2022 Foo Bar\n\n")))

(ert-deftest test-correct-notice ()
  (should (equal
   (with-temp-buffer
 (dotimes (_ 2)
   (insert "Copyright 2021 FSF\n"))
 (let ((copyright-at-end-flag t)
   (copyright-query nil))
   (copyright-update))
 (buffer-string))
   "Copyright 2021 FSF\nCopyright 2021, 2022 FSF\n")))

The cause may be that we are now in 2023 and the above tests
are expecting 2022. Instead of expecting 2022, shouldn't they
expect the current year?

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

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Running 3 tests (2023-01-13 15:46:41+0100, selector ‘(not (or (tag 
:expensive-test) (tag :unstable)))’)
   passed  1/3  test-copyright-update (0.372676 sec)
Test test-correct-notice backtrace:
  signal(ert-test-failed (((should (equal (with-temp-buffer (dotimes (
  ert-fail(((should (equal (with-temp-buffer (dotimes (_ 2) (insert "C
  #f(compiled-function () #)()
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name test-correct-notice :documentation ni
  ert-run-or-rerun-test(#s(ert--stats :selector (not (or (tag :expensi
  ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
  ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
  ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
  command-line-1(("-L" ":/home/vinc17/tmp/emacs-28.2+1/debian/build-sr
  command-line()
  normal-top-level()
Test test-c

Bug#1029112: Surprise build issue with ibus-libzhuyin

[Osamu Aoki]

Hi,

Debian official packages are required to build without downloading external
files during their build.  (Builddd is in isolated network environment only with
access to the Debian package repository.


> Tags: ftbfs

So if it requires wget file access, it is ftbfs.  Don't make build script to do
this.   ... (continue to the bottom).

> Making all in model
> make[4]: Entering directory '/<>/data/model'
> wget http://downloads.sourceforge.net/libzhuyin/models/model13.text.tar.gz
> /bin/bash: line 1: wget: command not found
> 
> And yes, it's true that wget is not included in Build-Depends. But 
> previously that has not been needed. This is from the buildlog for the 
> latest successful build:
> 
> Making all in model
> make[4]: Entering directory '/<>/data/model'
> rm -f phrase_index.bin pinyin_index.bin addon_phrase_index.bin 
> addon_pinyin_index.bin bigram.db tsi.bin
> gen_binary_files --table-dir ../../data/model
> import_interpolation --table-dir ../../data/model < 
> ../../data/model/interpolation2.text
> gen_unigram --table-dir ../../data/model
> 
> or just:
> 
> Making check in model
> make[3]: Entering directory '/<>/data/model'
> make[3]: Nothing to be done for 'check'.
> 
> I have not found any code changes which would explain the new behavior. 
> And when trying (in an Ubuntu PPA) to add wget to Build-Depends, it 
> failed to resolve the download URL. (It builds fine on my harddisk, though.)
> 
> I figured out that this patch would help it build successfully:
> 
> --- a/data/Makefile.am
> +++ b/data/Makefile.am
> @@ -27,7 +27,6 @@
> 
>    SUBDIRS = \
>    icons \
> -    model \
>    $(NULL)
> 
>    appdatadir = @datadir@/appdata
> 
> But since I don't know how that would affect the functionality of the 
> package, I have left it in its failed state for now.
> 
> In other words: I need help to solve this.


If I were you, I will build package "without this mod in an environment with
wget included as Build-dep" and "with this mod only without wget in chroot". 
Then I will check resulting binary packages.

If these generated packages contain different model data, then you need to
modify code to use pre-existing data and download such model data in advance to
be included in debian/ directory.  Of course, you need to check license terms of
such model data and document it.

If these contain same model data, your proposed fix should be OK.

Regards,

Osamu

Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

[Helge Deller]

On Sat, 14 Jan 2023 20:38:38 +0100 Andreas Henriksson  wrote:

Here's a slightly different patch to implement basically the same thing


Yes, I like this patch better too.

Helge

Bug#1029112: marked as done (Surprise build issue with ibus-libzhuyin)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2023 00:22:19 +
with message-id 
and subject line Bug#1029112: fixed in ibus-libzhuyin 1.10.2+ds-1
has caused the Debian Bug report #1029112,
regarding Surprise build issue with ibus-libzhuyin
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.)


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

Package: src:ibus-libzhuyin
Version: 1.10.2-1
Severity: serious
Tags: ftbfs

Hello!

ibus-libzhuyin 1.10.2-1 failed to build. This is the relevant part of 
the buildlog:


Making all in model
make[4]: Entering directory '/<>/data/model'
wget http://downloads.sourceforge.net/libzhuyin/models/model13.text.tar.gz
/bin/bash: line 1: wget: command not found

And yes, it's true that wget is not included in Build-Depends. But 
previously that has not been needed. This is from the buildlog for the 
latest successful build:


Making all in model
make[4]: Entering directory '/<>/data/model'
rm -f phrase_index.bin pinyin_index.bin addon_phrase_index.bin 
addon_pinyin_index.bin bigram.db tsi.bin

gen_binary_files --table-dir ../../data/model
import_interpolation --table-dir ../../data/model < 
../../data/model/interpolation2.text

gen_unigram --table-dir ../../data/model

or just:

Making check in model
make[3]: Entering directory '/<>/data/model'
make[3]: Nothing to be done for 'check'.

I have not found any code changes which would explain the new behavior. 
And when trying (in an Ubuntu PPA) to add wget to Build-Depends, it 
failed to resolve the download URL. (It builds fine on my harddisk, though.)


I figured out that this patch would help it build successfully:

--- a/data/Makefile.am
+++ b/data/Makefile.am
@@ -27,7 +27,6 @@

  SUBDIRS = \
  icons \
-model \
  $(NULL)

  appdatadir = @datadir@/appdata

But since I don't know how that would affect the functionality of the 
package, I have left it in its failed state for now.


In other words: I need help to solve this.

--
Rgds,
Gunnar
--- End Message ---
--- Begin Message ---
Source: ibus-libzhuyin
Source-Version: 1.10.2+ds-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated ibus-libzhuyin 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, 17 Jan 2023 18:34:23 -0500
Source: ibus-libzhuyin
Architecture: source
Version: 1.10.2+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Closes: 1029112
Changes:
 ibus-libzhuyin (1.10.2+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * debian/watch: Add downloadurlmangle to monitor tarball provided
 in releases page instead, which includes necessary data files.
 (Closes: #1029112)
 - Append +ds for current upload for now.
Checksums-Sha1:
 66b8773dfc6a2056ebcd0dc00459b1d469934a90 2166 ibus-libzhuyin_1.10.2+ds-1.dsc
 42e47843add9c781d4187ed84fd20781c8fc520d 16090950 
ibus-libzhuyin_1.10.2+ds.orig.tar.gz
 6b4e384cf234854b40ffbc646b94e539023e3c9a 3372 
ibus-libzhuyin_1.10.2+ds-1.debian.tar.xz
 1c354a454adb57009630192c41c7c7220474b327 8855 
ibus-libzhuyin_1.10.2+ds-1_amd64.buildinfo
Checksums-Sha256:
 75618ae5cb4e3800bff0df7ada0904e4c322696f6a701f725d9a2765f25b5fc5 2166 
ibus-libzhuyin_1.10.2+ds-1.dsc
 50f4fd07174699f46937906f9430a5d3c1d95da6cdb94efa713c8514a969b262 16090950 
ibus-libzhuyin_1.10.2+ds.orig.tar.gz
 9ee7d6ec0ddf9ed4318f11815944849f18e17dec98201e1040d373a0a73cea01 3372 
ibus-libzhuyin_1.10.2+ds-1.debian.tar.xz
 a4692b4fb65cb8a7af3f39df805f38010235ed9c440108465460baf1852d98e3 8855 
ibus-libzhuyin_1.10.2+ds-1_amd64.buildinfo
Files:
 3e44b85650139a078f6b9c05629e5b92 2166 utils optional 
ibus-libzhuyin_1.10.2+ds-1.dsc
 1c3505d0913c6e4898cccace07a227e1 16090950 utils optional 
ibus-libzhuyin_1.10.2+ds.orig.tar.gz
 db4cbf50daab2792bbf20fb637214798 3372 utils optional 
ibus-libzhuyin_1.10.2+ds-1.debian.tar.xz
 01a95ddf02d40eeff15bdfa61

Bug#1028758: marked as done (mozjs78: FTBFS with python3.11 as default: ValueError: invalid mode: 'rU')

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 23:46:43 +
with message-id 
and subject line Bug#1028308: fixed in mozjs78 78.15.0-6
has caused the Debian Bug report #1028308,
regarding mozjs78: FTBFS with python3.11 as default: ValueError: invalid mode: 
'rU'
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.)


-- 
1028308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs78
Version: 78.15.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>   CXX=x86_64-linux-gnu-g++ \
>   RUST_HOST=x86_64-unknown-linux-gnu \
>   RUST_TARGET=x86_64-unknown-linux-gnu \
> /bin/sh /<>/js/src/configure \
>   --host=x86_64-linux-gnu \
>   --target=x86_64-linux-gnu \
>   --prefix=/usr \
>   --libdir=/usr/lib/x86_64-linux-gnu/ \
>   --with-system-zlib \
>   --disable-strip \
>   --with-intl-api \
>   --enable-readline \
>   --disable-jemalloc \
>   --without-system-icu \
> ; then \
>   echo Configure successful; \
> else \
>   echo Configure failed with status $?; \
>   tail -v -n +0 config.log; \
>   exit 1; \
> fi
> Creating Python 3 environment
> created virtual environment CPython3.11.1.final.0-64 in 211ms
>   creator 
> CPython3Posix(dest=/<>/debian/build/_virtualenvs/init_py3, 
> clear=False, global=False)
>   seeder FromAppData(download=False, pip=bundle, setuptools=bundle, 
> wheel=bundle, via=copy, app_data_dir=/tmp/tmpuyka5ihg)
> added seed packages: pip==20.2.2, setuptools==49.6.0, wheel==0.35.1
>   activators 
> BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator
> /<>/python/mozbuild/mozbuild/virtualenv.py:697: 
> 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.version import LooseVersion
> /<>/python/mozbuild/mozbuild/virtualenv.py:316: 
> DeprecationWarning: The distutils.sysconfig module is deprecated, use 
> sysconfig instead
>   import distutils.sysconfig
> b"running build_ext\nbuilding 'psutil._psutil_linux' extension\ncreating 
> build\ncreating build/temp.linux-x86_64-3.11\ncreating 
> build/temp.linux-x86_64-3.11/psutil\nx86_64-linux-gnu-gcc -Wsign-compare 
> -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DPSUTIL_POSIX=1 -DPSUTIL_SIZEOF_PID_T=4 -DPSUTIL_VERSION=570 
> -DPSUTIL_LINUX=1 
> -I/<>/debian/build/_virtualenvs/init_py3/include 
> -I/usr/include/python3.11 -c psutil/_psutil_common.c -o 
> build/temp.linux-x86_64-3.11/psutil/_psutil_common.o\nx86_64-linux-gnu-gcc 
> -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong 
> -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DPSUTIL_POSIX=1 -DPSUTIL_SIZEOF_PID_T=4 -DPSUTIL_VERSION=570 
> -DPSUTIL_LINUX=1 
> -I/<>/debian/build/_virtualenvs/init_py3/include 
> -I/usr/include/python3.11 -c psutil/_psutil_linux.c -o 
> build/temp.linux-x86_64-3.11/psutil/_psutil_linux.o\nx86_64-linux-gnu-gcc 
> -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong 
> -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DPSUTIL_POSIX=1 -DPSUTIL_SIZEOF_PID_T=4 -DPSUTIL_VERSION=570 
> -DPSUTIL_LINUX=1 
> -I/<>/debian/build/_virtualenvs/init_py3/include 
> -I/usr/include/python3.11 -c psutil/_psutil_posix.c -o 
> build/temp.linux-x86_64-3.11/psutil/_psutil_posix.o\ncreating 
> build/lib.linux-x86_64-3.11\ncreating 
> build/lib.linux-x86_64-3.11/psutil\nx86_64-linux-gnu-gcc -shared -Wl,-O1 
> -Wl,-Bsymbolic-functions -g -fwrapv -O2 -g -fwrapv -O2 -g 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.11/psutil/_psutil_common.o 
> build/temp.linux-x86_64-3.11/psutil/_psutil_linux.o 
> build/temp.linux-x86_64-3.11/psutil/_psutil_posix.o -o 
> build/lib.linux-x86_64-3.11/psutil/_psutil_linux.cpython-311-x86_64-linux-gnu.so\nbuilding
>  'psutil._psutil_posix' extension\nx86_64-linux-gnu-gcc -Wsign-compare 

Bug#1028308: marked as done (mozjs78: FTBFS with python 3.11)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 23:46:43 +
with message-id 
and subject line Bug#1028308: fixed in mozjs78 78.15.0-6
has caused the Debian Bug report #1028308,
regarding mozjs78: FTBFS with python 3.11
to be marked as done.

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

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


-- 
1028308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs78
Version: 78.15.0-5
Severity: serious
Tags: ftbfs

mozjs78 FTBFS since Python 3.11 became the default Python3 version in
sid. The relevant part of the build log is pasted below.

Incidentally, src:0ad happens to FTBFS for the same reason because it
embeds mozjs/spidermonkey [1]. You can see how we fixed this in 0ad
(unfortunately this involves cherry-picking an upstream commit to
upgrade virtualenv) [2].

```
checking for valloc in malloc.h... yes
checking for valloc in unistd.h... no
checking for _aligned_malloc in malloc.h... no
updating cache ./config.cache
creating ./config.data
Creating config.status
Traceback (most recent call last):
  File "/build/mozjs78-78.15.0/js/src/../../configure.py", line 181, in 
sys.exit(main(sys.argv))
 ^^
  File "/build/mozjs78-78.15.0/js/src/../../configure.py", line 57, in main
return config_status(config)
   ^
  File "/build/mozjs78-78.15.0/js/src/../../configure.py", line 142,
in config_status
partial_config.write_vars(sanitized_config)
  File 
"/build/mozjs78-78.15.0/python/mozbuild/mozbuild/backend/configenvironment.py",
line 361, in write_vars
self.substs._fill_group(substs)
  File 
"/build/mozjs78-78.15.0/python/mozbuild/mozbuild/backend/configenvironment.py",
line 257, in _fill_group
new_files.add(self._write_file(k, v))
  ^^
  File 
"/build/mozjs78-78.15.0/python/mozbuild/mozbuild/backend/configenvironment.py",
line 240, in _write_file
with FileAvoidWrite(filename) as fh:
  File "/build/mozjs78-78.15.0/python/mozbuild/mozbuild/util.py", line
338, in __exit__
self.close()
  File "/build/mozjs78-78.15.0/python/mozbuild/mozbuild/util.py", line
261, in close
existing = _open(self.name, self.mode)
   ^^^
  File "/build/mozjs78-78.15.0/python/mozbuild/mozbuild/util.py", line
59, in _open
return io.open(path, mode, encoding='utf-8', newline='\n')
   ^^^
ValueError: invalid mode: 'rU'
Configure failed with status 1
```

Regards,
Vincent

[1] https://bugs.debian.org/1028179
[2] 
https://salsa.debian.org/games-team/0ad/-/commit/7048ef33282782d9af46335c9d928dfa9d9f379d
--- End Message ---
--- Begin Message ---
Source: mozjs78
Source-Version: 78.15.0-6
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated mozjs78 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, 17 Jan 2023 17:26:39 -0500
Source: mozjs78
Built-For-Profiles: noudeb
Architecture: source
Version: 78.15.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1028308
Changes:
 mozjs78 (78.15.0-6) unstable; urgency=medium
 .
   * Add patch to fix build with Python 3.11 (Closes: #1028308)
Checksums-Sha1:
 68d920c1fbe7e47642da74fe270ab3d666f0956b 2319 mozjs78_78.15.0-6.dsc
 62cf79fa40c400a5ecf0b35e017182fb0d20b171 65232 mozjs78_78.15.0-6.debian.tar.xz
 d3f2f729e6a79c3378e04883c7ad43f6ccb32876 11901 
mozjs78_78.15.0-6_source.buildinfo
Checksums-Sha256:
 a5c1f9260fe8bff9c78e4379e55b891bd231784b59cdbe396237ba6874c75696 2319 
mozjs78_78.15.0-6.dsc
 741cc79be228ff96a127d52148e7c24e7cfd9c770ed0c4e040a6607cf7d445f4 65232 
mozjs78_78.15.0-6.debian.tar.xz
 683c4cb3fb77ad1b31f8233708ca884b7609750f2cf4f545e10351f9abdf256a 11901 
mozjs78_78.15.0-6_source.buildinfo
Files:
 53bf5af34d61b9ff093ced870ff0d2ca 2319 libs optional mozjs78_78.15.0-6.dsc
 2385afb495b7caf5bb8c111605aec20

Bug#1029015: marked as done (qtmir-tests: Depends on NBS package python3-mir-perf-framework)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 22:48:59 +
with message-id 
and subject line Bug#1029015: fixed in qtmir 0.8.0~git20230115.30c2337-2
has caused the Debian Bug report #1029015,
regarding qtmir-tests: Depends on NBS package python3-mir-perf-framework
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.)


-- 
1029015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtmir-tests
Version: 0.8.0~git20230115.30c2337-1
Severity: serious
Justification: Policy 3.5

qtmir-tests depends on python3-mir-perf-framework which is no longer
built by the mir package.  Once it's decrufted, the package will not be
installable.  Please either drop the dependency or coordinate with the
mir maintainers to get python3-mir-perf-framework restored.

Scott K
--- End Message ---
--- Begin Message ---
Source: qtmir
Source-Version: 0.8.0~git20230115.30c2337-2
Done: Marius Gripsgard 

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

Debian distribution maintenance software
pp.
Marius Gripsgard  (supplier of updated qtmir 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, 17 Jan 2023 22:18:34 +
Source: qtmir
Built-For-Profiles: noudeb
Architecture: source
Version: 0.8.0~git20230115.30c2337-2
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Marius Gripsgard 
Closes: 1029015
Changes:
 qtmir (0.8.0~git20230115.30c2337-2) unstable; urgency=medium
 .
   * debian/control: Drop mir-pref-framework from qtmir-tests (closes: #1029015)
Checksums-Sha1:
 3b6d4f153a41b5d9064d0811b01f7c0337fe8dab 3349 
qtmir_0.8.0~git20230115.30c2337-2.dsc
 c0c517a719036e702696f693b4ded52d4deb68e1 252072 
qtmir_0.8.0~git20230115.30c2337.orig.tar.xz
 e1cfaadba6b3e99df055febb573aaa38122f23d2 40396 
qtmir_0.8.0~git20230115.30c2337-2.debian.tar.xz
 cc9e820e0d4bc1e298ad3def21ac3707760e365c 22247 
qtmir_0.8.0~git20230115.30c2337-2_source.buildinfo
Checksums-Sha256:
 be766dac3d056d6353154fdf13ec37480136b919fddff36457cc3117ba24e574 3349 
qtmir_0.8.0~git20230115.30c2337-2.dsc
 141f4dc53257d10e71180d6b15936d709d29d824e8bbe7e2e34cd70a3e732d8f 252072 
qtmir_0.8.0~git20230115.30c2337.orig.tar.xz
 4c344533aca1b292c1fe3d09eb3c073ccf4f79accf0679c4278c65720c6ca890 40396 
qtmir_0.8.0~git20230115.30c2337-2.debian.tar.xz
 48a8d3916e8fd185cd33ac77d2c1c19890c4d7e65a8929cc8d22ac1b1bdbeefb 22247 
qtmir_0.8.0~git20230115.30c2337-2_source.buildinfo
Files:
 803ef446dd2225cd4a77947e58936dfd 3349 libs optional 
qtmir_0.8.0~git20230115.30c2337-2.dsc
 5a4b3cc79b11ab006ab089fd6077bc9e 252072 libs optional 
qtmir_0.8.0~git20230115.30c2337.orig.tar.xz
 3154a73494771940f8590144d2d5b644 40396 libs optional 
qtmir_0.8.0~git20230115.30c2337-2.debian.tar.xz
 9d90128ac6dd6745e18c40d3fe389f70 22247 libs optional 
qtmir_0.8.0~git20230115.30c2337-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEm65oPpnDJVLXb56DuvnOw/aSJ4kFAmPHHt8THG1hcml1c0B1
YnBvcnRzLmNvbQAKCRC6+c7D9pInid4hEAC0xBC55Y+7V3PvDBGx5kdfUCz9767F
Tv0/Dev8+JtjEojwyYqdbaUqhwEyD5jRC1oRhv7si0nnYhNSz6ggs/2jyEiuFgZM
s72cdJBDck3//M52tFLNirvdjkxqEcdQEjXiw30Gw9ZXK2Q5NvQFOBENl401vld6
AHPodAlLTI3d19A/NCslB+7iYrWfVcHbK/47H2h4DeJYj8Yue3obRv9dImfINGEA
K/dbq8d1wUTVzTOwYSDvwOGkV0lQcfgpGMXlg//AacN/8U7WUIyVwv9jhJyYhiia
5cTl1RyYQfciuutOFRSzqSONzT6gcX3OZKEzHF9nvhhdfPZJ94TOgwHguDoE8Z+f
S5ky8C4k1DRhNo7zEOj8Oz4SpOpofp4P4RP4cl2xoUADu5wRyv1EU0qrcFUMZ9mX
ZdS5mTnfCjdtRrN/AjNf6jDMz8LaEzdAgWFikn9No1UbJWonLxQEtBgEFR4zLcqo
qOcY6G+WyzXesSBRS21xIGWhKlgNDMm9vS1958JWcGlcruh4VC1dldMDGLx1YGjJ
WdtYpG+CUBOwlS9xf8dt8Cjs6e6/uPRiCTkHJwN0p6xahXCcPw3bowB0mDwCqolN
+XF99iw/cCqhkiQmiMW+kX3esnO9j+/bmrzqwIQeT+Y7YSBhISaiDh5yaZYGXQnJ
4gx6bGYyEcgy8A==
=rZSc
-END PGP SIGNATURE End Message ---

Bug#1026585: marked as done (gfxreconstruct: FTBFS: generated_vulkan_enum_to_string.cpp:2006:10: error: ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR’ was not declared in this scope; did you mean ‘VK_STRUCTURE

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 22:42:23 +
with message-id 
and subject line Bug#1026585: fixed in gfxreconstruct 0.9.16.1+dfsg-1
has caused the Debian Bug report #1026585,
regarding gfxreconstruct: FTBFS: generated_vulkan_enum_to_string.cpp:2006:10: 
error: ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR’ was not declared in this scope; 
did you mean ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_INFO_KHR’?
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.)


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

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/framework/decode && /usr/bin/c++ 
> -DENABLE_LZ4_COMPRESSION -DENABLE_ZLIB_COMPRESSION -DENABLE_ZSTD_COMPRESSION 
> -DPAGE_GUARD_ENABLE_UCONTEXT_WRITE_DETECTION -DVK_ENABLE_BETA_EXTENSIONS 
> -DVK_NO_PROTOTYPES -DVK_USE_PLATFORM_DISPLAY_KHR -DVK_USE_PLATFORM_HEADLESS 
> -DVK_USE_PLATFORM_WAYLAND_KHR -DVK_USE_PLATFORM_XCB_KHR 
> -DVK_USE_PLATFORM_XLIB_KHR -DVK_USE_PLATFORM_XLIB_XRANDR_EXT 
> -DWAYLAND_LIBRARY=\"/usr/lib/x86_64-linux-gnu/libwayland-client.so\" 
> -DX11_XCB_LIBRARY=\"/usr/lib/x86_64-linux-gnu/libX11-xcb.so\" 
> -DXCB_KEYSYMS_LIBRARY=\"/usr/lib/x86_64-linux-gnu/libxcb-keysyms.so\" 
> -DXCB_LIBRARY=\"/usr/lib/x86_64-linux-gnu/libxcb.so\" -D_FILE_OFFSET_BITS=64 
> -I/<>/framework 
> -I/<>/external/Vulkan-Headers/include 
> -I/<>/external/VulkanMemoryAllocator/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security "-Wno-error=stringop-overflow=" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -Werror -std=gnu++14 -MD -MT 
> framework/decode/CMakeFiles/gfxrecon_decode.dir/__/generated/generated_vulkan_enum_to_string.cpp.o
>  -MF 
> CMakeFiles/gfxrecon_decode.dir/__/generated/generated_vulkan_enum_to_string.cpp.o.d
>  -o 
> CMakeFiles/gfxrecon_decode.dir/__/generated/generated_vulkan_enum_to_string.cpp.o
>  -c /<>/framework/generated/generated_vulkan_enum_to_string.cpp
> [ 73%] Linking CXX static library libgfxrecon_encode.a
> cd /<>/obj-x86_64-linux-gnu/framework/encode && /usr/bin/cmake 
> -P CMakeFiles/gfxrecon_encode.dir/cmake_clean_target.cmake
> cd /<>/obj-x86_64-linux-gnu/framework/encode && /usr/bin/cmake 
> -E cmake_link_script CMakeFiles/gfxrecon_encode.dir/link.txt --verbose=1
> /usr/bin/ar qc libgfxrecon_encode.a 
> CMakeFiles/gfxrecon_encode.dir/capture_manager.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/capture_settings.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/custom_vulkan_api_call_encoders.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/custom_vulkan_command_buffer_util.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/custom_vulkan_struct_encoders.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/custom_vulkan_struct_handle_wrappers.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/vulkan_capture_manager.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/vulkan_handle_wrapper_util.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/vulkan_state_tracker.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/vulkan_state_writer.cpp.o 
> CMakeFiles/gfxrecon_encode.dir/__/generated/generated_encode_pnext_struct.cpp.o
>  
> CMakeFiles/gfxrecon_encode.dir/__/generated/generated_vulkan_api_call_encoders.cpp.o
>  
> CMakeFiles/gfxrecon_encode.dir/__/generated/generated_vulkan_command_buffer_util.cpp.o
>  
> CMakeFiles/gfxrecon_encode.dir/__/generated/generated_vulkan_struct_encoders.cpp.o
>  
> CMakeFiles/gfxrecon_encode.dir/__/generated/generated_vulkan_struct_handle_wrappers.cpp.o
> /usr/bin/ranlib libgfxrecon_encode.a
> /<>/framework/generated/generated_vulkan_enum_to_string.cpp: In 
> function ‘std::string gfxrecon::util::ToString(const T&, ToStringFlags, 
> uint32_t, uint32_t) [with T = VkStructureType; std::string = 
> std::__cxx11::basic_string; ToStringFlags = unsigned int; uint32_t = 
> unsigned int]’:
> /<>/framework/generated/generated_vulkan_enum_to_string.cpp:2006:10:
>  error: ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR’ was not declared in this scope; 
> did you mean ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_INFO_KHR’?
>  2006 | case VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR: return 
> "VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR";
>   |  ^~~
>   |  VK_STRUCTURE_TYPE_VIDEO_PROFILE_INFO_KHR
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> /<>/framework/generated/generated_vulkan_enum_

Bug#1029006: marked as done (bpy: couldn't find 'scripts/modules', blender probably won't start)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 22:35:37 +
with message-id 
and subject line Bug#1029006: fixed in blender 3.4.1+dfsg-2
has caused the Debian Bug report #1029006,
regarding bpy: couldn't find 'scripts/modules', blender probably won't start
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.)


-- 
1029006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blender-data
Version: 3.4.1+dfsg-1
Severity: grave
Justification: renders package unusable

Blender has no menus, and the only reaction to mouse-movement or keypresses is
an "WM_keymap_poll: empty keymap" error to stdout/stderr. The logs to
stdout/stderr start with:

$ blender
bpy: couldn't find 'scripts/modules', blender probably won't start.
Freestyle: couldn't find 'scripts/freestyle/modules', Freestyle won't work 
properly.
ModuleNotFoundError: No module named 'bpy_types'
ModuleNotFoundError: No module named 'bpy_types'

It seems a lot of directories that 3.3.1 put in /u/s/b/scripts have
ended up down a level in /u/s/b/scripts/scripts instead:

/usr/share/blender/scripts:
drwxr-xr-x 3 root root 4096 Jan 16 15:05 addons
drwxr-xr-x 9 root root 4096 Jan 16 15:05 scripts

/usr/share/blender/scripts/scripts:
drwxr-xr-x 64 root root 4096 Jan 16 15:05 addons
drwxr-xr-x  4 root root 4096 Jan 16 15:05 freestyle
drwxr-xr-x 12 root root 4096 Jan 16 15:05 modules
drwxr-xr-x 19 root root 4096 Jan 16 15:05 presets
drwxr-xr-x  5 root root 4096 Jan 16 15:05 startup
drwxr-xr-x  2 root root 4096 Jan 16 15:05 templates_osl
drwxr-xr-x  2 root root 4096 Jan 16 15:05 templates_py

Symlinking the directories up a level didn't fix everything (I didn't resolve
the two "addons" directories), but was enough to show the menus and react to
input.

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

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

Versions of packages blender-data depends on:
ii  python3  3.11.1-1

blender-data recommends no packages.

blender-data suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: blender
Source-Version: 3.4.1+dfsg-2
Done: Matteo F. Vescovi 

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated blender 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, 17 Jan 2023 22:34:10 +0100
Source: blender
Architecture: source
Version: 3.4.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Matteo F. Vescovi 
Closes: 1029006
Changes:
 blender (3.4.1+dfsg-2) unstable; urgency=medium
 .
   * debian/patches/: patchset updated (Closes: #1029006)
Checksums-Sha1:
 cfd96d6aced9ce4865181f9f84dff38c16779b4f 3139 blender_3.4.1+dfsg-2.dsc
 4459d268339ed015c9dc4cd416bbf62b3dacbaef 34380 
blender_3.4.1+dfsg-2.debian.tar.xz
 324241c38290585f96393764b55d7c56faebd162 8260 
blender_3.4.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 9abc656ddfc210facd7ece4a5526d4bafdca0f195bc14b16d37947113579331f 3139 
blender_3.4.1+dfsg-2.dsc
 6728e8524de2c2e810e276a0ab6b5e8035541b6e148cf3bf52689bfd75de40b8 34380 
blender_3.4.1+dfsg-2.debian.tar.xz
 dd13650f7ace44029e02893c3822cc08f2dbfe3a17183c65bf18121b21f40e27 8260 
blender_3.4.1+dfsg-2_source.buildinfo
Files:
 db0d2bfce935587a831b8ff04f311efe 3139 graphics optional 
blender_3.4.1+dfsg-2.dsc
 f6522f8059758414e0d073eddc56b18c 34380 graphics optional 
blender_3.4.1+dfsg-2.debian.tar.xz
 8cfa68437569454ebe55f3c74e1888db 8260 graphics optional 
blender_3.4.1+dfsg-2_source.buildinfo

Bug#1029006: marked as pending in blender

[Matteo F. Vescovi]

Control: tag -1 pending

Hello,

Bug #1029006 in blender 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/multimedia-team/blender/-/commit/5a80283f8096f9214cb4336f96644f64b5e38fb9


debian/patches/: patchset updated

Closes: #1029006


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029006

Processed: Bug#1029006 marked as pending in blender

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029006 [blender-data] bpy: couldn't find 'scripts/modules', blender 
probably won't start
Added tag(s) pending.

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

Bug#1028716: marked as done (mozjs102: FTBFS with python3.11 as default: ValueError: invalid mode: 'rU')

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 22:09:21 +
with message-id 
and subject line Bug#1028716: fixed in mozjs102 102.7.0-1
has caused the Debian Bug report #1028716,
regarding mozjs102: FTBFS with python3.11 as default: ValueError: invalid mode: 
'rU'
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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: unrecognized option '--icf=safe'
> /usr/bin/ld: use the --help option for usage information
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/mozjs102_102.6.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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: mozjs102
Source-Version: 102.7.0-1
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated mozjs102 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, 17 Jan 2023 15:57:16 -0500
Source: mozjs102
Built-For-Profiles: noudeb
Architecture: source
Version: 102.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1028716
Changes:
 mozjs102 (102.7.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Cherry-pick patch to fix build with Python 3.11 (Closes: #1028716)
   * Re-export upstream signing key without extra signatures
   * Update standards version to 4.6.2, no changes needed
Checksums-Sha1:
 4e48a335c57a5f2d6b0e633f759bb72a1575f370 2274 mozjs102_102.7.0-1.dsc
 5c931de12449cf1fd29c431ffdd4efd63b11614a 145639804 mozjs102_102.7.0.orig.tar.xz
 c5c6470bcd90078e8d02f06f6dd63a80c1d8e2f3 54324 mozjs102_102.7.0-1.debian.tar.xz
 985bc5a3bc3d3c823bf9f6fb6fe56fed2c9bf910 11905 
mozjs102_102.7.0-1_source.buildinfo
Checksums-Sha256:
 a7b72d4008d4181b1accbb6f7561706c725596691fd8467e3904ab6c39f1bb03 2274 
mozjs102_102.7.0-1.dsc
 931fa8be3009979b4674d949e8adfb4c289904ba7d37c20c2dd716e36e8d208a 145639804 
mozjs102_102.7.0.orig.tar.xz
 37802aed35827675c298bacc02ee41fb5f56d75f37af0b2fa574e9cfd8e54c4b 54324 
mozjs102_102.7.0-1.debian.tar.xz
 c1f4aef96e497606c6df55c23502c9b940a082fbe22f1dbb9b2228dd100ce4b8 11905 
mozjs102_102.7.0-1_source.buildinfo
Files:
 c8b725dc9f2e99486c1875eaa5943d41 2274 libs optional mozjs102_102.7.0-1.dsc
 d02cd4dce6ccb8aefa262f142ec6f7f4 145639804 libs optional 
mozjs102_102.7.0.orig.tar.xz
 baef668c48ede564d832015ab096b997 54324 libs optional 
mozjs102_102.7.0-1.debian.tar.xz
 b17ee06287aec676d3ef70dc260f32d6 11905 libs optional 
mozjs102_102.7.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmPHC+4ACgkQ5mx3Wuv+
bH2mIw/9Hzeu179CjuzIjiS3PvqCSKR45P/wgfyM9tiN8i2jd3JKdD6XCVmfhZlN
v9SAs/gyIIcp0EsjxX62/AwxAAn8pdovqq97GgUk2auBCvjHMEdiviDNJACbhTbX
xh+5FWFgXivLJjq0u/Bq2aUfEbpquUVl+ZcPq7qyVyxGJMalV9pboqQtHlHdFnSR
Qp+6rkEVf

Processed: Re: Bug#1027760: gortr appears to be unmaintained

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1027760 [src:gortr] gortr appears to be unmaintained
Severity set to 'important' from 'serious'
> affects -1 cfrpki
Bug #1027760 [src:gortr] gortr appears to be unmaintained
Added indication that 1027760 affects cfrpki

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

Bug#1027760: gortr appears to be unmaintained

[Marco d'Itri]

Control: severity -1 important
Control: affects -1 cfrpki

On Jan 03, Marco d'Itri  wrote:

> gortr has not been updated upstream in over two years and probably most
> users at this point have switched to stayrtr for good.
But cfrpki build-depends on golang-github-cloudflare-gortr-dev, so let's 
ignore this for the time being.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Processed: Re: Bug#1029046: Wayland session doesn't get back to life post-suspend

[Debian Bug Tracking System]

Processing control commands:

> found -1 6.1.6-1
Bug #1029046 [src:linux] Wayland session doesn't get back to life post-suspend
The source 'linux' and version '6.1.6-1' do not appear to match any binary 
packages
Marked as found in versions linux/6.1.6-1.
> found -1 6.1.4-1
Bug #1029046 [src:linux] Wayland session doesn't get back to life post-suspend
Ignoring request to alter found versions of bug #1029046 to the same values 
previously set
> severity -1 serious
Bug #1029046 [src:linux] Wayland session doesn't get back to life post-suspend
Severity set to 'serious' from 'important'

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

Bug#996799: twitterwatch - upload needed

[Emmanuel Arias]

Hi,

On Tue, Jan 17, 2023 at 6:16 PM Malik  wrote:

> Hello Emmanuel,
>
> currently upstream-author has no plan to update or release any further
> releases for this project [1]
>
Ok

>
>

> [1] https://gitlab.com/chaica/twitterwatch/-/issues/1
>
> kind regards,
> Malik
>

If you leave the package as is it now, when a new release exists, d/watch
won't note it.
So, I'd change the d/watch to the Gitlab repository. Also Homepage link.

Cheers,
Emmanuel

Processed: pysurfer was still affected by numpy 1.24

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pysurfer 0.11.0-3
Bug #1028821 {Done: Étienne Mollier } [mayavi2] mayavi2 
missing python3.11 support causes pysurfer ftbfs
Bug reassigned from package 'mayavi2' to 'pysurfer'.
No longer marked as found in versions mayavi2/4.8.0-1.1.
No longer marked as fixed in versions mayavi2/4.8.0-2.
Bug #1028821 {Done: Étienne Mollier } [pysurfer] mayavi2 
missing python3.11 support causes pysurfer ftbfs
There is no source info for the package 'pysurfer' at version '0.11.0-3' with 
architecture ''
Unable to make a source version for version '0.11.0-3'
Marked as found in versions 0.11.0-3.
> retitle -1 pysurfer ftbfs with numpy 1.24
Bug #1028821 {Done: Étienne Mollier } [pysurfer] mayavi2 
missing python3.11 support causes pysurfer ftbfs
Changed Bug title to 'pysurfer ftbfs with numpy 1.24' from 'mayavi2 missing 
python3.11 support causes pysurfer ftbfs'.
> found -1 0.11.0-3
Bug #1028821 {Done: Étienne Mollier } [pysurfer] 
pysurfer ftbfs with numpy 1.24
There is no source info for the package 'pysurfer' at version '0.11.0-3' with 
architecture ''
Unable to make a source version for version '0.11.0-3'
Did not alter found versions and reopened.
> fixed -1 0.11.0-4
Bug #1028821 [pysurfer] pysurfer ftbfs with numpy 1.24
There is no source info for the package 'pysurfer' at version '0.11.0-4' with 
architecture ''
Unable to make a source version for version '0.11.0-4'
Marked as fixed in versions 0.11.0-4.

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

Bug#1028821: pysurfer was still affected by numpy 1.24

[Étienne Mollier]

Control: reassign -1 pysurfer 0.11.0-3
Control: retitle -1 pysurfer ftbfs with numpy 1.24
Control: found -1 0.11.0-3
Control: fixed -1 0.11.0-4

Hi,

I'm under the impression I was not well inspired to reassing the
present bug to mayavi2, because pysurfer still used to ftbfs
after the mayavi2 update.  Thankfully this has been fixed by Bas
patch and Nilesh's upload already.

Besides, it seems that I accidentally entangled a migration
between mayavi2 and pysurfer, which is forbidden at this stage
of the release I believe.  If need be, I'll check with the
Release Team.

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


signature.asc
Description: PGP signature

Bug#1029115: linux-apfs-rw: autopkgtest failure on armel, armhf and i386

[Salvatore Bonaccorso]

Hi,

On Tue, Jan 17, 2023 at 10:22:41PM +0100, Paul Gevers wrote:
> Source: linux-apfs-rw
> Version: 0+git20221028+ds-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
> 
> Dear maintainer(s),
> 
> You recently added an autopkgtest to your package linux-apfs-rw, great.
> However, it fails on armel, armhf and i386. Currently this failure is
> blocking the migration to testing [1]. Can you please investigate the
> situation and fix it?
> 
> I copied some of the output at the bottom of this report.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=linux-apfs-rw
> 
> https://ci.debian.net/data/autopkgtest/testing/armel/l/linux-apfs-rw/30094133/log.gz
> 
> I: Removing binary package apfs-dkms, to get clean state.
> I: Installing binary package apfs-dkms
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following NEW packages will be installed:
>   apfs-dkms
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 96.0 kB of archives.
> After this operation, 605 kB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian unstable/main armel apfs-dkms all
> 0+git20221028+ds-2 [96.0 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 96.0 kB in 0s (1502 kB/s)
> Selecting previously unselected package apfs-dkms.
> (Reading database ... (Reading database ... 5%
> (Reading database ... 10%
> (Reading database ... 15%
> (Reading database ... 20%
> (Reading database ... 25%
> (Reading database ... 30%
> (Reading database ... 35%
> (Reading database ... 40%
> (Reading database ... 45%
> (Reading database ... 50%
> (Reading database ... 55%
> (Reading database ... 60%
> (Reading database ... 65%
> (Reading database ... 70%
> (Reading database ... 75%
> (Reading database ... 80%
> (Reading database ... 85%
> (Reading database ... 90%
> (Reading database ... 95%
> (Reading database ... 100%
> (Reading database ... 29846 files and directories currently installed.)
> Preparing to unpack .../apfs-dkms_0+git20221028+ds-2_all.deb ...
> Unpacking apfs-dkms (0+git20221028+ds-2) ...
> Setting up apfs-dkms (0+git20221028+ds-2) ...
> autoinstall for dkms modules has been disabled.
> I: Checking for missing dkms dependency by trying to deinstall dkms
> dpkg: dependency problems prevent removal of dkms:
>  apfs-dkms depends on dkms (>= 2.1.0.0).
> 
> dpkg: error processing package dkms (--remove):
>  dependency problems - not removing
> Errors were encountered while processing:
>  dkms
> I: No Linux header packages are installed.
> I: Installing all available ones from src:linux 6.0.12-1:
> I:   install linux-headers-6.0.0-6-marvell
> I:   install linux-headers-6.0.0-6-rpi
> I:   install linux-headers-marvell
> I:   install linux-headers-rpi
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following additional packages will be installed:
>   linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common linux-kbuild-6.0
> The following NEW packages will be installed:
>   linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common
>   linux-headers-6.0.0-6-marvell linux-headers-6.0.0-6-rpi
>   linux-headers-marvell linux-headers-rpi linux-kbuild-6.0
> 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
> Need to get 12.8 MB of archives.
> After this operation, 64.8 MB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian testing/main armel
> linux-compiler-gcc-12-arm armel 6.0.12-1 [556 kB]
> Get:2 http://deb.debian.org/debian testing/main armel
> linux-headers-6.0.0-6-common all 6.0.12-1 [9655 kB]
> Get:3 http://deb.debian.org/debian testing/main armel linux-kbuild-6.0 armel
> 6.0.12-1 [789 kB]
> Get:4 http://deb.debian.org/debian testing/main armel
> linux-headers-6.0.0-6-marvell armel 6.0.12-1 [881 kB]
> Get:5 http://deb.debian.org/debian testing/main armel
> linux-headers-6.0.0-6-rpi armel 6.0.12-1 [867 kB]
> Get:6 http://deb.debian.org/debian testing/main armel linux-headers-marvell
> armel 6.0.12-1 [1144 B]
> Get:7 http://deb.debian.org/debian testing/main armel linux-headers-rpi
> armel 6.0.12-1 [1140 B]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 12.8 MB in 0s (31.3 MB/s)
> Selecting previously unselected package linux-compiler-gcc-12-arm.
> (Reading database ... (Reading database ... 5%
> (Reading database ... 10%
> (Reading database ... 15%
> (Reading database ... 20%
> (Reading database ... 25%
> (Reading database ... 30%
> (Reading database ... 35%
> (Reading database ... 40%
> (Reading database ... 45%
> (Reading database ... 50%
> (Reading database ... 55%
> (Reading database ... 60%
> (Reading database ... 65%
> (Reading database ... 70%
> (Reading database ... 75%
> (Reading database ... 80%
> (Rea

Bug#1029115: linux-apfs-rw: autopkgtest failure on armel, armhf and i386

[Paul Gevers]

Source: linux-apfs-rw
Version: 0+git20221028+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package linux-apfs-rw, great. 
However, it fails on armel, armhf and i386. Currently this failure is 
blocking the migration to testing [1]. Can you please investigate the 
situation and fix it?


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

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

Paul

[1] https://qa.debian.org/excuses.php?package=linux-apfs-rw

https://ci.debian.net/data/autopkgtest/testing/armel/l/linux-apfs-rw/30094133/log.gz

I: Removing binary package apfs-dkms, to get clean state.
I: Installing binary package apfs-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  apfs-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 96.0 kB of archives.
After this operation, 605 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main armel apfs-dkms all 
0+git20221028+ds-2 [96.0 kB]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 96.0 kB in 0s (1502 kB/s)
Selecting previously unselected package apfs-dkms.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29846 files and directories currently installed.)
Preparing to unpack .../apfs-dkms_0+git20221028+ds-2_all.deb ...
Unpacking apfs-dkms (0+git20221028+ds-2) ...
Setting up apfs-dkms (0+git20221028+ds-2) ...
autoinstall for dkms modules has been disabled.
I: Checking for missing dkms dependency by trying to deinstall dkms
dpkg: dependency problems prevent removal of dkms:
 apfs-dkms depends on dkms (>= 2.1.0.0).

dpkg: error processing package dkms (--remove):
 dependency problems - not removing
Errors were encountered while processing:
 dkms
I: No Linux header packages are installed.
I: Installing all available ones from src:linux 6.0.12-1:
I:   install linux-headers-6.0.0-6-marvell
I:   install linux-headers-6.0.0-6-rpi
I:   install linux-headers-marvell
I:   install linux-headers-rpi
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common linux-kbuild-6.0
The following NEW packages will be installed:
  linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common
  linux-headers-6.0.0-6-marvell linux-headers-6.0.0-6-rpi
  linux-headers-marvell linux-headers-rpi linux-kbuild-6.0
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.8 MB of archives.
After this operation, 64.8 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/main armel 
linux-compiler-gcc-12-arm armel 6.0.12-1 [556 kB]
Get:2 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-common all 6.0.12-1 [9655 kB]
Get:3 http://deb.debian.org/debian testing/main armel linux-kbuild-6.0 
armel 6.0.12-1 [789 kB]
Get:4 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-marvell armel 6.0.12-1 [881 kB]
Get:5 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-rpi armel 6.0.12-1 [867 kB]
Get:6 http://deb.debian.org/debian testing/main armel 
linux-headers-marvell armel 6.0.12-1 [1144 B]
Get:7 http://deb.debian.org/debian testing/main armel linux-headers-rpi 
armel 6.0.12-1 [1140 B]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 12.8 MB in 0s (31.3 MB/s)
Selecting previously unselected package linux-compiler-gcc-12-arm.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29875 files and directories currently installed.)
Preparing to unpack .../0-linux-compiler-gcc-12-arm_6.0.12-1_armel.deb ...
Unpacking linux-compiler-gcc-12-arm (6.0.12-1) ...

Processed: git: CVE-2022-23521 CVE-2022-41903

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:2.39.0-1
Bug #1029114 [src:git] git: CVE-2022-23521 CVE-2022-41903
Marked as found in versions git/1:2.39.0-1.

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

Bug#1029114: git: CVE-2022-23521 CVE-2022-41903

[Salvatore Bonaccorso]

Source: git
Version: 1:2.30.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:2.39.0-1

Hi,

The following vulnerabilities were published for git.

CVE-2022-23521[0]:
| gitattributes parsing integer overflow

CVE-2022-41903[1]:
| heap overflow in `git archive` and `git log --format`

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-23521
https://www.cve.org/CVERecord?id=CVE-2022-23521
[1] https://security-tracker.debian.org/tracker/CVE-2022-41903
https://www.cve.org/CVERecord?id=CVE-2022-41903

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#996799: twitterwatch - upload needed

[Malik]

Hello Emmanuel,

currently upstream-author has no plan to update or release any further
releases for this project [1]

[1] https://gitlab.com/chaica/twitterwatch/-/issues/1

kind regards,
Malik

Am So., 15. Jan. 2023 um 13:28 Uhr schrieb Emmanuel Arias <
eam...@yaerobi.com>:

> Hi,
>
> On Sun, Jan 15, 2023 at 12:24:43PM +0100, Malik wrote:
> > Hello Emannauel,
> >
> > Thank you for the suggestions.
> >
> > I was not sure how to handle the new homepage [1]  since there are no
> tags
> > or releases maintained by the upstream maintainer, should I delete the
> > watchfile? or can I watch the version in the setup.py ?
>
> Oh, I didn't note it. Perhaps it's a good reason to contact to upstream
> and ask for them. Don't remove d/watch file.
>
> >
> > And for the tests, should I mock the calls to the "internet" since those
> > would be skipped if conceited to the internet
>
> Yes, or skip them.
> >
> >
> > [1]: https://gitlab.com/chaica/twitterwatch/-/tags
> >
> > regards,
> > Malik
> >
>
> Cheers,
> Emmanuel
>


-- 
Malik Mlitat

Bug#1028710: marked as done (jackd2: FTBFS: ValueError: invalid mode: 'rUb')

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 21:10:22 +
with message-id 
and subject line Bug#1028710: fixed in jackd2 1.9.21~dfsg-2
has caused the Debian Bug report #1028710,
regarding jackd2: FTBFS: ValueError: invalid mode: 'rUb'
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.)


-- 
1028710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackd2
Version: 1.9.21~dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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 '/<>'
> python3 ./waf configure \
>   --prefix=/usr --classic --example-tools \
>   --libdir=/usr/lib/x86_64-linux-gnu \
>   --alsa --dbus --firewire \
>   CC='x86_64-linux-gnu-gcc' CXX='x86_64-linux-gnu-g++' 
> PKGCONFIG='x86_64-linux-gnu-pkg-config'
> Waf: The wscript in '/<>' is unreadable
> Traceback (most recent call last):
>   File "/<>/waflib/Scripting.py", line 141, in waf_entry_point
> set_main_module(wscript)
>   File "/<>/waflib/Scripting.py", line 191, in set_main_module
> Context.g_module = Context.load_module(file_path)
>^^
>   File "/<>/waflib/Context.py", line 665, in load_module
> code = Utils.readf(path, m='rU', encoding=encoding)
>
>   File "/<>/waflib/Utils.py", line 231, in readf
> with open(fname, m) as f:
>  ^^
> ValueError: invalid mode: 'rUb'
> make[1]: *** [debian/rules:22: override_dh_auto_configure] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/jackd2_1.9.21~dfsg-1_unstable.log

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

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

If you reassign this bug to another package, please 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: jackd2
Source-Version: 1.9.21~dfsg-2
Done: Dennis Braun 

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

Debian distribution maintenance software
pp.
Dennis Braun  (supplier of updated jackd2 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, 17 Jan 2023 21:34:44 +0100
Source: jackd2
Architecture: source
Version: 1.9.21~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 1028710
Changes:
 jackd2 (1.9.21~dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Bump Standards-Version to 4.6.2
   * Fix FTBFS: ValueError: invalid mode: 'rUb' (Closes: #1028710)
Checksums-Sha1:
 89c275fe11d83047d92ca6d04a9a63751018c79d 2545 jackd2_1.9.21~dfsg-2.dsc
 aa6664be87ec9388390fd87bd67d45f345dcff51 33880 
jackd2_1.9.21~dfsg-2.debian.tar.xz
 f9873995fcbb02facaf39dc8f58ed27a3d0f4ad1 6842 
jackd2_1.9.21~dfsg-2_source.buildinfo
Checksums-Sha256:
 f947e5fa3f97d9de69535853fe77361444670e64a6679f770a0350338b3528df 2545 
jackd2_1.9.21~dfsg-2.dsc
 ed4bea02acb46afb05959668428ce3f11ecf77b0fe224f63588dbc326da98380 33880 
jackd2_1.9.21~dfsg-2.debian.tar.xz
 6422a033b542eb4bca07e4db59bc8b9d172c6e5545162839e2201dd072fbbb37 6842 
jackd2_1.9.21~dfsg-2_source.buildinfo
Files:
 10165114c107416ba3b3a2916ffa751a 2545 sound optional jackd2_1.9.21~dfsg-2.

Bug#1029112: Surprise build issue with ibus-libzhuyin

[Gunnar Hjalmarsson]

Package: src:ibus-libzhuyin
Version: 1.10.2-1
Severity: serious
Tags: ftbfs

Hello!

ibus-libzhuyin 1.10.2-1 failed to build. This is the relevant part of 
the buildlog:


Making all in model
make[4]: Entering directory '/<>/data/model'
wget http://downloads.sourceforge.net/libzhuyin/models/model13.text.tar.gz
/bin/bash: line 1: wget: command not found

And yes, it's true that wget is not included in Build-Depends. But 
previously that has not been needed. This is from the buildlog for the 
latest successful build:


Making all in model
make[4]: Entering directory '/<>/data/model'
rm -f phrase_index.bin pinyin_index.bin addon_phrase_index.bin 
addon_pinyin_index.bin bigram.db tsi.bin

gen_binary_files --table-dir ../../data/model
import_interpolation --table-dir ../../data/model < 
../../data/model/interpolation2.text

gen_unigram --table-dir ../../data/model

or just:

Making check in model
make[3]: Entering directory '/<>/data/model'
make[3]: Nothing to be done for 'check'.

I have not found any code changes which would explain the new behavior. 
And when trying (in an Ubuntu PPA) to add wget to Build-Depends, it 
failed to resolve the download URL. (It builds fine on my harddisk, though.)


I figured out that this patch would help it build successfully:

--- a/data/Makefile.am
+++ b/data/Makefile.am
@@ -27,7 +27,6 @@

  SUBDIRS = \
  icons \
-model \
  $(NULL)

  appdatadir = @datadir@/appdata

But since I don't know how that would affect the functionality of the 
package, I have left it in its failed state for now.


In other words: I need help to solve this.

--
Rgds,
Gunnar

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Sebastian Reichel]

Hi,

On Sat, 14 Jan 2023 21:53:59 + Martin  wrote:
> Control: severity -1 normal
> 
> The problem disappeared magically for all users who reported it before.
> I assume, that there is a hidden bug in libproxy, that only appears in
> certain circumstances. Downgrading for now.

I just got the new package through testing and now gajim segfaults
ony my system with stacktrace pointing to libproxy. So this is not
magically solved.

-- Sebastian


signature.asc
Description: PGP signature

Bug#1029109: cimg: build dependency gone after tiff transition

[Paul Gevers]

Source: cimg
Version: 3.1.6+dfsg-6
Severity: serious
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 some Build-Depends for some while now. Not being able 
to build from source in a suite is an RC bug in that suite.


Your package Build-Depends on a particular SONAME of the tiff library, 
but that was dropped in the last tiff transition. Are you sure you need 
to Build-Depends on the library, it's already pulled in via the tiff 
header package.


Can you please solve the situation by either helping the maintainer of 
your Build-Depends to enable migration to testing, or by working around 
the lack of this build dependency?


Paul

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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1028451: 2nd DisplayPort doesn't get video

[Paul Gevers]

Hi,

On 17-01-2023 07:14, Salvatore Bonaccorso wrote:

I will bite the bullet (taking full responsibility for it if
necessary, don't blame the other kernel team members) and ask here now
the release team: Can we let linux 6.1.4-1 despite the RC bug
reported, migrate to testing, so we can move on to 6.1.y?


I have added the hints. linux should migrate in the 22:00 UTC britney run.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#1028716 marked as pending in mozjs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028716 [src:mozjs102] mozjs102: FTBFS with python3.11 as default: 
ValueError: invalid mode: 'rU'
Added tag(s) pending.

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

Bug#1029066: diffoscope: FTBFS if no internet is available (using internet connection during build)

[Vagrant Cascadian]

Control: found 1029066 230

On 2023-01-17, Gianfranco Costamagna wrote:
> Hello, your package FTBFS when internet is not available during control file 
> regeneration phase
...
> debian/tests/control.sh
> Generating the debian/tests/control file...
...
> ERROR: Could not find a version that satisfies the requirement setuptools 
> (from versions: none)
> ERROR: No matching distribution found for setuptools
> Traceback (most recent call last):
>File "", line 1, in 
>File "/usr/lib/python3/dist-packages/pep517/meta.py", line 72, in load
>  path = Path(build_as_zip(builder))
>  ^
>File "/usr/lib/python3/dist-packages/pep517/meta.py", line 59, in 
> build_as_zip
>  builder(dest=out_dir)
>File "/usr/lib/python3/dist-packages/pep517/meta.py", line 53, in build
>  env.pip_install(system['requires'])
>File "/usr/lib/python3/dist-packages/pep517/envbuild.py", line 103, in 
> pip_install
>  check_call(
>File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
>  raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'pip', 
> 'install', '--ignore-installed', '--prefix', 
> '/tmp/pep517-build-env-i1vz1wye', 'setuptools', 'wheel']' returned non-zero 
> exit status 1.
> Files debian/tests/control and debian/tests/control.tmp differ
>
> The generated control file differs from the actual one.
> A sourceful upload of this package is needed.
>
> Differences:
> --- debian/tests/control  2023-01-13 07:05:01.0 +
> +++ debian/tests/control.tmp  2023-01-17 02:06:59.340564039 +
> @@ -7,7 +7,7 @@
>   #   $ mv debian/tests/control.tmp debian/tests/control
>   
>   Tests: pytest-with-recommends
> -Depends: python3-all, diffoscope, black, python3-pytest, python3-h5py, file, 
> linux-image-amd64 [amd64] | linux-image-generic [amd64], abootimg, acl, 
> apksigcopier, apksigner, apktool [!ppc64el !s390x], binutils-multiarch, 
> bzip2, caca-utils, colord, coreboot-utils, db-util, default-jdk-headless | 
> default-jdk | java-sdk, device-tree-compiler, docx2txt, e2fsprogs, enjarify, 
> ffmpeg, fontforge-extras, fonttools, fp-utils [!ppc64el !s390x], genisoimage, 
> gettext, ghc, ghostscript, giflib-tools, gnumeric, gnupg, gnupg-utils, 
> hdf5-tools, html2text, imagemagick, jsbeautifier, libarchive-tools, 
> libxmlb-dev, llvm, lz4 | liblz4-tool, lzip, mono-utils, ocaml-nox, odt2txt, 
> oggvideotools [!s390x], openssh-client, openssl, pgpdump, poppler-utils, 
> procyon-decompiler, python3-pdfminer, r-base-core, rpm2cpio, sng, sqlite3, 
> squashfs-tools, tcpdump, u-boot-tools, unzip, wabt, xmlbeans, xxd, xz-utils, 
> zip, zstd, androguard, python3-argcomplete, python3-binwalk, 
> python3-defusedxml, python3-distro, python3-guestfs, python3-jsondiff, 
> python3-progressbar, python3-pypdf, python3-debian, python3-pyxattr, 
> python3-rpm, python3-tlsh
> +Depends: python3-all, diffoscope, black, python3-pytest, python3-h5py, file, 
> linux-image-amd64 [amd64] | linux-image-generic [amd64], abootimg, acl, 
> apksigcopier, apksigner, apktool [!ppc64el !s390x], binutils-multiarch, 
> bzip2, caca-utils, colord, coreboot-utils, db-util, default-jdk-headless | 
> default-jdk | java-sdk, device-tree-compiler, docx2txt, e2fsprogs, enjarify, 
> ffmpeg, fontforge-extras, fonttools, fp-utils [!ppc64el !s390x], genisoimage, 
> gettext, ghc, ghostscript, giflib-tools, gnumeric, gnupg, gnupg-utils, 
> hdf5-tools, html2text, imagemagick, jsbeautifier, libarchive-tools, 
> libxmlb-dev, llvm, lz4 | liblz4-tool, lzip, mono-utils, ocaml-nox, odt2txt, 
> oggvideotools [!s390x], openssh-client, openssl, pgpdump, poppler-utils, 
> procyon-decompiler, python3-pdfminer, r-base-core, rpm2cpio, sng, sqlite3, 
> squashfs-tools, tcpdump, u-boot-tools, unzip, wabt, xmlbeans, xxd, xz-utils, 
> zip, zstd,

Confirmed that it also affects the version in bookworm:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope.html

And according to test history, may go back to much earlier versions
(222+)... although there were some other possible FTBFS issues that may
have affected older versions, and I don't immediately see a way to look
at the logs from older versions.

live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Bug#1028804 marked as pending in libpdfbox2-java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028804 [src:libpdfbox2-java] libpdfbox2-java: FTBFS: No source files for 
package org.apache.fontbox.afm
Added tag(s) pending.

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

Bug#1028804: marked as pending in libpdfbox2-java

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/libpdfbox2-java/-/commit/95c2d69090ccf3ae812443150b26926d9bcab234


Drop documentation binary packages.

Closes: #1028804


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028804

Processed: Re: Bug#1029066: diffoscope: FTBFS if no internet is available (using internet connection during build)

[Debian Bug Tracking System]

Processing control commands:

> found 1029066 230
Bug #1029066 [src:diffoscope] diffoscope: FTBFS if no internet is available 
(using internet connection during build)
Marked as found in versions diffoscope/230.

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

Bug#1028716: marked as pending in mozjs

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1028716 in mozjs 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/gnome-team/mozjs/-/commit/f51a1f902757c4f10f7c75dfa541fb673ecab6c2


Cherry-pick patch to fix build with Python 3.11

Closes: #1028716


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028716

Processed: update

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1027613 [src:onetbb] onetbb: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned 
exit code 1
Severity set to 'important' from 'serious'

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

Bug#1027613: update

[M. Zhou]

Control: severity -1 important

I think this FTBFS mostly stems from the toolchain.

1. before the bug is filed, it builds successfully on amd64
2. On the day I recieved this bug report, I reproduced it
3. after some toolchain updates, I cannot reproduce it anymore

Bug#1026988: marked as done (Upcoming test suite regression due to changes in file/libmagic)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 19:25:56 +
with message-id 
and subject line Bug#1026988: fixed in ruby-ruby-magic-static 0.5.4-1.1
has caused the Debian Bug report #1026988,
regarding Upcoming test suite regression due to changes in file/libmagic
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.)


-- 
1026988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source:  ruby-ruby-magic-static
Version: 0.5.4-1
Severity: important

Hello,

The last upload of file/libmagic (1:5.43-3), currently in experimental) also
the ruby-ruby-magic-static test suite:

==
Failure: test_magic_get_parameter_with_PARAM_BYTES_MAX(MagicTest)
/<>/test/test_magic.rb:208:in 
`test_magic_get_parameter_with_PARAM_BYTES_MAX'
 205:   end
 206: 
 207:   def test_magic_get_parameter_with_PARAM_BYTES_MAX
  => 208: assert_equal(1024 * 1024, 
@magic.get_parameter(Magic::PARAM_BYTES_MAX))
 209:   end
 210: 
 211:   def test_magic_get_parameter_lower_boundary
<1048576> expected but was
<7340032>
==

In fact, file's upstream has changed the value. Please, at your own
descretion, relax that check, or adjust it to the new value once I've
uploaded file to unstable - my plan to do this is in about a week.

In case you're courious, the change was:

:
commit d2659ae455c7df7e8c6355dfaaea1180236a2932
Author: Christos Zoulas 
Date:   Sun Oct 2 12:53:28 2022 +

Increase the number of bytes we are looking for (Joerg Jenderek)


Regards,

Christoph



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-ruby-magic-static
Source-Version: 0.5.4-1.1
Done: Christoph Biedl 

We believe that the bug you reported is fixed in the latest version of
ruby-ruby-magic-static, 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.
Christoph Biedl  (supplier of updated 
ruby-ruby-magic-static 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, 11 Jan 2023 18:53:56 +0100
Source: ruby-ruby-magic-static
Architecture: source
Version: 0.5.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Christoph Biedl 
Closes: 1026988
Changes:
 ruby-ruby-magic-static (0.5.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Adjust PARAM_BYTES_MAX for change in file 5.44. Closes: #1026988
Checksums-Sha1:
 05940b233de4619e74ec0fc19ea45df04c4a2d4d 2196 
ruby-ruby-magic-static_0.5.4-1.1.dsc
 bb04791e73a980de28c8ff6aa1d6faae78abd67a 4084 
ruby-ruby-magic-static_0.5.4-1.1.debian.tar.xz
 48a2f0038609bd0d3eb38031d38c0c9e34797474 9528 
ruby-ruby-magic-static_0.5.4-1.1_powerpc.buildinfo
Checksums-Sha256:
 ac5048bff96a4ce71d11556fbad8988d474cff083167b3d47794b56dbbb413aa 2196 
ruby-ruby-magic-static_0.5.4-1.1.dsc
 2fca80781ce9a904011e84f49c1c8418559fa8a6d43fc3e75a9b11b9a592d1f7 4084 
ruby-ruby-magic-static_0.5.4-1.1.debian.tar.xz
 44656efbeec2469383e3785c51a2f4886873ba57b1540aa80fc8ac77d9ab45a3 9528 
ruby-ruby-magic-static_0.5.4-1.1_powerpc.buildinfo
Files:
 6bdcc2cd084a7cf456acf25dd050d215 2196 ruby optional 
ruby-ruby-magic-static_0.5.4-1.1.dsc
 b031948d305be1ee453ea9844895025f 4084 ruby optional 
ruby-ruby-magic-static_0.5.4-1.1.debian.tar.xz
 78d5ba476b03c973cf8c800280fe2511 9528 ruby optional 
ruby-ruby-magic-static_0.5.4-1.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmO/AbEACgkQxCxY61kU
kv1fVxAA4Y+C2l2wgAbEVT26aShy21lvEZknyZttz2Og4keZZFdfCG3zbHgeqCUJ
HED4FXKK/JGXDu1z6BzBw4Qi67VbL+Y6WRBuBuncvQd1dUWRYlIl8ChVmHfqkSXL
T6GkzfRPCWfjlErD7RGSmzji3fpKIpX6Dx7gj7LkZEwpGCCODQH0bbwy0YfQWE63
cTusri+jPwY//pbvL6nIwSMFPqYNiHx96+wpukUO4QotPBfBoYYE+uJ4bOoBlUVt
kynVOMeLvwZflKnkmFX52V7AV3ch2wuOXRjToBNypWZtXxThqi4x7Ump84pucy1a
td0pgfasbFF2wQuwwaDg6O5OU2kCzO4joYkkgTfAsR0B7AElTI2J4x3TXKilkDph
Sa1GN8hpVPHV1JF

Processed: Bug#1029104 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029104 [src:libreoffice] FTBFS with fontconfig 2.14.1 (doesn't expect RGB 
stripes
Ignoring request to alter tags of bug #1029104 to the same tags previously set

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

Bug#1029104: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1029104 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/5048dd6b7b7690f77c9f2bdd4f2cd86d7bdbc1b4


fix vcls testSimpleText with fontconfig-config 2.14.1-3 (closes: #1029104)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029104

Processed: RC Bug #1027503 forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 1027503 https://github.com/enthought/apptools/issues/325
Bug #1027503 [src:python-apptools] python-apptools: FTBFS: AttributeError: 
'NoneType' object has no attribute 'pop'
Set Bug forwarded-to-address to 
'https://github.com/enthought/apptools/issues/325'.
> thanks
Stopping processing here.

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

Processed: Bug#1029104 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029104 [src:libreoffice] FTBFS with fontconfig 2.14.1 (doesn't expect RGB 
stripes
Ignoring request to alter tags of bug #1029104 to the same tags previously set

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

Bug#1029104: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1029104 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/5048dd6b7b7690f77c9f2bdd4f2cd86d7bdbc1b4


fix vcls testSimpleText with fontconfig-config 2.14.1-3 (closes: #1029104)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029104

Processed: found 1029104 in 1:7.4.4-1

[Debian Bug Tracking System]

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

> found 1029104 1:7.4.4-1
Bug #1029104 [src:libreoffice] FTBFS with fontconfig 2.14.1 (doesn't expect RGB 
stripes
Marked as found in versions libreoffice/1:7.4.4-1.
> thanks
Stopping processing here.

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

Processed: Bug#1029104 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029104 [src:libreoffice] FTBFS with fontconfig 2.14.1 (doesn't expect RGB 
stripes
Added tag(s) pending.

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

Bug#1029104: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1029104 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/5048dd6b7b7690f77c9f2bdd4f2cd86d7bdbc1b4


fix vcls testSimpleText with fontconfig-config 2.14.1-3 (closes: #1029104)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029104

Processed (with 1 error): clone

[Debian Bug Tracking System]

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

> clone 1029101 -1
Bug #1029101 [fontconfig-config] please Enable RGB stripes layout for sub-pixel 
rendering
Bug 1029101 cloned as bug 1029104
1026825 was blocked by: 1027837 1029101 1028196
1026825 was not blocking any bugs.
Added blocking bug(s) of 1026825: 1029104
> reassign -1 src:libreoffice
Bug #1029104 [fontconfig-config] please Enable RGB stripes layout for sub-pixel 
rendering
Bug reassigned from package 'fontconfig-config' to 'src:libreoffice'.
No longer marked as found in versions fontconfig/2.14.1-3.
Ignoring request to alter fixed versions of bug #1029104 to the same values 
previously set
> retitle -1 FTBFS with fontconfig 2.14.1 (doesn't expect RGB stripes
Bug #1029104 [src:libreoffice] please Enable RGB stripes layout for sub-pixel 
rendering
Changed Bug title to 'FTBFS with fontconfig 2.14.1 (doesn't expect RGB stripes' 
from 'please Enable RGB stripes layout for sub-pixel rendering'.
> layout for sub-pixel rendering)
Unknown command or malformed arguments to command.
> severity -1 serious
Bug #1029104 [src:libreoffice] FTBFS with fontconfig 2.14.1 (doesn't expect RGB 
stripes
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#1029101: Acknowledgement (fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice)

[Debian Bug Tracking System]

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

> severity 1029101 important
Bug #1029101 [fontconfig-config] fontconfig-config: 2.14.1 upload breaks 
testSimpleText of libreoffice
Severity set to 'important' from 'serious'
> retitle 1029101 please Enable RGB stripes layout for sub-pixel rendering
Bug #1029101 [fontconfig-config] fontconfig-config: 2.14.1 upload breaks 
testSimpleText of libreoffice
Changed Bug title to 'please Enable RGB stripes layout for sub-pixel rendering' 
from 'fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice'.
> on KDE only
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#1029101: Acknowledgement (fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice)

[Rene Engelhard]

severity 1029101 important
retitle 1029101 please Enable RGB stripes layout for sub-pixel rendering 
on KDE only

thanks

[ sorry for "spamming" ]

Hi,

Am 17.01.23 um 19:04 schrieb Rene Engelhard:
it still fails. Probably it ignores it since it's already set in /etc 
and that already matches?


OK, got it. I need to "delete" it.

  

mode="delete">rgb

  


Then it passes and it shouldn't  break with 2.13 either since deleting 
somethng non-existing works ;-)


Will reassign a clone to libreoffice to fix that test failure.

Regards,


Rene

Bug#1029101: Acknowledgement (fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice)

[Rene Engelhard]

Hi again,

Am 17.01.23 um 18:28 schrieb Rene Engelhard:
I tried to adapt the test to expected values but failed. When I adapt 
some values stuff even further breaks, and at the 50% test I then had no 
idea what to do.)


LO has already a fc_local.conf:

./instdir/share/fonts/truetype/fc_local.conf

but when I add the stuff from the patch  there

rene@frodo:~/Debian/Pakete/LibreOffice/libreoffice/libreoffice-7.4.4.2$ 
cat ./instdir/share/fonts/truetype/fc_local.conf





  Symbol
  
OpenSymbol
  

  


  KDE

mode="append">rgb

  


it still fails. Probably it ignores it since it's already set in /etc 
and that already matches?


Regards,


Rene

Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors

[Diederik de Haas]

On Tuesday, 17 January 2023 18:12:30 CET Andreas Beckmann wrote:
> On Tue, 17 Jan 2023 10:56:33 +0100 Bastian Blank  wrote:
> > > Error! Bad return status for module build on kernel: 6.0.0-6-amd64
> > > (x86_64)
> > > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more
> > > information.
> 
> That does not look like a module packaged in Debian ...

These kind of issues get regularly filed against the Debian kernel and it does 
not matter whether the dkms module is packaged in Debian or not. If the dkms 
module is packaged in Debian, we assign it to the specific dkms package.

> > dkms fails the installation if anything it tries to build does not work.
> > This must go, reassigning accordingly.
> 
> What should dkms do instead? Out-of-tree modules break frequently on new
> kernel upstream major versions, that is completely out of dkms' control.
> 
> There are two points in time where these errors could show up:
> * ) at package installation/upgrade time because building the module
>  failed (there is a small chance of the build succeeding ater reboot
>  if a badly packaged module only supports building against the
>  running kernel)
> * ) at reboot due to a missing kernel module
> 
> A failing module could build be 'harmless' if it's e.g. just the
> soundcard driver missing (unless you depend on text-to-speech) but in
> the worst case it's the root file system that is not supported...

It seems fine to print (in all caps afaic) that there is an issue.

But it should not cause the kernel package install/upgrade to fail.
And that does seem in dkms' control afaict.

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

Processed: block 1026825 with 1029101

[Debian Bug Tracking System]

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

> block 1026825 with 1029101
Bug #1026825 [release.debian.org] python3.11 as default
1026825 was blocked by: 1028196 1027837
1026825 was not blocking any bugs.
Added blocking bug(s) of 1026825: 1029101
> thanks
Stopping processing here.

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

Bug#1029101: Acknowledgement (fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice)

[Rene Engelhard]

Hi,

addendum:

I tried to adapt the test to expected values but failed. When I adapt 
some values stuff even further breaks, and at the 50% test I then had no 
idea what to do.)


For reference,  this is the test:

https://cgit.freedesktop.org/libreoffice/core/tree/vcl/qa/cppunit/text.cxx?h=libreoffice-7.4.4.2#n164 
ff.



Regards,


Rene

Bug#1028669: marked as done (easymock: FTBFS: No source files for package org.easymock)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 17:19:04 +
with message-id 
and subject line Bug#1028669: fixed in easymock 5.1.0-1
has caused the Debian Bug report #1028669,
regarding easymock: FTBFS: No source files for package org.easymock
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibeasymock-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] EasyMock Parent
> [pom]
> [INFO] EasyMock   
> [jar]
> [WARNING] The artifact org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 
> has been relocated to org.apache.maven.plugins:maven-deploy-plugin:jar:3.0.0
> [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded 
> from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 has not been 
> downloaded from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-dependency-plugin:2.8: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:2.8 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 has not been 
> downloaded from it before.
> [WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 
> is missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-release-plugin:2.5.3: Plugin 
> org.apache.maven.plugins:maven-release-plugin:2.5.3 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 has not been 
> downloaded from it before.
> [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.3

Bug#1029101: fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice

[Rene Engelhard]

Package: fontconfig-config
Version: 2.14.1-3
Severity: serious
Justification: causes FTBFS
Tags: patch

Dear Maintainer,

See
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=amd64&ver=1%3A7.4.4-1&stamp=1673962775&raw=0:

[_RUN_] VclTextTest::testSimpleText
./vcl/qa/cppunit/text.cxx:222:VclTextTest::testSimpleText
double equality assertion failed
- Expected: 42
- Actual  : 37
- Delta   : 4

Indeed that also happens when I build it locally (unfortunately the C++
autopkgtests had to be disabled in libreoffice, otherwise they would
have catched it, too)

Downgrading to 2.13.1-4.5 "fixes" it.

Since other distributions already *do* ship 2.14.1 I looked what they
had and I came around

https://src.fedoraproject.org/rpms/fontconfig/c/25e368d9d2888159b5eb9acf3839821a4fe81c40?branch=rawhide

Indeed, when I added that ... into the already existing 
/etc/fonts/conf.d/10-sub-pixel-rgb.conf
the test passes.

Filing this as serious as it causes (autopkg)test failures. Which is bad
this late in the release cycle, especially for packages involved in
transitions like python3-defaults...

Regards,

Rene

Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors

[Andreas Beckmann]

On Tue, 17 Jan 2023 10:56:33 +0100 Bastian Blank  wrote:

> Error! Bad return status for module build on kernel: 6.0.0-6-amd64 (x86_64)
> Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.


That does not look like a module packaged in Debian ...


dkms fails the installation if anything it tries to build does not work.
This must go, reassigning accordingly.


What should dkms do instead? Out-of-tree modules break frequently on new 
kernel upstream major versions, that is completely out of dkms' control.


There are two points in time where these errors could show up:
* ) at package installation/upgrade time because building the module
failed (there is a small chance of the build succeeding ater reboot
if a badly packaged module only supports building against the
running kernel)
* ) at reboot due to a missing kernel module

A failing module could build be 'harmless' if it's e.g. just the 
soundcard driver missing (unless you depend on text-to-speech) but in 
the worst case it's the root file system that is not supported...



Andreas

Bug#1028717: marked as done (python-gsd: FTBFS: build-dependency not installable: python-numpy-doc)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 17:06:40 +
with message-id 
and subject line Bug#1028717: fixed in python-gsd 2.7.0-2
has caused the Debian Bug report #1028717,
regarding python-gsd: FTBFS: build-dependency not installable: python-numpy-doc
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), cython3, dh-python, 
> pybuild-plugin-pyproject, python3-setuptools, python3-all-dev, 
> python3-ipython, python3-numpy (<< 1:2), python3-sphinx, build-essential, 
> fakeroot, python3-doc, python-numpy-doc, libjs-mathjax, 
> python3-sphinx-rtd-theme
> Filtered Build-Depends: debhelper-compat (= 13), cython3, dh-python, 
> pybuild-plugin-pyproject, python3-setuptools, python3-all-dev, 
> python3-ipython, python3-numpy (<< 1:2), python3-sphinx, build-essential, 
> fakeroot, python3-doc, python-numpy-doc, libjs-mathjax, 
> python3-sphinx-rtd-theme
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [476 B]
> Get:5 copy:/<>/apt_archive ./ Packages [552 B]
> Fetched 1985 B in 0s (165 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: python-numpy-doc but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/python-gsd_2.7.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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: python-gsd
Source-Version: 2.7.0-2
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-gsd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 1

Bug#1028904: pillow: Lost tiff support after binNMU with tiff 4.5.0

[Sebastiaan Couwenberg]

On Mon, 16 Jan 2023 16:43:23 +0100 Bastian Germann wrote:

I am uploading a NMU with the attached debdiff to DELAYED/10 to fix this.


You can reschedule this to 5 days.

From the NMU guidelines:

"
 * Upload fixing only release-critical and important bugs: 5 days
"

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#when-and-how-to-do-an-nmu 



Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1028669: marked as pending in easymock

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/easymock/-/commit/328c5a157a155bce9dddbbc7198fe3d1e279109a


Drop binary package libeasymock-java-doc and do not build the javadoc.

Closes: #1028669


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028669

Processed: Bug#1028669 marked as pending in easymock

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028669 [src:easymock] easymock: FTBFS: No source files for package 
org.easymock
Added tag(s) pending.

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

Bug#1027230: marked as done (python-dmsh: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 17:50:55 +0100
with message-id <5067aa643496524769c6959064a57...@debian.org>
and subject line Re: Bug#1027230 python-dmsh: autopkgtest fail with numpy/1.24.1
has caused the Debian Bug report #1027230,
regarding python-dmsh: autopkgtest fail with numpy/1.24.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.)


-- 
1027230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dmsh
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---

Tests continue to pass fine, so closing this bug.--- End Message ---

Bug#1029080: Info received (Bug#1029080: linux-image-5.10.0-20-amd64: Boot failure "PM: Image not found (code -22)" where power management is NOT used)

[Claire Osborne]

Hi,

Sorry - can this be closed please.

I am going to diplomatically say that a network engineer suffered a failure 
between mouse and keyboard - who did not appreciate that /etc/fstab is an 
integral part of the system boot process.

My apologies if this has wasted anyone's time.

Kind regards

Claire

--
Claire Osborne (she/her)
Senior Systems Engineer
Information Technology | Canterbury Christ Church University
Anselm, North Holmes Road, Canterbury, Kent, CT1 1QU
Registered Company limited by guarantee (No: 4793659) | Registered Charity (No: 
1098136)

-Original Message-
From: Debian Bug Tracking System  
Sent: 17 January 2023 15:36
To: Claire Osborne 
Subject: Bug#1029080: Info received (Bug#1029080: linux-image-5.10.0-20-amd64: 
Boot failure "PM: Image not found (code -22)" where power management is NOT 
used)

CAUTION: This email originated from outside of CCCU. Do not click links or open 
attachments unless you recognise the sender and know the content is safe.


Thank you for the additional information you have supplied regarding this Bug 
report.

This is an automatically generated reply to let you know your message has been 
received.

Your message is being forwarded to the package maintainers and other interested 
parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian Kernel Team 

If you wish to submit further information on this problem, please send it to 
1029...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish to report a 
problem with the Bug-tracking system.

--
1029080: 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.debian.org%2Fcgi-bin%2Fbugreport.cgi%3Fbug%3D1029080&data=05%7C01%7Cclaire.osborne%40canterbury.ac.uk%7C2cab687c48eb41d8985508daf8a0903b%7C0320b2da22dd4dab8c216e644ba14f13%7C0%7C0%7C638095665767562029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=agzC8xxxWkcoE5YnvSZ5B0DtXPRB0EdmmjjI85zD9no%3D&reserved=0
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1029092: Don't update mysql-defaults in Debian testing/Bookworm too early

[Otto Kekäläinen]

Package: mysql-defaults
Version: 1.1.0
Severity: serious
Owner: Otto Kekäläinen 

Don't allow mysql-defaults into testing/Bookworm before MariaDB
1:10.11.1-1 has entered it first. There is no package
'mariadb-server-core' in MariaDB 1:10.6.11-2 and thus the defaults
pointer would fail.

This severity 'serious' bug should prevent the migration
automatically. Close this bug when migration is free to proceed.

Bug#1029080: linux-image-5.10.0-20-amd64: Boot failure "PM: Image not found (code -22)" where power management is NOT used

[Claire Osborne]

On Tue, 17 Jan 2023 15:59:51 +0100 Diederik de Haas  
wrote:
> What was the latest 5.10.x kernel which did boot correctly? Reboot-

This will (or should) have been the 5.10.0-20 kernel as a post installation 
reboot due to either new kernel or package dependency trigger indicated in 
/var/run/reboot-required detected by monitoring - after which we would manually 
schedule an out of hours reboot - this certainly didn't happen 
yesterday/overnight - so this initial crash at approx 5am (GMT) today is 
entirely unexplained at present. No other servers in our virtual environment 
have shown any issues.

I will arrange to get the server booted from an ISO so I can manually inspect 
the filesystems and extract logs from /var/log to see if there is further 
information available on the host.

Thanks

Claire

Bug#1028438: otpclient: OTP values are all 000000

[Francisco Vilmar Cardoso Ruviaro]

Hi,

Thanks for the help guys!

libcotp has been upgraded to 1.2.8-1 (see https://bugs.debian.org/1028305).

otpclient has been upgraded to 3.1.3-1, we will use libbaseencode version
1.0.15-1 with libcotp 1.2.8-1 while the transition from libcotp 1.2.8-1
to 2.0.0-1 doesn't happen (see https://bugs.debian.org/1028528).

Thanks!
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00


OpenPGP_signature
Description: OpenPGP digital signature

Processed: RC Bug #1026725: Forwarded to upstream fix

[Debian Bug Tracking System]

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

> forwarded 1026725 https://github.com/hynek/structlog/pull/418
Bug #1026725 [src:python-structlog] python-structlog: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned 
exit code 13
Set Bug forwarded-to-address to 'https://github.com/hynek/structlog/pull/418'.
> thanks
Stopping processing here.

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

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> forwarded 1028716 https://bugzilla.mozilla.org/show_bug.cgi?id=1769631
Bug #1028716 [src:mozjs102] mozjs102: FTBFS with python3.11 as default: 
ValueError: invalid mode: 'rU'
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1769631'.
> fixed-upstream 1028716 103
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#1028994: [Pkg-mailman-hackers] Bug#1028994: mailman3: (autopkgtest) needs update for Python 3.11

[James Addison]

On Tue, 17 Jan 2023 at 14:33, Pierre-Elliott Bécue  wrote:
>
> I intend to do a full sweep on mailman suite in the next week, so don't
> worry too much! :)

Brilliant - thank you :)

Processed: Re: Bug#1029080: linux-image-5.10.0-20-amd64: Boot failure "PM: Image not found (code -22)" where power management is NOT used

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1029080 [src:linux] linux-image-5.10.0-20-amd64: Boot failure "PM: Image 
not found (code -22)" where power management is NOT used
Added tag(s) moreinfo.

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

Bug#1029080: linux-image-5.10.0-20-amd64: Boot failure "PM: Image not found (code -22)" where power management is NOT used

[Diederik de Haas]

Control: tag -1 moreinfo

On Tuesday, 17 January 2023 14:20:19 CET Claire Osborne wrote:
> Booting in recovery mode on 5.10.0.20 also failed
> 
> I have fallen back to the previously installed kernel 5.10.19 - with the
> same effect.
> 
> Booting in recovery mode on 5.10.0.19 also fails.

What was the latest 5.10.x kernel which did boot correctly?

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

Processed: Re: Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors

[Debian Bug Tracking System]

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

> reassign 1029063 dkms
Bug #1029063 [src:linux] reportbug: linux-image-6.0.0-6-amd64 remains 
unconfigured because of errors
Bug reassigned from package 'src:linux' to 'dkms'.
No longer marked as found in versions linux/6.0.12-1.
Ignoring request to alter fixed versions of bug #1029063 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#1028994: [Pkg-mailman-hackers] Bug#1028994: mailman3: (autopkgtest) needs update for Python 3.11

[Pierre-Elliott Bécue]

Hi,

James Addison  wrote on 17/01/2023 at 15:17:43+0100:

> Source: mailman3
> Version: 3.3.7-3
> Followup-For: Bug #1028994
>
> Dear Maintainer,
>
> There is hopefully good news relating to this bug: upstream has
> discovered the same problem and fixed it after version v3.3.7 - the
> fix is included in v3.3.8 of mailman3.
>
> (the fix includes removal of a 'coroutine' decorator that causes the failure, 
> instead declaring the associated method using 'async def' instead of 'def')
>
> See the following links for the changes between the mentioned versions, and 
> the contents of the fix:
>
> - https://gitlab.com/mailman/mailman/-/compare/3.3.7...3.3.8
>
> - 
> https://gitlab.com/mailman/mailman/-/commit/1954815f32fea4d9d920cdc74f63bcc24d3b6c49
>
> Note: version 3.3.8 of the package retains Python 3.10 support, which
> may be helpful if the Debian project decides to rollback to that
> version of Python for the upcoming bookworm release.

I intend to do a full sweep on mailman suite in the next week, so don't
worry too much! :)

-- 
PEB

Bug#1028994: mailman3: (autopkgtest) needs update for Python 3.11

[James Addison]

Source: mailman3
Version: 3.3.7-3
Followup-For: Bug #1028994

Dear Maintainer,

There is hopefully good news relating to this bug: upstream has discovered the 
same problem and fixed it after version v3.3.7 - the fix is included in v3.3.8 
of mailman3.

(the fix includes removal of a 'coroutine' decorator that causes the failure, 
instead declaring the associated method using 'async def' instead of 'def')

See the following links for the changes between the mentioned versions, and the 
contents of the fix:

- https://gitlab.com/mailman/mailman/-/compare/3.3.7...3.3.8

- 
https://gitlab.com/mailman/mailman/-/commit/1954815f32fea4d9d920cdc74f63bcc24d3b6c49

Note: version 3.3.8 of the package retains Python 3.10 support, which may be 
helpful if the Debian project decides to rollback to that version of Python for 
the upcoming bookworm release.

Thank you,
James

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

Processed: tagging 1027354, tagging 1028621, notfound 1028607 in 28.2+1-9, found 1028607 in 1:28.2+1-9 ...

[Debian Bug Tracking System]

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

> tags 1027354 - sid bookworm
Bug #1027354 [src:ruby-fogbugz] ruby-fogbugz: FTBFS: ERROR: Test "ruby3.1" 
failed: 
:85:in 
`require': cannot load such file -- mocha/mini_test (LoadError)
Removed tag(s) sid and bookworm.
> tags 1028621 - sid bookworm
Bug #1028621 {Done: Dmitry Shachnev } [src:sphinx] sphinx: 
autopkgtest is failng after updating pygments to 2.14.0+dfsg-1
Bug #1028836 {Done: Dmitry Shachnev } [src:sphinx] sphinx: 
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.10 3.11" returned exit code 13
Removed tag(s) bookworm and sid.
Removed tag(s) sid and bookworm.
> notfound 1028607 28.2+1-9
Bug #1028607 [src:emacs] FTBFS: FAILED test-correct-notice and test-end-chop in 
copyright-tests.log due to new year 2023
The source 'emacs' and version '28.2+1-9' do not appear to match any binary 
packages
No longer marked as found in versions emacs/28.2+1-9.
> found 1028607 1:28.2+1-9
Bug #1028607 [src:emacs] FTBFS: FAILED test-correct-notice and test-end-chop in 
copyright-tests.log due to new year 2023
Marked as found in versions emacs/1:28.2+1-9.
> tags 1003694 + experimental
Bug #1003694 {Done: Mike Gabriel } [src:gosa] "gosa: 
completly broken in bookworm, breaking debian-edu"
Added tag(s) experimental.
> tags 1027354 - sid bookworm
Bug #1027354 [src:ruby-fogbugz] ruby-fogbugz: FTBFS: ERROR: Test "ruby3.1" 
failed: 
:85:in 
`require': cannot load such file -- mocha/mini_test (LoadError)
Ignoring request to alter tags of bug #1027354 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#1028709: marked as done (objenesis: FTBFS: No source files for package org.objenesis)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 13:35:29 +
with message-id 
and subject line Bug#1028709: fixed in objenesis 3.3-2
has caused the Debian Bug report #1028709,
regarding objenesis: FTBFS: No source files for package org.objenesis
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibobjenesis-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Objenesis parent project   
> [pom]
> [INFO] Objenesis  
> [jar]
> [WARNING] The POM for com.mycila:license-maven-plugin:jar:4.1 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> com.mycila:license-maven-plugin:4.1: Plugin 
> com.mycila:license-maven-plugin:4.1 or one of its dependencies could not be 
> resolved: Cannot access central (https://repo.maven.apache.org/maven2) in 
> offline mode and the artifact com.mycila:license-maven-plugin:jar:4.1 has not 
> been downloaded from it before.
> [WARNING] The POM for org.gaul:modernizer-maven-plugin:jar:2.4.0 is missing, 
> no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.gaul:modernizer-maven-plugin:2.4.0: Plugin 
> org.gaul:modernizer-maven-plugin:2.4.0 or one of its dependencies could not 
> be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in 
> offline mode and the artifact org.gaul:modernizer-maven-plugin:jar:2.4.0 has 
> not been downloaded from it before.
> [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded 
> from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:3.4.2 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:3.4.2: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:3.4.2 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:3.4.2 has not been 
> downloaded from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-dependency-plugin:2.8: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:2.8 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 has not been 
> do

Bug#1028636: marked as done (pocl: FTBFS on arm64: ***** The testsuite has failed! *****)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 13:35:56 +
with message-id 
and subject line Bug#1028636: fixed in pocl 3.1-2
has caused the Debian Bug report #1028636,
regarding pocl: FTBFS on arm64:  * The testsuite has 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.)


-- 
1028636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pocl
Version: 3.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=arm64&ver=3.1-1&stamp=1673537413&raw=0

dpkg-gensymbols: warning: debian/libpocl2/DEBIAN/symbols doesn't match 
completely debian/libpocl2.symbols
--- debian/libpocl2.symbols (libpocl2_3.1-1_arm64)
+++ dpkg-gensymbolsR76HBy   2023-01-12 15:29:59.848720577 +
@@ -23,28 +23,28 @@
  
_ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb0EEclEcE5__nul@Base
 3.0
  
_ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
 3.0
  _ZN4pocl23eraseFunctionAndCallersEPN4llvm8FunctionE@Base 1.8-3~visibility
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 0.11
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorIPKcSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 1.8# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceE{size_t}{size_t}PKc{size_t}@Base
 1.6-2~hardening
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 0.11
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorIPKcSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 3.1-1# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceE{size_t}{size_t}PKc{size_t}@Base
 1.6-2~hardening
 #MISSING: 1.8# 
(optional=templinst|arch=mipsel)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 1.1-6~llvm6.0+gcc8
-#MISSING: 1.8# 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4swapERS4_@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKc{size_t}@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_assignERKS4_@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_mutateE{size_t}{size_t}PKc{size_t}@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE24_M_get_insert_unique_posERKS5_@Base
 1.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERKS5_@Base
 1.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 1.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 1.1-2~llvm5.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_tree

Bug#1029076: uwsgi-plugin-python3: built against non-default libpython3.11 / should always build against the defalt Python in testing

[Dominik George]

Package: uwsgi-plugin-python3
Version: 2.0.21-3+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-pyt...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Currently, the uWSGI Python 3 plugin is built against
Python 3.11, and depends on libpython3.11. This is,
to some extent, fine, as Python 3.11 is already in
Debian.

However, Python 3.10 is still the default Python in
bookworm, and as it stands this will not change [1].
In practice, this means that without changing the
interpreter and manually ensuring that the Python 3.11
environment is fully available, apps run through uWSGI
do not work.

So, the uWSGI plugin should in general always build
against the default Python IMHO.

- -nik

[1] https://lists.debian.org/debian-python/2023/01/msg00010.html

- -- 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/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), 
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages uwsgi-plugin-python3 depends on:
ii  libc6  2.36-8
ii  libpython3.11  3.11.1-2
ii  uwsgi-core 2.0.21-3+b1

uwsgi-plugin-python3 recommends no packages.

Versions of packages uwsgi-plugin-python3 suggests:
pn  python3-uwsgidecorators  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCY8aedTEaaHR0cHM6Ly93
d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz
aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3ZDoAQCYW8oE4ZgiBKkgo1lge2Az
7/qTIXGHgKAAF5kmuGTB5QD+NiuAOboj6I6ZvxRZF4o1D3vXCBr1HkqYz+piZMQO
Fgc=
=Y+XX
-END PGP SIGNATURE-

Processed: Bug#1028709 marked as pending in objenesis

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028709 [src:objenesis] objenesis: FTBFS: No source files for package 
org.objenesis
Added tag(s) pending.

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