Bug#814403: ckeditor: FTBFS: /usr/bin/ckbuilder: 2: /usr/bin/ckbuilder: Syntax error: Unterminated quoted string

[Chris Lamb]

Source: ckeditor
Version: 4.5.6+dfsg-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,

ckeditor fails to build from source in unstable/amd64:

  [..]

  dh_auto_build
  cd dev/builder \
  && ckbuilder --no-zip --no-tar --overwrite \
  --version="4.5.6" --revision="1" \
  --build ../../ _build
  /usr/bin/ckbuilder: 1: /usr/bin/ckbuilder: PK: not found
  /usr/bin/ckbuilder: 2: /usr/bin/ckbuilder: Syntax error: Unterminated quoted 
string
  debian/rules:19: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160211091323.3ap86cQP05/ckeditor-4.5.6+dfsg'
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


ckeditor.4.5.6+dfsg-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: tagging 810929, severity of 810929 is important

[Debian Bug Tracking System]

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

> tags 810929 + moreinfo
Bug #810929 [vim-ultisnips] Renders Vim unusable
Added tag(s) moreinfo.
> #lowering severity as it does not seem to affect every user of ultisnips
> severity 810929 important
Bug #810929 [vim-ultisnips] Renders Vim unusable
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#813875: insighttoolkit4: FTBFS on i386 (member reference base type 'void' is not a structure or union)

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: tags -1 patch
Hi Gert, there is a patch
https://github.com/CastXML/CastXML/commit/5cfebb0f904131d1df8e36fcb9c290
f12c06e9ba

let me know if you need an upload!

cheers,

Gianfranco

On Tue, 9 Feb 2016 11:20:13 -0500 Brad King  wrot
e:
> On 02/06/2016 06:34 AM, Gert Wollny wrote:
>> As you can see, this  is actually a bug in castxml
> [snip]
>> would you please consider filing a bug upstream
> 
> I've recorded the issue upstream here:
> 
> https://github.com/CastXML/CastXML/issues/47
> 
> Please follow that for updates.
> 
> -Brad
> 
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWvFb1AAoJEPNPCXROn13ZQLAP/3JsMtzJxE6oT4x9OHQdzQDo
i4DGueEdVUDEjvTcCXFx+Vp976UjOQZ04pzg1IeSX8Fw+kXwe0VVifP4DyOqGa5P
NcKqi97hRYzN9hWFbeou4R9xZND8SllNC6MfatUtlzSHDyN6y1w8Q9UxiHuBy37K
l85tWFSfLrCh5LUScsq2O7pig9TTACnuw/bvhqi5TxfOqxS0ywqIxRytMtgO1oE8
wzm5Dv2JclngKgW3uoCRIRaBNcEQkfUyzwRho8HKBvkyKyejX4tU82Aw49geyJnK
hfCeaPsSa2UDPFlHEtzVfRLdXHqO7rz4DAbjkjIJPfgNOWCBZymFrM55FZEheMaD
bfLdYtARwvXkEPj1LD2oOORXH3CtxpKrchvndEYHSpWIQ4GzGcymkhsQNjO6bRCG
/cJo6VHLCondKQlxHFwQOeGWXVKSNSf6y3Q1TVeXXCeADEuUyICL8GewnCEWIQNP
PLLcZwU4wtLITWkWUyxt7ZnYoMXd/h+3PKakbvblUVbIHkFaEwk0G/Y8flC956Fq
jD5kb9QTyMo05jha/VHpLQb5Xtv0VAl5f4rNrOyzT5XxPp1wZicUXbI1OYsx1BS0
uIBTpqy9WewN2G/99celVK5QCuhUUb3vs3shv6vOPGK7b6OBeM1dQGJwb4wNfbIJ
7m+y6rW5JU2RhZn8uKJK
=AGNx
-END PGP SIGNATURE-

Processed: Re: Bug#813875: insighttoolkit4: FTBFS on i386 (member reference base type 'void' is not a structure or union)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #813875 [castxml] castxml on i386 doesn't support anonymous unions in type
Added tag(s) patch.

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

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Andreas Beckmann]

On 2016-02-06 13:59, Kartik Mistry wrote:
> On Wed, Feb 3, 2016 at 9:46 PM, Andreas Beckmann  wrote:
>>> What is the best way to fix this?
>>
>> Probably reverting the reverted transition, therefore reopening this bug.
>>
>> You can drop the v5 suffix once upstream bumps the SOVERSION again and
>> you have to rename the package anyway.
> 
> I'm preparing fix, Can anyone look at,
> https://anonscm.debian.org/cgit/debian-science/packages/lttoolbox.git/commit/?id=a3b07fe80d08de83902971f45aab75701bae8cea
> and see if it is OK?

You have a now useless

Breaks: liblttoolbox3-3.3-0v5 (<= 3.3.2~r61000-3.1)

in there.

For the changelog I would say something like "Reinstate the g++-5 ABI
transition and renamed packages."   


Andreas

Bug#800279: marked as done (ddtc: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 06:18:54 +
with message-id 
and subject line Bug#800279: fixed in ddtc 0.17.2
has caused the Debian Bug report #800279,
regarding ddtc: Please migrate a supported debhelper compat level
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

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

Thanks,
~Niels

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

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ddtc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 12 Feb 2016 06:40:16 +0100
Source: ddtc
Binary: ddtc
Architecture: source
Version: 0.17.2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 ddtc   - Deal with ddts mails
Closes: 800279
Changes:
 ddtc (0.17.2) unstable; urgency=medium
 .
   * QA upload.
   * Set the maintainer to the QA team.
   * Build with debhelper 9 (closes: #800279)
   * Update FSF's address.
Checksums-Sha1:
 4a81255ccc2ff6c63ee86254f135b431a45156a6 1025 ddtc_0.17.2.dsc
 3a9f09ea3546d7ddfc3406edef4ed9bd91c22327 47896 ddtc_0.17.2.tar.gz
Checksums-Sha256:
 62ca49a302864520bc5eb1ed40abf1ee94e2f63ebd18b718b5868e75fa688bbd 1025 
ddtc_0.17.2.dsc
 c7e52f86cbc29640ef7326b1334f980d27b04963a45a770926cf8fcdbec71d77 47896 
ddtc_0.17.2.tar.gz
Files:
 447740da6e8e24fa87bc1f9b575a3cb7 1025 text optional ddtc_0.17.2.dsc
 3cd6e70802a1cddd0d83f4b1b0f32c2b 47896 text optional ddtc_0.17.2.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWvXHYAAoJECw7Q2/qxoEB8rgH/1ftI/XKy7fIHMrJq2fyhO0c
3gV8VUYOjCiH+eQSeGWg3knICgRvhlWXi52krFfeTrT1fw/o13LvkJFw0B6dRJGU
L2+sdHOhSMnFfjlkMk1uVRvbbqe8RLwFUiGh5WmrUNrtVkBYWif+Ta8WQnDsduKs
x00q+u4KY5ebxAKaK42zM6mYHpKrvU8eJMYhGMRAW6s74Q4k+x335NDSoOfsINFl
+RxnOTBBZH4KD9ZiTDpNbk4PUQjn8N5XUfGEZ7t5pg+CRnu+1G6LTXMjI6vy/UFY
zOaNWjutdDrAXtpFUCtTFFqrMG7kRwdh0A/ujFhrwzdT5rW91zZo96cY5cQsoJc=
=W26v
-END PGP SIGNATURE End Message ---

Bug#814473: [Debichem-devel] Bug#814473: elpa: FTBFS: find: '/usr/share/libtool/config/ltmain.sh': No such file or directory

[Graham Inggs]

On 12 February 2016 at 01:20, Andreas Beckmann  wrote:
> dh_autoreconf --as-needed
> find: '/usr/share/libtool/config/ltmain.sh': No such file or directory
> dh_autoreconf: find /usr/share/libtool/config/ltmain.sh . ! -ipath 
> "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o -path '*/.bzr/*' 
> -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} \; > 
> debian/autoreconf.before returned exit code 1
> debian/rules:14: recipe for target 'override_dh_autoreconf' failed
> make[1]: *** [override_dh_autoreconf] Error 2
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> debian/rules:11: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
>
>
> I cannot reproduce this in a sid pbuilder environment.

Looks like #814063

Bug#814492: libgnome2-wnck-perl: FTBFS: Package 'xres', required by 'libwnck-1.0', not found

[Niko Tyni]

Package: libgnome2-wnck-perl
Version: 0.16-3
Severity: serious
Tags: stretch sid
X-Debbugs-Cc: libwnck-...@packages.debian.org

This package fails to build on current sid/amd64.  It looks like
libwnck-dev recently dropped its dependency on libxres-dev, making
things like 'pkg-config --cflags libwnck-1.0' fail.

