Bug#918595: marked as done (ruby-seed-fu FTBFS with rails 5.2)

Your message dated Fri, 30 Aug 2019 06:19:51 + with message-id and subject line Bug#918595: fixed in ruby-seed-fu 2.3.7-3 has caused the Debian Bug report #918595, regarding ruby-seed-fu FTBFS with rails 5.2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#935794: xfce4-sntray-plugin FTBFS

Hi, Am Donnerstag, 29. August 2019 schrieb peter green: > It looks like that class was dropped from vala-panel in > https://gitlab.com/vala-panel-project/vala-panel/commit/87493a6dfab9868f77b7b19b57fca40a06fe80af > > Unfortunately the commit message doesn't give any clues to what if-anything >

Bug#936017: marked as done (mapnik: FTBFS with scons 3.1.1 (environment variables not used))

Your message dated Fri, 30 Aug 2019 06:04:58 + with message-id and subject line Bug#936017: fixed in mapnik 3.0.22+ds1-1 has caused the Debian Bug report #936017, regarding mapnik: FTBFS with scons 3.1.1 (environment variables not used) to be marked as done. This means that you claim that the

Bug#936095: sardana: Obsolete libs (Python 2) - Depends on to be removed packages

Source: sardana Version: 2.6.2+dfsg-1 Severity: serious Justification: Policy 2.5 It appears that upstream supports python3 [1]. Please either upgrade the package or have it removed. This is, indirectly, one of the few remaining packages blocking python-qt4 removal. We are also removing Qt4. T

Bug#936092: gcc-9 patches apply even less

Source: cross-gcc Version: 231 Severity: serious Tags: patch Control: block -1 by 928035 On top of #928035, there is another change in gcc-9 that makes the gcc-9 patches no longer apply. The attached patch resolves the relevant hunk. Please consider uploading a new version that works with the curr

Processed: gcc-9 patches apply even less

Processing control commands: > block -1 by 928035 Bug #936092 [src:cross-gcc] gcc-9 patches apply even less 936092 was not blocked by any bugs. 936092 was not blocking any bugs. Added blocking bug(s) of 936092: 928035 -- 936092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936092 Debian Bug

Processed: Re: Bug#927135: src:rekall: Please update to python3 version

Processing control commands: > block -1 by 936091 Bug #927135 [src:rekall] src:rekall: Please update to python3 version 927135 was not blocked by any bugs. 927135 was not blocking any bugs. Added blocking bug(s) of 927135: 936091 -- 927135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92713

Bug#927135: src:rekall: Please update to python3 version

control: block -1 by 936091 On Mon, 26 Aug 2019 11:02:23 +0200 Raphael Hertzog wrote: > Hi, > > On Sun, 25 Aug 2019, Scott Kitterman wrote: > > If you have lost interest in the package, please let me know so I can ask to > > have it removed. > > Don't remove rekall please. There's a new upstream

Bug#936091: aff4: please package new upstream release (needed by rekall), port to python3

Source: aff4 Severity: serious Hello, please package the new upstream release for aff4; according to https://github.com/google/aff4 the project has been split in the Python and C parts separately. aff4 (specificly `'pyaff4 >= 0.26, < 0.30'`) is required by the new upstream release of rekall. Add

Bug#933584: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

Your message dated Fri, 30 Aug 2019 03:14:41 + with message-id and subject line Bug#936059: Removed package(s) from unstable has caused the Debian Bug report #933584, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye to be marked as done. This means that y

Bug#874891: marked as done ([gns3] Future Qt4 removal from Buster)

Your message dated Fri, 30 Aug 2019 03:16:16 + with message-id and subject line Bug#936077: Removed package(s) from unstable has caused the Debian Bug report #874891, regarding [gns3] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been deal

Bug#875240: marked as done ([xflr5] Future Qt4 removal from Buster)

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

Bug#784871: marked as done (gns3 version too old to be usable)

Your message dated Fri, 30 Aug 2019 03:16:16 + with message-id and subject line Bug#936077: Removed package(s) from unstable has caused the Debian Bug report #784871, regarding gns3 version too old to be usable to be marked as done. This means that you claim that the problem has been dealt wi

Bug#875234: marked as done ([writetype] Future Qt4 removal from Buster)

Your message dated Fri, 30 Aug 2019 03:16:43 + with message-id and subject line Bug#936078: Removed package(s) from unstable has caused the Debian Bug report #875234, regarding [writetype] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#936088: Acknowledgement (libmurmurhash autopkg tests fail)

