Bug#965164: [Pkg-utopia-maintainers] Bug#965164: policykit-1: fails to install

Am 17.07.20 um 04:57 schrieb Michael Stone: > Package: policykit-1 > Version: 0.105-27 > Severity: grave > Justification: renders package unusable > > On install: > > Setting up policykit-1 (0.105-27) ... > chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such > file or

Bug#965153: gscan2pdf: "fails to open device" for Epson NX100

The changes between 2.3.0 and 2.8.0/1 (at least as far as opening the scanner are concerned) were to cache the list of devices, in order to save a few seconds searching for them - on most systems they are identical every time. On some systems, the device names change due to the USB IDs changing.

Bug#965174: node-globby build depends on the babeljs provides that will not be in bullseye

Source: node-globby Version: 7.1.1-2 Severity: serious Tags: ftbfs bullseye sid Control: block 960748 by -1 node-globby build depends on the babeljs provides that will not be in bullseye due to #960748.

Processed: node-globby build depends on the babeljs provides that will not be in bullseye

Processing control commands: > block 960748 by -1 Bug #960748 [node-babel] node-babel: meta bug to keep out of testing 960748 was blocked by: 959798 960264 965173 960021 960120 960748 was not blocking any bugs. Added blocking bug(s) of 960748: 965174 -- 960748:

Bug#965164: policykit-1: fails to install

Package: policykit-1 Version: 0.105-26 Followup-For: Bug #965164 Same thing here, on my debian unstable installation. I did this to "force" dpkg complete the installation, but I do not know if it is correct mkdir /usr/lib/policykit-1/ cp /usr/libexec/polkit-agent-helper-1

Processed: node-ramda build depends on the babeljs provides that will not be in bullseye

Processing control commands: > block 960748 by -1 Bug #960748 [node-babel] node-babel: meta bug to keep out of testing 960748 was blocked by: 959798 960120 965173 965174 960021 960264 960748 was not blocking any bugs. Added blocking bug(s) of 960748: 965176 -- 960748:

Bug#965176: node-ramda build depends on the babeljs provides that will not be in bullseye

Source: node-ramda Version: 0.26.1+dfsg-2 Severity: serious Tags: ftbfs bullseye sid Control: block 960748 by -1 node-ramda build depends on the babeljs provides that will not be in bullseye due to #960748.

Bug#965164: policykit-1

This also makes the system fail to boot. Regards

Bug#965166: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation

Hi Bart, Thanks for forwarding the report on. Isn't it a generic net-snmp bug? Debian does use this feature of setting the user to not root but wouldn't anyone using the set the user feature have the same issue? Not sure of the best way to fix this. Maybe not being to set the user in /car files

Processed: forcibly merging 965165 965164

Processing commands for cont...@bugs.debian.org: > forcemerge 965165 965164 Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to /usr/libexec Bug #965164 [policykit-1] policykit-1: fails to install Severity set to 'serious' from 'grave' Added tag(s) patch. Bug #965165

Bug#964086: marked as done (r-cran-sf: autopkgtest failures with PROJ 7.1.0)

Your message dated Fri, 17 Jul 2020 07:33:36 + with message-id and subject line Bug#964086: fixed in r-cran-sf 0.9-5+dfsg-1 has caused the Debian Bug report #964086, regarding r-cran-sf: autopkgtest failures with PROJ 7.1.0 to be marked as done. This means that you claim that the problem has

Processed: severity of 965165 is serious

Processing commands for cont...@bugs.debian.org: > severity 965165 serious Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to /usr/libexec Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 965165:

Processed: Fwd: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation

Processing commands for cont...@bugs.debian.org: > tag 965166 security Bug #965166 [snmpd] snmpd privilege escalation Added tag(s) security. > severity 965166 critical Bug #965166 [snmpd] snmpd privilege escalation Severity set to 'critical' from 'normal' > thank you Stopping processing here.

Bug#965181: goval-dictionary: B-D on removed golang-github-dgrijalva-jwt-go-v3-dev

Source: goval-dictionary Version: 0.2.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, goval-dictionary/experimental cannot be built any more since its build-dependency golang-github-dgrijalva-jwt-go-v3-dev is gone. Andreas

Bug#964044: mrpt: FTBFS: test failure

Hello, > which is not yet released as 2.0.5, and which you can include as a > patch if you want to go on with the ros-geometry2 transition. > Since you are the maintainer, I'm uploading in deferred/1 your patch, refreshed in some parts to apply to the current 2.0.4 (and removing the rules

Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

Source: node-rollup-plugin-buble Version: 0.19.8-2 Severity: serious Tags: ftbfs Control: block 960748 by -1 node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye due to #960748.

Bug#965164: (no subject)

Package: policykit-1 Version: 0.105-27 Followup-For: Bug #965164 I confirm the bug. After fixing postinst script, package installation complete without error, but service restart fails because it can not find polkitd, which has been moved in /usr/libexec/polkit. Systemd unit file needs to be

Processed: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

Processing control commands: > block 960748 by -1 Bug #960748 [node-babel] node-babel: meta bug to keep out of testing 960748 was blocked by: 959798 960021 960264 960120 960748 was not blocking any bugs. Added blocking bug(s) of 960748: 965173 -- 960748:

Bug#964627: fractgen: FTBFS: colorschemeinterface.cc

Hi Lucas, thanks a lot for this bug report. I will do my best to sort this out during the week-end. cheers, Hugo -- Hugo Lefeuvre (hle)|www.owl.eu.com RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C

Bug#965177: libftdi: ships broken cmake file

Hello again: This is an example of cmake test file that might help in the future detecting such issues: (stolen and adapted from mrpt) cat ../CMakeLists.txt cmake_minimum_required(VERSION 3.16) project(test) find_package(LibFTDI1) message("Include directories: " ${LIBFTDI_INCLUDE_DIRS})

Bug#964634: marked as done (veyon: FTBFS: AccessControlProvider.cpp:168:93: error: ‘class QStringList’ has no member named ‘toSet’)

Your message dated Fri, 17 Jul 2020 08:55:50 + with message-id and subject line Bug#964634: fixed in veyon 4.4.1+repack1-1 has caused the Debian Bug report #964634, regarding veyon: FTBFS: AccessControlProvider.cpp:168:93: error: ‘class QStringList’ has no member named ‘toSet’ to be marked

Bug#965164:

Hi, Also affected, but it doesn't seem to affect reboot or sound for me. Regards, Jonathan Marsaud

Bug#961811: baresip: diff for NMU version 0.6.1-1.1

