Bug#674107: Processed: Re: Bug#674107: mx: Consider dropping libcluttergesture-dev build-depends

Hi Jeremy, Sounds ok. But abandoned upstream doesn't mean this lib is useless. To me I think it just works. The gadgets provides by this lib is just doing what it is without needed to upgrade or update. I'd like to remove it for a while because I didn't work for moblin anymore. But considering

Bug#885321: dolibarr: CVE-2017-17897 CVE-2017-17898 CVE-2017-17899 CVE-2017-17900

Source: dolibarr Version: 3.5.5+dfsg1-1 Severity: grave Tags: patch security upstream Hi, the following vulnerabilities were published for dolibarr. CVE-2017-17897[0]: | SQL injection vulnerability in comm/multiprix.php in Dolibarr ERP/CRM | version 6.0.4 allows remote attackers to execute

Bug#885320: dolibarr: CVE-2017-14238 CVE-2017-14239 CVE-2017-14240 CVE-2017-14241

Source: dolibarr Version: 3.5.5+dfsg1-1 Severity: grave Tags: patch security upstream Hi, the following vulnerabilities were published for dolibarr, filling only one bug for the four CVEs since afaict the common set of affectedversions to go back to at least 3.5.5+dfsg1-1. CVE-2017-14238[0]: |

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Package: systemd Version: 236-1 Severity: critical Dear maintainers, When using startx (no DM enabled) I suspect that systemd logs me out from my X session if it doesn't freezes it. I try to explain: I login in my openbox session on tty1 using startx, and in tty2 I run some program, say 'moc'.

Bug#885313: lottanzb: Depends on unmaintained pygtk

Source: lottanzb Version: 0.6-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885310: jumpnbump: Depends on unmaintained pygtk

Source: gumpnbump Version: 1.60-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885311: keepnote: Depends on unmaintained pygtk

Source: keepnote Version: 0.7.8-1.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885312: key-mon: Depends on unmaintained pygtk

Source: key-mon Version: 1.17-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885309: jack-mixer: Depends on unmaintained pygtk

Source: jack-mixer Version: 10-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885308: idjc: Depends on unmaintained pygtk

Source: idjc Version: 0.8.16-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885307: ibus-sunpinyin: Depends on unmaintained pygtk

Source: ibus-sunpinyin Version: 2.0.3-5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885302: gtklick: Depends on unmaintained pygtk

Source: gtklick Version: 0.6.4-5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885303: gwakeonlan: Depends on unmaintained pygtk

Source: gwakeonlan Version: 0.5.1-1.2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885305: hijra: Depends on unmaintained pygtk

Source: hijra Version: 0.4.1-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885299: griffith: Depends on unmaintained pygtk

Source: griffith Version: 0.13+20140313-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885298: gquilt: Depends on unmaintained pygtk

Source: gquilt Version: 0.25-5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885301: gtk-recordmydesktop: Depends on unmaintained pygtk

Source: gtk-recordmydesktop Version: 0.3.8-4.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use

Bug#885300: gtg: Depends on unmaintained pygtk

Source: gtg Version: 0.3.1-4 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885297: gpsd-clients: Depends on unmaintained pygtk

Package: gpsd-clients Version: 3.17-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885292: gmobilemedia: Depends on unmaintained pygtk

Source: gmobilemedia Version: 0.4+dfsg-14 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Processed: fix the bug title

Processing commands for cont...@bugs.debian.org: > retitle 885291 globs: Depends on unmaintained pygtk Bug #885291 [src:globs] : Depends on unmaintained pygtk Changed Bug title to 'globs: Depends on unmaintained pygtk' from ': Depends on unmaintained pygtk'. > retitle 885285 geda-xgsch2pcb:

Bug#885295: gpodder: Depends on unmaintained pygtk

Source: gpodder Version: 3.9.3-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885290: geximon: Depends on unmaintained pygtk

Source: geximon Version: 0.7.7-2.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885285: : Depends on unmaintained pygtk

Source: geda-xgsch2pcb Version: 0.1.3-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885291: : Depends on unmaintained pygtk

