Le 31/01/2019 à 12:34, Jö Fahlke a écrit : > Alright, pending Robert Klöfkorns opinion, I'm gonna attempt a draft > statement. We should get our move on, since Debian will stop accepting new > packages 2019-02-12[1], and renaming a package counts as a new package if I'm > not mistaken.
Right. But they are saying "no new package in testing for the next stable (Buster)", and to be in testing, a package has to go through the NEW queue (unpredictable amount of time), then unstable for at least 2 days (if we mark it as high priority), then testing. > [1] https://lists.debian.org/debian-devel-announce/2019/01/msg00008.html > > ---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT--- > > 1. Dune (numerics) does not see a good enough reason to stop dune (ocaml) > taking the /usr/bin/dune filename. > > 2. Dune (numerics) does not see a problem in dune (ocaml) using "dune" or > "libdune" in package names, as long as "ocaml" also appears in the package > name. > > ---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT---DRAFT--- This is nice. It would be wonderful if the Debian Technical Committee agrees with this statement (once it's official). I'm putting them in CC (via Debian bug #919951). > @Stéphane Glondu: Renaming the package was offered by Anil Madhavapeddy here: > https://lists.dune-project.org/pipermail/dune-devel/2019-January/002432.html > As the (visible) maintainer of Dune (ocaml) in Debian, do you consider this > feasible? Please let us know if not. It is possible in the long term. Note that reverse dependencies would also need to be changed. I don't know for Buster, though. At this stage, we would need approval from the release team (maybe a TC decision would help). Regards, -- Stéphane