Processing control commands: > tags -1 + patch Bug #936088 [src:libmurmurhash] libmurmurhash autopkg tests fail Added tag(s) patch. -- 936088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#936088: Acknowledgement (libmurmurhash autopkg tests fail)

Control: tags -1 + patch patch at http://launchpadlibrarian.net/439524642/libmurmurhash_1.5-1_1.5-1ubuntu1.diff.gz

Bug#936088: libmurmurhash autopkg tests fail

Package: src:libmurmurhash Version: 1.5-1 Severity: serious Tags: sid bullseye Apparently the package needs a rebuild at least, some tests don't work anymore. autopkgtest [22:47:58]: test run-unit-test: [--- /usr/bin/ld: /tmp/ccNY3NFj.o: in function `main': mmh.c:(.text.start

Bug#913041: marked as done (python-memprof fails its autopkg tests with Python 3.7)

Your message dated Fri, 30 Aug 2019 00:07:02 + with message-id and subject line Bug#913035: fixed in python-memprof 0.3.6-1 has caused the Debian Bug report #913035, regarding python-memprof fails its autopkg tests with Python 3.7 to be marked as done. This means that you claim that the probl

Bug#913035: marked as done (python-memprof fails its autopkg tests with Pyhton 3.7)

Your message dated Fri, 30 Aug 2019 00:07:02 + with message-id and subject line Bug#913035: fixed in python-memprof 0.3.6-1 has caused the Debian Bug report #913035, regarding python-memprof fails its autopkg tests with Pyhton 3.7 to be marked as done. This means that you claim that the probl

Processed: bug 913035 is forwarded to https://github.com/jmdana/memprof/issues/12

Processing commands for cont...@bugs.debian.org: > forwarded 913035 https://github.com/jmdana/memprof/issues/12 Bug #913035 [src:python-memprof] python-memprof fails its autopkg tests with Pyhton 3.7 Bug #913041 [src:python-memprof] python-memprof fails its autopkg tests with Python 3.7 Set Bug

Processed: severity of 934591 is normal

Processing commands for cont...@bugs.debian.org: > severity 934591 normal Bug #934591 [anki] Anki fails to start: ModuleNotFoundError: No module named 'PyQt5.sip' Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 934591: https:

Bug#928791: marked as done (congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys')

Your message dated Thu, 29 Aug 2019 22:19:37 + with message-id and subject line Bug#928791: fixed in congress 9.0.0+dfsg1-4 has caused the Debian Bug report #928791, regarding congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys' to be marked as done. This means that you clai

Bug#935938: marked as done (android-sdk-meta_25.0.0+11~deb10u1_all.changes REJECTED)

Your message dated Thu, 29 Aug 2019 22:19:24 + with message-id and subject line Bug#935938: fixed in android-sdk-meta 25.0.0+12 has caused the Debian Bug report #935938, regarding android-sdk-meta_25.0.0+11~deb10u1_all.changes REJECTED to be marked as done. This means that you claim that the

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

severity 931798 normal thanks On Wed, Aug 21, 2019 at 09:39:52PM +0100, Julian Gilbey wrote: > On Wed, Aug 21, 2019 at 04:22:23PM +0200, Arnaldo Pirrone wrote: > > Hi, i do have python3-sip. > > Now the error is this: > > $ anki > > Traceback (most recent call last): > >   File "/usr/bin/anki", li

Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

On Thu, Aug 29, 2019 at 10:55:28PM +0200, Francesco Poli wrote: > On Thu, 29 Aug 2019 22:14:04 +0200 Christian T. Steigies wrote: > > > Hi, > > On Fri, Aug 16, 2019 at 04:32:08PM +0100, Laurence Abbott via Glx-devel > > wrote: > > > I _think_ I have the fix for seg faults that occur when QGLE is

Bug#936016: meteo-qt crashes immediately

my bad, my first answer was wrong - should talk with the author cheers Alf

Bug#875234: [writetype] Future Qt4 removal from Buster

Thanks!!! Miry El jue., 29 ago. 2019 a las 23:05, Moritz Mühlenhoff () escribió: > > On Thu, Aug 29, 2019 at 10:58:03PM +0200, Miriam Ruiz wrote: > > It's okay for me to remove it from the archive. I think it would be > > the best. As you say, it seems to be dead upstream. > > Ack, I've just file

Bug#913756: marked as done (tootle: Tootle window opens and closes immediately)

Your message dated Thu, 29 Aug 2019 21:32:59 + with message-id and subject line Bug#913756: fixed in granite 5.2.4-1 has caused the Debian Bug report #913756, regarding tootle: Tootle window opens and closes immediately to be marked as done. This means that you claim that the problem has been

Bug#936016: meteo-qt crashes immediately

Nice finding, unfortunately you are right: >From bfe9ae4d25b914d5c2622042303ba09fa8060e80 Mon Sep 17 00:00:00 2001 From: Dimitrios Glentadakis Date: Mon, 6 May 2019 19:34:58 +0200 Subject: [PATCH] Fix crash when 6 days forceast is not available --- meteo_qt/meteo_qt.py | 4 1 file changed

Bug#933822: closed by Jan Dittberner (Bug#933822: fixed in virtualenvwrapper 4.8.4-1)

On 28/08/2019 09:12, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the virtualenvwrapper package: #933822: virtualenvwrapper depends on cruft package python-stevedore Is there a reason that the fix was only uploaded to expe

Bug#936079: python-ceilometerclient (build-)depends on cruft packages.

Package: python-ceilometerclient Version: 2.9.0-2 Severity: serious Tags: bullseye, sid The python-ceilometerclient binary package depends on and the python-ceilometerclient binary package build-depends on a number of python 2 binary packages that are no longer built by their corresponding sour

Bug#929697: marked as done (pyglet: FTBFS randomly because of timing tests)

Your message dated Thu, 29 Aug 2019 21:36:44 + with message-id and subject line Bug#929697: fixed in pyglet 1.4.1-3 has caused the Debian Bug report #929697, regarding pyglet: FTBFS randomly because of timing tests to be marked as done. This means that you claim that the problem has been deal

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

Processing commands for cont...@bugs.debian.org: > Found 935015 0.11.2-2 Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal effort) Marked as found in versions datalad/0.11.2-2. > Thanks Stopping processing here. Please contact me if you need assistance. -- 935015:

Bug#935015: datalad: please drop python-datalad (python 2 removal effort)

Found 935015 0.11.2-2 Thanks This bug also affects the version in testing.

Bug#928791: marked as pending in congress

Control: tag -1 pending Hello, Bug #928791 in congress 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/openstack-team/services/congress/commit/92cb080108bdfa87f

Processed: Bug#928791 marked as pending in congress

Processing control commands: > tag -1 pending Bug #928791 [src:congress] congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys' Added tag(s) pending. -- 928791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928791 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#875234: [writetype] Future Qt4 removal from Buster

On Thu, Aug 29, 2019 at 10:58:03PM +0200, Miriam Ruiz wrote: > It's okay for me to remove it from the archive. I think it would be > the best. As you say, it seems to be dead upstream. Ack, I've just filed a removal bug. Cheers, Moritz

Bug#936076: python3-numba: numba segfaults when run with python 3.7.4 at numba/_dynfunc.c:52

Package: python3-numba Version: 0.42.0-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Attempting to run any numba code immediately segfaults when running with python 3.7.4. I found this upstream bug report. https://github.com/numba/numba/pull/4328 "CPy

Bug#875234: [writetype] Future Qt4 removal from Buster

It's okay for me to remove it from the archive. I think it would be the best. As you say, it seems to be dead upstream. Greetings, Miry El jue., 29 ago. 2019 a las 22:42, Moritz Mühlenhoff () escribió: > > On Sat, Sep 09, 2017 at 11:12:40PM +0200, Lisandro Damián Nicanor Pérez Meyer > wrote: > >

Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

On Thu, 29 Aug 2019 22:14:04 +0200 Christian T. Steigies wrote: > Hi, > On Fri, Aug 16, 2019 at 04:32:08PM +0100, Laurence Abbott via Glx-devel wrote: > > I _think_ I have the fix for seg faults that occur when QGLE is used with > > ghostscript 9.27 (the latest release). > > I applied Laurence's

Bug#875234: [writetype] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:12:40PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: writetype > Version: 1.3.163-1 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [annou

Bug#925862: xbindkeys-config: ftbfs with GCC-9

