On Thu, Aug 23, 2018 at 07:39:13PM +0200, Mehdi Dogguy wrote: > On 2018-08-23 16:53, Nicolas Braud-Santoni wrote: > > On Thu, Aug 23, 2018 at 03:00:22PM +0200, Mehdi Dogguy wrote: > > > > It makes opam unusable for jessie users: already initialised ones can't > > > > install new compilers nor update packages, and with a fresh install opam > > > > is almost unusable (e.g. [3]). > > > > > > Unfortunately, we won't be able to upgrade Opam to 1.2.2 in Debian > > > stable. > > fwiw, I meant "oldstable" above. Yes, I didn't even notice the mistake :3 (i.e. I understood we were talking about jessie) > > > I can ask for its removal, or document in this bugreport how to > > > point their > > > installation to a frozen working mirror? > > > > Doesn't the release policy allow shipping a new upstream version to > > *-pu, if > > there is no other way to get the bug resolved (and after consulting the > > release > > team) ? Or is the issue that there won't be new point releases ? > > I am not sure what the Release Team would accept at this point (Jessie is > already EOL'ed). So, a sloppy-backport should be enough for oldstable > users. They can upgrade to stable if necessary. OK, that's fair enough; I had no idea whether there would be a point release in the future where we could have that put, or through LTS. Do you mind if I check with Ben? IIRC he does some LTS work, and I'm seeing him this weekend (at OMGWTFBBQ). > Once, 2.0 will be ready in Buster, Stretch users can use from backports. Yeap, I am very much planning to make a backport. Speaking of which, the version of opam in the packaging repo should be good-to-go, it's just blocked on someone sponsoring the upload; I asked highvoltage to do so, at the end of DebConf, but I guess he isn't very available currently, so fill free to review & dput if you feel like it. Worst case, I might get to upload 2.0 by myself within some weeks, at I'm currently going through the NM process. Best, nicoo
Attachment:
signature.asc
Description: PGP signature