[07:07]  * tsdgeos waves the channel
[08:03] <Jessedhammu> hay can i change the position of unity launcher ,,>>??
[09:53] <tsdgeos> Cimi: https://code.launchpad.net/~cimi/unity8/infographics-august-merge/+merge/231344/comments/573362
[09:54] <Cimi> tsdgeos, I don't bother about this branch unless someone tells me "fix this, we want to merge infographics today"
[09:54] <tsdgeos> ok
[09:54] <tsdgeos> maybe put it as WIP then?
[09:54] <Cimi> tsdgeos, I lost the count on how many times I fixed conflicts and noboduy reviewed
[09:55] <Cimi> tsdgeos, I did infographics two months ago
[09:55] <tsdgeos> i don't even know what it is about
[09:55] <tsdgeos> but i guess we don't want it now in rtm
[09:55] <tsdgeos> or do we?
[09:55] <Cimi> tsdgeos, replace infographics with svg
[09:56] <tsdgeos> i guess i'll say it put it as WIP and bug saviq when he comes back? it's not feature critical, is it?
[09:57] <Cimi> pete-woods, do you know anything about schedule for infographics as svg?
[09:58] <pete-woods> Cimi: I haven't been told anything. I think it's up to us two to push it forward
[09:59] <pete-woods> Cimi: if we find a "quiet" week for u8, then maybe we should just push it through
[10:00] <Cimi> pete-woods, on your side, do you think it has feature parity with the current implementation?
[10:00] <Cimi> pete-woods, unity side, is just a frontend, we don't control things
[10:00] <pete-woods> tsdgeos: I did the translation support for the YouTube scope while you were away. wasn't sure if it was blocking you from doing the spanish translation
[10:00] <pete-woods> Cimi: I think maybe it misses the "no data" infographic
[10:01] <pete-woods> Cimi: but that's difficult to do from my end now, because of translations
[10:01] <Cimi> pete-woods, so pleas, add this
[10:51] <tsdgeos> pete-woods: cool tx
[11:08] <facundobatista> Holas
[11:18] <tsdgeos> dednick: what's the status of https://code.launchpad.net/~nick-dedekind/unity8/indicator-polishing/+merge/228700 ?
[11:18] <tsdgeos> do we want it in? need reviewing?
[11:19] <dednick> tsdgeos: Cimi is reviewing
[11:19] <tsdgeos> dednick: good stuff
[11:34] <anpok> hm is there a simple way to trigger a notifaction
[11:34] <anpok> apart of calling the phone
[11:34] <anpok> and adding a callendar entry with reminter :(
[11:34] <anpok> reminder even
[11:34] <mzanetti> anpok: lp:unity-notifications
[11:34] <mzanetti> anpok: examples directory
[11:35] <anpok> oh thx having a loo
[11:35] <anpok> k
[11:54] <mzanetti> dandrader: good morning
[11:54] <mzanetti> dandrader: hey, what's the ETA on the lost input fix?
[11:54] <dandrader> mzanetti, hi
[11:54] <mzanetti> landing team wants to know
[11:54] <mzanetti> seems its blocking promotions
[11:54] <dandrader> mzanetti, you mean that second patch?
[11:54] <mzanetti> dandrader: I mean a fix for the lost input :D
[11:55] <mzanetti> yes, the second patch.
[11:55] <mzanetti> people think of this as one issue though
[11:55] <mzanetti> so for the landing team the issue is not fixed.
[11:56] <dandrader> mzanetti, https://code.launchpad.net/~dandrader/qtmir/frozenApps-lp1295623 needs a reviewer
[11:56] <dandrader> mzanetti, wanna do it? :)
[11:59] <mzanetti> dandrader: ah, great. will look at it, yes
[11:59] <mzanetti> wow... this is a whole lot of code
[12:00] <dandrader> mzanetti, 90% of it is refactoring to make it possible to unit test MirSurfaceItem
[12:00] <dandrader> mzanetti,  5% is the test itself and 5% is the actual fix
[12:01] <mzanetti> yeah.. see that
[12:01] <dandrader> mzanetti, the commit message explains that mess
[12:03] <mzanetti> dandrader: shouldn't SessionInterface be in unity-api too (not asking you to do that now - just for my undertstanding)
[12:03] <mzanetti> ?
[12:03] <dandrader> mzanetti, yes, I even had a TODO comment in its header stating that
[12:04] <dandrader> mzanetti, but greyback_ wants to nuke it in the nor so far future
[12:04] <dandrader> s/nor/not
[12:04]  * dandrader looks for the doc
[12:04] <mzanetti> ah ok
[12:04] <mzanetti> no need to dig docs now
[12:04] <mzanetti> I just wanted to know if my understanding is ok
[12:05] <dandrader> mzanetti, ah you opened it already. it's item #2
[12:05]  * mzanetti totally forgot about that tab being open :D
[12:06] <dandrader> mzanetti, and that nice diagram https://docs.google.com/a/canonical.com/drawings/d/1KFn03gFW1SXYOQn1l9hPCwFx_a8EAJA2AMc1hygqeEo/edit
[12:06] <mzanetti> ack. makes sens to me
[12:12] <mzanetti> dandrader: hmm... you sure you're not breaking multitouch with this? (I haven't tried it yet - but just reading through it you don't seem to care about touch ID in validateAndDeliverTouchEvent)
[12:15] <dandrader> mzanetti, when a QEvent::TouchBegin comes, it means a whole new touch sequence is starting. Which implies that previous to that there should be no active touch points
[12:15] <mzanetti> ah ok
[12:16] <mzanetti> dandrader: what event is there when there's just an additional finger put down?
[12:16] <dandrader> QEvent::TouchUpdate
[12:16] <mzanetti> ah
[12:16] <mzanetti> thanks
[12:17] <dandrader> a touch sequence starts when the first touch point is pressed and ends once the last remaining touch point is released
[12:17] <mzanetti> ok... I would have expected to get a TouchBegin for each finger
[12:18] <dandrader> mzanetti,  that you get from QTouchPoint::touchPoints()::state() or QTouchPoint::touchPointStates()
[12:18] <mzanetti> got it
[12:19] <mzanetti> dandrader: yeah... your branch looks good. compiling it on the device to test
[12:42] <darklight_> Is anyone looking at https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1305438? It's been broken one way or another since ~ 12.10
[12:54] <pstolowski> tsdgeos, ping
[12:56] <Guest60061> Cimi: tsdgeos ...i thot i did get access for the team, lemme check if i need to do one more approval step of something
[12:56] <tsdgeos> pstolowski: hi
[12:58] <pstolowski> tsdgeos, hey. i'm looking at an enhancement requested by thostr (and he discussed it with saviq) to delay invalidating of results model till first result of new search arrives; instead extsting results should be "disabled" (blurred, dimmed, whatever). do you know about that idea?
[12:58] <tsdgeos> pstolowski: nope
[12:58] <pstolowski> tsdgeos, (and they shouldn't be clickable when new search is in progress)
[12:59] <pstolowski> tsdgeos, ok.. so i've first part more less ready, but wanted to check with you about making current results dimmed
[13:00] <kgunn> greyback_: can you review ? https://code.launchpad.net/~dandrader/qtmir/frozenApps-lp1295623/+merge/234393
[13:00] <pstolowski> tsdgeos, would it make sense for you if it's a single property of Scope?
[13:00] <dandrader> kgunn, greyback_, mzanetti is on it
[13:00] <greyback_> kgunn: I believe mzanetti was looking at it
[13:00] <kgunn> ta
[13:00] <pstolowski> tsdgeos, (all results are either disabled or not for given scope)
[13:00] <dandrader> mzanetti, you should probably claim it
[13:01] <tsdgeos> pstolowski: i guess that's fine yes
[13:03] <pstolowski> tsdgeos, how busy are you currently? do you have time to hack something soonish (and I'd test/play with it and my plugin branch)?
[13:03] <tsdgeos> pstolowski: just came from a week out, settling in, not terribly busy
[13:04] <tsdgeos> i guess i could take it
[13:05] <pstolowski> tsdgeos, awesome; how about a bool property of Scope named 'resultsEnabled'?
[13:06] <tsdgeos> hmmm
[13:06] <tsdgeos> actually do we need a new property?
[13:06] <tsdgeos> don't we have the "searching" thing already? can use that?
[13:07] <tsdgeos> pstolowski: ↑
[13:07] <pstolowski> tsdgeos, we have searchInProgress getter, but not exposed via property
[13:07] <pstolowski> tsdgeos, the only qproperty I can see is for 'favorite' flag
[13:07] <tsdgeos> hmmm
[13:07] <tsdgeos> and what does trigger the orange busy bar?
[13:07]  * tsdgeos checks
[13:08] <pstolowski> tsdgeos, but yeah, resultsEnabled would = !searchInProgress afaict
[13:08] <tsdgeos> scope.searchInProgress
[13:09] <tsdgeos> seems exposed to me
[13:09] <tsdgeos> at least we use it :D
[13:09] <pstolowski> tsdgeos, ahhh, bloody scope interface defined somewhere else :/
[13:11] <pstolowski> tsdgeos, yeah, you're right, we do handle it. in that case no need for new property (unless we find it's limiting us for some reason; but should be ok)
[13:11] <tsdgeos> oki
[13:11] <tsdgeos> pstolowski: so what should i do then?
[13:11] <tsdgeos> make the thing blurred + disabled while searching?
[13:12] <pstolowski> tsdgeos, probably making them dimmed will be better. but i'm wondering if tying it to search-in-progress is a right thing, cause this will make them not-clickable until search finished
[13:12] <pstolowski> * finishes
[13:13] <tsdgeos> well you said
[13:13] <tsdgeos>  resultsEnabled would = !searchInProgress afaict
[13:13] <tsdgeos> :D
[13:13] <pstolowski> tsdgeos, yeah... but now as I think of it more.. what we want is to disable *old* results, but when new results start arriving, they should be clickable / enabled
[13:14] <pstolowski> tsdgeos, so, I think we need a new property after all :/
[13:15] <tsdgeos> ok
[13:17] <pstolowski> tsdgeos, i'll be back in 1h
[13:28] <kgunn> dednick_: just checking, i know there's no prereq marked, but i can land lp:~nick-dedekind/ubuntu-settings-components/indicator-polishing w/o landing
[13:29] <kgunn> lp:~nick-dedekind/unity8/indicator-polishing
[13:29] <kgunn> ?
[13:29] <Cimi> kgunn, yes
[13:30] <Cimi> kgunn, but he needs an approve first :)
[13:33] <kgunn> Cimi: yes sir...
[13:33] <kgunn> Cimi: was just noticing it seemed ready
[13:33] <kgunn> Cimi: is there someone who we usually get to top approve on u-s-s ?
[13:33] <Cimi> kgunn, it is quite ready yes, but it is affected from some changes to the sdk, I would like to wait tomorrow/wednesday
[13:34] <Cimi> kgunn, this is settings components, not system settings
[13:34] <kgunn> Cimi: cool, i'll keep it on the "still cookin'" pile
[13:34] <kgunn> Cimi: you're right, sorry, mis-spoke
[13:34] <Cimi> kgunn, basically, wait sdk to revert few things, then if nothing breaks approbe
[13:35] <kgunn> thanks Cimi, you know which mp's we're eyeballing from sdk to land first ?
[13:35] <Cimi> kgunn, otherwise we might just want to fine-tune some small details
[13:36] <kgunn> dednick_: and i thot lp:~nick-dedekind/unity8/indicator-polishing was landing last week ?...what happened ?
[13:36] <Cimi> kgunn, there are many of zsombi https://code.launchpad.net/ubuntu-ui-toolkit
[13:36] <kgunn> Cimi: ok
[13:36] <Cimi> kgunn, regarding listitems and divider
[13:36] <Cimi> kgunn, it happened me not approving
[13:37] <kgunn> Cimi: were you just being cruel ?
[13:37] <kgunn> :)
[13:37] <Cimi> kgunn, last week there was a bug around slow initialization of the indicators
[13:37] <Cimi> kgunn, you were receiving a message, you pulled down the indicators... blank page for 1-2 seconds
[13:37] <kgunn> eegads
[13:37] <Cimi> kgunn, nick fixed friday that and is fine
[13:38] <kgunn> Cimi: ok...well, there will also be another train
[13:38] <kgunn> to land on
[13:38] <Cimi> kgunn, however I dislike some UX changes daniela did (but she left)
[13:38] <Cimi> kgunn, design also has a redesign for indicators
[13:38] <kgunn> but she's back today right
[13:38] <kgunn> Cimi: yeah...but that branch fixes a poop-ton of bugs
[13:39] <Cimi> kgunn, so we might want to land the settings components part, and incorporate those design changes (that will fix my concern)
[13:39] <Cimi> kgunn, I know, but we have policy of no regressions
[13:39] <kgunn> Cimi: kk
[13:39] <mzanetti> re
[13:39] <mzanetti> kgunn: yes, on it
[13:39] <kgunn> Cimi: what regression if the slow-init was addressed ?
[13:41] <dednick_> Cimi: there's no regression in the the u8 branch
[13:41] <dednick_> Cimi: it's a different design
[13:43] <Cimi> dednick_, I think is a regression
[13:43] <Cimi> dednick_, not your fault
[13:43] <kgunn> Cimi: isn't danelia back today?
[13:43] <dednick_> Cimi: i think she's left?
[13:43] <kgunn> dednick_: you mean forever ?
[13:43] <Cimi> i think so
[13:44] <dednick_> kgunn: yeah
[13:44] <Cimi> kgunn, I can approve nick branch, is a good improvement
[13:44] <Cimi> kgunn, but I am sure we will receive complain for the new indicator design
[13:45] <Cimi> the header bar loses the chevron for example, you don't know how to switch indicators
[13:45] <Cimi> once you pulled down
[13:45] <kgunn> Cimi: i see, at that point...that monkey is on design
[13:46] <dednick_> it's going to change again in short order
[13:46] <Cimi> kgunn, at the same time, vesa and ben were working on a redesign... and now we have that
[13:46] <dandrader> greyback_, Here is QOpenGLDebugLogger::startLogging crashing on me again... http://paste.ubuntu.com/8350547/
[13:46] <dandrader> greyback_, commented it out
[13:46] <kgunn> Cimi: "working on redesign" doesn't sound "done"
[13:46] <greyback_> dandrader: weird
[13:46] <dandrader> greyback_, that was on krillin
[13:47] <Cimi> kgunn, they user tested this morning
[13:47] <Cimi> kgunn, and trust me, is miles better
[13:47] <greyback_> dandrader: looks like a null pointer..
[13:48] <kgunn> Cimi: sorry, user tested nick's branch that's up?
[13:49] <kgunn> or ....new design we have yet to implement ?
[13:51] <Cimi> kgunn, users tested the prototype
[13:51] <Cimi> of the new indicatords
[13:51] <Cimi> not nick branch
[13:52] <kgunn> got it
[13:52] <Cimi> kgunn, I don't think any designer ever saw nick branch working
[13:52] <Cimi> kgunn, because daniela left
[13:52] <Cimi> kgunn, and other designers were working on the redesign...
[13:54] <dednick_> Cimi: they approved my changes. it's been there for ages.
[13:54] <Cimi> dednick_, who approved?
[13:57] <dednick_> Cimi: ben, daniela, esti . can't remember who all
[13:57] <dednick_> Cimi, kgunn: https://docs.google.com/a/canonical.com/document/d/1KC40suUs13gajIlE1Ms6PJYoIPx_AjlF4ae6bvtNjNc/edit
[13:57] <Cimi> dednick_, esti is not UX, daniela left...
[13:57] <dednick_> removing the chevron was a direct request
[13:59] <Cimi> anyway, regardless we have UX approvals (only daniela), we have to change the design anyway, why not merging both?
[14:00] <Cimi> instead of getting comments publicly, google plus/whatever "hey indicator redesign!" etc etc... then change it all over again in a couple of days
[14:42] <mzanetti> Cimi: indeed much better with this option. thanks
[14:42] <Cimi> yw
[14:42] <mzanetti> Cimi: now do you know a cure for Telepathy hiding all the time?
[14:43] <Cimi> not using it :)
[14:43] <Cimi> probably similar solution
[14:43] <pstolowski> tsdgeos, hey, so ok for new attribute 'resultsEnabled'? do you know if it needs to be added to ScopesInterface (I don't know what was the history of extracting this interface into separate project)
[14:43] <mzanetti> doesn't have such an option I think
[14:43] <mzanetti> Cimi: don't you use any IM?
[14:43] <tsdgeos> pstolowski: everything needs to be in  the interface
[14:43] <tsdgeos> pstolowski: so mocks for example can use the interface
[14:43] <tsdgeos> unity8 mocks
[14:44] <pstolowski> tsdgeos, ah, ok
[14:44] <Cimi> mzanetti, I am antisocial, I don't chat apart IRC with colleagues :D
[14:50] <mzanetti> mhm...
[15:11]  * greyback_ needs reboot
[15:32] <mzanetti> dandrader: do you know what happened to the touch cancellation for the edges?
[15:32] <mzanetti> list time I heard from it, it was "soon after qtcomp landed"
[15:33] <dandrader> mzanetti, right
[15:33] <dandrader> mzanetti, waiting for it bubble up the prioritized queue of TODO work
[15:34] <dandrader> kgunn, ^
[15:34] <mzanetti> dandrader: ah... I think this should be critical... people start working around it: https://bugs.launchpad.net/ubuntu-ux/+bug/1368702
[15:34] <mzanetti> kgunn: ^
[15:34] <mzanetti> I think the only reason why this isn't critical for us, is that we don't have a bug number for it
[15:35] <tsdgeos> +1
[15:53] <tsdgeos> marcustomlinson: please fix the tests in your branch
[15:58] <marcustomlinson> tsdgeos: k
[16:34] <dednick> Cimi: looks like i you can't put a colorized image into an UbuntuShape.
[16:34] <dednick> Cimi: so can't do anything about it :/
[16:34] <Cimi> dednick, you can use shaderEffectSource
[16:35] <Cimi> is fixable, just, dammit!
[16:35] <Cimi> maybe there is a better fix
[16:35] <Cimi> like fixing the icons of the notifications
[16:39] <dednick> Cimi: hm? SharedEffectSource renders a texture.
[16:39] <dednick> *into a
[16:39] <Cimi> dednick, you can wrap a texture (an icon) inside a shape
[16:40] <Cimi> dednick, we use this in the shell already somewhere
[17:03]  * Cimi away, catch you a bit later
[17:19] <dednick> Cimi: that change is in usc now.
[19:10] <dandrader> greyback_, update the splashscreen unity8 mp
[19:10] <dandrader> updated


[16:56] <svendre> hello, I am interested in testing the 19.10 release.  My question is, if I install the OS (not liveboot) on top of ZFS, how difficult would it be to change it to a newer, official release in the future while leaving the initial ZFS filesystem infrastructure in place?  I realize I could have problems with a beta and the filesystem it creates, but my understanding is that the filesystem itself is mature, and the beta is
[16:56] <svendre> mostly about the installer process..
[16:57] <svendre> I'm pretty excited about this release, despite the licensing stuff I've heard, I think ZFS (on root) is a huge milestone for linux
[17:08] <tomreyn> svendre: the plan (and an implementation which is in the works) is to add experimental (!) ZFS support to the 19.10 desktop installer. if future ubuntu versions will also support ZFS you'll be able to upgrade to those. i am unsure whether predictions on whether this will be the case are currently possible.
[17:14] <svendre> tomreyn: I guess I was talking about if I download the daily image now (before the final release of 19.10 or newer), when the final release comes out, can the "beta" releases or whatever you call them be upgraded to the final releases?
[17:15] <tomreyn> svendre: while none of this is supported, yes, you can usually upgrade pre-release installations to release versions just fine by installing updates.
[17:16] <svendre> tomreyn: thanks, good enough for me.  I'll give it a try and report anything buggy if I encounter it.
[17:16] <tomreyn> svendre: if installation defaults would change in the meantime, though (such as, e.g., which parameters file systems are created with) you'd loose this change, though.
[17:17] <tomreyn> svendre: this said, i checked two days agao and back then is wasn't easily possible to test the daily installers with ZFS
[17:18] <svendre> tomreyn: ok.  I'm a pretty good person to test it out, I guess it'll be exciting.
[17:18] <svendre> I was just playing with SmartOS.. oh man.. good ideas there, but really, typing in a huge UUID of an image name in low rez kind of turned me off.
[17:20] <tomreyn> svendre: you're basically waiting for https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity/+merge/372690
[22:56] <misternumberone> hi i am on 19.10 kernel 5.3 mesa 19.3 and I recently switched from NVIDIA to AMD. I use multihead and I need a single X screen across all monitors, so that fullscreen applications are never told the physical resolution, only the virtual resolution. This is achieved with Xinerama and nvidiaXineramaInfo setting when using the nvidia proprietary driver. However, using xrandr --setmonitor for the same result on AMD and the open
[22:56] <misternumberone> source mesa/amdgpu/RadeonSI driver like the arch wiki advises does not obscure the physical resolution from fullscreen applications. Is there a way to create a single X screen from multiple physical displays using amdgpu?
[22:58] <misternumberone> I am using 19.10 because my graphics card (radeon rx 5700 xt) is not supported by any kernel older than 5.3. The kernel documentation states that creating virtual displays for randr forwarding should be supported, but when I add that kernel parameter it does not add any virtual displays to xrandr. https://dri.freedesktop.org/docs/drm/gpu/amdgpu.html
[23:07] <tomreyn> bionic-proposed (18.04 LTS) has linux-image-generic-hwe-18.04-edge | <IP_ADDRESS>.83
[23:13] <misternumberone> tomreyn:  thanks for the suggestion but it appears that the newest mesa for bionic is 19.0.8 and support for my graphics card was added in 19.2
[23:14] <tomreyn> oh ok. then, unless oibaf or padoka also offer this mesa version *and* a 5.3+ kernel image, you're doing exactly the right thing. ;)
[23:24] <tomreyn> do you want me to have a look at and second guess whether you configured amdgpu's virtual_display correctly?
[23:24] <tomreyn> i'm not sure this is actually what you want / need, though
[23:34] <tomreyn> misternumberone: maybe this would be an alternative: https://www.displaylink.com/products/find?cat=3&res=3840x2160&num=2&vid_dp=1
[23:34] <tomreyn> though i don't know how performant those are, never used their products. but they're said to usually work fine on ubuntu.
[23:40] <misternumberone> tomreyn:  sure here is my grub cfg also i am reading about that product https://paste.linux.community/view/raw/01d8d296 and im a little busy ill respond soon
[23:41] <tomreyn> that's unrelated, but in case you don't know it, and since you seem to be a power user, you may be interested in this as well: https://www.mesa3d.org/envvars.html
[23:42] <tomreyn> note there's also #amdgpu here on freenode. this is mostly used by driver developers, but maybe they'd help there, too.
[23:44] <tomreyn> the user named Venemo has actually answered support questions there in the past.
[23:51] <tomreyn> about virtual_display, have you tried     amdgpu.virtual_display=0000:01:00.0,1    instead? i assume you have verified that this address points to the correct device by using    lspci -s 0000:01:00.0,1    ?
[23:52] <tomreyn> (i'm suggesting to add the extra 0)
[23:53] <tomreyn> i assume what virtual_display really does is to just add more (virtual) 'screens' though, which can then be configured, too.
[23:59] <misternumberone> "lspci -s 0000:01:00.0" yields "01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 1478 (rev c1)", if I add the ",1" it yields "lspci: -s: Invalid function number". I can add the 0 you did and try that just in case, even though lspci doesn't seem to need the 0


[21:03] <teward> Pici: Mikaela: after the current meeting in #ubuntu-meeting is done, it looks like meetingology has failed with topic resetting after the hard-kill of the server team meeting
[21:03] <teward> it may need fixed later
[21:48] <N3X15> Anyone happen to have a backup or archive of the Encyclopedia development wiki for supybot/ubottu?  It's throwing 404s.
[21:51] <k1l> you mean this?
[21:51] <k1l> !bot
[21:52] <Fuchs> also the new freenode website is up since today, if there are any links to it in ubottu, they probably need updating.
[22:00] <dax> Fuchs: oh boy. i'll handle that tonight i guess
[22:00] <dax> shouldn't be too hard to find them all
[22:03] <Fuchs> not all content is up yet
[22:03] <Fuchs> but some is
[22:06] <dax> N3X15: https://web.archive.org/web/20150331065404/http://ubottu.com/devel/wiki/Main_Page seems to have everything. nobody was editing much, so it shouldn't be too out of date
[22:06] <dax> N3X15: i'd hazard a guess that the wiki went AWOL last time ubottu.com changed hosts, but not 100% sure
[22:07] <N3X15> Thanks, dax
[22:20] <Unit193> Yeah, that's when it disappeared.
[22:36] <dax> wow, you're not joking about "not all content". i searched the repo for "cloak"


[06:00] <Jose__> hi can I create private cloud storage and computing with #juju
[06:04] <Jose__> ?
[06:06] <Jose__> @markthoms ho
[18:28] <mbruzek> hello marcoceppi I have a few questions
[18:28] <marcoceppi> mbruzek: go for it
[18:29] <mbruzek> I am reading that Amulet can be installed via pip.  How does one add something so pip can find it?
[18:34] <marcoceppi> mbruzek: if you're on Ubuntu, just apt-get install amulet
[18:34] <mbruzek> Yeah I saw that
[18:34] <marcoceppi> mbruzek: as for pip, you just `sudo pip install amulet`
[18:34] <mbruzek> I am just a curious person and have used pip before, but don't know how you get your code in the pip repos
[18:35] <marcoceppi> pip is a package management tool for python, so you install pip with the pip package; then just pip install <package>
[18:35] <marcoceppi> you'll need sudo for amulet as it modifies system paths
[18:35] <marcoceppi> pip amulet and apt-get amulet will conflict with each other though
[18:36] <mbruzek> But how does pip know where to find amulet?
[18:36] <marcoceppi> mbruzek: PostScript
[18:36] <marcoceppi> oop
[18:36] <marcoceppi> mbruzek: https://pypi.python.org/pypi
[18:36] <marcoceppi> huh, maybe I didn't put it on pip yet
[18:36] <marcoceppi> pypi*
[18:37] <marcoceppi> oops, only charm-tools and charmworldlib are on pypi. So you can't install amulet with pip yet
[18:38] <mbruzek> Ok I see the Python Package index.  Thanks marcoceppi
[18:38] <marcoceppi> np o/
[18:50] <jaywink> hi. Anyone tips on how to modify image-metadata-url of bootstrapped machine? I bootstrapped to an openstack cloud with the image metadata hosted locally but of course the bootstrap instance cannot connect to my computer so I cannot deploy anything :)
[18:55] <mbruzek> hi jaywink I am guessing that your computer is not on the same subnet as your OpenStack instance?
[18:57] <jaywink> mbruzek, no :P I can upload the image metadata somewhere but the bootstrap was kind of tricky due to this cloud being in beta so wondering if I can modify the config on the bootstrap instance to use another metadata url
[18:57] <marcoceppi> jaywink: you can't modify it once bootstrapped, iirc; you'll need to destroy, put the image-medata somewhere accessible, then rebootstrap
[18:57] <jaywink> marcoceppi, ok :/ tnx
[18:57]  * mbruzek defers to marcoceppi
[18:58] <marcoceppi> jaywink: I'd check with one of the devs tomorrow, maybe fwereade would know, but they're usually not on during the weekends
[18:58] <marcoceppi> from what I understand it's not a trivial process
[18:58] <jaywink> btw what has happened to http://streams.canonical.com? it has gone empty
[19:00] <jaywink> marcoceppi, maybe I will raise I bug. I can think of a use case in a production environment if the metadata needs to be moved or is moved for some reason - recreating everything just to change the metadata url doesn't sound ideal :)
[19:01] <marcoceppi> jaywink: I'm not sure about the streams URL. The metadata is either stored in the object store or in the mongodb database. If it's the former, you should be able to download, overwrite it, then upload it again. If the latter it's going to be a bit more complex
[19:02] <marcoceppi> jaywink: check the bucket you defined as control-bucket if any of the files have the metadata information in there
[19:02] <jaywink> ok tnx will check
[19:15] <jaywink> marcoceppi, nah only tools in the objectstore afaict
[19:15] <marcoceppi> jaywink: hum, it's probably in the mongodb database then
[19:15] <marcoceppi> *unforunately*
[19:17] <jaywink> no prob, will raise a bug. thanks!
[19:41] <popey> I am running juju 0.7+bzr628+bzr633~precise1 on 12.04, and i have done a deploy of cs:~popey/precise/yacy-5 and expose, but it doesn't seem to get an IP
[19:42] <popey> where's the best place to start debugging?
[19:42] <popey> 2014-01-12 14:18:00,948 Machine:0: unit.deploy INFO: Started service unit yacy/1
[19:42] <popey> 2014-01-12 19:42:52,581 INFO Service 'yacy' was already exposed.
[19:42] <popey> 2014-01-12 19:42:52,584 INFO 'expose' command finished successfully
[19:43] <popey>         public-address: null
[19:43] <popey> ☹
[21:14] <marcoceppi> popey step 1) don't use 0.7
[21:15] <marcoceppi> popey: latest recommended stable is 1.16.5 from ppa:juju/stable
[21:15] <marcoceppi> if you don't want to add a PPA, consider using the cloud-tools archive (since you're on 12.04)
[21:20] <popey> alan@homeserver:/etc/apt/sources.list.d$ cat juju-pkgs-precise.list
[21:20] <popey> deb http://ppa.launchpad.net/juju/pkgs/ubuntu precise main
[21:20] <popey> thats my current ppa in use
[21:20]  * popey adds that ppa
[21:22]  * popey destroys and starts again
[21:26] <popey> bah!
[21:26] <popey> juju now needs mongo
[21:26] <popey> why didn't it install that as a dependency rather than echo some lines telling me how to use apt. how odd
[21:28] <popey> http://paste.ubuntu.com/6741064/
[21:28] <popey> bah
[21:37]  * popey regenerates config
[21:41] <popey> alan@homeserver:~$ juju debug-log
[21:41] <popey> Permission denied (publickey).
[21:41] <popey> ERROR exit status 255
[21:41] <popey> bah!
[21:41] <popey> alan@homeserver:~$ juju expose
[21:41] <popey> error: no service name specified
[21:42] <popey> inconsistency detected! (all other errors are "ERROR", but that one is "error:"
[21:49] <popey> \o/ got it working, thanks marcoceppi
[22:14] <marcoceppi> popey: debug-log doesn't work on local provider
[22:15] <marcoceppi> https://juju.ubuntu.com/docs/config-LXC.html#debug-log
[22:15] <marcoceppi> also, the errors should all be lower case, the ERROR exit status is an error message from SSH just being passed through to the client
[22:16] <marcoceppi> popey: to fix the mongodb issue, you should just install juju-local (which should be the package it tells you you need instead of saying "oh just install mongodb"
[22:16]  * marcoceppi wanders offline again