[00:27] <arraybolt3> tsimonq2: Good news, the cala-settings-ubuntu build failure doesn't appear to be the fault of cala-settings-ubuntu. It's Calamares' fault, due to a CMake file boffo
[00:27] <arraybolt3> so now to find what that boffo is
[00:30] <arraybolt3> found it
[00:32] <arraybolt3> Calamares' CMakeLists.txt includes the module FeatureSummary which includes the command set_package_properties which is used in CalamaresAddTransltions.cmake. But CalamaresConfig.cmake.in (which apparently is called when you do a find_package on Calamares, NOT Calamares' usual CMakeLists.txt) doesn't include that module, and thus the
[00:32] <arraybolt3> set_package_properties call fails in CalamaresAddTranslations.cmake making calamares-settings-ubuntu FTBFS.
[00:33] <arraybolt3> Actually then that may be our fault, perhaps *we* have to include FeatureSummary.
[00:53] <arraybolt3> tsimonq2: around? Could use some debugging help since I'm deep into the weeds with CMake weirdness.
 < 20 mins
 I'm not sure on this one tho since CMake docs don't exactly seem clear
 But I'm happy to be a rubber ducky
[00:54] <arraybolt3> kk
[00:56] <arraybolt3> the thing is that we have libkf5coreaddons-dev as a build dep in debian/control, but CMake is erroring with "The link interface of target "Calamares::calamares" contains: KF5::CoreAddons but the targets was not found."
[00:57] <arraybolt3> I suspect something significant changes in Calamares' CMake config that I don't know about, and that's what's causing this.
[00:57] <arraybolt3> actually I think that's the only thing that makes snse
[00:57] <arraybolt3> *sense
 Something changed. I know a Mantic build of the settings worked when I tried it.
[01:00] <arraybolt3> yeah and it uses alpha2
[01:00] <arraybolt3> so I'mma see what's awry
[01:40] <arraybolt3> well I fixed it sorta
[01:41] <arraybolt3> tsimonq2: I had to hack some pieces of Calamares alpha2's CMakeLists.txt file into our code but it worked. Basically I had to find_package KF5::CoreAddons myself rather than relying on Calamares to do it.
[01:41] <arraybolt3> Which feels a bit hacky...? I mean shouldn't Calamares be finding its own deps?
[01:42] <arraybolt3> I'm unsure because of https://stackoverflow.com/questions/74275590/the-link-interface-of-target-target-contains-dependency-but-the-target-was
[01:42] <arraybolt3> so this may be the right way to do things but I dunno
[01:43] <arraybolt3> `E: calamares-settings-ubuntu-common: shared-library-is-executable 0755 [usr/lib/x86_64-linux-gnu/usr/lib/x86_64-linux-gnu/calamares/modules/pkgselect/libcalamares_viewmodule_pkgselect.so]` new error?
[01:55] <arraybolt3> tsimonq2: pkgselect is your new thing right?
[01:55] <arraybolt3> the thing that allows a minimal installation mode?
[01:56] <arraybolt3> it *is*, ok ok
[01:57] <arraybolt3> tsimonq2: The pkgselect module in its current iteration breaks so many policy rules :P I fear trying to fix them all since I don't know exactly how everything works, so can I get your stamp of approval on uploading this thing Lintian mess and all and let you sort out the things you probably will be better at sorting out?
[01:58] <arraybolt3> this is my Lintian output: https://termbin.com/7ujp
[01:59] <arraybolt3> sigh, who am I kidding, I can figure this out...
[01:59] <arraybolt3> hopefully, with God's help
 LMFAO, I'm so, so sorry XD
 You don't have to make it policy compliant, God already knew it isn't :P
[02:09] <arraybolt3> lol, hey, don't stop me now!
[02:10] <arraybolt3> I already debugged why it was getting installed to /usr/lib/x86_64-linux-gnu/usr/lib/x86_64-linux/gnu/calamares/modules/pkgselect
 https://www.youtube.com/watch?v=cE1FrqheQNI
 jk lmfao
[02:10] <arraybolt3> lol
[02:11] <arraybolt3> if you really want me to not touch it I'm fine with not doing it
[02:11] <arraybolt3> but I think I have some ideas
 Knock yourself out, but once you start untangling the rules file, don't say I didn't warn you :P
 Some of those aren't too bad to fix and some of them are false positives (the noble stuff)
[02:12] <arraybolt3> already there and partially untangled :)
[02:12] <arraybolt3> kc2bez: true
[02:18]  * Eickmeyer yeets @tsimonq2 into #ubuntu-devel for a ping
 not at my IRC client so either wait 40 mins for the IRC logs to update or Telegram me the logs :P
[02:19] <Eickmeyer> Dunno if urgent or not, but it's been waiting there a while, not my ping.
 oiccc
 bandali's right?
[02:20] <Eickmeyer> Yup.
 I'll respond $later, nonurgent, thanks for the heads up
[02:21] <Eickmeyer> np
[02:24] <arraybolt3> tsimonq2: debian/rules untangled \o/
[02:25] <arraybolt3> gonna push this to the archive and to Git, I think it's in good shape. Got it Lintian-clean.
[02:25] <arraybolt3> almost
[02:25] <arraybolt3> there's a no-manual-page warning in there that I think we don't care about
[02:25] <arraybolt3> in fact I'm sure of it, so lemme add a lintian override
 Seems like an override
 Yeah
[02:32] <arraybolt3> alright fixed
[02:36] <arraybolt3> woot, perfectly lintian-clean now after a couple of overrides
[02:40] <arraybolt3> whew! Finally done.
[02:41] <arraybolt3> If this FTBFS all over the place I'm going to be a bit upset :P
[02:44] <arraybolt3> sigh, so far four out of six arches are dead
[02:44] <arraybolt3> amd64 seems to have emerged alive and riscv64 is still grinding
[02:48] <Eickmeyer> You can probably sleep on that one.
[02:48] <arraybolt3> Simon had tried to fix it and it appeared to cause amd64 to fail too but then we found out the total failure was unrelated
[02:49] <arraybolt3> cp -v common/modules/pkgselect/pkgselect.qml debian/calamares-settings-lubuntu/etc/calamares/branding/lubuntu/pkgselect.qml
[02:49] <arraybolt3> 'common/modules/pkgselect/pkgselect.qml' -> 'debian/calamares-settings-lubuntu/etc/calamares/branding/lubuntu/pkgselect.qml'
[02:49] <arraybolt3> cp: cannot create regular file 'debian/calamares-settings-lubuntu/etc/calamares/branding/lubuntu/pkgselect.qml': No such file or directory
[02:49] <arraybolt3> is how it dies on all but amd64
[02:49] <arraybolt3> so for some reason that directory... doesn't exist? Except on amd64?
[02:50] <Eickmeyer> That points to odd build rules usually.
[02:50] <Eickmeyer> Or botched localizations.
[02:51] <arraybolt3> I can't find any arch-specific build rules
[02:53] <arraybolt3> oh wait, I think I know what's going on!
[02:54] <arraybolt3> The module is in calamares-settings-ubuntu-common but the lubuntu/branding directory is in calamares-settings-lubuntu
[02:54] <arraybolt3> ooooooookay...
[02:54] <Eickmeyer> Logs, my friend. Loooooogs.
[02:54] <arraybolt3> https://launchpadlibrarian.net/697995409/buildlog_ubuntu-noble-s390x.calamares-settings-ubuntu_1%3A24.04.4_BUILDING.txt.gz
[02:55] <Eickmeyer> Yeah, when you see that, always check your .install files.
[02:56] <Eickmeyer> override_dh_missing was the clue.
[02:56] <arraybolt3> bUt iT WOrkS on aMd64!!!!!!111
[02:56] <Eickmeyer> Yeah, because arch=all on common.
[02:56] <arraybolt3> wah
[02:57] <arraybolt3> oh
[02:57] <arraybolt3> wait, I get what you mean
[02:57] <arraybolt3> the lubuntu and ubuntustudio packages are arch: all, but the common is arch:any
[02:57] <Eickmeyer> Yeah, I had it backwards, but yes, you're right.
[02:58] <arraybolt3> so basically on all but amd64, that directory doesn't exist because... ba-dum-tiss, that package wasn't build this time
[02:58] <arraybolt3> *built
[02:58] <Eickmeyer> Yep.
[02:58] <arraybolt3> sigh.
[02:59] <arraybolt3> the file in question probably has to be under common for things to work, but common should NOT be fiddling with lubuntu's stuff even if this is lubuntu-specific for now
[02:59] <Eickmeyer> Correct.
[02:59] <Eickmeyer> Means you need to move a file between binary packages. Fun times.
[03:00] <arraybolt3> well that's not too hard, except for common probably needs that file in order to build at all
[03:00] <arraybolt3> lemme find out
[03:00] <arraybolt3> what I need is to say "if on amd64, copy this file"
[03:00] <arraybolt3> unless I can move it without setting off Sbuild War III
[03:01] <Eickmeyer> But remember, common is arch:any.
[03:01] <arraybolt3> even then that would mean having one project split across two packages
[03:01] <arraybolt3> Eickmeyer: Right, so when building on amd64, copy the file. Otherwise, don't copy the file, amd64 did that for you already.
[03:01] <Eickmeyer> So anything that *doesn't have to be compiled* can be in either package.
[03:02] <Eickmeyer> i.e. anything that isn't localized.
[03:02] <arraybolt3> ok so Simon wrote the pkgselect module as its own little mini-project and has it, all of it, under common.
[03:02] <arraybolt3> but then he copies the qml file from common to lubuntu so that Calamares can find it, as part of debian/rules.
[03:03] <Eickmeyer> I see.
[03:03] <arraybolt3> so if I move that qml file, the compiler may scream, but even if it doesn't, now the pkgselect module has bits and pieces in two different packages.
[03:03] <arraybolt3> thus, copy it but only on amd64, thus satisfying all arches
[03:03] <Eickmeyer> Except now we have an open can of worms that only Simon can sort.
[03:04] <arraybolt3> perhaps we need some way to install the QML to a distro-independent location...?
[03:04] <arraybolt3> if Cala even has such a notion
[03:05] <arraybolt3> which it may not
[03:05] <Eickmeyer> I thought common was supposed to take care of the files that were shared between the two flavors, not be complicated spaghetti.
[03:06] <arraybolt3> correct, and this QML file may be shared between multiple flavors if any new flavors pick up Calamares.
[03:06] <arraybolt3> But it has to be in a flavor-specific spot for Calamares' sake IIUC.
[03:06] <arraybolt3> (if any new flavors pick up Calamares - i.e., if you switch back to it, or if I ever make Ubuntu Trinity using TDE, which if I do, I intend on using Cala as the installer)
[03:06] <Eickmeyer> Correct, but -lubuntu should be able to just pick it up via .install and put it where it needs to be.
[03:07] <arraybolt3> the .install file copies, not moves, right?
[03:07] <Eickmeyer> Correct.
[03:07]  * arraybolt3 's brain just uncramped
[03:07] <Eickmeyer> It copies at .deb creation time.
[03:07] <arraybolt3> I thought it moved things and never thought about doing that
[03:07] <arraybolt3> And this is why I'm not a MOTU yet :P
[03:08] <Eickmeyer> It's why -lubuntu and -ubuntustudio just needed breaks/replaces against each other since they'd be installing files to the same location, essentially.
[03:09] <arraybolt3> that makes perfect sense
[03:17] <arraybolt3> alright, if this doesn't fix it, I don't know what will :)
[03:19] <arraybolt3> both arm variants have passed, so I think we're good
[03:19] <arraybolt3> Eickmeyer: Thank you for your help, I probably would not have figured out how to do this properly without you.
[03:34] <teward> wxl: arraybolt3: it's Simon's fault
[03:34] <teward> we can stop the mirror and rename it, then do a reverse mirror
[03:34] <teward> it's not trivial but can be done
[03:35] <teward> but it'll have to be a 'new repo' locally
[03:35] <teward> i know i'm hours late but i've been busy so.  *pushes Simon off the ledge again*
[04:07] <arraybolt3> teward: we unraveled that mess like an hour ago
[04:07] <teward> as i said i'm late
[04:07] <teward> i only just got time to rest so :p
[04:07] <teward> *drops a small flashbang in the chat*
[04:08] <arraybolt3> np, actually more like four hours ago :p just giving you a hard time
[04:08] <arraybolt3> I haven't even gotten to the wallpaper yet, the pkgselect module was HARD to get working right
[04:09] <arraybolt3> Out of curiosity, do I still have the needed access to kick off image builds?
[04:09] <teward> no idea
[04:10] <arraybolt3> I think I need to be part of... /me finds it
[04:10] <arraybolt3> Lubuntu Product Managers, that's it
[04:11] <arraybolt3> Not part of that team anymore though.
[04:12] <arraybolt3> I may never have been part and only gained access during my brief stint on the Council that I had to resign from.
[04:12] <arraybolt3> Can't remember now
[04:12] <teward> yeah Council kind of has god rights to everything Lubuntu
[04:13] <teward> we can talk to the other Council members and see if we want to add you to that.  i think kc2bez is the current lead (tsimonq2 is part of the Ubuntu Release Team now so I have to make sure he can properly split hats xD)
[04:13] <teward> (he knows i'm just raising heck on him for no reason xD
[04:15] <arraybolt3> It would possibly be handy, and I was trained pretty well on how to use that access before.
[13:17] <dacash> Hi. It seems i can't just add ppa:lubuntu-dev/backports in Mantic? apt complains about missing Release file and indeed there is none i can see for mantic. Is it only for LTS?
[13:27] <dacash>  https://pastebin.com/kWMxaMAG , apt-get update with allow-insecure-repos also fails at 404 not found
 /names
 dacash: (Assuming you're still on IRC) we only support 22.04 for Backports :)
 I'm really, really considering whether we should just, yk, do 23.10 Backports as well
 Eickmeyer: Thank you very much for your help :)
 arraybolt3: Very nice, great success :D
 Kay, I re-spun our ISO. This new batch of Calamares settings WILL eat your kittens, and probably your lunch, too. Proceed with caution.
[13:53] <dacash> tsimonq2 that's what i assumed. Tho it's vaguely written "supporting stable versions", Well, i am not using any nightlies )
 That being said, it's the start of all of our new installer functionality, and I tested it, it works, so ;)
 dacash: No worries. I thought I was clear in the announcement but then again, I too am human :)
 @kc2bez arraybolt3 @teward001 wxl this is about a 3-4 hour notice that I'm probably going to be publishing an announcement regarding some preliminary Backports for 23.10. I'll paste the draft link here when I have it. Let's talk about it after I get back from lunch ;)
