On 4/2/21 5:19 AM, Sébastien Villemot wrote: > > Can you please clarify the situation regarding the above bug? > > As I understand it, /usr/bin/tetgen and its corresponding manpage are > provided by the tetgen package, which is *not* a dependency of > iso2mesh-tools. So there are installation scenarios where those symlinks may > be dangling. Hence the release critical bug.
hi Sébastien sorry, I was only able to see this bug today. the issue was caused by incorrect dependency, and it is now fixed in salsa https://salsa.debian.org/pkg-octave-team/octave-iso2mesh/-/commit/e2c128a60496d79de92cf41647d1b9f18a887860 Rafael, would you be able to review this change and upload? I assume we also need to update changelog. > But are those symlinks really needed in the first place? I could not find a > place in the package where “tetgen1.5” is called (with the version number as > a suffix). Only “tetgen” seems to be called. But maybe am I missing something. we noticed that the mesh output are not reproducible across different versions of tetgen. They also behave differently - some crash for certain input, some don't. therefore, in iso2mesh, we embedded different versions of iso2mesh and allow users to specifically choose using a flag in several core functions. Because debian only provides tetgen1.5 as tetgen, to allow some existing scripts/demos to run (at least), for example, in the octave-brain2mesh package https://salsa.debian.org/pkg-octave-team/octave-brain2mesh/-/blob/master/brain2mesh.m#L205 I need to create the tetgen1.5 link. let me know if there is a better solution. thanks Qianqian > > Thanks, >
