[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#907042: marked as done (opam 1.2.0 is deprecated (jessie))

Your message dated Sat, 25 Aug 2018 02:41:24 +0200
with message-id <7b53f22d478bb418bc59aa54c685e00f@dogguy.org>
and subject line Re: Bug#907042: opam 1.2.0 is deprecated (jessie)
has caused the Debian Bug report #907042,
regarding opam 1.2.0 is deprecated (jessie)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
907042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907042
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: opam
Version: 1.2.0-1+deb8u1
Severity: grave
Justification: renders package unusable
Tags: jessie

Dear Maintainer,

On jessie, opam 1.2.0 is packaged but it is officially deprecated since
a year [1][2].

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]).

The solution is to upgrade the opam package to 1.2.2.

[1] https://opam.ocaml.org/blog/deprecating-opam-1-2-0
[2] https://discuss.ocaml.org/t/rfc-deprecating-opam-1-2-0/332
[3] https://github.com/astrada/google-drive-ocamlfuse/issues/324

Note: I talked with a maintainer who advised me to set severity to
grave.

------------------------------------
Versions of packages opam depends on:
ii  build-essential  12.3
ii  curl             7.52.1-5+deb9u6
ii  libbz2-1.0       1.0.6-8.1
ii  libc6            2.24-11+deb9u3
pn  opam-docs        <none>
ii  tar              1.29b-1.1
ii  unzip            6.0-21
ii  wget             1.18-5+deb9u2
ii  zlib1g           1:1.2.8.dfsg-5

Versions of packages opam recommends:
ii  aspcud     1:1.9.1-2+b1
pn  darcs      <none>
ii  git        1:2.11.0-3+deb9u3
ii  mercurial  4.0-1+deb9u1
ii  ocaml      4.02.3-9
ii  rsync      3.1.2-1+deb9u1

opam suggests no packages.

--- End Message ---
--- Begin Message --- 
Version: 1.2.2-5

On 2018-08-24 21:10, Nicolas Braud-Santoni wrote:

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).
I do not mind at all, of course. But just keep in mind we are talking about 
an EOL'ed oldstable. I'm not sure it is worth the trouble.
For now, I am marking this bug as fixed in Stretch (so that RC-bug squashers 
do not lose their time).
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.



I already uploaded 2.0, after a few fixes. It is sitting in NEW waiting
for approval.
I'd appreciate next time if you could ask for sponsorship within the OCaml 
team, especially for packages where there is another active maintainer.

--
Mehdi

--- End Message ---
Reply to: