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

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

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + mrpt-apps
Bug #807662 [mrpt-common] mrpt-common: fails to upgrade from 'jessie' - trying 
to overwrite 
/usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini
Added indication that 807662 affects mrpt-apps

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

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

Processed (with 6 errors): Fixed in sid too

[Debian Bug Tracking System]

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

> unarchive 673038
Bug #673038 {Done: Michael Gilbert } [slapd] slapd: 
slapcat output truncated every now and then
Unarchived Bug 673038
> fixed -1 2.4.39-1
Failed to add fixed on -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_fixed did not pass regex check
.

> archive 673038
Bug #673038 {Done: Michael Gilbert } [slapd] slapd: 
slapcat output truncated every now and then
Bug 673038 cannot be archived
> According to [1] this is fixed since 2.4.36. See also the commit itself [2].
Unknown command or malformed arguments to command.
> [1] 
> http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=cc40af20711e86681b2971cd185ffd9b67e96ea7
Unknown command or malformed arguments to command.
> [2] 
> http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=853b9d1335d27e280751e9cfb8ca6b5356ffec73;hp=1c99711ede25860b24750aab9c529a49c53756ae
Unknown command or malformed arguments to command.
> Regards
Unknown command or malformed arguments to command.
> --
Stopping processing here.

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

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#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#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#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#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#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#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#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#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#807647: marked as done (perl/experimental: trigger cycle on upgrades)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 12:49:41 +
with message-id 
and subject line Bug#807647: fixed in perl 5.22.1~rc4-2
has caused the Debian Bug report #807647,
regarding perl/experimental: trigger cycle on upgrades
to be marked as done.

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

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


-- 
807647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.22.1~rc4-2

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

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

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Dec 2015 13:41:55 +0200
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.22 libperl-dev perl-modules-5.22 
perl
Architecture: source
Version: 5.22.1~rc4-2
Distribution: experimental
Urgency: low
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Description:
 libperl-dev - Perl library: development files
 libperl5.22 - shared Perl library
 perl   - Larry Wall's Practical Extraction and Report Language
 perl-base  - minimal Perl system
 perl-debug - debug-enabled Perl 

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)

