Bug#815404: Acknowledgement (linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 Carbon)

[Russel Winder]

I just upgraded and got the kernel 4.4.2-3 (2016-02-21) which seems to
boot fine.

Thanks for dealing with this very quickly, it is much appreciated.

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



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

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

[Sven Barth]

Am 22.02.2016 07:16 schrieb "Abou Al Montacir" :
>
> I finally managed to find the wrong option! It is -fPIC.
> Below are  tests with only -fPIC and with only -O2.
>
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
fpc -fPIC test2 && ./test2
>
> Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
>
> Copyright (c) 1993-2015 by Florian Klaempfl and others
>
> Target OS: Linux for ARMEL
>
> Compiling test2.pas
>
> Assembling test
>
> Linking test2
>
> /usr/bin/ld.bfd: warning: link.res contains output sections; did you
forget -T?
>
> 4 lines compiled, 0.3 sec
>
> Runtime error 103 at $000101D8
>
>   $000101D8
>
>   $00010124
>
>
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
fpc -O2 test2 && ./test2
>
> Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
>
> Copyright (c) 1993-2015 by Florian Klaempfl and others
>
> Target OS: Linux for ARMEL
>
> Compiling test2.pas
>
> Assembling test
>
> Linking test2
>
> /usr/bin/ld.bfd: warning: link.res contains output sections; did you
forget -T?
>
> 4 lines compiled, 0.3 sec
>
> Hello
>
> (sid_armel-dchroot)abou@abel
:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
>
>
>  Looks like PIC code was broken in 3.0. Is there anyone aware of that?
How can we fix that?
>

Would you please try the current development version of FPC (3.1.1) to
check whether the issue persists there?

Regards,
Sven

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

[Abou Al Montacir]

Dear All,
On Mon, 2016-02-22 at 00:32 +0100, Abou Al Montacir wrote:
> Hi Paul,
> 
> On Wed, 2016-02-17 at 22:26 +0100, Paul Gevers wrote:
> > Hmm, I was a tiny little bit wrong earlier.
> > 
> > I modified hedgewars a tiny bit (patch attached) and build in on
> > debomatic¹. You can see that the failing line reads:
> > "Lua test file specified: /<>/tests/lua/hellfire_burns.lua"
> ...
> > Anyways, it now fails for an access violation. I don't like this at all,
> > but it is hard to say if this is a fpc error or hedgewars'.
> I've tried some simpler code and it looks like the compilation options used by
> hedgewars cause the issue. I don't know if this is normal or not but at least
> we know now that it is not an issue in the code itself but rather in the
> compilation flags.
> 
> I'm copying FPC core in case some one can help with the impact of the used
> compilation flags.
> 
> Here are my experimentation:
> I first created very small programs:
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ cat test1.pas 
> program test;
> begin
> WriteLn('Hello');
> end.
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ cat test2.pas 
> program test;
> begin
> WriteLn(stdout, 'Hello');
> end.
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ 
> 
> I first compile using no special flags and both programs execute well:
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ fpc test1
> Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
> Copyright (c) 1993-2015 by Florian Klaempfl and others
> Target OS: Linux for ARMEL
> Compiling test1.pas
> Assembling test
> Linking test1
> /usr/bin/ld.bfd: warning: link.res contains output sections; did you forget
> -T?
> 4 lines compiled, 0.3 sec
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ ./test1
> Hello
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ fpc test2
> Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
> Copyright (c) 1993-2015 by Florian Klaempfl and others
> Target OS: Linux for ARMEL
> Compiling test2.pas
> Assembling test
> Linking test2
> /usr/bin/ld.bfd: warning: link.res contains output sections; did you forget
> -T?
> 4 lines compiled, 0.3 sec
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ ./test2
> Hello
> 
> Now, we use a subset of compilation flags from hedgewars and we can just
> reproduce the issue on second program but not the first one:
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ fpc -FU/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars/CMakeFiles/hwengine.dir -k-rpath
> -k'\$ORIGIN/../lib/:\$ORIGIN/:/usr/lib/hedgewars/lib/' -FD/usr/bin -Cs200
> -fPIC -Fl/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/bin -k-
> L/usr/lib/arm-linux-gnueabi -Fl/usr/lib/arm-linux-gnueabi -Fl/usr/lib/arm-
> linux-gnueabi -XLAlua=lua5.1 -Fl/usr/lib/arm-linux-gnueabi/libphysfs.so -O2 -g
> -gl -gp   -dUSE_VIDEO_RECORDING -dPNG_SCREENSHOTS -dSDL_MIXER_NEWER
> -dSDL_IMAGE_NEWER -dDEBUGFILE  test1
> Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
> Copyright (c) 1993-2015 by Florian Klaempfl and others
> Target OS: Linux for ARMEL
> Compiling test1.pas
> Assembling test
> Linking test1
> /usr/bin/ld.bfd: warning: link.res contains output sections; did you forget
> -T?
> 4 lines compiled, 0.3 sec
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ ./test1
> Hello
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ fpc -FU/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars/CMakeFiles/hwengine.dir -k-rpath
> -k'\$ORIGIN/../lib/:\$ORIGIN/:/usr/lib/hedgewars/lib/' -FD/usr/bin -Cs200
> -fPIC -Fl/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/bin -k-
> L/usr/lib/arm-linux-gnueabi -Fl/usr/lib/arm-linux-gnueabi -Fl/usr/lib/arm-
> linux-gnueabi -XLAlua=lua5.1 -Fl/usr/lib/arm-linux-gnueabi/libphysfs.so -O2 -g
> -gl -gp   -dUSE_VIDEO_RECORDING -dPNG_SCREENSHOTS -dSDL_MIXER_NEWER
> -dSDL_IMAGE_NEWER -dDEBUGFILE  test2
> Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
> Copyright (c) 1993-2015 by Florian Klaempfl and others
> Target OS: Linux for ARMEL
> Compiling test2.pas
> Assembling test
> Linking test2
> /usr/bin/ld.bfd: warning: link.res contains output sections; did you forget
> -T?
> 4 lines compiled, 0.3 sec
> (sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
> gnueabi/hedgewars$ ./test2
> Runtime error 103 at $000101C8
>   $000101C8  $main,  line 3 of test2.pas
> 
> It is not clear for me why RTE 103 is thrown, in the second case but not in
> the first one. I'd expect either both work or neither. Also I don't see what
> is the impact of 

Processed: Re: Bug#815485: [geneweb] Geneweb 6.x should not be compiled with OCAML >=4.02 (build dependency problem)

[Debian Bug Tracking System]

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

> severity 815485 serious
Bug #815485 [geneweb] [geneweb] Geneweb 6.x should not be compiled with OCAML 
>=4.02 (build dependency problem)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#684499: Streaming MOVE commands

[Jaldhar H. Vyas]

On Mon, 22 Feb 2016, Timo Sirainen wrote:


On 21 Feb 2016, at 13:46, Emilio Jesús Gallego Arias  
wrote:


Hello Timo,

Timo Sirainen  writes:


Thanks, looks like this was broken with Maildir and mbox formats. It
also caused expunges in some other situations to be lost. Fixed:

https://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b2895bc32b827


Thanks a lot for the fix, testing it now!

Is this patch suitable of being backported to 2.2.13? (Debian stable)


Should be.



This will definitely go into the upcoming 2.2.21 packages. (After a long 
period of stasis we're going to bring everything up to date again soon.)


I don't know if the release team will allow it for stable even though it 
is a minor change but I'll definitely bring it up for their consideration.


--
Jaldhar H. Vyas 

Bug#815521: openafs dkms module incompatible with Linux 4.4 kernel

[Benjamin Kaduk]

Yes, the incompatibility of any version of openafs with the linux kernel
4.4 and newer is known upstream.  In addition to the build-breaking
changes in linux, there are some changes in when ERESTART can be returned,
that openafs is also unadapted for; running with just the patches to fix
the build could lead to data corruption.

Unfortunately, it does not seem that anyone from upstream has been able to
investigate the scope of such issues or propose a patch, so I do not
expect there to be a version of openafs usable with the recent kernel for
some time.

-Ben

Processed: retitle 815521 to openafs dkms module incompatible with Linux 4.4 kernel

[Debian Bug Tracking System]

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

> retitle 815521 openafs dkms module incompatible with Linux 4.4 kernel
Bug #815521 [openafs-modules-dkms] DKMS module fails to build
Changed Bug title to 'openafs dkms module incompatible with Linux 4.4 kernel' 
from 'DKMS module fails to build'
> thanks
Stopping processing here.

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

Processed: tagging 815521

[Debian Bug Tracking System]

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

> tags 815521 + upstream
Bug #815521 [openafs-modules-dkms] DKMS module fails to build
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#815521: (no subject)

[Ryan Kavanagh]

package openafs
tags 815521 + upstream
retitle 815521 openafs dkms module incompatible with Linux 4.4 kernel
thanks

This bug appears to be known by upstream:
http://comments.gmane.org/gmane.comp.file-systems.openafs.devel/11924

-- 
|_)|_/  Ryan Kavanagh   | Debian Developer
| \| \  http://ryanak.ca/   | GPG Key 4A11C97A

Bug#815521: DKMS module fails to build

[Ryan Kavanagh]

Package: openafs-modules-dkms
Version: 1.6.15-1
Severity: grave
Justification: renders package unusable

The package fails to compile the kernel module, rendering AFS unusable.
I've attached the file /var/lib/dkms/openafs/1.6.15/build/make.log .
Attempting to (re)install the package produces the following output on
terminal:

 Uninstall Beginning 
Module:  openafs
Version: 1.6.15
Kernel:  4.3.0-1-amd64 (x86_64)
-

Status: Before uninstall, this module version was ACTIVE on this kernel.

openafs.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.3.0-1-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod

DKMS: uninstall completed.

--
Deleting module version: 1.6.15
completely from the DKMS tree.
--
Done.
Unpacking openafs-modules-dkms (1.6.15-1) over (1.6.15-1) ...
Setting up openafs-modules-dkms (1.6.15-1) ...
Loading new openafs-1.6.15 DKMS files...
Building only for 4.4.0-1-amd64
Building initial module for 4.4.0-1-amd64
Error! Bad return status for module build on kernel: 4.4.0-1-amd64 (x86_64)
Consult /var/lib/dkms/openafs/1.6.15/build/make.log for more information.


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

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

Versions of packages openafs-modules-dkms depends on:
ii  dkms   2.2.0.3-2
ii  libc6-dev  2.21-9
ii  perl   5.22.1-7

Versions of packages openafs-modules-dkms recommends:
ii  openafs-client  1.6.15-1

openafs-modules-dkms suggests no packages.

-- no debconf information

-- 
|_)|_/  Ryan Kavanagh   | Debian Developer
| \| \  http://ryanak.ca/   | GPG Key 4A11C97A
DKMS make.log for openafs-1.6.15 for kernel 4.4.0-1-amd64 (x86_64)
Sun Feb 21 20:20:55 EST 2016
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/var/lib/dkms/openafs/1.6.15/build/build-tools/missing: Unknown 
`--is-lightweight' option
Try `/var/lib/dkms/openafs/1.6.15/build/build-tools/missing --help' for more 
information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for flex... no
checking for lex... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libxslt... no
checking for saxon... no
checking for xalan-j... no
checking for xsltproc... no
checking for docbook2pdf... no
checking for dblatex... no
checking for library containing strerror... none required
checking for pid_t... yes
checking for size_t... yes
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for bison... no
checking for byacc... no
checking if lex is flex... no
checking whether byte order is known at compile time... yes
checking whether byte ordering is bigendian... no
checking whether printf understands the %z length modifier... yes
checking your OS... linux
checking if gcc accepts -march=pentium... no
checking if gcc needs -fno-strength-reduce... yes
checking if gcc needs -fno-strict-aliasing... yes
checking if gcc supports -fno-common... yes
checking if gcc supports -pipe... yes
checking if linux kbuild requires EXTRA_CFLAGS... yes
checking for linux kernel module build works... yes
checking operation follow_link 

Bug#815516: linux-image-4.4.0-1-amd64: Hangs at loading ramdisk

[Gretar Magnusson]

Thank you Ben, it is indeed the same bug. Reinstalled 15 minutes ago
and booted fine.



On Mon, 2016-02-22 at 01:07 +, Ben Hutchings wrote:
> Control: reassign -1 src:linux 4.4.2-2
> Control: tag -1 - lfs
> Control: forcemerge 815125 -1
> 
> On Mon, 2016-02-22 at 00:08 +, Gretar Magnusson wrote:
> > Package: linux-image-4.4.0-1-amd64
> > Version: 4.4.2-2
> > Severity: critical
> > Tags: lfs
> > Justification: breaks the whole system
> > 
> > Dear Maintainer,
> > 
> > 
> >    * What led up to the situation? Kernel upgrade
> >    * What exactly did you do (or not do) that was effective (or
> >  ineffective)? I tried update-grub but made no difference
> 
> This is almost certainly the same as bug #815125 which was fixed
> today
> in version 4.4.2-3.
> 
> Ben.
> 

Processed: Re: Bug#815516: linux-image-4.4.0-1-amd64: Hangs at loading ramdisk

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 4.4.2-2
Bug #815516 [linux-image-4.4.0-1-amd64] linux-image-4.4.0-1-amd64: Hangs at 
loading ramdisk
Bug reassigned from package 'linux-image-4.4.0-1-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.4.2-2.
Ignoring request to alter fixed versions of bug #815516 to the same values 
previously set
Bug #815516 [src:linux] linux-image-4.4.0-1-amd64: Hangs at loading ramdisk
Marked as found in versions linux/4.4.2-2.
> tag -1 - lfs
Bug #815516 [src:linux] linux-image-4.4.0-1-amd64: Hangs at loading ramdisk
Removed tag(s) lfs.
> forcemerge 815125 -1
Bug #815125 {Done: Ben Hutchings } [src:linux] 
linux-image-4.4.0-1-amd64 fails to load initrd - no booting
Bug #815126 {Done: Ben Hutchings } [src:linux] 
linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...'
Bug #815173 {Done: Ben Hutchings } [src:linux] 
kernel-image-4.4.0-1-amd64 does not boot on my Thinkpad X240
Bug #815404 {Done: Ben Hutchings } [src:linux] 
linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 Carbon
Bug #815516 [src:linux] linux-image-4.4.0-1-amd64: Hangs at loading ramdisk
Marked Bug as done
Marked as fixed in versions linux/4.4.2-3.
Marked as found in versions linux/4.4.2-1.
Added tag(s) moreinfo.
Bug #815126 {Done: Ben Hutchings } [src:linux] 
linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...'
Bug #815173 {Done: Ben Hutchings } [src:linux] 
kernel-image-4.4.0-1-amd64 does not boot on my Thinkpad X240
Bug #815404 {Done: Ben Hutchings } [src:linux] 
linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 Carbon
Merged 815125 815126 815173 815404 815516

-- 
815125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125
815126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815126
815173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815173
815404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815404
815516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#815516: linux-image-4.4.0-1-amd64: Hangs at loading ramdisk

[Ben Hutchings]

Control: reassign -1 src:linux 4.4.2-2
Control: tag -1 - lfs
Control: forcemerge 815125 -1

On Mon, 2016-02-22 at 00:08 +, Gretar Magnusson wrote:
> Package: linux-image-4.4.0-1-amd64
> Version: 4.4.2-2
> Severity: critical
> Tags: lfs
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> 
>    * What led up to the situation? Kernel upgrade
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)? I tried update-grub but made no difference

This is almost certainly the same as bug #815125 which was fixed today
in version 4.4.2-3.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou

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

Bug#814807: marked as done (ffmpeg: FTBFS on mips)

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2016 01:55:29 +0100
with message-id <20160222005529.gb23...@ramacher.at>
and subject line Re: Bug#814807: ffmpeg: FTBFS on mips
has caused the Debian Bug report #814807,
regarding ffmpeg: FTBFS on mips
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.)


-- 
814807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ffmpeg
Version: 7:2.8.5-1+b1
Severity: serious

Your package failed to build on mips:

[roq_dpcm @ 0xa345a0] packet is too small
Error while decoding stream #0:0: Invalid argument
/«PKGBUILDDIR»/debian/standard/tests/data/fate/acodec-roqaudio.roq: Invalid 
data found when processing input
size=   0kB time=00:00:00.00 bitrate=N/A
video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing 
overhead: unknown
Output file is empty, nothing was encoded (check -ss / -t / -frames parameters 
if used)
Conversion failed!
/«PKGBUILDDIR»/tests/Makefile:203: recipe for target 'fate-acodec-roqaudio' 
failed
make[2]: *** [fate-acodec-roqaudio] Error 69

Full logs at:

https://buildd.debian.org/status/logs.php?pkg=ffmpeg=7%3A2.8.6-1=mips
--- End Message ---
--- Begin Message ---
On 2016-02-15 17:03:44, Emilio Pozuelo Monfort wrote:
> Package: ffmpeg
> Version: 7:2.8.5-1+b1
> Severity: serious
> 
> Your package failed to build on mips:
> 
> [roq_dpcm @ 0xa345a0] packet is too small
> Error while decoding stream #0:0: Invalid argument
> /«PKGBUILDDIR»/debian/standard/tests/data/fate/acodec-roqaudio.roq: Invalid 
> data found when processing input
> size=   0kB time=00:00:00.00 bitrate=N/A
> video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing 
> overhead: unknown
> Output file is empty, nothing was encoded (check -ss / -t / -frames 
> parameters if used)
> Conversion failed!
> /«PKGBUILDDIR»/tests/Makefile:203: recipe for target 'fate-acodec-roqaudio' 
> failed
> make[2]: *** [fate-acodec-roqaudio] Error 69

With #813858 fixed in gcc, this is no longer an issue.

Cheers
-- 
Sebastian Ramacher


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

Bug#802398: marked as done (dipy: FTBFS: FAIL: dipy.core.tests.test_sphere.test_interp_rbf)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 19:54:55 -0500
with message-id <20160222005455.ga7...@onerussian.com>
and subject line was resolved
has caused the Debian Bug report #802398,
regarding dipy: FTBFS: FAIL: dipy.core.tests.test_sphere.test_interp_rbf
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.)


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

Dear Maintainer,

The package fails to build:

dipy.tests.test_scripts.test_qb_commandline ... ok

==
FAIL: dipy.core.tests.test_sphere.test_interp_rbf
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/dipy-0.7.1/debian/tmp/usr/lib/python2.7/dist-packages/dipy/core/tests/test_sphere.py",
 line 359, in test_interp_rbf
nt.assert_(np.mean(np.abs(interp_data_a - expected)) < 0.1)
  File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 53, in 
assert_
raise AssertionError(smsg)
AssertionError

--
Ran 211 tests in 16.885s

FAILED (SKIP=4, failures=1)
Downloading "testfile.txt" to /tmp/tmphB36ns

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

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

This version built successfully across many architectures and
debian/ubuntu releases, so I guess this issue was resolved upstream ;)

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Processed: notfound 815494 in 4.0.5+dfsg-3+b1, found 815494 in 4.1.4-3

[Debian Bug Tracking System]

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

> notfound 815494 4.0.5+dfsg-3+b1
Bug #815494 [src:zeromq3] zeromq3: FTBFS, with test suite errors
The source 'zeromq3' and version '4.0.5+dfsg-3+b1' do not appear to match any 
binary packages
No longer marked as found in versions zeromq3/4.0.5+dfsg-3+b1.
> found 815494 4.1.4-3
Bug #815494 [src:zeromq3] zeromq3: FTBFS, with test suite errors
Marked as found in versions zeromq3/4.1.4-3.
> thanks
Stopping processing here.

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

Bug#782179: marked as done (apt-zip: apt-zip-list --aptgetaction=update doesn't do anything because "apt-get -qq --print-uris update" outputs nothing)

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2016 00:46:09 +
with message-id 
and subject line Bug#815456: Removed package(s) from unstable
has caused the Debian Bug report #782179,
regarding apt-zip: apt-zip-list --aptgetaction=update doesn't do anything 
because "apt-get -qq --print-uris update" outputs nothing
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.)


-- 
782179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-zip
Version: 0.18
Severity: grave
Tags: patch jessie sid
Justification: Updating package lists silently broken

Dear Maintainer,

"apt-zip-list --aptgetaction=update" does nothing on Jessie:

# apt-zip-list --medium=/tmp/apt-zip-test/ --skip-mount --aptgetaction=update 
-o tar --no-md5
The download size is unknown in 0 files.
#

Reason is that "apt-get -qq --print-uris update" has no output at all
anymore:

# apt-get -qq --print-uris update
#

