[00:50] <Riddell> slangasek: are we aiming for a midday-ish UK time release?
[02:04] <bentkus> what the facebook
[02:04] <bentkus> why the facebook did you kick me?
[02:09] <nhandler> bentkus: Wrong channel
[02:11] <bentkus> Yeah
[02:11] <bentkus> i can see
[02:11] <bentkus> but i can pay you with beers if you tell me the exact release date
[02:13] <nhandler> bentkus: Date is April 29th. Now let's move back to -party
[02:15] <bentkus> -party mode yoohoo
[02:15] <bentkus> toobad its laread 3 in the night at here
[02:15] <bentkus> and its my last beer
[02:15] <bentkus> :(
[02:45] <ScottK> lool: I saw the bugmail.  I think closing it was the right thing to do (re 290153)
[04:22]  * lamont sleeps
[04:22] <lamont> meh.  ECHNA
[05:29] <slangasek> Riddell: early afternoon
[05:30] <slangasek> lool: errors on console is not what I was going to release note for 470776
[05:30] <slangasek> lool: my understanding of the remaining bug is that mountall is unhappy if you list a bind mount in fstab whose source is a symlink
[05:31] <pitti> Good morning
[05:31] <wgrant> slangasek: Hi. Are you planning to do the usual #ubuntu-release-party announcement this time, or shall we make other plans?
[05:32]  * slangasek waves
[05:32] <slangasek> wgrant: I was planning to do it
[05:33] <slangasek> I was also planning to do it last time, before someone stole the spotlight from me :)
[05:33] <wgrant> Yeah.
[05:33] <wgrant> ubuntu/member/* don't have access this time, so it's less likely.
[05:33] <wgrant> I don't want that disaster repeated :)
[05:36] <slangasek> :-)
[05:41] <ajmitch> talk about spoiling all the fun
[05:43] <ajmitch> we should thank whoever added the index.html to the .pool dir, that'll save a bit of bandwidth :)
[05:44] <wgrant> It's been there for a couple of releases now.
[05:44] <wgrant> Still doesn't stop them much...
[05:44] <ajmitch> It has? I guess I hadn't noticed
[05:54] <pitti> slangasek: do you think I can already start accepting some SRUs?
[05:54] <pitti> slangasek: if you want me, I can set one buildd for each arch to manual, so that we have them on standby in case we need an urgent lucid final build?
[05:57] <slangasek> pitti: accepting SRUs> yes, that would be good
[06:00] <pitti> slangasek: yellow is on manual now, but all the i386 buildds time out when I try to switch them
[06:01] <wgrant> pitti: A timeout timeout, or "Please try again" timeout without an OOPS number?
[06:01] <pitti> but oh well, most packages there are really small
[06:01] <pitti> wgrant: trying again for the exact text
[06:06] <Keybuk> slangasek: I have a last minute urgent mountall upload, is it too late to respin?
[06:07] <pitti> wgrant: no oops, just a "Sorry, there was a problem connecting to the Launchpad server."
[06:07] <wgrant> pitti: Aarrrrrgh.
[06:07] <wgrant> That is impossible.
[06:07] <wgrant> (it's the only page on which it happens, and it shouldn't be possible)
[06:08] <pitti> just that it happened four times today, and about a week ago when I desperately tried to reserve an amd64 builder
[06:09] <slangasek> Keybuk: ...
[06:10] <Keybuk> it fixes bug #571549
[06:11]  * slangasek snorts
[06:12] <slangasek> Keybuk: I don't think we need to respin for that, release notes should be fine
[06:12] <ajmitch> Keybuk: having a nice evil day giving people heart attacks?
[06:13] <Keybuk> ajmitch: since I can't do it in person ... :-(
[06:44] <slangasek> lool: oh, it seems 470776 may not be the bug I was thinking of; there was one where someone mentioned problems w/ bind mounts, and this appears not to be it
[07:25] <ara> morning all!
[07:36]  * slangasek waves
[08:07] <ara> hey slangasek
[08:07] <ara> slangasek, one quick question, are we going to have "home" webpages for every search engine in mozilla?
[08:09] <slangasek> ara: as far as I know, there's just one home page that points to the default search engine?
[08:09] <ara> slangasek, If I select a search engine other than Google or Yahoo and close firefox, when I restart firefox I get a 404
[08:12] <slangasek> oh, is *that* what causes that bug
[08:13] <slangasek> bug #557640?
[08:14] <ara> slangasek, yes, it is not a server not found, it is just a plain old 404
[08:14] <slangasek> ok
[08:14] <slangasek> I don't know how it's meant to work, but that's probably the bug report to track it on
[08:14] <ara> slangasek, ok, I'll comment there and will talk to the design guys
[08:17] <elmo>
[08:17] <elmo> wait
[08:17]  * ara waits
[08:19] <Jeeves_> morning
[08:20] <elmo> sorry, that's our bug
[08:20] <elmo> I'll get it fixed
[08:22] <elmo> we dropped some rewrites from start.ubuntu.com because we were running into apache mod rewrite bugs (sic) and I didn't realise firefox was sending arbitarty URLs to start.ubuntu.com for different search engines
[08:25] <ara> elmo, OK, thanks. Glad to hear you're working on it
[08:35] <ogra> wow, getting up and finding 100 new bugmails in my inbox ... must be release day
[08:37] <ara> morning ogra, and happy release day :)
[08:37] <ogra> same to you :)
[08:37]  * ogra hugs ara
[08:38]  * ara hugs ogra back
[08:40] <pitti> ogra: and it's not just the usual "branch linked" spam? :-)
[08:40] <ogra> nope :)
[08:40]  * pitti gets some 50 of those every day
[08:40] <ogra> i rarely have over 60 when i get up ... and probably another 60 during the day
[08:41] <pitti> ogra: ah, so it's 40 extra "OMGhowcanyounotfixthisbyrelease" comments :)
[08:41] <ogra> yeah
[08:41] <ogra> lovely how much testing we get the last day
[08:42] <ara> yes, yes
[08:42] <ogra> we should make secret release schedules and just spread rumours about the actual release date that are 3 weeks ahead
[08:42] <ara> I *love* that kind of comments
[08:42] <pitti> ogra: no, before, so that we can actually fix stuff still
[08:43] <ogra> thats what i meant :)
[08:43] <ogra> grammar skew :)
[08:43] <ajmitch> no matter what you do, someone will complain about it
[08:44]  * pitti suggests redirecting those folks to testing -proposed and giving feedback
[08:48]  * hyperair got a particularly large amount of spam from the tooltip bug
[08:53] <Jeeves_> btw: http://lvsd.lucid.bit.nl/stats/
[08:55] <pitti> yay statistics!
[08:56] <ogra> slick statistics even
[08:57] <Jeeves_> :)
[09:09] <elmo> ara: should be better now, can you confirm?
[09:13] <pitti> slangasek: FTR, -proposed queue is now processed, except for the four that I uploaded, empathy (had a question on the bug), and poppler (OMGbigdiff, needs more time/discussion to review)
[09:28] <ev> mvo: just a heads up, we may need you to mkdir ubiquity; touch ubiquity/10.04-update-available on changelogs.ubuntu.com in a bit
[09:31] <mvo> ev: ok
[09:31] <mvo> ev: I stand ready
[09:32] <ev> :) thanks
[09:33]  * ara checks
[09:34] <ara> elmo, confirmed
[09:34] <ara> elmo, thanks
[09:34] <mvo> ev: is that so that it picks the right release notes text?
[09:35] <ev> mvo: it's a hint to the installer that a new version is available, so it will show an update button
[09:35] <mvo> ev: aha, so that the installer can update itself? nice, I noticed that this got landed early this cycle
[09:36] <ev> mvo: indeed!  sabdfl asked us towards the end of the cycle to only show the option when an internet connection is available and an update is actually available, so we've implemented that.
[09:37]  * mvo nods
[10:32] <slangasek> so it seems we're going to do a last-minute respin of Ubuntu desktop CDs only, with a single lucid-updates change, to address the worst of bug #570765 in the limited time available
[10:33] <slangasek> pitti: ^^ in particular, this means do NOT promote anything else to -updates :)
[10:33] <pitti> slangasek: understood; there's just one candidate anyway, but I don't like -updates promotion before release
[10:33] <slangasek> right
[10:33] <slangasek> with good reason :-)
[10:34] <pitti> slangasek: does that require an upload? or just cd image build changes?
[10:35] <slangasek> pitti: migration-assistant, ubiquity are in progress
[10:38] <pitti> slangasek: want me to review m-a or are you doing it?
[10:40] <ev> spot check please - http://paste.ubuntu.com/424497/
[10:40] <slangasek> pitti: doing
[10:41] <pitti> yellow is standing by, will bump build score and reenable it on your command
[10:41] <slangasek> migration-assistant accepted
[10:42] <pitti> c'mon yellow, grab it
[10:42] <pitti> fodder for you
[10:42] <pitti> there
[10:43] <jarnos> Hello, will https://wiki.ubuntu.com/LucidLynx/ReleaseNotes and http://www.ubuntu.com/getubuntu/releasenotes/1004 have the same notes today?
[10:45] <pitti> slangasek: hm, I don't think we'll be able to move them to -updates before a publisher run, though
[10:45] <pitti> i. e. it'll take two publisher runs for them to get into -updates?
[10:45] <wgrant> You can do it quicker if you get Soyuz approval to run process-accepted manually.
[10:45] <wgrant> That takes seconds, and will mean you can immediately promote.
[10:45] <ara> slangasek, we will be respining only CDs or DVDs as well?
[10:46] <pitti> slangasek: m-a built on i386/amd64
[10:46] <slangasek> ara: we will be respinning DVDs, but have not yet made a hard decision to take the new ones
[10:46] <jarnos> Is it deliberate, that they have nothing about nouveu drivers? What is the role of https://wiki.ubuntu.com/LucidLynx/TechnicalOverview ? cjwatson
[10:47] <cjwatson> wgrant: Soyuz approval?  the Ubuntu archive team does manual stuff like this on production regularly
[10:47] <cjwatson> but in any case it's easier to just upload directly to -updates
[10:47] <jarnos> slangasek: ?
[10:47] <slangasek> pitti: shortcut: ubiquity is going to -updates now, and that's the only one that has to go on the livefs
[10:47] <cjwatson> jarnos: please raise bug tasks on the ubuntu-release-notes project for anythng you think should be added
[10:47] <pitti> cjwatson: *nod* but m-a was uploaded to -proposed
[10:47] <pitti> slangasek: ah, because it includes source, right
[10:47] <cjwatson> pitti: it doesn't really matter, it's only the source
[10:48] <wgrant> Oh, OK.
[10:48] <pitti> I have yellow on standby again, once ubiquity hits
[10:48] <pitti> ubiquity won't be fast enough to catch the :03 publisher; shall I disable it, or did someone already?
[10:48] <slangasek> already did
[10:49] <ev> http://paste.ubuntu.com/424502/
[10:51] <cjwatson> accepted
[10:52] <slangasek> amd64: "starting in 1 hour"?
[10:52] <pitti> build score bumped, yellow back on auto
[10:53] <stgraber> slangasek: are you going to respin the derivatives as well for that grub issue ?
[10:53] <pitti> argh
[10:53] <slangasek> stgraber: please hold, asking this question
[10:53] <pitti> wgrant: yellow manual/auto worked until five minutes again, and now it's timing out, arrrgh!
[10:54] <pitti> wgrant: do you have the powers of reenabling it with better tools than the webui?
[10:54] <wgrant> pitti: You can poke a LOSA to use SQL, but that's about it.
[10:54] <wgrant> No API yet :(
[10:54] <pitti> ah, worked now
[10:54] <wgrant> A LOSA or maybe a lamont. Not sure if he can do it.
[10:54] <pitti> ubiquity building
[10:54] <slangasek> stgraber: you have the option
[10:54] <pitti> dear launchpad, please keep working just a little longer
[10:54] <lool> it's building now
[10:55] <lamont> g'morning, btw
[10:55] <lamont> or morning at least
[10:55] <stgraber> slangasek: ok, then please respin edubuntu dvd. I have a very decent internet here so I should be able to re-validate both DVDs in ~2 hours after they are on cdimage.
[10:56] <pitti> good morning lamont, how are you?
[10:56] <jarnos> cjwatson: ok, but why there are different release notes at wiki and www.ubuntu.com?
[10:56] <lamont> pitti: the timeout setting manual/auto seems to be related to launchpad being busy holding the door closed on the buildd manager, or at least us
[10:56] <lamont> pitti: doing well
[10:56] <slangasek> stgraber: we have a hardlinked copy of the current tree; we'll respin all the affected derivatives regardless, and you'll have the option of taking the current one with the bug or the new one if you're happy doing the extra validation
[10:57] <stgraber> slangasek: ok
[10:58] <slangasek> stgraber: if you go with revalidation, I expect we're probably going to have to push the release button for the other flavors before you've completed validation, but we can adjust the announcements accordingly, if that's ok with you
[10:58] <cjwatson> jarnos: because they're copied over to www.ubuntu.com by our webmaster at release.  Don't worry, they'll be synced
[11:00] <jarnos> cjwatson: I am wondering, which one is better to be linked in Xubuntu's release notes. Xubuntu's final notes will be at https://wiki.ubuntu.com/Xubuntu/LucidLynx/Final Well, I guess I could choose any.
[11:02] <stgraber> slangasek: I'm guessing you have to release before and of day London time or is that going to happen even before that ?
[11:02] <Riddell> GrueMaster: were you able to test the Kubuntu Netbook ARM images?
[11:02] <cjwatson> jarnos: I think wiki linking to wiki would be fine
[11:02] <cjwatson> but I don't think it matters too much either way
[11:02] <stgraber> slangasek: otherwise, yes we can update the announcements to mention that due to that m-a bug we'll be releasing as soon as testing is over
[11:03] <cjwatson> stgraber: the stuff on releases.ubuntu.com does; things on cdimage.ubuntu.com can delay a little bit if necessary
[11:03] <Vge> so it will be released some time today? sorry, im little slow
[11:03] <stgraber> cjwatson: ok
[11:04] <cjwatson> Vge: that's still the plan
[11:04] <stgraber> slangasek: any kind of ETA on when we'd get the new images for testing ?
[11:04] <cjwatson> Vge: but please don't do the "are we there yet" thing in this channel :-)
[11:04] <stgraber> (as in edubuntu)
[11:07] <slangasek> stgraber: the Ubuntu release is expected to be before end of day London time, yes.  I don't have an ETA yet on edubuntu, I will see what I can do to expedite
[11:10] <stgraber> ok, thanks
[11:12] <pitti> slangasek: I guess it's safe now to reject the wine1.0 upload?
[11:15] <lamont> slangasek: would a second i386 livefs buildd help, or just unduly complicate things?
[11:18] <slangasek> lamont: I've asked elmo for a better king, amd64 is our bottleneck
[11:18] <ev> http://testcases.qa.ubuntu.com/Install/DesktopResize updated
[11:24] <pitti> slangasek: ubiquity built on i386/amd64; do we need to wait for armel for this run?
[11:24]  * pitti supposes not
[11:24] <pitti> armel will still take a while to compute that keyboard map
[11:24] <slangasek> pitti: no - confirming build status and starting the publisher
[11:24] <slangasek> confirmed
[11:24] <slangasek> publisher running
[11:24] <cjwatson> armel is unaffected because it doesn't have grub
[11:36] <elmo> 11:32 < elmo> seriously, people
[11:36] <elmo> 11:32 < elmo> a hardy kernel release TODAY?
[11:36] <elmo> (since smb claims it wasn't them that moved it from -proposed)
[11:37] <pitti> hm, I discussed it with smb on Monday, and he said they were good to move
[11:37] <elmo> pitti: yeah, it's more the timing relative to lucid
[11:37] <smb> pitti, I thought we discussed on last Friday to be moved this Monday. ;-)
[11:38] <pitti> smb: right, I forgot; I remembered again when I cleaned up SRUs today
[11:38] <pitti> oh, you mean mirror bandwidth-wise?
[11:38] <pitti> argh, sorry about that
[11:38] <elmo> slangasek: new-king is syncing, FWIW, but I hadn't quite counted on the n million files from chroots
[11:39] <elmo> slangasek: if at any point you want me to abort, and make king functional again, just let me know
[11:39] <slangasek> elmo: ok - what's the ETA?
[11:40] <elmo> slangasek: way too long, i suspect
[11:40] <elmo> based on a very poor sampling, it looks like at least an hour
[11:41] <elmo> slangasek: we could of course rebuild the chroots on new-king, but that's the whole 'introducing more variables' thing I was trying to avoid
[11:41] <ux2> an hour to the release? that's ok for me
[11:41] <cjwatson> ux2: huh?
[11:42] <cjwatson> ux2: please don't jump into the middle of conversation here
[11:42] <ux2> please don't be an asshole, you stupid ubuntuer
[11:43] <Jeeves_> hmm :)
[11:44] <slangasek> elmo: I can slot ubuntu-netbook, which is i386-only, at the front; that would buy us some more time to let king finish syncing, and would still be a net win for build time
[11:44] <cjwatson> I'm tempted to moderate this channel for the duration
[11:44] <slangasek> elmo: I expect the king.buildd respin to save us at least 3h on the livefs mastering
[11:44] <elmo> slangasek: ok
[11:45] <slangasek> (since we're doing opportunistic respins of all affected flavors)
[11:52] <cjwatson> voiced core-devs, testers, release team folks, etc. - please /msg me if you need to speak and don't have +v
[11:54] <ogra> i assume armel wont need a rebuild for the grub issue, right ?
[11:55] <slangasek> it will not
[11:55] <ogra> ok ... no install stress tests for me then :)
[11:57] <stgraber> ogra: would have been weird as AFAIK you don't have either grub, m-a or windows on armel ;)
[11:58] <ogra> yeah
[11:58] <ogra> just wanted to be sure if ubiquity might need any regression testing or so
[11:59] <cjwatson> stgraber: fwiw there's nothing windows-specific here
[12:01] <ara> cjwatson, in a ubuntu-ubuntu installation, what m-a is supposed to migrate apart of firefox bookmarks?
[12:02] <cjwatson> ev: ^-
[12:03] <ev> ara: internet explorer bookmarks, "My Documents", music, AOL IM, Yahoo IM,  "My Pictures", the set wallpaper, opera bookmarks, ...
[12:03] <ara> ev, in ubuntu / ubuntu ones, I was asking
[12:04] <ev> oh
[12:04] <ev> pidgin
[12:04] <ev> sorry about that
[12:04] <ara> ev, ok, thanks!
[12:11] <cjwatson> blink, what happened to the moderation here
[12:12] <lamont> cjwatson: they have voice...
[12:12] <cjwatson> no they don't
[12:12] <cjwatson> kraut,Kilos: please leave us to deal with things at the moment rather than asking
[12:12] <ara> cjwatson, I didn't see anything
[12:12] <cjwatson> ah!  only moderators see it
[12:12] <lamont> ah.. I didn't see anything from him
[12:12] <cjwatson> er, ops
[12:12] <lamont> heh
[12:13] <Laney> that's one of the chanmodes
[12:20] <elmo> FINALLY
[12:21] <ogra> oh SIGH !!!!
[12:21] <ogra> http://www.chip.de/news/Ubuntu-10.04-Lucid-Lynx-zum-Download_42676253.html
[12:21] <ogra> they mirrored yesterdays image, renamed it and offer it as 10.04 already
[12:22] <ogra> silly world
[12:22] <slangasek> elmo, lamont: lucid-updates Packages.gz doesn't seem to be making it to syncproxy
[12:22] <wgrant> Well, historically that has been, well, fine. Hopefully this late respin will cause them to stop that for a release or two :)
[12:23] <stgraber> ogra: file on their server seems to be RC. clicking on download gets me to ubuntu-10.04-rc-...
[12:23] <ogra> wgrant, i doubt that, they want the clicks ...
[12:23] <cjwatson> ogra: can you contact them?
[12:23] <slangasek> elmo, lamont: the *binaries* have mirrored; the Packages.gz has not
[12:24]  * ogra tries to find a mailto link or something
[12:25] <cjwatson> there's a "feedback" link at the bottom
[12:25] <lamont> slangasek: looking
[12:27] <slangasek> lamont: thanks
[12:27] <slangasek> lamont: aha, looks like things are moving now, thanks
[12:27] <lamont> yeah - was just going to say..  I see 2010-04-29 11:38 for a timestamp
[12:28] <lamont> echo "$(date -R): Waiting $DELAY seconds before triggering external mirrors."
[12:28] <lamont> sleep $DELAY
[12:28] <lamont> and DELAY=600
[12:29] <lamont> slangasek: and when I first logged in, there was a sleep 600 in the ps output...
[12:29] <slangasek> hum, ok
[12:29] <elmo> slangasek: what exactly were you seeing?
[12:29] <elmo> as in how were you checking syncproxy?
[12:29] <elmo> AFAIK it doesn't expose http
[12:30] <slangasek> elmo: cjwatson checked it
[12:30] <lamont> ok, same questions, cjwatson:
[12:31] <cjwatson> rsync
[12:32] <cjwatson> i.e.  RSYNC_PASSWORD=blah rsync -av ouruser@syncproxy
[12:32] <cjwatson> ::ubuntu/dists/lucid-updates/
[12:33] <elmo> hmm, that's worrying
[12:33] <elmo> I saw the same sleep as lamont
[12:33] <elmo> and at that point dists/ should be synced
[12:33] <lamont> yeah
[12:34] <cjwatson> I think I can confirm that this only happens if there's something to migrate on the other OS
[12:34] <cjwatson> (however, that is still a pretty common case)
[12:35] <lamont> something to migrate?
[12:37] <ogra> cjwatson, i sent something to the author and the chief editor
[12:37] <ogra> i dont expect them to react in time though
[12:39] <cjwatson> lamont: sorry, I'm talking about bug 570765 not about syncproxy
[12:40] <lamont> cjwatson: doh.  sry
[12:41] <dholbach> I posted a comment in the forum for the chip online article too
[12:54] <elmo> so
[12:55] <ogra> cjwatson, wow, that worked well, they replied and ask me for an MD5 for final so they can be sure to offer the right image :)
[12:55] <elmo> slangasek: new king is consisently hanging when adding modules, and I've no idea why.  at this point I'm going to either have to give up or ask for some help from someone either kernel-y or udev-y
[12:56] <ogra> cjwatson, and according to dholbach the article is corrected already
[12:56] <elmo> slangasek: I've done body swaps like this before and it's usually fine except for having to remove /etc/udev/rules.d/70*peristent*net*
[12:56] <cjwatson> ogra: good
[12:56] <dholbach> ogra: it's not corrected - it's an older article - I guess that's where the other author got their information (and the links from)
[12:57] <dholbach> but somebody said he'd pass the information on
[12:57] <slangasek> elmo: oubiwann sent to get you a kernel person
[12:57] <cjwatson> ogra: if you didn't already, it might be a good idea to emphasise that they should wait for the official announcement and get the checksums and such from there
[12:58] <elmo> slangasek: thanks, it was an incredibly hard technical problem and nothing remotely resembling extremely embarassing PEBKAC
[12:59] <ogra> cjwatson, they said they'll wait for me, i'll just forward them the official announcement then
[13:04] <slangasek> elmo: can I start flinging stuff at king?
[13:12] <elmo> slangasek: sorry
[13:12] <elmo> still working, rebooting now
[13:12] <slangasek> ok
[13:12] <elmo> this is a complete clusterf#%Y^
[13:15] <elmo> ok, booted, 30 more seconds
[13:36] <elmo> this is unbelivable, so far it looks like it's going to be slower :-///
[13:36] <elmo> than old king, never mind terranova!
[13:39] <slangasek> my build time estimates are very much ballpark; none of the livefs build logs have timestamps
[13:39] <slangasek> and I don't have any in my scrollback
[13:39] <slangasek> so I can't tell if it's actually slower
[13:39] <slangasek> would there be any reasons for network contention between the livefs buildds and the archive?
[13:42] <elmo> slangasek: not enough to be relevant
[13:42]  * slangasek nods
[13:42] <elmo> Fetched 515MB in 41s (12.3MB/s)
[13:43] <elmo> while that's not snappy, I don't think it's in the slow path
[13:44] <slangasek> stgraber: ETA 1h45 for edubuntu (best guess)
[13:45] <stgraber> slangasek: ok, thanks
[13:51] <slangasek> elmo: ok, 33min for a livefs build on king
[13:51] <slangasek> that's... longer than expected
[13:51] <slangasek> but < 2x the build time on terranova
[13:51] <elmo> slangasek: crazy idea, but could it be the completely cold cache?
[13:52] <slangasek> I have no idea
[13:54] <lamont> slangasek: and not very much at all pulls bits from ftpmaster
[14:18] <cjwatson> pitti: is that you looking at NEW?  I was just reviewing adobereader-deu binaries and then they disappeared out of the queue ...
[14:18] <slangasek> pitti: you reviewed wine1.0 and it's just waiting until the end for accept, right?
[14:25] <pitti> cjwatson: I NEWed l-b-m, but I left the partner ones alone
[14:26] <pitti> slangasek: it's fine by itself, but it needs to build (30 mins on i386/amd64) before we lock down lucid
[14:27] <slangasek> pitti: yep - accepted, I'm afraid we have time
[14:27] <pitti> cjwatson: and I did that about an hour ago; I'm testing ATM, not queue-juggling
[14:27] <pitti> cjwatson: something wrong with them?
[14:27] <pitti> slangasek: heh
[14:28] <cjwatson> pitti: no, they looked fine
[14:28] <Riddell> cjwatson: I did that
[14:28] <pitti> TBH I ignored the partner packages so far, since I never quite managed to read about their process
[14:28] <Riddell> iamfuzz just asked me to review adobereader-deu
[14:44] <slangasek> ttx: have you seen the follow-up from Nathan on bug #571057?
[14:45] <ttx> slangasek: about the olcAuthzRegexp line ?
[14:46] <slangasek> ttx: yes
[14:46] <ttx> slangasek: yes, that's not covered by mathiaz's patch, wanted to ask his opinion about it. Also I'm more and more confused by my tests, each upgrade path ends up with a different conffile
[14:47] <ttx> duplicated lines
[14:47] <ttx> so to solve this cleanly we probably need to cover more cases, and do more comprehensive testing of all paths
[14:47] <slangasek> mmk
[14:47] <ttx> I'm getting uncomfortable rushing that as a 0-day SRU
[14:48]  * slangasek nods
[14:48] <stgraber>  14:48:30 up 3 days,  6:27,  1 user,  load average: 89.62, 72.15, 52.79
[14:48] <stgraber> can we get someone from IS to look at quandong ?
[14:49] <cjwatson> elmo: ^- ?
[14:51] <elmo> well
[14:51] <elmo> I can bounce apache, but I'm not sure where the actual load is coming from
[14:51] <elmo> it's not actually all that busy
[14:53] <elmo> and it's coming down on it's own
[14:56] <pitti> nice, people are jumping on testing the new ISOs like hungry cats on a mouse
[14:56] <ogra> did oyu ask them in #u-r-p ?
[14:59] <elmo> sigh, now it crashed
[14:59] <pitti> ogra: no, just by the build notification emails, I figure
[14:59] <pitti> ogra: oh, and I prodded folks in #u-desktop
[14:59] <ogra> nice
[15:00] <slangasek> ogra: anyone who asks #u-r-p for ISO testing help may find themselves stabbed at UDS
[15:00] <ogra> lol
[15:00] <ara> slangasek, has any other image been posted?
[15:00] <pitti> ogra: like "test the new images NOW, or I tell Rick how bad you are in the next evaluation" :-P
[15:00] <ogra> *grin*
[15:00] <pitti> ogra: you are on #u-r-p? I didn't dare yet
[15:00] <ogra> sure i am
[15:01] <cjwatson> twitter is enough for me ...
[15:01] <cjwatson> (also insane)
[15:01] <ogra> dont want to miss the entertainment
[15:01] <slangasek> ara: not yet; the next one up is edubuntu DVD, ETA < 1h but hard to give an exact number
[15:01] <ara> slangasek, ok, thanks!
[15:01] <ara> slangasek, what about ubuntu dvds?
[15:01] <cjwatson> those are next after edubuntu dvd
[15:07] <pitti> oh, quangdong == iso.qa?
[15:07] <slangasek> yes
[15:12] <stgraber> tracker's going to be real slow for a few seconds but should be better after
[15:13] <slangasek> ah?
[15:13] <stgraber> seems like Drupal's sessions haven't been cleaned for a while
[15:13] <slangasek> ah
[15:13] <stgraber> so it had a table containing 543509 php sessions ...
[15:13] <slangasek> is that going to log me out of the tracker, *again*?
[15:13] <stgraber> it shouldn't, I'm only dropping the sessions of anonymous users
[15:13] <slangasek> ok
[15:14] <pitti> stgraber: "FATAL: connection limit exceeded for non-superusers" -> that's because of too many sessions?
[15:14] <stgraber> pitti: yes, seems like each apache process got stuck doing SQL queries
[15:15]  * ara hugs stgraber
[15:16] <stgraber> elmo: if you are still around, could you stop apache for a few secs ? should decrease the load and make the cleanup go faster
[15:16] <pitti> it's not working right now anyway
[15:16] <slangasek> elmo: ok, newking really is faster - edubuntu i386/amd64 just completed within a minute of each other
[15:17] <slangasek> oops - within 2 minutes of each other
[15:19] <elmo> slangasek: thank goodness
[15:19] <elmo> stgraber: if I can log in, sure
[15:21] <elmo> stgraber: done
[15:21] <stgraber> elmo: good, I'll tell you as soon as the cleanup + reindex is done, shouldn't take long
[15:23] <stgraber> elmo: looks like I need your help there ;)
[15:23] <stgraber> elmo: http://paste.ubuntu.com/424628/
[15:23] <stgraber> elmo: can you run these 3 queries as the DB owner ? seems like the "db" user can't do that
[15:24] <elmo> stgraber: running
[15:24] <stgraber> after that you can restart apache
[15:26] <elmo> done
[15:28] <stgraber> doesn't seem to have improved much :(
[15:28] <dholbach> slashdot says that "it's out"
[15:28] <dholbach> a bunch of people luckily told them already that they're wrong
[15:29] <elmo> sigh
[15:29] <elmo> what else is on this box
[15:29] <wgrant> Slashdot consistently announces it hours earlier.
[15:29] <wgrant> It's incredible.
[15:30] <ara> Maverick is out. You can download it from here (random link)
[15:31] <Jeeves_> :)
[15:31] <Wooster_> Jeeves_: wassup!
[15:31] <fader_> ara: I always trust thepiratebay.org for downloading OSes
[15:35] <dholbach> ara: where? where?
[15:35] <ara> dholbach, :D
[15:36] <dholbach> which isos were rebuilt? daily-live, dvd, edubuntu?
[15:36] <dholbach> ubuntu-netbook?
[15:36] <slangasek> daily-live, netbook, edubuntu so far
[15:36] <slangasek> edubuntu ISO still finalizing
[15:37] <cjwatson> ubuntu dvd also planned, plus mythbuntu and xubuntu
[15:41] <elmo> oh for god's sake quandong
[15:42] <slangasek> edubuntu ETA: 5min
[15:43] <lamont> slangasek: just netbook-i386.iso, or also the .img files?
[15:43] <slangasek> lamont: hmm?
[15:44] <lamont> slangasek: I think that means 'no, we're not respinning the .img files'
[15:44] <slangasek> lamont: what .img files?
[15:44] <slangasek> the armel ones?
[15:44] <lamont> yeah
[15:45] <lamont> which != netbook.
[15:45] <lamont> I'm just going to go pound my head on the wall for a few minutes.
[15:45] <slangasek> it's netbook, but it's not the netbook we're looking for :)
[15:45] <lamont> well, to my defense, they do have 'netbook' in the name
[15:45] <lamont> so I'm gonna use a _soft_ wal
[15:45] <lamont> l
[15:45] <Jeeves_> :)
[15:46] <stgraber> elmo: anything else running on the same xen host as quandong ? (seems like quandong is so slow that my ssh session is completely frozen)
[15:46] <stgraber> marjo: ^
[15:47] <stgraber> cjwatson: can you +v marjo ?
[15:47] <elmo> stgraber: yes, but it's an idle guest
[15:47] <elmo> stgraber: I'm going to move quandong to  new hardware, we're just bringing it up now
[15:47] <elmo> or rather the ISO tracker to new HW
[15:47] <marjo> elmo: thx
[15:48] <dholbach> slashdot article taken down, probably temporarily
[15:53] <GrueMaster> Riddell: Sorry for not getting back to you on kde netbook on arm.  I had not had a chance to test them unfortunately.  I noticed that they are not part of the kubuntu testcases on iso.qa.ubuntu.com.
[16:07] <stgraber> slangasek: what's the version number of the new edubuntu build ? I see 20100429.1 on cdimage
[16:07] <slangasek> stgraber: that's the one
[16:08] <stgraber> great, starting to rsync then
[16:08] <stgraber> highvoltage: ^
[16:09] <slangasek> stgraber: do you know the status of quandong?
[16:12] <stgraber> slangasek: nope
[16:13] <stgraber> slangasek: last thing I know is that elmo was going to move the tracker to another box
[16:13]  * slangasek nods
[16:13] <elmo> slangasek: sorry, there isn't  a quicker fix, ng is working on it right now though
[16:13] <slangasek> elmo: just wanting to confirm that the current page load failure is expected.  Any ETA?
[16:14] <pitti> so there were two successful tests of auto-resize, and I just finished one myself on i386; both OSes (well, lucids) are in grub
[16:14] <pitti> it's a bit sad that we don't show grub by default any more for > 1 OS, but I think that's actually deliberate
[16:15] <cjwatson> ... we should
[16:15] <cjwatson> it's a bug if we don't, and not one I have reproduced in my testing thus far
[16:15] <pitti> cjwatson: that didn't fall victim to the design team specs?
[16:15]  * pitti reboots again, this time without shift
[16:15] <cjwatson> no, one of the exceptions was in the case of multi-booting
[16:16] <pitti> ah, ignore me, sorry
[16:16] <fader_> Same here -- I have definitely seen the grub selector whenever I have done a resize and had multiple installs
[16:16] <charlie-tca> It showed the menu in my entire disk install by default
[16:16] <cjwatson> pitti: worked?
[16:16] <pitti> the other one I was looking at had two kernels
[16:16] <pitti> cjwatson: yes
[16:16] <cjwatson> ah
[16:16]  * pitti gets a little confused with too many installs, sorry
[16:17] <fader_> I'd like to have the option to hide it even when multiple OSes are installed, actually :)
[16:17] <pitti> they all worked great, though \o/
[16:17] <elmo> slangasek: 30m ok?
[16:17] <slangasek> elmo: it is what it is :)
[16:17] <elmo> right
[16:17] <cjwatson> fader_: yeah, bug about that, it was kind of hard to support all the options
[16:18] <slangasek> ubuntu DVD> 64-bit livefs is built, 32-bit is a-squashin'
[16:18] <fader_> cjwatson: Ack, I understand the reasons and am just griping :)
[16:25] <slangasek> Ubuntu DVD ETA: 20min
[16:27] <highvoltage> stgraber: would that be the one dated today 15:41 (for i386)?
[16:27] <GrueMaster> Riddell: critical bug on kubuntu-netbook for armel dove.  Bug 571732.  Only on dove (not on imx51, will check omap).
[16:27] <cjwatson> that bug's private?
[16:28] <GrueMaster> it just got filed by apport.  WIll change it.
[16:28]  * Riddell waits in anticipation
[16:28] <GrueMaster> Bug 571732.
[16:29] <GrueMaster> Unfortunately, I think the armel retracer is still wonked.
[16:31] <Riddell> GrueMaster: does that stop you using the desktop?
[16:31] <GrueMaster> Riddell: also, it is very slow, possibly due to it not running any optimized video drivers in live (imx51).  Will install and try with closed drivers.
[16:31] <GrueMaster> Riddell: on dove, yes.  No X.
[16:33] <GrueMaster> The slowness on imx51 is very aggravating, but the installer is now running.  We'll see how it runs once it is installed.
[16:35] <GrueMaster> Starting omap.  Not too hopeful due to low memory on system (256M), but we'll see,
[16:40] <GrueMaster> Riddell: knr boots on omap, goes straight to install.  Good so far.
[16:41] <slangasek> Ubuntu DVD up - 20100429, not available from the tracker yet
[16:45] <GrueMaster> slangasek: I am not seeing iso.qa site.  Is it still down?
[16:45] <slangasek> it is
[16:45] <GrueMaster> ok
[16:46] <elmo> tracker should be back up
[16:46] <slangasek> \o/
[16:49] <pitti> thanks so much!
[17:05] <Riddell> GrueMaster: so we should publish omap and imx51 but not dove?
[17:05] <GrueMaster> Yes, that is my current recommendation.
[17:05] <GrueMaster> We need to figure out why ksplashx fails.
[17:13] <Riddell> slangasek: for kubuntu netbook ports please publish omap and imx51 but not dove
[17:13] <slangasek> ack
[17:14] <GrueMaster> Riddell: Sorry for not testing it earlier.  I sometimes get overloaded here.
[17:15] <stgraber> slangasek: edubuntu is now 100% covered
[17:15] <Riddell> that's fine, it's all best effort stuff nothing we depend on
[17:16] <stgraber> slangasek: I'm going to do some other test installs but fader_ validated amd64 and I just finished i386
[17:17] <slangasek> stgraber: excellent :)
[17:18] <cjwatson> smoser: can you get the EC2 publishing going?
[17:19] <cjwatson> (pp slangasek)
[17:20] <ogra> slangasek, oh, i forgot to tell you, i tested omap -server last night, was all fine
[17:22] <slangasek> ogra: ok
[17:22] <ogra> (meaning all omap images are good to go)
[17:44] <Riddell> slangasek: I'm going out for a couple of hours, can you ping ofirk and shtylman if release happens, they'll update the kubuntu.org bits
[17:44] <Riddell> cjwatson: please +v ofirk and shtylman
[17:46] <cjwatson> Riddell: done
[17:48] <slangasek> Riddell: um, it appears that http://www.ubuntu.com/getubuntu/upgrading is not going to include information about upgrades for Kubuntu.  Can you take this into account as necessary on http://kubuntu.org/news/10.04-lts-release
[17:48] <slangasek> ?
[17:49] <Riddell> slangasek: I'm not expecting it to cover Kubuntu, we use https://help.ubuntu.com/community/LucidUpgrades/Kubuntu
[17:49] <Riddell> although a link might be nice
[17:49] <slangasek> Riddell: ok; it has discussed Kubuntu in the past, and I'm just finding out about this content change now, so just wanted to make sure this isn't going to break your links
[18:01] <stgraber> elmo: hey, how do I ssh to the ISO tracker now ? (seems like quandong has been abandoned)
[18:08] <Jeeves_> ipv6 bt tracker is updated
[18:10] <cjwatson> 17:59 <smoser> cjwatson, slangasek ec2 is essentially released.
[18:10] <slangasek> james_w: I believe we need the bazaar importer stopped
[18:10] <cjwatson> 17:59 <smoser> i've updated ami pages and also made images public
[18:10] <cjwatson> 18:10 <ara> stgraber, I will appreciate if you could share that info with me :-)
[18:10] <slangasek> smoser: oho - great, thanks
[18:10] <elmo> stgraber: the new host is temporary, unless it's urgent, do you mind if we wait till we migrate back to quandong?
[18:11] <ara> elmo, I will need to access tomorrow
[18:11] <elmo> ara: that's fine
[18:11] <elmo> ara: new host is limequat
[18:12] <elmo> ldap accounts are easy
[18:12] <elmo> I'll make sure yours gets enabled before tomorrow
[18:12] <ara> elmo, thanks :)
[18:18] <james_w> slangasek: done, thanks
[18:18] <slangasek> \o/
[18:18] <stgraber> elmo: nothing urgent, just nice to have when something comes up or when I want to make a DB dump.
[18:21] <smoser> http://uec-images.ubuntu.com/releases/10.04/release-20100427.1/ is there, but something went amuck in the web indices
[18:25] <smoser> i will get that fixed in 30 minutes or so. have to run now.
[18:26] <slangasek> mvo_: please update changelogs.u.c
[18:27] <james_w> congratulations slangasek et. al.
[18:27] <james_w> thanks for all your work
[18:28] <Jeeves_> Yeah, indeed.
[18:28] <ogra> yeah, slangasek great job !
[18:30]  * ara hugs slangasek :)
[18:31] <stgraber> congrats slangasek & everyone else
[18:31] <ara> slangasek, :'-)
[18:31] <kees> woo!
[18:32] <slangasek> congrats to all!
[18:35]  * charlie-tca sends congrats and thanks too
[18:35]  * fader_ cheers.
[18:38] <shtylman> are we supposed to activate our release pages?
[18:40] <cjwatson> web updates are in progress
[18:40] <slangasek> shtylman: yes
[18:40] <shtylman> kk
[18:45] <pitti> slangasek: will we still have a release meeting tomorrow?
[18:45] <pitti> slangasek, cjwatson: oh, and have a nice evening and beer drinking!
[19:04] <GrueMaster> Is someone updating http://www.ubuntu.com/products/whatisubuntu/arm?  Should be for 10.04 and netbook instead of desktop (as that was the focus since PDX Sprint).
[19:13] <cjwatson> pitti: release meeting> let's not :-)
[19:15] <slangasek> pitti: you can!  I'm on vacation tomorrow :)
[19:18] <doko_> is maverick open?
[19:27] <GrueMaster> doko_: no rest for the wicked, eh?
[19:28] <doko_> GrueMaster: it will take some time until we can open the gates for any uploads
[19:28] <GrueMaster> I was referring to your asking if it was open.
[20:19] <mdeslaur> Is there no way to see the release notes from www.ubuntu.com somewhere?
[20:41] <GrueMaster> There is a link to it by following the "Get Ubuntu" link, then selecting "How to Upgrade".
[20:42] <GrueMaster> Or http://www.ubuntu.com/getubuntu/releasenotes/1004
[20:42] <GrueMaster> (kind of round about way to get there though).
[20:43] <mdeslaur> GrueMaster: oh, thanks...it kind of buried
[20:43] <mdeslaur> s/it/it's/


[12:27] <gotwig> hey, can you please help me with my package build? It failed because of libgranite dependency: https://launchpadlibrarian.net/137380730/buildlog_ubuntu-precise-i386.gazette_1.1.1-0~23~precise1_FAILEDTOBUILD.txt.gz
[12:27] <gotwig> what is missing here?
[12:49] <tsimpson> gotwig: "error: Package `granite' not found in specified Vala API directories or GObject-Introspection GIR directories"
[12:49] <gotwig> tsbere: how to fix
[12:50] <gotwig> tsimpson: how to fix
[12:52] <tsimpson> gotwig: I don't know, I guess you need to build C# bindings for granite
[12:52] <gotwig> Depending on other PPAs If you want Launchpad to satisfy your package dependencies using one or more other PPAs, follow the Edit dependencies link on your PPA or the team's overview page.
[12:52] <gotwig> ok ...


[08:19] <smoser> adam_g, https://code.launchpad.net/~smoser/+junk/cobbler-devenv
[09:02] <smoser> adam_g, above, i'm interested in modifying it to "just work" with current ensemble, but i really dont think we're likely far off.
[12:42] <koolhead17> kim0, elhoo
[13:10] <kim0> koolhead17: hey o/
[13:10] <koolhead17> supp dude
[13:12] <kim0> all going good .. enjoying desktop summit ?
[13:15] <koolhead17> kim0, hmm. met many people including mr. shuttleworth
[13:16] <kim0> sounds like you're having fun then :)
[13:16] <kim0> enjoy
[13:16] <koolhead17> hmm. yes
[13:17] <koolhead17> i saw people wearing oneric &  openstack t-shirts and when i asked them, they said they got it for free
[13:17] <koolhead17> i felt !@#$
[13:18] <koolhead17> since most of them didn`t knew what are the things :(
[13:20] <adam_g> lol
[13:21] <TeTeT> he he
[13:23] <koolhead17> TeTeT, hey man.
[13:24] <TeTeT> koolhead17: how do you like Berlin?
[13:24] <koolhead17> adam_g, hehe. am serious :P its total !@#$ i thought i found few cloud guys in desktop conf :)
[13:24] <koolhead17> TeTeT, yeah its very cold,
[13:24] <koolhead17> planning to roam around city tomorrow.
[13:25] <TeTeT> koolhead17: for Germany it's exceptionally cold for August, at least 5-10 degrees missing
[13:26] <koolhead17> TeTeT, hehe. for me cold is below 18 degree :P
[13:27] <TeTeT> koolhead17: wrong country then ;)
[13:27] <koolhead17> TeTeT, hehe. i bought proper cloths so am fine/safe
[13:27] <koolhead17> TREllis, hey
[13:28] <adam_g> koolhead17: i believe there are more tshirts walking around than users :)
[13:28] <koolhead17> BTW i want the marketing guys to turn bit smart, they should tell people what t-shirt means before giving it free
[13:29] <koolhead17> BTW i want the marketing guys to turn bit smart, they should tell people what t-shirt means before giving it free :P
[13:29] <koolhead17> TeTeT, pm
[18:50] <gtaylor> So for those of you on EC2 or UEC, do you manually juggle SSH keys or do you authenticate over LDAP (or equivalent?)


[00:21] <ion> #6  0xb7ff3eee in nih_file_read (parent=0x0,
[00:21] <ion>     path=0xb800b094 "/sys/dev/block/8:1/../dev", length=0xbffff53c) at file.c:134
[00:21] <ion> mountall:file.c:134: Unhandled error from nih_file_read: Invalid or incomplete multibyte or wide character
[00:21] <ion> Wtf? :-P
[00:38] <ion> keybuk: A bug in nih_file_read: various errors cause a ‘goto error’, some of which set errno and some don’t. The error handler does nih_error_raise_system, potentially leading to nonsensical error messages.
[00:40] <ion> keybuk: I was trying to nih_file_read a sysfs file. Its stat says its size is 4096, whereas read actually returns 4 bytes. That caused the ‘Invalid or incomplete multibyte or wide character’ message.
[00:41] <ion> keybuk: Ah, you do set errno manually. I missed that.
[00:42] <ion> keybuk: I still think the error message for this case isn’t very helpful. :-)
[05:12] <ion> To ensure Keybuk notices this: hey, look at what i said on the other channel. :-P And now for some sleep.
[12:04] <ion> Morning
[12:04] <ion> keybuk: Online? :-)
[12:04] <Keybuk> yup
[12:04] <ion> Any comments about my patch?
[12:04] <Keybuk> patch?
[12:05] <ion> ti052526 < ion> keybuk: Here’s an untested implementation. It probably breaks your system and leaks memory, but it’s a start. Hey, at least it compiles without warnings. :-P  http://heh.fi/patches/mountall/
[12:05] <ion> ti052620 < ion> keybuk: I’ll have a better capability to test mountall patches as soon as i can get my system to run *some* version of mountall. ;-)
[12:05] <ion> ti052638 < ion> keybuk: As in, boot using it
[12:05] <Keybuk> oh cool
[12:06] <Keybuk> at a quick glance, isn't there a libudev way of doing this rather than dealing with sysfs by hand?
[12:06] <Keybuk> you have mnt->udev_device ;)
[12:06] <ion> Good point. I’ll take a look at that struct.
[12:06] <Keybuk> http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/
[12:07] <Keybuk> e.g. while (dev = udev_device_get_parent ())
[12:07] <Keybuk>         if (dev is what you're looking for)
[12:07] <Keybuk>             break;
[12:07] <Keybuk> etc.
[12:08] <ion> How about slaves?
[12:22] <ion> udevadm info --export-db doesn’t seem to contain slave information.
[12:23] <Keybuk> you can still get things like that as properties, attributes, etc.
[12:25] <ion> udevadm info --query=all --name=/dev/alku-main/root: http://pastebin.com/f49b5a4b
[12:26] <ion> udevadm info --attribute-walk --name=/dev/alku-main/root: http://pastebin.com/f5c3b19a
[12:26] <ion> I fail to notice any mention of the md slave.
[12:38] <ion> I made made the physical_dev_ids function work on Mount * directly, patch updated. I didn’t implement the udev thing yet. I’ll have to research more.
[12:49] <ion> keybuk: Whoops, forgot to add the entry to the list in queue_fsck. Patch updated.
[13:00] <ion> It would be nice to see whether the actually code works in the current form.
[13:01] <Keybuk> am figuring out why it doesn't now ;)
[13:01] <ion> Hehe
[13:09] <ion> Any debug output?
[13:13] <Keybuk> OMG
[13:13] <Keybuk> IT BUILT
[13:13] <Keybuk> ion: --debug ;)
[13:20] <ion> I mean, when you tested it
[13:22] <Keybuk> ?
[13:23] <ion> You said you’re figuring out why it doesn’t work. Does it print debug output i could take a look at?
[13:27] <Keybuk> oh, I mean mountall in general
[13:29] <ion> Ah
[14:15] <[psy]> so whats is the RightWay(tm) to turn off a service on boot?
[14:17] <[psy]> and: how do i make my ldap-service start automaticly when the user wants to start apache, for example?
[14:17] <[psy]> we wanna rewrite our daemontools based distro to upstart
[14:19] <[psy]> oh and: how do i make everything that 'depends' on ldap, stop, and start again automaticly, when the user wants to restart ldap?
[14:19] <[psy]> (just like gentoo's init system does)
[14:20] <[psy]> i've read the wiki, but i'm not sure how to do it with events.
[14:27] <Keybuk> if you're thinking in terms of "depends", you need to take a few steps backwards
[14:54] <[psy]> right
[14:54]  * [psy] steps back
[14:54] <[psy]> back to daemontools you mean? :)
[14:55] <Keybuk> no, just your way of thinking
[14:55] <Keybuk> Upstart isn't a dependency-based system
[14:55] <[psy]> its event based, right?
[14:55] <Keybuk> if you're interested in Upstart, you need to learn not to think in terms of dependencies
[14:55] <Keybuk> execatly
[14:56] <[psy]> my question was how to do it with events..is it possible?
[14:56] <Keybuk> yes
[14:56] <[psy]> e.g.: user wants to start apache, so ldap is started first
[14:56] <Keybuk> but you're still thinking in terms of dependencies
[14:56] <Keybuk> you need to unlearn that
[14:56] <Keybuk> that's not how Upstart works
[14:56] <[psy]> ok
[14:57] <Keybuk> in Upstart, we would say that apache is started when ldap is started
[14:57] <Keybuk> *not* the other way around
[14:57] <[psy]> so i need to but a start on ldap in the apache event-config
[14:58] <[psy]> however: i dont want apache to be started as soon as ldap is started all the time
[14:58] <[psy]> sometimes i just wanna start ldap, without apache
[14:58] <Keybuk> why?
[14:58] <[psy]> dont think in terms of why
[14:58] <[psy]> ldap+apache is just an example
[14:58] <Keybuk> what are the conditions in which apache would not be started at boot?
[14:59] <Keybuk> we don't do hypothetical examples here, only real world ones
[14:59] <[psy]> ok
[15:00] <[psy]> so i cant have ldap start automaticly as soon as i try to start apache? e.g. in the pre-start script of apache or something?
[15:00] <[psy]> dont tell me i need to unlearn dependencys
[15:01] <[psy]> maybe its time for upstart to implement dependencys
[15:02] <sadmac2> [psy]: why?
[15:02] <[psy]> why?
[15:03] <sadmac2> yeah, why do you need them?
[15:03] <[psy]> for example: winbindd cant start if smbd isnt running yet
[15:04] <[psy]> currently with daemontools it keeps restarting until smbd is started
[15:04] <[psy]> what i want is a way to start smbd automaticly if winbindd is started
[15:04] <[psy]> and stop winbindd automaticly when smbd is stopped
[15:04] <[psy]> by the sysadmin
[15:04] <sadmac2> ok. upstart does that...
[15:05] <[psy]> how?
[15:05] <sadmac2> have smbd start winbind
[15:06] <[psy]> thats the wrong way around
[15:06] <[psy]> package-maintainer-wise
[15:06] <sadmac2> ok
[15:07] <[psy]> now this will happen: for some reason ldap is started. ldap starts smbd, and smbd starts winbindd
[15:07] <sadmac2> have winbind be started by smbd
[15:07] <sadmac2> yes. that will happen. so?
[15:07] <[psy]> but the sysad doesnt want smbd and winbindd running!
[15:07] <sadmac2> why not?
[15:07] <[psy]> he only wants ldap
[15:08] <[psy]> you wont get peace with that attidue
[15:08] <[psy]> attitude
[15:08] <sadmac2> its not a rhetorical question
[15:08] <[psy]> i just told you: samba IS installed, but the sysad doesnt need it or use it. however, ldap IS needed for something
[15:09] <sadmac2> so he should uninstall samba
[15:09] <ion> keybuk: Patch updated. Using libudev now. It still needs to be tested, i only know it compiles. :-P
[15:09] <[psy]> furthermore: the package maintainer of openldap doesnt want all kinds of references to smbd in his ldap-event script
[15:09] <sadmac2> [psy]: the references can go in the other scripts
[15:09] <sadmac2> start on starting ldap
[15:10] <[psy]> ah ok
[15:10] <[psy]> well let me ask another question: how do i keep a service down without removeing or moving the event definition?
[15:11] <Keybuk> you'd place the service in manual mode (0.10 era)
[15:11] <sadmac2> [psy]: at the moment you don't. solution coming.
[15:11] <[psy]> oki
[15:11] <[psy]> i'll wait a while then
[15:12] <[psy]> i dont see any advantages to daemontools at the moment
[15:12] <sadmac2> Keybuk: one more 3-day weekend and event_operator will be gone from my tree :)
[15:12] <[psy]> some new features i dont need, some missing features i do need :)
[15:12] <Keybuk> sadmac2: I know I still have your mail to review :-/
[15:12]  * Keybuk is behind with lots of things atm
[15:13] <[psy]> and you really should implement dependencies
[15:13] <sadmac2> Keybuk: considering that changing event_operator was a precursor to that proposal, the fact that I figured out how to get rid of it entirely is kind of surprising.
[15:13] <[psy]> yeah..you could life without them...but then we you could say: hey..who needs packages, just ./confiugre;make install everything by hand because 'thats how we see it'
[15:14] <sadmac2> [psy]: there are some more powerful relationships coming. I won't say "dependencies" though.
[15:14] <[psy]> oki
[15:19] <[psy]> well the most important thing is the ability for the sysad to shutdown something permanently
[15:20] <[psy]> but we could work around that by using symlinks like /etc/event.d/servicename -> /etc/events/realservicescript
[15:20] <[psy]> sysv init style syslink ;)
[15:20] <[psy]> m
[15:21] <sadmac2> [psy]: that's a good for-now solution. Nicer things are coming.
[15:21] <[psy]> yup
[15:46] <ion> keybuk: Another small update, better debug logging in add_device.
[15:47] <ion> keybuk: The dev_ids code seems to work on a box that has lvm over md over two HDDs. I haven’t managed to test the fsck queue code yet.
[15:50] <ion> keybuk: I still had to call udev_device_get_syspath, add "/slaves" to its result and call udev_device_new_from_syspath for each entry under that path. I didn’t figure out a way to traverse the slaves using plain libudev API.
[15:52] <sadmac2> ion: what is this you're working on?
[15:55] <ion> sadmac: Keybuk implemented mountall, a program that handles the fscking and mounting of fstab entries in the proper order, parallelizing fsck as much as possible. Well, too much, since all fsck instances run in parallel, with a /* FIXME */ for having each fsck instance use a lock for each underlying physical device to avoid thrashing. My patch fixes the FIXME.
[15:58] <sadmac2> ion: oic
[16:26] <ion> keybuk: How does the patch look now?
[16:27] <Keybuk> ion: haven't looked yet ;)
[17:12] <ion> keybuk: I created the file /looptest, made an ext2 filesystem on it and added ‘/looptest /mnt ext2 loop 0 2’ to fstab. Mountall seems to end up waiting forever in the main loop select().
[17:16] <sadmac2> ion: missing an nih_main_loop_interrupt ?
[17:17] <Keybuk> ion: isn't it just waiting for the root filesystem to be ready?
[17:17] <Keybuk> udevadm trigger --subsystem-match=block
[17:18] <ion> http://pastebin.com/f2483aa5a
[17:19] <ion> It says mountpoint_ready: /
[17:20] <ion> Oh, now would be a good idea to test without my patch. :-P
[17:20] <ion> Nope, it still does the same thing.
[17:28] <ion> The same issue with a swapfile: i created the file /swaptest, did mkswap and added ‘swaptest none swap sw 0 0’ to fstab. Mountall says mountpoint_ready: / and then blocks forever in select().
[17:29] <ion> ‘/swaptest none swap sw 0 0’
[17:29] <ion> (having commented out the /looptest entry)
[17:32] <sadmac2> Keybuk: strange thought. What if instead of start on started <name> <env> it was start on started <env>, where the first item in <env> was always UPSTART_EVENT_NAME= ?
[17:32] <Keybuk> sadmac2: ugh
[17:32] <Keybuk> besides, 0.10 that's start on <job> started again ;)
[17:33] <sadmac2> Keybuk: yeah, I was wondering about the semantics for that. Is event.name == job.name and started is an argument?
[17:34] <Keybuk> jobs, states and events are the same fundamental thing
[17:34] <Keybuk> event is just an edge of a state
[17:34] <Keybuk> it's not so much an argument, as a sub-state if that makes sense
[17:34] <sadmac2> the edge of a state is not the same fundamental thing as a state.
[17:34] <Keybuk> I think it is
[17:35] <sadmac2> Keybuk: if you buy an apple and I give you the core of an apple are you happy>
[17:35] <Keybuk> *baffled*
[17:35] <sadmac2> Keybuk: better: if you buy a table and I give you the edge of a table, are you happy?
[17:35] <Keybuk> you're being silly
[17:35] <Keybuk> stop it
[17:37] <sadmac2> Keybuk: what does muddling states and events gain us?
[17:37] <Keybuk> symmetry
[17:38] <sadmac2> Keybuk: why not make states and malloc'd regions the same too then?
[17:38] <Keybuk> you're still being silly
[17:39] <sadmac2> If I'm being silly by following your logic to its conclusion...
[17:39] <Keybuk> for example:
[17:39] <Keybuk> one job
[17:39] <Keybuk>   while network-device eth0 up
[17:39] <Keybuk> another job
[17:39] <Keybuk>   while apache running
[17:39] <Keybuk>   on network-device eth0 up
[17:40] <Keybuk> that's why it makes sense for events and states to be symmetric
[17:40] <Keybuk> it's simple, obvious and elegant
[17:42] <sadmac2> does network-device eth0 up correspond to starting, started, stopping, stopped, or something in the middle?
[17:42] <Keybuk> to whatever you want
[17:44] <sadmac2> and how do you specify which?
[17:46] <sadmac2> Keybuk: I see what you're doing, but I think you describe it poorly. I think this model has no events at all (at least not ones visible to the user)
[17:47] <Keybuk> on is an event
[17:47] <sadmac2> on itself?
[17:48] <Keybuk> no
[17:48] <Keybuk> on matches events
[17:48] <Keybuk> while matches states
[17:48] <Keybuk> states are either true or false
[17:48] <sadmac2> but events are states
[17:48] <sadmac2> or so you say
[17:48] <Keybuk> events do not have any value
[17:48] <Keybuk> events are when states change
[17:49] <sadmac2> so are events the same as states or different?
[17:49] <Keybuk> events occur when states change
[17:50] <sadmac2> ok, so events aren't states
[17:53] <sadmac2> that kind of ruins your explanation of on's arguments
[17:55] <Keybuk> why?
[17:56] <sadmac2> Keybuk: because that explanation began "events are states"
[17:56] <sadmac2> Keybuk: and we've now arrived at "events aren't states"
[17:56] <Keybuk> only the way you describe them
[17:56] <Keybuk> to me they're one and the same thing
[17:57] <sadmac2> Keybuk: then why do we have two words for it?
[17:57] <sadmac2> not a rhetorical question.
[17:57] <Keybuk> because I haven't thought of a better word yet
[17:58] <sadmac2> Keybuk: I could follow you if there were no events at all, just states
[17:58] <Keybuk> I don't like the word "states"
[17:58] <sadmac2> Keybuk: on apache started => start at the earliest point in time at which apache started is true
[17:59] <Keybuk> right
[17:59] <sadmac2> Keybuk: if you're into the true/false thing, "conditions" would be the next point.
[17:59] <Keybuk> I'm not as much of a fan of PhD level logic problems are you are ;)
[17:59] <sadmac2> Keybuk: all of this makes 0.6 compatibility reeeely grody. Are you still interested in 0.6 compatibility?
[17:59] <Keybuk> I don't see it as a problem
[17:59] <sadmac2> Keybuk: I think "conditions" is a fairly sane word
[18:00] <sadmac2> Keybuk: information coded as conditions/states for 0.10 as you describe is coded as environment variables in 0.6. That gets scary fast.
[18:01] <sadmac2> unless these two things don't interact seamlessly
[18:01] <ion> keybuk: What’s missing from the ubuntu-boot PPA so that one could upgrade to it and have a booting system? Perhaps i could do something.
[18:02] <sadmac2> Keybuk: I actually prefer conditions precisely because its /less/ prominent in PhD-land. States is a reeeeely loaded word from the formalist side of things. Especially when we talk about "state machines"
[18:02] <sadmac2> which are rarely what "state machines" really are when we're talking about them.
[18:06] <sadmac2> Keybuk: also I wonder about the usefulness of your example. What wants to start "on network-device"? If it needs the network device to start why doesn't it care if it goes away halfway through initialization?
[18:08] <sadmac2> so if on x means "at the earliest point when x is true," then I'd assume we'd have an after x for "the earliest point when x is false"
[18:08] <sadmac2> from...until would want a from after...until, and a from...through counterpart as well
[18:14] <Keybuk> ion: figuring out why it's not working ;)
[18:14] <Keybuk> it works on one mini
[18:14] <Keybuk> but packaged up it doesn't
[18:14] <Keybuk> trying to figure out what step I've missed
[18:14] <Keybuk> sadmac2: ntpdate is started when a network device comes up
[18:15] <Keybuk> I don't think your "after" case is invalid, I've been thinking the same thing
[18:17] <sadmac2> Keybuk: beyond that, I'd keep the term states. It has heritage in the project and its not really "wrong" just yet. (Events I'd stop saying for awhile. They're still present here, but they're hidden."
[18:27] <sadmac2> honestly I'd be ok with calling them jobs.
[18:27] <sadmac2> that's what the code calls them now (or what will become them)
[18:29] <Keybuk> right, I suspect that's what the code will always call them ;)
[18:31] <sadmac2> Keybuk: so in the phrase "on foo" foo is a state, but on infers an event from it. "after" would take the same state and infer a different event.
[18:31] <Keybuk> don't know
[18:31] <Keybuk> I've used after for temporary events
[18:31] <Keybuk> <time period> after <event>
[18:33] <sadmac2> Keybuk: either way. Point is events don't really have names and arguments anymore. We don't talk about them directly in the config. We mention states, and an event is implied by context.
[18:34] <sadmac2> Keybuk: I'd also imagine initctl emit doesn't make much sense anymore. Things like udev can just start states for their devices.
[18:37] <Keybuk> no it still makes sense I think
[18:37] <Keybuk> there are still events that don't have attached states
[18:37] <Keybuk> events used as commands
[18:38] <sadmac2> Keybuk: how do we talk about them in job definitions. Do we just put them in the same namespace as states so "on fooevent" works too?
[18:47] <Keybuk> that's a pretty good question
[18:47] <Keybuk> I can't find my notes on this
[18:47] <Keybuk> but basically you have events that are really states
[18:47]  * sadmac2 gets nervous
[18:48] <sadmac2> how long do they last?
[18:48] <sadmac2> also you should publish these "notes" :P
[18:48] <Keybuk> I mean in the current scheme
[18:48] <sadmac2> were we all perfect :)
[18:49] <Keybuk> to publish involves typing
[18:49]  * Keybuk writes a lot with pen, paper and whiteboards
[18:49] <Keybuk> so
[18:49] <Keybuk> events that are states
[18:49] <Keybuk> "job started" type things
[18:49] <Keybuk> there are events that are real events that would never have states
[18:49] <Keybuk> control-alt-delete being a good example
[18:50] <Keybuk> and there are events that we use a bit like commands
[18:50] <Keybuk> where the *completion* is important to the emitter
[18:50] <Keybuk> maybe hooks is more appropriate than commands as a description
[18:50] <Keybuk> "I'm going to reboot, does anyone need to do anything first?"
[18:52] <sadmac2> Keybuk: so theres still the question of this time-interval (state) => point-in-time (event) mapping.
[18:53] <sadmac2> For the first case, job started clearly maps to an interval. if we need an event we say "The earliest point at which 'job started'"
[18:53] <sadmac2> for case two... that's hard.
[18:53] <Keybuk> I don't think it's earliest point at which
[18:53] <sadmac2> for case three, that looks a lot like injecting case 1.
[18:53] <Keybuk> it's "after 'job started' has happened"
[18:53] <Keybuk> the key point is that 'job started' may no longer be true anymore
[18:53] <sadmac2> Keybuk: so when the job stops
[18:53] <Keybuk> becoming false doesn't cancel the fact that the event is still queued
[18:54] <sadmac2> Keybuk: I would say job started is a convenience alias for job running
[19:09] <Keybuk> right, so that's the interesting bit
[19:09] <Keybuk> isn't "job running" just "job" ? :)
[19:10] <Keybuk> or is "job" true when the job *should* be running, but "job running" true when the job *is* running
[19:10] <Keybuk> etc.
[19:10] <sadmac2> Keybuk: assuming "job foo" can't be true unless "job" is true, then just job would have to be job starting U job running U job stopping
[19:11] <sadmac2> Keybuk: which means job is true when it should be running
[19:11] <sadmac2> Keybuk: which I like
[19:11] <Keybuk> right
[19:11] <Keybuk> that's pretty much the direction I was thinking
[19:12] <sadmac2> Keybuk: the idea that on tests for presence also gets around the "what if you start on started but its already running when you insert your job" thing.
[19:12] <Keybuk> huh?
[19:13] <sadmac2> Keybuk: suppose I have a running system, where apache is running. If I add a new job and have "on apache started" in it, if on is looking for an event, my job won't be running, because the "apache started" event has already passed. If on checks for earliest point at which a state is true, though, it can figure out to start my job right away.
[19:14] <sadmac2> when I say new job I mean new job and class. Completely new .conf
[19:14] <Keybuk> err
[19:15] <Keybuk> but you don't *want* that to be started
[19:15] <Keybuk> that's the whole point
[19:15] <Keybuk> if you're using "on" it should NOT look-behind like that
[19:15] <Keybuk> your "on apache started" job should only be run *when* apache is started
[19:15] <Keybuk> not if apache happens to be running
[19:15] <sadmac2> yeah. out-moded problem.
[19:15] <Keybuk> this is exactly how it differs from "while" :)
[19:15] <Keybuk> (and that while also implies a stop condition)


[02:01] <dkeith__> Good day folks
[02:01] <dkeith__> I have a mythbuntu backend that has started misbehaving recently, the backend app dieing frequently and sporadically.
[02:02] <dkeith__> I just took a look at the backend logs and noticed repeated blocks of errors indicating duplicate database errors
[02:03] <dkeith__> looks something like this (sorry for the length)
[02:03] <dkeith__> --
[02:03] <dkeith__> 2010-02-01 10:00:40.611 DB Error (change_program):
[02:03] <dkeith__> Query was:
[02:03] <dkeith__> UPDATE program SET starttime = '2010-02-01T12:30:14',     endtime   = '2010-02-02T10:16:54' WHERE chanid    = 5381 AND       starttime = '2010-02-01T12:00:14'
[02:03] <dkeith__> Driver error was [2/1062]:
[02:03] <dkeith__> QMYSQL3: Unable to execute query
[02:03] <dkeith__> Database error was:
[02:03] <dkeith__> Duplicate entry '5381-2010-02-01 12:30:14-0' for key 1
[02:03] <dkeith__> --
[02:03] <dkeith__> any chance this rings a bell?
[02:05] <dkeith__> version is mythbuntu 8.x with comcast tuner via firewaire and hd homerun listeing over the air.  Problems seem to happen while recording, though I have not been able to verify
[02:44] <mrand> dkeith__: Sorry, no firm leads.  Might first try cleaning database.  You might also check out http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding (even though you aren't upgrading, that article seems to imply to me there might be remote situations where daily operations could be affected)
[02:44] <mrand> dkeith__: BTW, as suggested in the /topic, you can use pastebin for logs.
[02:44] <Zinn> [www.mythtv.org] Fixing Corrupt Database Encoding - MythTV
[02:45] <tgm4883> i'd also note that in 9.10, the backend should get autorestarted if it dies by upstart
[02:52] <dkeith__> thanks.  to clarify - "cleaning the database" means folowing the instructions at that "Fixing_Corrupt_Database_Encoding"?
[02:52] <dkeith__> sorry bout the paste - the pastebin info scrolled off the screen.
[02:53] <dkeith__> I am intending to upgrade "real soon now".  But I am on the road for the next 4-5 weeks and hope t just stabilize it for now.  Que sera
[03:23] <ahhughes> if I want to add some music to my library where the hell do I copy it too?
[03:23] <Zinn> ahhughes: Please watch your language.
[03:24] <ahhughes> wow, that's harsh.
[03:30] <dkeith__> harsh, but fair.  The manual has instructions for doing this.  IIRC, you can declare where you music is and have it scan that directory.  I am using 8.x, which has a pretty limited music UI (IMHO), and since my FE's are runnign on MACos, just loaded up the myth from the same share full of mp3's that itunes uses
[03:33] <dkeith__> http://www.mythtv.org/wiki/MythMusic#Importing_an_existing_music_collection
[03:33] <Zinn> [www.mythtv.org] MythMusic - MythTV
[12:32] <jarrod1> how can I change the order of items in the main menu? like to make "watch tv" first.
[13:38] <jarrod1> is freenode still having troubles because of this firefox attack?
[17:07] <dlong> I am running 9.04 still due to the lack of support of the PVR 150 and recently upgraded mythtv to 0.22 using the daily builds repo.  That process is working well, with the exception of using new themes such as the new mythbuntu theme or the graphite theme.  Are these themes broken?
[17:08] <rhpot1991> dlong: how is the 150 broken?
[17:09] <dlong> rhpot1991: PVR-150 Blaster does not currently work
[17:10] <dlong> that's right on the front page of http://www.mythbuntu.org/9.10/release
[17:10] <Zinn> [www.mythbuntu.org] Mythbuntu 9.10 Release Notes | Mythbuntu
[17:13] <rhpot1991> ah blasting, nevermind :)
[17:14] <dlong> So if I look at the logs (/var/log/mythtv/mythfrontend.log), I see a lot of "Font needs a face" messages
[17:15] <dlong> In order to get any functionality of the frontend back I have to change the theme inside the database
[17:15] <dlong> blootube-wide works
[17:20] <rhpot1991> dlong: did you update all the themes?
[17:20] <rhpot1991> if you run a pre .22 theme on .22 things wont be happy
[17:22] <dlong> rhpot1991: yes, all the themes are updated
[17:24] <tgm4883> dlong, what is the output of
[17:24] <tgm4883> dpkg -l mythtv-frontend
[17:24] <tgm4883> and
[17:24] <tgm4883> dpkg -l mythtv-theme-mythbuntu
[17:26] <dlong> mythtv-frontend: 0.22+fixes22594
[17:26] <dlong> mythtv-theme-mythbuntu
[17:26] <dlong> 1.0.22+....
[17:28] <tgm4883> dlong, you are on 9.04?
[17:28] <dlong> tgm4883: yes
[17:28] <tgm4883> using the mythbuntu-repos auto-builds?
[17:28] <dlong> yes
[17:28] <gizmobay> dlong, I have a PVR150 on 9.10
[17:28] <dlong> gizmobay: 32 or 64 bit?
[17:28] <gizmobay> 64 bit
[17:28] <tgm4883> dlong, looks like you have an older build, maybe try apt-get updating again
[17:28] <dlong> gizmobay: hauppauge HVR-1600?
[17:29] <tgm4883> latest on the auto-builds is
[17:29] <tgm4883>  mythtv	 0.22.0+fixes23426-0ubuntu0+mythbuntu2
[17:29] <gizmobay> Just a pvr150 no hvr-1600
[17:29] <dlong> tgm4883: all right, I will update them
[17:34] <rhpot1991> gizmobay: it will record fine, he needs to blast
[17:35] <dlong> rhpot1991: correct.
[17:35] <dlong> Recording worked fine
[17:36] <gizmobay> hasn't setup lirc yet?
[17:36] <gizmobay> Does the HVR-1600 have an internal blaster or will he need a serial?
[17:36] <rhpot1991> gizmobay: blasting doesn't work on it in karmic
[17:37] <gizmobay> ah I see
[17:37] <gizmobay> blasting sucks though lol
[17:38] <dlong> gizmobay: blasting is great for a person who turns into a couch potato after a long day of work
[20:14] <lime4x4> what is the best way to link a usb hard drive to the music folder on 9.10
[20:16] <gizmobay> my blasting can be iffy on changing the channel
[20:16] <gizmobay> it's better 1 in 10 fail for me
[20:42] <Rob_Z> so the issues with the 150's has been fixed and it can now receive IR controls from a remote?
[20:42] <Rob_Z> (and 1600)
[21:35] <dlong> Rob_Z: I don't believe so
[21:48]  * Rob_Z grumbles
[22:20] <tgm4883> there is an issue with PVR 150's and IR Receiving?
[22:20] <tgm4883> I thought it was just with blasting
[22:48] <mrand> 1600 may still be broke.  Not sure of PVR-150 problems other than analog scanning.  http://old.nabble.com/Haupauge-Cards-on-Ubuntu-9.10-td26009614.html
[22:48] <Zinn> [old.nabble.com] Nabble - LIRC - Haupauge Cards on Ubuntu 9.10
[23:23] <zephead> hello.  I just purchased a USB-UIRT for channel changing my comcast DCT2224 box.  I'm able to successfully change channels with the "irsend --device /dev/lircd1 SEND_ONCE DCT2000 6 1 OK" command (example = channel 61) but cannot get this to work in a script.  Does anybody have any suggestions?
[23:24] <zephead> I did have to modify /etc/init.d/lirc as documented here: http://ubuntuforums.org/showpost.php?s=2620631671517159eb08ce9841966b8a&p=8557053&postcount=12
[23:24] <Zinn> [ubuntuforums.org] Ubuntu Forums - View Single Post - [SOLVED] Serial IR Blaster - IRSEND hardware does not support sending
[23:36] <mrand> zephead: I have a very similar cable box.... 2222 maybe.  I think it has the same interface.  I can't look at how my myth application is set up right now, but will be able to this evening if you wanna stick around or come back.  Note that while I have used IR blasting in the past, I use serial port right now.  Slightly faster and more reliable.
[23:39] <zephead> mrand: I wish my new board came w/ the serial pin header(s)! :)  I think my lack of scripting is the root cause here, I figure since irsend works from the commandline, I just need some help creating a script...  I wonder if the modification I had to make to get the blaster portion to work is causing grief since i have to use the "--device /dev/lircd1" flag?
[23:40] <zephead> mrand: I'll stick around and I greatly appreciate any help you may be able to provide.  Thanks!
[23:41] <mrand> Are you using a pre-canned script?
[23:43] <zephead> I've tried and failed ;(  I did just run across this though : http://losdos.dyndns.org:8080/public/mythtv-info/IR-BLASTER-HOWTO.html - and I'm modifying accordingly (REMOTE_NAME=JVC_RAW changed to REMOTE_NAME=DCT2000).  The good thing is my /usr/share/lirc/extras/transmitters/motorola/dctxxxx.conf file is good
[23:43] <Zinn> [losdos.dyndns.org:8080] IR-BLASTER-HOWTO // MYTHTV
[23:43] <mrand> zephead, here's mine: http://mythbuntu.pastebin.com/m1ae89e33
[23:43] <Zinn> [mythbuntu.pastebin.com] mythbuntu private pastebin - collaborative debugging tool
[23:43] <mrand> No promises, but it worked last time I tried it.
[23:43] <mrand> @ignore pastebin.com
[23:43] <Zinn> [pastebin.com] pastebin - collaborative debugging tool
[23:44] <mrand> bbl
[23:44] <zephead> pardon my ignorance, how is this command called from the commandline (rather than specifying in mythtv-setup)? :)
[23:44] <zephead> ok - thanks!
[23:45] <mrand> channel_change.sh <channel number>   I believe.
[23:45] <zephead> :) I'll give it a stab.  Thanks for you help!


