date:20170916

Bug#872528: marked as done (golang-github-grpc-ecosystem-grpc-gateway FTBFS: test failure)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sun, 17 Sep 2017 13:49:34 +0800
with message-id 

and subject line Re: golang-github-grpc-ecosystem-grpc-gateway FTBFS: test 
failure
has caused the Debian Bug report #872528,
regarding golang-github-grpc-ecosystem-grpc-gateway FTBFS: test failure
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.)


-- 
872528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-grpc-ecosystem-grpc-gateway
Version: 1.1.0+git20170127.54.6863684-1
Severity: serious

Some recent change in unstable makes
golang-github-grpc-ecosystem-grpc-gateway FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-grpc-ecosystem-grpc-gateway.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-grpc-ecosystem-grpc-gateway.html

...
=== RUN   TestJSONPbMarshal
--- FAIL: TestJSONPbMarshal (0.00s)
marshal_jsonpb_test.go:108: got = 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 enum_value:ONE oneof_string:"bar" 
map_value: map_value: ; want 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 enum_value:ONE oneof_string:"bar" 
map_value: map_value: ; spec={false 
true  false 0x7fe8b0}
=== RUN   TestJSONPbMarshalFields
--- PASS: TestJSONPbMarshalFields (0.00s)
=== RUN   TestJSONPbUnmarshal
--- PASS: TestJSONPbUnmarshal (0.00s)
=== RUN   TestJSONPbUnmarshalFields
--- PASS: TestJSONPbUnmarshalFields (0.00s)
=== RUN   TestJSONPbEncoder
--- FAIL: TestJSONPbEncoder (0.00s)
marshal_jsonpb_test.go:322: got = 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 oneof_string:"bar" map_value: map_value: ; want 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 oneof_string:"bar" map_value: map_value: ; spec={false true  false 0x7ff220}
=== RUN   TestJSONPbEncoderFields
--- PASS: TestJSONPbEncoderFields (0.00s)
=== RUN   TestJSONPbDecoder
--- PASS: TestJSONPbDecoder (0.00s)
=== RUN   TestJSONPbDecoderFields
--- PASS: TestJSONPbDecoderFields (0.00s)
=== RUN   TestMarshalerForRequest
--- PASS: TestMarshalerForRequest (0.00s)
=== RUN   TestMuxServeHTTP
--- PASS: TestMuxServeHTTP (0.00s)
=== RUN   TestPopulateParameters
proto: no coders for runtime_test.proto2Message
proto: no encoder for NestedNonNull runtime_test.proto2Message [GetProperties]
2017/08/17 21:02:44 too many field values: uint64_value
--- PASS: TestPopulateParameters (0.00s)
=== RUN   TestPopulateParametersWithFilters
--- PASS: TestPopulateParametersWithFilters (0.00s)
FAIL
FAILgithub.com/grpc-ecosystem/grpc-gateway/runtime  0.031s
?   github.com/grpc-ecosystem/grpc-gateway/runtime/internal [no test files]
?   
github.com/grpc-ecosystem/grpc-gateway/third_party/googleapis/google/api
[no test files]
=== RUN   TestMaxCommonPrefix
--- PASS: TestMaxCommonPrefix (0.00s)
=== RUN   TestAdd
--- PASS: TestAdd (0.00s)
PASS
ok  github.com/grpc-ecosystem/grpc-gateway/utilities0.016s
dh_auto_test: go test -v -p 15 github.com/grpc-ecosystem/grpc-gateway/examples 
github.com/grpc-ecosystem/grpc-gateway/examples/clients/abe 
github.com/grpc-ecosystem/grpc-gateway/examples/clients/echo 
github.com/grpc-ecosystem/grpc-gateway/examples/examplepb 
github.com/grpc-ecosystem/grpc-gateway/examples/server 
github.com/grpc-ecosystem/grpc-gateway/examples/server/cmd/example-server 
github.com/grpc-ecosystem/grpc-gateway/examples/sub 
github.com/grpc-ecosystem/grpc-gateway/examples/sub2 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/generator 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/gengateway 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/httprule 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger 
github.com/grpc-ecosyst
 em/grpc-gateway/runtime 
github.com/grpc-ecosystem/grpc-gateway/runtime/internal

Bug#862431: marked as done (m4/python.m4 should list recent python3.x versions)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sun, 17 Sep 2017 04:19:14 +
with message-id 
and subject line Bug#872052: fixed in automake-1.15 1:1.15.1-3
has caused the Debian Bug report #872052,
regarding m4/python.m4 should list recent python3.x versions
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.)


-- 
872052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:automake-1.15
Version: 1:1.15-6
Severity: important
Tags: sid buster
User: debian-pyt...@lists.debian.org
Usertags: python3.6

m4/python.m4 only lists python3 versions up to 3.3. Please add newer ones as
well, maybe up to 3.7 (already used in Python development) or 3.8.  The missing
python3 versions will make packages fail to build which are supporting all
Python 3 versions in Debian.
--- End Message ---
--- Begin Message ---
Source: automake-1.15
Source-Version: 1:1.15.1-3

We believe that the bug you reported is fixed in the latest version of
automake-1.15, 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.
Eric Dorland  (supplier of updated automake-1.15 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, 16 Sep 2017 21:41:45 -0400
Source: automake-1.15
Binary: automake
Architecture: source
Version: 1:1.15.1-3
Distribution: unstable
Urgency: medium
Maintainer: Eric Dorland 
Changed-By: Eric Dorland 
Description:
 automake   - Tool for generating GNU Standards-compliant Makefiles
Closes: 872052
Changes:
 automake-1.15 (1:1.15.1-3) unstable; urgency=medium
 .
   * Acknowledge NMU. (Closes: #872052)
   * debian/control: Upgrade Standards-Version to 4.1.0.
   * debian/copyright: Switch URLs to https.
   * debian/patches/0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch:
 $SOURCE_DATE_EPOCH support for mdate-sh.
Checksums-Sha1:
 485b415f5bad0fe9bfd5e6408ba1b05a3b4f7a35 2264 automake-1.15_1.15.1-3.dsc
 7ce9dea25968320d731476788aa9034cbd4db005 13748 
automake-1.15_1.15.1-3.debian.tar.xz
 9fe96bbfd9d29bc299c11d8e95bb172174c7f5a7 14842 
automake-1.15_1.15.1-3_amd64.buildinfo
Checksums-Sha256:
 f19b0bbcf91ff11908730d64d6377d0d223dd70e32ac7946a8e745c0ed82dac8 2264 
automake-1.15_1.15.1-3.dsc
 029739edc3fee410b74af5df2de2f9742bf10720230f8cbac76fab100b6e7b2a 13748 
automake-1.15_1.15.1-3.debian.tar.xz
 8b4b2797ca610dae38a1855f7319c701547b160af9d17fe2a2ce80e26f4a6ba0 14842 
automake-1.15_1.15.1-3_amd64.buildinfo
Files:
 209c471bff29f832c7651abac8b0fd26 2264 devel optional automake-1.15_1.15.1-3.dsc
 994ee089cfefc7a21f1869b1ea037cdd 13748 devel optional 
automake-1.15_1.15.1-3.debian.tar.xz
 9b94c3f1d88f545c2920cf6e0bfb3d7a 14842 devel optional 
automake-1.15_1.15.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ88SKPcm/VtHTOliwlb71QAiHpMFAlm98goACgkQwlb71QAi
HpPqYg/+KfqEIJ/lbLAvPGU/CCfXf68u9wxVesloUOxs2rKU3D29oZKM/HH5JiEE
VUOzcDTqSDFw64viuH3mSeRD5I2fChSUPa33d0dvURgqiYO6xshwiP+zxTJWcEwi
MyggVAARecig49ZzzrWBaf11dsGi8A74RvGvtzcRDUdmDO8ZlV+7ueUE3PMjwXFI
TfR6N0JgtXfNOWhlQ2iGIHMVaGxPdsN+qMJOPE+rzvjgXkAPro9M9AukOKE0NcHM
gtEZi0BgvIXlgRqoxcmVv1MMCh5eJEqWLGwBHht/KsbNZeRwOQLLo9BjRqaf2OhH
sIxCXbAe8OjCu2k+Enfg0wifaZITwBRa7ITmd1V8Cs5cZfotdam5VKftLgnhz3GB
k7Sb1fDmvu/n0XHP2Pyey4tB70GB3jtRLbvP68ZzfCqOkaZjLqyH+6VMelLLFo9l
LIrwBYC4PSRcZKA+fvLOR2qfe41XysRfEmwtzSvSp22vpZf7l9SYdfwJJhNGEb2A
VVOn7e3JRosmi8ny4rwQruJ5xEQPNmPcvpByru4xJztrrvxpCD9em0K/GLVjWgWO
gUZa1OgJV61puYQ+4gDJV1etZrumlZEYjYcnLExB6E6S8klcewZV6K36LAF3DID6
FkWOrBPyAVonTHbOMLZ9g9z5YKLHJ8iLbfnfhJVOdASGNNALxoQ=
=YptU
-END PGP SIGNATURE End Message ---

Bug#875995: sump-logicanalyzer: missing B-D: ant

2017-09-16 Thread Andreas Beckmann

Source: sump-logicanalyzer
Version: 0.8-1
Severity: serious
Justification: fails to build from source

Hi,

sump-logicanalyzer cannot be built in experimental any more:

 fakeroot debian/rules clean
dh clean 
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_auto_clean
dh_auto_clean: Compatibility levels before 9 are deprecated (level 8 in use)
   debian/rules override_dh_clean
make[1]: Entering directory '/build/sump-logicanalyzer-0.8'
cd client && ant clean
/bin/sh: 1: ant: not found
debian/rules:19: recipe for target 'override_dh_clean' failed
make[1]: *** [override_dh_clean] Error 127
make[1]: Leaving directory '/build/sump-logicanalyzer-0.8'
debian/rules:13: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


Cheers,

Andreas


sump-logicanalyzer_0.8-1.log.gz
Description: application/gzip

Bug#875993: yamcha: FTBFS with GCC 7

2017-09-16 Thread Andreas Beckmann

Package: yamcha
Version: 0.33-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

yamcha cannot be built any longer in experimental:

In file included from param.cpp:32:0:
param.cpp: In member function 'bool YamCha::Param::open(const char*, const 
YamCha::Option*)':
../config.h:76:17: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
 #define PACKAGE "yamcha"
 ^
param.cpp:186:14: note: in expansion of macro 'PACKAGE'
 ptr[0] = PACKAGE;
  ^~~
feature_index.cpp: In member function 'bool 
YamCha::FeatureIndex::setFeature(const string&, int)':
feature_index.cpp:150:62: error: no matching function for call to 
'make_pair(const int&, const int&)'
feature_set.insert (std::make_pair ( *rit, *cit ) );
  ^
In file included from /usr/include/c++/7/utility:70:0,
 from /usr/include/c++/7/tuple:38,
 from /usr/include/c++/7/functional:54,
 from feature_index.cpp:23:
/usr/include/c++/7/bits/stl_pair.h:519:5: note: candidate: template constexpr std::pair::__type, 
typename std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _
T2&&)
 make_pair(_T1&& __x, _T2&& __y)
 ^
/usr/include/c++/7/bits/stl_pair.h:519:5: note:   template argument 
deduction/substitution failed:
feature_index.cpp:150:51: note:   cannot convert 
'rit.std::_Rb_tree_const_iterator::operator*()' (type 'const int') to type 
'int&&'
feature_set.insert (std::make_pair ( *rit, *cit ) );
   ^~~~
feature_index.cpp:154:66: error: no matching function for call to 
'make_pair(const int&, const int&)'
bow_feature_set.insert (std::make_pair ( *rit, *cit ) );
  ^
In file included from /usr/include/c++/7/utility:70:0,
 from /usr/include/c++/7/tuple:38,
 from /usr/include/c++/7/functional:54,
 from feature_index.cpp:23:
/usr/include/c++/7/bits/stl_pair.h:519:5: note: candidate: template constexpr std::pair::__type, 
typename std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _
T2&&)
...


Andreas


yamcha_0.33-1.log.gz
Description: application/gzip

Processed: notfixed 820416 in 17.0~beta5+dfsg1-4, fixed 820416 in 2:17.0~beta5+dfsg1-4, fixed 502180 in 3.14.1-2 ...

2017-09-16 Thread Debian Bug Tracking System

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

> # fixing up bug metadata to allow archival
> notfixed 820416 17.0~beta5+dfsg1-4
Bug #820416 {Done: Santiago Vila } [src:kodi] kodi: FTBFS in 
testing (Segmentation fault)
The source 'kodi' and version '17.0~beta5+dfsg1-4' do not appear to match any 
binary packages
No longer marked as fixed in versions 17.0~beta5+dfsg1-4.
> fixed 820416 2:17.0~beta5+dfsg1-4
Bug #820416 {Done: Santiago Vila } [src:kodi] kodi: FTBFS in 
testing (Segmentation fault)
Marked as fixed in versions kodi/2:17.0~beta5+dfsg1-4.
> fixed 502180 3.14.1-2
Bug #502180 {Done: Pedro Beja } [evince-gtk] add ctrl-l to 
the menu proper
Marked as fixed in versions evince/3.14.1-2.
> fixed 794608 1.11
Bug #794608 {Done: "Dr. Tobias Quathamer" } [dput-ng] 
dput-ng: Please backport 1.9 to jessie
Marked as fixed in versions dput-ng/1.11.
> fixed 830316 1.11
Bug #830316 {Done: "Dr. Tobias Quathamer" } [dput-ng] 
dput-ng: uploading to jessie-backports fails with jessie's version
Marked as fixed in versions dput-ng/1.11.
> notfixed 545888 2.10.2-6
Bug #545888 {Done: Aurelien Jarno } [libc0.3-dev] 
libc0.3-dev: struct ether_addr defined twice
There is no source info for the package 'libc0.3-dev' at version '2.10.2-6' 
with architecture ''
Unable to make a source version for version '2.10.2-6'
No longer marked as fixed in versions 2.10.2-6.
> fixed 545888 eglibc/2.10.2-6
Bug #545888 {Done: Aurelien Jarno } [libc0.3-dev] 
libc0.3-dev: struct ether_addr defined twice
Marked as fixed in versions eglibc/2.10.2-6.
> notfixed 588102 3.4.1-1~experimental.1+rm
Bug #588102 {Done: Ben Hutchings } [src:linux] 
[linux-source-2.6.32] get_dvb_firmware script fails to download 
tda10045/tda10046 firmware
The source 'linux' and version '3.4.1-1~experimental.1+rm' do not appear to 
match any binary packages
No longer marked as fixed in versions 3.4.1-1~experimental.1+rm.
> notfixed 599615 3.4.1-1~experimental.1+rm
Bug #599615 {Done: Ben Hutchings } [src:linux] 
linux-image-2.6.32-5-xen-686: kernel BUG at 
/buildd/buildd-linux-2.6_2.6.32-24-i386-JPvGSk/linux-2.6-2.6.32/debi 
an/build/source_i386_xen/drivers/md/md.c: 6192!
Bug #626189 {Done: Ben Hutchings } [src:linux] 
linux-image-2.6.32-5-xen-686: kernel BUG (invalid opcode) on reboot -f
The source 'linux' and version '3.4.1-1~experimental.1+rm' do not appear to 
match any binary packages
No longer marked as fixed in versions 3.4.1-1~experimental.1+rm.
No longer marked as fixed in versions 3.4.1-1~experimental.1+rm.
> notfixed 599238 3.4.1-1~experimental.1+rm
Bug #599238 {Done: Ben Hutchings } [src:linux] Hash Sum 
mismatch when running Xen 4.0.1-1 and 2.6.32-5-xen-amd64
The source 'linux' and version '3.4.1-1~experimental.1+rm' do not appear to 
match any binary packages
No longer marked as fixed in versions 3.4.1-1~experimental.1+rm.
> notfixed 601625 3.4.1-1~experimental.1+rm
Bug #601625 {Done: Ben Hutchings } [src:linux] 
linux-patch-debian-2.6.32: unapplying 18 fails
The source 'linux' and version '3.4.1-1~experimental.1+rm' do not appear to 
match any binary packages
No longer marked as fixed in versions 3.4.1-1~experimental.1+rm.
> fixed 692350 0.6+git7fdc0cd97c093f-1
Bug #692350 {Done: Bastien Roucariès } 
[kbibtex] kbibtex: package version 0.4.1 in sid, patch provided
There is no source info for the package 'kbibtex' at version 
'0.6+git7fdc0cd97c093f-1' with architecture ''
Unable to make a source version for version '0.6+git7fdc0cd97c093f-1'
Marked as fixed in versions 0.6+git7fdc0cd97c093f-1.
> notfixed 693851 3.4.1-1~experimental.1+rm
Bug #693851 {Done: Ben Hutchings } [src:linux] Xen domU 
dynamic memory extension not working
The source 'linux' and version '3.4.1-1~experimental.1+rm' do not appear to 
match any binary packages
No longer marked as fixed in versions 3.4.1-1~experimental.1+rm.
> notfixed 694964 2.21
Bug #694964 {Done: Aurelien Jarno } [libc6] libc6:amd64: 
binary debian target fails - /usr/include/locale.h cannot be removed
There is no source info for the package 'libc6' at version '2.21' with 
architecture ''
Unable to make a source version for version '2.21'
No longer marked as fixed in versions 2.21.
> fixed 694964 2.21-1
Bug #694964 {Done: Aurelien Jarno } [libc6] libc6:amd64: 
binary debian target fails - /usr/include/locale.h cannot be removed
Marked as fixed in versions glibc/2.21-1.
> fixed 705655 3.3~rc6-1~experimental.1
Bug #705655 {Done: Ben Hutchings } [src:linux] iwlwifi 
requests unpackaged firmware blob iwlwifi-6000g2a-6.ucode
The source 'linux' and version '3.3~rc6-1~experimental.1' do not appear to 
match any binary packages
Marked as fixed in versions linux/3.3~rc6-1~experimental.1.
> fixed

Bug#875992: haskell-lens: unsatisfiable B-D: libghc-vector-dev (< 0.12) but 0.12.0.1-1 is to be installed

2017-09-16 Thread Andreas Beckmann

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

haskell-lens connot be built in sid any more, blocking the
ongoing ghc transition.


Andreas

Bug#875991: fast5: FTBFS: debian/python-fast5-bin/usr/bin/ is not a directory

2017-09-16 Thread Aaron M. Ucko

Source: fast5
Version: 0.6.2-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Greetings.

Builds of fast5 covering only its architecture-dependent binary
packages (as on the autobuilders, or with dpkg-buildpackage -B) have
been failing:

  dh_install
  mv debian/python-fast5/usr/bin/* debian/python-fast5-bin/usr/bin/
  mv: target 'debian/python-fast5-bin/usr/bin/' is not a directory
  debian/rules:36: recipe for target 'override_dh_install' failed
  make[1]: *** [override_dh_install] Error 1
  make[1]: Leaving directory '/<>'
  debian/rules:16: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Splitting override_dh_install into -arch and -indep variants can be
helpful in general, but could be problematic here when building all
the binary packages if the -arch target runs first.  Instead, I
suppose you'll want to conditionalize these mv commands on the
existence of debian/python-fast5-bin, and likewise conditionalize the
sed commands on the existence of debian/libfast5-dev.

Could you please take a look?

Thanks!

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

Bug#871116: marked as done (libgoogle-gson-java: FTBFS: ERROR Failed to execute goal [32morg.apache.maven.plugins:maven-jar-plugin:3.0.2:jar[m [1m(default)[m on project [36mgson[m: [1;31mYou ha

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 22:20:40 +0200
with message-id <01925417-dc1e-b213-4db3-84d953473...@apache.org>
and subject line 
has caused the Debian Bug report #871116,
regarding libgoogle-gson-java: FTBFS: ERROR Failed to execute goal 
[32morg.apache.maven.plugins:maven-jar-plugin:3.0.2:jar[m [1m(default)[m on 
project [36mgson[m: [1;31mYou have to use a classifier to attach 
supplemental artifacts to the project instead of replacing them.[m -> 
[1m[Help 1][m
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.)


-- 
871116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgoogle-gson-java
Version: 2.4-1
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[1]: Entering directory '/<>'
> make[1]: Nothing to be done for 'patch-poms'.
> make[1]: Leaving directory '/<>'
> cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>   -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Dmaven.repo.local=/<>/debian/maven-repo --file gson/pom.xml 
> package -DskipTests
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Gson 2.4[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.2:resources[m 
> [1m(default-resources)[m @ [36mgson[0;1m ---[m
> [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources.
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/gson/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mgson[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;34mINFO[m] Compiling 66 source files to 
> /<>/gson/target/classes
> Use of target 1.5 is no longer supported, switching to 1.7
> Use of source 1.5 is no longer supported, switching to 1.7
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.2:testResources[m 
> [1m(default-testResources)[m @ [36mgson[0;1m ---[m
> [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources.
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/gson/src/test/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:testCompile[m 
> [1m(default-testCompile)[m @ [36mgson[0;1m ---[m
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;34mINFO[m] Compiling 88 source files to 
> /<>/gson/target/test-classes
> Use of target 1.5 is no longer supported, switching to 1.7
> Use of source 1.5 is no longer supported, switching to 1.7
> [[1;34mINFO[m] 
> /<>/gson/src/test/java/com/google/gson/internal/LinkedHashTreeMapTest.java:
>  Some input files use unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/gson/src/test/java/com/google/gson/internal/LinkedHashTreeMapTest.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-surefire-plugin:2.19.1:test[m 
> [1m(default-test)[m @ [36mgson[0;1m ---[m
> [[1;34mINFO[m] Tests are skipped.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-jar-plugin:3.0.2:jar[m 
> [1m(default-jar)[m @ [36mgson[0;1m ---[m
> [[1;34mINFO[m] Building jar: /<>/gson/target/gson-2.4.jar
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-jar-plugin:3.0.2:jar[m 
> [1m(default)[m @ [36mgson[0;1m ---[m
> [[1;34mINFO[m] 
> [1m[m
>

Bug#874693: Is this still an issue?

2017-09-16 Thread Dean Loros

I see that gjs 1.50  has been released. Is this bug still applicable?

Bug#875690: Fixed in FreeXL 1.0.4

2017-09-16 Thread Sebastiaan Couwenberg

Hi Salvatore,

On 09/13/2017 07:27 PM, Bas Couwenberg wrote:
> Should be fixed in the new upstream release:
> 
> https://groups.google.com/forum/m/#!topic/spatialite-users/Wpj62XSzcZY
> 
> I'm not able to work on this until I return from VAC.

I've cherry-picked the changes from 1.0.4 and prepared updates for
stretch, jessie & wheezy. The changes are available in git, and the
debdiffs are attached.

 * https://anonscm.debian.org/cgit/pkg-grass/freexl.git/log/?h=stretch
 * https://anonscm.debian.org/cgit/pkg-grass/freexl.git/log/?h=jessie
 * https://anonscm.debian.org/cgit/pkg-grass/freexl.git/log/?h=wheezy

Are these OK to upload?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru freexl-1.0.0b/debian/changelog freexl-1.0.0b/debian/changelog
--- freexl-1.0.0b/debian/changelog  2015-11-13 11:39:37.0 +0100
+++ freexl-1.0.0b/debian/changelog  2017-09-16 23:26:04.0 +0200
@@ -1,3 +1,10 @@
+freexl (1.0.0b-1+deb7u4) wheezy-security; urgency=high
+
+  * Add upstream patch to fix CVE-2017-2923 & CVE-2017-2924.
+(closes: #875690, #875691)
+
+ -- Bas Couwenberg   Sat, 16 Sep 2017 23:26:04 +0200
+
 freexl (1.0.0b-1+deb7u3) wheezy-security; urgency=high
 
   * Add patch to fix regression introduced by afl-vulnerabilitities.patch.
diff -Nru freexl-1.0.0b/debian/patches/CVE-2017-2923_CVE-2017-2924.patch 
freexl-1.0.0b/debian/patches/CVE-2017-2923_CVE-2017-2924.patch
--- freexl-1.0.0b/debian/patches/CVE-2017-2923_CVE-2017-2924.patch  
1970-01-01 01:00:00.0 +0100
+++ freexl-1.0.0b/debian/patches/CVE-2017-2923_CVE-2017-2924.patch  
2017-09-16 23:26:04.0 +0200
@@ -0,0 +1,317 @@
+Description: fixing a security issue - Cisco TALOS-2017-430 and TALOS-2017-431
+ CVE-2017-2923 & CVE-2017-2924
+Author: Alessandro Furieri 
+Origin: https://www.gaia-gis.it/fossil/freexl/ci/40c17539ea56f0d8
+Bug-Debian: https://bugs.debian.org/875690
+https://bugs.debian.org/875691
+
+--- a/src/freexl.c
 b/src/freexl.c
+@@ -935,6 +935,21 @@ set_sst_value (biff_workbook * workbook,
+ return FREEXL_OK;
+ }
+ 
++static size_t
++xls_fread (size_t bufsz, void *buf, size_t size, size_t nmemb, FILE * fl)
++{
++/* 
++/ Sandro 2017-09-07
++/ secure version of "fread" checking against buffer overflows 
++/---
++/ expected to fix the issue reported by
++/ Cisco [TALOS-2017-431]
++*/
++if ((size * nmemb) > bufsz)
++  return 0;
++return fread (buf, size, nmemb, fl);
++}
++
+ static fat_chain *
+ alloc_fat_chain (int swap, unsigned short sector_shift,
+unsigned int directory_start)
+@@ -1377,7 +1392,8 @@ read_fat_sector (FILE * xls, fat_chain *
+   max_fat = 128;
+ 
+ /* reading a FAT sector */
+-if (fread (buf, 1, chain->sector_size, xls) != chain->sector_size)
++if (xls_fread (sizeof (buf), buf, 1, chain->sector_size, xls) !=
++  chain->sector_size)
+   return FREEXL_CFBF_READ_ERROR;
+ 
+ for (i_fat = 0; i_fat < max_fat; i_fat++)
+@@ -1419,7 +1435,8 @@ read_difat_sectors (FILE * xls, fat_chai
+ if (fseek (xls, where, SEEK_SET) != 0)
+ return FREEXL_CFBF_SEEK_ERROR;
+ /* reading a DIFAT sector */
+-if (fread (, 1, chain->sector_size, xls) != chain->sector_size)
++if (xls_fread (sizeof (difat), , 1, chain->sector_size, xls) !=
++chain->sector_size)
+ return FREEXL_CFBF_READ_ERROR;
+ blocks++;
+ if (chain->swap)
+@@ -1480,7 +1497,8 @@ read_miniFAT_sectors (FILE * xls, fat_ch
+ unsigned char *p_buf = buf;
+ block++;
+ /* reading a miniFAT sector */
+-if (fread (, 1, chain->sector_size, xls) != chain->sector_size)
++if (xls_fread (sizeof (buf), , 1, chain->sector_size, xls) !=
++chain->sector_size)
+ return FREEXL_CFBF_READ_ERROR;
+ for (i_fat = 0; i_fat < max_fat; i_fat++)
+   {
+@@ -1508,7 +1526,7 @@ read_cfbf_header (biff_workbook * workbo
+ int ret;
+ unsigned char *p_fat = header.fat_sector_map;
+ 
+-if (fread (, 1, 512, workbook->xls) != 512)
++if (xls_fread (sizeof (header), , 1, 512, workbook->xls) != 512)
+   {
+ *err_code = FREEXL_CFBF_READ_ERROR;
+ return NULL;
+@@ -1654,8 +1672,9 @@ read_mini_stream (biff_workbook * workbo
+   *errcode = FREEXL_CFBF_SEEK_ERROR;
+   return 0;
+   }
+-if (fread (buf, 1, workbook->fat->sector_size, workbook->xls) !=
+-workbook->fat->sector_size)
++if (xls_fread
++(sizeof (buf), buf, 1, workbook->fat->sector_size,
++ workbook->xls) != workbook->fat->sector_size)
+   {
+   *errcode = FREEXL_CFBF_READ_ERROR;
+   return 0;
+@@ -1987,7 +2006,7 @@ legacy_emergency_dimension (biff_workboo
+ /* looping on BIFF records */
+ if (!first)
+

Bug#849122: Please adjust the BTS version tracking info

2017-09-16 Thread Francesco Poli

On Sat, 9 Sep 2017 19:17:12 +0200 Francesco Poli wrote:

> On Sat, 1 Jul 2017 23:32:28 +0200 Francesco Poli wrote:
> 
> > Dear Debian wpasupplicant Maintainers,
> > I noticed that these 3 RC bugs (#849122, #849077, #849875) are marked
> > as found in wpa/2.6-2, which is now superseded by versions with epoch 2.
> > What seems to have happened (please correct me, if I am wrong) is that
> > the upstream version 2.4 was reintroduced into unstable (with epoch 2)
> > and then migrated to stretch (before the stretch release as stable).
> > 
> > Hence, I would say that those three bugs only affect experimental and
> > are not in stretch, buster or sid.
> > 
> > Could you please confirm that these 3 bugs should be marked as fixed in
> > wpa/2:2.4-1 and found in wpa/2:2.6-4 ?
> > 
> > Thanks for your time!
> > Bye.
> 
> Hello again,
> could you please reply to my question?
> 
> Again, thanks for your time.

Ping?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp9xTQ04xSqX.pgp
Description: PGP signature

Bug#853560: marked as done (mp4v2: ftbfs with GCC-7)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 21:50:34 +
with message-id 
and subject line Bug#853560: fixed in mp4v2 2.0.0~dfsg0-6
has caused the Debian Bug report #853560,
regarding mp4v2: 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.)


-- 
853560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mp4v2
Version: 2.0.0~dfsg0-5
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/mp4v2_2.0.0~dfsg0-5_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

[...]
 from src/itmf/impl.h:29,
 from src/itmf/CoverArtBox.cpp:24:
./src/mp4util.h:36:33: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 throw new Exception("assert failure: "LIBMPV42_STRINGIFY((expr)), 
__FILE__, __LINE__, __FUNCTION__ ); \
 ^
In file included from ./src/src.h:28:0,
 from ./src/impl.h:6,
 from src/itmf/impl.h:29,
 from src/itmf/Tags.cpp:27:
./src/mp4util.h:36:33: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 throw new Exception("assert failure: "LIBMPV42_STRINGIFY((expr)), 
__FILE__, __LINE__, __FUNCTION__ ); \
 ^
g++ -DHAVE_CONFIG_H   -I./include -I./include -I. -I. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wformat -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c -o util/mp4track.o util/mp4track.cpp
g++ -DHAVE_CONFIG_H   -I./include -I./include -I. -I. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wformat -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c -o util/mp4trackdump.o util/mp4trackdump.cpp
In file included from ./src/src.h:28:0,
 from ./src/impl.h:6,
 from src/itmf/impl.h:29,
 from src/itmf/generic.cpp:24:
./src/mp4util.h:36:33: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 throw new Exception("assert failure: "LIBMPV42_STRINGIFY((expr)), 
__FILE__, __LINE__, __FUNCTION__ ); \
 ^
In file included from ./src/src.h:28:0,
 from ./src/impl.h:6,
 from src/qtff/impl.h:29,
 from src/qtff/coding.cpp:24:
./src/mp4util.h:36:33: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 throw new Exception("assert failure: "LIBMPV42_STRINGIFY((expr)), 
__FILE__, __LINE__, __FUNCTION__ ); \
 ^
In file included from ./src/src.h:28:0,
 from ./src/impl.h:6,
 from src/qtff/impl.h:29,
 from src/qtff/ColorParameterBox.cpp:24:
./src/mp4util.h:36:33: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 throw new Exception("assert failure: "LIBMPV42_STRINGIFY((expr)), 
__FILE__, __LINE__, __FUNCTION__ ); \
 ^
In file included from ./src/src.h:28:0,
 from ./src/impl.h:6,
 from src/qtff/impl.h:29,
 from

Bug#853560: marked as pending

2017-09-16 Thread Matteo F . Vescovi

tag 853560 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/mp4v2.git/commit/?id=c9c4347

---
commit c9c434702803381bc9f16f9165911dd0826af567
Author: Matteo F. Vescovi 
Date:   Sat Sep 16 23:22:02 2017 +0200

debian/changelog: new revision entry added

Gbp-Dch: Ignore

diff --git a/debian/changelog b/debian/changelog
index 500f687..602aa70 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+mp4v2 (2.0.0~dfsg0-6) UNRELEASED; urgency=medium
+
+  * debian/: dh bump 9 -> 10
+  * debian/control: S-V bump 3.9.8 -> 4.0.0 (no changes needed)
+  * debian/patches/: patchset updated
+- 0004-Pointer_comparison.patch added (Closes: #853560)
+
+ -- Matteo F. Vescovi   Sat, 16 Sep 2017 23:20:23 +0200
+
 mp4v2 (2.0.0~dfsg0-5) unstable; urgency=medium
 
   * debian/patches/: patchset updated

Processed: Bug#853560 marked as pending

2017-09-16 Thread Debian Bug Tracking System

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

> tag 853560 pending
Bug #853560 [src:mp4v2] mp4v2: ftbfs with GCC-7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#874521: fwupd segfaults at start

2017-09-16 Thread Jeremy Bicha

Currently, this bug is keeping fwupd 0.9.7 from migrating to testing.

Is this crash new with fwupd 0.9 or can you also reproduce it with
testing's 0.8.2-2?

Also, if you aren't subscribed to the bug, see Mario's response at
https://bugs.debian.org/874521

Thanks,
Jeremy Bicha

Bug#875982: RM: obsolete with current Perl?

2017-09-16 Thread Florian Schlichting

Package: libsub-current-perl
Version: 0.03-2
Severity: serious
Justification: obsolete with perl >= 5.16.0

libsub-current-perl 0.03 added a note to its POD explaining that from
perl 5.16.0, the built-in __SUB__ can be used instead via the pragma

use feature 'current_sub';

libsub-current-perl has no reverse dependencies and an extremely low
popcon (7 installs, 0 votes currently). It would appear that it is
obsolete and can be removed from Debian.

Bug#868073: bioperl-run: FTBFS: t/Bowtie.t failure

2017-09-16 Thread Andreas Tille

control: forwarded -1 https://github.com/bioperl/bioperl-run/issues/52
control: tags -1 upstream

I have forwarded the issue upstream.

I think the issue occures since there is no such executable bowtie-align
any more. The executables that are shipped with bowtie are named
bowtie-align-l or bowtie-align-s. I personally have no idea which one is
the right one to run the test.

Any hint from the Debian Med team which one would be right would surely
help.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#868073: bioperl-run: FTBFS: t/Bowtie.t failure

2017-09-16 Thread Debian Bug Tracking System

Processing control commands:

> forwarded -1 https://github.com/bioperl/bioperl-run/issues/52
Bug #868073 [bioperl-run] bioperl-run: FTBFS: t/Bowtie.t failure
Set Bug forwarded-to-address to 
'https://github.com/bioperl/bioperl-run/issues/52'.
> tags -1 upstream
Bug #868073 [bioperl-run] bioperl-run: FTBFS: t/Bowtie.t failure
Added tag(s) upstream.

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

Bug#810694: marked as done (west-chamber-dkms: does not clean after module build)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 19:35:00 +
with message-id 
and subject line Bug#810694: fixed in west-chamber 20100405+svn2007.r124-8
has caused the Debian Bug report #810694,
regarding west-chamber-dkms: does not clean after module build
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.)


-- 
810694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: west-chamber-dkms
Version: 20100405+svn2007.r124-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

This looks like only a partial cleaning is performed after a
module build, which could cause problems when building for a
different kernel later on.

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

2m41.3s ERROR: FAIL: Package purging left files on system:
  /usr/src/west-chamber-20100405+svn2007.r124/   owned by: 
west-chamber-dkms
  /usr/src/west-chamber-20100405+svn2007.r124/extensions/owned by: 
west-chamber-dkms
  
/usr/src/west-chamber-20100405+svn2007.r124/extensions/.compat_xtables.o.cmd
   not owned
  /usr/src/west-chamber-20100405+svn2007.r124/extensions/.tmp_versions/ 
 not owned
  
/usr/src/west-chamber-20100405+svn2007.r124/extensions/.tmp_versions/compat_xtables.mod
not owned
  /usr/src/west-chamber-20100405+svn2007.r124/extensions/compat_xtables.o   
 not owned


cheers,

Andreas


west-chamber-dkms_20100405+svn2007.r124-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: west-chamber
Source-Version: 20100405+svn2007.r124-8

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated west-chamber 
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, 17 Sep 2017 01:44:53 +0800
Source: west-chamber
Binary: west-chamber-common west-chamber-source west-chamber-dkms
Architecture: source amd64 all
Version: 20100405+svn2007.r124-8
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 west-chamber-common - iptable extension for bypassing content filtering 
firewall
 west-chamber-dkms - iptable extension for bypassing content filtering firewall 
(dkms)
 west-chamber-source - iptable extension for bypassing content filtering 
firewall (modul
Closes: 810694
Changes:
 west-chamber (20100405+svn2007.r124-8) unstable; urgency=low
 .
   * west-chamber-dkms.conf: fix the clean rule after module build
 (Closes: #810694)
   * Add 03_port_to_linux_4.10.patch: build against linux version >= 4.10
   * Bump Standards-Version to 4.0.0: Nothing needs to be changed.
Checksums-Sha1:
 c8a80002bcf5348ff84c1eafe45af3193ccf8a8a 2160 
west-chamber_20100405+svn2007.r124-8.dsc
 563b46465783ded8e17cba1ec81de6a46c651771 9444 
west-chamber_20100405+svn2007.r124-8.debian.tar.xz
 c019031d5cab25f68f92da06d2db8ec302e84cdf 14760 
west-chamber-common-dbgsym_20100405+svn2007.r124-8_amd64.deb
 a5623b7fcbf30f9644a66f61314934ffe6899258 31394 
west-chamber-common_20100405+svn2007.r124-8_amd64.deb
 33358d1718eadcaf7b7bf500c5fcd526b0d8a10f 23180 
west-chamber-dkms_20100405+svn2007.r124-8_all.deb
 52eba3ba78dd97ae8f6a0c3170c5b4b6333abae6 20380 
west-chamber-source_20100405+svn2007.r124-8_all.deb
 6d595657bdda64f2aab7459ee78cfa94d4187b39 7171 
west-chamber_20100405+svn2007.r124-8_amd64.buildinfo
Checksums-Sha256:
 09f2e87e55c0b557cdf9cf765bea8a826c638ff2cfff7ef142de0fe9452bdca5 2160 
west-chamber_20100405+svn2007.r124-8.dsc
 60f028154709e43e59c83b9b06224614115f996fd28e0f0bdc53fa347a83ccd7 9444

Bug#875980: kodi-pvr-vuplus: PVR addon not compatible with Kodi from same Debian release

2017-09-16 Thread Marko von Oppen

Package: kodi-pvr-vuplus
Version: 2.4.4+git20160820-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The Vuplus PVR addon can be installed, configured and generally works until 
next Kodi start.

After next Kodi start a message box comes up stating that the Vu+/Enigma Client 
Addon is not compatible with this Kodi version and the Addon is automatically 
deactivated.

That behaviour finally renders the Addon and so complete Debian package 
unusable.

The current upstream version of the addon is 3.5.1.

BR
Marko

Log entry is
19:03:19.917 T:139766167123712  NOTICE: ADDON: pvr.vuplus version 2.4.4 is 
incompatible


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

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

Versions of packages kodi-pvr-vuplus depends on:
pn  kodi-api-pvr   
ii  libc6  2.24-11+deb9u1
ii  libgcc11:6.3.0-18
ii  libkodiplatform16  17.1.0-1
ii  libp8-platform22.1.0.1+dfsg1-1
ii  libstdc++6 6.3.0-18
ii  libtinyxml2.6.2v5  2.6.2-4

kodi-pvr-vuplus recommends no packages.

kodi-pvr-vuplus suggests no packages.

-- no debconf information

Processed: Re: Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

2017-09-16 Thread Debian Bug Tracking System

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

> reassign 875975 gtk-doc 1.26-1
Bug #875975 [src:kmod] kmod FTBFS: subprocess.CalledProcessError: Command 
'['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero 
exit status 1
Bug reassigned from package 'src:kmod' to 'gtk-doc'.
No longer marked as found in versions kmod/24-1.
Ignoring request to alter fixed versions of bug #875975 to the same values 
previously set
Bug #875975 [gtk-doc] kmod FTBFS: subprocess.CalledProcessError: Command 
'['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero 
exit status 1
There is no source info for the package 'gtk-doc' at version '1.26-1' with 
architecture ''
Unable to make a source version for version '1.26-1'
Marked as found in versions 1.26-1.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

2017-09-16 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 gtk-doc/1.26-1
Unknown command or malformed arguments to command.

> affects -1 kmod
Bug #875975 [src:kmod] kmod FTBFS: subprocess.CalledProcessError: Command 
'['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero 
exit status 1
Added indication that 875975 affects kmod
> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=787768
Bug #875975 [src:kmod] kmod FTBFS: subprocess.CalledProcessError: Command 
'['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero 
exit status 1
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=787768'.

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

Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

2017-09-16 Thread Emilio Pozuelo Monfort

Control: reassign -1 gtk-doc/1.26-1
Control: affects -1 kmod
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=787768

Hi,

On 16/09/17 20:42, Helmut Grohne wrote:
> Source: kmod
> Version: 24-1
> Severity: serious
> 
> kmod fails to build from source in unstable. The tail of the build log
> is:
> 
> | cd html && gtkdoc-mkhtml $mkhtml_options 
> --path=/<>/build-deb/../libkmod/docs/doc 
> --path=/<>/build-deb/libkmod/docs/doc libkmod ../libkmod-docs.xml
> | Computing chunks...
> | Writing libkmod-libkmod.html for refentry(libkmod-libkmod)
> | Writing libkmod-libkmod-list.html for refentry(libkmod-libkmod-list)
> | Writing libkmod-libkmod-config.html for refentry(libkmod-libkmod-config)
> | Writing libkmod-libkmod-module.html for refentry(libkmod-libkmod-module)
> | Writing libkmod-libkmod-loaded.html for refentry(libkmod-libkmod-loaded)
> | Writing ch01.html for chapter
> | Writing api-index-full.html for index(api-index-full)
> | Writing index.html for book(index)
> | Writing libkmod.devhelp2 for book(index)
> | gtkdoc-fixxref --module=libkmod --module-dir=html 
> --html-dir=/usr/share/gtk-doc/html 
> | Package glib-2.0 was not found in the pkg-config search path.
> | Perhaps you should add the directory containing `glib-2.0.pc'
> | to the PKG_CONFIG_PATH environment variable
> | No package 'glib-2.0' found
> | Traceback (most recent call last):
> |   File "/usr/bin/gtkdoc-fixxref", line 57, in 
> | fixxref.Run(options)
> |   File "/usr/share/gtk-doc/python/gtkdoc/fixxref.py", line 74, in Run
> | dir = common.GetModuleDocDir('glib-2.0')
> |   File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 104, in 
> GetModuleDocDir
> | path = subprocess.check_output([config.pkg_config, '--variable=prefix', 
> module_name], universal_newlines=True)
> |   File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
> | raise CalledProcessError(retcode, cmd, output=output)
> | subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', 
> '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1
> | Makefile:667: recipe for target 'html-build.stamp' failed
> | make[3]: *** [html-build.stamp] Error 1
> | Makefile:2117: recipe for target 'all-recursive' failed
> | make[2]: *** [all-recursive] Error 1
> | Makefile:1170: recipe for target 'all' failed
> | make[1]: *** [all] Error 2
> | make[1]: Leaving directory '/<>/build-deb'
> | debian/rules:78: recipe for target '.stamp-build' failed
> | make: *** [.stamp-build] Error 2
> | dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> 
> The timing of the failure strongly suggests a relation to the
> gtk-doc/1.26-1 upload. Please reassign if appropriate.

Yes, this is a regression in gtk-doc 1.26. The old version handled missing
glib-2.0.pc, but the new version is using python which is stricter. I have
forwarded this upstream.

Cheers,
Emilio

Processed: tagging 874365, tagging 875929

2017-09-16 Thread Debian Bug Tracking System

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

> tags 874365 - stretch
Bug #874365 {Done: HIGUCHI Daisuke (VDR dai) } [ruby-gdk3] 
ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found 
(GLib::Error)
Removed tag(s) stretch.
> tags 875929 + sid buster
Bug #875929 [src:acetoneiso] acetoneiso: should it be removed from Debian
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

2017-09-16 Thread Helmut Grohne

Source: kmod
Version: 24-1
Severity: serious

kmod fails to build from source in unstable. The tail of the build log
is:

| cd html && gtkdoc-mkhtml $mkhtml_options 
--path=/<>/build-deb/../libkmod/docs/doc 
--path=/<>/build-deb/libkmod/docs/doc libkmod ../libkmod-docs.xml
| Computing chunks...
| Writing libkmod-libkmod.html for refentry(libkmod-libkmod)
| Writing libkmod-libkmod-list.html for refentry(libkmod-libkmod-list)
| Writing libkmod-libkmod-config.html for refentry(libkmod-libkmod-config)
| Writing libkmod-libkmod-module.html for refentry(libkmod-libkmod-module)
| Writing libkmod-libkmod-loaded.html for refentry(libkmod-libkmod-loaded)
| Writing ch01.html for chapter
| Writing api-index-full.html for index(api-index-full)
| Writing index.html for book(index)
| Writing libkmod.devhelp2 for book(index)
| gtkdoc-fixxref --module=libkmod --module-dir=html 
--html-dir=/usr/share/gtk-doc/html 
| Package glib-2.0 was not found in the pkg-config search path.
| Perhaps you should add the directory containing `glib-2.0.pc'
| to the PKG_CONFIG_PATH environment variable
| No package 'glib-2.0' found
| Traceback (most recent call last):
|   File "/usr/bin/gtkdoc-fixxref", line 57, in 
| fixxref.Run(options)
|   File "/usr/share/gtk-doc/python/gtkdoc/fixxref.py", line 74, in Run
| dir = common.GetModuleDocDir('glib-2.0')
|   File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 104, in 
GetModuleDocDir
| path = subprocess.check_output([config.pkg_config, '--variable=prefix', 
module_name], universal_newlines=True)
|   File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
| raise CalledProcessError(retcode, cmd, output=output)
| subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', 
'--variable=prefix', 'glib-2.0']' returned non-zero exit status 1
| Makefile:667: recipe for target 'html-build.stamp' failed
| make[3]: *** [html-build.stamp] Error 1
| Makefile:2117: recipe for target 'all-recursive' failed
| make[2]: *** [all-recursive] Error 1
| Makefile:1170: recipe for target 'all' failed
| make[1]: *** [all] Error 2
| make[1]: Leaving directory '/<>/build-deb'
| debian/rules:78: recipe for target '.stamp-build' failed
| make: *** [.stamp-build] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

The timing of the failure strongly suggests a relation to the
gtk-doc/1.26-1 upload. Please reassign if appropriate.

Helmut

Bug#875957: marked as done (camlidl: uninstallable in sid)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 19:38:31 +0200
with message-id <20170916173830.43y5tagqqefzn...@seneca.home.org>
and subject line Re: Bug#875957: camlidl: uninstallable in sid
has caused the Debian Bug report #875957,
regarding camlidl: uninstallable in sid
to be marked as done.

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

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

-- 
875957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: camlidl
Version: 1.05-15
Severity: serious
Affects: src:plplot

Dear maintainer,

camlidl is currently not installable in sid, due to an unresolved
dependency:

# apt install camlidl
[...]
The following packages have unmet dependencies:
 camlidl : Depends: ocaml-nox-4.02.3 but it is not installable
E: Unable to correct problems, you have held broken packages.

This looks like it is broken by updating ocaml.

This causes FTBFS for the new plplot version.

Best regards

Ole
--- End Message ---
--- Begin Message ---
Hi Ole,

On Sat, Sep 16, 2017 at 04:12:07PM +0200, Ole Streicher wrote:
> Package: camlidl
> Version: 1.05-15
> Severity: serious
> Affects: src:plplot
> 
> Dear maintainer,
> 
> camlidl is currently not installable in sid, due to an unresolved
> dependency:
> 
> # apt install camlidl
> [...]
> The following packages have unmet dependencies:
>  camlidl : Depends: ocaml-nox-4.02.3 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> 
> This looks like it is broken by updating ocaml.

We are currently in an ocaml transition which started just last night.
Things should be back to normal in a few days.

-Ralf.--- End Message ---

Bug#819715: marked as done (node-starttls: FTBFS: Uncaught Error: unable to get local issuer certificate)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 17:35:02 +
with message-id 
and subject line Bug#819715: fixed in node-starttls 1.0.1-2
has caused the Debian Bug report #819715,
regarding node-starttls: FTBFS: Uncaught Error: unable to get local issuer 
certificate
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.)


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

Dear Maintainer,

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

  [..]

make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160401094149.CegZ3XcX5q/node-starttls-1.0.1'
  mocha \
--reporter dot \
--check-leaks \
--ui tdd
  (node) child_process: options.customFds option is deprecated. Use 
options.stdio instead.
  
[31mâ€¤[0m[33mâ€¤[0m[31mâ€¤[0m[31mâ€¤[0m[93mâ€¤[0m[33mâ€¤[0m
  
  [92m [0m[32m 3 passing[0m[90m (669ms)[0m
  [31m  3 failing[0m
  
  [0m  1) starttls tests simple connect with prepared socket:
  [0m[31m Uncaught Error: unable to get local issuer certificate[0m[90m
at Error (native)
at SecurePair. 
(/home/lamby/temp/cdt.20160401094149.CegZ3XcX5q/node-starttls-1.0.1/lib/starttls.js:82:24)
at SecurePair.g (events.js:260:16)
at emitNone (events.js:67:13)
at SecurePair.emit (events.js:166:7)
at 
SecurePair.options.ssl.onclienthello.ssl.onnewsession.ssl.onocspresponse.SecurePair.maybeInitFinished
 (_tls_legacy.js:790:10)
at CleartextStream.read [as _read] (_tls_legacy.js:277:13)
at CleartextStream.Readable.read (_stream_readable.js:336:10)
at EncryptedStream.write [as _write] (_tls_legacy.js:174:25)
at doWrite (_stream_writable.js:301:12)
at writeOrBuffer (_stream_writable.js:287:5)
at EncryptedStream.Writable.write (_stream_writable.js:215:11)
at Socket.ondata (_stream_readable.js:536:20)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:529:20)
  [0m
  [0m  2) starttls tests simple connect with options and prepared socket:
  [0m[31m Uncaught Error: unable to get local issuer certificate[0m[90m
at Error (native)
at SecurePair. 
(/home/lamby/temp/cdt.20160401094149.CegZ3XcX5q/node-starttls-1.0.1/lib/starttls.js:82:24)
at SecurePair.g (events.js:260:16)
at emitNone (events.js:67:13)
at SecurePair.emit (events.js:166:7)
at 
SecurePair.options.ssl.onclienthello.ssl.onnewsession.ssl.onocspresponse.SecurePair.maybeInitFinished
 (_tls_legacy.js:790:10)
at CleartextStream.read [as _read] (_tls_legacy.js:277:13)
at CleartextStream.Readable.read (_stream_readable.js:336:10)
at EncryptedStream.write [as _write] (_tls_legacy.js:174:25)
at doWrite (_stream_writable.js:301:12)
at writeOrBuffer (_stream_writable.js:287:5)
at EncryptedStream.Writable.write (_stream_writable.js:215:11)
at Socket.ondata (_stream_readable.js:536:20)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:529:20)
  [0m
  [0m  3) starttls tests simple connect with options:
  [0m[31m Uncaught AssertionError: false == true[0m[90m
at SecurePair. 
(/home/lamby/temp/cdt.20160401094149.CegZ3XcX5q/node-starttls-1.0.1/test/starttls.js:88:4)
at SecurePair. 
(/home/lamby/temp/cdt.20160401094149.CegZ3XcX5q/node-starttls-1.0.1/lib/starttls.js:107:12)
at SecurePair.g (events.js:260:16)
at emitNone (events.js:67:13)
at SecurePair.emit (events.js:166:7)
at 
SecurePair.options.ssl.onclienthello.ssl.onnewsession.ssl.onocspresponse.SecurePair.maybeInitFinished
 (_tls_legacy.js:790:10)
at CleartextStream.read [as _read] (_tls_legacy.js:277:13)
at CleartextStream.Readable.read (_stream_readable.js:336:10)
at EncryptedStream.write [as _write] (_tls_legacy.js:174:25)
at doWrite (_stream_writable.js:301:12)
at writeOrBuffer

Bug#875396: haskell-vector: FTBFS on any-i386

2017-09-16 Thread Samuel Thibault

Hello,

Samuel Thibault, on lun. 11 sept. 2017 10:02:12 +0200, wrote:
> In case you have not noticed, the haskell-vector fails the tests on i386
> ports (at least i386 and hurd-i386 failed, kfreebsd-i386 hasn't tried
> yet).

This is confirmed on kfreebsd-i386.

Samuel

Bug#875683: nvidia-graphics-drivers: libGL.so.1 missing with libglvnd libs

2017-09-16 Thread Luca Boccassi

On Fri, 2017-09-15 at 02:45 +0200, Andreas Beckmann wrote:
> On 15.09.2017 01:30, Luca Boccassi wrote:
> > > Is it because libgl1-glvnd-nvidia-glx declares a conflict with
> > > libgl1,
> > > which libgl1-mesa-glx provides perhaps?
> 
> That's the most likely case.
> 
> I tried a hack (r7481) s.t. this should now work with mesa 13 in
> testing. Some provides are disabled, so lib*-glvnd-nvidia* won't work
> as
> a substitute for the corresponding package from src:libglvnd.

Thanks, this works on Stretch now.

Kind regards,
Luca Boccassi

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

Bug#853559: mozjs24: ftbfs with GCC-7

2017-09-16 Thread Páder Rezső

https://github.com/uhulinux/ub-dev/commit/22ddd3bb42c4b8fb43f7c7263acf86900ea97b2c

-- 
R.

Bug#875945: fixed in at-spi2-core 2.26.0-2

2017-09-16 Thread Samuel Thibault

Hello,

Jeremy Bicha, on sam. 16 sept. 2017 11:31:48 -0400, wrote:
> I added the dependency because it was required for at-spi2-core to
> build when I packaged 2.25.90 or .91 but the dependency was correctly
> made optional again before 2.26.0 with this commit:
> 
> https://git.gnome.org/browse/at-spi2-core/commit/?id=aa3a11a1dece493

Yes, but this is bogus :)

We don't want to disable xkb support, we just want to avoid the spurious
dependency on xkbcommon, because xkb support is not there, but in
libX11.

Samuel

Bug#875970: ruby-fog-aws: FTBFS in experimental - test failures

2017-09-16 Thread Andreas Beckmann

Source: ruby-fog-aws
Version: 1.4.1-1
Severity: serious
Justification: fails to build from source

Hi,

the last upload of ruby-fog-aws to experimental did FTBFS: 

https://buildd.debian.org/status/fetch.php?pkg=ruby-fog-aws=all=1.4.1-1=1505064095=0


++  
  Compute::AWS | parsers | describe_images (compute, aws, parser) +  
  AWS::EFS | file systems (aws, efs)   
  tests/requests/efs/file_system_tests.rb
success
AWS::EFS | file systems (aws, efs)
  - has proper format
  
  tests/requests/efs/file_system_tests.rb
  undefined method `group_id' for nil:NilClass (NoMethodError)
tests/requests/efs/file_system_tests.rb:84:in `block (3 levels) in '
tests/helpers/formats_helper.rb:92:in `block in formats'
/usr/lib/ruby/vendor_ruby/shindo.rb:140:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:140:in `assert'
/usr/lib/ruby/vendor_ruby/shindo.rb:116:in `test'
tests/helpers/formats_helper.rb:85:in `formats'
tests/requests/efs/file_system_tests.rb:82:in `block (2 levels) in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
tests/requests/efs/file_system_tests.rb:6:in `block in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
/usr/lib/ruby/vendor_ruby/shindo.rb:38:in `initialize'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `new'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `tests'
tests/requests/efs/file_system_tests.rb:1:in `'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `load'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `block (2 levels) in 
run_in_thread'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `each'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `block in run_in_thread'
++  
  tests/requests/efs/file_system_tests.rb
  undefined method `group_id' for nil:NilClass (NoMethodError)
tests/requests/efs/file_system_tests.rb:98:in `block (3 levels) in '
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:7:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
tests/requests/efs/file_system_tests.rb:98:in `block (2 levels) in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
tests/requests/efs/file_system_tests.rb:6:in `block in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
/usr/lib/ruby/vendor_ruby/shindo.rb:38:in `initialize'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `new'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `tests'
tests/requests/efs/file_system_tests.rb:1:in `'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `load'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `block (2 levels) in 
run_in_thread'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `each'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `block in run_in_thread'
An error occurred outside of a test
rake aborted!
Command failed with status (1): [export FOG_MOCK=true && shindont...]
/<>/Rakefile:7:in `block in '
Tasks: TOP => test
(See full trace by running task with --trace)
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Andreas

Bug#852591: marked as done (flashcache: Update udevadm path)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 16:31:28 +
with message-id 
and subject line Bug#875682: Removed package(s) from unstable
has caused the Debian Bug report #852591,
regarding flashcache: Update udevadm path
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.)


-- 
852591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flashcache
Version: 3.1.3+git20150701-5
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package flashcache does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Version: 3.1.3+git20150701-5+rm

Dear submitter,

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

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

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

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

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

Bug#875969: libopenshot: FTBFS: Timeline_Tests.cpp:158:1: error: Failure in Timeline_Check_Two_Track_Video

2017-09-16 Thread Andreas Beckmann

Package: libopenshot
Version: 0.1.7+ds1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libopenshot FTBFS on amd64 with test failures:

https://buildd.debian.org/status/fetch.php?pkg=libopenshot=amd64=0.1.7%2Bds1-1%2Bb1=1502819536=0


 RUNNING ALL TESTS

[AudioData @ 0x7ffc51a8b0a0] invalid NULL pointer for src[0]
[AudioData @ 0x7fe633ffe630] invalid NULL pointer for src[0]
[AudioData @ 0x7fe633ffe630] invalid NULL pointer for src[0]
[AudioData @ 0x7ffc51a8ba40] invalid NULL pointer for src[0]
[AudioData @ 0x7fe633ffe450] invalid NULL pointer for src[0]
[AudioData @ 0x7ffc51a8ba40] invalid NULL pointer for src[0]
[AudioData @ 0x7ffc51a8ba40] invalid NULL pointer for src[0]
[libvpx @ 0x5634b47db880] v1.6.1
[webm @ 0x5634b45be660] Using AVStream.codec.time_base as a timebase hint to 
the muxer is deprecated. Set AVStream.time_base instead.
[webm @ 0x5634b45be660] Using AVStream.codec to pass codec parameters to muxers 
is deprecated, use AVStream.codecpar instead.
[webm @ 0x5634b45be660] Using AVStream.codec.time_base as a timebase hint to 
the muxer is deprecated. Set AVStream.time_base instead.
[webm @ 0x5634b45be660] Using AVStream.codec to pass codec parameters to muxers 
is deprecated, use AVStream.codecpar instead.
[AudioData @ 0x7fe633ffe630] invalid NULL pointer for src[0]
[AudioData @ 0x7fe6337fd630] invalid NULL pointer for src[0]
[AudioData @ 0x7fe6037fd450] invalid NULL pointer for src[0]
[AudioData @ 0x7fe602ffc450] invalid NULL pointer for src[0]
/<>/libopenshot-0.1.7+ds1/tests/Timeline_Tests.cpp:158:1: error: 
Failure in Timeline_Check_Two_Track_Video: Expected 23 but was 0
/<>/libopenshot-0.1.7+ds1/tests/Timeline_Tests.cpp:159:1: error: 
Failure in Timeline_Check_Two_Track_Video: Expected 190 but was 0
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
FAILURE: 1 out of 79 tests failed (2 failures).
Test time: 8.28 seconds.



Andreas

Bug#875967: publicsuffix: FTBFS - UnicodeDecodeError during tests

2017-09-16 Thread Andreas Beckmann

Source: publicsuffix
Version: 20170828.2009-1
Severity: serious
Justification: fails to build from source

Hi,

the last upload of publicsuffix did FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=publicsuffix=all=20170828.2009-1=1504820937=0


dpkg-buildpackage: info: source package publicsuffix
dpkg-buildpackage: info: source version 20170828.2009-1
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build publicsuffix-20170828.2009
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
make -j4
make[2]: Entering directory '/<>'
cd linter;\
  ./pslint_selftest.sh; \
  ./pslint.py ../public_suffix_list.dat;
test_allowedchars: OK
test_dots: OK
test_duplicate: OK
test_exception: OK
test_punycode: OK
test_section1: OK
test_section2: OK
test_section3: OK
test_section4: OK
test_spaces: OK
test_wildcard: OK
make[2]: Leaving directory '/<>'
TZ=UTC touch -t 201708282009 public_suffix_list.dat
psl-make-dafsa --input-format=psl --output-format=binary public_suffix_list.dat 
public_suffix_list.dafsa
Traceback (most recent call last):
  File "/usr/bin/psl-make-dafsa", line 695, in 
sys.exit(main())
  File "/usr/bin/psl-make-dafsa", line 689, in main
outfile.write(converter(parser(infile, utf_mode, codecs), utf_mode, codecs))
  File "/usr/bin/psl-make-dafsa", line 559, in parse_psl
for line in infile:
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 8046: 
ordinal not in range(128)
debian/rules:14: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

Build finished at 2017-09-07T21:48:55Z


Andreas

Bug#875965: ruby-net-ssh: FTBFS - test failures

2017-09-16 Thread Andreas Beckmann

Source: ruby-net-ssh
Version: 1:4.2.0-1
Severity: serious
Justification: fails to build from source

Hi,

the last upload of ruby-net-ssh does FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=ruby-net-ssh=all=1%3A4.2.0-1=1505233484=0

┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/<>/debian/ruby-net-ssh/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-net-ssh/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -w  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_all.rb" "test/test_buffer.rb" "test/test_buffered_io.rb" 
"test/test_config.rb" "test/test_key_factory.rb" "test/test_known_hosts.rb" 
"test/test_proxy_jump.rb" -v
/<>/test/transport/test_session.rb:305:in `': 
uninitialized constant Transport::TestSession::Logger (NameError)
from /<>/test/transport/test_session.rb:15:in 
`'
from /<>/test/transport/test_session.rb:13:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /<>/test/test_all.rb:11:in `block (2 levels) in '
from /<>/test/test_all.rb:11:in `each'
from /<>/test/test_all.rb:11:in `block in '
from /<>/test/test_all.rb:3:in `chdir'
from /<>/test/test_all.rb:3:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
rake aborted!
Command failed with status (1): [ruby -w  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_all.rb" 
"test/test_buffer.rb" "test/test_buffered_io.rb" "test/test_config.rb" 
"test/test_key_factory.rb" "test/test_known_hosts.rb" "test/test_proxy_jump.rb" 
-v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-net-ssh 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1


Andreas

Bug#875945: fixed in at-spi2-core 2.26.0-2

2017-09-16 Thread Jeremy Bicha

I'm attaching a different way of fixing this issue.

I added the dependency because it was required for at-spi2-core to
build when I packaged 2.25.90 or .91 but the dependency was correctly
made optional again before 2.26.0 with this commit:

https://git.gnome.org/browse/at-spi2-core/commit/?id=aa3a11a1dece493

Thanks,
Jeremy Bicha
From 5ad4d7ed515f8bea31631ccca300a75dfcd793af Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Sat, 16 Sep 2017 11:22:30 -0400
Subject: [PATCH] Alternate fix for libxkbcommon linking issue

---
 debian/control   |  2 --
 debian/patches/avoid_xkb_dep | 19 ---
 debian/patches/series|  1 -
 3 files changed, 22 deletions(-)
 delete mode 100644 debian/patches/avoid_xkb_dep

diff --git a/debian/control b/debian/control
index 3ffada4..e6d6a03 100644
--- a/debian/control
+++ b/debian/control
@@ -10,8 +10,6 @@ Build-Depends: debhelper (>= 9.20150628),
dh-autoreconf,
dbus, libdbus-1-dev,
libglib2.0-dev,
-   libxkbcommon-x11-dev,
-   libxkbcommon-dev,
libxtst-dev,
libgirepository1.0-dev,
intltool, gtk-doc-tools (>= 1.09),
diff --git a/debian/patches/avoid_xkb_dep b/debian/patches/avoid_xkb_dep
deleted file mode 100644
index e1cbb73..000
--- a/debian/patches/avoid_xkb_dep
+++ /dev/null
@@ -1,19 +0,0 @@
-reported on https://bugzilla.gnome.org/show_bug.cgi?id=787756
-

- configure.ac |4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
 a/configure.ac
-+++ b/configure.ac
-@@ -109,8 +109,8 @@ AS_IF([test "x$enable_x11" = xno], [
- # XKB (optional)
- PKG_CHECK_MODULES(XKB, [xkbcommon-x11], [
-   AC_DEFINE(HAVE_XKB, 1, [Define to use XKB])
--  X11_CFLAGS="$X11_CFLAGS $XKB_CFLAGS"
--  X11_LIBS="$X11_LIBS $XKB_LIBS"
-+  #X11_CFLAGS="$X11_CFLAGS $XKB_CFLAGS"
-+  #X11_LIBS="$X11_LIBS $XKB_LIBS"
- ], [:])
-   ])
- 
diff --git a/debian/patches/series b/debian/patches/series
index 2b38357..54237f3 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1 @@
 at-spi-by-default
-avoid_xkb_dep
-- 
2.14.1

Bug#875963: python-azure: ships /usr/lib/python2.7/dist-packages/tests/init.py

2017-09-16 Thread Andreas Beckmann

Package: python-azure
Version: 20170915+git-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

/usr/lib/python2.7/dist-packages/test/__init__.py is a way too generic
name that shouldn't be used by any python module, since it can easily
lead to file conflicts between packages (that is how I noticed it).


cheers,

Andreas

Bug#875962: python-oauth2client: ships /usr/lib/python2.7/dist-packages/tests/init.py

2017-09-16 Thread Andreas Beckmann

Package: python-oauth2client
Version: 3.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

/usr/lib/python2.7/dist-packages/test/__init__.py is a way too generic
name that shouldn't be used by any python module, since it can easily
lead to file conflicts between packages (that is how I noticed it).


cheers,

Andreas

Bug#875929: acetoneiso: should it be removed from Debian

2017-09-16 Thread Nikos Andrikos

Hi Mattia,

The program is dead upstream and I have been maintainting (the bare
minimum) on my own.

I just saw that some months ago, people from Redhat ported it to Qt5.
I'll see what I can get from there, in order to include in a new upload.

For these reasons, I would prefer if the package is not removed for
now, in order to have enough time to fix the issues.

Kind regards,
Nikos
--
=Do-
N.AND

Bug#873374: marked as done (libtsk13 4.4.2-1 crash in the dfvfs test suite)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 15:07:50 +
with message-id 
and subject line Bug#873374: fixed in pytsk 20170802-2
has caused the Debian Bug report #873374,
regarding libtsk13 4.4.2-1 crash in the dfvfs test suite
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.)


-- 
873374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtsk13
Version: 4.4.2-1
Severity: serious
Control: affects -1 src:dfvfs python-tsk

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dfvfs-20170723'
python run_tests.py
testIterateVolumes (volume.vshadow_volume_system.VShadowVolumeSystemTest)
Test the iterate volumes functionality. ... ok
testIterateVolumes (volume.tsk_volume_system.TSKVolumeSystemTest)
Test the iterate volumes functionality. ... debian/rules:23: recipe for target 
'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Floating point exception


Program terminated with signal SIGFPE, Arithmetic exception.
#0  0x7fa2ac0f606a in dos_load_prim_table (test=1 '\001', 
vs=0x55c56dcae270) at dos.c:821
821 dos.c: No such file or directory.
(gdb) bt
#0  0x7fa2ac0f606a in dos_load_prim_table (test=1 '\001', 
vs=0x55c56dcae270) at dos.c:821
#1  tsk_vs_dos_open (img_info=0x7fa2a322c070, offset=0, 
test=test@entry=1 '\001') at dos.c:1064
#2  0x7fa2ac0f3161 in tsk_vs_open (img_info=0x7fa2a322c070, offset=0, 
type=) at mm_open.c:56
#3  0x7fa2ac3bf41e in Volume_Info_Con (self=0x55c56dcbe2f0, 
img=, type=, offset=)
at tsk3.c:659
#4  0x7fa2ac3b3ade in pyVolume_Info_init (self=self@entry=0x7fa2a31b4c70, 
args=args@entry=(, _is_open=True, _file_object=) at remote 0x7fa2a31b4550>) at remote 0x7fa2a31b4590>, 
u'type: OS, location: /tmp/dfvfs-20170723/test_data/bdetogo.raw\n': 
) at remote 
0x7fa2a31b4bd0>}) at remote 0x7fa2a3fbad90>, 
_file_system_cache=) at remote 0x7fa2a3fba390>, 
_is_open=True, _file_object=) at remote 
0x7fa2a31b4890>) at remote 0x7fa2a31994b0>,), kwds=kwds@entry=0x0)
at pytsk3.c:20444
#5  0x55c56b688bf4 in type_call.lto_priv () at ../Objects/typeobject.c:765
#6  0x55c56b683163 in PyObject_Call () at ../Objects/abstract.c:2547
...



Works after downgrading libtsk13 to 4.4.0-5
--- End Message ---
--- Begin Message ---
Source: pytsk
Source-Version: 20170802-2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated pytsk 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, 16 Sep 2017 16:30:52 +0200
Source: pytsk
Binary: python-tsk python3-tsk
Architecture: source
Version: 20170802-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics 
Changed-By: Hilko Bengen 
Description:
 python-tsk - Python Bindings for The Sleuth Kit
 python3-tsk - Python Bindings for The Sleuth Kit
Closes: 873374
Changes:
 pytsk (20170802-2) unstable; urgency=medium
 .
   * Link libtsk statically, add Built-Using entry (Closes: #873374)
   * Modernize package: DH compat level, Standards-Version, Vcs-Git URL
Checksums-Sha1:
 628f470f6ebdc1227e05cec2882f07083a120d3f 2078 pytsk_20170802-2.dsc
 361e56011a6ce037c66909d31433ffc82fc856a7

Bug#875881: linux: CVE-2017-1000251

2017-09-16 Thread Julien Aubin

2017-09-15 21:03 GMT+02:00 Christoph Anton Mitterer :

> On Fri, 2017-09-15 at 19:18 +0100, Ben Hutchings wrote:
> > Probably less critical than you think, since we enable
> > CONFIG_CC_STACKPROTECTOR.
>
> Well... yes, but it wouldn't be the first time in history, that such
> defence could then also be circumvented in the next evolution of an
> exploit :-)
>
> But of course you can lower the bug severity if you think this is
> appropriate.
>
> Cheers


Looks like such issue has been found, stack clash is back :
https://security-tracker.debian.org/tracker/CVE-2017-1000379

Processed: severity of 875958 is normal, tagging 875958

2017-09-16 Thread Debian Bug Tracking System

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

> severity 875958 normal
Bug #875958 [sa-compile] sa-compile: The package fails to run sa-compile
Severity set to 'normal' from 'grave'
> tags 875958 + unreproducible
Bug #875958 [sa-compile] sa-compile: The package fails to run sa-compile
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#875958: sa-compile: The package fails to run sa-compile

2017-09-16 Thread Bernard

Package: sa-compile
Version: 3.4.1-6
Severity: grave
Justification: renders package unusable

The only purpose of the package is to run the program sa-compile.

For this is contains a single command line in postint (post installation
scripts)

like: su - debian-spamd -c sa-compile
The program line should be "su debian-spamd -c sa-compile" (I think).

sa-compile compiles rules in /var/lib/spamassassin/compiled. Directory and
files should be owned by debian-spamd.debian-spamd.

Anyway, it fails and as a result spamassassin cannot be installed
(configuration fails).




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

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

Versions of packages sa-compile depends on:
ii  gcc   4:6.3.0-4
ii  libc6-dev 2.24-11+deb9u1
ii  make  4.1-9.1
pn  re2c  
pn  spamassassin  

sa-compile recommends no packages.

sa-compile suggests no packages.

Bug#875957: camlidl: uninstallable in sid

2017-09-16 Thread Ole Streicher

Package: camlidl
Version: 1.05-15
Severity: serious
Affects: src:plplot

Dear maintainer,

camlidl is currently not installable in sid, due to an unresolved
dependency:

# apt install camlidl
[...]
The following packages have unmet dependencies:
 camlidl : Depends: ocaml-nox-4.02.3 but it is not installable
E: Unable to correct problems, you have held broken packages.

This looks like it is broken by updating ocaml.

This causes FTBFS for the new plplot version.

Best regards

Ole

Bug#875948: doxia-sitetools: FTBFS due to missing build dependencies

2017-09-16 Thread Hans Joachim Desserud


Control: tags -1 patch


see the attached patch.


...and if I actually attach it this time, this might help even more :)

--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/control b/debian/control
index 3b2ae09..edb91cd 100644
--- a/debian/control
+++ b/debian/control
@@ -9,6 +9,7 @@ Build-Depends: debhelper (>= 10),
maven-debian-helper (>= 1.4)
 Build-Depends-Indep: default-jdk-doc,
  junit (>= 3.8.2),
+ jython,
  libcommons-collections3-java,
  libdoxia-java (>= 1.7),
  libdoxia-java-doc,
@@ -23,6 +24,7 @@ Build-Depends-Indep: default-jdk-doc,
  libplexus-i18n-java,
  libplexus-utils2-java,
  libplexus-utils2-java-doc,
+ librhino-java,
  libvelocity-tools-java,
  libxalan2-java,
  libxalan2-java-doc

Processed: Re: doxia-sitetools: FTBFS due to missing build dependencies

2017-09-16 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #875948 [src:doxia-sitetools] doxia-sitetools: FTBFS due to missing build 
dependencies
Added tag(s) patch.

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

Bug#875952: moon-lander: contains unlicensed images (and perhaps sounds)

2017-09-16 Thread Stephen Kitt

Package: moon-lander
Version: 1:1.0-5+b1
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,

images/backgrounds contains NASA photos which aren’t DFSG-free AFAIK.
The sound files in sounds don’t have a documented origin.

Regards,

Stephen


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

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

Versions of packages moon-lander depends on:
ii  libc6 2.24-11+deb9u1
ii  libsdl-image1.2   1.2.12-5+b8
ii  libsdl-mixer1.2   1.2.12-11+b3
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  moon-lander-data  1:1.0-5

moon-lander recommends no packages.

moon-lander suggests no packages.

-- no debconf information

Bug#853559: mozjs24: ftbfs with GCC-7

2017-09-16 Thread Páder Rezső

Simply replace '\0' with NULL in js/src/shell/jsoptparse.cpp:256.

-- 
R.

Bug#875948: doxia-sitetools: FTBFS due to missing build dependencies

2017-09-16 Thread Hans Joachim Desserud


Source: doxia-sitetools
Version: 1.7.4-2
Severity: serious
Tag: patch

Dear Maintainer,

doxia-sitetools currently fails to build from source with the following
error message:

[ERROR] Failed to execute goal on project doxia-doc-renderer: Could not 
resolve dependencies for project 
org.apache.maven.doxia:doxia-doc-renderer:jar:1.7.4: The following 
artifacts could not be resolved: org.mozilla:rhino:jar:debian, 
org.python:jython:jar:debian: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.mozilla:rhino:jar:debian has not been downloaded from it before. -> 
[Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

[ERROR]
[ERROR] After correcting the problems, you can resume the build with the 
command

[ERROR]   mvn  -rf :doxia-doc-renderer

Please see 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/doxia-sitetools.html

for more details.

I was able to reproduce this issue in pbuilder on Sid.
After adding the missing build dependencies, the package
built successfully, see the attached patch.

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#875897: marked as done (Could not find gem 'sass-listen (~> 4.0.0)', which is required by gem 'sass (~>3.1)', in any of the sources)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 12:37:01 +
with message-id 
and subject line Bug#875897: fixed in ruby-sass 3.5.1-2
has caused the Debian Bug report #875897,
regarding Could not find gem 'sass-listen (~> 4.0.0)', which is required by gem 
'sass (~>3.1)', in any of the sources
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.)


-- 
875897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-sass
Version: 3.5.1-1
Severity: serious
Justification: FTBFS of other packages (devise, open-build-service)

ruby-devise and ruby-open-build-service build failed with below error.


Bundler could not find compatible versions for gem "sass-listen":
  In Gemfile:
sass-rails (~> 5.0) was resolved to 5.0.6, which depends on
  sass (~> 3.1) was resolved to 3.5.1, which depends on
sass-listen (~> 4.0.0)

Could not find gem 'sass-listen (~> 4.0.0)', which is required by gem
'sass (~>3.1)', in any of the sources.


Autopkgtest of ruby-sass-rails is also failing
(https://ci.debian.net/data/packages/unstable/amd64/r/ruby-sass-rails/latest-autopkgtest/log.gz).



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-sass
Source-Version: 3.5.1-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ruby-sass 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, 16 Sep 2017 14:12:31 +0200
Source: ruby-sass
Binary: ruby-sass
Architecture: source all
Version: 3.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Sass team 
Changed-By: Jonas Smedegaard 
Description:
 ruby-sass  - powerful but elegant CSS compiler that makes CSS fun again
Closes: 875897
Changes:
 ruby-sass (3.5.1-2) unstable; urgency=medium
 .
   * Fix suggest ruby-sass-listen (not recommend ruby-listen).
   * Add patch to avoid gemspec dependency on sass-listen: Needed only
 for --watch option, and library is not in Debian.
 Closes: Bug#875897. Thanks to Sruthi Chandran.
Checksums-Sha1:
 346bc1ee489d0233430eef840a429abc157ba91a 1951 ruby-sass_3.5.1-2.dsc
 4e3782516a4346d4941326610060108eece54f4a 13480 ruby-sass_3.5.1-2.debian.tar.xz
 d01e7df25288aa309f9200f799a2772d562d14b0 231534 ruby-sass_3.5.1-2_all.deb
 639043be7d0388d84f529f8be8e476065b46dee4 6428 ruby-sass_3.5.1-2_amd64.buildinfo
Checksums-Sha256:
 b8b5096795ed8ff6b000e954b121c767965a5e53c665d8248d5e63cca96c313e 1951 
ruby-sass_3.5.1-2.dsc
 24018efedef29a5d0cf562c00ac7fbd94523206b5fa803f43c99d4be1508e520 13480 
ruby-sass_3.5.1-2.debian.tar.xz
 9d294de874af7b9c18f1f3065acfcd540f0b767d6c39dbc318f3e915137f2fb3 231534 
ruby-sass_3.5.1-2_all.deb
 10746f6396c15d2f1988734ecac10f09817381d1c0459cf3a2c094072418c485 6428 
ruby-sass_3.5.1-2_amd64.buildinfo
Files:
 dfc4c3c65df934acbd3a99564d2c9ce1 1951 web optional ruby-sass_3.5.1-2.dsc
 e8bbeeddf0766298aeb24532073aa654 13480 web optional 
ruby-sass_3.5.1-2.debian.tar.xz
 fc398ebcd55f8a7ef5966946f9b55a09 231534 web optional ruby-sass_3.5.1-2_all.deb
 c2365de6cfdbb8136b870e98ed30820d 6428 web optional 
ruby-sass_3.5.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlm9FfUACgkQLHwxRsGg
ASFmMBAAqpbFXFCqVNh9lbfDXOAl+tj10vfty+f1M6/zSdOTkH+cH/SBsbfYOw1t
uQUo/u7FPtq3kUgm4T3hvVP5ifWq2BBEwQocjLL6m/A8+3o/namfg8CsnEIkf+ca
h4IRjAhs67Wb/MKTws19BxRFeDSvnkvcJSKoe+siu7JgiWmAjQ2j72sORYI2/gII
PKebvE/E/bS8UcyiMVYKzhfkIJHxO+bVAVP3O9pu8J0kWV7SHMfzd9gYTdkCC8H9
FgzeGnAq05H6AOKsuEgpiVk1RPQZpwCE8nk91rAEMvlcmd+TZrGqNhehexuhIXA9
And79roui0eNnzPbgALwLv1xHrvXf/2RUuq79Uih2YgkW4/Ye0XzpudMQsHUyrcO
by+IZGkTy1DfI7fH/bwy024DhEXcCz7DFXVm9IhiJcMZUPsoED2O7JHMUvUr+mqZ
Jqemw/lNSGb1uzYlwHMz6Z0hRRfn04XQDS3Tksplo0E8LoL/UpE3Q3RzspzXmc/B
rmS/2r4vhrHcQV6rRlhFs2jWdgYRJT7GkbVQ1w2b6PmKdCVYyqZoAlet+DaBARSc

Bug#875818: dbusada: FTBFS on arm* and alpha: Class_va_list undeclared

2017-09-16 Thread Nicolas Boulenguez

Package: src:dbusada
Followup-For: Bug #875818

Hello.
The attached patch fixes both issues, and removes the now unused
stdarg_h.ads.
It compiles on amd64, i386 and armel.
From: Nicolas Boulenguez 
Subject: Remove dangling references from g++ generated code. Closes: #875818.

--- a/debian/patches/refresh-thin.diff
+++ b/debian/patches/refresh-thin.diff
@@ -20,7 +20,7 @@ Author: Nicolas Boulenguez 
  	gnatmake $(GMAKE_OPTS) -Pd_bus_ada_examples -XLIBRARY_KIND=static
  
  install: install_lib install_$(LIBRARY_KIND)
-@@ -79,9 +79,37 @@
+@@ -79,9 +79,48 @@
  	@rm -rf $(OBJDIR)
  	@rm -rf $(LIBDIR)
  	@rm -rf $(DOCDIR)
@@ -47,8 +47,13 @@ Author: Nicolas Boulenguez 
 +	$(CXX) --dump-ada-spec $(dbus_h) `pkg-config --cflags $(dbus_lib)`
 +  # Remove unused file.
 +	rm -f $@/*_dbus_syntax_h.ads
-+  # Fix an error.
-+	sed -i '/^   subtype nullptr_t is ;  --/d' $@/stddef_h.ads
++	rm -f $@/stdarg_h.ads
++  # Removed a wrongly generated definition and a reference to an
++  # ungenerated type.  Neither one is used in dbusada.
++	sed -i \
++	  -e '/^   subtype nullptr_t is ;  --/d' \
++	  -e '/uu_float128/d' \
++	  $@/stddef_h.ads
 +  # Remove arch, path or version dependent prefixes.
 +	cd $@ && for i in *dbus_dbus_*; do \
 +	  mv $$i `echo $$i | sed 's/.*dbus_dbus_/dbus_/'`; \
@@ -58,5 +63,11 @@ Author: Nicolas Boulenguez 
 +	sed -i '/^with Interfaces\.C; use Interfaces\.C;$$/d' \
 +	  $@/dbus_memory_h.ads \
 +	  $@/dbus_pending_call_h.ads \
-+	  $@/dbus_shared_h.ads \
-+	  $@/stdarg_h.ads
++	  $@/dbus_shared_h.ads
++  # On arm processors, g++-7 generates a reference to starg_h.Class_va_list,
++  # but does not generate the referenced package.
++  # Remove the function using this reference, dbusada does not use it.
++	sed -i \
++	  -e '/^with stdarg_h;$$/d' \
++	  -e '/^   function dbus_message_\(append\|get\)_args_valist$$/{:l;N;/\n$$/d;bl}' \
++	  $@/dbus_message_h.ads

Bug#872874: marked as done (libxkbcommon-x11-dev: Missing depends on libxkbcommon-dev)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 12:04:56 +
with message-id 
and subject line Bug#872874: fixed in libxkbcommon 0.7.1-2
has caused the Debian Bug report #872874,
regarding libxkbcommon-x11-dev: Missing depends on libxkbcommon-dev
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.)


-- 
872874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxkbcommon-x11-dev
Version: 0.7.1-1
Severity: serious

libxkbcommon-x11-dev has this line in its pkgconfig file:

Requires: xkbcommon

That means it needs a Depends on libxkbcommon-dev .

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: libxkbcommon
Source-Version: 0.7.1-2

We believe that the bug you reported is fixed in the latest version of
libxkbcommon, 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.
Julien Cristau  (supplier of updated libxkbcommon 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, 16 Sep 2017 13:40:36 +0200
Source: libxkbcommon
Binary: libxkbcommon0 libxkbcommon-dev libxkbcommon-x11-0 libxkbcommon-x11-dev
Architecture: source
Version: 0.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 libxkbcommon-dev - library interface to the XKB compiler - development files
 libxkbcommon-x11-0 - library to create keymaps with the XKB X11 protocol
 libxkbcommon-x11-dev - library to create keymaps with the XKB X11 protocol - 
development
 libxkbcommon0 - library interface to the XKB compiler - shared library
Closes: 872874
Changes:
 libxkbcommon (0.7.1-2) unstable; urgency=medium
 .
   * Remove Cyril from Uploaders.
   * Add missing dependency libxkbcommon-x11-dev → libxkbcommon-dev
 (closes: #872874).
Checksums-Sha1:
 bbc964a0c158100682d3986f2ab24e7f2bfa2dfe 2333 libxkbcommon_0.7.1-2.dsc
 74ef9caf8715300f2d60476db4209e3774739772 31259 libxkbcommon_0.7.1-2.diff.gz
Checksums-Sha256:
 318aaf484826abf397a2762d869fb35a368e868c2cdb483bdb5519ada8f52748 2333 
libxkbcommon_0.7.1-2.dsc
 ab2a3ccadbd01227f9f57393aeb46f2719655508f69424e01bf9f61b10c854eb 31259 
libxkbcommon_0.7.1-2.diff.gz
Files:
 6c3ad87ba8ffa928c95ddb9898e349ae 2333 x11 optional libxkbcommon_0.7.1-2.dsc
 2b4cdaeab075b3029389a4e4b84f8a5d 31259 x11 optional 
libxkbcommon_0.7.1-2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAlm9DlIACgkQnbAjVVb4
z60HSQ/+P92YyPx+WQLpzRex5V3Aor+bhMFa+FMWQng/q3EPceJfChAtwBt8cKt4
4XI7Uk4SBVcbFeEHWtxlXGNbUgiGDh+N7q7SMfrWun71VWydOGbOOHp1+NXZvkaM
iVt14atHNas+WAePNLV4CPysUIZeaAdiD3SHyqQRwQG0GNF7Ca+DMl2FSwH+xvP/
H3177bv6lL9Fxp5Kx3HoPb6EUYhOsJ5YbcbvXuMnmQ2kKVaxSRhjzMUf4sc0qmEh
YkZ1NV5W/+5CYf5/+JnguRuHJdD/lwTP0VZqfV1G4D+60xHroP/UykuwPw38n6FT
FhTiM4JupgBmigvBkP9OtMvjHuga1TqWj3yFHclm/8QnxyQs8PrJXmuLe94T+q3d
shv51eEPjix5ouV+BE8jkakvD7OQpvcXUQXHy3JPgdEaB8ta5WhFnbfCmcvZjSOQ
OcAbTdAKIRH0Bwfmt5y3PW+8b6Qe4zWZtpi2fEbKDhVLx9cto0TI5exdFdws3Rvc
mSZIekZLI/PQd4nVm4ED1F4IrxAq9gySWjZrLpZvn9DJQAUu+x3HWK3bwL39ttOB
bzXR81J6g/4C2rOsYN2XM/MVLYb9bunU8GcAnzqWplH4NKOgMjRCQFEtxX644zxD
vxkaELK5//wZ1DnzLMN+PJyNcD7aEFXyXFtXNLpgHYlyIwMomDg=
=uTLi
-END PGP SIGNATURE End Message ---

Bug#873374: libtsk13 4.4.2-1 crash in the dfvfs test suite

2017-09-16 Thread Hilko Bengen

* Eriberto Mota:

> Control: reassign 873374 python-tsk
>
> After a conversation with upstream[1] and several tests, I can confirm
> the problem is being caused by python-tsk package. Rebuilding the
> package will solve the problem.

Thank you for doing the testing and getting to the root of this!

I must say that I am a bit surprised that this has become a problem, I
was not expecting there to be ABI breakage.

I'll have to figure out how to statically link libtsk and do the upload.

Cheers,
-Hilko

Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

2017-09-16 Thread Cyril Brulebois

Samuel Thibault  (2017-09-16):
> Cyril Brulebois, on sam. 16 sept. 2017 13:21:53 +0200, wrote:
> > Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a
> > package which isn't a udeb: libxkbcommon-x11-0;
> 
> Mmm, looking at it, it seems spurious actually:
> 
> libxkbcommon-x11.so.0 (it uses none of the library's symbols)
> 
> Indeed, it actually only uses functions from libX11... For now I have
> uploaded a package which does not link to xkbcommon, and will report to
> upstream that they should check for presence of the needed functions in
> libX11 itself.

Perfect, thanks.


KiBi.


signature.asc
Description: PGP signature

Bug#875945: marked as done (libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 11:49:00 +
with message-id 
and subject line Bug#875945: fixed in at-spi2-core 2.26.0-2
has caused the Debian Bug report #875945,
regarding libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0
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.)


-- 
875945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libatspi0-udeb
Version: 2.26.0-1
Severity: serious
Tags: d-i
Justification: not installable

[X-D-Ccing debian-boot@ and debian-x@ for information.]

Hi,

Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a
package which isn't a udeb: libxkbcommon-x11-0; I'm filing this bug
report against libatspi0-udeb (only) because that's the one in the
dependency chain from libgtk-3-0-udeb, which we might use at some point…


KiBi.
--- End Message ---
--- Begin Message ---
Source: at-spi2-core
Source-Version: 2.26.0-2

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated at-spi2-core 
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, 16 Sep 2017 13:42:33 +0200
Source: at-spi2-core
Binary: at-spi2-core at-spi2-core-udeb libatspi2.0-0 libatspi0-udeb 
libatspi2.0-dev gir1.2-atspi-2.0 at-spi2-doc
Architecture: source
Version: 2.26.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 at-spi2-core - Assistive Technology Service Provider Interface (dbus core)
 at-spi2-core-udeb - Assistive Technology Service Provider Interface (dbus core 
for d- (udeb)
 at-spi2-doc - Assistive Technology Service Provider Interface (Documentation)
 gir1.2-atspi-2.0 - Assistive Technology Service Provider (GObject 
introspection)
 libatspi0-udeb - Assistive Technology Service Provider Interface - module for 
d-i (udeb)
 libatspi2.0-0 - Assistive Technology Service Provider Interface - shared 
library
 libatspi2.0-dev - Development files for the assistive technology service 
provider
Closes: 875945
Changes:
 at-spi2-core (2.26.0-2) unstable; urgency=medium
 .
   * patches/avoid_xkb_dep: Do not link against xkbcommon, we don't actually
 need it (Closes: Bug#875945).
Checksums-Sha1:
 78199053b28c934bee672dd47d7d4d35f34fb524 2600 at-spi2-core_2.26.0-2.dsc
 16aa5aed6e3e95d89ead199b0a5a5126d1f9eac0 8896 
at-spi2-core_2.26.0-2.debian.tar.xz
Checksums-Sha256:
 f8bcfd3432eccd900951abc2e6b1d6046ed2fc89a8e5600fdad9ef0792221804 2600 
at-spi2-core_2.26.0-2.dsc
 4c234e3aa03eb222cdd207d3ccfff41fe598080bf749d99a63127436a426551f 8896 
at-spi2-core_2.26.0-2.debian.tar.xz
Files:
 2124575c74dbf47489940ff25a77acce 2600 misc optional at-spi2-core_2.26.0-2.dsc
 c6c379d7398a82e37622c00d541674c3 8896 misc optional 
at-spi2-core_2.26.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErr90SPq5RTpFUjkOsKUb9YyRecUFAlm9Dq4ACgkQsKUb9YyR
ecVziw/7BHubOAlxXYRHUuOg8a+n2tqaXj/kwABfV5wsTsXUaUN70Od1yNUVaxkp
ajAM6W5Z+24A16jhDulm6LHyu5QPMae9YMJ2bpz7RRhqpabtGijSZ+hzAD9yFfvS
UZ+FLx5oIIi9cgVg5OyGCr2Fi4c/x/X6wWZxh/pG+AOd9FS2n6K4QknY0WxBta1D
Ttw0yK8rpRAlIhKrl9U9TGcfWpfykQafsdb2G3o1hEovFolHU6vJdlAZhnoqO7ZG
+q3XNKyPgrDAfON/SYKzuzI3TOdPb1NlYgVRLSl3Dad+E7axmpTomMIG5M0kH5Cf
iZBfl1a/eSDznkR5MFxjOLriz37cxUDO0r+5C1nnqdqL+eDF4aQhTUpnuwImyB2h
J2kfZIKVasmQZfXv7Uz+TNPDHvFRV5WrAjX/nKvtDJ7lg2yxZU+xOepAA+37oDWD
8fGnBHU8igh1Jld+LUXMMK2m8jYqgZmDr7e7kyz0rK4EZbjvbKNlr1dElluLI8th
/zN312oxZI3ykEr/BVw0rY6d4a06Amvg28/qG7GREs8z/xPGLJgOF/09WINJYOOP
nBjjR6RxL9+QT5iLgk92eFmDdU5WLnNbGLHnEs2JysdDUqFxXixeATulsIVYIdmD
tyaq/0/8yQRE8BV7y58jGBFLtcqElw2FPcXZql1Nm4uhTH72C8w=
=bo6t
-END PGP SIGNATURE End Message ---

Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

2017-09-16 Thread Samuel Thibault

Control: tags -1 + pending

Hello,

Cyril Brulebois, on sam. 16 sept. 2017 13:21:53 +0200, wrote:
> Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a
> package which isn't a udeb: libxkbcommon-x11-0;

Mmm, looking at it, it seems spurious actually:

libxkbcommon-x11.so.0 (it uses none of the library's symbols)

Indeed, it actually only uses functions from libX11... For now I have
uploaded a package which does not link to xkbcommon, and will report to
upstream that they should check for presence of the needed functions in
libX11 itself.

Samuel

Processed: Re: Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

2017-09-16 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + pending
Bug #875945 [libatspi0-udeb] libatspi0-udeb: uninstallable, depends on 
libxkbcommon-x11-0
Added tag(s) pending.

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

Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

2017-09-16 Thread Cyril Brulebois

Package: libatspi0-udeb
Version: 2.26.0-1
Severity: serious
Tags: d-i
Justification: not installable

[X-D-Ccing debian-boot@ and debian-x@ for information.]

Hi,

Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a
package which isn't a udeb: libxkbcommon-x11-0; I'm filing this bug
report against libatspi0-udeb (only) because that's the one in the
dependency chain from libgtk-3-0-udeb, which we might use at some point…


KiBi.

Bug#870363: not fixed by 868308

2017-09-16 Thread 積丹尼 Dan Jacobson

I am not trying to install sane-backends.

I am just trying to do aptitude full-upgrade without any error messages.

This is the only package on the entire Debian that is making such error 
messages.

Bug#870363: not fixed by 868308

2017-09-16 Thread 積丹尼 Dan Jacobson

Please tell me what steps will make the error messages go away.

Bug#868308: marked as done (file conflict with libsane)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 11:23:23 +0200
with message-id <1505553803.9909.6.ca...@jff-webhosting.net>
and subject line Re: Bug#870363: not fixed by 868308
has caused the Debian Bug report #870363,
regarding file conflict with libsane
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.)


-- 
870363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsane1
Version: 1.0.27-1~experimental1
Severity: serious

The libsane package in experimental was renamed from libsane to
libsane1, yet it ships the same contents, e.g.
/usr/lib/x86_64-linux-gnu/libsane.so.1

This leads to a file conflicts between the two packages and failure to
install/upgrade the libsane1 package.


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

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)

Versions of packages libsane1 depends on:
ii  acl2.2.52-3+b1
ii  adduser3.115
ii  libavahi-client3   0.6.32-2
ii  libavahi-common3   0.6.32-2
ii  libc6  2.24-12
ii  libgphoto2-6   2.5.13-3
ii  libgphoto2-port12  2.5.13-3
ii  libieee1284-3  0.2.11-13
ii  libjpeg62-turbo1:1.5.1-2
ii  libsane-common 1.0.26~git20151121-1
ii  libtiff5   4.0.8-3
ii  libusb-1.0-0   2:1.0.21-2
ii  makedev2.3.1-93
ii  udev   234-1

Versions of packages libsane1 recommends:
ii  libsane-extras  1.0.22.4
ii  sane-utils  1.0.26~git20151121-1

Versions of packages libsane1 suggests:
ii  avahi-daemon  0.6.32-2
pn  hplip 
--- End Message ---
--- Begin Message ---
Hello Dan,


thank you for spending your time helping to make Debian better with
this bug report. 


Am Samstag, den 16.09.2017, 02:50 +0800 schrieb 積丹尼 Dan Jacobson:
> Note all these problems are still currently present:
> 
> The following packages have unmet dependencies:
>  libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
>  libsane : Depends: libsane-common (= 1.0.25-4.1) but 1.0.27-1~experimental2 
> is to be installed
> 

As described at[1] you can't install sane-backends from experimental
into sid/buster without transition.

Or you must first rebuild all reverse depends of sane-backends. 


So I close this bug.


CU
Jörg

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870363#10
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#870363: marked as done (libsane : Depends: libsane-common (= 1.0.26~git20151121-1) but 1.0.27-1~experimental1 is to be installed)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 11:23:23 +0200
with message-id <1505553803.9909.6.ca...@jff-webhosting.net>
and subject line Re: Bug#870363: not fixed by 868308
has caused the Debian Bug report #870363,
regarding libsane : Depends: libsane-common (= 1.0.26~git20151121-1) but 
1.0.27-1~experimental1 is 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.)


-- 
870363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsane
Version: 1.0.26~git20151121-1
Severity: minor

The following packages have unmet dependencies:
 libsane : Depends: libsane-common (= 1.0.26~git20151121-1) but 
1.0.27-1~experimental1 is to be installed

-- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (990, 'experimental'), (500, 'unstable-debug'), (500, 
'unstable'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Hello Dan,


thank you for spending your time helping to make Debian better with
this bug report. 


Am Samstag, den 16.09.2017, 02:50 +0800 schrieb 積丹尼 Dan Jacobson:
> Note all these problems are still currently present:
> 
> The following packages have unmet dependencies:
>  libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
>  libsane : Depends: libsane-common (= 1.0.25-4.1) but 1.0.27-1~experimental2 
> is to be installed
> 

As described at[1] you can't install sane-backends from experimental
into sid/buster without transition.

Or you must first rebuild all reverse depends of sane-backends. 


So I close this bug.


CU
Jörg

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870363#10
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#870363: not fixed by 868308

2017-09-16 Thread Jörg Frings-Fürst

Hello Dan,


thank you for spending your time helping to make Debian better with
this bug report. 


Am Samstag, den 16.09.2017, 02:50 +0800 schrieb 積丹尼 Dan Jacobson:
> Note all these problems are still currently present:
> 
> The following packages have unmet dependencies:
>  libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
>  libsane : Depends: libsane-common (= 1.0.25-4.1) but 1.0.27-1~experimental2 
> is to be installed
> 

As described at[1] you can't install sane-backends from experimental
into sid/buster without transition.

Or you must first rebuild all reverse depends of sane-backends. 


So I close this bug.


CU
Jörg

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870363#10
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#784509: marked as done ([postbooks-updater] Qt4's WebKit removal)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 08:53:19 +
with message-id 
and subject line Bug#784509: fixed in postbooks-updater 2.4.0-5
has caused the Debian Bug report #784509,
regarding [postbooks-updater] Qt4's WebKit removal
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.)


-- 
784509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postbooks-updater
Version: 2.2.5-8
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian xTuple Maintainers ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: postbooks-updater
Source-Version: 2.4.0-5

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

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated postbooks-updater 
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, 16 Sep 2017 09:12:08 +0200
Source: postbooks-updater
Binary: postbooks-updater
Architecture: source amd64
Version: 2.4.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian xTuple Maintainers 

Changed-By: Daniel Pocock 
Description:
 postbooks-updater - multi-user accounting / CRM / ERP suite (database update 
manager)
Closes: 784509
Changes:
 postbooks-updater (2.4.0-5) unstable; urgency=medium
 .
   * Remove build-dep libqtwebkit-dev (Closes: #784509)
Checksums-Sha1:
 0224d03c4f12a033b1b9f0917d46a52158351e03 2353 postbooks-updater_2.4.0-5.dsc
 939b3d2abe3cf0871e11bdd836be7845b249e198 12696 
postbooks-updater_2.4.0-5.debian.tar.xz
 b46119d4eb3bb50bea7255ecd0154d80ceb6277d 3006492 
postbooks-updater-dbgsym_2.4.0-5_amd64.deb
 f78ab4eb2bcedb242266935d172b5e642c3d95f6 11598 
postbooks-updater_2.4.0-5_amd64.buildinfo
 89351c57c5040cbcb3860b85c3a6147ec21725e6 130400 
postbooks-updater_2.4.0-5_amd64.deb
Checksums-Sha256:
 8836612ed241bb0eb551fdae2fc2d4417ab866d9f96bfc41f86ef044f43ade32 2353 
postbooks-updater_2.4.0-5.dsc
 40d1ba3ca0da64c679fad2e5762d489d2b40ae4b65f94e45f210f08b2e61e653 12696 
postbooks-updater_2.4.0-5.debian.tar.xz

Bug#875875: marked as done (gr-fcdproplus: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-fcdproplus.pc)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 08:51:14 +
with message-id 
and subject line Bug#875875: fixed in gr-fcdproplus 3.7.25.4b6464b-5
has caused the Debian Bug report #875875,
regarding gr-fcdproplus: fails to upgrade from 'stable' to 'sid' - trying to 
overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-fcdproplus.pc
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.)


-- 
875875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gr-fcdproplus
Version: 3.7.25.4b6464b-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skips 'testing' to find file overwrite problems
before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package gr-fcdproplus.
  Preparing to unpack .../14-gr-fcdproplus_3.7.25.4b6464b-4_amd64.deb ...
  Unpacking gr-fcdproplus (3.7.25.4b6464b-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-8H4jpD/14-gr-fcdproplus_3.7.25.4b6464b-4_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-fcdproplus.pc', which is also in 
package libgnuradio-fcdproplus3.7.10 3.7.25.4b6464b-2+b2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-8H4jpD/14-gr-fcdproplus_3.7.25.4b6464b-4_amd64.deb


After moving the .pc file to a different package, you of course
need to add (versioned) Breaks+Replaces against the packages that
previously contained the file. In this case that should be:

  Breaks:   libgnuradio-fcdproplus3.7.10 (<< 3.7.25.4b6464b-3), 
libgnuradio-fcdproplus3.7.11 (<< 3.7.25.4b6464b-4),
  Replaces: libgnuradio-fcdproplus3.7.10 (<< 3.7.25.4b6464b-3), 
libgnuradio-fcdproplus3.7.11 (<< 3.7.25.4b6464b-4),


cheers,

Andreas


libgnuradio-fcdproplus3.7.10=3.7.25.4b6464b-2+b2_gr-fcdproplus=3.7.25.4b6464b-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gr-fcdproplus
Source-Version: 3.7.25.4b6464b-5

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-fcdproplus 
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, 16 Sep 2017 03:25:39 -0400
Source: gr-fcdproplus
Binary: gr-fcdproplus libgnuradio-fcdproplus3.7.11
Architecture: source
Version: 3.7.25.4b6464b-5
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 gr-fcdproplus - Funcube Dongle Pro Plus controller for GNU Radio
 libgnuradio-fcdproplus3.7.11 - Funcube Dongle Pro Plus controller for GNU 
Radio (runtime)
Closes: 875875
Changes:
 gr-fcdproplus (3.7.25.4b6464b-5) unstable; urgency=medium
 .
   * add breaks/replaces line to hint upgrade (Closes: #875875)
Checksums-Sha1:
 05edf42ab483be16e0d3e5571c9cd3418e27f409 2313 
gr-fcdproplus_3.7.25.4b6464b-5.dsc
 69ca32909279e5cf8fb3f1ee4ad7e3d03c4a9070 191684 
gr-fcdproplus_3.7.25.4b6464b-5.debian.tar.xz
 cd2223822d173fd60d744b39899db99bb6b7ad60 16081 
gr-fcdproplus_3.7.25.4b6464b-5_amd64.buildinfo
Checksums-Sha256:
 28f8c250965ee5801d5b6c8ca53be72097e3aff1d837b2dd1287eeb09d115a7c 2313 
gr-fcdproplus_3.7.25.4b6464b-5.dsc
 2759c98b4d226a2bbbe5c6f2993f5aa0c86404ac6e2c0549bef5a516cc8eff92 191684 
gr-fcdproplus_3.7.25.4b6464b-5.debian.tar.xz
 486880653f77606fec3fb2e5c91ec7f2940ad2f0296c0fa954c97760c6793f94 16081 
gr-fcdproplus_3.7.25.4b6464b-5_amd64.buildinfo
Files:
 3566724621978359f2f64128c96a51e2 2313 science optional

Bug#875787: marked as done (libgnuradio-iqbalance3.7.11: fails to upgrade from 'stretch' - trying to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-iqbalance.pc)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 08:51:20 +
with message-id 
and subject line Bug#875787: fixed in gr-iqbal 0.37.2-10
has caused the Debian Bug report #875787,
regarding libgnuradio-iqbalance3.7.11: fails to upgrade from 'stretch' - trying 
to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-iqbalance.pc
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.)


-- 
875787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnuradio-iqbalance3.7.11
Version: 0.37.2-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libgnuradio-iqbalance3.7.11.
  Preparing to unpack .../libgnuradio-iqbalance3.7.11_0.37.2-8_amd64.deb ...
  Unpacking libgnuradio-iqbalance3.7.11 (0.37.2-8) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgnuradio-iqbalance3.7.11_0.37.2-8_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-iqbalance.pc', which is also in 
package libgnuradio-iqbalance3.7.10 0.37.2-7+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libgnuradio-iqbalance3.7.11_0.37.2-8_amd64.deb


Doesn't the .pc file belong into a -dev package?


cheers,

Andreas


libgnuradio-iqbalance3.7.10=0.37.2-7+b2_libgnuradio-iqbalance3.7.11=0.37.2-8.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gr-iqbal
Source-Version: 0.37.2-10

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-iqbal 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, 16 Sep 2017 03:53:56 -0400
Source: gr-iqbal
Binary: gr-iqbal libgnuradio-iqbalance3.7.11
Architecture: source
Version: 0.37.2-10
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 gr-iqbal   - GNU Radio Blind IQ imbalance estimator and correction
 libgnuradio-iqbalance3.7.11 - GNU Radio Blind IQ imbalance estimator and 
correction (runtime)
Closes: 875787
Changes:
 gr-iqbal (0.37.2-10) unstable; urgency=medium
 .
   * Add conflicts/replaces lines (Closes: #875787)
Checksums-Sha1:
 8c32e97620f7aacea30ced3e920b57a795a2c594 2410 gr-iqbal_0.37.2-10.dsc
 f25e916b06554b4fee5c2bc430df5e4e04d2650a 8524 gr-iqbal_0.37.2-10.debian.tar.xz
 ad80bed29a4a464040a1a247acc73187f8445b8e 15647 
gr-iqbal_0.37.2-10_amd64.buildinfo
Checksums-Sha256:
 678260b171929ce385f4408a918aa3db88c318ca723b2a14b7d76f85a177a32f 2410 
gr-iqbal_0.37.2-10.dsc
 db656317525668bf59059b75ba78ae6293702a9aba850f996d92886865581fd9 8524 
gr-iqbal_0.37.2-10.debian.tar.xz
 b84a4cd13cf1ff231927a548b33bac25ccfde942bd456ecb1730a1a835c9a25b 15647 
gr-iqbal_0.37.2-10_amd64.buildinfo
Files:
 b3e3bf876cd8008dd80fe89978ee30d5 2410 libs extra gr-iqbal_0.37.2-10.dsc
 5c4c9bd13bc6faea3bc2fd86fef9d83c 8524 libs extra 
gr-iqbal_0.37.2-10.debian.tar.xz
 ffef00bbc3beec03c81d30665b2199eb 15647 libs extra 
gr-iqbal_0.37.2-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAlm82dgACgkQUEHxiR9E
4JCCeA//VtPChVcK3BF8V2Abg/n89X3Miq/LaP2l+S6xmlb2neVUPEh1fGhXaBHz
OeHpT9A2/U7RUjSSAzR8CtUipCNpoy5IhKXu99jWHtRZZNvb1CIGreBdmu/9WpSf
L8puRqSoey56rvTuhUpkHANLNJxNMAzRt0aMFX2q8jB8IqjeTPOl1JEcXYeRC72S
tvFy8SttxL1x6ivNtT0TKfu5WOswVFDlAdaQEhmZwwXbSWmOz6fbkIyeMQ7Kj3Rj
ihEjgP/U2CpLWx2oqiWlnPbMQo9UY746T3mCNitr8JI+r4/mVpy+qa53kSGN5CPz

Bug#875930: arc-gui-clients: should it be removed from Debian?

2017-09-16 Thread Mattia Rizzolo

Source: arc-gui-clients
Version: 0.4.6-3
Severity: serious

Hi,

arc-gui-clients missed the last stable release (stretch) due to its RC
bugs, which have received no input from the maintainer for 9+ months.

Also considering the very low popcon, I believe this package in the
current state should be removed from Debian, and I'll have ftp-masters
to do so in the next weeks.


If you disagree with me, please take action to fix the outstanding bugs,
and close this one.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#875929: acetoneiso: should it be removed from Debian

2017-09-16 Thread Mattia Rizzolo

Source: acetoneiso
Version: 2.4-2
Severity: serious

Hi,

this package has long standing RC bugs (even if only recently rised to
RC level), without any input from the maintainer for years.
Also, it hasn't seen an upload in the last 3 years, that —whilst being
no indicator as is— feels kind of strange for an application aiming at
dealing with CD stuff.

I belive the best course of action would be to remove the package from
the archive, and I'll ask ftp-masters to do as such in the next few
weeks.

If you disagree with me, please take action to fix the outstanding bugs,
and closing this one.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: fixed 874068 in 1.13-0.2

2017-09-16 Thread Debian Bug Tracking System

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

> fixed 874068 1.13-0.2
Bug #874068 {Done: Sébastien Villemot } [src:ffcall] ABI 
breakage without shared library renaming
Marked as fixed in versions ffcall/1.13-0.2.
> thanks
Stopping processing here.

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

Processed: reassign 874068 to src:ffcall

2017-09-16 Thread Debian Bug Tracking System

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

> reassign 874068 src:ffcall 1.13-0.1
Bug #874068 {Done: Sébastien Villemot } [libffcall1] ABI 
breakage without shared library renaming
Bug reassigned from package 'libffcall1' to 'src:ffcall'.
No longer marked as found in versions 1.13-0.1.
No longer marked as fixed in versions ffcall/1.13-0.2.
Bug #874068 {Done: Sébastien Villemot } [src:ffcall] ABI 
breakage without shared library renaming
Marked as found in versions ffcall/1.13-0.1.
> thanks
Stopping processing here.

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

Bug#872496: marked as done (vdr-plugin-xineliboutput FTBFS with vdr 2.3.8)

2017-09-16 Thread Debian Bug Tracking System

Your message dated Sat, 16 Sep 2017 07:34:42 +
with message-id 
and subject line Bug#872496: fixed in vdr-plugin-xineliboutput 2.0.0-1
has caused the Debian Bug report #872496,
regarding vdr-plugin-xineliboutput FTBFS with vdr 2.3.8
to be marked as done.

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

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


-- 
872496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-xineliboutput
Version: 1.1.0+cvs20150907-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-xineliboutput.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DVIDEODIR='"/var/lib/video"' 
-DXINELIBOUTPUT_VERSION='"2.0.0-cvs"' -Wall  -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -o 
xineliboutput.o xineliboutput.c
xineliboutput.c:112:1: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 "   (default "LISTEN_PORT_S")\n"
 ^
In file included from xineliboutput.c:35:0:
device.h:126:13: error: 'eVideoSystem' does not name a type
 virtual eVideoSystem GetVideoSystem(void);
 ^~~~
Makefile:241: recipe for target 'xineliboutput.o' failed
make[2]: *** [xineliboutput.o] Error 1
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-xineliboutput
Source-Version: 2.0.0-1

We believe that the bug you reported is fixed in the latest version of
vdr-plugin-xineliboutput, 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.
Tobias Grimm  (supplier of updated vdr-plugin-xineliboutput 
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, 16 Sep 2017 08:54:16 +0200
Source: vdr-plugin-xineliboutput
Binary: vdr-plugin-xineliboutput vdr-plugin-xineliboutput-dbg 
libxineliboutput-fbfe libxineliboutput-fbfe-dbg libxineliboutput-sxfe 
libxineliboutput-sxfe-dbg xineliboutput-fbfe xineliboutput-fbfe-dbg 
xineliboutput-sxfe xineliboutput-sxfe-dbg libxine2-xvdr libxine2-xvdr-dbg
Architecture: source amd64
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Tobias Grimm 
Description:
 libxine2-xvdr - Xine input plugin for vdr-plugin-xineliboutput streams
 libxine2-xvdr-dbg - Xine input plugin for vdr-plugin-xineliboutput streams
 libxineliboutput-fbfe - Local framebuffer frontend for the xineliboutput plugin
 libxineliboutput-fbfe-dbg - Local framebuffer frontend for the xineliboutput 
plugin
 libxineliboutput-sxfe - Local X-Server frontend for the xineliboutput plugin
 libxineliboutput-sxfe-dbg - Local X-Server frontend for the xineliboutput 
plugin
 vdr-plugin-xineliboutput - VDR plugin for Xine based sofdevice frontends
 vdr-plugin-xineliboutput-dbg - VDR plugin for Xine based sofdevice frontends
 xineliboutput-fbfe - Remote Framebuffer frontend for vdr-plugin-xineliboutput
 xineliboutput-fbfe-dbg - Remote Framebuffer frontend for 
vdr-plugin-xineliboutput
 xineliboutput-sxfe - Remote X-Server frontend for vdr-plugin-xineliboutput
 xineliboutput-sxfe-dbg - Remote X-Server frontend for vdr-plugin-xineliboutput
Closes: 872496
Changes:
 vdr-plugin-xineliboutput (2.0.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #872496)

Bug#816804: [Pkg-crosswire-devel] Bug#816804: Qt5 version released upstream

2017-09-16 Thread Teus Benschop

I am working on this, time permitting, plus circumstances permitting.

On Sat, 16 Sep 2017 at 07:09 Scott Kitterman  wrote:

> This and #874831 would be resolved if someone would package the new
> upstream
> release.
>
> Scott K
>
> ___
> Pkg-crosswire-devel mailing list
> pkg-crosswire-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
>

73 matches

Mail list logo