Cc'ing the libwnck maintainers. Was this intentional?

  https://reproducible.debian.net/rb-pkg/unstable/amd64/libgnome2-wnck-perl.html

 dh_auto_configure
  perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro"
  Package xres was not found in the pkg-config search path.
  Perhaps you should add the directory containing `xres.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'xres', required by 'libwnck-1.0', not found
   at Makefile.PL line 46.
  *** can not find package libwnck-1.0 >= 2.20.0
  *** check that it is properly installed and available in PKG_CONFIG_PATH
   at Makefile.PL line 46.
  dh_auto_configure: perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 LD=x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro returned exit code 1
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 1
  
-- 
Niko Tyni   nt...@debian.org

Bug#814183: openmpi 1.10.2 is broken on powerpc

[Graham Inggs]

On 12 February 2016 at 01:17, Emilio Pozuelo Monfort  wrote:
> On Tue, 9 Feb 2016 21:49:29 +0200 Graham Inggs  wrote:
>> Petsc rebuilt successfully [1] a couple of hours ago on poulenc.d.o. [2].
>> My previous tests were done on partch.d.o. [3].  Partch has 2GB of RAM
>> vs Poulenc's 5GB, I don't know if this is significant.
>
> aces3 failed on powerpc-osuosl-01.
>
> poulenc is a PPC970FX
> patch is a POWER7
> powerpc-osuosl-01 is a POWER8
>
> Dunno if that is relevant.

It might be, thanks!  Is there any way to arrange for aces3 to be
rebuilt on poulenc?  That should tell us something.

Processed: tagging 814404

[Debian Bug Tracking System]

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

> tags 814404 + pending
Bug #814404 [src:etcd] etcd: FTBFS: rpc.pb.go:534: cannot use 
_Etcd_Range_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#791907: bootlogd: /var/log/boot is empty with systemd

[Petter Reinholdtsen]

[Vincent Lefevre]
> So, perhaps bootlogd is useless with systemd. If this is the case,
> and as it doesn't work anyway, perhaps it should conflict with
> systemd-sysv.

I have not investigated, but suspect you are right.  I suspect bootlogd
is depending on mechanism not available when using systemd, and is not
going to work with systemd.  So a conflict is probably a good idea, to
make this more clear.

-- 
Happy hacking
Petter Reinholdtsen

Bug#794686: nslcd start script does not report starting failure

[Nikolay Shaplov]

This bug was not fixed for debian jessie, as I can see... 
And I think it should be fixed in all supported distributives, as it can cause 
problems.

Bug#814415: gnuplot5: inconsistency on dependencies

[Vincent Lefevre]

Source: gnuplot5
Version: 5.0.3+dfsg1-1
Severity: serious
Justification: 7

When I want to upgrade gnuplot5-qt to 5.0.3+dfsg1-1, it wants to
remove gnuplot-x11:

# apt-get install gnuplot5-qt
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-4.1.0-2-amd64
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  gnuplot5-data
The following packages will be REMOVED:
  gnuplot-x11
The following packages will be upgraded:
  gnuplot5-data gnuplot5-qt
2 upgraded, 0 newly installed, 1 to remove and 34 not upgraded.

If the goal is to get rid of gnuplot4, then it should no longer
depend on it: gnuplot5-data 5.0.3+dfsg1-1 depends on gnuplot-tex,
which mentions gnuplot-x11 for X11 output:

Package: gnuplot-tex
Status: install ok installed
Priority: optional
Section: doc
Installed-Size: 131
Maintainer: Debian Science Team 

Architecture: all
Source: gnuplot
Version: 4.6.6-3
Breaks: gnuplot-nox (<< 4.6.5-5), gnuplot-qt (<< 4.6.5-5), gnuplot-x11 (<< 
4.6.5-5)
Description: Command-line driven interactive plotting program. Tex-files
 Gnuplot is a portable command-line driven interactive data and function
 plotting utility that supports lots of output formats, including drivers
 for many printers, (La)TeX, (x)fig, Postscript, and so on. The X11-output
 is packaged in gnuplot-x11.
[...]

BTW, gnuplot5-data also mentions gnuplot-x11.

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

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

Bug#814405: gnome-mines: FTBFS: gnome-mines.appdata.xml: FAILED: ? tag-missing: not specified

[Chris Lamb]

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

Dear Maintainer,

gnome-mines fails to build from source in unstable/amd64:

  [..]

  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2/data'
  LC_ALL=C /usr/bin/intltool-merge  -x -u -c ../po/.intltool-merge-cache ../po 
gnome-mines.appdata.xml.in gnome-mines.appdata.xml
  Found cached translation database
  Merging translations into gnome-mines.appdata.xml.
  CREATED gnome-mines.appdata.xml
  if test -f "gnome-mines.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}gnome-mines.appdata.xml; fi \
&& touch gnome-mines.appdata.valid
  gnome-mines.appdata.xml: FAILED:
  ? tag-missing   :  not specified
  Validation of files failed
  Makefile:859: recipe for target 'gnome-mines.appdata.valid' failed
  make[3]: *** [gnome-mines.appdata.valid] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2/data'
  Makefile:533: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2/data'
  Makefile:373: recipe for target 'check-recursive' failed
  make[1]: *** [check-recursive] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2'
  dh_auto_test: make -j9 check returned exit code 2
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


gnome-mines.1:3.18.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814406: sisu-guice: FTBFS: [FATAL] Non-resolvable parent POM for org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact org.sonatype.sisu.inject:guice-parent:pom:4.0-SNAPSH

[Chris Lamb]

Source: sisu-guice
Version: 3.2.6-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,

sisu-guice fails to build from source in unstable/amd64:

  [..]

  touch debian/stamp-poms-patched
  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
  clean
  [INFO] Scanning for projects...
  [ERROR] [ERROR] Some problems were encountered while processing the POMs:
  [FATAL] Non-resolvable parent POM for 
org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact 
org.sonatype.sisu.inject:guice-parent:pom:4.0-SNAPSHOT and 
'parent.relativePath' points at wrong local POM @ line 19, column 11
  [WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ 
org.sonatype.sisu.inject:guice-testlib:[unknown-version], 
/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/extensions/testlib/pom.xml,
 line 18, column 15
   @ 
  [ERROR] The build could not read 1 project -> [Help 1]
  [ERROR]   
  [ERROR]   The project org.sonatype.sisu.inject:jdk8-tests:[unknown-version] 
(/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/jdk8-tests/pom.xml)
 has 1 error
  [ERROR] Non-resolvable parent POM for 
org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact 
org.sonatype.sisu.inject:guice-parent:pom:4.0-SNAPSHOT and 
'parent.relativePath' points at wrong local POM @ line 19, column 11 -> [Help 2]
  [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/ProjectBuildingException
  [ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
  /usr/share/cdbs/1/class/maven.mk:104: recipe for target 'cleanbuilddir' failed
  make: [cleanbuilddir] Error 1 (ignored)
  rm -f -r 
/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
 debian/stamp-maven-build
  rm -f debian/*.substvars
  /usr/bin/make -f debian/rules unpatch-poms
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6'
  mh_unpatchpoms -plibsisu-guice-java
  rm -f -f debian/stamp-poms-patched
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6'
  dh_clean 
  mh_unpatchpoms -plibsisu-guice-java
  rm -f -f debian/stamp-poms-patched
  mh_clean
  rm -f debian/stamp-maven-check
   debian/rules build
  test -x debian/rules
  mkdir -p "."
  /usr/share/maven-debian-helper/copy-repo.sh 
/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian
  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 -plibsisu-guice-java --debian-build --keep-pom-version 
--maven-repo=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
  --build-no-docs
  touch debian/stamp-poms-patched
  # before-build target may be used to unpatch the pom files, so we need to 
check if
  # patching the pom files is needed here, normally not
  if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
  fi
  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [ERROR] [ERROR] Some problems were 

Bug#814404: etcd: FTBFS: rpc.pb.go:534: cannot use _Etcd_Range_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) as type grpc.methodHandler in field value

[Chris Lamb]

Source: etcd
Version: 2.2.3+dfsg-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,

etcd fails to build from source in unstable/amd64:

  [..]

  github.com/prometheus/client_golang/prometheus
  github.com/boltdb/bolt
  github.com/coreos/etcd/etcdserver/etcdserverpb
  github.com/coreos/etcd/storage/backend
  # github.com/coreos/etcd/etcdserver/etcdserverpb
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:534: cannot use 
_Etcd_Range_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:538: cannot use 
_Etcd_Put_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) 
(interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:542: cannot use 
_Etcd_DeleteRange_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:546: cannot use 
_Etcd_Txn_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) 
(interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:550: cannot use 
_Etcd_Compact_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
  github.com/google/btree
  github.com/coreos/etcd/rafthttp
  github.com/coreos/etcd/snap
  github.com/coreos/etcd/storage
  github.com/coreos/etcd/store
  github.com/coreos/etcd/pkg/crc
  github.com/coreos/etcd/wal/walpb
  github.com/coreos/etcd/wal
  golang.org/x/crypto/blowfish
  github.com/coreos/etcd/pkg/cors
  golang.org/x/crypto/bcrypt
  github.com/coreos/etcd/pkg/transport
  github.com/coreos/etcd/pkg/osutil
  github.com/coreos/etcd/proxy
  github.com/coreos/go-systemd/daemon
  github.com/coreos/go-systemd/util
  github.com/coreos/etcd/pkg/flags
  golang.org/x/net/netutil
  github.com/codegangsta/cli
  github.com/coreos/etcd/Godeps/_workspace/src/github.com/bgentry/speakeasy
  github.com/coreos/etcd/integration
  github.com/coreos/etcd/pkg/testutil
  github.com/coreos/etcd/raft/rafttest
  github.com/coreos/etcd/tools/functional-tester/etcd-agent/client
  github.com/coreos/etcd/Godeps/_workspace/src/github.com/rakyll/pb
  github.com/coreos/etcd/tools/functional-tester/etcd-agent
  github.com/coreos/etcd/client
  github.com/coreos/etcd/discovery
  github.com/coreos/etcd/tools/functional-tester/etcd-tester
  dh_auto_build: go install -v github.com/coreos/etcd 
github.com/coreos/etcd/client github.com/coreos/etcd/discovery 
github.com/coreos/etcd/error github.com/coreos/etcd/etcdctl 
github.com/coreos/etcd/etcdctl/command github.com/coreos/etcd/etcdctlv3 
github.com/coreos/etcd/etcdctlv3/command github.com/coreos/etcd/etcdmain 
github.com/coreos/etcd/etcdserver github.com/coreos/etcd/etcdserver/api/v3rpc 
github.com/coreos/etcd/etcdserver/auth 
github.com/coreos/etcd/etcdserver/etcdhttp 
github.com/coreos/etcd/etcdserver/etcdhttp/httptypes 
github.com/coreos/etcd/etcdserver/etcdserverpb 
github.com/coreos/etcd/etcdserver/stats github.com/coreos/etcd/integration 
github.com/coreos/etcd/pkg/cors github.com/coreos/etcd/pkg/crc 
github.com/coreos/etcd/pkg/fileutil github.com/coreos/etcd/pkg/flags 
github.com/coreos/etcd/pkg/httputil github.com/coreos/etcd/pkg/idutil 
github.com/coreos/etcd/pkg/ioutil github.com/coreos/etcd/pkg/netutil 
github.com/coreos/etcd/pkg/osutil github.com/coreos/etcd/pkg/pathutil 
github.com/coreos/etcd/pkg/pbutil github.com/coreos/etcd/pkg/runtime 
github.com/coreos/etcd/pkg/testutil github.com/coreos/etcd/pkg/timeutil 
github.com/coreos/etcd/pkg/transport github.com/coreos/etcd/pkg/types 
github.com/coreos/etcd/pkg/wait github.com/coreos/etcd/proxy 
github.com/coreos/etcd/raft github.com/coreos/etcd/raft/raftpb 
github.com/coreos/etcd/raft/rafttest github.com/coreos/etcd/rafthttp 
github.com/coreos/etcd/snap github.com/coreos/etcd/snap/snappb 
github.com/coreos/etcd/storage github.com/coreos/etcd/storage/backend 
github.com/coreos/etcd/storage/storagepb github.com/coreos/etcd/store 
github.com/coreos/etcd/tools/etcd-dump-logs 
github.com/coreos/etcd/tools/functional-tester/etcd-agent 
github.com/coreos/etcd/tools/functional-tester/etcd-agent/client 
github.com/coreos/etcd/tools/functional-tester/etcd-tester 
github.com/coreos/etcd/tools/v3benchmark github.com/coreos/etcd/version 
github.com/coreos/etcd/wal github.com/coreos/etcd/wal/walpb returned exit code 2
  debian/rules:11: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  

Bug#811708: [Fwd: Re: [PKG-OpenRC-Debian] Bug#811708: need help?]

[Svante Signell]

Adam,

Can you please NMU this package as you promised. Time is running out.

Thanks!--- Begin Message ---
On Mon, 2016-02-08 at 13:13 +0100, Svante Signell wrote:
> On Mon, 2016-02-08 at 08:26 +0100, Adam Borowski wrote:
> > > init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d
> > 
> > Uhm, guys... are you alive?  This bug keeps openrc uninstallable, and will
> > cause its autoremoval soon.
> > 
> > If you're too busy and need help, I could help with fixing or NMUing, but
> > you need to decide whether to:
> > * cooperate with init-system-helpers and put the logic there (like sysv-rc)
> > * divert update-rc.d (like file-rc)
> > 
> > Note that I'm not the best person to help, though, as I use openrc only on a
> > single desktop and thus don't know anything about its advanced features nor
> > internals.
> 
> Hi Adam,
> Cc: Roger
> 
> I sent the following mail to the openrc maintainers: Benda Xu, Thomas Goirand
> and Roger Leigh on Friday February 5th (no reply so far). The mail to Roger
> bounced, he is no longer a Debian maintainer.
> 
> > Hello,
> > 
> > Due to the serious bug 811708 openrc (0.18.3-1) will be removed from Debian
> > testing on February 18. In my opinion it would be a pity if it disappears.
> > 
> > Is it possible to do as file-rc (0.8.17) did in bug 812337: add a diversion?
> > 
> > From changelog: divert update-rc.d + invoke-rc.d files to cooperate with
> > init-
> > system-helpers =1.25. It seems like only divert() in preinst and
> > undivert() in
> > postrm scripts has to be created and called.

Attached are patches of debian/changelog and new files debian/preinst and
debian/postrm. Maybe the debian/control file has to be modified too. Are they
sufficient to create a diversion of openrc so that bug 811708 can be closed? I
have not yet had time to test-install, the plan is to do that for GNU/Linux and
GNU/Hurd.


--- a/debian/changelog.orig	2015-11-09 15:11:35.0 +0100
+++ b/debian/changelog	2016-02-09 22:41:37.0 +0100
@@ -1,3 +1,11 @@
+openrc (0.18.3-2) unstable; urgency=medium
+  * Create debian/{preinst,postrm} scripts as for file-rc to
+divert update-rc.d + invoke-rc.d files to cooperate with
+init-system-helpers >=1.25
+(Closes: #811708)
+
+ -- Svante Signell   Tue, 09 Feb 2016 16:53:58 +0100
+
 openrc (0.18.3-1) unstable; urgency=medium
 
   [ Dmitry Yu Okunev ]


postrm
Description: application/shellscript


preinst
Description: application/shellscript
--- End Message ---

Bug#814431: tests fail on i386

[Matthias Klose]

Package: src:swi-prolog
Version: 7.2.3-1
Severity: serious
Tags: sid stretch

tests fail on i386:

ERROR: /«PKGBUILDDIR»/packages/jpl/test_jpl.pl:1185:
	test threads3: received error: jpl:jFindClass/2: Undefined procedure: 
jpl:jni_func/3

ERROR: /«PKGBUILDDIR»/packages/jpl/test_jpl.pl:1203:
	test jref1: received error: plunit_jpl:'unit body'/2: Undefined procedure: 
jpl:jni_term_to_jref/2

ERROR: /«PKGBUILDDIR»/packages/jpl/test_jpl.pl:1213:
	test jref2: received error: plunit_jpl:'unit body'/2: Undefined procedure: 
jpl:jni_term_to_jref/2

Makefile:60: recipe for target 'check_pl' failed
make[2]: *** [check_pl] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»/packages/jpl'
debian/rules:134: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:70: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Bug#811708: pong on update-rc.d

[Adam Borowski]

On Fri, Feb 12, 2016 at 12:47:09AM +0900, Benda Xu wrote:
> Thanks for the report.  update-rc.d in OpenRC is a hack based on that
> from sysv-rc.  I think the right way forward is to extend
> init-system-helpers to support OpenRC.

Great, that answers the question about which way to fix the bug.  This
wasn't a decision that should be done in a NMU without your input.

> I will try to figure it out.  If I couldn't make it in time, Svante's
> patch will be upload to close this bug.

The patch would require some fixing.  Note that the two versions do differ:
the first one overwritten existing postrm.  The second one still does some
stuff specific to file-rc.

But as you decided to go the other way, this matters only if we'd need to
use it as a fallback.

-- 
A tit a day keeps the vet away.

Bug#808593: [Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: testHTTPNotExist

[Andreas Tille]

Hi,

any hint why this test that worked before might fail since end of
December?

Kind regards

 Andreas.

On Mon, Dec 21, 2015 at 10:59:11AM +, Chris Lamb wrote:
> Source: htsjdk
> Version: 1.138+dfsg.1-4
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> htsjdk fails to build from source in unstable/amd64:
> 
>   [..]
> 
>  [testng] PASSED: testReadAndSkipWithMultipleBlocks([null of CHAR, null 
> of CHAR, null of FLOAT])
>  [testng] PASSED: testReadAndSkipWithMultipleBlocks([null of CHAR, null 
> of CHAR, null of CHAR])
>  [testng] FAILED: testHTTPNotExist
>  [testng] java.lang.AssertionError: expected [false] but found [true]
>  [testng] at org.testng.Assert.fail(Assert.java:94)
>  [testng] at org.testng.Assert.failNotEquals(Assert.java:496)
>  [testng] at org.testng.Assert.assertEquals(Assert.java:125)
>  [testng] at org.testng.Assert.assertEquals(Assert.java:288)
>  [testng] at org.testng.Assert.assertEquals(Assert.java:298)
>  [testng] at 
> htsjdk.tribble.util.ParsingUtilsTest.tstExists(ParsingUtilsTest.java:142)
>  [testng] at 
> htsjdk.tribble.util.ParsingUtilsTest.testHTTPNotExist(ParsingUtilsTest.java:137)
>  [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>  [testng] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  [testng] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [testng] at java.lang.reflect.Method.invoke(Method.java:606)
>  [testng] at 
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
>  [testng] at 
> org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
>  [testng] at 
> org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
>  [testng] at 
> org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
>  [testng] at 
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:124)
>  [testng] at 
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
>  [testng] at org.testng.TestRunner.privateRun(TestRunner.java:773)
>  [testng] at org.testng.TestRunner.run(TestRunner.java:623)
>  [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
>  [testng] at 
> org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
>  [testng] at 
> org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
>  [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:259)
>  [testng] at 
> org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>  [testng] at 
> org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>  [testng] at 
> org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
>  [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
>  [testng] at org.testng.TestNG.run(TestNG.java:1018)
>  [testng] at org.testng.TestNG.privateMain(TestNG.java:1325)
>  [testng] at org.testng.TestNG.main(TestNG.java:1294)
>  [testng] 
>  [testng] SKIPPED: basic
>  [testng] org.testng.TestNGException: 
>  [testng] Method public void 
> htsjdk.samtools.util.IupacTest.basic(java.lang.String) throws 
> java.lang.Exception requires a @DataProvider named : basicDataProvider
>  [testng] at 
> org.testng.internal.Parameters.findDataProvider(Parameters.java:262)
>  [testng] at 
> org.testng.internal.Parameters.handleParameters(Parameters.java:418)
>  [testng] at 
> org.testng.internal.Invoker.handleParameters(Invoker.java:1276)
>  [testng] at 
> org.testng.internal.Invoker.createParameters(Invoker.java:992)
>  [testng] at 
> org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1082)
>  [testng] at 
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:124)
>  [testng] at 
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
>  [testng] at org.testng.TestRunner.privateRun(TestRunner.java:773)
>  [testng] at org.testng.TestRunner.run(TestRunner.java:623)
>  [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
>  [testng] at 
> org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
>  [testng] at 
> org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
>  [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:259)
>  [testng] at 
> 

Bug#814408: aptitude uses all disk space (12G) with recursive trace-dump in /tmp

[Chris Tillman]

Package: aptitude
Version: 0.7.5-3
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?
I had upgraded all packages a couple of weeks ago to testing current level.
Today I opened aptitude, performed update, and it said there were 123 packages
to be updated. I marked the Upgradeable line with +.
It said it was Resolving Dependencies, and then became unresponsive. I went on
to do something else. After 10 minutes or so I found I could not use readline
completion in bash because I had run out of disk space on the root device.
Going back to the aptitude window, I saw many out of disk space messages.
I hit OK on the messages window, and then canceled my pending actions and quit
aptitude.
Once back on the command line, I confirmed I was out of space with df -h.

root@ctillman:/home/chris# df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda519G   17G  865M  96% /

 Conveniently, I had just done df -h before starting the upgrade, so I scrolled
back up and verified I had 12G free beforehand.

root@ctillman:/home/chris# df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda519G  7.0G   11G  41% /

I then used du to drill down to where the space was being used. Here are the
final few lines.

root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-root.7985\:PR9HPH/
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton
9.7G/tmp/aptitude-root.7985:PR9HPH/
root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-
root.7985\:PR9HPH/*
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/usr
16K /tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/etc
24K /tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/var
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton
root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-
root.7985\:PR9HPH/usr
du: cannot access ‘/tmp/aptitude-root.7985:PR9HPH/usr’: No such file or
directory
root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-root.7985\:PR9HPH
/aptitude-trace-dumpubvton/usr
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/usr/bin
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/usr
root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-root.7985\:PR9HPH
/aptitude-trace-dumpubvton/usr/bin
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/usr/bin/X11
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/usr/bin
root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-root.7985\:PR9HPH
/aptitude-trace-dumpubvton/usr/bin/X11
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-
dumpubvton/usr/bin/X11/X11
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-dumpubvton/usr/bin/X11
root@ctillman:/home/chris# du --max-depth=1 -h /tmp/aptitude-root.7985\:PR9HPH
/aptitude-trace-dumpubvton/usr/bin/X11/X11/X11/X11/X11/X11/
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-
dumpubvton/usr/bin/X11/X11/X11/X11/X11/X11/X11
9.7G/tmp/aptitude-root.7985:PR9HPH/aptitude-trace-
dumpubvton/usr/bin/X11/X11/X11/X11/X11/X11/

As you can see, the X11 directory has been recursively created.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Quit aptitude, that freed up about 1G. Then
root@ctillman:/home/chris# rm -rf /tmp/aptitude-root.7985:PR9HPH/aptitude-
trace-dumpubvton/usr/bin/X11/X11/X11/X11/X11/X11/

   * What was the outcome of this action?
root@ctillman:/home/chris# df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda519G  6.9G   11G  40% /



-- Package-specific info:
$TERM not set.
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.7.5
Compiler: g++ 5.3.1 20151207
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.6.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20151024
  cwidget version: 0.5.17
  Apt version: 5.0.0

aptitude linkage:
linux-gate.so.1 (0xb771)
libapt-pkg.so.5.0 => /usr/lib/i386-linux-gnu/libapt-pkg.so.5.0 
(0xb71b8000)
libncursesw.so.5 => /lib/i386-linux-gnu/libncursesw.so.5 (0xb7182000)
libtinfo.so.5 => /lib/i386-linux-gnu/libtinfo.so.5 (0xb715d000)
libsigc-2.0.so.0 => /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 
(0xb7156000)
libcwidget.so.3 => /usr/lib/i386-linux-gnu/libcwidget.so.3 (0xb7053000)
libsqlite3.so.0 => /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb6f71000)
libboost_iostreams.so.1.58.0 => 
/usr/lib/i386-linux-gnu/libboost_iostreams.so.1.58.0 (0xb6f58000)
libboost_filesystem.so.1.58.0 => 
/usr/lib/i386-linux-gnu/libboost_filesystem.so.1.58.0 (0xb6f3c000)
libboost_system.so.1.58.0 => 
/usr/lib/i386-linux-gnu/libboost_system.so.1.58.0 (0xb6f37000)
libxapian.so.22 => /usr/lib/i386-linux-gnu/sse2/libxapian.so.22 
(0xb6d2d000)
libpthread.so.0 

Bug#814411: all ruby-rjb tests fail on i386

[Matthias Klose]

Package: src:ruby-rjb
Version: 1.5.3-1
Severity: serious
Tags: sid stretch

===
Error: test_unbind(TestRjb): RuntimeError: Constants DL and Fiddle is not 
defined.
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'

/scratch/packages/tmp/ruby-rjb-1.5.3/test/test.rb:21:in `setup'
===
E
===
Error: test_underscored_constant(TestRjb): RuntimeError: Constants DL and Fiddle 
is not defined.
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'

