Bug#1005556: marked as done (elan: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

[Debian Bug Tracking System]

Your message dated Wed, 2 Mar 2022 07:48:35 +
with message-id 

and subject line 
has caused the Debian Bug report #1005556,
regarding elan: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build 
returned exit code 101
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.)


-- 
1005556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elan
Version: 1.3.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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 '/<>'
> touch debian/cargo-checksum.json
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `rand = "^0.7.3"`
> candidate versions found which didn't match: 0.8.4
> location searched: directory source `/<>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `elan v1.3.1 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/elan_1.3.1-2_unstable.log

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

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

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

Bug#1006672: php8.1: CVE-2021-21708

[Salvatore Bonaccorso]

Source: php8.1
Version: 8.1.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://bugs.php.net/81708
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for php8.1.

CVE-2021-21708[0]:
| In PHP versions 7.4.x below 7.4.28, 8.0.x below 8.0.16, and 8.1.x
| below 8.1.3, when using filter functions with FILTER_VALIDATE_FLOAT
| filter and min/max limits, if the filter fails, there is a possibility
| to trigger use of allocated memory after free, which can result it
| crashes, and potentially in overwrite of other memory chunks and RCE.
| This issue affects: code that uses FILTER_VALIDATE_FLOAT with min/max
| limits.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-21708
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21708
[1] https://bugs.php.net/81708

Regards,
Salvatore

Bug#1006571: marked as done (wine64-development-tools: /usr/bin/function_grep.pl is already shipped by wine64-tools)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2022 01:48:39 +
with message-id 
and subject line Bug#1006571: fixed in wine-development 6.3~repack-1
has caused the Debian Bug report #1006571,
regarding wine64-development-tools: /usr/bin/function_grep.pl is already 
shipped by wine64-tools
to be marked as done.

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

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


