Bug#935496: Fuse 2.9.9-1

Hello, I can confirm this. While upgrading the package works just fine, new installations and reinstallations keep failing. Please let me know if I can be of further assistance. Best regards, Marco.

Bug#935680: marked as done (lower-case.patch: fix to also work under autopkgtest conditions)

Your message dated Mon, 26 Aug 2019 06:07:08 + with message-id and subject line Bug#935680: fixed in python-schema-salad 4.5.20190815125611-3 has caused the Debian Bug report #935680, regarding lower-case.patch: fix to also work under autopkgtest conditions to be marked as done. This means th

Bug#935089: marked as done (FTBFS: error: no dependency information found for /usr/lib/x86_64-linux-gnu/libeckit.so.0d)

Your message dated Mon, 26 Aug 2019 06:06:27 + with message-id and subject line Bug#935089: fixed in metview 5.6.1-2 has caused the Debian Bug report #935089, regarding FTBFS: error: no dependency information found for /usr/lib/x86_64-linux-gnu/libeckit.so.0d to be marked as done. This means

Bug#935575: marked as done (libmetview-dev: libatlas.so is already shipped by libatlas-base-dev)

Your message dated Mon, 26 Aug 2019 06:06:27 + with message-id and subject line Bug#935575: fixed in metview 5.6.1-2 has caused the Debian Bug report #935575, regarding libmetview-dev: libatlas.so is already shipped by libatlas-base-dev to be marked as done. This means that you claim that the

Bug#935702: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

On 26/08/2019 03:28, Guilhem Moulin wrote: > On Sun, 25 Aug 2019 at 12:43:26 +, n...@waifu.club wrote: >> Not only the access to protected data is lost, the integritysetup's "open" >> operation actually succeeds. All reads on the incorrectly created DM device >> will of course fail with I/O err

Bug#931147: gdb depends on newer libbabeltrace

On 2019-08-24 6:12 a.m., Andreas Beckmann wrote: > Followup-For: Bug #931147 > > Hi, > > I've just opened a PU request for babeltrace and a binNMU request > for gdb etc. to get this fixed in buster, too. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935583 > https://bugs.debian.org/cgi-bin/

Processed: Re: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

Processing control commands: > retitle -1 DM device size ≥2³² 512-bits sectors is truncated on 32-bits > platforms Bug #935702 [cryptsetup-bin] Wrong DM device size due to integer truncation Changed Bug title to 'DM device size ≥2³² 512-bits sectors is truncated on 32-bits platforms' from 'Wrong

Bug#935702: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

Control: retitle -1 DM device size ≥2³² 512-bits sectors is truncated on 32-bits platforms Control: tag -1 + upstream Hi, On Sun, 25 Aug 2019 at 12:43:26 +, n...@waifu.club wrote: > Not only the access to protected data is lost, the integritysetup's "open" > operation actually succeeds. All

Bug#875165: Patch set to remove Qt 4 support

On Mon, 19 Aug 2019 15:28:53 -0300 =?UTF-8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= wrote: > This also adds proper .pc files back. > > I also mailed qsapecng's maintainer in #875138. We are free to remove > the package, so we can proceed with this. > > I plan to NMU this package soon

Processed: Tag

Processing commands for cont...@bugs.debian.org: > tag 875165 pending Bug #875165 [src:qwt] [qwt] Future Qt4 removal from Buster Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 875165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875165

Bug#935615: marked as done (aptitude: FTBFS on amd64)

Your message dated Mon, 26 Aug 2019 00:19:34 + with message-id and subject line Bug#935615: fixed in aptitude 0.8.12-1 has caused the Debian Bug report #935615, regarding aptitude: FTBFS on amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#935764: freeipmi: --link-doc between architecture all and not all packages breaks binNMUs

Source: freeipmi Version: 1.6.3-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libfreeipmi17 The recent binNMU on amd64 rendered the freeipmi packages uninstallable because of the --link-doc from an arch:any to an arch:all package. The arch-dependen

Processed: freeipmi: --link-doc between architecture all and not all packages breaks binNMUs

