[00:02] <BluesKaj> hmm, sounds like the one I have
[01:22] <danbhfive> anyone know anything about nvidia driver not being installable?
[01:25] <yofel> danbhfive: bug 506618 ?
[01:25] <danbhfive> might be
[01:27] <danbhfive> yeah, that's it
[01:27] <danbhfive> thanks!
[01:27] <yofel> danbhfive: see the instructions here to install the driver anyway https://wiki.ubuntu.com/LucidLynx/TechnicalOverview#Known%20issues
[02:06] <mazda01> having sound issues with lucid where it worked out of the box for karmic. i have a Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) per lspci
[02:06] <mazda01> meaning, i have no sound
[03:06] <un214> ok who thinks it's a bad idea to upgrade already?
[03:07] <un214> really? nobody?
[03:08] <crimsun> well, you're going to hit /something/
[03:08] <mazda01> nope, whatever the problem may be, it won't be show stopping most likely. go for it! or just run it from a usb stick on the same hardware like I am to test it out
[03:09] <crimsun> mazda01: where's your alsa-info.sh output?
[03:09] <mazda01> crimsun, and where am i suppose to know to do that?
[03:09] <un214> just so long as it boots rescue I know how to back out
[03:10] <un214> I've been wanting an X server that doesn't use HAL for awhile
[03:12] <crimsun> mazda01: the DebuggingSoundProblems wiki page? Of course you can also use ubuntu-bug alsa-base
[03:12] <danbhfive> is anyone else having a problem with dkms and installing a kernel?
[03:13] <mazda01> crimsun, here ya go: http://www.alsa-project.org/db/?f=305c7512612fcdc9c41469548c326f452f3f9ac9
[03:14] <crimsun> why are you still using snd-hda-intel: probe_mask=1
[03:15] <mazda01> crimsun, i added that because I thought it may help, but after restarting pulseaudio i still have no sound. i can remove it if you think it would help
[03:15] <mazda01> crimsun, didn't work before i had that there either though
[03:15] <crimsun> remove it, reboot
[03:16] <mazda01> crimsun, my system is completely stock, installed yesterday with no change besides adding applications BUT sound didn't work from the get go
[03:16] <mazda01> crimsun, that wouldn
[03:16] <mazda01> t make a difference as I have stated that i have had no sound from the begining
[03:16] <crimsun> yes, it does make a difference
[03:16] <crimsun> when you pass a probe mask, it alters the codec init order
[03:17] <crimsun> I don't really care if you don't have audible sound right away; I do care that your codec dump is from a pristine boot.
[03:17] <mazda01> crimsun, im telling you, the sound didn't work before I added that and I haven't rebooted even after adding that.  i'll do  it just to satisfy your curiosity though
[03:17] <mazda01> crimsun, understood
[03:17] <mazda01> crimsun, be right back
[03:28] <mazda01> im back, here's the new file.http://www.alsa-project.org/db/?f=1d35f9a84ca862eb637a74c018951096b8ccbe0c   also, NOW my sound card is actually appearing within the preferences of sound. where as before it wasn't.
[03:29] <mazda01> u know what though, last time i booted up, i went and did the system test right away. i wonder if that mde my sound card not work?
[03:29] <crimsun> Master, Front, Center, LFE, Surround, Side are all muted
[03:31] <crimsun> e.g., use alsamixer to unmute them ('m')
[03:31] <mazda01> crimsun, sorry about that, i unmuted it and now it works. i don't know what was up with that. previous to me re-booting, there was no hardware within the sound dialog box. WEIRD!!! here is the system test report if you can use it. file:///home/ubuntu/.cache/checkbox/submission.xml
[03:32] <crimsun> I don't think I can reach through the intarwebs and pull that file from your home directory ;)
[03:33] <mazda01> crimsun, ha, i didn't even realize that it was my home directory.
[03:35] <mazda01> crimsun, here ya go if they can help, http://pastebin.com/f20f6ecb1
[03:35] <mazda01>     although i feel like a fool. i swear the sound didnt work and it had nothing to do with mute because before coming on the channel i ran alsamixer and everything, there was no hardware listed within sound preferences. i have been using ubuntu since breezy
[03:49] <mazda01> crimsun, HA, i knew it. the sound stopped working!!! it must be due to the system test, running a audio test makes it stop working. what can i provide you know to show it doesn't work?
[03:49] <mazda01> crimsun, http://www.alsa-project.org/db/?f=a58a265cbbd25d7be9580f2d13d4330c199cbc83
[03:50] <mazda01> crimsun, if i hold the cursor over the speaker, it says, 85% output -4.3 dB and Dummy Output
[03:57] <mazda01> crimsun, here are some piccs of sound preferences dialog. http://img686.imageshack.us/my.php?image=screenshothfq.png, http://img196.imageshack.us/my.php?image=screenshot1wn.png
[04:11] <\vish> hmm... is libsdl1.2debian-alsa being replaced by libsdl1.2debian-pulseaudio?
[04:16] <\vish> updates ask to remove the -alsa , or is it just broken dependencies?
[04:36] <crimsun> \vish: using Ubuntu?
[04:37] <crimsun> \vish: If so, it's intentional. I seeded that change.
[04:38] <crimsun> mazda01: unfortunately that second alsa-info.sh doesn't tell me anything. You should get me a verbose log (wiki/PulseAudio/Log).
[04:38] <crimsun> mazda01: note that a "dummy output" for PA is used when some other app has monopolized the sound device.
[04:44] <\vish> crimsun: yeah , ubuntu.. thankx
[04:44]  * \vish updates
[04:47] <un214> gak lucid installed some kind of X console by default
[04:48] <un214> how do I set this back to a real text console?
[04:54] <un214> ok that wasn't quite it
[04:54] <un214> something happened to the console graphics mode
[04:55] <un214> whatever mode it's using has incorrect hsync for my hardware
[05:03] <un214> that does it
[05:03] <un214> every single vga= value is wrong
[05:04] <un214> do I have to compile my own kernel just to get this stupid setting right?
[05:05] <un214> I know, i must sound like raving lunatic here but I spend most of my time at the console and the right edge is cut off
[05:06] <Sarvatt> un214: it's called KMS, your text console is at your monitors native resolution
[05:06] <un214> yeah and it's broke
[05:06] <Sarvatt> if you want an old ugly console like before you can boot with video=VGA-1:640x480 (replacing VGA-1 with what you use if its different)
[05:08] <Sarvatt> i dont know if you're using intel or ati because they both have KMS but you can boot with i915.modeset=0 or radeon.modeset=0 for now depending on which you use to not use KMS also
[05:09] <Sarvatt> are you sure its broken, and not just your monitors settings being wrong?
[05:09] <un214> well since X has no problem ...
[05:10] <un214> all right let's see what VGA-1 does
[05:10] <Sarvatt> is it a crt or lcd? possible you have gnome switching to a different refresh rate after it starts
[05:15] <un214> Sarvatt: sorry, didn't work
[05:17] <Sarvatt> xrandr say you're using vga-1?
[05:18] <un214> how should I know?
[05:28] <un214> what's it take to break KMS
[05:28] <un214> it wants a different monitor alignment than X does.
[05:28] <un214> very sorry, but it's gotta go
[05:33] <un214> sigh, looks like I'm compiling a kernel after all
[05:39] <bjsnider> you're compiling a kernel because you don't like kernel mode setting?
[05:46] <un214> that's right bjsnider
[05:47] <un214> I can't find a way to turn the setting off so out that component goes
[05:48] <un214> I went and booted previous kernel to get a usable console back
[05:49] <un214> why the heck is tex part of build-dep for kernel?!?
[06:01] <un214> ugh can't find KMS in the .config file either
[06:07] <un214> nice one cannot turn off framebuffer console because somebody depends on it
[06:08] <un214> anybody know a faster way to get rid of kms?
[06:28] <DanaG> E: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
[06:28] <DanaG> E: alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
[06:28] <DanaG> E: alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
[07:11] <Q-FUNK> hm.. this firefox 3.6 succesfully launched exactly once
[07:11] <Q-FUNK> now, it refuses to restart.
[07:28] <alkisg> If a newer package was uploaded in Lucid 1 hour ago, how long does it usually take to reach the mirrors? Hours? Days?
[07:29] <alkisg> Whoops never mind it just got here :)
[07:37] <DanaG> www.csc.calpoly.edu/~dgoyette/Screenshot-gbrainy.png
[07:38] <DanaG> somebody wasn't very "brainy" when creating that layout.
[07:39] <IdleOne> that is ugly
[07:39] <IdleOne> heh
[08:44] <BUGabundo_remote> morning
[08:47] <ideasman42> Hi there, Im `an upstream` and being requested to license every file in my project before distrobution, what does this mean for binary files?
[08:54] <ripps> ideasman42: that's probably a better question for #ubuntu-motu, but as far as I understand it, we're legally not allowed to redistribute your software unless it's published under gpl, cc, bsd, etc. By licesning it as such, you've given us permission to package it for debian/ubuntu without you coming to sue for theft later down the road.
[09:12] <ideasman42> ripps, its totally GPL/Creative commons
[09:12] <ideasman42> but I wasnt sure how to lisence 3D models
[09:12] <ideasman42> As in practically how to include the license
[09:14] <ripps> ideasman42: *shrugs* I wouldn't know, I think most packages just but a COPYING file in the root directory of source that states what the license of the entire source is, just to be safe. Once again, probably a better question for the MOTU's
[09:15] <ideasman42> thanks, Ill ask in that room
[11:15] <duffydack> oo, firefox 3.6 installed
[11:26] <ripps> Hmmm.... It seems that I still have HAL installed, wasn't that supposed to be removed by now? Should I just remove it?
[11:52] <yofel> ripps: I don't know about ubuntu, but at least kubuntu still needs it
[12:02] <vish> ripps: it was brought back in.. [some process depended on it] i forgot :s
[12:28] <mazda01> crimsun, well, how can unmonopolize the sound card. im telling you, it's that "system testing" within the system, admin menu
[13:02] <Q-FUNK> any suggestion for Bug #512673 ?
[13:03] <yofel> Q-FUNK: can you run 'firefox' from a terminal and see what you get?
[13:03] <Q-FUNK> yofel: I get nothing.  no stderr output whatsoever.
[13:03] <yofel> o.O
[13:04] <Q-FUNK> it just exists immediately
[13:04] <Q-FUNK> exits
[13:05] <yofel> not sure, maybe ask in #ubuntu-mozillateam
[13:05] <Q-FUNK> ah, we have such a channel?
[13:05] <yofel> yep ;)
[13:08] <Ian_Corne> how's the nvidia driver for lucid working out?
[13:11] <yofel> Ian_Corne: works fine, but jockey still isn't fixed afaik
[13:19] <test1122> !test
[13:26] <ripps> Q-FUNK: if i recall, alot of the problems with firefox-3.6 has to do with it's apparmor profile
[13:32] <Q-FUNK> ah, that could be worth testing. let's purge apparmor for a test.
[13:33] <Q-FUNK> ripps: nope.  still ain't it.
[13:35] <ripps> Q-FUNK: apparmor is a kernel module, you can't just purge it. Doesn't the #ubuntu-mozilla say to install firefox-3.6 from ppa:mozillateam/firefox-stable in it's topic?
[13:36] <Q-FUNK> ripps: that package has entered lucid toda
[13:38] <Q-FUNK> brb
[13:43] <BluesKaj> 'morning folks
[13:43] <Italian_Plumber> Hello.  The installation CD asks me what packages I want to install (Lamp, DNS, etc)... does it get those packages from the CD or from the web?
[13:43] <Q-FUNK> re
[13:43] <Q-FUNK> purging all apparmor packages and rebooting still doesn't fix it.
[13:45] <BluesKaj> Italian_Plumber, depends on your choice of applications and which live cd , some apps may be on the others will be downloaded ,
[13:45] <BluesKaj> on the cd
[13:45] <BluesKaj> BBL
[13:48] <Italian_Plumber> That's what I thought.  Thanks!
[13:49] <Italian_Plumber> I wanted to make sure that I switched over to my local apt-cacher before installing or updating.
[13:50] <yofel> Q-FUNK: there's usually no need to purge apparmor, just 'sudo service apparmor stop' ...
[13:50] <yofel> Q-FUNK: also, the firefox apparmor profile belongs to the firefox package, not apparmor
[13:51] <Q-FUNK> right, so it would have been updated prior to upload
[13:53] <Q-FUNK> actually, the reason why "firefox" won't report anything is because it's a shell script, plus it doesn't have -e set
[13:53] <Q-FUNK> directly launching /usr/lib/firefox-3.6/firefox-bin reports this, though:
[13:54] <Q-FUNK> usr/lib/firefox-3.6/firefox-bin: error while loading shared libraries: libxul.so: cannot open shared object file: No such file or directory
[14:14] <Italian_Plumber> Is this normal?  http://pastebin.com/m6442658b  what's with all the "none"s?
[14:23] <BluesKaj> Italian_Plumber, http://pwet.fr/man/linux/commandes/posix/df
[14:28] <BluesKaj>  I'm getting a bit fed up with dirs dying unexpectedly
[14:28] <pif> hi, how do I install a firefox language pack? I now have 3.6 with an incompatible language pack
[14:28] <Q-FUNK> yofel: ah. launching firefox with -safe-mode works, so I'm guessing that some extension or non-default setting is the culprit but which one?
[14:30] <Q-FUNK> pif: I'm guessing that updated language packs will be uploaded soon.
[14:30] <BluesKaj> firefox is becoming a problem for some , I think mozilla is rushing the newer versions out the door too quickly
[14:30] <pif> aha, ok, what are their names? I can't find them for 3.5
[14:31] <Q-FUNK> BluesKaj: I hope that LTS+1 would dump firefox in favor of chromium.
[14:32] <Q-FUNK> pif: they are a part of the normal language packs.
[14:32] <BluesKaj> Q-FUNK, I'm using chrome-beta for linux , chromium seems differnt and clunkier , altho I can't understand wgy
[14:32] <BluesKaj> why
[14:33] <pif> Q-FUNK: ok
[14:33] <BluesKaj> Q-FUNK, altho they look exactly alike :)
[14:34] <Q-FUNK> BluesKaj: here, I have chrome-beta on debian and the daily PPA chromium builds on lucid.  works nicely.
[14:35] <BluesKaj> Q-FUNK, good to hear
[14:36] <Q-FUNK> I think that the sooner we get debian's help to sort out the copyright and authorship of everything that's bundled with chromium source, the better this can become group maintained an turned into something really solid.
[14:44]  * yofel uses chromium when he needs to use websites that don't respect the system color sheme *-.-
[14:44] <yofel> having black text in a black input box is... not very useful
[14:46] <yofel> chromium doesn't apply any system colors at all
[14:48] <Italian_Plumber> you're so nice.  "it's..... not very useful" :)
[14:58] <BluesKaj> yofel, ff wasn't rendering some pages correctly , whereas chrome and konqueror do a bit better , not always and they've made konq so complicated to setup as a browser that it's not worth the trouble anymore
[14:59] <yofel> heh, well I use firefox most of the time, dropped konqueror long ago, but chromium is pretty nice
[15:20] <switchgirl> where can i d/l the latest version of the lts?
[15:20] <switchgirl> *lucid lynx
[15:22] <FiremanEd> check the topic
[15:23] <bjsnider> !daily-live
[15:23] <yofel> FiremanEd: please read that page (especially the known issues page)
[15:23] <bjsnider> !daily
[15:24] <yofel> FiremanEd: and you might want to try a daily image too like bjsnider indicates ;)
[15:24] <Italian_Plumber> Like that lucid server now tells you when a system restart is required. :)
[15:24] <FiremanEd> Already on Lucid, pardon the fragmented text on channel
[15:30] <Italian_Plumber> Is this something you would do: put together a lucid box now, with plans to update after April 29th and start using that box as a production machine?
[15:33] <yofel> FiremanEd: sry, I was busy following a few channels and got the wrong person in the end -.-
[15:33] <FiremanEd> yofel: no worries
[15:33] <yofel> Italian_Plumber: well, I would only install lucid now if you actually plan to help on testing, if you want don't then it's better to at least wait for beta
[15:34] <yofel> I usually use my lucid desktop as the primary desktop and have backups and a second pc if something goes wrong
[15:34] <Italian_Plumber> I should have added "as a server"
[15:36] <yofel> hm...........
[15:37] <yofel> If you really like bleeding edge, then do it, I have lucid running on my home-network server, but I strongly recommend daily backups in this case
[15:37] <yofel> so you can just revert any updates
[15:38] <Italian_Plumber> I guess I'm more concerned if that would be a good setup after the machine goes into production.  If something goes wrong before then, I won't cry. :)
[15:38] <FiremanEd> keyword is Bleeding Edge.  Expect things to be broken here and there
[15:38] <Italian_Plumber> yeah, good point.
[15:43] <dholbach> Day 2 of https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in #ubuntu-classroom (on irc.freenode.net) in 17 minutes!
[15:57] <switchgirl> the sourcefile is corrupted on http://cdimage.ubuntu.com/releases/lucid/alpha-2/lucid-desktop-i386.iso
[15:58] <yofel> switchgirl: really? lemme test
[15:59] <bjsnider> if true, let them know in the motu channel
[16:00] <Italian_Plumber> I downloaded the torrent yesterday with no problems.
[16:39] <om26er> !test
[16:46] <yofel> !ping
[17:29] <mileslane> Can anyone here answer questions about problems with Grub2?
[17:30] <mileslane> I installed Wubi 9.10 and then upgraded to Lucid.  I find that the new Lucid kernel won't boot and neither will my custom kernel builds.
[17:31] <yofel> mileslane: did you try to disable 'splash' on boot? Plymouth does seem to cause an unbootable system sometimes
[17:34] <mileslane> yofel:  Yes, I did try this.  My attempts to boot a custom kernel fail with a message saying that the kernel must be loaded first.
[17:34] <yofel> o.O
[17:36] <mileslane> yofel:  My attempts to boot the latest Lucid kernel fails differently.  IIRC, the message indicates a problem mounting the root filesystem (loopmounted from an NTFS partition)
[17:40] <yofel> well, I don't think I can help you, I don't know anything about WUBI, and I've never seen that error
[17:40] <onetinsoldier> hi all
[17:40] <mileslane> yofel:  Thanks.
[17:42] <onetinsoldier> can anyone who has upgraded to the latest tell me if firefox 3.6 is working ok in lucid? safe to go ahead and upgrade? if no one knows, i'll find just upgrade and find out. i was just curious before i go ahead ;-)
[17:43] <CosmiChaos> well i never saw firefox broke for me and i tried since karmic various alphas betas and now 3.6, i see no point
[17:43] <CosmiChaos> onetinsoldier, remember always to backup your person data especially when upgrading to a alpha/beta
[17:44] <onetinsoldier> CosmiChaos: roger. so, you haven't had a working firefox 3.6 yet?
[17:44] <CosmiChaos> onetinsoldier, well no but i really use chromium-browser for daily things
[17:44] <onetinsoldier> CosmiChaos: oh yes. i know about running debian 'sid' type beta OS
[17:45] <CosmiChaos> i just have it right there sometimes checking if chromium-daily broke :D
[17:45] <onetinsoldier> CosmiChaos: ok, roger. thanks :-)
[17:45] <onetinsoldier> well, here goes
[17:45] <CosmiChaos> onetinsoldier, this is not ubuntu nor linux relatet, always backup productive data when testing out new developement software
[17:45] <CosmiChaos> thats the point
[17:46] <onetinsoldier> no doubt. and, i do!
[17:46] <onetinsoldier> it's like someone said the other day. data that has not been backed is not important data
[17:47] <onetinsoldier> in other words, if it had been important data, then it would already be backed up
[17:47] <CosmiChaos> you most likely fit it when sepratiing a /home partition
[17:47] <CosmiChaos> ;)
[17:47] <onetinsoldier> it you lose data, it must not have been that important ;-)
[17:48] <CosmiChaos> see it other way around: backup is for people that freightens the loss of their data
[17:48] <CosmiChaos> if you dont fear downloaded bs sure you need no backup :D
[17:48] <DanaG> Better way to word things: For important data, always make sure it exists in at least two dfiferent, physically independent places.
[17:49] <CosmiChaos> DanaG, well you can dig the pc into a bunker too in case bombs will be dropped xD
[17:49] <acicula> what does UBUNTU: SAUCE stand for in the kernel git messages
[17:49] <DanaG> Ubuntu's "secret sauce" -- their tweaks to the kernel.
[17:50] <CosmiChaos> its ubuntus' sauce :)
[17:50] <onetinsoldier> a saucy and sassy kernel? heck, i don't know
[17:50] <acicula> is the SAUCE maintained separate from the upstream fixes , cant really tell from looking at the git page
[17:51] <onetinsoldier> what DanaG said. i know they add a couple things in the lucid kernel, suach as some filesystem called 'aufs' i think it was.... then a SELinux measure called 'apparmor'
[17:51] <onetinsoldier> such*
[17:52] <CosmiChaos> i need to know sauce for what?
[17:52] <acicula> CosmiChaos: u dont , unless you are poking around the kernel git tree
[17:53] <CosmiChaos> i just read the kernel daily digest, thats enough for some years :)
[17:54] <CosmiChaos> in fact i break my head at most of the very first sign that the replys start with, but well :)
[17:54] <DanaG> when'll ubuntu get 2.6.33?
[17:54] <CosmiChaos> wasnt it at no time?
[17:54] <Pici> I don't think we will
[17:54] <onetinsoldier> i'm willing to guess that lucid won't get it
[17:55] <DanaG> Even if it's PPA, that's fine.
[17:55] <DanaG> But... the ubuntu mainline builds donkernel
[17:55] <DanaG> er
[17:55] <DanaG> the ubuntu mainline builds don't have Staging drivers enabled.
[17:57] <CosmiChaos> 10.10 will likely dont get it but 2.6.34, comparing the next release feature freeze date with the possible kernel release window
[17:58] <CosmiChaos> but if 2.6.33/34 turn out to take much more time, you may have the same procedure than this release
[17:58] <acicula> so how is the ubuntu kernel tree synced with the maintained vanilla version if at all
[18:00] <CosmiChaos> DanaG, but you can always try compiling latest kernel on your own
[18:28] <simba_> are there a place where i can find the changes made day to day for lucid?
[18:29] <Pici> simba_: https://lists.ubuntu.com/mailman/listinfo/lucid-changes
[18:30] <simba_> Pici, thank you
[18:30] <onetinsoldier> you could also install 'apt-listchanges'
[18:30] <onetinsoldier> if you have lucid installed that is ;-)
[18:33] <Pici> apt-listchanges is a must-have for testing imo. Also for any LTS or server isntall.
[18:34] <simba_> onetinsoldier, will do that to..just reinstalled, and is only offered a partial update now...
[18:34] <onetinsoldier> simba_: roger. cheers and good luck :-)
[18:34] <tsimpson> you can also see the changelog of a package with "aptitude changelog <package>"
[18:35] <onetinsoldier> nice tsimpson
[18:37] <h0rnman> good morning everyone
[18:38] <simba_> morning,
[18:38] <onetinsoldier> hello there
[18:40] <simba_> tsimpson,  hmm aptitude changelog might not work if you only have partial upgrade avail, it seems.
[18:40] <h0rnman> a question for those who know more than me....in Lucid, which configuration file controls the execution of rc.<whatever> scripts?  More clearly, perhaps, which file controls runlevel changes.  in Debian, i believe it is /etc/inittab, but I do not see an equivalent in Ubuntu
[18:41] <tsimpson> simba_: it should go off whatever sources/versions apt sees
[18:42] <simba_> tsimpson, yes, it triet to fetch the file but i guess it is not updated to the mirror i use yet.
[18:42] <tsimpson> it's hard-coded to use changelogs.ubuntu.com
[18:44] <onetinsoldier> h0rnman: i don't know. you might need to look at a package named 'upstart'
[18:44] <simba_> tsimpson, yea i didnt notice "E: Couldn't fetch URL http://changelogs.ubuntu.com/changelogs/pool/main/g/gnome-control-center/gnome-control-center_2.29.6-0ubuntu1/changelog"
[18:44] <Pici> !upstart | h0rnman more info here
[18:44] <onetinsoldier> thanks Pici
[18:45] <h0rnman> ah...excellent....thank you
[19:31] <komputes> What has happened to /proc/bus/usb/ in Lucid? I am trying to mount usb as defined here (instructions for karmic): https://help.ubuntu.com/community/VirtualBox/USB
[19:40] <genii> komputes: "Note: Only the non-free version has USB support at present."     So you're using the commercial paid VBox version then?
[19:59] <komputes> genii: PLUE, it's free, just not GPL friendly
[20:01] <charlie-tca> Don't have to use paid version, but usb in version 3. plus is installed automatically now, you don't have to do anything special to mount it
[20:04] <charlie-tca> komputes: you got virtual box to install in lucid?
[20:05] <komputes> charlie-tca: yeah, that was never an issue for me
[20:05] <charlie-tca> I couldn't get it to work yet, a couple of days ago
[20:05] <komputes> charlie-tca: from the web site or from the repositories? PLUE or OSE?
[20:05] <charlie-tca> website
[20:06] <charlie-tca> I gave up on OSE, it is too limited for what I need
[20:06] <komputes> charlie-tca: what error/issue did you get/have?
[20:06] <charlie-tca> kernel was wrong
[20:07] <charlie-tca> I will have to try it again. Are you installing the karmic version in lucid?
[20:08] <arand> Soo, yahoo as the default search engine in FF Lucid, how nice..
[20:09] <myrradin> why not bing?
[20:10] <arand> One step at the time, I guess.
[20:11] <arand> Boiled frog idea you know.
[20:11] <myrradin> no, i dont.  what do you mean.
[20:13] <arand> Drop a frog in boiling water and it will jump out and survive, drop the frog in slowly heated water and it will boild to death.
[20:15] <simba_> i tried bing when i was running w7, i ended up typing google in the bing search.
[20:15] <myrradin> so you're saying we're going to boil google to death?
[20:18] <arand> myrradin: We're the frogs, right? If they switched to Bing and got paid by MS I figure quite a lot of people would simply jump ship, yahoo is a conveniently small step that people might complain like crazy, but still stick with it for the time being.
[20:19] <arand> I hope honestly it is a bad joke, alas, april is far away..
[20:19] <myrradin> oh is this part of the firefox foundation recommending everyone use bing
[20:22] <arand> Nah, recent post on the mailing list: https://lists.ubuntu.com/archives/ubuntu-devel/2010-January/030065.html
[20:22] <arand> "Canonical has negotiated a revenue
[20:22] <arand> sharing deal with Yahoo!"
[20:23] <myrradin> if it makes canonical some money , great !
[20:23] <myrradin> if they magically fix iwlwifi and intel, wonderful !
[20:24] <arand> Maybe, but I still don't think it's a good decision..
[20:26] <arand> Yahoo is a horrible page and will make ubu look bad.. I guess they might do something cleaner with the startpage, but still, every single search...
[20:27] <myrradin> that's ok.  one day yahoo will be a meta redirect to Bing
[20:29] <arand> Hmm, I guess so, *sigh*
[20:32] <xguru> anyone else's firefox break with today's updates?
[20:34] <simba_> xguru, update-manager refuse to upgrade firefox here...
[20:35] <IdleOne> I say we blame yahoo
[20:35] <xguru> http://pastebin.com/d571fca4d
[20:36] <onetinsoldier> xguru: my upgrade went fine. i'll look at your pastebin here in a moment
[20:36] <robin0800> xguru: works here too
[20:36] <xguru> when i launch it with the desktop launcher it crashes, it crashes in terminal, then alt+f2 gksu firefox ....that works fine
[20:37] <onetinsoldier> xguru: i don't know what 'libmoonloaderxpi' is yet, but i don't have that installed...
[20:37] <xguru> onetinsoldier: its a linux version of silverlight
[20:39] <onetinsoldier> ok, i'm not fmailiar with that either. but perhaps you could enlighten me. i noticed that a search for 'loaderxpi' doesn't come with anything. is this a piece of third party software?
[20:40] <robin0800> xguru: perhaps libmoonloaderxpi is not compatible with version 3.6
[20:41] <xguru> onetinsoldier: its a plugin from novell that allows me to listen to music from websites....thats about all i know
[20:41] <xguru> robin0800: i can't find it being installed in synaptic
[20:42] <onetinsoldier> xguru: roger. cool
[20:42] <simba_> moonlight-plugin-mozilla?
[20:43] <simba_> think that was the linux version of silverlight
[20:43] <xguru> simba_: I know i had it installed prior to the update, but it shows not installed in synaptic
[20:44] <xguru> anyhow i still dont know why it works with gksu firefox
[20:44] <onetinsoldier> a newer version is out than what's available in ubuntu
[20:44] <onetinsoldier> of the moonlight software
[20:45] <simba_> the v1 works better that the v2 when connecting to some places
[20:45] <voidmage> so if i don't have moonlight is the 3.6 upgrade in the repositories safe?
[20:45] <DanaG> if you ran firefox as root, your firefox profile is likely OWNED by root.
[20:46] <onetinsoldier> voidmage: yes
[20:48] <yofel> xguru: can you try if it works if you stop apparmor?
[20:48] <yofel> xguru: and did you try it with a new profile?
[20:50] <xguru> yofel: how do i disable apparmor?  And i have not tried with a new profile
[20:50] <yofel> xguru: 'sudo service apparmor stop'
[20:52] <yofel> xguru: and you can create a new Profile if you start firefox with -ProfileManager
[20:53] <xguru> yofel: creating a new profile did the trick....any ideas what might have caused the confusion?
[20:54] <xguru> yofel: i restarted apparmor and got this... http://pastebin.com/d4d68e641
[20:56] <yofel> xguru: apparmor is ok
[20:56] <sbeattie> xguru: just means the the apparmor policies for firefox have been disabled, so apparmor shouldn't be preventing firefox from doing anything.
[20:57] <yofel> xguru: and if a new Profile works I usually suspect some user addon/plugin to be at fault
[20:57] <yofel> xguru: did you install moonlight on OS or user level?
[20:57] <sbeattie> (if it is, you should see rejections show up in your dmesg|/var/log/kern.log)
[20:58] <xguru> OS
[20:59] <xguru> thanks everyone for the help!  learned something new :)
[20:59] <yofel> xguru: ok, then it should be used in a new Profile as well, you could try to launch the old profile with -safe-mode, disable all addons and enable them one-by-one again
[20:59] <yofel> bug you first need to re-enable the old profile first
[20:59] <yofel> in the ProfileManager
[21:02] <xguru> yofel: started with all plugins disabled.  I enabled them all.  Restarted firefox and everything is fine.  I then added the extension moonlight (which seemed to be the problem) and restarted with everything being fine.
[21:04] <yofel> heh, fixed itself
[21:05] <dupondje> finally fixed the aptitude bug :) hope it gets into Lucid now :)
[21:05] <onetinsoldier> dupondje: what bug is that?
[21:06] <onetinsoldier> did you file a bug?
[21:06] <dupondje> https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/391035
[21:06] <onetinsoldier> duffydack: roger
[21:06] <onetinsoldier> oops, sorry duffydack
[21:06] <dupondje> :p
[21:06] <onetinsoldier> dupondje:
[21:07] <onetinsoldier> dupondje: :)
[21:08] <dupondje> I forgot again who I need to add to get sponsoring :p
[21:13] <dupondje> ubuntu-main-sponsors is already added :)
[21:13] <onetinsoldier> oh :)
[21:15] <dupondje> now we need to slap some developper :)
[21:16] <onetinsoldier> a lot of the time there are some in here :-)
[21:17] <dupondje> but not when you need them :D
[21:17] <onetinsoldier> of course not! :D
[21:40] <edgy> hi, I have grub  0.97-29ubuntu59 and grub-common 1.98~20100101-1ubuntu2 installed, so do I have grub 1 or 2 now?!
[21:45] <onetinsoldier> edgy: what does dpkg -l grub-pc say?
[21:45] <onetinsoldier> edgy: what does 'dpkg -l grub-pc' say?
[21:46] <edgy> onetinsoldier: un  grub-pc                         <none>
[21:46] <onetinsoldier> hmmm
[21:46] <simba_> edgy, do you have /boot/grub/menu.list or /boot/grub/grub.cfg?
[21:47] <edgy> simba_: yes I have both files
[21:48] <edgy> what's the version you have in lucid installed by default?
[21:48] <onetinsoldier> ii  grub-pc                        1.98~20100101-1ubuntu2         GRand Unified Bootloader, version 2 (PC/BIOS version)
[21:49] <DanaG> hmm, #ubuntu-kernel seems pretty quiet most of the time.
[21:50] <edgy> onetinsoldier: you have grub2 package also installed?
[21:50] <onetinsoldier> grub-pc = grub2
[21:50] <edgy> onetinsoldier: but there is a separate package called grub2
[21:50] <onetinsoldier> un  grub2                          <none>
[21:50] <onetinsoldier> nope
[21:51] <edgy> onetinsoldier: and the package grub is also un?
[21:51] <edgy> onetinsoldier: I would install grub-pc then, do you expect i would face a problem?
[21:51] <onetinsoldier> yes... if you were you, i'd consider doing something like purging the old and and installing the new --> grub-pc
[21:52] <onetinsoldier> maybe make a copy of your menu.lst file first
[21:53] <onetinsoldier> i bet it's a little scary here for ya edgy ;-)
[21:54] <onetinsoldier> just make sure you have everything backed up
[21:54] <edgy> onetinsoldier: ok I will put my hand on my heart and do it and reboot, please don't evaporate from the channel ;)
[21:55] <onetinsoldier> ok, good luck! :-) grub-pc(grub2) seems to work pretty nicely though :)
[21:55] <onetinsoldier> so i think you'll be ok
[22:19] <dupondje> where are those sweet developpers :P
[22:25] <acicula> in the sweatshop below, hammering out sweet sweet code
[22:33] <edgy> onetinsoldier: this is just to say thanks. it works ;)
[22:37] <onetinsoldier> edgy: hi! you're welcome. congrats :-)
[22:43] <edgy> what about fgrlx does it work? I mean can I install those drivers for ati from jockey or should I wait?
[22:44] <edgy> fglrx I mean
[22:45] <onetinsoldier> they won't work for now
[22:46] <onetinsoldier> the Xorg version. they ati fglrx drivers haven't been made to work with it yet
[22:46] <onetinsoldier> there *is* a fix to get them to install into the kernel version that's in Lucid... but alas, they don't work with Xorg 7.5 yet
[22:48] <edgy> good you told me. thanks
[22:48] <onetinsoldier> cheers
[22:49] <edgy> now lucid looks very nice for me. I love it. and this is my main system. normally you keep updating every day or just leave it till another beta comes and then update?
[22:49] <DanaG> hmm, never did get an answer about the staging drivers in the mainline builds.
[22:50] <onetinsoldier> i installed just a couple of hours after the Alpha2 was released. since then, i've been updating every day, so far anyway. don't know if i'll keep updating that often or not
[22:52] <onetinsoldier> DanaG: i wouldn't know or anyting? but, you mean for grub2? i'm just guessing
[22:53] <onetinsoldier> what are staging drivers?
[22:54] <acicula> edgy: updating is a double edged sword, you risk stuf breaking but want some updates :P
[22:55] <onetinsoldier> oh, i see there's a bunch of staging drivers in the kernel
[22:57] <acicula> DanaG: http://lwn.net/Articles/359208/
[22:58] <acicula> appearantly the criterium for staging drivers is that it must compile, makes sense to leave it out i guess
[23:08] <onetinsoldier> yes! kernel compiled and .deb packages built :)
[23:08] <DanaG> acicula: the thing is, the whole staging MENU is disabled... not just specific drivers.
[23:09] <DanaG> oh, and I keep getting hangs with "execbuf while wedged".


