date:20160201

Your message dated Mon, 1 Feb 2016 20:38:00 +0100
with message-id <20160201193800.GA2780@klow>
and subject line Re: Bug#805736: subliminal: unusable due to weird dependency 
of stevedore
has caused the Debian Bug report #805736,
regarding subliminal: unusable due to weird dependency of stevedore
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.)


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

subliminal seems to be unusable, possibly due to a weird dependency of
stevedore. Feel free to reassign to python3-stevedore if necessary.

$ subliminal
Traceback (most recent call last):
  File "/usr/bin/subliminal", line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3080, 
in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3066, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3093, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 651, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 952, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 839, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'argparse' distribution was not found 
and is required by stevedore



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

Kernel: Linux 4.2.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 subliminal depends on:
ii  python3 3.4.3-7
ii  python3-subliminal  0.7.4-1

subliminal recommends no packages.

subliminal suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
* Félix Sipma  [160201 19:34]:
> subliminal seems to be unusable, possibly due to a weird dependency
> of stevedore. Feel free to reassign to python3-stevedore if
> necessary.

Hello,

This was indeed bug #809033 which has been fixed in the meantime.

Thanks for this bug report! And my apologies for the delay.

-- 
Etienne Millon--- End Message ---

Bug#812848: marked as done (mailutils: FTBFS: libmu_auth.so: undefined reference to `gnutls_mac_set_priority')

Your message dated Mon, 01 Feb 2016 19:54:10 +
with message-id 
and subject line Bug#812848: fixed in mailutils 1:2.99.99-1
has caused the Debian Bug report #812848,
regarding mailutils: FTBFS: libmu_auth.so: undefined reference to 
`gnutls_mac_set_priority'
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.)


-- 
812848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailutils
Version: 1:2.99.98-2
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,

mailutils fails to build from source in unstable/amd64:

  [..]

  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I.. -I../include  -I../include   -Wdate-time -D_FORTIFY_SOURCE=2 
-DSYSCONFDIR=\"/etc\" -DSITE_VIRTUAL_PWDDIR=\"/etc/domain\" 
-DSITE_CRAM_MD5_PWD=\"/etc/cram-md5.pwd\" -g  -fPIE -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdeclaration-after-statement -ggdb -c 
-o radius.lo radius.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include 
-I../include -Wdate-time -D_FORTIFY_SOURCE=2 -DSYSCONFDIR=\"/etc\" 
-DSITE_VIRTUAL_PWDDIR=\"/etc/domain\" -DSITE_CRAM_MD5_PWD=\"/etc/cram-md5.pwd\" 
-g -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdeclaration-after-statement -ggdb -c radius.c  -fPIC -DPIC -o .libs/radius.o
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I.. -I../include  -I../include   -Wdate-time -D_FORTIFY_SOURCE=2 
-DSYSCONFDIR=\"/etc\" -DSITE_VIRTUAL_PWDDIR=\"/etc/domain\" 
-DSITE_CRAM_MD5_PWD=\"/etc/cram-md5.pwd\" -g  -fPIE -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdeclaration-after-statement -ggdb -c 
-o sql.lo sql.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include 
-I../include -Wdate-time -D_FORTIFY_SOURCE=2 -DSYSCONFDIR=\"/etc\" 
-DSITE_VIRTUAL_PWDDIR=\"/etc/domain\" -DSITE_CRAM_MD5_PWD=\"/etc/cram-md5.pwd\" 
-g -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdeclaration-after-statement -ggdb -c sql.c  -fPIC -DPIC -o .libs/sql.o
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I.. -I../include  -I../include   -Wdate-time -D_FORTIFY_SOURCE=2 
-DSYSCONFDIR=\"/etc\" -DSITE_VIRTUAL_PWDDIR=\"/etc/domain\" 
-DSITE_CRAM_MD5_PWD=\"/etc/cram-md5.pwd\" -g  -fPIE -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdeclaration-after-statement -ggdb -c 
-o tls.lo tls.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include 
-I../include -Wdate-time -D_FORTIFY_SOURCE=2 -DSYSCONFDIR=\"/etc\" 
-DSITE_VIRTUAL_PWDDIR=\"/etc/domain\" -DSITE_CRAM_MD5_PWD=\"/etc/cram-md5.pwd\" 
-g -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdeclaration-after-statement -ggdb -c tls.c  -fPIC -DPIC -o .libs/tls.o
  In file included from tls.c:67:0:
  ../include/mailutils/sys/tls-stream.h:43:3: warning: 'gnutls_session' is 
deprecated [-Wdeprecated-declarations]
 gnutls_session session;
 ^
  tls.c:177:1: warning: 'gnutls_session' is deprecated 
[-Wdeprecated-declarations]
   {
   ^
  tls.c: In function 'initialize_tls_session':
  tls.c:178:3: warning: 'gnutls_session' is deprecated 
[-Wdeprecated-declarations]
 gnutls_session session = 0;
 ^
  tls.c: At top level:
  tls.c:359:1: warning: 'gnutls_transport_ptr' is deprecated 
[-Wdeprecated-declarations]
   _tls_stream_pull (gnutls_transport_ptr fd, void *buf, size_t size)
   ^
  tls.c:374:1: warning: 'gnutls_transport_ptr' is deprecated 
[-Wdeprecated-declarations]
   _tls_stream_push (gnutls_transport_ptr fd, const void *buf, size_t size)
   ^
  tls.c: In function '_tls_server_open':
  tls.c:409:9: warning: 'gnutls_transport_ptr' is deprecated 
[-Wdeprecated-declarations]
   (gnutls_transport_ptr) transport[0],
   ^
  tls.c:410:9: warning: 'gnutls_transport_ptr' is deprecated 
[-Wdeprecated-declarations]
   (gnutls_transport_ptr) transport[1]);
   ^
  tls.c: In function 'prepare_client_session':
  tls.c:440:3: warning: implicit declaration of function 
'gnutls_protocol_set_priority' [-Wimplicit-function-declaration]
 gnutls_protocol_set_priority (sp->session, protocol_priority);
 ^
  tls.c:441:3: warning: implicit declaration of function 
'gnutls_cipher_set_priority' [-Wimplicit-function-declaration]
 gnutls_cipher_set_priority (sp->session,

Bug#813427: fglrx-driver: Updating / installing libfglrx-amdxvba1 fails with a conflict

2016-02-01 Thread John Franklin

Package: fglrx-driver
Version: 1:15.9-4~deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Updating or installing the xvba-va-driver or the libfglrx-amdxvba1 packages, a 
conflict is reported by dpkg and the install fails.


# apt-get install xvba-va-driver
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libfglrx-amdxvba1
The following NEW packages will be installed:
  libfglrx-amdxvba1 xvba-va-driver
0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
Need to get 0 B/4,043 kB of archives.
After this operation, 13.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package libfglrx-amdxvba1:amd64.
(Reading database ... 53857 files and directories currently installed.)
Preparing to unpack .../libfglrx-amdxvba1_1%3a15.9-4~deb8u1_amd64.deb ...
Unpacking libfglrx-amdxvba1:amd64 (1:15.9-4~deb8u1) ...
Selecting previously unselected package xvba-va-driver.
Preparing to unpack .../xvba-va-driver_0.8.0-9_amd64.deb ...
Unpacking xvba-va-driver (0.8.0-9) ...
dpkg: error processing archive 
/var/cache/apt/archives/xvba-va-driver_0.8.0-9_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/xvba_drv_video.so', which 
is also in package libfglrx-amdxvba1:amd64 1:15.9-4~deb8u1
Errors were encountered while processing:
 /var/cache/apt/archives/xvba-va-driver_0.8.0-9_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd   1:14.9+ga14.201-2  amd64 
 events daemon for the non-free ATI/AMD RadeonHD display driver
ii  fglrx-driver   1:15.9-4~deb8u1amd64 
 non-free ATI/AMD RadeonHD display driver
ii  fglrx-modules-dkms 1:14.9+ga14.201-2  amd64 
 dkms module source for the non-free ATI/AMD RadeonHD display driver
ii  glx-alternative-fglrx  0.5.1  amd64 
 allows the selection of FGLRX as GLX provider
ii  libfglrx:amd64 1:15.9-4~deb8u1amd64 
 non-free ATI/AMD RadeonHD display driver (runtime libraries)
ii  libgl1-fglrx-glx:amd64 1:15.9-4~deb8u1amd64 
 proprietary libGL for the non-free ATI/AMD RadeonHD display driver

VGA-compatible devices on PCI bus:
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Temash [Radeon HD 8250/8280G] [1002:983d] (prog-if 00 [VGA 
controller])
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:b208]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: fglrx_pci


DRM and fglrx Informations from dmesg:
[0.00] AGP: No AGP bridge found
[0.00] AGP: Checking aperture...
[0.00] AGP: No AGP bridge found
[0.00] AGP: Node 0: aperture [bus addr 0x-0x01ff] (32MB)
[0.00] AGP: Your BIOS doesn't leave a aperture memory hole
[0.00] AGP: Please enable the IOMMU option in the BIOS setup
[0.00] AGP: This costs you 64MB of RAM
[0.00] AGP: Mapping aperture over RAM [mem 0x9000-0x93ff] 
(65536KB)
[1.817037] Linux agpgart interface v0.103
[3.240461] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, 
Starnberg, GERMANY' taints kernel.
[3.321153] <6>[fglrx] Maximum main memory to use for locked dma buffers: 
3180 MBytes.
[3.321257] <6>[fglrx]   vendor: 1002 device: 983d count: 1
[3.322071] <6>[fglrx] ioport: bar 4, base 0xf000, size: 0x100
[3.323038] <6>[fglrx] Kernel PAT support is enabled
[3.323096] <6>[fglrx] module loaded - fglrx 14.20.7 [Sep  2 2014] with 1 
minors

Xorg X server configuration file status:
-rw-r--r-- 1 root root 684 Aug  4 20:21 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen  0  "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Module"
EndSection

Section "Monitor"
Identifier   "aticonfig-Monitor[0]-0"
Option  "VendorName" "ATI Proprietary Driver"
Option  "ModelName" "Generic Autodetecting Monitor"
Option  "DPMS" "true"
EndSection

Section "Device"
Identifier  "aticonfig-Device[0]-0"
Driver  "fglrx"
BusID   "PCI:0:1:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor"aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport   0 0
Depth 24
EndSubSection
EndSection



No Xorg X server log files found.

Bug script

Bug#813189: [Pkg-openssl-devel] Bug#813189: libio-socket-ssl-perl: FTBFS with current libssl1.0.2: t/startssl-failed.t hangs

2016-02-01 Thread Salvatore Bonaccorso

Hi Kurt,

On Mon, Feb 01, 2016 at 06:44:32PM +0100, Kurt Roeckx wrote:
> On Mon, Feb 01, 2016 at 04:16:52PM +0100, Salvatore Bonaccorso wrote:
> > On Sun, Jan 31, 2016 at 08:34:44PM +0100, Kurt Roeckx wrote:
> > > On Sat, Jan 30, 2016 at 10:51:06PM +0100, Salvatore Bonaccorso wrote:
> > > > 
> > > > FTR, Upstream has released a new version (I have imported in our git
> > > > repo already):
> > > > 
> > > > 2.023 2016/01/30
> > > > - OpenSSL 1.0.2f changed the behavior of SSL shutdown in case the TLS 
> > > > connection
> > > >   was not fully established (commit: 
> > > > f73c737c7ac908c5d6407c419769123392a3b0a9).
> > > >   This somehow resulted in Net::SSLeay::shutdown returning 0 (i.e. keep 
> > > > trying)
> > > >   which caused an endless loop. It will now ignore this result in case 
> > > > the TLS
> > > >   connection was not yet established and consider the TLS connection 
> > > > closed
> > > >   instead.
> > > > 
> > > > But this does not seem to fully resolve the issue yet. When I try to
> > > > build the testsuite still get stuck.
> > > 
> > > So as I understand it, the problem is that the client just sends
> > > crap, the server tells the client it sends crap, but then waits
> > > for the client to properly terminate the question which it never
> > > does?
> > > 
> > > It's at least not behaviour I can reproducing using s_server, the
> > > server actually closes the connection for me.
> > 
> > JFTR, the additional problem is unrelated to the OpenSSL change. I
> > (and as well Gregor) was able to reproduce it in the pbuilder setup
> > when using the default USENETWORK=no (but not if switching to
> > USENETWORK=yes). So #813189 on its own can be considered resolved.
> 
> I'd like to understand what change was needed in
> libio-socket-ssl-perl.  Can you point me to it?
> 
> I'm wondering if we should change something on the OpenSSL side or
> not.

Ack. Here is the change which was applied to IO::Socket::SSL to
workaround the changes in OpenSSL:

https://github.com/noxxi/p5-io-socket-ssl/commit/6e23ee4a433f83f1065bd2467255eba5ee9b1ddd

Thank you for your help and looking into it!

Regards,
Salvatore

Bug#808123: marked as done (lvm2: adding LVM support after the installation makes the machine unbootable)

Your message dated Mon, 1 Feb 2016 20:46:33 +0100
with message-id <20160201194632.ga28...@shell.thinkmo.de>
and subject line Re: Bug#808123: lvm2: adding LVM support after the 
installation makes the machine unbootable
has caused the Debian Bug report #808123,
regarding lvm2: adding LVM support after the installation makes the machine 
unbootable
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.)

-- 
808123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lvm2
Version: 2.02.95-8
Severity: grave

Hello,
we added support for LVM after the installation of the machine, created an LV
and add it to /etc/fstab to mount it at boot. but then the boot process halts at
fsck as it cant find the device in /dev.

upon inspection, the initscript in /etc/rcS.d was created as S26, which start
lng after all the other initialization scripts, and after the S08checkfs
which causes the boot to halt.

moving the S26lvm2 to S05lvm2 (as on other machine where we created the lvm at
installation-time) fixed the issue.

I know it's the wheezy packages, but it's a rather painful bug, which should
be addressed even in oldstable (but I'm not sure if it might apply even on other
releases).

Thanks,
Sandro

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

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
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 ---
On Wed, Dec 16, 2015 at 04:44:41AM -0500, Sandro Tosi wrote:
> Source: lvm2
> Version: 2.02.95-8

This version is from Wheezy, there won't be any changes anymore.  Please
upgrade to something supported.

Bastian

-- 
But Captain -- the engines can't take this much longer!--- End Message ---

Bug#813424: postinst fails hosteddomains and esmtpacceptmailfor.dir

2016-02-01 Thread Anthony DeRobertis

Package: courier-base
Version: 0.75.0-10
Severity: serious

# dpkg --configure -a
Setting up courier-base (0.75.0-10) ...
chown: cannot access ‘/etc/courier/hosteddomains’: No such file or directory
dpkg: error processing package courier-base (--configure):
 subprocess installed post-installation script returned error exit status 1

I'm not sure where that file is supposed to come from, I don't think
I've ever had one.

I touched it in to existance, then got:

# dpkg --configure -a
Setting up courier-base (0.75.0-10) ...
chown: cannot access ‘/etc/courier/esmtpacceptmailfor.dir’: No such file or 
directory
dpkg: error processing package courier-base (--configure):
 subprocess installed post-installation script returned error exit status 1

I don't think had that ever, either. Note that I'm only using the IMAP
server, not the SMTP server. Touching that into existence finally
allowed the postinst to finish. After it finished, I rm'd them.

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

Kernel: Linux 4.3.0-1-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: systemd (via /run/systemd/system)

Versions of packages courier-base depends on:
ii  adduser 3.113+nmu3
ii  courier-authdaemon  0.66.1-1+b1
ii  courier-authlib 0.66.4-2
ii  courier-authlib-userdb  0.66.1-1+b1
ii  debconf [debconf-2.0]   1.5.58
ii  libc6   2.21-7
ii  libcourier-unicode1 1.4-1
ii  libfam0 2.7.0-17.1+b1
ii  libgdbm31.8.3-13.1
ii  libssl1.0.2 1.0.2f-2
ii  lsb-base9.20160110
ii  openssl 1.0.2f-2
ii  perl5.22.1-4

courier-base recommends no packages.

courier-base suggests no packages.

-- Configuration Files:
/etc/courier/shared/index [Errno 13] Permission denied: 
u'/etc/courier/shared/index'

-- debconf information:
  courier-base/maildirpath:
  courier-base/maildir: Maildir
* courier-base/webadmin-configmode: false
* courier-base/certnotice:

Bug#798988: g_slice_set_config: assertion 'sys_page_size == 0' failed

2016-02-01 Thread Stephen Paul Weber

Package: iceweasel
Version: 38.6.0esr-1~deb8u1
Followup-For: Bug #798988

iceweasel on jessie on lemote yeeloong laptop (mips) crashes when trying to 
launch it with:

(process:3226): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Illegal instruction

I installed iceweasel-dbg and ran under gdb which yields:

(process:2684): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
warning: GDB can't find the start of the function at 0x6bada978.

GDB is unable to find the start of the function at 0x6bada978
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x6bada978 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.

Program received signal SIGILL, Illegal instruction.
0x6bada978 in ?? ()
(gdb) bt
#0  0x6bada978 in ?? ()


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: mipsel (mips64)

Kernel: Linux 3.16.0-4-loongson-2f
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iceweasel depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u2
ii  libcairo2 1.14.0-2.1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u4
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-3
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.9-9
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages iceweasel recommends:
ii  gstreamer1.0-libav 1.4.4-2
ii  gstreamer1.0-plugins-good  1.4.4-2

Versions of packages iceweasel suggests:
pn  fonts-mathjax  
pn  fonts-oflb-asana-math  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-2.1
pn  libgnomeui-0   
ii  libgssapi-krb5-2   1.12.1+dfsg-19+deb8u1
pn  mozplugger 

-- no debconf information

Bug#813429: python-numpy: breaks the CI tests of some installed packages

2016-02-01 Thread Ole Streicher

Package: python3-numpy
Version: 1:1.11.0~b2-1
Severity: serious
Forwarded: Yes

The numpy beta release breaks the CI tests of some astrophysics
packages, namely python-astropy, sunpy, and wcsaxes. Upstream bug
reports are here:

https://github.com/numpy/numpy/issues/7161
https://github.com/numpy/numpy/issues/7162
https://github.com/numpy/numpy/issues/7164

Although it is not everywhere clear whether this is a problem of numpy
or the astrophysics packages, I'd ask not to enter testing unless the
problems are resolved by numpy or clarified that the dependent packages
shall fix it.

Would it generally be possible to put beta releases to experimental
instead of unstable?

Best regards

Ole

Bug#808123: closed by Bastian Blank <wa...@debian.org> (Re: Bug#808123: lvm2: adding LVM support after the installation makes the machine unbootable)

2016-02-01 Thread Sandro Tosi

did you at least check this doesnt apply to newer versions?

On Mon, Feb 1, 2016 at 7:51 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the src:lvm2 package:
>
> #808123: lvm2: adding LVM support after the installation makes the machine
> unbootable
>
> It has been closed by Bastian Blank .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Bastian Blank <
> wa...@debian.org> by
> replying to this email.
>
>
> --
> 808123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808123
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Bastian Blank 
> To: 808123-d...@bugs.debian.org
> Cc:
> Date: Mon, 1 Feb 2016 20:46:33 +0100
> Subject: Re: Bug#808123: lvm2: adding LVM support after the installation
> makes the machine unbootable
> On Wed, Dec 16, 2015 at 04:44:41AM -0500, Sandro Tosi wrote:
> > Source: lvm2
> > Version: 2.02.95-8
>
> This version is from Wheezy, there won't be any changes anymore.  Please
> upgrade to something supported.
>
> Bastian
>
> --
> But Captain -- the engines can't take this much longer!
>
> -- Forwarded message --
> From: Sandro Tosi 
> To: Debian Bug Tracking System 
> Cc:
> Date: Wed, 16 Dec 2015 04:44:41 -0500
> Subject: lvm2: adding LVM support after the installation makes the machine
> unbootable
> Source: lvm2
> Version: 2.02.95-8
> Severity: grave
>
> Hello,
> we added support for LVM after the installation of the machine, created an
> LV
> and add it to /etc/fstab to mount it at boot. but then the boot process
> halts at
> fsck as it cant find the device in /dev.
>
> upon inspection, the initscript in /etc/rcS.d was created as S26, which
> start
> lng after all the other initialization scripts, and after the
> S08checkfs
> which causes the boot to halt.
>
> moving the S26lvm2 to S05lvm2 (as on other machine where we created the
> lvm at
> installation-time) fixed the issue.
>
> I know it's the wheezy packages, but it's a rather painful bug, which
> should
> be addressed even in oldstable (but I'm not sure if it might apply even on
> other
> releases).
>
> Thanks,
> Sandro
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
> 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)
>
>


-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#813398: opensmtpd: segfaults when relaying email

2016-02-01 Thread Björn Schümann

OpenSMTPD has an issue about the problem:
https://github.com/OpenSMTPD/OpenSMTPD/issues/650

Bug#808123: closed by Bastian Blank <wa...@debian.org> (Re: Bug#808123: lvm2: adding LVM support after the installation makes the machine unbootable)

2016-02-01 Thread Sandro Tosi

On Mon, Feb 1, 2016 at 8:30 PM, Bastian Blank  wrote:
>
> Hi
>
> Please learn how to quote mails.

are you serious? so maybe you want to learn how to email the submitter
of a bug if you are communicating something to them, so that they dont
have only the close email to work with...

>
> On Mon, Feb 01, 2016 at 08:03:25PM +, Sandro Tosi wrote:
> > did you at least check this doesnt apply to newer versions?
>
> No, I did not.  But as you asked:
>
> | % grep checkfs /etc/init.d/lvm2
> | X-Start-Before:checkfs mountall
> | % ls -al /etc/rcS.d/*lvm2 /etc/rcS.d/*checkfs*
> | lrwxrwxrwx 1 root root 14 Jul 17  2013 /etc/rcS.d/S04lvm2 -> ../init.d/lvm2
> | lrwxrwxrwx 1 root root 20 Jul 17  2013 /etc/rcS.d/S06checkfs.sh -> 
> ../init.d/checkfs.sh

this doesnt prove the bug wont be there in newer versions: did you
install lvm2 after the machine installation?

-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Processed: Re: Bug#813427: fglrx-driver: Updating / installing libfglrx-amdxvba1 fails with a conflict

Processing control commands:

> tag -1 jessie
Bug #813427 [fglrx-driver] fglrx-driver: Updating / installing 
libfglrx-amdxvba1 fails with a conflict
Added tag(s) jessie.

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

Bug#813427: fglrx-driver: Updating / installing libfglrx-amdxvba1 fails with a conflict

Control: tag -1 jessie

On 2016-02-01 20:58, John Franklin wrote:
> Updating or installing the xvba-va-driver or the libfglrx-amdxvba1 packages, 
> a conflict is reported by dpkg and the install fails.

xvba-va-driver has been obsoleted by the updated driver package, which
provides the same functionality. So you should be able to remove tha
xvba-va-driver package while upgrading the fglrx-driver packages (which
will provide the virtual package xvba-va-driver, in case a dependency
needs it).
Looks like I didn't catch that upgrade error beforehand :-(

Andreas

Bug#813421: dbconfig-common: defaults for MariaDB are wrong: debian-sys-maint isn't anymore

2016-02-01 Thread Paul Gevers

Package: dbconfig-common
Version: 2.0.1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

MariaDB changed the way the packages manage the database. MySQL had the
debian-sys-maint user, but MariaDB uses the socket user (root) to manage the
database. The changes in 2.0.1 are therefore wrong when used for MariaDB fresh
installs. This should be fixed before the package can migrate to strech.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWr7INAAoJEJxcmesFvXUKRewH/RSmOEc9pPMw5cQNioHmdlAU
KOHMP9qZSbEJVe5fMjEoH2mKtqmzEsdbnA9UVhafn9bbuVBuEIWNNBcF8/8O0Jn+
hYKl6qQABtOtuLqmfepAhoRz8WTmb4Ssrk+Jjoven+e/haJFHTneprItp6qPIses
KdJb8J71D3BiaRzfnE4Bo5ckwarYT62qYztD/F+TVB6fJGxwzAo+7VChr1bDfd0o
nin5cnfsHEmtGpuCKl4rCJbA0uZcYEqyk1/u8zrsYR37/5uu3rGKq0MyPJANAP3f
hC6wSDME7XltLjMOKKbjOShjd/v7d0oICJrxkeXt8/9W9WiY0yv9uUgTmpmC06Y=
=lknW
-END PGP SIGNATURE-

Processed: dnssec-tools bugs fixed in 2.2-2

Processing commands for cont...@bugs.debian.org:

> fixed 783721 2.2-2
Bug #783721 [dnssec-tools] dnssec-tools: dnssec-signzone behaviour changed; new 
signed zonefiles unparseable by rollerd
Marked as fixed in versions dnssec-tools/2.2-2.
> fixed 811444 2.2-2
Bug #811444 [dnssec-tools] dnssec-tools fails to install: file conflict with 
dependency
Marked as fixed in versions dnssec-tools/2.2-2.
> fixed 642772 2.2-2
Bug #642772 [dnssec-tools] Net::DNS::ZoneFile::Fast.pm fails to parse valid 
zone files
Marked as fixed in versions dnssec-tools/2.2-2.
> fixed 783957 2.2-2
Bug #783957 [dnssec-tools] /usr/sbin/zonesigner: Incrementation failed on 
domains with a number
Marked as fixed in versions dnssec-tools/2.2-2.
> fixed 754704 2.2-2
Bug #754704 [dnssec-tools] rollerd crashes as soon as key rollover is started
Marked as fixed in versions dnssec-tools/2.2-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#811522: proposed RM: jenkins -- RoQA; multiple security issues, FTBFS, unmaintained in Debian

Processing control commands:

> retitle -1 RM: jenkins -- ROM; multiple security issues, FTBFS, unmaintained 
> in Debian
Bug #811522 [jenkins] proposed RM: jenkins -- RoQA; multiple security issues, 
FTBFS, unmaintained in Debian
Changed Bug title to 'RM: jenkins -- ROM; multiple security issues, FTBFS, 
unmaintained in Debian' from 'proposed RM: jenkins -- RoQA; multiple security 
issues, FTBFS, unmaintained in Debian'
> reassign -1 ftp.debian.org
Bug #811522 [jenkins] RM: jenkins -- ROM; multiple security issues, FTBFS, 
unmaintained in Debian
Bug reassigned from package 'jenkins' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #811522 to the same values 
previously set
Ignoring request to alter fixed versions of bug #811522 to the same values 
previously set

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

Bug#811522: proposed RM: jenkins -- RoQA; multiple security issues, FTBFS, unmaintained in Debian

2016-02-01 Thread Emmanuel Bourg

Control: retitle -1 RM: jenkins -- ROM; multiple security issues, FTBFS, 
unmaintained in Debian
Control: reassign -1 ftp.debian.org

Le 19/01/2016 17:11, Ansgar Burchardt a écrit :

> I suggest to remove the package from Debian.  If there are no
> objections, I'll reassign the request to the ftp.debian.org pseudo-
> package later.

Let's do it.

Bug#813087: marked as done (libslf4j-java: FTBFS: Failed to install artifact org.slf4j:slf4j-parent:pom:1.7.14: [..] (Permission denied))

Your message dated Mon, 01 Feb 2016 22:43:29 +
with message-id 
and subject line Bug#813087: fixed in libslf4j-java 1.7.14-2
has caused the Debian Bug report #813087,
regarding libslf4j-java: FTBFS: Failed to install artifact 
org.slf4j:slf4j-parent:pom:1.7.14: [..]  (Permission denied)
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.)


-- 
813087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libslf4j-java
Version: 1.7.14-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,

libslf4j-java fails to build from source in unstable/amd64:

  [..]

  dh_auto_build -- install
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160129090510.1Wae0DTFtJ/libslf4j-java-1.7.14
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20160129090510.1Wae0DTFtJ/libslf4j-java-1.7.14/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160129090510.1Wae0DTFtJ/libslf4j-java-1.7.14/debian/maven-repo
 install -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [INFO] 

  [INFO] Reactor Build Order:
  [INFO] 
  [INFO] SLF4J
  [INFO] SLF4J API Module
  [INFO] SLF4J Simple Binding
  [INFO] SLF4J NOP Binding
  [INFO] SLF4J JDK14 Binding
  [INFO] SLF4J LOG4J-12 Binding
  [INFO] SLF4J JCL Binding
  [INFO] JCL 1.1.1 implemented over SLF4J
  [INFO] Log4j Implemented Over SLF4J
  [INFO] JUL to SLF4J bridge
  [INFO] SLF4J Migrator
  [INFO]
 
  [INFO] 

  [INFO] Building SLF4J 1.7.14
  [INFO] 

  [INFO] 
  [INFO] --- build-helper-maven-plugin:1.8:parse-version (parse-version) @ 
slf4j-parent ---
  [INFO] 
  [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
slf4j-parent ---
  [INFO] Installing 
/home/lamby/temp/cdt.20160129090510.1Wae0DTFtJ/libslf4j-java-1.7.14/pom.xml to 
/home/lamby/temp/cdt.20160129090510.1Wae0DTFtJ/libslf4j-java-1.7.14/debian/maven-repo/org/slf4j/slf4j-parent/1.7.14/slf4j-parent-1.7.14.pom
  [INFO] 

  [INFO] Reactor Summary:
  [INFO] 
  [INFO] SLF4J .. FAILURE [  0.455 
s]
  [INFO] SLF4J API Module ... SKIPPED
  [INFO] SLF4J Simple Binding ... SKIPPED
  [INFO] SLF4J NOP Binding .. SKIPPED
  [INFO] SLF4J JDK14 Binding  SKIPPED
  [INFO] SLF4J LOG4J-12 Binding . SKIPPED
  [INFO] SLF4J JCL Binding .. SKIPPED
  [INFO] JCL 1.1.1 implemented over SLF4J ... SKIPPED
  [INFO] Log4j Implemented Over SLF4J ... SKIPPED
  [INFO] JUL to SLF4J bridge  SKIPPED
  [INFO] SLF4J Migrator . SKIPPED
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.898 s
  [INFO] Finished at: 2016-01-29T09:07:01+01:00
  [INFO] Final Memory: 8M/298M
  [INFO] 

  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install) 
on project slf4j-parent: Failed to install artifact 
org.slf4j:slf4j-parent:pom:1.7.14: 
/home/lamby/temp/cdt.20160129090510.1Wae0DTFtJ/libslf4j-java-1.7.14/debian/maven-repo/org/slf4j/slf4j-parent/1.7.14/slf4j-parent-1.7.14.pom
 (Permission denied) -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the

Processed: Bug#807578 marked as pending

Processing commands for cont...@bugs.debian.org:

> tag 807578 pending
Bug #807578 {Done: Daniel Stender } [afl-clang] 
/usr/bin/afl-clang-fast: strict dependency on clang version not declared
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#807578: marked as pending

tag 807578 pending
thanks

Hello,

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

http://git.debian.org/?p=collab-maint/afl.git;a=commitdiff;h=1e6dc42

---
commit 1e6dc423f23f66d171f90c38b0659567bcd4c77a
Author: Daniel Stender 
Date:   Thu Jan 7 00:33:02 2016 +0100

Imported Debian patch 1.95b-3

diff --git a/debian/changelog b/debian/changelog
index 8b27fa4..81a4d1d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+afl (1.95b-3) unstable; urgency=medium
+
+  * Hardcode current LLVM/clang version in debian/ files and in the
+source (added hardcode-llvm-version.patch) to prevent crash of
+afl-clang-fast because default build-time and runtime version
+differs (Closes: #807578).
+
+ -- Daniel Stender   Thu, 07 Jan 2016 00:33:02 +0100
+
 afl (1.95b-2) unstable; urgency=medium
 
   * Upload to unstable.

Bug#807578: /usr/bin/afl-clang-fast: strict dependency on clang version not declared

On Thu, 7 Jan 2016 01:28:17 +0100 Jakub Wilk  wrote:
> * Daniel Stender , 2016-01-07, 01:00:
> >+  * Hardcode current LLVM/clang version in debian/ files and in the
> >+source (added hardcode-llvm-version.patch) to prevent crash of
> >+afl-clang-fast because default build-time and runtime version
> >+differs (Closes: #807578).
> 
> I'd expect that afl-clang(-fast) uses clang, not clang-X.Y.
> Also, you patched afl-clang-fast, leaving afl-clang unchanged.
> 
> But this is all unnecessary, because the problem is somewhere else:
> 
> > override_dh_gencontrol:
> > dh_gencontrol
> >-debian/dh_clang -p afl-clang
> 
> You were calling dh_clang after dh_gencontrol, which is obviously too late.
> 
> -- 
> Jakub Wilk

I was planning to change hardcode-clang-version.patch to run against and build 
against
clang/llvm 3.7 to get afl for arm64 again (#796343, probably other bugs could 
be resolved by that
move, too), but llvm-3.7 is missing on some other archs currently, so that's 
not an option.

However, I'm going to keep the patch for the next upload although default clang 
doesn't differ
between Unstable and Testing anymore, it could be easily changed when 3.7 gets 
better. Dropping
the patch now and getting it back into charge again later doesn't makes much 
sense.

Anyway, dh_clang has been put into the right place for times hardcoding and 
versioned building
is going to be dropped again. Thanks for the pointer!

DS

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Bug#813419: eclipse-egit: FTBFS: generateScript: Some inter-plug-in dependencies have not been satisfied.

2016-02-01 Thread Emmanuel Bourg

Thank you for the report Chris. I guess this issue was caused by the
libslf4j-java/1.7.14-1 update where I replaced the custom OSGi metadata
with the one used upstream. This changed the Bundle-SymbolicName from
org.slf4j to slf4j.api but I fail to see how to modify eclipse-egit to
use the new name. Any help from an Eclipse expert would be welcome.

Emmanuel Bourg

Bug#813419: eclipse-egit: FTBFS: generateScript: Some inter-plug-in dependencies have not been satisfied.

2016-02-01 Thread Markus Koschany

Am 01.02.2016 um 22:37 schrieb Emmanuel Bourg:
> Thank you for the report Chris. I guess this issue was caused by the
> libslf4j-java/1.7.14-1 update where I replaced the custom OSGi metadata
> with the one used upstream. This changed the Bundle-SymbolicName from
> org.slf4j to slf4j.api but I fail to see how to modify eclipse-egit to
> use the new name. Any help from an Eclipse expert would be welcome.

I intend to work on upgrading Eclipse to the latest upstream release,
most likely starting at the beginning of March. I hope we can replace
the current version before the next release. I guess we shouldn't invest
too much time in fixing those kind of issues as long as we haven't
packaged a newer upstream release yet.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#798712: marked as done (ruby: transitional package ruby-activesupport-2.3 not installable in jessie)

Your message dated Mon, 01 Feb 2016 23:17:08 +
with message-id 
and subject line Bug#798712: fixed in ruby-defaults 1:2.1.5+deb8u2
has caused the Debian Bug report #798712,
regarding ruby: transitional package ruby-activesupport-2.3 not installable in 
jessie
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.)


-- 
798712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby
Version: 1:2.1.5+deb8u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 ruby-activesupport-2.3

Hi,

during a test with piuparts I noticed that the transitional package
ruby-activesupport-2.3 is no longer installable in jessie.
Transitional packages must be installable, otherwise they are pointless.

This is a regression introduced in the fix for #784336 (1:2.1.5+deb8u1)
Probably the Conflicts should have been versioned:
  Conflicts: ruby-activesupport-2.3 (<< 2:4)

The ruby-activesupport-2.3 package was reintroduced as a transitinal one
to fix #768850, i.e. to get rid of the ruby-*-2.3 and ruby-*-3.2 stacks.
Unfortunately this did not cover all the upgrade paths.


>From the attached log (scroll to the bottom...):

0m41.9s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpPOtlWM', 
'apt-get', '-y', 'install', 'ruby-activesupport-2.3=2:4.1.8-1']
0m42.6s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   ruby-activesupport-2.3 : Depends: ruby-activesupport (>= 2:4) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.
0m42.6s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpPOtlWM', 'apt-get', '-y', 'install', 
'ruby-activesupport-2.3=2:4.1.8-1']


Package: ruby
Source: ruby-defaults
Version: 1:2.1.5+deb8u1
Architecture: all
Replaces: irb, rdoc, rubygems
Provides: irb, rdoc, rubygems
Depends: ruby2.1
Suggests: ri, ruby-dev
Conflicts: ruby-activesupport-2.3, ruby-activesupport-3.2
Breaks: apt-listbugs (<< 0.1.6), rbenv (<= 0.4.0-1), ruby-debian (<< 0.3.8+b3), 
ruby-switch (<= 0.1.0)
Description-en: Interpreter of object-oriented scripting language Ruby (default 
version)



cheers,

Andreas


ruby-activesupport-2.3_2:4.1.8-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-defaults
Source-Version: 1:2.1.5+deb8u2

We believe that the bug you reported is fixed in the latest version of
ruby-defaults, 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 798...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-defaults 
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, 28 Jan 2016 11:28:36 -0200
Source: ruby-defaults
Binary: ruby ruby-dev ruby-all-dev libruby libtcltk-ruby ri ruby-full
Architecture: source all
Version: 1:2.1.5+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Antonio Terceiro 
Changed-By: Antonio Terceiro 
Description:
 libruby- Libraries necessary to run Ruby
 libtcltk-ruby - Tcl/Tk interface for Ruby
 ri - Ruby Interactive reference
 ruby   - Interpreter of object-oriented scripting language Ruby (default v
 ruby-all-dev - Ruby development environment (all versions supported in Debian)
 ruby-dev   - Header files for compiling extension modules for Ruby (default ve
 ruby-full  - Ruby full installation (default version)
Closes: 798712
Changes:
 ruby-defaults (1:2.1.5+deb8u2) jessie; urgency=medium
 .
   * ruby: make the conflict on ruby-activesupport-2.3 versioned on (<< 2:4) to
 allow transitional package to be installed (Closes: #798712)

Processed: forwarded 813159

Processing commands for cont...@bugs.debian.org:

> forwarded 813159 https://github.com/regebro/hovercraft/issues/102
Bug #813159 [src:hovercraft] hovercraft: FTBFS: FAIL: test_big 
(hovercraft.tests.test_hovercraft.HTMLTests)
Set Bug forwarded-to-address to 
'https://github.com/regebro/hovercraft/issues/102'.
> thanks
Stopping processing here.

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

Bug#813439: libcore-ocaml-dev: undeclared dependency on libcustom-printf-camlp4-dev

2016-02-01 Thread Aaron M. Ucko

Package: libcore-ocaml-dev
Version: 113.00.00-1
Severity: serious
Justification: Policy 7.2

ocaml-textutils FTBFS:

  ocaml setup.ml -build
  W: Cannot find source file matching module 'textutils' in library textutils
  ocamlfind ocamlopt unix.cmxa -I /usr/lib/ocaml/ocamlbuild 
/usr/lib/ocaml/ocamlbuild/ocamlbuildlib.cmxa -linkpkg myocamlbuild.ml 
/usr/lib/ocaml/ocamlbuild/ocamlbuild.cmx -o myocamlbuild
  /usr/bin/ocamlfind ocamldep -syntax camlp4o -syntax camlp4o -syntax camlp4o 
-package threads -package sexplib.syntax -package sexplib -package 
pa_ounit.syntax -package pa_ounit -package core -modules lib/ascii_table.mli > 
lib/ascii_table.mli.depends
  + /usr/bin/ocamlfind ocamldep -syntax camlp4o -syntax camlp4o -syntax camlp4o 
-package threads -package sexplib.syntax -package sexplib -package 
pa_ounit.syntax -package pa_ounit -package core -modules lib/ascii_table.mli > 
lib/ascii_table.mli.depends
  ocamlfind: Package `custom_printf' not found - required by `core'
  Command exited with code 2.
  E: Failure("Command ''/usr/bin/ocamlbuild' lib/textutils.cma 
lib/textutils.cmxa lib/textutils.a lib/textutils.cmxs -use-ocamlfind -tag 
debug' terminated with error code 10")
  debian/rules:25: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1

The issue appears to be that libcore-ocaml-dev has an undeclared
dependency on libcustom-printf-camlp4-dev.  Could you please take a
look?

Thanks!

Bug#812663: marked as done (debian-policy: FTBFS - nsgmls: Command not found)

Your message dated Tue, 02 Feb 2016 00:05:42 +
with message-id 
and subject line Bug#812663: fixed in debian-policy 3.9.7.0
has caused the Debian Bug report #812663,
regarding debian-policy: FTBFS - nsgmls: Command not found
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.)


-- 
812663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 3.9.6.1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-debian-policy/debian-policy-3.9.6.1'
nsgmls -wall -gues policy.sgml
make[1]: nsgmls: Command not found
Makefile:17: recipe for target 'policy.sgml.validate' failed
make[1]: *** [policy.sgml.validate] Error 127


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


debian-policy-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-policy
Source-Version: 3.9.7.0

We believe that the bug you reported is fixed in the latest version of
debian-policy, 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 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bill Allombert  (supplier of updated debian-policy 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: Mon, 01 Feb 2016 23:03:51 +0100
Source: debian-policy
Binary: debian-policy
Architecture: source all
Version: 3.9.7.0
Distribution: unstable
Urgency: low
Maintainer: Debian Policy List 
Changed-By: Bill Allombert 
Description:
 debian-policy - Debian Policy Manual and related documents
Closes: 106073 555979 666726 765499 770016 797478 799779 812663
Changes:
 debian-policy (3.9.7.0) unstable; urgency=low
 .
   * Policy: refreshed the names of the Policy Editors.
   * Makefile: use gzip -n when compressing generated files.
   * debian/control, Makefile:
  - add missing Build-Depends on sp (opensp). Closes: #812663
  - migrate to openjade and opensp.
   * debian/rules: no more ship libc6-migration.txt. Closes: #797478
   * Policy: Symbolic links must not traverse above the root directory.
 Wording: Andrey Rahmatullin 
 Seconded: Bill Allombert 
 Seconded: Jakub Wilk 
 Seconded: Henrique de Moraes Holschuh 
 Closes: #555979
   * Policy: [9.2.2] document 32-bit UIDs ranges.
 Wording: Matthew Vernon 
 Seconded: Russ Allbery 
 Seconded: Bill Allombert 
 Seconded: Julien Cristau 
 Closes: #765499
   * Policy: [5.1] empty field values in control files are only permitted in
 the debian/control file of a source package.
 Wording:  Bill Allombert 
 Seconded: Henrique de Moraes Holschuh 
 Seconded: Andrey Rahmatullin 
 Closes: #666726
   * Policy: [4.9] debian/rules: required targets must not attempt network
 access.
 Wording:  Bill Allombert 
 Seconded: Andrey Rahmatullin 
 Seconded: Lucas Nussbaum 
 Closes: #770016
   * Policy: [12.3] recommend to ship additional documentation for package 'pkg'
 in a separate package 'pkg-doc' and install it into /usr/share/doc/pkg.
 Wording:  Russ Allbery 
 Seconded: Bill Allombert 
 Seconded: Charles Plessy 
 Closes: #106073
   [ Stefano Zacchiroli ]
   * autopkgtest: new document containing the specification of automatic,
 as-installed (AKA autopkgtest, or DEP-8) package tests
 Closes: #799779
Checksums-Sha1:

Processed: Re: Bug#603995: libwpd-bindings: FTBFS: Collecting from unknown thread. Aborted.

Processing commands for cont...@bugs.debian.org:

> clone 603995 -1
Bug #603995 [src:libwpd-bindings] libwpd-bindings: FTBFS: Collecting from 
unknown thread.  Aborted.
Bug 603995 cloned as bug 813440
> reassign -1 ftp.debian.org
Bug #813440 [src:libwpd-bindings] libwpd-bindings: FTBFS: Collecting from 
unknown thread.  Aborted.
Bug reassigned from package 'src:libwpd-bindings' to 'ftp.debian.org'.
No longer marked as found in versions libwpd-bindings/0.1.0-1.
Ignoring request to alter fixed versions of bug #813440 to the same values 
previously set
> severity -1 normal
Bug #813440 [ftp.debian.org] libwpd-bindings: FTBFS: Collecting from unknown 
thread.  Aborted.
Severity set to 'normal' from 'serious'
> retitle -1 RM: libwpd-bindings/experimental -- ROM; FTBFS, obsolete
Bug #813440 [ftp.debian.org] libwpd-bindings: FTBFS: Collecting from unknown 
thread.  Aborted.
Changed Bug title to 'RM: libwpd-bindings/experimental -- ROM; FTBFS, obsolete' 
from 'libwpd-bindings: FTBFS: Collecting from unknown thread.  Aborted.'
> thanks
Stopping processing here.

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

Bug#603995: libwpd-bindings: FTBFS: Collecting from unknown thread. Aborted.

2016-02-01 Thread Rene Engelhard

clone 603995 -1
reassign -1 ftp.debian.org
severity -1 normal
retitle -1 RM: libwpd-bindings/experimental -- ROM; FTBFS, obsolete
thanks

Hi,

On Wed, Nov 12, 2014 at 09:10:14PM +0100, Andreas Beckmann wrote:
> Nowadays it already fails during the configure step:
> 
> [...]
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for WPDBINDINGS... no
> configure: error: Package requirements (
> libwpd-0.9 >= 0.9.0
> libwpd-stream-0.9 >= 0.9.0
> ) were not met:
> 
> No package 'libwpd-0.9' found
> No package 'libwpd-stream-0.9' found

Yeah.

And looking at http://sourceforge.net/projects/libwpd/files/libwpd-bindings/
it a) is dead b) never was ported to 0.10.

So let's remove it.

Regards,

Rene

Bug#801413: wheezy: update for polarssl's CVE-2015-5291

2016-02-01 Thread Sébastien Delafond

On Jan/31, Guido Günther wrote:
> Uploaded now. Thanks!

Hi Guido,

have you looked into fixing the jessie version (1.3.9-2.1) as well ? If
not, I'll need to look into it later this week, so that a DSA for
CVE-2015-5291 fixes both wheezy and jessie.

Cheers,

--Seb

Processed: [bts-link] source package charybdis

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package charybdis
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #812655 (http://bugs.debian.org/812655)
> # Bug title: charybdis: FTFBS against gnutls 3.4 (implicit declaration of 
> function 'gnutls_certificate_client_set_retrieve_function')
> #  * https://github.com/charybdis-ircd/charybdis/issues/123
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 812655 + fixed-upstream
Bug #812655 [charybdis] charybdis: FTFBS against gnutls 3.4 (implicit 
declaration of function 'gnutls_certificate_client_set_retrieve_function')
Added tag(s) fixed-upstream.
> usertags 812655 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#813415: libvigraimpex5v5: soname bump without package name change

2016-02-01 Thread Andreas Metzler

Package: libvigraimpex5v5
Version: 1.10.0+git20160120.803d5d4-1
Severity: grave
Justification: renders package unusable

(sid)ametzler@argenau:/usr/bin$ hugin
hugin: error while loading shared libraries: libvigraimpex.so.5: cannot open 
shared object file: No such file or directory

Going from 1.10.0+dfsg-11 to 1.10.0+git20160120.803d5d4-1 there is a
soname change without a corresponding package name change. All reverse
dependencies are broken:

1. Uploaded before vigra: The stop running
2. Uploaded after vigra: They are built against the new vigra but
still depend on libvigraimpex5v5. They will stop running if the reach
testing.


(sid)ametzler@argenau:/usr/bin$ for i in 
/var/cache/apt/archives/libvigraimpex5v5_1.10.0+* ; do basename $i ; dpkg 
--contents $i | grep '/usr/lib/l' ; done
libvigraimpex5v5_1.10.0+dfsg-11_amd64.deb
-rw-r--r-- root/root530744 2015-10-02 17:23 
./usr/lib/libvigraimpex.so.5.1.10.0
lrwxrwxrwx root/root 0 2015-10-02 17:23 ./usr/lib/libvigraimpex.so.5 -> 
libvigraimpex.so.5.1.10.0
libvigraimpex5v5_1.10.0+git20160120.803d5d4-1_amd64.deb
-rw-r--r-- root/root543296 2016-01-27 07:30 
./usr/lib/libvigraimpex.so.6.1.10.0
lrwxrwxrwx root/root 0 2016-01-27 07:30 ./usr/lib/libvigraimpex.so.6 -> 
libvigraimpex.so.6.1.10.0

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: [bts-link] source package librsvg

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package librsvg
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #807281 (http://bugs.debian.org/807281)
> # Bug title: crashes rendering SVGs with filters
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=759084
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 807281 + fixed-upstream
Bug #807281 [librsvg2-2] crashes rendering SVGs with filters
Added tag(s) fixed-upstream.
> usertags 807281 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 807281 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Bug#808043: closed by Ben Hutchings <b...@decadent.org.uk> (Re: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error)

2016-02-01 Thread Christian Marillat

reopen 808043
thanks

On 28 janv. 2016 01:36, ow...@bugs.debian.org (Debian Bug Tracking System) 
wrote:

[...]

> On Tue, 15 Dec 2015 15:26:39 +0100 Christian Marillat  
> wrote:
>> Package: src:linux
>> Version: 4.3.1-1
>> Severity: serious
>> 
>> Dear Maintainer,
>> 
>> Since 4.2.6-2 the Powerpc G5 doesn't start with an error 'unknow symbol in 
>> md_mod'
> [...]
>
> This was apparently due to bug #808246 in binutils.  That is now fixed
> and linux has been binNMU'd for powerpc and ppc64el
> (version 4.3.3-7+b1).

As I was saying in my previous e-mail, this bug isn't fixed. So bug
reopened.

Christian

Processed: Re: Bug#808043 closed by Ben Hutchings <b...@decadent.org.uk> (Re: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error)

Processing commands for cont...@bugs.debian.org:

> reopen 808043
Bug #808043 {Done: Ben Hutchings } [src:linux] [powerpc] 
Modules fail to load following toolchain upgrade
Bug reopened
Ignoring request to alter fixed versions of bug #808043 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#813376: dlm: B-D on obsolete package libsystemd-daemon-dev

Package: dlm
Version: 4.0.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package Build-Depends on the obsolete package libsystemd-daemon-dev
that is no longer built (nor provided) by src:systemd. Please adjust
your package to use libsystemd-dev instead.


Andreas

Bug#813262: python-biopython: FTBFS: ApplicationError: Non-zero return code 255 from 'phyml -i Phylip/interlaced2.phy -d aa'

2016-02-01 Thread Peter Cock

On Mon, Feb 1, 2016 at 12:08 PM, Andreas Tille  wrote:
> Hi Peter,
>
> ...
>
> Yes.  BioPython is OK - I need to reassign the bug - probably to
> libhmsbeagle-dev which is possibly not featuring the correct
> dependencies.  I just wanted to investigate the issue before I
> do the reassigning since for the moment it is just the BioPython
> *package* *in* *debian* that fails.

Understood.

> ...
>
> My plan for this years GSoC is to find a student who could add as much
> testing to Debian Med packages as possible.  In this sense BioPython is
> a great test suite since it somehow adds tests to those packages that
> come without one. :-)

Nice idea. We might be able to do that under the Open Bioinformatics
Foundation as a GSoC umbrella organisation if we're accepted into
GSoC this year [I'm not directly involved but am on the OBF board]:

http://mailman.open-bio.org/pipermail/open-bio-l/2016-January/001423.html

The Biopython tests here are generally for our command line tool
wrappers (and often catch changes to their command line API),
and/or checking we can parse the latest output from the command
line tools (Bioinformatics file formats are sadly often fluid).

> Thanks again for getting involved into this bug report.  I think
> I will use the upcoming Debian Med sprint[1] to sort these things
> out.

I hope to come along to another Debian Med sprint next time
one's close to home :)

Thanks,

Peter

Bug#813377: ocserv: B-D on obsolete package libsystemd-daemon-dev

Source: ocserv
Version: 0.10.10-1
Severity: serious
Justification: fails to build from source

Hi,

your package Build-Depends on the obsolete package libsystemd-daemon-dev
that is no longer built (nor provided) by src:systemd. Please adjust
your package to use libsystemd-dev instead.


Andreas

Bug#813262: python-biopython: FTBFS: ApplicationError: Non-zero return code 255 from 'phyml -i Phylip/interlaced2.phy -d aa'

2016-02-01 Thread Andreas Tille

Hi Peter,

On Mon, Feb 01, 2016 at 01:25:05PM +, Peter Cock wrote:
> > My plan for this years GSoC is to find a student who could add as much
> > testing to Debian Med packages as possible.  In this sense BioPython is
> > a great test suite since it somehow adds tests to those packages that
> > come without one. :-)
> 
> Nice idea. We might be able to do that under the Open Bioinformatics
> Foundation as a GSoC umbrella organisation if we're accepted into
> GSoC this year [I'm not directly involved but am on the OBF board]:
> 
> http://mailman.open-bio.org/pipermail/open-bio-l/2016-January/001423.html

I admit I do not care about the umbrella if at least the work gets done.
;-)  Usually Debian is accepted in GSoC so if OBF has problems to get
accepted but can help finding a student with a bioinformatics background
this could be of some advantage.

> The Biopython tests here are generally for our command line tool
> wrappers (and often catch changes to their command line API),
> and/or checking we can parse the latest output from the command
> line tools (Bioinformatics file formats are sadly often fluid).

Yes, I perfectly understand and that's very convinient also for the
Debian packaging.

> > Thanks again for getting involved into this bug report.  I think
> > I will use the upcoming Debian Med sprint[1] to sort these things
> > out.
> 
> I hope to come along to another Debian Med sprint next time
> one's close to home :)

You would be perfectly welcome at our Sprint!  What countries / geo
coordinates would be acceptable for you?  We are planing to have a
Sprint at Sanger ... 

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#813270: python3 stuff but no python3 dependency

2016-02-01 Thread Georges Khaznadar

Hello Mattia,

thank you for your fast notice!

Mattia Rizzolo a écrit :
> Source: pysatellites
> Version: 2.2-2
> Severity: serious
> 
> Dear maintainer,
> 
> It seems to me that python-satellites builds python3 stuff, it has
> several py3 dependencies, etc.
> But there is no python3 direct dependency, which is bad.
> That's because you're using ${python:Depends} instead of
> ${python3:Depends}.  I read in #813219 that you used to not be able to
> understand what it generated, feel free to ask I'm happy to explain it
> :)

I did not keep the file substvars which was made, but I remember that at
some time a dependency on a non-existing package had been automatically
generated. If I see something similar in the future, I shall try to
trigger the same error with a minimal package and report a bug.

Now I replaced ${python:Depends} by ${python3:Depends}, then launched
"debuild", and had a look at the file python-satellites.substvars
this file contains:
--8<
misc:Depends=
misc:Pre-Depends=
--8<

Should I raise a bug report? the environment used was not a chroot made
by pbuilder, and dh-python came in version 2.20150826.

> and btw, you build-depend on python2 packages, maybe you are more
> interested in python3 ones? (or at this point thet are maybe useless and
> just remove them?)

You are right! I only need the package which contains pyuic4 to convert
user interfaces designed with Qt designer.


> Then, the package name does not follow the debian python policy,
> according to which you should name it python3-satellites, the name you
> are currently using kind of imply python2 stuff (but this point is just
> a remark, the actual bug is about the first paragraph).

humm.. As this package does not create libraries very useful for other
developers, I suppose that it might as well be treated as a private
library: so the scripts should rather go to /usr/share/pysatellites, and
the package should just be named "pysatellites" rather than
python3-satellites. What do you think about it?

Best regards,   Georges

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Processed: [bts-link] source package src:python-axiom

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:python-axiom
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #810643 (http://bugs.debian.org/810643)
> # Bug title: python-axiom: FTBFS: 
> test_sequence.TestSequenceOperations.test_slices: Second list contains 3 
> additional elements.
> #  * https://github.com/twisted/axiom/issues/56
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 810643 + fixed-upstream
Bug #810643 [src:python-axiom] python-axiom: FTBFS: 
test_sequence.TestSequenceOperations.test_slices: Second list contains 3 
additional elements.
Added tag(s) fixed-upstream.
> usertags 810643 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 810643 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#813400: marked as done (libcglib-nodep-java: fails to upgrade from 'testing' - trying to overwrite /usr/share/java/cglib-nodep.jar)

Your message dated Mon, 01 Feb 2016 17:19:35 +
with message-id 
and subject line Bug#813400: fixed in cglib 3.2.0-2
has caused the Debian Bug report #813400,
regarding libcglib-nodep-java: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/java/cglib-nodep.jar
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.)


-- 
813400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcglib-nodep-java
Version: 3.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libcglib-nodep-java.
  Preparing to unpack .../libcglib-nodep-java_3.2.0-1_all.deb ...
  Unpacking libcglib-nodep-java (3.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcglib-nodep-java_3.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/java/cglib-nodep.jar', which is also in 
package libcglib-java 2.2.2+dfsg2-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libcglib-nodep-java_3.2.0-1_all.deb


cheers,

Andreas


libcglib-java=2.2.2+dfsg2-2_libcglib-nodep-java=3.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cglib
Source-Version: 3.2.0-2

We believe that the bug you reported is fixed in the latest version of
cglib, 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.
Emmanuel Bourg  (supplier of updated cglib 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: Mon, 01 Feb 2016 17:44:26 +0100
Source: cglib
Binary: libcglib-java libcglib-nodep-java libcglib-java-doc
Architecture: source all
Version: 3.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libcglib-java - Code generation library for Java
 libcglib-java-doc - Code generation library for Java (documentation)
 libcglib-nodep-java - Code generation library for Java (without dependencies)
Closes: 813400
Changes:
 cglib (3.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Specify that libcglib-nodep-java breaks/replaces libcglib-java (<< 3.0)
 (Closes: #813400)
Checksums-Sha1:
 23224bc0150b5f193464802d625f2e8fbcf5e1ad 2138 cglib_3.2.0-2.dsc
 d2390afe77f108f8a3533e19996c1701f77756af 5448 cglib_3.2.0-2.debian.tar.xz
 a67162b5a2013ac6172a097efe477731e1858493 141372 
libcglib-java-doc_3.2.0-2_all.deb
 a842389a2baac0d19e574de053733e7bb6c28015 257180 libcglib-java_3.2.0-2_all.deb
 8b57ea106a8da12d74c949a2b98c23d33b3fa83f 305340 
libcglib-nodep-java_3.2.0-2_all.deb
Checksums-Sha256:
 68687ffc6494bd54cc059a9bb876e89946e83754d32723b1a8e6c07c53c53000 2138 
cglib_3.2.0-2.dsc
 277c7038473ef2045a183b064f87ea704eb04c4add2012d80d1402f8d63fa97b 5448 
cglib_3.2.0-2.debian.tar.xz
 710807d60a7475de3b07da9a5d388efe77ad224b29c461cae22bc6a8a8b0516f 141372 
libcglib-java-doc_3.2.0-2_all.deb
 4884dbfb3cbf75e564ada43ce374e6ec0ac4f5ab2ba4c56cfe50845aa825381f 257180 
libcglib-java_3.2.0-2_all.deb
 a2f99efe29042587cd932b3d80549e2831b94fed18b3bbf7023911ed2d356b12 305340 
libcglib-nodep-java_3.2.0-2_all.deb
Files:
 9f911de0857be67f822385fdbff9bc7b 2138 java optional cglib_3.2.0-2.dsc
 a5258ce0f3bfcb972dfb38ee2e0dcaeb 5448 java optional cglib_3.2.0-2.debian.tar.xz
 3ba147508c06389dba63769062ccc975 141372 doc optional 
libcglib-java-doc_3.2.0-2_all.deb
 6af230f11bb9c482afe20f11f6b0dae9 257180 java optional 
libcglib-java_3.2.0-2_all.deb
 b3d29232ce4ef35ffe9fb7573245bfe4

Bug#813270: marked as done (python3 stuff but no python3 dependency)

Your message dated Mon, 01 Feb 2016 17:36:34 +
with message-id 
and subject line Bug#813270: fixed in pysatellites 2.2-3
has caused the Debian Bug report #813270,
regarding python3 stuff but no python3 dependency
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.)


-- 
813270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysatellites
Version: 2.2-2
Severity: serious

Dear maintainer,

It seems to me that python-satellites builds python3 stuff, it has
several py3 dependencies, etc.
But there is no python3 direct dependency, which is bad.
That's because you're using ${python:Depends} instead of
${python3:Depends}.  I read in #813219 that you used to not be able to
understand what it generated, feel free to ask I'm happy to explain it
:)

and btw, you build-depend on python2 packages, maybe you are more
interested in python3 ones? (or at this point thet are maybe useless and
just remove them?)

Then, the package name does not follow the debian python policy,
according to which you should name it python3-satellites, the name you
are currently using kind of imply python2 stuff (but this point is just
a remark, the actual bug is about the first paragraph).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pysatellites
Source-Version: 2.2-3

We believe that the bug you reported is fixed in the latest version of
pysatellites, 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.
Georges Khaznadar  (supplier of updated pysatellites 
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: Mon, 01 Feb 2016 16:42:11 +0100
Source: pysatellites
Binary: python-satellites
Architecture: source all
Version: 2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 python-satellites - simulates the launching of satellites
Closes: 813270
Changes:
 pysatellites (2.2-3) unstable; urgency=medium
 .
   * replaced python:Depends by python3:Depends. Closes: #813270
   * removed build-dependencies on python2 stuff, and on xsltproc stuff since
 the manpage is built in advance.
Checksums-Sha1:
 7a919d0c1a5d1aaee59ccf32f49ea0e9c0f88656 1750 pysatellites_2.2-3.dsc
 35cffc1210998d168dd9449f35b75e1fe98c8a8c 2924 pysatellites_2.2-3.debian.tar.xz
 20d08048686d9f42844e25810726a8695769fe64 2480364 
python-satellites_2.2-3_all.deb
Checksums-Sha256:
 ee4a0d5562c0ee310e3458ad5b79e0daec70afaa6bb4b9db45f63feb9139942e 1750 
pysatellites_2.2-3.dsc
 2b6f803f4f54413c2b1907e27384b7dc122edbec1bd3427ada46c240b2b054fd 2924 
pysatellites_2.2-3.debian.tar.xz
 030f277f3387215b067a35a651fed59b552904b00b88fda8f77015e69bfc4885 2480364 
python-satellites_2.2-3_all.deb
Files:
 98f4c6258bc4a6db63e9103ae38618db 1750 python extra pysatellites_2.2-3.dsc
 4a272accb404b3d3d58b22a40c902cb3 2924 python extra 
pysatellites_2.2-3.debian.tar.xz
 fb6316601f99c75beef7bbca8145d4f8 2480364 python extra 
python-satellites_2.2-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVq+CYxwoFpBxNq45AQhyOg//VtZwq15u106BD5M2pCcTdT7kd/BHID8C
du42+e6Vi0IFwytgGkfuROXNwCSG2sdO1WEMnZgIwQv8Wn3SJE6uXz37QO/bfTnp
cXhUZnrTLqjMu41EolsGqocT8xGRMRCDCeidSw4X/suslzG/oL5FWvmzQXqCBuqp
JJWjbsdKjqy72VtSY7+HdKAtL4UQgIoQDkei3A0ep5lkbPpqoz8lvtzbIq1YuAqK
2Frj5+5ztgcAA28/CCIIAcwNL+lJf71qMJJdNwfULUDiJCKd/i+euwu59mEwwL71
CPV9tbw9qcLr0ARVTLL1TNvcr6D0aHwa3yEDEUL4AZyCyI/b2CF1YDENVGsdE5Sj
VY02zGMvARhKundITRkQsDie88vCwYNpe/VRTFCRjGSHbL4xoo9ociCRIselm2oO
/lIQoIrlU9J1QhFHIiGLzFWji5Q2zmF1wN6LApgQvNOQfT668/q6E1ldsxZ6UySd

Bug#813339: isc-dhcp-server: Update to 4.3.3-7 today makes isc-dhcp-server unable to work

2016-02-01 Thread Russel Winder

On Sun, 31 Jan 2016 21:33:35 +0100 Sven Hartge 
wrote:
[…]
> 
> The variable to define which interface the dhcpd runs on has changed,
> but unfortunately the contents of /etc/default/isc-dhcp-server were
not
> adapted at the same time.
> 
> You need to change
> 
> INTERFACES="..."
> 
> to
> 
> INTERFACESv4="..."
> 
> to be able to start the DHCP server again.
> 
> And I guess this bug is not just important but of severity "grave".

I tried:

INTERFACESv4=""

on the assumption of interface discovery as used to happen, but this
didn't work.

INTERFACESv4="eth0"

does however work fine. I have a DHCP server again. :-) Thanks for
pointing me to the solution, and quickly, it is very much appreciated. 

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder



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

Bug#813262: python-biopython: FTBFS: ApplicationError: Non-zero return code 255 from 'phyml -i Phylip/interlaced2.phy -d aa'

2016-02-01 Thread Andreas Tille

Hi Peter,

On Mon, Feb 01, 2016 at 11:25:13AM +, Peter Cock wrote:
> I spotted this via an automated @DebianBug Twitter posting:
> https://twitter.com/DebianBug/status/693569490655776768
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813262

Thanks a lot for watching!

> Andreas has dealt with other issues like this in the past, but
> I wanted to make this explicit on the issue tracker:
> 
> This isn't a problem in Biopython itself,

Yes.  BioPython is OK - I need to reassign the bug - probably to
libhmsbeagle-dev which is possibly not featuring the correct
dependencies.  I just wanted to investigate the issue before I
do the reassigning since for the moment it is just the BioPython
*package* *in* *debian* that fails.

> but a Biopython test
> case calling phyml indicates there is a problem with the Debian
> phyml package.
> 
> Should the phyml GPU problem be filed under the phyml Debian
> package, perhaps adding a simple basic check to its tests?:
> 
> phyml -i Phylip/interlaced2.phy -d aa

I agree that we could add this check even to the phyml package.

> This sample input test file is available here, also used as an example
> in the EMBOSS suite:
> 
> https://github.com/biopython/biopython/blob/master/Tests/Phylip/interlaced2.phy
> 
> I suspect any PHYLIP input file would work for checking the
> binary works and might help catch this apparent compilation
> issue earlier. Looking over the upstream Makefile it was not
> obvious that there is any testing like this being done at the
> moment, but there are example files likely to be useful for
> adding such a test:
> 
> https://github.com/stephaneguindon/phyml

My plan for this years GSoC is to find a student who could add as much
testing to Debian Med packages as possible.  In this sense BioPython is
a great test suite since it somehow adds tests to those packages that
come without one. :-)

Thanks again for getting involved into this bug report.  I think
I will use the upcoming Debian Med sprint[1] to sort these things
out.

Kind regards

Andreas.

[1] https://wiki.debian.org/Sprints/2016/DebianMed2016

-- 
http://fam-tille.de

Bug#813361: doxygen: FTBFS on amd64 due to wrong version of flex

2016-02-01 Thread John Paul Adrian Glaubitz

Source: doxygen
Version: 1.8.9.1-6
Severity: serious
Justification: fails to build from source

Hi!

doxygen currently fails to build from source with the following error message:

/usr/bin/flex -i -PvhdlcodeYY -t vhdlcode.l | python3 increasebuffer.py > 
../generated_src/doxygen/vhdlcode.cpp
g++ -c -pipe -fno-exceptions -D_LARGEFILE_SOURCE -Wall -W -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -I../generated_src/doxygen -I../src 
-I../qtools -I../libmd5 -I../vhdlparser
-I/usr/lib/llvm-3.6/include -I/usr/include -o ../objects/doxygen/vhdlcode.o 
../generated_src/doxygen/vhdlcode.cpp
vhdlcode.l:1618:2: error: #error "You seem to be using a version of flex newer 
than 2.5.4 but older than 2.5.33.
These versions do NOT work with doxygen! Please use version <=2.5.4 or >=2.5.33 
or expect things to be parsed wrongly!"
 #endif
  ^

This was tested on amd64.

When addressing this bug, please also consider fixing #808766 [1].

Cheers,
Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808766

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#813262: python-biopython: FTBFS: ApplicationError: Non-zero return code 255 from 'phyml -i Phylip/interlaced2.phy -d aa'

2016-02-01 Thread Peter Cock

Hi all,

I spotted this via an automated @DebianBug Twitter posting:
https://twitter.com/DebianBug/status/693569490655776768
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813262

Andreas has dealt with other issues like this in the past, but
I wanted to make this explicit on the issue tracker:

This isn't a problem in Biopython itself, but a Biopython test
case calling phyml indicates there is a problem with the Debian
phyml package.

Should the phyml GPU problem be filed under the phyml Debian
package, perhaps adding a simple basic check to its tests?:

phyml -i Phylip/interlaced2.phy -d aa

This sample input test file is available here, also used as an example
in the EMBOSS suite:

https://github.com/biopython/biopython/blob/master/Tests/Phylip/interlaced2.phy

I suspect any PHYLIP input file would work for checking the
binary works and might help catch this apparent compilation
issue earlier. Looking over the upstream Makefile it was not
obvious that there is any testing like this being done at the
moment, but there are example files likely to be useful for
adding such a test:

https://github.com/stephaneguindon/phyml

Thanks,

Peter
(Biopython developer)

Processed: user debian...@lists.debian.org, usertagging 809766, found 812951 in 8.4.0+dfsg~rc2-4 ...

Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 809766 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> found 812951 8.4.0+dfsg~rc2-4
Bug #812951 [gitlab] gitlab: fails to install: gitlab.postinst: sudo: not found
Marked as found in versions gitlab/8.4.0+dfsg~rc2-4.
> found 792176 5.5.46-0+deb8u1
Bug #792176 [mysql-server-5.5] mysql-server-5.5: uninstallable in sid
Marked as found in versions mysql-5.5/5.5.46-0+deb8u1.
> usertags 797776 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 797776 + python3-gpgme
Bug #797776 [src:pygpgme] pygpgme: FTBFS: Ran 55 tests in 54.866s: FAILED 
(failures=2, errors=2)
Added indication that 797776 affects python3-gpgme
> usertags 808455 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 808455 + libroboptim-core-dev
Bug #808455 [src:roboptim-core] roboptim-core: FTBFS: dh_install: 
libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), 
aborting
Added indication that 808455 affects libroboptim-core-dev
> usertags 809998 piuparts
There were no usertags set.
Usertags are now: piuparts.
> tags 805933 + moreinfo unreproducible
Bug #805933 [libinsighttoolkit4-dev] FTBFS on recent systems
Added tag(s) unreproducible and moreinfo.
> usertags 797623 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 797623 + libsaml8
Bug #797623 {Done: Ferenc Wágner } [src:opensaml2] opensaml2: 
transition needed for g++-5 ABIs
Added indication that 797623 affects libsaml8
> tags 813261 + sid stretch
Bug #813261 [src:jhdf] jhdf: FTBFS: checking dependencies for HDF5 library... 
configure: error:  HDF5 library needs SZIP, SZIP not defined.
Added tag(s) stretch and sid.
> tags 813138 + sid stretch
Bug #813138 [python-gnutls] python-gnutls: Still depends on libgnutls-deb0-28 
instead of libgnutls30
Added tag(s) sid and stretch.
> notfixed 796440 0.2.3-3
Bug #796440 {Done: Jérémy Bobbio } [src:libldm] libldm: 
FTBFS: Package 'librt', required by 'devmapper', not found
No longer marked as fixed in versions 0.2.3-3.
> fixed 796440 0.2.3-4
Bug #796440 {Done: Jérémy Bobbio } [src:libldm] libldm: 
FTBFS: Package 'librt', required by 'devmapper', not found
Marked as fixed in versions libldm/0.2.3-4.
> found 813144 2.25.90.20151209-1+6.5
Bug #813144 [binutils-mingw-w64-i686] g++-mingw-w64-i686: unimplemented 
function libstdc++-6.dll._ZNSt8ios_base4InitC1Ev
There is no source info for the package 'binutils-mingw-w64-i686' at version 
'2.25.90.20151209-1+6.5' with architecture ''
Unable to make a source version for version '2.25.90.20151209-1+6.5'
Marked as found in versions 2.25.90.20151209-1+6.5.
> tags 813359 + sid stretch
Bug #813359 [src:xserver-xorg-input-aiptek] xserver-xorg-input-aiptek: FTBFS: 
xf86Aiptek.c:296:17: error: too many arguments to function 'xf86PostKeyEvent'
Added tag(s) stretch and sid.
> found 813143 7u91-2.6.3-1
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Marked as found in versions openjdk-7/7u91-2.6.3-1.
> found 805608 1.5-2
Bug #805608 {Done: Matthias Klose } [icedtea-7-plugin] Icedtea 
plugin fails to run applets - exception
Marked as found in versions icedtea-web/1.5-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
792176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792176
796440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796440
797623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797623
797776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797776
805608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805608
805933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805933
808455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808455
812951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812951
813138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813138
813143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813143
813144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813144
813261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813261
813359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#813373: rivet: FTBFS on armel/armhf: testsuite failures

Source: rivet
Version: 1.8.3-1.3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

rivet FTBFS on armel and armhf:

https://buildd.debian.org/status/fetch.php?pkg=rivet=armel=1.8.3-1.3=1450143143
https://buildd.debian.org/status/fetch.php?pkg=rivet=armhf=1.8.3-1.3=1450171455

make  check-TESTS
make[3]: Entering directory '/«PKGBUILDDIR»/test'
make[4]: Entering directory '/«PKGBUILDDIR»/test'
PASS: testMath
PASS: testCmp
PASS: testMatVec
PASS: testBoost
FAIL: testCmdLine.sh
../test-driver: line 107: 18058 Aborted "$@" > $log_file 2>&1
XFAIL: testNaN
PASS: testApi

Testsuite summary for Rivet 1.8.3

# TOTAL: 7
# PASS:  5
# SKIP:  0
# XFAIL: 1
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to ri...@projects.hepforge.org

Makefile:872: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/«PKGBUILDDIR»/test'
Makefile:978: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/«PKGBUILDDIR»/test'

Bug#812969: libvmime: FTBFS: net_tls_TLSSession.cpp:120:38: error: 'gnutls_certificate_type_set_priority' was not declared in this scope

2016-02-01 Thread Andreas Metzler

On 2016-02-01 Carsten Schoenert  wrote:
[...]
> Peter Green has submitted a debdiff with a possibly solution that's seen
> below. I'm not a security expert on those used functions inside libvmime
> and found a another solution based on suggestions for upgrading to 3.4
> [1] and created a patch that's appended.
[...]

Hello,

I am not able to do a code review but:
const char certTypePriority[] = { GNUTLS_CRT_X509, 0 };
const char protoPriority[] = { GNUTLS_TLS1, GNUTLS_SSL3, 0 };
const char cipherPriority[] = [list of ciphers]
const char macPriority[] = { GNUTLS_MAC_SHA, GNUTLS_MAC_MD5, 0};

Neither of these look very sane or useful to me. The certtype priority
setting matches the GnuTLS default and the other ones explicitely choose
algoritms that do not look like a improvement. (SSLv3, seriously?)

I think dropping these settings and using
gnutls_set_default_priority() would be a much better notion. This way
you would simply rely on the "sane and safe choice" from GnuTLS
instead of trying to reinvent the wheel.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#812877: gajim crashes at start

2016-02-01 Thread Norbert Tretkowski

Am 02.02.2016 um 08:06 schrieb Thuban:
>> Am 27.01.2016 um 15:05 schrieb xavier cartron:
>> I'm not able to reproduce this, neither on jessie, nor on sid. Have you
>> done some configuration between deleting the directory and restarting Gajim?
> 
> No, i didn't do anything special.
> 
> For information, I tried to run gajim in another desktop environment
> (fluxbox instead of xfce) and everything seems to work properly. I can't
> figure out how the DE could disturb gajim...

Ok, I'll try to reproduce it in a VM running jessie with xfce within the
next days...


Regards
Norbert



signature.asc
Description: OpenPGP digital signature

Bug#805124: marked as done (trafficserver: FTBFS on ppc64el: Uses -mcx16)

Your message dated Tue, 02 Feb 2016 07:35:26 +
with message-id 
and subject line Bug#805124: fixed in trafficserver 6.1.0-1
has caused the Debian Bug report #805124,
regarding trafficserver: FTBFS on ppc64el: Uses -mcx16
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.)


-- 
805124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trafficserver
Version: 6.0.0-2
Severity: serious
Control: block 797926 by -1

Hi,

Your package is failing to build on ppc64el.  It looks like this
is the error:
configure:25484: cc -c -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -std=gnu99 -pipe -Wall 
-feliminate-unused-debug-symbols -fno-strict-aliasing -mcx16 
-D_FORTIFY_SOURCE=2 -Dlinux -D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 
-D_GNU_SOURCE -D_REENTRANT -D__STDC_LIMIT_MACROS=1 -D__STDC_FORMAT_MACROS=1 
-DOPENSSL_NO_SSL_INTERN -I/usr/include/tcl8.6 -I/usr/include/libxml2 conftest.c 
>&5
cc: error: unrecognized command line option '-mcx16'

A full log can be seen at:
https://buildd.debian.org/status/fetch.php?pkg=trafficserver=ppc64el=6.0.0-2=1446769250


Kurt
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 6.1.0-1

We believe that the bug you reported is fixed in the latest version of
trafficserver, 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 805...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated trafficserver 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: Tue, 02 Feb 2016 12:18:10 +0800
Source: trafficserver
Binary: trafficserver trafficserver-experimental-plugins trafficserver-dev
Architecture: source
Version: 6.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Arno Töll 
Changed-By: Aron Xu 
Description:
 trafficserver - fast, scalable and extensible HTTP/1.1 compliant caching proxy 
se
 trafficserver-dev - Apache Traffic Server Software Developers Kit (SDK)
 trafficserver-experimental-plugins - experimental plugins for Apache Traffic 
Server
Closes: 805124
Changes:
 trafficserver (6.1.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Use -mcx16 on x86 platforms only (Closes: #805124)
Checksums-Sha1:
 2ff34b22aac21a29a7eec3c029835ea82a6058c9 2138 trafficserver_6.1.0-1.dsc
 033236f5bf845bba454fd74a948a931ae2f08f18 7850685 
trafficserver_6.1.0.orig.tar.bz2
 a49409cc7a0ee8b9e6c99ab702427c546822b4e8 18452 
trafficserver_6.1.0-1.debian.tar.xz
Checksums-Sha256:
 1bcaeee5cb94633d43f84d42d2cb0392829c769f58248395bbf6e788d305ad9f 2138 
trafficserver_6.1.0-1.dsc
 69878884df18566dd328b83ac82e4a615f8e3f076c9623b0b9d031d58c002774 7850685 
trafficserver_6.1.0.orig.tar.bz2
 88bf54a7c032ef454446a69985d8f8e3153e299096e4b7e4f78bca2ca9829387 18452 
trafficserver_6.1.0-1.debian.tar.xz
Files:
 5f2aa693ddce73de8e574470b3356e3a 2138 web optional trafficserver_6.1.0-1.dsc
 9297aba67bafb531d8e74ba709675433 7850685 web optional 
trafficserver_6.1.0.orig.tar.bz2
 636b3c2bfcbb92f74072ed2bc46cf70c 18452 web optional 
trafficserver_6.1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWsFiKAAoJEPbsVcVkKA0e+RQIAJjj2O5A7dnbm4dfsPbBTfWS
UBsQm9GzZ/ypubBiuenPF5X2L9/L5yH4TISr6X7m7nZhEcoEmfpW5Nux57EJ3/yx
2/aDZP9bPm/BvU1EhiDP0cYlucUkcWWi8KA2cfbhpN7TEyIIOkyxH9vPn3G6iBlJ
V06MgH1oEqqAteF9cvAuFXB2jczFLpO86i1BrgHxSeEINlXasym8UmNfw5aR3xSo
ohLjZDJAJJOe+I29jpfZVM6ludO1xZWSzdGNwaf5T2zLCHEMRTvyIo0DNCFuOWhB
fk0Gx05SRGwwvwXC+tk6VTQablhkvxrs0VtJvzuy8owzXTC8JGwo9GBra01elGE=
=K2Qy
-END PGP SIGNATURE End Message ---

Processed: severity of 789514 is normal, severity of 806666 is normal, severity of 810084 is normal ...

Processing commands for cont...@bugs.debian.org:

> severity 789514 normal
Bug #789514 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: jaffl -- ROM; superseded by jnr-ffi
Severity set to 'normal' from 'serious'
> severity 80 normal
Bug #80 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: advene -- RoQA; low popcon; depends on legacy libs 
scheduled for removals (gstreamer 0.10)
Severity set to 'normal' from 'serious'
> severity 810084 normal
Bug #810084 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: websvn (RoQA; unmaintained, rc-buggy, inactive upstream, 
alternatives exist)
Severity set to 'normal' from 'serious'
> severity 810251 normal
Bug #810251 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: guayadeque -- RoQA; dead upstream; depends on gstreamer 
0.10
Severity set to 'normal' from 'serious'
> severity 810049 normal
Bug #810049 [ftp.debian.org] override: libcodec2-0.4:libs/optional
Severity set to 'normal' from 'minor'
> thanks
Stopping processing here.

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

Bug#813444: mbtserver: FTBFS with timblserver 1.8

Source: mbtserver
Version: 0.7-3
Severity: serious
Tags: sid
Justification: fails to build from source (but built successfully in the past)

mbtserver FTBFS with timblserver 1.8 that I just moved from experimental
to sid:

/usr/bin/make  all-recursive
make[2]: Entering directory '/build/mbtserver-0.7'
Making all in src
make[3]: Entering directory '/build/mbtserver-0.7/src'
g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 -fopenmp 
-c -o MbtServer.o MbtServer.cxx
g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 -fopenmp 
-c -o MbtServerBase.o MbtServerBase.cxx
MbtServerBase.cxx:35:40: fatal error: timblserver/TimblServerAPI.h: No such 
file or directory
compilation terminated.
Makefile:308: recipe for target 'MbtServerBase.o' failed
make[3]: *** [MbtServerBase.o] Error 1
make[3]: Leaving directory '/build/mbtserver-0.7/src'
Makefile:323: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1

There is a new upstream release 0.10 reported by the watch file and
a new upstream release v3.2.15 on github.


Andreas

Bug#784220: marked as done (gst-plugins-bad0.10: CVE-2015-0797: buffer overflow in the plugin for mp4 playback)

Your message dated Tue, 02 Feb 2016 04:00:32 +
with message-id
and subject line Bug#813254: Removed package(s) from unstable
has caused the Debian Bug report #784220,
regarding gst-plugins-bad0.10: CVE-2015-0797: buffer overflow in the plugin for
mp4 playback
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.)

--
784220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-bad0.10
Version: 0.10.23-7.1
Severity: grave
Tags: security upstream patch
Justification: user security hole
Control: fixed -1 0.10.23-7.1+deb7u2

This is as well for keeping track of this issue in the BTS. In
DSA-3225-1 a buffer overflow in the plugin for mp4 playback was fixed.
For jessie and above the impact is less grave as no browser attack
vector is present. But could you fix this issue as well through a
jessie-pu?

https://security-tracker.debian.org/tracker/CVE-2015-0797
https://www.debian.org/security/2015/dsa-3225

Keeping the severity to RC (unless you dissagree), since
gst-plugins-bad0.10 might be as well a candidate for removal before
the stretch release.

Patch:
https://sources.debian.net/data/main/g/gst-plugins-bad0.10/0.10.23-7.1+deb7u2/debian/patches/buffer-overflow-mp4.patch

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.10.23-8.1+rm

Dear submitter,

as the package gst-plugins-bad0.10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/813254

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#812877: gajim crashes at start

2016-02-01 Thread Norbert Tretkowski

tags 812877 +unreproducible
thanks

Hi Xavier,

Am 27.01.2016 um 15:05 schrieb xavier cartron:
> When starting gajim, it crashes with this error : 
> 
> Traceback (most recent call last):
> File "gajim.py", line 532, in 
> interface = Interface()
> File "/usr/share/gajim/src/gui_interface.py", line 2773, in __init__
> cfg_was_read = parser.read()
> File "/usr/share/gajim/src/common/optparser.py", line 79, in read
> self.update_config(old_version, new_version)
> File "/usr/share/gajim/src/common/optparser.py", line 233, in 
> update_config
> caps_cache.capscache.initialize_from_db()
> File "/usr/share/gajim/src/common/caps_cache.py", line 391, in 
> initialize_from_db
> self._remove_outdated_caps()
> File "/usr/share/gajim/src/common/caps_cache.py", line 403, in 
> _remove_outdated_caps
> self.logger.clean_caps_table()
> File "/usr/share/gajim/src/common/logger.py", line 959, in 
> clean_caps_table
> self.simple_commit(sql)
> File "/usr/share/gajim/src/common/logger.py", line 187, in simple_commit
> self.cur.execute(sql_to_commit)
> sqlite3.OperationalError: no such column: last_seen
> 
> Note that if I delete ~/.config/gajim, it will start normally. But the
> next start, it crashes again.

I'm not able to reproduce this, neither on jessie, nor on sid. Have you
done some configuration between deleting the directory and restarting Gajim?

> Distributor ID:   HandyLinux
> Description:  HandyLinux GNU/Linux 8.3 (jessie)

WTF is HandyLinux? Are you able to reproduce this bug on Debian?


Regards
Norbert



signature.asc
Description: OpenPGP digital signature

Bug#807206: marked as done (hkl: Update build dependencies for GSL 2.x)

Your message dated Tue, 2 Feb 2016 04:36:12 +0100
with message-id <56b0242c.4070...@debian.org>
and subject line Re: hkl: Update build dependencies for GSL 2.x
has caused the Debian Bug report #807206,
regarding hkl: Update build dependencies for GSL 2.x
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.)

-- 
807206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hkl
Version: 4.99.99.1955-1
Severity: normal
Tags: patch

Dear Maintainer,

Please update your package for the ongoing gsl transition (#804246).

The attached patch updates the build dependencies to use libgsl-dev.

This change is required to not pull in GSL 1.x via libgsl0-dev.

Kind Regards,

Bas
diff -Nru hkl-4.99.99.1955/debian/changelog hkl-4.99.99.1955/debian/changelog
--- hkl-4.99.99.1955/debian/changelog	2015-07-15 16:10:16.0 +0200
+++ hkl-4.99.99.1955/debian/changelog	2015-11-22 17:30:38.0 +0100
@@ -1,3 +1,10 @@
+hkl (4.99.99.1955-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+
+ -- Bas Couwenberg   Sun, 22 Nov 2015 17:30:30 +0100
+
 hkl (4.99.99.1955-1) unstable; urgency=medium

   * Imported Upstream version 4.99.99.1955
diff -Nru hkl-4.99.99.1955/debian/control hkl-4.99.99.1955/debian/control
--- hkl-4.99.99.1955/debian/control	2015-07-07 15:47:50.0 +0200
+++ hkl-4.99.99.1955/debian/control	2015-11-22 17:30:29.0 +0100
@@ -12,7 +12,7 @@
libg3d-dev,
libg3d-plugins,
libgirepository1.0-dev,
-   libgsl0-dev,
+   libgsl-dev,
libgtk2.0-dev,
libgtkglext1-dev,
libyaml-dev,
@@ -63,7 +63,7 @@
 Depends: ${misc:Depends},
  gir1.2-hkl-5.0 (= ${binary:Version}),
  install-info,
- libgsl0-dev,
+ libgsl-dev,
  libhkl5 (= ${binary:Version})
 Pre-Depends: ${misc:Pre-Depends}
 Description: diffractometer computation control library - development files
--- End Message ---
--- Begin Message ---
Version: 4.99.99.1955-1.1

On Mon, 18 Jan 2016 13:47:42 +0100 Andreas Beckmann  wrote:
> based on Bas' patch I've uploaded a NMU to DELAYED/5. Please let me know
> if I should delay it longer.

But I forgot to close the bug ...

Andreas--- End Message ---

Bug#802815: marked as done (Remove gstreamer 0.10 in stretch)

Your message dated Tue, 02 Feb 2016 04:00:32 +
with message-id 
and subject line Bug#813254: Removed package(s) from unstable
has caused the Debian Bug report #802815,
regarding Remove gstreamer 0.10 in stretch
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.)


-- 
802815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-bad0.10
Severity: serious

Remove gstreamer 0.10 in stretch

gstreamer 0.10 is scheduled for removal, use this RC bug to keep it
out of testing (since removing it from unstable will take more time
than dropping it from stretch).

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 0.10.23-8.1+rm

Dear submitter,

as the package gst-plugins-bad0.10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/813254

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#813445: frog: FTBFS with timblserver 1.8

Source: frog
Version: 0.12.17-7.1
Severity: serious
Tags: sid
Justification: fails to build from source (but built successfully in the past)

Hi,

frog FTBFS with timblserver 1.8 that I just moved from experimental
to sid:

[...]
g++ -DHAVE_CONFIG_H -I. -I..  -I../include  -DSYSCONF_PATH=\"/etc\" 
-DPYTHONDIR=\"/usr/lib/python2.7/dist-packages/frog\" -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -fopenmp 
-I/usr/include  -I/usr/include/libxml2 -fopenmp -I/usr/include/libxml2 
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 
-I/usr/include/python2.7 -c -o Frog.o Frog.cxx
Frog.cxx:46:40: fatal error: timblserver/TimblServerAPI.h: No such file or 
directory
compilation terminated.
Makefile:454: recipe for target 'Frog.o' failed
make[3]: *** [Frog.o] Error 1
make[3]: Leaving directory '/build/frog-0.12.17/src'
Makefile:354: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/build/frog-0.12.17'
Makefile:285: recipe for target 'all' failed
make[1]: *** [all] Error 2

The watch file reports a new upstream release 0.13.0


Cheers,

Andreas

Processed: re: git-annex: FTBFS: libgnutls-deb0.so.28: cannot open shared object file: No such file or directory

Processing commands for cont...@bugs.debian.org:

> found 813078 5.20150731-1
Bug #813078 [src:git-annex] git-annex: FTBFS: libgnutls-deb0.so.28: cannot open 
shared object file: No such file or directory
Marked as found in versions git-annex/5.20150731-1.
> thanks
Stopping processing here.

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

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

2016-02-01 Thread peter green


found 813078 5.20150731-1
thanks

Debian reproducability tests in testing are not showing it right now, 
but I strongly suspect that is because some other package hasn't been 
rebuilt yet, not because the underlying issue is not there.


Having said that I think the real issue is actually in the 
libghc-network-protocol-xmpp-dev package. The file 
/usr/lib/haskell-packages/ghc/lib/arm-linux-ghc-7.10.3/network-protocol-xmpp-0.4.8-JhaYXxRYoe44FPYf4Nmd79/libHSnetwork-protocol-xmpp-0.4.8-JhaYXxRYoe44FPYf4Nmd79-ghc7.10.3.so 
contains a library dependency on gnutls but there are no corresponding 
package dependencies.


root@odroidu2:/# ldd 
/usr/lib/haskell-packages/ghc/lib/arm-linux-ghc-7.10.3/network-protocol-xmpp-0.4.8-JhaYXxRYoe44FPYf4Nmd79/libHSnetwork-protocol-xmpp-0.4.8-JhaYXxRYoe44FPYf4Nmd79-ghc7.10.3.so 
| grep gnutls
libHSgnutls-0.2-BYccZTzDgCw38R5GwM0fsE-ghc7.10.3.so => 
/usr/lib/haskell-packages/ghc/lib/arm-linux-ghc-7.10.3/gnutls-0.2-BYccZTzDgCw38R5GwM0fsE/libHSgnutls-0.2-BYccZTzDgCw38R5GwM0fsE-ghc7.10.3.so 
(0xb69c3000)

libgnutls-deb0.so.28 => not found
libgnutls.so.30 => /usr/lib/arm-linux-gnueabihf/libgnutls.so.30 
(0xb4ba9000)

root@odroidu2:/#

I'm going to try scheduling a binnmu of haskell-network-protocol-xmpp in 
raspbian stretch and see if that fixes things.

Bug#811136: marked as done (Incompatible with PostgreSQL 9.5)

Your message dated Tue, 02 Feb 2016 04:07:20 +
with message-id 
and subject line Bug#813362: Removed package(s) from unstable
has caused the Debian Bug report #811136,
regarding Incompatible with PostgreSQL 9.5
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.)


-- 
811136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pg-reorg
Version: 1.1.11-1
Severity: serious

pg-reorg fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2015-01-08 14:14:38.0 +
> +++ debian/control.wMSs2S 2016-01-15 23:07:52.281078294 +
> @@ -10,14 +10,14 @@
>  Vcs-Git: git://anonscm.debian.org/pkg-postgresql/pg-reorg.git
>  XS-Testsuite: autopkgtest
>  
> -Package: postgresql-9.4-reorg
> +Package: postgresql-9.5-reorg
>  Architecture: any
> -Depends: postgresql-9.4, ${shlibs:Depends}, ${misc:Depends}
> +Depends: postgresql-9.5, ${shlibs:Depends}, ${misc:Depends}
>  Description: reorganize tables in PostgreSQL databases without any locks
>   pg_reorg is an utility program to reorganize tables in PostgreSQL databases.
>   Unlike clusterdb, it doesn't block any selections and updates during
>   reorganization.
>   .
>   This package contains the pg_reorg program and the server extension for
> - PostgreSQL 9.4.
> + PostgreSQL 9.5.
>  
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
> 'debian/control' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 1.1.11-1+rm

Dear submitter,

as the package pg-reorg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/813362

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#812926: marked as done (tads2-mode is out-of-date and should be removed)

Your message dated Tue, 02 Feb 2016 04:06:35 +
with message-id 
and subject line Bug#813336: Removed package(s) from unstable
has caused the Debian Bug report #812926,
regarding tads2-mode is out-of-date and should be removed
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.)


-- 
812926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tads2-mode
Severity: serious
Justification: Policy 7.7

Dear Maintainer,

tads2-mode violates Section 7.7 of the Debian Policy Manual, which states that
packages must include dependencies for the clean rule in Build-Depends rather
than Build-Depends-Indep.

This package has a number of other packaging issues as well, due to its age of
over 10 years. It has a very small install base, as popcon shows 10 installs,
and it is no longer useful due to the deprecation of TADS2 itself. Thus, it
should be removed from Testing.



-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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 ---
Version: 1.2-2+rm

Dear submitter,

as the package tads2-mode has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/813336

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: gajim crashes at start

Processing commands for cont...@bugs.debian.org:

> tags 812877 +unreproducible
Bug #812877 [gajim] gajim crashes at start
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#812969: libvmime: FTBFS: net_tls_TLSSession.cpp:120:38: error: 'gnutls_certificate_type_set_priority' was not declared in this scope

2016-02-01 Thread Carsten Schoenert

Hello Peter,

Am 02.02.2016 um 06:59 schrieb peter green:
> On 01/02/16 07:45, Carsten Schoenert wrote:
>> Can you give us a suggestion how to handle this issues? I've seen a
>> similar solution like mine on the samba package upstream [5]. The zarafa
>> suite isn't using this parts of the libvmime package as they connect
>> locally to localhost. But the we have to provide a secure libvmime
>> package.
>>
> I'm not one of the gnutls maintainers but IMO you should only override 
> the defaults set by your tls library if you have good reason AND you are 
> prepared to maintain your modifications over the long term to take 
> account of changing best practice.

I fully agree with you!
But as written earlier, I'm also no security expert on cryptographic and
I haven't done any special code review on the gnutls part of libvmime
and I'm happy to get feedback from you and the GnuTLS Maintainers.

> The non-default settings in this package were clearly not being 
> maintained.

Hmm, I haven't taken a look in the current working parts of libvmime so
I can't say if it's not maintained, but consider, we are talking about
code and a release from 2010 and the code base we talking about is five
years old and there is nothing like security support by the vmime
developers!
It's some kind of ridiculous that upstream hasn't released a new version
since the 0.9.1 release related to what happens in the past two years.
But we (the Zarafa packaging Team) have a reverse dependency on that
library so we have to fix this issues.

I also fully agree with the rest of your email and I'm happy to let
libvmime use the default settings from the GnuTLS library. If this is
done by

  gnutls_set_default_priority()

as written by Andreas this is fine. We need finally a test scenario
there we can check the settings that are used if I use the libvmime
settings. Even better would be if upstream would releasing a upstream
version to get rid of special workarounds.

-- 
Regards
Carsten Schoenert

Bug#804678: marked as done (blender: Please switch from fonts-droid to fonts-noto)

Your message dated Mon, 01 Feb 2016 14:20:39 +
with message-id 
and subject line Bug#804678: fixed in blender 2.74+dfsg0-6
has caused the Debian Bug report #804678,
regarding blender: Please switch from fonts-droid to fonts-noto
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.)


-- 
804678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blender
Severity: normal
User: pkg-fonts-de...@lists.alioth.debian.org
Usertags: droid-migration

Dear Maintainer,

Since Android upstream stopped shipping Droid fonts and its been
declared that Noto fonts will be superseding the Droid¹² we in
"Debian Fonts Task Force" team decided to drop fonts-droid package.

One of your package blender either
Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly
request you to do the switch to fonts-noto instead.

If you are using Fallback variants of Droid fonts, I would like note
that these fonts will still be shipped as part of new
fonts-droid-fallback package.

¹ https://github.com/googlei18n/noto-fonts/issues/555
² 
http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht

Best Regards, 
--- End Message ---
--- Begin Message ---
Source: blender
Source-Version: 2.74+dfsg0-6

We believe that the bug you reported is fixed in the latest version of
blender, 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 804...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated blender 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: SHA512

Format: 1.8
Date: Sun, 31 Jan 2016 14:51:13 +0100
Source: blender
Binary: blender blender-data blender-dbg
Architecture: source
Version: 2.74+dfsg0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 blender- Very fast and versatile 3D modeller/renderer
 blender-data - Very fast and versatile 3D modeller/renderer - data package
 blender-dbg - Very fast and versatile 3D modeller/renderer - debug package
Closes: 804678
Changes:
 blender (2.74+dfsg0-6) unstable; urgency=medium
 .
   * debian/patches/: patchset updated (Closes: #804678)
 - 0007-look_for_droid_ttf_with_fontconfig.patch
   -> 0007-look_for_dejavu_ttf_with_fontconfig.patch
 - 0008-ffmpeg_2.9.patch refreshed
   * debian/control: fonts-droid -> fonts-dejavu dependency
 for binary package
   * debian/control: Vcs-* fields updated
Checksums-Sha1:
 2fce2e6fc1862e6c98b37691a0ae9d5218b35d54 2881 blender_2.74+dfsg0-6.dsc
 be8cbdac6c77063b445b3d95eeb7252449717688 47796 
blender_2.74+dfsg0-6.debian.tar.xz
Checksums-Sha256:
 2226df9dc69720479f05b23d471864271c41030d860b44fc60e7851a49b9 2881 
blender_2.74+dfsg0-6.dsc
 070babf0ba6b699aaf8f8ac14ed3458f7632438f27f9b765eda1b8dc68a46b77 47796 
blender_2.74+dfsg0-6.debian.tar.xz
Files:
 64d75ade4604a78f6190b6ac965f3d45 2881 graphics optional 
blender_2.74+dfsg0-6.dsc
 48cdce0e8147e73763f048d10ccd48a7 47796 graphics optional 
blender_2.74+dfsg0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJWrhF2XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1aXxIQAIAlmRY5IY8CIQQ1N3UnWLxa
UWp8Shu/sdGpKVxtx+YYeZlw3DnypwKFDk143bKYRdZWnOJspjUJXSvm79j8AtOs
X9+dcGJqk8HDIFASEhKphjfx9zTk7uoITeJxQ8vL9VGCODWFv/k3Koas4C1xqVL0
HB0CDqyhA6ZwSGEKAlflM/8CN4MBKxgjfdNtLEimc7G2fjszQ9qD5swpVh2Vi7pO
oYBXQDbEYjbBnnvV6hazsaJauqHb3Rg4V0MFSPRE31AxIOmbsREMEv2KS/D/ZikY
zu45IV/sopvLxrb8IO5gnHXUK0H1lIwvpHqqzDbP0Ja3oAkj72gVni3gAh3W1Pro
ZAtsgrOQR3NmHqJIawmWclg3wbwKbrELzlgv2xJ4jblnV02s3BPiOGqRT3zDK5HN
kwiMa/zskUfYcAIzbAhsbXbW7/r9XtSEUrC6R63IN6Jtn2GRUE0zwJI8QwEphVq6
F0C7macyeH8kY9rVgpvO//HYlMPUARnSS/ovhtpu2EdFUcAIzCJ8WLiy7SC49rTu
T8bGLQEHHD59WjWqaKwvWd7QMk/oCM7HHh/1lWImRNNgXv5VXrMTc5jOib9zHq05
NPMmaPxSij1SGAKuet6vzh/x/EJsqUSWj8cMk6ok9ePNAodGb9kPUPI96YSHmDBd

Bug#813189: marked as done (libio-socket-ssl-perl: FTBFS with current libssl1.0.2: t/startssl-failed.t hangs)

Your message dated Mon, 01 Feb 2016 14:40:51 +
with message-id 
and subject line Bug#813189: fixed in libio-socket-ssl-perl 2.023-1
has caused the Debian Bug report #813189,
regarding libio-socket-ssl-perl: FTBFS with current libssl1.0.2: 
t/startssl-failed.t hangs
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.)


-- 
813189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libio-socket-ssl-perl
Version: 2.022-1
Severity: serious
X-Debbugs-Cc: open...@packages.debian.org

The libio-socket-ssl-perl started hanging in its test suite
with libssl1.0.2 upgrade from 1.0.2e-1 to 1.0.2f-2.

The hanging test is t/startssl-failed.t, and running it
manually shows

 perl t/startssl-failed.t
 1..9
 ok #Server Initialization
 ok #client tcp connect
 ok #tcp accept
 ok #send non-ssl data

The libio-socket-ssl-perl package is arch:all, the actual extension
linking with libssl is libnet-ssleay-perl. That one is passing its
test suite, and recompiling it with 1.0.2f-2 doesn't change the
situation with libio-socket-ssl-perl.

Another affected package seems to be libnet-https-nb-perl, which is
using libio-socket-ssl-perl.

Cc'ing the openssl maintainers; any ideas? I hope I can make a smaller
test case later, but I'm out of time right now.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libio-socket-ssl-perl
Source-Version: 2.023-1

We believe that the bug you reported is fixed in the latest version of
libio-socket-ssl-perl, 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.
Salvatore Bonaccorso  (supplier of updated 
libio-socket-ssl-perl 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: SHA512

Format: 1.8
Date: Mon, 01 Feb 2016 11:21:22 +0100
Source: libio-socket-ssl-perl
Binary: libio-socket-ssl-perl
Architecture: source
Version: 2.023-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Salvatore Bonaccorso 
Closes: 813189
Description: 
 libio-socket-ssl-perl - Perl module implementing object oriented interface to 
SSL sockets
Changes:
 libio-socket-ssl-perl (2.023-1) unstable; urgency=medium
 .
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
   * Import upstream version 2.023
 - Addresses "FTBFS with current libssl1.0.2: t/startssl-failed.t hangs"
   (Closes: #813189).
Checksums-Sha1: 
 3f05d49d0486fb84a28e6b107a3003d2e011994a 2599 libio-socket-ssl-perl_2.023-1.dsc
 b091d0b6c90888fcb12177f48aa23e575b5b201b 209572 
libio-socket-ssl-perl_2.023.orig.tar.gz
 36d15989c2c87ec9a2988c0888cd6991323ccbd4 8964 
libio-socket-ssl-perl_2.023-1.debian.tar.xz
Checksums-Sha256: 
 0d634e72883b1c6921e8d0244310f2733c42a6aefe30d61ba11cdf577fd499a3 2599 
libio-socket-ssl-perl_2.023-1.dsc
 49ae36c6e881072229c17dee6b4d4f24e9ec9c40cdde1b0bd09903d87981f9e5 209572 
libio-socket-ssl-perl_2.023.orig.tar.gz
 20af2a306616c7bdc44d5e141c38fffcf507cb4adc7e05caa2cab61eff95ee24 8964 
libio-socket-ssl-perl_2.023-1.debian.tar.xz
Files: 
 8897949e18a35eaa1ad2d3a7922e4869 2599 perl optional 
libio-socket-ssl-perl_2.023-1.dsc
 89df81cbc1c477937fdcfa8fea173a48 209572 perl optional 
libio-socket-ssl-perl_2.023.orig.tar.gz
 639d31af02191381fc802bab6fbea2b1 8964 perl optional 
libio-socket-ssl-perl_2.023-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWrzJZAAoJEAVMuPMTQ89ESwsP/2tKNtTNdL3j6AiPvhn2g8A2
64Jh+SN6odGQ52S2/EDJt+Xjs8KT6a3pOzgrS0NmLXR+nJ7VHpSoPyNGQbBe7Pik
RRtEbAu410hXDgGAHLnGVogAFcdWDLz020ZWHi43XFdURqkucSp2TQtzjhUrE89p
/Evzix7wA6SsCSrHZ0hPY1vqmFCBfQgIpu+QiToUaBO7gfT7q+oAggyhrgH5qShm
bZm/NnqfgkKK8If2BCQSOwE2NxNBCZzH7oGX7fxiPhOB3I3PCDABC82CZTNARhYb
gULUOuP/WF7stg/eOUjKSAOh3IBb6lgVjeAnFOihwXxV/8hSOzfjigLXA2RC970F
jSE/qd7as0GHQfzwgNUidIfu7Sc15NJJIgYEIgk0XI9x6Y0FA/3WLEnAPZAo8nMa
dO3VeDLXr5AZm1yWzupeW05eWbWyjrf0U7xLOtpfHUr/Ik9kj2TVLMRSJ3Dqx4Bf
IzwCBYySP6BSrrP5Up35FZXM+DQYrfaZgkaqBRcTTLe9uOVOYpKTAxnsMNT1+tQT

Bug#812937: marked as done (ruby-test-unit-context: FTBFS - tests unexpectedly returning nil)

Your message dated Mon, 01 Feb 2016 14:46:29 +
with message-id 
and subject line Bug#812937: fixed in ruby-test-unit-context 0.5.0-2
has caused the Debian Bug report #812937,
regarding ruby-test-unit-context: FTBFS - tests unexpectedly returning nil
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.)


-- 
812937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-test-unit-context
Version: 0.5.0-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
===
Failure: test: runs setup method block a la 
Shoulda(Test::Unit::Context::TestHooks::ContextWithSetupTeardownMethods)
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-test-unit-context/ruby-test-unit-context-0.5.0/test/test/unit/context/hooks_test.rb:194:in
 `block (2 levels) in '
 191:   SAMPLE_TEST.class_eval { attr_reader :one, :two }
 192:   
 193:   it "runs setup method block a la Shoulda" do
  => 194: assert_equal 1, @test.one
 195:   end
 196: 
 197:   it "runs setup method block and regular callbacks" do
<1> expected but was

===
: (0.014986)
test: runs setup method block and regular callbacks:.: (0.001075)
test: runs teardown method block a la Shoulda:  F
===
Failure: test: runs teardown method block a la 
Shoulda(Test::Unit::Context::TestHooks::ContextWithSetupTeardownMethods)
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-test-unit-context/ruby-test-unit-context-0.5.0/test/test/unit/context/hooks_test.rb:202:in
 `block (2 levels) in '
 199:   end
 200: 
 201:   it "runs teardown method block a la Shoulda" do
  => 202: assert_equal 10, @test.two
 203:   end
 204: 
 205:   it "runs teardown method block and regular callbacks" do
<10> expected but was

===
[...]
Finished in 0.066519869 seconds.
--
67 tests, 92 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
97.0149% passed
--
1007.22 tests/s, 1383.05 assertions/s
rake aborted!
Command failed with status (1): [ruby -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test/unit/context/hooks_test.rb" "test/test/unit/context/shared_test.rb" 
"test/test/unit/context/spec_test.rb" "test/test/unit/context_test.rb" 
"test/test/unit/patches_test.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/srv/jenkins-slave/workspace/sid-goto-cc-ruby-test-unit-context/ruby-test-unit-context-0.5.0/debian/ruby-test-unit-context
 returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


ruby-test-unit-context-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-test-unit-context
Source-Version: 0.5.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-test-unit-context, 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 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated 
ruby-test-unit-context 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: SHA512

Format: 1.8
Date: Mon, 01 Feb 2016 15:32:39 +0530
Source: ruby-test-unit-context
Binary: ruby-test-unit-context
Architecture: source all
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras

Bug#813259: marked as done (ubuntu-archive-keyring: postrm called with unknown argument `upgrade')

Your message dated Mon, 01 Feb 2016 14:47:48 +
with message-id 
and subject line Bug#813259: fixed in ubuntu-keyring 2012.05.19-5
has caused the Debian Bug report #813259,
regarding ubuntu-archive-keyring: postrm called with unknown argument `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.)


-- 
813259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ubuntu-archive-keyring
Version: 2012.05.19-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed the maintainer scripts of your
package don't support all the ways they are going to be called.

See policy 6.5 at
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-mscriptsinstact

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ubuntu-archive-keyring_2012.05.19-4_all.deb ...
  Unpacking ubuntu-archive-keyring (2012.05.19-4) over (2012.05.19-1) ...
  postrm called with unknown argument `upgrade'
  dpkg: warning: subprocess old post-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  dpkg: ... it looks like that went OK

 
Testing reinstallation in sid:

Preparing to unpack .../ubuntu-archive-keyring_2012.05.19-4_all.deb ...
Unpacking ubuntu-archive-keyring (2012.05.19-4) over (2012.05.19-4) ...
postrm called with unknown argument `upgrade'
dpkg: warning: subprocess old post-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK


Cheers,

Andreas


ubuntu-archive-keyring_2012.05.19-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ubuntu-keyring
Source-Version: 2012.05.19-5

We believe that the bug you reported is fixed in the latest version of
ubuntu-keyring, 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.
Hideki Yamane  (supplier of updated ubuntu-keyring 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: SHA512

Format: 1.8
Date: Mon, 01 Feb 2016 21:54:21 +0900
Source: ubuntu-keyring
Binary: ubuntu-archive-keyring
Architecture: source all
Version: 2012.05.19-5
Distribution: unstable
Urgency: medium
Maintainer: Hideki Yamane 
Changed-By: Hideki Yamane 
Description:
 ubuntu-archive-keyring - GnuPG keys of the Ubuntu archive
Closes: 813259
Changes:
 ubuntu-keyring (2012.05.19-5) unstable; urgency=medium
 .
   * debian/postrm
 - fix "postrm called with unknown argument `upgrade'" (Closes: #813259)
Checksums-Sha1:
 60902d21d87b8c2a84fd6ea04530cd848c38fb37 1812 ubuntu-keyring_2012.05.19-5.dsc
 16f04c419f02e62f8f3b642d7f80746e9a597b79 3896 
ubuntu-keyring_2012.05.19-5.debian.tar.xz
 3c84538420d612fad3e31ad768a9f1b172a958b9 18384 
ubuntu-archive-keyring_2012.05.19-5_all.deb
Checksums-Sha256:
 91babdf96704868d0cc4311e5f197e6dc2d7f8bb7f0e6a559ec085766598759c 1812 
ubuntu-keyring_2012.05.19-5.dsc
 866b47dbd022009e191147753723722e9ff103a6cc8d4f5bbd400512a6205665 3896 
ubuntu-keyring_2012.05.19-5.debian.tar.xz
 c32550ad4d3d3aff89345ce2841ae1f791394121debcabbffebafd34998d14e2 18384 
ubuntu-archive-keyring_2012.05.19-5_all.deb
Files:
 5deda0ae3ad2da75d97547f21feceeca 1812 misc optional 
ubuntu-keyring_2012.05.19-5.dsc
 c5281b69600f5a66190312adc3a38d96 3896 misc optional 
ubuntu-keyring_2012.05.19-5.debian.tar.xz
 1cba6a797e299e24c4fbd870011e1271 18384 misc optional 
ubuntu-archive-keyring_2012.05.19-5_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWr1XUAAoJEF0yjQgqqrFAA1sQAIGoZBasyYetIgmqw+p9y0nn
mDETlKfnhSZj7dfP255hLddflrlE89Foj9i5lsqUSu013zejIHHcakyDgv/koawY
wSFT9tbUSt2Fcz22TaFXpKvNyAxWquITdJQ3E6HwduQT/GqFxOP87kWQHJjFPFc7
7cmD6pX1RgRdVK6UTHZmwkntYsz/cGGp5ITlELSbdOg/Kg6zV5PeLB/b8q1MMMDI
Lv3/Q7/hhnEY5eEf436Ge63f/ZM1vvYvW7MMqpubNeQOOQAsbXaFRzvNm447hI/G
yM2UDi3ktgvbaB8rswNdm4q9Yh9i2rsX5KQ2h8eMSSwQJl7GER8REjAT/T0B4TmY

Bug#813265: marked as done (ruby-bcat: postrm called with unknown argument `upgrade')

Your message dated Mon, 01 Feb 2016 14:46:24 +
with message-id 
and subject line Bug#813265: fixed in ruby-bcat 0.6.2-5
has caused the Debian Bug report #813265,
regarding ruby-bcat: postrm called with unknown argument `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.)


-- 
813265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-bcat
Version: 0.6.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed the maintainer scripts of your
package don't support all the ways they are going to be called.

See policy 6.5 at
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-mscriptsinstact

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ruby-bcat_0.6.2-4_all.deb ...
  Unpacking ruby-bcat (0.6.2-4) over (0.6.2-3) ...
  postrm called with unknown argument `upgrade'
  dpkg: warning: subprocess old post-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  Removing 'diversion of /usr/bin/bcat to /usr/bin/bcat.diverted by ruby-bcat'
  dpkg: ... it looks like that went OK


Testing reinstallation in sid:

Preparing to unpack .../ruby-bcat_0.6.2-4_all.deb ...
Unpacking ruby-bcat (0.6.2-4) over (0.6.2-4) ...
postrm called with unknown argument `upgrade'
dpkg: warning: subprocess old post-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Removing 'diversion of /usr/bin/bcat to /usr/bin/bcat.diverted by ruby-bcat'
dpkg: ... it looks like that went OK


Cheers,

Andreas


ruby-bcat_0.6.2-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-bcat
Source-Version: 0.6.2-5

We believe that the bug you reported is fixed in the latest version of
ruby-bcat, 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.
Hideki Yamane  (supplier of updated ruby-bcat 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: SHA512

Format: 1.8
Date: Mon, 01 Feb 2016 22:01:39 +0900
Source: ruby-bcat
Binary: ruby-bcat
Architecture: source all
Version: 0.6.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hideki Yamane 
Description:
 ruby-bcat  - pipe to browser utility
Closes: 813265
Changes:
 ruby-bcat (0.6.2-5) unstable; urgency=medium
 .
   * debian/postrm
 - fix "postrm called with unknown argument `upgrade'" (Closes: #813265)
Checksums-Sha1:
 f044c743690498f8f6c888212a22c04077d4b3d8 1984 ruby-bcat_0.6.2-5.dsc
 c01829640cfe106ceac970b17989b2e2f044d777 3096 ruby-bcat_0.6.2-5.debian.tar.xz
 0e9f6c0307040a3d3d63f56e5fa16eb7e5b1f431 10782 ruby-bcat_0.6.2-5_all.deb
Checksums-Sha256:
 25c5f474224d2b1da5d724d7dbcae6dd2510670ccd1c3151f9ed8b849254a523 1984 
ruby-bcat_0.6.2-5.dsc
 b52501067a97510b49492ceb7153e59bd85812c98b850f9b8ff72f7f5659be50 3096 
ruby-bcat_0.6.2-5.debian.tar.xz
 a0450a4c30c3dfc974910d93c680b3b92b04585243498e0bf1a864282b4154e1 10782 
ruby-bcat_0.6.2-5_all.deb
Files:
 c6a0172642e1839921b58b1bdba14fdb 1984 ruby optional ruby-bcat_0.6.2-5.dsc
 2a3fe592f2a6401e2c0c635825c46e66 3096 ruby optional 
ruby-bcat_0.6.2-5.debian.tar.xz
 0b0410fe910aa8d4bac815eafcb5ece9 10782 ruby optional ruby-bcat_0.6.2-5_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWr1eLAAoJEF0yjQgqqrFAvpkP/2z/Mo3QYNG4xHJb07hYfnuH
EthrphdVfyVx7tcOWmHxkJPNZ9/Cg94+GJWH6bP4ZrvkkR5DIgyWfB9262BV1VbM
k1E9czgjsO1jkLwjfvi+091aq8QpMlm+W653cu9OWiiwzFUV6aiwAVMZIFFJQxiY
6J1bWlz1QUnDJga/BV/+ENCxTS5RdoScDLPwOeJKZ84WlsFl2ETOvsHdeVtevJbq
dUEWcyC5MOn9cebihpavhFTNaByjxP3mhkF9F8Ay97fLEPGkLcvUu4zejKYfWQax
XWlW6bnngDE7Zv8yw0xis6l/g8A7EBSQ1lxwCUMWLSoloKSF/IMqD8kQgdsCQtNC
S/hDSJTYprhz0oYP42BHwMEiAqCHfvWrfDJQ1TrLFucoW4EsbAyoRnFODpp8HA8E
PtDHdnBZr+CKHJqkf2cj6yWwRKM9oZ0/EHrVVU6OM4yCAkHtsjxojsQeKgTUn6BP

Bug#813358: marked as done (wcsaxes: FTBFS: assert 1 == 0 # where 1 = len([]))

Your message dated Mon, 01 Feb 2016 14:48:26 +
with message-id 
and subject line Bug#813358: fixed in wcsaxes 0.6-5
has caused the Debian Bug report #813358,
regarding wcsaxes: FTBFS: assert 1 == 0 # where 1 = 
len([])
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.)


-- 
813358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wcsaxes
Version: 0.6-4
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,

wcsaxes fails to build from source in unstable/amd64:

  [..]

  copying wcsaxes/tests/baseline_images/changed_axis_units.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/rcparams.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/curvlinear_grid_patches_image.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/cube_slice_image_lonlat.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/tick_angles.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/image_plot.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/test_axislabels_regression.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/set_coord_type.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/test_noncelestial_angular.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/test_ticks_regression_1.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/coords_overlay.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  copying wcsaxes/tests/baseline_images/direct_init.png -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/baseline_images
  creating build/lib.linux-x86_64-3.4/wcsaxes/tests/data
  copying wcsaxes/tests/data/2MASS_k_header -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/data
  copying wcsaxes/tests/data/msx_header -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/data
  copying wcsaxes/tests/data/cube_header -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/data
  copying wcsaxes/tests/data/slice_header -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/data
  copying wcsaxes/tests/data/rosat_header -> 
build/lib.linux-x86_64-3.4/wcsaxes/tests/data
  /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:102: 
AstropyDeprecationWarning: Direct use of the adjust_compiler function in 
setup.py is deprecated and can be removed from your setup.py.  This 
functionality is now incorporated directly into the build_ext command.
'command.', AstropyDeprecationWarning)
  I: pybuild base:184: /usr/bin/python3 setup.py build 
  running build
  running build_py
  creating build/lib.linux-x86_64-3.5
  creating build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/utils.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/ticks.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/__init__.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/coordinate_range.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/conftest.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/axislabels.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/version.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/coordinates_map.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/settings.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/rc_utils.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/frame.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/wcs_wrapper.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/coordinate_helpers.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/core.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/wcs_utils.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/_astropy_init.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/grid_paths.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/transforms.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying wcsaxes/formatter_locator.py -> build/lib.linux-x86_64-3.5/wcsaxes
  copying

Bug#813383: herwig++: FTBFS on i386: Floating point exception in check-LHC-Powheg target

Source: herwig++
Version: 2.6.0-1.1
Severity: serious
Justification: fails to build from source

Hi,

your package FTBFS on i386:

https://buildd.debian.org/status/fetch.php?pkg=herwig%2B%2B=i386=2.6.0-1.1=1453986622

Makefile:1087: recipe for target 'check-LHC-Powheg' failed
make[5]: *** [check-LHC-Powheg] Floating point exception
make[5]: *** Waiting for unfinished jobs

Does that look like an error got triggered in make?

I could reproduce it locally by rebuilding the package in a sid-i386
pbuilder environment. It disappeared once I disabled the parallel build.
Is there something racy in the testsuite?


Andreas

Bug#812539: marked as done (criticalmass: FTBFS in pbuilder enviroment)

Your message dated Mon, 1 Feb 2016 14:52:16 +
with message-id <20160201145216.ga16...@chase.mapreri.org>
and subject line OP confirmed criticalmass builds
has caused the Debian Bug report #812539,
regarding criticalmass: FTBFS in pbuilder enviroment
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.)


-- 
812539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: criticalmass
Version: 1:1.0.0-4
Severity: serious
Justification: FTBFS

It FTBFS in a clean pbuilder enviroment.

built with:
pdebuild --debbuildopts "-I -i -j4 -d"

buildlog attached.

-- 
tobi

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
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)
dpkg-checkbuilddeps: error: Unmet build dependencies: libgl1-mesa-dev | 
libgl-dev libsdl-image1.2-dev (>= 1.2.2) libsdl-mixer1.2-dev libsdl1.2-dev 
libcurl4-gnutls-dev
W: Unmet build-dependency in source
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: source package criticalmass
dpkg-buildpackage: source version 1:1.0.0-4
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Adam Borowski 
 dpkg-source -I -i --before-build criticalmass-1.0.0
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
if [ -f config.status ]; then \
[ ! -f Makefile ] || /usr/bin/make distclean; \
fi
rm -f game/resource.dat
dh_autotools-dev_restoreconfig
cat debian/generated-files.txt | xargs rm -f
dh_clean
 dpkg-source -I -i -b criticalmass-1.0.0
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building criticalmass using existing 
./criticalmass_1.0.0.orig.tar.bz2
dpkg-source: warning: ignoring deletion of file aclocal.m4, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file configure, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file config.guess, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file install-sh, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file config.sub, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file defines.h.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file missing, use --include-removal 
to override
dpkg-source: warning: ignoring deletion of file tinyxml/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file game/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file tools/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file utilssdl/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file utils/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file 
utils/lzma/SRC/7zip/Compress/LZMA_Alone/makefile.orig, use --include-removal to 
override
dpkg-source: warning: ignoring deletion of file data/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file data/music/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file utilsgl/Makefile.in, use 
--include-removal to override
dpkg-source: info: building criticalmass in criticalmass_1.0.0-4.debian.tar.xz
dpkg-source: info: building criticalmass in criticalmass_1.0.0-4.dsc
 dpkg-genchanges -S >../criticalmass_1.0.0-4_source.changes
dpkg-genchanges: not including original source code in upload
 dpkg-source -I -i --after-build criticalmass-1.0.0
dpkg-buildpackage: binary and diff upload (original source NOT included)
W: /root/.pbuilderrc does not exist
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sun Jan 24 20:16:20 UTC 2016
I: pbuilder-time-stamp: 1453666580
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base.tgz]
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I:

Bug#808740: marked as done (kuser: FTBFS: dhmk.mk:110: recipe for target 'debian/dhmk_configure' failed)

Your message dated Mon, 01 Feb 2016 14:40:05 +
with message-id 
and subject line Bug#808740: fixed in kuser 4:15.12.0-1
has caused the Debian Bug report #808740,
regarding kuser: FTBFS: dhmk.mk:110: recipe for target 'debian/dhmk_configure' 
failed
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.)


-- 
808740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kuser
Version: 4:4.12.2-2
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,

kuser fails to build from source in unstable/amd64:

  [..]

  //ADVANCED property for variable: X11_Xrandr_LIB
  X11_Xrandr_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xrender_INCLUDE_PATH
  X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xrender_LIB
  X11_Xrender_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xscreensaver_INCLUDE_PATH
  X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xscreensaver_LIB
  X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xshape_INCLUDE_PATH
  X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xt_INCLUDE_PATH
  X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xt_LIB
  X11_Xt_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xutil_INCLUDE_PATH
  X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xv_INCLUDE_PATH
  X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xv_LIB
  X11_Xv_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xxf86misc_LIB
  X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_dpms_INCLUDE_PATH
  X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_xf86misc_INCLUDE_PATH
  X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_xf86vmode_INCLUDE_PATH
  X11_xf86vmode_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //Test _OFFT_IS_64BIT
  _OFFT_IS_64BIT:INTERNAL=1
  //Test __KDE_HAVE_GCC_VISIBILITY
  __KDE_HAVE_GCC_VISIBILITY:INTERNAL=1
  //Test __KDE_HAVE_W_OVERLOADED_VIRTUAL
  __KDE_HAVE_W_OVERLOADED_VIRTUAL:INTERNAL=1
  //Result of TRY_COMPILE
  _basic_compile_result:INTERNAL=TRUE
  //Result of TRY_COMPILE
  _compile_result:INTERNAL=TRUE
  
  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_USE_RELATIVE_PATHS=ON returned exit code 1
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 
'pre_configure_dh_auto_configure' failed
  make[1]: *** [pre_configure_dh_auto_configure] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151222120720.xSmIzdRgvf/kuser-4.12.2'
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 
'debian/dhmk_configure' failed
  make: *** [debian/dhmk_configure] Error 2

  [..]

The full build log is attached.


Regards,

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


kuser.4:4.12.2-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: kuser
Source-Version: 4:15.12.0-1

We believe that the bug you reported is fixed in the latest version of
kuser, 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.
Maximiliano Curia  (supplier of updated kuser 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: SHA512

Format: 1.8
Date: Mon, 01 Feb 2016 10:22:44 +0100
Source: kuser
Binary: kuser
Architecture: source
Version: 4:15.12.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers

Bug#810342: marked as done (taskd: fails to install: chown: cannot access '/var/lib/taskd/orgs': No such file or directory)

Your message dated Mon, 01 Feb 2016 14:47:31 +
with message-id 
and subject line Bug#810342: fixed in taskd 1.1.0+dfsg-2
has caused the Debian Bug report #810342,
regarding taskd: fails to install: chown: cannot access '/var/lib/taskd/orgs': 
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.)


-- 
810342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: taskd
Version: 1.1.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package taskd.
  (Reading database ... 
(Reading database ... 7411 files and directories currently installed.)
  Preparing to unpack .../taskd_1.1.0+dfsg-1_amd64.deb ...
  Unpacking taskd (1.1.0+dfsg-1) ...
  Processing triggers for systemd (228-3) ...
  Setting up taskd (1.1.0+dfsg-1) ...
  chown: cannot access '/var/lib/taskd/orgs': No such file or directory
  dpkg: error processing package taskd (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-3) ...
  Errors were encountered while processing:
   taskd


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: taskd
Source-Version: 1.1.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
taskd, 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 810...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated taskd 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, 08 Jan 2016 17:45:59 +0100
Source: taskd
Binary: taskd
Architecture: source amd64
Version: 1.1.0+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Sebastien Badia 
Changed-By: Sebastien Badia 
Description:
 taskd  - Synchronisation server for taskwarrior
Closes: 810342
Changes:
 taskd (1.1.0+dfsg-2) unstable; urgency=high
 .
   * Fix old installation pattern,
 orgs are now created by user (Closes: #810342).
Checksums-Sha1:
 e29fdf0e471d4815421c0bc9298099d31793b57c 1933 taskd_1.1.0+dfsg-2.dsc
 9c7a24602fcf25e6862515d2080a95c0668c9bfa 6536 taskd_1.1.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 5db22b9a24225a871596866cb9bd0375f5e1917ae361d19bf510e4a672f7ce0c 1933 
taskd_1.1.0+dfsg-2.dsc
 01dc3ea34815eb169193c3a65e58f420110a98f5c075093f07c5bfc1fd895632 6536 
taskd_1.1.0+dfsg-2.debian.tar.xz
Files:
 19b3db9c5e15ddfd7b9c67d53f8f29ce 1933 utils extra taskd_1.1.0+dfsg-2.dsc
 95119e3d86a8a86c2a78d64e3057d99c 6536 utils extra 
taskd_1.1.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIbBAEBCAAGBQJWrv/qAAoJEJFk+h0XvV02nj4P9j7JCkYag+8IxfQvoXxHxe0p
NRHoFvaom+0vx2MlGeUSTob3Apn+rNg6FSfUKKxxrVKIATmYjlIwFY+XDoqC9W+2
qpUTmXmtqzdsKmMlQJORLX3xRbPqVFl0uCkCTtJdroPlkM35spLRVYwZUrZttnMn
gbNoiqJKvqg2GxKpy/2mLCdK3wKHv9hsCVnTTEKJ8RpmPiy/H5a1WTzTfz6V+9YT
JLbNlYI5Kpm6bvJh8AzQ8kyAaRjrvylwMMiJ2W/wAE3h4jas6rh1y8AbggBHMSen
tA8RpiiHEEP1YoKqyxlXSierXtaGG2fMFMKqtxKLQCb4toCzD3HJYdEregoZOMs8
h2BI0oFq/JJLRdHoZRmVvM7cBqVuoBKv/XALVC2VdTdy+RnHh4f3BIkpjAXKinAO
4bb0yGwpLo+sRCjV0+htK3sEjr9KKW5/Sw2+gDvauO6xD6fWq9bHtG533HQq9ZyU
wSa6cR79HQETMLG937/po4PmbPkZ74CJCpM5fAGVoDRBPOxo48LirMVF2mGuVXY9
/s4aFj2aZIo196H2dowKi0G5+u1m2rCwsOoEDkL3bQtOiKa+uPZmSRmJex3ECRD/
5m9Jw98oV5+IbT/lNvDTvYN5ljeY9xu61/vr5dpz0xin+OGyKMIO1Ts2a5UetM8C
4xACXrF+ZYapsio39mE=
=8MRB
-END PGP SIGNATURE End Message ---

Bug#785891: psimedia: Please update to GStreamer 1.x

2016-02-01 Thread Boris Pek

Hi Moritz,

> what's the status, is there pending work to fix this upstream? The
> list of remaining gstreamer 0.10 is now becoming really short, so
> at one point psimedia will have to be removed along if it doesn't
> get fixed.

Unfortunately there is no any progress in porting psimedia to gstreamer 1.x in
upstream. If nothing changes I'll do it myself. But I am not sure when I will
find time for this.

Best regards,
Boris

Bug#813400: libcglib-nodep-java: fails to upgrade from 'testing' - trying to overwrite /usr/share/java/cglib-nodep.jar

Package: libcglib-nodep-java
Version: 3.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libcglib-nodep-java.
  Preparing to unpack .../libcglib-nodep-java_3.2.0-1_all.deb ...
  Unpacking libcglib-nodep-java (3.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcglib-nodep-java_3.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/java/cglib-nodep.jar', which is also in 
package libcglib-java 2.2.2+dfsg2-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libcglib-nodep-java_3.2.0-1_all.deb


cheers,

Andreas


libcglib-java=2.2.2+dfsg2-2_libcglib-nodep-java=3.2.0-1.log.gz
Description: application/gzip

Bug#813399: python-pip-whl: fails to upgrade from 'testing' - trying to overwrite /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl

Package: python-pip-whl
Version: 8.0.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python-pip-whl.
  Preparing to unpack .../python-pip-whl_8.0.2-2_all.deb ...
  Unpacking python-pip-whl (8.0.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pip-whl_8.0.2-2_all.deb (--unpack):
   trying to overwrite 
'/usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl', which is also in 
package python-six-whl 1.10.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pip-whl_8.0.2-2_all.deb


cheers,

Andreas


python-six-whl=1.10.0-1_python-pip-whl=8.0.2-2.log.gz
Description: application/gzip

Bug#813399: [Python-modules-team] Bug#813399: python-pip-whl: fails to upgrade from 'testing' - trying to overwrite /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl

2016-02-01 Thread Barry Warsaw

On Feb 01, 2016, at 04:24 PM, Andreas Beckmann wrote:

>during a test with piuparts I noticed your package fails to upgrade from
>'testing'.
>It installed fine in 'testing', then the upgrade to 'sid' fails
>because it tries to overwrite other packages files without declaring a
>Breaks+Replaces relation.
>
>See policy 7.6 at
>https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>
>>From the attached log (scroll to the bottom...):  
>
>  Selecting previously unselected package python-pip-whl.
>  Preparing to unpack .../python-pip-whl_8.0.2-2_all.deb ...
>  Unpacking python-pip-whl (8.0.2-2) ...
>  dpkg: error processing archive 
> /var/cache/apt/archives/python-pip-whl_8.0.2-2_all.deb (--unpack):
>   trying to overwrite 
> '/usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl', which is also in 
> package python-six-whl 1.10.0-1
>  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>  Errors were encountered while processing:
>   /var/cache/apt/archives/python-pip-whl_8.0.2-2_all.deb

python-pip-whl has Breaks/Replaces, but it looks like I got the version
specifications wrong.

Bug#812188: closed by Osamu Aoki <os...@debian.org> (Re: Bug#812188: debiandoc-sgml-doc-pt-br: FTBFS: make[1]: nsgmls: Command not found)

2016-02-01 Thread Jérémy Bobbio

Debian Bug Tracking System:
> This package is caught up in the package transition which caused:
> 
> >   make[1]: nsgmls: Command not found
> 
> With recent NMU of debiandoc-sgml changing by Niel its package
> dependencies, this should have been fixed. See Bug#805061

The last build attempted on 2016-01-31 on reproducible.debia.net failed
with the same error.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#813189: [Pkg-openssl-devel] Bug#813189: libio-socket-ssl-perl: FTBFS with current libssl1.0.2: t/startssl-failed.t hangs

2016-02-01 Thread Salvatore Bonaccorso

Hi Kurt,

On Sun, Jan 31, 2016 at 08:34:44PM +0100, Kurt Roeckx wrote:
> On Sat, Jan 30, 2016 at 10:51:06PM +0100, Salvatore Bonaccorso wrote:
> > Hi Niko,
> > 
> > On Sat, Jan 30, 2016 at 09:24:26PM +0200, Niko Tyni wrote:
> > > On Sat, Jan 30, 2016 at 12:03:27PM +0200, Niko Tyni wrote:
> > > > Package: libio-socket-ssl-perl
> > > > Version: 2.022-1
> > > > Severity: serious
> > > > X-Debbugs-Cc: open...@packages.debian.org
> > > > 
> > > > The libio-socket-ssl-perl started hanging in its test suite
> > > > with libssl1.0.2 upgrade from 1.0.2e-1 to 1.0.2f-2.
> > > > 
> > > > The hanging test is t/startssl-failed.t, and running it
> > > > manually shows
> > > > 
> > > >  perl t/startssl-failed.t
> > > >  1..9
> > > >  ok #Server Initialization
> > > >  ok #client tcp connect
> > > >  ok #tcp accept
> > > >  ok #send non-ssl data
> > > 
> > > It's looping in IO::Socket::SSL::stop_SSL, repeatedly getting 0 from
> > > Net::SSLeay::shutdown(), which seems to be just a thin wrapper for
> > > the libssl SSL_shutdown().
> > > 
> > > Reverting
> > >  
> > > https://github.com/openssl/openssl/commit/f73c737c7ac908c5d6407c419769123392a3b0a9
> > > makes things work again.
> > > 
> > > Kurt, which one do you think is wrong?
> > 
> > FTR, Upstream has released a new version (I have imported in our git
> > repo already):
> > 
> > 2.023 2016/01/30
> > - OpenSSL 1.0.2f changed the behavior of SSL shutdown in case the TLS 
> > connection
> >   was not fully established (commit: 
> > f73c737c7ac908c5d6407c419769123392a3b0a9).
> >   This somehow resulted in Net::SSLeay::shutdown returning 0 (i.e. keep 
> > trying)
> >   which caused an endless loop. It will now ignore this result in case the 
> > TLS
> >   connection was not yet established and consider the TLS connection closed
> >   instead.
> > 
> > But this does not seem to fully resolve the issue yet. When I try to
> > build the testsuite still get stuck.
> 
> So as I understand it, the problem is that the client just sends
> crap, the server tells the client it sends crap, but then waits
> for the client to properly terminate the question which it never
> does?
> 
> It's at least not behaviour I can reproducing using s_server, the
> server actually closes the connection for me.

JFTR, the additional problem is unrelated to the OpenSSL change. I
(and as well Gregor) was able to reproduce it in the pbuilder setup
when using the default USENETWORK=no (but not if switching to
USENETWORK=yes). So #813189 on its own can be considered resolved.

Should openssl maybe have a Breaks for the older libio-socket-ssl-perl
version?

Regards,
Salvatore

Bug#813398: opensmtpd: segfaults when relaying email

2016-02-01 Thread Nicolas Évrard

Package: opensmtpd
Version: 5.7.3p1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I noticed that since the update of libssl1.0.2 to 1.0.2f-2 opensmtpd segfaults
shortly after connecting to my tls relay:

Feb  1 14:50:47 balisto smtpd[1630]: smtp-out: session 038f0ec33bb86f16: 
connecting to tls://IPv6:2001:41d0:2:49d2::1:587 (thales.b2ck.com)
Feb  1 14:50:48 balisto kernel: [38398.267130] smtpd[1630]: segfault at 0 
ip   (null) sp 7fffe7186358 error 14 in smtpd[40+6d000]

I tried rebuilding the package without much success.
Downgrading to libssl1.0.2 1.0.2e-1 made smtpd work again.

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

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

Versions of packages opensmtpd depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.58
ii  libasr01.0.2-1
ii  libc6  2.21-7
ii  libdb5.3   5.3.28-11
ii  libevent-2.0-5 2.0.21-stable-2+b1
ii  libpam0g   1.1.8-3.2
ii  libssl1.0.21.0.2f-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages opensmtpd recommends:
pn  opensmtpd-extras  

opensmtpd suggests no packages.

-- Configuration Files:
/etc/smtpd.conf changed [not included]

-- debconf information:
* opensmtpd/mailname: localhost.localdomain
* opensmtpd/root_address:

Bug#798601: limereg: FTBFS on mips/mipsel

2016-02-01 Thread Roelof Berg

I changed the compiler settings as suggested. This is only a hotfix to 
enable the package-build again. Because the underlying problem might be 
safety relevant (BOF) I added an entry to upstream's issue tracker and 
added a note to inform debian, when the compiler can be reverted to more 
strict settings again.


Being also upstream, I will adress further investigation with highest 
priority for the next version of Limereg.

Bug#808616: marked as done (python-releases: FTBFS: rm: cannot remove 'releases.egg-info': Is a directory)

Your message dated Mon, 01 Feb 2016 16:03:11 +
with message-id 
and subject line Bug#808616: fixed in python-releases 1.0.0-1
has caused the Debian Bug report #808616,
regarding python-releases: FTBFS:  rm: cannot remove 'releases.egg-info': Is a 
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.)


-- 
808616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-releases
Version: 0.7.0-2
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,

python-releases fails to build from source in unstable/amd64:

  [..]

 dh_auto_clean -O--buildsystem=pybuild
  I: pybuild base:184: python2.7 setup.py clean 
  running clean
  removing 
'/home/lamby/temp/cdt.20151221145520.ICaacETuZQ/python-releases-0.7.0/.pybuild/pythonX.Y_2.7/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-2.7' does not exist -- can't clean it
  I: pybuild base:184: python3.5 setup.py clean 
  running clean
  removing 
'/home/lamby/temp/cdt.20151221145520.ICaacETuZQ/python-releases-0.7.0/.pybuild/pythonX.Y_3.5/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-3.5' does not exist -- can't clean it
  I: pybuild base:184: python3.4 setup.py clean 
  running clean
  removing 
'/home/lamby/temp/cdt.20151221145520.ICaacETuZQ/python-releases-0.7.0/.pybuild/pythonX.Y_3.4/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-3.4' does not exist -- can't clean it
 dh_clean -O--buildsystem=pybuild
  rm: cannot remove 'releases.egg-info': Is a directory
  dh_clean: rm -f -- releases.egg-info returned exit code 1
  debian/rules:5: recipe for target 'clean' failed
  make: *** [clean] Error 1

  [..]

The full build log is attached.


Regards,

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


python-releases.0.7.0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-releases
Source-Version: 1.0.0-1

We believe that the bug you reported is fixed in the latest version of
python-releases, 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.
Jan Dittberner  (supplier of updated python-releases 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: SHA512

Format: 1.8
Date: Sat, 30 Jan 2016 20:10:52 +0100
Source: python-releases
Binary: python-releases python3-releases python-releases-doc
Architecture: source all
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Zygmunt Krynicki 
Changed-By: Jan Dittberner 
Description:
 python-releases - Sphinx extension for changelog manipulation (Python 2)
 python-releases-doc - Sphinx extension for changelog manipulation documentation
 python3-releases - Sphinx extension for changelog manipulation (Python 3)
Closes: 808616
Changes:
 python-releases (1.0.0-1) unstable; urgency=medium
 .
   * Team upload.
   * add missing trailing slash in debian/clean (Closes: #808616)
   * Use https URL for Vcs-Git in debian/control
   * Disable tests in debian/rules because they require spec which is not
 packaged for debian yet, remove python{3,}-docutils from Build-Depends
   * New upstream version
   * add new python-releases-doc binary package containing the Sphinx
 documentation
 - add stanza to debian/control
 - add sphinx-build invocation in debian/rules
 - add docs/_build/ to debian/clean
 - add debian/python-releases-doc.doc-base and
   debian/python-releases-doc.docs files
   * Add myself to copyright file, bump copyright years
   * patch README.rst to avoid privacy breach caused by included travis-ci
 image
   * patch docs/conf.py

Bug#797770: marked as done (shibboleth-sp2: library transition needed with GCC 5 as default)

Your message dated Mon, 01 Feb 2016 16:03:13 +
with message-id 
and subject line Bug#797770: fixed in shibboleth-sp2 2.5.5+dfsg1-1
has caused the Debian Bug report #797770,
regarding shibboleth-sp2: library transition needed with GCC 5 as default
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.)


-- 
797770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shibboleth-sp2
Version: 2.5.3+dfsg-2.1
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

your library exposes std::string or std::list in its public API, and
therefore the library package needs to be renamed.

Cheers,
Julien

The following is a form letter:

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 are using the new ABI.  Libraries built
from this source package export some of the new __cxx11 or B5cxx11 symbols, and
dropping other symbols.  If these symbols are part of the API of the library,
then this rebuild with g++-5 will trigger a transition for the library.

What is needed:

 - Rebuild the library using g++/g++-5. Note that most likely all C++
   libraries within the build dependencies need a rebuild too. You can
   find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150813/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: shibboleth-sp2
Source-Version: 2.5.5+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
shibboleth-sp2, 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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated shibboleth-sp2 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: Tue, 26 Jan 2016 21:09:23 +0100
Source: shibboleth-sp2
Binary: libapache2-mod-shib2 libshibsp6v5 libshibsp-plugins libshibsp-dev 
libshibsp-doc shibboleth-sp2-common shibboleth-sp2-utils
Architecture: source amd64 all
Version: 2.5.5+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Shib Team 
Changed-By: Ferenc Wágner 
Description:
 libapache2-mod-shib2 - Federated web single sign-on system (Apache

Processed: Bug#813399 marked as pending

Processing commands for cont...@bugs.debian.org:

> tag 813399 pending
Bug #813399 [python-pip-whl] python-pip-whl: fails to upgrade from 'testing' - 
trying to overwrite /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#813415: libvigraimpex5v5: soname bump without package name change

On 01.02.2016 18:52, Andreas Metzler wrote:
> Package: libvigraimpex5v5
> Version: 1.10.0+git20160120.803d5d4-1
> Severity: grave
> Justification: renders package unusable
> 
> (sid)ametzler@argenau:/usr/bin$ hugin
> hugin: error while loading shared libraries: libvigraimpex.so.5: cannot open 
> shared object file: No such file or directory
> 
> Going from 1.10.0+dfsg-11 to 1.10.0+git20160120.803d5d4-1 there is a
> soname change without a corresponding package name change. All reverse
> dependencies are broken:
> 
> 1. Uploaded before vigra: The stop running
> 2. Uploaded after vigra: They are built against the new vigra but
> still depend on libvigraimpex5v5. They will stop running if the reach
> testing.
> (sid)ametzler@argenau:/usr/bin$ for i in 
> /var/cache/apt/archives/libvigraimpex5v5_1.10.0+* ; do basename $i ; dpkg 
> --contents $i | grep '/usr/lib/l' ; done
> libvigraimpex5v5_1.10.0+dfsg-11_amd64.deb
> -rw-r--r-- root/root530744 2015-10-02 17:23 
> ./usr/lib/libvigraimpex.so.5.1.10.0
> lrwxrwxrwx root/root 0 2015-10-02 17:23 ./usr/lib/libvigraimpex.so.5 
> -> libvigraimpex.so.5.1.10.0
> libvigraimpex5v5_1.10.0+git20160120.803d5d4-1_amd64.deb
> -rw-r--r-- root/root543296 2016-01-27 07:30 
> ./usr/lib/libvigraimpex.so.6.1.10.0
> lrwxrwxrwx root/root 0 2016-01-27 07:30 ./usr/lib/libvigraimpex.so.6 
> -> libvigraimpex.so.6.1.10.0
> 
> cu Andreas

Hi Andreas,

I've expected this bug to appear now. I've already prepared a fix for -2, it's 
coming up very soon. 

Daniel

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Processed: Bug#813415 marked as pending

Processing commands for cont...@bugs.debian.org:

> tag 813415 pending
Bug #813415 [libvigraimpex5v5] libvigraimpex5v5: soname bump without package 
name change
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to dlm, tagging 813376

Processing commands for cont...@bugs.debian.org:

> limit source dlm
Limiting to bugs with field 'source' containing at least one of 'dlm'
Limit currently set to 'source':'dlm'

> tags 813376 + pending
Bug #813376 [dlm] dlm: B-D on obsolete package libsystemd-daemon-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#813417: enblend: Must not enter testing, built against broken vigra

2016-02-01 Thread Andreas Metzler

Package: enblend
Version: 4.1.4+dfsg-5
Severity: serious

enblend 4.1.4+dfsg-5 is built against
libvigraimpex/1.10.0+git20160120.803d5d4-1 and therefore must not enter
testing. See https://bugs.debian.org/813415

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#813399: marked as pending

2016-02-01 Thread Barry Warsaw

tag 813399 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/python-pip.git;a=commitdiff;h=af4faa1

---
commit af4faa13f52f7c14b5a06c77a5ff2aad20164fce
Author: Barry Warsaw 
Date:   Mon Feb 1 13:09:38 2016 -0500

d/control: Fix Breaks/Depends for python-pip-whl.  (Closes: #813399)

diff --git a/debian/changelog b/debian/changelog
index 686617a..6c49120 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 python-pip (8.0.2-3) UNRELEASED; urgency=medium
 
   * Fix python-pip Recommends of python-all-dev.  (Closes: #799559)
+  * d/control: Fix Breaks/Depends for python-pip-whl.  (Closes: #813399)
 
  -- Barry Warsaw   Sat, 30 Jan 2016 17:07:08 -0500

Bug#813415: marked as pending

tag 813415 pending
thanks

Hello,

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


http://git.debian.org/?p=debian-science/packages/libvigraimpex.git;a=commitdiff;h=2a5aae4

---
commit 2a5aae440bbb4c81dc2dece9045fc1504d9b4f32
Author: Daniel Stender 
Date:   Mon Feb 1 19:21:28 2016 +0100

deb/changelog: added Closes

diff --git a/debian/changelog b/debian/changelog
index 455ed50..c5689fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,12 +1,12 @@
 libvigraimpex (1.10.0+git20160120.803d5d4-2) UNRELEASED; urgency=medium
 
-  * Build libvigraimpex6.
+  * Build libvigraimpex6 (Closes: #813415).
   * deb/control: depend libvigraimpex-dev on libpng-dev [thanks to
 Tobias Frost].
   * deb/README.Debian: corrected typo.
   * Dropped deb/libvigraimpex5v5.lintian-overrides.
 
- -- Daniel Stender   Sun, 31 Jan 2016 00:20:21 +0100
+ -- Daniel Stender   Mon, 01 Feb 2016 19:20:49 +0100
 
 libvigraimpex (1.10.0+git20160120.803d5d4-1) unstable; urgency=medium

Bug#813406: ctdb, raw sockets and CVE-2015-8543

2016-02-01 Thread Adi Kriegisch

Package: ctdb
Severity: grave
Tags: patch,upstream

Hi!

The kernel upgrade for CVE-2015-8543 showed a bug in CTDB that leads to a
broken cluster:
  | s = socket(AF_INET, SOCK_RAW, htons(IPPROTO_RAW));
htons(IPPROTO_RAW) leads to 0xff00 which causes "-1 EINVAL (Invalid
argument)" because of CVE-2015-8543.
The fix for the issue is quite simple: remove IPPROTO_RAW; to make the fix
more consistent with what was used before, use IPPROTO_IP (which is 0).

Error messages related to this bug are:
  | We are still serving a public IP 'x.x.x.x' that we should not be serving. 
Removing it
  | common/system_common.c:89 failed to open raw socket (Invalid argument)
  | Could not find which interface the ip address is hosted on. can not release 
it
and 
  | common/system_linux.c:344 failed to open raw socket (Invalid argument)
As a result, IP addresses cannot be released and multiple nodes in the
cluster serve the same address, which obviously does not work.

Upstream bug: https://bugzilla.samba.org/show_bug.cgi?id=11705 and mailing
list conversation: 
https://lists.samba.org/archive/samba/2016-January/197389.html

-- Adi
--- a/common/system_common.c2016-01-19 15:20:37.437683526 +0100
+++ b/common/system_common.c2016-01-19 15:20:50.417683526 +0100
@@ -83,7 +83,7 @@
struct ifconf ifc;
char *ptr;

-   s = socket(AF_INET, SOCK_RAW, htons(IPPROTO_RAW));
+   s = socket(AF_INET, SOCK_RAW, IPPROTO_IP);
if (s == -1) {
DEBUG(DEBUG_CRIT,(__location__ " failed to open raw socket (%s)\n",
 strerror(errno)));
--- a/common/system_linux.c 2016-01-19 16:06:53.021491231 +0100
+++ b/common/system_linux.c 2016-01-19 16:07:05.817491231 +0100
@@ -338,7 +338,7 @@
ip4pkt.tcp.check= tcp_checksum((uint16_t *), sizeof(ip4pkt.tcp), );

/* open a raw socket to send this segment from */
-   s = socket(AF_INET, SOCK_RAW, htons(IPPROTO_RAW));
+   s = socket(AF_INET, SOCK_RAW, IPPROTO_IP);
if (s == -1) {
DEBUG(DEBUG_CRIT,(__location__ " failed to open raw socket (%s)\n",
 strerror(errno)));


signature.asc
Description: Digital signature

Processed: forcibly merging 807036 813112

Processing commands for cont...@bugs.debian.org:

> forcemerge 807036 813112
Bug #807036 [src:eztrace-contrib] package tries to link using /usr/lib/libbfd.a
Bug #813112 [src:eztrace-contrib] eztrace-contrib: FTBFS: cannot find libgtg
Added tag(s) pending.
Merged 807036 813112
> thanks
Stopping processing here.

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

Bug#813412: unattended-upgrades: FTBFS with testsuite errors