[12:19] <manchicken> LMAO, Circuit City says they're cool with me testing out this machine with the live CD.
[12:32] <Riddell> nixternal: ping, can you do whatever tidying up is needed and publish http://fridge.ubuntu.com/node/1085 ?
[02:02] <nixternal> Riddell: posted!
[02:07] <jdong> lastlog jdong
[02:07] <jdong> grr
[02:07] <jdong> Riddell: it's a Ruby-on-rails wrapper over a set of pbuilders, automatically triages backports builds and spits out build logs and i386 debs
[02:07] <jdong> used for testing purposes
[02:10] <nixternal> Riddell: is amarok 1.4.7 being packaged yet? if not, where is the updated tarball?
[02:10] <nixternal> nevermind, found it
[03:16] <nixternal> hey, with Konqueror you don't need to install the java plugin do you?
[03:17] <nixternal> simply installing Sun Java 6 bin works with Konqueror right
[05:56] <kazuma_> hey
[05:56] <kazuma_> stdin
[05:56] <kazuma_> are you there? xD
[05:56] <kazuma_> someone can help me?
[06:00] <robotgeek> kazuma_: for support, please go to #kubuntu
[09:00] <cynics> apachelogger_: congrats  :)
[09:11] <Hobbsee> nixternal: i'm presuming you found it, but it's in the archive now
[09:38] <Riddell> anyone able to test amarok 1.4.7 in gutsy and/or fiesty-backports
[09:38] <_StefanS_> Riddell: uhm, I can
[09:39] <_StefanS_> Riddell: btw, I'm giving up on that networkstatus thingy, seems like it involves far too much compared to what we get out of it (nice error messages..)
[09:39] <Hobbsee> Riddell: WFM
[09:39] <Hobbsee> for the little that i do with amarok
[09:44] <Riddell> "WFM"?
[09:44] <Riddell> oh, works for you
[09:44] <Riddell> we need kdebluetooth
[09:45] <Hobbsee> yes
[09:49] <Riddell> it's blocked on obexftp MIR though
[09:50] <_StefanS_> Riddell: so you want me to test that amarok ?
[09:52] <Hobbsee> Riddell: can you poke someone to do it?
[09:52] <Riddell> please
[09:52] <Hobbsee> or just upload it, and let it sit in depwait?
[09:55] <Riddell> yes, I'll upload it now
[09:55] <Riddell> I've already poked pitti several times
[09:56] <Hobbsee> he does go on leave today, though
[09:56] <Hobbsee> Riddell: oh, i guess tollef isnt doing any NEW either.
[09:56] <Hobbsee> how frustrating
[09:56] <Riddell> today?
[09:56] <Riddell> oh, but only for two days
[09:57] <Hobbsee> Riddell: wedding.  unknown how long for
[09:57] <Riddell> it's two days
[09:57] <Hobbsee> Riddell: i'd expect that stuff isnt public
[09:57] <Riddell> then he's back for a week
[09:57] <Riddell> then he's on honeymoon, and he's promised me to do it before honeymoon
[09:57] <Riddell> well, if he has any stalkers, this is the place for them to be :)
[09:58] <Hobbsee> ahhh....
[09:58] <Hobbsee> heh
[10:00] <Riddell> what needs done in New?
[10:01] <Hobbsee> the obexftp that you mentioned before?
[10:03] <Riddell> needs a main inclusion report approved
[10:04] <Hobbsee> oh, sorry.  that's what i meant.  i think
[10:07] <Riddell> they're for pitti to do, sometimes iwj
[10:07] <Riddell> beta6 uploaded
[10:07] <Hobbsee> oh, so my brain is just totally broken.
[10:10] <_StefanS_> Hobbsee: you're not the only one :) - mine has been for a year or so ... gotta get.. some sleep.
[10:10] <_StefanS_> Hobbsee: kids.
[10:10] <Hobbsee> heh
[10:11] <_StefanS_> my wife is one week overdue, and we already have a girl which is turning 1 year this sunday.
[10:11] <Hobbsee> wow :)
[10:12] <_StefanS_> I wouldn't be surprised if it all happened at the same time :-/
[10:12] <_StefanS_> He's 4400grams at the moment, so we would like him to come out soon.
[10:14] <_StefanS_> Riddell: so you have me on ignore, or should I test that Amarok ? :)
[10:14] <Riddell> _StefanS_: please do
[10:15] <_StefanS_> Riddell: is it in backports already?
[10:15] <Riddell> _StefanS_: yes, should be (1.4.7)
[10:15] <_StefanS_> right. testing it now.
[10:16] <_StefanS_> Riddell: seems good.
[10:17] <_StefanS_> Riddell: mp3's is fine, and visualization works
[10:17] <Hobbsee> is there anything else we want shoved in before UVF?
[10:18] <Riddell> _StefanS_: great, thanks
[10:18] <_StefanS_> I would just like OOo and acroread, nspluginviewer to work. But I guess that someone is working on it
[10:19] <_StefanS_> all related to that gtk bug
[10:19] <_StefanS_> Riddell: np
[10:19] <Hobbsee> _StefanS_: i have an email in my inbox about that, actually.  something about it actually needing to be fixed in the affected apps
[10:19] <Hobbsee> but that's post-UVF
[10:19] <Riddell> k3b-i18n
[10:19] <Riddell> is old
[10:20] <_StefanS_> Hobbsee: I know.. I just dont want anyone to forget about it
[10:20] <Riddell> neversfelde|mobi: do you know if kwwii sent you the banner?
[10:20] <Riddell> hmm, debian has kmplayer 0.10.0~pre2, I wonder if that's suitable
[10:21] <neversfelde|mobi> hi
[10:21] <Riddell> fabo: is that stable?
[10:21] <neversfelde|mobi> Riddell: I have not checked it today, will do in the afternoon
[10:23] <Riddell> eek strigiapplet is old
[10:51] <virgilio>  hi all, I just installed gutsy alpha 4 and updated all the system. After that I've tried to install kubuntu-desktop package to switch to kubuntu, but the proccess can't start due to a dpendency problems with adept
[10:53] <Hobbsee> Riddell: yes, adept-notifier does not start now
[10:53] <Hobbsee> er, install
[10:53] <Riddell> yeah, needs mvo's new update-notifier
[10:54] <virgilio> Riddell: ok, I'll wait to the new version
[10:54] <virgilio> thanks for the info
[10:56] <Riddell> watch for 0.59.1 appearing
[11:43] <Riddell> kwwii: did you send the banner?
[11:44] <_StefanS_> Riddell: did you get that info about networkstatus ? I'm kinda leaving it for now, since it made a lot of issues I think.
[11:44] <_StefanS_> Riddell: dont think its worth it
[11:45] <Riddell> what issues did it make?
[11:45] <_StefanS_> Riddell: knetworkmanager stopped working since it depended on stuff in networkstatus
[11:45] <Riddell> whee
[11:46] <_StefanS_> Riddell: I havent investigated why exactly.. (1) either a recompile is needed (unlikely) , (2) suse has changes to knetworkmanager that make networkstatus split work also
[11:46] <_StefanS_> after that I sort of gave up...
[11:46] <_StefanS_> :)
[11:47] <_StefanS_> so.....
[11:48] <kwwii> Riddell: no, I never got a response - I will sendit asap if needed
[11:49] <Riddell> kwwii: yes, please do (conference is a week on saturday I think, so no mad panic)
[11:49] <kwwii> Riddell: right, I'll head up to the post now then
[12:16] <kwwii> Riddell: sent
[12:31] <Riddell> ScottK: the zekr error means one of the soyuz checks was rejected, but I don't know which one
[12:31] <Riddell> that package did have a tonne of lintian errors though
[12:32] <Riddell> or actually no, I'm thinking of another package
[12:37] <\sh> moins kwwii
[12:37] <kwwii> \sh: moin moin
[12:39] <\sh> Riddell, anything else which needs updates for gutsy?
[12:39] <Riddell> \sh: strigiapplet could do with a sync from debian
[12:39] <Riddell> needs someone to test if the sync is ok
[12:41] <\sh> Riddell, 0.5.2 from unstable?
[12:41] <Riddell> yes
[12:41] <Riddell> which seems to be above upstream, but never mind
[12:41] <\sh> building and testing
[01:13] <Riddell> dddddd
[01:25] <Lure> Hobbsee: update to knetworkmanager 0.2 release would be great before UVF (I did not manage to do it yesterday as I hoped)
[01:25] <Hobbsee> Lure: knetworkmanager | 1:0.2ubuntu1-0ubuntu1 | http://archive.ubuntu.com gutsy/main Sources
[01:25] <Hobbsee> ?
[01:25] <Hobbsee> and that's slightly strange versioning...
[01:26] <Lure> Hobbsee: 0.2~r686534-0ubuntu1 here...
[01:27] <Hobbsee> hm
[01:28] <Riddell> it's network-manager-kde now
[01:28] <Hobbsee> ahhh...
[01:29] <Hobbsee> tonio's done the weird version number.
[01:35] <\sh> Riddell, works
[01:36] <Riddell> \sh: great, thanks, I'll do the sync
[02:03] <Hobbsee> oh, not chandru again
[02:03] <Hobbsee> i remember replying to that thread last time
[02:03] <mhb> good afternoon
[02:03] <Hobbsee> hi mhb
[02:03] <Riddell> where?
[02:04] <Hobbsee> kubuntu devel ML
[02:05] <mhb> _StefanS_: thanks for the ideas, I really like the green leaves SVG. Not exactly the thing for the default desktop, but if it would be possible to ship it with other wallpapers, that would be great.
[02:05] <mhb> _StefanS_: do you own the copyright to that? Or what license is it?
[02:06] <_StefanS_> mhb: uhm I can look it up
[02:06] <_StefanS_> mhb: found it somewhere on kdelook I think
[02:07] <_StefanS_> mhb: http://www.kde-look.org/content/show.php/Palm?content=37708
[02:08] <ScottK> Riddell: Thanks for looking into zekr (the failed to upload).  I guess I'll wait and see what gets figured out.
[02:10] <mhb> _StefanS_: thanks
[02:23] <ScarFreewill> where is up in donlphin?
[02:24] <ScarFreewill> ah ok I can add it. wil it be released without up in the defualt toolbar?
[02:28] <Riddell> ScarFreewill: you can click on the directory you want to go to in the address bar?
[02:28] <ScarFreewill> yes I like the way that works very much
[02:29] <ScarFreewill> confusing at first, but I fould my way very fast
[02:29] <Hobbsee> Riddell: there's a mail for unmoderating on the ML, btw
[02:29] <Hobbsee> if you didnt already
[02:32] <Riddell> which mailing list?  I moderate several dozen
[02:34] <Hobbsee> Riddell: kubuntu-devel
[02:34] <Hobbsee> Riddell: (and can i have access to k-d moderation, precisely for this raeson?)
[02:34] <Hobbsee> right, listadmin is *really* nice.
[02:35] <_StefanS_> bbl..
[02:40] <Riddell> neversfelde|mobi: kwwii says banner is on its way
[02:41] <neversfelde|mobi> Riddell: perfect
[02:41] <neversfelde|mobi> thx
[02:41] <Riddell> Hobbsee: there's nothing waiting for moderation except spam and mhb's initial posting
[02:42] <Hobbsee> Riddell: oh right, i thought there was more
[02:42] <Riddell> what were you expecting?
[02:43] <Riddell> I can give you the admin password if you want, or even add you as an admin, but mhb's posting has been the first issue in months except for spam
[02:44] <Hobbsee> Riddell: and one i posted a while ago
[02:44] <Hobbsee> Riddell: dunno.  not much.  i just know it's helpful to be able to accses such things
[02:44] <Hobbsee> particularly with the listadmin, which doenst make it such a pain in the neck to do
[02:45] <Riddell> what's that?
[02:45] <Hobbsee> Riddell: man listadmin
[02:45] <Riddell> No manual entry for listadmin
[02:46] <Hobbsee> try installing it first
[03:19] <Riddell> Hobbsee: what's the status of bug 131552?
[03:19] <ubotu> Launchpad bug 131552 in live-initramfs "Please sync live-initramfs (universe) from Debian unstable (main)" [Wishlist,Confirmed]  https://launchpad.net/bugs/131552
[03:20] <Hobbsee> Riddell: please approve it
[03:20] <Hobbsee> Riddell: kmos decided to screw around with the bug - a MOTU has filed that.
[03:20] <Hobbsee> (siretart)
[03:21] <Riddell> Hobbsee: the bug doesn't say what the ubuntu change is and why it's ok to drop it
[03:21] <Hobbsee> siretart: ^
[03:21] <Hobbsee> Riddell: siretart, the filer, is also the last uploader, so it should be OK.  but you'd have to take that up with him
[03:38] <Riddell> Hobbsee: do people go through and confirm archive-admin sync requests?
[03:39] <Hobbsee> Riddell: for non-MOTU sync requests?  no
[03:39] <Hobbsee> Riddell: motu's confirm their own requests, obviously
[03:41] <Riddell> but if the request is from a mostly random person?  e.g. bug 130619 is from the debian packager
[03:41] <ubotu> Launchpad bug 130619 in ispell-et "Please sync ispell-et (main) from Debian unstable (main)" [Undecided,New]  https://launchpad.net/bugs/130619
[03:42] <Hobbsee> Riddell: then they havent followed protocol, and should be shoved back to u-u-s being subscribed.
[03:42] <Hobbsee> Riddell: use your discression about the debian maintainer though - but they're not supposed to do that
[03:43] <ScottK> It would be helpful if not just anyone was allowed to subscribe the archive-admins or if motu/core-devs could unsub archive-admin so there we less cruft presented to you guys.
[03:44] <Riddell> Hobbsee: or ubuntu-main-sponsors?
[03:44] <Hobbsee> ScottK: i think there are plans for that.  somewhere
[03:44] <Hobbsee> Riddell: yeah
[03:46] <Riddell> Hobbsee: what is bug 131911 actually asking for?
[03:46] <ubotu> Launchpad bug 131911 in network-manager "tries to clear nscd hosts cache even when it's not installed" [Undecided,Triaged]  https://launchpad.net/bugs/131911
[03:47] <Hobbsee> Riddell: oh...so *that's* why the other bug didnt get closed.  a likely case of "hobbsee cant type bug numbers"
[03:49] <ScarFreewill> when i right click the desktop, don't click the popupmenu (just click some where else so it disapears) then if you move the mouse its like your holding in click, and the grag bar it makes when your draging doesn't dissapear. does this happen to you too? (kde4)
[03:51] <Riddell> I'm not running kde 4 just now
[03:51] <Riddell> but that doesn't sound like a critical bug for kde 4 :)
[03:56] <ScarFreewill> yes :) I'm just wondering if its me because I had to hack more than one deb file to get it installed..
[03:58] <bddebian> Heya
[03:58] <Riddell> ah, bddebian
[03:59] <Riddell> you filed bug 132598 but didn't set it to confirmed
[03:59] <ubotu> Launchpad bug 132598 in marble "[Sync Request Universe]  marble 0.3-2" [Undecided,New]  https://launchpad.net/bugs/132598
[03:59] <bddebian> Riddell: Sorry
[04:00] <Riddell> bddebian: but I presume your intention is that it's ok to sync?
[04:03] <bddebian> Riddell: Checking to make sure..
[04:03] <Hobbsee> Riddell: yeah, that's OK
[04:03] <Hobbsee> Riddell: i filed the dupe
[04:03] <Hobbsee> bddebian: you do not like the request sync script?
[04:04] <Riddell> bddebian: similarly for tkdesk, qca, python-biopython?
[04:04] <bddebian> Hobbsee: Doesn't work for me currently and no I don't particularly like it :-)
[04:04] <bddebian> Riddell: Ah yes
[04:04] <Hobbsee> bddebian: awww
[04:04] <Riddell> thanks
[04:05] <Hobbsee> bddebian: unsure.  most people just use the script, y'know.
[04:06] <Riddell> bddebian: I don't know either, but it seems easiest if I just have to look for confirmed ones
[04:06] <bddebian> Maybe I'm just too old and crusty to do this anymore :-(
[04:06] <Riddell> ?!
[04:06] <Riddell> not at all
[04:07] <ScottK> bddebian: Nah.  Just confirm it.  The archive guys (some of them anyway) only look for certain bug statuses.
[04:07] <ScottK> As an example, I know that pitti will never see a backport request that isn't status "In progress".
[04:09] <bddebian> Damn I wish I would've known that because I needed qca to get the new psi in :'-(
[04:09] <Hobbsee> Riddell: oh, for https://bugs.launchpad.net/ubuntu/+source/ispell-et/+bug/130619 please go and blast him (q-funk) in person on -motu.  he appears to believe that he's exempt from requests or something.
[04:09] <ubotu> Launchpad bug 130619 in ispell-et "Please sync ispell-et (main) from Debian unstable (main)" [Undecided,New]
[04:09] <Hobbsee> Riddell: he bitched loudly at me for telling him that it was unacceptable to do that, but you may have more luck as an archive admin
[04:09] <Riddell> bddebian: qca2 has been in for a while
[04:10] <Hobbsee> oh, hmm, he's not online atm.
[04:10] <bddebian> Riddell: A high enough version for the psi in Unstable?
[04:11] <Riddell> bddebian: same version as debian experimental has
[04:11] <bddebian> Hmm, weird
[04:12] <Riddell> psi in debian unstable needs qca-dev, which is qca 1
[04:12] <bddebian> Oh I was trying to build the rc2 from Debian Experimental.  Still should have worked?
[04:12] <Riddell> should do, we have libqca2-dev
[04:13] <Riddell> maybe you tried it before we had qca 2 through New
[04:13] <Riddell> oh, wait, it's still in New
[04:13] <bddebian> hah~!
[04:13] <bddebian> :-)
[04:14] <Riddell> I have it installed since I packaged and uploaded it, how confusing
[04:14] <Riddell> you'll need to poke someone to approve it
[04:14] <bddebian> I hate when that happens
[04:14] <bddebian> Well it's too late for new psi now anyway
[04:14] <Riddell> seb128 being the only candidate around
[04:14] <Riddell> no it's not
[04:14] <bddebian> It's not?
[04:14] <Riddell> UVF isn't until this evening
[04:15] <Riddell> grab qca2 from http://people.ubuntu.com/~ubuntu-archive/queue/gutsy/new/
[04:15] <bddebian> Well I'm not sure I'm in any position to ask for favors from core-devs :-)
[04:15] <Riddell> install and test your psi, then upload
[04:28] <manchicken_> We get to find out what gender the baby is today.
[04:29] <Riddell> not keeping it a surprise?
[04:29] <manchicken_> Naw, it's hard to set up their Kubuntu machine as pink or blue if you wait ;)
[04:30] <ScottK> Riddell: It's always a suprise once.  It's just a question of when you get it.
[04:30] <Riddell> so not gender stereotyping him/her at all then :)
[04:30] <ScottK> That and the finding out in advance isn't 100%, so that's sometimes extra fun.
[04:30] <manchicken_> Riddell: when did I ever say I wouldn't? :)
[04:34] <siretart> Riddell: the ubuntu change in live-initramfs has been merged in debian
[04:34] <siretart> Riddell: the only change was dropping the transitional 'casper' binary package
[04:34] <siretart> live-initramfs is used for fai
[04:35] <Riddell> siretart: ok, thanks
[04:35] <Riddell> siretart: fai?
[04:36] <Riddell> [BLACKLISTED]  live-initramfs_1.91.4-1ubuntu1
[04:36] <siretart> Riddell: that can be removed, since the casper binary package has been dropeed
[04:40] <Riddell> groovy, done
[04:59] <bddebian> OK qca2 is a pig :(
[05:01] <Riddell> in which way?
[05:05] <bddebian> Taking forever to build :)
[05:06] <Riddell> you have the .debs?
[05:07] <bddebian> Not yet, I'm building them myself
[05:07] <bddebian> Of course seb said he New'd it anyway :-)
[05:07] <Riddell> why not just use the .debs?
[05:08] <bddebian> Because I'm a purist :-)
[05:08] <bddebian> Actually I think I'm insane
[05:08] <Riddell> oh dear
[05:15] <Riddell> yuriy: is this you? http://kubuntuforums.net/forums/index.php?topic=3085847.msg84477#msg84477
[05:15] <yuriy> Riddell: heh, no. i'm GameManK
[05:19] <Riddell> ok, didn't think so
[05:23] <bddebian> Gah screw this
[05:23] <bddebian> Riddell: Where can I get at the debs?
[05:26] <bddebian> NM, I'll pull them from debian
[05:34] <Riddell> 15:15 < Riddell> grab qca2 from http://people.ubuntu.com/~ubuntu-archive/queue/gutsy/new/
[05:45] <bddebian> Doh man, I am really out of it today, sorry Riddell
[05:53] <bddebian> Holy crap, psi isn't exactly a "quick" build either :)
[06:14] <Riddell> nixternal: grr, now I have flash on my amd64 machine, annoying adverts everywhere thanks to you!
[06:14] <nixternal> lol
[06:14] <nixternal> it worked though right?
[06:15] <nixternal> I needed to make sure that it worked for the doco...I am getting ready to update the current package so it can start getting bug reports and translations
[06:21] <Riddell> nixternal: certainly did, I wonder why it's so unknown
[06:21] <nixternal> I have no idea, I messed around for hours with all of the other howtos and they were a pita
[06:21] <Riddell> also it requires command line use, which should be fixed
[06:21] <Riddell> can't be hard to fix
[06:21] <nixternal> that could be fixed in the package?
[06:22] <Riddell> postinst script to run nspluginwrapper?
[06:22] <nixternal> yup
[06:24] <nixternal> have the script run uname -a, check for x86_64, and if it is true, then run nspluginwrapper
[06:27] <Riddell> then hopefully some dcop can get konqueror to reload its plugins
[06:41] <nixternal> ahh ya, forgot about having konqi reload...a reboot would fix that though :)
[06:41] <Riddell> erk, reboot?
[06:41] <nixternal> how do you create a .pot file from a .directory or a .desktop file?
[06:41] <nixternal> hehe
[06:41] <Riddell> how would that help?
[06:41] <nixternal> ya, or restart X...konqi reloads all plugins on startup
[06:42] <Riddell> so just restart konqi?
[06:42] <jjesse> you can't just force a restart of konqi you have to restart x?
[06:42] <Riddell> but there should be dcop for it
[06:42] <jjesse> that seems silly
[06:42] <nixternal> no, restarting konqi only restarts the khtml...konqi is preloaded
[06:42] <Riddell> although that would have to run as the user, so that wouldn't work
[06:42] <nixternal> ya
[06:42] <jjesse> so is konqi as much a part of the "OS" as IE is :)
[06:42] <nixternal> a dcop call would probably be the easiest
[06:42] <nixternal> jjesse: yup :)
[06:42] <nixternal> well no
[06:42] <nixternal> it is just preloaded
[06:42] <Riddell> nixternal: .desktop in KDE or elsewhere?
[06:43] <nixternal> in the docs
[06:43] <nixternal> that way there people will see the translated strings in the KHC sidebar/tree
[06:43] <nixternal> I can't believe nobody has ever filed a bug on that
[06:47] <Riddell> nixternal: if it's docs then you may be best doing what gnome does (uses intltool) if their docs also have .desktop files
[06:47] <Riddell> nixternal: KDE uses /usr/lib/kubuntu-desktop-i18n/createdesktop.pl in ways you can find in /usr/share/cdbs/1/class/kde.mk
[06:47] <nixternal> ya, I am reading that now
[07:17] <nixternal> kubuntu-docs building as we, or I, speak :)
[07:18] <kwwii> keep talking then, it might take a while
[07:25] <nixternal> hehe
[07:26] <nixternal> Riddell: I just uploaded kubuntu-docs updated package to my ppa...man I love that, it allows a nice test before you go an upload it to main...I will keep you updated here shortly
[07:31] <Riddell> groovy
[07:32] <nixternal> if only you could delete the old stuff from your ppa, then it would be perfect
[07:33] <nixternal> and I created the pot files for .desktop and .directory
[07:34] <Riddell> that's due to be fixed
[07:34] <Riddell> how did you do that?
[07:36] <nixternal> intltool :)
[07:37] <nixternal> cp systemdocs.desktop systemdocs.desktop.in && mkdir po && cd po && echo systemdocs.desktop.in > POTFILES.in && intltool-update --pot --gettext-package=systemdocs
[07:43] <nixternal> do we have anything that needs to get done asap or something that needs some love right now?
[07:44] <Riddell> package qtjambi!
[07:44] <nixternal> haha
[07:44] <Riddell> actually, for an easier time, package the qt accessibility bridge and qdasher from labs.trolltech.com
[07:44] <nixternal> ya, jambi is no joke
[07:45] <Riddell> from helio's blog it sounded painful
[07:45] <nixternal> I think Mandriva is the only distro with a package so far
[07:59] <nixternal> Riddell: http://ppa.dogfood.launchpad.net/nixternal/ubuntu/pool/main/k/kubuntu-docs/kubuntu-docs_7.10-2.dsc
[08:30] <manchicken_> It's a girlchicken.
[08:34] <nixternal> manchicken: CONGRATS!
[08:34] <nixternal> Riddell: is there a way to browse Trolltech's svn?
[08:35] <nixternal> I am working on the qdbusbridge package right now
[08:38] <manchicken> Thanks :)
[08:41] <Riddell> nixternal: checkout the whole thing
[08:41] <nixternal> ya, I already have it
[08:41] <nixternal> should I check out just qdbusbridge, or should I check out everything in accessibility?
[08:43] <ScottK> manchicken: Congratulations.  Catch up on sleep now, you won't get any once she's a teenager.
[08:43] <Riddell> or baby
[08:43] <nixternal> hehe
[08:43] <ScottK> That too.
[08:44] <ScottK> Different reasons though.
[08:44] <nixternal> sleepless nights for a baby doesn't last as long as sleepless nights as a teenager though :)
[08:44] <nixternal> my daughter is approaching "teenager" and I am hating every minute of it
[08:45] <ScottK> nixternal: How old?
[08:46] <nixternal> 11 in October
[08:47] <ScottK> IME (our oldest is 15) the angst peaks around 14 and then the boys kick in.  I don't think it ends until the leave the house.
[08:47] <nixternal> ouch
[08:47] <nixternal> haha
[08:47] <ScottK> YMMV.
[08:47] <nixternal> well at almost 11, my daughter is already boycrazy
[08:48] <nixternal> she keeps asking for a "MySpace" account..I let her know hackers don't use myspace :)
[08:48] <ScottK> Yes, our oldest was too (#2 at 13 isn't so much).
[08:48] <ScottK> nixternal: Look up the terms of service for myspace and then explain she's to young.
[08:48] <ScottK> You have to be 13 to get an account.
[08:49] <ScottK> Legally.
[08:49] <nixternal> heck no, I told her while she still lives at home, or is under 18, she don't get to have one
[08:49] <ScottK> Ah.
[08:49] <nixternal> and I told her if I find out about one, then her arse is grass, and I am the lawnmower :)
[08:49] <ScottK> Our rule for the oldest one is that we have to be on her friends list so we can review it whenever we feel like it.
[08:50] <nixternal> it isn't that I don't trust MySpace, it is because I can't stand MySpace
[08:50] <ScottK> We also reserve the right to quiz her about who else is on her list and yank the account if we don't like the answers.
[08:50] <ScottK> Ah.
[08:50] <ScottK> Well I don't like it either.
[08:50] <nixternal> I am trying to groom a little hacker here :D
[08:51] <nixternal> right now she is annoying me by wanting a Mac
[08:51] <ScottK> Of course #2 daughter set up an account while at a friends house last year.  She still has no idea how I found out.
[08:51] <nixternal> lol
[08:51] <ScottK> Get her a Mac and put Kubuntu on it.  That'll show her.
[08:51] <manchicken> mhb: I proposed a bounty for the artwork issue.
[08:51] <nixternal> well she runs Edubuntu now
[08:51] <manchicken> My baby will have a System76.
[08:52] <nixternal> when I head out there for her birthday, I am going to give her Kubuntu with the edubuntu-kde desktop
[08:52] <manchicken> Those mini Koalas look pretty badass.
[08:52] <nixternal> hehe
[08:52] <nixternal> I told her if she completes a grade with all A's, I will get her a Mac
[08:52] <ScottK> #2 daughter also still has neither a myspace account nor prospects for one due to her actions last year.
[08:52] <ScottK> Facebook is the latest challenge.
[08:53] <nixternal> I don't even want to know..I am not looking forward to such actions :)
[08:53] <manchicken> No child of mine will be running proprietary OS' :P
[08:53] <nixternal> Facebook I will probably let her do, but I am not hip to these "Social" sites
[08:53] <nixternal> my daughter started out on Slackware when she was 5 :)
[08:54] <nixternal> that is all we had in the house at that time was Slack, then she got a taste of Debian and SUSE
[08:54] <manchicken> I just don't see any need to buy an expensive Mac to run GNU/Linux when System76 machines are perfectly reasonable, and they're OEM.
[08:54] <manchicken> We just need to get system76 to start giving more OS options now :)
[08:54] <nixternal> so last year I finally built her a new computer and put Edubuntu on it...she has no problem editing sources.list and dist-upgrading now...she is getting quite good actually now
[08:55] <manchicken> Good stuff :)
[08:55] <ScottK> Cool.
[08:55] <manchicken> System76 says they'll have my order shipped within 4 business days.
[08:55] <nixternal> ya, but if she is on Kubuntu using KDE, then it is easier for me to help her
[08:55] <ScottK> Mine aren't so technical.
[08:58] <ScottK> Although #2 learned a little Python last year.
[08:58] <nixternal> hehe
[08:58] <nixternal> my daughter is messing with Logo a little right now
[08:58] <nixternal> she understands the basics of the command line, but she isn't hip to it yet
[08:58] <ScottK> I need a little shell scripting help here (speaking of which)...
[08:58] <manchicken> I just want my kids to be able to do normal computer tasks.
[08:58] <nixternal> I want mine to be lil hax0rz with the elite linux skillz :D
[08:58] <ScottK> What is in this init is: if [ -n "$SOCKET"] ; then ...
[08:58] <manchicken> If they want to learn programming that's fine, but I just don't want to expose them to software that forbids sharing while at the same time trying to teach them that sharing is a good thing.
[08:58] <ScottK> It's trying to do the then if the variable $SOCKET isn't defined.
[08:58] <ScottK> But that doesn't seem to do it.
[08:58] <ScottK> Suggestions?
[08:58] <nixternal> hrmm, I have had similar issues in the past when using dash instead of bash
[08:59] <manchicken> "" is always defined though, isn't it?
[08:59] <ScottK> I think I just got it.
[08:59] <nixternal> heh
[08:59] <manchicken> Wouldn't you want to, instead, do `if [ "$SOCKET" != "" ] ; then`?
[08:59] <ScottK> That would do it.  It works if SOCKET = '', just not if it doesn't exist.
[09:00] <\sh> ScottK,   -n string
[09:00] <\sh>               True if the length of string is non-zero.
[09:00] <ScottK> So my mistake was to make it undefined instead of empy.
[09:00] <ScottK> Cool.
[09:00] <\sh> ScottK, echo "$SOCKET" can give you a hint if $SOCKET is non-zero
[09:01] <\sh> oh you didn't even define $SOCKET?
[09:02] <ScottK> Yeah.  That was my mistake was to leave it undefined if I didn't want to specify a non-standard option instead of making it ""
[09:07] <ScottK> What's the difference between echo "$SOCKET" and echo $SOCKET?
[09:09] <manchicken> Not much with echo.
[09:09] <ScottK> OK
[09:09] <manchicken> You'll get the same
[09:09] <ScottK> How about in   if [ -n "$SOCKET"] ; then
[09:10] <manchicken> That will always be true.
[09:10] <ScottK> As long as the variable $SOCKET Is defined or always always?
[09:10] <manchicken> You'll want to do if [ -n $SOCKET ] ; then or if [ "$SOCKET" != "" ] ; then
[09:10] <manchicken> Well for `if [ -n "$SOCKET" ] ; then` the if will always evaluate true.
[09:11] <manchicken> Because even if socket is undefined, you still get a zero-length string, which is zero-length but still defined none-the-less.
[09:11] <ScottK> OK.  I do not undertand at all what the Debian maintainer intended then.
[09:11] <manchicken> "" is defined.
[09:12] <ScottK> Thanks again.
[09:12] <manchicken> heh
[09:12] <manchicken> np
[09:12] <manchicken> Stupid reality
[09:19] <\sh> hmm?
[09:19] <\sh> -n means non-zero
[09:20] <\sh> so if $SOCKET is not defined the term if [ -n "$SOCKET" ] ; then will give you  if [ -n "" ] ; which is false
[09:20] <\sh> because "" is zero string
[09:20] <\sh> and -n checks against non-zero strings
[09:20] <ScottK> Well for some reason it seems not to.
[09:21] <\sh> ScottK, pastebin the whole source somewhere
[09:21] <manchicken> \sh: I thought zero-length strings were still non-zero.
[09:22] <\sh> manchicken, nope....there is a difference...between -z and -n and a shell var in quotes which is empty will give "" and this is zero string
[09:22] <\sh> so -z "$SOCKET" would be true while -n "$SOCKET" will give false when $SOCKET is NIL
[09:22] <manchicken> Ah.
[09:22] <\sh> s/NIL/NULL/ forgive my pascalism
[09:22] <manchicken> So that's why I ignore shell in favor of Perl ;)
[09:23] <ScottK> \sh: http://paste.ubuntu-nl.org/33965/ line 34
[09:24] <\sh> -z and -n are stupid string comparison, while == and != are normally arithmetic ones
[09:25] <\sh> this crap init script is holy bullshit
[09:26] <\sh> # This can be set via Socket option in config file, so it's not required
[09:26] <\sh> if [ -n "$SOCKET" ] ; then
[09:26] <\sh>         DAEMON_OPTS="-p $RUNDIR/$NAME.sock $DAEMON_OPTS"
[09:26] <\sh> fi
[09:26] <\sh> DAEMON_OPTS="-x /etc/dkim-filter.conf -u $USER -P $RUNDIR/$NAME.pid $DAEMON_OPTS"
[09:26] <\sh> this is totally crap...it means the same
[09:26] <ScottK> so what I've trying to do is have the default behavior use what's in line 35, so I changed it to http://paste.ubuntu-nl.org/33966/ and that works.
[09:27] <\sh> ScottK, short question...is -p and -P the same or what does -P differently of -p?
[09:27] <ScottK> -p is the socket (TCP or Unix) and -P is the PID file.
[09:27] <\sh> ah
[09:28] <\sh> so he meant to do this:
[09:28] <\sh> SOCKET=$RUNDIR/$NAME.sock .... if [ -n "$SOCKET" ] ; then DAEMON_OPTS="-p $SOCKET"
[09:28] <\sh> lol
[09:28] <\sh> but he set SOCKET to $RUNDIR/$NAME.pid which is wrong and needs to PIDFILE and be set at -P line in DAEMON_OPTS
[09:29] <ScottK> So me, being pretty much a shell neophyte, was confused.
[09:29] <ScottK> I just knew it wasn't right.
[09:30] <\sh> ScottK, well the line itself is totally useless now, because SOCKET will always be zero (means empty)
[09:30] <\sh> and the script should never run the then clause
[09:30] <ScottK> That's what I was encountering.
[09:31] <\sh> 0r it will be set in /etc/default/dkim-filter
[09:31] <\sh> which could mean, $SOCKET is very well defined
[09:31] <\sh> what I would think he wanted to say with his comment "via Socket option in the config file"
[09:32] <\sh> # Include dkim-filter defaults if available
[09:32] <\sh> if [ -f /etc/default/dkim-filter ]  ; then
[09:32] <\sh>         . /etc/default/dkim-filter
[09:32] <\sh> fi
[09:32] <\sh> # This can be set via Socket option in config file, so it's not required
[09:32] <\sh> if [ -n $SOCKET ] ; then
[09:32] <\sh>         DAEMON_OPTS="-p $RUNDIR/$NAME.sock $DAEMON_OPTS"
[09:32] <\sh> fi
[09:32] <ScottK> By default it's not set in /etc/default.
[09:32] <ScottK> http://paste.ubuntu-nl.org/33967/ is what I have now.
[09:33] <ScottK> I changed from a Unix socket to TCP so it'd work with Postfix when chrooted.
[09:33] <\sh> is it for your own server?
[09:33] <ScottK> No.  It's for Ubuntu
[09:33] <ScottK> I'm trying to make the Debian package work properly with Postfix for Ubuntu.
[09:33] <\sh> yeah, but for packaging or for running on your server?
[09:33] <\sh> ah
[09:33] <ScottK> Both.
[09:33] <ScottK> I've got it running now on one of my servers.
[09:34] <\sh> but 12345 is the port number which can vary, right?
[09:34] <ScottK> Yeah.
[09:34] <ScottK> I think I used 8891
[09:34] <ScottK> It can be anything since it's loopback.
[09:34] <ScottK> You just have to pick the same one in Postfix and in the milter.
[09:34] <ScottK> I covered that in the README.Debian.
[09:35] <\sh> why don't you set in /etc/default/dkim-filter the SOCKET="inet:12345@localhost" and do if [ -n "$SOCKET" ] ; then DAEMON_OPTS="-p $SOCKET $DAEMON_OPTS" else DAEMON_OPTS="-p $RUNDIR/dkim-filter.sock $DAEMON_OPTS" fi
[09:36] <\sh> which means /etc/default/dkim-filter will be sourced into the init script, and if SOCKET="" it will run the else clause, but when SOCKET is set it will run the then clause
[09:36] <ScottK> I guess if there is an etc/default it would make sense to actually use one of them as the default.
[09:36] <\sh> ScottK, or use debconf
[09:37] <\sh> and set it via user decision ;)
[09:37] <ScottK> Well there's other stuff they have to do about setting up keys and such so it's not like this would be the only thing.
[09:38] <\sh> ScottK, yeah, I read all about domain keys-
[09:38] <\sh> we set it up already in our company..very painfull and resource hungry
[09:38] <ScottK> DKIM is less painful in some respects.
[09:39] <ScottK> It's at least a little less likely to suffer signature breakage in transit and has fewer implementation specific nits.
[09:39] <ScottK> I gave up on DK because it never seemed to work unless the place I was sending to used the same implementation as I did.
[09:39] <ScottK> Personally, I think SPF is more generally useful, but DKIM will have a place and the two are complementary.
[09:40] <coreymon77> hi
[09:40] <\sh> ScottK, spf is also a pain...regarding PR related campaignes, where PR agencies are sending out mails with your header
[09:41] <ScottK> Agreed.
[09:41] <ScottK> SPF sucks, it just sucks less than the alternatives.
[09:41] <\sh> ScottK, but thinking about sending out 800.000 mails in less then 4 hours, without dkim and only one third of those mails in 4 hours with dkim is argl
[09:42] <Riddell> kwwii, nixternal: council dudes, coreymon77 here wants to go for membership but can't make our meeting
[09:42] <nixternal> Riddell: -200 ;p
[09:42] <ScottK> Yeah.
[09:42] <Riddell> would we be ok for him to propose himself over e-mail
[09:42] <nixternal> oh, sure :)
[09:42] <coreymon77> school starts septemebr 4th, so that causes problems
[09:42] <Riddell> and we can ask questions and make a decision at the meeting without him being there
[09:42] <nixternal> that will work
[09:42] <ScottK> \sh: Ouch.
[09:43] <kwwii> Riddell: ok by me
[09:43] <nixternal> Riddell: you know what might be a good idea, a interview sheet like Debian does for NMs and DDs
[09:43] <kwwii> coreymon77: do you have any info on yourself and what you have done for kubuntu
[09:43] <kwwii> like on the wiki already or such?
[09:44] <coreymon77> yes, of course
[09:44] <Riddell> coreymon77: ok, please send an e-mail to kubuntu-devel with your wiki page
[09:44] <coreymon77> email address?
[09:44] <Riddell> your wiki page should include your contributions and anything we need to see that you have made a sustained and significant contribution to kubuntu
[09:45] <Riddell><EMAIL_ADDRESS>[09:45] <\sh> Riddell, btw...congrats to your new duty ;)
[09:45] <Riddell> you need to be a subscriber
[09:45] <Riddell> you should also say why kubuntu is great and why you want to be a member
[09:45] <coreymon77> do i need someone to confirm it for me?
[09:45] <nixternal> oh ya, congrats to Riddell, our new RM! :)
[09:46] <Riddell> coreymon77: also you should get other members and active community types to e-mail their support (or you can e-mail it for them if they don't want to subscribe)
[09:46] <coreymon77> here or in the email?
[09:46] <Riddell> in e-mail
[09:46] <Riddell> we'll e-mail back any questions and make a decision at the next meeting
[09:46] <coreymon77> well, i believe nixternal himself has seem first hand many of my contributions in the #kubuntu irc channel
[09:47] <coreymon77> nixternal: right?
[09:48] <nixternal> who are you again? :p
[09:48] <coreymon77> nixternal: i help with wireless problems alot
[09:48] <nixternal> heh, wireless is a problem nowadays
[09:48] <coreymon77> nixternal: the guy who tells people never to use ndiswrapper unless neccessary
[09:49] <nixternal> hey now, I use ndiswrapper, and it has rocked many a wifi cards for me
[09:49] <coreymon77> i know
[09:49] <coreymon77> it works for many cards
[09:49] <coreymon77> but its still unstable
[09:49] <coreymon77> if there is a more native way of using the card
[09:50] <coreymon77> thats better
[09:50] <coreymon77> ive had people trying to use ndiswrapper for atheros cards
[09:50] <coreymon77> thats completely uneccessary
[09:50] <ScottK> \sh: No suprise to you, I'm sure, but that works.  I'll go with that.
[09:51] <\sh> ScottK, :)
[09:52] <nixternal> Ubuntu Development Team getting ready to start
[09:52] <nixternal> heh, one silly typo has had me going nuts with this package
[09:53] <nixternal> if you don't do configure/foo:: correctly, ie mispell foo, you won't get any errors, and you won't get anything to build either :)
[10:02] <coreymon77> nixternal: what do i have to put in the email?
[10:04] <coreymon77> Riddell: what do i have to put in the email
[10:04] <Riddell> your wiki page and a few sentences about youself, what you do in kubuntu and why you think kubuntu is the bestest
[10:04] <coreymon77> thats all in my wikipage
[10:05] <coreymon77> Riddell: all of that stuff is in my wikipage
[10:06] <Riddell> well put 6 words to each point in the e-mail and you're done
[10:07] <coreymon77> Riddell: do i just send an email to that address
[10:07] <Riddell> yes
[10:07] <Riddell> you must be subscribed as I say
[10:07] <coreymon77> Riddell: what was that thing about subscribing?
[10:09] <coreymon77> Riddell: how do i subscribe
[10:09] <\sh> good night guys
[10:09] <ScottK> Good night \sh.  Thanks again.
[10:09] <ScottK> I just uploaded it.
[10:10] <Riddell> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
[10:11] <manchicken> I'm using kteatime for the first time :)
[10:13] <coreymon77> Riddell: okay, i filled out the form, but had it choose a pasword for me
[10:13] <coreymon77> Riddell: am i now subscribed, or is there a confirmation email?
[10:13] <ScottK> There's a confirmation.
[10:15] <coreymon77> how long does confirmation take
[10:16] <ScottK> Usually it's almost immediate.
[10:19] <coreymon77> well its not for me
[10:22] <coreymon77> im not getting the confirmation email
[10:23] <ScottK> Did you check your spam folder?
[10:23] <coreymon77> yup
[10:23] <coreymon77> i use gmail btw
[10:29] <manchicken> jjesse: Thanks for closing #96399.  That one was making my head hurt the other day.
[10:30] <jjesse> manchicken: your welcome
[10:30] <jjesse> bug #96399
[10:30] <ubotu> Launchpad bug 96399 in adept "Problem adding software through Adept" [Undecided,Invalid]  https://launchpad.net/bugs/96399
[10:30] <jjesse> ah that one
[10:52] <nixternal> Riddell: don't forget to tell them our oo.o is still broken, as well as nspluginviewer
[10:59] <Riddell> nixternal: calc has a fix for openoffice
[11:00] <Riddell> nspluginviewer, well, hmm, still hoping suse will fix it
[11:00] <nixternal> groovy, now we just need the nspluginviewer
[11:00] <nixternal> ahh, waiting for them
[11:00] <Riddell> but it'll still break acroread and opera
[11:00] <nixternal> is there a known fix at all?
[11:00] <Riddell> well, unless glib is changed
[11:00] <Riddell> if there was a known fix, we'd fix it :)
[11:00] <nixternal> lovely
[11:07] <coreymon77> Riddell: i still havent gotten confirmation for the subscription yet
[11:07] <coreymon77> Riddell: why is that?
[11:09] <Riddell> I've no idea
[11:09] <Riddell> try subscribing again, with a password
[11:10] <coreymon77> that worked
[11:25] <coreymon77> Riddell: i take it you dont want personal things about me in the email, just stuff pertaining to linux, right?
[11:32] <nixternal> personal is OK, as it gives us an idea of character I guess
[11:32] <coreymon77> i tend not to give out that stuff online
[11:32] <Riddell> it's not very important
[11:33] <Riddell> people like to put it on their wiki page
[11:33] <coreymon77> you already know that im a student because of the fact that school is the reason that i cant make it to the meeting
[11:33] <Riddell> but it's your contribution to kubuntu we care about
[11:33] <coreymon77> thats in the wiki page
[11:33] <Riddell> "school" in the US means many things
[11:33] <nixternal> coreymon77: we do want social security number, birth date, and full name though :p
[11:34] <nixternal> Riddell: what all does it mean? besides the lingo of "you have just been schooled" :)
[11:34] <Riddell> nixternal: well americans use it to mean university and college as well as school
[11:34] <nixternal> ahh, nm, I think I get it...what kind of school (ie. high school, college, trade, etc.)
[11:34] <nixternal> ya
[11:37] <coreymon77> i will tell you that i am a highschool student
[11:37] <coreymon77> from canada
[11:37] <coreymon77> thats all can say
[11:39] <coreymon77> do you guys want me to copy and paste the approval emails into my application email
[11:40] <coreymon77> or do you want me to forward them seperately
[11:41] <coreymon77> Riddell: hello?
[11:41] <jjesse> coreymon77: i think he might be in bed
[11:42] <coreymon77> nixternal: could you answer the question?
[11:42] <Riddell> coreymon77: just copy and paste is fine
[11:42] <coreymon77> okh
[11:42] <coreymon77> thanks
[11:42] <coreymon77> nixternal: nvm
[12:04] <nixternal> I am getting a permission denied when trying to create the directory /usr/lib/qt4/plugins/accessiblebridge with this package...it is starting to annoy me
[12:05] <coreymon77> nixternal: sudo is getting access denied?
[12:05] <coreymon77> nixternal: maybe something is being used
[12:05] <Riddell> nixternal: you presumably want to make it local to the package rather than the filesystem
[12:05] <nixternal> no, this is in the building of a package...no sudo used
[12:06] <nixternal> Riddell: I have tried debian/dirs and mkdir -p $(CURDIR)/debian/blahblah/blah
[12:08] <nixternal> I think I have found the problem..as a matter of fact, I know I did
[12:08] <nixternal> the Makefile that is created with qmake-qt4 has a DESTDIR = /usr/lib/qt4/plugins/accessiblebridge


