Bug#992654: marked as done (ruby-rugged autopkgtest regressed in Augustus 2021)

[Debian Bug Tracking System]

Your message dated Tue, 21 Sep 2021 05:33:29 +
with message-id 
and subject line Bug#992654: fixed in ruby-rugged 1.1.0+ds-5
has caused the Debian Bug report #992654,
regarding ruby-rugged autopkgtest regressed in Augustus 2021
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.)


-- 
992654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc, ruby-rugged
Control: found -1 glibc/2.31-16
Control: found -1 ruby-rugged/1.1.0+ds-4
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 glibc the autopkgtest of ruby-rugged fails in
testing when that autopkgtest is run with the binary packages of glibc
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
glibc  from testing2.31-16
ruby-ruggedfrom testing1.1.0+ds-4
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of glibc 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

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
glibc/2.31-16. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=glibc

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rugged/14750518/log.gz
autopkgtest [11:15:38]: test gem2deb-test-runner: [---

┌──┐
│ Checking Rubygems dependency resolution on ruby2.7
   │
└──┘

GEM_PATH= ruby2.7 -e gem\ \"rugged\"

┌──┐
│ Run tests for ruby2.7 from debian/ruby-tests.rb
   │
└──┘

mv lib .gem2deb.lib
mv ext .gem2deb.ext
RUBYLIB=. GEM_PATH= ruby2.7 debian/ruby-tests.rb
Run options: --seed 56390

# Running:

S....F...

Finished in 16.209826s, 33.8683 runs/s, 144.0484 assertions/s.

  1) Failure:
RemoteNetworkTest#test_remote_check_connection_push_credentials
[/tmp/autopkgtest-lxc.3h184rhw/downtmp/build.1At/src/test/remote_test.rb:40]:
Expected false to be truthy.

549 runs, 2335 assertions, 1 failures, 0 errors, 5 skips

You have skipped tests. Run with --verbose for details.
mv .gem2deb.lib lib
mv .gem2deb.ext ext
autopkgtest [11:15:55]: test gem2deb-test-runner: ---]




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-rugged
Source-Version: 1.1.0+ds-5
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-rugged package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#992654: marked as pending in ruby-rugged

[Cédric Boutillier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-rugged/-/commit/5a953c3e52a0f2441e8674ff4ce3a8a42bd7bb92


skip failing autopkgtest since Github disabled usr/pass git remote access 
(Closes: #992654)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/992654

Processed: Bug#992654 marked as pending in ruby-rugged

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #992654 [ruby-rugged] ruby-rugged autopkgtest regressed in Augustus 2021
Added tag(s) pending.

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

Processed: fixed 992668 in 1.1.4-3+b5

[Debian Bug Tracking System]

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

> fixed 992668 1.1.4-3+b5
Bug #992668 [ricochet-im] ricochet-im: does not start
Marked as fixed in versions ricochet-im/1.1.4-3.
> thanks
Stopping processing here.

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

Bug#992668: ricochet-im: does not start

[Paul Wise]

Control: fixed -1 + 1.1.4-3+b5

On Sat, 18 Sep 2021 13:06:25 +0800 Paul Wise wrote:

> I'll request the release team to rebuild it in bullseye/bookworm.

The rebuild has now happened for unstable/testing.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#994799: FTBFS on i386

[Daniel Baumann]

Package: firefox-esr
Version: 91.1.0esr-1
Severity: serious
Tags: experimental

Hi,

unfortunately the upstream changes introduced in math_private.h from 
91.0.1esr-1 to 91.1.0esr-1 make firefox fail to build from source on i386:


---snip---
In file included from /<>/modules/fdlibm/src/e_acos.cpp:44:
/<>/modules/fdlibm/src/math_private.h:34:21: error: 
conflicting declaration ‘typedef __double_t double_t’

   34 | typedef __double_t  double_t;
  | ^~~~
In file included from /usr/include/c++/10/cmath:45,
 from 
/<>/build-browser/dist/system_wrappers/cmath:3,
 from 
/<>/build-browser/dist/stl_wrappers/cmath:60,

 from /<>/modules/fdlibm/src/e_acos.cpp:41:
/usr/include/math.h:156:21: note: previous declaration as ‘typedef long 
double double_t’

  156 | typedef long double double_t;
  | ^~~~
make[5]: *** [/<>/config/rules.mk:676: e_acos.o] Error 1
make[5]: Leaving directory 
'/<>/build-browser/modules/fdlibm/src'
make[4]: *** [/<>/config/recurse.mk:72: 
modules/fdlibm/src/target-objects] Error 2

---snap---

Regards,
Daniel

Bug#994798: util-linux FTBFS: configure: error: raw selected, but required raw.h header file not available

[Helmut Grohne]

Source: util-linux
Version: 2.37.2-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-ker...@lists.debian.org

util-linux fails to build from source in unstable on amd64. I think the
relevant bits are:


| dh_auto_configure -- --enable-raw --with-selinux --with-smack --enable-partx 
--with-systemd --with-udev --with-audit --with-cryptsetup=dlopen --enable-write 
--enable-static-programs=fdisk,sfdisk,blkid --without-python --disable-login 
--disable-nologin --disable-kill --disable-chfn-chsh --disable-cal 
--disable-hwclock-gplv3
|   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --enable-raw 
--with-selinux --with-smack --enable-partx --with-systemd --with-udev 
--with-audit --with-cryptsetup=dlopen --enable-write 
--enable-static-programs=fdisk,sfdisk,blkid --without-python --disable-login 
--disable-nologin --disable-kill --disable-chfn-chsh --disable-cal 
--disable-hwclock-gplv3
...
| checking for linux/raw.h... no
...
| configure: error: raw selected, but required raw.h header file not available

I suspect that linux dropped the header and that way makes util-linux
FTBFS.

Helmut

Processed: found 994790 in 6.0.2-1, bug 994790 is forwarded to https://github.com/ZerBea/hcxtools/issues/155 ...

[Debian Bug Tracking System]

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

> found 994790 6.0.2-1
Bug #994790 [src:hcxtools] hcxtools: CVE-2021-32286
Marked as found in versions hcxtools/6.0.2-1.
> forwarded 994790 https://github.com/ZerBea/hcxtools/issues/155
Bug #994790 [src:hcxtools] hcxtools: CVE-2021-32286
Set Bug forwarded-to-address to 'https://github.com/ZerBea/hcxtools/issues/155'.
> tags 994790 + upstream
Bug #994790 [src:hcxtools] hcxtools: CVE-2021-32286
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#992913: marked as done (trickle: FTBFS due to RPC removal from glibc)

[Debian Bug Tracking System]

Your message dated Tue, 21 Sep 2021 02:36:13 +
with message-id 
and subject line Bug#992913: fixed in trickle 1.07-11
has caused the Debian Bug report #992913,
regarding trickle: FTBFS due to RPC removal from glibc
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.)


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

Dear maintainer,

The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead,
which also brings new features (IPv6, Kerberos support, ...).

For this reason trickle now fails to build from source. You will find
attached a patch to switch to the TI RPC implementation, fixing the
FTBFS.

Regards,
Aurelien
diff -u trickle-1.07/Makefile.am trickle-1.07/Makefile.am
--- trickle-1.07/Makefile.am
+++ trickle-1.07/Makefile.am
@@ -24,12 +24,12 @@
 
 trickled_SOURCES = trickled.c atomicio.c print.c bwstat.c client.c conf.c \
util.c cleanup.c getopt.c xdr.c
-trickled_LDADD = @EVENTLIB@ -lbsd
+trickled_LDADD = @EVENTLIB@ @TIRPC_LIBS@ -lbsd
 
 tricklectl_SOURCES = tricklectl.c trickledu.c atomicio.c xdr.c
-tricklectl_LDADD = @ERRO@  -lbsd
+tricklectl_LDADD = @ERRO@ @TIRPC_LIBS@ -lbsd
 
-AM_CFLAGS = -Wall -Icompat @EVENTINC@
+AM_CFLAGS = -Wall -Icompat @EVENTINC@ @TIRPC_CFLAGS@
 
 overloaddir = $(libdir)
 #overload_DATA = libtrickle.so
diff -u trickle-1.07/configure.in trickle-1.07/configure.in
--- trickle-1.07/configure.in
+++ trickle-1.07/configure.in
@@ -119,6 +119,9 @@
 AC_SUBST(EVENTINC)
 AC_SUBST(EVENTLIB)
 
+dnl Checks for libtirpc
+PKG_CHECK_MODULES(TIRPC, libtirpc)
+
 dnl check if underscores are needed
 AC_MSG_CHECKING(if underscores are needed for symbols)
 AC_TRY_RUN(
diff -u trickle-1.07/debian/control trickle-1.07/debian/control
--- trickle-1.07/debian/control
+++ trickle-1.07/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Robert Lemmen 
 Build-Depends: debhelper (>= 7.0.0), libevent-dev (>= 0.7b), autoconf,
- libbsd-dev, dh-autoreconf
+ libbsd-dev, dh-autoreconf, pkg-config, libtirpc-dev
 Standards-Version: 3.9.4
 
 Package: trickle
--- End Message ---
--- Begin Message ---
Source: trickle
Source-Version: 1.07-11
Done: Axel Beckert 

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated trickle 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, 21 Sep 2021 04:18:31 +0200
Source: trickle
Architecture: source
Version: 1.07-11
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Closes: 901077 992913
Changes:
 trickle (1.07-11) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Axel Beckert ]
   * Set Maintainer to Debian QA Group. (See #994644)
   * Convert to Debian source format "3.0 (quilt)"
 + Change trickled.conf from patch to file at debian/trickled.conf.
   * debian/watch: Bump version to 4 and use HTTPS.
   * Run "wrap-and-sort -a".
   * Add Homepage header. Use Github repo until original homepage is fixed.
 (Closes: #901077)
   * Add Vcs-* headers for new git repo on Salsa.
   * Remove trailing whitespace from debian/changelog and debian/rules.
   * Set "Rules-Requires-Root: no".
   * Use "dh" sequencer (rewrite debian/rules) and debhelper-compat=13.
 + Drop dependencies on autoconf and dh-autoreconf.
 + Enable hardening build flags.
 + Drop all patches against generated files (configure, config.*,
   Makefile.in, aclocal.m4, ltmain.sh, etc.)
 + Add patch to make test target build under dh compat level 13.
 + Add several generated files to debian/clean.
 + Use --no-parallel as the package FTBFS otherwise.
 + Drop now redundant 

Bug#994795: w3-dtd-mathml: invalid redeclaration of predefined entities amp and lt yields failures with libxml2 2.9.12

[Vincent Lefevre]

Alternatively, I wonder whether w3c-sgml-lib (which appears to be
correct) could replace w3-dtd-mathml, in which case w3-dtd-mathml
should be removed from Debian, as what had been done with
w3c-dtd-xhtml.

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

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

On 2021-09-20 17:50:56 +0200, Thorsten Glaser wrote:
> > > But if this upstream change affects DTDs that were once released, maybe
> > > it should accept, but ignore, this specific wrong redeclaration.
> > 
> > Perhaps. This should probably be first talked with upstream.
> 
> So indeed. Can one of you bring this to them? (My contributions to
> libxml2 don’t appear to be liked, even if multiple CVEs could have
> been avoided by applying them.)

Done here: https://gitlab.gnome.org/GNOME/libxml2/-/issues/307

I've also reported

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994795

against w3-dtd-mathml, which has a similar issue (also invalid
redeclarations of the amp and lt entities, though these
redeclarations are different from the w3c-dtd-xhtml ones).

BTW, this doesn't affect only validation, but also entity resolution,
e.g. when using "xmllint --noent", which makes the issue even worse.

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

Bug#994350: marked as done (python-djvulibre: Removal of the python3-*-dbg packages in sid/bookworm)

[Debian Bug Tracking System]

Your message dated Tue, 21 Sep 2021 00:35:11 +
with message-id 
and subject line Bug#994350: fixed in python-djvulibre 0.8.7-1
has caused the Debian Bug report #994350,
regarding python-djvulibre: Removal of the python3-*-dbg packages in 
sid/bookworm
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.)


-- 
994350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-djvulibre
Version: 0.8.4-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal

Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
https://lists.debian.org/debian-python/2021/09/msg4.html

Stop building the python3-*-dbg package, but be careful
that all the reverse dependencies are also removed.

Please check for dependencies, build dependencies AND autopkg tests.
If help is needed, please ask on IRC #debian-python,
or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-djvulibre
Source-Version: 0.8.7-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated python-djvulibre package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Sep 2021 20:20:21 -0400
Source: python-djvulibre
Architecture: source
Version: 0.8.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 994350
Changes:
 python-djvulibre (0.8.7-1) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
 + Update Vcs-* fields with new Debian Python Team layout.
 + Bump debhelper compat to v13
 +  Bump Standards-Version to 4.6.0.
   * New upstream version 0.8.7.
   * debian/patches: Dropped, not needed.
   * debian/control: Drop old -dbg package. (Closes: #994350)
   * debian/tests/: Use py3versions -s instead of -i (lintian).
Checksums-Sha1:
 3461013cfb2de042a370c12a633ea245fc034a4f 2603 python-djvulibre_0.8.7-1.dsc
 8975b4c882a1fd07d29f4d71f5ee3814a21da9b7 87788 
python-djvulibre_0.8.7.orig.tar.gz
 5dee76f3b06b9137319577fa4d39a5b14dc1d895 833 
python-djvulibre_0.8.7.orig.tar.gz.asc
 01e9866152d264fa73bd04c1061674a65be1dd22 29116 
python-djvulibre_0.8.7-1.debian.tar.xz
 774f503b94e9d834ad5d76e00dbf65b2ec2d1a31 10454 
python-djvulibre_0.8.7-1_amd64.buildinfo
Checksums-Sha256:
 7d66c9d6f96d3a6ebf1e95494e9e0141d6a57f2e382f36685b70b7e4e09fedfb 2603 
python-djvulibre_0.8.7-1.dsc
 0a5490560d4b85b3b623a27dae764b42cfb527caed6dbf21e160cdb5e8ca439d 87788 
python-djvulibre_0.8.7.orig.tar.gz
 0beb6c9caf1905f3642d38c05c805af6854f753ee60f995950629a73792bcf2c 833 
python-djvulibre_0.8.7.orig.tar.gz.asc
 17118dee1a58269f7bdceade2c12161a591ceaa9f02a9d49d40887cb836fb502 29116 
python-djvulibre_0.8.7-1.debian.tar.xz
 ab0d6ebb28a09792f6567f158bb31c564b48f4269eec8b6bdef20f9519a4fb13 10454 
python-djvulibre_0.8.7-1_amd64.buildinfo
Files:
 752a39e73a9288a64302c3988753b35f 2603 python optional 
python-djvulibre_0.8.7-1.dsc
 103203a1aa18bb13338193ee7fe233a0 87788 python optional 
python-djvulibre_0.8.7.orig.tar.gz
 8071ac33fe7743820450033759d639fe 833 python optional 
python-djvulibre_0.8.7.orig.tar.gz.asc
 c371c37c709dcb6355dd421dc0296da2 29116 python optional 
python-djvulibre_0.8.7-1.debian.tar.xz
 46119fe7f6f603f0ac3e03e047f6579e 10454 python optional 
python-djvulibre_0.8.7-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFJJb8ACgkQwpPntGGC
Ws4vug//QWaeR9SJGQnkzBG++Eko+es5YCsV0+CrdOPaTOLMRsV2+g0YkMHfXc4U
PLr22B9staLkrlxG4muFsQnGCYqvBHsetFOV4tqHhWxBdGP1HjWbY7YFE30M1tnm
tIB7Vqacl8wTNkZGr8jnP+GWw3I8U8FkR6+hYXOu2gs+d+uvqobgYNrEqW4Y60rG
A3hAnZjieYuFZSvzWXxbu712Mm7aQcWwRu5mM/OiFShf67Rncrheh8RUZ3YD8SeT
sAoOYNZbHsj22gLz5kmxWX/m8eB4vBDK4mZRTqku3walhkBL4gNkpN0EDJQkZkNA
RQSi74kFjm84V0vOyc1+cU1a+bm4hlmX1eXDHmJ8W7cNG2xqQEmDbny+QQlhaudV

Bug#994795: w3-dtd-mathml: invalid redeclaration of predefined entities amp and lt yields failures with libxml2 2.9.12

[Vincent Lefevre]

Package: w3-dtd-mathml
Version: 2.0.0.0-5.1
Severity: grave
Tags: patch
Justification: renders package unusable

The incorrect amp and lt entity redefinition yields failures with
libxml2 2.9.12, which is now in Debian. This introduces a major
regression.

Here's a testcase for one of the buggy files.

$ cat test.xml

http://www.w3.org/TR/MathML2/dtd/isonum.ent;>
%ent-isonum;
]>


$ xmllint --nonet --noout --noent test.xml
error : xmlAddEntity: invalid redeclaration of predefined entity
error : xmlAddEntity: invalid redeclaration of predefined entity

The attached patch fixes this bug.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993638 about a
similar problem in the old w3c-dtd-xhtml package (no longer in Debian)
and the behavior of libxml2 2.9.12.

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

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

Versions of packages w3-dtd-mathml depends on:
ii  sgml-base  1.30
ii  xml-core   0.18+nmu1

w3-dtd-mathml recommends no packages.

Versions of packages w3-dtd-mathml suggests:
ii  docbook-mathml  1.1CR1-2.1

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Description: Fix redeclaration of predefined entities amp and lt.
 The redeclaration of these entities is invalid and libxml2 2.9.12
 checks that a redeclaration is equivalent to the predefined one.
 See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993638 about
 the same issue in w3c-dtd-xhtml and a long discussion.
Author: Vincent Lefevre 
Last-Update: 2021-09-21

Index: b/isonum.ent
===
--- a/isonum.ent
+++ b/isonum.ent
@@ -25,7 +25,7 @@
 
 -->
 
-
+
 
 
 
@@ -63,7 +63,7 @@
 
 
 
-
+
 
 
 
Index: b/xhtml-math11-f.dtd
===
--- a/xhtml-math11-f.dtd
+++ b/xhtml-math11-f.dtd
@@ -1874,8 +1874,8 @@
 
 
 
-
-
+
+
 
 
 
@@ -8393,7 +8393,7 @@
 
 -->
 
-
+
 
 
 
@@ -8431,7 +8431,7 @@
 
 
 
-
+
 
 
 

Bug#994794: booth: intermittent autopkgtest failures

[Simon McVittie]

Source: booth
Version: 1.0-237-gdd88847-2
Severity: serious
Justification: https://release.debian.org/testing/rc_policy.txt 6a
X-Debbugs-Cc: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

While looking at glib2.0 migration from unstable to testing, I noticed
that migration was blocked by the src:booth autopkgtest failing with the
proposed glib2.0 version. Looking at the logs, it seems that this autopkgtest
is "flaky" (intermittently failing): it flips between passing and failing
without changes to the list of installed packages.

For example, the test run at 2021-09-20 15:36:40 UTC in [1] failed,
but when retried with the same package-set at 2021-09-20 22:55:06 UTC, it
passed.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are going to cause extra work for people unrelated to this specific package.

If this test cannot be made sufficiently reliable to be used for CI gating,
one option is to mark it with "Restrictions: flaky" in debian/tests/control
so that its failures are not considered to be a serious regression.

Thanks,
smcv

Processed: Re: Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present

[Debian Bug Tracking System]

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

> forwarded 993441 https://bugs.kde.org/show_bug.cgi?id=441957
Bug #993441 [kleopatra] kleopatra: Creates unsafe ~/.gnupg when not already 
present
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=441957'.
> thanks
Stopping processing here.

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

Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present

[Norbert Preining]

forwarded 993441 https://bugs.kde.org/show_bug.cgi?id=441957
thanks

Reported to upstream already, but no activity by now.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#994350: marked as pending in python-djvulibre

[Boyuan Yang]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-djvulibre/-/commit/5db1cf4b09fd37d87ed16ad0a5aab08a658fe300


debian/control: Drop old -dbg package (Closes: #994350)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/994350

Processed: Bug#994350 marked as pending in python-djvulibre

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #994350 [src:python-djvulibre] python-djvulibre: Removal of the 
python3-*-dbg packages in sid/bookworm
Added tag(s) pending.

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

Bug#978813: marked as done (fswatch: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 22:20:08 +
with message-id 
and subject line Bug#978813: fixed in fswatch 1.14.0+repack-13.1
has caused the Debian Bug report #978813,
regarding fswatch: ftbfs with autoconf 2.70
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.)


-- 
978813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fswatch
Version: 1.14.0+repack-13
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/fswatch_1.14.0+repack-13_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
dh clean --with autoreconf \
--as-needed
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
rm -f fswatch/doc/fswatch.info
rm -f fswatch/doc/stamp-vti
rm -f fswatch/doc/version.texi
rm -f po/e...@boldquot.gmo
rm -f po/e...@boldquot.po
rm -f po/e...@quot.gmo
rm -f po/e...@quot.po
rm -f po/es.gmo
rm -f po/it.gmo
rm -f po/stamp-po
rm -f -r config/
rm -f -r fswatch/src/.deps
rm -f -r libfswatch/src/libfswatch/c++/.deps
rm -f -r libfswatch/src/libfswatch/c++/string/.deps
rm -f -r libfswatch/src/libfswatch/c++/windows/.deps
rm -f -r libfswatch/src/libfswatch/c/.deps
dh_auto_clean
make[1]: Leaving directory '/<>'
   dh_autoreconf_clean -O--as-needed
   dh_clean -O--as-needed
 dpkg-source -b .
dpkg-source: info: using options from 
fswatch-1.14.0+repack/debian/source/options: --tar-ignore=.gitignore
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building fswatch using existing 
./fswatch_1.14.0+repack.orig.tar.xz
dpkg-source: info: building fswatch in fswatch_1.14.0+repack-13.debian.tar.xz
dpkg-source: info: building fswatch in fswatch_1.14.0+repack-13.dsc
 debian/rules binary
dh binary --with autoreconf \
--as-needed
   dh_update_autotools_config -O--as-needed
   dh_autoreconf -O--as-needed
Creating directory config
Copying file config/config.rpath
Copying file m4/codeset.m4
Copying file m4/extern-inline.m4
Copying file m4/fcntl-o.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/intdiv0.m4
Copying file m4/intl.m4
Copying file m4/intldir.m4
Copying file m4/intmax.m4
Copying file m4/inttypes-pri.m4
Copying file m4/inttypes_h.m4
Copying file m4/lcmessage.m4
Copying file m4/lock.m4
Copying file m4/longlong.m4
Copying file m4/printf-posix.m4
Copying file m4/size_max.m4
Copying file m4/stdint_h.m4
Copying file m4/threadlib.m4
Copying file m4/uintmax_t.m4
Copying file m4/visibility.m4
Copying file m4/wchar_t.m4
Copying file m4/wint_t.m4
Copying file m4/xsize.m4
Copying file po/Makevars.template
configure.ac:37: error: AC_CONFIG_MACRO_DIR can only be used once
./lib/autoconf/general.m4:1849: AC_CONFIG_MACRO_DIR is expanded from...
configure.ac:37: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoreconf: error: aclocal failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:10: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: fswatch
Source-Version: 1.14.0+repack-13.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fswatch 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, 15 Sep 2021 

Bug#994714: ncbi-blast+: makeblastdb output dependent of endianness

[Aaron M. Ucko]

Étienne Mollier  writes:

> the pieces of the puzzle together.  Thanks for your explanation,

No problem; please feel free to ping me if there's anything else I can
clarify.

Also, sorry for the badly half-baked metadata update.

> Have a nice day,  :)

Thanks, you too!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#992068: marked as done (libhdf5-mpich-dev: please bump libmpich-dev dependency to (>= 3.3-3~))

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 21:32:08 +
with message-id 
and subject line Bug#992068: fixed in hdf5 1.10.6+repack-4+deb11u1
has caused the Debian Bug report #992068,
regarding libhdf5-mpich-dev: please bump libmpich-dev dependency to (>= 3.3-3~)
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.)