[17:57] <arraybolt3> tsimonq2: Personally I'm -1 on a Backports for interim releases. That's a lot of extra work, plus if an LTS were only going to live for another nine months we probably wouldn't bother backporting to it.
[17:59] <arraybolt3> Interims are stable snapshots to get newer stuff before the next LTS. They're not rolling releases. The appeal of Backports for LTS is there because otherwise you use an old version of LXQt for long. But for interim, idk, I'm just not seeing a sufficient return on investment there.
[17:59] <arraybolt3> Perhaps I'm wrong though :p
 I've had no less than three media outlets and a half a dozen users ask/complain about it
 I'll highlight that in the announcement
 Usually I'm -1 as well... this one it really feels like we kinda have to
[18:10] <arraybolt3> *shrug* I mean that makes sense, I guess.
[18:13] <arraybolt3> One thing we should keep in mind though is, backporting LXQt means there's less incentive to move to the next release when it comes out.
[18:14] <arraybolt3> I.e., we're encouraging people to use their existing installs of interim releases when people need to upgrade to newer releases to stay secure.
[18:15] <arraybolt3> Not sure if we want to do that, we might see an increase in "hey why won't my system upgrade" support requests stemming from "your OS is EOL, you need to upgrade ASAP".
[18:16] <arraybolt3> For LTS we stop backporting once the new LTS is out, so there's a whole year (or three depending on how you look at it) to get tired of your LXQt and upgrade. Interim doesn't provide that advantage.
 Hi —sorry late reply —was away in Berlin past 7days just got home and yes will resume testing Lubuntu and all the other flavours.. (re @tsimonq2: @guiverc @Leokolb @Roberalz etc. I'd appreciate some testing help with Backports Staging/Backports (if you see this later) :) ^^^^)
 Thank you very much Leó! I hope all is well with you. (re @Leokolb: Hi —sorry late reply —was away in Berlin past 7days just got home and yes will resume testing Lubuntu and all the other flavours..)
 All is well ..thanks for asking! (re @tsimonq2: Thank you very much Leó! I hope all is well with you.)
 @tsimonq2 sorry missed out on some messages - what was it you needed help testing? Might be able to run a few tests tomorrow..
[20:07] <tsimonq2> https://notes.lubuntu.me/JfofmArESxmV8XwcLxV5UQ#
[20:13] <arraybolt3> tsimonq2: left a note, also I like how you got around the issue of EOL release problems.
[20:17] <tsimonq2> arraybolt3: Right, exactly. Strong message saying "upgrade or you shall perish." :P
[20:18] <arraybolt3> I have no further objections to the interim backports, and all the ones I had are dealt with, so I'm happy with it.
[20:20] <tsimonq2> Thank you.
[20:22] <arraybolt3> (I mean, it's not like I exactly get a vote since I'm not on the Council :P Thanks for taking into consideration what I was thinking too.)
[20:27] <tsimonq2> Of course :)
[20:34] <tsimonq2> https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/433283
[20:35] <tsimonq2> https://answers.launchpad.net/launchpad/+question/708471
[20:36] <tsimonq2> https://answers.launchpad.net/launchpad/+question/708471
[20:36] <tsimonq2> whoops
[20:40] <arraybolt3> Can't say no to free cloud storage :D
[20:44] <arraybolt3> Alright, so *today* I'mma try wallpaper stuff.
[20:45] <arraybolt3> tsimonq2: I know you were trolling with the retro wallpaper idea... but what if I used one of them for the placeholder SDDM screen?
[20:46] <arraybolt3> I could add a watermark like "Lubuntu Noble - DEVELOPMENT EDITION" somewhere to make it obvious it's a placeholder and also to act as a warning for those brave souls that choose to use Noble now other than our testers.
[20:54] <tsimonq2> Sure, heh. As long as it looks pretty under a variety of resolutions, lol.
[20:56] <arraybolt3> https://i.imgur.com/D4W366u.png
[20:56] <arraybolt3> that might even look good as a wallpaper
[20:56] <arraybolt3> aspect ratio wasn't as much as a problem as I expected
[20:57] <arraybolt3> also the numbat picture: https://i.imgur.com/oCQlcSp.jpg
[21:28]  * arraybolt3 really wishes QEMU supported drag-n-drop files without needing SPICE
[21:42] <tsimonq2> https://launchpad.net/~lubuntu-dev/+archive/ubuntu/backports-mantic-staging/+packages
[21:42] <tsimonq2> Just playing a game of chicken with the publisher.
[21:42] <tsimonq2> Don't worry, I have a local, hacky retry script. :P
[21:43] <tsimonq2> I would imagine it'll be another couple long publish runs before we fully release this thing.
[21:43] <tsimonq2> I'll just do a smoke test... but that's about it, lol.
[21:43] <tsimonq2> Also, I just uploaded some extra themes to both the PPAs that will be installed (but not enabled) by default. Like 300 kb. I think that's doable. :P
[21:56] <arraybolt3> tsimonq2: any idea what the copyright info is on that old wallpaper I linked earlier?
[21:56] <tsimonq2> arraybolt3: *shrug*
[21:57]  * arraybolt3 rummages through Phab to find it
[21:58] <arraybolt3> oh wow, we have a data loss situation in Phab
[21:58] <arraybolt3> something awry with AWS looks like
[21:58] <arraybolt3> teward: !needhelp
[21:59] <tsimonq2> arraybolt3: Email him for an instant response, at his personal email :P
[21:59] <arraybolt3> not that urgent, just something's Not Right
[21:59] <tsimonq2> arraybolt3: With big bold letters "THE NUKES HAVE BEEN UNLEASHED"
[21:59] <tsimonq2> XD
[21:59] <arraybolt3> tsimonq2: where did you pull that wallpaper from at first?
[21:59] <teward> #InvalidSummons
[21:59] <arraybolt3> teward: ohai
[21:59] <arraybolt3> DM incoming
[22:00] <teward> you owe me coffee if yer gonna be summoning meout of the blue :P
[22:01] <arraybolt3> don't we always ping you when infra throws a fit? :P
[22:02]  * tsimonq2 throws rocks at teward
[22:04] <tsimonq2> teward, Eickmeyer, RikMills: also FYI in case you fail to read logs, default PPA size is now 8 GB
[22:04] <arraybolt3> anyway, PSA: All file access within repos on Phab is entirely b0rked. Every repo, every file, that I try to access, gives an esoteric AWS-related error.
[22:04] <tsimonq2> \o\ /o/ \o/
[22:05] <arraybolt3> So for now, I have no clue what license or copyright one of these files is under :P gonna have to dig through oldreleases to find it and hope the copyright file is valid
[22:05] <tsimonq2> I'm 75% sure it's Rafael Laguna but wxl would know.
[22:12] <tsimonq2> https://9to5linux.com/lxqt-1-4-desktop-arrives-for-lubuntu-23-10-users-heres-how-to-install-it
[22:12] <tsimonq2> This current build cycle has the vast majority of packages, which also means the longest publisher run.
[22:13] <tsimonq2> As soon as it's all published in Backports Staging, I'll be smoke testing it, then shipping it right out the door.
[22:14] <arraybolt3> tsimonq2: see Matrix DM when you get a chance
[22:30] <arraybolt3> welp, I found the 10.04 package for lubuntu-artwork, and it has the (almost) right wallpaper... BUT... the copyright file is malformed so I'm not sure who owns that wallpaper's copyright still :P Looks like Rafael Laguna is most likely though.
[22:35]  * arraybolt3 has the joy of importing a CC-BY-3.0 license into a package :-/
[22:39] <arraybolt3> Aaaaaand... I imported BY-SA-3.0 rather than BY-3.0 XD
 Nice job XD
 Use sed/awk/regex
 :P
[22:42] <arraybolt3> just finished using Vim
[22:43] <arraybolt3> Those CC licenses are LOGN
[22:43] <arraybolt3> *LONG
[22:50] <arraybolt3> sigh, looking through Lubuntu's Wikipedia I miss LXDE.
[22:51] <wxl> why????
 ^^^^^^
 XD
[22:51] <arraybolt3> wxl: Fancy 3d-looking buttons :P
[22:51] <arraybolt3> and a less "flat" UI
 (phab is down while i shove it in a sandbox)
 (and will stay down even in the sandbox env)
[22:52] <arraybolt3> I get that flat user interfaces are the present and probably the future but I miss the 3d Everything world we had for a bit there.
[22:52] <wxl> arraybolt3: that's no reason to miss lxde.
[22:52] <wxl> but
[22:52] <wxl> if you really want 3d looking buttons, make yourself a theme
[22:53] <arraybolt3> I guess I could make one that looks suspiciously LXDE-like :P
[22:53] <arraybolt3> I loved its overall look and feel too
[22:53] <wxl> sounds like you care enough about looks that maybe you should be our new art lead XD
[22:53] <arraybolt3> lol, I thought that was you right now
 I already threatened wxl with it, he threatened me with making Fritz the QA lead so I backed down XD
[22:55] <arraybolt3> oh yikes :P
[22:55] <wxl> my problem is i don't care enough to be the art lead
 *reassigns tsimonq2 to the salt mines for reasons*
[22:56] <wxl> that and i have zero graphic design skills
[22:56] <wxl> which is more than the negative skills simon has but you get the idea
[22:56] <arraybolt3> 🤣
[22:57] <teward> i have 2.56% artistic skills xD
[22:57] <teward> so i mean i'm not a good fit either
[22:57] <teward> but mleh
[22:57] <teward> *sips coffee*
[22:57] <wxl> 2.56 > 0, sooooooo
[22:57] <teward> 2.56 < 50% competency which is bare minimum so
 How far in the negative am I? XD
[22:58] <arraybolt3> I'm decent with some things (especially Gimp fractals and basic Inkscape stuff), but my mom is breathtakingly good with a lot of stuff.
[22:58] <teward> tsimonq2: -500000000000%
[22:58] <teward> which is why i sent you to the salt mines
[22:58] <teward> go fix the autodrills
[22:58] <arraybolt3> She made the Kinetic and Lunar wallpapers, I'm probably going to talk her into making the Noble one too
[22:58] <teward> they run on Ubuntu 8.04 and COBOL
 XD : https://matterbridge.lubuntu.me/9bab9806/file_10122.jpg
[22:58] <arraybolt3> (I got to make the Lunar SDDM screen though :D)
 file image.png too big to download (2373886 > allowed size: 1000000)
 Can't see it pastebin it
[22:58] <teward> #TooLarge
[22:59] <wxl> oh whatever
 No I wanna see it pastebin it XD
[22:59] <wxl> it's on matrix go look there
[22:59] <arraybolt3> wxl: what is it, MacNCheeseBook?
[22:59] <arraybolt3> (I can see it and have no idea what to even name that)
[22:59] <wxl> https://i5.walmartimages.com/asr/4342f3f0-5f24-432a-8e41-9b7ebc51fe96_1.9596121f40a561f932002ba9554fc001.jpeg
 HAHAHAHAHAHA
 OMGGG
