Re: Upgrading the system and installing Gambas from binary packages

[Bruce Steers <bsteers4@xxxxxxxxx>]

Well there absolutely should not be any issues if just using the distro
repositories gambas and not a gambas OBS one.
Ubuntu has gambas in it's repo just like debian but never the latest
version.
PPA was only used to get the latest version on ubuntu and PPA has been
obsolete for some time now.
I will investigate the problem with debian. I am installing deb12 to a VM
right now and will install their repo gambas then upgrade to deb13 by
editing the sources.list file and see what errors i get.

BruceS


On Tue, 25 Nov 2025 at 09:20, Admin <admin@xxxxxxxxxx> wrote:

> I understand your point of view, but I was not talking about any separate
> Gambas repository. Only the official Debian one. IIRC Ubuntu does not have
> Gambas packages in the repository and it requires adding gambas ppa. Not
> the case with Debian, but you still have to remove Gambas packages to
> update distro. It's not that I think it's important to add anything to a
> wiki page, I just added my two cents about the situation in debian, which,
> I repeat, I never saw as a bug and never asked for any help. Yet, that's a
> unique situation, that a package, installed from a default repo, prevents
> distupgrade. If it was due to any non-default ppa, there would have been
> nothing to talk about.
>
> 25.11.2025 15:41, Bruce Steers пишет:
>
> I think if you have opened the /etc/apt/sources.list file to edit and
> changed bullseye to bookworm then you should have the intelligence to also
> change the Gambas repository links to bullseye as well, like willy said.
>
> "Edit all source references to point to the new distro (so gambas source
> reference included if installed from OSB for example)"
>
> The wiki is not "missing" any info. Unless it needs to be a complete idiot
> guide.
>
> ANY of you can add info to the wiki so add some if you feel it's important
> info.
>
> Why only write the info on the binary package install?, surely it's also
> missing from the compilation pages too with your logic?
>
> BruceS
>
>
> On Tue, 25 Nov 2025, 05:07 Admin, <admin@xxxxxxxxxx> wrote:
>
>> 24.11.2025 23:13, gbWilly пишет:
>> > On Monday, November 24th, 2025 at 16:46, Gianluigi <
>> gradobag@xxxxxxxxxxx> wrote:
>> >
>> >> Benoit, gbWilly, Lee
>> >>
>> >> The wiki is missing a warning that when automatically upgrading to a
>> >> later system version, you must delete the old Gambas and additional
>> >> repositories, then reinstall everything following the instructions for
>> >> the new system version.
>> >>
>> >> Regards
>> >> Gianluigi
>> > No you don't, you simply change the source to point to the newer
>> distribution before you do a distro update (like from jammy to noble for
>> example).
>> >
>> > Distro updates mainly comes down to:
>> > apt-get update
>> > apt-get upgrade
>> > apt-get full-upgrade
>> > apt-get autoremove
>> > reboot
>> >
>> > Next prepare the system for the actual distro upgrade by:
>> > Edit all source references to point to the new distro (so gambas source
>> reference included if installed from OSB for example)
>> >
>> > Next do:
>> > apt-get update
>> > apt upgrade --without-new-pkgs (minimal upgrade -> advised)
>> > apt-get full-upgrade
>> > reboot
>> >
>> > Your system should reboot with your gambas3 upgraded
>> > Where in that process do you see gambas being removed (provided you
>> installed from repository)?
>> >
>> >
>> > gbWilly
>> >
>> > GambOS
>> > Gambas3 for Debian/Ubuntu
>> >
>> > ...there is always a Catch if things go wrong!
>> >
>> >
>> >
>> >
>> Actually on Debian Gambas really prevents, for example, updating from 11
>> to 12. If Gambas is installed under Debian 11, and you change bullseye
>> to bookworm in sources.list, when dist-updating Gambas packages, it
>> causes conflicts of dependencies. You have to remove Gambas first, then
>> dist-upgrade, then install new Gambas from packages using apt. I cannot
>> provide you with more information, I kinda got used to it, treating it
>> as a feature, not a bug, and I don't remember which dependency was a
>> problem, but I updated quite a few 11th to 12th always facing this
>> problem, going through dpkg --fix-broken all the time. So yes, globally
>> Gianluigi is right.
>>
>> Dmitry
>>
>>
>>
>