I am using fedora but need to also distribute my software on debian and ubuntu.
When I use make installation package from the menu I create the 3 distros and the fedora works great.
The other 2 not so much… debian which is the more important one gives me about 2 dozen .deb files with names that differ only with "gtk" or "qt" and I see that with fedora also however I just grab the most generic named one and it works perfect. debian does not have one without the gtk or qt and the install packages are all 1K or under. Needless to say they do not work in debian. ubuntu I can't test until I get it working in a VM for testing.

clearly I am doing something wrong for creating installation files for debian on my fedora machine. What am I doing wrong?

 Firstly, clean out all the files in the target directory or change the target directory. This is so we have a "debuggable" work area.
Then, repackage your project again. BUT only generate ONE Debian based package type (preferably just Debian and not Ubuntu)
Post the package build log AND the settings you used on page 1 of the wizard.

Then we might be able to help.
b

thatbruce said

Firstly, clean out all the files in the target directory or change the target directory. This is so we have a "debuggable" work area.
Then, repackage your project again. BUT only generate ONE Debian based package type (preferably just Debian and not Ubuntu)
Post the package build log AND the settings you used on page 1 of the wizard.

Then we might be able to help.
b

Welcome to Gambas one Bruce   (great name you have there )

If anyone can help you with this sadams54 it's thatBruce. (He wrote some the IDE package enhancements so understands the packager stuff well)

And if there is a bug you can help too by following Bruce's steps to track the bug down. then it will get fixed

BruceSteers said

thatbruce said

Firstly, clean out all the files in the target directory or change the target directory. This is so we have a "debuggable" work area.
Then, repackage your project again. BUT only generate ONE Debian based package type (preferably just Debian and not Ubuntu)
Post the package build log AND the settings you used on page 1 of the wizard.

Then we might be able to help.
b

Welcome to Gambas one Bruce   (great name you have there )

If anyone can help you with this sadams54 it's thatBruce. (He wrote some the IDE package enhancements so understands the packager stuff well)

And if there is a bug you can help too by following Bruce's steps to track the bug down. then it will get fixed

when I tried this I got a working debian install. Seems it does not work well with the others selected. I will have to do one at a time. This however brings me to the next problem.
Seems the gambas3-runtime does not exist for debian 11? is this true or do I have to do the equivalent in fedora of installing more repos? if so how?

I will have to do one at a time.

Here's a clue, on the Destination Directory page of the wizard, there is a teeny-tiny leetle box at the bottom that says "Create directories for each distribution".

This however brings me to the next problem.
Seems the gambas3-runtime does not exist for debian 11? is this true or do I have to do the equivalent in fedora of installing more repos? if so how?

Sorry, I am afraid I have no idea what you are saying. Are you talking about the debian packagers? The Gambas team do not make the distro packages (except the ppa).

best of luck
b

thatbruce said

I will have to do one at a time.

Here's a clue, on the Destination Directory page of the wizard, there is a teeny-tiny leetle box at the bottom that says "Create directories for each distribution".

This however brings me to the next problem.
Seems the gambas3-runtime does not exist for debian 11? is this true or do I have to do the equivalent in fedora of installing more repos? if so how?

Sorry, I am afraid I have no idea what you are saying. Are you talking about the debian packagers? The Gambas team do not make the distro packages (except the ppa).

best of luck
b

I will try the create directories but long as they work I am good.

What I am meaning about debian is that it can't resolve the dependancy of Gambas3-runtime version 3.15 or higher. I also can't install the runtime manually as gambas3-runtime is not found in the debian repositories. I am wondering if they exist for Debian 11 or is there another repository I need to install to get to gambas runtime

sadams54 said

…What I am meaning about debian is that it can't resolve the dependancy of Gambas3-runtime version 3.15 or higher. I also can't install the runtime manually as gambas3-runtime is not found in the debian repositories. I am wondering if they exist for Debian 11 or is there another repository I need to install to get to gambas runtime

If I'm reading this right, this page: Debian -- Details of source package gambas3 in bullseye  
seems to indicate that Gambas runtime interpreter is included for Gambas3 v3.15.2 on Debian 11/Bullseye

So are you saying that this is not the case? Maybe double check that you are looking at the right repository.

My Debian11…


That's using Debian main server

that is gambas 3.15.2

To get a newer gambas than that you have to use the autotools install and remove the 3.15.2 apt installed version.
/install - Gambas Documentation
You're not adding the PPA are you?  PPA is for Ubuntu based systems only, not debian.

I've been down this road a few times.
This is why i made the gambas upgrader scripts/apps i did.
You either use gambas on one machine then 3.16 is just completely usable as is..

Or, for cross compatibility across other systems you have these choices…
The main problem is backward compatibility. a 3.16 app won't work on 3.15 (unless you know how) but a 3.15 will work fine on 3.16
So……

Upgrade the other systems to 3.16
Only Ubuntu/Mint/Etc can use the easiest apt PPA method
Other systems will need to use auto-tools method.


to write apps on 3.16+
You MUST ensure they have backward compatibility for older gambas versions (do not use code that did not exist on older gambas)
Ie..

sadams54 said

 ubuntu I can't test until I get it working in a VM for testing.

clearly I am doing something wrong for creating installation files for debian on my fedora machine. What am I doing wrong?

Never mind VMs  just add a partition to your hard drive and install a full speed os.

when my computer boots up i get a grub menu that gives me a choice of about 14 different os's to boot into for my testing needs.
Variants of Mint, ubuntu, debian, manjaro, mandriva, mageia,
To be honest 14 is kinda excessive if update-grub gets run it takes ages lol