[19:34] <flocculant> slickyma1ter: anything being done to slideshow this cycle - other than s/17.04/17.10 ?
[19:34] <flocculant> revamping for next lts perhaps?
[22:19] <flocculant> bluesabre: quick question ... would not 'Clear History' imply 'Clear whatever random playlist' you've got kicking about?
[22:21] <flocculant> I'd make the assume that any 'clar hist' in any app assumes I mean 'any' history at all
[22:26] <flocculant> doesn't appaer to be quite right, but once more stuck in this 'no-one from Xubutu's team appears to actually test things apart from 2 people'
[22:27] <flocculant> and then it all breaks on release
[22:27] <flocculant> I'm really fed up with that :(
[22:28] <flocculant> bluesabre: seriously we need to do somethign about hat
[22:28] <flocculant> if Testing can't even get the maintainer to report - then we stand NO CHANCRE
[22:29] <flocculant> sigh
[22:29] <flocculant> SHANCE#
[22:29] <flocculant> sigh
[22:29] <flocculant> I don't care enough
[23:08] <Unit193> I'm still running Artful and testing the new shiny things I'm pushing on others...
[23:08] <Unit193> Only thing I have held right now is one panel plugin, the load one.
[23:22] <flocculant> well
[23:22] <flocculant> I do as I can
[23:23] <flocculant> but the notifier thing does nout


