[07:44] <thorwil> humphreybc: thanks!
[08:22] <humphreybc> thorwil: no probs, looks great
[10:01] <humphreybc> how's the manual going
[10:01] <humphreybc> >
[10:01] <humphreybc> ?*
[10:01] <humphreybc> fail right there
[10:01]  * vish wonders why the logo cant be used as the icon too :)
[10:02] <vish> thorwil: scaling issues or .. ?
[10:02]  * vish likes the logo more than the icon btw ..;)
[10:03] <humphreybc> I have to agree with vish on that one too
[10:04] <vish> thorwil: one issue with the 256 px icon , it _will_ be scaled down , thats why most of the 256px icons are tested how they look at 64px too
[10:04] <thorwil> vish: partly scaling issues, yet. the icon concentrates on providing a hint what quickshot is about, while for the logo, looking good comes first
[10:07] <thorwil> vish: scaling it as bitmap is a dumb idea. should i made lines in the 256 px version wide enough so they will be 1px at 64px? ridiculous
[10:08] <vish> thorwil: yeah , thats why the 256 px icons are ridiculous :) , but thats how they work.. they scale down 4 times , hence lines are usually 4px thick
[10:08] <vish> thorwil: the 256 px are never used anywhere, its given in the readme though , not my idea :)
[10:09] <vish> thorwil: also, i dont know if others would know by looking at the icon as to it function.. it seems to relate to us since we know what it does.. i'd still prefer the logo one and try to scale it.. but your call .. ;)
[10:21] <thorwil> vish: that's not quite what i get out the README. already found 1 and 2 px wide lines and icons with nothing you can call an outline at all
[10:22] <vish> thorwil: its everything, not the lines alone , everything needs to be in multiples of 4 , the whole icon size , the margins, etc..
[10:25] <thorwil> vish: what's the reason to not work at 64px, then?
[10:26] <thorwil> wait, gotta ask them
[10:26] <vish> thorwil: beats me.. i still wonder that.. still not sure why/where we use 256 px icons..
[11:20] <nisshh> popey: did you manage to compile the manual in the end?
[11:22] <popey> yes!
[11:22] <popey> I CAN HAZ PDF!
[11:22] <nisshh> haha
[11:22] <nisshh> popey: so, what do you think so far?
[11:23] <popey> not had much chance to read it yet
[11:23] <nisshh> also, be aware that i havent gotten all the chapters in the branch yet
[11:23] <nisshh> right
[11:24] <nisshh> popey: any idea what you want to do yet? (edit/grammar check/consistency checking)
[11:25] <popey> well, the initial idea was grammar, consistency check, test
[11:25] <nisshh> right
[11:25] <nisshh> still want to do that or have you changed your mind?
[11:27] <popey> yeah, just not had a chance to look at it since I compiled it last night
[11:27]  * popey is at work
[11:28] <nisshh> right
[11:28] <nisshh> thought you might be
[15:46] <popey> http://www.ubuntugeek.com/ --> link on right to tradepub  for ubuntu manual download
[15:48] <nisshh> popey: i saw that the other day, they ripped it off our site
[15:48] <nisshh> bloody amateurs
[15:48] <popey> http://ubuntugeek.tradepub.com/c/pubRD.mpl/?pc=w_ubun01
[15:48] <nisshh> yea
[15:48] <popey> he's a uk person
[15:49] <nisshh> yea
[15:49] <nisshh> popey: you home from work now?
[15:50] <popey> no
[15:50] <popey> i have an appointment with a pint of beer directly after work
[15:50] <nisshh> ah ok
[15:50] <nisshh> hehe
[15:50] <popey> will ping you when I'm back home
[15:50] <nisshh> sure
[15:51] <nisshh> popey: just so i get the time difference, your in the UK correnct?
[15:51] <nisshh> correct*
[15:51] <popey> ya
[15:51] <nisshh> ok
[15:52] <nisshh> popey: i just tried to download the manual on tradepub there, and its asking me for all my details, WTF!?
[15:52] <popey> yeah
[15:52] <popey> its an affiliate site
[15:52] <popey> he gets a kickback for each download
[15:52] <nisshh> a kickback?
[15:52] <popey> its not the first time he's done that
[15:52] <popey> money
[15:52] <nisshh> ah
[15:52] <nisshh> what a douch
[15:52] <popey> just plain rude given how much time you lot put in
[15:52] <nisshh> yea
[15:53] <nisshh> i mean, itd be ok if he linked to the site
[15:53] <nisshh> but that is rediculous!
[15:53] <nisshh> popey: does humphreybc know?
[15:55] <popey> i suspect so
[15:55] <popey> it was tweeted months ago
[15:55] <popey> Chris Pirillo started it iirc
[15:55] <popey> and that ubuntu-geek guy just picks up links and posts them with zero thought
[15:55] <nisshh> yea
[15:55] <nisshh> i wanna punch that guy in the face
[15:58] <popey> heh
[15:58] <nisshh> :)
[15:58] <popey> you could send him a polite email pointing out the error of his ways
[15:59] <nisshh> i suspect that would just warrant an agry reply about him needing the money
[16:36] <flan> nisshh, I think I just had an evil idea.
[16:36] <flan> Deliciously so, of course.
[16:37] <nisshh> flan: hmmm?
[16:38] <nisshh> flan: whats your idea?
[16:38] <flan> Present Quickshot in AppDevWeek as a "howto", clone the live UMP data-set, and try to get participants to capture real data for merging back into the core tree.
[16:38] <flan> (Cloned so I can give them admin access to the demo server, for full immersion)
[16:38] <nisshh> flan: you mean use the session in order to get people to take the manual screenshots?
[16:38] <flan> Yes.
[16:39] <flan> Under the pretense of teaching them how to use it for their own projects./
[16:39] <nisshh> flan: holy shit! your a freaking genious! :)
[16:39] <nisshh> flan: so, do you need my help?
[16:39] <flan> If you're available, I wouldn't mind having someone to keep me from getting too technical.
[16:39] <flan> But I think I can manage.
[16:40] <nisshh> ok
[16:40] <nisshh> flan: if your sure, make sure you schedule a place, there arent many left
[16:40] <nisshh> sorry, not a place, a time
[16:40] <flan> I took the one right after "writing documentation with Mallard"
[16:40] <nisshh> ah cool
[16:40] <flan> It seemed appropriate.
[16:40] <flan> More likely to have a similar crowd.
[16:41] <flan> Er... interested crowd*
[16:41] <nisshh> hehe
[16:42] <nisshh> flan: ill make sure i hang around in the channel when your session is on
[16:42] <nisshh> just in case
[16:42] <flan> Thanks.
[16:42] <nisshh> :)
[16:57] <flan> Is it wrong to have a playlist of nothing but remixes of FFV's Battle on the Big Bridge?
[16:58] <nisshh> yes
[16:58] <flan> Aww. :(
[16:59] <nisshh> lol
[16:59] <nisshh> flan: you need some better music
[16:59] <flan> Says you.
[16:59] <nisshh> flan: my playlist is over 3800 items
[16:59] <flan> Small.
[17:00] <flan> I didn't meant to say this was all I have. Just that it's all I'm listening to at the moment.
[20:05] <flan> No bugs yet, jenkins?
[20:06] <jenkins> I have just started on it whilst i wait for latex to download. can you assign the icon to the windows and the error dialog needs to comform to gnome hig where would i edit it? I can't see it in glade
[20:06] <flan> The dialogues aren't in Glade.
[20:06] <flan> What do you need to change?
[20:07] <flan> Everything's created dynamically in gui/dialogue.py
[20:07] <flan> As for the icons, yes, just tell me where the file is, relative to data/ui/, and I'll get that working today.
[20:08] <jenkins> there should be a 12 px border around the main box, and 12px between each of the elements
[20:08] <ChrisWoollard> evening jenkins
[20:08] <flan> If thorwil gave us a .ico for the website (or a suitable alternative image), put it in server/quickshot/public and add an appropriate header to quickshot/templates/common/header.mako
[20:09] <flan> Remove the old favicon.ico, if it becomes redundant as a result.
[20:09] <flan> Oh. Yeah, just find out what to call or pass to the box in the GTK docs (pygtk + box) and set that in dialogue.py.
[20:10] <flan> You should only have to change it in the private function at the top.
[20:11] <jenkins> all the art work is in  https://code.launchpad.net/~t-w-/+junk/quickshot_art  I have just pussed the icon into the data/ui folder . i tried assigning it in glade but it did not work
[20:11] <jenkins> hey ChrisWoollard
[20:13] <ChrisWoollard> How is life treating you
[20:14] <jenkins> I am good thanks, your self
[20:14] <ChrisWoollard> I am ok. I am getting a bit fed up with writting this job application form. + my meeting is later
[20:17] <jenkins> o yea I will pop in, good luck . Please ping me before it starts
[20:17] <ChrisWoollard> np
[20:17] <ChrisWoollard> will do
[20:18] <flan> It's not gonna work if you assign it in Glade. Not yet, anyway.
[20:18] <flan> With the exception of the windows that are loaded as-is, like graphics_confirm.
[20:18] <flan> Assign everything in Glade, though.
[20:18] <flan> I'll just copy the icon from the parent to the internal window model.
[20:18] <jenkins> ok I will go through assiging in glade
[20:19] <flan> Or... maybe I can just let you do that.
[20:19] <flan> It'll be one line.
[20:19] <flan> Gimme a moment to write it.
[20:20] <flan> In base.py, where other attributes are being copied from content.parent, add the following: "self.set_icon(content.parent.get_icon())"
[20:20] <flan> That should cause everything to get pulled from Glade.
[20:23] <jenkins> ok thanks I will give it a tyr
[20:32] <jenkins> flan: are you sure you mean base.py? I added it to project_selection.py with all the other content parent stuff and that worked
[20:32] <flan> I'm sure I mean base.py.
[20:32] <flan> Oh, wait.
[20:32] <flan> No,.
[20:32] <flan> You're right.
[20:32] <flan> I meant every child of base.py.
[20:33]  * flan braindead.
[20:33] <jenkins> I will copy that into every file
[20:33] <flan> Every file that has a class that inherits from base.BaseWindow, not gtk.Window.
[20:33] <jenkins> ok will do
[20:33] <flan> I'm sure you'll notice the difference ins tructure, though
[20:33] <flan> They look nothing alike.
[20:41] <jenkins> http://tinypic.com/r/j0lkiu/7 quickshot with the new logo and icon!
[20:50] <flan> It almost looks like a real program!
[20:50] <jenkins> lol
[20:50] <flan> So, do you want to handle changing the server's icon, too, or should I do that?
[20:51] <flan> Also, thorwil, do you have a mini-logo I could use for the server's header area? Alternatively, any objection to me using the same reference material, but moving the text to teh right of the icon and using that?
[20:59] <ChrisWoollard> ping jenkins
[20:59] <ChrisWoollard> meeting started
[20:59] <jenkins> ready to watch ChrisWoollard :)
[21:03] <ChrisWoollard> thx
[21:04] <jenkins> everyone join #ubuntu-meeting and support ChrisWoollard
[21:04] <ChrisWoollard> I am glad i am not first. Then i can watch how it is done
[21:05] <jenkins> i agree
[21:16] <thorwil> flan: rough something in so i can see the size you desire and ask me again tomorrow
[21:16] <thorwil> flan: didn't make an ico so far. really hate the thought of trying to bring the logo down to 16px. using the icon would be easy, though
[21:17] <thorwil> flan: cool to see you use mako. now i have to run, cya!
[21:18] <ChrisWoollard> this may take a while.
[21:18] <jenkins> I was thinking the same
[21:20] <jenkins> they really quized ben when he had his but this appears to be easier. ben was applying for a different area of the world though
[21:22] <ChrisWoollard> nissh had his in the same region as be
[21:22] <ChrisWoollard> n
[21:22] <ChrisWoollard> he had a hard time too.
[21:22] <jenkins> I think they were really tough
[21:22] <ChrisWoollard> I also wonder if it makes a difference that there are a lot of people to get through
[21:23]  * jenkins has written his i like chris text up in gedit
[21:25] <ChrisWoollard> thanks
[21:25] <jenkins> I was thinking that a lot of people may make them quicker
[21:27] <ChrisWoollard> you should have done yours too.
[21:29] <jenkins> I should have done :(
[21:29] <jenkins> although at this rate i would have fallen asleep by the time it reached me
[21:31] <ChrisWoollard> i was hoping that half the people would have forgotton to turn up
[21:32] <jenkins> that does usually happen
[21:57] <ChrisWoollard> I am up next.
[21:58] <jenkins> cool
[22:04] <ChrisWoollard> Yay.
[22:04] <ChrisWoollard> I am now an Ubuntu Member
[22:05] <jenkins> nice one :) they so want to get them completed now
[22:05] <ChrisWoollard> I noticed.
[22:05] <ChrisWoollard> They did like my testimonials :)
[22:12] <dutchie> anybody interested in helping the a11y team come up with personas feel free to join #ubuntu-accessibility now
[22:53] <dutchie> a11y discussion finished, see http://pad.ubuntu-uk.org/WkO4TZbvWt for the fruits of our labour
[23:29] <daker> ChrisWoollard, congrats!!


