* Package name : visit Version : 1.5.4.060918 Upstream Author : Lawrence Livermore National Laboratory - University of California * URL : http://www.llnl.gov/visit/ * License : 3-clause BSD license with additional disclaimers (http://www.llnl.gov/visit/license.html) Description : interactive parallel visualization and graphical analysis tool VisIt is a free interactive parallel visualization and graphical analysis tool for viewing scientific data. Users can quickly generate visualizations from their data, animate them through time, manipulate them, and save the resulting images for presentations. VisIt contains a rich set of visualization features so that you can view your data in a variety of ways. It can be used to visualize scalar and vector fields defined on two- and three-dimensional (2D and 3D) structured and unstructured meshes. VisIt was designed to handle very large data set sizes in the terascale range and yet can also handle small data sets in the kilobyte range. Supported input data formats: * ANALYZE * ANSYS * BOV (brick of values) * Boxlib * CGNS * Curve2D * Ensight Gold * Enzo * Exodus * FITS * FLASH * FLUENT * FVCOM * GIS * Image * NASTRAN * NetCDF * OpenFOAM * PATRAN * PLOT3D * Protein Databank * SAMRAI * Silo * Spheral * STL * TecPlot * Vis5D * VTK * Wavefront OBJ * Xmdv * ZeusMP (HDF4)
Please note that I've already asked debian-legal to confirm that the license is suitable for a package in main. The thread starts at: http://lists.debian.org/debian-legal/2006/10/msg00209.html So far there have been no objections... :-)
Hi all, is anyone interested in packaging VisIt for Debian? Please see RFP bug #395573 [1] (which I'm Cc:ing). To get an idea of what this visualization tool is capable of, you could take a look at its gallery [2]. I think the images are quite impressive and speak for themselves. [1] http://bugs.debian.org/395573 [2] http://www.llnl.gov/visit/gallery.html Please Cc: me *and* the bug on replies, thanks.
Sounds great. Added it to the WML page of Debian-Med imaging todo list.
Many thanks for the hint
Andreas.
Good! Let's hope that some DD pops up soon volunteering to package VisIt (mmmh, what about... you?!? ;-) [...] Debian! P.S.: I am not a debian-med list subscriber, hence please Cc: me *and* the bug on replies, thanks.
For anyone interested in packaging VisIt
[ raise your hands, one at a time, please! ;-) ]
I gave a look at <http://www.llnl.gov/visit/source.html> and
and at <http://www.llnl.gov/visit/1.6.1/BUILD_NOTES>
It seems to me that VisIt has the following mandatory
build-dependencies:
* Mesa 5.0 http://packages.debian.org/libgl1-mesa-dev
* Mesa 6.4.2 http://packages.debian.org/libgl1-mesa-dev
* Python 2.5 http://packages.debian.org/python
* Qt X11 3.3.2 http://packages.debian.org/libqt4-dev
* Qt X11 3.3.8 http://packages.debian.org/libqt4-dev
* Silo060605 not in Debian?
* VTK 5.0.0c http://packages.debian.org/libvtk5-dev
Moreover, it seems to have some optional build-dependencies (libraries
that may be linked or else left out, IIUC):
* Boxlib 2.5 not in Debian?
* CFITSIO 3006 http://packages.debian.org/libcfitsio3-dev
* CGNS 2.4-3 not in Debian?
* ExodusII 4.46 not in Debian?
* GDAL 1.3.2 http://packages.debian.org/libgdal1-dev
* H5Part 1.3.3 not in Debian?
* HDF4 2.4.1 http://packages.debian.org/libhdf4g-dev
* HDF5 1.6.5 http://packages.debian.org/libhdf5-{serial|lam|mpich}-dev
* NetCDF 3.6.0 http://packages.debian.org/netcdfg-dev
I thought I should share these findings...
Hello, This is an automatic mail sent to close the RFP you have reported or are involved with. Your RFP wnpp bug is being closed because of the following reasons: - It is, as of today, older than 365 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be closing some bugs that are not intended by owners and submitters (like you) to be closed, for example if the RFP is still of your interest, or there has been some kind of activity around it. In that case, please reopen the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily reopen their bugs ;-). To re-open it, you simply have to mail control@bugs.debian.org with a body text like this: reopen 395573 stop Further comments on the work done in the bug sent to 395573@bugs.debian.org would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <damog@debian.org>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation,
reopen 395573 stop I am still interested in seeing this piece of software included in Debian. I hope that someone will soon be willing to package it...
block 395573 by 501924 thanks Hi, I am currently working on the packaging of cgns which is reported as being one of the dep of visit. It is available on debian-science: http://svn.debian.org/viewsvn/debian-science/packages/libcgns/trunk/ Sylvestre
Hi, You submitted an RFP for VISit in Debian. Have you done any work on this? we use VISit at work, and I would like to package it for Debian-Meteorology. Regards Alastair McKinstry
Hi there! :) Not really, I have little packaging experience and I do not (yet) feel to be ready for debianizing VISit. I would be *really* happy to see it packaged and included in Debian! Thank you very much for volunteering to do this job! :-) Feel free to convert this RFP into an ITP, if you like. Bye and thanks again.
Hi! How's the packaging of VisIt going? Is there any progress? Have you already packaged (or helped others packaging) the missing dependencies? Please let me know.
Again, any news?
Hi, Sorry about the delay in responding. I've been busy packaging various dependencies (of other packages, not just visit). Currently I've two issues: (1) packaging the SILO library needed by VISIT. See ftp://ftp.llnl.gov/pub/visit/3rd_party/silo060605.sh (2) Visit appears to need VTK 5.0.0c, while 5.2 is in Debian unstable. I'm working on this now and hope to have it done over the next two eeeks. Regards Alastair
That's OK, I was just worried that you could not receive mail... Yeah, that's the only mandatory dependency that's currently missing from Debian, AFAIK. As an aside, please note that, among the optional dependencies, libcgns is now included in Debian: see bug #501924 and http://packages.debian.org/libcgns I think that everything possible to make VisIt work with VTK 5.2.x (and then 5.4.x) should be done. I don't know whether upstream is willing to help with this task: I hope so, since they are more and more out of date with VTK versions... Wonderful! I am really looking forward to see an upload to unstable (or even a temporary test package). Thanks for the update and please keep up with the good work! ;-)
Hi, I've been looking at packaging SILO, a mandatory dependency of VisIt. Unfortunately, it contains the following license clause: Commercialization of this product is prohibited without notifying the Department of Energy (DOE) or Lawrence Livermore National Laboratory (LLNL). AFAIK, this is a show-stopper for packaging VisIT. We could write to LLNL and see if they are willing to relinquish this, but since I started this ITP, Paraview has been packaged for Debian, and it does my visualisation needs, so I am no longer packaging visit. Sorry about this, Alastair
retitle 395573 RFP: visit -- interactive parallel visualization and graphical analysis tool noowner 395573 thanks Hi! This seems to be very awkward: a Free Software application (VisIt) which links with a non-free library (Silo) by the same authors! :-( I think this should definitely be done. I am not especially enthusiast of Paraview, which ships with its own internal copy of VTK (see bug #495426) and hence does not automatically benefit of any fix or enhancement is applied to the Debian vtk package... Anyway, if Paraview satisfies you, nobody forces you to package VisIt, of course. It's a pity that we found out this after so long time since you turned this RFP into an ITP... :-( The commands at the beginning of this message should convert this ITP back into an RFP. Bye.
On Sat, 31 Oct 2009 23:34:31 +0100 Francesco Poli wrote: [...] [...] find any grant of permission in the Silo tar archive: this would imply that Silo is legally undistributable by anyone other than its copyright holders... :-(
Hi, In the BUILD_NOTES for visit 1.12.0, it says: It then goes on to list the optional readers. This made it seem like a compulsory element. I'm glad to hear it is no longer necessary, and can continue to build VisIt for Debian. Thanks Alastair Regards, Alastair
Ok, thanks for this info. We'll correct the build notes. Mark -- Mark C. Miller, Lawrence Livermore National Laboratory email: mailto:miller86@llnl.gov (M/T/W) (925)-423-5901 (!!LLNL BUSINESS ONLY!!) (Th/F) (530)-753-8511 (!!LLNL BUSINESS ONLY!!)
On Sat, 31 Oct 2009 23:34:31 +0100 Francesco Poli wrote: [...] [...] [...] I got in touch with Silo's upstream. They quickly replied in an encouraging manner. First thing they told me is that Silo is no longer a mandatory dependency for VisIt: they say it's been an *optional* dependency for quite some time. Alastair, did you try building VisIt without enabling the Silo plugin? I think VisIt could be packaged for Debian (main) with the Silo plugin disabled, while we wait for upstream to re-license Silo in a DFSG-free manner... Does it sound feasible? your willingness to package VisIt? Please let me know: thanks in advance.
Hi, I contacted VisIt's upstream (via visit-users list) and found the same thing; they are correcting the build notes that claim Silo is needed. I hadn't tested it without Silo. I'm trying to build it now, but Visit 1.12.0 needs VTK 5.0.0c : I tested against vtk 5.2 which is in Debian, and they're incompatible; LLNL ship a VTK 5.0.0.c (with changes) tarball to build VisIt with; it doesn't build on Debian, so back to working on the necessary fixes for visit 1.12.0 with Debian's VTK. (Some of these may be in the repo for visit ; they are currently working on visit 2.0 upstream, but I'm not sure it would be ready for Squeeze). I need to resign up to ITP visit. Regards Alastair
Great! :-) Ouch! :-( This is unfortunate. Do you feel that many invasive changes are needed? Where's the repository for VisIt? I seem to be unable to find it by reading the official website. Which VCS do they use? it. Do you have a preliminary package somewhere? Do you feel it could be used as a base for further hacking?
Hello debian-science and debian-med lists, is there anyone willing to package VisIt for Debian? My RFP (see bug #395573) was converted into an ITP, but later was converted back into an RFP... I still think VisIt is an interesting visualization and graphical analysis tool: the Debian distribution would benefit from having it included, in my opinion. Please Cc: me *and* the bug on replies, thanks.
Am Montag, den 23.11.2009, 00:10 +0100 schrieb Francesco Poli: I did not know about that but started packaging it a while ago. The files are surely around somewhere for those interested. I remember having a lot of trouble with it for several reasons. IIRC it was some weird build system and included libraries to get rid of. I will not have any time to have a second look at it before next month, I guess, but could dig for the files if there's interest. They probably do not build anything working, I guess. Even if I give it a second try to package, some co-maintainer would certainly be welcome; even better, someone who would take over maintainership. Done. Best regards Manuel
Hi Alastair! Is there any progress on the packaging of VisIt? Could you please provide a status update?
Unfortunately I've been swamped with work (and expect to be so for the next 3 months). I don't expect to get time to get Visit packaged in time for Debian squeeze - I'm concentrating on cleaning up my packages currently in Debian Squeeze, and adding one more - oasis, which is a library needed as a dependency for day-to-day work in my job. I hope to get back to it after April. If you can step in, please do.
[...] [...] [...] Hi again, did you manage to dedicate some time to VisIt? I noticed that version 2.0.0 has been released. Does it build with recent VTK?
[...] [...] After a bit of persuading by some people (including me!), and after a long re-licensing process, Silo is now Free Software under a 3-clause BSD license: see the September 20, 2010 release notes at <https://wci.llnl.gov/codes/silo/release_notes.html> and the Silo-4.8-bsd*tar.gz downloads at <https://wci.llnl.gov/codes/silo/downloads.html> Unfortunately a couple of compression features were not re-licensed and hence the Free version of Silo lacks some compression capabilities (again, see the release notes). Anyway, the rest of the library now does comply with the DFSG! :-) This means that we are now looking for someone who volunteers to package the Silo library! ;-)
On 2010-10-10 18:43, Francesco Poli wrote: Congrats! I've filed the ITP, but the actual packaging may take place after squeeze. Life is a little busy just now, but I'll get Visit packaged! - Alastair
On Sun, 10 Oct 2010 20:27:48 +0100 Alastair McKinstry wrote: [...] Thanks, but I think you should really send congratulations and thanks to LLNL for freeing Silo: I've just done some little "pushing" in the right direction... ;-) This is terrific news, indeed! :-) Thank you very much for volunteering to package Silo! For those who read this bug report on the BTW web interface, the ITP is http://bugs.debian.org/599747 Wow! That's terrific news, for the second time! :-) Did you manage to solve the issues with up-to-date versions of VTK? Does VisIt work with current VTK?
Hi, I've added a wiki page to describe the current state of packaging: http://wiki.debian.org/DebianScienceVisitPackaging I will be uploading the work in progress to a VCS within Debian. Regards, Alastair
Hi Alastair! impressed! It seems that things are really progressing now. I cannot stress enough how much I am happy to read such an update. Thank you very much for your time and for your efforts: they are *really* appreciated! Looking forward to seeing VisIt included in Debian! Bye.
[...] Hi again Alastair, any news on this front? I haven't seen much progress on the Debian wiki page lately... But a quick look at http://www.visitusers.org/index.php?title=VTK_Upgrade seems to suggest that most (if not all) the showstoppers on the VTK side are gone... Or am I completely off-track? Have you tested VisIt with libvtk* version 5.8.0-13 (currently in unstable and testing) or version 5.9.0-1 (currently in experimental)? Please let me know...
Hi, Is there any news on the Visit packaging ? Did you find the time to put your work on a VCS ? On the wiki page, I see no blocking stuff to prevent Visit to be packaging for Debian, so I wonder if it's still the case. Regards, Adrien
Hi, No, I've just been delayed by trying to finish my PhD ... There was some work in progress to merge / update VTK so that VisIT/Paraview did not use their own version, which I will need to revisit. I should at least put my work in alioth,etc so someone else could take over. regards Alastair
retitle 395573 RFP: visit -- interactive parallel visualization and graphical analysis tool noowner 395573 tag 395573 - pending thanks Hi, A long time ago, you expressed interest in packaging visit. Unfortunately, it seems that it did not happen. In Debian, we try not to keep ITP bugs open for a too long time, as it might cause other prospective maintainers to refrain from packaging the software. This is an automatic email to change the status of visit back from ITP (Intent to Package) to RFP (Request for Package), because this bug hasn't seen any activity during the last 12 months. If you are still interested in packaging visit, please send a mail to <control@bugs.debian.org> with: retitle 395573 ITP: visit -- interactive parallel visualization and graphical analysis tool owner 395573 ! thanks It is also a good idea to document your progress on this ITP from time to time, by mailing <395573@bugs.debian.org>. If you need guidance on how to package this software, please reply to this email, and/or contact the debian-mentors@lists.debian.org mailing list. Thank you for your interest in Debian,
This is a note to say I have been working on visit packaging, but am unlikely to complete before December due to completing a PhD. VisIt packaging has been mostly delayed awaiting vtk6 to be properly integrated and packaged in Debian (thus not requiring a separate visit-vtk). I have uploaded my work to date to alioth.debian.org (pkg-visit) where is can be downloaded via git.debian.org:/git/pkg-visit/pkg-visit.git regards Alastair McKinstry
It seems that the git repository pkg-visit is no longer accessible. Could you confirm? Best C
[...] Dear Alastair, could you please help Christophe Trophime and me in finding the git repository where you uploaded your packaging work? I could not find it listed in https://anonscm.debian.org/cgit/ I did find: https://alioth.debian.org/projects/pkg-visit/ but the "SCM Repository" link takes me to https://alioth.debian.org/scm/?group_id=100926 which is apparently accessible for alioth registered users only. This is strange... After logging in to Alioth, I could view the page describing the access to the git repository: it mentions the "Developer Git Access via SSH", which is claimed to be for project developers only, and then illustrates the "Git Repository Browser" with a link to https://alioth.debian.org/scm/browser.php?group_id=100926 which, however, shows a 404 - No such project Now I am really puzzled: where is the git repository? :-/ Please let us know. Thanks for your time!
Hi, Its available at: ssh://git.debian.org/git/pkg-visit/pkg-visit.git Most of the work was slightly outdated by the vtk5->vtk6 transition so I would be able to recreate it again when I get down to work post-jessie, but not right now. regards Alastair
On Mon, 24 Nov 2014 11:49:08 +0000 Alastair McKinstry wrote: [...] [...] I seem to be unable to find it: $ git clone ssh://git.debian.org/git/pkg-visit/pkg-visit.git Cloning into 'pkg-visit'... fatal: '/git/pkg-visit/pkg-visit.git' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Please note that I can access git.debian.org via SSH: $ ssh git.debian.org uname -a Linux moszumanska 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux Where am I going wrong?
repository for your packaging work? Please reply. Thanks for your time!
Yes. I plan to get visit into Stretch, as it is a requirement for the UV-CDAT analysis package, which is one of my main goals for stretch. The main blocker for jessie was VTK6, which I think is (nearly?) resolved. Visit depends on VTK6 It was not meant to be private, so i've CC'd the bug address. regards Alastair
[...] This is really wonderful news! :-) Thanks a lot for confirming. Please don't forget to change back the RFP bug report to an ITP one, when you feel it's time to do so. Debian jessie has vtk6/6.1.0+dfsg2-6, are you waiting for something that is fixed in vtk6/6.2.0+dfsg1-1 (currently in NEW)? [...] Bye.
Hi Alastair, since I was pointed to visIt by our cosmologists: what is the status of the packaging? It looks like you restarted this two years ago, but then abandoned it. What were the difficulties, and what is the current status? http://www.llnl.gov/visit/ https://anonscm.debian.org/cgit/debian-science/packages/visit.git Best regards Ole
Hi Steffen, Sorry for taking so long to respond. Packaging VisIt was delayed waiting for 'the correct VTK' to be packaged for Debian. I also haven't had much time to pay attention to this; I still wish to see VisIt packaged as it is a dependency of CDAT which I'd like to see in Debian. Currently VTK6 is present which should work, with VTK8 being packaged for buster. What branch are you using ? my latest branch (debian/master) should be based off 2.12.3, and refers to python- instead of python3 until python3-vtk? is provided. It doesn't build yet, but I can work with you to get it working. Best regards Alastair
Hi, I am interested to have visit for Debian Stretch. So I took the work you've done and tried to compile visit 2.12.3 on Debian Stretch. My work is here, feel free to use it: https://github.com/LHEEA/debian-visit Cmake now configure correctly the package, but I got compilations errors, which should be solved according to visit's wiki: https://www.visitusers.org/index.php?title=VTK_6.3_Upgrade Unfortunately I will not have time to finish the packaging… So if anyone have time to continue the work to have a proper package which compiles, please contribute… My patches are also quite dirty, sorry for that. Kind regards, Adrien
Hi, I am interested to have visit for Debian Stretch. So I took the work you've done and tried to compile visit 2.12.3 on Debian Stretch. My work is here, feel free to use it: https://github.com/LHEEA/debian-visit Cmake now configure correctly the package, but I got compilations errors, which should be solved according to visit's wiki: https://www.visitusers.org/index.php?title=VTK_6.3_Upgrade Unfortunately I will not have time to finish the packaging… So if anyone have time to continue the work to have a proper package which compiles, please contribute… My patches are also quite dirty, sorry for that. Kind regards, Adrien
Hi, I finally got through the compilation's errors. So if you take my repo, you should be able to build into sbuild a deb package for visit. It does build with python2 and Qt5. Be careful, it doesn't respect the Debian way at all : The FHS is not respected and some libraries are bundle in it (gfortran, etc.). I have build only one big .deb, but it may be split (python-visit, visit-dev, etc.). I also had to disable some functionalities in visit (HDF5, Silo, GDAL), BoxLib, as it triggers some compilation's errors. It is sufficient for our internal needs, so I won't invest more time in it. But if anyone wants to bring visit into Debian, feel free to use my work, it could be a start. Kind regards, Adrien
Hi, I finally got through the compilation's errors. So if you take my repo, you should be able to build into sbuild a deb package for visit. It does build with python2 and Qt5. Be careful, it doesn't respect the Debian way at all : The FHS is not respected and some libraries are bundle in it (gfortran, etc.). I have build only one big .deb, but it may be split (python-visit, visit-dev, etc.). I also had to disable some functionalities in visit (HDF5, Silo, GDAL), BoxLib, as it triggers some compilation's errors. It is sufficient for our internal needs, so I won't invest more time in it. But if anyone wants to bring visit into Debian, feel free to use my work, it could be a start. Kind regards, Adrien
Hi Alastair, Are you still working on visit packaging for Debian? I'm very interested in the package. However I fail myself to get it built at all from source... Regards,
Hi, Sorry about the delay in repsonding. I'm not currently actively working on visit; (I did some checks this week). You can see my current work at: https://salsa.debian.org/science-team/visit/tree/debian/master Basically, VisIt doesn't build against VTK6 or VTK7 as in Debian at the moment. I had been waiting on changes to VTK (There was a plan possibly to move to VTK8), but this has stalled; (See https://www.mail-archive.com/search?l=debian-science@lists.debian.org&q=subject:%22Re%5C%3A+Skip+VTK7+and+go+directly+VTK8%5C%3F+Was%5C%3A+Re%5C%3A+vtk6+and+vtk7%22&o=newest&f=1) It appears that work on VTK 7 / VTK8 has stalled due to lack of need for a new VTK8 from other users in Debian. If I get the time, I might investigate what needs to be done, but this is unlikely at the moment, Regards Alastair
Dear friend, Good day to you and your family. Please, I need to know if your email is still valid?. I have a very important proposal for you in regarding a fund with your name in a financial company, I cannot disclose more about this funds until i hear from you again, sir. Once I hear from you, I will furnish you with more information's. Get back to me with your name and telephone number urgent. I hope to hear from you soon. Mr. James Ben White & Will Chen. 538 Rush Green Road, Romford RM7 0LX. UK
meanwhile versions 3.0.0, .1, .2 are out, I'm failing to build them as they want VTK 8.1, but only 7.x is in unstable, and 8.2 on salsa.d.o best,
Did you received my mail or should I resend it?