-- 
992068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhdf5-mpich-dev
Version: 1.10.6+repack-4
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts

During an piuparts upgrade test of libhdf5-mpich-dev on the upgrade path
  squeeze -> wheezy -> jessie -> stretch -> buster -> bullseye
I observed this failure:

  Setting up libhdf5-mpich-dev (1.10.6+repack-4) ...
  update-alternatives: priority must be an integer

  Use 'update-alternatives --help' for program usage information.
  dpkg: error processing package libhdf5-mpich-dev (--configure):
   installed libhdf5-mpich-dev package post-installation script subprocess 
returned error exit status 2

At the time of the failure the libmpich1.0-dev package which
  Provides: libmpich-dev 
was still installed, but that uses an ancient mpi alternative scheme
the postinst cannot parse.
Making the libmpich-dev versioned (buster shipped with 3.3-3 which uses
the new alternatives scheme) ensures that libmpich-dev gets upgraded
(or rather installed, kicking out the ancient libmpich1.0-dev from
squeeze).

This fix needs to get backported to bullseye-pu.

This needs an update of mpich as well, since there is an unhandled
file conflict between libmpich1.0-dev and mpich, #992065.

I've verified that using the two updated packages fixes the problematic
upgrade path.

Andreas

PS: it took me quite some time to understand what was going on here
so the fix wasn't ready before the bullseye deadline.
diff -Nru hdf5-1.10.6+repack/debian/changelog 
hdf5-1.10.6+repack/debian/changelog
--- hdf5-1.10.6+repack/debian/changelog 2021-06-16 23:57:23.0 +0200
+++ hdf5-1.10.6+repack/debian/changelog 2021-08-10 16:54:23.0 +0200
@@ -1,3 +1,10 @@
+hdf5 (1.10.6+repack-5) UNRELEASED; urgency=medium
+
+  * libhdf5-mpich-dev: Bump libmpich-dev dependency to (>= 3.3-3~) to ensure
+the postinst is able to parse the mpi alternative.  (Closes: #-1)
+
+ -- Andreas Beckmann   Tue, 10 Aug 2021 16:54:23 +0200
+
 hdf5 (1.10.6+repack-4) unstable; urgency=medium
 
   * Revert support for read-only S3 virtual file driver, as it introduced
diff -Nru hdf5-1.10.6+repack/debian/control hdf5-1.10.6+repack/debian/control
--- hdf5-1.10.6+repack/debian/control   2021-06-16 23:57:23.0 +0200
+++ hdf5-1.10.6+repack/debian/control   2021-08-10 16:54:23.0 +0200
@@ -480,7 +480,7 @@
  zlib1g-dev,
  libaec-dev,
  libjpeg-dev,
- libmpich-dev,
+ libmpich-dev (>= 3.3-3~),
  ${misc:Depends}
 Suggests: libhdf5-doc
 Breaks: libhdf5-mpi-dev (= 1.10.6+repack-1~exp4)
diff -Nru hdf5-1.10.6+repack/debian/control.in 
hdf5-1.10.6+repack/debian/control.in
--- hdf5-1.10.6+repack/debian/control.in2021-06-16 23:57:23.0 
+0200
+++ hdf5-1.10.6+repack/debian/control.in2021-08-10 16:54:23.0 
+0200
@@ -480,7 +480,7 @@
  zlib1g-dev,
  libaec-dev,
  libjpeg-dev,
- libmpich-dev,
+ libmpich-dev (>= 3.3-3~),
  ${misc:Depends}
 Suggests: libhdf5-doc
 Breaks: libhdf5-mpi-dev (= 1.10.6+repack-1~exp4)


libhdf5-mpich-dev_1.10.6+repack-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.10.6+repack-4+deb11u1
Done: Gilles Filippini 

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated hdf5 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: Sun, 15 Aug 2021 15:56:44 +0200
Source: hdf5
Architecture: source
Version: 1.10.6+repack-4+deb11u1
Distribution: bullseye
Urgency: 

Bug#994790: hcxtools: CVE-2021-32286

[Moritz Mühlenhoff]

Source: hcxtools
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for hcxtools.

CVE-2021-32286[0]:
| An issue was discovered in hcxtools through 6.1.6. A global-buffer-
| overflow exists in the function pcapngoptionwalk located in
| hcxpcapngtool.c. It allows an attacker to cause code Execution.

https://github.com/ZerBea/hcxtools/issues/155
https://github.com/ZerBea/hcxtools/commit/e6505ddc262bc3254b39844895ebac70861001d2

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

Please adjust the affected versions in the BTS as needed.

Processed: tagging 994545

[Debian Bug Tracking System]

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

> tags 994545 + sid bookworm
Bug #994545 [src:lumino] FTBFS: can't build lumino with current typescript stack
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#994713: closing 994713

[Jochen Sprickerhof]

close 994713 6.8.0+ds-3
thanks

Processed: closing 994713

[Debian Bug Tracking System]

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

> close 994713 6.8.0+ds-3
Bug #994713 {Done: Jose Luis Rivero } 
[src:ignition-math] ignition-math: FTBFS on arm64, ppc64el, s390x
Marked as fixed in versions ignition-math/6.8.0+ds-3.
Bug #994713 {Done: Jose Luis Rivero } 
[src:ignition-math] ignition-math: FTBFS on arm64, ppc64el, s390x
Bug 994713 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: reassign to kleborate the ftbfs on s390x

[Debian Bug Tracking System]

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

> # huh, i thought it was reassigned already?  anyways...
> reassign 994714 kleborate 2.1.0-1
Bug #994714 [ncbi-blast+] kleborate: ftbfs on s390x due to architecture 
dependent blastdbv5
Bug reassigned from package 'ncbi-blast+' to 'kleborate'.
No longer marked as found in versions ncbi-blast+/2.11.0+ds-1.
Ignoring request to alter fixed versions of bug #994714 to the same values 
previously set
Bug #994714 [kleborate] kleborate: ftbfs on s390x due to architecture dependent 
blastdbv5
Marked as found in versions kleborate/2.1.0-1.
> thank you
Stopping processing here.

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

Processed: tagging 994672, tagging 994673, tagging 994677

[Debian Bug Tracking System]

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

> tags 994672 + sid bookworm
Bug #994672 [src:open-isns] open-isns FTBFS: error: ‘sigrelse’ is deprecated
Added tag(s) sid and bookworm.
> tags 994673 + sid bookworm
Bug #994673 [src:slcfitsio] slcfitsio FTBFS: error: too many decimal points in 
number
Added tag(s) bookworm and sid.
> tags 994677 + sid bookworm
Bug #994677 [src:ladvd] ladvd FTBFS: error: ‘MAXPATHLEN’ undeclared
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: apt-clone: diff for NMU version 0.4.3+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 981758 + patch
Bug #981758 [src:apt-clone] apt-clone: autopkgtest failure on i386
Added tag(s) patch.
> tags 981758 + pending
Bug #981758 [src:apt-clone] apt-clone: autopkgtest failure on i386
Added tag(s) pending.

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

Bug#981758: apt-clone: diff for NMU version 0.4.3+nmu1

[Boyuan Yang]

Control: tags 981758 + patch
Control: tags 981758 + pending

Dear maintainer,

I've prepared an NMU for apt-clone (versioned as 0.4.3+nmu1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru apt-clone-0.4.3/debian/changelog apt-clone-
0.4.3+nmu1/debian/changelog
--- apt-clone-0.4.3/debian/changelog2020-11-06 02:17:14.0 -0500
+++ apt-clone-0.4.3+nmu1/debian/changelog   2021-09-20 16:21:48.0
-0400
@@ -1,3 +1,22 @@
+apt-clone (0.4.3+nmu1) unstable; urgency=high
+
+  * Non-maintainer upload.
+
+  [ Michael Vogt ]
+  * tests: skip clone/upgrade test on i386. (Closes: #981758)
+The i386 architecture is not fully supported anymore on Ubuntu
+so testing the upgrade with that will lead to issues.
+
+  [ Shirocco88 ]
+  * README.md: fix a typo.
+
+  [ Lucas Kanashiro ]
+  * d/t/control: depend on ubuntu-keyring instead of ubuntu-archive-keyring.
+ubuntu-archive-keyring is a transitional package in Debian and
+no longer exists in Ubuntu.
+
+ -- Boyuan Yang   Mon, 20 Sep 2021 16:21:48 -0400
+
 apt-clone (0.4.3) unstable; urgency=medium
 
   * debian: update test dependencies
diff -Nru apt-clone-0.4.3/debian/tests/control apt-clone-
0.4.3+nmu1/debian/tests/control
--- apt-clone-0.4.3/debian/tests/control2020-11-06 02:17:14.0
-0500
+++ apt-clone-0.4.3+nmu1/debian/tests/control   2021-09-20 16:21:48.0
-0400
@@ -1,2 +1,2 @@
 Tests: run-tests
-Depends: @, pyflakes3, python3-apt, pycodestyle, python3-mock, python3-
distro-info, make, ubuntu-archive-keyring
+Depends: @, pyflakes3, python3-apt, pycodestyle, python3-mock, python3-
distro-info, make, ubuntu-keyring
diff -Nru apt-clone-0.4.3/README.md apt-clone-0.4.3+nmu1/README.md
--- apt-clone-0.4.3/README.md   2020-11-06 02:17:14.0 -0500
+++ apt-clone-0.4.3+nmu1/README.md  2021-09-20 16:21:48.0 -0400
@@ -35,7 +35,7 @@
 `
 $ sudo apt-clone restore ~/myhost.apt-clone.tar.gz
 `
-Note that you can give the option `--destination /some/dir` and it wil
debootstrap the clone into this directory.
+Note that you can give the option `--destination /some/dir` and it will
debootstrap the clone into this directory.
 
 [travis-image]: https://travis-ci.org/mvo5/apt-clone.svg?branch=master
 [travis-url]: https://travis-ci.org/mvo5/apt-clone
diff -Nru apt-clone-0.4.3/tests/test_clone_upgrade.py apt-clone-
0.4.3+nmu1/tests/test_clone_upgrade.py
--- apt-clone-0.4.3/tests/test_clone_upgrade.py 2020-11-06 02:17:14.0
-0500
+++ apt-clone-0.4.3+nmu1/tests/test_clone_upgrade.py2021-09-20
16:21:48.0 -0400
@@ -20,6 +20,11 @@
 
 class TestCloneUpgrade(unittest.TestCase):
 
+def setUp(self):
+arch = apt_pkg.config.find("APT::Architecture")
+if arch in ["i386"]:
+self.skipTest("architecutre no longer fully supported in ubuntu")
+
 @unittest.skip("need to update apt-clone-state-ubuntu.tar.gz first")
 def test_clone_upgrade_regression(self):
 """ regression test against known installs """


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

Bug#994786: spectral-cube: autopkgtest needs update for new version of radio-beam: warning message changed

[Paul Gevers]

Source: spectral-cube
Version: 0.5.0-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, radio-b...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:radio-beam

Dear maintainer(s),

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

   passfail
radio-beam from testing0.3.3-1
spectral-cube  from testing0.5.0-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems to me
that there was an *addition* warning raised and thus the check fails.

Currently this regression is blocking the migration of radio-beam to
testing [1]. Of course, radio-beam shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
radio-beam was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from radio-beam should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
radio-beam/0.3.3-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=radio-beam

https://ci.debian.net/data/autopkgtest/testing/amd64/s/spectral-cube/15365768/log.gz

=== FAILURES
===
___ test_parallel_bad_params
___

data_adv =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_parallel_bad_params0/adv.fits')

@pytest.mark.skipif('not scipyOK')
def test_parallel_bad_params(data_adv):

# This function only makes sense for the plain SpectralCube class

cube, data = cube_and_raw(data_adv, use_dask=False)

with pytest.raises(ValueError,
   match=("parallel execution was not requested,
but "
  "multiple cores were: these are
incompatible "
  "options.  Either specify num_cores=1 or "
  "parallel=True")):
cube.spectral_smooth_median(3, num_cores=2, parallel=False,
update_function=update_function)

with warnings.catch_warnings(record=True) as wrn:
cube.spectral_smooth_median(3, num_cores=1, parallel=True,
update_function=update_function)

>   assert ("parallel=True was specified but num_cores=1. "
"Joblib will be used to run the task with a "
"single thread.") in str(wrn[-1].message)
E   assert 'parallel=True was specified but num_cores=1. Joblib will
be used to run the task with a single thread.' in "'datfix' made the
change 'Set MJD-OBS to 50982.687794 from DATE-OBS'."
E+  where "'datfix' made the change 'Set MJD-OBS to 50982.687794
from DATE-OBS'." = str(FITSFixedWarning("'datfix' made the change 'Set
MJD-OBS to 50982.687794 from DATE-OBS'."))
E+where FITSFixedWarning("'datfix' made the change 'Set
MJD-OBS to 50982.687794 from DATE-OBS'.") = .message

/usr/lib/python3/dist-packages/spectral_cube/tests/test_spectral_cube.py:2279:
AssertionError



OpenPGP_signature
Description: OpenPGP digital signature

Processed: spectral-cube: autopkgtest needs update for new version of radio-beam: warning message changed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:radio-beam
Bug #994786 [src:spectral-cube] spectral-cube: autopkgtest needs update for new 
version of radio-beam: warning message changed
Added indication that 994786 affects src:radio-beam

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

Bug#994785: python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface

[Paul Gevers]

Source: python-ase
Version: 3.22.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
python-ase from testing3.22.0-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 to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
python-ase/3.22.0-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=python-ase

https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-ase/15401492/log.gz

=== FAILURES
===
__ TestSlab.test_vibration_on_surface
__

self = 
testdir =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_vibration_on_surface0')

def test_vibration_on_surface(self, testdir):
from ase.build import fcc111, add_adsorbate
ag_slab = fcc111('Ag', (4, 4, 2), a=2)
n2 = Atoms('N2', positions=[[0., 0., 0.],
[0., np.sqrt(2), np.sqrt(2)]])
add_adsorbate(ag_slab, n2, height=1, position='fcc')

# Add an interaction between the N atoms
hessian_bottom_corner = np.zeros((2, 3, 2, 3))
hessian_bottom_corner[-1, :, -2] = [1, 1, 1]
hessian_bottom_corner[-2, :, -1] = [1, 1, 1]

hessian = np.zeros((34, 3, 34, 3))
hessian[32:, :, 32:, :] = hessian_bottom_corner

ag_slab.calc = ForceConstantCalculator(hessian.reshape((34 * 3,
34 * 3)),
   ref=ag_slab.copy(),
   f0=np.zeros((34, 3)))

# Check that Vibrations with restricted indices returns correct
Hessian
vibs = Vibrations(ag_slab, indices=[-2, -1])
vibs.run()
vibs.read()

assert_array_almost_equal(vibs.get_vibrations().get_hessian(),
  hessian_bottom_corner)

# These should blow up if the vectors don't match number of atoms
vibs.summary()
vibs.write_jmol()

for i in range(6):
# Frozen atoms should have zero displacement
assert_array_almost_equal(vibs.get_mode(i)[0], [0., 0., 0.])

# The N atoms should have finite displacement
>   assert np.all(vibs.get_mode(i)[-2:, :])
E   assert False
E+  where False = (array([[
0.e+00, -2.21811191e-17,  2.25296944e-17],\n
[-1.88935009e-01,  1.88935009e-01,  1.69152862e-18]]))
E+where  = np.all

/usr/lib/python3/dist-packages/ase/test/vibrations/test_vib.py:527:
AssertionError
- Captured stdout call
-
-
  #meV cm^-1
-
  0   29.9i241.3i
  10.0   0.0
  20.0   0.0
  30.0   0.0
  40.0   0.0
  5   29.9 241.3
-
Zero-point energy: 0.015 eV
--- Captured stdout teardown
---
Testdir: /tmp/pytest-of-debci/pytest-0/test_vibration_on_surface0
Global seed for "test/vibrations/test_vib.py:test_vibration_on_surface"
was: 16



OpenPGP_signature
Description: OpenPGP digital signature

Bug#994784: mpi4py breaks gyoto autopkgtest on i386: 1 process returned, a non-zero exit code

[Paul Gevers]

Source: mpi4py, gyoto
Control: found -1 mpi4py/3.0.3-10
Control: found -1 gyoto/1.4.4-3
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 mpi4py the autopkgtest of gyoto fails in testing
when that autopkgtest is run with the binary packages of mpi4py from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
mpi4py from testing3.0.3-10
gyoto  from testing1.4.4-3
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of mpi4py 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

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
mpi4py/3.0.3-10. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=mpi4py

https://ci.debian.net/data/autopkgtest/testing/i386/g/gyoto/15316145/log.gz

Reading parameter file:
/tmp/autopkgtest-lxc.8uv_qvhr/downtmp/build.nbg/src/doc/examples/example-startrace.xml
 Copyright (c) 2011-2019 Frédéric Vincent, Thibaut Paumard,
 Odele Straub and Frédéric Lamy.
 GYOTO is distributed under the terms of the GPL v. 3 license.
 We request that use of Gyoto in scientific publications be  properly
 acknowledged. Please cite:
  GYOTO: a new general relativistic ray-tracing code,
  F. H. Vincent, T. Paumard, E. Gourgoulhon & G. Perrin 2011,
  Classical and Quantum Gravity 28, 225011 (2011) [arXiv:1109.4769]

j =
1/32--
Child job 2 terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--
--
mpirun.openmpi noticed that process rank 1 with PID 0 on node
ci-262-d8ad913b exited on signal 9 (Killed).
--



OpenPGP_signature
Description: OpenPGP digital signature

Processed: mpi4py breaks gyoto autopkgtest on i386: 1 process returned, a non-zero exit code

[Debian Bug Tracking System]

Processing control commands:

> found -1 mpi4py/3.0.3-10
Bug #994784 [src:mpi4py, src:gyoto] mpi4py breaks gyoto autopkgtest on i386: 1 
process returned, a non-zero exit code
Marked as found in versions mpi4py/3.0.3-10.
> found -1 gyoto/1.4.4-3
Bug #994784 [src:mpi4py, src:gyoto] mpi4py breaks gyoto autopkgtest on i386: 1 
process returned, a non-zero exit code
Marked as found in versions gyoto/1.4.4-3.

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

Bug#993187: gnome-shell-extension-hide-activities: does not declare compatibility with GNOME Shell 40

[Sven Geuer]

Please consider to switch upstream from
https://github.com/shayelkin/gnome-hide-activities to
https://github.com/nmingori/gnome-hide-actitivies-button.

Cheers,
Sven
-- 
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585


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

Processed: adjust metadata following reassigning to kleborate

[Debian Bug Tracking System]

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

> retitle  994714 kleborate: ftbfs on s390x due to architecture dependent 
> blastdbv5
Bug #994714 [ncbi-blast+] ncbi-blast+: makeblastdb output dependent of 
endianness
Changed Bug title to 'kleborate: ftbfs on s390x due to architecture dependent 
blastdbv5' from 'ncbi-blast+: makeblastdb output dependent of endianness'.
> severity 994714 serious
Bug #994714 [ncbi-blast+] kleborate: ftbfs on s390x due to architecture 
dependent blastdbv5
Severity set to 'serious' from 'important'
> thank you
Stopping processing here.

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

Processed: astropy-regions breaks gammapy autopkgtest: KeyError: '.'

[Debian Bug Tracking System]

Processing control commands:

> found -1 astropy-regions/0.5-1
Bug #994783 [src:astropy-regions, src:gammapy] astropy-regions breaks gammapy 
autopkgtest: KeyError: '.'
Marked as found in versions astropy-regions/0.5-1.
> found -1 gammapy/0.18.2-1
Bug #994783 [src:astropy-regions, src:gammapy] astropy-regions breaks gammapy 
autopkgtest: KeyError: '.'
Marked as found in versions gammapy/0.18.2-1.

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

Bug#994783: astropy-regions breaks gammapy autopkgtest: KeyError: '.'

[Paul Gevers]

Source: astropy-regions, gammapy
Control: found -1 astropy-regions/0.5-1
Control: found -1 gammapy/0.18.2-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 astropy-regions the autopkgtest of gammapy fails
in testing when that autopkgtest is run with the binary packages of
astropy-regions from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
astropy-regionsfrom testing0.5-1
gammapyfrom testing0.18.2-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 astropy-regions
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=astropy-regions

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gammapy/15348901/log.gz

=== FAILURES
===
___ test_edispkernel_from_diagonal_response


def test_edispkernel_from_diagonal_response():
energy_axis_true = MapAxis.from_energy_bounds(
"0.3 TeV", "10 TeV", nbin=11, name="energy_true"
)
energy_axis = MapAxis.from_energy_bounds(
"0.3 TeV", "10 TeV", nbin=11, name="energy"
)

>   region = make_region("fk5;circle(0.,0., 10.")

/usr/lib/python3/dist-packages/gammapy/irf/tests/test_edisp_map.py:244:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/gammapy/utils/regions.py:83: in make_region
return DS9Parser(region).shapes[0].to_region()
/usr/lib/python3/dist-packages/astropy/utils/decorators.py:124: in
deprecated_func
return func(*args, **kwargs)
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:194: in __init__
self.run()
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:223: in run
self.parse_line(line)
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:268: in parse_line
self.parse_region(include, region_type, region_end, line)
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:333: in parse_region
helper.parse()
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:436: in parse
self.convert_coordinates()
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:482: in
convert_coordinates
coord_list.append(element_parser(element))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

string_rep = '10.', unit = Unit("deg")

@staticmethod
def parse_angular_length_quantity(string_rep, unit=u.deg):
"""
Parse a string into a Quantity object.

Given a string that is a number and a unit, return a Quantity of
that string, e.g.:

* 23.9 -> 23.9 * u.deg
* 50" -> 50 * u.arcsec
"""
unit_mapping = {'"': u.arcsec,
"'": u.arcmin,
'd': u.deg,
'r': u.rad,
'i': u.dimensionless_unscaled,
'p': u.dimensionless_unscaled}
has_unit = string_rep[-1] not in string.digits
if has_unit:
>   unit = unit_mapping[string_rep[-1]]
E   KeyError: '.'

/usr/lib/python3/dist-packages/regions/io/ds9/read.py:136: KeyError
___ test_edispkernel_from_1D
___

def test_edispkernel_from_1D():
energy_axis_true = MapAxis.from_energy_bounds(
"0.5 TeV", "5 TeV", nbin=31, name="energy_true"
)
energy_axis = MapAxis.from_energy_bounds(
"0.1 TeV", "10 TeV", nbin=11, name="energy"
)

edisp = EDispKernel.from_gauss(energy_axis_true.edges,
energy_axis.edges, 0.1, 0.0)
>   region = make_region("fk5;circle(0.,0., 10.")

/usr/lib/python3/dist-packages/gammapy/irf/tests/test_edisp_map.py:265:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/gammapy/utils/regions.py:83: in make_region
return DS9Parser(region).shapes[0].to_region()
/usr/lib/python3/dist-packages/astropy/utils/decorators.py:124: in
deprecated_func
return func(*args, **kwargs)
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:194: in __init__
self.run()
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:223: in run
self.parse_line(line)
/usr/lib/python3/dist-packages/regions/io/ds9/read.py:268: in parse_line
self.parse_region(include, region_type, region_end, line)

Processed: Re: Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present

[Debian Bug Tracking System]

Processing control commands:

> found -1 4:20.08.3-1
Bug #993441 [kleopatra] kleopatra: Creates unsafe ~/.gnupg when not already 
present
Marked as found in versions kleopatra/4:20.08.3-1.

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

Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present

[Sebastian Ramacher]

Control: found -1 4:20.08.3-1

On 2021-09-07 14:27:28 +0200, Diederik de Haas wrote:
> On dinsdag 7 september 2021 11:32:28 CEST Peter Green wrote:
> >  > Version: 4:21.08.0-1
> > 
> > You filed this against the version in sid? 
> 
> I run Sid as my daily driver, so yes. That's what I (almost?) always do.
> 
> > have you investigated whether earlier versions are also affected?
> 
> No, I did not.

This issue can also be observed in bullseye.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#994775: flowblade: No module name 'mlt'

[Gürkan Myczko]

solution is here:

https://github.com/jliljebl/flowblade/issues/1016

sorry for the issue will try to fix


> On 20 Sep 2021, at 21:03, Alexandre Lymberopoulos  wrote:
> 
> Package: flowblade
> Version: 2.8.0.3-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> When I tried to open flowblade from terminal in my XFCE session I get the 
> following:
> 
> FLOWBLADE MOVIE EDITOR 2.8
> --
> Launch script dir: /usr/bin
> Running from installation...
> modules path: /usr/share/flowblade/Flowblade
> MLT not found, exiting...
> ERROR: No module named 'mlt'
> 
> But it seems that all the dependencies are installed here. I may provide any 
> further information upon request and guidance.
> 
> Thanks in advance and best regards, Alexandre
> 
> -- System Information:
> Debian Release: bookworm/sid
>  APT prefers testing
>  APT policy: (900, 'testing'), (800, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-8-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages flowblade depends on:
> ii  frei0r-plugins1.7.0-1
> ii  gir1.2-gdkpixbuf-2.0  2.42.6+dfsg-2
> ii  gir1.2-glib-2.0   1.68.0-2
> ii  gir1.2-gtk-3.03.24.30-3
> ii  gir1.2-pango-1.0  1.48.9+ds1-2
> ii  gmic  2.9.4-4
> ii  libmlt-data   7.0.1-3
> ii  librsvg2-common   2.50.3+dfsg-1
> ii  python3   3.9.2-3
> ii  python3-cairo 1.16.2-4+b2
> ii  python3-dbus  1.2.18-2
> ii  python3-distutils 3.9.7-1
> ii  python3-gi3.40.1-2
> ii  python3-gi-cairo  3.40.1-2
> ii  python3-mlt   7.0.1-3
> ii  python3-numpy 1:1.19.5-1
> ii  python3-opencv4.5.3+dfsg-1+b1
> ii  python3-pil   8.1.2+dfsg-0.3
> ii  swh-plugins   0.4.17-2
> 
> flowblade recommends no packages.
> 
> flowblade suggests no packages.
> 
> -- no debconf information
> 

Processed: src:paperwork: fails to migrate to testing for too long: RC bug (autopkgtest failure)

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.0.2-3
Bug #994777 [src:paperwork] src:paperwork: fails to migrate to testing for too 
long: RC bug (autopkgtest failure)
Marked as fixed in versions paperwork/2.0.2-3.
Bug #994777 [src:paperwork] src:paperwork: fails to migrate to testing for too 
long: RC bug (autopkgtest failure)
Marked Bug as done

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

Bug#994777: src:paperwork: fails to migrate to testing for too long: RC bug (autopkgtest failure)

[Paul Gevers]

Source: paperwork
Version: 1.3.1-3
Severity: serious
Control: close -1 2.0.2-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:paperwork has been trying to migrate for
211 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=paperwork




OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 994727 is important

[Debian Bug Tracking System]

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

> severity 994727 important
Bug #994727 [src:linux] reportbug: Hang at boot (pre-X) with [drm] CPU Pipe A 
FIFO underrun [workaround included]
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#994775: flowblade: No module name 'mlt'

[Alexandre Lymberopoulos]

Package: flowblade
Version: 2.8.0.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I tried to open flowblade from terminal in my XFCE session I get the 
following:

FLOWBLADE MOVIE EDITOR 2.8
--
Launch script dir: /usr/bin
Running from installation...
modules path: /usr/share/flowblade/Flowblade
MLT not found, exiting...
ERROR: No module named 'mlt'

But it seems that all the dependencies are installed here. I may provide any 
further information upon request and guidance.

Thanks in advance and best regards, Alexandre

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

Kernel: Linux 5.10.0-8-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flowblade depends on:
ii  frei0r-plugins1.7.0-1
ii  gir1.2-gdkpixbuf-2.0  2.42.6+dfsg-2
ii  gir1.2-glib-2.0   1.68.0-2
ii  gir1.2-gtk-3.03.24.30-3
ii  gir1.2-pango-1.0  1.48.9+ds1-2
ii  gmic  2.9.4-4
ii  libmlt-data   7.0.1-3
ii  librsvg2-common   2.50.3+dfsg-1
ii  python3   3.9.2-3
ii  python3-cairo 1.16.2-4+b2
ii  python3-dbus  1.2.18-2
ii  python3-distutils 3.9.7-1
ii  python3-gi3.40.1-2
ii  python3-gi-cairo  3.40.1-2
ii  python3-mlt   7.0.1-3
ii  python3-numpy 1:1.19.5-1
ii  python3-opencv4.5.3+dfsg-1+b1
ii  python3-pil   8.1.2+dfsg-0.3
ii  swh-plugins   0.4.17-2

flowblade recommends no packages.

flowblade suggests no packages.

-- no debconf information

Bug#994453: Kernel 5.14 does not boot Lenovo Thinkpad E595 (Ryzen 7 3700U)

[jmho]

Dear maintainers,

I might be hitting the same problem, but I can see the kernel panic 
message:


First a couple of lines saying:

"AMD-Vi: Completion-Wait loop timed out"

then:

"Kernel panic - not syncing: timer does't work through 
Interrupt-remapped IO-APIC"


I was experiencing this also with the 5.14.0-trunk kernel and the 5.13 
before from experimental.


I updated the Lenovo BIOS to the current version but the problem 
persists. Also, booting with "amd_iommu=off" did not help.


Do you need more information? Unfortunately this did not make it to the 
system logs.


kind regards,
Jens-Michael

Bug#978893: ripperx: ftbfs with autoconf 2.70

[Adrian Bunk]

On Mon, Sep 20, 2021 at 08:21:27PM +0300, Adrian Bunk wrote:
> On Mon, Sep 06, 2021 at 12:57:10AM +0100, Simon McVittie wrote:
> > On Thu, 31 Dec 2020 at 14:28:53 +, Matthias Klose wrote:
> > > The package fails to build in a test rebuild on at least amd64 with
> > > autoconf 2.70, but succeeds to build with autoconf 2.69.
> > ...
> > > The full build log can be found at:
> > > http://qa-logs.debian.net/2020/09/26.ac270/ripperx_2.8.0-2_unstable_ac270.log
> > > The last lines of the build log are at the end of this report.
> > 
> > I don't think those lines indicate the actual error, which looks like a C++
> > compiler problem (perhaps because the new Autoconf version passes options
> > that make the compiler more strict?):
> >...
> > This new error might be an Autoconf bug: the second check (with -lutil)
> > looks like it's missing an extern "C" on the prototype. If so,
> > http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=b27bc3e230bb12fdd9a813e38e82bc4c3e22b4cc
> > might help.
> 
> This commit is not sufficient, and the root cause is that 
> AC_PROG_CC([g++]) is documented to be no longer supported:
>   https://sources.debian.org/src/autoconf/2.71-2/NEWS/#L90

The problem is that ripperx is giving C++ sources a .c file extension.

The correct fix is:
  AC_PROG_CC([g++]) -> AC_PROG_CC

And then rename all C++ files
  foo.c -> foo.cc
with corresponding changes in Makefile.am.

This results in  automake automatically choosing the C++ compiler,
without any need to pretend it was a C compiler.

> cu
> Adrian

cu
Adrian

Bug#978893: ripperx: ftbfs with autoconf 2.70

[Adrian Bunk]

On Mon, Sep 06, 2021 at 12:57:10AM +0100, Simon McVittie wrote:
> On Thu, 31 Dec 2020 at 14:28:53 +, Matthias Klose wrote:
> > The package fails to build in a test rebuild on at least amd64 with
> > autoconf 2.70, but succeeds to build with autoconf 2.69.
> ...
> > The full build log can be found at:
> > http://qa-logs.debian.net/2020/09/26.ac270/ripperx_2.8.0-2_unstable_ac270.log
> > The last lines of the build log are at the end of this report.
> 
> I don't think those lines indicate the actual error, which looks like a C++
> compiler problem (perhaps because the new Autoconf version passes options
> that make the compiler more strict?):
>...
> This new error might be an Autoconf bug: the second check (with -lutil)
> looks like it's missing an extern "C" on the prototype. If so,
> http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=b27bc3e230bb12fdd9a813e38e82bc4c3e22b4cc
> might help.

This commit is not sufficient, and the root cause is that 
AC_PROG_CC([g++]) is documented to be no longer supported:
  https://sources.debian.org/src/autoconf/2.71-2/NEWS/#L90

> smcv

cu
Adrian

Bug#964654:

[Kaily Salmon]

Processed: Re: Bug#994758: libsgutils2-2: how to prevent the share lib from changing version to impact the package?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #994758 [libsgutils2-2] libsgutils2-2: how to prevent the share lib from 
changing version to impact the package?
Severity set to 'critical' from 'wishlist'
> retitle -1 Soname change without package name change
Bug #994758 [libsgutils2-2] libsgutils2-2: how to prevent the share lib from 
changing version to impact the package?
Changed Bug title to 'Soname change without package name change' from 
'libsgutils2-2: how to prevent the share lib from changing version to impact 
the package?'.
> found -1 1.45-1
Bug #994758 [libsgutils2-2] Soname change without package name change
Marked as found in versions sg3-utils/1.45-1.
> block 994521 by -1
Bug #994521 [ledmon] ledmon: libsgutils2-2 1.46 update breaks ledmon
994521 was not blocked by any bugs.
994521 was not blocking any bugs.
Added blocking bug(s) of 994521: 994758

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

Processed: closing 994439

[Debian Bug Tracking System]

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

> close 994439
Bug #994439 [dovecot-core] dovecot-core: SMTP auth failure on localhost [::1]
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#994439: closing 994439

[Noah Meyerhans]

close 994439 
thanks

resolving per submitter request

Processed: closing 994439

[Debian Bug Tracking System]

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

> close 994439
Bug #994439 {Done: Noah Meyerhans } [dovecot-core] 
dovecot-core: SMTP auth failure on localhost [::1]
Bug 994439 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: Re: Bug#993638: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:macaulay2
Bug #993638 {Done: Mattia Rizzolo } [libxml2] libxml2: 
XHTML 1.0 validation is broken with w3c-dtd-xhtml's xhtml-special.ent file
Removed indication that 993638 affects src:macaulay2

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

Bug#993638: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Torrance, Douglas]

Control: affects -1 - src:macaulay2

On Mon 20 Sep 2021 11:41:39 AM EDT, Vincent Lefevre  wrote:

On 2021-09-20 15:00:00 +, Torrance, Douglas wrote:

On Mon 20 Sep 2021 08:17:11 AM EDT, Vincent Lefevre  wrote:
> The error message is different. I'd say that this is a different issue.

Fair enough.  I think it's related -- the latest release is more strict about
DTD files --


Yes, but there seem to be many changes, thus potentially several kinds
of regressions for different reasons. It is better to report one bug
per kind of regression.


That makes sense -- I'll open a new bug.


but involving a different DTD file, xhtml-math-svg.dtd from the
w3c-sgml-lib package. Here's the output of xmllint, which gives a
bit more info:

$  xmllint --noout --loaddtd
/usr/share/doc/Macaulay2/Macaulay2Doc/html/_ideal.html 
file:///usr/share/xml/w3c-sgml-lib/schema/dtd/WD-XHTMLplusMathMLplusSVG-20020809/xhtml-math-svg.dtd:338:
parser error : xmlParseEntityDecl: entity xhtml-qname-extra.mod not
terminated
   %xhtml-qname-extra.decl;
   ^
Entity: line 2:
"http://www.w3.org/Math/DTD/mathml2/mathml2-qname-1.mod;
   ^
Perhaps this should be filed against w3c-sgml-lib?


I don't know about this one. It could be a bug either in libxml2
(e.g. an unexpected regression in a corner case due to some fix
of a more general case) or in the DTD from w3c-sgml-lib. Some
investigation would be needed.


I guess I'll start by filing it against libxml2 like this bug, and it can always
be re-assigned later if necessary.


signature.asc
Description: PGP signature

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Thorsten Glaser]

On Mon, 20 Sep 2021, Vincent Lefevre wrote:

> For the 1.1 DTD, w3c-dtd-xhtml 1.1-5 had the *upstream* file
> xhtml-1.1/basic/xhtml-special.ent with the buggy entity definitions

Hmm, now where did t̲h̲a̲t̲ come from?

http://www.w3.org/TR/2001/REC-xhtml11-20010531/xhtml11.tgz
has the flattened DTD.

Apparently XHTML™ Basic 1.1 is a thing, though. This is not XHTML 1.1…
http://www.w3.org/TR/2010/REC-xhtml-basic-20101123/xhtml-basic.tgz does
not contain the entities at all though.

Hah, got it! XHTML™ Basic 1.0 does contain the bogus file:
http://www.w3.org/TR/2000/REC-xhtml-basic-20001219/xhtml-basic.tgz
Its list of errata is empty, so this is not listed upstream as known bug.

> > But if this upstream change affects DTDs that were once released, maybe
> > it should accept, but ignore, this specific wrong redeclaration.
> 
> Perhaps. This should probably be first talked with upstream.

So indeed. Can one of you bring this to them? (My contributions to
libxml2 don’t appear to be liked, even if multiple CVEs could have
been avoided by applying them.)

Thanks,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against  Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!

Bug#993638: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Vincent Lefevre]

On 2021-09-20 15:00:00 +, Torrance, Douglas wrote:
> On Mon 20 Sep 2021 08:17:11 AM EDT, Vincent Lefevre  
> wrote:
> > The error message is different. I'd say that this is a different issue.
> 
> Fair enough.  I think it's related -- the latest release is more strict about
> DTD files --

Yes, but there seem to be many changes, thus potentially several kinds
of regressions for different reasons. It is better to report one bug
per kind of regression.

> but involving a different DTD file, xhtml-math-svg.dtd from the
> w3c-sgml-lib package. Here's the output of xmllint, which gives a
> bit more info:
> 
> $  xmllint --noout --loaddtd
> /usr/share/doc/Macaulay2/Macaulay2Doc/html/_ideal.html 
> file:///usr/share/xml/w3c-sgml-lib/schema/dtd/WD-XHTMLplusMathMLplusSVG-20020809/xhtml-math-svg.dtd:338:
> parser error : xmlParseEntityDecl: entity xhtml-qname-extra.mod not
> terminated
>%xhtml-qname-extra.decl;
>^
> Entity: line 2:
> "http://www.w3.org/Math/DTD/mathml2/mathml2-qname-1.mod;
>^
> Perhaps this should be filed against w3c-sgml-lib?

I don't know about this one. It could be a bug either in libxml2
(e.g. an unexpected regression in a corner case due to some fix
of a more general case) or in the DTD from w3c-sgml-lib. Some
investigation would be needed.

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

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

On 2021-09-20 17:08:26 +0200, Thorsten Glaser wrote:
> On Mon, 20 Sep 2021, Vincent Lefevre wrote:
> 
> > Then libxml2 can find the right file on the local file system via
> > catalogs. In my case (which is the *default* setup with Debian
> 
> I never understood this catalogue thing. When I tried it, it didn’t
> work for me (that may admittedly have been multiple releases ago),
> the documentation was as good as Chinese to me, and… meh.

The catalog system was very buggy in the past. I had reported
many bugs in 2004. Things have much improved. The latest bugs
I found were in 2012.

> > Hmm... there seems to be a subtle difference in xhtml-special.ent:
> 
> Interesting.
> 
> I’m working with an XHTML 1.1 DTD, which has the entities inline
> (not sure if that was my doing or if I got it like this) and it
> too has:
> 
> 
>  
>  
>  
>  
> 
>  

For the 1.1 DTD, w3c-dtd-xhtml 1.1-5 had the *upstream* file
xhtml-1.1/basic/xhtml-special.ent with the buggy entity definitions






In w3c-sgml-lib, the xhtml-special.ent file no longer depends on
the XHTML version, and it has correct definitions.

> But if this upstream change affects DTDs that were once released, maybe
> it should accept, but ignore, this specific wrong redeclaration.

Perhaps. This should probably be first talked with upstream.

> Though you said the bug was introduced in a Debian package only…
> where did the package get the wrong .ent files from?

See my other message: I suppose that Debian took the XHTML 1.1
version (which was buggy) to use it with both XHTML 1.0 and XHTML 1.1
DTDs. This is my only plausible explanation.

> If this is truly Debian-local, I agree nothing than the conflict is
> probably needed.

The XHTML 1.0 DTD issue seems Debian-local. But the XHTML 1.1 DTD
issue (which I have not tried) is an upstream one, according to the
w3c-dtd-xhtml_1.1.orig.tar.gz file, which is the upstream part I
got from https://snapshot.debian.org/package/w3c-dtd-xhtml/1.1-5/ .

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

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Thorsten Glaser]

On Mon, 20 Sep 2021, Vincent Lefevre wrote:

> Then libxml2 can find the right file on the local file system via
> catalogs. In my case (which is the *default* setup with Debian

I never understood this catalogue thing. When I tried it, it didn’t
work for me (that may admittedly have been multiple releases ago),
the documentation was as good as Chinese to me, and… meh.

> Hmm... there seems to be a subtle difference in xhtml-special.ent:

Interesting.

I’m working with an XHTML 1.1 DTD, which has the entities inline
(not sure if that was my doing or if I got it like this) and it
too has:


 
 
 
 

 

But if this upstream change affects DTDs that were once released, maybe
it should accept, but ignore, this specific wrong redeclaration. Though
you said the bug was introduced in a Debian package only… where did the
package get the wrong .ent files from? If this is truly Debian-local, I
agree nothing than the conflict is probably needed.

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#994479: marked as done (sssd FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 15:04:09 +
with message-id 
and subject line Bug#994479: fixed in sssd 2.5.2-2
has caused the Debian Bug report #994479,
regarding sssd FTBFS: test failures
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.)


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

https://buildd.debian.org/status/logs.php?pkg=sssd=2.5.2-1

...
FAIL: src/tests/pyhbac-test.py3
===

F
==
FAIL: testImport (__main__.PyHbacImport)
Import the module and assert it comes from tree
--
Traceback (most recent call last):
  File "/<>/src/tests/pyhbac-test.py", line 91, in testImport
self.assertEqual(pyhbac.__file__, MODPATH + "/pyhbac.so")
AssertionError: '/<>/build/./tp_pyhbac__5qlreyw/pyhbac.so' != 
'./tp_pyhbac__5qlreyw/pyhbac.so'
- /<>/build/./tp_pyhbac__5qlreyw/pyhbac.so
+ ./tp_pyhbac__5qlreyw/pyhbac.so


--
Ran 1 test in 0.002s

FAILED (failures=1)
FAIL src/tests/pyhbac-test.py3.sh (exit status: 1)

FAIL: src/tests/pysss-test.py3
==

F
==
FAIL: test_import (__main__.PysssImport)
Import the module and assert it comes from tree
--
Traceback (most recent call last):
  File "/<>/src/tests/pysss-test.py", line 61, in test_import
self.assertEqual(pysss.__file__, MODPATH + "/pysss.so")
AssertionError: '/<>/build/./tp_pysss_c9p_o2j6/pysss.so' != 
'./tp_pysss_c9p_o2j6/pysss.so'
- /<>/build/./tp_pysss_c9p_o2j6/pysss.so
+ ./tp_pysss_c9p_o2j6/pysss.so


--
Ran 1 test in 0.007s

FAILED (failures=1)
FAIL src/tests/pysss-test.py3.sh (exit status: 1)

FAIL: src/tests/pysss_murmur-test.py3
=

F
==
FAIL: testImport (__main__.PySssMurmurImport)
Import the module and assert it comes from tree
--
Traceback (most recent call last):
  File "/<>/src/tests/pysss_murmur-test.py", line 62, in testImport
self.assertEqual(pysss_murmur.__file__, MODPATH + "/pysss_murmur.so")
AssertionError: 
'/<>/build/./tp_pysss_murmur_2364eupq/pysss_murmur.so' != 
'./tp_pysss_murmur_2364eupq/pysss_murmur.so'
- /<>/build/./tp_pysss_murmur_2364eupq/pysss_murmur.so
+ ./tp_pysss_murmur_2364eupq/pysss_murmur.so


--
Ran 1 test in 0.002s

FAILED (failures=1)
/<>/build
./tp_pysss_murmur_2364eupq
FAIL src/tests/pysss_murmur-test.py3.sh (exit status: 1)

SKIP: src/tests/whitespace_test
===

Git repository is required for this test!
SKIP src/tests/whitespace_test (exit status: 77)

SKIP: src/tests/double_semicolon_test
=

Git repository is required for this test!
SKIP src/tests/double_semicolon_test (exit status: 77)


Testsuite summary for sssd 2.5.2

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

See ./test-suite.log
Please report to sssd-de...@lists.fedorahosted.org

make[6]: *** [Makefile:41345: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: sssd
Source-Version: 2.5.2-2
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated sssd package)

(This message was generated automatically at their request; if you
believe that there is a 

Bug#993638: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Torrance, Douglas]

On Mon 20 Sep 2021 08:17:11 AM EDT, Vincent Lefevre  wrote:

On 2021-09-20 11:58:00 +, Torrance, Douglas wrote:

Control: affects -1 src:macaulay2

I believe this bug is also affecting the build of the Macaulay2 package.  From
[1,2]:

/usr/bin/make -C M2 validate-html
make[2]: Entering directory 
'/<>/macaulay2-1.18.0.1+git202109031258/M2'
-- validating all html and xhtml files in 
/<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2
validating: BGG/html/_direct__Image__Complex.html
*** invalid HTML: 
/<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2/BGG/html/_direct__Image__Complex.html
error: line 338: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated


The error message is different. I'd say that this is a different issue.


Fair enough.  I think it's related -- the latest release is more strict about
DTD files -- but involving a different DTD file, xhtml-math-svg.dtd from the
w3c-sgml-lib package.  Here's the output of xmllint, which gives a bit more
info:

$  xmllint --noout --loaddtd /usr/share/doc/Macaulay2/Macaulay2Doc/html/_ideal.html 
file:///usr/share/xml/w3c-sgml-lib/schema/dtd/WD-XHTMLplusMathMLplusSVG-20020809/xhtml-math-svg.dtd:338: parser error : xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

   %xhtml-qname-extra.decl;
   ^
Entity: line 2: 
   "http://www.w3.org/Math/DTD/mathml2/mathml2-qname-1.mod;

   ^
Perhaps this should be filed against w3c-sgml-lib?


signature.asc
Description: PGP signature

Bug#994736: libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1

[Niko Tyni]

On Mon, Sep 20, 2021 at 10:25:43AM +0100, Niko Tyni wrote:
> Source: libmath-gsl-perl
> Version: 0.43-1
> Severity: serious
> Tags: ftbfs
> 
> This package failed to build on several architectures.
> 
> From 
> https://buildd.debian.org/status/fetch.php?pkg=libmath-gsl-perl=arm64=0.43-1=1632072156=0
> 
> #   Failed test 'use Math::GSL::Matrix;'
> #   at t/00-load.t line 14.
> # Tried to use 'Math::GSL::Matrix'.
> # Error:  Can't load 
> '/<>/blib/arch/auto/Math/GSL/Matrix/Matrix.so' for module 
> Math::GSL::Matrix: /<>/blib/arch/auto/Math/GSL/Matrix/Matrix.so: 
> undefined symbol: gsl_matrix_char_norm1 at 
> /usr/lib/aarch64-linux-gnu/perl-base/DynaLoader.pm line 187.
> #  at /<>/blib/lib/Math/GSL/Matrix.pm line 11.
> # Compilation failed in require at t/00-load.t line 14.
> # BEGIN failed--compilation aborted at t/00-load.t line 14.

The failing architectures are the ones where char is unsigned.

  https://github.com/leto/math--gsl/issues/231

  https://lists.gnu.org/archive/html/bug-gsl/2021-06/msg4.html

are probably related but "the other way around": aiui they disabled
the exposure of the unsigned char versions of the functions, which were
missing on the signed char architectures.
-- 
Niko Tyni   nt...@debian.org

Processed: Clone for buster and bullseye

[Debian Bug Tracking System]

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

> clone 994746 -1
Bug #994746 [ccextractor] ccextractor embeds unpatched and vulnerable source 
code from gpac
Bug 994746 cloned as bug 994754
> notfound 994746 0.93+ds1-1
Bug #994746 [ccextractor] ccextractor embeds unpatched and vulnerable source 
code from gpac
No longer marked as found in versions ccextractor/0.93+ds1-1.
> found 994746 0.88+ds1-1
Bug #994746 [ccextractor] ccextractor embeds unpatched and vulnerable source 
code from gpac
Marked as found in versions ccextractor/0.88+ds1-1.
> found 994746 0.87+ds1-1
Bug #994746 [ccextractor] ccextractor embeds unpatched and vulnerable source 
code from gpac
Marked as found in versions ccextractor/0.87+ds1-1.
> thanks
Stopping processing here.

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

Bug#994753: boost1.74: boost.mpi Python module not installed

[Graham Inggs]

Source: boost1.74
Version: 1.74.0-10
Severity: serious
Tags: patch

Hi Maintainer

After #992223 was fixed, I noticed that the mpi-python autopkgtest still fails.
I found that mpi.cpython-39-x86_64-linux-gnu.so was not installed in
the libboost-mpi-python1.74.0 package.

I was able to fix this with the following change in debian/rules:

- cp stage-3*/lib/mpi.*.so
debian/libboost-mpi-python$(SOVERSION)/usr/lib/python3/dist-packages/boost/
|| true
+ cp stage-3*/lib/*/mpi.*.so
debian/libboost-mpi-python$(SOVERSION)/usr/lib/python3/dist-packages/boost/
|| true

Also, demo2.py could be enabled again in debian/tests/mpi-python:

-#mpirun --oversubscribe --allow-run-as-root -np 2 python3 ./demo2.py
-echo "run: demo2 BROKEN FIXME"
+mpirun --oversubscribe --allow-run-as-root -np 2 python3 ./demo2.py
+echo "run: demo2 OK"

Regards
Graham

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

On 2021-09-20 15:57:35 +0200, Vincent Lefevre wrote:
> So, if I understand correctly, this was a Debian-specific bug. I
> suspect that the incorrect XHTML 1.1 definitions were retrieved
> from the old w3c-dtd-xhtml source and shared for both XHTML 1.0
> and XHTML 1.1 DTDs. This would explain how the bug has been
> introduced in Debian from 2012 to 2016 (and still now until the
> w3c-dtd-xhtml package is removed from users' machines).

I forgot to add that this means that probably almost all users
will not be affected by the bug after w3c-dtd-xhtml is removed
(i.e. I don't expect buggy files copied locally). So, definitively
no need to announce anything. The Conflicts should be sufficient.

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

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

On 2021-09-20 03:18:46 +0200, Vincent Lefevre wrote:
> Hmm... there seems to be a subtle difference in xhtml-special.ent:
> 
> With the file from w3c-dtd-xhtml:
> 
> 
> 
> 
> 
> 
> But with the file from w3c-sgml-lib:
> 
> 
> 
> 
> 
> 
 
 
 
 

in August 2002.

On https://snapshot.debian.org/package/w3c-dtd-xhtml/1.1-5/
I can see that the Debian package (released on 2004-08-08)
was correct (for the XHTML 1.0 xhtml-special.ent file; the
XHTML 1.1 one was incorrect).

But on https://snapshot.debian.org/package/w3c-sgml-lib/1.2-2/
(which gave the w3c-dtd-xhtml binary package in this version),
released on 2012-04-14, while the upstream part was correct,
the  w3c-sgml-lib_1.2-2.debian.tar.gz file has

  debian/legacy/basic/xhtml-special.ent

with the incorrect entity definitions. So, if I understand correctly,
this was a Debian-specific bug. I suspect that the incorrect XHTML 1.1
definitions were retrieved from the old w3c-dtd-xhtml source and
shared for both XHTML 1.0 and XHTML 1.1 DTDs. This would explain
how the bug has been introduced in Debian from 2012 to 2016 (and
still now until the w3c-dtd-xhtml package is removed from users'
machines).

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

Bug#994307: marked as done (libxml2: Removal of the python3-*-dbg packages in sid/bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 13:48:30 +
with message-id 
and subject line Bug#994307: fixed in libxml2 2.9.12+dfsg-5
has caused the Debian Bug report #994307,
regarding libxml2: Removal of the python3-*-dbg packages in sid/bookworm
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.)


-- 
994307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libxml2
Version: 2.9.12+dfsg-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal

Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
https://lists.debian.org/debian-python/2021/09/msg4.html

Stop building the python3-*-dbg package, but be careful
that all the reverse dependencies are also removed.

Please check for dependencies, build dependencies AND autopkg tests.
If help is needed, please ask on IRC #debian-python,
or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.12+dfsg-5
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Sep 2021 15:06:01 +0200
Source: libxml2
Architecture: source
Version: 2.9.12+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Mattia Rizzolo 
Closes: 993638 994307
Changes:
 libxml2 (2.9.12+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Stop building the python3-libxml2-dbg package.  Closes: #994307
   * Add a Conflicts against the old w3c-dtd-xhtml, that contains a .dtd that
 is not validating anymore.  Closes: #993638
   * Remove lintian override that was fixed in lintian for
 
debian-rules-uses-supported-python-versions-without-python-all-build-depends
Checksums-Sha1:
 b85091fd26c8ec67ef5490e7c776697f2d4d8efe 2576 libxml2_2.9.12+dfsg-5.dsc
 3dad03afdc4a42bcaa57f5c363748ad278d6a2d7 32960 
libxml2_2.9.12+dfsg-5.debian.tar.xz
 1ffeca05dea258df6eebbebf81a2fac49b90f738 9089 
libxml2_2.9.12+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 a8ed15cbe14a997109d5a81fde9af5fcd0adafc2026fd9f4932adb3e2b0a4f28 2576 
libxml2_2.9.12+dfsg-5.dsc
 ba1b6ec8ea12312cdffd1d7b24dbdfed2702ba920bab6f2029940be8159d2851 32960 
libxml2_2.9.12+dfsg-5.debian.tar.xz
 6108efb5fe7ce153b95f731ddc54362b5e8431d5abcae95592207c1bb1db6e9f 9089 
libxml2_2.9.12+dfsg-5_amd64.buildinfo
Files:
 d0ceaac200e3f4d41c83d4b9b208a8fa 2576 libs optional libxml2_2.9.12+dfsg-5.dsc
 02d6d97d0461600d47ba9242d5a0a596 32960 libs optional 
libxml2_2.9.12+dfsg-5.debian.tar.xz
 fae04d0c8745968045c8e4a8a33568aa 9089 libs optional 
libxml2_2.9.12+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmFIi64ACgkQCBa54Yx2
K61Q2g/+KC7LETlzrxC12HO23WBKcZ3iUdGNR+ftsNkefyOBTCAnjsVlCZ/6dVYr
CE5JmXJw+yTC3ZWuA4sxqh5FatpaVgEaBsqCrQ2vrHMWvbOE9DG4Gx/2pX9XE79M
FKJd45oUjb/1JGiCeeD/OO/YijlGYU1u+ocuEZBLeAJBBGV0v6kRV/cYjhNy6x5Y
h9BMj1IfFcpfw4Ri1Qec18HC5eTYUWmeur/UpyZS7WUH2l0sUw7+VOOiJn6AqQCm
YM3hhQ+eEjk0IkAJkMu2deto5q3o0sS9drdRuW8hs9EQ7SkCI5tBRUEqkNj0G5L5
LgcuR4HXy2tLrrGeu4dRPS0tFshPdo9VSNUoma6JX2rzza6cst4AuB8BRsG1I37p
A+1m45lEUpzuZfK0RFbD8OAJ31ngVRHF7QTT54j0aQRAYQ2xnPfbB2k5djnpUHvF
K3+uWp2Q6edn4Cr8LUjasNzZrh+SXO+M5ZwsV44U+GNEWN63N4T/arjWcuFbC5tx
L2Ygm7riu4bG6JeQGwa6DXVp46tn2dmhcwSXNy3/QgAbsgPxQTaka4+33tBVDhXv
qNn8ZwaKXmeYAg3dQXSrcX+3fe3g0jF3/KMr5zvQhlzPFMHFpy+Ilpgea8rbOVVD
iQLSS9TMWLpzI9WnnVW7eW+Sf//dSt4mXHwgY/5C8QNBYXPJOEQ=
=5rLf
-END PGP SIGNATURE End Message ---

Bug#993638: marked as done (libxml2: XHTML 1.0 validation is broken with w3c-dtd-xhtml's xhtml-special.ent file)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 13:48:30 +
with message-id 
and subject line Bug#993638: fixed in libxml2 2.9.12+dfsg-5
has caused the Debian Bug report #993638,
regarding libxml2: XHTML 1.0 validation is broken with w3c-dtd-xhtml's 
xhtml-special.ent file
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.)


-- 
993638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxml2
Version: 2.9.12+dfsg-3
Severity: grave
Justification: renders package unusable

After the upgrade to 2.9.12+dfsg-3, XHTML 1.0 validation is broken.
There was no such issue with 2.9.10+dfsg-6.7.

Testcase:


http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
title
text


$ xmllint --noout --loaddtd --valid test.html
error : xmlAddEntity: invalid redeclaration of predefined entity
error : xmlAddEntity: invalid redeclaration of predefined entity

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

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

Versions of packages libxml2 depends on:
ii  libc6 2.31-17
ii  libicu67  67.1-7
ii  liblzma5  5.2.5-2
ii  zlib1g1:1.2.11.dfsg-2

libxml2 recommends no packages.

libxml2 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.12+dfsg-5
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Sep 2021 15:06:01 +0200
Source: libxml2
Architecture: source
Version: 2.9.12+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Mattia Rizzolo 
Closes: 993638 994307
Changes:
 libxml2 (2.9.12+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Stop building the python3-libxml2-dbg package.  Closes: #994307
   * Add a Conflicts against the old w3c-dtd-xhtml, that contains a .dtd that
 is not validating anymore.  Closes: #993638
   * Remove lintian override that was fixed in lintian for
 
debian-rules-uses-supported-python-versions-without-python-all-build-depends
Checksums-Sha1:
 b85091fd26c8ec67ef5490e7c776697f2d4d8efe 2576 libxml2_2.9.12+dfsg-5.dsc
 3dad03afdc4a42bcaa57f5c363748ad278d6a2d7 32960 
libxml2_2.9.12+dfsg-5.debian.tar.xz
 1ffeca05dea258df6eebbebf81a2fac49b90f738 9089 
libxml2_2.9.12+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 a8ed15cbe14a997109d5a81fde9af5fcd0adafc2026fd9f4932adb3e2b0a4f28 2576 
libxml2_2.9.12+dfsg-5.dsc
 ba1b6ec8ea12312cdffd1d7b24dbdfed2702ba920bab6f2029940be8159d2851 32960 
libxml2_2.9.12+dfsg-5.debian.tar.xz
 6108efb5fe7ce153b95f731ddc54362b5e8431d5abcae95592207c1bb1db6e9f 9089 
libxml2_2.9.12+dfsg-5_amd64.buildinfo
Files:
 d0ceaac200e3f4d41c83d4b9b208a8fa 2576 libs optional libxml2_2.9.12+dfsg-5.dsc
 02d6d97d0461600d47ba9242d5a0a596 32960 libs optional 
libxml2_2.9.12+dfsg-5.debian.tar.xz
 fae04d0c8745968045c8e4a8a33568aa 9089 libs optional 
libxml2_2.9.12+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmFIi64ACgkQCBa54Yx2
K61Q2g/+KC7LETlzrxC12HO23WBKcZ3iUdGNR+ftsNkefyOBTCAnjsVlCZ/6dVYr
CE5JmXJw+yTC3ZWuA4sxqh5FatpaVgEaBsqCrQ2vrHMWvbOE9DG4Gx/2pX9XE79M

Bug#994746: ccextractor embeds unpatched and vulnerable source code from gpac

[Neil Williams]

Package: ccextractor
Version: 0.93+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team 


ccextractor embeds source code from the gpac project. Some files are
moved and some files are omitted but the files that remain match the
equivalent files in gpac. In unstable, ccextractor 0.93 embeds gpac 1.0.1.

This embedding has not been declared to the security team and is not
listed on the embedded copies wiki page (yet).

I have a local build which adds gpac to the existing list of ccextractor
dependencies which are removed from the ccextractor source and replaced
with a dependency on libgpac10. This will resolve this bug for unstable
and for bookworm.

The problem affects older versions of ccextractor as well. Version 0.88
and 0.87 of ccextractor embed gpac code in a similar fashion, from gpac
0.7.1 - a version which was packaged for Debian but did not make it into
a stable release. Buster and bullseye have gpac version 0.52, with some
additions. Version 0.52 of gpac is not used in ccextractor.

ccextractor in buster and bullseye therefore embeds newer gpac code than
is currently available in the binaries built from gpac in buster or bullseye.
It is likely that buster and bullseye would need separate updates to
patch the vulnerabilities directly into the embedded gpac code at
v0.7.1 - it should probably be the same patch for each.

Additionally, not all source code files from gpac are embedded into
ccextractor - an AppWizard was used to trim the source to the
functionality expected by the ccextractor upstream. Some CVEs which
affect gpac do not therefore affect ccextractor as the vulnerable source
code has been removed during the embedding process by ccextractor upstream.

An initial check of the ccextractor source code in buster showed that
the following CVEs are applicable to ccextractor in buster and therefore
in bullseye, via embedded gpac code at gpac version 0.7.1.

CVE-2021-33362
CVE-2021-32440
CVE-2021-32139
CVE-2021-32137
CVE-2021-32134
CVE-2021-31260
CVE-2021-31258
CVE-2021-30014
CVE-2021-28300
CVE-2021-21852
CVE-2020-35981
CVE-2020-35980
CVE-2020-24829
CVE-2020-19751
CVE-2020-6631
CVE-2020-6630
CVE-2019-20208
CVE-2019-20171
CVE-2019-20170
CVE-2019-20162
CVE-2019-20161
CVE-2019-13618
CVE-2019-12483
CVE-2019-12482
CVE-2019-12481
CVE-2018-21015


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

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

Versions of packages ccextractor depends on:
ii  libavcodec58   7:4.4-6+b1
ii  libavformat58  7:4.4-6+b1
ii  libavutil567:4.4-6+b1
ii  libc6  2.32-3
ii  libfreetype6   2.10.4+dfsg-1
ii  liblept5   1.79.0-1.1
ii  libpng16-161.6.37-3
ii  libswscale57:4.4-6+b1
ii  libtesseract4  4.1.1-2.1
ii  libutf8proc2   2.5.0-1
ii  zlib1g 1:1.2.11.dfsg-2

ccextractor recommends no packages.

ccextractor suggests no packages.

-- no debconf information

Bug#993638: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Vincent Lefevre]

On 2021-09-20 11:58:00 +, Torrance, Douglas wrote:
> Control: affects -1 src:macaulay2
> 
> I believe this bug is also affecting the build of the Macaulay2 package.  From
> [1,2]:
> 
> /usr/bin/make -C M2 validate-html
> make[2]: Entering directory 
> '/<>/macaulay2-1.18.0.1+git202109031258/M2'
> -- validating all html and xhtml files in 
> /<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2
> validating: BGG/html/_direct__Image__Complex.html
> *** invalid HTML: 
> /<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2/BGG/html/_direct__Image__Complex.html
> error: line 338: xmlParseEntityDecl: entity xhtml-qname-extra.mod not 
> terminated

The error message is different. I'd say that this is a different issue.

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

Bug#993638: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Torrance, Douglas]

Control: affects -1 src:macaulay2

I believe this bug is also affecting the build of the Macaulay2 package.  From
[1,2]:

/usr/bin/make -C M2 validate-html
make[2]: Entering directory 
'/<>/macaulay2-1.18.0.1+git202109031258/M2'
-- validating all html and xhtml files in 
/<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2
validating: BGG/html/_direct__Image__Complex.html
*** invalid HTML: 
/<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2/BGG/html/_direct__Image__Complex.html
error: line 338: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

...

validating: AlgebraicSplines/html/index.html
*** invalid HTML: 
/<>/macaulay2-1.18.0.1+git202109031258/M2/usr-dist/common/share/doc/Macaulay2/AlgebraicSplines/html/index.html
error: line 338: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

9328 HTML files checked; 9328 invalid
make[2]: *** [GNUmakefile:302: validate-html] Error 1

[1] 
https://launchpadlibrarian.net/556859860/buildlog_ubuntu-impish-amd64.macaulay2_1.18.0.1+git202109031258-0ppa202109031444~ubuntu21.10.1_BUILDING.txt.gz
[2] https://github.com/Macaulay2/M2/issues/2225


signature.asc
Description: PGP signature

Processed: xmlParseEntityDecl: entity xhtml-qname-extra.mod not terminated

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:macaulay2
Bug #993638 [libxml2] libxml2: XHTML 1.0 validation is broken with 
w3c-dtd-xhtml's xhtml-special.ent file
Added indication that 993638 affects src:macaulay2

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

Bug#994713: marked as done (ignition-math: FTBFS on arm64, ppc64el, s390x)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 13:34:15 +0200
with message-id 

and subject line 
has caused the Debian Bug report #994713,
regarding ignition-math: FTBFS on arm64, ppc64el, s390x
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.)


-- 
994713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ignition-math
Version: 6.8.0+ds-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| 98% tests passed, 1 tests failed out of 51
|
| Total Test time (real) = 127.49 sec
|
| The following tests FAILED:
|32 - UNIT_SpeedLimiter_TEST (Failed)
| Errors while running CTest
| make[2]: *** [Makefile:151: test] Error 8

See
https://buildd.debian.org/status/fetch.php?pkg=ignition-math=arm64=6.8.0%2Bds-2=1629995923=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Uploaded 6.8.0+ds-3 that fixed all the regressions:
https://buildd.debian.org/status/package.php?p=ignition-math
--- End Message ---

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

On 2021-09-20 12:11:17 +0200, Mattia Rizzolo wrote:
> On Mon, Sep 20, 2021 at 11:41:38AM +0200, Vincent Lefevre wrote:
> > Please also make sure that the NEWS file is up-to-date; see my other
> > message. This is also useful for the user when getting regressions
> > in general (possibly from bug fixes like here).
> 
> I'm not sure I'd like to add such item to the Debian's NEWS.

Note that for this one, I was talking about the upstream NEWS. But
this may be an upstream bug. The NEWS file hasn't been regenerated
in the git repository. I don't know about the tarball. But the
announce message *does* contain the release notes. So I'm wondering.

Well, there is already an upstream bug for this one:

  https://gitlab.gnome.org/GNOME/libxml2/-/issues/171

This was for 2.9.10, but is still a valid issue; I've added a comment.

> It would stop updates for too many users that most likely are not
> affected. For now, you are really the only one that brought up this
> issue.

Concerning Debian's NEWS, it is difficult to know, as I fear that
this hasn't been tested by most users. I could detect the issue,
because I use a machine more recent than Debian/stable and because
I have a cron job that does a check everyday.

> > I'm wondering whether this check for invalid redeclarations of
> > predefined entities should also go to Debian/stable since it fixes
> > an integer overflow at the same time:
> > 
> >   https://gitlab.gnome.org/GNOME/libxml2/-/issues/217
> > 
> > Any security issue related to that?
> 
> AFAIK not yet at least.

This is the opposite: things like integer overflows (in particular
when they occur on untrusted data like here) should be regarded as
security issues by default, but it can be found later that they
have no security implications.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 990079 93.0.4577.82-1
Bug #990079 [chromium] chromium: Several upstream versions released with 
important security fixes
Bug #992625 [chromium] chromium: security CVE-2021-30604To30598
Marked as fixed in versions chromium/93.0.4577.82-1.
Marked as fixed in versions chromium/93.0.4577.82-1.
> fixed 992625 93.0.4577.82-1
Bug #992625 [chromium] chromium: security CVE-2021-30604To30598
Bug #990079 [chromium] chromium: Several upstream versions released with 
important security fixes
Ignoring request to alter fixed versions of bug #992625 to the same values 
previously set
Ignoring request to alter fixed versions of bug #990079 to the same values 
previously set
> fixed 993998 93.0.4577.82-1
Bug #993998 [chromium] Security fixes
Marked as fixed in versions chromium/93.0.4577.82-1.
>
End of message, stopping processing here.

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

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Mattia Rizzolo]

On Mon, Sep 20, 2021 at 11:41:38AM +0200, Vincent Lefevre wrote:
> Please also make sure that the NEWS file is up-to-date; see my other
> message. This is also useful for the user when getting regressions
> in general (possibly from bug fixes like here).

I'm not sure I'd like to add such item to the Debian's NEWS.  It would
stop updates for too many users that most likely are not affected.  For
now, you are really the only one that brought up this issue.

> BTW, the error message should be more detailed, e.g. saying which
> entity and which URI. This would have made debugging so much easier.
> But that's a separate issue; I'll report a bug upstream if this has
> not already been done.

It hasn't been done, so you should raise a bug with them if you think
they should.

> I'm wondering whether this check for invalid redeclarations of
> predefined entities should also go to Debian/stable since it fixes
> an integer overflow at the same time:
> 
>   https://gitlab.gnome.org/GNOME/libxml2/-/issues/217
> 
> Any security issue related to that?

AFAIK not yet at least.

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

Bug#982731: closing 982731

[Andrej Shadura]

close 982731 
thanks
-- 
Cheers,
  Andrej

Bug#994699: libtest-xml-simple-perl: Test failure in t/03valid.t

[Niko Tyni]

On Sun, Sep 19, 2021 at 05:42:55PM +0200, gregor herrmann wrote:
> Package: libtest-xml-simple-perl
> Version: 1.05-2
> Severity: serious
> Tags: ftbfs sid bookworm
> Justification: fails to build from source (but built successfully in the past)

> This is a bit suprising as we have debian/patches/bug-952180.patch
> which fixes the same test (#952180), and now the issue has (almost)
> reappeared the other way round although I see no obvious changes (no
> uploads of neither libtest-xml-simple-perl nor libxml-libxml-perl).

FWIW I expect it broke with the recent libxml2 upload.
-- 
Niko

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

(We searched for the commmit at about the same time...)

On 2021-09-20 11:15:16 +0200, Mattia Rizzolo wrote:
> I bisected libxml2:
[...]

FYI, I found this commit just by looking at the git logs, with a
search for "predefined" (and "redeclaration" works too). This is
faster than bisecting. This is great that libxml2 has detailed
logs, not true for every software...

> > > In the latter case, I think that
> > > there should be a Breaks against w3c-dtd-xhtml.
> 
> On its way.

Thanks.

Please also make sure that the NEWS file is up-to-date; see my other
message. This is also useful for the user when getting regressions
in general (possibly from bug fixes like here).

BTW, the error message should be more detailed, e.g. saying which
entity and which URI. This would have made debugging so much easier.
But that's a separate issue; I'll report a bug upstream if this has
not already been done.

I'm wondering whether this check for invalid redeclarations of
predefined entities should also go to Debian/stable since it fixes
an integer overflow at the same time:

  https://gitlab.gnome.org/GNOME/libxml2/-/issues/217

Any security issue related to that?

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

Bug#994736: libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1

[Niko Tyni]

Source: libmath-gsl-perl
Version: 0.43-1
Severity: serious
Tags: ftbfs

This package failed to build on several architectures.

>From 
>https://buildd.debian.org/status/fetch.php?pkg=libmath-gsl-perl=arm64=0.43-1=1632072156=0

#   Failed test 'use Math::GSL::Matrix;'
#   at t/00-load.t line 14.
# Tried to use 'Math::GSL::Matrix'.
# Error:  Can't load 
'/<>/blib/arch/auto/Math/GSL/Matrix/Matrix.so' for module 
Math::GSL::Matrix: /<>/blib/arch/auto/Math/GSL/Matrix/Matrix.so: 
undefined symbol: gsl_matrix_char_norm1 at 
/usr/lib/aarch64-linux-gnu/perl-base/DynaLoader.pm line 187.
#  at /<>/blib/lib/Math/GSL/Matrix.pm line 11.
# Compilation failed in require at t/00-load.t line 14.
# BEGIN failed--compilation aborted at t/00-load.t line 14.

[...]

Test Summary Report
---
t/00-load.t  (Wstat: 512 Tests: 56 Failed: 2)
  Failed tests:  7, 54
  Non-zero exit status: 2
t/BLAS.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 109 tests but ran 0.
t/Eigen.t(Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 59 tests but ran 0.
t/GSL.t  (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/Linalg.t   (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/Matrix.t   (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/Multifit.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/Multilarge.t   (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/SparseMatrix.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=58, Tests=3449, 22 wallclock secs ( 1.15 usr  0.22 sys + 19.59 cusr  2.07 
csys = 23.03 CPU)
Result: FAIL

-- 
Niko

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

Concerning the change in the libxml2 code, I found this:

  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/01411e7c5ea0fff181271e092f46a2138c3720ec
  "Check for invalid redeclarations of predefined entities"

with the example of the incorrect

   

which was in the old libxml2 testcases, BTW.

Thus this is intentional. But such a major change (since this breaks
official DTDs released in the past, something which should normally
*never* happen) should have at least been announced somewhere.
Otherwise one doesn't know what's going on (even a web search for the
error message led to nothing -- now, there's only my bug report...).

Now, I understand why there's nothing mentioned in the NEWS file,
which is a symlink to the changelog file: this file stops at
"v2.9.9: Jan 03 2019", while this version is 2.9.12.

The upstream release notes of libxml2 2.9.11

  https://mail.gnome.org/archives/xml/2021-May/msg0.html

contain:

  - Check for invalid redeclarations of predefined entities (Nick Wellnhofer)

Note that this change is recent, so that most users (Debian or not)
have not upgraded yet. Whether the issue would be more visible once
most users have upgraded (in particular if the old DTDs have been
archived locally with the XML data), I don't know.

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

Processed: Bug#993638 marked as pending in libxml2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993638 [libxml2] libxml2: XHTML 1.0 validation is broken with 
w3c-dtd-xhtml's xhtml-special.ent file
Added tag(s) pending.

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

Bug#993638: marked as pending in libxml2

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #993638 in libxml2 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/xml-sgml-team/libxml2/-/commit/09914caee210cebce062ea771d37c3865b6fd5bd


Add a Conflicts against the old w3c-dtd-xhtml, that contains a .dtd that is not 
validating anymore

Closes: #993638
Signed-off-by: Mattia Rizzolo 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993638

Bug#994554: marked as done (wannier90: FTBFS due to test failure on several architectures)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 09:19:27 +
with message-id 
and subject line Bug#994554: fixed in wannier90 3.1.0+ds-6
has caused the Debian Bug report #994554,
regarding wannier90: FTBFS due to test failure on several architectures
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.)


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

https://buildd.debian.org/status/logs.php?pkg=wannier90=3.1.0%2Bds-5

...
tests/testw90_example11_2 - silicon.win: **FAILED**.
final_spreads
ERROR: absolute error 3.54e-06 greater than 3.00e-06. (Test: 7.20268752.  
Benchmark: 7.20269106.)
final_spreads
ERROR: absolute error 3.54e-06 greater than 3.00e-06. (Test: 7.20268752.  
Benchmark: 7.20269106.)
final_spreads
ERROR: absolute error 3.55e-06 greater than 3.00e-06. (Test: 7.20268754.  
Benchmark: 7.20269109.)
final_spreads
ERROR: absolute error 3.55e-06 greater than 3.00e-06. (Test: 7.20268754.  
Benchmark: 7.20269109.)
final_spreads
ERROR: absolute error 3.55e-06 greater than 3.00e-06. (Test: 8.46395018.  
Benchmark: 8.46394663.)
final_spreads
ERROR: absolute error 3.56e-06 greater than 3.00e-06. (Test: 8.46395022.  
Benchmark: 8.46394666.)
final_spreads
ERROR: absolute error 3.55e-06 greater than 3.00e-06. (Test: 8.46395024.  
Benchmark: 8.46394669.)
final_spreads
ERROR: absolute error 3.53e-06 greater than 3.00e-06. (Test: 8.46395016.  
Benchmark: 8.46394663.)
...
All done. ERROR: only 56 out of 57 tests passed.
Failed test in:
/<>/test-suite/tests/testw90_example11_2/
make[2]: *** [Makefile:194: test-serial] Error 1
--- End Message ---
--- Begin Message ---
Source: wannier90
Source-Version: 3.1.0+ds-6
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated wannier90 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Sep 2021 04:09:22 -0400
Source: wannier90
Architecture: source
Version: 3.1.0+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andrius Merkys 
Closes: 994554
Changes:
 wannier90 (3.1.0+ds-6) unstable; urgency=medium
 .
   * Skipping a test failing on a bunch of architectures (Closes: #994554).
Checksums-Sha1:
 e62596696979b069d7ced97535a1de327b48f7b0 2365 wannier90_3.1.0+ds-6.dsc
 323eae0e65cff79327bf522e745739c6f24764ab 14016 
wannier90_3.1.0+ds-6.debian.tar.xz
 7505ec09ae3a4d713fe6fdc55c7be1a8bfe60af5 9483 
wannier90_3.1.0+ds-6_source.buildinfo
Checksums-Sha256:
 6847d4cde7921c87a2e339aea5570f0765f4944652abef100f52606296aa5d28 2365 
wannier90_3.1.0+ds-6.dsc
 d0d93018d19371efde8e405d79f92558d14f127428ca3861f1413a484eba027a 14016 
wannier90_3.1.0+ds-6.debian.tar.xz
 6cdc140a6939a94ffe9fe4b2a9a0e6e0d3b891b04f250a1d0b65087523805f94 9483 
wannier90_3.1.0+ds-6_source.buildinfo
Files:
 5008243d16eaacdfca659b7372903af5 2365 science optional wannier90_3.1.0+ds-6.dsc
 457f3342a15c5bdd5dc41cf6a001527e 14016 science optional 
wannier90_3.1.0+ds-6.debian.tar.xz
 a688c78cf05a5e66d5e1c996433b293e 9483 science optional 
wannier90_3.1.0+ds-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmFIS6ISHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHGw8QAJEwANYwzL+yP/tvZBENkZJqtJolC+Jv
9aCb85hkQ73TBXy2s6V5+yvns9T7YZGN5p9c536ht4QLVP9bz490faKxmMyx3v2n
xQYm6d8HP6xELbBTYrKW9pj0/ZihZ7h8f0ydOc4j/UTm0U8c2yJZMxVw2zKzl59B
rhDr6p/0K1Cb2FIJO4Kr9WqhvOpYk2go/kVWkR2TC4mg2+Ai55a3MxCudjQjj3Y3
mmhZXo6XyuInMld6KWFK8ZHvhTrr4JAMaiO+XOpQGnFEfwMiSptsHbRx1rb7mI06
UYQJjXYd4OWC7SUPiekMFwAtpIEzIjxhWhBRJf2wwLrctX6o+ndebv/yzQ9bWdx4
G2DpGtv+m5yj3ClEj9aPJZjR6R21gPuxrSd6mhpi91z/nbEVeVbgzBqe/iInrvBA
9iu8PaDXIbtfAu+0V3juiktrdTQKVSOO8t4eEiEBP7wxl2BY05QetUc+Ivd7rBGD
IfSYvD9PYOUlNI/ihOToga4XeLOpHt46sxrTtAJ2myxX0TNNouC28BPE5q+3JHdw
4ypO0YyAseKgpA9y+MX+XXI9JwHz2EBlwnCJ7ggaEYLzf9x3UpP0En2qicbcjA1m

Bug#993638: [xml/sgml-pkgs] Bug#993638: libxml2: XHTML 1.0 validation is broken

[Mattia Rizzolo]

On Mon, Sep 20, 2021 at 03:55:39AM +0200, Vincent Lefevre wrote:
> Control: retitle -1 libxml2: XHTML 1.0 validation is broken with 
> w3c-dtd-xhtml's xhtml-special.ent file
> 
> This should be reproducible with w3c-dtd-xhtml's xhtml-special.ent file.
> The summary of the actual issue is below.

Yes, indeed it is.

> > The errors correspond to amp and lt.
> > 
> > Now, I don't know whether the new libxml2 version is too picky,
> > or there was a real issue with the old entity files (ignored
> > by all parsers until now?).

I bisected libxml2:

01411e7c5ea0fff181271e092f46a2138c3720ec is the first bad commit
commit 01411e7c5ea0fff181271e092f46a2138c3720ec
Author: Nick Wellnhofer 
Date:   Mon Feb 8 20:58:32 2021 +0100

Check for invalid redeclarations of predefined entities

https://gitlab.gnome.org/GNOME/libxml2/-/commit/01411e7c5ea0fff181271e092f46a2138c3720ec

So it's clearly intentional of libxml2 to be more picky now, and flag
this issue in the old dtd.

> > In the latter case, I think that
> > there should be a Breaks against w3c-dtd-xhtml.

On its way.



Thanks for your help in debugging this issue.

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

Processed: closing 982731

[Debian Bug Tracking System]

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

> close 982731
Bug #982731 [src:aspell-sk] aspell-sk: FTBFS: patches fail to apply
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#994227: marked as done (gfortran-10: generates incorrect Iftran compiler)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 11:08:59 +0200
with message-id <0af4729f-7c52-9d67-0cea-bdbaec4eb...@debian.org>
and subject line Re: gfortran-10: generates incorrect Iftran compiler
has caused the Debian Bug report #994227,
regarding gfortran-10: generates incorrect Iftran compiler
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.)


-- 
994227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncl
Version: 6.6.2-8
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so
Control: block 992563 by -1

Dear Maintainer,

Your package FTBFS on i386, mipsel, and mips64el:

 dh_install: error: missing files, aborting
install -d debian/.debhelper/generated/ncl-ncarg
install -d debian/.debhelper/generated/libncarg0
install -d debian/.debhelper/generated/libncarg-dev
install -d debian/.debhelper/generated/libncarg-bin
install -d debian/.debhelper/generated/libncarg-data

Full buildlogs:

 
https://buildd.debian.org/status/fetch.php?pkg=ncl=i386=6.6.2-8=1631137769=0
 
https://buildd.debian.org/status/fetch.php?pkg=ncl=mipsel=6.6.2-8=1631138470=0
 
https://buildd.debian.org/status/fetch.php?pkg=ncl=mips64el=6.6.2-8=1631136659=0

Interestingly 6.6.2-7+b1 built successfully on mips*, but also failed on i386:

 
https://buildd.debian.org/status/fetch.php?pkg=ncl=i386=6.6.2-7%2Bb1=1631139041=0

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Version: 10.3.0-11

Can't reproduce anymore with this version.--- End Message ---

Bug#994227: gfortran-10: generates incorrect Iftran compiler

[Matthias Klose]

Version: 10.3.0-11

Can't reproduce anymore with this version.

Bug#994732: python3-whiteboard: Python 2 syntax leads to SyntaxError

[Stuart Prescott]

Package: python3-whiteboard
Version: 1.0+git20170915-6
Severity: serious
Justification: crashes on startup;  not usable
X-Debbugs-Cc: stu...@debian.org

Dear Maintainer,

Installing python3-whiteboard and running python-whiteboard fails as follows:

$ /usr/bin/python-whiteboard
Using directory: /usr/share/python-whiteboard
Traceback (most recent call last):
  File "/usr/bin/python-whiteboard", line 24, in 
if __name__ == '__main__': main()
  File "/usr/bin/python-whiteboard", line 20, in main
import pywhiteboard
  File "/usr/share/python-whiteboard/pywhiteboard.py", line 4, in 
from wiimote import Wiimote
  File "/usr/share/python-whiteboard/wiimote.py", line 93
except bluetooth.BluetoothError, errString:
   ^
SyntaxError: invalid syntax

Quickly fixing that bug reveals that there are more:

/usr/share/python-whiteboard/linuxWiimoteLib.py:
TabError: inconsistent use of tabs and spaces in indentation

Looking at the upstream git repo, there seems to be some more recent commits
since this particular git snapshot and they are aimed at PyQt5 and Python 3
compatibility.

If possible, this package should be updated in bullseye but I suspect that
the release managers will not like the size of the changes required; if that
is the case then it should be removed from bullseye, but perhaps it could
appear in bullseye-backports instead.

thanks
Stuart


-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (550, 'stable-security'), (500, 'stable-updates'), (500, 
'stable-debug'), (500, 'proposed-updates'), (500, 'stable'), (60, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-whiteboard depends on:
ii  python33.9.2-3
ii  python3-bluez  0.23-3
ii  python3-cwiid  0.6.91-2+b1
ii  python3-numpy  1:1.19.5-1
ii  python3-pyqt5  5.15.2+dfsg-3
ii  python3-xlib   0.29-1

python3-whiteboard recommends no packages.

python3-whiteboard suggests no packages.

-- no debconf information

Processed: closing 994473

[Debian Bug Tracking System]

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

> close 994473 2.37-7
Bug #994473 [src:binutils] binutils FTBFS on x86: cannot stat 
'debian/binutils-/usr/x86_64-linux-gnu//lib/libbfd*arc*.so'
Marked as fixed in versions binutils/2.37-7.
Bug #994473 [src:binutils] binutils FTBFS on x86: cannot stat 
'debian/binutils-/usr/x86_64-linux-gnu//lib/libbfd*arc*.so'
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: python3-ecmwflibs: ModuleNotFoundError: No module named 'findlibs'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:cfgrib
Bug #994731 [python3-ecmwflibs] python3-ecmwflibs: ModuleNotFoundError: No 
module named 'findlibs'
Added indication that 994731 affects src:cfgrib

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

Bug#994731: python3-ecmwflibs: ModuleNotFoundError: No module named 'findlibs'

[Adrian Bunk]

Package: python3-ecmwflibs
Version: 0.13.3-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:cfgrib

https://buildd.debian.org/status/logs.php?pkg=cfgrib=0.9.9.0-1

This seems to be due to:

$ python3
Python 3.9.7 (default, Sep  3 2021, 06:18:44)
[GCC 10.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ecmwflibs
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/ecmwflibs/__init__.py", line 18, in 

from findlibs import find as _find_library
ModuleNotFoundError: No module named 'findlibs'
>>>

Bug#994309: marked as done (markupsafe: Removal of the python3-*-dbg packages in sid/bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 20 Sep 2021 07:18:48 +
with message-id 
and subject line Bug#994309: fixed in markupsafe 2.0.1-1
has caused the Debian Bug report #994309,
regarding markupsafe: Removal of the python3-*-dbg packages in sid/bookworm
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.)


-- 
994309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:markupsafe
Version: 1.1.1-1
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: pydbg-removal

Python 3.8 upstream now has a common ABI for normal and debug
extension builds, so we can drop the python3-*-dbg packages.
Details at
https://lists.debian.org/debian-python/2021/09/msg4.html

Stop building the python3-*-dbg package, but be careful
that all the reverse dependencies are also removed.

Please check for dependencies, build dependencies AND autopkg tests.
If help is needed, please ask on IRC #debian-python,
or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: markupsafe
Source-Version: 2.0.1-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated markupsafe 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: Fri, 17 Sep 2021 23:27:58 +0200
Source: markupsafe
Architecture: source
Version: 2.0.1-1
Distribution: experimental
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Thomas Goirand 
Closes: 994309
Changes:
 markupsafe (2.0.1-1) experimental; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from deprecated 9 to 12.
   * Apply multi-arch hints.
 + python-markupsafe-dbg, python3-markupsafe-dbg: Add Multi-Arch: same.
 .
   [ Ondřej Nový ]
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * Use the new Debian Python Team contact name and address
 .
   [ Thomas Goirand ]
   * Team upload.
   * New upstream release.
   * Ran wrap-and-sort -bastk.
   * Removed useless versions in build-depends.
   * Kill Python2 and dbg packages. (Closes: #994309).
Checksums-Sha1:
 a2e5f29b9960403c3fe6377054cf12084df74917 2008 markupsafe_2.0.1-1.dsc
 e1b766b2b1601fde67b3b19ed2f13b9746bb1cca 18596 markupsafe_2.0.1.orig.tar.gz
 4bc39e1f0aa7e42d6b8d33ee5f26a25dc3fbbfa6 3624 markupsafe_2.0.1-1.debian.tar.xz
 a30ce7db365bccd1aa6a79b669daa7088cf8c209 7179 
markupsafe_2.0.1-1_amd64.buildinfo
Checksums-Sha256:
 464a9e5da5726644431708c22e85d0d2e1e5f5c54ab0afe080ec3f82c1ed0f95 2008 
markupsafe_2.0.1-1.dsc
 594c67807fb16238b30c44bdf74f36c02cdf22d1c8cda91ef8a0ed8dabf5620a 18596 
markupsafe_2.0.1.orig.tar.gz
 f357907c56a0d8853b1af0a118bc49d2159413c8d6cd554a6382f6ea0fd1493b 3624 
markupsafe_2.0.1-1.debian.tar.xz
 0cd444ba870a9bc8663a6a8c1c0fc7dd6b4bad4ac34678aa65ee312d8223ada4 7179 
markupsafe_2.0.1-1_amd64.buildinfo
Files:
 840f25fdbdd4153f108637b6fe51c082 2008 python optional markupsafe_2.0.1-1.dsc
 892e0fefa3c488387e5cc0cad2daa523 18596 python optional 
markupsafe_2.0.1.orig.tar.gz
 e35fcaf972409aeeb9780665b262f91c 3624 python optional 
markupsafe_2.0.1-1.debian.tar.xz
 bb3f059d4ccc10eadd9c6eb66046e580 7179 python optional 
markupsafe_2.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmFIMf0ACgkQ1BatFaxr
Q/6vFg//didku88lt8+7/vLnnih32E/ZH2dWz8UomAceR6ZAwohFfHOZSx31Ap21
TtQUbnwIP/Z5aoTST9neOVMsaJ9eShuTs52BHvWlxTVS43Urpr5Xqo/KyQ5FfsJM
f0/7+zOURAXE5fg6TerjEnMMCg5vtiOMq/h42Ffemm4yOTtaZq+1z7InZGMxxFUM
dHQVvCzLw1yKAoOkyJyt1D1T7CRgXnII5Qcw0nWY9He44astz8GJ33bSjmDsRoXm
OgH2QYCa65ejSVH3uf01Ra8fM/amyIoQoF98OeD5xSdGJ86GmLsPKXad7whmuPmu
GmPDNEt/5iDGgZlhXatMwiZS6BoNBfAczpnGX0I2KGn++M3FH8n2eV/5xVjpjEG9
F5tIiJrv7J9gcDinervwZknHsf+GM/KokQlLyG4EemLPjRISMK8JSpygDRvhQ4zj
k+ds6kHaQDgS2EknhDeB0Z8l1Xh8Y4KksU5dkAM08TNJbCldu37iSLlH7jQOOybt
Xi00THI96msb8Jszu0nrhd7QCC2eIcMvZEiIqaaeuuKvOFUztDvhvHpv8IIGrCuL

Processed: Bug#994309 marked as pending in markupsafe

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #994309 [src:markupsafe] markupsafe: Removal of the python3-*-dbg packages 
in sid/bookworm
Added tag(s) pending.

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

Bug#994309: marked as pending in markupsafe

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/markupsafe/-/commit/9c10e0dc0974eb0a11e834f97a6ad8c7aa3754eb


Kill Python2 and dbg packages. (Closes: #994309).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/994309