Bug#802264: src:matita: FTBFS with OCaml 4.02.3

[Mehdi Dogguy]

Package: src:matita
Version: 0.99.1-3
Severity: serious

Dear Maintainer,

Your package fails to build from source. Here is an excerpt from the 
build

log:

  OCAMLOPT nCic.ml
File "nCic.ml", line 142, characters 11-460:
Error: This class type should be virtual.
   The following variables are undefined : ppterm ppsubst ppobj
 ppmetasenv ppcontext
../Makefile.common:102: recipe for target 'nCic.cmx' failed
make[3]: *** [nCic.cmx] Error 2

A full build log is attached.

Regards,

--
Mehdi -> Copying COW directory
  forking: rm -rf /var/cache/pbuilder/build//cow.12549 
  forking: cp -al /var/cache/pbuilder/cows/unstable-amd64/ 
/var/cache/pbuilder/build//cow.12549 
I: removed stale ilistfile /var/cache/pbuilder/build//cow.12549/.ilist
  forking: chroot /var/cache/pbuilder/build//cow.12549 cowdancer-ilistcreate 
/.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ' 
 -> Invoking pbuilder
  forking: pbuilder build --buildplace /var/cache/pbuilder/build//cow.12549 
--buildresult /var/cache/pbuilder/result/unstable-amd64 --debbuildopts  
--no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.12549 
cow-shell /tmp/tmp.xoIxvDvlsS/matita_0.99.1-3.dsc 
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sun Oct 18 22:53:33 CEST 2015
I: pbuilder-time-stamp: 1445201613
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /var/cache/pbuilder/result/
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
W: execute priv not set on file D09custompool, not executing.
I: user script /var/cache/pbuilder/build/cow.12549/tmp/hooks/D10aptupdate 
starting
Get:1 http://incoming.debian.org buildd-unstable InRelease [111 kB]
Get:2 http://incoming.debian.org buildd-unstable/main amd64 Packages [128 kB]
Get:3 http://http.debian.net unstable InRelease [250 kB]
Get:4 http://incoming.debian.org buildd-unstable/contrib amd64 Packages [500 B]
Get:5 http://incoming.debian.org buildd-unstable/non-free amd64 Packages [1828 
B]
Get:6 http://incoming.debian.org buildd-unstable/contrib Translation-en [402 B]
Get:7 http://incoming.debian.org buildd-unstable/main Translation-en [109 kB]   

Get:8 http://http.debian.net unstable/main amd64 Packages/DiffIndex [7876 B] 
Get:9 http://incoming.debian.org buildd-unstable/non-free Translation-en [2546 
B]
Get:10 http://http.debian.net unstable/main Translation-en/DiffIndex [7876 B]   
   
Get:11 http://http.debian.net unstable/main amd64 2015-10-18-1440.19.pdiff 
[13.4 kB]
Get:12 http://http.debian.net unstable/main amd64 2015-10-18-1440.19.pdiff 
[13.4 kB]
Get:13 http://http.debian.net unstable/main 2015-10-18-1440.19.pdiff [2025 B]
Get:14 http://http.debian.net unstable/main 2015-10-18-1440.19.pdiff [2025 B]
Fetched 635 kB in 3s (191 kB/s)  
Reading package lists... Done
I: user script /var/cache/pbuilder/build/cow.12549/tmp/hooks/D10aptupdate 
finished
I: user script /var/cache/pbuilder/build/cow.12549/tmp/hooks/D11unsafeio 
starting
Setting force-unsafe-io for dpkg
I: user script /var/cache/pbuilder/build/cow.12549/tmp/hooks/D11unsafeio 
finished
W: execute priv not set on file D12aptupgrade, not executing.
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: ocaml (>= 3.10.2), ocaml-findlib (>= 1.2.1-2), libgdome2-ocaml-dev, 
liblablgtk2-ocaml-dev, libocamlnet-ocaml-dev, libzip-ocaml-dev, 
libhttp-ocaml-dev, ocaml-ulex08 (>= 0.8-4), libexpat-ocaml-dev, debhelper (>= 
8), camlp5 (>= 5.04), liblablgtksourceview2-ocaml-dev, autoconf, help2man
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 12072 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on ocaml (>= 3.10.2); however:
  Package ocaml is not installed.
 pbuilder-satisfydepends-dummy depends on ocaml-findlib (>= 1.2.1-2); however:
  Package ocaml-findlib is not installed.
 pbuilder-satisfydepends-dummy depends on libgdome2-ocaml-dev; however:
  Package libgdome2-ocaml-dev is 

Bug#800574: Final analysis for Broadwell

[Henrique de Moraes Holschuh]

On Sun, 18 Oct 2015, Aurelien Jarno wrote:
> > Broadwell-H with a very recent microcode update (rev 0x12, from
> > 2015-06-04) was confirmed to have broken TSX-NI (RTM) and to _leave it
> > enabled_ in CPUID, causing glibc with lock elision enabled to SIGSEGV. 
> > An even more recent Broadwell-H microcode update, rev 0x13 from
> > 2015-08-03, is confirmed to (finally) disable the HLE and RTM CPUID
> > bits.  This should make blacklisting signature 0x40671 uncontroversial.

FWIW, in the last few days it became clear that so far, the mobile
Broadwell-H disables Intel TSX, but no instances of the desktop
Broadwell-H with RTM disabled were found yet, not even with the latest
microcode.  And they all use the same microcode.

It has also became clear a few days ago that it is very likely that the
BIOS can disable Intel TSX-NI (RTM) and HLE, and it doesn't need very
recent microcode to do that either.  If this is true, it should be
something like MSR 0x13c (bit 1 of that MSR disables AES-NI when set,
and bit 0 locks that MSR against writting when set).  Maybe the Intel
TSX-NI (HLE and RTM) disable switches are even on this very same MSR...

I've also since became aware of Debian bug #750792, and it describes the
same SIGSEGV observed by Broadwell and Skylake Arch-linux users on
lock-elision-enabled glibc.  From that bug report, it is clear that the
SIGSEGVs in __lll_unlock_elision can easily happen due to software bugs,
so it need not be linked to any Intel-TSX processor errata.  And this
kind of defect is quite common, apparently.

However, since Intel's current public specification update states (as
errata) that Intel TSX-NI is not supposed to be usable in the Broadwell
and Broadwell-H cores, that it should not even be reported in CPUID by
these processors (but it is :p), and that this is not supposed to be
fixable or worked around, I still think we need to blacklist it.

I will keep tracking this issue, and report back any relevant
information that becomes available.  It would be _really_ nice if the
Intel team that works with Canonical were to shed a light on this,
though.

> Thanks for the patch, I have committed it to the jessie and the 2.21
> branches.

Thank you.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Processed: limit source to firmware-nonfree, tagging 724970, tagging 793874, tagging 795303, tagging 801514 ...

[Debian Bug Tracking System]

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

> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of 
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'

> tags 724970 + pending
Bug #724970 [firmware-atheros] firmware-atheros: firmware for ath10k devices 
missing
Added tag(s) pending.
> tags 793874 + pending
Bug #793874 [firmware-realtek] rtl8192sfw.bin: no upstream in copyright file
Added tag(s) pending.
> tags 795303 + pending
Bug #795303 [firmware-brcm80211] firmware-brcm80211: Missing firmware 
brcmfmac43340-sdio.bin
Added tag(s) pending.
> tags 801514 + pending
Bug #801514 [firmware-realtek] firmware-realtek: Please include rtl8821a_fw.bin
Added tag(s) pending.
> tags 769633 + pending
Bug #769633 [firmware-iwlwifi] Please add iwlwifi-7260-12.ucode
Added tag(s) pending.
> tags 800440 + pending
Bug #800440 [firmware-brcm80211] Please include BCM4339 SDIO firmware
Added tag(s) pending.
> tags 800090 + pending
Bug #800090 [firmware-linux-nonfree] missing firmware - radeon TAHITI_vce.bin
Added tag(s) pending.
> tags 790061 + pending
Bug #790061 [firmware-linux-nonfree] firmware-linux-nonfree: please rebase to 
latest linux-firmware repo
Added tag(s) pending.
> tags 774914 + pending
Bug #774914 [firmware-linux-nonfree] firmware-linux-nonfree: Include the intel 
sst firmwares required for audio on Bay Trail
Added tag(s) pending.
> tags 620066 + pending
Bug #620066 [src:firmware-nonfree] linux-image-2.6.32-5-amd64: missing firmware 
file cbfw.bin for module bfa.ko for Brocade Fibre Channel HBA card
Added tag(s) pending.
> tags 793544 + pending
Bug #793544 [firmware-iwlwifi] firmware-iwlwifi: iwlwifi-7265-11.ucode and 
iwlwifi-7265-12.ucode missing for linux 4.0
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
620066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620066
724970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724970
769633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769633
774914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774914
790061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790061
793544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793544
793874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793874
795303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795303
800090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800090
800440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800440
801514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#802265: src:botch: FTBFS: target 'test-selfcontained' failed

[Mehdi Dogguy]

Package: src:botch
Version: 0.16-2
Severity: serious

Dear Maintainer,

Your package fails to build from source. Here is an excerpt from the 
build

log:

-Provides: myspell-dictionary, myspell-dictionary-en, 
myspell-dictionary-en-za

-Depends: dictionaries-common (>= 0.10) | openoffice.org-updatedicts
-Conflicts: openoffice.org (<= 1.0.3-2)
+Source: norwegian
+Provides: myspell-dictionary, myspell-dictionary-nn, 
openoffice.org-spellcheck-nn

+Depends: dictionaries-common (>> 0.10) | openoffice.org-updatedicts

 Package: mysql-common
 Version: 5.5.33+dfsg-1
Makefile:159: recipe for target 'test-selfcontained' failed
make[1]: *** [test-selfcontained] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Full build logs can be found here:

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

Regards,

--
Mehdi

Bug#794723: Policykit crashes systemd

[Simon McVittie]

On Sun, 11 Oct 2015 at 14:28:41 +0100, Simon McVittie wrote:
> I can reproduce something very like this in a smaller stretch VM

After upgrading to current stretch package versions and rebooting
(to rule out #801354), I can still reproduce the "Connection timed
out" messages (apparently reliably) by installing task-xfce-desktop.
I haven't found a smaller package set that does the same (at least not
reliably). If this is anything like #801354 then it might be a
race condition, so perhaps it's just less likely with smaller sets.

However, after waiting for the install to finish, systemctl still works
(I can restart avahi-daemon, for instance), rebooting also works (without
delay), and lightdm starts successfully after the reboot...  so the
worst of the symptoms do seem to be fixed, perhaps by fixing #801354.
I don't think this is necessarily release-critical.

S

Bug#802118: [pkg-opensc-maint] Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.

[Eric Dorland]

* persmule (persm...@gmail.com) wrote:
> Package: libengine-pkcs11-openssl
> Version: 0.1.8-5
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> Dear Maintainer,
> 
> Functions in src/engine_pkcs11.c to set static global data (set_module,
> set_pin, get_pin and set_init_args) do not free memories pointed by the
> corresponding pointers before assigning them to newly allocated
> memories, which
> may cause memory leaks if they are called more than once.
> 
> The bugs related to set_module, set_pin and get_pin are fixed on
> upstream, but
> the one of set_init_args is not.

Agreed that these are valid memory leaks but what's the security
implication? This doesn't seem obviously exploitable.

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: PGP signature

Processed: block 802049 with 802285

[Debian Bug Tracking System]

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

> block 802049 with 802285
Bug #802049 [cyphesis-cpp] cyphesis-cpp: FTBFS in sid: needs -std=c++11
802049 was not blocked by any bugs.
802049 was not blocking any bugs.
Added blocking bug(s) of 802049: 802285
> thanks
Stopping processing here.

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

Bug#802118: [pkg-opensc-maint] Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.

[Persmule]

  
  
Dear Maintainer,

I don't know whether it is easy to exploit. But I believe every
memory bug related to a security-oriented package is grave.

By the way, I managed creating a patch locally, may it be useful for
you.

Persmule

On Sun, 18 Oct 2015 17:31:08 -0400 Eric Dorland
 wrote:
> * persmule (persm...@gmail.com) wrote:
> > Package: libengine-pkcs11-openssl
> > Version: 0.1.8-5
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> > 
> > Dear Maintainer,
> > 
> > Functions in src/engine_pkcs11.c to set static global data
(set_module,
> > set_pin, get_pin and set_init_args) do not free memories
pointed by the
> > corresponding pointers before assigning them to newly
allocated
> > memories, which
> > may cause memory leaks if they are called more than once.
> > 
> > The bugs related to set_module, set_pin and get_pin are
fixed on
> > upstream, but
> > the one of set_init_args is not.
> 
> Agreed that these are valid memory leaks but what's the
security
> implication? This doesn't seem obviously exploitable.
> 
> -- 
> Eric Dorland 
> 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93

  

Description: 
 Functions in src/engine_pkcs11.c to set static global data
 (set_module, set_pin, get_pin and set_init_args) do not free
 memories pointed by the corresponding pointers before assigning
 them to newly allocated memories, which may cause memory leaks
 if they are called more than once.
 .
 engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium
 .
   * src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)
Author: Xie Tianming 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 

--- engine-pkcs11-0.1.8.orig/src/engine_pkcs11.c
+++ engine-pkcs11-0.1.8/src/engine_pkcs11.c
@@ -62,10 +62,22 @@ static char *init_args = NULL;
 
 int set_module(const char *modulename)
 {
+	free(module);
 	module = modulename ? strdup(modulename) : NULL;
 	return 1;
 }
 
+/* Free PIN storage in secure way. */
+static void zero_pin(void)
+{
+	if (pin != NULL) {
+		OPENSSL_cleanse(pin, pin_length);
+		free(pin);
+		pin = NULL;
+		pin_length = 0;
+	}
+}
+
 /**
  * Set the PIN used for login. A copy of the PIN shall be made.
  *
@@ -89,6 +101,7 @@ int set_pin(const char *_pin)
 
 	/* Copy the PIN. If the string cannot be copied, NULL
 	   shall be returned and errno shall be set. */
+	zero_pin();
 	pin = strdup(_pin);
 	if (pin != NULL)
 		pin_length = strlen(pin);
@@ -115,6 +128,7 @@ static int get_pin(UI_METHOD * ui_method
 
 	/* pin in the call back data, copy and use */
 	if (mycb != NULL && mycb->password) {
+		zero_pin();
 		pin = (char *)calloc(MAX_PIN_LENGTH, sizeof(char));
 		if (!pin)
 			return 0;
@@ -147,6 +161,7 @@ static int get_pin(UI_METHOD * ui_method
 
 int set_init_args(const char *init_args_orig)
 {
+	free(init_args);
 	init_args = init_args_orig ? strdup(init_args_orig) : NULL;
 	return 1;
 }
engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium

  * src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)

 -- Xie Tianming   Mon, 19 Oct 2015 09:19:53 +0800

engine-pkcs11 (0.1.8-5) unstable; urgency=medium

  * debian/source/options, debian/source/patch-header: Remove obsolete
source control files.
  * debian/watch: Fix URL.
  * debian/control: Move maintainer to
pkg-opensc-ma...@lists.alioth.debian.org to and myself to Uploaders.
  * debian/copyright: Move to DEP5 copyright file.
  * debian/gbp.conf: Use pristine-tar.
  * debian/control, debian/rules: Use dh-autoreconf.

 -- Eric Dorland   Sun, 10 May 2015 15:49:32 -0400

engine-pkcs11 (0.1.8-4) unstable; urgency=medium

  * debian/control: Standards-Version to 3.9.6.
  * debian/control: Add Vcs-* fields.
  * debian/control: Add Homepage field.
  * debian/watch: Update with new GitHub location.
  * debian/control: Run wrap-and-sort.

 -- Eric Dorland   Sat, 20 Sep 2014 19:03:02 -0400

engine-pkcs11 (0.1.8-3) unstable; urgency=low

  * debian/control, debian/rules: Use autotools-dev.
  * debian/compat, debian/control: Use debhelper v9.
  * debian/control: Upgrade Standards-Version to 3.9.4.

 -- Eric Dorland   Wed, 11 Sep 2013 23:52:42 -0400

engine-pkcs11 (0.1.8-2) unstable; urgency=low

  * debian/rules: Actually install the engine in the correct
location.(Closes: #566971)

 -- Eric Dorland   Tue, 09 Feb 2010 02:33:41 -0500

Bug#800574: Final analysis for Broadwell

[Aurelien Jarno]

On 2015-10-08 22:20, Henrique de Moraes Holschuh wrote:
> tag 800574 + patch
> thanks
> 
> Attached updated version of amd64/local-blacklist-on-TSX-Haswell.diff.  
> I believe it should be renamed to
> "amd64/local-blacklist-for-Intel-TSX.diff" as it is not just about Intel
> Haswell anymore.
> 
> The updated patch has been package-compile-tested on glibc 2.19-22.
> 
> This new version of the blacklist patch had the patch header text and
> blacklist code comments updated.   It doesn't change anything for
> Haswell.  It adds to the blacklist the current Broadwell CPU models and
> steppings.
> 
> Broadwell-H with a very recent microcode update (rev 0x12, from
> 2015-06-04) was confirmed to have broken TSX-NI (RTM) and to _leave it
> enabled_ in CPUID, causing glibc with lock elision enabled to SIGSEGV. 
> An even more recent Broadwell-H microcode update, rev 0x13 from
> 2015-08-03, is confirmed to (finally) disable the HLE and RTM CPUID
> bits.  This should make blacklisting signature 0x40671 uncontroversial.
> 
> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=103351 for details.
> 
> This version of the blacklist patch leaves upcoming Broadwell-E
> unblacklisted.  It also leaves Skylake unblacklisted, as I have not been
> able to confirm whether the newest Skylake-S microcode updates have
> working Intel TSX-NI, or have it disabled.
> 
> I propose that the updated blacklist patch be added to glibc in
> unstable, and after it spends a few weeks in testing, that it should
> also be the added to stable through a stable update.

Thanks for the patch, I have committed it to the jessie and the 2.21
branches.

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

Bug#802268: src:cduce: FTBFS with OCaml 4.02.3

[Mehdi Dogguy]

Package: src:cduce
Version: 0.6.0-1
Severity: serious

Dear Maintainer,

Your package fails to build from source. Here is an excerpt from the 
build

log:

File "clflags.ml", line 48, characters 19-25:
Error: The type of this expression, '_a list ref,
   contains type variables that cannot be generalized
File "_none_", line 1:
Error: File clflags.cmx not found
cp: cannot stat 'caml_cduce.cmx': No such file or directory
cp: cannot stat 'caml_cduce.o': No such file or directory
cp: cannot stat 'caml_cduce.cmi': No such file or directory
Makefile:35: recipe for target 'caml_cduce.cmx' failed
make[3]: *** [caml_cduce.cmx] Error 1

A full build log is attached.

(The changes made in 0.6.0-2 can be found in the git repository).

Regards,

--
MehdiI: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sun Oct 18 23:08:35 CEST 2015
I: pbuilder-time-stamp: 1445202515
I: copying local configuration
I: Installing apt-lines
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
I: user script 
/home/incoming/unstable/build/cow.24378/tmp/hooks/D10dpkg-speedup starting
I: user script 
/home/incoming/unstable/build/cow.24378/tmp/hooks/D10dpkg-speedup finished
I: user script 
/home/incoming/unstable/build/cow.24378/tmp/hooks/D15no-man-db-rebuild starting
I: user script 
/home/incoming/unstable/build/cow.24378/tmp/hooks/D15no-man-db-rebuild finished
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.2.11~), dh-ocaml (>= 0.9~), ocaml-nox (>= 3.11.1-3~), 
ocaml-best-compilers, camlp4-extra, ocaml-source (>= 3.11.0), libpcre-ocaml-dev 
(>= 6.0.1-2~), libocamlnet-ocaml-dev (>= 2.2.9-7~), libexpat-ocaml-dev (>= 
0.9.1+debian1-6~), libcurl-ocaml-dev (>= 0.5.1-2~), ocaml-ulex (>= 1.1-2~), 
chrpath, bzip2
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 13151 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on debhelper (>= 7.2.11~); however:
  Package debhelper is not installed.
 pbuilder-satisfydepends-dummy depends on dh-ocaml (>= 0.9~); however:
  Package dh-ocaml is not installed.
 pbuilder-satisfydepends-dummy depends on ocaml-nox (>= 3.11.1-3~); however:
  Package ocaml-nox is not installed.
 pbuilder-satisfydepends-dummy depends on ocaml-best-compilers; however:
  Package ocaml-best-compilers is not installed.
 pbuilder-satisfydepends-dummy depends on camlp4-extra; however:
  Package camlp4-extra is not installed.
 pbuilder-satisfydepends-dummy depends on ocaml-source (>= 3.11.0); however:
  Package ocaml-source is not installed.
 pbuilder-satisfydepends-dummy depends on libpcre-ocaml-dev (>= 6.0.1-2~); 
however:
  Package libpcre-ocaml-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libocamlnet-ocaml-dev (>= 2.2.9-7~); 
however:
  Package libocamlnet-ocaml-de
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  bsdmainutils{a} camlp4{ab} camlp4-extra{ab} chrpath{a} debhelper{a} 
  dh-ocaml{a} dh-strip-nondeterminism{a} file{a} gettext{a} gettext-base{a} 
  groff-base{a} intltool-debian{a} libarchive-zip-perl{a} 
  libcamlp4-ocaml-dev{a} libcroco3{a} libcurl-ocaml{a} libcurl-ocaml-dev{a} 
  libcurl3-gnutls{a} libcurl4-gnutls-dev{a} libexpat-ocaml{a} 
  libexpat-ocaml-dev{a} libexpat1{a} libexpat1-dev{a} libffi6{a} 
  libfile-stripnondeterminism-perl{a} libfindlib-ocaml{a} libglib2.0-0{a} 
  libgnutls-deb0-28{a} libgssapi-krb5-2{a} libhogweed4{a} libicu55{a} 
  libidn11{a} libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} 
  libkrb5support0{a} libldap-2.4-2{a} libmagic1{a} libncurses5-dev{a} 
  libnettle6{a} libnghttp2-14{a} 

Bug#802260: gnome-gmail: Some dependencies missing

[Mario Blättermann]

Package: gnome-gmail
Version: 1.9.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after installing gnome-gmail in Stretch, I was a bit surprised about the few
extra dependencies which have to be installed on a KDE-only system. After
launching gnome-gmail then, I got some error messages, gnome-gmail didn't
start:

mariobl@debian:~$ gnome-gmail
/usr/share/gnome-gmail/gnomegmail.py:37: PyGIWarning: Gtk was imported without
specifying a version first. Use gi.require_version('Gtk', '3.0') before import
to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/share/gnome-gmail/gnomegmail.py:41: PyGIWarning: Secret was imported
without specifying a version first. Use gi.require_version('Secret', '1')
before import to ensure that the right version gets loaded.
  from gi.repository import Secret
/usr/share/gnome-gmail/gnomegmail.py:42: PyGIWarning: Notify was imported
without specifying a version first. Use gi.require_version('Notify', '0.7')
before import to ensure that the right version gets loaded.
  from gi.repository import Notify
Traceback (most recent call last):
  File "/usr/share/gnome-gmail/gnomegmail.py", line 43, in 
from gi.repository import Wnck
ImportError: cannot import name Wnck

According to the messages, I installed python-wnck and gir1.0-wnck-3.0. The
messages have been shrinked a bit, and I the setup window has been opened where
I could submit my Gmail address. But there remain some terminal messages, and
gnome-gmail is still unusable:

mariobl@debian:~$ gnome-gmail
/usr/share/gnome-gmail/gnomegmail.py:37: PyGIWarning: Gtk was imported without
specifying a version first. Use gi.require_version('Gtk', '3.0') before import
to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/share/gnome-gmail/gnomegmail.py:41: PyGIWarning: Secret was imported
without specifying a version first. Use gi.require_version('Secret', '1')
before import to ensure that the right version gets loaded.
  from gi.repository import Secret
/usr/share/gnome-gmail/gnomegmail.py:42: PyGIWarning: Notify was imported
without specifying a version first. Use gi.require_version('Notify', '0.7')
before import to ensure that the right version gets loaded.
  from gi.repository import Notify
/usr/share/gnome-gmail/gnomegmail.py:43: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
  from gi.repository import Wnck
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py", line 103, in
_builder_connect_callback
handler, args = _extract_handler_and_args(obj_or_map, handler_name)
  File "/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py", line 83, in
_extract_handler_and_args
raise AttributeError('Handler %s not found' % handler_name)
AttributeError: Handler onUserSelClose not found
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py", line 103, in
_builder_connect_callback
handler, args = _extract_handler_and_args(obj_or_map, handler_name)
  File "/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py", line 83, in
_extract_handler_and_args
raise AttributeError('Handler %s not found' % handler_name)
AttributeError: Handler onOkClicked not found
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Traceback (most recent call last):
  File "/usr/share/gnome-gmail/gnomegmail.py", line 765, in 
main()
  File "/usr/share/gnome-gmail/gnomegmail.py", line 762, in main
browser().open(gmailurl, new_browser, True)
  File "/usr/share/gnome-gmail/gnomegmail.py", line 63, in browser
bpath = app.get_filename()
AttributeError: 'NoneType' object has no attribute 'get_filename'

Maybe it's only about missing dependencies... On a Fedora 23 system, with
similar software versions, gnome-gmail works as expected, although it is
actually Gnome 2 software.



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

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

Versions of packages gnome-gmail depends on:
ii  gir1.2-secret-1  0.18.3-1
ii  libgtk-3-bin 3.16.6-1
ii  python-gi3.18.0-1
ii  python2.72.7.10-5

gnome-gmail recommends no packages.

gnome-gmail suggests no packages.

-- no debconf information

Bug#802287: kdenlive: Kdenlive for Debian 8 fails to load

[Joe McEntire]

Package: kdenlive
Version: 0.9.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Attempted to install and run kdenlive

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Installed kdenlive, kdenlive fails to start once I clicked the icon.  I
then rolled back to the wheezy version of the packages kdenlive, kdenlive-data,
libmlt++3, libmlt5, melt holding these packages at the wheezy version level

   * What was the outcome of this action?
With the Jessie version the package fails to run.  kdenlive will not
start
With the Wheezy version the package works as expected.

The occurs on both my desktop and my laptop.  I cannot get the Jessie
version to work no matter what I try.

   * What outcome did you expect instead?
Kdenlive should launch as expected once installed.

*** End of the template - remove these template lines ***



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

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

Versions of packages kdenlive depends on:
ii  ffmpeg7:2.6.1-1~wheezy1
ii  kde-runtime   4:4.14.2-2
pn  kdenlive-data 
ii  libc6 2.19-18+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]  10.3.2-1+deb8u1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libkdecore5   4:4.14.2-5
ii  libkdeui5 4:4.14.2-5
ii  libkio5   4:4.14.2-5
ii  libknewstuff3-4   4:4.14.2-5
ii  libknotifyconfig4 4:4.14.2-5
ii  libkrossui4   4:4.14.2-5
pn  libmlt++3 
pn  libmlt5   
ii  libnepomuk4   4:4.14.2-5
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libsolid4 4:4.14.2-5
ii  libsoprano4   2.9.4+dfsg-1.1
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.1-1+b1
ii  libxext6  2:1.3.3-1
pn  melt  

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