Here's just the ones with gambas installed..
(attachment removed)

but working with VM's is slower than the occasional update-grub command being run

BruceSteers said

sadams54 said

 ubuntu I can't test until I get it working in a VM for testing.

clearly I am doing something wrong for creating installation files for debian on my fedora machine. What am I doing wrong?

Never mind VMs  just add a partition to your hard drive and install a full speed os.

when my computer boots up i get a grub menu that gives me a choice of about 14 different os's to boot into for my testing needs.
Variants of Mint, ubuntu, debian, manjaro, mandriva, mageia,
To be honest 14 is kinda excessive if update-grub gets run it takes ages lol

Here's just the ones with gambas installed..
Screenshot from 2021-09-09 14-18-23.png

but working with VM's is slower than the occasional update-grub command being run

the reason I use a VM is so I can do a snapshot and easily in just minutes revert it back to a clean state without complete reinstall. Not to mention that dual booting is a pain in the ass. I keep the VM's so I can test clean installs so partitions are just not going to cut it.

stevedee said

sadams54 said

…What I am meaning about debian is that it can't resolve the dependancy of Gambas3-runtime version 3.15 or higher. I also can't install the runtime manually as gambas3-runtime is not found in the debian repositories. I am wondering if they exist for Debian 11 or is there another repository I need to install to get to gambas runtime

If I'm reading this right, this page: Debian -- Details of source package gambas3 in bullseye  
seems to indicate that Gambas runtime interpreter is included for Gambas3 v3.15.2 on Debian 11/Bullseye

So are you saying that this is not the case? Maybe double check that you are looking at the right repository.

correct, I am saying it is not the case. when I do apt-get install gambas3-runtime  the software is not found by debian. Keep in mind I am not a debian guy. I am fedora so when it comes to repos for debian I am lost. if something is missing like a repo please tell me how to fix.

Well, a quick look through the debian 15.2 packages themselves (from that link you provided) reveals that the runtime is only packaged for the mipsel architecture. In fact, having a geezer at other Gambas3 packages it looks like they were put together by a "committee". Some for this architecture and some for that.
I recall now that a bulletin board "helper" said to me recently that he was damned if he knew or understood how debian decides to package some things. Now I see what he meant.
You will have to contact debian and get them to build an arm64 package (if that's your architecture).

b

What I am about to tell you is <COLOR color="#FF8000">absolutely top secret and you should not show it to any one else!</COLOR>

The Gambas packager assumes that you have installed Gambas from a packaged origin i.e. as binaries from some distro or other. However, not all distros package Gambas in the structure recommended in the wiki. Well I mean, why should they, after all they know better, don't they.  :roll:  :roll:  :roll:
Your problem is one example of the results of their "better" approach.

(Back to Gambas) It is, of course, impossible for us to guess what package structure a particular distro decides to use for such and such a version of Gambas.  All we can do is code for the recommended structure. So, the package builder and in particular I will talk of the Gambas package builder for Debian, includes requires lists. There are two lists, one for building the package (i.e. the current system you are building <COLOR color="#4000FF">on</COLOR>) and one included in the package (and by "in" I mean "inside") that is <COLOR color="#4000FF">for</COLOR> the target system.
(From memory, RPM "spec" based builds are the same.)

The upshot of these two lists are that
<LIST>

• <LI>you will not be able to build the target package unless you have those packages for your distro installed on your machine</LI>

</LIST>
<LIST>

• <LI>you will not be able to install the target package on the target machine unless it has the packages in the second list installed</LI>

</LIST>
<COLOR color="#FF0000">You should not need the debian runtime package to be installed on your build machine in order to build debian packages via the IDE packaging faculty. If you do so need, then we have a bug.</COLOR>

Sshhhhh! IMO you should also not need the "packages" for the build machine distro installed on the build machine. BruceS knows this fully well. Further, there is a way around it. But it is secret because someone, possibly with the initials BM, would probably nuke South Australia if he found that I was suggesting this.
To build debian packages so there are no "requires" dependencies takes only a very small modification or two of the IDE itself. In the Package module (in the Packager tree) there are several calls to GetDependencies() from the MakeDebPackage() method. By replacing those calls with a null-string literal you wont generate the dependencies in the builder list or the target list. Et voila! Packages build. BUT <COLOR color="#FF0000">if you do go down this road, don't ask for support from the Gambas development team and finally:</COLOR><COLOR color="#FF0000">
Now you have read this I'm afraid that I have to kill you.</COLOR>

THis is the result when I try to manually install the gambas3-runtime…

(Click to enlarge)

if this is a debian issue I understand. but I want to make sure it is not something I am not doing. If it is I want to learn what my mistake is.

looks like you only have the security debian repository set up , you need main and contrib too.
This happens when you choose not to select a network mirror at install

From debian website…

Using a repository is fairly simple: For the official Debian repository open /etc/apt/sources.list, insert the line

deb Index of /debian stable main contrib non-free

then run
apt update

 ps. you can use apt-cache to find what gambas3 packages are available from your configured repositories.

apt-cache search "gambas3*"

BruceSteers said

looks like you only have the security debian repository set up , you need main and contrib too.
This happens when you choose not to select a network mirror at install

From debian website…

Using a repository is fairly simple: For the official Debian repository open /etc/apt/sources.list, insert the line

deb Index of /debian stable main contrib non-free

then run
apt update

thank you. That was what I was looking for. also looks like the pathing was not set in the debian install. You helped me figure out the problems. Seems debian does not install as well as others but now I know how to fix so thank you and it works on debian.