[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Call to help testing osb for backward compatibility


On 12/21/24 12:06, Benoît Minisini wrote:
Le 21/12/2024 à 18:04, T Lee Davidson a écrit :
On 12/21/24 09:53, Gianluigi wrote:
I'm trying to update version 3.19.6 to the Master version after creating
the test package with gb.qt5.ext.
Of course I uninstalled the old repo (sudo zypper rr home_munix9).
Unfortunately I receive three problems from the terminal: (*)

I apologize for not mentioning before that those problems you experienced, IIRC (it's been a few days), can be alleviated by passing the '--allow-vendor-change' flag to the `zypper install gambas3` (or `zypper upgrade gambas3`) command.



Do not hesitate to update the 'https://gambaswiki.org/edit/doc/packages' wiki package (provided the wiki works of course!).

That way the information will be centralized and available for everyone.

Regards,


Okay.

There is a warning near the top of the page: "When you add the openSUSE build service repository for the first time, remove all previous installations of Gambas entirely, to prevent any weird dependency problem."

I think that can be removed (?) and an Info box placed under the openSUSE instructions regarding adding that flag if upgrading?


--
Lee

--- Gambas User List Netiquette [https://gambaswiki.org/wiki/doc/netiquette] ----
--- Gambas User List Archive [https://lists.gambas-basic.org/archive/user] ----


Follow-Ups:
Re: Call to help testing osb for backward compatibilityBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
References:
Call to help testing osb for backward compatibilitygbWilly <gbWilly@xxxxxxxxxxxxxx>
Re: Call to help testing osb for backward compatibilityChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: Call to help testing osb for backward compatibilityGianluigi <gradobag@xxxxxxxxxxx>
Re: Call to help testing osb for backward compatibilityT Lee Davidson <t.lee.davidson@xxxxxxxxx>
Re: Call to help testing osb for backward compatibilityBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>