Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

On 14.03.2018 22:25, Adrian Bunk wrote: > Package: libinput-dev > Version: 1.10.3-1 > Severity: grave > Control: affects -1 src:efl src:gnome-twitch src:muffin src:mutter > src:gnome-shell > > https://buildd.debian.org/status/package.php?p=efl=sid > > ... > configure: error: pkg-config missing

Bug#892981: cenon.app: Incomplete debian/copyright?

Source: cenon.app Version: 4.0.6+ds1-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Yavor Doganov Hi, I just ACCEPTed cenon.app from NEW but noticed it was missing attribution in debian/copyright for at least Adobe Systems, NeXT, vhf interservice GmbH, GraphiCode,

Processed: bug 888198 is forwarded to https://github.com/lsegal/yard/issues/1161

Processing commands for cont...@bugs.debian.org: > forwarded 888198 https://github.com/lsegal/yard/issues/1161 Bug #888198 [src:yard] yard: FTBFS on ruby2.5: got: ("gem.deps.rb") Set Bug forwarded-to-address to 'https://github.com/lsegal/yard/issues/1161'. > thanks Stopping processing here.

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

Source: gnome-themes-extra Version: 3.27.92-1 Severity: serious Justication: Policy 12.5 Hi, I just ACCEPTed gnome-themes-extra from NEW but noticed it was missing attribution in debian/copyright for at least adwaita_engine.c under themes/Adwaita/gtk-2.0. (This is not exhaustive so please

Bug#892933: marked as done (isl-0.18: Incomplete debian/copyright?)

Your message dated Thu, 15 Mar 2018 05:19:36 + with message-id and subject line Bug#892933: fixed in isl-0.18 0.18-4 has caused the Debian Bug report #892933, regarding isl-0.18: Incomplete debian/copyright? to be marked as done. This means that you claim

Bug#883636: stretch update for showq

On Wed, Mar 14, 2018, 6:47 PM Adrian Bunk wrote: > On Tue, Jan 02, 2018 at 05:36:06PM +, Debian Bug Tracking System wrote: > >... > > showq (0.4.1+git20161215~dfsg0-3) unstable; urgency=medium > >... > >* Hack prefix to get app started. (Closes: #883636) > > Thanks

Bug#884542: marked as done (prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics)

Your message dated Thu, 15 Mar 2018 04:04:14 + with message-id and subject line Bug#884542: fixed in prometheus-mysqld-exporter 0.10.0+git20180201.a71f4bb+ds-1 has caused the Debian Bug report #884542, regarding prometheus-mysqld-exporter FTBFS: FAIL:

Bug#884542: Pending fixes for bugs in the prometheus-mysqld-exporter package

tag 884542 + pending thanks Some bugs in the prometheus-mysqld-exporter package are closed in revision d5f1611c81992321eb63d2f3eba13fd10d49886e in branch 'debian/sid' by Martín Ferrari The full diff can be seen at

Processed: Pending fixes for bugs in the prometheus-mysqld-exporter package

Processing commands for cont...@bugs.debian.org: > tag 884542 + pending Bug #884542 [src:prometheus-mysqld-exporter] prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884542:

Bug#890893: marked as done (appstream-glib FTBFS: error: redefinition of ‘glib_autoptr_cleanup_GCabCabinet’)

Your message dated Thu, 15 Mar 2018 02:50:04 + with message-id and subject line Bug#890893: fixed in appstream-glib 0.7.7-1 has caused the Debian Bug report #890893, regarding appstream-glib FTBFS: error: redefinition of ‘glib_autoptr_cleanup_GCabCabinet’

Bug#892891: marked as done (chromium: FTBFS: error: invalid application of 'sizeof' to incomplete type 'policy::ConfigurationPolicyProvider')

Your message dated Thu, 15 Mar 2018 01:37:24 + with message-id and subject line Bug#892891: fixed in chromium-browser 65.0.3325.146-4 has caused the Debian Bug report #892891, regarding chromium: FTBFS: error: invalid application of 'sizeof' to incomplete

Bug#890430: make: warning: -jN forced in submake: disabling jobserver mode.

On Fri, 16 Feb 2018 14:34:40 +0100 Aurelien Jarno wrote: > This problem also affects the build daemons, the build of the linux > package is much longer now on the architectures where make-dfsg does not > FTBFS. The linux package indeed builds in parallel by using the >

Bug#892971: libignition-fuel-tools1-{1,dev}: both ship /usr/lib/ruby/ignition/cmdfuel1.rb

Package: libignition-fuel-tools1-dev,libignition-fuel-tools1-1 Version: 1.0.0+dfsg4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Selecting

Bug#890997: marked as done (boxbackup FTBFS on i386: test failures)

Your message dated Wed, 14 Mar 2018 23:34:36 + with message-id and subject line Bug#890997: fixed in boxbackup 0.13~~git20180313.g16a11e86-1 has caused the Debian Bug report #890997, regarding boxbackup FTBFS on i386: test failures to be marked as done.

Bug#891957: netbeans no starting "loading module" modules.netbinox NullPointerException

Package: netbeans Version: 8.2+dfsg1-1 Followup-For: Bug #891957 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was

Bug#892723: marked as done (dehydrated: Dehydrated broken in stable due to unhandled redirect)

Your message dated Wed, 14 Mar 2018 22:17:08 + with message-id and subject line Bug#892723: fixed in dehydrated 0.3.1-3+deb9u2 has caused the Debian Bug report #892723, regarding dehydrated: Dehydrated broken in stable due to unhandled redirect to be

Bug#886120: doxygen = scapegoat ?

On Wed, Mar 14, 2018 at 09:34:36PM +0100, Paolo Greppi wrote: > @kilobyte, let me see if I can understand your purpose with this bug report. > > What happened is: > 1) you find a serious bug in ctpp2 (popcon: 14) > 2) you decide it's RC > 3) it's doxygen fault so you reassign it to doxygen

Bug#892960: libdrm FTBFS on arm*: symbol differences

Control: tags -1 + pending On 2018-03-14 22:44 +0200, Adrian Bunk wrote: > Source: libdrm > Version: 2.4.91-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=libdrm=sid > > ... >debian/rules override_dh_makeshlibs > make[1]: Entering directory '/<>' > dh_makeshlibs

Processed: Re: Bug#892960: libdrm FTBFS on arm*: symbol differences

Processing control commands: > tags -1 + pending Bug #892960 [src:libdrm] libdrm FTBFS on arm*: symbol differences Added tag(s) pending. -- 892960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#892964: mercurial: CVE-2018-1000132

Source: mercurial Version: 3.1.2-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for mercurial. CVE-2018-1000132[0]: | Mercurial version 4.5 and earlier contains a Incorrect Access Control | (CWE-285) vulnerability in Protocol server that can result in |

Bug#892849: [3dprinter-general] Bug#892849: Bug#892849: cura: Exception while launching cura

> ii  libarcus3  3.1.0-1  amd64    message queue for Cura based on p > ii  python3-arcus  3.1.0-1  amd64    message queue for Cura based on p > ii  python3-sip    4.19.8+dfsg- amd64    Python 3/C++ bindings generator r Thank you. Unfortunately, I cannot reproduce the

Bug#892960: libdrm FTBFS on arm*: symbol differences

Source: libdrm Version: 2.4.91-1 Severity: serious https://buildd.debian.org/status/package.php?p=libdrm=sid ... debian/rules override_dh_makeshlibs make[1]: Entering directory '/<>' dh_makeshlibs -plibdrm2 -V'libdrm2 (>= 2.4.89)' --add-udeb=libdrm2-udeb -- -c4 dh_makeshlibs -plibdrm-nouveau2

Bug#886120: doxygen = scapegoat ?

@kilobyte, let me see if I can understand your purpose with this bug report. What happened is: 1) you find a serious bug in ctpp2 (popcon: 14) 2) you decide it's RC 3) it's doxygen fault so you reassign it to doxygen (popcon: 8381), and it stays RC Now let's look at the effect of all this: 1)

Bug#892959: slic3r-prusa FTBFS on 32bit: error: format not a string literal and no format arguments

Source: slic3r-prusa Version: 1.39.1+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=slic3r-prusa=sid ... /usr/bin/perl -MExtUtils::XSpp::Cmd -e xspp -- -t "/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/typemap.xspt" "/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/Print.xsp": In function

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

Package: libinput-dev Version: 1.10.3-1 Severity: grave Control: affects -1 src:efl src:gnome-twitch src:muffin src:mutter src:gnome-shell https://buildd.debian.org/status/package.php?p=efl=sid ... configure: error: pkg-config missing libinput >= 0.6.0 xkbcommon >= 0.3.0 libudev Root cause

Processed: libinput-dev: Requires.private without package dependencies breaks pkg-config users

Processing control commands: > affects -1 src:efl src:gnome-twitch src:muffin src:mutter src:gnome-shell Bug #892956 [libinput-dev] libinput-dev: Requires.private without package dependencies breaks pkg-config users Added indication that 892956 affects src:efl, src:gnome-twitch, src:muffin,

Bug#892950: apcupsd FTBFS: python-imaging removed from pillow/5.0.0-1

Source: apcupsd Version: 3.14.14-1 Severity: serious User: helm...@debian.org Usertags: rebootstrap apcupsd fails to build from source in unstable. Its Build-Depends are no longer satisfiable, because python-imaging was removed from pillow/5.0.0-1. Helmut

Processed: severity of 892945 is normal

Processing commands for cont...@bugs.debian.org: > severity 892945 normal Bug #892945 [libvirt-daemon] Cannot start domain using user session Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 892945:

Bug#890465: marked as done (pioneers: Depends on libgnome)

Your message dated Wed, 14 Mar 2018 19:20:21 + with message-id and subject line Bug#890465: fixed in pioneers 15.5-1 has caused the Debian Bug report #890465, regarding pioneers: Depends on libgnome to be marked as done. This means that you claim that the

Bug#886044: syncmaildir: raising severity of gconf dependency bug

On Wed, 14 Mar 2018 09:55:36 +0100, Enrico Tassi wrote: > > Looking at the ChangeLog and the git history, it seems that gconf has > > been replaced by gsettings already in 1.2.6. > > Grepping through the code shows two leftovers, the build dependency in > > debian/control, and a mentioning in

Bug#892375: marked as done (isl: Incomplete debian/copyright?)

Your message dated Wed, 14 Mar 2018 18:51:28 + with message-id and subject line Bug#892375: fixed in isl 0.19-1 has caused the Debian Bug report #892375, regarding isl: Incomplete debian/copyright? to be marked as done. This means that you claim that the

Bug#886532: Coming updates for meltdown/spectre

On Sun, 7 Jan 2018 12:11:17 + Nigel Kukard wrote: > > Is it going to be possible to include this patch in qemu please? > > https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00811.html > > > ref: https://www.qemu.org/2018/01/04/spectre/ > FTR this seems to be part

Bug#892799: Bug #892799 in libtgvoip marked as pending

Control: tag -1 pending Hello, Bug #892799 in libtgvoip 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:

Processed: Bug #892799 in libtgvoip marked as pending

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

Bug#892945: Cannot start domain using user session

Package: libvirt-daemon Version: 4.0.0-2 Severity: serious Hi, I cannot start a domain using a libvirt user session. I'm getting the following message: Impossible de terminer l’installation : « internal error: process exited while connecting to monitor: Could not access KVM kernel module:

Bug#888153: marked as done (prometheus: Performance problems in 2.1.0)

Your message dated Wed, 14 Mar 2018 18:34:48 + with message-id and subject line Bug#888153: fixed in prometheus 2.2.0+ds-1 has caused the Debian Bug report #888153, regarding prometheus: Performance problems in 2.1.0 to be marked as done. This means that

Bug#888153: Pending fixes for bugs in the prometheus package

tag 888153 + pending thanks Some bugs in the prometheus package are closed in revision 15211deb72e4a23726c1fd5467e20d4cfd3eb231 in branch 'debian/sid' by Martín Ferrari The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/prometheus.git/commit/?id=15211de Commit message:

Processed: Pending fixes for bugs in the prometheus package

Processing commands for cont...@bugs.debian.org: > tag 888153 + pending Bug #888153 [prometheus] prometheus: Performance problems in 2.1.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 888153:

Bug#881342: stretch update for rtkit

On Wed, Mar 14, 2018 at 2:35 PM, Adrian Bunk wrote: > On Wed, Feb 21, 2018 at 03:24:08PM +, Debian Bug Tracking System wrote: > >... > > rtkit (0.11-6) unstable; urgency=medium > > . > >* Move dbus and polkit from Recommends to Depends > > rtkit can't do much

Bug#877457: stretch update for trafficserver

On Wed, Jan 17, 2018 at 09:42:09AM +, Debian Bug Tracking System wrote: >... > trafficserver (7.1.1-1) unstable; urgency=medium > . >* Fix trafficserver-dev dependencies. (Closes: #877457) >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you

Bug#883636: stretch update for showq

On Tue, Jan 02, 2018 at 05:36:06PM +, Debian Bug Tracking System wrote: >... > showq (0.4.1+git20161215~dfsg0-3) unstable; urgency=medium >... >* Hack prefix to get app started. (Closes: #883636) > Thanks to James Cowgill >... Thanks a lot for fixing this bug

Bug#876251: stretch update for ola

On Thu, Sep 28, 2017 at 12:21:11PM +, Debian Bug Tracking System wrote: >... > ola (0.10.5.nojsmin-3) unstable; urgency=medium >... >* debian/ola-rdm-tests.rdm_test_server.init: fix typo. Closes: #876251 >... Thanks a lot for fixing this bug for unstable. It is still present in stretch,

Bug#881342: stretch update for rtkit

On Wed, Feb 21, 2018 at 03:24:08PM +, Debian Bug Tracking System wrote: >... > rtkit (0.11-6) unstable; urgency=medium > . >* Move dbus and polkit from Recommends to Depends > rtkit can't do much really without either of them so bump them to > Depends. > (Closes: #881342) >...

Processed: Re: [Openjdk] Bug#891573: openjdk-10: builds with unlimited 'make -j'

Processing control commands: > severity -1 important Bug #891573 [src:openjdk-10] openjdk-10: builds with unlimited 'make -j' Severity set to 'important' from 'serious' -- 891573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891573 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#891573: [Openjdk] Bug#891573: openjdk-10: builds with unlimited 'make -j'

Control: severity -1 important On 26.02.2018 19:56, Andreas Beckmann wrote: > Source: openjdk-10 > Version: 10~32-1 > Severity: serious > Justification: make build machine unusable while building > > Hi, > > I just stumbled upon load 425 while rebuilding openjdk-10 in > experimental ... the

Bug#867414: stretch update for pymongo

On Tue, Aug 29, 2017 at 11:30:06PM +, Debian Bug Tracking System wrote: >... > pymongo (3.5.1+dfsg1-1) unstable; urgency=medium >... >* Fix python3-pymongo-ext dependency (Closes: #867414) >... Thanks a lot for fixing this bug for unstable. It is still present in stretch, could you also

Bug#867464: stretch update for radicale

On Wed, Aug 23, 2017 at 10:54:05PM +, Debian Bug Tracking System wrote: >... > radicale (2.1.4-2) experimental; urgency=medium > . >* Fix resolve python-related dependencies and provisions, and drop > deprecated (and bogus, for python3 package) XB-Python-Version field. >

Bug#892933: isl-0.18: Incomplete debian/copyright?

Source: isl-0.18 Version: 0.18-2 Severity: serious Justication: Policy 12.5 Hi, I just ACCEPTed isl-0.18 from NEW but noticed it was missing attribution in debian/copyright for at least a code copy (?) of imath. (This is not exhaustive so please check over the entire package carefully and

Bug#880047: stretch update for postgrey

On Tue, Mar 13, 2018 at 11:25:21AM +0100, Julien Cristau wrote: > On 03/12/2018 07:03 PM, Adrian Bunk wrote: > > On Sat, Nov 25, 2017 at 10:36:10AM +, Debian Bug Tracking System wrote: > >> ... > >> postgrey (1.36-5) unstable; urgency=medium > >> . > >>* debian/postgrey.init: create

Bug#892926: marked as done (gcc-7-cross-ports stopped building packages that some of its binaries depend upon)

Your message dated Wed, 14 Mar 2018 17:40:16 +0100 with message-id and subject line Re: Bug#892926: gcc-7-cross-ports stopped building packages that some of its binaries depend upon has caused the Debian Bug report #892926, regarding

Processed: notfound 886806 in intel-microcode/3.20140913.1

Processing commands for cont...@bugs.debian.org: > notfound 886806 intel-microcode/3.20140913.1 Bug #886806 {Done: Henrique de Moraes Holschuh } [intel-microcode] intel-microcode: New version 20180108 published No longer marked as found in versions intel-microcode/3.20140913.1.

Processed: retitle 886367 to intel-microcode: spectre microcode updates for unstable/testing

Processing commands for cont...@bugs.debian.org: > retitle 886367 intel-microcode: spectre microcode updates for unstable/testing Bug #886367 [intel-microcode] intel-microcode: coming updates for meltdown/spectre Changed Bug title to 'intel-microcode: spectre microcode updates for

Processed: closing 886806

Processing commands for cont...@bugs.debian.org: > close 886806 Bug #886806 [intel-microcode] intel-microcode: New version 20180108 published Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 886806:

Processed: retitle 887856 to intel-microcode: spectre microcode updates for stable

Processing commands for cont...@bugs.debian.org: > retitle 887856 intel-microcode: spectre microcode updates for stable Bug #887856 [intel-microcode] intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch Changed Bug title to 'intel-microcode: spectre microcode updates

Bug#888121: marked as done (ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as')

Your message dated Wed, 14 Mar 2018 16:11:30 + with message-id and subject line Bug#888121: fixed in ruby-delayed-job 4.1.4-1 has caused the Debian Bug report #888121, regarding ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined

Processed: notfixed 886367 in intel-microcode/3.20180108.1

Processing commands for cont...@bugs.debian.org: > notfixed 886367 intel-microcode/3.20180108.1 Bug #886367 [intel-microcode] intel-microcode: coming updates for meltdown/spectre No longer marked as fixed in versions intel-microcode/3.20180108.1. > thanks Stopping processing here. Please

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

On Wed, Mar 14, 2018 at 12:39:22PM -0300, Henrique de Moraes Holschuh wrote: > On Wed, 14 Mar 2018, Moritz Muehlenhoff wrote: > > On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote: > > > severity 887856 grave > > > block 887856 by 886998 > > > thanks > > > > > > On Sat,

Processed: notfixed 886367 in intel-microcode/3.20171215.1

Processing commands for cont...@bugs.debian.org: > notfixed 886367 intel-microcode/3.20171215.1 Bug #886367 [intel-microcode] intel-microcode: coming updates for meltdown/spectre No longer marked as fixed in versions intel-microcode/3.20171215.1. > thanks Stopping processing here. Please

Bug#892074: marked as done (uwsgi: FTBFS with ruby2.5 as default)

Your message dated Wed, 14 Mar 2018 16:00:37 + with message-id and subject line Bug#892074: fixed in uwsgi 2.0.15-10.3 has caused the Debian Bug report #892074, regarding uwsgi: FTBFS with ruby2.5 as default to be marked as done. This means that you claim

Bug#892735: marked as done (beets tests pull in resources from the network, and fail as well)

Your message dated Wed, 14 Mar 2018 16:00:10 + with message-id and subject line Bug#892735: fixed in beets 1.4.6-2 has caused the Debian Bug report #892735, regarding beets tests pull in resources from the network, and fail as well to be marked as done.

Processed: fixed 886367 in intel-microcode/3.20180312.1

Processing commands for cont...@bugs.debian.org: > fixed 886367 intel-microcode/3.20180312.1 Bug #886367 [intel-microcode] intel-microcode: coming updates for meltdown/spectre Marked as fixed in versions intel-microcode/3.20180312.1. > thanks Stopping processing here. Please contact me if you

Processed: notfixed 886367 in intel-microcode/3.20180108.1+really20171117.1

Processing commands for cont...@bugs.debian.org: > notfixed 886367 intel-microcode/3.20180108.1+really20171117.1 Bug #886367 [intel-microcode] intel-microcode: coming updates for meltdown/spectre Ignoring request to alter fixed versions of bug #886367 to the same values previously set > thanks

Bug#892911: marked as done (intel-microcode: New version 20180312 published)

Your message dated Wed, 14 Mar 2018 12:40:58 -0300 with message-id <20180314154058.z3zakxy2xpr6p...@khazad-dum.debian.net> and subject line Re: Bug#892911: intel-microcode: New version 20180312 published has caused the Debian Bug report #892911, regarding intel-microcode: New version 20180312

Processed: found 886367 in intel-microcode/3.20180108.1+really20171117.1

Processing commands for cont...@bugs.debian.org: > found 886367 intel-microcode/3.20180108.1+really20171117.1 Bug #886367 {Done: Henrique de Moraes Holschuh } [intel-microcode] intel-microcode: coming updates for meltdown/spectre Marked as found in versions

Bug#892926: gcc-7-cross-ports stopped building packages that some of its binaries depend upon

Source: gcc-7-cross-ports Version: 11 Severity: serious Since February 2018, some of the binary packages are not built anymore. Per the changelog: gcc-7-cross-ports (10) unstable; urgency=medium * Build using 7.3.0-4. * * Stop building packages now built from gcc-8-cross. * --

Processed: unarchiving 886367

Processing commands for cont...@bugs.debian.org: > unarchive 886367 Bug #886367 {Done: Henrique de Moraes Holschuh } [intel-microcode] intel-microcode: coming updates for meltdown/spectre Unarchived Bug 886367 > thanks Stopping processing here. Please contact me if you need

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

On Wed, 14 Mar 2018, Moritz Muehlenhoff wrote: > On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote: > > severity 887856 grave > > block 887856 by 886998 > > thanks > > > > On Sat, 20 Jan 2018, Julien Aubin wrote: > > > As of now intel-microcode of stretch is still set to

Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

FYI Forwarded Message Subject: [Debian-astro-maintainers] ftools update Date: Wed, 14 Mar 2018 10:42:25 -0400 From: Michael Arida To: debian-astro-maintain...@lists.alioth.debian.org Dear Debian Astro Maintainers, As you may have noticed CFITSIO was

Bug#880842: marked as done (gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option "use-deprecated-webkit": "descritpion")

Your message dated Wed, 14 Mar 2018 15:19:28 + with message-id and subject line Bug#880842: fixed in gnome-twitch 0.4.1-1.1 has caused the Debian Bug report #880842, regarding gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option

Bug#865798: marked as done (golang-github-shopify-sarama FTBFS: test failures)

Your message dated Wed, 14 Mar 2018 15:19:36 + with message-id and subject line Bug#865798: fixed in golang-github-shopify-sarama 1.16.0-1 has caused the Debian Bug report #865798, regarding golang-github-shopify-sarama FTBFS: test failures to be marked as

Processed: gnome-twitch: diff for NMU version 0.4.1-1.1

Processing control commands: > tags 880842 + pending Bug #880842 [src:gnome-twitch] gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option "use-deprecated-webkit": "descritpion" Added tag(s) pending. -- 880842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880842 Debian Bug

Bug#880842: gnome-twitch: diff for NMU version 0.4.1-1.1

Control: tags 880842 + pending On Sun, 11 Mar 2018 20:58:24 -0400 Jeremy Bicha wrote: > Control: forwarded -1 https://github.com/vinszent/gnome-twitch/commit/6bee8bc0 > Control: tags -1 fixed-upstream patch > > Dear maintainer, I've prepared an NMU for gnome-twitch

Bug#892645: [gnome-twitch] Segfault on json node

control: severity -1 important Hello, On Sun, 11 Mar 2018 20:46:04 -0400 Jeremy Bicha wrote: > Is this reproducible with gnome-twitch 0.4.1-1 from experimental? > please try to reproduce with the one I'm uploading in unstable, and raise severity again if you get the same

Processed: Re: [gnome-twitch] Segfault on json node

Processing control commands: > severity -1 important Bug #892645 [gnome-twitch] [gnome-twitch] Segfault on json node Severity set to 'important' from 'grave' -- 892645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892645 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: add chromium prefix

Processing commands for cont...@bugs.debian.org: > retitle 892891 chromium: FTBFS: error: invalid application of 'sizeof' to > incomplete type 'policy::ConfigurationPolicyProvider' Bug #892891 [chromium] FTBFS: error: invalid application of 'sizeof' to incomplete type

Processed: Bug#892891: 65.0.3325.146-3 never uploaded

Processing control commands: > severity -1 serious Bug #892891 [chromium] 65.0.3325.146-3 never uploaded Severity set to 'serious' from 'normal' > retitle -1 FTBFS: error: invalid application of 'sizeof' to incomplete type > 'policy::ConfigurationPolicyProvider' Bug #892891 [chromium]

Bug#888124: marked as done (ruby-fakeweb: FTBFS on ruby2.5: undefined method `close' for #)

Your message dated Wed, 14 Mar 2018 13:50:46 + with message-id and subject line Bug#888124: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-1 has caused the Debian Bug report #888124, regarding ruby-fakeweb: FTBFS on ruby2.5: undefined method `close' for #

Bug#868839: marked as done (ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19)

Your message dated Wed, 14 Mar 2018 13:50:53 + with message-id and subject line Bug#868851: fixed in ruby-mustermann 1.0.0-4 has caused the Debian Bug report #868851, regarding ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19 to be marked as

Bug#868851: marked as done (ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19)

Your message dated Wed, 14 Mar 2018 13:50:53 + with message-id and subject line Bug#868851: fixed in ruby-mustermann 1.0.0-4 has caused the Debian Bug report #868851, regarding ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19 to be marked as

Bug#891901: arduino: Doesn't open.

On Fri, Mar 02, 2018 at 11:21:41AM +0100, Nicola wrote: > Package: arduino > Version: 2:1.5.6.2+sdfsg2-3 > Severity: grave > Tags: a11y > Justification: renders package unusable > Yes, it is sad to see there is no recent Arduino in Debian. Recent Arduino versions are reported in

Processed: Bug #868851 in ruby-mustermann marked as pending

Processing control commands: > tag -1 pending Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19 Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19 Added tag(s) pending. Added tag(s) pending. -- 868839:

Bug#868851: Bug #868851 in ruby-mustermann marked as pending

Control: tag -1 pending Hello, Bug #868851 in ruby-mustermann 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:

Bug#891245: marked as done (CVE-2018-6544 / CVE-2018-1000051)

Your message dated Wed, 14 Mar 2018 12:49:48 + with message-id and subject line Bug#891245: fixed in mupdf 1.12.0+ds1-1 has caused the Debian Bug report #891245, regarding CVE-2018-6544 / CVE-2018-151 to be marked as done. This means that you claim

Bug#892912: pytrainer: startup fails because gtk2 features were dropped from matplotlib

Source: pytrainer Version: 1.11.0-1 Severity: grave Tags: sid buster upstream Forwarded: https://github.com/pytrainer/pytrainer/issues/114 Since matplotlib 2.1.1-1 was uploaded to unstable dropping gtk2 features (last january) pytrainer fails at startup throwing an ImportError. Please see:

Bug#892911: intel-microcode: New version 20180312 published

Package: intel-microcode Version: 3.20180108.1+really20171117.1 Severity: grave Tags: security Hello! It looks like there has been a new release. The data file version is 20180312. The microcode download page is

Bug#878216: Info received (More informations about HyperV version impacted)

Hi, Just to add, look like only gen2 of vm are affected (But I have only few cases: 8) Best regards Vince

Bug#871153: marked as done (libqb: FTBFS: dh_auto_test: make -j16 check VERBOSE=1 returned exit code 2)

Your message dated Wed, 14 Mar 2018 12:04:18 + with message-id and subject line Bug#871153: fixed in libqb 1.0.3-1 has caused the Debian Bug report #871153, regarding libqb: FTBFS: dh_auto_test: make -j16 check VERBOSE=1 returned exit code 2 to be marked

Bug#892373: marked as done (proftpd-mod-fsync FTBFS with proftpd 1.3.6-1)

Your message dated Wed, 14 Mar 2018 11:53:13 + with message-id and subject line Bug#892373: fixed in proftpd-mod-fsync 0.3-1 has caused the Debian Bug report #892373, regarding proftpd-mod-fsync FTBFS with proftpd 1.3.6-1 to be marked as done. This means

Bug#892371: marked as done (proftpd-mod-vroot FTBFS with proftpd 1.3.6-1)

Your message dated Wed, 14 Mar 2018 11:53:22 + with message-id and subject line Bug#892371: fixed in proftpd-mod-vroot 0.9.4-2 has caused the Debian Bug report #892371, regarding proftpd-mod-vroot FTBFS with proftpd 1.3.6-1 to be marked as done. This

Processed: bug 888508 is forwarded to https://gitlab.com/gitlab-org/gitlab-ce/issues/44244

Processing commands for cont...@bugs.debian.org: > forwarded 888508 https://gitlab.com/gitlab-org/gitlab-ce/issues/44244 Bug #888508 [src:gitlab] gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory Set Bug forwarded-to-address to

Processed: Re: Bug#892738: consolekit: consolekit removal causes a regression

Processing commands for cont...@bugs.debian.org: > notfound 892738 0.4.6-6 Bug #892738 [consolekit] consolekit: consolekit removal causes a regression No longer marked as found in versions consolekit/0.4.6-6. > found 892738 0.4.6-6.1 Bug #892738 [consolekit] consolekit: consolekit removal causes

Bug#892738: consolekit: consolekit removal causes a regression

notfound 892738 0.4.6-6 found 892738 0.4.6-6.1 thanks Dear Maintainer, correct the complained version from 0.4.6-6 to 0.4.6-6.1, since 0.4.6-6 is OK, and due to https://tracker.debian.org/news/928882 add the NMU uploader to CC. Sincerly yours Bene

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote: > severity 887856 grave > block 887856 by 886998 > thanks > > On Sat, 20 Jan 2018, Julien Aubin wrote: > > As of now intel-microcode of stretch is still set to 20170707 (20171117 > > through > > bpo) which lets users

Bug#892096: gcc-snapshot: AddressSanitizer uses glibc internal functions

Control: reopen -1 On 2018-03-14 10:27:35 +0100, Vincent Lefevre wrote: > On 2018-03-14 09:20:17 +0100, Matthias Klose wrote: > > now built using glibc-2.27. > > Which version? FYI, I still obtain a crash with 201803012-1. Reopening since 201803012-1 depends on libc6 (>= 2.27), thus has

Processed: Re: gcc-snapshot: AddressSanitizer uses glibc internal functions

Processing control commands: > reopen -1 Bug #892096 {Done: Matthias Klose } [gcc-snapshot] gcc-snapshot: AddressSanitizer uses glibc internal functions Bug reopened Ignoring request to alter fixed versions of bug #892096 to the same values previously set -- 892096:

Processed (with 1 error): forcibly merging 888123 892798 888194

Processing commands for cont...@bugs.debian.org: > forcemerge 888123 892798 888194 Bug #888123 {Done: Cédric Boutillier } [src:ruby-safe-yaml] ruby-crack: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime Bug #888194 {Done: Cédric Boutillier

Processed: reassign 892798 to ruby-safe-yaml

Processing commands for cont...@bugs.debian.org: > reassign 892798 ruby-safe-yaml Bug #892798 [ruby-crack] ruby-crack FTBFS uninitialized constant SafeYAML::Parse::Date::DateTime (NameError) Bug reassigned from package 'ruby-crack' to 'ruby-safe-yaml'. No longer marked as found in versions

Bug#892874: marked as done (libmatio-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libmatio-dev/NEWS.gz)

Your message dated Wed, 14 Mar 2018 09:49:20 + with message-id and subject line Bug#892874: fixed in libmatio 1.5.12-2 has caused the Debian Bug report #892874, regarding libmatio-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite

Bug#892900: marked as done (console-setup: The last update console-setup 1.179 fails in its postinstallation scripts)

Your message dated Wed, 14 Mar 2018 09:34:06 + with message-id and subject line Bug#892900: fixed in console-setup 1.180 has caused the Debian Bug report #892900, regarding console-setup: The last update console-setup 1.179 fails in its postinstallation

Bug#891029: marked as done (dxf2gcode: overly generic python module name: /usr/lib/python3/dist-packages/core/__init__.py)

Your message dated Wed, 14 Mar 2018 09:34:12 + with message-id and subject line Bug#891029: fixed in dxf2gcode 20170925-2 has caused the Debian Bug report #891029, regarding dxf2gcode: overly generic python module name:

  1   2   >