Processed (with 1 error): git-remote-hg unusable due to Python 2 removal

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 971061 src:git-remote-hg 1.0.1~ds-1 Bug #971061 [git-remote-hg] git-remote-hg: Mercurial no longer supports Python 2 Bug reassigned from package 'git-remote-hg' to 'src:git-remote-hg'. No longer marked as found in versions

Bug#972045: marked as done (postgresql-plproxy: autopkgtest regression: make: Makefile: No such file or directory)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 21:35:13 + with message-id and subject line Bug#972045: fixed in postgresql-plproxy 2.10.0-2 has caused the Debian Bug report #972045, regarding postgresql-plproxy: autopkgtest regression: make: Makefile: No such file or directory to be marked as done.

Bug#972118: tpm2-abrmd: Daemon fails to start: needs to be rebuilt against newer libtss2-esys0

2020-10-12 Thread Jan Medlock
Package: tpm2-abrmd Version: 2.3.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, tpm2-abrmd fails to start with the error error while loading shared libraries: libtss2-sys.so.0: cannot open shared object file: No such file or directory I believe this is because the

Bug#972042: marked as done (pg-partman: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv')

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 21:19:35 + with message-id and subject line Bug#972042: fixed in pg-partman 4.4.0-3 has caused the Debian Bug report #972042, regarding pg-partman: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv' to be marked as done. This

Bug#972045: marked as pending in postgresql-plproxy

2020-10-12 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #972045 in postgresql-plproxy 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#972045 marked as pending in postgresql-plproxy

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972045 [src:postgresql-plproxy] postgresql-plproxy: autopkgtest regression: make: Makefile: No such file or directory Added tag(s) pending. -- 972045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972045 Debian Bug Tracking System Contact

Bug#972046: marked as done (postgresql-q3c: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv')

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 21:04:32 + with message-id and subject line Bug#972046: fixed in postgresql-q3c 2.0.0-4 has caused the Debian Bug report #972046, regarding postgresql-q3c: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv' to be marked as done.

Bug#972042: marked as pending in pg-partman

2020-10-12 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #972042 in pg-partman 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#972042 marked as pending in pg-partman

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972042 [src:pg-partman] pg-partman: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv' Added tag(s) pending. -- 972042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972042 Debian Bug Tracking System Contact

Bug#972046: marked as pending in postgresql-q3c

2020-10-12 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #972046 in postgresql-q3c 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#972046 marked as pending in postgresql-q3c

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972046 [src:postgresql-q3c] postgresql-q3c: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv' Added tag(s) pending. -- 972046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972046 Debian Bug Tracking System

Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)