[15:00] <coolo> JFYI, http://lists.opensuse.org/opensuse-factory/2010-02/msg00092.html
[15:53] <Keybuk> sweet


[00:03] <jfenn2199> Good evening all
[00:04] <cyberanger> evening jfenn2199
[00:04] <cyberanger> how's the weather
[00:04] <jfenn2199> White Death 2011 begins!
[00:05] <jfenn2199> Unfortunately the odds of a snow thunder storm have significantly dropped
[00:08] <cyberanger> same here I think
[00:08] <cyberanger> idk, it's hard to tell
[00:08] <cyberanger> netritious: how big is his hdd gonna be?
[00:08] <cyberanger> and can you throw in a thumbdrive
[00:11] <netritious> cyberanger: not big enough (40G)
[00:12] <netritious> I mean, I could squeeze it in there if I had to, but would rather give him that space to do other things
[00:12] <cyberanger> agreed, but for what I was thinking, it works
[00:12]  * cyberanger pokes excid3|mbp into telling netritious about keryx
[00:12] <excid3|mbp> herro
[00:12] <netritious> I know about keryx ;)
[00:12] <cyberanger> and I have a script on the same lines
[00:13] <excid3|mbp> :)
[00:13] <cyberanger> and yet your gonna burn the hell outta some dvd's, well ok
[00:13] <cyberanger> :-D
[00:13] <netritious> brb in a sec.. jfenn2199 going to look at this White Death hehe
[00:14] <cyberanger> excid3|mbp: btw, that script has really worked, still adapting it to fakepository usage
[00:14] <netritious> cyberanger: yeah, I mean the dude lives in a rural part of MS that I don't get down to very often
[00:14] <excid3|mbp> cyberanger: awesome!
[00:14] <netritious> dvd's are cheap too
[00:17] <cyberanger> netritious: so a usb drive to the local library is pointless
[00:17] <cyberanger> or a boost mobile phone and 15 a month on it
[00:17] <cyberanger> it works
[00:17] <netritious> he uses landline for phone
[00:18] <netritious> the only service provider out his way is dish
[00:18] <netritious> well, directv
[00:18] <cyberanger> the phone was for internet, but in that case, a linux modem, and 5 bucks a month
[00:20] <netritious> he's on a fixed income in the woods man, he's not interested in internet
[00:21] <cyberanger> can't blame him
[00:21] <cyberanger> the word addict comes to mind (for me)
[00:22] <netritious> addicted to the internet? you? noooo, don't believe it :D
[00:23] <cyberanger> ok, so I'mm not an addict (denial is the first step ;-)) they have meetings
[00:24] <netritious> this guy is a family friend that just needs a computer and some way to maintain it himself since I don't come around but every few years
[00:25] <cyberanger> and thus why I did suggest keryx or similar though
[00:25] <netritious> another friend, also in the "no internet boat" he lives about 400m/1300ft from my house, so thinking that I might be able to set up a directional antenna to provide some wifi access
[00:25] <cyberanger> head to the public library, keep it up to date
[00:25] <cyberanger> if you got los, that's no sweat
[00:26] <cyberanger> I've done 3 and 5 mile links
[00:26] <netritious> los?
[00:26] <cyberanger> like to try 30 miles next
[00:26] <cyberanger> line of sight
[00:26] <netritious> yeah, from the chimney's anyway
[00:26] <cyberanger> nothing in the way to degrade the signal
[00:26] <cyberanger> tree, so on
[00:26] <netritious> might be a tree or two
[00:26] <netritious> maybe...not 100% on that yet
[00:29] <netritious> I wonder if I would do better with an omni directional antenna instead
[00:32] <cyberanger> well, if you can get him and you on a directional, say with a ubiquity bullet, and then each have a local network with omni's that be best
[00:32] <cyberanger> easy to firewall off
[00:47] <chibihogoshino> netritious: you could get two old dishnetwork dishes and stick a antenna on the front of them
[00:48] <netritious> I'm thinking I might use directv dishes since we both have them and neither of us use them for anyhting and don't intend to
[00:48] <netritious> *anything
[00:48] <netritious> we both used to have dtv but don't anymore and haven't in a long time
[00:49] <netritious> change out the LNB for something wifi capable
[00:49] <netritious> I've seen a video or two on converting a dtv dish
[00:49] <chibihogoshino> that would be cool
[00:56] <chibihogoshino> iv seen people just stick a usb wifi adapter on the dish
[01:03] <netritious> chibihogoshino: yep
[01:03] <netritious> pringle can on a dish :)
[01:04] <chibihogoshino> heh yeah
[01:06] <cyberanger> it works
[01:06] <cyberanger> I've done it
[01:13] <chibihogoshino> how far has that gone cyberanger ?
[01:14] <cyberanger> at least 5mi
[01:14] <cyberanger> haven't seen further yet
[01:14] <chibihogoshino> with a usb ?
[01:15] <cyberanger> the design should be fine tuned to 30 miles at least
[01:15] <cyberanger> no, N Connector
[01:15] <chibihogoshino> oh
[01:53] <chibihogoshino> cyberanger: did you use two routers or wifi cards for that ?
[01:57] <cyberanger> technically routers
[01:57] <cyberanger> at that point
[01:57] <cyberanger> but it didn't matter
[01:59] <chibihogoshino> what was the power out put ?
[02:02] <cyberanger> well, idk the gain on the antenna, so I can't fully factor that, but I cut down the power the router had, from 42mW to I think 15mW
[02:02] <cyberanger> but that's not peak emitting power
[02:02] <cyberanger> which legally must be under 1W
[02:03] <cyberanger> (or I can be a ham operator and cook chickens at 1500W PEP) but at that distance, directional antennas, that still might have been more than necessary
[02:25] <chibihogoshino> you could light a few neon lights along the way
[12:49] <wrst> well cyberanger we do have snow after all shockingly enough
[12:50] <wrst> and cyberanger you might want to idnetify yourself
[14:11] <Xpistos> How bad is the snow where you all are
[14:11] <Xpistos> oh yeah
[14:11] <Xpistos> hi
[14:11] <Xpistos> wrst
[14:12] <wrst> hey Xpistos not bad 2-4" here
[14:44] <Xpistos> same as here
[14:55] <wrst> sounds like down south got a lot of snow
[16:03] <netritious> yeah about 3-4"
[16:08] <wrst> cool netritious so you surviving the blizzard of 2011 :)
[16:08] <netritious> yeah...turned the heat up lol
[16:09] <wrst> ha ha i'm about to go find some early lunch in celebration i think
[16:18] <Xpistos> I can't believe there are people with huge trucks
[16:18] <Xpistos> that couldn't get to work
[16:19] <Xpistos> that live closer than me
[16:19] <Xpistos> and I drive a toyota corolla
[16:19] <Xpistos> Yeah, I didn't feel bad when the president of the company was in my bosses office and I said "Well, i made it fine"
[16:24] <wrst> i made it in bright and early too Xpistos
[16:48] <wrst> greetings pace_t_zulu
[16:49] <pace_t_zulu> morningwr
[16:49] <pace_t_zulu> morning wrst
[16:50] <wrst> pace_t_zulu: how's it going?
[16:50] <pace_t_zulu> wrst: you can seen i am accustomed to autocompleting your handle after the 'wr'
[16:50] <pace_t_zulu> wrst: well, you?
[16:50] <pace_t_zulu> wrst: you make it into work today?
[16:50] <wrst> ha ha i do it after the pa pace_t_zulu :)
[16:50] <wrst> yep not that much up here pace_t_zulu compared to what we have already had probably 3-4"
[16:51] <pace_t_zulu> wrst: its nice powder in nashville right now... tomorrow could be bad if it becomes ice
[16:52] <wrst> yeah i suspect especially so if many try to get out in it
[19:44] <wrst> cyberanger: welcome back again :)
[19:46] <cyberanger> heh, barely
[19:47] <cyberanger> celluar and battery power only
[19:53] <wrst> well good to see you what of you is here :)
[19:56] <cyberanger> last night I rushed shutting down, killed the client, nearly shut down my server by mistake, in haste
[19:57] <cyberanger> and in the morning, power loss
[20:00] <wrst> power loss stinks :\
[20:23] <cyberanger> yep
[20:24] <cyberanger> not unexpected though
[20:25] <wrst> still... as i know they really can mess you up :)
[20:29] <cyberanger> back up
[20:30] <cyberanger> wrst: naw, not really
[20:30] <cyberanger> I mean it can, but precautions already factored both in
[20:31] <cyberanger> unfortunately not implemented as what happened, and ideally maintained or setup
[20:32] <cyberanger> but unless celluar went down (too localized I expect, car hit the right pole is what I figure) I was good
[20:32] <wrst> cyberanger: i am looking to change my setup some so when the power goes off my server will start back up the usb hard drives and it do not get along at all
[20:32] <wrst> but the car not so good
[20:34] <cyberanger> conserving power by sticking to the G2 smartphone was smart, I'm not where I'd like to be on battery capacity, doable but the downtime was more than I factored for
[20:35] <cyberanger> and I wasn't set for what I did factor
[20:35] <cyberanger> yeah, you might want to look at your bios boot order
[20:35] <cyberanger> and maybe you can shut off usb boot entirely
[20:35] <cyberanger> that's not ideal
[20:40] <cyberanger> wrst: have you looked at the bios to see if boot settings plays a role
[20:43] <wrst> yeah cyberanger no luck there just going esata on it
[20:56] <cyberanger> idk if that'd change it, if it's still booting to external hdd
[21:00] <cyberanger> guess it's worth a shot
[21:43] <netritious> ubuntu-tennessee.org's IP has changed. may take a few hours to resolve.
[21:43] <netritious> but it's there, and now should have less trouble using SSL
[21:46] <netritious> I got tired of trying to figure out how to force WP to redirect to an alternate port (:500) trying to be stingy with my statics, but after six months of trying on and off again I give up :P
[21:55] <cyberanger> you sure it was 6 months
[21:55] <cyberanger> we've had the domain for over 11 months now
[21:55] <cyberanger> gotta renew it next month
[21:56] <cyberanger> glad it's working reguardless
[21:57] <netritious> for some reason I was under the impression that you purchased the domain for two years?
[21:58] <netritious> I know the SSL cert is for two years
[21:58] <netritious> and yes, I'm pretty sure it's around or at six months
[21:58] <netritious> since initially the site was hosted on a dedicated VM and was moved to the shared hosting server
[22:00] <cyberanger> nope, I think I did say that it'd be covered that long at least
[22:00] <netritious> well, initially it was hosted on a free service somewhere and then moved to a dedicated vm Nov 2009
[22:00] <cyberanger> due to ssl
[22:01] <cyberanger> or something like that
[22:02] <netritious> yeah the SSL cert expires in Mar 2012
[22:02] <netritious> Mar 1 20:53:39 2012 GMT to be exact
[22:03] <cyberanger> so it would have been an issue anyhow
[22:04] <cyberanger> if I said two years
[22:05] <cyberanger> if I had it set for two years and split, then you'd be scrambling for a month
[22:05] <cyberanger> good thing we got that framework working out
[22:05] <cyberanger> however it seems it's been unnecessary
[22:06] <cyberanger> but everything is unnecessary until proven otherwise, and that was our track record at that time
[22:06] <netritious> not sure I understand what you mean
[22:12] <netritious> anyways I'm out...l8rs


[16:44] <BugeyeD> anyone aware of a valid repos for jaunty?
[16:49] <BugeyeD> ahh, never mind.
[16:49] <BugeyeD> in case anyone wondered ... and this may get me kicked. we'll see.
[16:49] <BugeyeD> ## EOL upgrade sources.list
[16:49] <BugeyeD> # Required
[16:49] <BugeyeD> deb http://old-releases.ubuntu.com/ubuntu/ CODENAME main restricted universe multiverse
[16:49] <BugeyeD> deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-updates main restricted universe multiverse
[16:49] <BugeyeD> deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-security main restricted universe multiverse
[16:49] <BugeyeD> # Optional
[16:50] <BugeyeD> #deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-backports main restricted universe multiverse


[00:22] <andrew> eG8b3zao
[02:40] <EvilPhoenix> lool
[06:00] <ChinnoDog> 1am
[06:15] <andrew> yes
[10:11] <JonathanD> 6:11am
[13:17] <rmg51> 9:17am
[16:29] <SamuraiAlba> Good bacon to all!
[16:48] <andrew> Sun Mar 13 12:48:49 EDT 2011


[14:23] <pfsmorigo> ingvar, hello, do you think it's possible to have a backport of the complete fix for 6.2.1 (focal version) or just mitigate the problem? (tks mdeslaur)
[14:28] <luis220413> pfsmorigo: I filed bug 1986627 for the incomplete fix.
[14:30] <mdeslaur> if it's causing an issue for users, and we don't know what the fix is, we need to back out the patch and release a new package
[14:31] <luis220413> mdeslaur: The fix is known. See the last comment in bug 1971504
[14:32] <mdeslaur> I don't see a fix in that comment
[14:33] <luis220413> mdeslaur: I mean the second-to-last comment: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1971504/comments/33
[14:33] <luis220413> I will return in 10 minutes but I will remain online.
[14:39] <luis220413> I am back.
[15:10] <teward> luis220413: i am not the security team but it sounds like you or others are proposing a full version bump.  unless the code changes between .1 and .2 are trivial and well documented what specifically was changed and why i'm not sure how feasible that proposed fix from the fedora maintainer would be
[15:10] <luis220413> luis220413: No. The comment says: "Which means that most of the code changes between varnish-6.2.2 and 6.2.3 (tests and doc and stuff may be dropped) should be included in the patch set that fixes CVE-2020-11653."
[15:11] <luis220413> *teward: ^
[15:12] <teward> we have .1 with patches.  including changes between .2 and .3 would be a version bump from .1 to .3.  so the changes between .1 and .2 *are* relevant as i stated
[15:12] <teward> whether we drop tests and documentation or not its still a version bump if tberes not cherrypickable changes for this
[15:13] <luis220413> teward: The changes between 6.2.1 and 6.2.2 are trivial and included in version 6.2.1-2ubuntu0.1: https://github.com/varnishcache/varnish-cache/compare/varnish-6.2.1...varnish-6.2.2
[15:13] <teward> it is, ultimately, a security team decision on whether they want to prod it with a stick and such and do these changes, but the consideration points are still there
[15:14] <luis220413> teward: The remaining changes can be cherry-picked: https://github.com/varnishcache/varnish-cache/compare/varnish-6.2.2...varnish-6.2.3
[15:26] <luis220413> ebarretto: The Xen SRU in bug 1956166 was merged! I would like you to provide a progress report on the review of my debdiff in bug 1970507.
[15:27] <luis220413> s/merged/released to focal-updates/
[16:17] <pfsmorigo> luis220413, are you going to work in a debdiff for the missing patches for CVE-2020-11653? I see 19 commits but some of them are already included.
[16:39] <luis220413> pfsmorigo: Yes. There are 14 commits to be included in that debdiff.
[16:40] <luis220413> This CVE only affects Ubuntu 20.04.
[16:59] <luis220413> pfsmorigo: I am working on it now.
[17:21] <luis220413> pfsmorigo: I will return in 5 minutes but I will remain online. There are only 4 patches remaining.
[17:31] <luis220413> pfsmorigo: The debdiff is ready.
[17:33] <luis220413> The patched package has just been uploaded to the usual PPA (https://launchpad.net/~luis220413/+archive/ubuntu/security-updates).
[17:37] <luis220413> pfsmorigo: I will return in 45 minutes but remain online.
[18:03] <luis220413> I am back.


[04:05] <mup> Bug #1647527 opened: error: builtins.KeyError: 'subarches' while attempting to sync images <sts> <MAAS:New> <https://launchpad.net/bugs/1647527>
[04:11] <mup> Bug #1647527 changed: error: builtins.KeyError: 'subarches' while attempting to sync images <sts> <MAAS:New> <https://launchpad.net/bugs/1647527>
[04:17] <mup> Bug #1647527 opened: error: builtins.KeyError: 'subarches' while attempting to sync images <sts> <MAAS:New> <https://launchpad.net/bugs/1647527>
[07:41] <compahis> Hi, anyone knows which power to use for HP proliant dl180 gen 6?
[07:42] <compahis> power type
[09:09] <mup> Bug #1645872 changed: Commissioning fails on NUCS previously loaded with coreos <MAAS:Incomplete> <https://launchpad.net/bugs/1645872>
[09:18] <mup> Bug #1645872 opened: Commissioning fails on NUCS previously loaded with coreos <MAAS:Incomplete> <https://launchpad.net/bugs/1645872>
[09:21] <mup> Bug #1645872 changed: Commissioning fails on NUCS previously loaded with coreos <MAAS:Incomplete> <https://launchpad.net/bugs/1645872>
[13:10] <zeestrat> Hey, is there a way to change the default DNS domain from .maas to something else?
[13:11] <roaksoax> lamont: ^^
[13:12] <lamont> zeestrat: from the command line: maas SESSION domain update 0 name=foo.com
[13:12] <mup> Bug #1647703 opened: [UI 2.1] renaming domain does not update node summary page <MAAS:New> <MAAS 2.1:New> <MAAS trunk:New> <https://launchpad.net/bugs/1647703>
[13:14] <zeestrat> Ah, OK. Anything to watch out for when changes the default domain? Figured there might a reason why it's not editable from the GUI.
[13:15] <lamont> zeestrat: other than bug 1647703, I'm not awareof anything
[13:15] <lamont> it was added to the API, but just didn't make the UI cutline
[13:16] <zeestrat> lamont: Gotcha, thanks for the quick response! I can add a bug for adding it to the UI in the future if you want.
[13:20] <lamont> wouldn't hurt
[13:42] <mup> Bug #1647720 opened: Unable to rename domain in web ui <MAAS:New> <https://launchpad.net/bugs/1647720>
[17:22] <cmart> Hi folks. Is there a doc on configuring SSL support for the Web UI of the latest stable MAAS? I don't see this at all in the setup guide (http://docs.ubuntu.com/maas/2.1/en/installconfig-gui)
[17:23] <cmart> I do see this documented for MaaS 1.9 (https://maas.ubuntu.com/docs1.9/configure.html), but don't see it for 2.0+.
[17:29] <mup> Bug #1441684 changed: Add test for SO_REUSEPORT and add warning log if kernel does not support it <tech-debt> <MAAS:Won't Fix> <https://launchpad.net/bugs/1441684>
[18:12] <rjbrenn> hey all - anyone have time to walk an utter noob through a /probably/ basic maas issue ?
[18:27] <cmart> <--- also an utter noob, rjbrenn, whatcha got?
[18:28] <rjbrenn> So I just installed 16.04 following the '
[18:28] <rjbrenn> 'dumb and easy' instructions of apt-get install maas
[18:28] <rjbrenn> and I've got it to the point where it will discover other nodes
[18:28] <rjbrenn> and commission them, and I can start the install
[18:29] <rjbrenn> but these are all UEFI servers
[18:29] <rjbrenn> and at the end of the install, it looks like curtin does not create a uefi boot entry
[18:30] <rjbrenn> so when the newly installed node starts up it ends up PXE booting from the rack controller again, and sits there at a grub prompt with a single 'Local' entry
[18:31] <rjbrenn> I can manually force the node to boot from the installed EFI code if I hit F12 fast enough and make a new boot entry
[18:31] <rjbrenn> installing Ubuntu from a disk normally also creates a boot entry
[18:32] <rjbrenn> so - the question I have is what is maas/curtin supposed to do here ?
[18:32] <cmart> I'm unsure -- but are you using the daily or the stable cloud images?
[18:33] <cmart> `maas admin boot-sources read` should tell you, in the URL field
[18:33] <rjbrenn> stable: 2.1.1+bzr5544-0ubuntu1~16.04.1
[18:38] <pmatulis> rjbrenn, can you kindly report your situation as a bug? https://bugs.launchpad.net/maas/+filebug
[18:38] <rjbrenn> sure
[18:42] <pmatulis> cmart, and can you file one here? https://github.com/CanonicalLtd/maas-docs/issues/new
[18:42] <cmart> certainly @pmautils
[18:50] <pmatulis> thanks to both of you
[19:03] <rjbrenn> you're welcome - but just for clarification - is a MAAS managed group of nodes supposed to always PXE boot from the rack controllers, or are they supposed to have local uefi boot entries on each node ?
[19:38] <mup> Bug #1647827 opened: curtin Xenial install does not uefi boot  <MAAS:New> <https://launchpad.net/bugs/1647827>
[20:22] <pmatulis> rjbrenn, i'm not a developer but i would think the node should not have any special requirements
[20:29] <brendand> rjbrenn, i didn't see your message but there are minimal requirements for a maas node
[20:43] <pmatulis> rjbrenn, brendand: yeah, i still have to review the storage docs so i missed this
[20:44] <pmatulis> http://docs.ubuntu.com/maas/2.1/en/installconfig-partitions
[20:44] <pmatulis> "An EFI partition is required to be on the boot disk for UEFI."
[21:36] <cmart> pmatulis, I'm not sure if it's just a documentation bug. I think MAAS should have a secure default behavior of web interface configured with HTTPS, at least with a self-signed certificate, and invite the user to provide their own certificate
[21:37] <cmart> but I will start by filing my bug in maas-docs :)
[21:51] <pmatulis> cmart, yeah. and thanks
[23:00] <mup> Bug #1647863 opened: DHCP snippet at node level is not added to dhcpd.conf <MAAS:New> <https://launchpad.net/bugs/1647863>


[04:59] -queuebot:#edubuntu- Unapproved: lxcfs (xenial-proposed/main) [2.0.4-0ubuntu1~ubuntu16.04.1 => 2.0.5-0ubuntu1~ubuntu16.04.1] (edubuntu, ubuntu-server)
[05:02] -queuebot:#edubuntu- Unapproved: lxcfs (yakkety-proposed/main) [2.0.4-0ubuntu1 => 2.0.5-0ubuntu1~ubuntu16.10.1] (edubuntu, ubuntu-server)
[10:41] <highvoltage> so long, and thanks for all the fish.


[21:02] <mohbana> what is 'OpenJDK Java runtime (headless)'?
[21:03] <mohbana> hello?
[21:16] <munckfish> mohbana: I believe it'll be the JDK less stuff which is only used for the GUI
[21:16] <munckfish> but you're better to look at the description in the synaptic for exact definition
[21:17] <munckfish> I guess it's intended for servers where there is no UI, and therefore no reason to force install of X related packages
[21:20] <jamesstansell> the -headless package? yes, that's exactly it - no X11 needed, but still able to process image classes, etc.


[06:09] <lhvf> Hello Ubuntu Development App Community! Is this right place to ask to updates of a given Ubuntu PPA?
[06:13] <lhvf> Is there someone Community involved, or that could contact someone that Develops to Ubuntu Distribution at the moment?
[06:22] <lhvf> Is there someone that Manages some Ubuntu Apps Development at the current moment, such as PPAs?
[06:35] <lhvf> Maybe would be better to try again another hour and day some Developer contact?
[06:42] <lhvf> Some people online right now?


[00:23] <nellery> What email interface command can be used to add a bug watch?
[00:34] <Hobbsee> brilliant.  Found a way to make launchpad load as quick, or quicker!
[00:34] <jml> oh?
[00:34]  * wgrant would like it accessible over IPv6, as his IPv6 routing is much better.
[00:38] <Ursinha> Hobbsee, how?
[00:38] <Hobbsee> Ursinha: running a socks proxy to the US, and loading pages thru that.
[00:38] <Ursinha> hmm
[00:39] <Ursinha> interesting
[00:39] <Hobbsee> a whole lot of pages are loading in 5 seconds.
[00:39] <Hobbsee> the minimum i normally get to au is 7.
[00:39] <jml> Hobbsee: that's surprising
[00:39] <jml> Hobbsee: I guess you look mostly at bugs pages?
[00:39] <Hobbsee> jml: yeah, although i was browsing around at random with the proxy
[00:40] <Hobbsee> https://edge.launchpad.net/ubuntu/intrepid/+builds?build_text=&build_state=pending loads in 4.381 seconds.
[00:40] <jml> Hobbsee: I find the code pages tend to load faster (although still too slowly)
[00:41] <james_w> hey, all, I'm trying to use the api, and a bug has an "unsubscribe" operation, but it doesn't take a parameter, so I don't see how to un-subscribe a team that I am on.
[00:41] <Hobbsee> hmmm
[00:42] <james_w> am I missing something? Would I report a bug against launchpad to get a parameter added so that I can do this?
[00:46]  * Hobbsee wonders if someone's written a greasemonkey script to not load the google maps.
[00:48] <elmo> adblock plus works well
[00:54] <Hobbsee> elmo: that's true, but i'd prefer to only block it on LP.
[00:54] <elmo> you can
[00:54] <elmo> block on http://maps.google.com/maps?file=api&v=2.121&key=ABQIAAAAd8GIgO6pcskVE20WMo0tMRRkABWjM-HFSmcaZJwi4T_L_gqd8hQZWt328aH2TFAi3x2jCPoCqCaLIQ
[00:55] <elmo> (that's LP's key, obviously - so other maps will work fine)
[00:55] <Hobbsee> oh :)
[00:58] <Hobbsee> elmo: thanks, I got that to work :)
[01:10] <paolettopn> Vado via alle Fri Oct 10 02:10:01... ci si rivede alle prossime!
[02:18] <Peng_> jml: Oh. Never mind about my ping earlier.
[02:19] <jml> Peng_: tbh, I'd forgotten :)
[02:19] <jml> Peng_: was it about branch mirroring?
[02:19] <Peng_> jml: Heheh, as always. :)
[02:20] <jml> Peng_: yeah, we had some teething problems with our new server, which have since been fixed.
[02:21] <Peng_> jml: So it should work now?
[02:22] <jml> Peng_: 'should' is such a slippery word.
[02:22] <jml> Peng_: I would be surprised if it didn't work :)
[02:25] <Peng_> I'm sure you were surprised when it didn't work before. :P
[02:25] <Peng_> Anyway, it works. Yays!
[02:26] <Peng_> bug 280059 -> fixed?
[02:26] <jml> mwhudson: ^^
[02:28] <Peng_> And I've finally converted a bunch of branches to packs, so they might actually be mirrored this time!
[02:28] <jml> heh heh
[02:32] <mwhudson> ah, yes, it probably is fixed
[04:35] <Peng_> LP even managed to mirror one of my knit branches that IIRC should've caused a revision not found error.
[04:37] <Peng_> One of my branches failed to mirror due to a KeyboardInterrupt?
[04:43] <mwhudson> Peng_: that means the puller process didn't see any activity for 15 minutes or something
[04:44] <Peng_> I hit the try again button and it worked.
[04:44] <mwhudson> i guess we may have been mirroring more than one branch from your server at once or something
[04:44] <Peng_> Yeah, you were.
[04:45] <mwhudson> (we should probably stop doing that)
[04:45] <Peng_> I don't mind. :)
[04:45] <mwhudson> jam does :)
[04:45] <Peng_> My web server dropped one readv, eventually giving up after 360 seconds. Maybe that helped cause it to time out.
[09:12] <ziroday> Hi, I am having issues logging in. I go to the login page, type in username and password. Click login, get directed back to original page but _have
[09:12] <ziroday> not logged in
[09:17] <wgrant> ziroday: Are you being redirected to edge, perhaps?
[09:17] <wgrant> Or do you have cookies disabled?
[09:23] <ziroday> wgrant: sorry, not being redirected to edge, and yes cookies are enabled
[09:24] <ziroday> wgrant: cleared cache and cookies, still there
[11:52] <persia> Is there a safe way to interrupt a bzr push to LP?  It's been over two hours for a 1k update (although pushing a new branch of 433 revisions).  I do have an open connection to crowberry.
[11:57] <wgrant> persia: A new branch means pushing the whole lot unless it's stacked.
[11:58] <persia> "stacked"?
[11:59] <wgrant> A nice new bzr feature which makes new branches much less tedious to push.
[11:59] <wgrant> Branches can refer to another branch in which revisions can be found.
[11:59] <wgrant> So you only have to push the new revisions, even for a new branch.
[12:09] <persia> Hrm.  Sounds nifty.  I think I'll want to use that next time.
[13:07] <persia> Now 4 hours still in Transferring 0/4.  If I Ctrl-C, and try to repush, is LP going to think I'm not pushing any revisions?
[13:17] <wgrant> persia: I doubt it, but you'll probably have to tell bzr to overwrite the target because it's a new branch.
[13:23] <persia> So I probably want to Ctrl-C, and try again with --stacked-on and --overwrite?
[13:25] <wgrant> persia: Likely. And you then need a three-line Python hack to get LP to like the stacking - I believe this will be fixed in 2.1.10.
[13:26] <wgrant> But it makes pushes so much faster.
[13:26] <wgrant> It is actually usable.
[13:27] <persia> I can probably skip the stacking if I upgrade the repo.  I'm not entirely comfortable hacking bzr at my current comfort level with using it at all.
[13:27] <persia> Hrm.  1/4.  Still, I don't want to wait another 6 hours.
[13:28] <wgrant> Is it a knit branch?
[13:28] <persia> Yes.
[13:29] <wgrant> That would do it.
[13:30] <persia> It's supposed to be that slow?
[13:30] <wgrant> I hope not.
[13:30] <wgrant> But I'm fairly sure that LP is slower with knit branches than it used to be.
[13:31] <wgrant> Packs are much, much faster.
[13:31] <persia> Hrm.  I wonder what happens if a format becomes not only deprecated, but no longer supported, and the server upgrades.  Will branches become non-useful?
[13:33] <wgrant> bzr hasn't dropped support for any formats yet, has it?
[13:34] <james_w> at least nothing that anyone could conceivably be using. I know the format support extends back to at least version 0.8 formats.
[13:36] <wgrant> I remember weaves... was anything before that?
[13:37] <persia> james_w, I suspect that as long as bzr supports all the formats ever used by LP, LP should be OK.  Otherwise, LP probably needs to grow some means of bringing the old code forward.
[13:38] <persia> Hrm.  Despite upgrading, now bzr is downgrading on push because of the previous push (even with --overwrite).  Does LP have some button to let me change the format stored in LP, or should I just pick a new name, and delete the old branch?
[13:38] <wgrant> LP does really need a server-side upgrade button.
[13:38] <wgrant> persia: No need to pick a new name - if it's a new branch, just delete it and repush.
[13:39] <persia> Ah.  "Delete" was the step I missed.  Thanks.
[13:40] <wgrant> There's probably a better way to do it in bzr, but the button in LP is the one I know of.
[13:44] <persia> Well, it definitely worked for me : it's at 3/5 already.  Thanks.
[13:45] <wgrant> Excellenmt.
[13:45] <wgrant> -m
[13:45] <wgrant> +sleep
[13:51]  * wgrant doesn't think he's seen gary_poster around these parts before.
[13:51]  * gary_poster thinks wgrant is right :-)
[13:52] <laga_> so, the community help contact. do you guys just draw straws or is there a schedule? ;)
[13:52] <gary_poster> heh
[13:52] <gary_poster> there's a schedule, which is swapped around
[13:52] <gary_poster> as needed
[13:52] <Hobbsee> gary_poster: what do you work on normally, then?
[13:52] <gary_poster> Launchpad foundations
[13:53] <Hobbsee> ahhh
[13:53] <gary_poster> so...the underlying goop :-)
[13:53] <gary_poster> (in a good way :-) )
[13:53] <Hobbsee> mmm...goop....
[13:53] <gary_poster> :-)
[13:53] <Hobbsee> we should hit you up for all the foundation bugs, then.
[13:53] <gary_poster> oh joy ;-)
[13:53] <wgrant> Foundations including Registry, or are the teams actually split now?
[13:53] <Hobbsee> you feel like fixing mail headers?  :)
[13:54] <gary_poster> wgrant: split up now
[13:54] <wgrant> Aha.
[13:54] <wgrant> ~launchpad is positively massive now.
[13:54] <gary_poster> Hobbsee: not particularly.  ;-) what's the bug, though?  I'm curious.
[13:54] <gary_poster> wgrant: yup, pretty big
[13:55] <Hobbsee> gary_poster: https://lists.ubuntu.com/archives/launchpad-users/2008-September/004228.html
[13:56] <Hobbsee> no X-Message-rationale, etc.
[13:56] <wgrant> And a fake from address.
[13:56] <gary_poster> Hobbsee: gotcha.  did you file a bug?
[13:57] <Hobbsee> gary_poster: no, but i'm not sure if anyone else did.
[13:58] <gary_poster> Hobbsee: heh, ok, well, I can at least dig around and check, and add it if I don't find it.  I'll ping you and put the bug # here in case you want to subscribe.
[13:59] <Hobbsee> gary_poster: cool, OK.
[13:59] <Hobbsee> gary_poster: does that imply fixing it too, or just reporting it?
[13:59] <gary_poster> Hobbsee: given other tasks for today, just reporting it I'm afraid
[14:00] <gary_poster> ...unless the solution falls down to me like an apple on my head...
[14:00] <Hobbsee> gary_poster: how hard is it to get headers added to mails?  Everything else manages to have headers....
[14:03] <gary_poster> Hobbsee: If one knows the code that is generating the email, and the reason for the missing header, presumably rather easy.  I know neither, and as I said, I have other tasks today.  I'll add the bug, and see if someone else has an immediate pointer.
[14:03] <gary_poster> Again, given the schedule, even if I fixed it today, it's doubtful that the fix would be in the next release.
[14:05] <Hobbsee> fair enough.
[14:05] <Hobbsee> no, but i'd hope it gets done in the next 6, tbh.
[14:05] <Hobbsee> or even 12, as most people probably don't care much about it.
[14:07] <gary_poster> understood
[15:02] <zachtib> is the PPA service running slow today? I uploaded packages ~15 minutes ago and haven't gotten an email from it yet
[15:02] <zachtib> usually, I get an email within a couple minutes
[15:02] <gary_poster> Hobbsee: appears to be new bug.  Assigned to registry team.  See bug 281293.
[15:02] <cprov> zachtib: let me check.
[15:03] <zachtib> thanks
[15:03] <cprov> zachtib: source name ?
[15:03] <zachtib> deluge-torrent_1.0.1
[15:05] <cprov> zachtib: you've signed the upload with a unknown GPG key
[15:05] <zachtib> really? that's odd
[15:05] <zachtib> it should be the same key i've been using in that repo since i started it
[15:05] <cprov> zachtib: key id ?
[15:06] <zachtib> i think it's this: 1024D/C1CB9387
[15:09] <cprov> zachtib: yes, it's signed with C1CB9387
[15:11] <zachtib> debuild did spit out some warnings when i signed it...
[15:11] <zachtib> wonder why
[15:12] <zachtib> hmm... it didn't do it this second time
[15:13] <cprov> zachtib: you have email
[15:13] <cprov> zachtib: I've reprocessed your uploads and they were accepted.
[15:13] <zachtib> ok, cool
[15:13] <zachtib> both the zachtib and deluge-team ppa?
[15:13] <cprov> zachtib: it looks like a keyserver temporary failure.
[15:14] <zachtib> ah
[15:14] <zachtib> awesome, they're building now
[15:14] <zachtib> thanks
[15:15] <cprov> zachtib: apparently I've just re-processed the ones to the team PPA.
[15:16] <cprov> zachtib: there was only one upload to your PPA (hardy) and it was accepted.
[15:16] <zachtib> right, ok
[15:16] <zachtib> thanks again
[15:19] <cprov> zachtib: np, you did well warning about the acceptance email delay.
[15:20] <cprov> zachtib: it should never take more than 10 minutes.  If it does, something is wrong.
[15:44] <synic> how do I get rid of this message?
[15:44] <synic> Server is too old for streaming pull, reconnecting.  (Upgrade the server to Bazaar 1.2 to avoid this)
[15:45] <persia> synic, That's an unfortunate error message, that should read "Server is too new for streaming pull, reconnecting.  (Upgrade the client to avoid this).
[15:46] <persia> For the most part, just ignore it, or upgrade bzr.
[15:46] <synic> ah
[15:46] <synic> oh nice, there's a ppa.
[16:48] <kirkland> is it possible for me to blacklist launchpad users that i no longer want to hear from?
[16:48] <kirkland> i'd like their comments on bugs, when sent to me, to be simply dropped.  and when in the web interface, hidden or collapsed
[16:50] <kirkland> also, what about a way to politely refer impolite users to the Code of Conduct?  perhaps a low-numbered bug that you could subscribe someone to
[16:50] <kirkland> or a button that says "Remind this person about the Ubuntu Code of Conduct"
[16:57] <persia> kirkland, There's no easy way, but perhaps you could use a mail filter?  Also, not all users are signatories to the CoC : you can check for "Ubuntutero: Yes" in their profile.
[16:59] <kirkland> persia: gotcha
[17:00] <persia> kirkland, I understand your pain, I'm just not sure there's any sane solution currently available from Launchpad.  I think the only tool available is the big hammer of suspending an account, but that's pointlessly trivial to work around.
[17:00] <persia> (and there have been past cases where attempts at restrictions have resulted in new users)
[17:00] <kirkland> persia: account suspension might be extreme
[17:01] <kirkland> persia: but i've reached wit's end with a few users
[17:01] <persia> procmail is your friend.
[17:01] <kirkland> persia: yeah, i suppose
[18:18] <chx> hi. please compare https://code.launchpad.net/~vcs-imports/drupal/main and http://drupal.org/project/cvs/3060
[18:18] <chx> it seems that the import ... broke? or something
[18:23] <Odd_Bloke> gary_poster: ^
[18:26] <gary_poster> chx, Odd_Bloke: thanks, looking
[18:31] <gary_poster> chx: have not forgotten you.  trying to find someone who would know more than I about it.
[18:34] <chx> gary_poster: thanks.
[18:59] <gary_poster> chx: a dev on that team has looked into the problem, put it into launchpad as a bug, and triaged it.  If you'd like to subscribe to the bug report, here's the URL: https://bugs.launchpad.net/launchpad-bazaar/+bug/281382
[19:00] <ahasenack> guys, I uploaded some packages to a PPA in LP. Then I requested their deletion and I'm watching the repository. Once the files are gone from it, will I be able to upload a package with the same name-version-release to it?
[19:00] <cprov> ahasenack: no
[19:00] <ahasenack> cprov: and a lower version? Also not?
[19:00] <ahasenack> I'm switching from 1.1.1-0ubuntu<IP_ADDRESS> to 1.1.1~bzr20081010-0ubuntu08.04
[19:01] <ahasenack> but the ~ one is lower
[19:01] <cprov> ahasenack: yes, a lower, but new, version will be accepted.
[19:01] <ahasenack> cprov: oh, so that one (with ~) would probably be accepted?
[19:01] <cprov> https://help.launchpad.net/Packaging/PPA#Deleting packages
[19:03] <cprov> ahasenack: only if you don't have any other version like '1.1.1-.*' published in the same series
[19:03] <ahasenack> cprov: ok, thanks
[19:03] <ahasenack> cprov: do I have to wait for the packages to disappear from the repository?
[19:04] <cprov> ahasenack: no, if it's DELETED you can upload a lower version.
[19:04] <ahasenack> cprov: ok, thanks again
[19:04] <cprov> ahasenack: np
[19:05] <persia> cprov, A lower, but different version is accepted?  If you're blocking the same version, surely that's a bug, no?
[19:07] <cprov> persia: no, it's not a bug.
[19:07] <cprov> persia: version blacklist avoid binaries to get rebuilt with the same version (and surely with different contents).
[19:07] <persia> cprov, Then I'm confused.  I thought the rationale for not accepting the same version was to make sure any users of the PPA would be upgraded if a new version appeared.  Is this incorrect?
[19:08] <persia> Yes, but if a lower version is accepted, then I don't see the point of doing that.
[19:08] <cprov> persia: lower versions will just require the user to remove the old binaries if he wants a update.
[19:08] <persia> So why not allow the same version then?
[19:08] <cprov> persia: the lower version is only accepted when the old (but higher) version gets deleted.
[19:09] <persia> I understand.  I just don't see the distinction in use cases.
[19:10] <cprov> persia: currently we are not spread binaries with the same versions but with different contents.
[19:10] <cprov> s/spread/spreading.
[19:10] <persia> From the same PPA.  I can certainly do that with multiple PPAs.
[19:11] <cprov> persia: yes, but the whole point is to not keep diverging binaries cached on clients and those are aware of repository location, right /
[19:12] <persia> But the Packages file will have changed, which means the signatures change, which mean the client downloads it again anyway.
[19:13] <persia> s/signatures/checksums/
[19:13] <cprov> persia: yes, the checksum will change and apt will re-install the binaries
[19:13] <persia> Right, so client cache doesn't matter.
[19:14] <cprov> persia: but how do you know which version a user has installed ?
[19:14] <persia> Why do you care?
[19:14] <cprov> persia: always suggest an upgrade or ask for the bin checksum
[19:14] <persia> Presumably you want the user to have the latest version you released installed.  If you have a repo intended for end-users, you need to have incrementing version numbers anyway.
[19:15] <cprov> persia: because I like PPA users and don't want to see them suffering ;)
[19:15] <persia> I just don't see any value to the blacklist if one can work around it by deleting it and uploading a *lower* package.
[19:16] <cprov> persia: well, there is a value in forcing users to always provide distinct versions, specially because deleted/superseded binaries can be downloaded and installed for testing purpose if necessary.
[19:16] <persia> But they will!  See, routinely people ask "what can I do to work around having uploaded 1.2.3rc4-0ubuntu1~ppa1 to my repo".  They are told they have to do something ugly, like 1.2.3release-0ubuntu1~ppa1".
[19:16] <persia> If they delete and upload 1.2.3-0ubuntu1~ppa1, which you've just said is possible, the users won't see the upgrade, and wil lbe unhappy.
[19:17] <persia> Explaining this to uploaders is significantly easier than explaining to users why they haven't been upgraded to the newest version.
[19:18] <persia> cprov, Well, there's no reason that the version number needs to be used to track that.  If it's just a matter of internal convenience, that's fine, but that should be explicit, and issues should be considered bugs.
[19:20] <cprov> persia: not entirely a internal issue at this point, we are just trying to keep versions distinct w/o forcing unnecessary version bumps.
[19:20] <persia> Hrm?
[19:20] <cprov> persia: I agree, allowing old version is potentially wrong and will block updates
[19:21] <cprov> persia: but it's better then saying "you cannot do it, activate a new PPA."
[19:21] <persia> At the current point, a PPA is not very useful for someone trying to package something for review, because they can't recover from mistakes without mangling the version number.  Apparently, it's not very useful for end-user distribution because it's easy to upload a version that won't get distributed.
[19:21] <persia> I'm not concerned which, but I'd like at least one of these use cases to work.
[19:23] <persia> The workaround for old versions for distribution is to use 1.2.0+really 1.1.7-0~ppa14 or something, just like for a normal archive.
[19:23] <persia> (or 1.2.0release to work around 1.2.0rc4)
[19:24] <persia> This enforces good practice in packagers who might later work with a distribution archive that enforces things.
[19:24] <persia> Alternately, drop the blacklist, and those that intend end-user distribution will have to take care to get it right.
[19:24] <cprov> persia: yes, both relaxed behaviour could work in the PPA context, I agree
[19:25] <cprov> persia: but look from the perspective of end-users, not really familiar with those nuances.
[19:25] <persia> I am.  That's why I want *one* of the two use cases to work.
[19:26]  * persia looks up the relevant bug numbers for context
[19:27] <cprov> persia: if you are really keen I prefer the later (simpler) use-case to work and thus avoiding poll overrides entirely
[19:27] <persia> Hmm.  I can only find one of them.
[19:28] <cprov> persia: but in this case we would have to said a big *sorry* for ahasenack.
[19:28] <persia> cprov, which is the response he would have gotten if he asked in #ubuntu-motu (which happens a couple times a week)
[19:29] <persia> So, if we want to be end-user friendly, bug #263301 should be Won't Fix, and the blacklist should extend to all previous versions as well.
[19:29] <persia> If we want to be uploader friendly, that bug should be fixed, and end-users will suffer.
[19:30] <persia> I'm not sure which is the right answer : it depends on the goal for PPAs.  I'm just annoyed at the current state.
[19:31] <cprov> persia: I agree, let's say 80% ;)
[19:31] <persia> cprov, And to be fair, I should say that most of the time I'm not annoyed at PPAs, and they can be very useful.
[19:32] <cprov> persia: I'd prefer a solution allowing bot use-cases to happen w/o being a configuration nightmare for users.
[19:32] <persia> In fact, the rumor that PPAs would only be available for developers is the primary reason I applied to be a developer.
[19:33] <persia> cprov, That would be ideal, but it's *really* hard.  The only way I thought it might be done is to have it be selectable on a per-PPA basis, and try to have some warning to end-users when using a development PPA.
[19:33] <persia> Not sure how to implement that : if PPA signing worked, maybe by only signing PPAs that followed a strict versioning scheme?
[19:34] <cprov> persia: all PPA will be signed when signing-support is ready (fyi)
[19:34] <persia> I know that's the plan, I was just thinking of a possible variation to support both use cases.
[19:35] <cprov> persia: I've moved that bug to the soyuz pending milestone, so next week it will be discussed/scheduled
[19:35] <cprov> persia: maybe a clearer configuration option would be the best solution.
[19:35] <persia> I've been instructing uploaders who aren't sure to use 1.2.3~ppa4-0~ppa5 as a version when uploading to PPAs to be safe, but that's not ideal either.
[19:36] <persia> For the uploaders, I think configuration works.  On the other hand, I think it's important to have some way of warning downloaders that a given PPA may not be a reliable distribution repository due to version skew.
[19:37] <persia> (unless it is decided that end-users don't matter, but that's not really ideal)
[19:37] <cprov> persia: ehe, no that's not good
[19:39] <persia> The only thing I can think of that will provide an alert to users that something is unreliable is not signing it, which is why I suggested not signing binaries from PPAs that didn't turn on version restrictions.
[19:39] <persia> For package review, the signatures aren't so important, as the reviewer is typically interested in the source package, rather than the binaries.
[19:39] <cprov> persia: let's discuss this with property next week. There are other issues in this area (archive behaviour configuration) that could be improved.
[19:39] <persia> (and the sources are signed anyway, to be accepted for upload)
[19:40] <persia> OK.  Any specific timing?
[19:41] <cprov> persia: we will do a triage round on pending next week, and I will point that bug as a MOTU-concern.
[19:42] <persia> Which bug?  263301?
[19:42] <cprov> persia: yup
[19:43] <persia> I'm not at all certain that's a MOTU concern, as few MOTU are likely to take the set of actions required to be in that state (having experience with the regular archive).
[19:43] <persia> It's more of a concern for those just learning packaging.
[19:44] <cprov> persia: which usually end up requesting MOTU help to solve their issues, right ?
[19:45] <persia> Yeah, but MOTU have zero sympathy for anyone wanting to create a lower version, and most are likely to suggest the same workarounds that would be used in a normal repo, as those are the ones they use when in the same situation.
[19:46] <persia> As much as I'd like to have some sane workflows for review, I'm personally fairly happy with the idea of setting 263301 to Won't Fix, and enforcing the blacklist also for all previous versions.
[19:47] <cprov> persia: right, let's advocate that idea then. I'm also happier doing it.
[19:48] <persia> cprov, OK.  Again, I'm not sure it's a "MOTU Concern", but I'm certainly happy to defend that viewpoint.
[19:49] <cprov> persia: great, let's do it :)
[19:50] <persia> OK.  When?  Where?
[19:50] <cprov> persia: comment the bug, I'll ping you next week.
[19:51] <persia> Beyond my already overlong diatribe?
[19:53] <cprov> persia: you haven't said you want it won't-fix, have you ?
[19:54] <persia> Well, no, because when I complained about it here last time, I was told that supporting developers trying to learn to package was a sufficiently important goal : that's why my comment is about balance.
[19:55] <persia> On the other hand, my last paragraph is fairly negative.
[20:30] <bryce> can I ask launchpadlib questions here?
[20:30] <persia> bryce: leonardr usually has the answers
[20:32] <bryce> leonardr: I want to print the source packages that a team is subscribed to.  I.e., the left column at https://edge.launchpad.net/~ubuntu-x-swat/+packagebugs
[20:32] <bryce> leonardr: how might I do this with launchpadlib?  I'm browsing the api doc but it's not evident what to do
[20:37] <leonardr> bryce, i don't think that has been published yet. if it were published it would show up as a link from the team
[20:37] <leonardr> maybe bac has more info
[20:39] <bac> leonardr, bryce: sorry, not off the top of my head.
[20:39]  * bac digs
[20:39] <leonardr> bac: it's possible it's not a relationship expressed in the schema
[20:39] <leonardr> only expressed in the ui, so we didn't pick up on it
[20:40] <persia> Are there many relationships like that?
[20:40] <leonardr> persia, i don't know, since by definition it's something we missed
[20:40] <bryce> hrm, pitty
[20:41] <leonardr> but it has to show up somewhere in the code
[20:41] <persia> leonardr, heh.  Understood :)
[20:47] <bac> bryce, leonardr: not to pass the buck, but these are methods we'll need to get the bugs team to export to the API
[20:48] <bac> bryce if you could open a bug stating the need it would be helpful.
[20:58] <bryce> bac: ok, against launchpadlib, or a different project?
[21:28] <bac> bryce: just launchpad
[21:34] <bryce> bac: lp #281443
[21:34] <bac> thanks
[21:35] <bryce> yep thanks too.  back to the drawing board for me...
[21:35] <bryce> cya
[21:47] <bryce> I posted the screenscraper I'm using to 281443.  I'll try using that for now.
[21:59] <cprov> matsubara: alright, PQM have another non-loom branch with my changes.
[22:01] <matsubara> cprov: thanks
[22:01] <cprov> matsubara: thank you
[23:31] <exarkun> Hey, can someone tell me about https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/18885
[23:32] <beuno> exarkun, what's up with it?
[23:32] <exarkun> It's associated with a bug in an upstream tracker, twistedmatrix.com/bugs/, #1148
[23:32] <exarkun> and it says "auto-twistedmatrix.com #1148"
[23:32] <exarkun> and if I expand the Twisted bug, then there's a nice pink error dialog
[23:33] <exarkun> http://twistedmatrix.com/bugs/ is actually a years out of date URL to our issue tracker
[23:33] <beuno> exarkun, so you've moved somewere else?
[23:34] <exarkun> beuno: yes, and we're even running the launchpad/trac integration plugin
[23:35] <beuno> exarkun, can you change the URL to the new tracker?
[23:35] <exarkun> Sure, if that's the best thing to do
[23:36] <beuno> yeap, it's just still associated with the old bug tracker
[23:37] <exarkun> and then for my own edification, what's the significance of something like "auto-twistedmatrix.com #1148" in "Remote bug watches"? (specifically the "auto" part)
[23:38] <beuno> that's a great question
[23:38] <beuno> I don't know  :)
[23:38] <beuno> it's friday evening, all the developers have fled
[23:39] <exarkun> heh, alright :)
[23:42] <wgrant> exarkun, beuno: auto just means that it was automatically created by somebody adding a bug watch with an unknown URL.
[23:43] <beuno> there ya' go, good old wgrant to the rescue
[23:43] <exarkun> wgrant: thanks
[23:43] <wgrant> np
[23:52] <Rinchen> exarkun, I'm aware of the issue
[23:53] <Rinchen> exarkun, there's a patch for it already but I'll pass this example up
[23:54] <Rinchen> exarkun, as far as the lp-trac import failures.  Do you need help changing the location?
[23:54] <exarkun> I think I succeeded in changing the location
[23:54] <exarkun> I just entered a new URL and it seems to be using that now
[23:56] <Rinchen> exarkun, I forwarded it over to another dev to peek at on Monday. If it's still broken he'll investigate
[23:57] <exarkun> Rinchen: Cool, thanks
[23:58] <Rinchen> if you've readjusted the import location though exarkun then it should be fixed overnight as your batch jobs run
[23:58] <wgrant> Isn't that much more frequent now?
[23:59] <Rinchen> it is
[23:59] <Rinchen> oh exarkun btw, I think this is bug 278276
[23:59] <wgrant> Or is that only for new ones, not changed?
[23:59] <Rinchen> bugs vs imports wgrant ...  bug checks are run at regularly intervals