Opened 5 years ago
Closed 5 years ago
#6393 closed defect (fixed)
Nightly build broken - Error during update of libomcsimulation
| Reported by: | Andrea Bartolini | Owned by: | Andreas Heuermann |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.18.0 |
| Component: | Installation program | Version: | 1.18.0-dev |
| Keywords: | Cc: | Francesco Casella |
Description
Updating the nightly build today I got the following error:
Preparing to unpack .../17-openmodelica_1.18.0~dev-65-g9ac6586-1_amd64.deb ... Unpacking openmodelica (1.18.0~dev-65-g9ac6586-1) over (1.18.0~dev-49-gc5c5e43-1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-V6ItF7/01-libomcsimulation_1.18.0~dev-65-g9ac6586-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
and, after that, trying to start OMEdit I got the following error:
~$ OMEdit OMEdit: error while loading shared libraries: libsuitesparseconfig.so: cannot open shared object file: No such file or directory
sysop: ubuntu 18.04
Change History (9)
comment:1 by , 5 years ago
| Component: | OMSimulator → *unknown* |
|---|---|
| Owner: | changed from to |
| Summary: | Error during update of libomcsimulation → Nightly build broken - Error during update of libomcsimulation |
comment:2 by , 5 years ago
Could be related to https://github.com/OpenModelica/OpenModelicaBuildScripts/pull/7 and probably related to https://trac.openmodelica.org/OpenModelica/ticket/6375.
comment:3 by , 5 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 5 years ago
| Component: | *unknown* → Installation program |
|---|
follow-ups: 6 8 comment:5 by , 5 years ago
It should have said E: Unmet dependencies. Try using -f. or similar somewhere. Calling apt install -f should fix the problem.
comment:6 by , 5 years ago
Replying to sjoelund.se:
It should have said
E: Unmet dependencies. Try using -f.or similar somewhere. Callingapt install -fshould fix the problem.
But this is just a workaround, not the proper fix, right?
comment:7 by , 5 years ago
No, it's the proper fix. The problem is we had one version of the library in the wrong package.
Then fixing it causes the install of the new package to fail because it's installed in another package.
Simply rerunning apt install fixes it. The working version is already staged for install.
comment:8 by , 5 years ago
Replying to sjoelund.se:
It should have said
E: Unmet dependencies. Try using -f.or similar somewhere. Callingapt install -fshould fix the problem.
tried with -f flag and it fixes the broken dependences...
I suppose this fixes definitly the issue...
comment:9 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |

any news?