Bug#935182: Concurrent file open results file deletion by the read-only instance

Hi, Actually, we were almost certain that the problem will be forwarded to the upstream, so we openned the bug on Document Fondation too. We also tryed with the backports version, the problem is there too. -- Gilles MOREL Ce message ne s'autodétruira pas dans cinq secondes. Cinq, quatre, trois,

Bug#935182: Concurrent file open results file deletion by the read-only instance

Hi, For severity, I read severity's description and the first that seemed to fit was grave, since I got data loss. For multiple user on the same host, the host is actually a RDP server, served by xrdp. For the version, that's because I tryed to use the backports version of LO, but the problem i

Processed: bug 934886 is forwarded to https://github.com/h2o/h2o/issues/2090

Processing commands for cont...@bugs.debian.org: > forwarded 934886 https://github.com/h2o/h2o/issues/2090 Bug #934886 {Done: Anton Gladky } [src:h2o] CVE-2019-9512 CVE-2019-9514 CVE-2019-9515 Ignoring request to change the forwarded-to-address of bug#934886 to the same value > thanks Stopping p

Processed: found 934886 in 2.2.5+dfsg2-2

Processing commands for cont...@bugs.debian.org: > found 934886 2.2.5+dfsg2-2 Bug #934886 {Done: Anton Gladky } [src:h2o] CVE-2019-9512 CVE-2019-9514 CVE-2019-9515 Marked as found in versions h2o/2.2.5+dfsg2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 9348

Bug#875208: [tora] Future Qt4 removal from Buster

On Fri, 09 Aug 2019 13:15:21 -0400 Scott Kitterman wrote: > On Sat, 9 Sep 2017 23:11:23 +0200 Lisandro =?iso-8859-1?Q? > Dami=E1n_Nicanor_P=E9rez?= Meyer wrote: > > Source: tora > > Version: 2.1.3-3 > > Severity: wishlist > > User: debian-qt-...@lists.debian.org > > Usertags: qt4-removal > > >

Bug#925650: marked as done (chasen: ftbfs with GCC-9)

Your message dated Wed, 21 Aug 2019 00:49:29 + with message-id and subject line Bug#925650: fixed in chasen 2.4.5-44 has caused the Debian Bug report #925650, regarding chasen: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#934992: marked as done (boot-smoke autopkgtest fails if polkitd is not D-Bus activated)

Your message dated Tue, 20 Aug 2019 23:10:41 + with message-id and subject line Bug#934992: fixed in systemd 242-3 has caused the Debian Bug report #934992, regarding boot-smoke autopkgtest fails if polkitd is not D-Bus activated to be marked as done. This means that you claim that the proble

Processed: Bug#931921 marked as pending in clutter-1.0

Processing control commands: > tag -1 pending Bug #931921 [clutter-1.0-tests] clutter's autopkgtests hang when ran with a libglib2.0-0 built with gcc-9 Added tag(s) pending. -- 931921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931921 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#931921: marked as pending in clutter-1.0

Control: tag -1 pending Hello, Bug #931921 in clutter-1.0 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/gnome-team/clutter/commit/1271f596ce8f0a8f0e965cdd1e50

Processed: tagging 880276

Processing commands for cont...@bugs.debian.org: > # Version tracking is fine... > tags 880276 - buster stretch Bug #880276 [src:ruby-encryptor] test using GCM with IV option fails after fix for CVE-2016-7798 Removed tag(s) buster and stretch. > thanks Stopping processing here. Please contact me

Processed: Bug#934992 marked as pending in systemd

Processing control commands: > tag -1 pending Bug #934992 [systemd] boot-smoke autopkgtest fails if polkitd is not D-Bus activated Added tag(s) pending. -- 934992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#934992: marked as pending in systemd

Control: tag -1 pending Hello, Bug #934992 in systemd 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/systemd-team/systemd/commit/af25bbb8f6624ae81f3b39c18154e9

Processed: tagging 931921, bug 931921 is forwarded to https://gitlab.gnome.org/GNOME/clutter/issues/8

Processing commands for cont...@bugs.debian.org: > tags 931921 = upstream Bug #931921 [clutter-1.0-tests] clutter's autopkgtests hang when ran with a libglib2.0-0 built with gcc-9 Removed tag(s) moreinfo. > forwarded 931921 https://gitlab.gnome.org/GNOME/clutter/issues/8 Bug #931921 [clutter-1.0-

Bug#932015: marked as done (wireguard-dkms: Wireguard dkms module build fails with gcc-8 on arm for 4.19.0-5-armmp-lpae kernel)

Your message dated Tue, 20 Aug 2019 18:06:31 -0400 with message-id <878srnebko@fifthhorseman.net> and subject line Re: Bug#932015: wireguard-dkms: Wireguard dkms module build fails with gcc-8 on arm for 4.19.0-5-armmp-lpae kernel has caused the Debian Bug report #932015, regarding wireguard-dk

Bug#932015: wireguard-dkms: Wireguard dkms module build fails with gcc-8 on arm for 4.19.0-5-armmp-lpae kernel

On Tue 2019-08-20 22:36:07 +0200, Martin Höfling wrote: > first of all, my bananapi 2 died and I will replace it, probably with a > newer arm board. ouch, sorry to hear that. > Package: linux-headers-4.19.0-5-armmp-lpae > Version: 4.19.37-5+deb10u1 > > Package: linux-headers-4.19.0-5-common > Ver

Bug#925695: marked as done (giada: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 21:35:46 + with message-id and subject line Bug#925695: fixed in giada 0.15.4+ds1-1 has caused the Debian Bug report #925695, regarding giada: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: Bug#931921: clutter's autopkgtests hang when ran with a libglib2.0-0 built with gcc-9

Processing control commands: > reassign -1 clutter-1.0-tests Bug #931921 [src:gcc-9] clutter's autopkgtests hang when ran with a libglib2.0-0 built with gcc-9 Bug reassigned from package 'src:gcc-9' to 'clutter-1.0-tests'. No longer marked as found in versions gcc-9/9.1.0-8. Ignoring request to a

Bug#928993: marked as done (sdaps: Please package the latest upstream version)

Your message dated Tue, 20 Aug 2019 21:12:22 + with message-id and subject line Bug#928993: fixed in sdaps 1.9.7-0.1~exp1 has caused the Debian Bug report #928993, regarding sdaps: Please package the latest upstream version to be marked as done. This means that you claim that the problem has

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

Hi Antoine, > Thanks for writing the patch! I tested it on > . For some reason it didn't > apply cleanly to debian/rules Mea culpa; there was another upload in the meantime that I somehow did not spot. I have now correctly subscribed to this package in

Bug#934886: marked as done (CVE-2019-9512 CVE-2019-9514 CVE-2019-9515)

Your message dated Tue, 20 Aug 2019 21:08:27 + with message-id and subject line Bug#934886: fixed in h2o 2.2.5+dfsg2-3 has caused the Debian Bug report #934886, regarding CVE-2019-9512 CVE-2019-9514 CVE-2019-9515 to be marked as done. This means that you claim that the problem has been dealt

Bug#874829: marked as done ([basket] Future Qt4 removal from Buster)

Your message dated Tue, 20 Aug 2019 21:04:55 + with message-id and subject line Bug#874829: fixed in basket 2.49-1 has caused the Debian Bug report #874829, regarding [basket] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with.

Bug#932015: wireguard-dkms: Wireguard dkms module build fails with gcc-8 on arm for 4.19.0-5-armmp-lpae kernel

On 20.08.19 00:38, Daniel Kahn Gillmor wrote: Hi Daniel, first of all, my bananapi 2 died and I will replace it, probably with a newer arm board. >>* What led up to the situation? >> >>Upgrading to buster and to kernel 4.19.0-5-armmp-lpae > > this is a package name, and not a package vers

Bug#935154: goopg depends on cruft package

You may want to file this upstream. https://github.com/LeoIannacone/goopg/issues On Tue, Aug 20, 2019 at 5:39 AM peter green wrote: > > Package: goopg > Version: 0.3.1-9 > Severity: serious > > goopg depends on the python-oauth2client binary package which is no longer > built by the python-oaut

Bug#934957: cups: multiple security issues (including CVEified CVE-2019-8675 and CVE-2019-8696)

clone -1 -2 reassign -2 release.debian.org retitle -2 buster-pu: package cups/2.2.10-6+deb10u1 user release.debian@packages.debian.org usertags -1 pu clone -1 -3 reassign -3 release.debian.org retitle -3 stretch-pu: package cups/2.2.1-8+deb9u3 user release.debian@packages.debian.org usertag

Bug#928993: Uploading new release of sdaps onto Debian experimental

Dear sdaps maintainers, Since sdaps in Debian Sid is now broken, I'm preparing a new upload (NMU) for sdaps and uploading it onto experimental first. I have made some preliminary tests first but did not test the new version extensively. If you find it okay, please feel free to upload it onto unst

Processed: found 935182 in 1:6.1.5-1

Processing commands for cont...@bugs.debian.org: > found 935182 1:6.1.5-1 Bug #935182 [libreoffice-core] Concurrent file open on the same host results file deletion Marked as found in versions libreoffice/1:6.1.5-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#934957: cups: multiple security issues (including CVEified CVE-2019-8675 and CVE-2019-8696)

Control: tags -1 +pending Le samedi, 17 août 2019, 11.34:01 h CEST Salvatore Bonaccorso a écrit : > Filling for tracking. The recent 2.2.12[1] release includes fixes for > several security issues, two of those got CVEs and are related to SNMP > buffer overflows. [2] includes all those. I had alre

Processed: Re: Bug#934957: cups: multiple security issues (including CVEified CVE-2019-8675 and CVE-2019-8696)

Processing control commands: > tags -1 +pending Bug #934957 {Done: Didier Raboud } [src:cups] cups: multiple security issues (including CVEified CVE-2019-8675 and CVE-2019-8696) Added tag(s) pending. -- 934957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934957 Debian Bug Tracking System

Bug#932614: marked as done (basemap: pyproj upstream going to drop Python 2 support)

Your message dated Tue, 20 Aug 2019 17:49:22 + with message-id and subject line Bug#932614: fixed in basemap 1.2.0+dfsg-2 has caused the Debian Bug report #932614, regarding basemap: pyproj upstream going to drop Python 2 support to be marked as done. This means that you claim that the proble

Bug#935092: Serious issues with inetsim in Debian 10

> The postinst script of the Debian 10 package copies all files from > /usr/share to /var/lib, including the files in data/certs. > So it will a) overwrite existing certificate files and b) never > generate a custom certficate. Correction: The package does not overwrite existing certificate files

Bug#925737: marked as done (libbpp-seq-omics: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 17:21:16 + with message-id and subject line Bug#925737: fixed in libbpp-seq-omics 2.4.1-4 has caused the Debian Bug report #925737, regarding libbpp-seq-omics: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt

Bug#934600: marked as done (cufflinks,gffread: both ship /usr/bin/gffread)

Your message dated Tue, 20 Aug 2019 17:20:01 + with message-id and subject line Bug#934600: fixed in cufflinks 2.2.1+dfsg.1-4 has caused the Debian Bug report #934600, regarding cufflinks,gffread: both ship /usr/bin/gffread to be marked as done. This means that you claim that the problem has

Bug#925732: marked as done (libbpp-phyl: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 17:20:50 + with message-id and subject line Bug#925732: fixed in libbpp-phyl 2.4.1-3 has caused the Debian Bug report #925732, regarding libbpp-phyl: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#932614: marked as pending in basemap

Control: tag -1 pending Hello, Bug #932614 in basemap 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/python-team/modules/basemap/commit/aa627748df17090ea0be79c

