Problems installing LibreOffice in HaikuDepot

I am new to Haiku. I have installed it as a VM in VirtualBox. It connects to the internet and I can browse via WebPositive. I have added repositories and been able to find LibreOffice, but I have run into difficulties with its installation. After selecting LibreOffice and clicking Install, the following pop up message occurred.
“Package Problem – The following problems have been encountered. Please
select a solution for each
nothing provides haiku >=r1-beta1_hrev54045-1 needed by libreoffice-6.4.3.1-4
Package Problem window pops up, giving me 2 options via radio buttons
Solution 1:
– do not install ‘providing libreoffice’ – options are Cancel and Retry
ignore problem for now – options ‘Cancel’ only”

The 2nd option is illogical as choosing Cancel is not ignoring the problem but cancelling the installation. If I click retry this pop up disappears. The entry in Haiku depot lists Libreoffice as Pending.

Any help and assistance welcomed

Stephanos

What version from Haiku did you install? The Beta1 or one of the nightlies? (hrev version is shown in the About window)

Dear Begasus

Thanks for the reply. The answer to the question is:
R1/beta1 (revision hrev 52295+96) x86_64

By the way I do not understand the nightlies. Do I treat it in the same way as I did the ISO I used to install Haiku or is it some type of add on I use once Haiku is installed?

The Nightly ISOs work the same way as the Beta1 ISO.

I wonder why that happened tho. Don’t buildslaves use beta1 images?

revbump for libreoffice is in the works, but that will take some time until finished, and yes, we had some problems with some recipes not building on the beta1, but this isn’t one of them afaik

I mean LibreOffice should have been built agains beta1. How come it requires a nightly hrev54045 which was just a few weeks ago.

Because we switched the HaikuPorts builders over to a nightly build a few weeks ago?

The R1/beta1 HaikuPorts repositories were disabled around then (which should also prevent people from upgrading to broken versions of OpenSSL on the beta.) So I am somewhat surprised that the error message is not “404 not found”, although maybe during the repo file was downloaded during the interim.