On 17/07/2020 06:40, Sebastian Ramacher wrote: Hi On 2020-07-17 00:02:17 +0100, peter green wrote: (note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and uploaded it to DELAYED/2. While I have not tested, I am 99% sure your

Bug#964044: mrpt: FTBFS: test failure

Hi, Gianfranco: > > This issue has been fixed upstream: > > https://github.com/MRPT/mrpt/commit/15234dc335c2413e3fd41021f7511f1d36fe915b. > > Could you please apply the fix to the Debian package so that > > ros-geometry2 transition can be completed? Thanks > > > looks like that commit is already

Bug#965182: python3-enlighten{,-doc}: both ship usr/share/man/man1/enlighten.1.gz

Package: python3-enlighten,python3-enlighten-doc Version: 1.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to

Bug#965164: [Pkg-utopia-maintainers] Bug#965164:

Am 17.07.20 um 11:18 schrieb Jonathan Marsaud: > Edit: doesn't prevent rebooting but prevent from launching a GNOME or > Plasma session (freeze after login). Sorry for all the inconvenience :-/ I clearly didn't test this properly. I uploaded a fixed package a couple of minutes ago. It should be

Bug#965177: libftdi: ships broken cmake file

Hello, I'm attaching a tested patch that also adds a new autopkgtest that spots this kind of failures in the future. (the diff fixes also #965175) G. diff -Nru libftdi1-1.5/debian/changelog libftdi1-1.5/debian/changelog --- libftdi1-1.5/debian/changelog 2020-07-14 23:32:06.0

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Package: policykit-1 Version: 0.105-27 Severity: grave Justification: renders package unusable policykit-1 cannot be installed: [...] Setting up policykit-1 (0.105-27) ... chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file or directory dpkg: error processing package

Bug#965164:

Edit: doesn't prevent rebooting but prevent from launching a GNOME or Plasma session (freeze after login). Jonathan Marsaud

Bug#965182: marked as done (python3-enlighten{,-doc}: both ship usr/share/man/man1/enlighten.1.gz)

Your message dated Fri, 17 Jul 2020 12:34:38 + with message-id and subject line Bug#965182: fixed in enlighten 1.6.0-2 has caused the Debian Bug report #965182, regarding python3-enlighten{,-doc}: both ship usr/share/man/man1/enlighten.1.gz to be marked as done. This means that you claim

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

Package: openssh-server Version: 1:7.9p1-10+deb10u2 Severity: critical Justification: breaks the whole system Updating libc on stable breaks sshd; it dies with a SIGSYS on clock_nanosleep. https://www.openssh.com/releasenotes.html says - Allow clock_nanosleep() in sandbox (recent

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Note: The bug is not present in 0.105-26, thus this is a different bug from 965164 (or the metadata have been messed up in bug 965164, which is ignored by apt-listbugs when upgrading from 0.105-26). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Processed: found 965154 in 5.42.1-1

Processing commands for cont...@bugs.debian.org: > found 965154 5.42.1-1 Bug #965154 [maxima] maxima: insecure use of /tmp Marked as found in versions maxima/5.42.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 965154:

Processed: tagging 965154

Processing commands for cont...@bugs.debian.org: > tags 965154 + security Bug #965154 [maxima] maxima: insecure use of /tmp Ignoring request to alter tags of bug #965154 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 965154:

Bug#965165: marked as done (policykit-1: polkit.service broken after switch to /usr/libexec)

Your message dated Fri, 17 Jul 2020 09:33:52 + with message-id and subject line Bug#965164: fixed in policykit-1 0.105-28 has caused the Debian Bug report #965164, regarding policykit-1: polkit.service broken after switch to /usr/libexec to be marked as done. This means that you claim that

Bug#965164: marked as done (policykit-1: fails to install)

Your message dated Fri, 17 Jul 2020 09:33:52 + with message-id and subject line Bug#965164: fixed in policykit-1 0.105-28 has caused the Debian Bug report #965164, regarding policykit-1: fails to install to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

On Fri, Jul 17, 2020 at 10:29:18AM +0200, Philipp Marek wrote: > Package: openssh-server > Version: 1:7.9p1-10+deb10u2 > Severity: critical > Justification: breaks the whole system > > > Updating libc on stable breaks sshd; it dies with a SIGSYS on > clock_nanosleep. I agree it might be worth

Bug#965173: [Pkg-javascript-devel] Bug#965173: Bug#965173: Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

Le 17/07/2020 à 12:15, Jonas Smedegaard a écrit : > Quoting Pirate Praveen (2020-07-17 11:50:17) >> >> >> On 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk wrote: >>> Source: node-rollup-plugin-buble >>> Version: 0.19.8-2 >>> Severity: serious >>> Tags: ftbfs >>> Control: block 960748 by -1 >>> >>>

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Hello, Same problem here, please provide a fix. Thanks. -- Florent

Bug#964908: tomcat9: Catalina fails to load due to missing MbeansDescriptorsIntrospectionSource

tomcat9 9.0.37-1~bpo10+1 in buster-backports has the same issue I have reinstalled tomcat9 using the 9.0.31-1~deb10u1 packages

Bug#965173: [Pkg-javascript-devel] Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

On 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk wrote: >Source: node-rollup-plugin-buble >Version: 0.19.8-2 >Severity: serious >Tags: ftbfs >Control: block 960748 by -1 > >node-rollup-plugin-buble build depends on the babeljs provides >that will not be in bullseye due to #960748. I think we

Bug#965019: marked as done (mir FTBFS with protobuf 3.12.3)

Your message dated Fri, 17 Jul 2020 10:00:23 + with message-id and subject line Bug#965019: fixed in mir 1.8.0+dfsg1-1 has caused the Debian Bug report #965019, regarding mir FTBFS with protobuf 3.12.3 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#965183: python3-intake{,-doc}: both ship /usr/share/man/man1/intake.1.gz

Package: python3-intake,python3-intake-doc Version: 0.6.0-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

Bug#965183: marked as done (python3-intake{,-doc}: both ship /usr/share/man/man1/intake.1.gz)

Your message dated Fri, 17 Jul 2020 13:18:38 + with message-id and subject line Bug#965183: fixed in intake 0.6.0-3 has caused the Debian Bug report #965183, regarding python3-intake{,-doc}: both ship /usr/share/man/man1/intake.1.gz to be marked as done. This means that you claim that the

Bug#962550: marked as done (libgclib1: ABI break without soname change)

Your message dated Fri, 17 Jul 2020 10:00:14 + with message-id and subject line Bug#962550: fixed in libgclib 0.11.9-2 has caused the Debian Bug report #962550, regarding libgclib1: ABI break without soname change to be marked as done. This means that you claim that the problem has been

Bug#964650: pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

Control: tags -1 help Hi, the new upstream version I've just pushed to git solves the issue that is reported here, but I'm running into a different issue: TypeError: data type 'uint15' not understood Any help is welcome Andreas. -- http://fam-tille.de

Processed: Re: Bug#964650: pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

Processing control commands: > tags -1 help Bug #964650 [src:pydicom] pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 Added tag(s) help. -- 964650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964650 Debian Bug Tracking

Bug#965164:

> Sorry for all the inconvenience :-/ I clearly didn't test this properly Don't worry, we are running Sid so we are prepared for this :-). Keep the good job, and thanks for your work anyway! Jonathan Marsaud