Processed: Bug#932614 marked as pending in basemap

Processing control commands: > tag -1 pending Bug #932614 [src:basemap] basemap: pyproj upstream going to drop Python 2 support Added tag(s) pending. -- 932614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#935182: Concurrent file open results file deletion by the read-only instance

Processing commands for cont...@bugs.debian.org: > retitle 935182 Concurrent file open on the same host results file deletion Bug #935182 [libreoffice-core] Concurrent file open results file deletion by the read-only instance Changed Bug title to 'Concurrent file open on the same host results fil

Bug#935182: Concurrent file open results file deletion by the read-only instance

retitle 935182 Concurrent file open on the same host results file deletion thanks Hi, On Tue, Aug 20, 2019 at 06:30:06PM +0200, Rene Engelhard wrote: > On Tue, Aug 20, 2019 at 04:52:52PM +0200, Gilles MOREL wrote: > > Package: libreoffice-core > > Version: 1:6.1.5-3+deb10u3 > > Severity: grave >

Bug#935182: Concurrent file open results file deletion by the read-only instance

forwarded 935182 https://bugs.documentfoundation.org/show_bug.cgi?id=127057 thanks Hi, On Tue, Aug 20, 2019 at 06:30:06PM +0200, Rene Engelhard wrote: > LO has lockinbg problems like this. This is nothing new. In fact, quick > googling > just gave me > https://bugs.documentfoundation.org/show_bu

Processed: Re: Bug#935182: Concurrent file open results file deletion by the read-only instance

Processing commands for cont...@bugs.debian.org: > forwarded 935182 https://bugs.documentfoundation.org/show_bug.cgi?id=127057 Bug #935182 [libreoffice-core] Concurrent file open results file deletion by the read-only instance Set Bug forwarded-to-address to 'https://bugs.documentfoundation.org/

Bug#935182: Concurrent file open results file deletion by the read-only instance

Hi, On Tue, Aug 20, 2019 at 04:52:52PM +0200, Gilles MOREL wrote: > Package: libreoffice-core > Version: 1:6.1.5-3+deb10u3 > Severity: grave 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowin

Bug#925745: [Debian-med-packaging] Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

On 8/20/19 3:41 PM, Andreas Tille wrote: > Hi Olivier, > > I'm just forwarding this to Debian Mentors list to get a wider audience. > I'd prefer a fix over simply removing the test ... commenting in text_line_reader.h:         // operator const std::string& () const { return line_string()

Bug#925795: marked as done (openblas: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 17:43:44 +0200 with message-id <34e4ea0c08592f34461bd02677ac95fe55eed287.ca...@debian.org> and subject line Re: Bug#925795: openblas: ftbfs with GCC-9 has caused the Debian Bug report #925795, regarding openblas: ftbfs with GCC-9 to be marked as done. This means

Bug#875036: How does this affect the Qt 5 binaries?

I maintain a package (src:gudhi) that build-depends on libqglviewer-dev-qt5 and depends on libqglviewer2-qt5. As a relatively fresh DM, I haven't experienced depending on a to-be-removed package yet, so I'm a bit confused. Are *all* binaries built from src:libqglviewer to be removed? If yes, why a

Bug#935182: Concurrent file open results file deletion by the read-only instance

Package: libreoffice-core Version: 1:6.1.5-3+deb10u3 Severity: grave Hello, When two users on the same machine open the same file from a samba share, the second gets a notice about the file to be openned in read-only mode. If the first user saves modification while the second user have the file

Processed: Bumping Qt 4 bugs to RC

Processing commands for cont...@bugs.debian.org: > severity 875086 serious Bug #875086 [src:paraview] [paraview] Future Qt4 removal from Buster Severity set to 'serious' from 'wishlist' > severity 875500 serious Bug #875500 [src:seascope] Qt4 removal form Buster Severity set to 'serious' from 'nor

Processed: Re: Bug#843897: Should allow pyqt5