[20:43] <wesdom> can i point my dns directly at he at the aws instance ip i get when i do a ping
[20:44] <wesdom> or do I need an elastic ip address
[20:45] <wesdom> i am confused on how to set up my dns now
[20:45] <wesdom> that i have an instance set up
[21:02] <smoser> while you're not supposed to be in this channel, if you are, the RC is available for ubuntu 9.10
[21:02] <smoser> http://uec-images.ubuntu.com/releases/9.10/rc/
[21:19] <jeremydei> haha, smoser, we're just a buncha rebels here i guess
[21:20] <jeremydei> (thx for the info, also)


[07:43] -queuebot:#ubuntu-release- New binary: librnd [amd64] (mantic-proposed/universe) [4.0.1-1] (no packageset)
[07:46] -queuebot:#ubuntu-release- New binary: librnd [arm64] (mantic-proposed/universe) [4.0.1-1] (no packageset)
[07:46] -queuebot:#ubuntu-release- New binary: librnd [ppc64el] (mantic-proposed/universe) [4.0.1-1] (no packageset)
[07:47] -queuebot:#ubuntu-release- New binary: librnd [s390x] (mantic-proposed/universe) [4.0.1-1] (no packageset)
[07:51] -queuebot:#ubuntu-release- New binary: librnd [armhf] (mantic-proposed/universe) [4.0.1-1] (no packageset)
[08:38] -queuebot:#ubuntu-release- New binary: librnd [riscv64] (mantic-proposed/universe) [4.0.1-1] (no packageset)
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected apport [source] (bionic-proposed) [2.20.9-0ubuntu7.30]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [sync] (bionic-proposed) [1.51.1~18.04.1]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected fwupd [source] (bionic-proposed) [1.2.14-0~18.04.3]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected postgresql-common [source] (bionic-proposed) [190ubuntu0.2]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected distro-info [source] (bionic-proposed) [0.18ubuntu<IP_ADDRESS>]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected lxc [source] (bionic-proposed) [3.0.3-0ubuntu1~18.04.3]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [sync] (bionic-proposed) [1.51~18.04.1]
[08:43] -queuebot:#ubuntu-release- Unapproved: rejected software-properties [source] (bionic-proposed) [<IP_ADDRESS>.22]
[08:43] -queuebot:#ubuntu-release- New: rejected fwupd-efi [sync] (bionic-proposed) [1:1.2-3ubuntu0.2]
[08:43] -queuebot:#ubuntu-release- New: rejected fwupd-efi [sync] (bionic-proposed) [1:1.4-0ubuntu0.1]
[08:43] -queuebot:#ubuntu-release- New: rejected fwupd-efi [sync] (bionic-proposed) [1:1.4-0ubuntu0.1]
[08:43] -queuebot:#ubuntu-release- New: rejected networking-mlnx [source] (bionic-proposed) [1:12.4.0-0ubuntu<IP_ADDRESS>]
[10:25] -queuebot:#ubuntu-release- New: accepted librnd [amd64] (mantic-proposed) [4.0.1-1]
[10:25] -queuebot:#ubuntu-release- New: accepted librnd [armhf] (mantic-proposed) [4.0.1-1]
[10:25] -queuebot:#ubuntu-release- New: accepted librnd [riscv64] (mantic-proposed) [4.0.1-1]
[10:25] -queuebot:#ubuntu-release- New: accepted librnd [arm64] (mantic-proposed) [4.0.1-1]
[10:25] -queuebot:#ubuntu-release- New: accepted librnd [s390x] (mantic-proposed) [4.0.1-1]
[10:25] -queuebot:#ubuntu-release- New: accepted librnd [ppc64el] (mantic-proposed) [4.0.1-1]
[14:33] <xnox> sru-alert / vorlon https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2020530 debootstrap update that drops symlinks breaks mk-sbuild.
[14:33] -ubottu:#ubuntu-release- Launchpad bug 2020530 in ubuntu-dev-tools (Ubuntu Jammy) "The debootstrap SRU to end all debootstrap SRUs" [Undecided, Confirmed]
[15:22] <vorlon> xnox: <table flip>
[15:22] <vorlon> xnox: so, thanks for identifying
[15:46] -queuebot:#ubuntu-release- Packageset: Removed php8.1 from i386-whitelist in mantic
[15:46] -queuebot:#ubuntu-release- Packageset: Added cpdb-backend-cups to i386-whitelist in mantic
[15:46] -queuebot:#ubuntu-release- Packageset: Added cpdb-libs to i386-whitelist in mantic
[16:50] <xnox> vorlon:  do you want me to do ubuntu-dev-tools cherry-picks & srus?
[16:50] <xnox> vorlon:  do you like what ubuntu-dev-tools does?
[16:50] <vorlon> xnox: cherry-picks> no, I'm writing an SRU exception for udt today
[16:53] <xnox> vorlon:  yeah, it really is something that needs to be new, otherwise it is pointless.
[18:32] <utkarsh2102> bdmurray: hey, with my Bionic EOSS lead hat on (heh :P), can you please go through the bionic-proposed ready-to-released packages during your shift today?
[18:33] <utkarsh2102> There were some packages blocked on by some comments yesterday that might be worth re-visiting, for eg: hibagent, iptables, etc.
[18:37] <bdmurray> utkarsh2102: Has there been any discussion about letting these blocked-proposed-bionic packages through?
[18:40] <bdrung> bdmurray, can you review the SRU in bug #2020461 please?
[18:40] -ubottu:#ubuntu-release- Bug 2020461 in nvme-stas (Ubuntu Kinetic) "Backport nvme-stas to Ubuntu 22.04 (jammy)" [Undecided, New] https://launchpad.net/bugs/2020461
[18:43] <bdmurray> bdrung: I'll try - I have a short week this week
[19:16] -queuebot:#ubuntu-release- Packageset: Removed cpdb-backend-cups from i386-whitelist in mantic
[19:48] <vorlon> xnox: https://lists.ubuntu.com/archives/ubuntu-release/2023-May/005639.html
[20:14] <utkarsh2102> bdmurray: haven't checked, didn't have the time :/
[20:14] <utkarsh2102> also, just as an FYI, we're fast-tracking LXC SRUs so in case there's something around that.
[21:18] -queuebot:#ubuntu-release- Unapproved: freeipmi (jammy-proposed/main) [1.6.9-2 => 1.6.9-2ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[21:18] -queuebot:#ubuntu-release- Unapproved: freeipmi (lunar-proposed/main) [1.6.10-1 => 1.6.10-1ubuntu0.1] (ubuntu-desktop)
[21:18] -queuebot:#ubuntu-release- Unapproved: freeipmi (kinetic-proposed/main) [1.6.9-2 => 1.6.9-2ubuntu<IP_ADDRESS>] (ubuntu-desktop)


[08:42] <pixel6692> Hello is there way to get/make/build linux-image-extra for 4.5 (15.10)? I need aufs module and I also need to use 4.5 because of my ethernet driver
[09:06] <xnox> pixel6692, usually one can find ethernet driver as a dkms module on e.g. github and use that with 15.10 kernel.
[09:06] <xnox> pixel6692, note that e.g. even 16.04 has 4.4 kernel, but with some backports
[09:10] <pixel6692> I am currently running 4.5 from here http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ I just need aufs module
[09:10] <pixel6692> that is typicaly in package linux-image-extra (which is not in this tree), I am trying to build it with this module now
[09:11] <pixel6692> my ethernet driver was repaired in 4.5
[14:19] <cryptohwlinuxhel> what function can I use from the kernel to copy a __user pointer to another __user pointer? can I just do memcpy?
[14:36] <apw> cryptohwlinuxhel, it seems unintuitive to want to copy userspace to userspace (within the same process) in a system call, i beleieve you cannot use mempcy as the kernel handles faults for userspace addresses differently if you are in a call it expects to touch userspace
[14:37] <cryptohwlinuxhel> yeah there is a flag I have to set to bypass what my driver does
[14:38] <cryptohwlinuxhel> so the bypass is to simply do a memory copy from one _user pointer to another
[14:38] <cryptohwlinuxhel> it cannot be done from outside the kernel since it is a driver
[14:38] <cryptohwlinuxhel> also the kernel gives this flag a shared common memory that all processes can see
[14:39] <cryptohwlinuxhel> so what can I use if I cannot use memcpy?
[14:40] <cryptohwlinuxhel> I can always allocate local memory copyfromuser to my local buffer and then copytouser from my buffer but that is not efficient and I would like to avoid it
[14:43] <apw> i am not sure there is one, but i have not looked, you will find copyfromuser etc are marked specially as copiers, so you could look at what other calls are the same
[15:00] <cryptohwlinuxhel> what do you mean they are marked as copiers?
[15:01] <cryptohwlinuxhel> http://lxr.free-electrons.com/source/arch/arm/include/asm/uaccess.h#L552
[15:01] <cryptohwlinuxhel> I see no markings
[16:25] <tych0> i'm trying to build a kernel from xenial's current master, and i'm getting, http://paste.ubuntu.com/15633017/
[16:25] <tych0> any ideas?
[16:47] <genkgo> jsalisbury: nice achievements again on the backup issue
[16:48] <jsalisbury> genkgo, getting closer.  I may have to perform a bisect of the entire tree, which will take a few more days of testing
[17:00] <pesari> hey, have you seen this with xenial-proposed 4.4.0-17 ? https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564951
[17:00] <ubot5`> Launchpad bug 1564951 in systemd (Ubuntu) "systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument" [Undecided,Confirmed]
[17:02] <genkgo> jsalisbury: i am really really wondering what it is
[17:02] <genkgo> jsalisbury: probably nobody ever thought of
[17:02] <genkgo> *something
[17:02] <genkgo> and might fixes other things too
[17:08] <jsalisbury> genkgo, Yeah, it isn't any of the hv commits or virtio commits between these two releases.  That's why sometimes a bisect is needed to identify the real offending commit.
[17:09] <genkgo> jsalisbury: the virtio commits are also not the problem?
[17:09] <jsalisbury> genkgo, no.  I built a test kernel with them all reverted and I still hit the bug in about an hour.
[17:09] <genkgo> ok
[17:12] <kamal> tych0, your problem there is (I think) that you're trying to build with just 'make' ...  to build an Ubuntu kernel, follow the "Building the kernel" instructions here:
[17:12] <kamal> https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[17:12] <kamal> specifically:
[17:12] <kamal> fakeroot debian/rules clean
[17:12] <kamal> fakeroot debian/rules binary-generic
[17:13] <tych0> kamal: ah, interesting, ok
[17:14] <kamal> tych0, that ^^ will build security/apparmor/ just fine.    (whereas, with bare 'make', the thing you reported is indeed the first failure I get too).
[17:14] <tych0> interesting; it used to work with make bindeb-pkg before that patch :)
[17:14] <genkgo> jsalisbury: thanks, looking forward to the end result! you must tired of all these backups by now ;)
[17:14] <tych0> although perhaps i was doing something horribly wrong
[17:15] <jsalisbury> genkgo, heh, not tired yet.  It too much of a fun puzzle.  The wait while testing is the pain.
[17:16] <genkgo> jsalisbury: hehe, alright. glad to hear you still got the spirit!
[17:16] <kamal> tych0, hmmm.  well if it used to work (when exactly?) then it probably should still -- maybe we actually do have a new glitch to sort out.
[17:16] <tych0> kamal: yeah, it used to work as of a few weeks ago with the xenial kernel's master
[17:16] <tych0> let me look for the exact ref
[17:17] <jsalisbury> genkgo, We'll get to the bottom of this.
[17:17] <tych0> kamal: f35781cd96795075436fde15abfc1b94bdffb99c
[17:18] <kamal> tych0, yup, you've got a point there!
[17:19] <tyhicks> tych0: looks like this would do it: https://paste.ubuntu.com/15634420/
[17:20]  * tych0 builds
[17:21] <tych0> tyhicks: but yeah, that looks suspicious :)
[17:22] <tych0> tyhicks: yeah, that fixes it
[17:22] <tyhicks> tych0: thanks - I'll send a patch to the kteam
[17:22] <tych0> tyhicks: cool, thanks
[17:23] <kamal> tych0, tyhicks: nice job ty-team!  ;-)  thanks
[17:23] <tyhicks> heh :)
[17:24] <tych0> i have to be useful every once in a while if i'm going to troll tyhicks' tab completion everywhere
[17:24] <kamal> :-)
[17:24] <tyhicks> jjohansen: ^ FYI so you know the reason for the patch that I'm about to send out
[17:27] <jjohansen> I'm not sure why our builds didn't catch that
[17:27] <tyhicks> me neither
[17:29] <tyhicks> jjohansen: are you wanting to understand it more or should I go ahead and send out the patch?
[17:29] <jjohansen> tyhicks: just send the patch


[16:33] <mdeslaur> \o
[16:33] <tyhicks> hello
[16:33]  * sbeattie waves
[16:34] <tyhicks> #startmeeting
[16:34] <meetingology> Meeting started Mon Apr 11 16:34:11 2016 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:34] <meetingology> Available commands: action commands idea info link nick
[16:34] <tyhicks> The meeting agenda can be found at:
[16:34] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:34] <tyhicks> [TOPIC] Weekly stand-up report
[16:34]  * tyhicks kicks the bot
[16:35] <tyhicks> mdeslaur: you're up
[16:35] <mdeslaur> I'm on community this week
[16:35] <mdeslaur> I have patch piloting tomorrow
[16:35] <mdeslaur> and I'm working on an embargoed issue
[16:35] <mdeslaur> that's it, sbeattie, you're up
[16:35] <sbeattie> I'm on bug triage this week
[16:36] <sbeattie> I'm working on testing glibc updates, trying to figure out what breaks with pt_chown disabled.
[16:37] <sbeattie> I've got a kernel USN to write I guess (not sure what the kernel team did there)
[16:37] <sbeattie> I've got some apparmor stuff to do (patch review)
[16:38] <sbeattie> That's probably it for me this week
[16:38] <sbeattie> tyhicks: you're up
[16:38] <tyhicks> I'm on cve triage this week
[16:38] <tyhicks> apparmor 2.10.95 landed in xenial over night so I'll be watching for any issues there
[16:39] <tyhicks> I have some ubuntu-core-launcher MPs to review for jdstrand
[16:39] <tyhicks> still have some pending ecryptfs patch reviews
[16:40] <tyhicks> would also like to do some triaging/updates for Touch
[16:40] <tyhicks> that's it for me
[16:40] <tyhicks> sarnold: you're up
[16:40] <tyhicks> sorry
[16:40] <tyhicks> jjohansen: you're up
[16:40] <sarnold> \o/ apparmor landing
[16:41] <jjohansen> I'm still working on apparmor this week
[16:41] <tyhicks> you say that like there is an end in sight :)
[16:41] <jjohansen> I have an upstream patchset of bug fixes to finish putting together and push up
[16:43] <jjohansen> and then it will be back to fixing bugs and issues in the newly landed apparmor 3.5
[16:44] <jjohansen> and of course watching for any issues that may surface from 2.10.95 landing
[16:44] <jjohansen> thats it for me sarnold you are up
[16:44] <sarnold> i'm in the happy place this week
[16:45] <sarnold> I'm working on mirs, neutron-vpnaas, aodh, barbican, designate, it's unlikely I'll get them all this week but I might get lucky, aodh is apparenhtly a piece from ceilometer
[16:45] <sarnold> and I'd like to test out shiny new apparmor stacking
[16:46] <sarnold> that's it for me, chrisccoulson?
[16:46] <chrisccoulson> Last week I made quite a bit of progress on automated testing in Oxide (I got all of our existing QML tests also running in single-process, which means we can officially support that now)
[16:47] <tyhicks> nice!
[16:47] <chrisccoulson> I plan to do more of the same this week - I'm adding some compiled unit-tests for bits of the API (most of our existing tests are more integration tests than unit tests). Then I plan to add a framework for writing unit-tests for internal classes
[16:48] <chrisccoulson> I need to also do some feature work (not much of that has happened over the last couple of weeks). I'll probably be experimenting with scrollbars to see how we can support the design requirements for those
[16:48] <chrisccoulson> And there's probably going to be a Firefox update
[16:48] <chrisccoulson> That's me done
[16:50] <tyhicks> thanks
[16:50] <tyhicks> [TOPIC] Highlighted packages
[16:50] <tyhicks> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:50] <tyhicks> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:50] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/python-requests-kerberos.html
[16:50] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/maildrop.html
[16:51] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/dcmtk.html
[16:51] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/xml-light.html
[16:51] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/loganalyzer.html
[16:51] <tyhicks> lots of good ones in there this week
[16:51] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:51] <tyhicks> Does anyone have any other questions or items to discuss?
[16:53] <tyhicks> mdeslaur, sbeattie, jjohansen, sarnold, ChrisCoulson: Thanks!
[16:53] <tyhicks> #endmeeting
[16:53] <meetingology> Meeting ended Mon Apr 11 16:53:06 2016 UTC.
[16:53] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2016/ubuntu-meeting-2.2016-04-11-16.34.moin.txt
[16:53] <jjohansen> thanks tyhicks
[16:53] <sarnold> thanks tyhicks!
[16:53] <sbeattie> tyhicks: thanks.
[16:54] <mdeslaur> thanks tyhicks!


[12:21] <cjohnston_> mhall119: next week
[12:22] <pace_t_zulu> mhall119: i'm getting into django :)
[12:30] <cjohnston> pace_t_zulu: awesome.
[12:31] <pace_t_zulu> cjohnston: loco.ubuntu.com is django right?
[12:36] <cjohnston> yes
[12:48] <mhall119> pace_t_zulu: great!
[12:49] <mhall119> pace_t_zulu: how's he new job?
[15:53] <pace_t_zulu> mhall119: excellent
[15:54] <pace_t_zulu> mhall119: going to use django for a project ... first time with it ... my new boss is enthusiastic about different languages, frameworks, and platforms
[15:54] <pace_t_zulu> so i don't have to stress about proving django's merits
[15:54] <pace_t_zulu> like i might have in my previous job
[15:54] <mhall119> nice, good luck and let us know if you have any questions
[15:55] <mhall119> #django is also very helpful
[16:05] <pace_t_zulu> mhall119: already there ;)
[16:05] <pace_t_zulu> mhall119: i won't have a chance to really dig in for a few weeks
[16:05] <pace_t_zulu> different project in the pipeline with a deadline
[21:41] <mhall119> cjohnston: james_w: https://code.launchpad.net/~mhall119/summit/optimizations/+merge/77758
[21:44] <mhall119> brings the query count on /uds-p/ down from ~120 to ~20, and on /uds-p/2011-10-31/ down from ~120 to ~45


[19:09] <daftykins> ooooh what a week
[19:10] <daftykins> it would seem news of my entering the dentist IT scene has other small practices wanting to jump ship to me from a local firm that charges £££
[19:10] <daftykins> i suppose i'm... going to take a bite out of the sector *cough*
[19:47] <zxmpi> ain't that the tooth :-P
[19:48] <daftykins> :D
[20:32] <penguin42> nice
[20:36] <daftykins> funny thing is i've been dealing with dental practice software for all of 5 minutes, heh
[20:37] <daftykins> although today i discovered that this shipped system from the provider is an intel 8th gen i7 PC which they'd set to the 'high performance' power profile, i.e. it'll just suck power to sit there idle - total waste
[20:37] <daftykins> i... improved that :D
[20:38] <penguin42> does it actually do that when it's really idle - I thought that was more about how it ramped up when it wasn't quite idle?
[20:39] <daftykins> certainly does, task manager on Windows 10 can even show you it sitting there @ max turbo, static
[20:40] <zxmpi> could it be the software sucks and when it has a database a few years old it will need all that cpu to crawl along?
[20:40] <daftykins> well the supplied system purely handles images from this new 3D x-ray and scanning machine, the practice server is a separate PC
[20:41] <daftykins> so until September it'll certainly be doing next to nothing
[20:41] <daftykins> given they had us do a bit of a dance in meeting system specs for the PC inside the surgery, it horrifies me that they insist a dedicated one must be used
[20:42] <daftykins> it has an nvidia GTX 1650 in it, too... the guy told me he encountered a client who removed the graphics card once and wondered why stuff stopped working, hah
[20:46] <daftykins> ok time for early bed, gonna pop in and do some more tomorrow
[20:47] <daftykins> g'night \o
[21:02] <zxmpi> o/


[14:13] <DavidBrooke> are there any settings for the notification area? I would like to be able to have it clear the notification after a certain amount of time.
[17:18] <swiss> DavidBrooke: i know what you mean... i have a lot of notifications that build up and are a pain to clear
[17:33] <bjsnider> DavidBrooke, the answer is no
[17:38] <bjsnider> DavidBrooke, there's an argument for turning off notification area plugins that are filling up the area with messages you don't care about though
[18:30] <xente> Does anyone know how to prevent unfocused windows from dimming in GNOME?
[18:45] <jw1200w> is bug reporting on gnome3 launchpad restricted to members?
[18:46] <bjsnider> some of these questions sound a bit like 'can i somehow stop gnome from being gnome?'
[18:47] <xente> if gnome can't do what its users want..maybe that's a good thing
[18:52] <bjsnider> it can't be all things to all people, and it's also by no means a finished product
[18:52] <bjsnider> and i don't believe it will ever be as customizable as gnome 2 was
[18:53] <xente> except for minor things, I personally like it (recently switched from Unity)
[19:15] <arpu> hello
[19:16] <arpu> gedit plugins dashboard does not work ?  gedit and gedit plugin versions http://paste.railsbox.eu/show/759/
[19:17] <arpu> ricotz, ^^
[20:01] <lubuntos> Hi everyone, I have an HP Desktop Quad 2.2 Ghz with 1GB ram running Lubuntu right now and I would like to install Ubuntu Gnome 13.10. What's your suggestions? Will it work smoothly?
[20:02] <roasted> hard to say. it'd definitely be heavier than lubuntu...
[20:02] <roasted> what sort of GPU do you have
[20:02] <lubuntos> GPU?
[20:02] <roasted> graphics card
[20:02] <roasted> (graphics processing unit)
[20:02] <lubuntos> a alright thanks
[20:03] <lubuntos> I dont know :P I have to go upstairs and see.
[20:04] <roasted> it's hard to say. GNOME can be a little heavy on resources. You say a quad proc, that sounds more than enough, 1GB is mehhhh
[20:04] <lubuntos> The problem is that Lubuntu 13.10 showed to me some mirror bugs that I don't know how to fix. Graphics on letters while reading, are messing up a bit, and I have to hover them with my mouse sometimes to see the text correctly.
[20:04] <roasted> but if the GPU is a workhorse I'm sure it would do fine
[20:04] <roasted> yeah
[20:04] <roasted> I don't know - I don't use Ubuntu GNOME on my main machine. What I do use it on is an i5 with a nice Intel GPU and it runs decent.
[20:04] <roasted> it's also on an SSD and 8GB of RAM...
[20:04] <roasted> so it SHOULD run half decent...
[20:05] <lubuntos> hmmm
[20:05] <lubuntos> I was waiting for ubuntu gnome, because I dont like unity.
[20:05] <lubuntos> :P
[20:05] <lubuntos> I'll see man, thanks! (Thinking now)
[20:06] <roasted> in my experience Gnome has ran a little better than Unity
[20:06] <roasted> not by an epic landslide, but noticeably better
[20:06] <roasted> but NOT like Lubuntu though
[20:06] <roasted> LXDE is crazy stupid light
[20:06] <lubuntos> yeap
[20:06] <lubuntos> I got bored of lubuntu.
[20:06] <roasted> yeah Lubuntu is admittedly a little poor on features :(
[20:06] <roasted> I run it on a laptop at home but that laptop is also terible so I expect very little out of it
[20:07] <lubuntos> my laptop is 6 years old, i can't format it again :P it gets stucked when I press any button while formatting.
[20:09] <lubuntos> i'll see, i just dont want to change os all the time, i already did 3-4 formats to decide which os to have. but am addicted to ubuntu, especially now with gnome.
[20:09] <lubuntos> had winblows 7 for a bit, then winblows xp, then ubuntu, then lubuntu, now ubuntu gnome :P i will see
[20:10] <roasted> yeah, that's why I try to mess around with VMs whenever possible.
[20:10] <roasted> although having root and home on different partitions helps too
[20:10] <roasted> I can blast a new OS over USB 3.0/SSD in a matter of 3-4 minutes, share out the same home directory, back in business
[20:10] <lubuntos> heheh
[20:11] <lubuntos> I'll buy a new laptop this year, so my main pc would be my laptop. desktop would be only for me, cuz my family doesnt know nada!
[20:12] <lubuntos> roasted, thank you very much
[20:12] <lubuntos> am gonna give it a try
[20:12] <roasted> no problem
[20:12] <roasted> good luck :D
[20:12] <lubuntos> even with 1gb ram
[20:12] <lubuntos> :P
[20:12] <roasted> there's other options out there, by the way
[20:13] <roasted> ones that are Ubuntu based yet not part of the 'official' Ubuntu brand
[20:13] <lubuntos> running through USB and see
[20:13] <roasted> Zorin, elementary OS (personally using this now). Just keep your options open.
[20:13] <lubuntos> i love ubuntu gnome ;p planning to buy more ram one day soon
[20:13] <roasted> there's a distro and desktop environment for everybody :D
[20:13] <SonikkuAmerica> lubuntos: http://downloadmoreram.com/ :) just for lulz
[20:13] <roasted> yeah, I like Gnome a lot too. Solid DE. It has it's times where I find myself elevating to a homicidal rage, but it's far less of an issue than what I experience on KDE or Unity. :P
[20:14] <lubuntos> heheheh
[20:14] <lubuntos> IRC the best help in the world.
[20:14] <lubuntos> I missed when I was 14 :P anyway
[20:14] <roasted> sometimes it's slow, but most times it's nice. :D
[20:15] <lubuntos> i'll give it a try :P have a nice day/night roasted :P here is 22:15 - Cyprus
[20:16] <lubuntos> SonikkuAmerica :P
[20:16] <lubuntos> lol
[20:17] <SonikkuAmerica> lubuntos: :)
[20:18] <lubuntos> good night guys! :P
[20:18] <lubuntos> see you around
[20:18] <lubuntos> =]
[20:45] <Guest30733> can i add proxy username  and password from system settings ?
[20:50] <millhouse513> hello