date:20171015

Bug#878674: [Pkg-javascript-devel] Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-15 Thread Pirate Praveen

On ഞായര്‍ 15 ഒക്ടോബര്‍ 2017 11:39 വൈകു, Jérémy Lal wrote:
> Do you know if any dependency is a c++ addon ?

These are the direct dependencies,

Depends:
 ${misc:Depends}
 , nodejs
 , node-acorn (>= 5.0~)
 , node-acorn-dynamic-import (>= 2.0~)
 , node-ajv (>= 5.0~)
 , node-ajv-keywords (>= 2.0~)
 , node-async (>= 0.8~)
 , node-enhanced-resolve (>= 3.4~)
 , node-escope
 , node-interpret (>= 1.0~)
 , node-json-loader (>= 0.5.4~)
 , node-json5 (>= 0.5~)
 , node-loader-runner (>= 2.3~)
 , node-loader-utils (>= 0.2~)
 , node-memory-fs (>= 0.4.1~)
 , node-mkdirp (>= 0.5~)
 , node-libs-browser (>= 2.0~)
 , node-source-map (>= 0.5.3~)
 , node-supports-color (>= 4.2.1~)
 , node-tapable (>= 0.2.7~)
 , node-uglifyjs-webpack-plugin
 , node-watchpack (>= 1.3.1~)
 , node-webpack-sources (>= 1.0.1~)
 , node-yargs (>= 6.0~)
 , node-lodash-packages
 , node-lodash

I don't think any of them is a C++ addon, probably one of their
dependencies.



signature.asc
Description: OpenPGP digital signature

Bug#790158: Upstream comment

2017-10-15 Thread James Cameron

Upstream could bring python-rsvg source into the code base; would that
be okay?

Porting from python-rsvg to gir1.2-rsvg-2.0 would also require porting
to GTK+ 2 GObject introspection.  This would break compatibility with
downloaded Sugar activities.

-- 
James Cameron
http://quozl.netrek.org/

Bug#790156: v44 already moved from python-rsvg to gir1.2-rsvg-2.0

2017-10-15 Thread James Cameron

New upstream release v44 fixed this, and was packaged, with gir-deps
of rsvg-2.0, so next step is to remove the python-rsvg dependency in
debian/rules.

-- 
James Cameron
http://quozl.netrek.org/

Processed: tagging 876551

2017-10-15 Thread Debian Bug Tracking System

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

> tags 876551 + pending
Bug #876551 [src:e2fsprogs] dh_installdocs: Unknown package libblkid1-udeb 
given via -N/--no-package
Bug #876672 [src:e2fsprogs] e2fsprogs: FTBFS: Unknown package libblkid1-udeb 
given via -N/--no-package
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876584: marked as done (libinfinity FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Mon, 16 Oct 2017 04:00:25 +
with message-id 
and subject line Bug#876584: fixed in libinfinity 0.7.1-1
has caused the Debian Bug report #876584,
regarding libinfinity FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


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

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

...
touch scan-build.stamp
gtkdoc-mktmpl --module=libinfinity-0.6 
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:736: recipe for target 'tmpl-build.stamp' failed
make[5]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: libinfinity
Source-Version: 0.7.1-1

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated libinfinity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Sep 2017 15:17:29 +0200
Source: libinfinity
Binary: libinfinity-0.7-dev libinfinity-0.7-doc libinfinity-0.7-dbg 
libinfinity-0.7-0 libinfgtk-0.7-0 infinoted
Architecture: source amd64 all
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern 
Changed-By: Philipp Kern 
Description:
 infinoted  - dedicated server for infinote-based collaborative editing
 libinfgtk-0.7-0 - infinote-based collaborative editing (Gtk widgets)
 libinfinity-0.7-0 - infinote-based collaborative editing
 libinfinity-0.7-dbg - infinote-based collaborative editing - debugging symbols
 libinfinity-0.7-dev - infinote-based collaborative editing - development files
 libinfinity-0.7-doc - infinote-based collaborative editing - documentation
Closes: 876584
Changes:
 libinfinity (0.7.1-1) unstable; urgency=medium
 .
   * New upstream release
 - Drop additional patches
 - Includes new gtk-doc.make (Closes: #876584)
Checksums-Sha1:
 852f7cfd453507d52a63d24dcec62853e61f9ec7 2215 libinfinity_0.7.1-1.dsc
 a59d9f18c6af3cf4a439b99ad5318d33e28a2712 2054876 libinfinity_0.7.1.orig.tar.gz
 141070894398b8efd8ed2619c648ca499e4ead26 2637 libinfinity_0.7.1.orig.tar.gz.asc
 ccd20952f5800399379077e90e02d085ce4e0b98 15308 
libinfinity_0.7.1-1.debian.tar.xz
 5cfec2d0fe99e7abec8b402c6a8729a1c2bebeac 200850 infinoted_0.7.1-1_amd64.deb
 5880a0b772e6e5bfdfe84aa9ce4bc87b33e2caf3 236702 
libinfgtk-0.7-0_0.7.1-1_amd64.deb
 75d84ac537ea0d7e7611a4af4e39862ce257a0ad 445964 
libinfinity-0.7-0_0.7.1-1_amd64.deb
 67d5444f5a1a847a5c088f22063c7a5d8ecad830 1927404 
libinfinity-0.7-dbg_0.7.1-1_amd64.deb
 396945723f17a2e8afa67302ec70f779459af9fa 634912 
libinfinity-0.7-dev_0.7.1-1_amd64.deb
 65d6f2362456e775457d586513b024510a78bb2e 388112 
libinfinity-0.7-doc_0.7.1-1_all.deb
 f4205764ca884f0d7ee2c0c9015ee65537c37404 15475 
libinfinity_0.7.1-1_amd64.buildinfo
Checksums-Sha256:
 0a4b454f09ef6ed6d7464e22d95a503933785e65abe5cfbc4ec19c68d787e714 2215 
libinfinity_0.7.1-1.dsc
 626ee0841bfe24f471580cd17d906dd83b973cf4f10019574adfdfc5327482cb 2054876 
libinfinity_0.7.1.orig.tar.gz
 3ab72ff782104d3667d2b18a366f42d98c2f9d358b114d3ee6001c4c94d2b45e 2637 
libinfinity_0.7.1.orig.tar.gz.asc
 29f0473aaeaf391f1186cea57c0ace12d9f1d2ffa770404fc412d016060e76c7 15308 
libinfinity_0.7.1-1.debian.tar.xz
 fc98ad5a1e0f16c29e7d520fc285706eca6e225cc3cac26ca126ecc63f280825 200850 
infinoted_0.7.1-1_amd64.deb
 f03b3d14215189755ba641ef2d53f6336bf9c22503aca9ecc277372da3800557 236702 
libinfgtk-0.7-0_0.7.1-1_amd64.deb
 26998e85c5a1a2fa4e5e8248a2895123665d4b99da2b1c941a82f9a75394bdda 445964 
libinfinity-0.7-0_0.7.1-1_amd64.deb
 56c525183b4086fd79015569458ba19d0a2608ffa85523347cfe4f4aafb0c318 1927404 
libinfinity-0.7-dbg_0.7.1-1_amd64.deb
 f2e2e754026ef44d685880aa14fc28f82f7176b8f4ac7d99467468dc69f37bc0 634912

Bug#878339: marked as done (golang-github-nbutton23-zxcvbn-go-dev 0.0~git20170830.0.f4cd9f5-1 causes FTBFS in golang-github-chzyer-readline)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Mon, 16 Oct 2017 02:50:26 +
with message-id 
and subject line Bug#878339: fixed in golang-github-nbutton23-zxcvbn-go 
0.0~git20170830.0.f4cd9f5-2
has caused the Debian Bug report #878339,
regarding golang-github-nbutton23-zxcvbn-go-dev 0.0~git20170830.0.f4cd9f5-1 
causes FTBFS in golang-github-chzyer-readline
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.)


-- 
878339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-nbutton23-zxcvbn-go-dev
Version: 0.0~git20170830.0.f4cd9f5-1
Severity: serious
Control: affects -1 src:golang-github-chzyer-readline

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-chzyer-readline.html

...
# github.com/nbutton23/zxcvbn-go
src/github.com/nbutton23/zxcvbn-go/transaction.go:4:10: fatal error: 
security/pam_appl.h: No such file or directory
 //#include 
  ^
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: golang-github-nbutton23-zxcvbn-go
Source-Version: 0.0~git20170830.0.f4cd9f5-2

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

Debian distribution maintenance software
pp.
Michael Lustfield  (supplier of updated 
golang-github-nbutton23-zxcvbn-go package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Oct 2017 21:13:53 -0500
Source: golang-github-nbutton23-zxcvbn-go
Binary: golang-github-nbutton23-zxcvbn-go-dev
Architecture: source
Version: 0.0~git20170830.0.f4cd9f5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Michael Lustfield 
Description:
 golang-github-nbutton23-zxcvbn-go-dev - Strong password generator in Go
Closes: 878339
Changes:
 golang-github-nbutton23-zxcvbn-go (0.0~git20170830.0.f4cd9f5-2) unstable; 
urgency=medium
 .
   * Include new build dep in -dev pkg. (Closes: #878339)
Checksums-Sha1:
 494010dd07a03b3bf5e9e1d7eb8f18bdf903cc03 2541 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2.dsc
 9ffa6695b57a7066f124d6c21ab95c644118c7c5 2216 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2.debian.tar.xz
 6d959b92e64680fb191b0b1eb9ea8e86be87908b 6201 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2_amd64.buildinfo
Checksums-Sha256:
 7894de8d843aaef5384401e50c3e4590f96bedf2a8057a9ca528c649b334eb06 2541 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2.dsc
 745780c36de783f1e0903351fb3ba9debe2c93170d5f97559285d6aef350ba46 2216 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2.debian.tar.xz
 2c34fc02ac450456d5583c5d92365115f58653d2937a604a2cbe38d93a20a919 6201 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2_amd64.buildinfo
Files:
 694d70343ca682744c67d1b0e39250e3 2541 devel extra 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2.dsc
 88cbff39934d0da174ebc9e3e1285b11 2216 devel extra 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2.debian.tar.xz
 ccb998ea0872ac7cce1c7e4822f2bcbd 6201 devel extra 
golang-github-nbutton23-zxcvbn-go_0.0~git20170830.0.f4cd9f5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEBs1j101ZjEpH5CyWA6iJGnZa0IUFAlnkFlAWHG1pY2hhZWxA
bHVzdGZpZWxkLm5ldAAKCRADqIkadlrQhceREACFwLjB4HQebFkxKwxExZItyYEu
8UQqHBSswT39HMkJnyeHk6stqDFT/2aGbf9mfXnZ6/N+N+eimsJOixicAszNBErn
Px1ZyMKpADa0nCAEUq+giYM6ZS6J/e7nb3+sU1XtGmU2MI/6pSQXoaK+57Kc3MsX
yUMbd2g2n2aNPpI+sQaEAxHSwWFi6KmC90xYaM+PqIL67Gpc4Ytl8lsoXFtte8+4
djPfjPk2DyyL5aXNMQ3Xxt69suiEjJzGnyYhCBWKJ9YvI1V54k2vehdvbm9D9Lj0
4IPGgyzGUPWDFlcd4+H/huDntHm9T/+JIfX66RoIZgvrRBUc0zXx8knmaTcDXRqK
QBVrJiByD+k+vekqlktsWyeVop/GRCD8JdnB/VDDPzNmDwjDjiOj1a/OLjX/0fbj
Xj/liGWidzQ2k1HrPmm/pz2davQR0vmuiL5zFovJHOXvIT2H46V/bJOJwphIzQJE
bOJ2zmoKJoLAH2Ya8ofMpEHZiu98PxmQ2TF84Tlzg+OMPRAToAx7EFHkM6Ch22Bk

Processed: Not a problem in stretch

2017-10-15 Thread Debian Bug Tracking System

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

> tags 822590 - stretch
Bug #822590 [src:liblunar] liblunar: depends on python-gtksourceview2 which is 
deprecated
Removed tag(s) stretch.
> tags 822586 - stretch
Bug #822586 [src:cherrytree] cherrytree: depends on python-gtksourceview2 which 
is deprecated
Removed tag(s) stretch.
> tags 790154 - stretch
Bug #790154 [src:dissy] dissy: depends on python-rsvg which is deprecated
Removed tag(s) stretch.
> tags 822588 - stretch
Bug #822588 [src:dreampie] dreampie: depends on python-gtksourceview2 which is 
deprecated
Removed tag(s) stretch.
> tags 790146 - stretch
Bug #790146 [src:gdevilspie] gdevilspie: depends on python-wnck which is 
deprecated
Removed tag(s) stretch.
> tags 822585 - stretch
Bug #822585 [src:gvrng] gvrng: depends on python-gtksourceview2 which is 
deprecated
Removed tag(s) stretch.
> tags 790147 - stretch
Bug #790147 [src:hamster-applet] hamster-applet: depends on python-wnck which 
is deprecated
Removed tag(s) stretch.
> tags 822589 - stretch
Bug #822589 [src:kabikaboo] kabikaboo: depends on python-gtksourceview2 which 
is deprecated
Removed tag(s) stretch.
> tags 878698 buster sid
Bug #878698 [src:pygtksourceview] pygtksourceview: keep out of testing
Added tag(s) buster and sid.
> tags 790145 - stretch
Bug #790145 [src:screenlets] screenlets: depends on python-wnck which is 
deprecated
Removed tag(s) stretch.
> tags 790152 - stretch
Bug #790152 [src:screenlets] screenlets: depends on python-rsvg which is 
deprecated
Removed tag(s) stretch.
> tags 790156 - stretch
Bug #790156 [src:sugar-calculate-activity] sugar-calculate-activity: depends on 
python-rsvg which is deprecated
Removed tag(s) stretch.
> tags 790158 - stretch
Bug #790158 [src:sugar-toolkit] sugar-toolkit: depends on python-rsvg which is 
deprecated
Removed tag(s) stretch.
> tags 790162 - stretch
Bug #790162 [src:winswitch] winswitch: depends on python-rsvg which is 
deprecated
Removed tag(s) stretch.
> tags 790149 - stretch
Bug #790149 [src:xword] xword: depends on python-wnck which is deprecated
Removed tag(s) stretch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
790145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790145
790146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790146
790147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790147
790149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790149
790152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790152
790154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790154
790156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790156
790158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790158
790162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790162
822585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822585
822586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822586
822588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822588
822589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822589
822590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822590
878698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#822590 closed by Emilio Pozuelo Monfort <po...@debian.org> (Re: liblunar: depends on python-gtksourceview2 which is deprecated)

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #822590 {Done: Emilio Pozuelo Monfort } [src:liblunar] 
liblunar: depends on python-gtksourceview2 which is deprecated
Bug reopened
Ignoring request to alter fixed versions of bug #822590 to the same values 
previously set
> severity -1 serious
Bug #822590 [src:liblunar] liblunar: depends on python-gtksourceview2 which is 
deprecated
Severity set to 'serious' from 'important'

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

Bug#878584: [Pkg-e-devel] Bug#878584: [libevas-dev] Missing dependency for libecore-dev

2017-10-15 Thread Ross Vandegrift

On Sun, Oct 15, 2017 at 01:20:05PM +0200, Andreas Metzler wrote:
> Ross, could you apply and push the attached patch?

Hmm, two concerns about this solution:

1) lintian finds a circular dependency
  libecore-dev libector-dev libeet-dev libeeze-dev libeina-dev libemile-dev 
libevas-dev
I don't know for sure that it's a problem here, but in the past the team
has worked hard to avoid cycles.

2) Upstream doesn't really support builds against part of EFL (and
hasn't since the library merge before 1.8).  I think we generally ought
to avoid supporting scenarios that upstream doesn't.

Instead, what if all of the -dev packages were merged into
libefl-all-dev?  Sample patch is attached.  It's mildly tested:
enlightenment from experimental builds, and the resulting Depends look
correct.  What do you think?

I've pushed the accumulated fixes to:
https://github.com/rvandegrift/efl/tree/debian/experimental
I've added this patch at:
https://github.com/rvandegrift/efl/tree/debian/experimental-next

Thanks,
Ross


merge-libe-dev-pkgs.diff.gz
Description: application/gzip

Processed: Re: txaws: depends on python-gnomekeyring which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790141 [src:txaws] txaws: depends on python-gnomekeyring which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: screenlets: depends on python-wnck which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790145 [src:screenlets] screenlets: depends on python-wnck which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: screenlets: depends on python-rsvg which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790152 [src:screenlets] screenlets: depends on python-rsvg which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: winswitch: depends on python-rsvg which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790162 [src:winswitch] winswitch: depends on python-rsvg which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: xword: depends on python-wnck which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790149 [src:xword] xword: depends on python-wnck which is deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: gdevilspie: depends on python-wnck which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790146 [src:gdevilspie] gdevilspie: depends on python-wnck which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: hamster-applet: depends on python-wnck which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790147 [src:hamster-applet] hamster-applet: depends on python-wnck which 
is deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: dissy: depends on python-rsvg which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790154 [src:dissy] dissy: depends on python-rsvg which is deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: sugar-calculate-activity: depends on python-rsvg which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790156 [src:sugar-calculate-activity] sugar-calculate-activity: depends on 
python-rsvg which is deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: sugar-toolkit: depends on python-rsvg which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #790158 [src:sugar-toolkit] sugar-toolkit: depends on python-rsvg which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: kabikaboo: depends on python-gtksourceview2 which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #822589 [src:kabikaboo] kabikaboo: depends on python-gtksourceview2 which 
is deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: cherrytree: depends on python-gtksourceview2 which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #822586 [src:cherrytree] cherrytree: depends on python-gtksourceview2 which 
is deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: dreampie: depends on python-gtksourceview2 which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #822588 [src:dreampie] dreampie: depends on python-gtksourceview2 which is 
deprecated
Severity set to 'serious' from 'important'

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

Processed: Re: gvrng: depends on python-gtksourceview2 which is deprecated

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #822585 [src:gvrng] gvrng: depends on python-gtksourceview2 which is 
deprecated
Severity set to 'serious' from 'important'

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

Bug#878698: pygtksourceview: keep out of testing

2017-10-15 Thread Emilio Pozuelo Monfort

Source: pygtksourceview
Severity: serious

It is high time that we remove pygtksourceview from testing. It's
completely dead upstream in favor of the gobject-introspection
bindings, gir1.2-gtksource-3.0. Remaining reverse dependencies
should be ported to use that.

Emilio

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

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

Bug#878631: marked as done (flightgear build depends on libsimgear-dev (<= 1:2017.2.999) but 1:2017.3.1+dfsg-1 is to be installed)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 20:51:28 +
with message-id 
and subject line Bug#878631: fixed in flightgear 1:2017.3.1+dfsg-1
has caused the Debian Bug report #878631,
regarding flightgear build depends on libsimgear-dev (<= 1:2017.2.999) but 
1:2017.3.1+dfsg-1 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.)