Control: tags -1 + patch Dear maintainer, the attached patch fixes the FTBFS by moving the linked libraries to the end of the command line. Regards, Reiner --- xbindkeys-config-0.1.3.orig/debian/patches/gcc9.patch +++ xbindkeys-config-0.1.3/debian/patches/gcc9.patch @@ -0,0 +1,15 @@ +Author: R

Processed: Re: xbindkeys-config: ftbfs with GCC-9

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

Bug#875250: [scim] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:09:36PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: scim > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced] in: > > [announced] > > > Current

Bug#875219: [unixodbc-gui-qt] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:11:54PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: unixodbc-gui-qt > Version: 2.3.0-4 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [a

Bug#930363: faad2: fix build with gcc-9 [patch]

Am Donnerstag, den 29.08.2019, 09:54 -0400 schrieb Hugo Lefeuvre: > Ack, I'll NMU then. Good luck with the baby :) Thank you! \o/ - Fabian signature.asc Description: This is a digitally signed message part

Bug#922767: marked as done (libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory -)

Your message dated Thu, 29 Aug 2019 21:54:39 +0200 with message-id <0ba8b1b9-8627-4306-d09d-17fec132c...@web.de> and subject line Re: Processed (with 1 error): NIMBY has caused the Debian Bug report #922767, regarding libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory - to be

Processed: [bts-link] source package kamoso

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kamoso > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Bug#934959: marked as done (python-mock breaks sunpy autopkgtest)

Your message dated Thu, 29 Aug 2019 19:10:59 + with message-id and subject line Bug#934959: fixed in sunpy 1.0.3-1 has caused the Debian Bug report #934959, regarding python-mock breaks sunpy autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#925625: abr2gbr: ftbfs with GCC-9

Control: tags -1 + patch Dear maintainer, the attached patch fixes the FTBFS by moving the libs to the end of the command line. Regards, Reiner diff -Nru abr2gbr-1.0.2/debian/patches/gcc9.patch abr2gbr-1.0.2/debian/patches/gcc9.patch --- abr2gbr-1.0.2/debian/patches/gcc9.patch 1970-01-01 01:00

Processed: Re: abr2gbr: ftbfs with GCC-9

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

Bug#875029: [lightdm] Future Qt4 removal from Buster

On Thu, Sep 21, 2017 at 03:36:38PM +0200, Yves-Alexis Perez wrote: > On Thu, 2017-09-21 at 00:09 +0800, Boyuan Yang wrote: > > I noticed that you are planning to remove Qt components of lightdm from > > Debian's lightdm. In fact, pkg-deepin team has a planned package that needs > > Qt5-based libl

Bug#875087: [phonon-backend-gstreamer] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 10:18:38PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: phonon-backend-gstreamer > Version: 4:4.9.0-1 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove

Bug#934457: installation in chroot failing with Unknown device "/dev/fuse": No such device

Hello, The issue is in the command: udevadm test --action -p $(udevadm info -q path -n /dev/fuse) the -p flag is being seen as a parameter to the --action flag, which is not a valid action. Per the udevadm man page: *-c*, *--action=**ACTION* Type of event to be triggered. Possible actions are

Processed: Re: Bug#932108: nextcloud-desktop-cmd: Missing nextcloud-desktop-common leads to error "Cannot load system exclude list[...]"

Processing control commands: > Severity -1 important Bug #932108 [nextcloud-desktop-cmd] nextcloud-desktop-cmd: Missing nextcloud-desktop-common leads to error "Cannot load system exclude list[...]" Severity set to 'important' from 'grave' -- 932108: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#932108: nextcloud-desktop-cmd: Missing nextcloud-desktop-common leads to error "Cannot load system exclude list[...]"

Control: Severity -1 important It does not fit the grave severity, that's why I lower the severity. Never the less I'll prepare an update for Buster. hefee On Samstag, 10. August 2019 18:59:07 CEST Calogero Lo Leggio wrote: > Hi, > > I think it's sufficient to add 'nextcloud-desktop-common' i

Bug#936035: marked as done (xfwm4: fails to load due to missing libxfconf-0.so.2)

Your message dated Thu, 29 Aug 2019 19:08:11 +0200 with message-id <18ccdd14c3a84d8ce121067c7f1610c4b6271467.ca...@debian.org> and subject line Re: Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2 has caused the Debian Bug report #936035, regarding xfwm4: fails to load due to missi

Bug#933922: marked as done (src:salt: Unsafe use of yaml.load())

