[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#895057: marked as done (RFH: ltsp -- network booted thin and fat clients)

Your message dated Tue, 12 Nov 2019 15:43:04 -0800
with message-id <87lfskoe47.fsf@yucca>
and subject line Re: RFH: ltsp -- network booted thin and fat clients
has caused the Debian Bug report #895057,
regarding RFH: ltsp -- network booted thin and fat clients
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
895057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895057
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal

It has been several years since I've actually maintained a real-world
deployment of LTSP, and there are very few other active developers of
the project upstream. I have continued to maintain it in Debian as best
I can, and would love to see it continue to be supported in Debian, but
would really need some active co-maintainers to keep it viable
long-term.

Right now there is an RC bug regarding support for the transition to
FreeRDP2 (which I've never used):

  https://bugs.debian.org/892626

Of course there are a few other bugs in Debian and upstream.

The main source packages affected are ltsp, ldm, ltspfs and the
much-neglected ltsp-docs.

There's also ltsp-manager, currently only in experimental, which is an
attempt to simplify installation and management of LTSP environments.

Another source package is libpam-sshauth, which is a major piece of an
attempt to replace the deficiencies of LDM with a regular display
manager using PAM... this has long been on the plans for a next
generation LTSP, but hasn't gotten beyond the proof of concept phase.


I've CCed debian-edu in the bug report, as that project has some of the
largest active users of ltsp in Debian that I'm aware of.


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 2018-04-06, Vagrant Cascadian wrote:
> It has been several years since I've actually maintained a real-world
> deployment of LTSP, and there are very few other active developers of
> the project upstream. I have continued to maintain it in Debian as best
> I can, and would love to see it continue to be supported in Debian, but
> would really need some active co-maintainers to keep it viable
> long-term.

This is all still true... but some new developments worth mentioning...


> The main source packages affected are ltsp, ldm, ltspfs and the
> much-neglected ltsp-docs.

I uploaded a new rewrite of LTSP was to unstable, which should be much
easier to maintain, and I'm even excited to work on it again, so marking
this bug as done.


The ltsp-docs package has been removed from unstable.

I've marked ldm, ldm-themes and ltspfs as orphaned now:

  https://bugs.debian.org/944567
  https://bugs.debian.org/944566
  https://bugs.debian.org/944565

They should also be removed if nobody adopts them soon, and the only
reason someone should adopt them is if they plan to maintain ltsp 5.x in
a separate source package; I have no intention of doing so.

None of these should be released with bullseye unless more active
maintenance happens.


> There's also ltsp-manager, currently only in experimental, which is an
> attempt to simplify installation and management of LTSP environments.

That should probably be removed now as well; unless someone revitalizes
ltsp 5.x somehow...


> Another source package is libpam-sshauth, which is a major piece of an
> attempt to replace the deficiencies of LDM with a regular display
> manager using PAM... this has long been on the plans for a next
> generation LTSP, but hasn't gotten beyond the proof of concept phase.

And libpam-sshauth was removed from unstable; the new version of LTSP
included a different implementation to solve the same goal.


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: