Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: ProviewR 5.7 / Debian 10

ProviewR 5.7 / Debian 10 4 weeks 9 hours ago #10479

  • Geno
  • Geno's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 33
  • Karma: 0
I struggle to get 5.7 running on Debian 10, as there were changes in the handling of system paths. Has someone. I did the following:

In ~/.bashrc
export pwra_db=/usr/pwrp/adm/db
source $pwra_db/pwra_env.sh
source $pwra_db/pwr_setup.sh
set base V5.7
set bus wb -p pwrp pwrp

After that, I could start the administrator using pwra, but following messages appear:
(wb:8681): dbind-WARNING **: 15:40:40.925: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2020-01-23 15:40:40 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_db
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_root
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_root
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_db
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_db
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_root
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_root
Warning! CoLog::log could not open log file $pwrp_db/wb_history.log
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_root
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_db
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_login
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_login
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_login
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_login
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_login
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_login
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_db
2020-01-23 15:40:41 DEBUG co_dcli_file.cpp:178: Warning! Could not resolve environment variable $pwrp_db


Now if I try to update an exisiting 5.6 project, following the instructions, sdf brings
$ sdf <project>
Unable to find base '<project>'

Obviously there is something weird regarding the system paths - any ideas?
Last Edit: 4 weeks 9 hours ago by Geno.
The administrator has disabled public write access.

ProviewR 5.7 / Debian 10 3 weeks 6 days ago #10480

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 2715
  • Thank you received: 358
  • Karma: 117
Hi Geno,

The warning messages are because no project is attached yet.

You can't sdf to a V5.6 project on debian 10. V5.6 runs on debian 9 and the project has to be upgraded to V5.7. Follow te instructions in the release notes for V5.7. Basically you have to dump the data base with reload.sh in debian 9, the change the version to V5.7 in debian 10 and continue the upgrade with upgrade.sh there.

If your debian 9 environment isn't present any more you could try changing the base to V5.7 for the project and activate Update Classes in the configurator for the root volume. This will replace the dumping/loading database and will work in most cases (take a copy of the project first though...).

/Claes
The administrator has disabled public write access.
The following user(s) said Thank You: Geno

ProviewR 5.7 / Debian 10 3 weeks 6 days ago #10481

  • Geno
  • Geno's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 33
  • Karma: 0
Thank you Claes!

Almost there:

screen.png


How can I edit the version in those files, as they seem not to able using an editor?
The administrator has disabled public write access.

ProviewR 5.7 / Debian 10 3 weeks 6 days ago #10482

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 2715
  • Thank you received: 358
  • Karma: 117
Activate Functions/Update Classes in the configurator for volheatsys to update these files.

/Claes
The administrator has disabled public write access.
The following user(s) said Thank You: Geno

ProviewR 5.7 / Debian 10 3 weeks 3 days ago #10483

  • Geno
  • Geno's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 33
  • Karma: 0
claes wrote:
Activate Functions/Update Classes in the configurator for volheatsys to update these files.

/Claes

Good morning Claes,

that fixed it - thank you!
The administrator has disabled public write access.

ProviewR 5.7 / Debian 10 3 weeks 3 days ago #10484

  • Geno
  • Geno's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 33
  • Karma: 0
Hmmm...ok...almost:


lplcferror.png


What does this mean? I have set the compiler to "linux_on_x86_64", as the project was transferred from a 32bit environment. Do I have to change any other settings / paths in the project structure?
Last Edit: 3 weeks 3 days ago by Geno.
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 2.939 seconds