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

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

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

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

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

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:

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

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

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

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:

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

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

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

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

Bug#1006445: marked as pending in openssh

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:

Processed: Bug#1006445 marked as pending in openssh

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:

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"

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

Bug#1006139: libdeflate FTBFS on armhf

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:

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

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

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"

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

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"

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

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

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

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

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

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

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

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

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

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

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

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"

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 >

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"

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.

Processed: reassign bug from ftpmasters to package

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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:

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

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

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

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,

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

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

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

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

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

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

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

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:

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

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

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

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

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

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.

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

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

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

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

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

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]

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

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

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

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

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

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.

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

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

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

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

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

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

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)

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

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

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

Bug#1006333: Biboumi 9.0 on bullseye

Same issue with Biboumi 9.0 on Debian Bullseye and libexpat1 2.2.10-2. Was working fine until I updated today.