Bug#841363: junit4: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:junit4
Version: 4.12-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -pjunit4 --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -O--buildsystem=maven
/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
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping JUnit
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.345 s
[INFO] Finished at: 2016-10-19T20:46:35+02:00
[INFO] Final Memory: 8M/90M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1: 1 problem was 
encountered while building the effective model for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[ERROR] [ERROR] 'dependencies.dependency.version' for 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar is missing. @
[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 

Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

[Adam Borowski]

Package: clementine
Version: 1.3.1+git240-g1a2f6e2+dfsg-1
Severity: grave
Justification: renders package unusable


Since today's upload, Clementine fails to produce any sound at all, instead
popping up a window with endlessly repeating:

GStreamer encountered a general stream error.
---
GStreamer encountered a general stream error.
---
GStreamer encountered a general stream error.
---
GStreamer encountered a general stream error.


No amount of messing with user-available settings (which have been dumbed
down to just "Output device" with "Choose automatically" and a handful of
"Default device on ") seems to help.  Settings that are apparently
not meant to be adjusted by the user (~/.config/Clementine/Clementine.conf)
are undocumented at all, with nary a comment; what I remember from past
versions (cf #823301) doesn't seem to work anymore.

This is reproducible on different hardware, even of different architectures
(I just happen to have exactly one non-remote amd64 box but plenty of arms),
all using plain ALSA.



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

Kernel: Linux 4.9.0-rc1-debug-pp2+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.8.3-1
ii  gstreamer1.0-plugins-good   1.8.3-1+b1
ii  gstreamer1.0-plugins-ugly   1.8.3-1
ii  libc6   2.24-5
ii  libcdio13   0.83-4.2+b1
ii  libchromaprint1 1.3.2-2
ii  libcrypto++65.6.4-1
ii  libfftw3-double33.3.5-1
ii  libgcc1 1:6.2.0-7
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.1-1
ii  libgpod40.8.3-8
ii  libgstreamer-plugins-base1.0-0  1.8.3-1
ii  libgstreamer1.0-0   1.8.3-1
ii  libimobiledevice6   1.2.0+dfsg-3
ii  liblastfm1  1.0.9-1
ii  libmtp9 1.1.12-1
ii  libmygpo-qt11.0.9~git20151122-1
ii  libplist3   1.12-3.1
ii  libprojectm2v5  2.1.0+dfsg-4+b1
ii  libprotobuf10   3.0.0-7
ii  libpulse0   9.0-4.0nosystemd1
ii  libqjson0   0.8.1-3
ii  libqt4-dbus 4:4.8.7+dfsg-9
ii  libqt4-network  4:4.8.7+dfsg-9
ii  libqt4-opengl   4:4.8.7+dfsg-9
ii  libqt4-sql  4:4.8.7+dfsg-9
ii  libqt4-sql-sqlite   4:4.8.7+dfsg-9
ii  libqt4-xml  4:4.8.7+dfsg-9
ii  libqtcore4  4:4.8.7+dfsg-9
ii  libqtgui4   4:4.8.7+dfsg-9
ii  libqxt-gui0 0.6.2-3
ii  libsqlite3-03.15.0-1
ii  libstdc++6  6.2.0-7
ii  libtag1v5   1.11+dfsg.1-0.3
ii  libx11-62:1.6.3-1
ii  projectm-data   2.1.0+dfsg-4
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages clementine recommends:
ii  gstreamer1.0-alsa  1.8.3-1

Versions of packages clementine suggests:
ii  gstreamer1.0-plugins-bad  1.8.3-1+b3

-- no debconf information

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Emmanuel Bourg]

Le 19/10/2016 à 22:31, Santiago Vila a écrit :

> I have already reported a bug like this in other packages.
> See Bug #841197 for a likely fix.

...and you'll get the same issue with all reverse dependencies of
maven-enforcer. These bugs are duplicates of the same issue, they should
be assigned to maven-enforcer, merged, and marked as affecting the
reverse dependencies:

  activemq
  activemq-activeio
  activemq-protobuf
  animal-sniffer
  annotation-indexer
  async-http-client
  checkstyle
  jacoco
  jboss-logmanager
  jboss-modules
  junit4
  libhibernate3-java
  maven-jar-plugin
  openjpa
  wagon

Emmanuel Bourg

Bug#832838: eclipse-xsd: FTBFS: Duplicate methods named spliterator with the parameters () and () are inherited from the types List and Collection

[Emmanuel Bourg]

Control: notfound -1 2.9.0-1
Control: close -1

This issue was a side effect of #757536. It went away with the upload of
eclipse/3.8.1-9

Processed: maven-enforcer: Missing dependency version causes FTBFS

[Debian Bug Tracking System]

Processing control commands:

> reassign 841197 maven-enforcer
Bug #841197 [src:libhibernate3-java] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:libhibernate3-java' to 'maven-enforcer'.
No longer marked as found in versions libhibernate3-java/3.6.10.Final-5.
Ignoring request to alter fixed versions of bug #841197 to the same values 
previously set
> reassign 841296 maven-enforcer
Bug #841296 [src:openjpa] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:openjpa' to 'maven-enforcer'.
No longer marked as found in versions openjpa/2.4.0-3.
Ignoring request to alter fixed versions of bug #841296 to the same values 
previously set
> reassign 841362 maven-enforcer
Bug #841362 [src:activemq-protobuf] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:activemq-protobuf' to 'maven-enforcer'.
No longer marked as found in versions activemq-protobuf/1.1-4.
Ignoring request to alter fixed versions of bug #841362 to the same values 
previously set
> reassign 841363 maven-enforcer
Bug #841363 [src:junit4] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:junit4' to 'maven-enforcer'.
No longer marked as found in versions junit4/4.12-4.
Ignoring request to alter fixed versions of bug #841363 to the same values 
previously set
> forcemerge 841197 841296 841362 841363
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Merged 841197 841296 841362 841363
> tags 841197 patch pending
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Added tag(s) pending and patch.
Added tag(s) patch and pending.
Added tag(s) patch and pending.
Added tag(s) patch and pending.

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

Bug#841197: maven-enforcer: Missing dependency version causes FTBFS

[Markus Koschany]

Control: reassign 841197 maven-enforcer
Control: reassign 841296 maven-enforcer
Control: reassign 841362 maven-enforcer
Control: reassign 841363 maven-enforcer
Control: forcemerge 841197 841296 841362 841363
Control: tags 841197 patch pending

I am going to reassign this issue to maven-enforcer and patch the pom file.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

On Wed, Oct 19, 2016 at 10:50:33PM +0200, Emmanuel Bourg wrote:
> Le 19/10/2016 à 22:31, Santiago Vila a écrit :
> 
> > I have already reported a bug like this in other packages.
> > See Bug #841197 for a likely fix.
> 
> ...and you'll get the same issue with all reverse dependencies of
> maven-enforcer. These bugs are duplicates of the same issue, they should
> be assigned to maven-enforcer, merged, and marked as affecting the
> reverse dependencies:
> [...]

You are absolutely right. Sorry for the duplicates.

I read a message from Markus yesterday, but I read it too fast and
didn't realize he already said this was a bug in maven-enforcer.

I see that he already did the merge and the reassign.

I'm going to make the "affects" with the list of reverse depends you
have provided. This definitely helps me to avoid duplicate bugs.

Thanks a lot.

Bug#841364: partial workaround: purging config files

[Adam Borowski]

It appears that there are two parts to this bug:

1. failure to deal with config files written by older versions.  Nuking
~/.config/Clementine then manually redoing all of your config makes
Clementine at least continue and put its sound _somewhere_.  Whether you'll
actually hear something depends on whether the first device is something
good or some crap like "HDA-Intel - HDA NVidia".  I guess that, had I
connected some HDMI TV or maybe a monitor with built-in speakers, I would
hear something.

2. routing regression gone further -- 1.3.1 merely didn't provide GUI
controls to select an audio sink but it still worked if set by an earlier
version or by manually by editing the config file


-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Processed: Re: Bug#841288: tigervnc-common: amd64 has dep libgnutls-deb0-28

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #841288 [tigervnc-common] tigervnc-common: amd64 has dep libgnutls-deb0-28
Severity set to 'serious' from 'normal'

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

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[Hilmar Preuße]

Am 19.10.2016 um 17:20 schrieb Danai SAE-HAN (韓達耐):

Hi all,


It looks like a problem with the wftodm binary.  This is an important piece
in the creation of the fonts.
I will only have access to my PC next week Thursday (27 October 2016) to
check the C source code and replicate it on amd64.  Please bear with me for
a while.


I *think* I can reproduce the bug.

Here is the gdb backtrace:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.
(gdb) bt
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x2ba08dfdbda3 in _IO_vfprintf_internal (s=s@entry=0x7ffd926eb3f0,
format=, format@entry=0x5643d866b22e "/StdHW [ %s ] 
|-\n",

ap=ap@entry=0x7ffd926eb518) at vfprintf.c:1637
#2  0x2ba08dffcacb in __IO_vsprintf (
string=0x7ffd926eb620 "/StdHW [ re{16 16} |-\n",
format=0x5643d866b22e "/StdHW [ %s ] |-\n", 
args=args@entry=0x7ffd926eb518)

at iovsprintf.c:42
#3  0x2ba08dfe2327 in __sprintf (s=, 
format=)

at sprintf.c:32
#4  0x5643d866a8e2 in e_printf (form=, i0=out>,

i1=, i2=, i3=,
i4=, i5=1936353124, i6=-1838284703, i7=0, 
i8=-1909291776,

i9=0) at wftodm.c:306
#5  0x5643d866aa77 in output_pfa (file=1) at wftodm.c:255
#6  0x5643d8669d3a in main (ac=, ag=)
at wftodm.c:158

And here is the function e_printf() in question:

e_printf(form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9)
char *form;
{
  int len,i;
  unsigned char buf[4096];
  sprintf(buf,form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9);
  len=strlen(buf);
  for(i=0;i

Processed: Bug#831857: libupnp: CVE-2016-6255: write files via POST

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #831857 [src:libupnp] libupnp: CVE-2016-6255: write files via POST
Added tag(s) pending and patch.

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

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:activemq-protobuf
Version: 1.1-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibactivemq-protobuf-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -O--buildsystem=maven
/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
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] 

[... snipped ...]

[WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-release-plugin:2.3.2: Plugin 
org.apache.maven.plugins:maven-release-plugin:2.3.2 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 has not been downloaded 
from it before.
[INFO] 
[INFO] 
[INFO] Building ActiveMQ Protocol Buffers POM 1.1
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
from it before.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could 
not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) 
in offline mode and the artifact 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from 
it before.
[WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-antrun-plugin:1.7: Plugin 
org.apache.maven.plugins:maven-antrun-plugin:1.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 has not been downloaded 
from it before.
[WARNING] The POM for 
org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-4 is missing, no 
dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4: Plugin 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline 

Processed: forwarded zshdb ftbfs bug

[Debian Bug Tracking System]

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

> forwarded 841342 https://github.com/rocky/zshdb/issues/8
Bug #841342 [src:zshdb] zshdb: FTBFS under some locales (eg. fr_CH.UTF-8)
Set Bug forwarded-to-address to 'https://github.com/rocky/zshdb/issues/8'.
> kthxbye
Stopping processing here.

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

Bug#831857: libupnp: CVE-2016-6255: write files via POST

[James Cowgill]

Control: tags -1 patch pending

Hi,

I am about to upload the attached NMU to finally fix this bug. I've also
attached a patch suitable for jessie-security, and a test script I used
to create a libupnp server for testing the fix with.

Thanks,
James
/*
 * Upnp CVE-2016-6255 test program
 *
 * This program runs the webserver from libupnp serving files from the current
 * directory. If libupnp is vulnerable to CVE-2016-6255, it will allow uploading
 * files.
 *
 * Example:
 *
 * $ gcc -I/usr/include/upnp cve-2016-6255-test.c -lupnp -ocve-2016-6255-test
 * $ cat testfile
 * cat: testfile: No such file or directory
 * $ ./cve-2016-6255-test > /dev/null &
 * [2] 32309
 * $ curl -i --data $'FAIL\n' http://localhost:49152/testfile
 * $ cat testfile
 * FAIL
 */

#define _GNU_SOURCE
#include 
#include 
#include 

int main(void)
{
	char* wd = get_current_dir_name();

	// Setup upnp
	printf("Init = %d\n", UpnpInit("127.0.0.1", 0));
	printf("SetRoot = %d\n", UpnpSetWebServerRootDir(wd));
	free(wd);

	// Hang
	for (;;)
		pause();
}
diff -Nru libupnp-1.6.19+git20141001/debian/changelog 
libupnp-1.6.19+git20141001/debian/changelog
--- libupnp-1.6.19+git20141001/debian/changelog 2014-10-23 21:48:01.0 
+0100
+++ libupnp-1.6.19+git20141001/debian/changelog 2016-10-19 21:02:05.0 
+0100
@@ -1,3 +1,12 @@
+libupnp (1:1.6.19+git20141001-1+deb8u1) jessie-security; urgency=high
+
+  * Non-maintainer upload.
+  * Don't allow unhandled POSTs to write to the filesystem by
+default (Closes: #831857) (CVE-2016-6255)
+Thanks to Matthew Garrett for the patch.
+
+ -- James Cowgill   Wed, 19 Oct 2016 21:02:05 +0100
+
 libupnp (1:1.6.19+git20141001-1) unstable; urgency=low
 
   * Ack both NMUs, thankyou for your care of this package.
diff -Nru libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch 
libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch
--- libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch   
1970-01-01 01:00:00.0 +0100
+++ libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch   
2016-10-19 21:00:38.0 +0100
@@ -0,0 +1,61 @@
+From c91a8a3903367e1163765b73eb4d43be7d7927fa Mon Sep 17 00:00:00 2001
+From: Matthew Garrett 
+Date: Tue, 23 Feb 2016 13:53:20 -0800
+Subject: [PATCH] Don't allow unhandled POSTs to write to the filesystem by
+ default
+
+If there's no registered handler for a POST request, the default behaviour
+is to write it to the filesystem. Several million deployed devices appear
+to have this behaviour, making it possible to (at least) store arbitrary
+data on them. Add a configure option that enables this behaviour, and change
+the default to just drop POSTs that aren't directly handled.
+
+Signed-off-by: Marcelo Roberto Jimenez 
+---
+ configure.ac | 4 
+ upnp/inc/upnpconfig.h.in | 5 +
+ upnp/src/genlib/net/http/webserver.c | 4 
+ 3 files changed, 13 insertions(+)
+
+--- a/configure.ac
 b/configure.ac
+@@ -495,6 +495,10 @@ if test "x$enable_blocking_tcp_connectio
+ AC_DEFINE(UPNP_ENABLE_BLOCKING_TCP_CONNECTIONS, 1, [see upnpconfig.h])
+ fi
+ 
++RT_BOOL_ARG_ENABLE([postwrite], [no], [write to the filesystem on otherwise 
unhandled POST requests])
++if test "x$enable_postwrite" = xyes ; then
++AC_DEFINE(UPNP_ENABLE_POST_WRITE, 1, [see upnpconfig.h])
++fi
+ 
+ RT_BOOL_ARG_ENABLE([samples], [yes], [compilation of upnp/sample/ code])
+ 
+--- a/upnp/inc/upnpconfig.h.in
 b/upnp/inc/upnpconfig.h.in
+@@ -131,5 +131,10 @@
+  * header (i.e. configure --enable-unspecified_server) */
+ #undef UPNP_ENABLE_UNSPECIFIED_SERVER
+ 
++/** Defined to 1 if the library has been compiled to support filesystem 
writes on POST
++ *  (i.e. configure --enable-postwrite) */
++#undef UPNP_ENABLE_POST_WRITE
++
++
+ #endif /* UPNP_CONFIG_H */
+ 
+--- a/upnp/src/genlib/net/http/webserver.c
 b/upnp/src/genlib/net/http/webserver.c
+@@ -1366,9 +1366,13 @@ static int http_RecvPostMessage(
+   if (Fp == NULL)
+   return HTTP_INTERNAL_SERVER_ERROR;
+   } else {
++#ifdef UPNP_ENABLE_POST_WRITE
+   Fp = fopen(filename, "wb");
+   if (Fp == NULL)
+   return HTTP_UNAUTHORIZED;
++#else
++  return HTTP_NOT_FOUND;
++#endif
+   }
+   parser->position = POS_ENTITY;
+   do {
diff -Nru libupnp-1.6.19+git20141001/debian/patches/series 
libupnp-1.6.19+git20141001/debian/patches/series
--- libupnp-1.6.19+git20141001/debian/patches/series2014-10-04 
05:26:29.0 +0100
+++ libupnp-1.6.19+git20141001/debian/patches/series2016-10-19 
21:00:43.0 +0100
@@ -5,3 +5,4 @@
 18-url-upnpstrings.patch
 19_fix_tests.patch
 21_fix-1.6.19+git.patch
+CVE-2016-6255.patch
diff -Nru libupnp-1.6.19+git20160116/debian/changelog 
libupnp-1.6.19+git20160116/debian/changelog
--- libupnp-1.6.19+git20160116/debian/changelog 2016-01-17 

Processed: bug 841304 is forwarded to https://sourceware.org/ml/libc-alpha/2016-10/msg00325.html

[Debian Bug Tracking System]

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

> forwarded 841304 https://sourceware.org/ml/libc-alpha/2016-10/msg00325.html
Bug #841304 [glibc] invalid code in glibc tests
Changed Bug forwarded-to-address to 
'https://sourceware.org/ml/libc-alpha/2016-10/msg00325.html' from 
'https://gcc.gnu.org/PR78039'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#832838: eclipse-xsd: FTBFS: Duplicate methods named spliterator with the parameters () and () are inherited from the types List and Collection

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 2.9.0-1
Bug #832838 [src:eclipse-xsd] eclipse-xsd: FTBFS: Duplicate methods named 
spliterator with the parameters () and () are inherited from the types 
List and Collection
No longer marked as found in versions eclipse-xsd/2.9.0-1.
> close -1
Bug #832838 [src:eclipse-xsd] eclipse-xsd: FTBFS: Duplicate methods named 
spliterator with the parameters () and () are inherited from the types 
List and Collection
Marked Bug as done

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

Processed: node-once: missing dependency on node-wrappy makes a lot of packages to FTBFS

[Debian Bug Tracking System]

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

> tags 841274 + patch
Bug #841274 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841321 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841322 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841323 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841324 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841325 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841326 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841327 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841328 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841329 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841330 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841331 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841332 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841333 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841334 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841335 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841336 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841337 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841338 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
841274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841274
841321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841321
841322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841322
841323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841323
841324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841324
841325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841325
841326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841326
841327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841327
841328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841328
841329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841329
841330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841330
841331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841331
841332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841332
841333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841333
841334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841334
841335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841335
841336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841336
841337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841337
841338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841274: node-once: missing dependency on node-wrappy makes a lot of packages to FTBFS

[Santiago Vila]

tags 841274 + patch
thanks

Trivial patch attached.

(Not that I know anything about node, this is just the message from
Bas but translated to patch).

Thanks.--- a/debian/control
+++ b/debian/control
@@ -15,6 +15,7 @@ Package: node-once
 Architecture: all
 Depends:
  ${misc:Depends}
+ , node-wrappy
  , nodejs
 Description: Run a function only once with this module for Node.js
  node-once is useful to make sure a listener for multiple events is

Bug#838414: marked as done (gpick: colors.txt is non-free)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 06:50:23 +
with message-id 
and subject line Bug#838414: fixed in gpick 0.2.5+git20161017-1
has caused the Debian Bug report #838414,
regarding gpick: colors.txt is non-free
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.)


-- 
838414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpick
Version: 0.2.5-2
Severity: serious
Justification: Policy 2.2.1


Hello and thanks for maintaining this little tool in Debian!

I noticed that the license for file share/gpick/colors.txt fails
to meet the DFSG, as it includes at least one non-free restriction.
Clause 5 states:

|  5. These RGB colour formulations may not be used to the detriment of
|  Resene Paints Ltd.

This is a non-free restriction on use, which does not comply with
DFSG#6 (No Discrimination Against Fields of Endeavor).

This file is therefore unfit for the main Debian archive.

Possible solutions I can think of:

 A) get in touch with the colors.txt copyright holders (Resene Paints
Ltd.) and persuade them to drop the troublesome clause or, even
better, to re-license the file under well-known and widely used
DFSG-free terms (such as, for instance, the 3-clause BSD license
adopted by the rest of gpick)

 B) find a DFSG-free replacement for share/gpick/colors.txt and use it
in stead of the non-free one

 C) drop share/gpick/colors.txt from the package, if possible

 D) move the gpick package to the non-free archive (I hope this will
*not* happen!)

I hope solution A may be persued soon.
Solution B (or C) may be chosen as a temporary quick fix, while trying
to achieve solution A.

Thanks for your time!
Bye.
--- End Message ---
--- Begin Message ---
Source: gpick
Source-Version: 0.2.5+git20161017-1

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

Debian distribution maintenance software
pp.
Elías Alejandro Año Mendoza  (supplier of updated gpick 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 Oct 2016 20:33:52 -0300
Source: gpick
Binary: gpick
Architecture: source i386
Version: 0.2.5+git20161017-1
Distribution: unstable
Urgency: medium
Maintainer: Elías Alejandro Año Mendoza 
Changed-By: Elías Alejandro Año Mendoza 
Description:
 gpick  - advanced GTK+ color picker
Closes: 838414
Changes:
 gpick (0.2.5+git20161017-1) unstable; urgency=medium
 .
   * Imported Upstream Git snapshot 0.2.5+git20161017
   * Upstream fixed replacement of colors.txt
 because of license issues (Closes: #838414)
   * Updated debian/copyright
   * debian/patches
 + 01_reproducible_build.patch: Updated
   * debian/control
 + Add Build-Depends: ragel, gettext,libboost-test-dev,
   libboost-system-dev, libboost-filesystem-dev
Checksums-Sha1:
 699596d2cae7942a63ed99d6e6ce9dda3f4beb5f 2140 gpick_0.2.5+git20161017-1.dsc
 2bada0e3c6eacaf344bfc8bf3c9ac325d1ea65ac 348875 
gpick_0.2.5+git20161017.orig.tar.gz
 819bcf87f038beb1e7ca530127dcf86576bdd57c 4124 
gpick_0.2.5+git20161017-1.debian.tar.xz
 1784ee700968b7440881cdf4c21a2cbc4e2d7008 4429088 
gpick-dbgsym_0.2.5+git20161017-1_i386.deb
 9efd8d3dbbc15c7b5ea39fb071e5f0bc8327fd15 349946 
gpick_0.2.5+git20161017-1_i386.deb
Checksums-Sha256:
 49c71af1bb3c4acf5e99234352fb27e495628a45f601dc0e2dd6b3eb28b498ff 2140 
gpick_0.2.5+git20161017-1.dsc
 c036296d992f486fe6214d68d977e1b045c250f642d1b7a559bcf4ebf11ddca6 348875 
gpick_0.2.5+git20161017.orig.tar.gz
 f5f0d359a4e3be556971a7e3f3a763828edae3797c1e3c643730611a34869478 4124 
gpick_0.2.5+git20161017-1.debian.tar.xz
 56b59dff76fd87d70098a0cd4b35966058d2b422c5adc78e8b54e812d0e8ec5b 4429088 
gpick-dbgsym_0.2.5+git20161017-1_i386.deb
 2366cb97f17de732d2fe3b8513d8620710dd90d4dc41cc281507d131533654df 349946 
gpick_0.2.5+git20161017-1_i386.deb
Files:
 6b9880677cb857772130811311f143f7 2140 graphics optional 
gpick_0.2.5+git20161017-1.dsc
 c7665f3f08d9dc4094a949e1a50aaaf5 

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Lars Tangvald]

Hi,

This might be an error in the CPU announcement (they sometimes get 
corrections after the initial announcement). I'll try to track down 
someone who's worked on this fix and ask.


--
Lars

On 10/19/2016 08:21 AM, Salvatore Bonaccorso wrote:

Hi Lars, hi Norvald,

On Wed, Oct 19, 2016 at 08:03:00AM +0200, Lars Tangvald wrote:

The following CVEs are fixed in 5.5.53:
CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

The listing of CVE-2016-6662 is confusing here. This should actually
already be addressed in 5.5.52, cf.
http://legalhackers.com/advisories/MySQL-Exploit-Remote-Root-Code-Execution-Privesc-CVE-2016-6662.html

Any insight on why Oracle claims it to be only fixed in 5.5.53?

Regards,
Salvatore

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Chris Lamb]

Source: node-define-property
Version: 0.2.5-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,

node-define-property fails to build from source in unstable/amd64:

  […]

  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23461 files and directories currently installed.)
  Preparing to unpack .../00-dh-buildinfo_0.11+nmu1_all.deb ...
  Unpacking dh-buildinfo (0.11+nmu1) ...
  Selecting previously unselected package libuv1:amd64.
  Preparing to unpack .../01-libuv1_1.9.1-1_amd64.deb ...
  Unpacking libuv1:amd64 (1.9.1-1) ...
  Selecting previously unselected package nodejs.
  Preparing to unpack .../02-nodejs_4.6.0~dfsg-3_amd64.deb ...
  Unpacking nodejs (4.6.0~dfsg-3) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../03-libjpeg62-turbo_1%3a1.5.1-1_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.5.1-1) ...
  Selecting previously unselected package libpng16-16:amd64.
  Preparing to unpack .../04-libpng16-16_1.6.25-2_amd64.deb ...
  Unpacking libpng16-16:amd64 (1.6.25-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../05-libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../06-libtiff5_4.0.6-2_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-2) ...
  Selecting previously unselected package libxau6:amd64.
  Preparing to unpack .../07-libxau6_1%3a1.0.8-1_amd64.deb ...
  Unpacking libxau6:amd64 (1:1.0.8-1) ...
  Selecting previously unselected package libxdmcp6:amd64.
  Preparing to unpack .../08-libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
  Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Selecting previously unselected package libxcb1:amd64.
  Preparing to unpack .../09-libxcb1_1.12-1_amd64.deb ...
  Unpacking libxcb1:amd64 (1.12-1) ...
  Selecting previously unselected package libx11-data.
  Preparing to unpack .../10-libx11-data_2%3a1.6.3-1_all.deb ...
  Unpacking libx11-data (2:1.6.3-1) ...
  Selecting previously unselected package libx11-6:amd64.
  Preparing to unpack .../11-libx11-6_2%3a1.6.3-1_amd64.deb ...
  Unpacking libx11-6:amd64 (2:1.6.3-1) ...
  Selecting previously unselected package shared-mime-info.
  Preparing to unpack .../12-shared-mime-info_1.7-1_amd64.deb ...
  Unpacking shared-mime-info (1.7-1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-common.
  Preparing to unpack .../13-libgdk-pixbuf2.0-common_2.36.0-1_all.deb ...
  Unpacking libgdk-pixbuf2.0-common (2.36.0-1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-0:amd64.
  Preparing to unpack .../14-libgdk-pixbuf2.0-0_2.36.0-1_amd64.deb ...
  Unpacking libgdk-pixbuf2.0-0:amd64 (2.36.0-1) ...
  Selecting previously unselected package libnotify4:amd64.
  Preparing to unpack .../15-libnotify4_0.7.7-1_amd64.deb ...
  Unpacking libnotify4:amd64 (0.7.7-1) ...
  Selecting previously unselected package libnotify-bin.
  Preparing to unpack .../16-libnotify-bin_0.7.7-1_amd64.deb ...
  Unpacking libnotify-bin (0.7.7-1) ...
  Selecting previously unselected package node-growl.
  Preparing to unpack .../17-node-growl_1.7.0-1_all.deb ...
  Unpacking node-growl (1.7.0-1) ...
  Selecting previously unselected package node-lru-cache.
  Preparing to unpack .../18-node-lru-cache_2.3.1-1_all.deb ...
  Unpacking node-lru-cache (2.3.1-1) ...
  Selecting previously unselected package node-sigmund.
  Preparing to unpack .../19-node-sigmund_1.0.0-1_all.deb ...
  Unpacking node-sigmund (1.0.0-1) ...
  Selecting previously unselected package node-minimatch.
  Preparing to unpack .../20-node-minimatch_1.0.0-1_all.deb ...
  Unpacking node-minimatch (1.0.0-1) ...
  Selecting previously unselected package node-readdirp.
  Preparing to unpack .../21-node-readdirp_0.2.4-2_all.deb ...
  Unpacking node-readdirp (0.2.4-2) ...
  Selecting previously unselected package node-monocle.
  Preparing to unpack .../22-node-monocle_1.1.51+dfsg-1_all.deb ...
  Unpacking node-monocle (1.1.51+dfsg-1) ...
  Selecting previously unselected package node-async.
  Preparing to unpack .../23-node-async_0.8.0-1_all.deb ...
  Unpacking node-async (0.8.0-1) ...
  Selecting previously unselected package node-minimist.
  Preparing to unpack .../24-node-minimist_1.2.0-1_all.deb ...
  Unpacking node-minimist (1.2.0-1) ...
  

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Lars Tangvald]

Hi,

On 10/19/2016 10:18 AM, Moritz Muehlenhoff wrote:

Hi,

On Wed, Oct 19, 2016 at 09:10:59AM +0200, Lars Tangvald wrote:

So for Linux we consider this fixed in 5.5.52, but the complete fix
was in 5.5.53.

Is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837984
addressed in 5.5.53?

No, this hasn't been changed.
If you take a look at 
https://github.com/mysql/mysql-server/blob/5.5/scripts/mysqld_safe.sh 
(just search for 'i386') you'll see it restricts it to intel architectures.
This is a whitelist of where the --malloc-lib option is allowed to be 
set, and is restricted to the intel archs because we considered it of 
little use on other architectures.
If needs to be available on other architectures we could make a patch in 
the packaging to add them.



Should I remove the CVE from the Debian changelog entry?

That's not needed, we can add a comment to the Security Tracker.

Ok, thanks :)

--
Lars

Cheers,
 Moritz

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Moritz Muehlenhoff]

Hi,

On Wed, Oct 19, 2016 at 09:10:59AM +0200, Lars Tangvald wrote:
> So for Linux we consider this fixed in 5.5.52, but the complete fix
> was in 5.5.53.

Is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837984
addressed in 5.5.53?

> Should I remove the CVE from the Debian changelog entry?

That's not needed, we can add a comment to the Security Tracker.

Cheers,
Moritz

Bug#841163: [debian-mysql] Bug#841163: Security fixes from the October 2016 CPU

[Lars Tangvald]

The following CVEs are fixed by 5.7.16:
CVE-2016-5584 CVE-2016-6304 CVE-2016-6662 CVE-2016-7440

--
Lars

On 10/18/2016 10:24 AM, Norvald H. Ryeng wrote:

Source: mysql-5.7
Version: 5.7.15-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on 
Tuesday, October 18. According to the pre-release announcement [1], it 
will contain information about CVEs fixed in MySQL 5.7.16.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html


___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#841257: sendmail: Privilege escalation from group smmsp to (user) root

[paul . szabo]

Hmm (again) ... Maybe file /usr/share/sendmail/sendmail needs updating
also? It is almost identical to /etc/init.d/sendmail, and in file
/etc/cron.daily/sendmail I notice the lines:

...
#--
# Every so often, give sendmail a chance to run the MSP queues.
*/20 ****   smmsp   test -x /etc/init.d/sendmail && 
/usr/share/sendmail/sendmail cron-msp
#
#--
# Every so often, give sendmail a chance to run the MTA queues.
# Will also run MSP queues if enabled
#*/10 ****  roottest -x /etc/init.d/sendmail && 
/usr/share/sendmail/sendmail cron-mta
...

Maybe no problem as long as that second line is commented out.

I wonder about the first line (whether it is needed), seeing how my
machines always have a process like:

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
smmsp 2880  0.0  0.0  11956  3236 ?Ss   Oct11   0:00 sendmail: 
Queue runner@00:10:00 for /var/spool/mqueue-client

running.

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Processed: Re: Bug#841252: libtk-filedialog-perl: Control-W is deprecated in $W variable, needs to be changed to $^W with literal ^ character

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #841252 [libtk-filedialog-perl] libtk-filedialog-perl: Control-W is 
deprecated in $W variable, needs to be changed to $^W with literal ^ character
Severity set to 'grave' from 'normal'
> tag -1 sid stretch
Bug #841252 [libtk-filedialog-perl] libtk-filedialog-perl: Control-W is 
deprecated in $W variable, needs to be changed to $^W with literal ^ character
Added tag(s) sid and stretch.

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

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Lars Tangvald]

The following CVEs are fixed in 5.5.53:
CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:

Source: mysql-5.5
Version: 5.5.52-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on 
Tuesday, October 18. According to the pre-release announcement [1], it 
will contain information about CVEs fixed in MySQL 5.5.53.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html


___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Salvatore Bonaccorso]

Hi Lars, hi Norvald,

On Wed, Oct 19, 2016 at 08:03:00AM +0200, Lars Tangvald wrote:
> The following CVEs are fixed in 5.5.53:
> CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

The listing of CVE-2016-6662 is confusing here. This should actually
already be addressed in 5.5.52, cf.
http://legalhackers.com/advisories/MySQL-Exploit-Remote-Root-Code-Execution-Privesc-CVE-2016-6662.html

Any insight on why Oracle claims it to be only fixed in 5.5.53?

Regards,
Salvatore

Bug#841267: libcork16 and libcork15: error when trying to install together

[Ralf Treinen]

Package: libcork15,libcork16
Version: libcork15/0.15.0+ds-6
Version: libcork16/0.15.0+ds-7
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-10-19
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package libcork15:amd64.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../libcork15_0.15.0+ds-6_amd64.deb ...
Unpacking libcork15:amd64 (0.15.0+ds-6) ...
Selecting previously unselected package libcork16:amd64.
Preparing to unpack .../libcork16_0.15.0+ds-7_amd64.deb ...
Unpacking libcork16:amd64 (0.15.0+ds-7) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcork16_0.15.0+ds-7_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcork.so.16.0.1', which is 
also in package libcork15:amd64 0.15.0+ds-6
Processing triggers for libc-bin (2.24-5) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libcork16_0.15.0+ds-7_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/lib/x86_64-linux-gnu/libcork.so.16.0.1

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

-Ralf.

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

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Lars Tangvald]

On 10/19/2016 08:21 AM, Salvatore Bonaccorso wrote:

Hi Lars, hi Norvald,

On Wed, Oct 19, 2016 at 08:03:00AM +0200, Lars Tangvald wrote:

The following CVEs are fixed in 5.5.53:
CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

The listing of CVE-2016-6662 is confusing here. This should actually
already be addressed in 5.5.52, cf.
http://legalhackers.com/advisories/MySQL-Exploit-Remote-Root-Code-Execution-Privesc-CVE-2016-6662.html

Any insight on why Oracle claims it to be only fixed in 5.5.53?

Regards,
Salvatore
The CPU listing concerns all platforms, and there were some additional 
complexities in the CVE for other platforms.
So for Linux we consider this fixed in 5.5.52, but the complete fix was 
in 5.5.53.

Should I remove the CVE from the Debian changelog entry?
I've got the updated packages built and tested, so should have the 
debdiff pretty much ready.


--
Lars

Bug#839791: qtcreator: builds with clang support on armel

[Emilio Pozuelo Monfort]

On Sat, 15 Oct 2016 10:52:30 -0300 "Lisandro
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer"  wrote:
> On miércoles, 5 de octubre de 2016 12:52:08 A. M. ART Emilio Pozuelo Monfort 
> wrote:
> > Source: qtcreator
> > Version: 4.1.0-1
> > Severity: serious
> > 
> > Hi!
> > 
> > qtcreator builds with LLVM 3.8 on armel, however LLVM 3.8 is not
> > available there. (Well, there is an old version still in the archive,
> > built from a snapshot from llvm-toolchain-snapshot, which hasn't been
> > removed yet, that will happen soon in #839033.
> > 
> > Note this is blocking testing migration:
> 
> Hi! I'm missing some commits in the repo, as soon as they are pushed I'll 
> happily fix this.

Cc'ing Adam so he can see this.

Cheers,
Emilio

Bug#841267: marked as done (libcork16 and libcork15: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 10:36:00 +
with message-id 
and subject line Bug#841267: fixed in libcork 0.15.0+ds-8
has caused the Debian Bug report #841267,
regarding libcork16 and libcork15: error when trying to install together
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.)