Processing control commands: > severity -1 serious Bug #843897 [python-pyqtgraph] Should allow pyqt5 Severity set to 'serious' from 'normal' -- 843897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#925759: marked as done (libseqlib: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 14:47:59 + with message-id and subject line Bug#925759: fixed in libseqlib 1.1.2+dfsg-4 has caused the Debian Bug report #925759, regarding libseqlib: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#925736: marked as done (libbpp-seq: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 14:46:58 + with message-id and subject line Bug#925736: fixed in libbpp-seq 2.4.1-4 has caused the Debian Bug report #925736, regarding libbpp-seq: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#925731: marked as done (libbpp-core: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 14:46:51 + with message-id and subject line Bug#925731: fixed in libbpp-core 2.4.1-4 has caused the Debian Bug report #925731, regarding libbpp-core: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: Re: Qt4 will be in buster, so no point forcing rdeps out

Processing commands for cont...@bugs.debian.org: > severity 914307 serious Bug #914307 [src:pyqwt5] src:pyqwt5: Should not ship with buster Severity set to 'serious' from 'important' > severity 891994 serious Bug #891994 [epigrass] epigrass: Depends on Qt4-only python-qwt5-qt4 Severity set to 'ser

Processed: Re: Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae

Processing control commands: > reassign -1 src:linux Bug #934483 [virtualbox-guest-dkms] virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae Bug reassigned from package 'virtualbox-guest-dkms' to 'src:linux'. No longer marked as found in versions virtualbox/6.0.10-

Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae

control: reassign -1 src:linux control: affects -1 virtualbox-guest-dkms control: found -1 5.2.9-1 On Mon, 19 Aug 2019 19:02:52 +0200 Raphael Hertzog wrote: > On Sun, 11 Aug 2019, Christian Marillat wrote: > > But bevare fixind the include file path (drm/ttm/ttm_page_alloc.h) doesn't > > work at

Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

Hi Olivier, I'm just forwarding this to Debian Mentors list to get a wider audience. I'd prefer a fix over simply removing the test ... Thanks for your analysis anyway Andreas. On Tue, Aug 20, 2019 at 03:36:48PM +0200, Olivier Sallou wrote: > > On 8/20/19 1:24 PM, Andreas Tille wrote: > >

Bug#925752: marked as done (libncl: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 13:36:55 + with message-id and subject line Bug#925752: fixed in libncl 2.1.21+git20190531.feceb81-1 has caused the Debian Bug report #925752, regarding libncl: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt

Bug#925659: marked as done (cpl-plugin-muse: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 13:35:16 + with message-id and subject line Bug#925659: fixed in cpl-plugin-muse 2.6.2+dfsg-1 has caused the Debian Bug report #925659, regarding cpl-plugin-muse: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dea

Bug#925745: [Debian-med-packaging] Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

On 8/20/19 1:24 PM, Andreas Tille wrote: > Control: tags -1 help > > Hi, > > any hint how to deal with this is a test file. In test, there is explicit conversion to string: line = reader.line_string() ; //first line - with explicit method to get the string which works fine as expected In gcc

Processed: Bug#925695 marked as pending in giada

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

Bug#925695: marked as pending in giada

Control: tag -1 pending Hello, Bug #925695 in giada 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/multimedia-team/giada/commit/7f9387a0268eb87e9ed384407b3aa9f

Bug#925700: marked as done (gnucash: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 12:54:59 + with message-id and subject line Bug#925700: fixed in gnucash 1:3.6-1 has caused the Debian Bug report #925700, regarding gnucash: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Processed: Increasing severities

Processing commands for cont...@bugs.debian.org: > severity 875318 serious Bug #875318 [src:kdepimlibs] QJson removal form Buster Severity set to 'serious' from 'important' > severity 875321 serious Bug #875321 [src:openambit] QJson removal form Buster Bug #875327 [src:openambit] QJson removal in

Bug#925723: marked as done (juce: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 12:22:33 + with message-id and subject line Bug#925723: fixed in juce 5.4.4~repack0-1 has caused the Debian Bug report #925723, regarding juce: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#874857: [dssi] Future Qt4 removal from Buster - patch available

