=== bjsnider_ is now known as bjsnider
=== salem_ is now known as _salem
=== henrix_ is now known as henrix
=== mnepton is now known as mneptok
=== henrix_ is now known as henrix
hallynjibel: (holiday today) saw the emails...  will look tomorrow.03:58
=== Mirv_ is now known as Mirv
=== Lutin is now known as Guest85904
=== mfisch is now known as Guest95146
=== zumbi_ is now known as Guest95491
=== happyaron is now known as Guest32898
=== ffio is now known as Guest45788
=== Tm_T is now known as Guest51964
=== shirgall is now known as Guest42483
=== jbicha is now known as Guest14309
=== Ursinha is now known as Guest36665
=== DarrenS is now known as Guest82988
=== zoktar_ is now known as zoktar
=== Nigel_ is now known as G
pitti_Good morning04:38
=== pitti_ is now known as pitti
=== tvoss|errands is now known as tvoss
=== popey_ is now known as popey
dholbachgood morning06:35
Noskcajroaksoax, daily reminder, testdrive07:20
=== ivoks_ is now known as ivoks
=== sraue_ is now known as sraue
=== lan3y is now known as Laney
=== oSoMoN_ is now known as oSoMoN
=== smb` is now known as smb
=== tsimpson_ is now known as tsimpson
pittimeh, https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-ubuntu-drivers-common/28/ regressed -- tseliot, could it be that the new kernel broke our nvidia/fglrx drivers?08:27
* tseliot looking08:28
=== Cimi_ is now known as Cimi
=== ejv_ is now known as ejv
pittitseliot: fglrx fails with08:29
pittiAssertionError: 100 != 0 : update-alternatives: error: error creating symbolic link `/usr/lib/i386-linux-gnu/xorg/extra-modules.dpkg-tmp': No such file or directory08:29
pittitseliot: nvidia-304 seems to work, but 304-updates, 310 and 313 don't08:30
tseliotpitti: I think I have a fix for the alternatives error08:30
pittitseliot: ah, great; those are always from a clean08:30
pitti... installation08:31
tseliotpitti: I assume mesa is not being installed for the tests right?08:32
cjwatsontjaalton: Your sssd/raring patch drops a linking fix (http://paste.ubuntu.com/5846034/).  Is that intentional?08:33
pittitseliot: no, unless the nvidia packages pull it in as a dependency08:33
pittitseliot: otherwise it's a minimal server install08:33
cjwatsontjaalton: If so I think it needs some reasoning for why it's a good idea to drop it in an SRU ...08:33
tseliotpitti: then it's bound to fail unless I add some directories in the debian/dirs files.08:33
tjaaltoncjwatson: hmm I'll check08:34
pittitseliot: so is there a missing dependency in the test case?08:34
pittitseliot: i. e. do these assume some Xorg-ish package to be installed now? (they didn't in the past)08:34
pittitseliot: I can add one easily08:34
tseliotpitti: either libgl1-mesa-glx or libgl1-mesa-glx-lts-quantal should fix it08:35
pittitseliot: ok, running locally with that added08:37
tseliotpitti: good, let me know how it goes08:37
tjaaltoncjwatson: good catch, must be some git fail by me.. reject and I'll reupload08:37
tjaaltonno wait08:37
* tjaalton runs a quick build-test08:38
tjaaltoncjwatson: yeah, reject. I'll sort out the local mystery of where it got lost and reupload08:41
tjaalton"a oneliner apparmor rule change doesn't need a build check, right?"08:42
pittidebdiff FTW08:42
infinitytjaalton: Probably doesn't, but every upload needs a debdiff. :)08:42
infinitypitti: Jinx.08:42
tjaaltonhmm yeah08:42
tjaaltonoh I see now08:43
tjaaltonbranched raring from a commit too early :)08:44
evis there some trick to convincing ubuntu touch to use the newly installed kernel, beyond remounting /system rw?08:44
cjwatsontjaalton: done08:44
evI've got a kernel from apw that I installed via dpkg, but uname -v is still reporting the build time of the previous kernel08:45
apwev, if it was my kernel running it would have a unique version string too08:46
apwev, did you only install the package08:46
apwie did you do anything after08:46
evapw: yeah, I just did dpkg -i on the three debs you gave me08:46
evand did a sudo reboot08:46
apwhmmm no idea in container flip world if that works or not, before container flip it is definatly not enough08:47
evapw: any idea where I prod the bootloader from on this?08:47
apwogra_, ^^ does flash-kernel grok container flip yet or are we abootimg'ing still08:47
evah, I remember that thing from the last time I toyed with all of this :)08:48
tjaaltoncjwatson: thanks, will upload again in a bit08:48
* ogra_ wonders why he writes instructions in announcements :P08:48
ogra_apw, see the flipped container mail08:48
ogra_(and then use flash-touch-kernel)08:49
ogra_(with path to zImage as arg)08:49
evI don't have an email that mentions flash-touch-kernel :), but fair enough08:52
pittitseliot: that seems to fix fglrx, but not the nvidia ones08:52
pittitseliot: expected?08:52
=== lilstevie_ is now known as lilstevie
tseliotpitti: err... let me check nvidia08:53
pittitseliot: I pushed that as f181e58e9cb8a20408:53
pittitseliot: oh, it's because nvidia-310 is now a transitional pacakge08:54
pittiand so is nvidia-313-updates08:54
tseliotpitti: correct08:54
pittitseliot: so I guess we want to update those to check 319 now?08:54
tseliotpitti: 319 and 319-updates, yes08:55
evwooo http://paste.ubuntu.com/5846078/08:57
evthanks apw and ogra_08:57
apwogra_, so you have somewhere to refer us to when we are being wallies ?08:58
tseliotpitti: BTW how do you run those tests in ubuntu-drivers-common?08:58
tseliotpitti: the ones in debian/tests/system08:58
=== gusch is now known as gusch|away
pittitseliot: you can just run them with sudo debian/tests/system, but I usually run them in a full VM with run-adt-test -sUS file://`pwd` ubuntu-drivers-common08:59
pitti(to test my local changes)08:59
tseliotah, nice09:00
tjaaltoncjwatson: ok fixed version up09:02
=== geser_ is now known as geser
=== jibel_ is now known as jibel
pittitseliot: success! thanks for the hints, uploading now09:13
tseliotpitti: excellent, thanks09:13
* pitti wants green dots again09:13
apwev, it would be good to know sooner rather than later if that test kerenl is any good, as i am considering an upload for grouper09:14
evapw: ^ see above. Works a treat09:14
apwev, awsome, i'll rack it and stack it then09:15
cjwatsontjaalton: thanks, accepted09:15
evapw: cheers09:18
ogra_apw, ev, i'll add a kernel/postinst.d script so installing packages will DTRT09:25
apwogra_, sounds good indeed09:29
evogra_, apw: fwiw the kernel packaging or something needs to remount /system rw since /lib/modules is a symlink to it09:35
ogra_ev, well, the whole disk  will be readonly soon09:49
evogra_: interesting. Why?09:50
ogra_ev, we will drop apt support and switch to image based upgrades09:50
ogra_(there will be a developer mode but it isnt clear yet what that will enable)09:50
evah, but surely we'll be write able to write to /var/log and friends?09:50
ogra_ev, security ... everything but the /data partition will be ro09:51
ogra_heh. indeed, the system will go on to function :)09:51
evas long as we arrange for /var/crash to be writeable, I'm happy09:51
ogra_/run and /var/foo will indeed be tmpfses09:51
evor whatever we set APPORT_REPORT_DIR to09:52
ogra_yeah, you might want the crashes persistent during the dev cycle, i guess using /data might be a good idea ... (we can then switch to a tmpfs after release)09:52
evI'm not convinced they need to persist for too long, but it might be worth making them survive a reboot. I'd need to talk to pitti about it, but an upstart inotify watch that removed both the .crash and .upload* when .uploaded is present09:55
evbut if it's going to make things difficult, we wont lose a ton by living on a tmpfs09:55
infinityHaving them survive a reboot is probably user-hostile on a shipping device anyway.09:55
infinityAssuming there's going to be some process that, at boot, tries to report it all and grinds my phone to a halt like apport does to my laptop.09:56
evyeah, was just trying to consider the case where the device crashes in a way that causes the user to reboot it09:56
pittiogra_, ev: yeah, we have some things which need to survive, such as suspend failure reports; the others are probably not all that interesting09:56
pitti(or in general kernel oopses)09:56
pittiwell, storing those in a persistent location doesn't imply that we necessarily have to send them all right after boot09:57
infinity(Tell me that whatever is reporting crashes on the phone isn't going to be the system-killing mess that the current state of affairs is?)09:57
infinityCause on an i7 laptop, booting with a dozen pending crash reports basically means an unusable system for half an hour.09:58
infinityPretty sure that's a non-starter on an A9 phone.09:58
evinfinity: so to some extent that's mitigated by not having a UI on top of this09:58
cjwatsonogra_: /var/foo> do you know just how much of /var?  It would be helpful to know for click09:58
evalso, we'll skip the (existing) hook paths09:58
evsince there's no interactive UI (though not ruling out server-side hooks)09:59
cjwatsonActually, tmpfses don't help me09:59
ogra_ev, you can write to /dev/kmsg .... android uses a ram console by default, that means crashes going to that device (or actual kernel oopses) will persist in /proc/last_kmsg over reboots09:59
ogra_cjwatson, well, i guess we define how much, stgraber designs this, so if you have specific needs make sure he knows09:59
evinfinity: I'd happily rewrite it in C, but it's been deemed not a good investment of my time. We might be able to convince it to run under pypy though.09:59
cjwatsonev: 'cos pypy works so well on ARM10:00
evI had not considered that :)10:00
cjwatson(Well, it might work, but it hasn't built in ages)10:00
infinityIt builds, with sufficient resources.  Calxeda will save us all.10:00
cjwatsonWhen it happens ...10:00
infinityStill have no idea how potentially awesome it is or isn't once it's built.10:00
cjwatsonI think any modules you need would need pypy-* packages too?10:01
cjwatsonNot quite sure how that stuff works10:01
infinityogra_: Note that last_kmsg only survives a warm reboot, not a hard-crash-and-battery-pull sort of situation.10:02
ogra_not a battery pull but up to now it survived all crashes i needed data for :)10:02
ogra_cjwatson, if a tmpfs isnt enough you need to use /data10:02
evinfinity, pitti, others: if you have further suggestions as to how we can make this a less intensive experience on the phone, I'm all ears. One option would be a more aggressive compression of the report data, either by compressing more fields or switching to something that gives a better ratio (for the increased decompression cpu burden on daisy.u.c.)10:03
infinitycjwatson: I assume click has a /var/lib/dpkg equivalent that it needs to write to?10:03
infinitycjwatson: Probably best to just bindmount that to data/clickdb or something.10:03
ogra_ev, more compression means more bttery draining and more CPU hogging10:03
cjwatsoninfinity: Yeah, just wanted to know what my parameters are, and it would be nice to avoid lots of package-specific bind-mounts10:04
ogra_if you have the diskspace i would go for extensive compression10:04
evogra_: okay, so then just compressing the core file as we do now is probably the way to go10:04
pittiev: more aggressive compression would probably be more CPU intensive? so that's a bandwidth/CPU tradeoff10:04
infinityev: Keeping it cheap on CPU is probably ideal.  Obviously, enormous reports over 3G data is also kinda crap, but hopefully they'll be smallish and infrequent...10:04
evwe wont send them over 3g, but yeah10:05
ogra_yeah, gzip with std options doesnt do much harm10:05
evwifi only. I don't want to get forwarded cell phone bills10:05
pittiev: but I guess if we really want to get a magnitude more performance out of this, we need to move from full core dumps and Python to something like minidumps and C/C++/vala..10:05
cjwatsonev: Hopefully it's a bit more fine-grained that that; some of us have reasonably adequate 3G limits10:05
infinityWe won't?  Android sends reports over 3G (it asks me if I want to, first, mind you, and they're also not huge cores)10:05
ogra_xz with highest compression rate definitely does ... i guess you even feel it on the UI10:05
cjwatson*than that10:05
evcjwatson: how do you make the distinction?10:06
cjwatsonev: ask10:06
cjwatsonev: system preference kind of thing10:06
evhttps://wiki.ubuntu.com/ErrorTracker#Privacy_settings for what it's worth10:06
pittiev: but with client-side dupe detection we hopefully won't actually have to send so many cores?10:06
evmpt: ^10:06
* ogra_ wouldnt allow reports via 3G ... period10:06
evpitti: correct10:06
infinityev: Android is littered with "use 3G for scary data" app options.  We could probably go one better and make it a global "just do it" option.10:06
cjwatsonev: I'd have expected this to be a system setting, not specific to errors10:06
pittiogra_: certainly not a bad approach to begin with -- send them when enabling wifi10:06
evwe only ask for a core if we haven't already retraced it or don't already have it in the pipeline to be retraed10:07
ogra_pitti, exactly ...10:07
cjwatsonAndroid's approach is pretty much right here IME10:07
cjwatsoninfinity: It has a general system-level setting too, doesn't it?10:07
infinitycjwatson: I'd argue Android's approach is a bit fragmented on the app level (I've had to tell several apps that it's okay to upload on 3G, had to tell VoIP apps that it's okay to make calls on 3G, etc... I'd love a system setting)10:07
ogra_cjwatson, androids approach ends up in a million of options ... i dont think thats good10:07
infinitycjwatson: If there's a system setting, that's new, which would explain all the apps also asking me. :P10:08
cjwatsonMaybe I'm imagining it10:08
infinity(So, we should get it right the first time)10:08
evpitti: minidumps would be pretty cool10:08
pittiev: still a question of how useful they are going to be for actually fixing the crashes..10:08
cjwatsonThere's things like Data usage -> ... -> Restrict background data10:09
pittiknowing in which function a crash happens doesn't tell you taht much10:09
evpitti: are we not able to just pair them with a symbol server and get a full stacktrace out?10:09
infinitycjwatson: Ahh, yeah, that's been there since 1.x10:09
cjwatsonAnyway, I thought I remembered seeing a spec for our 3G usage that included something plausibly system-level for this10:09
pittiev: no, minidumps don't have that information any more AFAIK; one really needs a core10:09
evah, rubbish10:09
cjwatsonAnd of course Android has the mobile data limit thing10:09
xnoxinfinity: i think mpt draw a setting for data, where all apps are listed and one can flick them on/off for 3G usage.10:10
xnoxmpt: shouldn't we have an upload service in addition to download service? u1, crash reports, files / photos.........10:11
pittiev: but again, hopefully with SAS we won't need to upload all that many cores..10:13
pittiev: perhaps we can dial down the aggressiveness of this for phones a bit, such as not requesting more cores until the first report (with matching SAS) finishes retracing and fails, and give up after three failures10:14
pittiev: not sure how agressively it collects cores right now, perhaps it already works that way?10:14
pittithat still leaves the local processing, of course10:15
mptxnox, on the contrary, I just now mailed ubuntu-devel-discuss@ saying I doubted it would be useful to have OS-level control  over which apps access the Internet.10:15
xnox /o\ mpt I only have 500MB data plan, I want everything on WiFi only. But I want an app automatically start using 3G, if it's in the foreground - meaning I want it to have internet access over the scarce 3G10:16
* xnox should consider forking out 5GBP a month for unlimited 3G internet.....10:17
mptI get 1 GB/month :-)10:17
xnoxmpt: not ubuntu-phone mailing list? https://launchpad.net/~ubuntu-phone10:17
mptxnox, I didn't decide where the discussion started10:18
=== oSoMoN_ is now known as oSoMoN
xnoxmpt: For me 0.5GB is fine, sitting at home/work on WiFi. But sometimes I am somewhere bored and decide to like pictures of all lolcats in my facebook newsfeed...... download a few games..... and it goes downhill from there.10:19
tjaaltonhow evil would it be to ship an identical file in two binaries and adding Replaces: "the other" to them?10:22
tjaaltonthis trying to match sssd packaging on fedora, where they can ship the same file on to packages and they won't conflict10:23
tjaaltonavoids creating a package which has just one file10:23
xnoxtjaalton: what's the file and why it's needed?10:24
tjaaltonit's a helper binary needed by ipa and ad backend10:25
xnoxtjaalton: instead of conflicts it could be an dpkg-alternative file, than both packages can be installed. And if the file is the same, it doesn't matter which one is "active" and it will be guaranteed to be available if either of the two packages are installed.10:25
xnoxtjaalton: would be nicer to have it in one place. Or can both packages be used without the other one installed?10:26
xnoxtjaalton: and can both be installed simultaniously and used as well? if yes, please don't make them conflict....10:27
tjaaltonthe backends got split into subpackages so you can only have what you need (ldap, krb5, ad, ipa)10:27
tjaaltonI didn't mean to make them conflict, but add Replaces10:27
cjwatsonidentical + Replaces> that's really very evil and is a timebomb for later developers.  Use a -common package or something.10:27
tjaaltonok, figured10:28
cjwatsonUsing alternatives is also pretty confusing.  I wouldn't recommend that.10:28
=== Guest95491 is now known as zumbi
infinitytjaalton: Mutual Replaces is more than just confusing, it's broken.  If you install A, then B, then remove B, the overlapping file disappears.10:40
tjaaltoninfinity: heh, ok.. didn't think of that10:40
infinitytjaalton: A -common, or alternatives, or a dpkg-divert all work fine, for varying levels of user and developer confusion around each option.10:42
tjaaltonsssd-ad-common is least confusing10:42
tjaaltonand really not much work either to "maintain"10:43
tjaaltonor pac-common10:44
evpitti: yeah, it should already work that way (sorry for the delay - we're moving Cassandra to prodstack today).10:49
pittiev: ooh!10:49
=== gusch|away is now known as gusch
ev:) exciting times10:51
pittidoko_: ah sorry, I didn't realize that postgresql-9.1 -2 (FTBFS fix) didn't autosync; I adjusted your tcl config change to work in Debian as well, and will upload now10:51
evTwelve 1 TB nodes to start with10:52
pitti11 TB! holy c***10:52
ev:D we've got a lot of data10:52
pittiev: do we really have that amount of data for errors, or is that "for futureproof"?10:52
pittierr, 12 TB, but whatever10:53
evpitti: we have 6 TB of actual data10:56
evwith a replication factor of two10:56
ev(we want to keep the node sizes down to about 1TB, since earlier versions of Cassandra deal better with 1TB or less)10:57
=== doko_ is now known as doko
evpitti: it's part of the reason why I'm really keen on getting Hadoop running soon after we finish the move to prodstack (being on prodstack makes it much easier, since we can spin up a secondary cluster for just hadoop analytics)10:58
pittiso we have more error data than archive size :)10:59
everrors.ubuntu.com will serve the common use case, but for real investigative work, having the whole dataset at your fingertips will be invaluable10:59
evlol, an interesting way to look at it, yeah10:59
evthe nodes themselves will have 2TB of disk space each11:00
evwe think we're the first people to use Ceph for this11:00
tunnelshadeNeed some help in packaging11:07
cjwatsonPlease ask your question directly, rather than asking to ask11:08
tunnelshadeI have to build a debian package which has to copy files and run postinst scripts. For this purpose I used debian/package.install. The install using deb was great. But when I tried to upgrade with the next version of .deb all the files previously copied are getting erased.11:11
cjwatsonMight be easiest if we could see the source package.11:11
cjwatsonAt least the debian/* part.11:12
tunnelshadehttps://anonfiles.com/file/6696ee30a49cde33f51c4d4bf14bcf81 <= If this can do11:15
cjwatsontunnelshade: Can you give an example path which is erased?11:16
tunnelshadeInitially during install the whole source gets copied to /opt11:17
tunnelshadeso when I tried an update, there is no source folder in /opt11:18
cjwatsonGiving exact paths would help.11:18
cjwatson(Bear in mind I'm unfamiliar with your package and am not planning to install it ...)11:18
cjwatsonNo matches for "/opt/package" in your debian/ directory.11:18
=== MacSlow is now known as MacSlow|lunch
tunnelshadeI didnt build it, I gave you the folder before building11:19
tunnelshadeone second11:19
cjwatsonGenerally speaking you should try to avoid your postinst fighting with the list of files shipped in your .deb11:19
cjwatsonSo any files listed by 'dpkg -c foo.deb' you should regard as read-only11:19
=== oSoMoN_ is now known as oSoMoN
cjwatsonMost problems of this kind are because the postinst is illicitly fiddling about with files shipped in the .deb11:20
tunnelshadeBut I am just using them for reading11:20
cjwatsonThen I'd need to see 'dpkg -c' output for the old and new versions, I think11:21
tunnelshadeAlmost same, with some new files11:21
cjwatsonTry cleaning everything out, installing the old version, then "dpkg --unpack owtf_newversion.deb", check whether the files are still there, "dpkg --configure owtf", check again11:22
cjwatsonThat will allow you to tell whether it's dpkg itself or your postinst that's removing the files11:22
tunnelshadeThe files are gone with --unpack itself11:24
cjwatsonWere they there before the --unpack?11:24
cjwatson*Which path*?11:25
cjwatsonExact copy and paste.11:25
cjwatson(Incidentally, sudo in a preinst makes no sense; the maintainer scripts always run as root.)11:25
tunnelshadethat is just a draft, first I get things working, I can cleanup11:26
cjwatsonYou mean that /opt/owtf itself is entirely absent?11:26
cjwatsonThen it must be your postinst's fault11:26
tunnelshade(Just to remind I am using install file inside debian folder for copying files)11:26
cjwatsonAssuming that those files are in owtf_oldversion.deb at all11:26
cjwatsonHow you got the files into the .deb is irrelevant11:27
tunnelshadeSo if I disable postinst you say that things should go fine11:27
cjwatsonThey're being unpacked and then apparently deleted; the only thing that runs that has the opportunity to delete them is your postinst11:27
cjwatsonWell, if I were you I would fix the postinst, not disable it11:27
tunnelshadeFixing means??? Not touching the files11:28
cjwatsonYou might like to execute bits of it step by step to see where exactly it's going wrong11:28
cjwatsonNot removing the files!11:28
cjwatsonI don't know exactly where it's doing that11:28
cjwatsonBecause it's calling out to external scripts I don't have11:28
=== slacker_1l is now known as slacker_nl
cjwatsonI can see that it's removing /opt/owtf/dictionaries/cms-explorer, which is almost certainly a bad idea11:28
cjwatsonBut not where it's removing all of /opt/owtf11:29
cjwatsonHowever, nothing else has the opportunity to do that ...11:29
tunnelshadeI am also blown by what is happening11:29
tunnelshadeFor information, what is the best place if I wish to run some scripts after installation and using the installed packages11:30
=== elmo_ is now known as elmo
cjwatsonThere's nothing fundamentally wrong with doing post-installation steps in the postinst (although in general the less maintainer script code you can get away with writing the better), but from what you've told me your current code would appear to be somehow responsible for the deletions you're complaining about, so start there.  It doesn't run in a particularly magic environment or anything; you can just try stepping ...11:32
cjwatson... through your commands from there as root and seeing where things get blown away.11:32
tunnelshadeI completely removed the postinst, but still the same11:33
tunnelshadeBy same I mean, the whole /opt/owtf got removed11:33
tunnelshadeAh, please take a look, I think the error is in my postrm11:34
cjwatsonAh!  Yes, indeed11:36
tunnelshaderemoving files for upgrade as well11:37
cjwatsonThat doesn't make a whole lot of sense.  Try to make it so that you only remove things created by the preinst/postinst.11:37
tunnelshadeOk, so I have to remove postrm from the oldversion package as well right11:38
tunnelshadeInorder to test11:38
cjwatsonpostrm bugs can be awkward to recover from, yes.11:38
=== funkyHat_ is now known as funkyHat
tunnelshadeThanks a lot for your time cjwatson11:43
cjwatsonno problem11:43
tunnelshadeMy problem is solved11:43
tunnelshadeCan you give me any suggestions other than above, to change in my package11:44
cjwatsonGenerally you should try to depend on packaged Python modules rather than doing a load of pip install calls.11:46
cjwatsonI'm afraid I don't have time for a full review though11:46
cjwatson(At least three urgent-ish things to do today of which I have started on about 0.5)11:47
tunnelshadeThe python packages are outdated in the repos11:47
tunnelshadeso I have to depend on pip11:47
cjwatsonOr package new versions11:47
tunnelshadeI am a cyber security guy, just wanted to package a tool I develop :(11:48
tunnelshadeSo I am not a debian guru11:48
=== _salem is now known as salem_
=== MacSlow|lunch is now known as MacSlow
=== Guest79110 is now known as JanC
=== JanC is now known as Guest3754
=== Guest3754 is now known as JanC
=== Guest51964 is now known as Tm_T
mdeslaurcjwatson: is there an example manifest file somewhere other than the file format document?14:19
=== Sweetsha1k is now known as Sweetshark
=== Guest28536 is now known as ahasenack
=== wedgwood_ is now known as wedgwood
=== rodarvus` is now known as rodarvus
A1ReconHas 802.11ac gone beyond draft?14:36
=== chiluk` is now known as chiluk
cjwatsonmdeslaur: there's one inside http://people.canonical.com/~cjwatson/tmp/com.ubuntu.apps.camera_2.9.1daily13.06.13_all.click - possibly not hugely informative though14:43
mdeslauroh, sweet, and actual click package! :)14:43
mdeslaurcjwatson: thanks :)14:43
cjwatsonpeople kept asking me for one so I cobbled something together.  I don't promise not to break it14:44
mdeslaurcjwatson: so, we don't seem to have a "display name" field in there...ie: "Camera"14:46
mdeslaurcjwatson: is that something we want?14:46
dholbachcan somebody please reject https://code.launchpad.net/~malizor/ubuntu/saucy/ubuntu-wallpapers/fix-for-1177260/+merge/171911?14:46
mdeslaurcjwatson: or is the "title" supposed to be that, but is a bad example in your click package?14:46
dholbachhey mvo, does lp:~dylanmccall/update-manager/dialogs-refactor look all right to you?14:47
cjwatsonmdeslaur:     "title": "Camera application",14:49
cjwatsonmdeslaur: isn't that a display name?14:50
cjwatsonmdeslaur: title is meant to correspond to the first line of Description:, basically14:50
mdeslaurcjwatson: ok, sounded like a short description to me14:50
cjwatsonmdeslaur: I think it would be OK to consider it as display-name14:50
cjwatsonIt's basically convention14:50
=== oSoMoN_ is now known as oSoMoN
Guest33546stgraber, hey, I haven't heard heard back from highvoltage yet, when he confirms which way we can do the call, I will kick it off15:02
Guest33546weird, this is jono15:02
* Guest33546 restart XChat15:02
stgraberjono_: I pinged him on IRC a few minutes ago but haven't heard back yet15:03
jono_stgraber, same here15:03
jono_stgraber, lets give him a few mins, and then if he doesn't respond maybe we can go ahead and I can talk to him later in a different call15:03
stgraberjono_: ok. I had a chat with him a couple days ago about our position wrt Mir, so at least our views should be pretty much aligned :)15:05
highvoltagejono_, stgraber: I' back15:05
highvoltage*I'm back, even15:05
stgraberhey highvoltage!15:05
jono_oh hey highvoltage :-)15:05
stgraberhighvoltage: can you do g+?15:05
highvoltage(ran a few minutes late with giving someone a lift)15:05
jono_highvoltage, np15:06
highvoltageyep, I'm logged in15:06
jono_highvoltage, stgraber cool, I will set it up now and send a link15:06
jono_highvoltage, stgraber https://plus.google.com/hangouts/_/e24720733bd142ef469692ef34939e0af9292a57?authuser=0&hl=en15:07
* highvoltage has not used hangouts in a while so might just have to configure a bit15:07
jono_highvoltage, no worries :-)15:08
dholbach@pilot out15:25
dholbach(more piloting on monday :))15:25
dholbachtsimpson, ^ do you know what happened with the bot?15:26
tsimpsondholbach: look like it died when freenode exploded, I'm bringing it back15:29
tsimpsonthere it is15:31
=== kk2 is now known as Kk2
=== Kk2 is now known as kk2
=== Guest14861 is now known as maxb
=== Guest85904 is now known as Lutin
=== achernya_ is now known as achernya
=== francisco is now known as Guest44759
=== Nisstyre-laptop is now known as Nisstyre
=== NCommand` is now known as NCommander
=== NCommander is now known as Guest96374
=== james_ is now known as Guest8292
=== pgraner` is now known as pgraner
=== Guest96374 is now known as NCommander
=== ppetraki_ is now known as ppetraki
=== salem_ is now known as _salem
=== Guest17995 is now known as charles
=== kk2 is now known as Kk2
=== Guest51174 is now known as elky

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