[23:00] <arraybolt3> (in reply to Simon's squiggly bird)
[23:01] <wxl> note he didn't say anything like "no i wouldn't be that bad"
 No I think I'd be worse tbh XD
[23:02] <wxl> hahahahaha
[23:02] <arraybolt3> Uploading new wallpaper and SDDM screen packaging to the archive
 Do ittt
[23:03] <arraybolt3> also lubuntu-artwork packaging is a hot mess right now, BUT I didn't leave it in any worse shape than it started, I think.
[23:03] <arraybolt3> I'll do a packaging cleanup on it hopefully soon.
[23:04] <arraybolt3> PSA: if you upgrade and your SDDM screen and wallpaper are solid black, I botched a symlink, feel free to force me to brew your virtual coffee for the remainder of next week.
[23:04] <arraybolt3> (I think I got the symlinks right though.)
[23:04] <arraybolt3> (I looked at the existing ones with ls -l and remade them the same way.)
[23:04]  * genii twitches
 LGTM, ship it. (re @tsimonq2: XD)
 TBF it is better than mine. At least you can make out that it is a bird. XD
 LMFAO
[23:16] <teward> genii: go get me a coffee
[23:17] <teward> :P
[23:17]  * genii breaks out the Aeropress and Death Wish coffee for teward
[23:17] <teward> thank you kindly *takes the caffeine*
[23:20] <arraybolt3> I actually wanted to do a UI refresh with the Lunar cycle, and I want to get Breeze out of Lubuntu *this* cycle because it's caused us issues before.
[23:20] <arraybolt3> So I might try some theming overhauls and see what y'all think.
[23:21] <arraybolt3> For now though, tell https://launchpad.net/ubuntu/+source/lubuntu-artwork/24.04.1 to hurry up and build so you can install it and tell me what you think :P
[23:21] <tsimonq2> Let us know what you find!
[23:25] <arraybolt3> I'm brave, so I just did an encrypted XFS installation of Lubuntu XD
[23:35] <arraybolt3> QTerminal is still broken :(
[23:36] <arraybolt3> sigh, I have unfortunate word placement
[23:36] <arraybolt3> https://i.imgur.com/BJaN7VK.png
[23:36] <arraybolt3> shoulda put it at the upper-right
[23:37] <arraybolt3> oh well, version numbers are cheap, yadda yadda
[23:37] <arraybolt3> I really should have tested before uploading it though
[23:39] <tsimonq2> Just manually install the package from proposed... :P
[23:39]  * tsimonq2 dinner


[09:46] <sridher> Error:  worker: exited "environ-provisioner": failed to process updated machines: cannot start machine 1: no matching tools available
[13:29] <Tug> Hi, I have a few questions about customizing a deployment of mongodb with mongodb charm
[13:29] <Tug> Like what would be the recommanded way to add authentication? Should I clone the mongodb charm, include the keyFile in it and modify the install hook to copy the file to the right place?
[13:40] <hazmat> Tug, keyfile being ssl?
[13:40] <hazmat> Tug, ideally that would be config
[13:40] <hazmat> Tug, but yeah.. in general fork, modify & test, submit pull request/merge proposal
[13:41] <Tug> hazmat, yeah ssl
[13:41] <Tug> hazmat, you mean modify the config-changed hook ?
[13:42] <hazmat> Tug, yeah
[13:42] <hazmat> Tug, and config options on the charm
[13:43] <hazmat> Tug, config.yaml
[13:43] <Tug> hazmat, yeah add a new config option for the path of the file for instance right ?
[13:44] <hazmat> Tug, for the contents of ssl cert / ssl key / ssl ca
[13:44] <hazmat> Tug, the config-hook drops those onto disk, and configures mongodb to use ssl if their present..
[13:44] <Tug> hazmat, the content directly into the config.yaml you think ?
[13:45] <hazmat> Tug, no.. config.yaml is the schema, but yeah.. the service config would have the ssl key/cert config..
[13:46] <Tug> hazmat, ok I see. Well why not. Not sure how it's going to render on juju-gui :)
[13:46] <hazmat> Tug, not to pretty, but should be fine, just gets collapsed into a text field  i've done this with some of the other charms
[13:47] <Tug> Ok thx, I'll try this then ;)
[13:47] <hazmat> Tug, there's one ancillary alternative  which is having the mongodb service act as its own ca, but that implementation is a bit more advanced (have to replicate the ca files across replicaset and potentially to shard servers).
[13:48] <hazmat> the config options for key/cert/ca usage is pretty straightforward
[13:49] <Tug> hazmat, Mmm I see, but I guess I would have to play with openssl to have this right ?
[13:50] <Tug> and add multiple hooks
[13:50] <hazmat> Tug, don't worry about the service being its own ca.. its complicated.. there's some helpers in charm-helpers..
[13:50] <Tug> ok hazmat
[13:51] <lazyPower> hazmat: ping
[13:51] <hazmat> Tug, the config option around ssl is pretty straight forward.. add additional options to config.yaml for key/cert/ca .. detect those in config-changed and configure mongodb for ssl.. also probably one more.. which is for clients to pass the ca
[13:51] <hazmat> unless its a system recognized ca
[13:51] <hazmat> lazyPower, pong
[13:51] <hazmat> lazyPower, yeah.. i'm on it :-)
[13:51] <hazmat> lazyPower, re DO
[13:51] <lazyPower> hazmat: I did some work on that api parser actually
[13:52] <hazmat> lazyPower, oh?
[13:52] <lazyPower> its made me realize how weak i am with regex :P
[13:52] <hazmat> lazyPower, api parser?
[13:52] <lazyPower> oh sorry, context
[13:52] <Tug> hazmat, out of curiosity, do you have a link to the charm-helpers you were talking about ?
[13:52] <lazyPower> i'm working on exact matches so we dont match their prefab app boxes.
[13:52] <lazyPower> eg: 12.04 dokku
[13:52] <hazmat> lazyPower, if you mean jujuclient.. rog has something that will use parse the golang client api to json
[13:53] <mbruzek> Hello Tug
[13:53] <hazmat> lazyPower, ah.. so i'm not quite sure what the best option is.. i was thinking of a unit test that verified all the default images chosen
[13:53] <lazyPower> i want to abstract away the list if i can, because it wont scale. They deprecate the vanilla images pretty often.
[13:53] <hazmat> lazyPower, and then tossing it into ci
[13:53] <Tug> Hi mbruzek
[13:53] <hazmat> lazyPower, basically i want to avoid clients having to do the api call, call its time consuming, but still keep constant check that the images are valid..
[13:53] <mbruzek> Tug, sorry I was catching up I see that hazmat answered your questions.
[13:54] <hazmat> it does sort of assume that clients get updated when images are invalid
[13:54] <hazmat> lazyPower, i just pushed a quick change that gives a nicer error message then just the traceback on api error (ie tell the user what the do said was in error)
[13:54] <lazyPower> awesome
[13:54] <lazyPower> do i need to rebase? or are you going to handle that?
[13:55] <hazmat> lazyPower, new output is http://pastebin.ubuntu.com/7299388/
[13:55] <hazmat> lazyPower, i'll handle.. i'm adding support to the mini do client for image fetching so i can add a unit test to verify the default image selection, and then merge your mp
[13:55] <lazyPower> + 1 on the new response message.
[13:55] <lazyPower> ack. Thanks for taking a look
[13:56] <hazmat> lazyPower, np.. thanks for the mp
[13:57] <hazmat> Tug, http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/ssl/service.py
[13:57] <hazmat> Tug, its used in a few charms for generating server and client certs for mutual auth with tls
[13:58] <Tug> thank you hazmat
[13:58]  * hazmat makes a note to add some charm-helper docs
[13:58] <Tug> yeah it's not so simple but it might not be impossible to adapt it for mongo
[13:59] <Tug> I'll have a look
[14:09] <hazmat> lazyPower, yeah.. i was hoping to avoid the image check on every plugin invocation. its only about 1.5s though..  so probably worthwhile to just bake it in.
[14:09] <lazyPower> hazmat: would probably be prudent to cache the response and expire every N hours?
[14:10] <lazyPower> unless it reaches a 404 on image creation, then refetch, THEN throw exception?
[14:10] <hazmat> lazyPower, that sounds pretty reasonable
[14:10] <hazmat> albeit more complexity
[14:10] <lazyPower> i agree that it adds complexity but it enhances the UX
[14:11] <hazmat> lazyPower, the issue is that we get user images/backups as well in that api call
[14:11] <hazmat> yeah
[14:11] <lazyPower> yeah, i was considering that.. i wonder if this is where we dont explore an opportunity presented by other mediums, and interrupt with an interactive list and let the user choose
[14:12] <lazyPower> that deviates pretty far from the vanilla juju ux, but makes sense
[14:13] <hazmat> argh.. battery dying.. back in a bit
[14:19] <lazyPower> sinzui: re: https://bugs.launchpad.net/juju-core/+bug/1309805 - shall i re-open the bug with my output or file a new bug?
[14:19] <_mup_> Bug #1309805: LXC / Local provider machines do not boot in 1.18 / 1.19 series <juju-core:Incomplete> <https://launchpad.net/bugs/1309805>
[14:20] <fro0g> will juju support spot instances?
[14:22] <lazyPower> fro0g: on AWS correct?
[14:25] <sinzui> lazyPower, The bug isn'
[14:26] <sinzui> t closed. There is no information for en gineer to reproduce the bug and make a fix
[14:26] <lazyPower> sinzui: ok, i was asking because it looked like a community member was trying to help by adding their output and it wasn't helping.
[14:26] <lazyPower> I'll attach machine agent logs + commands. I can reproduce this on 2 systems
[14:26] <sinzui> lazyPower, The other error in the bug is not about tools
[14:26] <sinzui> thank you lazyPower
[14:27] <lazyPower> np, thanks for taking a look sinzui
[14:34] <lazyPower> has anyone else bootstrapped on hpcloud today? Looks like i'm seeing a new bug here as well: https://bugs.launchpad.net/juju-core/+bug/1310645
[14:34] <_mup_> Bug #1310645: Bootstrapping on HPCloud fails with package Hash Sum Mismatch <hp-cloud> <juju-core:New> <https://launchpad.net/bugs/1310645>
[14:38] <sinzui> lazyPower, abentley reports the same issue on joyent and azure
[14:38] <lazyPower> ack. looks like monday hasn't lost its edge
[14:44] <fro0g> lazyPower: yes
[14:45] <lazyPower> fro0g: i'm not aware of any active efforts to support spot instances. You can request spot instances and work them into your environment with the manual provider - but i do not believe that juju supports provisioning spot instances as a provider option.
[14:47] <lazyPower> sinzui: attached logs to https://bugs.launchpad.net/juju-core/+bug/1309805
[14:47] <_mup_> Bug #1309805: LXC / Local provider machines do not boot in 1.18 / 1.19 series <juju-core:Incomplete> <https://launchpad.net/bugs/1309805>
[14:47] <lazyPower> i have mbruzek doing the same
[14:48] <fro0g> lazyPower: ok
[14:48] <sinzui> thank you lazyPower
[14:48] <fro0g> lazyPower: thanks!
[14:49] <lazyPower> Np problem fro0g. if you'd like to see it as a feature, i would open a feature request against juju-core. I can't promise anything above the core-team will take a look at it and triage it appropriately. but you'll be the first to know if it lands by doing so.
[15:01] <mbruzek> Hey guys it seems I have got past the "pending" problem on Trusty, just now.  Talking about https://bugs.launchpad.net/juju-core/+bug/1309805  lazyPower and cory_fu
[15:01] <_mup_> Bug #1309805: LXC / Local provider machines do not boot in 1.18 / 1.19 series <juju-core:Incomplete> <https://launchpad.net/bugs/1309805>
[15:01] <lazyPower> mbruzek: randomly started working or did you do something specific?
[15:02] <mbruzek> I destroyed my environment, ran the cleanup script that removed lxc containers.  But I think what solved it was running juju sync-tools before my bootstrap
[15:02] <mbruzek> I am able to get a charm to started this morning.
[15:02] <lazyPower> ah, excellent. Let me try syncing tools and trying again
[15:02] <mbruzek> I believe it was due to the juju sync-tools, can lazyPower  or cory_fu  confirm?
[15:03] <cory_fu> How do I add the dev ppa to get juju 1.19?
[15:03] <lazyPower> cory_fu: sudo add-apt ppa:juju/devel
[15:03] <lazyPower> s/add-apt/add-apt-repository
[15:03] <cory_fu> Ah, right, of course.  Thanks
[15:04] <mbruzek> I may have claimed victory too soon guys, I got the "ubuntu" charm to start, but my other tests are still in pending.
[15:04] <mbruzek> Try a charm other than "ubuntu"
[15:04] <mbruzek> please
[15:04] <lazyPower> ack, i'll deploy a bundle
[15:05] <lazyPower> however it appears my ubuntu charm is still pending... and i'm geting the same output in machine-0.log
[15:08] <mbruzek> I got the ubuntu charm to start...because that one is trusty ?
[15:09] <lazyPower> mbruzek: it didn't appear to fix it. bundle:mediawiki/single is pending. with the same scrolling log output
[15:09] <sinzui> mbruzek, lazyPower do either of you specify the default-series in your env?
[15:10] <mbruzek> no I do not
[15:10] <lazyPower> sinzui: i have specified precise in my local env config, yes.
[15:10] <sinzui> I do, I   local:
[15:10] <sinzui>     type: local
[15:10] <sinzui>     default-series: precise
[15:10] <hazmat> lazyPower, fwiw. i eschewed the regex .. http://pastebin.ubuntu.com/7299864/
[15:11] <lazyPower> hazmat: nice approach. I didn't think to look at the public: flag in the json output
[15:11] <lazyPower> s/flag/property
[15:12] <lazyPower> does it match on their single-click-deploy appliations? wrt dokku-wiki and gitlab? That was my other concern was matching on those and potentially launching an application along with juju.
[15:12] <lazyPower> oh line 10 takes care of that. awesome. great work hazmat
[15:13] <mbruzek> sinzui, I am setting that and testing it now
[15:15] <lazyPower> ah i apologize i jumped the gun, i set default-series on everything but local provider.
[15:20] <mbruzek> sinzui, That seems to work for me
[15:21] <mbruzek> sinzui, I have found a new problem however, and I need guideance on where to open it against.
[15:21] <cory_fu> Setting the default series as trusty or precise?
[15:21] <mbruzek> precise
[15:21] <mbruzek> I don't think local was uploading the tools for precise
[15:21] <sinzui> mbruzek, interesting. does : trusty work?
[15:21] <lazyPower> sinzui: are a lot of these problems related to the fact that we now have 2 LTS's to track? Where default-series wasn't mandatory before, but is now?
[15:21] <mbruzek> sinzui, I was able to deploy tomcat and ubuntu
[15:22] <mbruzek> sinzui, Both charms deploy.  tomcat failed in the install hook doing a apt-get update.
[15:22] <mbruzek> I sshed to ubuntu charm and ran apt-get update and that fails in the same way.
[15:22] <sinzui> mbruzek, my logs claim they were upload both tools...and since I know I don't have precise, It should have gone to the network to get them...there is no guarantee that the series and archs have the same tools
[15:23] <lazyPower> oh snap, that did appear to fix it. bundle:mediawiki/single is now deploying as expected.
[15:23] <sinzui> lazyPower, In my release notes for 1.18.1 I recommended default-series because I was getting a lot of issues that were caused by ambiguous envs
[15:24] <lazyPower> sinzui:  i remember that email now that you call attention to it. Sorry for not heeding the advice earler. Do we have default-series being added to the boilerplate environment config for new users now? We should probably add a ticket for that if not.
[15:25] <sinzui> lazyPower, I have not seen it yet. I think it is the sane thing to do.
[15:26] <mbruzek> sinzui, I believe apt-get update is failing for trusty charms.  What component would that be against?
[15:26] <lazyPower> mbruzek: is the output the same as i linked you earlier about a hash-sum mismatch?
[15:27] <mbruzek> Yes
[15:27] <sinzui> mbarnett, That's ubuntu, not charms or juju
[15:27] <lazyPower> mbruzek: elmo pushed a fix for that, its propigating - i can confirm it resolved my issues on hp-cloud....
[15:27] <cory_fu> lazyPower: I am getting the hash-sum mismatch on local, now, yes
[15:27] <lazyPower> however that was a precise host - do you know if that fix was pushed for trusty as well sinzui?
[15:28] <sinzui> mbruzek, lazyPower I believe the same package in in both series
[15:28] <cory_fu> And the local-machine that go the error was precise... Is there a way I can... encourage the propagation?
[15:29] <lazyPower> cory_fu: speak with a stern voice and shake your finger at it profusely
[15:29] <cory_fu> lol
[15:29] <cory_fu> I meant, is there any caching done by the LXC that I could explicitly expire?
[15:29] <lazyPower> its not an image update, it was a fix server side on the SUM file that apt uses for CRC checking.
[15:43] <mbruzek> so lazyPower I don't understand how the fix will be delivered.  If it is fixed on the server side how did I get it just now?
[15:44] <lazyPower> mbruzek: apt fetches the CRC during apt-get update and validates teh package list against that CRC file. It wasn't something that was pushed out to clients. So when it propigates to your apt mirror it will be available to you.
[16:22] <jose> lazyPower: that bug in wordpress is fixed, MP is up
[16:28] <tvansteenburgh> when amulet deploys a charm, where does it get the config.yaml from?
[16:28] <tvansteenburgh> i have a config.yaml that i've updated on disk, but amulet isn't using it
[16:29] <jose> tvansteenburgh: afaik it's the config.yaml file that's on the charm, but you can specify options by doing d.configure('servicename', {'option': 'value', 'option': 'value'})
[16:30] <tvansteenburgh> jose: that's what i assumed too, but that's not what i'm seeing.
[16:31] <jose> tvansteenburgh: oh, I'm not sure if it deploys the local charm, I think it gets it from the charm store
[16:32] <tvansteenburgh> well i have JUJU_TEST_CHARM set, which is supposed to make it deploy the local copy, but i'm not sure if it's working or not
[16:32] <tvansteenburgh> i guess i'll continue my debugging there
[16:33] <jose> for now I suggest you go ahead and set the options where needed
[16:34] <lazyPower> tvansteenburgh: when you run the test from the command line: eg ./100-deploy - it uses the charm store, if you're using the testing harness charm test -e <environment> it will deploy teh local charm.
[16:35] <lazyPower> not sure if that helps or answers the question but i thought maybe it would.
[16:35] <lazyPower> jose: woot. if its in the queue mbruzek will be taking a look at it.
[16:36] <jose> awesome, then :)
[16:42] <marcoceppi> jose: lazyPower we're mailing the list in a little bit, but future doc contributions should be done in the src/en/ markdown files
[16:42] <jcastro> marcoceppi, I am confused
[16:42] <jcastro> https://github.com/juju/docs/blob/master/src/en/charms-constraints.md
[16:42] <jcastro> juju bootstrap --constraints "cpu-power=0 cpu-power=0 mem=512M"
[16:42] <jcastro> is entirely correct in the MD
[16:42] <jose> marcoceppi: ack, will re-do my stuff and commit as soon as I get home
[16:43] <lazyPower> marcoceppi: thanks for the update. I'll keep that in mind when accepting PR's.
[16:43] <jcastro> jose, I'm fixing it now no worries
[16:43] <marcoceppi> lazyPower: very soon the htmldocs will be gitignored, so it won't be a problem, but fyi until then
[16:43] <jcastro> but from looking at the markdown source, it appears to be correct?
[16:43] <marcoceppi> jose: he removed cpu-power from the output
[16:43] <jose> in university I have only found a workaround to connect to IRC, so I can't do much
[16:43] <marcoceppi> jcastro: ^^
[16:44] <lazyPower> jose: sshuttle is your friend
[16:44] <jose> jcastro: thank you :)
[16:44] <jcastro> oh oh
[16:44] <jcastro> so cpu-power=0 doesn't work anymore?
[16:44] <lazyPower> jcastro: it was duplicated. that was the fix
[16:44] <jcastro> I could have sworn we used to not have it, and then at some point had to explicitly say 0
[16:44] <rick_h_> jcastro: there's cpu-power and cpu-cores
[16:44] <jose> marcoceppi, jcastro: I removed one of the cpu-power=0, it's doubled
[16:45] <jcastro> oh!
[16:45] <jcastro> now I see it'
[16:45] <rick_h_> jcastro: that had two cpu-powers vs one of each
[16:45] <rick_h_>  juju bootstrap --constraints "cpu-power=0 cpu-cores=0 mem=512M"
[16:45] <rick_h_> would be the better update perhaps?
[16:46] <jose> I can confirm "cpu-power=0 mem=512M" works, no need to specify cpu-cores
[16:46] <jose> lazyPower: sshuttle?
[16:46] <rick_h_> ok cool
[16:46] <lazyPower> jose: https://github.com/apenwarr/sshuttle
[16:46] <jcastro> lazyPower, new PR with fix incoming
[16:46] <jose> lazyPower: dns servers don't work here and if i set <IP_ADDRESS> I cannot connect :P
[16:47] <lazyPower> jose: sshuttle creates a VPN tunnel to your host of choice - so you could route all your traffic around whatever barrier you've got via ssh. Assuming you can ssh out.
[16:47] <jose> I cannot SSH out :P
[16:47] <lazyPower> but id ont know what your universities network policy is, so YMMV on if you're being a trouble maker
[16:48] <jose> nah, sysadminds are good with me messing with networks, I'm going to try with a personal VPN later on
[16:48] <jose> for now, /me runs to have lunch and take an exam
[16:48] <jcastro> lazyPower, don't accept my PR yet, let me see what rick's does
[16:49] <renier> Hi. within a hook, would there be a magic variable that has the name of the charm?
[16:49] <jcastro> rick_h_, yours is more explicit so I think I'll do that
[16:50] <rick_h_> jcastro: up to you. I like the shorter, but was trying to get at what I think the original line was meant to be/demonstrate
[16:51] <lazyPower> ack
[16:51] <jcastro> yeah longer, but better example
[16:53] <jcastro> lazyPower, I can confirm rick's modifications to the command still  fires up a t1.micro, so we're all set.
[16:54] <lazyPower> woo awesome
[16:54] <jcastro> jose, oh, I only fixed your accepted PR btw
[16:56] <jcastro> OMG
[16:56] <jcastro> arosales, did you add the joyent page to every file by hand?
[17:03] <jose> jcastro: ok, will fix as soon as I'm homr
[17:10] <arosales> jcastro: no, the make did that for me.
[17:10] <jcastro> oh ok
[17:10] <sinzui> lazyPower, mbruzek : I reposted the my default-series recommendations: http://curtis.hovey.name/2014/04/21/working-with-ubuntu-12-04-precise-and-14-04-trusty/
[17:10] <jcastro> arosales, I did another submission if you want to use that one
[17:11] <arosales> jcastro: for the joyent provider?
[17:11] <jcastro> yeah
[17:11] <lazyPower> sinzui: reblogging now. thanks for this!
[17:20] <jcastro> arosales, yeah
[17:20] <jcastro> https://github.com/juju/docs/pull/70
[17:21] <jcastro> arosales, that's how you add a page, we can either fix yours or accept that one, up to you
[17:21] <jcastro> <--- lunch
[17:28]  * arosales looking
[17:30] <arosales> jcastro: can you help me understand what is incorrect about https://github.com/juju/docs/pull/68 ?
[17:37] <renier> hi, arosales. think he means that you added the html generated page. I'm guessing only the markdown is needed
[17:38] <jcastro> yeah, but marcoceppi's .gitignore will fix that
[17:38] <jcastro> arosales, basically, we don't generate the pages, the build system does
[17:39] <jcastro> arosales, but we'll fix it so the generated html is ignored
[17:43] <renier> hey, so anyone using http://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-juju-vagrant-disk1.box lately? it's giving errors when bootstrapping
[17:43] <renier> what are people using here for a vagrant jujubox?
[17:43] <jcastro> renier, I just reported it's brokeness to the maintainer today
[17:43] <utlemming> renier: do you have a paste for that?
[17:43] <jcastro> but yeah, something changed in 1.18 that we need to fix and regen the boxes
[17:44] <jcastro> utlemming, lazyPower was the one trying them out
[17:44] <jcastro> utlemming, I think for starters it needs to explicitly install juju-local
[17:44] <jcastro> which was causing some pain
[17:44] <renier> jcastro, something changed in juju 1.18 you mean, or another piece?
[17:44] <renier> utlemming, I'll get that for you
[17:44] <jcastro> renier, I believe 1.18
[17:45] <renier> ok, yea, juju version 1.18.1 in the box
[17:48] <lazyPower> utlemming: do you need anything from me re: juju box investiation?
[17:49] <lazyPower> i can send logs and the vagrantfile if you'd like. what i saw was some missing components, and after installing them manually i ran into other issues with regard to missing a default-series in the environments.yaml (which we sussed out this morning)
[17:49] <cory_fu> Is it possible for a charm's config-changed hook to tell if it's being run as part of charm upgrade vs just a config-set?
[17:49] <lazyPower> cory_fu: set a sentinel file in $CHARM_DIR and act on it, when finished acting, rm said sentinel file?
[17:50] <cory_fu> Not sure I understand
[17:51] <lazyPower> cory_fu: during upgrade-charm at the end touch $CHARM_DIR/.upgrading
[17:52] <lazyPower> look for if [ -f $CHARM_DIR/.upgrading]; then   #do stuff rm $CHARM_DIR/.upgrading fi
[17:52] <lazyPower> theres your idempotency guard against running said code if being called directly after upgrade-charm
[17:53] <cory_fu> Ah, I see
[17:56] <arosales> renier: Hello, and thanks for the feedback :-)
[17:56] <arosales> jcastro: understood, I think all your pull (re: 70) is missing the png
[17:56] <jcastro> I just fixed it
[18:00] <tvansteenburgh> bzr branch
[18:01] <tvansteenburgh> wrong win
[18:04] <lazyPower> tvansteenburgh: bzr: ERROR: command 'branch' requires argument FROM_LOCATION
[18:04] <tvansteenburgh> so i finally figured out how to get my amulet tests working
[18:04] <lazyPower> woo!
[18:05] <tvansteenburgh> i had to bzr ci my local changes before amulet/juju-deployer will use them
[18:05] <arosales> jcastro: +1 for your commit then
[18:05] <marcoceppi> tvansteenburgh: yeah
[18:05] <tvansteenburgh> seems not good
[18:05] <marcoceppi> that should be addressed in the next rlease of amulet
[18:05] <marcoceppi> it's a known issue
[18:05] <tvansteenburgh> ok cool
[18:06] <renier> utlemming, https://gist.github.com/renier/11150973
[18:06] <tvansteenburgh> so now i have a patch for haproxy. do i file a bug against https://launchpad.net/~charmers/charms/precise/haproxy/trunk and push my changes to ~tvansteenburgh/charms/precise/haproxy/trunk ?
[18:07] <renier> utlemming, that's what I saw upon vagrant up. let me know if you need logs of anything ^
[18:09] <lazyPower> tvansteenburgh: indeed
[18:09] <lazyPower> you dont need to specify /trunk as your local branch through, you can name it whatever you like
[18:09] <tvansteenburgh> lazyPower: thanks
[18:21] <tvansteenburgh> lazyPower: do i need to subscribe ~charmers to this, or change the status? https://bugs.launchpad.net/charms/+source/haproxy/+bug/1310732
[18:21] <_mup_> Bug #1310732: Enable sticky sessions <haproxy (Juju Charms Collection):New> <https://launchpad.net/bugs/1310732>
[18:22] <lazyPower> tvansteenburgh: nah,  create a MP for your branch and it will show up in the REV Q
[18:44] <tvansteenburgh> anyone want to get on a hangout and discuss a good way to do a master election using peer relations?
[18:49] <marcoceppi> haha
[18:49] <marcoceppi> tvansteenburgh: I'd love to, but that's a long hangout
[18:51] <tvansteenburgh> marcoceppi: i got nothin but time :P
[18:52] <tvansteenburgh> even if we time-box it, i'd like to hear your thoughts
[18:52] <tvansteenburgh> i need to find some way to solve my problem, even if it's not proper leader election
[18:54] <lazyPower> tvansteenburgh: there's an effort to resolve this for cassandra to
[18:55] <lazyPower> so let me know what your ideas are. I'll be assuming responsibility for that behemoth soon
[19:32] <renier> jcastro, given juju 1.18 has that problem, should I use juju/stable or another branch? I'm going to try this on a trusty box
[19:36] <jcastro> renier, trying with 1.16 might help
[19:37] <renier> jcastro, ok. is that 'juju/unstable'? (not familiar with the branch names?
[19:38] <renier> I can look it up. don't worry
[19:39] <jcastro> 1.16 is old stable
[19:39] <jcastro> 1.18 is current stable
[19:39] <jcastro> 1.19 is current devel
[19:39] <renier> ok, thanks
[21:20] <jose> jcastro: are the juju docs good for translating?
[21:20] <jose> because if so, I can try and translate them to spanish
[21:26] <jcastro> jose, gimme a few days to sort out some minor issues first
[21:26] <jcastro> we need to connect it to launchpad, etc.
[21:26] <jose> no worries, just ping me once it's good to go and I'll do my best to translate them
[21:44] <utlemming> er, so why would I be seeing this: "machine-0: 2014-04-21 21:40:53 ERROR juju.provisioner provisioner.go:175 environ provisioner died: failed to process updated machines: cannot start machine 1: no matching tools available" in the logs?
[21:48] <lazyPower> utlemming: it needs a default-series property in teh environment config
[21:48] <utlemming> lazyPower: thanks
[21:54] <lazyPower> anytime


[04:49] <superfly> sp
[05:17] <Langjan> Hi to the boffins. Is there a way to sort out this update glitch? http://slexy.org/view/s2j10QHhI0
[05:30] <Kilos> morning superfly and others though i am sure you are the only one awake
[05:30] <Kilos> Maaz, coffee on
[05:30]  * Maaz washes some mugs
[05:30] <superfly> heya Kilos
[05:30] <superfly> hi Langjan
[05:30] <Kilos> morning Langjan
[05:32] <Langjan> Hi Kilos and superfly, are you well?
[05:34] <Maaz> Coffee's ready for Kilos!
[05:37] <Kilos> Maaz, ty
[05:37] <Maaz> Enjoy Kilos
[05:37] <Kilos> i fine ty
[05:46] <Langjan> This update problem is persevering, any suggestions? http://slexy.org/view/s2j10QHhI0
[05:52] <superfly> Langjan: run "sudo dpkg --configure nvidia-current"
[05:55] <superfly> Langjan: can you see where the error is?
[05:57] <Langjan> No superfly, I have no idea. This is the outcome of your input: http://slexy.org/view/s2oisgE4xr
[05:58] <superfly> Langjan: what can you see in the output of my command?
[05:59] <Langjan> Superfly, see http://slexy.org/view/s2oisgE4xr
[05:59] <superfly> no Langjan, I'm asking you what YOU can see
[05:59] <superfly> Langjan: I'm not going to solve your problem for you, you need to learn
[06:00] <Langjan> OK I agree, thanks but I don't understand. What do I see where?
[06:01] <superfly> Langjan: look at the output of my command, and see if you can find an error message
[06:02] <Langjan> superfly, alternative link /usr/lib/libvdpau_nvidia.so is already managed by _gl_conf.
[06:02] <superfly> Langjan: yep, that's the error
[06:03] <superfly> Langjan: now go back to your update output, and see if you can find that error in there
[06:05] <Kilos> oh my. still that one
[06:05] <Langjan> superfly, it started here: Setting up nvidia-current (280.04-0~maverickubuntu3) ...
[06:06] <superfly> Langjan: yep, that's right... now look at the line just below the error message. what does it say?
[06:07] <Langjan> update-alternatives: error: alternative link /usr/lib/libvdpau_nvidia.so is already managed by _gl_conf.
[06:07] <superfly> Langjan: and the line after that
[06:07] <Langjan> dpkg: error processing nvidia-current (--configure):
[06:08] <superfly> Langjan: yes, that's it. do you see why I told you to run that other command?
[06:09] <Langjan> yes I do, thanks this makes sense. Now I must try to see why did it not work?
[06:09] <Langjan> update-alternatives: error: alternative link /usr/lib/libvdpau_nvidia.so is already managed by _gl_conf.
[06:09] <superfly> Langjan: well, it told you why it didn't work, that's the error message, but I am thinking that we might be able to force it to run
[06:13] <superfly> Langjan: try "sudo dpkg --configure --force-overwrite nvidia-current"
[06:15] <Langjan> Same result superfly...
[06:15] <superfly> hrm
[06:16] <Langjan> update-alternatives: error: alternative link /usr/lib/libvdpau_nvidia.so is already managed by _gl_conf.
[06:18] <Kilos> this is an ugly one hey
[06:18] <Langjan> looks like.
[06:19] <Langjan> strange thing is everything seems to be working ok
[06:19] <Kilos> but i am learning with you two as you go. it will be fixed
[06:19] <Kilos> oh
[06:20] <superfly> Langjan: yes, it's just nvidia-current, bumblebee and bumblebee-ui that are not configured properly
[06:21] <superfly> Langjan: do me a favour, run this command: "ls -l /usr/lib/libvdpau_nvidia.*"
[06:21] <Langjan> Ok
[06:21] <Kilos> superfly, what would happen if jan purges nvidia-current and then installs it again?
[06:22] <Kilos> for my info only
[06:22] <superfly> Kilos: I''m not too sure, but if I can avoid the purging, I would rather
[06:22] <Kilos> ok ty
[06:22] <Langjan> No such file or directory
[06:23] <superfly> show me the output?
[06:23] <Langjan> ls: cannot access /usr/lib/libvdpau_nvidia: No such file or directory
[06:24] <Langjan> ls: cannot access /usr/lib/libvdpau_nvidia.*: No such file or directory
[06:25] <superfly> Langjan: weird
[06:26] <Langjan> Thinking maybe I should upgrade to 11.04 but no time for it at present
[06:27] <Langjan> update manager says all updates are done...
[06:30] <Kilos> maybe it is already configured but through that _gl_conf instead of where dpkg wants to do it
[06:30] <Langjan> Tried to reinstall packages: E: nvidia-current: subprocess installed post-installation script returned error exit status 2
[06:30] <Langjan> E: bumblebee: dependency problems - leaving unconfigured
[06:30] <Langjan> E: bumblebee-ui: dependency problems - leaving unconfigured
[06:32] <Kilos> Langjan, is there a reason you use bumblebee
[06:33] <Kilos> is there nothing in the repos that will work instead
[06:34] <Langjan> My virtualbox seems to be dependent on it
[06:34] <Kilos> what virtual box software are you using
[06:35] <Kilos> not the virtualbox in synaptic
[06:35] <Langjan> virtualbox OSE
[06:35] <Kilos> this is out of my league so dont listen to me , i am just trying to figure out why it gives probs every update with bumblebee
[06:37] <Langjan> Yes Kilos it was installed via Ubuntu software mgr
[06:37] <Kilos> and bumblebee?
[06:37] <Kilos> i dont see it anywhere
[06:39] <Langjan> 0.9-1~maverickubuntu6 (bumblebee-ui)
[06:39] <Langjan> Kilos, if you search bumblebee on software centre it will show
[06:40] <Kilos> oh. i only use synaptic. software centre is way too slow here
[06:40] <Kilos> does it show in your synaptic
[06:41] <Langjan> superfly, lets leave it for the moment, everything seems to be working fine.
[06:41] <Langjan> Yes Kilos it does
[06:42] <Kilos> try in synaptic then to reinstall it and nvidia-
[06:42] <Langjan> I did, no luck
[06:42] <Kilos> eish
[06:43] <Langjan> OK, am going to love and leave you for now, enjoy a blessed day
[06:43] <Kilos> you too Langjan
[06:43] <Langjan> thanks kilos
[07:20] <Kilos> sorry superfly i wasnt trying to take over from you. but getting info for me
[07:46] <marcog> tumbleweed: can you send reminders about the global jam to the mailing list and fb event?
[07:50] <superfly> Kilos: no problems, I was busy - had a couple of meetings
[07:50] <Kilos> ty superfly
[07:51] <Kilos> hiya marcog morgs
[07:51] <Kilos> lo sdehaan
[07:59] <morgs> morning
[08:01] <superfly> hiya morgs
[08:01] <morgs> hey superfly
[10:21] <Kilos> nuvolari, is jy ok seun
[10:24] <Kilos> Maaz, coffee on
[10:25]  * Maaz puts the kettle on
[10:25]  * Kilos tries xubuntu 11.04
[10:28] <Maaz> Coffee's ready for Kilos!
[10:29] <Kilos> Maaz, ty
[10:29] <Maaz> Enjoy Kilos
[10:31] <nuvolari> lo oom Kilos
[10:31] <nuvolari> net-net oom
[10:32] <Kilos> ek sien jy nogal besig
[10:39] <Kilos> hi packetboy
[10:39] <packetboy> sup
[10:40] <Kilos> your first time here?
[10:40] <packetboy> yip
[10:40] <Kilos> welcome to ubuntu-za
[10:41] <packetboy> ubuntu sounds like a bushman
[10:41] <Kilos> what OS are you using
[10:42] <packetboy> ubuntu
[10:42] <packetboy> u-bun-two
[10:42] <Kilos> thats good and are you happy with it
[10:43] <packetboy> no problems with any os
[10:43] <packetboy> like to learn them all
[10:44] <Kilos> thats good. you one of the clever guys
[10:44] <packetboy> no
[10:45] <Kilos> must be if you dont have probs with windows
[10:45] <Kilos> hehe
[10:45] <packetboy> what problems do you have with windows?
[10:45] <Kilos> oh , actually clever guys dont use windows
[10:46] <packetboy> huh?
[10:46] <Kilos> lol
[10:47] <Kilos> i gave it up coupla years ago because of virusses and lost programs and lotsa srtupid things
[10:47] <Kilos> like not seeing the cdrom at times
[10:47] <packetboy> how did you get a virus?
[10:48] <Kilos> with music one of the times
[10:48] <packetboy> did you play whack-a-mole?
[10:48] <Kilos> and  in mails other times
[10:48] <Kilos> huh?
[10:49] <Kilos> gotta run. be back a bit later
[15:46] <Kilos> hiya nlsthzn
[15:47] <Kilos> you well?
[15:47] <nlsthzn> Hey Uncle Kilos :) Weather a bit better in SA on this Spring day?
[15:47] <Kilos> lol. yeah it be very kiff to have sun that actually warms you
[15:47] <nlsthzn> Oh, I could complain... But it would be unfair in the bigger scheme of things...
[15:48] <Kilos> hehe
[15:51] <Kilos> google what is the ubuntu maverick file manager
[15:52] <Kilos> eish
[15:52] <Kilos> ek sukkel partykeer
[15:52] <nuvolari> Kilos: dis nautilus oom
[15:53] <nuvolari> :P naughtylust *cough*
[15:53] <Kilos> Clol its audacity hey?
[15:53] <nlsthzn> sorry... @ work so I am up and down from infront of the PC... lol @ nuvolari
[15:53] <Kilos> oh my
[15:53] <nuvolari> Kilos: audacity is an audio editor
[15:53] <nuvolari> lo nlsthzn
[15:54] <nuvolari> ok, I'm off
[15:54] <nuvolari> cheerz
[15:54] <nlsthzn> nuvolari: bai
[15:54] <Kilos> what is audacity for?
[15:54] <Kilos> aw dankie nuvolari
[15:54] <Kilos> mooi loop
[15:56] <nlsthzn> it is a application used to work with sound files...
[15:56] <nlsthzn> editing them etc.
[15:57] <Kilos> lol. i get mixed up with all the funny names
[15:57] <nlsthzn> :)
[15:57] <Kilos> hard work to edit music methinks
[15:58] <nlsthzn> As hard as most things in life that are hard before they become easy...
[15:58] <Kilos> hehe
[16:00] <nlsthzn> Also, in most applications you can check in help/about what the name is and version etc...
[16:01] <Kilos> didnt even think of that nlsthzn trying to find why things are opening slow here
[16:02] <Kilos> since the power cuts and the grub recovery giving up the ghost
[16:03] <Kilos> i read that fsck and tried from cd but not sure of what all to put in the command and it kept asking "is it mounted"
[16:03] <Kilos> so i getting closer to a clean install
[16:04] <Kilos> i even install xubuntu onna small drive today to check it out
[16:07] <nlsthzn> Cool... Xubuntu is pretty good... however, if Ubuntu ran OK before, then there is another issue, which is either something to do with what is installed now or a problem with the hardware... if it is hardware related then installing another distro isn't going to help...
[16:08] <nlsthzn> BTW, if there is a way for me to download all the required repo's etc. and burn them to DVD I will be happy to do this periodically and send disc's to SA to help where bandwidth is an issue...
[16:08] <Kilos> i prefer ubuntu. dont like the close minimise buttons on the right like windows
[16:09] <Kilos> Maaz, google where to download ubuntu repos
[16:09] <Maaz> Kilos: "Repositories/Ubuntu - Community Ubuntu Documentation" https://help.ubuntu.com/community/Repositories/Ubuntu :: "Ubuntu -- Ubuntu Packages Search" http://packages.ubuntu.com/ :: "AptGet/Offline/Repository - Community Ubuntu Documentation" https://help.ubuntu.com/community/AptGet/Offline/Repository :: "Medibuntu - Community Ubuntu Documentation" https://help.ubuntu.com/community/Medibuntu :: "Off-line custom repository [Archive] - Ubu
[16:10] <Kilos> but they too big nlsthzn . like 20g i think
[16:12] <Kilos> just send dates
[16:12] <Kilos> but not with ahab chicks
[16:13] <Kilos> those you chew on
[16:14] <Kilos> Maaz, coffee on
[16:14]  * Maaz starts grinding coffee
[16:16] <nlsthzn> :) 20GB sounds like 5 or 6 DVD's... easy as pie... as long as there is an easy way to do it :p You like dates Mr. Kilos?
[16:16] <Kilos> hehe i dont remember
[16:18] <Maaz> Coffee's ready for Kilos!
[16:18] <Kilos> Maaz, dankie man
[16:18] <Maaz> Groot plesier my vriend
[18:03] <Kilos> night all. sleep tight
[22:03] <Squirm> fp


[04:37] <cobb28> i have been working on this problem for a few hours, i'd love some help if someone is around, i don't want to go back top vista media center hehe
[04:38] <cobb28> i have a i have a TH-50PZ80U plasma tv connected via hdmi right now and i need help with my xorg.conf please, the desktop is too big currently by an inch or so on the screen, i cannot figure out what to put in my xorg.conf
[04:39] <cobb28> i have tried a couple different modelines but nothing seems to change....currently in my nvidia settings it shows my resolution is 1920x1080 @ 50hz if that helps..
[06:47] <camelreef> good morning from Scotland
[06:48] <rhpot1991_laptop> hey camelreef
[06:48]  * camelreef is aka Nico on LP
[06:49] <camelreef> hello rhpot1991_laptop
[06:49] <camelreef> I'm planning on testing the recent mythexport today
[06:49] <camelreef> I read you PM
[06:50] <rhpot1991_laptop> yep I know :)
[06:50] <rhpot1991_laptop> let me know how it goes
[06:50] <camelreef> quick Question: are the daily builds for -fixes coming back for Intrepid?
[06:51] <rhpot1991_laptop> yes, at some point
[06:51] <camelreef> ok, I'll keep watching the web site
[06:51] <camelreef> not that anything is broken on my system, it's working fine
[06:52]  * camelreef is excited by the NVIDIA VDPAU stuff
[06:53] <camelreef> this has been a great month, between VDPAU and blu-ray closer to be artificially "opened"
[06:53] <camelreef> the future of HD on Linux is bright
[06:58] <rhpot1991_laptop> camelreef: in due time
[06:58] <camelreef> indeed
[06:59] <camelreef> the important part is movement
[06:59] <camelreef> and there is movement
[06:59] <camelreef> then its only a matter of time
[06:59] <camelreef> rhpot1991_laptop, you seem to be active around the iPod stuff too
[07:00] <camelreef> or am I mistaken?
[07:00] <rhpot1991_laptop> camelreef: like?
[07:01] <rhpot1991_laptop> thats kinda where mythexport started from
[07:01] <camelreef> I'm looking for a PPA with an SNV snapshot of libgpod
[07:01]  * camelreef knows it's not the right channel
[07:02] <rhpot1991_laptop> hmmmm
[07:04] <rhpot1991_laptop> camelreef: http://packages.ubuntu.com/search?keywords=libgpod&searchon=names&suite=intrepid&section=all
[07:05] <rhpot1991_laptop> none of those new enough?
[07:08] <creol> HEY ALL NEW PROB... worked perfect last night, tonight all LIVE TV amd recorded TV playback is fast with chipmonk audio. Even recorded TV that was normal last night is playing back fast. I tried "time stretch" but that just sounds like a chipmonk talking slowly. Any suggestions?
[07:09] <creol> FYI Video playback is fine
[07:10] <creol> another FYI the playback pictur appears a little fast as well.
[07:23] <camelreef> rhpot1991, none, orry
[07:29] <creol> okay i fixed my own problem via a post i found via google. Apparently the setting in playback "Use video as timebase" can cause tv playback to be fast. Thanks anyway... time to get back to Smallville
[07:31] <rhpot1991> camelreef: I'd guess you could try checking for versions of amarok or programs that use it on launchpad, might be quicker to just deal with it yourself though
[07:31] <rhpot1991> camelreef: care if I ask why you need it?
[07:38] <rhpot1991> camelreef: I gotta get to bed, good luck :)
[07:38] <camelreef> rhpot1991, updated support for photos on Touch and support for Gen4 Nano
[07:38] <camelreef> thanks rhpot1991
[07:44] <superm1> suppport for photos on touch?
[07:45] <superm1> i'm assuming only on jailbroken touch though
[07:48] <camelreef> photos on Touch
[07:48] <camelreef> jailbroken 1.1.4
[07:48] <camelreef> music and movies are fine, but photos are broken
[07:48] <camelreef> and fixed in a more recent snapshot
[07:49] <camelreef> artwork support is also not working on current release for Gen4 Nano
[07:49] <camelreef> also fixed in SVN
[07:49] <camelreef> I'm fine with recompiling source packages against a newer libgpod lib
[07:50] <camelreef> but packaging from scratch, a library, on top of that, is a bit beyond my current capabilities
[07:50] <camelreef> I've tried
[07:50] <camelreef> not too hard, I have to say
[07:51] <camelreef> but I am amazed to see that no dev scratched the same itch
[07:51] <camelreef> I'd rather not compile from source and do a make install
[07:51] <camelreef> I'm a strong believer in package management
[07:52] <camelreef> oh, and Hi superm1, btw :o)
[07:53] <superm1> well if there is a newer libgpod in jaunty, you can use prevu
[07:53] <superm1> hi camelreef
[07:53] <superm1> but actually its the same version as intrepid: https://edge.launchpad.net/ubuntu/+source/libgpod
[07:54] <camelreef> yeah
[07:54] <superm1> so your next best thing is to check debian, and if nothing newer there, add the debian/ directory to an extracted new tarball
[07:54] <superm1> and try to build it
[07:54] <camelreef> Ubuntu has the latest libgpod release, but it is quite old
[07:54] <camelreef> same for Debian
[07:56] <superm1> oh, well go get upstream to do another release :)
[07:58] <camelreef> hehe
[07:58] <camelreef> I tried that
[07:58] <camelreef> I even asked if they could do like mplayer and include a debian dir so that we could build snapshots easily
[07:58] <camelreef> lemme try the debian dir stealing method you proposed
[08:01] <superm1> you might want to bump the changelog too
[08:01] <superm1> dch -i
[08:01] <superm1> will do the trick for you
[08:02] <superm1> what'd they say about doing another release?
[08:07] <camelreef> did the changelog, by hand
[08:07] <camelreef> removed the debian/patched and debian/patches content too
[08:07] <camelreef> no word from them on a new release
[08:08] <camelreef> just a quick comment about trying to release a bit before the major distros release, but no follow-up
[08:08] <camelreef> so far building OK
[08:08] <camelreef> woot
[08:09] <camelreef> spoke too quick
[08:10] <camelreef> failed on dpkg-gensymbols for pyhton-gpod
[08:11] <camelreef> ah no, for libgpod2-nogtk
[08:14] <camelreef> dpkg-gensymbols -c4 -Pdebian/libgpod3-nogtk -plibgpod3-nogtk
[08:14] <camelreef> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
[08:14] <camelreef> dpkg-gensymbols: warning: some symbols disappeared in the symbols file: see diff output below
[08:14] <camelreef> dpkg-gensymbols: warning: debian/libgpod3-nogtk/DEBIAN/symbols doesn't match completely debian/libgpod3-nogtk.symbols
[08:14] <camelreef> so close....
[09:03]  * camelreef is manually fixing his libgpod.symbols and libgpod-nogtk.symbols files, what a hack
[09:10]  * camelreef has built his libgpod SVN packages !
[09:34] <cann> sooo iam thinking of finaly take the plunge and go HD, i got a p4 3ghz backend / frontend and and a diskless SD frontend in my bed room today, i got this amdx2 4400 with 2gb ram and a 7900 gts pci-e  collecting dusts and the plan is to make it a diskless FE for HD. you guys think that will be enouh for 1080p ?
[09:34] <cann> enough*
[09:35] <cann> ohh i got 100mbit network at home, but it will get upgraded to 1gbit in the near future
[09:47] <camelreef> 1 Gbps will be needed
[09:47] <camelreef> I would wait a tiny bit, though
[09:48] <camelreef> NVIDIA's VDPAU is coming for full HD hardware accelleration
[09:48] <camelreef> you will probably need to change your video card for a more recent one
[09:48] <camelreef> $30 and fanless is available with the right circuitry
[09:49] <camelreef> then any CPU will be fine for 1080p
[09:53] <camelreef> superm1, now that the symbols stuff is "probably fixed" I have internal dependency issues. libgpod common depends on libgpod3-nogtk only and not on libgpo3-nogtk or libgpod3
[10:47] <cann> camelreef: alright thank you for your suggestions =)
[10:48] <hads> You don't need GigE
[10:50] <cann> yeah i know i dont *need* it but it wouldnt hurt either =) and i can tell my wife its needed, that way i get another toy \o/
[12:23] <AkhIL> Hi. I can't get data from my card reader browsed by myth video browser. How I can get usb disks automounted and displayer in video gallery? CD/DVD works well for me
[15:09] <msaul> Was directed from #mythtv-users to #mythtv developpers regarding nvidia driver issue, was wondering if I could chat with someone to provide info for suggestion or provide data for developpers to fix issue...
[15:09] <msaul> Running mythbuntu 8.10 with hp HVR1600 video capture card and Nvidia GEForce 7600 GSOC graphics card
[15:10] <msaul> When using restricted driver for Nvidia (version 96 or 173 or 177) upon bootup, get "failed to initialize nvidia graphics device PCI:1:0:0 and only allows to go into low graphics mode
[15:10] <msaul> I CAN watch TV in low graphics mode (after getting Capture utility to finally recognize HP HVR 1600 and then going back in to have it detect it for MPEG. BUT, when trying to view EPG (program guide) I can see it briefly, but flickers on and off making it unusable.
[15:10] <msaul> When running in su nvidia-xconfig and rebooting, may bring up better graphics, but does not recognize HP HRV1600.
[15:10] <msaul> I don't know if anyone can help or redirect me to appropriate place...
[16:11] <superm1> camelreef, modify debian/control and you should be able to resolve it
[21:02] <heyheyhey> hey all anytone tryed mythrecipe?
[21:15] <foxbuntu> heyheyhey, last I heard it didnt really work
[21:19] <jphillip> I tried it once upon a time and it was more designed for .19 and didn't play well with .2x IIRC
[21:21] <heyheyhey> they say it for .21
[21:21] <foxbuntu> heyheyhey, give it a shot then
[21:22] <heyheyhey> it don't tell ya how to install it
[21:22] <heyheyhey> MythRecipe  Confirmed to work with MythTV 0.21
[21:47] <heyheyhey> is 8.10 any better then 8.04?
[21:48] <laga> it's 0.06 better
[21:48] <heyheyhey> i mean for bugs? or what is different
[21:48] <foxbuntu> lol
[21:48] <foxbuntu> heyheyhey, its much worse
[21:48] <foxbuntu> er wait
[21:48] <foxbuntu> better
[21:48] <foxbuntu> er wait
[21:49] <foxbuntu> what do I know?
[21:49] <foxbuntu> ;)
[21:49] <laga> nothing.
[21:49] <laga> ;)
[21:49] <heyheyhey> lol
[21:49] <foxbuntu> laga, I left that one open for you
[21:49] <heyheyhey> well i just don't wanta mess up my system if i upgrade
[21:50] <foxbuntu> heyheyhey, you run the risk of that, but there are a few new features and many bug fixes in Intrepid
[21:50] <heyheyhey> okay thanks i will not upgrade lol
[22:08] <spoky99> hi all
[22:08] <spoky99> Someone know how to make work the program guide?
[22:09] <spoky99> I install it into one computer and work fine, but in other.. It don't work
[22:10] <spoky99> I fount the grubtv file into the root directory, i copy it into the folder .mythtv  into the home of the user
[22:11] <spoky99> but... I don't see any program description into the guide :(
[22:48] <camelreef> superm1, I'm not sure I  know how to resolve that. Googling will probably help resolve my current limitation


[01:13] <wrst> Omnifrog: DJ'ing go well tonight?
[01:14] <Omnifrog> yeah, it usually does even if I have no idea what I'm doing
[01:15] <wrst> ha ha sometimes that's when I do my best
[01:15] <Omnifrog> I'm pretty flexible though
[01:15] <Omnifrog> I just roll with it
[01:16] <Omnifrog> Saturday nights are generally slow too
[01:28] <wrst> I am a fan of slow
[01:37] <wrst> howdy eights
[01:43] <eights> wrst, how are you?
[01:43] <wrst> good how are you doing?
[01:59] <eights> wrst, im doing well, you?
[01:59] <wrst> yep getting adjusted to kde
[02:01] <eights> oh yea? how you like it? always been a gnome freak, i tried kde is  its 3.0 stages it was  alright, ive seen the newer version it looks sweet
[02:01] <Omnifrog> gnome blows
[02:01] <Omnifrog> >.>
[02:02] <eights> gnome with all panels removed, cario-dock installed with compiz, works lovely for me ;) lol
[02:03] <eights> gnome-fallback-session i should say
[02:05] <Omnifrog> I'm a fussy bastard but I've never liked gnome
[02:05] <Omnifrog> I've tried! lord knows I've tried
[02:07] <wrst> eights: kde 4.11 is solid
[02:08] <wrst> everything works they aren't taking features away
[02:08] <wrst> I have always loved gnome
[02:08] <wrst> but my main reason was trying out the kde connect stuff its very early but pretty neat
[02:08] <eights> ill deff check it out, i like trying new environments
[02:09] <wrst> in stock form its very Windows 7 looking but you can tweak it crazily
[02:09] <wrst> compositing works much better than mutter or clutter or whatever it is gnome uses now
[02:10] <wrst> I think it has a more polished default look and feel also, but the extensions with gnome shell are really nice
[02:13] <wrst> here is my current setup, not a lot changed from default: https://dl.dropboxusercontent.com/u/2959906/kde411.png
[02:22] <eights> wrst, i like it, very very clean. here is my current: http://tinypic.com/r/9r24ib/5
[02:23] <wrst> I like that
[02:23] <wrst> and I have wondered why gnome didn't put the dock at the bottom?
[02:23] <wrst> I used an extension to just autohide the regualr gnome dock and it worked well but never as good as having it at the bottom
[02:24] <eights> you can add the "applications menu" to a bottom gnome panel and have it look and have a "similar" feel to win
[02:25] <eights> ive always just removed all the panels execpt the top one and used another "docker" application like cario
[02:25] <wrst> cairo is nice
[02:25] <wrst> I have used it with xfce before
[02:25] <eights> you can custimize it to look like win osx etc i like it too
[02:27] <wrst> but must say for a default setup kde really is nice, and I suppose unity is ok fi you are into that type of thing
[02:28] <eights> yea cant stand unity, i always install the gnome classic shell with a default ubuntu install
[02:29] <wrst> yeah I'm not totally sold with all the convergence jazz
[02:35] <wrst> goodnight everyone
[02:35]  * wrst heads to sleepy town
[02:40] <eights> later
[20:40] <wrst> wb chris4585
[22:32] <chris4585> thanks wrst


