Bug#1006333: Biboumi 9.0 on bullseye

[Kris]

Same issue with Biboumi 9.0 on Debian Bullseye and libexpat1 2.2.10-2.

Was working fine until I updated today.

Bug#1005492: marked as done (slic3r-prusa: FTBFS: ld: cannot find -lcereal: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 09:48:53 +
with message-id 
and subject line Bug#1005492: fixed in slic3r-prusa 2.4.0+dfsg-2
has caused the Debian Bug report #1005492,
regarding slic3r-prusa: FTBFS: ld: cannot find -lcereal: No such file or 
directory
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fext-numeric-literals -Wall -Wno-reorder -O3 -DNDEBUG 
> -Wl,-z,relro CMakeFiles/libnest2d_tests.dir/libnest2d_tests_main.cpp.o 
> CMakeFiles/libnest2d_tests.dir/printer_parts.cpp.o -o libnest2d_tests  
> ../../src/libnest2d/liblibnest2d.a ../../src/libslic3r/liblibslic3r.a 
> ../../src/libnest2d/liblibnest2d.a ../../src/libslic3r/liblibslic3r.a 
> /usr/lib/x86_64-linux-gnu/libnlopt.so ../../src/admesh/libadmesh.a -lcereal 
> ../../src/miniz/libminiz_static.a 
> /usr/lib/x86_64-linux-gnu/libboost_log.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_locale.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0 
> ../../src/clipper/libclipper.a ../../src/boost/libnowide.a 
> /usr/lib/x86_64-linux-gnu/libexpat.so ../../src/glu-libtess/libglu-libtess.a 
> ../../src/qhull/libqhullstatic.a -lm ../../src/semver/libsemver.a 
> ../../src/libslic3r/liblibslic3r_cgal.a /usr/lib/x86_64-linux-gnu/libgmpxx.so 
> /usr/lib/x86_64-linux-gnu/libmpfr.so /usr/lib/x86_64-linux-gnu/libgmp.so -ldl 
> /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libopenvdb.so 
> /usr/lib/x86_64-linux-gnu/libtbb.so.2 /usr/lib/x86_64-linux-gnu/libz.so 
> /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 
> /usr/lib/x86_64-linux-gnu/libHalf-2_5.so.25.0.6 -pthread 
> /usr/bin/ld: cannot find -lcereal: No such file or directory
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/slic3r-prusa_2.4.0+dfsg-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 2.4.0+dfsg-2
Done: Chow Loong Jin 

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

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

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated slic3r-prusa 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: Fri, 25 Feb 2022 16:24:09 +0800
Source: slic3r-prusa
Built-For-Profiles: noudeb
Architecture: source
Version: 2.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Chow Loong Jin 
Closes: 1005492
Changes:
 slic3r-prusa (2.4.0+dfsg-2) unstable; urgency=medium
 .
   * [ee4ac72] Stop linking against cereal library.
 It doesn't exist and it's causing FTBFS. (Closes: #1005492)
   * [8f58b90] Refresh Stop-building-test_voronoi.cpp.pa

Bug#1005633: marked as done (perl6-zef: FTBFS: Failed to create directory '/usr/lib/perl6/site/short' with mode '0o777': Failed to mkdir: Permission denied)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 11:00:20 +
with message-id 
and subject line Bug#1005633: fixed in raku-zef 0.13.7-1
has caused the Debian Bug report #1005633,
regarding perl6-zef: FTBFS: Failed to create directory 
'/usr/lib/perl6/site/short' with mode '0o777': Failed to mkdir: Permission 
denied
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p /<>/debian/build
> HOME=/<>/debian/build dh_perl6_test
>   /usr/bin/prove6 -l -v
> WARNING: unhandled Failure detected in DESTROY. If you meant to ignore it, 
> you can mark it as handled by calling .Bool, .so, .not, or .defined methods. 
> The Failure was:
> Failed to create directory '/usr/lib/perl6/site/short' with mode '0o777': 
> Failed to mkdir: Permission denied
>   in any statement_control at /usr/lib/perl6/lib/Perl6/Grammar.moarvm line 1
>   in sub MAIN at /usr/bin/prove6 line 3
>   in block  at /usr/bin/prove6 line 1
> 
> WARNING: unhandled Failure detected in DESTROY. If you meant to ignore it, 
> you can mark it as handled by calling .Bool, .so, .not, or .defined methods. 
> The Failure was:
> Failed to create directory '/usr/lib/perl6/site/short' with mode '0o777': 
> Failed to mkdir: Permission denied
>   in any statement_control at /usr/lib/perl6/lib/Perl6/Grammar.moarvm line 1
>   in sub MAIN at /usr/bin/prove6 line 3
>   in block  at /usr/bin/prove6 line 1
> 
> WARNING: unhandled Failure detected in DESTROY. If you meant to ignore it, 
> you can mark it as handled by calling .Bool, .so, .not, or .defined methods. 
> The Failure was:
> Failed to create directory '/usr/lib/perl6/site/short' with mode '0o777': 
> Failed to mkdir: Permission denied
>   in any statement_control at /usr/lib/perl6/lib/Perl6/Grammar.moarvm line 1
>   in sub MAIN at /usr/bin/prove6 line 3
>   in block  at /usr/bin/prove6 line 1
> 
> ===SORRY!=== Error while compiling 
> /usr/lib/perl6/vendor/resources/6A9DFD7D011751D33AF15CF00C4C9078C8B1D2FF
> ===SORRY!=== Error while compiling 
> /<>/vendor#sources/B4401FC2C8E71132AE0D3CE2C47A7D2FBB0D50F1 
> (App::Prove6)
> Could not find Getopt::Long in:
> inst#/<>/debian/build/.raku
> inst#/usr/lib/perl6/site
> inst#/usr/lib/perl6/vendor
> inst#/usr/lib/perl6/core
> ap#
> nqp#
> perl5#
> at /<>/vendor#sources/B4401FC2C8E71132AE0D3CE2C47A7D2FBB0D50F1 
> (App::Prove6):25
> 
> at /usr/lib/perl6/vendor/resources/6A9DFD7D011751D33AF15CF00C4C9078C8B1D2FF:3
> dh_perl6_test: error: /usr/bin/prove6 -l -v returned exit code 1
> make[1]: *** [debian/rules:22: override_dh_perl6_test] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/perl6-zef_0.9.4-1_unstable.log

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated raku-zef package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Feb 2022 18:52:21 +0100
Source: raku-zef
Binary: raku-zef
Architecture: source amd64
Version: 0.13.7-1

Bug#990691: marked as done (gpac: CVE-2020-35980)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 11:00:18 +
with message-id 
and subject line Bug#990691: fixed in gpac 2.0.0+dfsg1-1
has caused the Debian Bug report #990691,
regarding gpac: CVE-2020-35980
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.)


-- 
990691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpac
Version: 1.0.1+dfsg1-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for gpac. Unfortunately
another round of CVEs. I'm not sure if you would actually like to have
to properly separate the CVEs per bug in such massive case, as in
particular we have not checked if as well they cover completely as set
the older version. Anyway, here is the additional list of CVEs
assigned for gpac:

CVE-2020-23928[0]:
| An issue was discovered in gpac before 1.0.1. The abst_box_read
| function in box_code_adobe.c has a heap-based buffer over-read.


CVE-2020-23930[1]:
| An issue was discovered in gpac through 20200801. A NULL pointer
| dereference exists in the function nhmldump_send_header located in
| write_nhml.c. It allows an attacker to cause Denial of Service.


CVE-2020-23931[2]:
| An issue was discovered in gpac before 1.0.1. The abst_box_read
| function in box_code_adobe.c has a heap-based buffer over-read.


CVE-2020-23932[3]:
| An issue was discovered in gpac before 1.0.1. A NULL pointer
| dereference exists in the function dump_isom_sdp located in
| filedump.c. It allows an attacker to cause Denial of Service.


CVE-2020-35979[4]:
| An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is
| heap-based buffer overflow in the function gp_rtp_builder_do_avc() in
| ietf/rtp_pck_mpeg4.c.


CVE-2020-35980[5]:
| An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is a
| use-after-free in the function gf_isom_box_del() in
| isomedia/box_funcs.c.


CVE-2020-35981[6]:
| An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is an
| invalid pointer dereference in the function SetupWriters() in
| isomedia/isom_store.c.


CVE-2020-35982[7]:
| An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is an
| invalid pointer dereference in the function gf_hinter_track_finalize()
| in media_tools/isom_hinter.c.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-23928
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-23928
[1] https://security-tracker.debian.org/tracker/CVE-2020-23930
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-23930
[2] https://security-tracker.debian.org/tracker/CVE-2020-23931
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-23931
[3] https://security-tracker.debian.org/tracker/CVE-2020-23932
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-23932
[4] https://security-tracker.debian.org/tracker/CVE-2020-35979
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35979
[5] https://security-tracker.debian.org/tracker/CVE-2020-35980
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35980
[6] https://security-tracker.debian.org/tracker/CVE-2020-35981
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35981
[7] https://security-tracker.debian.org/tracker/CVE-2020-35982
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35982

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gpac
Source-Version: 2.0.0+dfsg1-1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated gpac 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: Fri, 25 Feb 2022 00:24:53 +0100
Binary: gpac gpac-dbgsym gpac-modules-base gpac-modules-base-dbgsym

Processed: Re: upowerd: cannot open '/dev/input/event3': Success

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1006368 [upower] upowerd: cannot open '/dev/input/event3': Success
Severity set to 'serious' from 'normal'

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

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

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 13:04:42 +
with message-id 
and subject line Bug#1005405: fixed in nvidia-graphics-drivers-tesla-418 
418.226.00-2
has caused the Debian Bug report #1005405,
regarding Fails to build for Linux 5.16 onward
to be marked as done.

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

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


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

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

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

Kernel code must use  instead of .

