Our current version of ds9 has various problems. 1) It fails to open the TCL console: File -> Open TCL Console An error message appears 2) It fails to open VOT catalog. Test file attached. Analysis -> Catalog Tool -> File -> Open -> test.vot nothing happens.
Created attachment 12912 [details] A vot catalog file
ds9 updated to latest bug fix release 8.2.1, and fixing the above mentioned issues. To test, follow the bug report, the new version should work. Suggested advisory: ======================== Updated ds9 package to version 8.2.1 fixing a fatal issue in opening VOT catalogs. Updated packages in core/updates_testing: ======================== ds9-8.2.1-2.mga8 Source RPMs: ds9-8.2.1-2.mga8.src.rpm
CC: (none) => eatdirtAssignee: eatdirt => qa-bugs
Installed these: 1/8: tcl-tcllib ############################################# 2/8: tcl-tclxml ############################################# 3/8: lib64xpa1 ############################################# 4/8: xpa-tcl ############################################# 5/8: tcltls ############################################# 6/8: tcl-xmlrpc ############################################# 7/8: tkblt ############################################# 8/8: ds9 ############################################# $ rpm -q ds9 ds9-8.2-2.mga8 $ ds9 Error in startup script: couldn't load file "/usr/lib64/tcl8.6/tclxpa/libtclxpa.so": /usr/lib64/tcl8.6/tclxpa/libtclxpa.so: cannot open shared object file: No such file or directory while executing "load /usr/lib64/tcl8.6/tclxpa/libtclxpa.so" ("package ifneeded tclxpa 2.1" script) invoked from within "package require tclxpa" (file "/usr/share/ds9/mntpt/library/ds9.tcl" line 222) $ rpm -q tcl tcl-8.6.10-2.mga8 $ rpm -q lib64xpa1 lib64xpa1-2.1.20-1.mga8 $ rpm -q xpa-tcl xpa-tcl-2.1.20-1.mga8 $ locate libtclxpa.so /usr/lib64/tcl8.6/tclxpa/libtclxpa.so.1 /usr/lib64/tcl8.6/tclxpa/libtclxpa.so.1.0 Added the missing link: # ln -s libtclxpa.so.1 libtclxpa.so After that the ds9 interface appeared. "Open TCL Console" failed Downloaded the sample file. Followed the procedure as far as Open -> test.vot and sure enough nothing happened. Exited cleanly. Installed the update candidate and tried again. The TCL console opens: buffer line limit: 512 ..... Opened the sample vot file using the Analysis -> Catalog Tool, which showed NUMBER, ALPHA, DELTA.... columns of data. Forgot to remove the library link. Moved to another machine and installed ds9 and dependencies. ds9 failed. Installed the update and ds9 failed again with the same error. So this is good to go but waiting for advice on how to proceed. Should the update be withdrawn and resubmitted after the symbolic link problem is fixed?
Keywords: (none) => feedbackCC: (none) => tarazed25
As it's clearly not a regression, it can be validated, based on the assumption that anyone currently using it will have manually created the symlink. However Chris, please indicate if you would prefer this update to be validated as is, with a new bug report opened for the missing symlink, or hold the update until a new release with the symlink fixed.
CC: (none) => davidwhodgins
Well, considering it's not a critical security issue, I suggest to fix it properly...
It should be properly fixed, the problem with xpa is another bug waiting validation. Either install xpa-devel to test ds9, or try the xpa in updates_testing to test both: https://bugs.mageia.org/show_bug.cgi?id=29245 Thanks!
Keywords: feedback => (none)
This can now be passed on, in the light of the successful test of the https://bugs.mageia.org/show_bug.cgi?id=29245 update.
Whiteboard: (none) => MGA8-64-OK
Validating. Advisory in Comment 2.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0182.html
Status: NEW => RESOLVEDResolution: (none) => FIXED