The expected output comes back if I remove one "q":

# apt-get -q --print-uris update
'http://debian.ethz.ch/debian/dists/jessie/main/source/Sources.bz2' 
debian.ethz.ch_debian_dists_jessie_main_source_Sources 0 :
'http://debian.ethz.ch/debian/dists/jessie/main/binary-amd64/Packages.bz2' 
debian.ethz.ch_debian_dists_jessie_main_binary-amd64_Packages 0 :
'http://debian.ethz.ch/debian/dists/jessie/main/i18n/Translation-en.bz2' 
debian.ethz.ch_debian_dists_jessie_main_i18n_Translation-en 0 :
'http://debian.ethz.ch/debian/dists/jessie/InRelease' 
debian.ethz.ch_debian_dists_jessie_InRelease 0 
[...]
#

The following patch fixes the issue:

diff --git a/apt-zip-list b/apt-zip-list
index f5d7acb..49bb69e 100755
--- a/apt-zip-list
+++ b/apt-zip-list
@@ -33,9 +33,15 @@ APTGETEXTRAOPTS="${APTGETEXTRAOPTS} -o Debug::NoLocking=true"
 TMP=$(tempfile -p aptzip)
 TEMP=$(tempfile -p aptzip)
 
+if [ "$APTGETACTION" = update ]; then
+APTGETQUIETLEVEL=-q
+else
+APTGETQUIETLEVEL=-qq
+fi
+
 [ -n "$PACKAGES" ] && apt-get ${APTGETEXTRAOPTS} -qq --print-uris install 
$PACKAGES > "$TMP"
-[ -n "$APTGETACTION" ] && apt-get ${APTGETEXTRAOPTS} -qq --print-uris 
${APTGETACTION} >> "$TMP"
+[ -n "$APTGETACTION" ] && apt-get ${APTGETEXTRAOPTS} ${APTGETQUIETLEVEL} 
--print-uris ${APTGETACTION} >> "$TMP"
 grep $GREP < "$TMP" | tr -d "'" | sed 's/MD5Sum://' | sort -u > "$TEMP"
 if [ $? != 0 ]
 then

(The above patch can be applied after the patch from #638840 has been
applied.)

-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)

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

Versions of packages apt-zip depends on:
ii  apt  1.0.9.7

apt-zip recommends no packages.

apt-zip suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.18+rm

Dear submitter,

as the package apt-zip 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/815456

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#724173: marked as done (slimrat: FTBFS: POD errors)

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2016 00:48:34 +
with message-id 
and subject line Bug#815459: Removed package(s) from unstable
has caused the Debian Bug report #724173,
regarding slimrat: FTBFS: POD errors
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.)


-- 
724173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slimrat
Version: 1.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> rm -f debian/manpages
> test -d debian/pod2man || mkdir debian/pod2man
> for i in slimrat slimrat-gui; do \
>   pod2man --section=8 src/$i > debian/pod2man/$i.8; \
>   done
> Wide character in printf at /usr/share/perl/5.18/Pod/Simple.pm line 539.
> src/slimrat around line 600: Non-ASCII character seen before =encoding in 
> 'Přemek'. Assuming UTF-8
> POD document had syntax errors at /usr/bin/pod2man line 71.
> Wide character in printf at /usr/share/perl/5.18/Pod/Simple.pm line 539.
> src/slimrat-gui around line 683: Non-ASCII character seen before =encoding in 
> 'Přemek'. Assuming UTF-8
> POD document had syntax errors at /usr/bin/pod2man line 71.
> make[1]: *** [override_dh_installman] Error 255

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/slimrat_1.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.0-1+rm

Dear submitter,

as the package slimrat 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/815459

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#781915: marked as done (Checksum fails and other issues in Jessie)

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2016 00:46:09 +
with message-id 
and subject line Bug#815456: Removed package(s) from unstable
has caused the Debian Bug report #781915,
regarding Checksum fails and other issues in Jessie
to be marked as done.

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

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


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

Package: apt-zip
Version: 0.18
Severity: grave


Hi!


Machine A (Debian Wheezy without net connection, pendrive mounted in 
/media/3E77-C915, hostname=s3v3land-laptop)
machine B (Debian Jessie connected to the Internet, pendrive mounted in 
/media/s3v/3E77-C915, hostname=s3v3land)





with --no-md5 option




1) Machine A


# apt-zip-list --medium=/media/3E77-C915 --aptgetaction=update -o tar 
--no-md5

The download size is unknown in 41 files




1a) fetch-script-wget-s3v3land-laptop content:

 #!/bin/sh
 # This file was auto-generated by apt-zip-list 0.18
 # Method: wget - Options:  TAR

 err(){
echo >&2 "Fetching $1 failed ($2)"
 }
 check(){
[ ! -r "$1" ] && return 1
[ "$2" = "0" ] && return $3
[ "$2" = "" ] && return $3
[ "`type sha256sum`" ] &&
if [ "`sha256sum $1 | cut -d' ' -f1`" = $2 ]
then return 0
else err $1 "wrong checksum"; return 1
fi
[ "`type gzip`" ] &&
if ar p $1 data.tar.gz | gzip -t
then return 0
else err $1 "wrong contents"; return 1
fi
return $3
 }

 do_wget() {
wget -t3 -nv -O $2 $1
echo $2 $4 $?

return $?
 }


 getfile(){
FILE=""
for EXT in ".bz2" ".gz" ""
do
  do_wget $1$EXT $2$EXT $3 $4 &&
  FILE=$2$EXT &&
  break
  rm -f $2$EXT
done
[ "$FILE" = "" ] && return 1
tar rf debs-s3v3land-laptop.tar $FILE &&
rm $FILE
 }

 touch foo-stamp && "tar" cf "debs-s3v3land-laptop.tar" foo-stamp && rm 
foo-stamp


 echo Download will be of size: "unknown" in "41" files
 while read URL FILE SIZE CHECKSUM
 do getfile $URL $FILE $SIZE $CHECKSUM || true
 done 

Bug#815494: zeromq3: FTBFS, with test suite errors

[Aaron M. Ucko]

notfound zeromq3 4.0.5+dfsg-3+b1
found zeromq3 4.1.4-3
thanks

"László Böszörményi (GCS)"  writes:

>  You meant 4.1.4, right? It started with 4.1.x (4.1.2?) to be more
> precise in experimental.

Yes; I mostly run testing, and didn't notice that reportbug supplied the
wrong version number.  Metadata corrected.

>  Already done as I monitor buildd results.

Great, thanks; sorry for the noise.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#794148: marked as done (FTBFS: undefined method `mock' for #<RSpec::ExampleGroups::YARDCLICommandParser::Run:..)

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2016 00:32:16 +
with message-id 
and subject line Bug#794148: fixed in yard 0.8.7.6+git20160220-1
has caused the Debian Bug report #794148,
regarding FTBFS: undefined method `mock' for 
#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yard
Version: 0.8.7.6-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build:

Failures:

  1) YARD::CLI::CommandParser#run should show help if --help is provided
 Failure/Error: command = mock(:command)
 NoMethodError:
   undefined method `mock' for 
#
 # ./spec/cli/command_parser_spec.rb:10:in `block (3 levels) in '



  7) YARD::CLI::Config Viewing an item should view item if no value is given
 Failure/Error: YARD::Config.stub!(:save)
 NoMethodError:
   undefined method `stub!' for YARD::Config:Class
 # ./spec/cli/config_spec.rb:9:in `block (2 levels) in '



/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb 
failed
ERROR: Test "ruby2.1" failed. Exiting.

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

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

Kernel: Linux 3.19.0-23-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 ---
Source: yard
Source-Version: 0.8.7.6+git20160220-1

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated yard 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, 22 Feb 2016 00:49:05 +0100
Source: yard
Binary: yard yard-doc
Architecture: source all
Version: 0.8.7.6+git20160220-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 yard   - Ruby documentation tool
 yard-doc   - Ruby documentation tool - documentation