/scratch/packages/tmp/ruby-rjb-1.5.3/test/test.rb:21:in `setup'
===


Finished in 0.042415471 seconds.
--
65 tests, 0 assertions, 0 failures, 65 errors, 0 pendings, 0 omissions, 0 
notifications

0% passed
--
1532.46 tests/s, 0.00 assertions/s
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb returned exit code 1

debian/rules:43: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1

Processed: close 782330

[Debian Bug Tracking System]

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

> close 782330 0.3.3-2
Bug #782330 [src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: 
FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
The source 'xserver-xorg-video-openchrome' and version '0.3.3-2' do not appear 
to match any binary packages
Marked as fixed in versions xserver-xorg-video-openchrome/0.3.3-2.
Marked as fixed in versions xserver-xorg-video-openchrome/0.3.3-2.
Bug #782330 [src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: 
FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#813983: marked as done (python-multipletau: FTBFS: IndexError: invalid slice)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 10:22:40 +
with message-id 
and subject line Bug#813983: fixed in python-multipletau 0.1.5+ds-3
has caused the Debian Bug report #813983,
regarding python-multipletau: FTBFS: IndexError: invalid slice
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.)


-- 
813983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-multipletau
Version: 0.1.5+ds-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-multipletau fails to build from source in unstable/amd64:

  [..]

  ==
  ERROR: test_basic.test_ac
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File 
"/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds/tests/test_basic.py",
 line 16, in test_ac
  ist = autocorrelate(range(42), m=2, dtype=np.dtype(float))
File 
"/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds/multipletau/_multipletau.py",
 line 190, in autocorrelate
  if len(trace[:N - (n + m / 2)]) == 0:
  IndexError: invalid slice
  
  ==
  ERROR: test_basic.test_cc
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File 
"/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds/tests/test_basic.py",
 line 26, in test_cc
  soll = correlate(range(42), range(1,43), m=2, dtype=np.dtype(float))
File 
"/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds/multipletau/_multipletau.py",
 line 387, in correlate
  if len(trace1[:N - (n + m / 2)]) == 0:
  IndexError: invalid slice
  
  --
  Ran 2 tests in 0.027s
  
  FAILED (errors=2)
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: 
nosetests -v 
/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds/tests
  dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
--system=custom --test-args=nosetests -v 
/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds/tests
 --dir . returned exit code 13
  debian/rules:17: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160207103701.Pb4OZTbNP7/python-multipletau-0.1.5+ds'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-multipletau.0.1.5+ds-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-multipletau
Source-Version: 0.1.5+ds-3

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

Debian distribution maintenance software
pp.
Alexandre Mestiashvili  (supplier of updated 
python-multipletau 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, 10 Feb 2016 14:32:31 +0100
Source: python-multipletau
Binary: python-multipletau python3-multipletau python-multipletau-doc
Architecture: source all
Version: 0.1.5+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Alexandre Mestiashvili 

Processed: tagging 814403

[Debian Bug Tracking System]

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

> tags 814403 + unreproducible moreinfo
Bug #814403 [src:ckeditor] ckeditor: FTBFS: /usr/bin/ckbuilder: 2: 
/usr/bin/ckbuilder: Syntax error: Unterminated quoted string
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Kartik Mistry]

On Thu, Feb 11, 2016 at 3:13 PM, Andreas Beckmann  wrote:
> You have a now useless
>
> Breaks: liblttoolbox3-3.3-0v5 (<= 3.3.2~r61000-3.1)
>
> in there.
>
> For the changelog I would say something like "Reinstate the g++-5 ABI
> transition and renamed packages."

Breaks field was removed with latest upload.

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com

Bug#814405: marked as done (gnome-mines: FTBFS: gnome-mines.appdata.xml: FAILED: ? tag-missing: not specified)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 10:34:20 +
with message-id 
and subject line Bug#814405: fixed in gnome-mines 1:3.18.2-2
has caused the Debian Bug report #814405,
regarding gnome-mines: FTBFS: gnome-mines.appdata.xml: FAILED: ? tag-missing: 
 not specified
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.)


-- 
814405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-mines
Version: 1:3.18.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gnome-mines fails to build from source in unstable/amd64:

  [..]

  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2/data'
  LC_ALL=C /usr/bin/intltool-merge  -x -u -c ../po/.intltool-merge-cache ../po 
gnome-mines.appdata.xml.in gnome-mines.appdata.xml
  Found cached translation database
  Merging translations into gnome-mines.appdata.xml.
  CREATED gnome-mines.appdata.xml
  if test -f "gnome-mines.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}gnome-mines.appdata.xml; fi \
&& touch gnome-mines.appdata.valid
  gnome-mines.appdata.xml: FAILED:
  ? tag-missing   :  not specified
  Validation of files failed
  Makefile:859: recipe for target 'gnome-mines.appdata.valid' failed
  make[3]: *** [gnome-mines.appdata.valid] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2/data'
  Makefile:533: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2/data'
  Makefile:373: recipe for target 'check-recursive' failed
  make[1]: *** [check-recursive] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160211091521.UNWG7LljW7/gnome-mines-3.18.2'
  dh_auto_test: make -j9 check returned exit code 2
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


gnome-mines.1:3.18.2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gnome-mines
Source-Version: 1:3.18.2-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated gnome-mines 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: Thu, 11 Feb 2016 11:21:22 +0100
Source: gnome-mines
Binary: gnome-mines gnomine
Architecture: source amd64 all
Version: 1:3.18.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gnome-mines - popular minesweeper puzzle game for GNOME
 gnomine- popular minesweeper puzzle game for GNOME (transitional package)
Closes: 814405
Changes:
 gnome-mines (1:3.18.2-2) unstable; urgency=medium
 .
   * Add patches from upstream to build with new appstream-util (Closes: 
#814405)
 - debian/patches/git-appdata-update.patch
 - debian/patches/git-appdata-0.7.patch
Checksums-Sha1:
 89e3350334af779f1003ef7b04c95511ec33fe15 2303 gnome-mines_3.18.2-2.dsc
 af06d8cddfe23e3b3f8b90768f8ce80a5b441527 28028 
gnome-mines_3.18.2-2.debian.tar.xz
 dccb779e77ff4fce68c7e886a1045d4ed3833d42 206212 
gnome-mines-dbgsym_3.18.2-2_amd64.deb
 3d709248119625d6f1a1dabf6ec6aac50992ef25 2453114 gnome-mines_3.18.2-2_amd64.deb
 d783aacfcb453e7665395b9796eaf16aef7b1473 29210 gnomine_3.18.2-2_all.deb
Checksums-Sha256:
 

Bug#814403: ckeditor: FTBFS: /usr/bin/ckbuilder: 2: /usr/bin/ckbuilder: Syntax error: Unterminated quoted string

[Dmitry Smirnov]

Hi Chris,

Thanks for testing my package. :)


On Thu, 11 Feb 2016 09:44:50 AM Chris Lamb wrote:
> ckeditor fails to build from source in unstable/amd64:

I'm unable to reproduce the problem. I'm guessing maybe it could be some kind 
of file system corruption in your build environment...


> The full build log is attached.

Ahhm, build log is not full ;)

-- 
All the best,
 Dmitry Smirnov.

---

If any remedy is tested under controlled scientific conditions and
proved to be effective, it will cease to be alternative and will simply
become medicine. So-called alternative medicine either hasn't been
tested or it has failed its tests.
-- Richard Dawkins, 2007


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

Processed: tagging 814404

[Debian Bug Tracking System]

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

> tags 814404 + confirmed
Bug #814404 [src:etcd] etcd: FTBFS: rpc.pb.go:534: cannot use 
_Etcd_Range_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#813144: marked as done (g++-mingw-w64-i686: unimplemented function libstdc++-6.dll._ZNSt8ios_base4InitC1Ev)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 12:18:51 +
with message-id 
and subject line Bug#813144: fixed in binutils-mingw-w64 6.6
has caused the Debian Bug report #813144,
regarding g++-mingw-w64-i686: unimplemented function 
libstdc++-6.dll._ZNSt8ios_base4InitC1Ev
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.)


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

Package: g++-mingw-w64-i686
Version: 5.3.1-3+16+b1
Severity: grave

C++ programs that use iostreams cannot be run:

$ export CXX=i686-w64-mingw32-g++-win32
$ $CXX hello.cc -o hello.exe
$ $CXX --print-file-name=libgcc_s_sjlj-1.dll | xargs cp -vt.
‘/usr/lib/gcc/i686-w64-mingw32/5.3-win32/libgcc_s_sjlj-1.dll’ -> 
‘./libgcc_s_sjlj-1.dll’
$ $CXX --print-file-name=libstdc++-6.dll | xargs cp -vt.
‘/usr/lib/gcc/i686-w64-mingw32/5.3-win32/libstdc++-6.dll’ -> ‘./libstdc++-6.dll’
$ wine32 hello.exe
wine: Call from 0x7bc52969 to unimplemented function 
libstdc++-6.dll._ZNSt8ios_base4InitC1Ev, aborting
wine: Unimplemented function libstdc++-6.dll._ZNSt8ios_base4InitC1Ev called at 
address 0x7bc52969 (thread 0009), starting debugger...

Unhandled exception: unimplemented function 
libstdc++-6.dll._ZNSt8ios_base4InitC1Ev called in 32-bit code (0x7bc52969).
...


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

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

Versions of packages g++-mingw-w64-i686 depends on:
ii  gcc-mingw-w64-base  5.3.1-3+16+b1
ii  gcc-mingw-w64-i686  5.3.1-3+16+b1
ii  libc6   2.22-0experimental1
ii  libgmp102:6.1.0+dfsg-2
ii  libisl150.16.1-1
ii  libmpc3 1.0.3-1
ii  libmpfr43.1.3-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

--
Jakub Wilk
#include 

int main(int argc, char **argv)
{
	 return 0;
}
--- End Message ---
--- Begin Message ---
Source: binutils-mingw-w64
Source-Version: 6.6

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated binutils-mingw-w64 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: Thu, 11 Feb 2016 13:02:45 +0100
Source: binutils-mingw-w64
Binary: binutils-mingw-w64 binutils-mingw-w64-i686 binutils-mingw-w64-x86-64
Architecture: source
Version: 6.6
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 binutils-mingw-w64 - Cross-binutils for Win32 and Win64 using MinGW-w64
 binutils-mingw-w64-i686 - Cross-binutils for Win32 (x86) using MinGW-w64
 binutils-mingw-w64-x86-64 - Cross-binutils for Win64 (x64) using MinGW-w64
Closes: 813144
Changes:
 binutils-mingw-w64 (6.6) unstable; urgency=medium
 .
   * Disable -Werror (helps with #811598).
   * Switch to https: VCS URIs (see #810378).
   * Revert support for --gc-sections in COFF and PE images (Closes:
 #813144).
Checksums-Sha1:
 a9e7a69fe1e0cec777ebae53db0d24e72b541cd9 1859 binutils-mingw-w64_6.6.dsc
 676e0a0dad62b2f6a3a9972f61023a2fb3d690fe 12512 binutils-mingw-w64_6.6.tar.xz
Checksums-Sha256:
 5358cfaa95cbae54650fc0661d4c4a53624586bc8acb609bfb52eb86b63a3d39 1859 
binutils-mingw-w64_6.6.dsc
 7857b234ebf8121fe524c3ecb667e1f2e624248870db93631dd3b67d7b6c1b69 12512 
binutils-mingw-w64_6.6.tar.xz
Files:
 71496e0411332cf1ccc9241eba9d53d8 1859 devel extra binutils-mingw-w64_6.6.dsc
 5199a43831365fbbf28f6e6f278dc8b6 12512 devel extra 
binutils-mingw-w64_6.6.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWvHh+AAoJEIDTAvWIbYOc5KwP/0QKDrnvbyJq6IinsiYWIR+0
FmnwC+uOp1tFGJB8pm65VpPdAoYm7CUYNJVGiGX66wAL9+FLbWFHgnPAVnyvwfJA

Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

[Bálint Réczey]

Control: fixed -1 15.2+dfsg1-3

2016-02-11 1:53 GMT+01:00 Alessio Treglia :
> Please close again this bug by specifying the version it is no longer
> reproducible.
Most probably it was current version.
Please change it if that's not the case.

Cheers,
Balint

Processed: Re: Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 15.2+dfsg1-3
Bug #813497 {Done: Bálint Réczey } [kodi] kodi: 
Segfault on StartUp
Marked as fixed in versions kodi/15.2+dfsg1-3.

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

Bug#814427: linux-image-4.3.0-1-amd64: memory leak in rtl_usb

[Cristian Ionescu-Idbohrn]

Package: src:linux
Version: 4.3.3-7
Severity: critical
Tags: upstream
Justification: breaks the whole system

The bug triggers the oom-killer after memory gets exhausted.
Rebooting was the only option left.

Feb 10 17:09:01 debian kernel: [91971.006981] expr invoked oom-killer: 
gfp_mask=0x20858, order=0, oom_score_adj=0
Feb 10 17:13:16 debian kernel: [92224.364209] ssh invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=0
Feb 10 17:17:55 debian kernel: [92494.838897] chromium invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=300
Feb 10 17:18:10 debian kernel: [92512.491930] chromium invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=300
Feb 10 17:18:11 debian kernel: [92512.591229] chromium invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=200
Feb 10 17:18:11 debian kernel: [92512.627263] chromium invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:18:11 debian kernel: [92512.695305] chromium invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=300
Feb 10 17:18:11 debian kernel: [92518.620065] DOM Worker invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=0
Feb 10 17:19:49 debian kernel: [92616.049141] zsh invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:19:56 debian kernel: [92623.960756] ssh invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=0
Feb 10 17:19:56 debian kernel: [92624.064644] ssh invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=0
Feb 10 17:19:57 debian kernel: [92624.244884] fping invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:19:57 debian kernel: [92624.448912] expr invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:19:57 debian kernel: [92625.881507] chromium invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=300
Feb 10 17:20:07 debian kernel: [92635.538249] chromium invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=300
Feb 10 17:20:08 debian kernel: [92636.414606] Xorg invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:21:08 debian kernel: [92694.084031] sshd invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=0
Feb 10 17:22:28 debian kernel: [92744.218266] cron invoked oom-killer: 
gfp_mask=0x20858, order=0, oom_score_adj=0
Feb 10 17:22:28 debian kernel: [92773.248057] smtpd invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:22:28 debian kernel: [92777.365410] ssh invoked oom-killer: 
gfp_mask=0x201da, order=0, oom_score_adj=0
Feb 10 17:22:28 debian kernel: [92777.470042] hddtemp invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:22:28 debian kernel: [92777.514018] cron invoked oom-killer: 
gfp_mask=0x2040d0, order=0, oom_score_adj=0
Feb 10 17:22:30 debian kernel: [92781.628055] top invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0
Feb 10 17:26:30 debian kernel: [93018.201374] gconfd-2 invoked oom-killer: 
gfp_mask=0x200da, order=0, oom_score_adj=0

I found this on the LKML mailing list:

https://lkml.org/lkml/2015/12/6/113

FromPeter Wu <>
Subject [PATCH] rtlwifi: fix gigantic memleak in rtl_usb
DateSun, 6 Dec 2015 18:57:57 +0100

which seems to be related.

The device is:

Bus 003 Device 007: ID 2001:3308 D-Link Corp. DWA-121 802.11n Wireless N 150 
Pico Adapter [Realtek RTL8188CUS]

The interface was not set to 'monitor' type, but 'managed'.

I ifdowned the wlan0 iface and:

# lsmod | egrep rtl
rtl8192cu  65536  0
rtl_usb20480  1 rtl8192cu
rtl8192c_common49152  1 rtl8192cu
rtlwifi77824  3 rtl_usb,rtl8192c_common,rtl8192cu
mac80211  626688  3 rtl_usb,rtlwifi,rtl8192cu
cfg80211  540672  2 mac80211,rtlwifi
usbcore   233472  13 
uas,uhci_hcd,rtl_usb,usb_storage,usbserial,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ftdi_sio,rtl8192cu,xhci_hcd,xhci_pci

# modprobe -r -v rtl8192cu
rmmod rtl8192cu
rmmod rtl8192c_common
rmmod rtl_usb
rmmod rtlwifi
rmmod mac80211
rmmod cfg80211
rmmod rfkill

vmstat shows memory consumtion stabilized (at least it looks like
that). The leak was around 300 k/s.

Now it looks like the system is slowly recovering.  Is no longer
just allocating memory, but deallocating too.

Simplified system information follows:

-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/vg0-root ro 
cgroup_enable=memory swapaccount vga=795

** Model information
sys_vendor:
product_name:
product_version:
chassis_vendor:
chassis_version:
bios_vendor: Intel Corp.
bios_version: BAP6710H.86A.0067.2011.0526.1448
board_vendor: Intel Corporation
board_name: DP67BA
board_version: AAG10219-300

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 

Bug#807511: cpqarrayd: DNBFS (was: Re: failed ppc64el build of cpqarrayd 2.3-4)

[Fernando Seiti Furusato]

Source: cpqarrayd
Version: 2.3-4
Followup-For: Bug #807511

Hello.

I have been trying to fiture out this failure with cpqarrayd on ppc64el.

Since it is a conflict on the types definition, I worked around it by
patching the linux package downloaded to the source tree.

The result is the debdiff attached. It is a very ugly workaround, but it
works.

The build finishes with no errors on ppc64el and I also tested it on amd64
to make sure it does not affected it.
It is a ppc64el specific one, ie, does not work for ppc or ppc64 BE.

Thanks!
diff -Nru cpqarrayd-2.3/debian/changelog cpqarrayd-2.3/debian/changelog
--- cpqarrayd-2.3/debian/changelog	2015-08-08 06:55:01.0 +
+++ cpqarrayd-2.3/debian/changelog	2016-02-10 11:05:07.0 +
@@ -1,3 +1,10 @@
+cpqarrayd (2.3-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch to fix ftbfs on ppc64el 
+
+ -- Fernando Seiti Furusato   Wed, 10 Feb 2016 11:04:55 +
+
 cpqarrayd (2.3-4) unstable; urgency=medium
 
   * Make build agnostic of kernel major version number (Closes: #791618). 
diff -Nru cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch
--- cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch	1970-01-01 00:00:00.0 +
+++ cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch	2016-02-10 11:04:16.0 +
@@ -0,0 +1,63 @@
+diff -purN a/debian/linux/linux-source-4.3/include/linux/types.h b/debian/linux/linux-source-4.3/include/linux/types.h
+--- a/debian/linux/linux-source-4.3/include/linux/types.h	2016-02-09 17:42:39.476237208 +
 b/debian/linux/linux-source-4.3/include/linux/types.h	2016-02-09 17:44:30.950788014 +
+@@ -9,20 +9,22 @@
+ #define DECLARE_BITMAP(name,bits) \
+ 	unsigned long name[BITS_TO_LONGS(bits)]
+ 
++#if defined(__PPC64__) && defined(__LITTLE_ENDIAN__)
++#define u32 __u32
++#define u64 __u64
++#endif
++
+ typedef __u32 __kernel_dev_t;
+ 
+-typedef __kernel_fd_set		fd_set;
+-typedef __kernel_dev_t		dev_t;
++
+ typedef __kernel_ino_t		ino_t;
+ typedef __kernel_mode_t		mode_t;
+ typedef unsigned short		umode_t;
+-typedef __u32			nlink_t;
+ typedef __kernel_off_t		off_t;
+ typedef __kernel_pid_t		pid_t;
+ typedef __kernel_daddr_t	daddr_t;
+ typedef __kernel_key_t		key_t;
+ typedef __kernel_suseconds_t	suseconds_t;
+-typedef __kernel_timer_t	timer_t;
+ typedef __kernel_clockid_t	clockid_t;
+ typedef __kernel_mqd_t		mqd_t;
+ 
+@@ -41,9 +43,16 @@ typedef __kernel_old_uid_t	old_uid_t;
+ typedef __kernel_old_gid_t	old_gid_t;
+ #endif /* CONFIG_UID16 */
+ 
++#if !defined(__PPC64__) && !defined(__LITTLE_ENDIAN__)
++typedef __kernel_fd_set		fd_set;
++typedef __kernel_dev_t		dev_t;
++typedef __u32			nlink_t;
++typedef __kernel_timer_t	timer_t;
++
+ #if defined(__GNUC__)
+ typedef __kernel_loff_t		loff_t;
+ #endif
++#endif /* ppc64el */
+ 
+ /*
+  * The following typedefs are also protected by individual ifdefs for
+@@ -126,6 +135,7 @@ typedef		__s64		int64_t;
+  *
+  * blkcnt_t is the type of the inode's block count.
+  */
++#if !defined(__PPC64__) && !defined(__LITTLE_ENDIAN__)
+ #ifdef CONFIG_LBDAF
+ typedef u64 sector_t;
+ typedef u64 blkcnt_t;
+@@ -133,6 +143,7 @@ typedef u64 blkcnt_t;
+ typedef unsigned long sector_t;
+ typedef unsigned long blkcnt_t;
+ #endif
++#endif
+ 
+ /*
+  * The type of an index into the pagecache.
diff -Nru cpqarrayd-2.3/debian/rules cpqarrayd-2.3/debian/rules
--- cpqarrayd-2.3/debian/rules	2015-08-08 06:43:54.0 +
+++ cpqarrayd-2.3/debian/rules	2016-02-10 11:03:55.0 +
@@ -34,6 +34,7 @@
 	mkdir debian/linux
 	cd debian/linux && tar xvf /usr/src/$(KSRC).tar.xz
 	touch unpack-stamp
+	patch -p1 < $(CURDIR)/debian/patches/linux-types-ppc64el.patch
 
 config.status: configure unpack
 	dh_testdir

Bug#814429: geneweb: debian/mktemplates may fail due to grep binary matching: iconv: conversion from `Binary' is not supported

