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


Channel log from 4 April 2015   (all times are UTC)

00:21
<MarconM>
!ltsp-pnp
00:21
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
00:38championofcyrodi has left IRC (championofcyrodi!~cott@50-205-35-98-static.hfc.comcastbusiness.net, Ping timeout: 252 seconds)
01:00gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Remote host closed the connection)
01:19Excedere has joined IRC (Excedere!d046b605@gateway/web/freenode/ip.208.70.182.5)
01:22
<Excedere>
Hey all, trying to get ltsp-build-client to run. I specified the location of the Release file in the .conf file, however it is still failing due to unknown location. Any suggestions?
02:00gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
02:09gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 250 seconds)
02:24MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Ping timeout: 244 seconds)
02:25MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
02:33MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Ping timeout: 265 seconds)
02:34MarconM has joined IRC (MarconM!~Marcelo@179.254.52.68)
02:34MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
02:43MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Ping timeout: 252 seconds)
03:43
<Excedere>
bump
04:25MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
04:52Excedere has left IRC (Excedere!d046b605@gateway/web/freenode/ip.208.70.182.5, Quit: Page closed)
04:53work_alkisg is now known as alkisg
04:54telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
04:56telex has joined IRC (telex!teletype@freeshell.de)
05:03MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Quit: Leaving)
05:08
<alkisg>
vagrantc: hi! Is r1229 in https://code.launchpad.net/~vagrantc/ltsp/ltsp-debian-packaging supposed to be working against ltsp-trunk?
05:28
<vagrantc>
alkisg: not sure what you mean exactly
05:28
alkisg: that's just a changelog entry, no?
05:28
<alkisg>
vagrantc: let's start with this first:
05:28
https://code.launchpad.net/~alkisg/+recipe/ldm-daily
05:28
With the previous recipe, I just got a failed build,
05:28
then I appended revno:1574 in the recipe for ldm,
05:28
<vagrantc>
the debian-packaging branches are not targeted at trunk.
05:29
<alkisg>
and now I got a succesfull build
05:29
Right
05:29
<vagrantc>
they're targeted at whatever version is in debian
05:29
<alkisg>
So, what revno should I be using for the ltsp package?
05:29
I.e. what revno did you use in debian?
05:29
<vagrantc>
the tagged upstream version
05:29
alkisg: so in the case of the commit you reference, ltsp-5.5.4
05:30
<alkisg>
So, r2614
05:30
But vagrantc we don't have a way to easily test trunk now
05:31
Is it possible to keep different branches per debian releases, so that you also have one for -trunk?
05:31
I wouldn't be handy to have to pull your packaging, apply a diff, push to launchpad, and *then* call a recipe to do a daily build...
05:31
*it
05:33
How are you managing it currently? Do you have one branch per debian release?
05:38
<vagrantc>
i rarely have to maintain more than one or two branches
05:39
i can see the value in a daily build, but don't have the time to target another moving target
05:39
not that it's been moving much lately...
05:43gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
05:47gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 244 seconds)
05:48
<alkisg>
vagrantc: but won't you have to update the package anyway at some point?
05:48
Why do you consider it additional overhead?
05:51
Example:
05:51
You push this to ltsp-trunk: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2618 - Debian: Remove ltsp-build-client plugin pulseaudio-tweaks, as the
05:51
customizations are no longer needed.
05:52
That requires the respective quilt patch to be removed in debian/patches
05:52
If you do it at that time, in e.g. the "ltsp-trunk-debian-packaging" or "ltsp-debian-experimental-packaging" - however you want to call it,
05:53
then you don't have to figure out why packaging is broken at some later point when you'll be doing a release in e.g. experimental or unstable...
05:53
I.e. you're maintaining one packaging branch, and you're only doing the work once
05:55
vagrantc: If you want me to help in co-maintaining that branch, I'd be glad to
05:55
I could do simple things like dropping patches without asking you, and if there's something more significant then I would ping you
05:56
Otherwise I have to do double the work, to maintain that branch _and_ sync it with yours once in a while; I've done that in the past and I didn't like it...
05:56
:)
06:11
<vagrantc>
alkisg: when trunk was more active, not following it saved me from having to figure out all sorts of issues that got sorted out in trunk in 3-4 different ways
06:12
i only had to adjust packaging once rather than 3 or 4 times
06:12
<alkisg>
vagrantc: I offer to do that for you if you want
06:12
*for me, actually, but in your branch :)
06:12
I just hate duplicate work
06:12
<vagrantc>
alkisg: what do you mean by "in my branch" ?
06:12
<alkisg>
I mean that I would have to do the packaging changes in order to build it
06:12
In some local packaging branch
06:13
<vagrantc>
i've never used bzr's multiple branches in a single repository support ...
06:13
<alkisg>
Then when you did the same changes in your branch, I would have to sync it with mine
06:13
I mean that you could give me commit access to the packaging branch...
06:13
I'd be careful, no worries :)
06:14
<vagrantc>
i'm just not sure what you mean by it being my branch, as currently the branches are maintained in the pkg-ltsp project branches.
06:14
<alkisg>
Do I have commit access there?
06:15
<vagrantc>
i'd be happy to get you commit access!
06:15
alkisg: you'll need an account on alioth.debian.org
06:15
<alkisg>
I do have a guest account there, but...
06:15
<vagrantc>
ok, i'll need to figure out how to give you commit access
06:16
honestly, i've really been tempted to do the debian packaging in a merged upstream/master git branch lately...
06:16
er, merged packaging/master branch.
06:16
<alkisg>
...if I'll be synching the packaging with ltsp-trunk, and you want the older packaging version e.g. to issue a security update for jessie, will you have an issue with that?
06:16
We can easily move ltsp to github :)
06:16
<vagrantc>
meh.
06:17
oh, you mean as a projecT?
06:17
<alkisg>
Yeah
06:17
All the new projects do that :P
06:17* alkisg doesn't really care about bzr vs git as long as the overhead is low
06:17
<vagrantc>
it took ages, but at least the launchpad platform was finally opened up...
06:18
<alkisg>
I.e. I don't want to manually sync git + bzr + translations from 10 different sites
06:18* vagrantc nods
06:18* vagrantc is using git-remote-bzr for most bzr work these days
06:19
<vagrantc>
works fine for everything but tagging versions
06:19
<alkisg>
vagrantc: did you get a mail about half an hour ago, with this subject? [recipe build #899428] of ~alkisg ltsp-daily in trusty: Failed to build
06:19
I was hoping not to bother the other ltsp devs with failed builds, so I put the recipes in my own account
06:20
So if you didn't get that mail, it's working
06:20
<vagrantc>
haven't seen anything
06:20
<alkisg>
Cool
06:21
<vagrantc>
alkisg: i suppose you're wanting to resolve all this stuff before debconf :)
06:21
<alkisg>
vagrantc: people here are asking to test the ldm hash password fix etc, I just wanted to have a way to provide them with a newer ltsp version
06:21
Ubuntu doesn't even have the Jessie version yet
06:22
I think stgraber doesn't have much time for LTSP nowadays, I wish he'd drop all the Ubuntu-specific bits and just sync with Debian
06:22
<vagrantc>
have you run into the issue with pxelinux.0 and related files not getting copied?
06:22
<alkisg>
No I haven't used anything beyond 14.04 yet so I haven't seen it
06:22
Is it solved?
06:23
(in debian..)
06:23
<vagrantc>
upstream and in debian, but i think 14.10 results in a non-booting LTSP
06:23
<alkisg>
highvoltage, ogra_, maybe you can ping stgraber about that ^?
06:23
<vagrantc>
i haven't yet tested for sure, but i've seen a few folks mention it
06:24
<alkisg>
Marcomn also mentioned it for Lubuntu 14.10
06:24
2 days ago
06:24
I would also like to fix the DESKTOP_SESSION bit upstream
06:24
But it's broken in the Ubuntu packaging
06:24
<vagrantc>
the workaround is apparently to switch to Debian :)
06:24
<alkisg>
So I don't have commit access to fix it
06:24
I'd be glad to, except that I'd have to solve another 1000 problems unrelated to LTSP
06:25
E.g. that the default font doesn't contain Greek characters
06:25
(Ubuntu also had 1000 other issues, but over the years we found some workarounds, solved some of them etc)
06:25
And I'm worried about new hardware support in Debian
06:26
I.e. how will I send new kernels to the schools that have new hardware, when the stable release is e.g. 2 years old....
06:26
I think the solution here is for stgraber to stop maintaining ltsp in Ubuntu
06:26
And just let it sync with Debian
06:27
<vagrantc>
the differences are mostly in the ltsp-client-builder udeb, as I recall.
06:27
and the upstream bits, but those would be syncable
06:27
<alkisg>
There's ltsp-cluster, but I don't think it works anymore,
06:27
There's some Ubuntu-specific scripts like 40-ltsp-client and 40-ltsp-server, for DESKTOP_SESSION, which shouldn't be in debian/ really, but upstream,
06:28
And the theme dependencies, which I think we fixed with X-Ubuntu-Depends etc...
06:28
No those were for LDM, which is synced already
06:28
LTSP has some font dependencies
06:28
(which I don't believe are needed anyway)
06:29
stgraber: I'd be glad to do and test the packaging merge if you'll allow me
06:30* alkisg waves for now
06:30alkisg is now known as work_alkisg
06:30* vagrantc waves too
06:30
<vagrantc>
till next time!
06:30vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
06:32ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
08:14fiesh has joined IRC (fiesh!~fiesh@hq.wsoptics.de)
09:16khildin has joined IRC (khildin!~khildin@ip-213-49-85-2.dsl.scarlet.be)
10:12alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
10:30alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
10:37book` has left IRC (book`!~book`@105.ip-167-114-152.net, Ping timeout: 272 seconds)
10:41book` has joined IRC (book`!~book`@105.ip-167-114-152.net)
10:44ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 264 seconds)
10:47ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
12:19khildin has left IRC (khildin!~khildin@ip-213-49-85-2.dsl.scarlet.be, Quit: I'm gone, bye bye)
13:04gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
13:46work_alkisg is now known as alkisg
13:53izzle121 has joined IRC (izzle121!~izzle121@d-206-53-82-160.cpe.metrocast.net)
15:13adrianorg has left IRC (adrianorg!~adrianorg@177.156.225.76, Ping timeout: 256 seconds)
15:15adrianorg has joined IRC (adrianorg!~adrianorg@187.115.107.74)
15:21alkisg is now known as work_alkisg
15:39vmlintu has joined IRC (vmlintu!~vmlintu@37-219-7-80.nat.bb.dnainternet.fi)
15:49vmlintu has left IRC (vmlintu!~vmlintu@37-219-7-80.nat.bb.dnainternet.fi, Ping timeout: 256 seconds)
16:14MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
16:24telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
16:26telex has joined IRC (telex!teletype@freeshell.de)
16:37MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Quit: Leaving)
17:03AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-ojuekwjuacglhazm)
17:29yanu_ has joined IRC (yanu_!~yanu@d1F05B2CD.access.telenet.be)
17:29yanu has left IRC (yanu!~yanu@d1F05B2CD.access.telenet.be, Read error: Connection reset by peer)
19:17AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-ojuekwjuacglhazm, Quit: Connection closed for inactivity)
19:42ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
19:59gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, )
20:14vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
20:43vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
21:26adrianorg has left IRC (adrianorg!~adrianorg@187.115.107.74, Read error: Connection reset by peer)
21:32adrianorg has joined IRC (adrianorg!~adrianorg@187.115.107.74)
21:49adrianorg has left IRC (adrianorg!~adrianorg@187.115.107.74, Ping timeout: 264 seconds)
22:32gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
23:02gbaman_ has joined IRC (gbaman_!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
23:06gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 264 seconds)
23:58adrianorg has joined IRC (adrianorg!~adrianorg@186.215.22.196)