[Pkg-ltsp-devel] current upload and bug status

Gustavo Franco gustavorfranco at gmail.com
Wed Aug 9 00:17:56 UTC 2006


On 8/9/06, Vagrant Cascadian <vagrant at freegeek.org> wrote:
> just when i thought i had ltsp ready for another upload, we get a
> python policy bug in ldm :(
>
>
>    1) #380859: Python transition (#2): you are building a private python
> module !
>
> our inclusion of subprocess.py was a "private python module". we
> originally had included it only to support sarge, but removing it also
> borked things in sid/etch (because we no longer hard-code a dependency
> on python2.4). seems to work with the python and python-minimal package
> from experimental, which should hit sid "this week". when that happens,
> i think we can upload with what's in pkg-ltsp main branch. so it's not
> so ugly. (i'm testing if switching back to hard-coded python2.4 is
> another option).

I think the alternative is rewrite the bit of code that use
subprocess. I'll look into this while python2.4 doesn't hit sid. I
remember that mvo did it with gdebi (we co-maintain it).

> this gives us a little more time to review the outstanding bugs...
>
>    2) #367606: swap on thin clients (LTSP) should be turned on as
> default
>
> this one is pretty complicated to fix. might be able to set up an ugly
> workaround, or a script to enable it and create swapfiles on the server.
> i haven't tested the NBD swap stuff at all. another option would be to
> include ltspswapd(?) in the ltsp-server package, and do a lot of
> testing. ugh.

I don't think it's a blocker for a new upload.

>    3) #356986: ltsp-server: ltsp should not be dependent on sound
>
> i would like to move the ltsp-server dependency on "esound-clients" to a
> recommends, and add it as a dependency on ltsp-server-standalone. it's
> not truely necessary to have sound on the clients, even if it may be the
> default.

I agree that sound support should be off by default, but i dunno
what's the best way to let it be easy to use.

>    4) #360406: ltsp-server: what's skolelinux?
>
> in the long-term, we should probably use a debconf question
> (preseedable) to set up the preferred alternative. at the moment, it's
> hard-coded for debian-edu/skolelinux. the debian theme looks stupid, but
> maybe would be better to make that default, and try to find some artist
> to write a better debian theme?

I don't think it's a blocker for a new upload too, but we could work
on the infrastructure to change the artwork in the near future for
etch. I'll be organizing a meeting about desktop-base usage,
pkg-gnome, pkg-kde and pkg-xfce artwork. It would be good put pkg-ltsp
in the mix too.

>    5) #360409: ltsp-server: there's no sample dhcp conf in the doc
>
> would anyone be opposed to including the dhcpd.conf file in
> /usr/share/doc/ltsp-server/examples ? this might be helpful to some
> users, even if we include the same file in ltsp-server-standalone.

If the example is good enough for the users, why not? :)

regards,
-- stratus



More information about the Pkg-ltsp-devel mailing list