Processing control commands: > affects -1 + libfreeipmi17 Bug #935764 [src:freeipmi] freeipmi: --link-doc between architecture all and not all packages breaks binNMUs Added indication that 935764 affects libfreeipmi17 -- 935764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935764 Debian Bu

Processed: tagging 931944, tagging 931940, tagging 931935, tagging 931914, tagging 935698

Processing commands for cont...@bugs.debian.org: > tags 931944 + sid bullseye Bug #931944 [src:vtk7] vtk7: FTBFS with PROJ 6 Added tag(s) bullseye and sid. > tags 931940 + sid bullseye Bug #931940 [src:sumo] sumo: FTBFS with PROJ 6 Added tag(s) sid and bullseye. > tags 931935 + sid bullseye Bug #9

Bug#935713: marked as done (src:thrift: Incomplete debian/copyright)

Your message dated Sun, 25 Aug 2019 22:07:40 + with message-id and subject line Bug#935713: fixed in thrift 0.11.0-6 has caused the Debian Bug report #935713, regarding src:thrift: Incomplete debian/copyright to be marked as done. This means that you claim that the problem has been dealt with

Bug#935620: thrift: FTBFS on amd64

On Sun, Aug 25, 2019 at 11:55 AM Ivo De Decker wrote: > If you add a new binary package, your upload will go to the NEW queue > (and will have to include binaries). Sorry for the confusion, I meant which is better: upload it via experimental and then do a Sid upload or do a Sid upload and do a bi

Bug#935759: postgresql-9.4: fails to purge: RET=10 postgresql-9.4/postrm_purge_data doesn't exist

Package: postgresql-9.4 Version: 9.4.24-0+deb8u1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. According to policy 7.2 you cannot rely on the depends being available during purge, only the essential pa

Bug#932539: marked as done (qbittorrent: CVE-2019-13640)

Your message dated Sun, 25 Aug 2019 21:22:55 + with message-id and subject line Bug#932539: fixed in qbittorrent 4.1.7-1 has caused the Debian Bug report #932539, regarding qbittorrent: CVE-2019-13640 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#935713: src:thrift: Incomplete debian/copyright

On Sun, Aug 25, 2019 at 4:06 PM Scott Kitterman wrote: > While reviewing your package in New, I noticed omissions from debian/ > copyright. Since this problem also exists in the current package, I am > filing this bug rather than rejecting the package. [...] > lib/php/src/ext/thrift_protocol/run-

Bug#931914: marked as done (octave-octproj: FTBFS with PROJ 6)

Your message dated Sun, 25 Aug 2019 20:47:44 + with message-id and subject line Bug#931914: fixed in octave-octproj 1.1.5-5 has caused the Debian Bug report #931914, regarding octave-octproj: FTBFS with PROJ 6 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#935736: marked as done (Drop dependency on automoc)

Your message dated Sun, 25 Aug 2019 20:47:30 + with message-id and subject line Bug#935736: fixed in meta-kde 5:103 has caused the Debian Bug report #935736, regarding Drop dependency on automoc to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#935733: marked as done (libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS)

Your message dated Sun, 25 Aug 2019 20:39:30 + with message-id and subject line Bug#935733: fixed in bladerf 0.2019.07-3 has caused the Debian Bug report #935733, regarding libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS to be marke

Bug#935592: marked as done (cogl: FTBFS on i386: tests hang indefinitely, possibly during test_pixel_buffer_set_data)

Your message dated Sun, 25 Aug 2019 20:40:54 + with message-id and subject line Bug#935592: fixed in cogl 1.22.4-3 has caused the Debian Bug report #935592, regarding cogl: FTBFS on i386: tests hang indefinitely, possibly during test_pixel_buffer_set_data to be marked as done. This means tha

Bug#935752: gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No such file or directory)

Package: src:gcc-9-cross-mipsen Version: 1+c1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep gcc: 9.2.1-3 / 9.1.0-10cross1 old gcc

Bug#935592: marked as pending in cogl

Control: tag -1 pending Hello, Bug #935592 in cogl 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/cogl/commit/4109d02652132524e44b2591892ca44422e467

Processed: Bug#935592 marked as pending in cogl

