Now I get this error:
Setting up x2goserver (4.1.0.0-0x2go1.2+git20180302.1517+9.main.1) ...
Can't locate X2Go/Config.pm in @INC (you may need to install the X2Go::Config module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/sbin/x2godbadmin line 30.

At this point the salient question is: Why is this not working? There is nothing x2go on this server, I erased everything that the purge failed to do. At this point, the system should be as fresh as a completely new box. But for some reason, dpkg seems to remember that I erased something or that something is missing. Where is that stored, how can I make dpkg / apt treat this as though it does not know anything about the x2goserver package, like it was never installed before? This is not the first time this happened, dpkg seems to remember when things get erased and does not get that likely, an admin erased something for a purpose and that it should be replaced fresh when reinstalling it, instead of complaining that a config is not there (while in a fresh install, there is nothing installed and all the files need to be unpacked and installed from scratch)

Thanks,

Markus

On Wed, Mar 14, 2018 at 6:48 AM, Mihai Moldovan <ionic@ionic.de> wrote:

* On 03/14/2018 03:19 AM, Nigra Truo wrote:
> Thanks for the pointers. Yes, of course all apt commands are always executed
> as root. Right now it is not so much about the bug that prevents purging, it
> is more that I just can't reinstall x2goserver anymore. I see this message
>
> "X2Go is configured to use a non-SQLite DB backend, leaving the database
> alone" and the server install fails.
>
> and can't find any documentation and reference to it, it is a show stopper
> at this moment. Question: Where is x2go told to do that? Which config is
> still left on the system? I cleaned up EVERYTHING x2go related, erased all
> dirs and configs, I have never seen this message before. It is like apt /
> dpkg remembers some setting that it is not supposed to remember (as the
> package was purged)

It's determined in a {pre,post}{inst,rm} scripts... which are buggy in that regard.

We should ignore non-existing files instead of assuming a different SQL backend
being used.

Please create /etc/x2go/x2gosql/sql manually with a line containing
'backend=sqlite'. That should allow you to purge the packages.

Afterwards you should be able to reinstall them normally.

Mihai

Por sperto kaj lerno ne sufiĉas eterno.