Debian 7 and later has a completely broken install_initd thanks to the same crack team at Canonical that caused bug 4205 and bug 4439 (and forced us to do bug 4546). This time though they managed to screw Debian over, and not themselves.
Upstream bug here:
Bad commit here:
StringIO.StringIO and io.StringIO do not have identical API.
Start by reporting more information to Debian and updating our platform specific notes with a workaround. If Debian fails to take action we'll start looking into changing the product.
Additional info has been added to Debian's bug report.
Not convinced the maintainers will fix this within any reasonable timeframe, the thing's a mess. We should at least write up something in Platform Specific Notes in the mean time.
(In reply to comment #3)
> Not convinced the maintainers will fix this within any reasonable timeframe,
> the thing's a mess. We should at least write up something in Platform Specific
> Notes in the mean time.
I stand corrected, looks like it's been fixed upstream.
I installed up both a debian 7.5 and a 7.6, installed ThinLinc and verified that the bug is indeed fixed.
Reopening, not working in Debian 8:
2014-07-24 12:32:00,164: Output (stderr):
2014-07-24 12:32:00,164: Traceback (most recent call last):
2014-07-24 12:32:00,164: File "/usr/lib/lsb/install_initd", line 46, in <module>
2014-07-24 12:32:00,165: headers = initdutils.scan_initfile(initfile)
2014-07-24 12:32:00,165: File "/usr/lib/lsb/initdutils.py", line 79, in scan_initfile
2014-07-24 12:32:00,165: inheaders = RFC822Parser(strob=headerlines)
2014-07-24 12:32:00,165: File "/usr/lib/lsb/initdutils.py", line 24, in __init__
2014-07-24 12:32:00,165: fileob = StringIO(strob)
2014-07-24 12:32:00,165: TypeError: initial_value must be unicode or None, not str
2014-07-24 12:32:00,166: Failed to install service 'vsmserver'
2014-07-24 12:32:10,729: tl-setup aborted by user
> If you have further comments please address them to firstname.lastname@example.org,
> and the maintainer will reopen the bug report if appropriate.
Platform-specific note with workaround added in revision 29222.