Bug#800416: pbuilder: ships files belonging to -uml

[Aaron M. Ucko]

Package: pbuilder
Version: 0.217
Severity: serious
Justification: Policy 6.6(4)

pbuilder and pbuilder-uml both ship copies of some files that belong
only in the latter, which is consequently uninstallable without
--force-overwrite:

  /etc/pbuilder/pbuilder-uml.conf
  /usr/share/pbuilder/pbuilder-uml.conf
  /usr/lib/pbuilder/pdebuild-uml-checkparams
  /usr/lib/pbuilder/pbuilder-uml-checkparams
  /usr/bin/pdebuild-user-mode-linux
  /usr/bin/pbuilder-user-mode-linux

Could you please take a look?

Thanks!

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

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

Versions of packages pbuilder depends on:
ii  cdebconf [debconf-2.0]  0.195
ii  coreutils   8.23-4
ii  debconf [debconf-2.0]   1.5.57
ii  debianutils 4.5.1
ii  debootstrap 1.0.72
ii  dpkg-dev1.18.3
ii  wget1.16.3-3

Versions of packages pbuilder recommends:
ii  devscripts  2.15.8
ii  fakeroot1.20.2-1
ii  iproute24.1.1-1
ii  net-tools   1.60+git20150829.73cef8a-1
ii  sudo1.8.12-1

Versions of packages pbuilder suggests:
ii  cowdancer 0.73
ii  gdebi-core0.9.5.7
ii  pbuilder-uml  0.217

-- debconf information excluded

Bug#797043: xul-ext-noscript: menu no longer shows script sources after iceweasel 41.0-1

[Christian Kujau]

I'm using Iceweasel/release on Debian/Jessie and had the same error after 
the last Iceweasel upgrade (40.0.3-3 => 41.0-1).

In fact, NoScript was reported as "not compatible with v41" in 
about:addons and I could not even re-enable it after I disabled it 
temporarily to try to get the menu back again.

However, I think it may be too much work to maintain different versions of 
every Mozilla addon for every flavour of Iceweasel versions (esr, 
release, beta, aurora, testing, etc...).

For now I've switched to the upstream version of NoScript and the menu is back.

Thanks,
Christian.

Bug#799593: kde-config-systemd FTBFS because of missed systemd build dependency

[Shawn Sörbom]

For some reason, I didn't see your bug until I got a removal request from 
testing. Sorry.
On Sunday, September 20, 2015 19:17:05 Alf Gaida wrote:
> Source: kde-config-systemd
> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the
> past)
> 
> Hi,
> building the package in pbuilder fails:
> -- checking for module 'systemd'
> --   package 'systemd' not found
> CMake Error at /usr/share/cmake-3.2/Modules/FindPkgConfig.cmake:340
> (message): A required package was not found
> Call Stack (most recent call first):
>   /usr/share/cmake-3.2/Modules/FindPkgConfig.cmake:502
> (_pkg_check_modules_internal) CMakeLists.txt:36 (pkg_check_modules)
> 
> Adding systemd to build dependencies solve this
> 
> Cheers Alf
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers buildd-unstable
>   APT policy: (990, 'buildd-unstable'), (990, 'unstable'), (500,
> 'experimental') Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.0.5-5-ck-amd64 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#798436: odin: please make it build with vtk6 (or at least vtk-5.10)

[Gianfranco Costamagna]

Control: fixed -1 1.8.8-1.1


Closing.

Processed: Re: odin: please make it build with vtk6 (or at least vtk-5.10)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.8.8-1.1
Bug #798436 [src:odin] odin: please make it build with vtk6 (or at least 
vtk-5.10)
Marked as fixed in versions odin/1.8.8-1.1.

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

Bug#800014: multipath-udeb: not installable: depends on libsystemd0

[Cyril Brulebois]

[ Adding debian-b...@lists.debian.org back. ]

Ritesh Raj Sarraf  (2015-09-28):
> Adding systemd maintainers
> 
> 
> Hello Cyril,
> 
> THank you for the bug report.
> 
> 
> On Fri, 2015-09-25 at 11:59 +0200, Cyril Brulebois wrote:
> > Package: multipath-udeb
> > Version: 0.5.0+git0.770e6d0d-3
> > Severity: grave
> > Justification: renders package unusable
> > 
> > 
> > [ Please keep debian-b...@lists.debian.org in the loop. ]
> > 
> > Hi,
> > 
> > Your package in unstable gained a dependency which cannot be
> > satisfied:
> > libsystemd0 has no udeb. It's therefore no longer installable, along
> > with partman-multipath which depends on it.
> 
> This was intentionally done because upstream added systemd dependency
> some time ago. For Jessie, I had disabled systemd support, but now, it
> makes sense to have it, and align with upstream and other
> distributions.
> 
> So, I think the real question is about why libsystemd0 does not have a
> udeb ?
> 
> systemd maintainers should provide that input.

Some input from someone who doesn't know a thing about systemd or
multipath: libmultipath.so.0 has a NEEDED entry on libsystemd.so.0,
which seems to only define symbols named sd_* (which seems fair). The
only use I see in libmultipath.so.0 is sd_listen_fds.

Its manpage says:

   sd_listen_fds() shall be called by a daemon to check for file
   descriptors passed by the init system as part of the socket-based
   activation logic.

There's no systemd in d-i, so there's no socket-based activation logic,
and you can't rely on that in your multipath udeb.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config

[Debian Bug Tracking System]

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

> clone 800371 -1
Bug #800371 [src:glibmm2.4] glibmm2.4: C++11 features in headers but no 
-std=c++11 in pkg-config
Bug 800371 cloned as bug 800399
> reassign -1 libsigc++-2.0
Bug #800399 [src:glibmm2.4] glibmm2.4: C++11 features in headers but no 
-std=c++11 in pkg-config
Bug reassigned from package 'src:glibmm2.4' to 'libsigc++-2.0'.
No longer marked as found in versions glibmm2.4/2.46.1-1.
Ignoring request to alter fixed versions of bug #800399 to the same values 
previously set
> retitle -1 libsigc++-2.0: C++11 features in headers but no -std=c++11 in 
> pkg-config
Bug #800399 [libsigc++-2.0] glibmm2.4: C++11 features in headers but no 
-std=c++11 in pkg-config
Changed Bug title to 'libsigc++-2.0: C++11 features in headers but no 
-std=c++11 in pkg-config' from 'glibmm2.4: C++11 features in headers but no 
-std=c++11 in pkg-config'
> thanks
Stopping processing here.

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

Bug#800123: marked as done (libfile-rsync-perl: Missing dependency on libipc-run3-perl)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 19:04:04 +
with message-id 
and subject line Bug#800123: fixed in libfile-rsync-perl 0.48-2
has caused the Debian Bug report #800123,
regarding libfile-rsync-perl: Missing dependency on libipc-run3-perl
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.)


-- 
800123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unburden-home-dir
Version: 0.3.3
Severity: normal

The package needs libipc-run3-perl for Run3.pm

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

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

Versions of packages unburden-home-dir depends on:
ii  dpkg  1.18.3
ii  libconfig-file-perl   1.50-3
ii  libfile-basedir-perl  0.07-1
ii  libfile-rsync-perl0.48-1
ii  libfile-touch-perl0.09-1
ii  libfile-which-perl1.18-1
ii  perl  5.20.2-6

Versions of packages unburden-home-dir recommends:
ii  lsof4.89+dfsg-0.1
ii  x11-common  1:7.7+9

Versions of packages unburden-home-dir suggests:
pn  agedu   
pn  autotrash   
ii  baobab  3.18.0-1
pn  bleachbit   
pn  corekeeper  
pn  eatmydata   
pn  fslint  
pn  tmpreaper   

-- Configuration Files:
/etc/default/unburden-home-dir changed:
UNBURDEN_HOME=true


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libfile-rsync-perl
Source-Version: 0.48-2

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated libfile-rsync-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Sep 2015 20:49:24 +0200
Source: libfile-rsync-perl
Binary: libfile-rsync-perl
Architecture: source all
Version: 0.48-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Axel Beckert 
Description:
 libfile-rsync-perl - Perl module interface to rsync
Closes: 800123
Changes:
 libfile-rsync-perl (0.48-2) unstable; urgency=medium
 .
   * Also add runtime dependency on libipc-run3-perl. (Closes: #800123)
Checksums-Sha1:
 1a0be646ae2e10a8773f343349f84a85a46f64ef 2163 libfile-rsync-perl_0.48-2.dsc
 f32fa7349328b823569f1f6fea91b259e647ae78 3132 
libfile-rsync-perl_0.48-2.debian.tar.xz
 02d347b8d865708130367c40d9292073eb60c99e 28536 
libfile-rsync-perl_0.48-2_all.deb
Checksums-Sha256:
 6849355ecc5cc81d09c70c40f42615fdb2e82424e14169211b970c1fa309654f 2163 
libfile-rsync-perl_0.48-2.dsc
 15421f94355d514b280f21eae26a4e2996ec4b6aa0ef2722038516c87907b97a 3132 
libfile-rsync-perl_0.48-2.debian.tar.xz
 4c1aaf5d87f9bccbec1340266b1e3c818c30812732fd8cdb0879912ca7a16c9a 28536 
libfile-rsync-perl_0.48-2_all.deb
Files:
 47eea138ca5a73977ddb6abe40455912 2163 perl optional 
libfile-rsync-perl_0.48-2.dsc
 ad6f6b3d3b319c8d1646224092a9f55e 3132 perl optional 
libfile-rsync-perl_0.48-2.debian.tar.xz
 d8269ffc425ee11f7b257b4822c177c8 28536 perl optional 
libfile-rsync-perl_0.48-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWCYv4AAoJEGvmY8daNcl1hTcP/2K/EB4mD9zMYnCnnFkx7T/0
gZrZgwDP3+tA12wGaM1UjSF2UUgjC+XxAQL0e98wW6uMr+Aqx8F144W4yC1piYRg
QGNajCiRC8N8pyxr/y7mK7qTXggnr9Bzj6lJkeD6BXzuvhCYwBnkLHcUTsfPDBJl
HoDjRr2/TlQ75TlzGJF+xbXti6orzgJcbZ2IJkxjIsmE3xye7m9/LH9HQT5WIaHP
7bvbslu05gqcO/X7VzLeqmORhi6xtkAliWubPQjTibJ9f08Ba+RchkZbKWEtIjrl
JCEa+TaMuBsPL81gHCONm4Nqdn88RNcDphsMvespGxdEF2XuRh5qkBFjrNSK8z1Q
zuo1CMn4rYJ/Ebx06EyLEk+r357G2qvP161pR1QxREkjBIIIrJ2eUd2jtJHe9eSy
HffY4aFdFM9xPU2nvmK3zqJ8NdhJicx8lEywnU20yfNsrnIysTOSfVQ/HMQzyN6v

Bug#800014: multipath-udeb: not installable: depends on libsystemd0

[Ritesh Raj Sarraf]

Adding systemd maintainers


Hello Cyril,

THank you for the bug report.


On Fri, 2015-09-25 at 11:59 +0200, Cyril Brulebois wrote:
> Package: multipath-udeb
> Version: 0.5.0+git0.770e6d0d-3
> Severity: grave
> Justification: renders package unusable
> 
> 
> [ Please keep debian-b...@lists.debian.org in the loop. ]
> 
> Hi,
> 
> Your package in unstable gained a dependency which cannot be
> satisfied:
> libsystemd0 has no udeb. It's therefore no longer installable, along
> with partman-multipath which depends on it.

This was intentionally done because upstream added systemd dependency
some time ago. For Jessie, I had disabled systemd support, but now, it
makes sense to have it, and align with upstream and other
distributions.

So, I think the real question is about why libsystemd0 does not have a
udeb ?

systemd maintainers should provide that input.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#800014: multipath-udeb: not installable: depends on libsystemd0

[Ritesh Raj Sarraf]

On Mon, 2015-09-28 at 18:53 +0200, Cyril Brulebois wrote:
> [ Adding debian-b...@lists.debian.org back. ]
> 

Sorry about that.


> > This was intentionally done because upstream added systemd
> > dependency
> > some time ago. For Jessie, I had disabled systemd support, but now,
> > it
> > makes sense to have it, and align with upstream and other
> > distributions.
> > 
> > So, I think the real question is about why libsystemd0 does not
> > have a
> > udeb ?
> > 
> > systemd maintainers should provide that input.
> 
> Some input from someone who doesn't know a thing about systemd or
> multipath: libmultipath.so.0 has a NEEDED entry on libsystemd.so.0,
> which seems to only define symbols named sd_* (which seems fair). The
> only use I see in libmultipath.so.0 is sd_listen_fds.
> 
> Its manpage says:
> 
>sd_listen_fds() shall be called by a daemon to check for file
>descriptors passed by the init system as part of the socket
> -based
>activation logic.
> 
> There's no systemd in d-i, so there's no socket-based activation
> logic,
> and you can't rely on that in your multipath udeb.


Hmmm... I'll look into it later. But when you say "No systemd in d-i",
does it mean that is how it is going to remain ?

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Processed: your mail

[Debian Bug Tracking System]

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

> close 798436
Bug #798436 [src:odin] odin: please make it build with vtk6 (or at least 
vtk-5.10)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#800389: pycuda: needs to be rebuilt against boost 1.58

