Bug#1007117: marked as done (node-jsdom: ships */parse5-htmlparser2-tree-adapter/*, already in node-cheerio)

Your message dated Sat, 12 Mar 2022 07:20:28 + with message-id and subject line Bug#1007117: fixed in node-jsdom 19.0.0+~cs153.23.47-3 has caused the Debian Bug report #1007117, regarding node-jsdom: ships */parse5-htmlparser2-tree-adapter/*, already in node-cheerio to be marked as done.

Bug#1007117: marked as done (node-jsdom: ships */parse5-htmlparser2-tree-adapter/*, already in node-cheerio)

Your message dated Sat, 12 Mar 2022 07:20:19 + with message-id and subject line Bug#1007117: fixed in node-cheerio 1.0.0~rc~10+repack-1 has caused the Debian Bug report #1007117, regarding node-jsdom: ships */parse5-htmlparser2-tree-adapter/*, already in node-cheerio to be marked as done.

Bug#1006763: marked as done (python-reportlab: fails to build with python3.10)

Your message dated Sat, 12 Mar 2022 05:49:08 + with message-id and subject line Bug#1006763: fixed in python-reportlab 3.6.8-1 has caused the Debian Bug report #1006763, regarding python-reportlab: fails to build with python3.10 to be marked as done. This means that you claim that the

Bug#982159: dxvk: Dependency on development version of WINE might not be justified

Quack, On 2022-03-11 21:52, Adrian Bunk wrote: dxvk should have an RC bug documenting why it is not in testing, and this bug in dxvkshould be fixed by using the non-development version of wine. I agree documenting is nice but this is not my decision. It is unlikely that wine maintainers

Bug#1007010: python3.10: autopkgtest regression: FAIL: test_get_scheme_names

Hi Paul (2022.03.10_10:05:50_-0400) > I copied some of the output at the bottom of this report. To be fair, I'm > not sure if this isn't related to the missing arch:all build (bug #1000188). Aha, that explains why I was unable to reproduce this locally. Yes, I assume that's the issue here. SR

Bug#1007145: wordpress: WordPress 5.9.2 security and maintenance release

Package: wordpress Version: 5.8.3+dfsg1-1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team WordPress has released version 5.9.2 that has one bug fix and three security fixes[1]. They state the security fixes are required back to 3.7 so all

Bug#1005475: marked as done (net-cpp: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2)

Your message dated Sat, 12 Mar 2022 00:33:54 + with message-id and subject line Bug#1005475: fixed in net-cpp 3.0.0+dfsg1-2 has caused the Debian Bug report #1005475, regarding net-cpp: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned

Bug#1006017:

G'day Tiago > Are you sure you're testing it in a clean Bullseye system? Nah, far from *clean*. The Debian Bullseye box I used I use mostly as a media player; install shows it was with 8/squeeze or 20150422 installation media (/var/log/installer/lsb_release) and the drive has outlived a couple

Bug#997439: marked as done (signond: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Fri, 11 Mar 2022 22:20:47 + with message-id and subject line Bug#997439: fixed in signond 8.61-1 has caused the Debian Bug report #997439, regarding signond: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to

Bug#948987: marked as done (kopete: segfaults when is using it (libjingle-call))

Your message dated Fri, 11 Mar 2022 21:19:07 + with message-id and subject line Bug#948987: fixed in kopete 4:21.12.3-1 has caused the Debian Bug report #948987, regarding kopete: segfaults when is using it (libjingle-call) to be marked as done. This means that you claim that the problem has

Processed: tagging 997439

Processing commands for cont...@bugs.debian.org: > tags 997439 + pending Bug #997439 [src:signond] signond: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. > thanks Stopping processing here. Please contact me

Bug#1007117: marked as pending in node-cheerio

On 11/03/2022 20.14, Yadd wrote: https://salsa.debian.org/js-team/node-cheerio/-/commit/4232ad8c2e2fa65bfb806fbce25e7f06cd509968 Drop component parse5-htmlparser2-tree-adapter If the conflicting bits are going to be dropped from node-cheerio, node-jsdom will need Breaks+Replaces:

Bug#1007117: marked as pending in node-cheerio

Control: tag -1 pending Hello, Bug #1007117 in node-cheerio 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#1007117 marked as pending in node-cheerio

Processing control commands: > tag -1 pending Bug #1007117 [node-jsdom] node-jsdom: ships */parse5-htmlparser2-tree-adapter/*, already in node-cheerio Added tag(s) pending. -- 1007117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007117 Debian Bug Tracking System Contact

Bug#1006820: marked as done (src:cryfs: fails to migrate to testing for too long: FTBFS on armel and armhf)

Your message dated Fri, 11 Mar 2022 19:03:57 + with message-id and subject line Bug#1006820: fixed in cryfs 0.11.2-2 has caused the Debian Bug report #1006820, regarding src:cryfs: fails to migrate to testing for too long: FTBFS on armel and armhf to be marked as done. This means that you

Bug#1003679: marked as done (cryfs: autopkgtest regression on armhf: Resource temporarily unavailable)

Your message dated Fri, 11 Mar 2022 19:03:57 + with message-id and subject line Bug#1003679: fixed in cryfs 0.11.2-2 has caused the Debian Bug report #1003679, regarding cryfs: autopkgtest regression on armhf: Resource temporarily unavailable to be marked as done. This means that you claim

Bug#1006928: marked as done (librust-phf-shared+uncased-dev depends on package that is not in Debian.)

Your message dated Fri, 11 Mar 2022 19:00:13 + with message-id and subject line Bug#1006928: fixed in rust-uncased 0.9.6-1 has caused the Debian Bug report #1006928, regarding librust-phf-shared+uncased-dev depends on package that is not in Debian. to be marked as done. This means that you

Processed: now also FTBFS

Processing commands for cont...@bugs.debian.org: > severity 994456 serious Bug #994456 [src:ruby-stackprof] ruby-stackprof: flaky autopkgtests Severity set to 'serious' from 'important' > tags 994456 ftbfs Bug #994456 [src:ruby-stackprof] ruby-stackprof: flaky autopkgtests Added tag(s) ftbfs. >

Bug#1006017: playitslowly - PLEASE DON'T REMOVE FROM STABLE

Hi, I've double-checked playitslowly in a clean stable system and indeed it works. Thanks Chris for avoiding the removal in time. I'm not sure why it hadn't work in my previous system. Andreas, I had already tried 1.5.1 release and it presents the very same issues on unstable. If the upstream or

Bug#1006017: playitslowly - PLEASE DON'T REMOVE FROM STABLE

On 11/03/2022 16.39, Tiago Bortoletto Vaz wrote: Andreas Beckmann also confirmed it doesn't work for him. Digging a bit further into the problem ... https://stackoverflow.com/questions/55670051/python3-gtk-program-throws-introspection-typelib-error ... installing gir1.2-gtk-3.0 makes it no

Processed: affects 1006910

Processing commands for cont...@bugs.debian.org: > affects 1006910 src:cloudcompare src:paraview src:facet-analyser Bug #1006910 [src:pdal] pdal: Should not be included in bookworm Added indication that 1006910 affects src:cloudcompare, src:paraview, and src:facet-analyser > thanks Stopping

Processed: affects 1007126

Processing commands for cont...@bugs.debian.org: > affects 1007126 src:pdal src:cloudcompare Bug #1007126 [src:laszip] laszip: Should not be included in bookworm Added indication that 1007126 affects src:pdal and src:cloudcompare > thanks Stopping processing here. Please contact me if you need

Processed: laszip: Should not be included in bookworm

Processing control commands: > block -1 by 1006910 Bug #1007126 [src:laszip] laszip: Should not be included in bookworm 1007126 was not blocked by any bugs. 1007126 was not blocking any bugs. Added blocking bug(s) of 1007126: 1006910 -- 1007126:

Bug#1007126: laszip: Should not be included in bookworm

Source: laszip Version: 3.4.3-2 Severity: serious Tags: bookworm sid Justification: in the maintainer's opinion, makes the package unsuitable for release Control: block -1 by 1006910 LASzip is dead upstream, literally. It should not be included in bookworm, but cannot be removed before PDAL is.

Bug#1006017: playitslowly - PLEASE DON'T REMOVE FROM STABLE

Hi Chris, I've tested it here and got the same error as we have in unstable. Andreas Beckmann also confirmed it doesn't work for him. Are you sure you're testing it in a clean Bullseye system? Anyway, I'm dropping my request to removal from stable/old-stable for now:

Processed: severity of 1007115 is grave

Processing commands for cont...@bugs.debian.org: > severity 1007115 grave Bug #1007115 [squeekboard] squeekboard covers applications in landscape Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1007115:

Bug#1007117: node-jsdom: ships */parse5-htmlparser2-tree-adapter/*, already in node-cheerio

Package: node-jsdom Version: 19.0.0+~cs153.23.47-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...):