Source: globs Version: 0.2.0~svn50-4 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885284: gbirthday: Depends on unmaintained pygtk

Source: gbirthday Version: 0.6.10-0.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885279: ffrenzy: Depends on unmaintained pygtk

Source: ffrenzy Version: 1.0.2~svn20150731-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use

Bug#885283: ganyremote: Depends on unmaintained pygtk

Source: ganyremote Version: 6.3.3-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885281: furiusisomount: Depends on unmaintained pygtk

Source: furiusisomount Version: 0.11.3.1~repack1-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to

Bug#885280: fslint: Depends on unmaintained pygtk

Source: fslint Version: 2.44-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster X-Debbugs-CC: f...@rolf.leggewie.biz pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to

Bug#885282: gameclock: Depends on unmaintained pygtk

Source: gameclock Version: 5.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885277: emma: Depends on unmaintained pygtk

Source: emma Version: 0.6-5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection

Bug#885276: driconf: Depends on unmaintained pygtk

Source: driconf Version: 0.9.1-4 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster X-Debbugs-CC: vch...@debian.org pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port

Bug#885273: diffuse: Depends on unmaintained pygtk

Source: diffuse Version: 0.4.8-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885275: disk-manager: Depends on unmaintained pygtk

Source: disk-manager Version: 1.1.1-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885274: directoryassistant: Depends on unmaintained pygtk

Source: directoryassistant Version: 2.0-1.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use

Bug#885270: d-rats: Depends on unmaintained pygtk

Source: d-rats Version: 0.3.3-4 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885268: comix: Depends on unmaintained pygtk

Source: comix Version: 4.0.4-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885264: childsplay: Depends on unmaintained pygtk

Source: childsplay Version: 2.6.5+dfsg-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885262: buxon: Depends on unmaintained pygtk

Source: buxon Version: 0.0.5-5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885258: apoo: Depends on unmaintained pygtk

Source: apoo Version: 2.2-4 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection

Bug#885259: arandr: Depends on unmaintained pygtk

Source: arandr Version: 0.1.9-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885257: agtl: Depends on unmaintained pygtk

Source: agtl Version: 0.8.0.3-1.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#885256: activity-log-manager: Depends on unmaintained pygtk

Source: activity-log-manager Version: 0.8.0-1.2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use

Bug#825095: [Python-modules-team] Bug#825095: Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

> The page: > https://tracker.debian.org/pkg/python-backports-shutil-get-terminal-size > > says 1.0.0-3~bpo8+1 is in old-bbpo, 1.0.0-3 is in stable, and 1.0.0-4 is > in testing and unstable. > > The changelog is: > python-backports-shutil-get-terminal-size (1.0.0-4) unstable; urgency=medium > >

Bug#885254: bluewho: Depends on deprecated pygtk

Package: bluewho Version: 0.1-2 Severity: serious Tags: sid buster User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject

Bug#884034: marked as done (trinity FTBFS with linux-libc-dev 4.14.2-1)

Your message dated Tue, 26 Dec 2017 04:48:58 + with message-id and subject line Bug#884034: fixed in trinity 1.8-2 has caused the Debian Bug report #884034, regarding trinity FTBFS with linux-libc-dev 4.14.2-1 to be marked as done. This means that you

Bug#885252: yahtzeesharp: Build-Depends on libart2.0-cil-dev

From c5536ddbc2b7ed00a901413a452593b4edb4648a Mon Sep 17 00:00:00 2001 From: Jeremy Bicha Date: Mon, 25 Dec 2017 20:28:38 -0500 Subject: [PATCH 1/8] Drop unnecessary libart depends --- debian/control | 2 +-

Bug#885252: yahtzeesharp: Build-Depends on libart2.0-cil-dev

Source: yahtzeesharp Version: 1.1-6 Severity: serious Tags: patch pending X-Debbugs-CC: seb...@ubuntu.com yahtzeesharp Build-Depends on libart2.0-cil-dev, but libart2.0-cil-dev will be removed from Debian soon because it is an old unmaintained GNOME 2 library. See the announcement from the Debian

Bug#885240: libmsnumpress: FTBFS: dot and qhelpgenerator not found

Source: libmsnumpress Version: 1.0.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of libmsnumpress in minimal environments (as on the autobuilders) have been failing: mkdir -p debian/build && doxygen debian/Doxyfile warning: the

Processed: Re: Bug#674107: mx: Consider dropping libcluttergesture-dev build-depends

Processing control commands: > severity -1 serious Bug #674107 [mx] mx: Consider dropping libcluttergesture-dev build-depends Severity set to 'serious' from 'wishlist' -- 674107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674107 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: Re: bisho: Build-Depends on deprecated libgnome-keyring-dev

Processing control commands: > severity -1 serious Bug #867929 [src:bisho] bisho: Build-Depends on deprecated libgnome-keyring-dev Severity set to 'serious' from 'important' -- 867929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867929 Debian Bug Tracking System Contact

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

On Sat, 2017-12-23 at 12:42 +, Chris Boot wrote: > Severity: serious > Justification: kernel panic > > I experimented a little and disabled cgroupv2 on that server. Because I > had some issues during boot I attempted to enable > NetworkManager-wait-online.service using systemd, but that

Bug#885197: guile-2.2: Fails to build from source on amd64

Source: guile-2.2 Version: 2.2.2+2-1 Severity: serious guile-2.2 fails to build from source on amd64 as seen in the reproducibility builder (where it has never built from source on amd64): https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-2.2.html and in Ubuntu:

Bug#706877: marked as done (insserv: breaks dist-upgrade by installing before packages fix their init scripts)

Your message dated Mon, 25 Dec 2017 23:22:08 +0100 with message-id <2017122508.6rov36oagrusu...@angband.pl> and subject line upgrades _to_ wheezy are not interesting anymore has caused the Debian Bug report #706877, regarding insserv: breaks dist-upgrade by installing before packages fix their

Bug#856095: proposed NMU

Control: tags -1 +pending Hi! Only late during testing the NMU I noticed that this bug has been RC for just two days. Thus, sorry for rushing, but considering that timidity has been NMU-maintained since 2011, I'll upload to DELAYED/14. The preferred way to NAK is to make the upload fail due to

Processed: proposed NMU

Processing control commands: > tags -1 +pending Bug #856095 [src:timidity] timidity: Please drop the (build-)dependency against esound Added tag(s) pending. -- 856095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856095 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: [Python-modules-team] Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

Processing control commands: > fixed -1 1.0.0-3 Bug #825095 {Done: Sandro Tosi } [python-backports-shutil-get-terminal-size] python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname Marked as fixed in versions

Bug#825095: [Python-modules-team] Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

Control: fixed -1 1.0.0-3 Hi, Le 25/12/2017 à 07:05, Sandro Tosi a écrit : > control: reopen -1 > control: blocks -1 884690 > > On Mon, May 23, 2016 at 10:50 AM, Aaron M. Ucko wrote: >> Package: python-backports-shutil-get-terminal-size >> Version: 1.0.0-1 >> Severity:

Bug#885102: marked as done (fpc: upgrading from 3.0.4+dfsg-2 to 3.0.4+dfsg-9 fails on /usr/bin/grab_vcsa-3.0.4)

Your message dated Mon, 25 Dec 2017 21:19:00 + with message-id and subject line Bug#885102: fixed in fpc 3.0.4+dfsg-10 has caused the Debian Bug report #885102, regarding fpc: upgrading from 3.0.4+dfsg-2 to 3.0.4+dfsg-9 fails on /usr/bin/grab_vcsa-3.0.4

Bug#884947: freecad: FreeCad crashes on start due to updated libcoin

Very strange issue. It looks like it crashes after the simple rebuild of coin3 with the current toolchain. Anton

