Processed: Re: Bug#820693: gdebi: Add flakes8 Build-Depends to fix FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #820693 [gdebi] gdebi: Add flakes8 Build-Depends to fix FTBFS
Added tag(s) patch.

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

Bug#820693: gdebi: Add flakes8 Build-Depends to fix FTBFS

[Petter Reinholdtsen]

Control: tags -1 + patch

Here is a patch to fix it.

-- 
Happy hacking
Petter Reinholdtsen
diff -ur gdebi-0.9.5.7/debian/changelog gdebi-0.9.5.7+nmu1/debian/changelog
--- gdebi-0.9.5.7/debian/changelog	2015-07-08 13:38:19.0 +
+++ gdebi-0.9.5.7+nmu1/debian/changelog	2016-05-17 05:37:22.879032101 +
@@ -1,3 +1,11 @@
+gdebi (0.9.5.7+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build dependencies, add pyflakes3 needed after package split
+(Closes: #820693).
+
+ -- Petter Reinholdtsen   Tue, 17 May 2016 05:37:22 +
+
 gdebi (0.9.5.7) unstable; urgency=medium
 
   [ Michael Vogt ]
diff -ur gdebi-0.9.5.7/debian/control gdebi-0.9.5.7+nmu1/debian/control
--- gdebi-0.9.5.7/debian/control	2015-01-29 14:00:39.0 +
+++ gdebi-0.9.5.7+nmu1/debian/control	2016-05-17 05:36:42.842755578 +
@@ -16,6 +16,7 @@
xvfb,
xauth,
pyflakes,
+   pyflakes3,
lintian,
 X-Python3-Version: >= 3.3
 Standards-Version: 3.9.6

Bug#816739: rsyslog-gnutls: imtcp/TLS hangs on dropped packages

[Michael Biebl]

On Thu, 10 Mar 2016 17:23:50 +0100 Luca BRUNO  wrote:
> On Wednesday, March 09, 2016 09:09:42 PM you wrote:
> 
> > I don't have the setup to test this. So if you want to see this fixed in
> > stable, it would be great if you can apply the upstream fix on top of
> > 8.4.2 and test whether it actually fixes the issue.
> 
> I have this running live in a log aggregation center, but unfortunately 
> reproducing this is somehow non-deterministic (it randomly happens from time 
> to time, after several weeks that it is running under moderate load, without 
> simple triggers).
> 
> I have now applied this patch on top of 8.4.2-1+deb8u2, and I'll let it run 
> for some time in the environment above to check if it still deadlocks 
> (however 
> I can't exclude false negatives if the bug doesn't trigger).

Any updates?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: severity of 816739 is important

[Debian Bug Tracking System]

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

> severity 816739 important
Bug #816739 [rsyslog-gnutls] rsyslog-gnutls: imtcp/TLS hangs on dropped packages
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#824517: gnome-builder: clashes with ecere-dev over /usr/bin/ide

[Aaron M. Ucko]

Package: gnome-builder
Version: 3.20.4-1
Severity: serious
Justification: Policy 6.6(4)

gnome-builder 3.20.x ships /usr/bin/ide, making it impossible to
install alongside ecere-dev:

  Unpacking gnome-builder (3.20.4-1) over (3.18.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gnome-builder_3.20.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/ide', which is also in package ecere-dev 
0.44.14-1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

"ide" is a sufficiently generic name that both packages should
arguably leave it alone, but ecere-dev took it first, so I'm reporting
this bug against gnome-builder.

Could you please address this clash?

Thanks!

Bug#822378: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 00:21:58 +
with message-id 
and subject line Bug#822393: fixed in linux 4.5.4-1
has caused the Debian Bug report #822393,
regarding  and  conflict needs to be resolved
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.)


-- 
822393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons
Version: 2.10-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[6]: Entering directory '/<>/extensions/pknock'
> gcc -DHAVE_CONFIG_H -I. -I../..  -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64  -D_REENTRANT -I../../include 
> -I/<>/extensions -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Waggregate-return -Wmissing-declarations  -Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Winline -pipe  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o pknlusr.o 
> pknlusr.c
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall -Waggregate-return 
> -Wmissing-declarations   -Wmissing-prototypes -Wredundant-decls -Wshadow 
> -Wstrict-prototypes -Winline -pipe  -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security  -Wl,-z,relro -o pknlusr pknlusr.o  
> libtool: link: gcc -Wall -Waggregate-return -Wmissing-declarations 
> -Wmissing-prototypes -Wredundant-decls -Wshadow -Wstrict-prototypes -Winline 
> -pipe -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z 
> -Wl,relro -o pknlusr pknlusr.o 
> make -f ../../Makefile.iptrules all;
> make[7]: Entering directory '/<>/extensions/pknock'
>   CC libxt_pknock.oo
> In file included from /usr/include/xtables.h:16:0,
>  from libxt_pknock.c:15:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
>   ^
> /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>  IFF_UP = 0x1,  /* Interface is up.  */
>  ^
> /usr/include/linux/if.h:72:2: error: redeclaration of enumerator 
> 'IFF_BROADCAST'
>   IFF_BROADCAST   = 1<<1,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was 
> here
>  IFF_BROADCAST = 0x2, /* Broadcast address valid.  */
>  ^
> /usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
>   IFF_DEBUG   = 1<<2,  /* sysfs */
>   ^
> /usr/include/net/if.h:48:5: note: previous definition of 'IFF_DEBUG' was here
>  IFF_DEBUG = 0x4,  /* Turn on debugging.  */
>  ^
> /usr/include/linux/if.h:74:2: error: redeclaration of enumerator 
> 'IFF_LOOPBACK'
>   IFF_LOOPBACK   = 1<<3,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:50:5: note: previous definition of 'IFF_LOOPBACK' was 
> here
>  IFF_LOOPBACK = 0x8,  /* Is a loopback net.  */
>  ^
> /usr/include/linux/if.h:75:2: error: redeclaration of enumerator 
> 'IFF_POINTOPOINT'
>   IFF_POINTOPOINT   = 1<<4,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:52:5: note: previous definition of 'IFF_POINTOPOINT' 
> was here
>  IFF_POINTOPOINT = 0x10, /* Interface is point-to-point link.  */
>  ^
> /usr/include/linux/if.h:76:2: error: redeclaration of enumerator 
> 'IFF_NOTRAILERS'
>   IFF_NOTRAILERS   = 1<<5,  /* sysfs */
>   ^
> /usr/include/net/if.h:54:5: note: previous definition of 'IFF_NOTRAILERS' was 
> here
>  IFF_NOTRAILERS = 0x20, /* Avoid use of trailers.  */
>  ^
> /usr/include/linux/if.h:77:2: error: redeclaration of enumerator 'IFF_RUNNING'
>   IFF_RUNNING   = 1<<6,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:56:5: note: previous definition of 'IFF_RUNNING' was 
> here
>  IFF_RUNNING = 0x40,  /* Resources allocated.  */
>  ^
> /usr/include/linux/if.h:78:2: error: redeclaration of enumerator 'IFF_NOARP'
>   IFF_NOARP   = 1<<7,  /* sysfs */
>   ^
> /usr/include/net/if.h:58:5: note: previous definition of 'IFF_NOARP' was here
>  IFF_NOARP = 0x80,  /* No address resolution protocol.  */
>  ^
> /usr/include/linux/if.h:79:2: error: redeclaration of enumerator 'IFF_PROMISC'
>   IFF_PROMISC   = 1<<8,  /* sysfs */
>   ^
> /usr/include/net/if.h:60:5: note: previous definition of 'IFF_PROMISC' was 
> here
>  IFF_PROMISC = 0x100, /* Receive all packets.  */
>  ^
> /usr/include/linux/if.h:80:2: error: redeclaration of enumerator 
> 'IFF_ALLMULTI'
>   IFF_ALLMULTI   = 1<<9,  /* sysfs */
>   ^
> /usr/include/net/if.h:64:5: note: previous definition of 

Bug#822396: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 00:21:58 +
with message-id 
and subject line Bug#822393: fixed in linux 4.5.4-1
has caused the Debian Bug report #822393,
regarding  and  conflict needs to be resolved
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../src/libstrongswan -I../../../../src/libcharon -Wdate-time 
> -D_FORTIFY_SOURCE=2 -rdynamic -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -include /<>/config.h -c 
> connmark_listener.c  -fPIC -DPIC -o .libs/connmark_listener.o
> In file included from /usr/include/libiptc/ipt_kernel_headers.h:13:0,
>  from /usr/include/libiptc/libiptc.h:6,
>  from connmark_listener.c:24:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
>   ^
> /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>  IFF_UP = 0x1,  /* Interface is up.  */
>  ^
> /usr/include/linux/if.h:72:2: error: redeclaration of enumerator 
> 'IFF_BROADCAST'
>   IFF_BROADCAST   = 1<<1,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was 
> here
>  IFF_BROADCAST = 0x2, /* Broadcast address valid.  */
>  ^
> /usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
>   IFF_DEBUG   = 1<<2,  /* sysfs */
>   ^
> /usr/include/net/if.h:48:5: note: previous definition of 'IFF_DEBUG' was here
>  IFF_DEBUG = 0x4,  /* Turn on debugging.  */
>  ^
> /usr/include/linux/if.h:74:2: error: redeclaration of enumerator 
> 'IFF_LOOPBACK'
>   IFF_LOOPBACK   = 1<<3,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:50:5: note: previous definition of 'IFF_LOOPBACK' was 
> here
>  IFF_LOOPBACK = 0x8,  /* Is a loopback net.  */
>  ^
> /usr/include/linux/if.h:75:2: error: redeclaration of enumerator 
> 'IFF_POINTOPOINT'
>   IFF_POINTOPOINT   = 1<<4,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:52:5: note: previous definition of 'IFF_POINTOPOINT' 
> was here
>  IFF_POINTOPOINT = 0x10, /* Interface is point-to-point link.  */
>  ^
> /usr/include/linux/if.h:76:2: error: redeclaration of enumerator 
> 'IFF_NOTRAILERS'
>   IFF_NOTRAILERS   = 1<<5,  /* sysfs */
>   ^
> /usr/include/net/if.h:54:5: note: previous definition of 'IFF_NOTRAILERS' was 
> here
>  IFF_NOTRAILERS = 0x20, /* Avoid use of trailers.  */
>  ^
> /usr/include/linux/if.h:77:2: error: redeclaration of enumerator 'IFF_RUNNING'
>   IFF_RUNNING   = 1<<6,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:56:5: note: previous definition of 'IFF_RUNNING' was 
> here
>  IFF_RUNNING = 0x40,  /* Resources allocated.  */
>  ^
> /usr/include/linux/if.h:78:2: error: redeclaration of enumerator 'IFF_NOARP'
>   IFF_NOARP   = 1<<7,  /* sysfs */
>   ^
> /usr/include/net/if.h:58:5: note: previous definition of 'IFF_NOARP' was here
>  IFF_NOARP = 0x80,  /* No address resolution protocol.  */
>  ^
> /usr/include/linux/if.h:79:2: error: redeclaration of enumerator 'IFF_PROMISC'
>   IFF_PROMISC   = 1<<8,  /* sysfs */
>   ^
> /usr/include/net/if.h:60:5: note: previous definition of 'IFF_PROMISC' was 
> here
>  IFF_PROMISC = 0x100, /* Receive all packets.  */
>  ^
> /usr/include/linux/if.h:80:2: error: redeclaration of enumerator 
> 'IFF_ALLMULTI'
>   IFF_ALLMULTI   = 1<<9,  /* sysfs */
>   ^
> /usr/include/net/if.h:64:5: note: previous definition of 'IFF_ALLMULTI' was 
> here
>  IFF_ALLMULTI = 0x200, /* Receive all multicast packets.  */
>  ^
> /usr/include/linux/if.h:81:2: error: redeclaration of enumerator 'IFF_MASTER'
>   IFF_MASTER   = 1<<10, /* __volatile__ */
>   ^
> /usr/include/net/if.h:67:5: note: previous definition of 'IFF_MASTER' was here
>  IFF_MASTER = 0x400,  /* Master of a load balancer.  */
>  ^
> /usr/include/linux/if.h:82:2: error: redeclaration of enumerator 'IFF_SLAVE'
>   IFF_SLAVE   = 1<<11, /* __volatile__ */
>   ^
> /usr/include/net/if.h:69:5: note: previous definition of 'IFF_SLAVE' was here
>  IFF_SLAVE = 0x800,  /* Slave of a load balancer.  */
>  ^
> /usr/include/linux/if.h:83:2: error: redeclaration of enumerator 
> 'IFF_MULTICAST'
>   

Bug#822393: marked as done ( and conflict needs to be resolved)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 00:21:58 +
with message-id 
and subject line Bug#822393: fixed in linux 4.5.4-1
has caused the Debian Bug report #822393,
regarding  and  conflict needs to be resolved
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.)


-- 
822393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: connman
Version: 1.21-1.2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> gcc -DHAVE_CONFIG_H -I.  -I./include -I./gdbus -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/p11-kit-1  
> -DCONNMAN_PLUGIN_BUILTIN -DSTATEDIR=\""/var/run/connman"\" 
> -DPLUGINDIR=\""/usr/lib/x86_64-linux-gnu/connman/plugins"\" 
> -DSCRIPTDIR=\""/usr/lib/x86_64-linux-gnu/connman/scripts"\" 
> -DSTORAGEDIR=\""/var/lib/connman\"" 
> -DVPN_STORAGEDIR=\""/var/lib/connman-vpn\"" -DCONFIGDIR=\""/etc/connman\"" 
> -I./src -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
> -o src/src_connmand-inotify.o `test -f 'src/inotify.c' || echo 
> './'`src/inotify.c
> In file included from /usr/include/xtables.h:16:0,
>  from src/iptables.c:33:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
>   ^
> /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>  IFF_UP = 0x1,  /* Interface is up.  */
>  ^
> /usr/include/linux/if.h:72:2: error: redeclaration of enumerator 
> 'IFF_BROADCAST'
>   IFF_BROADCAST   = 1<<1,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:46:5: note: previous definition of 'IFF_BROADCAST' was 
> here
>  IFF_BROADCAST = 0x2, /* Broadcast address valid.  */
>  ^
> /usr/include/linux/if.h:73:2: error: redeclaration of enumerator 'IFF_DEBUG'
>   IFF_DEBUG   = 1<<2,  /* sysfs */
>   ^
> /usr/include/net/if.h:48:5: note: previous definition of 'IFF_DEBUG' was here
>  IFF_DEBUG = 0x4,  /* Turn on debugging.  */
>  ^
> /usr/include/linux/if.h:74:2: error: redeclaration of enumerator 
> 'IFF_LOOPBACK'
>   IFF_LOOPBACK   = 1<<3,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:50:5: note: previous definition of 'IFF_LOOPBACK' was 
> here
>  IFF_LOOPBACK = 0x8,  /* Is a loopback net.  */
>  ^
> /usr/include/linux/if.h:75:2: error: redeclaration of enumerator 
> 'IFF_POINTOPOINT'
>   IFF_POINTOPOINT   = 1<<4,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:52:5: note: previous definition of 'IFF_POINTOPOINT' 
> was here
>  IFF_POINTOPOINT = 0x10, /* Interface is point-to-point link.  */
>  ^
> /usr/include/linux/if.h:76:2: error: redeclaration of enumerator 
> 'IFF_NOTRAILERS'
>   IFF_NOTRAILERS   = 1<<5,  /* sysfs */
>   ^
> /usr/include/net/if.h:54:5: note: previous definition of 'IFF_NOTRAILERS' was 
> here
>  IFF_NOTRAILERS = 0x20, /* Avoid use of trailers.  */
>  ^
> /usr/include/linux/if.h:77:2: error: redeclaration of enumerator 'IFF_RUNNING'
>   IFF_RUNNING   = 1<<6,  /* __volatile__ */
>   ^
> /usr/include/net/if.h:56:5: note: previous definition of 'IFF_RUNNING' was 
> here
>  IFF_RUNNING = 0x40,  /* Resources allocated.  */
>  ^
> /usr/include/linux/if.h:78:2: error: redeclaration of enumerator 'IFF_NOARP'
>   IFF_NOARP   = 1<<7,  /* sysfs */
>   ^
> /usr/include/net/if.h:58:5: note: previous definition of 'IFF_NOARP' was here
>  IFF_NOARP = 0x80,  /* No address resolution protocol.  */
>  ^
> /usr/include/linux/if.h:79:2: error: redeclaration of enumerator 'IFF_PROMISC'
>   IFF_PROMISC   = 1<<8,  /* sysfs */
>   ^
> /usr/include/net/if.h:60:5: note: previous definition of 'IFF_PROMISC' was 
> here
>  IFF_PROMISC = 0x100, /* Receive all packets.  */
>  ^
> /usr/include/linux/if.h:80:2: error: redeclaration of enumerator 
> 'IFF_ALLMULTI'
>   IFF_ALLMULTI   = 1<<9,  /* sysfs */
>   ^
> /usr/include/net/if.h:64:5: note: previous definition of 'IFF_ALLMULTI' was 
> here
>  IFF_ALLMULTI = 0x200, /* Receive all multicast packets.  */
>  ^
> /usr/include/linux/if.h:81:2: error: redeclaration of enumerator 'IFF_MASTER'
>   IFF_MASTER   = 1<<10, /* __volatile__ */
>   ^
> /usr/include/net/if.h:67:5: note: previous definition of 'IFF_MASTER' was here
>  IFF_MASTER = 0x400,  /* Master of a load balancer.  */
>  ^
> /usr/include/linux/if.h:82:2: error: redeclaration of 

Bug#824458: marked as done (xtables-addons: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 00:21:58 +
with message-id <e1b2slq-0004wh...@franck.debian.org>
and subject line Bug#822393: fixed in linux 4.5.4-1
has caused the Debian Bug report #822393,
regarding xtables-addons: FTBFS in testing
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.)