Processing control commands: > tag -1 pending Bug #935592 [src:cogl] cogl: FTBFS on i386: tests hang indefinitely, possibly during test_pixel_buffer_set_data Added tag(s) pending. -- 935592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935592 Debian Bug Tracking System Contact ow...@bugs.d

Bug#875038: [lmms] Future Qt4 removal from Buster

A stable lmms 1.2.0 with Qt5 support is already released several months ago. Now it's about someone should be packaging it within Debian. Thanks, Boyuan Yang 在 2019-08-25日的 21:04 +0200，Moritz Mühlenhoff写道： > On Sun, Oct 14, 2018 at 03:16:27AM +0200, Javier Serrano Polo wrote: > > On Fri, 23 Mar 2

Bug#917925: marked as done (Module fails to load on Linux 4.3 or later)

Your message dated Sun, 25 Aug 2019 19:13:45 + with message-id and subject line Bug#935721: Removed package(s) from unstable has caused the Debian Bug report #917925, regarding Module fails to load on Linux 4.3 or later to be marked as done. This means that you claim that the problem has been

Bug#875207: [tipp10] Future Qt4 removal from Buster

On Fri, Aug 23, 2019 at 09:16:57AM +0200, Christoph Martin wrote: > Hi Moritz, > > Am 22.08.19 um 21:47 schrieb Moritz Mühlenhoff: > > > tipp10 seems to be dead upstream (not surprising given that it seems to be > > based on an old diploma thesis) > > > > Are you planning to port it to Qt5 yours

Bug#874911: [hamfax] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 09:05:57PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: hamfax > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced] in: > > In order to make this move, all packages directly or indirectly depending on > the Qt4 librar

Bug#935733: libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS

I got surprised by the result that adding a file to debian/libbladerf-doc.docs resulted in a file being unpacked to /usr/share/doc/libbladerf-dev/ Upload with Breaks:/Replaces: coming soon. -Maitland

Bug#931914: marked as pending in octave-octproj

Control: tag -1 pending Hello, Bug #931914 in octave-octproj 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/pkg-octave-team/octave-octproj/commit/a683eb8245a9d

Processed: severity of 910679 is serious

Processing commands for cont...@bugs.debian.org: > severity 910679 serious Bug #910679 [src:cegui-mk2] cegui-mk2 should build-depend on updated pyside-tools package Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 910679:

Processed: Bug#931914 marked as pending in octave-octproj

Processing control commands: > tag -1 pending Bug #931914 [src:octave-octproj] octave-octproj: FTBFS with PROJ 6 Added tag(s) pending. -- 931914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#935745: python-pushy: should this package be removed?

Package: python-pushy Severity: serious User: debian-pyt...@lists.debian.org Usertags: py2removal Hello, i'm looking at python-pushy as it depends on python-paramiko; one of bullseye goals is to remove python2 and python-pushy * is dead upstream * last upload was in 2015, and NMU (one of the only

Bug#874818: marked as done ([attica] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 19:14:24 + with message-id and subject line Bug#935735: Removed package(s) from unstable has caused the Debian Bug report #874818, regarding [attica] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been de

Bug#875038: [lmms] Future Qt4 removal from Buster

On Sun, Oct 14, 2018 at 03:16:27AM +0200, Javier Serrano Polo wrote: > On Fri, 23 Mar 2018 18:23:51 +0800 Boyuan Yang <073p...@gmail.com> > wrote: > > lmms 1.2.0 is on its way. > > I will not package a candidate version unless this bug becomes serious. > Efforts should be directed in helping upstr

Bug#935738: python-webunit: please port to python 3

Package: python-webunit Severity: serious Hello, python-webunit is still python2-only, and one of the goals for Bullseye is to remove python2. python-webunit is a reverse-dependency of funkload, which will also need to be ported to python3, but let's start with webunit. An alternative would be t

Bug#933705: marked as done (aiscm: depend on correct libomp5 library)

Your message dated Sun, 25 Aug 2019 18:49:25 + with message-id and subject line Bug#933705: fixed in aiscm 0.19.1-1 has caused the Debian Bug report #933705, regarding aiscm: depend on correct libomp5 library to be marked as done. This means that you claim that the problem has been dealt with

Bug#935734: [workaround] Re: Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

