[00:18] <slangasek> Riddell: so with soprano, do you think I should just upload it, or do you prefer that I wait for your testing on Monday?
[00:26] <Riddell> slangasek: what's the change?
[00:26] <cjwatson> the one I asked about in the release meeting ...
[00:27] <slangasek> Riddell: yep, that one - linking soprano-daemon against libvirtodbc0 directly instead of using libiodbc2 as a driver manager
[00:28] <Riddell> slangasek: how about if I test tomorrow?
[00:28] <slangasek> Riddell: you can test whenever you'd like, I was just checking if you actually thought it was better for me to wait :)
[00:29] <Riddell> slangasek: soprano is a bit unreliable at the best of times so I think I'd prefer to check it
[00:30] <slangasek> ok
[00:50] <SpamapS> woot.. always nice fixing 5xxxxx bugs :) .. though 4xxxxx are even sweeter.. ;)
[08:25] <scientes_> how much doesn't work if i install systemd?
[08:25] <scientes_> i.e. how much stuff uses upstart-native?
[08:25] <scientes_> and _doesn't_ also shit sysvinit scripts
[10:43] <shadeslayer> ScottK: I think telepathy-qt .... I'm not sure, I recall someone talking about telepathy-qt and farstream a couple of weeks ago
[10:43]  * shadeslayer doesn't quite remember ...
[10:50] <Laney> cd
[12:55] <dupondje> Some small question. When a module is copied to the initramfs, whats the order it will be loaded @ boot?
[14:01] <ximion> hi! You might want to take a look at my recent upload of the "packagekit" package at Debian...
[14:01] <ximion> the new upstream version might be wanted in Ubuntu too, and I applied some patches to it...
[14:01] <ximion> where one of them fixes a crash in PK.
[14:02] <ximion> so you might want to take the patches at least, to apply them on Ubuntu too :)
[14:11] <aseem> Hi is this the channel to discuss about Ubuntu's project ideas for GSOc2012 ?
[14:20] <Chipzz> aseem: I'm not 100% sure, but my guess would be yes (unless there's a more specific channel, but I'm not aware of any)
[14:21] <Chipzz> aseem: you should be aware though that it's weekend and that a lot of developers are not present
[14:22] <aseem> Chipzz, HI! There is #ubuntu-gsoc channel, but in the wiki #ubuntu-devel was mentioned so I got confused.
[17:59] <Darxus> How do I get bug 831768 added to the top of the list of known issues on https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes ?  I would not have upgraded last night if I had known about it.  (Admitedly, I failed to read that document first, but that's where the warning should be.)
[18:04] <awe> Darxus, I'd ping Kate.Stewart, as she's the Ubuntu Release manager ( and also was the last person to edit the page )
[18:04] <awe> https://wiki.ubuntu.com/ReleaseTeam
[18:04] <Darxus> Thanks.
[18:05] <awe> np
[18:54] <infinity> Darxus: If that's cause you issues, you could just disable multiarch again.
[18:54] <infinity> Darxus: "I wouldn't have upgraded" seems a bit harsh, when it's just one small config file.
[18:55] <Darxus> infinity: My understanding is that there will be 32 bit software I'll need to install at some point that I won't be able to because of this.
[18:56] <Darxus> I don't claim to fully understand the situation.
[18:56] <infinity> Darxus: That's only true is you already had 32-bit software installed...
[18:56] <infinity> s/is/if/
[18:57] <Darxus> infinity: And just disabling multiarch didn't work.  I had to re-enable multi-arch, apt-get install qdbus, and then disable multiarch again.  As I commented to that bug.
[18:57] <infinity> We have no intention of cutting out 64-bit software and forcing 32-bit stuff on you, just not shipping duplicates (like wine32) on both architectures.
[18:57] <Darxus> infinity: So.. I probably didn't have 32 bit software installed on natty, so I probably won't care about it on oneric+?
[18:58] <infinity> Yeah, if you're running a pure 64-bit system, we're not going to take that option away.
[18:58] <infinity> Did you upgrade with aptitude, or just run into problems with aptitude after upgrading with do-release-upgrade or similar?
[18:59] <infinity> Darxus: Anyhow, I'm not arguing that "aptitude and multiarch don't entirely get long" shouldn't have been in the Oneiric release notes, and feel free to ping skaet about that.
[18:59] <Darxus> Awesome, thanks.
[18:59] <infinity> skaet: ^
[19:00] <Darxus> I followed the directions for upgrading, so used update manager, then aptitude wouldn't work after.
[19:00] <infinity> Darxus: Just that there are any number of workarounds (the two most obvious being "disable multiarch" or "don't use aptitude")
[19:00] <skaet> infinity,  Darxus pinged me about it earlier.   I'll add it on monday.
[19:00] <infinity> skaet: Alright. ;)
[19:00] <Darxus> Damn, didn't even give me a chance to type that.
[19:01] <infinity> Darxus: We'd like to get this all fixed for precise, but I will admit that we have limited resources, and aptitude's not the top of too many priority lists. :/
[19:01]  * infinity wonders idly how well dselect plays with multiarch.
[19:01] <Darxus> Hah.
[19:01] <Darxus> Well, what about disabling multiarch by default on 64 bit systems in precise?
[19:02] <infinity> Not going to happen.
[19:03] <infinity> For users of update-manager, software-center, or just hardcore apt-get users, (or python-apt, libapt in general, etc), multiarch is just fine as a default.
[19:03] <infinity> aptitude's resolver has been known-broken for years, it's just that this hilights it much more than ever before. :/
[19:04] <infinity> I'd sooner port tasksel to libapt and demote aptitude to universe than disable multiarch.
[19:04] <infinity> But that's just me.
[19:04] <infinity> (And, honestly, that should probably be done regardless, even if we do find the time to fix aptitude)
[19:05] <Darxus> My entire reason for using aptitude is a belief that if I install a package, and its dependencies are automatically installed, then I uninstall that package, only aptitude will handle removing the no-longer needed dependencies.  How true is that?
[19:05] <infinity> apt-get does that.
[19:05] <Darxus> Automatically?
[19:05] <Darxus> I just saw something about apt-get autoremove...
[19:05] <infinity> Try it.  Install something with deps, remove that something, then note the list of "no longer needed packages", which it will happily remove with "apt-get autoremove"
[19:06] <Darxus> Why isn't that just done with apt-get remove?
[19:06] <infinity> Automatic autoremoval, apt won't do.  That was a conscious decision.
[19:06] <Darxus> Hmm, okay.
[19:06] <infinity> You may have come to rely on one of those deps.
[19:06] <Darxus> Sure.
[19:06] <infinity> autoremove gives you the option to at least think about it briefly.
[19:07] <infinity> (And you can mark something as "manually installed" just with "apt-get install <already-installed-package>"
[19:07] <infinity> Bu)
[19:07] <infinity> Err.
[19:07] <infinity> Typing hard.
[19:07] <Darxus> What about stuff installed via the gui package management software?  Will those dependencies also be removed by apt-get autoremove?  I've avoided using them for the same reason.
[19:07] <infinity> All the GUI tools we support (software-center, update-manager, and synaptic) use libapt (sometimes via python-apt), and so follow the same semantics.
[19:08] <infinity> So, only the software you manually "select" is marked as manually installed, the rest is transitively installed, and candidate for autoremoval if no longer needed.
[19:09] <Darxus> Awesome, that all sounds good enough for me to stop using aptitude.  I really appreciate that.  I'll probably mention it on that bug thread in case others are in the same position.
[19:09] <infinity> Oh hey, we don't support synaptic anymore.  Look at that.  But the above is still true. :P
[19:09] <infinity> Anyhow, the apt resolver is so much saner than aptitude's at this point that I don't see the point in aptitude usage for most people.
[19:10] <Darxus> "autoremove" is too long to type :P
[19:10] <infinity> aptitude and dselect both did a really good job of presenting higher level package relations, but I suspect that's less needed now that resolvers actually kinda work.
[19:10] <infinity> (I know I used to not be able to do anything without dselect holding my hand, but that was a decade ago)
[19:10] <Darxus> Heh.
[19:11] <Darxus> My memories of dselect are so distant at this point.
[19:11] <Darxus> At the time it seemed magical compared to redhat, which I had just switched from.
[19:11] <infinity> It was magical.
[19:11] <Darxus> Finding a package to test autoremove with is hard :P
[19:11] <infinity> And pre-apt, it was incredibly magical.
[19:12] <Darxus> Ah, here we go, clisp.
[19:13] <Darxus> I just accidentally verified that dependencies installed via aptitude also get removed via apt-get autoremove.
[19:13] <Darxus> This is going to be a tough habit to break.
[19:13] <infinity> Handy.
[19:13] <infinity> I think someone switched aptitude to use the apt cache for that a few years ago.
[19:13] <infinity> Or, it sounds vaguely familiar.
[19:13] <infinity> Which seems to be backed up by your evidence.
[19:14] <slangasek> yes, ~4 years ago
[19:14] <slangasek> when apt started having a notion of autoinstalled packages
[19:14] <Darxus> Nice.
[19:14] <infinity> slangasek: So, uhm.  Yeah.  Speaking of aptitude.  I wibbled on above about how it might be a sane idea to make tasksel stop depending on it.
[19:15] <infinity> slangasek: I suspect that, other than emotional attachment, that's the only reason it's in main.
[19:15] <slangasek> instead of fixing aptitude to support multiarch?
[19:15] <infinity> slangasek: Oh, both should happen, IMO.
[19:15] <slangasek> it is the only TUI we have for package management
[19:15] <slangasek> (not counting dselect, which I don't :)
[19:15] <infinity> slangasek: aptitude should stop being broken, but I see no reason why tasksel needs aptitude anymore.  apt has understood tasks for years.
[19:15] <slangasek> I think the tasksel dep remains reasonable
[19:16] <slangasek> no, aptitude is there so that users can drill down into tasks further from the installer and make more fine-grained selections interactively
[19:16] <slangasek> if it were just there for tasksel to tell apt "install tasks", I'd agree, but I don't think that's the rationale
[19:16] <infinity> Fair enough.
[19:16] <infinity> (And I would count dselect if we shipped it...)
[19:17] <infinity> I always thought the dependency was literally just for the "install this task" functionality.
[19:17] <infinity> Which apt didn't have at the time tasksel was written.
[19:17] <slangasek> as for fixing aptitude for multiarch, there are some comments on the bug from someone who seems to now be involved in aptitude upstream development... we should probably pull some patches for precise
[19:17]  * ScottK hands infinity cupt for even more 'fun'.
[19:17] <infinity> (And, indeed, not for many years after)
[19:18] <slangasek> yes, because everything's better in perl
[19:19] <infinity> Well, it's a perl frontend to a C++ library.
[19:20] <slangasek> The cupt maintainer is actively hostile to multiarch.  That suits me just fine, because I'm hostile towards reimplementing the wheel by casting it out of jello.
[19:20] <infinity> I'm still not sure why people feel the need to rewrite apt-get/libapt every 3 years, though.
[19:20] <ScottK> We also have libqapt now.
[19:21] <infinity> ScottK: Which isn't just a tiny shim on libapt? :/
[19:21] <ScottK> infinity: Yes.  It's a tiny shim to get a sane API from the author's POV for other development.
[19:21] <infinity> ScottK: Okay, yeah, looks more like a bindings interface, I'm okay with that.
[19:22] <ScottK> It is a lot like that.
[19:23]  * slangasek nods
[19:23] <infinity> There's a lot of value in making developers of Language/Toolkit X comfortable with using your library.
[19:23] <infinity> And Qt devs definitely seem to live in a world where if things don't look just like Qt, they die a little inside.
[19:25] <infinity> (Although, wrapping a C++ library in different-looking C++ just to make it cosmetically more appealing is a bit entertaining)
[19:28] <ScottK> libqapt was done by one of our developers as part of his drive to get an apt/dpkg native GUI package manager for Kubuntu.  It's in Debian now too.
[19:31] <Daviey> slangasek: Have you ever tried to dig into tasks deeper using aptitude, within d-i?
[19:34] <Darxus> Now I need to decid if I want to re-enable multiarch.
[19:34] <Darxus> I guess I'll leave it off until I need something that won't otherwise work.
[19:36] <Chipzz> infinity: does anyone even still use dselect?
[19:36] <Chipzz> I never used or even tried it. and frankly I only have a vague notion what it is/does :)
[19:36] <Darxus> Wait, how the hell did qdbus:i386 get installed on my system by update-manager?
[19:37] <Darxus> There's a 64 bit version, and that should've been installed instead, right?
[19:37] <infinity> It certainly should have been.  Are you sure update-manager was the culprit?
[19:38] <infinity> Chipzz: Some people still do.  I don't use either aptitude or dselect since apt's resolver is now good enough for me.
[19:38] <infinity> Chipzz: But I always preferred dselect to aptitude before that.
[19:39] <Darxus> infinity: Not certain, but how else could it have been installed?  The entire problem with aptitude was it choking on that package, and when I unleased apt-get on it, it switched it to the 64 bit version.
[19:39]  * Chipzz also an apt-get user
[19:39] <Chipzz> never really saw the need for aptitude and especially the dependencies it drags it
[19:39] <Chipzz> esp on a server
[19:39] <Chipzz> *in
[19:41] <infinity> Darxus: Not entirely sure how update-manager (via libapt) could mess that up, except in the case of version skew.  And since you were upgrading to oneiric, there would have been no chance of that.
[19:41] <Chipzz> ironically I have used apt-get dselect-upgrade for several years after I discovered it :P
[19:42] <Darxus> infinity: Is there anything else I could've done to cause it?  Could an aptitude dist-upgrade have done it?
[19:43] <infinity> Chipzz: Well, dselect-upgrade is only interesting if you also manipulate the status database by hand (or with dselect or dpkg --set-selections)
[19:43] <infinity> Chipzz: Though, yeah, it's wildly handy to do batch "dpkg --set-selections" operations, followed by apt-get dselect-upgrade to make sure a proper resolver is checking your work. :)
[19:43] <Chipzz> infinity: that, and dselect-upgrades also drags in recommends iirc
[19:43] <Chipzz> or is it suggests? I always forget
[19:44] <infinity> Darxus: aptitude perhaps could have broken it, yeah.  But I'm the wrong person to ask.  I know that aptitude is "very broken" with multiarch, just not in what sense.
[19:44] <Chipzz> infinity: I recall dsu being the only way (that I knew of) to install recommends for quite a while
[20:00] <Darxus> Wow.  Pulse audio volume control now goes over 100%.  That makes me so happy!
[20:01] <penguin42> you can turn it up to 11 ?
[20:43] <slangasek> Daviey: aptitude within d-i> not in a long time, why?
[20:44] <Daviey> slangasek: I just wondered if it was still a valid use.
[20:44] <Daviey> It's not something i hear of.
[20:45] <slangasek> it's certainly something that could be revisited
[20:52] <bkerensa> slangasek: I'm running into this when trying to edit a changelog "but this directory name does not match the package name according to theregex  PACKAGE(-.+)?."
[20:52] <slangasek> what exactly are you doing?
[20:53] <bkerensa> slangasek: dch -i  just trying to list my changes
[20:53] <bkerensa> slangasek: you were the last person to work on this package from what I can see in the changelog
[20:53] <slangasek> you're running 'dch -i' from within the package directory?
[20:53] <bkerensa> slangasek: from source dir yes
[20:53] <slangasek> what's the full error message?
[20:54] <slangasek> (I've never seen this error from dch in my life, but maybe the full output will tell me what's happening :)
[20:55] <bkerensa> slangasek: It seems to be a case of user error
[20:55] <bkerensa> :)
[20:55] <bkerensa> I was in package/src when I ran dch
[20:55] <bkerensa> when I moved up one level it worked as expected
[20:55] <slangasek> ah yes
[20:55] <bkerensa> The package still seems a bit odd though
[20:56] <bkerensa> for some reason the package name is "precise" even though it should be something else?
[20:59] <bkerensa> https://code.launchpad.net/~bkerensa/ubuntu/precise/activity-log-manager/fix-for-943066/+merge/96896
[21:00] <bkerensa> the package was activity-log-manager but when it came down the source dir was named "precise"
[22:12] <Daviey> bkerensa: if you bzr branch lp:~ubuntu-branches/ubuntu/precise/PACKAGENAME/precise , it will make a precise directory
[22:12] <Daviey> if you, bzr branch lp:ubuntu/PACKAGENAME , it'll make one with the package name
[22:21] <happyface> anyone else getting lots of screen flickering in b1?
[22:27] <bkerensa> Daviey: Ahh :)
[23:55] <ScottK> Need more memory: g++ -Wl,--as-needed -Wl,--version-script,/build/buildd/qtwebkit-source-2.2.1/Source/symbols.filter -fuse-ld=gold -fuse-ld=gold -Wl,--no-undefined -fuse-ld=gold -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -Wl,-soname,libQtWebKit.so.4 -o libQtWebKit.so.4.9.0 obj/release/MathMLNames.o obj/release/MathMLElementFactory.o obj/release/SVGNames.o obj/release/SVGElementFactory.o obj/release/JSSVGElementWrapperFactory.o
[23:55] <ScottK> obj/release/XLinkNames.o obj/release/CSSPropertyNames.o obj/release/CSSValueKeywords.o obj/release/JSCounter.o obj/release/JSCSSCharsetRule.o obj/release/JSCSSFontFaceRule.o obj/release/JSCSSImportRule.o obj/release/JSCSSMediaRule.o obj/release/JSCSSPageRule.o obj/release/JSCSSPrimitiveValue.o obj/release/JSCSSRule.o obj/release/JSCSSRuleList.o obj/release/JSCSSStyleDeclaration.o obj/release/JSCSSStyleRule.o obj/release/JSCSSStyleSheet.o
[23:55] <ScottK> obj/release/JSCSSValue.o obj/release/JSCSSValueList.o obj/release/JSMediaList.o obj/release/JSMediaQueryList.o obj/release/JSRect.o obj/release/JSRGBColor.o obj/release/JSStyleMedia.o obj/release/JSStyleSheet.o obj/release/JSStyleSheetList.o obj/release/JSWebKitCSSKeyframeRule.o obj/release/JSWebKitCSSKeyframesRule.o obj/release/JSWebKitCSSMatrix.o obj/release/JSWebKitCSSTransformValue.o obj/release/JSAttr.o obj/release/JSBeforeLoadEvent.o
[23:55] <ScottK> obj/release/JSBeforeProcessEvent.o obj/release/JSCharacterData.o obj/release/JSClientRect.o obj/release/JSClientRectList.o obj/release/JSClipboard.o obj/release/JSCDATASection.o obj/release/JSComment.o obj/release/JSCompositionEvent.o obj/release/JSCustomEvent.o obj/release/JSDataTransferItem.o obj/release/JSDataTransferItems.o obj/release/JSDeviceMotionEvent.o obj/release/JSDeviceOrientationEvent.o obj/release/JSDocumentFragment.o
[23:55] <ScottK> obj/release/JSDocument.o obj/release/JSDocumentType.o obj/release/JSDOMCoreException.o obj/release/JSDOMImplementation.o obj/release/JSDOMStringList.o obj/release/JSDOMStringMap.o obj/release/JSElement.o obj/release/JSEntity.o obj/release/JSEntityReference.o obj/release/JSErrorEvent.o obj/release/JSEvent.o obj/release/JSEventException.o obj/release/JSHashChangeEvent.o obj/release/JSKeyboardEvent.o obj/release/JSMouseEvent.o
[23:55] <ScottK> obj/release/JSMessageChannel.o obj/release/JSMessageEvent.o obj/release/JSMessagePort.o obj/release/JSMutationEvent.o obj/release/JSNamedNodeMap.o obj/release/JSNode.o obj/release/JSNodeFilter.o obj/release/JSNodeIterator.o obj/release/JSNodeList.o obj/release/JSNotation.o obj/release/JSOverflowEvent.o obj/release/JSPageTransitionEvent.o obj/release/JSPopStateEvent.o obj/release/JSProcessingInstruction.o obj/release/JSProgressEvent.o
[23:55] <ScottK> obj/release/JSRangeException.o obj/release/JSRange.o obj/release/JSStringCallback.o obj/release/JSText.o obj/release/JSTextEvent.o obj/release/JSTouch.o obj/release/JSTouchEvent.o obj/release/JSTouchList.o obj/release/JSTreeWalker.o obj/release/JSUIEvent.o obj/release/JSWebKitAnimationEvent.o obj/release/JSWebKitTransitionEvent.o obj/release/JSWheelEvent.o obj/release/JSBlob.o obj/release/JSDirectoryEntry.o obj/release/JSDirectoryEntrySync.o
[23:56] <ScottK> obj/release/JSDirectoryReader.o obj/release/JSDirectoryReaderSync.o obj/release/JSDOMFileSystem.o obj/release/JSDOMFileSystemSync.o obj/release/JSEntriesCallback.o obj/release/JSEntry.o obj/release/JSEntryArray.o obj/release/JSEntryArraySync.o obj/release/JSEntryCallback.o obj/release/JSEntrySync.o obj/release/JSErrorCallback.o obj/release/JSFile.o obj/release/JSFileCallback.o obj/release/JSFileEntry.o obj/release/JSFileEntrySync.o
[23:56] <ScottK> obj/release/JSFileError.o obj/release/JSFileException.o obj/release/JSFileList.o obj/release/JSFileReader.o obj/release/JSFileReaderSync.o obj/release/JSFileSystemCallback.o obj/release/JSFileWriter.o obj/release/JSFileWriterCallback.o obj/release/JSWebKitFlags.o obj/release/JSMetadata.o obj/release/JSMetadataCallback.o obj/release/JSWebKitBlobBuilder.o obj/release/JSArrayBufferView.o obj/release/JSArrayBuffer.o obj/release/JSDataView.o
[23:56] <ScottK> obj/release/JSInt8Array.o obj/release/JSFloat32Array.o obj/release/JSCanvasGradient.o obj/release/JSInt32Array.o obj/release/JSCanvasPattern.o obj/release/JSCanvasRenderingContext.o obj/release/JSCanvasRenderingContext2D.o obj/release/JSOESStandardDerivatives.o obj/release/JSOESTextureFloat.o obj/release/JSOESVertexArrayObject.o obj/release/JSWebGLActiveInfo.o obj/release/JSWebGLBuffer.o obj/release/JSWebGLContextAttributes.o
[23:56] <ScottK> obj/release/JSWebGLFramebuffer.o obj/release/JSWebGLProgram.o obj/release/JSWebGLRenderbuffer.o obj/release/JSWebGLRenderingContext.o obj/release/JSWebGLShader.o obj/release/JSInt16Array.o obj/release/JSWebGLTexture.o obj/release/JSWebGLUniformLocation.o obj/release/JSWebGLVertexArrayObjectOES.o obj/release/JSWebKitLoseContext.o obj/release/JSUint8Array.o obj/release/JSUint32Array.o obj/release/JSUint16Array.o obj/release/JSDOMFormData.o
[23:56] <ScottK> obj/release/JSDOMSettableTokenList.o obj/release/JSDOMTokenList.o obj/release/JSDOMURL.o obj/release/JSHTMLAllCollection.o obj/release/JSHTMLAudioElement.o obj/release/JSHTMLAnchorElement.o obj/release/JSHTMLAppletElement.o obj/release/JSHTMLAreaElement.o obj/release/JSHTMLBaseElement.o obj/release/JSHTMLBaseFontElement.o obj/release/JSHTMLBlockquoteElement.o obj/release/JSHTMLBodyElement.o obj/release/JSHTMLBRElement.o
[23:56] <ScottK> obj/release/JSHTMLButtonElement.o obj/release/JSHTMLCanvasElement.o obj/release/JSHTMLCollection.o obj/release/JSHTMLDataListElement.o obj/release/JSHTMLDetailsElement.o obj/release/JSHTMLDirectoryElement.o obj/release/JSHTMLDivElement.o obj/release/JSHTMLDListElement.o obj/release/JSHTMLDocument.o obj/release/JSHTMLElement.o obj/release/JSHTMLEmbedElement.o obj/release/JSHTMLFieldSetElement.o obj/release/JSHTMLFontElement.o
[23:56] <ScottK> obj/release/JSHTMLFormElement.o obj/release/JSHTMLFrameElement.o obj/release/JSHTMLFrameSetElement.o obj/release/JSHTMLHeadElement.o obj/release/JSHTMLHeadingElement.o obj/release/JSHTMLHRElement.o obj/release/JSHTMLHtmlElement.o obj/release/JSHTMLIFrameElement.o obj/release/JSHTMLImageElement.o obj/release/JSHTMLInputElement.o obj/release/JSHTMLIsIndexElement.o obj/release/JSHTMLKeygenElement.o obj/release/JSHTMLLabelElement.o
[23:56] <ScottK> obj/release/JSHTMLLegendElement.o obj/release/JSHTMLLIElement.o obj/release/JSHTMLLinkElement.o obj/release/JSHTMLMapElement.o obj/release/JSHTMLMarqueeElement.o obj/release/JSHTMLMediaElement.o obj/release/JSHTMLMenuElement.o obj/release/JSHTMLMetaElement.o obj/release/JSHTMLMeterElement.o obj/release/JSHTMLModElement.o obj/release/JSHTMLObjectElement.o obj/release/JSHTMLOListElement.o obj/release/JSHTMLOptGroupElement.o
[23:56] <ScottK> obj/release/JSHTMLOptionElement.o obj/release/JSHTMLOptionsCollection.o obj/release/JSHTMLOutputElement.o obj/release/JSHTMLParagraphElement.o obj/release/JSHTMLParamElement.o obj/release/JSHTMLPreElement.o obj/release/JSHTMLProgressElement.o obj/release/JSHTMLQuoteElement.o obj/release/JSHTMLScriptElement.o obj/release/JSHTMLSelectElement.o obj/release/JSHTMLSourceElement.o obj/release/JSHTMLStyleElement.o obj/release/JSHTMLTableCaptionElement.
[23:56] <ScottK> o obj/release/JSHTMLTableCellElement.o obj/release/JSHTMLTableColElement.o obj/release/JSHTMLTableElement.o obj/release/JSHTMLTableRowElement.o obj/release/JSHTMLTableSectionElement.o obj/release/JSHTMLTextAreaElement.o obj/release/JSHTMLTitleElement.o obj/release/JSHTMLTrackElement.o obj/release/JSHTMLUListElement.o obj/release/JSHTMLVideoElement.o obj/release/JSImageData.o obj/release/JSMediaError.o obj/release/JSTextMetrics.o
[23:56] <ScottK> obj/release/JSTimeRanges.o obj/release/JSValidityState.o obj/release/JSVoidCallback.o obj/release/JSInjectedScriptHost.o obj/release/JSInspectorFrontendHost.o obj/release/JSJavaScriptCallFrame.o obj/release/JSScriptProfile.o obj/release/JSScriptProfileNode.o obj/release/JSDOMApplicationCache.o obj/release/JSNotification.o obj/release/JSNotificationCenter.o obj/release/JSBarInfo.o obj/release/JSConsole.o obj/release/JSCoordinates.o
[23:56] <ScottK> obj/release/JSCrypto.o obj/release/JSDOMSelection.o obj/release/JSDOMWindow.o obj/release/JSEventSource.o obj/release/JSGeolocation.o obj/release/JSGeoposition.o obj/release/JSHistory.o obj/release/JSLocation.o obj/release/JSMemoryInfo.o obj/release/JSNavigator.o obj/release/JSNavigatorUserMediaError.o obj/release/JSNavigatorUserMediaErrorCallback.o obj/release/JSNavigatorUserMediaSuccessCallback.o obj/release/JSPerformance.o
[23:56] <ScottK> obj/release/JSPerformanceNavigation.o obj/release/JSPerformanceTiming.o obj/release/JSPositionError.o obj/release/JSScreen.o obj/release/JSSpeechInputEvent.o obj/release/JSSpeechInputResult.o obj/release/JSSpeechInputResultList.o obj/release/JSWebKitAnimation.o obj/release/JSWebKitAnimationList.o obj/release/JSWebKitPoint.o obj/release/JSWorkerNavigator.o obj/release/JSDOMPlugin.o obj/release/JSDOMMimeType.o obj/release/JSDOMPluginArray.o
[23:56] <ScottK> obj/release/JSDOMMimeTypeArray.o obj/release/JSDatabase.o obj/release/JSDatabaseCallback.o obj/release/JSDatabaseSync.o obj/release/JSIDBAny.o obj/release/JSIDBCursor.o obj/release/JSIDBDatabaseError.o obj/release/JSIDBDatabaseException.o obj/release/JSIDBDatabase.o obj/release/JSIDBFactory.o obj/release/JSIDBIndex.o obj/release/JSIDBKey.o obj/release/JSIDBKeyRange.o obj/release/JSIDBObjectStore.o obj/release/JSIDBRequest.o
[23:56] <ScottK> obj/release/JSIDBTransaction.o obj/release/JSStorage.o obj/release/JSStorageEvent.o obj/release/JSStorageInfo.o obj/release/JSStorageInfoErrorCallback.o obj/release/JSStorageInfoUsageCallback.o obj/release/JSSQLError.o obj/release/JSSQLException.o obj/release/JSSQLResultSet.o obj/release/JSSQLResultSetRowList.o obj/release/JSSQLStatementCallback.o obj/release/JSSQLStatementErrorCallback.o obj/release/JSSQLTransaction.o
[23:56] <ScottK> obj/release/JSSQLTransactionCallback.o obj/release/JSSQLTransactionErrorCallback.o obj/release/JSSQLTransactionSync.o obj/release/JSSQLTransactionSyncCallback.o obj/release/JSSVGZoomEvent.o obj/release/JSSVGAElement.o obj/release/JSSVGAltGlyphElement.o obj/release/JSSVGAngle.o obj/release/JSSVGAnimateColorElement.o obj/release/JSSVGAnimatedAngle.o obj/release/JSSVGAnimatedBoolean.o obj/release/JSSVGAnimatedEnumeration.o
[23:56] <ScottK> obj/release/JSSVGAnimatedInteger.o obj/release/JSSVGAnimatedLength.o obj/release/JSSVGAnimatedLengthList.o obj/release/JSSVGAnimatedNumber.o obj/release/JSSVGAnimatedNumberList.o obj/release/JSSVGAnimatedPreserveAspectRatio.o obj/release/JSSVGAnimatedRect.o obj/release/JSSVGAnimatedString.o obj/release/JSSVGAnimatedTransformList.o obj/release/JSSVGAnimateElement.o obj/release/JSSVGAnimateTransformElement.o obj/release/JSSVGAnimationElement.o
[23:56] <ScottK> obj/release/JSSVGCircleElement.o obj/release/JSSVGClipPathElement.o obj/release/JSSVGColor.o obj/release/JSSVGComponentTransferFunctionElement.o obj/release/JSSVGCursorElement.o obj/release/JSSVGDefsElement.o obj/release/JSSVGDescElement.o obj/release/JSSVGDocument.o obj/release/JSSVGElement.o obj/release/JSSVGElementInstance.o obj/release/JSSVGElementInstanceList.o obj/release/JSSVGEllipseElement.o obj/release/JSSVGException.o
[23:56] <ScottK> obj/release/JSSVGFEBlendElement.o obj/release/JSSVGFEColorMatrixElement.o obj/release/JSSVGFEComponentTransferElement.o obj/release/JSSVGFECompositeElement.o obj/release/JSSVGFEConvolveMatrixElement.o obj/release/JSSVGFEDiffuseLightingElement.o obj/release/JSSVGFEDisplacementMapElement.o obj/release/JSSVGFEDistantLightElement.o obj/release/JSSVGFEDropShadowElement.o obj/release/JSSVGFEFloodElement.o obj/release/JSSVGFEFuncAElement.o
[23:56] <ScottK> obj/release/JSSVGFEFuncBElement.o obj/release/JSSVGFEFuncGElement.o obj/release/JSSVGFEFuncRElement.o obj/release/JSSVGFEGaussianBlurElement.o obj/release/JSSVGFEImageElement.o obj/release/JSSVGFEMergeElement.o obj/release/JSSVGFEMergeNodeElement.o obj/release/JSSVGFEMorphologyElement.o obj/release/JSSVGFEOffsetElement.o obj/release/JSSVGFEPointLightElement.o obj/release/JSSVGFESpecularLightingElement.o obj/release/JSSVGFESpotLightElement.o
[23:56] <ScottK> obj/release/JSSVGFETileElement.o obj/release/JSSVGFETurbulenceElement.o obj/release/JSSVGFilterElement.o obj/release/JSSVGFontElement.o obj/release/JSSVGFontFaceElement.o obj/release/JSSVGFontFaceFormatElement.o obj/release/JSSVGFontFaceNameElement.o obj/release/JSSVGFontFaceSrcElement.o obj/release/JSSVGFontFaceUriElement.o obj/release/JSSVGForeignObjectElement.o obj/release/JSSVGGElement.o obj/release/JSSVGGlyphElement.o
[23:56] <ScottK> obj/release/JSSVGGradientElement.o obj/release/JSSVGHKernElement.o obj/release/JSSVGImageElement.o obj/release/JSSVGLength.o obj/release/JSSVGLengthList.o obj/release/JSSVGLinearGradientElement.o obj/release/JSSVGLineElement.o obj/release/JSSVGMarkerElement.o obj/release/JSSVGMaskElement.o obj/release/JSSVGMatrix.o obj/release/JSSVGMetadataElement.o obj/release/JSSVGMissingGlyphElement.o obj/release/JSSVGNumber.o obj/release/JSSVGNumberList.o
[23:56] <ScottK> obj/release/JSSVGPaint.o obj/release/JSSVGPathElement.o obj/release/JSSVGPathSegArcAbs.o obj/release/JSSVGPathSegArcRel.o obj/release/JSSVGPathSegClosePath.o obj/release/JSSVGPathSegCurvetoCubicAbs.o obj/release/JSSVGPathSegCurvetoCubicRel.o obj/release/JSSVGPathSegCurvetoCubicSmoothAbs.o obj/release/JSSVGPathSegCurvetoCubicSmoothRel.o obj/release/JSSVGPathSegCurvetoQuadraticAbs.o obj/release/JSSVGPathSegCurvetoQuadraticRel.o
[23:56] <ScottK> obj/release/JSSVGPathSegCurvetoQuadraticSmoothAbs.o obj/release/JSSVGPathSegCurvetoQuadraticSmoothRel.o obj/release/JSSVGPathSeg.o obj/release/JSSVGPathSegLinetoAbs.o obj/release/JSSVGPathSegLinetoHorizontalAbs.o obj/release/JSSVGPathSegLinetoHorizontalRel.o obj/release/JSSVGPathSegLinetoRel.o obj/release/JSSVGPathSegLinetoVerticalAbs.o obj/release/JSSVGPathSegLinetoVerticalRel.o obj/release/JSSVGPathSegList.o obj/release/JSSVGPathSegMovetoAbs.o
[23:56] <ScottK>  obj/release/JSSVGPathSegMovetoRel.o obj/release/JSSVGPatternElement.o obj/release/JSSVGPoint.o obj/release/JSSVGPointList.o obj/release/JSSVGPolygonElement.o obj/release/JSSVGPolylineElement.o obj/release/JSSVGPreserveAspectRatio.o obj/release/JSSVGRadialGradientElement.o obj/release/JSSVGRectElement.o obj/release/JSSVGRect.o obj/release/JSSVGRenderingIntent.o obj/release/JSSVGScriptElement.o obj/release/JSSVGSetElement.o
[23:56] <ScottK> obj/release/JSSVGStopElement.o obj/release/JSSVGStringList.o obj/release/JSSVGStyleElement.o obj/release/JSSVGSVGElement.o obj/release/JSSVGSwitchElement.o obj/release/JSSVGSymbolElement.o obj/release/JSSVGTextContentElement.o obj/release/JSSVGTextElement.o obj/release/JSSVGTextPathElement.o obj/release/JSSVGTextPositioningElement.o obj/release/JSSVGTitleElement.o obj/release/JSSVGTransform.o obj/release/JSSVGTransformList.o
[23:56] <ScottK> obj/release/JSSVGTRefElement.o obj/release/JSSVGTSpanElement.o obj/release/JSSVGUnitTypes.o obj/release/JSSVGUseElement.o obj/release/JSSVGViewElement.o obj/release/JSSVGVKernElement.o obj/release/JSInternals.o obj/release/JSAudioBuffer.o obj/release/JSAudioBufferSourceNode.o obj/release/JSAudioChannelMerger.o obj/release/JSAudioChannelSplitter.o obj/release/JSAudioContext.o obj/release/JSAudioDestinationNode.o obj/release/JSAudioGain.o
[23:57] <ScottK> obj/release/JSAudioGainNode.o obj/release/JSAudioListener.o obj/release/JSAudioNode.o obj/release/JSAudioPannerNode.o obj/release/JSAudioParam.o obj/release/JSAudioProcessingEvent.o obj/release/JSAudioSourceNode.o obj/release/JSConvolverNode.o obj/release/JSDelayNode.o obj/release/JSHighPass2FilterNode.o obj/release/JSJavaScriptAudioNode.o obj/release/JSLowPass2FilterNode.o obj/release/JSRealtimeAnalyserNode.o obj/release/JSWebSocket.o
[23:57] <ScottK> obj/release/JSAbstractWorker.o obj/release/JSDedicatedWorkerContext.o obj/release/JSSharedWorker.o obj/release/JSSharedWorkerContext.o obj/release/JSWorker.o obj/release/JSWorkerContext.o obj/release/JSWorkerLocation.o obj/release/JSDOMParser.o obj/release/JSXMLHttpRequest.o obj/release/JSXMLHttpRequestException.o obj/release/JSXMLHttpRequestProgressEvent.o obj/release/JSXMLHttpRequestUpload.o obj/release/JSXMLSerializer.o
[23:57] <Daviey> ScottK: ?!
[23:57] <ScottK> obj/release/JSXPathNSResolver.o obj/release/JSXPathException.o obj/release/JSXPathExpression.o obj/release/JSXPathResult.o obj/release/JSXPathEvaluator.o obj/release/JSXSLTProcessor.o obj/release/InspectorFrontend.o obj/release/InspectorBackendDispatcher.o obj/release/CSSGrammar.o obj/release/HTMLNames.o obj/release/HTMLElementFactory.o obj/release/JSHTMLElementWrapperFactory.o obj/release/XMLNSNames.o obj/release/XMLNames.o
[23:57] <ScottK> obj/release/HTMLEntityTable.o obj/release/DocTypeStrings.o obj/release/ColorData.o obj/release/UserAgentStyleSheetsData.o obj/release/XPathGrammar.o obj/release/qwebframe.o obj/release/qgraphicswebview.o obj/release/qwebpage.o obj/release/qwebview.o obj/release/qwebelement.o obj/release/qwebhistory.o obj/release/qwebsettings.o obj/release/qwebhistoryinterface.o obj/release/qwebplugindatabase.o obj/release/qwebpluginfactory.o
[23:57] <ScottK> obj/release/qwebsecurityorigin.o obj/release/qwebscriptworld.o obj/release/qwebdatabase.o obj/release/qwebinspector.o obj/release/qwebkitversion.o obj/release/QtFallbackWebPopup.o obj/release/ChromeClientQt.o obj/release/ContextMenuClientQt.o obj/release/DragClientQt.o obj/release/DumpRenderTreeSupportQt.o obj/release/EditorClientQt.o obj/release/EditCommandQt.o obj/release/FrameLoaderClientQt.o obj/release/FrameNetworkingContextQt.o
[23:57] <ScottK> obj/release/GeolocationPermissionClientQt.o obj/release/InspectorClientQt.o obj/release/InspectorServerQt.o obj/release/NotificationPresenterClientQt.o obj/release/PageClientQt.o obj/release/PopupMenuQt.o obj/release/QtPlatformPlugin.o obj/release/SearchPopupMenuQt.o obj/release/WebPlatformStrategies.o obj/release/FullScreenVideoQt.o obj/release/IconDatabaseClientQt.o obj/release/moc_qwebkitplatformplugin.o obj/release/moc_qwebhistoryinterface.o
[23:57] <ScottK>  obj/release/moc_qwebpluginfactory.o obj/release/moc_qwebinspector.o obj/release/moc_qwebplugindatabase_p.o obj/release/moc_InspectorServerQt.o obj/release/moc_QtFallbackWebPopup.o obj/release/moc_FullScreenVideoQt.o obj/release/qrc_WebCore.o obj/release/qrc_WebKit.o obj/release/qrc_InspectorBackendStub.o   -L../../WebCore/release -L../../JavaScriptCore/release -L/usr/X11R6/lib -L/usr/lib/arm-linux-gnueabihf -lwebcore -ljscore -lsqlite3 -
[23:57] <ScottK> lXrender -lgio-2.0 -lgstapp-0.10 -lgstinterfaces-0.10 -lgstpbutils-0.10 -pthread -lgstvideo-0.10 -lgstbase-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lxml2 -lglib-2.0 -lQtGui -lQtNetwork -lQtCore -lpthread -lXext -lX11 -lm
[23:57] <ScottK> /usr/bin/ld: final link failed: Memory exhausted
[23:57] <ScottK> Oops.
[23:57] <ScottK> Sorry.
[23:57] <ScottK> infinity: Help.
[23:57] <ScottK> Almost got QtWebKit to build on armhf.
[23:57] <ScottK> Needs MOAR RAM.