-- 
1006571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wine64-development-tools
Version: 6.1~repack-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package wine64-development-tools.
  Preparing to unpack .../wine64-development-tools_6.1~repack-1_amd64.deb ...
  Unpacking wine64-development-tools (6.1~repack-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/wine64-development-tools_6.1~repack-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/function_grep.pl', which is also in package 
wine64-tools 6.0.2~repack-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/wine64-development-tools_6.1~repack-1_amd64.deb


cheers,

Andreas


wine64-tools=6.0.2~repack-2_wine64-development-tools=6.1~repack-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 6.3~repack-1
Done: Michael Gilbert 

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine-development 
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, 02 Mar 2022 00:36:16 +
Source: wine-development
Architecture: source
Version: 6.3~repack-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 1006571
Changes:
 wine-development (6.3~repack-1) unstable; urgency=medium
 .
   * New upstream release 6.3, released Feb 26, 2021.
 - Better debugger support in the NT syscall interface.
 - WineGStreamer library converted to PE.
 - Still more WinRT support in WIDL.
 - Optional support for build IDs.
 - Various bug fixes.
   * Move function_grep.pl to /usr/libexec (closes: #1006571).
Checksums-Sha1:
 b273f14d70b82d4c87238964adf1264f5443c6a5 4706 wine-development_6.3~repack-1.dsc
 2f3341011b9779e43cd7332eed27a12ee3ce8a85 21461624 
wine-development_6.3~repack.orig.tar.xz
 2708f6df2df012cc9abbf00f3a11523dae03f3a5 5688440 
wine-development_6.3~repack-1.debian.tar.xz
 b48e2a2b6211c0460090e9f232be343b4308387b 19090 
wine-development_6.3~repack-1_source.buildinfo
Checksums-Sha256:
 d81072cf16c499d748e0411a86b2737a1fa284a3e431ed287d1609f141aa1977 4706 
wine-development_6.3~repack-1.dsc
 0fcd211f61cb72d1214f0c186f2ce928af88195a576b48c40cb1772dc25305b2 21461624 
wine-development_6.3~repack.orig.tar.xz
 561efb22ea6306bca5404e04527acf25ff779a959c3625b6d4c0b970baaff495 5688440 
wine-development_6.3~repack-1.debian.tar.xz
 05ebd75ce7ada8544f66d3833ba323cbeb12840c011b771d59df9582b45228d9 19090 
wine-development_6.3~repack-1_source.buildinfo
Files:
 13cf59621a7c710562c385bc2cb6cf90 4706 otherosfs optional 
wine-development_6.3~repack-1.dsc
 3c8c060fea29826e1b4d620173c7b9ee 21461624 otherosfs optional 
wine-development_6.3~repack.orig.tar.xz
 647364ab2ec11305fd2aa80eef3e5aaf 5688440 otherosfs optional 
wine-development_6.3~repack-1.debian.tar.xz
 363a596962f56d898978d0c770d477b6 19090 otherosfs optional 
wine-development_6.3~repack-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmIeyFMACgkQmD40ZYkU
ayiCBCAArsiLC7zEsCwiLvRHg4fFhwjgbUT9GoR8wJB0k+Din9JC+YDbPu+gw8P8
aksCH1vnfHDOtdl7f0vnx3gqDpcFwny527z+5P06ZrnbcHZbxF769zJhiUgGq3vA

Bug#1006379: marked as done (libssh2: autopkgtest regression: FAIL: ssh2.sh)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2022 01:03:38 +
with message-id 
and subject line Bug#1006379: fixed in libssh2 1.10.0-3
has caused the Debian Bug report #1006379,
regarding libssh2: autopkgtest regression: FAIL: ssh2.sh
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.)


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

Source: libssh2
Version: 1.10.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, recently it started 
failing in testing.


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

Paul

[1] https://ci.debian.net/packages/libs/libssh2/

https://ci.debian.net/data/autopkgtest/testing/amd64/libs/libssh2/19448377/log.gz

make  check-TESTS
make[3]: Entering directory 
'/tmp/autopkgtest-lxc.tkjc_w24/downtmp/build.J98/src/tests'
make[4]: Entering directory 
'/tmp/autopkgtest-lxc.tkjc_w24/downtmp/build.J98/src/tests'

PASS: simple
PASS: mansyntax.sh
FAIL: ssh2.sh

Testsuite summary for libssh2 -

# TOTAL: 3
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to libssh2-de...@cool.haxx.se

make[4]: *** [Makefile:870: test-suite.log] Error 1


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libssh2
Source-Version: 1.10.0-3
Done: Nicolas Mora 

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

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

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

Debian distribution maintenance software
pp.
Nicolas Mora  (supplier of updated libssh2 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, 01 Mar 2022 19:23:12 -0500
Source: libssh2
Architecture: source
Version: 1.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Mora 
Changed-By: Nicolas Mora 
Closes: 1006379
Changes:
 libssh2 (1.10.0-3) unstable; urgency=medium
 .
   * d/patches: Fix ssh2.sh test (Closes: #1006379)
   * d/control: Add openssh-server in Build-Depends
   * d/tests/control: Add openssh-server in Depends
   * d/copyright: Update copyright years
Checksums-Sha1:
 13e6cabe69150dc97eef405c749b120d68c552c9 2283 libssh2_1.10.0-3.dsc
 2ebb3bc5c944090ade840f3a0ada9874eced979b 965044 libssh2_1.10.0.orig.tar.gz
 d787c344d93468c118d3f9713b69cadc135bb1b8 488 libssh2_1.10.0.orig.tar.gz.asc
 692585691db4acfa2336632d9f3a6a18f24b473d 8416 libssh2_1.10.0-3.debian.tar.xz
 1bbdd86842d4f70985ce1e26fd0cde7982f34eb7 7251 libssh2_1.10.0-3_amd64.buildinfo
Checksums-Sha256:
 a0fe68f402a2f44dd6bd2219457fb8677b2149a83e7b009e93ff0635de940766 2283 
libssh2_1.10.0-3.dsc
 2d64e90f3ded394b91d3a2e774ca203a4179f69aebee03003e5a6fa621e41d51 965044 
libssh2_1.10.0.orig.tar.gz
 75702eaf490fa8c1e69b889c5c6366c2c3f3b089bc715f9f9be081c88f115f81 488 
libssh2_1.10.0.orig.tar.gz.asc
 c0bea31fe565273656349484d1000b557e489ee322834b40c4d7d33317a56940 8416 
libssh2_1.10.0-3.debian.tar.xz
 4f4029622dfd49e8e510bbb01fae6da9c8a3e40b7bfabfcc0032a60cbd46b829 7251 
libssh2_1.10.0-3_amd64.buildinfo
Files:
 2ca805b23186f806bce4f072cee64315 2283 libs optional libssh2_1.10.0-3.dsc
 f604ba083fad23bf715a9e9f57f4 965044 libs optional 
libssh2_1.10.0.orig.tar.gz
 71b76665e1984d5694363a4c96176053 488 libs optional 
libssh2_1.10.0.orig.tar.gz.asc
 8e7e4e96077c198681371537387406e5 8416 libs optional 
libssh2_1.10.0-3.debian.tar.xz
 acde8413ac42756d413903e473e48da7 7251 libs optional 
libssh2_1.10.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAmIevWQACgkQ/oITlEC9
Irl29g//W+TPDDxr/c4PAGBvtlvCfDjp19cO7waVqgghf4l0N344ny/llw5LoG78

Bug#1005934: marked as done (nvidia-graphics-drivers-tesla-470: incompatible with xorg-server video ABI 25)

[Debian Bug Tracking System]

Your message dated Wed, 02 Mar 2022 00:19:20 +
with message-id 
and subject line Bug#1005934: fixed in nvidia-graphics-drivers-tesla-470 
470.103.01-2
has caused the Debian Bug report #1005934,
regarding nvidia-graphics-drivers-tesla-470: incompatible with xorg-server 
video ABI 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.)


-- 
1005934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-418
Version: 418.226.00-1
Severity: serious

xorg-server's video ABI was recently bumped, and
nvidia-graphics-drivers-tesla-418 only declares compatibility for up to
v24.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.103.01-2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Mar 2022 00:58:08 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.103.01-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1005934
Changes:
 nvidia-graphics-drivers-tesla-470 (470.103.01-2) unstable; urgency=medium
 .
   * Add xorg-video-abi-25 (Xorg Xserver 21) as alternative dependency.
 (Closes: #1005934)
   * dkms.conf: Use a BUILD_EXCLUSIVE equivalent hack to skip building for -rt
 kernels, not supported upstream (510.54-1).
   * Declare Testsuite: autopkgtest-pkg-dkms (510.54-1).
Checksums-Sha1:
 d6cdc325459c2152d47aecca865dfffe1ae19909 7572 
nvidia-graphics-drivers-tesla-470_470.103.01-2.dsc
 08cd8e5326fdc77a755fda1eb8f63df1d62c910e 272473978 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-amd64.tar.gz
 6531d3a249e2d9d8ef584cb1659b06454f8e4a0d 184473786 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-arm64.tar.gz
 9c9a655d0a8b8f664f79b449b8f4a40d5bcacf53 67466214 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-ppc64el.tar.gz
 3bb42b02e44737b82039eb3d821453c8112c2c77 140 
nvidia-graphics-drivers-tesla-470_470.103.01.orig.tar.gz
 afbb53a9bdc107be30e74445f305067e75b389dc 208352 
nvidia-graphics-drivers-tesla-470_470.103.01-2.debian.tar.xz
 3afc0cd899448cec36f9c94769a57707c70eba81 7980 
nvidia-graphics-drivers-tesla-470_470.103.01-2_source.buildinfo
Checksums-Sha256:
 4bd58e56b356d94972f5da04413b97c8cb699ef70e2aef601b2ac862f8037803 7572 
nvidia-graphics-drivers-tesla-470_470.103.01-2.dsc
 c9cfae72a984d4272da94e85506ce550f54ea9b003fde4a6aeefa5db30734f69 272473978 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-amd64.tar.gz
 8d375a7c74cc813ae7ad32daed06bb46012beb7101b1c766902e3804ed9908ce 184473786 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-arm64.tar.gz
 3dcd7984957bb2dfbd8b5b0161a4ae63fde79cc03f8b09b15394c3158c3b1f38 67466214 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-ppc64el.tar.gz
 d1ea43ae7a5371143b63adc892e9c1906fc56a829b713326554e6eb63b4948a6 140 
nvidia-graphics-drivers-tesla-470_470.103.01.orig.tar.gz
 042175354dc8d69fb3f5c4ad25641e22371043189cd083346df95ec839484d2b 208352 
nvidia-graphics-drivers-tesla-470_470.103.01-2.debian.tar.xz
 3afc53d593c5b8cdeb35514708e04e4a26c3d2d291b36133d3b863d03452820a 7980 
nvidia-graphics-drivers-tesla-470_470.103.01-2_source.buildinfo
Files:
 98ae808552dc430092f497b91249abe6 7572 non-free/libs optional 
nvidia-graphics-drivers-tesla-470_470.103.01-2.dsc
 f959a1c3152972ecf09fa843481a17c9 272473978 non-free/libs optional 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-amd64.tar.gz
 a4c860d6f6eb3c145d2608b4b9a99699 184473786 non-free/libs optional 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-arm64.tar.gz
 80d993ebd742de78359d26dbed158627 67466214 non-free/libs optional 
nvidia-graphics-drivers-tesla-470_470.103.01.orig-ppc64el.tar.gz
 ec86fbbe7bdbd901ef61057ca7871156 140 

Bug#1006667: python-biopython - build-dependencies unsatisfiable on most architectures.

[peter green]

source: python-biopython
version: 1.79+dfsg-1
severity: serious
tags: patch

muscle was recently removed from most architectures[1], leaving
python-biopython's build-dependencies unsatisfiable on those
architectures. The build-dependency is already marked as
nocheck so presumably is only used for tests.

I added an architecture restriction to the dependency and was able
to perform a successfully test build in an environment without muscle
installed. Note that I used python3-fonttools from testing for the
test build as unstable's version is currently uninstallable. A
debdiff is attached.

The recent upload of python-biopython 1.79+dfsg-2 also moved
w3-dtd-mathml from Suggests to Depends. Unfortunately
w3-dtd-mathml is rc buggy[2] and not in testing. There is a patch
available for the rc bug, but discussion in the bug report
suggests that it may be better to migrate to w3c-sgml-lib
which has a newer version of the mathml dtd.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006161
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994795
diff -Nru python-biopython-1.79+dfsg/debian/changelog 
python-biopython-1.79+dfsg/debian/changelog
--- python-biopython-1.79+dfsg/debian/changelog 2022-02-17 19:15:09.0 
+
+++ python-biopython-1.79+dfsg/debian/changelog 2022-03-01 20:39:50.0 
+
@@ -1,3 +1,11 @@
+python-biopython (1.79+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Restrict architecture list of muscle build-dependency to reflect
+architectures where the current version of muscle is available.
+
+ -- Peter Michael Green   Tue, 01 Mar 2022 20:39:50 +
+
 python-biopython (1.79+dfsg-2) unstable; urgency=medium
 
   * Move w3-dtd-mathml from Suggests to Depends to avoid dangling symlink
diff -Nru python-biopython-1.79+dfsg/debian/control 
python-biopython-1.79+dfsg/debian/control
--- python-biopython-1.79+dfsg/debian/control   2022-02-17 19:15:09.0 
+
+++ python-biopython-1.79+dfsg/debian/control   2022-03-01 20:39:50.0 
+
@@ -25,7 +25,7 @@
emboss ,
fasttree ,
mafft ,
-   muscle ,
+   muscle [i386 amd64 x32] ,
ncbi-blast+ ,
phylip ,
phyml [any-amd64 any-i386] ,

Bug#1006666: emacsql-sqlite3: FTBFS with SQLite3 3.38.0+

[GCS]

Source: emacsql-sqlite3
Version: 1.0.2-1
Severity: serious
Tags: bookworm sid ftbfs patch

Hi,

Your package fails to build with SQLite 3.38.0; the reason is simple.
The output for creating an already existing table changed from
'Error:' to 'Parse error'. The attached patch updates the source
accordingly.

Regards,
Laszlo/GCS
Description: fix build with SQLite3 3.38.0+
 It changed the error message for creating an already existing table.
Forwarded: no
Author: Laszlo Boszormenyi (GCS) 
Last-Update: 2022-03-01

---

--- emacsql-sqlite3-1.0.2.orig/emacsql-sqlite3.el
+++ emacsql-sqlite3-1.0.2/emacsql-sqlite3.el
@@ -214,7 +214,7 @@ each arg will be quoted first."
 (cl-defmethod emacsql-parse ((conn emacsql-sqlite3-connection))
   (with-current-buffer (emacsql-buffer conn)
 (goto-char (point-min))
-(if (looking-at (rx "Error: " (group (1+ any)) eol))
+(if (looking-at (rx "Parse error " (group (1+ any)) eol))
 (signal 'emacsql-error (list (match-string 1)))
   (cl-macrolet ((sexps-in-line! ()
   `(cl-loop until (looking-at "\n")

Bug#1004532: marked as done (php-markdown: PHP message: PHP Fatal error: Array and string offset access syntax with curly braces)

[Debian Bug Tracking System]

Your message dated Tue, 1 Mar 2022 21:49:05 + (UTC)
with message-id 
and subject line php-markdown was removed from unstable and testing
has caused the Debian Bug report #1004532,
regarding php-markdown: PHP message: PHP Fatal error:  Array and string offset 
access syntax with curly braces
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.)


-- 
1004532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-markdown
Version: 1.8.0-1.1
Severity: grave
Tags: patch
Justification: renders package unusable

After the upgrade to PHP 8.1, this package has stopped working
completely with errors like:
---
PHP message: PHP Fatal error:  Array and string offset access syntax with curly 
braces is no longer supported in /usr/share/php/Michelf/Markdown.php on line 955
PHP message: PHP Fatal error:  Array and string offset access syntax with curly 
braces is no longer supported in /usr/share/php/Michelf/Markdown.php on line 
1361
PHP message: PHP Fatal error:  Array and string offset access syntax with curly 
braces is no longer supported in /usr/share/php/Michelf/Markdown.php on line 
1386
PHP message: PHP Fatal error:  Array and string offset access syntax with curly 
braces is no longer supported in /usr/share/php/Michelf/Markdown.php on line 
1799
PHP message: PHP Fatal error:  Array and string offset access syntax with curly 
braces is no longer supported in /usr/share/php/Michelf/Markdown.php on line 
1801
---

I think this patch should fix things up:

--- /usr/share/php/Michelf/Markdown.php.old 2018-01-14 16:49:33.0 
-0800
+++ /usr/share/php/Michelf/Markdown.php 2022-01-29 13:27:18.022519179 -0800
@@ -952,7 +952,7 @@
return $matches[0];
}
 
-   $level = $matches[2]{0} == '=' ? 1 : 2;
+   $level = $matches[2][0] == '=' ? 1 : 2;
 
// ID attribute generation
$idAtt = $this->_generateIdFromHeaderValue($matches[1]);
@@ -1358,7 +1358,7 @@
} else {
// Other closing marker: close one em 
or strong and
// change current token state to match 
the other
-   $token_stack[0] = str_repeat($token{0}, 
3-$token_len);
+   $token_stack[0] = str_repeat($token[0], 
3-$token_len);
$tag = $token_len == 2 ? "strong" : 
"em";
$span = $text_stack[0];
$span = $this->runSpanGamut($span);
@@ -1383,7 +1383,7 @@
} else {
// Reached opening three-char emphasis 
marker. Push on token
// stack; will be handled by the 
special condition above.
-   $em = $token{0};
+   $em = $token[0];
$strong = "$em$em";
array_unshift($token_stack, $token);
array_unshift($text_stack, '');
@@ -1796,9 +1796,9 @@
 * @return string
 */
protected function handleSpanToken($token, &$str) {
-   switch ($token{0}) {
+   switch ($token[0]) {
case "\\":
-   return 

Bug#1000559: marked as done (Compatibility with Symfony 5)

[Debian Bug Tracking System]

Your message dated Tue, 1 Mar 2022 21:44:39 + (UTC)
with message-id 
and subject line Re: Bug#1000558: Compatibility with Symfony 5
has caused the Debian Bug report #1000559,
regarding Compatibility with Symfony 5
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.)


-- 
1000559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-cboden-ratchet
Version: 0.4.2-1
Severity: serious
X-Debbugs-Cc: Debian PHP PEAR Maintainers 
User: pkg-php-p...@lists.alioth.debian.org
Usertags: Symfony5
Control: clone -1 -2 -3
Control: reassign -2 php-robmorgan-phinx 0.9.2-3
Control: reassign -3 php-laravel-framework 6.20.14+dfsg-2

Hi,

Since symfony 5 has finally been uploaded to unstable, packages now
can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new
upstream version should do the trick (Symfony 5 has been released two
years ago).

Symfony 5 (5.4, the upcoming LTS) will a priori be the version in
Bookworm, the next LTS (6.4) is expected in two years from now, so
probably well after the freeze starts (and hopefully the Bookworm
release).

Thanks in advance for fixing this issue, do not hesitate to ask for help
on pkg-php-p...@lists.alioth.debian.org if needed.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
David Prévot dixit:

>Since symfony 5 has finally been uploaded to unstable, packages now
>can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new

Packages are deleted from unstable (and testing) so this can be closed.

bye,
//mirabilos
-- 
Thorsten Glaser (Founding Member)
Teckids e.V. — Digital freedom with youth and education
https://www.teckids.org/--- End Message ---

Bug#1000558: marked as done (Compatibility with Symfony 5)

[Debian Bug Tracking System]

Your message dated Tue, 1 Mar 2022 21:44:39 + (UTC)
with message-id 
and subject line Re: Bug#1000558: Compatibility with Symfony 5
has caused the Debian Bug report #1000558,
regarding Compatibility with Symfony 5
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.)


-- 
1000558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-cboden-ratchet
Version: 0.4.2-1
Severity: serious
X-Debbugs-Cc: Debian PHP PEAR Maintainers 
User: pkg-php-p...@lists.alioth.debian.org
Usertags: Symfony5
Control: clone -1 -2 -3
Control: reassign -2 php-robmorgan-phinx 0.9.2-3
Control: reassign -3 php-laravel-framework 6.20.14+dfsg-2

Hi,

Since symfony 5 has finally been uploaded to unstable, packages now
can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new
upstream version should do the trick (Symfony 5 has been released two
years ago).

Symfony 5 (5.4, the upcoming LTS) will a priori be the version in
Bookworm, the next LTS (6.4) is expected in two years from now, so
probably well after the freeze starts (and hopefully the Bookworm
release).

Thanks in advance for fixing this issue, do not hesitate to ask for help
on pkg-php-p...@lists.alioth.debian.org if needed.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
David Prévot dixit:

>Since symfony 5 has finally been uploaded to unstable, packages now
>can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new

Packages are deleted from unstable (and testing) so this can be closed.

bye,
//mirabilos
-- 
Thorsten Glaser (Founding Member)
Teckids e.V. — Digital freedom with youth and education
https://www.teckids.org/--- End Message ---

Bug#1006352: marked as done (bsfiltger: "Cannot load such file -- sdbm (LoadError)")

[Debian Bug Tracking System]

Your message dated Tue, 01 Mar 2022 21:33:36 +
with message-id 
and subject line Bug#1006352: fixed in bsfilter 1:1.0.19-3
has caused the Debian Bug report #1006352,
regarding bsfiltger: "Cannot load such file -- sdbm (LoadError)"
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.)


-- 
1006352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bsfilter
Version: 1:1.0.19-2.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Due to ruby transition, ruby could not load sdbm module.

I use bsfilter which classifies spam mail.

```
$ bsfilter 
:85:in 
`require': cannot load such file -- sdbm (LoadError)
Did you mean?  dbm
from 
:85:in 
`require'
from /usr/bin/bsfilter:3106:in `get_options'
from /usr/bin/bsfilter:3262:in `setup'
from /usr/bin/bsfilter:3413:in `'
```


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

Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 bsfilter depends on:
ii  ruby  1:3.0

bsfilter recommends no packages.

Versions of packages bsfilter suggests:
pn  ruby-mecab  
pn  ruby-qdbm   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bsfilter
Source-Version: 1:1.0.19-3
Done: Antonio Terceiro 

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated bsfilter 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, 01 Mar 2022 18:26:49 -0300
Source: bsfilter
Architecture: source
Version: 1:1.0.19-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1006352
Changes:
 bsfilter (1:1.0.19-3) unstable; urgency=medium
 .
   [ Caitlin Matos ]
   * use d/pkg.examples instead of override_dh_installexamples
   * build against gem2deb
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Run wrap-and-sort on packaging files
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Bump debhelper from deprecated 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Update Vcs-* headers from URL redirect.
   * Use canonical URL in Vcs-Git.
   * Apply multi-arch hints.
 + bsfilter: Add :any qualifier for ruby dependency.
   * Drop fields with obsolete URLs.
   * Bump debhelper from old 12 to 13.
 .
   [ Antonio Terceiro ]
   * Add patch fix tests to run on modern Ruby
   * Add dependency on ruby-sdbm (Closes: #1006352)
   * Run tests during build and under autopkgtest
Checksums-Sha1:
 632af23b8cc7f69ed184e310a88cf443256c796a 2072 bsfilter_1.0.19-3.dsc
 f9f5eb2770f98cfea0619b69ac093f40dd343b6d 10208 bsfilter_1.0.19-3.debian.tar.xz
 288bbc5065b074d4c04699d5865908849d87bd35 9403 bsfilter_1.0.19-3_amd64.buildinfo
Checksums-Sha256:
 d937242547775b5989e4063681884ef169ce79a76696fae38ae621024ae29731 2072 
bsfilter_1.0.19-3.dsc
 704c8049f4f80aeab44c9519544b8e0c99007fcf3f675f72189f9f3c3e65a959 10208 
bsfilter_1.0.19-3.debian.tar.xz
 3fb4777f5fa451e932a1cbb8b092bc5447ade44bba8ad1beb5de334388330b16 9403 
bsfilter_1.0.19-3_amd64.buildinfo
Files:
 d3e10b6dfed607fcc28927fdf6b826e0 2072 mail optional bsfilter_1.0.19-3.dsc
 40ce9d1206369fecea87805fa84d 10208 mail optional 
bsfilter_1.0.19-3.debian.tar.xz
 17f53459f8f4091101700c1af18f03dd 9403 mail optional 
bsfilter_1.0.19-3_amd64.buildinfo

-BEGIN 

Bug#1006664: python3-fonttools has unmet dependencies

[Michael Biebl]

Package: python3-fonttools
Version: 4.29.1-2
Severity: serious

Installing python3-fonttools is currently not possible:

# apt install python3-fonttools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
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:
 python3-fonttools : Depends: python3-unicodedata2 (>= 14.0.0) but it is not 
installable or
  python3-all (>= 3.11.0) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

Bug#1006352: marked as pending in bsfilter

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/bsfilter/-/commit/eaac70e378ef4d16867d71e7dcdaf60076277be8


Add dependency on ruby-sdbm

Closes: #1006352


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006352

Processed: Bug#1006352 marked as pending in bsfilter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006352 [bsfilter] bsfiltger: "Cannot load such file -- sdbm (LoadError)"
Added tag(s) pending.

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

Bug#999037: marked as done (myspell: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 01 Mar 2022 21:09:12 +
with message-id 
and subject line Bug#1006134: Removed package(s) from unstable
has caused the Debian Bug report #999037,
regarding myspell: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: myspell
Version: 1:3.0+pre3.1-24.2
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 1:3.1-24.2+rm

Dear submitter,

as the package myspell has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1006134

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1005983: marked as done (Please migrate away from dpatch)

[Debian Bug Tracking System]

Your message dated Tue, 01 Mar 2022 21:09:12 +
with message-id 
and subject line Bug#1006134: Removed package(s) from unstable
has caused the Debian Bug report #1005983,
regarding Please migrate away from dpatch
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.)


-- 
1005983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: myspell
Version: 1:3.0+pre3.1-24.2
Severity: serious

dpatch is deprecated and will be removed before the bookworm release.
Please migrate to source format 3.0 (quilt) instead.
--- End Message ---
--- Begin Message ---
Version: 1:3.1-24.2+rm

Dear submitter,

as the package myspell has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1006134

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1005406: marked as done (Fails to build for Linux 5.16 onward)

[Debian Bug Tracking System]

Your message dated Tue, 01 Mar 2022 20:48:53 +
with message-id 
and subject line Bug#1005406: fixed in nvidia-graphics-drivers-tesla-460 
460.106.00-2
has caused the Debian Bug report #1005406,
regarding Fails to build for Linux 5.16 onward
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.)


-- 
1005406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-460
Version: 460.106.00-1
Severity: grave

These modules fail to build, with the compiler reporting that
 is not found.

This is due to an intentional change in Linux 5.16 removing user-space
headers from the kernel include path:
.

Kernel code must use  instead of .

Ben.

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-460
Source-Version: 460.106.00-2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-460 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, 01 Mar 2022 21:31:18 +0100
Source: nvidia-graphics-drivers-tesla-460
Architecture: source
Version: 460.106.00-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 999670 1005406
Changes:
 nvidia-graphics-drivers-tesla-460 (460.106.00-2) unstable; urgency=medium
 .
   * Backport stdarg.h and stddef.h changes from 495.44 to fix kernel module
 build for Linux 5.16.
   * Backport pde_data changes from 510.39.01 to fix kernel module build for
 Linux 5.17.  (Closes: #1005406)
   * nvidia-tesla-460-kernel-support: Provide
 /etc/modprobe.d/nvidia-options.conf as a template taking into account the
 module renaming. This is a slave alternative of the nvidia alternative
 (470.86-1).  (Closes: #999670)
   * dkms.conf: Use a BUILD_EXCLUSIVE equivalent hack to skip build for -rt
 kernels, not supported upstream.
   * Declare Testsuite: autopkgtest-pkg-dkms.
Checksums-Sha1:
 cf1a6d95adc363a5688479d7faea3359bb1bb78c 7442 
nvidia-graphics-drivers-tesla-460_460.106.00-2.dsc
 03539d4ff7d53c49159505a9c391aa8104c3128b 206096 
nvidia-graphics-drivers-tesla-460_460.106.00-2.debian.tar.xz
 8b9b5a2369d4d96e9839c0dd9d91d0035b9126a3 7939 
nvidia-graphics-drivers-tesla-460_460.106.00-2_source.buildinfo
Checksums-Sha256:
 842a7207510d2169e8d3b55d11ef0aed85f2759c1290bddbe0787cf4e979dc38 7442 
nvidia-graphics-drivers-tesla-460_460.106.00-2.dsc
 f082704691ef939ea51784b0d72b574117be8413bc25bb6d245df4f19261746e 206096 
nvidia-graphics-drivers-tesla-460_460.106.00-2.debian.tar.xz
 c0014d145bd8d4db895e933df8b36f59ce1cf2d828e71ed2b00eaef1bf75bfcd 7939 
nvidia-graphics-drivers-tesla-460_460.106.00-2_source.buildinfo
Files:
 53ae4972ebad9bd5fd44d60c8b07ad53 7442 non-free/libs optional 
nvidia-graphics-drivers-tesla-460_460.106.00-2.dsc
 f764e9619b02d9fdcd2e0194e61f8a0e 206096 non-free/libs optional 
nvidia-graphics-drivers-tesla-460_460.106.00-2.debian.tar.xz
 2701b7e8d0b9ed02767ee5b7324114b8 7939 non-free/libs optional 
nvidia-graphics-drivers-tesla-460_460.106.00-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmIegxIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCCL0D/0VNu5v0jlUcP0ZOwTTwoDGJ0jn0Znar/Dy
jKRP6dwK+RJaBEVO2KpXrZTW27sf2wrte1lbIiykY7fc9IkN3fnYkL0o331roK1I

Processed: fixed 1004656 in 0.4.5+repack10+~cs97.25.57-2, closing 1004656

[Debian Bug Tracking System]

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

> fixed 1004656 0.4.5+repack10+~cs97.25.57-2
Bug #1004656 [src:node-istanbul] jest,node-istanbul: fatal error: Cannot find 
module '/usr/share/nodejs/babel-plugin-istanbul/lib/index.js'
Marked as fixed in versions node-istanbul/0.4.5+repack10+~cs97.25.57-2.
> close 1004656
Bug #1004656 [src:node-istanbul] jest,node-istanbul: fatal error: Cannot find 
module '/usr/share/nodejs/babel-plugin-istanbul/lib/index.js'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1006659: python-django-timezone-field breaks python-django-celery-beat autopkgtest: type object 'TimeZoneField' has no attribute 'default_choices'

[Paul Gevers]

Source: python-django-timezone-field, python-django-celery-beat
Control: found -1 python-django-timezone-field/5.0-1
Control: found -1 python-django-celery-beat/2.2.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
python-django-timezone-field from testing5.0-1
python-django-celery-beat from testing2.2.1-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-celery-beat/19656491/log.gz

= test session starts 
==

platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
Django settings: t.proj.settings (from ini file)
rootdir: /tmp/autopkgtest-lxc.boenfl9l/downtmp/autopkgtest_tmp, 
configfile: setup.cfg, testpaths: t/unit/

plugins: case-1.5.3, django-3.5.1, timeout-2.1.0
collected 87 items / 1 error / 3 deselected / 83 selected

 ERRORS 

 ERROR collecting t/unit/test_models.py 


t/unit/test_models.py:85: in 
class CrontabScheduleTestCase(TestCase, TestDuplicatesMixin):
t/unit/test_models.py:87: in CrontabScheduleTestCase
TimeZoneField.default_choices[0][0].zone
E   AttributeError: type object 'TimeZoneField' has no attribute 
'default_choices'
=== warnings summary 
===

../../../../usr/lib/python3/dist-packages/kombu/utils/compat.py:82
  /usr/lib/python3/dist-packages/kombu/utils/compat.py:82: 
DeprecationWarning: SelectableGroups dict interface is deprecated. Use 
select.

for ep in importlib_metadata.entry_points().get(namespace, [])

t/unit/test_schedulers.py:155

/tmp/autopkgtest-lxc.boenfl9l/downtmp/autopkgtest_tmp/t/unit/test_schedulers.py:155: 
PytestUnknownMarkWarning: Unknown pytest.mark.celery - is this a typo? 
You can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html

@pytest.mark.celery(timezone='Europe/Berlin')

t/unit/test_schedulers.py:187

/tmp/autopkgtest-lxc.boenfl9l/downtmp/autopkgtest_tmp/t/unit/test_schedulers.py:187: 
PytestUnknownMarkWarning: Unknown pytest.mark.celery - is this a typo? 
You can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html

@pytest.mark.celery(timezone='Europe/Berlin')

t/unit/test_schedulers.py:223

/tmp/autopkgtest-lxc.boenfl9l/downtmp/autopkgtest_tmp/t/unit/test_schedulers.py:223: 
PytestUnknownMarkWarning: Unknown pytest.mark.celery - is this a typo? 
You can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html

@pytest.mark.celery(timezone='America/New_York')

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 

ERROR t/unit/test_models.py - AttributeError: type object 
'TimeZoneField' has...
 Interrupted: 1 error during collection 

== 3 deselected, 4 warnings, 1 error in 0.55s 
==

autopkgtest [17:17:01]: test upstream



OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-django-timezone-field breaks python-django-celery-beat autopkgtest: type object 'TimeZoneField' has no attribute 'default_choices'

[Debian Bug Tracking System]

Processing control commands:

> found -1 python-django-timezone-field/5.0-1
Bug #1006659 [src:python-django-timezone-field, src:python-django-celery-beat] 
python-django-timezone-field breaks python-django-celery-beat autopkgtest: type 
object 'TimeZoneField' has no attribute 'default_choices'
Marked as found in versions python-django-timezone-field/5.0-1.
> found -1 python-django-celery-beat/2.2.1-1
Bug #1006659 [src:python-django-timezone-field, src:python-django-celery-beat] 
python-django-timezone-field breaks python-django-celery-beat autopkgtest: type 
object 'TimeZoneField' has no attribute 'default_choices'
Marked as found in versions python-django-celery-beat/2.2.1-1.

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

Processed: libobject-pad-perl breaks libtickit-widget-scrollbox-perl autopkgtest: malloc_consolidate(): unaligned fastbin chunk detected

[Debian Bug Tracking System]

Processing control commands:

> found -1 libobject-pad-perl/0.61-1
Bug #1006658 [src:libobject-pad-perl, src:libtickit-widget-scrollbox-perl] 
libobject-pad-perl breaks libtickit-widget-scrollbox-perl autopkgtest: 
malloc_consolidate(): unaligned fastbin chunk detected
Marked as found in versions libobject-pad-perl/0.61-1.
> found -1 libtickit-widget-scrollbox-perl/0.11-1
Bug #1006658 [src:libobject-pad-perl, src:libtickit-widget-scrollbox-perl] 
libobject-pad-perl breaks libtickit-widget-scrollbox-perl autopkgtest: 
malloc_consolidate(): unaligned fastbin chunk detected
Marked as found in versions libtickit-widget-scrollbox-perl/0.11-1.

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

Bug#1006658: libobject-pad-perl breaks libtickit-widget-scrollbox-perl autopkgtest: malloc_consolidate(): unaligned fastbin chunk detected

[Paul Gevers]

Source: libobject-pad-perl, libtickit-widget-scrollbox-perl
Control: found -1 libobject-pad-perl/0.61-1
Control: found -1 libtickit-widget-scrollbox-perl/0.11-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of libobject-pad-perl the autopkgtest of 
libtickit-widget-scrollbox-perl fails in testing when that autopkgtest 
is run with the binary packages of libobject-pad-perl from unstable. It 
passes when run with only packages from testing. In tabular form:


   passfail
libobject-pad-perl from testing0.61-1
libtickit-widget-scrollbox-perl from testing0.11-1
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=libobject-pad-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtickit-widget-scrollbox-perl/19636133/log.gz

t/00use.t ... ok 1 - use Tickit::Widget::ScrollBox;
1..1
ok
t/01scrollbox-horizontal.t .. ok 1 - defined $widget
ok 2 - $widget has refcount 1 initially
ok 3 - $widget has refcount 1 after adding child
ok 4 - $widget wants 11 lines
ok 5 - $widget wants 159 cols
ok 6 - $widget has ->hextent
ok 7 - $static has window after $widget->set_window
ok 8 - $static window starts on line 0
ok 9 - $static window starts on column 0
ok 10 - $static given 24 line window
ok 11 - $static given 159 column window
ok 12 - $hextent->total is 159
ok 13 - $hextent->viewport is 80
ok 14 - $hextent->start is 0
ok 15 - Display initially
ok 16 - $static window starts on column -10 after ->scroll +10
ok 17 - $hextent->start is now 10 after ->scroll +10
ok 18 - Display after scroll +10
ok 19 - $static window starts on column -10 after ->scroll_to 25
ok 20 - $hextent->start is now 10 after ->scroll_to 25
ok 21 - Display after $vextent->scroll_to 25
ok 22 - $widget has refcount 1 at EOF
1..22
ok
t/01scrollbox-vertical.t  ok 1 - defined $widget
ok 2 - $widget has refcount 1 initially
ok 3 - $widget has refcount 1 after adding child
ok 4 - $widget wants 100 lines
ok 5 - $widget wants 20 cols
ok 6 - $widget has ->vextent
ok 7 - $static has window after $widget->set_window
ok 8 - $static window starts on line 0
ok 9 - $static window starts on column 0
ok 10 - $static given 100 line window
ok 11 - $static given 79 column window
ok 12 - $vextent->total is 100
ok 13 - $vextent->viewport is 25
ok 14 - $vextent->start is 0
ok 15 - Display initially
ok 16 - $static window starts on line -10 after ->scroll +10
ok 17 - $vextent->start is now 10 after ->scroll +10
ok 18 - Display after scroll +10
ok 19 - $static window starts on line -25 after ->scroll_to 25
ok 20 - $vextent->start is now 25 after ->scroll_to 25
ok 21 - Display after $vextent->scroll_to 25
ok 22 - $widget has refcount 1 at EOF
1..22
ok
t/02input-key.t . ok 1 - start is 0 initially
ok 2 - hextent start is 0 initially
ok 3 - start moves down +1 after 
ok 4 - start moves down +12 after 
ok 5 - start moves up -1 after 
ok 6 - start moves up -12 after 
ok 7 - start moves to 76 after 
ok 8 - start moves to 0 after 
ok 9 - start moves right +1 after 
ok 10 - start moves right +39 after 
ok 11 - start moves up -1 after 
ok 12 - start moves up -39 after 
ok 13 - start moves to 121 after 
ok 14 - start moves to 0 after 
1..14
malloc_consolidate(): unaligned fastbin chunk detected
All 14 subtests passed t/03input-mouse.t ... ok 1 - vextent 
start is 0 initially

ok 2 - hextent start is 0 initially
ok 3 - start moves down +1 after mouse click down arrow
ok 4 - start moves down +12 after mouse click after area
ok 5 - start moves up -1 after mouse click up arrow
ok 6 - start moves up -12 after mouse click up arrow
ok 7 - start is 22 after mouse drag
ok 8 - start moves down +5 after wheel down
ok 9 - start moves up -5 after wheel up
ok 10 - start moves right +1 after mouse click right arrow
ok 11 - start moves right +39 after mouse click after area
ok 12 - start moves left -1 after mouse click left arrow
ok 13 - start moves left -39 after mouse click before area
ok 14 - start is 26 after mouse drag
1..14
malloc_consolidate(): unaligned fastbin chunk detected
All 14 subtests passed t/04on_demand.t . ok 1 - H invisible 
at 80x25

ok 2 - V invisible at 80x25
ok 3 - H invisible at 80x15
ok 4 - V visible at 80x15
ok 5 - H visible at 30x25
ok 6 - V invisible at 30x25
ok 7 - H visible at 30x15
ok 8 - V visible at 30x15
ok 9 - H invisible at 40x20
ok 10 - V invisible at 

Bug#1006657: bowtie2 breaks optimir autopkgtest: Error with system call: Bowtie2 index creation failed

[Paul Gevers]

Source: bowtie2, optimir
Control: found -1 bowtie2/2.4.5-1
Control: found -1 optimir/1.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
bowtie2from testing2.4.5-1
optimirfrom testing1.1-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/optimir/19635699/log.gz

No output file specified!
Bowtie 2 version 2.4.5 by Ben Langmead (lang...@cs.jhu.edu, 
www.cs.jhu.edu/~langmea)

Usage: bowtie2-build [options]*  
reference_incomma-separated list of files with ref 
sequences

bt2_index_base  write bt2 data to files with this dir/basename
*** Bowtie 2 indexes will work with Bowtie v1.2.3 and later. ***
Options:
-f  reference files are Fasta (default)
-c  reference sequences given on cmd line (as
)
--large-index   force generated index to be 'large', even 
if ref

has fewer than 4 billion nucleotides
--debug use the debug binary; slower, assertions 
enabled

--verbose   log the issued command
-a/--noauto disable automatic -p/--bmax/--dcv 
memory-fitting
-p/--packed use packed strings internally; slower, less 
memory
--bmax max bucket sz for blockwise suffix-array 
builder
--bmaxdivn max bucket sz as divisor of ref len 
(default: 4)

--dcv  diff-cover period for blockwise (default: 1024)
--nodc  disable diff-cover (algorithm becomes 
quadratic)

-r/--noref  don't build .3/.4 index files
-3/--justrefjust build .3/.4 index files
-o/--offrate   SA is sampled every 2^ BWT chars 
(default: 5)
-t/--ftabchars # of chars consumed in initial lookup 
(default: 10)

--threads  # of threads
--seed seed for random number generator
-q/--quiet  verbose output (for debugging)
--h/--help  print this message and quit
--version   print version information and quit

#
##   OPTIMIR   ##
#

Starting workflow for sample S1
 > Starting Library preparation...
Error with system call: Bowtie2 index creation failed: command line = 
bowtie2-build -f 
/tmp/autopkgtest-lxc.ej3c3g68/downtmp/autopkgtest_tmp/OptimiR_Results_Dir/OptimiR_lib/fasta/optimiR_library.fa 
/tmp/autopkgtest-lxc.ej3c3g68/downtmp/autopkgtest_tmp/OptimiR_Results_Dir/OptimiR_lib/bowtie2_index/optimiR_alignment_library 
-q

Check that path to Bowtie2, Cutadapt, Samtools are well defined.

autopkgtest [18:11:44]: test run-sample-analysis



OpenPGP_signature
Description: OpenPGP digital signature

Processed: reassign 1004656 to src:node-istanbul, notfound 1004656 in 0.4.5+ds+~cs56.14.45-1 ...

[Debian Bug Tracking System]

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

> reassign 1004656 src:node-istanbul
Bug #1004656 {Done: Yadd } [node-istanbul] jest,node-istanbul: 
fatal error: Cannot find module 
'/usr/share/nodejs/babel-plugin-istanbul/lib/index.js'
Bug reassigned from package 'node-istanbul' to 'src:node-istanbul'.
Ignoring request to alter found versions of bug #1004656 to the same values 
previously set
No longer marked as fixed in versions 
node-istanbul/0.4.5+repack10+~cs97.25.57-2.
> notfound 1004656 0.4.5+ds+~cs56.14.45-1
Bug #1004656 {Done: Yadd } [src:node-istanbul] 
jest,node-istanbul: fatal error: Cannot find module 
'/usr/share/nodejs/babel-plugin-istanbul/lib/index.js'
Ignoring request to alter found versions of bug #1004656 to the same values 
previously set
> found 1004656 0.4.5+repack10+~cs97.25.57-1
Bug #1004656 {Done: Yadd } [src:node-istanbul] 
jest,node-istanbul: fatal error: Cannot find module 
'/usr/share/nodejs/babel-plugin-istanbul/lib/index.js'
Marked as found in versions node-istanbul/0.4.5+repack10+~cs97.25.57-1 and 
reopened.
> thanks
Stopping processing here.

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

Processed: bowtie2 breaks optimir autopkgtest: Error with system call: Bowtie2 index creation failed

[Debian Bug Tracking System]

Processing control commands:

> found -1 bowtie2/2.4.5-1
Bug #1006657 [src:bowtie2, src:optimir] bowtie2 breaks optimir autopkgtest: 
Error with system call: Bowtie2 index creation failed
Marked as found in versions bowtie2/2.4.5-1.
> found -1 optimir/1.1-1
Bug #1006657 [src:bowtie2, src:optimir] bowtie2 breaks optimir autopkgtest: 
Error with system call: Bowtie2 index creation failed
Marked as found in versions optimir/1.1-1.

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

Processed: severity of 1006134 is normal

[Debian Bug Tracking System]

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

> severity 1006134 normal
Bug #1006134 [src:myspell] myspell: do not ship with bookworm
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#997340: marked as done (pympress: FTBFS: AttributeError: 'Values' object has no attribute 'tab_width')

[Debian Bug Tracking System]

Your message dated Tue, 1 Mar 2022 18:18:03 +
with message-id 

and subject line 
has caused the Debian Bug report #997340,
regarding pympress: FTBFS: AttributeError: 'Values' object has no attribute 
'tab_width'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> Using setuptools.setup():
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'build-requires' will not be supported in future versions. 
> Please use the underscore name 'build_requires' instead
>   warnings.warn(
> running build
> running build_py
> running compile_catalog
> 129 of 153 messages (84%) translated in 
> pympress/share/locale/es/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/es/LC_MESSAGES/pympress.po to 
> pympress/share/locale/es/LC_MESSAGES/pympress.mo
> 150 of 153 messages (98%) translated in 
> pympress/share/locale/de/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/de/LC_MESSAGES/pympress.po to 
> pympress/share/locale/de/LC_MESSAGES/pympress.mo
> 150 of 153 messages (98%) translated in 
> pympress/share/locale/cs/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/cs/LC_MESSAGES/pympress.po to 
> pympress/share/locale/cs/LC_MESSAGES/pympress.mo
> 129 of 153 messages (84%) translated in 
> pympress/share/locale/pl/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/pl/LC_MESSAGES/pympress.po to 
> pympress/share/locale/pl/LC_MESSAGES/pympress.mo
> 153 of 153 messages (100%) translated in 
> pympress/share/locale/fr/LC_MESSAGES/pympress.po
> compiling catalog pympress/share/locale/fr/LC_MESSAGES/pympress.po to 
> pympress/share/locale/fr/LC_MESSAGES/pympress.mo
> creating /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/app.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/surfacecache.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/document.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/__main__.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/talk_time.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/util.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/builder.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/config.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/ui.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/scribble.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/pointer.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/editable_label.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> copying pympress/extras.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress
> creating 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/vlc_backend.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/gst_backend.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/gif_backend.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> copying pympress/media_overlays/base.py -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/media_overlays
> creating /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share
> copying pympress/share/defaults.conf -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share
> creating 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying pympress/share/xml/highlight.glade -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying pympress/share/xml/shortcuts.glade -> 
> /<>/.pybuild/cpython3_3.9_pympress/build/pympress/share/xml
> copying pympress/share/xml/media_overlay.glade -> 
> 

Bug#1006633: procmail is unmaintained upstream

[Santiago Vila]

severity 1006633 important
retitle 1006633 procmail is unmaintained upstream

Hi.

I could understand that we want to get rid of unmaintained software, but 
please do not inflate severities, at least while the discussion takes 
place and a consensus that the package should be removed has not been 
reached. This package is optional, and we are not forcing anybody to use 
it. If we had kept the extra priority, I would be glad to put it in 
"extra", but extra does not exist anymore.


There are some things which need a clarification because they are not 
100% accurate.


El 1/3/22 a las 3:11, Antoine Beaupre escribió:

# unmaintained

procmail is unmaintained. the "Final release", according to
Wikipedia[1], dates back to September 10, 2001 (3.22). this is the
release that is shipped with Debian, although we do have *26*
debian-specific uploads on top of that (3.22-26, in all suites since
buster).


The Debian package is actually based on version "3.23pre" since version 
3.22-21, dated 2013-10-15. I know this is a very minor correction, but I 
think it's important to state the facts right.


While it's true that procmail has not been maintained upstream for a 
long time, Debian is absolutely in his right to maintain its own version 
without an upstream, that's one of the properties of free software.



the last maintainer of procmail explicitly advised us (in #769938) and
other projects (e.g. OpenBSD, in [2]) to stop shipping it.


Same as before, Debian is in his right to follow this advice or not.


That Debian bug report is still open, and concerns a NULL pointer
dereference.


I've just make an upload to fix such bug.

Debian security people: Is there a CVE for Bug #769938? Maybe this
should backported for stable as well.


I do not know if it is exploitable. Strangely, the
original procmail author (Stephen R. van den Berg, presumably) wrote
in that bug report *last year* saying that was "Fixed in upcoming 3.23
release", which has been targeted for release for all of those last 20
years.


I guess he did not refer to the version which was "upcoming 20 years 
ago", but to the git version on which he was working in the last years.


In either case, I'm Cc:ing Stephen, who some time ago was preparing a 
release which included all the Debian fixes so far.


Stephen: If you intend to release a new procmail version, please do so.

Thanks.

Processed (with 5 errors): Re: Bug#1006633: procmail is unmaintained upstream

[Debian Bug Tracking System]

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

> severity 1006633 important
Bug #1006633 [procmail] procmail is unmaintained and a security liability
Severity set to 'important' from 'critical'
> retitle 1006633 procmail is unmaintained upstream
Bug #1006633 [procmail] procmail is unmaintained and a security liability
Changed Bug title to 'procmail is unmaintained upstream' from 'procmail is 
unmaintained and a security liability'.
> Hi.
Unknown command or malformed arguments to command.
> I could understand that we want to get rid of unmaintained software, but
Unknown command or malformed arguments to command.
> please do not inflate severities, at least while the discussion takes
Unknown command or malformed arguments to command.
> place and a consensus that the package should be removed has not been
Unknown command or malformed arguments to command.
> reached. This package is optional, and we are not forcing anybody to use
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#1006384: swi-prolog breaks logol autopkgtest: Program exited with wrong status code

[dogsleg]

Hi Olivier!

> ok,
> I uploaded logol 1.7.9+dfsg-2 built against swi-prolog 8.4.2 and
> closing the issue with upload.
> Let's see what happens for migration.

Thank you!

Bug#1006352: bsfiltger: "Cannot load such file -- sdbm (LoadError)"

[Antonio Terceiro]

On Thu, Feb 24, 2022 at 10:51:16AM +0900, YABUKI Yukiharu wrote:
> Package: bsfilter
> Version: 1:1.0.19-2.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Due to ruby transition, ruby could not load sdbm module.
> 
> I use bsfilter which classifies spam mail.
> 
> ```
> $ bsfilter 
> :85:in
>  `require': cannot load such file -- sdbm (LoadError)
> Did you mean?  dbm
> from 
> :85:in
>  `require'
> from /usr/bin/bsfilter:3106:in `get_options'
> from /usr/bin/bsfilter:3262:in `setup'
> from /usr/bin/bsfilter:3413:in `'
> ```

Yes, `sdbm` has been removed from the standard library. Thanks for the
bug report, since bsfilter has no automated tests (otherwise we would
have caught this earlier).

I just uploaded a standalone ruby-sdbm package to NEW now, and will
upload a bsfilter update with the right dependency as soon as that's in
the archive.


signature.asc
Description: PGP signature

Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)

[Paul Gevers]

Dear logol and swi-prolog maintainers,

On 01-03-2022 10:21, Debian Bug Tracking System wrote:

Changes:
  logol (1.7.9+dfsg-2) unstable; urgency=medium
  .
* Source only upload, rebuilding against swi-prolog/8.4.2+dfsg-2 after
  swi-prolog ABI break (Closes: #1006384).


This "fix" suggest there may be more breakage, normally the Release Team 
would schedule binNMU's. Can you please elaborate how ABI is normally 
maintained within swi-prolog, such that the rebuilds can be detected and 
requested? I fail to see how in the case of logol and swi-prolog the 
right versions are chosen. In other words, I think the "fixed" logol can 
migrate to testing even if swi-prolog does not and will be broken in 
testing until swi-prolog can migrate. Normally *versioned* dependencies 
should prevent this.


I checked, there are more reverse build dependencies of swi-prolog, I'm 
afraid there's more breakage that hasn't been detected yet. (eye seems 
to go in lockstep, so that package currently seems OK).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1005899: mplayer: should not release with bookworm

[Ian Jackson]

Reimar Döffinger writes ("Re: Bug#1005899: mplayer: should not release with 
bookworm"):
> 
> These are definitely fixed in 1.5, and the fix for giflib should be not hard 
> to cherry-pick for 1.4 if there is a need.
> 
> > and #958865 (crash on theora) really ought
> > to be fixed too.
> 
> I could never reproduce it, but it could be I never tested 1.4 Debian build. 
> But chances are this is fixed by 1.5 at least.

Interesting, thanks.

> >  If we had a maintainer who is able to deal with
> > those, and also deal with some of the outstanding bug gardening, then
> > we could conclude that mplayer ought to stay.
> 
> I am completely unfamiliar with the Debian processes and doubt I have time to 
> learn (and interacting with the bug tracker seems supremely painful and 
> confusing to me).
> So I also don't know what exactly is needed.
> But if it's just about debugging/fixing bugs or finding patches to 
> cherry-pick I am here, and as said the lists are also there, as is MPlayer's 
> trac bug tracker (though not that actively monitored, so would need to ping 
> me for a fast response).

I think what is needed is precisely for someone to volunteer to do the
bug gardening, coordination work, routine package maintenance, and so
on.

That doesn't require a Debian *expert*, but it does require a basic
level of Debian knowledge (or the time to get stuck in and learn).

While the maintainer role doesn't ahve to be a deep programming role,
it does take time and energy.  Sadly at the moment I don't think we
have a prospective maintainer for mplayer in Debian.

As I say, should someone come forward who wants to do this work, I
would be happy to sponsor their uploads, so it doesn't have to be
someone with formal status (eg Debian Project Member aka DD).  And
Sebastian has said someone who wants to be steward of mplayer in
Debian would be welcome to take over ownership of the package.

Best wishes,
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1006132: marked as done (ifrench-gut: please stop build-depending on myspell-tools)

[Debian Bug Tracking System]

Your message dated Tue, 01 Mar 2022 10:48:33 +
with message-id 
and subject line Bug#1006132: fixed in ifrench-gut 1:1.0-32.2
has caused the Debian Bug report #1006132,
regarding ifrench-gut: please stop build-depending on myspell-tools
to be marked as done.

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

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


-- 
1006132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ifrench-gut
Version: 1:1.0-32.1
Severity: serious

Dear maintainer,

we plan to remove src:myspell really soon, and together with it also
the package "myspell-tools".
Your package still depends on it.

Please see whether you can move whatever the package is doing to
hunspell-tools, or otherwise please tell us src:hunspell maintainers how
that is not possible for you.

Thank you for maintaining ifrench-gut.


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ifrench-gut
Source-Version: 1:1.0-32.2
Done: Agustin Martin Domingo 

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

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

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

Debian distribution maintenance software
pp.
Agustin Martin Domingo  (supplier of updated ifrench-gut 
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, 01 Mar 2022 11:07:15 +0100
Source: ifrench-gut
Architecture: source
Version: 1:1.0-32.2
Distribution: unstable
Urgency: medium
Maintainer: Lionel Elie Mamane 
Changed-By: Agustin Martin Domingo 
Closes: 1006132
Changes:
 ifrench-gut (1:1.0-32.2) unstable; urgency=medium
 .
   * Non maintainer upload with maintainer agreement.
   * Migrate myspell affix file generation from myspell-tools to
 hunspell-tools ispellaff2myspell (Closes: #1006132).
Checksums-Sha1:
 feb6eef52cb9ed8d8fd23ade22bace11dba55291 1811 ifrench-gut_1.0-32.2.dsc
 4ea2db7ee972a0d888de7efe544e00b0bd46ae82 27840 ifrench-gut_1.0-32.2.diff.gz
 9d08cd492e8071159075464cfd7dc8cf75dedb3b 6253 
ifrench-gut_1.0-32.2_amd64.buildinfo
Checksums-Sha256:
 478f48040b17301e007be49812bced658c8c4d47793c264cbdd2b773798a4c3f 1811 
ifrench-gut_1.0-32.2.dsc
 fa9964da62ca6fa0258c258d9024ef8ade93433eb522509887a5aaea1beab536 27840 
ifrench-gut_1.0-32.2.diff.gz
 0d69c56c1acec3a68690127050b93861d3b22ca5a3c3f55dcd82b1c6e32e3b2d 6253 
ifrench-gut_1.0-32.2_amd64.buildinfo
Files:
 746ad6e5b44b8b87d94c8418bc27c513 1811 text optional ifrench-gut_1.0-32.2.dsc
 bf2a0b14704f364f88b8d14080327fba 27840 text optional 
ifrench-gut_1.0-32.2.diff.gz
 cc02b1924e3f2faa7d8b52903d2ba50e 6253 text optional 
ifrench-gut_1.0-32.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEEehey7p+gYd346SEFJrCLeiggvwFAmId8iYACgkQFJrCLeig
gvxcZg//XYZFLTN4MZguVj8Z94PBYfRjsJO9iT/Zzt0oM4Gf7+hdFqlxXhdeKCyi
FvKHwYCNaT4+4B6sscaYKVDCyBeBEj0WUY/AASMXH2bq3n6MyxXo5aeltjGhYkYc
XF0njQhNnc5oP3O35MFnLGWsypBOM8IWdbtXEzPA25iuk7GjICstjZtI+1CcEwdK
yaabwCZ1drZ8ZKELS992+ByiJQXp/Y0h4TIasVS82HhZpgutOdBN/k+5jcFj02Ib
v9ABacCLANlSxEMYCIi79jdJOTF2J+2j55tUEvmrfx8VFWRnjTwl0V+pIFi+8M3n
J/FaPOAJyBtWAn7SDIC+SvWwQeqia+K+ffq78sAOFPVkR43rPe8vBYdCgCSZEH5d
7fEsTzU7CTtKfQz+NHw/KrcMbeUHasVqyMatMYa9368wTUYd97wcFugkuLtyBTvG
3jNm6fiLIb74fO19RqIbEyj+Em07c9hR6HTjOYYCp3VMEqytHf/vZzRdp16BG75z
duWWT3fQuDNCRiMo/wY97IUmCkSA7C3Ck9m5TmFXWMGYtj8BTUYQ1HSiquJTeak/
VHbT7xlXX6MnDrPf+0q7lzGcBUInXgGqopE1fTElupRYAEPTLOSXCfCS9Zywtve8
13KDVvunNHF0KWHHFj112vrmA3U90PhFGr0JM5p3HV6kV+TF/eM=
=9Y4P
-END PGP SIGNATURE End Message ---

Processed: block 1004684 with 1006642

[Debian Bug Tracking System]

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

> block 1004684 with 1006642
Bug #1004684 {Done: Paul Gevers } [src:ddnet] src:ddnet: 
fails to migrate to testing for too long: FTBFS on armel and mipsel
1004684 was not blocked by any bugs.
1004684 was not blocking any bugs.
Added blocking bug(s) of 1004684: 1006642
> thanks
Stopping processing here.

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

Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools

[Lionel Élie Mamane]

On Tue, Mar 01, 2022 at 09:48:04AM +0100, Agustin Martin wrote:

> Forgot to mention, but if you agree with the changes but are too
> busy to prepare an upload I can prepare a NMU.

By all means, please do.

Thanks.

Bug#1006642: osk-sdl: autopkgtest failure (with gcc-12)

[Bas Couwenberg]

Source: osk-sdl
Version: 0.66-4
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest for you package fail (with gcc-12):

 autopkgtest [05:11:09]: test test-functional: [---
 ** Testing key script with 'physical' key input
 INFO: osk-sdl v0.66
 ERROR: Syntax error on line 4
 ERROR: Could not parse config file: ./osk.conf
 ERROR: No valid config file specified, use -c [path]
 ERROR: Unexpected result!
got:
expected:   postmarketOS
 ** Testing osk toggle button and 'mouse' key input
 INFO: osk-sdl v0.66
 ERROR: Syntax error on line 4
 ERROR: Could not parse config file: ./osk.conf
 ERROR: No valid config file specified, use -c [path]
 ERROR: Unexpected result!
got:
expected:   qwerty
 autopkgtest [05:11:25]: test test-functional: ---]
 autopkgtest [05:11:25]: test test-functional:  - - - - - - - - - - results - - 
- - - - - - - -
 test-functional  FAIL non-zero exit status 2
 autopkgtest [05:11:25]:  summary
 test-machine-functional SKIP Test requires machine-level isolation but testbed 
does not provide that
 test-functional  FAIL non-zero exit status 2

https://ci.debian.net/data/autopkgtest/testing/amd64/o/osk-sdl/19643682/log.gz

Bug#1006384: marked as done (swi-prolog breaks logol autopkgtest: Program exited with wrong status code)

[Debian Bug Tracking System]

Your message dated Tue, 01 Mar 2022 09:18:37 +
with message-id 
and subject line Bug#1006384: fixed in logol 1.7.9+dfsg-2
has caused the Debian Bug report #1006384,
regarding swi-prolog breaks logol autopkgtest: Program exited with wrong status 
code
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.)


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

Source: swi-prolog, logol
Control: found -1 swi-prolog/8.4.2+dfsg-2
Control: found -1 logol/1.7.9+dfsg-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
swi-prolog from testing8.4.2+dfsg-2
logol  from testing1.7.9+dfsg-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/l/logol/19529867/log.gz

calling logol with parameters -g 1799.logol -s 1799.fasta -dna
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /var/log/logol/logol.log (Permission denied)
at java.base/java.io.FileOutputStream.open0(Native Method)
at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
at java.base/java.io.FileOutputStream.(FileOutputStream.java:237)
at java.base/java.io.FileOutputStream.(FileOutputStream.java:158)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
	at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
	at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
	at 
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
	at 
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
	at 
org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672)
	at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516)
	at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
	at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)

at org.apache.log4j.LogManager.(LogManager.java:127)
at org.apache.log4j.Logger.getLogger(Logger.java:117)
at org.irisa.genouest.logol.Logol.(Unknown Source)
For help, use option -h
INFO org.irisa.genouest.logol.Logol  - Using configuration file: 
/usr/share/logol/prolog/logol.properties

INFO org.irisa.genouest.logol.Logol  - option g called with 1799.logol
INFO org.irisa.genouest.logol.Logol  - option s called with 1799.fasta
INFO org.irisa.genouest.logol.Logol  - No maximum solutions defined, 
using defaults

INFO org.irisa.genouest.logol.Logol  - option dna called
INFO org.irisa.genouest.logol.Logol  - Start analyse to create grammar 
analyser

Executing prolog for pre-analyse
java.io.FileNotFoundException: 
/tmp/1799.logol.be129f0a-eeb3-4c10-a744-e5ccabb1087e.pre.res (No such 
file or directory)

at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
at java.base/java.io.FileInputStream.(FileInputStream.java:157)
at java.base/java.io.FileReader.(FileReader.java:75)
at org.irisa.genouest.logol.Logol.loadVariables2Postpone(Unknown Source)
at org.irisa.genouest.logol.Logol.generatePreAnalysis(Unknown Source)
at org.irisa.genouest.logol.Logol.analyse(Unknown Source)
at org.irisa.genouest.logol.Logol.execute(Unknown Source)
at 

Bug#1005778: pypandoc: diff for NMU version 1.7.2+ds0-1.1

[Elena ``of Valhalla'']

On 2022-02-28 at 15:31:58 -0500, nick black wrote:
> agreed, so long as it's not required by most outputs (i.e. you
> can run pypandoc without it and it works).

Latex is only used for pdf output, and even there it's just the default
option, but there is support for other engines as well.

If that wasn't the case, I agree that it should be a dependency, but it
should be a dependency of pandoc rather than pypandoc.

The issue here is that the tests of pypandoc do try to generate a pdf
(as it is a pretty common usecase), and thus they do need latex
installed, but that's only a requirement for the tests.

> alrightie. this was my NM application bug; i guess i will find
> another one. have a good day!

I'm even more sorry about having wasted your time then :(

-- 
Elena ``of Valhalla''


signature.asc
Description: PGP signature

Bug#1006384: swi-prolog breaks logol autopkgtest: Program exited with wrong status code

[olivier sallou]

Le lun. 28 févr. 2022 à 06:37,  a écrit :

> Dear Olivier,
>
> sorry for the delay with my message and thanks for your input.
>
> olivier sallou писал 2022-02-25 12:12:
> > ok,
> > after a quick look, issue is Logol is compiled against swi-prolog, and
> > there is an ABI issue I think, getting error:
> >
> > incompatible version (file: 67, Prolog: 68)]
> >
> > Recompiling logol in sid against swi-prolog 8.4.2+dfsg-2 results in
> > correct execution/tests.
> >
> > So, 2 things:
> >
> > * As swi-prolog is only a debian update (-1 to -2), I wonder why we
> > have this break now
> > * Possible fix is to rebuild logol package against this version in
> > sid, with a dep requirement on swi-prolog>=8.4.2+dfsg-2. But I don't
> > know how this should be managed (logol in testing will still prevent
> > swi-prolog to go, and logol in sid won't either go to testing because
> > will need swi-prolog version from sid...)
>
> It is not just Debian update. I've uploaded new upstream version of
> SWI-Prolog on Feb 15 (upgrade from 8.2.4 to 8.4.2). It is a new major
> update of stable branch of SWI-Prolog, and it breaks compatibility. As
> I can see logol tests failed already with 8.4.2+dfsg-1. There was an
> issue with ODBC support for SWI-Prolog on 32-bit platforms, so I
> uploaded
> 8.4.2+dfsg-2 fixing this issue.
>
> I think swi-prolog and (updated) logol may migrate simultaneously as it
> is the case for swi-prolog and eye (another package depending on
> swi-prolog). Otherwise, we could ask someone from Debian Release team to
> trigger the migration for the involved packages.
>
ok,
I uploaded logol 1.7.9+dfsg-2 built against swi-prolog 8.4.2 and closing
the issue with upload.
Let's see what happens for migration.

Olivier



>
> Cheers!
> Lev
>
> > Le jeu. 24 févr. 2022 à 19:36, Paul Gevers  a
> > écrit :
> >
> >> Source: swi-prolog, logol
> >> Control: found -1 swi-prolog/8.4.2+dfsg-2
> >> Control: found -1 logol/1.7.9+dfsg-1
> >> Severity: serious
> >> Tags: sid bookworm
> >> X-Debbugs-CC: debian...@lists.debian.org
> >> User: debian...@lists.debian.org
> >> Usertags: breaks needs-update
> >>
> >> Dear maintainer(s),
> >>
> >> With a recent upload of swi-prolog the autopkgtest of logol fails in
> >>
> >> testing when that autopkgtest is run with the binary packages of
> >> swi-prolog from unstable. It passes when run with only packages from
> >>
> >> testing. In tabular form:
> >>
> >> passfail
> >> swi-prolog from testing8.4.2+dfsg-2
> >> logol  from testing1.7.9+dfsg-1
> >> all others from testingfrom testing
> >>
> >> I copied some of the output at the bottom of this report.
> >>
> >> Currently this regression is blocking the migration of swi-prolog to
> >>
> >> testing [1]. Due to the nature of this issue, I filed this bug
> >> report
> >> against both packages. Can you please investigate the situation and
> >> reassign the bug to the right package?
> >>
> >> More information about this bug and the reason for filing it can be
> >> found on
> >>
> > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> >>
> >> Paul
> >>
> >> [1] https://qa.debian.org/excuses.php?package=swi-prolog
> >>
> >>
> >
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/logol/19529867/log.gz
> >>
> >> calling logol with parameters -g 1799.logol -s 1799.fasta -dna
> >> log4j:ERROR setFile(null,true) call failed.
> >> java.io.FileNotFoundException: /var/log/logol/logol.log (Permission
> >> denied)
> >> at java.base/java.io [1].FileOutputStream.open0(Native
> >> Method)
> >> at java.base/java.io
> >> [1].FileOutputStream.open(FileOutputStream.java:298)
> >> at java.base/java.io
> >> [1].FileOutputStream.(FileOutputStream.java:237)
> >> at java.base/java.io
> >> [1].FileOutputStream.(FileOutputStream.java:158)
> >> at
> >> org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> >> at
> >> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> >> at
> >>
> > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> >> at
> >>
> >
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
> >> at
> >>
> >
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> >> at
> >>
> >
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> >> at
> >>
> >
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> >> at
> >>
> >
> org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672)
> >> at
> >>
> >
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516)
> >> at
> >>
> >
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> >> at
> >>
> >
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> >> at org.apache.log4j.LogManager.(LogManager.java:127)
> >> at 

Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools

[Agustin Martin]

El dom, 27 feb 2022 a las 22:32, Agustin Martin
() escribió:
>
> Control: tags -1 +patch
>
> El vie, 25 feb 2022 a las 8:51, Lionel Élie Mamane
> () escribió:
> >
> > On Fri, Feb 25, 2022 at 12:51:32AM +0100, Agustin Martin wrote:
> > > El jue, 24 feb 2022 a las 16:09, Lionel Élie Mamane
> > > () escribió:
> >
> > > I have been looking at popcons and seems that regarding ispell dicts
> > > ifrench-gut is way more popular than ifrench, but on the hunspell side
> > > the winner is hunspell-fr (which pulls hunspell-fr-classical)
> >
> > > I do not know about the merits of the different ispell dicts, but
> > > keeping ifrench-gut ispell dict  seems reasonable. On the other hand,
> > > unless it provides something better, dropping myspell-fr-gut as a real
> > > dict seems also reasonable, but this really requires more feedback
> > > from french users.
> >
> > If the -gut variant has a "better" word list, then I expect it is
> > better for both ispell and myspell?
>
> Hi, Lionel,
>
> myspell is gone, only hunspell is available and supports old myspell
> dictionaries like this one.  Usually hunspell specific dicts are
> better than old myspell and ispell dicts, but sometimes they are just
> different and each one has its merits. Note that hunspell-fr-*dicts
> come from different source (https://grammalecte.net/home.php?prj=fr)
> than both ispell french dicts.
>
> If you think is useful to keep a myspell/hunspell version of gutenberg
> dict I am attaching a patch with a possible migration to
> ispellaff2myspell. In my limited tests it works better than old dict
> since it includes ' and - as wordchars. Whether to remove it or not in
> favour of hunspell-fr-* is something that can be decided later by
> french dicts maintainers (and will require some coordination). I have
> also noticed that while package contains a couple of patches with
> dpatch extension it does nor really use dpatch, so that would not be a
> problem, The mismatch in ispell hash format should be fixed by the new
> build (although I suggest to migrate to ispell-autobuildhash), so this
> patch should be enough if no side effects are found,

Hi, Lionel

Forgot to mention, but if you agree with the changes but are too busy
to prepare an upload I can prepare a NMU.

Regards,

-- 
Agustin