Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

[Viral Shah]

LLVM 3.7.1 should have decent performance as we upstreamed various performance 
patches from the Julia project. However, we still have patches on top of llvm 
3.7.1 for getting acceptable performance. However, this is all on the julia 
master, and not julia 0.4.

-viral



> On 08-Apr-2016, at 9:31 PM, Peter Colberg  wrote:
> 
> On Fri, Apr 08, 2016 at 09:55:02PM +0200, Graham Inggs wrote:
>> On 8 April 2016 at 21:16, Emilio Pozuelo Monfort  wrote:
>>> Why did you switch to 3.8? The default in unstable is 3.6 and in 
>>> experimental is
>>> 3.7.
>> 
>> I understood there were severe performance regressions with Julia on
>> LLVM > 3.3 that were only fixed in 3.8.
> 
> The reason for switching to LLVM 3.8 was the abysmal performance
> of LLVM 3.7 on i386, and complete failure of LLVM 3.6 or earlier.
> 
> https://github.com/JuliaLang/julia/issues/14191
> 
> Peter
> 
> ___
> Pkg-julia-devel mailing list
> pkg-julia-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-julia-devel

Bug#806487: This was fixed in an update to binutils 2.26

[Adam Baxter]

Upstream bugs https://sourceware.org/bugzilla/show_bug.cgi?id=19538 and
https://sourceware.org/bugzilla/show_bug.cgi?id=19615

This was fixed in Debian somewhere between binutils-2.26-3 (which is
affected) and -8 (which works fine).

This can probably be closed or assigned to the binutils package.


Regards,
Adam

Bug#798032: marked as done (libpgf: CVE-2015-6673: use-after-free vulnerability in Decoder.cpp)

[Debian Bug Tracking System]

Your message dated Sat, 09 Apr 2016 05:34:17 +
with message-id 
and subject line Bug#798032: fixed in libpgf 6.14.12-3.2
has caused the Debian Bug report #798032,
regarding libpgf: CVE-2015-6673: use-after-free vulnerability in Decoder.cpp
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.)


-- 
798032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpgf
Version: 6.14.12-3
Severity: important
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for libpgf.

CVE-2015-6673[0]:
use-after-free vulnerability in Decoder.cpp

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-6673

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libpgf
Source-Version: 6.14.12-3.2

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

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

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated libpgf 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, 03 Apr 2016 21:58:47 -0500
Source: libpgf
Binary: libpgf-dev libpgf6 libpgf6-dbg
Architecture: source amd64
Version: 6.14.12-3.2
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 
Changed-By: Steve M. Robbins 
Description:
 libpgf-dev - Progressive Graphics File (PGF) library - development files
 libpgf6- Progressive Graphics File (PGF) library - runtime files
 libpgf6-dbg - Progressive Graphics File (PGF) library - debugging symbols