[Peter Gervai]

Package: geneweb
Version: 6.08dfsg-3.1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Build fails with
iconv: conversion from `Binary' is not supported
on ca language file. The problem is that grep matches the file as binary, and
outputs "Binary file matches", which gets (mis)parsed and screw up iconv params.
Probably dependent on the version of grep, and the phase of the moon possibly. 
:-)

This should fix it anyway:

--- debian/mktemplates  2016-02-11 14:00:53.103700366 +
+++ debian/mktemplates~ 2016-02-11 13:59:01.0 +
@@ -67,7 +67,7 @@
sed '/^\"Content-Type/s/CHARSET/UTF-8/' \
> debian/pobuild/$pofilename.temp
 
-   pocharset=`grep -ai charset $pofile|cut -f2 -d=| sed 's/n\\"//g'`
+   pocharset=`grep -i charset $pofile|cut -f2 -d=| sed 's/n\\"//g'`
cat $pofile | \
 iconv --from $pocharset --to utf-8 | \
sed "s/$pocharset/UTF-8/g" \

Processed: cloning 813144, reopening -1, reassign -1 to g++-mingw-w64-i686

[Debian Bug Tracking System]

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

> clone 813144 -1
Bug #813144 {Done: Stephen Kitt } [binutils-mingw-w64-i686] 
g++-mingw-w64-i686: unimplemented function 
libstdc++-6.dll._ZNSt8ios_base4InitC1Ev
Bug 813144 cloned as bug 814425
> reopen -1
Bug #814425 {Done: Stephen Kitt } [binutils-mingw-w64-i686] 
g++-mingw-w64-i686: unimplemented function 
libstdc++-6.dll._ZNSt8ios_base4InitC1Ev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions binutils-mingw-w64/6.6.
> reassign -1 g++-mingw-w64-i686
Bug #814425 [binutils-mingw-w64-i686] g++-mingw-w64-i686: unimplemented 
function libstdc++-6.dll._ZNSt8ios_base4InitC1Ev
Bug reassigned from package 'binutils-mingw-w64-i686' to 'g++-mingw-w64-i686'.
No longer marked as found in versions 2.25.90.20151209-1+6.5.
Ignoring request to alter fixed versions of bug #814425 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: found 814425 in 5.3.1-3+16+b1

[Debian Bug Tracking System]

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

> found 814425 5.3.1-3+16+b1
Bug #814425 [g++-mingw-w64-i686] g++-mingw-w64-i686: unimplemented function 
libstdc++-6.dll._ZNSt8ios_base4InitC1Ev
Marked as found in versions gcc-mingw-w64/16.
> thanks
Stopping processing here.

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

Processed: Re: Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

[Debian Bug Tracking System]

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

> notfound 813497 15.2+dfsg1-3
Bug #813497 {Done: Bálint Réczey } [kodi] kodi: 
Segfault on StartUp
No longer marked as found in versions kodi/15.2+dfsg1-3.
> thanks
Stopping processing here.

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

Processed: severity of 814427 is important

[Debian Bug Tracking System]

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

> severity 814427 important
Bug #814427 [src:linux] linux-image-4.3.0-1-amd64: memory leak in rtl_usb
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#812997: marked as done (pynfft: FTBFS with libnfft version 3.3)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 16:23:15 +
with message-id 
and subject line Bug#812997: fixed in pynfft 1.3.2-2
has caused the Debian Bug report #812997,
regarding pynfft: FTBFS with libnfft version 3.3
to be marked as done.

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

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


-- 
812997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pynfft
Version: 1.3.2-1.1
Severity: important

Dear Maintainer,

This source package fails to build with the latest release of libnfft
available in experimental. The relevant portion of the build log is
available below.

```
running build_ext
building 'pynfft.nfft' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/build
creating build/temp.linux-x86_64-2.7/build/pynfft-1.3.2
creating build/temp.linux-x86_64-2.7/build/pynfft-1.3.2/pynfft
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c /build/pynfft-1.3.2/pynfft/nfft.c -o 
build/temp.linux-x86_64-2.7/build/pynfft-1.3.2/pynfft/nfft.o -O3 
-fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math
In file included from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1781:0,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
 from /build/pynfft-1.3.2/pynfft/nfft.c:272:
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
 warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it by " \
  ^
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-2.7/build/pynfft-1.3.2/pynfft/nfft.o -lnfft3_threads 
-lnfft3 -lfftw3_threads -lfftw3 -lm -o 
/build/pynfft-1.3.2/.pybuild/pythonX.Y_2.7/build/pynfft/nfft.so
building 'pynfft.solver' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c /build/pynfft-1.3.2/pynfft/solver.c -o 
build/temp.linux-x86_64-2.7/build/pynfft-1.3.2/pynfft/solver.o -O3 
-fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math
In file included from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1781:0,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
 from /build/pynfft-1.3.2/pynfft/solver.c:270:
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
 warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it by " \
  ^
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-2.7/build/pynfft-1.3.2/pynfft/solver.o -lnfft3_threads 
-lnfft3 -lfftw3_threads -lfftw3 -lm -o 
/build/pynfft-1.3.2/.pybuild/pythonX.Y_2.7/build/pynfft/solver.so
building 'pynfft.util' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c 

Bug#814403: ckeditor: FTBFS: /usr/bin/ckbuilder: 2: /usr/bin/ckbuilder: Syntax error: Unterminated quoted string

[Chris Lamb]

> I'm unable to reproduce the problem. I'm guessing maybe it could be some kind 
> of file system corruption in your build environment...

I don't think so; I can reproduce it on another machine.

> > The full build log is attached.
> 
> Ahhm, build log is not full ;)

Sorry, I don't understand.


Regards,

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

Bug#810070: [Pkg-xen-devel] Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

[andy]

 If possible it might be interesting to first try the 4.6 hypervisor in 
Stretch, I suspect the xen-hypervisor-4.6-amd64 package will just install 
on Jessie with no issues since it has no dependencies and you don't need 
the userspace tools just to check if it boots.Hey there,I can confirm the issue 
with new Intel i7-6700 Quad-Core Skylake CPUs and I'm also not able to derive 
further details than already provided. But I can also confirm, that the issue 
seems to be resolved in Debian Stretch.Andy

Processed: Re: Non-Free file: src/stdlib/SDL_qsort.c

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream
Bug #814276 [libsdl2] Non-Free file: src/stdlib/SDL_qsort.c
Added tag(s) upstream.
> clone -1 -2
Bug #814276 [libsdl2] Non-Free file: src/stdlib/SDL_qsort.c
Bug 814276 cloned as bug 814445
> reassign -2 src:libsdl1.2
Bug #814445 [libsdl2] Non-Free file: src/stdlib/SDL_qsort.c
Bug reassigned from package 'libsdl2' to 'src:libsdl1.2'.
No longer marked as found in versions 2.0.2+dfsg1-6.
Ignoring request to alter fixed versions of bug #814445 to the same values 
previously set

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

Bug#814276: Non-Free file: src/stdlib/SDL_qsort.c

[Manuel A. Fernandez Montecelo]

Control: tags -1 + upstream
Control: clone -1 -2
Control: reassign -2 src:libsdl1.2


Hi,

2016-02-09 20:45 stresswa...@ruggedinbox.com:


Package: libsdl2
Version: 2.0.2+dfsg1-6
Severity: serious

The file 'src/stdlib/SDL_qsort.c' in SDL2 seems to disallow
modification.


Thanks for the report.

This also affects v1.2, this file has been there since forever, so I am
cloning the bug report there.

We're in contact with upstream to try to solve the problem, since it
also affects them.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#791232: openvrml NMU

[tony]

Hi Wookey,

Just a quick response - I haven't yet had any time to dig into this in
any detail, but also didn't want your email to go un-answered.

First of all, thank you for working on this!  I don't have any direct
involvement with openvrml aside from trying to keep it in (and others
like it) in the archive when it seems like there is a userbase.

I can file a transition bug if we want to go that route.  The primary
benenfit I see there is that the buildds will automatically do binNMUs
of the r-deps, so for a package with a small set of r-deps, maybe it's
not worth it.  I will take a look at that.

As far as performing an upload, I should be able to do it without
requiring an NMU.  I'll take a look at that too, but it make take a week
or so.

Cheers,
tony

On Tue, Feb 09, 2016 at 08:09:37PM +, Wookey wrote:
> OK. I just tested the fixes in openvrml for building on new arches (arm64, 
> ppc64le, ppc64)
> And I included the java fixes so that it would build.
> But now neither of us can upload our NMU due to this g++-5 ABI issue.
> 
> The maintainer seems to be MIA (Sam - are you out there?) so I'd very
> much like to just upload something if we can.
> 
> If we were really keen we'd do a library transition just to be on the
> safe side. Does anyone know what's involved with that?
> 
> openvrml is kind of old and unloved these days, but I would expect
> some software to be using it as it's a file format still supported by
> some things. libg3d, meshlab and openscenegraph claim vrml support for
> example? Did they drop it, do we not build the osg-vrml plugin,
> perhaps they have internal code for reading? These are questions the
> maintainer should be able to help answer.
> 
> I've tried a build but it failed after the src build, because debian
> patches back in Makefile.am a 'lookat' target into, the source file
> for which was removed in 2006! after dh_autoreconfing this gets back
> into the build and it barfs.
> 
> GUess I'd better fix that and try again...
> 
> Wookey
> -- 
> Principal hats:  Linaro, Debian, Wookware, ARM
> http://wookware.org/




signature.asc
Description: Digital signature

Bug#811708: pong on update-rc.d

[Benda Xu]

Hey guys,

Thanks for the report.  update-rc.d in OpenRC is a hack based on that
from sysv-rc.  I think the right way forward is to extend
init-system-helpers to support OpenRC.

I will try to figure it out.  If I couldn't make it in time, Svante's
patch will be upload to close this bug.

Cheers,
Benda

Processed: tagging 813951, tagging 814177, tagging 814165, tagging 814162, tagging 814159, tagging 775775 ...

[Debian Bug Tracking System]

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

> tags 813951 + sid stretch
Bug #813951 [src:freefoam] freefoam: FTBFS with libopenmpi 1.10
Added tag(s) stretch and sid.
> tags 814177 + sid stretch
Bug #814177 [src:jalview] jalview: (Build-)Depends on OpenJDK 7
Added tag(s) stretch and sid.
> tags 814165 + sid
Bug #814165 [src:jcc] jcc: (Build-)Depends on OpenJDK 7
Added tag(s) sid.
> tags 814162 + sid stretch
Bug #814162 [src:hyperestraier] hyperestraier: (Build-)Depends on OpenJDK 7
Added tag(s) sid and stretch.
> tags 814159 + sid stretch
Bug #814159 [src:avian] avian: (Build-)Depends on OpenJDK 7
Added tag(s) sid and stretch.
> tags 775775 + sid stretch
Bug #775775 [ca-certificates-java] ca-certificates-java: please add support for 
openjdk-8
Added tag(s) stretch and sid.
> tags 760928 + sid
Bug #760928 [src:openvrml] openvrml: ftbfs with OpenJDK 8
Added tag(s) sid.
> tags 757536 + sid stretch
Bug #757536 [src:eclipse] eclipse: FTBFS with Java 8: Duplicate methods named 
spliterator with the parameters () and ()
Added tag(s) sid and stretch.
> tags 748045 + sid
Bug #748045 [src:openvrml] openvrml: FTBFS with Java 8: cannot stat 
'./javadoc/resources/*': No such file or directory
Added tag(s) sid.
> tags 814378 + experimental
Bug #814378 [kmail] dependency libkf5akonadisearchdebug5 unavailable
Added tag(s) experimental.
> tags 814160 + sid
Bug #814160 {Done: David Prévot } [src:doc-linux-fr] 
doc-linux-fr: (Build-)Depends on OpenJDK 7
Added tag(s) sid.
> tags 814180 + sid stretch
Bug #814180 [src:piespy] piespy: (Build-)Depends on OpenJDK 7
Added tag(s) stretch and sid.
> tags 814170 + sid
Bug #814170 [src:pegasus-wms] pegasus-wms: (Build-)Depends on OpenJDK 7
Added tag(s) sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
748045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748045
757536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757536
760928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760928
775775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775775
813951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813951
814159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814159
814160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814160
814162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814162
814165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814165
814170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814170
814177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814177
814180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814180
814378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814161: marked as done (drmips: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 00:34:12 +
with message-id 
and subject line Bug#814161: fixed in drmips 2.0.1-2
has caused the Debian Bug report #814161,
regarding drmips: (Build-)Depends on OpenJDK 7
to be marked as done.

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

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


-- 
814161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:drmips
Version: 2.0.1-1
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
Source: drmips
Source-Version: 2.0.1-2

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

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

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

Debian distribution maintenance software
pp.
Bruno Nova  (supplier of updated drmips 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: Thu, 11 Feb 2016 12:47:04 +
Source: drmips
Binary: drmips
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: low
Maintainer: Bruno Nova 
Changed-By: Bruno Nova 
Description:
 drmips - Educational MIPS simulator
Closes: 814161
Changes:
 drmips (2.0.1-2) unstable; urgency=low
 .
   * debian/control: Depend on default-jre and Build-Depend on default-jdk,
 instead of on a specific version of openjdk (Closes: #814161).
Checksums-Sha1:
 0f48e23e3e9875ef2fba03a29e7a0035ca10e1d7 1837 drmips_2.0.1-2.dsc
 3901906ae0c27e7eb12d49012ddf0caf4e9cd5f1 7524 drmips_2.0.1-2.debian.tar.xz
Checksums-Sha256:
 51791034521eeed9447e007e6ec003cd5f58ff41deb9499a2f72f91d747cec35 1837 
drmips_2.0.1-2.dsc
 1cecfbc74c0e74e7f0dffcdde06ddd3d429bfda98811675305ee589b09be56ad 7524 
drmips_2.0.1-2.debian.tar.xz
Files:
 9e4186fb63cf09fe34fcfc4b4798f9ea 1837 electronics optional drmips_2.0.1-2.dsc
 dce24e77896dcda3eea5cb7bb856053f 7524 electronics optional 
drmips_2.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWvSSRAAoJEN5juccE6+nvmNEP/A76Xpv2gOon/v7vyQ7+faHR
84xhmgIH+eT+qREpjILB+hFpbJbC/R2r8g1rXwoqywk64cTbXXlW9EHSbropB85D
70lzQG9llppS3IcUel+zvT++dZlMH7w5kEsu8XcZNJUdSlNA7fG2Qo/lqszvBhFb
rdxWjhcGltjV5QE3CL3YIN8DhiFYtNtt8yrmx9v7w05oJ9g3fipfn/0yOpoNtwz1
iqapoSGoAlFO0tPQSJP1TAD9huDPNDv+hAzN98ZKsEDj87A0iPm5KIbhy/jt9d5H
x6iI9ehxU7qtP3KAtvC2zaleWVydQKghFb4zFjeWj4iNF4ZPhEWPh9bI4kC3xDrM
481KmPGHrWFegVCvqDrlDhEruYhhH/DWlAspuyAIwf8KZLxTsbltv+XaLV7NMniK
bha17vEFasbDpbeLMyrkYySsAwGxdoU7PS4X9rboWIsvZKeURBmWksofk53vgNmf
GhsUDVWBFJYxMCn92thZDTNRBQM/Obiw7zx6CpFd/nTm6toD59LqcSn9eiKocEx1
Ri37dbr1x/5GP3nd/5Ge1mrwY/MiDPf9DB2Rza4ND390HWPGoshkkTApm/Lu+Lbb
3FMXFCGLa+wrTymbfaDnaqOkcS1qvmP/Dg3Fl+WlENJf6JV9ZcjcAJ+oforgS3HP
dzbBHnBpKN278vSBsBU5
=lUl1
-END PGP SIGNATURE End Message ---

Bug#813885: marked as done (cppo: Missing native libraries)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 00:05:26 +
with message-id 
and subject line Bug#813885: fixed in cppo 1.3.1-2
has caused the Debian Bug report #813885,
regarding cppo: Missing native libraries
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.)


-- 
813885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cppo
Version: 1.3.1-1
Severity: grave
Tags: patch

Dear Maintainer,

On architectures with OCaml support for native compilation, cppo 1.3.1-1
is missing the native libraries. (They were there in 1.1.2-2.) The patch
below fixes this problem (tested on amd64 and ppc64le), I have committed
that to the git repository.

Cheers,
-Hilko

diff --git a/debian/rules b/debian/rules
index 8d769dc..6339d8a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -26,4 +26,4 @@ endif
 .PHONY: override_dh_auto_install
 override_dh_auto_install:
mkdir -p $(OCAMLFIND_DESTDIR)
-   make install 'BINDIR=$(DESTDIR)/usr/bin' BEST=$(OCAML_BEST)
+   make install 'BINDIR=$(DESTDIR)/usr/bin'
--- End Message ---
--- Begin Message ---
Source: cppo
Source-Version: 1.3.1-2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated cppo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 12 Feb 2016 00:34:00 +0100
Source: cppo
Binary: cppo
Architecture: source
Version: 1.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Hilko Bengen 
Description:
 cppo   - cpp for OCaml
Closes: 813885
Changes:
 cppo (1.3.1-2) unstable; urgency=medium
 .
   * Team upload
   * Install native libraries where available (Closes: #813885)
Checksums-Sha1:
 8dd554a4f975c260663709a02492e9c5964d1f32 1939 cppo_1.3.1-2.dsc
 8c67ecee1d62c3637800d5d6515001b1e5a6c4ec 4552 cppo_1.3.1-2.debian.tar.xz
Checksums-Sha256:
 8b0a123098532f4f7948094d9699a8b7414a477d4a9a85009bb9b7d69836f400 1939 
cppo_1.3.1-2.dsc
 fbcb60f6f7ba8bb0c32b6328ee469c422cf16c0f7c86708fae9f8f30edf671fd 4552 
cppo_1.3.1-2.debian.tar.xz
Files:
 8259749bafba5cbc76eb8e922477b34d 1939 ocaml optional cppo_1.3.1-2.dsc
 6fba8fcfd3210ae21cf9d0022ce56b2a 4552 ocaml optional cppo_1.3.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWvRzhAAoJEHW3EGNcITp+e/oQAJUDmHWBmh6FdcZlim1L1+dD
lFYpFuP2mDP4lNyoaa8huDVx97O3teDz85RC8LKN6rFBxbZouuRkEmZKJ5E21xhf
88wz9B4nAD8la6Cu4qvoQ1sFRvLa6BYtw4q2VwgPdkT67BPDxzOiaGWWHY0xNbi2
FDXuHPr8Yx/tQLnLkKqLPC1Ah9CWMeQCpK99NyT7MmpQVDwA69raEsFWNY0n/lhx
B7aHms305mop+oUBDffSztR9toCqbtDC/WDQKh5Q5ydeop61zaf6/nwtlnemr0eM
3CdmxC3Gm0S+S/YQ4XLg3N+foA5XvpUfQUrp+4UfkmX7NSdt8emXtI342Pp5cgy6
5vBTgEFKbX9gs9EbzAPRMuaXXcKEWgbH0fqu7nSwdyj+5zv07V29yuubj4iPNndy
LYnNeg1YP8w/eAY5jMkWRSdegsTsNIu/EDNUrz5fqB5MW6ETdV586T66TPe/fak3
9259oduWjTVegnx/tUcSH1Q/9zmQUAkw+gXSENeHz+HPCyUU/jlNxeAENOY3SIY+
uir5eCTVa9mCiKBD+Hz+AialuzlZ7ZzplM9Ik8xLbRGX2xqpwhkbSYOUgYEsEZOq
Kw3NQsCwxkOMXbhciHOti0iy1agV4vnyuuRbAJ/557/NXjhESf9dP1FO/6guIKRU
VH4XOXoGd1plpa5nYW3s
=PwD5
-END PGP SIGNATURE End Message ---

Bug#814404: marked as done (etcd: FTBFS: rpc.pb.go:534: cannot use _Etcd_Range_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) as type grpc.methodHandler i

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 00:49:09 +
with message-id 
and subject line Bug#814404: fixed in etcd 2.2.5+dfsg-1
has caused the Debian Bug report #814404,
regarding etcd: FTBFS: rpc.pb.go:534: cannot use _Etcd_Range_Handler (type 
func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) 
as type grpc.methodHandler in field value
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.)


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

etcd fails to build from source in unstable/amd64:

  [..]

  github.com/prometheus/client_golang/prometheus
  github.com/boltdb/bolt
  github.com/coreos/etcd/etcdserver/etcdserverpb
  github.com/coreos/etcd/storage/backend
  # github.com/coreos/etcd/etcdserver/etcdserverpb
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:534: cannot use 
_Etcd_Range_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:538: cannot use 
_Etcd_Put_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) 
(interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:542: cannot use 
_Etcd_DeleteRange_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:546: cannot use 
_Etcd_Txn_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) 
(interface {}, error)) as type grpc.methodHandler in field value
  src/github.com/coreos/etcd/etcdserver/etcdserverpb/rpc.pb.go:550: cannot use 
_Etcd_Compact_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
  github.com/google/btree
  github.com/coreos/etcd/rafthttp
  github.com/coreos/etcd/snap
  github.com/coreos/etcd/storage
  github.com/coreos/etcd/store
  github.com/coreos/etcd/pkg/crc
  github.com/coreos/etcd/wal/walpb
  github.com/coreos/etcd/wal
  golang.org/x/crypto/blowfish
  github.com/coreos/etcd/pkg/cors
  golang.org/x/crypto/bcrypt
  github.com/coreos/etcd/pkg/transport
  github.com/coreos/etcd/pkg/osutil
  github.com/coreos/etcd/proxy
  github.com/coreos/go-systemd/daemon
  github.com/coreos/go-systemd/util
  github.com/coreos/etcd/pkg/flags
  golang.org/x/net/netutil
  github.com/codegangsta/cli
  github.com/coreos/etcd/Godeps/_workspace/src/github.com/bgentry/speakeasy
  github.com/coreos/etcd/integration
  github.com/coreos/etcd/pkg/testutil
  github.com/coreos/etcd/raft/rafttest
  github.com/coreos/etcd/tools/functional-tester/etcd-agent/client
  github.com/coreos/etcd/Godeps/_workspace/src/github.com/rakyll/pb
  github.com/coreos/etcd/tools/functional-tester/etcd-agent
  github.com/coreos/etcd/client
  github.com/coreos/etcd/discovery
  github.com/coreos/etcd/tools/functional-tester/etcd-tester
  dh_auto_build: go install -v github.com/coreos/etcd 
github.com/coreos/etcd/client github.com/coreos/etcd/discovery 
github.com/coreos/etcd/error github.com/coreos/etcd/etcdctl 
github.com/coreos/etcd/etcdctl/command github.com/coreos/etcd/etcdctlv3 
github.com/coreos/etcd/etcdctlv3/command github.com/coreos/etcd/etcdmain 
github.com/coreos/etcd/etcdserver github.com/coreos/etcd/etcdserver/api/v3rpc 
github.com/coreos/etcd/etcdserver/auth 
github.com/coreos/etcd/etcdserver/etcdhttp 
github.com/coreos/etcd/etcdserver/etcdhttp/httptypes 
github.com/coreos/etcd/etcdserver/etcdserverpb 
github.com/coreos/etcd/etcdserver/stats github.com/coreos/etcd/integration 
github.com/coreos/etcd/pkg/cors github.com/coreos/etcd/pkg/crc 
github.com/coreos/etcd/pkg/fileutil github.com/coreos/etcd/pkg/flags 
github.com/coreos/etcd/pkg/httputil github.com/coreos/etcd/pkg/idutil 
github.com/coreos/etcd/pkg/ioutil github.com/coreos/etcd/pkg/netutil 
github.com/coreos/etcd/pkg/osutil github.com/coreos/etcd/pkg/pathutil 
github.com/coreos/etcd/pkg/pbutil github.com/coreos/etcd/pkg/runtime 
github.com/coreos/etcd/pkg/testutil github.com/coreos/etcd/pkg/timeutil 
github.com/coreos/etcd/pkg/transport 

Bug#752821: marked as done (sshmenu: not installable in sid)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 01:06:36 +
with message-id 
and subject line Bug#814256: Removed package(s) from unstable
has caused the Debian Bug report #752821,
regarding sshmenu: not installable in sid
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.)


-- 
752821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sshmenu
Version: 3.18-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hello,

sshmenu is not installable in sid, at least since 2014-04-05 :
No package matches the dependency libgtk2-ruby of package sshmenu (=3.18-2)

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 3.18-2+rm

Dear submitter,

as the package sshmenu 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/814256

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#677595: marked as done (sshmenu: won't start : `require': cannot load such file -- sshmenu (LoadError))

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 01:06:36 +
with message-id 
and subject line Bug#814256: Removed package(s) from unstable
has caused the Debian Bug report #677595,
regarding sshmenu: won't start : `require': cannot load such file -- sshmenu 
(LoadError)
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.)


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

Hi.

Here's what I get :
$ sshmenu 
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
such file -- sshmenu (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/bin/sshmenu:3:in `'

then nothing :-(

Thanks in advance.

Best regards,

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sshmenu depends on:
ii  libgtk2-ruby 1.1.3-2
ii  libruby  4.9
ii  ruby 4.9
ii  ruby-gtk2 [libgtk2-ruby] 1.1.3-2+b1
ii  ruby1.8 [ruby]   1.8.7.358-4
ii  ssh-askpass  1:1.2.4.1-9
ii  ssh-askpass-gnome [ssh-askpass]  1:6.0p1-1

sshmenu recommends no packages.

sshmenu suggests no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Version: 3.18-2+rm

Dear submitter,

as the package sshmenu 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/814256

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#756871: marked as done (fatrat-unpack: non-distributable: GPL'd code linked to non-GPL unrar library)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 01:10:01 +
with message-id 
and subject line Bug#814357: Removed package(s) from unstable
has caused the Debian Bug report #756871,
regarding fatrat-unpack: non-distributable: GPL'd code linked to non-GPL unrar 
library
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.)


-- 
756871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fatrat-unpack
Version: 1.1.3-2
Severity: serious
Tags: upstream
Justification: Policy 2.3

While investigating #739308 I noticed that fatrat-unpack is licensed under
the GPL without any apparent non-GPL-linking exceptions, but links to
code that imposes restrictions beyond those of the GPL (the non-Free unrar
library). This means Debian does not have permission to distribute the
resulting binaries.

The authors of fatrat-unpack probably intended to be licensing it under
the GPL with a special exception that it may be linked to the non-Free
unrar code. However, they don't seem to have explicitly said so.

If the copyright holders are willing to relicense fatrat-unpack under
"GPL with exception" terms, similar to the exception documented in
http://metadata.ftp-master.debian.org/changelogs/main/w/wget/unstable_copyright
in which the copyright holders explicitly allow linking it to OpenSSL,
that would solve this.

Regards,
S

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

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 1.1.3-2+rm

Dear submitter,

as the package fatrat-unpack 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/814357

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#713663: marked as done (fatrat: FTBFS: config.hpp:46:2: error: #error you must define either BOOST_ASIO_SEPARATE_COMPILATION or BOOST_ASIO_DYN_LINK in your project in order for asio's declarations

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 01:10:19 +
with message-id 
and subject line Bug#814357: Removed package(s) from unstable
has caused the Debian Bug report #713663,
regarding fatrat: FTBFS: config.hpp:46:2: error: #error you must define either 
BOOST_ASIO_SEPARATE_COMPILATION or BOOST_ASIO_DYN_LINK in your project in order 
for asio's declarations to be correct. If you're linking dynamically against 
libtorrent, define BOOST_ASIO_DYN_LINK otherwise 
BOOST_ASIO_SEPARATE_COMPILATION. You can also use pkg-config or boost build, to 
automatically apply these defines
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.)


-- 
713663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fatrat
Version: 1.1.3-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /usr/bin/c++   -DBOOST_FILESYSTEM_VERSION=2 -DNDEBUG -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_HELP_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
> -DQT_SCRIPT_LIB -DQT_SVG_LIB -DQT_WEBKIT_LIB -DQT_XML_LIB -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -I/«PKGBUILDDIR»/src 
> -I/usr/include/libtorrent -isystem /usr/include/qt4 -isystem 
> /usr/include/qt4/QtScript -isystem /usr/include/qt4/QtSvg -isystem 
> /usr/include/qt4/QtHelp -isystem /usr/include/qt4/QtWebKit -isystem 
> /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtDBus -isystem 
> /usr/include/qt4/QtXml -isystem /usr/include/qt4/QtNetwork -isystem 
> /usr/include/qt4/QtCore -I/«PKGBUILDDIR»/. -I/«PKGBUILDDIR»/.. 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu-ggdb -o 
> CMakeFiles/fatrat.dir/src/AppTools.cpp.o -c /«PKGBUILDDIR»/src/AppTools.cpp
> In file included from /usr/include/libtorrent/entry.hpp:68:0,
>  from /usr/include/libtorrent/bencode.hpp:81,
>  from /usr/include/libtorrent/create_torrent.hpp:36,
>  from /«PKGBUILDDIR»/src/tools/CreateTorrentDlg.h:35,
>  from /«PKGBUILDDIR»/src/AppTools.cpp:35:
> /usr/include/libtorrent/config.hpp:46:2: error: #error you must define either 
> BOOST_ASIO_SEPARATE_COMPILATION or BOOST_ASIO_DYN_LINK in your project in 
> order for asio's declarations to be correct. If you're linking dynamically 
> against libtorrent, define BOOST_ASIO_DYN_LINK otherwise 
> BOOST_ASIO_SEPARATE_COMPILATION. You can also use pkg-config or boost build, 
> to automatically apply these defines
>  #error you must define either BOOST_ASIO_SEPARATE_COMPILATION or 
> BOOST_ASIO_DYN_LINK in your project in \
>   ^
> make[3]: *** [CMakeFiles/fatrat.dir/src/AppTools.cpp.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/fatrat_1.1.3-5_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.1.3-5+rm

Dear submitter,

as the package fatrat 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/814357

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#813783: marked as done (plexus-component-metadata: FTBFS: [ERROR] Cannot find parent dependency org.codehaus.plexus:plexus-containers:pom:debian)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 01:11:11 +
with message-id 
and subject line Bug#814410: Removed package(s) from unstable
has caused the Debian Bug report #813783,
regarding plexus-component-metadata: FTBFS: [ERROR] Cannot find parent 
dependency org.codehaus.plexus:plexus-containers:pom:debian
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.)


-- 
813783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plexus-component-metadata
Version: 1.0~beta3.0.7-5
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,

plexus-component-metadata fails to build from source in unstable/amd64:

  [..]


  init.pom:
   [echo] Base dir is 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7
   [echo] Pom name in 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/debian/libplexus-component-metadata-java.poms:
 pom.xml
   [echo] Pom file pom.xml available? true
  
  read.pom:
  [mkdir] Created dir: 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/debian/.mh
   [echo] Cleaner options:
   [java] Cleaning POM 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/pom.xml,
 saving the result into 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/debian/.mh/pom.xml
   [java] maven.rules:
   [java]   asm * * s/3\..*/3.x/
   [java]   junit junit jar s/3\..*/3.x/
   [java]   s/jdom/org.jdom/ jdom jar s/.*/debian/
   [java] -
   [java] Rules file does not exist: 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/debian/maven.publishedRules
   [java] [ERROR] Cannot find parent dependency 
org.codehaus.plexus:plexus-containers:pom:debian, use --no-parent option to 
resolve this issue or install the parent POM in the Maven repository
   [copy] Copying 1 file to 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7
   [copy] Copying 1 file to 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7
   [echo] Properties read from the POM file:
   [echo]   groupId: org.codehaus.plexus, artifactId: 
plexus-component-metadata, version: 1.0-beta-3.0.7, debianVersion: 
1.0-beta-3.0.7
  
  init:
   [echo] Compile classpath: target/classes:
   [echo] Test classpath: target/test-classes::target/classes:
  
  process-resources:
  [mkdir] Created dir: 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/target/classes
   [copy] Copying 1 file to 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/target/classes
  
  process-pom:
  [mkdir] Created dir: 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/target/classes/META-INF/maven/org.codehaus.plexus/plexus-component-metadata
   [copy] Copying 2 files to 
/home/lamby/temp/cdt.20160205085221.tfROdSWNGc/plexus-component-metadata-1.0~beta3.0.7/target/classes/META-INF/maven/org.codehaus.plexus/plexus-component-metadata
  
  mvn-generate:
  
  mvn-shared-repo:
   [java] + Error stacktraces are turned on.
   [java] [INFO] 
   [java] NOTE: Maven is executing in offline mode. Any artifacts not 
already in your local
   [java] repository will be inaccessible.
   [java] 
   [java] [INFO] Scanning for projects...
   [java] [INFO] Searching repository for plugin with prefix: 'plugin'.
   [java] [INFO] 

   [java] [INFO] Building Plexus :: Component Metadata
   [java] [INFO]task-segment: [plugin:descriptor]
   [java] [INFO] 

   [java] [INFO] 

   [java] [ERROR] BUILD ERROR
   [java] [INFO] 

   [java] [INFO] Failed to resolve artifact.
   [java] 
   [java] Missing:
   [java] --
   [java] 1) org.codehaus.plexus:plexus-utils:jar:2.x
   [java] 
   [java]   Try downloading the file 

Bug#814480: imagemagick: cannot upgrade: /usr/share/doc/imagemagick contains files not owned by package imagemagick:all

[Vincent Lefevre]

Package: imagemagick
Version: 8:6.9.2.10+dfsg-2
Severity: grave
Justification: renders package unusable

When upgrading, I get the following error:

dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick' contains 
files not owned by package imagemagick:all, cannot switch to symlink
dpkg: error processing archive 
/var/cache/apt/archives/imagemagick_8%3a6.9.2.10+dfsg-2_all.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/imagemagick_8%3a6.9.2.10+dfsg-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- Package-specific info:
ImageMagick program version
---
animate: compare: convert: composite: conjure: display: identify: import: 
mogrify: montage: stream: 
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages imagemagick depends on:
iu  imagemagick-6.q16  8:6.9.2.10+dfsg-2

imagemagick recommends no packages.

imagemagick suggests no packages.

-- no debconf information

Bug#814476: gitlab writes into /usr/share/gitlab during operation

[Johannes Schauer]

Package: gitlab
Version: 8.4.3+dfsg-3
Severity: serious
Justification: Policy 9.1.1

Hi,

as per Debian policy §9.1.1, packages must comply with the FHS 2.3 but
gitlab is writing log files to /usr/share/gitlab/log/ which violates
chapter 4 of the FHS. Quote:

"/usr is the second major section of the filesystem. /usr is shareable,
read-only data. That means that /usr should be shareable between various
FHS-compliant hosts and must not be written to. Any information that is
host-specific or varies with time is stored elsewhere."

this requirement is currently violated by gitlab.

No wonder I couldn't figure out where the log files were :D

Log files should go into /var/log/gitlab

Thanks!

cheers, josch

Bug#808593: [Help]: Bug#808593: htsjdk: FTBFS: [testng] FAILED: testHTTPNotExist

[Emmanuel Bourg]

Le 11/02/2016 21:01, Andreas Tille a écrit :

> any hint why this test that worked before might fail since end of
> December?

I got a quick look and I can't explain this test failure. It doesn't
seem very important though, you could just disable this test.

Emmanuel Bourg

Bug#814183: openmpi 1.10.2 is broken on powerpc

[Emilio Pozuelo Monfort]

On Tue, 9 Feb 2016 21:49:29 +0200 Graham Inggs  wrote:
> Petsc rebuilt successfully [1] a couple of hours ago on poulenc.d.o. [2].
> My previous tests were done on partch.d.o. [3].  Partch has 2GB of RAM
> vs Poulenc's 5GB, I don't know if this is significant.

aces3 failed on powerpc-osuosl-01.

poulenc is a PPC970FX
patch is a POWER7
powerpc-osuosl-01 is a POWER8

Dunno if that is relevant.

Cheers,
Emilio

Bug#814473: elpa: FTBFS: find: '/usr/share/libtool/config/ltmain.sh': No such file or directory

[Andreas Beckmann]

Source: elpa
Version: 2015.05.001-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

elpa FTBFS everywhere on the buildds:

https://buildd.debian.org/status/package.php?p=elpa=unstable
https://buildd.debian.org/status/fetch.php?pkg=elpa=i386=2015.05.001-1=1454891876

 debian/rules build-arch
dh build-arch --with autoreconf
   dh_testdir -a
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_autoreconf --as-needed
find: '/usr/share/libtool/config/ltmain.sh': No such file or directory
dh_autoreconf: find /usr/share/libtool/config/ltmain.sh . ! -ipath "./debian/*" 
-a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o -path '*/.bzr/*' -o -path 
'*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} \; > 
debian/autoreconf.before returned exit code 1
debian/rules:14: recipe for target 'override_dh_autoreconf' failed
make[1]: *** [override_dh_autoreconf] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:11: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2


I cannot reproduce this in a sid pbuilder environment.


Andreas

Bug#814334: marked as done (scalapack: please update the list of openmpi/mpich arch)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 23:21:16 +
with message-id 
and subject line Bug#814334: fixed in scalapack 1.8.0-12.3
has caused the Debian Bug report #814334,
regarding scalapack: please update the list of openmpi/mpich arch
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.)


-- 
814334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scalapack
Version: 1.8.0-12.2
Severity: serious

So, this morning I switched the default MPI implementation in s390x from
mpich to openmpi, and figured just now that scalapack needs a sourceful
change for it.

Attached a patch for it.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for scalapack-1.8.0 scalapack-1.8.0

 changelog |7 +++
 control   |   12 ++--
 rules |4 ++--
 3 files changed, 15 insertions(+), 8 deletions(-)

diff -Nru scalapack-1.8.0/debian/changelog scalapack-1.8.0/debian/changelog
--- scalapack-1.8.0/debian/changelog2016-02-05 14:31:33.0 +
+++ scalapack-1.8.0/debian/changelog2016-02-10 13:39:54.0 +
@@ -1,3 +1,10 @@
+scalapack (1.8.0-12.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update the list of MPI architecture.  s390x switched to OpenMPI.
+
+ -- Mattia Rizzolo   Wed, 10 Feb 2016 13:39:15 +
+
 scalapack (1.8.0-12.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru scalapack-1.8.0/debian/control scalapack-1.8.0/debian/control
--- scalapack-1.8.0/debian/control  2016-02-05 14:31:35.0 +
+++ scalapack-1.8.0/debian/control  2016-02-10 13:39:58.0 +
@@ -13,7 +13,7 @@
 
 Package: libscalapack-openmpi1
 Section: libs
-Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64el sparc
+Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64el sparc s390x
 Depends: mpi-default-bin, ${shlibs:Depends}, ${misc:Depends}
 Conflicts: scalapack1-mpich, scalapack1-lam
 Breaks: libscalapack-mpi1 (<< 1.8.0-9.1)
@@ -31,7 +31,7 @@
 
 Package: libscalapack-mpich1
 Section: libs
-Architecture: hppa m68k powerpcspe ppc64 s390x sparc64
+Architecture: hppa m68k powerpcspe ppc64 sparc64
 Depends: mpi-default-bin, ${shlibs:Depends}, ${misc:Depends}
 Conflicts: scalapack1-mpich, scalapack1-lam
 Breaks: libscalapack-mpi1 (<< 1.8.0-9.1)
@@ -49,9 +49,9 @@
 
 Package: libscalapack-mpi-dev
 Section: libdevel
-Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64el sparc hppa m68k 
powerpcspe ppc64 s390x sparc64
-Depends: libscalapack-openmpi1 (= ${binary:Version}) [alpha amd64 arm64 armel 
armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel mips64 mips64el 
powerpc ppc64el sparc],
- libscalapack-mpich1 (= ${binary:Version}) [hppa m68k powerpcspe ppc64 
s390x sparc64],
+Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64el sparc s390x hppa m68k 
powerpcspe ppc64 sparc64
+Depends: libscalapack-openmpi1 (= ${binary:Version}) [alpha amd64 arm64 armel 
armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel mips64 mips64el 
powerpc ppc64el sparc s390x],
+ libscalapack-mpich1 (= ${binary:Version}) [hppa m68k powerpcspe ppc64 
sparc64],
  libblacs-mpi-dev, ${misc:Depends}
 Conflicts: scalapack-mpich-dev, scalapack-lam-dev
 Replaces: scalapack-mpich-dev, scalapack-lam-dev
@@ -71,7 +71,7 @@
 
 Package: scalapack-mpi-test
 Section: math
-Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64el sparc hppa m68k 
powerpcspe ppc64 s390x sparc64
+Architecture: alpha amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64el sparc s390x hppa m68k 
powerpcspe ppc64 sparc64
 Depends: scalapack-test-common, ${shlibs:Depends}, ${misc:Depends}
 Conflicts: scalapack-mpich-test, scalapack-lam-test
 Replaces: scalapack-mpich-test, scalapack-lam-test
diff -Nru scalapack-1.8.0/debian/rules 

Processed: Re: FTBFS: error: 'OBEX_TRANS_CUST' undeclared

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.5.4-2.3
Bug #811300 {Done: Mattia Rizzolo } [libsyncml] FTBFS: 
error: 'OBEX_TRANS_CUST' undeclared
There is no source info for the package 'libsyncml' at version '0.5.4-2.3' with 
architecture ''
Unable to make a source version for version '0.5.4-2.3'
Marked as found in versions 0.5.4-2.3; no longer marked as fixed in versions 
libsyncml/0.5.4-2.3 and reopened.

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

Bug#811300: FTBFS: error: 'OBEX_TRANS_CUST' undeclared

[Andreas Beckmann]

Followup-For: Bug #811300
Control: found -1 0.5.4-2.3

Hi,

>   * Change B-D from libopenobex1-dev to libopenobex2-dev.

libsyncml-dev still Depends on the obsolete libopenobex1-dev.


Andreas

Bug#813063: marked as done (coq-doc: FTBFS in sid: File "kernel/univ.ml", line 229, characters 0-2: Error: This comment contains an unterminated string literal)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 22:23:10 +
with message-id 
and subject line Bug#813063: fixed in coq-doc 8.4pl4-2
has caused the Debian Bug report #813063,
regarding coq-doc: FTBFS in sid: File "kernel/univ.ml", line 229, characters 
0-2: Error: This comment contains an unterminated string literal
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.)


-- 
813063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coq-doc
Version: 8.4pl4-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source

Hi,

coq-doc FTBFS in sid and stretch. (It builds fine in jessie.)

[...]
OCAMLCkernel/univ.mli
OCAMLCkernel/univ.ml
File "kernel/univ.ml", line 229, characters 0-2:
Error: This comment contains an unterminated string literal
File "kernel/univ.ml", line 229, characters 17-20:
Error: String literal begins here
Makefile.build:853: recipe for target 'kernel/univ.cmo' failed
make[3]: *** [kernel/univ.cmo] Error 2
make[3]: Leaving directory '/build/coq-doc-8.4pl4'
Makefile:139: recipe for target 'refman' failed
make[2]: *** [refman] Error 2
make[2]: Leaving directory '/build/coq-doc-8.4pl4'
debian/rules:21: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/coq-doc-8.4pl4'
debian/rules:10: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: coq-doc
Source-Version: 8.4pl4-2

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated coq-doc 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, 11 Feb 2016 22:26:54 +0100
Source: coq-doc
Binary: coq-doc coq-doc-html coq-doc-pdf
Architecture: source all
Version: 8.4pl4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 coq-doc- documentation for Coq
 coq-doc-html - documentation for Coq in html format
 coq-doc-pdf - documentation for Coq in pdf format
Closes: 813063
Changes:
 coq-doc (8.4pl4-2) unstable; urgency=medium
 .
   * Team upload
   * patch unterminated_string_literal: fix FTBFS with ocaml 4.02.3
 (closes: #813063)
Checksums-Sha1:
 8214e7bec342a42bfd605c0d7c48086453bd0f8f 2243 coq-doc_8.4pl4-2.dsc
 47f933d45ba7140aa1b9117ff14d240c37c65de7 8404 coq-doc_8.4pl4-2.debian.tar.xz
 6bf752fae086fd79af57d3c2cd3dc8017cd66cf5 473720 coq-doc-html_8.4pl4-2_all.deb
 4350756c8063e8776a8348e384158259abef20c0 2467952 coq-doc-pdf_8.4pl4-2_all.deb
 6d1cfbd1ee5b4b5096c5b6eccf1a150d3a14002a 50462 coq-doc_8.4pl4-2_all.deb
Checksums-Sha256:
 f201ed002ffb53915d6964e545ca3dda4937ff2b87a0e3f4e5a68b60c4d568e5 2243 
coq-doc_8.4pl4-2.dsc
 061c31efe52366686526fc1d9636f584e5505a6bc4c93910965311b3830c7d28 8404 
coq-doc_8.4pl4-2.debian.tar.xz
 b624112ba962da667950a36316af845f2a5fd205617941e772a238a538a6a89c 473720 
coq-doc-html_8.4pl4-2_all.deb
 60fc068137c9b5da3b5af47c4e22c71a0d5098b2646f0873f2828c656a213dec 2467952 
coq-doc-pdf_8.4pl4-2_all.deb
 381eb08d65ea44f0378ab81403996212c096e1e6ec41eadeaf5cf72542eb739f 50462 
coq-doc_8.4pl4-2_all.deb
Files:
 4cddcfff171cc5ee808c4be2bbf862e2 2243 non-free/doc optional 
coq-doc_8.4pl4-2.dsc
 4c0a4cee245c8783497a9bcc5ba06d9a 8404 non-free/doc optional 
coq-doc_8.4pl4-2.debian.tar.xz
 512439fd435bde2a002b0788b053b4a0 473720 non-free/doc optional 
coq-doc-html_8.4pl4-2_all.deb
 21871c24e455eee22a6dcfe5628532eb 2467952 non-free/doc optional 
coq-doc-pdf_8.4pl4-2_all.deb
 d277e14458467f623aad99b7fbae665c 50462 non-free/doc optional 
coq-doc_8.4pl4-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWvQO3AAoJEHRcR2bUys3/wAIP/0CdCy79zu1Xm/kDxlYnstFh

Bug#813398: Uploaded

[Ryan Kavanagh]

Dear Leo,

I uploaded a fixed package this morning and received an email confirming that it
had been processed, though, oddly, I still haven't received an email from the
archive confirming it had been accepted. It should appear shortly I hope.

Best,
Ryan

-- 
|_)|_/  Ryan Kavanagh   | Debian Developer
| \| \  http://ryanak.ca/   | GPG Key 4A11C97A

Bug#814458: I'll fix it in next upload

[Pirate Praveen]

Thanks for the report. This is because of the following line,

echo "Initializing database..."
su ${gitlab_user} -s /bin/sh -c 'bundle exec rake gitlab:setup
RAILS_ENV=production force=yes'

I will remove that force=yes (created during the testing phase, but
never gotten to remove it).

Also because package update case is still in todo list
https://gitlab.com/debian-ruby/TaskTracker/issues/52



signature.asc
Description: OpenPGP digital signature

Processed: reassign 814069 to python-six-whl, fixed 814069 in 1.10.0-3

[Debian Bug Tracking System]

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

> reassign 814069 python-six-whl 1.10.0-2
Bug #814069 {Done: Barry Warsaw } 
[python-pip-whl,python-six-whl] python-six-whl and python-pip-whl: error when 
trying to install together
Bug reassigned from package 'python-pip-whl,python-six-whl' to 'python-six-whl'.
Ignoring request to alter found versions of bug #814069 to the same values 
previously set
No longer marked as fixed in versions six/1.10.0-3.
Bug #814069 {Done: Barry Warsaw } [python-six-whl] 
python-six-whl and python-pip-whl: error when trying to install together
Marked as found in versions six/1.10.0-2.
> fixed 814069 1.10.0-3
Bug #814069 {Done: Barry Warsaw } [python-six-whl] 
python-six-whl and python-pip-whl: error when trying to install together
There is no source info for the package 'python-six-whl' at version '1.10.0-3' 
with architecture ''
Unable to make a source version for version '1.10.0-3'
Marked as fixed in versions 1.10.0-3.
> thanks
Stopping processing here.

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

Bug#814429: marked as done (geneweb: debian/mktemplates may fail due to grep binary matching: iconv: conversion from `Binary' is not supported)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 21:51:54 +
with message-id 
and subject line Bug#814429: fixed in geneweb 6.08dfsg-4
has caused the Debian Bug report #814429,
regarding geneweb: debian/mktemplates may fail due to grep binary matching: 
iconv: conversion from `Binary' is not supported
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.)


-- 
814429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: geneweb
Version: 6.08dfsg-3.1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Build fails with
iconv: conversion from `Binary' is not supported
on ca language file. The problem is that grep matches the file as binary, and
outputs "Binary file matches", which gets (mis)parsed and screw up iconv params.
Probably dependent on the version of grep, and the phase of the moon possibly. 
:-)

This should fix it anyway:

--- debian/mktemplates  2016-02-11 14:00:53.103700366 +
+++ debian/mktemplates~ 2016-02-11 13:59:01.0 +
@@ -67,7 +67,7 @@
sed '/^\"Content-Type/s/CHARSET/UTF-8/' \
> debian/pobuild/$pofilename.temp
 
-   pocharset=`grep -ai charset $pofile|cut -f2 -d=| sed 's/n\\"//g'`
+   pocharset=`grep -i charset $pofile|cut -f2 -d=| sed 's/n\\"//g'`
cat $pofile | \
 iconv --from $pocharset --to utf-8 | \
sed "s/$pocharset/UTF-8/g" \
--- End Message ---
--- Begin Message ---
Source: geneweb
Source-Version: 6.08dfsg-4

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

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

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

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated geneweb 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, 11 Feb 2016 19:05:43 +0100
Source: geneweb
Binary: geneweb gwtp gwsetup geneweb-gui
Architecture: source i386
Version: 6.08dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Christian Perrier 
Changed-By: Christian Perrier 
Description:
 geneweb- genealogy software with web interface
 geneweb-gui - graphical user interface to Geneweb genealogy software
 gwsetup- utilities to configure and manipulate Geneweb databases
 gwtp   - web interface interacting with Geneweb databases
Closes: 808705 814429
Changes:
 geneweb (6.08dfsg-4) unstable; urgency=medium
 .
   * Update README.source to fit the switch to git. Only mention
 the use of git-import-orig.
 Closes: #808705
   * mktemplates: always treat PO files as text even when grep thinks
 they're binary data. Closes: #814429
 Thanks to Peter Gervai for the analysis of this weird cause of FTBFS
 at full moon time.
Checksums-Sha1:
 b96a3bb47f054c7cde81799931882d430935666f 2117 geneweb_6.08dfsg-4.dsc
 4d34c4d71f6646226348d3ec9f5e341511eea337 78432 geneweb_6.08dfsg-4.debian.tar.xz
 57db097ba59f5a1419ddedfc98f65ec97b0918a4 143302 
geneweb-gui-dbgsym_6.08dfsg-4_i386.deb
 05b158fbfe2914d2de1c0f0597801ea482d9b346 579724 geneweb-gui_6.08dfsg-4_i386.deb
 646532cb735b51304039f287ba3ab46396631a01 2400438 geneweb_6.08dfsg-4_i386.deb
 56f606e68ada43b8ab6dd517e386835ac0c342c0 357640 gwsetup_6.08dfsg-4_i386.deb
 ef0279b682aebb6eacd7e1020c726698ba0e78b4 356628 gwtp_6.08dfsg-4_i386.deb
Checksums-Sha256:
 56e469cc3864f44ecf7e27cf83dbb8720a370e6865d224601853c28e1330f5d9 2117 
geneweb_6.08dfsg-4.dsc
 2ab0ad5c30c49bae1e8dc029af614ccf427ac9c9ee50ade74aba3ebb59666558 78432 
geneweb_6.08dfsg-4.debian.tar.xz
 6a429aa2bbdf9080265565237953998e609685cbcbaf00869767f038d2793435 143302 
geneweb-gui-dbgsym_6.08dfsg-4_i386.deb
 d4912cebc6e376dd975697565ab2a0d365aeee8ba47706b4a8b9d9428b1bc955 579724 
geneweb-gui_6.08dfsg-4_i386.deb
 303c0ea49697aafc333c5aa01c90daa44c3bc7b996fab7cd1960de09cb46b7d1 2400438 
geneweb_6.08dfsg-4_i386.deb
 799052e1fbcf639df1843b94713ded90e30886c977f91ea461507ebc259f8da6 357640 
gwsetup_6.08dfsg-4_i386.deb
 

Bug#814467: python-urllib3-whl: depends on removed python-six-whl

[Andreas Beckmann]

Package: python-urllib3-whl
Version: 1.13.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

your package depends on python-six-whl which is no longer built by src:six.
python-urllib3-whl will become uninstallable once this gets decrufted from sid.


Cheers,

Andreas

Processed: severity of 814403 is normal

[Debian Bug Tracking System]

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

> severity 814403 normal
Bug #814403 [src:ckeditor] ckeditor: FTBFS: /usr/bin/ckbuilder: 2: 
/usr/bin/ckbuilder: Syntax error: Unterminated quoted string
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: Bug#814467 marked as pending

[Debian Bug Tracking System]

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

> tag 814467 pending
Bug #814467 [python-urllib3-whl] python-urllib3-whl: depends on removed 
python-six-whl
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#814467: marked as pending

[Daniele Tricoli]

tag 814467 pending
thanks

Hello,

Bug #814467 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=python-modules/packages/python-urllib3.git;a=commitdiff;h=a42d469