2020-10-12 Thread Étienne Mollier
Hi Andreas, Andreas Tille, on 2020-10-12 17:56:38 +0200: > third_party/cpuid.h:103:3: error: impossible constraint in ‘asm’ > 103 | __asm__ ("cpuid\n\t" \ > | ^~~ > third_party/cpuid.h:162:3: note: in expansion of macro ‘__cpuid’ > 162 | __cpuid (__ext, __eax, __ebx,

Processed: found 972100 in 5.99.0-3, tagging 972100

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 972100 5.99.0-3 Bug #972100 [src:rust-ncurses] CVE-2019-15547 CVE-2019-15548 Marked as found in versions rust-ncurses/5.99.0-3. > tags 972100 + upstream Bug #972100 [src:rust-ncurses] CVE-2019-15547 CVE-2019-15548 Added tag(s) upstream. >

Bug#972105: libeigen3-dev: Eigen::eigen_assert_exception missing from includes of src/Core/products/Parallelizer.h

2020-10-12 Thread Jochen Sprickerhof
Package: libeigen3-dev Version: 3.3.8-2 Severity: serious Tags: patch Justification: breaks build of ceres-solver Hi, Eigen 3.3.8 has bug breaking the ceres-solver build. It was already reported and fixed upstream: https://gitlab.com/libeigen/eigen/-/issues/2011 Please include the patch into

Bug#972100: CVE-2019-15547 CVE-2019-15548

2020-10-12 Thread Moritz Muehlenhoff
Source: rust-ncurses Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team This was assigned CVE-2019-15547 and CVE-2019-15548: https://rustsec.org/advisories/RUSTSEC-2019-0006.html Cheers, Moritz

Bug#945626: marked as done (android-platform-build: Python2 removal in sid/bullseye)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 17:33:35 + with message-id and subject line Bug#945626: fixed in android-platform-build 1:8.1.0+r23-5 has caused the Debian Bug report #945626, regarding android-platform-build: Python2 removal in sid/bullseye to be marked as done. This means that you

Bug#971806: python-hdf5storage's autopkg tests fail in unstable

2020-10-12 Thread Drew Parsons
On 2020-10-13 00:36, Drew Parsons wrote: For instance a recent amd64 error is ERROR: test_write_readback.TestPythonMatlabFormat.test_dtype_structured_with_offsets_titles -- Traceback (most recent call last): File

Bug#971806: python-hdf5storage's autopkg tests fail in unstable

2020-10-12 Thread Drew Parsons
On 2020-10-12 14:23, Graham Inggs wrote: On Mon, 12 Oct 2020 at 05:18, Drew Parsons wrote: Must have been a temporary package inconsistency? All tests are passing now. The autopkgtest looks flaky to me [1]. I see successes and failures with the same triggers. Looks like they might be

Bug#957264: marked as done (gdis: ftbfs with GCC-10)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 16:34:19 + with message-id and subject line Bug#957264: fixed in gdis 0.90-6 has caused the Debian Bug report #957264, regarding gdis: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: Bug#957264 marked as pending in gdis

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #957264 [src:gdis] gdis: ftbfs with GCC-10 Added tag(s) pending. -- 957264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957264: marked as pending in gdis

2020-10-12 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #957264 in gdis 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#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

2020-10-12 Thread dany_wilde
Package: pulseaudio Version: 13.0-5 Followup-For: Bug #904652 X-Debbugs-Cc: compte.perso.de-al...@bbox.fr the solution described here , doesn't work for me . aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: HDMI [HDA ATI HDMI], périphérique 3: HDMI 0 [HDMI 0]

Processed (with 1 error): Re: Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > reopen -a Unknown command or malformed arguments to command. > tags -1 help Bug #972004 {Done: Andreas Tille } [src:bowtie] bowtie ftbfs on several release architectures Ignoring request to alter tags of bug #972004 to the same tags previously set -- 972004:

Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)

2020-10-12 Thread Andreas Tille
Control: reopen -a Control: tags -1 help On Mon, Oct 12, 2020 at 02:50:41PM +0500, Andrey Rahmatullin wrote: > > while I've fixed the issue for arm64 the new version of bowtie seems to > > have some new assembly code where mips64el, ppc64el and others are > > stumbling upon [1]: > The reason it

Bug#966941: libpsl: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-10-12 Thread Lukasz Zemczak
Hello! Since we also saw the same FTBFS in Ubuntu, I have looked into it briefly today. It seems that the test-is-public-builtin data needs to be updated for the test to work as expected. This was fixed in libpsl 0.21.1 per this commit:

Bug#972004: marked as done (bowtie ftbfs on several release architectures)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 15:18:52 + with message-id and subject line Bug#972004: fixed in bowtie 1.3.0+dfsg-3 has caused the Debian Bug report #972004, regarding bowtie ftbfs on several release architectures to be marked as done. This means that you claim that the problem has been

Bug#970215: marked as done (otb-bin: programs fail with symbol lookup error)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 17:00:17 +0200 with message-id and subject line Re: Bug#970215: otb-bin: programs fail with symbol lookup error has caused the Debian Bug report #970215, regarding otb-bin: programs fail with symbol lookup error to be marked as done. This means that you claim

Bug#933865: marked as done (adb crashes on startup with SIGBUS (armhf))

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 15:03:59 + with message-id and subject line Bug#933865: fixed in android-platform-external-boringssl 8.1.0+r23-3 has caused the Debian Bug report #933865, regarding adb crashes on startup with SIGBUS (armhf) to be marked as done. This means that you claim

Processed: Re: Bug#970215: otb-bin: programs fail with symbol lookup error

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 970215 otb/7.2.0~rc2+dfsg-1~exp1 Bug #970215 [otb-bin] otb-bin: programs fail with symbol lookup error Marked as fixed in versions otb/7.2.0~rc2+dfsg-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#969622: gnome-shell-extension-log-out-button: fails to load: TypeError: System._createActionButton is not a function

2020-10-12 Thread Paul Wise
On Mon, 2020-10-12 at 15:35 +0200, Kyle Robbertze wrote: > I'm going to consider requesting the removal of this package from > unstable in the next while unless there is any other opinions. That seems reasonable. Personally I wanted an extension to move the "Power Off / Log Out" menu items to

Bug#969622: gnome-shell-extension-log-out-button: fails to load: TypeError: System._createActionButton is not a function

2020-10-12 Thread Kyle Robbertze
It seems that the extension isn't actually useful in GNOME 3.36 - gnome-shell includes a log out button in the list of Power Off/Log Out options and has removed the icons completely. I'm going to consider requesting the removal of this package from unstable in the next while unless there is any

Processed: src:rheolef: rheolef FTBFS: ...cut-bisector.eps: No such file or directory

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 971933 + ftbfs Bug #971933 [src:rheolef] src:rheolef: rheolef FTBFS: ...cut-bisector.eps: No such file or directory Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 971933:

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

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 11:03:25 + with message-id and subject line Bug#970901: fixed in black 20.8b1-2 has caused the Debian Bug report #970901, regarding diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be

Bug#970901: marked as done (black: cannot run, "ModuleNotFoundError: No module named '_black_version'")

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 11:03:25 + with message-id and subject line Bug#970901: fixed in black 20.8b1-2 has caused the Debian Bug report #970901, regarding black: cannot run, "ModuleNotFoundError: No module named '_black_version'" to be marked as done. This means that you claim

Processed: Re: Processed (with 1 error): Re: gr-gsm: FTBFS on mips64el

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 970051 important Bug #970051 [src:gr-gsm] gr-gsm: FTBFS on mips64el Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 970051:

Processed (with 2 errors): Re: Bug#972080: routine-update: Sometimes deletes manually added python3 dependency

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > severity 961492 important Bug #961492 [dh-r] dh-update-R removes non-R dependencies" Severity set to 'important' from 'grave' > merge -1 961492 Bug #972080 [routine-update] routine-update: Sometimes deletes manually added python3 dependency Unable to merge bugs

Bug#971137: marked as done (grml2usb: FTBFS: ModuleNotFoundError: No module named '_black_version')

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 11:03:25 + with message-id and subject line Bug#970901: fixed in black 20.8b1-2 has caused the Debian Bug report #970901, regarding grml2usb: FTBFS: ModuleNotFoundError: No module named '_black_version' to be marked as done. This means that you claim that

Bug#970759: marked as done (normaliz: Wrong e-mail address in Maintainer field)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 10:54:44 + with message-id and subject line Bug#970759: fixed in normaliz 3.8.9+ds-0.1 has caused the Debian Bug report #970759, regarding normaliz: Wrong e-mail address in Maintainer field to be marked as done. This means that you claim that the problem

Bug#969794: marked as done (normaliz: FTBFS with flint 2.6.3)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 10:54:44 + with message-id and subject line Bug#969794: fixed in normaliz 3.8.9+ds-0.1 has caused the Debian Bug report #969794, regarding normaliz: FTBFS with flint 2.6.3 to be marked as done. This means that you claim that the problem has been dealt

Bug#970051: gr-gsm: FTBFS on mips64el

2020-10-12 Thread Petter Reinholdtsen
Control: status -1 important [Sebastian Ramacher] > Justification: fails to build from source (but built successfully in the past) > > The rebuild of gr-gsm for the gnuradio transition failed to build on > mips64el: According to

Processed (with 2 errors): Re: Bug#972080: routine-update: Sometimes deletes manually added python3 dependency

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > merge -1 961492 Bug #972080 [routine-update] routine-update: Sometimes deletes manually added python3 dependency Unable to merge bugs because: severity of #961492 is 'grave' not 'important' package of #961492 is 'dh-r' not 'routine-update' Failed to merge 972080:

Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)