[00:08] <marcoceppi> magicaltrout: yeah, apt get install charm-tools; then you can do `charm create` (sans the -) ;)
[08:29] <jamespage> dosaboy, can you cast your eye over https://code.launchpad.net/~james-page/charm-helpers/fixup-service-running/+merge/294942
[08:40] <dosaboy> jamespage: sure
[08:40] <jamespage> dosaboy, ta - I was looking for the testing that beisner did yesterday - but he must of done it offline I think
[08:42] <dosaboy> jamespage: i just realised that since your fix for 1580320 is ceph-osd only and some amulet tests use ceph for osds it won't apply so tests will still fail
[08:42] <dosaboy> so i have a tmp workaround
[08:43] <jamespage> dosaboy, I can apply to ceph as well
[08:43] <dosaboy> jamespage: that would be the easy fix ;)
[08:43] <dosaboy> or we could get teh amulet tests using ceph-mon+ceph-osd
[08:43] <dosaboy> but that means more resources for each test
[08:43] <dosaboy> test run that is
[08:44] <dosaboy> jamespage: i'm working around it with https://review.openstack.org/#/c/314063/10..11/tests/basic_deployment.py for now
[08:48] <jamespage> dosaboy, https://review.openstack.org/#/c/317910/
[10:44] <jamespage> dosaboy, beisner: raised https://bugs.launchpad.net/juju-core/+bug/1583109
[10:44] <mup> Bug #1583109: error: private-address not set <juju-core:New> <https://launchpad.net/bugs/1583109>
[11:51] <gennadiy> hi everyone, is it possible to deploy custom openstack image from juju charm?
[11:51] <gennadiy> we have a few snapshots and we want to use them in our charms
[11:52] <gennadiy> seems it's not 'true' juju way
[11:55] <jamespage> beisner, shall we land the ch fix for service_running and then generate the master branch re-syncs?
[11:55] <jamespage> that would exercise this bug well
[11:55] <beisner> jamespage, sounds good.  just confirming that the trace log gets enabled as planned on 1 short run now.
[11:56] <jamespage> beisner, okies
[11:56] <jamespage> going to eat lunch
[12:22] <simonklb_> anyone familiar with the sync-watch plugin? for some reason it's causing two updates each time I re-build my charm - any idea why?
[12:43] <jamespage> beisner, ok going to raise reviews for resyncs right now
[12:43] <beisner> jamespage, merging your c-h thing now
[12:43] <jamespage> beisner, already done
[12:43] <beisner> jamespage, oh you beat me to it
[12:43] <jamespage> just pushed it
[12:43] <beisner> ha, good deal
[12:55] <jamespage> dosaboy, what's your bugref for the IPv6 thing?
[12:57] <beisner> jamespage, skip ceilometer-agent.  i've got a review that i'll just resync and append.
[12:59] <dosaboy> jamespage: there's this one for the charm bug - https://bugs.launchpad.net/charm-helpers/+bug/1581598
[12:59] <mup> Bug #1581598: ipv6 enabled charms don't understand mngtmpaddr flag <ipv6> <openstack> <sts> <Charm Helpers:In Progress by hopem> <ceilometer (Juju Charms Collection):In Progress by hopem> <ceph (Juju Charms Collection):In Progress by hopem> <ceph-mon (Juju Charms Collection):New> <ceph-osd (Juju
[12:59] <mup> Charms Collection):In Progress by hopem> <ceph-radosgw (Juju Charms Collection):New for hopem> <cinder (Juju Charms Collection):In Progress by hopem> <glance (Juju Charms Collection):In Progress by hopem> <heat (Juju Charms Collection):In Progress by hopem> <keystone (Juju Charms Collection):In
[12:59] <mup> Progress by hopem> <neutron-api (Juju Charms Collection):In Progress by hopem> <nova-cloud-controller (Juju Charms Collection):In Progress by hopem> <nova-compute (Juju Charms Collection):In Progress by hopem> <openstack-dashboard (Juju Charms Collection):In Progress by hopem> <percona-cluster
[12:59] <mup> (Juju Charms Collection):In Progress by hopem> <rabbitmq-server (Juju Charms Collection):In Progress by hopem> <swift-proxy (Juju Charms Collection):In Progress by hopem> <swift-storage (Juju Charms Collection):In Progress by hopem> <https://launchpad.net/bugs/1581598>
[12:59] <jamespage> dosaboy, beisner: OK re-running now with amended commit message - I'd not raised any reviews just yet...
[13:00] <dosaboy> jamespage: once it all lands i can kick off an ipv6 run
[13:15] <jamespage> beisner, dosaboy: ok here they come
[13:16] <jamespage> https://review.openstack.org/#/q/status:open+branch:master+topic:bug/1581171
[13:16] <mup> Bug #1581171: pause/resume failing (workload status races) <landscape> <maintenance-mode> <uosci> <ceilometer-agent (Juju Charms Collection):In Progress by 1chb1n> <cinder (Juju Charms Collection):Fix Committed by thedac> <glance (Juju Charms Collection):Fix Committed by thedac> <keystone (Juju
[13:16] <mup> Charms Collection):In Progress by thedac> <https://launchpad.net/bugs/1581171>
[13:29] <kjackal> Hey lazyPower, do you have a minute? Its about an exception I am getting when I stop filebeats.
[13:29] <lazyPower> sure, whats up?
[13:29] <kjackal> https://pastebin.canonical.com/156708/
[13:30] <kjackal> Let me also tell you what i am deploying
[13:30] <lazyPower> I've seen this before kjackal
[13:30] <kjackal> https://pastebin.canonical.com/156709/
[13:30] <kjackal> Do we know what it is?
[13:30] <lazyPower> unit-filebeat-0[15988]: 2016-05-18 13:06:11 INFO unit.filebeat/0.stop logger.go:40 subprocess.CalledProcessError: Command '['relation-list', '--format=json', '-r', 'elasticsearch:5']' returned non-zero exit status 2 <--  its trying to call relation-list on a relation thats been removed right?
[13:31] <lazyPower> i only got this once, and was unable to reproduce it
[13:31] <lazyPower> is the unit still alive?
[13:31] <kjackal> yes
[13:31] <lazyPower> paydirt. is the ES unit still alive?
[13:32] <kjackal> yes, the entire deployment is online
[13:33] <lazyPower> hmm.. when i encountered this, the beat subordinate did not have an active relation, and the scope.unit relation interfaces were still trying ot contact a disconnected elasticsearch unit
[13:33] <lazyPower> perhaps thats not the problem here
[13:33] <kjackal> waitup
[13:34] <lazyPower> which makes me think i should go peek at the elasticsearch interface to make sure i'm removing its .available state
[13:34] <kjackal> how do you check if you have active relations?
[13:35] <lazyPower> either via juju status, the gui, or by running the relation-* hookenv cmds on the unit
[13:35] <lazyPower> kjackal i think i found the root of the issue though
[13:35] <lazyPower> https://github.com/juju-solutions/interface-elasticsearch/blob/master/requires.py#L32
[13:36] <lazyPower> reactive is doing exactly what i told it to do. the .available state is still set,  (notice i only remove .connected) - so its hitting its cached data
[13:36] <lazyPower> and trying to reference that relationship because its still marked as active (i think this all true, cory may mythbust me)
[13:36] <kjackal> :)
[13:37] <lazyPower> kjackal - has this been happening consistently?
[13:37] <lazyPower> or is this the one-off that got hung up?
[13:37] <lazyPower> s/the/a
[13:37] <kjackal> it happened in two seperate deployment
[13:38] <kjackal> and i can reproduce it by jujuresolved --retry
[13:38] <lazyPower> ok let me grab a coffee and i'll push a fixed publish to my namespace
[13:38] <lazyPower> if it works out, we'll bump the store revision
[13:39] <kjackal> sounds good
[13:42] <kjackal> so we need something line @when (elastic search available AND connected) call cache_elasticsearch_data(...)
[13:42] <kjackal> let me try that
[13:42] <lazyPower> kjackal - think is, .available presumes .connected
[13:43] <lazyPower> as .available is only ever set when we've gotten the connection string data we expect
[13:43] <lazyPower> i think the problem lies in not removing that .available state on that conversation object
[13:44] <lazyPower> kjackal https://github.com/juju-solutions/interface-elasticsearch/pull/6
[13:45] <kjackal> let me try to test this... it will take some time...
[13:47] <kjackal> Ha! I believe the charm is killed now!
[13:47] <lazyPower> yeah?
[13:47] <kjackal> Yes, it seems to work!
[13:48] <kjackal> Good job lazyPower!!! Not so lazy!!!
[13:48] <kjackal> :)
[13:48] <lazyPower> :) Thanks
[13:49] <kjackal> So, do you have any eta on when this will be available?
[13:49] <kjackal> Do you want me to merge it?
[13:49] <lazyPower> url: cs:~lazypower/filebeat-0
[13:50] <lazyPower> give that a go in place of the store url if you dont mind. i'd like an a-z test before we merge this assuming its fixed
[13:50] <kjackal> let me do a full deployment with that charm
[13:51] <kjackal> These easy fixes are too good to be true! But I am optimistic!
[13:51] <lazyPower> :)
[13:51] <lazyPower> I am as well
[13:51] <lazyPower> i'm curious why this wasn't rooted out i the bundle tests
[13:51] <lazyPower> *in
[13:52] <beisner> jamespage, dosaboy, thedac, tinwood - fyi - i'll be doing some readme-only change/reviews and landing them to iterate a bit on gerrit change-merged stream advertisements and triggers wrt getting charm upload jobs set up in the chain.  just no-op noise, safe to ignore.
[13:54] <kjackal> lazyPower could I have also a url for topbeat? The fix is in the beats_base and affects all beats charms
[13:54] <lazyPower> sure, 1 sec and i'll rebuild that as well
[13:55] <kjackal> thank you
[13:56] <lazyPower> url: cs:~lazypower/topbeat-0
[14:00] <gahan> I'd like to update /etc/neutron/dhcp_agent.ini using juju (as it is maintained by juju). can someone enlighten me how to achieve through cli or gui?
[14:01] <cory_fu> I forget, does quickstart work with bundles that reference local: charms?
[14:01] <lazyPower> beisner - i know we've exposed config points for cinder like this, where you can modify config with a sub. Is this also true with neutron that you're aware of? (re: gahan's question above)
[14:01] <lazyPower> cory_fu negative
[14:01] <cory_fu> Blast and damn
[14:02] <lazyPower> thats why deployer was so long-lived
[14:02] <lazyPower> that and its wrapped by our testing tooling
[14:02] <beisner> gahan, curious, what specifically are you needing to mod?
[14:04] <gahan> beisner: I heard if I modify dhcp_domain field in mentioned .ini file, it wil change the value of field "search" in /etc/resolv.conf for all new instances in openstack
[14:07] <beisner> gahan, indeed, in liberty and prior you could do that there (ref:  http://docs.openstack.org/liberty/config-reference/content/section_neutron-dhcp_agent.ini.html) ... but it was deprecated and removed @mitaka.  i'm not sure where the equivalent is off hand.
[14:08] <gahan> beisner, I'm still using liberty :) thanks
[14:08] <beisner> gahan, typically, any adjustments to those confs must be done via charm config values.  if you modify the file by hand, your changes will be overwritten when the conf is re-rendered from templates by the charm, which could happen at any time.
[14:09] <gahan> it doesn't seem like this particular one is exposed or I'm looking in wrong place
[14:09] <beisner> gahan, we'd need to add a charm config option, but also figure out what it means for mitaka and later.  i'd imagine it can be set by some other approach there.
[14:10] <beisner> gahan, right.  we don't expose 1:1 all conf options as that would be massive.  we typically encapsulate sane common defaults with knobs and levers to tune things to common needs.
[14:11] <beisner> ah, dns_domain in neutron.conf for >= mitaka it appears
[14:12] <beisner> so this *could* be added to the charm so long as the conf template rendering logic is set up to plop the config in the right file depending on release version (we do that for other things, so that framework is already there).
[14:13] <beisner> it'd have to go into the next/dev (master) charm first, which would then be released at either 16.07 or 16.10.
[14:21] <lazyPower> hmm. i haven't validated this assertion yet, but do we know when using 1.25 if i set environment constraints (eg; tags=lazypower) and then i have additional tags defined in the bundle if those are additive (eg: tags=lazypower,bundle-constraint)   or if the bundle constraints override the environment constraints
[14:21] <lazyPower> beisner i think you have experience in this ^
[14:22] <beisner> lazyPower, hmm i've only ever used constraints at bootstrap and deploy time (ie. in the bundle)
[14:22] <beisner> lazyPower, i would think the constraint in the bundle would win though
[14:22] <lazyPower> yeah i was afraid of that :/
[14:23] <lazyPower> i'm trying to come up with a good workflow to test these submissions, without stepping all over oil's toes and without modifying the bundle
[14:23] <lazyPower> i guess i'm caught in a corner where i have to mod the bundle. *snaps*
[14:23] <beisner> lazyPower, sec...
[14:25] <jamespage> beisner, I think we should put this resync through on a smoke only
[14:25] <beisner> jamespage, ack
[14:26] <beisner> jamespage, maybe kick a few fulls to try to trap this juju core bug?
[14:26] <beisner> i kicked 1
[14:26] <jamespage> sure
[14:26] <jamespage> but I'd not block +2 landing on that basis
[14:26] <jamespage> infra queue must be long.... atm
[14:27] <jamespage> UOSCI is besting it hands down...
[14:27] <lazyPower>  i think they *are* merging the tag constraints, at least thats the behavior i'm seeing with this deploy. #TIL
[14:27] <beisner> jamespage, she's a hopping atm for sure
[14:27] <beisner> lazyPower, we use this to strip or insert constraints on the fly in osci:  http://bazaar.launchpad.net/~uosci/ubuntu-openstack-ci/trunk/view/head:/tools/bundle_constrainer.py#L18
[14:28] <beisner> lazyPower, i've got a WIP refactor of that into our git namespace with other features, but that one is functional.
[14:28] <lazyPower> that would be excellent if i were generating this bundle
[14:28] <beisner> lazyPower, pull it down, pipe it through that, get 0 constraints ;-)
[14:28] <lazyPower> i think thats a big part of the disconnect here, is i'm testing an artifact of their submission, not really using the tooling OS/OIL uses
[14:29] <beisner> oh, so they have a bundle that they're proposing with abnormal constraints?
[14:29] <lazyPower> yeah
[14:29] <lazyPower> tags=openstack, or tags=nedge
[14:29] <cory_fu> arosales, kwmonroe, kjackal: Quick review of README updates for Bigtop PR: https://github.com/juju-solutions/bigtop/pull/2
[14:29] <lazyPower> we kind of need that for placement however
[14:29] <lazyPower> these charms have very strict hardware requirements, if the charms detect they are on a sub-par node, it panics and sets the charm to blocked and refuses to continue
[14:30] <beisner> lazyPower, good thing actually.  much better than mysteriously failing
[14:30] <lazyPower> yeah i'd rather it punch me in the face with a reason, than punch me in the face and tell me to go troll the logs :)
[14:33] <beisner> jamespage, yah the zuul queue is large atm
[14:33] <beisner> we have 42 of the 235 jobs queued up ;-)
[14:46] <beisner> jamespage, bahh.  ceph-mon tox ini has site_packages True, which is bad.  it failed upstream CI, but passes ours b/c we of course have that installed.
[14:46] <beisner> i pulled ceph-mon master, changed to sitepackages = False locally, and we fail identically to http://logs.openstack.org/57/318057/1/check/gate-charm-ceph-mon-python27/1ab631a/console.html
[14:47] <beisner> we need to make a pass and flip those False on any charms that have that True
[14:48] <jamespage> beisner, is apt in pypi?
[14:48] <beisner> jamespage, not sure if it is.  but it seems to me that should be mocked out anyway
[14:48] <lazyPower> jamespage sure is https://pypi.python.org/pypi/apt/
[14:50] <beisner> jamespage, i'd suspect this passed before infra started re-paving hosts in the p->t upgrade efforts.
[14:50] <beisner> or something along those lines
[14:50] <jamespage> beisner, new virtualenv disables this by default
[14:50] <beisner> either way, site packages pollute the test and will give differing results on different hosts
[14:50] <beisner> jamespage, yes, but if it's explicitly set True in tox.ini, it'll still use site packages
[14:51] <jamespage> yup
[14:51] <beisner> we might be wise to inject False in case someone fires up with an older tox or virtualenv
[14:56] <arosales> cory_fu: thanks, taking a look at the readme now . . .
[15:00] <jcastro> lazyPower: out of curiosity, have you tested the beats charms on xenial? wondering why they're trusty-only
[15:01] <lazyPower> jcastro - at the time of writing that layer their archive did not have xenial packages available
[15:01] <lazyPower> now that xenial is out, i think that may have changed. simple enough to add a series and kick off a bundle test. /me will do that later today
[15:01] <jcastro> oh ok, so blocking on upstream packages
[15:01] <lazyPower> yeah however i'm not certain thats still the case
[15:34] <lutostag> where would I file a bug for the charm store?
[15:35] <lutostag> ah there's even a link at the bottom of the page... duh ;)
[16:45] <lazyPower> lutostag - we hid it down there in hopes it would be helpful :D
[16:53] <gennadiy> hi everybody, seems i have some issues charms publishing. as example i have pushed mesos-dns charm more than 1hr ago. but haven't got in store yet.
[16:53] <gennadiy> source code - https://code.launchpad.net/~dataart.telco/charms/trusty/mesos-dns/trunk
[16:54] <gennadiy> is it possible to check what is wrong with it?
[16:54] <lazyPower> gennadiy - launchpad ingestion was broken a couple weeks ago and has been unable to be restored. we're relying on the new charm publishing features of the store to continue progress
[16:55] <lazyPower> gennadiy see: https://jujucharms.com/docs/devel/authors-charm-store
[16:56] <lazyPower> gennadiy - bright side of the inconvenience is your publishing becomes instantaneous vs the 30/60 minute ingest waiting period.
[16:58] <gennadiy> thank you @lazyPower i will review new mechanism
[17:11] <jamespage> beisner, updated https://review.openstack.org/#/c/318057/ with mocking for apt
[17:11] <jamespage> waiting for check to confirm that's OK
[17:12] <jamespage> beisner, stable syncs
[17:12] <jamespage> https://review.openstack.org/#/q/status:open+branch:stable/16.04+topic:bug/1581171
[17:12] <mup> Bug #1581171: pause/resume failing (workload status races) <landscape> <maintenance-mode> <uosci> <ceilometer-agent (Juju Charms Collection):Fix Committed by 1chb1n> <cinder (Juju Charms Collection):Fix Committed by thedac> <glance (Juju Charms Collection):Fix Committed by thedac> <keystone (Juju
[17:12] <mup> Charms Collection):In Progress by thedac> <https://launchpad.net/bugs/1581171>
[17:12] <beisner> jamespage, ack thx
[17:20] <gennadiy> @lazyPower - is it possible to remove charm?
[17:20] <lazyPower> no removal, but you can remove the permissions from the charm so only you can see it
[17:21] <lazyPower> charm grant --help
[17:21] <gennadiy> ok
[17:21] <gennadiy> another question: can we deploy specific openstack snapshot from charm?
[17:21] <lazyPower> not sure what you mean
[17:29] <gennadiy> @lazyPower - now we have snapshot/image of openstack machine and we would like to deploy it from juju.
[17:29] <gennadiy> i know that it's not 'true' way. but maybe it's possible
[17:38] <lazyPower> ah, i dont think we have any support for that, as we assume the charms to probe/setup as required. i'm not going to say its not possible, but i dont know thats a supported deployment method as of yet
[17:39] <lazyPower> there has been talk of imaging support for providers that can support it, but i have no idea where that is on the roadmap if its a next cycle thing or cycle after next.
[17:46] <gennadiy> @lazyPower - one more question: i have account https://launchpad.net/~dataart.telco but email login is<EMAIL_ADDRESS>so when i make charm login it will not allow to push to cs:~dataart.telco/sipp
[17:46] <gennadiy> as i understand it calculates name by primary email. am i right?
[17:46] <lazyPower> launchpad name, or launchpad group actually
[17:47] <lazyPower> its still backed by the mechanisms (groups, acls, etc) inherited by ubuntu SSO
[17:49] <gennadiy> hm. "charm push . cs:~dataart.telco/sipp" returns error "unauthorized: access denied for user "tads2015dataart" but https://launchpad.net/~dataart.telco it's me
[17:50] <gennadiy> a few mouth ago i renamed account from tads2015dataart to dataart.telco
[17:51] <gennadiy> *month
[17:51] <lazyPower> jrwren - any known issues with accounts that have changed their handle and the charm-store's backend bits?
[17:52] <jrwren> lazyPower: yes, if the account name changed since they first logged into www.jujucharms.com
[17:56] <lazyPower> gennadiy - does this sound like the situation? ^   did you log into the charm-store (jujucharms.com website) prior to renaming your launchpad account?
[17:56] <gennadiy> also i can't login to jujucharm too
[17:56] <gennadiy> yes
[17:56] <gennadiy> yes i logged before rename
[17:57] <lazyPower> jrwren - anything we can do to help gennadiy? And for future reference, if i encounter a user with similar issues, where should i direct them to file bugs/etc. so we can triage accordingly?
[17:57] <gennadiy> does it fix issue if i remove account and create new with correct name?
[17:58] <lazyPower> ideally we should be able to fix this... i'm not very familiar with that side of the codebase however, so i'm bugging jay for details :)
[18:01] <Prabakaran> Hi Matt/Kevin, I was reviewing the merge proposal which you have given for ibm-java. It looks good to me and I have a small doubt in the default package name and SHA value for JRE.
[18:01] <Prabakaran> As per this merge proposal http://bazaar.launchpad.net/~kwmonroe/charms/trusty/ibm-java/may-2016/view/head:/reactive/ibm-java default package name and SHA values are used only for SDK in the reactive/ibm-java file (Between Line number 14 to 25).
[18:01] <Prabakaran> How this default package name and SHA values for JRE if it is not provided by the user as it handles only for SDK.
[18:03] <jrwren> lazyPower, gennadiy i'm browsing our docs to see if we have notes on this issue. iirc, we did the same thing for aisrael
[18:03] <Prabakaran> Kindly advise on this and also I was not able deploy this merge proposal because of the if loop in the line number 65. After accepting this merge proposal I will be correcting this line of code.
[18:03] <mbruzek> Prabakaran: What is your concern with the ibm-java merge proposal?
[18:05] <mbruzek>  Prabakaran: If you can fix it I think that is great. Let me check the code. Why is there a loop
[18:07] <Prabakaran> we have a different package for JRE and SDK. My doubt is regarding the line of codes http://pastebin.ubuntu.com/16498220/ in the reactive file. How default package will work for ibm-jre
[18:08] <Prabakaran> thats no problem. i will fix it.
[18:09] <jrwren> gennadiy: can you file a bug with your account rename details at https://github.com/CanonicalLtd/jujucharms.com/issues ?
[18:19] <Prabakaran> As per my understanding this new proposal code will install SDK primarly and if the user wants install jre obivously he must have to feed package name and its sha thru juju set command. Is my understanding is correct?
[18:28] <mbruzek> Prabakaran: that sounds good to me.
[18:30] <bbaqar> hey guys .. we can push revisions in charms using bzr right? i can see the revisions on launchpad but not is charm show cs....
[18:30] <kwmonroe> yup Prabakaran - you got it.  the user gets to choose what installer to use (sdk or jre) by setting the installer filename
[18:31] <kwmonroe> Prabakaran: so there is no need ot set the default for a jre (in fact, there's no need to set any default installer or sha since we say the installer filename and sha is required to be set in the config
[18:32] <mbruzek> bbaqar: You can push to your own namespace, but the ones in ~charmers need to be reviewed
[18:33] <bbaqar> mbruzek: well i have a private team space where i can push charms ..
[18:33] <bbaqar> i still cant get new revisions in
[18:34] <lazyPower> bbaqar - launchpad ingest has been broken for about 2 weeks, we sent a notice to the mailing list
[18:34] <lazyPower> bbaqar see: https://jujucharms.com/docs/devel/authors-charm-store
[18:35] <mbruzek> bbaqar: Yes the automatic injest is broken, but you can push using the document that lazyPower linked ^
[18:35] <lazyPower> this will get you ramped up on the new charm push commands which will eliminate your need to wait 20/30 minutes for ingest. Make sure you fully read that document and grokk the new ACL structure for charms. by default, they are only visible to you as the uploader, and go into an unpublished channel
[18:36] <bbaqar> lazyPower: i believe i have done all this .. i ll go over the document once again
[18:37] <lazyPower> bbaqar so just to confirm, charm publish . ~plumgrid-ons/series/mycharm does not work for you?
[18:38] <mbruzek> notice the dot for current directory.
[18:38] <lazyPower> i paraphrased the namespace, feel free to sub with the proper group string
[18:39] <bbaqar> lazypower: i ran the exact same thing: charm push . cs:~plumgrid-team/trusty/neutron-api-plumgrid .. but the problem is it did not have the last two revisions that i pushed in the last week
[18:39] <lazyPower> bbaqar - did you publish those charms you pushed?
[18:39] <mbruzek> bbaqar: Did you publish those charms?
[18:40] <lazyPower> by default they land in an unpublished channel. You have to both push, and publish against the appropriate channel (Stable/devel accordingly)
[18:40] <Prabakaran> I am deploying and checking this ibm-java now.. i will accept this merge proposal. Thanks matt and kevin :)
[18:40] <bbaqar> lazypower: yup .. charm publish cs:~plumgrid-team/trusty/neutron-api-plumgrid-18 --channel stable    problem is i want 20th rev
[18:41] <mbruzek> bbaquar: charm publish cs:~plumgrid-team/trusty/neutron-api-plumgrid-20
[18:42] <bbaqar> mbruzek: no matching charm or bundle for cs:~plumgrid-team/trusty/neutron-api-plumgrid-20
[18:42] <lazyPower> bbaqar - i'm showing that -18 is head of what you have published. verified with `charm list -u plumgrid-team`  and additionally charm show cs:~plumgrid-team/trusty/neutron-api-plumgrid  does not show a -20 revision as available.
[18:42] <lazyPower> bbaqar so where is the "20'th revision" coming from?
[18:42] <lazyPower> is that the BZR id?
[18:43] <mbruzek> bbaqar: Yeah I only see 18 revisions in the listing. Perhaps the permissions are not allowing us to see 19 and 20?
[18:43] <bbaqar> mbrukzek, lazypower: http://bazaar.launchpad.net/~plumgrid-team/charms/trusty/neutron-api-plumgrid/trunk/changes/20?start_revid=20
[18:43] <lazyPower> mbruzek - i'm pretty sure evne if its in unpublished, it will show up in the revision-info key
[18:43] <lazyPower> bbaqar ah thats where the disconnect is coming from. those revision id's do not match whats in bzr, at all
[18:43] <mbruzek> ah
[18:43] <bbaqar> its there on launchpad
[18:43] <lazyPower> its completely disconnected from VCS
[18:45] <bbaqar> So am i doing something wrong here?
[18:46] <mbruzek> bbaqar: Yeah as we mentioned the automatic launchpad injest is broken, you have to manually push each revision, and then publish the ones you want to see.  The upside is no waiting 30 minutes for the automatic process, and the downside is that you have more manual work.
[18:46] <lazyPower> bbaqar if you did a charm push, it will tell you what revision the charm store incremented to.
[18:46] <mbruzek> So checkout the latest from bzr to your computer, then push it to the charm store.
[18:46] <lazyPower> ^
[18:48] <mbruzek> * Where more manual work is 2 additional "charm" commands.
[18:48] <bbaqar> I love the fact that we dont have to wait 30 mins and i am willing to run as many commands it takes .. just trying to figure out what they are exactly .. so this is what i am going to do now
[18:49] <mbruzek> bbaqar: the document that lazyPower linked you to outlines the steps
[18:50] <bbaqar> okay so this is what i am going to do 1) bzr branch lp:~plumgrid-team/charms/trusty/neutron-api-plumgrid/trunk 2) bzr ci -m "commit message" --unchanged 3) bzr push lp:~plumgrid-team/charms/trusty/neutron-api-plumgrid/trunk 4) charm push . cs:~plumgrid-team/trusty/neutron-api-plumgrid 5) charm publish cs:~plumgrid-team/trusty/neutron-api-plumgrid --channel stable
[18:50] <bbaqar> mbruzek i did run that .. let me try this
[18:51] <lazyPower> bbaqar nope
[18:51] <lazyPower> bbaqar you *have* to specify the revision output in the charm push command to that charm publish command
[18:51] <bbaqar> ohhhh h
[18:51] <bbaqar> i get it ..
[18:51] <lazyPower> which should increment to -19, as -18 is head
[18:51] <bbaqar> wait let me try that
[18:51] <gennadiy> @lazyPower - new publish charm tool - very cool. it shows errors in bundle! very useful
[18:52] <lazyPower> gennadiy really happy its a positive impact on your experience :)
[18:52] <lazyPower> jrwren you're getting praise and not targeted sir ^ <3
[18:52] <gennadiy> one more improvement: add flag --grant-everyone to publish command
[18:52] <mbruzek> gennadiy: and it lets *you* control what charms/bundles are in the store, no more automated injestion
[18:52] <lazyPower> gennadiy file a bug over here: https://github.com/juju/charm
[18:52] <mbruzek> gennadiy: you can do that with the charm set acl command
[18:53] <bbaqar> lazyPower: so this right charm push . cs:~plumgrid-team/trusty/neutron-api-plumgrid-19
[18:53] <bbaqar> lazypower but it says error: charm or bundle id "cs:~plumgrid-team/trusty/neutron-api-plumgrid-21" is not allowed a revision
[18:53] <lazyPower> bbaqar nope push doesn't need the revno
[18:53] <mbruzek> gennadiy:  sorry the `charm grant cs:~kirk/foo everyone` command.
[18:53] <lazyPower> only publish does, push i creating the entity, publish is registering it.
[18:54] <lazyPower> bbaqar - so what you're looking to do is this:
[18:54] <lazyPower> charm push . cs:~plumgrid-team/trusty/neutron-api-plumgrid
[18:54] <lazyPower> which it should come back with some output like:
[18:54] <lazyPower> url: cs:~plumgrid-team/trusty/enutron-api-plumgrid-19
[18:54] <lazyPower> channel: unpublished
[18:54] <lazyPower> Then you move into the publish phase if its ready for that:
[18:55] <lazyPower> charm publish cs:~plumgrid-team/trusty/neutron-api-plumgrid-19 --acl read everyone
[18:55] <lazyPower> it will default to publishing into the stable channel. if this is a devel release, please target the channel appropriately
[18:55] <bbaqar> It returns the same revno url: cs:~plumgrid-team/trusty/neutron-api-plumgrid-18
[18:56] <lazyPower> so, this is a super cool feature of push
[18:56] <lazyPower> you dont have a change from what you pushed into the -18 revision, teh charm command does store *small bits of metadata about the VCS tree*
[18:57] <lazyPower> all that info is shown when you charm show cs:~plumgrid-team/trusty/neutron-api-plumgrid  --- pipe that into less and evaluate the output to see the revision it read in from teh bzr metadata. Its not reading and is disconnected from, but if its present, we will use it to our advantage and keep you from revving a charm with no changes
[18:57] <lazyPower> bbaqar - one way you can validate is to `charm pull  cs:~plumgrid-team/trusty/neutron-api-plumgrid-18`  to a temporary location and then dir-diff that against what you have in your bzr archive. You should see its 1:1 copy
[18:58] <lazyPower> also i think its worth mentioning that some of these nuances will be much easier to see once we have the new review queue launched, which offers diffing between revisions and is layer aware. no ETA on when that will be available though, other than we are actively cycling towards resolution.
[18:59] <bbaqar> i understand .. yup you are right . .i pulled the charm .. and did a diff between the two directories .. its the same .. but one more thing ... i should be able to deploy the charm using juju deploy cs:~plumgrid-team/trusty/neutron-api-plumgrid-18
[19:00] <lazyPower> That is correct, so long as you granted read access to the published charm to the user you are logged in as thats trying ot deploy it, or gave read permissions to everyone
[19:00] <mbruzek> bbaqar: It will depend on the permissions granted, but yes you should be able to
[19:01] <bbaqar> i got it .. thanks guys ..
[19:01] <bbaqar> thanks for patiently explaining it
[19:02] <mbruzek> bbaqar: No problem please raise issues (link above) if you feel it can be improved.  If the documentation was not clear you can open an issue for that too
[19:02] <lazyPower> np! if there's any verbiage we could explain better in those docs, i'd love to get a bug report from anyone struggling with the new publish workflow
[19:02] <lazyPower> mbruzek we have finished assimilation, we are the same person
[19:02] <lazyPower> mbruzek who are you?
[19:03] <bbaqar> mbruzek: now that it is working .. this is awesome
[19:03]  * mbruzek whoami
[19:03] <lazyPower> > Pizza
[19:03] <mbruzek> https://github.com/juju/docs/issues/new
[19:03] <lazyPower> :O it all makes sense now
[19:04] <mbruzek> So my other self (lazypower) gave you a link to create issues with the charm command, and the documentation link is there if you feel it could have been more clear (which I have a feeling it could have been)
[19:05] <lazyPower> we are the juju singularity
[19:07] <bbaqar> lazyPower: I ll read it once again and raise an issue if i think we should update the doc
[19:15] <bbaqar> Once again .. guys this is cool .. i feel like i have control now ..
[19:23] <lazyPower> \o/ thats awesome
[19:23] <lazyPower> bbaqar glad it had a positive impact on your experience :)
[19:37] <Prabakaran> Hi Matt/Kevin, I have tested ibm-java and i am able to deploy successfully. I have merged those changes into the stream. And also i have updated the charm store with the updated code https://jujucharms.com/u/ibmcharmers/ibm-java/trusty/7 . I hope it will be approved soon. Thanks for your help and support :)
[19:37] <mbruzek> Prabakaran: OK we will give it another look
[19:38] <Prabakaran> Thanks matt
[19:38] <mbruzek> Prabakaran: did you also build the charm and update the bzr merge proposal
[19:41] <Prabakaran> i did charm build with the latest source code and pushed using charm push command
[19:46] <Prabakaran> mbruzek, All ok? is there anything needs to be done from my end?...
[19:46] <mbruzek> Prabakaran: can you give me link to the merge proposal ?
[19:47] <Prabakaran> from which branch to which branch?
[19:49] <Prabakaran> Source Code Repo : https://code.launchpad.net/~ibmcharmers/charms/trusty/ibm-java/source  This charm has been pushed into the charm store. Below is the link  Charm store link : https://jujucharms.com/u/ibmcharmers/ibm-java/trusty/7
[19:51] <mbruzek> Prabakaran: The Juju charm store and bzr are different things.
[19:52] <mbruzek> To be in the review queue you need to create a bug with a merge proposal
[19:52] <mbruzek> You had one, let me find it
[19:52] <Prabakaran> https://bugs.launchpad.net/charms/+bug/1477067
[19:52] <mup> Bug #1477067: New Charm: IBM Java SDK <Juju Charms Collection:Fix Committed> <https://launchpad.net/bugs/1477067>
[19:54] <mbruzek> Prabakaran: Yep that is what I needed.
[19:54] <mbruzek> Prabakaran: my mistake, this one was a bug since there is no charm to merge with, so I incorrectly used "merge proposal"
[19:54] <Prabakaran> thats no problem
[19:55] <Prabakaran> nothing else from my end right..
[19:55] <mbruzek> no
[19:56] <Prabakaran> its time for me to sleep...if anything is required please email me.. thanks again for your great support :)
[19:56] <kjackal> cory_fu: Do you have a minute?
[19:57] <cory_fu> Sure.  We're in bigdata-daily
[21:08] <cholcombe> interfaces.juju.solutions doesn't seem to understand lp links
[21:08] <cholcombe> the Apache WSGI base layer repo link is dead
[21:16] <lazyPower> cholcombe - err thats just a databag
[21:16] <lazyPower> do you mean the builder?
[21:16] <lazyPower> cholcombe - here's the list of what we test with the builder: https://github.com/juju/charm-tools/blob/master/tests/test_fetchers.py#L49
[21:16] <cholcombe> lazyPower, i'm not sure.
[21:16] <lazyPower> sorry, i mean the fetcher
[21:17] <cholcombe> lazyPower, i see
[21:17] <cholcombe> well than maybe interfaces.juju.solutions is having an issue resolving lp links
[21:25] <cholcombe> lazyPower, i was just trying to click the repo link to figure out what the apache wsgi layer requires
[21:25] <lazyPower> cholcombe OH
[21:25] <cholcombe> firefox just gives me an: I don't understand this link error
[21:25] <cholcombe> :D you get it now haha
[21:25] <lazyPower> you mean with the browser
[21:25] <lazyPower> yeahhhhhh
[21:25] <cholcombe> yep
[21:25] <lazyPower> this is a fail on our planning part
[21:25] <lazyPower> can you file a bug against the repo?
[21:25] <cholcombe> sure if i could find it lol
[21:26] <lazyPower> this may still live in bens namespace
[21:26] <cholcombe> i can't find it under jacek's lp
[21:26] <lazyPower> https://github.com/bcsaller/juju-interface <- is what i meant
[21:26] <cholcombe> oh nvm i found it
[21:26] <cholcombe> https://code.launchpad.net/~jacekn/charms/+source/apache-wsgi/+git/apache-wsgi is the link
[21:27] <lazyPower> this is the codebase for the interfaces webservice
[21:27] <lazyPower> we'll need to add support to resolve those links
[21:27] <cholcombe> lazyPower, everyone else seems to just be putting in the link to the summary page
[21:28]  * lazyPower shrugs
[21:28] <lazyPower> i use github yo
[21:28] <cholcombe> lazyPower, i updated it
[21:28] <lazyPower> but that works equally as well
[21:29] <cholcombe> it would take me 10x as long to write a bug report haha
[21:32] <cholcombe> i still think it's too difficult to find out what reactive layers and interfaces require of the person using them.  You have to dig
[21:47] <mpjetta> random question: I’m using juju 2.0-beta6 and MAAS 2.0 beta3. I’m still having to use “export JUJU_DEV_FEATURE_FLAGS=maas2” , is that correct or am I doing something wrong ?
[21:55] <lazyPower> mpjetta - i dont think that came out from behind the feature flag until beta7
[21:55] <lazyPower> I'm pretty sure thats covered in the release notes in /topic however
[22:07] <mpjetta> ok thanks


