All we'd need to do is submit patches upstream for pam-python to support python 3

16:41

I'd take that on.

16:42

bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)

16:42

* vagrantc continues to be amazed at sbalneav's can-do attitude

16:43

<sbalneav>

ok, I'll work on an initial implementation of a "remote" command today

16:43

<bennabiy>

sbalneav: off work for a little time?

16:44

<sbalneav>

Nope, I'm at work now. It just happens to be slow. :D

16:44

<bennabiy>

ah

16:44

<sbalneav>

And since I administer an entire IT department that uses ltsp....

16:45

developing ltsp is part of my job XD

16:45

<vagrantc>

yay!

16:46

<bennabiy>

That works. It works something similar for me, but I have a couple other projects which are at front burner now, but I am encouraged to see a little thrust towards 5.9999 -> 6 :)

16:46

It almost was starting to feel like alkisg and vagrantc were getting worn out ;)

16:48

<vagrantc>

and here's a python2 countdown https://pythonclock.org/

16:52

hrm. so debian stretch will probably have ended support about the same time as python2, although stretch long-term-support might have challenges

16:53

lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection)

17:23

<vagrantc>

sbalneav: well, tested the latest ltsp-pam commits, seems to work after hitting it a bit

17:23

bennabiy: well, if you'd like to give it a test:

17:23

!pam | echo bennabiy

17:23

<ltsp>

bennabiy pam: http://wiki.ltsp.org/wiki/Dev:LTSPPamNotes

17:23

<vagrantc>

that's kind of where it's at

17:23

i updated that a few days ago, think it's still reasonably current

17:24

<bennabiy>

vagrantc: I should be able to test that out in the next couple days

17:24

<vagrantc>

it currently only works with fat clients ...

17:25

though i think there's some code to support thin clients, but i don't know that long-term we'll be able to support it

17:36

i wonder if we should start tracking bugs on ltsp-pam

17:36

<sbalneav>

Prolly

17:36

<vagrantc>

e.g. using launchpad

17:38

i wish there were a bugs-per VCS or soemthing ... i have no idea how to file bugs on this

17:39

and https://bugs.launchpad.net/~ltsp-upstream just gives me a search interface for bugs ...

17:39

how do i file a bug?

17:40

and if the search comes up empty, it doesn't provide a link to create a bug

17:46

lucascastro has joined IRC (lucascastro!~lucas@186.227.185.10)

17:46

<vagrantc>

apparently, i was looking for https://bugs.launchpad.net/ltsp/+filebug

17:49

* vagrantc was thinking if we recreate an ltsp-docs package, to use markdown and pandoc (or some other markdown-to-pdf exporter) rather than the docbook-xml mess

17:49

<vagrantc>

i think it'd be easier to edit and maintain if the text were more plaintext-readable

17:51

<sbalneav>

I use rst myself

17:53

where did the old ltsp-docs package go?

17:54

I'm not seeing it on https://code.launchpad.net/~ltsp-upstream/

17:57

<vagrantc>

maybe under ltsp-docwriters or one of the other half-dozen ltsp subgroups

17:57

https://code.launchpad.net/~ltsp-docwriters/ltsp/ltsp-docs-trun

17:58

k

17:58

<sbalneav>

found it, yeah.,

17:58

<vagrantc>

i'd be fine with .rst too ... though i've got more other projects using markdown, so minor bias in that direction

17:59

though until we have something to document for ltsp6, it's a bit premature to worry about that

18:03

!todo

18:03

<ltsp>

I do not know about 'todo', but I do know about these similar topics: 'bennabiy_todo', 'todo-jammcq-sbalneav', 'alkisg-todo'

18:03

<vagrantc>

!alkisg-todo

18:03

<ltsp>

alkisg-todo: (#1) support xnbd-proxy for local caching: https://bitbucket.org/hirofuchi/xnbd/wiki/Home#!scenario-2-simple-proxy-server-distributed-copy-on-write, or (#2) Support UEFI, or (#3) support for per-user login commands in lts.conf, or (#4) put panic=60 in the kernel cmdline, or (#5) document bind-interfaces, or (#6) test the null cipher with https://launchpad.net/~yoda-jazz-kc/+archive/ubuntu/hpn-ssh, or (#7) (1 more message)