VSIDO Community

VSIDO Support => General Support => VSIDO Installation Help => Topic started by: VastOne on January 11, 2018, 05:17:04 PM

Title: (SOLVED) VSIDO installs failing due to ImportError: No module named 'debconf'
Post by: VastOne on January 11, 2018, 05:17:04 PM
Have built new ISO's and the Trios installer is failing with the following error

Code: [Select]
ImportError: No module named 'debconf'
I have tested the old installer (which also uses debconf) and it worked fine

@filip Do know of this issue?  I'll try to rebuild the installer to see if that resolves the issue
Title: Re: VSIDO installs failing due to ImportError: No module named 'debconf'
Post by: filip on January 12, 2018, 07:31:36 PM
I´m away from any PC running Debian ( including my own ), so going blind here.

There was a recent split of debconf package into Py2 & Py3 versions ( changelog (http://metadata.ftp-master.debian.org/changelogs/main/d/debconf/debconf_1.5.65_changelog) ) so it´s most likely related to that.
Either the module was renamed ( thus the "import" fails ), or the package itself is not installed.

Hopefully:
Code: [Select]
apt install python-debconf... will fix the issue.  :)
Title: Re: VSIDO installs failing due to ImportError: No module named 'debconf'
Post by: VastOne on January 12, 2018, 08:54:14 PM
Hey filip...

On the first pass that seems to be the fix... testing the rest now

Thanks for the heads up!

Cheers!
Title: Re: (SOLVED) VSIDO installs failing due to ImportError: No module named 'debconf'
Post by: VastOne on January 12, 2018, 10:08:08 PM
The solution to this was installing python-debconf

The split broke python3-debconf which had already been installed and used since the beginning of VSIDO

Why the dev would not take into account both needs and make one or both a dependency is beyond me...

Laziness?

Thanks again to filip for the help
Title: Re: VSIDO installs failing due to ImportError: No module named 'debconf'
Post by: filip on January 15, 2018, 12:19:15 AM
Hey filip...

On the first pass that seems to be the fix... testing the rest now

Thanks for the heads up!

Cheers!
Well, for a change, I guess it was ´bout time for an easy fix...  ::) ;D

The solution to this was installing python-debconf

The split broke python3-debconf which had already been installed and used since the beginning of VSIDO

Why the dev would not take into account both needs and make one or both a dependency is beyond me...

Laziness?

Thanks again to filip for the help
No idea, though the split seems uneccessary to me. After all, both packages install the very same "debconf.py" ( it´s compatible with both Py´s ), just to different locations...
Perhaps they wanted to drop Python dependencies from "debconf" package...  ::)

You´re welcome, anytime!  :)