=== bjf is now known as bjf[afk] === almaisan-away is now known as al-maisan [07:10] Good morning [07:59] Guten Morgen pitti [07:59] -hum, I didn't say hi there? weird, should be tired today ;)) [08:00] pitti, good morning [08:01] pitti, can you push a couple packages through unapproved for me? compiz and light-themes, both UIF exceptions that robbiew approved [08:01] kenvandine: the queue will be reviewed, I'll have a look at it [08:01] pitti, and if you could also do telepathy-butterfly and telepathy-mission-control-5 [08:02] didrocks, thx [08:02] i am going to bed :) [08:02] kenvandine: oh, another compiz? [08:02] kenvandine: I'll have a look, yes [08:02] pitti, yeah... a few design tweaks [08:02] robbiew approved the exception [08:02] just some defaults [08:02] and the theme update too [08:03] the telepathy ones are just getting us to the versions upstream recommends [08:03] kenvandine: enjoy your evening :) [08:03] kenvandine: you didn't beat me, that's a fail :p [08:03] hehe... i will enjoy the pillow [08:03] hehe [08:03] * didrocks hugs kenvandine [08:03] didrocks, i see it the other way... i win! [08:04] yeah, for you health, i guess :-) [08:04] your* [08:04] :) [08:04] good night everyone! [08:04] good night kenvandine! [08:06] pitti: can I grab you for a minute about a libindicator change? [08:06] didrocks: what's up? [08:07] pitti: so, we have this bug for quite a long time (bug #637692) [08:07] Launchpad bug 637692 in unity (and 6 other projects) "Action for top-level dropdown menu item not activated (affects: 3) (heat: 16)" [High,Confirmed] https://launchpad.net/bugs/637692 [08:07] which prevent some applications to use the accelerators in appmenu [08:07] and so menu item not activated [08:07] ted fixed it yesterday, but this require an ABI break [08:07] (not enough free slots in a structure, has to be changed) [08:08] so, we have 8 source package depending on that one [08:08] and bumping libindicator0 -> libindicator1 [08:08] dbarth explains it in comment #4 [08:08] I can handle the transition today if the release team ack it [08:08] didrocks: adding a new field at the end of a struct is an abi break? [08:09] oh, do library clients have to fill it out, and the library expects it to be correct? then yes [08:09] pitti: I guess so, isn't it? as the structure doesn't have the same size? [08:09] right [08:10] so, do I need to do some paperwork in addition to the comments on the bug? (we wrote that yesterday with dbarth) [08:10] I think it's better to speak with you first :) [08:14] didrocks: this doesn't sound too bad, so please go ahead [08:14] also, another note, the issue is that people will only see one part of the indicators during the transition [08:14] * didrocks pastebin the summary he made yesterday [08:15] some discussion with tedg because he wanted a conflicts [08:15] (on the new bin package) [08:15] but updated [08:15] didrocks: hang on, new binary package? [08:16] I thought we just need a new library soname? [08:16] pitti: libindicator1 instead of libindicator0 [08:16] ah [08:16] yeah [08:16] didrocks: why would you want a conflicts? [08:16] libindicator0 will be NBS, and all rdepends transitioned [08:16] one second, pastebin one click away :) [08:16] libindicator1 can't conflicts: libindicator0 [08:17] http://paste.ubuntu.com/498267/ [08:17] that's why I told to ted [08:17] I just summarize it there ^ [08:17] ted is annoyed because some indicators won't show during the transition [08:17] the indicator protocol isn't versionned [08:18] so, if the render uses the new library (with the soname bump), only those indicators will be shown [08:18] without understanding the details of his rationale, but Breaks/Conflicts of different library ABIs is a no, no, no, no [08:18] ok, you agree then :) [08:18] what you _can_ do is to add breaks to the rebuilt packages against libindicate0 [08:18] * didrocks feels better now that pitti tells it :) [08:18] but of course that wouldn't help you for the partial upgrade case [08:19] right, that's why I explained yesterday [08:19] but *shrug*, if you do partial upgrades and don't upgrade one indicator, you'll break that indicator and get to keep both parts, yes [08:20] I agree, and at least, they won't be uninstalled but people in a partial upgrade :) [08:22] pitti: ok, so thanks, I'm handling the transition today [08:28] kenvandine: I followed up to the bugs, still some open questions [08:30] didrocks: ok, let me know when you need unapproved/NEW poking [08:31] didrocks: would be nice if you could add versioned b-deps to the rebuilds, so that we can accept them all at once and have the depwaits sort it out [08:31] pitti: thanks, I will (just rebuilding everything first) [08:31] pitti: will do :) [08:32] pitti: we have in addition 4 packages: xfce4-indicator-plugin, lxpanel, cairo-dock-plug-ins, ubiquity. So the total number is 12 [08:33] lxpanel is FTBFS, I've already mentionned it to lubuntu guys and they will fix that later today, so I won't upload it [08:33] okay [08:56] dobey: do you still remember ./DistUtilsExtra/command/check.py? would you mind to change the license to GPL-2 or later, so that it matches the rest of the code? [08:57] dobey: if you agree, can you please say so by mailing 597548@bugs.debian.org? [09:05] Morning/evening all. [09:07] hey RAOF, how are you? [09:07] Pretty good. [09:07] Being able to sleep in until 11 was a good call. :) [09:08] hey RAOF! [09:08] didrocks: Good... morning? [09:08] RAOF: hah, wearning off the jetlag? [09:09] pitti: Yup. I got back late yesterday afternoon. [09:09] I no longer am so tired I feel physically sick. Yay! [09:09] RAOF: heh, how it is to be to the right side of the world? ;) [09:10] Now that I'm back to the future, it's much better :) [09:11] RAOF: hehe :) [09:12] Were there any other firedrills due to my miscommunication while I was out of contact? :( [09:14] RAOF: not a lot, no, there was something IIRC, let me look at my logs [09:15] RAOF: false alarm, it will be for natty :) [09:16] RAOF: just think to close your WI on http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-ubuntu-10.10.html [09:26] good morning everyone [09:26] hey chrisccoulson [09:27] hey pitti, how are you? [09:27] doing well, thanks! how about you? [09:28] pitti - i'm good thanks, although a little bit tired [09:28] 6am start for 2 mornings in a row ;) [09:28] uh, how's that? [09:28] kids? [09:28] hey chrisccoulson! [09:29] pitti - yeah, i get up with my daughter on tuesday and wednseday mornings, as my gf works a night shift on tuesday night [09:29] hey didrocks [09:31] ooh, 2 bugs fixed for me already this morning. thanks to whoever approved my uploads :) [09:32] you're welcome [10:49] chrisccoulson: do you still work on the gtk bug? (again, if you think you don't have the time, or don't have any clue, I can point you to other small bugs :) [11:02] didrocks - yeah, i'm still spending some time on that [11:02] i'm determined not to have to give up on it ;) [11:02] but i can look at some other bugs too [11:03] chrisccoulson: hehe, good luck then! :) [11:04] chrisccoulson: if you want to change a little your mind, maybe bug #644447 is small and easy, do you want that I assign it to you? [11:04] Launchpad bug 644447 in indicator-application (Ubuntu) "When burning a disc with Brasero and with Ambiance theme can't read the text in the indicator applet (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/644447 [11:04] didrocks, yeah, that ones fine [11:04] chrisccoulson: jujst to look if it's because of the indicator or brasero :) [11:04] chrisccoulson: if it's the indicator, I'll give it to tedg, ok? [11:04] sure, no problem === MacSlow is now known as MacSlow|lunch === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === MacSlow|lunch is now known as MacSlow [14:26] grrrr /usr/include/cairo/cairo.h:1976: error: comma at end of enumerator list [14:26] fix is trivial, and already upstreamed. any chance we get an update? [14:38] could someone please take a look at bug 625696, I have a branch ready for merge, or alternatively I could make a debdiff for sponsoring :) [14:38] Launchpad bug 625696 in nautilus (Ubuntu Maverick) (and 4 other projects) "Nautilus crash when IM preedit (affects: 18) (dups: 7) (heat: 109)" [High,Triaged] https://launchpad.net/bugs/625696 [14:44] cyphermox, i can't sponsor nautilus, but didrocks might be able to take a look :) [14:45] can do it, but not just know [14:46] didrocks, all good [14:46] didrocks, is a branch fine or do you prefer debdiffs? [14:46] cyphermox: can you subscribe me to the merge request? [14:47] cyphermox: just do a merge request :) [14:47] cyphermox: your source is ~ubuntu-desktop/nautilus/maverick, right? [14:47] sure, I'll do that.. there isn't even a merge rq yet [14:47] yup [14:47] oupss [14:47] ~ubuntu-desktop/nautilus/ubuntu :) [14:47] oh wait no [14:47] it's a debian/ branch only [14:47] d'oh [14:47] well, i'll subscribe you ;) [14:48] i am doing murrine, btw [14:49] didrocks, anything you can do for cairo? (problem described above) [14:50] fta2: not like if I'm already postponing important changes for hours :) [14:50] is it making something failing? [14:51] didrocks, can't build anything that has quite aggressive flags and werror [14:51] it's a trivial 1 line fix [14:51] 1 char fix even [14:51] fta2: sure, can you send me a patch? I'll handle it when it's quieter there [14:52] didrocks, debdiff? (it's been fixed ~12d ago upstream: http://cgit.freedesktop.org/cairo/log/) [14:53] fta2: what is better for you :) [14:55] didrocks - any other bugs? :) [14:55] bug 644447 is a theme issue btw [14:55] Launchpad bug 644447 in light-themes (Ubuntu) "When burning a disc with Brasero and with Ambiance theme can't read the text in the indicator applet (dup-of: 617192)" [Undecided,Invalid] https://launchpad.net/bugs/644447 [14:55] Launchpad bug 617192 in light-themes (Ubuntu) "[maverick-beta] Disabled menu items unreadable (affects: 20) (dups: 5) (heat: 200)" [Low,Confirmed] https://launchpad.net/bugs/617192 [14:55] chrisccoulson: can you ping Cimi on #ayatana? [14:56] didrocks - yeah, sure [14:56] thanks :) === bjf[afk] is now known as bjf [15:17] pitti: ping [15:18] didrocks: no new libindicate in maverick yet? [15:18] hey nessita [15:18] pitti: hello! I was wondering if could help me with lp-project-upload [15:18] if you* [15:18] nessita: sure; doesn't it work for you? [15:19] pitti: it does, as long as my project doesn't have more than one series... is there any way of using it with more than one serie? like having trunk and stable-1-0 [15:19] sorry, not with the current version [15:19] oh! [15:19] * nessita cries [15:19] if len(proj.series) != 1: [15:19] print >> sys.stderr, 'Does not support creating releases if more than one series exists.' [15:20] * nessita cries some more [15:20] nessita: so, it wouldn't be too hard to add support for that, you were just the first one who asked :) [15:20] pitti: all is ready and we are testing and rdepends, but there is still an issue with dbusmenu not building [15:20] pitti: I *love* lp-project-upload [15:20] pitti: ted is looking at it [15:21] pitti: how much for that feature? /me bargains [15:21] :-D [15:21] nessita: I have my local patched version to add to latest series :) [15:21] nessita: how about a beer at UDS? :-) [15:22] didrocks: shhh :) [15:22] ;) [15:22] pitti: cheater! you have that ready already ;-) [15:22] nessita: I'm in a meeting right now, and then I have a job interview, but I can probably get to it later this evening [15:22] pitti: ok, thanks. No rush though [15:22] nessita: no, I haven't.. [15:23] pitti: I'll borrow's didrocks patch if he allows me to [15:24] nessita: if "latest series" is enough for your immediate need, that sounds fine [15:24] pitti: I may tweaked it to the oldest series or latests as I see it fit :-) [15:25] didrocks: can I borrow that patch? [15:25] nessita: sure, one second :) [15:25] * nessita only has 2 series, so oldest-latest is enough :-D [15:25] there goes my beer .. *sod* [15:26] j/k, /me hugs nessita and didrocks [15:26] and the hug show starts! [15:26] * didrocks hugs pitti back :) [15:26] nessita: http://paste.ubuntu.com/498521/ [15:26] * nessita hugs back as well [15:26] * bcurtiswx_ watches the "show-the-love-ometer" peak [15:27] I didn't propose it to pitti as "last serie" isn't best for everyone I guess [15:27] (be careful series = proj.series[-1] doesn't work with launchpad objects) [15:28] didrocks: oh, just -1? does it have a guaranteed ordering? [15:28] didrocks: it does not??? I was *about* mentioning it. Thanks! [15:28] pitti: yeah, I've tested a lot on different project and it seems to be historically ordered [15:29] nice [15:29] pitti: I tried in staging with crazy cases :) [15:29] pitti: not sure launchpadlib ensure it will stay like that [15:29] pitti: can I propose a branch? if so, where to? [15:29] nessita: yeah, it doesn't… got trapped at the beginning :) [15:29] nessita: it's in ubuntu-dev-tools [15:30] nessita: so, http://codebrowse.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/changes [15:30] pitti: ack [15:34] didrocks: I was just wondering because there's an xfce4-indicator-plugin in the queue [15:34] didrocks: I'll keep it until the new libindicator actually hits [15:34] pitti: oh? is it mine? [15:34] * didrocks checks [15:34] didrocks: the changelog says so [15:34] didrocks: oh, just -1? does it have a guaranteed ordering? [15:35] oops [15:35] :) [15:35] http://launchpadlibrarian.net/56248381/xfce4-indicator-plugin_0.0.1-2build1_source.changes [15:35] too many things in // ;) [15:35] I pushed also cairo-dock [15:35] pitti: the build-dep should be fine normally [15:36] pitti: are there any tests for ubuntu-dev-tools? [15:36] nessita: not sure, it's been a while since I touched it [15:36] pitti: ack [15:36] nessita: but I wouldn't propose a simple "use the last one" for merging, I'd rather add a --series option [15:37] otherwise it's way too easy to accidentally hit the wrong series [15:37] pitti: I agree [15:37] didrocks, empathy 2.32.0 will be released monday FYI [15:37] bcurtiswx_: I know, the all GNOME 2.32 is due to next Monday :) [15:37] thanks ;) [15:38] OK, i now know all gnome 2.32 is due Monday.. [15:38] * bcurtiswx_ adds this to the learn something new everyday ;) [15:38] :) [15:41] * bcurtiswx_ is also a chat killer apparently :P [15:42] no, you're not capable of killing others by that kind of chat [16:21] cyphermox: can I trigger the nautilus crash easily? [16:23] didrocks, yup. right click in the typeahread popup in icon view, then select any "special" input method, it doesn't have to be IBus [16:23] e.g. Cyrillic, Vietnamese, tend to work quite well [16:24] cyphermox: oh right [16:25] ok, getting your merge now [16:43] hi guys :) [16:53] didrocks, kenvandine: Have you guys by any chance noticed any bugs reported against gtk+ or gnome-panel that might be related to submenus remaining on the screen but not responding to updates? Then if you drag another window over that area you see parts of the other window left behind? Screenshot: http://imgur.com/OzDXz [16:54] bratsche: urgh, not really… apart when apps are not responding, but otherwise, no… [16:54] bratsche, not that i have noticed [16:57] rodrigo_: hey [16:58] hey didrocks [16:58] rodrigo_: is it a known bug that I can show/hide the ubuntu one in right-click->ubuntu one… but I see no effect in nautilus? [16:58] didrocks, yes, there is no way to tell nautilus to stop displaying the ribbon [16:59] Hey rodrigo_ how's it going? [16:59] didrocks, we can easily fix though, listening to the gconf changes and hide/show the ribbon [16:59] didrocks, it just didn't happen in time, but I can do it [16:59] rodrigo_: oh, right, I remember about that API [16:59] hey bratsche [16:59] rodrigo_: well, just do what you think it's better for the user. I think the current behavior is just weird from a user point of view :) [17:00] didrocks, yes [17:00] didrocks, if you file a bug, I'll fix it for maverick === al-maisan is now known as almaisan-away [17:00] didrocks, if I file the bug and provide the fix, it doesn't look like a good way to convince the release team :) [17:01] rodrigo_: right, will do then, ubuntuone-client, right? [17:01] didrocks, assign it to me, yes, u1-client [17:01] rodrigo_: will do, thanks! [17:13] didrocks, http://people.ubuntu.com/~fta/cairo/ [17:37] james_w, ping [17:40] hi kenvandine [17:40] james_w, you've had a look at python multiprocessing... mind taking a quick look at a patch? [17:40] https://code.edge.launchpad.net/~roignac/gwibber/Bug628686-unblocking-UI/+merge/35893 [17:40] that definitely makes startup of the client snappy... but seems like a hack to me [17:40] and i suspect it would prevent those dbus call_blocking errors [17:41] i would love to fix that before i do a release in a few minutes... [17:42] kenvandine: I don't know, it feels wrong to me [17:42] yeah, that was my thought too... [17:42] so right now, if you start gwibber when gwibber-service isn't running, the client doesn't show until the first set of jobs complete [17:43] and sometimes it times out [17:43] so this bypasses that [17:43] but definately seems like it could cause other problems [17:44] however, this does help knowing where that is happening [17:44] does it need to call get() at all? [17:44] then we don't get the failures [17:45] that would be cleaner than what is there [17:45] indeed [17:46] actually that might not be bad.... we don't do anything with the timeout exception yet anyway [17:46] which i am sure is why he did this [17:46] well it's just ignoring it there [17:46] yeah... we basically ignore it anyway [17:46] what he has done is just ensure that call takes 0 time [17:46] the idea was someday we might have some retry... [17:46] yeah [17:46] you can do that in cleaner ways [17:47] seeing as it's in a thread anyway, can't you not call get() with a timeout, and implement a polling loop with your own timeout? [17:47] yeah... but we might not need to do that anyway [17:48] seeing as the result of that call isn't used, and you have a callback, I don't think you need to call get() [17:49] i think the idea was we wanted to be able to get the Timeout exception [17:49] but timeouts are generally transient [17:50] and curl operation will timeout if it has to anyway [17:50] james_w, good compromise :) [17:51] james_w, thx [17:51] np [18:24] question: what's the recommended way of sending a signal to a process when installing a package upgrade? [18:25] nessita, you mean via dbus? [18:25] devildante: nopes, in a preinst script for example. I'd use killall, but lintian will not approve :-) [18:25] killall -signame [18:26] hmm, don't know... not enough experienced, I guess :p [18:26] devildante: thanks anyways. I think I'll trying with pkill [18:30] nessita, usually something like "kill -s HUP", but the process needs a handler for that signal [18:30] i'm sure someone asked the same question a few days ago for U1 ;) [18:31] chrisccoulson: but you need the pid for the process in order to use kill. I was hoping to use the name of the process [18:31] chrisccoulson: I think I got it, I was using pkill without the -f option, that's why my process wasn't killed [18:31] nessita, "kill -s HUP `pidof `" [18:32] that's awful! :-) [18:33] chrisccoulson: and the pidof doesn't work for process like "/usr/bin/python /usr/lib/ubuntu-sso-client/ubuntu-sso-login" [18:33] chrisccoulson: pkill -f -HUP works :-) [18:33] :-) [18:33] thanks! [18:35] ok, sponsor hunter time! is anyone available to sponsor/upload https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.2/+merge/36352 ? [18:39] i don't think i can sponsor that :( [18:39] i'm not special enough ;) [18:42] didrocks: around? [18:43] robbiew: yeah [18:44] chrisccoulson: thanks anyways [18:44] didrocks: https://bugs.launchpad.net/ubuntu/+source/utouch-grail/+bug/644385 needs some assistance in sponsorship....oubiwann and MT would thank you greatly ;) [18:44] Ubuntu bug 644385 in utouch-grail (Ubuntu) "[FFe] Update version of utouch-grail to 1.0.14 (affects: 1) (heat: 8)" [High,Confirmed] [18:44] didrocks: it's been ack'd by pitti already [18:45] robbiew: if I can sponsor without testing I can do it now. if it needs testing, I'm still on the libindicator transition and unity new release, so I can queue it :) [18:45] oubiwann: ^^^? === rickspencer3_ is now known as rickspencer3 [18:46] hey kenvandine, would you be available to sponsor a new ubuntu-sso-client release? merge proposal located at https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.2/+merge/36352 [18:47] robbiew: thanks... didrocks: gimme a sec, and I'll let you know how thoroughly it's been tested [18:47] oubiwann: sure :) [18:47] nessita, /me looks [18:47] nessita: I suggest ask on #ubuntu-motu for sponsorship. [18:47] just joined, oubiwann [18:48] rydberg: cool [18:48] ari-tczew: really? I was told this was the proper place to do it... [18:48] ari-tczew: not for things in main… [18:49] nessita, i am on it :) [18:49] kenvandine: thanks! [18:49] didrocks: I heard that also for main. [18:49] didrocks, oubiwann: the grail changes have been tested in desktop and unity settings since sunday, on five or six different machines, build tested, runtime tested, corner-case tested. [18:49] it's a new [18:49] ari-tczew: where did you hear that? /me wants to hear as well [18:50] ari-tczew: can be, but we are used to work that way with people we know and we keep doing that [18:50] rydberg: great, just signing then :) [18:50] didrocks, the fix for cairo i talked about earlier: http://people.ubuntu.com/~fta/cairo/ [18:50] oubiwann: ^^ [18:50] fta: yeah, queuing it too :) [18:50] nessita, looks quick, i have another call in 10m... crazy day :/ [18:50] * didrocks will soon be at 30 uploads today [18:50] didrocks: thanks! [18:50] didrocks, wow [18:51] didrocks, thanks man :-) [18:51] damn libindicator change! [18:51] didrocks, i rebuilt all of those 4 times yesterday :) [18:51] kenvandine: I hate hate hate now! :-) [18:51] nessita: from developers on #ubuntu-motu [18:52] i plan to sleep tonight :) [18:52] kenvandine: seems to start badly for me :) [18:52] 14h-16h maybe I'll reach 18h today :) [18:54] oubiwann: rydberg: uploaded [18:54] nessita, did you publish the tarball? [18:54] didrocks: phenomenal, thanks! [18:54] *bows* much obliged [18:54] oubiwann: rydberg: yw, for just a gpg signature, it's not a lot compared to building and testing :) [18:55] but its important :-) [18:59] kenvandine: I did, in the stable-1-0 release, which is the one binded to maverick [19:00] kenvandine: shall I change the watch file in a way that uscan detect that tarball? I was wondering about that... [19:00] kenvandine: tarball was uploaded to http://launchpad.net/ubuntu-sso-client/stable-1-0/1.0.2/+download/ubuntu-sso-client-1.0.2.tar.gz [19:03] pitti: https://code.launchpad.net/~nataliabidart/ubuntu-dev-tools/multiple-series-for-project-upload/+merge/36354 [19:14] kenvandine: did you update telepathy-gabble, btw? [19:18] didrocks, no... i couldn't [19:18] fta: cairo fixes? which? [19:18] it requires telepathy-glib update [19:18] kenvandine: ok, it was the gir issue :) [19:18] yes [19:19] fta: the trailing comma one? that should only be a problem if someone is misinformed enough to compile stuff with -pedantic :) [19:20] slomo, hit me already a few times since it landed. and it doesn't hurt to have the fix. it's also fixed upstream [19:21] kenvandine: thanks for the info, I can close one tab :) [19:21] hehe [19:21] slomo, and i don't consider -pedantic bad, it often help spot weird situations [19:21] +s [19:22] fta: sure, having that fix is fine i only didn't want to upload a new version just for that :) -pedantic is often really pedantic and using it doesn't guarantee that you only use language parts of the currently selected standard anyway [19:24] slomo, it enforces good practices, such as forcing you to check return values from almost everything, good to create resilient code [19:25] also avoid bad casts [19:29] fta: it does? well, for all these things there are -W flags too and they don't enable the nitpick mode in gcc that doesn't show any real problems ;) [19:49] ok... what is the right way of referencing a download file in a watch file for a series? [19:50] http://launchpad.net/ubuntu-sso-client/+download?start=10 .*/ubuntu-sso-client-([0-9.]+)\.tar\.gz [19:50] i am not thrilled with that [19:50] i tried putting the series in the url... and even the version but it doesn't like that [19:55] kenvandine: yeah, I tried that myself. I was hoping that http://launchpad.net/ubuntu-sso-client/stable-1-0/+download would work [19:56] i uploaded with this change to the watch file... but there must be a better way [19:56] i guess http://launchpad.net/ubuntu-sso-client/+download has some magic in it [19:57] kenvandine: any idea who can we ask? [19:58] people i don't want to bother atm [19:58] didrocks probably knows... but he is busy and i want him to get some rest at some point :) [19:58] kenvandine: https://launchpad.net/ubuntu-sso-client/+download?start=10 is not listing the stable-1-0 release for me, is it for you? [19:59] heh [19:59] yes it is... [19:59] weird [19:59] for uscan? [19:59] well, actually it finds the tarball [19:59] yeah [19:59] uscan --verbose first for debugging :) [19:59] wasn't useful [19:59] it finds the tarball? what's the issue then? [19:59] it seems hacky [19:59] https://launchpad.net/ubuntu-sso-client/+download?start=10 [20:00] hum, not good [20:00] I have example in unity [20:00] one second [20:00] i wonder if i used --verbose when i hate the typo in the series... [20:00]