Bug#640195: Remove paraview-dev

[Mathieu Malaterre]

2011/9/12 Lisandro Damián Nicanor Pérez Meyer <perezmeyer at gmail.com>:
> On Dom 11 Sep 2011 06:00:39 Mathieu Malaterre escribió:
> [snip]
>> > Now ParaViewConfig.cmake should be installed by paraview-dev. To help the
>> > transition, all the packages that currently build-depend on paraview
>> > should be filled a normal bug, raised to important in ~3 or 4 weeks and
>> > then to serious ~3 or 4 weeks later. It is customary to user-tag the
>> > bugs so as to follow the transition.
>>
>> Great. We'll keep this bug open as serious to prevent transition to
>> testing. Is that an acceptable solution or should I fill a ROM request
>> and re-upload paraview to experimental ?
>>
>> > After that is achieved, src:paraview can be uploaded with the dev package
>> > providing the header files and ParaViewConfig.cmake.
>>
>> As said above, paraview is already in unstable. I need a little more
>> time to test vtkedge and other package that build paraview plugins.
>
> First of all, sorry for the late reply.
>
> Well, it seems you are in the middle of a not well handled transition.
> I have found that there are several .cmake files in paraview wich should be in
> paraview-dev.
>
> Removing the package from unstable will cause the packages that build-depend
> on it FTBFS. So I guess the best thing wich can be done is simply move the
> cmake files to -dev, try to build whichever package B-Ds on paraview/paraview-
> dev and report FTBFS if necessary.
>
> I'm CCing debian-science to let more experienced people give their opinion.

Just FYI. *.cmake files have been moved to paraview-dev, if you take
the latest from git.
What is left to do is:

http://anonscm.debian.org/gitweb/?p=debian-science/packages/paraview.git;a=blob;f=debian/TODO;h=9c6efbc305b86826c5bb93abb606e11fc6180316;hb=8dab8a9a0a7db7a0360caafb4ab88352e1b6edcb

We will keep paraview 3.10-* in unstable until all issues are solved.

Thanks,
-- 
Mathieu