Bug#867541: please build ruby binding of grpc

[Pirate Praveen]

On Tue, 1 Aug 2017 22:00:28 +0530 Pirate Praveen
 wrote:> I was able to build and make tests
pass for grpc after adding this patch
> (attached).

I'm planning to NMU this patch, please review/upload if you like.

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=867541;filename=add-wrap-memcpy-flags.diff;msg=89



signature.asc
Description: OpenPGP digital signature

Processed: reassign 872058 to src:linux, forcibly merging 869511 872058

[Debian Bug Tracking System]

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

> reassign 872058 src:linux
Bug #872058 {Done: Ben Hutchings } 
[linux-headers-4.11.0-2-all] linux-headers-4.11.0-2-all: impossible to install 
due to version incompatibility with common header package
Bug reassigned from package 'linux-headers-4.11.0-2-all' to 'src:linux'.
No longer marked as found in versions linux/4.11.11-1.
No longer marked as fixed in versions 4.12.6-1.
> forcemerge 869511 872058
Bug #869511 {Done: Ben Hutchings } [src:linux] linux: 
binNMU-unsafe dependency on linux-headers-*-common
Bug #869670 {Done: Ben Hutchings } [src:linux] Depends: 
linux-headers-4.11.0-2-common ... but it is not going to be installed
Bug #869824 {Done: Ben Hutchings } [src:linux] missing 
package
Bug #870132 {Done: Ben Hutchings } [src:linux] 
linux-headers-amd64 broken, can't install
Bug #870298 {Done: Ben Hutchings } [src:linux] 
4.11.0-2-amd64 headers cannot be installed
Bug #872058 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.11.0-2-all: impossible to install due to version 
incompatibility with common header package
865614 was blocked by: 869511 870298 869824 870132 869670 867257
865614 was not blocking any bugs.
Added blocking bug(s) of 865614: 872058
866389 was blocked by: 869602 826471 866317 869383 869139 865033 869576 866934 
826502 865034 826505 865477 866315 869583 827640 866944 869670 865020 869579 
869824 870132 866978 826497 869418 865045 867213 870298 809352 867514 826473 
867046 865898 865380 869504 869578 869436 867984 865893 869580 865482 865224 
869357 869511 826489 867210 869433 865888
866389 was not blocking any bugs.
Added blocking bug(s) of 866389: 872058
Marked as fixed in versions linux/4.12.6-1.
The source linux and version 4.11.11-1+b1 do not appear to match any binary 
packages
Marked as found in versions linux/4.11.11-1+b1 and linux/4.11.11-1.
Added tag(s) newcomer.
Bug #869670 {Done: Ben Hutchings } [src:linux] Depends: 
linux-headers-4.11.0-2-common ... but it is not going to be installed
Bug #869824 {Done: Ben Hutchings } [src:linux] missing 
package
Bug #870132 {Done: Ben Hutchings } [src:linux] 
linux-headers-amd64 broken, can't install
Bug #870298 {Done: Ben Hutchings } [src:linux] 
4.11.0-2-amd64 headers cannot be installed
Merged 869511 869670 869824 870132 870298 872058
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865614
866389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866389
869511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869511
869670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869670
869824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869824
870132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870132
870298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870298
872058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871906: mongodb FTBFS on arm64: test failure

[Apollon Oikonomopoulos]

On 15:01 Sat 12 Aug , Adrian Bunk wrote:
> [executor:db_test] 2017-08-12T00:40:01.112+ Summary: 11 test(s) 
> ran in 40.28 seconds (10 succeeded, 48 were skipped, 1 failed, 0 
> errored)
> The following tests failed (with exit code):
> ExtensionsCallbackRealTest (-11)

Se, at least the ExtensionsCallbackRealTest and js suites are 
segfaulting on arm64. The relevant backtrace is:

(gdb) bt
#0  0xabf92ae0 in js::gc::Cell::storeBuffer (this=) at 
src/third_party/mozjs-38/extract/js/src/gc/Heap.h:1237
#1  js::HeapSlot::post (kind=js::HeapSlot::Slot, target=..., slot=60, 
owner=0xb0322060, this=0x9c03ac90) at 
src/third_party/mozjs-38/extract/js/src/gc/Barrier.h:911
#2  js::HeapSlot::set (v=..., slot=60, kind=js::HeapSlot::Slot, 
owner=0xb0322060, this=) at 
src/third_party/mozjs-38/extract/js/src/gc/Barrier.h:890
#3  js::NativeObject::setSlot (this=0xb0322060, slot=60, value=...) at 
src/third_party/mozjs-38/extract/js/src/vm/NativeObject.h:769
#4  0xac2f60dc in js::GlobalObject::setPrototype (value=..., 
key=JSProto_Object, this=)
at src/third_party/mozjs-38/extract/js/src/vm/GlobalObject.h:168
#5  js::GlobalObject::resolveConstructor (cx=0x9c015870, global=..., 
key=) at 
src/third_party/mozjs-38/extract/js/src/vm/GlobalObject.cpp:157
#6  0xac2f637c in js::GlobalObject::ensureConstructor 
(cx=cx@entry=0x9c015870, global=..., global@entry=..., 
key=key@entry=JSProto_Object)
at src/third_party/mozjs-38/extract/js/src/vm/GlobalObject.cpp:95
#7  0xabfb3b10 in js::GlobalObject::getOrCreateObjectPrototype 
(cx=0x9c015870, this=)
at src/third_party/mozjs-38/extract/js/src/vm/GlobalObject.h:326
#8  CreateArrayPrototype (cx=0x9c015870, key=) at 
src/third_party/mozjs-38/extract/js/src/jsarray.cpp:3249
#9  0xac2f7314 in InitBareBuiltinCtor (cx=cx@entry=0x9c015870, 
global=global@entry=..., protoKey=protoKey@entry=JSProto_Array)
at src/third_party/mozjs-38/extract/js/src/vm/GlobalObject.cpp:349
#10 0xac2f74d8 in js::GlobalObject::initSelfHostingBuiltins 
(cx=cx@entry=0x9c015870, global=global@entry=...,
builtins=builtins@entry=0xac9b8620 ) at 
src/third_party/mozjs-38/extract/js/src/vm/GlobalObject.cpp:386
#11 0xac0683c0 in JSRuntime::createSelfHostingGlobal 
(cx=cx@entry=0x9c015870) at 
src/third_party/mozjs-38/extract/js/src/vm/SelfHosting.cpp:1041
#12 0xac068508 in JSRuntime::initSelfHosting 
(this=this@entry=0x9c017790, cx=cx@entry=0x9c015870)
at src/third_party/mozjs-38/extract/js/src/vm/SelfHosting.cpp:1065
#13 0xac220e14 in js::NewContext (rt=0x9c017790, 
stackChunkSize=stackChunkSize@entry=8192) at 
src/third_party/mozjs-38/extract/js/src/jscntxt.cpp:126
#14 0xac220eac in JS_NewContext (rt=, 
stackChunkSize=stackChunkSize@entry=8192) at 
src/third_party/mozjs-38/extract/js/src/jsapi.cpp:569
#15 0xabebfed8 in mongo::mozjs::MozJSImplScope::MozRuntime::MozRuntime 
(this=0x9c00ebb0, engine=) at 
src/mongo/scripting/mozjs/implscope.cpp:288
#16 0xabec0044 in mongo::mozjs::MozJSImplScope::MozJSImplScope 
(this=0x9c00eb10, engine=0xaca69da0) at 
src/mongo/scripting/mozjs/implscope.cpp:347
#17 0xabee0154 in mongo::mozjs::MozJSProxyScope::implThread 
(arg=0xacd87060) at src/mongo/scripting/mozjs/proxyscope.cpp:330
#18 0xabeaad78 in nspr::Thread::ThreadRoutine (arg=0xacabedd0) at 
src/mongo/scripting/mozjs/PosixNSPR.cpp:56
#19 0xb78bf47c in std::execute_native_thread_routine 
(__p=0xacd86e30) at ../../../../../src/libstdc++-v3/src/c++11/thread.cc:83
#20 0xb770e0a0 in start_thread (arg=0xb78bf460 
) at pthread_create.c:335
#21 0xb7685e7c in thread_start () at 
../sysdeps/unix/sysv/linux/aarch64/clone.S:77

All other threads are blocked in pthread_cond_wait() et al.

It appears to be spidermonkey-gc-related, although I can't say much 
more. I'm afraid I won't be able to do much on this issue for the next 2 
weeks or so.

Regards,
Apollon

Bug#872058: marked as done (linux-headers-4.11.0-2-all: impossible to install due to version incompatibility with common header package)

[Debian Bug Tracking System]

Your message dated Mon, 14 Aug 2017 02:32:59 +0100
with message-id <1502674379.3688.8.ca...@decadent.org.uk>
and subject line Re: Bug#872058: linux-headers-4.11.0-2-all: impossible to 
install due to version incompatibility with common header package
has caused the Debian Bug report #872058,
regarding linux-headers-4.11.0-2-all: impossible to install due to version 
incompatibility with common header package
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.)


-- 
872058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-4.11.0-2-all
Version: 4.11.11-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the current version of the package is uninstallable because it depends
on linux-headers-4.11.0-2-common (=4.11.11-1+b1), but version 4.11.11-1
is present in the repository.

This bug affects all platform dependent header file packages.

Kind regards,
Matteo

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

Kernel: Linux 4.11.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 4.12.6-1

Just fixed this.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
  - John Lennon



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

Bug#868610: marked as done (apt-listdifferences FTBFS: 1 out of 4 hunks FAILED)

[Debian Bug Tracking System]

Your message dated Mon, 14 Aug 2017 00:33:57 +
with message-id 
and subject line Bug#868610: fixed in apt-listdifferences 1.20170813
has caused the Debian Bug report #868610,
regarding apt-listdifferences FTBFS: 1 out of 4 hunks 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.)


-- 
868610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-listdifferences
Version: 1.20161219
Severity: serious
Tags: buster sid

Some recent change in unstable makes apt-listdifferences FTBFS:

https://tests.reproducible-builds.org/debian/history/apt-listdifferences.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apt-listdifferences.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/apt-listdifferences-1.20161219'
patch /usr/bin/colordiff colordiff-git.patch -o colordiff-git   
File /usr/bin/colordiff is read-only; trying to patch anyway
patching file colordiff-git (read from /usr/bin/colordiff)
Hunk #1 succeeded at 7 with fuzz 2.
Hunk #3 FAILED at 166.
Hunk #4 succeeded at 516 (offset 8 lines).
1 out of 4 hunks FAILED -- saving rejects to file colordiff-git.rej
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: apt-listdifferences
Source-Version: 1.20170813

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated apt-listdifferences 
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, 13 Aug 2017 17:28:57 +
Source: apt-listdifferences
Binary: apt-listdifferences
Architecture: source
Version: 1.20170813
Distribution: unstable
Urgency: medium
Maintainer: Michael Gilbert 
Changed-By: Michael Gilbert 
Description:
 apt-listdifferences - source differences notification tool
Closes: 868610
Changes:
 apt-listdifferences (1.20170813) unstable; urgency=medium
 .
   * Update to debhelper 10.
   * Update copyright dates.
   * Update standards version.
   * Use colordiff's new built in git color schema (closes: #868610).
Checksums-Sha1:
 c322194aacc787f5d72d703a067e2be213a736d5 2227 
apt-listdifferences_1.20170813.dsc
 6a838b26a2b7a814255d4f250cb15d1ea12d2d6e 12340 
apt-listdifferences_1.20170813.tar.xz
 280432357828325d68ebdb0321323e29744489c1 6134 
apt-listdifferences_1.20170813_source.buildinfo
Checksums-Sha256:
 fd52b1e0476b7f60e66837eeff7511bc99371d9ec416f26183ae025853ccebf3 2227 
apt-listdifferences_1.20170813.dsc
 3e94f39618d691bea02500a2841bfe6a37dd85fbe2dad3a947aea837b803e739 12340 
apt-listdifferences_1.20170813.tar.xz
 d50ac44f17f12a47e4aca739b697c4247ad6467a2b5c00360502f17b3c039a00 6134 
apt-listdifferences_1.20170813_source.buildinfo
Files:
 9f2b0d7993788705a9a52f6d00e04a90 2227 utils extra 
apt-listdifferences_1.20170813.dsc
 9d5cc4ffe438b10b9e5d104fccf3aace 12340 utils extra 
apt-listdifferences_1.20170813.tar.xz
 40b29c6c4afd3561443f680f716da8ab 6134 utils extra 
apt-listdifferences_1.20170813_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAlmQ6m8ACgkQuNayzQLW
9HNcqiAAq9K/FD1DQIAxuzw33IY51QYrXFeFitKnrzTytQSIRqaW9LulFwG77U/a
tYTzOZZ2QdA5wENe28PZU1oAY+toEFRHBgxVwfHeTrzyXaWPpJdo29cxwZMp84L6
i7/LSphD8kFxr/TlBg6OO7pksw0DrdNOBX6bN13CB2hQjDva0oyUSd+LI3/Q7IvZ
DJeUt7y9h0cytERqygj/e+LvGu1Zm58s88AfTorY2ep1TR1jg6R2iIxqyTT2zRKz
GicvO11nvJjJHtIVG40Z+dwBRNTKcZXYk2sMPlspgXYU7l07zD826KIowSXz88c8
Pyd/vv0MkdEJkkRsJEjlBbmyPyhUnd1pJJxcb7N85lHeZNI+UKlE9KoSIvCBVXE4
lkgu95Z8IOd38sPyxcRjVP2VB+roPYf4mWZ8tWgUbmwJ1geSooQEP4gx/yvaB5Yy
RfsJ/rLCsiGZj8nhIb1DwGQGQx5+ugF0l+UdDgvBlTUyvorc/+1SYSe50RG65OFv
g+Gq5iR1LQC5P4u3idEcg06cHvyIoFfvNuWetg4XdIf8/KIzzGKZGR0WDTuGGGTs
gPv4692JaDrpxC8Am5/Pm9vBetcKAbQfJvhyM/ltZ6hDCKObOuPnavaoG7bj184f

Bug#872058: linux-headers-4.11.0-2-all: impossible to install due to version incompatibility with common header package

[Schiavon]

Package: linux-headers-4.11.0-2-all
Version: 4.11.11-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the current version of the package is uninstallable because it depends
on linux-headers-4.11.0-2-common (=4.11.11-1+b1), but version 4.11.11-1
is present in the repository.

This bug affects all platform dependent header file packages.

Kind regards,
Matteo

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

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

Bug#871357: packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at /usr/share/perl5/Locale/Po4a/TransTractor.pm line 6

[Martin Quinson]

On Sun, Aug 13, 2017 at 12:25:54PM -0400, gregor herrmann wrote:

> What po4a could maybe do is to mention in the documentation that the
> string in "position=something" in addendums will be interpreted as a
> Perl regexp later.

It's already the case:

position (mandatory)
a Perl regexp. The addendum will be placed near the line matching
this regexp. Note that we're speaking about the translated
document here, not the original. If more than a line match this
expression (or none), the addition will fail. It is indeed better
to report an error than inserting the addendum at the wrong
location. 

(I just added "Perl" in the first sentence, but the doc is otherwise
unchanged) If it's not explicit enough, please tell me how I could
improve it.

Thanks, Mt.

-- 
If Java had true garbage collection, most programs would delete
themselves upon execution.   -- Robert Sewell


signature.asc
Description: PGP signature

Bug#801975: linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing drive but mdadm doesn't set this drive failing

[Ben Hutchings]

Control: reassign -1 src:linux 3.16.7-ckt11-1
Control: tag -1 moreinfo

I'm sorry you didn't receive a response to this earlier.  The bug
tracking system didn't properly handle binary packages that only exist
in backports suites, so your report was not sent to the linux
maintainers.  It appears that that has been fixed, as your report now
shows up in a list of bugs for the linux source package.

Were you ever able to determine how to trigger this data loss?  Did you
find a fix?

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.



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

Processed: Re: linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing drive but mdadm doesn't set this drive failing

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 3.16.7-ckt11-1
Bug #801975 [linux-image-3.16.0-0.bpo.4-amd64] 
linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing drive but mdadm doesn't 
set this drive failing
Bug reassigned from package 'linux-image-3.16.0-0.bpo.4-amd64' to 'src:linux'.
No longer marked as found in versions linux/3.16.7-ckt11-1~bpo70+1.
Ignoring request to alter fixed versions of bug #801975 to the same values 
previously set
Bug #801975 [src:linux] linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing 
drive but mdadm doesn't set this drive failing
Marked as found in versions linux/3.16.7-ckt11-1.
> tag -1 moreinfo
Bug #801975 [src:linux] linux-image-3.16.0-0.bpo.4-amd64: pm80xx report failing 
drive but mdadm doesn't set this drive failing
Added tag(s) moreinfo.

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

Bug#872055: marked as done (linux-image-amd64: depends on a package that is no longer installable)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 22:48:58 +
with message-id 
and subject line Bug#872055: fixed in linux-latest 84
has caused the Debian Bug report #872055,
regarding linux-image-amd64: depends on a package that is no longer installable
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.)


-- 
872055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 4.11+83
Severity: grave
Justification: renders package unusable

linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is
no longer installable (bug 869511). But since this bug 869511 has
been fixed in linux/4.12.6-1 only and has been closed, it seems
that linux-image-4.11.0-2-amd64 will never be fixed, and that
linux-image-amd64 should depend on linux-image-4.12.0-1-amd64
(already available) ASAP.

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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.11.0-2-amd64  4.11.11-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux-latest
Source-Version: 84

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux-latest 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, 13 Aug 2017 23:16:51 +0100
Source: linux-latest
Binary: linux-source linux-doc linux-perf linux-image-alpha-generic 
linux-headers-alpha-generic linux-image-alpha-generic-dbg linux-image-alpha-smp 
linux-headers-alpha-smp linux-image-alpha-smp-dbg linux-image-amd64 
linux-headers-amd64 linux-image-amd64-dbg linux-image-arm64 linux-headers-arm64 
linux-image-arm64-dbg linux-image-marvell linux-headers-marvell 
linux-image-marvell-dbg linux-image-armmp linux-headers-armmp 
linux-image-armmp-dbg linux-image-armmp-lpae linux-headers-armmp-lpae 
linux-image-armmp-lpae-dbg linux-image-parisc linux-headers-parisc 
linux-image-parisc-dbg linux-image-parisc64-smp linux-headers-parisc64-smp 
linux-image-parisc64-smp-dbg linux-image-686 linux-headers-686 
linux-image-686-dbg linux-image-686-pae linux-headers-686-pae 
linux-image-686-pae-dbg linux-image-m68k linux-headers-m68k 
linux-image-m68k-dbg linux-image-4kc-malta linux-headers-4kc-malta 
linux-image-4kc-malta-dbg linux-image-5kc-malta linux-headers-5kc-malta 
linux-image-5kc-malta-dbg
 linux-image-octeon linux-headers-octeon linux-image-octeon-dbg 