[11:01] <bac> morning
[11:04] <frankban> hi bac
[12:09] <gary_poster> bac benji gmb frankban call in yellowsquad asap
[12:47] <gmb> haha. Precipitous exiting of hangout fail
[12:53] <gary_poster> gmb, benji call is open fwiw
[13:30] <frankban> who wants to be the victim? https://code.launchpad.net/~frankban/lpsetup/complete-tests/+merge/115985 To the victim: I am sorry.
[14:03] <benji> gmb and gary_poster: I'll be on the follow-up in a couple of minutes.
[14:03] <gary_poster> ok
[14:36] <frankban> thanks bac!
[15:14] <frankban> bac: branch updated, do you want to take another look or can I try to land it?
[15:14] <bac> frankban: just approve it
[15:14] <frankban> ok
[15:22]  * benji goes away to sign papers in front of a notary.
[16:45] <gmb> gary_poster: around?
[16:46] <gary_poster> gmb, would you be surprised to hear that I'm on an interview?
[16:46] <gmb> Ah, of course.
[16:46] <gmb> nm :)
[18:48] <bac> hi gmb, if you are around or show back up i have a very quick question
[19:47] <bac> hi benji
[19:47] <benji> hey bac
[19:48] <bac> benji: so i haven't used juju with lxc in a while.  i've deployed the ubuntu charm but cannot ssh to it.  doesn't like my ssh keys.  i wonder if there is a step i've forgotten?
[19:48] <benji> are you using a command like "juju ssh 1"?
[19:49] <bac> well, on lxc 'juju status' shows 0 and ubuntu/0.  so i am trying 'juju ssh ubuntu/0'
[19:49] <bac> 1 does not exist
[19:50] <benji> bac: is this in EC2 or LXC?
[19:50] <bac> l-x-c
[19:50] <bac> brb
[19:52] <benji> heh, sorry, I missed that part; I don't know why it wouldn't work like that.  Let me try it real quick.
[19:55] <bac> and i re-discovered there is a problem with libvirt in precise on vmware.  makes me curious what gmb is using.
[20:01] <benji> bac: using LXC on my laptop (no VMs or anthing) I can't get it to work the way I would expect, i.e., after deploying the ubuntu charm there is still only one machine (0) and I can't "juju ssh 0" into it
[20:01] <bac> benji: did you try ubuntu/0?
[20:02] <bac> what does status say?
[20:02] <benji> bac: ooh! "ubuntu/0" worked!
[20:02] <bac> no publickey complaints?
[20:03] <benji> juju status: http://paste.ubuntu.com/1102365
[20:03] <benji> nope, it worked fine
[20:06] <bac> benji: if you juju ssh -v ...  what key does it show using?
[20:06] <benji> bac: debug1: Authentication succeeded (publickey).
[20:07] <bac> but which was offered before the success?
[20:10] <benji> bac: here's the whole thing: http://paste.ubuntu.com/1102381
[20:11] <bac> benji: ok so it liked your /home/benji/.ssh/id_rsa
[20:11] <bac> my id_rsa gets offered and rejected
[20:15] <benji> hmm, I wonder if it isn't being picked up correctly when the container is being built
[20:22] <bac> benji: perhaps.  i'm fuzzy on how that is supposed to work
[20:23] <bac> does it use ssh-agent?
[20:23] <benji> me too
[20:23] <benji> I don't know.  I would strace it and/or read the code.
[20:24] <benji> you could also make sure there isn't anything funny going on with your keys.  I seem to remember someone recently having problems with their keys because they were odd in some way.  Still technically correct, but something had trouble parsing them.
[20:26] <bac> benji: yeah, my keys had been munged by our add_header() mess.  i cleaned that all up
[20:26] <benji> ahh
[20:27] <bac> still broken though
[20:38] <bac> benji: this actually fixed my problem : http://www.youtube.com/watch?v=p85xwZ_OLX0
[20:38] <bac> hate that
[20:46] <benji> :)


[07:32] <nibbon_> o/
[07:32] <nibbon_> can I safely delete and recreate /etc/machine-id && /var/lib/dbus/machine-id?
[13:36] <ahasenack> enr0n: around?
[13:36] <ahasenack> enr0n: about systemd multicastdns
[13:37]  * ahasenack checks tz
[13:37] <ahasenack> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038894
[13:37] -ubottu:#ubuntu-devel- Launchpad bug 2038894 in systemd (Ubuntu Mantic) "Ubuntu 23.10 cloud images unexpected UDP listening port  5353" [High, New]
[13:39] <enr0n> ahasenack: yeah I'm around
[13:40] <ahasenack> enr0n: noble is open now, could you upload a 253.5-1ubuntu7 to it? And the mantic version needs adjusting, otherwise it won't upgrade to noble
[13:40] <ahasenack> could you reupload mantic as 253.5-1ubuntu6.1?
[13:40] <ahasenack> then it's all good
[13:40] <ahasenack> wdyt?
[13:41] <enr0n> Wouldn't just syncing from mantic-proposed (if accepted) be sufficient? That was my original plan.
[13:41] <enr0n> If not, I can certainly do what you suggest
[13:42] <ahasenack> I think that was the way out when noble wasn't open yet, now I think it's best to adjust the version.
[13:43] <enr0n> ahasenack: ack, will do that now. Thanks!
[13:45] <adrien> rbasak: yeah, the "modified files" thing is definietely unrelated to git-ubuntu but they were the last straw yesterday and made me prefer going to bed :P  (I need to get back to it now though :) )
[14:13] <ahasenack> enr0n: I see the mantic upload, thx, on it
[14:13] <enr0n> ahasenack: great, thanks!
[14:49] <adrien> I gave up and cloned the repository in a new directory; no issue (but I need to dig deeper into that directory thing)
[19:15] <rbasak> lvoytek, ahasenack: on bug 2004676, it sounds like Andreas was expecting a PKCS #11 based test to ensure that the engine support doesn't regress, but I don't see any further plans on that in the bug. For example, was someone planning on verifying this first, or adding it to the Test Plan? Are you expecting something different?
[19:15] -ubottu:#ubuntu-devel- Bug 2004676 in openvpn (Ubuntu Jammy) "MRE Updates 2.5.9 / 2.4.12" [Undecided, In Progress] https://launchpad.net/bugs/2004676
[19:17] <ahasenack> rbasak: I'll get back to you on that later, finishing a score card now, and we have the sru team meeting later
[19:18] <ahasenack> I recall doing a pkcs#11 based test run, but it was a bit indirect, not using the engine directly. I couldn't find a way to use the engine directly, it was always through another module outside of openvpn
[19:25] <rbasak> I don't mean to imply that this must be done - it's just that this is where the conversation in the bug seemed to be leading, and now I'm unsure of the plan.
[19:26] <ahasenack> rbasak: I understand. I want to get the context again
[19:26] <ahasenack> maybe I was meant to provide that test and forgot it
[19:26] <ahasenack> or it was too difficult and I was meant to comment to that regard
[19:26] <ahasenack> I'll add a comment to the bug after I get this context again
[19:26] <ahasenack> thanks for checking
[21:11] <ahasenack> :q
[21:51] <ahasenack> philroche: hi, the livecd-rootfs rejects, were basically about the .changes file, there were multiple uploads in the unapproved queue. Also the SRU template was missing in two of the referenced bugs
[21:51] <ahasenack> we can talk tomorrow, I'll take a look in my morning again, since I couldn't spend much time on SRUs in my shift today due to meetings
[22:01] <sergiodj> @pilot in
[22:03] <sergiodj> @pilot out
[22:03] <sergiodj> I'll do my shift tomorrow, after Andreas'
[23:58] <jbicha> @pilot out