---
commit a42d46986aa2946ac97888ede17d73fff3c92e70
Author: Daniele Tricoli 
Date:   Fri Feb 12 01:33:47 2016 +0100

Update changelog

diff --git a/debian/changelog b/debian/changelog
index d902281..9cb58ff 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+python-urllib3 (1.13.1-2) UNRELEASED; urgency=medium
+
+  * debian/control
+- Remove python-urllib3-whl and python3-wheel B-D. (Closes: #814467)
+- Use secure URI for Vcs-Git.
+- Bump Standards-Version to 3.9.7 (no changes needed).
+- Bump X-Python3-Version to >= 3.2.
+  * debian/copyright
+- Update copyright years.
+  * debian/python-urllib3-whl.install
+- Remove.
+  * debian/rules
+- Remove override_dh_auto_install since it's no longer needed to build the
+  wheel package.
+
+ -- Daniele Tricoli   Fri, 12 Feb 2016 01:35:42 +0100
+
 python-urllib3 (1.13.1-1) unstable; urgency=medium
 
   * New upstream release.

Bug#814350: wine: recommended package libwine-gecko-2.40 is not in main

[Jens Reyer]

control: tags -1 + pending

On 02/10/2016 06:12 PM, Jens Reyer wrote:
> Imo the dependency on libwine-gecko-xxx should stay a recommends, a
> suggests imo doesn't meet the importance of Gecko in Wine.
> 
> So I'll commit a change to remove (comment) that from wine and
> wine-development.

Committed for both wine and wine-development. On a second thought I
decided to use suggests as you suggested. We should revert that as soon
as the correct version of libwine-gecko is available.

Greets
jre

Processed: Re:Bug#814350: wine: recommended package libwine-gecko-2.40 is not in main

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #814350 [wine] wine: recommended package libwine-gecko-2.40 is not in main
Added tag(s) pending.

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

Bug#812999: marked as done (flashcache: we are not correctly recording the bio error code in 4.3)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 04:19:51 +
with message-id 
and subject line Bug#812999: fixed in flashcache 3.1.3+git20150701-3
has caused the Debian Bug report #812999,
regarding flashcache: we are not correctly recording the bio error code in 4.3
to be marked as done.

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

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


-- 
812999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flashcache
Version: 3.1.3+git20150701-2
Severity: serious
Tags: patch
User: a...@ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

While merging up the Ubuntu delta with the current flashcache it looks
very much like we are not correctly passing over the BIO error code in
the 4.3 compatibility code.

We have the attached patch applied to correct this.  Looking at upstream
they also have fixed the 4.3 issue in the same manner.

Cheers.

-apw


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

Kernel: Linux 4.3.0-5-generic (SMP w/4 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)
diff -Nru flashcache-3.1.3+git20150701/debian/patches/record-bio-error-on-linux-4.3.patch flashcache-3.1.3+git20150701/debian/patches/record-bio-error-on-linux-4.3.patch
--- flashcache-3.1.3+git20150701/debian/patches/record-bio-error-on-linux-4.3.patch	1970-01-01 01:00:00.0 +0100
+++ flashcache-3.1.3+git20150701/debian/patches/record-bio-error-on-linux-4.3.patch	2016-01-28 12:20:13.0 +
@@ -0,0 +1,16 @@
+Description: record bio error on linux 4.3
+ Record the bio error code when ending an IO on linux 4.3 and later.
+Author: Andy Whitcroft 
+
+Index: flashcache-3.1.3+git20150701/src/flashcache_subr.c
+===
+--- flashcache-3.1.3+git20150701.orig/src/flashcache_subr.c
 flashcache-3.1.3+git20150701/src/flashcache_subr.c
+@@ -739,6 +739,7 @@ flashcache_bio_endio(struct bio *bio, in
+ #elif LINUX_VERSION_CODE < KERNEL_VERSION(4,3,0)
+ 	bio_endio(bio, error);
+ #else
++	bio->bi_error = error;
+ 	bio_endio(bio);
+ #endif	
+ }
diff -Nru flashcache-3.1.3+git20150701/debian/patches/series flashcache-3.1.3+git20150701/debian/patches/series
--- flashcache-3.1.3+git20150701/debian/patches/series	2015-12-25 03:59:22.0 +
+++ flashcache-3.1.3+git20150701/debian/patches/series	2016-01-27 16:27:07.0 +
@@ -1,3 +1,4 @@
 usable-makefile.patch
 honor-cflags-and-ldflags.patch
 fix-build-error-on-linux-4.3.patch
+record-bio-error-on-linux-4.3.patch
--- End Message ---
--- Begin Message ---
Source: flashcache
Source-Version: 3.1.3+git20150701-3

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

Debian distribution maintenance software
pp.
Liang Guo  (supplier of updated flashcache package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 12 Feb 2016 10:48:27 +0800
Source: flashcache
Binary: flashcache-dkms flashcache-utils
Architecture: source all amd64
Version: 3.1.3+git20150701-3
Distribution: unstable
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Liang Guo 
Description:
 flashcache-dkms - write-back block device cache for Linux (DKMS version)
 flashcache-utils - write-back block device cache for Linux (user space 
utilities)
Closes: 812999
Changes:
 flashcache (3.1.3+git20150701-3) unstable; urgency=medium
 .
   * Record bio error on linux(Closes: #812999)
   * Update debian/wath to use github tags
   * Add DEB_BUILD_MAINT_OPTIONS in debian/rules
   * Switch to secure uri in debian/control
Checksums-Sha1:
 69eb230b4794be9785bd0704fcb8968ef8fa7cd0 2064 
flashcache_3.1.3+git20150701-3.dsc
 

Bug#812661: marked as done (devscripts: FTBFS - test fails due to unexpected (new?) output)

[Debian Bug Tracking System]

Your message dated Fri, 12 Feb 2016 04:19:38 +
with message-id 
and subject line Bug#812661: fixed in devscripts 2.16.1
has caused the Debian Bug report #812661,
regarding devscripts: FTBFS - test fails due to unexpected (new?) output
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.)


-- 
812661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: devscripts
Version: 2.15.10
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
test_debuild
ASSERT:standard output of debuild --no-conf --no-lintian --preserve-envvar=PATH 
--preserve-envvar=PERL5LIB --preserve-envvar=DEBFULLNAME 
--preserve-envvar=DEBEMAIL --preserve-envvar=GNUPGHOME -k'uscan test key (no 
secret) ' matches 
/srv/jenkins-slave/workspace/sid-goto-cc-devscripts/devscripts-2.15.10/test/package_lifecycle/debuild.txt\n
 expected:<0> but was:<1>
21d20
' matches 
/srv/jenkins-slave/workspace/sid-goto-cc-devscripts/devscripts-2.15.10/test/package_lifecycle/debuild.txt\n
 expected:<0> but was:<1>
21d20
 (supplier of updated devscripts 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: Thu, 11 Feb 2016 21:07:17 -0500
Source: devscripts
Binary: devscripts
Architecture: source
Version: 2.16.1
Distribution: unstable
Urgency: medium
Maintainer: Devscripts Devel Team 
Changed-By: James McCoy 
Closes: 750024 774554 783497 803315 804735 809541 809554 809604 809662 809806 
812119 812417 812661 812860 814447
Description: 
 devscripts - scripts to make the life of a Debian Package maintainer easier
Changes:
 devscripts (2.16.1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * uscan:
 - fix regression in uscan when --destdir is set (Closes: #809662)
   Patch by Alex Mestiashvili 
 - fix crash when --rename is passed  (Closes: #812417)
 - when scanning for directories called 'debian', ignore the ones that
   don't have a file called 'watch'. This removes several annoying warnings
   when uscan is run on a package that has several directories called
   'debian' in its upstream source.
 - fix English phrases when logging download-related actions
   * mk-build-deps:
 - When installing, pass `-o Debug::pkgProblemResolver=yes` to `apt-get
   install` so that when build dependencies can't be satisfied, you know 
why.
   Otherwise it would just tell you that the *-build-deps package needs to
   be removed and you will never know why.
   * debian/control:
 - change Vcs-Git: to a https:// URL
 .
   [ James McCoy ]
   * checkbashisms:
 + Recognize dash as a valid shell.
 + Check scripts which use “#!/path/to/env $interpreter”
 + Allow %b as a 

Processed: Re: squid3: SSL error "sec_error_inadequate_key_usage" in the browser

[Debian Bug Tracking System]

Processing control commands:

> severity 814333 important
Bug #814333 [squid3] squid3: SSL error "sec_error_inadequate_key_usage" in the 
browser
Severity set to 'important' from 'grave'
> tags 814333 - newcomer
Bug #814333 [squid3] squid3: SSL error "sec_error_inadequate_key_usage" in the 
browser
Removed tag(s) newcomer.
> forwarded 814333 http://bugs.squid-cache.org/show_bug.cgi?id=4102
Bug #814333 [squid3] squid3: SSL error "sec_error_inadequate_key_usage" in the 
browser
Set Bug forwarded-to-address to 
'http://bugs.squid-cache.org/show_bug.cgi?id=4102'.
> notfound 814333 3.4.8-6+deb8u1
Bug #814333 [squid3] squid3: SSL error "sec_error_inadequate_key_usage" in the 
browser
Ignoring request to alter found versions of bug #814333 to the same values 
previously set
> fixed 814333 3.5.10-1
Bug #814333 [squid3] squid3: SSL error "sec_error_inadequate_key_usage" in the 
browser
Marked as fixed in versions squid3/3.5.10-1.

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

Bug#814333: squid3: SSL error "sec_error_inadequate_key_usage" in the browser

[Amos Jeffries]

Control: severity 814333 important
Control: tags 814333 - newcomer
Control: forwarded 814333 http://bugs.squid-cache.org/show_bug.cgi?id=4102
Control: notfound 814333 3.4.8-6+deb8u1
Control: fixed 814333 3.5.10-1


I am dowgrading this bug on grounds that the issue *does not occur in
any of the official Debian packages*.
Nor is fiddling with the security parameters and operation of TLS a bug
activity suitable for newcomers.


On Tue, 09 Feb 2016 22:51:43 -0200 Y wrote:
>
> I downloaded and compiled the squid through apt-build by adding the
following lines in "/var/cache/apt-build/build/squid3-3.4.8/debian/rules":
> --enable-ssl \
> --enable-ssl-CRTD \
> --with-openssl \
>
> Some https sites aprsentam as error the
"sec_error_inadequate_key_usage" message as error code.
> The errors appear when using Firefox and Iceweasel browsers.

As you noted this was a Mozilla issue (yes *was*). It was fixed in
current Firefox/Iceweasel releases, but several workarounds were also
added to recent Squid versions to not trigger it so easily. Those fixes
are not all suitable for backport IIRC, or they would definitely have
happened already.

Upstream policy is that TLS/SSL users should track the laest releases.
This is particularly important for TLS MITM users such as you (seen in
your choice of build options). There are known vulnerabilities in TLS
MITM for all Squid older than 3.5.10. The non-existence of TLS/SSL in
official Debian packages makes these irrelevant to the Debian security
team. Security issues in the custom additions are *your* problem to
track and fix. I highly recommend building from the Stretch package
instead of patching.


Amos Jeffries
(Squid upstream)

Bug#810070: [Pkg-xen-devel] Bug#810070: Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

[Ian Campbell]

Control: close -1 4.6.0-1

On Thu, 2016-02-11 at 16:56 +0100, a...@trash-mail.com wrote:
> > If possible it might be interesting to first try the 4.6 hypervisor in
> > Stretch, I suspect the xen-hypervisor-4.6-amd64 package will just
> install
> > on Jessie with no issues since it has no dependencies and you don't
> need
> > the userspace tools just to check if it boots.
> 
> Hey there,
> 
> I can confirm the issue with new Intel i7-6700 Quad-Core Skylake CPUs and
> I'm also not able to derive further details than already provided. But I
> can also confirm, that the issue seems to be resolved in Debian Stretch. 

Thanks, marking as fixed in 4.6.0-1.

Ian.

Bug#814446: tomcat8: wants to overwrite admin configuration on upgrade

[Thorsten Glaser]

Package: tomcat8
Version: 8.0.32-1
Severity: serious
Justification: Policy 10.7.3 (MUST), 3.9.1 (SHOULD)

On upgrade, I got asked by ucf to replace my config:

   │ --- /etc/default/tomcat8 2016-01-12 17:11:53.730570427 +0100
   │ +++ /tmp/tomcat8.rNFl7ipDcy 2016-02-11 17:24:28.959519437 +0100
   │ @@ -18,7 +18,7 @@
   │  # response time). If you use that option and you run Tomcat on a 
machine with
   │  # exactly one CPU chip that contains one or two cores, you should 
also add
   │  # the "-XX:+CMSIncrementalMode" option.
   │ -JAVA_OPTS="-Djava.awt.headless=true -Xmx2048m -XX:+UseConcMarkSweepGC"
   │ +JAVA_OPTS="-Djava.awt.headless=true -Xmx2048m -XX:+UseConcMarkSweepGC 
-Dfile.encoding=UTF-8
   │ -Djava.security.egd=file:/dev/./urandom -XX:MaxPermSize=128m"
   │
   │  # To enable remote debugging uncomment the following line.
   │  # You will then be able to use a java debugger on port 8000.
   │ @@ -38,16 +38,9 @@
   │
   │  # Location of the JVM temporary directory
   │  # WARNING: This directory will be destroyed and recreated at every 
startup !
   │ -JVM_TMP=/tmp/tomcat8-temp
   │ +#JVM_TMP=/tmp/tomcat8-temp
   │
   │  # If you run Tomcat on port numbers that are all higher than 1023, 
then you
   │  # do not need authbind. It is used for binding Tomcat to lower port 
numbers.
   │  # (yes/no, default: no)
   │  #AUTHBIND=no
   │ -
   │ -JAVA_OPTS="${JAVA_OPTS} -Dfile.encoding=UTF-8"
   │ -
   │ -export LC_ALL=C.UTF-8
   │ -
   │ -JAVA_OPTS="${JAVA_OPTS} -Djava.security.egd=file:/dev/./urandom"
   │ -JAVA_OPTS="${JAVA_OPTS} -XX:MaxPermSize=128m"

This is 100% changing my own settings (merging some options,
removing two others) and 0% package-provided configuration
changes, and as such violates Policy (cf. #812574).

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

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

Versions of packages tomcat8 depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.58
ii  tomcat8-common 8.0.32-1
ii  ucf3.0033

Versions of packages tomcat8 recommends:
pn  authbind  

Versions of packages tomcat8 suggests:
pn  libtcnative-1 
pn  tomcat8-admin 
pn  tomcat8-docs  
pn  tomcat8-examples  
pn  tomcat8-user  

-- Configuration Files:
/etc/tomcat8/catalina.properties changed [not included]
/etc/tomcat8/context.xml changed [not included]
/etc/tomcat8/server.xml changed [not included]
/etc/tomcat8/tomcat-users.xml changed [not included]

-- debconf information:
  tomcat8/username: tomcat8
  tomcat8/javaopts: -Djava.awt.headless=true -Xmx2048m -XX:+UseConcMarkSweepGC 
-Dfile.encoding=UTF-8 -Djava.security.egd=file:/dev/./urandom 
-XX:MaxPermSize=128m
  tomcat8/groupname: tomcat8

Processed: Re: [Pkg-xen-devel] Bug#810070: Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

[Debian Bug Tracking System]

Processing control commands:

> close -1 4.6.0-1
Bug #810070 [xen-hypervisor-4.4-amd64] XEN Hypervisor crashes/reboots at 
Startup after "Scrubbing Free Ram"
There is no source info for the package 'xen-hypervisor-4.4-amd64' at version 
'4.6.0-1' with architecture ''
Unable to make a source version for version '4.6.0-1'
Marked as fixed in versions 4.6.0-1.
Bug #810070 [xen-hypervisor-4.4-amd64] XEN Hypervisor crashes/reboots at 
Startup after "Scrubbing Free Ram"
Marked Bug as done

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

Bug#814150: marked as done (blacs-mpi: sync with mpi-default-dev 1.0.2+nmu2)

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 16:50:59 +
with message-id 
and subject line Bug#814150: fixed in blacs-mpi 1.1-33.3
has caused the Debian Bug report #814150,
regarding blacs-mpi: sync with mpi-default-dev 1.0.2+nmu2
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.)


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

Please resynchronize blacs-mpi's architecture lists with
mpi-default-dev's.  Per https://packages.debian.org/sid/mpi-default-dev,
sparc64 uses OpenMPI these days, and sh4 and x32 (both currently left
out) use MPICH.  As it stands, blacs-mpi FTBFS on sparc64, and scalapack
and elpa both FTBFS on x32 because blacs-mpi is out of date there.
(FTR, the elpa failure is #814129.)

Thanks!
--- End Message ---
--- Begin Message ---
Source: blacs-mpi
Source-Version: 1.1-33.3

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated blacs-mpi 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, 10 Feb 2016 17:47:00 +
Source: blacs-mpi
Binary: libblacs-openmpi1 libblacs-mpich1 libblacs-mpi-dev blacs-mpi-test 
blacs-test-common
Architecture: source
Version: 1.1-33.3
Distribution: unstable
Urgency: medium
Maintainer: Muammar El Khatib 
Changed-By: Mattia Rizzolo 
Description:
 blacs-mpi-test - Basic Linear Algebra Comm. Subprograms - Test files for MPI
 blacs-test-common - Test data for BLACS testers
 libblacs-mpi-dev - Basic Linear Algebra Comm. Subprograms - Dev. files for MPI
 libblacs-mpich1 - Basic Linear Algebra Comm. Subprograms - Shared libs. for 
MPICH
 libblacs-openmpi1 - Basic Linear Algebra Comm. Subprograms - Shared libs. for 
OpenMPI
Closes: 814150
Changes:
 blacs-mpi (1.1-33.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update the list of MPI architectures:
 + switch s390x from mpich to OpenMPI.
 + switch sparc64 from mpich to OpenMPI.
 + add x32 to OpenMPI.
 + add sh4 to mpich.
 + drop powerpcspe.
 + Closes: #814150
Checksums-Sha1:
 54d0b4166f0ddb3863e3965051d4449aa2c640db 2605 blacs-mpi_1.1-33.3.dsc
 c483e552ea3378af151cca7e0b86a3ddb040bed1 98957 blacs-mpi_1.1-33.3.diff.gz
Checksums-Sha256:
 3be04de719d6a5d707c9ae1f3e85b33bf194b7eeb5c828002ba8a12ce418b33c 2605 
blacs-mpi_1.1-33.3.dsc
 4f29df6fde2692ddbb041d62201f42e9d59f613757374783247264cd754dd562 98957 
blacs-mpi_1.1-33.3.diff.gz
Files:
 53f363d496f248bca23953dc39a09db6 2605 devel extra blacs-mpi_1.1-33.3.dsc
 9ebda3406b5cae67537f7cc07d5e894a 98957 devel extra blacs-mpi_1.1-33.3.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWu5yhAAoJEEsEP825REVAof8P/i6Atdm+SQqJes3ZyH24DZch
ZxCnnn0sZmf6kOYG3GqIC2KKUgI0sayKxOmAiQgp4xfShp1TC86KmG0zJpl+st8q
6JWbs590gXek4s6iYd1NmDPTTOQmqp8Oy9rITgdAnkx4OzJsO2xrIG09kCNp0/kY
CyWBQxbmJIBpNjyG38u5OeaNFgXRl+UfXtTlpt6sO9jC/lXrm023jnG+x0geI/oZ
/MAbua98YkEimN7gVdkcLDfQwoofos+/LNrO0DrHm/SYmOH8O1PCltShhtmme2JH
YWuvr+v526pRoe9toeDVPxr87c8BY0FNtHT7xqA3w33oD9k9u1JThxJjtte4fCte
4RVu8IXj7JhEzPSP9621S3/AXSm3Y8AMsKbZ2EIdEtsipcrPtQcekAXvcU9fSi4c
spUYPqQ8G21928fNC0uY2Xm59d9vUwfR3LJS1wrDYAV8XpVmn/+QOzGhg18RQvjT
IDbbE8Efg6EQ/rM3Y8D/j9I28fXe2f74KIyiP9GcwyYn3O4wo2Lfbfx1Wt5/DtWQ
zt7h+mjYeGZtH0CAEHi4EwhpGTLs5SuBCdynlp4S19hT3dupLaNLwInu4C/Lcv+q
lZUFCE9uDc/Ja3EUDWe67Gc6tqn8/ZbhwP6K01CAD/BmaGiQDMFrMPir+Xd+FfEk
XYpKUHaLyi0Li/slbzcp
=nm6U
-END PGP SIGNATURE End Message ---

Bug#814429: geneweb: debian/mktemplates may fail due to grep binary matching: iconv: conversion from `Binary' is not supported

[Christian PERRIER]

Quoting Peter Gervai (g...@grin.hu):
> Package: geneweb
> Version: 6.08dfsg-3.1
> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
> 
> Build fails with
> iconv: conversion from `Binary' is not supported
> on ca language file. The problem is that grep matches the file as binary, and
> outputs "Binary file matches", which gets (mis)parsed and screw up iconv 
> params.
> Probably dependent on the version of grep, and the phase of the moon 
> possibly. :-)
> 
> This should fix it anyway:


Indeed the reverse patch fixes the problem, but I got the point anywa,
thanks!

This ca.po file is weird. It has something strange which I can't catch
in its first line, which explains why grep thinks it's binary data, I
guess.

Anyway, building the package right now. It's quite some time since I
did so, so I hope that nothing else weird happens..:-)




signature.asc
Description: PGP signature

Bug#814406: marked as done (sisu-guice: FTBFS: [FATAL] Non-resolvable parent POM for org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact org.sonatype.sisu.inject:guice-paren

[Debian Bug Tracking System]

Your message dated Thu, 11 Feb 2016 09:52:39 +
with message-id 
and subject line Bug#814406: fixed in sisu-guice 3.2.6-2
has caused the Debian Bug report #814406,
regarding sisu-guice: FTBFS: [FATAL] Non-resolvable parent POM for 
org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact 
org.sonatype.sisu.inject:guice-parent:pom:4.0-SNAPSHOT
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.)


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

sisu-guice fails to build from source in unstable/amd64:

  [..]

  touch debian/stamp-poms-patched
  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
  clean
  [INFO] Scanning for projects...
  [ERROR] [ERROR] Some problems were encountered while processing the POMs:
  [FATAL] Non-resolvable parent POM for 
org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact 
org.sonatype.sisu.inject:guice-parent:pom:4.0-SNAPSHOT and 
'parent.relativePath' points at wrong local POM @ line 19, column 11
  [WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ 
org.sonatype.sisu.inject:guice-testlib:[unknown-version], 
/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/extensions/testlib/pom.xml,
 line 18, column 15
   @ 
  [ERROR] The build could not read 1 project -> [Help 1]
  [ERROR]   
  [ERROR]   The project org.sonatype.sisu.inject:jdk8-tests:[unknown-version] 
(/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/jdk8-tests/pom.xml)
 has 1 error
  [ERROR] Non-resolvable parent POM for 
org.sonatype.sisu.inject:jdk8-tests:[unknown-version]: Could not find artifact 
org.sonatype.sisu.inject:guice-parent:pom:4.0-SNAPSHOT and 
'parent.relativePath' points at wrong local POM @ line 19, column 11 -> [Help 2]
  [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/ProjectBuildingException
  [ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
  /usr/share/cdbs/1/class/maven.mk:104: recipe for target 'cleanbuilddir' failed
  make: [cleanbuilddir] Error 1 (ignored)
  rm -f -r 
/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
 debian/stamp-maven-build
  rm -f debian/*.substvars
  /usr/bin/make -f debian/rules unpatch-poms
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6'
  mh_unpatchpoms -plibsisu-guice-java
  rm -f -f debian/stamp-poms-patched
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6'
  dh_clean 
  mh_unpatchpoms -plibsisu-guice-java
  rm -f -f debian/stamp-poms-patched
  mh_clean
  rm -f debian/stamp-maven-check
   debian/rules build
  test -x debian/rules
  mkdir -p "."
  /usr/share/maven-debian-helper/copy-repo.sh 
/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian
  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 -plibsisu-guice-java --debian-build --keep-pom-version 
--maven-repo=/home/lamby/temp/cdt.20160211093402.c0PcNHqfLi/sisu-guice-3.2.6/debian/maven-repo
  

Bug#814408: aptitude uses all disk space (12G) with recursive trace-dump in /tmp

[Manuel A. Fernandez Montecelo]

Control: severity -1 minor


Hi,

2016-02-11 10:00 Chris Tillman:

Package: aptitude
Version: 0.7.5-3
Severity: critical
Justification: breaks unrelated software


This is not a critical bug by any strectch, anymore than wget or any
browser might break unrelated software if you download a partition
without enough space (when other packages depend on empty space in that
partition to work fine).  Many packages use /tmp and can cause this
problem under various circumstances, even with much smaller files.

Simply downloading files in aptitude for an upgrade can fill up
/var/cache/apt/archives, which might mean / and /tmp if it's a single
partition, and aptitude never stopped to be released because of that
behaviour.

There is a simple workaround for that, I suspect, which is to use the
defaults and not enable options related with trace-dumps.

It would be useful though if you could mention the exact config or
command line options that you enabled to make this happen.


Cheers.
--
Manuel A. Fernandez Montecelo 

Processed: Re: aptitude uses all disk space (12G) with recursive trace-dump in /tmp

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #814408 [aptitude] aptitude uses all disk space (12G) with recursive 
trace-dump in /tmp
Severity set to 'minor' from 'critical'

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

Bug#811708: [Fwd: Re: [PKG-OpenRC-Debian] Bug#811708: pong on update-rc.d]

[Svante Signell]

--- Begin Message ---
On Fri, 2016-02-12 at 00:47 +0900, Benda Xu wrote:
> Hey guys,
> 
> Thanks for the report.  update-rc.d in OpenRC is a hack based on that
> from sysv-rc.  I think the right way forward is to extend
> init-system-helpers to support OpenRC.
> 
> I will try to figure it out.  If I couldn't make it in time, Svante's
> patch will be upload to close this bug.

Hello,

I took a look at the diff between openrc's and init-system-helper's invoke-rc.d
and update-rc.d scripts. They don't seem to differ to much to make them merge-
able.

However, in case i divert is needed, attached is a debdiff of openrc-0.18.3-1
and openrc-0.18.3-2.

Maybe even the following ar not needed from the purge) target of openrc.postrm
+   rm -f /var/backups/rc-links.tar.gz \
+   /etc/runlevel.conf /etc/runlevel.fallback

+   echo Please purge /var/backups/rc.* manually.
diff -Nru openrc-0.18.3/debian/changelog openrc-0.18.3/debian/changelog
--- openrc-0.18.3/debian/changelog	2015-11-09 15:11:35.0 +0100
+++ openrc-0.18.3/debian/changelog	2016-02-11 17:22:14.0 +0100
@@ -1,3 +1,14 @@
+openrc (0.18.3-2) unstable; urgency=medium
+  * Update debian/openrc.postrm script to divert
+update-rc.d + invoke-rc.d files to cooperate with
+init-system-helpers >=1.25
+  * Create debian/openrc.preinst script to divert
+update-rc.d + invoke-rc.d files to cooperate with
+init-system-helpers >=1.25
+(Closes: #811708)
+
+ -- Svante Signell   Tue, 09 Feb 2016 16:53:58 +0100
+
 openrc (0.18.3-1) unstable; urgency=medium
 
   [ Dmitry Yu Okunev ]
diff -Nru openrc-0.18.3/debian/openrc.postrm openrc-0.18.3/debian/openrc.postrm
--- openrc-0.18.3/debian/openrc.postrm	2015-11-09 15:11:35.0 +0100
+++ openrc-0.18.3/debian/openrc.postrm	2016-02-11 17:19:38.0 +0100
@@ -1,11 +1,76 @@
 #!/bin/sh
+# postrm script for openrc
 
 set -e
 
-if [ "${1}" = "purge" ] ; then
+# summary of how this script can be called:
+#*  `remove'
+#*  `purge'
+#*  `upgrade' 
+#*  `failed-upgrade' 
+#*  `abort-install'
+#*  `abort-install' 
+#*  `abort-upgrade' 
+#*  `disappear' overwrit>r> 
+# for details, see http://www.debian.org/doc/debian-policy/ or
+# the debian-policy package
+
+# see #811708, #805487
+undivert() {
+  dpkg-divert --package openrc --remove --rename \
+--divert /usr/sbin/update-rc.d.init-system-helpers /usr/sbin/update-rc.d
+
+  dpkg-divert --package openrc --remove --rename \
+--divert /usr/sbin/invoke-rc.d.init-system-helpers /usr/sbin/invoke-rc.d
+
+  dpkg-divert --package openrc --remove --rename \
+--divert /usr/share/man/man8/update-rc.d.8.gz.init-system-helpers /usr/share/man/man8/update-rc.d.8.gz
+
+  dpkg-divert --package openrc --remove --rename \
+--divert /usr/share/man/man8/invoke-rc.d.8.gz.init-system-helpers /usr/share/man/man8/invoke-rc.d.8.gz
+}
+
+case "$1" in
+upgrade|failed-upgrade)
+;;
+
+abort-upgrade)
+  if dpkg --compare-versions "$2" lt 0.18.3-2 ; then
+undivert
+  fi
+;;
+
+abort-install|disappear)
+undivert
+;;
+
+remove)
+undivert
+
+	if [ ! -e /usr/sbin/update-rc.d ] ; then
+		ln -sf /usr/share/sysvinit/update-rc.d /usr/sbin/update-rc.d
+	fi
+	if [ ! -e /usr/sbin/invoke-rc.d ] ; then
+		ln -sf /usr/share/sysvinit/update-rc.d /usr/sbin/invoke-rc.d
+	fi
+;;
+
+purge)
+	rm -f /var/backups/rc-links.tar.gz \
+	/etc/runlevel.conf /etc/runlevel.fallback
 	rm -rf /lib/rc /etc/runlevels
 	rm -f /etc/init.d/transit
-fi
+	echo Please purge /var/backups/rc.* manually.
+;;
+
+*)
+echo "postrm called with unknown argument \`$1'" >&2
+exit 1
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
 
 #DEBHELPER#
 
diff -Nru openrc-0.18.3/debian/openrc.preinst openrc-0.18.3/debian/openrc.preinst
--- openrc-0.18.3/debian/openrc.preinst	1970-01-01 01:00:00.0 +0100
+++ openrc-0.18.3/debian/openrc.preinst	2016-02-11 17:19:48.0 +0100
@@ -0,0 +1,58 @@
+#! /bin/sh
+# preinst script for openrc
+#
+# see: dh_installdeb(1)
+
+set -e
+
+# summary of how this script can be called:
+#*  `install'
+#*  `install' 
+#*  `upgrade' 
+#*  `abort-upgrade' 
+#
+# for details, see http://www.debian.org/doc/debian-policy/ or
+# the debian-policy package
+
+# see #811708, #805487
+divert() {
+
+  dpkg-divert --package openrc --add --rename \
+  --divert /usr/sbin/update-rc.d.init-system-helpers /usr/sbin/update-rc.d
+
+  dpkg-divert --package openrc --add --rename \
+  --divert /usr/sbin/invoke-rc.d.init-system-helpers /usr/sbin/invoke-rc.d
+
+  dpkg-divert --package openrc --add --rename \
+  --divert /usr/share/man/man8/update-rc.d.8.gz.init-system-helpers /usr/share/man/man8/update-rc.d.8.gz
+
+  dpkg-divert --package openrc --add --rename \
+  

Bug#814458: gitlab postinst deletes existing data from postgresql database

[Johannes Schauer]

Package: gitlab
Version: 8.4.3+dfsg-1
Severity: critical
Justification: causes serious data loss

Hi,

I previously encountered bug #812841, so I left gitlab as unconfigured
by apt/dpkg and started it manually using `systemctl start gitlab.target`

This seems to have worked well and gitlab was able to make use of the
existing database table from my old manual installation of version
7.8.4.

Then later I wanted to install an unrelated package, so apt/dpkg were
running the gitlab postinst again. As part of the postinst, the database
seems to be completely overwritten with new content. All my existing
content would've been lost if I hadn't made a backup beforehand.

That I now have an empty gitlab instance can be seen from the following
output:

gitlab@22gitlab:~$ rake gitlab:check RAILS_ENV=production
fatal: Not a git repository (or any of the parent directories): .git
Checking GitLab Shell ...
GitLab Shell version >= 2.6.10 ? ... OK (2.6.10)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by gitlab:gitlab? ... yes
Repo base access is drwxrws---? ... yes
hooks directories in repos are links: ... can't check, you have no 
projects
Running /usr/share/gitlab-shell/bin/check
Check GitLab API access: FAILED. code: 302
gitlab-shell self-check failed
  Try fixing it:
  Make sure GitLab is running;
  Check the gitlab-shell configuration file:
  sudo -u gitlab -H editor /usr/share/gitlab-shell/config.yml
  Please fix the error above and rerun the checks.
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder 
yet)
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ... can't check, you have no projects
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.2.4)
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (2.1.4)
Active users: 1