Bug#965173: [Pkg-javascript-devel] Bug#965173: Bug#965173: node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye

Quoting Pirate Praveen (2020-07-17 11:50:17) > > > On 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk wrote: > >Source: node-rollup-plugin-buble > >Version: 0.19.8-2 > >Severity: serious > >Tags: ftbfs > >Control: block 960748 by -1 > > > >node-rollup-plugin-buble build depends on the babeljs

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

oh, sorry, libc actually is from unstable... why was that installed with "apt upgrade -t stable"?

Processed: py2removal bugs severity updates - 2020-07-17 13:45:31.171797+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Bug#964650: marked as done (pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

Your message dated Fri, 17 Jul 2020 14:38:28 + with message-id and subject line Bug#964650: fixed in pydicom 2.0.0-1 has caused the Debian Bug report #964650, regarding pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be

Bug#965207: haskell-yi-rope: Removal notice: unmaintained

Source: haskell-yi-rope Version: 0.11-2 Severity: grave Justification: renders package unusable The Yi package is unmaintained (see https://bugs.debian.org/965206). This package is only useful to Yi, so if we remove Yi, we should also remove this one. -- Ilias

Bug#965164: (no subject)

Cody Brownstein: > Is there a suggested fix for those who entirely cannot boot into their > system to upgrade the broken package? > > During boot with the broken package installed, I get: > > [FAILED] Failed to start Authorization Manager. Please kindly disregard. I fixed the issue by

Processed: Re: Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready

Processing control commands: > reopen 964670 Bug #964670 {Done: Mike Gabriel } [src:gsettings-qt] gsettings-qt: FTBFS: QQmlComponent: Component is not ready 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add

Processed: 936508 versions

Processing commands for cont...@bugs.debian.org: > notfound 936508 fdb/2.0.0-1.1 Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye Ignoring request to alter found versions of bug #936508 to the same values previously set > found 936508 fdb/2.0.1-1 Bug #936508 [src:fdb] fdb: Python2

Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready

Control: reopen 964670 X-Debbugs-CC: sunwea...@debian.org Hi Mike, It seems that the latest upload still did not solve this problem and all buildd builds are failing. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part

Bug#965193: [Pkg-utopia-maintainers] Bug#965193: Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Am 17.07.20 um 16:29 schrieb Michael Biebl: > Control: notfound 965164 0.105-26 > Control: forcemerge -1 965164 > > Am 17.07.20 um 15:29 schrieb Vincent Lefevre: >> Note: The bug is not present in 0.105-26, thus this is a different >> bug from 965164 (or the metadata have been messed up in bug

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

I agree it might be worth backporting this fix, but why would you be updating libc on stable? (The only reason I can think of would be partial upgrades to bullseye, which is hardly Severity: critical yet.) I did # apt-get upgrade -t stable got a new libc, and SSH broke. What data

Processed: tagging 965207

Processing commands for cont...@bugs.debian.org: > tags 965207 + bullseye sid Bug #965207 [src:haskell-yi-rope] haskell-yi-rope: Removal notice: unmaintained Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 965207:

Processed: tagging 965206

Processing commands for cont...@bugs.debian.org: > tags 965206 + bullseye sid Bug #965206 [src:haskell-yi-language] haskell-yi-language: Removal notice: broken and unmaintained Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#964908:

i have narrowed to problem down to an old version of the bnd tool. bnd in the debian repos is 3.5.0 - which seemed to work for tomcat9 up to 9.0.36. tomcat9 9.0.37 changed the format of the bnd-file res/bnd/tomcat-coyote.jar.tmp.bnd to use the instruction "-includepackage:" which is only

Bug#965193: [Pkg-utopia-maintainers] Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Control: notfound 965164 0.105-26 Control: forcemerge -1 965164 Am 17.07.20 um 15:29 schrieb Vincent Lefevre: > Note: The bug is not present in 0.105-26, thus this is a different > bug from 965164 (or the metadata have been messed up in bug 965164, > which is ignored by apt-listbugs when

Processed: Re: [Pkg-utopia-maintainers] Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Processing control commands: > notfound 965164 0.105-26 Bug #965164 {Done: Michael Biebl } [policykit-1] policykit-1: fails to install Bug #965165 {Done: Michael Biebl } [policykit-1] policykit-1: polkit.service broken after switch to /usr/libexec No longer marked as found in versions

Bug#965193: [Pkg-utopia-maintainers] Bug#965193: Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

On 2020-07-17 16:47:33 +0200, Michael Biebl wrote: > Am 17.07.20 um 16:29 schrieb Michael Biebl: > > Am 17.07.20 um 15:29 schrieb Vincent Lefevre: > >> Note: The bug is not present in 0.105-26, thus this is a different > >> bug from 965164 (or the metadata have been messed up in bug 965164, > >>

Bug#965164: (no subject)

Michael Biebl: > Sorry for all the inconvenience :-/ > I clearly didn't test this properly. It's a risk we always face running unstable. :-) Is there a suggested fix for those who entirely cannot boot into their system to upgrade the broken package? During boot with the broken package

Bug#964760: marked as done (chromium: Chromium 83.0.4103.116-2 crash : SEGV_MAPERR)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding chromium: Chromium 83.0.4103.116-2 crash : SEGV_MAPERR to be marked as done. This means that you claim

Bug#964287: marked as done (chromium: crashes after page interaction due to a double free)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding chromium: crashes after page interaction due to a double free to be marked as done. This means that you

Bug#964362: marked as done (chromium crash frequently, SEGV_MAPERR)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding chromium crash frequently, SEGV_MAPERR to be marked as done. This means that you claim that the problem

Bug#964451: marked as done (chromium (83.0.4103.116-1~deb10u2) constantly crashes and slow)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding chromium (83.0.4103.116-1~deb10u2) constantly crashes and slow to be marked as done. This means that you

Bug#964334: marked as done (segfault repeatedly)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding segfault repeatedly to be marked as done. This means that you claim that the problem has been dealt with.

Bug#963548: marked as done (Received signal 11 SEGV_MAPERR)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding Received signal 11 SEGV_MAPERR to be marked as done. This means that you claim that the problem has been

Bug#964817: marked as done (chromium 83.0.4103.116-1~deb10u2 crashes frequently)

Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding chromium 83.0.4103.116-1~deb10u2 crashes frequently to be marked as done. This means that you claim that

Processed: 936508 versions

Processing commands for cont...@bugs.debian.org: > fixed 936508 fdb/2.0.0-1.1 Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye Marked as fixed in versions fdb/2.0.0-1.1. > found 936508 fdb/2.0.1-1 Bug #936508 [src:fdb] fdb: Python2 removal in sid/bullseye Ignoring request to alter found

Bug#965206: haskell-yi-language: Removal notice: broken and unmaintained

Source: haskell-yi-language Version: 0.18.0-1 Severity: grave Justification: renders package unusable Forwarded: https://github.com/yi-editor/yi/issues/1114 This package is unmaintained (see [1]). Does not build with newer haskell-regex-base, and is not part of Stackage. Unless someone steps up

Bug#965180: openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!

sorry, my fault. I "had to" upgrade ffmpeg at some time in the past; i ffmpegDepends libavformat58 (= 7:4.3-2) i A libavformat58 Depends libgnutls30 (>= 3.6.14) i libgnutls30 Depends libc6 (>= 2.25) and so I had a newer libc than stable. Sorry about the confusion;

Processed: Re: Bug#964621: fakeroot: FTBFS: tests failed

Processing control commands: > affects -1 d-i Bug #964621 [src:fakeroot] fakeroot: FTBFS: tests failed Added indication that 964621 affects d-i -- 964621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#964044: mrpt: FTBFS: test failure

On Fri, 17 Jul 2020 08:41:13 +0200 Gianfranco Costamagna wrote: > Hello again > > I'm deleting the upload, looks like the new ftdi broke configure script. > > see the attached build log > > G. reuploaded, I gave ftdi a patch, and an upload is coming shortly G.

Bug#965221: src:pwget: fails to migrate to testing for too long: autopkgtest failure

Source: pwget Version: 2016.1019+git75c6e3e-1 Severity: serious Control: close -1 2016.1019+git75c6e3e-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 961456 Dear maintainer(s), As recently announced [1], the Release Team now considers

Processed: src:pwget: fails to migrate to testing for too long: autopkgtest failure

Processing control commands: > close -1 2016.1019+git75c6e3e-3 Bug #965221 [src:pwget] src:pwget: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions pwget/2016.1019+git75c6e3e-3. Bug #965221 [src:pwget] src:pwget: fails to migrate to testing for too long:

Processed: src:gsutil: fails to migrate to testing for too long: autokgtest failure

Processing control commands: > close -1 3.1-3 Bug #965222 [src:gsutil] src:gsutil: fails to migrate to testing for too long: autokgtest failure Marked as fixed in versions gsutil/3.1-3. Bug #965222 [src:gsutil] src:gsutil: fails to migrate to testing for too long: autokgtest failure Marked Bug

Bug#937156: marked as pending in nose

Control: tag -1 pending Hello, Bug #937156 in nose 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#965239: musescore-snapshot: FTBFS against Qt 5.14: error: ambiguous overload for ‘operator<<’

Andreas Beckmann dixit: >musescore-snapshot/experimental recently started to FTBFS, likely due to >some changes in Qt 5.14: Yes, same as #964641. I’m aware, but thank you anyway, in case I hadn’t been aware. This will go away with the next upload, but I’ll handle sid first and have to test some

Processed: Bug#928156 marked as pending in setuptools-scm

Processing control commands: > tag -1 pending Bug #928156 [python3-setuptools-scm] python3-setuptools-scm: uninstallable in stretch-backports: python3-distutils is not a separate package in stretch Added tag(s) pending. -- 928156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928156 Debian

Bug#928156: marked as pending in setuptools-scm

Control: tag -1 pending Hello, Bug #928156 in setuptools-scm 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#965239: musescore-snapshot: FTBFS against Qt 5.14: error: ambiguous overload for ‘operator<<’

Package: musescore-snapshot Version: 3.2.s20190704+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, musescore-snapshot/experimental recently started to FTBFS, likely due to some changes in Qt 5.14: In file included from

Bug#928156: marked as done (python3-setuptools-scm: uninstallable in stretch-backports: python3-distutils is not a separate package in stretch)

Your message dated Fri, 17 Jul 2020 21:52:23 + with message-id and subject line Bug#928156: fixed in setuptools-scm 4.1.2-4 has caused the Debian Bug report #928156, regarding python3-setuptools-scm: uninstallable in stretch-backports: python3-distutils is not a separate package in stretch

Bug#964650: pydicom: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

On Fri, 17 Jul 2020, Andreas Tille wrote: > Control: tags -1 help > Hi, > the new upstream version I've just pushed to git solves the issue thanks! > that is reported here, but I'm running into a different issue: >TypeError: data type 'uint15' not understood I do not understand it

Bug#964621: fakeroot: FTBFS: tests failed

control: affects -1 d-i Hi, On 2020-07-09 13:10, Lucas Nussbaum wrote: > Source: fakeroot > Version: 1.24-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs I am Not sure the bullseye tag is correct here. The version from bullseye/sid FTBFS when built in sid, but

Processed: affects 964621

Processing commands for cont...@bugs.debian.org: > affects 964621 = debian-installer Bug #964621 [src:fakeroot] fakeroot: FTBFS: tests failed Removed indication that 964621 affects d-i Added indication that 964621 affects debian-installer > thanks Stopping processing here. Please contact me if

Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready

Hi, On Fr 17 Jul 2020 16:43:39 CEST, Boyuan Yang wrote: Control: reopen 964670 X-Debbugs-CC: sunwea...@debian.org Hi Mike, It seems that the latest upload still did not solve this problem and all buildd builds are failing. ACK. Will take a look. Mike -- DAS-NETZWERKTEAM c\o Technik- und

Processed: retitle 964621 to fakeroot: statx function not wrapped, causing FTBFS

Processing commands for cont...@bugs.debian.org: > retitle 964621 fakeroot: statx function not wrapped, causing FTBFS Bug #964621 [src:fakeroot] fakeroot: FTBFS: tests failed Changed Bug title to 'fakeroot: statx function not wrapped, causing FTBFS' from 'fakeroot: FTBFS: tests failed'. > thanks

Bug#965224: src:mothur: fails to migrate to testing for too long: FTBFS & autopkgtest regression

Source: mothur Version: 1.42.1-1 Severity: serious Control: close -1 1.44.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 963288 960873 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: src:mothur: fails to migrate to testing for too long: FTBFS & autopkgtest regression

Processing control commands: > close -1 1.44.1-1 Bug #965224 [src:mothur] src:mothur: fails to migrate to testing for too long: FTBFS & autopkgtest regression Marked as fixed in versions mothur/1.44.1-1. Bug #965224 [src:mothur] src:mothur: fails to migrate to testing for too long: FTBFS &

Bug#964617: marked as done (yade: FTBFS: GLViewer.cpp:243:93: error: ‘QString::null’ is deprecated: use QString() [-Werror=deprecated-declarations])

Your message dated Fri, 17 Jul 2020 20:36:22 + with message-id and subject line Bug#964617: fixed in yade 2020.01a-9 has caused the Debian Bug report #964617, regarding yade: FTBFS: GLViewer.cpp:243:93: error: ‘QString::null’ is deprecated: use QString() [-Werror=deprecated-declarations] to

Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error

I cannot reproduce this issue on a new Debian unstable container with searx 0.17.0 and python3-werkzeug 1.0.1 The line referenced in the bug report exists in searx 0.16.0 https://github.com/asciimoo/searx/blob/v0.16.0/searx/webapp.py#L50 I'm using the same container image. The other dependencies

Bug#955054: marked as done (pygments: FTBFS with Sphinx 2.4: Theme error: An error happened in rendering the page docs/api.)

Your message dated Fri, 17 Jul 2020 15:03:55 -0400 with message-id and subject line Re: pygments: FTBFS with Sphinx 2.4: Theme error: An error happened in rendering the page docs/api. has caused the Debian Bug report #955054, regarding pygments: FTBFS with Sphinx 2.4: Theme error: An error

Bug#965222: src:gsutil: fails to migrate to testing for too long: autokgtest failure

Source: gsutil Version: 3.1-1 Severity: serious Control: close -1 3.1-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 961381 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync

Processed: src:opendht: fails to migrate to testing for too long: FTBFS on armel and mipsel

Processing control commands: > close -1 2.1.1-1 Bug #965223 [src:opendht] src:opendht: fails to migrate to testing for too long: FTBFS on armel and mipsel Marked as fixed in versions opendht/2.1.1-1. Bug #965223 [src:opendht] src:opendht: fails to migrate to testing for too long: FTBFS on armel

Processed: closing 965164

Processing commands for cont...@bugs.debian.org: > close 965164 Bug #965164 [policykit-1] policykit-1: fails to install Bug #965165 [policykit-1] policykit-1: polkit.service broken after switch to /usr/libexec Bug #965193 [policykit-1] policykit-1: fails to install: chown error on

  1   2   >