5.21
...
·
·
2
likes
|
|---|
Franco Grimoldi: So why did you update if all was working well, I alway stay one version behind all the time then no issues like this ever, it’s not rocket science is it….😂😂 |
7.22
...
·
·
2
likes
|
|---|
AstroShed:Franco Grimoldi: I'm a PixInsight newbie and wasn't aware of these apparently frequent issues with updates. On the other hand, I'm used to follow the updates schedule of all the OSs, programs and drivers I use. There might be an occasional bug but never such failures and crashes, this definitely caught me off guard. |
3.10
...
·
·
4
likes
|
|---|
Jeff Rothstein: It's simply because you waited until today. there's been enough time for the various script authors to update their repositories to allow 1.8.9-3 as a valid version. juan really should give the repository owners a heads up when he's going to change a minor or major version of PI. that would have avoided all this trouble. juan claims he will do this in the future; i hope so. i guess also some repositories were not using the latest developer signature files. also, deleting the signature file for the script will work up until the day juan decides to disallow unsigned scripts and modules from running. for now the trick still works. |
0.90
...
·
|
|---|
For the record, I updated the day after the release, not today.
|
|
3.10
...
·
·
2
likes
|
|---|
Jeff Rothstein: well, same difference. the problem did get fixed relatively quickly for the more popular repositories. bottom line is the release came as a surprise to the wider developer community. |
5.01
...
·
|
|---|
My update is working fine. Everyone says something about Graxpert on every update, until its updated by the author you'll have delete the files as stated above. Then repoint using spanner bottom right of script when you reuse. On a different note I have a copy of my repository entries saved separately just in case they get wiped. |
|
7.22
...
·
|
|---|
My update is working fine. Everyone says something about Graxpert on every update, until its updated by the author you'll have delete the files as stated above. Then repoint using spanner bottom right of script when you reuse. It would be great to be able to copy and paste the repositories URLs in bulk.... |
4.71
...
·
·
2
likes
|
|---|
This happens every new release and every new release the script developers ask the PixInsight team to give them a few days warning and a prerelease build they can use to test and every time they say they will. Best practice is to just consider every PixInsight release a prerelease for testing for a couple weeks, let everything cool down, and just update then.
|
|
3.10
...
·
·
2
likes
|
|---|
Franco Grimoldi:My update is working fine. Everyone says something about Graxpert on every update, until its updated by the author you'll have delete the files as stated above. Then repoint using spanner bottom right of script when you reuse. you shouldn't have to - the list of repositories is stored in the pixinsight settings file, and the settings file persists across upgradees. if you want you can get them out of the settings file with a text editor: %USERPROFILE%\AppData\Roaming\Pleiades\core-001-pxi.settings or ~/Library/PixInsight/core-001-pxi.settings on macos. i would make a copy of the file first. if you are handy with the shell, "grep http core-001-pxi.settings" will give you the list of repositories, along with some other junk, but it's easier to copy and backup that way. |
0.00
...
·
|
|---|
Using the latest build on PI 1.8.9.3 I also download GraXpert v3 When I run it says not supported yet. OK I can't find updates manage updates anymore was it removed in 1.8.93
|
2.81
...
·
|
|---|
Dunk: I think that expecting any software developer to cater for dozens of different plugins is never going to happen |
|
7.22
...
·
|
|---|
Geoff:Dunk: I think they meant "proper update" as a process that can be handled by the app itself, not needing to download an installer and overwrite an existing installation. |