Hi, On Tue, Aug 20, 2019 at 09:13:25AM +1000, Stuart Prescott wrote: > A patch to disable the generation of the Qt4 example plugins is at […] > (I will merge and upload in a few days if there are no further comments) I think you should just go ahead with that, lgtm. If I have to say one thing, i

Bug#935168: umockdev: runs xorg and leaves spurious process after test run

Source: umockdev Version: 0.13-1 Severity: serious tags: patch Hello, after debugging why the build of umockdev on arm64 was taking days to upload (and then being killed), I added a ps aux before dh_builddeb buildd 17658 1.2 0.4 110676 33536 ?S11:12 0:00 /usr/lib/xorg/Xorg -co

Bug#925731: libbpp-*: ftbfs with GCC-9

Hi Julien, On Tue, Aug 20, 2019 at 11:37:19AM +0200, Julien Dutheil wrote: > All packages compile without warning with gcc 9. I think the issue is (again) > the symbol files, which have to be regenerated. > Honestly, it seems to me that these symbol files brought more issues than > they solved a

Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

Control: tags -1 help Hi, any hint how to deal with ... g++ -DHAVE_CONFIG_H -I. -I.. -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -Wformat-nonliteral -Wformat-security -Wswitch-default -Wswi

Processed: [Help] libgtextutils: ftbfs with GCC-9

Processing control commands: > tags -1 help Bug #925745 [src:libgtextutils] libgtextutils: ftbfs with GCC-9 Added tag(s) help. -- 925745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#925690: marked as done (gatb-core: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 11:20:33 + with message-id and subject line Bug#925690: fixed in gatb-core 1.4.1+git20190813.a73b6dd+dfsg-1 has caused the Debian Bug report #925690, regarding gatb-core: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#934314: GnuTLS race causes HTTPS bad requests

Processing control commands: > reassign 934314 src:emacs 1:26.1+1-3.2 Bug #934314 [emacs] GnuTLS race causes HTTPS bad requests Bug reassigned from package 'emacs' to 'src:emacs'. No longer marked as found in versions emacs/1:26.1+1-3.2. Ignoring request to alter fixed versions of bug #934314 to t

Bug#934314: GnuTLS race causes HTTPS bad requests

Control: reassign 934314 src:emacs 1:26.1+1-3.2 Control: forcemerge 922659 934314 Control: severity 922659 important On August 9, 2019 at 8:32AM -0700, ian (at retrospec.tv) wrote: > Known workarounds involve disabling GnuTLS support or TLS 1.3, both of which > are inadvisable from a security per

Processed: fixed 919049 in 5.0.1-1~exp1

Processing commands for cont...@bugs.debian.org: > fixed 919049 5.0.1-1~exp1 Bug #919049 {Done: Ben Hutchings } [src:linux] posix-cpu-timers: Unbreak timer rearming (regression) Marked as fixed in versions linux/5.0.1-1~exp1. > thanks Stopping processing here. Please contact me if you need assis

Bug#932725: Acknowledgement (libunwind8: segfault on MIPS, fix needs backporting)

Hi Adrian, On 22/07/2019 12:09, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 932725: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932725. > > This is an automatically generated reply to let you know y

Bug#934600: [Debian-med-packaging] Bug#934600: gffread in cufflinks seems to be the same codebase but older

On 8/20/19 7:16 AM, Andreas Tille wrote: > Hi Alexandre, > > it looks as if the gffread code in cufflinks would be the > same code base but the code in gffread source seems to be > more recent. What do you think? > > Kind regards > > Andreas. > > - Forwarded message from Debian te

Bug#925700:

On Tuesday, 20 August 2019 1:43:39 AM AEST Michael Crusoe wrote: > I think this can be worked around by adding -Werror=stringop-truncation to > CXXFLAGS Yes, the following helps, thanks: export DEB_CXXFLAGS_MAINT_APPEND= -Wno-error=stringop-truncation -- All the best, Dmitry Smirnov. --- G

