01:17 | gdi2k has joined IRC (gdi2k!~gdi2k@112.208.205.80) | |
01:26 | gdi2k has left IRC (gdi2k!~gdi2k@112.208.205.80, Read error: Connection reset by peer) | |
03:53 | Hyperbyte has left IRC (Hyperbyte!~jan@middelkoop.cc, Ping timeout: 256 seconds) | |
05:29 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
05:40 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
06:36 | <enaut[m]> alkisg: is this dbus only used in maintenance and therefor not relevant for ltsp-manager? https://git.launchpad.net/sch-scripts/commit/?id=dcdd25d34d8a5c7aae8c69b66470300d3c580bb8
| |
06:37 | ah package removal is actually the stuff done in ip_dialog - is it?
| |
06:38 | <alkisg> enaut[m]: possibly, if `grep -r dbus` in ltsp-manager doesn't have any dbus calls, then that's not needed
| |
06:38 | Package removal is in maintenance
| |
06:38 | I think that both package removal and ip dialog have dbus calls
| |
06:38 | Anyway, if you run ltsp-manager from the command line and you don't see any dbus error messages, you're fine
| |
06:39 | It would show errors and I think hang, if you used dbus and didn't have that loop call
| |
06:39 | <enaut[m]> ok
| |
06:40 | in ip_dialog dbus is used so i probably need this.
| |
06:41 | but this code ip_dialog code is old...
| |
06:54 | <alkisg> enaut[m]: you could try to merge my recent sch-scripts changed back to ltsp-manager, if you like
| |
06:54 | *changes
| |
06:57 | <enaut[m]> alkisg: I'm in the process of selecting and cherry-picking/recreating the relevant commits... sometimes it is hard because I do not know the code base...
| |
07:01 | Natureshadow has left IRC (Natureshadow!45d1515d22@commu.teckids.org, Remote host closed the connection) | |
07:04 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Remote host closed the connection) | |
07:08 | deepanshuG has joined IRC (deepanshuG!~d78ui98@171.61.39.195) | |
07:08 | <deepanshuG> has ltsp manager been removed?
| |
07:09 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
07:17 | <alkisg> deepanshuG: removed from where? It hasn't been published in Debian or Ubuntu...
| |
07:17 | Well, it got in debian experimental, but not in testing or in any release
| |
07:18 | <deepanshuG> http://wiki.ltsp.org/wiki/Ltsp-manager. Almost a week ago I was able to use it on linux mint
| |
07:18 | now It says unable to find ltsp-manager.
| |
07:20 | <alkisg> deepanshuG: ah you mean the Greek schools ppa? Yeah I removed it from the PPA and only for the 18.04 series, as it hasn't been tested there, and it has known serious issues
| |
07:20 | It's still there for 16.04 of course
| |
07:21 | <deepanshuG> alkisg, ohh okay. Thanks for informing.
| |
07:21 | <alkisg> np
| |
07:26 | deepanshuG has left IRC (deepanshuG!~d78ui98@171.61.39.195, Quit: Leaving) | |
07:26 | Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc) | |
07:29 | <enaut[m]> alkisg: ok now I'm done... I will test the ltsp-manager on the school install because here at home I have limited testing capabilities - (Or you could just quickly run it on your fully automated virtual testing environment ;) )
| |
07:30 | <alkisg> enaut[m]: I don't have such a thing, maybe you meant the gsoc student, deepanshuG?
| |
07:30 | AFAIK he's the one working in virtual environments for ltsp
| |
07:31 | <enaut[m]> (wasn't expecting it was rather meant as a joke...)
| |
07:32 | <alkisg> Ah, ok, sorry for spoiling it :)
| |
07:32 | <enaut[m]> alkisg: Is there something to do for the testing - except for *press all the buttons* and *enter all the wrong and right data*?
| |
07:33 | <alkisg> That would be it. :)
| |
07:37 | <enaut[m]> alkisg I noticed that the starter script swallows most of the output - which sometimes makes it hard to find errors why is that? (the pipe "| exec_input")?
| |
07:39 | <alkisg> enaut[m]: ltsp-manager needs to run as root, yet some of its features like "open the irc web page" need to run as the user
| |
07:39 | So this is a trick for the root process to ask the initial user process "open this web page" and some other features
| |
07:40 | In an ideal design, all the GUI would run as the user, and a backend would be running as root, but that would take months to reimplement
| |
07:41 | And in that ideal design ltsp-manager would get split into a "normal unix account manager" and some ltsp-config scripts, i.e. it wouldn't be ltsp-manager anymore...
| |
07:44 | <enaut[m]> ah now I get it...
| |
07:46 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
08:19 | deepanshuG has joined IRC (deepanshuG!~d78ui98@171.61.58.117) | |
08:20 | <deepanshuG> hehe
| |
08:21 | * vagrantc waves | |
08:21 | <deepanshuG> hey
| |
08:23 | <alkisg> Heeey vagrantc :)
| |
08:24 | GSoC is pretty much finished, we'll merge the code soonish, but I also have this branch for merging to debian-master: https://github.com/eellak/gsoc2018-epoptes/tree/gsoc2018-debian
| |
08:25 | <vagrantc> cool
| |
08:25 | <alkisg> What workflow would you advice for that part? Would you like me to do a pull request in github, so that you can then merge it, do your code sync changes and release it?
| |
08:25 | <vagrantc> i clearly had no time during debcamp/debconf to do any of it :)
| |
08:25 | <alkisg> No worries it wasn't ready yet
| |
08:26 | <vagrantc> alkisg: that's for epoptes?
| |
08:26 | <alkisg> I could also do everything myself if needed, maybe even upload it to testing, but it's always better when you put your hand in it
| |
08:26 | Yup
| |
08:26 | <vagrantc> uploads go via unstable, but sure ...
| |
08:26 | <alkisg> While the main code is at https://github.com/Epoptes/epoptes/pull/63
| |
08:27 | That one will be merged upstream by fotis in a couple of days
| |
08:27 | <vagrantc> great
| |
08:27 | <alkisg> So? A pull request that you approve sounds like a plan?
| |
08:27 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Ping timeout: 244 seconds) | |
08:27 | <vagrantc> alkisg: give me a few days to start and finish my upcoming jetlag :)
| |
08:28 | alkisg: i don't know that i've ever done a github pull request
| |
08:28 | :)
| |
08:28 | <alkisg> Sure, no worries; but if you agree to that workflow, I can do the PR, put the link in my deliverables, and you can approve it whenever you have time, even weeks later
| |
08:28 | <vagrantc> i've done a couple with salsa.debian.net (at least once by accident)
| |
08:28 | <alkisg> Basically you just press Merge in a github button
| |
08:28 | <vagrantc> alkisg: main thing is to keep the upstream changes separate from the packaging
| |
08:28 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
08:29 | <alkisg> This then merges and pushes the result in the git branch, so we just pull to refresh
| |
08:29 | vagrantc: sure, that's exactly what I've done, and it was because you asked me to do it this way
| |
08:29 | <vagrantc> alkisg: thanks for trying it out :)
| |
08:30 | alkisg: actually, there's a new tool which might fit your desired workflow better ... git-debrebase
| |
08:30 | in conjunction with dgit
| |
08:30 | or independently
| |
08:31 | so now that i've convinced you to try this... :)
| |
08:31 | <alkisg> What was a bit hard with it was if I wanted to try an earlier epoptes version, e.g. from July 20th; in that case I had to also go to the debian branch and checkout that earlier date. But it wasn't that hard so OK.
| |
08:32 | * alkisg didn't understand though if vagrantc says "alkis, do the merge" or if he says "vagrantc will do the merge" :) | |
08:33 | <vagrantc> alkisg: i'd like to get a chance to review it, but go ahead with the pull request
| |
08:33 | <alkisg> vagrantc: OK, so I do the pull request and you can review it there for as long as you like
| |
08:33 | It supports discussion and I can add new commits etc, so it should be fine
| |
08:34 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Ping timeout: 268 seconds) | |
08:34 | <vagrantc> that gets your GSoC report something concrete
| |
08:34 | <alkisg> You'll get a mail that a PR was assigned to you in an hour or so
| |
08:34 | <vagrantc> basically working with python3 and other new libraries?
| |
08:35 | <alkisg> It's a better permanent link, yeah; although the main PR is e.g. 3000 lines and that one just 100, so it's not too important, but still it's nice for consistency
| |
08:35 | <vagrantc> maybe switching the vnc viewer again?
| |
08:35 | <alkisg> Python3, Gtk3, systemd, plus lots of fixes
| |
08:35 | <vagrantc> great
| |
08:35 | <alkisg> xvnc4viewer is great for Ubuntu, but we'd need to see if it can get to debian again since it was removed
| |
08:35 | <vagrantc> (doesn't that generally mean it'll get removed from Ubuntu eventually?)
| |
08:35 | <alkisg> At least for buster it would be a lot better than the alternatives
| |
08:36 | No, Ubuntu chose to keep it even though it was removed from debian a couple of ubuntu releases ago
| |
08:36 | <vagrantc> it's getting a bit late for buster... but i got the impression the remote desktop team or whatever abandoned it
| |
08:36 | so might need new maintainers
| |
08:37 | e.g. US
| |
08:37 | <alkisg> The other vnc viewers also have no maintainers, but at least xvnc4viewer works fine
| |
08:37 | <vagrantc> ah
| |
08:38 | <alkisg> We could do that temporarily for buster, while for later on, we should change epoptes to use a vnc library instead of an application
| |
08:40 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
08:40 | <alkisg> Ah, https://metadata.ftp-master.debian.org/changelogs/main/t/tigervnc/tigervnc_1.9.0+dfsg-1_changelog => tigervnc is in buster again
| |
08:42 | <vagrantc> ah, so we won't have to do anything with regards to that, then
| |
08:43 | heh. it was removed on july 27th and then migrated again on the 28th.
| |
08:43 | gotta head out for now
| |
08:44 | * vagrantc waves | |
08:44 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
08:45 | deepanshuG has left IRC (deepanshuG!~d78ui98@171.61.58.117, Quit: Leaving) | |
08:45 | <enaut[m]> alkisg: I pushed the changes I made so far to: https://code.launchpad.net/~franz-die/ltsp-manager/+git/ltsp-manager - just in case you are interested ;)
| |
08:46 | <alkisg> enaut[m]: thanks, but nah, I don't want to maintain 2 forks, ltsp-manager and sch-scripts...
| |
08:46 | If you want to become the maintainer though, I can give you access wherever you need
| |
09:08 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
09:31 | <enaut[m]> I'll make it rocksolid and will see if I can find enough time... (I don't want to claim maintainership and just dump it afterwards)
| |
09:51 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Ping timeout: 272 seconds) | |
10:05 | TatankaT has left IRC (TatankaT!~tim@heracles-ng.oma.be, Ping timeout: 256 seconds) | |
10:59 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
12:30 | adrianor1 is now known as adrianorg | |
13:00 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Ping timeout: 272 seconds) | |
13:07 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
14:45 | TatankaT has joined IRC (TatankaT!~tim@heracles-ng.oma.be) | |
14:50 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
15:01 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
15:48 | Helenah has joined IRC (Helenah!d49f2d5f@gateway/web/freenode/ip.212.159.45.95) | |
15:48 | <Helenah> Ohai
| |
15:49 | I'm wanting to set up a public storage area on the LTSP server where client endusers can share files with each other.
| |
15:50 | I tried setting fstabs in lts.conf, however after it didn't work, I'm not sure what to do, or if I'm setting up public areas correctly.
| |
17:36 | alkisg has joined IRC (alkisg!c15ccb10@ubuntu/member/alkisg) | |
18:42 | alkisg has left IRC (alkisg!c15ccb10@ubuntu/member/alkisg, Quit: Page closed) | |
18:48 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
19:13 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
19:58 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
20:32 | Helenah has left IRC (Helenah!d49f2d5f@gateway/web/freenode/ip.212.159.45.95, Ping timeout: 252 seconds) | |
21:32 | lucascastro has left IRC (lucascastro!~lucascast@177-185-139-236.isotelco.net.br, Read error: Connection reset by peer) | |
21:33 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-236.isotelco.net.br) | |