Your message dated Thu, 29 Aug 2019 17:08:29 + with message-id and subject line Bug#933922: fixed in salt 2018.3.4+dfsg1-7 has caused the Debian Bug report #933922, regarding src:salt: Unsafe use of yaml.load() to be marked as done. This means that you claim that the problem has been dealt wi

Bug#933922: marked as pending in salt

Control: tag -1 pending Hello, Bug #933922 in salt 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/salt-team/salt/commit/307770ff7b23e520a59bb03d2bea18f55464891

Processed: Bug#933922 marked as pending in salt

Processing control commands: > tag -1 pending Bug #933922 [src:salt] src:salt: Unsafe use of yaml.load() Added tag(s) pending. -- 933922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#933922: marked as pending in salt

Control: tag -1 pending Hello, Bug #933922 in salt 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/salt-team/salt/commit/ab64448c27bfa82502980204b570d1d8f1a6dce

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2

On Thu, Aug 29, 2019 at 6:25 PM Yves-Alexis Perez wrote: > xfwm4 4.14.0-1 (in sid and unstable) is only linked against libxfconf-0.3, not > libxfconf-0.2, so it's definitely not where the problem lies. Xfce 4.14 just > migrated to testing so that could explain your issue (which is likely > transi

Processed: Bug#933922 marked as pending in salt

Processing control commands: > tag -1 pending Bug #933922 [src:salt] src:salt: Unsafe use of yaml.load() Ignoring request to alter tags of bug #933922 to the same tags previously set -- 933922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933922 Debian Bug Tracking System Contact ow...@bugs

Bug#928791: congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys'

Control: tag -1 + patch Hi, On Sat, 11 May 2019 11:34:23 +0200 Andreas Beckmann wrote: [...] > congress/experimental fails to build twice in a row: > > Traceback (most recent call last): > File > "/build/congress-9.0.0+dfsg1/congress/tests/api/test_datasource_model.py", > line 45, in setUp

Processed: Re: congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys'

Processing control commands: > tag -1 + patch Bug #928791 [src:congress] congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys' Added tag(s) patch. -- 928791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928791 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Processed (with 1 error): NIMBY

Processing commands for cont...@bugs.debian.org: > reassign 922767 texlive-latex-extra Bug #922767 [libemf] libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory - Bug reassigned from package 'libemf' to 'texlive-latex-extra'. No longer marked as found in versions 1.0.11-2. Ign

Bug#936069: virtualenvwrapper-doc: missing Breaks+Replaces: virtualenvwrapper (<< 4.8)

Package: virtualenvwrapper-doc Version: 4.8.4-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

Bug#936068: python3-gnuplot: missing Breaks+Replaces: python-gnuplot

Package: python3-gnuplot Version: 1.8-7 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 tries

Bug#933185: marked as done (fai-server: /etc/fai/apt/sources.list should not contain trusted=yes to skip GPG verification)

Your message dated Thu, 29 Aug 2019 15:52:39 + with message-id and subject line Bug#933185: fixed in fai 5.8.5 has caused the Debian Bug report #933185, regarding fai-server: /etc/fai/apt/sources.list should not contain trusted=yes to skip GPG verification to be marked as done. This means th

Bug#932578: marked as done (Cinnamon Settings fail to start)

Your message dated Thu, 29 Aug 2019 15:49:42 + with message-id and subject line Bug#932578: fixed in cinnamon 4.0.10-1 has caused the Debian Bug report #932578, regarding Cinnamon Settings fail to start to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#931777: marked as done (cinnamon-settings does not start due incompatibility with python3-pil >= 6.0)

Your message dated Thu, 29 Aug 2019 15:49:42 + with message-id and subject line Bug#931777: fixed in cinnamon 4.0.10-1 has caused the Debian Bug report #931777, regarding cinnamon-settings does not start due incompatibility with python3-pil >= 6.0 to be marked as done. This means that you cl

Bug#922767: libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory -

On Wed, 20 Feb 2019 13:51:13 +0100 "Thierry fa...@linux.ibm.com" wrote: [...] > Current compilation fails with message > > /This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live > 2019/dev/Debian) (preloaded format=pdflatex) restricted \write18 > enabled. entering extended mode (./refman.tex

Bug#931609: Update release names after the Buster release.

On 28/08/2019 19.40, Sandro Tosi wrote: > please cancel the NMU, i'll update reportbug with this patch today. I Thanks! Unfortunately you didn't re-enable oldstable_pu in reportbug/debbugs.py, so there is no stretch-pu support any more :-( > will not take care of stables uploads tho OK, I'll ta

Bug#918595: marked as pending in ruby-seed-fu

Control: tag -1 pending Hello, Bug #918595 in ruby-seed-fu 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/ruby-team/ruby-seed-fu/commit/4c72d7a203deb6b6ca87280

Processed: Bug#918595 marked as pending in ruby-seed-fu

Processing control commands: > tag -1 pending Bug #918595 [src:ruby-seed-fu] ruby-seed-fu FTBFS with rails 5.2 Added tag(s) pending. -- 918595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#913756: tootle: Tootle window opens and closes immediately

Processing control commands: > reassign 913756 libgranite5,tootle Bug #913756 [tootle] tootle: Tootle window opens and closes immediately Bug reassigned from package 'tootle' to 'libgranite5,tootle'. No longer marked as found in versions tootle/0.2.0-1. Ignoring request to alter fixed versions of

Bug#913756: tootle: Tootle window opens and closes immediately

Control: reassign 913756 libgranite5,tootle Control: found -1 tootle/0.2.0-1 Control: found -1 granite/5.2.3-1 Control: tag 913756 + fixed-upstream Hi, context for the granite maintainers: Since the switch to granite 5.2, tootle crashes upon startup with "[GLib-GIO] Settings schema 'io.elementary

Bug#933922: [Pkg-salt-team] Bug#933922: src:salt: Unsafe use of yaml.load()

Am Montag, den 05.08.2019, 01:41 -0400 schrieb Scott Kitterman: > Package: src:salt > Version: 2018.3.4+dfsg1-6 > Severity: grave > Tags: security > Justification: user security hole > > The new version of pyyaml no longer allows use of yaml.load() without > a > loader being specifed. This raises

Bug#930363: faad2: fix build with gcc-9 [patch]

Hi Fabian, > Am Donnerstag, den 29.08.2019, 08:04 -0400 schrieb Hugo Lefeuvre: > > Fabian (faad2 maintainer and upstream), do you want to handle this? > > Otherwise I can NMU a second time with this patch. > > please go ahead with a second NMU. I am a bit short on time currently > (home alone wit

Bug#936049: metview: missing libopenmpi-dev dependency?

odb-api includes mpi-default-dev, which defaults to libopenmpi-dev. This may be failing if another mpi (mpich-dev) is installed instead. I agree hard-coding including libopenmpi-dev is needed for the moment. The CMake code in the ECMWF stack (eccodes, magics++, metview, ...) is brittle, and l

Bug#931255: Update in stable?

Le jeu. 29 août 2019 à 15:39, Christoph Haas a écrit : > > I would like to see this simple fix in Buster. Without it the package is > nearly unusable in my opinion. Do you think the release team would agree? Yes, the release team will agree. Unfortunately, I won't work on this soon. Regards --

Bug#931255: Update in stable?

I would like to see this simple fix in Buster. Without it the package is nearly unusable in my opinion. Do you think the release team would agree? …Christoph

Bug#930363: faad2: fix build with gcc-9 [patch]

Dear Hugo, Am Donnerstag, den 29.08.2019, 08:04 -0400 schrieb Hugo Lefeuvre: > Fabian (faad2 maintainer and upstream), do you want to handle this? > Otherwise I can NMU a second time with this patch. please go ahead with a second NMU. I am a bit short on time currently (home alone with the 10mo b

Processed: severity of 935527 is serious

Processing commands for cont...@bugs.debian.org: > severity 935527 serious Bug #935527 [scantool] scantool: FTBFS due to undefined reference to symbol 'ceilf@@GLIBC_2.4' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 93

Bug#936049: metview: missing libopenmpi-dev dependency?

Source: odb-api Version: 0.18.1-6 Severity: serious tags: patch Hello, looks like for some reasons eckit in Ubuntu fails to see the include directory for openmpi, because it simply doesn't exist adding libopenmpi-dev dependency to odb-api should fix the issue, bringing the directory back when c

Bug#933666: marked as done (leaflet-image: fails to build with webpack 4)

Your message dated Thu, 29 Aug 2019 12:20:16 + with message-id and subject line Bug#933666: fixed in leaflet-image 0.4.0~dfsg-2 has caused the Debian Bug report #933666, regarding leaflet-image: fails to build with webpack 4 to be marked as done. This means that you claim that the problem has

Bug#930363: faad2: fix build with gcc-9 [patch]

Hi Gianfranco, On Thu, Aug 29, 2019 at 07:43:15AM +0200, Gianfranco Costamagna wrote: > control: severity -1 serious > On Tue, 11 Jun 2019 15:06:01 +0200 Gianfranco Costamagna > wrote: > > Source: faad2 > > Version: 2.8.8-3 > > Severity: normal > > tags: patch > > > > Hello, looks like gcc-9 is

Processed: Bug#933666 marked as pending in leaflet-image

Processing control commands: > tag -1 pending Bug #933666 [leaflet-image] leaflet-image: fails to build with webpack 4 Added tag(s) pending. -- 933666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#933666: marked as pending in leaflet-image

Control: tag -1 pending Hello, Bug #933666 in leaflet-image 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/js-team/leaflet-image/commit/27116f225295b2741e62a54

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2019-08-29 at 17:31 +0700, Theppitak Karoonboonyanan wrote: > Package: xfwm4 > Version: 4.14.0-1 > Severity: serious > Justification: Policy 3.5 > > Dear Maintainer, > > xfwm4 fails to start: > > $ xfwm4 > xfwm4: error while loading shared

Bug#936040: isc-kea: CVE-2019-6472 CVE-2019-6473 CVE-2019-6474

Source: isc-kea Version: 1.5.0-2 Severity: grave Tags: security upstream Hi, The following vulnerabilities were published for isc-kea. CVE-2019-6472[0]: |A packet containing a malformed DUID can cause the kea-dhcp6 server to |terminate CVE-2019-6473[1]: |An invalid hostname option can cause the

Bug#924548: marked as done (gnome-core: does not actually install a desktop environment on s390x)

Your message dated Thu, 29 Aug 2019 10:50:19 + with message-id and subject line Bug#924548: fixed in meta-gnome3 1:3.30+2 has caused the Debian Bug report #924548, regarding gnome-core: does not actually install a desktop environment on s390x to be marked as done. This means that you claim th

Bug#935692: marked as done (cpufreqd: FTBFS on ppc64el)

Your message dated Thu, 29 Aug 2019 10:49:38 + with message-id and subject line Bug#935692: fixed in cpufreqd 2.4.2-2.2 has caused the Debian Bug report #935692, regarding cpufreqd: FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#935699: marked as done (gdm3: uninstallable on s390x)

Your message dated Thu, 29 Aug 2019 10:50:07 + with message-id and subject line Bug#935699: fixed in gdm3 3.30.2-4 has caused the Debian Bug report #935699, regarding gdm3: uninstallable on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#936014: dovecot: CVE-2019-11500

Hi Apollon, On Thu, Aug 29, 2019 at 12:55:57PM +0300, Apollon Oikonomopoulos wrote: > Source: dovecot > Version: 1:2.3.7.2-1 > > Hi, > > This was fixed in unstable in 1:2.3.7.2-1. Closing this manually as I > stripped the Closes: tag from d/changelog during a rebase ;) Thank you! Regards, Sal

Processed: Bug#935699 marked as pending in gdm3

Processing control commands: > tag -1 pending Bug #935699 [gdm3] gdm3: uninstallable on s390x Ignoring request to alter tags of bug #935699 to the same tags previously set -- 935699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935699 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: Bug#924548 marked as pending in meta-gnome3

Processing control commands: > tag -1 pending Bug #924548 [gnome-core] gnome-core: does not actually install a desktop environment on s390x Added tag(s) pending. -- 924548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924548 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#935699: marked as pending in gdm3

Control: tag -1 pending Hello, Bug #935699 in gdm3 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/gdm/commit/faeef5efcc7ae1334cf4ef5b047d9a4c363826a

Bug#924548: marked as pending in meta-gnome3

Control: tag -1 pending Hello, Bug #924548 in meta-gnome3 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/meta-gnome3/commit/654f70f5448f57eb69830315

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2

Package: xfwm4 Version: 4.14.0-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, xfwm4 fails to start: $ xfwm4 xfwm4: error while loading shared libraries: libxfconf-0.so.2: cannot open shared object file: No such file or directory $ ldd /usr/bin/xfwm4 | grep libxfconf libxfconf

  1   2   >