Closes: 794148
Changes:
 yard (0.8.7.6+git20160220-1) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Imported snapshot from upstream git repository
 + test suite ported to RSpec 3 (Closes: #794148)
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Set debhelper compatibility level to 9
   * Use https:// in Vcs-* fields
   * Add privacy-breach.patch avoiding loading distant images in HTML
 documentation
Checksums-Sha1:
 511afda3a9ae924e06b0ec343a3c59d9b1b7b221 1909 yard_0.8.7.6+git20160220-1.dsc
 bdb30bedcc2bbf8657c23fb884c7e8f29e55d9d5 864898 
yard_0.8.7.6+git20160220.orig.tar.gz
 0fb95977086e363534676a4af58269286fc6763f 79324 
yard_0.8.7.6+git20160220-1.debian.tar.xz
 3fb9795cfb0a296da0f78e28df0a6dc08f3ff861 451362 
yard-doc_0.8.7.6+git20160220-1_all.deb
 60885c8176d78a482a250073814f41760e3ab831 227932 
yard_0.8.7.6+git20160220-1_all.deb
Checksums-Sha256:
 15ba9a5c9a743f0a13edd1aa2473ab048e1f0e224a8f9d7dd3480a51389f3bbb 1909 
yard_0.8.7.6+git20160220-1.dsc
 178db19fcfafd29ddedc5bb3e11f9986f6a649251ec0b0aa684d416c0b641cae 864898 
yard_0.8.7.6+git20160220.orig.tar.gz
 1d5cf2f30e6978b57735102ad133c04d9fcee7e1ebc5278075895e566d0e9757 79324 
yard_0.8.7.6+git20160220-1.debian.tar.xz
 95fe25c2133e87a6bf7f561c003e31f53ae3cc41a50a000d07b8538120e46150 451362 
yard-doc_0.8.7.6+git20160220-1_all.deb
 ba1885c1686f13b2a333222dc39da4d56e60b7a3cf0557f0e25136477b23fdb4 227932 
yard_0.8.7.6+git20160220-1_all.deb
Files:
 352cb31768e0b7975c644c9b005ae234 1909 ruby optional 
yard_0.8.7.6+git20160220-1.dsc
 6e6811794ee8ee2263c57d6f289b8795 864898 ruby optional 
yard_0.8.7.6+git20160220.orig.tar.gz
 08f008e28ab4e0f0b8cb8cc894317935 79324 ruby optional 
yard_0.8.7.6+git20160220-1.debian.tar.xz
 3520de5dfec376daa7ebe9f47cf0a965 451362 doc optional 
yard-doc_0.8.7.6+git20160220-1_all.deb
 38df710d15cc7309e661e5d23d7dd62a 227932 ruby optional 
yard_0.8.7.6+git20160220-1_all.deb

-BEGIN PGP SIGNATURE-

Bug#815516: linux-image-4.4.0-1-amd64: Hangs at loading ramdisk

[Gretar Magnusson]

Package: linux-image-4.4.0-1-amd64
Version: 4.4.2-2
Severity: critical
Tags: lfs
Justification: breaks the whole system

Dear Maintainer,


   * What led up to the situation? Kernel upgrade
   * What exactly did you do (or not do) that was effective (or
 ineffective)? I tried update-grub but made no difference




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

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

Versions of packages linux-image-4.4.0-1-amd64 depends on:
ii  debconf [debconf-2.0]   1.5.58
ii  initramfs-tools [linux-initramfs-tool]  0.123
ii  kmod22-1
ii  linux-base  4.0

Versions of packages linux-image-4.4.0-1-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2

Versions of packages linux-image-4.4.0-1-amd64 suggests:
pn  debian-kernel-handbook 
pn  grub-pc | grub-efi | extlinux  
pn  linux-doc-4.4  

Bug#789825: python-lockfile: diff for NMU version 1:0.10.2-2.1

[Ben Finney]

On 20-Feb-2016, Neil Williams wrote:

> I've prepared an NMU for python-lockfile (versioned as 1:0.10.2-2.1)
> and uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

I am working with the existing sponsor for this package, to make a new
release of a later upstream version. The release includes a fix for
this bug.

The sponsor is busy at the moment, so I should seek someone else to
help with this release.

Would you be willing to look at my changes, to sponsor this release?
I'll contact you away from this bug report if so.

-- 
 \ “It is not enough to have a good mind. The main thing is to use |
  `\ it well.” —Rene Descartes |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Processed (with 1 error): tagging 693633, notfixed 750361 in 36.0.1985.67-1, fixed 775514 in 1:1.30.4-1 ..., affects 792698 ...

[Debian Bug Tracking System]

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

> # housekeeping - fixing bug metadata to allow automatic archival
> tags 693633 - jessie stretch
Bug #693633 {Done: Jonas Smedegaard } [squeak-vm] squeak-vm: 
FTBFS on powerpcspe (asm stfd/lfd)
Removed tag(s) jessie and stretch.
> notfixed 750361 36.0.1985.67-1
Bug #750361 {Done: Michael Gilbert } [chromium] chromium: 
upstream dropped support for older i386 processors
Bug #750443 {Done: Michael Gilbert } [chromium] chromium: 
upstream dropped support for older i386 processors
Bug #750584 {Done: Michael Gilbert } [chromium] chromium 
35 for i386 is miscompiled - it crashes with SIGILL on SSE2 instructions
Bug #763290 {Done: Michael Gilbert } [chromium] chromium: 
v8 dropped support for non-sse2 systems
Bug #764291 {Done: Michael Gilbert } [chromium] chromium 
37 for i386 is miscompiled - it crashes on CMOV and SSE instructions
Bug #766883 {Done: Michael Gilbert } [chromium] chromium: 
crashes at startup with "Illegal instruction"
No longer marked as fixed in versions chromium-browser/36.0.1985.67-1.
No longer marked as fixed in versions chromium-browser/36.0.1985.67-1.
No longer marked as fixed in versions chromium-browser/36.0.1985.67-1.
No longer marked as fixed in versions chromium-browser/36.0.1985.67-1.
No longer marked as fixed in versions chromium-browser/36.0.1985.67-1.
No longer marked as fixed in versions chromium-browser/36.0.1985.67-1.
> fixed 775514 1:1.30.4-1
Bug #775514 {Done: Hilko Bengen } [libguestfs-tools] No 
networking running virt-builder scripts after upgrading from 1.26 to 1.28
Marked as fixed in versions libguestfs/1:1.30.4-1.
> reassign 792698 src:haskell-chart-cairo
Bug #792698 {Done: Debian Haskell Group 
} [libghc-chart-dev] 
libghc-chart-dev: Package is useless without at least one backend
Bug reassigned from package 'libghc-chart-dev' to 'src:haskell-chart-cairo'.
No longer marked as found in versions haskell-chart/1.3.3-4.
No longer marked as fixed in versions haskell-chart-cairo/1.3.3-1.
> fixed 792698 1.3.3-1
Bug #792698 {Done: Debian Haskell Group 
} [src:haskell-chart-cairo] 
libghc-chart-dev: Package is useless without at least one backend
Marked as fixed in versions haskell-chart-cairo/1.3.3-1.
> affects 792698 + libghc-chart-dev
Bug #792698 {Done: Debian Haskell Group 
} [src:haskell-chart-cairo] 
libghc-chart-dev: Package is useless without at least one backend
Added indication that 792698 affects libghc-chart-dev
> reassign 782345 src:automake-1.15
Bug #782345 {Done: Eric Dorland } [automake] automake: 
mdate-sh has undeterministic output
Bug reassigned from package 'automake' to 'src:automake-1.15'.
Ignoring request to alter found versions of bug #782345 to the same values 
previously set
No longer marked as fixed in versions automake-1.15/1:1.15-2.
> fixed 782345 1:1.15-2
Bug #782345 {Done: Eric Dorland } [src:automake-1.15] 
automake: mdate-sh has undeterministic output
Marked as fixed in versions automake-1.15/1:1.15-2.
> reassign 729866 python-simpy3
Bug #729866 {Done: Larissa Reis } [python3-simpy] 
python3-simpy: new upstream version 3.0+
Bug reassigned from package 'python3-simpy' to 'python-simpy3'.
No longer marked as found in versions python-simpy/2.3.1-1.
No longer marked as fixed in versions python-simpy3/3.0.7+dfsg-1.
> fixed 729866 3.0.7+dfsg-1
Bug #729866 {Done: Larissa Reis } [python-simpy3] 
python3-simpy: new upstream version 3.0+
Marked as fixed in versions python-simpy3/3.0.7+dfsg-1.
> reassign 760455 src:automake-1.15 1:1.15-2
Bug #760455 {Done: Eric Dorland } [automake] install-sh: 
insecure use of /tmp
Bug reassigned from package 'automake' to 'src:automake-1.15'.
No longer marked as found in versions automake-1.15/1:1.15-2 and 
automake-1.14/1:1.14.1-3.
No longer marked as fixed in versions automake-1.15/1:1.15-3.
Bug #760455 {Done: Eric Dorland } [src:automake-1.15] 
install-sh: insecure use of /tmp
Marked as found in versions automake-1.15/1:1.15-2.
> fixed 760455 1:1.15-3
Bug #760455 {Done: Eric Dorland } [src:automake-1.15] 
install-sh: insecure use of /tmp
Marked as fixed in versions automake-1.15/1:1.15-3.
> found 760455 1:1.14.1-3
Bug #760455 {Done: Eric Dorland } [src:automake-1.15] 
install-sh: insecure use of /tmp
The source 'automake-1.15' and version '1:1.14.1-3' do not appear to match any 
binary packages
Marked as found in versions automake-1.15/1:1.14.1-3.
> reassign 401936 src:automake-1.15
Bug #401936 {Done: Eric Dorland } [automake] automake1.10-doc: 
Broken links in info documentation
Bug reassigned from 

Processed: Re: aptitude: artificial report to prevent migrating the package to testing

[Debian Bug Tracking System]

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

> unarchive 802958
Bug #802958 {Done: "Manuel A. Fernandez Montecelo" 
} [aptitude] aptitude: artificial report to prevent 
migrating the package to testing
Unarchived Bug 802958
> reopen 802958
Bug #802958 {Done: "Manuel A. Fernandez Montecelo" 
} [aptitude] aptitude: artificial report to prevent 
migrating the package to testing
Bug reopened
Ignoring request to alter fixed versions of bug #802958 to the same values 
previously set
> notfound 802958 aptitude/0.7.4-1
Bug #802958 [aptitude] aptitude: artificial report to prevent migrating the 
package to testing
No longer marked as found in versions aptitude/0.7.4-1.
> found 802958 aptitude/0.7.6-1
Bug #802958 [aptitude] aptitude: artificial report to prevent migrating the 
package to testing
Marked as found in versions aptitude/0.7.6-1.
> stop
Stopping processing here.

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

Bug#809055: marked as done (unbound FTBFS, passes -Wdate-time to swig, which choke on it)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 23:35:02 +
with message-id 
and subject line Bug#809055: fixed in unbound 1.5.7-2
has caused the Debian Bug report #809055,
regarding unbound FTBFS, passes -Wdate-time to swig, which choke on it
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.)


-- 
809055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subversion,unbound,swig
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org


Hi subversion, unbound and swig maintainers,
we in the Reproducible Builds effort use a non default dpkg which export
-Wdate-time through dpkg-buildflags.

There are package that pass CPPFLAGS (for example) quite unchanged to swig.

Sadly swig does not recognize -Wdate-time and choke and fail on it badly, e.g.

/usr/bin/swig -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/python2.7 
-I/usr/include/python2.7 -o pythonmod/interface.h -python 
./pythonmod/interface.i
swig error : Unrecognized option -Wdate-time
Use 'swig -help' for available options.
Makefile:369: recipe for target 'pythonmod/interface.h' failed
make[1]: *** [pythonmod/interface.h] Error 1


Needless to say, I'd like to build those packages with such flag (that we also
would like to get into the default set, see the bug #762683 for a start).


Possible solutions i see for this:

a. swig stops failing so badly on unrecognized options. If you really want to
   validate the options at least stop failing on unrecognized -W? Seems quite
   logical to pass CPPFLAGS to swig to me, and as such sounds sane
b. people stop passing CPPFLAGS to swig. I've already saw a "CPPFLAGS cleaner"
   on subversion's configure script. Please I don't want to see another


Even if I do have preference I don't have a strong opinion on this, so if you
agree this is not a bug in swig (which I could even accept, given that the
accepted flags are well documented), I'll just clone+reassign this bug around.


Thanks for maintaining such packages!

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: unbound
Source-Version: 1.5.7-2

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

Debian distribution maintenance software
pp.
Robert Edmonds  (supplier of updated unbound 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, 21 Feb 2016 16:22:23 -0500
Source: unbound
Binary: libunbound-dev libunbound2 python-unbound unbound unbound-anchor 
unbound-host
Architecture: source
Version: 1.5.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Robert Edmonds 
Description:
 libunbound-dev - static library, header files, and docs for libunbound
 libunbound2 - library implementing DNS resolution and validation
 python-unbound - library implementing DNS resolution and validation (Python 
bindin
 unbound- validating, recursive, caching DNS resolver
 unbound-anchor - utility to securely fetch the root DNS trust anchor
 unbound-host - reimplementation of the 'host' command
Closes: 573329 760461 763901 777228 790392 809055
Changes:
 unbound (1.5.7-2) unstable; urgency=medium
 .
   * debian/control: Add dh-python to Build-Depends
   * debian/: Install contrib/update-anchor.sh, contrib/unbound_munin_
 (Closes: #573329)
   * Makefile.in: Pass PYTHON_CPPFLAGS to swig instead of CPPFLAGS (Closes:
 #809055)
   * debian/: Run "wrap-and-sort -sabt"
   * debian/resolvconf: No longer use 

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

[Abou Al Montacir]

Hi Paul,

On Wed, 2016-02-17 at 22:26 +0100, Paul Gevers wrote:
> Hmm, I was a tiny little bit wrong earlier.
> 
> I modified hedgewars a tiny bit (patch attached) and build in on
> debomatic¹. You can see that the failing line reads:
> "Lua test file specified: /<>/tests/lua/hellfire_burns.lua"
...
> Anyways, it now fails for an access violation. I don't like this at all,
> but it is hard to say if this is a fpc error or hedgewars'.
I've tried some simpler code and it looks like the compilation options used by
hedgewars cause the issue. I don't know if this is normal or not but at least we
know now that it is not an issue in the code itself but rather in the
compilation flags.
I'm copying FPC core in case some one can help with the impact of the used
compilation flags.
Here are my experimentation:
I first created very small programs:
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
gnueabi/hedgewars$ cat test1.pas 
program test;
begin
WriteLn('Hello');
end.
(sid
_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
gnueabi/hedgewars$ cat test2.pas 
program test;
begin
WriteLn(stdout, 'Hello');
end.
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-
gnueabi/hedgewars$ 
I first compile using no special flags and both programs execute well:
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 fpc test1
Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for ARMEL
Compiling test1.pas
Assembling test
Linking test1
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
4 lines compiled, 0.3 sec
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 ./test1
Hello
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 fpc test2
Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for ARMEL
Compiling test2.pas
Assembling test
Linking test2
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
4 lines compiled, 0.3 sec
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 ./test2
Hello
Now, we use a subset of compilation flags from hedgewars and we can just
reproduce the issue on second program but not the first one:
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 fpc 
-FU/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars/CMakeFiles/hwengine.dir
 -k-rpath -k'\$ORIGIN/../lib/:\$ORIGIN/:/usr/lib/hedgewars/lib/' -FD/usr/bin 
-Cs200 -fPIC -Fl/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/bin 
-k-L/usr/lib/arm-linux-gnueabi -Fl/usr/lib/arm-linux-gnueabi 
-Fl/usr/lib/arm-linux-gnueabi -XLAlua=lua5.1 
-Fl/usr/lib/arm-linux-gnueabi/libphysfs.so -O2 -g -gl -gp   
-dUSE_VIDEO_RECORDING -dPNG_SCREENSHOTS -dSDL_MIXER_NEWER -dSDL_IMAGE_NEWER 
-dDEBUGFILE  test1
Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for ARMEL
Compiling test1.pas
Assembling test
Linking test1
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
4 lines compiled, 0.3 sec
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 ./test1
Hello
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 fpc 
-FU/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars/CMakeFiles/hwengine.dir
 -k-rpath -k'\$ORIGIN/../lib/:\$ORIGIN/:/usr/lib/hedgewars/lib/' -FD/usr/bin 
-Cs200 -fPIC -Fl/home/abou/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/bin 
-k-L/usr/lib/arm-linux-gnueabi -Fl/usr/lib/arm-linux-gnueabi 
-Fl/usr/lib/arm-linux-gnueabi -XLAlua=lua5.1 
-Fl/usr/lib/arm-linux-gnueabi/libphysfs.so -O2 -g -gl -gp   
-dUSE_VIDEO_RECORDING -dPNG_SCREENSHOTS -dSDL_MIXER_NEWER -dSDL_IMAGE_NEWER 
-dDEBUGFILE  test2
Free Pascal Compiler version 3.0.0+dfsg-2 [2016/01/28] for arm
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for ARMEL
Compiling test2.pas
Assembling test
Linking test2
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
4 lines compiled, 0.3 sec
(sid_armel-dchroot)abou@abel:~/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabi/hedgewars$
 ./test2
Runtime error 103 at $000101C8
  $000101C8  $main,  line 3 of test2.pas
It is not clear for me why RTE 103 is thrown, in the second case but not in the
first one. I'd expect either both work or neither. Also I don't see what is the
impact of the compilation flags that are used. Maybe I should perform more
experimentations in order to find a smaller subset. but that will be enough for
tonight!
-- 
Cheers,
Abou Al Montacir


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

Bug#815494: zeromq3: FTBFS, with test suite errors

[GCS]

On Sun, Feb 21, 2016 at 10:52 PM, Aaron M. Ucko  wrote:
> Source: zeromq3
> Version: 4.0.5+dfsg-3+b1
 You meant 4.1.4, right? It started with 4.1.x (4.1.2?) to be more
precise in experimental.

> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Builds of zeromq3 failed for many architectures with test suite
> errors,
[...]
> Could you please take a look?
 Already done as I monitor buildd results. The strange thing is that
in my pbuilder chroots the build always succeeded. It seems buildds
have some restriction that make tests fail, to be aborted to be exact.
I've already disabled some, but then other ones failed.
At the moment I have a plan to run those, but make the fails non
fatal. Then upstream may know something about the reason.

Cheers,
Laszlo/GCS

Bug#814171: marked as done (plm: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 22:36:04 +
with message-id 
and subject line Bug#814171: fixed in plm 2.6+repack-2
has caused the Debian Bug report #814171,
regarding plm: (Build-)Depends on OpenJDK 7
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.)


-- 
814171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:plm
Version: 2.6+repack-1
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
Source: plm
Source-Version: 2.6+repack-2

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated plm 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, 21 Feb 2016 21:23:01 +0100
Source: plm
Binary: plm
Architecture: source all
Version: 2.6+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 plm- Programming exerciser in Java, Python, Scala and others
Closes: 814171
Changes:
 plm (2.6+repack-2) unstable; urgency=medium
 .
   * Build-dep on default-jdk instead of specifying the version manually.
 (Closes: #814171)
Checksums-Sha1:
 b77228b9f67f974b816d5be0b299317f1bf58738 2102 plm_2.6+repack-2.dsc
 c4e1b837fbf134b0c95d358667cbcf93a183ff9d 46404 plm_2.6+repack-2.debian.tar.xz
 4f401f337956b975a33e0fa745a5d81ff7ffbb04 2977172 plm_2.6+repack-2_all.deb
Checksums-Sha256:
 e4a65a36dbdf5e1a6857a3ddb2c6f0a97f5dec80716b7050f3e88840d1fe6045 2102 
plm_2.6+repack-2.dsc
 b03931a35e9953e390feee0d4b8a4bb401f4c94aa03fb0ae1094d382cd95eca6 46404 
plm_2.6+repack-2.debian.tar.xz
 59fe80722186dbabb7daaef9cd245fc96af71c766087b872a09c8439a8dafc92 2977172 
plm_2.6+repack-2_all.deb
Files:
 a0e3e97568e8464667c32ca465bd12fc 2102 java extra plm_2.6+repack-2.dsc
 4d6c690356dde5ef17d4e77d61405ef1 46404 java extra 
plm_2.6+repack-2.debian.tar.xz
 07b4f98fcde12feddd0a4187274165a2 2977172 java extra plm_2.6+repack-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWyh59AAoJEJi9lyRPc76neRAP/2MuQruCfjdg/QwiOzM5qgg6
5Xx+jtTr+H2tHmxNOtPRKl4OERdSbzp367ZT/pRBRgSUsxsIk4wcY/6uejknMglp
VQYOiwmnz7i3kETah6zJgsoISfRLTx/iQMt7DxFAErHteHu53UToz9kE7L0H726T
b0MlAeSeSPchWtfK46SL15jlLHQTOKuOR90ADt7kXkyOWyMkW+dI++Q0LugPEq6o
Eba+FWU1M5gxS6EThFh4YYaSM31c8xJiRvRifRATDk1bgffuEO8LHEAJb/nBmZ2W
VTASvQoh3knVTlyT2JeLBZi88Vm8pL+my4xowOhKdwBsQWsnVD54wTRlY8sVUxW1
YucUXfpyvxkdNJAWowos4syfp8msHw6A7OJpX+mqBmiJAyZIV6rBBrRGoF43kEQY
w/dIpyJWBCd2YBaPxw9rSuSWFB2chpVHEayCy0abD94c90vK6gbP9trzsRKIfasm
EATFoFT8jMVZpdpLbtG1moELD+dK/c0SqJfmiFjyVVsoF/z1mxB14I5h/DqF5iMs
xXnu3yDEYg6eKsTb74hPWsKbTjxaHfn0H9AgI+pkf/SKNQvBZSZj+cE9N0imsCht
EFW+kpVIYrK9HYMUKlISiqMzduZGQxeuqwJIkXacafcUr/ygTp2KVtgqKzqiFENK
u7iWbmF3vLCjssxT1x3v
=O55n
-END PGP SIGNATURE End Message ---

Bug#815385: marked as done (python-service-identity: Missing dependency on python-attr)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 22:37:21 +
with message-id 
and subject line Bug#815385: fixed in python-service-identity 16.0.0-2
has caused the Debian Bug report #815385,
regarding python-service-identity: Missing dependency on python-attr
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.)


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

service_identity 16.0.0-1 requires python-attrs (upstream switched from
characteristic to attrs), but the Depends: is missing.

Also, it would be unsatisfiable due to attrs not being packaged yet, but I am
about to upload a package to NEW.

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

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

Versions of packages python-service-identity depends on:
ii  python-openssl 0.15.1-2
ii  python-pyasn1  0.1.9-1
ii  python-pyasn1-modules  0.0.7-0.1
pn  python:any 

Versions of packages python-service-identity recommends:
ii  python-idna  2.0-3

python-service-identity suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-service-identity
Source-Version: 16.0.0-2

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

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

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated 
python-service-identity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Feb 2016 23:30:43 +0200
Source: python-service-identity
Binary: python-service-identity python3-service-identity
Architecture: source
Version: 16.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Tristan Seligmann 
Description:
 python-service-identity - Service identity verification for pyOpenSSL (Python 
2 module)
 python3-service-identity - Service identity verification for pyOpenSSL (Python 
3 module)
Closes: 815385
Changes:
 python-service-identity (16.0.0-2) unstable; urgency=medium
 .
   * Adopt package; thanks to Matthias Klose for his work so far.
   * Update debian/watch to check signatures and use https.
   * Switch python{,3}-characteristic dependency to python{,3}-attr
 (closes: #815385).
Checksums-Sha1:
 3bad1c83fdc91234c84b3f74af5b54fa5d9cc79b 2270 
python-service-identity_16.0.0-2.dsc
 91b633a922126fe39fe5a92582b57f2bc0eff84a 7268 
python-service-identity_16.0.0-2.debian.tar.xz
Checksums-Sha256:
 0e16603cc18d980e8d65827744ea3d1741d062fb3e3e668c2f838999c911f45e 2270 
python-service-identity_16.0.0-2.dsc
 a9ad741d5ef1ffad30c96faf3c6a12f4387b2a3da1a9319987003236526bf993 7268 
python-service-identity_16.0.0-2.debian.tar.xz
Files:
 d6446527277f16ff9c7f85c9ec72a7cc 2270 python optional 
python-service-identity_16.0.0-2.dsc
 b52cc3d5c27dad5955c3b70139c12624 7268 python optional 
python-service-identity_16.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJWyizuXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1QzA2NTY4NTc1NTE2RDBBMzNGRkE3QTND
MDg5OTBGQjFGNjM3ODkzAAoJEMCJkPsfY3iTLbwH+wXG8Pmmo09w3+igoCVdLNnc
ZRtCEUfk6jo4U5hj5usxkfOsexxz2p2z5RYDjBINY8GL0kGSPIjHIKHYs+xm9Khj
Gxukvg985h1iE+1IEvHKvXwq9q9tiEjaC1OggvSvPzNv9w/LNxWgoodeJHMdhz8n
3xoGjXS2nDY3b1f9l2a5PNtd20DJnc0PbxGjaPC+DDM+IFYNvTPnqbrZEwWNtRam
GNEef1DbZwvDGWpAND29qsiwXOuTHDNRkBE4QzIT3a4+h6hCM6O7JTdhp8LU761s
5PqebKNfBw+pwmUWOA77zI+P6e4N2rc/2T92VXEDLDdWn8DPdelQRzwjMbgBF1k=
=mrQy
-END PGP SIGNATURE End Message 

Bug#809592: marked as done (plplot: FTBFS: x00a.adb:30:05: file "plplot_auxiliary.ads" not found)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 22:36:52 +
with message-id 
and subject line Bug#809592: fixed in plplot 5.10.0+dfsg2-0.2
has caused the Debian Bug report #809592,
regarding plplot: FTBFS: x00a.adb:30:05: file "plplot_auxiliary.ads" not found
to be marked as done.

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

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


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

Dear Maintainer,

The package fails to build:

 debian/rules build
make: Nothing to be done for 'build'.
 debian/rules binary
slice -o UNDEF+ADA:debian/control debian/control.in
make: mkoctfile: Command not found
make: mkoctfile: Command not found
make: mkoctfile: Command not found
mkdir -p /plplot-5.10.0+dfsg2/debian/build_tmp
( cd /plplot-5.10.0+dfsg2/debian/build_tmp ; \

...

[ 21%] Building Ada object examples/ada/CMakeFiles/x00a.dir/x00a.o
x00a.adb:30:05: file "plplot_auxiliary.ads" not found
x00a.adb:31:05: file "plplot_traditional.ads" not found
examples/ada/CMakeFiles/x00a.dir/build.make:62: recipe for target 
'examples/ada/CMakeFiles/x00a.dir/x00a.o' failed
make[3]: *** [examples/ada/CMakeFiles/x00a.dir/x00a.o] Error 1
make[3]: Leaving directory '/plplot-5.10.0+dfsg2/debian/build_tmp'
CMakeFiles/Makefile2:: recipe for target 
'examples/ada/CMakeFiles/x00a.dir/all' failed
make[2]: *** [examples/ada/CMakeFiles/x00a.dir/all] Error 2
make[2]: Leaving directory '/plplot-5.10.0+dfsg2/debian/build_tmp'
Makefile:160: recipe for target 'all' failed

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: plplot
Source-Version: 5.10.0+dfsg2-0.2

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated plplot 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, 16 Feb 2016 22:32:30 +0100
Source: plplot
Binary: libplplot12 libplplot-dev libplplot-c++11 libplplot-fortran10 
libplplot-java libcsiro0 libqsastime0 libqsastime-dev plplot12-driver-xwin 
plplot12-driver-wxwidgets plplot-tcl plplot-tcl-bin plplot-tcl-dev 
plplot12-driver-cairo python-plplot python-plplot-qt plplot-doc 
plplot12-driver-qt libplplot-ocaml libplplot-lua
Architecture: source amd64 all
Version: 5.10.0+dfsg2-0.2
Distribution: unstable
Urgency: medium
Maintainer: Andrew Ross 
Changed-By: Axel Beckert 
Description:
 libcsiro0  - Scientific plotting library (CSIRO libraries)
 libplplot-c++11 - Scientific plotting library (C++ binding)
 libplplot-dev - Scientific plotting library (development files)
 libplplot-fortran10 - Scientific plotting library (fortran bindings)
 libplplot-java - Scientific plotting library (Java bindings)
 libplplot-lua - Scientific plotting library (lua bindings)
 libplplot-ocaml - Scientific plotting library (OCaml bindings)
 libplplot12 - Scientific plotting library
 libqsastime-dev - Time format conversion library (development files)
 libqsastime0 - Time format conversion library
 plplot-doc - Documentation for PLplot, a plotting library
 plplot-tcl - Tcl/Tk support for PLplot, a plotting library
 plplot-tcl-bin - Tcl/Tk tools for PLplot, a plotting library
 plplot-tcl-dev - Tcl/Tk development support for PLplot, a plotting library
 plplot12-driver-cairo - Scientific plotting library (Cairo driver)
 plplot12-driver-qt - Scientific plotting library (qt driver)
 plplot12-driver-wxwidgets - Scientific plotting library (wxWidgets driver)
 plplot12-driver-xwin - Scientific plotting library (X11 

Bug#814591: marked as done (insighttoolkit4: testsuite failure on i386)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 22:28:56 +
with message-id 
and subject line Bug#814591: fixed in insighttoolkit4 4.9.0-2
has caused the Debian Bug report #814591,
regarding insighttoolkit4: testsuite failure on i386
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.)


-- 
814591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: testsuite failure on i386
Package: insighttoolkit4
Version: 4.9.0-1
Severity: serious
Tags: upstream
Forwarded: https://issues.itk.org/jira/browse/ITK-3413


Hi Insighttookit4 maintainers!
After the upload of castxml yesterday, the i386 build has been fixed (you can 
see the ubuntu log [1],
please note: ~4MB file, don't open in a browser!)
https://launchpad.net/ubuntu/+source/insighttoolkit4/4.9.0-1ubuntu1/+build/8996751

as you can see now the problem is a testsuite failure of a single test.


The following tests FAILED:
1591 - itkFlatStructuringElementTest2 (Failed)
Errors while running CTest


1591/2730 Testing: itkFlatStructuringElementTest2
1591/2730 Test: itkFlatStructuringElementTest2
Command: "/«PKGBUILDDIR»/BUILD/bin/ITKMathematicalMorphologyTestDriver" 
"--compare" 
"/«PKGBUILDDIR»/BUILD/ExternalData/Modules/Filtering/MathematicalMorphology/test/Baseline/FlatStructuringElementImageTest.png"
 "/«PKGBUILDDIR»/BUILD/Testing/Temporary/FlatStructuringElementImageTest.png" 
"itkFlatStructuringElementTest2" 
"/«PKGBUILDDIR»/BUILD/ExternalData/Modules/Filtering/MathematicalMorphology/test/Baseline/FlatStructuringElementImageTest.png"
 "/«PKGBUILDDIR»/BUILD/Testing/Temporary/FlatStructuringElementImageTest.png"
Directory: /«PKGBUILDDIR»/BUILD/Modules/Filtering/MathematicalMorphology/test
"itkFlatStructuringElementTest2" start time: Feb 13 07:11 UTC
Output:
--
49
49
255
255
255
/«PKGBUILDDIR»/BUILD/Testing/Temporary/FlatStructuringElementImageTest.png.diff.png
/«PKGBUILDDIR»/BUILD/Testing/Temporary/FlatStructuringElementImageTest.png.base.png
/«PKGBUILDDIR»/BUILD/Testing/Temporary/FlatStructuringElementImageTest.png.test.png
FlatStructuringElementImageTest.png

Test time =   0.10 sec
--
Test Failed.
"itkFlatStructuringElementTest2" end time: Feb 13 07:11 UTC
"itkFlatStructuringElementTest2" time elapsed: 00:00:00
--



[1] 
https://launchpadlibrarian.net/238349570/buildlog_ubuntu-xenial-i386.insighttoolkit4_4.9.0-1ubuntu1_BUILDING.txt.gz

do you have any clue about this?

cheers,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: insighttoolkit4
Source-Version: 4.9.0-2

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated insighttoolkit4 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, 21 Feb 2016 20:29:30 +
Source: insighttoolkit4
Binary: libinsighttoolkit4.9 libinsighttoolkit4-dev libinsighttoolkit4-dbg 
insighttoolkit4-examples insighttoolkit4-python
Architecture: source
Version: 4.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 insighttoolkit4-examples - Image processing toolkit for registration and 
segmentation - exam
 insighttoolkit4-python - Image processing toolkit for registration and 
segmentation - Pyth
 libinsighttoolkit4-dbg - Debugging information for the Insight Toolkit
 libinsighttoolkit4-dev - Image processing toolkit for registration and 
segmentation - deve
 libinsighttoolkit4.9 - Image processing toolkit for registration and 
segmentation - runt
Closes: 814591
Changes:
 insighttoolkit4 (4.9.0-2) unstable; urgency=medium
 .
   * d/p: add patch atomic_load.patch to make atomic Load
 operation truly atomic
   * d/p: add patch 

Bug#815494: zeromq3: FTBFS, with test suite errors

[Aaron M. Ucko]

Source: zeromq3
Version: 4.0.5+dfsg-3+b1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of zeromq3 failed for many architectures with test suite
errors, as detailed at

https://buildd.debian.org/status/logs.php?pkg=zeromq3=4.1.4-3

The kFreeBSD failures stem from a compilation error, which I'll report
separately.

Could you please take a look?

Thanks!

Bug#785924: [Freewx-maint] Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

[Sebastian Dröge]

On Mo, 2016-02-22 at 00:49 +1300, Olly Betts wrote:
> 
> Sebastian Dröge  wrote:
> > How can I test the wxwidgets GStreamer integration?
> You need to test via an application which uses it - something which
> depends on the wx or wxpython media package.  I think I've used
> whyteboard for this before.
> Thanks for looking at this.

Ok, it all seems to work. I've uploaded this to DELAYED/1, just let me
know if you want to do the upload yourself instead :)

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

Bug#814809: [pkg-php-pear] Bug#814809: Moving forward with the PHP 7.0 transition [Was: phing depends on php5-xdebug, which is not available anymore]

[Mathieu Parent]

Hello everybody,

[...]
> [ pkg-php-tools ]
>
> About the “root” issue, Mathieu, what are the current blockers holding
> the still current “pkg-php-tools package is still WIP”? [0] Is there
> anything we can help with in order to start making our PHP classes ready
> for the ongoing transition?

There is no blocker. I'll upload it soon.


> Among the things I was wondering that might need handling in order to
> make this transition possible without having to deal manually with every
> version of every (build-)dependency, recommendation, etc. of every
> package:
[...]

No idea, but we're already in a broken state, we need to go ahead now.

Regards
-- 
Mathieu

Bug#800096: FTBFS node-raw-body

[Thorsten Alteholz]

The linked logfile does not look that bad, at least it does not contain 
the error from the report!?


So this bug could be closed, right?

  Thorsten

Processed: severity of 788108 is serious, tagging 788108

[Debian Bug Tracking System]

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

> severity 788108 serious
Bug #788108 [src:qtlocation-opensource-src] qtlocation-opensource-src: Please 
switch to geoclue 2
Severity set to 'serious' from 'important'
> tags 788108 + sid stretch
Bug #788108 [src:qtlocation-opensource-src] qtlocation-opensource-src: Please 
switch to geoclue 2
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Processed: found 768724 in 11.88-1

[Debian Bug Tracking System]

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

> # still not fixed in sid
> found 768724 11.88-1
Bug #768724 {Done: sa...@debian.org (Davide G. M. Salvetti)} [src:auctex] 
auctex: FTBFS: build-dependency not installable: emacs23
Marked as found in versions auctex/11.88-1 and reopened.
> thanks
Stopping processing here.

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

Bug#814445: marked as done (Non-Free file: src/stdlib/SDL_qsort.c)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 19:40:02 +
with message-id 
and subject line Bug#814445: fixed in libsdl1.2 1.2.15+dfsg1-2
has caused the Debian Bug report #814445,
regarding Non-Free file: src/stdlib/SDL_qsort.c
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.)


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

Package: libsdl2
Version: 2.0.2+dfsg1-6
Severity: serious

The file 'src/stdlib/SDL_qsort.c' in SDL2 seems to disallow
modification.

The Debian copyright file simply mentions the license as:

  You may use it in anything you like; you may make money
  out of it; you may distribute it in object form or as
  part of an executable without including source code;
  you don't have to credit me. (But it would be nice if
  you did.)'.

What it does not mention is the text before that:

  * This code may be reproduced freely provided
  *   - this file is retained unaltered apart from minor
  * changes for portability and efficiency
  *   - no changes are made to this comment
  *   - any changes that *are* made are clearly flagged
  *   - the _ID string below is altered by inserting, after
  * the date, the string " altered" followed at your option
  * by other material. (Exceptions: you may change the name
  * of the exported routine without changing the ID string.
  * You may change the values of the macros TRUNC_* and
  * PIVOT_THRESHOLD without changing the ID string, provided
  * they remain constants with TRUNC_nonaligned, TRUNC_aligned
  * and TRUNC_words/WORD_BYTES between 8 and 24, and
  *   PIVOT_THRESHOLD between 32 and 200.)'.

Although the file states 'You may use it in anything you like', it
either contradicts itself, or is simply talking about using the
unmodified file in any program you like. The part before that clearly
says that the file cannot be 'reproduced freely' unless '[the] file is
retained unaltered apart from minor changes for portability and
efficiency'.
--- End Message ---
--- Begin Message ---
Source: libsdl1.2
Source-Version: 1.2.15+dfsg1-2

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

Debian distribution maintenance software
pp.
Manuel A. Fernandez Montecelo  (supplier of updated libsdl1.2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Feb 2016 17:46:19 +
Source: libsdl1.2
Binary: libsdl1.2debian libsdl1.2-dev libsdl1.2-dbg
Architecture: source amd64
Version: 1.2.15+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Manuel A. Fernandez Montecelo 
Description:
 libsdl1.2-dbg - Simple DirectMedia Layer debug files
 libsdl1.2-dev - Simple DirectMedia Layer development files
 libsdl1.2debian - Simple DirectMedia Layer
Closes: 814445
Changes:
 libsdl1.2 (1.2.15+dfsg1-2) unstable; urgency=medium
 .
   * d/control: remove "Multi-Arch: no" from -dev package, despite what
 lintian says there's an error processing the field (#768353) and the
 package got rejected
 .
 libsdl1.2 (1.2.15+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
 - Repack without SDL_qsort.c due to licence problem
   * Use newer relicenced version for SDL_qsort.c (Closes: #814445)
 Thanks the anonymous reporter, Ben Hutchings for looking into it and
 get in contact with the original author, the original author Gareth
 McCaughan for prompt relicencing.
 - d/patches/replace-relicenced-SDL_qsort.patch
   * Bump Policy Standards-Version to 3.9.7 (no changes needed)
   * Set -dev package as "Multi-Arch: no" (quells lintian error:
 old-style-config-script-multiarch-path)
   * d/watch: Add dfsg and pgpsig mangling
   * d/upstream/signing-key.asc: Import upstream gpg key for uscan to
 verify the orig tarball
Checksums-Sha1:
 1a6678604e8f9081033f2bf5c2bfb44d66aa367b 2451 

Bug#813421: marked as done (dbconfig-common: defaults for MariaDB are wrong: debian-sys-maint isn't anymore)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 19:38:39 +
with message-id 
and subject line Bug#813421: fixed in dbconfig-common 2.0.3
has caused the Debian Bug report #813421,
regarding dbconfig-common: defaults for MariaDB are wrong: debian-sys-maint 
isn't anymore
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.)


-- 
813421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbconfig-common
Version: 2.0.1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

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


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWr7INAAoJEJxcmesFvXUKRewH/RSmOEc9pPMw5cQNioHmdlAU
KOHMP9qZSbEJVe5fMjEoH2mKtqmzEsdbnA9UVhafn9bbuVBuEIWNNBcF8/8O0Jn+
hYKl6qQABtOtuLqmfepAhoRz8WTmb4Ssrk+Jjoven+e/haJFHTneprItp6qPIses
KdJb8J71D3BiaRzfnE4Bo5ckwarYT62qYztD/F+TVB6fJGxwzAo+7VChr1bDfd0o
nin5cnfsHEmtGpuCKl4rCJbA0uZcYEqyk1/u8zrsYR37/5uu3rGKq0MyPJANAP3f
hC6wSDME7XltLjMOKKbjOShjd/v7d0oICJrxkeXt8/9W9WiY0yv9uUgTmpmC06Y=
=lknW
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: dbconfig-common
Source-Version: 2.0.3

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated dbconfig-common 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, 21 Feb 2016 19:39:33 +0100
Source: dbconfig-common
Binary: dbconfig-common dbconfig-mysql dbconfig-pgsql dbconfig-sqlite 
dbconfig-sqlite3 dbconfig-no-thanks
Architecture: source
Version: 2.0.3
Distribution: unstable
Urgency: medium
Maintainer: Paul Gevers 
Changed-By: Paul Gevers 
Description:
 dbconfig-common - framework that helps packages to manage databases
 dbconfig-mysql - dbconfig-common MySQL/MariaDB support
 dbconfig-no-thanks - dbconfig-common bypass
 dbconfig-pgsql - dbconfig-common PostgreSQL support
 dbconfig-sqlite - dbconfig-common SQLite support
 dbconfig-sqlite3 - dbconfig-common SQLite3 support
Closes: 813040 813421 813923
Changes:
 dbconfig-common (2.0.3) unstable; urgency=medium
 .
   * Drop socket def and other duplication from mysql connection definition
   * Add mariadb-client to alternatives for dbconfig-mysql
   * Remove warnings for dbconfig- not being installed (Closes:
 #813923, #813040)
   * Revert MySQL default dbadmin for localhost as this isn't valid for
 MariaDB (Closes: #813421)
   * Obtain dbc_dbadmin from /etc/mysql/debian.cnf (only) on localhost
 setups
   * Update templates with default localhost (missed that in 1.8.55)
   * Fix Vcs-git URL
   * Bump standards to 3.9.7 (no changes)
Checksums-Sha1:
 b77ec6d01d462de008257d5143804aa1cc725bae 1699 dbconfig-common_2.0.3.dsc
 0fe3d8d8e64c29c2655c745d75d349296669b16d 210052 dbconfig-common_2.0.3.tar.xz
Checksums-Sha256:
 9464ec35462e6046e8a3133a411f9b2e848c0b0ec7478cfe6144e793adb32f7f 1699 
dbconfig-common_2.0.3.dsc
 85573b3e27902b44456671905dd1c10cebd984f2b8c12d62a3ea54f7d74e55f7 210052 
dbconfig-common_2.0.3.tar.xz
Files:
 4271cdb071469c55ecc14d1c3524d578 1699 admin optional dbconfig-common_2.0.3.dsc
 fa12b4199b23915883a2cb9c2c1ddb51 210052 admin optional 
dbconfig-common_2.0.3.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWyg5eAAoJEJxcmesFvXUKgmEIAIqyZUbLH3XB+V+xqMBKxIlC
sgNowKp5dpHJQiYPI1fjPGLnXGxMZiVFSoJdSrE5b3FeYpP74cQpH2lfmHiI6KZG
kE+8FA7dcZ0f5BDSX0aK9CIVFQ7rqBAtMbNJqLMZbjaQX4dNPL124mkTBa2dRp3n
B/3cX8bnSG5Ah3s06yIA+9NmK/QfBJLsu2lLMRP3schKzxkSUCmPc7KVEWOCEgiU
OcqbXria0f4km1054jiEoXG22nHo9FLbiNPf1wn7P6FJdDNnUMnWKiA1oLXrj3E5
YRyCMS/+V1Q0Olj63U4DByX5auRFQTj7jHa8hiwuUXTCzI+i9XXiXfcHgK91WKA=
=Wk3/
-END PGP 

Bug#815451: marked as done (initramfs-tools: Fails to install without busybox (Depends vs Recommends))

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 17:16:17 +
with message-id <1456074977.15241.39.ca...@decadent.org.uk>
and subject line Re: Bug#815451: initramfs-tools: Fails to install without 
busybox (Depends vs Recommends)
has caused the Debian Bug report #815451,
regarding initramfs-tools: Fails to install without busybox (Depends vs 
Recommends)
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.)


-- 
815451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.123
Severity: serious
Justification: Policy 7.2

Installation (processing triggers) fails if busybox is not installed:

Processing triggers for initramfs-tools (0.123) ...
update-initramfs: Generating /boot/initrd.img-4.3.0-1-amd64
E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but 
not installed
update-initramfs: failed for /boot/initrd.img-4.3.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1

This is ultimately because initramfs-tools-core "Recommends" busybox or 
busybox-static,
instead of "Depends". ("The Depends field should also be used if the postinst 
or prerm
scripts require the depended-on package to be unpacked or configured in order 
to run.")

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 4.7M Feb 21 11:52 /boot/initrd.img-4.3.0-1-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=4fd77b2d-aa89-422c-ad52-47c8020baf13 ro quiet

-- resume
RESUME=UUID=cce7de14-242f-494f-b3b2-0b39af56bbba
-- /proc/filesystems
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
ctr16384  3
ccm20480  3
appletalk  36864  0
ax25   57344  0
ipx28672  0
p8023  16384  1 ipx
p8022  16384  1 ipx
psnap  16384  2 ipx,appletalk
llc16384  2 p8022,psnap
cpufreq_conservative16384  0
cpufreq_powersave  16384  0
cpufreq_stats  16384  0
cpufreq_userspace  16384  0
pci_stub   16384  1
vboxpci24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   450560  3 vboxnetadp,vboxnetflt,vboxpci
loop   28672  0
firewire_sbp2  24576  0
intel_rapl 20480  0
iosf_mbi   16384  1 intel_rapl
hid_generic16384  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
usbhid 49152  0
coretemp   16384  0
hid   118784  2 hid_generic,usbhid
kvm_intel 163840  0
kvm   507904  1 kvm_intel
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
crc32c_intel   24576  0
joydev 20480  0
sha256_ssse3   28672  1
sha256_generic 24576  1 sha256_ssse3
arc4   16384  2
iwldvm135168  0
mac80211  626688  1 iwldvm
hmac   16384  1
drbg   24576  1
ansi_cprng 16384  0
firewire_ohci  40960  0
firewire_core  65536  2 firewire_ohci,firewire_sbp2
crc_itu_t  16384  1 firewire_core
sdhci_pci  24576  0
i915 1122304  2
sdhci  40960  1 sdhci_pci
aesni_intel   167936  6
mmc_core  126976  2 sdhci,sdhci_pci
aes_x86_64 20480  1 aesni_intel
lrw16384  1 aesni_intel
gf128mul   16384  1 lrw
glue_helper16384  1 aesni_intel
sr_mod 24576  0
ablk_helper16384  1 aesni_intel
cdrom  57344  1 sr_mod
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
evdev  20480  8
psmouse   126976  0
serio_raw  16384  0
ac 16384  0
ehci_pci   16384  0
ehci_hcd   77824  1 ehci_pci
drm_kms_helper131072  1 i915
iwlwifi   131072  1 iwldvm
cryptd 20480  2 aesni_intel,ablk_helper
sg 32768  0
pcspkr 16384  0
wmi20480  0
drm   348160  4 i915,drm_kms_helper
usbcore   233472  3 ehci_hcd,ehci_pci,usbhid
cfg80211  540672  3 iwlwifi,mac80211,iwldvm
mei_me 28672  0
thinkpad_acpi  81920  1
battery

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

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 17:00:31 +
with message-id 
and subject line Bug#811136: fixed in pg-repack 1.3.3-1
has caused the Debian Bug report #811136,
regarding Incompatible with PostgreSQL 9.5
to be marked as done.

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

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


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

pg-reorg fails to build in unstable:

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

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: pg-repack
Source-Version: 1.3.3-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pg-repack 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, 16 Feb 2016 11:50:58 +0100
Source: pg-repack
Binary: postgresql-9.5-repack
Architecture: source amd64
Version: 1.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Christoph Berg 
Description:
 postgresql-9.5-repack - reorganize tables in PostgreSQL databases with minimal 
locks
Closes: 811136
Changes:
 pg-repack (1.3.3-1) unstable; urgency=medium
 .
   * pg-reorg has been discontinued, switching to pg-repack.
 .
 pg_reorg development has been stopped, users should migrate to pg_repack.
 https://github.com/ossc-db/pg_reorg/issues/1
 .
   [ Martin Pitt ]
   * Build for PostgreSQL 9.5. (Closes: #811136)
   * Drop obsolete XS-Testsuite: field.
 .
   [ Christoph Berg ]
   * Point watchfile at github.
   * bin/Makefile: Make sure include/internal is loaded first.
   * Restrict to 9.3+.
Checksums-Sha1:
 a0aa7bfbdca0d5427e2f05cdfa037e759bfc6118 2017 pg-repack_1.3.3-1.dsc
 6cd4078a654299fe449e86cb5b6b30f717a9af40 86911 pg-repack_1.3.3.orig.tar.gz
 a8870c1bfc2a2fec59b9308a645d0bdbfc6b821b 3904 pg-repack_1.3.3-1.debian.tar.xz
 b33c02f988010647ad52f452107bd0b27f238a20 7616 
postgresql-9.5-repack-dbgsym_1.3.3-1_amd64.deb
 899ef1c621e3edaccfa6e1ff922b809ca173847a 62642 
postgresql-9.5-repack_1.3.3-1_amd64.deb
Checksums-Sha256:
 c3d06511d07166ab69f1f8e9ae55fcf213f84f02799974526a989324ef20cb50 2017 
pg-repack_1.3.3-1.dsc
 e4b6177362bbe8d022f87ae5d012badfbc0dcfdd634f1d508a5ba69e78a7d6b0 86911 
pg-repack_1.3.3.orig.tar.gz
 6f0789561f3e9feaaf0dfc4d1c38db586cd62227fe127fe952503a1750cd7bf4 3904 
pg-repack_1.3.3-1.debian.tar.xz
 71ae0e0274b895fff9b3631f314ac1078fe1fae5e57e4fdce5ed249fa8c0174c 7616 
postgresql-9.5-repack-dbgsym_1.3.3-1_amd64.deb
 fc7629da771a336306d600bab1cfc109b6d27f2f1fb868bc1aaebb3a2090fb96 62642 

Bug#815451: initramfs-tools: Fails to install without busybox (Depends vs Recommends)

[Christopher Hagar]

Package: initramfs-tools
Version: 0.123
Severity: serious
Justification: Policy 7.2

Installation (processing triggers) fails if busybox is not installed:

Processing triggers for initramfs-tools (0.123) ...
update-initramfs: Generating /boot/initrd.img-4.3.0-1-amd64
E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but 
not installed
update-initramfs: failed for /boot/initrd.img-4.3.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1

This is ultimately because initramfs-tools-core "Recommends" busybox or 
busybox-static,
instead of "Depends". ("The Depends field should also be used if the postinst 
or prerm
scripts require the depended-on package to be unpacked or configured in order 
to run.")

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 4.7M Feb 21 11:52 /boot/initrd.img-4.3.0-1-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=4fd77b2d-aa89-422c-ad52-47c8020baf13 ro quiet

-- resume
RESUME=UUID=cce7de14-242f-494f-b3b2-0b39af56bbba
-- /proc/filesystems
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
ctr16384  3
ccm20480  3
appletalk  36864  0
ax25   57344  0
ipx28672  0
p8023  16384  1 ipx
p8022  16384  1 ipx
psnap  16384  2 ipx,appletalk
llc16384  2 p8022,psnap
cpufreq_conservative16384  0
cpufreq_powersave  16384  0
cpufreq_stats  16384  0
cpufreq_userspace  16384  0
pci_stub   16384  1
vboxpci24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   450560  3 vboxnetadp,vboxnetflt,vboxpci
loop   28672  0
firewire_sbp2  24576  0
intel_rapl 20480  0
iosf_mbi   16384  1 intel_rapl
hid_generic16384  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
usbhid 49152  0
coretemp   16384  0
hid   118784  2 hid_generic,usbhid
kvm_intel 163840  0
kvm   507904  1 kvm_intel
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
crc32c_intel   24576  0
joydev 20480  0
sha256_ssse3   28672  1
sha256_generic 24576  1 sha256_ssse3
arc4   16384  2
iwldvm135168  0
mac80211  626688  1 iwldvm
hmac   16384  1
drbg   24576  1
ansi_cprng 16384  0
firewire_ohci  40960  0
firewire_core  65536  2 firewire_ohci,firewire_sbp2
crc_itu_t  16384  1 firewire_core
sdhci_pci  24576  0
i915 1122304  2
sdhci  40960  1 sdhci_pci
aesni_intel   167936  6
mmc_core  126976  2 sdhci,sdhci_pci
aes_x86_64 20480  1 aesni_intel
lrw16384  1 aesni_intel
gf128mul   16384  1 lrw
glue_helper16384  1 aesni_intel
sr_mod 24576  0
ablk_helper16384  1 aesni_intel
cdrom  57344  1 sr_mod
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
evdev  20480  8
psmouse   126976  0
serio_raw  16384  0
ac 16384  0
ehci_pci   16384  0
ehci_hcd   77824  1 ehci_pci
drm_kms_helper131072  1 i915
iwlwifi   131072  1 iwldvm
cryptd 20480  2 aesni_intel,ablk_helper
sg 32768  0
pcspkr 16384  0
wmi20480  0
drm   348160  4 i915,drm_kms_helper
usbcore   233472  3 ehci_hcd,ehci_pci,usbhid
cfg80211  540672  3 iwlwifi,mac80211,iwldvm
mei_me 28672  0
thinkpad_acpi  81920  1
battery16384  0
e1000e233472  0
mei94208  1 mei_me
button 16384  1 i915
nvram  16384  1 thinkpad_acpi
rfkill 24576  3 cfg80211,thinkpad_acpi
video  36864  2 i915,thinkpad_acpi
i2c_i801   20480  0
i2c_algo_bit   16384  1 i915
snd_hda_codec_conexant24576  1
snd_hda_codec_generic73728  1 snd_hda_codec_conexant
lpc_ich24576  0
mfd_core   16384  1 lpc_ich
shpchp 36864  0
ptp20480  1 e1000e
pps_core   20480  1 ptp
usb_common 16384  1 usbcore
snd_hda_intel  36864  0
snd_hda_codec 135168  3 
snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel
snd_hda_core   65536  4 
snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep  16384  1 snd_hda_codec
snd_pcm

Bug#813668: Possible patch

[Neil Williams]

I'm only putting this as a possible patch at this stage, I'm unsure
whether the change in the span class of the html_error is part of the
check being made or a result of external changes.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/

Description: Update matches for the template error strings
 mako (1.0.3+ds1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update template match data in test suite. (Closes: #813668)
Author: Neil Williams 
Bug-Debian: https://bugs.debian.org/813668

---

--- mako-1.0.3+ds1.orig/test/test_exceptions.py
+++ mako-1.0.3+ds1/test/test_exceptions.py
@@ -93,7 +93,7 @@ ${u'привет'}
 else:
 assert '3'\
 '${u'\
+'class="cp">${u'\
 ''\
 '}'.encode(
 sys.getdefaultencoding(),
@@ -236,7 +236,7 @@ ${foobar}
 'class="linenos">2'\
 '${'\
-'u'\
+'u'\
 ' + '\
 'foobar}'\
 '' in \


pgpV4LSJUwW09.pgp
Description: OpenPGP digital signature

Bug#808482: marked as done (deborphan: FTBFS: deborphan.h:39:14: error: expected identifier)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 16:21:15 +
with message-id 
and subject line Bug#808482: fixed in deborphan 1.7.28.8-0.3
has caused the Debian Bug report #808482,
regarding deborphan: FTBFS: deborphan.h:39:14: error: expected identifier
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.)


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

Dear Maintainer,

The package fails to build:

Making all in src
make[2]: Entering directory '/deborphan-1.7.28.8/src'
if gcc -DLOCALEDIR=\"/usr/share/locale\" 
-DKEEPER_FILE=\"/var/lib/deborphan/keep\" -DHAVE_CONFIG_H -I. -I. -I../include 
-I../include-O2 -g -MT deborphan.o -MD -MP -MF ".deps/deborphan.Tpo" -c -o 
deborphan.o deborphan.c; \
then mv -f ".deps/deborphan.Tpo" ".deps/deborphan.Po"; else rm -f 
".deps/deborphan.Tpo"; exit 1; fi
In file included from /usr/include/string.h:634:0,
 from deborphan.c:14:
../include/deborphan.h:39:14: error: expected identifier or ‘(’ before 
‘__extension__’
 extern char *strsep(char **, const char *);
  ^
../include/deborphan.h:39:14: error: expected identifier or ‘(’ before ‘)’ token
 extern char *strsep(char **, const char *);
  ^
In file included from deborphan.c:35:0:
../include/xalloc.h:13:21: warning: inline function ‘xstrdup’ declared but 
never defined
 extern inline char *xstrdup(const char *s);
 ^
../include/xalloc.h:12:21: warning: inline function ‘xrealloc’ declared but 
never defined
 extern inline void *xrealloc(void *ptr, size_t size);
 ^
../include/xalloc.h:11:21: warning: inline function ‘xmalloc’ declared but 
never defined
 extern inline void *xmalloc(size_t size);
 ^
../include/xalloc.h:10:21: warning: inline function ‘xcalloc’ declared but 
never defined
 extern inline void *xcalloc(size_t nmemb, size_t size);
 ^
In file included from deborphan.c:20:0:
../include/deborphan.h:176:28: warning: inline function ‘strhash’ declared but 
never defined
 extern inline unsigned int strhash(const char *line);
^
../include/deborphan.h:175:20: warning: inline function ‘strstripchr’ declared 
but never defined
 extern inline void strstripchr(char *s, int c);
^
Makefile:296: recipe for target 'deborphan.o' failed
make[2]: *** [deborphan.o] Error 1
make[2]: Leaving directory '/deborphan-1.7.28.8/src'
Makefile:282: recipe for target 'all-recursive' failed

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

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

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated deborphan 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, 21 Feb 2016 14:28:56 +
Source: deborphan
Binary: deborphan
Architecture: source
Version: 1.7.28.8-0.3
Distribution: unstable
Urgency: medium
Maintainer: deborphan devel team 
Changed-By: Julien Cristau 
Description:
 deborphan  - program that can find unused packages, e.g. libraries
Closes: 808482
Changes:
 deborphan (1.7.28.8-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with GCC-5 harder.  It makes no sense to declare functions
 "inline" and then not provide a definition for them.  Closes: #808482.
   * Remove duplicate strsep definition from 

Processed: Re: Fixed upstream

[Debian Bug Tracking System]

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

> found 684499 1:2.2.13-12~deb8u1
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Marked as found in versions dovecot/1:2.2.13-12~deb8u1.
> found 684499 1:2.2.18-2+b1
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Marked as found in versions dovecot/1:2.2.18-2.
> forwarded 684499 http://www.dovecot.org/list/dovecot/2016-February/103205.html
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Set Bug forwarded-to-address to 
'http://www.dovecot.org/list/dovecot/2016-February/103205.html'.
> severity 684499 serious
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Severity set to 'serious' from 'normal'
> tags 684499 +patch +fixed-upstream +confirmed
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Added tag(s) patch.
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Added tag(s) fixed-upstream.
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#809055: unbound: diff for NMU version 1.5.7-1.1

[Chris Boot]

Control: tags 809055 + patch
Control: tags 809055 + pending

Dear maintainer,

I've prepared an NMU for unbound (versioned as 1.5.7-1.1) and will
shortly upload it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

I have also pushed the changes to a Git repo on Alioth, keeping it
separate from yours in case you wish to do this differently:

https://anonscm.debian.org/git/users/bootc/unbound.git
git://anonscm.debian.org/users/bootc/unbound.git

Regards,
Chris

diff -Nru unbound-1.5.7/debian/changelog unbound-1.5.7/debian/changelog
--- unbound-1.5.7/debian/changelog  2015-12-12 20:08:27.0 +
+++ unbound-1.5.7/debian/changelog  2016-02-21 15:27:15.0 +
@@ -1,3 +1,13 @@
+unbound (1.5.7-1.1) unstable; urgency=medium
+
+  [ Chris Boot ]
+  * Non-maintainer upload.
+
+  [ Robert Edmonds ]
+  * [2372c14c] Makefile.in: Pass PYTHON_CPPFLAGS to swig instead of CPPFLAGS 
(Closes: #809055)
+
+ -- Chris Boot   Sun, 21 Feb 2016 15:27:06 +
+
 unbound (1.5.7-1) unstable; urgency=medium
 
   * [3cf7971b] debian/control: Vcs-Browser should point to cgit
diff -Nru unbound-1.5.7/debian/patches/debian-changes 
unbound-1.5.7/debian/patches/debian-changes
--- unbound-1.5.7/debian/patches/debian-changes 2015-12-12 20:11:09.0 
+
+++ unbound-1.5.7/debian/patches/debian-changes 2016-02-21 15:27:38.0 
+
@@ -5,13 +5,15 @@
  information below has been extracted from the changelog. Adjust it or drop
  it.
  .
- unbound (1.5.7-1) unstable; urgency=medium
+ unbound (1.5.7-1.1) unstable; urgency=medium
  .
-   * [3cf7971b] debian/control: Vcs-Browser should point to cgit
- (Closes: #804437)
-   * [66955294] Imported Upstream version 1.5.7
-Author: Robert Edmonds 
-Bug-Debian: https://bugs.debian.org/804437
+   [ Chris Boot ]
+   * Non-maintainer upload.
+ .
+   [ Robert Edmonds ]
+   * [2372c14c] Makefile.in: Pass PYTHON_CPPFLAGS to swig instead of CPPFLAGS 
(Closes: #809055)
+Author: Chris Boot 
+Bug-Debian: https://bugs.debian.org/809055
 
 ---
 The information above should follow the Patch Tagging Guidelines, please
@@ -26,6 +28,32 @@
 Reviewed-By: 
 Last-Update: 
 
+--- unbound-1.5.7.orig/Makefile.in
 unbound-1.5.7/Makefile.in
+@@ -54,6 +54,7 @@ LEX=@LEX@
+ STRIP=@STRIP@
+ CC=@CC@
+ CPPFLAGS=-I. @CPPFLAGS@
++PYTHON_CPPFLAGS=-I. @PYTHON_CPPFLAGS@
+ CFLAGS=@CFLAGS@
+ LDFLAGS=@LDFLAGS@
+ LIBS=@LIBS@
+@@ -389,13 +390,13 @@ pythonmod.lo pythonmod.o: $(srcdir)/pyth
+ 
+ pythonmod/interface.h:$(srcdir)/pythonmod/interface.i config.h
+   @-if test ! -d pythonmod; then $(INSTALL) -d pythonmod; fi
+-  $(SWIG) $(CPPFLAGS) -o $@ -python $(srcdir)/pythonmod/interface.i
++  $(SWIG) $(PYTHON_CPPFLAGS) -o $@ -python $(srcdir)/pythonmod/interface.i
+ 
+ libunbound_wrap.lo libunbound_wrap.o: libunbound/python/libunbound_wrap.c \
+   unbound.h
+ libunbound/python/libunbound_wrap.c:  
$(srcdir)/libunbound/python/libunbound.i unbound.h
+   @-if test ! -d libunbound/python; then $(INSTALL) -d libunbound/python; 
fi
+-  $(SWIG) -python -o $@ $(CPPFLAGS) 
-DPY_MAJOR_VERSION=$(PY_MAJOR_VERSION) $(srcdir)/libunbound/python/libunbound.i
++  $(SWIG) -python -o $@ $(PYTHON_CPPFLAGS) 
-DPY_MAJOR_VERSION=$(PY_MAJOR_VERSION) $(srcdir)/libunbound/python/libunbound.i
+ 
+ # Pyunbound python unbound wrapper
+ _unbound.la:  libunbound_wrap.lo libunbound.la
 --- unbound-1.5.7.orig/acx_python.m4
 +++ unbound-1.5.7/acx_python.m4
 @@ -43,7 +43,12 @@ $ac_distutils_result])

Processed: unbound: diff for NMU version 1.5.7-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 809055 + patch
Bug #809055 [unbound] unbound FTBFS, passes -Wdate-time to swig, which choke on 
it
Added tag(s) patch.
> tags 809055 + pending
Bug #809055 [unbound] unbound FTBFS, passes -Wdate-time to swig, which choke on 
it
Added tag(s) pending.

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

Bug#813775: Maintainer address bounces

[Ben Hutchings]

On Fri, 5 Feb 2016 00:00:25 -0800 Martin Michlmayr 
wrote:
> Package: linux-atm
> Version: 1:2.5.1-1.5
> Severity: serious
> 
> p...@mind.be no longer works.

I've now pointed this out to Peter on IRC.

Ben.
 
-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.


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

Bug#782332: Please re-test

[Neil Williams]

tag 782332 + unreproducible
thanks

I've just tried to reproduce this manually in a fresh Wheezy i386 VM,
installing libgpod-nogtk-dev and upgrading to jessie. The upgrade
proceeded normally.

root@wheezy:/home/neil# apt-get -y install libgpod-nogtk-dev

... 
root@wheezy:/home/neil# apt-get update
root@wheezy:/home/neil# apt-get upgrade
root@wheezy:/home/neil# apt-get dist-upgrade


root@wheezy:/home/neil# dpkg -l | cut -c -80| grep gpod
ii  libgpod-common0.8.3-1.1+b1  i386 com
ii  libgpod4:i386 0.8.3-1.1+b1  i386 lib
rc  libgpod4-nogtk:i386   0.8.2-7   i386 lib


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpqRfFcb3dX4.pgp
Description: OpenPGP digital signature

Processed: Please re-test

[Debian Bug Tracking System]

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

> tag 782332 + unreproducible
Bug #782332 [libgpod-nogtk-dev] libgpod-nogtk-dev: fails to upgrade from 
'wheezy': Depends: libgpod4-nogtk (= 0.8.3-1.1+b1) but it is not going to be 
installed
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#801781: marked as done (kate: Error in `kate': free(): invalid pointer)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 15:00:04 +
with message-id <56c9d0f4.1080...@debian.org>
and subject line Re: Bug#801781: Possibly fixed.
has caused the Debian Bug report #801781,
regarding kate: Error in `kate': free(): invalid pointer
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.)


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

Dear Maintainer,
after the last round of kde updates, kate krashes all the time

> *** Error in `kate': free(): invalid pointer: 0x7fbd0e50 ***

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

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

Versions of packages kate depends on:
ii  kate5-data   4:15.08.1-1
ii  ktexteditor-katepart 5.15.0-1
ii  libc62.19-22
ii  libgit2-23   0.23.1-1
ii  libkf5activities55.15.0-1
ii  libkf5bookmarks5 5.15.0-1
ii  libkf5completion55.15.0-1
ii  libkf5configcore55.15.0-1
ii  libkf5configgui5 5.15.0-1
ii  libkf5configwidgets5 5.15.0-1
ii  libkf5coreaddons55.15.0-1
ii  libkf5dbusaddons55.15.0-1
ii  libkf5guiaddons5 5.15.0-1
ii  libkf5i18n5  5.15.0-1
ii  libkf5iconthemes55.15.0-1
ii  libkf5itemmodels55.15.0-1
ii  libkf5jobwidgets55.15.0-1
ii  libkf5kiocore5   5.15.0-1
ii  libkf5kiofilewidgets55.15.0-1
ii  libkf5kiowidgets55.15.0-1
ii  libkf5newstuff5  5.15.0-1
ii  libkf5notifications5 5.15.0-1
ii  libkf5parts5 5.15.0-1
ii  libkf5plasma55.15.0-1
ii  libkf5service5   5.15.0+-1
ii  libkf5texteditor55.15.0-1
ii  libkf5textwidgets5   5.15.0-1
ii  libkf5threadweaver5  5.15.0-1
ii  libkf5wallet-bin 5.15.0-1
ii  libkf5wallet55.15.0-1
ii  libkf5widgetsaddons5 5.15.0-1
ii  libkf5windowsystem5  5.15.0-1
ii  libkf5xmlgui55.15.0-1
ii  libqt5core5a 5.4.2+dfsg-9
ii  libqt5dbus5  5.4.2+dfsg-9
ii  libqt5gui5   5.4.2+dfsg-9
ii  libqt5sql5   5.4.2+dfsg-9
ii  libqt5widgets5   5.4.2+dfsg-9
ii  libqt5xml5   5.4.2+dfsg-9
ii  libstdc++6   5.2.1-22
ii  plasma-framework 5.15.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.15.0-1
ii  qml-module-qtquick-layouts   5.4.2-2+b1
ii  qml-module-qtquick2  5.4.2-6

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell 0.60.7~20110707-3
pn  khelpcenter
ii  konsole-kpart  4:15.08.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:15.08.3-1


On 20/02/16 23:05, Salvo Tomaselli wrote:
> It works now. Sorry I had forgotten about this.
>
> 2016-02-20 13:00 GMT+01:00 Andy Simpkins :
>> Hi Salvo,
>>
>> I am looking back though open bugs at the moment and see that the mail
>> traffic for the bug you reported stopped back at the end of October,
>> with people suggesting that this has now gone away.
>>
>> Have you seen this?
>>
>> Have recent updates fixed the problem for you?
>>
>> If so can you please respond and we can close off the bug.  If not can
>> you just let us know that you are still seeing the problem and what
>> versions you are currently running.
>>
>> Many thanks
>>
>> /Andy
>>
>>




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#815436: afnix: FTBFS nearly everywhere

[Andreas Beckmann]

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

Hi,

the last upload of afnix FTBFS on nearly all platforms:

https://buildd.debian.org/status/package.php?p=afnix=unstable

mostly due to

  error: comparison between signed and unsigned integer expressions 
[-Werror=sign-compare]


Andreas

Bug#815133: marked as done (upgrading from gitlab (<< 8.4.3+dfsg-9) to to later versions requires purge and reinstall)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 20:18:33 +0530
with message-id <56c9ce41.3060...@autistici.org>
and subject line Re: gitlab installation fails with LoadError: cannot load such 
file -- /usr/share/gitlab/config/application
has caused the Debian Bug report #815133,
regarding upgrading from gitlab (<< 8.4.3+dfsg-9) to to later versions requires 
purge and reinstall
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.)