-- 
822393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xtables-addons
Version: 2.10-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


make[7]: Entering directory '/<>/extensions/pknock'
  CC libxt_pknock.oo
In file included from /usr/include/xtables.h:16:0,
 from libxt_pknock.c:15:
/usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
  IFF_UP= 1<<0,  /* sysfs */
  ^
/usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
 IFF_UP = 0x1,  /* Interface is up.  */
 ^


The full build log is attached.

Thanks.

xtables-addons_2.10-1_amd64-20160516-1230.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.5.4-1

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

Debian distribution maintenance software
pp.
Ben Hutchings <b...@decadent.org.uk> (supplier of updated linux 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, 16 May 2016 19:17:22 +0100
Source: linux
Binary: linux-source-4.5 linux-support-4.5.0-2 linux-doc-4.5 linux-manual-4.5 
linux-kbuild-4.5 linux-cpupower libcpupower0 libcpupower-dev linux-perf-4.5 
libusbip-dev usbip hyperv-daemons lockdep liblockdep4.5 liblockdep-dev 
linux-libc-dev linux-headers-4.5.0-2-all linux-headers-4.5.0-2-all-alpha 
kernel-image-4.5.0-2-alpha-generic-di nic-modules-4.5.0-2-alpha-generic-di 
nic-wireless-modules-4.5.0-2-alpha-generic-di 
nic-shared-modules-4.5.0-2-alpha-generic-di 
serial-modules-4.5.0-2-alpha-generic-di 
usb-serial-modules-4.5.0-2-alpha-generic-di 
ppp-modules-4.5.0-2-alpha-generic-di pata-modules-4.5.0-2-alpha-generic-di 
cdrom-core-modules-4.5.0-2-alpha-generic-di 
scsi-core-modules-4.5.0-2-alpha-generic-di 
scsi-modules-4.5.0-2-alpha-generic-di loop-modules-4.5.0-2-alpha-generic-di 
btrfs-modules-4.5.0-2-alpha-generic-di ext4-modules-4.5.0-2-alpha-generic-di 
isofs-modules-4.5.0-2-alpha-generic-di jfs-modules-4.5.0-2-alpha-generic-di 
xfs-modules-4.5.0-2-alpha-generic-di
 fat-modules-4.5.0-2-alpha-generic-di md-modules-4.5.0-2-alpha-generic-di 
multipath-modules-4.5.0-2-alpha-generic-di usb-modules-4.5.0-2-alpha-generic-di 
usb-storage-modules-4.5.0-2-alpha-generic-di 
fb-modules-4.5.0-2-alpha-generic-di input-modules-4.5.0-2-alpha-generic-di 
event-modules-4.5.0-2-alpha-generic-di mouse-modules-4.5.0-2-alpha-generic-di 
nic-pcmcia-modules-4.5.0-2-alpha-generic-di 
pcmcia-modules-4.5.0-2-alpha-generic-di 
nic-usb-modules-4.5.0-2-alpha-generic-di sata-modules-4.5.0-2-alpha-generic-di 
core-modules-4.5.0-2-alpha-generic-di crc-modules-4.5.0-2-alpha-generic-di 
crypto-modules-4.5.0-2-alpha-generic-di 
crypto-dm-modules-4.5.0-2-alpha-generic-di ata-modules-4.5.0-2-alpha-generic-di 
nbd-modules-4.5.0-2-alpha-generic-di squashfs-modules-4.5.0-2-alpha-generic-di 
virtio-modules-4.5.0-2-alpha-generic-di zlib-modules-4.5.0-2-alpha-generic-di 
fuse-modules-4.5.0-2-alpha-generic-di srm-modules-4.5.0-2-alpha-generic-di 
linux-headers-4.5.0-2-common
 linux-image-4.5.0-2-alpha-generic linux-headers-4.5.0-2-alpha-generic 
linux-image-4.5.0-2-alpha-smp linux-headers-4.5.0-2-alpha-smp 
linux-headers-4.5.0-2-all-amd64 kernel-image-4.5.0-2-amd64-di 
nic-modules-4.5.0-2-amd64-di nic-wireless-modules-4.5.0-2-amd64-di 
nic-shared-modules-4.5.0-2-amd64-di serial-modules-4.5.0-2-amd64-di 
usb-serial-modules-4.5.0-2-amd64-di ppp-modules-4.5.0-2-amd64-di 
pata-modules-4.5.0-2-amd64-di cdrom-co

Bug#824507: [Pkg-owncloud-maintainers] Bug#824507: Bug#824507: owncloud-client symbol lookup error

[Sandro Knauß]

Control: forwarded -1 https://github.com/owncloud/client/issues/4829

Hey,

well this issue is made up from owncloud repos. Inside debian there is no 
0.6.2-1. I was preparing 0.6.2 for debian, but actually stopped because of 
these symbol changes and filed a bug against qtkeychain to solve this.

https://github.com/frankosterfeld/qtkeychain/issues/73

Regards,

sandro


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

Processed: Re: [Pkg-owncloud-maintainers] Bug#824507: Bug#824507: owncloud-client symbol lookup error

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/owncloud/client/issues/4829
Bug #824507 [owncloud-client] owncloud-client symbol lookup error
Set Bug forwarded-to-address to 
'https://github.com/owncloud/client/issues/4829'.

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

Bug#824260: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Norbert Preining]

On Mon, 16 May 2016, Sebastiaan Couwenberg wrote:
> Adding --disable-upmendex to configure allows the build target to
> succeed, dh_install fails to install the missing texluajit files.

Thanks - the last thing is expected, need more trickery in the
config/control/rules. I will look into it and disable upmendex.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#822755: Upstream known and fixed bug with qt 5.6

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=360105
Control: tags -1 upstream fixed-upstream

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

Processed: Re: Bug#822755: Upstream known and fixed bug with qt 5.6

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugs.kde.org/show_bug.cgi?id=360105
Bug #822755 [kcalc] kcalc: When launching it nothing happens
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=360105'.
> tags -1 upstream fixed-upstream
Bug #822755 [kcalc] kcalc: When launching it nothing happens
Added tag(s) upstream and fixed-upstream.

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

Processed: Lost affects

[Debian Bug Tracking System]

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

> affects 824458 src:xtables-addons
Bug #824458 [src:linux] xtables-addons: FTBFS in testing
Bug #822378 [src:linux]  and  conflict needs to be 
resolved
Bug #822393 [src:linux]  and  conflict needs to be 
resolved
Bug #822396 [src:linux]  and  conflict needs to be 
resolved
Bug #824457 [src:linux] strongswan: FTBFS in testing
Added indication that 824458 affects src:xtables-addons
Added indication that 822378 affects src:xtables-addons
Added indication that 822393 affects src:xtables-addons
Added indication that 822396 affects src:xtables-addons
Added indication that 824457 affects src:xtables-addons
> thanks
Stopping processing here.

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

Processed: Reassign to linux

[Debian Bug Tracking System]

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

> reassign 824457 src:linux
Bug #824457 [src:strongswan] strongswan: FTBFS in testing
Bug reassigned from package 'src:strongswan' to 'src:linux'.
No longer marked as found in versions strongswan/5.4.0-1.
Ignoring request to alter fixed versions of bug #824457 to the same values 
previously set
> reassign 824458 src:linux
Bug #824458 [src:xtables-addons] xtables-addons: FTBFS in testing
Bug reassigned from package 'src:xtables-addons' to 'src:linux'.
No longer marked as found in versions xtables-addons/2.10-1.
Ignoring request to alter fixed versions of bug #824458 to the same values 
previously set
> affects 824457 src:strongswan
Bug #824457 [src:linux] strongswan: FTBFS in testing
Added indication that 824457 affects src:strongswan
> affects 824458 src:xtables-addons
Bug #824458 [src:linux] xtables-addons: FTBFS in testing
Added indication that 824458 affects src:xtables-addons
> forcemerge 824457 824458 822378
Bug #824457 [src:linux] strongswan: FTBFS in testing
Bug #822393 [src:linux]  and  conflict needs to be 
resolved
Added indication that 822393 affects src:strongswan
Added indication that 822378 affects src:strongswan
Added indication that 822396 affects src:strongswan
Bug #824458 [src:linux] xtables-addons: FTBFS in testing
Removed indication that 824458 affects src:xtables-addons
Added indication that 824458 affects src:strongswan
Marked as found in versions linux/4.5.1-1.
Bug #824457 [src:linux] strongswan: FTBFS in testing
Marked as found in versions linux/4.5.1-1.
Bug #822378 [src:linux]  and  conflict needs to be 
resolved
Bug #822396 [src:linux]  and  conflict needs to be 
resolved
Merged 822378 822393 822396 824457 824458
> thanks
Stopping processing here.

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

Bug#824507: [Pkg-owncloud-maintainers] Bug#824507: owncloud-client symbol lookup error

[David Prévot]

Hi,

> Package: owncloud-client
[…]
> trying to start the client I get this:
>
> leandro@sgorbio:~$ owncloud
> owncloud: symbol lookup error:
> /usr/lib/x86_64-linux-gnu/libowncloudsync.so.0: undefined symbol:
> _ZN9QKeychain16WritePasswordJob6setKeyERK7QString
[…]
> ii  libqtkeychain00.6.2-1.1

Where does that come from?

$ rmadison libqtkeychain0
libqtkeychain0 | 0.1.0-2~bpo70+1 | wheezy-backports |
libqtkeychain0 | 0.4.0-1 | stable   |
libqtkeychain0 | 0.4.0-1 | stable-kfreebsd  |
libqtkeychain0 | 0.5.0-1 | testing  |
libqtkeychain0 | 0.5.0-1 | unstable |

Regards

David

Bug#824260: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Sebastiaan Couwenberg]

On 05/16/2016 04:49 PM, Sebastiaan Couwenberg wrote:
> On 05/16/2016 03:16 PM, Norbert Preining wrote:
>> thanks a lot for testing. I there a porter box where I can test
>> it myself?
> 
> Yes, etler.debian.org, I used its sid_mipsel-dchroot for the test build.
> 
>>> I had to change the the CFLAGS option to use += -DU_IS_BIG_ENDIAN=0
>>> otherwise the build fails because CFLAGS references itself.
>>
>> Ahhh, I had the strange feeling that make and bash are different in
>> this respect ... sorry.
>>
>>> With that change the build still fails on mipsel porterbox:
>>
>> Bad, but this is at least a *different* error now, not related to
>> the ICE and upmendex/xetex, which is a bit better.
>>
>> Did the test run at least over the upmendex and xetex tests?
>>
>> What if you disable luajittex by removing it from the 
>>  LUAJIT_GOOD_ARCHS
>> list? After that it should compile without a problem???Hopefully.
> 
> I've remove mips & mipsel from LUAJIT_GOOD_ARCHS, I'll let you know when
> the results are in.

Adding --disable-upmendex to configure allows the build target to
succeed, dh_install fails to install the missing texluajit files.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#822755: Upstream known and fixed bug with qt 5.6

[Eric Valette]

So upstream beg to diffre and managed to reproduce the bug... Could you 
please rebuild with a fix...


https://quickgit.kde.org/?p=kcalc.git=commit=2678cb9c7a07381e3ffb8a2107946cec53bf5909

Processed: Re: [pkg-backupninja] Bug#824508: backupninja: Postgresql 9.4 backup databases = all crashes

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #824508 [backupninja] backupninja: Postgresql 9.4 backup databases = all 
crashes
Severity set to 'important' from 'critical'

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

Bug#824508: [pkg-backupninja] Bug#824508: backupninja: Postgresql 9.4 backup databases = all crashes

[intrigeri]

Control: severity -1 important

> Justification: causes serious data loss

I'm sorry, but we can't reasonably treat all bugs in backup software
as critical, at least as long as none of the original data that you're
backing up is lost, so I'm adjusting severity a bit.

Note that backupninja upstream is a sleepy state these days, so: good
patches are welcome :)

Cheers,
-- 
intrigeri

Bug#823750: Another out of bound

[Bastien ROUCARIES]

Fix an out of bound in psd file

Origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/533ea3b9047c67f9af49703de672f6c2e443f747
bug: https://github.com/ImageMagick/ImageMagick/issues/128
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1545180
bug-debian: https://bugs.debian.org/823750

Bug#790089: marked as done (FTBFS: makeinfo could not open stumpwm.texi: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 22:30:15 +0200
with message-id <874m9xg2zs@zamazal.org>
and subject line Re: FTBFS: makeinfo could not open stumpwm.texi: No such file 
or directory
has caused the Debian Bug report #790089,
regarding FTBFS: makeinfo could not open stumpwm.texi: 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.)


-- 
790089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stumpwm
Version: 2:0.9.9-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs


Dear Maintainer,

The package fails to build:

(SB-IMPL::READER-FIND-PACKAGE "STUMPWM" #)
0] 
* makeinfo stumpwm.texi
could not open stumpwm.texi: No such file or directory
Makefile:36: recipe for target 'stumpwm.info' failed
make[1]: *** [stumpwm.info] Error 1

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

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

Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
There used to be problems with building stumpwm on sid.  I believe those
problems were fixed with the recent cl-clx-sbcl update in sid and
stumpwm builds fine for me on current sid now.--- End Message ---

Bug#823750: Fix an out of bound in generic decoder

[Bastien ROUCARIES]

Fix an out of bound in generic decoder

Origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/430403b0029b37decf216d57f810899cab2317dd
bug-ubuntu: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1542785
bug-debian: https://bugs.debian.org/823750
bug: https://github.com/ImageMagick/ImageMagick/issues/126

Bug#824508: backupninja: Postgresql 9.4 backup databases = all crashes

[Christof Thalhofer]

Package: backupninja
Version: 1.0.1-2
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

backupninja PostgreSQL backup crashes since Jessie when the configuration 
option databases = all is choosen. On my system backupninja with pg_dumpall 
does something crazy, greating a lot of garbage dumps with size of 0 byte. It 
seems, that backupninja wants to dump these senseless databases:

