Bug#851667: shifted bug in openjdk-8 8u121-b13-1

2017-02-02 Thread Jesse Lopez
This update has completely broken the installation of openjdk-8-j* on Jessie via backports. The bug report needs to be reopened.

Bug#854020: Wine does not longer work with OSS

2017-02-02 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: wine64-development Version: 2.0-3 Severity: grave The newest package does not work anymore with OSS sound system. That renders Wine nearly unusable as the only think where I need wine is to play WoW. OSS is the only sound system working. (

Bug#853998: CVE-2017-3250 / CVE-2017-3249 / CVE-2017-3247 / CVE-2016-5528 / CVE-2016-5519

2017-02-02 Thread Emmanuel Bourg
Le 2/02/2017 à 23:08, Moritz Muehlenhoff a écrit : > So Oracle has these lovely, unspecified vulnerabilities reported against > Glassfish, > but it's my understanding that the Debian package only provides a minor subset > what usually constitutes Java, so could you have a look, which of > > htt

Bug#853926: cloud-init depends on net-base

2017-02-02 Thread Adam Bolte
On closer inspection, the error from netstat is different. I missed the "Reason: [Errno 2] No such file or directory: 'netstat'" line from the original report, so I'm seeing a different bug. If the netstat command isn't doing anything critical (as implied by cloud-init otherwise working just fine

Bug#853926: cloud-init depends on net-base

2017-02-02 Thread Adam Bolte
On Thu, Feb 02, 2017 at 02:22:12PM +0100, Thomas Goirand wrote: > I don't see how Jessie would be affected, as there, net-base is > still an essential package. You are correct, and it certainly is installed into the AMIs in question. I think the suggested cause is incorrect. From the debug log:

Bug#853926: Retitle cloud-init net-base -> net-tools

2017-02-02 Thread gustavo panizzo
Control: retitle -1 cloud-init depends on net-tools thanks On Thu, Feb 02, 2017 at 02:50:45PM +0100, Thomas Goirand wrote: > There's no such package as net-base. Did you mean net-tools? yes, i meant to say net-tools. the retitle email never came through Zigo, sorry if you get this email twice -

Processed: Re: Bug#853926: Retitle cloud-init net-base -> net-tools

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 cloud-init depends on net-tools Bug #853926 [cloud-init] cloud-init depends on net-base Bug #853744 [cloud-init] cloud-init needs net-tools Changed Bug title to 'cloud-init depends on net-tools' from 'cloud-init depends on net-base'. Changed Bug title to

Bug#853921: ttx and grep result for DroidSansFallback(Full)?.ttf

2017-02-02 Thread Cyril Brulebois
[ Adding Kenshi Muto to recipients for having suggested the switch to fonts-android-udeb. ;) Context: We have no glyphs for Korean right now. Quoting in full my previous mail on that topic. ] Hi, Cyril Brulebois (2017-02-03): > victory (2017-02-03): > > added testing src apt line, apt update, a

Bug#853921: ttx and grep result for DroidSansFallback(Full)?.ttf

2017-02-02 Thread Cyril Brulebois
Hi, victory (2017-02-03): > added testing src apt line, apt update, apt-get source ..., tar zxf ... > $ ttx DroidSansFallback.ttf > $ ttx DroidSansFallbackFull.ttf > these 2 generate [filename].ttx > > (just FYI, used letters (in ko) other than 7-bit are in 0xac00-0xd790 range) > > $ grep Hangu

Processed: Re: [pkg-gnupg-maint] Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > affects 853935 + src:gnupg2 Bug #853935 [rephrase] rephrase: No more works with gpg2 and causes one pinentry popup per guess Added indication that 853935 affects src:gnupg2 -- 853935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853935 Debian Bug Tracking Syst

Bug#853935: [pkg-gnupg-maint] Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

2017-02-02 Thread Daniel Kahn Gillmor
Control: affects 853935 + src:gnupg2 Hi folks-- On Thu 2017-02-02 05:37:30 -0500, Axel Beckert wrote: > It seems that rephrase is incompatible or at least not yet ported to > GnuPG 2.x. > > Trying to use it on Sid or Stretch causes one pinentry window popup per > guessed try (i.e. potentially tho

Processed: found 853755 in 232-11

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 853755 232-11 Bug #853755 [systemd] systemd-udevd.service fails to start on ppc64el Bug #852811 [systemd] udev: Doesn't start after upgrade powerpc Bug #853940 [systemd] systemd: RestrictAddressFamilies causes services to fail to start on p

Bug#852884: marked as done (Requires "-lssl -lcrypto" but does not depend on an OpenSSL -dev package)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Fri, 03 Feb 2017 00:18:27 + with message-id and subject line Bug#852884: fixed in libesmtp 1.0.6-4.2 has caused the Debian Bug report #852884, regarding Requires "-lssl -lcrypto" but does not depend on an OpenSSL -dev package to be marked as done. This means that you claim

Bug#854008: kstars-data-extra-tycho2: deepstars.dat installed in wrong directory

2017-02-02 Thread Jan Echternach
Package: kstars-data-extra-tycho2 Version: 1.1r1-9 Severity: grave Justification: renders package unusable The current testing version of kstars, version 4:16.08.3-1, expects deepstars.dat to reside in /usr/share/kstars along with its other data files. However, the current testing version of kstar

Processed: reassign 853755 to systemd, reassign 852811 to systemd, forcibly merging 853755 852811 853940 ...

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 853755 systemd Bug #853755 [src:systemd] systemd-udevd.service fails to start on ppc64el Bug reassigned from package 'src:systemd' to 'systemd'. No longer marked as found in versions systemd/232-11. Ignoring request to alter fixed version

Processed: Forwarded #849932

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 849932 https://bugzilla.xamarin.com/show_bug.cgi?id=52262 Bug #849932 [gtk-sharp2-gapi] gtk-sharp2-gapi: gapi2-codegen generates fields with void type Set Bug forwarded-to-address to 'https://bugzilla.xamarin.com/show_bug.cgi?id=52262'

Bug#853937: [package:tex-common] dist-upgrade fails on ann error of updmap-sys, teaving tex-common unconfigured

2017-02-02 Thread Norbert Preining
severity 853937 serious merge 853970 853937 thanks > Move to the package. Already there ..., in fact at texlive-lang-japanese. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC

Processed (with 1 error): Re: Bug#853937: [package:tex-common] dist-upgrade fails on ann error of updmap-sys, teaving tex-common unconfigured

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 853937 serious Bug #853937 [tex-common] [package:tex-common] dist-upgrade fails on ann error of updmap-sys, teaving tex-common unconfigured Severity set to 'serious' from 'grave' > merge 853970 853937 Bug #853970 [tex-common] errors duri

Bug#849932: libindicate: FTBFS (Fields cannot have void type)

2017-02-02 Thread Gilles Filippini
Control: reassign -1 gtk-sharp2-gapi Control: affects -1 src:libindicate Control: retitle -1 gtk-sharp2-gapi: gapi2-codegen generates fields with void type Gilles Filippini a écrit le 01/02/2017 à 00:05 : > On Mon, 02 Jan 2017 12:01:41 + Santiago Vila wrote: >> I tried to build this package

Processed: Re: libindicate: FTBFS (Fields cannot have void type)

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 gtk-sharp2-gapi Bug #849932 [src:libindicate] libindicate: FTBFS (Fields cannot have void type) Bug reassigned from package 'src:libindicate' to 'gtk-sharp2-gapi'. No longer marked as found in versions libindicate/0.6.92-3. Ignoring request to alter fixed

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

2017-02-02 Thread Mathieu Parent
2017-02-02 21:36 GMT+01:00 Mathieu Parent : > 2017-02-02 20:36 GMT+01:00 Michael Meskes : >>> Sorry, my patch was wrong >>> >>> local _, unix = pcall(require, "socket.unix"); >>> if unix then >>>socket.unix = unix.stream or unix.tcp; >>> end >>> >> >> This one seems to work. Gre

Bug#852380: Proposed ekeyd fix

2017-02-02 Thread Mathieu Parent
Hi, Can you try the attached patch with both lua-socket versions? - 3.0~rc1+git+321c0c9-2 - 3.0~rc1+git+ac3201d-3 Thanks -- Mathieu Parent From 7ae3639338b643a42e3a7dd9672ab00f514debc0 Mon Sep 17 00:00:00 2001 From: Mathieu Parent Date: Thu, 2 Feb 2017 23:26:03 +0100 Subject: [PATCH] Fix compa

Processed: severity of 853282 is grave

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 853282 grave Bug #853282 [bitlbee] bitlbee: Incomplete fix for "Null pointer dereference with file transfer request from unknown contacts" issue Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact

Processed: severity of 852385 is grave

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 852385 grave Bug #852385 [src:libplist] libplist: CVE-2017-5545 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 852385: http://bugs.debian.org/cgi-bin/bugreport.cg

Bug#854000: CVE-2017-5834 CVE-2017-5835 CVE-2017-5836

2017-02-02 Thread Moritz Muehlenhoff
Source: libplist Severity: grave Tags: security CVE-2017-5834: heap-buffer-overflow in parse_dict_node https://github.com/libimobiledevice/libplist/issues/89 CVE-2017-5835: memory allocation error https://github.com/libimobiledevice/libplist/issues/88 CVE-2017-5836 issue in plist_free_data plist

Processed: severity of 851196 is grave

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 851196 grave Bug #851196 [src:libplist] libplist: CVE-2017-5209 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 851196: http://bugs.debian.org/cgi-bin/bugreport.cg

Bug#794466: VIrtualBox future in Debian

2017-02-02 Thread Moritz Muehlenhoff
On Mon, Jan 30, 2017 at 02:36:11PM +, Gianfranco Costamagna wrote: > fully agree, but I'm not in the position to revert this change > >Why can't the Security Team treat VirtualBox like how it's been > >treating WebKit1? Still have it in the archives but with a prominent > >notice that Debian do

Bug#853998: CVE-2017-3250 / CVE-2017-3249 / CVE-2017-3247 / CVE-2016-5528 / CVE-2016-5519

2017-02-02 Thread Moritz Muehlenhoff
Source: glassfish Severity: grave Tags: security So Oracle has these lovely, unspecified vulnerabilities reported against Glassfish, but it's my understanding that the Debian package only provides a minor subset what usually constitutes Java, so could you have a look, which of http://www.oracle

Bug#852532: Acknowledgement (olvwm: source code not 64-bit clean, SIGSEGV everywhere)

2017-02-02 Thread Benjamin Moody
Unless there is an automated way to identify all the cases of integer/pointer confusion, I don't expect there'll ever be a way to make libxview work on LP64 systems. I am less familiar with olwm/olvwm, but this report is not encouraging. It seems to me that the most sensible thing to do would be

Bug#853997: CVE-2017-5849

2017-02-02 Thread Moritz Muehlenhoff
Source: netpbm-free Severity: grave Tags: security Please see http://www.openwall.com/lists/oss-security/2017/02/02/2 Cheers, Moritz

Processed: Re: Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #843474 [src:ruby-ethon] ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800 Severity set to 'normal' from 'serious' > tags -1 + unreproducible moreinfo Bug #843474 [src:ruby-ethon] ruby-ethon: FTBFS: [BUG] Segmentation fault at 0

Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800

2017-02-02 Thread Christian Hofstaedtler
Control: severity -1 normal Control: tags -1 + unreproducible moreinfo > ruby-ethon fails to build from source in unstable/amd64: Builds for me just fine in sbuild (multiple builds). More info needed. Best, -ch

Bug#841586: marked as done (ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown option '--force')

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 2 Feb 2017 22:43:46 +0100 with message-id <20170202214346.ga25...@percival.namespace.at> and subject line Re: ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown option '--force' has caused the Debian Bug report #841586, regarding ruby-em-synchrony: FTBFS: mysql_ins

Processed: retitle 841586 to ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 841586 ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown > option '--force' Bug #841586 [src:ruby-em-synchrony] ruby-em-synchrony: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [em-synchrony.gemspec]: No such file or

Bug#852306: marked as done (valgrind FTBFS on mips/mipsel: Error: float register should be even, was 1)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 21:10:56 + with message-id and subject line Bug#852306: fixed in valgrind 1:3.12.0-1.1 has caused the Debian Bug report #852306, regarding valgrind FTBFS on mips/mipsel: Error: float register should be even, was 1 to be marked as done. This means that you

Bug#853108: marked as done (chromium: fails to build on armhf)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 21:07:15 + with message-id and subject line Bug#853108: fixed in chromium-browser 56.0.2924.76-2 has caused the Debian Bug report #853108, regarding chromium: fails to build on armhf to be marked as done. This means that you claim that the problem has been

Bug#851909: Problems disappear after downgrade

2017-02-02 Thread Roger Kalt
Yes, I can confirm I was able to reproduce and it was the patch which was not correctly backported for deb8u1. Please test the UNRELEASED deb8u2 version available from here and give feedback: https.//www.helferplan.ch/debian/ Kind regards Roger On 02/02/2017 02:22 PM, Christopher Huhn wrote: >

Processed: your mail

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 851909 + confirmed pending Bug #851909 [elog] elog: most recent elog update included with Debian 8.7 no longer allows login (except for Admin) Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you n

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

2017-02-02 Thread Mathieu Parent
2017-02-02 20:36 GMT+01:00 Michael Meskes : >> Sorry, my patch was wrong >> >> local _, unix = pcall(require, "socket.unix"); >> if unix then >>socket.unix = unix.stream or unix.tcp; >> end >> > > This one seems to work. Great, thank you so much. > >> Unfortunately I can't reall

Bug#797161: should libprelude be removed from stretch?

2017-02-02 Thread Helmut Grohne
I looked into the current libprelude rc bugs and in the end, I give up. Yet, let me summarize my findings. I looked at symbol differences between jessie's libprelude2 and stretch's. Indeed, the C++ library breaks ABI and would need an soname bump if we had reverse dependencies to consider. Thus th

Bug#839409: marked as done (gnustep-base: FTBFS: Test failures)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 19:48:57 + with message-id and subject line Bug#839409: fixed in gnustep-base 1.24.9-3.1 has caused the Debian Bug report #839409, regarding gnustep-base: FTBFS: Test failures to be marked as done. This means that you claim that the problem has been dealt w

Bug#853979: marked as done (lambdabot FTBFS in sid)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Fri, 3 Feb 2017 00:35:22 +0500 with message-id <20170202193522.7icb2foj63k6u...@belkar.wrar.name> and subject line closing has caused the Debian Bug report #853979, regarding lambdabot FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt w

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

2017-02-02 Thread Michael Meskes
> Sorry, my patch was wrong > > local _, unix = pcall(require, "socket.unix"); > if unix then >    socket.unix = unix.stream or unix.tcp; > end > This one seems to work. Great, thank you so much.    > Unfortunately I can't really test the patches I propose, so I beg > your > pard

Bug#853978: marked as done (haskell-lambdabot-haskell-plugins FTBFS)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Fri, 3 Feb 2017 00:35:22 +0500 with message-id <20170202193522.7icb2foj63k6u...@belkar.wrar.name> and subject line closing has caused the Debian Bug report #853978, regarding haskell-lambdabot-haskell-plugins FTBFS to be marked as done. This means that you claim that the problem

Bug#853980: marked as done (haskell-lambdabot-haskell-plugins FTBFS)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Fri, 3 Feb 2017 00:35:22 +0500 with message-id <20170202193522.7icb2foj63k6u...@belkar.wrar.name> and subject line closing has caused the Debian Bug report #853980, regarding haskell-lambdabot-haskell-plugins FTBFS to be marked as done. This means that you claim that the problem

Bug#853977: marked as done (lambdabot FTBFS in sid)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Fri, 3 Feb 2017 00:35:22 +0500 with message-id <20170202193522.7icb2foj63k6u...@belkar.wrar.name> and subject line closing has caused the Debian Bug report #853977, regarding lambdabot FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt w

Processed: gnustep-base: diff for NMU version 1.24.9-3.1

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > tags 839409 + patch Bug #839409 [src:gnustep-base] gnustep-base: FTBFS: Test failures Added tag(s) patch. -- 839409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed (with 1 error): forcibly merging 842740 853977 853978 853979 853980

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 842740 853977 853978 853979 853980 Bug #842740 [libghc-lambdabot-haskell-plugins-dev] libghc-lambdabot-haskell-plugins-dev: insane memory usage during profiling build Bug #844810 [libghc-lambdabot-haskell-plugins-dev] lambdabot: FTBFS:

Bug#839409: gnustep-base: diff for NMU version 1.24.9-3.1

2017-02-02 Thread Andrey Rahmatullin
Control: tags 839409 + patch Dear maintainer, I've prepared an NMU for gnustep-base (versioned as 1.24.9-3.1). The diff is attached to this message. Regards. -- WBR, wRAR diff -Nru gnustep-base-1.24.9/debian/changelog gnustep-base-1.24.9/debian/changelog --- gnustep-base-1.24.9/debian/changelo

Processed: found 853980 in 5.1-2

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 853980 5.1-2 Bug #853980 [src:haskell-lambdabot-haskell-plugins] haskell-lambdabot-haskell-plugins FTBFS Marked as found in versions haskell-lambdabot-haskell-plugins/5.1-2. > thanks Stopping processing here. Please contact me if you need

Bug#850286: lambdabot FTBFS in stretch

2017-02-02 Thread Andrey Rahmatullin
Control: clone -1 -2 -3 Control: retitle -2 lambdabot FTBFS in sid Control: notfound -2 lambdabot/5.0.3-4 Control: found -2 lambdabot/5.1-2 Control: reassign -3 src:haskell-lambdabot-haskell-plugins Control: retitle -3 haskell-lambdabot-haskell-plugins FTBFS Control: block -2 by -3 On Thu, Jan 05,

Processed: Re: Bug#850286: lambdabot FTBFS in stretch

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 -3 Bug #850286 [lambdabot] lambdabot FTBFS in stretch: missing build-dependencies Bug 850286 cloned as bugs 853979-853980 > retitle -2 lambdabot FTBFS in sid Bug #853979 [lambdabot] lambdabot FTBFS in stretch: missing build-dependencies Changed Bug title

Processed: Re: Bug#850286: lambdabot FTBFS in stretch

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 -3 Bug #850286 [lambdabot] lambdabot FTBFS in stretch: missing build-dependencies Bug 850286 cloned as bugs 853977-853978 > retitle -2 lambdabot FTBFS in sid Bug #853977 [lambdabot] lambdabot FTBFS in stretch: missing build-dependencies Changed Bug title

Processed: Problem is also in the version in stretch

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 853931 3.2-2 Bug #853931 [src:suricata] FTBFS: dh_install: debian/suricata-hyperscan.install returned exit code 127 Marked as found in versions suricata/3.2-2. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#853966: remmina crashes with segfault on startup

2017-02-02 Thread Andreas Henriksson
Hello Jonathan Carter, On Thu, Feb 02, 2017 at 04:59:39PM +0200, Jonathan Carter wrote: > Package: remmina > Version: 1.1.2-4 > Severity: serious > > > Remmina crashes on startup, it does the same on a few different stretch > machines: [...] > Segmentation fault remmina starts without crashing

Bug#853937: [package:tex-common] dist-upgrade fails on ann error of updmap-sys, teaving tex-common unconfigured

2017-02-02 Thread Adrian Bunk
Control: reasign -1 tex-common 6.06 Move to the package. On Thu, Feb 02, 2017 at 10:47:51AM +, CHARPENTIER Emmanuel wrote: > Package: package:tex-common > Version: 6.06 > Severity: grave > > --- Please enter the report below this line. --- > > During a routine dist-upgrade, tex-common faile

Processed: Bug is also in the version in stretch

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 852924 5.7.0-3 Bug #852924 [collectd] Uses "-lssl -lcrypto" but does not depend on libssl Marked as found in versions collectd/5.7.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 852924: http://bugs.deb

Bug#853207: bluez: bluetooth.service doesn't start with systemd

2017-02-02 Thread Matthias Liertzer
Most likely the bluetooth support for your laptop is broken under linux. The bluetooth.service file contains ConditionPathIsDirectory=/sys/class/bluetooth which means that systemd only tries to start the bluetooth daemon when the bluetooth module from the kernel is loaded which creates the above

Bug#839444: libgda5: FTBFS: tests failures annotations:

2017-02-02 Thread Emilio Pozuelo Monfort
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=778094 On 12/12/16 22:37, Santiago Vila wrote: > On Mon, Dec 12, 2016 at 10:32:30PM +0100, Emilio Pozuelo Monfort wrote: > >> I need the full log. Run valgrind like this: >> >> valgrind --tool=memcheck --leak-check=full --leak-resol

Processed: Re: Bug#839444: libgda5: FTBFS: tests failures annotations:

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=778094 Bug #839444 [src:libgda5] libgda5: FTBFS sometimes (check_data_proxy fails) Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=778094'. -- 839444: http://bugs.debian.org/cgi-bi

Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

2017-02-02 Thread Vincent Bernat
Control: tags -1 + patch ❦ 2 février 2017 10:50 +0200, Lauri Niskanen  : > I can reproduce this bug with awesomewm on Arch Linux. I get the same > error message as Vincent Bernat. > > As a workaround I changed my pinentry program to pinentry-gnome3. I am fixing with this patch. Only lightly te

Processed: Re: Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #851707 [pinentry-gtk2] pinentry-gtk-2 frequently fails to grab the keyboard under awesome Ignoring request to alter tags of bug #851707 to the same tags previously set -- 851707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851707 Debian B

Processed: Re: Bug#846782: gobject-introspection randomly hangs liferea build

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #846782 [gobject-introspection] gobject-introspection randomly hangs liferea build Severity set to 'important' from 'serious' -- 846782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846782 Debian Bug Tracking System Contact ow...@bugs

Processed: tagging 849836, tagging 849836

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Reset auto-removal counter - BTS does not seem to realize the fix reached > testing > tags 849836 + pending Bug #849836 {Done: Christoph Biedl } [zekr] zekr: Missing dependency on libwebkitgtk-1.0-0 Added tag(s) pending. > tags 849836 - pendin

Bug#846782: gobject-introspection randomly hangs liferea build

2017-02-02 Thread Emilio Pozuelo Monfort
Control: severity -1 important Hi Paul, First of all, sorry for the delay. On 11/12/16 21:11, Paul Gevers wrote: > Hi > > On 11-12-16 17:46, Emilio Pozuelo Monfort wrote: >> They should be available in stretch: > > I missed the part where it is in a separate archive. > >> emilio@tatooine:~$ a

Bug#811068: libgda5: Patch to disable the failing tests

2017-02-02 Thread Emilio Pozuelo Monfort
On 02/02/17 12:58, Santiago Vila wrote: > On Wed, 1 Feb 2017, Emilio Pozuelo Monfort wrote: > >> This bug was originally for a different problem: >> >> ERROR:gda-vprovider-data-model.c:1316:map_sqlite3_info_to_gda_filter: code >> should not be reached >> >> That was already fixed. > > Are you sur

Bug#853973: qemu: QEMU user mode emulation on PowerPC fails to run i386 executables.

2017-02-02 Thread Michael Tokarev
Control: severity -1 normal 02.02.2017 19:13, Steven Gawroriski wrote: > Package: qemu > Version: 1:2.8+dfsg-2 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > For QEMU user mode, attempting to run i386 executables on a PowerPC > host fails. > > Running e

Processed: Re: Bug#853973: qemu: QEMU user mode emulation on PowerPC fails to run i386 executables.

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #853973 [qemu] qemu: QEMU user mode emulation on PowerPC fails to run i386 executables. Severity set to 'normal' from 'critical' -- 853973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853973 Debian Bug Tracking System Contact ow...@bugs

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

2017-02-02 Thread Enrico Tassi
On Thu, Feb 02, 2017 at 10:08:48AM +0100, Michael Meskes wrote: > > Sorry, I'm a bit puzzled.  The only module with such error is > > sasl_dovecot that AFAICT is not part of the debian package. > > Correct, nobody ever claimed it was. > > > Anyway, I was wrong saying that the incriminated line is

Bug#853935: [pkg-gnupg-maint] Bug#853935: rephrase: No more works with gpg2 and causes one pinentry popup per guess

2017-02-02 Thread Werner Koch
On Thu, 2 Feb 2017 11:37, a...@debian.org said: > Trying to use it on Sid or Stretch causes one pinentry window popup per > guessed try (i.e. potentially thousands). And since pinentry usually I don't know rephase but according to the description it should not use gpg to test the passphrase. Th

Bug#853962: marked as done (vagrant-mutate: completely broken)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 16:33:33 + with message-id and subject line Bug#853962: fixed in vagrant-mutate 1.2.0-3 has caused the Debian Bug report #853962, regarding vagrant-mutate: completely broken to be marked as done. This means that you claim that the problem has been dealt wit

Bug#814978: Update bug 814978 to: found in gcc-6 and severity serious

2017-02-02 Thread Matthias Klose
On 27.01.2017 13:29, Svante Signell wrote: > Looking into the problems with the acats tests not being run reveals problems > with the ada-gcc-name.diff and ada-acats.diff patches. > Adding gcc-6 to the files in ada-gcc-name.diff makes the functions > Locate_Executable in gnatchop.adb and Program_Na

Processed: Re: Bug#853970: tex-common: Can't update conffile when apt update in stretch

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 853970 errors during update: updmap missing maps otf-@jaEmbed@.map etc Bug #853970 [tex-common] tex-common: Can't update conffile when apt update in stretch Changed Bug title to 'errors during update: updmap missing maps otf-@jaEmbed@.ma

Processed: block 853917 with 853921

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 853917 with 853921 Bug #853917 [src:debian-installer] debian-installer: missing glyphs for Korean / broken rendering 853917 was not blocked by any bugs. 853917 was not blocking any bugs. Added blocking bug(s) of 853917: 853921 > thanks Stop

Bug#852434: marked as done (cowbuilder: No longer accepts command later in arguments list)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 16:03:26 + with message-id and subject line Bug#852434: fixed in cowdancer 0.85 has caused the Debian Bug report #852434, regarding cowbuilder: No longer accepts command later in arguments list to be marked as done. This means that you claim that the proble

Processed: severity of 853755 is serious

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 853755 serious Bug #853755 [src:systemd] systemd-udevd.service fails to start on ppc64el Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 853755: http://bugs.debi

Bug#853951: marked as done (iio-sensor-proxy: configures dbus-daemon to be insecure)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 15:06:11 + with message-id and subject line Bug#853951: fixed in iio-sensor-proxy 2.0-4 has caused the Debian Bug report #853951, regarding iio-sensor-proxy: configures dbus-daemon to be insecure to be marked as done. This means that you claim that the prob

Bug#853966: remmina crashes with segfault on startup

2017-02-02 Thread Jonathan Carter
Package: remmina Version: 1.1.2-4 Severity: serious Remmina crashes on startup, it does the same on a few different stretch machines: ~ $ remmina Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina

Bug#853918: marked as done (syslinux-utils: Unable to build writable installation thumb drive)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 2 Feb 2017 15:48:40 +0100 with message-id <20170202144840.ga15...@mraw.org> and subject line Re: Bug#853918: syslinux-utils: Unable to build writable installation thumb drive has caused the Debian Bug report #853918, regarding syslinux-utils: Unable to build writable instal

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-02 Thread Steve McIntyre
On Thu, Feb 02, 2017 at 02:42:26PM +0100, Jens Reyer wrote: >On 02/02/2017 02:30 PM, Steve McIntyre wrote: >> Dropping the -nostdlib argument to the gcc call inside sonames2elf >> makes a difference - it'll add libc6 to the mix and force the output >> to match the system you're building for. You ma

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-02 Thread Steve McIntyre
Hi, On Thu, Feb 02, 2017 at 05:10:14AM +0100, Guillem Jover wrote: >On Wed, 2017-02-01 at 15:34:04 +, Steve McIntyre wrote: >> >> Please don't go down that route, the ABI flags are intended to save >> people from that. I'm curious what's going wrong with libgsm1 here >> such that we're not se

Bug#835334: tex-common: failed on other fonts today

2017-02-02 Thread Karsten Hilbert
On Thu, Feb 02, 2017 at 10:52:24PM +0900, Norbert Preining wrote: >> W: APT had planned for dpkg to do more than it reported back (20 vs 24). >> Affected packages: tex-common:i386 > > That is something of dpkg, I know, just wanted to point it out. > not related to anything in TeX L

Bug#835334: tex-common: failed on other fonts today

2017-02-02 Thread Norbert Preining
On Thu, 02 Feb 2017, Karsten Hilbert wrote: > Works for me but eventually gives a warning: Which warning? > [ Rootkit Hunter version 1.4.2 ] > File updated: searched for 178 files, found 151 > W: APT had planned for dpkg to do more than it reported back (20 vs 24). > Af

Bug#853962: vagrant-mutate: completely broken

2017-02-02 Thread Antonio Terceiro
Package: vagrant-mutate Version: 1.2.0-2 Severity: grave Justification: renders package unusable $ vagrant mutate ubuntu/trusty64 libvirt /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:184:in `rescue in load_yml': can not load translations from /usr/lib/ruby/locales/en.yml: # (I18n::InvalidLocal

Bug#844779: osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope

2017-02-02 Thread Gianfranco Costamagna
control: severity -1 important Lowering the severity since the arm* binaries have been removed in sid. (sigh) G. signature.asc Description: OpenPGP digital signature

Bug#853926: Retitle cloud-init net-base -> net-tools

2017-02-02 Thread Thomas Goirand
There's no such package as net-base. Did you mean net-tools? Cheers, Thomas Goirand (zigo)

Bug#831245: marked as done (gts: FTBFS: Tests failures)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 13:48:48 + with message-id and subject line Bug#831245: fixed in gts 0.7.6+darcs121130-3 has caused the Debian Bug report #831245, regarding gts: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #844779 [src:osmose-emulator] osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope Severity set to 'important' from 'serious' -- 844779: http://bugs.debian.org/cgi-bin/bugre

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-02 Thread Jens Reyer
On 02/02/2017 02:30 PM, Steve McIntyre wrote: > Dropping the -nostdlib argument to the gcc call inside sonames2elf > makes a difference - it'll add libc6 to the mix and force the output > to match the system you're building for. You may then need to filter > out the libc6 entry afterwards, but that

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-02 Thread Steve McIntyre
On Wed, Feb 01, 2017 at 05:03:13PM +0100, Jens Reyer wrote: >On 02/01/2017 04:34 PM, Steve McIntyre wrote: >> >> Please don't go down that route, the ABI flags are intended to save >> people from that. I'm curious what's going wrong with libgsm1 here >> such that we're not seeing consistent ABI fl

Bug#853948: Bug#835334: tex-common: failed on other fonts today

2017-02-02 Thread Norbert Preining
severity 835334 serious severity 853946 serious severity 853948 serious severity 853939 serious reassign 835334 texlive-lang-japanese reassign 853946 texlive-lang-japanese reassign 853948 texlive-lang-japanese reassign 853939 texlive-lang-japanese severity 852611 serious merge 852611 835334 853946

Bug#853951: iio-sensor-proxy: configures dbus-daemon to be insecure

2017-02-02 Thread Simon McVittie
Control: tags -1 + patch upstream On Thu, 02 Feb 2017 at 12:22:27 +, Simon McVittie wrote: > I'm assuming the intended policy was to put a > send_destination="net.hadess.SensorProxy" on everythng See attached - seems to work, but I have no IIO hardware. Here is a non-weaponized exploit. You

Processed: Re: Bug#853951: iio-sensor-proxy: configures dbus-daemon to be insecure

2017-02-02 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch upstream Bug #853951 [iio-sensor-proxy] iio-sensor-proxy: configures dbus-daemon to be insecure Added tag(s) patch and upstream. -- 853951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853951 Debian Bug Tracking System Contact ow...@bugs.debian

Processed: Re: Bug#835334: tex-common: failed on other fonts today

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 835334 serious Bug #835334 [tex-common] tex-common: dist-upgrade failed (updmap-sys: CormorantGaramond.map not found) Bug #853939 [tex-common] upgrade failed Severity set to 'serious' from 'minor' Severity set to 'serious' from 'minor' >

Bug#853926: cloud-init depends on net-base

2017-02-02 Thread Thomas Goirand
On 02/02/2017 10:40 AM, Adam Bolte wrote: > I'm also confirming this issue exists in the jessie-backports package > version 0.7.7~bzr1156-1~bpo8+1. It's not fatal (networking still > works), but certainly something I noticed when creating new EC2 AMIs. > > -Adam I don't see how Jessie would be af

Bug#851909: Problems disappear after downgrade

2017-02-02 Thread Christopher Huhn
OK, after downgrading to 2.9.2+2014.05.11git44800a7-2 elog starts to work again. So this is definitely a regression. Kind regards, Christopher

Processed: bug 853951 is forwarded to https://github.com/hadess/iio-sensor-proxy/issues/41

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 853951 https://github.com/hadess/iio-sensor-proxy/issues/41 Bug #853951 [iio-sensor-proxy] iio-sensor-proxy: configures dbus-daemon to be insecure Set Bug forwarded-to-address to 'https://github.com/hadess/iio-sensor-proxy/issues/41'.

Bug#853907: marked as done (openstack-debian-images: FTBFS when built with dpkg-buildpackage -B)

2017-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 02 Feb 2017 13:03:28 + with message-id and subject line Bug#853907: fixed in openstack-debian-images 1.16 has caused the Debian Bug report #853907, regarding openstack-debian-images: FTBFS when built with dpkg-buildpackage -B to be marked as done. This means that you c

Bug#853907: marked as pending

2017-02-02 Thread Thomas Goirand
tag 853907 pending thanks Hello, Bug #853907 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: http://git.debian.org/?p=openstack/openstack-debian-images.git;a=commitdiff;h=712b4bb --- commit 712b4bbf7e5b0ac7349

Processed: Bug#853907 marked as pending

2017-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 853907 pending Bug #853907 [src:openstack-debian-images] openstack-debian-images: FTBFS when built with dpkg-buildpackage -B Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 853907: http:

  1   2   >