-- 
815133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.4.3+dfsg-9
Severity: grave
Justification: renders package unusable

Hi,

I just tried to upgrade my gitlab installation from 8.4.3+dfsg-8 to
8.4.3+dfsg-9 and this happened:


Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
Running final rake tasks...
Initializing database...
gitlab_production database is not empty, skipping gitlab setup
Precompiling assets...
rake aborted!
LoadError: cannot load such file -- /usr/share/gitlab/config/application
/usr/share/gitlab/Rakefile:5:in `require'
/usr/share/gitlab/Rakefile:5:in `'
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit 
status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)


Thus, the package is uninstallable.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
On Sun, 21 Feb 2016 14:06:18 +0100 Johannes Schauer 
wrote:
> I already told you in bug #814714, but you again forgot to CC me so I only am
> reading this now that I manually checked this bug after having read your reply
> to the thread on debian-devel. Thus let me repeat it here:
> 
>  | Notice, that the Debian bug tracker does *not* automatically send replies 
> to
>  | bugs to the submitter (or participants) of the bug. One has to manually
>  | subscribe to the bug to receive updates. So if you want to reach the
>  | submitter of a bug, then you either have to put their email in the CC
>  | explicitly or add nnn-submit...@bugs.debian.org to the CC where nnn is the
>  | current bug number.  The bts will then forward your email to the actual
>  | submitter. You can not rely on the submitter of a bug having subscribed to
>  | it.

