Bug#807653: nedit and numeric keypad

[Orvoine Bertrand]

Package: nedit
Version: 1:5.6~cvs20081118-9
Severity: normal

Dear Maintainer,

When using NEdit, I am unable to use the numeric keypad to enter numbers no
matter whether the numlock is on or off ( with the exception of key "5")

wheezy nedit version is ok ( 1:5.6~cvs20081118-7 ) but not after (jessie,
testing)

If I recompil wheezy version on jessie, it's ok. Probably because
1:5.6~cvs20081118-7 depend's on lesstif2, and later depend on libxm4 ...

sincerely



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages nedit depends on:
ii  libc6 2.19-18+deb8u1
ii  libx11-6  2:1.6.2-3
ii  libxm42.3.4-6+deb8u1
ii  libxt61:1.1.4-1+b1

nedit recommends no packages.

Versions of packages nedit suggests:
pn  csh  

-- no debconf information

Bug#807651: udev: unowned files after purge (policy 6.8, 10.8): /etc/init/udev.override

[Michael Biebl]

Control: severity -1 minor

Am 11.12.2015 um 11:21 schrieb Andreas Beckmann:

> during a test with piuparts I noticed your package left unowned files on
> the system after purge, which is a violation of policy 6.8 (or 10.8):
> 
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
> 
> Filing this as important as having a piuparts clean archive is a release
> goal since lenny.
> 
>>From the attached log (scroll to the bottom...):
> 
> 0m44.8s ERROR: FAIL: Package purging left files on system:
>   /etc/init/udev.override  not owned
> 


That means someone called "update-rc.d udev disable".

The udev package itself doesn't do that afaics. Can you find out who?

I'm not convinced that the package itself should clean that up.


-- 
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#799546: digikam: Digikam not installable

[Hans-J. Ullrich]

Dear maintainers,

I can confirm this on my systems, too. IMHO, as digikam is not usable at the 
moment for ALL debian/testing users, I suggest, to set the status to "grave".

The problem with the dependencies is a really bad situation. Hope it will be 
fixed soon, as digikam is a really fine application.

Thanks for all your efforts!

Best 

Hans

Bug#807655: tripwire: segfaults during installation in i386 (chroot on amd64 host)

[Andreas Beckmann]

Package: tripwire
Version: 2.4.2.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

This bug was observed during i386 tests in i386 testing and unstable
chroots on an amd64 host.
This seems to have started after the binNMU against glibc 2.21.

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

  Selecting previously unselected package tripwire.
  (Reading database ... 
(Reading database ... 8843 files and directories currently installed.)
  Preparing to unpack .../tripwire_2.4.2.2-5+b1_i386.deb ...
  Unpacking tripwire (2.4.2.2-5+b1) ...
  Setting up tripwire (2.4.2.2-5+b1) ...
  Segmentation fault
  Segmentation fault
  Generating site key (this may take several minutes)...
  Segmentation fault
  dpkg: error processing package tripwire (--configure):
   subprocess installed post-installation script returned error exit status 139
  Errors were encountered while processing:
   tripwire


cheers,

Andreas


tripwire_2.4.2.2-5+b1.log.gz
Description: application/gzip

Bug#807651: udev: unowned files after purge (policy 6.8, 10.8): /etc/init/udev.override

[Andreas Beckmann]

Package: udev
Version: 228-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m44.8s ERROR: FAIL: Package purging left files on system:
  /etc/init/udev.overridenot owned


cheers,

Andreas


udev_228-2.log.gz
Description: application/gzip

Bug#807652: php7.0-cli: unowned symlinks after purge (policy 6.8, 10.8): /etc/php/7.0/cli/conf.d/20-{json, opcache}.ini

[Andreas Beckmann]

Package: php7.0-cli
Version: 7.0.0-4
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m50.8s ERROR: FAIL: Package purging left files on system:
  /etc/php/7.0/cli/  owned by: php7.0-cli
  /etc/php/7.0/cli/conf.d/   owned by: php7.0-cli
  /etc/php/7.0/cli/conf.d/20-json.ini -> /etc/php/mods-available/json.ini   
 not owned
  /etc/php/7.0/cli/conf.d/20-opcache.ini -> /etc/php/mods-available/opcache.ini 
 not owned


cheers,

Andreas


php7.0-cli_7.0.0-4.log.gz
Description: application/gzip

Bug#807658: python-enum: This package will be removed

[Federico Ceratto]

Package: python-enum
Version: 0.4.4-3
Severity: normal

python-enum conflicts with python-enum34 and it's not maintained upstream.
It's used only by flashbake and python-laditools.

The package will be removed before the next freeze.

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

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

Versions of packages python-enum depends on:
ii  python 2.7.9-1
ii  python2.7  2.7.11-1

python-enum recommends no packages.

python-enum suggests no packages.

-- no debconf information

Bug#807657: dvdauthor: FTBFS: compat.h:141:8: error: expected identifier or '(' before '__extension__'

[Chris Lamb]

Source: dvdauthor
Version: 0.7.0-1.3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

dvdauthor fails to build from source in unstable/amd64:

  [..]

  dvdcompile.c: In function 'negateif':
  dvdcompile.c:1157:17: warning: suggest parentheses around arithmetic in 
operand of '|' [-Wparentheses]
   ifs & 0x8ff /* remove comparison op */
   ^
  dvdcompile.c: In function 'vm_optimize':
  dvdcompile.c:1417:21: warning: suggest parentheses around '&&' within '||' 
[-Wparentheses]
   &&
   ^
  dvdcompile.c:1455:21: warning: suggest parentheses around '&&' within '||' 
[-Wparentheses]
   &&
   ^
  mv -f .deps/dvdcompile.Tpo .deps/dvdcompile.Po
  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I.  -DSYSCONFDIR="\"/etc\"" 
-I/usr/include/libxml2  -I/usr/include/freetype2 -I/usr/include/fribidi 
-I/usr/include/freetype2  -Wall -g -O2 -MT dvdvml.o -MD -MP -MF 
.deps/dvdvml.Tpo -c -o dvdvml.o dvdvml.c
  In file included from /usr/include/string.h:634:0,
   from dvdvml.c:40:
  compat.h:141:8: error: expected identifier or '(' before '__extension__'
   char * strndup
  ^
  Makefile:552: recipe for target 'dvdvml.o' failed
  make[3]: *** [dvdvml.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151211131336.Db8T0bq8an/dvdauthor-0.7.0/src'
  Makefile:376: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151211131336.Db8T0bq8an/dvdauthor-0.7.0/src'
  Makefile:382: recipe for target 'all-recursive' failed
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211131336.Db8T0bq8an/dvdauthor-0.7.0'
  debian/rules:35: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

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


dvdauthor.0.7.0-1.3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807542: fixed in virtualbox 5.0.10-dfsg-6

[Laurent Bigonville]

reopen 807542
thanks

On Thu, 10 Dec 2015 17:26:38 + Gianfranco Costamagna 
 wrote:


> Closes: 807542
> Changes:
> virtualbox (5.0.10-dfsg-6) unstable; urgency=medium
> .
> * Do not enable vboxweb.service by default
> (Closes: #807542)

I don't think this is the proper fix, the call to dh_systemd_enable 
shouldn't be removed, but you should pass the --no-enable flag to it


Cheers,

Laurent Bigonville

Bug#807660: jenkins-winstone: FTBFS: jenkins-winstone-2.8/target/test-classes does not exist

[Chris Lamb]

Source: jenkins-winstone
Version: 2.8-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

jenkins-winstone fails to build from source in unstable/amd64:

  [..]

  main:
   [copy] Copying 3 files to 
/home/lamby/temp/cdt.20151211131603.5ByL2e24N7/jenkins-winstone-2.8/target
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 2.550 s
  [INFO] Finished at: 2015-12-11T13:18:59+02:00
  [INFO] Final Memory: 19M/298M
  [INFO] 

  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (prepare-testwebapp) on 
project winstone: An Ant BuildException has occured: 
/home/lamby/temp/cdt.20151211131603.5ByL2e24N7/jenkins-winstone-2.8/target/test-classes
 does not exist.
  [ERROR] around Ant part .. @ 7:136 in 
/home/lamby/temp/cdt.20151211131603.5ByL2e24N7/jenkins-winstone-2.8/target/antrun/build-main.xml
  [ERROR] -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


jenkins-winstone.2.8-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#791463: closing RFS: udfclient/0.8-1 [ITP] -- userland implementation of the UDF filesystem

[Pali Rohár]

On Wednesday 09 December 2015 18:05:29 Gianfranco Costamagna wrote:
> On Wed, 09 Dec 2015 16:40:21 + Bart Martens
>  wrote:
> > Package udfclient has been removed from mentors.
> > 
> > 
> Hi Pali, did you forget to update the package?
> 
> cheers,
> 
> G.
> 

Hi Gianfranco, I did not updated package because I did not know that
some step is needed to do. My last uploaded version worked and I thought
that it was OK.

-- 
Pali Rohár
pali.ro...@gmail.com

Bug#807509: nmu: clementine_1.2.3+git1354-gdaddbde+dfsg-1

[Emilio Pozuelo Monfort]

On 09/12/15 21:44, Stefan Ahlers wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Severity: normal
> 
> Hello,
> 
> Due to a update of libechonest2.1 to libechonest2.3, the package clementine 
> is broken and has to be rebuild against libechonest2.3
> because the name of the shared librarie "libechonest.so.2.1" changed to 
> "libechonest.so.2.3"
> 
> Please rebuild clementine against libechonest2.3 2.3.1-0.1 to bump its 
> dependency on libechonest2.3. nmu clementine_1.2.3+git1354-gdaddbde+dfsg-1 . 
> ANY . -m 'Rebuild against libechonest2.3 to correct dependency'

It'd be good to get libechonest fixed:

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

Emilio

Bug#807662: mrpt-common: fails to upgrade from 'jessie' - trying to overwrite /usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini

[Andreas Beckmann]

Package: mrpt-common
Version: 1:1.3.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + mrpt-apps

Hi,

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

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

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

  Selecting previously unselected package mrpt-common.
  (Reading database ... 
(Reading database ... 9945 files and directories currently installed.)
  Preparing to unpack .../mrpt-common_1%3a1.3.2-1_all.deb ...
  Unpacking mrpt-common (1:1.3.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/mrpt-common_1%3a1.3.2-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini', which 
is also in package mrpt-apps 1:1.2.2-1.1


cheers,

Andreas

Bug#807661: linux: With 4.4 kernel sources, libcrc32c is needed by raid so udeb build fails

[Wookey]

Source: linux
Version: 4.3-1~exp2
Severity: normal

I had to make the debian packaging work with a 4.4 tree and it needed this 
minor fix.

Here is a patch as you'll no doubt be doing the same thing shortly

Without this the build fails with:
debian/md-modules-4.4.0-trunk-arm64-di 
lib/modules/4.4.0-trunk-arm64/kernel/lib/libcrc32c.ko
debian/crc-modules-4.4.0-trunk-arm64-di 
lib/modules/4.4.0-trunk-arm64/kernel/lib/libcrc32c.ko
some modules are in more than one package

It seems that raid6 has added a dependency on libcrc32c
Only tested on arm64, but I presume this is a generic change. I could be 
wrong...

Author: Wookey 
Date:   Thu Dec 10 17:44:12 2015 +

Fix for 4.4 kernels udebs

diff --git a/debian/installer/package-list b/debian/installer/package-list
index e79890b..adaee53 100644
--- a/debian/installer/package-list
+++ b/debian/installer/package-list
@@ -180,7 +180,7 @@ Description: NFS filesystem support
  This package contains the NFS filesystem module for the kernel.
 
 Package: md-modules
-Depends: kernel-image
+Depends: kernel-image, crc-modules
 Priority: extra
 Description: RAID and LVM support
  This package contains RAID and LVM modules for the kernel.



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

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
commit b6e5b7ebed9f043b05e629bbdbab1cf1f007f581
Author: Wookey 
Date:   Thu Dec 10 17:44:12 2015 +

Fix for 4.4 kernels udebs

diff --git a/debian/installer/package-list b/debian/installer/package-list
index e79890b..adaee53 100644
--- a/debian/installer/package-list
+++ b/debian/installer/package-list
@@ -180,7 +180,7 @@ Description: NFS filesystem support
  This package contains the NFS filesystem module for the kernel.
 
 Package: md-modules
-Depends: kernel-image
+Depends: kernel-image, crc-modules
 Priority: extra
 Description: RAID and LVM support
  This package contains RAID and LVM modules for the kernel.

Bug#791463: closing RFS: udfclient/0.8-1 [ITP] -- userland implementation of the UDF filesystem

[Gianfranco Costamagna]

Hi Pali, can you please reupload?

Andrew are you still interested in looking at it?

cheers,

G.


>Hi Gianfranco, I did not updated package because I did not know that

>some step is needed to do. My last uploaded version worked and I thought
>that it was OK.

Bug#807617: FTBFS due to test-suite failures

[Guus Sliepen]

On Thu, Dec 10, 2015 at 11:41:06PM +0100, Michael Biebl wrote:

> Since version 0.8, the test-suite basically fails on all architectures
> as can be seen at
> https://buildd.debian.org/status/package.php?p=ifupdown=unstable
> 
> I can reproduce the problem on amd64 with a pbuilder build.
> >From a cursory glance it looks like the test suite needs files from the
> installed package (i.e. it looks for /lib/ifupdown/settle-dad.sh).
> 
> Shouldn't it use ./settle-dad.sh instead when running the test-suite?

It actually doesn't call settle-dad.sh at all. The problem is that the
testsuite is running ifup with the --no-act option, and compares the
output of it to the expected output as written in
debian/testbuild-linux. Ifup only calls /lib/ifupdown/settle-dad.sh if
it exists and is executable, but that of course depends on the build
environment. The expected output was written with the assumption that
/lib/ifupdown/settle-dad.sh is already there. So I'll have to fix that.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#807648: zyne: Fails to start (missing dep for wx?)

[Harri Haataja]

Package: zyne
Version: 0.1.2-2
Severity: normal

Dear Maintainer,

Trying to start zyne:
$ zyne 
Traceback (most recent call last):
  File "/usr/bin/zyne", line 3, in 
  import wxversion
  ImportError: No module named wxversion

The executable tries to load several wx libs, but none of them are
mentioned in package dependencies.

Installing python-wxversion leads to
$ zyne
Traceback (most recent call last):
  File "/usr/bin/zyne", line 4, in 
wxversion.select("2.8")
  File "/usr/lib/python2.7/dist-packages/wxversion.py", line 152, in select
raise VersionError("Requested version of wxPython not found")
wxversion.VersionError: Requested version of wxPython not found

I'm not sure what would satisfy 2.8. Doesn't seem that installing
python-wxgtk3.0 will do. The plain lib package I have and I'm not really
familiar with the lib, let alone the Python bindings.

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

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

Versions of packages zyne depends on:
ii  python  2.7.9-1
ii  python-pyo  0.7.6+git20150902.a1d7123d76-1

zyne recommends no packages.

zyne suggests no packages.

-- no debconf information

Bug#807659: libgettext-commons-java: FTBFS: Error resolving version for plugin 'org.apache.maven.plugins:maven-eclipse-plugin'

[Chris Lamb]

Source: libgettext-commons-java
Version: 0.9.6-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building Gettext Commons 0.9.6
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.163 s
  [INFO] Finished at: 2015-12-11T13:18:58+02:00
  [INFO] Final Memory: 6M/236M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.maven.plugins:maven-eclipse-plugin' from the repositories [local 
(/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


libgettext-commons-java.0.9.6-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807099: RFS: corsix-th/0.50-1 ITP 610087 - A Theme Hospital engine reimplementation.

[Alexandre Detiste]

Le dimanche 6 décembre 2015, 20:34:42 Markus Koschany a écrit :
> Several Expat copyright holder are missing in
> CorsixTH/Lua/languages
> CorsixTH/Src/jit_opt.h
> SpriteEncoder/*
> LevelEdit/*
> 
> GPL-3+
> SpriteEncoder/parser.cpp
> SpriteEncoder/tokens.h

This license has this special exception; does this mean
it can be considered Expat-licensed as the whole game ?

   As a special exception, you may create a larger work that contains
   part or all of the Bison parser skeleton and distribute that work
   under terms of your choice

> 
> zlib:
> WindowsInstaller/ReplaceInFile.nsh


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

Bug#807625: Include output from /proc/device-tree/model in installation report

[Ian Campbell]

On Fri, 2015-12-11 at 11:43 +0100, Cyril Brulebois wrote:
> Martin Michlmayr  (2015-12-10):
> > * Cyril Brulebois  [2015-12-11 04:44]:
> > > A cursory look suggests this file is made available through:
> > > > drivers/of/base.c:  proc_symlink("device-tree", NULL,
> > > > "/sys/firmware/devicetree/base");
> > 
> > Yopu're right.  It's also available via
> > /sys/firmware/devicetree/base/model but I'm not sure if that's
> > preferred.
> 
> Sorry for being as unclear as usual. I meant: instead of special-casing
> /proc/device-tree/model in "addfile" (to make sure we have proper line
> endings), we could use readlink there and special-case based on whether the
> ultimate location is below /sys/firmware/devicetree. But docs suggest that
> might break in the future.

Could addfile somehow detect the lack of a \n at the end of any file and add it?

Someone recently taught me that instead of "cat file" you can use "grep ''
foo" which adds the \n if needed, not sure if installation-report runs in a
suitable context with a grep which does so?

Ian.

Bug#743638: RFP: shairport -- Play music streamed from iTunes/iPads/iPods

[Chris Boot]

Control: retitle -1 ITP: shairport-sync -- AirPlay audio player
Control: owner -1 !

Hi folks,

I think I'd like to package shairport-sync for Debian. I think it makes
sense to package shairport-sync rather than the now-defunct shairport,
not least because it's actively maintained but also because Mike Braidy
(its current upstream maintainer) appears to have put some thought into
licensing by e.g. permitting the use of PolarSSL.

I think the first task in all of this is to properly review the
licensing situation of the package due to its long and winding history.
The actual packaging looks to be fairly straightforward.

Any objections?

Cheers,
Chris

-- 
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D  C918 F5C8 3C05 D9CE 

Bug#804253: apt-listbugs: Please allow pinning broken version to -1

[Julian Andres Klode]

On Fri, Nov 06, 2015 at 07:46:19PM +0100, Francesco Poli wrote:
> Control: tags -1 moreinfo
> 
> 
> On Fri, 6 Nov 2015 16:36:01 +0100 Julian Andres Klode wrote:
> 
> > Package: apt-listbugs
> > Version: 0.1.17
> > Severity: wishlist
> 
> Hello Julian,
> thanks for your feature request!

Sorry it took so long to reply, but here we go:

> With your proposed new strategy, the package would be pinned so that one
> buggy version would be forbidden. Then, for *each* new version of the
> package that becomes available with the bug unfixed, apt-listbugs would
> prompt again the user and ask again whether the new buggy version
> should be forbidden. Until a fixed version becomes finally available.
> I have seen a good number of cases where a bug (even an RC bug) stays
> unfixed for several uploads, unfortunately.
> I think that prompting the user again and again for a previously
> examined bug would be annoying.

What happens currently for me is that some packages are not upgraded and
I wonder why - I then manually remove the apt-listbugs pin and run
apt (full-)upgrade again.

Another problem with a daily cron job is the following: If the bug
was fixed between two dak runs on the same day, I'll not get the new
upgrade, because the cron job has not run yet. That happens often
enough.


> It's true that I could implement a check inside apt-listbugs in order
> to avoid prompting again the user for already examined bugs:
> apt-listbugs should check whether the bug is already mentioned in one
> of the pins... It's probably feasible, but then I don't see any special
> advantage over the current implementation.

Optimally we would have hooks in APT that allow you to just block
a single upgrade and let the rest go on, but without that feature,
I think the best that can be done for my use case is the -1 pinning
thing.



> Another drawback is that a number of obsolete pins would be left in APT
> preferences, once the bug is actually fixed and the fixed version of
> the package finally lands on the user's system.
> Unless a daily cron job does the cleaning, of course. But then, again,
> I don't see any special advantage over the current implementation.

You can just clean up with the cron job. Or clean up with a post
install hook, that just checks if a newer version of the blocked
packages was installed.


-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.


signature.asc
Description: PGP signature

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[Stefan Ahlers]

Hi Adrian,

> If you like, you can send me a debdiff with your changes and I can
> quickly review it and test-build it on one of the buildds.

here is a new version of the debdiff. I have included the differences of
armhf and armel architechture into the libechonest2.3.symbol file.
I hope I have not make a mistake, again.

Cheers,
Stefan
diff -Nru libechonest-2.3.1/debian/changelog libechonest-2.3.1/debian/changelog
--- libechonest-2.3.1/debian/changelog  2015-12-10 12:43:21.0 +0100
+++ libechonest-2.3.1/debian/changelog  2015-12-11 10:20:47.0 +0100
@@ -1,9 +1,17 @@
+libechonest (2.3.1-0.3) unstable; urgency=low
+
+  * Non-maintainer upload, with maintainer permission.
+  * Fix symbols again.
+  * Drop bogus libechonest2.1 (Closes: #807507)
+
+ -- Stefan Ahlers   Fri, 11 Dec 2015 09:00:00 +0100
+
 libechonest (2.3.1-0.2) unstable; urgency=low
 
   * Non-maintainer upload, with maintainer permission.
   * Fix symbols.
 
- -- Stefan Ahlers   Thu, 26 Dec 2015 12:00:00 +0100
+ -- Stefan Ahlers   Thu, 10 Dec 2015 12:00:00 +0100
 
 libechonest (2.3.1-0.1) unstable; urgency=low
 
@@ -21,7 +29,7 @@
   * Set myself as the new maintainer with permission of Lisandro the original
 maintainer.
   * Update package repository location.
-
+ 
  -- Thomas Pierson   Sun, 11 Oct 2015 22:43:01 +0200
 
 libechonest (2.1.0-2) unstable; urgency=low
diff -Nru libechonest-2.3.1/debian/libechonest2.3.symbols 
libechonest-2.3.1/debian/libechonest2.3.symbols
--- libechonest-2.3.1/debian/libechonest2.3.symbols 2015-12-10 
11:40:27.0 +0100
+++ libechonest-2.3.1/debian/libechonest2.3.symbols 2015-12-11 
10:15:08.0 +0100
@@ -39,38 +39,57 @@
  _ZN8Echonest11CatalogSongD1Ev@Base 2.1.0
  _ZN8Echonest11CatalogSongD2Ev@Base 2.1.0
  _ZN8Echonest11CatalogSongaSERKS0_@Base 2.1.0
- _ZN8Echonest12AudioSummary10setValenceEd@Base 2.3.0
- _ZN8Echonest12AudioSummary11setDurationEd@Base 2.1.0
- _ZN8Echonest12AudioSummary11setLivenessEd@Base 2.3.0 
- _ZN8Echonest12AudioSummary11setLoudnessEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary10setValenceEd@Base 2.3.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary11setDurationEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary11setLivenessEd@Base 2.3.0 
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary11setLoudnessEd@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary10setValenceEf@Base 2.3.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary11setDurationEf@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary11setLivenessEf@Base 2.3.0 
+ (arch=armhf armel)_ZN8Echonest12AudioSummary11setLoudnessEf@Base 2.1.0
  _ZN8Echonest12AudioSummary11setSectionsERK7QVectorINS_10AudioChunkEE@Base 
2.1.0
  _ZN8Echonest12AudioSummary11setSegmentsERK7QVectorINS_7SegmentEE@Base 2.1.0
  _ZN8Echonest12AudioSummary12setSampleMD5ERK7QString@Base 2.1.0
- _ZN8Echonest12AudioSummary12setTimestampEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary12setTimestampEd@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary12setTimestampEf@Base 2.1.0
+ _ZN8Echonest12AudioSummary12setTimestampEf@Base 2.1.0
  _ZN8Echonest12AudioSummary13setNumSamplesEx@Base 2.1.0
- _ZN8Echonest12AudioSummary13setSampleRateEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary13setSampleRateEd@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary13setSampleRateEf@Base 2.1.0
  _ZN8Echonest12AudioSummary14setAnalysisUrlERK4QUrl@Base 2.1.0
- _ZN8Echonest12AudioSummary14setEndOfFadeInEd@Base 2.1.0
- _ZN8Echonest12AudioSummary14setSpeechinessEd@Base 2.3.0 
- _ZN8Echonest12AudioSummary15setAcousticnessEd@Base 2.3.0 
- _ZN8Echonest12AudioSummary15setAnalysisTimeEd@Base 2.1.0
- _ZN8Echonest12AudioSummary15setDanceabilityEd@Base 2.1.0
- _ZN8Echonest12AudioSummary16setKeyConfidenceEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary14setEndOfFadeInEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary14setSpeechinessEd@Base 2.3.0 
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary15setAcousticnessEd@Base 2.3.0 
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary15setAnalysisTimeEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary15setDanceabilityEd@Base 2.1.0
+ (arch=!armhf !armel)_ZN8Echonest12AudioSummary16setKeyConfidenceEd@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary14setEndOfFadeInEf@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary14setSpeechinessEf@Base 2.3.0 
+ (arch=armhf armel)_ZN8Echonest12AudioSummary15setAcousticnessEf@Base 2.3.0 
+ (arch=armhf armel)_ZN8Echonest12AudioSummary15setAnalysisTimeEf@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary15setDanceabilityEf@Base 2.1.0
+ (arch=armhf armel)_ZN8Echonest12AudioSummary16setKeyConfidenceEf@Base 2.1.0
  _ZN8Echonest12AudioSummary16setTimeSignatureEi@Base 2.1.0
  _ZN8Echonest12AudioSummary17parseFullAnalysisEP13QNetworkReply@Base 2.1.0
  

Bug#807645: ifupdown package fails to configure itself (by dpkg)

[Guus Sliepen]

On Fri, Dec 11, 2015 at 10:16:18AM +0100, Vincent Danjean wrote:

> Executing /lib/systemd/systemd-sysv-install enable networking
> done 0
> Failed to execute operation: File exists
> dpkg: error processing package ifupdown (--configure):
>  subprocess installed post-installation script returned error exit status 1

Hm, that's weird...

> Using "strace -f -o /tmp/strace.out2 systemctl enable networking.service" did
> not help me to find which file is already existing.

Try using -ff instead of -f. If it's not obvious what the problem is
from the strace logs, could you send them to me in any case?

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#807507: removal of libechonest2.1

[Stefan Ahlers]

Hello,

> which, besides a date from the future, lacks a vital line:
> * Drop bogus libechonest2.1 (Closes: #807507)
>
> Thus, I'm hereby closing this manually.
>
> 2.3.1-0.1 does break its users, but fortunately there's only one such
user,
> clementine. I've just requested a rebuild of it (#807639), so there's no
> need to do anything more to transition properly.

Sorry, I know that this package was not correct but I going to fix it
with the help of my sponsor and I also opened a request for a rebuild
(#807509) on Wednesday.

But thank you for your help!

Bug#807663: Split snippet fastcgi-php/conf, leaving leading fastcgi_split_path_info out

[Gerardo Esteban Malazdrewicz]

Package: nginx-common
Version: 1.9.6-2
Severity: wishlist

The need for a custom fastcgi_split_path_info renders snippet unusable.

Case in point:

location /cluebringer/ {
alias /usr/share/postfix-cluebringer-webui/webui/;
index index.php;

location ~ ".+\.php$" {
fastcgi_split_path_info ^/cluebringer(.+\.php)()$;
include snippets/fastcgi-php-no-split.conf;
...

fastcgi-php-no-split.conf is the old fastcgi-php.conf without the leading
fastcgi_split_path_info.

fastcgi-php.conf can be rewritten as:

# regex to split $uri to $fastcgi_script_name and $fastcgi_path
fastcgi_split_path_info ^(.+\.php)(/.+)$;

include snippets/fastcgi-php-no-split.conf;
EOF

Thanks,
   Gerardo



-- 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

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

Versions of packages nginx-common depends on:
ii  init-system-helpers  1.24
ii  lsb-base 9.20150917
ii  python   2.7.11-1

nginx-common recommends no packages.

Versions of packages nginx-common suggests:
ii  fcgiwrap   1.1.0-6
pn  nginx-doc  
ii  ssl-cert   1.0.37

-- no debconf information

Bug#222232: #222232 cruft: Should take 'localpurge' into account

[Alexandre Detiste]

control: tag -1 wontfix

"#619086 cruft: support dpkg path-exclude/path-include" has now been 
implemented.

As "#603587 localepurge: Please use dpkg --path-exclude / --path-include to 
implement the service"
has been implemented for a long time; please use this feature and then 
your localepurge-generated dpkg settings will be automatically picked-up by 
cruft-ng.

https://sources.debian.net/src/localepurge/0.7.3.4/debian/README.dpkg-path/

> Thus localepurge (since 0.7.0) now has the option to
> generate a dpkg configuration file to exclude locale specific
> documentation for various packages.

Greets,

Alexandre

Bug#807656: flashbake: Please package new upstream version 0.27.1 so that Debian can drop python-enum

[Axel Beckert]

Package: flashbake
Version: 0.26.2-5.1
Severity: normal

Hi,

Debian wants to get rid of the more or less obsolete python-enum
library. See e.g. https://github.com/commandline/flashbake/issues/22

Upstream has released a new version of flashbake which depends on the
prefered python-enum34 library instead. Debian's flashbake package no
more depend on python-enum is only one of two remaining packages which
are in the way of the python-enum removal. (See
https://bugs.debian.org/800805 for the issue in the other remaining
reverse dependency.)

This bug report may be raised in severity once we're getting closer to
the python-enum removal.

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

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

Versions of packages flashbake depends on:
ii  git [git-core] 1:2.6.3-1
ii  git-core   1:2.6.3-1
ii  python 2.7.11-1
ii  python-enum0.4.4-2
ii  python-feedparser  5.1.3-3
ii  python-setuptools  18.7-1
pn  python:any 

flashbake recommends no packages.

flashbake suggests no packages.

-- no debconf information

Bug#807509: nmu: clementine_1.2.3+git1354-gdaddbde+dfsg-1

[Stefan Ahlers]

Hi,
> It'd be good to get libechonest fixed:
>
yes, I'm working on it! Thank you for your help!

Stefan

Bug#807649: ITP: ruby-flowdock -- Ruby Gem for using Flowdock's API

[Pirate Praveen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

package: wnpp
severity: wishlist
owner: Pirate Praveen 

rubygems.org/gems/flowdock
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWaqHQAAoJEM4fnGdFEsIqanoP/2Xv55d7VoMMge9wtcHgE42L
iFGP9bXQapnDRuGI73PIU14yhLjq5wz95vHKR40ltv8R6EaMCSGwQybe3MpScvDI
6zcJ/Pwe6HRt5d5/d3fK1LuVIFbzodRXnbFErIZ1EeFozDmfPAX7dndcGNcDQf4V
OCHNrF8LorTc4nCidjwFSYFhZ6Me0YLlPjqJ17DLjXMjXVISce0bOYvEBHrKTnY2
ZW485JmyP1QPvE8SZiBQi3TMcXxzXZt3DnjXgljbFDLYPntkJiIPomlqpyuMRTaL
3P/7R6oV9ycsBmANtHvxUXvC1PprtPLk9SoFYJMcCysrLV6D+QX7IbOO8x+kxe/z
d/Luq4V5u0i3qPKSX5EjDA+jI0BlsEXeBhmrMYWZkpncDs5P55qp9PSOPJHw8OYh
a9ahy2mt1+FULBPoGgPZKfEFXFRIWGfEuLfaPYtZ6OdrP0fe7EViuu6WbjlHQtEF
74TnTLNz6okcbk1vz/yv8Ab4guZEFgQqJxta7vDEvYZvBSaM5t6cfKmOgCRGsxT3
/aA7erylzJxCrT9bp/X7Psw+KnHlL30Gn9L8xl9iYBvJgcJG1C3t9pDfLM0ZV6T6
kdlKiyXV67J/kqk4GyMK2Y1dNhODK4T9PbD28GKP++vuV5o0DIIcGvsJYuEHgIUk
EhmUq/YOZweIHy/2v9Yr
=LH29
-END PGP SIGNATURE-

Bug#807650: mercurial-crecord: incompatible with mercurial 3.6

[Andreas Beckmann]

Package: mercurial-crecord
Version: 0.20140626-1
Severity: serious
Tags: sid stretch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid because mercurial 3.6.1-1 added a Breaks against it:

mercurial (3.6.1-1) unstable; urgency=medium

  * New upstream release
  * mercurial 3.6 breaks mercurial-crecord 0.20150626-1



Cheers,

Andreas

Bug#807241: ITP: archlinux-xdg-menu -- Convert freedesktop files to a format used by various WMs

[Jonathan Dowland]

On Sun, Dec 06, 2015 at 04:20:28PM +, Nicholas Bamber wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Nicholas Bamber 
> 
> * Package name: archlinux-xdg-menu

^ don't put archlinux in the package name. It might warrant a mention in the
long description, however.

>   Description : Convert freedesktop files to a format used by various WMs
^^^
> xdg-menu generates menus for WMs using the Free Desktop menu standard.
   ^^^
probably worth expanding WMs to "window managers" to reduce ambiguity.

> You can install archlinux-xdg-menu from the official repositories.

^ I wouldn't include this sentence in the package description.

> The following WMs are supported:

^ I wouldn't enumerate a list of WMs one-per-line in the long description.
Instead do something like

  twm; ion3; WindowMaker; fvwm2; icewm; blackbox; fluxbox; openbox; awesome.

> KDE, Gnome, Xfce, Enlightenment are already XDG compatible.

What does this mean? Does it mean you do not need this package if you use
on of these environments?

Bug#807625: Include output from /proc/device-tree/model in installation report

[Cyril Brulebois]

Martin Michlmayr  (2015-12-10):
> * Cyril Brulebois  [2015-12-11 04:44]:
> > A cursory look suggests this file is made available through:
> > | drivers/of/base.c:proc_symlink("device-tree", NULL, 
> > "/sys/firmware/devicetree/base");
> 
> Yopu're right.  It's also available via
> /sys/firmware/devicetree/base/model but I'm not sure if that's
> preferred.

Sorry for being as unclear as usual. I meant: instead of special-casing
/proc/device-tree/model in "addfile" (to make sure we have proper line
endings), we could use readlink there and special-case based on whether the
ultimate location is below /sys/firmware/devicetree. But docs suggest that
might break in the future.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#807654: jessie-pu: package python-django/1.7.11-1

[Raphael Hertzog]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hello,

I would like to update python-django in jessie to the latest upstream bug
fix release in the 1.7.x branch, aka 1.7.11. It should also be the last
upstream release in that branch since it's now unsupported upstream.

I already argued for that during the freeze but it's still the same now:
Django is a sane upstream that does not add new features in branches
of released versions, they only fix bugs and security issues. They have
a large test suite and it's easier for us to maintain Django over the
next 4 years to be as close as possible to the last released version.

Here are some pointers about upstream's policies for stable releases:
https://docs.djangoproject.com/en/1.9/internals/release-process/
https://docs.djangoproject.com/en/1.9/misc/api-stability/

Much like you trust PostgreSQL upstream devs to be sane, I would like
you to trust the Django upstream devs.

I attach a filtered debdiff, I dropped all the changes to test code and
all the changes to the documentation. There are also some harmless changes
related to the switch of the python-modules team to git-dpm too.

Please let me know if I can upload the package.

(I want to do the same for wheezy with 1.4.22, but I'll wait the outcome
of this one before doing the work for wheezy, so it would be nice from you
to have a timely answer)

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

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

-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
diff -Nru python-django-1.7.7/debian/changelog 
python-django-1.7.11/debian/changelog
--- python-django-1.7.7/debian/changelog2015-11-22 20:36:09.0 
+0100
+++ python-django-1.7.11/debian/changelog   2015-12-11 10:51:59.0 
+0100
@@ -1,3 +1,10 @@
+python-django (1.7.11-1) jessie; urgency=medium
+
+  * New upstream release incorporating former security updates and
+multiple bugfixes.
+
+ -- Raphaël Hertzog   Fri, 11 Dec 2015 10:44:42 +0100
+
 python-django (1.7.7-1+deb8u3) jessie-security; urgency=high
 
   * SECURITY UPDATE:
diff -Nru python-django-1.7.7/debian/.git-dpm 
python-django-1.7.11/debian/.git-dpm
--- python-django-1.7.7/debian/.git-dpm 1970-01-01 01:00:00.0 +0100
+++ python-django-1.7.11/debian/.git-dpm2015-12-11 10:51:59.0 
+0100
@@ -0,0 +1,11 @@
+# see git-dpm(1) from git-dpm package
+e4cd95fc1d5322f9bff209890b71f57ee9d36e62
+e4cd95fc1d5322f9bff209890b71f57ee9d36e62
+2d07f4b16101fcc8973128c4e4920b41f87175ee
+2d07f4b16101fcc8973128c4e4920b41f87175ee
+python-django_1.7.11.orig.tar.gz
+f9abaf7eacec73bc1c5e6080e2778a7174ebf9d4
+7586798
+debianTag="debian/%e%v"
+patchedTag="patched/%e%v"
+upstreamTag="upstream/%e%u"
diff -Nru 
python-django-1.7.7/debian/patches/02_disable-sources-in-sphinxdoc.diff 
python-django-1.7.11/debian/patches/02_disable-sources-in-sphinxdoc.diff
--- python-django-1.7.7/debian/patches/02_disable-sources-in-sphinxdoc.diff 
2015-03-23 20:52:49.0 +0100
+++ python-django-1.7.11/debian/patches/02_disable-sources-in-sphinxdoc.diff
2015-12-11 10:51:59.0 +0100
@@ -1,15 +1,25 @@
-Description: Disable creation of _sources directory by Sphinx
+From 09dc3a85f5a42a5695687c8105cc39f884c19931 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Rapha=C3=ABl=20Hertzog?= 
+Date: Sun, 11 Oct 2015 12:06:13 +1100
+Subject: Disable creation of _sources directory by Sphinx
+
  We do this to save some space as the sources of the documentation
  are not really useful in a binary package.
  .
  This is a Debian specific patch.
 Forwarded: not-needed
-Author: Raphaël Hertzog 
 Origin: vendor
 
+Patch-Name: 02_disable-sources-in-sphinxdoc.diff
+---
+ docs/conf.py | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/docs/conf.py b/docs/conf.py
+index 6df8dd8..90e4d69 100644
 --- a/docs/conf.py
 +++ b/docs/conf.py
-@@ -196,7 +196,10 @@ html_additional_pages = {}
+@@ -200,7 +200,10 @@ html_additional_pages = {}
  #html_split_index = False
  
  # If true, links to the reST sources are added to the pages.
diff -Nru python-django-1.7.7/debian/patches/03_manpage.diff 
python-django-1.7.11/debian/patches/03_manpage.diff
--- python-django-1.7.7/debian/patches/03_manpage.diff  2015-03-23 
20:52:49.0 +0100
+++ python-django-1.7.11/debian/patches/03_manpage.diff 2015-12-11 
10:51:59.0 +0100
@@ -1,12 +1,23 @@

Bug#807647: perl/experimental: trigger cycle on upgrades

[Niko Tyni]

Package: perl
Version: 5.22.1~rc4-1
Severity: serious
Tags: patch

When spamassassin is installed, upgrading perl et al. from sid/5.20
to experimental/5.22.1~rc4-1 breaks due to a trigger cycle, see below.

I believe perl.postinst should trigger 'perl-major-upgrade' with
'noawait'. Quoting deb-triggers(5):

   The “-noawait” variants should always be favored when possible
   since triggering packages are not put in triggers-awaited state and
   can thus be immediately configured without requiring the processing
   of  the trigger.   If  the  triggering  packages  are dependencies of
   other upgraded packages, it will avoid an early trigger processing
   run and make it possible to run the trigger only once as one of the
   last steps of the upgrade.

It seems sensible that perl configuration shouldn't wait for spamassassin
to recompile its ruleset.

I've tested locally that

--- a/debian/perl.postinst
+++ b/debian/perl.postinst
@@ -21,7 +21,7 @@ then
[ -n "$2" ] && \
dpkg --compare-versions "$2" lt 5.21.9
 then
-dpkg-trigger perl-major-upgrade
+dpkg-trigger --no-await perl-major-upgrade
 fi
 fi

makes the problem go away.

  Setting up perl (5.22.1~rc4-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
spamassassin -> spamassassin
   packages' pending triggers which are or may be unresolvable:
sa-compile: perl-major-upgrade
libc-bin: ldconfig
spamassassin: perl-major-upgrade
  dpkg: error processing package sa-compile (--configure):
   triggers looping, abandoned
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
spamassassin -> spamassassin -> spamassassin
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
spamassassin: perl-major-upgrade
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
spamassassin -> spamassassin -> spamassassin -> spamassassin -> 
spamassassin -> spamassassin
   packages' pending triggers which are or may be unresolvable:
spamassassin: perl-major-upgrade
  dpkg: error processing package spamassassin (--configure):
   triggers looping, abandoned
  Setting up libnet-ssleay-perl (1.72-1+b2) ...
  Setting up libhtml-parser-perl (3.71-2+b1) ...
  Setting up libnet-dns-perl (0.81-2+b1) ...
  Setting up libsocket6-perl (0.25-1+b2) ...
  Setting up libnetaddr-ip-perl (4.078+dfsg-1+b1) ...
  Errors were encountered while processing:
   sa-compile
   libc-bin
   spamassassin

-- 
Niko Tyni   nt...@debian.org

Bug#807651: udev: unowned files after purge (policy 6.8, 10.8): /etc/init/udev.override

[Michael Biebl]

Am 11.12.2015 um 11:40 schrieb Michael Biebl:

> That means someone called "update-rc.d udev disable".
> 
> The udev package itself doesn't do that afaics. Can you find out who?
> 
> I'm not convinced that the package itself should clean that up.

From a cursory glance, that seems to be duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806276

-- 
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#807012: python3-apt & unattended-upgrades get confused by uppercase pkg

[Julian Andres Klode]

Control: reassign -1 python-apt

On Fri, Dec 11, 2015 at 01:49:06PM +0100, Alexandre Detiste wrote:
> Le vendredi 11 décembre 2015, 13:37:32 Julian Andres Klode a écrit :
> > > Reading en.diff_Index translations from 
> > > /var/lib/apt/lists/ftp.be.debian.org_debian_dists_unstable_main_i18n_Translation-en.diff_Index:
> > >  done.  
> > > Rebuilding Xapian index... 0%
> > > Traceback (most recent call last):
> > >   File "/usr/sbin/update-apt-xapian-index", line 104, in 
> > > indexer.rebuild(opts.pkgfile)
> > >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 717, in 
> > > rebuild
> > > self.buildIndex(dbdir, generator)
> > >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 692, in 
> > > buildIndex
> > > for doc in documents:
> > >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 563, in 
> > > gen_documents_apt
> > > for idx, pkg in enumerate(cache):
> > >   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 231, in 
> > > __iter__
> > > yield self[pkgname]
> > >   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 200, in 
> > > __getitem__
> > > raise KeyError('The cache has no package named %r' % key)
> > > KeyError: "The cache has no package named 'WorldOfGoo'"
> > > 
> > > 
> > 
> > I'm running since multiple weeks with a dummy package 
> > installed and cannot produce any error.
> 
> I found just now that to reproduce this bug the package
> must be installed & available in a repository.

That helped me reproduce the issue. It is indeed a bug in
python-apt.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#807099: RFS: corsix-th/0.50-1 ITP 610087 - A Theme Hospital engine reimplementation.

[Markus Koschany]

Am 11.12.2015 um 12:35 schrieb Alexandre Detiste:
> Le dimanche 6 décembre 2015, 20:34:42 Markus Koschany a écrit :
>> Several Expat copyright holder are missing in
>> CorsixTH/Lua/languages
>> CorsixTH/Src/jit_opt.h
>> SpriteEncoder/*
>> LevelEdit/*
>>
>> GPL-3+
>> SpriteEncoder/parser.cpp
>> SpriteEncoder/tokens.h
> 
> This license has this special exception; does this mean
> it can be considered Expat-licensed as the whole game ?
> 
>As a special exception, you may create a larger work that contains
>part or all of the Bison parser skeleton and distribute that work
>under terms of your choice

I would add the following paragraph to debian/copyright to avoid any
confusion.

License: GPL-3+-with-exception
 On Debian systems, the complete text of the GNU General Public License
 version 3 can be found in `/usr/share/common-licenses/GPL-3'.
 .
 As a special exception, you may create a larger work that contains
 part or all of the Bison parser skeleton and distribute that work
 under terms of your choice, so long as that work isn't itself a
 parser generator using the skeleton or a modified version thereof
 as a parser skeleton.  Alternatively, if you modify or redistribute
 the parser skeleton itself, you may (at your option) remove this
 special exception, which will cause the skeleton and the resulting
 Bison output files to be licensed under the GNU General Public
 License without this special exception.

Bonus points if these files are generated automatically during the build.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#807616: [Pkg-xfce-devel] Bug#807616: lightdm: Lightdm (and KDM) does not autologin on desktop computers

[Avery Adams]

The installs were virtually identical, except for whatever packages Debian
may have chosen to install due to the hardware differences. I only
installed very few packages myself, such as VirtualBox, before I rebooted
to use autologin. I did this on both the laptop and one desktop. The other
desktop had a base setup only and still failed with XFCE and LightDM.

Sorry I sent the first one directly to Yves.

Bug#806206: [pkg-wine-party] Bug#806206: Bug#806206: wine don't install programs from CD

[Heiko Ernst]

Am Donnerstag, 10. Dezember 2015, 22:00:44 schrieb Jens Reyer:
> On 11/26/2015 08:24 AM, Heiko Ernst wrote:
> > Am Mittwoch, 25. November 2015, 10:28:28 schrieb Austin English:
> >> Do you have the cd/dvd mounted? Is it in dosdevices? Is there a
> >> symlink to the raw device in dosdevices? Are you attempting to 
start
> >> the installer with the full path (e.g., wine "D:\\setup.exe")?
> > 
> > I have mounted the dvd on kde 5 and start with wine "D:
\\setup.exe". The
> > installe start and show an undefined error on kde.
> 
> And what happens if you try it directly from the CD, e.g. if it was
> mounted to /mount/user/risen/:
>   cd /mount/user/risen/
>   wine setup.exe

how can i mount this to /mount/useres/risen/ ?

Bug#807012: python3-apt & unattended-upgrades get confused by uppercase pkg

[Julian Andres Klode]

Control: reassign -1 apt

On Fri, Dec 11, 2015 at 02:01:44PM +0100, Julian Andres Klode wrote:
> Control: reassign -1 python-apt
> 
> On Fri, Dec 11, 2015 at 01:49:06PM +0100, Alexandre Detiste wrote:
> > Le vendredi 11 décembre 2015, 13:37:32 Julian Andres Klode a écrit :
> > > > Reading en.diff_Index translations from 
> > > > /var/lib/apt/lists/ftp.be.debian.org_debian_dists_unstable_main_i18n_Translation-en.diff_Index:
> > > >  done.  
> > > > Rebuilding Xapian index... 0%
> > > > Traceback (most recent call last):
> > > >   File "/usr/sbin/update-apt-xapian-index", line 104, in 
> > > > indexer.rebuild(opts.pkgfile)
> > > >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 717, in 
> > > > rebuild
> > > > self.buildIndex(dbdir, generator)
> > > >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 692, in 
> > > > buildIndex
> > > > for doc in documents:
> > > >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 563, in 
> > > > gen_documents_apt
> > > > for idx, pkg in enumerate(cache):
> > > >   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 231, in 
> > > > __iter__
> > > > yield self[pkgname]
> > > >   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 200, in 
> > > > __getitem__
> > > > raise KeyError('The cache has no package named %r' % key)
> > > > KeyError: "The cache has no package named 'WorldOfGoo'"
> > > > 
> > > > 
> > > 
> > > I'm running since multiple weeks with a dummy package 
> > > installed and cannot produce any error.
> > 
> > I found just now that to reproduce this bug the package
> > must be installed & available in a repository.
> 
> That helped me reproduce the issue. It is indeed a bug in
> python-apt.
> 

It turns out to be a bug in APT itself. dpkg converts the
package name to lower case after reading it, APT does not
do the same.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#776409: cryptsetup fails to unlock volumes with key files from initramfs

[Guilhem Moulin]

On Fri, 11 Dec 2015 at 01:48:24 +, Ben Hutchings wrote:
> So don't assume; add $rootmnt to the beginning of the paths.

Sure.  I was only wondering if the documentation was outdated since you
said /root not $rootmnt in message 61.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#807672: natlog: FTBFS: [/usr/bin/icmbuild, line 166] Error: idx undefined

[Chris Lamb]

Source: natlog
Version: 1.02.00-4
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

natlog fails to build from source in unstable/amd64:

  [..]

  # Add here commands to configure the package.
  touch configure-stamp
  dh_testdir
  # compile the package.
  ./build program
  [icmake/md, line 15] Warning: `sizeof' is deprecated. Use `listlen'
  
  touch version.cc
  gcc -E VERSION.h | grep -v '#' | sed 's/\"//g' > release.yo
  icmbuild program 
  [/usr/bin/icmbuild, line 166] Error: idx undefined
  [/usr/bin/icmbuild, line 166] Error: Incorrect returntype for function 
'find()'
  
  2 error(s) detected
  Fatal: system - failure of system call (status 256)
  debian/rules:33: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


natlog.1.02.00-4.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807673: perspectives-extension: FTBFS: ValueError: empty namespace prefix is not supported in ElementPath

[Chris Lamb]

Source: perspectives-extension
Version: 4.6.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

perspectives-extension fails to build from source in unstable/amd64:

  [..]

 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151211162639.kdboGsbOYR/perspectives-extension-4.6.2'
  rm -f Perspectives.xpi
  rm -rf build/
  python test/extlib/checkloc.py plugin
  (Main) Starting Localization tests...
  Traceback (most recent call last):
File "test/extlib/checkloc.py", line 730, in 
  errors = validate_loc_files(args.manifest_dir, locales_only=locales_only)
File "test/extlib/checkloc.py", line 601, in validate_loc_files
  ms.validate_manifests()
File "test/extlib/checkloc.py", line 480, in validate_manifests
  for locale in root.findall('.//em:locale', root.nsmap):
File "src/lxml/lxml.etree.pyx", line 1563, in lxml.etree._Element.findall 
(src/lxml/lxml.etree.c:61450)
File "/usr/lib/python2.7/dist-packages/lxml/_elementpath.py", line 304, in 
findall
  return list(iterfind(elem, path, namespaces))
File "/usr/lib/python2.7/dist-packages/lxml/_elementpath.py", line 277, in 
iterfind
  selector = _build_path_iterator(path, namespaces)
File "/usr/lib/python2.7/dist-packages/lxml/_elementpath.py", line 234, in 
_build_path_iterator
  raise ValueError("empty namespace prefix is not supported in ElementPath")
  ValueError: empty namespace prefix is not supported in ElementPath
  Makefile:21: recipe for target 'loctests' failed
  make[1]: *** [loctests] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211162639.kdboGsbOYR/perspectives-extension-4.6.2'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:3: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


perspectives-extension.4.6.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807527: initramfs-tools: Please provide an API or best practices for custom initramfs hook configuration

[Guilhem Moulin]

On Fri, 11 Dec 2015 at 00:54:03 +, Ben Hutchings wrote:
> On Thu, 2015-12-10 at 12:15 +0100, Jonas Meurer wrote:
>> Hi there,
>> 
>> On Thu, 10 Dec 2015 02:52:11 +0100 Guilhem Moulin 
>> wrote:
>>> AFAIK there is no documentation for where users should set variables to
>>> configure an initramfs hook.  There are a couple of workaround, all
>>> hacky and/or relying on undocumented properties of initramfs-tools(8):
>>> 
>>>   1/ Setting said variable in initramfs.conf(5).  (Since hook scripts
>>>  are executed is sub-shells the variable need to be exported.)  This
>>>  is somewhat ugly since initramfs.conf(5) is the configuration file
>>>  *for mkinitramfs*, not for the hook files.
>>> 
>>>   2/ Using /usr/share/initramfs-tools/conf-hooks.d/$hook.  This is an
>>>  undocumented (short of an entry in the changelog) hack.  Also
>>>  unless that file is marked as a conffile (which violates the
>>>  policy) user modifications are wiped upon upgrade.
>> 
>> If I got it right (didn't find documentation about it), the current
>> purpose of conf-hooks.d seems to be to configure *mkinitramfs* in a
>> proper way required by the hook scripts, not to set configuration
>> variables for the hook scripts themselves, no?
> 
> The only documentation I'm aware of is in the changelog:
> 
>   * mkinitramfs: Export MODULES, allows hook scripts to act accordingly.
>     (closes: #421658) Add /usr/share/initramfs-tools/conf-hooks.d for hooks
>     options on mkinitramfs run. Do not land in initramfs.

Please consider adding it to the mkinitramfs manpage, too.  Package
maintainers can't rely on something that's only documented in the
manpage, IMHO.
 
> Also, it doesn't make any sense to me, to put hook-specific
> configuration into a namespace shared across all hooks.  You can
> always add a configuration file to your own package and source it in
> your hook script.

Using /etc/$package/initramfs adds a useless directory level for
packages that only ship initramfs hook and script.  The directory
/etc/default is shared, also.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#807674: printer-driver-gutenprint: Canon S4500: Papersize A3 is missing.

[Gerald Kollenda]

Package: printer-driver-gutenprint
Version: 5.2.10-3
Severity: normal

Dear Maintainer,

When printing, using the Canon S4500 the paper size A3 is not available (cannot
be selected).
The printer itself is able to handle A3-paper. (german/european standard,
420*297mm)
I tried the selection in "Druckeinstellungen" (printer settings) and in several
applications.

In debian 6 (my former distibution) A3-paper could be selected and used.

In the /etc/cups/ppd/Canon-S4500.ppd of debian 8 no A3 PageSize is mentioned.

I compared the .ppd to the version of debian 6, there A3-paper is specified.

I tried, but I am not deep enough in .ppd-files to solve the problem by myself
and write a patch.




-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages printer-driver-gutenprint depends on:
ii  cups 1.7.5-11+deb8u1
ii  cups-client  1.7.5-11+deb8u1
ii  cups-filters [ghostscript-cups]  1.0.61-5+deb8u2
ii  libc62.19-18+deb8u1
ii  libcups2 1.7.5-11+deb8u1
ii  libcupsimage21.7.5-11+deb8u1
ii  libgutenprint2   5.2.10-3
ii  libusb-1.0-0 2:1.0.19-1

printer-driver-gutenprint recommends no packages.

Versions of packages printer-driver-gutenprint suggests:
pn  gutenprint-doc  
pn  gutenprint-locales  

-- no debconf information

Bug#807502: gcc-avr: Missing support for atxmega

[Thorsten Schulz]

Hej,

this may be a broader issue. I must confirm this bug for the x32e5 as well.
Stepping gcc-avr back to testing helps for the meanwhile.

The complained files do not exist in earlier versions. So either this 
may be a problem of a new feature or some odd configuration. GOOD LUCK, 
I have no idea :/

Bug#807677: RM: haskell-scrobble -- ROM; Unmaintained by upstream

[Joachim Breitner]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

another leaf package with insufficient upstream activity. Please remove
from the archive.

Joachim

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlZq4xgACgkQ9ijrk0dDIGwEbwCgl/Wt9s5F4vSMoHWJMG7TztQ9
GUcAn09e2ml1F6QJhTb9jDmTXulOxCQj
=65RC
-END PGP SIGNATURE-

Bug#807666: nmu: mpich_3.1-6

[Samuel Thibault]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

Compiling c++ programs against mpich currently fails in sid:

In file included from /usr/include/mpich/mpi.h:2175:0,
 from test.c:1:
/usr/include/mpich/mpicxx.h:22:4: error: #error 'Please use the same version of 
GCC and g++ for compiling MPICH and user MPI programs'
 #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'

Apparently mpich got built with 5.2, and sid currently has 5.3, thus the
failure.  Rebuilding mpich with current gcc 5.3 should be fixing it.

Samuel

nmu mpich_3.1-6 . ANY . unstable . -m "Rebuild against g++ 5.3"

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

Kernel: Linux 4.3.0 (SMP w/4 CPU cores)
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)

-- 
Samuel
 Créer une hiérarchie supplementaire pour remedier à un problème (?) de
 dispersion est d'une logique digne des Shadocks.
 * BT in: Guide du Cabaliste Usenet - La Cabale vote oui (les Shadocks aussi) *

Bug#807667: schroot-mount doesn't cope well with absolute symlinks in mount points

[Yann Soubeyrand]

Package: schroot
Version: 1.6.10-1+b1
Severity: normal
Tags: upstream

Dear maintainer,

The description of this bug can be found upstream at
https://github.com/codelibre-net/schroot/issues/21.

Regards

Bug#807671: 20copyfiles doesn't cope well with absolute symlinks in destination path

[Yann Soubeyrand]

Package: schroot
Version: 1.6.10-1+b1
Severity: normal
Tags: upstream

Dear maintainer,

A patch for this bug is being discussed upstream at
https://github.com/codelibre-net/schroot/pull/20.

Regards

Bug#807665: apt-listbugs: please allow q as alias for n

[Julian Andres Klode]

Package: apt-listbugs
Version: 0.1.17
Severity: wishlist

What happens after pinning is that I try q a few
times and then press Ctrl+D because q does not do
anything. It somehow does not occur to me that I
would need to press n. Probably used vi too often
in the past months.

So, it would be nice if you could allow q as an
alias for n. 

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

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

Versions of packages apt-listbugs depends on:
ii  apt 1.1.4
ii  ruby1:2.2.3
ii  ruby-debian 0.3.9+b4
ii  ruby-gettext3.1.7-1
ii  ruby-soap4r 2.0.5-3
ii  ruby-unicode0.4.4-2+b5
ii  ruby-xmlparser  0.7.3-1+b2
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.3-2

Versions of packages apt-listbugs recommends:
ii  ruby-httpclient  2.3.3-3.1

Versions of packages apt-listbugs suggests:
ii  debianutils 4.5.1
ii  epiphany-browser [www-browser]  3.18.1-1
ii  google-chrome-stable [www-browser]  47.0.2526.80-1
ii  links2 [www-browser]2.12-1+b1
ii  lynx-cur [www-browser]  2.8.9dev6-5
ii  netsurf [www-browser]   3.2+dfsg-2.2
ii  netsurf-gtk [www-browser]   3.2+dfsg-2.2+b1
ii  reportbug   6.6.5
ii  w3m [www-browser]   0.5.3-26

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#768651:

[Vega Hidalgo, Jose Antonio]

$850,000 was donated to you reply to ( 
hawil6...@mediacombb.net ) for details.

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[John Paul Adrian Glaubitz]

On 12/11/2015 02:56 PM, Gianfranco Costamagna wrote:
> I have a build ongoing right now in amd64 i386 arm64 armel armhf powerpc.

Sounds good.

> the builds seems fine, at least I had to tweak a little bit the symbols and 
> change something in changelog

Ok, good.

> e.g. a symbol was leftover in symbols file:
> + _ZN8Echonest12AudioSummary12setTimestampEf@Base 2.1.0
> and was preventing amd64 and i386 builds to succeed.

Btw, Stefan noticed that armel and armhf seem to have completely
different symbol tables as the types for many of the function
symbols are changed from double to float.

Did you verify that?

> as you wish, if you want to sponsor please look at this debdiff, otherwise I 
> can sponsor in a few minutes, because it seems good now.

If you are sure that the symbol files for all architectures are
fixed, please go ahead and upload. I can take care of the ports
architectures in case something breaks.

Adrian

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

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[John Paul Adrian Glaubitz]

(Sorry for the slightly asynchronous reply, I got interrupted)

On 12/11/2015 03:01 PM, Gianfranco Costamagna wrote:
> this is *exactly* the reason for trying all yesterday evening to get it 
> working :)
> (pbuilder now fails under qemu and arm*, probably because of the new 
> aptitude, so I had to push on DebOMatic my builds)

Use sbuild instead. It's much more flexible anyway and easier to
set up and also what we use on the official buildds (and the
buildds in debian-ports).

I have stopped pbuilder long time ago, too unflexible and too
slow. sbuild with eatmydata, ccache and btrfs-snapshots is
extremely fast. Just using eatmydata cut my build times in
half for smaller packages.

>> If you are sure that the symbol files for all architectures are
>> fixed, please go ahead and upload. I can take care of the ports
>> architectures in case something breaks.
> 
> 
> I guess also the ports should be good.

Yeah, you got the build logs as a reference, so it shouldn't
be too difficult.

> (I don't want to steal your upload, but I spent all yesterday looking at this 
> package, and I'm learning a lot from this experience :) )

Don't worry. It's not important for me to do it myself, especially
when others can learn from this experience. I have done such fixes
endless times, I don't find them entertaining anymore ;-).

Just make sure everything is fixed properly to avoid additional
uploads.

Adrian

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

Bug#807676: [gnupg2] Update to 2.1.10 break hidden-encrypt-to with groups

[LeJacq, Jean Pierre]

Package: gnupg2
Version: 2.1.10-1
Severity: normal

--- Please enter the report below this line. ---

Decryption fails if the group mechanism is used by the sender when encrypting 
when \ a users ~/.gnupg/gpg.conf file with the hidden-encrypt-to option.

group mygr...@acme.org=0x 0x
hidden-encrypt-to mygr...@acme.org

This worked for the 2.0.x and version 2.1.9 and below.


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.3.0-trunk-amd64

Debian Release: stretch/sid
  800 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 stable  dl.google.com 
  100 experimentalftp.us.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-=
gnupg-agent (= 2.0.26-1) | 2.1.10-1
libassuan0(>= 2.0.1) | 2.4.2-1
libbz2-1.0   | 1.0.6-8
libc6  (>= 2.15) | 
libcurl3-gnutls  (>= 7.16.2) | 
libgcrypt20   (>= 1.6.1) | 
libgpg-error0  (>= 1.10) | 
libksba8  (>= 1.2.0) | 
libreadline6(>= 6.0) | 
zlib1g  (>= 1:1.1.4) | 
dpkg(>= 1.15.4)  | 
 OR install-info | 


Recommends (Version) | Installed
-+-===
libldap-2.4-2 (>= 2.4.7) | 2.4.42+dfsg-2


Suggests(Version) | Installed
=-+-===
gnupg-doc | 
parcimonie| 
xloadimage| 

-- 
JP


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

Bug#807012: python3-apt & unattended-upgrades get confused by uppercase pkg

[Julian Andres Klode]

On Fri, Dec 04, 2015 at 08:52:59PM +0100, Alexandre Detiste wrote:
> Le vendredi 4 décembre 2015, 10:16:05 Julian Andres Klode a écrit :
> > Control: reassign -1 unattended-upgrades
> > 
> > On Fri, Dec 04, 2015 at 08:06:36AM +0100, Alexandre Detiste wrote:
> > > Package: python3-apt
> > > Version: 1.1.0~beta1
> > > Severity: normal
> > > 
> > > Hi,
> > > 
> > > Since the last update of python3-apt to 1.1, unattended-upgrades
> > > is crashing on a package with an uppercase case name.
> > > 
> > > I do know this package is not policy-compliant;
> > > but still UU / python3-apt should handle this situation
> > > in a more gracefull way than a triple exception.
> > > (and more enterprise-ish stuff may want to use
> > > uppercase package names too)
> > 
> > dpkg won't even let you create packages with upper case package
> > names.
> > 
> > Internally they are mapped to lowercase before entered into the
> > cache, so I don't know where unattended-upgrades gets the mixed
> > case name from.
> > 
> > The behaviour of not accepting the upper case name is consistent
> > with APT (apt-cache show WorldOfGoo fails) and dpkg (dpkg -l 
> > WorldOfGoo fails too).
> > 
> > As such, I'm not going to fix this in python-apt. This should
> > be patched in unattended-upgrades that gets a mixed name from
> > somewhere it should not look at.
> > 
> > 
> 
> (keeping you in CC because I don't know if you'll get this mail
> after bug has been reassigned)
> 
> 
> update-apt-xapian-index now barfs on this upercase package too.
> 
> I agree the package was likely built on a Debian-less system with "ar + tar"  
> and without lintian.
> 
> It looks like in some cases the package name is converted to lowercase
> and in other cases not.
> 
> 
> 
> Reading en.diff_Index translations from 
> /var/lib/apt/lists/ftp.be.debian.org_debian_dists_unstable_main_i18n_Translation-en.diff_Index:
>  done.  
> Rebuilding Xapian index... 0%
> Traceback (most recent call last):
>   File "/usr/sbin/update-apt-xapian-index", line 104, in 
> indexer.rebuild(opts.pkgfile)
>   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 717, in rebuild
> self.buildIndex(dbdir, generator)
>   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 692, in 
> buildIndex
> for doc in documents:
>   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 563, in 
> gen_documents_apt
> for idx, pkg in enumerate(cache):
>   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 231, in __iter__
> yield self[pkgname]
>   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 200, in 
> __getitem__
> raise KeyError('The cache has no package named %r' % key)
> KeyError: "The cache has no package named 'WorldOfGoo'"
> 
> 

I'm running since multiple weeks with a dummy package 
installed and cannot produce any error.

Running update-apt-xapian-index works fine as well.

So I'm sorry, but I can't help here, I don't know where your code
get's a mixed case package name from, but the expected response
to mixed case package names is a "no such package" response.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#807012: python3-apt & unattended-upgrades get confused by uppercase pkg

[Alexandre Detiste]

Le vendredi 11 décembre 2015, 13:37:32 Julian Andres Klode a écrit :
> > Reading en.diff_Index translations from 
> > /var/lib/apt/lists/ftp.be.debian.org_debian_dists_unstable_main_i18n_Translation-en.diff_Index:
> >  done.  
> > Rebuilding Xapian index... 0%
> > Traceback (most recent call last):
> >   File "/usr/sbin/update-apt-xapian-index", line 104, in 
> > indexer.rebuild(opts.pkgfile)
> >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 717, in 
> > rebuild
> > self.buildIndex(dbdir, generator)
> >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 692, in 
> > buildIndex
> > for doc in documents:
> >   File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 563, in 
> > gen_documents_apt
> > for idx, pkg in enumerate(cache):
> >   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 231, in 
> > __iter__
> > yield self[pkgname]
> >   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 200, in 
> > __getitem__
> > raise KeyError('The cache has no package named %r' % key)
> > KeyError: "The cache has no package named 'WorldOfGoo'"
> > 
> > 
> 
> I'm running since multiple weeks with a dummy package 
> installed and cannot produce any error.

I found just now that to reproduce this bug the package
must be installed & available in a repository.

Here removing this .deb from my local reprepro repository solved the problem.

> Running update-apt-xapian-index works fine as well.
> 
> So I'm sorry, but I can't help here, I don't know where your code
> get's a mixed case package name from, but the expected response
> to mixed case package names is a "no such package" response.

That's right; you may close this bug as it only relate
to people running unofficial repository with broken
unofficial .deb files.


Greets,

Alexandre

Bug#791463: closing RFS: udfclient/0.8-1 [ITP] -- userland implementation of the UDF filesystem

[Andrew Shadura]

On 11 December 2015 at 12:58, Gianfranco Costamagna
 wrote:
> Hi Pali, can you please reupload?
>
> Andrew are you still interested in looking at it?

Gianfranco, if you wish to sponsor it, please go ahead. And please
make sure Pali uses the feature of bmake package I developed for his
specific use case ;)

-- 
Cheers,
  Andrew

Bug#807664: python3-cap-ng: Python3 import error: undefined symbol: capng_print_caps_numeric

[Benjamin Drung]

Package: python3-cap-ng
Version: 0.7.7-1
Severity: grave
Justification: renders package unusable

Hi,

The Python3 library doesn't work at all. A simple import causes an import error:

$ cat test.py 
#!/usr/bin/python3
import capng
$ python3 test.py
Traceback (most recent call last):
  File "test.py", line 2, in 
import capng
  File "/usr/lib/python3/dist-packages/capng.py", line 28, in 
_capng = swig_import_helper()
  File "/usr/lib/python3/dist-packages/capng.py", line 24, in swig_import_helper
_mod = imp.load_module('_capng', fp, pathname, description)
  File "/usr/lib/python3.4/imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
ImportError: 
/usr/lib/python3/dist-packages/_capng.cpython-34m-x86_64-linux-gnu.so: 
undefined symbol: capng_print_caps_numeric

Maybe this is related to the ignored build error:

===
libtool: install: warning: remember to run `libtool --finish 
/usr/lib/python3.4/site-packages'
 /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/lib/python3.4/site-packages'
 /usr/bin/install -c -m 644 capng.py 
'/«PKGBUILDDIR»/debian/tmp/usr/lib/python3.4/site-packages'
Byte-compiling python modules...
  File "/usr/lib/python3.4/site-packages/capng.py", line 141
def capng_clear(*args) -> "void" :
   ^
SyntaxError: invalid syntax

capng.py
Byte-compiling python modules (optimized versions) ...
===

The test was done in an up-to-date unstable chroot with python3 3.4.3-10+b1.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.

Bug#577785: Provide variable DEB_MAVEN_BUILDFILE to specify alternating pom.xml file

[Emmanuel Bourg]

control: tags -1 + wontfix
control: done -1

Adding a DEB_MAVEN_BUILDFILE variable isn't necessary, the same result
can be achieved with DEB_MAVEN_ARGS:

DEB_MAVEN_ARGS := -f path/to/pom.xml

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[Gianfranco Costamagna]

I'm looking at it soon.

I already have a look yesterday, but I had issues with some arm platforms.

Now I should have time to finish it.

cheers,

G.





Il Venerdì 11 Dicembre 2015 10:27, Stefan Ahlers  ha 
scritto:
Hi Adrian,

> If you like, you can send me a debdiff with your changes and I can
> quickly review it and test-build it on one of the buildds.

here is a new version of the debdiff. I have included the differences of
armhf and armel architechture into the libechonest2.3.symbol file.
I hope I have not make a mistake, again.

Cheers,
Stefan

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[John Paul Adrian Glaubitz]

On 12/11/2015 02:36 PM, Gianfranco Costamagna wrote:
> I'm looking at it soon.

You don't have to. Stefan has already made a proposed change which
I will testbuild later today or tomorrow. I'm just still at work :).

Adrian

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

Bug#748664: libquvi: upload 0.9.x to unstable

[Alberto Garcia]

On Fri, Nov 20, 2015 at 02:19:55PM +0100, Sebastien Bacher wrote:

> What's the status of getting the new version in unstable?

I've been checking the reverse dependencies of libquvi7, and there are
not many. However it looks like the API has changed. I cannot build
cclive against libquvi 0.9, so it would need to fixed.

On the other hand, it looks like both libquvi versions can be
installed in parallel, so what's preventing us from uploading the
current packages to unstable as they are now?

Totem needs them, and it's also blocking the update of grilo-plugins.

Berto

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[Gianfranco Costamagna]

Hi again,

>Btw, Stefan noticed that armel and armhf seem to have completely
>different symbol tables as the types for many of the function
>symbols are changed from double to float.
>
>Did you verify that?


this is *exactly* the reason for trying all yesterday evening to get it working 
:)
(pbuilder now fails under qemu and arm*, probably because of the new aptitude, 
so I had to push on DebOMatic my builds)

I could try a porterbox next time...

>If you are sure that the symbol files for all architectures are
>fixed, please go ahead and upload. I can take care of the ports
>architectures in case something breaks.


I guess also the ports should be good.


I think we are good now, lets see!

(I don't want to steal your upload, but I spent all yesterday looking at this 
package, and I'm learning a lot from this experience :) )

cheers!

G.

Bug#807663: Split snippet fastcgi-php/conf, leaving leading fastcgi_split_path_info out

[Christos Trochalakis]

Hello Gerardo,

On Fri, Dec 11, 2015 at 08:14:45AM -0400, Gerardo Esteban Malazdrewicz wrote:

Package: nginx-common
Version: 1.9.6-2
Severity: wishlist

The need for a custom fastcgi_split_path_info renders snippet unusable.



fastcgi-php.conf is there to capture 90% of all the PHP configurations
out there. I don't think we should make this more complex for now, one
can copy the snippet and remove the split directive.

But, if more people request it we 'll reconsider!

Thank again,
chris

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[Stefan Ahlers]

Hi,

> anyway, I still get issues with armhf and armel, but this time they seem to 
> be related
> to one symbols wrong copy-pasted on line 249
> _ZN8Echonest4Term9setWeightEf@Base instead of 
> _ZN8Echonest4Term12setFrequencyEf@Base

Hmm, it looks like I'm too unconsecrated. Fixed.
> and something on the qt5 package.
Ok, this was a copy and paste error, too. armhf was listed for the wrong
symbols. Done.

Bug#791463: closing RFS: udfclient/0.8-1 [ITP] -- userland implementation of the UDF filesystem

[Gianfranco Costamagna]

Hi Andrew,

>Gianfranco, if you wish to sponsor it, please go ahead. And please
>make sure Pali uses the feature of bmake package I developed for his
>specific use case ;)


I'm not a bmake-savvy person, I don't think I'll be able to check if the 
packaging
is really error prone...

cheers,

G.

Bug#802665: augeas-lenses: httpd lens is broken in 1.2

[Yann Soubeyrand]

On Tue, 27 Oct 2015 13:37:46 + Dominic Cleal  wrote:
> On 22/10/15 11:52, Erebus wrote:
> > Package: augeas-lenses
> > Version: 1.2.0-0.2
> > Severity: serious
> > Justification: httpd lens is broken in 1.2 
> > 
> > Dear Maintainer,
> > 
> > I have learned that augeas-lenses v1.2 includes a broken httpd lens. In
> > particular, the 1.2 lens throws errors when an httpd config happens to end 
> > with
> > a comment. This is causing trouble for several other projects.
> > 
> > This issue is fixed in upstream version 1.4.
> >
> > See also: https://github.com/letsencrypt/letsencrypt/issues/981
> 
> Attached is a patch against upstream's Augeas 1.2.0 tarball to resolve
> the issue reported on the letsencrypt issue when parsing ssl.conf.

I'm wondering if the severity of that bug could not be reduced. Indeed,
I wasn't successful trying to reproduce the bug mentioned in the above
link concerning ssl.conf.
https://github.com/letsencrypt/letsencrypt/issues/981#issuecomment-148525136 
suggests version 1.2 isn't affected by this bug. However the attached patch 
fixes some other bugs with 1.2 httpd lens which I was able to reproduce.

Dominic, Erebus, before lowering the severity of this bug, could you
confirm or infirm that the bug with the sample ssl.conf isn't present in
Augeas 1.2? And do you confirm that the httpd lens in Augeas 1.2 isn't
broken any more once the attached patch is applied?

Cheers

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[Stefan Ahlers]

Hi,

first of all, thank you for your help, both of you! I also learned a lot
from this experience.

> e.g. a symbol was leftover in symbols file:
> + _ZN8Echonest12AudioSummary12setTimestampEf@Base 2.1.0
> and was preventing amd64 and i386 builds to succeed.

You are right, it seems that I have forgotten this line to exclude for
the other architecture, sorry. But now it looks good for me, too!

The package on mentors.debian.net should be up to date, now. (Hopefully :-))

Stefan

Bug#807670: Can't build linux-tools-4.2 package

[Alexey]

Package: linux-perf
Version: 4.2
Source: linux-tools-4.2-2


Hello!
When I try to build source package I got error.

Command: dpkg-buildpackage -uc -us -nc -d -S -i -I 
--source-option=--unapply-patches

Result:
dpkg-buildpackage: source package linux-tools
dpkg-buildpackage: source version 4.2-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Ben Hutchings 
 dpkg-source -i -I --unapply-patches --before-build linux-tools-4.2
dpkg-source: info: using options from 
linux-tools-4.2/debian/source/options: --compression=xz

dpkg-source: info: applying gitignore.patch
dpkg-source: info: applying modpost-symbol-prefix.patch
can't find file to patch at input line 15
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|From: Chris Boot 
|Date: Mon, 01 Jul 2013 23:10:02 +0100
|Subject: modpost symbol prefix setting
|Forwarded: not-needed
|
|[bwh: The original version of this was added by Bastian Blank.  The
|upstream code includes  so that 
|can tell whether C symbols have an underscore prefix.  Since we build
|modpost separately from the kernel,  won't exist.
|However, no Debian Linux architecture uses the symbol prefix, so we
|can simply omit it.]
|
|--- a/scripts/mod/modpost.c
|+++ b/scripts/mod/modpost.c
--
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is 
malformed
dpkg-source: info: if patch 'modpost-symbol-prefix.patch' is correctly 
applied by quilt, use 'quilt refresh' to update it
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b 
-B .pc/modpost-symbol-prefix.patch/ --reject-file=- < 
linux-tools-4.2/debian/patches/modpost-symbol-prefix.patch gave error 
exit status 1
dpkg-buildpackage: error: dpkg-source -i -I --unapply-patches 
--before-build linux-tools-4.2 gave error exit status 2




If I execute build command again without cleaning catalog source package 
will be build successfully.
I make my build with git-buildpackage software. And I have separated 
debian and upstream branches, which specified in debian/gbp.conf.
If I manually create .gitignore file like this doing patch 
gitignore.path that build will be successful too. I have many other 
packages which do not behave strangely.


Whats wrong with tis repo?

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

[Gianfranco Costamagna]

Hi,

>You are right, it seems that I have forgotten this line to exclude for
>the other architecture, sorry. But now it looks good for me, too!


nope, the lines was already splitted, just just forgot to delete it.
now you have twice that symbol.

anyway, I still get issues with armhf and armel, but this time they seem to be 
related
to one symbols wrong copy-pasted on line 249
_ZN8Echonest4Term9setWeightEf@Base instead of 
_ZN8Echonest4Term12setFrequencyEf@Base

and something on the qt5 package.


- (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el ppc64 ppc64el s390x 
sparc64)_ZThn16_N8Echonest11CatalogSongD0Ev@Base 2.1.0
- (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el ppc64 ppc64el s390x 
sparc64)_ZThn16_N8Echonest11CatalogSongD1Ev@Base 2.1.0
- (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el ppc64 ppc64el s390x 
sparc64)_ZThn16_N8Echonest13CatalogArtistD0Ev@Base 2.1.0
- (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el ppc64 ppc64el s390x 
sparc64)_ZThn16_N8Echonest13CatalogArtistD1Ev@Base 2.1.0
- (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el ppc64 ppc64el s390x 
sparc64)_ZThn16_NK8Echonest11CatalogSong4typeEv@Base 2.1.0
- (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el ppc64 ppc64el s390x 
sparc64)_ZThn16_NK8Echonest13CatalogArtist4typeEv@Base 2.1.0
- (arch=!alpha !amd64 !arm64 !armhf !kfreebsd-amd64 !mips64el !ppc64 !ppc64el 
!s390x !sparc64)_ZThn8_N8Echonest11CatalogSongD0Ev@Base 2.1.0
- (arch=!alpha !amd64 !arm64 !armhf !kfreebsd-amd64 !mips64el !ppc64 !ppc64el 
!s390x !sparc64)_ZThn8_N8Echonest11CatalogSongD1Ev@Base 2.1.0
- (arch=!alpha !amd64 !arm64 !armhf !kfreebsd-amd64 !mips64el !ppc64 !ppc64el 
!s390x !sparc64)_ZThn8_N8Echonest13CatalogArtistD0Ev@Base 2.1.0
- (arch=!alpha !amd64 !arm64 !armhf !kfreebsd-amd64 !mips64el !ppc64 !ppc64el 
!s390x !sparc64)_ZThn8_N8Echonest13CatalogArtistD1Ev@Base 2.1.0
- (arch=!alpha !amd64 !arm64 !armhf !kfreebsd-amd64 !mips64el !ppc64 !ppc64el 
!s390x !sparc64)_ZThn8_NK8Echonest11CatalogSong4typeEv@Base 2.1.0
- (arch=!alpha !amd64 !arm64 !armhf !kfreebsd-amd64 !mips64el !ppc64 !ppc64el 
!s390x !sparc64)_ZThn8_NK8Echonest13CatalogArtist4typeEv@Base 2.1.0
+#MISSING: 2.3.1-0.3# (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el 
ppc64 ppc64el s390x sparc64)_ZThn16_N8Echonest11CatalogSongD0Ev@Base 2.1.0
+#MISSING: 2.3.1-0.3# (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el 
ppc64 ppc64el s390x sparc64)_ZThn16_N8Echonest11CatalogSongD1Ev@Base 2.1.0
+#MISSING: 2.3.1-0.3# (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el 
ppc64 ppc64el s390x sparc64)_ZThn16_N8Echonest13CatalogArtistD0Ev@Base 2.1.0
+#MISSING: 2.3.1-0.3# (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el 
ppc64 ppc64el s390x sparc64)_ZThn16_N8Echonest13CatalogArtistD1Ev@Base 2.1.0
+#MISSING: 2.3.1-0.3# (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el 
ppc64 ppc64el s390x sparc64)_ZThn16_NK8Echonest11CatalogSong4typeEv@Base 2.1.0
+#MISSING: 2.3.1-0.3# (arch=alpha amd64 arm64 armhf kfreebsd-amd64 mips64el 
ppc64 ppc64el s390x sparc64)_ZThn16_NK8Echonest13CatalogArtist4typeEv@Base 2.1.0
+ _ZThn8_N8Echonest11CatalogSongD0Ev@Base 2.1.0
+ _ZThn8_N8Echonest11CatalogSongD1Ev@Base 2.1.0
+ _ZThn8_N8Echonest13CatalogArtistD0Ev@Base 2.1.0
+ _ZThn8_N8Echonest13CatalogArtistD1Ev@Base 2.1.0
+ _ZThn8_NK8Echonest11CatalogSong4typeEv@Base 2.1.0
+ _ZThn8_NK8Echonest13CatalogArtist4typeEv@Base 2.1.0




I'll be back soon.

Bug#807669: dh-strip-nondeterminism: Breaks some jar file

[Sophie Brun]

Package: dh-strip-nondeterminism
Version: 0.014-1
Severity: normal

When building the package dirbuster (for kali), dh_strip_nondeterminism breaks 
the jar file.

The package is built but when I tried to launch the program, it failed with 
this error:
Exception in thread "main" java.lang.SecurityException: Invalid signature file 
digest for Manifest main attributes
at 
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:287)
at 
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:240)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:274)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:348)
at java.util.jar.JarFile.getInputStream(JarFile.java:415)
at 
sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:775)
at sun.misc.Resource.cachedInputStream(Resource.java:77)
at sun.misc.Resource.getByteBuffer(Resource.java:160)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:436)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at com.sittinglittleduck.DirBuster.Start.main(Start.java:51)


Disabling dh_strip_nondeterminism in debian/rules (via override_dh_...)
fixed it.

The source of package dirbuster can be found:
git://git.kali.org/packages/dirbuster.git

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

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

Versions of packages dh-strip-nondeterminism depends on:
ii  debhelper 9.20151126
ii  libfile-stripnondeterminism-perl  0.014-1
ii  libtimedate-perl  2.3000-2
ii  perl  5.20.2-6

dh-strip-nondeterminism recommends no packages.

dh-strip-nondeterminism suggests no packages.

-- no debconf information

Bug#807668: terminator: Please update terminator to 0.98

[Martin Dosch]

Package: terminator
Version: 0.97-4
Severity: normal

Dear Maintainer,

please update terminator to 0.98 as the changelog [1] is quite impressive and
in my opinion this version should be included in stretch.

Best regards,
Martin

[1] http://bazaar.launchpad.net/~gnome-
terminator/terminator/trunk/view/1638/ChangeLog



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

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

Versions of packages terminator depends on:
ii  gconf2  3.2.6-3
ii  python-dbus 1.2.0-2+b4
ii  python-gobject  3.18.2-2
ii  python-gtk2 2.24.0-4
ii  python-vte  1:0.28.2-5
pn  python:any  

Versions of packages terminator recommends:
ii  python-gnome2 2.28.1+dfsg-1.1
ii  python-keybinder  0.3.1-1
ii  python-notify 0.1.1-4
ii  xdg-utils 1.1.1-1

terminator suggests no packages.

-- debconf-show failed

Bug#807675: dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing

[Chris Lamb]

Source: dcmtkpp
Version: 0.3.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

dcmtkpp fails to build from source in unstable/amd64:

  [..]

  Generating member index...
  Generating file index...
  Generating file member index...
  Generating example index...
  finalizing index lists...
  writing tag file...
  lookup cache used 5124/65536 hits=34949 misses=5178
  finished...
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211163341.wUBAYFVFa6/dcmtkpp-0.3.1'
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151211163341.wUBAYFVFa6/dcmtkpp-0.3.1'
  cd build && ../tests/run.sh
  W: no data dictionary loaded, check environment variable: DCMDICTPATH
  F: cannot initialize network: 0006:031c TCP Initialization Error: Address 
already in use
  W: no data dictionary loaded, check environment variable: DCMDICTPATH
  E: DcmFileFormat: Cannot determine Version of MetaHeader
  W: no data dictionary loaded, check environment variable: DCMDICTPATH
  E: Store Failed, file: dcmtkpp.4mR/data.dcm:
  E: 0006:0213 Data dictionary missing
  E: Store SCU Failed: 0006:0213 Data dictionary missing
  debian/rules:18: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211163341.wUBAYFVFa6/dcmtkpp-0.3.1'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


dcmtkpp.0.3.1-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807407: icedove: stable 38.4 seems to forget SMTP password, can't send email

[W. Martin Borgert]

Quoting Carsten Schoenert :

Security:   STARTTLS
Authentication: password, normal


Yes, with "Normal password" everything works fine, thanks!

Which means for me and my colleagues the problem is solved,
but I'm not sure whether every user can savely change this?
It still looks like a regression in Icedove to me, but I
leave this to the package maintainers now, OK?

Bug#807627: RFS: taskd/1.1.0+dfsg-1 [ITP]

[Tobias Frost]

Control: owner -1 !

Am Freitag, den 11.12.2015, 02:51 +0100 schrieb Sebastien Badia:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "taskd"
> 
> * Package name: taskd
>   Version : 1.1.0+dfsg-1
>   Upstream Author : Paul Beckingham 
> * URL : http://taskwarrior.org
> * License : MIT
>   Section : utils
> 
> It builds those binary packages:
> 
>   taskd - Synchronisation server for taskwarrior
> 
> To access further information about this package, please visit the
> following URL:
> 
>  http://mentors.debian.net/package/taskd
> 
> Alternatively, one can download the package with dget using this
> command:
> 
>   dget -x http://mentors.debian.net/debian/pool/main/t/taskd/taskd_1.
> 1.0+dfsg-1.dsc
> 
> Note: This is the first upload of taskd package (ITP).
> 
> Thanks in advance, cheers,
> 
> Seb

Bug#807626: RFS: taskwarrior/2.5.0+dfsg-1

[Tobias Frost]

Control: owner -1 !

Am Freitag, den 11.12.2015, 02:50 +0100 schrieb Sebastien Badia:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "taskwarrior"
> 
> * Package name: taskwarrior
>   Version : 2.5.0+dfsg-1
>   Upstream Author : Paul Beckingham 
> * URL : http://taskwarrior.org
> * License : MIT
>   Section : utils
> 
> It builds those binary packages:
> 
>   task - feature-rich console based todo list manager
> 
> To access further information about this package, please visit the
> following URL:
> 
>  http://mentors.debian.net/package/task
> 
> Alternatively, one can download the package with dget using this
> command:
> 
>   dget -x http://mentors.debian.net/debian/pool/main/t/task/task_2.5.
> 0+dfsg-1.dsc
> 
> Note: This upload introduce the new upstream version 2.5.0.
> 
> Thanks in advance, cheers,
> 
> Seb

Bug#807694: libpng: CVE-2015-8540: read underflow in libpng

[Salvatore Bonaccorso]

Source: libpng
Version: 1.2.44-1
Severity: important
Tags: security upstream patch fixed-upstream
Forwarded: http://sourceforge.net/p/libpng/bugs/244/

Hi,

the following vulnerability was published for libpng.

CVE-2015-8540[0]:
underflow read in png_check_keyword in pngwutil.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8540
[1] http://sourceforge.net/p/libpng/bugs/244/
[2] 
http://sourceforge.net/p/libpng/code/ci/d9006f683c641793252d92254a75ae9b815b42ed/

Regards,
Salvatore

Bug#791463: closing RFS: udfclient/0.8-1 [ITP] -- userland implementation of the UDF filesystem

[Pali Rohár]

Now I uploaded my last version of udfclient to mentors again.

But I did not used bmake for two reasons:

1) I have older Debian and Ubuntu systems which do not support bmake, so 
cannot test or use that package

2) It needs to patch original tarball, my debian/rules file is also 
short and does not need to patch software just for compilation

-- 
Pali Rohár
pali.ro...@gmail.com


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

Bug#807675: More failures apparently unrelated to "SCU Failed: 0006:0213 Data dictionary missing"

[Gert Wollny]

After fixing dcmtk (uploading right now) there are still failures: 

On one hand, during the build I get: 

cd build && ../tests/run.sh
F: cannot initialize network: 0006:031c TCP Initialization Error:
Address already in use
E: Store Failed, file: dcmtkpp.iZA/data.dcm:
E: 0006:0317 Peer aborted Association (or never connected)
debian/rules:18: recipe for target 'override_dh_auto_test' failed


On the other hand, when I just run "make test" in the build directory I
get various failures: 

The following tests FAILED:
134 - StoreSCU_Store (Failed)
174 - FindSCU_Find (Failed)
175 - FindSCU_FindCallback (Failed)
216 - Association_Associate (Failed)
288 - GetSCU_Get (Failed)
289 - GetSCU_GetCallback (Failed)
293 - MoveSCU_Move (Failed)
294 - MoveSCU_MoveCallback (Failed)
297 - SCU_Echo (Failed)
Errors while running CTest

The all point to the same problem: 
  
dcmtkpp/tests/code/../PeerFixtureBase.h(74): fatal error in "Store":
DCMTKPP_OWN_AET is not defined


Best 
Gert 

Bug#807683: python-django: missing project_template files

[Marco Pattaro]

Package: python-django
Version: 1.9-1
Severity: important
Tags: newcomer

Dear Maintainer,

The package version of Django 1.9 is missing files from
django/conf/project_template, making the commands `startproject` and `startapp`
besically useless.

Thanks
Marco




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

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

Versions of packages python-django depends on:
ii  python-django-common  1.9-1
pn  python:any

Versions of packages python-django recommends:
ii  libjs-jquery 1.11.3+dfsg-4
pn  python-sqlparse  
ii  python-tz2012c+dfsg-0.1

Versions of packages python-django suggests:
pn  bpython   
ii  geoip-database-extra  2015-1
ii  gettext   0.19.6-1
ii  ipython   2.3.0-2
pn  libgdal1  
pn  python-bcrypt 
ii  python-django-doc 1.9-1
pn  python-flup   
pn  python-memcache   
ii  python-mysqldb1.3.7-1
ii  python-pil3.0.0-1
ii  python-psycopg2   2.6.1-1+b1
ii  python-sqlite 1.0.1-12
ii  python-yaml   3.11-3

-- no debconf information

Bug#807684: kdenlive: rendering with rescaling video changes fps

[Vaclav Ovsik]

Package: kdenlive
Version: 15.08.3-1
Severity: normal

Dear Maintainer,
there is a problem with rendering final video file when user checks
to rescale video resolution. The original fps is not preserved.
I had clips with 29.97fps, the same was the project setting, but
rendered & rescaled video was 25fps, but the same total number of
frames. Additional frames at the end was black.

As a workaround one can render with the original resolution and rescale
using ffmpeg command line of course :).

To reproduce the problem, please start Kdenlive, setup video profile
with 29.97 fps. Create blank title clip - simply click OK. Place it on
timeline. Render mp4 video file and second time with rescaling:

  zito@bobek:~/kdenlive$ tcprobe -i untitled.mp4 
  [probe_mov.c] audio codec=mp4a
  [probe_mov.c] video codec=avc1
  [tcprobe] Apple QuickTime movie file
  [tcprobe] summary for untitled.mp4, (*) = not default, 0 = not detected
  import frame size: -g 1920x1080 [720x576] (*)
   aspect ratio: 16:9 (*)
 frame rate: -f 29.970 [25.000] frc=4 (*)
audio track: -a 0 [0] -e 48000,16,2 [48000,16,2] -n 0x1 [0x2000] (*)
 length: 150 frames, frame_time=33 msec, duration=0:00:05.005
  
  zito@bobek:~/kdenlive$ tcprobe -i untitled2.mp4 
  [probe_mov.c] audio codec=mp4a
  [probe_mov.c] video codec=avc1
  [tcprobe] Apple QuickTime movie file
  [tcprobe] summary for untitled2.mp4, (*) = not default, 0 = not detected
  import frame size: -g 512x288 [720x576] (*)
   aspect ratio: 16:9 (*)
 frame rate: -f 25.000 [25.000] frc=3 
audio track: -a 0 [0] -e 48000,16,2 [48000,16,2] -n 0x1 [0x2000] (*)
 length: 150 frames, frame_time=40 msec, duration=0:00:06.000

Thanks
-- 
Zito


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

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

Versions of packages kdenlive depends on:
ii  ffmpeg7:2.8.3-1
ii  kded5 5.16.0-1
ii  kdenlive-data 15.08.3-1
ii  kinit 5.16.0-1
ii  kio   5.16.0-1
ii  libc6 2.21-4
ii  libgcc1   1:5.3.1-3
ii  libgl1-mesa-glx [libgl1]  11.0.7-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libkf5archive55.16.0-1
ii  libkf5attica5 5.16.0-1
ii  libkf5auth5   5.16.0-1
ii  libkf5bookmarks5  5.16.0-1
ii  libkf5codecs5 5.16.0-1
ii  libkf5completion5 5.16.0-1
ii  libkf5configcore5 5.16.0-1
ii  libkf5configgui5  5.16.0-1
ii  libkf5configwidgets5  5.16.0-1
ii  libkf5coreaddons5 5.16.0-1
ii  libkf5dbusaddons5 5.16.0-1
ii  libkf5guiaddons5  5.16.0-1
ii  libkf5i18n5   5.16.0-1
ii  libkf5iconthemes5 5.16.0-1
ii  libkf5itemviews5  5.16.0-1
ii  libkf5jobwidgets5 5.16.0-1
ii  libkf5kiocore55.16.0-1
ii  libkf5kiofilewidgets5 5.16.0-1
ii  libkf5kiontlm55.16.0-1
ii  libkf5kiowidgets5 5.16.0-1
ii  libkf5newstuff5   5.16.0-1
ii  libkf5notifications5  5.16.0-1
ii  libkf5notifyconfig5   5.16.0-1
ii  libkf5plotting5   5.16.0-1
ii  libkf5service-bin 5.16.0-1
ii  libkf5service55.16.0-1
ii  libkf5solid5  5.16.0-1
ii  libkf5sonnetui5   5.16.0-1
ii  libkf5textwidgets55.16.0-1
ii  libkf5widgetsaddons5  5.16.0-1
ii  libkf5xmlgui5 5.16.0-1
ii  libmlt++3 0.9.8-3
ii  libmlt6   0.9.8-3
ii  libqt5concurrent5 5.5.1+dfsg-8
ii  libqt5core5a  5.5.1+dfsg-8
ii  libqt5dbus5   5.5.1+dfsg-8
ii  libqt5gui55.5.1+dfsg-8
ii  libqt5network55.5.1+dfsg-8
ii  libqt5qml55.5.1-3
ii  libqt5quick5  5.5.1-3
ii  libqt5script5 5.5.1+dfsg-2
ii  libqt5svg55.5.1-2
ii  libqt5widgets55.5.1+dfsg-8
ii  libqt5xml55.5.1+dfsg-8
ii  libstdc++65.3.1-3
ii  libv4l-0  1.8.0-1
ii  melt  0.9.8-3
ii  qml-module-qtquick2   5.5.1-3

Versions of packages kdenlive recommends:
ii  dvdauthor0.7.0-1.3
ii  dvgrab   3.5-2+b3
ii  frei0r-plugins   1.4-3+b1
ii  genisoimage  9:1.1.11-3
ii  recordmydesktop  0.3.8.1+svn602-1+b1
ii  swh-plugins  0.4.15+1-8

Versions of packages kdenlive suggests:
ii  khelpcenter  4:5.4.3-1

-- no debconf information

Bug#807502: gcc-avr: Missing support for atxmega

[Hakan Ardo]

Please do. It might be that we need to update avr-libc too? That work is in
progress, but was delayed. Should be ready any day now...

On Fri, Dec 11, 2015 at 3:57 PM, Lisandro Damián Nicanor Pérez Meyer <
perezme...@gmail.com> wrote:

> Then I would prefer to raise the severity to serious, are you OK with
> that?
>
> --
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
> El dic 11, 2015 11:48 AM, "Thorsten Schulz" <
> thorsten.sch...@uni-rostock.de> escribió:
>
>> Hej,
>>
>> this may be a broader issue. I must confirm this bug for the x32e5 as
>> well.
>> Stepping gcc-avr back to testing helps for the meanwhile.
>>
>> The complained files do not exist in earlier versions. So either this may
>> be a problem of a new feature or some odd configuration. GOOD LUCK, I have
>> no idea :/
>>
>> --
>> To unsubscribe, send mail to 807502-unsubscr...@bugs.debian.org.
>>
>


-- 
Håkan Ardö

Bug#807680: systemd: xdm fails to restart

[Michael Biebl]

Am 11.12.2015 um 16:29 schrieb Salvo Tomaselli:
>> I'm not sure why xdm should behave differently under systemd. After all,
>> it only ships a SysV init script atm.
> 
> if "service xdm restart" is run directly by systemd rather than within
> the session, it would not
> kill itself and would keep working.

I'm pretty sure systemd delivers the start and stop request successfully
to the sysv init script.
I suspect that it's the sysv init script which doesn't properly stop or
start the xdm process.

What's the status of xdm.service before and after the systemctl restart xdm?

-- 
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#807690: libassimp-dev: CMake files gives incorrect info

[Leopold Palomo-Avellaneda]

Package: libassimp-dev
Version: 3.2~dfsg-2
Severity: normal

Dear Maintainer,

I would like to tell you one bug I have found. I'm a bit shamed because 
it has been my fault, because I think that I introduce it with the last bug 
(#806317)

As the cmake files are installed, the some software that uses Assimp try to
use then searching the assimp-config file (CMake based). The problem is that in
that file there are these two lines:


set( ASSIMP_LIBRARIES assimp${ASSIMP_LIBRARY_SUFFIX})
set( ASSIMP_LIBRARIES ${ASSIMP_LIBRARIES})


upstream by default has:

set( ASSIMP_LIBRARIES assimp${ASSIMP_LIBRARY_SUFFIX})
set( ASSIMP_LIBRARIES ${ASSIMP_LIBRARIES}@CMAKE_DEBUG_POSTFIX@)

so, the cmake files return to the assimp users (developers) that to link
with assimp thery must link against -lassimpd, and that library doesn't exist 
in 
debian.

So, one simple way to solve it is to add in the rules file:

DEB_CMAKE_EXTRA_FLAGS=-DASSIMP_BUILD_ARCHITECTURE=$(DEB_HOST_ARCH) \
-DASSIMP_LIB_INSTALL_DIR=lib/$(DEB_HOST_MULTIARCH) \
-DCMAKE_SHARED_LINKER_FLAGS="$(LDFLAGS)" \
-DCMAKE_EXE_LINKER_FLAGS="$(LDFLAGS)" \   
-DCMAKE_INSTALL_PREFIX=/usr \
-DBUILD_ASSIMP_SAMPLES=OFF \ 
-DASSIMP_BUILD_TESTS=OFF \   
-DCMAKE_DEBUG_POSTFIX='' \   
-DASSIMP_ENABLE_BOOST_WORKAROUND=OFF

the   -DCMAKE_DEBUG_POSTFIX='' 

Sorry for the noise produced. I hope that not too much package had the FTBFS 
label.

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libassimp-dev depends on:
ii  libassimp3  3.2~dfsg-1~drp8+3

libassimp-dev recommends no packages.

libassimp-dev suggests no packages.

-- no debconf information

Bug#807696: ARM: dts: Kirkwood: Fix QNAP TS219 power-off

[Martin Michlmayr]

Package: linux
Version: 4.3-1~exp2
Tags: patch

Please add this patch to Debian's 4.3 kernel:

ARM: dts: Kirkwood: Fix QNAP TS219 power-off
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5442f0eadf2885453d5b2ed8c8592f32a3744f8e

It was accepted for v4.4-rc3.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#807695: lintian: false positive for command-with-path-in-maintainer-script

[Thorsten Glaser]

Package: lintian
Version: 2.5.38.1
Severity: normal

I got a false positive for FusionForge in sid:

W: gforge-db-postgresql: command-with-path-in-maintainer-script postinst:8 
/usr/bin/pg_lsclusters
[…]
N:See particularly the function pathfind() in devref.

The line in question:

if [ -x /usr/bin/pg_lsclusters ]; then

OK, I looked into devref, and it explicitly says:

    If you need to check for the existence of a command, you should
use something like

    if [ -x /usr/sbin/install-docs ]; then ...

But, huh? Turns out lintian false-positives that as well:

$ perl -e '$cmd = "if [ -x /usr/bin/pg_lsclusters ]; then"; if($cmd =~ 
m{\[\s+(?:!\s+)? -x \s+(/(?:usr/)?s?bin/[\w.+-]+)\s+ \]}xsm){print 
"true\n";}else{print "false\n";}'
true
$ perl -e '$cmd = "if [ -x /usr/sbin/install-docs ]; then"; if($cmd =~ 
m{\[\s+(?:!\s+)? -x \s+(/(?:usr/)?s?bin/[\w.+-]+)\s+ \]}xsm){print 
"true\n";}else{print "false\n";}'
true

This doesn’t happen in wheezy but in sid.

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

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

Versions of packages lintian depends on:
ii  binutils   2.25.90.20151209-1
ii  bzip2  1.0.6-8
ii  diffstat   1.60-1
ii  file   1:5.25-2
ii  gettext0.19.6-1
ii  hardening-includes 2.7
ii  intltool-debian0.35.0+20060710.4
ii  libapt-pkg-perl0.1.29+b4
ii  libarchive-zip-perl1.55-1
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.38-1
ii  libdigest-sha-perl 5.95-2
ii  libdpkg-perl   1.18.3
ii  libemail-valid-perl1.198-1
ii  libfile-basedir-perl   0.07-1
ii  libipc-run-perl0.94-1
ii  liblist-moreutils-perl 0.413-1
ii  libparse-debianchangelog-perl  1.2.0-8
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  liburi-perl1.69-1
ii  man-db 2.7.5-1
ii  patchutils 0.3.4-1
ii  perl [libdigest-sha-perl]  5.20.2-6
ii  t1utils1.38-4
ii  xz-utils   5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg1.18.3
pn  libperlio-gzip-perl 
ii  perl5.20.2-6
ii  perl-modules [libautodie-perl]  5.20.2-6

Versions of packages lintian suggests:
ii  binutils-multiarch 2.25.90.20151209-1
ii  dpkg-dev   1.18.3
ii  libhtml-parser-perl3.71-2
pn  libtext-template-perl  
ii  libyaml-perl   1.15-1

-- no debconf information

Bug#807666: nmu: mpich_3.1-6

[Emilio Pozuelo Monfort]

Control: reassign -1 src:mpich
Control: severity -1 serious
Control: retitle -1 mpich: overly restrictive GCC check

On 11/12/15 14:50, Samuel Thibault wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> Hello,
> 
> Compiling c++ programs against mpich currently fails in sid:
> 
> In file included from /usr/include/mpich/mpi.h:2175:0,
>  from test.c:1:
> /usr/include/mpich/mpicxx.h:22:4: error: #error 'Please use the same version 
> of GCC and g++ for compiling MPICH and user MPI programs'
>  #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
> user MPI programs'
> 
> Apparently mpich got built with 5.2, and sid currently has 5.3, thus the
> failure.  Rebuilding mpich with current gcc 5.3 should be fixing it.
> 
> Samuel
> 
> nmu mpich_3.1-6 . ANY . unstable . -m "Rebuild against g++ 5.3"

This sounds like a too restrictive check, especially now that a 5.2 -> 5.3 GCC
bump is similar to a 4.9.2 -> 4.9.3 one (i.e. a "micro" or bugfix update). I'm
reassigning so this gets fixed in mpich.

Cheers,
Emilio

Bug#807666: nmu: mpich_3.1-6

[Matthias Klose]

On 11.12.2015 14:50, Samuel Thibault wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

Compiling c++ programs against mpich currently fails in sid:

In file included from /usr/include/mpich/mpi.h:2175:0,
  from test.c:1:
/usr/include/mpich/mpicxx.h:22:4: error: #error 'Please use the same version of 
GCC and g++ for compiling MPICH and user MPI programs'
  #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'

Apparently mpich got built with 5.2, and sid currently has 5.3, thus the
failure.  Rebuilding mpich with current gcc 5.3 should be fixing it.

Samuel

nmu mpich_3.1-6 . ANY . unstable . -m "Rebuild against g++ 5.3"


better fix mpich to not give this error on minor releases. This was correct 
before GCC 5, not for GCC 5 and newer versions.

Bug#807695: lintian: false positive for command-with-path-in-maintainer-script

[Axel Beckert]

Hi,

Thorsten Glaser wrote:
> I got a false positive for FusionForge in sid:
> 
> W: gforge-db-postgresql: command-with-path-in-maintainer-script postinst:8 
> /usr/bin/pg_lsclusters
> […]
> N:See particularly the function pathfind() in devref.
> 
> The line in question:
> 
> if [ -x /usr/bin/pg_lsclusters ]; then
> 
> OK, I looked into devref, and it explicitly says:
> 
>     If you need to check for the existence of a command, you should
> use something like
> 
>     if [ -x /usr/sbin/install-docs ]; then ...

And if you read just one paragraph further:

  If you don't wish to hard-code the path of a command in your
  maintainer script, the following POSIX-compliant shell function may help:

  pathfind() {
OLDIFS="$IFS"
IFS=:
for p in $PATH; do
if [ -x "$p/$*" ]; then
IFS="$OLDIFS"
return 0
fi
done
IFS="$OLDIFS"
return 1
  }

I guess _that_ is the part, Lintian refers, too.

But besides that, I'm also annoyed by that warning and tend to ignore
it. I don't think, forbidding "if [ -x /usr/*bin/* ];" adds any value.
Especially not if you're supposed to add like a dozen lines of sh code
instead which is surely more error-prone than that single line.

(In case someone disagrees: Have a look at one of the reasons why
systemd is said to be s much better since it has no more init
scripts... :-P)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#807687: wiki.debian.org: can't see wiki.debian.org if using tor and tor exit

[Alex Vong]

Hi Shirish,

I am a Debian user. I tried using Tor for awhile (not using it now
though), and sometimes this happened. For example, websites often
thought I am a bot, and asked me to answer some questions to show I am
a human. My solution was to re-establish connection to change the exit
relay. Does this work for you?

Cheers,
Alex

On 11/12/2015, shirish शिरीष  wrote:
> Package: wiki.debian.org
> Severity: important
>
> Dear Maintainer,
>
> Just saw #754920, similar here the only difference is I'm using tor
> and tor exit 198.96.155.3 , probably somebody tried to spam the site
> using this exit or maybe it's the tor thing, anyways sharing it.
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (1, 'experimental'), (1, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
>
> --
>   Regards,
>   Shirish Agarwal  शिरीष अग्रवाल
>   My quotes in this email licensed under CC 3.0
> http://creativecommons.org/licenses/by-nc/3.0/
> http://flossexperiences.wordpress.com
> EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
>
>

Bug#801897: TypeError: Request path contains unescaped characters

[Sébastien NOBILI]

Hi,

Same issue here on a Jessie machine with nodejs backported (by myself) from
testing (which shouldn't to be related).

>From this [1] post, it seems to be a proxy issue.

1: 
http://stackoverflow.com/questions/31199457/nodejs-module-install-error-request-path-contains-unescaped-characters

I've got some proxy-related environment variables. Unsetting them fixes the
issue :

$ HTTP_PROXY= HTTPS_PROXY= http_proxy= https_proxy= npm view keybase
[No more error]

Sébastien

Bug#791463: closing RFS: udfclient/0.8-1 [ITP] -- userland implementation of the UDF filesystem

[Andrew Shadura]

On 11 December 2015 at 18:01, Pali Rohár  wrote:
> Now I uploaded my last version of udfclient to mentors again.
>
> But I did not used bmake for two reasons:
>
> 1) I have older Debian and Ubuntu systems which do not support bmake, so
> cannot test or use that package
>
> 2) It needs to patch original tarball, my debian/rules file is also
> short and does not need to patch software just for compilation

Please install the latest bmake and use it (you have to build and test
your package on unstable anyway!), and it's not a big deal to patch
the Makefile after all, you just dropping the patch into the right
place.

-- 
Cheers,
  Andrew

Bug#807679: Please rename the package to python-websocket-client

[Thomas Goirand]

Source: websocket-client
Severity: normal

Hi,

It is my understanding that the Python egg-info name should match the
package name in Debian. The fact that python-websocket was called this
way lead me to wrongly open an ITP for it.

So my suggestion is to transition to python-websocket-client instead of
python-websocket.

Also, please package the latest version.

Cheers,

Thomas Goirand (zigo)

Bug#807581: closed by Piotr Ożarowski <pi...@debian.org> (Re: Bug#807581: ITP: python-websocket-client -- low level APIs for WebSocket)

[Thomas Goirand]

> Thomas, how do you check if given module is already packaged in
> Debian?

I did, in Sid:
apt-cache search python-websocket-client

This gave no result, as the package is python-websocket. It's IMO a
mistake that it's called this way, because the egg-info really shows
websocket-client, not just websocket.

Then I've also tried wnpp.debian.net, which gave no result.

> Why don't you use tools we pointed you to?

I did, though it's hard to find out when a package is badly named (I
have just filed a bug about this). This isn't the first time I'm hit by
this kind of issue, and I have no idea how to fix the problem.

Cheers,

Thomas Goirand (zigo)

Bug#792569: kded5: take whole CPU

[Maximiliano Curia]

Hi,

On 16/07/15 08:02, Eric Valette wrote:
> Package: kded5
> Version: 5.12.0-1
> Severity: important

> I was wonering why the fan on my latop was busy for a while and discovered 
> kded5 was taking 99%CPU for at elast the 20 mins I watched
Thanks for your report. kded is a small daemon that takes care of running the 
background tasks, and as such, the cpu usage might be due to a buggy (or really 
busy) background task.

It would be better if you could add try to pinpoint the background task 
responsible for the high cpu usage. From the system settings "Background 
Services" you can stop the running services and with that search for the 
responsible task.

Happy hacking,

Bug#807672: natlog: FTBFS: [/usr/bin/icmbuild, line 166] Error: idx undefined

[Frank B. Brokken]

Dear Chris Lamb, you wrote:

> natlog fails to build from source in unstable/amd64:

Yes, it's a hard life

But no kidding: thanks for the update. The build-problems are caused by
natlog's build script not yet being updated to the latest icmake version.

I'm working on that right now, and I'll raise natlog in my personal priority
stack ;-)

In the meantime, you could change 'sizeof' into 'listlen', as suggested:

>   [icmake/md, line 15] Warning: `sizeof' is deprecated. Use `listlen'

>   [/usr/bin/icmbuild, line 166] Error: idx undefined
>   [/usr/bin/icmbuild, line 166] Error: Incorrect returntype for function
>   'find()'

and this error is simply fixed by moving the 'int idx' definition in the for
statement to right above the for statement. The following change should be all
that's required:

int idx;// definition moved out of the next for-statement
for (idx = listlen(haystack); idx--; )

But I'll handle this bug ASAP.

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#807685: RM: libcommons-openpgp-java -- ROM; RC buggy; unmaintained upstream; never officially released

[Markus Koschany]

Package: ftp.debian.org
Severity: normal

Hi,

please remove libcommons-openpgp-java from Debian. This issue was
recently discussed on debian-java. There were no objections against
the removal.

Reasons:

 * It is RC buggy. [1]
 * It is unmaintained upstream and was never officially released.
 * It has no reverse dependencies.

Regards,

Markus


[1] https://lists.debian.org/debian-java/2015/12/msg00053.html
[2] https://bugs.debian.org/807391

Bug#807680: systemd: xdm fails to restart

[Michael Biebl]

Control: tags -1 moreinfo

Am 11.12.2015 um 16:00 schrieb Salvo Tomaselli:
> Package: systemd
> Version: 228-2
> Severity: normal
> 
> Dear Maintainer,
> 
> doing 
>> service xdm restart
> 
> inside a graphic session will terminate Xorg but not restart.
> 
> Systemd was supposed to solve this issue...

I'm not sure why xdm should behave differently under systemd. After all,
it only ships a SysV init script atm.
Please elaborate where you think the bug is in systemd.


-- 
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