On 2015-02-10, Andreas Beckmann wrote: > On 2015-02-09 10:26, Vagrant Cascadian wrote: >> The lenny and squeeze versions shipped /etc/init.d/ltsp-client-setup >> (and /etc/default/ltsp-client-setup), but is no longer used by ltsp, and >> could actually be harmful! I suspect many LTSP installations re-install >> LTSP chroots rather than upgrade, which has probably hidden the issue >> over the years... > > If it's potentially harmful, you should consider fixing this in > stable, too.
True enough. >> The following patch removes the init script and corresponding >> configuration file: > > Do you have the packaging in git somewhwere available? > debcheckout only tries to fetch some not working bzr. The Vcs-Bzr just includes the debian dir, not the upstream part of the code. I use git-remote-bzr to checkout the upstream code, and then git-remote-bzr to checkout a debian dir. It's a bit clumsy to work with, but still that way mostly for historical reasons... > Anyway, I applied your patch, rebuilt the package and fed it through > piuparts - that seems to have worked and fixed the issue. > > a 2-line ltsp-client-core.maintscript file should have been even easier: > > rm_conffile /etc/init.d/ltsp-client-setup 5.5.4-3~ > rm_conffile /etc/default/ltsp-client-setup 5.5.4-3~ Thanks for the suggestion; that looks much simpler! Committed a new version with just the ltsp-client-core.maintscript. live well, vagrant
signature.asc
Description: PGP signature