[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#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#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)

[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#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#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#807589: marked as done (libechonest: FTBFS on all architectures due to mismatched symbols file(s))

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 15:53:09 +
with message-id 
and subject line Bug#807589: fixed in libechonest 2.3.1-0.3
has caused the Debian Bug report #807589,
regarding libechonest: FTBFS on all architectures due to mismatched symbols 
file(s)
to be marked as done.

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

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


-- 
807589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libechonest
Version: 2.3.1-0.2
Severity: serious

Hello!

libechonest currently fails to build from source on *all* architectures
due to mismatched symbols file(s) after an unsuccessful NMU to fix
these files.

Please use the logs provided by the buildds [1] to fix the symbols for ALL
architectures, even on older architectures like m68k or sh4.

If you need assistance updating the symbol files for these architectures,
please let me know and I will help as I am an active porter for most
Debian Ports architectures.

Cheers,

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
--- End Message ---
--- Begin Message ---
Source: libechonest
Source-Version: 2.3.1-0.3

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

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

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

Debian distribution maintenance software
pp.
Stefan Ahlers  (supplier of updated libechonest 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Dec 2015 09:00:00 +0100
Source: libechonest
Binary: libechonest2.3 libechonest-dev libechonest-dbg libechonest5-2.3 
libechonest5-dev libechonest5-dbg
Architecture: source
Version: 2.3.1-0.3
Distribution: unstable
Urgency: low
Maintainer: Thomas Pierson 
Changed-By: Stefan Ahlers 
Description:
 libechonest-dbg - Qt4 library for The Echo Nest platform - debug files
 libechonest-dev - Qt4 library for The Echo Nest platform - development files
 libechonest2.3 - Qt4 library for communicating with The Echo Nest platform
 libechonest5-2.3 - Qt5 library for communicating with The Echo Nest platform
 libechonest5-dbg - Qt5 library for The Echo Nest platform - debug files
 libechonest5-dev - Qt5 library for The Echo Nest platform - development files
Closes: 807507 807589
Changes:
 libechonest (2.3.1-0.3) unstable; urgency=low
 .
   [ Stefan Ahlers ]
   * Non-maintainer upload, with maintainer permission.
   * Fix symbols again (Closes: #807589).
   * Drop bogus libechonest2.1 (Closes: #807507)
 - fix already inplace in the previous upload.
 .
   [ Gianfranco Costamagna ]
   * Tweak symbols to build on armhf and arm*.
Checksums-Sha1:
 2e8b15b8ddd553eac5dbfc00428640fe031f0234 2292 libechonest_2.3.1-0.3.dsc
 8de9f5fd29150ba5d8b677e26cfd8810650ce0cc 9536 
libechonest_2.3.1-0.3.debian.tar.xz
Checksums-Sha256:
 5cb7987ca12e6f355a0a3d7201d2be32ec4210d225f3e77ad47e6d9629a2b17f 2292 
libechonest_2.3.1-0.3.dsc
 cf31fbe6a53928a84f3f4c78eb454d000de3b6aa8ebc4f09d6b938e840aadb20 9536 
libechonest_2.3.1-0.3.debian.tar.xz
Files:
 d928d38f500a0493ed0a7023f3640604 2292 libs extra libechonest_2.3.1-0.3.dsc
 ed4f25943253f640a612c3780ac2b775 9536 libs extra 
libechonest_2.3.1-0.3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWauqaAAoJEPNPCXROn13ZJYkP/jnSOrAZmo97GOEdy6QZB9JL
qEHtai3DSiwvD8fzhO/7zA/1xWpS1lZ+ctGZpNv/CNcWzSIA5w9iltqBNToZ/mkj
Hp2RPs1CznN77SydeINCA1Y135V57GVbgp/jlGSAdlSnyxTXGGWe6Nid7vAVTm1T
D+D2EEVMEbKTtR3CwLaB2a/Woo2baWKoN96ew2VF3CHU1x9Khrf3TXn2P/OxqOOB
L9a3Tqyd+g5tyrUz6AmsHzT3FpEi/boW+c4KPW+Mh+NplSn6qoQTgQMnNAv/rzbv
Y8nv5UhFRhXneozkz4ZU8tm9IVXFCQP68R/iTxQB3Hl005w1Gy29Os8/xCPYEbgG
+3vrugr5Faksm20Ou8JxEmZympuPkroBh/n+ddrEfrwTBrx5A7s4I1Nqlw/3iv3A
5dpyvibmsFiwGlM1Zk8eGwX8Kyh0q1rW9oXAUZ/b2ytLUcpbJIYqpa+OJFSKHohv
sXE1LH/9LzQ03vd3aH2Y+5ZQKVKtKqsbkoAbyDH6y+U4y9Uix6j0SMJX6QWLVezY
82+VefLDw7ovh9hFUB6xCPmwpg0CeqI60mcxQAs6vieOCsm6wkpu43f3dRj0r9YN

Processed: DCMDICTPATH is not set properly in dcmtk

[Debian Bug Tracking System]

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

> block 807675 by 807691
Bug #807675 [src:dcmtkpp] dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary 
missing
807675 was not blocked by any bugs.
807675 was not blocking any bugs.
Added blocking bug(s) of 807675: 807691
> thanks
Stopping processing here.

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

Processed: Re: Bug#807666: nmu: mpich_3.1-6

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:mpich
Bug #807666 [release.debian.org] nmu: mpich_3.1-6
Bug reassigned from package 'release.debian.org' to 'src:mpich'.
Ignoring request to alter found versions of bug #807666 to the same values 
previously set
Ignoring request to alter fixed versions of bug #807666 to the same values 
previously set
> severity -1 serious
Bug #807666 [src:mpich] nmu: mpich_3.1-6
Severity set to 'serious' from 'normal'
> retitle -1 mpich: overly restrictive GCC check
Bug #807666 [src:mpich] nmu: mpich_3.1-6
Changed Bug title to 'mpich: overly restrictive GCC check' from 'nmu: 
mpich_3.1-6'

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

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

[Lisandro Damián Nicanor Pérez Meyer]

On Friday 11 December 2015 16:15:52 Hakan Ardo wrote:
> Please do. 

Done, thanks!

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

It might be, if so just ping me as soon as it's available in incoming.d.o and 
I'll happily give it a try.

Thanks!

-- 
The volume of a pizza of thickness a and radius z can be described by
the following formula:

pi zz a

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: severity of 791964 is important

[Debian Bug Tracking System]

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

> severity 791964 important
Bug #791964 [gdm3] gdm3: upgrade causes X session to be terminated
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#807507: marked as done (libechonest2.1: Missing libechonest.so.2.1)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 15:53:09 +
with message-id 
and subject line Bug#807507: fixed in libechonest 2.3.1-0.3
has caused the Debian Bug report #807507,
regarding libechonest2.1: Missing libechonest.so.2.1
to be marked as done.

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

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


-- 
807507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libechonest2.1
Version: 2.3.1-0.1
Severity: grave

libechonest2.1 no longer provides libechonest.so.2.1 and breaks all its reverse
dependencies.

$ clementine
clementine: error while loading shared libraries: libechonest.so.2.1: cannot 
open shared object file: No such file or directory

Indeed:

$ dpkg -L libechonest2.1
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libechonest2.1
/usr/share/doc/libechonest2.1/changelog.Debian.gz
/usr/share/doc/libechonest2.1/copyright

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libechonest
Source-Version: 2.3.1-0.3

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

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

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

Debian distribution maintenance software
pp.
Stefan Ahlers  (supplier of updated libechonest 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Dec 2015 09:00:00 +0100
Source: libechonest
Binary: libechonest2.3 libechonest-dev libechonest-dbg libechonest5-2.3 
libechonest5-dev libechonest5-dbg
Architecture: source
Version: 2.3.1-0.3
Distribution: unstable
Urgency: low
Maintainer: Thomas Pierson 
Changed-By: Stefan Ahlers 
Description:
 libechonest-dbg - Qt4 library for The Echo Nest platform - debug files
 libechonest-dev - Qt4 library for The Echo Nest platform - development files
 libechonest2.3 - Qt4 library for communicating with The Echo Nest platform
 libechonest5-2.3 - Qt5 library for communicating with The Echo Nest platform
 libechonest5-dbg - Qt5 library for The Echo Nest platform - debug files
 libechonest5-dev - Qt5 library for The Echo Nest platform - development files
Closes: 807507 807589
Changes:
 libechonest (2.3.1-0.3) unstable; urgency=low
 .
   [ Stefan Ahlers ]
   * Non-maintainer upload, with maintainer permission.
   * Fix symbols again (Closes: #807589).
   * Drop bogus libechonest2.1 (Closes: #807507)
 - fix already inplace in the previous upload.
 .
   [ Gianfranco Costamagna ]
   * Tweak symbols to build on armhf and arm*.
Checksums-Sha1:
 2e8b15b8ddd553eac5dbfc00428640fe031f0234 2292 libechonest_2.3.1-0.3.dsc
 8de9f5fd29150ba5d8b677e26cfd8810650ce0cc 9536 
libechonest_2.3.1-0.3.debian.tar.xz
Checksums-Sha256:
 5cb7987ca12e6f355a0a3d7201d2be32ec4210d225f3e77ad47e6d9629a2b17f 2292 
libechonest_2.3.1-0.3.dsc
 cf31fbe6a53928a84f3f4c78eb454d000de3b6aa8ebc4f09d6b938e840aadb20 9536 
libechonest_2.3.1-0.3.debian.tar.xz
Files:
 d928d38f500a0493ed0a7023f3640604 2292 libs extra libechonest_2.3.1-0.3.dsc
 ed4f25943253f640a612c3780ac2b775 9536 libs extra 
libechonest_2.3.1-0.3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWauqaAAoJEPNPCXROn13ZJYkP/jnSOrAZmo97GOEdy6QZB9JL
qEHtai3DSiwvD8fzhO/7zA/1xWpS1lZ+ctGZpNv/CNcWzSIA5w9iltqBNToZ/mkj
Hp2RPs1CznN77SydeINCA1Y135V57GVbgp/jlGSAdlSnyxTXGGWe6Nid7vAVTm1T
D+D2EEVMEbKTtR3CwLaB2a/Woo2baWKoN96ew2VF3CHU1x9Khrf3TXn2P/OxqOOB
L9a3Tqyd+g5tyrUz6AmsHzT3FpEi/boW+c4KPW+Mh+NplSn6qoQTgQMnNAv/rzbv
Y8nv5UhFRhXneozkz4ZU8tm9IVXFCQP68R/iTxQB3Hl005w1Gy29Os8/xCPYEbgG
+3vrugr5Faksm20Ou8JxEmZympuPkroBh/n+ddrEfrwTBrx5A7s4I1Nqlw/3iv3A
5dpyvibmsFiwGlM1Zk8eGwX8Kyh0q1rW9oXAUZ/b2ytLUcpbJIYqpa+OJFSKHohv
sXE1LH/9LzQ03vd3aH2Y+5ZQKVKtKqsbkoAbyDH6y+U4y9Uix6j0SMJX6QWLVezY
82+VefLDw7ovh9hFUB6xCPmwpg0CeqI60mcxQAs6vieOCsm6wkpu43f3dRj0r9YN
1Q67H6Yed7eFL1KgCrp6jZ2781ZazfhJLS+M4bFi8+783LpgPRdfYa5IRBFE4D2s
Gx9dmqmIshpE50sYQM7J
=AntR
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

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

> severity 807502 serious
Bug #807502 [gcc-avr] gcc-avr: Missing support for atxmega384d3 since last 
upload
Ignoring request to change severity of Bug 807502 to the same value.
> thanks
Stopping processing here.

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

Bug#732723: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready

[Tobias Frost]

Am Montag, den 05.10.2015, 11:28 +0200 schrieb Muammar El Khatib:
> On Sun, Sep 27, 2015 at 8:42 PM, Tobias Frost 
> wrote:
> > > Yes. Go ahead. Today I contacted FTP masters because I think the
> > > debian/copyright file is ok. I will keep you posted about it.
> > > 
> > 
> > Recreated the repository in the meantime.
> 
> 
> So far I haven't gotten a reply from FTP masters. The claimed the
> following:
> 
> > I found lots of files that are not mentioned in your
> > debian/copyright:
> >  doc/doxygen/falagard/fal_main.dox is GFDL
> >  promo/* is CC-BY-SA
> >  cegui/src/ScriptModules/Python/bindings/generate.py is GPL3
> >  cegui/src/ScriptModules/Python/bindings/generators/__init__.py is
> > GPL3
> >  cegui/src/ScriptModules/Python/bindings/output/CEGUIOgreRenderer/*
> > is BOOST
> >  some fonts in datafiles/font/* have licenses as shown in
> > datafiles/fonts/Legal.txt
> 
> But those files were indeed included in the copyright file. See:
> 
> https://web.archive.org/web/20150907175032/https://ftp-master.debian.
> org/new/cegui-mk2_0.8.4-2.html
> 
> Regards,
> 

Hi Muammar,

did you get any response in the meantime?
Should we reupload?


Tobi

Bug#793911: groovy should not release with stretch

[Miguel Landaeta]

Hi Markus,

On Fri, Dec 11, 2015 at 09:23:42PM +0100, Markus Koschany wrote:
> 
> we can always consider to fix red5 with a NMU. We just should raise the
> severity accordingly before we do that.

Sure, that's a valid option. An NMU to DELAYED/7 or something is OK
with me.

> I hope I can lend you a hand with an update of libspring-java after I
> have packaged the latest netbeans release. Perhaps you can write a short
> TODO list and push it to the libspring-java repo, which upstream should
> be packaged, if we have to package new dependencies and where you need
> help.

OK, unfortunately I don't have too much time lately but I think I can
review latest Spring upstream releases to document if/which new
dependencies are needed and push that to the repo.

Cheers,

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#807713: telepathy-idle: Cannot create any connection

[Julian Andres Klode]

Package: telepathy-idle
Severity: grave

It appears that telepathy-idle is unusable right now,
adding a connection in Polari or Empathy fails. Polari
console output shows:

(org.gnome.Polari:3203): Gjs-WARNING **: JS ERROR: TelepathyGLib.Error: 
Protocol 'irc' not found on CM 'idle'
ConnectionDetails<._createAccount/<@resource:///org/gnome/Polari/js/connections.js:331
main@resource:///org/gnome/Polari/js/main.js:17
run@resource:///org/gnome/gjs/modules/package.js:192
start@resource:///org/gnome/gjs/modules/package.js:176
@/usr/bin/polari:5


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

-- 
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#807487: pbuilder update in sid breaks pbuilder on (old)stable

[Jakub Wilk]

* Mattia Rizzolo , 2015-12-09, 19:07:
I *believe* aptitude was using /build/.aptitude/cache/ for this so the 
wildcard was not picking it, instead now it started using 
/build/aptitude/cache, so interferring with the wildcard.


This is bug #807545, which is now fixed...


For now, I'll set XDG_CACHE_HOME=/root only while calling aptitude


...so it should be possible to drop this ugly work-around.

--
Jakub Wilk

Bug#800172: marked as done (forg: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 22:50:22 +
with message-id 
and subject line Bug#800172: fixed in forg 0.5.1-7.2
has caused the Debian Bug report #800172,
regarding forg: Please migrate a supported debhelper compat level
to be marked as done.

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

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


-- 
800172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: forg
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package forg is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: forg
Source-Version: 0.5.1-7.2

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated forg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Dec 2015 22:46:49 +0100
Source: forg
Binary: forg
Architecture: source all
Version: 0.5.1-7.2
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen 
Changed-By: Axel Beckert 
Description:
 forg   - Graphical Gopher Browser
Closes: 453526 800172
Changes:
 forg (0.5.1-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert to debhelper compatibility level 9 (Closes: #800172).
 + Magically fixes lintian warning no-upstream-changelog.
 + Replace "dh_clean -k" with "dh_prop"
 + Replace "dh_installmanpages" with "dh_installman".
 + Add dependency on ${misc:Depends}.
 + Use dh_auto_clean instead of "-$(MAKE) clean". (Fixes lintian warning
   debian-rules-ignores-make-clean-error.)
 + Add recommended debian/rules targets build-indep and build-arch.
   * Build-depend on dh-python. (Fixes dh_python2 warning.)
   * Fix lintian warning capitalization-error-in-description (python vs
 Python) and remove trailing newline from debian/control.
   * Add man-page written by Robert Marder. (Closes: #453526)
Checksums-Sha1:
 04f37d422f9786315bfe1b272be6c1b03381447a 1625 forg_0.5.1-7.2.dsc
 109493d9d90ed6784f0b14bd029fa0eb0ea92612 5830 forg_0.5.1-7.2.diff.gz
 1447c7756c034464be4982f2a4abe0ec2f69e8cc 63090 forg_0.5.1-7.2_all.deb
Checksums-Sha256:
 40a332530ee543b38fae910514e10987c5914df813a3051cf385afc59c4932e1 1625 
forg_0.5.1-7.2.dsc
 331223002a61cd61929bf304fe90c246e083dbf4178ee3c29b58dbe7535ee4a5 5830 
forg_0.5.1-7.2.diff.gz
 7489be7a8700935e0ae062b29c4621ff4d1f4f81b4bb32eddfb8a24740d1ae1d 63090 
forg_0.5.1-7.2_all.deb
Files:
 4a843641153d0938b55e40db26780b6f 1625 net optional forg_0.5.1-7.2.dsc
 ddc9e7cee3b465b0de6f2969184c17d8 5830 net optional forg_0.5.1-7.2.diff.gz
 93f8a1550950529bf2d1b687f98fad1b 63090 net optional forg_0.5.1-7.2_all.deb

-BEGIN 

Bug#807707: ddclient exit hook for dhclient breaks network configuration

[Torsten Landschoff]

Hi Doug,

On 12/11/2015 09:42 PM, Doug Kingston wrote:
> The Problem:  When I looked at the ddclient hook, I noticed it was
> calling exit(0),
> which exited the entire dhclient-script prematurely.  This is very
> bad, since none
> of the other exits was given an opportuntity to run.  Exits must not
> call exit!
> Returning of error status should be through the "exit_status" shell
> variable
> instead - as documented (poorly) in the manual page for
> dhclient-script(8).
Ouch, good catch. I wasn't aware of this and did not see anything wrong
when the dhclient script was added.
> I changed the ddclient exit hook to not call exit, but instead to
> return control
> to the dhclient-script as is the "API" for these hooks.
>
> What was the outcome of this action?
>
> The system now boots properly.  :-)
I am wondering how nobody else reported this.

Thanks for the report, I'll try to update the package soon.

Greetings, Torsten

Bug#804386: marked as done (condor: FTBFS on arm64 ppc64el and s390x: conflicting declaration 'typedef long unsigned int uint64_t')

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 22:35:00 +
with message-id 
and subject line Bug#804386: fixed in condor 8.4.2~dfsg.1-1
has caused the Debian Bug report #804386,
regarding condor: FTBFS on arm64 ppc64el and s390x: conflicting declaration 
'typedef long unsigned int uint64_t'
to be marked as done.

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

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


-- 
804386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: condor
Version: 8.4.0~dfsg.1-1
Severity: serious

Your package failed to build on arm64, s390x and ppc64el:

In file included from /usr/lib/gcc/aarch64-linux-gnu/5/include/stdint.h:9:0,
 from /usr/include/c++/5/cstdint:41,
 from /usr/include/c++/5/bits/char_traits.h:380,
 from /usr/include/c++/5/string:40,
 from /«PKGBUILDDIR»/src/condor_utils/condor_event.h:36,
 from /«PKGBUILDDIR»/src/condor_utils/read_user_log.h:45,
 from 
/«PKGBUILDDIR»/src/condor_userlog/condor_userlog_job_counter.cpp:30:
/usr/include/stdint.h:55:27: error: conflicting declaration 'typedef long 
unsigned int uint64_t'
 typedef unsigned long int uint64_t;
   ^
In file included from 
/«PKGBUILDDIR»/src/condor_userlog/condor_userlog_job_counter.cpp:30:0:
/«PKGBUILDDIR»/src/condor_utils/read_user_log.h:38:31: note: previous 
declaration as 'typedef long long unsigned int uint64_t'
typedef unsigned long long uint64_t;
   ^

Full logs at
https://buildd.debian.org/status/logs.php?pkg=condor=8.4.0~dfsg.1-1

Emilio
--- End Message ---
--- Begin Message ---
Source: condor
Source-Version: 8.4.2~dfsg.1-1

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

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

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

Debian distribution maintenance software
pp.
Michael Hanke  (supplier of updated condor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Dec 2015 20:30:35 +0100
Source: condor
Binary: htcondor htcondor-dev htcondor-doc htcondor-dbg libclassad-dev 
libclassad7 condor condor-doc condor-dev condor-dbg
Architecture: source all amd64
Version: 8.4.2~dfsg.1-1
Distribution: unstable
Urgency: medium
Maintainer: HTCondor Developers 
Changed-By: Michael Hanke 
Description:
 condor - transitional dummy package
 condor-dbg - transitional dummy package
 condor-dev - transitional dummy package
 condor-doc - transitional dummy package
 htcondor   - distributed workload management system
 htcondor-dbg - distributed workload management system - debugging symbols
 htcondor-dev - distributed workload management system - development files
 htcondor-doc - distributed workload management system - documentation
 libclassad-dev - HTCondor classads expression language - development library
 libclassad7 - HTCondor classads expression language - runtime library
Closes: 804386
Changes:
 condor (8.4.2~dfsg.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Simplified configuration to hold or preempt jobs that exceed resource
   claims.
 - Fix FTBFS on non-amd64 64bit platforms (Closes: #804386).
 - Various other bug fixes.
   * Install tmpfiles configuration for systemd to prevent service start
 failure due to missing /var/run/condor.
Checksums-Sha1:
 32425a8c921fb972c4283f6aa7e6b6eff47ca3e2 3048 condor_8.4.2~dfsg.1-1.dsc
 8cfb9bc321ed724b5b395a1b3e402003e230f18f 10126777 
condor_8.4.2~dfsg.1.orig.tar.gz
 b440bf1441457a3e6fbeac1aaf0a481774ecd1ec 71632 
condor_8.4.2~dfsg.1-1.debian.tar.xz
 81639ff3bbd8a524b22fc848f5aa0db2d982d1ce 15552 
condor-dbg_8.4.2~dfsg.1-1_all.deb
 be9b53cccd46455ab904dc3e7f65db6c26ce72d4 15552 
condor-dev_8.4.2~dfsg.1-1_all.deb
 811dcc2b09a347020f4ba23b9560eae820cccef9 15544 
condor-doc_8.4.2~dfsg.1-1_all.deb
 cc1813e8263ba975c10748aa3ed85906901eb053 15542 condor_8.4.2~dfsg.1-1_all.deb
 3220d46fc9758e35c1d76ef84b5f70bf411c37e3 34825264 

Processed: Re: Bug#807713: telepathy-idle: Cannot create any connection

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #807713 [telepathy-idle] telepathy-idle: Cannot create any connection
Severity set to 'normal' from 'grave'

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

Bug#807713: telepathy-idle: Cannot create any connection

[Julian Andres Klode]

Control: severity -1 normal

On Fri, Dec 11, 2015 at 11:12:59PM +0100, Julian Andres Klode wrote:
> Package: telepathy-idle
> Severity: grave
> 
> It appears that telepathy-idle is unusable right now,
> adding a connection in Polari or Empathy fails. Polari
> console output shows:
> 
> (org.gnome.Polari:3203): Gjs-WARNING **: JS ERROR: TelepathyGLib.Error: 
> Protocol 'irc' not found on CM 'idle'
> ConnectionDetails<._createAccount/<@resource:///org/gnome/Polari/js/connections.js:331
> main@resource:///org/gnome/Polari/js/main.js:17
> run@resource:///org/gnome/gjs/modules/package.js:192
> start@resource:///org/gnome/gjs/modules/package.js:176
> @/usr/bin/polari:5
> 

Logging out and in again fixes the issue, so downgrading.

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

Processed: tagging 807673, bug 807673 is forwarded to https://github.com/danwent/Perspectives/issues/166

[Debian Bug Tracking System]

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

> tags 807673 + upstream
Bug #807673 [src:perspectives-extension] perspectives-extension: FTBFS: 
ValueError: empty namespace prefix is not supported in ElementPath
Added tag(s) upstream.
> forwarded 807673 https://github.com/danwent/Perspectives/issues/166
Bug #807673 [src:perspectives-extension] perspectives-extension: FTBFS: 
ValueError: empty namespace prefix is not supported in ElementPath
Set Bug forwarded-to-address to 
'https://github.com/danwent/Perspectives/issues/166'.
> thanks
Stopping processing here.

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

Processed: retitle 807698 to srtp: CVE-2015-6360: Prevent potential DoS attack due to lack of bounds checking on RTP header CSRC count and extension header length ...

[Debian Bug Tracking System]

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

> retitle 807698 srtp: CVE-2015-6360: Prevent potential DoS attack due to lack 
> of bounds checking on RTP header CSRC count and extension header length
Bug #807698 [src:srtp] CVE-2015-6360: Prevent potential DoS attack due to lack 
of bounds checking on RTP header CSRC count and extension header length
Changed Bug title to 'srtp: CVE-2015-6360: Prevent potential DoS attack due to 
lack of bounds checking on RTP header CSRC count and extension header length' 
from 'CVE-2015-6360: Prevent potential DoS attack due to lack of bounds 
checking on RTP header CSRC count and extension header length'
> fixed 807698 1.5.3~dfsg-1
Bug #807698 [src:srtp] srtp: CVE-2015-6360: Prevent potential DoS attack due to 
lack of bounds checking on RTP header CSRC count and extension header length
Marked as fixed in versions srtp/1.5.3~dfsg-1.
> tags 807698 + upstream fixed-upstream
Bug #807698 [src:srtp] srtp: CVE-2015-6360: Prevent potential DoS attack due to 
lack of bounds checking on RTP header CSRC count and extension header length
Added tag(s) fixed-upstream and upstream.
> found 807698 1.4.4~dfsg-6
Bug #807698 [src:srtp] srtp: CVE-2015-6360: Prevent potential DoS attack due to 
lack of bounds checking on RTP header CSRC count and extension header length
Marked as found in versions srtp/1.4.4~dfsg-6.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 673038 2.4.39-1
Bug #673038 {Done: Michael Gilbert } [slapd] slapd: 
slapcat output truncated every now and then
Ignoring request to alter fixed versions of bug #673038 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#793911: groovy should not release with stretch

[Emmanuel Bourg]

Le 11/12/2015 21:16, Miguel Landaeta a écrit :

> To package libspring-java new upstream releases is a task that would
> be very appreciated although is not easy but with the recent progress
> in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is
> something more feasible nowadays.

I should have mentioned that I'm working on upgrading libspring-java to
the version 4.0.9, I'm almost done. I confirm that gradle-debian-helper
renders the task much easier!

Emmanuel

Processed: fixed 673038 in 2.4.39-1

[Debian Bug Tracking System]

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

> fixed 673038 2.4.39-1
Bug #673038 {Done: Michael Gilbert } [slapd] slapd: 
slapcat output truncated every now and then
Marked as fixed in versions openldap/2.4.39-1.
> thanks
Stopping processing here.

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

Bug#793911: groovy should not release with stretch

[Emmanuel Bourg]

Le 11/12/2015 22:49, Miguel Landaeta a écrit :

> OK, unfortunately I don't have too much time lately but I think I can
> review latest Spring upstream releases to document if/which new
> dependencies are needed and push that to the repo.

I've packaged most the new dependencies required by Spring 4.0.x except:
- com.jayway.jsonpath:json-path:0.9.1
- org.apache.taglibs:taglibs-standard-jstlel:1.2.1

I haven't checked the new dependencies for Spring 4.1 yet.

Emmanuel Bourg

Bug#793911: groovy should not release with stretch

[Markus Koschany]

Am 11.12.2015 um 22:49 schrieb Miguel Landaeta:
> Hi Markus,
> 
> On Fri, Dec 11, 2015 at 09:23:42PM +0100, Markus Koschany wrote:
>>
>> we can always consider to fix red5 with a NMU. We just should raise the
>> severity accordingly before we do that.
> 
> Sure, that's a valid option. An NMU to DELAYED/7 or something is OK
> with me.

I suggest to raise the severity of red5 to serious as soon as we have
fixed libspring-java and it remains the only package left. Then we
should give the maintainer at least ten days to fix the issue (according
to the NMU guide lines) and after that it is fire at will.

>> I hope I can lend you a hand with an update of libspring-java after I
>> have packaged the latest netbeans release. Perhaps you can write a short
>> TODO list and push it to the libspring-java repo, which upstream should
>> be packaged, if we have to package new dependencies and where you need
>> help.
> 
> OK, unfortunately I don't have too much time lately but I think I can
> review latest Spring upstream releases to document if/which new
> dependencies are needed and push that to the repo.

No problem. I just read Emmanuel's comment. If you need some help with
the packaging, just ping me. Like I said I intend to work on Netbeans,
maven-repo-helper (#805228) and Eclipse in the near future but there is
hopefully always some time to package a new dependency. :E

Markus



signature.asc
Description: OpenPGP digital signature

Bug#807730: incorrect bsd/unistd.h header

[Vincent Bernat]

Package: libbsd-dev
Version: 0.8.0-2
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

After a recent update of libbsd, programs using it now fail at compile
time with:

/usr/include/bsd/unistd.h: In function 'setproctitle':
/usr/include/bsd/unistd.h:64:2: error: expected declaration specifiers before 
'__printflike'
  __printflike(1, 2);
  ^

It seems there is a missing backslash at the end of the previous line.

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

Kernel: Linux 4.3.0-trunk-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)

Versions of packages libbsd-dev depends on:
ii  libbsd0  0.8.0-2

libbsd-dev recommends no packages.

libbsd-dev suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIbBAEBCAAGBQJWa9LxAAoJEJWkL+g1NSX5gtAP9R8iiCZnqA7dxdtrv+54K/zm
RqwW/nneJA/OgZOKkHR64wlcoJlNHOCRTIQnAm/uVpG/vcHdFkmwBf5ksZl7jkjE
yOp5vqGo1Av3EKAfVr7LQwFNoH7ubCWXaFfHS5aR6Mgt7QIojGmxuMKXULzyhi9/
nThm3De3F/8fAuNSvgO0YvEm7HvzCXsWBUU2pn+0Ahw40cI5pdACnY6YgQsoM/wB
NDhkdPLfURtyQk0DIxspFImJ9MGSAvPZdy3wpsW7A4SvgjM1FHORQRWmebE2JczN
JB9UeYIbN/WNJEK4c++YChpFFuWRWpXJUU2x5a/anD+huAEgHzL3alGwaWm4eYOr
h1PVWZ5tGlIkTxtzYtOM212ex/VFawvdcnILjhO49X2/SfFYFVoGT4eOCtlJSTt2
15dMRj4FwZcf8sl23tUmVnt6b5Ye1ryWYjfgfeGQWfvW98NnPn3wqJXJMBsWul56
VFHLzuXMuscejznXXzg1l4MUvVK1UbdT5NRi0W64S4E55FjeRD68XYREfTkVIm8S
f20SY0ZUbKeojnAXMSysqxsSRBTQx0apTdjP4bhgbl+qYIGNLCuRrRZbcdViNxEQ
1/e450Pd4hvvAgdkvpBfV/K3309Ck0/hs5a+oOByEPPrL4MOYIsdYxlUJUqazbG2
/YHvQJQMzdKv7awlP6c=
=4rdN
-END PGP SIGNATURE-

Bug#807629: marked as done (Incomplete dependencies: clementine fails to start)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 03:29:41 +0100
with message-id <20151212022940.ga3...@angband.pl>
and subject line fixed in binNMU
has caused the Debian Bug report #807629,
regarding Incomplete dependencies: clementine fails to start
to be marked as done.

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

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


-- 
807629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clementine
Version: 1.2.3+git1354-gdaddbde+dfsg-1
Severity: grave

Hi,

I must have removed some package because clementine now fails to start:

steve@riemann{Downloads}clementine
clementine: error while loading shared libraries: libechonest.so.2.1: cannot 
open shared object file: No such file or directory


I reinstalled clementine, to no avail.  There must be some dependency missing 
somewhere in the chain.

-Steve




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

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

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.6.1-1
ii  gstreamer1.0-plugins-good   1.6.1-1
ii  gstreamer1.0-plugins-ugly   1.6.1-1+b1
ii  libc6   2.21-3
ii  libcdio13   0.83-4.2+b1
ii  libchromaprint0 1.2-1+b1
ii  libcrypto++9v5  5.6.1-9
ii  libechonest2.1  2.3.1-0.1
ii  libfftw3-double33.3.4-2
ii  libgcc1 1:5.3.1-3
ii  libgdk-pixbuf2.0-0  2.32.2-1
ii  libglib2.0-02.46.2-1
ii  libgpod40.8.3-1.1+b3
ii  libgstreamer-plugins-base1.0-0  1.6.1-1
ii  libgstreamer1.0-0   1.6.1-1
ii  libimobiledevice4   1.1.6+dfsg-3.1+b1
ii  liblastfm1  1.0.9-1
ii  libmtp9 1.1.10-2
ii  libprojectm2v5  2.1.0+dfsg-3+b1
ii  libprotobuf9v5  2.6.1-1.3
ii  libpulse0   7.1-2
ii  libqjson0   0.8.1-3
ii  libqt4-dbus 4:4.8.7+dfsg-5
ii  libqt4-network  4:4.8.7+dfsg-5
ii  libqt4-opengl   4:4.8.7+dfsg-5
ii  libqt4-sql  4:4.8.7+dfsg-5
ii  libqt4-sql-sqlite   4:4.8.7+dfsg-5
ii  libqt4-xml  4:4.8.7+dfsg-5
ii  libqtcore4  4:4.8.7+dfsg-5
ii  libqtgui4   4:4.8.7+dfsg-5
ii  libqxt-gui0 0.6.2-2
ii  libsqlite3-03.9.2-1
ii  libstdc++6  5.3.1-3
ii  libtag1v5   1.9.1-2.4
ii  libx11-62:1.6.3-1
ii  projectm-data   2.1.0+dfsg-3
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages clementine recommends:
ii  gstreamer1.0-pulseaudio  1.6.1-1

clementine suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Meow!
This has been fixed by rebuilding against libechonest2.3.

-- 
A tit a day keeps the vet away.--- End Message ---

Bug#805746: aghermann: Fails to build with GSL 2

[andrei zavada]

Hey Yaroslav & Bas,

Sorry for getting a bit late with an apparently simple fix. Here's
version 1.0.7, which builds with gsl-2.0:
http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_1.0.7-1.dsc.

Cheers,
Andrei

On Sat, 21 Nov 2015 23:52:21 +0100
Bas Couwenberg  wrote:

> Source: aghermann
> Version: 1.0.6-1
> Severity: important
> Tags: upstream
> 
> Dear Maintainer,
> 
> Your package fails to build with GSL 2:
> 
>  model/borbely.cc: In function 'agh::beersma::SClassicFit
> agh::beersma::classic_fit(agh::CRecording&, const
> agh::beersma::SClassicFitCtl&)': model/borbely.cc:175:32: error:
> 'struct gsl_multifit_fdfsolver' has no member named 'J'
> gsl_multifit_covar( S->J, 0.0, covar); ^
> 
> This needs to be fixed for the ongoing gsl transition (#804246).
> 
> The full build log is attached, as is a patch to update the build
> dependencies for GSL 2 (changing libgsl0-dev to libgsl-dev).
> 
> Kind Regards,
> 
> Bas



pgpMJUEreAGN7.pgp
Description: OpenPGP digital signature

Bug#807728: Could not create directory: /home/jff/.cache

[Jörg Frings-Fürst]

Package: pbuilder
Version: 0.221.1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

since the last update I get allways:

[...]
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
E: Could not create directory: /home/jff/.cache:
boost::filesystem::create_directory: No such file or directory:
"/home/jff/.cache"
E: pbuilder-satisfydepends failed.
[...]

The directory /home/jff/.cache exists:

ls -al
insgesamt 38248
drwxr-xr-x 71 jff  jff   4096 Dez 12 07:30 .
drwxr-xr-x  4 root root  4096 Okt  9  2014 ..
[...]
- -rw-r--r--  1 jff  jff  39261 Jan 26  2015 .bzr.log
drwx-- 55 jff  jff   4096 Dez 12 07:19 .cache
drwx-- 10 jff  jff   4096 Jul 26 20:16 .claws-mail
drwx-- 53 jff  jff   4096 Dez  8 06:14 .config
drwx--  2 jff  jff   4096 Jul 19 13:01 .cups
drwx--  3 jff  jff   4096 Okt  9  2014 .dbus






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

Kernel: Linux 4.2.0-1-amd64 (SMP w/6 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 pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  debootstrap1.0.75
ii  dpkg-dev   1.18.3
ii  wget   1.17-1

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

Versions of packages pbuilder suggests:
ii  cowdancer 0.75
ii  gdebi-core0.9.5.7
pn  pbuilder-uml  

- -- debconf information:
  pbuilder/rewrite: false
  pbuilder/mirrorsite: http://mirror.1und1.de/debian/
  pbuilder/nomirror:

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWa8JzAAoJEAn4nzyModJdKJcQAIg7rf7JdR+OIldpLDOkBigN
GzRmai0waB3Wbvsl4H5dekxBNjAfW5UV6gS+ujX3c3uwgvXf29YS8BBn9V5a0gb/
r39txzdkJNXHA1UwNviH8N7MllsUoN+YAZ9/oOLak7uKYxggUYwncxBDWkZhJTGL
y2pamYf+ywbZ5bcqv/FuMP4hQq8ARO9DWxp0ehhjYXy+PX5rYu7OhOFJg3xKUch+
YECMo6Icf5qvcQieYO0M3QluU63NThBspYlKLo4349/MXvK3lh7MadRFSOFzgYh8
w8pcEQaL0Nsyg+P7Vk5QmtjhE1plR9tUzQP+q2WBYW7V4A/7PRqoKLgh+HOLAVrx
qDJU/MQ2rcNR07DgsSGdoU4KS+KfRNxWsiHAYkd3phGotLW8NUyw5dymcX2kujBv
df5B8nh82Ctcl+u7ShlZkHW0mBAi3XccpvXFMQ+mLP9vix/vFIKtXmIkOiUP5Zx9
WMRyEDLRZogQPNycKQ2X2XrkzZ/ZgiM6eAviGb+hJoRwOGSsvoKAA8xxadj362pi
zK2PRHxbhU39fpeeVqjBvL2ESQKDGyqGq6Z6pTF+4tfk1ptPJ5XGwzQZe6NW3lYA
VSk2h9+GQCY5TJAJHktWw2KEYlzNHHGUhjLYdXG4fZc/Hgg7vw64c6Z6l9rkLI2q
7SeBLo9n03DwK2LpqFSS
=1R+Y
-END PGP SIGNATURE-

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

[Lisandro Damián Nicanor Pérez Meyer]

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

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#807645: ifupdown package fails to configure itself (by dpkg)

[Vincent Danjean]

Package: ifupdown
Version: 0.8.2
Severity: serious
Justification: fail to configure itself

  Hi,

  I just upgraded ifupdown and it fails to configure itself.
I've added "set -x" to /var/lib/dpkg/info/ifupdown.postinst and
a final "echo done $?" at the end of /lib/systemd/systemd-sysv-install. Here
are the results:

# LC_ALL=C dpkg -a --configure
Setting up ifupdown (0.8.2) ...
+ MYNAME=ifupdown.postinst
+ [ configure = configure ]
+ addgroup --quiet --system netdev
+ [ configure = configure ]
+ [ ! -f /etc/network/interfaces ]
+ [ configure = configure ]
+ [ -x /etc/init.d/networking ]
+ update-rc.d networking defaults
+ [ configure = configure ]
+ [ -e /etc/udev/rules.d/z60_ifupdown.rules ]
+ dpkg-maintscript-helper rm_conffile /etc/default/ifupdown 0.7~+ ifupdown -- 
configure 0.7.54
+ dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown 0.7~+ ifupdown -- 
configure 0.7.54
+ dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown-clean 0.7~beta1 
ifupdown -- configure 0.7.54
+ [ configure = configure -a -e /bin/systemctl ]
+ [ -z 0.7.54 ]
+ dpkg --compare-versions 0.7.54 lt 0.8
+ echo Enabling networking.service.
Enabling networking.service.
+ systemctl enable networking.service
Synchronizing state of networking.service with SysV init with 
/lib/systemd/systemd-sysv-install...
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
Errors were encountered while processing:
 ifupdown
#

So, something is wrong with the "systemctl enable networking.service" call but
is is not the /lib/systemd/systemd-sysv-install invocation.

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

  Regards,
Vincent

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

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

Versions of packages ifupdown depends on:
ii  adduser   3.113+nmu3
ii  iproute2  4.3.0-1
ii  libc6 2.19-22
ii  lsb-base  9.20150917

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.3.3-5

Versions of packages ifupdown suggests:
ii  ppp 2.4.7-1+1
pn  rdnssd  

-- no debconf information

Processed: tagging 804386

[Debian Bug Tracking System]

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

> tags 804386 + pending fixed-upstream
Bug #804386 [condor] condor: FTBFS on arm64 ppc64el and s390x: conflicting 
declaration 'typedef long unsigned int uint64_t'
Added tag(s) fixed-upstream and pending.
> thanks
Stopping processing here.

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

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

[Guido Günther]

Source: srtp
Version: 1.4.5~20130609~dfsg-1.1
Severity: grave
Tags: security

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

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

for a list of patches.
Cheers,
 -- Guido


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

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

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Stephen Allen]

Package: gnome-shell
Version: 3.18.3-2
Followup-For: Bug #789118

Dear Maintainer,

Pretty close to this bug, although it's not dependant on upgrading Gnome. The
last few upgrades of SID have surfaced a similiar bug.

On setting my power settings via Gnome-Settings for 15 minutes, upon attempting
to 'wake up' screenlock, nothing will work. Must do a hard reboot.



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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  evolution-data-server3.18.2-1
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.18.3-1
ii  gir1.2-caribou-1.0   0.4.19-1
ii  gir1.2-clutter-1.0   1.24.2-1
ii  gir1.2-freedesktop   1.46.0-3
ii  gir1.2-gcr-3 3.18.0-1
ii  gir1.2-gdesktopenums-3.0 3.18.1-1
ii  gir1.2-gdm-1.0   3.18.2-1
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.46.0-3
ii  gir1.2-gnomebluetooth-1.03.18.1-1
ii  gir1.2-gnomedesktop-3.0  3.18.2-1
ii  gir1.2-gtk-3.0   3.18.6-1
ii  gir1.2-gweather-3.0  3.18.1-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.18.2-1
ii  gir1.2-networkmanager-1.01.0.8-2
ii  gir1.2-nmgtk-1.0 1.0.8-1
ii  gir1.2-pango-1.0 1.38.1-1
ii  gir1.2-polkit-1.00.105-14
ii  gir1.2-soup-2.4  2.52.2-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.3-1+b2
ii  gjs  1.44.0-1
ii  gnome-backgrounds3.18.0-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gnome-settings-daemon3.18.2-1
ii  gnome-shell-common   3.18.3-2
ii  gsettings-desktop-schemas3.18.1-1
ii  libatk-bridge2.0-0   2.18.1-1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-4
ii  libcairo21.14.4-1
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libclutter-1.0-0 1.24.2-1
ii  libcogl-pango20  1.22.0-1
ii  libcogl201.22.0-1
ii  libcroco30.6.9-1
ii  libdbus-glib-1-2 0.102-1
ii  libecal-1.2-19   3.18.2-1
ii  libedataserver-1.2-213.18.2-1
ii  libgcr-base-3-1  3.18.0-1
ii  libgdk-pixbuf2.0-0   2.32.2-1
ii  libgirepository-1.0-11.46.0-3
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.44.0-1
ii  libglib2.0-0 2.46.2-1
ii  libgstreamer1.0-01.6.1-1
ii  libgtk-3-0   3.18.6-1
ii  libical1a1.0.1-0.1
ii  libjson-glib-1.0-0   1.0.4-2
ii  libmozjs-24-024.2.0-3
ii  libmutter0g  3.18.2-1
ii  libnm-glib4  1.0.8-2
ii  libnm-util2  1.0.8-2
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpolkit-agent-1-0  0.105-14
ii  libpolkit-gobject-1-00.105-14
ii  libpulse-mainloop-glib0  7.1-2
ii  libpulse07.1-2
ii  libsecret-1-00.18.3-1
ii  libstartup-notification0 0.12-4
ii  libsystemd0  228-2
ii  libtelepathy-glib0   0.24.1-1.1
ii  libx11-6 2:1.6.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  mutter   3.18.2-1
ii  python3  3.4.3-7
ii  telepathy-mission-control-5  1:5.16.3-1

Versions of packages gnome-shell 

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

[Gianfranco Costamagna]

I have a build ongoing right now in amd64 i386 arm64 armel armhf powerpc.

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

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

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.

cheers,

G.




Il Venerdì 11 Dicembre 2015 14:39, John Paul Adrian Glaubitz 
 ha scritto:
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


-- 
To unsubscribe, send mail to 807589-unsubscr...@bugs.debian.org.


debdiff
Description: Binary data

Bug#807705: xserver-xorg-video-openchrome: FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before '__extension__'

[Chris Lamb]

Source: xserver-xorg-video-openchrome
Version: 1:0.3.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

xserver-xorg-video-openchrome fails to build from source in unstable/amd64:

  [..]

  make[5]: Entering directory 
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -fvisibility=hidden -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri  
-fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm 
-I/usr/include/xorg -I/usr/include/X11/dri  -I/usr/include/libdrm 
-I/usr/include/X11/dri -g -O2 -c -o via_3d.lo ../../src/via_3d.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
-fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm 
-I/usr/include/xorg -I/usr/include/X11/dri -fvisibility=hidden 
-I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/xorg 
-I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -c 
../../src/via_3d.c  -fPIC -DPIC -o .libs/via_3d.o
  In file included from /usr/include/string.h:634:0,
   from /usr/include/xorg/os.h:53,
   from /usr/include/xorg/misc.h:115,
   from /usr/include/xorg/xf86str.h:37,
   from /usr/include/xorg/xf86.h:44,
   from ../../src/via_3d.h:27,
   from ../../src/via_3d.c:24:
  /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
   strndup(const char *str, size_t n);
   ^
  Makefile:596: recipe for target 'via_3d.lo' failed
  make[5]: *** [via_3d.lo] Error 1
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
  Makefile:611: recipe for target 'all-recursive' failed
  make[4]: *** [all-recursive] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
  Makefile:475: recipe for target 'all' failed
  make[3]: *** [all] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
  Makefile:445: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build'
  Makefile:377: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:34: 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
   `-


xserver-xorg-video-openchrome.1:0.3.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807707: ddclient exit hook for dhclient breaks network configuration

[Doug Kingston]

Package: ddclient
Version: 3.8.2-2
Severity: critical
Tags: patch
Justification: breaks the whole system

Dear Maintainer,

As far as I can tell, this also impacts the unstable version (3.8.2-3)

What led up to the situation?

After installing ddclient on my Google Compute Engine hosted Debian/Jessie
VM
the VM failed to be usable after a reboot.  The VM was unable to route
packets
because it had failed to install the route to the network gateway or a
default
route.

What exactly did you do (or not do) that was effective (or ineffective)?

Determined that adding ddclient to a Debian/Jessie system on GCE rendered
the
VM unable to reboot properly.  Diagnosis indicated that routing was not
being
properly set up.  Neither was the hostname being set properly.  Both are
done
by other dhclient exit hooks in /etc/dhcp/dhclient-exit-hooks.d.  They were
not
being run.  They are run by /sbin/dhclient-script using run-part -list and
then
sourcing each hook file in turn.

The Problem:  When I looked at the ddclient hook, I noticed it was calling
exit(0),
which exited the entire dhclient-script prematurely.  This is very bad,
since none
of the other exits was given an opportuntity to run.  Exits must not call
exit!
Returning of error status should be through the "exit_status" shell variable
instead - as documented (poorly) in the manual page for dhclient-script(8).

I changed the ddclient exit hook to not call exit, but instead to return
control
to the dhclient-script as is the "API" for these hooks.

What was the outcome of this action?

The system now boots properly.  :-)

-Doug-


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

Kernel: Linux 3.16.0-4-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: systemd (via /run/systemd/system)

Versions of packages ddclient depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  initscripts2.88dsf-59
ii  lsb-base   4.1+Debian13+nmu1
ii  perl [perl5]   5.20.2-3+deb8u1

Versions of packages ddclient recommends:
ii  libio-socket-ssl-perl  2.002-2+deb8u1

ddclient suggests no packages.

-- Configuration Files:
/etc/dhcp/dhclient-exit-hooks.d/ddclient changed:
run_ddclient() {
[ -x /usr/sbin/ddclient ] || return
[ -f /etc/default/ddclient ] || return
. /etc/default/ddclient
[ $run_dhclient = "true" ] || return
case $reason in
BOUND | RENEW | REBIND)
/usr/bin/logger -t dhclient $reason, updating IP address with
ddclient
/usr/sbin/ddclient -daemon=0 -syslog > /dev/null 2>&1
;;
*)
;;
esac
}
run_ddclient


-- debconf information:
* ddclient/protocol: dyndns2
  ddclient/blankhostslist:
  ddclient/run_daemon: true
* ddclient/server: dynamic.pairnic.com
* ddclient/names: google.randomnotes.org
* ddclient/service: other
* ddclient/username: pairnic
* ddclient/fetchhosts: Manually
  ddclient/daemon_interval: 300
* ddclient/password-mismatch:
  ddclient/hostslist:
  ddclient/run_ipup: false
  ddclient/run_dhclient: false
* ddclient/interface: lo1
* ddclient/checkip: false
  ddclient/modifiedconfig:



Suggested Patch:
*** ddclient.broken 2014-10-06 18:46:05.0 +
--- ddclient2015-12-11 19:52:57.248086052 +
***
*** 1,16 
  #!/bin/sh
  # /etc/dhcp/dhclient-exit-hooks.d/ddclient - exit hook for dhclient

! [ -x /usr/sbin/ddclient ] || exit 0
! [ -f /etc/default/ddclient ] || exit 0
! . /etc/default/ddclient
! [ $run_dhclient = "true" ] || exit 0

! case $reason in
! BOUND | RENEW | REBIND)
! /usr/bin/logger -t dhclient $reason, updating IP address with
ddclient
! /usr/sbin/ddclient -daemon=0 -syslog > /dev/null 2>&1
! ;;
! *)
! ;;
! esac
--- 1,20 
  #!/bin/sh
  # /etc/dhcp/dhclient-exit-hooks.d/ddclient - exit hook for dhclient

! run_ddclient() {
! [ -x /usr/sbin/ddclient ] || return
! [ -f /etc/default/ddclient ] || return
! . /etc/default/ddclient
! [ $run_dhclient = "true" ] || return

! case $reason in
!   BOUND | RENEW | REBIND)
! /usr/bin/logger -t dhclient $reason, updating IP address with
ddclient
! /usr/sbin/ddclient -daemon=0 -syslog > /dev/null 2>&1
! ;;
!   *)
! ;;
! esac
! }
!
! run_ddclient

Bug#793911: groovy should not release with stretch

[Miguel Landaeta]

Hi Markus,

On Sat, Nov 28, 2015 at 01:53:03PM +0100, Markus Koschany wrote:
> 
> [...]
> 
> These are the current reverse dependencies in unstable:
> 
> libspring-java -> must be updated to a newer version

I already pushed some trivial changes to the repo to migrate
libspring-java to groovy2.

> jenkins -> unmaintainable, can be ignored
> 
> It bothers me jenkins package status but I'm not in a position to
> help at this moment.
> 
> red5 -> must be updated to a newer version

Emmanuel sent a patch for this. Please see #805627.

> If you want to update either libspring-java or red5, that would be a big
> help.

To package libspring-java new upstream releases is a task that would
be very appreciated although is not easy but with the recent progress
in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is
something more feasible nowadays.

Regarding red5, I'm not quite sure how much is used in Debian
nowadays. Maybe we should contact Damien to check if he agrees to
transfer its maintenance to pkg-java. I'm ccing him just in case.

Cheers,

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#793911: groovy should not release with stretch

[Markus Koschany]

Am 11.12.2015 um 21:16 schrieb Miguel Landaeta:
[...]
>> red5 -> must be updated to a newer version
> 
> Emmanuel sent a patch for this. Please see #805627.
> 
>> If you want to update either libspring-java or red5, that would be a big
>> help.
> 
> To package libspring-java new upstream releases is a task that would
> be very appreciated although is not easy but with the recent progress
> in Maven and Gradle helpers (thanks to Emmanuel again!) maybe this is
> something more feasible nowadays.
> 
> Regarding red5, I'm not quite sure how much is used in Debian
> nowadays. Maybe we should contact Damien to check if he agrees to
> transfer its maintenance to pkg-java. I'm ccing him just in case.

Hi,

we can always consider to fix red5 with a NMU. We just should raise the
severity accordingly before we do that.

I hope I can lend you a hand with an update of libspring-java after I
have packaged the latest netbeans release. Perhaps you can write a short
TODO list and push it to the libspring-java repo, which upstream should
be packaged, if we have to package new dependencies and where you need
help.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#807706: uima-addons: FTBFS: Unresolveable build extension: Plugin org.apache.uima:PearPackagingMavenPlugin:2.3.1

[Chris Lamb]

Source: uima-addons
Version: 2.3.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,

uima-addons fails to build from source in unstable/amd64:

  [..]

  [INFO] Scanning for projects...
  [WARNING] The POM for org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 is 
missing, no dependency information available
  [ERROR] [ERROR] Some problems were encountered while processing the POMs:
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 807502 binutils-avr
Bug #807502 [gcc-avr] gcc-avr: Missing support for atxmega384d3 since last 
upload
Bug reassigned from package 'gcc-avr' to 'binutils-avr'.
No longer marked as found in versions gcc-avr/1:4.9.2+Atmel3.5.0-1.
Ignoring request to alter fixed versions of bug #807502 to the same values 
previously set
> --
Stopping processing here.

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

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

[Hakan Ardo]

Hi,
the file you want is crtx384d3.o and not crtatxmega384d3.o (even i the new
avr-libc). Dont know why he's suddenly trying to use crtatxmega384d3.o
instead, but the issue seems to be in binutils. I'm reassigning the bug
there and will keep looking...

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

> On Friday 11 December 2015 16:15:52 Hakan Ardo wrote:
> > Please do.
>
> Done, thanks!
>
> > 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...
>
> It might be, if so just ping me as soon as it's available in incoming.d.o
> and
> I'll happily give it a try.
>
> Thanks!
>
> --
> The volume of a pizza of thickness a and radius z can be described by
> the following formula:
>
> pi zz a
>
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
>



-- 
Håkan Ardö

Processed: RM: haskell-concrete-typerep -- ROM; Unmaintained by upstream

[Debian Bug Tracking System]

Processing control commands:

> block 807606 by -1
Bug #807606 [src:haskell-concrete-typerep] haskell-concrete-typerep: FTBFS: 
Constructor `TypeRep' should have 4 arguments, but has been given 3
807606 was not blocked by any bugs.
807606 was not blocking any bugs.
Added blocking bug(s) of 807606: 807642

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

Bug#807607: marked as done (pkg-haskell-tools: FTBFS: At least the following dependencies are missing: base >=4.6 && <4.8)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2015 09:47:01 +0100
with message-id <1449823621.3363.0.ca...@debian.org>
and subject line Re: Bug#807607: pkg-haskell-tools: FTBFS:
has caused the Debian Bug report #807607,
regarding pkg-haskell-tools: FTBFS: At least the following dependencies are 
missing: base >=4.6 && <4.8
to be marked as done.

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

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


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

pkg-haskell-tools fails to build from source in unstable/amd64:

  [..]

  make_setup_recipe
  Running ghc --make Setup.hs -o debian/hlibrary.setup
  [1 of 1] Compiling Main ( Setup.hs, Setup.o )
  Linking debian/hlibrary.setup ...
  . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
  configure_recipe
  Running debian/hlibrary.setup configure --ghc -v2
  --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
  --libdir=/usr/lib/haskell-packages/ghc/lib --builddir=dist-ghc
  --ghc-option=-optl-Wl\,-z\,relro
  --haddockdir=/usr/lib/ghc-doc/haddock/dht-0.1/ --datasubdir=dht
  --htmldir=/usr/share/doc/libghc-dht-doc/html/
  Configuring dht-0.1...
  hlibrary.setup: At least the following dependencies are missing:
  base >=4.6 && <4.8
  /usr/share/cdbs/1/class/hlibrary.mk:142: recipe for target
  'configure-ghc-stamp' failed
  make: *** [configure-ghc-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


pkg-haskell-tools.0.10.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 0.10.1

already fixed. Thanks nevertheless!

Am Donnerstag, den 10.12.2015, 22:59 +0200 schrieb Chris Lamb:
> Source: pkg-haskell-tools
> Version: 0.10
> 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,
> 
> pkg-haskell-tools fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   make_setup_recipe
>   Running ghc --make Setup.hs -o debian/hlibrary.setup
>   [1 of 1] Compiling Main ( Setup.hs, Setup.o )
>   Linking debian/hlibrary.setup ...
>   . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
>   configure_recipe
>   Running debian/hlibrary.setup configure --ghc -v2
>   --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
>   --libdir=/usr/lib/haskell-packages/ghc/lib --builddir=dist-ghc
>   --ghc-option=-optl-Wl\,-z\,relro
>   --haddockdir=/usr/lib/ghc-doc/haddock/dht-0.1/ --datasubdir=dht
>   --htmldir=/usr/share/doc/libghc-dht-doc/html/
>   Configuring dht-0.1...
>   hlibrary.setup: At least the following dependencies are missing:
>   base >=4.6 && <4.8
>   /usr/share/cdbs/1/class/hlibrary.mk:142: recipe for target
>   'configure-ghc-stamp' failed
>   make: *** [configure-ghc-stamp] Error 1
> 
>   [..]
> 
> The full build log is attached.
> 
> 
> Regards,
> 
> ___
> Pkg-haskell-maintainers mailing list
> pkg-haskell-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-m
> aintainers
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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