Sorry, I missed this comment in #814714.

> Since by now you sent a few more emails, I assume that you no longer need my
> answer to your question above?
> 

Rahul was able to reproduce it and we confirmed these steps.

> Just to make sure I backup all the important stuff, let me summarize:
> 
>  - /usr/share/gitlab/public/uploads/ is now /var/lib/gitlab/public/uploads
>  - /usr/share/gitlab/.ssh/authorized_keys is now ??

home directory of gitlab user is now changed from /usr/share/gitlab to
/var/lib/gitlab, so /usr/share/gitlab/.ssh/authorized_keys is now
/var/lib/gitlab/.ssh/authorized_keys

> Anything else that I don't want to loose from /usr/share/gitlab before 
> purging?

Take a backup of /usr/share/gitlab to be sure.

> I also updated the title of this bug so that other users know to look at this
> bug before they try to upgrade to a version before 8.4.3+dfsg-9.

> Will you implement facilities for a smooth transition in the future?

Well, official support for updates are provided only for stable to next
stable. It will not be viable to support updates between unstable versions.

> Otherwise, I'd keep this bug open until gitlab is part of the next
> stable release at least.

I don't think this should block gitlab migration to testing. If someone
is choosing to install a package from unstable, they know what level of
support to expect.

I'm closing this bug now.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#815171: diffoscope: build time tests fail on armhf

[Jérémy Bobbio]

Control: retitle -1 diffoscope: tests for directory are brittle
Control: severity -1 normal

Holger Levsen:
> diffoscope fails to build from source in unstable/armhf but has 
> successfully built in the past: […]
> […]
> tests/comparators/test_directory.py:53: AssertionError
> […]
> tests/comparators/test_directory.py:59: IndexError

Feel free to just retry. The test suite for the directory comparator is
brittle and tend to break once in a while for timing reasons.

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


signature.asc
Description: Digital signature

