Bug#896969: Bug#886865: Bug#896969: Info received (Bug#896969: Acknowledgement (nlohmann-json: Version 3.1.2 is now available - any reason not to update?))

[Gianfranco Costamagna]

control: retitle -1 "nlohmann-json: should it be removed from the archive?"

Hello, the new nlohmann-json3 has been uploaded a while ago from the archive, 
with compatibility
with newer toolchains and now all the reverse dependencies have switched to it, 
making this version useless wrt archive consistency

The package is now unmaintained upstream, and I personally don't find it useful 
anymore.

ssh coccia.debian.org dak rm -Rn nlohmann-json
Will remove the following packages from unstable:

nlohmann-json |  2.1.1-1.1 | source
nlohmann-json-dev |  2.1.1-1.1 | all

Maintainer: Muri Nicanor 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


I plan to request its removal in some hours if nobody complains!

(this plan has been announced previously with maintainers)

Muri, would you like to help the nlohmann-json3 maintainer if you like?
I'm already doing it, we can all help the new version instead of maintaining 
the old unmaintained one!

thanks,

G.

Bug#896969: Bug#886865: Bug#896969: Info received (Bug#896969: Acknowledgement (nlohmann-json: Version 3.1.2 is now available - any reason not to update?))

[Hubert Chathi]

On Mon, 30 Apr 2018 04:31:29 +0100, Wookey  said:

> On 2018-04-28 18:24 +0200, Muri Nicanor wrote:
>> Hi Wookey,
>> 
>> sorry for the delay- there is an ITP for nlohmann-json3
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886865

> Ah yes. Well, it looks like I've done that work 'accidentally' :-).

I've already uploaded the nlohmann-json3 package, and it's sitting in
NEW.  But looking at your patch, it looks like I missed a bunch of files
in debian/copyright, so I'll update that.  Thanks.

Do you want to be listed as a co-maintainer of this package?

> Should this conflict with nlohmann-json, so only one or the other can
> be installed? If both can be installed then they need different paths,
> and software will fail to find the headers unless it is modified to
> use a #include "nlohmann3/json.hpp" or similar.

I opted to install it as nlohmann/json.hpp, and add a conflict with the
nlohmann-json-dev package.

> If we go for that then a new nlohmann-json needs uploading which also
> conflicts with nlohmann-json3.

> nlohmann-json3 provides both a single-file interface and a
> multiple-file interface.

> horizon-eda expects the multiple-header interface (it includes
> nlohmann/json_fwd.hpp as well as nlohmann/json.hpp). I don't know this
> package well enough to know whether providing the multiple-header
> interface works for all the programs that expect to just include
> nlohmann/json.hpp and get everything?

I'm not familiar enough either, but from my quick glance, it looks like
it should work, as json.hpp in the multi-header version seems to include
everything else.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368