-- 
878631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flightgear
Version: 1:2017.2.1+dfsg-4
Severity: serious

The following packages have unmet dependencies:
 builddeps:flightgear : Depends: libsimgear-dev (<= 1:2017.2.999) but 
1:2017.3.1+dfsg-1 is to be installed
--- End Message ---
--- Begin Message ---
Source: flightgear
Source-Version: 1:2017.3.1+dfsg-1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated flightgear package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Oct 2017 21:37:06 +0200
Source: flightgear
Binary: flightgear
Architecture: source
Version: 1:2017.3.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FlightGear Crew 
Changed-By: Dr. Tobias Quathamer 
Description:
 flightgear - Flight Gear Flight Simulator
Closes: 878631
Changes:
 flightgear (1:2017.3.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 2017.3.1+dfsg. Closes: #878631
 - Refresh patches
 - Remove patch init-allowed-paths-earlier, applied upstream
 - Remove patch prevent-arbitrary-file-writes, applied upstream
   * Update Standards-Version to 4.1.1
 - Use Priority: optional
 - Use HTTPS for URL in d/copyright
   * Fix typo in Vcs-Browser URL
   * Update dependencies on flightgear-data and simgear-dev
   * Use debhelper v10
Checksums-Sha1:
 14afb711d7e113c0534c7c213f76522a1d7da1ac 2727 flightgear_2017.3.1+dfsg-1.dsc
 8192bddcfe8c7958f46d834e01dc5367e5eaad56 6536836 
flightgear_2017.3.1+dfsg.orig.tar.bz2
 97b597330c54f36a31755622e7a48be4c387e968 27176 
flightgear_2017.3.1+dfsg-1.debian.tar.xz
 b89a82d917f8ac59aea448b70e92a1681036779d 17998 
flightgear_2017.3.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 da88f4b5a9dba5a85ae1c34286c10ee6e8d7d54f05391c3088401a7eccfa613e 2727 
flightgear_2017.3.1+dfsg-1.dsc
 18ddb5243246438b05525f85b3235dccbf710ba28faeee11249d8c5fed126a71 6536836 
flightgear_2017.3.1+dfsg.orig.tar.bz2
 b2a2cd9670001b5070e9338724cc4b26aba0b1f59712bad5839e5e87b51d937b 27176 
flightgear_2017.3.1+dfsg-1.debian.tar.xz
 1de5cf1eba7e9e717adda0c39d762e2f4b7b11f79241b3bbc6c4998c64783a8d 17998 
flightgear_2017.3.1+dfsg-1_amd64.buildinfo
Files:
 076d0cffa46a31155d3a561660df1884 2727 games optional 
flightgear_2017.3.1+dfsg-1.dsc
 d926e9e1632f63b5addbb62d52a5a326 6536836 games optional 
flightgear_2017.3.1+dfsg.orig.tar.bz2
 bdcd27eb88fbbc26accae9f252f097ef 27176 games optional 
flightgear_2017.3.1+dfsg-1.debian.tar.xz
 3b3a08a0cb14d82d6328f3552f59168b 17998 games optional 
flightgear_2017.3.1+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlnjvIoACgkQEwLx8Dbr
6xkX1g//YZTB/YFCgyjHitprrwhJ74x3PM72aIo7UIKIbAVf8b7mndMc+xYlvkYV
UCV0a7w0NGwko+vJS7suESbvgTxRZGz8bLX3SnjdJLazO9aK+vMYneWREkwmI2ey
B4bVb19VVOjOihFn8sN2lApixNMvY1eQadwLztFYgrXAfyQgmVQ58YmFO20FsPq6
1PGSFXnYNi06VN99xrEM5nWxVxC4HtRfvwmX+24dH+SsQqT/3bX+v24i7oWirv2g
6zgrLWHS30r7f7tfEGZKTbM8ph8kPZjfyhK7YP9BDhzpwwqUKNhz4l4ixKCznKZT
42t9skZw3GvkDlsoinB09JGQNEUZ7O+FPw9JMO2CWBvFDkBBeuUlBzIt4L6yHsA6
ZKH0njG9+WHm4M6YXeH8TfnRWeJhI2W/O3T+RgUiajVCALiII+NYf5UMZRufskGL
N5A8qlW940Hlp4+bPpQ+8RDFYU9Fq1F33Hbe+gIoRD77xtwT56D3EmO1lZIHqlLa
EnpkJT8RtMBvCc5CzaIn4w0ckp7956rLKWhPJ20eCJ/N18qMDoGBMq2Ym+Q4suXW
laMhZ7jeAFMRYgA85gWjh8VtIwCvYl2ML0C4wjJIDJFckaJws8XBscpPHkLSxSvG
CM26tSM+4Uh9egNFr6YHegZp2RkWaVmls6OIjlQna2OroRbgPFc=
=A9rQ
-END PGP SIGNATURE End Message ---

Bug#867588: buildbot: application fails at runtime requiring sqlalchemy-migrate==0.7.2

2017-10-15 Thread Charles Lepple

So far, I have not observed any failures after removing the offending
lines ("sqlalchemy >= 0.6, <= 0.7.10" and "sqlalchemy-migrate==0.7.2")
from
/usr/lib/python2.7/dist-packages/buildbot-0.8.12.egg-info/requires.txt

Tested with buildbot 0.8.12-3.2 on stretch, with python-sqlalchemy
1.0.15+ds1-1 and python-migrate 0.10.0-7. Also installed "python-mock" and
ran the Buildbot tests with trial, though I am not sure how much of the
migration code gets exercised in the tests.

This commit to upstream seems to indicate that the newer versions of
sqlalchemy and sqlalchemy-migrate included in Debian should be compatible
with each other:

https://github.com/buildbot/buildbot/commit/222361a0e061291c9ba7fd7e6a660c7356ecd218

"Accept sqlalchemy-migrate versions 0.8 and up as compatible with
sqlalchemy version 0.8 and up."

Bug#878695: xul-ext-noscript: no longer works on existing profiles since last update

2017-10-15 Thread Christoph Anton Mitterer

Package: xul-ext-noscript
Version: 5.1.2-1
Severity: grave
Tags: security
Justification: renders package unusable

Hi.


Since the upgrade to 5.1.2-1 the plugin, while still appearing in the
add-ons list (and marked enabled there), no longer seems to work.
It's "icons/menus/etc" disappeared and cannot be added back again.

It does seem to appear on fresh profiles and it works again with the existing
profiles when downgrading to 5.0.10-1

Any ideas?

tag security, since all scripts seem to be now allowed.

Cheers,
Chris.

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

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

Versions of packages xul-ext-noscript depends on:
ii  firefox56.0-2
ii  iceweasel  100

xul-ext-noscript recommends no packages.

xul-ext-noscript suggests no packages.

-- Configuration Files:
/etc/iceweasel/searchplugins/common/opensearch_html.xml [Errno 2] No such file 
or directory: '/etc/iceweasel/searchplugins/common/opensearch_html.xml'

-- no debconf information

Processed: Re: Bug#876739: pyfai FTBFS: help2man: can't get `--help' info from /tmp/check_calib_0hk8odnh

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #876739 {Done: PICCA Frederic-Emmanuel 
} [src:pyfai] pyfai FTBFS: 
help2man: can't get `--help' info from /tmp/check_calib_0hk8odnh
Bug reopened
Ignoring request to alter fixed versions of bug #876739 to the same values 
previously set

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

