Processed: tagging 815907

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 815907 + pending
Bug #815907 [src:xerces-c] xerces-c: CVE-2016-0729
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
815907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 816021

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 816021 + pending
Bug #816021 [src:xerces-c] xerces-c: FTBFS: Exception in thread "main" 
java.awt.AWTError: Assistive Technology not found: 
org.GNOME.Accessibility.AtkWrapper
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#816063: emacs24: TLS certificate validation is silently broken

2016-02-26 Thread Nathaniel Smith
Package: emacs24
Version: 24.5+1-6+b1
Severity: serious
Tags: security
Justification: 5(b) of https://release.debian.org/testing/rc_policy.txt

Debian's emacs builds are linked against gnutls:

(gnutls-available-p)
t

By default, they aren't configured to validate TLS certificates,
leaving users open to trivial MITM attacks:

(require 'gnutls)
gnutls-verify-error
nil

(url-retrieve-synchronously "https://wrong.host.badssl.com;)
#
(url-retrieve-synchronously "https://self-signed.badssl.com;)
#

Okay, fine, but at least it is easy to turn this on:

(setq gnutls-verify-error t)

There are even some nice docs explaining how and why to do this:
   https://glyph.twistedmatrix.com/2015/11/editor-malware.html
(Short version: if you aren't using https for the package servers --
#797477 -- and haven't enabled TLS checking, and ever run
package-install over coffee-shop wifi, then congratulations, you've
just allowed anyone within wifi range to execute arbitrary code on
your user account.)

However, Debian's emacs24 somehow manages to be so broken that turning
on cert verification via (setq gnutls-verify-error t) *doesn't
work*. The docs say it should work, and explain in detail how to
configure finding the CA trust store (this is configured correctly
out-of-the-box on Debian). And sometimes I've even had it fail on
https://wrong.host.badssl.com after setting this (but not
always). However, it always happily loads
https://self-signed.badssl.com, which means it's providing no
protection at all against MITM attacks.

Bottom line: even if you configure everything correctly, Debian's
emacs will still happily execute whatever random code your barista
gives you.

The only way I've found to work around this and get a minimally-secure
setup is to add the following extremely simple and obvious incantation
to my .emacs:

;; Monkeypatch emacs so that it doesn't think gnutls is compiled in
(if (fboundp 'gnutls-available-p)
(fmakunbound 'gnutls-available-p))
;; Force emacs to use gnutls-cli *without* the --insecure flag it
;; defaults to. (Note that the --x509cafile argument here depends on
;; your distro; this is correct for Debian.)
(setq tls-program
  '("gnutls-cli --x509cafile /etc/ssl/certs/ca-certificates.crt -p %p %h"))
;; Not sure if this is necessary, but it certainly doesn't hurt
(setq tls-checktrust t)

and then doing 'apt install gnutls-bin'.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.5+1-6+b1
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-3
ii  libasound2 1.1.0-1
ii  libatk1.0-02.18.0-1
ii  libc6  2.21-9
ii  libcairo-gobject2  1.14.6-1
ii  libcairo2  1.14.6-1
ii  libdbus-1-31.10.6-1
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.1-0.1
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.32.3-1.2
ii  libgif75.1.2-0.2
ii  libglib2.0-0   2.46.2-3
ii  libgnutls303.4.9-2
ii  libgomp1   5.3.1-8
ii  libgpm21.20.4-6.1+b2
ii  libgtk-3-0 3.18.7-1
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.4.2-2
ii  libm17n-0  1.7.0-3
ii  libmagickcore-6.q16-2  8:6.8.9.9-7+b1
ii  libmagickwand-6.q16-2  8:6.8.9.9-7+b1
ii  libotf00.9.13-3
ii  libpango-1.0-0 1.38.1-1
ii  libpangocairo-1.0-01.38.1-1
ii  libpng12-0 1.2.54-3
ii  librsvg2-2 2.40.11-2
ii  libselinux12.4-3
ii  libsm6 2:1.2.2-1+b1
ii  libtiff5   4.0.6-1
ii  libtinfo5  6.0+20151024-2
ii  libx11-6   2:1.6.3-1
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.3+dfsg1-1
ii  libxpm41:3.5.11-1+b1
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.9-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
pn  emacs24-common-non-dfsg  

-- no debconf information



Processed: tagging 816026, found 816042 in 1:13.1.0~dfsg-1.1, notfound 815970 in 3.4.1-3 ...

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 816026 - moreinfo
Bug #816026 {Done: dererk } [src:fglrx-driver] 
[fglrx-source] Fails to build against linux 4.3
Removed tag(s) moreinfo.
> found 816042 1:13.1.0~dfsg-1.1
Bug #816042 [src:asterisk] Don't include in stretch
Marked as found in versions asterisk/1:13.1.0~dfsg-1.1.
> notfound 815970 3.4.1-3
Bug #815970 [libtesseract3] libtesseract4 and libtesseract3: error when trying 
to install together
There is no source info for the package 'libtesseract3' at version '3.4.1-3' 
with architecture ''
Unable to make a source version for version '3.4.1-3'
No longer marked as found in versions 3.4.1-3.
> found 815970 3.04.01-3
Bug #815970 [libtesseract3] libtesseract4 and libtesseract3: error when trying 
to install together
Marked as found in versions tesseract/3.04.01-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
815970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815970
816026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816026
816042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: NFS mounts from /etc/fstab can fail w/out network-manager

2016-02-26 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 NFS mounts from /etc/fstab can fail w/out network-manager
Bug #775541 [nfs-common] NFS mounts from /etc/fstab do not work
Changed Bug title to 'NFS mounts from /etc/fstab can fail w/out 
network-manager' from 'NFS mounts from /etc/fstab do not work'

-- 
775541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: severity of 815942 is normal, tagging 815942

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #will only FTBFS after changing build-dependency to libzmq5-dev
> severity 815942 normal
Bug #815942 [src:jzmq] jzmq: FTBFS: missing header inclusion
Severity set to 'normal' from 'serious'
> tags 815942 + pending
Bug #815942 [src:jzmq] jzmq: FTBFS: missing header inclusion
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
815942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#813819: marked as done (please switch build-dep from libopenobex1-dev to libopenobex2-dev)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 27 Feb 2016 00:26:59 +
with message-id 
and subject line Bug#813819: fixed in syncevolution 1.4.99.4-5
has caused the Debian Bug report #813819,
regarding please switch build-dep from libopenobex1-dev to libopenobex2-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: syncevolution
Version: 1.4.99.4-4+b1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

the current package does not work:
syncevolution: error while loading shared libraries: libopenobex.so.1: cannot 
open shared object file: No such file or directory

There is now libopenobex2-dev, see http://bugs.debian.org/810556.

Greetings,
Joachim



- -- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages syncevolution depends on:
ii  libc6 2.21-7
ii  libgcc1   1:5.3.1-7
ii  libgdbussyncevo0  1.4.99.4-4+b1
ii  libglib2.0-0  2.46.2-3
ii  libstdc++65.3.1-7
ii  libsyncevolution0 1.4.99.4-4+b1
ii  syncevolution-common  1.4.99.4-4
ii  syncevolution-libs1.4.99.4-4+b1

Versions of packages syncevolution recommends:
ii  bluez  5.36-1

syncevolution suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAla0uIUACgkQ9ijrk0dDIGwuLgCgv4YczkGlv85hRDeik7mM8I96
/RAAnA/19l05pStYRyi49Fgscs8RbInS
=X5VI
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: syncevolution
Source-Version: 1.4.99.4-5

We believe that the bug you reported is fixed in the latest version of
syncevolution, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tino Mettler  (supplier of updated syncevolution package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 11:57:35 +0100
Source: syncevolution
Binary: syncevolution sync-ui syncevolution-common syncevolution-libs 
syncevolution-libs-gnome syncevolution-libs-kde syncevolution-dbus 
syncevolution-http syncevolution-dbg libsyncevolution0 libsyncevo-dbus0 
libgdbussyncevo0
Architecture: source amd64 all
Version: 1.4.99.4-5
Distribution: unstable
Urgency: medium
Maintainer: Tino Mettler 
Changed-By: Tino Mettler 
Description:
 libgdbussyncevo0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 libsyncevo-dbus0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 libsyncevolution0 - Sync personal information data using SyncML and 
CalDAV/CardDAV (s
 sync-ui- Sync personal information data using SyncML and CalDAV/CardDAV (G
 syncevolution - Sync personal information data using SyncML and CalDAV/CardDAV 
(C
 syncevolution-common - Sync personal information data using SyncML and 
CalDAV/CardDAV
 syncevolution-dbg - Sync personal information data using SyncML and 
CalDAV/CardDAV (d
 syncevolution-dbus - Sync personal information data using SyncML and 
CalDAV/CardDAV (D
 syncevolution-http - Sync personal information data using SyncML and 
CalDAV/CardDAV (H
 syncevolution-libs - Sync personal information data using SyncML and 
CalDAV/CardDAV (l
 syncevolution-libs-gnome - Sync personal information data using SyncML and 
CalDAV/CardDAV (l
 syncevolution-libs-kde - Sync personal information data using SyncML and 
CalDAV/CardDAV (l
Closes: 813819
Changes:
 syncevolution (1.4.99.4-5) unstable; urgency=medium
 .
   * Build-depend on libopenobex2-dev (Closes: #813819)
Checksums-Sha1:
 d11ac478eac330b3a6f43e38cbf6c21305fad6b2 3082 syncevolution_1.4.99.4-5.dsc
 

Processed: severity of 678512 is grave

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 678512 grave
Bug #678512 [ruby-eventmachine] ruby-eventmachine: crashes when using IPv6 
socket
Bug #696015 [ruby-eventmachine] segfaults with IPv6
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
678512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678512
696015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#815070: marked as done (postfix: does not start)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 22:56:25 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-4
has caused the Debian Bug report #815047,
regarding postfix: does not start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.0.3-1
Severity: grave
Justification: renders package unusable

After a dist-upgrade:

tglase@tglase-nb:~ $ fgrep postmulti /var/log/syslog.1
Feb 18 09:10:42 tglase-nb postmulti[7295]: fatal: instance /etc/postfix, 
shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix, 
daemon_directory=/usr/lib/postfix
tglase@tglase-nb:~ $ sudo /etc/init.d/postfix stop
Stopping Postfix Mail Transport Agent: postfixpostmulti: fatal: instance 
/etc/postfix, shlib_directory=/usr/lib/postfix conflicts with instance 
/etc/postfix, daemon_directory=/usr/lib/postfix
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-4

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 22:15:25 +
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-4
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: LaMont Jones 
Closes: 815047 815985 816018
Description: 
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-dev - Loadable modules development environment for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
Changes:
 postfix (3.0.4-4) unstable; urgency=medium
 .
   [LaMont Jones]
 .
   * If main.cf has daemon_directory = /usr/lib/postfix, then fix it or abort
 the install.  Closes: #815047
 .
   [localization folks]
 .
   * l10n: New Brazilian Portuguese debconf translations.  Closes: #815985
 (Marcelo Santana)
   * l10n: Updated Frence debconf templates.  Closes: #816018 (Christian
 Perrier)
Checksums-Sha1: 
 2ac097c9d01d3d5306f6b52aef12166e255c69f4 2441 postfix_3.0.4-4.dsc
 df8c2d3bc5bc933306d596790496dc641ed2faf1 177716 postfix_3.0.4-4.debian.tar.xz
 b8f3ed468489548ea521e8a48c2be61bf86ce196 2398 
postfix-cdb-dbgsym_3.0.4-4_amd64.deb
 027f9f4c0cd57a23e6fde3e7a8b4bba83457a247 301258 postfix-cdb_3.0.4-4_amd64.deb
 bf9c5ad12b84dd058cd50269b3070006904baa43 97454 postfix-dbgsym_3.0.4-4_amd64.deb
 89d0978fc4bdf8b4c02dd424daa5ce55dd5689fc 404910 postfix-dev_3.0.4-4_all.deb
 a4e669cd0d1830f1f0a195ef1bb7654ad853bf4b 1144058 postfix-doc_3.0.4-4_all.deb
 5194b59ed3ae4bf6a415c551e493f4df4fa97f2d 3106 
postfix-ldap-dbgsym_3.0.4-4_amd64.deb
 c486e60d9abcd3ca1b9abae1b596d46826d57319 308956 postfix-ldap_3.0.4-4_amd64.deb
 e768e042860a6b341f5d4cc0a14b711868081d59 2648 
postfix-mysql-dbgsym_3.0.4-4_amd64.deb
 5c3abce6f089d7c80fc8733fc95af02687c4fbaa 303006 postfix-mysql_3.0.4-4_amd64.deb
 efd076ac1e60121a2b0f36fe1e53ba413371174f 2474 
postfix-pcre-dbgsym_3.0.4-4_amd64.deb
 e7c27c663dfb98c0c4b3af37d2c16d31bd9942aa 303212 postfix-pcre_3.0.4-4_amd64.deb
 e27d61b1255fc184a4187ebd8ed333ff59a62157 2618 
postfix-pgsql-dbgsym_3.0.4-4_amd64.deb
 0164cedaba029558c46cace4ed3eb46f39eace5f 302814 postfix-pgsql_3.0.4-4_amd64.deb
 f038887be37d74f0e9106d2bfa8883f37380257d 1410192 postfix_3.0.4-4_amd64.deb
Checksums-Sha256: 
 2a56d19590eb5fba0e23c7060aec8a59bf15fbd7196a0d04ed6038c397908664 2441 
postfix_3.0.4-4.dsc
 3d3ad8af18280834d8721c0f6366480216e57c73d90b20698b6805fe172c37d5 177716 
postfix_3.0.4-4.debian.tar.xz
 

Bug#815047: marked as done (postfix: Postfix fails to start after upgrade)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 22:56:25 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-4
has caused the Debian Bug report #815047,
regarding postfix: Postfix fails to start after upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.0.3-1
Severity: important

Dear Maintainer,


After this morning's upgrade of Postfix from 2.11.3-1+b1 to 3.0.3-1, postfix 
refuses to start saying:

fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix conflicts with 
instance /etc/postfix, daemon_directory=/usr/lib/postfix

It seems from email threads on the archives that haveing shlib_directory and 
daemon_directory refer to the
same directory is now considered unacceptable. I have not set these variables 
explicitly in /etc/postfix/main.cf or/etc/postfix/
master.cf.

postconf -d indicates daemon_directory is set to /usr/lib/postfix from 
somewhere.


Copying /usr/lib/postfix to /usr/libexec/postifx and setting:

daemon_directory = /usr/libexec/postfix

in /etc/postfix/main.cf

allows the postfix server to run.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libicu55   55.1-7
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-1
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python3  3.5.1-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]8.1.2-0.20160123cvs-2
ii  dovecot-core [dovecot-common]  1:2.2.18-2+b1
ii  emacs24 [mail-reader]  24.5+1-6+b1
ii  libsasl2-modules   2.1.26.dfsg1-14+b1
ii  mutt [mail-reader] 1.5.24-1+b1
pn  postfix-cdb
pn  postfix-doc
pn  postfix-ldap   
pn  postfix-mysql  
pn  postfix-pcre   
pn  postfix-pgsql  
ii  procmail   3.22-25
pn  resolvconf 
ii  sasl2-bin  2.1.26.dfsg1-14+b1
pn  ufw

-- debconf information:
  postfix/destinations:
  postfix/mydomain_warning:
  postfix/procmail:
* postfix/main_mailer_type: No configuration
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/sqlite_warning:
  postfix/mailname: /etc/mailname
  postfix/mailbox_limit: 0
  postfix/relay_restrictions_warning:
  postfix/relayhost:
  postfix/retry_upgrade_warning:
  postfix/root_address:
  postfix/recipient_delim: +
  postfix/kernel_version_warning:
  postfix/tlsmgr_upgrade_warning:
  postfix/bad_recipient_delimiter:
  postfix/protocols:
  postfix/chattr: false
  postfix/not_configured:
  postfix/rfc1035_violation: false
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-4

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 22:15:25 +
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-4
Distribution: unstable

Bug#815538: marked as done (postfix: Does not start after upgrading to 3.0.3-1 - instance conflicts)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 22:56:25 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-4
has caused the Debian Bug report #815047,
regarding postfix: Does not start after upgrading to 3.0.3-1 - instance 
conflicts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.0.3-1
Severity: important

After upgrading to 3.0.3 postfix fails to start with the following
error:

Starting Postfix Mail Transport Agent: postfixpostmulti: fatal: instance
/etc/postfix, shlib_directory=/usr/lib/postfix conflicts with instance
/etc/postfix, daemon_directory=/usr/lib/postfix

Downgrading to 2.11.3-1+b1 fixes this issue (and the reportbug tool
generated its information from that version; I've manually corrected
the above Version: header).


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-1
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python  2.7.11-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20160123cvs-2
pn  dovecot-common   
ii  icedove [mail-reader]38.6.0-1
ii  libsasl2-modules 2.1.26.dfsg1-14+b1
ii  mailutils [mail-reader]  1:2.99.99-1
ii  mutt [mail-reader]   1.5.24-1+b1
pn  postfix-cdb  
ii  postfix-doc  3.0.3-1
pn  postfix-ldap 
pn  postfix-mysql
pn  postfix-pcre 
pn  postfix-pgsql
ii  procmail 3.22-25
ii  resolvconf   1.78
ii  s-nail [mail-reader] 14.8.6-1
pn  sasl2-bin
pn  ufw  

-- debconf information:
[ Note: I've manually stripped some information in the following
lines, even though I'm pretty sure this does not hide anything]
  postfix/rfc1035_violation: false
* postfix/sqlite_warning: true
* postfix/procmail: true
  postfix/master_upgrade_warning:
* postfix/protocols: ipv4
  postfix/transport_map_warning:
  postfix/bad_recipient_delimiter:
* postfix/chattr: true
* postfix/mynetworks: 127.0.0.0/8, 192.[stripped]
  postfix/nqmgr_upgrade_warning:
* postfix/mailbox_limit: 0
* postfix/root_address: robert
  postfix/not_configured:
* postfix/mydomain_warning: true
* postfix/retry_upgrade_warning: true
  postfix/tlsmgr_upgrade_warning:
  postfix/dynamicmaps_upgrade_warning:
* postfix/destinations: vox.[stripped], localhost.[stripped], localhost, vox
* postfix/recipient_delim: +
  postfix/relay_restrictions_warning:
* postfix/mailname: vox.[stripped]
  postfix/db_upgrade_warning: true
  postfix/kernel_version_warning:
* postfix/relayhost:
* postfix/main_mailer_type: Internet with smarthost
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-4

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 22:15:25 +
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-4

Bug#815622: marked as done (Postfix fails to start after apt-get upgrade)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 22:56:25 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-4
has caused the Debian Bug report #815047,
regarding Postfix fails to start after apt-get upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.0.3-1
Severity: important

After running apt-get upgrade, postfix fails to start due to this:

postmulti: fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix 
conflicts with instance /etc/postfix, daemon_directory=/usr/lib/postfix

Neither shlib_directory nor daemon_directory are mentioned in my /etc/postfix,
and I had not been using multi at all on this box.

If the new init script cannot handle having shlib_directory and daemon_directory
be identical, the defaults should not have them identical.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libicu55   55.1-7
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-1
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python3  3.5.1-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]8.1.2-0.20160123cvs-2
pn  dovecot-common 
ii  emacs24-nox [mail-reader]  24.5+1-6+b1
ii  libsasl2-modules   2.1.26.dfsg1-14+b1
ii  mutt [mail-reader] 1.5.24-1+b1
ii  postfix-cdb3.0.3-1
ii  postfix-doc3.0.3-1
pn  postfix-ldap   
pn  postfix-mysql  
ii  postfix-pcre   3.0.3-1
ii  postfix-pgsql  3.0.3-1
ii  procmail   3.22-25
pn  resolvconf 
ii  s-nail [mail-reader]   14.8.6-1
pn  sasl2-bin  
pn  ufw

-- debconf information:
  postfix/sqlite_warning:
  postfix/protocols: all
  postfix/relayhost:
  postfix/procmail: true
  postfix/mynetworks: 127.0.0.0/8 [::1]/128
  postfix/root_address:
  postfix/tlsmgr_upgrade_warning:
  postfix/mailbox_limit: 0
  postfix/recipient_delim: +
* postfix/main_mailer_type: Internet Site
  postfix/mydomain_warning:
  postfix/bad_recipient_delimiter:
  postfix/destinations: globe.jhcloos.com, localhost.jhcloos.com, localhost
  postfix/not_configured:
  postfix/kernel_version_warning:
  postfix/retry_upgrade_warning:
* postfix/mailname: globe.jhcloos.com
  postfix/rfc1035_violation: false
  postfix/chattr: false
  postfix/relay_restrictions_warning:
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-4

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 22:15:25 +
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-4
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: LaMont Jones 
Closes: 815047 815985 816018
Description: 
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 

Bug#815996: marked as done (elastix: diff for NMU version 4.8-3.1)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 22:44:32 +
with message-id 
and subject line Bug#815996: fixed in elastix 4.8-3.1
has caused the Debian Bug report #815996,
regarding elastix: diff for NMU version 4.8-3.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elastix
Version: 4.8-3
Severity: serious
Justification: FTBFS


Dear maintainer,

the elastix package doesn't build anymore against the new ITK4.9.
I did cherry-pick the patch from upstream and the build was successful.

build error:
https://launchpadlibrarian.net/243044486/buildlog_ubuntu-xenial-amd64.elastix_4.8-3build1_BUILDING.txt.gz
the patch is really simple, you can see it below, or just drag it from there
http://launchpadlibrarian.net/243063499/elastix_4.8-3build1_4.8-3ubuntu1.diff.gz

upstream commits:
r5140 | kmarstal | 2015-11-16 09:38:55 + (Mon, 16 Nov 2015) | 1 line

r5139 | dpshamonin | 2015-11-13 12:42:05 + (Fri, 13 Nov 2015) | 1 line


I'm uploading it to deferred/15 and attaching the debdiff to this email.
(I'll close this bug in changelog)


debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: elastix
Source-Version: 4.8-3.1

We believe that the bug you reported is fixed in the latest version of
elastix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated elastix 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 12:54:10 +0100
Source: elastix
Binary: elastix elastix-doc
Architecture: source
Version: 4.8-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gianfranco Costamagna 
Description:
 elastix- toolbox for rigid and nonrigid registration of images
 elastix-doc - toolbox for rigid and nonrigid registration of images - docs
Closes: 815996
Changes:
 elastix (4.8-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/fix-cast-error.patch:
 fix FTBFS with insighttoolkit4.9 (Closes: #815996).
Checksums-Sha1:
 14ec34305c33f70bcfbd62cad1df61e17ce309c7 2326 elastix_4.8-3.1.dsc
 8a17233ac4600e911a33587a403a3d9024de6914 16841027 elastix_4.8.orig.tar.bz2
 13a09aec13a59d179089feccb621a9f1d5daa772 10348 elastix_4.8-3.1.debian.tar.xz
Checksums-Sha256:
 d0842b0bd65456f96298042481a2a7793c0c947d14be900187bc1dec293d7c43 2326 
elastix_4.8-3.1.dsc
 9ec2bec426e8a249150fdf5af3a69037355ccb7b2c2d937bbfb7f0c563b6e81d 16841027 
elastix_4.8.orig.tar.bz2
 d649e6d4f38f20050c89867957a0cc5037d2d91738457bc5b1281bdf248d7a94 10348 
elastix_4.8-3.1.debian.tar.xz
Files:
 591dd2a5ae8cfd0ad48f1761b6a7c015 2326 science optional elastix_4.8-3.1.dsc
 2bd1cfe9017a6d4d062769fcef32e814 16841027 science optional 
elastix_4.8.orig.tar.bz2
 199d10926a9fd1f356dda52c4f7f296b 10348 science optional 
elastix_4.8-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW0FdRAAoJEPNPCXROn13ZS/AP/jkxp/brqi/3Apvm0qIIe9rB
IYlXFnLP3c0ZsNMOzlfSnfeMqHwVQf0dNl37nOd9mrJs2284MVacQoHf1bS8MToC
2R8U29Z0+VgaBjpXByQDRGWV7peEZ1vLuC3PJPVWnRqVwEvCHqufpeBegNcA9M5+
mi48TFJR0hveqRMK+QfElsL15il3RHIjYxgDX4IAXHu7sEcICprkNqZMZQGOmxMp
/sdDa8WlKL6WkSqnqb4krHE9Sdvc09VF70gEN866R8NchfMkCCveotmM4yeWV6dv
5UzhsaBDokVgsKlqDKRT14bWFjNL/ks2zV4VDyOibvmG5CxHypFGRu/0cvpKirti
IwaHtg64s9V+GIvCGxWLfFr1PadN/OBXVw3zz2UDTx1HBL8p6Y4mDwhbpUA+XR0c
NpL6XN9Lcs8kF9Yr3rf+MBEs2UG13yIDhxUXyV2ApYvuoxJLYHnGKQKLREmDE5ye
EK/x7WNOYbNxrOgM8CEqci78dN8T/AS4N7XsEZ+Z0MPwyLJc/+YWdD7kErhzQULe
GAVdQCWSvu750FZpmGYNQ8JdVbFsnbNHZrLTs44gm/J2AAYj0/fRv25El3BBK9xG
g+qRcj0ef2k140Sy0MuGfLRSgwrz4rso0ljpqmbbuMjr3o7c5/vBhy6S/jU5u7g3
e5sAMQdgswsgNQFp/Qju
=iHd5
-END PGP SIGNATURE End Message ---


Bug#816050: evolution: Crash on launch in e_mail_display_init (camel-data-cache.c:248)

2016-02-26 Thread Sam Morris
Package: evolution
Version: 3.18.5-1
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Since upgrading to 3.18.5-1 evolution segfaults when launched.
3.18.3-1 worked fine.

I also have problems with gnome-contacts and gnome-calendar, which
no longer see my Google contacts & calendars. Perhaps the problems are
related. If not then I'll file separate bugs.

$ gdb evolution
Reading symbols from evolution...Reading symbols from 
/usr/lib/debug/.build-id/a5/c5009a661ad6d9a4f0c162c18e103124226bcc.debug...done.
done.

(gdb) r
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdb5bf700 (LWP 21643)]
[New Thread 0x7fffdadbe700 (LWP 21644)]
[New Thread 0x7fffd1ea1700 (LWP 21645)]
[New Thread 0x7fffd16a0700 (LWP 21646)]
[New Thread 0x7fffd0c67700 (LWP 21647)]
[New Thread 0x7fffc7fff700 (LWP 21648)]
[New Thread 0x7fffc6b27700 (LWP 21652)]
[New Thread 0x7fffc6224700 (LWP 21653)]
[Thread 0x7fffc6224700 (LWP 21653) exited]

** (evolution:21631): WARNING **: Failed to add service 's...@blinkbox.com' 
(1380489432.25892.2@wintermute): Permission denied

** (evolution:21631): WARNING **: Failed to add service 's...@robots.org.uk' 
(1380561889.26206.2@wintermute): Permission denied
[New Thread 0x7fff73ed5700 (LWP 21674)]
[New Thread 0x7fff736d4700 (LWP 21675)]
[New Thread 0x7fff72ed3700 (LWP 21695)]
[New Thread 0x7fff726d2700 (LWP 21696)]
[New Thread 0x7fff71ed1700 (LWP 21697)]
[New Thread 0x7fff716d0700 (LWP 21698)]
[New Thread 0x7fff70ecf700 (LWP 21699)]
[Thread 0x7fff72ed3700 (LWP 21695) exited]
[Thread 0x7fff70ecf700 (LWP 21699) exited]
[Thread 0x7fff716d0700 (LWP 21698) exited]
[Thread 0x7fff71ed1700 (LWP 21697) exited]
[Thread 0x7fff736d4700 (LWP 21675) exited]
[Thread 0x7fff726d2700 (LWP 21696) exited]

Program received signal SIGSEGV, Segmentation fault.
camel_data_cache_set_expire_age (cdc=0x0, when=when@entry=86400) at 
camel-data-cache.c:248
248 camel-data-cache.c: No such file or directory.

(gdb) where
#0  camel_data_cache_set_expire_age (cdc=0x0, when=when@entry=86400) at 
camel-data-cache.c:248
#1  0x7fffc5384493 in e_mail_display_init (display=0x58a5c410) at 
e-mail-display.c:2018
#2  0x73a2c329 in g_type_create_instance () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x73a0e2bb in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x73a10155 in g_object_new_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x73a104c1 in g_object_new () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7fffc538ee2b in mail_paned_view_constructed (object=0x57e92500) 
at e-mail-paned-view.c:681
#7  0x73a0e837 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x73a10155 in g_object_new_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x73a104c1 in g_object_new () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x7fffc538f2ec in e_mail_paned_view_new (shell_view=) at 
e-mail-paned-view.c:1110
#11 0x7fff76522b8d in mail_shell_content_constructed 
(object=0x7fff68012410) at e-mail-shell-content.c:198
#12 0x73a0e837 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x73a10155 in g_object_new_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x73a104c1 in g_object_new () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x77bc3f8f in shell_view_constructed (object=0x57fb77e0) at 
e-shell-view.c:617
#16 0x7fff7652586b in mail_shell_view_constructed (object=0x57fb77e0) 
at e-mail-shell-view.c:307
#17 0x73a0e837 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x73a10155 in g_object_new_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x73a104c1 in g_object_new () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x77bc68d4 in shell_window_create_shell_view 
(shell_window=0x589dc390, view_name=) at e-shell-window.c:774
#21 0x77bc6347 in e_shell_window_get_shell_view 
(shell_window=shell_window@entry=0x589dc390, 
view_name=view_name@entry=0x58003660 "mail") at e-shell-window.c:1228
#22 0x77bc71a8 in e_shell_window_set_active_view 
(shell_window=0x589dc390, view_name=0x58003660 "mail") at 
e-shell-window.c:1470
#23 0x77bc7b86 in shell_window_set_property (object=0x589dc390, 
property_id=, value=, pspec=) at 
e-shell-window.c:290
#24 0x73a1128b in g_object_set_property () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x73d0b053 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#26 0x73d0dbf0 in g_settings_bind_with_mapping () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#27 0x73d0de6a in g_settings_bind () from 

Bug#816042: Don't include in stretch

2016-02-26 Thread Moritz Muehlenhoff
Source: asterisk
Severity: serious

asterisk hasn't seen a maintainer upload to unstable in 2015. It's
already excluded from testing due to an unrelated FTBFS bug. This
bug is used to ensure that it doesn't enter stretch unless maintenance
(especially for the lifetime of stable) is properly ensured again.

Cheers,
Moritz



Bug#816041: ldap-account-manager depends on php5-imagick which is no longer built

2016-02-26 Thread peter green

Package: ldap-account-manager
Severity: serious
Version: 5.2-1

ldap-account-manager depends on php5-imagick which is no longer built by 
the source package php-imagick.


I'm not sure if you can just change the dependency to php-imagick or if 
more work is needed.




Bug#816040: fusiondirectory depends on php5-imagick which is no longer built

2016-02-26 Thread peter green

Package: fusiondirectory
Severity: serious
Version: 1.0.8.8-3

fusiondirectory depends on php5-imagick which is no longer built by the 
source package php-imagick.


I'm not sure if you can just change the dependency to php-imagick or if 
more work is needed.




Bug#816039: libpwiz: FTBFS: dh_testroot: You must run this as root (or use fakeroot)

2016-02-26 Thread Jakub Wilk

Source: libpwiz
Version: 3.0.8789-1
Severity: serious
Justification: fails to build from source

libpwiz FTBFS:
|  debian/rules build-arch
| "---"
| DEB_HOST_GNU_TYPE: i586-linux-gnu
| DEB_BUILD_GNU_TYPE i586-linux-gnu
| DEB_BUILD_OPTIONS: parallel=4
| DEB_HOST_MULTIARCH: i386-linux-gnu
| NUMJOBS: 4
| MAKEFLAGS:  -j4
| "---"
| entering the clean target
| dh_testdir
| dh_testroot
| dh_testroot: You must run this as root (or use fakeroot).
| debian/rules:73: recipe for target 'clean' failed
| make: *** [clean] Error 255
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=libpwiz=i386=3.0.8789-1=1443803953

--
Jakub Wilk



Processed: tagging 777675, reassign 813974 to dogecoin, fixed 813974 in 1.10.0-1, affects 813974 ...

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 777675 - moreinfo
Bug #777675 {Done: Patrick Matthäi } [fglrx-driver] 
qtcreator: hang and repeated SIGSEGV on exit
Removed tag(s) moreinfo.
> reassign 813974 dogecoin 1.8.10-1
Bug #813974 {Done: Keng-Yu Lin } 
[libbitcoinconsensus-dev,dogecoin] dogecoin and libbitcoinconsensus-dev: error 
when trying to install together
Bug reassigned from package 'libbitcoinconsensus-dev,dogecoin' to 'dogecoin'.
No longer marked as found in versions dogecoin/1.8.10-2, dogecoin/1.8.10-1, and 
bitcoin/0.11.2-1.
No longer marked as fixed in versions dogecoin/1.10.0-1.
Bug #813974 {Done: Keng-Yu Lin } [dogecoin] dogecoin and 
libbitcoinconsensus-dev: error when trying to install together
Marked as found in versions dogecoin/1.8.10-1.
> fixed 813974 1.10.0-1
Bug #813974 {Done: Keng-Yu Lin } [dogecoin] dogecoin and 
libbitcoinconsensus-dev: error when trying to install together
Marked as fixed in versions dogecoin/1.10.0-1.
> affects 813974 + libbitcoinconsensus-dev
Bug #813974 {Done: Keng-Yu Lin } [dogecoin] dogecoin and 
libbitcoinconsensus-dev: error when trying to install together
Added indication that 813974 affects libbitcoinconsensus-dev
> reassign 813973 dogecoin 1.8.10-1
Bug #813973 {Done: Keng-Yu Lin } 
[libbitcoinconsensus0,dogecoin] dogecoin and libbitcoinconsensus0: error when 
trying to install together
Bug reassigned from package 'libbitcoinconsensus0,dogecoin' to 'dogecoin'.
No longer marked as found in versions bitcoin/0.11.2-1, dogecoin/1.8.10-1, and 
dogecoin/1.8.10-2.
No longer marked as fixed in versions dogecoin/1.10.0-1.
Bug #813973 {Done: Keng-Yu Lin } [dogecoin] dogecoin and 
libbitcoinconsensus0: error when trying to install together
Marked as found in versions dogecoin/1.8.10-1.
> fixed 813973 1.10.0-1
Bug #813973 {Done: Keng-Yu Lin } [dogecoin] dogecoin and 
libbitcoinconsensus0: error when trying to install together
Marked as fixed in versions dogecoin/1.10.0-1.
> affects 813973 + libbitcoinconsensus0
Bug #813973 {Done: Keng-Yu Lin } [dogecoin] dogecoin and 
libbitcoinconsensus0: error when trying to install together
Added indication that 813973 affects libbitcoinconsensus0
> found 816019 0.1.9-2
Bug #816019 [roarplaylistd-codechelper-gst] roarplaylistd-codechelper-gst: 
Depends on gstreamer 0.10
Marked as found in versions roarplaylistd/0.1.9-2.
> found 816013 1.27.0-2
Bug #816013 [mp3cd] mp3cd: Depends on gstreamer 0.10
Marked as found in versions mp3cd/1.27.0-2.
> tags 816013 + sid stretch
Bug #816013 [mp3cd] mp3cd: Depends on gstreamer 0.10
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
777675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777675
813973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813973
813974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813974
816013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816013
816019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#785714: kexec-tools is broken when using systemd, danger of filesystem corruption

2016-02-26 Thread Daniel Baumann
Hi,

thanks for maintaining kexec-tools, however, kexec-tools reliably and
reproducibly trashes my root filesystem *on* *every* *reboot*.

can this be finally fixed please?

Regards,
Daniel



Bug#813819: MIA Ping

2016-02-26 Thread Tino Mettler
On Thu, Feb 25, 2016 at 12:29:25 +0100, Joachim Breitner wrote:
> Hi,
> 
> Am Donnerstag, den 25.02.2016, 11:51 +0100 schrieb Tino Mettler:
> > yes, I am. The simple change is not as simple as it seems. It got a
> > (not very verbose) build error in pbuilder and got no time for
> > investigating, yet. I'll ask for help if I can't figure it out this
> > evening.
> 
> here, I could simply rebuild syncevolution against unstable and it
> worked...

Ooops, it was a local problem. The oom-killer killed the compiler so
the build aborted with a (silent) error.

Regards,
Tino



Processed: tagging 815773, reassign 815970 to libtesseract3

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 815773 + sid stretch
Bug #815773 [ruby-zoom] ruby-zoom: FTBFS against ruby2.3
Added tag(s) stretch and sid.
> reassign 815970 libtesseract3 3.4.1-3
Bug #815970 [libtesseract3,libtesseract4] libtesseract4 and libtesseract3: 
error when trying to install together
Bug reassigned from package 'libtesseract3,libtesseract4' to 'libtesseract3'.
Ignoring request to alter found versions of bug #815970 to the same values 
previously set
Ignoring request to alter fixed versions of bug #815970 to the same values 
previously set
Bug #815970 [libtesseract3] libtesseract4 and libtesseract3: error when trying 
to install together
There is no source info for the package 'libtesseract3' at version '3.4.1-3' 
with architecture ''
Unable to make a source version for version '3.4.1-3'
Marked as found in versions 3.4.1-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
815773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815773
815970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#813819: Needs a rebuild due to libopenobex soname bump

2016-02-26 Thread Tino Mettler
On Fri, Feb 05, 2016 at 15:58:16 +0100, Joachim Breitner wrote:
> Package: syncevolution
> Version: 1.4.99.4-4+b1
> Severity: serious
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> the current package does not work:
> syncevolution: error while loading shared libraries: libopenobex.so.1: cannot 
> open shared object file: No such file or directory
> 
> There is now libopenobex2-dev, see http://bugs.debian.org/810556.

Hi,

I uploaded a package with a fix and also pushed the change to the git
repository.

You can find the package here:

http://tikei.de/debian/syncevolution/syncevolution_1.4.99.4-5.dsc

It would be nice if you can upload the package.

Regards,
Tino


signature.asc
Description: PGP signature


Processed: Re: [Pkg-javascript-devel] Bug#787924: node-crc: test failure Error: Use CoffeeScript.register()

2016-02-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 sid stretch
Bug #787924 {Done: Thorsten Alteholz } [node-crc] node-crc: 
test failure Error: Use CoffeeScript.register()
Added tag(s) stretch.

-- 
787924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#787924: [Pkg-javascript-devel] Bug#787924: node-crc: test failure Error: Use CoffeeScript.register()

2016-02-26 Thread Andreas Beckmann
Control: tag -1 sid stretch

On 2016-02-26 19:33, Thorsten Alteholz wrote:
> On Thu, 25 Feb 2016, Andreas Beckmann wrote:
>> this package FTBFS in a similar way in jessie:
> 
> yes, version 3.0.0-2 works on Jessie but FTBFS on Sid and 3.0.0-3 works
> on Sid but fails on Jessie. I think there has been some change in
> coffeescript...

Oops, you are right, somehow I picked up -3 for a testbuild on jessie.
-2 does actually work fine there.

Andreas



Bug#811431: fails to install: php5-symfony-debug.postinst: php5enmod: not found

2016-02-26 Thread David Prévot
Control: clone -1 -2
Control: reassign -2 dh-php5
Control: retitle -2 Should add explicit dependency

Hi,

On Tue, Jan 19, 2016 at 03:27:07AM +0100, Andreas Beckmann wrote:
> On 2016-01-19 02:38, David Prévot wrote:
> > php5-symfony-debug actually installs fine if php5-common is fetched
> > instead of php5.6-phpdbg (new package that also provides
> > phpapi-20131226).
> 
> Whatever apt considered to satisfy the dependency got installed ... if
> it has to choose, it takes the "wrong" choice ;-P

Right. Since dh-php5 is adding the php5enmod call in postinst, as well
as the dependency on phpapi-20131226, I assume the root issue is there
anyway.

> In case these transient bugs cause migration/removal problems, feel free
> to downgrade the severity.

I just stagged a workaround (adding an explicit dependency on
php5-common), but I guess it is better to address it properly in dh-php5
(since we’re getting rid of it, it could be worth ensuring that dh-php
is not affected by a similar issue).

Regards

David


signature.asc
Description: PGP signature


Processed: Re: fails to install: php5-symfony-debug.postinst: php5enmod: not found

2016-02-26 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #811431 [php5-symfony-debug] php5-symfony-debug: fails to install: 
php5-symfony-debug.postinst: php5enmod: not found
Bug 811431 cloned as bug 816029
> reassign -2 dh-php5
Bug #816029 [php5-symfony-debug] php5-symfony-debug: fails to install: 
php5-symfony-debug.postinst: php5enmod: not found
Bug reassigned from package 'php5-symfony-debug' to 'dh-php5'.
No longer marked as found in versions symfony/2.7.7+dfsg-1 and 
symfony/2.7.9+dfsg-1.
Ignoring request to alter fixed versions of bug #816029 to the same values 
previously set
> retitle -2 Should add explicit dependency
Bug #816029 [dh-php5] php5-symfony-debug: fails to install: 
php5-symfony-debug.postinst: php5enmod: not found
Changed Bug title to 'Should add explicit dependency' from 'php5-symfony-debug: 
fails to install: php5-symfony-debug.postinst: php5enmod: not found'

-- 
811431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811431
816029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#813452: fpc-3.0 regression in armhf and armel architectures

2016-02-26 Thread Paul Gevers
Hi Gianfranco,

On 26-02-16 10:53, Gianfranco Costamagna wrote:
> fpc 
> Free Pascal Compiler version 3.0.1+dfsg-1 [2016/02/25] for arm
> Copyright (c) 1993-2015 by Florian Klaempfl and others
> /usr/bin/fpc-3.0.1 [options]  [options]
> 
> so fPIC seems to be *not* fixed in current trunk (unless I did something 
> seriously wrong).
> Moreover current trunk doesn't build :)

Trunk is already at 3.1.1. So you apparently did not get trunk this way.

And Abou in the message before yours to this bug report already showed
that the issue with fprint IS fixed in trunk.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#789835: memcached: FTBFS in sid: timeout in t/lru-crawler.t

2016-02-26 Thread Dominic Hargreaves
On Sat, Feb 20, 2016 at 03:39:33PM +, Julien Cristau wrote:
> On Mon, Jul 20, 2015 at 23:52:42 +0200, Guillaume Delacour wrote:
> 
> > On Mon, 29 Jun 2015 22:40:01 +0200 Guillaume Delacour 
> > wrote:
> > > > 
> > > > This package FTBFS in a clean sid sbuild setup:
> > > > 
> > > > t/line-lengths.t . ok
> > > > Timeout.. killing the process
> > > > t/lru-crawler.t .. 
> > > > Failed 126/221 subtests 
> > > 
> > > Seems to be a random issue that affect other distributions (i'm quite
> > > sure to have been reproduced at least one time a long time ago, but
> > > wrongly guess this was my env):
> > > 
> > > http://forums.famillecollet.com/viewtopic.php?id=3165
> > > https://code.google.com/p/memcached/issues/detail?id=398
> > > http://webcache.googleusercontent.com/search?q=cache:2j2npL8eOAMJ:https://arch-ci.org/extra/memcached/log/+=10=fr=clnk
> > > 
> > > I've opened issue on upstream googlecode (as GitHub memcached space
> > > don't let me create issues) to have his point of view about this issue.
> > 
> > Upstream and i don't reproduce the problem, do you ?
> > I tried to iterate around 250 times on this test and never reproduce this.
> > 
> > $ while true ; do prove t/lru-crawler.t ; done
> > 
> > If you reproduce it, don't hesitate to give me as much details as
> > possible to reproduce myself/upstream to fix this issue.
> > 
> If you want to ask the submitter a question, it's better to actually
> send them mail, rather than just to the BTS.

I don't have the test infrastructure I used to report this (it would
have been to do with the perl 5.22 rebuilds) so I can't help, sorry.



Bug#787924: [Pkg-javascript-devel] Bug#787924: node-crc: test failure Error: Use CoffeeScript.register()

2016-02-26 Thread Thorsten Alteholz

Hi Andreas,

On Thu, 25 Feb 2016, Andreas Beckmann wrote:

this package FTBFS in a similar way in jessie:


yes, version 3.0.0-2 works on Jessie but FTBFS on Sid and 3.0.0-3 works 
on Sid but fails on Jessie. I think there has been some change in 
coffeescript...


 Thorsten



Bug#816016: marked as done (starpu-contrib: needs a rebuild against libglpk39)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 19:27:25 +0100
with message-id <20160226182725.gz3...@var.bordeaux.inria.fr>
and subject line Re: Bug#816016: starpu-contrib: needs a rebuild against 
libglpk39
has caused the Debian Bug report #816016,
regarding starpu-contrib: needs a rebuild against libglpk39
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starpu-contrib
Version: 1.1.4+dfsg-4
Severity: serious

Your package depends on libglpk36. The soname of that lib has been
bumped, so your package needs a rebuild to pick up a dependency on
libglpk39.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Emilio Pozuelo Monfort, on Fri 26 Feb 2016 18:33:47 +0100, wrote:
> Your package depends on libglpk36. The soname of that lib has been
> bumped, so your package needs a rebuild to pick up a dependency on
> libglpk39.

Now uploaded, thanks for the notice.

Samuel--- End Message ---


Bug#812456: davfs2: dies with stack smashing error; can't mount

2016-02-26 Thread Werner Baumann
This is a (very) late reply from upstream.
Sorry for the delay. I hoped somebody else would care because I had no
32-bit testing system.

Now I have upgraded an old Thinkpad from Jessie to Stretch installed
davfs2-1.5.2-1.2 from Sid and tested. Result:

Works as expected; no stack smashing error. I can't reproduce the
problem.

Could you please verify that the problem still exists, probably after
updating your system and checking for possible inconsistencies?

Werner



Bug#816021: xerces-c: FTBFS: Exception in thread "main" java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper

2016-02-26 Thread Salvatore Bonaccorso
Source: xerces-c
Version: 3.1.2+debian-1
Severity: serious
Justification: FTBFS

Hi

src:xerces-c FTBFS on unstable:

> [Xalan2Processor] Applying XSL sheet 
> "sbk:/style/stylesheets/context2label.xsl"
> Exception in thread "main" java.awt.AWTError: Assistive Technology not found: 
> org.GNOME.Accessibility.AtkWrapper  
> at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:807)
> at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:886)
> at javax.swing.ImageIcon.(ImageIcon.java:198)
> at javax.swing.ImageIcon.(ImageIcon.java:217)
> at org.apache.stylebook.printers.ImagePrinter.print(Unknown Source)
> at org.apache.stylebook.BasicEntry.create(Unknown Source)
> at org.apache.stylebook.Project.create(Unknown Source)
> at org.apache.stylebook.StyleBook.main(Unknown Source)
> make[1]: *** [override_dh_auto_build-indep] Error 1
> debian/rules:19: recipe for target 'override_dh_auto_build-indep' failed
> make[1]: Leaving directory '/BUILDDIR/xerces-c-3.1.2+debian'
> make: *** [build] Error 2
> debian/rules:4: recipe for target 'build' failed

Full build log attached.

Regards,
Salvatore


xerces-c_3.1.2+debian-1_amd64.build.gz
Description: application/gzip


Bug#816019: roarplaylistd-codechelper-gst: Depends on gstreamer 0.10

2016-02-26 Thread Moritz Muehlenhoff
Package: roarplaylistd-codechelper-gst
Severity: serious

gstreamer 0.10 is being removed from Debian, but
roarplaylistd-codechelper-gst still depends on gstreamer-tools (which is
for gst 0.10), please depend on gstreamer1.0-tools instead.

Cheers,
Moritz



Bug#816016: starpu-contrib: needs a rebuild against libglpk39

2016-02-26 Thread Emilio Pozuelo Monfort
Source: starpu-contrib
Version: 1.1.4+dfsg-4
Severity: serious

Your package depends on libglpk36. The soname of that lib has been
bumped, so your package needs a rebuild to pick up a dependency on
libglpk39.

Cheers,
Emilio



Bug#816013: mp3cd: Depends on gstreamer 0.10

2016-02-26 Thread Moritz Muehlenhoff
Package: mp3cd
Severity: serious

gstreamer 0.10 is being removed from Debian, but mp3cd still depends
on gstreamer-tools (which is for gst 0.10), please depend on
gstreamer1.0-tools instead.

Cheers,
Moritz



Bug#815731: marked as done (arandr: Doesn't work with the current version of xrandr)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 16:26:59 +
with message-id 
and subject line Bug#815731: fixed in arandr 0.1.9-1
has caused the Debian Bug report #815731,
regarding arandr: Doesn't work with the current version of xrandr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arandr
Version: 0.1.8-1
Severity: grave
Justification: renders package unusable

Lately, xrandr has been updated to v1.5:

user@host:~$ xrandr --version
xrandr program version   1.5.0
Server reports RandR version 1.5

arandr doesn't like that at all:

user@host:~$ arandr 
Traceback (most recent call last):
  File "/usr/bin/arandr", line 42, in 
main()
  File "/usr/lib/python2.7/dist-packages/screenlayout/gui.py", line 319, in main
force_version=options.force_version
  File "/usr/lib/python2.7/dist-packages/screenlayout/gui.py", line 157, in 
__init__
self.widget = widget.ARandRWidget(display=randr_display, 
force_version=force_version)
  File "/usr/lib/python2.7/dist-packages/screenlayout/widget.py", line 48, in 
__init__
self._xrandr = XRandR(display=display, force_version=force_version)
  File "/usr/lib/python2.7/dist-packages/screenlayout/xrandr.py", line 45, in 
__init__
raise Exception("XRandR 1.2/1.3 required.")
Exception: XRandR 1.2/1.3 required.

If this can't be fixed easily, then at a versioned dependency
should be added to the package. (It still won't be usable for sid,
but at least ppl will know.)


-- Package-specific info:
Output of /usr/share/bug/arandr:
$ xrandr --version
xrandr program version   1.5.0
Server reports RandR version 1.5
$ xrandr --query --current
Screen 0: minimum 320 x 200, current 9600 x 1200, maximum 16384 x 16384
LVDS connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 
382mm x 215mm
   1920x1080 60.01*+
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 59.89  
   1440x900  59.89  
   1280x960  59.94  
   1280x854  59.89  
   1280x800  59.81  
   1280x720  59.86  
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
DisplayPort-0 connected 1920x1200+1920+0 (normal left inverted right x axis y 
axis) 518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1600x1200 60.00  
   1680x1050 59.95  
   1280x1024 60.02  
   1280x960  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   60.00  
   720x400   70.08  
DisplayPort-1 connected 1920x1200+3840+0 (normal left inverted right x axis y 
axis) 518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1600x1200 60.00  
   1680x1050 59.88  
   1280x1024 60.02  
   1280x960  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   60.00  
   720x400   70.08  
DisplayPort-2 connected 1920x1200+5760+0 (normal left inverted right x axis y 
axis) 518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1600x1200 60.00  
   1680x1050 59.95  
   1280x1024 60.02  
   1280x960  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   60.00  
   720x400   70.08  
VGA-0 connected 1920x1200+7680+0 (normal left inverted right x axis y axis) 
518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1600x1200 60.00  
   1680x1050 59.95  
   1280x1024 60.02  
   1280x960  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   60.00  
   720x400   70.08  
$ xrandr --query --current --verbose
Screen 0: minimum 320 x 200, current 9600 x 1200, maximum 16384 x 16384
LVDS connected primary 1920x1080+0+0 (0x5b) normal (normal left inverted right 
x axis y axis) 382mm x 215mm
Identifier: 0x55
Timestamp:  1208114748
Subpixel:   horizontal rgb
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2 3 4 5
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000030e4da02
00140104902615780af195a35552a126
0f50540001010101010101010101
010101010101b03680b0703821403020
35007ed71018b03680b070382140
   

Bug#813973: marked as done (dogecoin and libbitcoinconsensus0: error when trying to install together)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 15:38:15 +
with message-id 
and subject line Bug#813973: fixed in dogecoin 1.10.0-1
has caused the Debian Bug report #813973,
regarding dogecoin and libbitcoinconsensus0: error when trying to install 
together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbitcoinconsensus0,dogecoin
Version: libbitcoinconsensus0/0.11.2-1
Version: dogecoin/1.8.10-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-02-07
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 30%
Extracting templates from packages: 60%
Extracting templates from packages: 90%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libexpat1:amd64.
(Reading database ... 10944 files and directories currently installed.)
Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-7) ...
Selecting previously unselected package libpng12-0:amd64.
Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.54-1) ...
Selecting previously unselected package libfreetype6:amd64.
Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
Selecting previously unselected package ucf.
Preparing to unpack .../archives/ucf_3.0033_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0033) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
Unpacking fonts-dejavu-core (2.35-1) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
Unpacking fontconfig-config (2.11.0-6.3) ...
Selecting previously unselected package libfontconfig1:amd64.
Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
Selecting previously unselected package fontconfig.
Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
Unpacking fontconfig (2.11.0-6.3) ...
Selecting previously unselected package x11-common.
Preparing to unpack .../x11-common_1%3a7.7+13_all.deb ...
Unpacking x11-common (1:7.7+13) ...
Selecting previously unselected package libice6:amd64.
Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
Selecting previously unselected package libmtdev1:amd64.
Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
Unpacking libmtdev1:amd64 (1.1.5-1) ...
Selecting previously unselected package libsm6:amd64.
Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.4-5) ...
Processing triggers for libc-bin (2.21-7) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libgcrypt20:amd64 (1.6.4-5) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libsystemd0:amd64.
(Reading database ... 11204 files and directories currently installed.)
Preparing to unpack .../libsystemd0_228-6_amd64.deb ...
Unpacking libsystemd0:amd64 (228-6) ...
Selecting previously unselected package libxau6:amd64.
Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
Unpacking libxau6:amd64 (1:1.0.8-1) ...
Selecting previously unselected package libxdmcp6:amd64.
Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
Selecting previously unselected package libxcb1:amd64.
Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
Unpacking libxcb1:amd64 (1.11.1-1) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
Unpacking libx11-data (2:1.6.3-1) ...
Selecting previously unselected package libx11-6:amd64.
Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-6:amd64 (2:1.6.3-1) ...
Selecting previously unselected package libx11-xcb1:amd64.
Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
Selecting previously unselected 

Bug#813974: marked as done (dogecoin and libbitcoinconsensus-dev: error when trying to install together)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 15:38:15 +
with message-id 
and subject line Bug#813974: fixed in dogecoin 1.10.0-1
has caused the Debian Bug report #813974,
regarding dogecoin and libbitcoinconsensus-dev: error when trying to install 
together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbitcoinconsensus-dev,dogecoin
Version: libbitcoinconsensus-dev/0.11.2-1
Version: dogecoin/1.8.10-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-02-07
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 29%
Extracting templates from packages: 59%
Extracting templates from packages: 89%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libexpat1:amd64.
(Reading database ... 10944 files and directories currently installed.)
Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-7) ...
Selecting previously unselected package libpng12-0:amd64.
Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.54-1) ...
Selecting previously unselected package libfreetype6:amd64.
Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
Selecting previously unselected package ucf.
Preparing to unpack .../archives/ucf_3.0033_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0033) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
Unpacking fonts-dejavu-core (2.35-1) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
Unpacking fontconfig-config (2.11.0-6.3) ...
Selecting previously unselected package libfontconfig1:amd64.
Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
Selecting previously unselected package fontconfig.
Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
Unpacking fontconfig (2.11.0-6.3) ...
Selecting previously unselected package x11-common.
Preparing to unpack .../x11-common_1%3a7.7+13_all.deb ...
Unpacking x11-common (1:7.7+13) ...
Selecting previously unselected package libice6:amd64.
Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
Selecting previously unselected package libmtdev1:amd64.
Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
Unpacking libmtdev1:amd64 (1.1.5-1) ...
Selecting previously unselected package libsm6:amd64.
Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.4-5) ...
Processing triggers for libc-bin (2.21-7) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libgcrypt20:amd64 (1.6.4-5) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libsystemd0:amd64.
(Reading database ... 11204 files and directories currently installed.)
Preparing to unpack .../libsystemd0_228-6_amd64.deb ...
Unpacking libsystemd0:amd64 (228-6) ...
Selecting previously unselected package libxau6:amd64.
Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
Unpacking libxau6:amd64 (1:1.0.8-1) ...
Selecting previously unselected package libxdmcp6:amd64.
Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
Selecting previously unselected package libxcb1:amd64.
Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
Unpacking libxcb1:amd64 (1.11.1-1) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
Unpacking libx11-data (2:1.6.3-1) ...
Selecting previously unselected package libx11-6:amd64.
Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-6:amd64 (2:1.6.3-1) ...
Selecting previously unselected package libx11-xcb1:amd64.
Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
Selecting previously 

Processed: Re: elastix: diff for NMU version 4.8-3.1

2016-02-26 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #815996 [elastix] elastix: diff for NMU version 4.8-3.1
Added tag(s) patch.
> tags -1 pending
Bug #815996 [elastix] elastix: diff for NMU version 4.8-3.1
Added tag(s) pending.

-- 
815996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#815996: elastix: diff for NMU version 4.8-3.1

2016-02-26 Thread Gianfranco Costamagna
control: tags -1 patch
control: tags -1 pending

Hi, I'm attaching the patch with the bug closed. And I'm uploading on
deferred/7.

cheers,

G.

On Fri, 26 Feb 2016 13:41:32 + (UTC) Gianfranco Costamagna
 wrote:
> Package: elastix
> Version: 4.8-3
> Severity: serious
> Justification: FTBFS
> 
> 
> Dear maintainer,
> 
> the elastix package doesn't build anymore against the new ITK4.9.
> I did cherry-pick the patch from upstream and the build was successful.
> 
> build error:
> https://launchpadlibrarian.net/243044486/buildlog_ubuntu-xenial-amd64.elastix_4.8-3build1_BUILDING.txt.gz
> the patch is really simple, you can see it below, or just drag it from there
> http://launchpadlibrarian.net/243063499/elastix_4.8-3build1_4.8-3ubuntu1.diff.gz
> 
> upstream commits:
> r5140 | kmarstal | 2015-11-16 09:38:55 + (Mon, 16 Nov 2015) | 1 line
> 
> r5139 | dpshamonin | 2015-11-13 12:42:05 + (Fri, 13 Nov 2015) | 1 line
> 
> 
> I'm uploading it to deferred/15 and attaching the debdiff to this email.
> (I'll close this bug in changelog)
diff -Nru elastix-4.8/debian/changelog elastix-4.8/debian/changelog
--- elastix-4.8/debian/changelog2016-01-07 12:50:07.0 +0100
+++ elastix-4.8/debian/changelog2016-02-26 14:46:49.0 +0100
@@ -1,3 +1,11 @@
+elastix (4.8-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/fix-cast-error.patch:
+fix FTBFS with insighttoolkit4.9 (Closes: #815996).
+
+ -- Gianfranco Costamagna   Fri, 26 Feb 2016 
12:54:10 +0100
+
 elastix (4.8-3) unstable; urgency=medium
 
   [ Andreas Tille ]
diff -Nru elastix-4.8/debian/patches/fix-cast-error.patch 
elastix-4.8/debian/patches/fix-cast-error.patch
--- elastix-4.8/debian/patches/fix-cast-error.patch 1970-01-01 
01:00:00.0 +0100
+++ elastix-4.8/debian/patches/fix-cast-error.patch 2016-02-26 
14:39:54.0 +0100
@@ -0,0 +1,70 @@
+Description: fix FTBFS because of an overload issue with ITK-4.9
+
+In file included from 
/«PKGBUILDDIR»/src/Components/Optimizers/AdaptiveStochasticGradientDescent/elxAdaptiveStochasticGradientDescent.h:430:0,
+ from 
/«PKGBUILDDIR»/src/Components/Optimizers/AdaptiveStochasticGradientDescent/elxAdaptiveStochasticGradientDescent.cxx:19:
+/«PKGBUILDDIR»/src/Components/Optimizers/AdaptiveStochasticGradientDescent/elxAdaptiveStochasticGradientDescent.hxx:194:45:
 error: call of overloaded 'vnl_math_min(const unsigned int&, int)' is ambiguous
+ const unsigned int movdim = vnl_math_min( 
this->GetElastix()->MovingDimension, 2 );
+ ^
+In file included from /usr/include/ITK-4.9/itkVector.hxx:21:0,
+ from /usr/include/ITK-4.9/itkVector.h:289,
+ from /usr/include/ITK-4.9/itkPoint.h:23,
+ from /usr/include/ITK-4.9/itkContinuousIndex.h:21,
+ from /usr/include/ITK-4.9/itkImageRegion.h:34,
+ from /usr/include/ITK-4.9/itkImageIORegion.h:24,
+ from /usr/include/ITK-4.9/itkImageIOBase.h:26,
+ from /usr/include/ITK-4.9/itkImageFileReader.h:24,
+ from /«PKGBUILDDIR»/src/Core/Kernel/elxElastixBase.h:39,
+ from /«PKGBUILDDIR»/src/Core/Kernel/elxElastixTemplate.h:21,
+ from /«PKGBUILDDIR»/src/Core/Install/elxIncludes.h:39,
+ from 
/«PKGBUILDDIR»/src/Components/Optimizers/AdaptiveStochasticGradientDescent/elxAdaptiveStochasticGradientDescent.h:21,
+ from 
/«PKGBUILDDIR»/src/Components/Optimizers/AdaptiveStochasticGradientDescent/elxAdaptiveStochasticGradientDescent.cxx:19:
+/usr/include/ITK-4.9/vnl/vnl_math.h:567:27: note: candidate: int 
vnl_math_min(int, int)
+ inline intvnl_math_min(int x, int y)  
 { return (x < y) ? x : y; }
+   ^
+/usr/include/ITK-4.9/vnl/vnl_math.h:568:27: note: candidate: unsigned int 
vnl_math_min(unsigned int, unsigned int)
+ inline unsigned int   vnl_math_min(unsigned int x, unsigned int y)
 { return (x < y) ? x : y; }
+   ^
+/usr/include/ITK-4.9/vnl/vnl_math.h:569:27: note: candidate: long int 
vnl_math_min(long int, long int)
+ inline long   vnl_math_min(long x, long y)
 { return (x < y) ? x : y; }
+   ^
+/usr/include/ITK-4.9/vnl/vnl_math.h:570:27: note: candidate: long unsigned int 
vnl_math_min(long unsigned int, long unsigned int)
+ inline unsigned long  vnl_math_min(unsigned long x, unsigned long y)  
 { return (x < y) ? x : y; }
+   ^
+/usr/include/ITK-4.9/vnl/vnl_math.h:571:27: note: candidate: long long int 
vnl_math_min(long long int, long long int)
+ inline long long  vnl_math_min(long long x, long long y)  
 { return (x < y) ? x : y; }
+   ^

Bug#815996: elastix: diff for NMU version 4.8-3.1

2016-02-26 Thread Gianfranco Costamagna
Package: elastix
Version: 4.8-3
Severity: serious
Justification: FTBFS


Dear maintainer,

the elastix package doesn't build anymore against the new ITK4.9.
I did cherry-pick the patch from upstream and the build was successful.

build error:
https://launchpadlibrarian.net/243044486/buildlog_ubuntu-xenial-amd64.elastix_4.8-3build1_BUILDING.txt.gz
the patch is really simple, you can see it below, or just drag it from there
http://launchpadlibrarian.net/243063499/elastix_4.8-3build1_4.8-3ubuntu1.diff.gz

upstream commits:
r5140 | kmarstal | 2015-11-16 09:38:55 + (Mon, 16 Nov 2015) | 1 line

r5139 | dpshamonin | 2015-11-13 12:42:05 + (Fri, 13 Nov 2015) | 1 line


I'm uploading it to deferred/15 and attaching the debdiff to this email.
(I'll close this bug in changelog)


debdiff
Description: Binary data


Bug#808692: marked as done (watchdog: FTBFS: dpkg-genbuildinfo: error: cannot fstat file ../watchdog-dbgsym_5.14-3_amd64.deb: No such file or directory)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 12:36:38 +
with message-id 
and subject line Bug#808692: fixed in watchdog 5.15-1
has caused the Debian Bug report #808692,
regarding watchdog: FTBFS: dpkg-genbuildinfo: error: cannot fstat file 
../watchdog-dbgsym_5.14-3_amd64.deb: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
808692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: watchdog
Version: 5.14-3
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

dh_fixperms
dpkg --build debian/watchdog ..
dpkg-deb: building package 'watchdog' in '../watchdog_5.14-3_amd64.deb'.
 dpkg-genchanges  >../watchdog_5.14-3_amd64.changes
dpkg-genchanges: warning: package watchdog-dbgsym listed in files list but not 
in control info
dpkg-genchanges: not including original source code in upload
dpkg-genchanges: error: cannot fstat file ../watchdog-dbgsym_5.14-3_amd64.deb: 
No such file or directory
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/watchdog.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: watchdog
Source-Version: 5.15-1

We believe that the bug you reported is fixed in the latest version of
watchdog, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 808...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated watchdog package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Jan 2016 22:54:48 +0100
Source: watchdog
Binary: watchdog
Architecture: source amd64
Version: 5.15-1
Distribution: unstable
Urgency: medium
Maintainer: Michael Meskes 
Changed-By: Michael Meskes 
Description:
 watchdog   - system health checker and software/hardware watchdog handler
Closes: 772760 776125 783166 784211 793309 798294 808692 815857
Changes:
 watchdog (5.15-1) unstable; urgency=medium
 .
   * New upstream version.
   * Updated Dutch translation. (Closes: #772760)
   * Updated Russian translation. (Closes: #776125)
   * Updated Japanese translation. (Closes: #815857)
   * Added missing quote to systemd service file. (Closes: #783166, #798294)
   * Use dh_builddeb to build the package. (Closes: #784211, #808692)
   * Re-added Install stanza to service file. (Closes: #793309)
Checksums-Sha1:
 6315f0991efef32c947a5fe155d060862bb9f527 1688 watchdog_5.15-1.dsc
 92307c420bf900911e6bae0d022c293ba3092adc 228132 watchdog_5.15.orig.tar.gz
 339a42f407b0a52b9da5f323adb91e521566b04e 670 watchdog_5.15-1.diff.gz
 4c2ecdf39336d3b27e1833a7df99c2c69d070f68 158066 
watchdog-dbgsym_5.15-1_amd64.deb
 0fb5f3ce1165ed0623297cf679d09fd9dafbcc87 90130 watchdog_5.15-1_amd64.deb
Checksums-Sha256:
 39c1714bdfe1d2c99c8687f2b9f534276d5be69375606d6918eaadf4db2baf17 1688 
watchdog_5.15-1.dsc
 ffdc865137ad5d8e53664bd22bad4de6ca136d1b4636720320cb52af0c18947c 228132 
watchdog_5.15.orig.tar.gz
 f906dfca6bb63a9013004ad368aee452c38fb9981f7e6cf8ef0813d75082ada5 670 
watchdog_5.15-1.diff.gz
 3e46d51ad180b224cf5ca657c06663a1b2a76f0ab8b435f90e7f4c09820ae568 158066 
watchdog-dbgsym_5.15-1_amd64.deb
 6771f4f753776557254c08505eb95a26c90e43864561c83a57345c7124f948e0 90130 
watchdog_5.15-1_amd64.deb
Files:
 950a02dfdefa828a0dc827e7fb627cad 1688 admin extra watchdog_5.15-1.dsc
 678c32f6f35a0492c9c1b76b4aa88828 228132 admin extra watchdog_5.15.orig.tar.gz
 414b89232279c0f5beb50615ba0a53a6 670 admin extra watchdog_5.15-1.diff.gz
 dd93b988952f147b5463c1defe05b0cb 158066 debug extra 
watchdog-dbgsym_5.15-1_amd64.deb
 f39d6c425723b94dbd4ed9d322723ab5 90130 admin extra watchdog_5.15-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1


Bug#815978: aptitude: 'aptitude show' segfaults on some packages

2016-02-26 Thread anabioz34
On Fri, Feb 26, 2016 at 11:18:06AM +, Manuel A. Fernandez Montecelo wrote:
> OK, thanks!
> 
> 
> -- 
> Manuel A. Fernandez Montecelo 
> 
Thank you for the quick response.



Bug#815983: nodejs: Program received signal SIGILL on i686

2016-02-26 Thread Daniele Forsi
Package: nodejs
Version: 4.3.1~dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

running nodejs with or without arguments on a Pentium III results in an illegal 
instruction fault:
$ LANG= gdb nodejs
[...]
Program received signal SIGILL, Illegal instruction.
0x083ceefb in v8::internal::(anonymous namespace)::Flag::IsDefault 
(this=0x8a49870 )
at ../deps/v8/src/flags.cc:122
122 ../deps/v8/src/flags.cc: No such file or directory.
(gdb) bt
#0  0x083ceefb in v8::internal::(anonymous namespace)::Flag::IsDefault 
(this=0x8a49870 )
at ../deps/v8/src/flags.cc:122
#1  v8::internal::ComputeFlagListHash () at ../deps/v8/src/flags.cc:556
#2  0x083cf1fe in v8::internal::FlagList::EnforceFlagImplications () at 
../deps/v8/src/flags.cc:572
#3  0x0861ad1a in v8::internal::V8::InitializeOncePerProcessImpl () at 
../deps/v8/src/v8.cc:67
#4  0x08738ec8 in v8::base::CallOnceImpl (once=0x8a4f2b0 
, 
init_func=0x861ad10 , 
arg=0x0) at ../deps/v8/src/base/once.cc:37
#5  0x0861ae31 in v8::base::CallOnce (init_func=, 
once=) at ../deps/v8/src/base/once.h:86
#6  v8::internal::V8::InitializeOncePerProcess () at ../deps/v8/src/v8.cc:107
#7  v8::internal::V8::Initialize () at ../deps/v8/src/v8.cc:43
#8  0x0826dadb in v8::V8::Initialize () at ../deps/v8/src/api.cc:5345
#9  0x086c6c8f in node::Start (argc=1, argv=0x8a560f8) at ../src/node.cc:4163
#10 0x0825897b in main (argc=1, argv=0xb2e4) at ../src/node_main.cc:44
(gdb)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nodejs depends on:
ii  libc62.21-8
ii  libgcc1  1:5.3.1-8
ii  libicu55 55.1-7
ii  libssl1.0.2  1.0.2f-2
ii  libstdc++6   5.3.1-8
ii  libuv1   1.8.0-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

nodejs recommends no packages.

nodejs suggests no packages.

-- no debconf information



Bug#815978: aptitude: 'aptitude show' segfaults on some packages

2016-02-26 Thread Manuel A. Fernandez Montecelo

2016-02-26 11:10 anabioz34:


Can you please confirm that for example unattended-upgrades was not
installed in your system?


Yes, it's not installed in my system.


OK, thanks!


--
Manuel A. Fernandez Montecelo 



Bug#815978: aptitude: 'aptitude show' segfaults on some packages

2016-02-26 Thread anabioz34
On Fri, Feb 26, 2016 at 11:01:36AM +, Manuel A. Fernandez Montecelo wrote:
> Control: forcemerge 815581 -1
> 
> 
> Hi,
> 
> 2016-02-26 09:57 anabioz34:
> >Subject: aptitude: 'aptitude show' segfaults on some packages
> >Package: aptitude
> >Version: 0.7.6-1
> >Severity: normal
> >
> >Dear Maintainer,
> >
> >Sometimes, 'aptitude show' lead to 'Segmentation fault (core dumped)'
> >(exit-code 139). For example, aptitude show unattended-upgrades. I tried
> >to update packages list, but it did not give any effect. This bug is
> >rare and does not affect most of the packages.
> 
> Presumably it happens with the packages that are not installed (there
> have been a couple of reports like that), so I am going to merge the
> report with them.
> 
> Can you please confirm that for example unattended-upgrades was not
> installed in your system?
> 
> 
> Cheers.
> -- 
> Manuel A. Fernandez Montecelo 
> 
Yes, it's not installed in my system.



Processed: Re: aptitude: 'aptitude show' segfaults on some packages

2016-02-26 Thread Debian Bug Tracking System
Processing control commands:

> forcemerge 815581 -1
Bug #815581 [aptitude] aptitude crashes when trying to show information about 
packages that are not installed
Bug #815810 [aptitude] "aptitude show pkgname" does not display information 
about non-installed packages
Bug #815978 [aptitude] aptitude: 'aptitude show' segfaults on some packages
Severity set to 'serious' from 'normal'
Added tag(s) pending and confirmed.
Bug #815810 [aptitude] "aptitude show pkgname" does not display information 
about non-installed packages
Merged 815581 815810 815978

-- 
815581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815581
815810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815810
815978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#815981: findbugs: does not start without root permissions

2016-02-26 Thread Luca Ghio
Package: findbugs
Version: 3.0.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
I installed the findbugs package and I launched it by the following command:

$ findbugs

The window of the GUI opened, so I clicked the "File" menu and the application
froze.

The console printed out:

(java:6177): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0'
failed

(java:6177): Gdk-CRITICAL **: gdk_screen_is_composited: assertion
'GDK_IS_SCREEN (screen)' failed

I had to close the running process, which was the following one (under "ps
-fe"):

java -classpath
/usr/share/findbugs/lib/findbugs.jar:/usr/share/java/dom4j.jar:/usr/share/java/junit4.jar:/usr/share/java
/commons-
lang.jar:/usr/share/java/jaxen.jar:/usr/share/java/jdepend.jar:/usr/share/java/asm4.jar:/usr/share/java/asm4-commons.jar:/usr/share/java/asm4-tree.jar:/usr/share/java/ant.jar:/usr/share/java/jcip.jar:/usr/share/java/jsr305.jar:/usr/share/java/jFormatString.jar:/usr/share/java/bcel.jar
-Dfindbugs.home=/usr/share/findbugs -Xmx768m
-Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel
edu.umd.cs.findbugs.LaunchAppropriateUI

The application appears to work when:

1) launching the following command:
$ java -jar /usr/share/java/findbugs.jar

2) running it under root permissions, e.g.:
# findbugs



-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (990, 'testing-updates'), (990, 'testing'), (500, 'unstable'), 
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages findbugs depends on:
ii  default-jre [java7-runtime]2:1.7-52.1
ii  java-wrappers  0.1.28
ii  junit4 4.12-4
ii  libasm4-java   5.0.4-1
ii  libbcel-java   6.0~rc3-2
ii  libcommons-lang-java   2.6-6
ii  libdom4j-java  1.6.1+dfsg.3-2
ii  libjaxen-java  1.1.6-1
ii  libjcip-annotations-java   20060626-5
ii  libjdepend-java2.9.1-1
ii  libjformatstring-java  0.10~20131207-1
ii  libjsr305-java 0.1~+svn49-9
ii  openjdk-7-jre [java7-runtime]  7u91-2.6.3-1
ii  openjdk-8-jre [java7-runtime]  8u72-b05-6

findbugs recommends no packages.

findbugs suggests no packages.

-- no debconf information



Processed: closing 814650

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 814650 0.7.8-3
Bug #814650 [python-xattr] python-xattr: No module named cffi
Marked as fixed in versions python-xattr/0.7.8-3.
Bug #814650 [python-xattr] python-xattr: No module named cffi
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
814650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#815979: dotclear: New minor releases with security fixes

2016-02-26 Thread Vincent Danjean
Package: dotclear
Version: 2.8.0+dfsg-1
Severity: serious
Tags: security
Justification: security

  Hi,

  I'm using Debian packages of dotclear (a php blogs engine) for a few years.
For 6 months, the package do not change, and I did not get any anwser to
my previous bug reports, including an important one (#797055) that probably
prevent any one to use the Debian package as-is.
  I just see today that two minor releases have been published that
fix security bugs. From upstream webpage:
===
News

2015 Oct 25 Dotclear 2.8.2

A new maintenance release which fixes one potential XSS vulnerability in
comments's list and enforce media extension before upload[1] (thanks to Tim
Coen, Curesec Gmbh, for reporting them) and two...

2015 Sep 23 Dotclear 2.8.1

A new maintenance release which fixes one potential XSS vulnerabilities
(thanks to Yuji Tounai of NTT Com Security (Japan) KK, via Keiko Yashiki from
JPCERT/CC) and two other bugfixes. Your dashboard...
===

  I tagged this bug with a serious severity so that, if dotclear is not
maintained anymore, it will be removed from testing (so admins tracking testing
will be notified and can manually install the upstream versions). If dotclear
is still maintained (I hope for that), then an update must be done.

  Note that I do not know if the security bugs also apply or not to the
jessie version.

  Regards,
Vincent

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'squeeze-lts'), (500, 
'oldstable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dotclear depends on:
ii  apache2 [httpd]2.4.18-1
ii  dbconfig-common2.0.3
ii  debconf [debconf-2.0]  1.5.58
pn  libapache2-mod-php5 | php5 | php5-cgi  
ii  libjs-jquery   1.11.3+dfsg-4
ii  libjs-jquery-cookie10-2
ii  libjs-jquery-ui1.10.1+dfsg-1
pn  php5-cli   
pn  php5-mysql | php5-pgsql | php5-sqlite  
ii  sqlite33.11.0-2

Versions of packages dotclear recommends:
ii  apache2 [httpd] 2.4.18-1
pn  mysql-server | mariadb-server | postgresql  

dotclear suggests no packages.

-- debconf information excluded



Bug#814606: libvigraimpex: FTBFS on armel (error: return type 'class std::future')

2016-02-26 Thread Ullrich Koethe

threadpool.hxx:333:26: error: return type 'class std::future' is 
incomplete
 ThreadPool::enqueue(F&& f)
  ^


This message is emitted by outdated compilers that lack sufficient C++11 
support. What compiler did you use? If gcc: was the '-std=c++11' flag 
active?


Best
Ulli (VIGRA maintainer)



Bug#813452: [Pkg-pascal-devel] Bug#813452: [Core] Bug#813452: Bug#813452: fpc-3.0 regression in armhf and armel architectures

2016-02-26 Thread Gianfranco Costamagna
Hi

>I'm not sure but if you checkout (untar) a snpashot on abel.debian.org and 
>just run make all it would work.

I did:
wget ftp://ftp.freepascal.org/pub/fpc/snapshot/fixes/source/fpcbuild.zip

unzip fpcbuild.zip
cd fpcsrc
make all.

the builds fails with 

as  -o 
/home/locutusofborg/fpc-3.1~alpha+dfsg/fpcsrc/rtl/units/arm-linux/ucprt0.o 
arm/ucprt0.as
/usr/bin/ppcarm -Ur -Ur -Xs -O2 -n -Fi../inc -Fi../arm -Fi../unix -Fiarm -FE. 
-FU/home/locutusofborg/fpc-3.1~alpha+dfsg/fpcsrc/rtl/units/arm-linux -darm 
-dRELEASE -Us -Sg system.pp
arm.inc(18,2) Error: Illegal assembler style specified "GAS"
system.inc(1824,8) Warning: Implicit string type conversion from 
"RawByteString" to "UnicodeString"


I tried also to patch the debian packaging to work with the latest trunk and 
I'm attaching it)
the packaging didn't change too much, just an arm64 patch deleted, and some 
patch refresh.
amd64 build went fine, so this seems to be an armhf regression.


>Normally you need to checkout the fpcbuild repository and just replace debian 
>folder by the one from our git. If things did not diverge too much it should 
>work.
>I'll see if this works for amd64 and puch the changes.
the problem is on armel and armhf, so I'm trying the latter, that should be 
faster :)
let me know if you have some more fixes to test,

I deleted line 18 on arm.inc and restarted the build.

with the newly shiny built fpc 3.0.1 I did a rebuild of hedgewars on my local 
pbuilder-dist armhf chroot.

same result.

make[1]: Entering directory '/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabihf'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project /hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabihf
Start 1: drillrockets_drill.lua
1/6 Test #1: drillrockets_drill.lua ...***Failed0.33 sec
An unhandled exception occurred at $000C054C:
EInOutError: File not open
$000C054C  WriteLn,  line 467 of /hedgewars-0.9.22-dfsg/hedgewars/uUtils.pas


Start 2: drillrockets_boom.lua
2/6 Test #2: drillrockets_boom.lua ***Failed0.22 sec
An unhandled exception occurred at $000C054C:
EInOutError: File not open
$000C054C  WriteLn,  line 467 of /hedgewars-0.9.22-dfsg/hedgewars/uUtils.pas


Start 3: twothousandmines.lua
3/6 Test #3: twothousandmines.lua .***Failed0.22 sec
An unhandled exception occurred at $000C054C:
EInOutError: File not open
$000C054C  WriteLn,  line 467 of /hedgewars-0.9.22-dfsg/hedgewars/uUtils.pas


Start 4: hellfire_burns.lua
4/6 Test #4: hellfire_burns.lua ...***Failed0.23 sec
An unhandled exception occurred at $000C054C:
EInOutError: File not open
$000C054C  WriteLn,  line 467 of /hedgewars-0.9.22-dfsg/hedgewars/uUtils.pas


Start 5: luaAPI/zoom_get_set.lua
5/6 Test #5: luaAPI/zoom_get_set.lua ..***Failed0.22 sec
An unhandled exception occurred at $000C054C:
EInOutError: File not open
$000C054C  WriteLn,  line 467 of /hedgewars-0.9.22-dfsg/hedgewars/uUtils.pas


Start 6: luaAPI/gravity_get_set.lua
6/6 Test #6: luaAPI/gravity_get_set.lua ...***Failed0.22 sec
An unhandled exception occurred at $000C054C:
EInOutError: File not open
$000C054C  WriteLn,  line 467 of /hedgewars-0.9.22-dfsg/hedgewars/uUtils.pas



0% tests passed, 6 tests failed out of 6

Total Test time (real) =   1.48 sec

The following tests FAILED:
1 - drillrockets_drill.lua (Failed)
2 - drillrockets_boom.lua (Failed)
3 - twothousandmines.lua (Failed)
4 - hellfire_burns.lua (Failed)
5 - luaAPI/zoom_get_set.lua (Failed)
6 - luaAPI/gravity_get_set.lua (Failed)
Errors while running CTest
Makefile:129: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabihf'
dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2


fpc 
Free Pascal Compiler version 3.0.1+dfsg-1 [2016/02/25] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
/usr/bin/fpc-3.0.1 [options]  [options]

so fPIC seems to be *not* fixed in current trunk (unless I did something 
seriously wrong).
Moreover current trunk doesn't build :)

cheers,
HTH

G.

fpc_3.0.1~alpha+dfsg-1.debian.tar.xz
Description: application/xz


Bug#815712: marked as done (ilmbase: FTBFS on many 32-bit arches: testBoxAlgo.cpp:892)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 09:49:33 +
with message-id 
and subject line Bug#815712: fixed in ilmbase 2.2.0-10
has caused the Debian Bug report #815712,
regarding ilmbase: FTBFS on many 32-bit arches: testBoxAlgo.cpp:892
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ilmbase
Version: 2.2.0-3
Severity: normal

Currenly ilmbase fails to build on non-linux arch because of the following 
try-compile. ilmbase checks for an old bug in GNU libc

[...]
//
// Ugly, the mxcsr isn't defined in GNU libc ucontext_t, but
// it's passed to the signal handler by the kernel.  Use
// the kernel's version of the ucontext to get it, see
// 
//

#include 
[...]

This code path is only executed when the following autoconf step fails:

AC_MSG_CHECKING(for fpe support handling)
control_register_support="no"
AC_TRY_COMPILE([
#include 
#include 
],[
ucontext_t ucon;
uint32_t mxcsr = ucon.uc_mcontext.fpregs->mxcsr;
uint16_t cw= ucon.uc_mcontext.fpregs->cwd;

],
AC_DEFINE(ILMBASE_HAVE_CONTROL_REGISTER_SUPPORT) control_register_support=yes)
AC_MSG_RESULT($control_register_support)

If I check online, it appears that ilmbase compile and runs nicely on FreeBSD, 
therefore ucontext.h does not seems linux specific after all:

https://www.freebsd.org/ports/graphics.html#ilmbase-2.2.0


-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (700, 'stable'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ilmbase
Source-Version: 2.2.0-10

We believe that the bug you reported is fixed in the latest version of
ilmbase, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated ilmbase package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 25 Feb 2016 21:18:13 +0100
Source: ilmbase
Binary: libilmbase12 libilmbase-dev
Architecture: source
Version: 2.2.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Description:
 libilmbase-dev - development files for IlmBase
 libilmbase12 - several utility libraries from ILM used by OpenEXR
Closes: 788102 815633 815712
Changes:
 ilmbase (2.2.0-10) unstable; urgency=medium
 .
   * Remove symbols file. Closes: #815633
   * Fix kFreeBSD compilation. Closes: #788102
   * Fix FTBFS on many 32-bit arches. Closes: #815712
Checksums-Sha1:
 7d64a216c97022836ced2f24f6eaade3bc890a54 2065 ilmbase_2.2.0-10.dsc
 5be4e74215b7c1bede3f92edfa7466ce0ef28302 9892 ilmbase_2.2.0-10.debian.tar.xz
Checksums-Sha256:
 e8cbfb0c68fa9d8cfd3787270f819ae7ff227a632d4b280499a9358bbf23f795 2065 
ilmbase_2.2.0-10.dsc
 acae4431a2bf69ec45e1ff21efcb4fc7d08ee81db55d7c24f2d7164eec331875 9892 
ilmbase_2.2.0-10.debian.tar.xz
Files:
 4de3bfcf751bf80a3442e7fde93193e6 2065 libs optional ilmbase_2.2.0-10.dsc
 95befd9dfda833fc2553d3b6c621a8fc 9892 libs optional 
ilmbase_2.2.0-10.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW0B0KAAoJEAFx4YKK4JNFZ38P/jVyZnYreQrq5lcaciOz3xs7
vbPTaTnVDmeUgc4wPPq+MWpnBu9EPISPTGgpjryhFtZlAkbrTImzkhECOJ7D29aF
e0BSS3ZDGwTO5wzHPUPPBtTkK6fReTR7G4OJFtVrwq/IQtQ5W5nAlfbIT7xW/j62
ifIVRpnhBIqWPyb8cX9vFthbjEX4wwIXlf4CTXdSf0BTw6492s8xaRakxjKDu2b5
sfKYBDM3YNqDTvFZfrv1q5RmHalS1pD8Sn4dFfEQdLsnrezfrvbl/dQyiTn5vH5E
qhjlJLnX2FcqV0f/bFJUWjMW5eFpBZ9VdAHftB/nWtLJQcxsq8KMIeewZX0kQNvJ
nbFC3A9bVDacdGCVIDQbADYtTj2UI05IOf1oIOY9I8mAm+dJGYPsemojjMcd5TG0
Z0R4MKrrHefa0o4eKfXPxgiOGNpDzcF5jFyvtd4HWs4mqJx2dHp3wwNcRno1B6WP
Eb2aF37i51sCGC86/NiKRpNDYxzxQmb3f+0U1VgQKYr8N/OFnZIRDPyFzAQZrmQy

Processed: Re: Bug#812488: Alternative chain verification failure after 1024b root CAs removal

2016-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 812488 Alternative chain verification failure after 1024b root CAs 
> removal
Bug #812488 [ca-certificates] libsms-send-perl: After upgrade: Can't send SMS: 
500 Can't connect to api.twilio.com:443 (certificate verify failed)
Bug #812708 [ca-certificates] ca-certificates: on fresh debian install typical 
ssl session fails on Thawte certificates
Changed Bug title to 'Alternative chain verification failure after 1024b root 
CAs removal' from 'libsms-send-perl: After upgrade: Can't send SMS: 500 Can't 
connect to api.twilio.com:443 (certificate verify failed)'
Changed Bug title to 'Alternative chain verification failure after 1024b root 
CAs removal' from 'ca-certificates: on fresh debian install typical ssl session 
fails on Thawte certificates'
> severity 812488 grave
Bug #812488 [ca-certificates] Alternative chain verification failure after 
1024b root CAs removal
Bug #812708 [ca-certificates] Alternative chain verification failure after 
1024b root CAs removal
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812488
812708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#814055: marked as done (has broken binding to libgnutls-deb0.so.28)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 08:19:49 +
with message-id 
and subject line Bug#813078: fixed in haskell-network-protocol-xmpp 0.4.8-3
has caused the Debian Bug report #813078,
regarding has broken binding to libgnutls-deb0.so.28
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-network-protocol-xmpp-dev
Version: 0.4.8-2 in stretch (and 0.4.8-2+b1 in sid)
Severity: grave

Was building a fresh snapshot of annex in stretch and then in sid to run to the
same issue:

[ 91 of 534] Compiling Database.Types   ( Database/Types.hs, 
dist/build/git-annex/git-annex-tmp/Database/Types.o )
: can't load .so/.DLL for: 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/network-protocol-xmpp-0.4.8-AArRa3ialU19Kz62aVPiMC/libHSnetwork-protocol-xmpp-0.4.8-AArRa3ialU19Kz62aVPiMC-ghc7.10.3.so
 (libgnutls-deb0.so.28: cannot open shared object file: No such file or 
directory)
Makefile:27: recipe for target 'git-annex' failed

and indeed so:

# ldd 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/network-protocol-xmpp-0.4.8-AArRa3ialU19Kz62aVPiMC/libHSnetwork-protocol-xmpp-0.4.8-AArRa3ialU19Kz62aVPiMC-ghc7.10.3.so
 | grep gnutls-deb
libgnutls-deb0.so.28 => not found

I am not quite sure why libgnutls-deb0.so  since no package seems to provide 
that one in the archive
https://packages.debian.org/search?suite=sid=all=i386=contents=libgnutls-deb0.so
which I guess should have been just libgnutls.so.whateverversion

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-rc1+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libghc-network-protocol-xmpp-dev depends on:
ii  ghc [libghc-transformers-dev-0.4.2.0-81450]7.10.3-4
ii  libc6  2.21-6
pn  libghc-base-dev-4.8.2.0-0d6d1  
pn  libghc-bytestring-dev-0.10.6.0-9a873   
ii  libghc-gnuidn-dev [libghc-gnuidn-dev-0.2.1-55c71]  0.2.1-4
ii  libghc-gnutls-dev [libghc-gnutls-dev-0.2-e9479]0.2-2
ii  libghc-gsasl-dev [libghc-gsasl-dev-0.3.6-44bf4]0.3.6-2
ii  libghc-libxml-sax-dev [libghc-libxml-sax-dev-0.7.5-5c696]  0.7.5-4
ii  libghc-monads-tf-dev [libghc-monads-tf-dev-0.1.0.2-6cb91]  0.1.0.2-5
ii  libghc-network-dev [libghc-network-dev-2.6.2.1-25f4f]  2.6.2.1-3
ii  libghc-text-dev [libghc-text-dev-1.2.1.3-50bb4]1.2.1.3-2
ii  libghc-xml-types-dev [libghc-xml-types-dev-0.3.6-f0364]0.3.6-3

libghc-network-protocol-xmpp-dev recommends no packages.

Versions of packages libghc-network-protocol-xmpp-dev suggests:
pn  libghc-network-protocol-xmpp-doc   
pn  libghc-network-protocol-xmpp-prof  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: haskell-network-protocol-xmpp
Source-Version: 0.4.8-3

We believe that the bug you reported is fixed in the latest version of
haskell-network-protocol-xmpp, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joachim Breitner  (supplier of updated 
haskell-network-protocol-xmpp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 09:00:16 +0100
Source: haskell-network-protocol-xmpp
Binary: libghc-network-protocol-xmpp-dev libghc-network-protocol-xmpp-prof 
libghc-network-protocol-xmpp-doc
Architecture: source amd64 all
Version: 0.4.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Joachim Breitner 
Description:
 libghc-network-protocol-xmpp-dev - 

Bug#813078: marked as done (git-annex: FTBFS: libgnutls-deb0.so.28: cannot open shared object file: No such file or directory)

2016-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2016 08:19:49 +
with message-id 
and subject line Bug#813078: fixed in haskell-network-protocol-xmpp 0.4.8-3
has caused the Debian Bug report #813078,
regarding git-annex: FTBFS: libgnutls-deb0.so.28: cannot open shared object 
file: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-annex
Version: 5.20151208-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

git-annex fails to build from source in unstable/amd64:

  [..]


  [ 89 of 526] Compiling Types.NumCopies  ( Types/NumCopies.hs, 
dist/build/git-annex/git-annex-tmp/Types/NumCopies.o )
  [ 90 of 526] Compiling Database.Types   ( Database/Types.hs, 
dist/build/git-annex/git-annex-tmp/Database/Types.o )
  : can't load .so/.DLL for: 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/network-protocol-xmpp-0.4.8-AArRa3ialU19Kz62aVPiMC/libHSnetwork-protocol-xmpp-0.4.8-AArRa3ialU19Kz62aVPiMC-ghc7.10.3.so
 (libgnutls-deb0.so.28: cannot open shared object file: No such file or 
directory)
  Makefile:23: recipe for target 'git-annex' failed
  make[1]: *** [git-annex] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160129144930.fV5S4V5awz/git-annex-5.20151208'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


git-annex.5.20151208-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: haskell-network-protocol-xmpp
Source-Version: 0.4.8-3

We believe that the bug you reported is fixed in the latest version of
haskell-network-protocol-xmpp, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joachim Breitner  (supplier of updated 
haskell-network-protocol-xmpp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Feb 2016 09:00:16 +0100
Source: haskell-network-protocol-xmpp
Binary: libghc-network-protocol-xmpp-dev libghc-network-protocol-xmpp-prof 
libghc-network-protocol-xmpp-doc
Architecture: source amd64 all
Version: 0.4.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Joachim Breitner 
Description:
 libghc-network-protocol-xmpp-dev - 
${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-network-protocol-xmpp-doc - 
${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-network-protocol-xmpp-prof - 
${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 813078
Changes:
 haskell-network-protocol-xmpp (0.4.8-3) unstable; urgency=medium
 .
   * Rebuild to pick up new gnutls dependency (Closes: #813078)
Checksums-Sha1:
 2d4dc85417394d3a7aa1f27bdbc5b5424a2e93a0 3127 
haskell-network-protocol-xmpp_0.4.8-3.dsc
 adf97441db406112ead1e4493ea6ff5ecd94f355 2100 
haskell-network-protocol-xmpp_0.4.8-3.debian.tar.xz
 588a8d748ecfc3a0dbe244f99b77791e0bab861b 175934 
libghc-network-protocol-xmpp-dev_0.4.8-3_amd64.deb
 d385b4b24bf16190197d2434f97906ace63f214b 54770 
libghc-network-protocol-xmpp-doc_0.4.8-3_all.deb
 c3b0f8e8e3807860217804f8e9334dfe1309e291 147840 
libghc-network-protocol-xmpp-prof_0.4.8-3_amd64.deb
Checksums-Sha256:
 c4965e80980d6797a904ab302ad18096121a972101fb14d066a027248fcfa985 3127 
haskell-network-protocol-xmpp_0.4.8-3.dsc
 184f499111fff50937af0215d4b704a354ed4d2f9aec161b6e4bbfdb5f1ee269 2100 
haskell-network-protocol-xmpp_0.4.8-3.debian.tar.xz
 02c718d2f7f49462f1e5810ec835b41d2d0073701614a5fc397412358fded05f 175934 
libghc-network-protocol-xmpp-dev_0.4.8-3_amd64.deb
 

Bug#813849: Multiple security issues

2016-02-26 Thread Salvatore Bonaccorso
Hi David,

On Fri, Feb 05, 2016 at 07:08:45PM -0400, David Pr??vot wrote:
> I???ve just noticed that php-dompdf upstream released ???a security-focused
> release that addresses a number of vulnerabilities that can expose your
> system to exploitation.???
> [CVE-2014-5011], [CVE-2014-5012] and [CVE-2014-5013] have been assigned
> to these issues, but I don???t have much input about them.
> 
> I believe we should simply remove this leaf package from Jessie (along
> with php-font-lib that is only used by php-dompdf). I???ll follow up with
> an RM request if the security team agrees with that option.

Given there was no concern reaised about that I think you can go ahead
with the request for removal on the next Jessie point release.

Thanks for your work,

Salvatore


signature.asc
Description: PGP signature


Bug#815906: postfix: upgrade to 3.0.4-3 breaks

2016-02-26 Thread Dominik George
Control: tags -1 + moreinfo

Hi,

> Stopping Postfix Mail Transport Agent: postfix.
> Starting Postfix Mail Transport Agent: postfixcp: cannot overwrite directory 
'/var/spool/postfix/etc/ssl/godaddy.ca' with non-directory
> invoke-rc.d: initscript postfix, action "restart" failed.
> dpkg: error processing package postfix (--configure):
>  subprocess installed post-installation script returned error exit status 10

I cannot reproduce this issue (setting moreinfo on maintainer's behalf because 
of that).

> What I’d like to know is why it duplicates /etc/ssl there, and badly?

Most likely because you are running a component of Postfix in chroot that 
needs to validate certificates.

That said, maybe posting relevant parts of your config might help.

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Mobil: +49-151-61623918

Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)

signature.asc
Description: This is a digitally signed message part.


Processed: Re: postfix: upgrade to 3.0.4-3 breaks

2016-02-26 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #815906 [postfix] postfix: upgrade to 3.0.4-3 breaks
Added tag(s) moreinfo.

-- 
815906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems