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


Channel log from 30 March 2013   (all times are UTC)

00:11vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
00:13gbaman has left IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com, Ping timeout: 245 seconds)
00:16gbaman has joined IRC (gbaman!~gbaman@host81-130-88-58.in-addr.btopenworld.com)
00:19andygraybeal_ has joined IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net)
00:29gentgeen__ has left IRC (gentgeen__!~kevin@c-98-239-202-150.hsd1.pa.comcast.net, Ping timeout: 248 seconds)
00:41gentgeen__ has joined IRC (gentgeen__!~kevin@c-98-239-202-150.hsd1.pa.comcast.net)
00:50andygraybeal_ has left IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net, Ping timeout: 240 seconds)
01:21Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 252 seconds)
02:01andygraybeal_ has joined IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net)
02:12alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
02:13alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Ping timeout: 255 seconds)
02:14andygraybeal_ has left IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net, Ping timeout: 240 seconds)
02:23otwieracz has left IRC (otwieracz!~gonet9@v6.gen2.org, Ping timeout: 246 seconds)
02:24otwieracz has joined IRC (otwieracz!~gonet9@v6.gen2.org)
02:48leio_ has joined IRC (leio_!~leio@gentoo/developer/leio)
02:50telex has left IRC (telex!~telex@freeshell.de, Disconnected by services)
02:51telex has joined IRC (telex!~telex@freeshell.de)
02:55leio has left IRC (leio!~leio@gentoo/developer/leio, *.net *.split)
02:55stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, *.net *.split)
02:55lotharn has left IRC (lotharn!~taco@24.154.55.32, *.net *.split)
03:00stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
03:03lotharn has joined IRC (lotharn!~taco@24.154.55.32)
04:52hzlshndlozve has joined IRC (hzlshndlozve!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
04:52|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Read error: Connection reset by peer)
04:53hzlshndlozve is now known as |Paradox|
05:05alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:15alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
05:17alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Ping timeout: 252 seconds)
05:21alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
05:46
<ajith>
some of thin clients are unable to boot as in our offices we are having branches located in different..
05:46
prroviously they used to boot ..but now they are stopping at Ubuntu logo
05:46
no network issues everything is fine
05:47
any idea??
06:19komunista has joined IRC (komunista!~slavko@87.244.209.121)
06:52
<ajith>
discover failed...no lease found
06:52
in ltsp ubutnu
08:20
what does that mean
08:23komunista has left IRC (komunista!~slavko@87.244.209.121, Ping timeout: 255 seconds)
08:26
<Hyperbyte>
ajith, dhcp problem?
08:27
<ajith>
dhcp problem ..hey my system are able to boot
08:28
some of them..but others cant
08:38
getaddrinfo:name or service not known
08:41
<Hyperbyte>
What happens if you swap their network connections?
08:42
(I'm just guessing here)
08:47
<ajith>
getaddrinfo:name or service not known
08:47
what does this mean Mr.Hyper
08:49
<Hyperbyte>
It means it tried to do a lookup on some address, but that name or service isn't known by the system
08:49
I have no idea how that relates to LTSP though, Iá'm not an LTSP developer. Like I said, it might be DHCP related.
08:50
It might also help if you could put the error message into context. For example, publish a complete log of all the things that appear on screen, so we can see -where- exactly that error appears.
08:57komunista has joined IRC (komunista!~slavko@87.244.209.121)
09:23andygraybeal_ has joined IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net)
09:50
<ajith>
okay the log dont have any error
09:59
what is getaddr info:name or service not known
10:09markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
10:10Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
10:11khildin has joined IRC (khildin!~khildin@ip-83-134-215-251.dsl.scarlet.be)
10:12markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, Client Quit)
10:13andygraybeal_ has left IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net, Ping timeout: 240 seconds)
10:20alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
10:40
<Enslaver>
Hmm having an issue with my fat clients, I can log into them fine but when my screen locks it won't take password, no entry for my user in shadow but there is in passwd
10:41
<alkisg>
Enslaver: I had asked for ldm to store the hash of the password in shadow; the other devs didn't like it due to security reasons
10:41
Let's see if libpam_sshauth has an option to support that in the future
10:41
So for now we just disable screen locking
10:42
<Enslaver>
:(
10:42
I guess there's good and bad about that
11:12Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
11:20Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
11:42lotharn has left IRC (lotharn!~taco@24.154.55.32, Ping timeout: 246 seconds)
11:42lotharn has joined IRC (lotharn!~taco@24.154.55.32)
11:43lotharn has joined IRC (lotharn!~taco@24.154.55.32)
12:00alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
12:02alexqwesa_ has left IRC (alexqwesa_!~alex@109.172.12.47, Ping timeout: 245 seconds)
12:04alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Client Quit)
12:04awilliam1 has joined IRC (awilliam1!~awilliams@unaffiliated/mistik1)
12:06awilliams has left IRC (awilliams!~awilliams@unaffiliated/mistik1, Ping timeout: 272 seconds)
12:06awilliam1 is now known as awilliams
12:13alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
12:26alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Read error: Connection reset by peer)
12:26alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
12:33alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Quit: Хана X'ам !!!)
12:33alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
12:36alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Client Quit)
12:36alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
12:50alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Quit: Хана X'ам !!!)
12:50alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
12:50komunista has left IRC (komunista!~slavko@87.244.209.121, Ping timeout: 245 seconds)
13:02highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 245 seconds)
13:07ajith has left IRC (ajith!b7522f02@gateway/web/freenode/ip.183.82.47.2, Quit: Page closed)
13:08vnc786 has left IRC (vnc786!~chatzilla@49.248.129.178, Quit: ChatZilla 0.9.90 [Firefox 19.0.2/20130307023931])
13:24markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
13:27highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
13:27
<markit>
alkisg: the friend of mine has still the same problem with the new class, we have reinstalled everything from scratch. I've noticed in teh home a strange directory. "d????????? ? ? ? ? ? .gvfs" does it trigger somethign on your mind?
14:23vagrantc has joined IRC (vagrantc!~vagrant@c-98-232-129-196.hsd1.or.comcast.net)
14:23vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
14:49komunista has joined IRC (komunista!~slavko@87.244.209.121)
14:50|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Ping timeout: 264 seconds)
14:53|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
14:56|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Read error: Connection reset by peer)
14:56|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
15:00andygraybeal has left IRC (andygraybeal!~andy.gray@obsidian.casanueva.com, Ping timeout: 272 seconds)
15:00|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Read error: No route to host)
15:01|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
15:14andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
15:20
<alkisg>
markit: which problem?
15:21
The gvfs issue you see is there if you're using another account (like root) for `ls`
15:21
<markit>
alkisg: Failed to load session ‘gnome-fallback’
15:21
yes, I was root
15:21
<alkisg>
OK, it's normal then
15:21
And is gnome-fallback installed?
15:21
<markit>
today I've re- ls that homedir and the .gvfs is ok now
15:21
yes, should be there, let me re-check
15:22
ii gnome-session-fallback 3.2.1-0ubuntu8 GNOME Session Manager - GNOME fallback session
15:22
<alkisg>
Fat clients? Is that in the chroot?
15:22
<markit>
yes, fat and chroot
15:23
I've to run now, I'll be back soon
15:23
<alkisg>
OK, bb
15:23buofkzqitr has joined IRC (buofkzqitr!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
15:25|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Ping timeout: 245 seconds)
15:28buofkzqitr has left IRC (buofkzqitr!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Ping timeout: 252 seconds)
15:44
<markit>
alkisg: back
15:44
unfortunately on the other side I've a tecnician that don't know GNU/Linux very well and often does random tests and configuration changes :(
15:45
<alkisg>
markit: it used to work and then it broke?
15:45
<markit>
no, new install, some hardware works that one not (that one is the one of most of the lab)
15:45
I've the suspect was running as thin client also
15:45
because there is threshold of 900MB
15:46
and those clients have 1GB ony
15:46
in any case, tomorrow I'll contact him again and hope to be able to do experiments a step at time
15:46
<alkisg>
NFS or SSHFS?
15:46
<markit>
sshfs
15:46
<alkisg>
Is it "some hardware" that doesn't work, or is it "the same user, on second login" that doesn't work?
15:46|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
15:47
<alkisg>
And is the message "cannot load gnome fallback session", or "cannot load fallback graphics mode"?
15:47
<markit>
the "cheap" hardware does not work whatever user (autologin configured) you use
15:47
the strange thing is that today first attempt worked
15:47
second failed
15:48
<alkisg>
Second fails because of the sshfs issues
15:48
<markit>
and so all the subsequent tryies, even with new account
15:48
<alkisg>
Ah btw, are you using the greek schools ppa on that installation?
15:49
<markit>
even with LDM_LIMIT_ONE_SESSION=True ?
15:49
yep, greek schools ppa as usual
15:50
would be wonderful have a bash script that tests all the ltsp functionality, I've done one just to check about listening ports
15:50
<alkisg>
There's ltsp-info
15:50
ldm_limit... isn't related to sshfs issues
15:51
ltsp - 5.4.3-1+r2462+p1163~precise1 published 1st of March
15:51
Do you think you have that in the chroot?
15:51
(from the greek ppa)
15:51
<markit>
alkisg: http://www.pastebin.ca/2345594
15:52
ii ltsp-client 5.4.3-1+r2462+p1163~precise1
15:52
I've not "ltsp" package installed
15:52
<alkisg>
Yes, ltsp client
15:52
In the pastebin, why does it say not installed for ltsp-client?
15:53
Also, are you using ltsp-pnp?
15:53
<markit>
no, stock ltsp
15:53
"not installed for ltsp-client?" what?
15:53
<alkisg>
root@serverme:/home/fat01# LANG=C ltsp-info ==> so you ran that on an ltsp thin client?
15:53
un ltsp-client <none>
15:53
<markit>
un ltsp-client <none>
15:53
<vagrantc>
sbalneav: so, with libpam-sshauth ... how are we going to support multiple servers?
15:54
<alkisg>
packages in chroot: /opt/ltsp/i386
15:54
<markit>
mmm the chroot installation is done automatically
15:54alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Quit: Хана X'ам !!!)
15:54
<markit>
dubt that the other package installed have pushed out ltsp-client
15:55
but could be...
15:55
<alkisg>
(05:52:20 μμ) markit: ii ltsp-client 5.4.3-1+r2462+p1163~precise1 ==> what command did you run to get that?
15:56
<markit>
in the Server (not chroot) I run: root@serverme:/# dpkg -l | grep ltsp
15:56
mmmmaybe I was in chroot
15:57
hold on
15:57
EVERYTHING WRONG, was in chroot
15:57
even with ltsp-info probably
15:57|Paradox| has left IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net, Read error: Connection reset by peer)
15:57
<markit>
no, root@serverme:/home/fat01# ltsp-info
15:58|Paradox| has joined IRC (|Paradox|!~iamparado@c-71-206-132-62.hsd1.va.comcast.net)
15:58
<markit>
says packages in chroot: /opt/ltsp/i386 un ltsp-client <none>
15:58
if I chroot
15:58
dpkg -l | grep ltsp
15:58
<alkisg>
Just run ltsp-info outside the chroot
15:58
<markit>
ii ltsp-client 5.4.3-1+r2462+p1163~precise1 complete LTSP client environment
15:58
<alkisg>
sudo ltsp-info
15:59
<markit>
http://pastebin.ca/2345599
15:59
that's outside chroot for sure
16:00
also because in chroot there is NO ltsp-info
16:00
so seems that ltsp-info is bogus
16:01
<alkisg>
Yeah...
16:01
<markit>
btw, would be great if ltsp-chroot would change the prompt with somethign useful
16:01
like "I'm in chroot, stupid" #
16:01
;P
16:02
<alkisg>
You could file a bug report in "chroot" if you want...
16:02
<vagrantc>
ltsp-info is producing invalid informmation?
16:02
<alkisg>
It's not ltsp specific
16:02
vagrantc: seems like it...
16:02
<markit>
alkisg: nothing the script could do once chrooted? I mean, chroot + change the prompt
16:02
<alkisg>
Sure it could
16:02
<vagrantc>
works for me just fine... hard to imagine how it could fails
16:03
<markit>
since we work in chroot just for some brief settings
16:03
<alkisg>
And you can also configure it manually if you want
16:03
<markit>
vagrantc: don't know if relevant, I have server at 64 bit, chroot at 32, and using greek ppa for ltsp
16:03
<alkisg>
But changing the prompt doesn't sound like a task for ltsp-chroot, but a generic setting for any chroot...
16:03
<vagrantc>
markit: should work fine...
16:04
<markit>
alkisg: I understand your point, but I think that the goal of chroot is have you belive you are in a regular root
16:04
<vagrantc>
the pastebin.ca urls didn't work for me, btw
16:04
<markit>
a sort of "jahil"
16:04
while in ltsp is not the case
16:04
<alkisg>
Why not?
16:04
Where's the difference from "generic chroots" vs "ltsp chroots"?
16:04
<markit>
alkisg: because I'm not a user put there ignoring it
16:04
<vagrantc>
alkisg: i believe there is support in debian and derivatives to display something in the prompt if an environment variable is set, explicitly for these sorts of chroot environments
16:05
<alkisg>
vagrantc: yes, I think we have a bug report for that in launchpad
16:05
<ogra_>
yeah, in bashrc or so
16:05
<alkisg>
Something starting with debian*
16:05
markit: I didn't understand your last sentence...
16:06
<markit>
alkisg: I mean, chroot is good to make you belive you are in a real root, not in chroot. Is a security way of running some things AFAIU, so is important to mimic the real root
16:06
in ltsp we have chroot only "by accident", (in fact ltsp-pnp avoids it)
16:07
and when I'm in chroot I do want to know
16:07
<alkisg>
markit: I don't think that's the case; chroots are installations inside some directory, whether for ltsp or for any other case
16:07
<markit>
I've had a lot of issues because I thought I was in the server while I was in chroot
16:07
alkisg: can't you agree that not having a informative prompts in ltsp is only damage and no gain?
16:07
<alkisg>
So while I agree with you, and I would like a different prompt in ltsp chroots, I'd also like different prompts in other chroots as well
16:08
markit, vagrantc, ogra_: http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg40889.html
16:08
<markit>
alkisg: isn't chroot usually used to "trick" users and services about not being in chroot but in a regular system?
16:08
<alkisg>
+eval LTSP_HANDLE_DAEMONS=false debian_chroot="remaster" chroot "$ROOT" $COMMAND
16:09
markit: I don't think that's the main use of chroots, no
16:09
E.g. suppose I create a chroot in order to compile it to ubuntu.iso later on
16:09
I'd want to know I'm in a chroot there too
16:09
<ogra_>
chroots can be used like that though
16:10
<markit>
http://en.wikipedia.org/wiki/Chroot
16:10
<ogra_>
my very first encounter of the chroot command was at an ISP where we jailed their ftp access liek that
16:10
<alkisg>
ogra_: so you used `chroot ftp`?
16:10
I don't think so... you ftp'ed to a chroot
16:10
<vagrantc>
chroots can be used for lots of different things.
16:10
<alkisg>
So in that case, the chroot command wouldn't run, and you wouldn't get a prompt
16:10
<markit>
seems you are right
16:10
<ogra_>
we used a special /etc/passwd setup and copied /lib/libc.so and /bin/bash in place ...
16:11
<markit>
in any case, I've more hopes that ltsp people will implement it soon than hope to convince the whole GNU/Linux community
16:11* vagrantc notes that plain ol chroot is a fairly ineffective security measure these days
16:11
<ogra_>
on login you were inside /home/$USER/public_html which turned into /
16:12
yeah, you wouldnt do it like that anymore
16:12
<alkisg>
ogra_: so you didn't use the chroot command yourself, so you wouldn't get a prompt
16:12* vagrantc plans to carry a patch for ltsp-chroot to set something in the debian_chroot var in the future.
16:12
<alkisg>
Why a patch, and not send that upstream?
16:12
<ogra_>
alkisg, the login command used the chroot command as login shell
16:13
<alkisg>
ogra_: right, but you didn't use it. As part of the automation there, they could have set any prompt they liked
16:13
<vagrantc>
alkisg: if i can figure out how to do it just for debian derivatives, sure.
16:13* ogra_ cant remember the exact setup anymore, thats nearly 20 years ago :)
16:13
<vagrantc>
alkisg: without it getting uglified in the code
16:13
<alkisg>
vagrantc: just a distro overridable function
16:13
We have pre_chroot, post_chroot...
16:14
<vagrantc>
alkisg: but with the eval, i think it's tricky to set
16:14
<alkisg>
We just need to override the chroot call into an "actual_chroot()" function, and you can then override that in debian
16:14
I don't see any eval's there
16:14
LTSP_HANDLE_DAEMONS=false chroot "$ROOT" "$@"
16:14
<vagrantc>
eval LTSP_HANDLE_DAEMONS=false debian_chroot="remaster" chroot "$ROOT" $COMMAND ??
16:14
<alkisg>
That would just be written as `do_chroot "$@"`
16:14
vagrantc: that was from the old code
16:14
<vagrantc>
ah
16:15
<alkisg>
I've removed the eval some time ago...
16:15
<vagrantc>
at any rate, i'd like to support that someday
16:15
somehow, someway
16:15* alkisg doesn't care at all about chroots anymore so he's happy with any prompt :)
16:17
<ogra_>
pfft ... think of your users :)
16:17
<markit>
mm if I chroot, # COLUMNS=200 dpkg --root=$chroot -l 'ltsp*' 'ldm*' | awk '/ltsp-client|ldm|ltspfs/{print $1,$2,$3}'
16:17
says ii ltsp-client 5.4.3-1+r2462+p1163~precise1
16:17
while if I run ltsp-info does not
16:18
(but should run that code)
16:18
so a) is unable to chroot, b) is running something different
16:18
<vagrantc>
it doesn't run it using chroot
16:18
it just tells dpkg to look at the files in the chroot
16:19
that way it doesn't require root access
16:19
<markit>
ah, I see (reading more carefully the code, yeah)
16:20
in fatct # COLUMNS=200 dpkg --root=/opt/ltsp/i386 -l 'ltsp*' 'ldm*' | awk '/ltsp-client|ldm|ltspfs/{print $1,$2,$3}'
16:20
does not have the same output
16:21
FOUND
16:21
vagrantc:
16:21
# dpkg --root=/opt/ltsp/i386 -l | grep ltsp
16:21
ii ltsp-client:i386 5.4.3-1+r2462+p1163~precise1 complete LTSP client environment
16:22
probably that :i386 confuses awk
16:22
that is looking for just "ltsp-client"
16:22
<vagrantc>
don't see how it would
16:23
that is looking for any line that includes the text "ltsp-client"
16:23
<markit>
mmm yep
16:23
<vagrantc>
it coulld say foobarbazltsp-clientsowhateveryouwant
16:23
and it would print it
16:24
<markit>
BUT
16:24* vagrantc wonders if apparmor or something is interfering
16:25
<vagrantc>
at any rate, have to head out
16:25
<ogra_>
shouldnt
16:25
<vagrantc>
very curious what the issue is
16:25
<markit>
vagrantc: http://pastebin.ca/2345625
16:26
is the ... -l 'ltsp*' 'ldm*' part the reason
16:26
<vagrantc>
markit: for some reason pstebin.ca isn't working for me.
16:26
<markit>
vagrantc: ok, in short
16:26
dpkg --root=/opt/ltsp/i386 -l | grep ltsp
16:26
ii ltsp-client:i386 5.4.3-1+r2462+p1163~precise1 complete LTSP client environment
16:26
WHILE
16:27
dpkg --root=/opt/ltsp/i386 -l 'ltsp*' 'ldm*' | grep ltsp
16:27
un ltsp-client <none> (no description available)
16:27
<vagrantc>
that's odd.
16:28
bug in dpkg?
16:29
<markit>
I've no idea, I'm a dumb newbie (and always be) ;P
16:30
<vagrantc>
markit: try: cd / ; dpkg --root=/opt/ltsp/i386 -l 'ltsp*' 'ldm*' | grep ltsp
16:31
<markit>
vagrantc: the same un ltsp-client <nessuna> (nessuna descrizione disponibile)
16:31
<vagrantc>
i can only guess it's a bug in dpkg's handling of --root + -l with wildcards
16:32
markit: at any rate, congradulate yourself, you figured out a weird issue! :)
16:32
<ogra_>
probably introduced with multiarch
16:32
<vagrantc>
works fine on wheezy.
16:33
markit: dpkg --root=/opt/ltsp/i386 -l ltsp-client
16:33
?
16:33
<markit>
un ltsp-client
16:33
<vagrantc>
ok, not specific with wildcards
16:33
<markit>
dpkg --root=/opt/ltsp/i386 -l ltsp-client:386
16:33
ii ltsp-client:i386
16:33
<vagrantc>
ogra_ ftw!
16:33
<ogra_>
:)
16:34
<vagrantc>
markit: and your initial hunch was in the right direction for that
16:34* vagrantc disappears
16:34vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
16:35
<markit>
ehm, will you file a bug?
16:35
<ogra_>
you should ... with your findings ... since you can reproduce it if someone asks
16:36
<markit>
ogra_: against ubuntu then?
16:36
<ogra_>
if you are on ubuntu, then yes
16:36
else in debian indeed
16:39
<markit>
ogra_: I've no idea if sqeeze has it and weezy (as vagrantc says) no
16:39
I put in the list of "things to do
16:39
"
16:40
alkisg: in the meantime, in ltsp-info code just removing the 'ltsp*' 'ldm*' solves the issue
16:40
just adding a little overhead
16:41
<alkisg>
markit: we're not using chroots at all here, so I can't even test
16:42
On a test wheezy chroot that I have, wildcards appear to work
16:42
Although it's same arch, i386
16:42
<markit>
alkisg: is ltsp-pnp the future of ltsp, or a "additional way of set things up"?
16:42
<alkisg>
An additional way
16:43
But each ltsp developer tests what he's interested in
16:43
E.g. I couldn't test the fedora bits, I've never even used fedora
16:44
<markit>
alkisg: the 'ltsp*' 'ldm*' is just to make dpkg produce a reduced set of packages that are filtered by awk
16:44
without that part, just awk has to do more work, but the result is the same
16:44
<alkisg>
Sure. And fixing that in dpkg is much saner than working around it in ltsp.
16:44
In any case, I can't even test, so I'm not the correct person to talk about this...
16:44
<markit>
alkisg: but you could wait ages before that, like the chroot prompt stuff
16:44
<alkisg>
Why?
16:45
File an SRU when it's ready, or use a PPA
16:45
It's not like you'll get an LTSP SRU for that either
16:45
<markit>
alkisg: my feeling that, for chroot prompt, you have to convince 100 thousand peoples, all with some corner test, and discussion will last forever
16:45
in ltsp we have no corner cases, would be just great
16:45
<alkisg>
For the prompt, ok, but not for bugs
16:46
It should be very easy to convince people to fix bugs :)
16:46
<markit>
lol, really
16:46
but "works as designed" is often used for bugs too
16:46
<ogra_>
and discussions usually dont last more than 7.5 years in ltsp land ... forever is an exxageration :P
16:46
<alkisg>
I don't think this is the case for the dpkg bug you mentioned
16:46
<markit>
I remember a bad openoffice localization for numeric keyboard and decimal separator
16:46
alkisg: ok, I trust your opinion more than mine :)
16:47
I'll try
16:47
<alkisg>
First thing is to search for an existing bug report
16:47
If it's fixed, and you want to, you can try backporting the fix to 12.04, with an "SRU"
16:48
<ogra_>
12.04's multiarch definitely has its weaknesses ...
16:49
i think there were only some basic bits backported from the newer dpkg, not everything since that would have been to intrusive
17:16bobby_C has joined IRC (bobby_C!~bobby@188.20.161.210)
17:18komunista has left IRC (komunista!~slavko@87.244.209.121, Ping timeout: 255 seconds)
17:28markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
18:00Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 240 seconds)
18:04Enslaver has left IRC (Enslaver!~Enslaver@c-98-196-42-169.hsd1.tx.comcast.net, Ping timeout: 252 seconds)
18:08bobby_C has left IRC (bobby_C!~bobby@188.20.161.210, Ping timeout: 246 seconds)
18:15Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
18:22alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
18:45awilliams has left IRC (awilliams!~awilliams@unaffiliated/mistik1, Ping timeout: 256 seconds)
18:46awilliams has joined IRC (awilliams!~awilliams@unaffiliated/mistik1)
19:09shogunx has left IRC (shogunx!~shogunx@2001:4978:106:1:1d45:81cb:34f4:db4d, Ping timeout: 245 seconds)
19:11awilliams has left IRC (awilliams!~awilliams@unaffiliated/mistik1, Ping timeout: 256 seconds)
19:22shogunx has joined IRC (shogunx!~shogunx@2001:4978:106:1:acb9:2eb2:60f2:2b2d)
19:31adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.204.148.206.dynamic.adsl.gvt.net.br)
19:31adrianorg_ has left IRC (adrianorg_!~adrianorg@177.156.230.191, Read error: Connection reset by peer)
19:35vagrantc has joined IRC (vagrantc!~vagrant@97-115-26-201.ptld.qwest.net)
19:35vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
19:38bobby_C has joined IRC (bobby_C!~bobby@188.20.161.210)
20:10vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
20:12
<warren>
way too busy. /msg me if needed.
20:12warren has left IRC (warren!~warren@fedora/wombat/warren)
20:33andygraybeal_ has joined IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net)
21:07vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
21:13andygraybeal_ has left IRC (andygraybeal_!~andy@h139.67.213.151.dynamic.ip.windstream.net, Ping timeout: 240 seconds)
21:23Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 256 seconds)
21:26bobby_C has left IRC (bobby_C!~bobby@188.20.161.210, Ping timeout: 272 seconds)
21:38khildin has left IRC (khildin!~khildin@ip-83-134-215-251.dsl.scarlet.be, Remote host closed the connection)
21:39Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
21:43vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 240 seconds)
21:44vagrantc has joined IRC (vagrantc!~vagrant@97-115-26-201.ptld.qwest.net)
21:44vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
21:48vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 256 seconds)
22:03alexqwesa__ has joined IRC (alexqwesa__!~alex@109.172.12.47)
22:15vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
22:29vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 260 seconds)
23:18vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
23:31vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
23:40Enslaver has joined IRC (Enslaver!~Enslaver@c-98-196-42-169.hsd1.tx.comcast.net)
23:59alexqwesa__ has left IRC (alexqwesa__!~alex@109.172.12.47, Read error: Operation timed out)