Bug#876739: pyfai FTBFS: help2man: can't get `--help' info from /tmp/check_calib_0hk8odnh

2017-10-15 Thread Adrian Bunk

Control: reopen -1

On Sun, Oct 15, 2017 at 06:23:35AM +, PICCA Frederic-Emmanuel wrote:
> This problem was due to this  
> 
> python-fabio (0.5.0+dfsg-2) unstable; urgency=medium
> 
>   * d/control
> - python-qt4 -> python3-pyqt4-dbg (Closes: #876288)
> 
> Now that python-fabio was solved, it is ok to close this bug

Still FTBFS with python-fabio 0.5.0+dfsg-2:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyfai.html

> thanks
> 
> Frederic

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-15 Thread Jérémy Lal

2017-10-15 18:36 GMT+02:00 Pirate Praveen :

> package: nodejs
> version: 6.11.4~dfsg-1
> severity: serious
>
> I have noticed this failure when building multiple node-d3-* packages
> (node-d3-zoom for example) and also installing gitlab 9.5 using webpack.
>
> When building the same node-d3-zoom with nodejs
> 7.10.1-2nodesource1~stretch1 the build passed. Tried both in local
> installation and using sbuild.
>
> Also tested the same on my laptop and on a vm
>
> babeljs src -d lib
> src/constant.js -> lib/constant.js
> src/event.js -> lib/event.js
> src/noevent.js -> lib/noevent.js
> src/transform.js -> lib/transform.js
> src/zoom.js -> lib/zoom.js
> babeljs index.js -d lib
> index.js -> lib/index.js
> sed -i 's/.\/src/./' lib/index.js
> webpack --config debian/webpack.config.js index.js build/d3-zoom.js
> --target=web --output-library=d3-zoom --output-library-target=umd
> --module-bind 'js=babel-loader'
> debian/rules:12: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Segmentation fault
> make[1]: Leaving directory '/<>'
> debian/rules:9: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
>
> Since babel and other dependencies are still in NEW, I have setup a repo
> for packages still in NEW.
>
> I have /usr/local/bin/sbuild-babel,
> sbuild -A -s -d unstable --extra-repository='deb
> https://people.debian.org/~praveen/babel sid main'
> --extra-repository-key=/home/pravi/forge/debian/babel/repo/praveen.key.asc
> $@
>
> With nodejs from nodesource.com, the build passes, both locally and in
> sbuild. For sbuild I have to pass --extra-package option and in
> debian/rules, I have to add export NODE_PATH=/usr/lib/nodejs
>
> node-d3-geo, node-d3-scale are other packages that segfaults.
>
> All node-d3-* packages are in pkg-javascript team repo in alioth.
>
>
Do you know if any dependency is a c++ addon ?

Jérémy

Bug#871102: marked as done (javamail: FTBFS: ERROR Failed to execute goal [32morg.apache.maven.plugins:maven-dependency-plugin:2.8:unpack[m [1m(get-binaries)[m on project [36mmailapi[m: [1;31mE

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 20:23:23 +0200
with message-id <33d344ec-109a-6a13-7f42-f37ff9d92...@debian.org>
and subject line Re: javamail: FTBFS: ERROR Failed to execute goal 
[32morg.apache.maven.plugins:maven-dependency-plugin:2.8:unpack [m 
[1m(get-binaries) [m on project [36mmailapi [m: [1;31mExecution get-binaries of 
goal org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack: 
org/codehaus/plexus/util/MatchPatterns [m
has caused the Debian Bug report #871102,
regarding javamail: FTBFS: ERROR Failed to execute goal 
[32morg.apache.maven.plugins:maven-dependency-plugin:2.8:unpack[m 
[1m(get-binaries)[m on project [36mmailapi[m: [1;31mExecution get-binaries 
of goal org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack: 
org/codehaus/plexus/util/MatchPatterns[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.)


-- 
871102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: javamail
Version: 1.5.6-2
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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibmail-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] JavaMail API distribution
> [[1;34mINFO[m] JavaMail API
> [[1;34mINFO[m] JavaMail API (no providers)
> [[1;34mINFO[m] JavaMail API jar
> [[1;34mINFO[m] JavaMail API smtp provider
> [[1;34mINFO[m] JavaMail API imap provider
> [[1;34mINFO[m] JavaMail API Gmail IMAP provider
> [[1;34mINFO[m] JavaMail API pop3 provider
> [[1;34mINFO[m] JavaMail API dsn support
> [[1;34mINFO[m] JavaMail API logging handler
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.8: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1 or one of its 
> dependencies could not be resolved: Cannot access

Bug#869001: marked as done (maven-site-plugin: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tool

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 20:05:15 +0200
with message-id <165a5828-8f39-67cd-f05d-3ca652950...@debian.org>
and subject line Re: maven-site-plugin: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
has caused the Debian Bug report #869001,
regarding maven-site-plugin: FTBFS: dh_auto_test: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
to be marked as done.

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

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


-- 
869001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-site-plugin
Version: 2.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-site-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Maven Site Plugin 2.2[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-site-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 25 resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-site-plugin[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;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 18 source files to /<>/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
>

Bug#869021: marked as done (jetty9: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 19:54:03 +0200
with message-id <4170cb55-c209-3eca-9cc8-0cc812acc...@debian.org>
and subject line Re: jetty9: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869021,
regarding jetty9: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
to be marked as done.

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

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


-- 
869021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jetty9
Version: 9.2.22-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --with javahelper
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibjetty9-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty:jetty-project:pom:9.2.14.v20151106, use --no-parent option 
> to resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty.rhttp:jetty-rhttp-project:pom:9.2.14.v20151106, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty.rhttp:jetty-rhttp-project:pom:9.2.14.v20151106, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty.rhttp:jetty-rhttp-project:pom:9.2.14.v20151106, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
>jh_linkjars
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-util:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 43, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-jmx:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 43, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-io:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 49, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-http:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 49, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-continuation:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 38, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for

Bug#869002: marked as done (conversant-disruptor does not install the jar file)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 17:48:45 +
with message-id 
and subject line Bug#869002: fixed in conversant-disruptor 1.2.10-2
has caused the Debian Bug report #869002,
regarding conversant-disruptor does not install the jar file
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.)


-- 
869002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache-log4j2
Version: 2.8.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -pliblog4j2-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Apache Log4j 2
> [[1;34mINFO[m] Apache Log4j API
> [[1;34mINFO[m] Apache Log4j Core
> [[1;34mINFO[m] Apache Log4j 1.x Compatibility API
> [[1;34mINFO[m] Apache Log4j to SLF4J Adapter
> [[1;34mINFO[m] Apache Log4j Commons Logging Bridge
> [[1;34mINFO[m] Apache Log4j BOM
> [[1;34mINFO[m] Apache Log4j NoSQL
> [[1;34mINFO[m] Apache Log4j Web
> [[1;34mINFO[m] Apache Log4j JUL Adapter
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-doap-plugin:jar:1.2 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-doap-plugin:1.2: Plugin 
> org.apache.maven.plugins:maven-doap-plugin:1.2 or one of its dependencies 
> could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact org.apache.maven.plugins:maven-doap-plugin:jar:1.2 has 
> not been downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 
> has not been downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.8: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies 
> could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 
> has not been downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1: Plugin 
>

Bug#869017: marked as done (powermock: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 19:42:53 +0200
with message-id 
and subject line Re: powermock: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869017,
regarding powermock: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
to be marked as done.

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

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


-- 
869017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: powermock
Version: 1.6.6-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibpowermock-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] powermock
> [[1;34mINFO[m] powermock-reflect
> [[1;34mINFO[m] powermock-core
> [[1;34mINFO[m] powermock-api
> [[1;34mINFO[m] powermock-api-support
> [[1;34mINFO[m] powermock-api-easymock
> [[1;34mINFO[m] powermock-api-mockito-common
> [[1;34mINFO[m] powermock-api-mockito
> [[1;34mINFO[m] powermock-modules
> [[1;34mINFO[m] powermock-module-junit4-common
> [[1;34mINFO[m] powermock-module-junit4
> [[1;34mINFO[m] powermock-classloading-base
> [[1;34mINFO[m] powermock-module-junit4-rule
> [[1;34mINFO[m] powermock-module-javaagent
> [[1;34mINFO[m] powermock-module-junit4-rule-agent
> [[1;34mINFO[m] powermock-module-testng-common
> [[1;34mINFO[m] powermock-module-testng
> [[1;34mINFO[m] powermock-module-testng-agent
> [[1;34mINFO[m] powermock-modules-impl
> [[1;34mINFO[m] powermock-classloading-module
> [[1;34mINFO[m] powermock-classloading-objenesis
> [[1;34mINFO[m] powermock-classloading-xstream
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding powermock 1.6.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-bundle-plugin:2.5.4:manifest[m 
> [1m(bundle-manifest)[m @ [36mpowermock[0;1m ---[m
> [[1;33mWARNING[m] Ignoring project type pom - supportedProjectTypes = [jar, 
> bundle]
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding powermock-reflect 1.6.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mpowermock-reflect[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/reflect/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mpowermock-reflect[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
>

Processed: Pending fixes for bugs in the conversant-disruptor package

2017-10-15 Thread Debian Bug Tracking System

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

> tag 869002 + pending
Bug #869002 [src:conversant-disruptor] conversant-disruptor does not install 
the jar file
Ignoring request to alter tags of bug #869002 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#869002: Pending fixes for bugs in the conversant-disruptor package

2017-10-15 Thread pkg-java-maintainers

tag 869002 + pending
thanks

Some bugs in the conversant-disruptor package are closed in revision
2f26f401f9bb46eede68346a1dc021d8f598b9e7 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/conversant-disruptor.git/commit/?id=2f26f40

Commit message:

Add remove-jdkClassifier.patch and remove the jdkClassifier from the 
resulting

jar file. This will ensure that dh_auto_install will correctly install the 
file
into the binary package.

Closes: #869002

Processed: Re: apache-log4j2: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> reassign -1 src:conversant-disruptor
Bug #869002 [src:apache-log4j2] apache-log4j2: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Bug reassigned from package 'src:apache-log4j2' to 'src:conversant-disruptor'.
No longer marked as found in versions apache-log4j2/2.8.2-1.
Ignoring request to alter fixed versions of bug #869002 to the same values 
previously set
> retitle -1 conversant-disruptor does not install the jar file
Bug #869002 [src:conversant-disruptor] apache-log4j2: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Changed Bug title to 'conversant-disruptor does not install the jar file' from 
'apache-log4j2: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory'.
> tags -1 pending
Bug #869002 [src:conversant-disruptor] conversant-disruptor does not install 
the jar file
Added tag(s) pending.

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

Bug#869002: apache-log4j2: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-10-15 Thread Markus Koschany

Control: reassign -1 src:conversant-disruptor
Control: retitle -1 conversant-disruptor does not install the jar file
Control: tags -1 pending

The original toolchain issue appears to be resolved. However there is a
second issue because the disruptor artifact cannot be found. The reason
is libconversant-disruptor-java does not ship this jar file!
Reassigning. Fix is pending.

Markus



signature.asc
Description: OpenPGP digital signature

Processed (with 5 errors): Re: unrar-free: Should unrar-free be removed from the archive? Alternatives (libarchive) exist; unmaintained upstream; has security issues

2017-10-15 Thread Debian Bug Tracking System

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

> severity 874065 important
Bug #874065 [src:unrar-free] unrar-free: Should unrar-free be removed from the 
archive? Alternatives (libarchive) exist; unmaintained upstream; has security 
issues
Severity set to 'important' from 'serious'
> Hi all,
Unknown command or malformed arguments to command.
> I've fixed the security issues happened on unrar-free. Seems not hard.
Unknown command or malformed arguments to command.
> But as I explain before that I think programs should move to use unar if
Unknown command or malformed arguments to command.
> possible.
Unknown command or malformed arguments to command.
> But to me I think there's still many programs which depends on the
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#874060: marked as done (unrar-free: CVE-2017-14122: stack overread vulnerability)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 17:20:19 +
with message-id 
and subject line Bug#874060: fixed in unrar-free 1:0.0.1+cvs20140707-4
has caused the Debian Bug report #874060,
regarding unrar-free: CVE-2017-14122: stack overread vulnerability
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.)


-- 
874060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unrar-free
Version: 1:0.0.1+cvs20140707-1
Severity: grave
Tags: security upstream

Hi

>From http://www.openwall.com/lists/oss-security/2017/08/20/1 

Issue 2: Stack overread

A malformed archive can cause a stack overread, detectable with asan.
This issue doesn't happen reliably, I haven't investigated further.

==2585==ERROR: AddressSanitizer: stack-buffer-overflow on address 
0x7fff76184120 at pc 0x00445d25 bp 0x7fff76183ef0 sp 0x7fff761836a0
READ of size 519 at 0x7fff76184120 thread T0
#0 0x445d24 in __interceptor_strchr.part.33 (/r/unrar-gpl/unrar+0x445d24)
#1 0x516d0d in stricomp /f/unrar-gpl/unrar/src/unrarlib.c:851:19
#2 0x511613 in ExtrFile /f/unrar-gpl/unrar/src/unrarlib.c:745:20
#3 0x510b02 in urarlib_get /f/unrar-gpl/unrar/src/unrarlib.c:303:13
#4 0x50b249 in unrar_extract_file /f/unrar-gpl/unrar/src/unrar.c:343:8
#5 0x50be32 in unrar_extract /f/unrar-gpl/unrar/src/unrar.c:483:9
#6 0x50c69c in main /f/unrar-gpl/unrar/src/unrar.c:556:14
#7 0x7f632d3834f0 in __libc_start_main (/lib64/libc.so.6+0x204f0)
#8 0x419e19 in _start (/r/unrar-gpl/unrar+0x419e19)

Address 0x7fff76184120 is located in stack of thread T0 at offset 544 in frame
#0 0x516c1f in stricomp /f/unrar-gpl/unrar/src/unrarlib.c:844

  This frame has 2 object(s):
[32, 544) 'S1'
[608, 1120) 'S2' <== Memory access at offset 544 partially
underflows this variable

Regards,
Salvatore


unrar-gpl-stack-overread.rar
Description: application/rar
--- End Message ---
--- Begin Message ---
Source: unrar-free
Source-Version: 1:0.0.1+cvs20140707-4

We believe that the bug you reported is fixed in the latest version of
unrar-free, 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 874...@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 unrar-free 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Oct 2017 00:46:04 +0800
Source: unrar-free
Binary: unrar-free
Architecture: source amd64
Version: 1:0.0.1+cvs20140707-4
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 unrar-free - Unarchiver for .rar files
Closes: 724295 874060 874061
Changes:
 unrar-free (1:0.0.1+cvs20140707-4) unstable; urgency=low
 .
   * Fix CVE-2017-14122 (Closes: #874060)
 - debian/patches/0002-CVE-2017-14122.patch
   * Add autopkgtest for testing CVE-2017-14122
   * Fix CVE-2017-14121 (Closes: #874061)
 - debian/patches/0003-CVE-2017-14121.patch
   * Add autopkgtest for testing CVE-2017-14121
   * Fix compatibility for -y option (Closes: #724295)
 - debian/patches/0004-unrar-nonfree-compat-ignored-options.patch
 - Thanks to Dominik George 
   * Bump Standards-Version to 4.1.1: Nothing needs to be changed
Checksums-Sha1:
 ee918fcd8e93bbd251b9ff3a58ec555c3c4840f4 1994 
unrar-free_0.0.1+cvs20140707-4.dsc
 b20bba1496e45edbd5668b4c30916e61c91bffe8 8016 
unrar-free_0.0.1+cvs20140707-4.debian.tar.xz
 0e31a6b1a90aa3723e7d8474e05e56f416299be6 38966 
unrar-free-dbgsym_0.0.1+cvs20140707-4_amd64.deb
 94ded45816828c4c96cab5c51a1b751278d5ed7b 6264 
unrar-free_0.0.1+cvs20140707-4_amd64.buildinfo
 ce388783311931beae64536f193b4c1674939454 25132 
unrar-free_0.0.1+cvs20140707-4_amd64.deb
Checksums-Sha256:
 6424e3673e8306e623da65b7562c4fbb5cb4ab45756d4a1b690ded3b955813d4 1994 
unrar-free_0.0.1+cvs20140707-4.dsc
 4727e63baed3d254d80be9fe6dc77791d1d16dadc31110004d0ee9b74fda097e 8016 
unrar-free_0.0.1+cvs20140707-4.debian.tar.xz

Bug#874061: marked as done (unrar-free: CVE-2017-14121: null pointer dereference)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 17:20:20 +
with message-id 
and subject line Bug#874061: fixed in unrar-free 1:0.0.1+cvs20140707-4
has caused the Debian Bug report #874061,
regarding unrar-free: CVE-2017-14121: null pointer dereference
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.)


-- 
874061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unrar-free
Version: 1:0.0.1+cvs20140707-1
Severity: grave
Tags: security upstream

Hi

>From http://www.openwall.com/lists/oss-security/2017/08/20/1


Issue 3: Null pointer

A malformed input file can cause a null pointer read.

==3328==ERROR: AddressSanitizer: SEGV on unknown address 0x0020 (pc 
0x0051ed2c bp 0x00278b18 sp 0x7fffc410e300 T0)
==3328==The signal is caused by a READ memory access.
==3328==Hint: address points to the zero page.
#0 0x51ed2b in DecodeNumber /f/unrar-gpl/unrar/src/unrarlib.c:1649:16
#1 0x5186f5 in Unpack /f/unrar-gpl/unrar/src/unrarlib.c:1148:4
#2 0x511c47 in ExtrFile /f/unrar-gpl/unrar/src/unrarlib.c:799:10
#3 0x510b02 in urarlib_get /f/unrar-gpl/unrar/src/unrarlib.c:303:13
#4 0x50b249 in unrar_extract_file /f/unrar-gpl/unrar/src/unrar.c:343:8
#5 0x50be32 in unrar_extract /f/unrar-gpl/unrar/src/unrar.c:483:9
#6 0x50c69c in main /f/unrar-gpl/unrar/src/unrar.c:556:14
#7 0x7f0a337df4f0 in __libc_start_main (/lib64/libc.so.6+0x204f0)
#8 0x419e19 in _start (/r/unrar-gpl/unrar+0x419e19)

Regards,
Salvatore


unrar-gpl-nullptr.rar
Description: application/rar
--- End Message ---
--- Begin Message ---
Source: unrar-free
Source-Version: 1:0.0.1+cvs20140707-4

We believe that the bug you reported is fixed in the latest version of
unrar-free, 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 874...@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 unrar-free 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Oct 2017 00:46:04 +0800
Source: unrar-free
Binary: unrar-free
Architecture: source amd64
Version: 1:0.0.1+cvs20140707-4
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 unrar-free - Unarchiver for .rar files
Closes: 724295 874060 874061
Changes:
 unrar-free (1:0.0.1+cvs20140707-4) unstable; urgency=low
 .
   * Fix CVE-2017-14122 (Closes: #874060)
 - debian/patches/0002-CVE-2017-14122.patch
   * Add autopkgtest for testing CVE-2017-14122
   * Fix CVE-2017-14121 (Closes: #874061)
 - debian/patches/0003-CVE-2017-14121.patch
   * Add autopkgtest for testing CVE-2017-14121
   * Fix compatibility for -y option (Closes: #724295)
 - debian/patches/0004-unrar-nonfree-compat-ignored-options.patch
 - Thanks to Dominik George 
   * Bump Standards-Version to 4.1.1: Nothing needs to be changed
Checksums-Sha1:
 ee918fcd8e93bbd251b9ff3a58ec555c3c4840f4 1994 
unrar-free_0.0.1+cvs20140707-4.dsc
 b20bba1496e45edbd5668b4c30916e61c91bffe8 8016 
unrar-free_0.0.1+cvs20140707-4.debian.tar.xz
 0e31a6b1a90aa3723e7d8474e05e56f416299be6 38966 
unrar-free-dbgsym_0.0.1+cvs20140707-4_amd64.deb
 94ded45816828c4c96cab5c51a1b751278d5ed7b 6264 
unrar-free_0.0.1+cvs20140707-4_amd64.buildinfo
 ce388783311931beae64536f193b4c1674939454 25132 
unrar-free_0.0.1+cvs20140707-4_amd64.deb
Checksums-Sha256:
 6424e3673e8306e623da65b7562c4fbb5cb4ab45756d4a1b690ded3b955813d4 1994 
unrar-free_0.0.1+cvs20140707-4.dsc
 4727e63baed3d254d80be9fe6dc77791d1d16dadc31110004d0ee9b74fda097e 8016 
unrar-free_0.0.1+cvs20140707-4.debian.tar.xz
 a5a0ac29d95c28fb035bde6bc675727290d2afca01aeb95372b5cdecb0f0a937 38966 
unrar-free-dbgsym_0.0.1+cvs20140707-4_amd64.deb
 ea5b558efd8f8f53abf4938634404d89b315474eca582fcd049e42ecec74e11b 6264 
unrar-free_0.0.1+cvs20140707-4_amd64.buildinfo
 8b2113d348e065ce71cffab1e15d86102d242efd082d692a9818914d9f8ca36b 25132 
unrar-free_0.0.1+cvs20140707-4_amd64.deb
Files:

Bug#874065: unrar-free: Should unrar-free be removed from the archive? Alternatives (libarchive) exist; unmaintained upstream; has security issues

2017-10-15 Thread Ying-Chun Liu (PaulLiu)

severity 874065 important
Hi all,

I've fixed the security issues happened on unrar-free. Seems not hard.
But as I explain before that I think programs should move to use unar if
possible.

But to me I think there's still many programs which depends on the
command line unrar-nonfree tool thus unrar-free still is needed for
compatibility. I'm lowering the severity of this bug temporarily and
will look on how many other programs are still depends on unrar-nonfree.

Yours Sincerely,
Paul

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature

Bug#874061: unrar-free: CVE-2017-14121: null pointer dereference

2017-10-15 Thread Ying-Chun Liu (PaulLiu)

Hi,

I've fixed this bug. Please see the attachment. The patch and the
autopkgtest scripts.

Yours,
Paul

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 
Description: This patch fixes CVE-2017-14121
 CVE-2017-14121 describes a security issue about null pointer dereference
 vulnerability.
Author: Ying-Chun Liu (PaulLiu) 
Bug-Debian: https://bugs.debian.org/874061
Last-Update: 2017-10-14

Index: unrar-free-0.0.1+cvs20140707/src/unrarlib.c
===
--- unrar-free-0.0.1+cvs20140707.orig/src/unrarlib.c
+++ unrar-free-0.0.1+cvs20140707/src/unrarlib.c
@@ -1651,6 +1651,8 @@ DecodeNumber (struct Decode *Deco)
 
 #else
   N = BitField & 0xFFFE;
+  if (!Deco->DecodeLen)
+return;
   if (N < Deco->DecodeLen[8])
 {
   if (N < Deco->DecodeLen[4])
#!/bin/sh
#
# Test CVE-2017-14121

setUp() {
uudecode > unrar-gpl-nullptr.rar < 
"$AUTOPKGTEST_TMP"/0004-CVE-2017-14121.log 2>&1
grep -q '*** Segmentation fault' 
"$AUTOPKGTEST_TMP"/0004-CVE-2017-14121.log
assertNotEquals "catchsegv value" 0 $?

valgrind --error-exitcode=121 --track-origins=yes unrar-free --extract 
unrar-gpl-nullptr.rar
assertNotEquals "Valgrind status code" 121 $?
}

. /usr/bin/shunit2


signature.asc
Description: OpenPGP digital signature

Bug#878670: marked as done (python3-fonttools needs Replaces: fonttools (<< 3.15.1-3~))

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 16:49:21 +
with message-id 
and subject line Bug#878670: fixed in fonttools 3.16.0-1
has caused the Debian Bug report #878670,
regarding python3-fonttools needs Replaces: fonttools (<< 3.15.1-3~)
to be marked as done.

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

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


-- 
878670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fonttools
Version: 3.15.1-3
Severity: serious

Preparing to unpack .../4-python3-fonttools_3.15.1-3_all.deb ...
Unpacking python3-fonttools (3.15.1-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-VMnXg8/4-python3-fonttools_3.15.1-3_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3/dist-packages/fontTools/__init__.py', 
which is also in package fonttools 3.15.1-2
--- End Message ---
--- Begin Message ---
Source: fonttools
Source-Version: 3.16.0-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated fonttools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Oct 2017 18:13:56 +0200
Source: fonttools
Binary: python3-fonttools python-fonttools python-fonttools-doc fonttools
Architecture: source all
Version: 3.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Rene Engelhard 
Description:
 fonttools  - Converts OpenType and TrueType fonts to and from XML
 python-fonttools - Converts OpenType and TrueType fonts to and from XML
 python-fonttools-doc - Converts OpenType and TrueType fonts to and from XML
 python3-fonttools - Converts OpenType and TrueType fonts to and from XML
Closes: 878670
Changes:
 fonttools (3.16.0-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 3.16.0
 .
   * add Replaces:/Breaks: also for python3-fonttools (closes: #878670)
Checksums-Sha1:
 2294cef8c4e66319f15459b95c05d51cd1c40ddc 2260 fonttools_3.16.0-1.dsc
 5ef92b9294a5814aa758c26ea25227a83ace9bf8 932006 fonttools_3.16.0.orig.tar.gz
 6071a8349d82e524ced1fb09dc05b40f48128aec 5496 fonttools_3.16.0-1.debian.tar.xz
 49a7d1668e02e231f4980620203cc279299abb4d 8260 fonttools_3.16.0-1_all.deb
 25782278f0c71f9a6e1e1d81440d526a7e7f15e8 8094 
fonttools_3.16.0-1_amd64.buildinfo
 c2269fab974dc85db7f5c35df7f2211bc791 586044 
python-fonttools-doc_3.16.0-1_all.deb
 ffb8e414a3a6cd69472a597693f8d1b0b19c93a9 356556 
python-fonttools_3.16.0-1_all.deb
 6fe870b4c9867a8a96a28fe61078e590c13b0481 374758 
python3-fonttools_3.16.0-1_all.deb
Checksums-Sha256:
 79dd3ddb36c50fb9baeecfaacb1d32e06d5c287e6305cbeb81be474745b06615 2260 
fonttools_3.16.0-1.dsc
 e883c7392bd7c9b2e91058c39177f0312da6b1770b4ca363a1da5fa17846e80e 932006 
fonttools_3.16.0.orig.tar.gz
 e1453127e3eb60881500c7de678376412c9a490e8400e62d453a6ebe55964f49 5496 
fonttools_3.16.0-1.debian.tar.xz
 5da86a5bdcd83d24916183c8797eeff7ff9502bae68bd7b7c08dd1ba9d77c702 8260 
fonttools_3.16.0-1_all.deb
 8ee4697e6fcba58a61db986d3f40c881fb9166e5776d1daede93090f5a2f57ba 8094 
fonttools_3.16.0-1_amd64.buildinfo
 9a445f73b3040f9fc00c3a5a21606477486ec796fe32d37a644b3667cd4f93fa 586044 
python-fonttools-doc_3.16.0-1_all.deb
 b393df73e6cb829a5d982f7b64fa459b3e1512bb5c69e81abc0cee99123eadf9 356556 
python-fonttools_3.16.0-1_all.deb
 8f4f73b1ff2f543b30778d3a25df139bcb07ab1da60d88353615c850b5f49f46 374758 
python3-fonttools_3.16.0-1_all.deb
Files:
 813702a92db6675f7ee30b731716ea3b 2260 devel optional fonttools_3.16.0-1.dsc
 0a1221d0b13d6e6f0281c78a31d363cf 932006 devel optional 
fonttools_3.16.0.orig.tar.gz
 c85d761ebc5002136d3de783513b3853 5496 devel optional 
fonttools_3.16.0-1.debian.tar.xz
 f24a7587e5f78bdbef61c73855ca2cdf 8260 devel optional fonttools_3.16.0-1_all.deb
 2f4ba7910e392be952810fa6b2ab58e9 8094 devel optional 
fonttools_3.16.0-1_amd64.buildinfo
 ccbb855c7e7333ed75bc71fc1b05c8a4 586044 doc optional

Bug#878674: nodejs segfaults when building d3-* with webpack

2017-10-15 Thread Pirate Praveen

package: nodejs
version: 6.11.4~dfsg-1
severity: serious

I have noticed this failure when building multiple node-d3-* packages
(node-d3-zoom for example) and also installing gitlab 9.5 using webpack.

When building the same node-d3-zoom with nodejs
7.10.1-2nodesource1~stretch1 the build passed. Tried both in local
installation and using sbuild.

Also tested the same on my laptop and on a vm

babeljs src -d lib
src/constant.js -> lib/constant.js
src/event.js -> lib/event.js
src/noevent.js -> lib/noevent.js
src/transform.js -> lib/transform.js
src/zoom.js -> lib/zoom.js
babeljs index.js -d lib
index.js -> lib/index.js
sed -i 's/.\/src/./' lib/index.js
webpack --config debian/webpack.config.js index.js build/d3-zoom.js
--target=web --output-library=d3-zoom --output-library-target=umd
--module-bind 'js=babel-loader'
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Segmentation fault
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Since babel and other dependencies are still in NEW, I have setup a repo
for packages still in NEW.

I have /usr/local/bin/sbuild-babel,
sbuild -A -s -d unstable --extra-repository='deb
https://people.debian.org/~praveen/babel sid main'
--extra-repository-key=/home/pravi/forge/debian/babel/repo/praveen.key.asc
$@

With nodejs from nodesource.com, the build passes, both locally and in
sbuild. For sbuild I have to pass --extra-package option and in
debian/rules, I have to add export NODE_PATH=/usr/lib/nodejs

node-d3-geo, node-d3-scale are other packages that segfaults.

All node-d3-* packages are in pkg-javascript team repo in alioth.



signature.asc
Description: OpenPGP digital signature

Bug#869007: marked as done (libslf4j-java: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 18:10:13 +0200
with message-id <1bbbcaa7-2ec4-ab7c-d416-2c634fcd9...@debian.org>
and subject line Re: libslf4j-java: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869007,
regarding libslf4j-java: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
to be marked as done.

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

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


-- 
869007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libslf4j-java
Version: 1.7.25-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibslf4j-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-api:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-simple:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-nop:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-jdk14:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-log4j12:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-jcl:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:jcl-over-slf4j:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:log4j-over-slf4j:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:jul-to-slf4j:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
>

Bug#869009: marked as done (mustache-java: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 18:05:11 +0200
with message-id <4efb52a3-bfce-2e78-0899-19c02a2f3...@debian.org>
and subject line Re: mustache-java: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869009,
regarding mustache-java: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
to be marked as done.

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

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


-- 
869009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mustache-java
Version: 0.8.18-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmustache-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] mustache.java
> [[1;34mINFO[m] compiler
> [[1;34mINFO[m] codegen
> [[1;34mINFO[m] indy
> [[1;34mINFO[m] mustache-maven-plugin Maven Mojo
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding mustache.java 0.8.18[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding compiler 0.8.18[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mcompiler[0;1m ---[m
> [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources.
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/compiler/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mcompiler[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 63 source files to 
> /<>/compiler/target/classes
> [[1;34mINFO[m] 
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java:
>  
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java
>  uses unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default)[m @ [36mcompiler[0;1m ---[m
>

Bug#878671: python-enable: dependency must be changed from fonttools to python-fonttools

2017-10-15 Thread Adrian Bunk

Package: python-enable
Version: 4.5.1-3
Severity: serious

fonttools does no longer provide the python2 modules
(and now depends on python3-fonttools),
see #876439 and #877165 for background.

Bug#878670: python3-fonttools needs Replaces: fonttools (<< 3.15.1-3~)

2017-10-15 Thread Adrian Bunk

Package: python3-fonttools
Version: 3.15.1-3
Severity: serious

Preparing to unpack .../4-python3-fonttools_3.15.1-3_all.deb ...
Unpacking python3-fonttools (3.15.1-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-VMnXg8/4-python3-fonttools_3.15.1-3_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3/dist-packages/fontTools/__init__.py', 
which is also in package fonttools 3.15.1-2

Bug#877379: marked as done (CVE-2017-14685 / CVE-2017-14686 / CVE-2017-14687)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 15:38:35 +
with message-id 
and subject line Bug#877379: fixed in mupdf 1.11+ds1-1.1
has caused the Debian Bug report #877379,
regarding CVE-2017-14685 / CVE-2017-14686 / CVE-2017-14687
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.)


-- 
877379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mupdf
Version: 1.11+ds1-1
Severity: grave
Tags: security

Hi,
please see
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14685
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14686
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14687

which contains further descriptions and links to upstream fixes.
Can you please also prepare updates for stretch-security/jessie-security?

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: mupdf
Source-Version: 1.11+ds1-1.1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated mupdf 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, 08 Oct 2017 10:37:23 +0200
Source: mupdf
Binary: libmupdf-dev mupdf mupdf-tools
Architecture: source
Version: 1.11+ds1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kan-Ru Chen (陳侃如) 
Changed-By: Salvatore Bonaccorso 
Closes: 877379
Description: 
 libmupdf-dev - development files for the MuPDF viewer
 mupdf  - lightweight PDF viewer
 mupdf-tools - command line tools for the MuPDF viewer
Changes:
 mupdf (1.11+ds1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't use xps font if it could not be loaded (CVE-2017-14685)
 (Closes: #877379)
   * Check name, comment and meta size field signs (CVE-2017-14686)
 (Closes: #877379)
   * Handle non-tags in tag name comparisons (CVE-2017-14687) (Closes: #877379)
Checksums-Sha1: 
 ec41dd2f4d1ecd3d0e0974bc7ac7cc2d8ed84153 2316 mupdf_1.11+ds1-1.1.dsc
 2f4d9fcde11d09058834c6b34eac0d06821ec9f0 26408 mupdf_1.11+ds1-1.1.debian.tar.xz
Checksums-Sha256: 
 77bd9843f4c442b99f4e98d7605fb9139fb8e2c38d710ef7fd9b8dc96475a04b 2316 
mupdf_1.11+ds1-1.1.dsc
 cb274532e34f818b2f1871fee6303cfffda37251937dd7d731a898b2ca736433 26408 
mupdf_1.11+ds1-1.1.debian.tar.xz
Files: 
 630593b9756c7076c81053da26132a5e 2316 text optional mupdf_1.11+ds1-1.1.dsc
 4bf112ceea37740d8ee71510228692c3 26408 text optional 
mupdf_1.11+ds1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlnhupRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89Etf4P/1LVBMWOoVlpO4KTy/6xy7z03+hwrpQo
sJdPo+s8v9G4+kXCUBUZh4kKz3D8HxUBR2kg5c3IVd01gXFctM+lyNJwtm5UgxBW
ZMNRc1Qjm0MMJW1t1qlnXlcxPy35hkSDsAGQs7L/haZXn6fnfLSNtvPl21xYHHDw
/jNBGwgMIo9MXKftY6cBzAOspD2Z8jOa/f3LSEb6fiBmp8kkOz+KTRpZqkYgXvN8
VtelaPjSb81+VFu5lcZ0BFqWToQJDtNXAh1ZiADSxs4umeTW0hOVOwSDo+FZflCG
t9kDkBuiRxk1m0KUvPjH9+lAK0EMY9N0k/g8SsKh3ZGQ+OKnMJBst59OQyjbPnlI
Ha5THFoPbc+b6A2mSTTl+wMDyM6e/hTJmkhpku1DKo9UXk5jefUbuM4mBli+5bwM
u0V07OlIFaFZenv3ppMGQk2vPHwk9Xs+38eP7Wrx8To+CyyYbd6UUH46Yj8/NZnM
lruaUC65XRRTR7WUQ0Jug5TXIjH2pRyyk22GH/4lC/6S0xd6Vfb5vUZBKReCOJ1z
5iE02l7uuDbom3fABipI+DH5Mx/R1vfN56PBD2dYAj3vjsJK2yswBid75V598wiL
M0CKXIU6b8vaVBdGx0TgEIwMLvR+UL8ONGRzpS0jZbE6cBfsa1x1ODqt/F5hwHHD
FnFaxjkD21ZH
=5Ehs
-END PGP SIGNATURE End Message ---

Bug#878666: kopano-search depends on cruft package mktemp

2017-10-15 Thread peter green


Package: kopano-search
Severity: serious
Tags: buster, sid

kopano-search depends on the package mktemp which is no longer built by the coreutils source 
package. Prior to being dropped this was a transitional package depending on "coreutils 
(>= 7.4-1)", please update your dependency so that the package can be decrufted.

Bug#877379: mupdf: diff for NMU version 1.11+ds1-1.1

2017-10-15 Thread Salvatore Bonaccorso

Hi

On Sat, Oct 14, 2017 at 11:52:44PM +0800, Kan-Ru Chen wrote:
> Thanks for preparing the NMU! I really appreciate that.
> 
> Please go ahead and upload it directly to sid. 

Thank you!

I rescheduled now (could only act on it now).

Regards,
Salvatore

Processed: bug 878632 is forwarded to https://github.com/zmughal/p5-Font-FreeType/issues/21

2017-10-15 Thread Debian Bug Tracking System

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

> forwarded 878632 https://github.com/zmughal/p5-Font-FreeType/issues/21
Bug #878632 [src:libfont-freetype-perl] libfont-freetype-perl: FTBFS and Debci 
failure with libfreetype6 2.8.1-0.1
Set Bug forwarded-to-address to 
'https://github.com/zmughal/p5-Font-FreeType/issues/21'.
> thanks
Stopping processing here.

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

Processed: limit source to pgextwlist, tagging 876851

2017-10-15 Thread Debian Bug Tracking System

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

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

> tags 876851 + pending
Bug #876851 [src:pgextwlist] pgextwlist FTBFS with PostgreSQL 10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 878632

2017-10-15 Thread Debian Bug Tracking System

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

> tags 878632 + confirmed
Bug #878632 [src:libfont-freetype-perl] libfont-freetype-perl: FTBFS and Debci 
failure with libfreetype6 2.8.1-0.1
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#876752: marked as done (libllvm5.0: Can not install libllvm5.0:i386 from latest unstable)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 15:37:41 +0200
with message-id <5125a339-9b3f-f13c-b9fd-598b86f26...@debian.org>
and subject line ocaml transition / llvm ocaml binding removed for now
has caused the Debian Bug report #876752,
regarding libllvm5.0: Can not install libllvm5.0:i386 from latest unstable
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.)


-- 
876752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libllvm5.0
Version: 1:5.0-2
Severity: important

Dear Maintainer,

Can not install libllvm5.0:i386 while libllvm5.0:amd64 already exists in system:

# aptitude why-not libllvm5.0:i386
i   libllvm5.0 Breaks libllvm5.0:i386 (!= 1:5.0-2)


Also, apt message is not very usable:

apt install libllvm5.0:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 default-jre : Depends: openjdk-8-jre but it is not going to be installed
   Recommends: default-java-plugin but it is not going to be 
installed
 gnome-user-guide : Depends: gnome-user-docs but it is not going to be installed
 gnucash : Depends: libwebkitgtk-1.0-0 (>= 1.3.10) but it is not going to be 
installed
   Recommends: yelp but it is not going to be installed
 gvfs-daemons : Depends: x11-utils
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


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

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

Versions of packages libllvm5.0 depends on:
ii  libc6   2.24-17
ii  libedit23.1-20170329-1
ii  libffi6 3.2.1-6
ii  libgcc1 1:7.2.0-7
ii  libstdc++6  7.2.0-7
ii  libtinfo5   6.0+20170902-1
ii  zlib1g  1:1.2.8.dfsg-5

libllvm5.0 recommends no packages.

libllvm5.0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
fixed 876752 1:5.0-4
fixed 878291 1:5.0-4
thanks--- End Message ---

Processed: ocaml transition / llvm ocaml binding removed for now

2017-10-15 Thread Debian Bug Tracking System

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

> fixed 876752 1:5.0-4
Bug #876752 [libllvm5.0] libllvm5.0: Can not install libllvm5.0:i386 from 
latest unstable
Marked as fixed in versions llvm-toolchain-5.0/1:5.0-4.
> fixed 878291 1:5.0-4
Bug #878291 [libllvm-5.0-ocaml-dev] libllvm-5.0-ocaml-dev: Please consider 
dropping ocaml bindings or moving to a separate source package
There is no source info for the package 'libllvm-5.0-ocaml-dev' at version 
'1:5.0-4' with architecture ''
Unable to make a source version for version '1:5.0-4'
Marked as fixed in versions 1:5.0-4.
> thanks
Stopping processing here.

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

Processed: found 878643 in 3.15.1-2

2017-10-15 Thread Debian Bug Tracking System

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

> found 878643 3.15.1-2
Bug #878643 [src:fonttools] fonttools: Incomplete debian/copyright?
Marked as found in versions fonttools/3.15.1-2.
> thanks
Stopping processing here.

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

Bug#876752: libllvm5.0: Can not install libllvm5.0:i386 from latest unstable

2017-10-15 Thread Antoine

Installing the testing version of the package is no longer needed, the
new build available in unstable allow to install both amd64 and i386
versions of the package at the same time.

Unless I’m missing something, this bug is fixed with version 1:5.0-4 of
libllvm5.0



signature.asc
Description: OpenPGP digital signature

Bug#876308: libxml2 FTBFS: rename: "Unknown option: vf"

2017-10-15 Thread Mattia Rizzolo

On Sun, Oct 15, 2017 at 12:41:53PM +0200, Manuel A. Fernandez Montecelo wrote:
> >> libxslt needed also to add "rename" as B-D, which I added in a recent
> >> NMU.
> >
> > About that, next time please consider using the delayed queue, and for
> > packages where I'm somehow involved consider also picking the unreleased
> > changes from the git repositories :)
> 
> Sorry about that Mattia.  Since there almost no uploads in the last
> year (other than fixes for old suites), and the FTBFS bug open for 2
> or 3 weeks without replies, I thought that the package was a bit
> behind in maintenance

Yes, it is definitly under-maintained…  (as libxml2 is, btw) :(
That's why, don't get me wrong, I'm very happy you NMUed it!  I just
hoped you could give a notice before it landed, so I could suggest you
picked the unreleased VCS changes :)

-- 
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: Re: Bug#878584: [libevas-dev] Missing dependency for libecore-dev

2017-10-15 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #878584 [libevas-dev] [libevas-dev] Missing dependency for libecore-dev
Severity set to 'serious' from 'important'
> tags -1 patch
Bug #878584 [libevas-dev] [libevas-dev] Missing dependency for libecore-dev
Added tag(s) patch.

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

Bug#878631: [pkg-fgfs-crew] Bug#878631: flightgear build depends on libsimgear-dev (<= 1:2017.2.999) but 1:2017.3.1+dfsg-1 is to be installed

2017-10-15 Thread Dr. Tobias Quathamer

Am 15. Oktober 2017 11:27:31 MESZ schrieb Adrian Bunk :
>Source: flightgear
>Version: 1:2017.2.1+dfsg-4
>Severity: serious
>
>The following packages have unmet dependencies:
>builddeps:flightgear : Depends: libsimgear-dev (<= 1:2017.2.999) but
>1:2017.3.1+dfsg-1 is to be installed
>
>___
>pkg-fgfs-crew mailing list
>pkg-fgfs-c...@lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fgfs-crew

control: tag -1 pending

Hi,

thanks for filing this bug, you've been a bit too fast -- I did not manage to 
upload the next version of flightgear yesterday as well, which will fix this 
bug. :-)

I plan to do the upload today, probably in the evening.

Regards,
Tobias

Bug#877165: marked as done (fonttools: python library should be in separate binary package python(3)-fonttools)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 11:00:11 +
with message-id 
and subject line Bug#877165: fixed in fonttools 3.15.1-3
has caused the Debian Bug report #877165,
regarding fonttools: python library should be in separate binary package 
python(3)-fonttools
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.)


-- 
877165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonttools
Severity: serious
Justification: python policy §3.3

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Public python libraries must be named with a leading "python-" or
"python3-":
https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html#package_names

Python library part of FontTools should therefore be packaged in
separate binary package named "python3-fonttools".


Regards,

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlnOKYYACgkQLHwxRsGg
ASGfNg/+MVzwFuhP7/A/EofTmq6dq+x+FCNidtCoRArGQYVjVYvOFLxMMFEhzNfe
yfYIYhobYANfeUQfQQe3HBbO1WVGi/0jSQbBZ/I4cnRfS+U62N1bzUqj63D3lsaJ
Kjeu5HpsQ48d7KHNsatJicuCdd2vQf0mRwrZpACWQqCZGo1b8Gl6S4vnyxgTO8MO
PWinB3XIQtVnb9OXLyst9+mdc7NBlvgvOJr7SOtw60A3lfBztUu5OpVEkoyhKDZo
S95HSIcz5WZhfm5XQBCdfP38v6/5OIIo94qlQ6Jr7/9oCgYu0Dm/dGuAS5uOjMCd
XOZ4435QjASatJpSIK0V/OsfeyOKUTnWaFTCJsvQyeihuJb0R0JnqgW4YTsoGkor
SVjaIviCab62Ml3dttmPih0kGt3RhrcrWPx9ofXADvH7H5Ldp1sls4xy2psMz9/k
0+9nfXrXnCup3TXlcNp99thm3Vr1Q4zu6PtD8XHwqSd6EbbVOoVprUtdtRCjkGgU
zFlOcH/w8VHP9xHM7MGM3pJWlXSgl3BlXQ+Zmi3bzXJ8K8tb2/0XLEZxw+305ryJ
biSrrfBEYqHuCKewfesorxID+tir7YNRw3vHlCqH4uOVv/FDcoe3I16DHwow9IqZ
Ij5YFSFTas7L7KuwxMebk7YGrNdnyKo++sn1pkdXHBWzlVIMGPE=
=cBxK
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: fonttools
Source-Version: 3.15.1-3

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

Debian distribution maintenance software
pp.
Yao Wei (魏銘廷)  (supplier of updated fonttools 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: Tue, 03 Oct 2017 11:52:42 +0800
Source: fonttools
Binary: python3-fonttools python-fonttools python-fonttools-doc fonttools
Architecture: source all
Version: 3.15.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Yao Wei (魏銘廷) 
Description:
 fonttools  - Converts OpenType and TrueType fonts to and from XML
 python-fonttools - Converts OpenType and TrueType fonts to and from XML
 python-fonttools-doc - Converts OpenType and TrueType fonts to and from XML
 python3-fonttools - Converts OpenType and TrueType fonts to and from XML
Closes: 876439 877165
Changes:
 fonttools (3.15.1-3) unstable; urgency=medium
 .
   * Team upload
   * Separate the package to multiple packages (Closes: #877165)
   * Provide python2 version of fonttools (Closes: #876439)
   * Change the section from fonts to devel
   * Set Standards-Version to 4.1.1
Checksums-Sha1:
 0d8ff93b7c614053a9cab0bc1310e9b9873bf59d 2260 fonttools_3.15.1-3.dsc
 d08dbd71bc24a5b417960c931818efed3780b1fc 5424 fonttools_3.15.1-3.debian.tar.xz
 56de305d3eba9176bc3b1551ba1c3539323edbe1 8194 fonttools_3.15.1-3_all.deb
 e0d77d3a41c8259a6c4dd1b49fb854ae740a88b7 8076 
fonttools_3.15.1-3_amd64.buildinfo
 a1d43c4e0058763e5ca293219a103f790bdc4577 585950 
python-fonttools-doc_3.15.1-3_all.deb
 5234a5af060ab80777063aa4d9d303d665838a1b 338792 
python-fonttools_3.15.1-3_all.deb
 d8e5363de4ebf2a5b90d1b5bd847ba4baa8dc925 356452 
python3-fonttools_3.15.1-3_all.deb
Checksums-Sha256:
 44dcb07d02b6a6ab90058b5be3f5be5b4c30f2e9c114cfa2cbdc9c852846a114 2260 
fonttools_3.15.1-3.dsc
 469a16c7d44c24e9228a7ba42f1cc81e33062fe6799141446cc5bcd423fd398e 5424 
fonttools_3.15.1-3.debian.tar.xz
 c32d8e577c638f4b58af5532f8e2b1d1bf582d9a793c559b736bf97632a4b713 8194 
fonttools_3.15.1-3_all.deb
 243e8564e79412c8c16dec1ee0e7bcb856f19e8bee0b9d9a94662a617dea1efb 8076 
fonttools_3.15.1-3_amd64.buildinfo

Bug#878643: fonttools: Incomplete debian/copyright?

2017-10-15 Thread Chris Lamb

Source: fonttools
Version: 3.15.1-3
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Yao Wei (魏銘廷) 

Hi,

I just ACCEPTed fonttools from NEW but noticed it was missing 
attribution in debian/copyright for a large nember of files
under Tests/*.

This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Processed: tagging 709198

2017-10-15 Thread Debian Bug Tracking System

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

> tags 709198 + pending
Bug #709198 [debconf] debconf: should not use python in maintainer scripts
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876308: libxml2 FTBFS: rename: "Unknown option: vf"

2017-10-15 Thread Manuel A. Fernandez Montecelo

2017-10-15 2:31 GMT+02:00 Mattia Rizzolo :
> On Sun, Oct 15, 2017 at 02:01:53AM +0200, Manuel A. Fernandez Montecelo wrote:
>> Maybe it needs a build-depends on "rename", which was split from the
>> Perl package.
>
> No.
>
> The bug here is that the new `rename` doesn't support '-vf' as options,
> but it needs to be separated as '-v -f'.
> This package actually uses `prename`, not `rename`, which was only took
> over last month, which is why this FTBFS has been caught so late.
>
>> libxslt needed also to add "rename" as B-D, which I added in a recent
>> NMU.
>
> About that, next time please consider using the delayed queue, and for
> packages where I'm somehow involved consider also picking the unreleased
> changes from the git repositories :)

Sorry about that Mattia.  Since there almost no uploads in the last
year (other than fixes for old suites), and the FTBFS bug open for 2
or 3 weeks without replies, I thought that the package was a bit
behind in maintenance, so just followed the general NMU
recommendation.


>> I can also prepare an NMU for this package if it helps.
>
> On it, thanks for the buzz.

Great, thanks!


Cheers.
-- 
Manuel A. Fernandez Montecelo

Bug#875759: marked as done ([uim-chewing] Future uim-utils removal)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 10:18:42 +
with message-id 
and subject line Bug#875759: fixed in uim-chewing 0.1.0-5
has caused the Debian Bug report #875759,
regarding [uim-chewing] Future uim-utils 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.)


-- 
875759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uim-chewing
Version: 0.1.0-4
Severity: wishlist

uim maintainer team changed `uim` package from meta package to real package,
and removed uim-utils and integrated into `uim` package in experimental.

https://anonscm.debian.org/cgit/collab-maint/uim.git/commit/?h=debian-experimental=24ec7a1f9f817efa084ac57a4406ecdcc219a513
https://anonscm.debian.org/cgit/collab-maint/uim.git/commit/?h=debian-experimental=b1a39b2ee33402c8ae87a652f83e23cc6fb48296

So please depend `uim` package instead of `uim-utils` package
for `uim-module-manager` commmand.

We plan to upload `uim` to unstable within Sept.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: uim-chewing
Source-Version: 0.1.0-5

We believe that the bug you reported is fixed in the latest version of
uim-chewing, 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.
ChangZhuo Chen (陳昌倬)  (supplier of updated uim-chewing 
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, 15 Oct 2017 17:48:10 +0800
Source: uim-chewing
Binary: uim-chewing
Architecture: source
Version: 0.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 uim-chewing - Universal Input Method - Chewing plugin
Closes: 875759
Changes:
 uim-chewing (0.1.0-5) unstable; urgency=medium
 .
   * Change uim-utils and uim-common in Depends to uim for uim migration
 (Closes: #875759).
   * Bump Standards-Version to 4.1.1.
 * Update d/copyright Format to copyright-format 1.0.
   * Migrate from googlecode to GitHub.
 * Update d/control Homepage to GitHub.
 * Update d/copyright Source to GitHub.
 * Update d/watch to watch GitHub.
   * Update Vcs-* fields to use https.
   * Change ChangZhuo Chen's email to czc...@debian.org.
Checksums-Sha1:
 dae2870e97978a83c062ed96f9aaf091f4152639 2097 uim-chewing_0.1.0-5.dsc
 ebf2047210136b9253bda1b991656649872b5441 3648 uim-chewing_0.1.0-5.debian.tar.xz
 d280f5569bc2a07e8a4396dd6b05c1ba0fc06ea9 6056 
uim-chewing_0.1.0-5_source.buildinfo
Checksums-Sha256:
 f208f5b504937cfd48e9548c112c23392c7fa4fe0480428a756afad0fefad02e 2097 
uim-chewing_0.1.0-5.dsc
 bc55cc2231d1b6bb1a6789d85961de603aee60b2b3023b0fa43330ffe773ce3b 3648 
uim-chewing_0.1.0-5.debian.tar.xz
 a803cfface383d14adacb73f45e16c32d5a871e33ee8964a302589ecb9276be0 6056 
uim-chewing_0.1.0-5_source.buildinfo
Files:
 72b86d8271c8771bcdb185915cf5c9d8 2097 utils optional uim-chewing_0.1.0-5.dsc
 dfe4e167ecfc0d5816c5c14da0045e81 3648 utils optional 
uim-chewing_0.1.0-5.debian.tar.xz
 4bef74ceb0fadbfb919bc0ddbe459e6e 6056 utils optional 
uim-chewing_0.1.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEE5H9tOJ8ReWWaF1PGrc2MXdaTaQFAlnjL8IACgkQGrc2MXda
TaRiZw//Sw1ClsKFxPCabgNu1yd25XBHDQ93pV0rVVJ3JJyqzdMZS7tVOVL6HXpT
yFtG63gmZBDecnqtYe3RPLZH/TuXpqRhZdp3qWEDIyvIFPolvm2UtT3vZA1e9uSD
RWH+9VKsMwbapSbZpui94zgY94uAlso1/nBFj4wLApldd91CzLCKO0YQpGifkxjF
L5/GUGsTmC+DZrCBDZWLzqQiW0llGCyQHB3GFaCutEMkPCNkY2ky37ZHjpVCAb4p
ioD7uOOPA3WuuQI+Vx5BDd5cOxVn1T2HcQ7cWMk0coPSWRGjLqCMiIa1HlwQKtn0
HMqxmzK8cF2cPDVwFO/Zh+R2DqQZgxNqhFHkiNzKS8+D3IDsdWB3KDC9M9El/Z84
nlo/8kT/+6ZsN0kk23cBjxjthGQlw00mJ8fppYTivRFdgM7DIlq3HbtxJNS/zcHv
91F+xtFyFCcYoJPthP/tZ5/67e/5s3tyd8kjF+lUv4zGhSSpqnSMNpCDGUUTQM6W
eGhweCe6xYQGwRpiarXbLAi28wWN79sbCmMd9YTTCu/4NcFh/DiW84Zh8nClhnvt
xYH6cg0qRsb39FLv7RSPOht1Ua50mZE2iPbEfavbwaJl9214FvSSjskerum5w/0r

Bug#878633: python-pgpy FTBFS with more than one supported Python3 version

2017-10-15 Thread Adrian Bunk

Source: python-pgpy
Version: 0.4.3-2
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-pgpy-0.4.3'
LC_ALL=C.UTF-8 dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-pgpy-0.4.3/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest 
tests
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/_pytest/config.py", line 342, in 
_getconftestmodules
return self._path2confmods[path]
KeyError: 
local('/build/1st/python-pgpy-0.4.3/.pybuild/pythonX.Y_3.5/build/tests')

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/_pytest/config.py", line 373, in 
_importconftest
return self._conftestpath2mod[conftestpath]
KeyError: 
local('/build/1st/python-pgpy-0.4.3/.pybuild/pythonX.Y_3.5/build/tests/conftest.py')

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gpg/gpgme.py", line 14, in 
swig_import_helper
return importlib.import_module(mname)
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 985, in _gcd_import
  File "", line 968, in _find_and_load
  File "", line 955, in _find_and_load_unlocked
ImportError: No module named 'gpg._gpgme'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/_pytest/config.py", line 379, in 
_importconftest
mod = conftestpath.pyimport()
  File "/usr/lib/python3/dist-packages/py/_path/local.py", line 662, in pyimport
__import__(modname)
  File "/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py", line 212, 
in load_module
py.builtin.exec_(co, mod.__dict__)
  File 
"/build/1st/python-pgpy-0.4.3/.pybuild/pythonX.Y_3.5/build/tests/conftest.py", 
line 5, in 
import gpg
  File "/usr/lib/python3/dist-packages/gpg/__init__.py", line 101, in 
from . import core
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 34, in 
from . import gpgme
  File "/usr/lib/python3/dist-packages/gpg/gpgme.py", line 17, in 
_gpgme = swig_import_helper()
  File "/usr/lib/python3/dist-packages/gpg/gpgme.py", line 16, in 
swig_import_helper
return importlib.import_module('_gpgme')
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_gpgme'
ERROR: could not load 
/build/1st/python-pgpy-0.4.3/.pybuild/pythonX.Y_3.5/build/tests/conftest.py

E: pybuild pybuild:283: test: plugin distutils failed with: exit code=4: cd 
/build/1st/python-pgpy-0.4.3/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest 
tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.5 3.6" 
returned exit code 13
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25



Either #866555 needs fixing or as workaround the tests
should run only with the default python3 version.

Bug#878632: libfont-freetype-perl: FTBFS and Debci failure with libfreetype6 2.8.1-0.1

2017-10-15 Thread Adrian Bunk

Source: libfont-freetype-perl
Version: 0.07-1
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/libf/libfont-freetype-perl/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libfont-freetype-perl.html

...
Can't call method "bitmap" on an undefined value at t/20bitmap.t line 61, 
<$bmp_file> line 8.
# Looks like your test exited with 25 just after 12.
t/20bitmap.t ... 
1..21
ok 1 - bdf format font, glyph 0020: bitmap image matches
ok 2 - bdf format font, glyph 0020: bitmap starts 0 pixels to left of origin
ok 3 - bdf format font, glyph 0020: bitmap starts 6 pixels above origin
ok 4 - bdf format font, glyph 0041: bitmap image matches
ok 5 - bdf format font, glyph 0041: bitmap starts 0 pixels to left of origin
ok 6 - bdf format font, glyph 0041: bitmap starts 6 pixels above origin
ok 7 - bdf format font, glyph 00FE: bitmap image matches
ok 8 - bdf format font, glyph 00FE: bitmap starts 0 pixels to left of origin
ok 9 - bdf format font, glyph 00FE: bitmap starts 6 pixels above origin
ok 10 - bdf format font, glyph 2588: bitmap image matches
ok 11 - bdf format font, glyph 2588: bitmap starts 0 pixels to left of origin
ok 12 - bdf format font, glyph 2588: bitmap starts 6 pixels above origin
Dubious, test returned 25 (wstat 6400, 0x1900)
Failed 9/21 subtests
...
Test Summary Report
---
t/20bitmap.t (Wstat: 6400 Tests: 12 Failed: 0)
  Non-zero exit status: 25
  Parse errors: Bad plan.  You planned 21 tests but ran 12.
Files=7, Tests=2595,  1 wallclock secs ( 0.32 usr  0.02 sys +  1.14 cusr  0.12 
csys =  1.60 CPU)
Result: FAIL
Failed 1/7 test programs. 0/2595 subtests failed.
Makefile:1038: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255

Bug#878631: flightgear build depends on libsimgear-dev (<= 1:2017.2.999) but 1:2017.3.1+dfsg-1 is to be installed

2017-10-15 Thread Adrian Bunk

Source: flightgear
Version: 1:2017.2.1+dfsg-4
Severity: serious

The following packages have unmet dependencies:
 builddeps:flightgear : Depends: libsimgear-dev (<= 1:2017.2.999) but 
1:2017.3.1+dfsg-1 is to be installed

Bug#762638: Update on DFSG-freeness of perl/Configure

2017-10-15 Thread Dominic Hargreaves

Hi Helmut et al,

At the Perl 5 hackathon in Amsterdam[1], Niko and I have been working
on Configure maintenance with several other core developers (including
H.Merijn Brand, who has been the lead/only maintainer of Configure for
some years). The conclusions of these discussions are threefold:

1) the previous assertion on this ticket that Configure was, de facto,
*a* preferred form of modification was a misunderstanding on our side.
I have updated the header for Configure, and the information in
Porting/pumpkin.pod, upstream. Hence this bug being reopened.

2) an understanding of the the current mechanism for updating Configure
upstream has been shared amongst several people, and the documentation
has been improved both in the perl source and in the separate metaconfig
repository, which is now on github[2]. It is now much easier for a new
contributor to start working on this process upstream (and PRs are
welcome there).

2a) There is renewed interest in looking at the dist tools itself,
with a view to modernizing them. I'm not sure if the type of cross-building
work you might be interested in would be better done there or not. 

2b) One issue is that we are still using many older version of units
from the upstream dist package, as well as the perl-specific units, but
over time this divergence is being reduced.

3) the Debian perl package is in the process of being updated to
regenerate Configure in the build process by adding (parts of) the
repository to the perl source package as a separate component. Although
the upstream metaconfig.git contains a generated version of the tools
from dist, we are using the already-packaged version of dist in Debian
for this and this doesn't (substantially) change Configure at the moment.

I'm therefore hopeful that this bug will be resolved in more satisfactory
way very soon, and that this might prove a useful basis for your porting
work.

Best wishes,
Dominic.

[1] thanks to the sponsors for this event, listed at http://p5h.org/
[2]

Processed: Reopening the Configure discussion

2017-10-15 Thread Debian Bug Tracking System

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

> unarchive 762638
Bug #762638 {Done: Dominic Hargreaves } [src:perl] missing 
source: Configure
Unarchived Bug 762638
> reopen 762638
Bug #762638 {Done: Dominic Hargreaves } [src:perl] missing 
source: Configure
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions perl/5.22.0-3.
>
End of message, stopping processing here.

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

Bug#876739: marked as done (pyfai FTBFS: help2man: can't get `--help' info from /tmp/check_calib_0hk8odnh)

2017-10-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Oct 2017 06:23:35 +
with message-id 

and subject line RE:Bug#876739: pyfai FTBFS: help2man: can't get `--help' info 
from /tmp/check_calib_0hk8odnh
has caused the Debian Bug report #876739,
regarding pyfai FTBFS: help2man: can't get `--help' info from 
/tmp/check_calib_0hk8odnh
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.)


-- 
876739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfai
Version: 0.14.2+dfsg-1
Severity: serious

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

...
running build_man
INFO:pyFAI.setup:Build man for entry-point target 'check_calib'
INFO:pyFAI.setup:Build man for entry-point target 'detector2nexus'
INFO:pyFAI.setup:Build man for entry-point target 'diff_map'
INFO:pyFAI.setup:Build man for entry-point target 'diff_tomo'
INFO:pyFAI.setup:Build man for entry-point target 'eiger-mask'
INFO:pyFAI.setup:Build man for entry-point target 'MX-calibrate'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-average'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-benchmark'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-calib'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-calib2'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-drawmask'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-integrate'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-recalib'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-saxs'
INFO:pyFAI.setup:Build man for entry-point target 'pyFAI-waxs'
[298091 refs]
I: pybuild base:184: 
PYTHONPATH=/<>/pyfai-0.14.2+dfsg/.pybuild/pythonX.Y_3.6/build 
xvfb-run -a --server-args="-screen 0 1024x768x24" python3.6 setup.py build_man
INFO:root:Generating grammar tables from /usr/lib/python3.6/lib2to3/Grammar.txt
INFO:root:Generating grammar tables from 
/usr/lib/python3.6/lib2to3/PatternGrammar.txt
INFO:pyFAI.setup:Use setuptools
running build_man
INFO:pyFAI.setup:Build man for entry-point target 'check_calib'
help2man: can't get `--help' info from /tmp/check_calib_0hk8odnh
Try `--no-discard-stderr' if option outputs to stderr
Traceback (most recent call last):
  File "setup.py", line 868, in 
setup_package()
  File "setup.py", line 865, in setup_package
setup(**setup_kwargs)
  File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
  File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
  File "setup.py", line 248, in run
raise RuntimeError("Fail to generate '%s' man documentation" % target_name)
RuntimeError: Fail to generate 'check_calib' man documentation
E: pybuild pybuild:283: build: plugin custom failed with: exit code=1: 
PYTHONPATH=/<>/pyfai-0.14.2+dfsg/.pybuild/pythonX.Y_3.6/build 
xvfb-run -a --server-args="-screen 0 1024x768x24" python3.6 setup.py build_man
dh_auto_build: pybuild --build -i python{version} -p "3.6 3.5" returned exit 
code 13
debian/rules:18: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 25
--- End Message ---
--- Begin Message ---
This problem was due to this  

python-fabio (0.5.0+dfsg-2) unstable; urgency=medium

  * d/control
- python-qt4 -> python3-pyqt4-dbg (Closes: #876288)

Now that python-fabio was solved, it is ok to close this bug

thanks

Frederic--- End Message ---

Bug#876739: pyfai FTBFS: help2man: can't get `--help' info from /tmp/check_calib_0hk8odnh

2017-10-15 Thread PICCA Frederic-Emmanuel

This problem was due to this  

python-fabio (0.5.0+dfsg-2) unstable; urgency=medium

  * d/control
- python-qt4 -> python3-pyqt4-dbg (Closes: #876288)

Now that python-fabio was solved, it is ok to close this bug

thanks

Frederic

75 matches

Mail list logo