linux-image-loongson-3 linux-headers-loongson-3 linux-image-loongson-3-dbg 
linux-image-powerpc linux-headers-powerpc linux-image-powerpc-dbg 
linux-image-powerpc-smp linux-headers-powerpc-smp linux-image-powerpc-smp-dbg 
linux-image-powerpc64 linux-headers-powerpc64 linux-image-powerpc64-dbg 
linux-image-powerpcspe linux-headers-powerpcspe linux-image-powerpcspe-dbg 
linux-image-powerpc64le linux-headers-powerpc64le linux-image-powerpc64le-dbg 
linux-image-s390x linux-headers-s390x linux-image-s390x-dbg linux-image-sh7751r 
linux-headers-sh7751r linux-image-sh7751r-dbg linux-image-sh7785lcr 
linux-headers-sh7785lcr linux-image-sh7785lcr-dbg linux-image-sparc64 
linux-headers-sparc64 linux-image-sparc64-dbg linux-image-sparc64-smp 
linux-headers-sparc64-smp
 linux-image-sparc64-smp-dbg
Architecture: source
Version: 84
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description:
 linux-doc  - Linux kernel 

Processed: severity of 871445 is important ...

[Debian Bug Tracking System]

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

> severity 871445 important
Bug #871445 [src:linux] linux-image-4.9.0-3-amd64: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
Severity set to 'important' from 'critical'
> retitle 871445 Soft lockup in vmw_pvscsi driver during package installation
Bug #871445 [src:linux] linux-image-4.9.0-3-amd64: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
Changed Bug title to 'Soft lockup in vmw_pvscsi driver during package 
installation' from 'linux-image-4.9.0-3-amd64: soft lockup - CPU#0 stuck for 
22s! [swapper/0:0]'.
> thanks
Stopping processing here.

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

Processed: tagging 869406, severity of 869406 is important

[Debian Bug Tracking System]

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

> tags 869406 - ipv6
Bug #869406 [src:linux] linux-image-4.9.0-3-amd64: Various USB Wifi adapters 
don't work after upgrade to Stretch (Installing new kernel)
Removed tag(s) ipv6.
> severity 869406 important
Bug #869406 [src:linux] linux-image-4.9.0-3-amd64: Various USB Wifi adapters 
don't work after upgrade to Stretch (Installing new kernel)
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#790201: marked as done (geany-plugins: depends on libwebkitgtk-1.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 22:34:00 +
with message-id 
and subject line Bug#790201: fixed in geany-plugins 1.31+dfsg-1.1
has caused the Debian Bug report #790201,
regarding geany-plugins: depends on libwebkitgtk-1.0-0 which is deprecated
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.)


-- 
790201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geany-plugins
Severity: important
Tags: sid stretch
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

geany-plugins depends on libwebkitgtk-1.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37. geany-plugins should be ported to the
new webkitgtk version so we can remove the old, unmaintained one.

As an intermediate step you can port geany-plugins to
libwebkitgtk-3.0-0, which has a similar API to libwebkitgtk-1.0-0 but
is based on GTK+ 3.0. Thus you'd be porting geany-plugins to GTK+ 3.0
first, using libwebkitgtk-3.0-0, and you could then port to
libwebkit2gtk-4.0-37 later. But note that libwebkitgtk-3.0-0 is also
deprecated.

Please try to do this before the Stretch release as we're going to
try to remove libwebkitgtk-1.0-0 this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing libwebkitgtk-1.0-0 completely.

If you have any question don't hesitate to ask.

Emilio 
--- End Message ---
--- Begin Message ---
Source: geany-plugins
Source-Version: 1.31+dfsg-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated geany-plugins 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, 30 Jul 2017 23:54:55 +0300
Source: geany-plugins
Binary: geany-plugins geany-plugins-common geany-plugin-addons 
geany-plugin-autoclose geany-plugin-automark geany-plugin-codenav 
geany-plugin-commander geany-plugin-ctags geany-plugin-debugger 
geany-plugin-defineformat geany-plugin-doc geany-plugin-extrasel 
geany-plugin-gendoc geany-plugin-geniuspaste geany-plugin-gproject 
geany-plugin-git-changebar geany-plugin-insertnum geany-plugin-latex 
geany-plugin-lipsum geany-plugin-lua geany-plugin-lineoperations 
geany-plugin-macro geany-plugin-miniscript geany-plugin-multiterm 
geany-plugin-overview geany-plugin-numberedbookmarks 
geany-plugin-pairtaghighlighter geany-plugin-pg geany-plugin-pohelper 
geany-plugin-prj geany-plugin-projectorganizer geany-plugin-py 
geany-plugin-scope geany-plugin-sendmail geany-plugin-tableconvert 
geany-plugin-vc geany-plugin-prettyprinter geany-plugin-shiftcolumn 
geany-plugin-spellcheck geany-plugin-treebrowser geany-plugin-updatechecker 
geany-plugin-xmlsnippets
Architecture: source
Version: 1.31+dfsg-1.1
Distribution: unstable
Urgency: low
Maintainer: Geany Packaging Team 
Changed-By: Adrian Bunk 
Description:
 geany-plugin-addons - miscellaneous plugins for Geany
 geany-plugin-autoclose - auto-closing plugin for Geany
 geany-plugin-automark - auto-mark plugin for Geany
 geany-plugin-codenav - code navigation plugin for Geany
 geany-plugin-commander - command panel plugin for Geany
 geany-plugin-ctags - ctags plugin for Geany
 geany-plugin-debugger - debugger plugin for Geany
 geany-plugin-defineformat - on-the-fly #define prettyprinter plugin for Geany
 geany-plugin-doc - documentation plugin for Geany
 geany-plugin-extrasel - extra selection plugin for Geany
 geany-plugin-gendoc - documentation generation plugin for Geany
 geany-plugin-geniuspaste - GeniusPaste plugin for Geany
 geany-plugin-git-changebar - git change bar plugin for Geany
 geany-plugin-gproject - transitional dummy package for 
geany-plugin-projectorganizer
 geany-plugin-insertnum - number inserting plugin for Geany
 geany-plugin-latex - improved LaTeX support plugin for Geany
 geany-plugin-lineoperations - Line 

Processed: severity of 869623 is important

[Debian Bug Tracking System]

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

> severity 869623 important
Bug #869623 [src:linux] linux-image-4.9.0-3-amd64: Stretch does not boot with 
linux-image-4.9.0-3-amd64,   linux-image-3.16.0-4-amd64  does boot.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#868956: libmspack: CVE-2017-11423

[Stuart Caie]

For your information, libmspack 0.6alpha has now been released.

On 06/08/17 20:22, Sebastian Andrzej Siewior wrote:

On 2017-08-06 10:22:11 [+0100], Stuart Caie wrote:

Commited a fix: 
https://github.com/kyz/libmspack/commit/17038206fcc384dcee6dd9e3a75f08fd3ddc6a38

I'll put out a release in the near future.

thank you Stuart.
Marc do plan you upload something to unstable/security soon, wait for a
new release or would you prefer someone else to NMU it with this
change?


Regards
Stuart

Sebastian

Bug#869511: dependency on linux-headers-*-common

[Vincent Lefevre]

On 2017-08-13 23:36:53 +0200, Vincent Lefevre wrote:
> On 2017-08-13 14:40:12 -0600, Gustavo Castro wrote:
> > The "linux-headers-4.11.0-2-common" fault is uncorrected?
> 
> Not on my machine. It is still not possible to upgrade.

I assume that since this bug has been closed and marked as fixed
in linux/4.12.6-1, I assume that the linux-*-4.11.0-2-* packages
will never be fixed. So, I've reported a bug against
linux-image-amd64, so that it depends on linux-image-4.12.0-1-amd64
ASAP.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#872055: linux-image-amd64: depends on a package that is no longer installable

[Vincent Lefevre]

On 2017-08-13 23:49:21 +0200, Vincent Lefevre wrote:
> linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is
> no longer installable (bug 869511). But since this bug 869511 has
> been fixed in linux/4.12.6-1 only and has been closed, it seems
> that linux-image-4.11.0-2-amd64 will never be fixed, and that
> linux-image-amd64 should depend on linux-image-4.12.0-1-amd64
> (already available) ASAP.

Actually that the corresponding headers file that it no longer
installable. But this file is needed by many users to be able
to build some drivers...

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#872055: linux-image-amd64: depends on a package that is no longer installable

[Vincent Lefevre]

Package: linux-image-amd64
Version: 4.11+83
Severity: grave
Justification: renders package unusable

linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is
no longer installable (bug 869511). But since this bug 869511 has
been fixed in linux/4.12.6-1 only and has been closed, it seems
that linux-image-4.11.0-2-amd64 will never be fixed, and that
linux-image-amd64 should depend on linux-image-4.12.0-1-amd64
(already available) ASAP.

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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.11.0-2-amd64  4.11.11-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Processed: Python3.6 blocker: automake

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 872052
Bug #866335 [release.debian.org] transition: python3-defaults
866335 was blocked by: 866575
866335 was not blocking any bugs.
Added blocking bug(s) of 866335: 872052
> affects 872052 src:imagemagick
Bug #872052 [automake] [automake] Lack of python3.6 support
Added indication that 872052 affects src:imagemagick

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

Bug#869511: dependency on linux-headers-*-common

[Vincent Lefevre]

On 2017-08-13 14:40:12 -0600, Gustavo Castro wrote:
> The "linux-headers-4.11.0-2-common" fault is uncorrected?

Not on my machine. It is still not possible to upgrade.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: reassign 865633 to src:spice-gtk

[Debian Bug Tracking System]

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

> reassign 865633 src:spice-gtk
Bug #865633 [virt-viewer] can't drag windows or click "Activities" in GNOME 3 
guest
Bug reassigned from package 'virt-viewer' to 'src:spice-gtk'.
No longer marked as found in versions virt-viewer/5.0-1.
Ignoring request to alter fixed versions of bug #865633 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#865633: [Pkg-libvirt-maintainers] Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Guido Günther]

control: ressign -1 src:spice-gtk
control: affects -1 virt-viewer

Hi,
On Sun, Aug 13, 2017 at 10:17:39AM +0200, Petter Reinholdtsen wrote:
> This RC issue has caused virt-viewer to be thrown out of testing.  Anyone
> got any idea how to fix it?

This slipped througk. I wonder how this ended up on virt-viewer anyway
since it's reproducible for the submitter with spicy:

Daniel Pocock  wrote:
>> I also tried the spicy client instead of virt-viewer, it has the bug too.

so reassigning.
Cheers,
 -- Guido

Processed (with 1 error): Re: [Pkg-libvirt-maintainers] Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Debian Bug Tracking System]

Processing control commands:

> ressign -1 src:spice-gtk
Unknown command or malformed arguments to command.

> affects -1 virt-viewer
Bug #865633 [virt-viewer] can't drag windows or click "Activities" in GNOME 3 
guest
Added indication that 865633 affects virt-viewer

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

Bug#871907: marked as done (praat FTBFS on non-amd64)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 20:55:55 +
with message-id 
and subject line Bug#871907: fixed in praat 6.0.30-3
has caused the Debian Bug report #871907,
regarding praat FTBFS on non-amd64
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.)


-- 
871907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: praat
Version: 6.0.30-1
Severity: serious
Tags: patch

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

...
g++ -std=c++11 -DNO_GUI -DNO_NETWORK -D_FILE_OFFSET_BITS=64 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/cairo -I/usr/include/pango-1.0 -DUNIX -Dlinux 
-Werror=missing-prototypes -Werror=implicit -Wreturn-type -Wunused 
-Wunused-parameter -Wuninitialized -O3 -g1 -pthread -Wshadow -g -O2 
-fdebug-prefix-map=/<>/sys=. -fstack-protector-strong -Wformat 
-Werror=format-security -I ../sys -I ../num -I ../dwsys -I ../kar -I 
../external/portaudio -I ../external/flac -I ../external/mp3  -c -o 
melder_audio.o melder_audio.cpp
In file included from /usr/include/glib-2.0/glib/galloca.h:32:0,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/pango-1.0/pango/pango-coverage.h:25,
 from /usr/include/pango-1.0/pango/pango-font.h:25,
 from /usr/include/pango-1.0/pango/pango-attributes.h:25,
 from /usr/include/pango-1.0/pango/pango.h:25,
 from Gui.h:62,
 from melder_audio.cpp:46:
/usr/include/glib-2.0/glib/gtypes.h:32:10: fatal error: glibconfig.h: No such 
file or directory
 #include 
  ^~
compilation terminated.
: recipe for target 'melder_audio.o' failed
make[3]: *** [melder_audio.o] Error 1


Fix is attached.
Description: Use pkg-config for pangocairo cflags and libs
 Use pkg-config instead of hardcoding pangocairo cflags and libs
 (gives the proper location instead of x86_64-linux-gnu in the
  include search path even on non-amd64).
Author: Adrian Bunk 

--- praat-6.0.30.orig/makefiles/makefile.defs.linux.nogui
+++ praat-6.0.30/makefiles/makefile.defs.linux.nogui
@@ -7,7 +7,7 @@ CC = gcc -std=gnu99
 
 CXX = g++ -std=c++11
 
-CFLAGS = -DNO_GUI -DNO_NETWORK -D_FILE_OFFSET_BITS=64 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo 
-I/usr/include/pango-1.0 -DUNIX -Dlinux -Werror=missing-prototypes 
-Werror=implicit -Wreturn-type -Wunused -Wunused-parameter -Wuninitialized -O3 
-g1 -pthread
+CFLAGS = -DNO_GUI -DNO_NETWORK -D_FILE_OFFSET_BITS=64 `pkg-config --cflags 
pangocairo` -DUNIX -Dlinux -Werror=missing-prototypes -Werror=implicit 
-Wreturn-type -Wunused -Wunused-parameter -Wuninitialized -O3 -g1 -pthread
 
 CXXFLAGS = $(CFLAGS) -Wshadow
 
@@ -15,10 +15,10 @@ LINK = g++
 
 EXECUTABLE = praat_nogui
 
-LIBS = -lpangocairo-1.0 -lcairo -lpango-1.0 -lgobject-2.0 -lm -lpthread
+LIBS = `pkg-config --libs pangocairo` -lm -lpthread
 
 AR = ar
 RANLIB = ls
 ICON =
 MAIN_ICON =
 
--- End Message ---
--- Begin Message ---
Source: praat
Source-Version: 6.0.30-3

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

Debian distribution maintenance software
pp.
Rafael Laboissiere  (supplier of updated praat 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, 13 Aug 2017 04:00:07 -0300
Source: praat
Binary: praat
Architecture: source amd64
Version: 6.0.30-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Rafael Laboissiere 
Description:
 praat  - program for speech analysis and synthesis
Closes: 871907
Changes:
 praat (6.0.30-3) unstable; urgency=medium
 .
   * d/p/pangocairo-pkg-config.patch: New patch.
 This patch replaces d/p/use-gtk-pkg-config.patch and provides a better
 argument for the pkg-config invocation when building praat_nogui.
 Thanks to 

Bug#866694: marked as done (src:pythonmagick: FTBFS with python3.6 as a supported python3)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 20:56:02 +
with message-id 
and subject line Bug#866694: fixed in pythonmagick 0.9.17-1
has caused the Debian Bug report #866694,
regarding src:pythonmagick: FTBFS with python3.6 as a supported python3
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.)


-- 
866694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pythonmagick
Version: 0.9.14-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

With python3.6 as a supported python3 version, this package FTBFS:

checking for python with minimal version... 3.6
checking for a Python interpreter with version >= 3.6... none
configure: error: no suitable Python interpreter found

See [1].

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=pythonmagick=amd64=0.9.14-3%2Bb2=1498871134=0
--- End Message ---
--- Begin Message ---
Source: pythonmagick
Source-Version: 0.9.17-1

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated pythonmagick 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, 13 Aug 2017 17:22:42 +0200
Source: pythonmagick
Binary: python-pythonmagick python3-pythonmagick
Architecture: source
Version: 0.9.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Bastien Roucariès 
Description:
 python-pythonmagick - Object-oriented Python interface to ImageMagick
 python3-pythonmagick - Object-oriented Python 3 interface to ImageMagick
Closes: 866694
Changes:
 pythonmagick (0.9.17-1) unstable; urgency=medium
 .
   * Bug fix: "FTBFS with python3.6 as a supported python3", thanks to
 Scott Kitterman (Closes: #866694).
   * Use lastest autoconf-archive for some python macros.
   * Bump policy (no changes)
Checksums-Sha1:
 dc953384b2de5456ff5082f45d17746ef8fee2a5 2439 pythonmagick_0.9.17-1.dsc
 728e140ef90b5b1bb786121ec8e220625b44043c 271844 pythonmagick_0.9.17.orig.tar.xz
 2f63bc928d5a157b56d752770b5080d1bab99739 12656 
pythonmagick_0.9.17-1.debian.tar.xz
 471a7d7c5d4b302c6bb025a43f466cb5ea4a545a 12486 
pythonmagick_0.9.17-1_source.buildinfo
Checksums-Sha256:
 eef26b5e4d341a5f787824dfa6d6e03da1ab2f85cb2771036107467d32951edb 2439 
pythonmagick_0.9.17-1.dsc
 34aeaab51268432c25f68b36fbd5daca97c0d564cb61c761b018731516d0711e 271844 
pythonmagick_0.9.17.orig.tar.xz
 341687bb12499c7b65f0b10b45dfc5d472f7ca1a132b7e6ee796c2568eab5c3b 12656 
pythonmagick_0.9.17-1.debian.tar.xz
 18e92aa067fc6706cf61d7fcf3d6f7c90edabca0df57a14a1a8d7ac2d9ada430 12486 
pythonmagick_0.9.17-1_source.buildinfo
Files:
 a4876b1b9f10372311834cde9c22e46e 2439 python extra pythonmagick_0.9.17-1.dsc
 53b9442c6bcbbe539c47454527f127dc 271844 python extra 
pythonmagick_0.9.17.orig.tar.xz
 d634f62784bccf6bba3f31c0ca10ab2d 12656 python extra 
pythonmagick_0.9.17-1.debian.tar.xz
 7fcfe938e04ccdccbaf4c8acd5720e42 12486 python extra 
pythonmagick_0.9.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlmQtCkACgkQADoaLapB
CF+8wxAAnKkC4hRPCNyOLs1rlG8dxX0HChoUbD9/fDU8SGC5aEA34XIjL+B79GBC
chtguhGE3ZVRhKvI0UcUmdqU9Wbo6fp3sOE+bH1qFuEt7ImCiuZgI+dltGga7U3L
gJoMhMJY8EojhJyKtVmkqq298+4TyTcIJCKrc+zpVUbUs3KmPn4bZ488hBBHBMLq
nhuYIZXi7gFFcYR7/+dearTpYluyeQqnZh5DZFX/PLSsV78FFN4vxBGcD6a+VMGU
V4cv2XsNgDOOP+y+d7lomNYLoMsavrG2ZzjVPsu82wBJyqaR3YmYenKa6tE9nOS/
ZN5nmyhnUkXtVwRvdUpVAEUu46Sqr3g+i2m35IbV6zd7jcC2Srg+gjAP3LSbSK5D
IqLcMx3h9Rh7rAL07cDxwXb0D3ks6BSkJ4FUPPdR3a2WMIChraLYJiRT5QScPP8q
M1lqDykPTPquWHGTEM2y2UPbwfD8X2Mii5w/RkkTLaaF/89Q8aqwD9HFvv/6YxWW
uuDEna4cb1hZjJ7QVIIklS2xnugGNl8V99mgVOWay2A+S2wq2rguchXcEUhmlCW8
8k9sZQZlN1Q8HpIA6Uq0VDtZAj8PQ8z7uFhvjZWY3e2O5xJWtl7q50OYdS71CyVN
PD3POaLJoLLxZN2Rj+pf1JtrxgQk/kvB+L9+u3uIPSlQPdbwD6E=
=3JLL
-END PGP SIGNATURE End 

Bug#869511: dependency on linux-headers-*-common

[Gustavo Castro]

The "linux-headers-4.11.0-2-common" fault is uncorrected?

apt install linux-headers-$(uname -r)
Reading package list ... Done
Creating dependency tree
Reading the status information ... Done
Some packages could not be installed. This may mean that
You asked for an impossible situation or, if you are using the distribution
Unstable, that some necessary packages have not yet been created or are
Have taken from "Incoming".
The following information can help resolve the situation:

The following packages have unmet dependencies:
Linux-headers-4.11.0-2-amd64: Depends: linux-headers-4.11.0-2-common (= 
4.11.11-1 + b1) but will not install

E: Problems could not be corrected, you have retained broken packets.


Thanks

Processed: [automake] Lack of python3.6 support

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream
Bug #872052 [automake] [automake] Lack of python3.6 support
Added tag(s) upstream.

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

Processed: Make photutils bug pending

[Debian Bug Tracking System]

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

> forwarded 872011 https://github.com/astropy/photutils/pull/578
Bug #872011 [src:photutils] photutils FTBFS with pytest 3.2.0
Set Bug forwarded-to-address to 'https://github.com/astropy/photutils/pull/578'.
> tags 872011 pending
Bug #872011 [src:photutils] photutils FTBFS with pytest 3.2.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871986: marked as done (postgresql-9.6: PostgreSQL fails to start after upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 21:17:01 +0200
with message-id <20170813191701.xxwmt4er47z7l...@msg.df7cb.de>
and subject line Re: [Pkg-postgresql-public] Bug#871986: Bug#871986: 
postgresql-9.6: PostgreSQL fails to start after upgrade
has caused the Debian Bug report #871986,
regarding postgresql-9.6: PostgreSQL fails to start after upgrade
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.)