Ben.

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

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

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla-418, which is due to be installed in the Debian 
FTP archive.

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-418 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, 25 Feb 2022 13:48:18 +0100
Source: nvidia-graphics-drivers-tesla-418
Architecture: source
Version: 418.226.00-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 999670 1005405
Changes:
 nvidia-graphics-drivers-tesla-418 (418.226.00-2) unstable; urgency=medium
 .
   * Backport stdarg.h and stddef.h changes from 495.44 to fix kernel module
 build for Linux 5.16.
   * Backport pde_data changes from 510.39.01 to fix kernel module build for
 Linux 5.17.  (Closes: #1005405)
   * nvidia-tesla-418-kernel-support: Provide
 /etc/modprobe.d/nvidia-options.conf as a template taking into account the
 module renaming. This is a slave alternative of the nvidia alternative
 (470.86-1).  (Closes: #999670)
Checksums-Sha1:
 56a821c9f613618ff0abfda592354ec3d3ac7b0f 7239 
nvidia-graphics-drivers-tesla-418_418.226.00-2.dsc
 30b8afc7c819db5c47ee2fe8492313796ee1590b 196924 
nvidia-graphics-drivers-tesla-418_418.226.00-2.debian.tar.xz
 57de8377b41b68990db7a13fa744ae8a9ed0da50 7939 
nvidia-graphics-drivers-tesla-418_418.226.00-2_source.buildinfo
Checksums-Sha256:
 eafacea749b6834da7a4eb3d0da4c78e36a4f7a30dbb266a885854ed757f3750 7239 
nvidia-graphics-drivers-tesla-418_418.226.00-2.dsc
 11e518033440fdc6a66feb1e402ef290a3a994006cfd1a13426539382c057431 196924 
nvidia-graphics-drivers-tesla-418_418.226.00-2.debian.tar.xz
 a6946b639f40e43e496e0311a9b070706ca89ef9c01b10368cf9fe431cb081ac 7939 
nvidia-graphics-drivers-tesla-418_418.226.00-2_source.buildinfo
Files:
 cbb2fdfef845f9fc0bb742ba7b323c74 7239 non-free/libs optional 
nvidia-graphics-drivers-tesla-418_418.226.00-2.dsc
 9dcf1f5dda704b612def76a6b4c618e2 196924 non-free/libs optional 
nvidia-graphics-drivers-tesla-418_418.226.00-2.debian.tar.xz
 6598282e0065854cacc263099fb8957e 7939 non-free/libs optional 
nvidia-graphics-drivers-tesla-418_418.226.00-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmIY0I0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCG4zEACLUwPsTGY2aAbJT77ib5mp6audQWR7K8hu
4Dz/Y8ZVvuhERMTPECJapDS6orb+mTNbrSrjm8EATu5iKoJ3H7lduHAql9a2bmMy
VKgLd6wj9U4/7hXkzPK1+yxz4fD1lVWa1A+JgsWznilOygvS3nbl4pq3d6XjQh4O
PKQeFA+dFaPqwWWOy120yihnIxEXlmSTyS/gxPBPt9UoHbwz7KPKcH6WL4KcQ6ar
27by7gKbkh/VT6uLUmIcYjUtgBvP8CGUM

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

[Bob Friesenhahn]

On Thu, 24 Feb 2022, Dan Bungert wrote:


Hi All,

I investigated debbug 1006374 today and found that revision 16603:ba930c1fc380
of graphicsmagick appears to be causing the regression to ruby-mini-magick.  A
rebuild of graphicsmagick minus this commit allows ruby-mini-magick to pass
autopkgtest.  I did my testing against Ubuntu but expect the same results for
Debian.


This is interesting.  This sort of issue is likely dependent on the 
specific JPEG file which was used.  JPEG stores the profiles in one or 
more chunks which need to be concatenated together to produce the 
original profile.


What is the minimum that I need to do to reproduce the issue in 
GraphicsMagick?


Is the specific JPEG file which caused the issue available?

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

[GCS]

On Fri, Feb 25, 2022 at 3:45 PM Bob Friesenhahn
 wrote:
> On Thu, 24 Feb 2022, Dan Bungert wrote:
> > I investigated debbug 1006374 today and found that revision 
> > 16603:ba930c1fc380
> > of graphicsmagick appears to be causing the regression to ruby-mini-magick. 
> >  A
> > rebuild of graphicsmagick minus this commit allows ruby-mini-magick to pass
> > autopkgtest.  I did my testing against Ubuntu but expect the same results 
> > for
> > Debian.
[...]
> What is the minimum that I need to do to reproduce the issue in
> GraphicsMagick?
>
> Is the specific JPEG file which caused the issue available?
 Wild guess only, as I'm away from home right now. But that image can
be exif.jpg [1] or any other from the 'fixtures' directory.

Hope this helps,
Laszlo/GCS
[1] 
https://salsa.debian.org/ruby-team/ruby-mini-magick/-/blob/master/spec/fixtures/exif.jpg

Bug#997430: marked as done (xaw3d: FTBFS: -q: invalid option -- '.')

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 15:58:05 +0100
with message-id 
and subject line [c0llap...@yahoo.it: Bug#997430: xaw3d: FTBFS: -q: invalid 
option -- '.']
has caused the Debian Bug report #997430,
regarding xaw3d: FTBFS: -q: invalid option -- '.'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/xc/lib/Xaw3d'
> + mkdir unshared
> sed -e 's/\/\* I18n support \*\//#define XAW_INTERNATIONALIZATION/' -e 
> 's/\/\* XPM support \*\//#undef XAW_MULTIPLANE_PIXMAPS/'   -e 's/\/\* 
> gray stipples \*\//#define XAW_GRAY_BLKWHT_STIPPLES/' -e 's/\/\* arrow 
> scrollbars \*\//#define XAW_ARROW_SCROLLBARS/'Xaw3dP.h.sed > Xaw3dP.h
> rm -f AllWidgets.o unshared/AllWidgets.o
> gcc -c-I.-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L
> -D_POSIX_SOURCE -D_XOPEN_SOURCE   
>   -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO-D_REENTRANT 
> -DARROW_SCROLLBAR-g -O2 -fno-strict-aliasing -g  AllWidgets.c -o 
> unshared/AllWidgets.o
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from AllWidgets.c:30:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f AllWidgets.o
> gcc -c -g -O2 -fno-strict-aliasing -g-I.-Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO-D_REENTRANT -DARROW_SCROLLBAR  -D_REENTRANT 
> -DARROW_SCROLLBAR  -fPIC AllWidgets.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from AllWidgets.c:30:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f AsciiSink.o unshared/AsciiSink.o
> gcc -c-I.-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L
> -D_POSIX_SOURCE -D_XOPEN_SOURCE   
>   -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO-D_REENTRANT 
> -DARROW_SCROLLBAR-g -O2 -fno-strict-aliasing -g  AsciiSink.c -o 
> unshared/AsciiSink.o
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from AsciiSink.c:51:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f AsciiSink.o
> gcc -c -g -O2 -fno-strict-aliasing -g-I.-Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO-D_REENTRANT -DARROW_SCROLLBAR  -D_REENTRANT 
> -DARROW_SCRO

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

[Bob Friesenhahn]

On Fri, 25 Feb 2022, László Böszörményi (GCS) wrote:


Is the specific JPEG file which caused the issue available?

Wild guess only, as I'm away from home right now. But that image can
be exif.jpg [1] or any other from the 'fixtures' directory.

Hope this helps,
Laszlo/GCS
[1] 
https://salsa.debian.org/ruby-team/ruby-mini-magick/-/blob/master/spec/fixtures/exif.jpg


This is what I get from 'gm identify -verbose exif.jpg' for the above 
file on my system.  Is the output different/failing on the targets 
with the problem?


Image: /home/bfriesen/src/minimagick.git/spec/fixtures/exif.jpg
  Format: JPEG (Joint Photographic Experts Group JFIF format)
  Geometry: 50x81
  Class: DirectClass
  Type: true color
  Depth: 8 bits-per-pixel component
  Channel Depths:
Red:  8 bits
Green:8 bits
Blue: 8 bits
  Channel Statistics:
Red:
  Minimum: 0.00 (0.)
  Maximum: 65535.00 (1.)
  Mean:29908.26 (0.4564)
  Standard Deviation:  18652.70 (0.2846)
Green:
  Minimum: 0.00 (0.)
  Maximum: 65535.00 (1.)
  Mean:28896.32 (0.4409)
  Standard Deviation:  18685.80 (0.2851)
Blue:
  Minimum: 0.00 (0.)
  Maximum: 65535.00 (1.)
  Mean:28056.72 (0.4281)
  Standard Deviation:  18467.20 (0.2818)
  Resolution: 72x72 pixels
  Filesize: 14.7Ki
  Interlace: No
  Orientation: Unknown
  Background Color: white
  Border Color: #DFDFDF
  Matte Color: #BDBDBD
  Page geometry: 50x81+0+0
  Compose: Over
  Dispose: Undefined
  Iterations: 0
  Compression: JPEG
  JPEG-Quality: 93
  JPEG-Colorspace: 2
  JPEG-Colorspace-Name: RGB
  JPEG-Sampling-factors: 1x2,1x1,1x1
  Signature: 32e486a5139c320c9eff1667ee4e9261d8eec83c51fe408913fa22eb0d87dcfc
  Profile-EXIF: 7576 bytes
Make: samsung
Model: SM-G925F
Orientation: 0
X Resolution: 72/1
Y Resolution: 72/1
Resolution Unit: 0
Software: GIMP 2.8.10
Date Time: 2016:11:12 16:00:01
Y Cb Cr Positioning: 1
Exif Offset: 200
Exposure Time: 1/25
F Number: 19/10
Exposure Program: 2
ISO Speed Ratings: 200
Exif Version: 0220
Date Time Original: 2016:11:12 09:17:56
Date Time Digitized: 2016:11:12 09:17:56
Shutter Speed Value: 464/100
Aperture Value: 185/100
Brightness Value: 30/100
Exposure Bias Value: 0/10
Max Aperture Value: 185/100
Metering Mode: 2
Flash: 0
Focal Length: 430/100
Maker Note: 
\007\000\001\000\007\000\004\000\000\100\002\000\004\000\001\000\000\000\000
 
\001\000\014\000\004\000\001\000\000\000\000\000\000\000\020\000\005\000\001\000\000\000Z\000\000\000@\000\004\000\001\000\000\000\000\000\000\000P\000\004\000\001\000\000\000\001\000\000\000\000\001\003\000\001\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
User Comment: 
\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
Flash Pix Version: 0100
Color Space: 1
Exif Image Width: 1459
Exif Image Length: 2360
Exposure Mode: 0
White Balance: 0
Focal Length In35mm Film: 28
Scene Capture Type: 0
Image UniqueID: A16LSIA00VM A16LSIL02SM\012
  Profile-XMP: 4102 bytes
  Tainted: False
  Elapsed Time: 0m:0.000187s
  Pixels Per Second: 20.6Mi

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt

Processed: bug 1006368 is forwarded to https://gitlab.freedesktop.org/upower/upower/-/issues/174 ...

[Debian Bug Tracking System]

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

> # Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368#10
> forwarded 1006368 https://gitlab.freedesktop.org/upower/upower/-/issues/174
Bug #1006368 [upower] upowerd: cannot open '/dev/input/event3': Success
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/upower/upower/-/issues/174'.
> # 
> https://gitlab.freedesktop.org/upower/upower/-/commit/72469426b737f1398651efc360f62a86e3b2633b
> tags 1006368 + fixed-upstream
Bug #1006368 [upower] upowerd: cannot open '/dev/input/event3': Success
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

[GCS]

On Fri, Feb 25, 2022 at 4:35 PM Bob Friesenhahn
 wrote:
> On Fri, 25 Feb 2022, László Böszörményi (GCS) wrote:
> > Wild guess only, as I'm away from home right now. But that image can
> > be exif.jpg [1] or any other from the 'fixtures' directory.
> > [1] 
> > https://salsa.debian.org/ruby-team/ruby-mini-magick/-/blob/master/spec/fixtures/exif.jpg
>
> This is what I get from 'gm identify -verbose exif.jpg' for the above
> file on my system.  Is the output different/failing on the targets
> with the problem?
 This should be it. Is your GM the latest version from Mercurial?

> Image: /home/bfriesen/src/minimagick.git/spec/fixtures/exif.jpg
>  Exif Version: 0220
>  Date Time Original: 2016:11:12 09:17:56
>  Flash: 0
 Package ruby-mini-magick check tree values: EXIF:Flash,
DateTimeOriginal and ExifVersion. With GM 1.3.37 it succeeds and gets
real values in order 0, a string and 0220 just like in your dump. But
with the mentioned GM commit the results are in order "", nil and nil.
Maybe the GM output or its variable types changed somehow and now
ruby-mini-magick can't parse that? Needs more investigation. I think
tomorrow in the evening (CET) I will arrive back home and will try to
support you with more details.

Regards,
Laszlo/GCS

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

[Bob Friesenhahn]

On Fri, 25 Feb 2022, László Böszörményi (GCS) wrote:


On Fri, Feb 25, 2022 at 4:35 PM Bob Friesenhahn
 wrote:

On Fri, 25 Feb 2022, László Böszörményi (GCS) wrote:

Wild guess only, as I'm away from home right now. But that image can
be exif.jpg [1] or any other from the 'fixtures' directory.
[1] 
https://salsa.debian.org/ruby-team/ruby-mini-magick/-/blob/master/spec/fixtures/exif.jpg


This is what I get from 'gm identify -verbose exif.jpg' for the above
file on my system.  Is the output different/failing on the targets
with the problem?

This should be it. Is your GM the latest version from Mercurial?


Yes it is.


Image: /home/bfriesen/src/minimagick.git/spec/fixtures/exif.jpg
 Exif Version: 0220
 Date Time Original: 2016:11:12 09:17:56
 Flash: 0

Package ruby-mini-magick check tree values: EXIF:Flash,
DateTimeOriginal and ExifVersion. With GM 1.3.37 it succeeds and gets
real values in order 0, a string and 0220 just like in your dump. But
with the mentioned GM commit the results are in order "", nil and nil.
Maybe the GM output or its variable types changed somehow and now
ruby-mini-magick can't parse that? Needs more investigation. I think
tomorrow in the evening (CET) I will arrive back home and will try to
support you with more details.


There is dependency on the JPEG library so some change in the JPEG 
library could impact code which works "fine" on some other system.


I am using Ubuntu 20.04 LTS and the JPEG that comes with that OS.

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

[Bob Friesenhahn]

On Fri, 25 Feb 2022, Bob Friesenhahn wrote:


There is dependency on the JPEG library so some change in the JPEG library 
could impact code which works "fine" on some other system.


I am using Ubuntu 20.04 LTS and the JPEG that comes with that OS.


I made a mis-statement.  For this particular system I am testing on I 
am using a private build of TurboJPEG which was built and installed on 
December 26th.  This still appears to be lastest git code.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt

Processed: Re: [Pkg-javascript-devel] Bug#1006359: node-eslint-utils: Update to node-dot-prop 7

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1006359 [node-eslint-utils] node-eslint-utils: Update to node-dot-prop 7
Severity set to 'important' from 'serious'

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

Bug#1006359: [Pkg-javascript-devel] Bug#1006359: node-eslint-utils: Update to node-dot-prop 7

[Jonas Smedegaard]

Control: severity -1 important

Quoting Yadd (2022-02-24 09:21:29)
> I just released node-dot-prop 7.2.0. API changed. Here is a trivial 
> patch that fixes test.

Thanks.  Appreciated!

Will postpone applying the patch, however, until it can be verified that 
it works: Currently testsuite is not checked due to Node.js module esm 
missing in Debian.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Processed: Bug#1006078 marked as pending in node-eslint-utils

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006078 [src:node-eslint-utils] node-eslint-utils: FTBFS: Function 
'getFunctionNameWithKind' has a complexity of 20. Maximum allowed is 16.
Added tag(s) pending.

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

Bug#1006078: marked as pending in node-eslint-utils

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-eslint-utils/-/commit/00cade41c7fa085d57ef670f407c7ec75faf83f6


tighten build-dependency on node-mysticatea-eslint-plugin; drop patch 2002 to 
use older mysicatea plugin; stop explicitly stop breaking older nodejs; closes: 
bug#1006078, thanks to Lucas Nussbaum


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006078

Bug#1006078: marked as done (node-eslint-utils: FTBFS: Function 'getFunctionNameWithKind' has a complexity of 20. Maximum allowed is 16.)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 17:18:48 +
with message-id 
and subject line Bug#1006078: fixed in node-eslint-utils 3.0.0-1
has caused the Debian Bug report #1006078,
regarding node-eslint-utils: FTBFS: Function 'getFunctionNameWithKind' has a 
complexity of 20. Maximum allowed is 16.
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.)


-- 
1006078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-eslint-utils
Version: 2.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> eslint --format tap src test
> TAP version 13
> 1..25
> ok 1 - /<>/src/find-variable.js
> ok 2 - /<>/src/get-function-head-location.js
> ok 3 - /<>/src/get-function-name-with-kind.js
>   ---
>   message: >-
> Function 'getFunctionNameWithKind' has a complexity of 20. Maximum 
> allowed is
> 16.
>   severity: warning
>   data:
> line: 8
> column: 8
> ruleId: complexity
>   ...
> ok 4 - /<>/src/get-innermost-scope.js
> ok 5 - /<>/src/get-property-name.js
> not ok 6 - /<>/src/get-static-value.js
>   ---
>   message: '''global'' is already defined as a built-in global variable.'
>   severity: error
>   data:
> line: 1
> column: 32
> ruleId: no-redeclare
>   ...
> ok 7 - /<>/src/get-string-if-constant.js
> ok 8 - /<>/src/has-side-effect.js
> ok 9 - /<>/src/index.js
> ok 10 - /<>/src/is-parenthesized.js
> ok 11 - /<>/src/pattern-matcher.js
> ok 12 - /<>/src/reference-tracker.js
> ok 13 - /<>/src/token-predicate.js
> ok 14 - /<>/test/find-variable.js
> ok 15 - /<>/test/get-function-head-location.js
> ok 16 - /<>/test/get-function-name-with-kind.js
> ok 17 - /<>/test/get-innermost-scope.js
> ok 18 - /<>/test/get-property-name.js
> ok 19 - /<>/test/get-static-value.js
> ok 20 - /<>/test/get-string-if-constant.js
> ok 21 - /<>/test/has-side-effect.js
> ok 22 - /<>/test/is-parenthesized.js
> ok 23 - /<>/test/pattern-matcher.js
> ok 24 - /<>/test/reference-tracker.js
> ok 25 - /<>/test/token-predicate.js
> 
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-eslint-utils_2.1.0-3_unstable.log

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-eslint-utils 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: Fri, 25 Feb 2022 18:03:13 +0100
Source: node-eslint-utils
Architecture: source
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 1006078
Changes:
 node-eslint-utils (3.0.0-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release
 .
   [ Jonas Smedegaard ]
   * generate documentation with cmark-gfm (not pandoc);
 fix clean generated documentation;
 build-depend on cmark-gfm (not pandoc)
   * tighten build-dependency on node-mysticatea-eslint-plugin;
 drop patch 2002 to use older mysicatea plugin;
 stop explicitly stop breaking older nodejs;
 closes: bug#1006078, thanks to Lucas Nussbaum
   * stop build-depend on nodejs: not used explicitly during build
   * update test coverage
   * update git-buildpackage config:
 + use DE

Bug#1006451: minify-maven-plugin: should not be part of a stable release unless actually used

[Thorsten Glaser]

Package: libminify-maven-plugin-java
Version: 1.7.4-1.1
Severity: serious
Justification: other
X-Debbugs-Cc: t...@mirbsd.de

minify-maven-plugin is currently only in Debian to satisfy a Build-Depends
of guacamole-client on libminify-maven-plugin-java (its binary package).

However, guacamole-client is in bad shape and has last worked in stretch;
newer guacamole-client versions will require minify-maven-plugin 2.0.1
anyway, so this version is not necessary to carry around.


-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libminify-maven-plugin-java depends on:
ii  libclosure-compiler-java  20130227+dfsg1-10.1
ii  libprotobuf-java  3.12.4-1
ii  yui-compressor2.4.8-2.1

libminify-maven-plugin-java recommends no packages.

libminify-maven-plugin-java suggests no packages.

-- no debconf information

Bug#1006058: marked as done (node-eslint-plugin-es: FTBFS: message: Definition for rule '@mysticatea/prettier' was not found.)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 17:50:24 +
with message-id 
and subject line Bug#1006058: fixed in node-eslint-plugin-es 4.1.0~ds1-4
has caused the Debian Bug report #1006058,
regarding node-eslint-plugin-es: FTBFS: message: Definition for rule 
'@mysticatea/prettier' was not found.
to be marked as done.

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

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


-- 
1006058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-eslint-plugin-es
Version: 4.1.0~ds1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> eslint --format tap lib tests scripts
> TAP version 13
> 1..252
> ok 1 - /<>/lib/configs/no-new-in-es2015.js
> ok 2 - /<>/lib/configs/no-new-in-es2016.js
> ok 3 - /<>/lib/configs/no-new-in-es2017.js
> ok 4 - /<>/lib/configs/no-new-in-es2018.js
> ok 5 - /<>/lib/configs/no-new-in-es2019.js
> ok 6 - /<>/lib/configs/no-new-in-es2020.js
> ok 7 - /<>/lib/configs/no-new-in-es5.js
> ok 8 - /<>/lib/configs/no-new-in-esnext.js
> ok 9 - /<>/lib/configs/restrict-to-es2015.js
> ok 10 - /<>/lib/configs/restrict-to-es2016.js
> ok 11 - /<>/lib/configs/restrict-to-es2017.js
> ok 12 - /<>/lib/configs/restrict-to-es2018.js
> ok 13 - /<>/lib/configs/restrict-to-es2019.js
> ok 14 - /<>/lib/configs/restrict-to-es3.js
> ok 15 - /<>/lib/configs/restrict-to-es5.js
> ok 16 - /<>/lib/index.js
> ok 17 - /<>/lib/rules/no-accessor-properties.js
> ok 18 - /<>/lib/rules/no-array-from.js
> ok 19 - /<>/lib/rules/no-array-isarray.js
> ok 20 - /<>/lib/rules/no-array-of.js
> not ok 21 - /<>/lib/rules/no-arrow-functions.js
>   ---
>   message: Definition for rule '@mysticatea/prettier' was not found.
>   severity: error
>   data:
> line: 56
> column: 17
> ruleId: '@mysticatea/prettier'
>   messages:
> - message: Definition for rule '@mysticatea/prettier' was not found.
>   severity: error
>   data:
> line: 64
> column: 17
> ruleId: '@mysticatea/prettier'
>   ...
> ok 22 - /<>/lib/rules/no-async-functions.js
> ok 23 - /<>/lib/rules/no-async-iteration.js
> ok 24 - /<>/lib/rules/no-atomics.js
> ok 25 - /<>/lib/rules/no-bigint.js
> ok 26 - /<>/lib/rules/no-binary-numeric-literals.js
> ok 27 - /<>/lib/rules/no-block-scoped-functions.js
> ok 28 - /<>/lib/rules/no-block-scoped-variables.js
> ok 29 - /<>/lib/rules/no-classes.js
> ok 30 - /<>/lib/rules/no-computed-properties.js
> ok 31 - /<>/lib/rules/no-date-now.js
> ok 32 - /<>/lib/rules/no-default-parameters.js
> ok 33 - /<>/lib/rules/no-destructuring.js
> ok 34 - /<>/lib/rules/no-dynamic-import.js
> ok 35 - /<>/lib/rules/no-exponential-operators.js
> ok 36 - /<>/lib/rules/no-export-ns-from.js
> ok 37 - /<>/lib/rules/no-for-of-loops.js
> ok 38 - /<>/lib/rules/no-generators.js
> ok 39 - /<>/lib/rules/no-global-this.js
> ok 40 - /<>/lib/rules/no-import-meta.js
> ok 41 - /<>/lib/rules/no-json-superset.js
> ok 42 - /<>/lib/rules/no-json.js
> ok 43 - /<>/lib/rules/no-keyword-properties.js
> ok 44 - /<>/lib/rules/no-logical-assignment-operators.js
> ok 45 - /<>/lib/rules/no-malformed-template-literals.js
> ok 46 - /<>/lib/rules/no-map.js
> ok 47 - /<>/lib/rules/no-math-acosh.js
> ok 48 - /<>/lib/rules/no-math-asinh.js
> ok 49 - /<>/lib/rules/no-math-atanh.js
> ok 50 - /<>/lib/rules/no-math-cbrt.js
> ok 51 - /<>/lib/rules/no-math-clz32.js
> ok 52 - /<>/lib/rules/no-math-cosh.js
> ok 53 - /<>/lib/rules/no-math-expm1.js
> ok 54 - /<>/lib/rules/no-math-fround.js
> ok 55 - /<>/lib/rules/no-math-hypot.js
> ok 56 - /<>/lib/rules/no-math-imul.js
> ok 57 - /<>/lib/rules/no-math-log10.js
> ok 58 - /<>/lib/rules/no-math-log1p.js
> ok 59 - /<>/lib/rules/no-math-log2.js
> ok 60 - /<>/lib/rules/no-math-sign.js
> ok 61 - /<>/lib/rules/no-math-sinh.js
> ok 62 - /<>/lib/rules/no-math-tanh.js
> ok 63 - /<>/lib/rules/no-math-trunc.js
> ok 64 - /<>/lib/rules/no-modules.js
> ok 65 - /<>/lib/rules/no-new-target.js
> ok 66 - /<>/lib/rules/no-nullish-coalescing-operators.js
> ok 67 - /<>/lib/rules/no-number-epsilon.js
> ok 68 - /<>/lib/rules/no-number-isfinite.js
> ok 69 - /<>/lib/rules/no-number-isinteger.js
> ok 70 - /<>/lib/rules/no-number-isnan.js
> ok 71 - /<>/lib/rules/no-number-issafeinteger.js
> ok 72 - /<>/lib/rules/no-number-maxsafeinteger.js
> ok 73 - /<>/lib/rules/no-number-minsafeinteger.js
> ok 74 - /<>/lib/rules/no-number-parsefloat.js
> ok 75 - /<>/lib/rules/no-number-parseint.js
> ok 76 - /<>/lib/rules/no-numeric-separators.js
> ok 77 

Bug#1006065: marked as pending in node-eslint-plugin-eslint-plugin

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-eslint-plugin-eslint-plugin/-/commit/62b96848d82c5712b5a7eb74e0e834c3ecd51760


fix lint-check only visible files; closes: bug#1006065, thanks to Lucas Nussbaum


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006065

Processed: Bug#1006065 marked as pending in node-eslint-plugin-eslint-plugin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006065 [src:node-eslint-plugin-eslint-plugin] 
node-eslint-plugin-eslint-plugin: FTBFS: ESLint couldn't find the config 
"not-an-aardvark/node" to extend from. Please check that the name of the config 
is correct.
Added tag(s) pending.

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

Bug#1006065: marked as done (node-eslint-plugin-eslint-plugin: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from. Please check that the name of the config is correct.)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 18:20:08 +
with message-id 
and subject line Bug#1006065: fixed in node-eslint-plugin-eslint-plugin 
2.3.0+~0.3.0-4
has caused the Debian Bug report #1006065,
regarding node-eslint-plugin-eslint-plugin: FTBFS: ESLint couldn't find the 
config "not-an-aardvark/node" to extend from. Please check that the name of the 
config is correct.
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.)


-- 
1006065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-eslint-plugin-eslint-plugin
Version: 2.3.0+~0.3.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> eslint --format tap Xcomposer
> TAP version 13
> 1..2
> ok 1 - /<>/Xcomposer/lib/rule-composer.js
> ok 2 - /<>/Xcomposer/tests/lib/rule-composer.js
> 
> eslint --format tap . --ignore-pattern '!.*'
> 
> Oops! Something went wrong! :(
> 
> ESLint: 6.4.0.
> 
> ESLint couldn't find the config "not-an-aardvark/node" to extend from. Please 
> check that the name of the config is correct.
> 
> The config "not-an-aardvark/node" was referenced from the config file in 
> "/<>/.pc/2002_avoid_eslint-plugin-self.patch/.eslintrc.yml".
> 
> If you still have problems, please stop by https://gitter.im/eslint/eslint to 
> chat with the team.
> 
> make[1]: *** [debian/rules:38: override_dh_auto_test] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-eslint-plugin-eslint-plugin_2.3.0+~0.3.0-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-eslint-plugin-eslint-plugin
Source-Version: 2.3.0+~0.3.0-4
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated 
node-eslint-plugin-eslint-plugin 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: Fri, 25 Feb 2022 19:02:38 +0100
Source: node-eslint-plugin-eslint-plugin
Architecture: source
Version: 2.3.0+~0.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 1006065
Changes:
 node-eslint-plugin-eslint-plugin (2.3.0+~0.3.0-4) unstable; urgency=medium
 .
   * update git-buildpackage config:
 + use DEP-14 branch names debian/latest upstream/latest
   (not debian/master upstream)
 + add usage comment
   * fix lint-check only visible files;
 closes: bug#1006065, thanks to Lucas Nussbaum
   * generate documentation with cmark-gfm (not pandoc);
 build-depend on cmark-gfm (not pandoc)
   * declare compliance with Debian Policy 4.6.0
   * update copyright info:
 + use Reference field (not License-Reference);
   tighten lintian overrides
 + update coverage
   * simplify source helper script copyright-check
Checksums-Sha1:
 6938136a194c845ec3d5875f317e906e73528774 3035 
node-eslint-plugin-eslint-plugin_2.3.0+~0.3.0-4.dsc
 211464020333995b8240f1329606e140d2702807 6932 
node-eslint-plugin-eslint-plugin_2.3.0+~0.3.0-4.debian.tar.xz
 8193922e8c969a1d917cf625ea7fd1f72038624c 12378 
node-eslint-plugin-eslint-plugin_2.3.0+~0.3.0-4_amd64.buildinfo
Checksums-Sha256:
 d7c3bf2d4c0e06400e8c6cb1eccf9fe9b3680879c7b72e392c81044e560f3898 3035 
node-eslint-plugin-eslint-plugin_2.3.0+~0.3.0-4.dsc
 98fd3583813c8caa45646e252e809510c178e4d6b79b6256fe29c394af5c5007 6932 
node-eslint

Bug#984352: marked as done (srt: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 18:52:36 +
with message-id 
and subject line Bug#984352: fixed in srt 1.4.2-2
has caused the Debian Bug report #984352,
regarding srt: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:srt
Version: 1.4.2-1.3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

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

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. 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://people.debian.org/~doko/logs/20210228/filtered/gcc11/srt_1.4.2-1.3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  | 
  ^
/<>/srtcore/sync.h:182:94: error: ‘::min’ has not been declared; 
did you mean ‘std::min’?
  182 | static inline ATR_CONSTEXPR TimePoint min() { return 
TimePoint(numeric_limits::min()); }
  | 
 ^~~
  | 
 std::min
In file included from /usr/include/c++/11/algorithm:62,
 from /<>/srtcore/utilities.h:103,
 from /<>/srtcore/api.cpp:62:
/usr/include/c++/11/bits/stl_algo.h:3455:5: note: ‘std::min’ declared here
 3455 | min(initializer_list<_Tp> __l, _Compare __comp)
  | ^~~
In file included from /<>/srtcore/common.h:70,
 from /<>/srtcore/packet.h:57,
 from /<>/srtcore/api.h:62,
 from /<>/srtcore/api.cpp:64:
/<>/srtcore/sync.h: In static member function ‘static constexpr 
srt::sync::TimePoint srt::sync::TimePoint::max()’:
/<>/srtcore/sync.h:183:68: error: ‘numeric_limits’ was not 
declared in this scope
  183 | static inline ATR_CONSTEXPR TimePoint max() { return 
TimePoint(numeric_limits::max()); }
  |
^~
/<>/srtcore/sync.h:183:94: error: ‘::max’ has not been declared; 
did you mean ‘std::max’?
  183 | static inline ATR_CONSTEXPR TimePoint max() { return 
TimePoint(numeric_limits::max()); }
  | 
 ^~~
  | 
 std::max
In file included from /usr/include/c++/11/algorithm:62,
 from /<>/srtcore/utilities.h:103,
 from /<>/srtcore/api.cpp:62:
/usr/include/c++/11/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here
 3467 | max(initializer_list<_Tp> __l, _Compare __comp)
  | ^~~
In file included from /<>/srtcore/common.h:70,
 from /<>/srtcore/packet.h:57,
 from /<>/srtcore/api.h:62,
 from /<>/srtcore/api.cpp:64:
/<>/srtcore/sync.h:183:67: error: expected primary-expression 
before ‘(’ token
  183 | static inline ATR_CONSTEXPR TimePoint max() { return 
TimePoint(numeric_limits::max()); }
  |   ^
/<>/srtcore/sync.h:183:91: error: expected primary-expression 
bef

Bug#1006458: src:sslsplit: fails to migrate to testing for too long: FTBFS on amd64

[Paul Gevers]

Source: sslsplit
Version: 0.5.5-1
Severity: serious
Control: close -1 0.5.5-2
Tags: sid bookworm ftbfs
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:sslsplit has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on amd64 the buildd.


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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:sslsplit: fails to migrate to testing for too long: FTBFS on amd64

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.5.5-2
Bug #1006458 [src:sslsplit] src:sslsplit: fails to migrate to testing for too 
long: FTBFS on amd64
Marked as fixed in versions sslsplit/0.5.5-2.
Bug #1006458 [src:sslsplit] src:sslsplit: fails to migrate to testing for too 
long: FTBFS on amd64
Marked Bug as done

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

Bug#1006459: surf: flaky autopkgtest on arm64: too short timeout?

[Paul Gevers]

Source: surf
Version: 2.1+git20210719-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on arm64 
because it was showing up as a regression for the upload of autopkgtest. 
I noticed that the test regularly fails. As the test specifies a 
timeout, I wonder if that's just to short in some cases. I'm not 
excluding other causes.


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 causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/arm64/s/surf/19548818/log.gz

autopkgtest [11:15:07]: test command3: timeout 1m xvfb-run 
debian/tests/test_text.sh

autopkgtest [11:15:07]: test command3: [---

(surf:4981): dbind-WARNING **: 03:15:07.813: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.a11y.Bus was not provided by any .service files


(WebKitWebProcess:4997): dbind-WARNING **: 03:15:07.973: AT-SPI: Error 
retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files

Could not read style file: /home/debci/.surf/styles/default.css
Tesseract Open Source OCR Engine v4.1.1 with Leptonica
Warning: Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 123
autopkgtest [11:16:07]: test command3: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006068: marked as done (node-mysticatea-eslint-plugin: FTBFS: message: Definition for rule '@mysticatea/prettier' was not found.)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 21:30:01 +0100
with message-id <164582100151.2566810.16879327728515921...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#1006068: 
node-mysticatea-eslint-plugin: FTBFS: message: Definition for rule 
'@mysticatea/prettier' was not found.
has caused the Debian Bug report #1006068,
regarding node-mysticatea-eslint-plugin: FTBFS: message: Definition for rule 
'@mysticatea/prettier' was not found.
to be marked as done.

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

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


-- 
1006068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-mysticatea-eslint-plugin
Version: 11.0.0~ds-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> NO_COLOR=1 NODE_PATH=debian/node_modules eslint --format tap lib scripts tests
> TAP version 13
> 1..61
> ok 1 - /<>/lib/configs/+browser.js
> ok 2 - /<>/lib/configs/+eslint-plugin.js
> ok 3 - /<>/lib/configs/+modules.js
> ok 4 - /<>/lib/configs/+node.js
> ok 5 - /<>/lib/configs/_browser-globals.js
> ok 6 - /<>/lib/configs/_mocha.js
> ok 7 - /<>/lib/configs/_special.js
> ok 8 - /<>/lib/configs/_ts.js
> ok 9 - /<>/lib/configs/_vue.js
> ok 10 - /<>/lib/configs/es2015.js
> ok 11 - /<>/lib/configs/es2016.js
> ok 12 - /<>/lib/configs/es2017.js
> ok 13 - /<>/lib/configs/es2018.js
> ok 14 - /<>/lib/configs/es2019.js
> ok 15 - /<>/lib/configs/es5.js
> ok 16 - /<>/lib/configs.js
> ok 17 - /<>/lib/foreign-rules/eslint-comments.js
> ok 18 - /<>/lib/foreign-rules/eslint-plugin.js
> ok 19 - /<>/lib/foreign-rules/node.js
> ok 20 - /<>/lib/foreign-rules/prettier.js
> ok 21 - /<>/lib/foreign-rules/ts.js
> ok 22 - /<>/lib/foreign-rules/vue.js
> ok 23 - /<>/lib/processors/vue.js
> ok 24 - /<>/lib/processors.js
> ok 25 - /<>/lib/rules/arrow-parens.js
> ok 26 - /<>/lib/rules/block-scoped-var.js
> ok 27 - /<>/lib/rules/no-instanceof-array.js
> ok 28 - /<>/lib/rules/no-instanceof-wrapper.js
> ok 29 - /<>/lib/rules/no-literal-call.js
> ok 30 - /<>/lib/rules/no-this-in-static.js
> ok 31 - /<>/lib/rules/no-use-ignored-vars.js
> not ok 32 - /<>/lib/rules/no-useless-rest-spread.js
>   ---
>   message: Definition for rule '@mysticatea/prettier' was not found.
>   severity: error
>   data:
> line: 134
> column: 21
> ruleId: '@mysticatea/prettier'
>   messages:
> - message: Definition for rule '@mysticatea/prettier' was not found.
>   severity: error
>   data:
> line: 138
> column: 21
> ruleId: '@mysticatea/prettier'
>   ...
> not ok 33 - /<>/lib/rules/prefer-for-of.js
>   ---
>   message: Definition for rule '@mysticatea/prettier' was not found.
>   severity: error
>   data:
> line: 118
> column: 5
> ruleId: '@mysticatea/prettier'
>   messages:
> - message: Definition for rule '@mysticatea/prettier' was not found.
>   severity: error
>   data:
> line: 189
> column: 5
> ruleId: '@mysticatea/prettier'
>   ...
> ok 34 - /<>/lib/rules.js
> ok 35 - /<>/lib/utils.js
> ok 36 - /<>/scripts/generate-browser-globals.js
> ok 37 - /<>/scripts/generate-configs.js
> ok 38 - /<>/scripts/generate-rules.js
> not ok 39 - /<>/tests/lib/configs/_rules.js
>   ---
>   message: '"eslint/lib/config/config-validator" is not found.'
>   severity: error
>   data:
> line: 7
> column: 27
> ruleId: '@mysticatea/node/no-missing-require'
>   messages:
> - message: '"eslint/lib/config/environments" is not found.'
>   severity: error
>   data:
> line: 8
> column: 30
> ruleId: '@mysticatea/node/no-missing-require'
> - message: '"eslint/lib/built-in-rules-index" is not found.'
>   severity: error
>   data:
> line: 9
> column: 28
> ruleId: '@mysticatea/node/no-missing-require'
>   ...
> ok 40 - /<>/tests/lib/configs/browser.js
> ok 41 - /<>/tests/lib/configs/es2015.js
> ok 42 - /<>/tests/lib/configs/es2016.js
> ok 43 - /<>/tests/lib/configs/es2017.js
> ok 44 - /<>/tests/lib/configs/es2018.js
> ok 45 - /<>/tests/lib/configs/es5.js
> ok 46 - /<>/tests/lib/configs/eslint-plugin.js
> ok 47 - /<>/tests/lib/configs/mocha.js
> ok 48 - /<>/tests/lib/configs/modules.js
> ok 49 - /<>/tests/lib/configs/node.js
> ok 50 - /<>/tests/lib/configs/special.js
> ok 51 - /<>/tests/lib/configs/ts.js
> ok 52 - /<>/tests/lib/configs/vue.js
> ok 53 - /<>/tests/lib/rules/arrow-parens.js
> ok 54 - /<>/tests/lib/rules/block-scope

Processed: reassign bug from ftpmasters to package

[Debian Bug Tracking System]

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

> reassign 1006139 libdeflate
Bug #1006139 {Done: Scott Kitterman } [ftp.debian.org] 
RM: libdeflate [armhf] -- ROM; does not seem suitable for armhf 'baseline'
Bug reassigned from package 'ftp.debian.org' to 'libdeflate'.
Ignoring request to alter found versions of bug #1006139 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1006139 to the same values 
previously set
> reopen 1006139
Bug #1006139 {Done: Scott Kitterman } [libdeflate] RM: 
libdeflate [armhf] -- ROM; does not seem suitable for armhf 'baseline'
Bug reopened
Ignoring request to alter fixed versions of bug #1006139 to the same values 
previously set
> severity 1006139 serious
Bug #1006139 [libdeflate] RM: libdeflate [armhf] -- ROM; does not seem suitable 
for armhf 'baseline'
Severity set to 'serious' from 'normal'
> tags 1006139 -moreinfo +bookworm +sid
Bug #1006139 [libdeflate] RM: libdeflate [armhf] -- ROM; does not seem suitable 
for armhf 'baseline'
Removed tag(s) moreinfo.
Bug #1006139 [libdeflate] RM: libdeflate [armhf] -- ROM; does not seem suitable 
for armhf 'baseline'
Added tag(s) bookworm.
Bug #1006139 [libdeflate] RM: libdeflate [armhf] -- ROM; does not seem suitable 
for armhf 'baseline'
Added tag(s) sid.
> retitle 1006139 libdeflate FTBFS on armhf
Bug #1006139 [libdeflate] RM: libdeflate [armhf] -- ROM; does not seem suitable 
for armhf 'baseline'
Changed Bug title to 'libdeflate FTBFS on armhf' from 'RM: libdeflate [armhf] 
-- ROM; does not seem suitable for armhf 'baseline''.
> thanks
Stopping processing here.

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

Bug#1006463: openssh-client: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY"

[Axel Beckert]

Package: openssh-server
Version: 1:8.9p1-2
Severity: grave

Hi,

TL;DR: OpenSSH clients (at least 8.8 and 8.9) can't talk with OpenSSH
8.9 servers in some cases (common property so far: if and only if it's
i386 on the server-side), but 8.9 clients can talk with 8.8 servers in
the same cases (i.e. i386 on the server-side) after downgrading the
server-side. i386 OpenSSH clients can't talk to i386 8.9 servers either.

Full details:

Since I've upgraded my Debian Unstable boxes to 1:8.9p1-2, I can't login
from my desktop (Sid amd64) to at least two hosts (both Sid i386)
anymore:

~ → ssh -v 192.168.1.179
OpenSSH_8.9p1 Debian-2, OpenSSL 1.1.1m  14 Dec 2021
debug1: Reading configuration data /home/abe/.ssh/config
debug1: /home/abe/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.179 [192.168.1.179] port 22.
debug1: Connection established.
debug1: identity file /home/abe/.ssh/id_rsa type 0
debug1: identity file /home/abe/.ssh/id_rsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa type 2
debug1: identity file /home/abe/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519 type 3
debug1: identity file /home/abe/.ssh/id_ed25519-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_xmss type -1
debug1: identity file /home/abe/.ssh/id_xmss-cert type -1
debug1: identity file /home/abe/.ssh/id_dsa type -1
debug1: identity file /home/abe/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Debian-2
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 
Debian-2
debug1: compat_banner: match: OpenSSH_8.9p1 Debian-2 pat OpenSSH* compat 
0x0400
debug1: Authenticating to 192.168.1.179:22 as 'abe'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or 
directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection reset by 192.168.1.179 port 22

~ → ssh -v 192.168.1.108
OpenSSH_8.9p1 Debian-2, OpenSSL 1.1.1m  14 Dec 2021
debug1: Reading configuration data /home/abe/.ssh/config
debug1: /home/abe/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.108 [192.168.1.108] port 22.
debug1: Connection established.
debug1: identity file /home/abe/.ssh/id_rsa type 0
debug1: identity file /home/abe/.ssh/id_rsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa type 2
debug1: identity file /home/abe/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519 type 3
debug1: identity file /home/abe/.ssh/id_ed25519-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_xmss type -1
debug1: identity file /home/abe/.ssh/id_xmss-cert type -1
debug1: identity file /home/abe/.ssh/id_dsa type -1
debug1: identity file /home/abe/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Debian-2
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 
Debian-2
debug1: compat_banner: match: OpenSSH_8.9p1 Debian-2 pat OpenSSH* compat 
0x0400
debug1: Authenticating to 192.168.1.108:22 as 'abe'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or 
directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
ssh_dispatch_run_fatal: Connection to 192.168.1.108 port 22: Broken pipe

I though still can login on an Sid amd64 running VM:

~ → ssh -v 192.0.2.21
OpenSSH_8.9p1 Debian-2, OpenSSL 1.1.1m  14 Dec 2021
debug1: Reading configuration data /home/abe/.ssh/config
debug1: /home/abe/.ssh/config line 1: A

Processed: retitle 1006463 to openssh-server: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY"

[Debian Bug Tracking System]

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

> # I initially started to write the bug report against the client, but it's 
> actually an issue of the server-side. Forgot to fix the subject before 
> sending it.
> retitle 1006463 openssh-server: Can't login on two i386 boxes anymore since 
> the server-side has been upgraded to 8.9p1: "debug1: expecting 
> SSH2_MSG_KEX_ECDH_REPLY"
Bug #1006463 [openssh-server] openssh-client: Can't login on two i386 boxes 
anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
Changed Bug title to 'openssh-server: Can't login on two i386 boxes anymore 
since the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"' from 'openssh-client: Can't login on two i386 boxes 
anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"'.
> thanks
Stopping processing here.

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

Bug#1006463: openssh-server: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY" -> also affects armhf

[Axel Beckert]

Control: retitle -1 openssh-server: Can't login on any 32-bit box anymore after 
the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"

Hi,

Axel Beckert wrote:
> TL;DR: OpenSSH clients (at least 8.8 and 8.9) can't talk with OpenSSH
> 8.9 servers in some cases (common property so far: if and only if it's
> i386 on the server-side),

Found another case, this time Sid armhf (a Raspberry Pi 2) on the
server-side, i.e. also a 32-bit architecture:

~ → ssh -v 192.168.1.152
OpenSSH_8.9p1 Debian-2, OpenSSL 1.1.1m  14 Dec 2021
debug1: Reading configuration data /home/abe/.ssh/config
debug1: /home/abe/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.152 [192.168.1.152] port 22.
debug1: Connection established.
debug1: identity file /home/abe/.ssh/id_rsa type 0
debug1: identity file /home/abe/.ssh/id_rsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa type 2
debug1: identity file /home/abe/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519 type 3
debug1: identity file /home/abe/.ssh/id_ed25519-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_xmss type -1
debug1: identity file /home/abe/.ssh/id_xmss-cert type -1
debug1: identity file /home/abe/.ssh/id_dsa type -1
debug1: identity file /home/abe/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Debian-2
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 
Debian-2
debug1: compat_banner: match: OpenSSH_8.9p1 Debian-2 pat OpenSSH* compat 
0x0400
debug1: Authenticating to 192.168.1.152:22 as 'abe'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or 
directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
ssh_dispatch_run_fatal: Connection to 192.168.1.152 port 22: Broken pipe

Currently looks to me as if 8.9 on the server-side is generally broken
iff the server runs on a 32-bit architectures. Al least all Sid 32-bit
architecture boxes I tried so far, failed with the same symptoms.

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

Processed: Re: Bug#1006463: openssh-server: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY" -> also affects armhf

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 openssh-server: Can't login on any 32-bit box anymore after the 
> server-side has been upgraded to 8.9p1: "debug1: expecting 
> SSH2_MSG_KEX_ECDH_REPLY"
Bug #1006463 [openssh-server] openssh-server: Can't login on two i386 boxes 
anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
Changed Bug title to 'openssh-server: Can't login on any 32-bit box anymore 
after the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"' from 'openssh-server: Can't login on two i386 boxes 
anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"'.

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

Bug#1006465: python-dbusmock: Fails to build from source: README.rst is not README.md

[Jeremy Bicha]

Source: python-dbusmock
Severity: serious
Version: 0.26.1-1
X-Debbugs-CC: mp...@debian.org

Today's python-dbusmock fails to build:

dh_installdocs: error: Cannot find (any matches for) "README.rst"
(tried in ., debian/tmp)

Try updating the file to install README.md instead of README.rst

Thank you,
Jeremy Bicha

Processed: Re: [Pkg-javascript-devel] Bug#1006053: node-regexpp: FTBFS: Cannot find type definition file for 'eslint'.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 eslint
Bug #1006053 [src:node-regexpp] node-regexpp: FTBFS: Cannot find type 
definition file for 'eslint'.
Bug reassigned from package 'src:node-regexpp' to 'eslint'.
No longer marked as found in versions node-regexpp/3.2.0-2.
Ignoring request to alter fixed versions of bug #1006053 to the same values 
previously set
> found -1 6.1.0~dfsg+~6.1.9-1
Bug #1006053 [eslint] node-regexpp: FTBFS: Cannot find type definition file for 
'eslint'.
Marked as found in versions eslint/6.1.0~dfsg+~6.1.9-1.

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

Bug#1006053: [Pkg-javascript-devel] Bug#1006053: node-regexpp: FTBFS: Cannot find type definition file for 'eslint'.

[Jonas Smedegaard]

Control: reassign -1 eslint
Control: found -1 6.1.0~dfsg+~6.1.9-1

Quoting Lucas Nussbaum (2022-02-19 07:51:14)
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > pandoc --from gfm-raw_html --to html --standalone --output README.html 
> > README.md
> > [WARNING] This document format requires a nonempty  element.
> >   Defaulting to 'README' as the title.
> >   To specify a title, use 'title' in metadata or --metadata title="...".
> > pandoc --from gfm-raw_html --to plain --output README.txt README.md
> > tsc --module es2015
> > error TS2688: Cannot find type definition file for 
> > 'eslint'.
> >   The file is in the program because:
> > Entry point for implicit type library 'eslint'

This is a bug in recent releases of esling, failing to include all its 
TypeScript types.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#1006463: openssh-client: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY"

[Colin Watson]

Control: forcemerge -1 1006445

On Fri, Feb 25, 2022 at 09:38:31PM +0100, Axel Beckert wrote:
> TL;DR: OpenSSH clients (at least 8.8 and 8.9) can't talk with OpenSSH
> 8.9 servers in some cases (common property so far: if and only if it's
> i386 on the server-side), but 8.9 clients can talk with 8.8 servers in
> the same cases (i.e. i386 on the server-side) after downgrading the
> server-side. i386 OpenSSH clients can't talk to i386 8.9 servers either.

See #1006445.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Processed: Re: Bug#1006463: openssh-client: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY"

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 1006445
Bug #1006463 [openssh-server] openssh-server: Can't login on any 32-bit box 
anymore after the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
Bug #1006445 [openssh-server] openssh-server: Killed by seccomp after accepting 
connection (i386)
Severity set to 'grave' from 'important'
There is no source info for the package 'openssh-server' at version 
'1:8.9p1-2.1' with architecture ''
Unable to make a source version for version '1:8.9p1-2.1'
Marked as found in versions openssh/1:8.9p1-2.
Bug #1006463 [openssh-server] openssh-server: Can't login on any 32-bit box 
anymore after the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
There is no source info for the package 'openssh-server' at version 
'1:8.9p1-2.1' with architecture ''
Unable to make a source version for version '1:8.9p1-2.1'
Marked as found in versions 1:8.9p1-2.1.
Added tag(s) patch.
Merged 1006445 1006463

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

Bug#1006459: marked as done (surf: flaky autopkgtest on arm64: too short timeout?)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 22:49:20 +
with message-id 
and subject line Bug#1006459: fixed in surf 2.1+git20210719-2
has caused the Debian Bug report #1006459,
regarding surf: flaky autopkgtest on arm64: too short timeout?
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.)


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

Source: surf
Version: 2.1+git20210719-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on arm64 
because it was showing up as a regression for the upload of autopkgtest. 
I noticed that the test regularly fails. As the test specifies a 
timeout, I wonder if that's just to short in some cases. I'm not 
excluding other causes.


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 causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/arm64/s/surf/19548818/log.gz

autopkgtest [11:15:07]: test command3: timeout 1m xvfb-run 
debian/tests/test_text.sh

autopkgtest [11:15:07]: test command3: [---

(surf:4981): dbind-WARNING **: 03:15:07.813: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.a11y.Bus was not provided by any .service files


(WebKitWebProcess:4997): dbind-WARNING **: 03:15:07.973: AT-SPI: Error 
retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files

Could not read style file: /home/debci/.surf/styles/default.css
Tesseract Open Source OCR Engine v4.1.1 with Leptonica
Warning: Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 123
autopkgtest [11:16:07]: test command3: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: surf
Source-Version: 2.1+git20210719-2
Done: Reiner Herrmann 

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

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

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated surf 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: Fri, 25 Feb 2022 23:29:59 +0100
Source: surf
Architecture: source
Version: 2.1+git20210719-2
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 1006459
Changes:
 surf (2.1+git20210719-2) unstable; urgency=medium
 .
   * Increase timeout in autopkgtest and let it fail more verbosely.
 (Closes: #1006459)
Checksums-Sha1:
 11770892ad4ad5734788cf1fbe97a97b7fb8db06 2110 surf_2.1+git20210719-2.dsc
 4fc58ba29015c2f0e55a88df8f62f3065463f09b 10648 
surf_2.1+git20210719-2.debian.tar.xz
 cb83fabb6108c2b4d7ba48d18014518e2af7f6db 16907 
surf_2.1+git20210719-2_source.buildinfo
Checksums-Sha256:
 b351b03215e0181e567b468afa7c6d927f88d6d5e9b508250d67e97e03f35208 2110 
surf_2.1+git20210719-2.dsc
 8d609967214481b040c6793eca375a9b360208433352f5681c6b9aa6c63c4977 10648 
surf_2.1+git20210719-2.debian.tar.xz
 d0911f771287abf30d55dbe9ab43213ece124406e97826a1c7fb2957c3c5aa12 16907 
surf_2.1+git20210719-2_source.buildinfo
Files:
 255278238ee6923f9c69424e37be88e4 2110 web optional surf_2.1+git20210719-2.dsc
 092075bd637f55ae71fc305b27778c43 10648 web optional 
surf_2.1+git20210719-2.debian.tar.xz
 b3f59c9507b902b265c9cf80e67ef048 16907 web optional 
surf_2.1+git20210719-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAmIZWNkACgkQzPBJKNsO
6qfU1Q//Yo8n9Xsr5OoGGYh+uNPKSA0X8uuckD+eMPJ10nAMkAcdp2BNaJ0hmrhA
YWZXUSEYKur8yCJJqHA14lbLdn4cRM+4Q2lPsyTAFuQADds+u8QR3jY3RQVqBDU1
6ygu1u9AjZ55TBkqpz3Sm99w0/r1eSQj

Bug#1006139: libdeflate FTBFS on armhf

[Peter Green]

Wookey wrote:

That seems an oversimplification. There is usually an FPU (almost
always) and a neon unit (usually). The point is that their presence is
not guaranteed


Debian armhf requires a FPU as part of the baseline. More than
that it requires a FPU as part of the ABI!

Andreas Tille wrote:

It fails to build with

   lib/arm/crc32_impl.h:77:1: error: ‘-mfloat-abi=hard’: selected architecture 
lacks an FPU


This issue is caused by the way current versions of debian/ubuntu 
package/configure gcc

The gcc packaging used to specify cpu and fpu architectures separately, but now 
it specifies
the fpu as an extension of the cpu architecture using the "armv7-a+fp" syntax. 
The result of
this is if you override the CPU architecture on debian armhf you must also 
specify a fpu
(either using a seperate "mfpu" setting or using the syntax for CPU 
architecture extensions).
If you don't then gcc will assume you have no FPU and therefore that it is 
unable to implement
the hard float ABI.

The particular code in question seems to be an implementation of crc32 using 
the crc32 extension
added as an optional feature in armv8. From a quick look it appears to already 
be behind runtime
cpu detection.

At least gcc seems to think that on armv8 floating point and simd always go together, 
"+fp"
is not recognised as an extension to armv8, only "+simd". So I think Ubuntu's 
current patch
which changes the CPU settings for the code that uses the crc extension from an 
architecture
setting of "armv8+crc32" to and architecture setting of "armv8+simd+crc32" is 
correct for
Debian armhf.

You could however argue that it is not correct for Debian armel, I suspect it 
is possible in
theory to have an armv8 CPU that doesn't have any floating point or simd 
support, but does have
the crc32 extension and to run debian armel on such a CPU. In practice I 
suspect such CPUs are
likely to be like hens teeth and I suspect the compiler is unlikely to actually 
use any floating
point or simd instructions when compiling that function anyway.

Still if you want to be safer, you could do something like

--- a/lib/arm/crc32_impl.h
+++ b/lib/arm/crc32_impl.h
@@ -41,7 +41,11 @@
 #  ifdef __clang__
 #define ATTRIBUTES __attribute__((target("armv8-a,crc")))
 #  else
-#define ATTRIBUTES __attribute__((target("arch=armv8-a+crc")))
+#ifdef __ARM_PCS_VFP
+#  define ATTRIBUTES   __attribute__((target("arch=armv8-a+simd+crc")))
+#else
+#  define ATTRIBUTES   __attribute__((target("arch=armv8-a+crc")))
+#endif
 #  endif
 #else
 #  ifdef __clang__

Bug#1006463: openssh-client: Can't login on two i386 boxes anymore since the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY"

[Axel Beckert]

Hi Colin,

Colin Watson wrote:
> On Fri, Feb 25, 2022 at 09:38:31PM +0100, Axel Beckert wrote:
> > TL;DR: OpenSSH clients (at least 8.8 and 8.9) can't talk with OpenSSH
> > 8.9 servers in some cases (common property so far: if and only if it's
> > i386 on the server-side), but 8.9 clients can talk with 8.8 servers in
> > the same cases (i.e. i386 on the server-side) after downgrading the
> > server-side. i386 OpenSSH clients can't talk to i386 8.9 servers either.
> 
> See #1006445.

Hmmm, I looked through the open bug reports before filing mine, but
I hadn't notice that one, sorry.

Thanks for the hint!

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

Bug#1006445: marked as pending in openssh

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1006445 in openssh 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/ssh-team/openssh/-/commit/62765c0d4297dae75c91aa1d3191df3e3a1b5893


Allow ppoll_time64 in seccomp filter

Closes: #1006445


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006445

Processed: Bug#1006445 marked as pending in openssh

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006445 [openssh-server] openssh-server: Killed by seccomp after accepting 
connection (i386)
Bug #1006463 [openssh-server] openssh-server: Can't login on any 32-bit box 
anymore after the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Re: Bug#1006445: openssh-server: Killed by seccomp after accepting connection (i386)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.mindrot.org/show_bug.cgi?id=3396
Bug #1006445 [openssh-server] openssh-server: Killed by seccomp after accepting 
connection (i386)
Bug #1006463 [openssh-server] openssh-server: Can't login on any 32-bit box 
anymore after the server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
Set Bug forwarded-to-address to 
'https://bugzilla.mindrot.org/show_bug.cgi?id=3396'.
Set Bug forwarded-to-address to 
'https://bugzilla.mindrot.org/show_bug.cgi?id=3396'.

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

Bug#1006445: openssh-server: Killed by seccomp after accepting connection (i386)

[Colin Watson]

Control: forwarded -1 https://bugzilla.mindrot.org/show_bug.cgi?id=3396

On Fri, Feb 25, 2022 at 03:50:05PM +, Colin Watson wrote:
> On Fri, Feb 25, 2022 at 02:14:58PM +, Paul Brook wrote:
> > The attached patch fixes this by adding ppoll_time64 the seccomp sanbox 
> > filters,
> > which seems reasonable as ppoll is already allowed.
> 
> Yeah, this looks reasonable to me too, though for tidiness I'd suggest
> moving __NR_ppoll_time64 below __NR_ppoll to match the ordering of
> __NR_pselect6 and __NR_pselect6_time64.
> 
> Would you mind sending this upstream to https://bugzilla.mindrot.org/ ?
> I can do it for you if you can't, but it's usually best to have fewer
> people in the middle of the discussion.

Looks like somebody else already filed this at
https://bugzilla.mindrot.org/show_bug.cgi?id=3396 with a very similar
patch, so no need to send it again.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1006463: marked as done (openssh-server: Can't login on any 32-bit box anymore after the server-side has been upgraded to 8.9p1: "debug1: expecting SSH2_MSG_KEX_ECDH_REPLY")

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 23:49:11 +
with message-id 
and subject line Bug#1006445: fixed in openssh 1:8.9p1-3
has caused the Debian Bug report #1006445,
regarding openssh-server: Can't login on any 32-bit box anymore after the 
server-side has been upgraded to 8.9p1: "debug1: expecting 
SSH2_MSG_KEX_ECDH_REPLY"
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.)


-- 
1006445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:8.9p1-2
Severity: grave

Hi,

TL;DR: OpenSSH clients (at least 8.8 and 8.9) can't talk with OpenSSH
8.9 servers in some cases (common property so far: if and only if it's
i386 on the server-side), but 8.9 clients can talk with 8.8 servers in
the same cases (i.e. i386 on the server-side) after downgrading the
server-side. i386 OpenSSH clients can't talk to i386 8.9 servers either.

Full details:

Since I've upgraded my Debian Unstable boxes to 1:8.9p1-2, I can't login
from my desktop (Sid amd64) to at least two hosts (both Sid i386)
anymore:

~ → ssh -v 192.168.1.179
OpenSSH_8.9p1 Debian-2, OpenSSL 1.1.1m  14 Dec 2021
debug1: Reading configuration data /home/abe/.ssh/config
debug1: /home/abe/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.179 [192.168.1.179] port 22.
debug1: Connection established.
debug1: identity file /home/abe/.ssh/id_rsa type 0
debug1: identity file /home/abe/.ssh/id_rsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa type 2
debug1: identity file /home/abe/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519 type 3
debug1: identity file /home/abe/.ssh/id_ed25519-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_xmss type -1
debug1: identity file /home/abe/.ssh/id_xmss-cert type -1
debug1: identity file /home/abe/.ssh/id_dsa type -1
debug1: identity file /home/abe/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Debian-2
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 
Debian-2
debug1: compat_banner: match: OpenSSH_8.9p1 Debian-2 pat OpenSSH* compat 
0x0400
debug1: Authenticating to 192.168.1.179:22 as 'abe'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or 
directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection reset by 192.168.1.179 port 22

~ → ssh -v 192.168.1.108
OpenSSH_8.9p1 Debian-2, OpenSSL 1.1.1m  14 Dec 2021
debug1: Reading configuration data /home/abe/.ssh/config
debug1: /home/abe/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.108 [192.168.1.108] port 22.
debug1: Connection established.
debug1: identity file /home/abe/.ssh/id_rsa type 0
debug1: identity file /home/abe/.ssh/id_rsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa type 2
debug1: identity file /home/abe/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/abe/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519 type 3
debug1: identity file /home/abe/.ssh/id_ed25519-cert type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk type -1
debug1: identity file /home/abe/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/abe/.ssh/id_xmss type -1
debug1: identity file /home/abe/.ssh/id_xmss-cert type -1
debug1: identity file /home/abe/.ssh/id_dsa type -1
debug1: identity file /home/abe/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Debian-2
debug1: Remote protocol version 2.0, remote software versio

Bug#1006445: marked as done (openssh-server: Killed by seccomp after accepting connection (i386))

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 23:49:11 +
with message-id 
and subject line Bug#1006445: fixed in openssh 1:8.9p1-3
has caused the Debian Bug report #1006445,
regarding openssh-server: Killed by seccomp after accepting connection (i386)
to be marked as done.

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

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


-- 
1006445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:8.9p1-2.1
Severity: important
Tags: patch

Dear Maintainer,

After accepting an ssh connection, the sshd process is killed and I see
the following in dmesg:

audit: type=1326 audit(1645794361.669:40): auid=0 uid=100 gid=65534 ses=1 
subj==unconfined pid=8338 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=4003 
syscall=414 compat=0 ip=0xb7ee3559 code=0x0

Sysycall 414 is ppoll_time64, so I'm guessing this is fallout from
ongoing 2038 fixes.

The attached patch fixes this by adding ppoll_time64 the seccomp sanbox filters,
which seems reasonable as ppoll is already allowed.

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

Kernel: Linux 5.16.0-2-686-pae (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.79
ii  dpkg   1.21.1
ii  init-system-helpers1.62
ii  libaudit1  1:3.0.7-1
ii  libc6  2.33-7
ii  libcom-err21.46.5-2
ii  libcrypt1  1:4.4.27-1.1
ii  libgssapi-krb5-2   1.19.2-2
ii  libkrb5-3  1.19.2-2
ii  libpam-modules 1.4.0-11
ii  libpam-runtime 1.4.0-11
ii  libpam0g   1.4.0-11
ii  libselinux13.3-1+b1
ii  libssl1.1  1.1.1m-1
ii  libsystemd0250.3-2
ii  libwrap0   7.6.q-31
ii  lsb-base   11.1.0
ii  openssh-client 1:8.9p1-2.1
ii  openssh-sftp-server1:8.9p1-2
ii  procps 2:3.3.17-6
ii  runit-helper   2.10.3
ii  ucf3.0043
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  250.3-2
pn  ncurses-term 
ii  xauth1:1.1-1

Versions of packages openssh-server suggests:
ii  molly-guard   0.7.2
pn  monkeysphere  
pn  ssh-askpass   
pn  ufw   

-- debconf information:
  ssh/insecure_telnetd:
  ssh/vulnerable_host_keys:
* ssh/use_old_init_script: true
  ssh/new_config: true
  ssh/insecure_rshd:
* openssh-server/permit-root-login: true
  ssh/disable_cr_auth: false
  openssh-server/password-authentication: false
  ssh/encrypted_host_key_but_no_keygen:
diff -ur clean/sandbox-seccomp-filter.c openssh-8.9p1/sandbox-seccomp-filter.c
--- clean/sandbox-seccomp-filter.c  2022-02-23 11:31:11.0 +
+++ openssh-8.9p1/sandbox-seccomp-filter.c  2022-02-25 13:16:17.319892443 
+
@@ -273,6 +273,9 @@
 #ifdef __NR__newselect
SC_ALLOW(__NR__newselect),
 #endif
+#ifdef __NR_ppoll_time64
+   SC_ALLOW(__NR_ppoll_time64),
+#endif
 #ifdef __NR_ppoll
SC_ALLOW(__NR_ppoll),
 #endif
--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:8.9p1-3
Done: Colin Watson 

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated openssh 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, 25 Feb 2022 23:30:49 +
Source: openssh
Architecture: source
Version: 1:8.9p1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers 
Changed-By: Colin Watson 
Closes: 1006445
Changes:
 openssh (1:8.9p1-3) unstable; urgency=medium
 .
   * Allow ppoll_time64 in seccomp filter 

Processed: ansible-core: No such file or directory: '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1001040 [src:ansible-core] ansible-core: No such file or directory: 
'/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py'
Severity set to 'grave' from 'important'

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

Bug#1005640: marked as done (fonttools: Missing dependency python3-unicodedata2 (ITP needed))

[Debian Bug Tracking System]

Your message dated Sat, 26 Feb 2022 03:18:43 +
with message-id 
and subject line Bug#1005640: fixed in fonttools 4.29.1-2
has caused the Debian Bug report #1005640,
regarding fonttools: Missing dependency python3-unicodedata2 (ITP needed)
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.)


-- 
1005640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonttools
Version: 4.29.1-1
Severity: serious
Justification: Policy 3.5
X-Debbugs-Cc: debian-fo...@lists.debian.org
Control: block 1005477 by -1
Control: block 1005474 by -1

This package has missing dependency of python package name
"unicodedata2" since version 4.29.1-1, according to the FTBFS messages
from #1005474 and #1005477.

NEW python package for unicodedata2 is needed.

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

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

Versions of packages fonttools depends on:
ii  python33.9.8-1
ii  python3-fonttools  4.29.1-1

fonttools recommends no packages.

fonttools suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fonttools
Source-Version: 4.29.1-2
Done: Yao Wei (魏銘廷) 

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

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

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

Debian distribution maintenance software
pp.
Yao Wei (魏銘廷)  (supplier of updated fonttools 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: Sat, 26 Feb 2022 10:45:25 +0800
Source: fonttools
Architecture: source
Version: 4.29.1-2
Distribution: unstable
Urgency: high
Maintainer: Debian Fonts Task Force 
Changed-By: Yao Wei (魏銘廷) 
Closes: 1005640
Changes:
 fonttools (4.29.1-2) unstable; urgency=high
 .
   * debian/control: Add missing dependency of python3-unicodedata2
 (Closes: #1005640)
Checksums-Sha1:
 08cba5f42c2aa65d084b4a2b5d854e84d9775451 2703 fonttools_4.29.1-2.dsc
 3b0444159a9c1dc7219db084758309f91e164d3c 10764 fonttools_4.29.1-2.debian.tar.xz
 596e75767c290fcbf89a032d45708c4465d6ea8e 11215 
fonttools_4.29.1-2_amd64.buildinfo
Checksums-Sha256:
 c6dda853e455cd2aaac9458fd72b8e25a083cb2221077dca912d7d07b80b05e1 2703 
fonttools_4.29.1-2.dsc
 129c38d4abe338f1003bb6089783894e56f858e961f4203b64b42e5a79d82251 10764 
fonttools_4.29.1-2.debian.tar.xz
 17b17adb20d0cb6a8a3b22478094d42c76231e359eea04a3e821a8440c458ddd 11215 
fonttools_4.29.1-2_amd64.buildinfo
Files:
 c2f8028a78c3c03131c087b2affb64a1 2703 devel optional fonttools_4.29.1-2.dsc
 8f1f748aa6b73c0f2eba90d2192f8be1 10764 devel optional 
fonttools_4.29.1-2.debian.tar.xz
 55e502ce66c8eef553815e611671fe37 11215 devel optional 
fonttools_4.29.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE8htgli/cvAeDZWXRl1ewRNNETDMFAmIZlp4QHG13ZWlAZGVi
aWFuLm9yZwAKCRCXV7BE00RMM8bKD/0UkaxZf3ABCoOp0tKg8vUSvek72Kwe20ga
KBw7UjMq8ARbAD1o/PqgchHzwrIE5IzAoNcsU7uZqBBJj0zxj8Z1wjLdwzkW8Icq
oTCpSZjsNWAKO2q7ELj5gGgZUAfFKaCd2ehJOrzXjiebthRAak/++gzsjYF0JlLr
h/rCQCyBA8nRRi4e2vIK+Dy4gAISgLRn35XsjNYkg2HmzaQE6Z7rdsqFA1bX2OvJ
uQnR4DkI6uFce6u0z6/8ZWCCNi3Z2vKCqyhAWsOaDirPyn4DVmKU8877u96/aHsF
UyduLC4NvOeBLicAIgautVkjBYgqK8Z45bHTsOx16irqhqUD8wBgcMF/n9CmY49z
3kHIk4UTvJyk2a1m8KJowCQ9h1DsJNlvP2hyNN9TgMbbMZNqWtXOWtwi8afPV2hC
TGVhDRT88jiGpthkrt4QohiMfjTU5D2moG8IcSyxBnPv+wl8/pQpzfRlozsDVCFW
9lsxz/ao/eN+lgz+G3e+GCbd00TEMd8q5BjlIlgyhr45uuy5c+LDu/kHDhXLZQEF
SXS/+8DsxXtWsIvnj7aBw6/sMzDax1jaFkrsb+FHmlP9aXUXEA2WERjUHK5Gf9Wp
61CA5vb3oFTDokGuaiQxttRJ0oDM8mycS/FJ7ykeiMDi8sm1MrFW03Hl7BbhhkPX
igblUuJnmg==
=O1yf
-END PGP SIGNATURE End Message ---

Bug#900821: apache reads wrong data over cifs filesystems served by samba

[Guy Elsmore-Paddock]

I recently encountered this bug without using Apache. It is reproducible using 
Nextcloud PHP on nginx, as explained in this bug report I filed earlier today 
in the Nextcloud issue queue:
https://github.com/nextcloud/server/issues/31361

We saw it on both nginx and Apache, so that rules out Apache as one of the 3 
components that are involved in causing the issue. It appears that the issue is 
related to mmap(), which IMO points to the kernel but I suppose that the 
Samba/CIFS driver could be handling buffers improperly. We saw this in two 
different Kubernetes clusters, one running kernel 4.15.0-1113-azure and 
5.4.0-1068-azure

Guy Elsmore-Paddock | he/him/his
Lead Architect/Chief Technology Officer
Inveniem
[Inveniem Logo]