[Emilio Pozuelo Monfort]

Source: pycuda
Version: 2015.1.2-1
Tags: sid stretch
Severity: serious

Hi,

pycuda needs to be rebuilt to pick a dependency on boost 1.58 instead of boost
1.58. This seems to require manual uploads instead of binNMUs due to the
build-dependency on non-free packages.

Emilio

Bug#800122: python3-babeltrace: Mis-builds when there are multiple python3 versions supported

[Scott Kitterman]

On Sun, 27 Sep 2015 02:07:09 -0400 Scott Kitterman  
wrote:
> Package: python3-babeltrace
> Version: 1.2.4-2
> Severity: grave
> Justification: renders package unusable
> 
> I haven't had time to investigate at all yet, but here's part of the file 
list
> following today's binNMU to add python3.5 as a supported version.  From
> looking at where the symlinks point, I don't think this will work at all.

Looking just a bit at this, it seems something is confusing dh_python3 so it 
tries to rename the symlink and it shouldn't:

   dh_python3 -a
I: dh_python3 fs:90: renaming debian/python3-
babeltrace/usr/lib/python3.4/site-packages/_babeltrace.so to debian/python3-
babeltrace/usr/lib/python3.4/site-packages/_babeltrace.cpython-34m-x86_64-
linux-gnu.so
I: dh_python3 fs:90: renaming debian/python3-
babeltrace/usr/lib/python3.5/site-packages/_babeltrace.so to debian/python3-
babeltrace/usr/lib/python3.5/site-packages/_babeltrace.cpython-35m-x86_64-
linux-gnu.so
I: dh_python3 fs:300: removing symlink: debian/python3-
babeltrace/usr/lib/python3/dist-packages/_babeltrace.cpython-34m-x86_64-linux-
gnu.so
I: dh_python3 fs:302: renaming debian/python3-babeltrace/usr/lib/python3/dist-
packages/_babeltrace.so.0.0.0 to _babeltrace.cpython-34m-x86_64-linux-gnu.so
I: dh_python3 fs:193: removing dangling symlink: debian/python3-
babeltrace/usr/lib/python3/dist-packages/_babeltrace.so.0

Scott K

Processed: tagging 800123

[Debian Bug Tracking System]

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

> tags 800123 + pending
Bug #800123 [libfile-rsync-perl] libfile-rsync-perl: Missing dependency on 
libipc-run3-perl
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:d-feet

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:d-feet
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #797398 (http://bugs.debian.org/797398)
> # Bug title: FTBFS: pep8 complains about: E402 module level import not at top 
> of file
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=754312
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 797398 + fixed-upstream
Bug #797398 [src:d-feet] FTBFS: pep8 complains about: E402 module level import 
not at top of file
Added tag(s) fixed-upstream.
> usertags 797398 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 797398 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:mesa-demos

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:mesa-demos
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #796373 (http://bugs.debian.org/796373)
> # Bug title: mesa-demos: FTBFS: error: 'EGL_SCREEN_BIT_MESA' undeclared 
> (first use in this function)
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=91643
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 796373 + fixed-upstream
Bug #796373 [src:mesa-demos] mesa-demos: FTBFS: error: 'EGL_SCREEN_BIT_MESA' 
undeclared (first use in this function)
Added tag(s) fixed-upstream.
> usertags 796373 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 796373 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Processed: Re: Bug#800123: unburden-home-dir: Missing dependency: libipc-run3-perl

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libfile-rsync-perl 0.48-1
Bug #800123 [unburden-home-dir] unburden-home-dir: Missing dependency: 
libipc-run3-perl
Bug reassigned from package 'unburden-home-dir' to 'libfile-rsync-perl'.
No longer marked as found in versions unburden-home-dir/0.3.3.
Ignoring request to alter fixed versions of bug #800123 to the same values 
previously set
Bug #800123 [libfile-rsync-perl] unburden-home-dir: Missing dependency: 
libipc-run3-perl
Marked as found in versions libfile-rsync-perl/0.48-1.
> severity -1 serious
Bug #800123 [libfile-rsync-perl] unburden-home-dir: Missing dependency: 
libipc-run3-perl
Severity set to 'serious' from 'normal'
> retitle -1 libfile-rsync-perl: Missing dependency on libipc-run3-perl
Bug #800123 [libfile-rsync-perl] unburden-home-dir: Missing dependency: 
libipc-run3-perl
Changed Bug title to 'libfile-rsync-perl: Missing dependency on 
libipc-run3-perl' from 'unburden-home-dir: Missing dependency: libipc-run3-perl'
> affects -1 unburden-home-dir
Bug #800123 [libfile-rsync-perl] libfile-rsync-perl: Missing dependency on 
libipc-run3-perl
Added indication that 800123 affects unburden-home-dir

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

Bug#800014: multipath-udeb: not installable: depends on libsystemd0

[Cyril Brulebois]

Ritesh Raj Sarraf  (2015-09-28):
> Hmmm... I'll look into it later. But when you say "No systemd in d-i",
> does it mean that is how it is going to remain ?

I'm not sure why there would be a need to change that in the near
future.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: notfound 789670 in python-future

[Debian Bug Tracking System]

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

> notfound 789670 python-future
Bug #789670 {Done: Scott Kitterman } 
[python-future,python-pies2overrides] python-future,python-pies2overrides: 
error when trying to install together
There is no source info for the package 'python-future' at version 
'python-future' with architecture ''
There is no source info for the package 'python-pies2overrides' at version 
'python-future' with architecture ''
Unable to make a source version for version 'python-future'
Ignoring request to alter found versions of bug #789670 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> close 798436
Bug #798436 {Done: Gianfranco Costamagna } 
[src:odin] odin: please make it build with vtk6 (or at least vtk-5.10)
Bug 798436 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#800392: python-numpy: FTBFS on powerpc due to test failure

[Scott Kitterman]

Source: python-numpy
Version: 1:1.9.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Here's the build-log excerpt:

test_basic (test_multiarray.TestChoose) ... ok
test_broadcast1 (test_multiarray.TestChoose) ... ok
test_broadcast2 (test_multiarray.TestChoose) ... ok
test_basic (test_multiarray.TestClip) ... python2.7-dbg: 
numpy/core/src/multiarray/lowlevel_strided_loops.c.src:820: 
_aligned_contig_cast_double_to_longdouble: Assertion `npy_is_aligned(dst, 
__builtin_offsetof (struct {char c; npy_longdouble v;}, v))' failed.
Running unit tests for numpy
NumPy version 1.9.2
NumPy is installed in 
/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/numpy
Python version 2.7.10 (default, Sep 13 2015, 20:30:50) [GCC 5.2.1 20150911]
nose version 1.3.6
Aborted
make[1]: *** [override_dh_auto_install] Error 134
debian/rules:147: recipe for target 'override_dh_auto_install' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [binary-arch] Error 2
debian/rules:15: recipe for target 'binary-arch' failed

Seems like this may be related to #702169.

Resolution of this bug will be an issue with making python3.5 the default
python3, so it would be good to get this resolved soon.

Thanks,

Scott K

Bug#798601: Bug Analyzation

[Roelof Berg]

I assume, the software is ok but the test automation is not. The 
'algorithm under test' gives a bit fuzzy results depending on the 
multicore calling order and depending on numerical rounding issues. 
Therefore the automated tests accept results within a range of plausible 
values.  Seems that one of the automated tests is too strict. This is 
probably best fixed by upstream (which is also me, have I told about my 
multiple personality disorder yet ? :).


Regards, Roelof

Bug#800407: woo: FTBFS with python3.5 due to test failures

[Scott Kitterman]

Package: woo
Version: 1.0-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Here is an excerpt from the build log from the binNMU to add python3.5
support:

pybuild --test -i python{version} -p "3.5 3.4" --dir .
I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 
-m unittest discover -v 
woo (unittest.loader._FailedTest) ... ERROR

==
ERROR: woo (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: woo
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/woo/__init__.py", line 125, 
in 
import minieigen
ImportError: No module named 'minieigen'


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13
make: *** [build-arch] Error 25
debian/rules:7: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
────
Build finished at 20150928-2128

Scott K

Bug#800318: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations

[Aurelien Jarno]

Hi

On 2015-09-28 18:17, Andreas Cadhalpun wrote:
> Hi Aurelien,
> 
> On 28.09.2015 14:48, Aurelien Jarno wrote:
> > On 2015-09-27 23:43, Andreas Cadhalpun wrote:
> >> A slightly larger test case for mips is compiling ffmpeg...
> > 
> > It what I did to test if the failure is due to the above changes.
> > ffmpeg builds fine with gcc version 5.2.1-17 and -march=mips2
> > -mtune=mips32 (instead of the new default -march=mips32r2), and passes
> > the testsuite. I'll see if I can isolate a smaller testcase so that we
> > can understand the problem.
> 
> Attached is a testcase for mips, but it works fine for mipsel.
> 
> One more peculiarity I noticed is that adding 'c->A = 1;' to
> an unused code path inverts the behavior: It works with
> -fexpensive-optimizations, but fails with -fno-expensive-optimizations.

Big thanks for working on that. I have done some tests with it and
-mtune=mips32r2 is the culprit not -march=mips32r2. This is kind of
unexpected, but at least it is consistent with the mipsel issue. This
means the optimization happens when scheduling the instructions. This
also means we have an easy workaround without lowering the ISA. I'll
commit that so that's in the next gcc upload.

I'll also try to better understand the issue so that I can report the
bug upstream.

Aurelien

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

Bug#800356: libpango1.0-udeb: not installable: depends on libthai0

[Cyril Brulebois]

Cyril Brulebois  (2015-09-28):
> Package: libpango1.0-udeb
> Version: 1.38.0-1
> Severity: grave
> Justification: renders package unusable
> 
> [ Please keep debian-b...@lists.debian.org in copy. ]
> 
> Hi,
> 
> Your package is no longer installable since it gained a dependency on a
> library package which has no udeb variant: libthai0.
> 
> This makes all these packages uninstallable:
>   cdebconf-gtk-entropy
>   cdebconf-gtk-terminal
>   cdebconf-gtk-udeb
>   gtk2-engines-udeb
>   libgtk2.0-0-udeb
>   libpango1.0-udeb
>   libvte9-udeb
>   matchbox-keyboard-udeb

Just to let debian-boot@ know: this was swiftly fixed, thanks!
  https://packages.qa.debian.org/p/pango1.0/news/20150928T153904Z.html

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#796488: Temporary fix

[Santiago Vila]

Hi.

The following trivial patch undoes the failed conversion from
dh_pysupport to dh_python2 and does not change anything else.

I suggest an upload with urgency=high. There will be plenty of time to
do the dh-python2 thing "right" afterwards.

Thanks.diff -ru 333/debian/control 444/debian/control
--- 333/debian/control  2015-08-19 22:37:23.0 +0200
+++ 444/debian/control  2015-09-28 13:35:00.297756378 +0200
@@ -4,7 +4,7 @@
 Maintainer: Carl Chenet 
 Uploaders: Python Applications Packaging Team 

 Standards-Version: 3.8.3
-Build-Depends: debhelper (>= 7), cdbs (>= 0.4.43), python (>= 2.3.5-11), 
dh-python
+Build-Depends: debhelper (>= 7), cdbs (>= 0.4.43), python (>= 2.3.5-11), 
python-support (>= 0.5.3)
 Homepage: http://pyzor.sourceforge.net/
 Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/pyzor/trunk/
 Vcs-Browser: http://anonscm.debian.org/viewvc/python-apps/packages/pyzor/trunk/
diff -ru 333/debian/rules 444/debian/rules
--- 333/debian/rules2015-08-19 22:32:11.0 +0200
+++ 444/debian/rules2015-09-28 13:29:45.924961634 +0200
@@ -1,4 +1,5 @@
 #!/usr/bin/make -f
+DEB_PYTHON_SYSTEM=pysupport
 
 include /usr/share/cdbs/1/class/python-distutils.mk
 include /usr/share/cdbs/1/rules/debhelper.mk
@@ -14,4 +15,4 @@
rm -f lib/pyzor/*.pyc lib/pyzor/*.pyo
 
 binary-install/pyzor::
-   dh_python2 -p$(cdbs_curpkg)
+   dh_pysupport -p$(cdbs_curpkg)

Bug#799039: dcmqrscp : index.dat data corruption

[Mathieu Malaterre]

Dear Andreas,

On Mon, Sep 28, 2015 at 4:02 PM, Andreas Tille  wrote:
> Hi Mathieu,
>
> On Tue, Sep 15, 2015 at 09:32:14AM +0200, Mathieu Malaterre wrote:
>> Package: dcmtk
>> Version: 3.6.1~20150629-1
>> Severity: grave
>> Justification: causes non-serious data loss
>>
>> As describe in the previous bug report:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715011#50
>>
>> One cannot simply upgrade dcmtk package without grave data loss
>> (index.dat binary format is not compatible), which should result as
>> -best case- index.dat corruption, or dcmqrscp to segfault and not
>> start.
>>
>> This correspond to the following upstream commit:
>> c8423ab1fcf0273061462697b8eca56f894984c7
>
> I can n ot find this commit under
>
>git clone https://github.com/commontk/DCMTK.git

See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715011#43

> Would you be able to provide a patch incorporating this commit to
> fix the issue?

I've never written a preinstall script before. I'd prefer you find
somebody else.

> Do you think it is better to switch back to the former version of dcmtk?

Given that this is an experimental package and that the
SONAME/SOVERSION scheme is not clear at that point (per upstream), I
would not have uploaded this version at this point in time, but that
is an entirely different issue IMHO.

>> This should be clearly indicated during package upgrades. Marking as
>> grave as I believe the DICOM file themselves are still kept as-is, so
>> this is IMHO not a critical `causes serious data loss`. Upstream may
>> have a finer understanding of the loss.
>
> You perfectly know that I have no contact to upstream and I'm quite busy
> with a lot of stuff.

`perfectly` ? Sorry to disapoint you, but I am not stalking you :)

>  If you are interested to help it would be great to
> discuss the issue with upstream how to fix this issue in Debian in the
> best possible way.  My motivation was simply to avoid the need for a
> migration of two dcmtk versions - one in unstable and one in
> experimental.  I do not feel able to maintain two versions.  May be
> also the later snapshot 3.6.1_20150924 would fix the issue?  Any hint
> would be welcome.

There is no going back. This is not backward compatible, and the
current dcmtk is trashing the memory (one byte of). Anyone using dcmtk
dcmqrscp from jessie should have noticed the crash (per original bug
report). Just display a warning user need to reconstruct the db (I
believe mysql and other such packages are doing this sort of things).

-M

Processed: Re: Bug#800371: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=755750
Bug #800371 [src:glibmm2.4] glibmm2.4: C++11 features in headers but no 
-std=c++11 in pkg-config
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=755750'.

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

Bug#800371: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=755750

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



signature.asc
Description: OpenPGP digital signature

Bug#800356: marked as done (libpango1.0-udeb: not installable: depends on libthai0)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 15:39:05 +
with message-id 
and subject line Bug#800356: fixed in pango1.0 1.38.0-3
has caused the Debian Bug report #800356,
regarding libpango1.0-udeb: not installable: depends on libthai0
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.)


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

[ Please keep debian-b...@lists.debian.org in copy. ]

Hi,

Your package is no longer installable since it gained a dependency on a
library package which has no udeb variant: libthai0.

This makes all these packages uninstallable:
  cdebconf-gtk-entropy
  cdebconf-gtk-terminal
  cdebconf-gtk-udeb
  gtk2-engines-udeb
  libgtk2.0-0-udeb
  libpango1.0-udeb
  libvte9-udeb
  matchbox-keyboard-udeb

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.38.0-3

We believe that the bug you reported is fixed in the latest version of
pango1.0, 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.
Andreas Henriksson  (supplier of updated pango1.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Sep 2015 16:01:38 +0200
Source: pango1.0
Binary: libpango1.0-0 libpango-1.0-0 libpangocairo-1.0-0 libpangoxft-1.0-0 
libpangoft2-1.0-0 libpango1.0-udeb libpango1.0-dev libpango1.0-0-dbg 
libpango1.0-doc gir1.2-pango-1.0 pango1.0-tests
Architecture: source amd64 all
Version: 1.38.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0-dbg - Pango library and debugging symbols
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of internationalized text - minimal 
runtime (udeb)
 libpangocairo-1.0-0 - Layout and rendering of internationalized text
 libpangoft2-1.0-0 - Layout and rendering of internationalized text
 libpangoxft-1.0-0 - Layout and rendering of internationalized text
 pango1.0-tests - Layout and rendering of internationalized text - installed 
tests
Closes: 800356
Changes:
 pango1.0 (1.38.0-3) unstable; urgency=medium
 .
   * Add debian/patches/configure-without-libthai.patch
 - make it possible to disable checking for libthai
   * debian/rules: configure udeb build --without-libthai
 - this avoids the udeb picking up a dependency on libthai which has
   no udeb. (Closes: #800356)
Checksums-Sha1:
 d5341ed52d8c8d62f6559e81f26785b5c1c4e6fc 3169 pango1.0_1.38.0-3.dsc
 5020d67912c5ad67a87b8a40eb14d27ad7833fcb 29420 pango1.0_1.38.0-3.debian.tar.xz
 459c8cd82fa74485d508f0b1ebe1a81395d728fc 220334 
gir1.2-pango-1.0_1.38.0-3_amd64.deb
 3646864dda4ed5d825345c3420ac465f826018b7 307048 
libpango-1.0-0_1.38.0-3_amd64.deb
 e1573e1cfa947601a95c57297ed91f91e17e32c3 657732 
libpango1.0-0-dbg_1.38.0-3_amd64.deb
 79b95fb95e733cccd6c3c663a1e67631fe35f697 202118 
libpango1.0-0_1.38.0-3_amd64.deb
 38efe6766ffa19a7b9ce00b8ec6815533acecc34 476268 
libpango1.0-dev_1.38.0-3_amd64.deb
 de9339e5c349f92da2b2933831f935433924a5f9 386896 
libpango1.0-doc_1.38.0-3_all.deb
 e3480b0f1677bd81ef925a42ac1711492918720b 136866 
libpango1.0-udeb_1.38.0-3_amd64.udeb
 9e99ff7d48835a628f1c3575fdf5460df27037b0 220138 
libpangocairo-1.0-0_1.38.0-3_amd64.deb
 e088ba98a145bcfa8d69171fb37f9d04a93d8bf2 232876 
libpangoft2-1.0-0_1.38.0-3_amd64.deb
 3f52a83d4143072c635eaa3e24ffad81a297549e 214538 
libpangoxft-1.0-0_1.38.0-3_amd64.deb
 6463405c241f720cd2106bd23c3dca99d308db05 281118 
pango1.0-tests_1.38.0-3_amd64.deb
Checksums-Sha256:
 

Bug#800371: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config

[Aurelien Jarno]

Source: glibmm2.4
Version: 2.46.1-1
Severity: serious

glibmm2.4 version 2.46.1-1 started to use C++11 features in the headers
it exports, but pkg-config --cflags doesn't return -std=c++11. Given the
default is still -std=gnu++98 in GCC 5, it causes packages which use
these headers to fails to build.

A build log showing the issue can be found here:

https://buildd.debian.org/status/fetch.php?pkg=inkscape=mips64el=0.91-5%2Bb1=1443446208


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

Kernel: Linux 4.1.0-2-5kc-malta
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#799656: [JsSIP] Re: Bug#799656: NaN 2.x issue

[Iñaki Baz Castillo]

2015-09-24 15:14 GMT+02:00 Daniel Pocock :
> Can anybody from the JsSIP team comment on this?  How do you feel about
> having node-nan 2.x in the dependency hierarchy?  Will you continue
> using node-websocket or would you possibly use node-ws[1] instead?
> Using node-ws instead of node-websocket will reduce the number of
> packages we have to keep track of in Debian.

Initially I used node-ws, and removed it in favor of node-websocket
because node-ws was not good for JsSIP needs. There is no way to move
back to node-ws (in fact, I'm now developer of node-websocket).

Regards.


-- 
Iñaki Baz Castillo

Bug#800318: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations

[Andreas Cadhalpun]

Hi Aurelien,

On 28.09.2015 14:48, Aurelien Jarno wrote:
> On 2015-09-27 23:43, Andreas Cadhalpun wrote:
>> A slightly larger test case for mips is compiling ffmpeg...
> 
> It what I did to test if the failure is due to the above changes.
> ffmpeg builds fine with gcc version 5.2.1-17 and -march=mips2
> -mtune=mips32 (instead of the new default -march=mips32r2), and passes
> the testsuite. I'll see if I can isolate a smaller testcase so that we
> can understand the problem.

Attached is a testcase for mips, but it works fine for mipsel.

One more peculiarity I noticed is that adding 'c->A = 1;' to
an unused code path inverts the behavior: It works with
-fexpensive-optimizations, but fails with -fno-expensive-optimizations.

Best regards,
Andreas

#include 
#include 

typedef struct Context {
int64_t out;
int64_t A;
int64_t B;
int C;
} Context;

void init_tables(Context *c, int *table, int brightness, int contrast, int saturation);

int main()
{
Context c = { 0 };
int table[3] = {104597, 132201, 25675};
init_tables(, table, 0, 65536, 65536);

fprintf(stderr, "TEST: 0x%"PRIX64"\n", c.out);
if (c.out == 0x12a15) {
printf("working\n");
return 0;
}
printf("broken\n");
return 1;
}
CFLAGS += -fPIC -O2
LDFLAGS += -shared

all: working broken
LD_LIBRARY_PATH=. ./working || true
LD_LIBRARY_PATH=. ./broken || true

working.o:
$(CC) $(CFLAGS) -fno-expensive-optimizations -c -o working.o test.c

broken.o:
$(CC) $(CFLAGS) -c -o broken.o test.c

libworking.so: working.o
$(CC) $(LDFLAGS) -o libworking.so working.o

libbroken.so: broken.o
$(CC) $(LDFLAGS) -o libbroken.so broken.o

working: libworking.so
$(CC) -o working main.c -L. -lworking

broken: libbroken.so
$(CC) -o broken main.c -L. -lbroken

clean:
rm -f working.o libworking.so working broken.o libbroken.so broken
#include 

typedef struct Context {
int64_t out;
int64_t A;
int64_t B;
int C;
} Context;

static uint8_t clip_uint8_c(int a)
{
if (a&(~0xFF)) return (-a)>>31;
else return a;
}
static void fill_table(uint8_t* table[256 + 2*256], const int elemsize,
   const int64_t inc, void *y_tab)
{
int i;
uint8_t *y_table = y_tab;
y_table -= elemsize * (inc >> 9);
for (i = 0; i < 256 + 2*256; i++) {
int64_t cb = clip_uint8_c(i-256)*inc;
table[i] = y_table + elemsize * (cb >> 16);
}
}
static void fill_gv_table(int table[256 + 2*256], const int elemsize, const int64_t inc)
{
int i;
int off = -(inc >> 9);
for (i = 0; i < 256 + 2*256; i++) {
int64_t cb = clip_uint8_c(i-256)*inc;
table[i] = elemsize * (off + (cb >> 16));
}
}
static uint16_t roundToInt16(int64_t f)
{
int r = (f + (1 << 15)) >> 16;
if (r < -0x7FFF)
return 0x8000;
else if (r > 0x7FFF)
return 0x7FFF;
else
return r;
}

uint8_t yuvTable[1024];
int table_gV[256 + 2*256];
uint8_t *table_rV[256 + 2*256];
uint8_t *table_gU[256 + 2*256];
uint8_t *table_bU[256 + 2*256];
int64_t loc1;
int64_t loc2;
int64_t loc3;
int loc4;

__attribute__((cold)) void init_tables(Context *c, int *table, int brightness, int contrast, int saturation)
{
int i;
const int bpp = c->C;
const int yoffs = brightness ? 384 : 326;
int64_t crv = table[0];
int64_t cbu = table[1];
int64_t cgu = -table[0];
int64_t cgv = -table[2];
int64_t cy = 1 << 16;
int64_t TEST = 1 << 16;
int64_t oy = 0;
int64_t yb = 0;
if (!brightness) {
cy = (cy * 255) / 219;
TEST = (TEST * 255) / 219;
oy = 16 << 16;
} else {
crv = (crv * 224) / 255;
cbu = (cbu * 224) / 255;
cgu = (cgu * 224) / 255;
cgv = (cgv * 224) / 255;
}
cy = (cy * contrast) >> 16;
//c->out = TEST;
TEST = (TEST * contrast) >> 16;
c->out = TEST;

crv = (crv * contrast * saturation) >> 32;
cbu = (cbu * contrast * saturation) >> 32;
cgu = (cgu * contrast * saturation) >> 32;
cgv = (cgv * contrast * saturation) >> 32;
oy -= 256 * brightness;
c->A = 1;
c->B = roundToInt16(cy * 8192) + roundToInt16(crv * 8192);
loc1 = roundToInt16(cgv * 8192);
loc2 = roundToInt16(cgu * 8192);
loc3 = roundToInt16(oy * 8);
loc4 = roundToInt16(cy << 13) + roundToInt16(oy) + roundToInt16(crv << 13) 
   + roundToInt16(cgv << 13) + roundToInt16(cgu << 13) + roundToInt16(cbu << 13);
crv = ((crv << 16) + 0x8000) / ((cy) > (1) ? (cy) : (1));
cbu = ((cbu << 16) + 0x8000) / ((cy) > (1) ? (cy) : (1));
cgu = ((cgu << 16) + 0x8000) / ((cy) > (1) ? (cy) : (1));
cgv = ((cgv << 16) + 0x8000) / ((cy) > (1) ? (cy) : (1));
switch (bpp) {
case 0:
yb = -(384 << 16) - oy;
for (i = 0; i < 1024; i++) {
yuvTable[i] = clip_uint8_c(yb >> 16);
yb += cy;
}
fill_table(table_rV, 1, crv, yuvTable);
fill_table(table_gU, 

Bug#796488: marked as done (pyzor: Missing binary pyzor in 0.5.0-3)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 15:43:57 +
with message-id 
and subject line Bug#796488: fixed in pyzor 1:0.5.0-4
has caused the Debian Bug report #796488,
regarding pyzor: Missing binary pyzor in 0.5.0-3
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.)


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

Dear Maintainer,

The 0.5.0-3 package of pyzor is apparently missing all the binaries, it only 
contains the documentation.
This makes the package unusable.

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

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

Versions of packages pyzor depends on:
ii  python-gdbm  2.7.9-1

pyzor recommends no packages.

pyzor suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pyzor
Source-Version: 1:0.5.0-4

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated pyzor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Sep 2015 17:21:04 +0200
Source: pyzor
Binary: pyzor
Architecture: source all
Version: 1:0.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Carl Chenet 
Changed-By: Piotr Ożarowski 
Description:
 pyzor  - spam-catcher using a collaborative filtering network
Closes: 796488
Changes:
 pyzor (1:0.5.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix last upload, now installs all binaries (closes: #796488)
Checksums-Sha1:
 393ddc321decf714f816b02da42018ee9752a352 1946 pyzor_0.5.0-4.dsc
 d19232dc98d52987b9225a7a59ab63ce0b5c137a 4644 pyzor_0.5.0-4.debian.tar.xz
 a20f679d5f25c051bbeb889e36cb0ddb89aca15e 29560 pyzor_0.5.0-4_all.deb
Checksums-Sha256:
 5329ab1aa672369a10daac8928751888ace306d6c0b64bbd8026b5c7d1835ce4 1946 
pyzor_0.5.0-4.dsc
 b04d0af3db54380a7e21bca497c720e72f2f7651fb5c8cdbc49eabfa1ce05b3b 4644 
pyzor_0.5.0-4.debian.tar.xz
 73e9247cd15bc10bb274fe539f714041cfd4ebda05d828d80a801bb25c15094e 29560 
pyzor_0.5.0-4_all.deb
Files:
 63ac1f85bc2b573a8a30527d13536bcb 1946 mail optional pyzor_0.5.0-4.dsc
 88f14fb10fb13a2286c9ce5e336a13ec 4644 mail optional pyzor_0.5.0-4.debian.tar.xz
 0d44e7d62a67499d79cad71cda609663 29560 mail optional pyzor_0.5.0-4_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWCVtlAAoJEK728aKnRXZFkxQP/ixTIdDjbs+/r2UmGLqTFU+9
dwxcCdlLMrEuFxOVQ1poMfi3DD++FR7hOGaKIuEnrbALwldH6V+dYJ+pwCDD9Q1C
bsIJ60vfHand8z9IarV2X0nbKmaveSkkidvweH23Ldk1JDbVa+wDqYbm/YSpdlvj
22r4c1g5eWf3eNluyuhb0x7wPG9kHzghpIfiL8/62JkAck454x2tqEiWk3XMColv
TUSuR+Bl5Q0oczoIcGCS63MYU5ARvby6LkSJQkZdQS4V/qFvSDlFO6E9D8Ygzp+b
8B5QebhLa51rhsUwaDGjhHdzi0pZiMlenbxcBU5bTJQlpMbTFadGLTqE/Fe3hVyL
43ExncxG8+8ciljnjbTlEYNQ+NYhN5b77ClE05Oy3LrLo1829o1SSpzkLARlBazg
0OVD0UF5LSkU61MQ7esAuaSeK7vtT89CqNNLL6oIWYHkHwaSK4allBEeIi9cbcLc
oyhFeu6HlZSBBMPAFOOnBJN2CyREw9mYeNJRxboqEgGyP6VjHWW5kQg9pFCAeEvz
K3QksMR6HgWt28GnzL88lMb/ISF928SaaXEPWzJPmfrm4RDVM2U51jQ2D1jAHpDy
dzEhG6IW4tN4ryN1/zbsRB4vvrhr/Fi4TAISMYi1jW81MyEPYlPDFsRbq8I8ej/F
74XaOP4wHifp8XhZEvlz
=EHBl
-END PGP SIGNATURE End Message ---

Bug#799653: marked as done (vxl: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 16:00:39 +
with message-id 
and subject line Bug#799653: fixed in vxl 1.17.0.dfsg2-2
has caused the Debian Bug report #799653,
regarding vxl: ABI transition needed for libstdc++ v5
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.)


-- 
799653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vxl
Version: 1.17.0.dfsg2-1
Severity: serious
Justification: ABI break since stable when rebuilt
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

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

In the case of vxl, there's some std::string use in headers that
are installed (for example vgui_window::set_title), so a transition
does appear to be needed. The transition normally consists of renaming
the affected library packages, adding a v5 suffix (libvxl1.17v5). The
upstream-provided SONAME should not be changed.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. However, the libstdc++ transition has been going on for nearly
2 months already, and anything that makes it take longer is bad for Debian,
so introducing new upstream code is not recommended at this stage.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of vxl:

* coin, dcmtk have already had their renames
* Qt did not need a rename
* the rest appear to be C ABIs

so I think vxl is ready to go.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: vxl
Source-Version: 1.17.0.dfsg2-2

We believe that the bug you reported is fixed in the latest version of
vxl, 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.
Andreas Tille  (supplier of updated vxl 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, 21 Sep 2015 15:34:14 +0200
Source: vxl
Binary: libvxl1.17v5 libvxl1-dev
Architecture: source amd64
Version: 1.17.0.dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libvxl1-dev - C++ Libraries for Computer Vision Research (development files)
 libvxl1.17v5 - C++ Libraries for Computer Vision Research
Closes: 799653
Changes:
 vxl (1.17.0.dfsg2-2) unstable; urgency=medium
 .
   * Rename library packages for g++5 ABI transition
 Closes: #799653
Checksums-Sha1:
 dd389d9b481ab06884bb5f05beeaa5390847afbd 2444 vxl_1.17.0.dfsg2-2.dsc
 6bcd654b66c829316a6d880682a4f645557273ad 35488 vxl_1.17.0.dfsg2-2.debian.tar.xz
 64da335765580d2c85aa9f67b56fb84604ce018c 1782170 

Bug#799039: dcmqrscp : index.dat data corruption

[Andreas Tille]

Hi Mathieu,

On Tue, Sep 15, 2015 at 09:32:14AM +0200, Mathieu Malaterre wrote:
> Package: dcmtk
> Version: 3.6.1~20150629-1
> Severity: grave
> Justification: causes non-serious data loss
> 
> As describe in the previous bug report:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715011#50
> 
> One cannot simply upgrade dcmtk package without grave data loss
> (index.dat binary format is not compatible), which should result as
> -best case- index.dat corruption, or dcmqrscp to segfault and not
> start.
> 
> This correspond to the following upstream commit:
> c8423ab1fcf0273061462697b8eca56f894984c7

I can n ot find this commit under

   git clone https://github.com/commontk/DCMTK.git

Would you be able to provide a patch incorporating this commit to
fix the issue?

Do you think it is better to switch back to the former version of dcmtk?

> This should be clearly indicated during package upgrades. Marking as
> grave as I believe the DICOM file themselves are still kept as-is, so
> this is IMHO not a critical `causes serious data loss`. Upstream may
> have a finer understanding of the loss.

You perfectly know that I have no contact to upstream and I'm quite busy
with a lot of stuff.  If you are interested to help it would be great to
discuss the issue with upstream how to fix this issue in Debian in the
best possible way.  My motivation was simply to avoid the need for a
migration of two dcmtk versions - one in unstable and one in
experimental.  I do not feel able to maintain two versions.  May be
also the later snapshot 3.6.1_20150924 would fix the issue?  Any hint
would be welcome.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#800357: marked as done (pango1.0: FTBFS on buildds: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 16:09:16 +0200
with message-id <20150928140916.ga2...@fatal.se>
and subject line "fixed" in 1.38.0-1
has caused the Debian Bug report #800357,
regarding pango1.0: FTBFS on buildds: test failures
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.)


-- 
800357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pango1.0
Version: 1.38.0-1
Severity: serious
Justification: ftbfs

Hi,

Your package FTBFS on all buildds, with test failures. Example on i386:
| /usr/bin/make  testboundaries testboundaries_ucd testcolor testscript 
markup-parse test-layout test-font testattributes testiter 
test-pangocairo-threads test-ot-tags cxx-test
| make[3]: Entering directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| make[3]: 'testboundaries' is up to date.
| make[3]: 'testboundaries_ucd' is up to date.
| make[3]: 'testcolor' is up to date.
| make[3]: 'testscript' is up to date.
| make[3]: 'markup-parse' is up to date.
| make[3]: 'test-layout' is up to date.
| make[3]: 'test-font' is up to date.
| make[3]: 'testattributes' is up to date.
| make[3]: 'testiter' is up to date.
| make[3]: 'test-pangocairo-threads' is up to date.
| make[3]: 'test-ot-tags' is up to date.
| make[3]: 'cxx-test' is up to date.
| make[3]: Leaving directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| /usr/bin/make  check-TESTS
| make[3]: Entering directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| make[4]: Entering directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| PASS: testscript
| PASS: testboundaries
| PASS: testcolor
| PASS: testboundaries_ucd
| PASS: testattributes
| PASS: test-font
| /«PKGBUILDDIR»/./test-driver: line 107: 10692 Aborted "$@" > 
$log_file 2>&1
| FAIL: test-layout
| PASS: markup-parse
| PASS: cxx-test
| PASS: testiter
| PASS: test-ot-tags
| PASS: test-pangocairo-threads
| 
|pango 1.38.0: tests/test-suite.log
| 
| 
| # TOTAL: 12
| # PASS:  11
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
| 
| .. contents:: :depth: 2
| 
| FAIL: test-layout
| =
| 
| /layout/valid-2.markup: OK
| /layout/valid-1.markup: Contents don't match expected contents:
| --- /«PKGBUILDDIR»/./tests/layouts/valid-1.expected   2014-09-29 
19:07:11.0 +
| +++ /tmp/.G4VB5X  2015-09-28 03:44:14.577140541 +
| @@ -24,10 +24,10 @@
|  ---
|  
|  i=1, index=0, chars=22, level=0, gravity=south, flags=0, font=OMITTED, 
script=latin, language=c, 'This is a test of the '
| -i=2, index=22, chars=11, level=0, gravity=south, flags=0, font=OMITTED, 
script=latin, language=c, 'automatic e'
| +i=2, index=22, chars=10, level=0, gravity=south, flags=0, font=OMITTED, 
script=latin, language=c, 'automatic '
|[22 41] foreground #
|[22 41] underline 1
| -i=3, index=33, chars=15, level=0, gravity=south, flags=2, font=OMITTED, 
script=common, language=c, 'mergency brake!'
| +i=3, index=32, chars=16, level=0, gravity=south, flags=2, font=OMITTED, 
script=common, language=c, 'emergency brake!'
|[0 2147483647] fallback 0
|[22 41] foreground #
|[22 41] underline 1
| FAIL
| FAIL test-layout (exit status: 134)
| 
| 
| Testsuite summary for pango 1.38.0
| 
| # TOTAL: 12
| # PASS:  11
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=pango1.0=i386=1.38.0-1=1443411858

And overview for all archs:
  https://buildd.debian.org/status/package.php?p=pango1.0=sid

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Version: 1.38.0-2

Hello.

This should be resolved as of the above just uploaded version.
(Unfortunately Bug#800356 was not, so another upload will hopefully
follow soon.)

Regards,
Andreas Henriksson--- End Message ---

Bug#800368: pbuilder: keep in unstable for a while

[Gianfranco Costamagna]

Package: pbuilder
Version: 0.217
Severity: serious

Since this new release brings a *lot* of bugfixes (more than 27 bugs fixed) and
many of them might cause breakages in non-standard system configurations with 
custom hook
scripts [1], together with Mattia, the new pbuilder maintainer, we think this 
release
should wait a little bit more to migrate in Stretch.

[1] https://sources.debian.net/src/pbuilder/0.216/debian/NEWS/


cheers,

Gianfranco, sponsor of the 0.216 and 0.217 packages

Bug#799641: marked as done (ppl: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 16:00:35 +
with message-id 
and subject line Bug#799641: fixed in ppl 1:1.1-7
has caused the Debian Bug report #799641,
regarding ppl: ABI transition needed for libstdc++ v5
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.)


-- 
799641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ppl
Version: 1:1.1-6
Severity: serious
Justification: ABI break since stable
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

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

In the case of ppl, at least float_mpq_to_string() appears to change
its ABI in this way, so a transition does appear to be needed.
The transition normally consists of renaming the affected library
packages, adding a v5 suffix (libppl13v5). The SONAME should not be
changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. However, the libstdc++ transition has been going on for a
month already, and anything that makes it take longer is bad for Debian,
so introducing new upstream code is not desired at this stage.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of ppl, there doesn't seem to be any
C++, so this transition seems to be ready to go.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: ppl
Source-Version: 1:1.1-7

We believe that the bug you reported is fixed in the latest version of
ppl, 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.
Michael Tautschnig  (supplier of updated ppl 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, 21 Sep 2015 12:27:25 +0100
Source: ppl
Binary: libppl13v5 libppl-dev ppl-dev libppl-c4 libppl-doc libppl-swi
Architecture: source i386 all
Version: 1:1.1-7
Distribution: unstable
Urgency: medium
Maintainer: Michael Tautschnig 
Changed-By: Michael Tautschnig 
Description:
 libppl-c4  - Parma Polyhedra Library (C interface)
 libppl-dev - Parma Polyhedra Library (development)
 libppl-doc - Parma Polyhedra Library: Documentation
 libppl-swi - Parma Polyhedra Library (SWI Prolog interface)
 libppl13v5 - Parma Polyhedra Library (runtime library)
 ppl-dev- Parma Polyhedra Library (development binaries)
Closes: 799641
Changes:
 ppl (1:1.1-7) unstable; urgency=medium
 .
   * Rename C++ library package for the libstdc++ v5 transition. Thanks Simon
 McVittie for providing the necessary patch and chasing all this up.
 Closes: #799641.
   * Run gzip with -n to enable reproducible builds
Checksums-Sha1:
 

Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash

[Pascal Obry]

Just one precison, I'm using GDM (not sddm) and have the same issue.

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#796310: libgraphicsmagick3: --with-quantum-depth=16 breaks ABI

[GCS]

Hi Niels, Bob, others,

On Fri, Sep 25, 2015 at 8:34 AM, Niels Thykier  wrote:
> Thanks for getting it uploaded to NEW.
>
> I have prodded the FTP masters about fast tracking and will try to
> finish the resulting transition as fast as possible. :)
 Now it's accepted, built fine on almost all architectures and the
tracker seems to be correct.
It fails on mipsel[1] with:
-- cut --
Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"...
/«PKGBUILDDIR»/scripts/tap-functions.shi: line 58:  2290 Aborted
  ( "$@" )
EXEC: ./rwfile -stdio -filespec out_truecolor_stdio_%d
/«PKGBUILDDIR»/tests/input_truecolor.miff PCDS
not ok 244 - PCDS truecolor (stdio)
FAIL: tests/rwfile.tap 244 - PCDS truecolor (stdio)
-- cut --

It was failed previously a few times as well, but a rescheduled build
solved it. To be honest the reasons were: signal 01 (SIGBUS) "Bus
Error"
But I suspect the cause may be the same, please reschedule the build
of graphicsmagick on mipsel.

The build is strange on mips just for the record. Sometimes (just like
in the past) it builds in a hour. Nowadays it's over twelve hours
sometimes, but it seems to be at lease six hours[2].
Bob, how may I help you to find the root cause of the slow building on
mips at least?

Thanks,
Laszlo/GCS
[1] 
https://buildd.debian.org/status/fetch.php?pkg=graphicsmagick=mipsel=1.3.21-4=1443407301
[2] https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=mips

Bug#799948: glx-diversions: gdm also crashes

[Ara Keary]

 Guy Roussin  wrote:

> Hi,
>
> adduser sddm video
> adduser Debian-gdm video
>

Hi,

this also fixes the problem with  gdm 3.14.2-2  and  glx-diversions  0.6.0 .

One should thus open a bug for a package which forgets to implement this
user addition (upon an upgrade?).
Any idea of which?

Best,

Ara

Bug#796310: libgraphicsmagick3: --with-quantum-depth=16 breaks ABI

[Aurelien Jarno]

On 2015-09-28 08:46, László Böszörményi (GCS) wrote:
> Hi Niels, Bob, others,

Hi,

> On Fri, Sep 25, 2015 at 8:34 AM, Niels Thykier  wrote:
> > Thanks for getting it uploaded to NEW.
> >
> > I have prodded the FTP masters about fast tracking and will try to
> > finish the resulting transition as fast as possible. :)
>  Now it's accepted, built fine on almost all architectures and the
> tracker seems to be correct.
> It fails on mipsel[1] with:
> -- cut --
> Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"...
> /«PKGBUILDDIR»/scripts/tap-functions.shi: line 58:  2290 Aborted
>   ( "$@" )
> EXEC: ./rwfile -stdio -filespec out_truecolor_stdio_%d
> /«PKGBUILDDIR»/tests/input_truecolor.miff PCDS
> not ok 244 - PCDS truecolor (stdio)
> FAIL: tests/rwfile.tap 244 - PCDS truecolor (stdio)
> -- cut --
> 
> It was failed previously a few times as well, but a rescheduled build
> solved it. To be honest the reasons were: signal 01 (SIGBUS) "Bus
> Error"
> But I suspect the cause may be the same, please reschedule the build
> of graphicsmagick on mipsel.

The failure is strange, but indeed the new build was successful. Looks
like something to be investigated.

> The build is strange on mips just for the record. Sometimes (just like
> in the past) it builds in a hour. Nowadays it's over twelve hours
> sometimes, but it seems to be at lease six hours[2].
> Bob, how may I help you to find the root cause of the slow building on
> mips at least?

graphicsmagick uses FP instructions, and it happens that the machines we
currently use for the mips port do not have an FPU. The instructions are
emulated, that's why it takes longer to build (or actually to run the
testsuite). We have recently changed the ISA to mips32r2, which improves
things a bit (up to 40% on some packages), but the gain for
graphicsmagick seems to be around 10% only. The real solution is to get
new machines with an FPU, we are currently working on that.

Aurelien

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

Processed: Re: X32 enabled kernel and "Build of vmhgfs.ko failed for: 4.2.0-1-amd64 (x86_64)"

[Debian Bug Tracking System]

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

> reassign 800322 open-vm-tools-dkms
Bug #800322 [open-vm-tools] X32 enabled kernel and "Build of vmhgfs.ko failed 
for: 4.2.0-1-amd64 (x86_64)"
Bug reassigned from package 'open-vm-tools' to 'open-vm-tools-dkms'.
No longer marked as found in versions open-vm-tools/2:9.4.6-1770165-8.
Ignoring request to alter fixed versions of bug #800322 to the same values 
previously set
> severity 800322 grave
Bug #800322 [open-vm-tools-dkms] X32 enabled kernel and "Build of vmhgfs.ko 
failed for: 4.2.0-1-amd64 (x86_64)"
Severity set to 'grave' from 'normal'
> stop
Stopping processing here.

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

Bug#792920: marked as done (uqm: FTBFS due to missing -lm)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 11:34:54 +
with message-id 
and subject line Bug#792920: fixed in uqm 0.6.2.dfsg-9.1
has caused the Debian Bug report #792920,
regarding uqm: FTBFS due to missing -lm
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.)


-- 
792920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uqm
Version: 0.6.2.dfsg-9
Severity: serious
Tags: jessie sid stretch
Justification: fails to build from source (but built successfully in the past)

Hi,

starting with jessie, uqm FTBFS due to missing -lm:


  CC   obj/release/src/sc2code/netplay/proto/ready.c.o
  CC   obj/release/src/sc2code/netplay/proto/reset.c.o
  CC   obj/release/src/getopt/getopt.c.o
  CC   obj/release/src/getopt/getopt1.c.o
  LINK uqm
/usr/bin/ld: obj/release/src/sc2code/planets/plangen.c.o: undefined reference 
to symbol 'exp@@GLIBC_2.2.5'
//lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from 
command line
collect2: error: ld returned 1 exit status
Makefile.build:84: recipe for target 'uqm' failed
make[1]: *** [uqm] Error 1
make[1]: Leaving directory '/tmp/buildd/uqm-0.6.2.dfsg/sc2'
debian/rules:13: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Please enable verbose build, too. I.e. the individual command lines need
to be shown s.t. it is easier to analyze such bugs from the buildlog and
run automated checks like blhc.


Andreas
--- End Message ---
--- Begin Message ---
Source: uqm
Source-Version: 0.6.2.dfsg-9.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated uqm 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, 18 Sep 2015 12:37:50 +0200
Source: uqm
Binary: uqm
Architecture: source
Version: 0.6.2.dfsg-9.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry E. Oboukhov 
Changed-By: Andreas Beckmann 
Description:
 uqm- The Ur-Quan Masters - An inter-galatic adventure game
Closes: 792920
Changes:
 uqm (0.6.2.dfsg-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix missing -lm, thanks to Peter Piwowarski.  (Closes: #792920)
Checksums-Sha1:
 aeda7a31706945cfa40c4d72f4c96f675f4ade6d 1886 uqm_0.6.2.dfsg-9.1.dsc
 b1779d3a78b7461bb2b0b0d226d66519092dce5c 9171 uqm_0.6.2.dfsg-9.1.diff.gz
Checksums-Sha256:
 2c25617ee9d4db10bafd7d400e9e3d90773c84aa265cbd5a8118dc0dd7a934e8 1886 
uqm_0.6.2.dfsg-9.1.dsc
 db32410195ce2c7c62c5123be02cf2606bbff2dfc17c1839f8a50d44d5fdabd5 9171 
uqm_0.6.2.dfsg-9.1.diff.gz
Files:
 a345c7c50cbc8ed67422005c68c94381 1886 contrib/games optional 
uqm_0.6.2.dfsg-9.1.dsc
 c2af60a4828e9591bb26fb28224e480c 9171 contrib/games optional 
uqm_0.6.2.dfsg-9.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV++xrAAoJEF+zP5NZ6e0IVAIQAIov2gJy1qB9hm/LWcAoejao
mq8NQZ+6paVRGKbr5SeVVB4zDdUjmAbuvduXyqwnaUpaRJ6ss0hmTzxAnU3RRQ0t
miOkp7TUtlmnx1lQ6dwtZrcxjpAgcsod48+gHqL6iNa/crwXAVvrZv99POsb+r1Y
ndb0RfhniD4CFEteYTGTv7by5jmlQNc1PJL8MZYQ+6zQlYuCYAeuKbeCrLS+HCkD
roAItXF3C0V3CbBAA1CpjolHYLttVUV0JiV6CDPd2Zdo8HXa0Q+RVAKN8h0z0p3m
u3QP+21hYx6MlQad211S98OL9lt0N5HVhITgV3B5k01mUI/jLN9jjd3XZlXpncEO
GUv0VXoo0Ga9htutVWDiytTOsXTzjmBuC5WBuccIDW4AmnfECptlufwbmR/7stJk
d1Dkc4jZPpIFRtbpdTFn8v2Tr+8jQQmVaZFXgv3+73WmKPFrPEMf+BCUhtA4j5J5
eZAcD2bgUm51yUAx+RsYWWqardxkfmXRe+PlHpV/CreeHJ0CFseJo23X+o9qjXt2
oUy8MoxuOVfCTXJTarZJ1FmAyCtl5F+thgkN+Ls4nB+cCTuV6JYQcvSqYdRyCjqA
KlbEDYI/8K8WprD2suxBYDvztudeDh6MxM6fLZkMH+zvP2nZi96YOd2v3jD3+rX+
UpOgJfDTRoSNuuHlX5/j
=HX16
-END PGP SIGNATURE End Message ---

Bug#800357: pango1.0: FTBFS on buildds: test failures

[Cyril Brulebois]

Source: pango1.0
Version: 1.38.0-1
Severity: serious
Justification: ftbfs

Hi,

Your package FTBFS on all buildds, with test failures. Example on i386:
| /usr/bin/make  testboundaries testboundaries_ucd testcolor testscript 
markup-parse test-layout test-font testattributes testiter 
test-pangocairo-threads test-ot-tags cxx-test
| make[3]: Entering directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| make[3]: 'testboundaries' is up to date.
| make[3]: 'testboundaries_ucd' is up to date.
| make[3]: 'testcolor' is up to date.
| make[3]: 'testscript' is up to date.
| make[3]: 'markup-parse' is up to date.
| make[3]: 'test-layout' is up to date.
| make[3]: 'test-font' is up to date.
| make[3]: 'testattributes' is up to date.
| make[3]: 'testiter' is up to date.
| make[3]: 'test-pangocairo-threads' is up to date.
| make[3]: 'test-ot-tags' is up to date.
| make[3]: 'cxx-test' is up to date.
| make[3]: Leaving directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| /usr/bin/make  check-TESTS
| make[3]: Entering directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| make[4]: Entering directory '/«PKGBUILDDIR»/debian/build/shared/tests'
| PASS: testscript
| PASS: testboundaries
| PASS: testcolor
| PASS: testboundaries_ucd
| PASS: testattributes
| PASS: test-font
| /«PKGBUILDDIR»/./test-driver: line 107: 10692 Aborted "$@" > 
$log_file 2>&1
| FAIL: test-layout
| PASS: markup-parse
| PASS: cxx-test
| PASS: testiter
| PASS: test-ot-tags
| PASS: test-pangocairo-threads
| 
|pango 1.38.0: tests/test-suite.log
| 
| 
| # TOTAL: 12
| # PASS:  11
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
| 
| .. contents:: :depth: 2
| 
| FAIL: test-layout
| =
| 
| /layout/valid-2.markup: OK
| /layout/valid-1.markup: Contents don't match expected contents:
| --- /«PKGBUILDDIR»/./tests/layouts/valid-1.expected   2014-09-29 
19:07:11.0 +
| +++ /tmp/.G4VB5X  2015-09-28 03:44:14.577140541 +
| @@ -24,10 +24,10 @@
|  ---
|  
|  i=1, index=0, chars=22, level=0, gravity=south, flags=0, font=OMITTED, 
script=latin, language=c, 'This is a test of the '
| -i=2, index=22, chars=11, level=0, gravity=south, flags=0, font=OMITTED, 
script=latin, language=c, 'automatic e'
| +i=2, index=22, chars=10, level=0, gravity=south, flags=0, font=OMITTED, 
script=latin, language=c, 'automatic '
|[22 41] foreground #
|[22 41] underline 1
| -i=3, index=33, chars=15, level=0, gravity=south, flags=2, font=OMITTED, 
script=common, language=c, 'mergency brake!'
| +i=3, index=32, chars=16, level=0, gravity=south, flags=2, font=OMITTED, 
script=common, language=c, 'emergency brake!'
|[0 2147483647] fallback 0
|[22 41] foreground #
|[22 41] underline 1
| FAIL
| FAIL test-layout (exit status: 134)
| 
| 
| Testsuite summary for pango 1.38.0
| 
| # TOTAL: 12
| # PASS:  11
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=pango1.0=i386=1.38.0-1=1443411858

And overview for all archs:
  https://buildd.debian.org/status/package.php?p=pango1.0=sid

Mraw,
KiBi.

Bug#800356: libpango1.0-udeb: not installable: depends on libthai0

[Cyril Brulebois]

Package: libpango1.0-udeb
Version: 1.38.0-1
Severity: grave
Justification: renders package unusable

[ Please keep debian-b...@lists.debian.org in copy. ]

Hi,

Your package is no longer installable since it gained a dependency on a
library package which has no udeb variant: libthai0.

This makes all these packages uninstallable:
  cdebconf-gtk-entropy
  cdebconf-gtk-terminal
  cdebconf-gtk-udeb
  gtk2-engines-udeb
  libgtk2.0-0-udeb
  libpango1.0-udeb
  libvte9-udeb
  matchbox-keyboard-udeb

Mraw,
KiBi.

Processed: tagging 788062

[Debian Bug Tracking System]

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

> tags 788062 + pending
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#799948: glx-diversions: gdm also crashes

[Gernot Hassenpflug]

All the xgreeters?
I had this bug on the 24th or 25th, and fixed it with Guy's comment
straight away.
Using lightdrm, so:

adduser lightdm video

Made a post in the Debian user forums:
http://forums.debian.net/viewtopic.php?f=6=124950=83476f324bbbe81da6526c1eea2f916d

Regards,
Gernot Hassenpflug

Bug#752615: marked as done (moodle is licensed under the PHP license and is not PHP)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 09:24:08 +
with message-id 
and subject line Bug#752615: fixed in moodle 2.7.10+dfsg-1
has caused the Debian Bug report #752615,
regarding moodle is licensed under the PHP license and is not PHP
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.)


-- 
752615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-gearman
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

From the REJECT faq:

/
| You have a PHP add-on package (any php script/"app"/thing, not PHP
| itself) and it's licensed only under the standard PHP license. That
| license, up to the 3.x which is actually out, is not really usable for
| anything else than PHP itself. I've mailed our -legal list about that
| and got only one response, which basically supported my view on this.
| Basically this license talks only about PHP, the PHP Group, and includes
| Zend Engine, so its not applicable to anything else. And even worse,
| older versions include the nice ad-clause.
| 
| One good solution here is to suggest a license change to your upstream,
| as they clearly wanted a free one. LGPL or BSD seems to be what they
| want.
\

Sorry this made it through NEW,


Hope you're well, and thanks for your work,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: moodle
Source-Version: 2.7.10+dfsg-1

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

Debian distribution maintenance software
pp.
Joost van Baal-Ilić  (supplier of updated moodle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 21 Sep 2015 09:52:15 +0200
Source: moodle
Binary: moodle
Architecture: source all
Version: 2.7.10+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Moodle Packaging Team 

Changed-By: Joost van Baal-Ilić 
Description:
 moodle - course management system for online learning
Closes: 746594 749609 752615 775842 778422 785591 792242 799634
Changes:
 moodle (2.7.10+dfsg-1) unstable; urgency=high
 .
   * New upstream security release, released Sept 21, 2015. Note that the
 upstream 2.7 branch is now supported for security fixes only until May 2017
 (LTS).  Security issues fixed:
 - MSA-15-0030: Students can re-attempt answering questions in the lesson,
   Reported by Eric Eakin, MDL-50516, CVE-2015-5264
 - MSA-15-0031: Teacher in forum can still post to "all participants" and
   groups they are not members of, Reported by David Scotson, MDL-50576,
   CVE-2015-5272
 - MSA-15-0032: Users can delete files uploaded by other users in wiki,
   Reported by John Provasnik, MDL-48371, CVE-2015-5265
 - MSA-15-0033: Meta course synchronisation enrols suspended students as
   managers for a short period of time, Reported by Brian Winstead,
   MDL-50744, CVE-2015-5266
 - MSA-15-0034: Vulnerability in password recovery mechanism, Reported by
   Vincent Herbulot (@us3r777), MDL-50860, CVE-2015-5267
 - MSA-15-0035: Rating component does not check separate groups, Reported by
   Juan Leyva, MDL-50173, CVE-2015-5268
 - MSA-15-0036: XSS in grouping description, Reported by Marina Glancy,
   MDL-50709, CVE-2015-5269
 See the 21 Sep 2015 post from Marina Glancy at
 http://www.openwall.com/lists/oss-security/2015/09/21/1 for more details on
 these fixed security issues.  Some other fixes and improvements: MDL-51050
 - Forms such as "Create new group" are no longer populated with passwords
 and usernames by the browsers; MDL-42670 - Recent activity block no longer
 shows student 

Bug#799634: marked as done (moodle: CVE-2015-5264 CVE-2015-5265 CVE-2015-5266 CVE-2015-5267 CVE-2015-5268 CVE-2015-5269 CVE-2015-5272)

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 09:24:08 +
with message-id 
and subject line Bug#799634: fixed in moodle 2.7.10+dfsg-1
has caused the Debian Bug report #799634,
regarding moodle: CVE-2015-5264 CVE-2015-5265 CVE-2015-5266 CVE-2015-5267 
CVE-2015-5268 CVE-2015-5269 CVE-2015-5272
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.)


-- 
799634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moodle
Version: 2.7.9+dfsg-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerabilities were published for moodle.

CVE-2015-5264[0]:
MSA-15-0030: Students can re-attempt answering questions in the lesson

CVE-2015-5265[1]:
MSA-15-0032: Users can delete files uploaded by other users in wiki

CVE-2015-5266[2]:
MSA-15-0033: Meta course synchronisation enrols suspended students as
managers for a short period of time

CVE-2015-5267[3]:
MSA-15-0034: Vulnerability in password recovery mechanism

CVE-2015-5268[4]:
MSA-15-0035: Rating component does not check separate groups

CVE-2015-5269[5]:
MSA-15-0036: XSS in grouping description

CVE-2015-5272[6]:
MSA-15-0031: Teacher in forum can still post to "all participants" and
groups they are not members of

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-2015-5264
[1] https://security-tracker.debian.org/tracker/CVE-2015-5265
[2] https://security-tracker.debian.org/tracker/CVE-2015-5266
[3] https://security-tracker.debian.org/tracker/CVE-2015-5267
[4] https://security-tracker.debian.org/tracker/CVE-2015-5268
[5] https://security-tracker.debian.org/tracker/CVE-2015-5269
[6] https://security-tracker.debian.org/tracker/CVE-2015-5272
[7] http://www.openwall.com/lists/oss-security/2015/09/21/1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: moodle
Source-Version: 2.7.10+dfsg-1

We believe that the bug you reported is fixed in the latest version of
moodle, 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.
Joost van Baal-Ilić  (supplier of updated moodle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 21 Sep 2015 09:52:15 +0200
Source: moodle
Binary: moodle
Architecture: source all
Version: 2.7.10+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Moodle Packaging Team 

Changed-By: Joost van Baal-Ilić 
Description:
 moodle - course management system for online learning
Closes: 746594 749609 752615 775842 778422 785591 792242 799634
Changes:
 moodle (2.7.10+dfsg-1) unstable; urgency=high
 .
   * New upstream security release, released Sept 21, 2015. Note that the
 upstream 2.7 branch is now supported for security fixes only until May 2017
 (LTS).  Security issues fixed:
 - MSA-15-0030: Students can re-attempt answering questions in the lesson,
   Reported by Eric Eakin, MDL-50516, CVE-2015-5264
 - MSA-15-0031: Teacher in forum can still post to "all participants" and
   groups they are not members of, Reported by David Scotson, MDL-50576,
   CVE-2015-5272
 - MSA-15-0032: Users can delete files uploaded by other users in wiki,
   Reported by John Provasnik, MDL-48371, CVE-2015-5265
 - MSA-15-0033: Meta course synchronisation enrols suspended students as
   managers for a short period of time, Reported by Brian Winstead,
   MDL-50744, CVE-2015-5266
 - MSA-15-0034: Vulnerability in password recovery mechanism, Reported by
   Vincent Herbulot (@us3r777), MDL-50860, CVE-2015-5267
 - MSA-15-0035: Rating component does not check separate groups, Reported by
   Juan Leyva, MDL-50173, CVE-2015-5268
 - MSA-15-0036: XSS in grouping description, Reported by Marina Glancy,
   MDL-50709, CVE-2015-5269
 See the 21 Sep 2015 post from Marina Glancy 

Bug#746594: marked as done (Embedded OLE is not DFSG-compliant (PHP-2.02))

[Debian Bug Tracking System]

Your message dated Mon, 28 Sep 2015 09:24:08 +
with message-id 
and subject line Bug#746594: fixed in moodle 2.7.10+dfsg-1
has caused the Debian Bug report #746594,
regarding Embedded OLE is not DFSG-compliant (PHP-2.02)
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.)


-- 
746594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moodle
Version: 2.6.2-1
Severity: serious
Tags: upstream
X-Debbugs-CC: ftpmas...@debian.org, dolib...@packages.debian.org
Control: clone -1 -2
Control: reassign -2 dolibarr 3.3.4-3

Hi,

The embedded PHPExcel copy (#718585) embeds OLE (#487558) which is not
DFSG compliant (PHP-2.02)[1,2].

1: http://ftp-master.debian.org/REJECT-FAQ.html
2: https://bugs.debian.org/487558#48

Regards

David


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: moodle
Source-Version: 2.7.10+dfsg-1

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

Debian distribution maintenance software
pp.
Joost van Baal-Ilić  (supplier of updated moodle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 21 Sep 2015 09:52:15 +0200
Source: moodle
Binary: moodle
Architecture: source all
Version: 2.7.10+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Moodle Packaging Team 

Changed-By: Joost van Baal-Ilić 
Description:
 moodle - course management system for online learning
Closes: 746594 749609 752615 775842 778422 785591 792242 799634
Changes:
 moodle (2.7.10+dfsg-1) unstable; urgency=high
 .
   * New upstream security release, released Sept 21, 2015. Note that the
 upstream 2.7 branch is now supported for security fixes only until May 2017
 (LTS).  Security issues fixed:
 - MSA-15-0030: Students can re-attempt answering questions in the lesson,
   Reported by Eric Eakin, MDL-50516, CVE-2015-5264
 - MSA-15-0031: Teacher in forum can still post to "all participants" and
   groups they are not members of, Reported by David Scotson, MDL-50576,
   CVE-2015-5272
 - MSA-15-0032: Users can delete files uploaded by other users in wiki,
   Reported by John Provasnik, MDL-48371, CVE-2015-5265
 - MSA-15-0033: Meta course synchronisation enrols suspended students as
   managers for a short period of time, Reported by Brian Winstead,
   MDL-50744, CVE-2015-5266
 - MSA-15-0034: Vulnerability in password recovery mechanism, Reported by
   Vincent Herbulot (@us3r777), MDL-50860, CVE-2015-5267
 - MSA-15-0035: Rating component does not check separate groups, Reported by
   Juan Leyva, MDL-50173, CVE-2015-5268
 - MSA-15-0036: XSS in grouping description, Reported by Marina Glancy,
   MDL-50709, CVE-2015-5269
 See the 21 Sep 2015 post from Marina Glancy at
 http://www.openwall.com/lists/oss-security/2015/09/21/1 for more details on
 these fixed security issues.  Some other fixes and improvements: MDL-51050
 - Forms such as "Create new group" are no longer populated with passwords
 and usernames by the browsers; MDL-42670 - Recent activity block no longer
 shows student name when assignment blind marking is on. See
 https://docs.moodle.org/dev/Moodle_2.7.10_release_notes for more details.
 Thanks Salvatore Bonaccorso and Thijs Kinkhorst for forwarding the news.
 Closes: #799634
   * debian/source/lintian-overrides: add comment/comment.js, some
 lib/yuilib/3.15.0/**/*-debug.js and
 lib/yuilib/2in3/2.9.0/build/yui2-*/*-debug.js files to list of false
 positives "source-is-missing". Bug #799861 reported against lintian.
   * debian/copyright: clarify license situation of
 lib/pear/HTML/QuickForm/DHTMLRulesTableless.php and
 lib/pear/HTML/QuickForm/Renderer/Tableless.php. Thanks
 Ondřej Surý and Paul Tagliamonte. Closes: #752615
   * debian/control: no longer 

Bug#774149: systemd

[Mathieu Malaterre]

Just FYI:

[How to automount optical media on Debian Linux for Kodi]

https://ddumont.wordpress.com/2015/09/27/how-to-automount-optical-media-on-debian-linux-for-kodi/

Processed: Re: Bug#796310: Info received (libgraphicsmagick3: --with-quantum-depth=16 breaks ABI)

[Debian Bug Tracking System]

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

> fixed 796310 1.3.21-4
Bug #796310 {Done: Laszlo Boszormenyi (GCS) } 
[src:graphicsmagick] libgraphicsmagick3: --with-quantum-depth=16 breaks ABI
Marked as fixed in versions graphicsmagick/1.3.21-4.
> thanks
Stopping processing here.

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

Bug#800409: Synaptic not starting, false positive

[Carlos Kosloff]

Package: synaptic
Version: 0.81.4+b2
Severity: grave

Dear maintainer,

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

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

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

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

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

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

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

-- no debconf information

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

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

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

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

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

The failed processes are synaptic-pkexec and pkexec.

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

Please help.

*Carlos Kosloff*

Processed (with 1 error): libgraphicsmagick3: --with-quantum-depth=16 breaks ABI

[Debian Bug Tracking System]

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

> reassign 796310 src:graphicsmagick 1.3.20-4
Bug #796310 {Done: Laszlo Boszormenyi (GCS) } 
[libgraphicsmagick3] libgraphicsmagick3: --with-quantum-depth=16 breaks ABI
Bug reassigned from package 'libgraphicsmagick3' to 'src:graphicsmagick'.
No longer marked as found in versions graphicsmagick/1.3.20-4.
No longer marked as fixed in versions graphicsmagick/1.3.21-4.
Bug #796310 {Done: Laszlo Boszormenyi (GCS) } 
[src:graphicsmagick] libgraphicsmagick3: --with-quantum-depth=16 breaks ABI
Marked as found in versions graphicsmagick/1.3.20-4.
> fixed 796310 src:graphicsmagick 1.3.21-4
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#796310: libgraphicsmagick3: --with-quantum-depth=16 breaks ABI

[Emilio Pozuelo Monfort]

reassign 796310 src:graphicsmagick 1.3.20-4
fixed 796310 src:graphicsmagick 1.3.21-4
thanks

Hi,

Since libgraphicsmagick3 no longer exists, the BTS gets confused and thinks this
bug isn't fixed, and so britney won't attempt to migrate graphicsmagick:

Updating libgraphicsmagick3 introduces new bugs: #796310

Let's see if this fixes that.

Emilio

Bug#800371: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config

[Aurelien Jarno]

clone 800371 -1
reassign -1 libsigc++-2.0
retitle -1 libsigc++-2.0: C++11 features in headers but no -std=c++11 in 
pkg-config
thanks

On 2015-09-28 16:59, Aurelien Jarno wrote:
> Source: glibmm2.4
> Version: 2.46.1-1
> Severity: serious
> 
> glibmm2.4 version 2.46.1-1 started to use C++11 features in the headers
> it exports, but pkg-config --cflags doesn't return -std=c++11. Given the
> default is still -std=gnu++98 in GCC 5, it causes packages which use
> these headers to fails to build.
> 
> A build log showing the issue can be found here:
> 
> https://buildd.debian.org/status/fetch.php?pkg=inkscape=mips64el=0.91-5%2Bb1=1443446208

Looking at the build log more in details, it appears that libsigc++-2.0
is affected by the exact same bug. I am therefore cloning it to this
package.

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

Bug#799550: libuhd003v5 lost its v5 suffix...

[A. Maitland Bottoms]

Raphaël Hertzog writes:
 > Package: libuhd003
 > Version: 3.9.0-1
 > Severity: serious
 > User: de...@kali.org
 > Usertags: origin-kali
 > 
 > I just noticed that with uhd 3.9.0 libuhd003 lost the v5 suffix that had
 > been introduced with 3.8.5-2.1.
 > 
 > And the changelog has no explanation for this. So to avoid problems
 > when upgrading from jessie to stretch, this should be fixed again...
 > 
 > Thank you!

I've got uhd-3.9.1-1 conflicting with gnuradio << 3.7.8-3
and I am considering adding a versioned depends for gnuradio 3.7.8-4
and libgnuradio-osmosdr0.1.4 0.1.4-3 that requires libuhd003 >= 3.9.
Will that be enough to avoid problems when upgrading from jessie to stretch?

Upstream has been breaking ABI routinely. Another approach would be
to patch the soname and soversion for the Debian packaging resulting
in a new libuhd3.9 library package. At the moment I am preferring
this approach to the v5 suffix approach.

But if taking the v5 suffix approach is the recommended way forward,
I can certainly do that. But I would like your advice now that you
know upstream UHD often breaks ABI without soname/soversion bumps.

I think UHD upstream is interested in best practices for library
release management, but, like me, needs a bit of education and a
plan to move from the current state of release management to
something better.

Thanks,
-Maitland

also:
peter green writes regarding bug #794878:
 > It appears the library rename introduced in uhd 3.8.5-2.1 was reverted
 > in uhd 3.9.0-1. There was no mention of this revert in the changelog.
 >
 > Was the revert intentional and if so what was the reasoning behind it?

Yes it was intentional.
The reasoning is that uhd routinely changes ABI and API between versions.
I have been using versioned package dependencies to manage library ABI
changes. Since 3.9.0 was another ABI bump from 3.8.5, I went ahead and
reverted the library rename.

Not mentioning this in the changelog is my mistake and I do feel silly
for not doing it.

I used dh-acc to check that uhd 3.9.1 was compatible with uhd 3.9.0.
Also, upstream has told me that they were beginning to use the
abi-compliance-checker tool as well. So with luck better library
soname and soversion settings will make it easier to follow normal
library package name conventions in the future.

Thank you for your interest and attention. Library ABI/API release
management and soname/soversion practices are weaknesses of mine, so
I am eager to learn. Let me know any comments or advice you have,
and I'll pass it along to my upstreams too.

When faced with upstream libraries not bumping sonames, how many
Debian packages patch to do their own library release management
versus simply following upstream's conventions?

Thanks,
-Maitland

Processed: reassign 789955 to iceweasel, forcibly merging 798988 789955

[Debian Bug Tracking System]

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

> reassign 789955 iceweasel
Bug #789955 [devscripts] devscripts: [bts] "bts show" command displays error: 
(process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Bug reassigned from package 'devscripts' to 'iceweasel'.
No longer marked as found in versions devscripts/2.15.3.
Ignoring request to alter fixed versions of bug #789955 to the same values 
previously set
> forcemerge 798988 789955
Bug #798988 [iceweasel] g_slice_set_config: assertion 'sys_page_size == 0' 
failed
Bug #789955 [iceweasel] devscripts: [bts] "bts show" command displays error: 
(process:29614): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Severity set to 'grave' from 'minor'
Marked as found in versions iceweasel/38.2.1esr-1~deb8u1.
Merged 789955 798988
> thanks
Stopping processing here.

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

Bug#800318: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations

[Aurelien Jarno]

On 2015-09-27 23:43, Andreas Cadhalpun wrote:
> Hi Aurelien,
> 
> On 27.09.2015 23:10, Aurelien Jarno wrote:
> > On 2015-09-27 20:37, Andreas Cadhalpun wrote:
> > Thanks for the detailed testcase. I have been able to reproduce the
> > issue on mipsel, but not on mips.
> 
> Indeed, this test case only works on mipsel.
> However, the same tests of ffmpeg's testsuite fail on mips, just with 
> different
> checksums. So it likely has the same cause.
> 
> >> This works correctly with gcc-5 5.2.1-16, so it is a regression in 
> >> 5.2.1-17.
> >> The changelog reveals:
> >>   [ Aurelien Jarno ]
> >>   * Use --with-mips-plt on mips*.
> >>   * Build for R2 ISA on mips, mips64 and mips64el.
> >>   * Optimize for R2 ISA on mipsel.
> >>   * Only apply mips-fix-loongson2f-nop on mipsel.
> >>
> >> I assume one of these changes is responsible for this regression.
> > 
> > Indeed. At least on mipsel the issue is due to the use of
> > -mtune=mips32r2 by default. I guess the best is to change it back to
> > -mtune=mips32 until we better understand the issue.
> 
> OK.
> 
> > Does someone have time to look at the issue more in details? The
> > generated code is quite different between -mtune=mips32 and
> > -mtune=mips32r2 (not in terms of instructions, but in terms of
> > sequencing).
> > 
> > As for mips, given I am not able to reproduce the issue, my guess is
> > that it's due to the switch to -march=mips32r2, but I currently have
> > no way to make sure.
> 
> A slightly larger test case for mips is compiling ffmpeg...

It what I did to test if the failure is due to the above changes.
ffmpeg builds fine with gcc version 5.2.1-17 and -march=mips2
-mtune=mips32 (instead of the new default -march=mips32r2), and passes
the testsuite. I'll see if I can isolate a smaller testcase so that we
can understand the problem.

Aurelien

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

Processed: Re: Bug#797132: gobject-introspection: missing -fPIC option when compiling

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #797132 [gobject-introspection] gobject-introspection: missing -fPIC option 
when compiling
Severity set to 'important' from 'serious'

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

Bug#797132: gobject-introspection: missing -fPIC option when compiling

[Samuel Thibault]

Control: severity -1 important

Samuel Thibault, le Fri 28 Aug 2015 03:26:01 +0200, a écrit :
> linking of temporary binary failed: Command '['/bin/bash', '../libtool', 
> '--mode=link', '--tag=CC', 'cc', '-o', 
> '/tmp/buildd/at-spi2-core-2.16.0/atspi/tmp-introspect9yGBBn/Atspi-2.0', 
> '-export-dynamic', '-D_FORTIFY_SOURCE=2', '-Wall', '-g', 
> '-Werror-implicit-function-declaration', '-fPIE', '-pie', '-Wl,-z,relro', 
> '-Wl,-z,now', 
> '/tmp/buildd/at-spi2-core-2.16.0/atspi/tmp-introspect9yGBBn/Atspi-2.0.o', 
> '-L.', 'libatspi.la', '../dbind/libdbind.la', '-lgio-2.0', '-lgobject-2.0', 
> '-Wl,--export-dynamic', '-lgmodule-2.0', '-pthread', '-lglib-2.0', 
> '-ldbus-1']' returned non-zero exit status 1
> /usr/share/gobject-introspection-1.0/Makefile.introspection:153: recipe for 
> target 'Atspi-2.0.gir' failed
> 
> Atspi-2.0.o was indeed not built with -fPIC.  I don't know how all this
> is supposed to use -fPIC/-fPIE.

I've dug a bit more.  By disabling pie hardening, the build succeeds,
thus lowering the severity.  But we'll probably want to keep pie
hardening.

Samuel

Bug#778106: HELP needed for uploading a new version 6.6 of the Rheolef package (english translation)

[Sébastien Villemot]

Dear Pierre,

Le vendredi 25 septembre 2015 à 13:24 +0200, Pierre Saramito a écrit :

> I just commit in svn a new version the debianization of rheolef :
> it fixes the problem related to g++ 5 in sid and testing (bug #778106 ).

I had a quick look at your work and it looks like the debian/copyright
file is outdated. In particular, it does not mention the files under
utils/qd/, which seem to be under a modified BSD license. There may be
other problems (including outdated copyright years), but I did not check
for them. Could you please fix this?

There is also the hand-crafted shlibs file created in debian/rules, as
mentionned by kibi. This looks very ugly. Is this hack really necessary?

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594