Dixi quod… > tglase@tglase:~ $ virsh -c qemu:///system start MirBSD > error: Failed to start domain MirBSD > error: Operation not supported: operation 'setCpusetMemoryMigrate' not > supported Looking around I found the (not very helpful to me) https://bugzilla.redhat.com/show_bug.cgi?id=1688736

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

On Sun, 25 Aug 2019, Thorsten Glaser wrote: > Package: libvirt-daemon > Version: 5.0.0-4.1 > After a recent upgrade in sid: Hm, but it’s not libvirt, I think, whose upgrade broke things (even if libvirt is unusable): looking at the logfiles under /var/log/libvirt/qemu/ I see the last successful

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

> The diff is: HOME, USER, LOGNAME, fd argument for netdev, and kernel > 4.19.0-5-amd64 (worked) vs 5.2.0-2-amd64 (fails). Another difference might be that, in the meantime, I switched from consolekit plus old policykit to elogind, which might have affected some of the “modern desktop” things like

Bug#935736: Drop dependency on automoc

Package: kde-sc-dev-latest Severity: serious All reverse dependencies of automoc have been dropped, but kde-sc-dev-latest still depends on it, blocking it's removal. Cheers, Moritz

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

Package: libvirt-daemon Version: 5.0.0-4.1 Severity: grave Justification: renders package unusable After a recent upgrade in sid: tglase@tglase:~ $ virsh -c qemu:///system start MirBSD error: Failed to start domain MirBSD error: Operation not supported: operation 'setCpusetMemoryMigrate' not

Bug#935733: libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS

Package: libbladerf-doc Version: 0.2019.07-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it

Bug#935711: marked as done (FTBFS: looks for docker?)

Your message dated Sun, 25 Aug 2019 18:07:52 + with message-id and subject line Bug#935711: fixed in emacs-pdf-tools 0.90-3 has caused the Debian Bug report #935711, regarding FTBFS: looks for docker? to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#935712: marked as done (FTBFS: dh-elpa error)

Your message dated Sun, 25 Aug 2019 18:07:41 + with message-id and subject line Bug#935712: fixed in emacs-git-modes 1.2.8-3 has caused the Debian Bug report #935712, regarding FTBFS: dh-elpa error to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#935710: marked as done (FTBFS: tests fail)

Your message dated Sun, 25 Aug 2019 18:07:59 + with message-id and subject line Bug#935710: fixed in emacs-python-environment 0.0.2-5 has caused the Debian Bug report #935710, regarding FTBFS: tests fail to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#935731: comitup: port to python 3

Package: comitup Severity: serious Hello, comitup is one of the only rdeps of python-tabulate; Debian has a target of dropping Python 2 from Bullseye, so please port comitup to python 3. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500,

Bug#935730: kamcli: port to python 3 (or remove from Debian?)

Package: kamcli Severity: serious Hello, kamcli is one of the only rdeps of python-tabulate; Debian has a target of dropping Python 2 from Bullseye, so please port kamcli to python 3; an alternative would be to drop kamcli entirely: it has a single popcon entry, so i'm afraid it's not that popular

Bug#875149: marked as done ([qtcurve] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 17:09:59 + with message-id and subject line Bug#875149: fixed in qtcurve 1.9-4 has caused the Debian Bug report #875149, regarding [qtcurve] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Tagging #935570 as pending

Processing commands for cont...@bugs.debian.org: > tags 935570 + pending Bug #935570 [src:pysph] src:pysph: License and Copyrights missing from debian/copyright Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 935570: https://bugs.debian.org/

Bug#935615: [Aptitude-devel] Bug#935615: aptitude: FTBFS on amd64

Hi, Em dom, 25 de ago de 2019 às 16:27, Axel Beckert escreveu: > > Hi Manuel, > > Ivo De Decker wrote: > > A binnmu of aptitude in unstable fails on amd64: > > > > https://buildd.debian.org/status/package.php?p=aptitude > > Do you happen to know if any of your recent commits to the master > branc

Bug#935698: amule-utils-gui: amulegui crashing with current libwxgtk3.0-0v5 3.0.4+dfsg-9 and friends