[01:05] -lugito:#lubuntu-devel- [rDEFAULTSETTINGSe46db7f72dd4: Add alt-tab switching for all desktops.] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rDEFAULTSETTINGSe46db7f72dd4
[01:37] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T146#3185
 @The_LoudSpeaker [<The_LoudSpeaker> @kc2bez re: your comments on the same, For those in control fi …], I think syntactically it is the same. Personnally, I find it easier to read and if you have enough items you need to wrap that around properly. Also,  from the outline on the wiki page `1. Prefer the newer Debian changes when possible
[13:05] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T146#3186
[13:36] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T146#3187
 Sorry for missing standup yesterday
 Let's do it today, maybe 3:30 Central?
 After the daylight savings time shift things got complicated for me - school ends at the same time the standup starts so I always miss the beginning
[17:02] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T146#3188
[17:03] <wxl> oh i didn't know we officially changed it XD
 Oh I didn't realize it either.
[17:07] -lugito:#lubuntu-devel- [T150: Erase Disk fails with existing partition scheme] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T150#3189
[17:09] <wxl> you know what would be really good? if we could figure a time where we could all get together and just deal with these merges. @The_LoudSpeaker @tsimonq2 @kc2bez (@RikMills if you want) perhaps sometime between 1400-1600 UTC?
[17:10] <wxl> it would also be a good opportunity for interested developers to join in and learn
[17:10] <wxl> p.s. new cala's out soon from what it looks like on the irc channel
 14 UTC works for me on Saturday?
 @wxl [<wxl> p.s. new cala's out soon from what it looks like on the irc channel], I saw that too.
[17:12] <wxl> works for me
 @tsimonq2 [14 UTC works for me on Saturday?], I can make it work.
[17:14] <wxl> i'm pm'ing raman
[17:16] <wxl> it's generally a good time for him but i bet he's in class
[17:16] <wxl> ^ @HMollerCl you might want to come to this
 Raman needs to be there I think
[17:17] <wxl> btw @HMollerCl i'm not sure of the context but when crazy was doing automated installs he got this somehow https://dpaste.org/kBD3
[17:17] <wxl> we'll get him there :)
 mm, saturday and sunday might be complicated because of family
 @wxl [<wxl> btw @HMollerCl i'm not sure of the context but when crazy was doing automa …], crazy?
[17:18] <wxl> well if you can come you can come if not c'est la vie
[17:18] <wxl> crazy with cala
 @HMollerCl [crazy?], IRC nick
[17:19] <wxl> https://github.com/abucodonosor
 is he in lubuntu support channel?
[17:20] <wxl> no
 mm, how can I reach him?
[17:21] <wxl> aw i didn't even notice i got added to contribs https://github.com/calamares/calamares/commit/c854006e768ec34e46d6e0ff266b8e8091a57530#diff-3d350169560e75d0cf9fc8e3574a3639
[17:21] <wxl> you can go to the #calamares channel but there's no telegram there
[17:22] <wxl> of that list i have no idea which he is :)
[17:23] <wxl> oh he said he found it in ~/.xsession-errors
[17:28] <wxl> ok i think i've managed to figure out who he is. he's the primary contributor to frugalware and if that's still the founder, it's miklós vajna
 mmm, I don't have it in ~/.xsession-errors
[17:28] <wxl> maybe only under some conditions
 #calamares is in freenode?
[17:29] <wxl> yep
 there is one crazy in #calamares, but he is away
[17:29] <wxl> but he's still not listed if that's the case. sheesh.
 maybe he doesn't have update-notifier-common
[17:32] <wxl> it was from the iso
[17:32] <wxl> i couldn't help myself: https://github.com/calamares/calamares/pull/1322
[17:33] <wxl> ok i better go to work love you bye
 kthanksbye
[17:43] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T146#3190
 @wxl [<wxl> you know what would be really good? if we could figure a time where we cou …], It would be great
 @wxl [<wxl> it's generally a good time for him but i bet he's in class], On Saturdays I have class till 1300 IST free after that.
 I will be there.
 Also, today is the standup right? In a few hours.
 ¯\_(ツ)_/¯
 I can't keep track anymore XD
 I think the new time is today only.
 "I am here all the week"
 Earlier it was Friday 2.30 am according to IST but now it is Thursday 2.30 am. That's in 3 hours.
[18:47] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T146#3191
[19:28] -lugito:#lubuntu-devel- [T128: Alt-Tab and Alt-Shift-Tab feature request (openbox conf)] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T128#3192
[19:44] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T146#3193
 wxl @kc2bez talk with crazy, he found it in the logs during instalation on live CD
 I believe it might be if update-notifier-common is not in live. But, does it make sense to have update-notifier in live?
[20:06] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T146#3194
[21:25] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T146#3195
 @kc2bez why change feature freeze to 5 am?
 Infinity usually implements the freeze a 9pm UTC on the day in question
 phab calendar is a little weird. I made an all day event and midnight my time is 5 AM UTC
 I will adjust accordingly.
 ah, I see
[22:07] -lugito:#lubuntu-devel- [rMANUAL09a215b6f7db: Fix capitilzation] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL09a215b6f7db
[22:14] -lugito:#lubuntu-devel- [rMANUALa7e755109c4c: Fix button to what actually shows up] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALa7e755109c4c
[22:37] -lugito:#lubuntu-devel- [T146: libreoffice qt5 vcl] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T146#3196
[23:12] -lugito:#lubuntu-devel- [rMANUAL2fc86b4440a2: Add Apply Full Upgrade] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2fc86b4440a2
[23:13] -lugito:#lubuntu-devel- [rMANUAL34c8b20b4927: Add undocking playlist] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL34c8b20b4927