[00:25] <alteregolio> high
[02:13] <Toma-> what would be nice, is apt-get or aptitude making a suggestion of what packages to remove if youre running out of disk space. kind of like running deborphan when its needed or something
[02:15] <h3sp4wn> You would need to work out how often things are run to make a sane decision as of what to remove
[03:23] <ghuang> hi
[03:23] <ghuang> during boot of the hardy alpha 1 CD on my laptop, it gets stuck diplaying this message over and over:
[03:24] <ghuang> bcm43xx: Error: microcode bcm43xx_microcode5.fw not available or load failed
[03:24] <ghuang> not like rapidly, but once every 30 secodns or so
[03:24] <ghuang> I have my ethernet plugged in, so it's not like it *has* to figure out the wireless to proceed
[03:24] <h3sp4wn> Get the microcode ?
[03:24] <ghuang> any ideas?
[03:24] <ghuang> how can I get the microcode in the middle of kernel init on a bootable CD?
[03:25] <ghuang> I am familiar with this scenario when linux is already isntalled -- this is different
[03:25] <h3sp4wn> Are you running 2.6.24-1 ?
[03:26] <ghuang> whatever is on the hardy alpha 1 bootable CD
[03:27] <ghuang> 2.6.22-14
[03:27] <ghuang> it's ata  shell prompt (finally), but X didn't start at all
[03:27] <h3sp4wn> Thats the gutsy kernel still
[03:27] <ghuang> it must be an issue with the hardy CD packaging, then ;)
[03:28] <h3sp4wn> As far as I can see there is no restricted modules for the hardy kernel yet
[03:28] <ghuang> ah
[03:28] <ghuang> that's too bad, I was hoping to help out with testing
[03:28] <ghuang> I guess I'll install using gutsy and then try upgrading from there
[03:28] <ghuang> thanks for the info! :)
[03:28] <h3sp4wn> ghuang: You could try a daily build or alpha 2 (if alpha 2 exists)
[03:29] <h3sp4wn> or the netboot/mini.iso (that has never failed for me yet)
[05:31] <tumbleweed__> E: /var/cache/apt/archives/slocate_3.1-1.1ubuntu1_amd64.deb: subprocess pre-installation script returned error exit status 1
[05:34] <Hobbsee> is there a bug about it?
[05:35]  * tumbleweed__ checks
[05:36] <tumbleweed__> nope
[05:42] <compwiz18> tumbleweed__: https://bugs.launchpad.net/bugs/157661
[05:42] <ubotu> Launchpad bug 157661 in slocate "package slocate 3.1-1ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1" [High,Confirmed]
[05:42] <tumbleweed__> ah
[05:42] <tumbleweed__> I was looking in hardy
[05:43] <compwiz18> it isn't in Hardy?
[05:43] <tumbleweed__> nope
[05:43] <tumbleweed__> didn't have this problem in gutsy, either
[05:43] <compwiz18> me neither
[05:43] <compwiz18> its a hardy update, I think
[05:44]  * tumbleweed__ shrugs
[05:45] <Hobbsee> looks like a gutsy--> hardy dist-upgrade problem
[05:45] <compwiz18> yeah
[05:46] <DarkMageZ> not a gutsy --> hardy problem. i have it on my hardy alpha 1 clean install.
[05:46] <DarkMageZ> after updates of course :p
[05:47] <compwiz18> same
[05:47] <Hobbsee> ah
[05:47] <Hobbsee> yes, but we only carea bout gutsy --> hardy, or current clean-installs from herd 2 (when it's out)
[05:54] <malnilion> Why are they called herds?
[05:55] <tumbleweed__> nope
[05:55] <tumbleweed__> I did a clean install of hardy
[05:55] <Hobbsee> malnilion: they're not
[05:55] <Hobbsee> tumbleweed__: off what?
[05:55] <tumbleweed__> an alternate install disc
[05:55] <Hobbsee> alpha 1?
[05:55] <tumbleweed__> yup
[05:56] <Hobbsee> well, that was not ever promised to be trouble free
[05:56] <tumbleweed__> right
[05:56] <tumbleweed__> wasn't what I was looking for :P
[05:57] <Hobbsee> the bug has the solution, if you were looking for that
[05:57] <tumbleweed__> yup, saw it
[05:57]  * Hobbsee was more interested about where it's going to hit, and if it should be required to be fixed for tribe 2.
[05:58] <tumbleweed__> doesn't seem as if it will need to be fixed by tribe 2, as it's an upgrade issue, and a newer version will be in tribe 2
[05:58] <tumbleweed__> unless I'm mistaken
[05:59] <compwiz18> that sounds right
[05:59] <compwiz18> its a upgrade issue, not installation
[07:09] <DanaG> Yay, it seems like the 2.6.24-2-generic kernel is at least slightly less laggy than the .24-1 kernel.
[07:09] <DanaG> But it's stilll rather annoying.
[07:16] <DanaG> Argh, that trackerd icon is distracting.
[07:18] <gary4gar> becuase bug 43154 my system crashes :(, now Via came up with new driver. can anyone help me install & configure the new driver?
[07:18] <ubotu> Launchpad bug 43154 in xserver-xorg-video-via "freezes with 3D applications on VIA Unichrome K8M800, KM400" [High,Confirmed] https://launchpad.net/bugs/43154
[07:22] <DanaG> Wow, this new scheduler sucks.
[07:22] <DanaG> I
[07:23] <DanaG> I'm getting audio cracking when trying to use the 'duplicate' feature in PulseAudio.
[07:24] <DanaG> It only stops crackling when I stop folding@home.
[08:22] <gary4gar> j #uclibc
[08:50] <gary4gar> what is VMI-ONLY path or V4L path?
[08:51] <h3sp4wn> gary4gar: VMI is the vmware paravirtualised interface
[08:51] <gary4gar> and V4L?
[08:52] <h3sp4wn> video for linux
[08:52] <gary4gar> okay thanks
[08:53] <gary4gar> i am trying to compile driver from source, but facing lot of issues
[08:53] <h3sp4wn> which driver ?
[08:53] <gary4gar> VIA Linux K8M64XF41061 Driver kernel Source Code
[08:53] <gary4gar>  Product/s:  	K8M800/K8N800 UniChrome Pro integrated graphics
[08:54] <gary4gar> bug #43154
[08:54] <ubotu> Launchpad bug 43154 in xserver-xorg-video-via "freezes with 3D applications on VIA Unichrome K8M800, KM400" [High,Confirmed] https://launchpad.net/bugs/43154
[08:54] <h3sp4wn> are you sure its for 2.6.24 ?
[08:54] <gary4gar> h3sp4wn, i have both, then gutsy kernel & hardy 's kernel
[08:55] <gary4gar> on whichever this thing works, i will make a switch :)
[08:56] <h3sp4wn> gary4gar: Where can I get the thing you are trying to compile from ?
[08:57] <gary4gar> http://www.viaarena.com/Driver/k8m64xf41061-kernel-src_20050926.tgz
[08:57] <gary4gar> ^^direct link
[08:57] <gary4gar> http://www.viaarena.com/default.aspx?PageID=420&OSID=25&CatID=2580&SubCatID=109
[08:57] <gary4gar> ^^information of the driver packsge
[08:58] <h3sp4wn> gary4gar: Are you sure thats the new just released driver ?
[08:58] <h3sp4wn> (that is mentioned in the bug report - seems wierd that it has 2005 in the filename
[08:59] <gary4gar> h3sp4wn, yeah...the date is :13 December 2007
[08:59] <gary4gar> few days back
[09:00] <gary4gar> oops my mistake, i gave the wrong link
[09:00] <gary4gar> http://www.viaarena.com/Driver/cle266cn400cn-cx700cn800xorg40072-kernel-src_20071213d.rar
[09:00] <gary4gar> ^^^correct one
[09:00] <gary4gar> there also a binary available
[09:00] <gary4gar> http://www.viaarena.com/default.aspx?PageID=420&OSID=45&CatID=3220&SubCatID=150
[09:01] <h3sp4wn> That build system is a complete mess
[09:01] <gary4gar> yeah i know
[09:01] <gary4gar> topic running on this in forums : http://ubuntuforums.org/showthread.php?t=636368
[09:08] <mrtimdog> Hi, I've just installed an alternative browser with no problems (Swiftfox). But when I create a gnome desktop URL link this link always opens in Firefox. I've changed the default applications, and also the alternatives for x-www-browser but no luck!
[09:09] <mrtimdog> What do I need to change to change the default browser for desktop URL links?
[09:10] <Tomcat_> mrtimdog: Have you checked that FF is closed? Sometimes, FF derivates just open another window of an existing FF. :)
[09:12] <mrtimdog> Hi Tomcat_: Yes all ff and sf processes were gone.
[09:13] <mrtimdog> When a Swiftfox browser is open, the desktop link will open within the running Swiftfox. It's just for when a new browser is needed to open the link.
[09:16] <Tomcat_> mrtimdog: Mh. What does "gnome-open <URL>" do?
[09:19] <mrtimdog> Tomcat_: gedit!
[09:19] <Tomcat_> Eh. .)
[09:20] <mrtimdog> Tomcat_: It's a .desktop file, with a Type=Link and a URL=http://... entries.
[09:20] <mrtimdog> Is there a way of listing any registered URL type handlers?
[09:21] <mikkael> the kdesudo part in systemsettings/kcontrol is broken in hardy (which is already reported in launchpad). i need to access the kdm settings, what would be the kcmshell command to launch this with kdesu ?
[09:27] <h3sp4wn> !info xserver-xorg-video-via
[09:27] <ubotu> xserver-xorg-video-via: X.Org X server -- VIA display driver. In component main, is optional. Version 1:0.2.2-5 (hardy), package size 146 kB, installed size 456 kB
[09:33] <h3sp4wn> gary4gar: Yeah you don't need that very old version of DRI
[09:39] <h3sp4wn> gary4gar: There is another one in the updated rar file
[09:44] <gary4gar> h3sp4wn, where?, link please?
[09:47] <h3sp4wn> gary4gar: Just underneath the other one
[09:47] <h3sp4wn> http://drivers.viaarena.com/cle266cn400cn-cx700cn800xorg40072-kernel-src_20071213d.rar
[09:48] <clusty> hey
[09:48] <clusty> i am having some issues with the java and new X
[09:48] <gary4gar> h3sp4wn, whats your video card?
[09:48] <clusty> the famous lock issue with some library
[09:48] <clusty> any ideas how to fix it?
[09:49] <gary4gar> h3sp4wn, but thats a old 14 February 2007, A Valentine gift from Via
[09:49] <gary4gar> :p
[09:49] <gary4gar> lol
[09:51] <h3sp4wn> gary4gar: I use nvidia don't like it though
[09:52] <gary4gar> h3sp4wn, mobo?
[09:53] <h3sp4wn> gary4gar: No seperate graphics card
[09:54] <gary4gar> h3sp4wn, oh
[09:55] <gary4gar> h3sp4wn, can you help me in enable 3d support ?
[09:55] <mikkael> ive got a nasty problem in kubuntu hardy: i wanted kdm to autologin my user. kdesudo in systemsettings/kcontrol is broken. i used "kdesu kcmshell kdm" and changed it to autologin, but kdm respect my changes. then i tried the same but with "sudo" (which was propably bad), now kdm doesnt start at boot, i have to switch to another tty, startx, and launch kdesktop, kicker, kwin manually to have a desktop back. any idea how i can fix kdm again
[09:56] <mikkael> *kdm didnt respect my changes with kdesu..
[09:59] <h3sp4wn> gary4gar: I am trying to build the damn thing right now
[09:59] <gary4gar> h3sp4wn, but you don't have the required hardware, then how can you manage?
[10:00] <mikkael> brb
[10:01] <h3sp4wn> gary4gar: I know what the current driver looks like
[10:07] <gary4gar> h3sp4wn, sadly unichrome part of Mesa is unmaintained. :(
[10:11] <gary4gar> h3sp4wn,forums at via, might be help too, http://forums.viaarena.com/categories.aspx?catid=28&entercat=y if you succed then please do write a Howto or a wiki page on it for sure :)
[10:11] <gary4gar> if you don't have much time then guide me,  i can write a write on your behalf, with all due credits :
[10:23] <h3sp4wn> gary4gar: I cannot guarantee I can do it - its seems its a forked version of - http://www.openchrome.org
[10:24] <gary4gar> i was already using open-chrome
[10:25] <gary4gar> are there any performance boost & does the hanging problem still there?
[10:27] <gary4gar> h3sp4wn, you are trying is a big deal for me, if you succeed then great, else its okay :)
[10:28] <h3sp4wn> gary4gar: openchrome has not been updated since october
[10:30] <gary4gar> yeah..i noticed that, i too gave up, & now thinking to get a nvidia 5200
[10:30] <gary4gar> if the issue does not solve soon
[13:46] <rgreening> Anyone have a problem with adept meta package and recent updates causing conflict and adept packages to be removed? It seems that the adept metapackage needs to be updated else it causes all other deps to be removed. Was this intended or a small error?
[13:53] <Hobbsee> rgreening: yes
[13:54] <rgreening> Hobbsee: any idea on how to correctly fix or recover? I could temp use the apt-get or aptitude from command line, but I'd like to get adept back or whatever the Hardy Heron GUI manager will be for Kubuntu
[13:55] <Hobbsee> rgreening: do a dist-upgrade
[13:56] <rgreening> 1 sec then...
[13:56] <Hobbsee> oh, wait
[13:56] <rgreening> no. that wont help.
[13:57] <rgreening> Im already at latest dist and updates, which removed the adept
[13:57] <Pici> I typically use aptitude and use its 'the follwing actions will resolve this thing' options to pick something that works for me.
[13:57] <rgreening> It applied a bunch of updates to apt, which caused adept to be removed.
[13:57] <Hobbsee> yup
[13:57] <Hobbsee> Pici: adept needs to be rebuilt, etc
[13:58] <Hobbsee> iirc, it didn't actuallyb uild with the new stuff
[13:58] <Pici> Hobbsee: Right, I realize that.
[13:58] <h3sp4wn> Pici: Thats what I usually do - but recently first sign of trouble I just do an aptitude safe-upgrade
[14:04] <rgreening> so, will adept meta package get rebuilt?
[14:04] <rgreening> I really dislike using aptitude long-term
[14:06] <Pici> I can't speak for the devs for when that will happen, but usaually given a period of time these things 'fix themselves' (in other words, the devs work their magic)
[14:06] <Hobbsee> rgreening: yes, eventually
[14:07] <rgreening> I guess I'll try and revent my blunder. I was holding back the update which was going to remove adept, but accidentally did the update this am. DOH.
[14:08] <rgreening> I'll prob use synaptic for now.
[15:11] <WorkingOnWise> good morning. I just did a fresh install from the alpha1 cd. I expected to be greeted with the restricted driver manager so I couln get my Nvidia Geforce GO 6100 video card. Where do you go to setup the 3d vid drivers the "ubuntu" way in Hardy?
[15:13] <Pici> The restricted drivers manager should be there, if its not, you might need to install it. (There was an issue in the Gutsy alphas that you had to do that too)
[15:13] <Pici> My install was an upgrade, so I didnt encounter this.
[15:13] <bazhang> I had to install mine
[15:16] <livingdaylight> Anyone here know or have any thought about the future adoption of Conary as a pm replacement to APT?
[15:16] <WorkingOnWise> ty everyone. will go now and instal it.
[15:17] <Pici> I don't forsee that happening any time in the near future, especially for an LTS release.
[15:18] <livingdaylight> shame it would be nice to see more innovation and ubuntu being brought into the future
[15:18] <crdlb> ubuntu is based on debian, so unless debian moves to conary ... :)
[15:19] <Pici> Huge changes tend not to be made before an LTS release, we're aiming for stability.
[15:20] <livingdaylight> crdlb, conary is just a package manager
[15:20] <crdlb> right, and using it would mean dropping dpkg and apt
[15:21] <livingdaylight> Ubuntu was founded on doing things better ... if conary is better than apt why not adopt is... they did consider smart a while back didn't they?
[15:23] <crdlb> because rewrites are bad
[15:23] <crdlb> anyway, that's not a support question, so it's offtopic for this channel too :)
[15:23] <bazhang> haha
[15:29] <WorkingOnWise> i hit the enable checkbox in rdm for the NVIDIA drivers and get the error "Reconfiguring X.org video drivers is not possible: /etc/X11/xorg.conf is invalid or does not exist. I used gedit to look at the xorg.conf, which indeed did not exist in that location, so I saved a blank one there, hoping that rdm would accept it and config my video. What do I do?
[15:35] <cypherdelic> Somehow after an update my /var/lib/dpkg/available was currupted, so I rm'ed it and run apt-get update and upgrade, but dpkg still claims for that missing file, please help.
[15:37] <cypherdelic> Any ideas?
[15:39] <cypherdelic> can somebody send me his file?
[15:39] <albert23> cypherdelic: don't you have /var/lib/dpkg/available-old?
[15:40] <cypherdelic> hold on ill have a look
[15:43] <WorkingOnWise> I know there is intended to be a clean simple  GUI way to do this. It worked perfectly in Gutsy. Is it broke in Hardy? I didnt find anything in launchpad. It has happened 2 times on the same laptop. Is this broke? Do I report Theres so much in launchpad now I hate to add redundant bugs....
[15:43] <WorkingOnWise> oh....AMD64 also...sorry
[15:44] <kalpik> WorkingOnWise, sudo dpkg-reconfigure -phigh xserver-xorg
[15:46] <WorkingOnWise> kalpik: what went wrong that that is needed. I am looking to the final rlease, when mom and pop will be installing this, and they get the same problem. They won't even know what to ask, or where, let alone understand the answer. They will just think Ubuntu is junk and stay in Windows
[15:47] <kalpik> WorkingOnWise, hardy is not meant for your mom and dad right now :)
[15:47] <kalpik> WorkingOnWise, things WILL break time and again during alphas.. read the topic! :)
[15:48] <WorkingOnWise> kalpik: hehe...yeah, but if this is a problem is a bug, I want to help fix it, so Hardy is ready for mom and pop...
[15:52] <WorkingOnWise> I guess I will file a bug report and old off on repairing it in case there are any questions on the current state. I can go a few days without 3D and compiz-fusion for the good of dear old ma and pa....
[15:52] <WorkingOnWise> old=hold
[15:52] <bardyr> Morgen
[15:53] <WorkingOnWise> is rdm going to be installed and in the panel by default for the final release, like it was in Gutsy?
[15:53] <Pici> I've gone without compositing since I upgraded to Hardy.
[15:53] <bardyr> why?
[15:54] <WorkingOnWise> Pici: my heart is heavy for u....
[15:54] <WorkingOnWise> hehe
[15:54] <Pici> bardyr: me?
[15:54] <bardyr> yea
[15:54] <kalpik> WorkingOnWise, definitely report bugs! That's what public alpha testing is all about! but you really cant complain if it breaks :)
[15:55] <Pici> bardyr: Well, I was a bit wrong. Compositing support is there, but no compositing window manager (compiz) will run. Bug 173663
[15:55] <ubotu> Launchpad bug 173663 in linux-restricted-modules-2.6.22 "compiz will not launch with fglrx driver - falls back to metacity" [Undecided,New] https://launchpad.net/bugs/173663
[15:55] <WorkingOnWise> kalpik: I am not complaining. I know it will break. When they do, I thought this was the first place to come to begin to sort it out....
[15:56] <bardyr> Pici, whitelist fglrx :)
[15:56] <Pici> bardyr: I did.
[15:56] <DanaG> One thing that DID surprise me:
[15:56] <bardyr> Pici, does aiglx/glx work?
[15:56] <Pici> And l-r-m hasnt built succesfully for i386 yet :/
[15:56] <DanaG> the supposedly "completely fair scheduler" actually makes my system much LESS responsive under load than it used to be.
[15:57] <Pici> bardyr: Nope.
[15:57] <kalpik> WorkingOnWise, yeah.. this is a good place to start.. but you would see more activity in this channel around alpha 4. Also when you report a bug, launchpad shows you related bugs.. the search algorith is VERY good.. if its been reported previously, there's a 99% chance it will show you the bug :)
[15:57] <Pici> bardyr: It is using aiglx
[15:57] <Pici> I cant really do any testing here fyi, I'm only on an ssh connection to that computer.
[15:59] <WorkingOnWise> kalpik: thanks. I have run  previous alphas (Gutsy and Fiesty) but with the intent of just farmilurizing with maintenance and repair. This time I thought I might try helping the development too...:)
[15:59] <kalpik> WorkingOnWise, that's the spirit! alphas FTW! :D
[16:01] <bardyr> i just run alphas because i love the bleeding edge and breakning things
[16:01] <jtt> where is the hardy alpha?
[16:02] <jtt> iso that is
[16:02] <bazhang> am I the only that having a non-broken hardy experience so far?
[16:02] <WorkingOnWise> I do it because the breakage is comfortable...been a M$ junkie for years. Dont know what to do without a BSOD a few days a week  :)
[16:02] <WorkingOnWise> sory....ot, I know
[16:03] <bardyr> bazhang, then you havent played around yet and run good hardware
[16:04] <bazhang> bardyr: au contraire :}
[16:08] <livingdaylight> is anything really exciting expected for Hardy?
[16:09] <livingdaylight> anything dramatic innovative? or is the work going into consolidation and stability?
[16:10] <bardyr> livingdaylight, kernel 2.6.24 has some interesting things
[16:11] <livingdaylight> bardyr, oh...??
[16:11] <bardyr> and they are going to redo the hardware detection to use more better upstream
[16:12] <livingdaylight> so, it sounds like the efforts are going more into consolidation then rather than flashy innovation
[16:12] <bardyr> livingdaylight, like the new schedule CFS and bunch of better drivers
[16:13] <bardyr> livingdaylight, yea but ubuntu needs that atm
[16:13] <livingdaylight> fair enough
[16:14] <bardyr> just off because the first LTS is very old and because i feel like ubuntu is being more and more "buggy"
[16:14] <bardyr> i dont know how to make sense of that sentence btw
[16:15] <kalpik> bardyr, lol..
[16:15] <bazhang> pulseaudio?
[16:16] <kalpik> bazhang, you can get pulseaudio working on gutsy too.. with minimal efforts :P
[16:16] <bazhang> kalpik: thanks!
[16:16] <kalpik> bazhang, https://wiki.ubuntu.com/PulseAudio
[16:16] <bardyr> whats the problem with alsa or is pulseaudio just much better?
[16:17] <bazhang> thanks for the link! kalpik
[16:17] <DanaG> Gaack, my system is so sluggish now with the new scheduler.
[16:17] <DanaG> I'll type and the letters will take up to 1/4 second to show up.
[16:17] <kalpik> bardyr, just some more "flashy" features.. like on the fly switching between sound cards.. splitting your existing soundcard into two.. stuff like that
[16:18] <DanaG> PulseAudio won't use the surround feature on my cardbus Audigy.
[16:18] <bardyr> DanaG, sluggish?
[16:18] <DanaG> Yeah.
[16:18] <bardyr> DanaG, prioritize X
[16:19] <DanaG> I run two instances of Folding@Home in the background, niced to +19 and SCHED_IDLEPRIO, but now my system acts like those are high priority.
[16:19] <bardyr> lol
[16:19] <bardyr> isnt 19 high priority?
[16:19] <DanaG> It seems odd to me that the supposedly wonderful "completely fair scheduler" seems to disregard 'nice' levels.
[16:20] <DanaG> Positive is low priority -- extra "nice".
[16:20] <DanaG> It's really hard to type properly when keyboard input lags so severely.
[16:21] <bardyr> oh yea, by bad
[16:21] <DanaG> In fact, it'll even cause audio dropouts if I'm using PulseAudio's "Simultaneous Output" feature.
[16:21] <Pici> I always try to remember it as higher numbers are nicer to the processor because its giving it less work.
[16:22] <bardyr> ha, smart
[16:22] <bardyr> DanaG, CFS should respect nice
[16:23] <DanaG> For some reason, it's subjectively not being very 'nice'.
[16:30] <DanaG> Oh, and PulseAudio is niced to -11, yet it still gets dropouts caused by the +19 process.
[16:31] <DanaG> That's just plain wrong.
[16:31] <Tm_T> lovely
[16:31] <Tm_T> hug it?
[16:33] <AnRkey> I was thinking that the community could benefit from a Dell Idea Storm style website to get user feedback?
[16:33] <AnRkey> who would I bother about that?
[16:33] <AnRkey> :P
[16:34] <DanaG> Here's an idea for Dell: stop being cheap, and use gigabit ethernet!
[16:34] <bazhang> AnRkey: build it and they will come :}
[16:34] <DanaG> A friend of mine got a nice new XPS M1330 notebook, and I was surprised to see that it only has 100 megabit ethernet.
[16:34] <DanaG> On a """"high end"""""" notebook.
[16:35] <AnRkey> thanks wayne
[16:35] <DanaG> Or rather, not high end, but "extra special"
[16:35] <AnRkey> but will the dev guys use the data it collects?
[16:36] <AnRkey> I was thinking something like ideastorm.ubuntu.com
[16:43] <DanaG> LAG.
[16:44] <Dr_willis> a 'high prioced' notebook. :)
[16:44] <DanaG> aah, then there's the key.
[16:45] <DanaG> High priced but not actaully as high-featured as they'd like you to think.
[16:45] <DanaG> Now here's something I really wanna' see in a notebook: audio chip with independent streaming.
[16:45] <DanaG> Front outputs for notebook speakers, and then full surround outputs too, as a separate device.
[16:45] <DanaG> Gaack, damn typing laggagagag.
[16:47] <Dr_willis> Im waiting for those Eee's to get more common. :) i want one.
[16:49] <Tm_T> I don't :p
[16:49] <DanaG> I'd wait for them to not use a celeron.
[16:49] <DanaG> How stupid: ultraportable notebook with an ultra-lacking-power-savings-features celeron?
[16:50] <Dr_willis> not really an issue for me.
[16:50] <Dr_willis> I just want somthing smaller to put in my lunchbox for me to use at work.
[16:50] <Dr_willis> 'price range dictates all'
[16:51] <Dr_willis> or so the pc/laptop market seems to be now a days
[16:51] <DanaG> At least they could've socketed the thing...
[16:51] <Dr_willis> No idea on that. :) i dont have one yet.. so i cant open it up.
[16:51] <Dr_willis> I wonder how well it plays videos actually.
[16:51] <bazhang> very well
[16:52] <Dr_willis> i got my laptop set up with GeeXbox. so i can boot to a video player in like 20 sec.
[16:52] <bazhang> hd is superb, but this is way offtopic..sorry
[16:52] <Dr_willis> its a small laptop. but still a bit big for me to be lugging around.
[16:52] <Dr_willis> I do have ubuntu on my laptop also. :)
[16:52] <Dr_willis> Does that count as on topic? heh heh..
[16:53] <Dr_willis> Id want to put ubuntu on the EEE also.
[16:53] <bazhang> haha likely not--you should join #eeepc
[16:53] <bazhang> or visit the site www.eeeuser.com
[16:54] <Dr_willis> That was one of the worst sites ive seen :) it was all Flash!
[16:54] <bazhang> haha
[16:54] <Dr_willis> it was one big comercial.. told ya very little about the actual product.
[16:54] <bardyr> i dont know if i should buy a EEE or a mini gPC laptop
[16:55] <Dr_willis> I may get me an EEE for my birthday  heh. wife will say 'what do ya need another laptop for'
[16:55] <bazhang> maybe youre thinking of asus' website--the link above is from actual users--nice wiki and forums
[16:55] <bardyr> Dr_willis, well its not a "computer"
[16:55] <Dr_willis> Been eyeing those Nokia  things also.
[16:55] <Dr_willis> bazhang,  proberly
[16:55] <Dr_willis> It is a nice trend to see low priced/flexiable micro-sized comptuers.  getting common.
[16:56] <Dr_willis> I rember portable "dos pc's" with  little 8x16 lcd type screens.. ages ago.  egad i am old.
[16:57] <h3sp4wn> Dr_willis: There is an 8GB version coming out in the not too distant future (of the EE)
[16:57] <DanaG> I wish I could fix that **** CFS scheduler.
[16:57] <Dr_willis> h3sp4wn,  yep. thats what i am waiting for i think. :) or the price drop on the low end one. when the 8 comes out.
[16:57] <h3sp4wn> DanaG: Its just fair - did you try using schedtool ?
[16:57] <DanaG> Yeah.
[16:58] <DanaG> And I'm even running folding@home as SCHED_IDLEPRIO.
[17:00] <h3sp4wn> and you have the sound at real time ?
[17:02] <DanaG> It's +11, but it's not going realtime for some reason.
[17:02] <DanaG> oh wait, I think not-realtime is default.
[17:02] <DanaG> er, pulseaudio is -11.
[17:02] <bardyr> DanaG, look at the bright sight, you are flooding alot!
[17:03] <bardyr> foolding*
[17:04] <DanaG>  W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
[17:09] <DanaG> That's odd.
[17:09] <DanaG> PulseAudio is installed suid root...
[17:09] <DanaG> And I am a member of pulse-rt.
[17:21] <DanaG> gaaaaaaacackkck.
[17:22] <DanaG> Somebody else using 2.6.24: try running something cpu-intensive at nice +19, and see if it bogs down the rest of the system.
[17:23] <DanaG> That was odd... gdm just segfaulted.
[17:23] <bazhang> how does one do that DanaG?
[17:24] <bazhang> the nice +19 part I mean
[17:24] <DanaG> Try this: nice +19 sh -c 'cat /dev/zero'
[17:24] <bazhang> okay, just a moment
[17:24] <DanaG> just nice NUMBER COMMAND
[17:24] <DanaG> If you have dual core, it may take two instances to make it happen.
[17:25] <DanaG> er
[17:25] <DanaG> nice -n +19 cat /dev/zero
[17:25] <bazhang> firefox with a bunch of flash tabs open should do it, yes?
[17:25] <DanaG> AAAAAAAAAAAAAAAAAAAaaaactually, it seems like it's already slowing down at only one instance.
[17:26] <DanaG> I'm testing nice load, specifically.
[17:26] <DanaG> If I'm not running my folding, then everything works nicely enough, including firefox.
[17:27] <bazhang> so perhaps its folding and not ubuntu
[17:27] <DanaG> But even just 'cat /dev/zero' niced to +19 is making it slow.
[17:28] <DanaG> Anyway, I have to go to an appointment.  I'll be back (quite) a while later.
[17:28] <DanaG> Bye.
[17:34] <bazhang> no real slowness detected--though I was just running several apps--don't have folding installed
[18:23] <WorkingOnWise> which flash plug in works best, Adobe or Gnash?
[18:23] <WorkingOnWise> in AMD64?
[18:24] <bardyr> adobe
[18:24] <bardyr> gnash has still not full flash support
[18:25] <nanonyme> gnash has had some stability issues too
[18:25] <Tomcat_> WorkingOnWise: gnash should be good for youtube vids, but I'd suggest Adobe.
[18:29] <WorkingOnWise> ty.
[19:02] <NumBeast> how far along is Hardy?
[19:03] <pwnguin> almost alpha 2
[19:03] <pwnguin> but mostly, a month and a half in
[19:04] <pwnguin> most all the software has been refreshed from debian -- i think the kernel's still being kept away from users
[19:04] <NumBeast> allright
[19:05] <NumBeast> what new features are planned
[19:05] <pwnguin> https://blueprints.launchpad.net/ubuntu/
[19:06] <frojnd> hello
[19:06] <pwnguin> looks like they're pushing in windows authentication integration
[19:07] <Pici> Yeah, linux-restricted-modules isnt building on i386, I think thats a main reason why we havnt seen it yet.
[19:08] <NumBeast> windows authentication integration?
[19:08] <NumBeast> like replacing gksudo?
[19:09] <frojnd> I have a question. Is someone willing to check a clip if I give'em url, its wmv and the content isn't exactly OK for everyone, (girl dancing and oiling herself) But it's not pron. What I'm trying to do is to figure it out what's the title of the song that's in the bacground. So is anyone willing to hear this, if he/she doesn't want to watch this. But I will only give link in a private window, because As I said someone don't allow this on other
[19:09] <frojnd> chans...
[19:10] <frojnd> pretty weird situation for me too :S
[19:10] <NumBeast> what genre is the song
[19:10] <NumBeast> but shouldn't that be in a different channel?
[19:10] <frojnd> NumBeast, man vocal
[19:10] <Pici> frojnd: Ignoring the content of the question, this isn't that kind of channel.  Second of all, you getting banned from -offtopic wasn't enough of a hint that this isn't welcome here?
[19:11] <frojnd> Pici, oh here you are... I ask polite ... please direct me in channels that are more for talk..
[19:11] <frojnd> on freenode I only know for linux, ubuntu, kubuntu
[19:11] <frojnd> that's it
[19:11] <frojnd> and now for offtopic for ubuntu
[19:12] <frojnd> So Pici what's the chaannel for regular talking on freenode
[19:12] <Pici> frojnd: Do you understand why this isnt allowed here?
[19:12] <frojnd> Oh I see..
[19:12] <frojnd> it's for hardy heron
[19:12] <Pici> frojnd: The only think I can think of is #defocus, but you should ask before just blindly posting a link.
[19:13] <frojnd> I'll keep that in mind
[19:13] <Pici> frojnd: can you join me in #ubuntu-ops please?
[19:13] <frojnd> Pici, sure
[19:14] <pwnguin> NumBeast: like ldap
[21:07] <NumBeast> where can I download hoary source?
[21:07] <DanaG> Gaack, whose bright idea was that blinking magnifying-glass icon?
[21:07] <tumbleweed__> NumBeast : you mean hardy?
[21:08] <NumBeast> sorry, I do mean hardy
[21:08] <tumbleweed__> I make that mistake all the time too :P
[21:23] <DanaG> blink
[21:23] <DanaG> blink
[21:23] <DanaG> magnifying glass
[21:23] <DanaG> (wow, that icon is annoying!)
[21:24] <tumbleweed__> lul
[21:24] <tumbleweed__> what magnifying glass?
[21:24] <DanaG> The tracker applet.
[21:24] <tumbleweed__> oh
[21:24] <tumbleweed__> yeah
[21:24] <tumbleweed__> oh
[21:24] <tumbleweed__> and just so you know
[21:25] <tumbleweed__> multimedia keys don't work off the bat in ubuntu if you choose to use xfce
[21:27] <DanaG> Go to keyboard preferences and set your layout there -- that may fix it.
[21:32] <NumBeast> DanaG: isn't there an option to disable that?
[21:33] <tumbleweed__> ummm
[21:33] <NumBeast> DanaG: the infernal blinking
[21:33] <tumbleweed__> DanaG : nope
[21:37] <NumBeast> so where can I get the hardy source?
[21:37] <hydrogen> huh?
[21:41] <NumBeast> is the hardy source available for download, and if it is, where can I find it
[21:41] <hydrogen> what do you mean?
[21:46] <theunixgeek> What features will be available in Hardy Alpha 2?
[21:50] <theunixgeek> What features will be available in Hardy Alpha 2?
[21:51] <NumBeast> I suppose hardy is in development
[21:51] <NumBeast> and probably has source code
[21:51] <NumBeast> is that source code available to the public
[21:51] <theunixgeek> NumBeast: yes.
[21:51] <hydrogen> NumBeast: you havn't really clarified *what* source code you are after
[21:52] <NumBeast> where could I find that source code?
[21:52] <theunixgeek> NumBeast: ubuntu is open source
[21:52] <hydrogen> hardy is primarly a compilation of new versions of packages
[21:52] <hydrogen> all put together under one big distro umbrella
[21:52] <NumBeast> ah
[21:52] <NumBeast> sorry
[21:52] <hydrogen> do you want the source to every package?
[21:52] <hydrogen> or just ones new to hardy?
[21:53] <NumBeast> just the new ones to hardy
[21:53] <NumBeast> sorry, I want to test hardy
[21:54] <NumBeast> on a computer that doesn't have already ubuntu
[21:55] <NumBeast> and I would like to know either where to find a .img, or where to find what I need to compile to make an .img
[21:55] <hydrogen> oh
[21:55] <hydrogen> you want the cd
[21:55] <hydrogen> image
[21:56] <NumBeast> yes please
[21:56] <hydrogen> http://cdimage.ubuntu.com/daily/20071218/ is todays build
[21:56] <NumBeast> thank you
[21:56] <hydrogen> or you could look for the alpha image
[22:07] <PirateHead> If the Fawn alphas were called herds and the Gibbon releases were called tribes, why aren't the Heron alphas called flocks?
[22:10] <tumbleweed__> PirateHead : because king nelson mandella said so.
[22:39] <Erealz> hey all
[22:40] <Erealz> umm is anyone running hardy heron and if so how those it run compared to gusty?
[23:59] <infinitycircuit> does anyone know why dynticks is not enabled in the hardy kernels
[23:59] <infinitycircuit> 2.6.24 branch that is


[04:47] <cpaelzer> blackboxsw: you were late to reply, but you beat it by replying twice :-)
[15:11] <lucidguy> Ok, can you not set ssh-authorized-keys for the root account?
[15:11] <lucidguy> via cloud-init
[15:19] <blackboxsw> lucidguy: you can, just provide a cloud config like the following :
[15:19] <blackboxsw> #cloud-config
[15:19] <blackboxsw> disable_root: false
[15:19] <blackboxsw> ssh_authorized_keys:
[15:19] <blackboxsw>   - ssh-rsa AA.....
[15:20] <blackboxsw> found per http://cloudinit.readthedocs.io/en/latest/topics/modules.html#ssh
[15:20] <lucidguy> I tried that, minus the disable_root
[15:20] <blackboxsw> cloud-init automatically disables the root user for securtiy
[15:20] <blackboxsw> cloud-init automatically disables the root user for security. yeah have to turn that default feature off
[15:21] <lucidguy> Thanks blackboxsw
[15:22] <blackboxsw> no problem
[15:23] <lucidguy> I hope its also not an issue with this centos6.9 cloud image
[17:07] <blackboxsw> powersj: rharper https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/347824 for integration test breakage on artful containers per https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-lxd-a/377/console
[17:11] <powersj> \o/
[17:16] <blackboxsw> bah good review powersj fixing that conditional was bogus :/
[17:17] <blackboxsw> cut-n-paste fail
[17:18] <blackboxsw> pushed e5baa98996aacd7a1906fad4a77a0aaa679f5827 powersj
[17:18]  * powersj looks
[17:21] <blackboxsw> thx .landing once jenkins is happy again on that branch
[17:23] <blackboxsw> salt_minion you are next on my radar buddy: https://jenkins.ubuntu.com/server/job/cloud-init-integration-nocloud-kvm-b/212/console
[17:29] <powersj> blackboxsw: will both of those make us all green again?
[17:31] <blackboxsw> powersj: I think that will do it for cloud-init. (integration-b and  integration-c are both salt_minion I think (on all platforms)
[17:32] <powersj> sweet
[17:32] <blackboxsw> so it feels like a bug in how cloud-init writes salt minion keys.
[17:32] <blackboxsw> in bionic++
[17:32] <blackboxsw> but hadn't really gotten to a proper solution yet. (that citest --preserve-instance param will help now)
[18:40] <blackboxsw> another one for readability in jenkins rharper powersj https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/347833
[18:40] <rharper> looking
[18:40] <powersj> oh yes please
[18:41] <rharper> indeed
[18:41] <blackboxsw> yeah I finally hit my limit with that giant dict of hopelessness
[18:42] <blackboxsw> so much time wasted searching the browser for FAILURE: or FAILED: etc
[18:43] <blackboxsw> good thoght rharper will drop all those indents
[18:48] <blackboxsw> rharper/powersj: updated the decription with the new output   I'm all ears for other formatting thoughts
[18:48] <rharper> lemme see
[21:21] <blackboxsw> powersj: rharper eureka. found the salt-minion error for jenkins on bionic ++
[21:22] <rharper> \o/
[21:22] <powersj> sweet
[21:22] <blackboxsw> newer versions of salt-minion auto-move /etc/salt/pki/minion files over into /var/lib/salt/pki/minion/* no logs tell you about the behavior. even setting log_level:trace gives me no info about this
[21:23] <blackboxsw> though I did see that trace presented an authentication request to the salt master I had to set up. it contained a new path that I hadn't written:  Initializing new AsyncAuth for ('/var/lib/salt/pki/minion', 'b3', 'tcp://<IP_ADDRESS>:4506')
[21:24] <rharper> sneaky
[21:24] <blackboxsw> man. that was a bit tedious. but I know know how to setup salt_master on ubuntu to auto-accept new-client certs :)
[21:24] <blackboxsw> I'm going to write a tiny blog on this
[21:25] <blackboxsw> s/know know/now know
[21:27] <rharper> blackboxsw: yeah, good content with some cloud-init in there = )
[21:57] <blackboxsw> ok salt_minion integration test passes on bionic/cosmic
[21:57] <blackboxsw> putting up another small mp.
[22:12] <blackboxsw> ok it's up https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/347856
[22:35] <blackboxsw> rharper: powersj  if either of you have a chance on that mp above. it could get us green on jenkins
[22:37] <powersj> blackboxsw: land it ;)
[22:41] <blackboxsw> thanks powersj


[00:25] <wallyworld> axw: when you get a chance, no rush, a small tweak to series validation. i'll then update dep in the master pr https://github.com/juju/charm/pull/198
[00:40] <davecheney> thumper: https://github.com/juju/juju/pull/4688
[00:41]  * thumper looks
[00:41] <davecheney> i tried a few ways yesterday to merge these two handlers into one
[00:41] <davecheney> but as the one from api/private/server comes with a compelte implementation of a python mocking framework
[00:41] <davecheney> it was infeasable
[00:41] <davecheney> this is a smaller change which does the same thing
[00:41] <davecheney> and the author of the original code will have to figure out how to merge the two types
[00:45] <thumper> davecheney: change looks good +1
[00:46] <davecheney> thumper: ta
[01:13] <thumper> hmm... third time today I've hit bad record mac trying to land things
[01:16] <thumper> wallyworld: can you meet early?
[01:16] <wallyworld> thumper: sure, give me a couple of minutes
[01:16] <thumper> ok
[01:24] <natefinch> evening all
[01:28] <alexisb> evening natefinch
[01:28] <katco> natefinch: kiddo feeling any better?
[01:29] <natefinch> katco: not really... she's only had water & pedialyte since 6pm last night, and threw up even the water just before bed tonight.  But that's only #3 since 8am, so I'll take it over last night, for sure.
[01:30] <katco> natefinch: jees :(
[01:31] <natefinch> katco: my wife is slightly better off... she's managed to have, I think, two crackers, besides various liquids since around 8pm last night.   Crazy bad virus.
[01:32] <alexisb> natefinch, that sounds terrible :(
[01:34] <natefinch> alexisb: OMG, it was horrible.    Another guy on my team kept doing that... the aggravating thing was that he didn't notice, which made me really wonder if he even looked at what he was checking in.
[01:47] <natefinch> katco: ericsnow left a comment on my charmrepo PR about this needing to get merged into the new-channels-model branch.  Should I just PR this against that branch as well?  ref: https://github.com/juju/charmrepo/pull/65
[01:59] <natefinch> katco: just landed that 3 pointer in charmrepo.v2 (master)
[02:12] <davecheney> thumper, menn0: https://github.com/juju/juju/pull/4691
[02:12] <davecheney> followup from previous CL
[02:12] <menn0> davecheney: thumper is about to drive up to Christchurch so i'll do it
[02:13] <davecheney> ta
[02:13] <davecheney> this is more refactoring to remove the apisever/common dependency from the resource/api
[02:13] <davecheney> because apiserver imports resource/api
[02:13] <davecheney> so if I want to move apiserver/common.ServerError to apiserver
[02:13] <davecheney> i need to break that import loop
[02:14] <davecheney> and i want to move apiserver/common.ServerErr to apiserver to pay down the technical debt from the UpgradeInProgress refactor
[02:39] <cherylj> menn0: ping?
[02:40] <menn0> cherylj: howdy
[02:41] <cherylj> menn0: hey there, wanted to pick your brain on this mongo problem
[02:41] <cherylj> so we had mario run mgopurge
[02:41] <cherylj> and we told it to skip objects with an invalid token
[02:42] <cherylj> but I was wondering...  do those need to get cleaned up anyhow?
[02:42] <cherylj> some how?
[02:42] <menn0> cherylj: yeah, i was going to reply to that email thread today but have been flat out
[02:42] <cherylj> we're panicking in the same sort of way now in jujud - the token is invalid
[02:43] <menn0> cherylj: are the bad txn tokens in the txn-queue field?
[02:43] <menn0> cherylj: if so, yes they'll need to be removed. I kind thought that's what we were getting mgopurge to do but I could be misremembering
[02:43] <cherylj> menn0: that's what I'm wondering / thinking.  I haven't downloaded the db yet to look
[02:43] <menn0> cherylj: seems likely if that's the case
[02:44] <menn0> cherylj: mgo/txn will be trying to look up those txns, failing to find them and panicking
[02:44] <cherylj> menn0: but what I added in to prevent mgopurge from panicking was just to skip those transactions
[02:44] <menn0> cherylj: I was going to say on the email that they should get the replicaset healthy *before* trying to fix anything else
[02:44] <cherylj> maybe there's something else I need to add which removes them from the queue
[02:45] <cherylj> menn0: it sounds like they've done that
[02:45] <menn0> cherylj: he said that 2 out of the 3 nodes are ok
[02:45] <menn0> cherylj: that's not healthy
[02:45] <menn0> cherylj: they should get that 3rd node happy again first
[02:45] <cherylj> menn0: ah, gotcha
[02:46] <cherylj> menn0: I can ask Mario to do that
[02:47] <menn0> cherylj: and it sounds like making mgopurge remove the bad txn tokens needs to happen too
[02:47] <menn0> cherylj: a bad/empty token should just be treated the same as a missing txn
[02:47] <cherylj> menn0: yeah, that's what I was thinking.  I'll take a closer look at the PurgeMissing code
[02:47] <menn0> cherylj: the same logic that removes missing txns from the txn-queue field can then be used to remove the bad ones too
[02:51] <cherylj> bleh this mgo stuff is hard to read
[03:08] <katco> natefinch: i'd say just master and they an bug us if the merge conflicts are too bad
[03:20] <axw> wallyworld: charm change LGTM
[03:21] <wallyworld> tyvm
[03:48] <axw> wallyworld: adding cloud name, etc. to controllers.yaml doesn't really work :/   if you did "juju register", we've got nowhere to pull that information from
[03:48] <axw> wallyworld: so I think it goes back into bootstrap-config.yaml, and we cross-reference that in list-controllers
[03:52] <wallyworld> axw: ok, let's go with that; we can be clear about the limitations. the only other option i guess it to make an api call
[03:52] <rick_h__> axw: is this for the provider type info?
[03:53] <axw> wallyworld: IMO that's out of the question
[03:53] <wallyworld> yeah, agreed, was just making sure we covered all options
[03:53] <axw> rick_h__: sorta. it's for that, plus the bits we need to kill-controller if the controller is dead
[03:53] <axw> rick_h__: we could store the provider type easily, but the other information not so much
[03:53] <rick_h__> axw: ah ok, for the provider type user query I'd hope we could put that in the show-controller metadata
[03:53] <rick_h__> axw: gotcha
[03:54] <rick_h__> axw: yea, /me didn't catch the rest of the convo for the kill-controller link
[03:54] <axw> rick_h__: two birds, one stone :)
[03:54] <rick_h__> axw: yea, but let's make sure they're both birds and not one moose and one bird
[03:54] <axw> ;)
[03:55] <rick_h__> no thumper? curses
[04:16] <menn0> rick_h__: thumper is driving up to christchurch (where I live). he's taking his kids to a convention up here.
[04:16] <menn0> rick_h__: can I help at all?
[04:36] <axw> wallyworld: just thinking out loud... we could forget about storing the credential label/origin, and just auto-detect and use whatever it returns, like at bootstrap
[04:37] <axw> wallyworld: and if none auto-detected, say something like "no credentials detected". I guess the origin is still useful though...
[04:38] <axw> wallyworld: (just trying to minimise surface for such a corner case)
[05:24] <wallyworld> axw: sorry, was out with anastasia talking lxd image caching. yeah, we went around and around on minimising the serface for the corner case didn't we. but the idea of storing the label/origin is so that if we autodetected the wrong credentials, we could prompt for the correct ones
[05:24] <wallyworld> but is the effort worth it
[05:24] <axw> wallyworld: yeah, I suppose so. I'll add it later, doing the minimal work for now to support lxd
[05:25] <wallyworld> sgtm. i don't think it's that much extra to store the label/origin, let's take a view once things have settled a bit
[08:00] <TheMue> morning o/
[08:10] <mup> Bug #1555969 opened: API server stops responding after juju add-unit <juju-core:Triaged> <https://launchpad.net/bugs/1555969>
[08:21] <axw> wallyworld: if you're around later and feel like looking, here's the WIP: https://github.com/juju/juju/compare/admin-controller-model...axw:bootstrapconfig-partial-ondemand
[08:22] <axw> wallyworld: all working, lots of tests to update now.
[09:12] <frobware> voidspace: did this (http://reviews.vapour.ws/r/3955/) get back into master?
[09:13] <voidspace> frobware: well, the code it was changing wasn't on master I don't think
[09:14] <voidspace> frobware: I can have a look
[09:15] <voidspace> frobware: the subnetToSpaceIds function it changes doesn't exist on current master
[09:15] <dimitern> frobware, hey, I've realized I gave you bad advice yesterday wrt dependencies.tsv :/
[09:15] <frobware> dimitern: so let's fix it before we merge to master
[09:15] <dimitern> frobware, those imports which were removed with the master merge caused issues on windows
[09:16] <frobware> dimitern: I was looking at the report
[09:16] <dimitern> frobware, yeah, I suppose just adding back the missing ones will fix 3 of the curses
[09:16] <frobware> dimitern: can I just merge in what I had done?
[09:16] <frobware> originally
[09:16] <menn0> fwereade__: i'm aiming to review your model agent integration PR soon
[09:16] <dimitern> frobware, I'd try to use GOOS=windows godeps -N ... as suggested in the linked bug report
[09:16] <frobware> voidspace: if we're going to get maas-spaces2 into master next week we can wait till then
[09:17] <frobware> voidspace: I was just curious if you ported that single fix into master. I guess not because it was only broken on maas-spaces2
[09:18] <voidspace> frobware: right, it *couldn't* be ported to master...
[09:22] <dimitern> dooferlad, hey, I see getMongoSpace changes caused a data race in the last CI run
[09:22] <dooferlad> dimitern: really? Grr.
[09:22] <dimitern> dooferlad, can you have a look at that? http://reports.vapour.ws/releases/3735/job/run-unit-tests-race/attempt/1095#highlight
[09:23] <dooferlad> dimitern: on it
[09:23] <dimitern> dooferlad, cheers
[09:23] <fwereade__> menn0, <3
[09:24] <fwereade__> menn0, I recommend ignoring everything under worker/dependendency; core/life; and all the */lifeflag bits
[09:24] <fwereade__> menn0, because I can and will extract those
[09:24] <menn0> fwereade__: ok will do
[09:25] <dimitern> frobware, in my experiments yesterday I found this quick hack significantly reduces the initial boot time: http://paste.ubuntu.com/15346394/
[09:26] <dimitern> frobware, ~2m (average) from allocated to deployed
[09:41] <frobware> dimitern: the bridge wait I understand, the ntp is a step too far...
[09:43] <dimitern> frobware, that's because of the race I was telling you about when trying to ifup a lot of static interfaces
[09:44] <dimitern> frobware, I was seeing 4-5 bash instances trying to run ntpdata and getting blocked on trying to create a lockfile
[09:47] <frobware> dimitern: I'm going to try an experiment with a one-time reboot post our butchering of eni
[09:47] <frobware> dimitern: but somewhat secondary to getting the devices work done
[09:48] <dimitern> frobware, I tried that as well - depending on when you reboot, it might not work at all - e.g. before installing bridge-utils
[09:48] <dimitern> frobware, agreed
[09:48] <frobware> dimitern: the bridge-utils is a pre-req so is already present before we run the script
[09:49] <dimitern> frobware, yeah, that's assuming we got the chance to even run apt-get install bridge-utils
[09:49] <dimitern> frobware, which will happen after the bridge script completes
[09:56] <frobware> dimitern: it happens the other way round.
[09:56] <frobware> dimitern: our script would fail catastrophically if it wasn't present
[09:57] <frobware> dimitern: you can see this if you deploy from MAAS, cp the script, and run it. the whole thing fails because there is no brctl
[09:59] <dimitern> frobware, that's what I'm talking about :)
[09:59] <dimitern> frobware, since the script runs as a bootcmd, it will run before any packages listed in the generated userdata are installed..
[09:59] <frobware> dimitern: I was confused. you said "after the bridge script completes"
[10:00] <dimitern> frobware, hmm.. I might be wrong - just observed something like that
[10:01] <frobware> dimitern: there is no way we could bring the interface up without bridge-utils being there
[10:01] <frobware> dimitern, voidspace, dooferlad: standup/planning
[10:02] <voidspace> frobware: omw
[10:51] <menn0> fwereade__: review done. lots of great stuff. thank you. it will be great to get this landed.
[10:53] <dimitern> frobware, this is the gist of what's needed: http://paste.ubuntu.com/15346665/, and those API calls follow the pattern in http://paste.ubuntu.com/15241590/
[10:53]  * menn0 bed
[10:55] <dimitern> frobware, so if we agree on the interface, I can use a stub for now, and later we integrate
[10:56] <dimitern> frobware, let me know what you think
[10:59] <frobware> dimitern: will look in a bit
[11:03] <frobware> dimitern: I don't see a great deal of diff with your godeps incantation; https://pastebin.canonical.com/151643/
[11:05] <dimitern> frobware, that's exactly the missing import causing the curse
[11:05] <frobware> dimitern: :) yes, just read the bug.
[11:06] <dimitern> frobware, well, now we know what this package is for :)
[11:06] <frobware> dimitern: so another alternative is that we merge from master again this morning
[11:06] <frobware> dimitern: we would get that ^^ for free
[11:08] <dimitern> frobware, also works, and will give us updated lxd stuff as a benefit
[11:08] <frobware> dimitern: right, I'll do that instead.
[11:09] <dimitern> frobware, however, that should be followed up by dooferlad's fix not long after the merge lands in order not to waste a CI run
[11:09] <frobware> dimitern: good point
[11:13] <frobware> dimitern: can we HO re: the godeps stuff again. as in what's the best way to merge and or update it
[11:13] <dimitern> frobware, ok
[11:14] <dimitern> frobware, I'm in the sapphire HO (last one we used)
[11:55] <dooferlad> dimitern / frobware / voidspace: http://reviews.vapour.ws/r/4132/ fixes those races.
[11:57] <dimitern> dooferlad, looking
[11:59] <dimitern> dooferlad, did you run the test with -race?
[11:59] <dooferlad> yes
[12:00] <dimitern> dooferlad, so the issue is easy to reproduce and verify the fix
[12:01] <dimitern> dooferlad, LGTM, thanks that was quick :)
[12:01] <dooferlad> dimitern: yea, just running the tests with -race showed it and then it was just a moment of "oh crumbs, that was dumb"
[12:02] <dimitern> :)
[12:02] <frobware> dooferlad: we should try and land the changes close together; just running make check on my merge from master and will propose
[12:02] <dooferlad> frobware: I hit $$merge$$ about two seconds before you said that.
[12:03] <frobware> c'est la view
[12:03] <frobware> vie...
[12:03] <dooferlad> frobware: it will take some time to test, so as long as we get to reviewing your code soon we will be fine.
[12:32] <frobware> dimitern, voidspace, dooferlad: http://reviews.vapour.ws/r/4133/ -- merge master into maas-spaces2
[12:32] <voidspace> frobware: did you land one yesterday?
[12:32] <frobware> voidspace: yes
[12:32] <voidspace> frobware: ah yes, this one isn't as huge
[12:32] <voidspace> frobware: go for it
[12:32] <frobware> voidspace: that commit was also a blessed build.
[12:33] <frobware> voidspace: if there's one thing to look at its dependencies.txt
[12:33] <frobware> voidspace: I meant dependencies.tsv
[12:34] <voidspace> frobware: yeah, I looked - LGTM
[12:34] <voidspace> frobware: although we seem to be depending on stuff in people's own github repositories now
[12:34] <dimitern> frobware, looks good
[12:35] <dimitern> dooferlad, your fix should merge cleanly onto frobware's merge PR right?
[12:41] <frobware> dimitern: going to grab some lunch and then let's do devices... \o/
[12:41] <dimitern> frobware, sweet!
[13:05] <frobware> dimitern, voidspace, dooferlad: both merged. we should, in theory, get a blessed CI run now.
[13:07] <dimitern> frobware, let's hope we do :)
[13:13] <rogpeppe2> natefinch: ping
[13:31] <frobware> dimitern: whenever works for you let's sync
[13:31] <dimitern> frobware, in 15m ?
[13:32] <frobware> yep
[14:00] <dimitern> frobware, let's use the standup HO?
[14:01] <dimitern> frobware, well, last one we used anyway
[14:01] <frobware> ok
[14:24] <natefinch> rogpeppe: pong
[14:27] <mattyw> fwereade__, ping?
[14:35] <mup> Bug #1556113 opened: TestCleaner should have fired by now <ci> <go1.5> <go1.6> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1556113>
[14:35] <mup> Bug #1556116 opened: TestDeployBundleMachinesUnitsPlacement mismatch <ci> <gccgo> <ppc64el> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core maas-spaces2:Triaged> <https://launchpad.net/bugs/1556116>
[14:36] <fwereade__> mattyw, heyhey
[14:50] <mup> Bug #1556137 opened: Juju 2.0: cannot connect to LXC container when deploying bundle with LXC container placement <oil> <juju-core:New> <https://launchpad.net/bugs/1556137>
[14:59] <natefinch> ericsnow: let me know if you need help with that cards you took over from me
[15:02] <mup> Bug #1556137 changed: Juju 2.0: cannot connect to LXC container when deploying bundle with LXC container placement <oil> <juju-core:New> <https://launchpad.net/bugs/1556137>
[15:05] <mup> Bug #1556137 opened: Juju 2.0: cannot connect to LXC container when deploying bundle with LXC container placement <oil> <juju-core:New> <https://launchpad.net/bugs/1556137>
[15:13] <mattyw> ericsnow, ping?
[15:13] <mattyw> ericsnow, do you know if the todo comment at the top of this file is currently being worked on? https://github.com/juju/juju/blob/master/cmd/juju/charmcmd/store.go
[15:14]  * ericsnow takes a look
[15:15] <ericsnow> mattyw: not really
[15:15] <mattyw> ericsnow, ok that's fine, I might have to end up doing some of it for the stuff I'm working on, wanted to make sure I wasn't going to be duplicating work
[15:15] <ericsnow> mattyw: I have a patch that accomplishes that but haven't had a chance to pursue landing it
[15:16] <mattyw> ericsnow, i'd be interested in seeing that if possible
[15:16] <ericsnow> mattyw: k, thanks for the heads up
[15:16] <ericsnow> mattyw: looking it up as we speak
[15:16] <mattyw> ericsnow, many thanks
[15:22] <ericsnow> mattyw: pretty sure this is the branch: https://github.com/ericsnowcurrently/juju/tree/resources-charmstore-client
[15:22] <ericsnow> mattyw: it isn't quite right at this point, but the key thing is the httpcontext package
[15:23] <ericsnow> mattyw: however, it looks like the new "charm" command would use it too, so it may make more sense in some other common repo
[15:29] <ericsnow> natefinch: #1556146
[15:29] <mup> Bug #1556146: github.com/juju/juju/resource/api undefined: parseMediaType <ci> <go1.6> <regression> <xenial> <juju-core:Incomplete> <juju-core feature-resources:Triaged> <https://launchpad.net/bugs/1556146>
[15:29] <ericsnow> natefinch: bug #1556146
[15:29] <mup> Bug #1497801 changed: provider/joyent: data races <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1497801>
[15:29] <mup> Bug #1461961 opened: UniterSuite teardown fails <ci> <intermittent-failure> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1461961>
[15:29] <mup> Bug #1556146 opened: github.com/juju/juju/resource/api undefined: parseMediaType <ci> <go1.6> <regression> <xenial> <juju-core:Incomplete> <juju-core feature-resources:Triaged> <https://launchpad.net/bugs/1556146>
[15:32] <katco> ericsnow: natefinch: planning time
[15:34] <mattyw> ericsnow, thanks, I'll take a look
[15:39] <mup> Bug #1556152 opened: data race peergrouper.(*pgWorker).getMongoSpace() <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1556152>
[15:39] <mup> Bug #1556155 opened: worker/periodicworker data race <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1556155>
[15:48] <mup> Bug #1556152 changed: data race peergrouper.(*pgWorker).getMongoSpace() <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1556152>
[15:48] <mup> Bug #1556155 changed: worker/periodicworker data race <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1556155>
[16:00] <mup> Bug #1556152 opened: data race peergrouper.(*pgWorker).getMongoSpace() <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1556152>
[16:00] <mup> Bug #1556155 opened: worker/periodicworker data race <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1556155>
[16:03] <natefinch> ericsnow: review a single character bug fix? http://reviews.vapour.ws/r/4135/diff/#
[16:09] <mup> Bug #1556152 changed: data race peergrouper.(*pgWorker).getMongoSpace() <race-condition> <juju-core:Invalid> <juju-core maas-spaces2:Fix Committed by dooferlad> <https://launchpad.net/bugs/1556152>
[16:09] <mup> Bug # opened: 1556153, 1556157, 1556161, 1556167, 1556171
[16:31] <HollyRain> does the Juju license is going to change? the issue is that at using a library like "juju/service", it does that all my code been AGPL
[16:31] <natefinch> HollyRain: very doubtful that the license will change
[16:33] <HollyRain> natefinch, well, at least there is an alternative to handle services: kardianos/service
[16:33] <HollyRain> in github.com
[16:36] <natefinch> HollyRain: if you mean github.com/juju/juju/service - anything under github.com/juju/juju is not really intended to be used as a general library
[16:36] <HollyRain> ok
[16:39] <mup> Bug #1556176 opened: TestCmdLine dial unix no such file or directory <ci> <go1.5> <intermittent-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1556176>
[16:39] <mup> Bug #1556180 opened: MachineSuite.TestManageModelRunsRegisteredWorkers mismatch <go1.5> <go1.6> <intermittent-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1556180>
[16:39] <mup> Bug #1556183 opened: help text for list-controllers needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1556183>
[16:51] <frobware> cherylj: ping
[16:52] <cherylj> frobware: in stand up, responses will be slow :)
[17:16] <frobware> voidspace: you still about?
[17:19] <voidspace> frobware: yup
[17:19] <frobware> voidspace: any joy with MAAS 2.0? I didn't get around to installing...
[17:20] <voidspace> frobware: not yet, recloning my vm and installing xenial - about to install a newer version of maas (different ppa) that may fix the bug
[17:20] <voidspace> frobware: did some diagnostic work with roaksoax and he thinks it might be fixed in this version
[17:27] <mup> Bug #1556207 opened: 1.25.4: "tomb: dying" in all units <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1556207>
[17:30] <mup> Bug #1556207 changed: 1.25.4: "tomb: dying" in all units <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1556207>
[17:31] <frobware> cherylj: we've made sure that maas-spaces2 is up to date w.r.t to master. if we get a clean CI build on maas-spaces2 we'd like to merge into master and continue the multi-NIC and MAAS 2.0 work elsewhere. Is master still locked down?
[17:33] <cherylj> frobware: yes, we want to merge perrito666's machine-provisioning-status before we unblock
[17:33] <cherylj> frobware: if your branch is ready, we can put it on the list to get shepherded in next
[17:34] <frobware> cherylj: waiting to see if the couple of fixes we did today give us a blessed CI run; should find out a bit later.
[17:37] <cherylj> frobware: okay, cool.  I'll keep an eye on it
[17:42] <mup> Bug #1556207 opened: 1.25.4: "tomb: dying" in all units <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1556207>
[18:24] <katco> sinzui: hey, is this a spurious curse? http://reports.vapour.ws/releases#nate-minver
[18:31] <sinzui> katco: maybe. The lack of bless might be because the branch makes juju less reliable. The azure arm-bundle looks interesting. I can retest it
[18:32] <natefinch> spurious curse is the name of my goth metal band
[18:32] <katco> sinzui: thanks, i would appreciate it. i don't think there should be anything in there that would cause it to be less reliable
[18:32] <katco> sinzui: but appreciate your more informed opinion
[18:42] <mup> Bug #1556238 opened: Missing a Juju shell <juju-core:New> <https://launchpad.net/bugs/1556238>
[19:18] <mup> Bug #1556249 opened: help text for juju list-models needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1556249>
[19:48] <mup> Bug #1556252 opened: help text for juju show-user needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1556252>
[20:15] <marcoceppi> sinzui: is juju2 the name of the binary going forward?
[20:15] <marcoceppi> I noticed juju-core and juju are no longer listed and installing juju2 removes them
[20:21] <natefinch> marcoceppi: it's a vast underworld conspiracy
[20:28] <marcoceppi> well, it breaks the new charm and charm-tools command
[20:28] <marcoceppi> so I'd just like to align those packages
[20:29] <marcoceppi> it also means we can't install 1.25 and 2.0 sidebyside which completely kills this blog post from last week
[20:29] <marcoceppi> http://marcoceppi.com/2016/03/testing-juju-without-wrecking-juju/
[20:30] <marcoceppi> oh, jk, it doesn't break juju-core, just juju-core2
[20:30] <natefinch> marcoceppi: I'm 99% sure that we are supposed to be able to run them side by side.  WE've done a lot of work to enable that.
[20:30] <marcoceppi> I'm actually okay with that
[20:30] <marcoceppi> I'll jus tneed to update the packaging for charm and charm-tools
[20:31] <natefinch> marcoceppi: I think it's juju-core and juju (the latter being juju 2)
[20:31] <natefinch> marcoceppi: but I am certainly not the authority on these things
[20:31] <marcoceppi> natefinch: I upgraded and both versions are still there, I jus tneed to update the other packaging
[20:33] <natefinch> rick_h__, katco: charm publish --channel=stable cs:rabbit-22 --resources "foo-6 bar-3" ... this command seems to require that resource names not have spaces in them, in order to parse them in a single string like that.  Do we want to start to enforce that, or should we change this to be --resource foo-3 --resource bar-6?  or some third way?
[20:34] <katco> natefinch: yes, separate flags to mirror deploy
[20:34] <katco> natefinch: check out rick_h__ 's comment in the 1-pager
[20:34] <natefinch> katco: awesome.  I love consistency
[20:34] <katco> +1
[20:39] <marcoceppi> omg I just bootstrapped lxd \o/
[20:41] <natefinch> marcoceppi: huzzah
[20:57] <natefinch> katco: I kinda wish that for publish, it was --resource foo=3 --resource foo=5 ... but I understand that we're trying to make them like charm revisions, where it's part of the name
[20:57] <natefinch> s/foo=5/bar=5
[20:58] <katco> natefinch: yeah, i prefer = as well
[20:58] <katco> natefinch: but, precedent and all
[21:05] <katco> natefinch: ericsnow_afk: we don't need to do a standup
[21:05] <ericsnow> katco: k
[21:13] <sinzui> marco yes, juju2 is the package name. juju2 is also the name of binary.
[21:13] <sinzui> marcoceppi: if you havw juju-core and juju2 installed, you can use alternates to switch which Juju is /usr/bin/juju
[21:14] <marcoceppi> sinzui: right, it's just that juju2 removes some packages, including charm and charm-tools
[21:15] <sinzui> marcoceppi: it does? how?
[21:15] <natefinch> marcoceppi: hmm, that seems wrong.  It definitely shouldn't *remove* anything
[21:15] <sinzui> marcoceppi: a package cannot remove another package and it is intended to be co-installable.
[21:16] <perrito666> sinzui: cant a deb remove another if it is marked as conflicts or replaces?
[21:16] <marcoceppi> perrito666: yes
[21:16] <sinzui> perrito666: yes, replaces, but we don't use that. conflicts blocks and lets a user choose
[21:16] <marcoceppi> sinzui: juju2 removed juju which are depends on charm and charm-tools
[21:17] <perrito666> sinzui: I would re-check the package definition given what marcoceppi says
[21:17] <sinzui> marcoceppi: oh, I can remove that metapackage. we don't need it
[21:17] <marcoceppi> sinzui: which metapackage?
[21:17] <sinzui> juju is a metapackage marcoceppi. It hasn't been a real package in 4 years
[21:18] <natefinch> marcoceppi: welcome.... to the real world
[21:18] <perrito666> oh that is right, juju is to pull juju-core and juju-local right?
[21:18] <marcoceppi> sinzui: I know. but charm-tools, amulet, etc, depend on Juju
[21:18] <sinzui> right, and juju2 is really just juju2 now. no other deps
[21:19] <sinzui> marcoceppi: I think we need to drop the juju metapackage from the juju2 package. two source packages cannot provide it an be co-installable
[21:20] <natefinch> marcoceppi: what do charm-tools and amulet etc need from the juju package that isn't in core?
[21:20] <sinzui> marcoceppi: juju2 source package coul provide juju2-all or juju2-dev to get the authoring tools
[21:20]  * sinzui likes juju2-authors more than juju2-dev
[21:20] <marcoceppi> we just need juju installed whenever a user installs these tools
[21:21] <sinzui> marcoceppi: which juju needs to be install when someone installs those tools? if so, then shouldn't those package depend on juju-core or juju2?
[21:21] <marcoceppi> well either juju is fine
[21:21] <marcoceppi> just a juju
[21:21] <natefinch> marcoceppi: why do those tools need juju?
[21:21] <marcoceppi> hence the metapackage
[21:21] <marcoceppi> well, it's not a depends
[21:22] <marcoceppi> it's a Recommends
[21:22] <marcoceppi> the idea being that multiple things can provide a juju, so I'm just going to have it Recommend: juju2 || juju
[21:25] <sinzui> marcoceppi: the juju-core package we put in the ppa:juju/stable doesn't have a recommends or depends on amulet charm-tools. maybe the Ubuntu version of the package does
[21:29] <marcoceppi> sinzui:
[21:29] <marcoceppi> no amulet and charm-tools and charm recommends juju
[21:29] <marcoceppi> that way if you install them, you
[21:30] <marcoceppi> 'll get juju
[21:30] <marcoceppi> well, amulet depends on juju, the rest recommend it
[21:31] <sinzui> marcoceppi: okay, so amulet could "Depends: juju2 | juju-local"
[21:31] <marcoceppi> why juju-local? you mean juju-core?
[21:32] <sinzui> marcoceppi: yes, juju-core is fine for 1.x. I just assumed that a charm author would want local-provider
[21:33] <natefinch> OMG, so glad we dumped local provider for 2.0
[21:33] <sinzui> marcoceppi: I can add a metapackage to the new juju2 source package to install everything you think a charm-author needs.
[21:33] <sinzui> natefinch: \o/
[21:33] <sinzui> We can take half a day and close 200 bugs
[21:34] <sinzui> marcoceppi: also, we don't need to wait for the next release to remake the juju2 package to provide a metapackage for authors
[21:35] <ericsnow> natefinch: http://reviews.vapour.ws/r/4138/
[21:36] <marcoceppi> sinzui: well, I think juju2 should recommend the charm command
[21:36] <marcoceppi> sinzui: and charm depends on charm-tools
[21:36] <marcoceppi> and that'll all work
[21:39] <sinzui> marcoceppi: as in the charm package I see sitting in ppa:juju/devel... "Recommends: charm"
[21:40] <natefinch> what's the user-experience for "recommended" packages?
[21:40] <sinzui> natefinch: it will be installed, if it exists
[21:40] <natefinch> sinzui: so we're forcing every user of juju to install charm authorship tools?
[21:40] <sinzui> natefinch: the user can specify not to install recommends
[21:41] <sinzui> natefinch: I most often use recommends for cases where we know older ubuntu series don't have the optional package
[21:42] <natefinch> sinzui: I don't really see why juju would ever recommend charm authorship tools.  charm authors, in theory, should be like .1% or less of juju users
[21:42] <sinzui> natefinch: yeah, that is why I suggested a metapackage names charm-authors to be clear who wants the extra packages
[21:42] <natefinch> sinzui: agreed
[21:43] <natefinch> ericsnow: looking
[21:44] <natefinch> ericsnow: btw, thanks for tackling that..sorry you got burdened with the result of my misunderstanding.
[21:44] <ericsnow> natefinch: glad to do it
[21:45] <ericsnow> natefinch: it's all complicated by our usual high-coupling/low-encapsulation
[21:48] <natefinch> ericsnow: seems like we could use an AuthorizedCharm struct or something, that holds a CharmURL + macaroom
[21:48] <ericsnow> natefinch: I was totally thinking that the whole time :/
[21:48] <natefinch> ericsnow: or even slap a macaroom on the charm.URL struct
[21:48] <ericsnow> natefinch: yep
[21:49] <natefinch> blah
[21:58] <sinzui> perrito666: machine-provisioning-staus branch is merge
[21:58] <perrito666> sinzui: oh, you just made my weekend
[22:00] <natefinch> ericsnow: only had time for a half a review, sorry.  I'll finish up the rest later tonight.
[22:00] <natefinch> ericsnow: mostly looks good, just didn't get through it all.
[22:01] <ericsnow> natefinch: np
[22:01] <ericsnow> natefinch: thanks
[22:25] <mup> Bug #1556293 opened: Invalid volume ID <ci> <destroy-environment> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1556293>
[22:31] <alexisb> anyone know how I make this go away:
[22:31] <alexisb> checking: go vet ...
[22:31] <alexisb> tools/lxdclient/client_instance.go:329: wrong number of args for format in Tracef call: 1 needed but 2 args
[22:32] <alexisb> I can build and run locally on my machine
[22:32] <katco> alexisb: what version of go are you compiling with locally?
[22:33] <alexisb> 1.6rc2
[22:34] <katco> alexisb: and CI is giving you this error?
[22:35] <perrito666> katco: I had the same
[22:35] <perrito666> alexisb: its a vet issue introduced by jam
[22:35] <alexisb> so I can build locally but the "go vet" check in the prepush script is failing
[22:35] <alexisb> perrito666, ah ok
[22:35] <alexisb> I will follow-up with him
[22:36] <perrito666> alexisb: just go to that line and delete the second argument to the Tracef
[22:36] <katco> alexisb: ah... yeah vet is separate than building, but it's probably because CI is using a different version of go than you
[22:36] <perrito666> katco: is CI running vet?
[22:36] <katco> alexisb: they change how vet works between versions sometimes
[22:36] <katco> perrito666: it should be
[22:36] <katco> perrito666: that should be blocking imo
[22:36] <katco> perrito666: and i thought it was
[22:36] <perrito666> katco: me too
[22:36] <perrito666> but apparently it isnt
[22:37] <katco> perrito666: i think it is, and CI is just using an older version of go
[22:37] <katco> perrito666: thus, the change jam made is fine
[22:37] <perrito666> katco: I thought go vet was catching that before
[22:37] <perrito666> odd
[22:37] <perrito666> in any case, it breaks with go 1.5
[22:38] <katco> perrito666: ci is building with 1.2.1 still
[22:38] <katco> alexisb: perrito666: lots o' things have changed between 1.2.1 and 1.5, let alone 1.6r2
[22:38] <alexisb> katco, not for 2.0
[22:38] <perrito666> that explains
[22:39] <alexisb> for trusty we build with 1.2.1, until 1.6 is officially in updates
[22:39] <alexisb> that did it perrito666
[22:39] <katco> alexisb: i think our CI workers are still using 1.2.1. sinzui can you comment?
[22:39] <katco> alexisb: i.e. the workers that $$merge$$ changes
[22:40] <sinzui> katco: oh, the merge job is using a trusty ami, so it is using go 1.2.1
[22:40] <perrito666> sinzui: mm, that is wrong for 2.0
[22:40] <katco> alexisb: ^^^ hence, go vet change made it in, but is incompatible with go1.6-r2
[22:40] <sinzui> katco: The release agreed to switch to ggo 1.6 nexgt week
[22:41] <sinzui> and that that time, we expect master to be blocked as we fix bugs
[22:45] <sinzui> katco: the merge job nor Juju's one Makefile does not specific how to install a version of go on a temporary instance in AWS. It gets the version from the Ubuntu release. so switching to xenial images will select golang (2:1.6-0ubuntu3)
[22:47] <katco> sinzui: understood, and that sounds correct. just trying to inform alexisb
[22:48] <katco> sinzui: by the by, how goes the retest of nate-minver?
[22:49] <sinzui> katco: it failed? but I am looking to it still as a substrate issue the same bundle passed on other substrates
[22:49] <katco> sinzui: oh, i thought you were going to retest with a higher timeout? does this mean we can merge into master?
[22:50] <sinzui> katco: I did  and we still timeout
[22:51] <katco> sinzui: ah ok. what do i need to do to get it landed into master? just wait for you guys to work your magic?
[22:51] <sinzui> katco: If am hoping to retest and provide good results, or find some reason why the banch fails
[22:52] <katco> sinzui: ok, when will you know more?
[22:52] <sinzui> maybe by morning. katco.
[22:53] <katco> ok ta sinzui
[23:01] <alexisb> sinzui, thanks for pushing hard to get releases out this week, have a great weekend!
[23:02] <sinzui> thank you alexis. you too
[23:31] <mup> Bug #1551276 changed: 2.0-beta2 stabilization <juju-core:Invalid> <https://launchpad.net/bugs/1551276>


[09:06] <ApOgEE> salam semua
[11:36] <darknite> Assalamualaikumsalam wbt
[15:08] <fakrul> :)
[15:55] <fairuz_> helo rakan2
[15:55] <fairuz_> salam
[16:10] <fakrul> wslm wbt
[16:12] <fairuz_> takde admin tukar topik ka hehe
[16:28] <EgyParadox> can someone change the topic its kind of old?
[16:38] <fairuz_> EgyParadox: Agree
[16:39] <fairuz_> ping ejat-
[17:07] <EgyParadox> ejat-


[00:48] <raevol> surprised i haven't seen more talk about this: http://arstechnica.com/information-technology/2013/01/ubuntu-considers-huge-change-that-would-end-traditional-release-cycle/
[00:48] <darthrobot> Title: [Ubuntu considers “huge” change that would end traditional release cycle | Ars Technica]
[00:49] <pleia2> because immediately after Leann said that, Jane clarified that's they're in the very very early stages of discussion ;)
[00:50] <pleia2> http://www.pcpro.co.uk/news/379507/ubuntu-ceo-two-year-releases-are-only-an-idea
[00:50] <darthrobot> Title: [Ubuntu CEO: two-year releases are only "an idea" | News | PC Pro]
[00:50] <raevol> still an interesting proposal
[00:51] <pleia2> it would make it like debian
[00:51] <pleia2> testing is a rolling release, stable is released every 2 years or so
[00:52] <raevol> i think it's interesting because it means the ubuntu devs are, to some extent, confident in the stability of the development branch


[19:39] <ibeardslee> morning
[19:42] <ajmitch> morning
[21:58] <hads> Ubuntu keyboard; http://www.amazon.com/gp/product/B007W66BRG/
[22:08] <snail> hads: that's actually pretty tempting
[22:10] <ChrisNZ> yay ubuntu people
[22:11] <ChrisNZ> Is anyone here?
[22:11] <thumper> yes
[22:11] <thumper> about 20 others
[22:11] <ChrisNZ> lol Awesome
[22:11] <ChrisNZ> im moving all my company stuff away from MS
[22:12] <ChrisNZ> and i had some questions kinda if anyone was up for it
[22:12] <ChrisNZ> its mostly about SAMBA on Ubunutu 12.04 LTS
[22:12] <ChrisNZ> or am i in the wrong room :)
[22:12] <ajmitch> depends on what you want to know about it
[22:13] <thumper> well, you can ask...
[22:13] <ChrisNZ> ok, well ill give it a crack
[22:13] <ChrisNZ> basically i have a main region and sub regions, and im sharing samba across subnets.
[22:14] <ChrisNZ> so here comes my question, i wrote this down so ill cut n paste
[22:14] <ChrisNZ> Ubuntu 12.04 LTS
[22:14] <ChrisNZ> damn only pastes one line at a time lol
[22:15] <ChrisNZ> ok, bullet points, the darn thing works mostly, all samba shares work locally, with either usernames and pw or plain shares
[22:15] <ChrisNZ> all sub regions can connect using usernames and pw, or blank shares
[22:15] <ChrisNZ> main region can connect to sub region plain shares
[22:16] <ChrisNZ> main region cant connect to sub region password/username shares
[22:16] <hads> Who named liboobs
[22:16] <ChrisNZ> however, if i connect to the old windows 2003 VPN i can access the sub region samba
[22:17] <ChrisNZ> the regions are connected via IPSEC site to site
[22:17] <ChrisNZ> lol hads
[22:18] <ChrisNZ> when i try to browse the sub regions from the main region it jsut keeps asking for my username and password over and over, the same u/n and p/w that works via VPN connection or locally
[22:18] <ChrisNZ> so i guess my question is why cant i connect from the main region to the sub regions with usernames and p/w
[22:18] <ChrisNZ> when those work locally
[22:21] <ajmitch> that may be best asked in #ubuntu-server or on a support site like askubuntu.com if noone knows here
[22:21] <ChrisNZ> thanks man
[22:21]  * hads doesn't use SMB
[22:22] <ChrisNZ> I just cracked up as i was toying with the idea of asking TIM P if he knew
[22:22] <ChrisNZ> and then realised hes thumper
[22:22] <thumper> :)
[22:23] <ChrisNZ> Hey Tim, its Chris M, you know me from facebook and John E lol
[22:23]  * ajmitch only uses samba on the local network
[22:23] <hads> Sounds like some sort of silly broadcast thing.
[22:23] <thumper> hi ChrisNZ
[22:23] <ajmitch> veebers: see what I meant about small world last night?
[22:23] <ChrisNZ> lol
[22:23] <thumper> ChrisNZ: I've only used samba very simply, nothing complex
[22:24] <veebers> ajmitch: heh
[22:24] <ChrisNZ> Havent used IRC for ages, whats private message again?
[22:24] <ChrisNZ> i do agree it sounds like a broadcast thing, since the VPN lets me through....
[22:25] <ChrisNZ> alhtough i can access the plain shares without usernames and passwords without a challenge
[22:26] <ChrisNZ> not private message, i mean, "directed message to a user"
[22:27] <ChrisNZ> i was thinking of paying caconical to help lol
[22:30] <hads> Sounds like a reasonable idea.
[22:32] <ChrisNZ> Thumper, how do i best contact them in NZ?
[22:32] <thumper> um... contact the help desk?
[22:32] <thumper> it runs 24/5
[22:37] <ChrisNZ> do you mean using this page, http://www.ubuntu.com/business/services/contact
[22:38] <thumper> ChrisNZ: never tried, as I poke them internally :)
[22:39] <ChrisNZ> lol do they have a number?
[22:40] <thumper> ChrisNZ: try the links off http://canonical.com
[22:42] <ChrisNZ> Okeis guys, and girls??? thanks! lol later Thumps
[22:51] <chilts> morning
[22:51]  * chilts forgot
[22:56] <ibeardslee> hads: can't tell, but is that a wobbly square on the key between the Ctrl and Alt ?
[22:59] <ibeardslee> http://liliputing.com/2012/08/great-wall-u310-packs-an-ubuntu-desktop-pc-into-a-keyboard.html  That one certainly is
[23:24] <hads> Heh, looks like it.
[23:25] <hads> What perplexes me is all these phones coming out with 1280x720 IPS screens and laptops seem to be stuck with crappy TN panels of around the same resolution.
[23:26] <Atamira> if a laptop could be used as a phone, id get it instead of a phone


[00:50] <CIA-62> ubiquity: cjwatson * r5405 trunk/d-i/sources.list: precise -> quantal
[10:13] <jo-erlend> I have a bootable usb on my keyring. It uses persistence. If I store things on it, then those won't be copied if I install from it, right?
[10:16] <CIA-62> localechooser: cjwatson * r174 ubuntu/ (16 files in 3 dirs): merge from Debian 2.40
[10:17] <cjwatson> right, I don't believe we copy that
[10:18] <CIA-62> localechooser: cjwatson * r175 ubuntu/debian/changelog: releasing version 2.40ubuntu1
[10:28] <CIA-62> ubiquity: cjwatson * r5406 trunk/ (debian/real-po/my.po po/my.po debian/changelog): Add Burmese translations.
[10:34] <CIA-62> ubiquity: cjwatson * r5407 trunk/debian/ (3 files):
[10:34] <CIA-62> ubiquity: Remove obsolete uxlaunch handling, since it's no longer used and has
[10:34] <CIA-62> ubiquity: been removed from the archive.
[11:17] <CIA-62> debian-installer-utils: cjwatson * r1153 ubuntu/debian/changelog: merge from Debian 1.89
[11:18] <CIA-62> debian-installer-utils: cjwatson * r1154 ubuntu/debian/changelog: releasing version 1.89ubuntu1
[11:20] <CIA-62> cdrom-detect: cjwatson * r912 ubuntu/debian/ (71 files in 2 dirs): merge from Debian 1.40
[11:21] <CIA-62> cdrom-detect: cjwatson * r913 ubuntu/debian/po/kn.po: msgmerge
[11:22] <CIA-62> cdrom-detect: cjwatson * r914 ubuntu/debian/ (cdrom-detect.templates changelog): Set cdrom/suite default to quantal; drop maverick.
[11:23] <CIA-62> cdrom-detect: cjwatson * r915 ubuntu/debian/changelog: releasing version 1.40ubuntu1
[11:25] <CIA-62> iso-scan: cjwatson * r557 ubuntu/debian/ (changelog iso-scan.templates): Add quantal to cdrom/suite Choices; drop maverick.
[11:26] <CIA-62> iso-scan: cjwatson * r558 ubuntu/debian/changelog: releasing version 1.38ubuntu2
[11:28] <CIA-62> choose-mirror: cjwatson * r1178 ubuntu/ (3 files in 2 dirs): Switch to quantal by default.
[11:29] <CIA-62> choose-mirror: cjwatson * r1179 ubuntu/debian/changelog: releasing version 2.39ubuntu5
[12:04] <CIA-62> clock-setup: cjwatson * r229 ubuntu/ (10 files in 3 dirs): merge from Debian 0.110
[12:05] <CIA-62> clock-setup: cjwatson * r230 ubuntu/debian/changelog: releasing version 0.110ubuntu1
[12:07] <CIA-62> debian-installer: cjwatson * r1685 ubuntu/ (6 files in 2 dirs): Move to 3.4.0-1 kernels.
[12:38] <CIA-62> ubiquity: cjwatson * r5408 trunk/ (7 files in 2 dirs): Use test.support rather than test.test_support if available.
[13:06] <stgraber> cjwatson: I'm looking at merging os-prober and I see that the last time around you did a proper bzr merge into lp:~ubuntu-core-dev/os-prober/ubuntu/ but I can't figure out what parent branch you used for that
[13:08] <stgraber> cjwatson: oh, looks like that could be lp:os-prober
[13:08] <stgraber> yep, that was it. Sorry, for some reason I didn't think of looking at the most obvious place...
[13:10] <cjwatson> that's the one
[13:16] <CIA-62> os-prober: stgraber * r343 ubuntu/ (5 files in 3 dirs): Merge 1.52 from Debian
[13:19] <CIA-62> os-prober: stgraber * r344 ubuntu/debian/changelog: releasing version 1.52ubuntu1
[13:21] <stgraber> ok, so first easy merge of the day, done. Now to continue with the much funnier ifupdown one ;)
[13:24] <CIA-62> ubiquity: cjwatson * r5409 trunk/tests/test_osextras.py: Another new-style except.
[13:25] <cjwatson> At some point I may get the tests to stop raising SyntaxError under Python 3 :-P
[13:35] <cjwatson> Hmm, no python3-pyicu
[13:39] <cjwatson> Ah, but this is apparently a trivial packaging matter now


[00:01] -queuebot:#ubuntu-release- New binary: haskell-quickcheck-classes [armhf] (noble-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[00:02] -queuebot:#ubuntu-release- New binary: haskell-deriving-aeson [armhf] (noble-proposed/universe) [0.2.9-1] (no packageset)
[00:08] -queuebot:#ubuntu-release- New binary: nextpnr [s390x] (noble-proposed/universe) [0.6-3] (no packageset)
[00:19] -queuebot:#ubuntu-release- New binary: haskell-hslua-list [s390x] (noble-proposed/universe) [1.1.1-2] (no packageset)
[00:25] -queuebot:#ubuntu-release- New binary: tds-fdw [riscv64] (noble-proposed/universe) [2.0.3-3] (no packageset)
[00:51] -queuebot:#ubuntu-release- New binary: nextpnr [arm64] (noble-proposed/universe) [0.6-3] (no packageset)
[01:38] -queuebot:#ubuntu-release- New binary: geany-plugins [riscv64] (noble-proposed/universe) [2.0-2] (no packageset)
[02:10] -queuebot:#ubuntu-release- New binary: haskell-hslua-list [riscv64] (noble-proposed/universe) [1.1.1-2] (no packageset)
[02:51] -queuebot:#ubuntu-release- New binary: haskell-deriving-aeson [riscv64] (noble-proposed/universe) [0.2.9-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: haskell-quickcheck-classes [riscv64] (noble-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[06:57] -queuebot:#ubuntu-release- New binary: nextpnr [riscv64] (noble-proposed/universe) [0.6-3] (no packageset)
[09:51] -queuebot:#ubuntu-release- New: accepted geany-plugins [amd64] (noble-proposed) [2.0-2]
[09:51] -queuebot:#ubuntu-release- New: accepted geany-plugins [armhf] (noble-proposed) [2.0-2]
[09:51] -queuebot:#ubuntu-release- New: accepted geany-plugins [riscv64] (noble-proposed) [2.0-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-deriving-aeson [amd64] (noble-proposed) [0.2.9-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-deriving-aeson [armhf] (noble-proposed) [0.2.9-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-deriving-aeson [riscv64] (noble-proposed) [0.2.9-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-hslua-list [amd64] (noble-proposed) [1.1.1-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-hslua-list [armhf] (noble-proposed) [1.1.1-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-hslua-list [s390x] (noble-proposed) [1.1.1-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-quickcheck-classes [arm64] (noble-proposed) [<IP_ADDRESS>-2]
[09:51] -queuebot:#ubuntu-release- New: accepted geany-plugins [arm64] (noble-proposed) [2.0-2]
[09:51] -queuebot:#ubuntu-release- New: accepted geany-plugins [s390x] (noble-proposed) [2.0-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-deriving-aeson [ppc64el] (noble-proposed) [0.2.9-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-hslua-list [arm64] (noble-proposed) [1.1.1-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-quickcheck-classes [amd64] (noble-proposed) [<IP_ADDRESS>-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-quickcheck-classes [ppc64el] (noble-proposed) [<IP_ADDRESS>-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-quickcheck-classes [s390x] (noble-proposed) [<IP_ADDRESS>-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-text-builder-dev [arm64] (noble-proposed) [<IP_ADDRESS>-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-text-builder-dev [ppc64el] (noble-proposed) [<IP_ADDRESS>-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-text-builder-dev [s390x] (noble-proposed) [<IP_ADDRESS>-1]
[09:51] -queuebot:#ubuntu-release- New: accepted geany-plugins [ppc64el] (noble-proposed) [2.0-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-deriving-aeson [s390x] (noble-proposed) [0.2.9-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-quickcheck-classes [armhf] (noble-proposed) [<IP_ADDRESS>-2]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-text-builder-dev [amd64] (noble-proposed) [<IP_ADDRESS>-1]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-text-builder-dev [riscv64] (noble-proposed) [<IP_ADDRESS>-1]
[09:51] -queuebot:#ubuntu-release- New: accepted nextpnr [arm64] (noble-proposed) [0.6-3]
[09:51] -queuebot:#ubuntu-release- New: accepted nextpnr [riscv64] (noble-proposed) [0.6-3]
[09:51] -queuebot:#ubuntu-release- New: accepted tds-fdw [amd64] (noble-proposed) [2.0.3-3]
[09:51] -queuebot:#ubuntu-release- New: accepted tds-fdw [armhf] (noble-proposed) [2.0.3-3]
[09:51] -queuebot:#ubuntu-release- New: accepted tds-fdw [riscv64] (noble-proposed) [2.0.3-3]
[09:51] -queuebot:#ubuntu-release- New: accepted haskell-deriving-aeson [arm64] (noble-proposed) [0.2.9-1]
[09:52] -queuebot:#ubuntu-release- New: accepted haskell-quickcheck-classes [riscv64] (noble-proposed) [<IP_ADDRESS>-2]
[09:52] -queuebot:#ubuntu-release- New: accepted nextpnr [amd64] (noble-proposed) [0.6-3]
[09:52] -queuebot:#ubuntu-release- New: accepted nextpnr [s390x] (noble-proposed) [0.6-3]
[09:52] -queuebot:#ubuntu-release- New: accepted tds-fdw [ppc64el] (noble-proposed) [2.0.3-3]
[09:52] -queuebot:#ubuntu-release- New: accepted haskell-hslua-list [riscv64] (noble-proposed) [1.1.1-2]
[09:52] -queuebot:#ubuntu-release- New: accepted nextpnr [ppc64el] (noble-proposed) [0.6-3]
[09:52] -queuebot:#ubuntu-release- New: accepted tds-fdw [s390x] (noble-proposed) [2.0.3-3]
[09:52] -queuebot:#ubuntu-release- New: accepted haskell-text-builder-dev [armhf] (noble-proposed) [<IP_ADDRESS>-1]
[09:52] -queuebot:#ubuntu-release- New: accepted tds-fdw [arm64] (noble-proposed) [2.0.3-3]
[10:27] <doko> so apparently there are currently no armhf autopkg testers, the armhf queues show empty, and the last status update on discourse is from August
[10:27] <doko> anyway, traveling now ...
[10:40] -queuebot:#ubuntu-release- New binary: haskell-text-builder [amd64] (noble-proposed/universe) [0.6.7-1] (no packageset)
[10:40] -queuebot:#ubuntu-release- New binary: haskell-text-builder [s390x] (noble-proposed/universe) [0.6.7-1] (no packageset)
[10:40] -queuebot:#ubuntu-release- New binary: haskell-text-builder [ppc64el] (noble-proposed/universe) [0.6.7-1] (no packageset)
[10:41] -queuebot:#ubuntu-release- New binary: haskell-text-builder [arm64] (noble-proposed/universe) [0.6.7-1] (no packageset)
[10:45] -queuebot:#ubuntu-release- New binary: haskell-bitvec [amd64] (noble-proposed/universe) [<IP_ADDRESS>-3build1] (no packageset)
[10:46] -queuebot:#ubuntu-release- New binary: haskell-arithmoi [amd64] (noble-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[10:47] -queuebot:#ubuntu-release- New binary: haskell-bitvec [arm64] (noble-proposed/universe) [<IP_ADDRESS>-3build1] (no packageset)
[10:47] -queuebot:#ubuntu-release- New binary: haskell-bitvec [ppc64el] (noble-proposed/universe) [<IP_ADDRESS>-3build1] (no packageset)
[10:49] -queuebot:#ubuntu-release- New binary: haskell-text-builder [armhf] (noble-proposed/universe) [0.6.7-1] (no packageset)
[10:54] -queuebot:#ubuntu-release- New binary: haskell-arithmoi [ppc64el] (noble-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[10:54] -queuebot:#ubuntu-release- New binary: haskell-bitvec [s390x] (noble-proposed/universe) [<IP_ADDRESS>-3build1] (no packageset)
[11:01] -queuebot:#ubuntu-release- New binary: haskell-arithmoi [arm64] (noble-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[12:20] -queuebot:#ubuntu-release- New binary: haskell-text-builder [riscv64] (noble-proposed/universe) [0.6.7-1] (no packageset)
[12:26] -queuebot:#ubuntu-release- New binary: haskell-bitvec [armhf] (noble-proposed/universe) [<IP_ADDRESS>-3build1] (no packageset)
[12:50] -queuebot:#ubuntu-release- New binary: haskell-bitvec [riscv64] (noble-proposed/universe) [<IP_ADDRESS>-3build1] (no packageset)
[13:15] -queuebot:#ubuntu-release- New binary: haskell-arithmoi [riscv64] (noble-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: sqlcipher [amd64] (noble-proposed/universe) [4.5.5-3] (kubuntu)
[17:14] -queuebot:#ubuntu-release- New binary: pbbam [amd64] (noble-proposed/universe) [2.4.0+dfsg-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: sqlcipher [ppc64el] (noble-proposed/universe) [4.5.5-3] (kubuntu)
[17:17] -queuebot:#ubuntu-release- New binary: pbbam [ppc64el] (noble-proposed/universe) [2.4.0+dfsg-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: sqlcipher [s390x] (noble-proposed/universe) [4.5.5-3] (kubuntu)
[17:20] -queuebot:#ubuntu-release- New binary: sqlcipher [armhf] (noble-proposed/universe) [4.5.5-3] (kubuntu)
[17:27] -queuebot:#ubuntu-release- New binary: sqlcipher [arm64] (noble-proposed/universe) [4.5.5-3] (kubuntu)
[17:30] -queuebot:#ubuntu-release- New binary: pbbam [arm64] (noble-proposed/universe) [2.4.0+dfsg-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: adios2 [amd64] (noble-proposed/universe) [2.8.2+dfsg1-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: adios2 [s390x] (noble-proposed/universe) [2.8.2+dfsg1-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: adios2 [ppc64el] (noble-proposed/universe) [2.8.2+dfsg1-1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: sqlcipher [riscv64] (noble-proposed/universe) [4.5.5-3] (kubuntu)
[18:23] -queuebot:#ubuntu-release- New binary: adios2 [arm64] (noble-proposed/universe) [2.8.2+dfsg1-1] (no packageset)
[18:39] -queuebot:#ubuntu-release- New binary: pbbam [riscv64] (noble-proposed/universe) [2.4.0+dfsg-1] (no packageset)
[22:29] -queuebot:#ubuntu-release- New binary: adios2 [riscv64] (noble-proposed/universe) [2.8.2+dfsg1-1] (no packageset)
[23:10] -queuebot:#ubuntu-release- New binary: env-assert [amd64] (noble-proposed/universe) [0.008-2] (no packageset)
[23:10] -queuebot:#ubuntu-release- New binary: referencing [amd64] (noble-proposed/universe) [0.30.2-2] (no packageset)
[23:10] -queuebot:#ubuntu-release- New binary: rust-rlp-derive [amd64] (noble-proposed/universe) [0.1.0-1] (no packageset)
[23:10] -queuebot:#ubuntu-release- New binary: jupyterlab [amd64] (noble-proposed/universe) [4.0.8+ds1-1] (no packageset)
[23:10] -queuebot:#ubuntu-release- New binary: rust-embedded-io [amd64] (noble-proposed/universe) [0.6.1-1] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: golang-github-johanneskaufmann-html-to-markdown [amd64] (noble-proposed/universe) [1.4.1-1] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: python-ssdpy [amd64] (noble-proposed/universe) [0.4.1-1] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: jupyter-events [amd64] (noble-proposed/universe) [0.9.0-1] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: rust-embedded-io [ppc64el] (noble-proposed/universe) [0.6.1-1] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: ticketbooth [amd64] (noble-proposed/universe) [1.0.1-1] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: rust-rlp-derive [ppc64el] (noble-proposed/universe) [0.1.0-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: python-gradientmodel [amd64] (noble-proposed/universe) [0.0.2-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: rust-embedded-io [s390x] (noble-proposed/universe) [0.6.1-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: rust-embedded-io [armhf] (noble-proposed/universe) [0.6.1-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: rust-rlp-derive [s390x] (noble-proposed/universe) [0.1.0-1] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: rust-embedded-io [arm64] (noble-proposed/universe) [0.6.1-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: rust-rlp-derive [armhf] (noble-proposed/universe) [0.1.0-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: gnome-video-trimmer [amd64] (noble-proposed/universe) [0.8.2-2] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: rust-rlp-derive [arm64] (noble-proposed/universe) [0.1.0-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: gnome-video-trimmer [armhf] (noble-proposed/universe) [0.8.2-2] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: gnome-video-trimmer [ppc64el] (noble-proposed/universe) [0.8.2-2] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: gnome-video-trimmer [s390x] (noble-proposed/universe) [0.8.2-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: bespokesynth [amd64] (noble-proposed/universe) [1.2.1+dfsg-2] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: gnome-video-trimmer [arm64] (noble-proposed/universe) [0.8.2-2] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-rlp-derive [riscv64] (noble-proposed/universe) [0.1.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-embedded-io [riscv64] (noble-proposed/universe) [0.6.1-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: bespokesynth [ppc64el] (noble-proposed/universe) [1.2.1+dfsg-2] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: bespokesynth [s390x] (noble-proposed/universe) [1.2.1+dfsg-2] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: bespokesynth [armhf] (noble-proposed/universe) [1.2.1+dfsg-2] (no packageset)