Hello Martintxo, I am just looking at crashes of some random packages and found your backtrace. Thats already a good start. As I it looks like you had installed the package amule-utils-gui-dbgsym maybe you could also install these packages: libwxbase3.0-0v5-dbgsym libwxgtk3.0-0v5-dbgsym libgtk

Bug#874833: marked as done ([boats] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 16:36:01 + with message-id and subject line Bug#874833: fixed in boats 201908-1 has caused the Debian Bug report #874833, regarding [boats] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with.

Bug#875021: marked as done ([libdbusmenu-qt] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 16:36:45 + with message-id and subject line Bug#875021: fixed in libdbusmenu-qt 0.9.3+16.04.20160218-2 has caused the Debian Bug report #875021, regarding [libdbusmenu-qt] Future Qt4 removal from Buster to be marked as done. This means that you claim that t

Bug#935717: marked as done (FTBFS: tests fail)

Your message dated Sun, 25 Aug 2019 16:05:35 + with message-id and subject line Bug#935717: fixed in haskell-mode 16.1-8 has caused the Debian Bug report #935717, regarding FTBFS: tests fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#874808: marked as done ([akonadi4] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:45:47 + with message-id and subject line Bug#935718: Removed package(s) from unstable has caused the Debian Bug report #874808, regarding [akonadi4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#925810: marked as done (qjson: ftbfs with GCC-9)

Your message dated Sun, 25 Aug 2019 15:44:18 + with message-id and subject line Bug#935705: Removed package(s) from unstable has caused the Debian Bug report #925810, regarding qjson: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#875139: marked as done ([qjson] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:44:18 + with message-id and subject line Bug#935705: Removed package(s) from unstable has caused the Debian Bug report #875139, regarding [qjson] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dea

Bug#935568: marked as done (sphinx-issuetracker: should this package be removed?)

Your message dated Sun, 25 Aug 2019 15:40:12 + with message-id and subject line Bug#935700: Removed package(s) from unstable has caused the Debian Bug report #935568, regarding sphinx-issuetracker: should this package be removed? to be marked as done. This means that you claim that the proble

Bug#925718: marked as done (ioprocess: ftbfs with GCC-9)

Your message dated Sun, 25 Aug 2019 15:39:08 + with message-id and subject line Bug#935693: Removed package(s) from unstable has caused the Debian Bug report #925718, regarding ioprocess: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#925662: marked as done (criu: ftbfs with GCC-9)

Your message dated Sun, 25 Aug 2019 15:36:02 + with message-id and subject line Bug#935675: Removed package(s) from unstable has caused the Debian Bug report #925662, regarding criu: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#876905: marked as done (qtwebkit should not be released with buster)

Your message dated Sun, 25 Aug 2019 15:35:34 + with message-id and subject line Bug#935668: Removed package(s) from unstable has caused the Debian Bug report #876905, regarding qtwebkit should not be released with buster to be marked as done. This means that you claim that the problem has bee

Bug#796536: marked as done (criu: package not yet ready for stable release / fast moving (blocking bug))

Your message dated Sun, 25 Aug 2019 15:36:02 + with message-id and subject line Bug#935675: Removed package(s) from unstable has caused the Debian Bug report #796536, regarding criu: package not yet ready for stable release / fast moving (blocking bug) to be marked as done. This means that y

Bug#875159: marked as done ([qtwebkit] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:35:34 + with message-id and subject line Bug#935668: Removed package(s) from unstable has caused the Debian Bug report #875159, regarding [qtwebkit] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875146: marked as done ([qt-at-spi] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:34:58 + with message-id and subject line Bug#935662: Removed package(s) from unstable has caused the Debian Bug report #875146, regarding [qt-at-spi] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#934268: marked as done (kde4libs: CVE-2019-14744)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #934268, regarding kde4libs: CVE-2019-14744 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#925724: marked as done (kde4libs: ftbfs with GCC-9)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #925724, regarding kde4libs: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#874945: marked as done ([kde4libs] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #874945, regarding [kde4libs] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#784479: marked as done ([kde4libs] Qt4's WebKit removal)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #784479, regarding [kde4libs] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been dealt with

Bug#875318: marked as done (QJson removal form Buster)

Your message dated Sun, 25 Aug 2019 15:30:26 + with message-id and subject line Bug#935663: Removed package(s) from unstable has caused the Debian Bug report #875318, regarding QJson removal form Buster to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#874937: marked as done ([kdepimlibs] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:30:26 + with message-id and subject line Bug#935663: Removed package(s) from unstable has caused the Debian Bug report #874937, regarding [kdepimlibs] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has bee

Bug#874932: marked as done ([kate4] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:29:50 + with message-id and subject line Bug#935222: Removed package(s) from unstable has caused the Debian Bug report #874932, regarding [kate4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dea

Bug#874944: marked as done ([kde-runtime] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:29:15 + with message-id and subject line Bug#935664: Removed package(s) from unstable has caused the Debian Bug report #874944, regarding [kde-runtime] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has be

Bug#784477: marked as done ([kde-runtime] Qt4's WebKit removal)

Your message dated Sun, 25 Aug 2019 15:29:15 + with message-id and subject line Bug#935664: Removed package(s) from unstable has caused the Debian Bug report #784477, regarding [kde-runtime] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been dealt w

Bug#874925: marked as done ([kactivities] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:28:01 + with message-id and subject line Bug#935219: Removed package(s) from unstable has caused the Debian Bug report #874925, regarding [kactivities] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has be

Bug#933130: marked as done (FTBFS, not Django 2.2 ready)

Your message dated Sun, 25 Aug 2019 15:23:16 + with message-id and subject line Bug#933130: fixed in python-django-debug-toolbar 1:2.0-1 has caused the Debian Bug report #933130, regarding FTBFS, not Django 2.2 ready to be marked as done. This means that you claim that the problem has been de

Bug#935699: gdm3: uninstallable on s390x

On Sun, 25 Aug 2019 at 12:52:08 +0200, Ivo De Decker wrote: > On s390x, gdm3 isn't installable, because it needs gnome-shell, which FTBFS > there. So either the dependency should be dropped or the binaries for gdm3 on > s390x should be removed. gdm3 genuinely does require gnome-shell at runtime: i

Bug#925686: marked as done (fmtlib: ftbfs with GCC-9)

Your message dated Sun, 25 Aug 2019 15:17:38 + with message-id and subject line Bug#925686: fixed in fmtlib 5.3.0+ds-1 has caused the Debian Bug report #925686, regarding fmtlib: 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#935620: marked as done (thrift: FTBFS on amd64)

Your message dated Sun, 25 Aug 2019 15:10:11 + with message-id and subject line Bug#935620: fixed in thrift 0.11.0-5 has caused the Debian Bug report #935620, regarding thrift: FTBFS on amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#935717: FTBFS: tests fail

Package: haskell-mode Version: 16.1-6 Severity: serious Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 during a no-change rebuild of haskell-mode I noticed the tests are failing. failing tests: , | 4 unexpected results: |FAILED haskell-cabal-compute-checksum-1 |

Bug#842892: marked as done (java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model)

Your message dated Sun, 25 Aug 2019 14:28:17 + with message-id and subject line Bug#842892: fixed in z3 4.4.1-1~deb9u1 has caused the Debian Bug report #842892, regarding java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model to be marked as done. This means that

Bug#935615: [Aptitude-devel] Bug#935615: aptitude: FTBFS on amd64

Hi Manuel, Ivo De Decker wrote: > A binnmu of aptitude in unstable fails on amd64: > > https://buildd.debian.org/status/package.php?p=aptitude Do you happen to know if any of your recent commits to the master branch already fixes this issue? I haven't found any which looks fitting on a first gla

Bug#910577: marked as done (gdb-multiarch: libbabeltrace1 dependency not tight enough)

Your message dated Sun, 25 Aug 2019 14:27:32 + with message-id and subject line Bug#931147: fixed in babeltrace 1.5.6-2+deb10u1 has caused the Debian Bug report #931147, regarding gdb-multiarch: libbabeltrace1 dependency not tight enough to be marked as done. This means that you claim that th

Bug#842892: marked as done (java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model)

Your message dated Sun, 25 Aug 2019 14:27:50 + with message-id and subject line Bug#842892: fixed in z3 4.4.1-1~deb10u1 has caused the Debian Bug report #842892, regarding java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model to be marked as done. This means tha

Bug#931147: marked as done (gdb depends on newer libbabeltrace)

Your message dated Sun, 25 Aug 2019 14:27:32 + with message-id and subject line Bug#931147: fixed in babeltrace 1.5.6-2+deb10u1 has caused the Debian Bug report #931147, regarding gdb depends on newer libbabeltrace to be marked as done. This means that you claim that the problem has been deal

Processed: tagging 935615

Processing commands for cont...@bugs.debian.org: > tags 935615 + confirmed Bug #935615 [src:aptitude] aptitude: FTBFS on amd64 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 935615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935615

Processed: FTBFS with PROJ 6

Processing control commands: > severity -1 serious Bug #931940 [src:sumo] sumo: FTBFS with PROJ 6 Severity set to 'serious' from 'important' -- 931940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: FTBFS with PROJ 6

Processing control commands: > severity -1 serious Bug #931948 [src:r-cran-lwgeom] r-cran-lwgeom: FTBFS with PROJ 6 Severity set to 'serious' from 'important' -- 931948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Processed: FTBFS with PROJ 6

Processing control commands: > severity -1 serious Bug #931944 [src:vtk7] vtk7: FTBFS with PROJ 6 Severity set to 'serious' from 'important' -- 931944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: FTBFS with PROJ 6

Processing control commands: > severity -1 serious Bug #931914 [src:octave-octproj] octave-octproj: FTBFS with PROJ 6 Severity set to 'serious' from 'important' -- 931914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931914 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Processed: FTBFS with PROJ 6

Processing control commands: > severity -1 serious Bug #931935 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with PROJ 6 Severity set to 'serious' from 'important' -- 931935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931935 Debian Bug Tracking System Contact ow...@bugs.de

Processed: reassign 934600 to cufflinks, fixed 934600 in 2.2.1+dfsg.1-4, affects 934600

Processing commands for cont...@bugs.debian.org: > reassign 934600 cufflinks 2.2.1+dfsg.1-3 Bug #934600 {Done: Alexandre Mestiashvili } [cufflinks,gffread] cufflinks,gffread: both ship /usr/bin/gffread Bug reassigned from package 'cufflinks,gffread' to 'cufflinks'. No longer marked as found in ve

Bug#935713: src:thrift: Incomplete debian/copyright

Package: src:thrift Version: 0.11.0-4 Severity: serious Justification: Policy 2.3 While reviewing your package in New, I noticed omissions from debian/ copyright. Since this problem also exists in the current package, I am filing this bug rather than rejecting the package. At a minimum, the foll

Bug#935714: python-os-net-config (build-) depends on cruft package.

Package: python-os-net-config Version: 0.1.0-1 Severity: serious Tags: bullseye, sid python-os-net-config (build-)depends on the python-oslo.config binary package which is no longer built by the corresponding source package. I see no reverse-depends, should this package simply be removed?

Bug#935712: FTBFS: dh-elpa error

Source: emacs-git-modes Version: 1.2.8-2 Severity: serious Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 during a no-change rebuild of this package I noticed that it fails to build from source It looks like there is an incompatibility with the latest dh-elpa. , | Gen

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote: > * Francesco Poli: > > > Hello everyone, > > I am sorry to ask, but... I cannot understand what's the status of > > [this bug report]. > > > > [this bug report]: > > > > A serious bug for libc6-dev without

Bug#866980: marked as done (biomaj-watcher: fails to upgrade from 'jessie': Exception in thread "main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : Unsupported major.minor version 52.

Your message dated Sun, 25 Aug 2019 13:47:29 + with message-id and subject line Bug#866980: fixed in biomaj-watcher 1.2.2-4+deb9u1 has caused the Debian Bug report #866980, regarding biomaj-watcher: fails to upgrade from 'jessie': Exception in thread "main" java.lang.UnsupportedClassVersionEr

Bug#935711: FTBFS: looks for docker?

Source: emacs-pdf-tools Version: 0.90-2 Severity: serious Justification: ftbfs During a no-change rebuild I noticed this packge does not build from source. Apologies if this is caused by the way I created the source package: % dgit --quilt=auto push-source --overwrite A sample build log is at

  1   2   >