Closes: 798032
Changes:
 libpgf (6.14.12-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply upstream changes 147 & 148 to fix CVE-2015-6673 (Closes:
 #798032).  New patches 02-fix-CVE-2015-6673-upstream-147.patch and
 03-fix-CVE-2015-6673-upstream-148.patch.
Checksums-Sha1:
 d56027f55aa05a0139337d539c5a1125551c858b 1954 libpgf_6.14.12-3.2.dsc
 50c98be546e335e31a7c06fdc0d968a5a728a210 29572 libpgf_6.14.12-3.2.debian.tar.xz
 12b4b927294ad880e9561af4de971fb14f32e2a7 49600 libpgf-dev_6.14.12-3.2_amd64.deb
 28b5e12a00e7de1c43b1f7d9988c5c79507dec13 100662 
libpgf6-dbg_6.14.12-3.2_amd64.deb
 06d7d9da1e7066b063a6023b1d664b6840b26be0 37580 libpgf6_6.14.12-3.2_amd64.deb
Checksums-Sha256:
 f745d7b3c8545d185fe15f1b09b797abbb42292cc96e59cc0c5a2617eb1fca8b 1954 
libpgf_6.14.12-3.2.dsc
 bfbc8d866f9ff8e5b428161b63cf1869d9314f3731f66e43b1dd7baa39832ea6 29572 
libpgf_6.14.12-3.2.debian.tar.xz
 b5f6e44e507e73241aaeb253539ce64be6ca2b3f072f3eba43980745530fe4e7 49600 
libpgf-dev_6.14.12-3.2_amd64.deb
 e5fabf366996abfb675eba1e3cf3307edb647ecbaaa45a34ec57f52fa80de737 100662 
libpgf6-dbg_6.14.12-3.2_amd64.deb
 63d8027522e12fba39f841a5ecf16c86b4f35322bc07efadac5119ee6643ce4b 37580 
libpgf6_6.14.12-3.2_amd64.deb
Files:
 3a0acffb12461275d6fb082af313d0d4 1954 libs optional libpgf_6.14.12-3.2.dsc
 9d8e7010caafdd1d4fe1b83ce28c6f3c 29572 libs optional 
libpgf_6.14.12-3.2.debian.tar.xz
 e8f713e5218ce79eac9e218ab5d7d732 49600 libdevel optional 
libpgf-dev_6.14.12-3.2_amd64.deb
 bd24548f4352e94ad0074b7e80008670 100662 debug extra 
libpgf6-dbg_6.14.12-3.2_amd64.deb
 456d8cd738859ec6d9b95d4bbd5e2e56 37580 libs optional 
libpgf6_6.14.12-3.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVwH4GsnlXi+tyPS5AQjH7xAAlZB4hq9OixiCdnczzzwW/i/e3RVIljf+
378gS7p/IScnwRK1KDP8saMtwcd5fTB5JMj146vkzi6bonLtBVkE8CabwCTXtZdI
BPpD3u/DVGyErltiKHDqUHa99yWuQl3yxo8A33up2J0Cq8JqlV01CYi2viRugqbD
5ErR6fwjxUAokOaSO4bXKTVTqcYA9SshIz92iwhL1l/IzEOeBP6XWmNG2Mm/dFU+
2hB85LLkVtBU0ywv6chDIq1PLWr5vsXks4QwG7wQM616pffv8cDwMzoIyQAWXvWe
TqSc+4fSu87hLv1IjC41rYpjBzMeLiewHZYkcW/4CkiRz52l6zTw/ECJ5RACMYju
NZPzqsQ34SeS6OVoBrfHoTlfGQ2m2Q8gv4YWMHPhZ955/JmQkwKufSxzvExDBnkh
U9e6cyuJCCqk06dHLUDrZnjqP7rTOEIp5+H5qaRcdG6G/9C9ifQ/sCLzvkpL4XIJ
auNsu4LwuGs0fL2YGm4BQMNqBnr8ir0Z7X3/daOybSKmREt+jvTL07eLinC58NWW
EI11N1B1rcd4tVGRv8UxEkYaNgviD1BRIis9Kuq6sYgbUIiJYdhzlKndxkcJVcWG
vVtP

Bug#820439: imview: diff for NMU version 1.1.9c-12.1

[Anton Gladky]

Hi Tobias,

thank you for the patch!

Please cancel NMU-upload, because I integrated your patch
into the version 1.1.9c-13 and uploaded it.

Best regards


Anton

2016-04-08 16:24 GMT+02:00 Tobias Frost :

> Control: tags 820439 + patch
> Control: tags 820439 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for imview (versioned as 1.1.9c-12.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
> diff -Nru imview-1.1.9c/debian/changelog imview-1.1.9c/debian/changelog
> --- imview-1.1.9c/debian/changelog  2013-05-07 21:00:45.0 +0200
> +++ imview-1.1.9c/debian/changelog  2016-04-08 16:23:52.0 +0200
> @@ -1,3 +1,10 @@
> +imview (1.1.9c-12.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix for libpng1.6 (Closes: #820439)
> +
> + -- Tobias Frost   Fri, 08 Apr 2016 16:23:52 +0200
> +
>  imview (1.1.9c-12) unstable; urgency=low
>
>[ Sebastian Ramacher ]
> diff -Nru imview-1.1.9c/debian/patches/08_fix_libpng16.patch
> imview-1.1.9c/debian/patches/08_fix_libpng16.patch
> --- imview-1.1.9c/debian/patches/08_fix_libpng16.patch  1970-01-01
> 01:00:00.0 +0100
> +++ imview-1.1.9c/debian/patches/08_fix_libpng16.patch  2016-04-08
> 16:23:37.0 +0200
> @@ -0,0 +1,80 @@
> +Description: Patch for libpng1.6
> + libpng1.6 removed direct access of its member functions.
> +Author: Tobias Frost 
> +Bug-Debian: https://bugs.debian.org/820439
> +Forwarded: no
> +Last-Update: 2016-04-08
> +---
> +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
> +--- a/io/readpng.cxx
>  b/io/readpng.cxx
> +@@ -96,7 +96,7 @@
> + pp   = png_create_read_struct(PNG_LIBPNG_VER_STRING, NULL, NULL,
> NULL);
> + info = png_create_info_struct(pp);
> +
> +-if (setjmp(pp->jmpbuf))
> ++if (setjmp(png_jmpbuf(pp)))
> + {
> + errprintf("PNG file \"%s\" contains errors!\n", pngfilename);
> + return 103;
> +@@ -108,28 +108,40 @@
> + // Get the image dimensions and convert to grayscale or RGB...
> + png_read_info(pp, info);
> +
> +-if (info->color_type == PNG_COLOR_TYPE_PALETTE)
> ++png_uint_32 width;
> ++png_uint_32 height;
> ++int bit_depth;
> ++int color_type;
> ++int interlace_type;
> ++int compression_type;
> ++int filter_method;
> ++
> ++png_get_IHDR(pp, info, &width, &height,
> ++   &bit_depth, &color_type, &interlace_type,
> ++   &compression_type, &filter_method);
> ++
> ++if (color_type == PNG_COLOR_TYPE_PALETTE)
> + png_set_expand(pp);
> +
> +-if (info->color_type & PNG_COLOR_MASK_COLOR)
> ++if (color_type & PNG_COLOR_MASK_COLOR)
> + channels = 3;
> + else
> + channels = 1;
> +
> +-if ((info->color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
> ++if ((color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
> + channels ++;
> +
> +-w = (int)(info->width);
> +-h = (int)(info->height);
> ++w = (int)(width);
> ++h = (int)(height);
> + d = channels;
> +
> +-if (info->bit_depth < 8)
> ++if (bit_depth < 8)
> + {
> + png_set_packing(pp);
> + png_set_expand(pp);
> + }
> + // we ought to read the 16-bit data correctly, since we can !
> +-else if (info->bit_depth == 16)
> ++else if (bit_depth == 16)
> + png_set_strip_16(pp);
> +
> + #  if defined(HAVE_PNG_GET_VALID) && defined(HAVE_PNG_SET_TRNS_TO_ALPHA)
> +--- a/io/readpng.cxx
>  b/io/readpng.cxx
> +@@ -128,7 +128,9 @@
> + else
> + channels = 1;
> +
> +-if ((color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
> ++int num_trans;
> ++png_get_tRNS(pp, info, NULL, &num_trans, NULL);
> ++if ((color_type & PNG_COLOR_MASK_ALPHA) || num_trans)
> + channels ++;
> +
> + w = (int)(width);
> diff -Nru imview-1.1.9c/debian/patches/series
> imview-1.1.9c/debian/patches/series
> --- imview-1.1.9c/debian/patches/series 2013-05-07 20:20:40.0 +0200
> +++ imview-1.1.9c/debian/patches/series 2016-04-08 15:45:09.0 +0200
> @@ -5,3 +5,4 @@
>  05_fix_dangerous_use_of_strncpy.patch
>  06_fix_format_not_a_string.patch
>  07_fix_kfreebsd_FTBFS.patch
> +08_fix_libpng16.patch
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
>

Processed: playonlinux: FTBFS in sid: dh_install: Cannot find (any matches for) "plugins/TransgamingCedega*" and "plugins/Wine*"

[Debian Bug Tracking System]

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

> tags 820329 patch
Bug #820329 [src:playonlinux] playonlinux: FTBFS in sid: dh_install: Cannot 
find (any matches for) "plugins/TransgamingCedega*" and "plugins/Wine*"
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#820329: playonlinux: FTBFS in sid: dh_install: Cannot find (any matches for) "plugins/TransgamingCedega*" and "plugins/Wine*"

[Denis Briand]

tags 820329 patch
thanks

Hello,
Upstream did removed these two plugin and add another one.
You should try this trivial patch.

Best regards

Denis Briand  
--- playonlinux.install.old	2016-04-09 06:22:29.913632999 +0200
+++ playonlinux.install	2016-04-09 06:35:42.134081741 +0200
@@ -8,7 +8,7 @@
 python/*.py usr/share/playonlinux/python/
 python/lib/*.py usr/share/playonlinux/python/lib/
 resources/* usr/share/playonlinux/resources/
-plugins/plugins.lst plugins/polvault* plugins/ScreenCap* plugins/TransgamingCedega* plugins/Wine* usr/share/playonlinux/plugins/
+plugins/plugins.lst plugins/polvault* plugins/ScreenCap* plugins/Capture* usr/share/playonlinux/plugins/
 playonlinux usr/share/playonlinux/
 playonlinux-bash usr/share/playonlinux/
 playonlinux-pkg usr/share/playonlinux/

Bug#817815: marked as done (drupal7-mod-civicrm: directory vs. symlink conflict: /usr/share/drupal7/sites -> /etc/drupal/7/sites)

[Debian Bug Tracking System]

Your message dated Sat, 09 Apr 2016 03:35:31 +
with message-id 
and subject line Bug#817815: fixed in civicrm 4.7.6+dfsg-1
has caused the Debian Bug report #817815,
regarding drupal7-mod-civicrm: directory vs. symlink conflict: 
/usr/share/drupal7/sites -> /etc/drupal/7/sites
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.)


-- 
817815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drupal7-mod-civicrm
Version: 4.7.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.

Your package ships:

drwxr-xr-x root/root 0 2016-02-26 15:34 ./usr/share/drupal7/
drwxr-xr-x root/root 0 2016-02-26 15:34 ./usr/share/drupal7/sites/
drwxr-xr-x root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/
drwxr-xr-x root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/files/
lrwxrwxrwx root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/files/civicrm -> /var/lib/civicrm
lrwxrwxrwx root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/civicrm -> /etc/civicrm

but package drupal7 ships:

drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/7/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/7/sites/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/7/sites/default/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./usr/share/drupal7/
lrwxrwxrwx root/root 0 2016-02-26 05:58 
./etc/drupal/7/sites/default/files -> /var/lib/drupal7/files
lrwxrwxrwx root/root 0 2016-02-26 05:58 ./usr/share/drupal7/sites -> 
/etc/drupal/7/sites


Installing something over existing symlinks is considered bad practice.
See e.g. https://lists.debian.org/87ehlevcrf@windlord.stanford.edu

It may break in subtle ways and dpkg cannot detect this as a problem.
* Your package might silently overwrite files installed at the symlink
  destination by other packages.
* If the package shipping the symlink decides to make the link point
  somewhere else (or turn it into a real directory), the files owned
  by your package "will be lost" somewhere in the filesystem.
* Depending on installation order the problematic path will be created
  either as a symlink or a directory: the package installed first will
  "win" and all others have "lost".
  Note that dpkg intentionally does not replace directories with
  symlinks and vice versa, see in particular the end of point 4 in
  
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
  (Note: Adding Pre-Depends is *not* a solution.)

Please move the files shipped in your package to the "real" location.

>From the attached log (usually somewhere in the middle...):

3m15.9s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/drupal7/sites/default (drupal7-mod-civicrm) != 
/etc/drupal/7/sites/default (drupal7)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
  /usr/share/drupal7/sites/default/civicrm (drupal7-mod-civicrm) != 
/etc/drupal/7/sites/default/civicrm (?)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
  /usr/share/drupal7/sites/default/files (drupal7-mod-civicrm) != 
/etc/drupal/7/sites/default/files (drupal7)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
  /usr/share/drupal7/sites/default/files/civicrm (drupal7-mod-civicrm) != 
/var/lib/drupal7/files/civicrm (?)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
/etc/drupal/7/sites/default/files -> /var/lib/drupal7/files


cheers,

Andreas


drupal7-mod-civicrm_4.7.2+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: civicrm
Source-Version: 4.7.6+dfsg-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated civicrm 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 ft

Processed: Bug#817815 tagged as pending

[Debian Bug Tracking System]

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

> tag 817815 pending
Bug #817815 [drupal7-mod-civicrm] drupal7-mod-civicrm: directory vs. symlink 
conflict: /usr/share/drupal7/sites -> /etc/drupal/7/sites
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#817815: tagged as pending

[Dmitry Smirnov]

tag 817815 pending
--

We believe that the bug #817815 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/civicrm.git/diff/?id=24763cd

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 24763cd
Author: Dmitry Smirnov 
Date:   Fri Apr 8 23:11:36 2016

Another drupal7 symlink conflict correction (Closes: #817815).

Processed: affects 814131

[Debian Bug Tracking System]

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

> affects 814131 civicrm
Bug #814131 [php-pager] Useless in Debian
Added indication that 814131 affects civicrm
> thanks
Stopping processing here.

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

Bug#820489: codeblocks: Codeblocks crashes very frequently

[Alejandro Carrazzoni]

Package: codeblocks
Version: 13.12+dfsg-4
Severity: grave
Justification: renders package unusable

Codeblocks very frequently crashes suddenly with no error message when editing
code, particularly when the code involves templates. I'm attaching the .xml
crash log of the last crash.



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

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

Versions of packages codeblocks depends on:
ii  codeblocks-common13.12+dfsg-4
ii  libatk1.0-0  2.18.0-1
ii  libc62.22-5
ii  libcairo21.14.6-1
ii  libcodeblocks0   13.12+dfsg-4
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3
ii  libgcc1  1:5.3.1-13
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.48.0-1
ii  libgtk2.0-0  2.24.30-1.1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpangoft2-1.0-01.38.1-1
ii  libstdc++6   5.3.1-13
ii  libwxbase3.0-0v5 3.0.2+dfsg-1.3
ii  libwxgtk3.0-0v5  3.0.2+dfsg-1.3

Versions of packages codeblocks recommends:
ii  g++4:5.3.1-1
ii  gcc4:5.3.1-1
ii  gdb7.10-1+b1
ii  xterm  324-1

Versions of packages codeblocks suggests:
pn  codeblocks-contrib  
pn  libwxgtk3.0-dev 

-- no debconf information


codeblocks.xml
Description: XML document

Bug#814177: marked as done (jalview: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 23:24:22 +
with message-id 
and subject line Bug#814177: fixed in jalview 2.7.dfsg-5
has caused the Debian Bug report #814177,
regarding jalview: (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.)


-- 
814177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jalview
Version: 2.7.dfsg-4
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: jalview
Source-Version: 2.7.dfsg-5

We believe that the bug you reported is fixed in the latest version of
jalview, 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.
Markus Koschany  (supplier of updated jalview 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, 08 Apr 2016 23:36:00 +0200
Source: jalview
Binary: jalview
Architecture: source all
Version: 2.7.dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 jalview- multiple alignment editor
Closes: 814177
Changes:
 jalview (2.7.dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Add debian/jalview.classpath and replace usage of JH_CLASSPATH_ARGS to
 avoid unwanted dependency on openjdk-7-jdk. (Closes: #814177)
   * Declare compliance with Debian Policy 3.9.7.
   * Vcs: Use cgit and https.
   * Fix Lintian warning dep5-copyright-license-name-not-unique.
Checksums-Sha1:
 6d59834a48e9ccdc64b5391467a7a36969dfd033 2475 jalview_2.7.dfsg-5.dsc
 b6b157004f3080cc7a443f11642af1552536ca92 8296 jalview_2.7.dfsg-5.debian.tar.xz
 a2e31dc561bcb026a70484f980fb418cb476ce25 3392510 jalview_2.7.dfsg-5_all.deb
Checksums-Sha256:
 8c775953bf0e264fdf55d77286f5ffa44fc6b651ac430b9934ea859d0adfae0a 2475 
jalview_2.7.dfsg-5.dsc
 f23dcbfa72f80be78c172bceef1b424df3fe2490ff5a31c03e4baba71ab8cbac 8296 
jalview_2.7.dfsg-5.debian.tar.xz
 3a4562270a9986477be78fc903cc9f0ad255caa843c272fb2f0b81a124114c04 3392510 
jalview_2.7.dfsg-5_all.deb
Files:
 9b56759750ddd639c5489e67b00ecb55 2475 science optional jalview_2.7.dfsg-5.dsc
 077bc0e6149eb1a4d480af347d8d2d52 8296 science optional 
jalview_2.7.dfsg-5.debian.tar.xz
 68ebf3781fa5e822a15a86b7584ad60a 3392510 science optional 
jalview_2.7.dfsg-5_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXCCkSXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkQ3IP/3xxjZ47iKdBqxvUDd+nPSut
IQ9d6Qwf2HD38+7g+Xqw+7MbYj0sUpcbC850tT9SJRUPbeIHO86D8xoAOwUCHN/C
dLnqQM30noADkYVUk9FekLAO4zIaubxeoTfzCbIJZNBXT3TGh5mtr2u6bfv/escb
t5dv0Lg8TXkTXECCrwIH1aJB97qQML8GNFWAM7j4nudAuTVRBYKeD0AqNtlIbjY1
YTuNYgZRTXE+84OBfqA5AZOrjVXyocLUfZWtSBsHq0QoVlmR/62XioR6oNIqzAPP
oGYm+StJuQWo0CX0FKFOt7WP1Pjd/u/7VNThE0G81dY5sOmbk+g9LjGlBWWjmqul
z49/FDh4iSQnj6N/95A1uduXjeRrMhij4AhV2xmerLcf1n5dw5CKBhLLlSPVVMPL
3hERbJ6SOZoh2u/RYUJX+75qyk3YAfG6cW5jUKSLWPj72qde2RLoxJvQD07msUmy
NX85AE8YJNSYKnP34bxQxbPSAmq7SnMImY8HfQwfXwHvD0LwBpQirQ9n845ZED7Z
EQKb1YJs/zh+jMxoXJOWWpQGxsCa7LiC4sUaR9GEBHMCcvHKGyQfq+XSmGnMNTuz
+IjMAu1QGxN1SSpXnijk1U/BBzjwdmxZzNeFxcEulEj2vwd+unLlchLKQbpeL341
Ix9VsdxYzp00RxBd/fdM
=mcU5
-END PGP SIGNATURE End Message ---

Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

[peter green]

On 08/04/16 20:55, Graham Inggs wrote:


Secondly, it should be possible to reproduce the fault by building in
an armhf schroot on abel.d.o, which has the same hardware as the
buildds.  A temporary solution would be to upload armhf binaries built
on asachi.d.o.
   
It would be useful if someone can reproduce the issue and get a 
dissasembly of the failure location.


My gut feeling is that llvm is trying to use neon without first checking 
it is supported. Afaict the marvell boards we are using for armhf 
buildds (and for the abel.d.o porterbox) don't have neon.



[1] 
https://buildd.debian.org/status/package.php?p=llvm-toolchain-3.8&suite=unstable

   

Bug#820026: icedove crashes (segfaults) when installed along with xul-ext-foxyproxy-standard

[Carsten Schoenert]

Hello Cyril,

On Mon, Apr 04, 2016 at 10:50:55PM +0200, Cyril Chaboisseau wrote:
> I've been fighting to understand why icedove was crashing on me (either
> segfaults or with bus error) for both versions 38 and 44, 

sounds strange.
Can you please create a backtrace of such crashes?

  https://wiki.debian.org/Icedove#Debugging

Before deciding what to do next it would be interesting to see where
the crashes happen.

> after finally
> discovering that Firefox extension foxyproxy 4.5.6 was causing the
> crashes
> 
> see bug #815000
> 
> if the problem cannot be solved (from what I understand after a quick
> look at the upstream bug report), that needs to be dealt in the icedove
> package to prevent others from having both packages installed alongside
> 
> foxyproxy 4.5.6 is already in testing since 31 March, and I fear that
> many Debian users who have both programs don't understand at first
> glance that the instability comes from this bad interaction
> 
> please, add a tag to put xul-ext-foxyproxy-standard in conflict with
> icedove (at least with this specific version if you think that it will
> be solved in an upcoming release)

A crash is definitely a bug and have to be fixed, so it wouldn't be the
right thing to "fix" such a issue by adding a conflicts line. For now we
have to figure out where and why Icedove is crashing.

Regards
Carsten

Processed: bug 813429 is not forwarded

[Debian Bug Tracking System]

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

> notforwarded 813429
Bug #813429 [python3-numpy] python-numpy: breaks the CI tests of some installed 
packages
Bug #813932 [python3-numpy] sunpy: FTBFS: IndexError: only integers, slices 
(`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays 
are valid indices
Bug #816369 [python3-numpy] TypeError: 'float' object cannot be interpreted as 
an index
Bug #816574 [python3-numpy] FTBFS: object cannot be interpreted as an index
Unset Bug forwarded-to-address
Unset Bug forwarded-to-address
Unset Bug forwarded-to-address
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Bug#820068: marked as done (optipng: CVE-2016-2191: Invalid write while processing delta escapes without any boundary checking)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 22:09:02 +
with message-id 
and subject line Bug#820068: fixed in optipng 0.7.6-1
has caused the Debian Bug report #820068,
regarding optipng: CVE-2016-2191: Invalid write while processing delta escapes 
without any boundary checking
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.)


-- 
820068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: optipng
Version: 0.6.4-1
Severity: important
Tags: security upstream fixed-upstream
Forwarded: https://sourceforge.net/p/optipng/bugs/59/

Hi,

the following vulnerability was published for optipng and is fixed
in 0.7.6 upstream.

CVE-2016-2191[0]:
Invalid write while processing delta escapes without any boundary checking

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-2191
[1] https://sourceforge.net/p/optipng/bugs/59/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1308550

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: optipng
Source-Version: 0.7.6-1

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

Debian distribution maintenance software
pp.
Emmanuel Bouthenot  (supplier of updated optipng 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, 08 Apr 2016 23:13:38 +0200
Source: optipng
Binary: optipng
Architecture: source amd64
Version: 0.7.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Emmanuel Bouthenot 
Description:
 optipng- advanced PNG (Portable Network Graphics) optimizer
Closes: 801700 820068
Changes:
 optipng (0.7.6-1) unstable; urgency=medium
 .
   * New upstream release
 - fix CVE-2016-2191: Invalid write while processing delta escapes
   without any boundary checking (Closes: #820068)
 - fix CVE-2015-7802: Buffer overflow in global memory (Closes: #801700)
   * Enable hardening=+all build
   * Fix Vcs-(Git|Browser) fields to use secure URIs
   * Bump Standards-Version to 3.9.7
   * Add a patch to fix typo in manpage
Checksums-Sha1:
 b8ccd9319a7df84119bc9c28d623f6b16249c57d 1986 optipng_0.7.6-1.dsc
 abc480543b85d227db4a84be80ae2dd8a8e53a66 200670 optipng_0.7.6.orig.tar.gz
 7874a68c483cee09ceba09b1ed18ad8edc115896 5045 optipng_0.7.6-1.debian.tar.bz2
 13131d59a660f2a66edb55784e7f974342f4c31e 86936 optipng-dbgsym_0.7.6-1_amd64.deb
 dfea5ec4f7f720734feb7b33130cec80d2225124 82370 optipng_0.7.6-1_amd64.deb
Checksums-Sha256:
 2f573057f3a086e42cc113bcfbbfe261ea64febc5ff7aa06827f3014d5c66b3d 1986 
optipng_0.7.6-1.dsc
 cd7eccd51f15c789e61041b3e03260e2886e74a274c9a6513a1f6db6cce07dc8 200670 
optipng_0.7.6.orig.tar.gz
 4beb4c16dc7af4370da95852dc6df23de30f783fbdd4c054dbc449002a530ae2 5045 
optipng_0.7.6-1.debian.tar.bz2
 12641220585e1e82abbfde28a3b37622c223fd9d98024b0944b783c68c0b3098 86936 
optipng-dbgsym_0.7.6-1_amd64.deb
 1599e8e48790e139c2c57075a8b0b27089ca7061ef5350d554b64a85758d1f2e 82370 
optipng_0.7.6-1_amd64.deb
Files:
 aa27c551da35e2cf5a2b532d14e3f709 1986 graphics optional optipng_0.7.6-1.dsc
 c36836166ec3b6a12a75600fdb73e6ce 200670 graphics optional 
optipng_0.7.6.orig.tar.gz
 064fd868647bc1be18f62b70b7c613fa 5045 graphics optional 
optipng_0.7.6-1.debian.tar.bz2
 a7e655d729e5ba7583a5f2eb53635489 86936 debug extra 
optipng-dbgsym_0.7.6-1_amd64.deb
 525301a013aa36c631812de052d9e034 82370 graphics optional 
optipng_0.7.6-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXCCDEAAoJEEsHdyOSnULDFNAP/i/VaIiHIfvE3i7IU6tdXxCQ
Ht1+Ej6iXKzAnF1aX4ejP3mPhtbfhFNA74ICmystkM8j1wWa+YBPQwJk7YiEekI9
ITNlDSnZcOkNJ4hOK5koQNPF94fIX5n4kjio/JcDKBPXChzQHw8WuU7okphIPlu6
CTGBGJWKXk1hllGQOAGO3yFj2T0AgVEVlxEgF3pWRj73UiAJ1QfRdzfV/p/NoP8k
jMb/PKfhhKbGfF/tDeGs86FWe6C1XID4T8V0OxVCNB6ZIK9FOlWVCtizfLcjQQpe
RtEcwzJtUUdHfHmc4lOcZkud/4b2ivNQHxamzXq97+iR3+xJjqaPLe8fzF4CXa+x
yw7tC3Mcne5nxc5zozhkzOpxn/JHgWaM4UBL

Bug#820439: marked as done (imview: FTBFS with libpng1.6)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 21:52:01 +
with message-id 
and subject line Bug#820439: fixed in imview 1.1.9c-13
has caused the Debian Bug report #820439,
regarding imview: FTBFS with libpng1.6
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.)


-- 
820439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imview
Severity: serious
Justification: FTBFS
Control: block 650601 by -1

Buildlog: 
https://buildd.debian.org/status/fetch.php?pkg=imview&arch=arm64&ver=1.1.9c-12%2Bb2&stamp=1460117919

Example snippet:

In file included from /usr/include/pngconf.h:50:0,
 from /usr/include/png.h:340,
 from readpng.cxx:57:
readpng.cxx: In function 'int readPNGImage(const char*, int)':
readpng.cxx:99:18: error: invalid use of incomplete type 'png_struct {aka 
struct png_struct_def}'
 if (setjmp(pp->jmpbuf))
^

I will try to comeup with an patch / NMU this weekend.


--
tobi

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: imview
Source-Version: 1.1.9c-13

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated imview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 08 Apr 2016 22:57:03 +0200
Source: imview
Binary: imview
Architecture: source
Version: 1.1.9c-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 imview - Image viewing and analysis application
Closes: 820439
Changes:
 imview (1.1.9c-13) unstable; urgency=medium
 .
   [ Anton Gladky ]
   * [d63a786] Apply cme fix dpkg.
   * [4800c3e] Enable use of buildflags.
 .
   [ Tobias Frost ]
   * [0f258fd] Fix for libpng1.6 (Closes: #820439)
Checksums-Sha1:
 9239ff2e12ab256f60cfd761fc449a8fe88f9cb2 2126 imview_1.1.9c-13.dsc
 1a7791ea3dc3473cb87241167b28e4f6ff465f29 29372 imview_1.1.9c-13.debian.tar.xz
Checksums-Sha256:
 85e4eab48d0992037650a5f89dd333b329234535efcd7ac038ca1a28ff8607d9 2126 
imview_1.1.9c-13.dsc
 d496ddcf8beb508f4c9c298c1c72cb7437383b75a1292d40ae6c0f2877c7ae81 29372 
imview_1.1.9c-13.debian.tar.xz
Files:
 8943107862c0d8fcf378c15d75ada285 2126 science optional imview_1.1.9c-13.dsc
 0e619f2ee238e00d97b0ea17c10cad3f 29372 science optional 
imview_1.1.9c-13.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXCBydAAoJENPhc4PPp/8GaAAP/iVmKgKiGbKt/dHDPoxoGQrq
VI1vBQxsqvCoSeo0mxQzCFL9kQ/VxcHjDz+YEYFy04h7YWi/J9D4OiBFtpQcdifG
7hLXIo41V/REQqQppoA5DO1xR9nPqtiKsWcdwNkR7VF8qCF7uU9BW9MN6tEJvN6u
FL7LK21alCzL9QnzJtwHMHVAPWWcWVcBLvcBXnq1ycbwC9rmXDYrvQzXby2EkyyL
wgwV1gsQGjQ5HrX2WfiSQ7r6ADQLEQVJlaorFq2Xl9vikV86m9chPybsol+Ev7L+
+MIXFOtTiqe/Iu+GZTioFzKAT/cVepvXNyeM33KGqZxjfGJWX7b6MEOk+ISFrNLx
ObvBkfnZvW/5k3fipYrOstOnFwlN1JALRYGhvQv/5u1HGrapDcnuKGsqsjjv3uOI
CfThVcNUk1DXBnSEuaPs3Vu6ZzGJgAiPhw59UnpSFVqcoZ5bZTK1CEQ3YL01ipcN
4Ee7WrwCObhBujB14JGHxnHzV0HEu4yXvqJ2opcN0oWCtCxjV2Y6fvEtvcAzviAa
/AXdovicxSbL5nejBaKR/6+2Atk/DFA6niV5jOYKFvJuciOaSpROfnTVUYiQJhGa
tMkxliGFmSxFd01xfJ8uVScKGsTYIjGxXA2YDBIpUoZcBgKIcpZWCzbAOPMByTk9
bezhuQSb3AXllS0BwbE9
=4+lm
-END PGP SIGNATURE End Message ---

Bug#820068: [Pkg-phototools-devel] Bug#820068: optipng: diff for NMU version 0.7.5-1.1

[Emmanuel Bouthenot]

Salvatore,

On Fri, Apr 08, 2016 at 07:19:35AM +0200, Salvatore Bonaccorso wrote:
[...]

> jessie-security upload. Better would be though to straight go to 0.7.6.
Thanks for your various feedbacks.

optipng 0.7.6 will be uploaded into unstable in a few minutes.

Regards,

M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}

Bug#804582: (no subject)

[Barry Warsaw]

Okay, so I think the locale changes are enough to fix the FTBFS.  I retried
building in an Ubuntu PPA and the build succeeded.

The timeout failure must just have been a problem with my local sbuild.

Processed: Bug#816983

[Debian Bug Tracking System]

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

> severity 816983 serious
Bug #816983 [src:nipy] nipy: FTBFS when built with dpkg-buildpackage -A (recipe 
for target 'test' failed)
Severity set to 'serious' from 'important'
> retitle 816983 nipy: FTBFS in testing
Bug #816983 [src:nipy] nipy: FTBFS when built with dpkg-buildpackage -A (recipe 
for target 'test' failed)
Changed Bug title to 'nipy: FTBFS in testing' from 'nipy: FTBFS when built with 
dpkg-buildpackage -A (recipe for target 'test' failed)'.
> thanks
Stopping processing here.

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

Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

[Peter Colberg]

On Fri, Apr 08, 2016 at 09:55:02PM +0200, Graham Inggs wrote:
> On 8 April 2016 at 21:16, Emilio Pozuelo Monfort  wrote:
> > Why did you switch to 3.8? The default in unstable is 3.6 and in 
> > experimental is
> > 3.7.
> 
> I understood there were severe performance regressions with Julia on
> LLVM > 3.3 that were only fixed in 3.8.

The reason for switching to LLVM 3.8 was the abysmal performance
of LLVM 3.7 on i386, and complete failure of LLVM 3.6 or earlier.

https://github.com/JuliaLang/julia/issues/14191

Peter

Bug#812823: utopia-documents: Segmentation fault on start

[Douglas Calvert]

Package: utopia-documents
Version: 2.4.4-2.1
Followup-For: Bug #812823

Ping?


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

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

Versions of packages utopia-documents depends on:
ii  libboost-python1.58.0 1.58.0+dfsg-5+b1
ii  libboost-system1.58.0 1.58.0+dfsg-5+b1
ii  libboost-thread1.58.0 1.58.0+dfsg-5+b1
ii  libc6 2.22-5
ii  libexpat1 2.1.1-1
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:5.3.1-13
ii  libgl1-mesa-glx [libgl1]  11.1.2-1
ii  libglew1.10   1.10.0-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libpcre3  2:8.38-3.1
ii  libpcrecpp0v5 2:8.38-3.1
ii  libpython2.7  2.7.11-7
ii  libqglviewer2 2.6.3+dfsg1-1
ii  libqjson0 0.8.1-3
ii  libqt4-network4:4.8.7+dfsg-6+b1
ii  libqt4-opengl 4:4.8.7+dfsg-6+b1
ii  libqt4-script 4:4.8.7+dfsg-6+b1
ii  libqt4-svg4:4.8.7+dfsg-6+b1
ii  libqt4-xml4:4.8.7+dfsg-6+b1
ii  libqtcore44:4.8.7+dfsg-6+b1
ii  libqtgui4 4:4.8.7+dfsg-6+b1
ii  libqtwebkit4  2.3.4.dfsg-6+b1
ii  libraptor11.4.21-11+b1
ii  libssl1.0.0   1.0.2d-1
ii  libstdc++65.3.1-13
ii  python-cssselect  0.9.1+git90c72b0-1
ii  python-imaging3.1.1-1
ii  python-lxml   3.6.0-1
ii  python-suds   0.7~git20150727.94664dd-3
ii  python2.7 2.7.11-7
pn  python:any
ii  xdg-utils 1.1.1-1
ii  zlib1g1:1.2.8.dfsg-2+b1

utopia-documents recommends no packages.

utopia-documents suggests no packages.

-- no debconf information

Bug#790423: marked as done (Fails to load xpms if mime cache folder is missing)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 19:44:25 +
with message-id 
and subject line Bug#790423: fixed in gdk-pixbuf 2.32.3-2
has caused the Debian Bug report #790423,
regarding Fails to load xpms if mime cache folder is missing
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.)


-- 
790423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icewm
Version: 1.3.8+githubmod+20150412+960629d-1
Severity: important

Hi,

IceWM does not display pixmaps/icons/graphics (window decorations,
start menu button, etc.) for me on some systems. I now found out
why: shared-mime-info must be installed for that to work.

Please either fix icewm to not require shared-mime-info, or add it
to Depends. (I fail to see why that package should be required for
graphics, so the former is actually the better option).

Also found as: https://bugs.launchpad.net/ubuntu/+source/icewm/+bug/1097192


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

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

Versions of packages icewm depends on:
ii  fonts-dejavu-core   2.35-1
ii  icewm-common1.3.8+githubmod+20150412+960629d-1
ii  libc6   2.19-18
ii  libesd0 0.2.41-11
ii  libfontconfig1  2.11.0-6.3
ii  libgcc1 1:5.1.1-12
ii  libgdk-pixbuf2.0-0  2.31.4-2
ii  libglib2.0-02.44.1-1.1
ii  libice6 2:1.0.9-1+b1
ii  libsm6  2:1.2.2-1+b1
ii  libx11-62:1.6.3-1
ii  libxext62:1.3.3-1
ii  libxft2 2.3.2-1
ii  libxinerama12:1.1.3-1+b1
ii  libxrandr2  2:1.4.2-1+b1
ii  ttf-dejavu-core 2.35-1

icewm recommends no packages.

icewm suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gdk-pixbuf
Source-Version: 2.32.3-2

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated gdk-pixbuf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Apr 2016 21:01:50 +0200
Source: gdk-pixbuf
Binary: libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0-dbg libgdk-pixbuf2.0-common 
libgdk-pixbuf2.0-dev libgdk-pixbuf2.0-doc libgdk-pixbuf2.0-0-udeb 
gir1.2-gdkpixbuf-2.0
Architecture: source
Version: 2.32.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-gdkpixbuf-2.0 - GDK Pixbuf library - GObject-Introspection
 libgdk-pixbuf2.0-0 - GDK Pixbuf library
 libgdk-pixbuf2.0-0-dbg - GDK Pixbuf library - debug symbols
 libgdk-pixbuf2.0-0-udeb - GDK Pixbuf library - minimal runtime (udeb)
 libgdk-pixbuf2.0-common - GDK Pixbuf library - data files
 libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files)
 libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation)
Closes: 790423 808332 818233
Changes:
 gdk-pixbuf (2.32.3-2) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * Add share-mime-info dependency (Closes: #790423)
   * Bump Standards-Version to 3.9.7
 .
   [ Tobias Frost ]
   * Move gtk-doc-tools to Build-Depends-Indep (Closes: #808332)
 .
   [ Emilio Pozuelo Monfort ]
   * debian/patches/01-disable-oom-test.patch:
 + Disable a test on kfreebsd and alpha that fails because it runs
   out of memory on those buildds. Closes: #818233.
Checksums-Sha1:
 c41451046f06dc0b3a25e0ac625523f0b9921b9f 2836 gdk-pixbuf_2.32.3-2.dsc
 d3085802c22dd259fb7d0dc11d48d7fb4af2d381 2430720 gdk-pixbuf_2.32.3.orig.tar.xz
 51d19571675ce1abb8aab75fae1b29a14974749e 12868 
gdk-pixbuf_2.32.3-2.debian.tar.xz
Checksums-Sha256:
 8d74c9de7ed4699da999e80e2ccc8ef47608f5f9c58b7b282c507948e93edf33 2836 
gdk-pixbuf_2.32.3-2.dsc
 2b6771f1ac72f687a8971e59810b8dc658e65e7d3086bd2e676

Processed: tagging 820439

[Debian Bug Tracking System]

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

> tags 820439 + stretch sid
Bug #820439 [imview] imview: FTBFS with libpng1.6
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#801170: marked as done (Missing dependency on shared-mime-info)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 19:44:25 +
with message-id 
and subject line Bug#790423: fixed in gdk-pixbuf 2.32.3-2
has caused the Debian Bug report #790423,
regarding Missing dependency on shared-mime-info
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.)


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

Hi,

to reproduce my problem, I prepared the following script which sets up a
minimal virtual machine image:

rm -f testimg
fallocate -l 10G testimg

sudo mkfs.ext4 testimg

ROOT=`mktemp -d`
sudo mount testimg "$ROOT"
sudo debootstrap --variant=minbase unstable "$ROOT" 
http://127.0.0.1:3142/httpredir.debian.org/debian
echo 'APT::Install-Recommends "0";' | sudo tee 
"$ROOT/etc/apt/apt.conf.d/99no-install-recommends" > /dev/null
cat << END | sudo tee "$ROOT/etc/kernel-img.conf" > /dev/null
link_in_boot = yes
do_symlinks = yes
relative_links = yes
END
cat << END | sudo tee "$ROOT/usr/sbin/policy-rc.d" > /dev/null
#!/bin/sh
echo "sysvinit: All runlevel operations denied by policy" >&2
exit 101
END
sudo chmod +x "$ROOT/usr/sbin/policy-rc.d"
cat << END | sudo tee "$ROOT/etc/fstab" > /dev/null
root / auto errors=remount-ro 0 1
END
sudo chroot "$ROOT" apt-get update
sudo chroot "$ROOT" apt-get -y install xserver-xorg xinit udev 
linux-image-amd64 sudo awesome xterm
sudo rm "$ROOT/usr/sbin/policy-rc.d"
sudo chroot "$ROOT" useradd --groups 
lp,dialout,cdrom,floppy,sudo,audio,video,plugdev --create-home --shell 
/bin/bash --uid 1000 --user-group josch
echo "josch:secret" | sudo chroot "$ROOT" chpasswd
cp -L "$ROOT"/boot/initrd.img .
cp -L "$ROOT"/boot/vmlinuz .
sudo umount "$ROOT" rm -r "$ROOT"


you can boot into the system by doing:




after logging in as user josch, password secret, you can run xinit to
get an X server together with an xterm. If you then start awesome from
within that xterm you will see the following error message:

error while running function
stack traceback:
[C]: in function 'load_image'
/usr/share/awesome/lib/gears/surface.lua:39: in function 

(tail call): ?
(tail call): ?
/usr/share/awesome/lib/gears/wallpaper.lua:128: in function 'maximized'
/etc/xdg/awesome/rc.lua:79: in main chunk
error: /usr/share/awesome/lib/gears/surface.lua:39: Couldn't recognize the 
image file format for file '/usr/share/awesome/themes/default/background.png'
E: awesome: main:535: couldn't find any rc file


as you can convince yourself, the system has libpng12-0:amd64 (=
1.2.50-2+b2) installed.

cheers, josch
--- End Message ---
--- Begin Message ---
Source: gdk-pixbuf
Source-Version: 2.32.3-2

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated gdk-pixbuf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Apr 2016 21:01:50 +0200
Source: gdk-pixbuf
Binary: libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0-dbg libgdk-pixbuf2.0-common 
libgdk-pixbuf2.0-dev libgdk-pixbuf2.0-doc libgdk-pixbuf2.0-0-udeb 
gir1.2-gdkpixbuf-2.0
Architecture: source
Version: 2.32.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-gdkpixbuf-2.0 - GDK Pixbuf library - GObject-Introspection
 libgdk-pixbuf2.0-0 - GDK Pixbuf library
 libgdk-pixbuf2.0-0-dbg - GDK Pixbuf library - debug symbols
 libgdk-pixbuf2.0-0-udeb - GDK Pixbuf library - minimal runtime (udeb)
 libgdk-pixbuf2.0-common - GDK Pixbuf library - data files
 libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files)
 libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation)
Closes: 790423 808332 818233
Changes:
 gdk-pixbuf (2.32.3-2) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * Add share-mime-info dependency (Closes: #790423)
   * Bump Standards-Version to 3.9.7
 .
   [ Tobias Frost ]
   * Move gtk-doc-tools to Build-Depend

Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

[Graham Inggs]

On 8 April 2016 at 21:16, Emilio Pozuelo Monfort  wrote:
> Why did you switch to 3.8? The default in unstable is 3.6 and in experimental 
> is
> 3.7.

I understood there were severe performance regressions with Julia on
LLVM > 3.3 that were only fixed in 3.8.

> I'm Cc'ing the arm and llvm lists, maybe they can give some hints.

Thanks.

I did ask on #debian-arm earlier today and was given some pointers by
suihkulokki.

Firstly, llvm-toolchain-3.8 hasn't actually built on armel yet [1], so
the julia build on armel is being attempted with llvm
1:3.8~svn247576-1 from llvm-toolchain-snapshot.

Secondly, it should be possible to reproduce the fault by building in
an armhf schroot on abel.d.o, which has the same hardware as the
buildds.  A temporary solution would be to upload armhf binaries built
on asachi.d.o.


[1] 
https://buildd.debian.org/status/package.php?p=llvm-toolchain-3.8&suite=unstable

Bug#800036: marked as done (ledgersmb: failing to install)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 19:46:05 +
with message-id 
and subject line Bug#800036: fixed in ledgersmb 1.3.47-1
has caused the Debian Bug report #800036,
regarding ledgersmb: failing to install
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.)


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

Dear Maintainer,
the installation of ledgersmb fails on a brand new install of jessie.
During install I answered both question if I want automatic configuration
and configuration of a database via dbconfig-common 'yes'.
previously I configured all local connection to Postgresql to "trust".
I left the password for ledgersmb blank (a rendom one will be created)
and the result is:
An error occurred while installing the database:
│ 
 │
│ 
 │ ERROR: syntax error at or near "#" LINE 1: # Configure ledgersmb user
permissions ^  ...

There are also a few other mistakes.
The initial apache2 install does not enable "RewriteEngine", so the
configuration of ledgersmb.conf will cause apache2 to not restart properly.

Also the default version of Postgresql in jessie is 9.4.
So most likely the configuration in /etc/ledgersmb/ledgersmb.conf
...
contrib_dir = /usr/share/postgresql/9.3/extension
...

is wrong too.





-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Henning Follmann   | hfollm...@itcfollmann.com
--- End Message ---
--- Begin Message ---
Source: ledgersmb
Source-Version: 1.3.47-1

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

Debian distribution maintenance software
pp.
Robert James Clay  (supplier of updated ledgersmb 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, 08 Apr 2016 11:15:15 -0400
Source: ledgersmb
Binary: ledgersmb
Architecture: source all
Version: 1.3.47-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LedgerSMB Team 

Changed-By: Robert James Clay 
Description:
 ledgersmb  - financial accounting and ERP program
Closes: 800036 819481
Changes:
 ledgersmb (1.3.47-1) unstable; urgency=medium
 .
   * New upstream release.
   * Changes to debian/control:
 - Set the Vcs-Browser URL to use 'https' instead of 'http'.
 - Set Standards-Version to 3.9.8, no package changes required.
 - Change texlive-xetex from 'Suggests' to 'Recommends' to work around 
issues
   with using liblatex-driver-perl needed for printing.
   * Changes to debian/copyright:
 - Add 'Nick Prater' copyright information.
 - Correct spelling of 'Portugese' to 'Portuguese'.
 - Update end years in debian/copyright as necessary.
   * Changes to debian/patches/*:
 - Create debian/patches/22_SpellingErrors.patch.
 - Add 'Origin: vendor' to the debian/patches/*.patch files.
 - Remove unneeded line 5 in debian/patches/20_BashPath.patch.
 - Refresh debian/patches/10_httpdconf.patch for updated package.
 - Set default for the 'contrib_dir' setting in 05_confdir.patch to be for
   v9.5 instead of v9.1.
   * Correct spelling of 'authorative' as 'authoritative' in the file
 debian/README.Debian.
   * Default to 'true' in debian/templates to automatically configure package.
   * Changes to debian/ledgersmb.preinst and debian/ledgersmb.postrm:
 - Update the package version to v1.3.18-2 that is being checked for in the
   ledgersmb apache config file renaming.
   * Changes to debian/ledgersmb.postinst:
 - Explicitly do 'db_stop' after operations with debconf have completed.
 - Rewrite how apache 2.4 modules are enabled and how the apache v2.2 
related
   configuration files are handled. (Closes: #800036, #819481, LP#1513691)
Checksums-Sha1:
 4e205edc012e667df0a3a22a999a71e2f98d6713 2023 ledgersmb_1.3.

Bug#820476: opensips: unsatisfiable dependency on db4.6-util

[Steve Langasek]

Package: opensips-berkeley-module
Version: 2.1.2-2
Severity: grave

The opensips package in Debian unstable builds an opensips-berkeley-module
binary package which is uninstallable, and this package will therefore not
migrate to testing or be eligible for inclusion in the Debian release.

The uninstallability is caused by a dependency on db4.6-util, which does not
exist in any supported Debian release.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#790925: 818501 may be related

[Diane Trout]

Hi,

I was looking through this bug and noticed the failure was in the HDF code.

This pytables bug might be related:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818501

The bug affected anything that used HDF indexes via pytables.

Diane

Bug#804582: (no subject)

[Barry Warsaw]

It's a locale problem.  This fixes most of the problems:

diff --git a/debian/rules b/debian/rules
index 9c04662..6130dc4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,8 @@
 #!/usr/bin/make -f
 
 export PYBUILD_NAME=paramiko
+export PYBUILD_VERBOSE=1
+export DH_VERBOSE=1
 
 %:
dh $@ --with python2,python3 --buildsystem=pybuild
@@ -11,3 +13,12 @@ ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS)))
 endif
dh_installdocs
 
+override_dh_auto_test:
+   mkdir -p $(CURDIR)/tmp-locales
+   localedef -i /usr/share/i18n/locales/en_US -c -f UTF-8 \
+ -A /usr/share/locale/locale.alias \
+ $(CURDIR)/tmp-locales/en_US.UTF-8
+   LOCPATH=$(CURDIR)/tmp-locales LC_ALL=en_US.UTF-8 \
+   dh_auto_test -- \
+   --system=custom \
+   --test-args='{interpreter} $(CURDIR)/test.py --verbose'


Unfortunately, I still have one last test I'm tracking down in python3.5
(python2.7 passes now):

==
FAIL: test_L_handshake_timeout (tests.test_transport.TransportTest)
--
Traceback (most recent call last):
  File "/<>/tests/test_transport.py", line 811, in 
test_L_handshake_timeout
password='pygmalion')
AssertionError: EOFError not raised by connect

Bug#820068: optipng: diff for NMU version 0.7.5-1.1

[Salvatore Bonaccorso]

Hi

The used patch took into account as well the fixed from upstream bugs
56 and 57, which correspond to CVE-2016-3981 and CVE-2016-3982. At the
time of writing those two CVEs were not yet assigned.

So once accepted into the archive, I will update as well the
information for those CVEs.

Regards,
Salvatore

Bug#782735: marked as done (kfreebsd-9: CVE-2015-2923: IPv6 Hop limit lowering via RA messages)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 18:18:54 +
with message-id 
and subject line Bug#782735: fixed in kfreebsd-9 9.0-10+deb70.10
has caused the Debian Bug report #782735,
regarding kfreebsd-9: CVE-2015-2923: IPv6 Hop limit lowering via RA messages
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.)


-- 
782735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.1~svn274115-3
Severity: grave
Tags: security

Hi,

A local-network DoS was reported in the IPv6 stack of FreeBSD:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:09.ipv6.asc
(the same issue as CVE-2015-2922 on Linux).

This affects all our kfreebsd-8, -9, -10 and -11 packages.

Debian GNU/kFreeBSD packages enable "accept_rtadv" by default, so are
vulnerable to this DoS unless that flag is manually disabled on an
interface, or IPv6 connectivity not used.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: kfreebsd-9
Source-Version: 9.0-10+deb70.10

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

Debian distribution maintenance software
pp.
Steven Chamberlain  (supplier of updated kfreebsd-9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Apr 2015 21:45:05 +
Source: kfreebsd-9
Binary: kfreebsd-source-9.0 kfreebsd-headers-9.0-2 kfreebsd-image-9.0-2-686-smp 
kfreebsd-image-9-686-smp kfreebsd-headers-9.0-2-686-smp 
kfreebsd-headers-9-686-smp kfreebsd-image-9.0-2-amd64 kfreebsd-image-9-amd64 
kfreebsd-headers-9.0-2-amd64 kfreebsd-headers-9-amd64 
kernel-image-9.0-2-amd64-di nic-modules-9.0-2-amd64-di 
nic-wireless-modules-9.0-2-amd64-di nic-shared-modules-9.0-2-amd64-di 
serial-modules-9.0-2-amd64-di ppp-modules-9.0-2-amd64-di 
cdrom-modules-9.0-2-amd64-di scsi-core-modules-9.0-2-amd64-di 
scsi-modules-9.0-2-amd64-di scsi-extra-modules-9.0-2-amd64-di 
plip-modules-9.0-2-amd64-di floppy-modules-9.0-2-amd64-di 
loop-modules-9.0-2-amd64-di ipv6-modules-9.0-2-amd64-di 
nls-core-modules-9.0-2-amd64-di ext2-modules-9.0-2-amd64-di 
isofs-modules-9.0-2-amd64-di ntfs-modules-9.0-2-amd64-di 
reiserfs-modules-9.0-2-amd64-di xfs-modules-9.0-2-amd64-di 
fat-modules-9.0-2-amd64-di zfs-modules-9.0-2-amd64-di 
nfs-modules-9.0-2-amd64-di nullfs-modules-9.0-2-amd64-di
 md-modules-9.0-2-amd64-di parport-modules-9.0-2-amd64-di 
sata-modules-9.0-2-amd64-di acpi-modules-9.0-2-amd64-di 
i2c-modules-9.0-2-amd64-di crypto-modules-9.0-2-amd64-di 
crypto-dm-modules-9.0-2-amd64-di mmc-core-modules-9.0-2-amd64-di 
mmc-modules-9.0-2-amd64-di sound-modules-9.0-2-amd64-di 
zlib-modules-9.0-2-amd64-di kfreebsd-image-9.0-2-486 kfreebsd-image-9-486 
kfreebsd-headers-9.0-2-486 kfreebsd-headers-9-486 kfreebsd-image-9.0-2-686 
kfreebsd-image-9-686 kfreebsd-headers-9.0-2-686 kfreebsd-headers-9-686 
kfreebsd-image-9.0-2-xen kfreebsd-image-9-xen kfreebsd-headers-9.0-2-xen 
kfreebsd-headers-9-xen kernel-image-9.0-2-486-di nic-modules-9.0-2-486-di 
nic-wireless-modules-9.0-2-486-di nic-shared-modules-9.0-2-486-di 
serial-modules-9.0-2-486-di ppp-modules-9.0-2-486-di cdrom-modules-9.0-2-486-di 
scsi-core-modules-9.0-2-486-di scsi-modules-9.0-2-486-di 
scsi-extra-modules-9.0-2-486-di plip-modules-9.0-2-486-di 
floppy-modules-9.0-2-486-di loop-modules-9.0-2-486-di
 ipv6-modules-9.0-2-486-di nls-core-modules-9.0-2-486-di 
ext2-modules-9.0-2-486-di isofs-modules-9.0-2-486-di ntfs-modules-9.0-2-486-di 
reiserfs-modules-9.0-2-486-di xfs-modules-9.0-2-486-di fat-modules-9.0-2-486-di 
zfs-modules-9.0-2-486-di nfs-modules-9.0-2-486-di nullfs-modules-9.0-2-486-di 
md-modules-9.0-2-486-di parport-modules-9.0-2-486-di sata-modules-9.0-2-486-di 
acpi-modules-9.0-2-486-di i2c-modules-9.0-2-486-di crypto-modu

Bug#779201: marked as done (kfreebsd-9: CVE-2015-1414: DoS via IGMP packet)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 18:18:31 +
with message-id 
and subject line Bug#779201: fixed in kfreebsd-9 9.0-10+deb70.9
has caused the Debian Bug report #779201,
regarding kfreebsd-9: CVE-2015-1414: DoS via IGMP packet
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.)


-- 
779201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.1~svn274115-2
Severity: grave
Tags: security upstream patch

Hi,

A remote DoS was reported in FreeBSD's IGMP packet handling:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:04.igmp.asc

This affects all our kfreebsd-8, -9, -10 and -11 packages.

I don't know yet if this can be exploited over the public Internet
or only on a local network segment.

As a mitigation, the PF firewall can probably be configured to block
'proto igmp' packets before the kernel processes them.  

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: kfreebsd-9
Source-Version: 9.0-10+deb70.9

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

Debian distribution maintenance software
pp.
Christoph Egger  (supplier of updated kfreebsd-9 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: Wed, 25 Feb 2015 14:08:57 +0100
Source: kfreebsd-9
Binary: kfreebsd-source-9.0 kfreebsd-headers-9.0-2 kfreebsd-image-9.0-2-686-smp 
kfreebsd-image-9-686-smp kfreebsd-headers-9.0-2-686-smp 
kfreebsd-headers-9-686-smp kfreebsd-image-9.0-2-amd64 kfreebsd-image-9-amd64 
kfreebsd-headers-9.0-2-amd64 kfreebsd-headers-9-amd64 
kernel-image-9.0-2-amd64-di nic-modules-9.0-2-amd64-di 
nic-wireless-modules-9.0-2-amd64-di nic-shared-modules-9.0-2-amd64-di 
serial-modules-9.0-2-amd64-di ppp-modules-9.0-2-amd64-di 
cdrom-modules-9.0-2-amd64-di scsi-core-modules-9.0-2-amd64-di 
scsi-modules-9.0-2-amd64-di scsi-extra-modules-9.0-2-amd64-di 
plip-modules-9.0-2-amd64-di floppy-modules-9.0-2-amd64-di 
loop-modules-9.0-2-amd64-di ipv6-modules-9.0-2-amd64-di 
nls-core-modules-9.0-2-amd64-di ext2-modules-9.0-2-amd64-di 
isofs-modules-9.0-2-amd64-di ntfs-modules-9.0-2-amd64-di 
reiserfs-modules-9.0-2-amd64-di xfs-modules-9.0-2-amd64-di 
fat-modules-9.0-2-amd64-di zfs-modules-9.0-2-amd64-di 
nfs-modules-9.0-2-amd64-di nullfs-modules-9.0-2-amd64-di
 md-modules-9.0-2-amd64-di parport-modules-9.0-2-amd64-di 
sata-modules-9.0-2-amd64-di acpi-modules-9.0-2-amd64-di 
i2c-modules-9.0-2-amd64-di crypto-modules-9.0-2-amd64-di 
crypto-dm-modules-9.0-2-amd64-di mmc-core-modules-9.0-2-amd64-di 
mmc-modules-9.0-2-amd64-di sound-modules-9.0-2-amd64-di 
zlib-modules-9.0-2-amd64-di kfreebsd-image-9.0-2-486 kfreebsd-image-9-486 
kfreebsd-headers-9.0-2-486 kfreebsd-headers-9-486 kfreebsd-image-9.0-2-686 
kfreebsd-image-9-686 kfreebsd-headers-9.0-2-686 kfreebsd-headers-9-686 
kfreebsd-image-9.0-2-xen kfreebsd-image-9-xen kfreebsd-headers-9.0-2-xen 
kfreebsd-headers-9-xen kernel-image-9.0-2-486-di nic-modules-9.0-2-486-di 
nic-wireless-modules-9.0-2-486-di nic-shared-modules-9.0-2-486-di 
serial-modules-9.0-2-486-di ppp-modules-9.0-2-486-di cdrom-modules-9.0-2-486-di 
scsi-core-modules-9.0-2-486-di scsi-modules-9.0-2-486-di 
scsi-extra-modules-9.0-2-486-di plip-modules-9.0-2-486-di 
floppy-modules-9.0-2-486-di loop-modules-9.0-2-486-di
 ipv6-modules-9.0-2-486-di nls-core-modules-9.0-2-486-di 
ext2-modules-9.0-2-486-di isofs-modules-9.0-2-486-di ntfs-modules-9.0-2-486-di 
reiserfs-modules-9.0-2-486-di xfs-modules-9.0-2-486-di fat-modules-9.0-2-486-di 
zfs-modules-9.0-2-486-di nfs-modules-9.0-2-486-di nullfs-modules-9.0-2-486-di 
md-modules-9.0-2-486-di parport-modules-9.0-2-486-di sata-modules-9.0-2-486-di 
acpi-modules-9.0-2-486-di i2c-modules-9.0-2-486-di crypto-modules-9

Bug#779201: marked as done (kfreebsd-9: CVE-2015-1414: DoS via IGMP packet)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 18:18:54 +
with message-id 
and subject line Bug#779201: fixed in kfreebsd-9 9.0-10+deb70.10
has caused the Debian Bug report #779201,
regarding kfreebsd-9: CVE-2015-1414: DoS via IGMP packet
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.)


-- 
779201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.1~svn274115-2
Severity: grave
Tags: security upstream patch

Hi,

A remote DoS was reported in FreeBSD's IGMP packet handling:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:04.igmp.asc

This affects all our kfreebsd-8, -9, -10 and -11 packages.

I don't know yet if this can be exploited over the public Internet
or only on a local network segment.

As a mitigation, the PF firewall can probably be configured to block
'proto igmp' packets before the kernel processes them.  

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: kfreebsd-9
Source-Version: 9.0-10+deb70.10

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

Debian distribution maintenance software
pp.
Steven Chamberlain  (supplier of updated kfreebsd-9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Apr 2015 21:45:05 +
Source: kfreebsd-9
Binary: kfreebsd-source-9.0 kfreebsd-headers-9.0-2 kfreebsd-image-9.0-2-686-smp 
kfreebsd-image-9-686-smp kfreebsd-headers-9.0-2-686-smp 
kfreebsd-headers-9-686-smp kfreebsd-image-9.0-2-amd64 kfreebsd-image-9-amd64 
kfreebsd-headers-9.0-2-amd64 kfreebsd-headers-9-amd64 
kernel-image-9.0-2-amd64-di nic-modules-9.0-2-amd64-di 
nic-wireless-modules-9.0-2-amd64-di nic-shared-modules-9.0-2-amd64-di 
serial-modules-9.0-2-amd64-di ppp-modules-9.0-2-amd64-di 
cdrom-modules-9.0-2-amd64-di scsi-core-modules-9.0-2-amd64-di 
scsi-modules-9.0-2-amd64-di scsi-extra-modules-9.0-2-amd64-di 
plip-modules-9.0-2-amd64-di floppy-modules-9.0-2-amd64-di 
loop-modules-9.0-2-amd64-di ipv6-modules-9.0-2-amd64-di 
nls-core-modules-9.0-2-amd64-di ext2-modules-9.0-2-amd64-di 
isofs-modules-9.0-2-amd64-di ntfs-modules-9.0-2-amd64-di 
reiserfs-modules-9.0-2-amd64-di xfs-modules-9.0-2-amd64-di 
fat-modules-9.0-2-amd64-di zfs-modules-9.0-2-amd64-di 
nfs-modules-9.0-2-amd64-di nullfs-modules-9.0-2-amd64-di
 md-modules-9.0-2-amd64-di parport-modules-9.0-2-amd64-di 
sata-modules-9.0-2-amd64-di acpi-modules-9.0-2-amd64-di 
i2c-modules-9.0-2-amd64-di crypto-modules-9.0-2-amd64-di 
crypto-dm-modules-9.0-2-amd64-di mmc-core-modules-9.0-2-amd64-di 
mmc-modules-9.0-2-amd64-di sound-modules-9.0-2-amd64-di 
zlib-modules-9.0-2-amd64-di kfreebsd-image-9.0-2-486 kfreebsd-image-9-486 
kfreebsd-headers-9.0-2-486 kfreebsd-headers-9-486 kfreebsd-image-9.0-2-686 
kfreebsd-image-9-686 kfreebsd-headers-9.0-2-686 kfreebsd-headers-9-686 
kfreebsd-image-9.0-2-xen kfreebsd-image-9-xen kfreebsd-headers-9.0-2-xen 
kfreebsd-headers-9-xen kernel-image-9.0-2-486-di nic-modules-9.0-2-486-di 
nic-wireless-modules-9.0-2-486-di nic-shared-modules-9.0-2-486-di 
serial-modules-9.0-2-486-di ppp-modules-9.0-2-486-di cdrom-modules-9.0-2-486-di 
scsi-core-modules-9.0-2-486-di scsi-modules-9.0-2-486-di 
scsi-extra-modules-9.0-2-486-di plip-modules-9.0-2-486-di 
floppy-modules-9.0-2-486-di loop-modules-9.0-2-486-di
 ipv6-modules-9.0-2-486-di nls-core-modules-9.0-2-486-di 
ext2-modules-9.0-2-486-di isofs-modules-9.0-2-486-di ntfs-modules-9.0-2-486-di 
reiserfs-modules-9.0-2-486-di xfs-modules-9.0-2-486-di fat-modules-9.0-2-486-di 
zfs-modules-9.0-2-486-di nfs-modules-9.0-2-486-di nullfs-modules-9.0-2-486-di 
md-modules-9.0-2-486-di parport-modules-9.0-2-486-di sata-modules-9.0-2-486-di 
acpi-modules-9.0-2-486-di i2c-modules-9.0-2-486-di crypto-modu

Bug#820061: marked as done (linux-image-amd64: kernel hangs since debian 8.4)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 18:17:22 +
with message-id 
and subject line Bug#819881: fixed in linux 3.16.7-ckt25-2
has caused the Debian Bug report #819881,
regarding linux-image-amd64: kernel hangs since debian 8.4
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.)


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

Hi,

Since yesterday (update to debian 8.4) some PC at work, hangs randomly.

All the machines freeze when reading e-mails, searching things online, reading
PDF, lauching PHP Storm, etc ...

All the machines are from Dell (tested on Dell 990 and Dell 9010).

They are all equiped with a SSD disk.

Updating to linux-image-4.4.0-0.bpo.1-amd64 seems to resolve the issue.

I found this in /var/log/syslog :


Apr  4 18:52:55 pci003-01 kernel: [   79.316412] BUG: unable to handle kernel
NULL pointer dereference at 0008
Apr  4 18:52:55 pci003-01 kernel: [   79.317910] IP: []
radeon_fence_ref+0xd/0x50 [radeon]
Apr  4 18:52:55 pci003-01 kernel: [   79.318687] PGD 0
Apr  4 18:52:55 pci003-01 kernel: [   79.319445] Oops: 0002 [#1] SMP
Apr  4 18:52:55 pci003-01 kernel: [   79.320209] Modules linked in: md4 hmac
nls_utf8 cifs dns_resolver pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O)
vboxdrv(O) cpufreq_stats cpufreq_userspace cpufreq_conservative
cpufreq_powersave nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache
sunrpc snd_pcm_oss snd_mixer_oss fuse joydev x86_pkg_temp_thermal
intel_powerclamp intel_rapl coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support
crc32_pclmul evdev snd_hda_codec_realtek snd_hda_codec_generic aesni_intel
aes_x86_64 radeon lrw gf128mul glue_helper dcdbas ablk_helper cryptd ttm
drm_kms_helper pcspkr serio_raw drm i2c_i801 i2c_algo_bit i2c_core lpc_ich
snd_hda_intel mfd_core snd_hda_controller snd_hda_codec snd_hwdep snd_pcm
snd_timer tpm_tis snd tpm soundcore mei_me mei button shpchp video processor
thermal_sys parport_pc ppdev lp parport autofs4 hid_generic usbhid hid ext4
crc16 mbcache jbd2 raid1 md_mod sg sr_mod sd_mod cdrom crc_t10dif
crct10dif_generic crct10dif_pclmul crct10dif_common crc32c_intel psmouse ahci
libahci ehci_pci ehci_hcd libata scsi_mod e1000e usbcore ptp usb_common
pps_core
Apr  4 18:52:55 pci003-01 kernel: [   79.326413] CPU: 3 PID: 1604 Comm: Xorg
Tainted: G   O  3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-1
Apr  4 18:52:55 pci003-01 kernel: [   79.327346] Hardware name: Dell Inc.
OptiPlex 990/06D7TR, BIOS A19 08/26/2015
Apr  4 18:52:55 pci003-01 kernel: [   79.328278] task: 8802216c0a20 ti:
88003639c000 task.ti: 88003639c000
Apr  4 18:52:55 pci003-01 kernel: [   79.329223] RIP: 0010:[]
[] radeon_fence_ref+0xd/0x50 [radeon]
Apr  4 18:52:55 pci003-01 kernel: [   79.330192] RSP: 0018:88003639fb18
EFLAGS: 00010292
Apr  4 18:52:55 pci003-01 kernel: [   79.331154] RAX:  RBX:
8802218f55f8 RCX: 8802218f4d08
Apr  4 18:52:55 pci003-01 kernel: [   79.332125] RDX: 0001 RSI:
 RDI: 
Apr  4 18:52:55 pci003-01 kernel: [   79.333110] RBP: 8802218f5550 R08:
8802218f4000 R09: 
Apr  4 18:52:55 pci003-01 kernel: [   79.334119] R10: 0002 R11:
88003639fe08 R12: 0020
Apr  4 18:52:55 pci003-01 kernel: [   79.335117] R13: 88003639fbe0 R14:
88003639fbb0 R15: 8802218f55f8
Apr  4 18:52:55 pci003-01 kernel: [   79.336120] FS:  7fd8f5323980()
GS:88022dc6() knlGS:
Apr  4 18:52:55 pci003-01 kernel: [   79.337143] CS:  0010 DS:  ES: 
CR0: 80050033
Apr  4 18:52:55 pci003-01 kernel: [   79.338142] CR2: 0008 CR3:
000223b3e000 CR4: 000407e0
Apr  4 18:52:55 pci003-01 kernel: [   79.339125] Stack:
Apr  4 18:52:55 pci003-01 kernel: [   79.340065]  a04900bc
0020 eea00100 88003639fcd0
Apr  4 18:52:55 pci003-01 kernel: [   79.341006]  8802218f4000
8802216c0a20 8802216c0a20 0001
Apr  4 18:52:55 pci003-01 kernel: [   79.341952]  
  
Apr  4 18:52:55 pci003-01 kernel: [   79.342899] Call Trace:
Apr  4 18:52:55 pci003-01 kernel: [   79.343854]  [] ?
radeon_sa_bo_new+0x25c/0x460 [radeon]
Apr  4 18:52:55 pci003-01 kernel: [   79.344808]  [] ?
radeon_ib_get+0x2e/0xd0 [radeon]
Apr  4 18:52:55 pci003-01 kernel: [   79.345758]  [] ?
radeon_cs_ioctl+0x13c/0x730 [radeon]
Apr  4 18:52:55 pci003-01 kern

Bug#799724: marked as done (cyrus-replication broken / wrong connection)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 18:17:10 +
with message-id 
and subject line Bug#799724: fixed in cyrus-imapd-2.4 2.4.17+nocaldav-0~deb8u1
has caused the Debian Bug report #799724,
regarding cyrus-replication broken / wrong connection
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.)


-- 
799724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-replication
Version: 2.4.17+caldav~beta10-18
Severity: grave
Justification: renders package unusable



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

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

Versions of packages cyrus-replication depends on:
ii  cyrus-common  2.4.17+caldav~beta10-18
ii  cyrus-imapd   2.4.17+caldav~beta10-18
ii  dpkg  1.17.25
ii  libc6 2.19-18
ii  libcomerr21.42.12-1.1
ii  libdb5.3  5.3.28-9
ii  libical1a 1.0-1.3
ii  libkrb5-3 1.12.1+dfsg-19
ii  libsasl2-22.1.26.dfsg1-13
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libssl1.0.0   1.0.1k-3
ii  libwrap0  7.6.q-25
ii  zlib1g1:1.2.8.dfsg-2+b1

cyrus-replication recommends no packages.

cyrus-replication suggests no packages.

-- no debconf information

I am trying to sync (replicate) IMAP-Storage between an Gentoo and a
Debian 8 system.
Master is a Gentoo cyrus imap 2.4.17, Debian is the replica aka slave system.
syncserver in Debian 8 is configured in /etc/cyrus.conf as

syncserver  cmd="/usr/lib/cyrus/bin/sync_server" listen="2005"

and listens. However, connecting via netcat shows the follwing answer

root@debian:~# netcat localhost 2005
* OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE AUTH=DIGEST-MD5 AUTH=NTLM 
AUTH=CRAM-MD5 AUTH=PLAIN AUTH=LOGIN SASL-IR] debian 
Cyrus IMAP v2.4.17-caldav-beta10-Debian-2.4.17+caldav~beta10-18 server ready


This is wrong ! This is the answer of the standard IMAP-Service.
In Debian 7 and on Gentoo the answer is
root@debian:~# netcat localhost 2005
* SASL DIGEST-MD5 CRAM-MD5 NTLM LOGIN
* COMPRESS DELETE
* OK debian Cyrus sync server v2.4.16-Debian-2.4.16-4+deb7u2

wich is expected. I am running the config beetween Debian 7 and Gentoo
for a long time now, and it ever worked.
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd-2.4
Source-Version: 2.4.17+nocaldav-0~deb8u1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated cyrus-imapd-2.4 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: Wed, 30 Dec 2015 15:29:16 +0100
Source: cyrus-imapd-2.4
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder 
cyrus-replication cyrus-nntpd cyrus-clients cyrus-dev libcyrus-imap-perl 
cyrus-common-2.4 cyrus-doc-2.4 cyrus-imapd-2.4 cyrus-pop3d-2.4 cyrus-admin-2.4 
cyrus-murder-2.4 cyrus-replication-2.4 cyrus-nntpd-2.4 cyrus-clients-2.4 
cyrus-dev-2.4 libcyrus-imap-perl24
Architecture: source amd64 all
Version: 2.4.17+nocaldav-0~deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Debian Cyrus Team 

Changed-By: Ondřej Surý 
Description:
 cyrus-admin - Cyrus mail system - administration tools
 cyrus-admin-2.4 - Cyrus mail system - administration tools [dummy package]
 cyrus-clients - Cyrus mail system - test clients
 cyrus-clients-2.4 - Cyrus mail system - test clients [dummy package]
 cyrus-common - Cyrus mail system - common files
 cyrus-common-2.4 - Cyrus mail system - common files [dummy package]
 cyrus-dev  - Cyrus mail system - developer files
 cyrus-dev-2.4 - Cyrus mail system - developer files [dummy package]
 cyrus-doc  - Cyrus mail system - documentation files
 cyrus-doc-2.4 - Cyrus mail system - documentation files [dummy package]
 cyrus-imapd - Cyrus mail system - IMAP support
 cyrus-imapd-2.4

Bug#743388: marked as done (t4kcommon: FTBFS with libpng 1.6)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 17:10:02 +
with message-id 
and subject line Bug#743388: fixed in t4kcommon 0.1.1-1.1
has caused the Debian Bug report #743388,
regarding t4kcommon: FTBFS with libpng 1.6
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.)


-- 
743388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source:  t4kcommon
Version: 0.1.1-1
User: lib...@packages.debian.org
Usertags: libpng15-transition

Hi,

libpng maintainers have a plan transition of libpng16[0].

libpng16 is already installed in experimental, and we are re-building
the package depending on libpng16.
As a result, we checked that your package was FTBFS.
Would you check also in your environment?

-

t4k_loaders.c: In function 'saveSVGInfo':
t4k_loaders.c:841:7: warning: variable 'ret' set but not used
[-Wunused-but-set-variable]
   int ret = 0;
   ^
t4k_loaders.c: In function 'do_png_save':
t4k_loaders.c:1031:17: error: dereferencing pointer to incomplete type
 info_ptr->width = surf->w;
 ^
t4k_loaders.c:1032:17: error: dereferencing pointer to incomplete type
 info_ptr->height = surf->h;
 ^
t4k_loaders.c:1033:17: error: dereferencing pointer to incomplete type
 info_ptr->bit_depth = 8;
 ^
t4k_loaders.c:1034:17: error: dereferencing pointer to incomplete type
 info_ptr->color_type = PNG_COLOR_TYPE_RGB_ALPHA;
 ^
t4k_loaders.c:1035:17: error: dereferencing pointer to incomplete type
 info_ptr->interlace_type = 1;
 ^
t4k_loaders.c:1036:17: error: dereferencing pointer to incomplete type
 info_ptr->valid = 0; /* will be updated by various
png_set_FOO() functions */
 ^
-

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
--- End Message ---
--- Begin Message ---
Source: t4kcommon
Source-Version: 0.1.1-1.1

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated t4kcommon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Apr 2016 21:11:17 +0200
Source: t4kcommon
Binary: libt4k-common0 libt4k-common0-dev
Architecture: source
Version: 0.1.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Holger Levsen 
Changed-By: Tobias Frost 
Description:
 libt4k-common0 - common library for tux4kids
 libt4k-common0-dev - common library for tux4kids - development files
Closes: 743388
Changes:
 t4kcommon (0.1.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS against new libpng1.6 API. Patch from BTS (Closes: #743388)
   * Add explicit B-D against libpng-dev (to avoid that we miss it again the
 next transition)
Checksums-Sha1:
 0739a6fc56793770ede901c40080d23bbb4db931 2137 t4kcommon_0.1.1-1.1.dsc
 e238eb46abac1c8fa5d65cd91282a5cc9d51dfd5 4552 t4kcommon_0.1.1-1.1.debian.tar.xz
Checksums-Sha256:
 ad4467d7625892f9b883e122216cb870cd396ee11565203a369d7a87537e5c3c 2137 
t4kcommon_0.1.1-1.1.dsc
 a50b29799963d834666f62b713d272d6a36951de2311412c1f8df5f41b18bc7c 4552 
t4kcommon_0.1.1-1.1.debian.tar.xz
Files:
 f49c3862ae73c422a167e21e402479a3 2137 libs optional t4kcommon_0.1.1-1.1.dsc
 497b97e29018728f9ab8248b8668910d 4552 libs optional 
t4kcommon_0.1.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXBrJcAAoJEJFk+h0XvV02YGMP/3M7vIRKIC1Sqpd8GoSgdeOR
e2beP87jK+7vF1aMyvwD7ArL18+y1tsevJLof7wNUWZgWr1UbSsGZjdwI7G2pF8c
zHRV73g7VfL1xYTHBBJ+e8vM5WKpBjAL8d84hkACjSb8wkwK/CbihaArWEbrAI03
ttS/Zt4UlZeBQjWeCa15DOntgmeD7tV5dypsdoUQWbqbAlCJk0hUD2yAqFvsljHF
1TMO9VfC3UMMdPFdk2f1vWzAS96D0xgyofpZki7bj45JUZKvilJoxzBdn5eLKPKI
Ln+1MShrHW8+cjZ4RMNyyKAT1ZP7QijpbratWzl+1Ca3Y6b5DrITYqRyzUTajxz/
nngFMmJTUTWiZdhv8gY5OSnFcAGsvDY/MO8fgKZbTS1pNb5ACsIK61FBkT3eUpFd
j2WeiVSDkH8TDoM80xTk8yl1w1VlRKvVwRhjIGkgDzjNRM0PEOBI2CkHUdS2663v
zddfM9UfBKCCDbxRUeXW95PpiI7BxWul4D3mxDCv4EpVwS6BOl+

Bug#820464: linux-headers-4.4.0-1-grsec-amd64: missing scripts/Makefile.gcc-plugins

[Andreas Beckmann]

Package: linux-headers-4.4.0-1-grsec-amd64
Version: 4.4.6-1+grsec201604021734+1
Severity: serious
Justification: fails to build from source

Hi,

external modules cannot be built against the 4.4.0-1-grsec-amd64 kernel
(but this worked for 4.3.0-1-grsec-amd64):

DKMS make.log for r8168-8.041.01 for kernel 4.4.0-1-grsec-amd64 (x86_64)
Fri Apr  8 16:54:52 UTC 2016
make: Entering directory '/usr/src/linux-headers-4.4.0-1-grsec-amd64'
/usr/src/linux-headers-4.4.0-1-common-grsec/Makefile:625: 
scripts/Makefile.gcc-plugins: No such file or directory
make[2]: *** No rule to make target 'scripts/Makefile.gcc-plugins'.  Stop.
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.4.0-1-grsec-amd64'


Andreas

Bug#820062: marked as done (building only arch:all packages broken: orthanc-doc contains everything)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 16:48:04 +
with message-id 
and subject line Bug#820062: fixed in orthanc 1.0.0+dfsg-3
has caused the Debian Bug report #820062,
regarding building only arch:all packages broken: orthanc-doc contains 
everything
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.)


-- 
820062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: orthanc-doc,orthanc
Version: orthanc-doc/1.0.0+dfsg-1
Version: orthanc/1.0.0+dfsg-1+b1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-04-05
Architecture: amd64
Distribution: sid

Hi,

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



Extracting templates from packages: 65%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libwrap0:amd64.
(Reading database ... 10944 files and directories currently installed.)
Preparing to unpack .../libwrap0_7.6.q-25_amd64.deb ...
Unpacking libwrap0:amd64 (7.6.q-25) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-13_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-13) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up gcc-5-base:amd64 (5.3.1-13) ...
(Reading database ... 10963 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-13_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-13) over (4.8.2-19) ...
Processing triggers for libc-bin (2.22-5) ...
Setting up libstdc++6:amd64 (5.3.1-13) ...
Processing triggers for libc-bin (2.22-5) ...
Selecting previously unselected package libcharls1:amd64.
(Reading database ... 10977 files and directories currently installed.)
Preparing to unpack .../libcharls1_1.0-6_amd64.deb ...
Unpacking libcharls1:amd64 (1.0-6) ...
Selecting previously unselected package libjbig0:amd64.
Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
Unpacking libjbig0:amd64 (2.1-3.1) ...
Selecting previously unselected package libssl1.0.2:amd64.
Preparing to unpack .../libssl1.0.2_1.0.2g-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2g-1) ...
Selecting previously unselected package libdb5.3:amd64.
Preparing to unpack .../libdb5.3_5.3.28-11_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-11) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.6.5-2_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.5-2) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libnettle6:amd64.
Preparing to unpack .../libnettle6_3.2-1_amd64.deb ...
Unpacking libnettle6:amd64 (3.2-1) ...
Selecting previously unselected package libhogweed4:amd64.
Preparing to unpack .../libhogweed4_3.2-1_amd64.deb ...
Unpacking libhogweed4:amd64 (3.2-1) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Preparing to unpack .../libp11-kit0_0.23.2-3_amd64.deb ...
Unpacking libp11-kit0:amd64 (0.23.2-3) over (0.18.5-3) ...
Selecting previously unselected package libtasn1-6:amd64.
Preparing to unpack .../libtasn1-6_4.7-3_amd64.deb ...
Unpacking libtasn1-6:amd64 (4.7-3) ...
Selecting previously unselected package libgnutls30:amd64.
Preparing to unpack .../libgnutls30_3.4.10-4_amd64.deb ...
Unpacking libgnutls30:amd64 (3.4.10-4) ...
Selecting previously unselected package libkeyutils1:amd64.
Preparing to unpack .../libkeyutils1_1.5.9-8_amd64.deb ...
Unpacking libkeyutils1:amd64 (1.5.9-8) ...
Selecting previously unselected package libkrb5support0:amd64.
Preparing to unpack .../libkrb5support0_1.13.2+dfsg-5_amd64.deb ...
Unpacking libkrb5support0:amd64 (1.13.2+dfsg-5) ...
Selecting previously unselected package libk5crypto3:amd64.
Preparing to unpack .../libk5crypto3_1.13.2+dfsg-5_amd64.deb ...
Unpacking libk5crypto3:amd64 (1.13.2+dfsg-5) ...
Selecting previously unselected package libkrb5-3:amd64.
Preparing to unpack .../libkrb5-3_1.13.2+dfsg-5_amd64.deb ...
Unpacking libkrb5-3:amd64 (1.13.2+dfsg-5) ...
Selecting previously unselected package libgssapi-krb5-2:amd64.
Preparing to unpack .../libgssapi-krb5-2_1.13.2+dfsg-5_amd64.deb ...
Unpacking libgssapi-krb5-2:amd64 (1.13.2+dfsg-5) ...
Selecting previously unselected package libsasl2-modules-db:amd64.
Preparing to

Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

[Aurelien Jarno]

On 2016-04-08 10:45, Aurelien Jarno wrote:
> Hi,
> 
> On 2016-04-07 11:51, James Cowgill wrote:
> > 
> > Based only on chrpath and cmake reverse dependencies, there is an upper
> > bound of about 1500 binNMUs (after the tools after fixed). Hopefully
> > that can be reduced!
> >
> > I really don't have any time to fix all this. Please can someone else
> > have a look!
> 
> I'll try to do an archive scan asap to really get an idea on how many
> packages are affected. After I'll look at how to fix chrpath, but help
> would be welcome as I also don't have a lot of time.

Please find below a small quick and dirty python script to check that.
There is probably a way to do it better and cleaner, but it does its
job.

I will start an archive scan and will start working on a chrpath fix.

Aurelien



#!/usr/bin/python3

from sys import argv, exit
from elftools.elf.elffile import ELFFile, DynamicSection

# MIPS specific constants
DT_MIPS_BASE_ADDRESS=0x7006
DT_MIPS_RLD_MAP=0x7016
DT_MIPS_RLD_MAP_REL=0x7035

good = True
filename = argv[1]

with open(filename, 'rb') as f:
for section in ELFFile(f).iter_sections():
if not isinstance(section, DynamicSection):
continue

base = None
rld_map = None
rld_map_rel = None
rld_map_rel_offset = None
for index, tag in enumerate(section.iter_tags()):
if tag.entry.d_tag == DT_MIPS_BASE_ADDRESS:
base = tag.entry.d_val
elif tag.entry.d_tag == DT_MIPS_RLD_MAP:
rld_map = tag.entry.d_val
elif tag.entry.d_tag == DT_MIPS_RLD_MAP_REL:
rld_map_rel = tag.entry.d_val
rld_map_rel_offset = section.header.sh_offset + index * 
section.header.sh_entsize

if base and rld_map and rld_map_rel:
if rld_map != base + rld_map_rel + rld_map_rel_offset:
good = False

print('%s: %s' % (filename, 'ok' if good else 'bad'))
exit(0 if good else 1)

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#819262: marked as done (gitlab: overwrites nginx configuration file settings unconditionally)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 16:30:31 +
with message-id 
and subject line Bug#819262: fixed in gitlab 8.5.8+dfsg-5
has caused the Debian Bug report #819262,
regarding gitlab: overwrites nginx configuration file settings unconditionally
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.)


-- 
819262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.4.3+dfsg-12
Severity: serious

On upgrade, the gitlab package overwrites any exisiting
/etc/nginx/sites-available/${GITLAB_HOST} file, thus obliterating any
local changes.  This is a serious violation of the Debian policy on
configuration files, section 10.7.3.

The postinst should only create this file if it does not already
exist.  Even then, it potentially conflicts with any existing nginx
configuration, so it would be nicer to ask whether to set it up at
all.

Less severely, it does not remove this file and the corresponding
/etc/nginx/sites-enabled link on package purge.  Also, if nginx is
already running (which it may be if letsencrypt is not being used),
invoke-rc.d nginx start may not be effective; reload may be more
appropriate.

   Julian

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

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

Versions of packages gitlab depends on:
ii  adduser3.114
ii  asciidoctor1.5.4-1
ii  bc 1.06.95-9+b1
ii  bundler1.11.2-1
ii  debconf [debconf-2.0]  1.5.59
ii  git1:2.8.0~rc3-1
ii  gitlab-shell   2.6.10-1
ii  gitlab-workhorse   0.6.3-1
ii  init-system-helpers1.29
ii  letsencrypt0.4.1-1
ii  libjs-chartjs  1.0.2-1
ii  libjs-clipboard1.4.2-1
ii  libjs-fuzzaldrin-plus  0.3.1-1
ii  libjs-graphael 0.5+dfsg-1
ii  libjs-jquery-cookie10-2
ii  libjs-jquery-history   10-2
ii  libjs-jquery-nicescroll3.6.6-1
ii  nginx  1.9.10-1
ii  nginx-full [nginx] 1.9.10-1
ii  nodejs 4.3.1~dfsg-3
ii  postgresql 9.5+172
ii  postgresql-client  9.5+172
ii  postgresql-client-9.4 [postgresql-client]  9.4.6-0+deb8u1
ii  postgresql-client-9.5 [postgresql-client]  9.5.1-1
ii  rake   10.5.0-2
ii  redis-server   2:3.0.6-1
ii  ruby   1:2.3.0+1
ii  ruby-ace-rails-ap  3.0.3-2
ii  ruby-activerecord-deprecated-finders   1.0.4-1
ii  ruby-activerecord-session-store0.1.1-3
ii  ruby-acts-as-taggable-on   3.5.0-2
ii  ruby-addressable   2.3.8-1
ii  ruby-after-commit-queue1.3.0-1
ii  ruby-allocations   1.0.3-1+b2
ii  ruby-asana 0.4.0-1
ii  ruby-attr-encrypted1.3.4-1
ii  ruby-babosa1.0.2-1
ii  ruby-bootstrap-sass3.3.5.1-3
ii  ruby-browser   1.0.1-1
ii  ruby-cal-heatmap-rails 3.5.1+dfsg-1
ii  ruby-carrierwave   0.10.0+gh-2
ii  ruby-charlock-holmes   0.7.3+dfsg-2+b2
ii  ruby-coffee-rails  4.1.0-2
ii  ruby-colorize  0.7.7-1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise3.5.6-2
ii  ruby-devise-async  0.9.0-1
ii  ruby-devise-two-factor 2.0.0-1
ii  ruby-diffy 3.0.6-1
ii  ruby-doorkeeper   

Bug#804582: (no subject)

[Barry Warsaw]

I haven't quite fixed it yet, but it's almost certainly related to FOLDER in
test_sftp.py.  When the tests, such as test_K_utf8() fail, it's because the
folder isn't empty so the os.rmdir() fails.

Quickly I tried to add a TEST_FOLDER=`mktemp -d` to the test command but that
didn't quite work.  I think that's still probably on the right track, but I
don't have some detail right yet.

Processed: Re: feh: FTBFS: test failure when preloading gif images

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #812657 {Done: Andreas Tille } [feh] feh: FTBFS: test 
failure when preloading gif images
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions feh/2.14.1-1.

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

Bug#812657: feh: FTBFS: test failure when preloading gif images

[Tobias Frost]

Package: feh
Followup-For: Bug #812657
Control: reopen -1

Hi Michael,

on the buildds this (or quite similar) error shows up on powerppc, hppa and 
kfreebsd-i386.
Mind to take a look?

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

(The binNMU was due to the libpng transition)

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

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

Bug#804582: (no subject)

[Barry Warsaw]

On Apr 08, 2016, at 10:59 AM, Jeremy T. Bouse wrote:

>Yes, I'd taken a slightly different approach but got to the same results
>that you are currently getting. I have included your approach as it is
>much cleaner than what I'd hacked together.
>
>Still trying to get to the bottom of those remaining failures causing
>the test to fail and the build to cease.

Awesome, thanks.  I'm also trying to investigate those last few failures.  I
applied the following patch to get a bit more debugging, but other than seeing
the errno is 4 (EINTR) I don't have any more information.

I also looked at updating the package to the latest upstream but that didn't
seem to help the failures, and upstream's latest tarball isn't compatible with
the current quilt patch.  I also tried 1.15.4 but that didn't help either.

I'll also note that `tox -e py27,py35` of upstream's git (master, v1.15.3, and
v1.15.4) passes all its tests so there's something weird about the build
environment that's breaking the build.  FWIW, I'm using sbuild with a sid
chroot.

--- a/paramiko/sftp_client.py
+++ b/paramiko/sftp_client.py
@@ -803,7 +803,7 @@
 elif code == SFTP_PERMISSION_DENIED:
 raise IOError(errno.EACCES, text)
 else:
-raise IOError(text)
+raise IOError(code, text)
 
 def _adjust_cwd(self, path):
 """


pgpuW7HIy20DY.pgp
Description: OpenPGP digital signature

Bug#804582: (no subject)

[Jeremy T. Bouse]

Yes, I'd taken a slightly different approach but got to the same results
that you are currently getting. I have included your approach as it is
much cleaner than what I'd hacked together.

Still trying to get to the bottom of those remaining failures causing
the test to fail and the build to cease.

On 04/07/2016 06:28 PM, Barry Warsaw wrote:
> I'm running across this too now.  I think part of the problem is that pybuild
> invokes unittest discover by default, but this isn't how paramiko's test suite
> is actually run, at least if you go by what's in the tox.ini file.
> 
> This gets me closer:
> 
> diff --git a/debian/rules b/debian/rules
> index 9c04662..8d5d25b 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1,6 +1,7 @@
>  #!/usr/bin/make -f
>  
>  export PYBUILD_NAME=paramiko
> +export PYBUILD_TEST_ARGS={interpreter} $(CURDIR)/test.py
>  
>  %:
>   dh $@ --with python2,python3 --buildsystem=pybuild
> @@ -11,3 +12,5 @@ ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS)))
>  endif
>   dh_installdocs
>  
> +override_dh_auto_test:
> + PYBUILD_SYSTEM=custom dh_auto_test
> 
> 
> But I'm still seeing two failures and two errors:
> 
> ==
> ERROR: test_K_utf8 (tests.test_sftp.SFTPTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_sftp.py", line 171, in tearDown
> sftp.rmdir(FOLDER)
>   File "/<>/paramiko/sftp_client.py", line 390, in rmdir
> self._request(CMD_RMDIR, path)
>   File "/<>/paramiko/sftp_client.py", line 729, in _request
> return self._read_response(num)
>   File "/<>/paramiko/sftp_client.py", line 776, in _read_response
> self._convert_status(msg)
>   File "/<>/paramiko/sftp_client.py", line 806, in 
> _convert_status
> raise IOError(text)
> IOError: Failure
> 
> ==
> ERROR: test_L_utf8_chdir (tests.test_sftp.SFTPTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_sftp.py", line 679, in test_L_utf8_chdir
> sftp.mkdir(FOLDER + '/' + unicode_folder)
>   File "/<>/paramiko/sftp_client.py", line 380, in mkdir
> self._request(CMD_MKDIR, path, attr)
>   File "/<>/paramiko/sftp_client.py", line 729, in _request
> return self._read_response(num)
>   File "/<>/paramiko/sftp_client.py", line 776, in _read_response
> self._convert_status(msg)
>   File "/<>/paramiko/sftp_client.py", line 806, in 
> _convert_status
> raise IOError(text)
> IOError: Failure
> 
> ==
> FAIL: test_K_utf8 (tests.test_sftp.SFTPTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_sftp.py", line 675, in test_K_utf8
> self.fail('exception ' + str(e))
> AssertionError: exception Failure
> 
> ==
> FAIL: test_O_getcwd (tests.test_sftp.SFTPTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_sftp.py", line 734, in test_O_getcwd
> self.assertEqual(None, sftp.getcwd())
> AssertionError: None != u'/'
> 
> --
> Ran 148 tests in 34.596s
> 
> FAILED (failures=2, errors=2)
> 




signature.asc
Description: OpenPGP digital signature

Processed: libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 4:15.12.1-1
Bug #820447 [libkf5libkdepim5,oxygen5-icon-theme] 
libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together
There is no source info for the package 'oxygen5-icon-theme' at version 
'4:15.12.1-1' with architecture ''
Marked as found in versions kdepim/4:15.12.1-1.
> found -1 5.19.0-1
Bug #820447 [libkf5libkdepim5,oxygen5-icon-theme] 
libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together
There is no source info for the package 'libkf5libkdepim5' at version 
'5.19.0-1' with architecture ''
Marked as found in versions oxygen-icons5/5.19.0-1.

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

Bug#820447: libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together

[Andreas Beckmann]

Package: libkf5libkdepim5,oxygen5-icon-theme
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 4:15.12.1-1
Control: found -1 5.19.0-1

Hi,

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

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

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

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

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

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

Cheers,

Andreas

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


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

Processed: imview: diff for NMU version 1.1.9c-12.1

[Debian Bug Tracking System]

Processing control commands:

> tags 820439 + patch
Bug #820439 [imview] imview: FTBFS with libpng1.6
Added tag(s) patch.
> tags 820439 + pending
Bug #820439 [imview] imview: FTBFS with libpng1.6
Added tag(s) pending.

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

Bug#820439: imview: diff for NMU version 1.1.9c-12.1

[Tobias Frost]

Control: tags 820439 + patch
Control: tags 820439 + pending

Dear maintainer,

I've prepared an NMU for imview (versioned as 1.1.9c-12.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru imview-1.1.9c/debian/changelog imview-1.1.9c/debian/changelog
--- imview-1.1.9c/debian/changelog  2013-05-07 21:00:45.0 +0200
+++ imview-1.1.9c/debian/changelog  2016-04-08 16:23:52.0 +0200
@@ -1,3 +1,10 @@
+imview (1.1.9c-12.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix for libpng1.6 (Closes: #820439)
+
+ -- Tobias Frost   Fri, 08 Apr 2016 16:23:52 +0200
+
 imview (1.1.9c-12) unstable; urgency=low
 
   [ Sebastian Ramacher ]
diff -Nru imview-1.1.9c/debian/patches/08_fix_libpng16.patch 
imview-1.1.9c/debian/patches/08_fix_libpng16.patch
--- imview-1.1.9c/debian/patches/08_fix_libpng16.patch  1970-01-01 
01:00:00.0 +0100
+++ imview-1.1.9c/debian/patches/08_fix_libpng16.patch  2016-04-08 
16:23:37.0 +0200
@@ -0,0 +1,80 @@
+Description: Patch for libpng1.6
+ libpng1.6 removed direct access of its member functions.
+Author: Tobias Frost 
+Bug-Debian: https://bugs.debian.org/820439
+Forwarded: no
+Last-Update: 2016-04-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/io/readpng.cxx
 b/io/readpng.cxx
+@@ -96,7 +96,7 @@
+ pp   = png_create_read_struct(PNG_LIBPNG_VER_STRING, NULL, NULL, NULL);
+ info = png_create_info_struct(pp);
+ 
+-if (setjmp(pp->jmpbuf))
++if (setjmp(png_jmpbuf(pp)))
+ {
+ errprintf("PNG file \"%s\" contains errors!\n", pngfilename);
+ return 103;
+@@ -108,28 +108,40 @@
+ // Get the image dimensions and convert to grayscale or RGB...
+ png_read_info(pp, info);
+ 
+-if (info->color_type == PNG_COLOR_TYPE_PALETTE)
++png_uint_32 width;
++png_uint_32 height;
++int bit_depth;
++int color_type;
++int interlace_type;
++int compression_type;
++int filter_method;
++
++png_get_IHDR(pp, info, &width, &height,
++   &bit_depth, &color_type, &interlace_type,
++   &compression_type, &filter_method);
++
++if (color_type == PNG_COLOR_TYPE_PALETTE)
+ png_set_expand(pp);
+ 
+-if (info->color_type & PNG_COLOR_MASK_COLOR)
++if (color_type & PNG_COLOR_MASK_COLOR)
+ channels = 3;
+ else
+ channels = 1;
+ 
+-if ((info->color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
++if ((color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
+ channels ++;
+ 
+-w = (int)(info->width);
+-h = (int)(info->height);
++w = (int)(width);
++h = (int)(height);
+ d = channels;
+ 
+-if (info->bit_depth < 8)
++if (bit_depth < 8)
+ {
+ png_set_packing(pp);
+ png_set_expand(pp);
+ }
+ // we ought to read the 16-bit data correctly, since we can !
+-else if (info->bit_depth == 16)
++else if (bit_depth == 16)
+ png_set_strip_16(pp);
+ 
+ #  if defined(HAVE_PNG_GET_VALID) && defined(HAVE_PNG_SET_TRNS_TO_ALPHA)
+--- a/io/readpng.cxx
 b/io/readpng.cxx
+@@ -128,7 +128,9 @@
+ else
+ channels = 1;
+ 
+-if ((color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
++int num_trans;
++png_get_tRNS(pp, info, NULL, &num_trans, NULL);
++if ((color_type & PNG_COLOR_MASK_ALPHA) || num_trans)
+ channels ++;
+ 
+ w = (int)(width);
diff -Nru imview-1.1.9c/debian/patches/series 
imview-1.1.9c/debian/patches/series
--- imview-1.1.9c/debian/patches/series 2013-05-07 20:20:40.0 +0200
+++ imview-1.1.9c/debian/patches/series 2016-04-08 15:45:09.0 +0200
@@ -5,3 +5,4 @@
 05_fix_dangerous_use_of_strncpy.patch
 06_fix_format_not_a_string.patch
 07_fix_kfreebsd_FTBFS.patch
+08_fix_libpng16.patch

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Jérémy Lal]

2016-04-08 15:10 GMT+02:00 Sebastiaan Couwenberg :

> On 04/08/2016 02:20 PM, Jérémy Lal wrote:
> > 2016-04-08 14:04 GMT+02:00 Sebastiaan Couwenberg:
> >> The test target fails because it requires node-pre-gyp, as do the
> >> bin/mapnik-*.js executables. We'll need to patch those to not require
> >> node-pre-gyp too.
> >>
> >> Do you have any suggestions for that?
> >
> > Yes, i have: i'm packaging node-pre-gyp and rc modules, it seems pkg-tar
> > could stay a recommandation.
> > It will be way simpler than spending the time patching node-mapnik.
>
> Thanks!
>
> I've patched the mapnik-*.js executables to not require node-pre-gyp,
> that just leaves lib/mapnik.js which uses it to find mapnik_settings.js.
>
> Since its path differs between the build environment and after
> installation, I'm not sure if we can make it support both without
> node-pre-gyp.
>
> I think I'll leave the node-mapnik packaging as it is for now, add have
> another look when node-pre-gyp is available or if it becomes clear we
> can work around it.
>

Ok. I'll be able to upload node-pre-gyp and node-rc later today.

Jérémy

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Sebastiaan Couwenberg]

On 04/08/2016 02:20 PM, Jérémy Lal wrote:
> 2016-04-08 14:04 GMT+02:00 Sebastiaan Couwenberg:
>> The test target fails because it requires node-pre-gyp, as do the
>> bin/mapnik-*.js executables. We'll need to patch those to not require
>> node-pre-gyp too.
>>
>> Do you have any suggestions for that?
> 
> Yes, i have: i'm packaging node-pre-gyp and rc modules, it seems pkg-tar
> could stay a recommandation.
> It will be way simpler than spending the time patching node-mapnik.

Thanks!

I've patched the mapnik-*.js executables to not require node-pre-gyp,
that just leaves lib/mapnik.js which uses it to find mapnik_settings.js.

Since its path differs between the build environment and after
installation, I'm not sure if we can make it support both without
node-pre-gyp.

I think I'll leave the node-mapnik packaging as it is for now, add have
another look when node-pre-gyp is available or if it becomes clear we
can work around it.

Kind Regards,

Bas

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

Bug#820439: imview: FTBFS with libpng1.6

[Tobias Frost]

Package: imview
Severity: serious
Justification: FTBFS
Control: block 650601 by -1

Buildlog: 
https://buildd.debian.org/status/fetch.php?pkg=imview&arch=arm64&ver=1.1.9c-12%2Bb2&stamp=1460117919

Example snippet:

In file included from /usr/include/pngconf.h:50:0,
 from /usr/include/png.h:340,
 from readpng.cxx:57:
readpng.cxx: In function 'int readPNGImage(const char*, int)':
readpng.cxx:99:18: error: invalid use of incomplete type 'png_struct {aka 
struct png_struct_def}'
 if (setjmp(pp->jmpbuf))
^

I will try to comeup with an patch / NMU this weekend.


--
tobi

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

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

Processed: imview: FTBFS with libpng1.6

[Debian Bug Tracking System]

Processing control commands:

> block 650601 by -1
Bug #650601 [release.debian.org] transition: libpng 1.6
650601 was blocked by: 810190 636004 662556 810182 809891 742559 662278 810172 
809871 809892 662421 648126 810201 662444 809897 809950 638812 810202 816103 
809867 635946 649557 819434 810183 810193 662522 809878 741891 662314 649971 
809860 809941 809879 809859 809952 650483 810171 809865 809945 809938 809944 
810169 810189 809946 809880 662476 810179 810208 810180 810207 809907 662465 
809862 809864 809939 809921 741894 809896 809904 649547 809942 809895 809957 
809960 809956 650489 810176 809868 809911 648131 810200 809869 641892 809959 
819438 742655 810197 641889 809893 810186 809940 809905 809887 809884 662566 
650575 814879 741901 810191 650567 819440 809951 809866 650571 809937 810209 
635704 809833 809947 662411 810095 809961 650484 810175 649546 662416 662437 
809954 742569 636998 809898 809899 809861 810168 809955 742560 816102 810165 
816115 809962 635945 809883 809886 810178 810195 809894 809943 743391 809908 
816116 809882 649552 662273 809948 819428 649798 810177 810166 662492 809885 
809933 809889 810174 662473 809936 810192 662554 809890 662334 810170 648129 
810167 809863 809913 662550 810187 809935 820347 809910 809870 662443 809872 
642265 662381 662523 809881 662407 811370 809873 650563 810188 809949 809953 
662530 810185 809835 809934 809836 816114 810205 810203 809906 809958 809888 
809909
650601 was blocking: 649556 649973
Added blocking bug(s) of 650601: 820439

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

Bug#820315: marked as done (lgogdownloader: FTBFS: util.cpp:391:48: error: conversion from 'Json::Value::const_iterator {aka Json::ValueConstIterator}' to non-scalar type 'Json::ValueIterator' request

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 12:30:18 +
with message-id 
and subject line Bug#820315: fixed in lgogdownloader 2.27-2
has caused the Debian Bug report #820315,
regarding lgogdownloader: FTBFS: util.cpp:391:48: error: conversion from 
'Json::Value::const_iterator {aka Json::ValueConstIterator}' to non-scalar type 
'Json::ValueIterator' requested
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.)


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

lgogdownloader fails to build from source in unstable/amd64:

  [..]

cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
  -- The CXX compiler identification is GNU 5.3.1
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Boost version: 1.58.0
  -- Found the following Boost libraries:
  --   system
  --   filesystem
  --   regex
  --   program_options
  --   date_time
  -- Found CURL: /usr/lib/x86_64-linux-gnu/libcurl.so (found version "7.47.0") 
  -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") 
  -- Checking for module 'oauth'
  --   Found oauth, version 1.0.1
  -- Checking for module 'jsoncpp'
  --   Found jsoncpp, version 1.7.2
  -- Checking for module 'htmlcxx'
  --   Found htmlcxx, version 0.86
  -- Checking for module 'tinyxml'
  --   Found tinyxml, version 2.6.2
  -- Configuring done
  -- Generating done
  CMake Warning:
Manually-specified variables were not used by the project:
  
  CMAKE_INSTALL_LOCALSTATEDIR
  CMAKE_INSTALL_SYSCONFDIR
  
  
  -- Build files have been written to: 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu'
  /usr/bin/cmake 
-H/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27 
-B/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu
 --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu/CMakeFiles
 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
  make -f CMakeFiles/Makefile2 all
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu'
  make -f CMakeFiles/lgogdownloader.dir/build.make 
CMakeFiles/lgogdownloader.dir/depend
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu/CMakeFiles/lgogdownloader.dir/DependInfo.cmake
 --color=
  Scanning dependencies of target lgogdownloader
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu'
  make -f CMakeFiles/lgogdownloader.dir/build.make 
CMakeFiles/lgogdownloader.dir/build
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/obj-x86_64-linux-gnu'
  [ 10%] Building CXX object CMakeFiles/lgogdownloader.dir/main.cpp.o
  /usr/bin/c++   -DVERSION_NUMBER=\"2.27\" -DVERSION_STRING="\"LGOGDownloader 
2.27\"" -D_FILE_OFFSET_BITS=64 
-I/home/lamby/temp/cdt.20160407113052.e5mz1FQa3p/lgogdownloader-2.27/include 
-I/usr/include/jsoncpp -I/usr/include/htmlcxx  -g -O2 -fPIE 
-fstack-protector-strong -Wformat -We

Bug#820062: orthanc and orthanc-doc: error when trying to install together

[Sébastien Jodogne]

Hi Andreas,

> please double check my commits whether all files end up where they
> should be.  The package builds nor also for arch all binary packages.
> 
> I also fixed some other minor issues.
> 
> Hope this helps and let me know if it should be sponsored as it is
> now.

I am extremely grateful for your solving of all these issues!

I confirm that all my integration tests pass, and that the files are put where 
they should be.

As far as I'm concerned, the package can be uploaded right now.

Thank again for your help,
Sébastien-

Bug#820064: marked as done (lgogdownloader: Needs fix to work with new jsoncpp version)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 12:30:18 +
with message-id 
and subject line Bug#820064: fixed in lgogdownloader 2.27-2
has caused the Debian Bug report #820064,
regarding lgogdownloader: Needs fix to work with new jsoncpp version
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.)


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

Dear Maintainer,

the upgrade to the new libjsoncpp1 version seems to have introduced a
problem:

$ lgogdownloader --update-cache
terminate called after throwing an instance of 'Json::RuntimeError'
  what():  ConstIterator to Iterator should never be allowed.
Aborted

Applying the patch from

https://github.com/Sude-/lgogdownloader/commit/519cb78d38be04a3af79784b5326e21651ced6e1

and rebuilding the package fixes this issue for me.

Cheers
Wolfgang

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

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

Versions of packages lgogdownloader depends on:
ii  libboost-date-time1.58.01.58.0+dfsg-5+b1
ii  libboost-filesystem1.58.0   1.58.0+dfsg-5+b1
ii  libboost-program-options1.58.0  1.58.0+dfsg-5+b1
ii  libboost-regex1.58.01.58.0+dfsg-5+b1
ii  libboost-system1.58.0   1.58.0+dfsg-5+b1
ii  libc6   2.22-5
ii  libcss-parser-pp0v5 0.86-1
ii  libcss-parser0  0.86-1
ii  libcurl3-gnutls 7.47.0-1
ii  libgcc1 1:5.3.1-13
ii  libhtmlcxx3v5   0.86-1
ii  libjsoncpp1 1.7.2-1
ii  liboauth0   1.0.1-1
ii  librhash0   1.3.3-1
ii  libstdc++6  5.3.1-13
ii  libtinyxml2.6.2v5   2.6.2-3

lgogdownloader recommends no packages.

lgogdownloader suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lgogdownloader
Source-Version: 2.27-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated lgogdownloader 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, 08 Apr 2016 13:46:48 +0200
Source: lgogdownloader
Binary: lgogdownloader
Architecture: source
Version: 2.27-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 lgogdownloader - downloader for GOG.com files
Closes: 820064 820315
Changes:
 lgogdownloader (2.27-2) unstable; urgency=medium
 .
   * Apply upstream patch to build with libjsoncpp 1.7.1 and later. Closes:
 #820064, #820315.
Checksums-Sha1:
 e86e77f7ecfacbf6f633b3c2a9e737dfb325f0ef 2193 lgogdownloader_2.27-2.dsc
 caf6fb08b53228aba1bab9648458d75cd36cf404 3384 
lgogdownloader_2.27-2.debian.tar.xz
Checksums-Sha256:
 5a78996c71afdd47cbe642920485ff197d418513ae1cbe74ca9c412bf385f0bc 2193 
lgogdownloader_2.27-2.dsc
 b80eda75ee43f55758f8b3ff9e4eb9044fc943111c7678fa8143df84ec1e4436 3384 
lgogdownloader_2.27-2.debian.tar.xz
Files:
 a1ec0adad4107a88c5eb42be4f81e724 2193 web optional lgogdownloader_2.27-2.dsc
 fce83c58aeb4cc69120af66689d6712b 3384 web optional 
lgogdownloader_2.27-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXB5y+AAoJEIDTAvWIbYOcq4IQAISu+nLJ6FwuiQJRVc8u4nnA
ORp85jdArGzCXYkuXXVmllOfSFFnV2FTb8jMobvc7s6kmg3ALLP3EcUmxZLsWCF7
tXgpTNDKDOup2WG/0ibzt08+leIF+o29+Vgshowt3AleODMKi8Cu2DDa44t1JGSJ
WlKHEf7JDDXHAlJ3frF3ZsqrCV+PVZLK+F7nVDgpOfqAKBnNPUqWgO8WTnWG/Cda
nv4yi9OWDAJIZSGGMLiPawNyl3gT9OsuxTl/eCdj2pcpRyLgHDL9QtdGEnoEetFq
KZvA3v4VFshsPOg7i91t34bxKRhj1PL1AmEE5A5Kk/fkcN2g5VMnFInG82MVbqqV
z0qTzTYDM92NvFtjxVWVnj7toNje8i/0y4W6OM/ajh2gQlQyabrhiVyzErTMH

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Jérémy Lal]

2016-04-08 14:04 GMT+02:00 Sebastiaan Couwenberg :

> On 04/08/2016 01:54 PM, Jérémy Lal wrote:
> > 2016-04-08 12:49 GMT+02:00 Sebastiaan Couwenberg :
> >
> >> On 04/08/2016 12:34 PM, Jérémy Lal wrote:
> >>> 2016-04-08 12:24 GMT+02:00 Sebastiaan Couwenberg:
>  Currenly `node-gyp configure` fails with:
> 
>  gyp: Undefined variable module_path in binding.gyp while trying to
> load
>  binding.gyp
> 
>  If it's possible to fix that by using the system provided
> dependencies,
>  it may be feasible to get node-mapnik working again.
> 
> 
> >>> The generic way of getting rid of these:
> >>>
> >>> node-gyp configure --module_name=`nodejs -e
> >>> "console.log(require('./package.json').binary.module_name)"`
> >>> --module_path=`nodejs -e
> >>> "console.log(require('./package.json').binary.module_path)"`
> >>>
> >>>
> >>> Updating node-mapnik is looking good; but I have trouble with
> >>>
> >>> In file included from /usr/include/vector_tile_merc_tile.hpp:5:0,
> >>>  from ../src/mapnik_vector_tile.hpp:11,
> >>>  from ../src/node_mapnik.cpp:5:
> >>> /usr/include/vector_tile_tile.hpp:208:32: fatal error:
> >>> vector_tile_tile.ipp: Aucun fichier ou dossier de ce type
> >>>
> >>> does it ring a bell ?
> >>
> >> Yes, the .ipp file is included in the mapnik-vector-tile source, but not
> >> installed in the binary package.
> >>
> >> I'll update mapnik-vector-tile to install the .ipp files too.
> >
> > I've just tested with those files installed by hand and it works all
> right.
>
> Yes, I've got similar results after some more changes to the node-mapnik
> packaging.
>
> The test target fails because it requires node-pre-gyp, as do the
> bin/mapnik-*.js executables. We'll need to patch those to not require
> node-pre-gyp too.
>
> Do you have any suggestions for that?
>
>
Yes, i have: i'm packaging node-pre-gyp and rc modules, it seems pkg-tar
could stay a recommandation.
It will be way simpler than spending the time patching node-mapnik.

Jérémy

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Sebastiaan Couwenberg]

On 04/08/2016 01:54 PM, Jérémy Lal wrote:
> 2016-04-08 12:49 GMT+02:00 Sebastiaan Couwenberg :
> 
>> On 04/08/2016 12:34 PM, Jérémy Lal wrote:
>>> 2016-04-08 12:24 GMT+02:00 Sebastiaan Couwenberg:
 Currenly `node-gyp configure` fails with:

 gyp: Undefined variable module_path in binding.gyp while trying to load
 binding.gyp

 If it's possible to fix that by using the system provided dependencies,
 it may be feasible to get node-mapnik working again.


>>> The generic way of getting rid of these:
>>>
>>> node-gyp configure --module_name=`nodejs -e
>>> "console.log(require('./package.json').binary.module_name)"`
>>> --module_path=`nodejs -e
>>> "console.log(require('./package.json').binary.module_path)"`
>>>
>>>
>>> Updating node-mapnik is looking good; but I have trouble with
>>>
>>> In file included from /usr/include/vector_tile_merc_tile.hpp:5:0,
>>>  from ../src/mapnik_vector_tile.hpp:11,
>>>  from ../src/node_mapnik.cpp:5:
>>> /usr/include/vector_tile_tile.hpp:208:32: fatal error:
>>> vector_tile_tile.ipp: Aucun fichier ou dossier de ce type
>>>
>>> does it ring a bell ?
>>
>> Yes, the .ipp file is included in the mapnik-vector-tile source, but not
>> installed in the binary package.
>>
>> I'll update mapnik-vector-tile to install the .ipp files too.
> 
> I've just tested with those files installed by hand and it works all right.

Yes, I've got similar results after some more changes to the node-mapnik
packaging.

The test target fails because it requires node-pre-gyp, as do the
bin/mapnik-*.js executables. We'll need to patch those to not require
node-pre-gyp too.

Do you have any suggestions for that?

Kind Regards,

Bas

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

Bug#820062: orthanc and orthanc-doc: error when trying to install together

[Sébastien Jodogne]

Dear Andreas,

> > I am really sorry, but despite hours of work and readings, I am still
> > totally unable to reproduce (and thus fix) this bug by myself.
> > [...]
> 
> Try
> 
>   pdebuild [pbuilder options] -- --debbuildopts -A
> 
> This will produce the broken package.

Great! The option "-A" was exactly what I was not able to find by myself.

Thanks again for your support,
Sébastien-

Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

[Emilio Pozuelo Monfort]

On Fri, 8 Apr 2016 12:16:47 +0200 Alastair McKinstry
 wrote:
> 
> >> OpenMPI maintainers (and anyone else affected):
> >> One possible workaround is to use chrpath -r ""  on mips*
> >> architectures until this is fixed since that command does not cause any
> >> tags to be moved. It has a tiny performance penalty but should
> >> otherwise work properly.
> > Thanks for the workaround.
> >
> > Aurelien
> >
> Thanks.
> I've tested this fix within openmpi on mips (works) and have uploaded a
> new version with
> the workaround.

Thanks! Unfortunately you forgot to apply this same workaround to mipsel and
mips64el. Could you apply it in those architectures as well?

Thanks,
Emilio

Bug#819881: radeon_fence_ref BUG: unable to handle kernel NULL pointer dereference

[Erik]

I visited the Debian CDs/DVDs archive and picked Jessie 8.3 from there.
Probably the easiest and fastest solution for me.
Rock solid again.

Processed: severity of 816116 is serious

[Debian Bug Tracking System]

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

> severity 816116 serious
Bug #816116 {Done: Gianfranco Costamagna } 
[libpolybori-dev] libpolybori-dev: Please change dependency from libpng12-dev 
to libpng-dev
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Sebastiaan Couwenberg]

On 04/08/2016 12:34 PM, Jérémy Lal wrote:
> 2016-04-08 12:24 GMT+02:00 Sebastiaan Couwenberg:
>> Currenly `node-gyp configure` fails with:
>>
>> gyp: Undefined variable module_path in binding.gyp while trying to load
>> binding.gyp
>>
>> If it's possible to fix that by using the system provided dependencies,
>> it may be feasible to get node-mapnik working again.
>>
>>
> The generic way of getting rid of these:
> 
> node-gyp configure --module_name=`nodejs -e
> "console.log(require('./package.json').binary.module_name)"`
> --module_path=`nodejs -e
> "console.log(require('./package.json').binary.module_path)"`
> 
> 
> Updating node-mapnik is looking good; but I have trouble with
> 
> In file included from /usr/include/vector_tile_merc_tile.hpp:5:0,
>  from ../src/mapnik_vector_tile.hpp:11,
>  from ../src/node_mapnik.cpp:5:
> /usr/include/vector_tile_tile.hpp:208:32: fatal error:
> vector_tile_tile.ipp: Aucun fichier ou dossier de ce type
> 
> does it ring a bell ?

Yes, the .ipp file is included in the mapnik-vector-tile source, but not
installed in the binary package.

I'll update mapnik-vector-tile to install the .ipp files too.

Kind Regards,

Bas

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

Bug#743388: t4kcommon: diff for NMU version 0.1.1-1.1

[Tobias Frost]

> Hi Tobi,
>
> On Thu, Apr 07, 2016 at 09:17:25PM +0200, Tobias Frost wrote:
>> I've prepared an NMU for t4kcommon (versioned as 0.1.1-1.1) and
>> uploaded it to DELAYED/2. Please feel free to tell me if I
>> should delay it longer.
>
> thanks for your work on t4kcommon and the whole libpng transition! Much
> appreciated.
>
>
> thanks,
>   Holger
>

Hi Holger,

would it be ok to move to 0-day then?
Thanks!

Tobi

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Jérémy Lal]

2016-04-08 12:24 GMT+02:00 Sebastiaan Couwenberg :

> On 04/08/2016 12:09 PM, Jérémy Lal wrote:
> > 2016-04-08 11:32 GMT+02:00 Sebastiaan Couwenberg :
> >
> >> On Wed, 8 Jul 2015 09:31:46 +0200 Jérémy Lal wrote:
> >>> 2015-07-07 23:43 GMT+02:00 Emilio Pozuelo Monfort :
>  Your package fails to build against mapnik 3.0.0:
> >>>
> >>> Thanks, it's going to be like this until gcc5 and latest boost libs are
> >>> available (which should be this summer).
> >>
> >> More recent node-mapnik versions are required for their Mapnik 3.x
> >> support, but these require the unpackaged node-pre-gyp to build.
> >>
> >> Perhaps it's better to remove node-mapnik and its reverse dependencies
> >> from the archive since they haven't seen any activity in over two years.
> >>
> >
> > Let me see if updating it goes smoothly. If not then i'll request the
> > removal.
>
> Thanks, that's much appreciated.
>
> I've pushed my initial changes for node-mapnik 3.5.8 to Alioth.
>
> > FYI node-pre-gyp is a useless module in debian because it is made to
> > download binaries from remote sources instead of properly compiling.
>
> Currenly `node-gyp configure` fails with:
>
> gyp: Undefined variable module_path in binding.gyp while trying to load
> binding.gyp
>
> If it's possible to fix that by using the system provided dependencies,
> it may be feasible to get node-mapnik working again.
>
>
The generic way of getting rid of these:

node-gyp configure --module_name=`nodejs -e
"console.log(require('./package.json').binary.module_name)"`
--module_path=`nodejs -e
"console.log(require('./package.json').binary.module_path)"`


Updating node-mapnik is looking good; but I have trouble with

In file included from /usr/include/vector_tile_merc_tile.hpp:5:0,
 from ../src/mapnik_vector_tile.hpp:11,
 from ../src/node_mapnik.cpp:5:
/usr/include/vector_tile_tile.hpp:208:32: fatal error:
vector_tile_tile.ipp: Aucun fichier ou dossier de ce type

does it ring a bell ?

Jérémy

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Sebastiaan Couwenberg]

On 04/08/2016 12:09 PM, Jérémy Lal wrote:
> 2016-04-08 11:32 GMT+02:00 Sebastiaan Couwenberg :
> 
>> On Wed, 8 Jul 2015 09:31:46 +0200 Jérémy Lal wrote:
>>> 2015-07-07 23:43 GMT+02:00 Emilio Pozuelo Monfort :
 Your package fails to build against mapnik 3.0.0:
>>>
>>> Thanks, it's going to be like this until gcc5 and latest boost libs are
>>> available (which should be this summer).
>>
>> More recent node-mapnik versions are required for their Mapnik 3.x
>> support, but these require the unpackaged node-pre-gyp to build.
>>
>> Perhaps it's better to remove node-mapnik and its reverse dependencies
>> from the archive since they haven't seen any activity in over two years.
>>
> 
> Let me see if updating it goes smoothly. If not then i'll request the
> removal.

Thanks, that's much appreciated.

I've pushed my initial changes for node-mapnik 3.5.8 to Alioth.

> FYI node-pre-gyp is a useless module in debian because it is made to
> download binaries from remote sources instead of properly compiling.

Currenly `node-gyp configure` fails with:

gyp: Undefined variable module_path in binding.gyp while trying to load
binding.gyp

If it's possible to fix that by using the system provided dependencies,
it may be feasible to get node-mapnik working again.

Kind Regards,

Bas

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

Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

[Alastair McKinstry]

>> OpenMPI maintainers (and anyone else affected):
>> One possible workaround is to use chrpath -r ""  on mips*
>> architectures until this is fixed since that command does not cause any
>> tags to be moved. It has a tiny performance penalty but should
>> otherwise work properly.
> Thanks for the workaround.
>
> Aurelien
>
Thanks.
I've tested this fix within openmpi on mips (works) and have uploaded a
new version with
the workaround.

regards
Alastair

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 

Processed: Gotta love BTS aka ssmtp to the rescue

[Debian Bug Tracking System]

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

> outlook 820331 Asked upstream whether original author wants to fix this / has 
> a preferred temp file creation method. Otherwise I'll patch with mktemp.
Outlook recorded from message bug 820331 message 
> thanks
Stopping processing here.

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

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Jérémy Lal]

2016-04-08 11:32 GMT+02:00 Sebastiaan Couwenberg :

> On Wed, 8 Jul 2015 09:31:46 +0200 Jérémy Lal wrote:
> > 2015-07-07 23:43 GMT+02:00 Emilio Pozuelo Monfort :
> > > Your package fails to build against mapnik 3.0.0:
> >
> > Thanks, it's going to be like this until gcc5 and latest boost libs are
> > available (which should be this summer).
>
> More recent node-mapnik versions are required for their Mapnik 3.x
> support, but these require the unpackaged node-pre-gyp to build.
>
> Perhaps it's better to remove node-mapnik and its reverse dependencies
> from the archive since they haven't seen any activity in over two years.
>

Let me see if updating it goes smoothly. If not then i'll request the
removal.

FYI node-pre-gyp is a useless module in debian because it is made to
download
binaries from remote sources instead of properly compiling.

Jérémy

Bug#819952: marked as done (oar: CVE-2016-1235: vulnerability in the oarsh command)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 09:49:29 +
with message-id 
and subject line Bug#819952: fixed in oar 2.5.2-3+deb7u1
has caused the Debian Bug report #819952,
regarding oar: CVE-2016-1235: vulnerability in the oarsh command
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.)


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

  This bug is fixed upstream but it will help to track affected versions in 
Debian

  Vincent

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

Kernel: Linux 4.5.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: oar
Source-Version: 2.5.2-3+deb7u1

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

Debian distribution maintenance software
pp.
Vincent Danjean  (supplier of updated oar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Apr 2016 11:07:22 +0200
Source: oar
Binary: liboar-perl oar-common oar-server oar-server-mysql oar-server-pgsql 
oar-node oar-user oar-user-mysql oar-user-pgsql oar-web-status oar-doc 
oar-admin oar-restful-api oar-api
Architecture: source amd64 all
Version: 2.5.2-3+deb7u1
Distribution: oldstable
Urgency: high
Maintainer: Philippe Le Brouster 
Changed-By: Vincent Danjean 
Description: 
 liboar-perl - OAR batch scheduler common library package
 oar-admin  - OAR batch scheduler administration tools package
 oar-api- transitional dummy package
 oar-common - OAR batch scheduler common package
 oar-doc- OAR batch scheduler documentation package
 oar-node   - OAR batch scheduler node package
 oar-restful-api - OAR RESTful API
 oar-server - OAR batch scheduler server package
 oar-server-mysql - OAR batch scheduler MySQL server backend package
 oar-server-pgsql - OAR batch scheduler PostgreSQL server backend package
 oar-user   - OAR batch scheduler user package
 oar-user-mysql - OAR batch scheduler MySQL user backend package
 oar-user-pgsql - OAR batch scheduler PostgreSQL user backend package
 oar-web-status - OAR batch scheduler visualization tool package
Closes: 819952
Changes: 
 oar (2.5.2-3+deb7u1) wheezy-security; urgency=high
 .
   [ Pierre Neyron ]
   * Add patch: fix a vulnerability in the oarsh command
 (CVE-2016-1235; Closes: #819952)
Checksums-Sha1: 
 39653f3beec97536fdd2668f6c3a92af2a32f2b8 2408 oar_2.5.2-3+deb7u1.dsc
 d80d6c1830bec7eeea057031b1e3d64967f4840e 6249043 oar_2.5.2.orig.tar.gz
 bbde697903029d8634d7f0281b52ce2842fe82b2 69755 oar_2.5.2-3+deb7u1.debian.tar.gz
 13738dff1da3241d4d42fa2f7724fc263adf8d83 74434 
liboar-perl_2.5.2-3+deb7u1_amd64.deb
 25a3193dcb9dc460be1bc25e6aae5b4729f04d91 67246 
oar-common_2.5.2-3+deb7u1_amd64.deb
 c6997b1ca6a70acf381e7c32e1ca0c71359730f0 151416 
oar-server_2.5.2-3+deb7u1_amd64.deb
 faab061d60ad766e925f25dca117ae5bf54e7b44 16446 
oar-server-mysql_2.5.2-3+deb7u1_amd64.deb
 7f41b032488ee3794234afd3e41b187f42c63931 16452 
oar-server-pgsql_2.5.2-3+deb7u1_amd64.deb
 ed5a4a35679a723e2ec921b141b383a23e65a3b7 28610 
oar-node_2.5.2-3+deb7u1_amd64.deb
 d9d82c79ec767eb93d96e46bf7e1989ac342394f 65694 
oar-user_2.5.2-3+deb7u1_amd64.deb
 d1010a58c396e6109d351dba3639c8a4e1451cbd 16426 
oar-user-mysql_2.5.2-3+deb7u1_amd64.deb
 6f753704fa7cec19e178fb7b8e0c17a92386a682 16428 
oar-user-pgsql_2.5.2-3+deb7u1_amd64.deb
 0b24dcf6a4b3671adcbedb4e18886aaed404547a 67830 
oar-web-status_2.5.2-3+deb7u1_all.deb
 b5fb82b2a219f95d16f872d6e30b9efbdca8568b 1277058 oar-doc_2.5.2-3+deb7u1_all.deb
 06923d8fb441d99d28cf2e49e77fb4da4e6e15a7 47890 
oar-adm

Bug#819952: marked as done (oar: CVE-2016-1235: vulnerability in the oarsh command)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 09:47:59 +
with message-id 
and subject line Bug#819952: fixed in oar 2.5.4-2+deb8u1
has caused the Debian Bug report #819952,
regarding oar: CVE-2016-1235: vulnerability in the oarsh command
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.)


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

  This bug is fixed upstream but it will help to track affected versions in 
Debian

  Vincent

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

Kernel: Linux 4.5.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: oar
Source-Version: 2.5.4-2+deb8u1

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

Debian distribution maintenance software
pp.
Vincent Danjean  (supplier of updated oar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Apr 2016 10:49:52 +0200
Source: oar
Binary: liboar-perl oar-common oar-server oar-server-mysql oar-server-pgsql 
oar-node oar-user oar-user-mysql oar-user-pgsql oar-web-status oar-doc 
oar-restful-api oar-api
Architecture: source amd64 all
Version: 2.5.4-2+deb8u1
Distribution: stable
Urgency: high
Maintainer: Pierre Neyron 
Changed-By: Vincent Danjean 
Description:
 liboar-perl - OAR batch scheduler common library package
 oar-api- transitional dummy package
 oar-common - OAR batch scheduler common package
 oar-doc- OAR batch scheduler documentation package
 oar-node   - OAR batch scheduler node package
 oar-restful-api - OAR web services
 oar-server - OAR batch scheduler server package
 oar-server-mysql - OAR batch scheduler MySQL server backend package
 oar-server-pgsql - OAR batch scheduler PostgreSQL server backend package
 oar-user   - OAR batch scheduler user package
 oar-user-mysql - OAR batch scheduler MySQL user backend package
 oar-user-pgsql - OAR batch scheduler PostgreSQL user backend package
 oar-web-status - OAR batch scheduler visualization tool package
Closes: 819952
Changes:
 oar (2.5.4-2+deb8u1) jessie-security; urgency=high
 .
   [ Pierre Neyron ]
   * Add patch: fix a vulnerability in the oarsh command
 (CVE-2016-1235; Closes: #819952)
Checksums-Sha1:
 91877597acadd7fad2deb9d14faafb6798b62153 2511 oar_2.5.4-2+deb8u1.dsc
 c7418643121da9852fad26a1071c50bd02d9d958 5066627 oar_2.5.4.orig.tar.gz
 cf30b0fef5afa2fd38bf3f1b63c30de0d2f60ba0 15240 oar_2.5.4-2+deb8u1.debian.tar.xz
 44d0d89594685f53a741c774584f0e25c086e996 73560 
liboar-perl_2.5.4-2+deb8u1_amd64.deb
 ee8609632d4c99d2e8c839ea2b4e39edcc4021ff 64314 
oar-common_2.5.4-2+deb8u1_amd64.deb
 e280ae9b2a0b541e3acbbddfdac07f49cca3fc23 147532 
oar-server_2.5.4-2+deb8u1_amd64.deb
 1756189f2fb04a7411dfdf0b6ab932ee60b74676 19846 
oar-server-mysql_2.5.4-2+deb8u1_amd64.deb
 285d4c7f09e4d59e275bf607e113d079fc5d 19842 
oar-server-pgsql_2.5.4-2+deb8u1_amd64.deb
 343380dcd57c9581a97375b1a4189776f889ba1f 31798 
oar-node_2.5.4-2+deb8u1_amd64.deb
 bb721d267db35d17ea1763aad64a26ff735297a9 66728 
oar-user_2.5.4-2+deb8u1_amd64.deb
 de0536afc8d97fa3fafe5b367f7dfe999d6ee5d4 19816 
oar-user-mysql_2.5.4-2+deb8u1_amd64.deb
 c1e4613f1ad30f2a672473a29163b705d78716db 19822 
oar-user-pgsql_2.5.4-2+deb8u1_amd64.deb
 a1b0633546be68e23aa88c663db7ee102a4300ad 48532 
oar-web-status_2.5.4-2+deb8u1_all.deb
 e90944adf7fe78bdd0e47aaefb710bf8b57df60c 1188308 oar-doc_2.5.4-2+deb8u1_all.deb
 a33db428087ad6853a38e80453380e35297ffd4f 51680 
oar-restful-api_2.5.4-2+deb8u1_amd64.deb
 6ecf297faab9f6b8a60024d3a183e6d5138ecdb8 19688 oar

Bug#807698: marked as done (srtp: CVE-2015-6360: Prevent potential DoS attack due to lack of bounds checking on RTP header CSRC count and extension header length)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 09:48:18 +
with message-id 
and subject line Bug#807698: fixed in srtp 1.4.5~20130609~dfsg-1.1+deb8u1
has caused the Debian Bug report #807698,
regarding srtp: CVE-2015-6360: Prevent potential DoS attack due to lack of 
bounds checking on RTP header CSRC count and extension header length
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.)


-- 
807698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srtp
Version: 1.4.5~20130609~dfsg-1.1
Severity: grave
Tags: security

Hi,
from what I figured out it seems the 1.4 series is also affected by
CVE-2015-6360. While there is no aead mode srtp_unprotect needs the
patch nevertheless. See:

https://security-tracker.debian.org/tracker/CVE-2015-6360

for a list of patches.
Cheers,
 -- Guido


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

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: srtp
Source-Version: 1.4.5~20130609~dfsg-1.1+deb8u1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated srtp 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, 01 Apr 2016 18:59:17 +0200
Source: srtp
Binary: libsrtp0-dev libsrtp0 srtp-docs srtp-utils
Architecture: source all amd64
Version: 1.4.5~20130609~dfsg-1.1+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Jonas Smedegaard 
Changed-By: Markus Koschany 
Description:
 libsrtp0   - Secure RTP (SRTP) and UST Reference Implementations - shared libr
 libsrtp0-dev - Secure RTP (SRTP) and UST Reference Implementations - 
development
 srtp-docs  - Secure RTP (SRTP) and UST Reference Implementations - documentati
 srtp-utils - Secure RTP (SRTP) and UST Reference Implementations - utilities
Closes: 807698
Changes:
 srtp (1.4.5~20130609~dfsg-1.1+deb8u1) jessie-security; urgency=high
 .
   * Non-maintainer upload.
   * Add CVE-2015-6360.patch.
 Prevent potential DoS attack due to lack of bounds checking on RTP header
 CSRC count and extension header length. (Closes: #807698)
Checksums-Sha1:
 5d15f647dda178828c786560c814caf06acb1cde 2411 
srtp_1.4.5~20130609~dfsg-1.1+deb8u1.dsc
 1276b78ad6d6c8d16a1c4cee0bf29b7fba41d72c 251824 
srtp_1.4.5~20130609~dfsg.orig.tar.gz
 d8ec48cd5337cca30a20db04a48a0fe7482ef736 14520 
srtp_1.4.5~20130609~dfsg-1.1+deb8u1.debian.tar.xz
 e919fdead3c6ff64dd2204116c832447f3b97797 237976 
srtp-docs_1.4.5~20130609~dfsg-1.1+deb8u1_all.deb
 e77cc49c24067d45be2a2da6e9891bbc81d0e513 93474 
libsrtp0-dev_1.4.5~20130609~dfsg-1.1+deb8u1_amd64.deb
 a9e0e83b85e0d02d79e07c568918332a5eeae03c 65154 
libsrtp0_1.4.5~20130609~dfsg-1.1+deb8u1_amd64.deb
 c065753813f5ce32b3879400fbf11222cf541c18 101224 
srtp-utils_1.4.5~20130609~dfsg-1.1+deb8u1_amd64.deb
Checksums-Sha256:
 07a5889fdd719369e7b1953f3c1ba1cd4de14c564a1257aa5516756c92ae4319 2411 
srtp_1.4.5~20130609~dfsg-1.1+deb8u1.dsc
 32083ced5621613a0190e4f0d5e7486aa0deb7d3a8f02d7d8bb45c57d0920584 251824 
srtp_1.4.5~20130609~dfsg.orig.tar.gz
 64566be5e36141bc42637434733c17de3ee9c6cb56ec8e822c4825e1f0dc058f 14520 
srtp_1.4.5~20130609~dfsg-1.1+deb8u1.debian.tar.xz
 e85c369a98cfa29187d8184c5d4d1adef250decaebee68917a9ac8fc03bd78f1 237976 
srtp-docs_1.4.5~20130609~dfsg-1.1+deb8u1_all.deb
 be4bed57687c6ebf363b0b1236605c3c8dfdbb1403039946354b906ec6ec2f3b 93474 
libsrtp0-dev_1.4.5~20130609~dfsg-1.1+deb8u1_amd64.deb
 f093edf30ed905e316c64727ff9ccac38946c1185fafa74f8ed6741338e0b5ef 65154 
libsrtp0_1.4.5~20130609~dfsg-1.1+deb8u1_amd64.deb
 dff65254de5f051a962f61922234e646c87e158bda4a2a7e857992961a9bdbce 101224 
srtp-utils_1.4.5~20

Bug#807698: marked as done (srtp: CVE-2015-6360: Prevent potential DoS attack due to lack of bounds checking on RTP header CSRC count and extension header length)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 09:49:44 +
with message-id 
and subject line Bug#807698: fixed in srtp 1.4.4+20100615~dfsg-2+deb7u2
has caused the Debian Bug report #807698,
regarding srtp: CVE-2015-6360: Prevent potential DoS attack due to lack of 
bounds checking on RTP header CSRC count and extension header length
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.)


-- 
807698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srtp
Version: 1.4.5~20130609~dfsg-1.1
Severity: grave
Tags: security

Hi,
from what I figured out it seems the 1.4 series is also affected by
CVE-2015-6360. While there is no aead mode srtp_unprotect needs the
patch nevertheless. See:

https://security-tracker.debian.org/tracker/CVE-2015-6360

for a list of patches.
Cheers,
 -- Guido


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

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: srtp
Source-Version: 1.4.4+20100615~dfsg-2+deb7u2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated srtp 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, 01 Apr 2016 19:07:24 +0200
Source: srtp
Binary: libsrtp0-dev libsrtp0 srtp-docs srtp-utils
Architecture: source all amd64
Version: 1.4.4+20100615~dfsg-2+deb7u2
Distribution: wheezy-security
Urgency: high
Maintainer: Jonas Smedegaard 
Changed-By: Markus Koschany 
Description: 
 libsrtp0   - Secure RTP (SRTP) and UST Reference Implementations - shared libr
 libsrtp0-dev - Secure RTP (SRTP) and UST Reference Implementations - 
development
 srtp-docs  - Secure RTP (SRTP) and UST Reference Implementations - documentati
 srtp-utils - Secure RTP (SRTP) and UST Reference Implementations - utilities
Closes: 807698
Changes: 
 srtp (1.4.4+20100615~dfsg-2+deb7u2) wheezy-security; urgency=high
 .
   * Non-maintainer upload.
   * Add CVE-2015-6360.patch.
 Prevent potential DoS attack due to lack of bounds checking on RTP header
 CSRC count and extension header length. (Closes: #807698)
Checksums-Sha1: 
 ddef67f6d1726ff4b2788292e061fe16c28b23c8 2404 
srtp_1.4.4+20100615~dfsg-2+deb7u2.dsc
 eb38e263929e84a4b214284ab26136c6abe67fff 15732 
srtp_1.4.4+20100615~dfsg-2+deb7u2.debian.tar.gz
 0f9eb8f4443d39b47a3de075b4a13d6ec9f6f0f0 232820 
srtp-docs_1.4.4+20100615~dfsg-2+deb7u2_all.deb
 ab56d6d140fe43016fccb3eca8ffa405a649e251 117244 
libsrtp0-dev_1.4.4+20100615~dfsg-2+deb7u2_amd64.deb
 abc1ec430267121a0514a29a777bc070195d5146 79998 
libsrtp0_1.4.4+20100615~dfsg-2+deb7u2_amd64.deb
 fb4debe4e545fe545ce75129b7713e9823668dca 366576 
srtp-utils_1.4.4+20100615~dfsg-2+deb7u2_amd64.deb
Checksums-Sha256: 
 46af8f4ec2ec8322d6e4cfcd111c72ddb45d63b4ad47dc1b892b74eb666a8e02 2404 
srtp_1.4.4+20100615~dfsg-2+deb7u2.dsc
 3dbffa22fdcdaee52ef8db71651b2193843b0a2d8a4108cfaeb0e547390b06be 15732 
srtp_1.4.4+20100615~dfsg-2+deb7u2.debian.tar.gz
 647bb100b37546f40f364c98845a8fda64b6d1cfff9a984b6f282d97a073a430 232820 
srtp-docs_1.4.4+20100615~dfsg-2+deb7u2_all.deb
 1910bcbc78e435360e02321a9e4801d2a018fb42fe94e25d5f91dd8182e6171b 117244 
libsrtp0-dev_1.4.4+20100615~dfsg-2+deb7u2_amd64.deb
 4f97bfcd92e39256aa16730567a8436ef4989168858117e2a83353bed03bd0fe 79998 
libsrtp0_1.4.4+20100615~dfsg-2+deb7u2_amd64.deb
 e5189cffc86618cca9b88befa9cd0a2e675acfb2423fa2a926186577d1972c6b 366576 
srtp-utils_1.4.4+20100615~dfsg-2+deb7u2_amd64.deb
Files: 
 793d7153d73e6313a37137c271c21456 2404 libs optional 
srtp_1.4.4+20100615~dfsg-2+deb7u2.dsc
 847a9d474d0e1c1efa5f5838d3377168 15732 libs optional 
srtp_1.4.4+20100615~dfsg-2+deb7u2.de

Bug#819504: marked as done (mercurial: CVE-2016-3068 CVE-2016-3069 CVE-2016-3630)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 09:49:25 +
with message-id 
and subject line Bug#819504: fixed in mercurial 2.2.2-4+deb7u2
has caused the Debian Bug report #819504,
regarding mercurial: CVE-2016-3068 CVE-2016-3069 CVE-2016-3630
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.)


-- 
819504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 3.7.2-2
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerabilities were published for mercurial.

CVE-2016-3068[0]:
arbitrary code execution with Git subrepos

CVE-2016-3069[1]:
arbitrary code execution when converting Git repos

CVE-2016-3630[2]:
remote code execution in binary delta decoding

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-3068
[1] https://security-tracker.debian.org/tracker/CVE-2016-3069
[2] https://security-tracker.debian.org/tracker/CVE-2016-3630
[3] https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.7.3_.282016-3-29.29

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 2.2.2-4+deb7u2

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mercurial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Apr 2016 22:51:48 +0200
Source: mercurial
Binary: mercurial-common mercurial
Architecture: source all amd64
Version: 2.2.2-4+deb7u2
Distribution: wheezy-security
Urgency: high
Maintainer: Python Applications Packaging Team 

Changed-By: Julien Cristau 
Description: 
 mercurial  - easy-to-use, scalable distributed version control system
 mercurial-common - easy-to-use, scalable distributed version control system 
(common
Closes: 819504
Changes: 
 mercurial (2.2.2-4+deb7u2) wheezy-security; urgency=high
 .
   * CVE-2016-3630:
 + mpatch: rewrite pointer overflow checks (prerequisite for the following)
 + parsers: fix list sizing rounding error
 + parsers: detect short records
   * CVE-2016-3068:
 + subrepo: set GIT_ALLOW_PROTOCOL to limit git clone protocols
   * CVE-2016-3069:
 + convert: add new, non-clowny interface for shelling out to git
 + convert: rewrite calls to Git to use the new shelling mechanism
 + convert: dead code removal - old git calling functions
 + convert: rewrite gitpipe to use common.commandline
 + convert: test for shell injection in git calls
   Closes: #819504
Checksums-Sha1: 
 312521447cfbf886d168441b61df63c2202efd0b 2164 mercurial_2.2.2-4+deb7u2.dsc
 2454b00f21ac9676da89600b004bae0e294d5d7a 50657 
mercurial_2.2.2-4+deb7u2.debian.tar.gz
 4713d1438c1f4ed810089ade7a8c662df0bbdf51 2324960 
mercurial-common_2.2.2-4+deb7u2_all.deb
 15332c9fdb6439d7974c12cdb29d47b2d06617cd 93336 
mercurial_2.2.2-4+deb7u2_amd64.deb
Checksums-Sha256: 
 7e7f259ce8b9690d5e7ff1b5d6c9fb8bdc32daef412f3bfa876a8d02782d8d39 2164 
mercurial_2.2.2-4+deb7u2.dsc
 765a1c55b1f44ee21c22d3defa5499499199888145bb4d0ba724e83fd95235fb 50657 
mercurial_2.2.2-4+deb7u2.debian.tar.gz
 4fc801b8c827d9ad7d2f2de6fe46fc3b4b85680eda6283544cc8208607390d10 2324960 
mercurial-common_2.2.2-4+deb7u2_all.deb
 726874d1d91fd78e91e3a81faf58675292d4d64a51b24897816bec3622bdf5f8 93336 
mercurial_2.2.2-4+deb7u2_amd64.deb
Files: 
 effd7642cb0a60494740790fb81ff436 2164 vcs optional mercurial_2.2.2-4+deb7u2.dsc
 06c072a5f1be9a71eb53fc82af782f1e 50657 vcs optional 
mercurial_2.2.2-4+deb7u2.debian.tar.gz
 4d5de4fb9280473937204150504ddaaa 2324960 vcs optional 
mercurial-common_2.2.2-4+deb7u2_all.deb
 1ce86af92568a418bddf9db911f01eed 93336 vcs optional 
mercurial_2.2.2-4+deb7u2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXAvE+AAoJEJ2wI1VW+M+tuGwQAIOumNfqB/jEqxvYY6

Bug#819504: marked as done (mercurial: CVE-2016-3068 CVE-2016-3069 CVE-2016-3630)

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 09:47:55 +
with message-id 
and subject line Bug#819504: fixed in mercurial 3.1.2-2+deb8u2
has caused the Debian Bug report #819504,
regarding mercurial: CVE-2016-3068 CVE-2016-3069 CVE-2016-3630
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.)


-- 
819504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 3.7.2-2
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerabilities were published for mercurial.

CVE-2016-3068[0]:
arbitrary code execution with Git subrepos

CVE-2016-3069[1]:
arbitrary code execution when converting Git repos

CVE-2016-3630[2]:
remote code execution in binary delta decoding

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-3068
[1] https://security-tracker.debian.org/tracker/CVE-2016-3069
[2] https://security-tracker.debian.org/tracker/CVE-2016-3630
[3] https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.7.3_.282016-3-29.29

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 3.1.2-2+deb8u2

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mercurial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Apr 2016 15:41:22 +0200
Source: mercurial
Binary: mercurial-common mercurial
Architecture: source all amd64
Version: 3.1.2-2+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Python Applications Packaging Team 

Changed-By: Julien Cristau 
Description:
 mercurial  - easy-to-use, scalable distributed version control system
 mercurial-common - easy-to-use, scalable distributed version control system 
(common
Closes: 819504
Changes:
 mercurial (3.1.2-2+deb8u2) jessie-security; urgency=high
 .
   * CVE-2016-3630:
 + parsers: fix list sizing rounding error
 + parsers: detect short records
   * CVE-2016-3068:
 + subrepo: set GIT_ALLOW_PROTOCOL to limit git clone protocols
   * CVE-2016-3069:
 + convert: add new, non-clowny interface for shelling out to git
 + convert: rewrite calls to Git to use the new shelling mechanism
 + convert: dead code removal - old git calling functions
 + convert: rewrite gitpipe to use common.commandline
 + convert: test for shell injection in git calls
   Closes: #819504
Checksums-Sha1:
 18764a7b25256dc7b1412ddc7ea3a444dd6e2c34 2273 mercurial_3.1.2-2+deb8u2.dsc
 df69dd5b4b561241c6c70d6a3cc7faaf1932d96a 53104 
mercurial_3.1.2-2+deb8u2.debian.tar.xz
 c08b338aa119e4e50f6665dc2bff6a61786d8435 1601038 
mercurial-common_3.1.2-2+deb8u2_all.deb
 09dd4187518be64d6f3a0cfbc2a303bcb9225737 59998 
mercurial_3.1.2-2+deb8u2_amd64.deb
Checksums-Sha256:
 a9f0e92d27935a0bdcf418260cd1d31552e311cbcf3a7112bc8ada24f73e6927 2273 
mercurial_3.1.2-2+deb8u2.dsc
 7d3c9f6b221605e129f2476c86017b4bb47048c4587e8376888d18d80ef196b0 53104 
mercurial_3.1.2-2+deb8u2.debian.tar.xz
 52c1e914ca57743c5e331f6308d0bff755c446b21e86491ca9f3339d26dfa643 1601038 
mercurial-common_3.1.2-2+deb8u2_all.deb
 bcd724239c207424520a871956663bd55d265e1ad5b93dd91aefdaa2df6e 59998 
mercurial_3.1.2-2+deb8u2_amd64.deb
Files:
 3e98ecc94ceed22414f308977c5c33ce 2273 vcs optional mercurial_3.1.2-2+deb8u2.dsc
 09443346fcd32df0e48d42c0d9e9fbb7 53104 vcs optional 
mercurial_3.1.2-2+deb8u2.debian.tar.xz
 0178734936ac3e7c0da633b8826cdf2b 1601038 vcs optional 
mercurial-common_3.1.2-2+deb8u2_all.deb
 06da0420aa8c640110c603fbb63429f2 59998 vcs optional 
mercurial_3.1.2-2+deb8u2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXAuJgAAoJEJ2wI1VW+M+tCyMP/2KTVmxqxwThvcnOjxfL0Dvx
2uqgZTbnlyeuPt5R65x0lCIUiRKjFjb0ESM+pBr7MnlCOvlRDC1dFkWaDPjfKm7G
UD9CnoAlx09Lg

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

[Sebastiaan Couwenberg]

On Wed, 8 Jul 2015 09:31:46 +0200 Jérémy Lal wrote:
> 2015-07-07 23:43 GMT+02:00 Emilio Pozuelo Monfort :
> > Your package fails to build against mapnik 3.0.0:
> 
> Thanks, it's going to be like this until gcc5 and latest boost libs are
> available (which should be this summer).

More recent node-mapnik versions are required for their Mapnik 3.x
support, but these require the unpackaged node-pre-gyp to build.

Perhaps it's better to remove node-mapnik and its reverse dependencies
from the archive since they haven't seen any activity in over two years.

Kind Regards,

Bas

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

Processed (with 2 errors): Status update

[Debian Bug Tracking System]

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

> outlook 820331
Removed outlook
> Asked upstream whether original author wants to fix this / has a
Unknown command or malformed arguments to command.
> preferred temp file creation method. Otherwise I'll patch with mktemp.
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#743388: t4kcommon: diff for NMU version 0.1.1-1.1

[Holger Levsen]

Hi Tobi,

On Thu, Apr 07, 2016 at 09:17:25PM +0200, Tobias Frost wrote:
> I've prepared an NMU for t4kcommon (versioned as 0.1.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

thanks for your work on t4kcommon and the whole libpng transition! Much
appreciated.


thanks,
Holger


signature.asc
Description: Digital signature

Processed (with 2 errors): Status update

[Debian Bug Tracking System]

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

> outlook 820331 Asked upstream whether original author wants to fix this
Outlook recorded from message bug 820331 message 
> / has a preferred temp file creation method. Otherwise I'll patch with
Unknown command or malformed arguments to command.
> mktemp.
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#818515: iulib: diff for NMU version 0.3-3.3

[Gianfranco Costamagna]

Control: tags 818515 + patch
Control: tags 818515 + pending

Dear maintainer,

I've prepared an NMU for iulib (versioned as 0.3-3.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

I'm not sure about your workaround in rules file, but they seems
to be some really old stuff, I think autoreconf handles them correctly.
http://debomatic-amd64.debian.net/distribution#unstable/iulib/0.3-3.3/buildlog
I also bumped compat level, because I'm not sure about the multiarch stuff
Hope you don't mind it :)

Regards.

Gianfranco
diff -Nru iulib-0.3/debian/changelog iulib-0.3/debian/changelog
--- iulib-0.3/debian/changelog  2016-01-23 18:32:44.0 +0100
+++ iulib-0.3/debian/changelog  2016-04-08 11:03:31.0 +0200
@@ -1,3 +1,11 @@
+iulib (0.3-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to autoreconf (Closes: #818515).
+  * Bump compat level to 9 and std-version to 3.9.8.
+
+ -- Gianfranco Costamagna   Fri, 08 Apr 2016 
11:02:55 +0200
+
 iulib (0.3-3.2) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru iulib-0.3/debian/compat iulib-0.3/debian/compat
--- iulib-0.3/debian/compat 2011-10-21 21:32:10.0 +0200
+++ iulib-0.3/debian/compat 2016-04-08 11:03:34.0 +0200
@@ -1 +1 @@
-7
+9
diff -Nru iulib-0.3/debian/control iulib-0.3/debian/control
--- iulib-0.3/debian/control2016-01-23 18:18:11.0 +0100
+++ iulib-0.3/debian/control2016-04-08 11:02:28.0 +0200
@@ -3,8 +3,8 @@
 Priority: optional
 Maintainer: Jeffrey Ratcliffe 
 Uploaders: Jakub Wilk 
-Build-Depends: debhelper (>= 7.0.50~), autotools-dev, automake1.11, libtool 
(>= 2), libpng-dev, libjpeg-dev, libtiff-dev, libsdl-gfx1.2-dev, 
libsdl-image1.2-dev, dpkg-dev (>= 1.16)
-Standards-Version: 3.9.2
+Build-Depends: debhelper (>= 9), dh-autoreconf, libpng-dev, libjpeg-dev, 
libtiff-dev, libsdl-gfx1.2-dev, libsdl-image1.2-dev, dpkg-dev (>= 1.16)
+Standards-Version: 3.9.8
 Homepage: http://code.google.com/p/iulib/

 Package: libiulib0
diff -Nru iulib-0.3/debian/rules iulib-0.3/debian/rules
--- iulib-0.3/debian/rules  2011-10-28 14:55:39.0 +0200
+++ iulib-0.3/debian/rules  2016-04-08 11:02:53.0 +0200
@@ -8,25 +8,4 @@
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)

 %:
-   dh $@
-
-override_dh_auto_configure:
-   mv aclocal.m4 aclocal.m4.old
-   mv configure configure.old
-   mv Makefile.in Makefile.in.old
-   cp /usr/share/libtool/config/ltmain.sh .
-   aclocal
-   autoconf
-   automake --add-missing
-   ./configure \
-   --prefix=/usr \
-   --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
-
-clean:
-   dh_testdir
-   dh_auto_clean
-   dh_clean config.guess config.sub ltmain.sh
-   [ ! -f aclocal.m4.old ] || mv aclocal.m4.old aclocal.m4
-   [ ! -f configure.old ] || mv configure.old configure
-   [ ! -f Makefile.in.old ] || mv Makefile.in.old Makefile.in
-
+   dh $@ --with autoreconf



signature.asc
Description: OpenPGP digital signature

Processed: iulib: diff for NMU version 0.3-3.3

[Debian Bug Tracking System]

Processing control commands:

> tags 818515 + patch
Bug #818515 [iulib] iulib: FTBFS: '/usr/share/libtool/config/ltmain.sh': No 
such file or directory
Added tag(s) patch.
> tags 818515 + pending
Bug #818515 [iulib] iulib: FTBFS: '/usr/share/libtool/config/ltmain.sh': No 
such file or directory
Added tag(s) pending.

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

Processed: Re: Bug#810945: Useless dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #810945 [src:odin] odin: please drop build-dependency on removed libdcmtk2
Severity set to 'serious' from 'important'

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

Bug#820297: silly: FTBFS on several architectures

[Tobias Frost]

Package: src:silly
Followup-For: Bug #820297

Dear Muammar,  

in the hope this helps, I did de-filt the symbols and it seems that size_t 
changed from long to int:

One function that changed signature is: 
MemoryDataSource::MemoryDataSource(const byte* data, size_t size)

so the size_t change is:
- SILLY::MemoryDataSource::MemoryDataSource(unsigned char const*, unsigned 
long)@Base 0.1.0
+ SILLY::MemoryDataSource::MemoryDataSource(unsigned char const*, unsigned 
int)@Base 0.1.0-5

the second is also size_t related:
void PNG_read_function(png_structp png_ptr, png_bytep data, png_size_t length)
- SILLY::PNG_read_function(png_struct_def*, unsigned char*, unsigned long)@Base 
0.1.0
+ SILLY::PNG_read_function(png_struct_def*, unsigned char*, unsigned int)@Base 
0.1.0-5


-- 
tobi

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

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

Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

[Aurelien Jarno]

Hi,

On 2016-04-07 11:51, James Cowgill wrote:
> Hi,
> 
> I've managed to find the cause of the openmpi segfault (#818909). It
> might affect a number of different packages.

Thanks for working on that.

> The segfault is caused by the interaction of the
> new DT_MIPS_RLD_MAP_REL dynamic tag (from binutils 2.26) and chrpath.
> Unlike all other tags, this tag is relative to the offset of the tag
> within the executable. chrpath is used to remove rpaths from ELF files.
> It does this by moving all of the other dynamic tags up one entry, but
> since the DT_MIPS_RLD_MAP_REL is not updated, it now points to an
> incorrect offset. The dynamic linker will then overwrite some other
> memory when processing the DT_MIPS_RLD_MAP_REL tag.
> 
> The openmpi segfault was caused by a global variable being initialized
> incorrectly (overwritten by the dynamic linker). I expect other
> executables using chrpath will also be affected - possibly in strange
> ways (not nessesarily a segfault).
> 
> It also seems that at least cmake uses the same technique for removing
> the RPATH so any cmake reverse dependencies could be affected. The
> DT_MIPS_RLD_MAP_REL is only created for executables which limits the
> effect of this slightly. Only packages built using binutils
> >= 2.25.51.20151014-1 will be affected.

It seems the other condition is to use glibc 2.22, which contains the
following corresponding commits:

| commit a2057c984e4314c3740f04cf54e36c824e4c8f32
| Author: Matthew Fortune 
| Date:   Thu Jun 11 10:43:48 2015 +0100
| 
| Add support for DT_MIPS_RLD_MAP_REL.
| 
| This tag allows debugging of MIPS position independent executables
| and provides access to shared library information.
| 
| * elf/elf.h (DT_MIPS_RLD_MAP_REL): New macro.
| (DT_MIPS_NUM): Update.
| * sysdeps/mips/dl-machine.h (ELF_MACHINE_DEBUG_SETUP): Handle
| DT_MIPS_RLD_MAP_REL.

Maybe we can temporarily revert this commit until the problem is fixed
in chrpath and the packages are rebuilt. 

> There is a convinient way to test if a package is broken using the
> presence of the old DT_MIPS_RLD_MAP tag. When correct
> (DT_MIPS_RLD_MAP_REL + tag offset + executable base address) equals
> DT_MIPS_RLD_MAP, so someone could analyze the archive to find which
> packages are affected (any if any tools other than chrpath and cmake
> are broken).
> 
> Based only on chrpath and cmake reverse dependencies, there is an upper
> bound of about 1500 binNMUs (after the tools after fixed). Hopefully
> that can be reduced!
>
> I really don't have any time to fix all this. Please can someone else
> have a look!

I'll try to do an archive scan asap to really get an idea on how many
packages are affected. After I'll look at how to fix chrpath, but help
would be welcome as I also don't have a lot of time.

> OpenMPI maintainers (and anyone else affected):
> One possible workaround is to use chrpath -r ""  on mips*
> architectures until this is fixed since that command does not cause any
> tags to be moved. It has a tiny performance penalty but should
> otherwise work properly.

Thanks for the workaround.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#820178: marked as done (new upload broke ruby-re2 (in turn broke gitlab))

[Debian Bug Tracking System]

Your message dated Fri, 08 Apr 2016 08:00:45 +
with message-id 
and subject line Bug#820178: fixed in re2 20160401+dfsg-2
has caused the Debian Bug report #820178,
regarding new upload broke ruby-re2 (in turn broke gitlab)
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.)


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

Hi,

on a Debian unstable system with all packages upgraded, following is
happening when I try installing the gitlab package:

Using sass-rails 5.0.3
Using redis-rails 4.0.0
Using turbolinks 2.5.3
Using devise 3.5.6
Using dropzonejs-rails 0.7.1
Using jquery-turbolinks 2.1.0
Using devise-async 0.9.0
Using devise-two-factor 2.0.0
Bundle complete! 121 Gemfile dependencies, 253 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
Running final rake tasks...
Creating secrets.yml...
Initializing database...
*** Error in `/usr/bin/ruby': malloc(): memory corruption: 0x0af3f8f0 
***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x71ff5)[0x7f4915eeaff5]
/lib/x86_64-linux-gnu/libc.so.6(+0x77946)[0x7f4915ef0946]
/lib/x86_64-linux-gnu/libc.so.6(+0x79a99)[0x7f4915ef2a99]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f4915ef4374]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_Znwm+0x18)[0x7f490e675ae8]
/usr/lib/x86_64-linux-gnu/libre2.so.1v5(+0x41952)[0x7f4906a4b952]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xe4e9)[0x7f4916be74e9]
/usr/lib/x86_64-linux-gnu/libre2.so.1v5(_ZN3re23RE24InitERKNS_11StringPieceERKNS0_7OptionsE+0x80)[0x7f4906a4f5e0]
/usr/lib/x86_64-linux-gnu/libre2.so.1v5(_ZN3re23RE2C2EPKc+0xe3)[0x7f4906a509d3]
/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/re2.so(+0x4012)[0x7f4906c8d012]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18cd1e)[0x7f4916f82d1e]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18d8a2)[0x7f4916f838a2]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_class_new_instance+0x21)[0x7f4916eb7ec1]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1822eb)[0x7f4916f782eb]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1901d3)[0x7f4916f861d3]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x191203)[0x7f4916f87203]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x186059)[0x7f4916f7c059]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18ae72)[0x7f4916f80e72]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x77259)[0x7f4916e6d259]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x78e18)[0x7f4916e6ee18]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_require_safe+0x9)[0x7f4916e6f119]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1822eb)[0x7f4916f782eb]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x186059)[0x7f4916f7c059]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18ae72)[0x7f4916f80e72]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_yield+0x364)[0x7f4916f879e4]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_ary_each+0x3d)[0x7f4916e2671d]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1822eb)[0x7f4916f782eb]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x185f8c)[0x7f4916f7bf8c]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18ae72)[0x7f4916f80e72]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_yield+0x364)[0x7f4916f879e4]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_ary_each+0x3d)[0x7f4916e2671d]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1822eb)[0x7f4916f782eb]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1901d3)[0x7f4916f861d3]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x191203)[0x7f4916f87203]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x185f8c)[0x7f4916f7bf8c]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18ae72)[0x7f4916f80e72]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x77259)[0x7f4916e6d259]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x78e18)[0x7f4916e6ee18]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(rb_require_safe+0x9)[0x7f4916e6f119]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1822eb)[0x7f4916f782eb]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x1901d3)[0x7f4916f861d3]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x191203)[0x7f4916f87203]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x186059)[0x7f4916f7c059]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x18ae72)[0x7f4916f80e72]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x77259)[0x7f4916e6d259]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x7787d)[0x7f4916e6d87d]
/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3(+0x77959)[0x7f4916e6d959]

Bug#820182: Debian Bug #820182 (freeze when scrolling)

[Dr. Johannes-Heinrich Vogeler]

I have the same problem on a system with RADEON HD 6450 graphics card;
on my second computer with NVIDIA Geforce all is running flawless. Probably
the issue is due to the RADEON module.

Regards

Johannes-Heinrich Vogeler
-- 
Dr. Johannes-Heinrich Vogeler
Am Kiesgrund 16 b
D-16548 Glienicke/Nordbahn
e-mail: auc...@t-online.de

Bug#650575: rescheduling

[Gianfranco Costamagna]

Hi Bas!

Nope, I don't care about the package (I don't even know what it does do :) )

if you don't need it anymore, and it has no reverse-dependencies you might 
consider an RM on
ftpmasters ;)


I rescheduled because we want this transition to end soon(TM), and I want every 
package fixed,
to avoid breaking of them on testing.

thanks for understanding!

Gianfranco


Il Venerdì 8 Aprile 2016 9:24, Bas Zoetekouw  ha scritto:
Thanks for the fix and NMU!  Are you perhaps interested in taking over
this package?  I don't use it anymore, and wouldn't mind giving it away.

Gr,
BAs.

On 08-04-16 08:09, Gianfranco Costamagna wrote:
> rescheduling because of #819477.
> 

-- 
And what shoulder and what art
Could twist the sinews of thy heart?
And when thy heart began to beat
What dread hand and what dread feet?

Bug#650575: rescheduling

[Bas Zoetekouw]

Thanks for the fix and NMU!  Are you perhaps interested in taking over
this package?  I don't use it anymore, and wouldn't mind giving it away.

Gr,
BAs.

On 08-04-16 08:09, Gianfranco Costamagna wrote:
> rescheduling because of #819477.
> 

-- 
 And what shoulder and what art
 Could twist the sinews of thy heart?
 And when thy heart began to beat
 What dread hand and what dread feet?



signature.asc
Description: OpenPGP digital signature

Bug#761544: libtruth-java: FTBFS: xargs: /usr/lib/jvm/java-7-openjdk-*/bin/javac: No such file or directory

[Logan Rosen]

Package: libtruth-java
Version: 0.7.0-1
Followup-For: Bug #761544
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/control: Build-depend on default-jdk instead of java7-jdk.
  * debian/rules: Don't manually set JAVA_HOME.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-17-generic (SMP w/2 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)
diff -Nru libtruth-java-0.7.0/debian/control libtruth-java-0.7.0/debian/control
--- libtruth-java-0.7.0/debian/control	2012-08-29 14:55:57.0 +
+++ libtruth-java-0.7.0/debian/control	2016-04-08 06:46:45.0 +
@@ -2,7 +2,7 @@
 Section: java
 Priority: extra
 Maintainer: Brian Thomason 
-Build-Depends: debhelper (>= 8.0.0), ant-optional, java7-jdk, javahelper
+Build-Depends: debhelper (>= 8.0.0), ant-optional, default-jdk, javahelper
 Build-Depends-Indep: maven-repo-helper, junit4
 Standards-Version: 3.9.3
 Homepage: https://github.com/truth0/truth
diff -Nru libtruth-java-0.7.0/debian/rules libtruth-java-0.7.0/debian/rules
--- libtruth-java-0.7.0/debian/rules	2012-08-29 14:59:27.0 +
+++ libtruth-java-0.7.0/debian/rules	2016-04-08 03:41:20.0 +
@@ -1,7 +1,6 @@
 #!/usr/bin/make -f
 
 PACKAGE   := libtruth-java
-export JAVA_HOME := /usr/lib/jvm/java-7-openjdk-*
 export CLASSPATH := /usr/share/java/junit4.jar
 
 %:

Bug#800204: pygopherd: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: pygopherd
Version: 2.0.18.3+nmu4
Followup-For: Bug #800204
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Use dh_prep instead of dh_clean -k.
- Add recommended build-arch and build-indep targets.
- Remove example doc-base file.
- Don't allow $(MAKE) clean to ignore errors.
  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9) and dh-python.
- Move python to Build-Depends since clean needs it.
- Depend on ${misc:Depends}.
  * debian/conffiles: Remove, since debhelper automatically adds conffiles in
/etc.
  * debian/copyright:
- Remove "(s)" from "Upstream Author(s)" to satisfy Lintian.
- Replace old FSF address with new one.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-17-generic (SMP w/2 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)
diff -Nru pygopherd-2.0.18.3+nmu4/debian/compat pygopherd-2.0.18.3+nmu4ubuntu1/debian/compat
--- pygopherd-2.0.18.3+nmu4/debian/compat	1970-01-01 00:00:00.0 +
+++ pygopherd-2.0.18.3+nmu4ubuntu1/debian/compat	2016-04-08 04:37:42.0 +
@@ -0,0 +1 @@
+9
diff -Nru pygopherd-2.0.18.3+nmu4/debian/conffiles pygopherd-2.0.18.3+nmu4ubuntu1/debian/conffiles
--- pygopherd-2.0.18.3+nmu4/debian/conffiles	2008-03-02 21:51:01.0 +
+++ pygopherd-2.0.18.3+nmu4ubuntu1/debian/conffiles	1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-/etc/pygopherd/pygopherd.conf
diff -Nru pygopherd-2.0.18.3+nmu4/debian/control pygopherd-2.0.18.3+nmu4ubuntu1/debian/control
--- pygopherd-2.0.18.3+nmu4/debian/control	2013-06-30 12:30:23.0 +
+++ pygopherd-2.0.18.3+nmu4ubuntu1/debian/control	2016-04-08 06:45:35.0 +
@@ -2,8 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: John Goerzen 
-Build-Depends-Indep: debhelper (>> 5.0.37.2), python (>= 2.6.6-3~)
-Build-Depends: debhelper (>= 5.0.37.2)
+Build-Depends: debhelper (>= 9), python (>= 2.6.6-3~), dh-python
 Standards-Version: 3.5.2
 Homepage: gopher://gopher.quux.org/1/devel/gopher/pygopherd
 Vcs-Git: git://git.complete.org/pygopherd
@@ -11,7 +10,7 @@
 
 Package: pygopherd
 Architecture: all
-Depends: python, mime-support, logrotate, python-simpletal, ${python:Depends}
+Depends: ${misc:Depends}, python, mime-support, logrotate, python-simpletal, ${python:Depends}
 Provides: gopher-server
 Description: Modular Multiprotocol Gopher/HTTP/WAP Server in Python
  This is an all-new, modern Gopher server.  It can serve documents
@@ -28,7 +27,7 @@
 
 Package: pygfarm
 Architecture: all
-Depends: pygopherd (>= ${Source-Version}), python-dictclient (>= 1.0.1)
+Depends: ${misc:Depends}, pygopherd (>= ${Source-Version}), python-dictclient (>= 1.0.1)
 Description: Collection of add-on modules for Pygopherd
  These add-on modules provide additional functionality for
  your Pygopherd server.
diff -Nru pygopherd-2.0.18.3+nmu4/debian/copyright pygopherd-2.0.18.3+nmu4ubuntu1/debian/copyright
--- pygopherd-2.0.18.3+nmu4/debian/copyright	2008-04-10 13:56:55.0 +
+++ pygopherd-2.0.18.3+nmu4ubuntu1/debian/copyright	2016-04-08 05:20:15.0 +
@@ -3,7 +3,7 @@
 
 It was downloaded from http://quux.org/give-me-gopher/
 
-Upstream Author(s): John Goerzen 
+Upstream Author: John Goerzen 
 
 Copyright:
 
@@ -20,7 +20,7 @@
 
 You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
-Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
 
 Debian GNU/Linux may find the GNU General Public License, version 2, in
 /usr/share/common-licenses/GPL-2.
diff -Nru pygopherd-2.0.18.3+nmu4/debian/ex.package.doc-base pygopherd-2.0.18.3+nmu4ubuntu1/debian/ex.package.doc-base
--- pygopherd-2.0.18.3+nmu4/debian/ex.package.doc-base	2008-03-02 21:51:01.0 +
+++ pygopherd-2.0.18.3+nmu4ubuntu1/debian/ex.package.doc-base	1970-01-01 00:00:00.0 +
@@ -1,22 +0,0 @@
-Document: pygopherd
-Title: Debian pygopherd Manual
-Author: 
-Abstract: This manual describes what pygopherd is
- and how it can be used to
- manage online manuals on Debian systems.
-Section: unknown
-
-Format: debiandoc-sgml
-Files: /usr/share/doc/pygopherd/pygopherd.sgml.gz
-
-Format: postscript
-Files: /usr/share/doc/pygopherd/pygopherd.ps.gz
-
-Format: text
-Files: /usr/share/doc/pygopherd/pygopherd.text.gz
-
-Format: HTML
-Index: /usr/share/doc/pygopherd/html/index.html

Bug#805389: signon-ui: runaway dbus-daemon during build

[Santiago Vila]

On Thu, 7 Apr 2016, Diane Trout wrote:

> I wasn't able to replicate this issue with an amd64-unstable sbuild chroot on 
> my system. I ran it in several times in case it was a intermittent failure.
> 
> for a in $(seq 10) ; do sbuild -c unstable-amd64-sbuild signon-
> ui_0.17+15.10.20150810-2.dsc ; done
> 
> Do you have any thoughts what might be different about our build environments?

I can reproduce it every time.

My system is a QEMU/KVM virtual machine with 4GB RAM + 4GB swap running jessie.

I'm using sbuild 0.68.0-1~bpo8+1 from jessie-backports.

I call sbuild this way:

sbuild -A -d stretch signon-ui_0.17+15.10.20150810-2

The build happens normally but only until this point:

[...]
dpkg-genchanges: warning: package signon-ui-x11-dbgsym listed in files list but 
not in control info
dpkg-genchanges: binary-only upload (no source code included)
 dpkg-source --after-build signon-ui-0.17+15.10.20150810
 dpkg-buildpackage: binary-only upload (no source included)
---

At this point, it hangs and does nothing else.

When you finally kill the dbus-daemon process by hand, the remaining
build log appears:

---
Build finished at 20160408-0111

Finished

[...]
---

Hope this helps.

Thanks.