Processed: Re: Bug#815171: diffoscope: build time tests fail on armhf

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 diffoscope: tests for directory are brittle
Bug #815171 [src:diffoscope] diffoscope: build time tests fail on armhf
Changed Bug title to 'diffoscope: tests for directory are brittle' from 
'diffoscope: build time tests fail on armhf'
> severity -1 normal
Bug #815171 [src:diffoscope] diffoscope: tests for directory are brittle
Severity set to 'normal' from 'serious'

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

Processed: deborphan: diff for NMU version 1.7.28.8-0.3

[Debian Bug Tracking System]

Processing control commands:

> tags 808482 + patch
Bug #808482 [src:deborphan] deborphan: FTBFS: deborphan.h:39:14: error: 
expected identifier
Added tag(s) patch.
> tags 808482 + pending
Bug #808482 [src:deborphan] deborphan: FTBFS: deborphan.h:39:14: error: 
expected identifier
Added tag(s) pending.

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

Bug#808482: deborphan: diff for NMU version 1.7.28.8-0.3

[Julien Cristau]

Control: tags 808482 + patch
Control: tags 808482 + pending

Dear maintainer,

I've prepared an NMU for deborphan (versioned as 1.7.28.8-0.3) and
am about to upload it.  You'll find the NMU diff attached (and in dgit,
if I can get it to work).

Cheers,
Julien
diff -Nru deborphan-1.7.28.8/debian/changelog deborphan-1.7.28.8/debian/changelog
--- deborphan-1.7.28.8/debian/changelog	2015-07-18 17:18:59.0 +0100
+++ deborphan-1.7.28.8/debian/changelog	2016-02-21 14:29:06.0 +
@@ -1,3 +1,12 @@
+deborphan (1.7.28.8-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC-5 harder.  It makes no sense to declare functions
+"inline" and then not provide a definition for them.  Closes: #808482.
+  * Remove duplicate strsep definition from deborphan.h.
+
+ -- Julien Cristau   Sun, 21 Feb 2016 14:28:56 +
+
 deborphan (1.7.28.8-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru deborphan-1.7.28.8/include/deborphan.h deborphan-1.7.28.8/include/deborphan.h
--- deborphan-1.7.28.8/include/deborphan.h	2015-07-18 17:18:22.0 +0100
+++ deborphan-1.7.28.8/include/deborphan.h	2016-02-21 14:24:09.0 +
@@ -30,15 +30,6 @@
 #  define KEEPER_FILE "/var/lib/deborphan/keep"
 #endif
 
-/* strsep, ftruncate, and fileno, are the only remaining functions that
- * are not ANSI-compliant, afaik. These #ifdef's will help compilation
- * with -ansi -pedantic -Wall, but not linking. ftruncate, and fileno
- * are not needed anymore and these #ifdefs broke splint, thus removed.
- */
-#ifndef _BSD_SOURCE
-extern char *strsep(char **, const char *);
-#endif
-
 #ifndef HAVE_ERRNO_H
 #  define errno 0
 #endif
@@ -172,8 +163,8 @@
 int string_to_priority(const char *priority);
 const char *priority_to_string(int priority);
 char *sstrsep(char **str, int c);
-extern inline void strstripchr(char *s, int c);
-extern inline unsigned int strhash(const char *line);
+void strstripchr(char *s, int c);
+unsigned int strhash(const char *line);
 
 /* keep.c */
 dep *readkeep(const char *kfile);
diff -Nru deborphan-1.7.28.8/include/xalloc.h deborphan-1.7.28.8/include/xalloc.h
--- deborphan-1.7.28.8/include/xalloc.h	2015-07-18 17:18:22.0 +0100
+++ deborphan-1.7.28.8/include/xalloc.h	2016-02-21 14:10:24.0 +
@@ -7,7 +7,7 @@
Distributed under the terms of the Artistic License.
 */
 
-extern inline void *xcalloc(size_t nmemb, size_t size);
-extern inline void *xmalloc(size_t size);
-extern inline void *xrealloc(void *ptr, size_t size);
-extern inline char *xstrdup(const char *s);
+void *xcalloc(size_t nmemb, size_t size);
+void *xmalloc(size_t size);
+void *xrealloc(void *ptr, size_t size);
+char *xstrdup(const char *s);
diff -Nru deborphan-1.7.28.8/src/string.c deborphan-1.7.28.8/src/string.c
--- deborphan-1.7.28.8/src/string.c	2012-06-30 19:47:50.0 +0100
+++ deborphan-1.7.28.8/src/string.c	2016-02-21 14:10:11.0 +
@@ -13,7 +13,7 @@
 
 /* Simple function to hash a string to an unsigned int. 
 */
-inline unsigned int
+unsigned int
 strhash(const char *line)
 {
 unsigned int r = 0;
@@ -30,7 +30,7 @@
 /* This function removes all occurences of the character 'c' from the
string 's'.
 */
-inline void
+void
 strstripchr(char *s, int c)
 {
 register char *t;
diff -Nru deborphan-1.7.28.8/src/xalloc.c deborphan-1.7.28.8/src/xalloc.c
--- deborphan-1.7.28.8/src/xalloc.c	2012-06-30 19:47:50.0 +0100
+++ deborphan-1.7.28.8/src/xalloc.c	2016-02-21 14:10:54.0 +
@@ -35,7 +35,7 @@
 #   define EXIT_FAILURE 1
 #endif /* STDC_HEADERS */
 
-inline void *
+void *
 xrealloc(void *ptr, size_t size)
 {
 void *t;
@@ -44,7 +44,7 @@
 return t;
 }
 
-inline void *
+void *
 xcalloc(size_t nmemb, size_t size)
 {
 void *t;
@@ -55,7 +55,7 @@
 return t;
 }
 
-inline void *
+void *
 xmalloc(size_t size)
 {
 void *t;
@@ -66,7 +66,7 @@
 return t;
 }
 
-inline char *
+char *
 xstrdup(const char *s)
 {
 char *t;


signature.asc
Description: PGP signature

Processed: tagging 765380

[Debian Bug Tracking System]

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

> tags 765380 - jessie
Bug #765380 [src:gcc-4.8] gcc-4.8: do not ship with Jessie+1
Removed tag(s) jessie.
> thanks
Stopping processing here.

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

Bug#814722: xserver-xorg-video-intel: blank screen with cursor when trying to open a second screen

[Eugene V. Lyubimkin]

Package: xserver-xorg-video-intel
Version: 2.99.917+git20160218-1
Followup-For: Bug #814722

Dear Maintainer,

I am not sure this is the same bug, but I get similar symptoms when
I try to open a second X screen by using 'kdmctl reserve'. When I do
this, the screen goes to blank black with a blinking cursor, and I
cannot switch to any X screen or VT consoles anymore, only reboot helps.

I verified this happens on my system with the current unstable and
testing versions of xserver-xorg/video-intel, and this doesn't happen
when I downgrade it back to jessie version.

I'd happy to provide an additional info.


-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)

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

Versions of packages xserver-xorg-video-intel depends on:
ii  libc6  2.21-8
ii  libdrm-intel1  2.4.65-3
ii  libdrm22.4.65-3
ii  libpciaccess0  0.13.2-3+b1
ii  libpixman-1-0  0.32.6-3
ii  libudev1   215-12
ii  libx11-6   2:1.6.3-1
ii  libx11-xcb12:1.6.3-1
ii  libxcb-dri2-0  1.10-3+b1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.10-3+b1
ii  libxv1 2:1.0.10-1+b1
ii  libxvmc1   2:1.0.8-2+b1
ii  xserver-xorg-core [xorg-video-abi-18]  2:1.16.4-1

xserver-xorg-video-intel recommends no packages.

xserver-xorg-video-intel suggests no packages.

-- no debconf information

Bug#815377: mariadb-10.0: newly split out plugin packages need Breaks+Replaces: mariadb-server-10.0

[Andreas Beckmann]

On 2016-02-21 14:09, Otto Kekäläinen wrote:
> PS. Where was the log? I don't see any jessie2sid option at
> https://piuparts.debian.org/jessie2stretch/maintainer/p/pkg-mysql-ma...@lists.alioth.debian.org.html

That's something I run locally :-)
And it's not a traditional piuparts test, but one that tests specific
package combinations for file conflicts.


Andreas

Bug#808874: debian-installer: FTBFS on i386: 586 vs. 686

[Adam D. Barratt]

On Fri, 2015-12-25 at 18:55 +0100, Cyril Brulebois wrote:
> Ben Hutchings  (2015-12-24):
> > On Thu, 2015-12-24 at 03:30 +0100, Cyril Brulebois wrote:
> > > Ben Hutchings  (2015-12-24):
> > > > I already updated base-installer for this, and I think the only other
> > > > change needed was in build/config/i386.cfg.  I've pushed a change to
> > > > that.
> > > 
> > > Checking my notes, it appears the following bits were involved last time:
> > > base-installer, debian-installer, debian-cd, installation guide.
> > > 
> > > The first two seem covered now, thanks.
> > > 
> > > Adding debian-cd@ for the third (sorry, didn't do any research for this
> > > one).
> > 
> > I opened bug #808958 with a patch.
> > 
> > > The last one seems to have been dealt with in r69410, r69411, r69412
> > > last time; something similar might do the trick this time.
> > 
> > Updated in r70113, r70114.
> 
> Perfect, thanks!

It looks like the 20160101 upload included relevant changes, and built
happily on i386. Is there anything remaining to fix?

Regards,

Adam

Bug#815125: linux-image-4.4.0-1-amd64 fails to load initrd - no booting

[Norbert Preining]

Hi Ben,

On Sun, 21 Feb 2016, Ben Hutchings wrote:
> Norbert, I didn't get confirmation from you whether the problem on your
> system is fixed by the new patches I found.  If it isn't, please
> *unmerge* this bug report before reopening it.

Sorry, this is my work computer and I didn't have access to it today
after I sent the one email.

I will try tomorrow whether it fixes the problem.

Thanks for your work on that

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#815125: linux-image-4.4.0-1-amd64 fails to load initrd - no booting

[Ben Hutchings]

Norbert, I didn't get confirmation from you whether the problem on your
system is fixed by the new patches I found.  If it isn't, please
*unmerge* this bug report before reopening it.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.

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

Processed: affects 660206, affects 663948

[Debian Bug Tracking System]

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

> # squeeze bugs
> affects 660206 - release.debian.org
Bug #660206 [mysql-server-5.1] mysql-server: client cannot authenticate
Removed indication that 660206 affects release.debian.org
> affects 663948 - release.debian.org
Bug #663948 [libc6] Wrong resolver behavior (ipv6) after squeeze point release
Removed indication that 663948 affects release.debian.org
> thanks
Stopping processing here.

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

Bug#815126: marked as done (linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...')

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 13:23:59 +
with message-id 
and subject line Bug#815125: fixed in linux 4.4.2-3
has caused the Debian Bug report #815125,
regarding linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...'
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.)


-- 
815125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.4.2-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I upgraded from linux-image-4.3.0-1-amd64 (version 4.3.5-1) to 
linux-image-4.4.0-1-amd64.
On rebooting the system I am presented with grub, and then start booting into 
Linux.
I only get to see 2 lines with the cursor below them on the lefthand side.

Loading Linux 4.4.0-1 ...
Loading initial ramdisk ...
_

The system freezes at this point and is unresponsive.
I have to hold my power button down for approx 10s to power off the laptop.
Booting back into linux-4.3.0-1-amd64 works fine.

I attempted to reinstall the kernel (from a different location/network) using:

aptitude reinstall linux-image-4.4.0-1-amd64

This made no difference.
Choosing to boot the same kernel using the (recovery mode) grub option results 
in the same problem.

Because the boot hangs so early I can't provide any useful diagnostic 
information.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20BS0038AU
product_version: ThinkPad X1 Carbon 3rd
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N14ET33W (1.11 )
board_vendor: LENOVO
board_name: 20BS0038AU
board_version: SDK0E50510 WIN

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: Lenovo Broadwell-U Audio Controller [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller [17aa:2227]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: Lenovo Wildcat Point-LP MEI Controller [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) 
I218-LM [8086:15a2] (rev 03)
Subsystem: Lenovo Ethernet Connection (3) I218-LM [17aa:2227]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] 

Bug#815404: marked as done (linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 Carbon)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 13:23:59 +
with message-id 
and subject line Bug#815125: fixed in linux 4.4.2-3
has caused the Debian Bug report #815125,
regarding linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 Carbon
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.)


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

Dear Maintainer,

This morning saw a kernel upgrade from 4.3.0 to 4.4.0. This worked fine on 
Lenovo T500, Lenovo Z201, and
Dell Precision T5400, the machines now boot to 4.4.0, without problem. However 
on a Lenovo X1 Carbon, the
upgrade seem to go without a problem, but when a reboot is attempted, the 
machine hangs on the message:

loading initial ramdisk…

At this point the machine is "locked up" and an enforced power down is 
required. The machine
boots fine to 4.3.0, hence being able to send this bug report in from the 
machine itself.

I tried reinstalling the packages in case there was simply a problem with the 
upgrade process itself, but
whilst the installation seemed to go fine, the same behaviour occured on boot: 
not able to get past the
ramdisk message.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20BSCTO1WW
product_version: ThinkPad X1 Carbon 3rd
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N14ET25W (1.03 )
board_vendor: LENOVO
board_name: 20BSCTO1WW
board_version: SDK0E50512 STD

** Network interface configuration:

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: Lenovo Broadwell-U Audio Controller [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: Lenovo Wildcat Point-LP MEI Controller [17aa:2227]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) 
I218-LM [8086:15a2] (rev 03)
Subsystem: Lenovo Ethernet Connection (3) I218-LM [17aa:2227]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] (rev 03)
Subsystem: Lenovo Wildcat Point-LP High Definition Audio 

Bug#815173: marked as done (kernel-image-4.4.0-1-amd64 does not boot on my Thinkpad X240)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 13:23:59 +
with message-id 
and subject line Bug#815125: fixed in linux 4.4.2-3
has caused the Debian Bug report #815125,
regarding kernel-image-4.4.0-1-amd64 does not boot on my Thinkpad X240
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.)


-- 
815125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.4.0-1-amd64
Version: 4.4.2-1
Severity: serious

Hello,

This kernel does not boot on my Thinkpad X240.

grub loads the kernel and the initrd. Then die computer hangs. There is no 
additional output. I must switch the computer with the powerbutton.

linux-image-4.4.0-trunk-amd64 works fine.

Regards
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.4.2-3

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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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: Sun, 21 Feb 2016 13:11:18 +
Source: linux
Binary: linux-source-4.4 linux-support-4.4.0-1 linux-doc-4.4 linux-manual-4.4 
linux-libc-dev linux-headers-4.4.0-1-all linux-headers-4.4.0-1-all-alpha 
kernel-image-4.4.0-1-alpha-generic-di nic-modules-4.4.0-1-alpha-generic-di 
nic-wireless-modules-4.4.0-1-alpha-generic-di 
nic-shared-modules-4.4.0-1-alpha-generic-di 
serial-modules-4.4.0-1-alpha-generic-di 
usb-serial-modules-4.4.0-1-alpha-generic-di 
ppp-modules-4.4.0-1-alpha-generic-di pata-modules-4.4.0-1-alpha-generic-di 
cdrom-core-modules-4.4.0-1-alpha-generic-di 
scsi-core-modules-4.4.0-1-alpha-generic-di 
scsi-modules-4.4.0-1-alpha-generic-di loop-modules-4.4.0-1-alpha-generic-di 
btrfs-modules-4.4.0-1-alpha-generic-di ext4-modules-4.4.0-1-alpha-generic-di 
isofs-modules-4.4.0-1-alpha-generic-di jfs-modules-4.4.0-1-alpha-generic-di 
xfs-modules-4.4.0-1-alpha-generic-di fat-modules-4.4.0-1-alpha-generic-di 
md-modules-4.4.0-1-alpha-generic-di multipath-modules-4.4.0-1-alpha-generic-di 
usb-modules-4.4.0-1-alpha-generic-di
 usb-storage-modules-4.4.0-1-alpha-generic-di 
fb-modules-4.4.0-1-alpha-generic-di input-modules-4.4.0-1-alpha-generic-di 
event-modules-4.4.0-1-alpha-generic-di mouse-modules-4.4.0-1-alpha-generic-di 
nic-pcmcia-modules-4.4.0-1-alpha-generic-di 
pcmcia-modules-4.4.0-1-alpha-generic-di 
nic-usb-modules-4.4.0-1-alpha-generic-di sata-modules-4.4.0-1-alpha-generic-di 
core-modules-4.4.0-1-alpha-generic-di crc-modules-4.4.0-1-alpha-generic-di 
crypto-modules-4.4.0-1-alpha-generic-di 
crypto-dm-modules-4.4.0-1-alpha-generic-di ata-modules-4.4.0-1-alpha-generic-di 
nbd-modules-4.4.0-1-alpha-generic-di squashfs-modules-4.4.0-1-alpha-generic-di 
virtio-modules-4.4.0-1-alpha-generic-di zlib-modules-4.4.0-1-alpha-generic-di 
fuse-modules-4.4.0-1-alpha-generic-di srm-modules-4.4.0-1-alpha-generic-di 
linux-headers-4.4.0-1-common linux-image-4.4.0-1-alpha-generic 
linux-headers-4.4.0-1-alpha-generic linux-image-4.4.0-1-alpha-smp 
linux-headers-4.4.0-1-alpha-smp linux-headers-4.4.0-1-all-amd64
 kernel-image-4.4.0-1-amd64-di nic-modules-4.4.0-1-amd64-di 
nic-wireless-modules-4.4.0-1-amd64-di nic-shared-modules-4.4.0-1-amd64-di 
serial-modules-4.4.0-1-amd64-di usb-serial-modules-4.4.0-1-amd64-di 
ppp-modules-4.4.0-1-amd64-di pata-modules-4.4.0-1-amd64-di 
cdrom-core-modules-4.4.0-1-amd64-di firewire-core-modules-4.4.0-1-amd64-di 
scsi-core-modules-4.4.0-1-amd64-di scsi-modules-4.4.0-1-amd64-di 
loop-modules-4.4.0-1-amd64-di btrfs-modules-4.4.0-1-amd64-di 
ext4-modules-4.4.0-1-amd64-di isofs-modules-4.4.0-1-amd64-di 
jfs-modules-4.4.0-1-amd64-di ntfs-modules-4.4.0-1-amd64-di 
xfs-modules-4.4.0-1-amd64-di fat-modules-4.4.0-1-amd64-di 
md-modules-4.4.0-1-amd64-di multipath-modules-4.4.0-1-amd64-di 
usb-modules-4.4.0-1-amd64-di usb-storage-modules-4.4.0-1-amd64-di 
pcmcia-storage-modules-4.4.0-1-amd64-di 

Bug#814824: marked as done (SyntaxError: invalid syntax)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 13:24:17 +
with message-id 
and subject line Bug#814824: fixed in pytango 8.1.8-2
has caused the Debian Bug report #814824,
regarding SyntaxError: invalid syntax
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.)


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

Dear Maintainer,

Paramétrage de python3-pytango (8.1.8-1) ...
  File "/usr/lib/python3/dist-packages/PyTango/tango_gevent.py", line 56
raise result.error_string, None, result.tb
 ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/PyTango/tango_gevent.py", line 56
raise result.error_string, None, result.tb
 ^
SyntaxError: invalid syntax


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

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

Versions of packages python3-pytango depends on:
ii  ipython32.4.1-1
ii  libboost-python1.58.0   1.58.0+dfsg-5+b1
ii  libc6   2.21-7
ii  libgcc1 1:5.3.1-8
ii  libstdc++6  5.3.1-8
ii  libtango8v5 8.1.2c+dfsg-7
ii  python3 3.5.1-1
ii  python3-numpy [python3-numpy-abi9]  1:1.11.0~b3-1
pn  python3.5:any   

python3-pytango recommends no packages.

python3-pytango suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pytango
Source-Version: 8.1.8-2

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated pytango 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, 21 Feb 2016 14:03:38 +0100
Source: pytango
Binary: python-pytango python3-pytango python-pytango-doc
Architecture: source
Version: 8.1.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 python-pytango - API for the TANGO control system (Python 2)
 python-pytango-doc - API for the TANGO control system
 python3-pytango - API for the TANGO control system (Python 3)