su 29 [[ not found 35 [[ not found ... and so on.

Here is what backupninja sends in a mail:

== warnings from /etc/backup.d/20.webback.pgsql ==

Info: Successfully finished pgsql globals (roles and tablespaces) dump
Warning: /usr/lib/postgresql/9.4/bin/pg_dump: Ungültige Option -- u
Versuchen Sie „pg_dump --help“ für weitere Informationen.
Warning: Failed to dump pgsql database -su:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „29:“
fehlgeschlagen: FATAL: Datenbank „29:“ existiert nicht
Warning: Failed to dump pgsql database 29:
Warning: -su:
/var/backups/bninja-webback/postgres//usr/share/bash-completion/bash_completion:.pg_dump:
Datei oder Verzeichnis nicht gefunden
Warning: Failed to dump pgsql database
/usr/share/bash-completion/bash_completion:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „[[:“
fehlgeschlagen: FATAL: Datenbank „[[:“ existiert nicht
Warning: Failed to dump pgsql database [[:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „not“
fehlgeschlagen: FATAL: Datenbank „not“ existiert nicht
Warning: Failed to dump pgsql database not
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „found“
fehlgeschlagen: FATAL: Datenbank „found“ existiert nicht
Warning: Failed to dump pgsql database found
Warning: /usr/lib/postgresql/9.4/bin/pg_dump: Ungültige Option -- u
Versuchen Sie „pg_dump --help“ für weitere Informationen.
Warning: Failed to dump pgsql database -su:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „35:“
fehlgeschlagen: FATAL: Datenbank „35:“ existiert nicht
Warning: Failed to dump pgsql database 35:
Warning: -su:
/var/backups/bninja-webback/postgres//usr/share/bash-completion/bash_completion:.pg_dump:
Datei oder Verzeichnis nicht gefunden
Warning: Failed to dump pgsql database
/usr/share/bash-completion/bash_completion:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „[[:“
fehlgeschlagen: FATAL: Datenbank „[[:“ existiert nicht
Warning: Failed to dump pgsql database [[:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „not“
fehlgeschlagen: FATAL: Datenbank „not“ existiert nicht
Warning: Failed to dump pgsql database not
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „found“
fehlgeschlagen: FATAL: Datenbank „found“ existiert nicht
Warning: Failed to dump pgsql database found
Warning: /usr/lib/postgresql/9.4/bin/pg_dump: Ungültige Option -- u
Versuchen Sie „pg_dump --help“ für weitere Informationen.
Warning: Failed to dump pgsql database -su:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „51:“
fehlgeschlagen: FATAL: Datenbank „51:“ existiert nicht
Warning: Failed to dump pgsql database 51:
Warning: -su:
/var/backups/bninja-webback/postgres//usr/share/bash-completion/bash_completion:.pg_dump:
Datei oder Verzeichnis nicht gefunden
Warning: Failed to dump pgsql database
/usr/share/bash-completion/bash_completion:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „shopt:“
fehlgeschlagen: FATAL: Datenbank „shopt:“ existiert nicht
Warning: Failed to dump pgsql database shopt:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „not“
fehlgeschlagen: FATAL: Datenbank „not“ existiert nicht
Warning: Failed to dump pgsql database not
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „found“
fehlgeschlagen: FATAL: Datenbank „found“ existiert nicht
Warning: Failed to dump pgsql database found
Warning: /usr/lib/postgresql/9.4/bin/pg_dump: Ungültige Option -- u
Versuchen Sie „pg_dump --help“ für weitere Informationen.
Warning: Failed to dump pgsql database -su:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „57:“
fehlgeschlagen: FATAL: Datenbank „57:“ existiert nicht
Warning: Failed to dump pgsql database 57:
Warning: -su:
/var/backups/bninja-webback/postgres//usr/share/bash-completion/bash_completion:.pg_dump:
Datei oder Verzeichnis nicht gefunden
Warning: Failed to dump pgsql database
/usr/share/bash-completion/bash_completion:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank
„complete:“ fehlgeschlagen: FATAL: Datenbank „complete:“ existiert nicht
Warning: Failed to dump pgsql database complete:
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „not“
fehlgeschlagen: FATAL: Datenbank „not“ existiert nicht
Warning: Failed to dump pgsql database not
Warning: pg_dump: [Archivierer (DB)] Verbindung zur Datenbank „found“
fehlgeschlagen: FATAL: Datenbank „found“ existiert nicht
Warning: Failed to dump pgsql database found
Warning: /usr/lib/postgresql/9.4/bin/pg_dump: Ungültige Option -- u
Versuchen Sie 

Bug#824507: owncloud-client symbol lookup error

[Leandro sullo sgorbio]

Package: owncloud-client
Version: 2.1.1+dfsg-1~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the new (2.2.0-2.2) and the old version (2.1.1+dfsg-1) suffers the same error,
trying to start the client I get this:

leandro@sgorbio:~$ owncloud 
owncloud: symbol lookup error: /usr/lib/x86_64-linux-gnu/libowncloudsync.so.0: 
undefined symbol: _ZN9QKeychain16WritePasswordJob6setKeyERK7QString

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages owncloud-client depends on:
ii  libc6 2.19-18+deb8u4
ii  libgcc1   1:4.9.2-10
ii  libowncloudsync0  2.1.1+dfsg-1~bpo8+1
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt5sql5-sqlite 5.3.2+dfsg-4+deb8u1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtkeychain00.6.2-1.1
ii  libqtwebkit4  2.3.4.dfsg-3
ii  libssl1.0.0   1.0.2d-1
ii  libstdc++64.9.2-10
ii  owncloud-client-l10n  1.7.0~beta1+really1.6.4+dfsg-1+deb8u1

owncloud-client recommends no packages.

owncloud-client suggests no packages.

-- Configuration Files:
/etc/sysconf.d/100-owncloud-inotify.conf a4b015d9a5dc4ea142b9cee49b4830c9 
[Errno 2] File o directory non esistente: 
u'/etc/sysconf.d/100-owncloud-inotify.conf a4b015d9a5dc4ea142b9cee49b4830c9'

-- no debconf information

Bug#823750: LP1542125

[Bastien ROUCARIES]

Fixed by previous commit

Bug#823750: New bug

[Bastien ROUCARIES]

Fix a wpg file out of bound

Origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/bef1e4f637d8f665bc133a9c6d30df08d983bc3a
bug: https://github.com/ImageMagick/ImageMagick/issues/120
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1542114
bug-debian: https://bugs.debian.org/823750
bug: https://github.com/ImageMagick/ImageMagick/issues/120

Bug#823750: Already fixed

[Bastien ROUCARIES]

https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1542112 is
fixed by previous commit

Bug#823750: Not a concern

[Bastien ROUCARIES]

Because we do not enable accelerate we are not affected by
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1542111

Bug#823830: qemu: CVE-2016-3710 CVE-2016-3712

[Cristian Aires]

Hello,

All types of video models are affected?

The default is cirrus.

On Mon, 09 May 2016 14:22:37 +0200 Salvatore Bonaccorso 
wrote:
> Source: qemu
> Version: 2.1+dfsg-1
> Severity: grave
> Tags: security upstream
>
> Hi,
>
> the following vulnerabilities were published for qemu.
>
> CVE-2016-3710[0]:
> incorrect banked access bounds checking in vga module
>
> CVE-2016-3712[1]:
> Out-of-bounds read when creating weird vga screen surface
>
> If you fix the vulnerabilities please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2016-3710
> [1] https://security-tracker.debian.org/tracker/CVE-2016-3712
> [2] http://xenbits.xen.org/xsa/advisory-179.html
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore
>
>

Bug#824426: syncevolution quits with SIGABRT

[Justus-dev]

Hi -

Syncevolution now quits, before producing any console output, with a
SIGABRT.  This apparently happens since I upgraded evolution and
associated libraries to 3.18.5.1-1+b1 this morning, the only change
being "Rebuild against libical2".  It seems to me that this may well be
related to this bug, syncevolution now being incompatible with the rest
of the evolution ecosystem.

The sync log file ends with the lines:

  [2016-05-16 18:58:50.120] stderr: syncevolution: 
/tmp/buildd/libical-1.0.1/src/libical/icalarray.c:146:
  icalarray_element_at: Assertion `(unsigned int)position < 
array->num_elements' failed.

Here are the last few lines of "syncevolution --daemon=no" under strace:

write(2, "syncevolution: /tmp/buildd/libic"..., 157) = 157
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f09dad8e000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(11827, 11827, SIGABRT)   = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=11827, si_uid=1000} ---
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f09d94b6d30}, {SIG_DFL, [], 
0}, 8) = 0
alarm(5)= 0
recvfrom(6, "syncevolution: /tmp/buildd/libic"..., 1023, MSG_PEEK|MSG_DONTWAIT, 
NULL, NULL) = 157
recvfrom(6, NULL, 0, MSG_DONTWAIT, NULL, NULL) = 0
write(9, "  [2016-05-16 18:52:38.50"..., 220) = 220
recvfrom(6, 0x555b500a1080, 1023, 66, 0, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
dup2(4, 2)  = 2
close(4)= 0
close(5)= 0
close(6)= 0
tgkill(11827, 11827, SIGABRT)   = 0
rt_sigreturn({mask=[]}) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=11827, si_uid=1000} ---
+++ killed by SIGABRT +++

Regards,
Justus

Bug#824457: [Pkg-swan-devel] Bug#824457: strongswan: FTBFS in testing

[Santiago Vila]

On Mon, 16 May 2016, Yves-Alexis Perez wrote:

> Please investigate #822396 before?

Ok, yes, I'll investigate and will merge/reassign as appropriate.

For the record, avoiding this kind of duplicates is what the "affects"
keyword in the BTS is for. I promise that I looked at the bug page
for this package before submitting this report!

Thanks.

Bug#805144: marked as done (libmongodbx-class-perl: FTBFS: Attribute (bson_codec) is required at constructor)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 18:35:26 +
with message-id 
and subject line Bug#824396: Removed package(s) from unstable
has caused the Debian Bug report #805144,
regarding libmongodbx-class-perl: FTBFS: Attribute (bson_codec) is required at 
constructor
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.)


-- 
805144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmongodbx-class-perl
Version: 1.030002-1 
Severity: serious
Tags: sid stretch

This package fails to build on current sid. Looking at
 https://reproducible.debian.net/history/libmongodbx-class-perl.html
this regressed between 2015-10-21 and 2015-11-02.


  PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" 
t/*.t
  # Testing MongoDBx::Class 1.030002, Perl 5.020002, /usr/bin/perl
  t/00-load.t  
  1..1
  ok 1 - use MongoDBx::Class;
  ok
  Attribute (bson_codec) is required at constructor 
MongoDBx::Class::Database::new (defined at 
/build/libmongodbx-class-perl-1.030002/blib/lib/MongoDBx/Class/Database.pm line 
110) line 22
  MongoDBx::Class::Database::new('MongoDBx::Class::Database', '_client', 
'MongoDBx::Class::Connection=HASH(0x54f41c8)', 'name', 'mongodbx_class_test') 
called at 
/build/libmongodbx-class-perl-1.030002/blib/lib/MongoDBx/Class/Connection.pm 
line 102
  
MongoDBx::Class::Connection::__ANON__('MongoDBx::Class::Connection=HASH(0x54f41c8)',
 'mongodbx_class_test') called at 
/usr/lib/x86_64-linux-gnu/perl5/5.20/Moose/Meta/Method/Overridden.pm line 38
  
MongoDBx::Class::Connection::get_database('MongoDBx::Class::Connection=HASH(0x54f41c8)',
 'mongodbx_class_test') called at t/01-simple.t line 31
  # Looks like you planned 32 tests but ran 2.
  # Looks like your test exited with 255 just after 2.
  t/01-simple.t .. 
  1..32
  ok 1 - successfully loaded schema
  ok 2 - Using safe operations by default
  Dubious, test returned 255 (wstat 65280, 0xff00)
  [...]
  Test Summary Report
  ---
  t/01-simple.t(Wstat: 65280 Tests: 2 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 32 tests but ran 2.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Version: 1.030002-1+rm

Dear submitter,

as the package libmongodbx-class-perl 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/824396

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#821659: make slbackup-php PHP 7.0 compliant

[Wolfgang Schweer]

This patch should be enough, no need to package newer upstream release
(the split() function is deprecated since PHP 5.3.0 and gone in 7.0).


diff --git a/debian/control b/debian/control
index 68f7eac..1b15544 100644
--- a/debian/control
+++ b/debian/control
@@ -17,12 +17,12 @@ Package: slbackup-php
 Architecture: all
 Depends:
  ${misc:Depends},
- libapache2-mod-php5 | php5-cgi,
+ php,
  apache2 | httpd,
  ssh,
- php5-cli,
+ php-cli,
  smarty3,
- smarty-gettext (>= 1.0b1-7),
+ smarty-gettext,
 Suggests:
  x-www-browser,
  slbackup,
diff --git a/src/functions.php b/src/functions.php
index 7f52734..89524da 100644
--- a/src/functions.php
+++ b/src/functions.php
@@ -75,7 +75,7 @@ function loadLocale () {
$lang_accept = array () ; 
$lang_accept = explode (",", $_SERVER['HTTP_ACCEPT_LANGUAGE']); 
for ($i = 0 ; $i < count ($lang_accept) ; $i++ ) {
-   $lang_accept[$i] = split(";", $lang_accept[$i]) ; 
+   $lang_accept[$i] = preg_split(';', $lang_accept[$i]) ;
$lang_accept[$i] = $lang_accept[$i][0] ; 
}
 
@@ -101,13 +101,13 @@ function loadLocale () {
$locales = array();
$locales_utf8 = array();
if (isset($found_locale) && !empty($lang_accept[0])) {
-   $found_locale_tuple = split('_', $found_locale);
+   $found_locale_tuple = preg_split('_', $found_locale);
if (count($found_locale_tuple) > 1) {
$locales[] = $found_locale;
$locales_utf8[] = $found_locale.'.UTF-8';
}
foreach ($lang_accept as $lang) {
-   $lang_tuple = split('-',$lang);
+   $lang_tuple = preg_split('-',$lang);
if (count($lang_tuple) > 1) {
$language = strtolower($lang_tuple[0]);
$country = strtoupper($lang_tuple[1]);


Wolfgang


signature.asc
Description: Digital signature

Bug#821661: make smarty-gettext PHP 7.0 compliant

[Wolfgang Schweer]

This patch should do it:


diff --git a/debian/control b/debian/control
index 0444836..777fe85 100644
--- a/debian/control
+++ b/debian/control
@@ -13,7 +13,7 @@ Package: smarty-gettext
 Architecture: all
 Depends: ${misc:Depends},
  ${phpcomposer:Debian-require},
- php5-cli,
+ php-cli,
  smarty3,
  gettext,
 Description: Gettext plugin enabling internationalization in Smarty


Wolfgang


signature.asc
Description: Digital signature

Bug#821660: make smarty3 PHP 7.0 compliant

[Wolfgang Schweer]

This patch should make smarty3 PHP 7.0 compliant.
 

diff --git a/debian/README.Debian b/debian/README.Debian
index 78893ff..5d392cf 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -2,8 +2,8 @@ smarty3 for Debian
 --
 
 In order to use Smarty 3 from your php scripts, you'll have to add
-/usr/share/php/smarty3 on the include_path of php5, that is in the
-file /etc/php5/{apache,apache2}/php.ini or use
+/usr/share/php/smarty3 on the include_path of php, that is in the
+file /etc/php/{apache,apache2}/php.ini or use
 require("smarty3/Smarty.class.php");
 
 On smarty update, please note you will have to clear out all smarty
diff --git a/debian/control b/debian/control
index bf94986..84c4b5b 100644
--- a/debian/control
+++ b/debian/control
@@ -12,7 +12,7 @@ Homepage: http://www.smarty.net/
 Package: smarty3
 Architecture: all
 Depends:
- php5 | php5-cgi | php5-cli,
+ php | php-cgi | php-cli,
  ${misc:Depends}
 Provides:
  smarty


Wolfgang


signature.asc
Description: Digital signature

Bug#824485: [Pkg-clamav-devel] Bug#824485: clamav-freshclam: Segfault

[Kurt Roeckx]

On Mon, May 16, 2016 at 07:05:01PM +0200, Sebastian Andrzej Siewior wrote:
> On 2016-05-16 17:32:55 [+0200], Kurt Roeckx wrote:
> > Received signal: wake up
> > ClamAV update process started at Mon May 16 15:52:55 2016
> > main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: 
> > amishhammer)
> > Downloading daily-21555.cdiff [100%]
> > Downloading daily-21556.cdiff [100%]
> > ERROR: Database load killed by signal 11
> > ERROR: Failed to load new database
> 
> Could you please install the dbg package for freshclam + libclamav7 and send
> a gdb backtrace?

I just noticed that libclamav7 is still the 99.1 version.  It
seems to have a new dependency and so an "upgrade" didn't upgrade
that.

After having upgraded that, it works.

I'm guessing there is some ABI breakage between the 2 versions.


Kurt

Bug#824465: littler: FTBFS in testing

[Santiago Vila]

I wish everybody fixed FTBFS bugs as fast as you.
Thanks a lot!

Processed: fixed 824475 in python-mne/0.12+dfsg-1

[Debian Bug Tracking System]

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

> fixed 824475 python-mne/0.12+dfsg-1
Bug #824475 [src:python-mne] python-mne: FTBFS: TraitError: The 'input' trait 
of a QuadricDecimation instance is 'read only'.
Marked as fixed in versions python-mne/0.12+dfsg-1.
> thanks
Stopping processing here.

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

Bug#824485: [Pkg-clamav-devel] Bug#824485: clamav-freshclam: Segfault

[Sebastian Andrzej Siewior]

On 2016-05-16 17:32:55 [+0200], Kurt Roeckx wrote:
> Received signal: wake up
> ClamAV update process started at Mon May 16 15:52:55 2016
> main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: 
> amishhammer)
> Downloading daily-21555.cdiff [100%]
> Downloading daily-21556.cdiff [100%]
> ERROR: Database load killed by signal 11
> ERROR: Failed to load new database

Could you please install the dbg package for freshclam + libclamav7 and send
a gdb backtrace?
I have here:
|# freshclam 
|ClamAV update process started at Mon May 16 19:02:44 2016
|main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: 
amishhammer)
|Downloading daily-21518.cdiff [100%]
…
|Downloading daily-21555.cdiff [100%]
|Downloading daily-21556.cdiff [100%]
|daily.cld updated (version: 21556, sigs: 143888, f-level: 63, builder: neo)
|bytecode.cvd is up to date (version: 277, sigs: 47, f-level: 63, builder: neo)
|Database updated (4362725 signatures) from db.fr.clamav.net (IP: 178.32.100.7)
|Clamd successfully notified about the update.

on my sid-amd64 box.

> Kurt

Sebastian

Bug#824008: marked as done (python-xdo: FTBFS: ImportError: No module named 'six')

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 16:24:15 +
with message-id 
and subject line Bug#824008: fixed in python-xdo 0.3-2
has caused the Debian Bug report #824008,
regarding python-xdo: FTBFS: ImportError: No module named 'six'
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.)


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

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

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'python-xdo-build-deps' in 
'../python-xdo-build-deps_0.3-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package python-xdo-build-deps.
  (Reading database ... 23076 files and directories currently installed.)
  Preparing to unpack python-xdo-build-deps_0.3-1_all.deb ...
  Unpacking python-xdo-build-deps (0.3-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxdo3 libxext6 libxi6
libxinerama1 libxkbcommon0 libxtst6 python-all python-setuptools python3-all
python3-pkg-resources python3-setuptools x11-common xkb-data
  Suggested packages:
python-setuptools-doc
  The following NEW packages will be installed:
libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxdo3 libxext6 libxi6
libxinerama1 libxkbcommon0 libxtst6 python-all python-setuptools python3-all
python3-pkg-resources python3-setuptools x11-common xkb-data
  0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 2607 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 libxau6 amd64 
1:1.0.8-1 [20.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libxdmcp6 amd64 
1:1.1.2-1.1 [26.2 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libxcb1 amd64 
1.11.1-1 [44.1 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libx11-data all 
2:1.6.3-1 [128 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libx11-6 amd64 
2:1.6.3-1 [742 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libxext6 amd64 
2:1.3.3-1 [52.7 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libxinerama1 amd64 
2:1.1.3-1+b1 [16.9 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 xkb-data all 2.17-1 
[627 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 libxkbcommon0 amd64 
0.5.0-1 [121 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libxi6 amd64 
2:1.7.6-1 [80.6 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 x11-common all 
1:7.7+15 [251 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libxtst6 amd64 
2:1.2.2-1+b1 [27.3 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libxdo3 amd64 
1:3.20150503.1-2 [32.2 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-1 [936 B]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 python-setuptools 
all 20.10.1-1 [203 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 python3-all amd64 
3.5.1-3 [936 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 
python3-pkg-resources all 20.10.1-1 [112 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 python3-setuptools 
all 20.10.1-1 [122 kB]
  Fetched 2607 kB in 0s (36.7 MB/s)
  Selecting previously unselected package libxau6:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%

Bug#824485: clamav-freshclam: Segfault

[Kurt Roeckx]

Package: clamav-freshclam
Version: 0.99.2+dfsg-1
Severity: serious

Hi,

I did an update of various packages today including clamav from
0.99.1+dfsg-1+b2 to 0.99.2+dfsg-1.

My kernel log contains things like:
freshclam[19891]: segfault at 34 ip 7f2f1b193e3a sp 7ffcafe2f450 error 
4 in libclamav.so.7.1.1[7f2f1b0c6000+1a]

The freshclam.log file contains things like:
Received signal: wake up
ClamAV update process started at Mon May 16 14:52:54 2016
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: 
amishhammer)
Downloading daily-21555.cdiff [100%]
ERROR: Database load killed by signal 11
ERROR: Failed to load new database
--
Received signal: wake up
ClamAV update process started at Mon May 16 15:52:55 2016
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: 
amishhammer)
Downloading daily-21555.cdiff [100%]
Downloading daily-21556.cdiff [100%]
ERROR: Database load killed by signal 11
ERROR: Failed to load new database


Kurt

Bug#824008: marked as pending

[Daniel Kahn Gillmor]

tag 824008 pending
thanks

Hello,

Bug #824008 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-xdo.git;a=commitdiff;h=d244de4

---
commit d244de46c8e409d7f5dbd036ce91a12f2be696cd
Author: Daniel Kahn Gillmor 
Date:   Mon May 16 10:52:04 2016 -0400

clean up dependencies (Closes: #824008)

diff --git a/debian/changelog b/debian/changelog
index 6e13e5a..139ae32 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-xdo (0.3-2) unstable; urgency=medium
+
+  * clean up dependencies (Closes: #824008)
+
+ -- Daniel Kahn Gillmor   Mon, 16 May 2016 10:46:52 
-0400
+
 python-xdo (0.3-1) unstable; urgency=medium
 
   * new upstream release (based on ctypes, now Arch: all)

Processed: Bug#824008 marked as pending

[Debian Bug Tracking System]

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

> tag 824008 pending
Bug #824008 [src:python-xdo] python-xdo: FTBFS: ImportError: No module named 
'six'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824260: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Sebastiaan Couwenberg]

On 05/16/2016 03:16 PM, Norbert Preining wrote:
> thanks a lot for testing. I there a porter box where I can test
> it myself?

Yes, etler.debian.org, I used its sid_mipsel-dchroot for the test build.

>> I had to change the the CFLAGS option to use += -DU_IS_BIG_ENDIAN=0
>> otherwise the build fails because CFLAGS references itself.
> 
> Ahhh, I had the strange feeling that make and bash are different in
> this respect ... sorry.
> 
>> With that change the build still fails on mipsel porterbox:
> 
> Bad, but this is at least a *different* error now, not related to
> the ICE and upmendex/xetex, which is a bit better.
> 
> Did the test run at least over the upmendex and xetex tests?
> 
> What if you disable luajittex by removing it from the 
>   LUAJIT_GOOD_ARCHS
> list? After that it should compile without a problem???Hopefully.

I've remove mips & mipsel from LUAJIT_GOOD_ARCHS, I'll let you know when
the results are in.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#823112: freeradius-client is still in active development

[Alan DeKok]

  The repository was forked by "nmav" because we had technical disagreements 
about the code.

  The "freeradius-client" code still works, and has 99% of the functionality 
needed by an application using RADIUS.

  If an application needs more functionality, I would suggest using the 
libfreeradius-radius library from the main server distribution.  It has many 
more features, such as RFC 6929 "extended" attributes.

  Alan DeKok.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#808518: Please port to clutter-gst-3.0

[Michael Biebl]

Am 16.05.2016 um 15:47 schrieb Michael Biebl:
> Fwiw, there is a new upstream release 1.0.0 available which has been
> ported to clutter-3.0 [1]


Small correction: version 1.0.0 does not contain that commit as can be
seen at https://git.gnome.org/browse/snappy/log/

Based on 1.0.0, it should be simple though to cherry-pick the
clutter-gst related commits.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#824011: warzone2100: FTBFS in testing (maybe missing Build-Conflicts)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #824011 [src:warzone2100] warzone2100: FTBFS in testing (maybe missing 
Build-Conflicts)
Severity set to 'normal' from 'serious'

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

Bug#824011: warzone2100: FTBFS in testing (maybe missing Build-Conflicts)

[Markus Koschany]

Control: severity -1 normal

How come I am not surprised about your reaction and this reminds me of
the discussion we had about Bullet and the bug you eventually closed.
Again, if you disagree with maintainer decisions, then just don't raise
the severity again. Try to respect your fellow maintainers for once or
ask yourself if probably you are the one who has come to the wrong
conclusion. Not every bug is release critical.

Try to make your point but if the maintainer still disagrees and you
think he or she is totally wrong, please forward this issue to the CTTE.
Full stop. No severity bumping will ever make your argument right or
solve an issue quicker.

Am 16.05.2016 um 03:27 schrieb Santiago Vila:
> severity 824011 serious
> thanks
> 
> On Mon, May 16, 2016 at 02:17:23AM +0200, Markus Koschany wrote:
> 
>> I have just rebuilt warzone2100 in a clean sid cowbuilder chroot.
> 
> Well, if that's all you did, then I would say that you didn't
> understand the nature of the problem.
> 
> I'll try to explain better below.
> 
>> Everything went fine. Currently automake 1.11 is automatically installed
>> but this might change in the future so we should keep an eye on this
>> issue. I don't consider this to be release critical at the moment as
>> long as warzone2100 can be built from source in a default chroot
>> environment but I leave the rest to pabs, if he should feel differently
>> about that.
> 
> That's precisely the problem: chroots do *not* have to be "default",
> and that's precisely why Build-Conflicts exists at all.
> 
> Moreover, my chroot was pretty "standard" as it had debhelper installed
> by default, nothing really strange.
> 
> This is a FTBFS bug. Please read Debian Policy about Build-Conflicts
> before modifying severity again.

warzone2100 build-depends on automake1.11. I know the paragraph about
Build-Conflicts and I understand why the package FTBFS for you. My
conclusion is that warzone2100 simply requires automake1.11 to build.
Using Build-Conflicts would be one way to solve this issue for you, the
other one is to make the build system compatible with either of them.
You could also remove the other automake version from your chroot...


> I'll quote policy for you to save time:
> 
>   Build-Depends, Build-Depends-Indep, Build-Conflicts, Build-Conflicts-Indep
> 
>  Source packages that require certain binary packages to be installed
>  or *absent* at the time of building the package can declare
>  relationships to those binary packages.
> 
> This is the case here. This package requires normal automake to be
> *absent* because it needs automake1.11 and gets confused if there is
> another automake floating around.

Exactly, they _can_ declare relationships. No _must_ directive here. It
is not a Policy violation if you don't use Build-Conflicts. The package
builds fine from source in my environment and on the buildd. Thus it is
a bug when it FTBFS with another version of automake installed but not a
serious one.

I suggest to keep this bug report open but at severity normal and try to
fix this when upgrading to the latest upstream release which we should
do before the next freeze.

Regards,

Markus






signature.asc
Description: OpenPGP digital signature

Processed: notfound 808866 in 0.2-1

[Debian Bug Tracking System]

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

> notfound 808866 0.2-1
Bug #808866 [snappy] (snappy:15699): Clutter-CRITICAL **: The Clutter backend 
is not a X11 backend
Ignoring request to alter found versions of bug #808866 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#823143: marked as done (context: non-free files (CC-BY-NC-SA-3.0))

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 13:49:11 +
with message-id 
and subject line Bug#823143: fixed in context 2016.05.14.20160516-1
has caused the Debian Bug report #823143,
regarding context: non-free files (CC-BY-NC-SA-3.0)
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.)


-- 
823143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: context
Version: 2015.05.18.20150601-2
Severity: serious
Usertags: dfsg

Files in
texmf-dist/doc/context/sources/general/manuals/swiglib
texmf-dist/doc/context/sources/general/manuals/tools
texmf-dist/doc/context/sources/general/manuals/xtables

are licensed as CC-BY-NC-SA-3.0;

Files
texmf-dist/doc/context/sources/general/manuals/readme/mreadme.tex
texmf-dist/doc/context/documents/general/manuals/mreadme.pdf

contain:


The documentation is provided under another Creative Commons licence

   Attribution NonCommercial ShareAlike


(Arguably "mreadme.pdf" is a documentation hence it describes its own 
license.)

Please investigate.

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

You have to start with the truth. The truth is the only way that we can
get anywhere. Because any decision-making that is based upon lies or
ignorance can't lead to a good conclusion.
-- Julian Assange, 2010


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: context
Source-Version: 2016.05.14.20160516-1

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated 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, 16 May 2016 22:21:35 +0900
Source: context
Binary: context
Architecture: source all
Version: 2016.05.14.20160516-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX maintainers 
Changed-By: Norbert Preining 
Description:
 context- powerful TeX format
Closes: 823143 824471
Changes:
 context (2016.05.14.20160516-1) unstable; urgency=medium
 .
   * new upstream release(s) -- context to accompany TL 2016
 - cc-nc-sa licensed files relicensed (Closes: #823143)
   * bump standards version, no changes necessary
   * bump depends onto 2016 version of TL packages
   * depends on texlive-binaries >= 2016 (Closes: #824471)
Checksums-Sha1:
 33d1ae3968e8b948d0b95fe952a5c0e9fc38ca11 1629 context_2016.05.14.20160516-1.dsc
 974db8dd04043af01baca71a04e8bd72080140ee 29973725 
context_2016.05.14.20160516.orig.tar.gz
 a3c6b67f07d833030e586aad8bb8b20254938694 28264 
context_2016.05.14.20160516-1.debian.tar.xz
 b18d12be730c1cbd3856e2b934fcebb2fd95e383 22607732 
context_2016.05.14.20160516-1_all.deb
Checksums-Sha256:
 981c3846c84f21b29150681e35b18010d5e3c501eb735ea6f3bd82873ab67b50 1629 
context_2016.05.14.20160516-1.dsc
 c6d2704ce4509b75df065313ded671187ad015a480c2adef705d8b77252a519b 29973725 
context_2016.05.14.20160516.orig.tar.gz
 d84091c70a16646bee9d09a51d26bcf17c5e6a4853288f63a64488c221fce1e1 28264 
context_2016.05.14.20160516-1.debian.tar.xz
 7f45b4d3b5177855f7511502939c5f03a49178191e10814edcb5156ce05ed292 22607732 
context_2016.05.14.20160516-1_all.deb
Files:
 bc9dabd193987ffbf947c98e3c57c4c8 1629 tex optional 
context_2016.05.14.20160516-1.dsc
 d76cd0bd813a6008868fe492757a29ba 29973725 tex optional 
context_2016.05.14.20160516.orig.tar.gz
 43b711b4e1689bff4748cd8ef7b4c119 28264 tex optional 
context_2016.05.14.20160516-1.debian.tar.xz
 34bb82a649790b75b0e57b0662c7834a 22607732 tex optional 
context_2016.05.14.20160516-1_all.deb

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJXOctwAAoJEOwAuNrTImaqA58H/2NaDTj2M7EH2gu5uthaY6S8
5ojkN5rac/3s3mULR9xPP4DH1uO53uksi6vLG374DglG1oVyeRa7L7O8lTNAFxmL
qvPptb8SjYkda7yWX2dHTMkH2w6fN5zEYYdZvZxSXGvA1NwpPg002N/eV1uHy6H6

Processed: Re: Please port to clutter-gst-3.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #808518 [src:snappy-player] Please port to clutter-gst-3.0
Severity set to 'serious' from 'normal'
> tags -1 fixed-upstream
Bug #808518 [src:snappy-player] Please port to clutter-gst-3.0
Added tag(s) fixed-upstream.

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

Bug#823773: marked as done (jhighlight: FTBFS: [javadoc] javadoc: error - The -encoding option may be specified no more than once.)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 13:33:52 +
with message-id 
and subject line Bug#823773: fixed in ant 1.9.7-3
has caused the Debian Bug report #823773,
regarding jhighlight: FTBFS: [javadoc] javadoc: error - The -encoding option 
may be specified no more than once.
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.)


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

jhighlight fails to build from source in unstable/amd64:

  [..]

  Adding debian:Global_Chambersign_Root_-_2008.pem
  Adding debian:Go_Daddy_Class_2_CA.pem
  Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
  Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem
  Adding debian:Hongkong_Post_Root_CA_1.pem
  Adding debian:IGC_A.pem
  Adding debian:IdenTrust_Commercial_Root_CA_1.pem
  Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
  Adding debian:Izenpe.com.pem
  Adding debian:Juur-SK.pem
  Adding debian:Microsec_e-Szigno_Root_CA.pem
  Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
  Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
  Adding debian:NetLock_Business_=Class_B=_Root.pem
  Adding debian:NetLock_Express_=Class_C=_Root.pem
  Adding debian:NetLock_Notary_=Class_A=_Root.pem
  Adding debian:NetLock_Qualified_=Class_QA=_Root.pem
  Adding debian:Network_Solutions_Certificate_Authority.pem
  Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
  Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem
  Adding debian:PSCProcert.pem
  Adding debian:QuoVadis_Root_CA.pem
  Adding debian:QuoVadis_Root_CA_1_G3.pem
  Adding debian:QuoVadis_Root_CA_2.pem
  Adding debian:QuoVadis_Root_CA_2_G3.pem
  Adding debian:QuoVadis_Root_CA_3.pem
  Adding debian:QuoVadis_Root_CA_3_G3.pem
  Adding debian:RSA_Security_2048_v3.pem
  Adding debian:Root_CA_Generalitat_Valenciana.pem
  Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
  Adding debian:S-TRUST_Universal_Root_CA.pem
  Adding debian:SecureSign_RootCA11.pem
  Adding debian:SecureTrust_CA.pem
  Adding debian:Secure_Global_CA.pem
  Adding debian:Security_Communication_EV_RootCA1.pem
  Adding debian:Security_Communication_RootCA2.pem
  Adding debian:Security_Communication_Root_CA.pem
  Adding debian:Sonera_Class_1_Root_CA.pem
  Adding debian:Sonera_Class_2_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:Starfield_Class_2_CA.pem
  Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
  Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
  Adding debian:StartCom_Certification_Authority.pem
  Adding debian:StartCom_Certification_Authority_2.pem
  Adding debian:StartCom_Certification_Authority_G2.pem
  Adding debian:SwissSign_Gold_CA_-_G2.pem
  Adding debian:SwissSign_Platinum_CA_-_G2.pem
  Adding debian:SwissSign_Silver_CA_-_G2.pem
  Adding debian:Swisscom_Root_CA_1.pem
  Adding debian:Swisscom_Root_CA_2.pem
  Adding debian:Swisscom_Root_EV_CA_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
  Adding debian:TC_TrustCenter_Class_3_CA_II.pem
  Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
  Adding debian:TWCA_Global_Root_CA.pem
  Adding debian:TWCA_Root_Certification_Authority.pem
  Adding debian:Taiwan_GRCA.pem
  Adding debian:TeliaSonera_Root_CA_v1.pem
  Adding debian:Trustis_FPS_Root_CA.pem
  Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
  Adding debian:USERTrust_ECC_Certification_Authority.pem
  Adding debian:USERTrust_RSA_Certification_Authority.pem
  Adding debian:UTN_USERFirst_Email_Root_CA.pem
  Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
  Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
  Adding 

Bug#824457: [Pkg-swan-devel] Bug#824457: strongswan: FTBFS in testing

[Yves-Alexis Perez]

On lun., 2016-05-16 at 12:44 +0200, Santiago Vila wrote:
> Package: src:strongswan
> Version: 5.4.0-1
> Severity: serious
> 
> Dear maintainer:
> 
> This package currently fails to build from source in stretch:
> 
> 
> In file included from /usr/include/libiptc/ipt_kernel_headers.h:13:0,
>  from /usr/include/libiptc/libiptc.h:6,
>  from connmark_listener.c:24:
> /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
>   IFF_UP= 1<<0,  /* sysfs */
> 
> 
> The full build log is attached.

Please investigate #822396 before?

Regards,
-- 
Yves-Alexis



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

Bug#824260: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Norbert Preining]

Hi Bas,

thanks a lot for testing. I there a porter box where I can test
it myself?

> I had to change the the CFLAGS option to use += -DU_IS_BIG_ENDIAN=0
> otherwise the build fails because CFLAGS references itself.

Ahhh, I had the strange feeling that make and bash are different in
this respect ... sorry.

> With that change the build still fails on mipsel porterbox:

Bad, but this is at least a *different* error now, not related to
the ICE and upmendex/xetex, which is a bit better.

Did the test run at least over the upmendex and xetex tests?

What if you disable luajittex by removing it from the 
LUAJIT_GOOD_ARCHS
list? After that it should compile without a problem???Hopefully.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#824260: texlive-bin: FTBFS on mips, mipsel & sparc64 due to test failures

[Sebastiaan Couwenberg]

On 05/16/2016 05:34 AM, Norbert Preining wrote:
> I am travelling so I cannot actually test-build it. If someone could do
> a test run, here is a test package that sets the 
>   U_IS_BIG_ENDIAN=0 
> for C(XX)FLAGS on these architectures.
> 
> http://www.preining.info/debian/texlive-bin_2016.20160513.41080-2~1.debian.tar.xz
> http://www.preining.info/debian/texlive-bin_2016.20160513.41080-2~1.dsc
> 
> (.orig.tar.xz is in the normal Debian pool).
> 
> Thanks for any testing

I had to change the the CFLAGS option to use += -DU_IS_BIG_ENDIAN=0
otherwise the build fails because CFLAGS references itself.

With that change the build still fails on mipsel porterbox:

FAIL: luajiterr.test
===
   luajit for TeX Live 2.1.0-beta2: ./test-suite.log
===

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: luajiterr
===

1,4c1
< ./luajittry: (command line):1: test
< stack traceback:
<   [C]: in function 'error'
<   (command line):1: in main chunk
---
> luajit: attempt to call a function value
FAIL luajiterr.test (exit status: 1)

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#824475: python-mne: FTBFS: TraitError: The 'input' trait of a QuadricDecimation instance is 'read only'.

[Chris Lamb]

Source: python-mne
Version: 0.11+dfsg-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,

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

  [..]

  copying mne/time_frequency/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/_stockwell.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/ar.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/tfr.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/psd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/stft.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/csd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  copying mne/time_frequency/multitaper.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency
  creating build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_psd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_stockwell.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_csd.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_multitaper.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_ar.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_stft.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  copying mne/time_frequency/tests/test_tfr.py -> 
build/lib.linux-x86_64-2.7/mne/time_frequency/tests
  creating build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/__init__.py -> build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/mockclient.py -> build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/epochs.py -> build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/stim_server_client.py -> 
build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/fieldtrip_client.py -> 
build/lib.linux-x86_64-2.7/mne/realtime
  copying mne/realtime/client.py -> build/lib.linux-x86_64-2.7/mne/realtime
  creating build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/test_fieldtrip_client.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/test_stim_client_server.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  copying mne/realtime/tests/test_mockclient.py -> 
build/lib.linux-x86_64-2.7/mne/realtime/tests
  creating build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/__init__.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/base.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/time_gen.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/mixin.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/transformer.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/ems.py -> build/lib.linux-x86_64-2.7/mne/decoding
  copying mne/decoding/csp.py -> build/lib.linux-x86_64-2.7/mne/decoding
  creating build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/__init__.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_csp.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_ems.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_transformer.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/decoding/tests/test_time_gen.py -> 
build/lib.linux-x86_64-2.7/mne/decoding/tests
  copying mne/commands/utils.py -> build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_coreg.py -> build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/__init__.py -> build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_make_scalp_surfaces.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_browse_raw.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_flash_bem.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_compute_proj_ecg.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_show_fiff.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_watershed_bem.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_surf2bem.py -> 
build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_report.py -> build/lib.linux-x86_64-2.7/mne/commands
  copying mne/commands/mne_maxfilter.py -> 

Bug#821528: marked as done (libphp-simplepie: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 12:52:17 +
with message-id 
and subject line Bug#821528: fixed in simplepie 1.3.1+dfsg-3.1
has caused the Debian Bug report #821528,
regarding libphp-simplepie: PHP 7.0 Transition
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.)


-- 
821528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libphp-simplepie
Version: 1.3.1+dfsg-3
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The libphp-simplepie package currently depends on php5 php5-cli php5-curl
php5-intl .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: libphp-simplepie -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUqAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHNWwQAMX727e+oNk8ds7tVGUw6syb
bPKKIDpCLTV+gLLxiPfGLDMpzoi8z3y+Sr/P6j7lLKaWxExxPdo/l3WCfBExCP4w
KKRYy5M1vsd+jGlb0jU3mTg4h/RPMoc2slUsxunw2z6e1PXQZXTXu49IkegUv1DK
GF/DjLSRRFa7arZ5SW2CJ+0Ilkps64T1QuaJMHzg3yHHltLNUKIPL/1WV95Nlb5L

Bug#821714: marked as done (src:simplepie: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 12:52:17 +
with message-id 
and subject line Bug#821714: fixed in simplepie 1.3.1+dfsg-3.1
has caused the Debian Bug report #821714,
regarding src:simplepie: PHP 7.0 Transition
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.)


-- 
821714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:simplepie
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The simplepie package currently build-depends on php5 php5-cli .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: simplepie -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUt5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHVYIQAJiyPdlr4k5drOwtEe5LrNlp
t60JVQTH50ZdOZKMFELIVp+SfpuWYyyITE8j/WS0y0KgQNQ9ywuh3TjNhKl4UbIP
Qj0CQJtVvs6pWnPO0ZlBrrb9X8XS1PCb6VpAt5GGKAz76Wvf6XyFuP1kvza0jc8I
AX0xbYPQJKY5gvLt+t8wW8tPgb2zX3a4AoFCfmY99BRSDBrZvuwAwReYrTKmDt9U
gD6rCtL7YHgjRC72K2VLb54PVuMhi7Sc5d5SqIUlfwqU/A9kGpdaQVhhohaQFVE7

Bug#799264: marked as done (plasma-desktop: fails to upgrade from 'jessie' - trying to overwrite /etc/dbus-1/system.d/org.kde.kcontrol.kcmclock.conf)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 14:49:27 +0200
with message-id <20160516124927.gf4...@gnuservers.com.ar>
and subject line Re: Bug#799264: plasma-desktop: fails to upgrade from 'jessie' 
- trying to overwrite /etc/dbus-1/system.d/org.kde.kcontrol.kcmclock.conf
has caused the Debian Bug report #799264,
regarding plasma-desktop: fails to upgrade from 'jessie' - trying to overwrite 
/etc/dbus-1/system.d/org.kde.kcontrol.kcmclock.conf
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.)


-- 
799264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-desktop
Version: 4:5.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + kde-workspace-bin

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' 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...):

  Unpacking plasma-desktop (4:5.4.0-2) over (4:4.11.13-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/plasma-desktop_4%3a5.4.0-2_amd64.deb (--unpack):
   trying to overwrite '/etc/dbus-1/system.d/org.kde.kcontrol.kcmclock.conf', 
which is also in package kde-workspace-data 4:4.11.13-2
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for mime-support (3.58) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/plasma-desktop_4%3a5.4.0-2_amd64.deb


cheers,

Andreas


kde-workspace-bin_4:4.11.22-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

Version: 4:5.4.1-1

¡Hola Andreas!

El 2015-09-17 a las 12:23 +0200, Andreas Beckmann escribió:
Version: 4:5.4.0-2 


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


This was added as part of the 5.4.1 packaging, but it seems that we forgot to 
close this bug with the upload. Closing now.


Thanks for reporting,

Happy hacking,
--
"Don't let what you cannot do interfere with what you can do."
-- Wooden's Rule
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature
--- End Message ---

Bug#823773: jhighlight: FTBFS: [javadoc] javadoc: error - The -encoding option may be specified no more than once.

[Emmanuel Bourg]

Control: reassign -1 ant
Control: affects -1 jhighlight

This is a bug caused by the patch to make the javadocs reproducible in
ant/1.9.7-1. jhighlight sets the javadoc encoding with an extra argument
() instead of the 'encoding' attribute of the
javadoc task, and the patch doesn't handle this case.

Processed: Re: jhighlight: FTBFS: [javadoc] javadoc: error - The -encoding option may be specified no more than once.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ant
Bug #823773 [src:jhighlight] jhighlight: FTBFS: [javadoc] javadoc: error - The 
-encoding option may be specified no more than once.
Bug reassigned from package 'src:jhighlight' to 'ant'.
No longer marked as found in versions jhighlight/1.0-1.
Ignoring request to alter fixed versions of bug #823773 to the same values 
previously set
> affects -1 jhighlight
Bug #823773 [ant] jhighlight: FTBFS: [javadoc] javadoc: error - The -encoding 
option may be specified no more than once.
Added indication that 823773 affects jhighlight

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

Bug#821714: src:simplepie: PHP 7.0 Transition

[Tanguy Ortolo]

Tanguy Ortolo, 2016-05-16 12:39+0200:
As I maintain dokuwiki which depends on php-simplepie, I am concerned 
by this. I will try to NMU this.


NMU done, without delay considering this is an RC bug.  Marcelo, I have 
put my changes on a Git repository of mine, so you want you can merge 
them at your convenience, with:


   $ git pull https://git.ortolo.eu/git/contrib-pkg-simplepie.git

Librement,

--
 ,--.
: /` )   Tanguy Ortolo  
| `-'Debian Developer   
 \_


signature.asc
Description: Digital signature

Bug#824465: marked as done (littler: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 11:48:40 +
with message-id <e1b2h0q-00066g...@franck.debian.org>
and subject line Bug#824465: fixed in littler 0.3.0-3
has caused the Debian Bug report #824465,
regarding littler: FTBFS in testing
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.)


-- 
824465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:littler
Version: 0.3.0-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


make[1]: Entering directory '/<>/src'
gcc -std=gnu99 -o r -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_S
OURCE=2 -g -I/usr/share/R/include littler.c  -Wl,--export-dynamic -fopenmp  
-L/usr/lib/R/lib -lR -lpcre -llzm
a -lbz2 -lz -lrt -ldl -lm -licuuc -licui18n -lblas -llapack 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,/usr/lib/x86
_64-linux-gnu -Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,
/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib
 -Wl,-rpath,/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server -Wl,-rpath,/u
sr/lib/x86_64-linux-gnu/libfakeroot -Wl,-rpath,/usr/lib64/libfakeroot 
-Wl,-rpath,/usr/lib32/libfakeroot 
/usr/bin/ld: cannot find -licuuc
/usr/bin/ld: cannot find -licui18n
collect2: error: ld returned 1 exit status
Makevars:29: recipe for target 'r' failed


The full build log is attached.

Thanks.

littler_0.3.0-2_amd64-20160516-1238.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: littler
Source-Version: 0.3.0-3

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel <e...@debian.org> (supplier of updated littler 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, 16 May 2016 06:22:23 -0500
Source: littler
Binary: r-cran-littler littler
Architecture: source all amd64
Version: 0.3.0-3
Distribution: unstable
Urgency: low
Maintainer: Dirk Eddelbuettel <e...@debian.org>
Changed-By: Dirk Eddelbuettel <e...@debian.org>
Description:
 littler- GNU R scripting and command-line front-end -- transition package
 r-cran-littler - GNU R scripting and command-line front-end
Closes: 824465
Changes:
 littler (0.3.0-3) unstable; urgency=low
 .
   * debian/control: Add libicu-dev to Build-Depends(Closes: #824465)
 .
   * debian/rules: Strip /usr/bin/r when installing
Checksums-Sha1:
 cc9fc62b206f8a7ad1d8761692411d2376bf382c 1721 littler_0.3.0-3.dsc
 9bae4578b9f6e89d48a02168437b5e9fca720715 4277 littler_0.3.0-3.diff.gz
 3d15561df9e16678dff90799b988605a160ea861 11018 littler_0.3.0-3_all.deb
 431c6b366eefaeb7ab349badec884e7fbef37b14 14764 
r-cran-littler-dbgsym_0.3.0-3_amd64.deb
 1891b5489e195125377537481d1651db2eb6f614 54588 r-cran-littler_0.3.0-3_amd64.deb
Checksums-Sha256:
 3a19533bcdbd1189e291ecd3162a2702cbf0e934ad224f029b67e748f34429fe 1721 
littler_0.3.0-3.dsc
 efadaacb89965cc7fc1caa432342aff337bb4a385a83235a204ffc91e4a0d3a2 4277 
littler_0.3.0-3.diff.gz
 4cd37dae7dd02e66be08872894f2c7cef9dae2a56274b946bd7717c6d9893bb8 11018 
littler_0.3.0-3_all.deb
 c04e3b230e37711b8d459b7684de263dc4e28ae402c2cf3be568ed039d0f93fc 14764 
r-cran-littler-dbgsym_0.3.0-3_amd64.deb
 c1614b2029de75f317a24c6866ae2c933725b8e0b0244bf143a647446269e359 54588 
r-cran-littler_0.3.0-3_amd64.deb
Files:
 096f281808c5ca691166d927cbf53dc5 1721 gnu-r optional littler_0.3.0-3.dsc
 5708c182df4d19450dd7d60a24eed605 4277 gnu-r optional littler_0.3.0-3.diff.gz
 07022ae241f7b41a9aa791efe56b0923 11018 gnu-r optional littler_0.3.0-3_all.deb
 2e3aca5bc59ab25431ab3ff6f881e249 14764 debug extra 
r-cran-littler-dbgsym_0.3.0-3_amd64.deb
 feb22d248d7052d01bbe92d4ae16fa96 54588 gnu-r 

Bug#824465: littler: FTBFS in testing

[Dirk Eddelbuettel]

On 16 May 2016 at 12:58, Santiago Vila wrote:
| Package: src:littler
| Version: 0.3.0-2
| Severity: serious
| 
| Dear maintainer:
| 
| This package currently fails to build from source in stretch:
| 
| 
| make[1]: Entering directory '/<>/src'
| gcc -std=gnu99 -o r -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_S
| OURCE=2 -g -I/usr/share/R/include littler.c  -Wl,--export-dynamic -fopenmp  
-L/usr/lib/R/lib -lR -lpcre -llzm
| a -lbz2 -lz -lrt -ldl -lm -licuuc -licui18n -lblas -llapack 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,/usr/lib/x86
| _64-linux-gnu -Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,
| /usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib
|  -Wl,-rpath,/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server -Wl,-rpath,/u
| sr/lib/x86_64-linux-gnu/libfakeroot -Wl,-rpath,/usr/lib64/libfakeroot 
-Wl,-rpath,/usr/lib32/libfakeroot 
| /usr/bin/ld: cannot find -licuuc
| /usr/bin/ld: cannot find -licui18n
| collect2: error: ld returned 1 exit status
| Makevars:29: recipe for target 'r' failed
| 

I just rebuilt, adding libicu-dev to Build-Depends (and will add to
r-base-dev where it belongs; longs like R added this) and get

make[1]: Entering directory '/build/littler-0.3.0/src'
gcc -std=gnu99 -o r -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-I/usr/share/R/include littler.c  -Wl,--export-dynamic -fopenmp  
-L/usr/lib/R/lib -lR -lpcre -llzma -lbz2 -lz -lrt -ldl -lm -licuuc -licui18n 
-lblas -llapack -Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/x86_64-linux-gnu/libfakeroot 
-Wl,-rpath,/usr/lib64/libfakeroot -Wl,-rpath,/usr/lib32/libfakeroot 

So all good.  Will ship a 0.3.0-3 fixing this. And fix r-base-dev.

Thanks for the report.

Dirk
 
| The full build log is attached.
| 
| Thanks.
| x[DELETED ATTACHMENT littler_0.3.0-2_amd64-20160516-1238.gz, application/gzip]

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#707826: marked as done (opengrm-ngram: FTBFS on big-endian architectures)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 11:01:27 +
with message-id 
and subject line Bug#707826: fixed in opengrm-ngram 1.2.2-1
has caused the Debian Bug report #707826,
regarding opengrm-ngram: FTBFS on big-endian architectures
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.)


-- 
707826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opengrm-ngram
Version: 1.0.3-1
Severity: serious
Tags: upstream
Justification: fails to build from source

This package fails to build from source on several architectures.
The problem is due to the fact that this package ships with some binary data
files (OpenFST files) and those files are not architecture independent.
Both OpenFST and OpenGRM-NGram developers have been contacted: there is no plan
to add support for architecture independent binary data files in OpenFST,
instead developers that want to share data files for OpenFST should provide
them in text format.
In this case the solution would be to disable the test suite in OpenGRM-NGram.



-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8.5geppetto (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: opengrm-ngram
Source-Version: 1.2.2-1

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

Debian distribution maintenance software
pp.
Giulio Paci  (supplier of updated opengrm-ngram 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, 10 May 2016 12:45:29 +0200
Source: opengrm-ngram
Binary: libngram-tools libngram-dev libngram1
Architecture: source i386
Version: 1.2.2-1
Distribution: experimental
Urgency: low
Maintainer: Giulio Paci 
Changed-By: Giulio Paci 
Description:
 libngram-dev - OpenGRM n-gram Language Modeling toolkit - development files
 libngram-tools - OpenGRM n-gram Language Modeling toolkit
 libngram1  - OpenGRM n-gram Language Modeling toolkit - runtime library
Closes: 707826
Changes:
 opengrm-ngram (1.2.2-1) experimental; urgency=low
 .
   * Import Upstream version 1.2.2.
   * Fix FTBFS (Closes: #707826).
   * Update copyright file.
 - Drop autotools files
 - Simplified sections
   * Drop libngram-tools.lintian-overrides.
   * Rename libngram0 package into libngram1.
   * Refresh libngram1.lintian-overrides.
   * Do not create -dbg package.
 Rely on automatic dbgsym packages instead, as described in
 https://lists.debian.org/5675e791.6060...@thykier.net
   * Update build dependencies
 - bump libfst-dev and libfst-tools minimum version to 1.5.1
 - replace automake1.11 with automake
 - set cdbs minimum version to 0.4.123~
   * Refresh 1005_fix_libraries_linking.patch.
   * Update 1002_remove_bashisms.patch.
 This patch contained a no more needed replacement for $RANDOM,
 now it just drops function keyword.
   * Add 1006_fix_autotools_warnings.patch,
 1007_fix_parallel_tests.patch,
 1008_fix_compilation_with_openfst_1.5.x.patch and
 1009_fix_spelling.patch.
   * Drop 1003_fix_spelling.patch and 1004_fix_ngram_h_file.patch.
 These patches have been applied upstream.
   * Add update-man.sh to simplify manpages' updates.
   * Update manpages.
   * Add ngramcontext.1, ngrammarginalize.1, ngramrandtest.1,
 ngramsort., ngramsplit.1, ngramtransfer.1.
   * Update Vcs-* fields to use secure uri.
   * Change Section from text to science.
   * Bump Standards-Version to 3.9.8.
   * Fix clean target and backups in rules.
Checksums-Sha1:
 f8633818e70b3dc78809e89116fa7164ce00455d 2188 opengrm-ngram_1.2.2-1.dsc
 bba291fd00ee73cbd99a67b1df6dad5d1325ec95 15307289 
opengrm-ngram_1.2.2.orig.tar.gz
 54ba77c33632849e3139acfbcd27ab11066687c1 

Bug#824465: littler: FTBFS in testing

[Santiago Vila]

Package: src:littler
Version: 0.3.0-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


make[1]: Entering directory '/<>/src'
gcc -std=gnu99 -o r -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_S
OURCE=2 -g -I/usr/share/R/include littler.c  -Wl,--export-dynamic -fopenmp  
-L/usr/lib/R/lib -lR -lpcre -llzm
a -lbz2 -lz -lrt -ldl -lm -licuuc -licui18n -lblas -llapack 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,/usr/lib/x86
_64-linux-gnu -Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib -Wl,-rpath,
/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server 
-Wl,-rpath,/usr/lib/R/lib
 -Wl,-rpath,/usr/lib/x86_64-linux-gnu 
-Wl,-rpath,/usr/lib/jvm/default-java/jre/lib/amd64/server -Wl,-rpath,/u
sr/lib/x86_64-linux-gnu/libfakeroot -Wl,-rpath,/usr/lib64/libfakeroot 
-Wl,-rpath,/usr/lib32/libfakeroot 
/usr/bin/ld: cannot find -licuuc
/usr/bin/ld: cannot find -licui18n
collect2: error: ld returned 1 exit status
Makevars:29: recipe for target 'r' failed


The full build log is attached.

Thanks.

littler_0.3.0-2_amd64-20160516-1238.gz
Description: application/gzip

Bug#824463: elektra: FTBFS in testing

[Santiago Vila]

Package: src:elektra
Version: 0.8.14-5
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


In file included from 
/<>/src/libgetenv/benchmarks/benchmark_getenv.cpp:11:0:
/<>/src/bindings/cpp/include/kdbtimer.hpp:33:15: error: 'vector' 
in namespace 'std' does not nam
e a template type
  typedef std::vector results_t;
   ^
/<>/src/bindings/cpp/include/kdbtimer.hpp:34:2: error: 'results_t' 
does not name a type
  results_t results;
  ^


The full build log is attached.

Thanks.

elektra_0.8.14-5_amd64-20160516-1227.gz
Description: application/gzip

Bug#821375: marked as done (claws-mail-themes: Skypilot-Clawssic is non-free)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 10:48:43 +
with message-id 
and subject line Bug#821375: fixed in claws-mail-themes 20140629+dfsg1-1
has caused the Debian Bug report #821375,
regarding claws-mail-themes: Skypilot-Clawssic is non-free
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.)


-- 
821375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: claws-mail-themes
Severity: serious
Tags: upstream
Justification: Policy 2.3

Hi,

In upstream bug 3640¹ it has been reported that the original theme from
which Skypilot_Clawssic Claws Mail theme is derived is not allowed to be
modified among other things²:

,--
| REF: https://addons.mozilla.org/en-US/firefox/addon/12773
| This is an unauthorized port of the theme. The author simply disregarded 
| the license contained in the theme file:
|
| "The original artwork may not be redistributed, or used for any other 
| purpose without the expressed permission of the author. The original 
| artwork is not covered by any open-source license and cannot be 
| distributed under such license. In addition, this package may not be 
| modified and re-released under its name at any time."
| 
| Anyone know how I can contact the AMO folks to have theme remove it?
| 
| -- 
| Sailfish - Netscape/Mozilla Champion
| Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/
| Rare Mozilla Stuff: http://www.projectit.com/
`--

Hence, this theme should be removed from Debian (and probably upstream).

regards,

¹ http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3640
² https://groups.google.com/forum/#!topic/mozilla.dev.themes/Ois-_dWv79Y

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

Kernel: Linux 3.16-3-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)
--- End Message ---
--- Begin Message ---
Source: claws-mail-themes
Source-Version: 20140629+dfsg1-1

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated claws-mail-themes 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: Sun, 01 May 2016 13:54:07 +0200
Source: claws-mail-themes
Binary: claws-mail-themes
Architecture: source all
Version: 20140629+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Description:
 claws-mail-themes - Pixmap icon themes for the Claws Mail mailer
Closes: 821375
Changes:
 claws-mail-themes (20140629+dfsg1-1) unstable; urgency=medium
 .
   * make-upstream-tarball-DFSG, claws-mail-themes.1
   - Remove non-free theme Skypilot_Clawssic (Closes: #821375)
   * Include KDE4ish: relicensing LGPL works as GPL is explicitly
 allowed by LGPL-2.1 §3 and LGPL-3.0 §2b.
 Thanks mju...@free.fr for noticing this on upstream bug 3640
   * make-upstream-tarball-DFSG, patches/remove-non-free-themes
   - Add parameter for allowing dfsgN upstream tarballs and new patch
   * docs.in
   - Update documents installed
   * control
   - Update Standards-Version to 3.9.8 (no other changes required)
   * copyright
   - Update themes, authors, dates and fix some obsolete URL.
Checksums-Sha1:
 90b2e19d409259dc87843b4d6b5b3144ba4bd57b 2111 
claws-mail-themes_20140629+dfsg1-1.dsc
 0f8070ada851beabc49e19ef0a970d7ed672de95 1738444 
claws-mail-themes_20140629+dfsg1.orig.tar.xz
 1fe6c4b414d7d771cd3feaba33086be5b8eb2ddd 21300 
claws-mail-themes_20140629+dfsg1-1.debian.tar.xz
 61e83040b198c747693ae68fefb552b9bc5a4382 1776802 
claws-mail-themes_20140629+dfsg1-1_all.deb
Checksums-Sha256:
 

Bug#824459: tango: FTBFS in testing

[Santiago Vila]

Package: src:tango
Version: 8.1.2c+dfsg-7
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


In file included from ../../../../lib/cpp/server/w_attribute.cpp:61:0:
../../../../lib/cpp/server/w_attribute.cpp: In member function 'virtual bool 
Tango::WAttribute::check_rds_ala
rm()':
../../../../lib/cpp/server/tango_config.h:201:38: error: expected 
unqualified-id before '(' token
 #define Tango_isnan(A)  std::isnan(A)
  ^
../../../../lib/cpp/server/w_attribute.cpp:3421:11: note: in expansion of macro 
'Tango_isnan'
  if ( Tango_isnan(double_array_val[0]) || Tango_isnan(tmp_db[0]) )


The full build log is attached.

Thanks.

tango_8.1.2c+dfsg-7_amd64-20160516-1227.gz
Description: application/gzip

Bug#824458: xtables-addons: FTBFS in testing

[Santiago Vila]

Package: src:xtables-addons
Version: 2.10-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


make[7]: Entering directory '/<>/extensions/pknock'
  CC libxt_pknock.oo
In file included from /usr/include/xtables.h:16:0,
 from libxt_pknock.c:15:
/usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
  IFF_UP= 1<<0,  /* sysfs */
  ^
/usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
 IFF_UP = 0x1,  /* Interface is up.  */
 ^


The full build log is attached.

Thanks.

xtables-addons_2.10-1_amd64-20160516-1230.gz
Description: application/gzip

Bug#824457: strongswan: FTBFS in testing

[Santiago Vila]

Package: src:strongswan
Version: 5.4.0-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


In file included from /usr/include/libiptc/ipt_kernel_headers.h:13:0,
 from /usr/include/libiptc/libiptc.h:6,
 from connmark_listener.c:24:
/usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
  IFF_UP= 1<<0,  /* sysfs */


The full build log is attached.

Thanks.

strongswan_5.4.0-1_amd64-20160516-1227.gz
Description: application/gzip

Bug#821714: src:simplepie: PHP 7.0 Transition

[Tanguy Ortolo]

As I maintain dokuwiki which depends on php-simplepie, I am concerned by 
this. I will try to NMU this.


--
 ,--.
: /` )   Tanguy Ortolo  
| `-'Debian Developer   
 \_


signature.asc
Description: Digital signature

Bug#823587: marked as done (proguard: FTBFS: build.xml:124: Please set the value of the property gradle.home in the file build.properties, if you want to build the optional ProGuard Gradle task.)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 10:35:51 +
with message-id 
and subject line Bug#823587: fixed in proguard 5.2.1-4
has caused the Debian Bug report #823587,
regarding proguard: FTBFS: build.xml:124: Please set the value of the property 
gradle.home in the file build.properties, if you want to build the optional 
ProGuard Gradle task.
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.)


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

proguard fails to build from source in unstable/amd64:

  [..]

  Setting up libgradle-core-java (2.11-1) ...
  Setting up bnd (2.4.1-3) ...
  Setting up libmsv-java (2009.1+dfsg1-5) ...
  Setting up libdom4j-java (1.6.1+dfsg.3-2) ...
  Setting up libjetty-extra-java (6.1.26-5) ...
  Setting up libeasymock-java (3.3.1+ds-3) ...
  Setting up libwagon2-java (2.10-3) ...
  Setting up libmaven3-core-java (3.3.9-4) ...
  Setting up maven-repo-helper (1.8.12) ...
  Setting up ca-certificates-java (20160321) ...
  done.
  Setting up libgtk-3-common (3.20.3-2) ...
  Setting up libgtk-3-0:amd64 (3.20.3-2) ...
  Setting up libatk-wrapper-java-jni:amd64 (0.33.3-6+b1) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-2) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up openjdk-8-jdk:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer 
to provide /usr/bin/appletviewer (appletviewer) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to 
provide /usr/bin/jconsole (jconsole) in auto mode
  Setting up default-jdk (2:1.8-57) ...
  Setting up findbugs (3.0.1-2) ...
  Setting up libgradle-plugins-java (2.11-1) ...
  Setting up gradle (2.11-1) ...
  Setting up proguard-build-deps (5.2.1-3) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  Adding debian:ACCVRAIZ1.pem
  Adding debian:ACEDICOM_Root.pem
  Adding debian:AC_Raíz_Certicámara_S.A..pem
  Adding debian:Actalis_Authentication_Root_CA.pem
  Adding debian:AddTrust_External_Root.pem
  Adding debian:AddTrust_Low-Value_Services_Root.pem
  Adding debian:AddTrust_Public_Services_Root.pem
  Adding debian:AddTrust_Qualified_Certificates_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:AffirmTrust_Networking.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:AffirmTrust_Premium_ECC.pem
  Adding debian:ApplicationCA_-_Japanese_Government.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
  Adding debian:Baltimore_CyberTrust_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:Buypass_Class_2_Root_CA.pem
  Adding debian:Buypass_Class_3_Root_CA.pem
  Adding debian:CA_Disig.pem
  Adding debian:CA_Disig_Root_R1.pem
  Adding debian:CA_Disig_Root_R2.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:CFCA_EV_ROOT.pem
  Adding debian:CNNIC_ROOT.pem
  Adding debian:COMODO_Certification_Authority.pem
  Adding debian:COMODO_ECC_Certification_Authority.pem
  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:Certigna.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:Certinomis_-_Root_CA.pem
  Adding debian:Certplus_Class_2_Primary_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:ComSign_CA.pem
  Adding debian:Comodo_AAA_Services_root.pem
  Adding debian:Comodo_Secure_Services_root.pem
  Adding debian:Comodo_Trusted_Services_root.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
  Adding debian:DST_ACES_CA_X6.pem
  Adding 

Bug#824455: missing license in debian/copyright

[Thorsten Alteholz]

Package: irstlm
Version: 6.00.05-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing license of:
 irstlm-6.00.05/doc/mdframed.sty
to your debian/copyright.

Thanks!
  Thorsten

Bug#823893: marked as done (libarchive: CVE-2016-1541)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 09:53:04 +
with message-id 
and subject line Bug#823893: fixed in libarchive 3.1.2-11.1
has caused the Debian Bug report #823893,
regarding libarchive: CVE-2016-1541
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.)


-- 
823893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libarchive
Version: 3.1.2-11
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole
Control: fixed -1 3.2.0-1

Hi,

the following vulnerability was published for libarchive.

CVE-2016-1541[0]:
| Heap-based buffer overflow in the zip_read_mac_metadata function in
| archive_read_support_format_zip.c in libarchive before 3.2.0 allows
| remote attackers to execute arbitrary code via crafted entry-size
| values in a ZIP archive.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1541
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1541
[1] https://www.kb.cert.org/vuls/id/862384

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libarchive
Source-Version: 3.1.2-11.1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libarchive 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, 16 May 2016 09:46:05 +0100
Source: libarchive
Binary: libarchive-dev libarchive13 bsdtar bsdcpio
Architecture: amd64 source
Version: 3.1.2-11.1
Distribution: unstable
Urgency: high
Maintainer: Debian Libarchive Maintainers 
Changed-By: Simon McVittie 
Closes: 823893 823984
Description: 
 bsdcpio- Implementation of the 'cpio' program from FreeBSD
 bsdtar - Implementation of the 'tar' program from FreeBSD
 libarchive13 - Multi-format archive and compression library (shared library)
 libarchive-dev - Multi-format archive and compression library (development 
files)
Changes:
 libarchive (3.1.2-11.1) unstable; urgency=high
 .
   * Non-maintainer upload.
 - Make libarchive/unstable catch up with libarchive/stable
   (Closes: #823984)
 .
   [ Salvatore Bonaccorso ]
   * CVE-2016-1541: heap-based buffer overflow due to improper input
 validation (Closes: #823893)
Checksums-Sha1: 
 ec25d752ead61a1b367f4f24c43d0b6a59284422 2275 libarchive_3.1.2-11.1.dsc
 30a83cc6aff08394efa7215db7d6da6681ecb6d6 15356 
libarchive_3.1.2-11.1.debian.tar.xz
 9644f65bbcf4eb06c9c91eee9f60dd93e8402865 26322 
bsdcpio-dbgsym_3.1.2-11.1_amd64.deb
 03e75b7c56b5275d98d2fe745c4fcf0ba3bf442e 39392 bsdcpio_3.1.2-11.1_amd64.deb
 b9e2f714fdecc0c6d7582ad92956ddc3c3a843d9 46360 
bsdtar-dbgsym_3.1.2-11.1_amd64.deb
 b0fb316aa887b8817606c7ec36032046d0918979 53808 bsdtar_3.1.2-11.1_amd64.deb
 ed74ec6eed114c9676b6f8460a64661c84443ed0 429448 
libarchive-dev_3.1.2-11.1_amd64.deb
 7398d14faecca1e45109b24fd7763dd44489c6c8 702668 
libarchive13-dbgsym_3.1.2-11.1_amd64.deb
 7c320688e4231d2feb3fbaed2043bb134a4ae7bf 265848 
libarchive13_3.1.2-11.1_amd64.deb
Checksums-Sha256: 
 7f5453b9e7c8de99bf67e38e67ea63e8ab03518e6b955d625c3d28fcc0d3b327 2275 
libarchive_3.1.2-11.1.dsc
 459cc3b691b5c043b3d8009588d8f9446de12214f994c2b2c3208120a9a563bb 15356 
libarchive_3.1.2-11.1.debian.tar.xz
 6acbe648b855903af0f0696dccfe6f446fd3655aba2466d314a284fa5d391ae4 26322 
bsdcpio-dbgsym_3.1.2-11.1_amd64.deb
 cab17d0d430b60b2a92a44a53ff67c61a509730974207ec1dcf4bedbb1e12bec 39392 
bsdcpio_3.1.2-11.1_amd64.deb
 10abfbd8ba6a3a2b7dc0d521fdda61a34530bf96443fc7dc0ee716783839e13e 46360 
bsdtar-dbgsym_3.1.2-11.1_amd64.deb
 7448cea1f7fa178c5ece8caf8fd2fb4706fbcd6f97ed7a7f7a589a6857c3ddda 53808 
bsdtar_3.1.2-11.1_amd64.deb
 

Bug#823984: marked as done (libarchive13/unstable is older than libarchive13/stable)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 09:53:04 +
with message-id 
and subject line Bug#823984: fixed in libarchive 3.1.2-11.1
has caused the Debian Bug report #823984,
regarding libarchive13/unstable is older than libarchive13/stable
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.)


-- 
823984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libarchive13
Version: 3.1.2-11+b1
Severity: grave
Justification: renders package unusable

libarchive13 from unstable is now older than the version from stable
(due to a security update). Thus it is no longer installable, because
the version from stable (which is selected by default) cannot be
installed in unstable:

libarchive13 : Depends: libnettle4 (>= 2.3) but it is not going to be installed

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 libarchive13 depends on:
ii  libacl1 2.2.52-3
ii  libattr11:2.4.47-2
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.22-7
ii  liblzma55.1.1alpha+20120614-2.1
ii  liblzo2-2   2.08-1.2
ii  libnettle6  3.2-1
ii  libxml2 2.9.3+dfsg1-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

libarchive13 recommends no packages.

Versions of packages libarchive13 suggests:
pn  lrzip  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libarchive
Source-Version: 3.1.2-11.1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libarchive 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, 16 May 2016 09:46:05 +0100
Source: libarchive
Binary: libarchive-dev libarchive13 bsdtar bsdcpio
Architecture: amd64 source
Version: 3.1.2-11.1
Distribution: unstable
Urgency: high
Maintainer: Debian Libarchive Maintainers 
Changed-By: Simon McVittie 
Closes: 823893 823984
Description: 
 bsdcpio- Implementation of the 'cpio' program from FreeBSD
 bsdtar - Implementation of the 'tar' program from FreeBSD
 libarchive13 - Multi-format archive and compression library (shared library)
 libarchive-dev - Multi-format archive and compression library (development 
files)
Changes:
 libarchive (3.1.2-11.1) unstable; urgency=high
 .
   * Non-maintainer upload.
 - Make libarchive/unstable catch up with libarchive/stable
   (Closes: #823984)
 .
   [ Salvatore Bonaccorso ]
   * CVE-2016-1541: heap-based buffer overflow due to improper input
 validation (Closes: #823893)
Checksums-Sha1: 
 ec25d752ead61a1b367f4f24c43d0b6a59284422 2275 libarchive_3.1.2-11.1.dsc
 30a83cc6aff08394efa7215db7d6da6681ecb6d6 15356 
libarchive_3.1.2-11.1.debian.tar.xz
 9644f65bbcf4eb06c9c91eee9f60dd93e8402865 26322 
bsdcpio-dbgsym_3.1.2-11.1_amd64.deb
 03e75b7c56b5275d98d2fe745c4fcf0ba3bf442e 39392 bsdcpio_3.1.2-11.1_amd64.deb
 b9e2f714fdecc0c6d7582ad92956ddc3c3a843d9 46360 
bsdtar-dbgsym_3.1.2-11.1_amd64.deb
 b0fb316aa887b8817606c7ec36032046d0918979 53808 bsdtar_3.1.2-11.1_amd64.deb
 ed74ec6eed114c9676b6f8460a64661c84443ed0 429448 
libarchive-dev_3.1.2-11.1_amd64.deb
 7398d14faecca1e45109b24fd7763dd44489c6c8 702668 
libarchive13-dbgsym_3.1.2-11.1_amd64.deb
 7c320688e4231d2feb3fbaed2043bb134a4ae7bf 265848 
libarchive13_3.1.2-11.1_amd64.deb
Checksums-Sha256: 
 7f5453b9e7c8de99bf67e38e67ea63e8ab03518e6b955d625c3d28fcc0d3b327 2275 
libarchive_3.1.2-11.1.dsc
 459cc3b691b5c043b3d8009588d8f9446de12214f994c2b2c3208120a9a563bb 15356 
libarchive_3.1.2-11.1.debian.tar.xz
 6acbe648b855903af0f0696dccfe6f446fd3655aba2466d314a284fa5d391ae4 

Processed: Re: warzone2100: FTBFS in testing (maybe missing Build-Conflicts)

[Debian Bug Tracking System]

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

> tags 824011 + patch
Bug #824011 [src:warzone2100] warzone2100: FTBFS in testing (maybe missing 
Build-Conflicts)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#820447: marked as done (libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 11:48:12 +0200
with message-id <20160516094812.ge4...@gnuservers.com.ar>
and subject line Changing bug status to closed
has caused the Debian Bug report #820447,
regarding libkf5libkdepim5,oxygen5-icon-theme: error when trying to install 
together
to be marked as done.

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

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


-- 
820447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkf5libkdepim5,oxygen5-icon-theme
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 4:15.12.1-1
Control: found -1 5.19.0-1

Hi,

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

  Selecting previously unselected package libkf5libkdepim5.
  Preparing to unpack .../libkf5libkdepim5_4%3a15.12.1-1_amd64.deb ...
  Unpacking libkf5libkdepim5 (4:15.12.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libkf5libkdepim5_4%3a15.12.1-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/icons/oxygen/128x128/mimetypes/x-mail-distribution-list.png', which 
is also in package oxygen5-icon-theme 5.19.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for experimental/amd64, which may be
slightly out of sync):

  usr/share/icons/oxygen/128x128/mimetypes/x-mail-distribution-list.png
  usr/share/icons/oxygen/16x16/mimetypes/x-mail-distribution-list.png
  usr/share/icons/oxygen/22x22/mimetypes/x-mail-distribution-list.png
  usr/share/icons/oxygen/256x256/mimetypes/x-mail-distribution-list.png
  usr/share/icons/oxygen/32x32/mimetypes/x-mail-distribution-list.png
  usr/share/icons/oxygen/48x48/mimetypes/x-mail-distribution-list.png

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


oxygen5-icon-theme=5.19.0-1_libkf5libkdepim5=4%15.12.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

Version: 5.21.0-1

Somehow the bug mangling changed the status back to open.
Please, reopen if this was intentional.

Happy hacking,
--
"There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence."
-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature
--- End Message ---

Bug#824011: warzone2100: FTBFS in testing (maybe missing Build-Conflicts)

[Santiago Vila]

tags 824011 + patch
thanks

Patch attached.

In either case, I recommend that you still try to reproduce the bug to
fully understand it. Here is the way to reproduce it:

* Create a stretch chroot (with debootstrap).

* Install debhelper in the chroot. This will automatically install
  "automake" as a dependency.

* Then try to build warzone2100 with a command line like this:

sbuild -d stretch -A warzone2100_3.1.1-3

You will get a nice FTBFS like the one I attached in the initial bug report.

This is what happens: sbuild knows that it has to install automake1.11
because it's in the build-depends, so it does install it, but
then configure still detects normal automake (because nowhere it's said
that it has to be removed), and it fails.

When the Build-Conflicts is in place, sbuild knows that it has to remove
"automake" (in addition to installing automake1.11), and you can see
this in the build log:

The following packages will be REMOVED:
  automake*

As I said in the previous email, Build-Conflicts exist precisely
to deal with cases like this one.

Another solution would be to modify debian/rules so that automake1.11
is detected instead of automake when both are installed. I don't know
how to do that, but if you manage to do that way, it would also fix
the bug.

Hope this helps.

Thanks.--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,8 @@ Build-Depends:
  xsltproc,
  xvfb,
  zip
+Build-Conflicts:
+ automake
 Standards-Version: 3.9.8
 Homepage: http://www.wz2100.net/
 Vcs-Svn: svn://anonscm.debian.org/pkg-games/packages/trunk/warzone2100/

Bug#823893: libarchive: CVE-2016-1541

[Simon McVittie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 16 May 2016 at 11:25:31 +0200, Andreas Henriksson wrote:
> Please feel free to go ahead with NMU without delay (as already mentioned
> to Salvatore)!

Thanks, rescheduled to 0-day.

> I'll focus on 3.2.0 myself which means I'll likely just ignore your NMU
> if you base it on 3.1.2 when I feel 3.2.0 is ready to go to unstable
> (unless you have strong opinions on having your NMU changelog entry
> merged).

Not merging 3.1.2-11.1 is fine, as long as the BTS version-tracking is happy
(#823893 is already marked as fixed in 3.2.0, I'll mark #823984 as fixed
there too).

S
-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXOZQJAAoJEE3o/ypjx8yQpHcP/1aioiphA4HItEvUjPCZI5nu
frJn6ebrsrj5OmpCitT12xzF2fojeAzw+05+lEeqMRLydTOALFO6hDXpH++sB/mT
B4k3sGweEg+RpkK0HY76I1C+NLHmswqULNQ7WEbcPCwqkkDsPmMnLfLPZh68SvSq
zHuYG+miHlIUX9Jvn1Myr4XyfS1hv/z1I0u+XZzpIN3UJLbh9eg7onOqvMHqXMkA
1Ki2AJkL9mXB1o2V5yJtqpnNfB0qQTvuELZ0yo6kjE4A/A2lMvTPOrUkQcbx9yS9
Kqgw1s5Fo5gOW5AKNNXwYe1Y2FWLWKNEw6IxiU+ClNMOzXVYy1GodBMO9CidbMo9
eZGbhYoivdrEYqI7KC5k4/+asxmfG/SGNcLY1FWzRAlS5tlJbs6Qd4dkX7EhQcxw
kYTHxRj4xRu+hHvsXWT/KKvAwWeVg5iaIbMzk7Ovun4NRQDWUjN0OC5tv6jQCZqK
8sRAIVQg+cx3pYUSZbNYre79b/SJ89D66IZnW4mGEs0xBuhtA92dYsEVZ6yMgnOQ
fkj/qcl6ivPRh0yGbRJgc20gceWlrCip3ooQi0J2snerZUq+Blj8Ig5OzeXrfNa9
FjhS0mQnkaNLaWTQ6sdG0KlQAyHxc9VATOrxMGRHhXekkOF9ulnDMoGnLkaEsFfy
ktuNI/VIobQAoy/ejZGU
=Xr3y
-END PGP SIGNATURE-

Bug#823984: libarchive13/unstable is older than libarchive13/stable

[Simon McVittie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Version: 3.2.0-1

On Wed, 11 May 2016 at 02:52:08 +0200, Vincent Lefevre wrote:
> libarchive13 from unstable is now older than the version from stable
> (due to a security update).

This will be fixed when a version based on 3.2.0 reaches unstable.
Updating the BTS version-tracking accordingly.

For a stop-gap solution until 3.2.0 is ready, I've done a non-maintainer
upload versioned 3.1.2-11.1 which will also close this bug.

S
-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXOZSUAAoJEE3o/ypjx8yQODwP/2NMI9317WwaKwzysF1ivUDX
Bscktrl+6L6yyI9TFYUPHkGhC3/ZhLWW1zAl9X5gY2r10rXIIB9DTnlVifmLNBg0
Z7NiCxZxfd3QD+4OgW2uiwiYu2YodA0qQAY4MpNUp7OHynjx2XG1yR2qzj5Dik+S
7j/GhRq/9y1OajmuewifMKOfaAovqzSvUDu30MXM20WthjolJzHGaE5LFZx6rRXl
koC6GgteTxsSAo0GJfCbTFKmT+5WlYugMVbAEBj/VAO3pxtJOYXnGyy+6eHcO4Qm
t6v/guMXptUGqJhrLvICpv5ICqGzdOzrhro+ewNNR0u3ARYyuHwrP5xLi7Eddamf
Tkv5YW7YAsJwrgDVtPe+nd+5AcCG1WSjRn+FHalCGoJLFvEkucIBgFZ8TciS+YLE
yQenuQXnRC4wXAJlvdgIRM/jFGPPhUceZmbRdPF0abDsipNIVrNvoZ+BoxKjons0
ZclKipq2lLdnhawAaCMeDbpdTJvrsOfEvtF6mcdTlGfVjUAnWrpxNr/DyD6CA2xX
cXDokIH6kreQtuf52f1n70z3ryfaYjMdMNvyo2aOY/uDUlImgG5ZlCbj5uZ1qQwQ
25fjSa0yXzVleqUtEtWsOYlt4aHcd1f4X+3MAbVVapMIM5jGRkxc0UYgy4T/ppUv
YoKAbuV5Tg7afeD7FwUy
=JmIL
-END PGP SIGNATURE-

Bug#823893: libarchive: CVE-2016-1541

[Andreas Henriksson]

Hello Simon McVittie.

On Mon, May 16, 2016 at 10:12:19AM +0100, Simon McVittie wrote:
[...]
> uploaded to DELAYED/5. Diff attached, or available here:
> ssh://alioth.debian.org/srv/home/users/smcv/public_git/libarchive.git
> 
> If you would like it accelerated or cancelled, please let me know; or

Please feel free to go ahead with NMU without delay (as already mentioned
to Salvatore)!

> if you decide to go ahead with 3.2.0 or a 3.1.2-12 maintainer upload
> in unstable so that my NMU is superseded and rejected, that's also fine
> of course.

I'll focus on 3.2.0 myself which means I'll likely just ignore your NMU
if you base it on 3.1.2 when I feel 3.2.0 is ready to go to unstable
(unless you have strong opinions on having your NMU changelog entry
merged).

> 
> I'll open a separate bug for the test failure. Since you are the
> libarchive maintainer, you get to decide whether you consider failures on
> the non-release kFreeBSD architectures to be RC. Because the kFreeBSD
> architectures aren't release architectures, I believe out-of-date
> binaries on those architectures don't slow down testing migration,
> so fixing the security vulnerability on Linux doesn't need to block on
> fixing the tests on kFreeBSD.

Thanks. I don't consider kfreebsd a "real" blocker as this bug should
not be RC, but given that AFAIK libarchive has a pretty exploding
reverse dependency chain many important parts of the archive could
quickly become unbuildable I thought it would be nice to give the
kfreebsd porters a chance to reply to
https://lists.debian.org/debian-bsd/2016/05/msg00032.html
before proceeding. Not that I have super high hopes of getting a reply
and I'll certainly not wait forever... just giving them a chance (so
in another week or a bit more maybe I'll just upload).

Regards,
Andreas Henriksson

PS. Help maintaining libarchive welcome!

Processed: Re: Bug#823893: libarchive: CVE-2016-1541

[Debian Bug Tracking System]

Processing control commands:

> tags 823893 + pending
Bug #823893 [src:libarchive] libarchive: CVE-2016-1541
Added tag(s) pending.
> tags 823984 + pending
Bug #823984 [libarchive13] libarchive13/unstable is older than 
libarchive13/stable
Added tag(s) pending.

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

Bug#823893: libarchive: CVE-2016-1541

[Simon McVittie]

Control: tags 823893 + pending
Control: tags 823984 + pending

On Tue, 10 May 2016 at 09:18:26 +0200, Andreas Henriksson wrote:
> I'm torn on uploading 3.2.0 to unstable now because of regressing on
> kfreebsd where we now have test failures because of FTBFS. Feel free to
> NMU to unstable as well if you think it's urgent to get it fixed and
> don't want to wait for giving kfreebsd porters time to look at the
> regression.

I think it would have been better to upload *something* with the security
fix immediately, if not 3.2.0 then a patched 3.1.2; either way, if it
had been high or medium urgency and had no new RC bugs, then testing
would not be vulnerable by now.

libarchive/stable is uninstallable in unstable due to the libnettle
transition, so to keep this moving, I've prepared an NMU which I have
uploaded to DELAYED/5. Diff attached, or available here:
ssh://alioth.debian.org/srv/home/users/smcv/public_git/libarchive.git

If you would like it accelerated or cancelled, please let me know; or
if you decide to go ahead with 3.2.0 or a 3.1.2-12 maintainer upload
in unstable so that my NMU is superseded and rejected, that's also fine
of course.

I'll open a separate bug for the test failure. Since you are the
libarchive maintainer, you get to decide whether you consider failures on
the non-release kFreeBSD architectures to be RC. Because the kFreeBSD
architectures aren't release architectures, I believe out-of-date
binaries on those architectures don't slow down testing migration,
so fixing the security vulnerability on Linux doesn't need to block on
fixing the tests on kFreeBSD.

S
>From 8be0f04dc6f9e8955e99346f234d1188b43ecf9b Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Mon, 16 May 2016 09:46:56 +0100
Subject: [PATCH] Make libarchive/unstable catch up with libarchive/stable
 (Closes: #823984)

* CVE-2016-1541: heap-based buffer overflow due to improper input
  validation (Closes: #823893)
---
 debian/changelog   | 12 
 .../Issue-656-Fix-CVE-2016-1541-VU-862384.patch| 65 ++
 debian/patches/series  |  1 +
 3 files changed, 78 insertions(+)
 create mode 100644 debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch

diff --git a/debian/changelog b/debian/changelog
index 2f53cae..a982094 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+libarchive (3.1.2-11.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+- Make libarchive/unstable catch up with libarchive/stable
+  (Closes: #823984)
+
+  [ Salvatore Bonaccorso ]
+  * CVE-2016-1541: heap-based buffer overflow due to improper input
+validation (Closes: #823893)
+
+ -- Simon McVittie   Mon, 16 May 2016 09:46:05 +0100
+
 libarchive (3.1.2-11) unstable; urgency=medium
 
   * Add d/p/Add-ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS-option.patch
diff --git a/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch b/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch
new file mode 100644
index 000..22a1bb2
--- /dev/null
+++ b/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch
@@ -0,0 +1,65 @@
+From d0331e8e5b05b475f20b1f3101fe1ad772d7e7e7 Mon Sep 17 00:00:00 2001
+From: Tim Kientzle 
+Date: Sun, 24 Apr 2016 17:13:45 -0700
+Subject: [PATCH] Issue #656:  Fix CVE-2016-1541, VU#862384
+
+When reading OS X metadata entries in Zip archives that were stored
+without compression, libarchive would use the uncompressed entry size
+to allocate a buffer but would use the compressed entry size to limit
+the amount of data copied into that buffer.  Since the compressed
+and uncompressed sizes are provided by data in the archive itself,
+an attacker could manipulate these values to write data beyond
+the end of the allocated buffer.
+
+This fix provides three new checks to guard against such
+manipulation and to make libarchive generally more robust when
+handling this type of entry:
+ 1. If an OS X metadata entry is stored without compression,
+abort the entire archive if the compressed and uncompressed
+data sizes do not match.
+ 2. When sanity-checking the size of an OS X metadata entry,
+abort this entry if either the compressed or uncompressed
+size is larger than 4MB.
+ 3. When copying data into the allocated buffer, check the copy
+size against both the compressed entry size and uncompressed
+entry size.
+---
+ libarchive/archive_read_support_format_zip.c | 13 +
+ 1 file changed, 13 insertions(+)
+
+--- a/libarchive/archive_read_support_format_zip.c
 b/libarchive/archive_read_support_format_zip.c
+@@ -560,6 +560,11 @@ zip_read_mac_metadata(struct archive_rea
+ 
+ 	switch(rsrc->compression) {
+ 	case 0:  /* No compression. */
++		if (rsrc->uncompressed_size != rsrc->compressed_size) {
++			archive_set_error(>archive, ARCHIVE_ERRNO_FILE_FORMAT,
++			"Malformed OS X metadata entry: inconsistent size");
++			return 

Processed: Re: Bug#823893: libarchive: CVE-2016-1541

[Debian Bug Tracking System]

Processing control commands:

> tags 823893 + pending
Bug #823893 [src:libarchive] libarchive: CVE-2016-1541
Ignoring request to alter tags of bug #823893 to the same tags previously set
> tags 823984 + pending
Bug #823984 [libarchive13] libarchive13/unstable is older than 
libarchive13/stable
Ignoring request to alter tags of bug #823984 to the same tags previously set

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

Processed: closing 791745

[Debian Bug Tracking System]

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

> close 791745
Bug #791745 [kwayland] FTBFS with GCC 5: changes to symbols file
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#791745: closing 791745

[Maximiliano Curia]

close 791745 
thanks

Closing the bug, it has been fixed in all the available versions.
-- 
Saludos,
Maxy

Bug#824426: FTBFS against libical2

[Andreas Henriksson]

Hello!

Some information below which might be useful

On Sun, May 15, 2016 at 09:37:24PM +0200, Michael Biebl wrote:
> Source: syncevolution
> Version: 1.4.99.4-5
> Severity: serious
> 
> Hi,
> 
> during the libical transition [1], your package syncevolution was
> rebuilt and it now FTBFS:
[...]
> src/syncevo/.libs/libsyncevolution.so: undefined reference to
> `ical_tzid_prefix'
[...]

I've quickly looked into this issue since it was discovered
(sorry I missed spotting it before the transition started).

The global variable referenced above is indeed gone (in general
libical seems to be moving away from global variables in 2.0.0
in favour of accessor methods). The new accessor function to
get the value is called icaltimezone_tzid_prefix(). See:
http://sources.debian.net/src/libical/2.0.0-0.4/src/libical/icaltimezone.c/?hl=150#L150

I looked upstream but there seemed to be very little activity in recent time.
Possibly there's some bug tracker or mailing list post somewhere, but I
didn't search that far.

The libical2 transition has already been done in fedora so for comparison
they're patching their syncevolution, see:
http://pkgs.fedoraproject.org/cgit/rpms/syncevolution.git/tree/syncevolution-1.5.1-libical2.patch

IMNSHO the fedora patch is an ugly hack since duplicating the information
instead of using accessor method isn't nice IMO. OTOH I've looked at
syncevolutions usage of the global variable and if we're going to replace
it we see it in two places. The one failing the build above + in the
syncevolution homebrew/duplicated evolution(-data-server?) API.
That one looks too scary to touch for me who has no way to test this
so I sympathize with fedoras patch and maybe it's better to go that
route. Also, the get accessor seems to be missing from the libical2.symbols
for some reason so might need fixes on the libical side to be properly
exported

Regards,
Andreas Henriksson

Bug#823688: marked as done (sitesummary: prerm called with unknown argument `upgrade')

[Debian Bug Tracking System]

Your message dated Mon, 16 May 2016 07:33:37 +
with message-id 
and subject line Bug#823688: fixed in sitesummary 0.1.21
has caused the Debian Bug report #823688,
regarding sitesummary: prerm 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.)


-- 
823688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sitesummary
Version: 0.1.20
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...):

0m37.5s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp5IwKQK', 
'apt-get', '-y', 'install', '--reinstall', 'sitesummary=0.1.20']
0m38.6s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  debconf: delaying package configuration, since apt-utils is not installed
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/45.1 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 
(Reading database ... 9514 files and directories currently installed.)
  Preparing to unpack .../sitesummary_0.1.20_all.deb ...
  prerm called with unknown argument `upgrade'
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  prerm called with unknown argument `failed-upgrade'
  dpkg: error processing archive 
/var/cache/apt/archives/sitesummary_0.1.20_all.deb (--unpack):
   subprocess new pre-removal script returned error exit status 1
  Errors were encountered while processing:
   /var/cache/apt/archives/sitesummary_0.1.20_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
0m38.6s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmp5IwKQK', 'apt-get', '-y', 'install', '--reinstall', 
'sitesummary=0.1.20']


Cheers,

Andreas


sitesummary_0.1.20.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sitesummary
Source-Version: 0.1.21

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated sitesummary 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, 16 May 2016 09:21:25 +0200
Source: sitesummary
Binary: sitesummary sitesummary-client
Architecture: source
Version: 0.1.21
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Petter Reinholdtsen 
Description:
 sitesummary - Generate site summary of submitting hosts (server part)
 sitesummary-client - Generate site summary of submitting hosts (client part)
Closes: 803720 816940 823688
Changes:
 sitesummary (0.1.21) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * Fix sitesummary.prerm (Closes: #823688).
 .
   [ Petter Reinholdtsen ]
   * Add Brazilian Portuguese (pt_BR) translation by Adriano Rafael Gomes
 (Closes: #816940).
   * Adjust nagios kernel version checking module to work with recent
 Ubuntu kernels (Closes: #803720).  Patch from Daniele Palumbo.
   * Updated Standards-Version 3.9.6 to 3.9.8.
   * Added Wolfgang Schweer as uploader.
   * Use Testsuite, not obsolete XS-Testsuite, in control file to
 indicate a autopkgtest is available.
Checksums-Sha1:
 b495c9f070e1860ab07a784f559fc876f0e9277b 1915 sitesummary_0.1.21.dsc
 70c4413bf6a2549a7225425a18fe4f4b09680dc8 77249 sitesummary_0.1.21.tar.gz
Checksums-Sha256:
 a59f9f760621fbd9c07cb3028e4cfa0227edfd1ef97d9d9c473eb7d4f8ec1097 1915 
sitesummary_0.1.21.dsc
 2ab449218bc56900c4b3eb46a3d2d3c324840fe56819061e84460a13e644aa9a 

Bug#821523: Bug#821691: fixed in owfs 3.1p1-4

[Vincent Danjean]

Le 16/05/2016 08:12, Logan Rosen a écrit :
> Hi,
> 
> On Sat, 07 May 2016 09:57:28 + Vincent Danjean  
> wrote:
>> Source: owfs
>> Source-Version: 3.1p1-4
>>
>> We believe that the bug you reported is fixed in the latest version of
>> owfs, which is due to be installed in the Debian FTP archive.
> 
> This bug actually isn't totally fixed in owfs 3.1p1-4. libownet-php
> depends on php5 | php5-cli, which should be changed to php | php-cli.
> Can you please change the dependency accordingly?

Oups, sorry. I just uploaded 3.1p1-5 that should fix this:
$ debdiff owfs_3.1p1-4.dsc owfs_3.1p1-5.dsc
diff -Nru owfs-3.1p1/debian/changelog owfs-3.1p1/debian/changelog
--- owfs-3.1p1/debian/changelog 2016-05-07 11:09:23.0 +0200
+++ owfs-3.1p1/debian/changelog 2016-05-16 08:53:52.0 +0200
@@ -1,3 +1,9 @@
+owfs (3.1p1-5) unstable; urgency=medium
+
+  * really fix php dependencies (Thanks Logan Rosen)
+
+ -- Vincent Danjean   Mon, 16 May 2016 08:53:29 +0200
+
 owfs (3.1p1-4) unstable; urgency=medium

   * Remove php bindings. Swig do not support php7 (yet) and Debian not
diff -Nru owfs-3.1p1/debian/control owfs-3.1p1/debian/control
--- owfs-3.1p1/debian/control   2016-05-07 11:09:23.0 +0200
+++ owfs-3.1p1/debian/control   2016-05-16 08:53:52.0 +0200
@@ -227,7 +227,7 @@
 Package: libownet-php
 Architecture: all
 Section: web
-Depends: php5 | php5-cli,
+Depends: php | php-cli,
  ${misc:Depends}
 Description: Dallas 1-wire support: PHP OWNet library
  The 1-Wire bus is a cheap low-speed bus for devices like weather

> Thanks,
> Logan
> 

  Regards,
Vincent

-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#821523: Bug#821691: fixed in owfs 3.1p1-4

[Logan Rosen]

Hi,

On Sat, 07 May 2016 09:57:28 + Vincent Danjean  wrote:
> Source: owfs
> Source-Version: 3.1p1-4
>
> We believe that the bug you reported is fixed in the latest version of
> owfs, which is due to be installed in the Debian FTP archive.

This bug actually isn't totally fixed in owfs 3.1p1-4. libownet-php
depends on php5 | php5-cli, which should be changed to php | php-cli.
Can you please change the dependency accordingly?

Thanks,
Logan