[06:07]  * Unit193 awaits ahasenack's return.
[11:37] <ogayot> Hi, could an AA look at the following upload? https://launchpad.net/ubuntu/+source/opencolorio/2.1.2+dfsg1-3ubuntu1 ; there is a new binary package libopencolorio2.1. Thanks!
[12:24] <ahasenack> is something wrong with the main archive site? I got this for armhf and arm64 now:
[12:24] <ahasenack> E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/kinetic/main/binary-arm64/Packages  404  Not Found [IP: <IP_ADDRESS> 80]
[12:34] <ahasenack> ops, sorry for the noise, it's a very different url
[12:34] <ahasenack> I just moved my lxd profile from my amd64 host to a pi4 box, and didn't realize the archive urls need changing
[13:16] <ricotz> RikMills, hi :), is KDE going to use QT6 as default in kinetic?
[13:21] <ricotz> hmm, I guess that answers my question - https://community.kde.org/Schedules/Plasma_6
[13:38] <RikMills> ricotz: indeed, no
[16:04] <ricotz> RikMills, are you pushing more qt6-abi rebuilds? :) - like pyqt6, calibre
[16:06] <RikMills> ricotz: calibre doesn't need it, as there is calibre in -proposed that just needs retrying when qt6-webengine has built
[16:06] <RikMills> others are pointless until webengine has built. the I will do them
[16:07] <RikMills> *then I
[16:08] <ricotz> RikMills, thanks!
[16:08] <RikMills> np
[20:49] <Unit193> ahasenack: https://salsa.debian.org/debian/wireguard/-/merge_requests/6#note_330684 pinged dkg, but like I said seems fine.  I can no longer merge/upload wireguard to Ubuntu so I guess you'll have to merge/sync though.
[21:12] <ahasenack> Unit193: that's because of the MIR promotion of wireguard?
[21:12] <sarnold> yeah :(
[21:12] <ahasenack> hm
[21:13] <ahasenack> Unit193: but you do upload it in debian, right?
[21:13] <Unit193> I took a look at the package last night or so, I plan to drop all patches and make other adjustments.
[21:13] <Unit193> ahasenack: Yes, I seem to be the most active on it now.
[21:14] <Unit193> I defer to dkg because he's actually the maintainer, but I'm in 'uploaders'.
[21:14] <ahasenack> I'm subscribed to it in the debian tracker, I will get notified of any uploads or bugs even
[21:14] <ahasenack> so I don't think ubuntu will fall behind
[21:15] <Unit193> Great.  That's actually how I got sucked into this, Ubuntu fell far behind and I did a few merges.
[21:16] <ahasenack> ah, famous TIL
[21:17] <Unit193> I think after the DEP8 upload, we can just sync.  The flip of the recommends shouldn't really matter too much anymore.
[21:19] <ahasenack> I think so too
[21:22] <ahasenack> but I'll recheck when the time gomes
[21:22] <ahasenack> comes
[21:22] <ahasenack> there was something about ubuntu cloud images that kept the recommends flip in place back then
[21:23] <ahasenack> I have links to irc conversations with apw about that
[21:24] <ahasenack> not just cloud images, but if you happen to be on a kernel that doesn't have the module, then dkms would be pulled in and just do the right thing
[21:24] <ahasenack> something like that
[21:24] <Unit193> Basically it could pull in a hwe kernel or one of the other kernels when pulling in the dkms module would have been the sane option.
[21:24] <ahasenack> but since dpkg doesn't check the *running* kernel, I don't remember how this could work in all cases
[21:24] <Unit193> Since it should now be everywhere...
[21:26] <Unit193> I think it's also time for wireguard-linux-compat to be removed from Debian (and Ubuntu too I imagine.)
[21:28] <ahasenack> if debian gets rid of it first,  it's much easier for ubuntu to follow
[21:28] <ahasenack> but I remember upstream commenting in a bug about that, objecting. Or am i mixing up things, maybe upstream objected to the dkms removal
[21:28] <sarnold> I can't find that package via apt-cache show wireguard-linux-compat  on any of my machines that are turned on
[21:28] <vorlon> for awareness, I've just uploaded an openssh package to kinetic that switches sshd to use systemd socket activation.  Please yell at me if you see any regressions https://lists.ubuntu.com/archives/kinetic-changes/2022-August/005198.html
[21:33] <Unit193> sarnold: wireguard-linux-compat is the source package, wireguard-dkms is the binary.
[21:33] <sarnold> ahhhhhhh
[21:33] <sarnold> I shoulda checked the machine that's turned off :)
[23:07] <arraybolt3> Is it worth keeping around my original 22.04 ISOs for potential future use in testing, or is it an OK idea to chuck them and only keep the 22.04.1 ISOs?
[23:11] <vorlon> arraybolt3: do whatever you want with them? they'll still be available for download from old-releases.u.c
[23:12] <arraybolt3> The flavors, not usually. Multiple flavor ISOs are just gone from there.
[23:12] <vorlon> oh for flavors, right
[23:12] <arraybolt3> I usually pull "missing" ISOs from Archive.org but there's no guarantee that they'll be there.
[23:12] <arraybolt3> (Also, out of curiosity, *why* are the flavor ISOs deleted even from old-releases?)
[23:12] <vorlon> well I would say there's diminishing value in testing the .0 ISOs that aren't even available for download
[23:13] <Unit193> arraybolt3: Keep the torrent files, hope for the best?
[23:13] <vorlon> arraybolt3: old-releases has always been an archive of releases; we've never retained cdimage.u.c content there
[23:13] <arraybolt3> Yeah, I just thought for regression testing and that sort of thing. But I don't think it will be needed - if there's a regression, it can be verified with a downgraded package.
[23:14] <arraybolt3> vorlon: Hmm, there certainly are a lot of ancient Ubuntu flavor ISOs on there. Just curious since they can be rather valuable in some instances.
[23:14] <arraybolt3> Unit193: If only I could torrent safely with my ISP...
[23:14] <Unit193> Weird, as long as they're legal torrents the ISP shouldn't care. :/
[23:15] <vorlon> moreover, it's decreasingly important whether a bug is a regression vs the release pocket
[23:15] <vorlon> we don't undo a point release because someone found a regression 3 months later
[23:15] <arraybolt3> Unit193: They are legal, but I'm on cellular internet (T-Mobile hotspot through Calyx Institute) and T-Mobile considers BitTorrent to be network abuse. :( I could try it, but they might throttle me down beyond all reason.
[23:16] <vorlon> and if you're testing for regressions in individual packages in -updates, as opposed to of the installer, there are more efficient ways of doing that
[23:16] <arraybolt3> vorlon: Good point. I guess I'll save on disk space then and clear out the old ones.
[23:16] <Unit193> vorlon: Can be helpful to find at what stage the regression hit so as to help figure out what change caused it.
[23:16] <Unit193> Note: "Can be"
[23:17] <arraybolt3> Unit193: My use case for very old Ubuntu flavor releases is mostly out of preference - sometimes you've gotta run some ancient app in a VM and would rather do it with KDE4 than with Unity. But I'm getting off-topic now.
[23:22] <vorlon> arraybolt3: "ancient Ubuntu flavor ISOs" - well kubuntu and edubuntu once upon a time were distributed from releases.u.c; the others are on there by accident, but unfortunately they've been deleted from the source but this doesn't reflect on the web frontend
[23:23] <arraybolt3> Ah, that makes sense to me.


[00:10] <Sammy> do you play any instruments eickmeyer?
[00:11] <Eickmeyer[m]> Sammy: I do, just not guitar. I'm an audio engineer. Live audio mixing, mostly.
[00:11] <Sammy> nice!!!
[00:13] <Sammy> i really like that I can watch youtube so easilly while still getting audio from it, impossible in windows!
[00:13] <Sammy> its so easy to load and find what i want to play
[00:14] <Eickmeyer[m]> Sammy: Social conversations are over in #ubuntustudio-offopic if you ever want to join us. :)
[17:45] <AppAraat[m]> Not sure what I changed, but I guess thanks goes out to kernel/drivers/UbuntuStudio: https://mobile.twitter.com/improbabilitist/status/1221932396188139522
[17:46] <Eickmeyer[m]> AppAraat[m]: Probably the Ubuntu Kernel team as we have zero involvement there. Ubuntu Studio is simply a different default installation of Ubuntu, nothing more.
[17:48] <AppAraat[m]> ah ok, so Ubuntu Studio is basically custom ALSA+JACK+PA config + (optionally) packaged apps then ?
[17:51] <AppAraat[m]> In any case I'm super glad. Ubuntu Studio solved my xrun torment and has been super stable for me so far. I haven't tested it in combination with external MIDI hardware but I'm guessing that shouldn't be much of a problem.
[17:51] <Eickmeyer[m]> AppAraat[m]: Basically. You can see all of the config we do at https://git.launchpad.net/ubuntustudio-default-settings/tree/
[17:52] <Eickmeyer[m]> Ubuntu Studio Controls does the bulk of the audio configuration as well.
[17:54] <AppAraat[m]> oh sweet, thanks for that link! I'll consult it when diving deeper into learning more about my audio config.


[10:47] <cjwatson> could somebody process libchamplain and syslinux-themes-ubuntu through binary NEW, please?
[10:47] <cjwatson> (can't do them myself, as I'm the uploader)
[11:27] <pitti> can do
[11:31] <pitti> cjwatson: is syslinux actually meant to still build the -oneiric binary?
[11:32] <pitti> (champlain accepted)
[11:32] <cjwatson> yes, I left it that way so that one can build oneiric live CDs on precise
[11:32] <cjwatson> which seems like a reasonable thing to want to do
[11:33] <cjwatson> likewise syslinux-themes-debian includes themes for old releases
[11:35] <pitti> cjwatson: ok, accepted; -oneiric might need seeding then (or go to universe, but then you couldn't build live CDs)
[11:52] <cjwatson> good point, I'll sort that out
[11:56] <cjwatson> done
[11:56] <cjwatson> (seeded, that is)
[17:36] <lamont> i386 ppas on manual for a few min
[18:40] <skaet> just noticed that 11/11 is a holiday here in the US,  so will be starting up the release weekly meetings on the 18th.   (unless someone wants to volunteer to host it ;) )
[19:14] <infinity> skaet: Holiday for us too.
[19:19] <skaet> infinity,  :)
[19:22]  * infinity ponders throwing an 11/11/11 party.
[19:29] <skaet> at 11:11:11 ?
[19:29] <nigelb> obviously.
[19:30] <nigelb> with 111 beers available.
[19:30] <skaet> GMT or local?  ;)
[19:35] <slangasek> apparently the pdx kernel group is having a 10/11/11 party
[19:42] <lamont> http://www.meetup.com/106miles/events/38000342/ <-- infinity