[20:29] <thomi> hi barry, have you got a moment?
[20:29] <barry> thomi: hi!  sure
[20:29] <thomi> I'm trying to package the current version of selenium from pypi into a debian package, and it's a real mess
[20:30] <thomi> debian/watch doesn't seem to work (but looks cvorrect to me), patches in d/patches don't apply to new version, and new version contains binary .so files, that I'm not sure what to do with
[20:30] <thomi> ummmmm
[20:30] <thomi> let's start with that last one :D
[20:30] <barry> yuck
[20:31] <thomi> I guess it's a 'Bad Idea' to put .so files in a source package?
[20:31] <barry> oh, very much so
[20:31] <barry> also policy violating :)
[20:31] <thomi> :(
[20:31] <barry> can they not be built from source?
[20:32] <barry> (or maybe they can, but the build process is hidden upstream?)
[20:33] <thomi> there's certainly no way to build them in the .tar.gz that you download from pypi
[20:33] <barry> that's not exactly free software then is it?
[20:34] <thomi> well, the problem is that the tarball on pypi doesn't match their actual source code
[20:35] <barry> ew
[20:35] <barry> thomi: you might have to build the orig.tar.gz from $vcs branch
[20:35] <thomi> hmm, ok, I'll take a look
[20:36] <thomi> there's some debian server that allows you to download a tarball of a tag from google code, right?
[20:36] <barry> not that i know of
[20:36] <thomi> oh :(
[20:37] <barry> there are various ways to write a d/rules get-orig-source to checkout a tag.  it depends on what upstream is using for vcs
[20:37] <thomi> oh no: "Selenium uses a custom build system called crazyfun"
[20:37]  * thomi bangs head on desk
[20:37] <thomi> oh! it gets better!
[20:37] <barry> i still don't get it.  .so are platform dependent, so how can they possibly include them in their tar.gz?
[20:38] <thomi> "...we are in the process of replacing this with buck"
[20:38] <thomi> barry: they include a .so for every platform
[20:38] <thomi> and every arch
[20:38] <barry> *every* :)
[20:38] <thomi> well
[20:38] <thomi> x86 and amd64
[20:39] <thomi> all the good ones :D
[20:39]  * barry packs up his sparc machine
[20:39] <barry> and arm
[20:39] <thomi> arm? no one uses arm :P
[20:40] <barry> obscure platform
[20:42] <thomi> barry: so the upstream vcs includes bindings for all sorts of languages, including ones we don't support (C#)
[20:42] <thomi> what do I do to those files? Keep them in the source package, or strip them somehow?
[20:43] <barry> i'd probably keep them in the source package, but just ignore them for purposes of debian binary builds
[20:43] <thomi> ok
[20:51] <thomi> barry: what's the best way to aproach this? It sounds like you'd make an empty folder with just a debian/ directory in it... what tools would you use to build it from there? I've never managed to get that working very well
[20:52] <barry> thomi: are you going to try to get this into debian after the freeze?
[20:52] <thomi> barry: hmm.. probably not
[20:53] <thomi> Ii mean, I know I should
[20:53] <thomi> but I don't have the patience TBH
[20:53] <thomi> but *someone* should :D
[20:54] <barry> looks like python-selenium has a debian maintainer.  best to contact them about that
[20:54] <barry> ah, it's even in sid/non-free, and way behind upstream
[20:54] <barry> and behind in ubuntu
[20:54] <thomi> barry: Sascha Girrulat ?
[20:55] <barry> yeah
[20:55] <thomi> why is it in nonfree?
[20:55] <barry> thomi: no idea, but if it's got those .so's in it back then, that would probably explain it
[20:55] <thomi> hmmm
[20:57] <barry> thomi: so i'd probably start with `bzr branch ubuntu:python-selenium` and work from that branch.  maybe.  could be a lot of trouble if you need tons of modifications.  yeah, i guess this isn't going to be much fun
[20:57] <barry> thomi: if you start from scratch, create an empty debian/ and steal as much as you can from the ubuntu package
[20:58] <thomi> barry: that should be the same as what 'apt-get source python-selenium'; gets me, right?
[20:58] <barry> thomi: you might also reach out on ubuntu-devel and ubuntu-motu to see if anyone can give you a hand
[20:58] <barry> thomi: more or less.  could be less if the udd importer is broken on that package ;)
[20:58] <barry> so yes, you could start with that
[20:59] <barry> (and you can always create a bzr branch from the .dsc)
[20:59] <barry> just to have some local version control to make your life easier, not for any upload requirements or what not
[21:01] <thomi> ok, if i'm using upstream vcs as the source then there's not much I can steal  from the existing package
[21:13] <barry> it's a start at least
[21:13] <barry> maybe only d/rules will need to be rewritten
[21:13] <thomi> reading the git section of https://wiki.debian.org/onlyjob/get-orig-source scares me
[21:14] <barry> upstream is git?
[21:14] <thomi> yeah
[21:14] <thomi> https://code.google.com/p/selenium/source/list
[21:14] <barry> man, i know there are simpler examples.  not sure i can put my finger on one though
[21:15] <thomi> oooh! google code exports tarballs for every tag
[21:15] <thomi> such as: https://selenium.googlecode.com/archive/selenium-2.44.0.tar.gz
[21:15] <barry> hey, that could be much easier
[21:15] <thomi> so I can use d/watch after all
[21:15] <barry> cool!
[21:22] <thomi> barry: neither of their (two) build systems are packaged. Do I need to package those first?
[21:23] <barry> sadly yes
[21:23]  * thomi dies a little on the inside
[21:25] <thomi> ....they invoke their build systems by running a java .jar file
[21:25] <thomi> I feel like this source code is mocking me now
[21:26] <barry> it's certainly laughing at you from hell
[22:50] <balloons> veebers, adding json should be this simple :-) https://code.launchpad.net/~nskaggs/autopilot/add-json-build/+merge/247912
[22:50]  * veebers looks
[22:50] <veebers> balloons: heh nice, that is simple :-) /me tests
[22:55] <veebers> balloons: looks good to me
[23:11] <balloons> veebers, awesome :-)