kdenlive suggests no packages.

-- no debconf information

Bug#800574: Final analysis for Broadwell

[Aurelien Jarno]

On 2015-10-07 07:32, Henrique de Moraes Holschuh wrote:
> Meanwhile, a suggestion by Samuel Thibault to try to use hwcap did
> provide for a possible long-term plan to fine-tune the lock-elision
> blacklist (and anything else of that sort).
> 
> We would have to (finally) extend x86-64 hwcap to cpuid(1) fully, and
> also at least cpuid(7), which is anything but trivial and a lot of work.
>  This is _not_ worth the trouble if it is done just for lock elision
> blacklisting purposes.
> 
> However, it would be useful for link-time optimization in libraries
> (e.g. avx2 flavours of something that really benefits from it, etc), so
> it is likely worth pursuing... but only if we get buy-in from upstream.

Why do you believe that hwcap is better for handling that than the
current STT_GNU_IFUNC mechanism?

For me hwcap is clearly superseded by the STT_GNU_IFUNC:

1) With the hwcap mechanism the libraries need to be recompiled multiple
times, increasing build time, but also the disk space on the users
computer.

2) It makes the upgrades more complex (see the nohwcap part of the libc
preinst/postinst).

3) We need to ensure the ABI is the same for all versions of the same
library (this is not the case for upstream glibc between i586 and i686).

4) The fact that the CPU supports a feature doesn't mean it supports it
with good performances. For instance Intel Silvermont supports SSE4.2,
but SSE2/SSSE3 based version of string functions are much faster there.

5) Finally it means that we need to provide a version of the libc for
all combinations. Think on i386, we would need to provide:
 - libc6
 - libc6-i686
 - libc6-i686-tsx
 - libc6-xen
 - libc6-xen-tsx

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

Bug#802070: marked as done (freezegun: FTBFS: ImportError (No module named mock))

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 21:49:08 +
with message-id 
and subject line Bug#802070: fixed in freezegun 0.3.5-2
has caused the Debian Bug report #802070,
regarding freezegun: FTBFS: ImportError (No module named mock)
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.)


-- 
802070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freezegun
Version: 0.3.5-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

for python in python2.7; do \
$python /usr/bin/nosetests tests; \
done
..S.S...S...E
==
ERROR: Failure: ImportError (No module named mock)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 420, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/freezegun-0.3.5/tests/test_ticking.py", line 3, in 
import mock
ImportError: No module named mock

NameStmts   Miss  Cover   Missing
-
freezegun   8  0   100%   
freezegun.api 302 2093%   21-22, 32, 52, 64, 236-237, 240, 306, 
328, 362, 372-374, 397-399, 443-444, 450, 462-464
-
TOTAL 310 2094%   
--
Ran 69 tests in 0.940s

FAILED (SKIP=3, errors=1)
debian/rules:16: recipe for target 'override_dh_auto_test' failed


Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/freezegun.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: freezegun
Source-Version: 0.3.5-2

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated freezegun 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: Sun, 18 Oct 2015 22:35:31 +0100
Source: freezegun
Binary: python-freezegun python3-freezegun
Architecture: source all
Version: 0.3.5-2
Distribution: unstable
Urgency: low
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Description:
 python-freezegun - Python library to mock the datetime module in unit testing
 python3-freezegun - Python3 library to mock the datetime module in unit testing
Closes: 802070
Changes:
 freezegun (0.3.5-2) unstable; urgency=low
 .
   * Add build dependencies on Mock (Closes: #802070)
Checksums-Sha1:
 542563e871e6b54965da685296ee932b73812e8d 2180 freezegun_0.3.5-2.dsc
 3bb17f807551b095958c23d4a07d823e4fcc4d26 2032 freezegun_0.3.5-2.debian.tar.xz
 da50041a2e4591b34452cb9d303c465251a7d49b 6902 python-freezegun_0.3.5-2_all.deb
 ed7ada9b292ec64e8b72c482733d914872d1868a 6146 python3-freezegun_0.3.5-2_all.deb
Checksums-Sha256:
 4607711c4939ec6cb59463ef6f1f40eec0f376a6a43c2f5b00c6e246f40cff70 2180 
freezegun_0.3.5-2.dsc
 78a757e8f7e892167d6d5488b0ca7e4232629e50d5646a34879860e3080f2494 2032 
freezegun_0.3.5-2.debian.tar.xz
 8fc94540e2f93009812ca65d0a9c431755d82b501650b442b27ef343ae495fc5 6902 
python-freezegun_0.3.5-2_all.deb
 9e9ba1514ee1e896f2f6612099c7e22a660d6f14f30086225ee61d219f1d0d2c 6146 
python3-freezegun_0.3.5-2_all.deb
Files:
 

Bug#801869: nvidia-graphics-drivers: setting /dev/nvidia* to root:video 0660 breaks gdm3, sddm, ...

[Andreas Beckmann]

On 2015-10-19 01:20, Luca Boccassi wrote:
> Installed Ubuntu 15.10 beta2 on another partition to check. It's
> running with 352.
> 
> The devices are created with 666 root:root:
> 
> $ ls -l /dev/nvidia*
> crw-rw-rw- 1 root root 195,   0 Oct 19 00:13 /dev/nvidia0
> crw-rw-rw- 1 root root 195, 255 Oct 19 00:13 /dev/nvidiactl
> 
> Let me know if you would like to check anything else.

Can you "break" it with /etc/modprobe.d/nvidia-kernel-common.conf from
Debian? (maybe adjusting the module name... I don't know whether/how
they rename the modules)

I'm getting slightly tempted to 2s/^/#/ ...


Andreas

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Luca Boccassi]

On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrote:
> Hi all,
> 
> 
> Vladimir is right, same issue here. Indeed, It is weird to me not so
> many people is currently reporting on it, but it is affecting a lot of
> programs. Something happens when upgrading to version 0.6.x (I agree
> at this point)
> 
> 
> plasma-desktop is also unable to start and panic (black screen).If you
> update-alternative glx fall back to mesa, the desktop runs just fine
> (of course, without the nvidia drivers)
> 
> 
> I though it was solved by bug 799948 (ssdm panic too), but again, it
> is not. At least you can "adduser sddm video" and make ssdm-greater
> works as a workaround, but plasma-desktop panics still panics after
> you try to log on.
> 
> 
> 
> It is very easy to check it. Just install a fresh installation of KDE
> and nvidia drivers and you will see a beautiful black screen. Let me
> know if you need additional information but it is quite easy to
> reproduce

Hi,

Could you please attach the output of:

reportbug --template glx-alternative-nvidia
reportbug --template nvidia-driver

Kind regards,
Luca Boccassi

Bug#802129: marked as done (python-u2flib-server: FTBFS: ImportError: No module named setuptools)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 21:21:14 +
with message-id 
and subject line Bug#802129: fixed in python-u2flib-server 3.2.0-2
has caused the Debian Bug report #802129,
regarding python-u2flib-server: FTBFS: ImportError: No module named setuptools
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.)


-- 
802129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-u2flib-server
Version: 3.2.0-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Traceback (most recent call last):
  File "setup.py", line 28, in 
from u2flib_server.yubicommon import setup
  File "/python-u2flib-server-3.2.0/u2flib_server/yubicommon/__init__.py", line 
33, in 
from setuptools import setup as _setup, find_packages, Command
ImportError: No module named setuptools
E: pybuild pybuild:262: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean --test-nose -i python{version} -p 2.7 --dir . 
returned exit code 13

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-u2flib-server.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-u2flib-server
Source-Version: 3.2.0-2

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated 
python-u2flib-server 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: Sun, 18 Oct 2015 21:00:42 +0100
Source: python-u2flib-server
Binary: python-u2flib-server
Architecture: source all
Version: 3.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Arvid Requate 
Changed-By: Federico Ceratto 
Description:
 python-u2flib-server - Universal 2nd Factor (U2F) server communication Python 
module
Closes: 802129
Changes:
 python-u2flib-server (3.2.0-2) unstable; urgency=medium
 .
   * Add setuptools dependency (Closes: 802129)
Checksums-Sha1:
 bd1c4c0fd8b274a039d4a2dcfe8ae6bdeb4961ab 2190 python-u2flib-server_3.2.0-2.dsc
 21a59247ee4cd228d459b170add85440efa31d0b 4988 
python-u2flib-server_3.2.0-2.debian.tar.xz
 c8c93e8c8d6e06c056449a3f852ffb9d298c8788 21266 
python-u2flib-server_3.2.0-2_all.deb
Checksums-Sha256:
 7e5e8e707a2d9e5cdb90d87a4518b289a422d8d516c7a6c42229abae80525164 2190 
python-u2flib-server_3.2.0-2.dsc
 3354dae1867890d8d06049ed522dec2384dadeddb72a2aba11d5de4c74e8b132 4988 
python-u2flib-server_3.2.0-2.debian.tar.xz
 dc9ab4567cc2c83bc134aa6c289898514945f2090b3671f24d6c5daa58df7c59 21266 
python-u2flib-server_3.2.0-2_all.deb
Files:
 5575cd9211763758ef452382bdb8a4a4 2190 python optional 
python-u2flib-server_3.2.0-2.dsc
 4484db20fa9ba3dbd19d824a01b61028 4988 python optional 
python-u2flib-server_3.2.0-2.debian.tar.xz
 a1ff454e5e859ce08b451566ee7f4b5e 21266 python optional 
python-u2flib-server_3.2.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWI/q6AAoJEG8xvET1F32qHCcP/1CTJ+yFicONbb5umYKcwFz5
kk8YJbA/1LCp7xBlIv+vLSxEyMzR2U8IxmZRPsJDHeZ37aV6qJZ5uzMOO2ilbKbi
tdJcw2ecgw66Q3LGtFszBsRTnvBVfZ/Ch6WE7uW3cwCW4WGfUyUpNrCUYbZ2KRZd
PksNUtT3zka2hKOHp79qd7N0tDOD/JxsrtHTI64oXskr28ekEQnkVmmzvs/0ru92
iOSg9HnnXl65Qepse5fPmbXranzb4/S1MqvCeatymy+fiWUVxY3wJ39kvR5TrkuH
10CydpXxmjunrsqS17IMQPuvrlWmRBMBNgtfQtQLHcKErqiVondTfPEeMG2bBj5Y
T/4dRYH9JjuvGNWLICvvxRCp07QXyJk3wOqjpbJqvdbRO9l+MG3DaBgKbrESqeq/
UcosbeGEWaSDnZpRpowImoec9v/x4hAtT7Q92pwDChoR2TAollSIUbxovsXVgpjf
EmlE7MiDkH27/FEp2QDzsFNVic+5C3Zv/B79o+ylT2x0RC75g4V55+kCTsB9WFGe
b+Rw/JG3b27d/B3gTASq9fAInBHcMgxbdCjwk6CRXGoFQWPTZrI1qfah/2/tQ4Tk

Bug#802158: marked as done (python-spur: FTBFS: ImportError: No module named 'paramiko')

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 21:21:09 +
with message-id 
and subject line Bug#802158: fixed in python-spur 0.3.14-2
has caused the Debian Bug report #802158,
regarding python-spur: FTBFS: ImportError: No module named 'paramiko'
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.)


-- 
802158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-spur
Version: 0.3.14-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

OK
I: pybuild base:170: cd /python-spur-0.3.14/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m unittest discover -v 
spur (unittest.loader._FailedTest) ... ERROR