-- 
871986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-9.6
Version: 9.6.4-0+deb9u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Last night I upgraded "postgresql-9.6" to the most recent version
(went from 9.6.3-3 to 9.6.4-0+deb9u1).

As a part of the upgrade PostgreSQL was shut down, and it has not come
up since then.

% ls -lFNart /var/log/postgresql
totalt 16
-rw-r-  1 postgres adm   700 jul  2 06:25 postgresql-9.6-main.log.2.gz
-rw-r-  1 postgres adm   341 aug 13 06:25 postgresql-9.6-main.log.1
drwxrwxr-t  2 root postgres 4096 aug 13 06:25 ./
-rw-r-  1 postgres adm 0 aug 13 06:25 postgresql-9.6-main.log
drwxr-xr-x 10 root root 4096 aug 13 06:25 ../
% tail /var/log/postgresql/postgresql-9.6-main.log.1
2017-08-12 19:33:04 CEST [2060-2] LOG:  received fast shutdown request
2017-08-12 19:33:04 CEST [2060-3] LOG:  aborting any active transactions
2017-08-12 19:33:04 CEST [2065-2] LOG:  autovacuum launcher shutting down
2017-08-12 19:33:04 CEST [2062-1] LOG:  shutting down
2017-08-12 19:33:04 CEST [2060-4] LOG:  database system is shut down
%

I've tried "sudo service postgresql restart" without any visible effect.

/Jacob

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=da:da_DK:fo:fo_FO:nb:nb_NO:nn:nn_NO:no:no_NO:sv:sv_SE:sv_FI:en_GB:en_DK:en_AU:en:it:it_IT:is:is_IS:fr:fr_FR:de:de_DE:en_US
 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-9.6 depends on:
ii  libc6  2.24-11+deb9u1
ii  libgssapi-krb5-2   1.15-1
ii  libldap-2.4-2  2.4.44+dfsg-5
ii  libpam0g   1.1.8-3.6
ii  libpq5 9.6.4-0+deb9u1
ii  libssl1.1  1.1.0f-3
ii  libsystemd0232-25+deb9u1
ii  libxml22.9.4+dfsg1-2.2
ii  locales2.24-11+deb9u1
ii  postgresql-client-9.6  9.6.4-0+deb9u1
ii  postgresql-common  181
ii  ssl-cert   1.0.39
ii  tzdata 2017b-1

Versions of packages postgresql-9.6 recommends:
ii  postgresql-contrib-9.6  9.6.4-0+deb9u1
ii  sysstat 11.4.3-2

Versions of packages postgresql-9.6 suggests:
ii  locales-all  2.24-11+deb9u1

-- no debconf information
--- End Message ---
--- Begin Message ---
Re: Jacob Sparre Andersen 2017-08-13 
<051d907f-37cd-73ff-e55d-a84a3c955...@jacob-sparre.dk>
> Christoph Berg wrote:
> 
> > Is /etc/postgresql/9.6/main/start.conf set to "auto"?
> 
> No. :-(
> 
> It appears that I simply hadn't switched from "manual" to "auto" after I
> finished the upgrade from 9.4 (Jessie) to 9.6.
> 
> I'm sorry about filling trivial problems like that in the bug database.

No worries, thanks for reporting it. This is way better than the
reverse - having problems not fixed just because they happen to
everyone except the maintainer doesn't make sense :)

> > > I've tried "sudo service postgresql restart" without any visible effect.
> > 
> > postgresql.service is just a stub which forwards all actions to the
> > individual services like postgresql@9.6-main.service. Unfortunately
> > systemctl doesn't really relay any errors back if there's any.
> 
> Could "postgresql.service" be expanded such that running "service
> postgresql" will output a suggestion to use "systemctl" instead?

Using the "service" program to start/stop services is fine - what I
meant to say was that "service postgresql status" or "systemctl status
postgresql" (which are backed by /lib/systemd/system/postgresql.service)
won't output much, while "service postgresql@9.6-main status" (or via
systemctl) gives you the real information.

The idea to add a hint to the "postgresql status" output is
interesting. I'm not sure we can really put any text there, but I'll
investigate. Thanks for the idea!

Christoph--- End Message ---

Processed: Again re-assigning to astropy

[Debian Bug Tracking System]

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

> forwarded 871995 https://github.com/astropy/astropy/pull/6423
Bug #871995 [python-astropy] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #871999 [python-astropy] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872000 [python-astropy] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872006 [python-astropy] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872008 [python-astropy] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug #872010 [python-astropy] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/6423'.
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/6423'.
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/6423'.
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/6423'.
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/6423'.
Set Bug forwarded-to-address to 'https://github.com/astropy/astropy/pull/6423'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871995
871999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871999
872000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872000
872006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872006
872008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872008
872010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Again re-assigning to astropy

[Debian Bug Tracking System]

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

> reassign 871995 python-astropy 2.0.1-1
Bug #871995 [python-astropy] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #871999 [python-astropy] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872000 [python-astropy] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872006 [python-astropy] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872008 [python-astropy] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug #872010 [python-astropy] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Ignoring request to reassign bug #871995 to the same package
Ignoring request to reassign bug #871999 to the same package
Ignoring request to reassign bug #872000 to the same package
Ignoring request to reassign bug #872006 to the same package
Ignoring request to reassign bug #872008 to the same package
Ignoring request to reassign bug #872010 to the same package
Bug #871995 [python-astropy] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #871999 [python-astropy] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872000 [python-astropy] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872006 [python-astropy] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872008 [python-astropy] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug #872010 [python-astropy] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Marked as found in versions python-astropy/2.0.1-1.
Marked as found in versions python-astropy/2.0.1-1.
Marked as found in versions python-astropy/2.0.1-1.
Marked as found in versions python-astropy/2.0.1-1.
Marked as found in versions python-astropy/2.0.1-1.
Marked as found in versions python-astropy/2.0.1-1.
> tags 871995 pending
Bug #871995 [python-astropy] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #871999 [python-astropy] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872000 [python-astropy] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872006 [python-astropy] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872008 [python-astropy] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug #872010 [python-astropy] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871995
871999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871999
872000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872000
872006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872006
872008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872008
872010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#865633: [Pkg-libvirt-maintainers] Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Daniel Pocock]

On 13/08/17 10:17, Petter Reinholdtsen wrote:
> This RC issue has caused virt-viewer to be thrown out of testing.  Anyone
> got any idea how to fix it?
> 

I did a full reboot of the physical host and the guest VM and after that
I was able to connect successfully from virt-viewer on stretch.

This is not ideal though.  Has anybody else seen the issue?

Bug#868068: ([xserver-xorg-core] Upgrade from 2:1.16.4-1 to 2:1.16.4-1+deb8u1 loses keyboard and mouse)

[Fungi4All]