[07:08] -GitHub[m]:#mir-server- **[MirServer/wlcs]** RAOF opened [pull request #250](https://github.com/MirServer/wlcs/pull/250): CI: Drive LXD directly, avoiding spread
[08:39] <RAOF> Saviq: what do you think of dropping the use of spread for WLCS and just driving the tests directly?
[08:41] <RAOF> I know why Ubuntu 22.10+ are failing, and could add another hack into spread to work around it, but it'd just be another hack, and we don't actually use most of the features of spread…
[08:52] <Saviq> Oi!
[08:54] <Saviq> RAOF (he/they) one reason why I like spread (at least for Mir) is that we (now, through LXD) can trivially reproduce the builds locally. What would the hack be? There is _some_ movement in spread upstream so we could try and move things there
[09:00] <alan_g[m]> Does it gain much over using LXC to set up a test environment locally?
[09:02] <Saviq> With the breadth of configs, IMO it does, since any config is just a `spread lxd:…` away. Maintaining that set locally is possible, but by the time you actually need it, you're likely to need to update enough for it to be easier to start from scratch
[09:03] <Saviq> While we could build a tool of our own around it, would it be better?
[09:21] <alan_g[m]> If we were doing it more often, I would care more. But it is an infrequent inconvenience
[09:21] <Saviq> "it"?
[09:22] <alan_g[m]> testing some non-native environment locally
[09:22] <Saviq> Right, but we'd have to maintain it for CI
[09:23] <Saviq> And I currently doubt it would be less maintenance than our spread solution
[09:31] <alan_g[m]> That is a more convincing argument than "can trivially reproduce the builds locally"
[09:51] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned AlanGriffiths to [issue #2695](https://github.com/MirServer/mir/issues/2695): Miriway died upon disconnecting external screen
[10:53] -GitHub[m]:#mir-server- **[MirServer/wlcs]** Saviq opened [issue #251](https://github.com/MirServer/wlcs/issues/251): Support for private tests... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/c3673b374e6277f15ddf5e222e979d21c9ff71d3>)
[11:27] <RAOF> @Saviq A fix (for now) for the spread failure-to-set-up-22.10+ images would be to delete `/etc/ssh/sshd_config.d/60-cloudimg-settings.conf` before restarting sshd in setup.
[11:42] <Saviq> alan_g on display reconfiguration, if through a wayland extension, would it be possible to switch layouts without creating a surface? That's a limitation of the sleep inhibitor that we would want to do away with some time.
[11:42] <Saviq> On that note, should sleep timeout maybe become part of the display layout? Sounds like something we may expose per display?
[11:45] <alan_g[m]> There's no requirement for a surface, just a connection on which globals can be published. But we'd obviously want to use `wl_output`
[11:48] <Saviq> FWIW I believe there are two distinct features here - clients asking for a display configuration (that we don't want on Frame, by default), and switching between predefined display layouts. The latter is what we should focus on.
[12:15] <alan_g[m]> The sleep inhibitor protocol chooses to use a surface so that inhibition can be associated with surface visibility. You could have a different protocol that does things differently
[12:16] <Saviq> Sure, just wanted to clarify what we're aiming for. Working with `wl_output` to select layouts sounds wrong to me when a layout describes more than one output
[12:21] <alan_g[m]> Thinking back to how mirclient managed display configurations we may want to allow a surface to be associated with a display configuration
[12:23] <Saviq> Sure, for the general case, but Frame should not respect those requests by default. We have a static display config defined by the operator and we should never stray from it
[13:03] <alan_g[m]> We have enough control over publishing extensions for that
[15:50] -GitHub[m]:#mir-server- **[MirServer/wlcs]** Saviq requested a review from RAOF for [pull request #252](https://github.com/MirServer/wlcs/pull/252): spread: use spread-mir-ci
[15:50] -GitHub[m]:#mir-server- **[MirServer/wlcs]** Saviq opened [pull request #252](https://github.com/MirServer/wlcs/pull/252): spread: use spread-mir-ci... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/49bc0201f495d5d326f898fc5f12c2cce244cd01>)
[16:17] <alan_g[m]> > fix unqualified use of `std::move`
[16:17] <alan_g[m]> Why would that be needed?
[16:18] <Saviq> https://github.com/MirServer/wlcs/actions/runs/3516098418/jobs/5892209519#step:5:1164
[16:29] <alan_g[m]> "-Wunqualified-std-cast-call` wtf?!
[17:54] <Saviq> Good night all o/
[18:13] <alan_g[m]> o/


[01:32] <stdin> jrib: you still want to see the hedgehog on the wheel?
[01:33] <jrib> stdin: is this a trick question?
[01:33] <stdin> no: http://jussi01.com/upload/uploads/20081022-012228-22102008033.mp4
[01:34]  * jrib eagerly awaits the end of the download
[01:34]  * jrib hopes it is not a video of rick astley
[01:35] <stdin> nah, I'm not that evil
[01:35] <genii> hehe
[01:36] <jrib> he's on it!
[01:36] <jrib> haha
[01:36] <stdin> yeah :)
[01:36] <jrib> that's really amusing to me
[01:38] <genii> Thats one insane hedgehog
[02:06]  * genii hands out a round of coffees
[04:04] <Flannel> So, since the CC didn't have a quorum today, they're just going to discuss it in private?  Does that seem odd to anyone else?
[04:05] <Flannel> Oh, Howdy all.
[04:06] <nalioth> discuss what?
[04:34] <Flannel> nalioth: the ubuntero thing
[04:37]  * nalioth thinks he missed something
[04:39] <Flannel> nalioth: https://launchpad.net/bugs/272826
[04:41] <nalioth> ahhh
[04:42] <nalioth> political correctness at it's best . . .
[07:14] <Mez> is ##club-ubuntu emma's channel?
[07:14] <Mez> yeah... hmmles
[07:14] <Mez> they have a new bot... linked to manpages.ubuntu.com
[07:15] <Mez> http://blog.dustinkirkland.com/2008/10/irc-bot-for-manpagesubuntucom.html
[07:20] <Flannel> yeah
[07:20] <Flannel> sort of silly
[07:27] <PriceChild> Hmmm hilights aren't working again after refreshing my irssi/config and I can't remember how to fix it. It will be a fun afternoon looking through it and remembering.
[07:59] <Flannel> Ah, fun.
[08:01] <ret> hmm.
[08:01] <ret> how would i go about becoming an ubuntu developer, and how long does the procedure take?
[08:01] <Flannel> ret: you know, threatening people certainly isn't a good way to win friends or influence people.
[08:01] <ret> Flannel: this doesn't truly address my request.
[08:02] <Flannel> ret: I was making no attempt to address your request.
[08:02] <ret> Flannel: but if you would like to address a prior problem you may or may not be having with me, please join #ret-op
[08:03] <Flannel> ret: If you aren't here to actually discuss disciplinary issues, please don't idle here.
[08:04] <ret>  Well, I would like to become an #ubuntu operator. I suppose this is on topic.
[08:07] <ret> :)
[08:07] <ret> Maybe not.
[08:13] <ret> Is anyone else here then :)
[08:14] <Flannel> Do I contact staffers regarding threats? or just ignore it?
[08:29] <jussi01> Morning all!
[08:29] <Flannel> Howdy jussi01
[08:30] <jussi01> Flannel: no harm in grabbing one and mentioning it
[08:30] <elkbuntu> was that who i think it was?
[08:30] <Flannel> elkbuntu: hmm?
[08:30] <elkbuntu> the person who has claimed to be 73 years old
[08:30] <Flannel> elkbuntu: If the person you thought it was likes threats of DOSs and feeding my fingers and toes to my kids... then perhaps.
[08:31] <Flannel> jussi01: I couldn't find anyone who was awake, but next time I see one, I'll mention it.
[08:31] <Flannel> He's also in +1
[08:32] <elkbuntu> Flannel, i'm thinking it's bunnyto
[08:32] <elkbuntu> just the MO in this channel
[08:34] <elkbuntu> http://pastebin.ca/ExTCrfMh pass:idjit
[08:35] <elkbuntu> not sure why i put a pass on that, but meh
[08:36] <Flannel> doesn't really sound like the same person.  But that doesn't mean much.
[08:37] <jussi01> btw, I fixed the video link everyone
[08:37] <elkbuntu> video link?
[08:37] <Flannel> http://jussi01.com/?p=42
[08:38] <jussi01> err, hang ona sec...
[08:39] <elkbuntu> ooh, teh hedgehog
[08:39] <jussi01> ok, now really fixed
[09:01] <elkbuntu> 30 seconds lag here, incoming netsplit?
[09:02] <Flannel> not here
[09:06] <jussi01> not here either
[09:14] <elkbuntu> must just be the leaf i'm connected to
[09:16] <jussi01> oh sigh... stupid spammes...
[09:23] <elkbuntu> jussi01, where?
[09:23] <jussi01> elkbuntu: everywhere, #u #k and #x - the one with the big "dick" or "balls"
[09:25] <elkbuntu> jussi01, ah yeah. it looks like a possible compromised dreamhost box...
[11:36] <ikonia> <IP_ADDRESS> seems a lot of people connected from that IP from "software Technology Parks of India"
[11:57] <ikonia> @btlogin
[13:12] <ikonia> got my eye on ret back in #ubuntu+1
[13:14] <ikonia> @btlogin
[13:14] <ikonia> eagles is in #ubuntu+1
[13:14] <ikonia> is that accetpable - I don't know the details of his current ban
[13:15] <ikonia> (s)
[13:15] <ikonia> where is hobbsee
[13:15] <ikonia> it looks like he's ok in there according to bt
[13:15] <elkbuntu> leave him until he causes grief
[13:16] <ikonia> he just parted any way
[13:16] <ikonia> just in #kubuntu-devel
[13:17] <Tm_T> ikonia: who?
[13:18] <ikonia> eagles
[13:18] <ikonia> eagles0513875
[13:19] <Tm_T> ah, him
[13:21] <ikonia> he was fine, just needed to check it was ok he was there
[13:22] <ikonia> I knew hobbsee had had a long ban with im
[13:22] <ikonia> him
[13:25] <elkbuntu> he's basically hobbsee's issue.
[13:26] <elkbuntu> unless we need to stop a disruption, we keep out of it.
[13:27] <jussi01> hehe
[13:40] <ikonia> fair enough, just checking
[13:49] <Pici> sudo vim!
[14:10] <christel> i cant read today, i read the "im" (him) from ikonia and "basically hobbsee's issue" from elkbuntu and pondered why elkbuntu was hobbsee's issue :x
[14:27]  * jussi01 hugs christel
[14:27]  * jussi01 slides genii a piping hot kubuntu mug of coffee!
[14:33] <genii> jussi01: Heh, thanks, needing all the caffeine I can find this morning
[14:34] <ikonia> jussi01you're such a corperate lacky
[14:35] <genii> If only we actually had Kubuntu mugs, jussi01 could sell them.... ;)
[14:40] <jussi01> ikonia: how so?
[14:44] <Pici> jussi01: Probably becauase of all the coffee that you're getting for everyone.
[14:51] <jrib> erm
[14:51] <jrib> what
[14:51] <Pici> lag, I guess.
[14:51] <jrib> stupid bot
[14:51] <genii> What the hells going on in #ubuntu with the floodbots?
[14:52] <LjL> i just joined, what's happening?
[14:55] <jrib> LjL: floodbot set +Rr for no apparent reason, pici took it off, then floodbot went and put it back on
[14:55]  * jrib pastes log one sec
[14:56] <jrib> http://paste.ubuntu.com/61000/ I guess you joined by then though
[14:57] <jrib> different bots though
[14:59] <LjL> jrib: thanks. yes when you see ljl-temp joining, that's me attaching
[15:00] <LjL> jrib, Pici: it was just a false positive because there were a few joins (remember how those used to happen relatively often?). there's always some degree of probability that too many legitimate people will join for the floodbots' liking
[15:00] <Pici> LjL: Okay, so this shouldn't happen again for a while?
[15:01] <jrib> LjL: can we somehow tell the floodbots to backoff?  I think the false positives are ok, but if an op sets a mode, the floodbot shouldn't change it so fast
[15:03] <LjL> jrib, if an op sets a mode, the bot will considered the perceived "attack" handled and not do anything more about it
[15:03] <LjL> the problem is, in this case it was a *different* bot
[15:03] <LjL> which thought there was an attack *after* you had already set the modes
[15:03] <jrib> I see
[15:04] <genii> Too bad they don't talk to each other, as such
[15:05] <LjL> genii: that would be slightly too complicated (they can certainly talk to each other on irc, though)
[15:06] <ikonia> jussi01: you where not just giving out cups of coffee, but kubuntu coffee
[15:08] <genii> ikonia: It's sort of an inside joke, virtual Kubuntu mugs of coffee are given out in #kubuntu-offtopic a lot
[15:09] <genii> LjL: Interesting. Maybe they could pass values by pm to each other meaning "OK I just set channel mode, wait a while" or so
[15:09] <Seeker`> genii: How do you ensure it isn't someone else impersonating the bot?
[15:09] <LjL> Seeker`: because only the bots can be identified to services *and* have "floodbotn" nicknames
[15:10] <genii> Seeker`: whois ?
[15:10] <LjL> genii: that's not really needed, because they can *see* that the other bot set the mode in the first place ;)
[16:10] <LjL> jrib: that shouldn't happen anymore now
[17:02] <jrib> !botclone =~ s/additionals/additional/
[19:28]  * Tm_T huggggggs Myrtti tightly
[19:29] <Myrtti> hi
[19:33] <Pici> !yay | Myrtti
[19:34] <Pici> Glad to have you back
[19:34] <Myrtti> me too
[19:34] <Myrtti> I had to do something to reduce the background noise for a while
[19:40] <Myrtti> I know I'm missing some channels...
[19:40] <Myrtti> I just can't put my finger on which
[19:54] <Myrtti> mmmm soup
[20:02] <Pici> mmmm zsh
[20:04] <Pici> I spent the last 30 minutes trying to import my personal .zshrc into a redhat system with weird extra environment variables
[20:51] <LjL> GasFurnace can forget joining any Ubuntu channel from now on.
[20:56]  * jussio1 is on the train to oulu again
[20:56] <PriceChild> Hi ErrantEgo, how can we help you?
[20:57] <ErrantEgo> no help needed
[20:59] <GasFurnace> so yeah why was i banned from offtopic
[20:59] <LjL> for trolling once too many
[20:59] <GasFurnace> its an offtopic room
[21:00] <LjL> trolling is not condoned
[21:00] <LjL> also, you did the same in #kubuntu, at the same time
[21:00] <PriceChild> Quite the collection.
[21:00] <LjL> and you've done this before, many times
[21:00] <GasFurnace> yeah wrong room
[21:00] <LjL> and there's no reason to believe you won't do it again
[21:01] <GasFurnace> how is saying ext3 sucks in an offtopic room trolling
[21:02] <PriceChild> wikipedia says a troll is...
[21:02] <PriceChild> "a person who is deliberately inflammatory on the Internet in order to provoke a vehement response from other users"
[21:02] <PriceChild> Yes, its wikipedia but I'd say that's a reasonable description. Can you see how that applies?
[21:02] <nalioth> GasFurnace: can we help you with something?
[21:03] <GasFurnace> I want an answer why i was kicked from ubuntu-offtopic saying something sucks is not trolling
[21:03] <LjL> GasFurnace, you weren't really kicked from #ubuntu-offtopic
[21:03] <nalioth> you _were_ trolling.
[21:03] <LjL> due to your continued trolling behavior,
[21:04] <LjL> you are now unwelcome on any Ubuntu channel.
[21:04] <GasFurnace> says who
[21:04] <LjL> says i
[21:04] <GasFurnace> you cant find me if my ip changes like it does twice a year
[21:05] <LjL> GasFurnace: ban evasion is not tolerated.
[21:05] <GasFurnace> ok
[21:05] <LjL> do you have any other questions?
[21:05] <GasFurnace> yeah
[21:06] <GasFurnace> Im done trolling
[21:06] <Myrtti> and the question?
[21:06] <GasFurnace> Linux sucks ubuntu sucks and windows owns
[21:06] <LjL> @mark #ubuntu-ops john_nel
[21:07] <PriceChild> Yay he made it easy for us.
[21:07] <PriceChild> I guess we'll see him next spring 8-)
[21:07] <LjL> i had /b gasfurnace pre-typed
[21:08] <LjL> watch out anyway, he also uses the ident Administ (which i can't really ban)
[21:08] <LjL> and i really think his IP changes more often than twice a year
[21:08] <PriceChild> Is Admininst common to something?
[21:09] <LjL> PriceChild: it's what a Windows user who logs in as Administrator and uses a client that truncates idents to 8 characters gets
[21:09] <LjL> actually, i think freenode (like other networks) truncates to 8 to begin with
[21:10] <PriceChild> That makes sense.
[21:14] <jussio1> did I mention I love kde 4 and its new network manager? built in 3g mobile connect!
[21:52] <Seeker`> eww, Rafik's quit message does horrible things to putty
[21:52] <PriceChild> Seeker`: where was he?
[21:52] <Seeker`> -irc
[21:53] <Seeker`> I get malformed characters spread over a few lines
[21:54] <PriceChild> I see lots of ?s so guess that's some unicode messed up.
[21:55] <Seeker`> actually, it means that I cant read what happens in -irc
[21:56] <PriceChild>  /reload do anything?
[21:56] <PriceChild> I guess you should sort out your unicode.
[21:56] <Seeker`> http://cjo20.pastebin.com/d609df1de
[21:56] <Seeker`> quite possibly
[21:58] <Seeker`> aha, UTF-8 is much better
[22:01] <LjL> it's not messed up
[22:01] <LjL> it's just utf arabic
[22:03] <LjL> PriceChild: proof - [22:33:55] --> administrator has joined this channel (n=administ@cpc1-bele4-0-0-cust104.belf.cable.ntl.com).
[22:03] <PriceChild> I didn't doubt you :)
[22:04] <LjL> and nalioth: you might find the fact that john_nel now also joined #gentoo and #gentoo-ops interesting
[22:04] <LjL> told them to keep a watch on him
[22:05] <nalioth> noted
[22:05] <LjL> he changed nickname to do that (of course)
[22:51] <LjL> jrib: <plasmarox> im having troubles downlloading the depostitaries indexes when i update
[22:56] <Pici> Just as long as it wasn't suppositories.
[23:06] <jdong> Pici: http://ubuntuforums.org/showthread.php?t=25171
[23:06] <jdong> I also particularly like "hoardy hedgehog" in that context.


[08:52] <brobostigon> morning boys and girls.
[09:00] <SuperEngineer> \o
[09:01] <brobostigon> o/
[10:11] <zmoylan-pi> o/
[10:12] <brobostigon> o/
[11:49] <diplo> 1
[11:52] <zmoylan-pi> 2
[12:05] <SuperEngineer> 2 1/2
[12:07] <diplo> 3
[12:07] <diplo> Couldn't get focus on screen :)
[12:08] <zmoylan-pi> makes it way harder to count the pixels that way... :-)
[12:23] <diplo> heheh
[12:28] <Azelphur> Random question, does anyone know of a gadget I can use to print QR code labels? I've tried label printer in my laser printer, but it's really hard to get them lined up right.
[12:31] <zmoylan-pi> i think they can be printed on any printer... it really comes down to cost of printer and consumables...
[12:33] <diplo> yeah, we've used proper Zebra label printers for work, but I've also printed one on my HP here and it works with my phone
[12:33] <diplo> I'd go with quality of print is part of the issue, try from a PDF on screen and same after printing
[12:37] <zmoylan-pi> perhaps a laser printer with a better single page feed?
[12:38] <zmoylan-pi> then sorting the templates for whatever app you're printing from
[15:52] <daftykins> Azelphur: why not a Dymo?
[21:38] <Azelphur> daftykins: could do
[22:46] <zmoylan-pi> last time i had access to a printer specifically for labels from a computer was mid 90s... an avery label printer iirc...
[23:32] <daftykins> :D
[23:32] <daftykins> i've been amused recently when clients on Windows 10 have gone to print a normal page - and because 10 tries to be clever in 'managing' your default printer, they've been presented by the cutest little diddy 1" high rendition of their document
[23:33] <diddledan> haha
[23:46] <zmoylan-pi> postage stamp mode: saves on paper and postage... :-P
[23:47] <daftykins> it does!
[23:52] <diddledan> postage stamp mode even prints your postage stamp!
[23:52] <daftykins> something i got from ebay the other day had a printed one, it just said "Only to be used once" and wasn't crossed through or anything after delivery
[23:52] <daftykins> so surely that could be done once, posted back to the sender and then used over and over


[02:37] <arafat> anybody there ?
[02:37] <arafat> Hello
[08:29] <toufique> Hi
[08:29] <toufique> Anybody here?
[21:01] <kaziweb> hello
[21:02] <kaziweb> is there any one to talk?
[21:02] <kaziweb> I'm here for the first time.


[00:22] <kamal> dannf, remind me about this tomorrow and I'll help poke it if you like
[14:12] <Joe_CoT> smb, were you able to replicate  #1349883 ?
[14:13] <apw> bug #1349883
[14:13] <smb> Joe_CoT, No, not locally and not on the few ec2 m1.small I started up. One of those ended up on an AMD, the other on some Intel but even with a few reboots the times in dmesg were ok
[14:15] <Joe_CoT> ok. would it be helpful if I reproduced it on a clean instance and gave you ssh access to it?
[14:18] <smb> Hm, maybe... give me a sec (or a few minutes) Thenn I try to see whether I can do what I am thinking of on a local instance
[14:21] <Joe_CoT> ok
[14:30] <smb> hrm, could be some minutes more... only getting around 300K/s for the ddebs...
[15:13] <smb> Joe_CoT, So I am not really sure it would help. Though I can have peeks at the vpcu time info, I suspect it would only show a high system time (which we already know) and the general progress of time. From what I get from the data we have, this is a one time badness only. Meaning from that point at boot when it jumps, it increments normally
[15:14] <Joe_CoT> yes
[15:14] <Joe_CoT> but once it boots once badly, it consistently reboots badly
[15:14] <Joe_CoT> again, I think it's the specific hardware it runs on.
[15:14] <Joe_CoT> if I give you a bad one, when you reboot it it'll still be bad
[15:15] <smb> That could be one additional part of circumstances, yes
[15:15] <Joe_CoT> I'm busy deploying a new code release, but after that I'll see if I can give you a clean instance where it's happening
[15:16] <smb> Ok, yeah. I need a bit more time to get my head around the code anyway.
[16:57] <slangasek> jsalisbury: so I'm having a terrible time with my KVM host box all of a sudden becoming very unstable, and kernel panicking left and right.  I'm concerned that it might be hardware flakiness, because the panics don't seem to all be in the same place.  Do you have any advice for me before I start hand-transcribing kernel oopses into LP?
[17:02] <jsalisbury> slangasek, I guess the first thing to check, did anything change?  Did you apply any updates or upgrade the kernel?
[17:02] <jsalisbury> slangasek, It might be good to try an older kernel, that was known to work and see if the panic persists or goes away, that might indicate if a software change caused this.
[17:03] <slangasek> jsalisbury: I previously had 3.11.0-26 installed, which is when I first saw a crash; then I upgraded the host to trusty in response to this, and am now running 3.13.0-32 which is definitely crashy
[17:03] <slangasek> jsalisbury: prior to that I was running on the saucy kernel for a long long time
[17:04] <jsalisbury> Can you test a Saucy kernel to see if the panic stops?  I can post a link to one, if you don't have one installed already.
[17:05] <jsalisbury> slangasek, If the panic persists, then it might indicate hardware.  If it goes away, we should did deeper.
[17:05] <jsalisbury> s/did/dig/
[17:06] <kirkland> howdy!  the 3.13.0-32-generic update is rendering my Intel NUCs unbootable
[17:07] <jsalisbury> kirkland, uh oh.  Do you get a panic, or blank screen, or something else?
[17:08] <kirkland> jsalisbury: hung on the ubuntu splash screen;  never makes it into the desktop
[17:08] <kirkland> jsalisbury: note that this only happens on a cold boot (warm reboots seem to work fine)
[17:08] <kirkland> jsalisbury: and downgrading back to the -24-generic kernel also seems to work fine
[17:08] <slangasek> jsalisbury: I still have the saucy kernel to hand, I'll reboot and see
[17:09] <jsalisbury> kirkland, can you turn on the screen to get further debugging?  I think you just need to remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
[17:10] <jsalisbury> kirkland, and see if anything is printed.
[17:10] <kirkland> jsalisbury: done;  powering down then booting again
[17:11] <jsalisbury> kirkland, just don't forget to run update-grub too
[17:14] <kirkland> jsalisbury: okay, I have call traces now
[17:14] <kirkland> jsalisbury: pictures from my phone
[17:14] <kirkland> jsalisbury: looks like its http://support.sundtek.com/index.php/topic,1600.0.html
[17:14] <jsalisbury> kirkland, cool, that should help.
[17:17] <jsalisbury> kirkland, looks like the bug is upstream as well.   I'm reading through the forum posts and upstream bug report.
[17:18] <jsalisbury> kirkland, We probably pulled in the offending commit as part or upstream updates.
[17:18] <kirkland> jsalisbury: okay -- is there a fix upstream yet for the offending commit?
[17:20] <jsalisbury> kirkland, I see a test patch in the upstream bug report.  I guess it might be worth while to test the latest mainline kernel, in case it's being worked from someone else too.  It can be downloaded from:
[17:20] <jsalisbury> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc7-utopic/
[17:25] <jsalisbury> kirkland, The -24-generic kernel was based off of upstream 3.13.9, so we can also bisect from that version on, if mainline still exhibits the bug.
[17:28] <kirkland> jsalisbury: seems I do not trigger the bug, if I unplug my usb keyboard when booting
[17:28] <jsalisbury> kirkland, It appears to be xhci related and there were a few changes I can look at closer.
[17:33] <jsalisbury> kirkland, I'll build a test kernel with some of the xhci changes reverted to see if we can narrow down the cause and not have to bisect.  I'll post a link in a bit.
[17:34] <jsalisbury> kirkland, just to confirm, the mainline kernel still has the bug, if you leave the keyboard connected while booting?
[17:36] <slangasek> jsalisbury: so, the saucy kernel just crashed for me again.  Interestingly, while on trusty the crashes seem to be more varied, this saucy crash is the same or similar to the last saucy crash I saw, which is ksm-related
[17:41] <jsalisbury> slangasek, Hmm, and you used a kernel that never paniced before?  It might be worth while to run a memory test real quick on the machine.  Any type of HW related errors in the syslog?
[17:41] <slangasek> nothing hw-y in the syslog, no; and it never panicked before earlier this month, around the time the weather turned hot ;P
[17:43] <jsalisbury> slangasek, heh, blame the weather
[17:44] <slangasek> jsalisbury: the problem has persisted when the weather got better :)
[17:44] <jsalisbury> slangasek, speaking of weather, does the syslog have any mention of temp readings?
[17:44] <jsalisbury> slangasek, Just shut the window, lol
[17:44] <slangasek> wat
[17:44] <slangasek> shutting the window is what makes the room hot! :)
[17:45] <jsalisbury> slangasek, whoops, figured keeping the rain off might help :-)
[17:45] <slangasek> jsalisbury: what would I search for to find temp readings? 'temp' doesn't find anything useful
[17:46] <jsalisbury> slangasek, you would find something like this: " Core temperature above threshold"
[17:46] <jsalisbury> or "Core temperature/speed normal"
[17:46] <slangasek> jsalisbury: nada
[17:46] <jsalisbury> slangasek, maybe the logs rolled and the temps been ok.  Maybe grep the /sys/log directory
[17:47] <slangasek> jsalisbury: did that already
[17:49] <TJ-> slangasek: I've found lm-sensors and the 'sensors' util good for monitoring, or simply "cat /sys/class/thermal/thermal_zone*/temp"
[17:49] <jsalisbury> slangasek, Hard to know if it is HW releated if there are no errors.  Can you post a picture of the crashes
[17:51] <slangasek> jsalisbury: the fact that the backtraces are varied makes that more difficult.  If I get the same ksm crash on saucy again, perhaps I'll take a picture - but saucy is EOL so that hardly helps for getting it fixed
[17:51] <slangasek> and in trusty the backtraces are all over the map
[17:57] <kirkland> jsalisbury: do we have a Launchpad bug for this yet?
[17:57] <kirkland> jsalisbury: do you want me to file one?
[18:00] <jsalisbury> kirkland, That would be great
[18:00] <slangasek> jsalisbury: memory test> I don't think we have a memtest that works on UEFI-only systems, do we
[18:01] <jsalisbury> slangasek, hmm, I don't know off hand.  Can you not selecet it from the GRUB menu?
[18:01] <slangasek> nope
[18:01] <slangasek> memtest86+ has grub code that specifically says it doesn't work on UEFI
[18:02] <jsalisbury> slangasek, Ahh, ok.
[18:02] <slangasek> /etc/grub.d/20_memtest86+:
[18:02] <slangasek> # We need 16-bit boot, which isn't available on EFI.
[18:02] <slangasek> if [ -d /sys/firmware/efi ]; then
[18:02] <slangasek>   exit 0
[18:02] <slangasek> fi
[18:03] <jsalisbury> slangasek, It makes it difficult that the backtraces are not consistent.  Do you have to put some load on the machine, or does just booting and waiting trigger it?
[18:03] <mjg59> memtest is difficult with UEFI
[18:04] <mjg59> Because the firmware is using so much more of the memory
[18:04] <slangasek> jsalisbury: the "load" appears to be nothing more than having VMs configured to start at boot
[18:04] <mjg59> You'd probably need something that did ExitBootServices() and then ignored the runtime regions
[18:04] <mjg59> And hoped that there was no periodic SMM code using them
[18:04]  * slangasek nods to mjg59
[18:05] <slangasek> and writing that is out of scope for my current problem ;)
[18:06] <jsalisbury> slangasek, to see if it is HW releated, can you try to boot a LiveCD and see if you can get a crash again.  That would rule out anything configuration wise.
[18:07] <slangasek> jsalisbury: not conveniently, but I'll put that on my list of things to try
[18:08] <jsalisbury> slangasek, ok
[18:09] <jsalisbury> kirkland, Can you try the test kernel here: http://kernel.ubuntu.com/~jsalisbury/kirkland/
[18:09] <kirkland> jsalisbury: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350480
[18:10] <jsalisbury> kirkland, That has four out of the five xhci commits added after 3.13.9 reverted.
[18:12] <jsalisbury> kirkland, The fifth didn't revert without a backport, so I'll revert that one if the bug still exists with v1 of this test kernel.
[18:14] <kirkland> jsalisbury: installing now
[18:15] <jsalisbury> kirkland, this one needs the linux-image-extra package as well as linux-image
[18:15] <kirkland> jsalisbury: k
[18:15] <kirkland> jsalisbury: I'm just trying to apport-collect before I reboot
[18:16] <jsalisbury> kirkland, ack
[18:16] <kirkland> jsalisbury: rebooting
[18:17] <kirkland> jsalisbury: Linux OrangeBox01 3.13.0-33-generic #58~DustinTestKernelv1 SMP Wed Jul 30 17:40:39 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[18:17] <kirkland> jsalisbury: booted just fine ;-)
[18:19] <jsalisbury> kirkland, Hmm, cool.  So that means with was one of these four commits:
[18:19] <jsalisbury> 7ba40e8 xhci: delete endpoints from bandwidth list before freeing whole device
[18:19] <jsalisbury> 8172925 usb: xhci: Prefer endpoint context dequeue pointer over stopped_trb
[18:19] <jsalisbury> 00bd7b9 xhci: Switch Intel Lynx Point ports to EHCI on shutdown.
[18:19] <jsalisbury> c349a2e xhci: Prevent runtime pm from autosuspending during initialization
[18:20] <jsalisbury> kirkland, I'll try to revert only two of them and see if we can narrow it down.
[18:22] <Joe_CoT> smb, I was able to reproduce it right away. Can you toss me your public ssh key, and preferably your IP, and I'll give you access?
[18:23] <Joe_CoT> For reference, it was m1.small, in us-east-1c, off the latest Ubuntu 14.04 PV SSD AMI, straight off
[18:23] <smb> Joe_CoT, You should be able to use "ssh-import-id smb" for that
[18:25] <Joe_CoT> nifty
[18:26] <smb> So in theory I should be able to get there if you pm me the external host name
[18:26] <Joe_CoT> yeah, give me a minute and I'll have you set up
[18:32] <Joe_CoT> smb, all set. PMed. You have full reign of that server. Just lmk when you're done with it
[18:33] <smb> ack
[18:37] <Joe_CoT> smb, that server has ssh allowed in, http and https allowed out. LMK if you need more than that. You can reboot it as many times as you want, but please don't shut it down, as the problem may go away if they switch hardware on me.
[18:38] <smb> Joe_CoT, Ok, sure.
[18:51] <jsalisbury> kirkland, the second test kernel is ready at: kernel.ubuntu.com/~jsalisbury/kirkland/
[18:51] <jsalisbury> kirkland, if my guess is right, this kernel should still have the bug.
[18:52] <jsalisbury> kirkland, I think the bug is going to be caused by:
[18:52] <jsalisbury> 8172925 usb: xhci: Prefer endpoint context dequeue pointer over stopped_trb
[18:52] <jsalisbury> kirkland, I'll start building a third test kernel with just commit  8172925 reverted.
[19:06] <kirkland> jsalisbury: testing that 2nd one now
[19:09] <jsalisbury> kirkland, ack
[19:09] <kirkland> jsalisbury: Linux OrangeBox01 3.13.0-33-generic #58~lp1350480v2 SMP Wed Jul 30 18:25:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[19:09] <kirkland> jsalisbury: hang on
[19:10] <kirkland> jsalisbury: let me do a hard power down, and up
[19:10] <jsalisbury> kirkland, ok.  I expect it may have the bug
[19:10] <kirkland> jsalisbury: yeah, sorry, that previous warm boot worked fine;  it's cold boots that suffer
[19:11] <jsalisbury> kirkland, good :-)
[19:11] <jsalisbury> kirkland, A 3rd kernel is building now with only commit 8172925 reverted.  I expect it will be the fix
[19:11] <kirkland> jsalisbury: boom
[19:11] <kirkland> jsalisbury: explosions in the sky
[19:12] <jsalisbury> kirkland, I'm already crafting an email to the patch author.  In the mean time, we can request a revert upstream and in Ubuntu, once we verify it's that commit.
[19:13] <jsalisbury> kirkland, build should be done in a few minutes
[19:14] <kirkland> jsalisbury: okay, I'm ready and waiting :-)
[19:22] <jsalisbury> kirkland, The kernel is ready at: kernel.ubuntu.com/~jsalisbury/kirkland/
[19:23] <jsalisbury> kirkland, If it fixes the bug, I'll fire off some email to have it reverted
[19:23] <kirkland> jsalisbury: k
[19:29] <kirkland> jsalisbury: v3 boots fine (cold + warm boot)
[19:29] <kirkland> jsalisbury: Linux OrangeBox01 3.13.0-33-generic #58~lp1350480OnlyCommit8172925Reverted SMP Wed Jul 30 18:56:31 U x86_64 x86_64 x86_64 GNU/Linux
[19:30] <jsalisbury> kirkland, great.  I'll send email upstram and cc you.  I'll also request that this gets reverted in the Ubuntu kernel
[19:34] <kirkland> jsalisbury: fantastic, thanks for this :-)
[19:34] <jsalisbury> kirkland, np
[19:36] <smb> Joe_CoT, So I would be off the machine for today.  I extracted some data. Interesting that most time info actually is correct. Like uptime and even the formatted time in /var/log/syslog. Just the seconds in the timestamp are off. Also interesting that while the timestamp in dmesg on my local system is correct, the vcpu_info time actually is the uptime of the host. Apparently that gets corrected by the delta (of tsc
[19:36] <smb> timestamp in the same struct and result of readtsc)
[19:36] <smb> While on that host it seems to be the same
[19:36] <smb> So looks a bit like the correction delta goes wrong and you end up having the hosts uptime in dmesg
[19:37] <Joe_CoT> the formatted time in syslog is correct, when using rsyslog. When using syslog-ng, it ends up with logs in october
[19:37] <Joe_CoT> because it's using the time from kmsg
[19:37] <Joe_CoT> but when I reported I brought it down to the core problem, which is the dmesg timestamp
[19:39] <Joe_CoT> If you're done for the day I'll turn it off then. If you need it again lmk. I'll try to be in the channel when I'm in the office, if I disappear give me a poke on the bug or by email.
[19:39] <smb> Probably syslog-ng does its own calculation in some way. Just some additional fact. I mean the main issue is as you pointed out, the dmesg timestamp being wrong
[19:40] <Joe_CoT> I think that syslog-ng does: current time - uptime + dmesg time. Which is why it's getting dates in the future
[19:40] <smb> Sounds reasonable. Basically offset by the hosts uptime
[19:41] <smb> and not the guests
[19:41] <Joe_CoT> And if you do dmesg -T you'll see the same then
[19:41] <Joe_CoT> yeah
[19:42] <Joe_CoT> /proc/uptime ends up with the guest uptime, but /dev/kmsg is using timestamps based on the host uptime
[19:43] <smb> Since the field containing the system time is the uptime of the host in both cases, there must be somethign wrong with how the delta is used. But I won't have enough brain for that to figure out right now.
[19:43] <smb> Oh when I say host I meant the host running the guest
[19:44] <smb> And we probably are on the same page and I am just too dumb by now. :)
[19:44] <Joe_CoT> lol, ok
[19:45] <Joe_CoT> well if you need back on the server later, lmk. I'm just hoping to have this fixed before I've got PCI auditors rolling through. Don't really want to explain how our servers went back to the future :D
[19:49] <smb> Heh ok, will do. You may always claim they run ahead of time to spot problems sooner. :-P
[19:51] <Joe_CoT> For now I just changed syslog-ng to ignore the time from the kmsg logs. It means that on server startup the entire startup shows up in the logs as the same second. That's better than October.
[19:53] <smb> True... unless it is October, though then it would be likely next year in the logs...
[19:53] <smb> Btw, I write up some summary and will post it to the bug report
[21:59] <bjf> slangasek, bug 1350035 is preventing any automated testing of Utopic by either CI or the kernel team
[23:06] <xnox> slangasek: bjf: i believe dropping essential:yes from init metapackage would fix it. Which i have done 10h ago, but it's stuck in utopic-proposed because of the alpha2 freeze block. And debootstrap doesn't know how to use overlay repositories, so we need to wait till tomorrow for block to drop, init to migrate and try again.
[23:07] <xnox> updated bug report.
[23:14] <bjf> xnox, many thanks for that update


[00:33] <adam_g> using PPA, is 'instance-state' meant to reach the 'started' state, or stop at 'provisioned' ?
[00:40] <hazmat> adam_g, started
[00:41] <hazmat> robbiew, cool, good to know thanks
[00:43] <adam_g> hazmat: hmm. at least the bootstrap node of this new environment only made it as far as 'provisioned' with orchestra,but seems otherwise fine
[00:43] <hazmat> adam_g, hmm.
[00:45] <hazmat> adam_g, looking at the orchestra provider, it looks like its either 'provisioned' or 'pending'
[00:45] <hazmat> so no 'started' staet..
[00:45] <hazmat> probably worth a trivial for consistency
[00:46] <hazmat> except its not really checking that the machine is started
[00:46] <adam_g> hazmat: right, i knew it hit 'provisioned' as soon as it finishes its preseeded install. thought it went to 'started' in the past, though, after first boot
[00:48] <hazmat> adam_g, apparently not.. does orchestra provide that info?
[00:48] <hazmat> the code reads.. state = "pending" if d["netboot_enabled"] else "provisioned"
[00:48] <hazmat> not sure what other info is available from cobbler wrt to the actual state
[00:50] <hazmat> interesting yet another cobbler fork.. http://code.google.com/p/madhatter/
[00:53] <hazmat> i don't see anything more appropriate for actual status looking over the internal data struct.. https://github.com/cobbler/cobbler/blob/master/cobbler/item_system.py
[00:54] <SpamapS> cobbler only knows that it has been setup for pxe boot
[00:54] <SpamapS> and can be asked what the power state is *if* it has power control setup
[00:54] <jcastro> SpamapS: hey, my mini proliant came in
[00:54] <jcastro> you want one
[00:54] <jcastro> it is SO cute.
[00:55] <jcastro> I think everyone should have one
[00:57] <marcoceppi> I know what the charm contest winners can put their gift card towards
[01:01] <adam_g> those mini proliants are great
[01:01] <adam_g> and cheap
[01:13] <bkerensa> adam_g: but are they energy efficient?
[01:15] <bkerensa> oo 150W
[01:15] <bkerensa> two PCI slots so you could turn it into a little RADIUS box
[08:38] <yolanda> hi, can i get some help with a charm? i have a db-relation-joined hook with postgresql, and seems that my hook hasn't been called. If i debug and call it manually my charm is working, if not, seems that the code isn't triggered
[09:25] <yolanda> hi m_3, are you available? i found a problem in the openerp&postgres hooks
[10:12] <_mup_> juju/trunk r521 committed by<EMAIL_ADDRESS>[10:12] <_mup_> [trivial] merge provider-error status fix [a=bac][r=hazmat]
[12:03] <yolanda> hi, what's correct way of restarting a service in a juju charm?
[12:03] <yolanda> i have something like that:
[12:03] <yolanda> # restart service
[12:03] <yolanda> service openerp-core start || service openerp-core restart
[12:04] <yolanda> however, it doesn't seem to be stopping openerp-core, it says that the process doesn't exist. If i find it manually using a ps -ef, do a kill and start the service, then works
[12:17] <yolanda> hi, need help with a juju charm, i'm having problems restarting a service
[12:26] <sc-rm> yolanda: where does your restart part of you gem look for the pid of the process and is that pid stored there when startet through your charm?
[12:26] <yolanda> sc-rm, there is an openerp-core service, that is started on the install hook
[12:26] <yolanda> and in the db-relation-changed, i try to restart it
[12:27] <yolanda> because i need some changes to be applied on a config file
[12:28] <marcoceppi> yolanda: How is it started in the start hook?
[12:28] <marcoceppi> err, in the install hoook*
[12:28] <sc-rm> youlanda: so openrp-core is a standard script in the init.d ? aka you are able to do /etc/init.d/openrp-core start|stop|restart and it works?
[12:29] <yolanda> sc-rm, yes
[12:30] <yolanda> the service is started automatically when installed the package
[12:30] <yolanda> however, do i need to also provide an start hook that starts the service? or if it's done in the install is enough?
[12:30] <sc-rm> youlanda: okay, but if you log into that machine are you then able to do /etc/init.d/openrp-core stop and the process stops?
[12:35] <yolanda> sc-rm, not at first try, if i do it it says that the process doesn't exist, but i can do a "ps -ef | grep openerp" and kill it
[12:35] <yolanda> then if i do the service openerp-core start it works, and after that i can restart correctly
[12:36] <yolanda> seems that there is some problem between install and db-config-changed hooks
[12:36] <sc-rm> youlanda: ahe, there is the problem, the way the service is started is not storing the pid in the same place as the start script expect it to be located
[12:37] <sc-rm> the openrp-core script in init.d is that something you created and is it public accessible?
[12:42] <yolanda> sc-rm, the openerp-core is a package that we are writing for openerp 6.1 version
[12:42] <yolanda> i can send you the url for you to check it
[12:53] <yolanda> sc-rm, code for the package is here: https://code.launchpad.net/~openerp-community/openerp-tools/yolanda.robla-openerp-core
[13:10] <yolanda> sc-rm, any idea?
[13:46] <yolanda> hi, any help with the openerp start script, please? i'm just blocked with that, only i need to restart service correctly to finish the charm
[13:46] <sc-rm> youlanda: it seems okay to me, if you do install do you then see the same pid in /var/run/openerp-server.pid as when doing ps ?
[13:47] <yolanda> let me test
[14:17] <yolanda> sc-rm, pid is the same in /var/run/openerp-server.pid as the ps
[14:22] <al-maisan> Can I use environment variables in environments.yaml? E.g. for secret keys?
[14:22] <yolanda> sc-rm, but when i run the db-relation-changed hook, i see different pid in /var/run/openerp-server.pid and in ps
[14:22] <yolanda> so i'm not able to kill old process and start new
[14:27] <yolanda> sc-rm, i found some problem. I have this line in my db-relation-changed hook: service openerp-core start || service openerp-core restart
[14:27] <yolanda> when i run it, pid in ps remains the same, but pid in /var/run/openerp-server.pid changes
[14:27] <yolanda> and process isn't restarte
[14:27] <yolanda> restarted
[14:36] <avoine> yolanda: it should not be: service openerp-core start && service openerp-core restart
[14:36] <avoine> because you want to restart only if the start doesn't worked
[14:36] <yolanda> yes
[14:37] <yolanda> well, the start should not work because process should be already started by the last step
[14:37] <avoine> oh no, your right
[14:38] <avoine> my logic fail in the morning
[14:39] <yolanda> avoine, the probem i face is that when i do it, pid in ps isn't changed, but pid in /var/run/openerp-server.pid changes
[14:40] <al-maisan> hmm .. did anubody see a "ERROR Invalid SSH key" upon sudo juju status -e oneiric-aws? The bootstrap command finished successfully
[14:40] <al-maisan> anybody even
[14:40] <yolanda> sems that the process isn't restarting correctly, but if i kill process by hand and then run it, it starts to behave correctly, and also starts/stops correctly
[14:41] <marcoceppi> al-maisan: do you have either an id_rsa.pub or id_dsa.pub in your .ssh folder?
[14:41] <avoine> yolanda: maybe a permission problem
[14:41] <al-maisan> marcoceppi: I have a symbolic link as follows: " id_rsa.pub -> juju_rsa.pub"
[14:41] <al-maisan> in ~/.ssh
[14:42] <yolanda> avoine, the process is running as openerp user, perhaps is that?
[14:42] <yolanda> but it's the same also if i run as root
[14:42] <marcoceppi> al-maisan: that error is usually indicative of your public key not be copyied to the bootstrap
[14:42] <avoine> yolanda: if it's an upstart script it should not be a problem
[14:43] <al-maisan> marcoceppi: removed the symbolic links and renamed the files, trying again
[14:43] <yolanda> yes it is
[14:43] <marcoceppi> al-maisan: if it works, what you can do then is add just juju_rsa.pub to authorized-keys in the stanza if you wish to segregate it from your standard id_rsa
[14:44] <avoine> yolanda: have you try  start openerp-core || restart openerp-core just in case
[14:44] <al-maisan> marcoceppi: will try
[14:45] <yolanda> avoine, unknown job
[14:45] <avoine> hum
[14:46] <al-maisan> hmm .. marcoceppi .. made no difference .. still getting "ERROR Invalid SSH key"
[14:46] <marcoceppi> al-maisan: are you using the juju PPA?
[14:46] <al-maisan> I am on 12.04 and using the juju package
[14:47] <al-maisan> marcoceppi: I also get this: http://pastebin.ubuntu.com/924951/
[14:47] <al-maisan> is that normal?
[14:48] <marcoceppi> al-maisan: yes
[14:52] <al-maisan> hmm .. no luck .. I get the "ERROR Invalid SSH key" no matter what I try
[14:53] <al-maisan> .. and I am supposed to demo this in 2 hours :-P
[14:55] <al-maisan> marcoceppi: I see that jdstrand had a similar problem http://irclogs.ubuntu.com/2012/03/22/%23juju.txt
[14:55] <marcoceppi> al-maisan: can you log in to ec2 get the address for the bootstrap and try to ssh -vv ubuntu@ec2url ?
[14:55] <al-maisan> will try
[14:56] <al-maisan> debug1: connect to address <IP_ADDRESS> port 22: Connection refused
[14:57] <marcoceppi> al-maisan: that looks like a bug, but it might already be fixed in the PPA
[14:58] <al-maisan> I am running Version: 0.5+bzr504-0ubuntu1
[14:58] <al-maisan> should I install from the PPA?
[14:58] <marcoceppi> Try the ppa, and add "origin: ppa" to the environments stanza you're using
[14:58] <hazmat> al-maisan, can you pastebin the console output from the instance?
[14:58] <marcoceppi> *in the interest of getting it ready for your demo*
[14:59] <al-maisan> I try "ec2-get-console-output i-84af18e3"
[14:59] <al-maisan> Only getting:
[14:59] <al-maisan> i-84af18e3
[14:59] <al-maisan> 2012-04-11T14:59:12+0000
[14:59] <al-maisan> quietsch ~ $
[15:00] <al-maisan> ignore the last line please
[15:01] <al-maisan> OK .. upgraded to 0.5+bzr519-1juju5~precise1
[15:01] <marcoceppi> al-maisan: make sure to update your environments.yaml file to use ppa as well
[15:01] <al-maisan> yup
[15:13] <yagey> monring.  is there a way to juju ssh into the bootstrap host?   I apparently need to run some lxc apt updates
[15:13] <marcoceppi> yagey: juju ssh 0
[15:14] <al-maisan> marcoceppi: when I try to connect to the instance from the aws web page it says: "Instance is not associated with a Key Pair. "
[15:14] <yagey> that's what I hoped.  ^Cyagey@yagey-VirtualBox:/tmp$ juju ssh 0 2012-04-11 08:13:51,250 INFO Connecting to machine 0 at localhost ssh: connect to host localhost port 22: Connection refused
[15:15] <al-maisan> marcoceppi: "juju ssh 0" gets me into  the aws instance..
[15:15] <marcoceppi> al-maisan: does juju status work?
[15:16] <al-maisan> yes!
[15:16] <al-maisan> now it works
[15:16] <marcoceppi> al-maisan: success! you should be good to go for your demo
[15:16] <al-maisan> yeah !!
[15:16] <marcoceppi> yagey: have you restarted since the last time you tried to connect?
[15:16] <al-maisan> marcoceppi: thanks for your help!
[15:17] <yagey> rebooted? I'm using lxc, won't that kill the bootstrap instance?
[15:19] <marcoceppi> yagey: it will, I was just making sure you haven't
[15:19] <al-maisan> marcoceppi: I think I know what went wrong all the time: I was using *sudo* with juju all the time :-P
[15:20] <marcoceppi> al-maisan: ah! that would probably be the reason, good to know it wasn't a bug *bug* :)
[15:20] <al-maisan> yeah .. sorry for the noise :-/
[15:22] <yagey> my mongo install is failing with: 2012-04-11 08:09:56,966 Machine:0: twisted ERROR: The following packages have unmet dependencies: 2012-04-11 08:09:56,966 Machine:0: twisted ERROR:  ubuntu-minimal : Depends: netcat-openbsd but it is not going to be installed - any suggestions  please?
[15:39] <yagey> how about this one? juju deploy tomcat7 Invalid options specification: options.multicast.type: expected 'string', got 'boolean' 2012-04-11 08:39:14,215 ERROR Invalid options specification: options.multicast.type: expected 'string', got 'boolean'
[15:44] <marcoceppi> yagey: one of your charms isn't updated properly.
[15:44] <marcoceppi> Or the tomcat7 isn't updated. Let me check it
[15:46] <marcoceppi> Interesting, which version of juju are you using yagey?
[15:49] <yagey> whichever apt-get installed
[15:50] <yagey> how can I tell?
[15:52] <marcoceppi> dpkg -l | grep juju
[15:52] <yagey> dpkg -l | grep juju ii  ensemble                               0.5+bzr398-0ubuntu1                     transition package for rename to juju ii  juju                                   0.5+bzr398-0ubuntu1                     next generation service orchestration system
[15:55] <marcoceppi> that's a pretty old version of juju, I don't think it has the updated types since boolean was added later
[15:55] <marcoceppi> which is why it's saying expected string when it got boolean for the multicast configuration option in tomcat7
[15:56] <yagey> ok.  upgrade from the ppa?
[15:56] <marcoceppi> upgrading juju from that version to latest will likely break your current deployment though
[15:56] <marcoceppi> so if you're okay with re-boostrapping then yes
[16:33] <imbrandon> SpamapS: ok so you have a conf file in /etc , you change a value of that conf , should you not place the whole tested conf in the charm vs potentially untested conf with sed vaules changed after install when the maintainer of a package changes values
[16:35] <imbrandon> like the example given is 8 months from now the maintainer changes a default value, i would think just as in package management you would not want that default value altomaticly propigated to the charm untill its been tested against your charm
[16:36] <imbrandon> ( or anyones feedback )
[16:36] <marcoceppi> dropping a configuration file from 8 months in the past against an updated package is just as reckless
[16:36] <imbrandon> no, not if there is no abi change
[16:36] <marcoceppi> with a greater chance for breakage as it does not account for changes to the package
[16:37] <imbrandon> much less chance, its been tested, the latter way has not, thus less
[16:42] <imbrandon> if i have a config with show-errors off even if thats the default, then i know errors are off, if the maintainer changes that default to on, then errors are shown in my charm and it is then broken imho
[16:42] <imbrandon> if i have a known state for the software in the charm, not the full system, but what your provinding then you should own it all
[16:43] <imbrandon> not the package mantainer
[16:44] <marcoceppi> imbrandon: if you know you always need show-errors off then you should make sure it's set via the install hook
[16:44] <imbrandon> sure, and i do as well as every other value
[16:44] <imbrandon> by the whole conf
[16:44] <imbrandon> known state
[16:44] <marcoceppi> won't scale, and does not smell like a best practice to me
[16:44] <imbrandon> it scales every day
[16:44] <imbrandon> its called debian packageing
[16:45] <imbrandon> it works the same way
[16:45] <imbrandon> damn near every deb drops their config in place
[16:46] <imbrandon> for much the same reason
[16:46] <imbrandon> like i said if thats the default now, i cannot garentee its the default alwys
[16:46] <imbrandon> just as you point out
[16:46] <imbrandon> so i need to make sure by setting all values
[16:48] <imbrandon> thats why you get the little popup when debconf see's changes to files in /etc
[17:13] <hazmat> there's a reason that charms have series in their qualified name
[17:29] <imbrandon> hazmat: sure thats holds up if all the software is installed via the package mgmt sysxtem and not git or gotdeb or src :)
[17:45] <SpamapS> imbrandon: for my oney, you store the whole config in the charm
[17:46] <SpamapS> and for my money toocurse you high latency
[19:29] <_mup_> txzookeeper/managed-watch-and-ephemeral r57 committed by<EMAIL_ADDRESS>[19:29] <_mup_> session renewal notification, don't track eph sequence nodes, speling comments from review
[19:35] <_mup_> txzookeeper/managed-watch-and-ephemeral r58 committed by<EMAIL_ADDRESS>[19:35] <_mup_> use a separate container node for the no track ephemeral test
[19:37] <_mup_> txzookeeper/trunk r47 committed by<EMAIL_ADDRESS>[19:37] <_mup_> merge managed-watch-and-ephemeral a new auto reconnecting client that recreates presence nodes and triggers watch handlers on session expiration [r=fwereade,jimbaker]
[19:49] <hazmat> m_3, ping
[19:50] <m_3> hazmat: pong
[19:50] <hazmat> m_3, i just saw r28 on charmrunner.. why did the relation check need to be disabled?
[19:50] <hazmat> that's sort of the whole point..
[19:55] <m_3> hazmat: I'll re-enable it wrt the new schema once environments are working (lp:~mark-mims/charmrunner/with-environment)
[19:56] <m_3> hazmat: it was choking on status
[19:58] <hazmat> m_3,  on the new status?
[20:12] <m_3> hazmat: yup
[20:12] <m_3> sorry... latency probs atm
[20:13] <m_3> hazmat: there's no relation state there if the relation's good... only on fail
[20:13] <m_3> hazmat: not a hard change, just in the way at the time
[20:13] <hazmat> m_3,  right but that seems orthognal to the env stuff
[20:13] <hazmat> k
[20:14] <m_3> yup... only related by the serial processing queue :)
[20:56] <hazmat> m_3, if you use go i'm sure you could do it in parallel ;-)
[20:56] <m_3> :)
[20:57] <m_3> need go for wetware
[23:46] <m_3> whoohoo!... charm in ec2 is testing charms in ec2... not quite automated yet
[23:47] <m_3> gotta probably write a separate zombie killer script to clean up if there are accidental danglers
[23:57] <SpamapS> m_3: and maybe use a limited access key that can only spawn a few machines? ;)
[23:57] <m_3> SpamapS: unhuh
[23:57] <SpamapS> m_3: I'd hate for the graph runner to get crazy with the cheeze whiz and cost you $500 ;)
[23:57] <SpamapS> s/you/somebody/
[23:57] <SpamapS> cripes
[23:58] <SpamapS> precise is changing faster now than it has all cycle
[23:58] <SpamapS> every day I sbuild-update and get 15 packages in the base install
[23:58] <m_3> gotta wait until I get a fatter pipe to update


[09:26] <imamcereyan> join
[09:26] <imamcereyan> hello
[11:08] <Guest73788> hey, pretty new to xubuntu and linux in general, i havent been able to figure out how to fix the issue of my dual monitor setup always mirroring the secondary monitor whenever i turn my monitors on.. any clues?
[11:25] <makenomistake> hello


[02:04] -queuebot:#edubuntu- Builds: Edubuntu Desktop amd64 [Mantic Daily] has been updated (20230511)


[00:00] <tsimonq2> lynorian: YAY
[00:07] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Xenial 16.04.2] has been marked as ready
[00:07] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop i386 [Xenial 16.04.2] has been marked as ready
[17:07] <flexiondotorg> wxl tsimonq2 I've published 16.04.2 images of Lubuntu for Pi 2 and 3.
[17:07] <tsimonq2> flexiondotorg: Excellent :)
[17:07] <wxl> yay thanks flexiondotorg :)
[17:07] <tsimonq2> Thanks :)
[17:08] <tsimonq2> wxl: Mornin' :)
[17:08] <wxl> oh hai
[17:09] <tsimonq2> wxl: How are ya?
[17:10] <wxl> tsimonq2: not too bad. been going crazy on that ubiquity bug.
[17:12] <wxl> tsimonq2: needless to say, it looks like it's not actually a bug.
[17:13] <wxl> tsimonq2: what you up to?
[17:14] <wxl> flexiondotorg: for your edification, i refer to http://launchpad.net/bugs/1663298 since it was filed against MATE on the tracker
[17:16] <tsimonq2> wxl: Oh ok, so I don't have to worry?
[17:17] <wxl> tsimonq2: looks like it.
[17:17] <wxl> tsimonq2: one of the problems was someone trying to do an auto-resize with an encrypted LVM partition. ubiquity can't handle that. file that in the memory banks.
[17:19] <wxl> tsimonq2: the other issue was size. the Lubuntu reporter was running off an 8GB disk.
[17:19] <wxl> tsimonq2: sinstre did have their weird issue but i'm working on it.
[17:21] <flexiondotorg> wxl I saw that bug and couldn't reproduce in Ubuntu MATE.
[17:22] <wxl> flexiondotorg: if you use too small of a disk and/or try to install alongside encrypted LVM, it will fail. but it's supposed to
[17:24] <flexiondotorg> OK.
[18:48] <lynorian> OR trying to shrink an xfs partition will not work
[21:04] <lynorian> hmm zesty alternative images have not built recently.
[21:04] <lynorian> argh keep forgetting the build logs url


[07:39] <dholbach> good morning
[07:39] <bkerensa> good morning dholbach
[07:40] <dholbach> hey bkerensa
[08:44] <Rhonda> about Bug 921118, should I close it and run syncpackage instead?
[08:45] <tumbleweed> Rhonda: syncpackage can close bugs
[08:46] <Rhonda> ah, right
[08:48] <Rhonda> hmm
[08:48] <Rhonda> syncpackage: Launchpad bugs to be closed: 921118
[08:48] <Rhonda> syncpackage: Please wait for the sync to be successful before closing bugs.
[08:48] <Rhonda> Close bugs [Y|n]?
[08:48] <tumbleweed> yeah, it's less than perfect :P
[08:48] <Rhonda> Somehow that sounds like it doesnt want me to close bugs?
[08:48] <tumbleweed> launchpad 's syncing api doesn't offer to close
[08:50] <Rhonda> So will they get closed before the sync happens?
[08:54] <dholbach> I usually wait for the mail to show up, then hit "Y"
[08:55] <Rhonda> does backportpackage only work for uploading to PPAs?
[08:56] <tumbleweed> Rhonda: you have to tell it to close the bug
[08:56] <tumbleweed> Rhonda: it's up to you to say "ok close it now"
[08:56] <Rhonda> dholbach: how long does that usually take?
[08:57] <Rhonda> tumbleweed: so it wouldn't pick up LP: #1234 from the changelog automatically?
[08:57] <dholbach> Rhonda, 2-3 minutes, I think
[08:57] <tumbleweed> Rhonda: no
[08:57] <tumbleweed> oh, sorry yes
[13:01] <tumbleweed> Laney: thanks for taking this to the techboard
[13:04] <Laney> absolutely
[14:05] <highvoltage> Laney ftw.
[14:08] <Laney> highvoltage: make sure you comment or turn up to the meeting :-)
[14:10] <highvoltage> Laney: oh, I will
[14:10] <Laney> rock
[14:11] <highvoltage> Laney: backtracking on that there's no seperate 'business' release and that 'parner' is now somehow part of Ubuntu is just BS.
[14:11] <highvoltage> (but that you know)
[14:11] <Laney> the business thing is a proposed new product
[14:12] <Laney> well I think it's more than proposed actually
[14:12] <highvoltage> at least in the default sources.list it always said:
[14:12] <highvoltage> ## Uncomment the following two lines to add software from Canonical's
[14:12] <highvoltage> ## 'partner' repository.
[14:12] <highvoltage> ## This software is not part of Ubuntu, but is offered by Canonical and the
[14:12] <highvoltage> ## respective vendors as a service to Ubuntu users.
[14:12] <Laney> heh heh
[14:14] <highvoltage> Laney: actually I might even end up launching a campaign about it, I'm really worked up about it
[14:19] <geser> I hope it's easier than to teach Debian users that Debian non-free isn't part of Debian
[14:20] <tumbleweed> well yeah, from most users' point of view it is part of Ubuntu. They see Ubuntu as a Canonical product, so this is totally part of Ubuntu
[14:20] <highvoltage> yeah
[14:20] <Laney> Debian is easier, as SC#5 says that.
[14:20] <tumbleweed> yup
[14:21] <Laney> We should work with the TB in the first instance. I'm sure there's a sensible outcome to be had here (…)
[14:21] <tumbleweed> sure, and we'd all like to not see Ubuntu internal bickering in the news :)
[14:23] <highvoltage> Laney: I have a stong urge to blog about it, do you think that's ok?
[14:24] <Laney> Depends how you write it :-)
[14:35] <geser> Laney: true, but how many Debian users have really read the SC and know about #5?
[14:37] <Laney> At least it is there to point people at, in a founding document
[14:41] <Laney> i.e. it is unquestionable in that sense
[18:07] <Q-FUNK> howdy.  I seem to get warnings from CDBS' list-missing since I split one library into foo2 and foo-common, yet debc shows that the files correctly installed in foo-dev as intended.
[18:08] <Q-FUNK> would anyone happen to know what causes list-missing to complain, even though everything was correctly installed?
[19:26] <jtaylor> yey the lp ppa build queue is so long my daily builds are starting to queue up :O
[19:27] <ajmitch> you're at the point where you've got more than 1 day of builds in the queue?
[19:43] <micahg> wow, PPA queue is longer than PowerPC now
[20:26] <l3on> Hey.. someone can open bug 629246 for oneiric/maverick/natty ?
[20:40] <TiMiDo> hey guys
[20:40] <TiMiDo> how is everyone doing. here
[20:46] <roaksoax> 9/win 3
[21:38] <koolhead17> hi all
[21:55] <TiMiDo> hi koolhead17
[21:57] <koolhead17> hi TiMiDo
[22:26] <TiMiDo> hi koolhead17
[22:26]  * koolhead17 reading up on merging
[22:28] <TiMiDo> nice I'm uploading some patches to upload,
[22:28] <TiMiDo> to see if that will get rid of the bug,,
[22:52] <astraljava> Hey Masters! Are packages synced from unstable still? Do I need to file a request for one?
[22:53] <ajmitch> they've been synced from testing up until a couple of weeks ago, so a sync request is needed for anything newer
[22:54] <ajmitch> or merge if there are changes in ubuntu
[22:54] <astraljava> ajmitch: Thanks! I just noticed there is an update to audacious in unstable, and we're seeding that. But it FTBFS on some archs, so I will wait a little while to see if there are fixes. Thanks!
[23:08] <micahg> l3on: I don't know that dropping hal in the stable releases is a good SRU
[23:09] <l3on> mmmmmmmmmmm
[23:10] <l3on> well, in oneiric works great
[23:10] <jtaylor> tumbleweed: you're in the motu relase team right?
[23:10] <micahg> l3on: works, yes, but that might regress functionality
[23:11] <l3on> not really, wait, there is a old debian bug ...
[23:12] <micahg> l3on: it's perfect for precise though as hal needs to die, so syncing
[23:13] <l3on> micahg, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615210
[23:13] <l3on> seems that hal is not necessary
[23:14] <jtaylor> tumbleweed: ipython upstream is discussing bugfix release or new upstream mid march if it would still got into precise
[23:14] <micahg> l3on: right, well, it's not used very much as all now, but in the stable releases, the further back you go, the more it's used
[23:15] <jtaylor> is it still realistic to get a freeze exception based on this rational: core functionallty known from < 12.04 is not changed much, we don't want to keep 0.12 due to bugs and interface change in new parts of 0.13?
[23:18] <l3on> micahg, so, what you suggest ? :)
[23:20] <micahg> l3on: no rdeps, so adding hal as a dependency seems safest
[23:21] <micahg> l3on: but feel free to discuss with an SRU team member, I"ll give you the bug tasks since you're working onthis
[23:22] <l3on> ok, thanks micahg :)