Checking GitLab ... Finished


This should not happen!

Thanks!

cheers, josch

Processed: systemd checking was not foolproof

[Debian Bug Tracking System]

Processing control commands:

> found -1 gitlab/8.4.0+dfsg-2
Bug #812841 [gitlab] gitlab: Fails to install with 'invoke-rc.d: initscript 
gitlab, action "start" failed'.
Marked as found in versions gitlab/8.4.0+dfsg-2; no longer marked as fixed in 
versions gitlab/8.4.0+dfsg-2.
> forcemerge -1 814413
Bug #812841 [gitlab] gitlab: Fails to install with 'invoke-rc.d: initscript 
gitlab, action "start" failed'.
Bug #814413 [gitlab] Gitlab failed to install E: Sub-process /usr/bin/dpkg 
returned an error code
Set Bug forwarded-to-address to 
'https://gitlab.com/gitlab-org/gitlab-ce/issues/12787'.
Severity set to 'important' from 'grave'
Marked as found in versions gitlab/8.4.0+dfsg~rc2-2 and gitlab/8.4.0+dfsg-2.
Merged 812841 814413

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

Bug#814431: tests fail on i386

[Lev Lamberov]

Hi Mattias,

11.02.2016 19:38, Matthias Klose пишет:
> Package: src:swi-prolog
> Version: 7.2.3-1
> Severity: serious
> Tags: sid stretch
>
> tests fail on i386:
>
> ERROR: /«PKGBUILDDIR»/packages/jpl/test_jpl.pl:1185:
> test threads3: received error: jpl:jFindClass/2: Undefined
> procedure: jpl:jni_func/3
> ERROR: /«PKGBUILDDIR»/packages/jpl/test_jpl.pl:1203:
> test jref1: received error: plunit_jpl:'unit body'/2: Undefined
> procedure: jpl:jni_term_to_jref/2
> ERROR: /«PKGBUILDDIR»/packages/jpl/test_jpl.pl:1213:
> test jref2: received error: plunit_jpl:'unit body'/2: Undefined
> procedure: jpl:jni_term_to_jref/2
> Makefile:60: recipe for target 'check_pl' failed
> make[2]: *** [check_pl] Error 1
> make[2]: Leaving directory '/«PKGBUILDDIR»/packages/jpl'
> debian/rules:134: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 2
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> debian/rules:70: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
>

Hmmm... As I can see it cannot find libjpl.so, because on i386 it fails
to build that library, see:


gcc -shared -rdynamic -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  -L/«PKGBUILDDIR»/src/../lib/i386  -o 
libjpl.so src/c/jpl.o  -ljava -lverify -ljvm -lswipl
/usr/bin/ld: cannot find -ljava
/usr/bin/ld: cannot find -lverify
/usr/bin/ld: cannot find -ljvm
collect2: error: ld returned 1 exit status
Makefile:43: recipe for target 'libjpl.so' failed
make[4]: *** [libjpl.so] Error 1
make[4]: *** Waiting for unfinished jobs


And compare it to log for amd64:


gcc -shared -rdynamic -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  -L/«PKGBUILDDIR»/src/../lib/amd64 
-L'/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server' 
-L'/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64' -o libjpl.so src/c/jpl.o  
-ljsig -ljava -lverify -ljvm -lswipl



Something wrong with Makefile generation on i386. Will look at it.
Thanks! Lev Lamberov



signature.asc
Description: OpenPGP digital signature