IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 3 October 2018   (all times are UTC)

00:07vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
03:30adrianor1 has joined IRC (adrianor1!~adrianorg@189.58.224.211.dynamic.adsl.gvt.net.br)
03:31adrianorg has left IRC (adrianorg!~adrianorg@187.115.109.233, Ping timeout: 252 seconds)
04:12lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br)
05:00alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
05:05alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:38kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87)
05:53alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
05:59alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
06:32kjackal has left IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87, Ping timeout: 252 seconds)
07:01kjackal has joined IRC (kjackal!~quassel@ppp-94-66-232-238.home.otenet.gr)
07:11alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
07:15alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
07:19Natureshadow has left IRC (Natureshadow!45d1515d22@commu.teckids.org, *.net *.split)
07:47jgee has left IRC (jgee!~jgee@190.159.118.121, Ping timeout: 245 seconds)
08:10
<alkisg>
!screenshot
08:10
<ltsp>
screenshot: to upload a screenshot use a site like https://prnt.sc/ or https://snag.gy/ and then paste the URL here
09:20
<Hyperbyte>
Yesplease.
10:01
<alkisg>
!bug
10:01
<ltsp>
bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
10:04gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
10:58kjackal has left IRC (kjackal!~quassel@ppp-94-66-232-238.home.otenet.gr, Ping timeout: 252 seconds)
11:24kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87)
12:31vsuojanen has left IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com, Remote host closed the connection)
12:46Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:54mwalters has joined IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net)
12:55vsuojanen has joined IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
13:17Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
15:06lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Remote host closed the connection)
15:23lucascastro has joined IRC (lucascastro!~lucascast@189.90.38.210.jupiter.com.br)
16:16gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:23adrianor1 is now known as adrianorg
16:50vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:02lucascastro has left IRC (lucascastro!~lucascast@189.90.38.210.jupiter.com.br, Remote host closed the connection)
17:15lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br)
17:17
<alkisg>
vagrantc: heya, did you see the new one? :D https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910216
17:17
That removal was there since ages, I don't know why they just saw it now...
17:17
I'm not sure how to handle this either; if that conffile stays there it launches epoptes twice and it's causing issues now with systemd
17:18
And https://wiki.debian.org/DpkgConffileHandling does say we can remove it on preinst etc
17:18
So I don't know why piuparts complains...
17:21
<vagrantc>
alkisg: yes
17:21
alkisg: it's done improperly
17:21
<alkisg>
What's the correct way to do it?
17:21
<vagrantc>
alkisg: the removal should use dpkg-maintscript-helper
17:21
i'll fix it
17:22
<alkisg>
Isn't that just one option out of all those referenced in that wiki page?
17:22
And we're just using another option of that wiki page?
17:22
Thanks, if you take care of it I don't need to learn more about it :D
17:22
<vagrantc>
forcefully manually removing it breaks policy
17:22
e.g. if a user modified it, for better or worse, we cannot forcefully remove it
17:23
<alkisg>
It's not a configuration file though, it's code :/
17:23
So it'll just result in epoptes not starting properly. But ok I get it :/
17:23
I should probably have used a symlink instead there
17:24* vagrantc finds symlinks in /etc very dangerous ... since an admin might edit the file outside of /etc without realizing it
17:25
<alkisg>
Eh, if he edited our code in /usr/share/epoptes/if-up-script without realizing it, it'd be fine to delete it in newer versions :D
17:25
So we'd be fine policy-wise, and epoptes would start fine too :D
17:26
# find /etc -type l | wc -l
17:26
1047
17:26
Not uncommon...
17:29
<vagrantc>
i know
17:29
by forcefully deleting it in preinst, if the upgrade fails, it can't rollback to the working version, though
17:29
at least, that's the simplest of the million corner cases
17:30
basically, it comes down to the fact that debian packaging is too complicated, and so a lot of crazy stuff needs to be done to handle all the supported installation, upgrade, failed-install, failed-upgrade, etc.
17:34
alkisg: and the wiki page you referenced you didn't follow any of their examples :P
17:34
<alkisg>
Hehe
17:35
<vagrantc>
alkisg: the very first line suggest using dpkg-maintscript-helper ... but even if you ignore that, all of the given examples are much more complicated :P
17:38
<alkisg>
Actually ifupdown should have given us an if-up.d dir in /usr, so /etc wouldn't even be involved then
17:39
Like systemd does with /lib/systemd/*
17:39
<vagrantc>
sure
17:40
best practices of today are shoehorned on top of the best practices of yesterday :)
17:53lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Remote host closed the connection)
18:08lucascastro has joined IRC (lucascastro!~lucascast@189.90.45.62.jupiter.com.br)
18:42
<alkisg>
Btw I synced epoptes 1.0 to Ubuntu 18.10... best to support 0.5 as little as possible
18:48lucascastro has left IRC (lucascastro!~lucascast@189.90.45.62.jupiter.com.br, Quit: Leaving)
18:49adrianor1 has joined IRC (adrianor1!~adrianorg@189.58.181.181.dynamic.adsl.gvt.net.br)
18:51adrianorg has left IRC (adrianorg!~adrianorg@189.58.224.211.dynamic.adsl.gvt.net.br, Ping timeout: 268 seconds)
19:06
<mwalters>
hmm, ldm seems to be segfaulting in the 18.04 test environment I set up (on the client)
19:07
<vagrantc>
segfaulting! exciting...
19:09
<mwalters>
segfaults twice even!
19:09
one segfault just isn't enough
19:11lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br)
19:20
<mwalters>
no more segfault, but doesn't ever seem to start X. Suck at "[ OK ] Started update UTMP about runlevel changes"
19:21
I did change the IP of the server, ran ltsp-update-sshkeys
19:21
<vagrantc>
ip address shouldn't matter anymore- modern versions of ldm run without strict checking
19:21
it only checks that the key matches
19:22
<mwalters>
oic
19:56
dist-upgrading and not getting tftp now =/... can manually tftp to it, though
20:00
<alkisg>
!install
20:00
<ltsp>
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
20:00
<alkisg>
mwalters: are you following that one, or something else?
20:03
<mwalters>
yeah, I followed that one
20:03
client was getting tftp at least before I ran dist-upgrade and rebooted
20:03
<alkisg>
mwalters: with or without chroots?
20:03
<mwalters>
with chroot
20:04
<alkisg>
Do you have the ppa in the chroot?
20:05
<mwalters>
nope :D
20:09
<alkisg>
There are many, many known issues with ltsp in 18.04, if you're not using the ppa
20:10
You really don't want to troubleshoot those again; I already did that in the summer :)
20:11
<mwalters>
Pretty sure I followed directions in that exactly, I don't see where it says I need to explicitely add the source to the chroot
20:11
<alkisg>
ltsp-build-client --purge-chroot --mount-package-cache --extra-mirror 'http://ppa.launchpad.net/ts.sch.gr/ppa/ubuntu bionic main' \
20:11
That line adds the ppa to the chroot
20:11
If you did it as it says, you already have it
20:11
<mwalters>
yeah, p sure I copy/pasted that
20:11
<alkisg>
sudo ltsp-info ==> will tell us
20:11
<mwalters>
it wasn't in sources in the chroot
20:12
or in or in sources.list.d
20:12
dunno, maybe I goofed
20:13
<alkisg>
I think I just tried the chroot method once... but I think it did work
20:13
<mwalters>
yeah, I'm rebuilding it and we'll see what happens
20:22
after rerunning the build client copy/pasted from the wiki, I don't see the ppa in the chroot
20:23
<alkisg>
what's the output of `sudo ltsp-info | nc termbin.com 9999`?
20:23
<mwalters>
should be in either /opt/ltsp/amd64/etc/apt/sources.list or a file in /opt/ltsp/amd64/etc/apt/sources.list.d/, right?
20:23
from the host or the chroot?
20:23
<alkisg>
host
20:24
<vagrantc>
doesn't it also need another keyring?
20:24
<alkisg>
--apt-keys '/etc/apt/trusted.gpg.d/ts_sch_gr_ubuntu_ppa.gpg' --late-packages epoptes-client
20:24
It's there in the wiki...
20:24
<mwalters>
root@test-server:/opt/ltsp/amd64/etc/apt# ltsp-info | nc termbin.com 9999
20:24
sh: 0: getcwd() failed: No such file or directory
20:24
<vagrantc>
ah.
20:24
<mwalters>
No LSB modules are available.
20:24
http://termbin.com/te7u
20:24
<alkisg>
mwalters: you are "cd"'ed to a directory that you moved/deleted
20:25
<mwalters>
ops
20:25jgee has joined IRC (jgee!~jgee@190.159.118.121)
20:25
<alkisg>
Your package versions show that you do have the ppa in the chroot
20:26
You can verify with `sudo ltsp-chroot apt policy ldm` etc
20:26
<mwalters>
root@test-server:~# ltsp-info | nc termbin.com 9999
20:26
No LSB modules are available.
20:26
http://termbin.com/n2wi
20:26
root@test-server:~#
20:27
https://pastebin.com/akefiKTR
20:27
<alkisg>
Can you paste the errors/segfaults that you see on the client?
20:27
<mwalters>
it stopped doing that, haven't restarted a client since rebuilding
20:27
<alkisg>
And `getltscfg -a` from a client might help as well
20:27
<mwalters>
yeah, I'll get that tomorrow, gotta run in just a minute
20:27
thanks
20:28
<alkisg>
bb
21:04lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Remote host closed the connection)
23:07GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 252 seconds)