Bug#935156: ceph: Multiple mon deployment failure on arm64: ms_verfity_authorizer bad authorizer and crc check failure

Package: ceph Version: 12.2.11+dfsg1-2.1 Severity: grave Justification: renders package unusable Dear Maintainer, I'm trying to deploy a 2 monitor ceph cluster with 2 arm64 server nodes. root@ceph-node1:~# ceph -v ceph version 12.2.11 (26dc3775efc7bb286a1d6d66faee0ba30ea23eee) luminous (stable)

Bug#935154: goopg depends on cruft package

Package: goopg Version: 0.3.1-9 Severity: serious goopg depends on the python-oauth2client binary package which is no longer built by the python-oauth2client source package. If you want your package to be in bullseye you need to migrate to python 3 (and fix the other rc bug)

Processed: re: datalad: please drop python-datalad (python 2 removal effort)

Processing commands for cont...@bugs.debian.org: > severity 935015 serious Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal effort) Severity set to 'serious' from 'important' > tags 935015 +bullseye Bug #935015 [src:datalad] datalad: please drop python-datalad (pyth

Bug#935150: mercurial: FTBFS on mips and s390x (zstd-related test failures)

Package: mercurial Version: 5.1-1 Severity: serious Seeing similar-looking test failures on both big-endian archs: https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=s390x&ver=5.1-1&stamp=1565970181&raw=0 https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=mips&ver=5.1-1&stam

Bug#934599: marked as done (python3-grapefruit: missing Breaks+Replaces: python-grapefruit-doc)

Your message dated Tue, 20 Aug 2019 09:04:51 + with message-id and subject line Bug#934599: fixed in grapefruit 0.1~a3+dfsg-8 has caused the Debian Bug report #934599, regarding python3-grapefruit: missing Breaks+Replaces: python-grapefruit-doc to be marked as done. This means that you claim

Bug#934476: marked as done (django-oauth-toolkit non-buildd binary)

Your message dated Tue, 20 Aug 2019 09:02:10 + with message-id and subject line Bug#934476: fixed in django-oauth-toolkit 1.2.0-2 has caused the Debian Bug report #934476, regarding django-oauth-toolkit non-buildd binary to be marked as done. This means that you claim that the problem has bee

Bug#934034: marked as done (monkeysphere: FTBFS in stretch (failing tests))

Your message dated Tue, 20 Aug 2019 08:58:41 + with message-id and subject line Bug#934034: fixed in monkeysphere 0.41-1+deb9u1 has caused the Debian Bug report #934034, regarding monkeysphere: FTBFS in stretch (failing tests) to be marked as done. This means that you claim that the problem h

Processed: Re: Bug#934591: Anki fails to start: ModuleNotFoundError: No module named 'PyQt5.sip'

Processing commands for cont...@bugs.debian.org: > tags 934591 + unreproducible moreinfo Bug #934591 [anki] Anki fails to start: ModuleNotFoundError: No module named 'PyQt5.sip' Added tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#934591: Anki fails to start: ModuleNotFoundError: No module named 'PyQt5.sip'

tags 934591 + unreproducible moreinfo thanks On Mon, Aug 12, 2019 at 01:13:36PM +0200, Arnaldo Pirrone wrote: > Package: anki > Version: 2.1.8+dfsg-1 > Severity: grave > > pyqt5 package is installed > > Traceback (most recent call last): > File "/usr/bin/anki", line 6, in > import aqt >

Bug#925680: marked as done (firefox: ftbfs with GCC-9)

Your message dated Tue, 20 Aug 2019 07:40:45 + with message-id and subject line Bug#925680: fixed in firefox 68.0.2-3 has caused the Debian Bug report #925680, regarding firefox: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#935142: FTBFS arch all

On 8/20/19 8:48 AM, Mike Hommey wrote: > This is presumably fixed in 68.0.2-3 ah, thanks! :) Regards, Daniel