2020-10-12 Thread Andrey Rahmatullin
On Mon, Oct 12, 2020 at 11:36:36AM +0200, Andreas Tille wrote: > Control: tags -1 help > > Hi, > > while I've fixed the issue for arm64 the new version of bowtie seems to > have some new assembly code where mips64el, ppc64el and others are > stumbling upon [1]: The reason it works on arm64 is

Bug#971972: vde-switch,vde-wirefilter,vdeplug: Miissing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1"

2020-10-12 Thread crvi c
Unpacking vde-switch (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-3FOuDD/77-vde-switch_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/vde_switch', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vde-wirefilter.

Processed: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #972004 [src:bowtie] bowtie ftbfs on several release architectures Added tag(s) help. -- 972004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)

2020-10-12 Thread Andreas Tille
Control: tags -1 help Hi, while I've fixed the issue for arm64 the new version of bowtie seems to have some new assembly code where mips64el, ppc64el and others are stumbling upon [1]: ...In file included from ebwt_build.cpp:8: ds.h: In function ‘void mkeyQSortSuf2(const T&, size_t,

Bug#957653: marked as done (otb: ftbfs with GCC-10)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 10:00:17 + with message-id and subject line Bug#957653: fixed in otb 7.2.0~rc2+dfsg-1~exp1 has caused the Debian Bug report #957653, regarding otb: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#958620: marked as done (sanlock: Build-Depends on deprecated dh-systemd which is going away)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 10:00:31 + with message-id and subject line Bug#958620: fixed in sanlock 3.8.2-1 has caused the Debian Bug report #958620, regarding sanlock: Build-Depends on deprecated dh-systemd which is going away to be marked as done. This means that you claim that

Bug#954678: node-xterm: FTBFS: src/renderer/ColorManager.test.ts(12,18): error TS2694: Namespace '"/usr/share/nodejs/@types/jsdom/ts3.1/index"' has no exported member 'JSDOM'.

2020-10-12 Thread Xavier
node-xterm is incompatible with current tsc. It requires ^3.5.3. I tried to fix it but without success

Processed: Re: Bug#972004: marked as done (bowtie ftbfs on several release architectures)

2020-10-12 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #972004 {Done: Andreas Tille } [src:bowtie] bowtie ftbfs on several release architectures '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 them. Bug reopened No

Bug#972004: marked as done (bowtie ftbfs on several release architectures)

2020-10-12 Thread Andreas Tille
Control: reopen -1 Mips64el and ppc64el are showing ... /tmp/ccRHXYbX.s: Assembler messages: /tmp/ccRHXYbX.s:27483: Error: unrecognized opcode: `popcntq' /tmp/ccRHXYbX.s:27951: Error: unrecognized opcode: `popcntq' /tmp/ccRHXYbX.s:28493: Error: unrecognized opcode: `popcntq'

Processed: freefem++: ftbfs with GCC-10

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 957233 + ftbfs Bug #957233 [src:freefem++] freefem++: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957233

Bug#972074: r-cran-bayestestr: autopkgtest regression

2020-10-12 Thread Graham Inggs
Source: r-cran-bayestestr Version: 0.7.2-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the removal of r-cran-rstanarm from testing on 2020-07-22, r-cran-bayestestr's autopkgtests have been

Bug#970754: marked as done (e-antic: Wrong e-mail address in Maintainer field)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 07:48:35 + with message-id and subject line Bug#970754: fixed in e-antic 0.1.8+ds-0.1 has caused the Debian Bug report #970754, regarding e-antic: Wrong e-mail address in Maintainer field to be marked as done. This means that you claim that the problem has

Bug#972004: marked as done (bowtie ftbfs on several release architectures)

2020-10-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Oct 2020 07:48:28 + with message-id and subject line Bug#972004: fixed in bowtie 1.3.0+dfsg-2 has caused the Debian Bug report #972004, regarding bowtie ftbfs on several release architectures to be marked as done. This means that you claim that the problem has been

Processed: bug 972051 is forwarded to https://github.com/mruby/mruby/issues/5042, tagging 972051

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 972051 https://github.com/mruby/mruby/issues/5042 Bug #972051 [mruby] CVE-2020-15866 Set Bug forwarded-to-address to 'https://github.com/mruby/mruby/issues/5042'. > tags 972051 + upstream Bug #972051 [mruby] CVE-2020-15866 Added tag(s)

Processed: found 972050 in 3.0-1

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 972050 3.0-1 Bug #972050 [src:ndpi] CVE-2020-11939 CVE-2020-11940 CVE-2020-15471 CVE-2020-15472 CVE-2020-15473 CVE-2020-15474 CVE-2020-15475 CVE-2020-15476 Marked as found in versions ndpi/3.0-1. > thanks Stopping processing here. Please

Processed: tagging 972050

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 972050 + upstream Bug #972050 [src:ndpi] CVE-2020-11939 CVE-2020-11940 CVE-2020-15471 CVE-2020-15472 CVE-2020-15473 CVE-2020-15474 CVE-2020-15475 CVE-2020-15476 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if

Processed: tagging 972053

2020-10-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 972053 + upstream Bug #972053 [gpac] CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165 CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629 CVE-2019-20630 CVE-2019-20631 CVE-2019-20632 CVE-2020-11558 CVE-2020-6630

Bug#971806: python-hdf5storage's autopkg tests fail in unstable

2020-10-12 Thread Graham Inggs
On Mon, 12 Oct 2020 at 05:18, Drew Parsons wrote: > Must have been a temporary package inconsistency? > > All tests are passing now. The autopkgtest looks flaky to me [1]. I see successes and failures with the same triggers. [1]

Bug#972070: bluez-obexd: Failure to browse files, Failed to execute program org.bluez.obex: No such file or directory

2020-10-12 Thread Boris Shtrasman
Package: bluez-obexd Version: 5.55-1 Severity: grave X-Debbugs-Cc: borissh1983+b...@gmail.com Dear Maintainer, After upgrading to 5.55-1 (from 5.50), I no longer able to browse files on connected bluetooth device. I had tried to browse files via plasma's bluetooth deamon (bluedevil?) and was