Re: Looking for advice about json-simple 3 transition
Hello, On 2020-05-13 16:46, Gilles Filippini wrote: > I'd like to push json-simple 3.1.1 into unstable, but I'm not sure how I > should handle the transition. The 3.x releases are not backward > compatible with 2.x. > > A whole set of deprecated classes has been removed: >> * Deprecated JSONParse and JSONValue in favor of Jsoner. >> * Deprecated JSONStreamAware and JSONAware in favor of Jsonable. >> * Deprecated JSONObject in favor of JsonObject. >> * Deprecated JSONArray in favor of JsonArray. Maybe it wouldn't be too difficult to patch the dependencies to work with 3.x release? There are ~15 source packages, so I'd say it should be doable provided the API changes are not too drastic. This would allow to retain the same binary package name. > I think about renaming the binary package to libjson-simple1-java but > keeping the jar file name as json-simple.jar. It implies setting > Conflicts: libjson-simple-java. Name libjson-simple3-java would be better, as it reflects the upstream version. However, I would recommend against having conflicting JAR names, as this would effectively forbid coexistence of packages depending on different versions of json-simple. If having both v2 and v3 JARs could not be avoided, I'd suggest providing /usr/share/java/json-simple-2.x.jar in libjson-simple-java and /usr/share/java/json-simple-3.x.jar in libjson-simple3-java. Packages junit [1] and junit4 [2] are made to coexist in a similar manner. [1] https://packages.debian.org/sid/all/junit/filelist [2] https://packages.debian.org/sid/all/junit4/filelist Hope this helps, Andrius signature.asc Description: OpenPGP digital signature
Re: Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))
On Wed, May 13, 2020 at 08:33:07PM +0200, Thorsten Glaser wrote: > > I remember times when such a web page (actually some autogenerated text > > file) existed which was **extremely** helpful. I wished this would be > > back! > > > > > … I just volunteerd, didn’t I? > > Here you are: > > https://wiki.debian.org/Java/MavenPkgs Looks pretty helpful! > Sponsored by ⮡ tarent, see below. Thanks! > This is step 1, the list of all Maven packages ⇒ Debian package name. > It doesn’t go as far as to map Java packages or even classes… yet. > For this I’d have to download all those packages, extract them and > look into the JARs. I’d prefer some central service to offer archive > contents if possible (diffoscope already extracts archives anyway). Sounds very promising. Thanks a lot Andreas. -- http://fam-tille.de
Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))
On Wed, 6 May 2020, Andreas Tille wrote: > > Or perhaps we need a webpage or wiki page generated by parsing the > > Contents file and listing the matching Debian package for each class > > or, at least, Java package (unless split across multiple packages)… > > I remember times when such a web page (actually some autogenerated text > file) existed which was **extremely** helpful. I wished this would be > back! > > > … I just volunteerd, didn’t I? Here you are: https://wiki.debian.org/Java/MavenPkgs Sponsored by ⮡ tarent, see below. This is step 1, the list of all Maven packages ⇒ Debian package name. It doesn’t go as far as to map Java packages or even classes… yet. For this I’d have to download all those packages, extract them and look into the JARs. I’d prefer some central service to offer archive contents if possible (diffoscope already extracts archives anyway). bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Looking for advice about json-simple 3 transition
Hi, I'd like to push json-simple 3.1.1 into unstable, but I'm not sure how I should handle the transition. The 3.x releases are not backward compatible with 2.x. A whole set of deprecated classes has been removed: > * Deprecated JSONParse and JSONValue in favor of Jsoner. > * Deprecated JSONStreamAware and JSONAware in favor of Jsonable. > * Deprecated JSONObject in favor of JsonObject. > * Deprecated JSONArray in favor of JsonArray. I think about renaming the binary package to libjson-simple1-java but keeping the jar file name as json-simple.jar. It implies setting Conflicts: libjson-simple-java. I'm reluctant to change the jar file name, to keep consistancy with upstream naming. Would this be acceptable? Thanks in advance for you inputs, _g. signature.asc Description: OpenPGP digital signature