-- 
841267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcork15,libcork16
Version: libcork15/0.15.0+ds-6
Version: libcork16/0.15.0+ds-7
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-10-19
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package libcork15:amd64.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../libcork15_0.15.0+ds-6_amd64.deb ...
Unpacking libcork15:amd64 (0.15.0+ds-6) ...
Selecting previously unselected package libcork16:amd64.
Preparing to unpack .../libcork16_0.15.0+ds-7_amd64.deb ...
Unpacking libcork16:amd64 (0.15.0+ds-7) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcork16_0.15.0+ds-7_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcork.so.16.0.1', which is 
also in package libcork15:amd64 0.15.0+ds-6
Processing triggers for libc-bin (2.24-5) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libcork16_0.15.0+ds-7_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/lib/x86_64-linux-gnu/libcork.so.16.0.1

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

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: libcork
Source-Version: 0.15.0+ds-8

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated libcork package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Oct 2016 19:09:44 +0900
Source: libcork
Binary: libcork-dev libcork16 libcork-doc
Architecture: source
Version: 0.15.0+ds-8
Distribution: unstable
Urgency: medium
Maintainer: Roger Shimizu 
Changed-By: Roger Shimizu 
Description:
 libcork-dev - simple, easily embeddable, cross-platform C library (development
 libcork-doc - simple, easily embeddable, cross-platform C library (documentatio
 libcork16  - simple, easily embeddable, cross-platform C library
Closes: 841267
Changes:
 libcork (0.15.0+ds-8) unstable; urgency=medium
 .
   * debian/patches:
 - Add 0012 patch to bump libcork version to 16.0.2
   (Closes: #841267)
Checksums-Sha1:
 18ae89a7670731dfc88dfef2cb1929d97ee02241 1993 

Bug#841285: freemat: FTBFS (cannot find -lclangTidyReadabilityModule)

[Santiago Vila]

Package: src:freemat
Version: 4.2+dfsg1-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/freemat-4.2+dfsg1/debian/build --parallel
   dh_testdir -i -O--buildsystem=cmake 
-O--builddirectory=/<>/freemat-4.2\+dfsg1/debian/build -O--parallel
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/freemat-4.2\+dfsg1/debian/build -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/freemat-4.2+dfsg1'
dh_auto_configure -- -DCMAKE_INSTALL_PREFIX=/usr 
-DRESOURCEDIR=/usr/share/freemat -DCMAKE_BUILD_TYPE=Release 
-DCMAKE_C_FLAGS="-Wall -g -O2 
-fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security" -DCMAKE_C_FLAGS_DEBUG="-Wall -g -O2 
-fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security" -DCMAKE_C_FLAGS_RELEASE="-Wall -g -O2 
-fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -DNDEBUG" -DCMAKE_SKIP_RPATH=ON -DUSE_LLVM=ON 
-DFORCE_BUNDLED_PCRE=OFF -DFORCE_BUNDLED_UMFPACK=OFF 
-DFORCE_BUNDLED_PORTAUDIO=OFF -DFORCE_BUNDLED_ZLIB=OFF -DFORCE_BUNDLED_AMD=OFF
cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_INSTALL_PREFIX=/usr 
-DRESOURCEDIR=/usr/share/freemat -DCMAKE_BUILD_TYPE=Release 
"-DCMAKE_C_FLAGS=-Wall -g -O2 
-fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security" "-DCMAKE_C_FLAGS_DEBUG=-Wall -g -O2 
-fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security" "-DCMAKE_C_FLAGS_RELEASE=-Wall -g -O2 
-fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -DNDEBUG" -DCMAKE_SKIP_RPATH=ON -DUSE_LLVM=ON 
-DFORCE_BUNDLED_PCRE=OFF -DFORCE_BUNDLED_UMFPACK=OFF 
-DFORCE_BUNDLED_PORTAUDIO=OFF -DFORCE_BUNDLED_ZLIB=OFF -DFORCE_BUNDLED_AMD=OFF
-- The CXX compiler identification is GNU 6.2.0
-- The C compiler identification is GNU 6.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info

[... snipped ...]

[100%] Linking CXX executable FreeMat
cd /<>/freemat-4.2+dfsg1/debian/build/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/FreeMat.dir/link.txt --verbose=1
/usr/bin/c++   -g -O2 -fdebug-prefix-map=/<>/freemat-4.2+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -O3 -DNDEBUG   -Wl,-z,relro 
CMakeFiles/FreeMat.dir/application.moc.cpp.o 
CMakeFiles/FreeMat.dir/application.cpp.o 
CMakeFiles/FreeMat.dir/FuncMode.moc.cpp.o 
CMakeFiles/FreeMat.dir/ScriptMode.moc.cpp.o 
CMakeFiles/FreeMat.dir/FuncMode.cpp.o CMakeFiles/FreeMat.dir/ScriptMode.cpp.o 
CMakeFiles/FreeMat.dir/FuncTerminal.cpp.o 
CMakeFiles/FreeMat.dir/MainApp.moc.cpp.o CMakeFiles/FreeMat.dir/MainApp.cpp.o 
CMakeFiles/FreeMat.dir/main.cpp.o CMakeFiles/FreeMat.dir/DumbTerminal.moc.cpp.o 
CMakeFiles/FreeMat.dir/DumbTerminal.cpp.o 
CMakeFiles/FreeMat.dir/Terminal.moc.cpp.o CMakeFiles/FreeMat.dir/Loader.cpp.o 
CMakeFiles/FreeMat.dir/Terminal.cpp.o CMakeFiles/FreeMat.dir/qrc_FreeMat.cxx.o 
CMakeFiles/FreeMat.dir/dummy.f.o  -o FreeMat  -L/usr/lib/llvm-3.6/lib -rdynamic 
../libs/libCore/libCore.a ../libs/libFN/libFN.a ../libs/libGraphics/libGrap
 hics.a ../libs/libFreeMat/libFreeMatlib.a ../libs/libXP/libXP.a 
../libs/libMex/libMex.a ../libs/libMatC/libMatC.a 
../libs/libFN/levmar-2.3/liblevmar.a ../libs/libMath/libLAPACK_C/liblapack_c.a 
../libs/libMath/libDynBlas/libdynblas.a ../libs/libMath/libBLAS_C/libblasref.a 
-lQtCore -lQtGui -lQtNetwork -lQtOpenGL -lQtXml -lQtSvg -lGLU -lGL -lncurses 
-lpcre -lfftw3 -lfftw3f -lz -larpack ../libs/libMath/libLAPACK_C/liblapack_c.a 
-lffi -lportaudio -lboost_math_c99 -lclang -lclangAnalysis 
-lclangApplyReplacements -lclangARCMigrate -lclangAST -lclangASTMatchers 
-lclangBasic -lclangCodeGen -lclangDriver -lclangDynamicASTMatchers -lclangEdit 
-lclangFormat -lclangFrontend -lclangFrontendTool -lclangIndex -lclangLex 
-lclangParse -lclangQuery -lclangRename -lclangRewrite -lclangRewriteFrontend 
-lclangSema -lclangSerialization -lclangStaticAnalyzerCheckers 
-lclangStaticAnalyzerCore -lclangStaticAnalyzerFrontend -lclangTidy 
-lclangTidyGoogleModule -lclangTidyLLVMModule -lclangTidyMiscModule -lclan
 gTidyReadabilityModule -lclangTidyUtils -lclang 
/usr/lib/llvm-3.6/lib/libLLVMExecutionEngine.a 
/usr/lib/llvm-3.6/lib/libLLVMOption.a /usr/lib/llvm-3.6/lib/libLLVMIRReader.a 
/usr/lib/llvm-3.6/lib/libLLVMLTO.a 

Processed: Re: [Pkg-php-pecl] Bug#841250: php-facedetect: FTBFS: error with opencv 3.1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #841250 [src:php-facedetect] php-facedetect: FTBFS: error with opencv 3.1
Severity set to 'serious' from 'important'

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

Bug#828674: marked as done (FTBFS under Django 1.10)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 10:39:01 +
with message-id 
and subject line Bug#828674: fixed in python-django-treebeard 4.0.1+dfsg-2
has caused the Debian Bug report #828674,
regarding FTBFS under Django 1.10
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.)


-- 
828674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-treebeard
Version: 4.0.1+dfsg-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-treebeard FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-treebeard_4.0.1+dfsg-1.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-django-treebeard
Source-Version: 4.0.1+dfsg-2

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
python-django-treebeard package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Oct 2016 11:29:57 +0200
Source: python-django-treebeard
Binary: python-django-treebeard python3-django-treebeard 
python-django-treebeard-doc
Architecture: source all
Version: 4.0.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-treebeard - Efficient implementations of tree data structures 
for Django
 python-django-treebeard-doc - Efficient implementations of tree data 
structures for Django (doc
 python3-django-treebeard - Efficient implementations of tree data structures 
for Django (Pyt
Closes: 828674
Changes:
 python-django-treebeard (4.0.1+dfsg-2) unstable; urgency=medium
 .
   * Replace django.conf.urls.patterns with lists (Closes: #828674).
   * Fix typo in long description.
   * Add patches to support Django 1.10:
 - Replace django.conf.urls.patterns with lists.
 - Pass through additional kwargs to support new `use_required_attribute`
   ModelForm argument.
 - Do not load templatetag  `cycle` from `future`.
 - Search request context processor in settings.TEMPLATES.
 - Add basic settings.TEMPLATES for tests.
   * Use https:// for copyright-format 1.0 URL.
Checksums-Sha1:
 1a15ffc754677e1d53895f692355f726ecd9ad0a 2129 
python-django-treebeard_4.0.1+dfsg-2.dsc
 431f4828689d08f23471e8ab5bb6160fcd9cb003 74349 
python-django-treebeard_4.0.1+dfsg.orig.tar.gz
 4a2f8a9e6127da38e8975a9978926910b99a3cbf 8788 
python-django-treebeard_4.0.1+dfsg-2.debian.tar.xz
 b20156f3793f4f6902334fdd62e6715e96b78e3c 119914 
python-django-treebeard-doc_4.0.1+dfsg-2_all.deb
 e6a33e593b9bea4eae07c251cae21702f7193a63 49110 
python-django-treebeard_4.0.1+dfsg-2_all.deb
 36336b7205f68a605470513944f8284d179bf7be 49010 
python3-django-treebeard_4.0.1+dfsg-2_all.deb
Checksums-Sha256:
 9fa3f273f01c5fb831a96ac0939bcd9f3d09ad9bacd5d9b89250954fa153276e 2129 
python-django-treebeard_4.0.1+dfsg-2.dsc
 f7b87244283efb1b80d619a91633b9575fc22f35f511c5d401a23e323ba8a88f 74349 
python-django-treebeard_4.0.1+dfsg.orig.tar.gz
 900e48386336b41d15df25a7aeab8c8e52d968d4fce253efae6b145b24f0a089 8788 
python-django-treebeard_4.0.1+dfsg-2.debian.tar.xz
 021bc2d5dada3064a292bddbd4aff8fd9a5f67e3cd8e21125616214c407f72d1 119914 
python-django-treebeard-doc_4.0.1+dfsg-2_all.deb
 

Bug#811836: marked as done (libavg: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 11:50:42 +
with message-id 
and subject line Bug#811836: fixed in libavg 1.8.1-3
has caused the Debian Bug report #811836,
regarding libavg: FTBFS with GCC 6: no match for
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.)


-- 
811836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libavg
Version: 1.8.1-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I. -I../../src  -I.. -I/usr/include/libxml2 -pthread 
> -Wdate-time -D_FORTIFY_SOURCE=2  -msse2 -O3 -ffast-math -Wall -pipe 
> -Wno-invalid-offsetof -Woverloaded-virtual -Wswitch -Wuninitialized 
> -Wempty-body -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -c -o testbase.o testbase.cpp
> In file included from StringHelper.cpp:22:0:
> StringHelper.h: In instantiation of 'void avg::fromString(const string&, T&) 
> [with T = int; std::__cxx11::string = std::__cxx11::basic_string]':
> StringHelper.cpp:70:20:   required from here
> StringHelper.h:115:35: error: no match for 'operator!=' (operand types are 
> 'std::basic_istream::__istream_type {aka std::basic_istream}' and 
> 'int')
>  bool bOk = (stream >> result) != 0;
> ~~~^~~~
> 
> StringHelper.h:115:35: note: candidate: operator!=(int, int) 
> StringHelper.h:115:35: note:   no known conversion for argument 1 from 
> 'std::basic_istream::__istream_type {aka std::basic_istream}' to 
> 'int'
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from Exception.h:26,
>  from StringHelper.h:26,
>  from StringHelper.cpp:22:
> /usr/include/c++/6/bits/stl_pair.h:357:5: note: candidate: template _T1, class _T2> constexpr bool std::operator!=(const std::pair<_T1, _T2>&, 
> const std::pair<_T1, _T2>&)
>  operator!=(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
>  ^~~~
> 
> /usr/include/c++/6/bits/stl_pair.h:357:5: note:   template argument 
> deduction/substitution failed:
> In file included from StringHelper.cpp:22:0:
> StringHelper.h:115:35: note:   'std::basic_istream::__istream_type {aka 
> std::basic_istream}' is not derived from 'const std::pair<_T1, _T2>'
>  bool bOk = (stream >> result) != 0;
> ~~~^~~~
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:67:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from Exception.h:26,
>  from StringHelper.h:26,
>  from StringHelper.cpp:22:
> /usr/include/c++/6/bits/stl_iterator.h:304:5: note: candidate: template _Iterator> bool std::operator!=(const std::reverse_iterator<_Iterator>&, 
> const std::reverse_iterator<_Iterator>&)
>  operator!=(const reverse_iterator<_Iterator>& __x,
>  ^~~~
> 
> /usr/include/c++/6/bits/stl_iterator.h:304:5: note:   template argument 
> deduction/substitution failed:
> In file included from StringHelper.cpp:22:0:
> StringHelper.h:115:35: note:   'std::basic_istream::__istream_type {aka 
> std::basic_istream}' is not derived from 'const 
> std::reverse_iterator<_Iterator>'
>  bool bOk = (stream >> result) != 0;
> ~~~^~~~
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:67:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from Exception.h:26,
>  from StringHelper.h:26,
>  from StringHelper.cpp:22:
> /usr/include/c++/6/bits/stl_iterator.h:354:5: note: candidate: template _IteratorL, class _IteratorR> bool std::operator!=(const 
> std::reverse_iterator<_Iterator>&, const std::reverse_iterator<_IteratorR>&)
>  

Bug#841281: gkeyring: Missing dependency on python-gnomekeyring

[Sam Morris]

Package: gkeyring
Version: 0.4-1-gf4ce4c7-1
Severity: serious
Justification: Policy 7.2

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The package appears to be missing a dependency on python-gnomekeyring.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (550, 'testing-debug'), (550, 'testing'), (520, 
'unstable-debug'), (520, 'unstable'), (510, 'experimental-debug'), (510, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gkeyring depends on:
pn  python:any  

gkeyring recommends no packages.

gkeyring suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIvBAEBCAAZBQJYB0SIEhxzYW1Acm9ib3RzLm9yZy51awAKCRDSC0ICXNonufja
EACNfRWaUPARQ3P9aNAXsnvyLAf8Sq4H1Zop3XM6Ap1NyBJMz0nE6BV4Sk9PODSx
bL8nozWwvc3W7GMmnmQjDuOPxiUU0OHRxpY+u4RGNTRpBuZeu+6kCyUoGT1xGu3L
UNk6raVN2zrxjt+eChlwnCwlzyGBZV83eatTDw4qBL5UMv+Rgp58XctuBM44OI4G
ED187AlinugBIsAtyUvTkqpKLDc+93UPXz7X+zXWc2eZkmv4KrPWKLNk+a4PppGl
IZrIwH5cDSncQi+wPqh2YttrSG80HTJJ5OHNT6j4HcRy5beed33CGGPKRJrcGLO0
YPmd9S/RE9W9hPLRpbDXjqRrv6CwmVF8ovytf3tbHnZfEQ7Dv2krUU8TNySl8wwl
EDXR8n8vitEgLYQX40WPWHVxyBHwVKafqDw2YTZLs3v++XPEn5wY3sHFzPKv3w9m
yNcrKzDAfk0NA82+CUHbKyNUbTwHB7m0bynWZHDLRs/TgHGcc9xQDOD4NbJ4zpPJ
ZmtH7eOW9BogHjRBHcYZruBPebNFYgKgSacsPDHOprkTfFith16Y8INnw2MP2VZh
uM/daBsC7WHYfs1iYz5yP0RRvkxMy83NAUvi0fa5AjWtXRzgKrGwMOQbfQJkV54/
WhsS3zRCQXbHxCKhjVERghSRKgGsCvWmoFzS73yOMVssHw==
=97s1
-END PGP SIGNATURE-

Bug#841286: jison depends on contrib packages (node-ebnf-parser, node-cjson)

[Jakub Wilk]

Package: jison
Version: 0.4.17+dfsg-3
Severity: serious
Justification: Policy §2.2.1

This package is in main, but it depends on node-ebnf-parser and node-cjson, 
which are both in contrib.


--
Jakub Wilk

Bug#836326: marked as done (gsequencer: FTBFS on i386: ags_channel_test segmentation fault)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 11:25:43 +
with message-id 
and subject line Bug#836326: fixed in gsequencer 0.7.90-1
has caused the Debian Bug report #836326,
regarding gsequencer: FTBFS on i386: ags_channel_test segmentation fault
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.)


-- 
836326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsequencer
Version: 0.7.62-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest i386 build of gsequencer failed because ags_channel_test
crashed.  Could you please take a look?

Thanks!

  PASS: ags_thread_test
  PASS: ags_audio_test
  ./test-driver: line 107:  9968 Segmentation fault  "$@" > $log_file 2>&1
  FAIL: ags_channel_test
  PASS: ags_recycling_test
  PASS: ags_audio_signal_test
  PASS: ags_recall_test
  PASS: ags_pattern_test
  PASS: ags_notation_test
  PASS: ags_automation_test
  PASS: ags_functional_audio_test
  =
 gsequencer 0.7.62: ./test-suite.log
  =
  
  # TOTAL: 10
  # PASS:  9
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  .. contents:: :depth: 2
  
  FAIL: ags_channel_test
  ==
  
  
  
   CUnit - A unit testing framework for C - Version 2.1-3
   http://cunit.sourceforge.net/
  
  
  Suite: AgsChannelTest
Test: test of AgsChannel add recall ...passed
Test: test of AgsChannel add recall container ...FAILED
  1. ags/test/audio/ags_channel_test.c:131  - 
g_list_find(channel->container, recall_container) != NULL
Test: test of AgsChannel add recall id ...FAILED
  1. ags/test/audio/ags_channel_test.c:148  - 
g_list_find(channel->recall_id, recall_id) != NULL
Test: test of AgsChannel add duplicate recall ...FAIL ags_channel_test 
(exit status: 139)
--- End Message ---
--- Begin Message ---
Source: gsequencer
Source-Version: 0.7.90-1

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
gsequencer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Oct 2016 11:40:23 +0200
Source: gsequencer
Binary: gsequencer gsequencer-doc libags0 libags-audio0 libags-gui0 libags-dev 
libags-audio-dev libags-gui-dev libags-doc libags-audio-doc libags-gui-doc
Architecture: source
Version: 0.7.90-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 gsequencer - Advanced Gtk+ Sequencer audio processing engine
 gsequencer-doc - documentation for Advanced Gtk+ Sequencer
 libags-audio-dev - Advanced Gtk+ Sequencer audio processing engine 
(Development file
 libags-audio-doc - Advanced Gtk+ Sequencer audio processing engine (API 
documentatio
 libags-audio0 - Advanced Gtk+ Sequencer audio processing library
 libags-dev - Advanced Gtk+ Sequencer core library (Development files)
 libags-doc - Advanced Gtk+ Sequencer core library (API documentation)
 libags-gui-dev - Advanced Gtk+ Sequencer widget library (Development files)
 libags-gui-doc - Advanced Gtk+ Sequencer widget library (API documentation)
 libags-gui0 - Advanced Gtk+ Sequencer widget library
 libags0- Advanced Gtk+ Sequencer core library
Closes: 836326 836327 836328
Changes:
 gsequencer (0.7.90-1) unstable; urgency=medium
 .
   * New upstream version 0.7.90
 (Closes: #836326, #836327, #836328)
 .
   [ Joël Krähemann ]
   * Added OSS4 dependency because GSequencer supports your /dev/dsp now
   * Upstream only partially fixed overlinking fix is now in vcs
   * Added configure flag alsa needs to be enabled
   * Updated debian/rules to build gtk-doc properly
   * Removed obsolete patch
   * Added libsamplerate 

Bug#836327: marked as done (gsequencer: FTBFS on mips and powerpc: ags_functional_audio_test segmentation fault)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 11:25:43 +
with message-id 
and subject line Bug#836327: fixed in gsequencer 0.7.90-1
has caused the Debian Bug report #836327,
regarding gsequencer: FTBFS on mips and powerpc: ags_functional_audio_test 
segmentation fault
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.)


-- 
836327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsequencer
Version: 0.7.62-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest builds of gsequencer for mips and powerpc both failed
because ags_functional_audio_test segfaulted:

https://buildd.debian.org/status/fetch.php?pkg=gsequencer=mips=0.7.62-1=1472716604
https://buildd.debian.org/status/fetch.php?pkg=gsequencer=powerpc=0.7.62-1=1472714618

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: gsequencer
Source-Version: 0.7.90-1

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
gsequencer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Oct 2016 11:40:23 +0200
Source: gsequencer
Binary: gsequencer gsequencer-doc libags0 libags-audio0 libags-gui0 libags-dev 
libags-audio-dev libags-gui-dev libags-doc libags-audio-doc libags-gui-doc
Architecture: source
Version: 0.7.90-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 gsequencer - Advanced Gtk+ Sequencer audio processing engine
 gsequencer-doc - documentation for Advanced Gtk+ Sequencer
 libags-audio-dev - Advanced Gtk+ Sequencer audio processing engine 
(Development file
 libags-audio-doc - Advanced Gtk+ Sequencer audio processing engine (API 
documentatio
 libags-audio0 - Advanced Gtk+ Sequencer audio processing library
 libags-dev - Advanced Gtk+ Sequencer core library (Development files)
 libags-doc - Advanced Gtk+ Sequencer core library (API documentation)
 libags-gui-dev - Advanced Gtk+ Sequencer widget library (Development files)
 libags-gui-doc - Advanced Gtk+ Sequencer widget library (API documentation)
 libags-gui0 - Advanced Gtk+ Sequencer widget library
 libags0- Advanced Gtk+ Sequencer core library
Closes: 836326 836327 836328
Changes:
 gsequencer (0.7.90-1) unstable; urgency=medium
 .
   * New upstream version 0.7.90
 (Closes: #836326, #836327, #836328)
 .
   [ Joël Krähemann ]
   * Added OSS4 dependency because GSequencer supports your /dev/dsp now
   * Upstream only partially fixed overlinking fix is now in vcs
   * Added configure flag alsa needs to be enabled
   * Updated debian/rules to build gtk-doc properly
   * Removed obsolete patch
   * Added libsamplerate dependency because libags_audio uses it
 .
   [ IOhannes m zmölnig ]
   * Removed unused patches
 .
   [ Joël Krähemann ]
   * Initial *.symbols files
 .
   [ IOhannes m zmölnig ]
   * Stripped debian-revision from .symbols files
 .
   [ Joël Krähemann ]
   * Added liboss4-salsa alternative to libasound2
   * Removed unneeded dependency
 .
   [ IOhannes m zmölnig ]
   * B-D on libjack-dev
   * Enabled ALSA-PCM only on linux
Checksums-Sha1:
 6d10d9dcdf24cbae3b0db9eabccda2dd4fea1c86 2911 gsequencer_0.7.90-1.dsc
 569482312f26267cd94565c219b48395244cabd6 2251746 gsequencer_0.7.90.orig.tar.gz
 d454d9f4fd6ec64b59400c7ddc565946292b04e6 16912 
gsequencer_0.7.90-1.debian.tar.xz
Checksums-Sha256:
 007ad4d416f6d45edc95ab945f7af7766d42f0a3f1bdd60c0383624fae41e080 2911 
gsequencer_0.7.90-1.dsc
 a35add9d8010aece755d5f499f884c8a25261588835279c48c011b57717c3a6e 2251746 
gsequencer_0.7.90.orig.tar.gz
 e85d7dcae01f1e8d851e9b4d5fc690f7304545843e2fe9093f86d447c47bcb13 16912 
gsequencer_0.7.90-1.debian.tar.xz
Files:
 

Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset

[Jonas Meurer]

Package: src:linux
Version: 4.7.6-1
Severity: grave
Justification: renders package unusable

Hello,

recently, something on my system related to drm/i915 broke. Since no
xserver/drm packages have been upgraded, I strongly suspect the latest
linux kernel upgrade to be the culprit.

Since several days, the X server on my Lenovo Thinkpad T460 sometimes
freezes, apparently when gnome locks and turns of the screen after some
time of inactivity. This renders the system completely unusable, it
seems to not react at all anymore. Also changing to a text consoly
(tty) doesn't work.

Below you find a copy of the relevant syslog entries. Unfortunately,
since the system is rendered unusable, I'm not able to save the crash
details from /sys/class/drm/card0/error. After reboot, it obviously is
empty again.

Please tell me if I can do anything more to debug this bug. It's very
annoying as it sometimes implies loosing things that you just worked on.

Unfortunately, I don't know another way to reproduce the bug apart from
waiting for the automatic screen lock. Then you have to be (un)lucky
because it doesn't freeze every time.

Cheers,
 jonas

(Assumed) relevant logs from /var/log/syslog:

[...]
Oct 12 21:43:01 calvin2 kernel: [11219.762878] [drm] RC6 on
Oct 12 21:43:25 calvin2 kernel: [11243.760753] [drm] RC6 on
Oct 12 21:43:54 calvin2 kernel: [11272.758240] [drm] RC6 on
Oct 12 21:44:23 calvin2 kernel: [11301.754923] [drm] RC6 on
Oct 12 21:44:40 calvin2 kernel: [11318.753426] [drm] stuck on render ring
Oct 12 21:44:40 calvin2 kernel: [11318.754593] [drm] GPU HANG: ecode 
9:0:0xfffe, in Xorg [2507], reas
on: Engine(s) hung, action: reset
Oct 12 21:44:40 calvin2 kernel: [11318.754599] [drm] GPU hangs can indicate a 
bug anywhere in the entire 
gfx stack, including userspace.
Oct 12 21:44:40 calvin2 kernel: [11318.754603] [drm] Please file a _new_ bug 
report on bugs.freedesktop.o
rg against DRI -> DRM/Intel
Oct 12 21:44:40 calvin2 kernel: [11318.754607] [drm] drm/i915 developers can 
then reassign to the right c
omponent if it's not a kernel issue.
Oct 12 21:44:40 calvin2 kernel: [11318.754610] [drm] The gpu crash dump is 
required to analyze gpu hangs,
 so please always attach it.
Oct 12 21:44:40 calvin2 kernel: [11318.754614] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Oct 12 21:44:40 calvin2 kernel: [11318.756979] drm/i915: Resetting chip after 
gpu hang
Oct 12 21:44:41 calvin2 kernel: [11319.761430] [drm] RC6 on
Oct 12 21:44:50 calvin2 kernel: [11328.752757] [drm] stuck on render ring
Oct 12 21:44:50 calvin2 kernel: [11328.753891] [drm] GPU HANG: ecode 
9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset
Oct 12 21:44:50 calvin2 kernel: [11328.756633] drm/i915: Resetting chip after 
gpu hang
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
EDID vendor "LGD", prod id 1188
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Printing DDC gathered Modelines:
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088  
+hsync -vsync (66.7 kHz eP)
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
EDID vendor "LGD", prod id 1188
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Printing DDC gathered Modelines:
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088  
+hsync -vsync (66.7 kHz eP)
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
EDID vendor "LGD", prod id 1188
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Printing DDC gathered Modelines:
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088  
+hsync -vsync (66.7 kHz eP)
Oct 12 21:44:51 calvin2 kernel: [11329.760399] [drm] RC6 on
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: 
intel_do_flush_locked failed: Input/output error
Oct 12 21:44:51 calvin2 firefox-esr.desktop[3113]: firefox-esr: Fatal IO error 
11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
Oct 12 21:44:51 calvin2 pidgin.desktop[2749]: Pidgin: Fatal IO error 11 (Die 
Ressource ist zur Zeit nicht verfügbar) on X server :0.
[...]
Oct 12 21:44:51 calvin2 kernel: [11329.834184] Qt bearer threa[2850]: segfault 
at 0 ip 7fd4d6fbe9e5 sp 7fd4b7b8e560 error 4 in 
libQt5DBus.so.5.6.1[7fd4d6f5c000+87000]
Oct 12 21:44:51 calvin2 nautilus-autostart.desktop[2779]: Server response: 
STATUS:OK:/home/user
Oct 12 21:44:51 calvin2 org.a11y.atspi.Registry[2589]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Oct 12 21:44:51 calvin2 org.a11y.atspi.Registry[2589]:   after 17393 
requests (17393 known processed) with 0 events remaining.
Oct 12 21:44:51 calvin2 

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Chris Lamb]

affects 841274 node-is-accessor-descriptor node-is-descriptor 
node-is-extendable node-is-number node-to-regex-range
thanks


Regards,

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

Bug#841132: marked as done (kid3: FTBFS: fatal error: chapterframe.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 10:44:41 +0200
with message-id <20161019084441.pzatnhr3whfyy...@aurel32.net>
and subject line Re: Bug#841132: Fwd: taglib_1.11+dfsg.1-0.3_amd64.changes 
ACCEPTED into unstable
has caused the Debian Bug report #841132,
regarding kid3: FTBFS: fatal error: chapterframe.h: No such file or directory
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.)


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

kid3 fails to build from source on all architectures with the following
error:

| /«PKGBUILDDIR»/src/plugins/taglibmetadata/taglibfile.cpp:119:26: fatal error: 
chapterframe.h: No such file or directory
|  #include 
|   ^
| compilation terminated.
| src/plugins/taglibmetadata/CMakeFiles/taglibmetadata.dir/build.make:93: 
recipe for target 
'src/plugins/taglibmetadata/CMakeFiles/taglibmetadata.dir/taglibfile.cpp.o' 
failed
| make[4]: *** 
[src/plugins/taglibmetadata/CMakeFiles/taglibmetadata.dir/taglibfile.cpp.o] 
Error 1

A full build log is available for example there:

https://buildd.debian.org/status/fetch.php?pkg=kid3=s390x=3.4.2-1%2Bb2=1476154044

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 2016-10-18 21:31, Matteo Cypriani wrote:
> This should fix it, but I'll let you guys close the bug whenever kid3 is 
> successfully rebuilt. I appologize for the trouble!

Thanks for the fix. I confirm that kid3 now builds fine, I am therefore
closing the bug.

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


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

Processed: Re: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Debian Bug Tracking System]

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

> affects 841274 node-is-accessor-descriptor node-is-descriptor 
> node-is-extendable node-is-number node-to-regex-range
Bug #841274 [src:node-define-property] node-define-property: FTBFS: Error: 
Cannot find module 'wrappy'
Added indication that 841274 affects node-is-accessor-descriptor, 
node-is-descriptor, node-is-extendable, node-is-number, and node-to-regex-range
> thanks
Stopping processing here.

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

Processed: Bug#836327 marked as pending

[Debian Bug Tracking System]

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

> tag 836327 pending
Bug #836327 [src:gsequencer] gsequencer: FTBFS on mips and powerpc: 
ags_functional_audio_test segmentation fault
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#836327: marked as pending

[IOhannes m zmölnig]

tag 836327 pending
thanks

Hello,

Bug #836327 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=pkg-multimedia/gsequencer.git;a=commitdiff;h=49a9008

---
commit 49a9008824e7758269778051990cadd75c804795
Author: IOhannes m zmölnig 
Date:   Wed Oct 19 11:41:09 2016 +0200

Ready for upload to unstable.

diff --git a/debian/changelog b/debian/changelog
index 7247fe8..e558727 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,42 +1,34 @@
-gsequencer (0.7.90-1) UNRELEASED; urgency=medium
+gsequencer (0.7.90-1) unstable; urgency=medium
+
+  * New upstream version 0.7.90
+(Closes: #836326, #836327, #836328)
 
   [ Joël Krähemann ]
-  * added OSS4 dependency because GSequencer supports your /dev/dsp now
-  * upstream only partially fixed overlinking fix is now in vcs
-  * added configure flag alsa needs to be enabled
-  * update debian/rules to build gtk-doc properly
-  * remove patch from series because upstream fixed
-  * added libsamplerate dependency because libags_audio uses it
+  * Added OSS4 dependency because GSequencer supports your /dev/dsp now
+  * Upstream only partially fixed overlinking fix is now in vcs
+  * Added configure flag alsa needs to be enabled
+  * Updated debian/rules to build gtk-doc properly
+  * Removed obsolete patch
+  * Added libsamplerate dependency because libags_audio uses it
 
   [ IOhannes m zmölnig ]
   * Removed unused patches
 
   [ Joël Krähemann ]
-  * initial *.symbols files
-  * added shlibs files
-  * updated symbols files
-  * remove unneeded shlibs files
-  * updated symbols files
-  * fixed initial symbols
-  * updated symbols
+  * Initial *.symbols files
 
   [ IOhannes m zmölnig ]
   * Stripped debian-revision from .symbols files
 
   [ Joël Krähemann ]
-  * added liboss4-salsa alternative to libasound2
-  * updated libags.symbols to 0.7.86
-  * updated libags-audio.symbols to 0.7.86
-  * removed unneeded dependency
+  * Added liboss4-salsa alternative to libasound2
+  * Removed unneeded dependency
 
   [ IOhannes m zmölnig ]
   * B-D on libjack-dev
-  * Enable ALSA-PCM only on linux
-
-  [ Joël Krähemann ]
-  * New upstream version 0.7.90
+  * Enabled ALSA-PCM only on linux
 
- -- Joël Krähemann   Fri, 02 Sep 
2016 13:15:49 +0200
+ -- IOhannes m zmölnig (Debian/GNU)   Wed, 19 Oct 2016 
11:40:23 +0200
 
 gsequencer (0.7.62-1) unstable; urgency=medium
 

Processed: Bug#836326 marked as pending

[Debian Bug Tracking System]

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

> tag 836326 pending
Bug #836326 [src:gsequencer] gsequencer: FTBFS on i386: ags_channel_test 
segmentation fault
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#836326: marked as pending

[IOhannes m zmölnig]

tag 836326 pending
thanks

Hello,

Bug #836326 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=pkg-multimedia/gsequencer.git;a=commitdiff;h=49a9008

---
commit 49a9008824e7758269778051990cadd75c804795
Author: IOhannes m zmölnig 
Date:   Wed Oct 19 11:41:09 2016 +0200

Ready for upload to unstable.

diff --git a/debian/changelog b/debian/changelog
index 7247fe8..e558727 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,42 +1,34 @@
-gsequencer (0.7.90-1) UNRELEASED; urgency=medium
+gsequencer (0.7.90-1) unstable; urgency=medium
+
+  * New upstream version 0.7.90
+(Closes: #836326, #836327, #836328)
 
   [ Joël Krähemann ]
-  * added OSS4 dependency because GSequencer supports your /dev/dsp now
-  * upstream only partially fixed overlinking fix is now in vcs
-  * added configure flag alsa needs to be enabled
-  * update debian/rules to build gtk-doc properly
-  * remove patch from series because upstream fixed
-  * added libsamplerate dependency because libags_audio uses it
+  * Added OSS4 dependency because GSequencer supports your /dev/dsp now
+  * Upstream only partially fixed overlinking fix is now in vcs
+  * Added configure flag alsa needs to be enabled
+  * Updated debian/rules to build gtk-doc properly
+  * Removed obsolete patch
+  * Added libsamplerate dependency because libags_audio uses it
 
   [ IOhannes m zmölnig ]
   * Removed unused patches
 
   [ Joël Krähemann ]
-  * initial *.symbols files
-  * added shlibs files
-  * updated symbols files
-  * remove unneeded shlibs files
-  * updated symbols files
-  * fixed initial symbols
-  * updated symbols
+  * Initial *.symbols files
 
   [ IOhannes m zmölnig ]
   * Stripped debian-revision from .symbols files
 
   [ Joël Krähemann ]
-  * added liboss4-salsa alternative to libasound2
-  * updated libags.symbols to 0.7.86
-  * updated libags-audio.symbols to 0.7.86
-  * removed unneeded dependency
+  * Added liboss4-salsa alternative to libasound2
+  * Removed unneeded dependency
 
   [ IOhannes m zmölnig ]
   * B-D on libjack-dev
-  * Enable ALSA-PCM only on linux
-
-  [ Joël Krähemann ]
-  * New upstream version 0.7.90
+  * Enabled ALSA-PCM only on linux
 
- -- Joël Krähemann   Fri, 02 Sep 
2016 13:15:49 +0200
+ -- IOhannes m zmölnig (Debian/GNU)   Wed, 19 Oct 2016 
11:40:23 +0200
 
 gsequencer (0.7.62-1) unstable; urgency=medium
 

Bug#841292: gcc-6: flexible array support broken

[Aurelien Jarno]

Package: gcc-6
Version: 6.2.0-7
Severity: serious

gcc-6 version 6.2.0-7 is not able to build the C++ part of the glibc
testsuite anymore, while version 6.2.0-6. was able to build it fine:

| In file included from ../include/gconv.h:1:0,
|  from ../sysdeps/unix/sysv/linux/_G_config.h:32,
|  from ../libio/libio.h:31,
|  from ../include/libio.h:4,
|  from ../libio/stdio.h:74,
|  from ../include/stdio.h:5,
|  from test-math-isinff.cc:22:
| ../iconv/gconv.h:142:50: error: flexible array member '__gconv_info::__data' 
not at end of 'struct _IO_codecvt'
|__extension__ struct __gconv_step_data __data __flexarr;
|   ^
| In file included from ../include/libio.h:4:0,
|  from ../libio/stdio.h:74,
|  from ../include/stdio.h:5,
|  from test-math-isinff.cc:22:
| ../libio/libio.h:211:14: note: next member '_G_iconv_t _IO_codecvt::__cd_out' 
declared here
|_IO_iconv_t __cd_out;
|   ^~~~
| ../libio/libio.h:187:8: note: in the definition of 'struct _IO_codecvt'
|  struct _IO_codecvt
| ^~~
| In file included from ../include/gconv.h:1:0,
|  from ../sysdeps/unix/sysv/linux/_G_config.h:32,
|  from ../libio/libio.h:31,
|  from ../include/libio.h:4,
|  from ../libio/stdio.h:74,
|  from ../include/stdio.h:5,
|  from test-math-isinff.cc:22:
| ../iconv/gconv.h:142:50: error: flexible array member '__gconv_info::__data' 
not at end of 'struct _IO_wide_data'
|__extension__ struct __gconv_step_data __data __flexarr;
|   ^
| In file included from ../include/libio.h:4:0,
|  from ../libio/stdio.h:74,
|  from ../include/stdio.h:5,
|  from test-math-isinff.cc:22:
| ../libio/libio.h:211:14: note: next member '_G_iconv_t _IO_codecvt::__cd_out' 
declared here
|_IO_iconv_t __cd_out;
|   ^~~~
| ../libio/libio.h:215:8: note: in the definition of 'struct _IO_wide_data'
|  struct _IO_wide_data
| ^

Full build logs available there:
https://buildd.debian.org/status/fetch.php?pkg=glibc=kfreebsd-amd64=2.24-5=1476834913
https://buildd.debian.org/status/fetch.php?pkg=glibc=powerpc=2.24-5=1476834176
https://buildd.debian.org/status/fetch.php?pkg=glibc=x32=2.24-5=1476845693

This seems related to the PR c++/71912 fix that went in this version.

I have attached an i386 preprocessed source file to demonstrate the
issue.

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

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


test-math-isinff.ii.gz
Description: application/gzip

Bug#831143: marked as done (hmat-oss: FTBFS with GCC 6: compression.cpp:717:25: error: there are no arguments to 'isnan' that depend on a template parameter, so a declaration of 'isnan' must be availa

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 00:24:44 +
with message-id 
and subject line Bug#831143: fixed in hmat-oss 1.2.0-1
has caused the Debian Bug report #831143,
regarding hmat-oss: FTBFS with GCC 6: compression.cpp:717:25: error: there are 
no arguments to 'isnan' that depend on a template parameter, so a declaration 
of 'isnan' must be available [-fpermissive]
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.)


-- 
831143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hmat-oss
Version: 1.0.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> /usr/bin/c++   -D_GNU_SOURCE -Dhmat_oss_EXPORTS -I/«PKGBUILDDIR»/include 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR»/src  -fopenmp  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -ffast-math -funsafe-math-optimizations -fopenmp -fPIC   
> -UNDEBUG -o CMakeFiles/hmat-oss.dir/src/compression.cpp.o -c 
> /«PKGBUILDDIR»/src/compression.cpp
> /«PKGBUILDDIR»/src/compression.cpp: In function 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*)':
> /«PKGBUILDDIR»/src/compression.cpp:717:25: error: there are no arguments to 
> 'isnan' that depend on a template parameter, so a declaration of 'isnan' must 
> be available [-fpermissive]
>  if (isnan(approxNorm)) {
>  ^
> /«PKGBUILDDIR»/src/compression.cpp:717:25: note: (if you use '-fpermissive', 
> G++ will accept your code, but allowing the use of an undeclared name is 
> deprecated)
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = float; typename Types::dp = 
> double]':
> /«PKGBUILDDIR»/src/compression.cpp:786:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if (isnan(approxNorm)) {
>  ~^~~~
> /«PKGBUILDDIR»/src/compression.cpp:717:14: note: suggested alternative:
> In file included from /«PKGBUILDDIR»/src/compression.cpp:26:0:
> /usr/include/c++/6/cmath:655:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = double; typename Types::dp = 
> double]':
> /«PKGBUILDDIR»/src/compression.cpp:787:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if (isnan(approxNorm)) {
>  ~^~~~
> /«PKGBUILDDIR»/src/compression.cpp:717:14: note: suggested alternative:
> In file included from /«PKGBUILDDIR»/src/compression.cpp:26:0:
> /usr/include/c++/6/cmath:655:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = std::complex; typename 
> Types::dp = std::complex]':
> /«PKGBUILDDIR»/src/compression.cpp:788:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if (isnan(approxNorm)) {
>  ~^~~~
> /«PKGBUILDDIR»/src/compression.cpp:717:14: note: suggested alternative:
> In file included from /«PKGBUILDDIR»/src/compression.cpp:26:0:
> /usr/include/c++/6/cmath:655:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = std::complex; typename 
> Types::dp = std::complex]':
> /«PKGBUILDDIR»/src/compression.cpp:789:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if 

Bug#841373: mv: cannot stat 'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file or directory

[Trent W. Buck]

Package: pepperflashplugin-nonfree
Version: 1.8.1+deb8u1
Severity: critical

Install is currently failing.
Maybe the paths within the upstream deb have changed?

Here's what the postinst said:

Setting up pepperflashplugin-nonfree (1.8.1+deb8u1) ...
converted 
'http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_54.0.2840.59-1_amd64.deb'
 (ANSI_X3.4-1968) -> 
'http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_54.0.2840.59-1_amd64.deb'
 (UTF-8)
--2016-10-20 11:49:21--  
http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_54.0.2840.59-1_amd64.deb
Resolving proxy (proxy)... 203.7.155.12
Connecting to proxy (proxy)|203.7.155.12|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 45527232 (43M) [application/x-debian-package]
Saving to: 
'/tmp/pepperflashplugin-nonfree.LdNEpJHj9m/google-chrome-stable_54.0.2840.59-1_amd64.deb'

 0K .. .. .. .. ..  0%  156K 
4m44s
[...]
 44400K .. .. .. .. .. 99%  444K 0s
 44450K ..100% 38.8M=60s

2016-10-20 11:50:22 (739 KB/s) - 
'/tmp/pepperflashplugin-nonfree.LdNEpJHj9m/google-chrome-stable_54.0.2840.59-1_amd64.deb'
 saved [45527232/45527232]

mv: cannot stat 
'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file 
or directory
Setting up plymouth (0.9.0-9) ...


Because errors in the postinst's call to update-pepperflashplugin-nonfree 
aren't fatal,
my build scripts explicitly rerun it.  Here's the same problem:

# Work around https://bugs.debian.org/823005; also #31001
[[ -e $t/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so ]] ||
(   wget -O $t/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt 
https://dl.google.com/linux/linux_signing_key.pub
chroot $t update-pepperflashplugin-nonfree -ifq )

+ [[ -e live/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so ]]
+ wget -O live/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt 
https://dl.google.com/linux/linux_signing_key.pub
converted 'https://dl.google.com/linux/linux_signing_key.pub' 
(ANSI_X3.4-1968) -> 'https://dl.google.com/linux/linux_signing_key.pub' (UTF-8)
--2016-10-20 11:51:10--  https://dl.google.com/linux/linux_signing_key.pub
Resolving dl.google.com (dl.google.com)... 172.217.25.46, 
2404:6800:4006:807::200e
Connecting to dl.google.com (dl.google.com)|172.217.25.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5840 (5.7K) [application/octet-stream]
Saving to: 'live/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt'

 0K . 100% 
1.02M=0.005s

2016-10-20 11:51:12 (1.02 MB/s) - 
'live/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt' saved [5840/5840]

+ chroot live update-pepperflashplugin-nonfree -ifq
mv: cannot stat 
'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file 
or directory

When I look inside the deb myself, I don't see libpepflashplayer.so:

$ dpkg -c google-chrome-stable_54.0.2840.59-1_amd64.deb | grep -F .so
-rw-r--r-- root/root   7964784 2016-10-12 15:41 
./opt/google/chrome/libwidevinecdm.so
-rw-r--r-- root/root 71984 2016-10-12 15:41 
./opt/google/chrome/libwidevinecdmadapter.so

Bug#841341: bd "Bad substitution" if /bin/sh is not bash

[Paulo Henrique de Lima Santana]

Hi Gerardo,

Thanks! I'm fixing it.

Best regards,

-- 
Paulo Henrique de Lima Santana (phls)
Membro da Comunidade Curitiba Livre
Fone: +55 (41) 9198-1897
Site: http://www.phls.com.br
GNU/Linux user: 228719  GPG ID: 0443C450

Apoie a campanha pela igualdade de gênero #HeForShe (#ElesPorElas)  
http://www.heforshe.org/pt

Bug#841374: cf-python: FTBFS: dh: unable to load addon sphinxdoc

[Aaron M. Ucko]

Source: cf-python
Version: 1.3.2+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of cf-python in minimal environments geared towards building
only its architecture-dependent python-cf binary package (as on the
autobuilders) have been failing:

   fakeroot debian/rules clean
  dh clean  --with python2,sphinxdoc --buildsystem=pybuild
  dh: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: [...]) at (eval 
12) line 2.
  BEGIN failed--compilation aborted at (eval 12) line 2.
  
  debian/rules:11: recipe for target 'clean' failed
  make: *** [clean] Error 2

Please either conditionalize the usage of --with-sphinxdoc
appropriately or move python-sphinx from Build-Depends-Indep to
Build-Depends.

Thanks!

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

Bug#831857: marked as done (libupnp: CVE-2016-6255: write files via POST)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 22:47:26 +
with message-id 
and subject line Bug#831857: fixed in libupnp 1:1.6.19+git20160116-1.1
has caused the Debian Bug report #831857,
regarding libupnp: CVE-2016-6255: write files via POST
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.)


-- 
831857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libupnp
Version: 1:1.6.17-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi

See http://www.openwall.com/lists/oss-security/2016/07/18/13 and
https://twitter.com/mjg59/status/755062278513319936 .

Proposed fix:
https://github.com/mjg59/pupnp-code/commit/be0a01bdb83395d9f3a5ea09c1308a4f1a972cbd

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libupnp
Source-Version: 1:1.6.19+git20160116-1.1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated libupnp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Oct 2016 21:03:51 +0100
Source: libupnp
Binary: libupnp6 libupnp6-dev libupnp-dev libupnp6-dbg libupnp6-doc
Architecture: source
Version: 1:1.6.19+git20160116-1.1
Distribution: unstable
Urgency: high
Maintainer: Nick Leverton 
Changed-By: James Cowgill 
Description:
 libupnp-dev - Portable SDK for UPnP Devices (development files)
 libupnp6   - Portable SDK for UPnP Devices, version 1.6 (shared libraries)
 libupnp6-dbg - debugging symbols for libupnp6
 libupnp6-dev - Portable SDK for UPnP Devices, version 1.6 (development files)
 libupnp6-doc - Documentation for the Portable SDK for UPnP Devices, version 1.6
Closes: 831857
Changes:
 libupnp (1:1.6.19+git20160116-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Don't allow unhandled POSTs to write to the filesystem by
 default (Closes: #831857) (CVE-2016-6255)
 Thanks to Matthew Garrett for the patch.
Checksums-Sha1:
 8f31c49dbce41876d8b24c2da80251ea01336680 2063 
libupnp_1.6.19+git20160116-1.1.dsc
 c1c0a4ec12985d7c05622de385089eb1b1499118 27556 
libupnp_1.6.19+git20160116-1.1.debian.tar.xz
Checksums-Sha256:
 f5f1ebe446db23082da1cfd02f0c7402c31e61e94758d332154282901f65fec6 2063 
libupnp_1.6.19+git20160116-1.1.dsc
 b046b9278c828dc2d6507dd470b8bf9ef81710b711748799d1812489df5672a7 27556 
libupnp_1.6.19+git20160116-1.1.debian.tar.xz
Files:
 a0befa3ea459b2448280b273709c81d8 2063 net optional 
libupnp_1.6.19+git20160116-1.1.dsc
 5ef9b6f217cd269cf186b68527ba4244 27556 net optional 
libupnp_1.6.19+git20160116-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYB9WHAAoJEMfxZ23qLQHv2lIQAKIiJkq6VIsfVMXs7KA+0cu3
oql7QnodK/loAHXx+4DTi6ccqxCAXe05eILRDESwxBHkE+xUZMZQ2zAqmIt9cJIs
FPYRDJ6n7nAxejj2cgTa4ZxNcJRqpaInF/1R3lwD5U4Bn5mBRrCrTtDAZhjZKJhs
Mo33hCHPqVRRY2wTul1p7Ypp9oYtw/Y8ri3po43WSVVDTVp8TDoVJZ2+3lCL80tr
5eDcmCXBqnhp8BkCwOg368UBUi/fqfFj4CNnQ95P0V2RBD6jPZC35Ge5L1Yfi5dh
oXZBWYDqwRaLwCO1pH1PFpLKWrNAPNWW/N29yXhYHp69b2WRKB+YoBKx5qCv2M6C
OG0H6lEyvPyR3ot3uexlf2l/I5zzusQ50UCcQYGEKNlJPNYPgIaeU+bSP+KjywEQ
e/kUgPOHj2kLd1eqyerBGBIjOpt6GJyKoTCgDlOF15VXj2LnS2QPRgvDVAjvSK1P
OhzqkmIwa3hva1P92wJeTsQrCtBOUIocrSzAWXkZYKNX52JHMfziHbBHxb1FZ+4N
KwM52FJFujdZJ2yYe4RHjldtmH7jJudcnzOQpiUZCukBx35hxVnsm7oUtFWhdCXa
Gp81QE/Z/Bn5T9WyCDbVw/DUUdCf29WWiW4MO/bcJ/r1XuV2X2FE1PFdeGjVBGnd
j20rlFVcmlff870I1PJo
=b/rE
-END PGP SIGNATURE End Message ---

Processed: tagging 831097

[Debian Bug Tracking System]

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

> tags 831097 + pending
Bug #831097 [src:eclipse-pydev] eclipse-pydev: FTBFS with GCC 6: 
plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:237:25:
 error: expected initializer before 'pydevdTracingMod'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#813419: marked as done (eclipse-egit: FTBFS: generateScript: Some inter-plug-in dependencies have not been satisfied.)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 22:27:57 +
with message-id 
and subject line Bug#813419: fixed in eclipse-egit 3.7.0-2
has caused the Debian Bug report #813419,
regarding eclipse-egit: FTBFS: generateScript: Some inter-plug-in dependencies 
have not been satisfied.
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.)


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

eclipse-egit fails to build from source in unstable/amd64:

  [..]
  
  init:
  
  generateScript:
  [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
  [eclipse.buildScript] Bundle org.eclipse.egit.mylyn.ui.test:
  [eclipse.buildScript] Host plug-in org.eclipse.egit.mylyn.ui_0.0.0 
has not been found.
  [eclipse.buildScript] Missing required plug-in 
org.apache.log4j_[1.0.0,2.0.0).
  [eclipse.buildScript] Missing required plug-in 
org.hamcrest_[1.1.0,2.0.0).
  [eclipse.buildScript] Bundle org.eclipse.egit.core:
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api.errors_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.diff_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.dircache_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.errors_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.events_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.internal.storage.file_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.lib_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.merge_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.patch_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.revwalk_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.revwalk.filter_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.storage.file_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.submodule_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.transport_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.treewalk_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.treewalk.filter_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.util_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.util.io_[3.7.0,3.8.0).
  [eclipse.buildScript] Bundle org.eclipse.egit.ui.test:
  [eclipse.buildScript] Host plug-in org.eclipse.egit.ui_0.0.0 has not 
been found.
  [eclipse.buildScript] Missing required plug-in 
org.apache.log4j_[1.0.0,2.0.0).
  [eclipse.buildScript] Missing required plug-in 
org.hamcrest_[1.1.0,2.0.0).
  [eclipse.buildScript] Missing required plug-in 
org.mockito_[1.8.0,1.9.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.egit.core.test_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api.errors_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.junit_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.junit.http_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.lib_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.revwalk_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.storage.file_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.transport_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied 

Bug#817880: marked as done (eclipse-cdt: FTBFS: [javac] 209 problems (1 error, 208 warnings))

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 22:27:45 +
with message-id 
and subject line Bug#817880: fixed in eclipse-cdt 8.6.0-2
has caused the Debian Bug report #817880,
regarding eclipse-cdt: FTBFS: [javac] 209 problems (1 error, 208 warnings)
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.)


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

eclipse-cdt fails to build from source in unstable/amd64:

  [..]

  [javac] 206. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/CygPath.java
 (at line 20)
  [javac]   import org.eclipse.cdt.internal.core.Cygwin;
  [javac]  
  [javac] The import org.eclipse.cdt.internal.core.Cygwin is never used
  [javac] --
  [javac] --
  [javac] 207. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/EFSExtensionManager.java
 (at line 23)
  [javac]   import org.eclipse.core.runtime.Path;
  [javac]  ^
  [javac] The import org.eclipse.core.runtime.Path is never used
  [javac] --
  [javac] --
  [javac] 208. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/envvar/StorableEnvironment.java
 (at line 22)
  [javac]   import 
org.eclipse.cdt.utils.envvar.StorableEnvironmentLoader.ISerializeInfo;
  [javac]  
^
  [javac] The import 
org.eclipse.cdt.utils.envvar.StorableEnvironmentLoader.ISerializeInfo is never 
used
  [javac] --
  [javac] --
  [javac] 209. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/envvar/StorableEnvironmentLoader.java
 (at line 36)
  [javac]   import org.eclipse.core.runtime.preferences.IEclipsePreferences;
  [javac]  
  [javac] The import 
org.eclipse.core.runtime.preferences.IEclipsePreferences is never used
  [javac] --
  [javac] 209 problems (1 error, 208 warnings)
  [javac] Compilation failed. Compiler errors are available in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/@dot.log
  
  BUILD FAILED
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:36:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:105:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:118:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:123:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/build/features/org.eclipse.cdt.platform/build.xml:65:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/build/features/org.eclipse.cdt.platform/build.xml:20:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/build.xml:213:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/build.xml:119:
 Compile failed; see the compiler error output for details.
  
  Total time: 24 seconds
  An error has occurred. 

Processed: affects and retitle

[Debian Bug Tracking System]

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

> affects 841197 
> src:activemq,src:activemq-activeio,src:activemq-protobuf,src:animal-sniffer,src:annotation-indexer,src:async-http-client,src:checkstyle,src:jacoco,src:jboss-logmanager,src:jboss-modules,src:junit4,src:libhibernate3-java,src:maven-jar-plugin,src:openjpa,src:wagon
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Added indication that 841197 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
Added indication that 841296 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
Added indication that 841362 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
Added indication that 841363 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
> retitle 841197 maven-enforcer: makes several packages to FTBFS with "Plugin 
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
> dependencies could not be resolved"
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
> thanks
Stopping processing here.

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

Bug#841362: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
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.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:activemq-protobuf
Version: 1.1-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibactivemq-protobuf-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -O--buildsystem=maven
/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
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] 

[... snipped ...]

[WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-release-plugin:2.3.2: Plugin 
org.apache.maven.plugins:maven-release-plugin:2.3.2 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 has not been downloaded 
from it before.
[INFO] 
[INFO] 
[INFO] Building ActiveMQ Protocol Buffers POM 1.1
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
from it before.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could 
not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) 
in offline mode and the artifact 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 

Bug#841197: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
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.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libhibernate3-java
Version: 3.6.10.Final-5
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibhibernate3-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -Rf debian/maven-repo/org/hibernate/hibernate
rm -Rf debian/maven-repo/org/hibernate/hibernate-parent

[... snipped ...]

[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
from it before.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could 
not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) 
in offline mode and the artifact 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from 
it before.
[INFO] 
[INFO] 
[INFO] Building Hibernate Core Parent POM 3.6.10.Final
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping Hibernate Core Aggregator
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Hibernate Core Parent POM .. FAILURE [  0.010 s]
[INFO] Hibernate Core . SKIPPED
[INFO] Hibernate Testing .. SKIPPED
[INFO] Hibernate Testsuite  SKIPPED
[INFO] Hibernate Ehcache Integration .. SKIPPED
[INFO] Hibernate OSCache Integration .. SKIPPED
[INFO] Hibernate SwarmCache Integration ... SKIPPED
[INFO] Hibernate C3P0 ConnectionProvider .. SKIPPED
[INFO] Hibernate Proxool ConnectionProvider ... SKIPPED
[INFO] Hibernate JDBC3-JdbcSupport Testing  SKIPPED
[INFO] Hibernate Entity Manager ... SKIPPED
[INFO] Hibernate JDBC4-JdbcSupport Testing  SKIPPED
[INFO] Hibernate Core Aggregator .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 

Bug#841363: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
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.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:junit4
Version: 4.12-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -pjunit4 --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -O--buildsystem=maven
/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
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping JUnit
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 

Bug#841296: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
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.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openjpa
Version: 2.4.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibopenjpa-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- install
/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
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
-Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

[INFO] Replacing /<>/openjpa/target/openjpa-2.4.0.jar with 
/<>/openjpa/target/openjpa-2.4.0-shaded.jar
[INFO] Dependency-reduced POM written at: 
/<>/openjpa/dependency-reduced-pom.xml
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ openjpa ---
[INFO] Installing /<>/openjpa/target/openjpa-2.4.0.jar to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Installing /<>/openjpa/dependency-reduced-pom.xml to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.pom
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.4:install (default-install) @ openjpa ---
[INFO] Writing OBR metadata
[INFO] Installing org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] 
[INFO] Building OpenJPA Parent POM 2.4.0
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] OpenJPA Utilities Library .. SUCCESS [  8.801 s]
[INFO] OpenJPA Kernel . SUCCESS [ 12.904 s]
[INFO] OpenJPA JDBC ... SUCCESS [  7.667 s]
[INFO] OpenJPA Persistence  SUCCESS [  4.218 s]
[INFO] OpenJPA Persistence JDBC ... SUCCESS [  1.028 s]
[INFO] OpenJPA XML Store .. SUCCESS [  0.481 s]
[INFO] OpenJPA Slice .. SUCCESS [  0.709 s]
[INFO] OpenJPA JEST ... SUCCESS [  0.609 s]
[INFO] OpenJPA Aggregate Jar .. SUCCESS [  6.807 s]
[INFO] OpenJPA Parent POM . FAILURE [  0.007 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 44.824 s
[INFO] Finished at: 2016-10-19T13:58:12+02:00
[INFO] Final 

Bug#840177: marked as done (qconf: FTBFS: mkdir: cannot create directory '/usr/share/qconf/': Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 01:29:17 +
with message-id 
and subject line Bug#840177: fixed in qconf 2.1-1
has caused the Debian Bug report #840177,
regarding qconf: FTBFS: mkdir: cannot create directory '/usr/share/qconf/': 
Permission denied
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.)


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

qconf fails to build from source in unstable/amd64:

  [..]

  Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-xml:amd64.
  Preparing to unpack .../03-libqt4-xml_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-xml:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqtdbus4:amd64.
  Preparing to unpack .../04-libqtdbus4_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqtdbus4:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package qtchooser.
  Preparing to unpack .../05-qtchooser_58-gfab25f1-1_amd64.deb ...
  Unpacking qtchooser (58-gfab25f1-1) ...
  Selecting previously unselected package qdbus.
  Preparing to unpack .../06-qdbus_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking qdbus (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-dbus:amd64.
  Preparing to unpack .../07-libqt4-dbus_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-dbus:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-network:amd64.
  Preparing to unpack .../08-libqt4-network_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-network:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-script:amd64.
  Preparing to unpack .../09-libqt4-script_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-script:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-sql:amd64.
  Preparing to unpack .../10-libqt4-sql_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-sql:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-xmlpatterns:amd64.
  Preparing to unpack .../11-libqt4-xmlpatterns_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libpng16-16:amd64.
  Preparing to unpack .../12-libpng16-16_1.6.25-1_amd64.deb ...
  Unpacking libpng16-16:amd64 (1.6.25-1) ...
  Selecting previously unselected package libfreetype6:amd64.
  Preparing to unpack .../13-libfreetype6_2.6.3-3+b1_amd64.deb ...
  Unpacking libfreetype6:amd64 (2.6.3-3+b1) ...
  Selecting previously unselected package ucf.
  Preparing to unpack .../14-ucf_3.0036_all.deb ...
  Moving old data out of the way
  Unpacking ucf (3.0036) ...
  Selecting previously unselected package fonts-dejavu-core.
  Preparing to unpack .../15-fonts-dejavu-core_2.37-1_all.deb ...
  Unpacking fonts-dejavu-core (2.37-1) ...
  Selecting previously unselected package fontconfig-config.
  Preparing to unpack .../16-fontconfig-config_2.11.0-6.7_all.deb ...
  Unpacking fontconfig-config (2.11.0-6.7) ...
  Selecting previously unselected package libfontconfig1:amd64.
  Preparing to unpack .../17-libfontconfig1_2.11.0-6.7_amd64.deb ...
  Unpacking libfontconfig1:amd64 (2.11.0-6.7) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../18-fontconfig_2.11.0-6.7_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.7) ...
  Selecting previously unselected package libxau6:amd64.
  Preparing to unpack .../19-libxau6_1%3a1.0.8-1_amd64.deb ...
  Unpacking libxau6:amd64 (1:1.0.8-1) ...
  Selecting previously unselected package x11-common.
  Preparing to unpack .../20-x11-common_1%3a7.7+16_all.deb ...
  Unpacking x11-common (1:7.7+16) ...
  Selecting previously unselected package libice6:amd64.
  Preparing to unpack .../21-libice6_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../22-libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libxdmcp6:amd64.
  Preparing to unpack .../23-libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
  Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Selecting previously unselected package libxcb1:amd64.
  Preparing to unpack .../24-libxcb1_1.12-1_amd64.deb ...
  

Processed: tagging 808485

[Debian Bug Tracking System]

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

> tags 808485 + help
Bug #808485 [src:eclipse-pydev] eclipse-pydev: FTBFS: Missing required plug-in 
org.python_0.0.0.
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: tagging 809566

[Debian Bug Tracking System]

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

> tags 809566 + help
Bug #809566 [src:eclipse-mylyn] eclipse-mylyn: FTBFS: Unsatisfied import 
package javax.mail_0.0.0.
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#789988: marked as done (FTBFS: The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 00:21:55 +
with message-id 
and subject line Bug#789988: fixed in eclipse-mylyn-tasks-github 3.3.0-2
has caused the Debian Bug report #789988,
regarding FTBFS: The import org.eclipse.egit.ui.internal.FilteredCheckboxTree 
cannot be resolved
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.)


-- 
789988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eclipse-mylyn-tasks-github
Version: 3.3.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The package fails to build, probably because egit has changed:

@dot:
[mkdir] Created dir: 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot
[javac] Compiling 50 source files to 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot



[javac] 29. ERROR in 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java
 (at line 27)
[javac] import org.eclipse.egit.ui.internal.FilteredCheckboxTree;
[javac]^
[javac] The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot 
be resolved
[javac] --
[javac] 30. ERROR in 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java
 (at line 184)
[javac] private FilteredCheckboxTree tree;
[javac] 
[javac] FilteredCheckboxTree cannot be resolved to a type

etc.

Full build log:
https://reproducible.debian.net/rb-pkg/testing/amd64/eclipse-mylyn-tasks-github.html

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

Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: eclipse-mylyn-tasks-github
Source-Version: 3.3.0-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
eclipse-mylyn-tasks-github package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Oct 2016 01:12:28 +0200
Source: eclipse-mylyn-tasks-github
Binary: eclipse-mylyn-tasks-github
Architecture: source all
Version: 3.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 eclipse-mylyn-tasks-github - Mylyn GitHub Connector
Closes: 789988
Changes:
 eclipse-mylyn-tasks-github (3.3.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure caused by eclipse-egit 3.7 (Closes: #789988)
   * Compile with javac instead of the Eclipse compiler
   * Standards-Version updated to 3.9.8
   * Use secure Vcs-* URLs
   * Fixed the watch file
Checksums-Sha1:
 305c7cce25c3bfa9ee4f3a4117892501412e3a6b 2205 
eclipse-mylyn-tasks-github_3.3.0-2.dsc
 6490eae4704dc39d03f9ed2931c0ff1f83734916 6468 
eclipse-mylyn-tasks-github_3.3.0-2.debian.tar.xz
 690520409ee270f116958a1c28e19e8f3d7f6f88 663810 
eclipse-mylyn-tasks-github_3.3.0-2_all.deb
Checksums-Sha256:
 e464a8dd979f8b69685c323131cb5e1e2da9ac995339af1e812ffdbc7d720d43 2205 
eclipse-mylyn-tasks-github_3.3.0-2.dsc
 668fa8ebfa477f18f4034551e0418bf5dd3f966575ff624505aaaf05295752ab 6468 
eclipse-mylyn-tasks-github_3.3.0-2.debian.tar.xz
 15da15e5f1a94a7aa8aae4a2a5915d0a20272ed05f95d843d6b8ad618712b58f 663810 

Bug#841274: [Pkg-javascript-devel] Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Sruthi Chandran]

control: reassign -1 node-once

Its caused by node-once missing dependency on node-wrappy
>   make[1]: Entering directory 
> '/home/lamby/temp/cdt.20161019103506.HYMipgpTLB.db.node-define-property/node-define-property-0.2.5'
>   mocha
>   module.js:327
>   throw err;
>   ^
>   
>   Error: Cannot find module 'wrappy'
>   at Function.Module._resolveFilename (module.js:325:15)
>   at Function.Module._load (module.js:276:25)
>   at Module.require (module.js:353:17)
>   at require (internal/module.js:12:17)
>   at Object. (/usr/lib/nodejs/once.js:1:76)
>   at Module._compile (module.js:409:26)
>   at Object.Module._extensions..js (module.js:416:10)
>   at Module.load (module.js:343:32)
>   at Function.Module._load (module.js:300:12)
>   at Module.require (module.js:353:17)
>   debian/rules:13: recipe for target 'override_dh_auto_test' failed
>   make[1]: *** [override_dh_auto_test] Error 1
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20161019103506.HYMipgpTLB.db.node-define-property/node-define-property-0.2.5'
>   debian/rules:8: recipe for target 'build' failed
>   make: *** [build] Error 2
>
>   […]
>

Processed: Re: [Pkg-javascript-devel] Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-once
Bug #841274 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841321 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841322 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841323 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841324 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841325 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841326 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841327 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841328 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841329 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841330 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841331 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841332 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841333 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841334 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841335 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841336 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841337 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841338 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Ignoring request to reassign bug #841274 to the same package
Ignoring request to reassign bug #841321 to the same package
Ignoring request to reassign bug #841322 to the same package
Ignoring request to reassign bug #841323 to the same package
Ignoring request to reassign bug #841324 to the same package
Ignoring request to reassign bug #841325 to the same package
Ignoring request to reassign bug #841326 to the same package
Ignoring request to reassign bug #841327 to the same package
Ignoring request to reassign bug #841328 to the same package
Ignoring request to reassign bug #841329 to the same package
Ignoring request to reassign bug #841330 to the same package
Ignoring request to reassign bug #841331 to the same package
Ignoring request to reassign bug #841332 to the same package
Ignoring request to reassign bug #841333 to the same package
Ignoring request to reassign bug #841334 to the same package
Ignoring request to reassign bug #841335 to the same package
Ignoring request to reassign bug #841336 to the same package
Ignoring request to reassign bug #841337 to the same package
Ignoring request to reassign bug #841338 to the same package

-- 
841274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841274
841321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841321
841322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841322
841323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841323
841324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841324
841325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841325
841326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841326
841327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841327
841328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841328
841329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841329
841330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841330
841331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841331
841332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841332
841333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841333
841334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841334
841335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841335
841336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841336
841337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841337
841338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 840575 is normal

[Debian Bug Tracking System]

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

> severity 840575 normal
Bug #840575 [sbuild] sbuild should Depends: gnupg (>= 2.1)
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#841281: marked as done (gkeyring: Missing dependency on python-gnomekeyring)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 05:00:06 +
with message-id 
and subject line Bug#841290: Removed package(s) from unstable
has caused the Debian Bug report #841281,
regarding gkeyring: Missing dependency on python-gnomekeyring
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.)


-- 
841281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gkeyring
Version: 0.4-1-gf4ce4c7-1
Severity: serious
Justification: Policy 7.2

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The package appears to be missing a dependency on python-gnomekeyring.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (550, 'testing-debug'), (550, 'testing'), (520, 
'unstable-debug'), (520, 'unstable'), (510, 'experimental-debug'), (510, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gkeyring depends on:
pn  python:any  

gkeyring recommends no packages.

gkeyring suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIvBAEBCAAZBQJYB0SIEhxzYW1Acm9ib3RzLm9yZy51awAKCRDSC0ICXNonufja
EACNfRWaUPARQ3P9aNAXsnvyLAf8Sq4H1Zop3XM6Ap1NyBJMz0nE6BV4Sk9PODSx
bL8nozWwvc3W7GMmnmQjDuOPxiUU0OHRxpY+u4RGNTRpBuZeu+6kCyUoGT1xGu3L
UNk6raVN2zrxjt+eChlwnCwlzyGBZV83eatTDw4qBL5UMv+Rgp58XctuBM44OI4G
ED187AlinugBIsAtyUvTkqpKLDc+93UPXz7X+zXWc2eZkmv4KrPWKLNk+a4PppGl
IZrIwH5cDSncQi+wPqh2YttrSG80HTJJ5OHNT6j4HcRy5beed33CGGPKRJrcGLO0
YPmd9S/RE9W9hPLRpbDXjqRrv6CwmVF8ovytf3tbHnZfEQ7Dv2krUU8TNySl8wwl
EDXR8n8vitEgLYQX40WPWHVxyBHwVKafqDw2YTZLs3v++XPEn5wY3sHFzPKv3w9m
yNcrKzDAfk0NA82+CUHbKyNUbTwHB7m0bynWZHDLRs/TgHGcc9xQDOD4NbJ4zpPJ
ZmtH7eOW9BogHjRBHcYZruBPebNFYgKgSacsPDHOprkTfFith16Y8INnw2MP2VZh
uM/daBsC7WHYfs1iYz5yP0RRvkxMy83NAUvi0fa5AjWtXRzgKrGwMOQbfQJkV54/
WhsS3zRCQXbHxCKhjVERghSRKgGsCvWmoFzS73yOMVssHw==
=97s1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.4-1-gf4ce4c7-1+rm

Dear submitter,

as the package gkeyring has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/841290

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#841162: marked as done (quagga: CVE-2016-1245: zebra: stack overrun in IPv6 RA receive code)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 12:47:08 +
with message-id 
and subject line Bug#841162: fixed in quagga 0.99.23.1-1+deb8u3
has caused the Debian Bug report #841162,
regarding quagga: CVE-2016-1245: zebra: stack overrun in IPv6 RA receive code
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.)


-- 
841162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quagga
Version: 0.99.23.1-1
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for quagga.

CVE-2016-1245[0]:
zebra: stack overrun in IPv6 RA receive code

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1245

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: quagga
Source-Version: 0.99.23.1-1+deb8u3

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated quagga package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Oct 2016 09:57:46 +0200
Source: quagga
Binary: quagga quagga-dbg quagga-doc
Architecture: all source
Version: 0.99.23.1-1+deb8u3
Distribution: jessie-security
Urgency: high
Maintainer: Christian Hammers 
Changed-By: Salvatore Bonaccorso 
Closes: 841162
Description: 
 quagga - BGP/OSPF/RIP routing daemon
 quagga-dbg - BGP/OSPF/RIP routing daemon (debug symbols)
 quagga-doc - documentation files for quagga
Changes:
 quagga (0.99.23.1-1+deb8u3) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * zebra: stack overrun in IPv6 RA receive code (CVE-2016-1245)
 (Closes: #841162)
Checksums-Sha1: 
 e7f5d6b52e0de9f8f3b7bbea99369fecd30bb2bd 2306 quagga_0.99.23.1-1+deb8u3.dsc
 30785870c5e43167a224d2bebd99dea548abd43a 39008 
quagga_0.99.23.1-1+deb8u3.debian.tar.xz
 03f5a9e83e26dee3bd918192d27d71efea6b392e 907704 
quagga-doc_0.99.23.1-1+deb8u3_all.deb
Checksums-Sha256: 
 23d4081f21041248e1ea9f7eee285356e3d761f9b553f2e013fd4a4db3da619e 2306 
quagga_0.99.23.1-1+deb8u3.dsc
 e7934bd1e41808f2097efe93478111ac3e32dcc71d34955f337a837a0573a1ad 39008 
quagga_0.99.23.1-1+deb8u3.debian.tar.xz
 b975c24798a3590dfa0e0484f508e0266e290e126d62523eed027ce58d0ae6b6 907704 
quagga-doc_0.99.23.1-1+deb8u3_all.deb
Files: 
 97a1bf8e25e716c561b3b69a21a9bd7c 2306 net optional 
quagga_0.99.23.1-1+deb8u3.dsc
 c3571ef57255f77c46a5d7bc75df1b5f 39008 net optional 
quagga_0.99.23.1-1+deb8u3.debian.tar.xz
 1180ebdd35c5e3d8ebbe6d65aa2c0dc7 907704 net optional 
quagga-doc_0.99.23.1-1+deb8u3_all.deb

-BEGIN PGP SIGNATURE-

iQKPBAEBCgB5BQJYBdmAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NjQ0NDA5ODA4QzE3MUUwNTUzMURERUUw
NTRDQjhGMzEzNDNDRjQ0EhxjYXJuaWxAZGViaWFuLm9yZwAKCRAFTLjzE0PPRK0t
EACezc2m0WnF0sCC+c3ilESIUWNJYK7LKKHbXNJj7oVtc5r5odgqL75cWCFGU/iw
KQh9KpKEGkGdTNimk7oAPsbfrdjhUw0WKhhBSSfwW0RcXijAYcJowf8uSUTgygJD
ixXYLorZkTZIwrt3ChVH6O9Jz4mjCsv5A5C2nWuk43bTFssDNcLkmUtthxse5MOU
Zv8apQGswZPHmTEuqGSjZq7GST/3ADLQW8ZN1gS6Afhu4MKXb9AlMETdiOt+CFvV
5RKum760ia9yI0n5qxVwA6tRgUV6073FLZL1R6P3DIk+cGMcNqM/c1uCCg8XLabC
frJALvKIjWQOJD6VbxpVG5yIdwz0LJpolj0vdra6EvwnyJPh0dnDSKWYVZsYLYkZ
ckuYXvgBX9sOluS/OB2zHyyDJHG28qO2PLbzwIc5kyduNBxfJOp3w04/PZKyAOBH
ict0glwsLBrtPGL4hXSm2/xha8VqAWpth4oTPzkWQul0j4+qOHFiM5SQ4Bx/ymcC
JtczghM8/RWZrRHQVAnVeoNVkAAAG15y7Lgiam3SDRZnH+deLSsX4jUBj6TMN3SF
tgIqp//osCvnYOK47ElgDaQ4TN3LGJOGGkRdSU0Qkj7IBt1gqHIWJiiBaBlf9/aa
mcX6RHzZ4wIFo8l6ILILdmL+wXLhmcqu+wuWCZudr1I4bw==
=07hM
-END PGP SIGNATURE End Message ---

Bug#841296: openjpa: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:openjpa
Version: 2.4.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibopenjpa-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- install
/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
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
-Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

[INFO] Replacing /<>/openjpa/target/openjpa-2.4.0.jar with 
/<>/openjpa/target/openjpa-2.4.0-shaded.jar
[INFO] Dependency-reduced POM written at: 
/<>/openjpa/dependency-reduced-pom.xml
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ openjpa ---
[INFO] Installing /<>/openjpa/target/openjpa-2.4.0.jar to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Installing /<>/openjpa/dependency-reduced-pom.xml to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.pom
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.4:install (default-install) @ openjpa ---
[INFO] Writing OBR metadata
[INFO] Installing org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] 
[INFO] Building OpenJPA Parent POM 2.4.0
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] OpenJPA Utilities Library .. SUCCESS [  8.801 s]
[INFO] OpenJPA Kernel . SUCCESS [ 12.904 s]
[INFO] OpenJPA JDBC ... SUCCESS [  7.667 s]
[INFO] OpenJPA Persistence  SUCCESS [  4.218 s]
[INFO] OpenJPA Persistence JDBC ... SUCCESS [  1.028 s]
[INFO] OpenJPA XML Store .. SUCCESS [  0.481 s]
[INFO] OpenJPA Slice .. SUCCESS [  0.709 s]
[INFO] OpenJPA JEST ... SUCCESS [  0.609 s]
[INFO] OpenJPA Aggregate Jar .. SUCCESS [  6.807 s]
[INFO] OpenJPA Parent POM . FAILURE [  0.007 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 44.824 s
[INFO] Finished at: 2016-10-19T13:58:12+02:00
[INFO] Final Memory: 53M/161M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1: 1 problem was 
encountered while building the effective model for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[ERROR] [ERROR] 'dependencies.dependency.version' for 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar is missing. @
[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/PluginResolutionException
dh_auto_build: 

Processed: tag as pending

[Debian Bug Tracking System]

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

> tag 839791 pending
Bug #839791 [src:qtcreator] qtcreator: builds with clang support on armel
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841312: cacti-spine: FTBFS: configure: error: MySQL libraries not found

[Chris Lamb]

Source: cacti-spine
Version: 0.8.8h-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,

cacti-spine fails to build from source in unstable/amd64:

  […]

  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Selecting previously unselected package libmysqlclient-dev.
  Preparing to unpack .../03-libmysqlclient-dev_5.7.15-1_amd64.deb ...
  Unpacking libmysqlclient-dev (5.7.15-1) ...
  Selecting previously unselected package libpci3:amd64.
  Preparing to unpack .../04-libpci3_1%3a3.3.1-1.1_amd64.deb ...
  Unpacking libpci3:amd64 (1:3.3.1-1.1) ...
  Selecting previously unselected package libsensors4:amd64.
  Preparing to unpack .../05-libsensors4_1%3a3.4.0-3_amd64.deb ...
  Unpacking libsensors4:amd64 (1:3.4.0-3) ...
  Selecting previously unselected package libwrap0:amd64.
  Preparing to unpack .../06-libwrap0_7.6.q-25_amd64.deb ...
  Unpacking libwrap0:amd64 (7.6.q-25) ...
  Selecting previously unselected package libsnmp-base.
  Preparing to unpack .../07-libsnmp-base_5.7.3+dfsg-1.5_all.deb ...
  Unpacking libsnmp-base (5.7.3+dfsg-1.5) ...
  Selecting previously unselected package libsnmp30:amd64.
  Preparing to unpack .../08-libsnmp30_5.7.3+dfsg-1.5+b1_amd64.deb ...
  Unpacking libsnmp30:amd64 (5.7.3+dfsg-1.5+b1) ...
  Selecting previously unselected package libwrap0-dev:amd64.
  Preparing to unpack .../09-libwrap0-dev_7.6.q-25_amd64.deb ...
  Unpacking libwrap0-dev:amd64 (7.6.q-25) ...
  Selecting previously unselected package libssl-dev:amd64.
  Preparing to unpack .../10-libssl-dev_1.0.2j-1_amd64.deb ...
  Unpacking libssl-dev:amd64 (1.0.2j-1) ...
  Selecting previously unselected package libsensors4-dev.
  Preparing to unpack .../11-libsensors4-dev_1%3a3.4.0-3_amd64.deb ...
  Unpacking libsensors4-dev (1:3.4.0-3) ...
  Selecting previously unselected package libudev-dev:amd64.
  Preparing to unpack .../12-libudev-dev_231-9_amd64.deb ...
  Unpacking libudev-dev:amd64 (231-9) ...
  Selecting previously unselected package libpci-dev.
  Preparing to unpack .../13-libpci-dev_1%3a3.3.1-1.1_amd64.deb ...
  Unpacking libpci-dev (1:3.3.1-1.1) ...
  Selecting previously unselected package libsnmp-dev.
  Preparing to unpack .../14-libsnmp-dev_5.7.3+dfsg-1.5+b1_amd64.deb ...
  Unpacking libsnmp-dev (5.7.3+dfsg-1.5+b1) ...
  Selecting previously unselected package help2man.
  Preparing to unpack .../15-help2man_1.47.4_amd64.deb ...
  Unpacking help2man (1.47.4) ...
  Setting up mysql-common (5.8+1.0.0) ...
  update-alternatives: using /etc/mysql/my.cnf.fallback to provide 
/etc/mysql/my.cnf (my.cnf) in auto mode
  Processing triggers for libc-bin (2.24-5) ...
  Setting up help2man (1.47.4) ...
  Setting up libsensors4:amd64 (1:3.4.0-3) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libmysqlclient20:amd64 (5.7.15-1) ...
  Setting up libpci3:amd64 (1:3.3.1-1.1) ...
  Setting up libudev-dev:amd64 (231-9) ...
  Setting up libwrap0:amd64 (7.6.q-25) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libsnmp-base (5.7.3+dfsg-1.5) ...
  Setting up libsnmp30:amd64 (5.7.3+dfsg-1.5+b1) ...
  Setting up libmysqlclient-dev (5.7.15-1) ...
  Setting up libwrap0-dev:amd64 (7.6.q-25) ...
  Setting up libssl-dev:amd64 (1.0.2j-1) ...
  Setting up libsensors4-dev (1:3.4.0-3) ...
  Setting up libpci-dev (1:3.3.1-1.1) ...
  Setting up libsnmp-dev (5.7.3+dfsg-1.5+b1) ...
  Setting up cacti-spine-build-deps (0.8.8h-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=988541d05689
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20161019163212.J91Hw9gpQ6.db.cacti-spine/cacti-spine-0.8.8h
  OLDPWD=/home/lamby/temp/cdt.20161019163212.J91Hw9gpQ6.db.cacti-spine
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building cacti-spine 0.8.8h-1 on amd64 
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: 

Bug#841012: marked as done (swi-prolog: FTBFS on armel/armhf: segmentation fault during the tests)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 17:19:05 +0500
with message-id <516fc1c2-6ca7-199a-6544-07b618bbd...@riseup.net>
and subject line Closing this bug
has caused the Debian Bug report #841012,
regarding swi-prolog: FTBFS on armel/armhf: segmentation fault during the tests
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.)


-- 
841012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swi-prolog
Version: 7.2.3+dfsg-1
Severity: serious

Your package failed to build on armel/armhf during a rebuild:

make[3]: Leaving directory 
'/«BUILDDIR»/swi-prolog-7.2.3+dfsg/packages/jpl/src/java'
if [ -r jpltest.jar ]; then \
  
LD_LIBRARY_PATH="/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/server:/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm"
 ../swipl.sh  -q -f test_jpl.pl -g run_tests,halt -t 'halt(1)' ; \
else \
  echo "No jpltest.jar; maybe junit is not installed?" ; \
fi
JUNIT=/usr/share/java/junit.jar JAVA=java 
JAVA_PRELOAD=/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/libjsig.so 
./test-java.sh
Welcome to SWI-Prolog (Multi-threaded, 32 bits, Version 7.2.3)
Copyright (c) 1990-2015 University of Amsterdam, VU Amsterdam
SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions.
Please visit http://www.swi-prolog.org for details.

For help, use ?- help(Topic). or ?- apropos(Word).


% halt
Segmentation fault

Full logs at https://buildd.debian.org/status/package.php?p=swi-prolog

Emilio

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

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



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

Bug#841012: swi-prolog: FTBFS on armel/armhf: segmentation fault during the tests

[Lev Lamberov]

17.10.2016 02:00, Emilio Pozuelo Monfort пишет:
> make[3]: Leaving directory 
> '/«BUILDDIR»/swi-prolog-7.2.3+dfsg/packages/jpl/src/java'
> if [ -r jpltest.jar ]; then \
> 
> LD_LIBRARY_PATH="/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/server:/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm"
>  ../swipl.sh  -q -f test_jpl.pl -g run_tests,halt -t 'halt(1)' ; \
>   else \
> echo "No jpltest.jar; maybe junit is not installed?" ; \
>   fi
> JUNIT=/usr/share/java/junit.jar JAVA=java 
> JAVA_PRELOAD=/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/libjsig.so 
> ./test-java.sh
> Welcome to SWI-Prolog (Multi-threaded, 32 bits, Version 7.2.3)
> Copyright (c) 1990-2015 University of Amsterdam, VU Amsterdam
> SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software,
> and you are welcome to redistribute it under certain conditions.
> Please visit http://www.swi-prolog.org for details.
>
> For help, use ?- help(Topic). or ?- apropos(Word).
>
>
> % halt
> Segmentation fault

Disables java support for armel and armhf. Moreover, found out that
upstream do not support 32-bit architectures that do not implement
64-bit atomic increment/decrement operations. Upstream developers are
not sure that it should be fixed at all. Probably, they will drop
(whole) support of 32-bit platforms.

Cheers!
Lev



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#840329: taglib-extras: FTBFS: CMake Error at cmake/modules/FindTaglib.cmake:132 (message): Could not find Taglib

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #840329 [src:taglib-extras] taglib-extras: FTBFS: CMake Error at 
cmake/modules/FindTaglib.cmake:132 (message):   Could not find Taglib
Added tag(s) patch.

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

Processed: severity of 841289 is important

[Debian Bug Tracking System]

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

> severity 841289 important
Bug #841289 [src:linux] [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg 
[2507], reason: Engine(s) hung, action: reset
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#723964: marked as done (devtodo: FTBFS: required file './compile' not found)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 13:19:26 +
with message-id 
and subject line Bug#723964: fixed in devtodo 0.1.20-6.1
has caused the Debian Bug report #723964,
regarding devtodo: FTBFS: required file './compile' not found
to be marked as done.

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

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


-- 
723964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: devtodo
Version: 0.1.20-6
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
ln -sf /usr/share/misc/config.sub config.sub
ln -sf /usr/share/misc/config.guess config.guess
autoreconf
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader: 
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template 
without
autoheader: WARNING: `acconfig.h':
autoheader: 
autoheader: WARNING:   AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader: 
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:3: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.  For more info, see:
configure.in:3: 
http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:12: error: required file './compile' not found
configure.in:12:   'automake --add-missing' can install 'compile'
Makefile.am:2: warning: shell ls contrib/*: non-POSIX variable name
Makefile.am:2: (probably a GNU make extension)
doc/Makefile.am:10: warning: addprefix $(DESTDIR: non-POSIX variable name
doc/Makefile.am:10: (probably a GNU make extension)
doc/Makefile.am:10: warning: addsuffix .1, $(manlinks: non-POSIX variable name
doc/Makefile.am:10: (probably a GNU make extension)
src/Makefile.am:20: warning: addprefix $(DESTDIR: non-POSIX variable name
src/Makefile.am:20: (probably a GNU make extension)
src/Makefile.am:7: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
'*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
autoreconf: automake failed with exit status: 1
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: devtodo
Source-Version: 0.1.20-6.1

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

Debian distribution maintenance software
pp.
Fernando Seiti Furusato  (supplier of updated 
devtodo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 14 Sep 2016 12:21:03 -0400
Source: devtodo
Binary: devtodo
Architecture: source
Version: 0.1.20-6.1
Distribution: unstable
Urgency: medium
Maintainer: Ryan Niebur 
Changed-By: Fernando Seiti Furusato 
Description:
 devtodo- hierarchical, prioritised todo list manager
Closes: 723964 779551
Changes:
 devtodo (0.1.20-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: added dh-autoreconf as build-dep, removed its
 dependencies and added libtool-bin to fix ftbfs. (Closes: #779551, #723964)
   * debian/rules
 - added usage of dh-autoreconf
 - expanded dh clean to include dh_autoreconf_clean before dh_clean
Checksums-Sha1:
 fc2feb2abbaa6fe307fdfaa3064a98d3f0974bf0 1923 devtodo_0.1.20-6.1.dsc
 4aab0f24ffdd635557b7f61d1b83e39892f344f6 17180 devtodo_0.1.20-6.1.debian.tar.xz
Checksums-Sha256:
 465e2679bcb714ff2671637f7e94547a223c2e240da3c818140cb283aa90d00e 1923 

Bug#841300: arcboot: remove this package?

[James Cowgill]

Source: arcboot
Version: 0.3.15
Severity: serious
Tags: sid stretch

Hi,

Given that stretch will drop support for pre-mips32r2 processors
including the SGI IP22 and IP32, should this package be removed?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#840329: taglib-extras: FTBFS: CMake Error at cmake/modules/FindTaglib.cmake:132 (message): Could not find Taglib

[Stuart Prescott]

Control: tags -1 + patch

The existing FindTaglib.cmake in this package uses the STRLESS function for 
lexical comparison of the version strings rather than using VERSION_LESS. It 
thus (wrongly) concludes that the minimum version requirement of 1.6 was not 
met when it finds version 1.11 installed.

-- TagLib version not found: version searched :1.6, found 1.11
CMake Error at cmake/modules/FindTaglib.cmake:132 (message):
  Could not find Taglib

The attached patch corrects this test allowing the package to build 
successfully.

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7Description: Fix version comparison for finding taglib

Existing cmake code doesn't do the min version comparison correctly.

(Closes: #840329)

--- a/cmake/modules/FindTaglib.cmake
+++ b/cmake/modules/FindTaglib.cmake
@@ -29,10 +29,10 @@
 
   exec_program(${TAGLIBCONFIG_EXECUTABLE} ARGS --version RETURN_VALUE _return_VALUE OUTPUT_VARIABLE TAGLIB_VERSION)
 
-  if(TAGLIB_VERSION STRLESS "${TAGLIB_MIN_VERSION}")
+  if(TAGLIB_VERSION VERSION_LESS "${TAGLIB_MIN_VERSION}")
  message(STATUS "TagLib version not found: version searched :${TAGLIB_MIN_VERSION}, found ${TAGLIB_VERSION}")
  set(TAGLIB_FOUND FALSE)
-  else(TAGLIB_VERSION STRLESS "${TAGLIB_MIN_VERSION}")
+  else(TAGLIB_VERSION VERSION_LESS "${TAGLIB_MIN_VERSION}")
 
  exec_program(${TAGLIBCONFIG_EXECUTABLE} ARGS --libs RETURN_VALUE _return_VALUE OUTPUT_VARIABLE TAGLIB_LIBRARIES)
 
@@ -42,7 +42,7 @@
 set(TAGLIB_FOUND TRUE)
  endif(TAGLIB_LIBRARIES AND TAGLIB_CFLAGS)
  string(REGEX REPLACE " *-I" ";" TAGLIB_INCLUDES "${TAGLIB_CFLAGS}")
-  endif(TAGLIB_VERSION STRLESS "${TAGLIB_MIN_VERSION}") 
+  endif(TAGLIB_VERSION VERSION_LESS "${TAGLIB_MIN_VERSION}")
   mark_as_advanced(TAGLIB_CFLAGS TAGLIB_LIBRARIES TAGLIB_INCLUDES)
 
 else(TAGLIBCONFIG_EXECUTABLE)

Bug#841285: freemat: FTBFS (cannot find -lclangTidyReadabilityModule)

[Santiago Vila]

On Wed, 19 Oct 2016, Gianfranco Costamagna wrote:

> Hi, this is because of the llvm transition.
> We switched to unversioned llvm to avoid further issues on the next llvm 
> defaults
> bump.
> 
> In this case, it is true that it fails to build with llvm-3.6, and it is also 
> true that
> llvm-toolchain-3.6 has been removed from unstable/testing (soon), so the bug 
> for sure
> (if a bug is here), can't be serious in any case)

Ok, I could agree that freemat is probably not to be blamed for this.

But this is of course a bug, and it is of course serious, because
packages in testing *must* be buildable in testing (release policy).

So, the bug would be really something like this:

"llvm 3.8 is not the default llvm compiler in stretch yet"

which seems RC enough to me, because we have already packages in
testing requiring llvm 3.8 to be the default.

Simple question: Are there more packages like this one, which fail
to build when llvm 3.8 is not the default?

If not, I'm ok with you closing this one as you already did.

But if yes, it might be worth to reopen, reassign to release.debian.org
and start using "affects" to track all of them.

Thanks.

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[Chris Lamb]

Source: latex-cjk-japanese-wadalab
Version: 0.20050817-16
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,

latex-cjk-japanese-wadalab fails to build from source in unstable/amd64:

  […]

  Setting up libopenjp2-7:amd64 (2.1.2-1) ...
  Setting up libptexenc1:amd64 (2016.20160513.41080-7) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.1-1) ...
  Processing triggers for mime-support (3.60) ...
  Setting up libpng16-16:amd64 (1.6.25-2) ...
  Setting up liblcms2-2:amd64 (2.7-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up fonts-dejavu-core (2.37-1) ...
  Setting up poppler-data (0.4.7-7) ...
  Setting up libtiff5:amd64 (4.0.6-2) ...
  Setting up libnspr4:amd64 (2:4.12-6) ...
  Setting up ucf (3.0036) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libjbig2dec0:amd64 (0.13-3) ...
  Setting up libpixman-1-0:amd64 (0.34.0-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for systemd (231-9) ...
  Setting up libijs-0.35:amd64 (0.35-12) ...
  Setting up libpotrace0 (1.13-2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libzzip-0-13:amd64 (0.13.62-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up xdg-utils (1.1.1-1) ...
  Setting up libtexluajit2:amd64 (2016.20160513.41080-7) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libpaper1:amd64 (1.1.24+nmu4) ...
  
  Creating config file /etc/papersize with new version
  Setting up libpaper-utils (1.1.24+nmu4) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  Setting up libnss3:amd64 (2:3.26-2) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libxcb1:amd64 (1.12-1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-render0:amd64 (1.12-1) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.7-1+b1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-shm0:amd64 (1.12-1) ...
  Setting up libxpm4:amd64 (1:3.5.11-1+b1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libpoppler61:amd64 (0.44.0-3) ...
  Setting up libcups2:amd64 (2.2.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libcupsimage2:amd64 (2.2.1-1) ...
  Setting up libgs9:amd64 (9.19~dfsg-3) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up libxaw7:amd64 (2:1.0.13-1) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up texlive-binaries (2016.20160513.41080-7) ...
  update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin 
(xdvi.bin) in auto mode
  update-alternatives: using /usr/bin/bibtex.original to provide 
/usr/bin/bibtex (bibtex) in auto mode
  Processing triggers for tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  texlive-base is not ready, skipping fmtutil --all call
  Setting up texlive-base (2016.20161008-1) ...
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... 
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... 
  mktexlsr: Updating /var/lib/texmf/ls-R... 
  mktexlsr: Done.
  /usr/bin/tl-paper: setting paper size for dvips to a4.
  /usr/bin/tl-paper: setting paper size for dvipdfmx to a4.
  /usr/bin/tl-paper: setting paper size for xdvi to a4.
  /usr/bin/tl-paper: setting paper size for pdftex to a4.
  Processing triggers for tex-common (6.05) ...
  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
This may take some time... done.
  Setting up texlive-font-utils (2016.20161008-1) ...
  Setting up latex-cjk-japanese-wadalab-build-deps (0.20050817-16) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for systemd (231-9) ...
  
  
**
  ** Environment
  **
  
**
  
  

Processed: Re: Bug#841292: gcc-6: flexible array support broken

[Debian Bug Tracking System]

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

> forwarded 841292 https://gcc.gnu.org/PR78039
Bug #841292 [gcc-6] gcc-6: flexible array support broken
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR78039'.
> tags 841292 + upstream
Bug #841292 [gcc-6] gcc-6: flexible array support broken
Added tag(s) upstream.
> clone 841292 -1
Bug #841292 [gcc-6] gcc-6: flexible array support broken
Bug 841292 cloned as bug 841304
> reassign -1 glibc
Bug #841304 [gcc-6] gcc-6: flexible array support broken
Bug reassigned from package 'gcc-6' to 'glibc'.
No longer marked as found in versions gcc-6/6.2.0-7.
Ignoring request to alter fixed versions of bug #841304 to the same values 
previously set
> retitle -1 invalid code in glibc tests
Bug #841304 [glibc] gcc-6: flexible array support broken
Changed Bug title to 'invalid code in glibc tests' from 'gcc-6: flexible array 
support broken'.
> severity 841292 important
Bug #841292 [gcc-6] gcc-6: flexible array support broken
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#820965: marked as done ([regression]: net usersidlist: Could not malloc sid array Could not get the user/sid list)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 13:47:10 +
with message-id 
and subject line Bug#820965: fixed in samba 2:4.2.14+dfsg-0+deb8u1
has caused the Debian Bug report #820965,
regarding [regression]: net usersidlist: Could not malloc sid array Could not 
get the user/sid list
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.)


-- 
820965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-common-bin
Version: 2:4.2.10+dfsg-0+deb8u1
Severity: serious
File: /usr/bin/net

The upgrade of samba in the Debian security archive has caused an error
with net usersidlist, it is now unable to retrieve the user SID list:

$ sudo net usersidlist -d2
added interface bond0 ip=X.X.X.X bcast=X.X.X.255 netmask=255.255.255.0
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Could not malloc sid array
Could not get the user/sid list
return code = -1

-- System Information:
Debian Release: 8.4
  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 samba-common-bin depends on:
ii  libbsd00.7.0-2
ii  libc6  2.19-18+deb8u4
ii  libldap-2.4-2  2.4.40+dfsg-1+deb8u2
ii  libncurses55.9+20140913-1+b1
ii  libpopt0   1.16-10
ii  libreadline6   6.3-8+b3
ii  libtalloc2 2.1.2-0+deb8u1
ii  libtdb11.3.6-0+deb8u1
ii  libtevent0 0.9.25-0+deb8u1
ii  libtinfo5  5.9+20140913-1+b1
ii  libwbclient0   2:4.2.10+dfsg-0+deb8u1
ii  python 2.7.9-1
ii  python-samba   2:4.2.10+dfsg-0+deb8u1
pn  python2.7:any  
ii  samba-common   2:4.2.10+dfsg-0+deb8u1
ii  samba-libs 2:4.2.10+dfsg-0+deb8u1

samba-common-bin recommends no packages.

Versions of packages samba-common-bin suggests:
pn  heimdal-clients  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.2.14+dfsg-0+deb8u1

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Sep 2016 14:21:35 +
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev samba-doc 
python-samba samba-dsdb-modules samba-vfs-modules libpam-smbpass libsmbclient 
libsmbclient-dev winbind libpam-winbind libnss-winbind samba-dbg libwbclient0 
libwbclient-dev ctdb
Architecture: all amd64 source
Version: 2:4.2.14+dfsg-0+deb8u1
Distribution: jessie
Urgency: high
Maintainer: Debian Samba Maintainers 
Changed-By: Jelmer Vernooij 
Closes: 820965 824177 827141
Description: 
 ctdb   - clustered database to store temporary data
 libnss-winbind - Samba nameservice integration plugins
 libpam-smbpass - pluggable authentication module for Samba
 libpam-winbind - Windows domain authentication integration plugin
 libparse-pidl-perl - IDL compiler written in Perl
 libsmbclient-dev - development files for libsmbclient
 libsmbclient - shared library for communication with SMB/CIFS servers
 libwbclient0 - Samba winbind client library
 libwbclient-dev - Samba winbind client library - development files
 python-samba - Python bindings for Samba
 registry-tools - tools for viewing and manipulating the Windows registry
 samba-common-bin - Samba common files used by both the server and the client
 samba-common - common files used by both the Samba server and client
 samba-dbg  - Samba debugging symbols
 samba-dev  - tools for extending Samba
 

Bug#841302: ngraph-gtk: FTBFS on mips*: ngraph segfaults on testing

[Dejan Latinovic]

Package: ngraph-gtk
Version: 6.06.13-5.1
Severity: serious
Tags: sid, patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch


Package ngraph-gtk FTBFS for mips* on testing with an error:

> make[6]: Entering directory '/«PKGBUILDDIR»/doc/html/ja'
> cat object.html.in > object.html
> ../../../src/ngraph -i ../objlist.nsc >> object.html
> Unable to init server: Could not connect: Connection refused
> /bin/bash: line 1: 23170 Segmentation fault  ../../../src/ngraph -i 
> ../objlist.nsc >> object.html
> Makefile:750: recipe for target 'object.html' failed
> make[6]: *** [object.html] Error 139

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=ngraph-gtk=mipsel=6.06.13-5.1%2Bb2=1476151762


Back trace from gdb shows that segfault happens in  __GI__IO_wsetb, libc.so.6

Full back trace:
(gdb) bt
#0  __GI__IO_wsetb (f=0x76df0dbc <_IO_stdout_>, b=0x0, eb=0x0, a=0) at 
wgenops.c:105
#1  0x76cea24c in _IO_unbuffer_all () at genops.c:924
#2  _IO_cleanup () at genops.c:966
#3  0x76ca4eac in __run_exit_handlers (status=0, listp=0x76df03cc 
<__exit_funcs>, run_list_atexit=, run_dtors=) at 
exit.c:96
#4  0x76ca4f70 in __GI_exit (status=) at exit.c:105
#5  0x005051e8 in sysdone (obj=0x632988, inst=0x632ed0, rval=0x632ef0, argc=2, 
argv=0x646048) at osystem.c:171
#6  0x004a51c0 in delobj (obj=0x632988, delid=0) at object.c:2398
#7  0x00521e44 in cmdel (nshell=0x642d70, argc=2, argv=0x645f28) at 
shellcm.c:920
#8  0x0051b84c in cmdexec (nshell=0x642d70, cmdroot=0x6455d8, namedfunc=0) at 
shell.c:3906
#9  0x0051c610 in cmdexecute (nshell=0x642d70, cline=0x0) at shell.c:4115
#10 0x00501a64 in cmdshell (obj=0x631ab0, inst=0x642ca0, rval=0x642cc8, argc=3, 
argv=0x645638) at oshell.c:164
#11 0x004a6db0 in exeobj (obj=0x631ab0, vname=0x5ba400 "shell", id=0, argc=1, 
argv=0x7fff654c) at object.c:2794
#12 0x0040db10 in main (argc=3, argv=0x7fff6634) at main.c:1007


The reason for this behavior is using of version script during creation of 
ngraph executable.
Marking  _IO_stdin_used symbol as global solves this issue.

Similar problem was noticed in lua5.2 package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816059


The patch that solves this is attached.

Regards,
Dejan

--- ngraph-gtk-6.06.13.orig/src/ngraph_export.map
+++ ngraph-gtk-6.06.13/src/ngraph_export.map
@@ -1,5 +1,6 @@
 {
   global:
 ngraph_*;
+_IO_stdin_used;
   local: *;
 };

Processed: Re: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Debian Bug Tracking System]

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

> affects 841274 node-collection-visit node-component-emitter 
> node-copy-descriptor node-extend-shallow node-has-values node-isobject 
> node-map-visit node-repeat-element
Bug #841274 [src:node-define-property] node-define-property: FTBFS: Error: 
Cannot find module 'wrappy'
Added indication that 841274 affects node-collection-visit, 
node-component-emitter, node-copy-descriptor, node-extend-shallow, 
node-has-values, node-isobject, node-map-visit, and node-repeat-element
> thanks
Stopping processing here.

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

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Emmanuel Bourg]

Le 20/10/2016 à 00:06, Santiago Vila a écrit :

> You are absolutely right. Sorry for the duplicates.

No need to be sorry. Your reports and the reproducible build
notifications help us greatly to detect and fix the build issues
quickly, thanks a lot for your time.

Emmanuel Bourg

Bug#841322: node-component-emitter: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-component-emitter
Version: 1.2.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Skip upstream Makefile
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha --require should --reporter spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841325: node-filename-regex: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-filename-regex
Version: 2.0.0-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841327: node-glob-parent: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-glob-parent
Version: 3.0.0-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841323: node-copy-descriptor: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-copy-descriptor
Version: 0.1.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841320: marked as done (node-collection-visit: FTBFS (Error: Cannot find module wrappy))

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 17:52:50 +0200
with message-id <20161019155250.i6n2tydvt3ovulpy@nuc>
and subject line Re: Bug#841320: node-collection-visit: FTBFS (Error: Cannot 
find module wrappy)
has caused the Debian Bug report #841320,
regarding node-collection-visit: FTBFS (Error: Cannot find module wrappy)
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.)


-- 
841320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-collection-visit
Version: 0.2.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Sorry for this one. Closing duplicate.

(It said "in stretch" but it's not true).--- End Message ---

Bug#841326: node-fill-range: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-fill-range
Version: 3.0.3-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841328: node-has-values: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-has-values
Version: 0.1.4-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841316: gcc: the last 6.2.0-7 broke the virtualbox build

[Matthias Klose]

clone 841316 -1
reassign -1 src:virtualbox
retitle -1 invalid code in virtualbox sources
severity 841316 important
forwarded 841316 https://gcc.gnu.org/PR78039
forcemerge 841292 841316
thanks

This code will be rejected with GCC 7; there is still discussion upstream how
much to revert in this backport to GCC 6.

Processed (with 1 error): Re: Bug#841316: gcc: the last 6.2.0-7 broke the virtualbox build

[Debian Bug Tracking System]

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

> clone 841316 -1
Bug #841316 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Bug 841316 cloned as bug 841340
> reassign -1 src:virtualbox
Bug #841340 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Bug reassigned from package 'src:gcc-6' to 'src:virtualbox'.
Ignoring request to alter found versions of bug #841340 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841340 to the same values 
previously set
> retitle -1 invalid code in virtualbox sources
Bug #841340 [src:virtualbox] gcc: the last 6.2.0-7 broke the virtualbox build
Changed Bug title to 'invalid code in virtualbox sources' from 'gcc: the last 
6.2.0-7 broke the virtualbox build'.
> severity 841316 important
Bug #841316 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Severity set to 'important' from 'serious'
> forwarded 841316 https://gcc.gnu.org/PR78039
Bug #841316 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR78039'.
> forcemerge 841292 841316
Bug #841292 [gcc-6] gcc-6: flexible array support broken
Unable to merge bugs because:
package of #841316 is 'src:gcc-6' not 'gcc-6'
Failed to forcibly merge 841292: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#841342: zshdb: FTBFS under some locales (eg. fr_CH.UTF-8)

[Chris Lamb]

Source: zshdb
Version: 0.92-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org


Dear Maintainer,

zshdb fails to build from source in unstable/amd64 under some
locales (eg. LANG="fr_CH.UTF-8").

The code already tries to work around this:

  54 # set the constants readonly
  55 shunit_constants_=`set |grep '^__SHUNIT_' |cut -d= -f1`
  56 echo "${shunit_constants_}" |grep '^Binary file' >/dev/null && \
  57 shunit_constants_=`set |grep -a '^__SHUNIT_' |cut -d= -f1`

… but this doesn't work if the "Binary file" message is in, say, French :)

Changing this:

  - shunit_constants_=`set |grep '^__SHUNIT_' |cut -d= -f1`
  + shunit_constants_=`set |LC_ALL=C grep '^__SHUNIT_' |cut -d= -f1`

… makes this appear to work, but then you get other errors:

--- /tmp/setshow-filtered.check 2016-10-19 18:22:06.324491603 +0200
+++ zshdb-0.92/test/data/setshow.right  2016-07-06 18:47:42.0 +0200
@@ -1,4 +1,3 @@
-** pas un tty is not reputed to be a tty.
 (dbg-test2.sh:6):
 fn1 () { echo "fn1 here" x=5 fn3 }

etc. etc.

One solution (attached) is to simply set LC_ALL=C when running the
tests, but that suggests it would still fail at runtime and we are
just masking that issue? I would speak to upstream.

The full build log is attached.


Regards,

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


zshdb.0.92-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index 5639f0e..a3b5d33 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,5 +11,5 @@ override_dh_auto_test:
# The tests make use of things like the history file, they need a dummy
# home directory.
mkdir test_homedir
-   HOME=$(shell pwd)/test_homedir dh_auto_test
+   LC_ALL=C HOME=$(shell pwd)/test_homedir dh_auto_test
rm -rf test_homedir

Bug#841341: bd "Bad substitution" if /bin/sh is not bash

[Gerardo Martin Chaves]

Package: bd
Version: 1.01-1
Severity: grave
Tags: patch
Justification: renders package unusable

bd fails if /bin/sh is not bash on line 39

elif [ "${@: -1}" = -v ]



-- 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.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information
*** bd.orig	2016-10-19 13:22:02.361683645 -0300
--- bd	2016-10-19 13:22:18.265769346 -0300
***
*** 36,42 
  if [ $# -eq 0 ]
  then
usage_error
! elif [ "${@: -1}" = -v ]
  then
usage_error
  else
--- 36,42 
  if [ $# -eq 0 ]
  then
usage_error
! elif [ "${@}" = -v -o "${@}" = "" ]
  then
usage_error
  else

Bug#841338: node-repeat-element: FTBFS (Error: Cannot find module wrappy)

[Chris Lamb]

Hi,

> node-repeat-element: FTBFS (Error: Cannot find module wrappy)

This (and others) appears to be a duplicate of #841274. I used
"affects" there, perhaps incorrectly, but at least it avoids
duplicates.


Regards,

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