On Tue, May 12, 2015 at 10:07 AM, Johannes Ring <joha...@simula.no> wrote: > On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel > <joachim.reic...@gmx.de> wrote: >> Hi, >> >> dolfin is now the only reverse dependency holding up the libcgal11 >> transition. >> >> What are the options? >> (1) Fix dolfin without causing another transition >> (2) Remove dolfin from testing >> (3) Upload 1.5.0-1 from experimental to unstable > > This will be the correct solution IMO. I will do that now.
Sorry for asking, but how should I upload to unstable when the package is already in experimental. I haven't done that before. Johannes > Johannes > >> (4) ...? >> >> (1) I don't know the details but it seems to me that this is not easy. >> >> (3) This causes another transition, but the only reverse dependencies of the >> binary packages of dolfin are python-viper (plus the meta packages fenics, >> science-mathematics and science-mathematics-dev). Rebuilding python-viper >> against dolfin 1.5.0-1 worked without problems. Maybe this additional >> transition >> isn't that bad (apart from the delay)? >> >> BTW does anyone understand why dolfin does not appear in the list of >> autoremovals? The bug is release-critical and not fixed in unstable/testing, >> only experimental. >> >> Joachim >> >> -- >> debian-science-maintainers mailing list >> debian-science-maintainers@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
