[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Houston, we do seem to have a problem on OSB!!
[Thread Prev] | [Thread Next]
- Subject: Houston, we do seem to have a problem on OSB!!
- From: gbWilly <gbWilly@xxxxxxxxxxxxxx>
- Date: Wed, 18 Dec 2024 21:40:02 +0000
- To: Gambas Mailing List <user@xxxxxxxxxxxxxxxxxxxxxx>
The mail of PICCORO McKAY Lenz on breaking stuff kind a got me wondering what was going on.
I knew that my own packages where installing to breaking things, even upgrading from debian official was possible, be it in a few steps.
I knew that my own packages where installing to breaking things, even upgrading from debian official was possible, be it in a few steps.
I hadn't tested any osb builds anymore, as I was in need of a break, now stuff was up and running and others where installing all with succes.
But I didn't hear of anyone upgrading from previous installs (like ppa for example) except for PICCORO McKAY Lenz . So, what was he talking about, I had to know.
I had noticed in a quick compare that some packages in osb recipe where missing (like x11 and wayland) and believe I dropped a message here on the list, but didn't see any reaction.
So, I started up a vm and installed one of my old gambas 3,19.6 packaged versions (that provide same packages as gambas ubuntu team ppa did -> most accurate packages in their time).
Next I removed the repo form sources.list add added debian osb as source and did apt-get update and apt-get upgrade.
It started with gambas3 and gambas3-ide not upgrading (but that happens with official to and can be solved later).
But then something new:
gtk3 and qt5 where not upgrading, resulting in 5 broken packages. Normally anf apt --fix-broken install takes care of that, but not now.
The old gtk3 and qt5 refused to be removed, reverting back to previous version was impossible, removing gambas impossible. Luckily this all happened in a vm.
So, I had a good look at the debian recipe on OSB (in the tar) and soon saw what Benoit had changed. Very nifty solution and I like it. Benoit integrated some parts into qt5, gtk3 and qt6 (like wayland and x11 and ext for the qt's) resulting less packages, but for backward compatibility in missing packages.
This backward compatibility is on 2 fronts:
- upgrading gambas from previous versions (either ppa or official) is broken completely because of all of a sudden thare are missing components
- applications before osb that where packaged in gambas3-ide relying on said missing components will NOT install on OSB version of gambas3
So, I went to work again, glad I used my time well to automate a lot of my processes in gambas. I took the changes Benoit implemented and made it so that my recipe makes the same packages.
Next I added the backward compatibility into the recipe and build the packages. Then maed a repository and started up a vm.
Next I added the backward compatibility into the recipe and build the packages. Then maed a repository and started up a vm.
Installed same 3,19,6 version as in my previous test, changed sources.list to new 3.19.90 version, upgraded, next did an apt --fix-broken install and it installed all but gambas3 and gambas3-ide. A simple apt-get install gambas3 did the last part and I had a fully upgraded version running.
And this one does install packages of applications made in older version of gambas IDE.
I have done a merge request with the fixes (https://gitlab.com/gbWilly/gambas/-/commit/2a412aec2919b63d091ab72a97f56dc357737d04), and a much improved changelog for osb and of course I came up with a way to prevent dbgsymb packages to be made, done in debian/rules file.
My excuses to PICCORO McKAY Lenz, you where right, the osb version did seriously break gambas3 in the worst way possible (not even fixable).
But a certain amount of backward compatibility has been added now, to the best of my knowledge. All are free to improve on that.
But a certain amount of backward compatibility has been added now, to the best of my knowledge. All are free to improve on that.
Re: Houston, we do seem to have a problem on OSB!! | Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> |