[00:38] <antarus> cjwatson: :(
[16:53] <pmatulis> how do i install a package to be used at the partitioning stage?  would this work?:
[16:53] <pmatulis> d-i partman/early_command string apt-install gdisk
[16:54] <pmatulis> (debugging preseed files can take such a long time i thought someone could propel me forward)
[17:03] <cjwatson> apt isn't available at partitioning because the base system hasn't even been installed yet
[17:03] <cjwatson> you can use modules=something to install udebs
[17:04] <cjwatson> but you have to have made sure the appropriate things are actually available in udeb form first
[17:04] <cjwatson> best read something like the d-i internals documentation
[17:06] <pmatulis> alright thanks.  doesn't look easy
[17:54] <infinity> fwiw, there's no gdisk udeb, likely because you're expected to use parted, like everything else.
[17:55] <infinity> pmatulis: Is there a reason parted won't work for your usecase, or is it just that you're more familiar with the fdisk/sfdisk UIs?
[17:58] <pmatulis> infinity: i was just pointed to parted by someone else, silly me
[20:43] <bdmurray> xnox: Could you have a look at bug 1301720?
[20:43] <ubot2> Launchpad bug 1301720 in ubiquity (Ubuntu) "[Text Entry] Missing English input in Simplified and Traditional Chinese default enviroment" [High,Triaged] https://launchpad.net/bugs/1301720


[06:36] <ScottK> Sarvatt_: Has my logout patch stabilized yet?
[06:39] <RAOF> It hasn't hit master yet, no.
[06:56] <RAOF> Last update was on Friday; I'd expect more movement of it after the weekend.
[06:56] <ScottK> Thanks
[06:57] <RAOF> Note that I also cherry-picked the other glxdrawable refcnt patch in master for those test packages; you shouldn't be seeing the crash reported at the end of the upstream bug.
[06:59] <RAOF> It's still tracking along nicely?
[10:48] <bdmz> hi, does anyone know how /etc/environment gets loaded?
[10:49] <jcristau> pam_env
[10:49] <bdmz> thanks
[10:51] <era878> Sarvatt_ are you there?
[10:54] <era878> Sarvatt_, can you look at my Xorg.0.log, http://pastebin.ubuntu.com/545890/, and tell me why its loading the vesa driver instead of intel. Please could you email me the answer to<EMAIL_ADDRESS>[10:56] <bdmz>  Where would I put an env variable assignment that depends on bash completion and needs to run as early in the boot process as possible?
[10:58] <jcristau> bdmz: what are you trying to do, and why do you ask here?
[10:59] <bdmz> I switch between a couple of different JVMs alot, and I keep forgetting to update JAVA_HOME
[11:00] <bdmz> I ask here because someone in #ubuntu said you guys have are pretty knowledgeable
[11:01] <bdmz> I know this is the X channel bit I figured I'd ask
[11:15] <virtuald> bdmz: why not put it in .bashrc?
[11:17] <bdmz> I need to have it defined before services like tomcat are started
[11:17] <bdmz> that depend on it to start
[11:23] <virtuald> ok then set it in the upstart or init script
[11:25] <virtuald> or you could probably use the alternatives system to chose versions (update-alternatives)
[11:25] <bdmz> alternatives doesn't set JAVA_HOME
[11:26] <bdmz> and i'd like to have it set properly regardless of which services are running
[11:26] <bdmz> do you know of any way to hook into the alternatives system?
[11:27] <bdmz> it would be nice if I could run a script every time a change was made
[11:28] <virtuald> no i've never done that :>
[11:30] <bdmz> thanks anyway for the help, i know this is off topic
[20:44] <ScottK> RAOF: Still working nicely, AFAIK.


[00:46] <stokachu> catbus1, i should be around for a bit just ping me if you come back to it
[01:45] <stokachu> balloons, around?
[06:06] <pranav_> Hi. I have a question regarding Cinder charm.
[06:07] <pranav_> If i locally modify the cinder.conf through the shell and then modify config through the juju-gui
[06:07] <pranav_> the local changes get overridden. Any workaround this?
[07:13] <junaidali> pranav_: I haven't used juju gui for deployment. Have you tried modifying the template file in /var/lib/juju/agents/unit-cinder-0/charm/templates/ and then writing changes using gui?
[07:20] <pranav_> junaidali: No haven't tried that. We tried to see if any relation hooks get fired on modification but no good. Let me check the templates
[07:22] <pranav_> One question, to modify the template file our application has to be running in the same unit, correct? Or is there a way to change the templates via relations?
[07:36] <junaidali> imo, if you want some changes to be retained, you probably look for changing template file because whenever you change some config, all the template files will be re-written
[07:37] <junaidali> if you've more than one units of charm, update template file in each unit
[07:38] <junaidali> should probably*
[07:41] <pranav_> I see. In which case our application always has to co-exist with the cinder charm.
[07:43] <junaidali> sorry, just to correct what i said earlier, whenever we change any config, all the file are re-written **from the template file**
[07:43] <junaidali> pranav_:
[07:44] <junaidali> files*
[07:50] <pranav_> Cool! we are gonna try out changing the templates, which i feel should work for us.
[07:51] <pranav_> Thanks for the help Junaid :)
[08:33] <anrah> Hi! I'm starting to write tests to my charms, however I seem to have a problem:
[08:33] <anrah> 2017-02-07 10:32:51 Error getting env api endpoints, env bootstrapped?
[08:33] <anrah> 2017-02-07 10:32:51 Command (juju api-endpoints -e localhost-localhost:admin/default) Output:
[08:35] <anrah> http://paste.ubuntu.com/23946536/
[08:35] <anrah> juju version is 2.0.2
[08:37] <anrah> and amulet is 1.18.2
[08:37] <anrah> somehow it looks like the amulet? is using old juju commands that are not available on 2.0 ?
[08:47] <junaidali> anrah: what's the version of juju-deployer you have?
[08:48] <anrah> 0.6.4
[08:51] <anrah> I upgraded it but no help
[08:54] <junaidali> upgraded to which version? i think juju-deployer doesn't yet support 2.0. You can get a 2.0 supported package from Tim Van's ppa https://launchpad.net/~tvansteenburgh/+archive/ubuntu/ppa
[08:54] <anrah> 0.10.0 is the new version
[08:54] <junaidali> oh okay, you've the newest version..
[08:55] <anrah> I think the problem is not with the juju-deployer but the at the very first lines where the amulet? is trying to get information about the controller
[08:56] <anrah> as it trys to run this command: Command (juju api-endpoints -e localhost-localhost:admin/default)
[08:56] <anrah> and there is no juju api-endpoints command on juju 2.0
[08:56] <junaidali> yes, you're right
[08:57] <anrah> so.. Amulet is useless with Juju 2.0 ?
[09:03] <junaidali> wait, someone will help you. It is probably late for many people here
[09:05] <anrah> Thanks!
[09:19] <anrah> I think I mixed the python versions.. As amulet uses python3 and juju-deployer python2 so had old version of the juju-deployer on python2 packages
[09:22] <lazyPower> Zic heyo, i'm starting to hack on that issue you uncovered lastnight now.
[09:23] <lazyPower> Zic - should have something fo ryou to look at before we head into the kubernetes hacking sessions later today. This might take a bit, but i'm hoping to have something for you to setup in a staging capacity shortly.
[09:25] <Zic> lazyPower: hello, I just come to my office, you're so synced :)
[09:25] <lazyPower> Zic :) Blame it on Belgium
[09:26] <Zic> lazyPower: what jetlag does it cause to you? you came from London/Canonical?
[10:24] <lazyPower> Zic - i came from KC MO, so much further than London
[10:37] <Zic> lazyPower: so "jetlag" was the right word :D I was not so sure "jetlag" is applicable if you just... take the boat or the train :)
[10:41] <lazyPower> indeed. i'll be leaving tomorrow so onw that i'm adjusted to the timezone, its time to leave soon
[10:42] <lazyPower> @stub  hey stub, question for you re: layer-leadership if you're around
[10:42] <stub> yo
[10:42] <lazyPower> stub, can i just invoke it once and give it a dict? or do i need to call it everytime with key=val pairs for each data point i want the leader to push?
[10:43] <lazyPower>        charms.leadership.leader_set({'service_key': '/etc/kubernetes/serviceaccount.key', 'foo': 'bar'})
[10:43] <stub> that method accepts keyword arguments or a dictionary, so either leader_set({'foo': 'bar','baz':False}) or leader_set(foo='bar', baz=False)
[10:44] <lazyPower> oh fantastic
[10:44] <lazyPower> stub <3
[10:46] <stub> although now I look at the signature, leader_set(settings='hello') will fail, so don't call your leadership setting 'setting' until I fix that :-P
[11:37] <Zic> lazyPower: as you are at Europe time now, I will be available if you need any test to 19:00 :)
[11:37] <lazyPower> Zic - i'm just now deploying the first attempt at fixing, currently waiting on convergence
[11:37] <lazyPower> Zic - but as i'm at a conference its hard to dedicate any reasonable amount of time, so thank you for being patience
[11:37] <lazyPower> *patient
[11:37] <Zic> I understand, no worries :)
[11:38] <Zic> my customer continue to adapt their code to k8s with minikube installed locally for now
[13:09] <magicalt1out> kwmonroe: have you come up with an apachecon talk yet?
[13:09] <magicalt1out> dont want to end up sumitting something similar to you guys
[14:12] <xnox> let the fun begin
[14:12] <xnox> $ juju deploy easyrsa
[14:12] <xnox> ERROR cannot resolve URL "cs:easyrsa": charm or bundle not found
[14:14] <xnox> juju deploy cs:~containers/easyrsa-6 works.
[14:20] <marcoceppi> xnox: yup, it's not yet in a promoted namespace
[14:20] <xnox> ok
[14:20] <marcoceppi> xnox: you can expect it to complete review in time for the 1.6.0 release of kubernetes
[14:21] <xnox> working of instructions from https://jujucharms.com/u/containers/easyrsa/
[14:21] <xnox> I cannot do "juju deploy tls-client" and the relation name is wrong too?
[14:21] <marcoceppi> tls-client is a place holder for connecting to something that consumes tls
[14:21] <marcoceppi> xnox: what's your end goal?
[14:22] <xnox> currently testing that this charm (by itself) works on s390x.
[14:22] <xnox> assuming since i have managed to deploy easyrsa, it does.
[14:22] <marcoceppi> xnox: you'll probably want something that connects
[14:23] <marcoceppi> it's python so it'll probably work
[14:23] <marcoceppi> I don't think it uses anything that's not interprutted
[14:23] <xnox> i am getting a lot of _juju_complete_2_0: command not found
[14:24] <marcoceppi> xnox: where? in your terminal?
[14:24] <xnox> yes
[14:25] <xnox> when i try to tab complete things
[14:25] <xnox> (i'm running zesty)
[14:25] <marcoceppi> xnox: are you using the snap?
[14:25] <xnox> no
[14:25] <xnox> whatever is in zesty as deb
[14:36] <xnox> where is source code for https://jujucharms.com/u/containers/kubernetes-master/11 ?
[14:39] <marcoceppi> xnox: https://github.com/kubernetes/kubernetes/tree/master/cluster/juju/layers/kubernetes-master
[14:39] <xnox> marcoceppi, how would I fund that from the charmstore?
[14:40] <marcoceppi> xnox: you wouldn't unless it's in th ereadme
[14:41] <xnox> marcoceppi, but that's the source code, rather than published charm revision?
[14:41] <xnox> does that correspond to the v11 of the charm?
[14:41] <marcoceppi> xnox: no, that's the upstream code
[14:41] <xnox> marcoceppi, how can I clone the actual charm?
[14:41] <marcoceppi> xnox: just download the .zip or use `charm pull ~containers/kubernetes-master`
[14:42] <xnox> it's missing resources and binaries for my architecture, so i need to modify it and submit merge proposals back. But also test before I do all that.
[14:42] <marcoceppi> nope
[14:42] <xnox> what do you mean nope?
[14:43] <marcoceppi> resources aren't delivered in the source code
[14:43] <marcoceppi> you can deploy kubernetes-master from the store, and attach your kubernetes rsource during that time from a local mirror
[14:43] <xnox> =)
[14:43] <xnox> sure, but i want to fix it for everyone on s390x, not just me.
[14:44] <marcoceppi> xnox: well, that's a slight change, but it's on our roadmap. s390x either just landed in upstream for support or will be soon
[14:44] <marcoceppi> once it does we can include it in the charm officially
[14:44] <xnox> landed
[14:44] <marcoceppi> xnox: either way, you'll want to submit pull requests to the repo mentioned above
[14:45] <xnox> ok
[14:45] <marcoceppi> xnox: as the charms are built from that source, using `charm build`
[14:45] <xnox> and after charm build, i can test my merge proposal locally, right?
[14:45] <xnox> (last time i did charms, there was no `charm build` and no reactive anything)
[14:46] <marcoceppi> xnox: modify the code; charm build, juju deploy builds/kubernetes-master --resource kubernetes=s390x.tar.gz; test
[14:46] <marcoceppi> xnox: I'm a bit busy at the moment, but i'd love to help you more
[14:46] <xnox> ok, thanks for your time.
[14:46] <marcoceppi> Very interested in getting s390x support (and ppc64el) added to the charms
[14:46] <marcoceppi> we have two routes we're chasing for that, so we should chat more
[14:47] <admcleod> it appears my 'juju deploy' is using a proxy, although i dont have http_proxy or https_proxy set - any ideas?
[14:52] <lazyPower> stokachu - both the snap and deb packages are illustrating some odd behavior. its no longer waiting for the deployment
[14:52] <lazyPower> stokachu - i'll try to get more details about this and get a proper bug filed, but just FYI'ing you that there's one in flight incoming.
[14:52] <stokachu> lazyPower, thanks im debugging right now
[14:52] <lazyPower> oh has someone already reported?
[14:53] <stokachu> yea arosales
[14:53] <lazyPower> Zic - i've got a branch in flight, not going to be ready by EOD today.
[14:53] <lazyPower> Zic - however, i will def get some additinoal testing on this and ping you in the PR so you can track its progress
[14:59] <xnox> i am confused where and how a resource ends up packaged and uploaded into the charm store.
[15:02] <rick_h> xnox: how so? using the charm command?
[15:03] <xnox> rick_h, but i'm failing to pin point where the resource is assembled/downloaded from, e.g. a makefile or some declarative syntax.
[15:05] <rick_h> xnox: https://jujucharms.com/docs/2.0/developer-resources ?
[15:06] <xnox> aha! thank you
[15:08] <xnox> rick_h, is there $ charm resource-get command?
[15:08] <arosales> lazyPower: in case your interested the bug I filled was https://github.com/conjure-up/spells/issues/45
[15:08] <lazyPower> arosales - thats consistent with whats happened in the k8s flavors of spells
[15:08] <lazyPower> thanks, i'll sub to this
[15:09]  * arosales thought it was the deploy_done step, but seems more prevalent if your hitting it as well. Good news is stokachu is aware and working on a fix.
[15:10] <rick_h> xnox: so there's a resource-get hook for the charm itself. I don't see a charm pull-resource like there is a charm pull command for outside of a running unit :(
[15:10] <xnox> rick_h, also that makes little sense...... so the resource has binaries, but they are x86-64 binaries.
[15:10] <xnox> rick_h, how does one envision having arch specific resources? e.g. similar to how juju-tools are arch specific.
[15:10] <xnox> rick_h, can I register s390x resource; amd64 resource; etc? with the same name?
[15:11] <xnox> or shall I have everything inside the resource tarball and do it myself in the charm (and keep just one resource name)
[15:11] <marcoceppi> xnox: well we're doing one of two things
[15:11] <xnox> it seems like it's already an API that a tarball with toplevel binaries must be supported
[15:12] <marcoceppi> xnox: the first is you can add a named resource like `kubernetes-s390x` and rename kubernetes to `kubernetes-x86`
[15:12] <rick_h> xnox: no, so I think you'd need to define them as different resources and upload them at publish time and then the hooks would have to have an if block that states "if arch = xxx resource-get xxx"
[15:12] <xnox> eeewwww
[15:12] <marcoceppi> xnox: packing every arch in a tarbal is expensive for everyone
[15:12] <Zic> lazyPower: just saw your message, ACK, thanks for your work while travelling anyway... it's tough :)
[15:12] <marcoceppi> xnox: to be honest we're moving ot snaps for deliverying kubernetes
[15:13] <xnox> marcoceppi, renaming a resource breaks all deployments that use custom resource.
[15:13] <marcoceppi> which handles architecture specific payloads (and adds security / process confinement)
[15:13] <marcoceppi> xnox: we'll we'd deprecate the kubernetes resource
[15:13] <xnox> ack.
[15:13] <marcoceppi> keep it, but deliver an empty blob
[15:13] <marcoceppi> the charm would say if the blobs empty, look for an arch named resource key
[15:14] <marcoceppi> that way we wouldn't break exising custom stuff
[15:14] <marcoceppi> we can do that tastefully, but I think we're going to move away from charm resources
[15:14] <xnox> about expensive, the tarball is currently 78MB, if we explode it 3 times. It's ok, if we download that; but then remove unused arches.
[15:14] <xnox> ./foo ->
[15:15] <xnox> ./x86_64/foo
[15:15] <xnox> ./s390x/foo
[15:15] <xnox> ./ppc64el/foo
[15:15] <xnox> as a resource should be backwards enough compatible. E.g. look for ./arch/foo, failing that take ./foo and run with it.
[15:16] <Zic> lazyPower: do you have any recommendation to do manually the work of the fix while waiting for the fix? my customer/devs works on their minikube locally while the cluster is b0rken so it's fine, but I need myself to do some testing (like connecting our k8s cluster with our Nagios)
[15:17] <lazyPower> Zic - you can manually sync those files, but i'd rather have this run during a charm upgrade so its consistent if thats ok
[15:17] <lazyPower> Zic - otherwise i'm encourgaing you to make a snowflake
[15:21] <Zic> lazyPower: bonus question, how can I explain to my customer that this problem was not discovered in your testing environment, as for him, the step-to-reproduce is just a reboot
[15:21] <Zic> I don't want to put all the fault on your shoulders :/
[15:21] <lazyPower> Zic - we're in beta and HA testing hasn't been part of the release process. #honestanswer
[15:21] <Zic> what can cause this in our environment and not in your?
[15:22] <lazyPower> Zic - we've been more focused on single master with in-place upgrades, once that's rock solid, we were going to do HA testing.
[15:22] <lazyPower> you just happened to beat us to it :)
[15:22] <Zic> \o/
[15:22] <lazyPower> Zic and thanks to that testing, we should get HA bits done before we're done with the upgrade testing that we're still working through. A lot of the plumbing is there
[15:22] <lazyPower> but the minor release updates is different from major release updates
[15:23] <lazyPower> so we're workign through *that* story this cycle, is 1.5.x => 1.6.x
[15:27] <stokachu> lazyPower, are you guys seeing errors like (ServerError(...), 'json: cannot unmarshal string into Go value of type uint64')
[15:27] <stokachu> arosales, ^
[15:29] <arosales> stokachu: checking
[15:30] <stokachu> arosales, lazyPower, can you guys also try with `sudo snap refresh conjure-up --edge`
[15:30] <stokachu> i got some more debugging in there
[15:30] <arosales> stokachu: not seeing that in my stack trace, where else should I look?
[15:30] <stokachu> arosales, ~/.cache/conjure-up/conjure-up.log
[15:33] <arosales> stokachu: not finding that string in my conjure-up.log
[15:33] <stokachu> arosales, ok give that --edge version a go
[15:33]  * arosales now going to try with "sudo snap refresh conjure-up --edge
[15:33] <stokachu> thanks
[15:40] <Zic> hmm, what exactly "juju enable-ha" do? especially as I'm on manual-cloud provisionning with no MaaS, does it pop a new juju controller machine?
[15:45] <Zic> jcastro: hello, the k8s meeting we talked the last week is tomorrow right?
[15:46] <Zic> I will have time to come this time normally :)
[15:48] <stokachu> arosales, how's it going?
[15:48] <marcoceppi> Zic: on manual nothing much, however if you `juju switch controller; juju add-machine <user>@<ip>; juju add-machine <user>@<ip>; juju enable-ha --to <machine-id1>,<machine-id2>;` you can get ha for contorller. However, there are some caveats with manual provider
[15:49] <Zic> marcoceppi: thanks! was wat I'm looking for :)
[15:49] <Zic> what*
[15:51] <arosales> stokachu: hitting a snap issue atm
[15:51] <arosales> working through that
[15:51] <stokachu> arosales, ok
[15:52] <Zic> marcoceppi: I think we're going to deploy a MaaS anyway if we have other infra like the one we are preparing with CDK, as our interest for Juju will also be on OpenStack in coming month
[15:52] <marcoceppi> Zic: I think it'll help with a lot of the headaches you've had
[15:56] <Zic> the main reason I didn't deploy a MaaS was because we have a kind of like prudct internally-developed, but with less features, and for only one infra, even if MaaS has more features, it's a bit redundant (and our internal system is so strongly tied to other tools we used here...)
[15:56] <Zic> but as we're planning to deploy more CDK, and test Juju for OpenStack in coming month... I will give it a try :)
[15:57] <Zic> s/prudct/product/ what happened to my keyboard! :]
[16:01] <arosales> stokachu: got a stack at a different point now
[16:01] <arosales> http://paste.ubuntu.com/23948408/
[16:01] <stokachu> arosales, paste ~/.cache/conjure-up/conjure-up.log
[16:02] <SimonKLB> when having reset:false in the bundletester yaml manifest, are charms already in the model supposed to be upgraded if the test is running a newer version of the charms or not?
[16:02] <SimonKLB> i suppose this is up to amulet?
[16:03] <marcoceppi> Zic: sure, understood. If that system has an api, you could probably bridge the two, by adding your thing as a cloud provider, if you're comfortable with golang
[16:03] <arosales> stokachu: http://paste.ubuntu.com/23948419/
[16:03] <arosales> stokachu: odd its calling out not registering a controller
[16:03] <arosales> conjure should make one for me if I don't have one, but I going to bootstrap and try again just for a data point
[16:04] <stokachu> arosales, yea it can't find your aws creds for some reason
[16:04] <stokachu> do you have ~/.local/share/juju/credentials.yaml file?
[16:06] <arosales> stokachu: http://paste.ubuntu.com/23948429/ <--- with a controller bootstrapped
[16:06] <Zic> marcoceppi: Go is one of my "needed skills of 2017", as I'm only skilled in C today (and Bash/Python of course, but I do not place Go in the scripting category)
[16:06] <stokachu> arosales, ok remove ~/.local/share/juju/credentials.yaml
[16:06] <arosales> stokachu: and yes I have a ~/.local/share/juju/credentials.yaml file
[16:06] <arosales> ?
[16:07] <stokachu> arosales, look in that file is one of the accounts for aws incomplete?
[16:07] <arosales> I still get a stack when I conjure-up with a controller ready
[16:07] <stokachu> i wonder if we're failing on that
[16:07] <arosales> I bootstrapped just fine
[16:07] <stokachu> arosales, pastebin ~/.cache/conjure-up/conjure-up.log
[16:08] <arosales> http://paste.ubuntu.com/23948438/
[16:08] <stokachu> arosales, ah! ok that was the bug i was wrestling
[16:08] <stokachu> arosales, i pushed an update `sudo snap refresh conjure-up --edge`
[16:08] <stokachu> there is an issue with the constraints parameters we're doing
[16:09] <arosales> snap refresh conjure-up --edge
[16:09] <stokachu> yea
[16:09] <arosales> previously didn't give me an update
[16:09] <arosales> said I was at the latest
[16:09] <arosales> ran it again . . .
[16:09] <stokachu> what about now?
[16:09] <arosales> and looks to be downloading
[16:09] <stokachu> arosales, should be rev56
[16:09] <arosales>  snap refresh conjure-up --edge
[16:09] <arosales> conjure-up (edge) 2.1.0 from 'canonical' refreshed
[16:09] <arosales> any way to tell which rev?
[16:09] <stokachu> whats snap list show?
[16:09] <arosales> conjure-up  2.1.0    56   canonical  classic
[16:09] <stokachu> yea
[16:09] <arosales> rev 56
[16:09] <stokachu> try that
[16:10] <arosales> ok
[16:11] <Zic> marcoceppi: in the first stage of Go, I preferred Rust as it's more like C (no garbage collector or runtime), but Go is everywhere today, so I'm beginning to train at it :)
[16:11] <arosales> stokachu: good that it is now waiting for applications to deploy
[16:11] <arosales> still getting an odd message about the size of my terminal though
[16:12] <stokachu> arosales, ok good, yea need to debug the constraints
[16:12] <arosales> but if the spell works . .  . .
[16:12] <stokachu> arosales, yea you gotta be 134x42
[16:12] <stokachu> arosales, you using gnome-terminal
[16:12] <arosales> what ever ships with xenial
[16:13] <arosales> gnome 3.18.3
[16:13] <stokachu> arosales, so if you go to the menu item 'Terminal' and select 132x43
[16:13] <stokachu> that's what we test the UI on
[16:13] <stokachu> that size
[16:13] <arosales> I def have a terminal > 132x43
[16:14] <stokachu> hmm ok i just tested it and it works as expected
[16:14] <stokachu> arosales, those are rows and columns
[16:14] <stokachu> nothing to do with the resolution
[16:15] <arosales> but I did go ahead and try to select Terminal --> 132x43 and then `conjure-up bigdata` and I still get the warning
[16:15] <arosales> stokachu: no stack and waiting for the deploy though . .  .
[16:15] <stokachu> arosales, ok cool
[16:19] <arosales> stokachu: got to reclocate
[16:19] <arosales> but looks to be coming up
[16:19] <stokachu> arosales, ill be here
[16:19] <stokachu> arosales, cool thanks
[16:19] <arosales> not sure how conjure will handle a suspend
[16:19] <arosales> we'll see
[16:19] <arosales> getting kicked out of this room
[16:19] <stokachu> are you  mid deploy?
[16:19] <arosales> thanks for the speedy work on the bug
[16:19] <stokachu> np
[16:19] <arosales> yes deploying to aws atm. . . .
[16:20] <stokachu> ok yea that'd be interesting to see
[16:35] <Madarafv> Like teh video plssss!!! https://youtu.be/wFhaJaY4pqU
[16:35] <Madarafv> PLSSS
[16:35] <Madarafv> shur up and like, no DISLIKES
[16:46] <cholcombe> gnuoy, i'm having trouble finding the ceph nerpe scripts.  Do you know where they are?
[17:14] <lutostag> cory_fu: kwmonroe: any chance I can get write access/collab to https://github.com/juju/juju-crashdump when you all get a chance?
[17:15] <cory_fu> lutostag: You should already have admin access.  Let me get you the invite link again
[17:16] <cory_fu> lutostag: https://github.com/juju/juju-crashdump/invitations
[17:17] <lutostag> cory_fu: indeed, thanks!
[17:55] <catbus1> stokachu: conjure-down command not found, how do I destroy the deployment?
[18:02] <mmcc> catbus1: all conjure-down does is 'juju destroy-model -y' under the hood. If you can tell which model it created, you can do it and nothing else needs to happen
[18:03] <catbus1> mmcc: got it, thanks.
[19:36] <hml> help please: juju ssh nova-compute/0 is failing with an ssh key failure… however then ssh-keygen to remove the line can’t find the ssh_known_hosts file listed.
[19:37] <hml> where would it reside?
[19:43] <stokachu> catbus1, you install via snap?
[19:43] <catbus1> stokachu: no, via apt, added ppa:conjure-up/next first. 16.04
[19:44] <catbus1> stokachu: the snap install with the --classic flag doesn't work, it says --classic flag is unknown
[19:44] <stokachu> catbus1, ok if you remove that package and do `sudo snap install conjure-up --classic --beta`
[19:44] <stokachu> catbus1, you need to be using snap 2.21
[19:44] <stokachu> which is in the xenial-updates
[19:45] <catbus1> hm, snap is not installed on the node.
[19:45] <catbus1> ok, I will remove conjure-up and start from snap.
[19:45] <stokachu> catbus1, thanks
[19:47] <catbus1> stokachu: to confirm, by snap 2.21, you mean 'snap' package, or 'snapd'? I do have snapd and snap-confine 2.21 installed.
[19:47] <stokachu> catbus1, yea snapd version 2.21
[19:49] <catbus1> weird, snap install conjure-up with --classic flag works now.
[19:50] <stokachu> catbus1, :)
[19:52] <catbus1> stokachu: conjure-up is installed fine. Will redeploy openstack soon.
[19:52] <stokachu> catbus1, \o/
[19:52] <stokachu> catbus1, ill be around lemme know how it goes
[19:52] <catbus1> stokachu: Thank you!
[21:16] <catbus1> stokachu: Running 'conjure-up' says -bash: /usr/bin/conjure-up: No such file or directory
[21:17] <catbus1> conjure-up 2.1.0 56 canonical classic
[21:29] <catbus1> it works on another machine. reinstalling
[21:37] <stokachu> catbus1, you probably need to logout and back in
[21:37] <stokachu> if you apt removed previously deb package
[21:38] <catbus1> got it
[22:56] <stormmore> anyone played with running Nexus3 in a container?


[08:51] <tjaalton> klebers: hi, you marked 1818049 as invalid for trusty, but the sru queue has an upload for it to fix the dkms build?
[10:30] <klebers> tjaalton, hi. Initially I have submitted the patches to fix only the packages that seemed to be supported with the 4.4 kernels by the ADT matrix. virtualbox seems to be not installable alongside linux-lts-xenial on trusty. But probably LocutusOfBorg made an upload with that build fix along with a security fix
[10:32] <tjaalton> klebers: ok, I've asked him why there are multiple uploads on the queue, I'll just wait his reply :)
[10:32] <tjaalton> +for


[00:01] <spiv> Good morning.
[00:09] <peitschie> mornin spiv
[00:36] <poolie> jelmer, hi, still awake?
[00:36] <poolie> hi spiv
[00:36] <jelmer> poolie: Hi!
[00:36] <jelmer> poolie: Apparently :-)
[01:34] <spiv> Ooh, I'm patch pilot this week.
[01:35] <spiv> poolie: perhaps you should review https://code.edge.launchpad.net/~gz/bzr/smart_add_former_file_dir_251864/+merge/38676 ?  I think you may have touched that code or near it with your smart_add deprecation patch.
[01:35] <poolie> spiv, actually i was going to propose swapping with you because i'll be away for the next two
[01:36] <poolie> i have, i'd be happy
[01:36] <poolie> to
[01:36] <poolie> (otp)
[01:37] <spiv> So you'd pp this week, and I'd pp the week of Nov 1?  I'm happy to do that.
[02:00] <dOxxx> spiv, pooile: y'all are just afraid to review my monster mergetools mp ;)
[02:00] <dOxxx> poolie^
[02:00] <spiv> Heh
[02:01] <spiv> dOxxx: pfft, I had patch with a 26000 line diff last week ;)
[02:01] <dOxxx> I don't blame you. Took me 3 months.
[02:01] <dOxxx> Automated refactorings don't count! :)
[02:04] <poolie> :)
[02:04] <poolie> spiv of course you can still do reviews this week
[02:15] <poolie> spiv, are you all better? or a bit better?
[02:31] <spiv> poolie: I'm mostly better.
[02:32] <spiv> Well enough to continue looking at https://bugs.edge.launchpad.net/udd/+bug/653307 at least :)
[02:33] <poolie> want a quick catchup call or pm (depending on the state of your voice)?
[02:50] <zamabe> so. debian and bzr
[02:50] <zamabe> i hear they don't mix
[02:50] <zamabe> and i can't exactly download it
[02:52] <poolie> what is 'it'?
[02:52] <spiv> poolie: a catch up would be good, but maybe just after lunch as I'm in the middle of digging through a udd/bzr-builddeb maze right now
[02:52] <poolie> ok, thanks
[02:53] <zamabe> poolie, i've recently decided to download the tarball and build it
[02:53] <zamabe> what i mean by 'it' is this
[02:54] <zamabe> http://wiki.bazaar.canonical.com/DistroDownloads#Debian
[03:50] <poolie> zamabe, you just need 'sudo apt-get install bzr' or the equivalent
[04:08] <jbowtie> FryGuy-, thanks for those branches; I've already merged one and will create patches based on the other two soon.
[04:09] <jbowtie> FryGuy-: I was also surprised to see that it worked with 2010 with such a small change. They actually did pretty well with backwards compatibility.
[04:09] <jbowtie> FryGuy-: unfortunately I can't use the branch directly, need to put in conditional version checks.  ;)
[04:19] <jbowtie> poolie: My "chopping up the file" proposal was based on what ZFS, Dropbox, et al do for versioning large files. Memory usage was a side effect.
[04:19] <jbowtie> poolie: Do you know of any better algorithms I should be looking at, maybe in the literature somewhere?
[04:38] <poolie> i think the basic idea of chopping it up based on a rolling checksum is not too bad
[04:54] <lifeless> it might be nice to just be deterministic
[04:54] <lifeless> every 128K for instance
[04:54] <lifeless> so that we don't have to /diff/ to do it.
[04:54] <lifeless> in fact, thats probably a must-do, not a might-do.
[04:59] <jbowtie> lifeless: Should that apply to large text files as well or just binaries.
[04:59] <jbowtie> ?
[05:11] <poolie> well, rolling checksums are deterministic
[05:11] <poolie> spiv, can you reproduce that bug in bzr alone?
[05:13] <lifeless> poolie: they are, but using them to find the boundary between and old and new version means that partial branches cannot reproduce the result
[05:13] <lifeless> poolie: which is a significant concern
[05:13] <poolie> maybe we're talking about different things?
[05:14] <poolie> i understood jbowtie to be considering using them to chop single large files
[05:16] <jbowtie> Yes, trying to find a way to solve some of the issues around large binaries.
[05:16] <lifeless> that would be fine, I understood him to be using delta logic based on that
[05:16] <lifeless> via the reference to zfs and dropbox
[05:17] <spiv> poolie: no, at least not without intentionally driving the bzrlib APIs to generate two inventories with the same ID but different details.
[05:17] <poolie> jbowtie: so are you saying that dropbox chop the files on boundaries and then apply librsync?
[05:17] <poolie> i know they at least used to use librsync
[05:19] <jbowtie> poolie: AFAICT yes, that lets them do data deduplication as well as versioning.
[05:19] <poolie> mm
[05:21] <poolie> jbowtie: i'm wondering: in which layer should this be done?
[05:22] <poolie> should the repository present the abstraction that you're just dealing with files, some of which may be extremely large?
[05:22] <poolie> or do you want to expose it at a higher level?
[05:22] <poolie> to me it seems pretty clear it should be behind that abstraction if at all possible
[05:23] <poolie> so then we do need to make sure all those interfaces work with iterators of bytes (or some similar convention)
[05:23] <poolie> otherwise we'll just propagate this problem
[05:26] <jbowtie> poolie: I'd like to keep it confined to the repository if possible, but I think I need to spend some time trying to implement it to come up with something workable.
[05:26] <jbowtie> poolie: Figured I'd put together something experimental this week if I can find the free time.
[05:27] <jbowtie> Speaking of which I have to go offline while I travel home; pick up the conversation on the mailing list if necessary.
[05:34] <poolie> i don't really understand the relevance of the xemacs startup to hooks...
[05:34] <poolie> spiv: now?
[05:35] <spiv> poolie: now is good
[07:34] <vila> hi all !
[07:44] <spm> yo vila!
[07:45] <vila> spm: hey !
[07:57] <vila> poolie, spiv: Hmm, did I miss something ? jam and poolie are at UDS next week, so PP should be either me or spiv for week 43 (starting 25 oct)
[07:58] <poolie> that is what i meant to make it
[07:58] <poolie> ... and i got it wrong
[07:58] <poolie> i'll fix it
[07:58] <vila> poolie: done
[07:59] <vila> was doing it in parallel but wanted to give a heads-up
[08:00] <lifeless> spiv: you should get a twitter account ;)
[08:44] <poolie> vila, did you get to talk to charline?
[08:44] <vila> poolie: no, she never ponged, I will try again today
[08:45] <vila> poolie: hmm, she's not online currently though...
[08:45] <vila> poolie: I will mail her
[08:45] <poolie> ah, she might have already gone to the US
[08:45] <poolie> that would be good
[08:45] <vila> argh, goodbye same-TZ-ness
[08:46] <poolie> i thought she wasn't leaving til later this week
[08:47] <vila> and I can't find here on the UDS-N attendees :-? >-/
[08:53] <poolie> vila, ok, i sent her a mail
[08:53] <poolie> you could call later today?
[08:53] <vila> poolie: sure
[08:57] <poolie> what a day
[08:57] <poolie> i'm going to sign off, good night
[09:01] <vila> poolie: night !
[09:13] <thevibe> morning anyone
[09:14] <thevibe> does anyone of you have a post_commit update hook/plugin ?
[09:18] <lifeless> what do you mean?
[09:51] <thevibe> I mean if you have an already running post_commit hook/plugin that does an update on the server
[09:53] <thevibe> lifeless - I'm just at the beginning with python so I don't want to jump over my level with a plugin that needs to serve a development environment
[09:54] <lifeless> oh, I think someone may have written one
[09:54] <lifeless> check the plugins page?
[09:56] <thevibe> lifeless, I checked google up to page xx and I can't find one
[09:56] <lifeless> hmm
[09:56] <thevibe> honestly the problem is that I can't wait till I get a ggod grip of python for this
[09:57] <thevibe> I need it and that's why I am asking for help
[09:57] <lifeless> I'd ask on the list
[09:57] <lifeless> more people see questions there
[09:57] <thevibe> I built the development environment in a semi-decentralized manner
[09:57] <thevibe> and because is the developement server and we have a routine in place
[09:58] <thevibe> an update run after commit will display everything in the broser straight away
[09:58] <thevibe> which is what I want
[09:59] <thevibe> I've sent my question there but not very successful
[09:59] <thevibe> because of that I said I will come here maybe someone has one and maybe will be willing to share it
[10:00] <thevibe> the other problem is that I need to put everything in place to close the gates for svn fans asap
[10:00] <thevibe> :)
[10:24] <GaryvdM> thevibe: Not sure if I understand you correctly, but maybe the bzr-upload plugin will do what you want.
[10:37] <thevibe> bzr-upload will be used to deploy things but I don't think it does what I want
[10:38] <thevibe> I just want an equivalent of an svn post_commit hook that runs an update on the server after any commit
[10:39] <thevibe> it should be in the same category with hooks that send an email after commit or something similar
[10:40] <thevibe> to describe the structure this is how it looks
[10:40] <thevibe> we init a project on the server
[10:40] <GaryvdM> thevibe: What does "runs an update" entail?
[10:41] <thevibe> the developer will checkout a branch which is bound to the main one
[10:41] <thevibe> after any chaneg the developer will commit the changes to the main repo
[10:41] <thevibe> after that cmmit I need a hook that will execute a bzr update
[10:41] <thevibe> so I can see the changes in the browser straight away
[10:42] <thevibe> is being used for web dev mostly
[10:42] <thevibe> GaryvdM, after a commit I need a hook that will execute bzr update on the server
[10:43] <thevibe> it is something like push-and-update but I need commit-and-update
[10:43] <GaryvdM> thevibe: Ok - bzr update needs to be run on the server. Do the devs all have ssh access?
[10:43] <thevibe> everything is run under ssh
[10:43] <thevibe> bzr+ssh
[10:44] <thevibe> so yes they have as the server is inside
[10:44] <thevibe> but I need an automated process
[10:44] <thevibe> I don't want them to login and run the command by themselves
[10:45] <GaryvdM> thevibe: You will want a post tip change hook on the master branch, rather than a post commit hook on the devs branch, so that if they unbind, and push, it still works.
[10:45]  * GaryvdM looks at the push-and-update to see if it can be made to do this
[10:46] <GaryvdM> * push-and-update code...
[10:47] <GaryvdM> thevibe: Note that you can get bzr-upload to do this...
[10:48] <thevibe> as I was saying I am not very advanced with python so I don't want to digg in an area where I can miss things and not understand others
[10:48] <thevibe> GaryvdM, can you give me more details on how bzr-upload can do this
[10:48] <thevibe> ?
[10:49] <thevibe> I trust you about the post tip change hook but the issue is still there: how can I get one of those? :)
[10:51] <GaryvdM> thevibe: step 1: in the master branch  on the server, run bzr remove tree
[10:52] <GaryvdM> thevibe: step 2 : from your pc run bzr upload sftp://server/path-to-branch  -d bzr+ssh://server/path-to-branch --auto
[10:54] <GaryvdM> thevibe: that will get bzr-upload to do a post tip change hook on bzr+ssh://server/path-to-branch to upload to sftp://server/path-to-branch
[10:55] <GaryvdM> thevibe: step 3: make all the devs install bzr-upload.
[10:56] <Glenjamin> s/remove tree/remove-tree/
[10:56] <GaryvdM> Glenjamin: yes - thanks
[11:06] <thevibe> excellent
[11:06] <thevibe> I will do that
[11:06] <thevibe> one more thing
[11:08] <thevibe> some of the are front-end developers or even designers and I suggest them to use bzr explorer as it can be installed on multiple OS's
[11:08] <thevibe> I use Ubuntu, for me it's easy
[11:08] <GaryvdM> Hmm - push-and-update date has a post_push hook, but that limits it to push. It would be much more useful if it used post-tip-changed, like bzr upload..
[11:08] <thevibe> can I create a tool in bzr for this command?
[11:09] <thevibe> you're right and I told you I tried that plugin and is not exactly what I need
[11:09] <thevibe> it has his good parts but probably a post-tip-changed would be much more useful in real-world
[11:10] <thevibe> I think at least
[11:10] <thevibe> :)
[18:21] <mgz> I'm pretty sure using bzr with gunicorn is just a bad idea.
[18:26] <jam> mgz: but... but... unicorns, man
[18:27] <mgz> the problem on the list doesn't look intermittent though, so I won't start yelling about signals just yet.
[18:27] <jam> mgz: signals shmignals, unicorns man, its all about the unicorns
[18:28] <jam> (and the fairy dust, but that is harvested from the unicorns anyway)
[18:28] <mgz> shouldn't animal welfare have something to say about covering a unicorn in green paint?
[18:29] <GaryvdM> Hi mgz, jam
[18:29] <jam> hi GaryvdM
[18:29] <mgz> have you got any smart ideas on bug 663234 Gary?
[18:30] <GaryvdM> He He, was about to ask you....
[18:30] <GaryvdM> * I was...
[18:31] <mgz> well, Alexander might be right, it's hard to tell without more information
[18:31] <mgz> suggesting the guy tries do just do python -c "import PyQt4.QtGui" might help.
[18:31] <GaryvdM> He said that it was working with 2.2.0, so I wonder if he removes the msvcp dlls and manifest, if it will work
[18:32] <mgz> yeah, I wondered if it was something I'd broken, but I'm not even sure which installer he used
[18:32] <GaryvdM> I've been assuming 2.2.1-2, but I may be wrong.
[18:33] <GaryvdM> I looked, and I can't find any window 2000 cd.
[18:33] <mgz> yeah, not sure it's really worth us trying to test it.
[18:34] <mgz> working out some sensible things for him to try might be worth it though.
[18:34] <GaryvdM> I was still in school when win2000 came out - Seems so long ago.
[18:34] <mgz> ehehhe
[18:34] <mgz> I have a box with win98 on it still!
[18:34] <GaryvdM> :-0
[18:35] <mgz> but I was in school when I got it.
[18:36] <GaryvdM> I never used 98 much. I went from 95 -> nt 4
[18:38] <GaryvdM> btw - I got my build host working finally :-) I need to document how I did it with vs express .
[18:38] <mgz> cool.
[18:40] <GaryvdM> And I have built a 64bit python installer, which I need to upload. But I think what people will really be looking for is the standalone 64bit installer.
[18:41] <mgz> I did wonder what people were going on about on the mailing list with 64 bit windows.
[18:41] <mgz> ...if you care that much, just download a 64 bit python and install bzr yourself
[18:42] <GaryvdM> I'm busy in building a 2.2.1-3, with bzr-explorer 1.1.1. 1.1.0 had a bug thats getting alot of heat.
[18:45] <GaryvdM> mgz: Did you see my mail about using build out for the dependences?
[18:45] <mgz> ...no, what list was it sent to?
[18:46] <GaryvdM> mgz: bzr-windows
[18:46] <GaryvdM> Ah - just got jam's reply
[18:47] <jam> GaryvdM: well, I just sent it now, too :)
[18:47] <jam> I like the idea
[18:47] <jam> not sure about the path
[18:47] <jam> I would be fine using a default that fits the build machine
[18:48] <mgz> I'd really like a way of bypassing buildout, but using it for more things is also good.
[18:49] <GaryvdM> jam: I finally managed to create a bundle on ec2, but the name I gave it was not very good. Sorry
[18:54] <mgz> jam: if you have a mo, could I have some input on my worrying in <https://code.launchpad.net/~gz/bzr/require_unicode_committer_614593/+merge/38334> ?
[18:58] <jam> mgz: commented
[19:00] <mgz> thanks!
[19:27] <mtaylor> is there already a bug out there requesting that bzr launchpad-login set bzr whoami based on metainfo on launchpad
[19:28] <mtaylor> I _keep_ having folks who have obviously dong lp-login (since they are pushing) but skip the whoami step because nothing reminds them to
[19:30] <fullermd> Don't recent versions just refuse to commit if you haven't whoamied?
[19:30] <fullermd> (whoami'd?  How do you conjugate that?)
[19:53] <mtaylor> fullermd: not that I can see ... although maybe that's in newer revs than what we have
[19:53] <mtaylor> fullermd: do you mean post-2.2?
[19:53] <fullermd> Looks like it was in 2.2.
[20:08] <mwhudson> jam: hi
[20:18] <jam> hi mwhudson
[20:18] <mwhudson> jam: did you see the lp-service failure?
[20:19] <jam> yes, I wasn't 100% sure about what it was telling me
[20:19] <mwhudson> jam: i think it's an unbound variable 'socket_path'
[20:19] <jam> mwhudson: what I saw was "exited without failures but with nonzero exit code"
[20:21] <mwhudson> $ pyflakes lib/lp/codehosting/tests/test_acceptance.py
[20:21] <mwhudson> lib/lp/codehosting/tests/test_acceptance.py:81: undefined name 'socket_path'
[20:21] <mwhudson> jam: ^
[20:21] <jam> AttributeError: 'TestProtocolClient' object has no attribute '_exc_info_to_unicode'
[20:23] <jam> mwhudson: so it certainly could have failed randomly because of a broken exception handler
[20:23] <jam> but all the test_acceptance tests seemed to pass here
[20:25] <mwhudson> jam: you haven't forgotten to push to lp?
[20:26] <mwhudson> jam: because there's pretty clearly a socket_path that needs to be self.socket_path in the branch i just pulled
[20:27] <jam> it is possible
[20:27] <jam> or I pushed without commit, etc
[20:30] <mwhudson> jam: the deprecationwarnings are probably from the atexit stuff
 AttributeError: 'TestProtocolClient' object has no attribute '_exc_info_to_unicode' <- this is subunit bug 635702 and indicates an old testtools version
[21:13] <jam> mgz: someone should tell launchpad to update their testtools :)
[21:13] <mgz> There's probably an rt on it buried somewhere.
[21:16] <mgz> content filtering hits before diff, right?
[21:17] <mgz> so, content filtering a utf-16 file to utf-8 in the repo would mean you could diff it?
[21:29] <mwhudson> jam: lifeless tried (to update testtools), it uncovered some broken tests
[21:54] <lifeless> mwhudson: I'd be delighted if you wanted to tug on them.
[21:55] <poolie> jam, shall we talk in a bit?
[21:58] <mwhudson> lifeless: two of the tests are really easy to fix, i guess i can look at them in a bit
[22:54] <peitschie> mornin all :)
[23:01] <vila> ouch, now is already tomorrow, night all ;)
[23:03] <peitschie> night vila lol
[23:14] <jelmer> Bonne nuit vila