[OCaml 3.11.2 transition][round 5/6] Please sync packages involved in OCaml transition from Debian (sid) to lucid (universe)

Bug #530305 reported by Stéphane Glondu
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
frama-c (Ubuntu)
Fix Released
Undecided
Unassigned
ocaml-batteries (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: frama-c

Hello,

Reminder: there is an OCaml transitition going on in lucid. Its progress can be monitored at:

  http://bentobako.org/ubuntu-ocaml-status/transition_monitor/ocaml_transition_monitor.html
  http://bentobako.org/ubuntu-ocaml-status/transition_monitor/ports_transition_monitor.html

Please sync the following package:

  frama-c (20090901+beryllium+dfsg-2 -> 20090902+beryllium+dfsg-4)

Note:this is a new upstream (minor) release. Most changes are in packaging (upstream as well as debian). Dependencies changed so that why now depends on frama-c (and not the other way around, as it was previously). It has been built successfully on all architectures in Debian, and is in testing. I hereby request a feature freeze exception.

Thanks in advance,

--
Stéphane

Revision history for this message
Stéphane Glondu (glondu) wrote :

The raw diff between both versions is very messy; I'm attaching the new changelog entries (both upstream and Debian).

Revision history for this message
Martin Pitt (pitti) wrote :

FF/Sync ack.

Changed in frama-c (Ubuntu):
status: New → Confirmed
Revision history for this message
Stéphane Glondu (glondu) wrote :

Can this sync be done soon? There remains (at least) why to be sync'ed with Debian to complete this transition.

Revision history for this message
Martin Pitt (pitti) wrote :

synced

Changed in frama-c (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Stéphane Glondu (glondu) wrote :

I've just added ocaml-batteries (0.20090405+beta1-5 -> 1.1.0-1).

The version currently in lucid was a beta release, and the upstream project changed quite a bit since then. That's why this version has been removed from squeeze [1]. There has been a new upstream release since them, that has been uploaded to sid yesterday. Currently, it has been built on all architectures that exist in Ubuntu [2].

I think that the package should be either synced or removed from Lucid before the beta1 freeze.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570488
[2] https://buildd.debian.org/status/package.php?p=ocaml-batteries

Revision history for this message
Martin Pitt (pitti) wrote :

> I think that the package should be either synced or removed from Lucid

Which do you think is the more appropriate option?

It currently has zero reverse dependencies, and its recent removal from Debian might indicate that it's not very well maintained/too much in flux. So would it be better to remove?

Changed in ocaml-batteries (Ubuntu):
status: New → Incomplete
Revision history for this message
Stefano Zacchiroli (zack-debian) wrote :

Hi, I'm the maintainer of ocaml-batteries in Debian. I believe that the release is stable enough to be released any time soon in a distro; the packaging is meant to be in good shape too. More importantly, I believe it would be totally inappropriate to release the *fomer* ocaml-batteries which was in Debian/unstable until a few days ago, as it is a line of developement which is completely abandoned now.

FWIW, let me remind you that currently no one from Ubuntu is helping out with OCaml package maintanance. On the Debian side we do our best to have sync stable for Ubuntu releases, but it would just be fair to have someone on the Ubuntu side help out, or at least come to us (our VCS and/or mailing lists) for specific information (like in this case).

Hope this helps,
Cheers.

Revision history for this message
Martin Pitt (pitti) wrote :

Thank you Stefano for following up here! Approved then.

Changed in ocaml-batteries (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

synced 1.1.0-1 from sid

Changed in ocaml-batteries (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.