IRC log for #maemo-ssu on 20130410

01:03.28*** join/#maemo-ssu arcean_ (~arcean@apn-77-112-169-170.dynamic.gprs.plus.pl)
02:01.07*** join/#maemo-ssu MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG)
02:03.20*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:03.49*** join/#maemo-ssu DocScrutinizer06 (~HaleBopp@openmoko/engineers/joerg)
04:25.00*** join/#maemo-ssu futpib (~futpib@89.106.197.72)
04:25.13*** join/#maemo-ssu jon_y (~enforcer@2002:3c35:9d87::3c35:9d87)
04:36.45*** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:35a2:ea45:8d89:d7cd)
04:50.48*** join/#maemo-ssu Skry (~skry@adsl-77-109-215-222.kymp.net)
06:02.22*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
06:06.02*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
06:56.55*** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro)
07:52.20*** join/#maemo-ssu FReaper (~assassin@203.106.65.1)
07:57.05*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
07:57.11*** join/#maemo-ssu prometoys (~prometoys@2a00:e68:14:16:219:dbff:feb6:eccc)
08:06.24*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz)
08:09.32*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
08:12.33*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
08:16.50*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
08:44.47*** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-176.residential.rdsnet.ro)
09:08.12*** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net)
09:22.59*** join/#maemo-ssu arcean (~arcean@apn-77-112-172-151.dynamic.gprs.plus.pl)
09:41.29*** join/#maemo-ssu futpib (~futpib@89.106.197.54)
09:54.23*** join/#maemo-ssu kolp (~quassel@212.255.237.74)
10:04.06*** join/#maemo-ssu M13 (~Miranda@83.149.35.61)
10:27.08*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-nibsrjxtsvqwvxky)
11:46.39*** join/#maemo-ssu infobot (~infobot@rikers.org)
11:46.39*** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2013-01-07): 21.2011.38-1Tmaemo7.2; Stable(2013-01-10): 21.2011.38-1Smaemo6 | Next meeting 06.03
11:46.39*** mode/#maemo-ssu [+v infobot] by ChanServ
12:01.37*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
12:54.43*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
13:08.48*** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net)
14:47.44*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-nkuilkvixrkvzceh)
15:51.05*** join/#maemo-ssu freemangordon_ (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
15:51.52*** part/#maemo-ssu freemangordon_ (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
16:03.45*** join/#maemo-ssu NIN101 (~NIN@p5DD28B7E.dip0.t-ipconnect.de)
16:26.03*** join/#maemo-ssu Raimu-Z (~raimu@kameli.net)
16:29.40*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
16:37.28*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
16:38.50*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
16:42.06*** join/#maemo-ssu kolp (~quassel@212.255.237.74)
17:03.05*** join/#maemo-ssu Raimu-Z (~raimu@kameli.net)
17:08.50*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz)
17:50.29*** join/#maemo-ssu arcean (~arcean@apn-77-113-73-85.dynamic.gprs.plus.pl)
17:51.24*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
18:01.25*** join/#maemo-ssu Martix_ (martix@nat/redhat/x-dexoqdgtbsevicgq)
18:43.32*** join/#maemo-ssu infobot (~infobot@rikers.org)
18:43.32*** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2013-01-07): 21.2011.38-1Tmaemo7.2; Stable(2013-01-10): 21.2011.38-1Smaemo6 | Next meeting 06.03
18:43.36*** mode/#maemo-ssu [+v infobot] by ChanServ
19:06.56*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
20:26.43*** join/#maemo-ssu Martix_ (martix@nat/redhat/x-syrcqudsdrgzpcxs)
20:27.36*** join/#maemo-ssu Martix (martix@nat/redhat/x-rwgkqletckvuosme)
20:27.41*** join/#maemo-ssu Raimu-Z (~raimu@kameli.net)
20:28.39*** join/#maemo-ssu Martix (martix@nat/redhat/x-adhpfcvhscvalnet)
20:29.16*** join/#maemo-ssu Martix (martix@nat/redhat/x-lgwwpkkohttzcytp)
20:30.10*** join/#maemo-ssu Martix (martix@nat/redhat/x-onhfzttgpmhtncie)
20:46.27*** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:35a2:ea45:8d89:d7cd)
21:19.53merlin1991kerio: I tried to but apt-mirror wants to dl 30GB each run
21:20.03merlin1991and I didn't find the time to debug that
21:20.12kerio:(
21:20.59freemangordonmerlin1991: http://talk.maemo.org/showpost.php?p=1335313&postcount=1484 , could you put those packages in cssu-thumb?
21:21.32freemangordonmerlin1991: from CSSU-T 7.2 ofc
21:26.14merlin1991freemangordon: done
21:27.01freemangordonmerlin1991: thanks
21:27.48merlin1991about the cssu repo, I did what I could, but the rights system is seriously foobar and I need a higher authority than me to do something
21:28.15freemangordonmerlin1991: hmm, who, doc?
21:28.50Pali[20:36:20] <DocScrutinizer05> merlin1991 has sufficient right to do what needs to be done on repos, if he's missing rights he will pester me and we'll fix stuff in 5min
21:29.03freemangordon:nod:
21:29.07merlin1991Pali: the problem isn't a simple fix anymore
21:29.22merlin1991it's a policy thing about users and groups on serveral machines
21:29.25freemangordonmerlin1991: it was about the rights
21:29.28merlin1991the setup is friggin silly
21:30.03DocScrutinizer05indeed
21:30.26kerio5 years of cruft?
21:30.31keriobureaucratic cruft
21:30.33DocScrutinizer05we got no write permissions on a NFS mount despite the group is +w
21:30.57DocScrutinizer05the group/user ids between both machines aren't in sync
21:31.04keriooh god D:
21:31.07Paliah NFS :-)
21:32.02PaliNFS (ver 1?) was maybe only one FS where mkdir was not atomic :D
21:32.21DocScrutinizer05my take is "it never will work flawlessly until we get those etc/passwd and etc/group files "synced", so num IDs for identical users/groups are identical on both machines
21:32.50merlin1991yeah but it makes no sense to sync all users and groups from drop to repo just for the cssu upload
21:32.59merlin1991we should simply ditch the old idea and set up something new
21:33.00DocScrutinizer05but it as well might be something completely different that what I suspect
21:33.52DocScrutinizer05I suggested to ditch the old cssu-testing group and add it anew on both machines, with identical numID
21:34.04DocScrutinizer05same for all related/involved users
21:34.21DocScrutinizer05can olnly be 2 or 3
21:35.11*** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz)
21:35.12DocScrutinizer05you need to chown all files owned by any of those users/groups as well, wehn you do that
21:35.36DocScrutinizer05wonders if there really isn't a script already to do that friggin task
21:36.02DocScrutinizer05not the first time somebody needs to change a user's numID on unix
21:36.16merlin1991DocScrutinizer05: the grage -> drop script would ruin that group on each run
21:36.32DocScrutinizer05err why?
21:37.19merlin1991hm actually not since it atm does not check group ids
21:39.42DocScrutinizer05look, aiui you log in on drop.m.o via ssh key, and you are member of group cssu-testing (or whatever) which is supposed to have write access to /mnt/incoming/foo/bar/dunnowhat
21:43.09DocScrutinizer05now that group has write access to the NFS seeding dir (I.E. on repo(?) side where the dir gets exported), and you have write access to it on the mounting side drop, if you are root, or you are others and the dir is others+w. You do NOT have write access on drop when you're member of cssu-testing group, despite the group has +w and numID is identical with the numID of your group on drop
21:43.33DocScrutinizer05and that's the bug
21:44.02DocScrutinizer05I think it can only be related to owner/group numID not in sync between the both machines
21:45.10DocScrutinizer05<PROTECTED>
21:45.26DocScrutinizer05<PROTECTED>
21:47.42DocScrutinizer051003 cssu-stable 4096 Mar 30  2012 /mnt/incoming/community/fremantle/
21:48.48DocScrutinizer05root@vcs:/mnt/incoming/community-testing/fremantle# ll
21:49.01DocScrutinizer051003 cssu-testing 4096 May 30  2012 ./
21:49.14DocScrutinizer051005 falk         4096 Oct 26  2010 ../
21:50.19DocScrutinizer051003 and 1005 seem orphaned users on *both* machnes
21:50.49merlin19911003 is "respository" on repo
21:51.03DocScrutinizer05ooh, ok
21:51.16DocScrutinizer05I created cssu-testing on vcs anyway
21:52.28DocScrutinizer05drop==vcs, for lurkers info
21:55.46merlin1991currently fixes his win7 newest system update resulted in bluescreen on boot
21:57.54DocScrutinizer05joerg@vcs:~$ id
21:57.55DocScrutinizer05uid=30401(joerg) gid=30580(joerg) groups=30580(joerg),27(sudo),30550(cssu-testing)
21:57.57DocScrutinizer05joerg@vcs:~$ date >/mnt/incoming/community-testing/fremantle/xxx
21:57.58DocScrutinizer05-bash: /mnt/incoming/community-testing/fremantle/xxx: Permission denied
21:58.00DocScrutinizer05joerg@vcs:~$ ll -dn /mnt/incoming/community-testing/fremantle/
21:58.01DocScrutinizer05drwxrwxr-x 2 1005 1005 4096 Apr  9 05:18 /mnt/incoming/community-testing/fremantle//
22:07.52DocScrutinizer05do NFS mounts need permissions on parent dirs? like the mount is vcs:/mnt/incoming/community-testing owned by 999:999 770, but the dir/file I wanna write to is vcs:/mnt/incoming/community-testing/fremantle/xxxx and that dir is owned by me but still I mustn't write since I'm not owner of parent dir?
22:13.48DocScrutinizer05sg when not fixed so at least solved the miracle
22:14.08ShadowJKI do not believe parent dir needs write permissions
22:14.25DocScrutinizer05yeah, evidently not
22:15.00DocScrutinizer05but afaik there are differing concepts about applying auxiliary groups of a user automatically
22:15.17ShadowJKconsidering users dont have write to / or /home either, but do have to /home/user/
22:15.27DocScrutinizer05while this might work on a local machine, since the local machine has access to /etc/groups
22:15.38DocScrutinizer05...it is prone to fail on a NFS mount
22:16.20*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
22:16.38DocScrutinizer05joerg@vcs:~$ id
22:16.39DocScrutinizer05uid=30401(joerg) gid=30580(joerg) groups=30580(joerg),27(sudo),30550(cssu-testing)
22:16.41DocScrutinizer05joerg@vcs:~$ date >/mnt/incoming/community-testing/fremantle/xxx
22:16.43DocScrutinizer05bash: /mnt/incoming/community-testing/fremantle/xxx: Permission denied
22:16.44DocScrutinizer05joerg@vcs:~$ sg cssu-testing
22:16.45DocScrutinizer05joerg@vcs:~$ id
22:16.47DocScrutinizer05uid=30401(joerg) gid=30550(cssu-testing) groups=30580(joerg),27(sudo),30550(cssu-testing)
22:16.48DocScrutinizer05joerg@vcs:~$ date >/mnt/incoming/community-testing/fremantle/xxxx
22:17.39DocScrutinizer05joerg@vcs:~$ ls -l /mnt/incoming/community-testing/fremantle/xxx
22:17.40DocScrutinizer05-rw-rw-r-- 1 dkothari hayrinenk 29 Apr  9 05:18 /mnt/incoming/community-testing/fremantle/xxx
22:18.09DocScrutinizer05meh
22:18.11DocScrutinizer05-rw-r--r-- 1 joerg    cssu-testing 29 Apr 10 22:11 xxxx
22:19.05DocScrutinizer05the NFS server can't know about user's auxiliary groups on client
22:32.14*** join/#maemo-ssu MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG)
23:03.00ShadowJKnfs usually doesn't care about user or group names, it's all numerical.. So, user 'jk' with uid 500 on machine 1, would not have access over nfs to machine 2 to a user 'jk' uid 501.. but would have access to user 'kj' uid 500
23:03.56ShadowJKthough there's modern stuff these days that might "fix" that, but I'm not up to date on it :/
23:39.23DocScrutinizer05ShadowJK: the problem is more like: a user jk with primary group 999, aux-groups:12,13,20,21  will not have access to a dir with owner:group 4711:20, despite group:20 is in his aux-groups
23:40.54DocScrutinizer05he needs to do `sg 20` which is allowed any time to users who have that group in their auxgroups, and then access to that 4711:20 dir will work
23:43.00DocScrutinizer05see above! while I had no access as >>uid=30401(joerg) gid=30580(joerg)<<, I was allowed as >> uid=30401(joerg) gid=30550(cssu-testing)<< to write to /mnt/incoming/community-testing/fremantle root:cssu-testing
23:44.27DocScrutinizer05it's kinda like s(et)u(ser) but for group: s(et)g(roup) cssu-testing
23:45.54DocScrutinizer05just it's not needed (anymore?) on recent unix systems since on local dirs the fs checks your auxiliary groups if you *could* have done sg and thus would have been allowed to access that dir. This however doesn't work for NFS mounts, for relatively obvious reasons
23:48.21DocScrutinizer05maybe NFS even has a mount parameter that allows feedback from server to client about "group doesn't match" and then client's nfs fs driver would check locally and do an implicit sg and repeat the request
23:48.42DocScrutinizer05if there's such a nfs mount parameter, then I don't know about it

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.