Bug#884430: marked as done (test_nothing_logged.py:7: AssertionError)

Your message dated Sun, 31 Dec 2017 09:46:14 +0100 with message-id <8705a28b-b2f2-cdae-294a-a8f076d6c...@debian.org> and subject line pytest-catchlog: works now has caused the Debian Bug report #884430, regarding test_nothing_logged.py:7: AssertionError to be marked as done. This means that you

Processed: notfound 884525 in 1.5.5

Processing commands for cont...@bugs.debian.org: > notfound 884525 1.5.5 Bug #884525 {Done: Andreas Tille } [src:mobyle] mobyle: Mobyle javascript includes Google analytics beacon The source 'mobyle' and version '1.5.5' do not appear to match any binary packages No longer

Bug#885785: marked as done (automatically created packages (-dbgsym) should not be rejected by lintian)

Your message dated Sun, 31 Dec 2017 10:30:58 +0100 with message-id and subject line Re: Bug#885785: automatically created packages (-dbgsym) should not be rejected by lintian has caused the Debian Bug report #885785, regarding automatically

Bug#885545: marked as done (hannah-foo2zjs: Don't depend on gksu)

Your message dated Sun, 31 Dec 2017 10:33:55 + with message-id and subject line Bug#885545: fixed in hannah-foo2zjs 1:3 has caused the Debian Bug report #885545, regarding hannah-foo2zjs: Don't depend on gksu to be marked as done. This means that you

Bug#885914: "RuntimeError: dictionary changed size during iteration" in s3cmd put

Package: s3cmd Version: 2.0.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, s3cmd put is failing with: ! An unexpected error has occurred. Please try reproducing the error using the latest s3cmd code

Bug#867561: marked as done (hplip-gui: Depending on gksu is not good)

Your message dated Sun, 31 Dec 2017 11:04:45 + with message-id and subject line Bug#867561: fixed in hplip 3.17.10+repack0-2 has caused the Debian Bug report #867561, regarding hplip-gui: Depending on gksu is not good to be marked as done. This means that

Bug#884849: librsvg: test failures on 32-bit no longer FTBFS

Control: severity 884849 normal Control: severity 884850 normal Control: retitle 884849 librsvg: test failure on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image Control: retitle 884850 librsvg: test failure on (32-bit && !any-i386):

Processed: Re: librsvg: test failures on 32-bit no longer FTBFS

Processing control commands: > severity 884849 normal Bug #884849 [src:librsvg] librsvg: FTBFS on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image Severity set to 'normal' from 'serious' > severity 884850 normal Bug #884850 [src:librsvg]

Bug#885920: [firefox] Firefox window doesn't show under wayland

Package: firefox Version: 57.0.3-1 Severity: grave --- Please enter the report below this line. --- When launching Firefox under Gnome shell/Wayland, nothing seems to happen: no window is shown. But doing a "ps ax" shows two processes with the name "firefox". Killing the second one (the one

Processed: block 868410 with 885911

Processing commands for cont...@bugs.debian.org: > block 868410 with 885911 Bug #868410 [src:yarssr] yarssr: Please drop the (build-)dependency against gnome-vfs 868410 was not blocked by any bugs. 868410 was blocking: 868395 868398 Added blocking bug(s) of 868410: 885911 > thanks Stopping

Bug#868410: yarssr: Please drop the (build-)dependency against gnome-vfs

Hi, Joachim Breitner: > yarssr is dead upstream (for a decade or so) and I’d rather drop it > than patch it. So when it is time to RM gnome-vfs, feel free to RM > yarssr as well. Thanks! I've requested the removal today: #885911.

Bug#856085: marked as done (madplay: Please drop the (build-)dependency against esound)

Your message dated Sun, 31 Dec 2017 13:19:00 + with message-id and subject line Bug#856085: fixed in madplay 0.15.2b-8.2 has caused the Debian Bug report #856085, regarding madplay: Please drop the (build-)dependency against esound to be marked as done.

Bug#885888: marked as done (lordsawar: Don't Build-Depend on libglademm2.4-dev)

Your message dated Sun, 31 Dec 2017 18:05:14 + with message-id and subject line Bug#885888: fixed in lordsawar 0.3.1-4 has caused the Debian Bug report #885888, regarding lordsawar: Don't Build-Depend on libglademm2.4-dev to be marked as done. This means

Bug#884476: derivations FTBFS with poppler 0.61.1

Thank you for the reminder. Poppler is always changing, isn't it? NMUs are always okay with me, but I assume that you have better things to do than to NMU an obscure package like my derivations. When I have some time, I will look into the matter. I need to update the package to the upstream

Processed: Re: verbiste: Please drop the (build-)dependency against gnome-vfs

Processing control commands: > severity -1 serious Bug #868409 [src:verbiste] verbiste: Please drop the (build-)dependency against gnome-vfs Severity set to 'serious' from 'important' -- 868409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868409 Debian Bug Tracking System Contact

Bug#885943: Fails to start: GLX version not found

Package: gr-osmosdr Version: 0.1.4-14 Severity: grave I installed gr-osmosdr and tried to run it only to get an error: wx._core.PyAssertionError: C++ assertion "ok" failed at ../src/unix/glx11.cpp(589) in GetGLXVersion(): GLX version not found The full output of the command is: linux; GNU C++

Processed: Re: gallery-uploader: Uses deprecated python-gnomekeyring

Processing control commands: > severity -1 serious Bug #867959 [src:gallery-uploader] gallery-uploader: Uses deprecated python-gnomekeyring Severity set to 'serious' from 'important' > tags -1 +sid +buster Bug #867959 [src:gallery-uploader] gallery-uploader: Uses deprecated python-gnomekeyring

Bug#790589: gnome-specimen: depends on python-gnome2 which is deprecated

On Tue, Jun 30, 2015 at 4:18 PM, Kartik Mistry wrote: > It seems that we can remove this package. I will file request. Removal bug filed: https://bugs.debian.org/885949 Thanks, Jeremy Bicha

Bug#885570: More info

I also have reproduced this flicker which leads to a total freeze on my Lenovo T450 running Stretch with Intel HD Graphics 5500.  It was immediately noticed when rebooting and using the linux-image-4.9.0-4-amd kernel.  Once I booted back into the previous kernel (4.9.0-3-amd) the problem went

Bug#882955: marked as done (ufo-filters FTBFS with glibc 2.25)

Your message dated Sun, 31 Dec 2017 21:49:33 + with message-id and subject line Bug#882955: fixed in ufo-filters 0.14.1+dfsg1-1.1 has caused the Debian Bug report #882955, regarding ufo-filters FTBFS with glibc 2.25 to be marked as done. This means that

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

Il giorno dom, 31/12/2017 alle 14.28 -0500, Jeremy Bicha ha scritto: > It is my understanding that it is Release > Critical for a package to recommend a removed library because it > keeps > the package from being a candidate for auto-removal when users > upgrade. Thanks Jeremy for opening this

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston wrote: > given that gallery is dead upstream since 2014 > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to orphan > this package (which I'm using no more). > > In fact, gallery-uploader (and its dependency

Bug#883938:

Report

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

On Mon, 11 Dec 2017 19:07:05 +0100 Karsten Heiken < hei...@luis.uni-hannover.de> wrote: > Bernhard Schmidt wrote: > >Can you check whether numa=off on the kernel command line fixes this as well? > > Indeed it does. Appending numa=off to the kernel command line fixes > the bug in my KVM virtual

Bug#801849: marked as done (node-jquery does not register)

Your message dated Sun, 31 Dec 2017 15:06:18 + with message-id and subject line Bug#801849: fixed in node-jquery 2.2.4+dfsg-1 has caused the Debian Bug report #801849, regarding node-jquery does not register to be marked as done. This means that you claim

Bug#884214: marked as done (purify FTBFS with libspdlog-dev 1:0.14.0-1)

Your message dated Sun, 31 Dec 2017 15:07:31 + with message-id and subject line Bug#884214: fixed in purify 2.0.0-2 has caused the Debian Bug report #884214, regarding purify FTBFS with libspdlog-dev 1:0.14.0-1 to be marked as done. This means that you

Bug#864337: marked as done (python-blessed: Non-determistically FTBFS due to unreliable timing in tests)

Your message dated Sun, 31 Dec 2017 15:07:50 + with message-id and subject line Bug#864337: fixed in python-blessed 1.14.2-1 has caused the Debian Bug report #864337, regarding python-blessed: Non-determistically FTBFS due to unreliable timing in tests to

Bug#885401: marked as done (openmw uninstallable)

Your message dated Sun, 31 Dec 2017 16:03:57 + with message-id and subject line Bug#885401: fixed in openmw 0.43.0-1 has caused the Debian Bug report #885401, regarding openmw uninstallable to be marked as done. This means that you claim that the problem

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is deprecated Severity set to 'serious' from 'important' -- 822595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822595 Debian Bug Tracking System Contact

Bug#885927: xdemorse: file xdemorse.glade missing from package

Package: xdemorse Version: 3.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, xdemorse fails to start. When running it from a terminal it prints the following messages: Xdemorse: failed to add objects to builder: Failed to open file

Processed: severity of 885929 is grave

Processing commands for cont...@bugs.debian.org: > severity 885929 grave Bug #885929 [git-buildpackage] git-buildpackage: gbp pq import fails on non UTF-8 chars in patch Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#864963: Uploading NMU to drop gdebi-kde package

Control: tags -1 +pending I am "fixing" this bug by not building the gdebi-kde package any more since this is the last package in Debian depending on pykde4. I have uploaded this to Debian's DELAYED/15 queue. Please let me know if I should speed up or delay the upload. Please see

Processed: Uploading NMU to port gdebi away from gksu

Processing control commands: > tags -1 +pending Bug #822596 [src:gdebi] gdebi: depends on gksu which is deprecated Added tag(s) pending. -- 822596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#822596: Uploading NMU to port gdebi away from gksu

Control: tags -1 +pending I am uploading the work done in Ubuntu to port gdebi away from gksu to Debian's DELAYED/15 queue. Please let me know if I should speed up or delay the upload. Note that gdebi still won't work in the default Debian GNOME Buster or Ubuntu 17.10 sessions (in other words,

Processed: Uploading NMU to drop gdebi-kde package

Processing control commands: > tags -1 +pending Bug #864963 [gdebi-kde] gdebi-kde: Depends on python3-pykde4 which is to be removed for Buster Added tag(s) pending. -- 864963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864963 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#885935: python-pysodium depends on cruft package libsodium18

package: pysodium severity: serious libsodium18 has been replaced by libsodium23, python-pysodium and python3-pysodium still depends on libsodium18. I have not checked whether a simple no-change rebuild and upload is all that is needed or if further changes are required but either way since

Bug#885934: python-libnacl depends on cruft package libsodium18

package: python-libnacl severity: serious libsodium18 has been replaced by libsodium23, python-libnacl still depends on libsodium18. I have not checked whether a simple no-change rebuild and upload is all that is needed or if further changes are required but either way since the package is

Bug#885934: python-libnacl depends on cruft package libsodium18

On Sun, Dec 31, 2017 at 02:36:06PM +, peter green wrote: > libsodium18 has been replaced by libsodium23, python-libnacl still > depends on libsodium18. > > I have not checked whether a simple no-change rebuild and upload is > all that is needed or if further changes are required but either

Bug#885929: [git-buildpackage/master] patch_series: Don't fail on decoding errors when looking for DEP3 headers

tag 885929 pending thanks Date: Sun Dec 31 16:40:21 2017 +0100 Author: Guido Günther Commit ID: 0730a57db438b935bc7f16957650a6ef25589598 Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=0730a57db438b935bc7f16957650a6ef25589598 Patch URL:

Processed: [git-buildpackage/master] patch_series: Don't fail on decoding errors when looking for DEP3 headers

Processing commands for cont...@bugs.debian.org: > tag 885929 pending Bug #885929 [git-buildpackage] git-buildpackage: gbp pq import fails on non UTF-8 chars in patch Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 885929:

Bug#885934: marked as done (python-libnacl depends on cruft package libsodium18)

Your message dated Sun, 31 Dec 2017 15:49:20 + with message-id and subject line Bug#885934: fixed in python-libnacl 1.6.1-2 has caused the Debian Bug report #885934, regarding python-libnacl depends on cruft package libsodium18 to be marked as done. This

Processed: Raise severity of libgnome-keyring reverse depends bugs

Processing commands for cont...@bugs.debian.org: > severity 867939 serious Bug #867939 [src:smbnetfs] smbnetfs: Build-Depends on deprecated libgnome-keyring-dev Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#853323: marked as done (atlas-cpp: ftbfs with GCC-7)

Your message dated Mon, 01 Jan 2018 00:18:53 + with message-id and subject line Bug#853323: fixed in atlas-cpp 0.6.3-4 has caused the Debian Bug report #853323, regarding atlas-cpp: ftbfs with GCC-7 to be marked as done. This means that you claim that the

Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

Source: distro-info Version: 0.17 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build with: Test: Run pylint on Python source code ... FAIL

Processed: tagging 884546

Processing commands for cont...@bugs.debian.org: > tags 884546 + pending Bug #884546 [src:sreview] sreview: FTBFS: missing B-D on perl modules Mojo::JSON Mojo::Pg Moose DBI Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884546:

Bug#884546: marked as done (sreview: FTBFS: missing B-D on perl modules Mojo::JSON Mojo::Pg Moose DBI)

Your message dated Mon, 01 Jan 2018 03:04:02 + with message-id and subject line Bug#884546: fixed in sreview 0.2.3-1 has caused the Debian Bug report #884546, regarding sreview: FTBFS: missing B-D on perl modules Mojo::JSON Mojo::Pg Moose DBI to be marked

Bug#853391: marked as done (eris: ftbfs with GCC-7)

Your message dated Mon, 01 Jan 2018 03:49:02 + with message-id and subject line Bug#853391: fixed in eris 1.3.23-6 has caused the Debian Bug report #853391, regarding eris: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem

Processed: Fix typos in package assignments

Processing commands for cont...@bugs.debian.org: > reassign 885057 src:gnome-color-chooser 0.2.5-1.1 Bug #885057 [src:gnome-color-choser] gnome-color-chooser: Depends on old GNOME libraries Warning: Unknown package 'src:gnome-color-choser' Bug reassigned from package 'src:gnome-color-choser' to