[04:42] <saptech> hello all
[04:43] <wxl> \o
[04:43] <saptech> after updating to 18.10, when I boot I'm taking to this virtual keyboard screen instead of the login screen
[04:43] <wxl> is lightdm running?
[04:43] <saptech> how can I remove the virtual keyboard screen?
[04:44] <saptech> yes lightdm
[04:44] <wxl> well there's your problem
[04:44] <wxl> 18.10 uses sddm
[04:44] <wxl> you have holdovers from 18.04 which creates all sorts of ridiculous issues
[04:44] <saptech> hmmm
[04:45] <saptech> will it be okay to use lxdm? I've had problems with sddm before
[04:45] <wxl> we haven't tested it so you're welcome to try it out
[04:45] <wxl> have you had problems with THIS version of sddm? if not, i'd try it before deciding it's not going to work
[04:46] <saptech> issues with sddm and another distro running plasma5
[04:47] <wxl> that's pretty much unrelated, it sounds like
[04:48] <saptech> I'll see
[04:48] <wxl> you should see this
[04:48] <wxl> ESPECIALLY the very end
[04:48] <wxl> https://manual.lubuntu.me/D/upgrading.html
[04:48] <wxl> it tells you what you should get rid of to not have a total frankenstein system
[04:49] <saptech> that's the info I used to upgrade
[04:49] <wxl> but you didn't do the very end which suggests to remove packages, lightdm included
[04:50] <saptech> I removed most all of it. I left lightdm because I didn't want to use sddm
[04:51] <wxl> well if you don't follow the instructions you're on your own XD
[04:51] <saptech> I do not remember seeing the virtual keyboard with 18.04
[04:51] <wxl> well you could go and tweak the lightdm settings so that there's no virtual keyboard
[04:51] <saptech> but I only used lubuntu for a few months before the upgrade to 18.10
[04:52] <wxl> you probably have a "keyboard" line in there somewhere
[04:53] <saptech> ok
[04:53] <saptech> thanks for the info
[04:54] <wxl> np
[04:55] <saptech> this was my first time trying lubuntu, but became a little disappointed when it was upgrading with lxqt instead of lxde
[04:55] <saptech> I understand why you doing it
[04:56] <saptech> bad experiences with lxqt
[04:56] <saptech> but I'm always willing to give a distro a try
[04:57] <wxl> yeah well lxde has slowed to a crawl. one of its most major developers left it for lxqt (pcman himself). they STILL aren't ready for gtk3, not to mention upcoming gtk4. it's a necessity
[04:57] <wxl> lxqt is under heavy development. if there's something lacking in it, i'm sure you'll find a quick resolution
[04:59] <saptech> interesting
[04:59] <wxl> it's hard to get *translations* into lxde
[04:59] <saptech> I'm going to stick with it and see how it work for me
[05:00] <wxl> if you have problems, file a bug report! we'll work to get it fixed
[05:00] <saptech> ok, good to know
[05:01] <saptech> I'll give sddm a try, since this experience with lxqt is going great with me
[05:02] <wxl> good to hear
[05:06] <saptech> wxl, it we're not using xfburn, what are they using in place of it?
[05:06] <wxl> everytime someone asks me this i have to go look it up because i never burn cds XD
[05:07] <saptech> lol....I do not see a substitute for it
[05:07] <saptech> xfburn is a great burner
[05:07] <saptech> I think people are burning dvd moreso now days
[05:08] <wxl> yeah i don't even bother with those
[05:09] <wxl> k3b
[05:10] <saptech> hmmm
[05:13] <saptech> will k3b pull in a bunch of kde/plasma depends?
[05:13] <wxl> it's included in lxqt.. so assumedly you already have it
[05:14] <wxl> but kde has pretty much modularized all their stuff so there's nothing (except for plasma and pieces related to it) that pull in a whole ton of dependencies
[05:14] <saptech> ok
[05:19] <JohnDoe_71Rus> xfburn +
[05:20] <saptech> :)
[05:20] <JohnDoe_71Rus> and k3b + too
[05:20] <saptech> yes
[05:20] <JohnDoe_71Rus> different case
[05:21] <JohnDoe_71Rus>  xfburn quick burn image
[05:22] <saptech> how well does lxqt apps work with standalone openbox?
[05:22] <wxl> should work fine, but we don't actually include it in our tests
[05:24] <JohnDoe_71Rus> not lxde(qt) but very nice https://commit-digest.org/issues/2006-12-10/files/sensorload14.png
[05:26] <JohnDoe_71Rus> better lxtask
[05:28] <saptech> I normally use the default DE for the family but usually run openbox for myself, and I use the Switch User feature alot. Some distros gave me problems switching users running sddm & lightdm
[05:29] <saptech> I have Mageia as my main OS, Voidlinux, Devuan & now Lubuntu
[05:29] <saptech> that is one reason I stuck with Lxdm for display manager
[05:34] <wxl> i'm not sure lxdm is even very well maintained
[05:35] <saptech> I'm going to try sddm...I need to try it now