==
ERROR: spur (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: spur
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File "/python-spur-0.3.14/.pybuild/pythonX.Y_3.5/build/spur/__init__.py", 
line 2, in 
from spur.ssh import SshShell
  File "/python-spur-0.3.14/.pybuild/pythonX.Y_3.5/build/spur/ssh.py", line 15, 
in 
import paramiko
ImportError: No module named 'paramiko'


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/python-spur-0.3.14/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest 
discover -v 

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-spur.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-spur
Source-Version: 0.3.14-2

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

Debian distribution maintenance software
pp.
Ruben Undheim  (supplier of updated python-spur 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Oct 2015 10:27:41 +0200
Source: python-spur
Binary: python-spur python3-spur
Architecture: source
Version: 0.3.14-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ruben Undheim 
Description:
 python-spur - Run commands easily over SSH
 python3-spur - Run commands easily over SSH (Python3)
Closes: 802158
Changes:
 python-spur (0.3.14-2) unstable; urgency=medium
 .
   * debian/control: add python-paramiko and python3-paramiko to
 build-dependencies
 - Fixes FTBFS (test suite problem) (Closes: #802158)
   * Converted to git-dpm patch management
Checksums-Sha1:
 c16e9446e95f747743a78e966b53d13addd2da86 2145 python-spur_0.3.14-2.dsc
 78bbaa349e1dea2648a27d3b7c55bbd119611fa3 2328 
python-spur_0.3.14-2.debian.tar.xz
Checksums-Sha256:
 a6ae639dbe433e325b1dda7843cdef137c1731b486799de44976affd45a9ace4 2145 
python-spur_0.3.14-2.dsc
 d00497dd56ba522ff43d6a568aa82b125a4650062a14f2c635368847d0b2f7f7 2328 
python-spur_0.3.14-2.debian.tar.xz
Files:
 97a51543da3d1ffc15ae6bcb86111f99 2145 python optional python-spur_0.3.14-2.dsc
 5b2e497a7313ae3fd17eac58202b6576 2328 python optional 
python-spur_0.3.14-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWJAvKAAoJEPxqH2TRCNERvBwP/2ubk9i2WzOj96PjADB3IMXp
TTIlOjN/kMbigW5/1GPxKdVpF5PJfFqdLFEwJWCxiN2MXlNiGw1BAtxrAAX87A3w
oq9P6shaND8NXAKBwz17b/JCridwjkHJL04fGengFtaM6ebuAEArsLoV9EdbOQvQ

Bug#800574: Final analysis for Broadwell

[Henrique de Moraes Holschuh]

On Sun, 18 Oct 2015, Aurelien Jarno wrote:
> On 2015-10-07 07:32, Henrique de Moraes Holschuh wrote:
> > Meanwhile, a suggestion by Samuel Thibault to try to use hwcap did
> > provide for a possible long-term plan to fine-tune the lock-elision
> > blacklist (and anything else of that sort).
> > 
> > We would have to (finally) extend x86-64 hwcap to cpuid(1) fully, and
> > also at least cpuid(7), which is anything but trivial and a lot of work.
> >  This is _not_ worth the trouble if it is done just for lock elision
> > blacklisting purposes.
> > 
> > However, it would be useful for link-time optimization in libraries
> > (e.g. avx2 flavours of something that really benefits from it, etc), so
> > it is likely worth pursuing... but only if we get buy-in from upstream.
> 
> Why do you believe that hwcap is better for handling that than the
> current STT_GNU_IFUNC mechanism?

I was not aware of STT_GNU_IFUNC.  I will look into it.

> 5) Finally it means that we need to provide a version of the libc for
> all combinations. Think on i386, we would need to provide:
>  - libc6
>  - libc6-i686
>  - libc6-i686-tsx
>  - libc6-xen
>  - libc6-xen-tsx

No.  We need nothing of the sort for Intel TSX.  TSX-NI is something
already detected at runtime by glibc using the cpuid instruction, there
is no need to use the dynamic loader's hwcap object selection for this.

What I proposed was to extend the kernel-supplied hwcap area for x86-64
(and x32, I suppose) to export the full flags information returned by
CPUID.EAX=1, and also by CPUID.EAX=7 to all processes... and use _that_
instead of a direct call to the cpuid instruction to detect Intel TSX
(and anything else based on cpuid(1) and cpuid(7) in glibc).

We could do it for 32-bit too, I suppose.  But if hardware-assisted lock
elision is important enough to justify that kind of work for i686, that
just means we should deploy x32 instead, as far as I'm concerned.

Then, change glibc to use this extended hwcap information to detect such
runtime-selected features instead of calling the cpuid instruction
directly on the processor.  On an older kernel without the extended
hwcap fields, either call cpuid directly, or disable them.

However, for stuff like AVX512, you might want to have the *entire*
library compiled with a much more advanced instruction set (based on the
fact that AVX512 being available also implies that very fast SSE4.2 is
available, for example).  It would be possible to use the dynamic
linker's hwcap support to do that, if one wanted to.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Bug#802118: [pkg-opensc-maint] Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.

[Persmule]

Dear Maintainer,

I don't know whether it is easy to exploit. But I believe every memory
bug related to a security-oriented package is grave.

By the way, I managed creating a patch locally, may it be useful for you.

Persmule

On Sun, 18 Oct 2015 17:31:08 -0400 Eric Dorland  wrote:
> * persmule (persm...@gmail.com) wrote:
> > Package: libengine-pkcs11-openssl
> > Version: 0.1.8-5
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> >
> > Dear Maintainer,
> >
> > Functions in src/engine_pkcs11.c to set static global data (set_module,
> > set_pin, get_pin and set_init_args) do not free memories pointed by the
> > corresponding pointers before assigning them to newly allocated
> > memories, which
> > may cause memory leaks if they are called more than once.
> >
> > The bugs related to set_module, set_pin and get_pin are fixed on
> > upstream, but
> > the one of set_init_args is not.
>
> Agreed that these are valid memory leaks but what's the security
> implication? This doesn't seem obviously exploitable.
>
> --
> Eric Dorland 
> 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93

Description: 
 Functions in src/engine_pkcs11.c to set static global data
 (set_module, set_pin, get_pin and set_init_args) do not free
 memories pointed by the corresponding pointers before assigning
 them to newly allocated memories, which may cause memory leaks
 if they are called more than once.
 .
 engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium
 .
   * src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)
Author: Xie Tianming 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 

--- engine-pkcs11-0.1.8.orig/src/engine_pkcs11.c
+++ engine-pkcs11-0.1.8/src/engine_pkcs11.c
@@ -62,10 +62,22 @@ static char *init_args = NULL;
 
 int set_module(const char *modulename)
 {
+	free(module);
 	module = modulename ? strdup(modulename) : NULL;
 	return 1;
 }
 
+/* Free PIN storage in secure way. */
+static void zero_pin(void)
+{
+	if (pin != NULL) {
+		OPENSSL_cleanse(pin, pin_length);
+		free(pin);
+		pin = NULL;
+		pin_length = 0;
+	}
+}
+
 /**
  * Set the PIN used for login. A copy of the PIN shall be made.
  *
@@ -89,6 +101,7 @@ int set_pin(const char *_pin)
 
 	/* Copy the PIN. If the string cannot be copied, NULL
 	   shall be returned and errno shall be set. */
+	zero_pin();
 	pin = strdup(_pin);
 	if (pin != NULL)
 		pin_length = strlen(pin);
@@ -115,6 +128,7 @@ static int get_pin(UI_METHOD * ui_method
 
 	/* pin in the call back data, copy and use */
 	if (mycb != NULL && mycb->password) {
+		zero_pin();
 		pin = (char *)calloc(MAX_PIN_LENGTH, sizeof(char));
 		if (!pin)
 			return 0;
@@ -147,6 +161,7 @@ static int get_pin(UI_METHOD * ui_method
 
 int set_init_args(const char *init_args_orig)
 {
+	free(init_args);
 	init_args = init_args_orig ? strdup(init_args_orig) : NULL;
 	return 1;
 }

engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium

  * src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)

 -- Xie Tianming   Mon, 19 Oct 2015 09:19:53 +0800

engine-pkcs11 (0.1.8-5) unstable; urgency=medium

  * debian/source/options, debian/source/patch-header: Remove obsolete
source control files.
  * debian/watch: Fix URL.
  * debian/control: Move maintainer to
pkg-opensc-ma...@lists.alioth.debian.org to and myself to Uploaders.
  * debian/copyright: Move to DEP5 copyright file.
  * debian/gbp.conf: Use pristine-tar.
  * debian/control, debian/rules: Use dh-autoreconf.

 -- Eric Dorland   Sun, 10 May 2015 15:49:32 -0400

engine-pkcs11 (0.1.8-4) unstable; urgency=medium

  * debian/control: Standards-Version to 3.9.6.
  * debian/control: Add Vcs-* fields.
  * debian/control: Add Homepage field.
  * debian/watch: Update with new GitHub location.
  * debian/control: Run wrap-and-sort.

 -- Eric Dorland   Sat, 20 Sep 2014 19:03:02 -0400

engine-pkcs11 (0.1.8-3) unstable; urgency=low

  * debian/control, debian/rules: Use autotools-dev.
  * debian/compat, debian/control: Use debhelper v9.
  * debian/control: Upgrade Standards-Version to 3.9.4.

 -- Eric Dorland   Wed, 11 Sep 2013 23:52:42 -0400

engine-pkcs11 (0.1.8-2) unstable; urgency=low

  * debian/rules: Actually install the engine in the correct
location.(Closes: #566971)

 -- Eric Dorland   Tue, 09 Feb 2010 02:33:41 -0500

engine-pkcs11 (0.1.8-1) unstable; urgency=low

  * New upstream release. (Closes: #564056)
  * debian/libengine-pkcs11-openssl.links: Engine is now installed into
the correct location 

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

Hi Luca,

Thanks for the quick answer!

Here you have both report you asked for. Hopefully it will help us to know
where the issue is.

Regards

On Sun, Oct 18, 2015 at 9:43 PM, Luca Boccassi 
wrote:

> On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrote:
> > Hi all,
> >
> >
> > Vladimir is right, same issue here. Indeed, It is weird to me not so
> > many people is currently reporting on it, but it is affecting a lot of
> > programs. Something happens when upgrading to version 0.6.x (I agree
> > at this point)
> >
> >
> > plasma-desktop is also unable to start and panic (black screen).If you
> > update-alternative glx fall back to mesa, the desktop runs just fine
> > (of course, without the nvidia drivers)
> >
> >
> > I though it was solved by bug 799948 (ssdm panic too), but again, it
> > is not. At least you can "adduser sddm video" and make ssdm-greater
> > works as a workaround, but plasma-desktop panics still panics after
> > you try to log on.
> >
> >
> >
> > It is very easy to check it. Just install a fresh installation of KDE
> > and nvidia drivers and you will see a beautiful black screen. Let me
> > know if you need additional information but it is quite easy to
> > reproduce
>
> Hi,
>
> Could you please attach the output of:
>
> reportbug --template glx-alternative-nvidia
> reportbug --template nvidia-driver
>
> Kind regards,
> Luca Boccassi
>
>

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of 

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Luca Boccassi]

On 18 October 2015 at 22:23, Miguel Angel Rojas  wrote:
> Hi Luca,
>
> Thanks for the quick answer!
>
> Here you have both report you asked for. Hopefully it will help us to know
> where the issue is.

Nothing seems wrong in the setup.

What is the exact error you get with plasma?

Kind regards,
Luca Boccassi

Bug#802281: icedove: Stuck at "Welcome to Icedove"

[Eliot Blennerhassett]

Package: icedove
Version: 42.0~b1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I run icedove, the "Welcome to Icedove" dialog appears.
However, none of the the three buttons on that dialog results in the dialog
closing.
The only thing to be done is kill the application.

This is a new install of icedove on a  new system (so no preexisting profile).

I am running icedove (42.0~b1-1) from experimental (installed over (38.3.0-1))
Both do the same thing.

regards

Eliot



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

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

Versions of packages icedove depends on:
ii  debianutils   4.5.1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libc6 2.19-22
ii  libcairo-gobject2 1.14.2-2
ii  libcairo2 1.14.2-2
ii  libdbus-1-3   1.10.0-3
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.2.1-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-22
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libglib2.0-0  2.46.1-1
ii  libgtk-3-03.18.2-1
ii  libhunspell-1.3-0 1.3.3-3+b1
ii  libicu55  55.1-5
ii  libnspr4  2:4.10.9-2
ii  libnss3   2:3.20-1
ii  libpango-1.0-01.38.0-3
ii  libpangocairo-1.0-0   1.38.0-3
ii  libpangoft2-1.0-0 1.38.0-3
ii  libpixman-1-0 0.33.2-2
ii  libsqlite3-0  3.8.11.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.2.1-22
ii  libvpx2   1.4.0-4
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  psmisc22.21-2.1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
pn  iceowl-extension  

Versions of packages icedove suggests:
ii  fonts-lyx 2.1.4-2
ii  libgssapi-krb5-2  1.13.2+dfsg-2

-- no debconf information

Bug#782456: Bug also in GDM

[Carlos Prieto López]

Dear maintainer:

Yesterday I installed Stretch (the last weekly build). Installed plymouth
and it ran without problem. With today's update, the problem described in
this bug started: the splash screen shows, but freees before switching to
GDM.

-If pressing Esc on time, the problem does not show
-If removing splash parameter from linux in grub, the problem does not show
-It happens with spinner as well as joy themes
-The system completely blocks Ctrl+Alt+F1 does not work (neither other
virtual terminals), nor Ctrl+Alt+Del
-Only Alt+ Req Sys+ rsuib restarts the system

Plymouth version: 0.9.2-1
Graphic card: Intel

Regards.

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Sun, Oct 18, 2015 at 08:43:50PM +0100, Luca Boccassi wrote:

 
> Could you please attach the output of:
> 
> reportbug --template glx-alternative-nvidia
> reportbug --template nvidia-driver

*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Vladmimir Stavrinov ' as your from address.
Getting status for glx-alternative-nvidia...
Will send report to Debian (per lsb_release).
Maintainer for glx-alternative-nvidia is 'Debian NVIDIA Maintainers 
'.
Looking up dependencies of glx-alternative-nvidia...
Getting status for related package glx-diversions...
Looking up 'depends' of related package glx-diversions...
Looking up 'recommends' of related package glx-diversions...
Getting status for related package nvidia-glx...
Getting status for related package fglrx-driver...
Looking up status of additional packages...

Rewriting subject to 'glx-alternative-nvidia: none'
Gathering additional data, this may take a while...
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Vladmimir Stavrinov 
To: Debian Bug Tracking System 
Subject: glx-alternative-nvidia: none

Package: glx-alternative-nvidia
Version: 0.6.91
Severity: wishlist

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of 

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Sun, Oct 18, 2015 at 11:03:35PM +0100, Luca Boccassi wrote:

> Nothing seems wrong in the setup.

The problem is not about setup.

> What is the exact error you get with plasma?

The problem is not about "exact error".

The problem is about GLX, that doesn't works with any software.
Errors may be differ. But segfault is common.

###  Vladimir Stavrinov  ###

Bug#800574: marked as done (libc6: lock elision hazard on Intel Broadwell and Skylake)

[Debian Bug Tracking System]

Your message dated Mon, 19 Oct 2015 05:19:14 +
with message-id 
and subject line Bug#800574: fixed in glibc 2.21-0experimental2
has caused the Debian Bug report #800574,
regarding libc6: lock elision hazard on Intel Broadwell and Skylake
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.)


-- 
800574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.19-4
Severity: grave
Justification: causes non-serious data loss

Intel Broadwell-H and Skylake-S/H have critical errata that causes HLE
to be extremely dangerous to use on those processors, resulting in
unpredictable behavior (i.e. process crashes when you are lucky, data
corruption when you are not) when hardware lock-elision is enabled in
glibc/libpthread.

Broadwell errata BBD50 (desktop/mobile), BDW50 (server):

An HLE (Hardware Lock Elision) transactional region begins with
an instruction with the XACQUIRE prefix.  Due to this erratum,
reads from within the transactional region of the memory
destination of that instruction may return the value that was
in memory before the transactional region began

According to the Intel errata list, a firmware fix is possible, but I
have no idea whether it is done by toggling a boot-locked MSR that
disables HLE, or through a microcode update.  The MSR is more likely,
but if it is a microcode update, it is going to be as much of a hazard
as the Haswell one that disabled TSX+HLE.

I recommend that we extend the HLE blacklist in glibc to also include
CPU signature 0x40671.  This will disable HLE on Xeon E3-1200v4, and
5th-generation Core i5/i7.  These processors are supposed to already
have TSX disabled (errata BBD51/BDW51).

Skylake's latest public specification update still doesn't list any HLE
errata, but it is not really recent.  OTOH, there is a Gentoo user's
report that Skylake is also unstable when HLE is enabled in glibc and
that the crashes stop when glibc is compiled without lock elision.

For that reason, it might be a good idea to also blacklist HLE on CPU
signatures 0x506e1, 0x506e2 and 0x506e3, which would disable HLE on
Skylake-S and Skylake-H (6th gen Core i5/i7).  This won't cover the
Skylake Xeon E3-1200v5, for which there are no reports of breakage (nor
a public specification update I could find).

References: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762195
https://bbs.archlinux.org/viewtopic.php?id=202545

In hindsight, it looks like we would have been better off by disabling
lock elision entirely for Debian jessie when we fixed #762195.
Something to consider when the time comes to fix this bug in stable
through a stable update...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.21-0experimental2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 19 Oct 2015 00:20:34 +0200
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 

Bug#802251: marked as done (usbview: does not run on modern Debian system)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 20:36:55 +0100
with message-id <20151018193655.gz14...@sirena.org.uk>
and subject line Re: Bug#802251: usbview: does not run on modern Debian system
has caused the Debian Bug report #802251,
regarding usbview: does not run on modern Debian system
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.)


-- 
802251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usbview
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Upon running usbview, it looks for a usbdevfs devices file in
/sys/kernel/debug/usb/devices.  When this is, of course, not found, a window
is presented, asking for the correct location of the non-existend usbdevfs
devices file.

Leaving out that usbdevfs has been usbfs for probably 10 years now, and that
there is no devices 'file' related to USB at all in the /sys dir tree, if
one tries to change the "Location of usbdevfs devices file" to something
that exists, like anything in /sys/bus/usb/drivers/usbfs/*, then the
application hangs until killed.

It does not work as shipped, and the only action that usbview can complete
successfully is to hang.

usbview should be removed from testing/stretch: it is completely
disfunctional. It's last documentation update was in 2002. 

usbview is also unable to be built from source: it's config script dies when
testing for c++ as the config file is incorrect but that's another bug.




-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)

Kernel: Linux 4.2.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Sun, Oct 18, 2015 at 09:49:20PM +0300, Stephen McGregor wrote:

> Upon running usbview, it looks for a usbdevfs devices file in
> /sys/kernel/debug/usb/devices.  When this is, of course, not found, a window
> is presented, asking for the correct location of the non-existend usbdevfs
> devices file.

Works for me with v4.2, the file is still provided by the kernel.  The
issue you are most likely seeing is that by default debugfs is not
readable by users for security reasons so can't be read, if you
configure your system to allow access to it then it can be parsed just
fine.

Ideally the program would use libusb but it can still function.


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

Bug#798421: Please don't depend specifically on the OpenSSL variant of Curl

[Josh Triplett]

On Wed, Sep 09, 2015 at 12:53:42PM +1000, Russell Sim wrote:
> On 9 September 2015 at 12:37, Josh Triplett  wrote:
> 
> > I'd like to use libgit2 for projects under the GPL.  Would you please
> > consider either building libgit2 against the gnutls version of Curl, or
> > otherwise making it possible to avoid building with OpenSSL, for the
> > benefit of GPLed projects?
> >
> 
> Fair call, this should be pretty straight forward.  I thought it was
> required for threading, but this doesn't seem to be the case.
> 
> A new version will be released shortly, I can move to the gnutls version of
> curl then.
> 
> Thanks for looking into this.

Any update on this issue?

- Josh Triplett

Bug#802188: marked as done (bochs: Support building under Linux 4.x)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 22:18:48 +
with message-id 
and subject line Bug#802188: fixed in bochs 2.6-5
has caused the Debian Bug report #802188,
regarding bochs: Support building under Linux 4.x
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.)


-- 
802188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bochs
Version: 2.6-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
Tags: patch

Hi,

The configure script checks `uname -r` and checks for 2.6 or 3.x, etc.,
rejecting any others. but the latest kernel version at the time of
writing is 4.2.3. Severity serious as this therefore will FTBFS under
your typical developer system running sid.

A patch is attached that reverses this logic, rejecting 2.2 and
essentially allowing anything 2.6+.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/configure.in b/configure.in
index f6f1513..aadb82b 100644
--- a/configure.in
+++ b/configure.in
@@ -713,17 +713,17 @@ AC_ARG_ENABLE(pcidev,
   AC_MSG_NOTICE([Linux detected as host for PCI host device mapping])
   linux_version=`uname -r`
  case "$linux_version" in
+   2.2*)
+   AC_MSG_ERROR([Linux kernel 2.4, 2.6 or 3.x is required 
for PCI host device mapping])
+   ;;
2.4*)
PCIDEV_MODULE_MAKE_ALL="all-kernel24"
KERNEL_MODULE_SUFFIX="o"
;;
-   2.6*|3.*)
+   *)
PCIDEV_MODULE_MAKE_ALL="all-kernel26"
KERNEL_MODULE_SUFFIX="ko"
;;
-   *)
-   AC_MSG_ERROR([Linux kernel 2.4, 2.6 or 3.x is required 
for PCI host device mapping])
-   ;;
  esac
  KERNELDIR="/lib/modules/$linux_version/build"
  LSMOD="lsmod"
--- End Message ---
--- Begin Message ---
Source: bochs
Source-Version: 2.6-5

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated bochs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Oct 2015 00:05:38 +0200
Source: bochs
Binary: bochs bochs-doc bochsbios bochs-wx bochs-sdl bochs-term bochs-x bximage 
sb16ctrl-bochs
Architecture: source
Version: 2.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 bochs  - IA-32 PC emulator
 bochs-doc  - Bochs upstream documentation
 bochs-sdl  - SDL plugin for Bochs
 bochs-term - Terminal (ncurses-based) plugin for Bochs
 bochs-wx   - WxWindows plugin for Bochs
 bochs-x- X11 plugin for Bochs
 bochsbios  - BIOS for the Bochs emulator
 bximage- Disk Image Creation Tool for Bochs
 sb16ctrl-bochs - control utility for Bochs emulated SB16 card
Closes: 802188
Changes:
 bochs (2.6-5) unstable; urgency=medium
 .
   * QA upload.
   * Apply patch from Chris Lamb to build under recent versions of Linux.
 Closes: #802188.
Checksums-Sha1:
 757fdeb809460cee4d29a8fedff5d8495fa47214 2184 bochs_2.6-5.dsc
 f485f3a50b2cde1c9eb48f876c16a710ec7ff333 40992 bochs_2.6-5.debian.tar.xz
Checksums-Sha256:
 3a593ea5111ca7d208f8ea0a5aef70ce13c1527b945d40663ed46fafe9e98620 2184 
bochs_2.6-5.dsc
 5210e4fa577ab1d654c76897a812a16f3fc323a80e2e47654acd3d1eea10490e 40992 
bochs_2.6-5.debian.tar.xz
Files:
 8a961e391d0859b96710f78c0b1463b5 2184 otherosfs extra bochs_2.6-5.dsc
 fd9bb9d3275400d62ad1b40674d0e725 40992 otherosfs extra 
bochs_2.6-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWJBgAAAoJEEHOfwufG4syzhAIAJvMMi69dia/hThQHv2raWX5

Bug#802192: marked as done (gabedit: FTBFS: recipe for target 'override_dh_compress' failed)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 22:33:44 +
with message-id 
and subject line Bug#802192: fixed in gabedit 2.4.8-2
has caused the Debian Bug report #802192,
regarding gabedit: FTBFS: recipe for target 'override_dh_compress' failed
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.)


-- 
802192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gabedit
Version: 2.4.8-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

   debian/rules override_dh_compress
make[1]: Entering directory '/gabedit-2.4.8'
dh_compress 
/gabedit-2.4.8/debian/gabedit/usr/share/doc/gabedit/examples/exampleGeoConv.gab
gzip: . is a directory -- ignored
dh_compress: gzip -9nf . usr/share/doc/gabedit/changelog 
usr/share/doc/gabedit/changelog.Debian 
usr/share/doc/gabedit/examples/exampleCartezian.gab 
usr/share/doc/gabedit/examples/exampleSpheric.gab 
usr/share/doc/gabedit/examples/gtkrc usr/share/man/man1/gabedit.1 returned exit 
code 2
debian/rules:61: recipe for target 'override_dh_compress' failed
make[1]: *** [override_dh_compress] Error 2
make[1]: Leaving directory '/gabedit-2.4.8'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/gabedit.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: gabedit
Source-Version: 2.4.8-2

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated gabedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Oct 2015 00:12:18 +0200
Source: gabedit
Binary: gabedit
Architecture: source amd64
Version: 2.4.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Daniel Leidert 
Description:
 gabedit- graphical user interface to Ab Initio packages
Closes: 802192
Changes:
 gabedit (2.4.8-2) unstable; urgency=medium
 .
   * debian/compat: Raised to level 9.
   * debian/control (Build-Depends): Raised debhelper version accordingly.
 (Standards-Version): Bumped to 3.9.6.
   * debian/gabedit.menu: Removed (CTTE #741573).
   * debian/rules (override_dh_compress): Remove non-package specific directory
 part from the target (closes: #802192).
   * debian/upstream: Renamed to debian/upstream/metadata.
Checksums-Sha1:
 f0409f6040388b9fbfdc3c1054b05baeabe4190f 2075 gabedit_2.4.8-2.dsc
 debc2997d2858ab017b5d7a59664f0ea8c236c69 11220 gabedit_2.4.8-2.debian.tar.xz
 49dbe73ff1155f4b141e2d46dd299746f0bcfed5 1676656 gabedit_2.4.8-2_amd64.deb
Checksums-Sha256:
 d6dc60e22a2680842580945bd4ba1e6160d9bbc696c0d2dc2a7cbbe4d7a17b40 2075 
gabedit_2.4.8-2.dsc
 197f3ad3cb50151d78e69be5efec04437f339ab2bc74c90b491c894c6c7c1780 11220 
gabedit_2.4.8-2.debian.tar.xz
 1f63da0a6209500796dddb7c43131b22e45e5f69177730b9742def8a80f6c670 1676656 
gabedit_2.4.8-2_amd64.deb
Files:
 be5f5fcc84940283b171b67535485753 2075 science optional gabedit_2.4.8-2.dsc
 3e93082d78535e8d87056627517240e3 11220 science optional 
gabedit_2.4.8-2.debian.tar.xz
 7b06d76533c4d4c9414e979c46caf7ea 1676656 science optional 
gabedit_2.4.8-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWJBrXAAoJEEvNBWfCltBd0NsQANr3/nzBmkQEmQZLvVKaXsEm
EmU1aglZO6yKivYzYl/DpgXTba7RWzLYzTOyhl22J/o9XrbAgiyJa9Eola/56MXN
m8rDRrkmVwySJ/r14YWqSxltDkmxFCbkddLahK5qQzNJ3g91IVvuv44tqFbiLShW
qH10n+RSf9cDjdsiBe9qxEQHFj7zAAHHgL5d0ejEBTrA/SS3FVdoB8uApu+32IHO
5ts5esSi2QxaAsv92y8z39uxkIIWgY8nnCuCPMCj5PYY/htHLJXGNQxHG83hI4yc
V94D64SCT01bSKgLFb1d9VdHqrE/dax9639sRcyAXiUn6+xnd+sF24GDj+lJFOSe

Bug#785898: freerdp: Please update to GStreamer 1.x

[Laurent Bigonville]

Package: src:freerdp
Followup-For: Bug #785898

Hi,

Quickly looking at upstream git repository, it seems that they now
support gst 1.0, so I guess it would be a good idea to upgrade the git
snapshot.

Cheers,

Laurent Bigonville

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

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

Bug#801869: nvidia-graphics-drivers: setting /dev/nvidia* to root:video 0660 breaks gdm3, sddm, ...

[Luca Boccassi]

On 17 October 2015 at 18:05, Andreas Beckmann  wrote:
> On 2015-10-15 15:14, Andreas Beckmann wrote:
>> Setting the permissions on /dev/nvidia* properly (i.e. root:video 0660)
>> breaks display managers that use acceleration (e.g. gdm3, sddm).
>
> BTW, how is this issue solved in other distributions? Ubuntu? Any other?
> Or are they all using 0666 default permissions?

Installed Ubuntu 15.10 beta2 on another partition to check. It's
running with 352.

The devices are created with 666 root:root:

$ ls -l /dev/nvidia*
crw-rw-rw- 1 root root 195,   0 Oct 19 00:13 /dev/nvidia0
crw-rw-rw- 1 root root 195, 255 Oct 19 00:13 /dev/nvidiactl

Let me know if you would like to check anything else.

Kind regards,
Luca Boccassi

Bug#802136: marked as done (python-launchpadlib: FTBFS: test_get_token_and_login_is_deprecated 3 != 1)

[Debian Bug Tracking System]

Your message dated Mon, 19 Oct 2015 00:19:05 +
with message-id 
and subject line Bug#802136: fixed in python-launchpadlib 1.10.3-3
has caused the Debian Bug report #802136,
regarding python-launchpadlib: FTBFS: test_get_token_and_login_is_deprecated 3 
!= 1
to be marked as done.

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

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


-- 
802136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-launchpadlib
Version: 1.10.3-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

test_service_name_with_embedded_version 
(launchpadlib.tests.test_launchpad.TestServiceNameWithEmbeddedVersion) ... ok

==
FAIL: test_get_token_and_login_is_deprecated 
(launchpadlib.tests.test_launchpad.TestDeprecatedLoginMethods)
--
Traceback (most recent call last):
  File "src/launchpadlib/tests/test_launchpad.py", line 591, in 
test_get_token_and_login_is_deprecated
self.assertEqual(len(caught), 1)
AssertionError: 3 != 1

==
FAIL: test_login_is_deprecated 
(launchpadlib.tests.test_launchpad.TestDeprecatedLoginMethods)
--
Traceback (most recent call last):
  File "src/launchpadlib/tests/test_launchpad.py", line 583, in 
test_login_is_deprecated
self.assertEqual(len(caught), 1)
AssertionError: 2 != 1

--
Ran 64 tests in 0.126s

FAILED (failures=2)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: 
python3.5 setup.py test 

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-launchpadlib.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-launchpadlib
Source-Version: 1.10.3-3

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated python-launchpadlib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Oct 2015 17:04:51 -0700
Source: python-launchpadlib
Binary: python-launchpadlib python3-launchpadlib
Architecture: source
Version: 1.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Stefano Rivera 
Changed-By: Stefano Rivera 
Description:
 python-launchpadlib - Launchpad web services client library
 python3-launchpadlib - Launchpad web services client library (Python 3)
Closes: 802136
Changes:
 python-launchpadlib (1.10.3-3) unstable; urgency=medium
 .
   * Fix test suite on Python 3.5 by ignoring PendingDeprecationWarnings from
 lazr.restfulclient. (Closes: #802136).
Checksums-Sha1:
 32703440a21d1c2e8b10bf46bbada0d833879d72 2213 python-launchpadlib_1.10.3-3.dsc
 54da6203dc7ab252fd49c89a31bd15cd21e40ac9 275052 
python-launchpadlib_1.10.3-3.debian.tar.xz
Checksums-Sha256:
 89a304b31b54f910552095e33c895a120f703e1c169ef7d68469fdf611d1c3ba 2213 
python-launchpadlib_1.10.3-3.dsc
 c80c76fee893daf2faacd645c525d2a98926a89a3066c653e99f02f6783bbb00 275052 
python-launchpadlib_1.10.3-3.debian.tar.xz
Files:
 74d06d58c1f0df029c91968b49a21a1a 2213 python optional 
python-launchpadlib_1.10.3-3.dsc
 3b2aabd1e06f15a301053452f282 275052 python optional 
python-launchpadlib_1.10.3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJWJDU0AAoJEOrxkryqPw9RLzkH/0mwq/+zv6ZmpGJ7D81a/Syj
qmEPYN0S7TiWSR5rDQsdZwTWIxywOuYmGtSM8x6ReuZHFaOAkMpfGbsc8fYD/i7y

Bug#802281: icedove: Stuck at "Welcome to Icedove"

[Eliot Blennerhassett]

I can also confirm that 64 bit thunderbird 38.3.0 does *not* have this 
problem.


On 19/10/15 13:54, Eliot Blennerhassett wrote:

Package: icedove
Version: 42.0~b1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I run icedove, the "Welcome to Icedove" dialog appears.
However, none of the the three buttons on that dialog results in the dialog
closing.
The only thing to be done is kill the application.

This is a new install of icedove on a  new system (so no preexisting profile).

I am running icedove (42.0~b1-1) from experimental (installed over (38.3.0-1))
Both do the same thing.

Bug#802289: go-mtpfs: FTBFS - "pkg-config": executable file not found in $PATH

[Aaron M. Ucko]

Source: go-mtpfs
Version: 0.0~git20150802.0.3ef47f9-1
Severity: serious
Justification: fails to build from source

Builds of go-mtpfs in minimal environments (such as on the
autobuilders) have been failing:

  github.com/hanwen/usb
  # pkg-config --cflags libusb-1.0
  pkg-config: exec: "pkg-config": executable file not found in $PATH

Please declare a build dependency on pkg-config, and confirm via
pbuilder or the like that you haven't missed anything else.

Thanks!

Bug#795104: Fwd: Bug#795104: Fwd: Re: Processed: found 795104 in 7.21-1

[Iain Lane]

See the attached diff of the latest upload (filtered to only include
debian/) - all of my changes are gone and the package is back to how it
was before.

On Sun, Oct 18, 2015 at 10:22:50AM +0200, Dirk Hünniger wrote:
> Hi Iain,
> as I can see from mediawiki2latex_7.21-1.debian.tar.xz in sid the patches
> still seem to be there. So I don't understand why your change did not make
> it into 7.21.
> Yours Dirk
> 
> On 17.10.2015 22:36, Iain Lane wrote:
> >On Sat, Oct 17, 2015 at 03:01:01PM +0200, Dirk Hünniger wrote:
> >>Hi Iain,
> >>since you resolved the issue in mediawiki2latex 7.20. Can you give me some
> >>more info on how I can resolve the issue with mediawiki2latex 7.21 and ghc
> >>7.8 on power pc. If it can be solved by changing the makefile, just send me
> >>the new makefile and I will publish a new version of mediawiki2latex with
> >>your makefile.
> >>Yours Dirk
> >You reverted my change with the latest upload, so it is broken once
> >again. You should fetch the diff of my NMU and reapply it, and keep it
> >around until we have ghc 7.10 in unstable. There's no real need to fix
> >it outside of packaging, as we are working around a ghc bug here.
> >
> 
> 

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
diff -Nru mediawiki2latex-7.20/debian/changelog 
mediawiki2latex-7.21/debian/changelog
--- mediawiki2latex-7.20/debian/changelog   2015-09-02 22:02:26.0 
+0100
+++ mediawiki2latex-7.21/debian/changelog   2015-07-12 19:24:15.0 
+0100
@@ -1,12 +1,10 @@
-mediawiki2latex (7.20-1.1) unstable; urgency=medium
+mediawiki2latex (7.21-1) unstable; urgency=medium
 
-  * Non-maintainer upload.
-  * Avoid using runhaskell (ghci), to work around bug on powerpc causing FTBFS
-(see Debian bug #789458) (Closes: #795104)
-  * Generalise the lintian override to catch all binary-or-shlib-defines-rpath
-instances.
+  * upgraded to the last upstream version
+  * Changed one word in the description
+  * updated lintian overrides
 
- -- Iain Lane   Wed, 02 Sep 2015 22:02:26 +0100
+ -- Georges Khaznadar   Mon, 29 Jun 2015 22:52:40 +0200
 
 mediawiki2latex (7.20-1) unstable; urgency=medium
 
diff -Nru mediawiki2latex-7.20/debian/control 
mediawiki2latex-7.21/debian/control
--- mediawiki2latex-7.20/debian/control 2015-05-09 12:52:36.0 +0100
+++ mediawiki2latex-7.21/debian/control 2015-07-12 19:23:17.0 +0100
@@ -40,6 +40,6 @@
  Much effort was put into providing reasonable defaults for this way
  of processing for the needs of the English and German Wikibooks
  projects. Images are also downloaded, and if necessary modified for
- use in a LaTeX document. Our latest test run on more than 2000
+ use in a LaTeX document. The latest test run on more than 2000
  featured articles on the English Wikipedia completed without
  failures.
diff -Nru mediawiki2latex-7.20/debian/lintian-overrides 
mediawiki2latex-7.21/debian/lintian-overrides
--- mediawiki2latex-7.20/debian/lintian-overrides   2015-05-25 
15:40:58.0 +0100
+++ mediawiki2latex-7.21/debian/lintian-overrides   1970-01-01 
01:00:00.0 +0100
@@ -1,125 +0,0 @@
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/ghc/template-haskell-2.9.0.0
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/transformers-compat-0.4.0.4
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/data-default-class-0.0.1
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/idna-0.3.0
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/hxt-regex-xmlschema-9.2.0.2
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/cipher-des-0.0.6
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/data-default-instances-containers-0.0.1
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/conduit-extra-1.1.7.1
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/conduit-1.2.4
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/ghc/containers-0.5.5.1
-E: mediawiki2latex: binary-or-shlib-defines-rpath usr/bin/mediawiki2latex 
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/hxt-unicode-9.0.2.4
-E: mediawiki2latex: binary-or-shlib-defines-rpath 

Bug#795104: Fwd: Bug#795104: Fwd: Re: Processed: found 795104 in 7.21-1

[Dirk Hünniger]

Hi Georges,
as far as I see right now the problem why the mediawiki2latex 7.21 does 
not work on build properly on powerpc and thus can not make it to 
testing is that we need to have overrides in the debian rules file. The 
proper rules file is included in the 
mediawiki2latex_7.20-1.1.debian.tar.xz . So could you please take that 
rules file and use it as new rules file for the new to be uploaded 
package mediawiki2latex_7.21-2 . We also should use this rules file for 
all further packages until ghc 7.10 is included in unstable and testing.

Yours Dirk
On 18.10.2015 20:24, Iain Lane wrote:

See the attached diff of the latest upload (filtered to only include
debian/) - all of my changes are gone and the package is back to how it
was before.

On Sun, Oct 18, 2015 at 10:22:50AM +0200, Dirk Hünniger wrote:

Hi Iain,
as I can see from mediawiki2latex_7.21-1.debian.tar.xz in sid the patches
still seem to be there. So I don't understand why your change did not make
it into 7.21.
Yours Dirk

On 17.10.2015 22:36, Iain Lane wrote:

On Sat, Oct 17, 2015 at 03:01:01PM +0200, Dirk Hünniger wrote:

Hi Iain,
since you resolved the issue in mediawiki2latex 7.20. Can you give me some
more info on how I can resolve the issue with mediawiki2latex 7.21 and ghc
7.8 on power pc. If it can be solved by changing the makefile, just send me
the new makefile and I will publish a new version of mediawiki2latex with
your makefile.
Yours Dirk

You reverted my change with the latest upload, so it is broken once
again. You should fetch the diff of my NMU and reapply it, and keep it
around until we have ghc 7.10 in unstable. There's no real need to fix
it outside of packaging, as we are working around a ghc bug here.

Bug#802248: awesome: FTBFS: ldoc: Error: no suitable Lua interpreter found

[Chris West (Faux)]

Source: awesome
Version: 3.5.6-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[3]: Entering directory '/awesome-3.5.6/obj-x86_64-linux-gnu'
/usr/bin/ldoc .
Error: no suitable Lua interpreter found
Error: supported versions are: 5.2
CMakeFiles/ldoc.dir/build.make:130: recipe for target 'CMakeFiles/ldoc' failed
make[3]: *** [CMakeFiles/ldoc] Error 1
make[3]: Leaving directory '/awesome-3.5.6/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:176: recipe for target 'CMakeFiles/ldoc.dir/all' failed
make[2]: *** [CMakeFiles/ldoc.dir/all] Error 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/awesome.html

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

Bug#802249: collectd: FTBFS: error: 'c_varnish_stats_t.. has no member named 'backend_toolate'

[Chris West (Faux)]

Source: collectd
Version: 5.5.0-3
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

varnish.c: In function 'varnish_monitor':
varnish.c:203:90: error: 'c_varnish_stats_t {aka const struct VSC_C_main}' has 
no member named 'backend_toolate'
   varnish_submit_derive (conf->instance, "backend", "connections", 
"was-closed"   , stats->backend_toolate);

  ^
varnish.c:232:88: error: 'c_varnish_stats_t {aka const struct VSC_C_main}' has 
no member named 'fetch_close'
   varnish_submit_derive (conf->instance, "fetch", "http_requests", "close" 
 , stats->fetch_close);

^
varnish.c:234:88: error: 'c_varnish_stats_t {aka const struct VSC_C_main}' has 
no member named 'fetch_oldhttp'
   varnish_submit_derive (conf->instance, "fetch", "http_requests", "oldhttp"   
 , stats->fetch_oldhttp);

^
varnish.c:236:88: error: 'c_varnish_stats_t {aka const struct VSC_C_main}' has 
no member named 'fetch_zero'
   varnish_submit_derive (conf->instance, "fetch", "http_requests", "zero"  
 , stats->fetch_zero);

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/collectd.html

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

Bug#802250: gfs2-utils: FTBFS: error: unknown type name 'cpg_error_t'

[Chris West (Faux)]

Source: gfs2-utils
Version: 3.1.3-1.2
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

cpg-new.c: In function ‘_send_message’:
cpg-new.c:345:2: error: unknown type name ‘cpg_error_t’
  cpg_error_t error;
  ^
cpg-new.c:353:15: error: ‘CPG_ERR_TRY_AGAIN’ undeclared (first use in this 
function)
  if (error == CPG_ERR_TRY_AGAIN) {
   ^
cpg-new.c:353:15: note: each undeclared identifier is reported only once for 
each function it appears in
cpg-new.c:361:15: error: ‘CPG_OK’ undeclared (first use in this function)
  if (error != CPG_OK) {
   ^

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/gfs2-utils.html

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

Bug#802251: usbview: does not run on modern Debian system

[Stephen McGregor]

Package: usbview
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Upon running usbview, it looks for a usbdevfs devices file in
/sys/kernel/debug/usb/devices.  When this is, of course, not found, a window
is presented, asking for the correct location of the non-existend usbdevfs
devices file.

Leaving out that usbdevfs has been usbfs for probably 10 years now, and that
there is no devices 'file' related to USB at all in the /sys dir tree, if
one tries to change the "Location of usbdevfs devices file" to something
that exists, like anything in /sys/bus/usb/drivers/usbfs/*, then the
application hangs until killed.

It does not work as shipped, and the only action that usbview can complete
successfully is to hang.

usbview should be removed from testing/stretch: it is completely
disfunctional. It's last documentation update was in 2002. 

usbview is also unable to be built from source: it's config script dies when
testing for c++ as the config file is incorrect but that's another bug.




-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)

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

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Sun, Oct 18, 2015 at 08:16:39PM +0200, Miguel Angel Rojas wrote:

>Vladimir is right, same issue here. Indeed, It is weird to me not so
>many people is currently reporting on it, but it is affecting a lot of

And even more weird is practice to close an issue without
confirmation from users who reported the problem, that it has been
solved.

###  Vladimir Stavrinov  ###

Bug#802190: genparse: FTBFS: Tests fail with segmentation fault

[Chris Lamb]

Source: genparse
Version: 0.9.1-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,

genparse fails to build from source in unstable/amd64:

  [..]

  ../../src/genparse -l C -g -o double_clp ./double.gp
  creating double_clp.h...done
  creating double_clp.c...done
  gcc -DHAVE_CONFIG_H -I. -I../..  -I./../../gnulib/lib -Wdate-time
  -D_FORTIFY_SOURCE=2  -g -O2 -fPIE -fstack-protector-strong -Wformat
  -Werror=format-security -Wall -pedantic -c double_clp.c
  gcc -DHAVE_CONFIG_H -I. -I../..  -I./../../gnulib/lib -Wdate-time
  -D_FORTIFY_SOURCE=2  -g -O2 -fPIE -fstack-protector-strong -Wformat
  -Werror=format-security -Wall -pedantic -c double_test.c
  In file included from double_test.c:23:0:
  gnulib_test.h:38:33: warning: initialization from incompatible pointer
  type [-Wincompatible-pointer-types]
 { "TestGenparse", NULL, NULL, test_genparse },
   ^
  gnulib_test.h:38:33: note: (near initialization for
  'suites[0].pSetUpFunc')
  gcc  -g -O2 -fPIE -fstack-protector-strong -Wformat
  -Werror=format-security -Wall -pedantic -L../../gnulib/lib -fPIE -pie
  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o double_test ftest.o
  double_clp.o double_test.o -lcunit -lgnu -ll 
  make[4]: Leaving directory '/tmp/buildd/genparse-0.9.1/tests/ccheck'
  make  check-TESTS
  make[4]: Entering directory '/tmp/buildd/genparse-0.9.1/tests/ccheck'
  /bin/bash: line 5: 59539 Segmentation fault  ${dir}$tst
  FAIL: default_test
  /bin/bash: line 5: 59544 Segmentation fault  ${dir}$tst
  FAIL: longmembers_test
  /bin/bash: line 5: 59549 Segmentation fault  ${dir}$tst
  FAIL: long_test
  /bin/bash: line 5: 59555 Segmentation fault  ${dir}$tst
  FAIL: ulong_test
  /bin/bash: line 5: 59560 Segmentation fault  ${dir}$tst
  FAIL: intmax_test
  /bin/bash: line 5: 59565 Segmentation fault  ${dir}$tst
  FAIL: uintmax_test
  /bin/bash: line 5: 59570 Segmentation fault  ${dir}$tst
  FAIL: double_test
  ===
  7 of 7 tests failed
  ===
  Makefile:632: recipe for target 'check-TESTS' failed
  make[4]: *** [check-TESTS] Error 1
  make[4]: Leaving directory '/tmp/buildd/genparse-0.9.1/tests/ccheck'
  Makefile:737: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  make[3]: Leaving directory '/tmp/buildd/genparse-0.9.1/tests/ccheck'
  Makefile:489: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory '/tmp/buildd/genparse-0.9.1/tests'
  Makefile:526: recipe for target 'check-recursive' failed
  make[1]: *** [check-recursive] Error 1
  make[1]: Leaving directory '/tmp/buildd/genparse-0.9.1'
  dh_auto_test: make -j1 check returned exit code 2
  debian/rules:68: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/genparse_0.9.1-1.build1.log.gz


Regards,

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


genparse.0.9.1-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#802199: bzr-loom: FTBFS: TypeError: _delta_to_float() takes exactly 3 arguments (2 given)

[Chris West (Faux)]

Source: bzr-loom
Version: 2.2.0-5
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

bzr selftest: /usr/bin/bzr
   /usr/lib/python2.7/dist-packages/bzrlib
   bzr-2.7.0dev1 python-2.7.10 
Linux-4.2.0-16-generic-x86_64-with-debian-stretch-sid

bzrlib.plugins.loom.tests.test_branch.TestFormat.test_disk_formatbzrlib.plugins.loom.tests.test_branch.TestFormat.test_disk_formatbzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_as_branchbzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_as_branchbzrlib.plugins.loom.tests.test_branch.TestLoom.test_clone_empty_loombzrlib.plugins.loom.tests.test_branch.TestLoom.test_clone_empty_loombzrlib.plugins.loom.tests.test_branch.TestLoom.test_clone_nonempty_loom_bottombzrlib.plugins.loom.tests.test_branch.TestLoom.test_clone_nonempty_loom_bottombzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_as_treebzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_as_treebzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_initialbzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_initialbzrlib.plugins.loom.tests.test_branch.TestLoom.test_clone_nonempty_loom_topbzrlib.plugins.loom.tests.test_branch.TestLoom.test_clone_nonempty_loom_topbzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_root_transportbzrlib.plugins.loom.tests.test_branch.TestLoom.test_export_loom_root_transportbroken-runnerbroken-runnerException
 in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/dist-packages/testtools/testsuite.py", line 112, in 
_run_test
case.run(process_result)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 780, in 
run
outcome(self, details=self._details)
  File "/usr/lib/python2.7/dist-packages/testtools/testresult/real.py", line 
1133, in addError
return self.decorated.addError(test, err)
  File "/usr/lib/python2.7/dist-packages/testtools/testresult/real.py", line 
1008, in addError
test, err, details=details)
  File "/usr/lib/python2.7/dist-packages/testtools/testresult/real.py", line 
999, in _add_result_with_semaphore
method(test, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/testtools/testresult/real.py", line 
1133, in addError
return self.decorated.addError(test, err)
  File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 451, 
in addError
self.report_error(test, err)
  File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 719, 
in report_error
% (self._testTimeString(test),
  File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 372, 
in _testTimeString
return self._elapsedTestTimeString()
  File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 365, 
in _elapsedTestTimeString
self._now() - self._start_datetime))
TypeError: _delta_to_float() takes exactly 3 arguments (2 given)

...

--
Ran 32 tests in 2.669s

FAILED (errors=16)
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/bzr-loom-2.2.0'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/bzr-loom.html

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

Bug#795104: Fwd: Bug#795104: Fwd: Re: Processed: found 795104 in 7.21-1

[Dirk Hünniger]

Hi Iain,
as I can see from mediawiki2latex_7.21-1.debian.tar.xz in sid the 
patches still seem to be there. So I don't understand why your change 
did not make it into 7.21.

Yours Dirk

On 17.10.2015 22:36, Iain Lane wrote:

On Sat, Oct 17, 2015 at 03:01:01PM +0200, Dirk Hünniger wrote:

Hi Iain,
since you resolved the issue in mediawiki2latex 7.20. Can you give me some
more info on how I can resolve the issue with mediawiki2latex 7.21 and ghc
7.8 on power pc. If it can be solved by changing the makefile, just send me
the new makefile and I will publish a new version of mediawiki2latex with
your makefile.
Yours Dirk

You reverted my change with the latest upload, so it is broken once
again. You should fetch the diff of my NMU and reapply it, and keep it
around until we have ghc 7.10 in unstable. There's no real need to fix
it outside of packaging, as we are working around a ghc bug here.

Bug#802184: marked as done (installation-reports: systemd refuses to boot (/etc/mtab vs. /proc/self/mounts))

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 09:49:38 +
with message-id 
and subject line Bug#802184: fixed in finish-install 2.58
has caused the Debian Bug report #802184,
regarding installation-reports: systemd refuses to boot (/etc/mtab vs. 
/proc/self/mounts)
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.)


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

Boot method: VMware Workstation 12 Player
Image version: http://www.debian.org/devel/debian-installer/
Date: 2015-10-18 13:27

Machine: Generic amd64
Processor:AMD Phenom II
Memory:2G
Partitions: installer default

Output of lspci -knn (or lspci -nn): cannot perform, see comments

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

On the first run systemd freezes execution. Exact wording:
[5.942102] systemd[1]: /etc/mtab is not a symlink or not
pointing to /proc/self/mounts. This is not supported anymore.
Please replace /etc/mtab with a symlink to /proc/self/mounts.

[5.943702] systemd[1]: Freezing execution.
--- End Message ---
--- Begin Message ---
Source: finish-install
Source-Version: 2.58

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

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated finish-install 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: Sun, 18 Oct 2015 10:07:53 +0200
Source: finish-install
Binary: finish-install
Architecture: source
Version: 2.58
Distribution: unstable
Urgency: high
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 finish-install - Finish the installation and reboot (udeb)
Closes: 802184 802187
Changes:
 finish-install (2.58) unstable; urgency=high
 .
   [ Steve McIntyre ]
   * finish-install.d/70mtab: Make sure /etc/mtab is a symlink to 
/proc/self/mounts
 (Closes: #802184, #802187; See: #801961).
Checksums-Sha1:
 2d55eac3118f363b4014de8b14dc6dbdfc973600 1622 finish-install_2.58.dsc
 127f9f7d9e2f79d681bb2b9c5d87334b3a6e0993 53808 finish-install_2.58.tar.xz
Checksums-Sha256:
 385224bbf814ce91895326da6817632d12eb5fbe92340a21ef8fea3be2477388 1622 
finish-install_2.58.dsc
 4345aadcfd1c281d29446f0af0183bd5f2ef76471ca1fc4c2c442a567612c1cc 53808 
finish-install_2.58.tar.xz
Files:
 a3b371f573d80787223f401007987f2e 1622 debian-installer required 
finish-install_2.58.dsc
 28fd8643134511f740a042e19687fbed 53808 debian-installer required 
finish-install_2.58.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWI1dVAAoJEP+RSvDCs1UgL9sQALoxWnudnbe6MiPC7cF6gqzh
QVgJN9sEV6cSS6vThIIha8L3uwG3cBoZIkCTQ4M/qtyVcgkqsaTF3Rymazzw1W49
k9YLZa1ZGH8ja6zAECGeUPTuigBncdREJcLj8b2QXV+h8eZ1qDPA/D/+uiVazBGl
pbBmBrSpF/PwWDkkgBhSLY4EbTrWqvqgVqMLnfkbOC/8RxpWaUKsDUVre6gi9dHC
poZk73WxOGr1poIhM1qW91lVf02KJ25FOUbTN8V0DhYWiqHhajW5UB+6XizLj1la
/9JE8b6lMpWRWHKEttjFZdycnyjBedu2lO+lKMW5wpmj+zXdOvRIGbj7sWyKInfF
yCys9e/ubQLMT5UbVZ6FmM/kkc4L8FVKgXVoN/U+KKONKkF+n7bgBxq6NYXcNmaI
GlOjBtZ3GZdBBnI/HuzbaostjyU+6LJEQ6744zFLX9Q4sIwfYgb4oN4/2aOzGe/o
52JC3X9Ot+wEQw9sZslB44nuWhVe6aF3oiImwyy9vHqPF6CQrzrdcAXB5k+Hn/+b
2tAgTROr4AGKfU4SwbBw/ijxFYslGvI2+BdyVD6DKpBswIMTsDUliygzBf5XGjN4
LLMn/0HhUJG3RCSmA5ggumiDFWq7qzEy9N2CAzHQHlaU8sV1HqgZKK9e2OI9J0hK
D2BR7UO7DUl3ofJ6CeBl
=xx8+
-END PGP SIGNATURE End Message ---

Bug#802187: marked as done (debian-installer: On first boot after install init hangs due to missing symlink "/etc/mtab to /proc/self/mounts")

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 09:49:38 +
with message-id 
and subject line Bug#802187: fixed in finish-install 2.58
has caused the Debian Bug report #802187,
regarding debian-installer: On first boot after install init hangs due to 
missing symlink "/etc/mtab to /proc/self/mounts"
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.)


-- 
802187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: Debian GNU/Linux testing "Stretch" - Official Snapshot amd64
CD Binary-1 20151012-12:17
Severity: important
Tags: d-i

Dear Maintainer,

On first boot after install init hangs due to missing symlink

[ 4.904755] systemd [1]: /etc/mtab is not a symlink or not pointing to
/proc/self/mounts. This is not supported anymore. Please replace
/etc/mtab with a symlink to /proc/self/mounts.
[ 4.904755] systemd [1]: Freezing execution.

Was able to get the system working by booting into rescue mode from the
install CD, 
mounting the root partion, 
moving the current /etc/mtab to /etc/mtab.old and then making the
symlink ln -s /proc/self/mounts /etc/mtab

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: finish-install
Source-Version: 2.58

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

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated finish-install 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: Sun, 18 Oct 2015 10:07:53 +0200
Source: finish-install
Binary: finish-install
Architecture: source
Version: 2.58
Distribution: unstable
Urgency: high
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 finish-install - Finish the installation and reboot (udeb)
Closes: 802184 802187
Changes:
 finish-install (2.58) unstable; urgency=high
 .
   [ Steve McIntyre ]
   * finish-install.d/70mtab: Make sure /etc/mtab is a symlink to 
/proc/self/mounts
 (Closes: #802184, #802187; See: #801961).
Checksums-Sha1:
 2d55eac3118f363b4014de8b14dc6dbdfc973600 1622 finish-install_2.58.dsc
 127f9f7d9e2f79d681bb2b9c5d87334b3a6e0993 53808 finish-install_2.58.tar.xz
Checksums-Sha256:
 385224bbf814ce91895326da6817632d12eb5fbe92340a21ef8fea3be2477388 1622 
finish-install_2.58.dsc
 4345aadcfd1c281d29446f0af0183bd5f2ef76471ca1fc4c2c442a567612c1cc 53808 
finish-install_2.58.tar.xz
Files:
 a3b371f573d80787223f401007987f2e 1622 debian-installer required 
finish-install_2.58.dsc
 28fd8643134511f740a042e19687fbed 53808 debian-installer required 
finish-install_2.58.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWI1dVAAoJEP+RSvDCs1UgL9sQALoxWnudnbe6MiPC7cF6gqzh
QVgJN9sEV6cSS6vThIIha8L3uwG3cBoZIkCTQ4M/qtyVcgkqsaTF3Rymazzw1W49
k9YLZa1ZGH8ja6zAECGeUPTuigBncdREJcLj8b2QXV+h8eZ1qDPA/D/+uiVazBGl
pbBmBrSpF/PwWDkkgBhSLY4EbTrWqvqgVqMLnfkbOC/8RxpWaUKsDUVre6gi9dHC
poZk73WxOGr1poIhM1qW91lVf02KJ25FOUbTN8V0DhYWiqHhajW5UB+6XizLj1la
/9JE8b6lMpWRWHKEttjFZdycnyjBedu2lO+lKMW5wpmj+zXdOvRIGbj7sWyKInfF
yCys9e/ubQLMT5UbVZ6FmM/kkc4L8FVKgXVoN/U+KKONKkF+n7bgBxq6NYXcNmaI
GlOjBtZ3GZdBBnI/HuzbaostjyU+6LJEQ6744zFLX9Q4sIwfYgb4oN4/2aOzGe/o
52JC3X9Ot+wEQw9sZslB44nuWhVe6aF3oiImwyy9vHqPF6CQrzrdcAXB5k+Hn/+b
2tAgTROr4AGKfU4SwbBw/ijxFYslGvI2+BdyVD6DKpBswIMTsDUliygzBf5XGjN4
LLMn/0HhUJG3RCSmA5ggumiDFWq7qzEy9N2CAzHQHlaU8sV1HqgZKK9e2OI9J0hK
D2BR7UO7DUl3ofJ6CeBl
=xx8+
-END PGP SIGNATURE End Message ---

Bug#802076: marked as done (hhsuite: FTBFS: /usr/include/ffindex.h:128:34: fatal error: ffindex_posix_search.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 06:18:43 +
with message-id 
and subject line Bug#802076: fixed in hhsuite 2.0.16-6
has caused the Debian Bug report #802076,
regarding hhsuite: FTBFS: /usr/include/ffindex.h:128:34: fatal error: 
ffindex_posix_search.h: No such file or directory
to be marked as done.

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

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


-- 
802076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hhsuite
Version: 2.0.16-5
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from hhblits.C:119:0:
/usr/include/ffindex.h:128:34: fatal error: ffindex_posix_search.h: No such 
file or directory
compilation terminated.
Makefile:95: recipe for target 'hhblits' failed
make[3]: *** [hhblits] Error 1

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/hhsuite.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: hhsuite
Source-Version: 2.0.16-6

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated hhsuite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Oct 2015 07:53:08 +0200
Source: hhsuite
Binary: hhsuite hhsuite-doc hhsuite-data hhsuite-dbg
Architecture: source all amd64
Version: 2.0.16-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 hhsuite- sensitive protein sequence searching based on HMM-HMM alignment
 hhsuite-data - sensitive protein sequence searching based on HMM-HMM alignment 
(
 hhsuite-dbg - sensitive protein sequence searching based on HMM-HMM alignment (
 hhsuite-doc - documentation for HHsuite for HMM-HMM comparisons
Closes: 802076
Changes:
 hhsuite (2.0.16-6) unstable; urgency=medium
 .
   * Versioned Build-Depends ffindex0-dev (>= 0.9.9.6-2)
 Closes: #802076
Checksums-Sha1:
 71ebbdc6ff8daffe037f7164985bf0f559149fb3 2205 hhsuite_2.0.16-6.dsc
 fd036e4d26cc50bebd351a723ed17ca4e75fda5c 10028 hhsuite_2.0.16-6.debian.tar.xz
 9896189fd91d755dfd5d96fb2a4b0897805720b2 2157170 hhsuite-data_2.0.16-6_all.deb
 99c45f110dd732dbc2bfe7ed90db42fb2f2ab61a 3645376 hhsuite-dbg_2.0.16-6_amd64.deb
 0ccaccffbc9588e527b83a2f5cfab7b099e9f5fb 329628 hhsuite-doc_2.0.16-6_all.deb
 0fa356f2788e313d023def2807316748b631f810 738042 hhsuite_2.0.16-6_amd64.deb
Checksums-Sha256:
 fbdbf151490a89643c3dd24dcbd62e0a3ae7893927eb9166a2b96cf5d36c101d 2205 
hhsuite_2.0.16-6.dsc
 b9381c81162291a90d08fab216fa5d8677a65e7c8e7e92b1bf74bf70f71cf171 10028 
hhsuite_2.0.16-6.debian.tar.xz
 d17aa77bedfba5d4c5bf3ffb6819b0f0d7eb97d3cfd6046e95cfde10bc530877 2157170 
hhsuite-data_2.0.16-6_all.deb
 d2470cc84989ed8d9395d8337b7e90483b0888ad97e12dad7f0e5f6184b073ed 3645376 
hhsuite-dbg_2.0.16-6_amd64.deb
 5e2e0d845a6a20268645c45b7a019645cfa31ed35c4f6fdc2b06ec88bed8183e 329628 
hhsuite-doc_2.0.16-6_all.deb
 f2cbe46948eda4c7e90f288d648e2c550a4e9cba7c136df598f674acfdcc263a 738042 
hhsuite_2.0.16-6_amd64.deb
Files:
 76d2a98c2b65fe33125eb857f031c3c9 2205 science optional hhsuite_2.0.16-6.dsc
 59ff5b945e030de36e5ca6b25f3609f2 10028 science optional 
hhsuite_2.0.16-6.debian.tar.xz
 1bf98aa9acb0fcded80d1ddfb086a340 2157170 science optional 
hhsuite-data_2.0.16-6_all.deb
 c10b4e854b1a9f94b2994b266956068e 3645376 debug extra 
hhsuite-dbg_2.0.16-6_amd64.deb
 efc0217d9cc1e90af8f59b05138dfd85 329628 doc optional 
hhsuite-doc_2.0.16-6_all.deb
 d17c6f3b0838fc228fddaa45f8b351bd 738042 science optional 
hhsuite_2.0.16-6_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#802188: bochs: Support building under Linux 4.x

[Chris Lamb]

Package: bochs
Version: 2.6-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
Tags: patch

Hi,

The configure script checks `uname -r` and checks for 2.6 or 3.x, etc.,
rejecting any others. but the latest kernel version at the time of
writing is 4.2.3. Severity serious as this therefore will FTBFS under
your typical developer system running sid.

A patch is attached that reverses this logic, rejecting 2.2 and
essentially allowing anything 2.6+.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/configure.in b/configure.in
index f6f1513..aadb82b 100644
--- a/configure.in
+++ b/configure.in
@@ -713,17 +713,17 @@ AC_ARG_ENABLE(pcidev,
   AC_MSG_NOTICE([Linux detected as host for PCI host device mapping])
   linux_version=`uname -r`
  case "$linux_version" in
+   2.2*)
+   AC_MSG_ERROR([Linux kernel 2.4, 2.6 or 3.x is required 
for PCI host device mapping])
+   ;;
2.4*)
PCIDEV_MODULE_MAKE_ALL="all-kernel24"
KERNEL_MODULE_SUFFIX="o"
;;
-   2.6*|3.*)
+   *)
PCIDEV_MODULE_MAKE_ALL="all-kernel26"
KERNEL_MODULE_SUFFIX="ko"
;;
-   *)
-   AC_MSG_ERROR([Linux kernel 2.4, 2.6 or 3.x is required 
for PCI host device mapping])
-   ;;
  esac
  KERNELDIR="/lib/modules/$linux_version/build"
  LSMOD="lsmod"

Bug#802191: bats: FTBFS: not ok 7 summary passing tests

[Chris West (Faux)]

Source: bats
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[1]: Entering directory '/bats-0.4.0'
bin/bats --tap test
1..43
ok 1 no arguments prints usage instructions
ok 2 -v and --version print version number
ok 3 -h and --help print help
ok 4 invalid filename prints an error
ok 5 empty test file runs zero tests
ok 6 one passing test
not ok 7 summary passing tests
# (in test file test/bats.bats, line 46)
#   `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
not ok 8 summary passing and skipping tests
# (in test file test/bats.bats, line 52)
#   `[ "${lines[2]}" = "2 tests, 0 failures, 1 skipped" ]' failed
not ok 9 summary passing and failing tests
# (in test file test/bats.bats, line 58)
#   `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
not ok 10 summary passing, failing and skipping tests
# (in test file test/bats.bats, line 64)
#   `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
ok 11 one failing test
ok 12 one failing and one passing test



debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/bats-0.4.0'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/bats.html

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

Processed: Re: Bug#802184: Installation-reports

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 installation-reports: systemd refuses to boot (/etc/mtab vs. 
> /proc/self/mounts)
Bug #802184 [installation-reports] Installation-reports
Changed Bug title to 'installation-reports: systemd refuses to boot (/etc/mtab 
vs. /proc/self/mounts)' from 'Installation-reports'
> reassign -1 finish-install
Bug #802184 [installation-reports] installation-reports: systemd refuses to 
boot (/etc/mtab vs. /proc/self/mounts)
Bug reassigned from package 'installation-reports' to 'finish-install'.
Ignoring request to alter found versions of bug #802184 to the same values 
previously set
Ignoring request to alter fixed versions of bug #802184 to the same values 
previously set
> severity -1 serious
Bug #802184 [finish-install] installation-reports: systemd refuses to boot 
(/etc/mtab vs. /proc/self/mounts)
Severity set to 'serious' from 'normal'
> tag -1 - d-i
Bug #802184 [finish-install] installation-reports: systemd refuses to boot 
(/etc/mtab vs. /proc/self/mounts)
Ignoring request to alter tags of bug #802184 to the same tags previously set
> affects -1 installation-reports
Bug #802184 [finish-install] installation-reports: systemd refuses to boot 
(/etc/mtab vs. /proc/self/mounts)
Added indication that 802184 affects installation-reports

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

Processed: Bug#802158 marked as pending

[Debian Bug Tracking System]

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

> tag 802158 pending
Bug #802158 [src:python-spur] python-spur: FTBFS: ImportError: No module named 
'paramiko'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802158: marked as pending

[Ruben Undheim]

tag 802158 pending
thanks

Hello,

Bug #802158 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-spur.git;a=commitdiff;h=d6576f0

---
commit d6576f0b1ecf675702d7291d7ad4e241de787262
Author: Ruben Undheim 
Date:   Sun Oct 18 10:30:27 2015 +0200

Fix FTBFS

diff --git a/debian/changelog b/debian/changelog
index e76897f..2d544b9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-spur (0.3.14-2) unstable; urgency=medium
+
+  * debian/control: add python-paramiko and python3-paramiko to
+build-depenedencies
+- Fixes FTBFS (test suite problem) (Closes: #802158)
+
+ -- Ruben Undheim   Sun, 18 Oct 2015 10:27:41 +0200
+
 python-spur (0.3.14-1) unstable; urgency=low
 
   * Initial release (Closes: #784026)

Processed: Re: Bug#802187: debian-installer: On first boot after install init hangs due to missing symlink "/etc/mtab to /proc/self/mounts"

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 finish-install
Bug #802187 [debian-installer] debian-installer: On first boot after install 
init hangs due to missing symlink "/etc/mtab to /proc/self/mounts"
Bug reassigned from package 'debian-installer' to 'finish-install'.
Ignoring request to alter found versions of bug #802187 to the same values 
previously set
Ignoring request to alter fixed versions of bug #802187 to the same values 
previously set
> severity -1 serious
Bug #802187 [finish-install] debian-installer: On first boot after install init 
hangs due to missing symlink "/etc/mtab to /proc/self/mounts"
Severity set to 'serious' from 'normal'
> tag -1 - d-i
Bug #802187 [finish-install] debian-installer: On first boot after install init 
hangs due to missing symlink "/etc/mtab to /proc/self/mounts"
Ignoring request to alter tags of bug #802187 to the same tags previously set
> affects -1 debian-installer
Bug #802187 [finish-install] debian-installer: On first boot after install init 
hangs due to missing symlink "/etc/mtab to /proc/self/mounts"
Added indication that 802187 affects debian-installer

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

Bug#802192: gabedit: FTBFS: recipe for target 'override_dh_compress' failed

[Chris West (Faux)]

Source: gabedit
Version: 2.4.8-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

   debian/rules override_dh_compress
make[1]: Entering directory '/gabedit-2.4.8'
dh_compress 
/gabedit-2.4.8/debian/gabedit/usr/share/doc/gabedit/examples/exampleGeoConv.gab
gzip: . is a directory -- ignored
dh_compress: gzip -9nf . usr/share/doc/gabedit/changelog 
usr/share/doc/gabedit/changelog.Debian 
usr/share/doc/gabedit/examples/exampleCartezian.gab 
usr/share/doc/gabedit/examples/exampleSpheric.gab 
usr/share/doc/gabedit/examples/gtkrc usr/share/man/man1/gabedit.1 returned exit 
code 2
debian/rules:61: recipe for target 'override_dh_compress' failed
make[1]: *** [override_dh_compress] Error 2
make[1]: Leaving directory '/gabedit-2.4.8'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/gabedit.html

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

Bug#801844: [systemd] Sudden Unbootable System

[David Baron]

Spontaneously gave it a try today and ... it 
booted successfully!

Did have an "invalid mount point" error up 
front but does not show on journalctl or 
dmesg.

Bug#802025: /etc/mtab is not a symlink or not pointing to /proc/self/mounts

[Martin Pitt]

Hello Steve,

Steve McIntyre [2015-10-17 21:31 +0100]:
> On Sat, Oct 17, 2015 at 09:12:27PM +0200, Michael Biebl wrote:
> >Am 17.10.2015 um 17:46 schrieb Michael Biebl:
> >> Am 17.10.2015 um 00:53 schrieb Ilya Sukhanov:
> >>> Package: systemd
> >>> Version: 227-2
> >>> Severity: grave
> >>>
> >>> System freezes at boot with "/etc/mtab is not a symlink or not pointing
> >>> to /proc/self/mounts..."
> >>>
> >>> To reproduce install debian from stretch_di_alpha3 amd64 image (used
> >
> >> Sounds like a bug in debian-installer. It shouldn't setup /etc/mtab as
> >> real file.

Indeed. So having a hard failure about it was at least useful for
something..

> I've just committed a fix for that in d-i.

Thanks!

> >Martin, I guess there is some value in keeping that hard freeze for now,
> >which should help us identify such faulty software.
> >
> >I wouldn't release stretch with that behaviour, but having it in
> >stretch/sid for a while is probably ok.

Yes, agreed. Otherwise we'll still fight this in the next two
releases.

> Right now, it's going to stop people from being able to install
> stretch at all. Please take out this retarded mis-feature. By all
> means, complain and warn about the problem, but hanging hard is just
> not helpful for our users here.

The plan is indeed to stop that freeze, see the upstream bug. We'll do
that with util-linux 2.27.1 which stops looking at /etc/mtab. So this
won't go into Stretch.

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

[Sebastiaan Couwenberg]

Hi Felix,

I missed this update to the bugreport.

On Fri, 16 Oct 2015 20:49:12 +0200 Felix Natter wrote:
> I added a patch for JMapViewer-1.11 compatibility:
>   http://anonscm.debian.org/cgit/pkg-java/freeplane.git
> 
> I've set the distribution to experimental since it should probably be
> uploaded to unstable together with jmapviewer (now that it _requires_
> jmapviewer>=1.11).
> 
> @Tony: Would you be willing to sponsor this and/or shall I submit an RFS
> for this?

Since my upload of jmapviewer now causes freeplane to FTBFS, I'm willing
to sponsor the upload of freeplane too.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#802030: [Debichem-devel] Bug#802030: psi4 FTBFS on mips, testsuite timeout

[Michael Banck]

Hi,

On Sun, Oct 18, 2015 at 12:44:42PM +0100, peter green wrote:
> On 18/10/15 11:38, Michael Banck wrote:
> >I don't think it's a problem with psi4 (so I am closing this bug for
> >now),
> Note that this needs to be dealt with one way or another before your
> package can migrate to testing.

Sure.  I'll have the mips binary removed if I don't hear back from the
mips porters (assuming you are not talking for the mips port per se?).
 
> >So I see three alternatives:
> >
> >1. Reschedule on a different, presumably more powerful, buildd, if one
> >exists (I don't think so?)
> >
> >2. Crank up the testsuite timeout to 2000 minutes or so
> >
> >3. Add it to not-for-us on mips, or otherwise blacklist it, and remove
> >the .deb (which built by accident on lucatelli when the testsuite was
> >not exercised)
> >
> 4. disable the testsuite when building on mips
 
I'd prefer a solution that does not need touching the source package
again once (hopefully soon) FPU-enabled mips autobuilders start
operating. 

But I'm happy to take patches to that end for the time being.

Also, I appreciate the test coverage on mips, so would not want to have
it disabled unless it is absolutely necesary, even if it is unlikely
somebody would want to run psi4 on mips anytime soon.


Michael

Bug#802120: marked as pending

[W . Martin Borgert]

tag 802120 pending
thanks

Hello,

Bug #802120 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-mpld3.git;a=commitdiff;h=573b3e4

---
commit 573b3e463222a0b521d324776b53c9e56291e131
Author: W. Martin Borgert 
Date:   Sun Oct 18 12:29:49 2015 +

fix build-deps

diff --git a/debian/changelog b/debian/changelog
index 466eb0d..9f3b82d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-mpld3 (0.3git+20140910dfsg-3) unstable; urgency=medium
+
+  * Fix b-d on matplotlib and jinja2 (Closes: #802120) Thanks Chris West!
+
+ -- W. Martin Borgert   Sun, 18 Oct 2015 12:25:43 +
+
 python-mpld3 (0.3git+20140910dfsg-2) unstable; urgency=low
 
   * Added the missing link(s) to d3.js (Closes: #770759)

Bug#802213: node-postgres: FTBFS: error: expected class-name before '{' token

[Chris Lamb]

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

Dear Maintainer,

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

  [..]

  gyp info spawn make
  make[1]: Entering directory '/tmp/buildd/node-postgres-0.13.3/build'
  gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
g++ '-DNODE_GYP_MODULE_NAME=binding' '-D_LARGEFILE_SOURCE'
'-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION'
-I/usr/include/nodejs/include/node -I/usr/include/nodejs/src
-I/usr/include/nodejs/deps/uv/include
-I/usr/include/nodejs/deps/v8/include -I/usr/include/postgresql 
-fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3
-ffunction-sections -fdata-sections -fno-omit-frame-pointer
-fno-rtti -fno-exceptions -std=gnu++0x -MMD -MF
./Release/.deps/Release/obj.target/binding/src/binding.o.d.raw -g
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o
Release/obj.target/binding/src/binding.o ../src/binding.cc
  ../src/binding.cc:36:38: error: expected class-name before '{' token
   class Connection : public ObjectWrap {
^
  ../src/binding.cc:84:12: error: 'uv_poll_t' has not been declared
 io_event(uv_poll_t* w, int status, int revents)
  ^
  ../src/binding.cc:100:17: error: 'Arguments' does not name a type
 Connect(const Arguments& args)
   ^
  ../src/binding.cc:120:16: error: 'Arguments' does not name a type
 Cancel(const Arguments& args)
  ^
  ../src/binding.cc:136:19: error: 'Arguments' does not name a type
 SendQuery(const Arguments& args)
 ^
  ../src/binding.cc:159:29: error: 'Arguments' does not name a type
 SendQueryWithParams(const Arguments& args)
   ^
  ../src/binding.cc:168:21: error: 'Arguments' does not name a type
 SendPrepare(const Arguments& args)
   ^
  ../src/binding.cc:183:27: error: 'Arguments' does not name a type
 SendQueryPrepared(const Arguments& args)
 ^
  ../src/binding.cc:191:36: error: 'Arguments' does not name a type
 DispatchParameterizedQuery(const Arguments& args, bool isPrepared)
  ^
  ../src/binding.cc:235:13: error: 'Arguments' does not name a type
 End(const Arguments& args)
   ^
  ../src/binding.cc:245:3: error: 'uv_poll_t' does not name a type
 uv_poll_t read_watcher_;
 ^
  ../src/binding.cc:246:3: error: 'uv_poll_t' does not name a type
 uv_poll_t  write_watcher_;
 ^
  ../src/binding.cc:269:27: error: 'Arguments' does not name a type
 SendCopyFromChunk(const Arguments& args) {
 ^
  ../src/binding.cc:280:21: error: 'Arguments' does not name a type
 EndCopyFrom(const Arguments& args) {
   ^
  ../src/binding.cc:296:14: error: 'Arguments' does not name a type
 New (const Arguments& args)
^
  In file included from /usr/include/nodejs/src/node.h:42:0,
   from ../src/binding.cc:2:
  /usr/include/nodejs/deps/v8/include/v8.h: In static member function
  'static void Connection::Init(v8::Handle)':
  /usr/include/nodejs/deps/v8/include/v8.h:885:13: error:
  'v8::HandleScope::HandleScope()' is protected
 V8_INLINE HandleScope() {}

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/node-postgres_0.13.3-1.build1.log.gz


Regards,

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


node-postgres.0.13.3-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#802149: marked as pending

[W . Martin Borgert]

tag 802149 pending
thanks

Hello,

Bug #802149 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-mplexporter.git;a=commitdiff;h=db60571

---
commit db60571aa18a1f0fb9cc2f7dddf51e611c61bb7b
Author: W. Martin Borgert 
Date:   Sun Oct 18 15:37:43 2015 +0200

fix build-deps on numpy and matplotlib

diff --git a/debian/changelog b/debian/changelog
index 3e0aa9b..c2d4ea2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-mplexporter (0.0.1+20140921-2) unstable; urgency=medium
+
+  * fix b-d on numpy/matplotlib (Closes: #802149) Thanks Chris West!
+
+ -- W. Martin Borgert   Sun, 18 Oct 2015 13:35:57 +
+
 python-mplexporter (0.0.1+20140921-1) unstable; urgency=low
 
   * Initial release (Closes: #762629)

Bug#802208: jq: FTBFS on mips*: tests fail

[Jakub Wilk]

Source: jq
Version: 1.5+dfsg-1
Severity: serious
Justification: fails to build from source
User: debian-m...@lists.debian.org
Usertags: mips

jq FTBFS on mips*:
|dh_auto_test
| make -j1 check
| make[1]: Entering directory '/home/jwilk/jq-1.5+dfsg'
| make  check-am
| make[2]: Entering directory '/home/jwilk/jq-1.5+dfsg'
| make  check-TESTS
| make[3]: Entering directory '/home/jwilk/jq-1.5+dfsg'
| make[4]: Entering directory '/home/jwilk/jq-1.5+dfsg'
| FAIL: tests/mantest
| FAIL: tests/jqtest
| FAIL: tests/onigtest
| FAIL: tests/shtest
| 
| Testsuite summary for jq 1.5-1-a5b5cbe
| 
| # TOTAL: 4
| # PASS:  0
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  4
| # XPASS: 0
| # ERROR: 0
| 
| See ./test-suite.log
| Please report to https://github.com/stedolan/jq/issues

The attached test-suite.log is from a mips build.
Presumably it's the same on mipsel, but I didn't check.

Full build logs:
https://buildd.debian.org/status/fetch.php?pkg=jq=mips=1.5%2Bdfsg-1=1444735454
https://buildd.debian.org/status/fetch.php?pkg=jq=mipsel=1.5%2Bdfsg-1=1444639924

--
Jakub Wilk

   jq 1.5-1-a5b5cbe: ./test-suite.log


# TOTAL: 4
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  4
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/mantest
===

Segmentation fault
rake aborted!
Errno::EPIPE: Broken pipe @ io_write - 
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:50:in `write'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:50:in `puts'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:50:in `puts'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:50:in `block (5 levels) in '
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:50:in `each'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:50:in `block (4 levels) in '
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:47:in `each'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:47:in `block (3 levels) in '
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:46:in `each'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:46:in `block (2 levels) in '
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:45:in `each'
/home/jwilk/jq-1.5+dfsg/docs/Rakefile:45:in `block in '
Tasks: TOP => mantests
(See full trace by running task with --trace)
FAIL tests/mantest (exit status: 139)

FAIL: tests/jqtest
==

Segmentation fault
FAIL tests/jqtest (exit status: 139)

FAIL: tests/onigtest


Segmentation fault
FAIL tests/onigtest (exit status: 139)

FAIL: tests/shtest
==

jq: jv.c:435: jvp_string_ptr: Assertion `jv_get_kind(a) == JV_KIND_STRING' 
failed.
Aborted
FAIL tests/shtest (exit status: 134)

Processed: freeplane: Fails to build with JMapViewer 1.11

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #801475 [src:freeplane] freeplane: Fails to build with JMapViewer 1.11
Severity set to 'serious' from 'important'

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 802208 https://github.com/stedolan/jq/issues/994
Bug #802208 [src:jq] jq: FTBFS on mips*: tests fail
Set Bug forwarded-to-address to 'https://github.com/stedolan/jq/issues/994'.
> thanks
Stopping processing here.

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

Processed: Bug#802120 marked as pending

[Debian Bug Tracking System]

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

> tag 802120 pending
Bug #802120 [src:python-mpld3] python-mpld3: FTBFS: ImportError: No module 
named 'matplotlib'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802120: marked as done (python-mpld3: FTBFS: ImportError: No module named 'matplotlib')

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 13:19:54 +
with message-id 
and subject line Bug#802120: fixed in python-mpld3 0.3git+20140910dfsg-3
has caused the Debian Bug report #802120,
regarding python-mpld3: FTBFS: ImportError: No module named 'matplotlib'
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.)


-- 
802120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mpld3
Version: 0.3git+20140910dfsg-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

OK
I: pybuild base:170: cd 
/python-mpld3-0.3git+20140910dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
unittest discover -v 
mpld3 (unittest.loader._FailedTest) ... ERROR

==
ERROR: mpld3 (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: mpld3
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/python-mpld3-0.3git+20140910dfsg/.pybuild/pythonX.Y_3.5/build/mpld3/__init__.py",
 line 41, in 
from . import plugins
  File 
"/python-mpld3-0.3git+20140910dfsg/.pybuild/pythonX.Y_3.5/build/mpld3/plugins.py",
 line 18, in 
import matplotlib
ImportError: No module named 'matplotlib'


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/python-mpld3-0.3git+20140910dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
unittest discover -v 

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-mpld3.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-mpld3
Source-Version: 0.3git+20140910dfsg-3

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated python-mpld3 
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: Sun, 18 Oct 2015 12:25:43 +
Source: python-mpld3
Binary: python-mpld3 python3-mpld3
Architecture: source all
Version: 0.3git+20140910dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-mpld3 - D3 viewer for matplotlib
 python3-mpld3 - D3 viewer for matplotlib
Closes: 802120
Changes:
 python-mpld3 (0.3git+20140910dfsg-3) unstable; urgency=medium
 .
   * Fix b-d on matplotlib and jinja2 (Closes: #802120) Thanks Chris West!
Checksums-Sha1:
 c291bc4ddf69a13bb9b333f296937d849e7d526b 2340 
python-mpld3_0.3git+20140910dfsg-3.dsc
 c389d53b5838e19ea0a741a0bdf4caf33bd9824e 4220 
python-mpld3_0.3git+20140910dfsg-3.debian.tar.xz
 2c4c49e002464cc2a1155b8b24f1dbe82d4fbe0d 679556 
python-mpld3_0.3git+20140910dfsg-3_all.deb
 483eadb02ace3624a98cd53773a48132153fc2eb 679644 
python3-mpld3_0.3git+20140910dfsg-3_all.deb
Checksums-Sha256:
 974976c46e1d3246490a2beea976c3b5b914b961e8b7f751eb9471f23327b818 2340 
python-mpld3_0.3git+20140910dfsg-3.dsc
 eddd8f3ae8047b81be39c2ee95cd06d7f47388cae25ae4c43cc72169bc46af2d 4220 
python-mpld3_0.3git+20140910dfsg-3.debian.tar.xz
 a434ff6ffd1da6f0f31782ad458d73938523c8d636b5a4fd0afbd7abc1ab 679556 
python-mpld3_0.3git+20140910dfsg-3_all.deb
 f219241ed98172b69371de9b68af30d31bf0863513b00ced19d121a9cd77ae8a 679644 

Bug#802214: node-connect: FTBFS: Uncaught Error: getaddrinfo ENOTFOUND [::1] [::1]:50403

[Chris Lamb]

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

Dear Maintainer,

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

  [..]

 debian/rules override_dh_auto_test
  make[1]: Entering directory '/tmp/buildd/node-connect-3.3.0'
  mocha -C --require test/support/env --reporter spec --bail
  --check-leaks test/
  (node) child_process: options.customFds option is deprecated. Use
  options.stdio instead.
  
  
app.listen()
✓ should wrap in an http.Server (47ms)
  
app.use()
1) should not obscure FQDNs
  with a connect app
  
app.use()
  with a connect app
  with a node app
  error handling
  
app
  404 handler
  error handler
  
  
1 passing (78ms)
1 failing
  
1) app.use() should not obscure FQDNs:
   Uncaught Error: getaddrinfo ENOTFOUND [::1] [::1]:50403
at errnoException (dns.js:26:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)
  
  
  
  debian/rules:14: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/tmp/buildd/node-connect-3.3.0'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/node-connect_3.3.0-1.build1.log.gz


Regards,

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


node-connect.3.3.0-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#799948: 0.6.1 doesn't solves the problem

[Vladimir Stavrinov]

On Tue, Oct 06, 2015 at 07:38:23PM +0300, Vladimir Stavrinov wrote:

> The problem still exists. See

Again, with new version the problem don't solved as You reported.
With 0.6.91 and 340.93-5 GLX still doesn't works. See attached log.
It is not about kodi only. The problem exists for other software too:
GLX doesn't works. And as before to make it working all related
packages should be downgraded to 0.5.1 and 340.93-1 versions.

### Vladimir Stavrinov ###
## Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Sun Oct 18 12:27:57 MSK 2015
 Kodi Options: 
 Arch: x86_64
 Kernel: Linux 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14)
 Release: Debian GNU/Linux
## END SYSTEM INFO ##

### STACK TRACE #
=>  Core file: /home/vs/core (2015-10-18 12:27:57.398449307 +0300)
=
[New LWP 2592]
[New LWP 2600]
[New LWP 2602]
[New LWP 2601]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/kodi/kodi.bin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x in ?? ()
[Current thread is 1 (Thread 0x7ff3bdc2b980 (LWP 2592))]

Thread 4 (Thread 0x7ff3941db700 (LWP 2601)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:143
#1  0x7ff3b71a2e18 in pa_threaded_mainloop_wait () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x00999dac in CAESinkPULSE::AddPackets(unsigned char**, unsigned 
int, unsigned int) ()
#3  0x0097cf56 in 
ActiveAE::CActiveAESink::OutputSamples(ActiveAE::CSampleBuffer*) ()
#4  0x0097e122 in ActiveAE::CActiveAESink::StateMachine(int, 
Actor::Protocol*, Actor::Message*) ()
#5  0x0097eb57 in ActiveAE::CActiveAESink::Process() ()
#6  0x01146aff in CThread::Action() ()
#7  0x01146dc2 in CThread::staticThread(void*) ()
#8  0x7ff3bb5210a4 in start_thread (arg=0x7ff3941db700) at 
pthread_create.c:309
#9  0x7ff3b2e2306d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7ff3939da700 (LWP 2602)):
#0  0x7ff3b2e1a52d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff3b71a2831 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7ff3b7193e51 in pa_mainloop_poll () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7ff3b71944ee in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7ff3b71945a0 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7ff3b71a27c6 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7ff3ab331ff8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-7.0.so
#7  0x7ff3bb5210a4 in start_thread (arg=0x7ff3939da700) at 
pthread_create.c:309
#8  0x7ff3b2e2306d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7ff3901da700 (LWP 2600)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x0097afc7 in ActiveAE::CActiveAE::Process() ()
#2  0x01146aff in CThread::Action() ()
#3  0x01146dc2 in CThread::staticThread(void*) ()
#4  0x7ff3bb5210a4 in start_thread (arg=0x7ff3901da700) at 
pthread_create.c:309
#5  0x7ff3b2e2306d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ff3bdc2b980 (LWP 2592)):
#0  0x in ?? ()
#1  0x00746995 in CMediaSourceSettings::Clear() ()
#2  0x00c9dbb1 in CSettingsManager::OnSettingsUnloaded() ()
#3  0x00c9e843 in CSettingsManager::Unload() ()
#4  0x00ca1d9e in CSettingsManager::Clear() ()
#5  0x007312fd in CSettings::Uninitialize() ()
#6  0x0073175f in CSettings::~CSettings() ()
#7  0x7ff3b2d74bc9 in __run_exit_handlers (status=-1, listp=0x7ff3b30e05a8 
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#8  0x7ff3b2d74c15 in __GI_exit (status=) at exit.c:104
#9  0x7ff3b2d5eb4c in __libc_start_main (main=0x6ccd00 , argc=1, 
argv=0x7fffc9ed7e18, init=, fini=, 
rtld_fini=, stack_end=0x7fffc9ed7e08) at libc-start.c:321
#10 0x00716fc9 in _start ()
# END STACK TRACE ###

# LOG FILE ##

12:27:56 T:140684837435776  NOTICE: special://profile/ is mapped to: 
special://masterprofile/
12:27:56 T:140684837435776  NOTICE: 
---
12:27:56 T:140684837435776  NOTICE: Starting Kodi from Debian (15.2-RC3 Debian 
package version:15.2~rc3+dfsg1-1 Git: (unknown)). Platform: Linux x86 64-bit
12:27:56 T:140684837435776  NOTICE: Using Debug Kodi from Debian x64 build
12:27:56 T:140684837435776  NOTICE: Kodi from Debian compiled from 
15.2~rc3+dfsg1-1 by GCC 5.2.1 for 

Bug#802119: marked as pending

[W . Martin Borgert]

tag 802119 pending
thanks

Hello,

Bug #802119 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-diaspy.git;a=commitdiff;h=a5837f6

---
commit a5837f6e21fdd4fd8a1958b2509c15ec77a10089
Author: W. Martin Borgert 
Date:   Sun Oct 18 10:59:58 2015 +

fix build-dep on -requests

diff --git a/debian/changelog b/debian/changelog
index 434683f..6c93d32 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-diaspy (0.5.0.1-2) unstable; urgency=low
+
+  * Fix build-dep (Closes: #802119). Thanks Chris West!
+
+ -- W. Martin Borgert   Sun, 18 Oct 2015 10:13:44 +
+
 python-diaspy (0.5.0.1-1) unstable; urgency=low
 
   * Initial release (Closes: #794531).

Processed: Bug#802119 marked as pending

[Debian Bug Tracking System]

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

> tag 802119 pending
Bug #802119 [src:python-diaspy] python-diaspy: FTBFS: ImportError: No module 
named 'requests'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802119: marked as done (python-diaspy: FTBFS: ImportError: No module named 'requests')

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 11:33:46 +
with message-id 
and subject line Bug#802119: fixed in python-diaspy 0.5.0.1-2
has caused the Debian Bug report #802119,
regarding python-diaspy: FTBFS: ImportError: No module named 'requests'
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.)


-- 
802119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-diaspy
Version: 0.5.0.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:170: cd /python-diaspy-0.5.0.1/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m unittest discover -v 

--
Ran 0 tests in 0.000s

OK
I: pybuild base:170: cd /python-diaspy-0.5.0.1/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m unittest discover -v 
diaspy (unittest.loader._FailedTest) ... ERROR

==
ERROR: diaspy (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: diaspy
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/python-diaspy-0.5.0.1/.pybuild/pythonX.Y_3.5/build/diaspy/__init__.py", line 
3, in 
import diaspy.connection as connection
  File 
"/python-diaspy-0.5.0.1/.pybuild/pythonX.Y_3.5/build/diaspy/connection.py", 
line 11, in 
import requests
ImportError: No module named 'requests'


--
Ran 1 test in 0.000s


Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-diaspy.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-diaspy
Source-Version: 0.5.0.1-2

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated python-diaspy 
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: Sun, 18 Oct 2015 10:13:44 +
Source: python-diaspy
Binary: python-diaspy python3-diaspy python-diaspy-doc
Architecture: source all
Version: 0.5.0.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-diaspy - unofficial interface to the Diaspora social network (Python 2)
 python-diaspy-doc - unofficial interface to the Diaspora social network 
(documentatio
 python3-diaspy - unofficial interface to the Diaspora social network (Python 3)
Closes: 802119
Changes:
 python-diaspy (0.5.0.1-2) unstable; urgency=low
 .
   * Fix build-dep (Closes: #802119). Thanks Chris West!
Checksums-Sha1:
 7b1ead6512b9bd0d108e39a38e59b24c83418064 2276 python-diaspy_0.5.0.1-2.dsc
 f857468f7c57079d282c9cc57631345f6c9395c0 2372 
python-diaspy_0.5.0.1-2.debian.tar.xz
 f9c20828cdc9d01e99ac61cb7304fc2767dfb063 6806 
python-diaspy-doc_0.5.0.1-2_all.deb
 7910effc23414d3aac140c82b7a1733ca4c4615c 18386 python-diaspy_0.5.0.1-2_all.deb
 cbf51d6708369637d659cfd527d0060042305cfc 18458 python3-diaspy_0.5.0.1-2_all.deb
Checksums-Sha256:
 44c76580746793525c69e9f1cd423907422fa1d1dcaf8c8a18acd08be663d3ff 2276 
python-diaspy_0.5.0.1-2.dsc
 7fe5927087ad860d5767f7045564ff5f7f60623a111cbeb0e4ad9f804efe 2372 
python-diaspy_0.5.0.1-2.debian.tar.xz
 

Bug#802170: libopenscenegraph100v5: Can't install; package depends on libgdal.so.1-1.11.2 which doesn't exist

[Manuel A. Fernandez Montecelo]

Control: severity -1 important
Control: tags -1 + moreinfo unreproducible


2015-10-18 1:36 GMT+01:00 John Haiducek :
> Package: libopenscenegraph100v5
> Version: Package depends on libgdal.so.1-1.11.2 which isn't provided by any 
> package
> Severity: serious
> Justification: 2
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> I tried to install flightgear
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> apt-get install flightgear
> apt-get install libopenscenegraph100v5
>
>* What was the outcome of this action?
>
> The following packages have unmet dependencies:
>  flightgear : Depends: libopenscenegraph100v5 but it is not going to be
> installed
>   Depends: libsimgearscene3.4.0 (>= 3.4.0~) but it is not going to
> be installed
>
> The following packages have unmet dependencies:
>  libopenscenegraph100v5 : Depends: libgdal.so.1-1.11.2
>
>* What outcome did you expect instead?
>
> libopenscenegraph100v5 should install along with its dependencies

With an up-to-date unstable, "apt install openscenegraph" installs
fine.  Maybe some of the dependencies cannot be installed in testing
due to transitions or other reasons.

That library libgdal.so.1-1.11.2 is provided by libgdal1i, you can try
"apt-get install libgdal1i" to see if there are further explanations
why that package cannot be installed in your system.

We do no add the dependency of libgdal.so.1-1.11.2 directly, it was
added by depending on libgdal-dev.  I think that if there are any
problems with this is due to changes in that package or knock-on
effects.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Processed: Re: Bug#802170: libopenscenegraph100v5: Can't install; package depends on libgdal.so.1-1.11.2 which doesn't exist

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #802170 [libopenscenegraph100v5] libopenscenegraph100v5: Can't install; 
package depends on libgdal.so.1-1.11.2 which doesn't exist
Severity set to 'important' from 'serious'
> tags -1 + moreinfo unreproducible
Bug #802170 [libopenscenegraph100v5] libopenscenegraph100v5: Can't install; 
package depends on libgdal.so.1-1.11.2 which doesn't exist
Added tag(s) unreproducible and moreinfo.

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

Bug#802149: marked as done (python-mplexporter: FTBFS: ImportError: No module named 'numpy')

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 13:48:47 +
with message-id 
and subject line Bug#802149: fixed in python-mplexporter 0.0.1+20140921-2
has caused the Debian Bug report #802149,
regarding python-mplexporter: FTBFS: ImportError: No module named 'numpy'
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.)


-- 
802149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mplexporter
Version: 0.0.1+20140921-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Ran 0 tests in 0.000s

OK
I: pybuild base:170: cd 
/python-mplexporter-0.0.1+20140921/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
unittest discover -v 
mplexporter (unittest.loader._FailedTest) ... ERROR

==
ERROR: mplexporter (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: mplexporter
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/python-mplexporter-0.0.1+20140921/.pybuild/pythonX.Y_3.5/build/mplexporter/__init__.py",
 line 1, in 
from .renderers import Renderer
  File 
"/python-mplexporter-0.0.1+20140921/.pybuild/pythonX.Y_3.5/build/mplexporter/renderers/__init__.py",
 line 9, in 
from .base import Renderer
  File 
"/python-mplexporter-0.0.1+20140921/.pybuild/pythonX.Y_3.5/build/mplexporter/renderers/base.py",
 line 5, in 
import numpy as np
ImportError: No module named 'numpy'


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/python-mplexporter-0.0.1+20140921/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
unittest discover -v 

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-mplexporter.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-mplexporter
Source-Version: 0.0.1+20140921-2

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated python-mplexporter 
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: Sun, 18 Oct 2015 13:35:57 +
Source: python-mplexporter
Binary: python-mplexporter python3-mplexporter
Architecture: source all
Version: 0.0.1+20140921-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-mplexporter - general matplotlib exporter
 python3-mplexporter - general matplotlib exporter
Closes: 802149
Changes:
 python-mplexporter (0.0.1+20140921-2) unstable; urgency=medium
 .
   * fix b-d on numpy/matplotlib (Closes: #802149) Thanks Chris West!
Checksums-Sha1:
 fb58407a019afef0d935577c90287e28c259034b 2314 
python-mplexporter_0.0.1+20140921-2.dsc
 9e2a7d1fc622b0ba92d46d262c48f16e9e79ba16 2156 
python-mplexporter_0.0.1+20140921-2.debian.tar.xz
 b99e56a82678df2b00389b158f8fa53c781d6f1e 24896 
python-mplexporter_0.0.1+20140921-2_all.deb
 e2e4ff64a9723f972eef06767cef0aaffe0901d4 24870 
python3-mplexporter_0.0.1+20140921-2_all.deb
Checksums-Sha256:
 5cf743f02e7197ccf7146ebc11f7979bdbcf31b7b5aba1a860f842aed4c181ea 2314 
python-mplexporter_0.0.1+20140921-2.dsc
 

Bug#802030: marked as done (psi4 FTBFS on mips, testsuite timeout)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 12:38:40 +0200
with message-id <20151018103838.gk18...@raptor.chemicalconnection.dyndns.org>
and subject line Re: [Debichem-devel] Bug#802030: psi4 FTBFS on mips, testsuite 
timeout
has caused the Debian Bug report #802030,
regarding psi4 FTBFS on mips, testsuite timeout
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.)


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

Package: psi4
Version: 1:0.3-1
Severity: serious

The last three uploads of your package (0.3-1, 0.3-2 and 0.3-3) have all 
failed on mips with testsuite timeouts.
--- End Message ---
--- Begin Message ---
(Adding the mips list to CC)

On Sat, Oct 17, 2015 at 04:13:38AM +0100, peter green wrote:
> Package: psi4
> Version: 1:0.3-1
> Severity: serious
> 
> The last three uploads of your package (0.3-1, 0.3-2 and 0.3-3) have
> all failed on mips with testsuite timeouts.

Right, the problem is apparently that all the mips autobuilders do not
have an FPU (ball and swarm maybe did, but they were decomissioned), so
running computation-heavy testsuites is cumbersome.

I don't think it's a problem with psi4 (so I am closing this bug for
now), if you look at the build log, one of the tests before the timeout
was a near miss:

|42/95 Test #101: dfmp2-1 ..   Passed  19441.39 sec
|  Start 105: dfmp2-grad1
|43/95 Test #105: dfmp2-grad1 ..   Passed  579.99 sec
|  Start 106: dfmp2-grad2
|44/95 Test #106: dfmp2-grad2 ..***Failed  1224.16 sec
|  Start 109: dfomp2-1
|45/95 Test #109: dfomp2-1 .   Passed  454.26 sec
|  Start 110: dfomp2-2
|46/95 Test #110: dfomp2-2 .***Failed  954.27 sec
|  Start 122: dft1
|make: *** wait: No child processes.  Stop.
|make: *** Waiting for unfinished jobs
|make: *** wait: No child processes.  Stop.
|E: Caught signal ‘Terminated’: terminating immediately
|debian/rules:54: recipe for target 'override_dh_auto_test' failed
|make[1]: [override_dh_auto_test] Terminated (ignored)
|Build killed with signal TERM after 720 minutes of inactivity

19441 seconds are 324 minutes. For reference, those are the numbers on
mipsel:

|42/95 Test #101: dfmp2-1 ..   Passed  239.63 sec
|  Start 105: dfmp2-grad1
|43/95 Test #105: dfmp2-grad1 ..   Passed   12.09 sec
|  Start 106: dfmp2-grad2
|44/95 Test #106: dfmp2-grad2 ..   Passed   15.59 sec
|  Start 109: dfomp2-1
|45/95 Test #109: dfomp2-1 .   Passed9.56 sec
|  Start 110: dfomp2-2
|46/95 Test #110: dfomp2-2 .   Passed   18.00 sec
|  Start 122: dft1
|47/95 Test #122: dft1 .   Passed  1169.88 sec

So mips seems to be around 80x slower than mipsel and the timeout would
need to be around 1700 minutes rather 720 minutes for it to have a
chance to build that.

So I see three alternatives:

1. Reschedule on a different, presumably more powerful, buildd, if one
exists (I don't think so?)

2. Crank up the testsuite timeout to 2000 minutes or so

3. Add it to not-for-us on mips, or otherwise blacklist it, and remove
the .deb (which built by accident on lucatelli when the testsuite was
not exercised)

Mips porters/buildd maintainers, what is your preference?


Michael--- End Message ---

Bug#785926: Bug#731122: Initial patch for GStreamer 1.0 / farstream 0.2 support

[Bernhard Schmidt]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 17.10.2015 20:12, Sebastian Dröge wrote:

Hi Sebastian,

>>> I can't do that, as
>>> 
>>> - my DD application is still in progress - I certainly don't
>>> want to NMU a multi-binary package with a library and
>>> five-digit popcon count as first action
>>> 
>>> However, if someone wants to, I have uploaded 2.10.11-1.1 to
>>> mentors
>>> 
>>> http://mentors.debian.net/package/pidgin
>> 
>> I'll take a look at this later today, thanks for preparing this!
>> I assume, considering what you wrote above, that you don't want
>> to be listed in the changelog at the bottom line then?
> 
> Going to upload that in a bit now.

Thanks :-)

> But I noticed that Fedora has lots of other patches that would
> probably be useful to have for proper interoperability with other
> software, and various fixes:
> http://pkgs.fedoraproject.org/cgit/pidgin.git/tree/
> 
> Might make sense for Ari to merge at least some of these, they're
> all upstream but it doesn't look like there will be a new release
> anytime soon.

I agree. Ubuntu also has some additional patches.

Bernhard
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWI4SQAAoJEHdQeeW4ULyTqxQP/RDL8WMOGvYjLDYfuupoYJIr
YHLfntwm7E2a6trsKgbq9StnD1mfXVzb5Lmm9OCwQMzsx72iGWxInV2+puVoPx5n
2WQzAmQXMSclZr6mjPEXcKD4Y25C8cz1bCkhuY3ILZvvHdjw3efyzMvspNihfSrK
X5kWa9cAWR72z2X4UbhAJLVViBb8/DUMQq5csjLVZNIbcQrwIswin9TQ7eFVQZfF
fd2J3Rwt8hDwjtw0q8MXwKRpb4450bgy3kwBCC9NQ+JL7M6V5RG83JJVrXmZlzuN
086mx0lc5ItY++rISCdnUY+RgaXk6kIuA4L2d9XZL09dBdIVJhURL2lYNlJQV8Sx
ikXXWCpkzBIogPKg6c3Oy5PO7VcOLKl4WDeV3Kc7EJUB0E29VzxnMXj5u6ifp1Mv
0p2KIxmsc9btm/oOvjCe5RMWEo4SySOVrlPrtRNcayI9NYhGf1xkdneAOhy82AQb
5iSSohiRbOC9iZ2cOYHhHkM39XDYJBIplCPCKvCrmPoDFkuf0ihLwPqQgta/1wGD
LvLfIbdOP6vlpIz7/BECGT7zgSjbmRII1D47u+rh2AcCU7UfjSXowEudltBBuDJl
FcFGiKFlUcBet5OYrHBJj95jc0p2O++qyVR53GiZFZgvutjb9P78R0DuAgJLIL3U
5TihI/mIrQjw19Va97ak
=DKMT
-END PGP SIGNATURE-

Processed: Bug#802149 marked as pending

[Debian Bug Tracking System]

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

> tag 802149 pending
Bug #802149 [src:python-mplexporter] python-mplexporter: FTBFS: ImportError: No 
module named 'numpy'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802025: /etc/mtab is not a symlink or not pointing to /proc/self/mounts

[Martin Pitt]

Control: severity -1 important
Control: tag -1 confirmed
Control: forwarded -1 https://github.com/systemd/systemd/issues/1495

Ilya Sukhanov [2015-10-16 18:53 -0400]:
> System freezes at boot with "/etc/mtab is not a symlink or not pointing
> to /proc/self/mounts..."

As discussed on the upstream bug, this check will be removed from
systemd with util-linux 2.27.1. Until then we'll keep it around for a
few weeks to uncover issues like #802184 (which got fixed now in
https://tracker.debian.org/news/719605).

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Processed: Re: Bug#802025: /etc/mtab is not a symlink or not pointing to /proc/self/mounts

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #802025 [systemd] /etc/mtab is not a symlink or not pointing to 
/proc/self/mounts
Severity set to 'important' from 'grave'
> tag -1 confirmed
Bug #802025 [systemd] /etc/mtab is not a symlink or not pointing to 
/proc/self/mounts
Added tag(s) confirmed.
> forwarded -1 https://github.com/systemd/systemd/issues/1495
Bug #802025 [systemd] /etc/mtab is not a symlink or not pointing to 
/proc/self/mounts
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/1495'.

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

Processed: found 799140 in 3.6.1+dfsg-1

[Debian Bug Tracking System]

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

> found 799140 3.6.1+dfsg-1
Bug #799140 {Done: Mike Gabriel } [src:wordpress] 
wordpress: CVE-2015-5714 CVE-2015-5715
Marked as found in versions wordpress/3.6.1+dfsg-1.
> thanks
Stopping processing here.

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

Bug#802208: jq: FTBFS on mips*: tests fail

[Jakub Wilk]

* Jakub Wilk , 2015-10-18, 13:17:

FAIL: tests/jqtest
==

Segmentation fault
FAIL tests/jqtest (exit status: 139)


I ran this under gdb:

(gdb) run
Starting program: /home/jwilk/jq-1.5+dfsg/jq -L tests/modules --run-tests 
tests/jq.test

Program received signal SIGSEGV, Segmentation fault.
jvp_array_read (i=0, a=...) at jv.c:222
222 assert(i + jvp_array_offset(a) < array->length);
(gdb) bt
#0  jvp_array_read (i=0, a=...) at jv.c:222
#1  0x55575244 in jv_array_get (j=..., idx=0) at jv.c:325
#2  0x5558c33c in jv_test () at jq_test.c:205
#3  0x5558faa8 in jq_testsuite (libdirs=..., verbose=0, argc=1, 
argv=0x7fff6734) at jq_test.c:14
#4  0x69cc in main (argc=5, argv=) at main.c:412
warning: GDB can't find the start of the function at 0x77d7f7c3.


Unfortunately, many things are optimized out, so it's hard to tell 
what's wrong here; and if I disable optimizations, the problem goes 
away. :-\


--
Jakub Wilk

Bug#802208: jq: FTBFS on mips*: tests fail

[Simon Elsbrock]

Hi Jakub,

On Sun, Oct 18, 2015, at 16:36, Jakub Wilk wrote:
> I ran this under gdb:
> […]
> 
> Unfortunately, many things are optimized out, so it's hard to tell 
> what's wrong here; and if I disable optimizations, the problem goes 
> away. :-\

thank you, I will make sure this information is forwarded to upstream.

Regards
Simon

Bug#802208: jq: FTBFS on mips*: tests fail

[Jakub Wilk]

* Jakub Wilk , 2015-10-18, 16:36:
Unfortunately, many things are optimized out, so it's hard to tell 
what's wrong here; and if I disable optimizations, the problem goes 
away. :-\


Even -O1 makes the tests pass.
It doesn't crash when you compile with gcc-4.9 with default 
optimizations either.


--
Jakub Wilk

Bug#800617: marked as done (Fails to provide secrets)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 15:50:05 +
with message-id 
and subject line Bug#800617: fixed in gnome-keyring 3.18.1-1
has caused the Debian Bug report #800617,
regarding Fails to provide secrets
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.)


-- 
800617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.18.0-1
Severity: grave

Since upgrading gnome-keyring from 3.16.0-4 to 3.18.0-1, applications
trying to retrieve secrets from gnome-keyring no longer can.  I see log
messages like the following:

Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5801]: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
[...]
Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't register in 
session: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't communicate 
with already running daemon: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't 
communicate with already running daemon: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: 
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 01 10:36:39 jtriplet-mobl1 gnome-keyring-daemon[5844]: couldn't register in 
session: Timeout was reached
[...]
Oct 01 10:37:03 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't request 
name 'org.freedesktop.secrets' on session bus: Timeout was reached
[...]
Oct 01 10:48:34 jtriplet-mobl1 org.gnome.evolution.dataserver.Sources4[5783]: 
server_side_source_credentials_lookup_cb: Failed to lookup password: Error 
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
Oct 01 10:48:35 jtriplet-mobl1 org.gnome.seahorse.Application[5783]: 
(seahorse:8293): seahorse-WARNING **: gkr-backend.vala:85: couldn't connect to 
secret service: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

In addition to that, it also looks like every time an application tries to
access the org.freedesktop.secrets service, dbus spawns an instance of
gnome-keyring with the --foreground option, likely based on
/usr/share/dbus-1/services/org.freedesktop.secrets.service ; does this conflict
with the instance already run via /etc/xdg/autostart?

- Josh Triplett

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

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

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.10.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.16.0-1
ii  libc62.19-22
ii  libcap-ng0   0.7.7-1
ii  libcap2-bin  1:2.24-11
ii  libgck-1-0   3.16.0-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.46.0-2
ii  p11-kit  0.23.1-3
ii  pinentry-gnome3  0.9.5-4

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.18.0-1

gnome-keyring suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-keyring
Source-Version: 3.18.1-1

We believe that the bug you reported is fixed in the latest version of
gnome-keyring, 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 

Bug#800660: marked as done (gnome-keyring: crashes iceweasel when logging into a password-protected website)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 15:50:05 +
with message-id 
and subject line Bug#800660: fixed in gnome-keyring 3.18.1-1
has caused the Debian Bug report #800660,
regarding gnome-keyring: crashes iceweasel when logging into a 
password-protected website
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.)


-- 
800660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.18.0-1
Severity: grave
Justification: renders package unusable

Since I upgraded to gnome-keyring 3.18, I'm no longer able to login into
password-protected website with iceweasel. It just gets stuck and I have
to kill it.

In the logs I see this:

oct. 02 10:04:42 x230-buxy gnome-keyring-daemon[2195]: asked to register item 
/org/freedesktop/secrets/collection/login/23, but it's already registered
oct. 02 10:05:06 x230-buxy gnome-session[2199]: ** (gnome-shell:2354): CRITICAL 
**: remove_mnemonics: assertion 'label != NULL' failed
oct. 02 10:05:06 x230-buxy gnome-keyring-daemon[2195]: could not register 
secret unlock prompt on session bus: Un objet est déjà exporté pour l'interface 
« org.freedesktop.Secret.Prompt » en « /org/freedesktop/secrets/prompt/p6 »
oct. 02 10:05:06 x230-buxy gnome-keyring-daemon[2195]: GLib-GIO: 
g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != 
NULL' failed

“Un objet est déjà exporté pour l'interface“ means “An object is already
exported for the interface”.

Note that I am using dbus-user-session 1.10.0-3 in order to make
pinentry-gnome3 work with gpg-agent (which otherwise lacks the variables for
the session dbus).

Note that I also have customized start up scripts:
$ tail -n 1 /home/rhertzog/.config/autostart/gnome-keyring-*.desktop 
==> /home/rhertzog/.config/autostart/gnome-keyring-gpg.desktop <==
X-GNOME-Autostart-enabled=false

==> /home/rhertzog/.config/autostart/gnome-keyring-ssh.desktop <==
X-GNOME-Autostart-enabled=false

I don't know if it's still needed nowadays but in the past, it
used to take over the place of gpg-agent which handles both GPG
and SSH keys for me.

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

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

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.10.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.16.0-1
ii  libc62.19-22
ii  libcap-ng0   0.7.7-1
ii  libcap2-bin  1:2.24-11
ii  libgck-1-0   3.16.0-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.46.0-2
ii  p11-kit  0.23.1-3
ii  pinentry-gnome3  0.9.5-4.1

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.18.0-1

gnome-keyring suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-keyring
Source-Version: 3.18.1-1

We believe that the bug you reported is fixed in the latest version of
gnome-keyring, 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.
Dmitry Shachnev  (supplier of updated gnome-keyring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Oct 2015 17:30:21 +0300
Source: gnome-keyring
Binary: gnome-keyring libpam-gnome-keyring
Architecture: source
Version: 3.18.1-1

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

[Felix Natter]

Sebastiaan Couwenberg  writes:

> On 18-10-15 17:00, tony mancill wrote:
>> On 10/18/2015 04:58 AM, Sebastiaan Couwenberg wrote:
>>> On Fri, 16 Oct 2015 20:49:12 +0200 Felix Natter wrote:
 I added a patch for JMapViewer-1.11 compatibility: 
 http://anonscm.debian.org/cgit/pkg-java/freeplane.git
 
 I've set the distribution to experimental since it should
 probably be uploaded to unstable together with jmapviewer (now
 that it _requires_ jmapviewer>=1.11).
 
 @Tony: Would you be willing to sponsor this and/or shall I
 submit an RFS for this?
>>> 
>>> Since my upload of jmapviewer now causes freeplane to FTBFS, I'm
>>> willing to sponsor the upload of freeplane too.
>> 
>> Whoops - I'm several days behind on email.  I'll upload freeplane
>> today, if Bas doesn't beat me to it.

hello Tony,
hello Bas,

> Since I cannot commit to pkg-java freeplane git repository (due to not
> being a member of pkg-java), I think you (Tony) are in a better
> position to sponsor the upload.

Ok, that makes sense, I think :-)

> Currently freeplane (1.3.15-3) is targeted at experimental in the
> changelog, this should probably change to unstable now that jmapviewer
> (1.11+dfsg-1) is available in unstable.
>
> @Felix, can you confirm that this is also your intention?

Yes, I just changed this to unstable and uploaded to mentors:
  https://mentors.debian.net/package/freeplane

Thanks and Best Regards,
-- 
Felix Natter

Bug#802128: marked as done (python-crank: FTBFS: ImportError: No module named 'webob')

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 15:52:29 +
with message-id 
and subject line Bug#802128: fixed in python-crank 0.7.2-2
has caused the Debian Bug report #802128,
regarding python-crank: FTBFS: ImportError: No module named 'webob'
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.)


-- 
802128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-crank
Version: 0.7.2-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

running build_ext
objectdispatcher (unittest.loader._FailedTest) ... ERROR
restdispatcher (unittest.loader._FailedTest) ... ERROR
test_dispatcher (unittest.loader._FailedTest) ... ERROR
test_objectdispatcher (unittest.loader._FailedTest) ... ERROR
test_restdispatcher (unittest.loader._FailedTest) ... ERROR
tests.test_dispatcher (unittest.loader._FailedTest) ... ERROR
tests.test_objectdispatcher (unittest.loader._FailedTest) ... ERROR
tests.test_restdispatcher (unittest.loader._FailedTest) ... ERROR

==
ERROR: objectdispatcher (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: objectdispatcher
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/python-crank-0.7.2/crank/objectdispatcher.py", line 21, in 
from webob.exc import HTTPNotFound
ImportError: No module named 'webob'


==
ERROR: restdispatcher (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: restdispatcher
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/python-crank-0.7.2/crank/restdispatcher.py", line 8, in 
from webob.exc import HTTPMethodNotAllowed
ImportError: No module named 'webob'


==
ERROR: test_dispatcher (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_dispatcher
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/python-crank-0.7.2/tests/test_dispatcher.py", line 1, in 
from nose.tools import raises
ImportError: No module named 'nose'



Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-crank.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-crank
Source-Version: 0.7.2-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-crank package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Oct 2015 14:01:10 +
Source: python-crank
Binary: python-crank python3-crank
Architecture: source all
Version: 0.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-crank - dispatch mechanism for use across frameworks - Python 2.7
 python3-crank - dispatch mechanism for use across frameworks - Python 3.x
Closes: 802128
Changes:
 python-crank (0.7.2-2) unstable; urgency=medium
 .
   * Fixed FTBFS by adding python-webob as build-depends 

Bug#802110: marked as done (rtkit: FTBFS: rtkit_daemon-sd-daemon.o: undefined reference to symbol 'mq_getattr@@GLIBC_2.3.4')

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 16:20:23 +
with message-id 
and subject line Bug#802110: fixed in rtkit 0.11-3
has caused the Debian Bug report #802110,
regarding rtkit: FTBFS: rtkit_daemon-sd-daemon.o: undefined reference to symbol 
'mq_getattr@@GLIBC_2.3.4'
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.)


-- 
802110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rtkit
Version: 0.11-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

/usr/bin/ld: rtkit_daemon-sd-daemon.o: undefined reference to symbol 
'mq_getattr@@GLIBC_2.3.4'
//lib/x86_64-linux-gnu/librt.so.1: error adding symbols: DSO missing from 
command line
collect2: error: ld returned 1 exit status
Makefile:474: recipe for target 'rtkit-daemon' failed
make[2]: *** [rtkit-daemon] Error 1
make[2]: Leaving directory '/rtkit-0.11'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/rtkit.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: rtkit
Source-Version: 0.11-3

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated rtkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Oct 2015 12:45:11 -0300
Source: rtkit
Binary: rtkit
Architecture: source amd64
Version: 0.11-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 rtkit  - Realtime Policy and Watchdog Daemon
Closes: 802110
Changes:
 rtkit (0.11-3) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Add myself to uploaders
   * Add patch to fix rtkit-test failure
   * Install rtkit test program
   * Use autoreconf at build
   * Fix linkage with librt (Closes: #802110)
   * Build rtkit out-of-tree
   * Fixup build in outoftree
   * Pick up no-ptrace patch from ubuntu.
 .
   [ Alessio Treglia ]
   * Drop 02-fix-undropped-supp-groups.patch.
Checksums-Sha1:
 2e2cbe8ec3879bf6ff3a9a0dc44dcafb57faa4db 2038 rtkit_0.11-3.dsc
 2870ee59f946bdf19d0f3355208ac21b0284fbd7 5400 rtkit_0.11-3.debian.tar.xz
 9dbc4faa471941b72059c923d1791b9f0743b086 33418 rtkit_0.11-3_amd64.deb
Checksums-Sha256:
 0f363458275a08fca8cec236a853eb63a2cc998fb5885abc63dbbbf4f5c99a90 2038 
rtkit_0.11-3.dsc
 eee4a27a7d80a75824442f6e8be1785f06d987fa7d6e361d31217b53874bc956 5400 
rtkit_0.11-3.debian.tar.xz
 757f00991a9430d78f0d844c49edc2850050d4546d4d5c146f4ae61bbafb77c3 33418 
rtkit_0.11-3_amd64.deb
Files:
 a57a9a32d7c3a45f82804aec4987fdf9 2038 admin optional rtkit_0.11-3.dsc
 7a34c6be47a41a56ffeb5ec922739778 5400 admin optional rtkit_0.11-3.debian.tar.xz
 d289422b533ce6ab7f834a7aff89a10e 33418 admin optional rtkit_0.11-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWI7+6AAoJEKO6uuJAjdbPj8AP/1VACqGWvTez7CPxhdu/z6sO
CdSf6LO6sfOtiVUNVncyswuVxGrTeEBW7qhy2C1MnAA9eZTyjcxSDXCNSJ7xAlwF
8yrbkYhEwkQP283RIImX1mP0PlJkMF2801xRE7VpNESRPfrkokiZQgZhJ21SZ+ux
mbygzZrx3/OASieH7FMBnodY5g5yQcr6uyy+i6RsdLwKh1DQ0YATSjOQC309105q
oHCUdUtoM+SYyUrkg0dRBITKBALvTMsVoiPXLTf747bocdK6X8jKM63FMGybd9pE
Xz2O8S47/2wt/pi4Byd8zI2cYA9wy1oT/lO0b0l39bFT8Axz/QM5nDC8H1/dCjv+
hNjy6nrDgUNdKWOwpbUy8lWeKsujmldlji4VjQpNiCR57JoqkpIJPbGlipH4SkdL
3uqXybOvPIG66iwZNCft1slKndE8AamMLqvgODYUOJNoH7QzyDeyJ3nAGhrWD5+z
oO3GrA8xBZjZJAVwftCugOAqe0uW+Hs0omvZYgoyjo8N2PRBhVmYZclb+i5ic114
X90MfWu5ySW1/5eB33kFVF78pzJldfi/ylKruLT8jJklKgIfLSVGnIgq4ggFCNgW
FMPU4NRhZapxNhpanfC11sQL3YdOFCSp62IHDmbBcFK2vLIyJ1g/kWG75mfn6Mmc
8+c0XJDKf4ad/g7qdY0g
=eElw
-END PGP SIGNATURE 

Bug#801475: marked as done (freeplane: Fails to build with JMapViewer 1.11)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 16:19:50 +
with message-id 
and subject line Bug#801475: fixed in freeplane 1.3.15-3
has caused the Debian Bug report #801475,
regarding freeplane: Fails to build with JMapViewer 1.11
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.)


-- 
801475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeplane
Version: 1.3.15-2
Severity: important
Tags: upstream

Dear Maintainer,

The jmapviewer package in Debian has been updated to the recent
JMapViewer 1.11 upstream release as required for JOSM 8800
(both available in experimental).

Unfortunately freeplane (1.3.15-2) fails to build with
jmapviewer (1.11+dfsg-1~exp1) as can be seen in the partial build log
below.

Please update the openmaps plugin to support JMapViewer 1.11 or consider
adding skip_openmaps=true to debian/ant.properties.

The severity of this issue will be raised to serious when
jmapviewer (1.11+dfsg-1) is moved from experimental to unstable.
I expect to do that next week.


>From the freeplane (1.3.15-2) build log:

 build:
 [mkdir] Created dir: 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/build
 [javac] 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/ant/build.xml:23: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
 [javac] Compiling 12 source files to 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/build
 [javac] warning: [options] bootstrap class path not set in conjunction 
with -source 1.5
 [javac] 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/src/org/freeplane/plugin/openmaps/mapelements/OpenMapsController.java:64:
 error: incompatible types
 [javac] return map.getPosition(clickedLocation); 
 [javac]   ^
 [javac]   required: Coordinate
 [javac]   found:ICoordinate
 [javac] 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/src/org/freeplane/plugin/openmaps/mapelements/OpenMapsController.java:84:
 error: cannot find symbol
 [javac] int x = (int)OsmMercator.LonToX(location.getLon(), zoom);
 [javac] ^
 [javac]   symbol:   method LonToX(double,int)
 [javac]   location: class OsmMercator
 [javac] 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/src/org/freeplane/plugin/openmaps/mapelements/OpenMapsController.java:85:
 error: cannot find symbol
 [javac] int y = (int)OsmMercator.LatToY(location.getLat(), zoom);
 [javac] ^
 [javac]   symbol:   method LatToY(double,int)
 [javac]   location: class OsmMercator
 [javac] Note: 
/tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/src/org/freeplane/plugin/openmaps/mapelements/OpenMapsViewer.java
 uses or overrides a deprecated API.
 [javac] Note: Recompile with -Xlint:deprecation for details.
 [javac] 3 errors
 [javac] 1 warning
 
 BUILD FAILED
 /tmp/buildd/freeplane-1.3.15/build.xml:4: The following error occurred while 
executing this line:
 /tmp/buildd/freeplane-1.3.15/freeplane_framework/ant/build.xml:139: The 
following error occurred while executing this line:
 /tmp/buildd/freeplane-1.3.15/freeplane_framework/ant/build.xml:55: The 
following error occurred while executing this line:
 /tmp/buildd/freeplane-1.3.15/freeplane_plugin_openmaps/ant/build.xml:23: 
Compile failed; see the compiler error output for details.

 Total time: 18 seconds


My appologies for the inconvenience,

Bas
--- End Message ---
--- Begin Message ---
Source: freeplane
Source-Version: 1.3.15-3

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

Debian distribution maintenance software
pp.
Felix Natter  (supplier of updated freeplane package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Oct 2015 17:11:38 +0200
Source: freeplane
Binary: 

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

[tony mancill]

On 10/18/2015 04:58 AM, Sebastiaan Couwenberg wrote:
> Hi Felix,
> 
> I missed this update to the bugreport.
> 
> On Fri, 16 Oct 2015 20:49:12 +0200 Felix Natter wrote:
>> I added a patch for JMapViewer-1.11 compatibility:
>>   http://anonscm.debian.org/cgit/pkg-java/freeplane.git
>>
>> I've set the distribution to experimental since it should probably be
>> uploaded to unstable together with jmapviewer (now that it _requires_
>> jmapviewer>=1.11).
>>
>> @Tony: Would you be willing to sponsor this and/or shall I submit an RFS
>> for this?
> 
> Since my upload of jmapviewer now causes freeplane to FTBFS, I'm willing
> to sponsor the upload of freeplane too.

Whoops - I'm several days behind on email.  I'll upload freeplane today,
if Bas doesn't beat me to it.

Cheers,
tony




signature.asc
Description: OpenPGP digital signature

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

[Sebastiaan Couwenberg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 18-10-15 17:00, tony mancill wrote:
> On 10/18/2015 04:58 AM, Sebastiaan Couwenberg wrote:
>> On Fri, 16 Oct 2015 20:49:12 +0200 Felix Natter wrote:
>>> I added a patch for JMapViewer-1.11 compatibility: 
>>> http://anonscm.debian.org/cgit/pkg-java/freeplane.git
>>> 
>>> I've set the distribution to experimental since it should
>>> probably be uploaded to unstable together with jmapviewer (now
>>> that it _requires_ jmapviewer>=1.11).
>>> 
>>> @Tony: Would you be willing to sponsor this and/or shall I
>>> submit an RFS for this?
>> 
>> Since my upload of jmapviewer now causes freeplane to FTBFS, I'm
>> willing to sponsor the upload of freeplane too.
> 
> Whoops - I'm several days behind on email.  I'll upload freeplane
> today, if Bas doesn't beat me to it.

Since I cannot commit to pkg-java freeplane git repository (due to not
being a member of pkg-java), I think you (Tony) are in a better
position to sponsor the upload.

Currently freeplane (1.3.15-3) is targeted at experimental in the
changelog, this should probably change to unstable now that jmapviewer
(1.11+dfsg-1) is available in unstable.

@Felix, can you confirm that this is also your intention?

Kind Regards,

Bas

- -- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWI7dkAAoJEGdQ8QrojUrxBpcP/A+c7JKzP38FgfxpzUy5DWHN
kg0OlC3N7n1TMabWXzPA829Hlm6HC9Z/1jhokKacKmkpiTDq3EH5GLnfHOQYzZz9
I87Lr0LynHPvv/pxHFGOkAvNCcy+56dnvvdHWbAbcdJJyAwk1T97A068gVpglK4u
sWFRbabQDwXDzIYl23OiznFj78NaYq1+Tidi5u8Dh9rtroEXY3KzK9ot8iM7aiKV
AyT6tZwMbkwsJiQJovLDNoJagQuryHTgoXYshFQOSj10++2PB0EyWk9P/ZJ0E57I
kSgEdLIVqqgYz4h0nzCoBax36zknZ7PnVbtAdzPU0zMkuvc4INu0I+8g7qkhs4zp
kDp3HgSPjRait9QHGf16yUxuiWnStkyryxHQbq4c068eVg6NSL6l7/7Q3g9gxbnF
aXROEzBSnW3w2pAwWweEWtmNI7bdLi3Lx/lf/8pTVzSf/6YIH0kYT1G41rnz8ap/
jGESagJElcz9c9y1ImyQ8xwVa/WuzMuEmiHcMM/B4kelGUFh8sfrt/1KP4T+/ZwA
hqHKkFj4LAZwHx+AEmE/zBaVdwBWx0Bus5sdkaohBHkj13lYMtwBPtzxroOjgU2X
M4MdALFejQsreGuSyfWZ52lbqXs0R2qtLgLQKnueKhEAIUvFtxNQe3P5ZrGKca0/
2jPCRF84YqmojFHNEsyY
=4K9W
-END PGP SIGNATURE-

Bug#802150: marked as done (python-tosca-parser: FTBFS: dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 15:52:37 +
with message-id 
and subject line Bug#802150: fixed in python-tosca-parser 0.1.0-3
has caused the Debian Bug report #802150,
regarding python-tosca-parser: FTBFS: dh: Unknown sequence 
/usr/share/openstack-pkg-tools/pkgos.make
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.)


-- 
802150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tosca-parser
Version: 0.1.0-2
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

dpkg-buildpackage: source package python-tosca-parser
dpkg-buildpackage: source version 0.1.0-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Thomas Goirand 
 dpkg-source --before-build python-tosca-parser-0.1.0
dpkg-buildpackage: host architecture amd64
dpkg-source: info: using options from 
python-tosca-parser-0.1.0/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
 debian/rules clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:7: /usr/share/openstack-pkg-tools/pkgos.make: No such file or 
directory
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
debian/rules:11: recipe for target '/usr/share/openstack-pkg-tools/pkgos.make' 
failed
make: *** [/usr/share/openstack-pkg-tools/pkgos.make] Error 255
dpkg-buildpackage: error: debian/rules clean gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-tosca-parser.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-tosca-parser
Source-Version: 0.1.0-3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-tosca-parser 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Oct 2015 14:11:41 +
Source: python-tosca-parser
Binary: python-tosca-parser python3-tosca-parser python-tosca-parser-doc
Architecture: source all
Version: 0.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-tosca-parser - parser for TOSCA Simple Profile in YAML - Python 2.x
 python-tosca-parser-doc - parser for TOSCA Simple Profile in YAML - doc
 python3-tosca-parser - parser for TOSCA Simple Profile in YAML - Python 3.x
Closes: 802150
Changes:
 python-tosca-parser (0.1.0-3) unstable; urgency=medium
 .
   * Added missing openstack-pkg-tools build-depends (Closes: #802150).
Checksums-Sha1:
 26ec7180a95a20da8fbb8b5822ec6718654393f9 2847 python-tosca-parser_0.1.0-3.dsc
 ffc0ad921cfc086cdb04a0513dad28910fc9fd91 3032 
python-tosca-parser_0.1.0-3.debian.tar.xz
 619804fe446da98f9d9a54ee397d0636fd0b8f07 24606 
python-tosca-parser-doc_0.1.0-3_all.deb
 7c6ca0d7da8572e3230ab5bfe101ce4d34f3e5d1 37202 
python-tosca-parser_0.1.0-3_all.deb
 fba05054d9dd27dcfac07b47451db50fdd53b561 37282 
python3-tosca-parser_0.1.0-3_all.deb
Checksums-Sha256:
 848f4f48dc7561509bbddc2a1de4bf26b91a826038dc02561187e1451815a8fc 2847 
python-tosca-parser_0.1.0-3.dsc
 5babcd964d84b20c8739c3593df64ed5262772070c12ee0ecfdc7126c4bf874e 3032 

Bug#802099: marked as done (python-django-appconf-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/appconf-doc)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 17:19:21 +
with message-id 
and subject line Bug#802099: fixed in python-django-appconf 1.0.1-4
has caused the Debian Bug report #802099,
regarding python-django-appconf-doc: fails to upgrade from 'testing' - trying 
to overwrite /usr/share/doc-base/appconf-doc
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.)


-- 
802099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django-appconf-doc
Version: 1.0.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-django-appconf-doc.
  Preparing to unpack .../python-django-appconf-doc_1.0.1-3_all.deb ...
  Unpacking python-django-appconf-doc (1.0.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-django-appconf-doc_1.0.1-3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/appconf-doc', which is also in 
package python-appconf-doc 0.5-4
  Errors were encountered while processing:
   /var/cache/apt/archives/python-django-appconf-doc_1.0.1-3_all.deb


cheers,

Andreas


python-appconf-doc=0.5-4_python-django-appconf-doc=1.0.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-django-appconf
Source-Version: 1.0.1-4

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-django-appconf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Oct 2015 17:07:59 +
Source: python-django-appconf
Binary: python-django-appconf python-appconf python3-django-appconf 
python3-appconf python-django-appconf-doc python-appconf-doc
Architecture: source all
Version: 1.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-appconf - helper class handling configuration defaults of apps - 2.7 
transi
 python-appconf-doc - helper class handling configuration defaults of apps - 
transition
 python-django-appconf - helper class handling configuration defaults of apps - 
Python 2.7
 python-django-appconf-doc - helper class handling configuration defaults of 
apps - doc
 python3-appconf - helper class handling configuration defaults of apps - 3.x 
transi
 python3-django-appconf - helper class handling configuration defaults of apps 
- Python 3.x
Closes: 802099
Changes:
 python-django-appconf (1.0.1-4) unstable; urgency=medium
 .
   * Fix Breaks+Replaces to fix upgrades (Closes: #802099).
Checksums-Sha1:
 a48953de2eed4c5b2e35feb75f9256a09dd5f1a3 2576 python-django-appconf_1.0.1-4.dsc
 235a91090d2812bebcb973d04ee6beeb31719962 3960 
python-django-appconf_1.0.1-4.debian.tar.xz
 5b0cc6076e88f46125be94fb5bcbf4398cc3b667 3922 
python-appconf-doc_1.0.1-4_all.deb
 9f78c658ebd4736a5c87f7de427740b6537ed09b 3918 python-appconf_1.0.1-4_all.deb
 ddf8a2c773815032bb81efb2f05fcdc2ab5350d6 27186 
python-django-appconf-doc_1.0.1-4_all.deb
 5e4a70e219ad05a753f7daf4862c6e2cfd729fa5 8226 
python-django-appconf_1.0.1-4_all.deb
 0c0e7752411754861c04588ef7ee1193f01b6a5f 3926 python3-appconf_1.0.1-4_all.deb
 480583508ba967204fa183623184aa5b67a72a04 8010 
python3-django-appconf_1.0.1-4_all.deb
Checksums-Sha256:
 eae288073242a27efe30c1c631177ef0ad1d071b52f837ebc44d44b084d46087 2576 
python-django-appconf_1.0.1-4.dsc
 d31e4759ce17dc2cc8d09e6bd0b4512981b26ddc8da2ad7df47f57fa0bebe382 3960 

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

Hi all,

Vladimir is right, same issue here. Indeed, It is weird to me not so many
people is currently reporting on it, but it is affecting a lot of programs.
Something happens when upgrading to version 0.6.x (I agree at this point)

plasma-desktop is also unable to start and panic (black screen).If you
update-alternative glx fall back to mesa, the desktop runs just fine (of
course, without the nvidia drivers)

I though it was solved by bug 799948 (ssdm panic too), but again, it is
not. At least you can "adduser sddm video" and make ssdm-greater works as a
workaround, but plasma-desktop panics still panics after you try to log on.

It is very easy to check it. Just install a fresh installation of KDE and
nvidia drivers and you will see a beautiful black screen. Let me know if
you need additional information but it is quite easy to reproduce

Regards

Bug#802184: Installation-reports

[Michael Biebl]

Am 18.10.2015 um 10:18 schrieb Cyril Brulebois:
> Control: retitle -1 installation-reports: systemd refuses to boot (/etc/mtab 
> vs. /proc/self/mounts)
> Control: reassign -1 finish-install
> Control: severity -1 serious
> Control: tag -1 - d-i
> Control: affects -1 installation-reports
> 
> Hi Henry,
> 
> Henry Williams  (2015-10-18):
>> Comments/Problems:
>>
>> On the first run systemd freezes execution. Exact wording:
>> [5.942102] systemd[1]: /etc/mtab is not a symlink or not
>> pointing to /proc/self/mounts. This is not supported anymore.
>> Please replace /etc/mtab with a symlink to /proc/self/mounts.
>>
>> [5.943702] systemd[1]: Freezing execution.
> 
> Thanks for reporting! This has been discussed in another bug report[1] a
> few hours ago, and a fix has been pushed to git; I'm uploading a fixed
> package in a moment.
> 
>  1. https://lists.debian.org/debian-boot/2015/10/msg00120.html
> 
> Adding systemd maintainers in copy for reference; it would be nice to
> know when systemd becomes stricter before it actually happens.
> 


While we were aware of the /etc/mtab issue (see [1]), we didn't know it
would affect d-i, otherwise we would have filed a bug report against d-i
in advance / notified you.

Thanks for fixing it so promptly,

Michael

[1] https://github.com/systemd/systemd/issues/1495
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#798765: xtrs: FTBFS with GCC 5: trs_memory.c:152:6: error: type of 'state' defaults to 'int' [-Werror=implicit-int]

[YunQiang Su]

On Sat, 12 Sep 2015 14:17:11 +0200 Andreas Beckmann  wrote:
> Package: xtrs
> Version: 4.9c-3.4
> Severity: serious
> Tags: sid stretch
> Justification: fails to build from source (but built successfully in the past)
>
> Hi,
>
> xtrs FTBFS in sid with GCC 5:
>
> [...]
> /usr/bin/make DEBUG="-Wall -Werror -Wno-error=unused-but-set-variable -O2 -g 
> -D_REENTRANT" PREFIX=/usr
> make[1]: Entering directory '/tmp/buildd/xtrs-4.9c'
> cc -Wall -Werror -Wno-error=unused-but-set-variable -O2 -g -D_REENTRANT  
> -DDEFAULT_ROM='"/usr/local/lib/xtrs/level2rom.hex"' 
> -DDEFAULT_ROM3='"/usr/local/lib/xtrs/romimage.m3"' 
> -DDEFAULT_ROM4P='"/usr/local/lib/xtrs/romimage.m4p"' -DREADLINE 
> -DDISKDIR='"."' -I/usr/include/X11 
> -DAPPDEFAULTS='"/usr/X11/lib/X11/app-defaults"' -DKBWAIT -DHAVE_SIGIO   -c -o 
> z80.o z80.c
> cc -Wall -Werror -Wno-error=unused-but-set-variable -O2 -g -D_REENTRANT  
> -DDEFAULT_ROM='"/usr/local/lib/xtrs/level2rom.hex"' 
> -DDEFAULT_ROM3='"/usr/local/lib/xtrs/romimage.m3"' 
> -DDEFAULT_ROM4P='"/usr/local/lib/xtrs/romimage.m4p"' -DREADLINE 
> -DDISKDIR='"."' -I/usr/include/X11 
> -DAPPDEFAULTS='"/usr/X11/lib/X11/app-defaults"' -DKBWAIT -DHAVE_SIGIO   -c -o 
> main.o main.c
> cc -Wall -Werror -Wno-error=unused-but-set-variable -O2 -g -D_REENTRANT  
> -DDEFAULT_ROM='"/usr/local/lib/xtrs/level2rom.hex"' 
> -DDEFAULT_ROM3='"/usr/local/lib/xtrs/romimage.m3"' 
> -DDEFAULT_ROM4P='"/usr/local/lib/xtrs/romimage.m4p"' -DREADLINE 
> -DDISKDIR='"."' -I/usr/include/X11 
> -DAPPDEFAULTS='"/usr/X11/lib/X11/app-defaults"' -DKBWAIT -DHAVE_SIGIO   -c -o 
> load_cmd.o load_cmd.c
> cc -Wall -Werror -Wno-error=unused-but-set-variable -O2 -g -D_REENTRANT  
> -DDEFAULT_ROM='"/usr/local/lib/xtrs/level2rom.hex"' 
> -DDEFAULT_ROM3='"/usr/local/lib/xtrs/romimage.m3"' 
> -DDEFAULT_ROM4P='"/usr/local/lib/xtrs/romimage.m4p"' -DREADLINE 
> -DDISKDIR='"."' -I/usr/include/X11 
> -DAPPDEFAULTS='"/usr/X11/lib/X11/app-defaults"' -DKBWAIT -DHAVE_SIGIO   -c -o 
> load_hex.o load_hex.c
> cc -Wall -Werror -Wno-error=unused-but-set-variable -O2 -g -D_REENTRANT  
> -DDEFAULT_ROM='"/usr/local/lib/xtrs/level2rom.hex"' 
> -DDEFAULT_ROM3='"/usr/local/lib/xtrs/romimage.m3"' 
> -DDEFAULT_ROM4P='"/usr/local/lib/xtrs/romimage.m4p"' -DREADLINE 
> -DDISKDIR='"."' -I/usr/include/X11 
> -DAPPDEFAULTS='"/usr/X11/lib/X11/app-defaults"' -DKBWAIT -DHAVE_SIGIO   -c -o 
> trs_memory.o trs_memory.c
> trs_memory.c: In function 'mem_romin':
> trs_memory.c:152:6: error: type of 'state' defaults to 'int' 
> [-Werror=implicit-int]
>  void mem_romin(state)
>   ^
> cc1: all warnings being treated as errors
> : recipe for target 'trs_memory.o' failed
> make[1]: *** [trs_memory.o] Error 1
> make[1]: Leaving directory '/tmp/buildd/xtrs-4.9c'
> debian/rules:34: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

I NMUed this package with the attached patch to 5 days delay.

>
>
> Andreas
>
>


xtrs.debdiff
Description: Binary data

Bug#802080: marked as done (kadu-mime-tex: FTBFS: cmake couldn't find Qt5Core)

[Debian Bug Tracking System]

Your message dated Sun, 18 Oct 2015 17:49:29 +
with message-id 
and subject line Bug#802080: fixed in kadu-mime-tex 2.1-1
has caused the Debian Bug report #802080,
regarding kadu-mime-tex: FTBFS: cmake couldn't find Qt5Core
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.)


-- 
802080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kadu-mime-tex
Version: 1.0-2
Severity: serious
Justification: fails to build from source
Tags: sid
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

-- Detecting CXX compile features - done
CMake Error at /usr/share/cmake/Kadu/KaduMacros.cmake:25 (find_package):
  By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt5Core", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5Core"
  (requested version 5.2) with any of the following names:

Qt5CoreConfig.cmake
qt5core-config.cmake

  Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
  "Qt5Core_DIR" to a directory containing one of the above files.  If
  "Qt5Core" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  /usr/share/cmake/Kadu/KaduConfig.cmake:62 (include)
  CMakeLists.txt:8 (find_package)


-- Configuring incomplete, errors occurred!
See also "/kadu-mime-tex-1.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
"tail -v -n +0 CMakeCache.txt"

...

Died at /usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm line 93.
debian/rules:22: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/kadu-mime-tex.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: kadu-mime-tex
Source-Version: 2.1-1

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

Debian distribution maintenance software
pp.
Patryk Cisek  (supplier of updated kadu-mime-tex 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: Sun, 18 Oct 2015 19:15:26 +0200
Source: kadu-mime-tex
Binary: kadu-mime-tex
Architecture: source amd64
Version: 2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Patryk Cisek 
Changed-By: Patryk Cisek 
Description:
 kadu-mime-tex - Plugin for Kadu, that TeX formulas in chat window
Closes: 802080
Changes:
 kadu-mime-tex (2.1-1) unstable; urgency=medium
 .
   * Added missing packages to Build-Depends (Closes: #802080)
   * Using Vogel's upstream port now
   * Updated Source link in debian/copyright
Checksums-Sha1:
 6ca3fe8e6aeecb68a6fda75d621eb08da7e6f773 2302 kadu-mime-tex_2.1-1.dsc
 c00ad0027ddd3ed0a851a0604d225b43444c97fe 563331 kadu-mime-tex_2.1.orig.tar.bz2
 16421a80a8bf31e2926fe806eae5f8dfb2384219 2692 kadu-mime-tex_2.1-1.debian.tar.xz
 402fd4864bb009821bd333b069de37f6daa45bf6 328634 kadu-mime-tex_2.1-1_amd64.deb
Checksums-Sha256:
 726769057b8029168937239298dab9ed3b091e48e6b9ef2ca252fb7806d05568 2302 
kadu-mime-tex_2.1-1.dsc
 ae586b1a027817dc4f1d27d99f82287930dbcd08c942ac4f2d28ebb45af6e9cc 563331 
kadu-mime-tex_2.1.orig.tar.bz2
 a3be358c43bed0486b8d7fd072acbbde6f3d9848b448cb8a84566f8b3239b05a 2692 
kadu-mime-tex_2.1-1.debian.tar.xz
 44dd3613b5b1bca49f894c5f606dcfa6e59220d982e8a40522283c295e665f68 328634 
kadu-mime-tex_2.1-1_amd64.deb
Files:
 15a6365f18e01bb9d531627af0b42a62 2302 libs optional kadu-mime-tex_2.1-1.dsc
 cfea5813582ced56f52c186030c89e5b 563331 libs optional 
kadu-mime-tex_2.1.orig.tar.bz2
 068554f058ab4776f44e65227674dde8 2692 libs optional