Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics

The author of this package apparently doesn't know how to pack a .deb file correctly. Not only does it not install, the paths to the executable in the various script files are wrong.

This is going to take me awhile to get this thing to work, I don't have time at this moment to work on it.

Note: The proper path to create a .deb package installer file;

All files must have a project named directory, the second directory to be created inside that project name is, "DEBIAN". Inside the "DEBIAN" directory you need all of these files included the packed archives;

control, control.tar.gz, data.tar.gz, debian.binary and md5sums

Then from the top level (just outside your project name directory). Use 'dpkg --build YourProjectDirectoryGoesHere. I'd recommend using double quotes around your project directory, that way, if you have spaces or some other weird character that UNIX / Linux does normally like or are case sensitive with go through without a hitch.

Now, I've built the .deb just fine, however, you don't have script to reslove the 'mono-complete' in your installation script.

If you attempt to install it, you run into unmet dependencies.

To fix this you need to run;

sudo apt -f install

That will get what is needed and then the dpkg with finish doing it's thing.

However, there is another problem, "scellix" should have a symlink created to go from the "Launch" button in itch to the systems directory it's located in via "/usr/lib".

I hate to say this, the tool isn't ready for use on Debian and Ubuntu. While the pictures and videoes on said package look amazing, well, there is still a lot of work to be done.

(1 edit)

Hey Sub_Atomic_Quark,

First off, we apologise for not coming back to you sooner but the itch notification got lost in the crowd.

Thank you for bringing this issue to our attention.

Since we have shifted to a more generic system for packaging (Effing package management: ), it is possible that there are some structural differences, although we did not experience such problems, at least in some later versions of Ubuntu, Debian, Fedora, CentOS, SUSE and Red Hat. It could also be something that arose in our last releases, so we will definitely have a look at it and consider your helpful instructions :)

In the meanwhile, could you provide us with some more information about the Linux distribution that you are using?

Regarding the installation, here is a direct link to the documentation:

We did not package the mono dependencies in the deb package - so a separate installation is, in fact, required.

All of my dev machines are the following in 86_64.

All use Xubuntu desktop (XFCE4 based).







Those are just the Ubuntu related version I have. The main one I use is 16.04 for client's needs. That's also what I have installed on the gaming systems, too.

Yes, I've read your instructions but there was no .deb for me to install, I had to generate it from the files and some were missing so I had to create dummy files. Also, I use mono-complete, which installs all of mono and it's dependencies as well. Your .deb file should have the proper version of Ubuntu it's designed for, what architecture and of course the specific packages as dependencies. About Ubuntu and it's forks, from time to time, often version to version they change the name of he package in question which makes it tough to write a shell script that is executed when you use dpkg to install the .deb installer archive file.