/srv/irclogs.ubuntu.com/2008/06/17/#ubuntu-devel.txt

taconehello, how may I ask to, for reporting a problem on a canonical server ?00:51
taconeerr.00:51
taconewho may ask to ?00:51
=== Zic_ is now known as Zic
=== eldalion is now known as eldawlion
tedgWhy do the lpia PPAs always build faster?02:38
TheMusotedg: Probably because they are not loaded down with arch all packages.02:40
tedgTheMuso: Ah, okay.  Thanks.02:41
=== pgraner_ is now known as pgraner
TheMusoo/c04:33
pittiGood morning06:17
* StevenK waves to pitti 06:17
ajmitchhi pitti06:18
pittikirkland: if you keep 'user=kirkland' in mtab, then umount works as user? I. e. it doesn't need an fstab entry? nice! the "mount as root" part was ok, AFAIR, right?06:21
pittikirkland: ecrypts_private_owner=kirkland? that's not something umount currently understands; so you do want to patch mount after all?06:21
pittikirkland: sync> will do06:22
pittislangasek: "I can live with that"> If we disable LANMAN by default in intrepid, to put an end to it, and reenable it in hardy-updates, if you think that a gvfs patch to display a proper error message is too complicated for an SRU06:23
nxvlslangasek: around?06:24
slangasekpitti: I don't think it's too complicated for an SRU; I do think it would take too long to include in 8.04.1.06:24
slangaseknxvl: vaguely06:24
nxvlslangasek: i was wondering about the delay on alpha106:25
nxvlslangasek: is there some page or something with a list of what's needed?06:25
pittislangasek: that was because of the insufficient error reporting API in libsmbclient, so it takes some hacks to get the actual error cause?06:25
slangaseknxvl: the short list is "debian-installer needs to be merged"06:27
slangasekpitti: yes, the libsmbclient is POSIX-like, so detecting the right error would require some kludging to get out-of-band info06:27
pittino smberrno or so?06:28
pittikirkland: hm, I just did a "sync all" run, but ecryptfs wasn't amongst it; apparently it's not on ftp.uk.d.o yet?06:29
nxvlslangasek: look like a looong and hard merge06:33
slangaseknxvl: yes, it's in progress; merges are, of course, not very parallelizable06:34
nxvlyup06:34
nxvlbut we can still have a bzr branch to work on it06:35
slangasekwell, that would be a strange way to handle merge conflicts, IMHO06:35
nxvlmmm06:36
nxvlyep, it could be06:36
nxvlwell06:36
nxvlnow i need to sleep06:36
nxvlsee you06:36
nxvlslangasek: if you need some help on anything please ping me06:36
nxvl:D06:36
lifelessslangasek: actually its a common feature request for large-scale vcs's06:36
lifelessslangasek: to be able to save and restore conflict state and collaborate on such things06:37
slangaseklifeless: hmm, feels dirty to me, but ok. :)06:37
slangaseknxvl: sure :)06:37
lifelessslangasek: consider a merge with 2K conflicts06:38
lifelessslangasek: parallelising that would save a lot of time off the process, if you could06:38
slangaseklifeless: I would prefer to never have to consider one of those if I can help it ;)06:38
lifelessslangasek: or even, imagine if debian and ubuntu were single vcs trees06:38
lifelessmom is basically doing this by splitting the conflict set by package, but there are conflicts that are cross-package - they are artificially partitioned by our tool chain but need to be treated as a unit06:39
=== persia_ is now known as persia
dholbachgood morning06:42
theJamAbidesHey guys just looking for the bugs channel and how to get involved with helping out a little... see it in the banner, see you around!06:43
philwyettYikes... People are using the [[FullSearch()]] macro on wiki.ubuntu.com in their personal pages to list all pages with their wiki name in instead of using links. That might be stressing the server doing many searches. :-/07:17
lifelessphilwyett: if so, then its a bug in the wiki07:20
ion_Indeed07:20
philwyettGoing by the limited docs, it's usage is not restricted and is doing the correct thing and listing pages containing the calling pages title string which is the users wiki name. Where would I file something like this do you think?07:23
=== tkamppeter_ is now known as tkamppeter
ion_If it slows down the wiki, probably whereever one is supposed to file bugs agains the wiki engine in question.07:25
philwyettI will dig further and see if can be corrected at the server now or it should be file at MoinMoin.07:27
=== LucidFox is now known as LucidFox_away
* philwyett laughs. Well [[FullSearch()]] is not a bug it's a feature. Listed No.1 in the performance cpu and I/O usage hit parade on the MoinMoin site. Educating users is suggested. :-)07:56
=== LucidFox_away is now known as StargateFox
ion_philwyett: Fixing MoinMoin is suggested. :-)08:08
philwyettion_: I will put in an RFE with MoinMoin, but also mail the Ubuntu webmaster and discuss. There are 432 instances of it's use on the wiki, so only a medium large job to correct the bad usages. :-)08:13
ion_s/correct the bad usages/workaround the wiki bug/08:17
philwyett:-)08:18
=== freeflyi1g is now known as freeflying
ion_macslow: Hi09:01
ion_macslow: Btw, the keyboard layout indicator in gnome-screensaver’s unlock dialog doesn’t share the background gradient.09:01
MacSlowgreetings ion_09:01
MacSlowion_, that's "fixed"...09:01
ion_Alright :-)09:02
MacSlowion_, in the way that there is no more gradient as it was decided against the gradient09:02
ion_Oh, ok. I kind of agree with that.09:02
MacSlowion_, but otherwise it would have been fixed too by now :)09:02
MacSlowion_, sadly there are still a couple of issues with some widgets and RGBA-colormaps09:03
MacSlowion_, but if we don't stress it, issues don't turn up and we don't know that we need to fix them09:03
ion_Yeah09:04
=== StargateFox is now known as LucidFox
asacis there a "common" way to specify dns server for static interface definitions in /etc/network/interfaces ?09:19
RicardoPerezasac: Hi! Any news about language-pack-es-base bug #240028?09:24
ubottuLaunchpad bug 240028 in language-pack-es-base "Problem in language-pack-es-base order installation makes Firefox translations lost" [Undecided,Confirmed] https://launchpad.net/bugs/24002809:24
Doriswhen running dpkg-buildpackage on a project i get "dpkg-shlibdeps: failure: no dependency information found for" - anyone know where this is fixed ? i have a depends line in my debian/rules file.09:30
=== RAOF_ is now known as RAOF
pittiasac, RicardoPerez: ah, we figured it out (bug updated); I'll fix it09:32
persiaDoris: Better to ask packaging questions on #ubuntu-motu.  Also, you generally want the dependencies in debian/control, rather than debian/rules.09:33
RicardoPerezpitti: oh, great!09:33
Dorissorry i did mean the control file09:48
Dorisill try motu though, thanks :)09:48
pitticjwatson: *phew*, dhcp3 merge finally done and uploaded (adopting our patches and sending them all upstreamwards took a while)09:49
RicardoPerezpitti: I can do all the testing you want, if you need it...09:54
pittiRicardoPerez: I at it already09:55
pittiRicardoPerez: I'd upload them to hardy-proposed, then you test, and if it's confirmed to work, I'll copy them to -updates09:55
pittiRicardoPerez: works for you?09:55
RicardoPerezpitti: great, of course!09:56
RicardoPerezpitti: you only need to notify me when the updates are in hardy-proposed, in order to test them09:56
pittiRicardoPerez: will do; thanks!09:56
RicardoPerezpitti: thanks to you :)09:57
=== asac_ is now known as asac
DktrKranzmvo: bug 222000 still has issues. If you want, I can look at it myself.10:05
ubottuLaunchpad bug 222000 in axyl-lucene "Update from Gibbon to Heron failed" [High,Confirmed] https://launchpad.net/bugs/22200010:05
cjwatsonpitti: woo, thanks; if that turns out to be enough to build d-i (unfortunately it's hard to tell in advance), I'll upload it10:06
pitticjwatson: still needs to pass NEW (new -ldap package), I'll watch it10:07
mdkewhat package should I use for filing a bug on the absence of sound if I don't have the first idea about what the cause is?10:10
mvoDktrKranz: that would be nice, I looked at this and fixed some bits, but there are other issue left I think10:11
DktrKranzmvo: thanks, I'll look at it more deeply.10:12
mvothanks10:12
seb128mdke: what sounds?10:14
mdkeseb128: all10:15
mdkesince asking the question I've found some info on the debug page on the wiki10:16
mdkeI'll follow those instructions, sorry for the noise10:16
seb128mdke:  I guess trying aplay first is a good idea10:17
RicardoPerezpitti: there's a delay in the hardy-proposed packages to be updated, isn't it?10:17
pittiRicardoPerez: yes, they need to build now, and then publish, I'll shepherd that10:17
pittiRicardoPerez: they should hit archive.u.c. at 1100 UTC10:18
mdkeseb128: ok, I'll try that too, thanks10:18
RicardoPerezpitti: ok, great, i'll wait then :)10:18
cjwatsonpitti: dhcp3-server-ldap is in NEW now for all but hppa10:45
Riddellpitti: indi is compiled now for that MIR, I realise the reason it wasn't uploading before is it used to be part of kdeedu (and so the version number was too low), so maybe it doesn't need a MIR?10:47
pittioh, doko is on the conference10:48
pittiRiddell: I'll have a look soon10:48
pittiRiddell: right, I just poked indi to build so far, so that it can actually be reviewed10:48
=== devfil_ is now known as devfil
=== LucidFox is now known as JapaneseFox
=== Traxer|off is now known as Traxer
mnabilguys, when  i tried to chroot on ubuntu from sabayon , i successfuly chrooted but i wanna run a gui application from ubuntu,   i got "Error: cannot open display: :0.0" ,  i export the DISPLAY variable, and used xhost , but i got the same error11:25
mnabilhttp://pastebin.ca/104899711:25
mnabildetails11:25
mnabilany idea11:26
cjwatsonI use things like http://people.ubuntu.com/~cjwatson/tmp/chroot-enter (see also chroot-setup and chroot-teardown) to deal with that sort of thing11:31
cjwatsondon't use xhost11:31
cjwatsonthe reason it can't resolve your DISPLAY is that you haven't bind-mounted /tmp/.X11-unix so it can't find the socket11:31
Mithrandirxhost is fine if you use xhost +SI:localuser:foo, though.11:32
Mithrandirbut you still need that bind-mount, yes.11:32
mnabilthanks , i'll try that11:35
Riddellpitti: dhcp3-server-ldap in main or universe?11:40
pittiRiddell: main should be fine, I think; the server guys should be happy about it11:40
Riddellpitti: shouldn't it conflict with dhcp3-server since they both contain /usr/sbin/dhcpd3 ?11:42
pittiRiddell: no, it diverts dhcpd11:42
pittiRiddell: thus -ldap even depends: on dhcp3-server, for reusing the init script, config files, and other infrastructure11:42
Riddellright11:42
RicardoPerezpitti: I've noticed that only language-pack-es & language-pack-es-base has been updated. Is it right?12:04
pittiRicardoPerez: no, also -pt and -zh12:31
pittiRicardoPerez: or what do you mean?12:31
pittiRiddell: hm, libsbigudrv-dev doesn't ship any header files?12:41
pittiRiddell: also, indi seems to deal with quite special hardware; do we have any of this for supporting this?12:42
Riddellpitti: right, the header files are duplicated in kdeedu12:43
Riddellpitti: no, can't say I have any telescopes12:43
pittiRiddell: so, not having it in main would entirely disable that part of kdeedu instead of just having it in universe (which would be ideal), right?12:45
* ogra_cmpc fears thats kstars12:46
Riddellpitti: yes12:46
Riddellogra_cmpc: yes12:46
pittiRiddell: ok, then I guess you want to have it in main12:47
ogra_cmpcpitti, if Riddell doesnt, i do12:47
pittiok12:47
pittiso, promoted12:48
ogra_cmpcunkless you have any equivalent to kstars i could take :)12:48
pittiRiddell: the -dev package still looks broken, though12:48
Riddellpitti: how so?12:48
pittiRicardoPerez: the langpacks are on archive.u.c. now, ready for testing12:48
pittiRiddell: no header files12:48
pittiRiddell: qca2 doesn't contain any crypto functions on its own, right?12:55
Riddellpitti: I'm afraid I don't know12:56
pittiok, I'll have a look12:56
ccmhey guys, just a short question: i looked at #156204, checked it and wrote a six line patch for pidgin-otr to enable creation of files with 0600 instead of 0644.12:59
zulmorning13:00
ccmno my question is if i should mail this patch to the debian maintainer, attach it to the bug report13:00
ccmor... whatever13:00
=== JapaneseFox is now known as LucidFox
=== pedro__ is now known as pedro_
james_wccm: hi, so the bug is in the pidgin-otr package, and not pidgin?13:07
RicardoPerezpitti: I'm working on it :)13:07
ccmjames_w: yes. but i got already two answers instructing me how to proceed13:07
RicardoPerezpitti: I'll do a fresh install, then an update, to be really sure the fix works13:12
Riddellinfinity: do you know why openhackware hasn't built?  I'm not sure what to do with bug 21743213:14
ubottuLaunchpad bug 217432 in openhackware "Please build openhackware 0.4.1-3" [Undecided,Fix committed] https://launchpad.net/bugs/21743213:14
geserRiddell: see I it correctly that openhackware 0.4.1-3 has no build records? neither for hardy nor intrepid13:30
ScottKgeser: It has to be manually built.13:31
elmoIIRC, openhackware is/has an arch all package that can't be built on i386 (sic) - soyuz doesn't support that13:32
geserright, it's in Pas: %openhackware: powerpc      # per Guillem Jover13:32
Riddellmvo: motu-sru don't like your proposal for bug 23109813:47
ubottuLaunchpad bug 231098 in ubuntu-restricted-extras "Please add sun-java6-jre and sun-java6-plugin to *ubuntu-restricted-extras" [Wishlist,Fix committed] https://launchpad.net/bugs/23109813:47
mvoRiddell: thanks, I'm answering now13:50
norsettoRiddell: don't think he is in motu-sru13:52
Riddellnorsetto: hmm?13:52
ScottKnorsetto: I asked Riddell to respond to his comment.13:52
* ScottK is in motu-sru13:53
norsettoScottK: ah ok13:53
* mvo answered now13:53
persiaRiddell: I'm not MOTU SRU.  I'm just an opinionated MOTU.13:54
Coren`anyone know where is "doko" ?13:56
persiaCoren`: This is the right place to ask, but providing context will often generate a more full response.13:57
jordioi13:57
jordiI notice ia32-libs in ubuntu includes alsa plugins.13:58
ogra_cmpclikely for flash13:59
jordiwe'd love to provide this in lib32asound-plugins, but we really don't grok biarch, I wonder if someone from the ubuntu core team would be able to tackle that13:59
Coren`persia: ok, I will give more context13:59
Coren`persia: he has forgotten to add a file into ooo-build svn14:00
Coren`nothing really serious, but I am pretty confident that he is the only one which has the file available14:00
persiaCoren`: Ah.  Put that next to his name, and there's a chance that he'll see it in backscroll, and add the file.14:01
Coren`persia: good idea14:01
Coren`mmh .. he can see irc logs even if he is not connected ...14:01
jordiwho's the biarch dude? doko?14:02
Coren`well, whatever, doko, please addd writer-default-font.diff to ooo-build svn whenever you can, thanks14:02
jordidoko?14:04
pittiCoren`: you want to talk to calc about OO.o patching14:07
jordipitti!14:07
pittihey jordidude! how are you?14:07
jordipitti: besides doko, any others who I could mail regarding biarch matters'14:07
jordipitti: all is well. dude, I saw pics of you, lots, from UDSS14:08
jordi-S14:08
jordinice beard :)14:08
Coren`pitti: thanks, but calc cannot help me on this one14:08
pittijordi: *scratching head* look how lib32readline5 or lib32z1 are built?14:08
pittijordi: thanks14:08
Coren`(as far as i know)14:08
jordipitti: see above; we need help to create a biarch alsa plugins package14:09
jordiwe already build lib32asound14:09
jordipeople want lib32asound-plugins14:09
jordiUbuntu actually sticks the plugins in ia32-libs, but that's ugly, of course14:09
pittijordi: yes, absolutely14:14
cjwatsonCoren`: people rarely read IRC logs from when they aren't connected; please send e-mail14:14
pittijordi: ia32-libs should ideally disappear; it's a PITA and a hack14:15
pittijordi: in an ideal world you could just apt-get install the _i386.deb on amd64, and we'd avoid all the multibuild stuff and ia32-libs *dream*14:15
Coren`cjwatson: he has an email @ubuntu.com ?14:16
cjwatsonCoren`: yes14:16
Coren`ok, thanks cjwatson14:17
ScottKmvo and Riddell: I acked the SRU for bug 231098 conditional on adding amd64.14:18
ubottuLaunchpad bug 231098 in ubuntu-restricted-extras "Please add sun-java6-jre and sun-java6-plugin to *ubuntu-restricted-extras" [Wishlist,Fix committed] https://launchpad.net/bugs/23109814:18
* norsetto wonders why java packages are arch dependent14:19
Coren`I have send it, thanks again cjwatson, pitti and bye everyone14:23
pittibdmurray: any chance that you can generate the DB queries on https://devpad.canonical.com/~brian/ with "psql -At"? this will suppress the table header and footer, and the leading whitespace14:24
cjwatsonnorsetto: sun-java6-plugin doesn't work properly on amd64, I believe; 64-bit support was pushed out to JDK 714:28
* ogra_cmpc wonders what's the reason for gpg stealing his terminal if a passphrase was mistyped three times or a passphrase input was canceled14:29
ogra_cmpci mean, if i have to execute reset anyway, gpg could do that for me as well on exit14:30
norsettocjwatson: I was just curios in a general way as why a java package was arch dependant (don't know what that particular one does)14:31
cjwatsonogra_cmpc: usually just a bug in terms of forgetting to turn the echo flag back on in some code paths14:31
ogra_cmpcah14:31
cjwatsonterminal settings are per-terminal rather than process-specific, so the process has to take care to restore them14:32
ogra_cmpcright, wso i should file that against gpg i guess14:32
cjwatsonand if it forgets (often due to being interrupted by a signal that it doesn't handle properly, but not always) then you can end up with echo left off14:32
cjwatsonyes14:33
ogra_cmpcright, thats what i see (actually since ages, but it didnt bother me enough yet)14:33
kirklandpitti: hiya14:38
kirklandpitti: http://packages.qa.debian.org/e/ecryptfs-utils.html shows 48-1 is in unstable14:39
pittihi kirkland, how's it going?14:39
kirklandpitti: good, i made some good progress yesterday with help from slangasek and kees14:39
kirklandpitti: i created a C program for umount.ecryptfs, setuid14:39
pittikirkland: hm, looks like it's on ftp.uk.d.o now, too14:39
* pitti runs a sync14:39
cjwatsonkirkland: FWIW you don't normally need to ask for syncs of unmodified-in-Ubuntu packages until DebianImportFreeze (26 June)14:40
kirklandcjwatson: by that you mean they happen automatically?14:41
cjwatsonsemi-automatically14:41
cjwatsonas in, an archive admin runs some stuff roughly daily which slurps everything in, in bulk14:41
kirklandcjwatson: right, but if I want it to happen "now", i was told to ask pitti....14:41
cjwatsonif you're desperate for it to happen in sub-day timeframes, yes :)14:41
pittiright, I tried this morning, but ftp.uk.d.o. seems to be pretty behind14:41
pittihm, sorry, ftp.uk's Package lists still seem old14:42
pittistill not autosynced14:42
cjwatsonyou could always just switch ~lp_archive/bin/update-sources over to some other mirror14:43
cjwatsonwouldn't be the first time :)14:43
pittiah, we can still do that?14:44
pittiI thought it'd all be buried in LP code now14:44
cjwatsonsyncorigins.py downloads from ftp.d.o anyway ;-)14:44
cjwatsonupdate-sources isn't14:44
pittiah14:44
cjwatsonsyncorigins.py *ought* to be under our control but isn't14:44
kirklandpitti: you mentioned force-syncing *just* ecryptfs-utils last week....  is it possible for me to use those scripts and do that, pushing to my PPA instead of the real Intrepid archive?14:46
kirkland(that assumes PPA have started building Intrepid binaries, which it wasn't last I checked)14:46
cjwatsonyou can't use the LP scripts, but you can always upload the same thing manually to a PPA14:46
cjwatsonjust need to construct a suitable .changes file ...14:47
cjwatsonkirkland: anyway, I see (from happening to have a shell there) that pitti is in the process of syncing ecryptfs-utils now, so don't worry about it14:48
kirklandcjwatson: or, if the deb is completely unchanged, I should in theory be able to use the Debian .deb, right?14:48
pittikirkland: not 'force', but 'fake'; yes14:48
pittikirkland: yes, I switched to ftp.debian.org, which seems to be better ATM; sync coming in14:48
kirklandpitti: cool, thanks14:48
cjwatsonit is often possible to use Debian .debs with some care14:48
kirklandcjwatson: not "deb completely unchanged", but "package unmodified"14:48
pittikirkland: http://people.ubuntu.com/~pitti/scripts/syncpackage is the script I am using14:49
kirklandah, right, different tool chain.....14:49
cjwatsonkirkland: like I say :)14:49
kirklandpitti: thanks, i'll take a look14:49
pittikirkland: it constructs a suitable source.changes from a .dsc14:49
cjwatsonor why not just download the source and build it yourself if you're in a rush to test with it14:49
pittikirkland: but use it with a grain of salt, and only after proofreading that the .changes has the correct changelogs14:49
kirklandcjwatson: that's what I've been doing14:49
kirklandcjwatson: i've been working from the upstream's git14:49
cjwatsonperfectly reasonable for local testing14:49
kirklandcjwatson: testing/building/running that14:50
kirklandcjwatson: patching against that, sending upstream14:50
kirklandcjwatson: when the upstream maintainer takes them, he'll do a version bump14:50
* ogra_cmpc scratches head why the cmpc kernel doesnt show up in the PPA14:50
kirklandcjwatson: if the debian packager doesn't pick up the change within a week or so, i'll ask him to bump up the unstable version14:50
kirklandcjwatson: he's been very kind and responsive14:51
kirklandonce it's built in debian, i pull that dsc and build and test locally on Ubuntu14:51
kirklandcjwatson: then i usually ask pitti for a sync, if it hasn't happened14:51
kirklandcjwatson: how does that workflow sound to you?14:52
pittithere, all synced and uploaded14:52
kirklandpitti: big thanks ;-)14:52
* ogra_cmpc sighs and actually gives the right option to dput ...14:53
LaneyWould there be any problem with me doing the merge/sync for boost? It's blocking at least two merges in Universe atm.14:55
jordipitti: unfortunately we're not in that ideal world yet ;)14:56
ogra_cmpcLaney, i doubt anyone would complain if you do the work, but contact the former uploader/maintainer (see http://merges.ubuntu.com) and have him review it or so14:59
Laneyogra_cmpc: Yeah, I've just not done one for main before so thought I'd check in here ;)14:59
ogra_cmpcboost is in main, so you will need a main sponsor anyway14:59
Laneyjdstrand: You were the last uploader of boost. Do you mind if I work on the sync/merge?15:00
Laneyogra_cmpc: :)15:00
jdstrandLaney: you'll want to ask zul-- he asked me if he could do it15:00
jdstrand(and I said yes)15:00
Laneyjdstrand: Ah, right.15:00
zulLaney: go ahead15:00
Laneyzul: Thanks. Will do now.15:01
pittijordi: so, I haven't done multiarch building myself either, so I'm sorry that I cannot give you hints for that15:02
kirklandpitti: oh, i just saw another post from you to me at Jun 17 00:21:37 ...15:03
kirkland<pitti> kirkland: if you keep 'user=kirkland' in mtab, then umount works as user? I. e. it doesn't need an fstab entry? nice!15:03
kirklandpitti: that would seem the case from the umount manpage, but in practice that's not what's happening....15:03
kirklandpitti: i haven't inspected umount's code yet (on today's todo list), but empirically, umount checks existence in /etc/fstab FIRST, and errors out if there's no entry15:04
pittikirkland: I wonder whether it would be too evil to modify mount itself to (alternatively) accept user= in mtab15:04
pitti              user   Allow an ordinary user to mount  the  file  system.   The15:05
pitti                     name  of  the mounting user is written to mtab so that he15:05
pitti                     can unmount the file system again.15:05
kirklandpitti: well, either the code or the manpage needs updating, i agree with that15:06
pittikirkland: ^ the manpage seems to indicate that it's meant to be like that15:06
kirklandpitti: slangasek's objection to changing the code was mainly that that cannot be done haphazardly.....15:06
pittiso umount should continue to check fstab for the people who have /etc/mtab -> /proc/mounts15:06
kirklandpitti: yep, your reading and my reading of the manpage agree15:07
pittiof course people who do have that won't be able to use your ecryptfs-umount either then15:07
kirklandpitti: however, my test case looks like....15:07
seb128pitti: any reason that new versions srus don't move to hardy-updates? ie tomboy is a new tarball upstream specially rolled to fix one bug and has been uploaded 18 days ago15:07
kirklandpitti: 1) add fstab entry allowing user=dustin to mount a filesystem, 2) have user=dustin mount the filesystem, 3) become root and comment out that fstab entry, 4) have user dustin umount, and umount fails saying entry is not in fstab15:08
pittire15:12
pittiargh, that was the dumbest action ever15:12
pittiI dropped a piece of chocolate, and it flew straight to the power plug, hitting the switch15:12
pittiseb128: usually the reason is that nobody gave testing feedback on the SRU bug15:13
pittikirkland: last thing I got from you was "however, my test case looks like...."15:13
kirkland pitti: 1) add fstab entry allowing user=dustin to mount a filesystem, 2) have user=dustin mount the filesystem, 3) become root and comment out that fstab entry, 4) have user dustin umount, and umount fails saying entry is not in fstab15:13
kirklandpitti: weird that got dropped15:13
ograpitti, a "piece" ?15:14
pittiogra: half of an Easter bunny :)15:14
* ogra looks at his switched powerplug ... it would need at least two bars of chocolate to switch15:14
kirklandevidently germans have large pieces of chocolate!15:14
seb128pitti: well, for new versions bug we could say that the no feedback is a good sign ;-)15:14
ograkirkland, we're not swiss ... we'Re the ones with the big sausages ;)15:14
pittiseb128: are you using tomboy, and the actual hardy-proposed .debs?15:15
kirkland;-)15:15
pittiwell, with 80 cm of acceleration, even a small piece evidently has enough impulse to flip the switch...15:15
seb128pitti: yes15:15
pittiseb128: can you please say so in the SRU bug then? that's the kind of feedback I want to hear :)15:16
pittiseb128: (and yes, we should push for verifying all the currently pending stuff and get it to -updates ASAP)15:16
=== pgraner_ is now known as pgraner
norsettoasac: re. gnome-mplayer, I just sent a patch upstream to fix some license/copyright issues for translations. We therefore have some time since I would like to upload the newer version (to avoid being rejected)15:21
asacnorsetto: oh ok. thanks for looking into it15:29
asaclet me know when the bits are ready to go up ;)15:29
norsettoasac: sure15:29
pittiasac: did you hear any regressions with ffox/xulrunner rc2? 7 days in -proposed have elapsed15:42
loolc15:49
loolUps15:49
pittiogra: I'm a bit worried about the ltsp verification; none of the bugs got any feedback so far :(15:54
pittiogra: once we get a couple of "I have used that updated version for a few days in my production environment", I'm happy, but we didn't15:55
cjwatsonkirkland: workflow> sounds normal and reasonable15:59
kirklandcjwatson: thx15:59
cjwatsonooh, looks like d-i roughly builds now16:06
cody-somervillecjwatson, I thought you fixed the PPC build failures for Xubuntu.16:08
cody-somervillecjwatson, I'm still getting notifications of failures.16:08
cjwatsonyou thought wrong ;-)16:08
cjwatsonI just suggested a possibility for fixing it16:08
cjwatsonand put some provision in place to make fixing it possible16:09
asacpitti: no they are fine. we should wait till 10:00 PDT and release them16:46
asacthats 1900 our time i think16:46
=== thekorn_ is now known as thekorn
asacpitti: ok i am off now for 1h ... if you are around, please push xulrunner-1.9 and firefox-3.0 at 19:00 our time (or slightly in advance). thanks17:36
asac(to -updates)17:36
cody-somervillecjwatson, okay :)17:45
=== qense is now known as qense|dinner
ograpitti, well, as i predicted, ltsp users are reluctant to upgrading their chroots (thats why its important for me to get it on the 8.04.1 CD) ... all i can say is that i verfied all of the fixes and am running ltsp here with them successfully since without problems ... afaik stgraber verified two of them as well18:39
stgraberogra: yep I did, I'll try to verify the lts.conf ones (X parameters) too18:40
ograthat would be great18:40
calcslangasek: do you happen to know what is currently holding OOo out of updates?18:51
calcor is it just a time thing?18:51
slangasekcalc: the SRU policy, which states there's a 7-day waiting period barring exceptional circumstances? :)18:52
calcslangasek: ah ok18:52
=== qense|dinner is now known as qense
tedgIs there a good reason that I have to do "(cd mypackage; debuild)" instead of "debuild mypackage"?18:58
tedgIt's mighty annoying that debuild and dput have to be done in different directories.18:58
fqhany one familiar with script? I want to erase all the first characters "+" of each lines in the diff file, how to do it?19:00
slangasektedg: I'm going to take it as assumed that any reason given would not be accepted as a good reason. :)  But you could write "tedbuild" which wraps debuild... :)19:01
slangasekfqh: why would you want to do that?  If you do that, what you have is no longer a patch...19:01
fqhslangasek: Actually, it is a completely new c source file. so all line starts with "+". after erasing "+", my tool will be able to parse that source file19:05
slangasekfqh: sed -e's/^\+//'19:05
tedgslangasek: I'd rather patch debuild to do it right :)19:06
fqhslangasek: thanks very much19:06
slangasektedg: I think any syntax you would come up with would be less optimized for the common case than just running "dput ../foo.changes" ?19:07
slangaseksince typically, one edits a package before building it19:07
* ScottK agrees with slangasek.19:08
ograand all the output of dpkg-buildpackage/debuild usually has the ../ if you are in the source dir19:09
* ogra finds that very convenient for copy/paste19:09
tedgI don't ever edit the package before building it.  I'm always editing the debian directory in the VCS and then copying it over.19:10
tedgSo it's something more like "tar -xvzf mypackage ; cp -a vcs/debian mypackage ; cd mypackage ; debuild ; cd .. ; dput mypackage"19:11
slangasekoh, well, keeping only the debian directory in the VCS is its own kind of breakage ;)19:11
* mvo raises a eyebrow19:11
pwnguinputting the whole source package in vcs makes sense to me. whether it's feasible today's another story19:12
* tedg is going to laugh when slangasek gets hit with the bazaar packaging dunk tank :)19:21
slangaseklike the grub package that I put into bzr myself for maintenance?19:22
tedgWhere are you putting the bazaar branches for the packages?  I put them under "~ted-gould/<package name>/ubuntu-packaging" -- I didn't know if they should go under /ubuntu/ or something different.19:29
pittistgraber, ogra: fine; can you please say so in one of the bug reports?19:32
pittiasac: ok; I guess we can move them now then?19:33
pittiasac: ok, seems slangasek beat me to it19:34
slangasektedg: for grub, it's https://code.launchpad.net/~ubuntu-core-dev/grub/ubuntu (i.e., a shared branch committable by all of core-dev)19:38
slangasekone can obviously have other personal branches too19:38
mvohey cody-somerville! what environment does xfce set when it runs? something like XFCE_SESSION or XFCE_SESSION_ID or something like this?19:38
mvoto detect if a session is running19:39
mario_limoncielltedg, but its not necessarily <package name>, you have to make a LP project for that part of the branch name19:39
tedgslangasek: Hmm, that'd imply that I'm core-dev ;)19:39
slangasektedg: well, if it's a package in main, the official packaging branch (and the one represented in the Vcs-Bzr field) ought to be one that core-dev can commit to... :)19:40
mario_limoncielltedg, so in the case for the mythbuntu project, we have about 15 branches out there, so we push them to ~mythbuntu/mythbuntu/<package name> for sanity19:40
slangasekor the subset of core-dev that maintains the package in practice, I guess, such as ubuntu-desktop19:40
tedgmario_limonciell: Ah, but I usually have "ubuntu-packaging" and "debian-packaging" -- so I guess they'd become "<package>-..."19:41
mario_limoncielltedg, all the more reason to make shoe packaging the same :)19:41
mario_limonciellshoe=those19:41
tedgslangasek: Well, having a branch that core-dev can commit to does me no good, as I'm not core-dev.  But ubuntu-desktop would be interesting.19:41
liwpwnguin, it's perfectly feasibly to have the entire source for a package in a bzr branch (been there, done that...)19:42
mario_limonciellit just gets a wii bit slow when you have a very large source package and need to do a full checkout somewhere19:42
slangasektedg: the commit rights on the "official" packaging branch should match the commit rights in the archive; that's certainly the game plan for the eventual everything-in-bazaar scheme.  You would just prod someone to merge your branch (&& upload), rather than prodding to upload19:43
ograpitti, ok, commented on all of them, the NBD_PORT one actually got some more feedback :)19:43
tedgslangasek: While I see what you're saying, that'd be very annoying for me personally.19:44
pittiogra: thanks! hm, I wonder why I didn't get mail about it; is ubuntu-sru sub'ed?19:44
pittiogra: anyway, I have the bug list here, I'll look at that19:44
ograthanks19:44
ograyep, "SRU Verification" on all of them19:45
pwnguinare there any packages still in debian/ubuntu that require explicit distribution as patches?19:45
stgraberI receive mail notification only for one of them (so far), maybe LP is a bit slow with bugmail19:46
stgraber*received19:46
pitticjwatson: ah, d-i upload; did the dhcp changes work out?19:47
pittiogra: ah, sru-verification; I meant ubuntu-sru19:47
ograoh, no, should i ?19:47
pittipwnguin: yes, at least LaTeX is like that19:47
pittiogra: ah, that explains it19:47
ograi have them all open anyway atm19:47
pittiogra: if it's quick for you, would be nice19:48
pittiogra: ubuntu-sru > slangasek and me (management); sru-verification -> QA team (verification)19:48
pittiyes, slightly confusing19:48
pwnguinpitti: ah right19:49
ograah, k19:49
asacpitti: thanks. sorry for asking steve. didnt know if and when you return and wanted to get the bits out19:50
pittiasac: why sorry? no need to apologize for causing less work for me :-P19:50
* pitti hugs asac19:51
* pitti hugs heno, too, for verifying all the OO.o SRU bugs19:51
pittiogra: oh -- not fixed in intrepid yet?19:51
pittiogra: are all the fixes in bzr trunk?19:52
ograpitti, still fiddling with the new setup of the ltsp source19:52
ograyes19:52
ograupstream19:52
ograbut we rearranged the complete tree and i'm merely building new packages and starting to consider to just take vagrantc's work from debian to avoid that in the future19:53
ograso it takes a bit longer this time19:53
* heno hugs pitti for helping push .1 along19:54
pittiogra: ok, so I can reasonably rely on the fixes not getting lost for intrepid?19:55
ograpitti, yes19:55
pittiogra: indeed there was quite a lot of positive feedback from other people; so I just didn't see it due to the missing subscription19:55
pittiso all is well19:56
ograyay :)19:56
ogranow to find out why my classmate kernel build failed *again*19:56
* ogra sighs loudly .... i thought i had cheated the abicheck 19:56
pittiogra: so updating the ltsp package doesn't cause the chroots to be rebuilt?19:57
ograpitti, ergh, no ...19:57
pittiogra: how do you automatically fix bugs in the chroots then?19:58
ograthat would be mean19:58
pitti"Don't introduce bugs"?19:58
ograthere is no automatism19:58
stgraberpitti: you can't19:58
pittiogra: well, surely you need to at least apply security updates?19:58
* pitti thinks "libssl!!!!"19:58
ograyou need to chroot into it, update, and re-roll the squashfs19:58
pittiright, that's what I meant19:58
stgraberpeople have to chroot inside it, run "apt-get update && apt-get dist-upgrade", then run ltsp-update-client19:58
stgraberogra was faster ... :)19:59
pittiso it'd be impractical to do that in the ltsp postinst?19:59
ograad i dont want to hog peoples machines for 20min for rebuilding an image while upgarding19:59
pitti(so that fixes in ltsp actually get applied)19:59
pittiogra: *shrug* better than unsafe SSL keys :)19:59
stgraberyou can't do that in postinst as you don't know where the chroot is, if it's using nbd or nfs, you don't even know if it's the same arch as the server :)19:59
pittistgraber: well, the arch shouldn't matter, should it? As you say, it's more or less "chroot /foo apt-get"?20:00
ograpitti, well, ldm wont let you log in without updating the keys indeed20:00
ograthe server prevents that20:00
ograpitti, powerpc chroots on x86 do matter for some packages :)20:00
stgraberpitti: I have an amd64 server with a powerpc chroot on it, people with large network can do that to match all their thin clients20:01
stgraberand ogra was faster, again ...20:01
ograand if we get arm, arm will also have a problem here20:01
pittiright, I don't question that20:01
pittithat wouldn't work locally, true20:01
ograi was playing with some qemu ideas a year ago20:01
pittiwell, at least not very easily20:01
ograbut the time i have left for ltsp gets less and less so beyond noml maintenance and fixes there is not much dev time atm20:02
ograso that never got implemented20:02
ograi count on the other distros though, fedora just had their fors ltsp5 release, opensuse plays with ltsp5 in kiwi now and gentoo just had their first successfull install20:03
ogras/fors/first/20:04
stgraberusually LTSP server admins are aware of security and updates and update their chroot at the same time as the servers (for large network at least). You can't take 100% CPU power for 20 minutes during every upgrade affecting the chroot on a LTSP server with users using it ...20:06
stgraberogra: do you know if guys from the other distros plan to integrate it with their respective update managers so it proposes to update the chroot too ? (or similar way of solving the issue)20:07
ograno idea20:07
ograi discussed that with mov once but never got around to implement that either20:07
ogra*mvo20:07
stgraberanyway, I don't see much possible security issues with a thin client. Even if they manage to get root access, that won't help them as it doesn't have an hdd and will be stuck with a squashfs+unionfs setup ...20:10
ograwell, there might be some ... in case external access from teh network side gets possible due to some bug20:10
lagayeah, but are in your network..20:10
lagayeah20:10
ograi'm not worried about local exploits either with a 100% locked down system20:11
ograbut remote stuff can be harmful20:11
stgraberyou shouldn't have access to the outside on the thin client network20:11
stgraberthin clients should only have access to the terminal server and nothing else20:11
=== salty_horse is now known as salty-horse
mkrufkymario_limonciell / superm1: ping me when you want to20:25
=== dpm_ is now known as dpm
=== fta_ is now known as fta
=== thegodfather is now known as fabbione
Ngdo auto-logged-in users not qualify for consolekit is-local?22:22
tormodis it only me, or is there a problem with ssh+svn on alioth.d.o?22:34
=== mthaddon changed the topic of #ubuntu-devel to: Launchpad is going down in from 22:00 UTC until 03:00 UTC for hardy server upgrades | Regenerate your SSH keys! http://www.ubuntu.com/usn/usn-612-2 | Ubuntu 8.04 LTS released! | Development of Ubuntu (not support, not application development on Ubuntu) | #ubuntu for support and general discussion for dapper/feisty/gutsy/hardy, #ubuntu+1 for intrepid | #ubuntu-motu for getting involved in development | http://wiki.ubuntu
cjwatsonpitti: yeah, it was fine, thanks22:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!