Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Markus Koschany Newsgroups: linux.debian.maint.java,linux.debian.bugs.dist Subject: Re: Bug#798343: libbcprov-java-doc: Package does not contain docs, api folder empty Date: Wed, 14 Oct 2015 20:50:02 +0200 Message-ID: References: X-Original-To: dean X-Mailbox-Line: From debian-java-request@lists.debian.org Wed Oct 14 18:41:57 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.58 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, GMAIL=1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, PGPSIGNATURE=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Reply-To: 798343@bugs.debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JXTqbdcOHQstOHOQxkbngbm4HevSx5pai" X-Sa-Exim-Scanned: No (on richard.fcube.de); SAEximRunCond expanded to false X-Mailing-List: archive/latest/18785 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/561EA1DF.8030207@gambaru.de Approved: robomod@news.nic.it Lines: 93 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-java@lists.debian.org, 798343@bugs.debian.org X-Original-Date: Wed, 14 Oct 2015 20:41:35 +0200 X-Original-Message-ID: <561EA1DF.8030207@gambaru.de> X-Original-References: <20150908100840.25545.10520.reportbug@debian> <5619CE0D.7020508@gmail.com> <5619CE0D.7020508@gmail.com> <561A55CC.6030508@gambaru.de> <561E37A0.3030708@gmail.com> Xref: csiph.com linux.debian.maint.java:8470 linux.debian.bugs.dist:686987 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JXTqbdcOHQstOHOQxkbngbm4HevSx5pai Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am 14.10.2015 um 13:08 schrieb dean: > On 10/11/15 22:27, Markus Koschany wrote: >> On Sun, 11 Oct 2015 12:48:45 +1000 dean =20 > Hi Markus and list, >=20 >> >> I think there is even a simpler way to change the source encoding. In >> Debian we normally use an ant.properties file for that. >=20 > bouncycastle is already using a bc-build.properties Would it be > appropriate to use that? Hi dean, that would probably work too. However you have to patch that file again because it is part of the upstream sources whereas an ant.properties file is part of Debian's packaging and can just be placed into the debian directory. >> A line like encoding=3DUTF-8 or compile.encoding=3DUTF-8 should do the= =20 >> trick. It should be even possible to drop the 01_build.patch but I=20 >> haven't tested this yet. >> >=20 > I originally looked at something like that but I could not make it work= =2E > I think something is setting file.encoding -> ANSI_X3.4-1968 > but I cannot find out where. I don't know a lot about bouncycastle but = I > believe they use different encodings in their source for a reason. >=20 > Any suggestions? I'm out of my league here. ANSI is the default encoding for your Java platform and if you want to have a specific encoding that is identical on all platforms you have to tell Ant about it, for instance you can use ant -Dfile.encoding=3DUTF-8 o= n the command line or you can use the already mentioned ant.properties file. I think we will fix this with the next revision of bouncycastle one way or the other. > ps. I CC'ed this to the list instead of the bug to keep the noise down > on the bug report while troubleshooting, I hope this was the right way = to go It's completely fine to reply to the bug report. We have a dedicated bug mailing list too and all your e-mails to the bug report are automatically forwarded to it. Keeping the bug report in CC also ensures that other interested parties can follow the conversation without having to subscribe to a dedicated mailing list like debian-java. Therefore I suggest to continue the discussion by only writing to the bug report. Cheers, Markus --JXTqbdcOHQstOHOQxkbngbm4HevSx5pai Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJWHqHfXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkcmEQAMrloqVwYXEvtlxQfVQ5qYSD RRuNCjEf4gdKV4gHVOOGl9+/fvPbJUQulKVSe0bhwgCtwuTGECVC6Ie3cCzFCQgS qtk73DyOxXLU3ShBrh4qfoJhJSISee4vhEvKR7jh3gAtX6TBBtRB0szjtkDNgStW f+7qufDXgIwgHD0uCovrJMImg20E4Q+zYXilNCuo4G+IW/eANnh6NGX41KWBAHC4 A3QG83QTqdXUQhrv/dNGn1QHOKKi/dDCEeh9drYwzUOD/MwO+YsZXGuABJOtBlsR 4/2HAH538cRvBh0cJYINE3LYdYfBfcAclWkKluh/6fEJj1JZ2y4bvEFazKc56z1G bDKL16WyVLpp9lNn+2ePeJhe0fi8dBqn+KcmV6IQXNThg/VW0gGcstrI2cY0Vo1T 64rHJGjkw6fvOr5TtsB738QGfRI/e3sNs4Pwzv1BgQG5Q/CbaeL5qzaYzD+G0dm+ Q2hoK1PelRXXTnzYiYKpQ88LIJAqrT6q2wi+4JEHT05J7dDKr588kkyzBID0JYbV PQslX8WVqb/o7nz1GwVvn984r1qV8gGjgRaPpz+wl0H4R1k7Sk4QI1Yi5vp7DtL1 K/0LGL5Ai7J+t9GAZ4OzxHPGUTFdGYVjITgZvQzomtcAk1x+RFQpIpMW/cHhYBMJ lBGvtviU8wZSPbXLFi0I =O6EY -----END PGP SIGNATURE----- --JXTqbdcOHQstOHOQxkbngbm4HevSx5pai--