Intel 82Q35 Express Integrated Graphics Controller
Intel(R) Core(TM)2 Duo CPU E6550
lshw does not return anything about Haswell
lspci returns
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port (rev 
02)
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated 
Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated Graphics 
Controller (rev 02)
00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI 
Controller (rev 02)
00:03.2 IDE interface: Intel Corporation 82Q35 Express PT IDER Controller (rev 
02)
00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT Controller 
(rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network 
Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller 
(rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port 
SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)

lsusb
Bus 002 Device 004: ID 148f:2770 Ralink Technology, Corp. RT2770 Wireless 
Adapter
Bus 006 Device 003: ID 0461:4dbf Primax Electronics, Ltd
Bus 006 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

Bug#868068: [xserver-xorg-core] Loss of keyboard and mouse at Debian 9.1 ("Stretch" under AMD64), too.

[Kim Olsen]

Hi,

when running Debian-9.1 on an AMD64-machine with

xserver-xorg-core (2:1.19.2-1+deb9u1) and
xserver-common (2:1.19.2-1+deb9u1)

keyboard and mouse are freezing up sometimes, too.

Shutting down the PC or unplug/plug the USB-units
can't be a solution for a longer period!

Greetings

Kim Olsen

Bug#871810: cvs: CVE-2017-12836: CVS and ssh command injection

[Chris Lamb]

Hi Thorsten,

> […]

Thanks for uploading. I'll send the DLA announcement out now…


Regards,

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

Bug#872017: [Pkg-zsh-devel] Bug#872017: zsh-syntax-highlighting FTBFS with zsh 5.4.1-1

[Daniel Shahaf]

Control: tag -1 + fixed-upstream
Control: fixed -1 0.6.0~rc1-2

Adrian Bunk wrote on Sun, 13 Aug 2017 16:39 +0300:
> # alias
> /build/1st/zsh-syntax-highlighting-0.5.0/./highlighters/main/test-data/alias.zsh:32:
>  defining function based on alias `alias1'
> /build/1st/zsh-syntax-highlighting-0.5.0/./highlighters/main/test-data/alias.zsh:32:
>  parse error near `()'
> Bail out! Either 'PREBUFFER' or 'BUFFER' must be declared and non-blank
> Bail out! output on stderr

Fixed upstream in 9523d6d49cb3d4db5bd84c3cec6168a2057fe3ab, already in
experimental and due to be uploaded to sid soon.

To be clear, there is no bug in z-sy-h itself; this is entirely a test suite 
issue.

Thanks,

Daniel

Processed: Re: [Pkg-zsh-devel] Bug#872017: zsh-syntax-highlighting FTBFS with zsh 5.4.1-1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + fixed-upstream
Bug #872017 [src:zsh-syntax-highlighting] zsh-syntax-highlighting FTBFS with 
zsh 5.4.1-1
Added tag(s) fixed-upstream.
> fixed -1 0.6.0~rc1-2
Bug #872017 [src:zsh-syntax-highlighting] zsh-syntax-highlighting FTBFS with 
zsh 5.4.1-1
Marked as fixed in versions zsh-syntax-highlighting/0.6.0~rc1-2.

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

Bug#872017: marked as pending

[Daniel Shahaf]

tag 872017 pending
thanks

Hello,

Bug #872017 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:


https://anonscm.debian.org/cgit/pkg-zsh/zsh-syntax-highlighting.git/commit/?id=93d31c2

---
commit 93d31c2496d3a5609f52320a8faff26c99d6bc98
Author: Daniel Shahaf 
Date:   Sun Aug 13 18:18:01 2017 +

d/changelog: #872017 will be fixed by the next upload.

It is already fixed in experimental 0.6.0~rc1-2.

diff --git a/debian/changelog b/debian/changelog
index d6b2ba5..a7f32df 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+zsh-syntax-highlighting (0.6.0~rc1-2+git) UNRELEASED; urgency=medium
+
+  * New upstream release.
+- Fixes test suite error on zsh>=5.4~.  (Closes: #872017)
+
+ -- Daniel Shahaf   Sun, 13 Aug 2017 18:16:12 +
+
 zsh-syntax-highlighting (0.6.0~rc1-2) experimental; urgency=medium
 
   * New upstream pre-release.

Bug#872039: initscripts: umountfs leaves /var mounted (rw)

[Elrond]

Package: initscripts
Version: 2.88dsf-59.9
Severity: serious
Tags: patch


Hi,


Reason for Severity=serious: This leaves /var (or other
filesystems) in an unclean state, so could possibly lead to
data loss!
(not to mention the lengthy fsck at every boot.)


umountfs in stretch changed the sed-calculation of
ROTECTED_MOUNTS. The new one includes /var on my system:

# sed -n ':a;/^[^ ]* \(\/\|\/usr\) /!{H;n;ba};{H;s/.*//;x;s/\n//;p}' 
/proc/mounts
/dev/root / ext2 rw,relatime,errors=continue 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=305176k,mode=755 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=10240k,nr_inodes=381118,mode=755 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=610340k 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/mapper/intvg1-sys_var /var ext2 rw,relatime,errors=continue 0 0
/dev/md3 /boot ext2 ro,relatime,errors=continue 0 0
/dev/mapper/intvg1-sys_usr /usr ext2 rw,relatime,errors=continue 0 0

The new sed was likely changed to include /usr in the list
of protected filesystems (it's remounted ro later).
But the new version basicly means (at least, I understand
it that way): Include all filesystems in ROTECTED_MOUNTS,
that are above the last mention of / or /usr.  While the
old one was about / only.


I propose to undo the sed changes and include /usr in the
specific list of filesystems to exclude from unmounting.

See attached patch.


Can you please try to include a fix in the next point
release of stretch?


Cheers

Elrond
--- umountfs.orig	2017-07-20 09:23:26.0 +0200
+++ umountfs	2017-08-13 19:24:16.0 +0200
@@ -17,7 +17,7 @@
 umask 022
 
 do_stop () {
-	PROTECTED_MOUNTS="$(sed -n ':a;/^[^ ]* \(\/\|\/usr\) /!{H;n;ba};{H;s/.*//;x;s/\n//;p}' /proc/mounts)"
+	PROTECTED_MOUNTS="$(sed -n ':a;/^[^ ]* \/ /!{H;n;ba};{H;s/.*//;x;s/\n//;p}' /proc/mounts)"
 	WEAK_MTPTS="" # be gentle, don't use force
 	REG_MTPTS=""
 	TMPFS_MTPTS=""
@@ -25,7 +25,7 @@
 	do
 		echo "$PROTECTED_MOUNTS" | grep -qs "^$DEV $MTPT " && continue
 		case "$MTPT" in
-		  /|/proc|/dev|/.dev|/dev/pts|/dev/shm|/dev/.static/dev|/proc/*|/sys|/sys/*|/run|/run/*|/dev/vcs)
+		  /|/usr|/proc|/dev|/.dev|/dev/pts|/dev/shm|/dev/.static/dev|/proc/*|/sys|/sys/*|/run|/run/*|/dev/vcs)
 			continue
 			;;
 		esac

Bug#853304: marked as done (alljoyn-core-1504: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 18:19:18 +
with message-id 
and subject line Bug#853304: fixed in alljoyn-core-1504 15.04b+dfsg.1-1
has caused the Debian Bug report #853304,
regarding alljoyn-core-1504: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:alljoyn-core-1504
Version: 15.04b-8
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/alljoyn-core-1504_15.04b-8_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
Install file: "services/about/cpp/inc/alljoyn/about/PropertyStoreProperty.h" as 
"build/linux/x86_64/release/dist/cpp/inc/alljoyn/about/PropertyStoreProperty.h"
Install file: "services/about/cpp/inc/alljoyn/about/AboutService.h" as 
"build/linux/x86_64/release/dist/cpp/inc/alljoyn/about/AboutService.h"
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AboutPropertyStoreImpl.o -c 
-Wall -Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -DNDEBUG 
-DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/about/cpp/src/AboutPropertyStoreImpl.cc
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AboutService.o -c -Wall 
-Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -DNDEBUG 
-DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/about/cpp/src/AboutService.cc
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AboutServiceApi.o -c -Wall 
-Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -DNDEBUG 
-DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/about/cpp/src/AboutServiceApi.cc
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AnnounceHandler.o -c -Wall 
-Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -DNDEBUG 
-DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 

Processed: Bug#872017 marked as pending

[Debian Bug Tracking System]

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

> tag 872017 pending
Bug #872017 [src:zsh-syntax-highlighting] zsh-syntax-highlighting FTBFS with 
zsh 5.4.1-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#870103: freeplane: a Java (knopflerfish) exception will prevent freeplane from starting

[Felix Natter]

hello Sophoklis,

unfortunately I cannot reproduce this, but I'll look into it.

Does that file exist (could be a permission problem...)?

Could you try to touch that file (as root) as a possible workaround?
If that doesn't work, try to "sudo cp" the attached "props.xargs" to
/usr/share/freeplane/fwdir/fwprops.xargs?

Cheers and Best Regards,
-- 
Felix Natter


props.xargs
Description: Binary data

Bug#869824: marked as done (missing package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 18:00:12 +
with message-id 
and subject line Bug#869511: fixed in linux 4.12.6-1
has caused the Debian Bug report #869511,
regarding missing package
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.)


-- 
869511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-amd64
Version: 4.11.0-2-amd64

this package is missing
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.12.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Sat, 12 Aug 2017 23:09:26 +0100
Source: linux
Binary: linux-source-4.12 linux-support-4.12.0-1 linux-doc-4.12 
linux-manual-4.12 linux-kbuild-4.12 linux-cpupower libcpupower1 libcpupower-dev 
linux-perf-4.12 libusbip-dev usbip hyperv-daemons linux-headers-4.12.0-1-common 
linux-libc-dev linux-headers-4.12.0-1-all linux-headers-4.12.0-1-all-alpha 
kernel-image-4.12.0-1-alpha-generic-di nic-modules-4.12.0-1-alpha-generic-di 
nic-wireless-modules-4.12.0-1-alpha-generic-di 
nic-shared-modules-4.12.0-1-alpha-generic-di 
serial-modules-4.12.0-1-alpha-generic-di 
usb-serial-modules-4.12.0-1-alpha-generic-di 
ppp-modules-4.12.0-1-alpha-generic-di pata-modules-4.12.0-1-alpha-generic-di 
cdrom-core-modules-4.12.0-1-alpha-generic-di 
scsi-core-modules-4.12.0-1-alpha-generic-di 
scsi-modules-4.12.0-1-alpha-generic-di loop-modules-4.12.0-1-alpha-generic-di 
btrfs-modules-4.12.0-1-alpha-generic-di ext4-modules-4.12.0-1-alpha-generic-di 
isofs-modules-4.12.0-1-alpha-generic-di jfs-modules-4.12.0-1-alpha-generic-di
 xfs-modules-4.12.0-1-alpha-generic-di fat-modules-4.12.0-1-alpha-generic-di 
md-modules-4.12.0-1-alpha-generic-di 
multipath-modules-4.12.0-1-alpha-generic-di 
usb-modules-4.12.0-1-alpha-generic-di 
usb-storage-modules-4.12.0-1-alpha-generic-di 
fb-modules-4.12.0-1-alpha-generic-di input-modules-4.12.0-1-alpha-generic-di 
event-modules-4.12.0-1-alpha-generic-di mouse-modules-4.12.0-1-alpha-generic-di 
nic-pcmcia-modules-4.12.0-1-alpha-generic-di 
pcmcia-modules-4.12.0-1-alpha-generic-di 
nic-usb-modules-4.12.0-1-alpha-generic-di 
sata-modules-4.12.0-1-alpha-generic-di crc-modules-4.12.0-1-alpha-generic-di 
crypto-modules-4.12.0-1-alpha-generic-di 
crypto-dm-modules-4.12.0-1-alpha-generic-di 
ata-modules-4.12.0-1-alpha-generic-di nbd-modules-4.12.0-1-alpha-generic-di 
squashfs-modules-4.12.0-1-alpha-generic-di 
virtio-modules-4.12.0-1-alpha-generic-di zlib-modules-4.12.0-1-alpha-generic-di 
fuse-modules-4.12.0-1-alpha-generic-di srm-modules-4.12.0-1-alpha-generic-di
 linux-image-4.12.0-1-alpha-generic linux-headers-4.12.0-1-alpha-generic 
linux-image-4.12.0-1-alpha-generic-dbg linux-image-4.12.0-1-alpha-smp 
linux-headers-4.12.0-1-alpha-smp linux-image-4.12.0-1-alpha-smp-dbg 
linux-headers-4.12.0-1-all-amd64 kernel-image-4.12.0-1-amd64-di 
nic-modules-4.12.0-1-amd64-di nic-wireless-modules-4.12.0-1-amd64-di 
nic-shared-modules-4.12.0-1-amd64-di serial-modules-4.12.0-1-amd64-di 
usb-serial-modules-4.12.0-1-amd64-di ppp-modules-4.12.0-1-amd64-di 
pata-modules-4.12.0-1-amd64-di cdrom-core-modules-4.12.0-1-amd64-di 
firewire-core-modules-4.12.0-1-amd64-di scsi-core-modules-4.12.0-1-amd64-di 
scsi-modules-4.12.0-1-amd64-di loop-modules-4.12.0-1-amd64-di 
btrfs-modules-4.12.0-1-amd64-di ext4-modules-4.12.0-1-amd64-di 
isofs-modules-4.12.0-1-amd64-di jfs-modules-4.12.0-1-amd64-di 
ntfs-modules-4.12.0-1-amd64-di xfs-modules-4.12.0-1-amd64-di 
fat-modules-4.12.0-1-amd64-di md-modules-4.12.0-1-amd64-di 
multipath-modules-4.12.0-1-amd64-di
 usb-modules-4.12.0-1-amd64-di usb-storage-modules-4.12.0-1-amd64-di 
pcmcia-storage-modules-4.12.0-1-amd64-di fb-modules-4.12.0-1-amd64-di 
input-modules-4.12.0-1-amd64-di event-modules-4.12.0-1-amd64-di 
mouse-modules-4.12.0-1-amd64-di 

Bug#870132: marked as done (linux-headers-amd64 broken, can't install)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 18:00:12 +
with message-id 
and subject line Bug#869511: fixed in linux 4.12.6-1
has caused the Debian Bug report #869511,
regarding linux-headers-amd64 broken, can't install
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.)


-- 
869511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-amd64
Version: 4.11+83
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer, linux-headers-amd64 depends on 4.11.0-2-amd64, wich depends on
4.11.0-2-common (version =4.11.11-1+b1), but only 4.11.11-1 is available on
Sid. In result, can't install headers to compile any third party module.

I can install linux-headers-common-4.11.11-1 and "force install" linux-
headers-4.11.0-2-amd64 with dpkg (downloading .deb and with --ignore-depends),
but apt tries to fix this situation removing the headers package on every
upgrade.



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

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

Versions of packages linux-headers-amd64 depends on:
pn  linux-headers-4.11.0-2-amd64  

linux-headers-amd64 recommends no packages.

linux-headers-amd64 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.12.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Sat, 12 Aug 2017 23:09:26 +0100
Source: linux
Binary: linux-source-4.12 linux-support-4.12.0-1 linux-doc-4.12 
linux-manual-4.12 linux-kbuild-4.12 linux-cpupower libcpupower1 libcpupower-dev 
linux-perf-4.12 libusbip-dev usbip hyperv-daemons linux-headers-4.12.0-1-common 
linux-libc-dev linux-headers-4.12.0-1-all linux-headers-4.12.0-1-all-alpha 
kernel-image-4.12.0-1-alpha-generic-di nic-modules-4.12.0-1-alpha-generic-di 
nic-wireless-modules-4.12.0-1-alpha-generic-di 
nic-shared-modules-4.12.0-1-alpha-generic-di 
serial-modules-4.12.0-1-alpha-generic-di 
usb-serial-modules-4.12.0-1-alpha-generic-di 
ppp-modules-4.12.0-1-alpha-generic-di pata-modules-4.12.0-1-alpha-generic-di 
cdrom-core-modules-4.12.0-1-alpha-generic-di 
scsi-core-modules-4.12.0-1-alpha-generic-di 
scsi-modules-4.12.0-1-alpha-generic-di loop-modules-4.12.0-1-alpha-generic-di 
btrfs-modules-4.12.0-1-alpha-generic-di ext4-modules-4.12.0-1-alpha-generic-di 
isofs-modules-4.12.0-1-alpha-generic-di jfs-modules-4.12.0-1-alpha-generic-di
 xfs-modules-4.12.0-1-alpha-generic-di fat-modules-4.12.0-1-alpha-generic-di 
md-modules-4.12.0-1-alpha-generic-di 
multipath-modules-4.12.0-1-alpha-generic-di 
usb-modules-4.12.0-1-alpha-generic-di 
usb-storage-modules-4.12.0-1-alpha-generic-di 
fb-modules-4.12.0-1-alpha-generic-di input-modules-4.12.0-1-alpha-generic-di 
event-modules-4.12.0-1-alpha-generic-di mouse-modules-4.12.0-1-alpha-generic-di 
nic-pcmcia-modules-4.12.0-1-alpha-generic-di 
pcmcia-modules-4.12.0-1-alpha-generic-di 
nic-usb-modules-4.12.0-1-alpha-generic-di 
sata-modules-4.12.0-1-alpha-generic-di crc-modules-4.12.0-1-alpha-generic-di 
crypto-modules-4.12.0-1-alpha-generic-di 
crypto-dm-modules-4.12.0-1-alpha-generic-di 
ata-modules-4.12.0-1-alpha-generic-di nbd-modules-4.12.0-1-alpha-generic-di 
squashfs-modules-4.12.0-1-alpha-generic-di 
virtio-modules-4.12.0-1-alpha-generic-di zlib-modules-4.12.0-1-alpha-generic-di 
fuse-modules-4.12.0-1-alpha-generic-di srm-modules-4.12.0-1-alpha-generic-di
 linux-image-4.12.0-1-alpha-generic linux-headers-4.12.0-1-alpha-generic 
linux-image-4.12.0-1-alpha-generic-dbg 

Bug#870298: marked as done (4.11.0-2-amd64 headers cannot be installed)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 18:00:12 +
with message-id 
and subject line Bug#869511: fixed in linux 4.12.6-1
has caused the Debian Bug report #869511,
regarding 4.11.0-2-amd64 headers cannot be installed
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.)


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

Package: linux-headers-4.11.0-2-amd64
Version: 4.11.11-1+b1
Severity: serious

Hi,

I have been trying to install linux-headers-4.11.0-2-amd64 on
unstable/sid for a couple of days now and cannot due to an
unresolved dependency.

Specifically, the package depends on linux-headers-4.11.0-2-common
revision (= 4.11.11-1+b1), but the latter does not exist.

Can someone check that revision numbers and dependencies are
correct?


# LANG=C apt-get install linux-headers-4.11.0-2-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-headers-4.11.0-2-amd64 : Depends: linux-headers-4.11.0-2-common 
(= 4.11.11-1+b1) but 4.11.11-1 is to be installed

E: Unable to correct problems, you have held broken packages.



Thank you.


Regards,

Philippe
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.12.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Sat, 12 Aug 2017 23:09:26 +0100
Source: linux
Binary: linux-source-4.12 linux-support-4.12.0-1 linux-doc-4.12 
linux-manual-4.12 linux-kbuild-4.12 linux-cpupower libcpupower1 libcpupower-dev 
linux-perf-4.12 libusbip-dev usbip hyperv-daemons linux-headers-4.12.0-1-common 
linux-libc-dev linux-headers-4.12.0-1-all linux-headers-4.12.0-1-all-alpha 
kernel-image-4.12.0-1-alpha-generic-di nic-modules-4.12.0-1-alpha-generic-di 
nic-wireless-modules-4.12.0-1-alpha-generic-di 
nic-shared-modules-4.12.0-1-alpha-generic-di 
serial-modules-4.12.0-1-alpha-generic-di 
usb-serial-modules-4.12.0-1-alpha-generic-di 
ppp-modules-4.12.0-1-alpha-generic-di pata-modules-4.12.0-1-alpha-generic-di 
cdrom-core-modules-4.12.0-1-alpha-generic-di 
scsi-core-modules-4.12.0-1-alpha-generic-di 
scsi-modules-4.12.0-1-alpha-generic-di loop-modules-4.12.0-1-alpha-generic-di 
btrfs-modules-4.12.0-1-alpha-generic-di ext4-modules-4.12.0-1-alpha-generic-di 
isofs-modules-4.12.0-1-alpha-generic-di jfs-modules-4.12.0-1-alpha-generic-di
 xfs-modules-4.12.0-1-alpha-generic-di fat-modules-4.12.0-1-alpha-generic-di 
md-modules-4.12.0-1-alpha-generic-di 
multipath-modules-4.12.0-1-alpha-generic-di 
usb-modules-4.12.0-1-alpha-generic-di 
usb-storage-modules-4.12.0-1-alpha-generic-di 
fb-modules-4.12.0-1-alpha-generic-di input-modules-4.12.0-1-alpha-generic-di 
event-modules-4.12.0-1-alpha-generic-di mouse-modules-4.12.0-1-alpha-generic-di 
nic-pcmcia-modules-4.12.0-1-alpha-generic-di 
pcmcia-modules-4.12.0-1-alpha-generic-di 
nic-usb-modules-4.12.0-1-alpha-generic-di 
sata-modules-4.12.0-1-alpha-generic-di crc-modules-4.12.0-1-alpha-generic-di 
crypto-modules-4.12.0-1-alpha-generic-di 
crypto-dm-modules-4.12.0-1-alpha-generic-di 
ata-modules-4.12.0-1-alpha-generic-di nbd-modules-4.12.0-1-alpha-generic-di 
squashfs-modules-4.12.0-1-alpha-generic-di 
virtio-modules-4.12.0-1-alpha-generic-di zlib-modules-4.12.0-1-alpha-generic-di 
fuse-modules-4.12.0-1-alpha-generic-di srm-modules-4.12.0-1-alpha-generic-di
 linux-image-4.12.0-1-alpha-generic linux-headers-4.12.0-1-alpha-generic 
linux-image-4.12.0-1-alpha-generic-dbg linux-image-4.12.0-1-alpha-smp 

Bug#869670: marked as done (Depends: linux-headers-4.11.0-2-common ... but it is not going to be installed)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 18:00:12 +
with message-id 
and subject line Bug#869511: fixed in linux 4.12.6-1
has caused the Debian Bug report #869511,
regarding Depends: linux-headers-4.11.0-2-common ... but it is not going to be 
installed
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.)


-- 
869511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-4.11.0-2-amd64
Version: 4.11.11-1

The following packages have unmet dependencies:
 linux-headers-4.11.0-2-amd64 : Depends: linux-headers-4.11.0-2-common (= 
4.11.11-1+b1) but it is not going to be installed
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.12.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Sat, 12 Aug 2017 23:09:26 +0100
Source: linux
Binary: linux-source-4.12 linux-support-4.12.0-1 linux-doc-4.12 
linux-manual-4.12 linux-kbuild-4.12 linux-cpupower libcpupower1 libcpupower-dev 
linux-perf-4.12 libusbip-dev usbip hyperv-daemons linux-headers-4.12.0-1-common 
linux-libc-dev linux-headers-4.12.0-1-all linux-headers-4.12.0-1-all-alpha 
kernel-image-4.12.0-1-alpha-generic-di nic-modules-4.12.0-1-alpha-generic-di 
nic-wireless-modules-4.12.0-1-alpha-generic-di 
nic-shared-modules-4.12.0-1-alpha-generic-di 
serial-modules-4.12.0-1-alpha-generic-di 
usb-serial-modules-4.12.0-1-alpha-generic-di 
ppp-modules-4.12.0-1-alpha-generic-di pata-modules-4.12.0-1-alpha-generic-di 
cdrom-core-modules-4.12.0-1-alpha-generic-di 
scsi-core-modules-4.12.0-1-alpha-generic-di 
scsi-modules-4.12.0-1-alpha-generic-di loop-modules-4.12.0-1-alpha-generic-di 
btrfs-modules-4.12.0-1-alpha-generic-di ext4-modules-4.12.0-1-alpha-generic-di 
isofs-modules-4.12.0-1-alpha-generic-di jfs-modules-4.12.0-1-alpha-generic-di
 xfs-modules-4.12.0-1-alpha-generic-di fat-modules-4.12.0-1-alpha-generic-di 
md-modules-4.12.0-1-alpha-generic-di 
multipath-modules-4.12.0-1-alpha-generic-di 
usb-modules-4.12.0-1-alpha-generic-di 
usb-storage-modules-4.12.0-1-alpha-generic-di 
fb-modules-4.12.0-1-alpha-generic-di input-modules-4.12.0-1-alpha-generic-di 
event-modules-4.12.0-1-alpha-generic-di mouse-modules-4.12.0-1-alpha-generic-di 
nic-pcmcia-modules-4.12.0-1-alpha-generic-di 
pcmcia-modules-4.12.0-1-alpha-generic-di 
nic-usb-modules-4.12.0-1-alpha-generic-di 
sata-modules-4.12.0-1-alpha-generic-di crc-modules-4.12.0-1-alpha-generic-di 
crypto-modules-4.12.0-1-alpha-generic-di 
crypto-dm-modules-4.12.0-1-alpha-generic-di 
ata-modules-4.12.0-1-alpha-generic-di nbd-modules-4.12.0-1-alpha-generic-di 
squashfs-modules-4.12.0-1-alpha-generic-di 
virtio-modules-4.12.0-1-alpha-generic-di zlib-modules-4.12.0-1-alpha-generic-di 
fuse-modules-4.12.0-1-alpha-generic-di srm-modules-4.12.0-1-alpha-generic-di
 linux-image-4.12.0-1-alpha-generic linux-headers-4.12.0-1-alpha-generic 
linux-image-4.12.0-1-alpha-generic-dbg linux-image-4.12.0-1-alpha-smp 
linux-headers-4.12.0-1-alpha-smp linux-image-4.12.0-1-alpha-smp-dbg 
linux-headers-4.12.0-1-all-amd64 kernel-image-4.12.0-1-amd64-di 
nic-modules-4.12.0-1-amd64-di nic-wireless-modules-4.12.0-1-amd64-di 
nic-shared-modules-4.12.0-1-amd64-di serial-modules-4.12.0-1-amd64-di 
usb-serial-modules-4.12.0-1-amd64-di ppp-modules-4.12.0-1-amd64-di 
pata-modules-4.12.0-1-amd64-di cdrom-core-modules-4.12.0-1-amd64-di 
firewire-core-modules-4.12.0-1-amd64-di scsi-core-modules-4.12.0-1-amd64-di 
scsi-modules-4.12.0-1-amd64-di loop-modules-4.12.0-1-amd64-di 
btrfs-modules-4.12.0-1-amd64-di ext4-modules-4.12.0-1-amd64-di 
isofs-modules-4.12.0-1-amd64-di jfs-modules-4.12.0-1-amd64-di 
ntfs-modules-4.12.0-1-amd64-di xfs-modules-4.12.0-1-amd64-di 
fat-modules-4.12.0-1-amd64-di md-modules-4.12.0-1-amd64-di 
multipath-modules-4.12.0-1-amd64-di
 usb-modules-4.12.0-1-amd64-di 

Bug#869511: marked as done (linux: binNMU-unsafe dependency on linux-headers-*-common)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 18:00:12 +
with message-id 
and subject line Bug#869511: fixed in linux 4.12.6-1
has caused the Debian Bug report #869511,
regarding linux: binNMU-unsafe dependency on linux-headers-*-common
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.)


-- 
869511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.11.11-1
Severity: grave
Justification: renders package unusable (uninstallable)

The recent binNMU of linux for Perl 5.26 broke the build-specific
headers packages, which are architecture-dependent but depend on an
identical *binary* version of the architecture-independent
linux-headers-*-common package.  Specifically, I observe that
linux-headers-4.11.0-2-amd64 4.11.11-1+b1 depends on
linux-headers-4.11.0-2-common (= 4.11.11-1+b1), which does not exist.

Could you please fix these relationships to use ${source:Version}?
(As you may recall, the legacy ${Source-Version} variable is an alias
for *${binary:Version}*.)

Thanks!

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

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.12.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Sat, 12 Aug 2017 23:09:26 +0100
Source: linux
Binary: linux-source-4.12 linux-support-4.12.0-1 linux-doc-4.12 
linux-manual-4.12 linux-kbuild-4.12 linux-cpupower libcpupower1 libcpupower-dev 
linux-perf-4.12 libusbip-dev usbip hyperv-daemons linux-headers-4.12.0-1-common 
linux-libc-dev linux-headers-4.12.0-1-all linux-headers-4.12.0-1-all-alpha 
kernel-image-4.12.0-1-alpha-generic-di nic-modules-4.12.0-1-alpha-generic-di 
nic-wireless-modules-4.12.0-1-alpha-generic-di 
nic-shared-modules-4.12.0-1-alpha-generic-di 
serial-modules-4.12.0-1-alpha-generic-di 
usb-serial-modules-4.12.0-1-alpha-generic-di 
ppp-modules-4.12.0-1-alpha-generic-di pata-modules-4.12.0-1-alpha-generic-di 
cdrom-core-modules-4.12.0-1-alpha-generic-di 
scsi-core-modules-4.12.0-1-alpha-generic-di 
scsi-modules-4.12.0-1-alpha-generic-di loop-modules-4.12.0-1-alpha-generic-di 
btrfs-modules-4.12.0-1-alpha-generic-di ext4-modules-4.12.0-1-alpha-generic-di 
isofs-modules-4.12.0-1-alpha-generic-di jfs-modules-4.12.0-1-alpha-generic-di
 xfs-modules-4.12.0-1-alpha-generic-di fat-modules-4.12.0-1-alpha-generic-di 
md-modules-4.12.0-1-alpha-generic-di 
multipath-modules-4.12.0-1-alpha-generic-di 
usb-modules-4.12.0-1-alpha-generic-di 
usb-storage-modules-4.12.0-1-alpha-generic-di 
fb-modules-4.12.0-1-alpha-generic-di input-modules-4.12.0-1-alpha-generic-di 
event-modules-4.12.0-1-alpha-generic-di mouse-modules-4.12.0-1-alpha-generic-di 
nic-pcmcia-modules-4.12.0-1-alpha-generic-di 
pcmcia-modules-4.12.0-1-alpha-generic-di 
nic-usb-modules-4.12.0-1-alpha-generic-di 
sata-modules-4.12.0-1-alpha-generic-di crc-modules-4.12.0-1-alpha-generic-di 
crypto-modules-4.12.0-1-alpha-generic-di 
crypto-dm-modules-4.12.0-1-alpha-generic-di 
ata-modules-4.12.0-1-alpha-generic-di nbd-modules-4.12.0-1-alpha-generic-di 
squashfs-modules-4.12.0-1-alpha-generic-di 
virtio-modules-4.12.0-1-alpha-generic-di zlib-modules-4.12.0-1-alpha-generic-di 
fuse-modules-4.12.0-1-alpha-generic-di srm-modules-4.12.0-1-alpha-generic-di
 linux-image-4.12.0-1-alpha-generic linux-headers-4.12.0-1-alpha-generic 
linux-image-4.12.0-1-alpha-generic-dbg linux-image-4.12.0-1-alpha-smp 
linux-headers-4.12.0-1-alpha-smp 

Bug#871506: marked as done (libhdf5-java package does not contain jar)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 17:49:21 +
with message-id 
and subject line Bug#871506: fixed in hdf5 1.10.0-patch1+docs-4
has caused the Debian Bug report #871506,
regarding libhdf5-java package does not contain jar
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.)


-- 
871506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhdf5-java
Version: 1.10.0-patch1+docs-3
Severity: grave
Justification: renders package unusable

Hi,

I have just discovered that the libhdf5-java package fails to ship
the jarhdf5.jar file.  This makes the HDF5 java bindings unusable
(this came up whilst trying to compile the newly released hdfview).

The problem seems to be the use of $(upstreamversion) to rename
the jar file in the install rule and also that jh_installlibs
is not being called.

I've hacked around it for now by changing the dh_install_java
rule in debian/rules to contain:

dh_install_java: build_serial
mv debian/build-serial/java/src/jarhdf5-*.jar 
debian/build-serial/java/src/jarhdf5.jar
jh_installlibs

which ensures that the jar is shipped - this may not be the
solution which you want to use.

This problem affects stable as well as unstable (as it's the same
version).

Thanks,

Mark
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.10.0-patch1+docs-4

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated hdf5 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, 13 Aug 2017 18:50:36 +0200
Source: hdf5
Binary: libhdf5-100 libhdf5-cpp-100 libhdf5-dev libhdf5-openmpi-100 
libhdf5-openmpi-dev libhdf5-mpich-100 libhdf5-mpich-dev libhdf5-mpi-dev 
libhdf5-doc hdf5-helpers hdf5-tools libhdf5-serial-dev libhdf5-java libhdf5-jni
Architecture: source
Version: 1.10.0-patch1+docs-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Gilles Filippini 
Description:
 hdf5-helpers - Hierarchical Data Format 5 (HDF5) - Helper tools
 hdf5-tools - Hierarchical Data Format 5 (HDF5) - Runtime tools
 libhdf5-100 - Hierarchical Data Format 5 (HDF5) - runtime files - serial versio
 libhdf5-cpp-100 - Hierarchical Data Format 5 (HDF5) - C++ libraries
 libhdf5-dev - Hierarchical Data Format 5 (HDF5) - development files - serial ve
 libhdf5-doc - Hierarchical Data Format 5 (HDF5) - Documentation
 libhdf5-java - Hierarchical Data Format 5 (HDF5) - Java Wrapper Library
 libhdf5-jni - native library used by libhdf5-java
 libhdf5-mpi-dev - Hierarchical Data Format 5 (HDF5) - development files - 
default M
 libhdf5-mpich-100 - Hierarchical Data Format 5 (HDF5) - runtime files - MPICH2 
versio
 libhdf5-mpich-dev - Hierarchical Data Format 5 (HDF5) - development files - 
MPICH ver
 libhdf5-openmpi-100 - Hierarchical Data Format 5 (HDF5) - runtime files - 
OpenMPI versi
 libhdf5-openmpi-dev - Hierarchical Data Format 5 (HDF5) - development files - 
OpenMPI v
 libhdf5-serial-dev - transitional dummy package
Closes: 871506
Changes:
 hdf5 (1.10.0-patch1+docs-4) unstable; urgency=medium
 .
   * debian/rules: fix javahelper invocation (closes: #871506)
Checksums-Sha1:
 14214ee4c1fe4f6b99b5077b85951cd12ef36ac2 2748 hdf5_1.10.0-patch1+docs-4.dsc
 4f5602cfa78dcdd749039dd6df4920e0f21779b1 119648 
hdf5_1.10.0-patch1+docs-4.debian.tar.xz
 49f692e9ecf3330df73b1f8257ab5b0cdeeaf81a 8197 
hdf5_1.10.0-patch1+docs-4_source.buildinfo
Checksums-Sha256:
 cffb7859ef5db09b27d1cb0fc14375241e499c7f602f124b2a1e1019feaf9adf 2748 
hdf5_1.10.0-patch1+docs-4.dsc
 d527f57aa97334bf9669b104d884ce4471cb9a49ef326d964b3d6c8620be283f 119648 
hdf5_1.10.0-patch1+docs-4.debian.tar.xz
 f1b5390ff675ae728b0acd5baea15ff885fd68173c18aa10351bba9772554563 8197 
hdf5_1.10.0-patch1+docs-4_source.buildinfo
Files:
 3278e420fd692f7efdc282cbe9fc452d 2748 science optional 

Processed: Add another affected package

[Debian Bug Tracking System]

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

> affects 871246 src:libkolab
Bug #871246 [libkf5akonadi-dev] libkf5akonadi-dev: std_exception.h includes 
/usr/include/c++/6/exception
Added indication that 871246 affects src:libkolab
> thanks
Stopping processing here.

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

Bug#872037: libvigrampex: Failure in MultiArrayPointoperatorsTest::testCombine2() [mips64el]

[Daniel Stender]

Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Current Vigra FTBFS on mips64el [1]:


[ 63%] Building CXX object 
test/multiarray/CMakeFiles/test_multiarray.dir/testsuccess.cxx.o
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/c++  -DHasHDF5 -DHasJPEG -DHasPNG -DHasTIFF 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/include 
-I/usr/include/hdf5/serial  -std=c++11 -pthread -W -Wall -Wextra 
-Wno-unused-parameter -Wno-sign-compare -Wno-unused-variable -Wno-type-limits 
-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2   -o CMakeFiles/test_multiarray.dir/testsuccess.cxx.o -c 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray/testsuccess.cxx
[ 65%] Linking CXX executable test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/test_multiarray.dir/link.txt 
--verbose=1
/usr/bin/c++  -std=c++11 -pthread -W -Wall -Wextra -Wno-unused-parameter 
-Wno-sign-compare -Wno-unused-variable -Wno-type-limits -g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2  -rdynamic CMakeFiles/test_multiarray.dir/test.cxx.o 
CMakeFiles/test_multiarray.dir/testsuccess.cxx.o  -o test_multiarray 
-Wl,-rpath,/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/src/impex:/usr/lib/mips64el-linux-gnuabi64/hdf5/serial
 ../../src/impex/libvigraimpex.so.6.1.11.0 -ljpeg -lpng -lz -ltiff -lIlmImf 
-lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz -lz -ltiff 
-lIlmImf -lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz 
Running test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& ./run_test_multiarray.sh
Entering test suite MultiArrayTestSuite
All (24) tests passed in test suite MultiArrayTestSuite
Leaving test suite MultiArrayTestSuite

Entering test suite MultiArrayDataTestSuite
All (32) tests passed in test suite MultiArrayDataTestSuite
Leaving test suite MultiArrayDataTestSuite

Entering test suite ImageViewTestSuite
All (16) tests passed in test suite ImageViewTestSuite
Leaving test suite ImageViewTestSuite

Entering test suite MultiArrayPointOperatorsTestSuite

Failure in MultiArrayPointoperatorsTest::testCombine2()
Unexpected signal: memory access violation

Fatal error - aborting test suite MultiArrayPointOperatorsTestSuite.

test/multiarray/CMakeFiles/test_multiarray.dir/build.make:146: recipe for 
target 'test/multiarray/test_multiarray' failed
make[5]: *** [test/multiarray/test_multiarray] Error 1


DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libvigraimpex=mips64el=1.10.0%2Bgit20160211.167be93%2Bdfsg-4=1502638529=0

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

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

Processed: Fix the found version

[Debian Bug Tracking System]

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

> notfound 815632 2.2.15-4
Bug #815632 [gnubiff] gnubiff: Fails to read config at startup
No longer marked as found in versions gnubiff/2.2.15-4.
> found 815632 2.2.16-1
Bug #815632 [gnubiff] gnubiff: Fails to read config at startup
Marked as found in versions gnubiff/2.2.16-1.
> thanks
Stopping processing here.

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

Bug#871992: marked as done (juffed FTBFS on !amd64 64bit: missing symbol)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 17:04:56 +
with message-id 
and subject line Bug#871992: fixed in juffed 0.10-85-g5ba17f9-13
has caused the Debian Bug report #871992,
regarding juffed FTBFS on !amd64 64bit: missing symbol
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.)


-- 
871992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: juffed
Version: 0.10-85-g5ba17f9-12
Severity: serious

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

...
   dh_makeshlibs -a -O--buildsystem=cmake -O--fail-missing 
-O--builddirectory=./build
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libjuffed-engine-qsci0.10/DEBIAN/symbols 
doesn't match completely debian/libjuffed-engine-qsci0.10.symbols
--- debian/libjuffed-engine-qsci0.10.symbols 
(libjuffed-engine-qsci0.10_0.10-85-g5ba17f9-12_arm64)
+++ dpkg-gensymbols1_O3Nv   2017-08-12 21:35:07.207296281 +
@@ -390,7 +390,7 @@
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)::{lambda()#8}::operator()() 
const::qstring_literal@Base" 0.10
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)::{lambda()#9}::operator()() 
const::qstring_literal@Base" 0.10
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)@Base" 0.10
- (c++|arch= !amd64)"int const* std::__find_if >(int const*, int const*, 
__gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.10
+#MISSING: 0.10-85-g5ba17f9-12# (c++|arch= !amd64)"int const* 
std::__find_if >(int 
const*, int const*, __gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.10
  (c++)"non-virtual thunk to Juff::FileTypesPage::~FileTypesPage()@Base" 0.10
  (c++)"non-virtual thunk to Juff::JuffScintilla::~JuffScintilla()@Base" 0.10
  (c++)"non-virtual thunk to Juff::PrintingPage::~PrintingPage()@Base" 0.10
dh_makeshlibs: failing due to earlier errors
debian/rules:14: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: juffed
Source-Version: 0.10-85-g5ba17f9-13

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated juffed 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, 13 Aug 2017 18:38:14 +0200
Source: juffed
Binary: juffed juffed-dev juffed-plugins libjuff0.10 libjuffed-engine-qsci0.10
Architecture: source
Version: 0.10-85-g5ba17f9-13
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 juffed - Lightweight yet powerful Qt text editor
 juffed-dev - Lightweight yet powerful Qt text editor - development files
 juffed-plugins - Lightweight yet powerful Qt text editor - plugins
 libjuff0.10 - Lightweight yet powerful Qt text editor - libjuff0.10
 libjuffed-engine-qsci0.10 - Lightweight yet powerful Qt text editor - 
libjuffed-engine-qsci0.
Closes: 871992
Changes:
 juffed (0.10-85-g5ba17f9-13) unstable; urgency=medium
 .
   * Fixed 64 bit symbol (Closes: #871992)
Checksums-Sha1:
 ba9aea213e81d401b1cb9098dd711d1ad534c01e 2004 juffed_0.10-85-g5ba17f9-13.dsc
 e77d4b0ba4ccec3a79d3f5cb7655d0eec5a9048d 13520 
juffed_0.10-85-g5ba17f9-13.debian.tar.xz
 2f80373f03ed321d76fd4554a557fc6382f57377 10319 
juffed_0.10-85-g5ba17f9-13_source.buildinfo
Checksums-Sha256:
 458857b269d8813568c8ef2d59af204bd8b70ea0a24314cb83557511fd2dc828 2004 
juffed_0.10-85-g5ba17f9-13.dsc
 ed4db03593360462e5548aa38ce3e59b9affe853370035f285c46989260d40e0 13520 
juffed_0.10-85-g5ba17f9-13.debian.tar.xz
 0796b63dc6a86ddf2107c87f368e99378946c1fb621e0d694451b1abc250eb53 10319 
juffed_0.10-85-g5ba17f9-13_source.buildinfo
Files:
 8c6455308e32beb08d935ae12b639bd8 2004 editors optional 
juffed_0.10-85-g5ba17f9-13.dsc
 aaeedf700b4d1e2e6607567000ed805e 13520 editors optional 

Bug#872035: sysdig FTBFS with curl 7.55.0-1

[Adrian Bunk]

Source: sysdig
Version: 0.17.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sysdig.html

...
/build/1st/sysdig-0.17.0/userspace/libsinsp/marathon_http.cpp:10:10: fatal 
error: curl/curlbuild.h: No such file or directory
 #include "curl/curlbuild.h"
  ^~
compilation terminated.
userspace/libsinsp/CMakeFiles/sinsp.dir/build.make:1049: recipe for target 
'userspace/libsinsp/CMakeFiles/sinsp.dir/marathon_http.cpp.o' failed
make[3]: *** [userspace/libsinsp/CMakeFiles/sinsp.dir/marathon_http.cpp.o] 
Error 1

Bug#871629: Problem solved with unstable version

[Vinzenz Vietzke]

Hi,

the version available from unstable solves this issue for me (Buster, Xfce).

thunderbird:
  Installiert:   1:52.2.1-5
  Installationskandidat: 1:52.2.1-5
  Versionstabelle:
 *** 1:52.2.1-5 500
500 http://http.debian.net/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 1:52.2.1-4+b1 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages

Regards,
vinz.

--
Xfce.space | skyrocket your desktop usage
https://xfce.space

Bug#871357: packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at /usr/share/perl5/Locale/Po4a/TransTractor.pm line 6

[gregor herrmann]

On Tue, 08 Aug 2017 23:55:26 +0200, Martin Quinson wrote:

> Thanks for investigating this bug.

Thanks for looking into this issue.
 
> > The error is in /usr/share/perl5/Locale/Po4a/TransTractor.pm:643
> > which is
> > my $found = scalar grep { /$position/ } @{$self->{TT}{doc_out}};
> > and $position (comes from addendum_parse() in the same file and)
> > contains '\\end{document}' at that point.
> > 
> > And this '\\end{document}' itself comes from files in the
> > packaging-tutorial po4a directory.
> > 
> > So I don't know if po4a needs a generic fix, or packaging-tutorial
> > needs to change how it uses it.
> 
> I would be unable to generate a patch for the first option. My perl is
> rather rotten nowadays. 

I also think it would be difficult; all tha po4a sees at this point
is a string, and it's probably impossible to preprocess it into a
regexp.

What po4a could maybe do is to mention in the documentation that the
string in "position=something" in addendums will be interpreted as a
Perl regexp later.

> I think that the second option is sensible:
> packaging-tutorial is providing some code that is interpreted by po4a,
> so it should ensure that it provides correct code.

I tend to agree. (And it aleady escapes the backslash.)
 

Lucas, what do you think?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: Add more affected packages

[Debian Bug Tracking System]

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

> affects 871246 src:kf5-kdepimlibs src:kf5-kdepim-apps-libs src:kalarmcal
Bug #871246 [libkf5akonadi-dev] libkf5akonadi-dev: std_exception.h includes 
/usr/include/c++/6/exception
Added indication that 871246 affects src:kf5-kdepimlibs, 
src:kf5-kdepim-apps-libs, and src:kalarmcal
> thanks
Stopping processing here.

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

Bug#871180: marked as done (nomacs: FTBFS: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:34:31 +
with message-id 
and subject line Bug#871180: fixed in nomacs 3.4.1+dfsg-10
has caused the Debian Bug report #871180,
regarding nomacs: FTBFS: dh_makeshlibs: failing due to earlier errors
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.)


-- 
871180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomacs
Version: 3.4.1+dfsg-9
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/nomacs-3.4.1+dfsg/obj-x86_64-linux-gnu'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory 
> '/<>/nomacs-3.4.1+dfsg/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "RelWithDebInfo"
> -- Installing: /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/bin/nomacs
> -- Set runtime path of 
> "/<>/nomacs-3.4.1+dfsg/debian/tmp/usr/bin/nomacs" to ""
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsGui.so.3.4.0
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsGui.so.3
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsGui.so
> -- Set runtime path of 
> "/<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsGui.so.3.4.0"
>  to ""
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsLoader.so.3.4.0
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsLoader.so.3
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsLoader.so
> -- Set runtime path of 
> "/<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsLoader.so.3.4.0"
>  to ""
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsCore.so.3.4.0
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsCore.so.3
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsCore.so
> -- Set runtime path of 
> "/<>/nomacs-3.4.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/libnomacsCore.so.3.4.0"
>  to ""
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/applications/nomacs.desktop
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/pixmaps/nomacs.svg
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_als.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_ar.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_az.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_bg.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_bs.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_cs.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_de.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_en.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_es.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_fr.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_hr.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_it.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_ja.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_ko.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_nl.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_pl.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_pt.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_ru.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_sk.qm
> -- Installing: 
> /<>/nomacs-3.4.1+dfsg/debian/tmp/usr/share/nomacs/translations/nomacs_sl.qm
> -- Installing: 
> 

Processed: Bug was introduced in 1.2.4+dfsg1-6

[Debian Bug Tracking System]

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

> found 871774 1.2.4+dfsg1-6
Bug #871774 {Done: Adrian Bunk } [src:bogofilter] Broken 
dependencies
Bug #871694 {Done: Adrian Bunk } [src:bogofilter] 
bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 depends on bogofilter-common 
(same version),the latter does not exist
Marked as found in versions bogofilter/1.2.4+dfsg1-6.
Marked as found in versions bogofilter/1.2.4+dfsg1-6.
> thanks
Stopping processing here.

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

Processed: Re: mate-power-manager: sometimes hits not-reached assertion on startup

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 mate-power-manager: crashes with upower 0.99.5 on any device with 
> a backlit keyboard
Bug #870121 [mate-power-manager] mate-power-manager: sometimes hits not-reached 
assertion on startup
Changed Bug title to 'mate-power-manager: crashes with upower 0.99.5 on any 
device with a backlit keyboard' from 'mate-power-manager: sometimes hits 
not-reached assertion on startup'.
> severity -1 grave
Bug #870121 [mate-power-manager] mate-power-manager: crashes with upower 0.99.5 
on any device with a backlit keyboard
Severity set to 'grave' from 'important'

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

Bug#871774: marked as done (Broken dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:18:59 +
with message-id 
and subject line Bug#871694: fixed in bogofilter 1.2.4+dfsg1-10
has caused the Debian Bug report #871694,
regarding Broken dependencies
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.)


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

Package: bogofilter-bdb
Severity: normal
Version: 1.2.4+dfsg1-9+b1

Probably as a result of a rebuild, bogofilter-bdb 1.2.4+dfsg1-9+b1 depends on 
both:

--- bogofilter-common (= 1.2.4+dfsg1-9)
--- bogofilter-common (= 1.2.4+dfsg1-9+b1) (UNAVAILABLE)

-- System Information:
Debian Release: buster/sid
 APT prefers unstable
 APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: bogofilter
Source-Version: 1.2.4+dfsg1-10

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated bogofilter 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, 13 Aug 2017 18:39:05 +0300
Source: bogofilter
Binary: bogofilter bogofilter-bdb bogofilter-sqlite bogofilter-tokyocabinet 
bogofilter-common
Architecture: source
Version: 1.2.4+dfsg1-10
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Description:
 bogofilter - fast Bayesian spam filter (dummy package)
 bogofilter-bdb - fast Bayesian spam filter (Berkeley DB)
 bogofilter-common - fast Bayesian spam filter (common files)
 bogofilter-sqlite - fast Bayesian spam filter (sqlite)
 bogofilter-tokyocabinet - fast Bayesian spam filter (tokyocabinet)
Closes: 871694
Changes:
 bogofilter (1.2.4+dfsg1-10) unstable; urgency=medium
 .
   * Make bogofilter-common binary-any, to avoid broken dependencies
 after binNMUs. (Closes: #871694)
Checksums-Sha1:
 8b7a04c9252b810bc126010826fb71c60ef7e950 2145 bogofilter_1.2.4+dfsg1-10.dsc
 9daf9dc96ff8287556233092a4ebf08ccfe007c3 19012 
bogofilter_1.2.4+dfsg1-10.debian.tar.xz
Checksums-Sha256:
 f1dcd3603e8c635ad247b92c0c13de3a6dca14b3e6b66330ab31f808ad640e29 2145 
bogofilter_1.2.4+dfsg1-10.dsc
 59b8163d426b660d07d69444cdc4f6da36b4a15f4d5515f9e422766ff8303885 19012 
bogofilter_1.2.4+dfsg1-10.debian.tar.xz
Files:
 07c407b66e385da98009bd23da8c6cb7 2145 mail optional 
bogofilter_1.2.4+dfsg1-10.dsc
 526e093dd9e9e9f3ceb2d5f5edd8bb08 19012 mail optional 
bogofilter_1.2.4+dfsg1-10.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlmQdt8ACgkQiNJCh6LY
mLExqA//d9bvKkHOXRGX7SlBUu/7tSiLmOQk4ZeoqV6toPANCUc9QP/qi++RaYv3
/veXpTa6jKDhu8jMTy9oiDtUaw/NiyqNOt/B9aX0Jmn9YHlk0zja1nVLKcbmIme/
AfvY//xb3a4HDkr/7XXjhkx9dGYGP2FRRPxC2odpE+vxvAULZ0wyYy/W5/aUAX7R
E2E8TdVaBXbcSK+/zlv1p7/3lR8yZyJ1uuGbnlSVpl+rohzLh9K0otzOcx5yqN7y
IdurTvBdRBZNDuBlDYXgZcVgrpjmyLsBXPrE3Nm1RYet+QWfs49tGfFfMyuT2WaB
m2V+aY8mFQ1qLPH2hx6SU+FqKAjpADb3UaXFRyIzY27h4LveeEhwDZJ1eMYABJwh
YWHwULtkOftnNbpiLc69doDB6B4DaGwx7+gJoF6eIBU+kQR+h/eX1x+vdkp8zydU
ZvYDUdTyo4psQ1DRkjber624hZYjAewpMIvDVWjBVUmQdGHVqE+hAjjDrni2TfHn
yGojmu7rq7xXZXkXzFiBAbOMoiZ1jyeyW3WQhqSWP275kySIXWayEkyKAAwidnnQ
Ch2XtJVE15E3Ify7GWuGeAI5AyAfYI0NSMOBeZo2PnvhbzA2iU6hUZumcY/uGjqU
67eKaEwJ9RDdbGerV0BnhPNBnjxewV1w2+EHCPoz+6K0VPvFeQE=
=d6XC
-END PGP SIGNATURE End Message ---

Bug#871694: marked as done (bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 depends on bogofilter-common (same version),the latter does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:18:59 +
with message-id 
and subject line Bug#871694: fixed in bogofilter 1.2.4+dfsg1-10
has caused the Debian Bug report #871694,
regarding bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 depends on 
bogofilter-common (same version),the latter does not exist
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.)


-- 
871694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bogofilter-common
Version: 1.2.4+dfsg1-9
Severity: serious
Justification: 2

Dear Maintainer,

Trying to install bogofilter-bdb-1.2.4+dfsg1-9+b1 fails, due to a dependency on 
bogofilter-common of the same version, which does not exist. Seems like an 
oversight, but it blocks me from completing an upgrade. I'd really appreciate a 
fix!

Many thanks!

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'), 
(500, 'testing-debug'), (500, 'oldstable-updates'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

bogofilter-common depends on no packages.

bogofilter-common recommends no packages.

Versions of packages bogofilter-common suggests:
pn  doc-base  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bogofilter
Source-Version: 1.2.4+dfsg1-10

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated bogofilter 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, 13 Aug 2017 18:39:05 +0300
Source: bogofilter
Binary: bogofilter bogofilter-bdb bogofilter-sqlite bogofilter-tokyocabinet 
bogofilter-common
Architecture: source
Version: 1.2.4+dfsg1-10
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Description:
 bogofilter - fast Bayesian spam filter (dummy package)
 bogofilter-bdb - fast Bayesian spam filter (Berkeley DB)
 bogofilter-common - fast Bayesian spam filter (common files)
 bogofilter-sqlite - fast Bayesian spam filter (sqlite)
 bogofilter-tokyocabinet - fast Bayesian spam filter (tokyocabinet)
Closes: 871694
Changes:
 bogofilter (1.2.4+dfsg1-10) unstable; urgency=medium
 .
   * Make bogofilter-common binary-any, to avoid broken dependencies
 after binNMUs. (Closes: #871694)
Checksums-Sha1:
 8b7a04c9252b810bc126010826fb71c60ef7e950 2145 bogofilter_1.2.4+dfsg1-10.dsc
 9daf9dc96ff8287556233092a4ebf08ccfe007c3 19012 
bogofilter_1.2.4+dfsg1-10.debian.tar.xz
Checksums-Sha256:
 f1dcd3603e8c635ad247b92c0c13de3a6dca14b3e6b66330ab31f808ad640e29 2145 
bogofilter_1.2.4+dfsg1-10.dsc
 59b8163d426b660d07d69444cdc4f6da36b4a15f4d5515f9e422766ff8303885 19012 
bogofilter_1.2.4+dfsg1-10.debian.tar.xz
Files:
 07c407b66e385da98009bd23da8c6cb7 2145 mail optional 
bogofilter_1.2.4+dfsg1-10.dsc
 526e093dd9e9e9f3ceb2d5f5edd8bb08 19012 mail optional 
bogofilter_1.2.4+dfsg1-10.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlmQdt8ACgkQiNJCh6LY
mLExqA//d9bvKkHOXRGX7SlBUu/7tSiLmOQk4ZeoqV6toPANCUc9QP/qi++RaYv3
/veXpTa6jKDhu8jMTy9oiDtUaw/NiyqNOt/B9aX0Jmn9YHlk0zja1nVLKcbmIme/
AfvY//xb3a4HDkr/7XXjhkx9dGYGP2FRRPxC2odpE+vxvAULZ0wyYy/W5/aUAX7R
E2E8TdVaBXbcSK+/zlv1p7/3lR8yZyJ1uuGbnlSVpl+rohzLh9K0otzOcx5yqN7y
IdurTvBdRBZNDuBlDYXgZcVgrpjmyLsBXPrE3Nm1RYet+QWfs49tGfFfMyuT2WaB
m2V+aY8mFQ1qLPH2hx6SU+FqKAjpADb3UaXFRyIzY27h4LveeEhwDZJ1eMYABJwh
YWHwULtkOftnNbpiLc69doDB6B4DaGwx7+gJoF6eIBU+kQR+h/eX1x+vdkp8zydU
ZvYDUdTyo4psQ1DRkjber624hZYjAewpMIvDVWjBVUmQdGHVqE+hAjjDrni2TfHn

Bug#871994: marked as done (python-cryptography FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:05:53 +
with message-id 
and subject line Bug#871994: fixed in pytest 3.2.1-1
has caused the Debian Bug report #871994,
regarding python-cryptography FTBFS: TypeError: putenv() argument 2 must be 
string without null bytes, not str
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.)


-- 
871994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cryptography
Version: 1.9-1
Severity: serious

Some recent change in unstable makes python-cryptography FTBFS:

https://tests.reproducible-builds.org/debian/history/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cryptography.html

...
 ERRORS 
 ERROR at setup of TestPKCS7.test_invalid_padding[128-] 

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestPKCS7::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
__ ERROR at teardown of TestPKCS7.test_invalid_padding[128-] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestPKCS7::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
__ ERROR at setup of TestANSIX923.test_invalid_padding[128-] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
_ ERROR at teardown of TestANSIX923.test_invalid_padding[128-] _

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
___ ERROR at setup of TestANSIX923.test_pad[128-11-11�] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_pad[128-11-11\x00\x00\x00\x00\x00\x06]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
_ ERROR at teardown of TestANSIX923.test_pad[128-11-11�] __

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 

Bug#871770: marked as done (python-bcrypt FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:05:53 +
with message-id 
and subject line Bug#871994: fixed in pytest 3.2.1-1
has caused the Debian Bug report #871994,
regarding python-bcrypt FTBFS: TypeError: putenv() argument 2 must be string 
without null bytes, not str
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.)


-- 
871994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bcrypt
Version: 3.1.3-1
Severity: serious

Some recent change in unstable makes python-bcrypt FTBFS:

https://tests.reproducible-builds.org/debian/history/python-bcrypt.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-bcrypt.html

...
 ERRORS 
_ ERROR at setup of test_kdf[4-password-�-\xc1+Vb5\xee\xe0L!%\x98\x97\nW\x9ag] _

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/test_bcrypt.py::test_kdf[4-password-\x00-\\xc1+Vb5\\xee\\xe0L!%\\x98\\x97\\nW\\x9ag]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
 ERROR at teardown of 
test_kdf[4-password-�-\xc1+Vb5\xee\xe0L!%\x98\x97\nW\x9ag] 

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/test_bcrypt.py::test_kdf[4-password-\x00-\\xc1+Vb5\\xee\\xe0L!%\\x98\\x97\\nW\\x9ag]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
=== warnings summary ===
tests/test_bcrypt.py::test_kdf[4-password-salt-[\xbf\x0c\xc2\x93X\x7f\x1c65U\\\'ye\x98\xd4~W\x90q\xbfB~\x9d\x8f\xbe\x84*\xba4\xd9]
  
/build/1st/python-bcrypt-3.1.3/.pybuild/pythonX.Y_2.7/build/bcrypt/__init__.py:137:
 UserWarning: Warning: bcrypt.kdf() called with only 4 round(s). This few is 
not secure: the parameter is linear, like PBKDF2.
UserWarning)

-- Docs: http://doc.pytest.org/en/latest/warnings.html
 Interrupted: stopping after 2 failures 
=== 120 passed, 1 warnings, 2 error in 0.85 seconds 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python2.7 
-m pytest -v -x
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: pytest
Source-Version: 3.2.1-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated pytest 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, 13 Aug 2017 17:34:34 +0200
Source: pytest
Binary: python-pytest python3-pytest pypy-pytest python-pytest-doc
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sebastian Ramacher 
Description:
 pypy-pytest - Simple, powerful testing in PyPy
 python-pytest - Simple, powerful testing in Python
 python-pytest-doc - Simple, powerful testing in Python - Documentation
 python3-pytest - Simple, powerful testing in 

Bug#871996: marked as done (suds FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:05:53 +
with message-id 
and subject line Bug#871994: fixed in pytest 3.2.1-1
has caused the Debian Bug report #871994,
regarding suds FTBFS: TypeError: putenv() argument 2 must be string without 
null bytes, not str
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.)


-- 
871994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: suds
Version: 0.7~git20150727.94664dd-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes suds FTBFS:

https://tests.reproducible-builds.org/debian/history/suds.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/suds.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0
rootdir: /build/1st/suds-0.7~git20150727.94664dd, inifile: setup.cfg
collected 1846 items

tests/test_argument_parser.py 
.x.x..
tests/test_cache.py 

tests/test_client.py ..
tests/test_compare_sax.py 

tests/test_date_time.py 
.
tests/test_dependency_sort.py .
tests/test_document_store.py .
tests/test_input_parameters.py x.x...
tests/test_mx.py ..
tests/test_plugin.py 
tests/test_reader.py .
tests/test_reply_handling.py ...x...
tests/test_request_construction.py 
xx.x.xxxx.xx.x.xx.
tests/test_sax_document.py .
tests/test_sax_element.py 
tests/test_sax_encoder.py 
...xxx...xxx.
tests/test_suds.py xx
tests/test_timezone.py 
tests/test_transport.py 
EE.EE.
tests/test_transport_http.py 
.......
tests/test_xsd_builtins.py 
.
tests/test_xsd_element.py 
.

 ERRORS 
__ ERROR at setup of TestRequest.test_URL[�] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'.pybuild/pythonX.Y_2.7/build/tests/test_transport.py::TestRequest::()::test_URL[\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
_ ERROR at teardown of TestRequest.test_URL[�] _

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 

Bug#871986: [Pkg-postgresql-public] Bug#871986: postgresql-9.6: PostgreSQL fails to start after upgrade

[Jacob Sparre Andersen]

Christoph Berg wrote:


Is /etc/postgresql/9.6/main/start.conf set to "auto"?


No. :-(

It appears that I simply hadn't switched from "manual" to "auto" after I 
finished the upgrade from 9.4 (Jessie) to 9.6.


I'm sorry about filling trivial problems like that in the bug database.


> I've tried "sudo service postgresql restart" without any visible effect.

postgresql.service is just a stub which forwards all actions to the
individual services like postgresql@9.6-main.service. Unfortunately
systemctl doesn't really relay any errors back if there's any.


Could "postgresql.service" be expanded such that running "service 
postgresql" will output a suggestion to use "systemctl" instead?


Thanks for the help!

/Jacob

Bug#871994: marked as pending

[Sebastian Ramacher]

tag 871994 pending
thanks

Hello,

Bug #871994 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:


https://anonscm.debian.org/cgit/python-modules/packages/pytest.git/commit/?id=76e3d56

---
commit 76e3d5655c678fc6d2330c9b988c3b2098432265
Author: Sebastian Ramacher 
Date:   Sun Aug 13 17:47:18 2017 +0200

Finalize changelog

diff --git a/debian/changelog b/debian/changelog
index c421e04..2a8b89a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pytest (3.2.1-1) unstable; urgency=medium
+
+  * New upstream release.
+- Properly escape test names when setting PYTEST_CURRENT_TEST environment
+  variable. (Closes: #871994)
+
+ -- Sebastian Ramacher   Sun, 13 Aug 2017 17:34:34 +0200
+
 pytest (3.2.0-1) unstable; urgency=medium
 
   * New upstream release.

Bug#870834: Bug is due to an API break in GLib

[Uli Schlachter]

Hi,

FYI, the bug was already reported upstream:

https://github.com/pavouk/lgi/issues/167

The reason seems to be a (GObject-introspection) API break in GLib.
Previously g_object_newv was [rename-to g_object_new], but now this
annotation is on g_object_new_with_properties().

If you ask me, this is a regression in GLib, but I guess only breaking
the C API is considered an API break and the introspection API has no
stable guarantees, right?

Cheers,
Uli
-- 
Sent from my Game Boy.

Processed: Bug#871994 marked as pending

[Debian Bug Tracking System]

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

> tag 871994 pending
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Bug #871770 [python-pytest] python-bcrypt FTBFS: TypeError: putenv() argument 2 
must be string without null bytes, not str
Bug #871996 [python-pytest] suds FTBFS: TypeError: putenv() argument 2 must be 
string without null bytes, not str
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 871694 src:bogofilter
Bug #871694 [bogofilter-common] bogofilter-common: 
bogofilter-bdb-1.2.4+dfsg1-9+b1 depends on bogofilter-common (same version),the 
latter does not exist
Bug reassigned from package 'bogofilter-common' to 'src:bogofilter'.
No longer marked as found in versions bogofilter/1.2.4+dfsg1-9.
Ignoring request to alter fixed versions of bug #871694 to the same values 
previously set
> reassign 871774 src:bogofilter
Bug #871774 [bogofilter-bdb] Broken dependencies
Bug reassigned from package 'bogofilter-bdb' to 'src:bogofilter'.
No longer marked as found in versions bogofilter/1.2.4+dfsg1-9.
Ignoring request to alter fixed versions of bug #871774 to the same values 
previously set
> forcemerge 871694 871774
Bug #871694 [src:bogofilter] bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 
depends on bogofilter-common (same version),the latter does not exist
Bug #871774 [src:bogofilter] Broken dependencies
Severity set to 'serious' from 'normal'
Merged 871694 871774
> affects 871774 bogofilter-bdb bogofilter-sqlite bogofilter-tokyocabine
Bug #871774 [src:bogofilter] Broken dependencies
Bug #871694 [src:bogofilter] bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 
depends on bogofilter-common (same version),the latter does not exist
Added indication that 871774 affects bogofilter-bdb, bogofilter-sqlite, and 
bogofilter-tokyocabine
Added indication that 871694 affects bogofilter-bdb, bogofilter-sqlite, and 
bogofilter-tokyocabine
> thanks
Stopping processing here.

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

Bug#872029: cinnamon-settings-daemon: does not remain running

[S. Porth]

Package: cinnamon-settings-daemon
Version: 3.2.1-3
Severity: grave
Justification: renders package unusable

cinnamon-settings-daemon exits during normal startup and when run manually:

** (cinnamon-settings-daemon:13693): WARNING **: You can only run one xsettings
manager at a time; exiting

** (cinnamon-settings-daemon:13693): WARNING **: Unable to start xsettings
manager: Could not initialize xsettings manager.

** (cinnamon-settings-daemon:13693): WARNING **: Name taken or bus went away -
shutting down

(cinnamon-settings-daemon:13693): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed

(cinnamon-settings-daemon:13693): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed

(cinnamon-settings-daemon:13693): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed

ps shows no other cinnamon-setting-daemon running nor any other
*.settings.daemon running

--

cinnamon-settings-daemon --debug

** (cinnamon-settings-daemon:13723): DEBUG: Starting settings manager
** (cinnamon-settings-daemon:13723): DEBUG: loading PNPIDs
** (cinnamon-settings-daemon:13723): DEBUG: Loading settings plugins from dir:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/a11y-settings.cinnamon-
settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Accessibility settings' file='/usr/lib/x86_64-linux-gnu/cinnamon-
settings-daemon-3.0/a11y-settings.cinnamon-settings-plugin'
location='a11y-settings'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/orientation.cinnamon-
settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Orientation' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/orientation.cinnamon-settings-plugin' location='orientation'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/smartcard.cinnamon-
settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Smartcard' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/smartcard.cinnamon-settings-plugin' location='smartcard'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/cursor.cinnamon-
settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Cursor' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/cursor.cinnamon-settings-plugin' location='cursor'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/power.cinnamon-settings-
plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Power' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/power.cinnamon-settings-plugin' location='power'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/background.cinnamon-
settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Background' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/background.cinnamon-settings-plugin' location='background'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/media-keys.cinnamon-
settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Media keys' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/media-keys.cinnamon-settings-plugin' location='media-keys'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/mouse.cinnamon-settings-
plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Mouse' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/mouse.cinnamon-settings-plugin' location='mouse'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/print-
notifications.cinnamon-settings-plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Print-notifications' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/print-notifications.cinnamon-settings-plugin' location='print-
notifications'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:
/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon-3.0/color.cinnamon-settings-
plugin
** (cinnamon-settings-daemon:13723): DEBUG: CinnamonSettingsPluginInfo:
name='Color' file='/usr/lib/x86_64-linux-gnu/cinnamon-settings-
daemon-3.0/color.cinnamon-settings-plugin' location='color'
** (cinnamon-settings-daemon:13723): DEBUG: Loading plugin:

Bug#872028: scikit-learn FTBFS on big endian: FAIL: sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign

[Adrian Bunk]

Source: scikit-learn
Version: 0.19.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=scikit-learn=sid

...
==
FAIL: 
sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py",
 line 291, in wrapper
return fn(*args, **kwargs)
  File 
"/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/feature_extraction/tests/test_feature_hasher.py",
 line 122, in test_hasher_alternate_sign
assert_true(len(Xt.data) < len(X[0]))
AssertionError: False is not true

--
Ran 7994 tests in 367.585s

FAILED (SKIP=74, failures=1)
debian/rules:88: recipe for target 'python-test2.7' failed
make[1]: *** [python-test2.7] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:41: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

Bug#853540: marked as done (mathic: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 15:19:11 +
with message-id 
and subject line Bug#853540: fixed in mathic 1.0~git20170606-1
has caused the Debian Bug report #853540,
regarding mathic: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mathic
Version: 1.0~git20160320-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mathic_1.0~git20160320-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
- 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-4# 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
  _ZNK6mathic13BoolParameter12argumentTypeB5cxx11Ev@Base 1.0~git20160320
  _ZNK6mathic13BoolParameter13valueAsStringB5cxx11Ev@Base 1.0~git20160320
  _ZNK6mathic13ColumnPrinter14getColumnCountEv@Base 1.0~git20130827
@@ -118,20 +118,24 @@
  
_ZNK6mathic9CliParser29pushBackRegisteredActionNamesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base
 1.0~git20160320
  
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED1Ev@Base 
1.0~git20160320
  
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED2Ev@Base 
1.0~git20160320
- 
(optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
- 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
 1.0~git20160320
+ 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 1.0~git20160320-4
+#MISSING: 1.0~git20160320-4# 
(optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-4# 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
 1.0~git20160320
  
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
 1.0~git20160320
  
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
 1.0~git20160320
- 
(optional)_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
- 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
 1.0~git20130827
+ 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE17_M_realloc_insertIJS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 1.0~git20160320-4
+#MISSING: 1.0~git20160320-4# 
(optional)_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
+#MISSING: 1.0~git20160320-4# 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
 1.0~git20130827
  

Processed: affects 871514, affects 871514

[Debian Bug Tracking System]

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

> affects 871514 postgresql-9.6
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Added indication that 871514 affects postgresql-9.6
Added indication that 871538 affects postgresql-9.6
> affects 871514 postgresql-10
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Added indication that 871514 affects postgresql-10
Added indication that 871538 affects postgresql-10
> thanks
Stopping processing here.

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

Bug#871150: marked as pending

[Mike Gabriel]

tag 871150 pending
thanks

Hello,

Bug #871150 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:

https://anonscm.debian.org/cgit/pkg-remote/freerdp2.git/commit/?id=503c311

---
commit 503c311f8556e98584ee4d12f786d948311642c9
Author: Mike Gabriel 
Date:   Sat Aug 12 22:06:49 2017 -0400

debian/changelog: post-upload add closure of #871150

diff --git a/debian/changelog b/debian/changelog
index 31a2c51..62350fe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -13,7 +13,7 @@ freerdp2 (2.0.0~git20170725.1.1648deb+dfsg1-1) unstable; 
urgency=medium
   have conflicting file names anymore
   * debian/patches
 + add 0001-Fix-gstreamer-1.0-detection.patch - fix gstreamer detection with
-  recent cmake versions
+  recent cmake versions. (Closes: #871150).
 
   [ Mike Gabriel ]
   * debian/{control,*.install,*.symbols}:

Processed: Bug#871150 marked as pending

[Debian Bug Tracking System]

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

> tag 871150 pending
Bug #871150 {Done: Mike Gabriel } 
[src:freerdp2] freerdp2: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-postgresql-public] Bug#871986: postgresql-9.6: PostgreSQL fails to start after upgrade

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #871986 [postgresql-9.6] postgresql-9.6: PostgreSQL fails to start after 
upgrade
Added tag(s) moreinfo.

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

Bug#871986: [Pkg-postgresql-public] Bug#871986: postgresql-9.6: PostgreSQL fails to start after upgrade

[Christoph Berg]

Control: tags -1 moreinfo

Re: Jacob Sparre Andersen 2017-08-13 
<150261237312.2459.10119247764903837989.report...@franka.jacob-sparre.dk>
> Last night I upgraded "postgresql-9.6" to the most recent version
> (went from 9.6.3-3 to 9.6.4-0+deb9u1).
> 
> As a part of the upgrade PostgreSQL was shut down, and it has not come
> up since then.

Hi Jacob,

can we see the output of "systemctl status postgresql@9.6-main"?

Is /etc/postgresql/9.6/main/start.conf set to "auto"?
Do you have /usr/sbin/policy-rc.d installed?

> I've tried "sudo service postgresql restart" without any visible effect.

postgresql.service is just a stub which forwards all actions to the
individual services like postgresql@9.6-main.service. Unfortunately
systemctl doesn't really relay any errors back if there's any.

Christoph

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 871770 python-pytest
Bug #871770 [src:python-bcrypt] python-bcrypt FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Bug reassigned from package 'src:python-bcrypt' to 'python-pytest'.
No longer marked as found in versions python-bcrypt/3.1.3-1.
Ignoring request to alter fixed versions of bug #871770 to the same values 
previously set
> reassign 871996 python-pytest
Bug #871996 [src:suds] suds FTBFS: TypeError: putenv() argument 2 must be 
string without null bytes, not str
Bug reassigned from package 'src:suds' to 'python-pytest'.
No longer marked as found in versions suds/0.7~git20150727.94664dd-3.
Ignoring request to alter fixed versions of bug #871996 to the same values 
previously set
> forcemerge 871994 871770 871996
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Bug #871996 [python-pytest] suds FTBFS: TypeError: putenv() argument 2 must be 
string without null bytes, not str
Added indication that 871996 affects python-cryptography
Added tag(s) upstream and fixed-upstream.
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Added tag(s) sid and buster.
Bug #871770 [python-pytest] python-bcrypt FTBFS: TypeError: putenv() argument 2 
must be string without null bytes, not str
Added indication that 871770 affects python-cryptography
Added tag(s) fixed-upstream, buster, upstream, and sid.
Merged 871770 871994 871996
> affects 871994 src:python-bcrypt src:python-cryptography src:suds
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Bug #871770 [python-pytest] python-bcrypt FTBFS: TypeError: putenv() argument 2 
must be string without null bytes, not str
Bug #871996 [python-pytest] suds FTBFS: TypeError: putenv() argument 2 must be 
string without null bytes, not str
Added indication that 871994 affects src:python-bcrypt, 
src:python-cryptography, and src:suds
Added indication that 871770 affects src:python-bcrypt, 
src:python-cryptography, and src:suds
Added indication that 871996 affects src:python-bcrypt, 
src:python-cryptography, and src:suds
> forwarded 871994 https://github.com/pytest-dev/pytest/pull/2646
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Bug #871770 [python-pytest] python-bcrypt FTBFS: TypeError: putenv() argument 2 
must be string without null bytes, not str
Bug #871996 [python-pytest] suds FTBFS: TypeError: putenv() argument 2 must be 
string without null bytes, not str
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest/pull/2646'.
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest/pull/2646'.
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest/pull/2646'.
> thanks
Stopping processing here.

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

Processed (with 3 errors): Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 871994 871770 871996
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Unable to merge bugs because:
package of #871996 is 'src:suds' not 'python-pytest'
package of #871770 is 'src:python-bcrypt' not 'python-pytest'
Failed to forcibly merge 871994: Did not alter merged bugs.

> affects 871994 src:python-bcrypt src:python-cryptography src:suds
Failed to mark 871994 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/871994 -- Unable to lock 
/org/bugs.debian.org/spool/lock/871994 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

> forwarded 871994 https://github.com/pytest-dev/pytest/pull/2646
Failed to set the forwarded-to-address of 871994: failed to get lock on 
/org/bugs.debian.org/spool/lock/871994 -- Unable to lock 
/org/bugs.debian.org/spool/lock/871994 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871994 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

> thanks
Stopping processing here.

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

Processed: Again re-assigning to astropy

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-astropy
Bug #871995 [python-pytest] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #871999 [python-pytest] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872000 [python-pytest] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872006 [python-pytest] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872008 [python-pytest] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug #872010 [python-pytest] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug reassigned from package 'python-pytest' to 'python-astropy'.
Bug reassigned from package 'python-pytest' to 'python-astropy'.
Bug reassigned from package 'python-pytest' to 'python-astropy'.
Bug reassigned from package 'python-pytest' to 'python-astropy'.
Bug reassigned from package 'python-pytest' to 'python-astropy'.
Bug reassigned from package 'python-pytest' to 'python-astropy'.
No longer marked as found in versions pytest/3.2.0-1.
No longer marked as found in versions pytest/3.2.0-1.
No longer marked as found in versions pytest/3.2.0-1.
No longer marked as found in versions pytest/3.2.0-1.
No longer marked as found in versions pytest/3.2.0-1.
No longer marked as found in versions pytest/3.2.0-1.
Ignoring request to alter fixed versions of bug #871995 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871999 to the same values 
previously set
Ignoring request to alter fixed versions of bug #872000 to the same values 
previously set
Ignoring request to alter fixed versions of bug #872006 to the same values 
previously set
Ignoring request to alter fixed versions of bug #872008 to the same values 
previously set
Ignoring request to alter fixed versions of bug #872010 to the same values 
previously set

-- 
871995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871995
871999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871999
872000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872000
872006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872006
872008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872008
872010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871995: Again re-assigning to astropy

[Ole Streicher]

Control: reassign -1 python-astropy

While I would still "INTERNALERROR"s count as errors of pytest, it seems
that there is a fix (or workaround) in astropy, which may (well,
hopefully) also fix the FTBFSs in the several packages:

https://github.com/astropy/astropy/pull/6423

I am going to add this to the next upload of astropy; therefore, I
re-assign the bug(s).

Processed: reassign 871994 to python-pytest, affects 871994, tagging 871994

[Debian Bug Tracking System]

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

> reassign 871994 python-pytest
Bug #871994 [src:python-cryptography] python-cryptography FTBFS: TypeError: 
putenv() argument 2 must be string without null bytes, not str
Bug reassigned from package 'src:python-cryptography' to 'python-pytest'.
No longer marked as found in versions python-cryptography/1.9-1.
Ignoring request to alter fixed versions of bug #871994 to the same values 
previously set
> affects 871994 python-cryptography
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Added indication that 871994 affects python-cryptography
> tags 871994 + upstream fixed-upstream
Bug #871994 [python-pytest] python-cryptography FTBFS: TypeError: putenv() 
argument 2 must be string without null bytes, not str
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#863480: marked as done ([node-static-module] Uninitialized Memory Exposure)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 13:49:42 +
with message-id 
and subject line Bug#863480: fixed in node-static-module 1.5.0-1
has caused the Debian Bug report #863480,
regarding [node-static-module] Uninitialized Memory Exposure
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.)


-- 
863480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-static-module
Version: 1.3.1-1
Severity: grave
Tags: patch security fixed-upstream
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
forwarded: https://snyk.io/vuln/npm:concat-stream:20160901

concat-stream is writable stream that concatenates strings or binary data and 
calls a callback with the result. Affected versions of the package are 
vulnerable to Uninitialized Memory Exposure.

A possible memory disclosure vulnerability exists when a value of type number 
is provided to the stringConcat() method and results in concatination of 
uninitialized memory to the stream collection.

This is a result of unobstructed use of the Buffer constructor, whose insecure 
default constructor increases the odds of memory leakage.
Details

Constructing a Buffer class with integer N creates a Buffer of length N with 
raw (not "zero-ed") memory.

In the following example, the first call would allocate 100 bytes of memory, 
while the second example will allocate the memory needed for the string "100":

// uninitialized Buffer of length 100
x = new Buffer(100);
// initialized Buffer with value of '100'
x = new Buffer('100');

concat-stream's stringConcat function uses the default Buffer constructor as-
is, making it easy to append uninitialized memory to an existing list. If the 
value of the buffer list is exposed to users, it may expose raw server side 
memory, potentially holding secrets, private data and code. This is a similar 
vulnerability to the infamous Heartbleed flaw in OpenSSL.

You can read more about the insecure Buffer behavior on our blog.

Similar vulnerabilities were discovered in request, mongoose, ws and 
sequelize.


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: node-static-module
Source-Version: 1.5.0-1

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated node-static-module 
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: Sat, 27 May 2017 16:29:32 +0200
Source: node-static-module
Binary: node-static-module
Architecture: source
Version: 1.5.0-1
Distribution: unstable
Urgency: high
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Description:
 node-static-module - convert module usage to inline expressions
Closes: 863480
Changes:
 node-static-module (1.5.0-1) unstable; urgency=high
 .
   * Security bug fix: Uninitialized Memory Exposure
 (Closes: #863480).
Checksums-Sha1:
 c03bfadef6e44a1b539cc404b1c3e4e69359d043 2758 node-static-module_1.5.0-1.dsc
 4a768c9deb5abe7af2f8d8a1b86e69ccf88ff0d2 10219 
node-static-module_1.5.0.orig.tar.gz
 1d2264845a295787507e64104c3a653852b5e18d 4000 
node-static-module_1.5.0-1.debian.tar.xz
 16d8dab09ed2cdcb9dca3e6e949e51ab9dfa926d 6894 
node-static-module_1.5.0-1_source.buildinfo
Checksums-Sha256:
 f0dc30dd0d921c87ac10bb498d72dc58fb930a2d7e54dea1f9392875a9a21802 2758 
node-static-module_1.5.0-1.dsc
 3b089685081d2380d06f0eff90be3eecb2c3d9f840139f25d2b332b07b0f9779 10219 
node-static-module_1.5.0.orig.tar.gz
 7667491a46aac6c67218b5a2892392a7fef2ea99a16e5e1143beec1ea30a7463 4000 
node-static-module_1.5.0-1.debian.tar.xz
 e5934ae1145ffcc3b59afea264e9c4ab41daf76fd814ff4bd339a8e4268ba6de 6894 
node-static-module_1.5.0-1_source.buildinfo
Files:
 0a517e39c42d2416de5f16be949ee5da 2758 web optional 
node-static-module_1.5.0-1.dsc
 

Bug#871994: python-cryptography FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str

[Tristan Seligmann]

On Sun, 13 Aug 2017 at 14:36 Adrian Bunk  wrote:

> Some recent change in unstable makes python-cryptography FTBFS:
>

Control: reassign -1 python-pytest
Control: affects -1 python-cryptography
Control: tags -1 + upstream fixed-upstream

This is caused by an upstream bug in pytest, that should be fixed by pytest
3.2.1: https://github.com/pytest-dev/pytest/issues/2644

Bug#872020: frobby FTBFS: latex: not found

[Adrian Bunk]

Source: frobby
Version: 0.9.0-3
Severity: serious

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

...
for i in 1 2 3; do latex -output-directory=bin/doc/ doc/manual.tex; done
/bin/sh: 1: latex: not found
/bin/sh: 1: latex: not found
/bin/sh: 1: latex: not found
Makefile:253: recipe for target 'docPs' failed
make[2]: *** [docPs] Error 127

Bug#872017: zsh-syntax-highlighting FTBFS with zsh 5.4.1-1

[Adrian Bunk]

Source: zsh-syntax-highlighting
Version: 0.5.0-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zsh-syntax-highlighting.html

...
   dh_auto_test
make -j1 test
make[1]: Entering directory '/build/1st/zsh-syntax-highlighting-0.5.0'
Running test brackets
# cursor-matchingbracket-line-finish
1..1
ok 1 - [11,11] «]»
# cursor-matchingbracket
1..1
ok 1 - [9,9] «)»
# empty-styles
1..1
ok 1 - [1,5] «: (x)»
# loop-styles
1..14
ok 1 - [3,3] «(»
ok 2 - [4,4] «{»
ok 3 - [5,5] «[»
ok 4 - [6,6] «(»
ok 5 - [7,7] «{»
ok 6 - [8,8] «[»
ok 7 - [9,9] «(»
ok 8 - [11,11] «)»
ok 9 - [12,12] «]»
ok 10 - [13,13] «}»
ok 11 - [14,14] «)»
ok 12 - [15,15] «]»
ok 13 - [16,16] «}»
ok 14 - [17,17] «)»
# mismatch-patentheses
1..4
ok 1 - [6,6] «(»
ok 2 - [7,7] «{»
ok 3 - [9,9] «}»
ok 4 - [10,10] «]»
# near-quotes
1..3
ok 1 - [3,3] «{»
ok 2 - [4,8] «"{x}"»
ok 3 - [9,9] «}»
# nested-parentheses
1..6
ok 1 - [7,7] «(»
ok 2 - [14,14] «{»
ok 3 - [15,15] «(»
ok 4 - [17,17] «)»
ok 5 - [23,23] «}»
ok 6 - [24,24] «)»
# nested-quote
1..1
not ok 1 - [3,9] «"\"{x"» - expected "", observed "bracket-error". # TODO 
'issue #303'
# quoted-patentheses
1..1
ok 1 - [1,16] «echo "foo ( bar"»
# simple-parentheses
1..4
ok 1 - [6,6] «(»
ok 2 - [7,7] «{»
ok 3 - [9,9] «}»
ok 4 - [10,10] «)»
# unclosed-patentheses
1..3
ok 1 - [6,6] «(»
ok 2 - [7,7] «{»
ok 3 - [9,9] «}»
# unclosed-patentheses2
1..3
ok 1 - [6,6] «{»
ok 2 - [8,8] «}»
ok 3 - [9,9] «)»
Running test main
# alias-assignment1
1..1
ok 1 - [1,3] «x=y»
# alias
/build/1st/zsh-syntax-highlighting-0.5.0/./highlighters/main/test-data/alias.zsh:32:
 defining function based on alias `alias1'
/build/1st/zsh-syntax-highlighting-0.5.0/./highlighters/main/test-data/alias.zsh:32:
 parse error near `()'
Bail out! Either 'PREBUFFER' or 'BUFFER' must be declared and non-blank
Bail out! output on stderr
Running test pattern
# rm-rf
1..1
ok 1 - [1,8] «rm -rf /»
Makefile:55: recipe for target 'test' failed
make[1]: *** [test] Error 2
make[1]: Leaving directory '/build/1st/zsh-syntax-highlighting-0.5.0'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:16: recipe for target 'build' failed
make: *** [build] Error 2

Processed: Re: reassigning bug to gcc

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:lxc
Bug #853531 [gcc-7] lxc: ftbfs with GCC-7
Bug reassigned from package 'gcc-7' to 'src:lxc'.
Ignoring request to alter found versions of bug #853531 to the same values 
previously set
Ignoring request to alter fixed versions of bug #853531 to the same values 
previously set

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

Bug#871280: marked as done (libfrobby0: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 13:35:52 +
with message-id 
and subject line Bug#871280: fixed in frobby 0.9.0-3
has caused the Debian Bug report #871280,
regarding libfrobby0: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfrobby0
Version: 0.9.0-2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: frobby
Source-Version: 0.9.0-3

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated frobby 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: Sat, 12 Aug 2017 23:36:41 -0400
Source: frobby
Binary: frobby libfrobby0 libfrobby-dev libfrobby-doc
Architecture: source amd64 all
Version: 0.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 frobby - Computations with monomial ideals
 libfrobby-dev - Computations with monomial ideals (development tools)
 libfrobby-doc - Computations with monomial ideals (library documentation)
 libfrobby0 - Computations with monomial ideals (shared library)
Closes: 871280
Changes:
 frobby (0.9.0-3) unstable; urgency=medium
 .
   * debian/compat
 - Bump dephelper compatibility level to 10.
   * debian/control
 - Tidy up using wrap-and-sort.
 - Bump Standards-Version to 4.0.1.
 - Bump versioned dependency on debhelper to >= 10.
 - Add g++ (>= 4:7) to Build-Depends.
 - Add Build-Depends-Indep.
 - Use https protocol for Vcs-Browser.
 - Remove libfrobby-dbg in 

Bug#853531: reassigning bug to gcc

[Matthias Klose]

Control: reassign -1 src:lxc

On 13.08.2017 08:24, Tomas Pospisek wrote:
> reassign 853531 gcc-7
> thanks
> 
> Stéphane Graber wrote:
> 
>> This issue is a compiler bug, tracked upstream.
>>
>> LXC upstreams has received reports of this affecting ArchLinux and
>> OpenSUSE after they switched to gcc 7.1.
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
> 
> So it appears that this bug should be correctly reassigned to gcc-7, which 
> I've
> done here.

no, it should not, unless you want to have lxc outside of testing. It's a wrong
warning which can be easily worked around in the lxc sources.

Processed: Re-assigning bugs to pytest

[Debian Bug Tracking System]

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

> reassign 871995 python-pytest 3.2.0-1
Bug #871995 [src:astroscrappy] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug reassigned from package 'src:astroscrappy' to 'python-pytest'.
No longer marked as found in versions astroscrappy/1.0.5-1.
Ignoring request to alter fixed versions of bug #871995 to the same values 
previously set
Bug #871995 [python-pytest] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Marked as found in versions pytest/3.2.0-1.
> affects 871995 astroscrappy
Bug #871995 [python-pytest] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Added indication that 871995 affects astroscrappy
> reassign 871999 python-pytest 3.2.0-1
Bug #871999 [src:spectral-cube] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug reassigned from package 'src:spectral-cube' to 'python-pytest'.
No longer marked as found in versions spectral-cube/0.4.0-3.
Ignoring request to alter fixed versions of bug #871999 to the same values 
previously set
Bug #871999 [python-pytest] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Marked as found in versions pytest/3.2.0-1.
> affects 871999 spectral-cube
Bug #871999 [python-pytest] spectral-cube FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Added indication that 871999 affects spectral-cube
> reassign 872000 python-pytest 3.2.0-1
Bug #872000 [src:montage-wrapper] montage-wrapper FTBFS: AttributeError: 
'NoneType' object has no attribute 'lineno'
Bug reassigned from package 'src:montage-wrapper' to 'python-pytest'.
No longer marked as found in versions montage-wrapper/0.9.9-1.
Ignoring request to alter fixed versions of bug #872000 to the same values 
previously set
Bug #872000 [python-pytest] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Marked as found in versions pytest/3.2.0-1.
> affects 872000 montage-wrapper
Bug #872000 [python-pytest] montage-wrapper FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Added indication that 872000 affects montage-wrapper
> reassign 872006 python-pytest 3.2.0-1
Bug #872006 [src:python-drizzle] python-drizzle FTBFS: AttributeError: 
'NoneType' object has no attribute 'lineno'
Bug reassigned from package 'src:python-drizzle' to 'python-pytest'.
No longer marked as found in versions python-drizzle/1.10-1.
Ignoring request to alter fixed versions of bug #872006 to the same values 
previously set
Bug #872006 [python-pytest] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Marked as found in versions pytest/3.2.0-1.
> affects 872006 python-drizzle
Bug #872006 [python-pytest] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Added indication that 872006 affects python-drizzle
> reassign 872008 python-pytest 3.2.0-1
Bug #872008 [src:astroplan] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Bug reassigned from package 'src:astroplan' to 'python-pytest'.
No longer marked as found in versions astroplan/0.2.1-2.
Ignoring request to alter fixed versions of bug #872008 to the same values 
previously set
Bug #872008 [python-pytest] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Marked as found in versions pytest/3.2.0-1.
> affects 872008 astroplan
Bug #872008 [python-pytest] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Added indication that 872008 affects astroplan
> reassign 872010 python-pytest 3.2.0-1
Bug #872010 [src:ccdproc] ccdproc FTBFS: AttributeError: 'NoneType' object has 
no attribute 'lineno'
Bug reassigned from package 'src:ccdproc' to 'python-pytest'.
No longer marked as found in versions ccdproc/1.2.0-2.
Ignoring request to alter fixed versions of bug #872010 to the same values 
previously set
Bug #872010 [python-pytest] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Marked as found in versions pytest/3.2.0-1.
> affects 872010 ccdproc
Bug #872010 [python-pytest] ccdproc FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Added indication that 872010 affects ccdproc
> forcemerge 871995 871999 872000 872006 872010 872008
Bug #871995 [python-pytest] astroscrappy FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Bug #872006 [python-pytest] python-drizzle FTBFS: AttributeError: 'NoneType' 
object has no attribute 'lineno'
Removed indication that 872006 affects python-drizzle
Added indication that 872006 affects astroscrappy
Added tag(s) buster and sid.
Bug #872008 [python-pytest] astroplan FTBFS: AttributeError: 'NoneType' object 
has no attribute 'lineno'
Removed indication that 872008 affects astroplan
Added indication that 872008 affects astroscrappy
Added tag(s) buster and sid.
Bug #871999 [python-pytest] spectral-cube FTBFS: 

Bug#871927: forwarded upstream

[Ghislain Vaillant]

control: forwarded -1 
https://github.com/QuantStack/xtensor-python/issues/102

Bug#871992: juffed FTBFS on !amd64 64bit: missing symbol

[Alf Gaida]

Right, but you missed one point - it is missed in arm64, not amd64. And
ppc64el, s390x, alpha, ppc64 and some of the architectures that are not
built yet. And your are right, it is serious and I'm aware of it.

Switching from optional|c++ to c++|arch= !foo !bar !baz has it's up- and
downsides. The upside is: it is more readable and more precise, the
downside is: i have to collect the missed symbols after this build and
fix the symbols again. But it is not wasted work or build time as it
will ease the maintainance for future uploads.

Cheers Alf




signature.asc
Description: OpenPGP digital signature

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 871942 52.3.0esr-1
Bug #871942 [firefox-esr] firefox-esr: Firefox will not render the YouTube page 
correctly nor play YT videos rel 8/12/17.
Marked as found in versions firefox-esr/52.3.0esr-1.
> thanks
Stopping processing here.

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

Bug#871344: marked as done (golang-1.6: FTBFS: test fails)

[Debian Bug Tracking System]

Your message dated Sun, 13 Aug 2017 16:04:46 +0300
with message-id <20170813130446.oalakbqgydtnpzij@localhost>
and subject line golang-1.6 is Extra-Source-Only
has caused the Debian Bug report #871344,
regarding golang-1.6: FTBFS: test fails
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.)


-- 
871344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.6
Version: 1.6.3-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> set -ex; \
>   cd src; \
>   export PATH="/<>/bin:$PATH"; \
>   eval "$(go tool dist env)"; \
>   bash run.bash -k -no-rebuild;
> + cd src
> + export 
> PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + go tool dist env
> + eval CC="gcc"
> CC_FOR_TARGET="gcc"
> GOROOT="/<>"
> GOBIN="/<>/bin"
> GOARCH="amd64"
> GOOS="linux"
> GOHOSTARCH="amd64"
> GOHOSTOS="linux"
> GOTOOLDIR="/<>/pkg/tool/linux_amd64"
> + CC=gcc
> + CC_FOR_TARGET=gcc
> + GOROOT=/<>
> + GOBIN=/<>/bin
> + GOARCH=amd64
> + GOOS=linux
> + GOHOSTARCH=amd64
> + GOHOSTOS=linux
> + GOTOOLDIR=/<>/pkg/tool/linux_amd64
> + bash run.bash -k -no-rebuild
> 
> # Testing packages.
> okarchive/tar 0.038s
> okarchive/zip 0.109s
> okbufio   0.127s
> okbytes   0.147s
> okcompress/bzip2  0.191s
> okcompress/flate  0.424s
> okcompress/gzip   0.074s
> okcompress/lzw0.022s
> okcompress/zlib   0.080s
> okcontainer/heap  0.049s
> okcontainer/list  0.007s
> okcontainer/ring  0.033s
> okcrypto/aes  0.027s
> okcrypto/cipher   0.005s
> okcrypto/des  0.039s
> okcrypto/dsa  0.005s
> okcrypto/ecdsa0.028s
> okcrypto/elliptic 0.093s
> okcrypto/hmac 0.019s
> okcrypto/md5  0.011s
> okcrypto/rand 0.011s
> okcrypto/rc4  0.224s
> okcrypto/rsa  0.229s
> okcrypto/sha1 0.032s
> okcrypto/sha256   0.072s
> okcrypto/sha512   0.005s
> okcrypto/subtle   0.019s
> okcrypto/tls  1.621s
> okcrypto/x509 2.221s
> okdatabase/sql0.056s
> okdatabase/sql/driver 0.003s
> okdebug/dwarf 0.017s
> okdebug/elf   0.034s
> okdebug/gosym 0.448s
> okdebug/macho 0.023s
> okdebug/pe0.040s
> okdebug/plan9obj  0.004s
> okencoding/ascii850.003s
> okencoding/asn1   0.016s
> okencoding/base32 0.022s
> okencoding/base64 0.052s
> okencoding/binary 0.033s
> okencoding/csv0.004s
> okencoding/gob0.060s
> okencoding/hex0.025s
> okencoding/json   0.417s
> okencoding/pem0.025s
> okencoding/xml0.013s
> okerrors  0.089s
> okexpvar  0.029s
> okflag0.047s
> okfmt 0.198s
> okgo/ast  0.006s
> okgo/build0.118s
> okgo/constant 0.011s
> okgo/doc  0.047s
> okgo/format   0.088s
> okgo/internal/gccgoimporter   0.009s
> okgo/internal/gcimporter  0.392s
> okgo/parser   0.072s
> okgo/printer  0.563s
> okgo/scanner  0.012s
> okgo/token0.062s
> okgo/types1.119s
> okhash/adler320.024s
> okhash/crc32  0.016s
> okhash/crc64  0.018s
> okhash/fnv0.013s
> okhtml0.028s
> okhtml/template   0.039s
> okimage   0.180s
> okimage/color 0.122s
> okimage/draw  0.118s
> okimage/gif   0.124s
> okimage/jpeg  0.303s
> okimage/png   0.089s
> okindex/suffixarray   0.066s
> okinternal/golang.org/x/net/http2/hpack   0.026s
> okinternal/singleflight   0.014s
> okinternal/trace  0.003s
> okio  0.021s
> okio/ioutil   0.043s
> oklog 0.012s
> oklog/syslog  2.052s
> okmath0.005s
> okmath/big0.557s
> okmath/cmplx  0.004s
> okmath/rand   0.140s
> okmime0.056s
> okmime/multipart  0.913s
> okmime/quotedprintable0.405s
> oknet 1.515s
> oknet/http9.531s
> oknet/http/cgi0.644s
> oknet/http/cookiejar  0.018s
> oknet/http/fcgi   0.033s
> oknet/http/httptest   0.058s
> oknet/http/httputil   0.065s
> oknet/http/internal   0.015s
> oknet/internal/socktest   0.046s
> oknet/mail0.034s
> ok   

Bug#869670: Dependency missing

[Andrea Villa]

The reason for this bug is a dependency problem:

The current sid kernel is linux-image-4.11.0-2-amd64
->
corresponding headers are linux-headers-4.11.0-2-amd64:
->
they depend on linux-headers-4.11.0-2-common (= 4.11.11-1+b1)
->
there is no such version (only 4.11.11-1 *NO +b1*), maybe never made it
from experimental?

Only work around is to boot to an older kernel and install the
corresponding linux-headers-VERSION package.

Do not try to fix by installing/upgrading meta-package linux-headers-amd64
since in sid this depends on linux-headers-4.11.0-2-amd64 thus initiating
the broken dependency links described above.
Don't try to fix 4.11 kernel (it's EOL anyway), we should probably just
wait for 4.12 coming from experimental soon.

Hope this helps you folks!

Bests,

Andrea

Bug#872011: photutils FTBFS with pytest 3.2.0

[Adrian Bunk]

Source: photutils
Version: 0.3.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/photutils.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ..

Running tests with photutils version 0.3.2.
Running tests in lib.linux-x86_64-2.7/photutils.

Date: 2017-08-12T20:33:33

Platform: Linux-4.9.0-3-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python2.7

Full Python Version: 
2.7.13+ (default, Jul 19 2017, 18:15:03) 
[GCC 6.4.0 20170704]

encodings: sys: ascii, locale: ANSI_X3.4-1968, filesystem: ANSI_X3.4-1968, 
unicode bits: 20
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.12.1
Scipy: not available
Matplotlib: not available
Pandas: not available
Astropy: 2.0.1
scikit-image: not available
Using Astropy options: remote_data: none.

rootdir: /tmp/photutils-test-o_Rm6f, inifile: setup.cfg
collecting ... collected 1058 items / 1 errors

 ERRORS 
_ ERROR collecting lib.linux-x86_64-2.7/photutils/psf/tests/test_photometry.py _
/usr/lib/python2.7/dist-packages/_pytest/runner.py:191: in __init__
self.result = func()
/usr/lib/python2.7/dist-packages/_pytest/runner.py:370: in 
lambda: list(collector.collect()),
/usr/lib/python2.7/dist-packages/_pytest/python.py:389: in collect
return super(Module, self).collect()
/usr/lib/python2.7/dist-packages/_pytest/python.py:330: in collect
res = self.makeitem(name, obj)
/usr/lib/python2.7/dist-packages/_pytest/python.py:342: in makeitem
collector=self, name=name, obj=obj)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:745: in 
__call__
return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:339: in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:334: in 

_MultiCall(methods, kwargs, hook.spec_opts).execute()
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:613: in 
execute
return _wrapped_call(hook_impl.function(*args), self.execute)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:250: in 
_wrapped_call
wrap_controller.send(call_outcome)
/usr/lib/python2.7/dist-packages/_pytest/python.py:188: in 
pytest_pycollect_makeitem
res = list(collector._genfunctions(name, obj))
/usr/lib/python2.7/dist-packages/_pytest/python.py:362: in _genfunctions
self.ihook.pytest_generate_tests(metafunc=metafunc)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:745: in 
__call__
return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:339: in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:334: in 

_MultiCall(methods, kwargs, hook.spec_opts).execute()
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:614: in 
execute
res = hook_impl.function(*args)
/usr/lib/python2.7/dist-packages/_pytest/python.py:113: in pytest_generate_tests
metafunc.parametrize(*marker.args, **marker.kwargs)
/usr/lib/python2.7/dist-packages/_pytest/python.py:781: in parametrize
for x in argvalues]
/usr/lib/python2.7/dist-packages/_pytest/mark.py:66: in extract_from
warnings.warn(MARK_PARAMETERSET_UNPACKING)
E   RemovedInPytest4Warning: Applying marks directly to parameters is 
deprecated, please use pytest.param(..., marks=...) instead.
E   For more details, see: https://docs.pytest.org/en/latest/parametrize.html
=== warnings summary ===
None
  [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
!!! Interrupted: 1 errors during collection 
= 1 warnings, 1 error in 7.49 seconds ==
debian/rules:18: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 2
make[1]: Leaving directory '/build/1st/photutils-0.3.2'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2

Bug#872010: ccdproc FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: ccdproc
Version: 1.2.0-2
Severity: serious

Some recent change in unstable makes ccdproc FTBFS:

https://tests.reproducible-builds.org/debian/history/ccdproc.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ccdproc.html

...
ccdproc/utils/slices.py::ccdproc.utils.slices.slice_from_string PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_needs_enclosing_brackets[1:2]
 PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_needs_enclosing_brackets[[1:2]
 PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_needs_enclosing_brackets[1:2]]
 PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[None-None--1] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[5-10-None] PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[None-25-None] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[2-30-3] PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[30-None--2] PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[None-None-None] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_spaces[  [ 1:  45]] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_spaces[[ 1  :4 5]] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_spaces[  [1:45] ] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_2d PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_fits_style PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_fits_inverted PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_empty PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_bad_fits_slice PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_fits_wildcard PASSED
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
169, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 

Bug#872008: astroplan FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: astroplan
Version: 0.2.1-2
Severity: serious

Some recent change in unstable makes astroplan FTBFS:

https://tests.reproducible-builds.org/debian/history/astroplan.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/astroplan.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0

Running tests with astroplan version 0.2.1.
Running tests in lib.linux-x86_64-2.7/astroplan docs.

Date: 2018-09-15T02:47:00

Platform: Linux-4.9.0-3-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python2.7

Full Python Version: 
2.7.13+ (default, Jul 19 2017, 18:15:03) 
[GCC 6.4.0 20170704]

encodings: sys: ascii, locale: ANSI_X3.4-1968, filesystem: ANSI_X3.4-1968, 
unicode bits: 20
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.12.1
Scipy: not available
Matplotlib: 2.0.0
Pandas: not available
Astropy: 2.0.1
pytz: 2017.2
pyephem: not available
matplotlib: 2.0.0
nose: not available
pytest-mpl: not available
Using Astropy options: remote_data: none.

rootdir: /tmp/astroplan-test-c0dPUn, inifile: setup.cfg
collected 104 items

astroplan/constraints.py 
astroplan/observer.py .
astroplan/target.py .
astroplan/plots/tests/test_sky.py .
astroplan/tests/test_constraints.py 
astroplan/tests/test_moon.py .
astroplan/tests/test_observer.py ..
astroplan/tests/test_scheduling.py 
astroplan/tests/test_target.py ...
astroplan/tests/test_utils.py s...
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
169, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> 

Processed: dh_strip fails randomly "No such file or directory" during parallel builds

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:fuse
Bug #872007 [debhelper] dh_strip fails randomly "No such file or directory" 
during parallel builds
Added indication that 872007 affects src:fuse

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

Bug#872007: dh_strip fails randomly "No such file or directory" during parallel builds

[Helmut Grohne]

Package: debhelper
Version: 10.7.2
Severity: serious
File: /usr/bin/dh_strip
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:fuse

Hi Niels,

I noticed that cross building fuse failed. Once. The issue isn't
reproducible, at least not easily. It also FTBFSed on the jenkins
reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/fuse.html

| dh_strip --dbg-package=fuse-dbg
| chmod: cannot access 
'debian/fuse-dbg/usr/lib/debug/.build-id/2b/bbc8403aec6a1ea2abd3cf6467439e0c4ae1ed.debug':
 No such file or directory
| dh_strip: chmod 0644 -- 
debian/fuse-dbg/usr/lib/debug/.build-id/2b/bbc8403aec6a1ea2abd3cf6467439e0c4ae1ed.debug
 returned exit code 1

I attempted to natively build fuse 13 times now (with parallel=100) and
it failed twice like that. Without parallel, I couldn't reproduce it at
all.

Whatever is broken over here, it likely resides in debhelper and makes
fuse FTBFS randomly. I wish I could provide more details.

Helmut