Processed: [/master] Add patch trap_errors_from_make.patch (Closes: #883526)

Processing commands for cont...@bugs.debian.org: > tag 883526 pending Bug #883526 {Done: Andreas Rönnquist } [src:geeqie] geeqie build does not trap errors from make Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 883526:

Bug#883526: [/master] Add patch trap_errors_from_make.patch (Closes: #883526)

tag 883526 pending thanks Date: Mon Dec 25 18:30:02 2017 +0100 Author: Andreas Rönnquist Commit ID: a816317d0a6a6a7cfd3b0856f743a6af0d311278 Commit URL: http://anonscm.debian.org/gitweb/?p=collab-maint/geeqie.git;a=commitdiff;h=a816317d0a6a6a7cfd3b0856f743a6af0d311278 Patch

Bug#883526: marked as done (geeqie build does not trap errors from make)

Your message dated Mon, 25 Dec 2017 18:34:19 + with message-id and subject line Bug#883526: fixed in geeqie 1:1.3-1.1 has caused the Debian Bug report #883526, regarding geeqie build does not trap errors from make to be marked as done. This means that you

Bug#833507: Confirmation

I can also confirm that downgrading fixes the problem (used the 2:2.4-1.1 buster package for amd64 instead of 2:2.6-13). Stopping NM and using a simple config file for wpa_supplicant only yields the same problem (pages of CTRL-EVENT-SCAN-FAILED ret=-22 ...). Using "02:00.0 Network controller:

Bug#856078: marked as done (cynthiune.app: Please drop the (build-)dependency against esound)

Your message dated Mon, 25 Dec 2017 18:03:51 + with message-id and subject line Bug#856078: fixed in cynthiune.app 1.0.0-2 has caused the Debian Bug report #856078, regarding cynthiune.app: Please drop the (build-)dependency against esound to be marked as

Bug#884690: marked as done (ImportError with astroid 1.5)

Your message dated Mon, 25 Dec 2017 18:03:45 + with message-id and subject line Bug#884690: fixed in backports.functools-lru-cache 1.4-2 has caused the Debian Bug report #884690, regarding ImportError with astroid 1.5 to be marked as done. This means that

Bug#825095: marked as done (python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname)

Your message dated Mon, 25 Dec 2017 17:49:39 + with message-id and subject line Bug#825095: fixed in python-backports-shutil-get-terminal-size 1.0.0-5 has caused the Debian Bug report #825095, regarding python-backports-shutil-get-terminal-size: clashes

Bug#884690: marked as pending

tag 884690 pending thanks Hello, Bug #884690 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/backports.functools-lru-cache.git/commit/?id=c84da4d ---

Processed: Bug#884690 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884690 pending Bug #884690 [python-backports.functools-lru-cache] ImportError with astroid 1.5 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884690:

Bug#825095: marked as pending

tag 825095 pending thanks Hello, Bug #825095 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at:

Processed: Bug#825095 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 825095 pending Bug #825095 [python-backports-shutil-get-terminal-size] python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname Ignoring request to alter tags of bug #825095 to

Processed: limit source to python-backports-shutil-get-terminal-size, tagging 825095

Processing commands for cont...@bugs.debian.org: > limit source python-backports-shutil-get-terminal-size Limiting to bugs with field 'source' containing at least one of 'python-backports-shutil-get-terminal-size' Limit currently set to 'source':'python-backports-shutil-get-terminal-size' >

Processed: tagging 880229

Processing commands for cont...@bugs.debian.org: > tags 880229 + moreinfo Bug #880229 [qbittorrent] qbittorrent fills /tmp filesystem causing other programs to fail Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 880229:

Processed: notfound 884947 in 3.1.4~abc9f50+dfsg1-2

Processing commands for cont...@bugs.debian.org: > notfound 884947 3.1.4~abc9f50+dfsg1-2 Bug #884947 [coin3] freecad: FreeCad crashes on start due to updated libcoin Bug #885101 [coin3] freecad: Segfault after start There is no source info for the package 'coin3' at version

Processed: severity of 880229 is important

Processing commands for cont...@bugs.debian.org: > severity 880229 important Bug #880229 [qbittorrent] qbittorrent fills /tmp filesystem causing other programs to fail Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Re: freecad: FreeCad crashes on start due to updated libcoin

Processing control commands: > reopen -1 Bug #884947 {Done: Anton Gladky } [coin3] freecad: FreeCad crashes on start due to updated libcoin Bug #885101 {Done: Anton Gladky } [coin3] freecad: Segfault after start 'reopen' may be inappropriate when a bug has

Bug#884947: freecad: FreeCad crashes on start due to updated libcoin

Source: coin3 Followup-For: Bug #884947 Control: reopen -1 Control: found -1 3.1.4~abc9f50+d Hi, I was to fast in concluding that the bug is fixed.. (I accidentially installed libcoin80, not the gcc5 abi one and it worked with that one) After fixing that (installing 80v5 again) I see the

Processed: affects 884947

Processing commands for cont...@bugs.debian.org: > affects 884947 freecad Bug #884947 {Done: Anton Gladky } [coin3] freecad: FreeCad crashes on start due to updated libcoin Bug #885101 {Done: Anton Gladky } [coin3] freecad: Segfault after start Added

Processed: reassign 885101 to coin3, forcibly merging 884947 885101

Processing commands for cont...@bugs.debian.org: > reassign 885101 coin3 Bug #885101 [freecad] freecad: Segfault after start Bug reassigned from package 'freecad' to 'coin3'. No longer marked as found in versions freecad/0.16.6712+dfsg1-1. Ignoring request to alter fixed versions of bug #885101

Processed (with 1 error): Re: freecad: Segfault after start

Processing control commands: > forcemerge 884947 -1 Bug #884947 {Done: Anton Gladky } [coin3] freecad: FreeCad crashes on start due to updated libcoin Unable to merge bugs because: package of #885101 is 'freecad' not 'coin3' Failed to forcibly merge 884947: Did not alter merged

Bug#885101: freecad: Segfault after start

Control: forcemerge 884947 -1 Control: affects -1 freecad This is #884947 in libcoin80. (It's already fixed). -- tobi

Bug#876599: marked as done (libcryptui FTBFS with gnupg 2.2)

Your message dated Mon, 25 Dec 2017 16:34:32 + with message-id and subject line Bug#876599: fixed in libcryptui 3.12.2-5 has caused the Debian Bug report #876599, regarding libcryptui FTBFS with gnupg 2.2 to be marked as done. This means that you claim

Processed: Correct the fixed version with the correct command

Processing commands for cont...@bugs.debian.org: > fixed 882790 0.7.1-2 Bug #882790 {Done: Piotr Ożarowski } [src:aiozmq] aiozmq: sourceful upload needed for the python3.6 transition Marked as fixed in versions aiozmq/0.7.1-2. > thanks Stopping processing here. Please contact

Processed: Bug is also in stretch

Processing commands for cont...@bugs.debian.org: > tags 880276 stretch Bug #880276 [src:ruby-encryptor] test using GCM with IV option fails after fix for CVE-2016-7798 Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 880276:

Processed: Corect the fixed version

Processing commands for cont...@bugs.debian.org: > notfixed 882790 0.7.0-2 Bug #882790 {Done: Piotr Ożarowski } [src:aiozmq] aiozmq: sourceful upload needed for the python3.6 transition The source 'aiozmq' and version '0.7.0-2' do not appear to match any binary packages No

Bug#853471: marked as done (kate4: ftbfs with GCC-7)

Your message dated Mon, 25 Dec 2017 15:19:38 + with message-id and subject line Bug#853471: fixed in kate4 4:4.14.3-5 has caused the Debian Bug report #853471, regarding kate4: ftbfs with GCC-7 to be marked as done. This means that you claim that the

Processed: hex-a-hop fix for #876600 is waiting in NEW

Processing commands for cont...@bugs.debian.org: > tags 876600 pending Bug #876600 [src:hex-a-hop] hex-a-hop FTBFS: msgfmt: found 1 fatal error Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 876600:

Bug#869994: Confirming with upstream tarball on openSUSE Tumbleweed

Hello everyone, I would like to point out that I just downloaded the upstream tarball and unpacked in my htdocs-Directory of my openSUSE "Tumbleweed" system and I am having the exact same issues as mentioned in the original bug. [Mon Dec 25 15:28:41.235156 2017] [cgi:error] [pid 509] [client

Bug#884974: sdpa: hardcoded mumps runtime dependency

On Sun, 24 Dec 2017 22:01:33 +0900 Makoto Yamashita wrote: > > However, unfortunately for us, I could not resolve the issues. > (I tried them before, but I could not.) > > When I prepared the debian package, I needed libmumps-seq-4.10.0. > Without

Bug#881767: marked as done (sensible-utils: CVE-2017-17512: Argument injection in sensible-browser)

Your message dated Mon, 25 Dec 2017 10:33:40 + with message-id and subject line Bug#881767: fixed in sensible-utils 0.0.9+deb8u1 has caused the Debian Bug report #881767, regarding sensible-utils: CVE-2017-17512: Argument injection in sensible-browser to

Bug#885157: thunderbird: Upgrading from 1:52.5.0-1 to 1:52.5.2-1 enforces the AppArmor profile

Hi, On Mon, Dec 25, 2017 at 08:55:34AM +0100, intrig...@debian.org wrote: > Package: thunderbird > Version: 1:52.5.2-1 > Severity: serious > X-Debbugs-Cc: Simon Deziel , Guido Günther > > > Hi, > > I've upgraded thunderbird from 1:52.5.0-1 to 1:52.5.2-1 in

Bug#883774: marked as done (otrs2: CVE-2017-16921: Remote code execution)

Your message dated Mon, 25 Dec 2017 10:33:36 + with message-id and subject line Bug#883774: fixed in otrs2 3.3.18-1+deb8u3 has caused the Debian Bug report #883774, regarding otrs2: CVE-2017-16921: Remote code execution to be marked as done. This means

Bug#885157: thunderbird: Upgrading from 1:52.5.0-1 to 1:52.5.2-1 enforces the AppArmor profile

Hello intrigeri, On Mon, Dec 25, 2017 at 08:55:34AM +0100, intrig...@debian.org wrote: > Hi, > > I've upgraded thunderbird from 1:52.5.0-1 to 1:52.5.2-1 in my test sid > VM after double-checking that > /etc/apparmor.d/disable/usr.bin.thunderbird existed and the profile > was not loaded. I

Bug#884034: trinity FTBFS with linux-libc-dev 4.14.2-1

Hi That's correct, I have an update ready to upload, just waiting until Debian takes my new key to upload (should only take a few more days) If you need an updated pkg you can retrieve the packaging git repo On December 25, 2017 4:41:33 PM GMT+08:00, Juhani Numminen

Bug#882315: marked as done (kwalify: FTBFS and Debci failure with ruby 2.3 2.3.5-1)

Your message dated Mon, 25 Dec 2017 08:50:56 + with message-id and subject line Bug#882315: fixed in kwalify 0.7.2-5 has caused the Debian Bug report #882315, regarding kwalify: FTBFS and Debci failure with ruby 2.3 2.3.5-1 to be marked as done. This

Bug#882315: marked as pending

tag 882315 pending thanks Hello, Bug #882315 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/kwalify.git/commit/?id=53f33c3 --- commit

Processed: Bug#882315 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 882315 pending Bug #882315 [src:kwalify] kwalify: FTBFS and Debci failure with ruby 2.3 2.3.5-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 882315:

Processed: Re: Bug#884034: trinity FTBFS with linux-libc-dev 4.14.2-1

Processing control commands: > tags 884034 fixed-upstream Bug #884034 [src:trinity] trinity FTBFS with linux-libc-dev 4.14.2-1 Added tag(s) fixed-upstream. -- 884034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#884034: trinity FTBFS with linux-libc-dev 4.14.2-1

Control: tags 884034 fixed-upstream Seems to be fixed in this commit: https://github.com/kernelslacker/trinity/commit/e4f31d5a1ce65974c2a6b2e6e1a2b16fffc51518 Juhani

  1   2   >