Bug#982159: dxvk: Dependency on development version of WINE might not be justified

On Wed, Mar 09, 2022 at 12:56:39PM +0900, Marc Dequènes (duck) wrote: > Quack, > > Btw, Adrian could you clarify with you bumped the severity? > wine-development was already blocked from entering Bullseye and that blocked > dxvk as well, so no need to add a RC bug just for that. dxvk should have

Processed: tagging 1006919, found 1003570 in 0.3-3, found 1003568 in 0.9.5+dfsg.2-1, tagging 1003568 ...

Processing commands for cont...@bugs.debian.org: > tags 1006919 + sid bookworm Bug #1006919 [src:cbmc] src:cbmc FTBFS Added tag(s) bookworm and sid. > found 1003570 0.3-3 Bug #1003570 [giara] giara: Depends on python3-mistune 0.8.4 which is deprecated Marked as found in versions giara/0.3-3. >

Bug#1003566: Please modify your dependencies from python3-mistune to python3-mistune0

Pierre-Elliott Bécue wrote on 24/02/2022 at 22:04:28+0100: > [[PGP Signed Part:Good signature from 29BFA0D079290ACA Pierre-Elliott Bécue > (trust ultimate) created at 2022-02-24T22:36:30+0100 using > RSA]] > Hi, > > Following up some exchanges, we agreed within the Python Team to > reupload

Processed: severity of 1003570 is serious

Processing commands for cont...@bugs.debian.org: > severity 1003570 serious Bug #1003570 [giara] giara: Depends on python3-mistune 0.8.4 which is deprecated Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 1003570:

Processed: severity of 1003568 is serious

Processing commands for cont...@bugs.debian.org: > severity 1003568 serious Bug #1003568 [python3-flasgger] python3-flasgger: Depends on python3-mistune 0.8.4 which is deprecated Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 1003566 is serious

Processing commands for cont...@bugs.debian.org: > severity 1003566 serious Bug #1003566 [lektor] lektor: Depends on python3-mistune 0.8.4 which is deprecated Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 1003566:

Processed: severity of 1003567 is serious

Processing commands for cont...@bugs.debian.org: > severity 1003567 serious Bug #1003567 [python3-schema-salad] python3-schema-salad: Depends on python3-mistune 0.8.4 which is deprecated Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need