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. Kinds regards, Lisandro. -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. Dennis Ritchie Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.