Closes: 814824
Changes:
 pytango (8.1.8-2) unstable; urgency=medium
 .
   * debian/patches
 - 0001-Fix-syntax-error-in-python-3.patch (Closes: #814824)
Checksums-Sha1:
 d2279d1a2977b0bca448f36530e1e86a4ace279c 2285 pytango_8.1.8-2.dsc
 52e2de8e7f110d61271f564b31cc3c85597996bd 4644 pytango_8.1.8-2.debian.tar.xz
Checksums-Sha256:
 4da31f786d949dde9a292bdaf1c5983aaf0da6a10c61f40fc161fe8e3c05b9a6 2285 
pytango_8.1.8-2.dsc
 3b2b3026380a68f656b6f84919db964dec41343e99e341b607b6952a324c6ee7 4644 
pytango_8.1.8-2.debian.tar.xz
Files:
 74fe447cc4ef530e61c1e310f1716b7d 2285 science extra pytango_8.1.8-2.dsc
 97bebc1ddbefea2faf6b4c493e2f6bdf 4644 science extra 
pytango_8.1.8-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWybZlAAoJEFYykG9GluAVw9QQAJZ5JZm4GdcjCk1BFuwZZlpa
lduCr7nAQrrzL20nWlOCq3DBYO1fOFBZ9ZBIpwi+qRF5aaetPtr/3Q9HFr5lIk+k
iPT9DRNpV69WsCbl3ViwJpjx2o9TY4YPe6/ppep7t+f/mIEl6rwC9oRn/8vBIcem
8OxKP0wGmuKpuZUg/r6pMIhRzlJ+6w0gVDREXs1fEyoTqEUPeGyDMLDcBIjUF1Se
69MMz2bdJzIfpp+gUE0gGkarVWrvgjtwhteSQFAqBFqzVM+X+Vu4Ag79+d6XrutX
ujqsnP1Qs20+t8XgvCkqZvEKvAVfd6iaJxyxE9iUqNvCrtpHhXaXm1au5RUiiagm
vx/eWZsteZLMFwY6tBsxjARxznA6BtHEN0iIMBnxiERmHrG0Pb8UpUHDArwy+vHq
ugcsSm33x4KOH6gMk7eR7Y+bSev7gOEZlDLTZQTLkrMIZlw89T3bUOn2fb3eETrY

Bug#815377: [debian-mysql] Bug#815377: mariadb-10.0: newly split out plugin packages need Breaks+Replaces: mariadb-server-10.0

[Otto Kekäläinen]

Hello!

Thanks for keeping an eye on Piuparts and spotting this. We had
breaks+replaces only for old plugin packages and we completely
overlooked the need for breaks+replaces for the server package.

I have now fixed this in git and it will be included in next upload - soon.

http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=6c50a4521fb44b61fbb3ff6dae9cc21fa8d602d8

PS. Where was the log? I don't see any jessie2sid option at
https://piuparts.debian.org/jessie2stretch/maintainer/p/pkg-mysql-ma...@lists.alioth.debian.org.html



> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>
> >From the attached log (scroll to the bottom...):
>
>   Selecting previously unselected package mariadb-plugin-mroonga.
>   Preparing to unpack .../mariadb-plugin-mroonga_10.0.23-3_amd64.deb ...
>   Unpacking mariadb-plugin-mroonga (10.0.23-3) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/mariadb-plugin-mroonga_10.0.23-3_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/mysql/plugin/ha_mroonga.so', which is also 
> in package mariadb-server-10.0 10.0.22-0+deb8u1
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/var/cache/apt/archives/mariadb-plugin-mroonga_10.0.23-3_amd64.deb
>
> Similarily for mariadb-plugin-spider and mariadb-plugin-tokudb.

Bug#814276: Non-Free file: src/stdlib/SDL_qsort.c

[Ben Hutchings]

On Sun, 2016-02-21 at 11:37 +, Manuel A. Fernandez Montecelo wrote:
> Hi Ben,
> 
> 2016-02-21 03:09 Ben Hutchings:
> > I happen to know the original author, so I've mailed him requesting he
> > consider relicencing.
> 
> I suppose that you were looking into this as part of the BSP.

Yes.

> I notified upstream a few days ago, and they didn't want to be in
> possible breach of the license, so they changed the implementation for
> libsdl2:
> 
>   
> http://lists.alioth.debian.org/pipermail/pkg-sdl-maintainers/2016-February/002374.html
> 
> libsdl1.2 suffers from the same problem, but we can just repack the
> orig.tar and disable the use of this implementation (it's supposed to
> not be used by default, so an empty file would do, or otherwise the file
> from libsdl2 can be used).
> 
> So, in summary, I am going to upload fixes in the next few days.
> 
> 
> At this point I suspect that upstream is not going to go back (unless
> the implementation that they now use is problematic).  Maybe it's good
> if you could get this relicenced just in case, e.g. for the benefit of
> other distros.  What do you think?

It might be.

Gareth has now updated the licence text at


Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.


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

Bug#815133: gitlab installation fails with LoadError: cannot load such file -- /usr/share/gitlab/config/application

[Johannes Schauer]

Control: retitle -1 upgrading from gitlab (<< 8.4.3+dfsg-9) to to later 
versions requires purge and reinstall

Hi,

On Sat, 20 Feb 2016 21:34:50 +0530 Pirate Praveen  
wrote:
> I'm not able to reproduce it in a fresh install (after apt-get purge).
> 
> Can you check if config is a symlink to /etc/gitlab?
> 
> There are other symlinks too
> 
> config -> /etc/gitlab
> Gemfile.lock -> /var/lib/gitlab/Gemfile.lock
> log -> /var/log/gitlab
> public -> /var/lib/gitlab/public
> tmp -> /run/gitlab
> shared/cache -> /var/lib/gitlab/cache
> /usr/share/gitlab/.secret -> /var/lib/gitlab/.secret
> 
> Can you check if all symlinks are in order?

I already told you in bug #814714, but you again forgot to CC me so I only am
reading this now that I manually checked this bug after having read your reply
to the thread on debian-devel. Thus let me repeat it here:

 | Notice, that the Debian bug tracker does *not* automatically send replies to
 | bugs to the submitter (or participants) of the bug. One has to manually
 | subscribe to the bug to receive updates. So if you want to reach the
 | submitter of a bug, then you either have to put their email in the CC
 | explicitly or add nnn-submit...@bugs.debian.org to the CC where nnn is the
 | current bug number.  The bts will then forward your email to the actual
 | submitter. You can not rely on the submitter of a bug having subscribed to
 | it.

Since by now you sent a few more emails, I assume that you no longer need my
answer to your question above?

> On Sat, 20 Feb 2016 22:37:20 +0530 Pirate Praveen  
> wrote:
> > Hi Josch,
> > 
> > You'll have to do a fresh install as directory structure has changed 
> > significantly.
> > 
> > 1. apt-get purge gitlab (removes files, so new version can add symlinks)
> > 2. rm -rf /usr/share/gitlab (config, tmp, log were not empty).
> > 3. userdel -r gitlab (/var/lib/gitlab is new home or .gitconfig can't be 
> > created)
> > 4. apt-get install gitlab
> 
> You have to also remove /usr/share/gitlab-shell/.gitlab_shell_secret

Thanks, I'll do a full reinstall then.

Just to make sure I backup all the important stuff, let me summarize:

 - /usr/share/gitlab/public/uploads/ is now /var/lib/gitlab/public/uploads
 - /usr/share/gitlab/.ssh/authorized_keys is now ??

Anything else that I don't want to loose from /usr/share/gitlab before purging?

I also updated the title of this bug so that other users know to look at this
bug before they try to upgrade to a version before 8.4.3+dfsg-9.

Will you implement facilities for a smooth transition in the future?

Otherwise, I'd keep this bug open until gitlab is part of the next stable
release at least.

Thanks!

cheers, josch


signature.asc
Description: signature

Processed: Re: gitlab installation fails with LoadError: cannot load such file -- /usr/share/gitlab/config/application

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 upgrading from gitlab (<< 8.4.3+dfsg-9) to to later versions 
> requires purge and reinstall
Bug #815133 [gitlab] gitlab installation fails with LoadError: cannot load such 
file -- /usr/share/gitlab/config/application
Changed Bug title to 'upgrading from gitlab (<< 8.4.3+dfsg-9) to to later 
versions requires purge and reinstall' from 'gitlab installation fails with 
LoadError: cannot load such file -- /usr/share/gitlab/config/application'

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

Processed: unpatch

[Debian Bug Tracking System]

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

> tag 792177 - patch
Bug #792177 [libjson0-dev] libjson0-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Processed: found

[Debian Bug Tracking System]

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

> tag 792177 + sid stretch
Bug #792177 [libjson0-dev] libjson0-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#815398: marked as done (ros-ros-comm: FTBFS: dh_install: python-rosbag missing files: usr/lib/*/rosbag)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 13:57:54 +0100
with message-id <20160221125754.gc9...@vis.informatik.uni-osnabrueck.de>
and subject line closing
has caused the Debian Bug report #815398,
regarding ros-ros-comm: FTBFS: dh_install: python-rosbag missing files: 
usr/lib/*/rosbag
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.)


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

ros-ros-comm fails to build from source in unstable/amd64:

  [..]

  running build
  running build_py
  creating 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/lib.linux-x86_64-2.7
  creating 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/lib.linux-x86_64-2.7/rostopic
  copying src/rostopic/__init__.py -> 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/lib.linux-x86_64-2.7/rostopic
  running build_scripts
  creating 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/scripts-2.7
  copying and adjusting scripts/rostopic -> 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/scripts-2.7
  changing mode of 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/scripts-2.7/rostopic
 from 644 to 755
  running install
  running install_lib
  creating 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/lib/python2.7/dist-packages/rostopic
  copying 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/lib.linux-x86_64-2.7/rostopic/__init__.py
 -> 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/lib/python2.7/dist-packages/rostopic
  byte-compiling 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/lib/python2.7/dist-packages/rostopic/__init__.py
 to __init__.pyc
  running install_scripts
  copying 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build/tools/rostopic/scripts-2.7/rostopic
 -> 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/bin
  changing mode of 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/bin/rostopic
 to 755
  running install_egg_info
  Writing 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/lib/python2.7/dist-packages/rostopic-1.11.16.egg-info
  -- Installing: 
/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/debian/tmp/usr/lib/rostopic/rostopic
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160221091918.5hY6ViggBF/ros-ros-comm-1.11.16/build'
 dh_install -O--parallel -O--buildsystem=cmake -O--builddirectory=build
  dh_install: python-rosbag missing files: usr/lib/*/rosbag
  dh_install: topic-tools missing files: usr/lib/*/topic_tools
  dh_install: missing files, aborting
  debian/rules:7: recipe for target 'binary' failed
  make: *** [binary] Error 255

  [..]

The full build log is attached.


Regards,

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


ros-ros-comm.1.11.16-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
fixed 815398 1.11.16-4


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

Bug#815369: Fwd: gcc-5-doc: FTBFS in sid: ./gnat_rm.aux:1: TeX capacity exceeded, sorry [input stack size=5000].

[Norbert Preining]

Dear all

> > I just filed this bug (#815369) against gcc-5-doc, but maybe you want to

The patch
gnat-cross-references.diff
in gcc-5-doc is broken. The header says:
Description: Changed cross reference to versioned info pages.
 Created using perl, then manually checked for correctness.
 perl -i -pe 's/gnat_rm/\@value{fngnatrm}/g'
 perl -i -pe 's/gnat_ugn/\@value{fngnatugn}/g'
 perl -i -pe 's/gnat-style/\@value{fngnatstyle}/g'
but this also changes the
@setfilename 
setting, which is not supported, and in fact it seems it has never been
supported (looking back into the history of texinfo).

I don't know how these packages were built, but the change was introduced
in git commit da9d947d (btw, the git master is outdated - what is going 
on here??? git contains still as changelog:
gcc-5-doc (5.2.0-1) UNRELEASED; urgency=medium
and last commit from Sun Aug 9 16:28:21 2015 -0400.

As far as I am concerned, this is not a bug in texinfo.

Thanks

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

Processed: found

[Debian Bug Tracking System]

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

> found 792177 0.11-4
Bug #792177 [libjson0-dev] libjson0-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
Marked as found in versions json-c/0.11-4.
> thanks
Stopping processing here.

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

Bug#815369: [BUG] command line definitions not expanded

[Norbert Preining]

> >Did this ever work, and if so, which version of texinfo.tex and
> >texi2dvi?

Forget this - sorry for the noise - this was introduced recently
by Debian packaging.

Can be closed on the texinfo side.

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

Processed: retitle

[Debian Bug Tracking System]

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

> retitle 792177 libjson0-dev: causes creation of unowned 
> /usr/lib//libjson-c.so.2 -> libjson-c.so symlink
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
Changed Bug title to 'libjson0-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink' from 'libjson-c-dev: 
causes creation of unowned /usr/lib//libjson-c.so.2 -> libjson-c.so 
symlink'
> thanks
Stopping processing here.

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

Bug#792177: NMUs have delayed uploads

[Neil Williams]

Once the blocking bugs are fixed, libjson0-dev can be dropped which is
the correct fix for this bug - with corresponding changes to the postrm
to tidy up.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpYh8AKoJCr0.pgp
Description: OpenPGP digital signature

Bug#800409: marked as done (Synaptic not starting, false positive)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 12:40:21 +
with message-id <20160221124021.ga4...@betterave.cristau.org>
and subject line Re: Bug#800409: Synaptic not starting, false positive
has caused the Debian Bug report #800409,
regarding Synaptic not starting, false positive
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.)


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

Package: synaptic
Version: 0.81.4+b2
Severity: grave

Dear maintainer,

* What led to this situation?
A failed install of a Java package from Oracle.

* What exactly did you do?
Purged package completely and reinstalled after reboot, issue persists.

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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme 0.13-1
ii  libapt-inst1.7 1.0.10.2
ii  libapt-pkg4.16 1.0.10.2
ii  libatk1.0-0 2.16.0-2
ii  libc6 2.19-22
ii  libcairo-gobject2 1.14.2-2
ii  libcairo2 1.14.2-2
ii  libept1.4.16 1.0.14+b1
ii  libgcc1 1:5.2.1-17
ii  libgdk-pixbuf2.0-0 2.32.0-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgtk-3-0 3.16.6-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libstdc++6 5.2.1-17
ii  libvte-2.90-9 1:0.36.3-1
ii  libx11-6 2:1.6.3-1
ii  libxapian22v5 1.2.21-1.2
ii  libxext6 2:1.3.3-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-9
ii  libgtk2-perl   2:1.2496-3
ii  policykit-10.105-12
ii  rarian-compat  0.8.1-6

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.47
ii  deborphan1.7.28.8-0.2
pn  dwww 
ii  menu 2.1.47
pn  software-properties-gtk  
ii  tasksel  3.33

-- no debconf information

Purging and reinstalling did not help in this system, I had similar 
issue on another one and that fixed it.

Synaptic throws false positive on root password and will not start.
The root password is correct and these are the errors in terminal:

ckosloff@crosshair:~$ su
Password:
root@crosshair:/home/ckosloff# synaptic
No protocol specified

** (synaptic:3056): WARNING **: Could not open X display
No protocol specified
Unable to init server: Could not connect: Connection refused

(synaptic:3056): Gtk-WARNING **: cannot open display: :0
root@crosshair:/home/ckosloff# exit

The failed processes are synaptic-pkexec and pkexec.

Here is a snapshot: http://imgur.com/rlz0ga4

Please help.

*Carlos Kosloff*


--- End Message ---
--- Begin Message ---
On Mon, Sep 28, 2015 at 18:43:49 -0400, Carlos Kosloff wrote:

> Package: synaptic
> Version: 0.81.4+b2
> Severity: grave
> 
> Dear maintainer,
> 
> * What led to this situation?
> A failed install of a Java package from Oracle.
> 
> * What exactly did you do?
> Purged package completely and reinstalled after reboot, issue persists.
> 
[...]
> 
> Purging and reinstalling did not help in this system, I had similar issue on
> another one and that fixed it.
> Synaptic throws false positive on root password and will not start.
> The root password is correct and these are the errors in terminal:
> 
> ckosloff@crosshair:~$ su
> Password:
> root@crosshair:/home/ckosloff# synaptic
> No protocol specified
> 
> ** (synaptic:3056): WARNING **: Could not open X display
> No protocol specified
> Unable to init server: Could not connect: Connection refused
> 
> (synaptic:3056): Gtk-WARNING **: cannot open display: :0
> root@crosshair:/home/ckosloff# exit
> 
> The failed processes are synaptic-pkexec and pkexec.
> 
> Here is a snapshot: http://imgur.com/rlz0ga4
> 
This looks like an issue on your side, not a synaptic bug.  For
support/help channels please see https://www.debian.org/support

Cheers,
Julien


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

Processed: blocks

[Debian Bug Tracking System]

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

> block 792177 by 815411
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was not blocked by any bugs.
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 815411
> block 792177 by 815412
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was blocked by: 815411
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 815412
> block 792177 by 815413
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was blocked by: 815411 815412
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 815413
> block 792177 by 815415
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was blocked by: 815413 815412 815411
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 815415
> block 792177 by 815419
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was blocked by: 815411 815412 815415 815413
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 815419
> block 792177 by 815421
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was blocked by: 815412 815411 815413 815415 815419
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 815421
> block 792177 by 745006
Bug #792177 [libjson0-dev] libjson-c-dev: causes creation of unowned 
/usr/lib//libjson-c.so.2 -> libjson-c.so symlink
792177 was blocked by: 815411 815412 815421 815413 815419 815415
792177 was not blocking any bugs.
Added blocking bug(s) of 792177: 745006
> thanks
Stopping processing here.

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

Processed: forcibly merging 815125 815404

[Debian Bug Tracking System]

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

> forcemerge 815125 815404
Bug #815125 [src:linux] linux-image-4.4.0-1-amd64 fails to load initrd - no 
booting
Bug #815126 [src:linux] linux-image-4.4.0-1-amd64 hangs after 'Loading initial 
ramdisk ...'
Bug #815173 [src:linux] kernel-image-4.4.0-1-amd64 does not boot on my Thinkpad 
X240
Bug #815404 [src:linux] linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 
Carbon
Severity set to 'critical' from 'important'
Marked as found in versions linux/4.4.2-2.
Added tag(s) moreinfo.
Bug #815126 [src:linux] linux-image-4.4.0-1-amd64 hangs after 'Loading initial 
ramdisk ...'
Bug #815173 [src:linux] kernel-image-4.4.0-1-amd64 does not boot on my Thinkpad 
X240
Merged 815125 815126 815173 815404
> thanks
Stopping processing here.

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

Processed: severity of 785069 is important

[Debian Bug Tracking System]

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

> severity 785069 important
Bug #785069 [apt-setup] jessie live-installer can't install grub when booted 
via usb drive without internet
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#814067: marked as done (xdelta3: CVE-2014-9765: buffer overflow in main_get_appheader)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 12:17:49 +
with message-id 
and subject line Bug#814067: fixed in xdelta3 3.0.0.dfsg-1+deb7u1
has caused the Debian Bug report #814067,
regarding xdelta3: CVE-2014-9765: buffer overflow in main_get_appheader
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.)


-- 
814067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xdelta3
Severity: grave
Tags: security upstream fixed-upstream

xdelta3 before 3.0.9 contains buffer overflow which allows arbitrary
code execution from input files at least on some systems.

3.0.0.dfsg-1 and 3.0.8-dfsg-1 are definitly affected.

08.02.2016 в 06:57:12 +0100 Salvatore Bonaccorso написал:
> On Sun, Feb 07, 2016 at 07:05:12PM +0400, Stepan Golosunov wrote:
> > This appears to be fixed in xdelta3 3.0.9 and later via
> > https://github.com/jmacd/xdelta-devel/commit/ef93ff74203e030073b898c05e8b4860b5d09ef2
> > but not in Debian.
> > 
> > What should be done next? Should I open a bug?
> 
> Yes, since the commit is in the public git repo I think it is best to
> open a bug in the Debian BTS.

> p.s.: Just noticed there seem to be two git repositories by jmacd, the
>   commit is as well in
>   
> https://github.com/jmacd/xdelta/commit/969e65d3a5d70442f5bafd726bcef47a0b48edd8

README.md says that this repository contains old data from
https://code.google.com/p/xdelta. Newer code and releases are
currently only in xdelta-devel.
--- End Message ---
--- Begin Message ---
Source: xdelta3
Source-Version: 3.0.0.dfsg-1+deb7u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated xdelta3 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: Fri, 19 Feb 2016 14:35:03 +0100
Source: xdelta3
Binary: xdelta3 python-xdelta3
Architecture: source amd64
Version: 3.0.0.dfsg-1+deb7u1
Distribution: wheezy-security
Urgency: high
Maintainer: A Mennucc1 
Changed-By: Salvatore Bonaccorso 
Description: 
 python-xdelta3 - Xdelta3 python module
 xdelta3- A diff utility which works with binary files
Closes: 814067
Changes: 
 xdelta3 (3.0.0.dfsg-1+deb7u1) wheezy-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2014-9765: buffer overflow in main_get_appheader (Closes: #814067)
Checksums-Sha1: 
 9e9f261d46bdb773d803a9c47ca0bfb74ef4462b 1806 xdelta3_3.0.0.dfsg-1+deb7u1.dsc
 ca8ffc1a74f5808411d3abb3f83bb1f978725295 173789 xdelta3_3.0.0.dfsg.orig.tar.bz2
 7c3f6f2ee0d205860eba8a1a4c91823494972b8b 10596 
xdelta3_3.0.0.dfsg-1+deb7u1.debian.tar.gz
 651ae3d1adf288e899a019f134c215eafaad3788 83974 
xdelta3_3.0.0.dfsg-1+deb7u1_amd64.deb
 c86fe011c356dc2048d675276c3139eb37972de7 153034 
python-xdelta3_3.0.0.dfsg-1+deb7u1_amd64.deb
Checksums-Sha256: 
 88cfe5ea7249c852216fb8dfca66f0298aa0d6d6b5251e2d06d3adb9ce62ca21 1806 
xdelta3_3.0.0.dfsg-1+deb7u1.dsc
 dc486b24600aa21a40e5bf28308fdfecd54c2fd64d5ca78a81c9036521fd2fc3 173789 
xdelta3_3.0.0.dfsg.orig.tar.bz2
 05a41e80749c043541ba4a3a7ac86d9fca737cf19a8b2e6417931312e2b84b65 10596 
xdelta3_3.0.0.dfsg-1+deb7u1.debian.tar.gz
 388de74707c1cb66b551cb4291dd75c1b20a9df456207ddf6de22844f492a931 83974 
xdelta3_3.0.0.dfsg-1+deb7u1_amd64.deb
 3088cb2914a5a6ae95f0c2f5358d21c4a95b1bac9118c10512f1d4f545c63ab3 153034 
python-xdelta3_3.0.0.dfsg-1+deb7u1_amd64.deb
Files: 
 a4523f5be7635241b335eef605c9b843 1806 utils optional 
xdelta3_3.0.0.dfsg-1+deb7u1.dsc
 a0753ef32a6aac97caf718e193b83172 173789 utils optional 
xdelta3_3.0.0.dfsg.orig.tar.bz2
 509dfbb7e3de524dc7db2b81a8d20ee2 10596 utils optional 
xdelta3_3.0.0.dfsg-1+deb7u1.debian.tar.gz
 6007260866bdd289a78fa3ccd05f9395 83974 utils optional 
xdelta3_3.0.0.dfsg-1+deb7u1_amd64.deb
 ed404f90df8ead673abefde19e02dd6a 153034 python optional 
python-xdelta3_3.0.0.dfsg-1+deb7u1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#815111: marked as done (didiwiki: CVE-2013-7448: path traversal vulnerability)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 12:17:45 +
with message-id 
and subject line Bug#815111: fixed in didiwiki 0.5-11+deb7u1
has caused the Debian Bug report #815111,
regarding didiwiki: CVE-2013-7448: path traversal vulnerability
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.)


-- 
815111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: didiwiki
Version: 0.5-11
Tags: patch + pending
Severity: critical

A user has privately sent me a security patch for the didiwiki
package, that I maintain. The current installation allows any of the
system's the user to access any file on the filesystem. To reproduce
it:

apt-get install didiwiki

curl http://localhost:8000/api/page/get?page=/etc/passwd


A patch was also provided by Alexander Izmailov, and will be applied
in the upcoming update. Thank you for that!

A CVE request has been requested. The Debian security team has been
notified too.

A version correcting this error will be uploaded soon.

 Ignace M
--- End Message ---
--- Begin Message ---
Source: didiwiki
Source-Version: 0.5-11+deb7u1

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

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

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated didiwiki 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: Fri, 19 Feb 2016 15:25:26 +0100
Source: didiwiki
Binary: didiwiki
Architecture: source amd64
Version: 0.5-11+deb7u1
Distribution: wheezy-security
Urgency: high
Maintainer: Ignace Mouzannar 
Changed-By: Sebastien Delafond 
Description: 
 didiwiki   - simple wiki implementation with built-in webserver
Closes: 815111
Changes: 
 didiwiki (0.5-11+deb7u1) wheezy-security; urgency=high
 .
   * NMU by the Security Team; thanks to Ignace Mouzannar
  and Alexander Izmailov  for
 providing the patch for CVE-2013-7448, correcting a major security
 issue allowing didiwiki to display any file on the
 filesystem. (Closes: #815111)
Checksums-Sha1: 
 886af9719e00744714ac6c3135c4afd85aeb383c 1341 didiwiki_0.5-11+deb7u1.dsc
 3a338305a020951243344ef27e42f163f52288ea 99569 didiwiki_0.5.orig.tar.gz
 7d59da3465e4ad46ac6c01e7bd5885d647e88ddb 15697 
didiwiki_0.5-11+deb7u1.debian.tar.gz
 2ef918a63bde3484a103c309a80d44ab00bfbbce 31482 didiwiki_0.5-11+deb7u1_amd64.deb
Checksums-Sha256: 
 68f5f941638b62e2d1bf1ef72ddf5af0124a9297080fbc8527fcbc06269d5c46 1341 
didiwiki_0.5-11+deb7u1.dsc
 31e8e536f5efd7d7d1d5f4e4458b42aa9cd7910acf3da933cb7fa3507cf7f752 99569 
didiwiki_0.5.orig.tar.gz
 b6382c85824c67e583af64b0a2048cbc9e35bb9fb5d672b6a2ee0e054aef77fa 15697 
didiwiki_0.5-11+deb7u1.debian.tar.gz
 f50e59be20f3a2fb7a0963892ea5897989dd4a3989adb4c01b396dbe289db073 31482 
didiwiki_0.5-11+deb7u1_amd64.deb
Files: 
 b88e8e011df187fddc90a3eda9a7c3c0 1341 web optional didiwiki_0.5-11+deb7u1.dsc
 94d5fb06d091804b31658481f23b120f 99569 web optional didiwiki_0.5.orig.tar.gz
 77a87480f00a92816002c57d2d6c6313 15697 web optional 
didiwiki_0.5-11+deb7u1.debian.tar.gz
 e78a1578b4fa057473e6eab07b627bcb 31482 web optional 
didiwiki_0.5-11+deb7u1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWyFqUAAoJEBC+iYPz1Z1kJjsIALxwSdh6dNGIziZPFfT/gkRx
NpXxShDyBZGJnS2kdUNYONjMXAPbdsf2T5LNgJPlW79x8h41cJIVrWEb2rYRoJtx
lW267h9OBnOl/VJDzz7cobzp+HU+u4oc/tHDzfefI664yKKpRUHU3UU4RuVwTVao
ycrrPk9dXuL7uk83WFSsxP4cNwrYBWFnX3HDoEjDbgJ/pi+u84uuJNM9R+AUHWcz
ByEicLei//sS0I2i4CmLRYYKGviaLUkxL9KLXV1eGQQqbxZH5NVM09cm5buuyi+1
AAgyyht9NN75iQ9Zxd+4ICKW5kX2CVG3Hu77e+YtFRCgJfkU+57fAVnMqfV355s=
=38XO
-END PGP SIGNATURE End Message ---

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Ben Hutchings]

On Sun, 2016-02-21 at 08:40 +0100, Mateusz Kaduk wrote:
> Hi Ben,
[...]
> > - If you haven't already reported this, does the Linux 4.5-rc4 package
> >   from experimental have the same problem?
> > 
> 
> I am using 4.5.0-rc4-amd64 from experimental at the moment as that boots
> without issues.
> Only 4.4.0 seems to be affected.
> 
> > This test version is now available at
> > https://people.debian.org/~benh/packages/unstable/
> 
> 
> > Please report back whether this does or doesn't fix the problem for
> > you. 
> 
> I installed 4.4.2-3~a.test and it replaced previous 4.4.x package, but
> system is not booting either.
> 
> Let me know if you need anything.

It sounds like this is a slightly different bug; please open a new bug report.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.

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

Processed: severity of 793661 is important

[Debian Bug Tracking System]

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

> severity 793661 important
Bug #793661 [nfs-kernel-server] crashes the server
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 787218 is important

[Debian Bug Tracking System]

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

> severity 787218 important
Bug #787218 [gnome-session-bin] gnome-session-failed tried to wreck my X session
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#815396: marked as done (python-snuggs: FTBFS: E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 12:05:32 +
with message-id 
and subject line Bug#815396: fixed in python-snuggs 1.3.1-2
has caused the Debian Bug report #815396,
regarding python-snuggs: FTBFS: E: pybuild pybuild:274: test: plugin distutils 
failed with: exit code=5
to be marked as done.

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

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


-- 
815396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-snuggs
Version: 1.3.1-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-snuggs fails to build from source in unstable/amd64:

  [..]

 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20160221091808.ywQnUdn26V/python-snuggs-1.3.1/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest 
  = test session starts 
==
  platform linux2 -- Python 2.7.11, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
  rootdir: /home/lamby/temp/cdt.20160221091808.ywQnUdn26V/python-snuggs-1.3.1, 
inifile: 
  collected 0 items
  
  = no tests ran in 0.00 seconds 
=
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5: cd 
/home/lamby/temp/cdt.20160221091808.ywQnUdn26V/python-snuggs-1.3.1/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

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


python-snuggs.1.3.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-snuggs
Source-Version: 1.3.1-2

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-snuggs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Feb 2016 12:20:27 +0100
Source: python-snuggs
Binary: python-snuggs python3-snuggs
Architecture: source all
Version: 1.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 python-snuggs - S-expressions for numpy - Python 2 version
 python3-snuggs - S-expressions for numpy - Python 3 version
Closes: 815396
Changes:
 python-snuggs (1.3.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Update Vcs-* URLs to use HTTPS.
   * Bump Standards-Version to 3.9.7, no changes.
   * Add test_snuggs.py to test command.
 (closes: #815396)
   * Enable parallel builds.
Checksums-Sha1:
 f334eeeae40d6aa23be247421cd53c7088a26f3e 2218 python-snuggs_1.3.1-2.dsc
 53057b920083052874d68fba241b6b01ded380b4 2416 
python-snuggs_1.3.1-2.debian.tar.xz
 4731e27fd99531a4fc9c8419e7ae74c35f12bf19 5868 python-snuggs_1.3.1-2_all.deb
 28f367d09a2e455a383446797bdc4b0682317f4f 5954 python3-snuggs_1.3.1-2_all.deb
Checksums-Sha256:
 3734f6bdf5825f8920ea6d2f8df9b1d2f0c4138cff12d68b9ac03211090024fa 2218 
python-snuggs_1.3.1-2.dsc
 b506fdc479d3460bfc7b7e204606448a24cf2a93ae1bf15d04ece119d9e01583 2416 
python-snuggs_1.3.1-2.debian.tar.xz
 ab3b6fdf3216db73bcbada6cf2c562189faf097bbfe451785620666e227f2cfe 5868 
python-snuggs_1.3.1-2_all.deb
 f7cbe048291f72a23ffc60b9e16ecea9f47499c67850b0f7ee44c8abe3b528df 5954 
python3-snuggs_1.3.1-2_all.deb
Files:
 3d18b63efff8810bfba78c4a05f46054 2218 python optional python-snuggs_1.3.1-2.dsc
 afdfaba8d9a653e79ffc2777cae3bae9 2416 python optional 
python-snuggs_1.3.1-2.debian.tar.xz
 43dcd78a99b61deea3c2756d0f5a34f1 5868 python optional 
python-snuggs_1.3.1-2_all.deb
 

Bug#785924: [Freewx-maint] Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

[Olly Betts]

Sebastian Dröge  wrote:
> How can I test the wxwidgets GStreamer integration?

You need to test via an application which uses it - something which depends
on the wx or wxpython media package.  I think I've used whyteboard for this
before.

Thanks for looking at this.

Cheers,
Olly

Bug#814276: Non-Free file: src/stdlib/SDL_qsort.c

[Manuel A. Fernandez Montecelo]

Hi Ben,

2016-02-21 03:09 Ben Hutchings:

I happen to know the original author, so I've mailed him requesting he
consider relicencing.


I suppose that you were looking into this as part of the BSP.

I notified upstream a few days ago, and they didn't want to be in
possible breach of the license, so they changed the implementation for
libsdl2:

 
http://lists.alioth.debian.org/pipermail/pkg-sdl-maintainers/2016-February/002374.html

libsdl1.2 suffers from the same problem, but we can just repack the
orig.tar and disable the use of this implementation (it's supposed to
not be used by default, so an empty file would do, or otherwise the file
from libsdl2 can be used).

So, in summary, I am going to upload fixes in the next few days.


At this point I suspect that upstream is not going to go back (unless
the implementation that they now use is problematic).  Maybe it's good
if you could get this relicenced just in case, e.g. for the benefit of
other distros.  What do you think?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#815394: marked as done (python-certifi: FTBFS: h_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 21 Feb 2016 11:28:49 +
with message-id 
and subject line Bug#815394: fixed in python-certifi 2015.11.20.1-2
has caused the Debian Bug report #815394,
regarding python-certifi: FTBFS: h_auto_test: pybuild --test --test-pytest -i 
python{version} -p 2.7 --dir . returned exit code 13
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.)


-- 
815394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-certifi
Version: 2015.11.20.1-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-certifi fails to build from source in unstable/amd64:

  [..]

 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20160221091706.x6lrDRbUP9/python-certifi-2015.11.20.1/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest 
  = test session starts 
==
  platform linux2 -- Python 2.7.11, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
  rootdir: 
/home/lamby/temp/cdt.20160221091706.x6lrDRbUP9/python-certifi-2015.11.20.1, 
inifile: 
  collected 0 items
  
  = no tests ran in 0.00 seconds 
=
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5: cd 
/home/lamby/temp/cdt.20160221091706.x6lrDRbUP9/python-certifi-2015.11.20.1/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest 
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . 
returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

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


python-certifi.2015.11.20.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-certifi
Source-Version: 2015.11.20.1-2

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

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

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated python-certifi 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Feb 2016 11:52:46 +0100
Source: python-certifi
Binary: python-certifi python3-certifi
Architecture: source all
Version: 2015.11.20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 python-certifi - root certificates for validating SSL certs and verifying TLS 
host
 python3-certifi - root certificates for validating SSL certs and verifying TLS 
host
Closes: 815394
Changes:
 python-certifi (2015.11.20.1-2) unstable; urgency=medium
 .
   * No tests (Closes: #815394)
Checksums-Sha1:
 35011c67c49b710d4895ea5ae95a17b883ed7f70 1728 python-certifi_2015.11.20.1-2.dsc
 e78afa3084d33e2346ba0268249029318bb14295 7044 
python-certifi_2015.11.20.1-2.debian.tar.xz
 a735c6ce9832ea10b7485ea4ff7aa8af8c2e0049 172658 
python-certifi_2015.11.20.1-2_all.deb
 9439f97ea9f35dc2759a7061c77f702056b27ccf 172664 
python3-certifi_2015.11.20.1-2_all.deb
Checksums-Sha256:
 e8584c8ccadf6614e5322e146a3279dbed07b44fdab930b36b80c32ccc93efa8 1728 
python-certifi_2015.11.20.1-2.dsc
 11f106da5e346b9eac262409c23f0b862a7edd021ea3f0d95ad71633e0a83c18 7044 
python-certifi_2015.11.20.1-2.debian.tar.xz
 4f529dda7e65853f1cbda2cad77223e6ff152523c38fecf2fbaaa07aa42e14eb 172658 
python-certifi_2015.11.20.1-2_all.deb
 3fc7f3926a25bf748f8bf8060e7350f15eae7282a58d5cee9e554161e6b8edd1 172664 
python3-certifi_2015.11.20.1-2_all.deb
Files:
 d3686c674665a9abbffea68fa6f1d59b 1728 python optional 
python-certifi_2015.11.20.1-2.dsc
 f00c9023a44c3ea61062e905cf37484c 7044 python optional 
python-certifi_2015.11.20.1-2.debian.tar.xz
 

Processed: Re: Bug#815396: python-snuggs: FTBFS: E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #815396 [src:python-snuggs] python-snuggs: FTBFS: E: pybuild pybuild:274: 
test: plugin distutils failed with: exit code=5
Added tag(s) pending.

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

Bug#815396: python-snuggs: FTBFS: E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Chris,

Thanks for your work reproducible builds and reporting this issue.

On 21-02-16 09:38, Chris Lamb wrote:
>   E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5: cd 
> /home/lamby/temp/cdt.20160221091808.ywQnUdn26V/python-snuggs-1.3.1/.pybuild/pythonX.Y_2.7/build;
>  python2.7 -m pytest 

The test command needed the path to the test script appended.

The fixed package is on its way to unstable.

Kind Regards,

Bas

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

Bug#815395: [Pkg-freeipa-devel] Bug#815395: python-kdcproxy: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . returned exit code 13

[Timo Aaltonen]

21.02.2016, 10:37, Chris Lamb kirjoitti:
> Source: python-kdcproxy
> Version: 0.3.2-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-kdcproxy fails to build from source in unstable/amd64:

I'm not sure if pybuild did the right thing, but running tox manually
reveals something that is actually a bug in mock

 FAILURES ===
_KDCProxyWSGITests.test_post_asreq ___
/usr/lib/python2.7/dist-packages/mock/mock.py:1297: in patched
arg = patching.__enter__()
/usr/lib/python2.7/dist-packages/mock/mock.py:1450: in __enter__
_name=self.attribute, **kwargs)
/usr/lib/python2.7/dist-packages/mock/mock.py:2320: in create_autospec
_name='()', _parent=mock)
/usr/lib/python2.7/dist-packages/mock/mock.py:2359: in create_autospec
_check_signature(original, new, skipfirst=skipfirst)
/usr/lib/python2.7/dist-packages/mock/mock.py:228: in _check_signature
_copy_func_details(func, checksig)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

func = 
funcopy = 

def _copy_func_details(func, funcopy):
funcopy.__name__ = func.__name__
funcopy.__doc__ = func.__doc__
try:
funcopy.__text_signature__ = func.__text_signature__
except AttributeError:
pass
# we explicitly don't copy func.__dict__ into this copy as it would
# expose original attributes that should be mocked
try:
funcopy.__module__ = func.__module__
except AttributeError:
pass
try:
funcopy.__defaults__ = func.__defaults__
except AttributeError:
pass
try:
funcopy.__kwdefaults__ = func.__kwdefaults__
except AttributeError:
pass
if not inPy3k:
>   funcopy.func_defaults = func.func_defaults
E   AttributeError: 'functools.partial' object has no attribute
'func_defaults'

https://github.com/nsqio/pynsq/pull/147

though I haven't tested if this would fix the tests here.

-- 
t

Processed: tagging 813260

[Debian Bug Tracking System]

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

> tags 813260 + pending
Bug #813260 [scim] scim: prerm called with unknown argument `upgrade'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#815133: gitlab installation fails with LoadError: cannot load such file -- /usr/share/gitlab/config/application

[Pirate Praveen]

On Sat, 20 Feb 2016 22:37:20 +0530 Pirate Praveen  
wrote:
> Hi Josch,
> 
> You'll have to do a fresh install as directory structure has changed 
> significantly.
> 
> 1. apt-get purge gitlab (removes files, so new version can add symlinks)
> 2. rm -rf /usr/share/gitlab (config, tmp, log were not empty).
> 3. userdel -r gitlab (/var/lib/gitlab is new home or .gitconfig can't be 
> created)
> 4. apt-get install gitlab

You have to also remove /usr/share/gitlab-shell/.gitlab_shell_secret

> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#815409: libguestfs: FTBFS on mips: segfault while creating blank-disk-1s.qcow2

[Andreas Beckmann]

Source: libguestfs
Version: 1:1.32.2-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libguestfs FTBFS on mips:

https://buildd.debian.org/status/fetch.php?pkg=libguestfs=mips=1%3A1.32.2-3=1455065650

Making all in blank-disks
make[5]: Entering directory 
'/«PKGBUILDDIR»/debian/build-python3.4/test-data/blank-disks'
rm -f blank-disk-1s.raw
qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512
truncate -s 512 blank-disk-1s.raw
rm -f blank-disk-1K.raw
truncate -s 1K blank-disk-1K.raw
qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1K.qcow2 1K
Makefile:1691: recipe for target 'blank-disk-1s.qcow2' failed
make[5]: *** [blank-disk-1s.qcow2] Segmentation fault


Andreas