[00:46] <jkakar> Do all Launchpad Blog entries get aggregated on Ubuntu Planet... can I remove Launchpad Blog from my reader?
[00:55]  * Fujitsu wonders if it is a coincidence that most of the projects properly using Launchpad (jokosher, inkscape) are run by Canonical employees.
[00:55] <Fujitsu> schooltool...
[00:57] <jkakar> Fujitsu: What do you mean by "properly"?  Zope and Zope 3 use Launchpad, which are projects not run by Canonical employees.
[00:57] <Fujitsu> Hm, I guess.
[00:59] <lifeless> Fujitsu: When you say most, did you survey? Or is it just a random figure?
[00:59] <lifeless> I'd add paramiko to the list of non-canonical using-launchpad, offhand.
[01:00] <Fujitsu> lifeless: I did not survey, but the ones I know of largely seem to be (I didn't know that paramiko did)
[01:00]  * Fujitsu looks further.
[01:01] <lifeless> you can check the 'uses launchpad for XXX' settings
[01:01] <lifeless> eg. translations or bugs or packaging
[01:01] <Fujitsu> You can't actually search by them, though, can you?
[01:01] <lifeless> google probably can :)
[01:01] <Fujitsu> Haha.
[01:02] <jamesh> Fujitsu: Inkscape will be using Launchpad for bug tracking soon.  Does that count as properly?
[01:03] <jamesh> oops.  that's by a canonical employee :)
[01:03] <Fujitsu> jamesh: Bryce Harringotn.
[01:03] <Fujitsu> Yes.
[01:03] <Fujitsu> Er, spelt properly.
[01:04] <jamesh> Fujitsu: one of the other larger ones is the Silva CMS
[01:04] <jamesh> (yet another CMS built on top of Zope)
[01:05] <elmo> Fujitsu: the schooltool people are not Canonical employees
[01:05] <Fujitsu> elmo: True, but they're quite related.
[01:06] <elmo> Fujitsu: no, they're really not.  Mark's involved in schooltool, but that's a different thing
[01:06] <elmo> (maybe not pertinent to your point/argument, but it's an important distinction outside of that)
[01:08] <jamesh> Fujitsu: https://launchpad.net/moblin is another
[01:08] <Fujitsu> jamesh: A Google shows quite a number, but I've never heard of most of them.
[01:08]  * Fujitsu returns to his cave.
[01:08] <jamesh> and Intel is most definitely a separate company :)
[02:09] <jkakar> I think something might be wrong with PPAs buildds: http://launchpadlibrarian.net/10505500/buildlog_ubuntu-feisty-i386.landscape-client_0.16.0-feisty1-michel2_FAILEDTOBUILD.txt.gz
[02:09] <jkakar> dh_testdir and lsb_release should definitely be available.  And, prior builds with no significant changes to packaging files were successful.
[02:34] <Hobbsee> jkakar: you're not build-depending on debhelper.
[02:35] <Hobbsee> jkakar: you're also not build-depending on lsb-release
[02:35] <Hobbsee> jkakar: therefore, your build will fail.  they're not in build-essential.
[02:35] <Hobbsee> jkakar: so, it's not the buildd that has the problem - i'm afraid it's your package
[02:35] <Hobbsee> morning cprov 
[02:36] <cprov> Hobbsee: hey
[02:39] <cprov> well, the night will be very boring w/o LP, let me have some sleep, g'night folks
[02:39] <Hobbsee> cprov-ZzZ: oops, you broke it :)
[02:55] <Hobbsee> grah!!!!  forgot about the upgrade.
[02:57] <Fujitsu> Hobbsee: Upgrade Extra Long Edition, too.
[02:57] <Hobbsee> yup
[03:01] <jkakar> Hobbsee: Hmm.  I wonder if someone changed something; those Build-Depends are in the code I'm looking at. :)
[03:02] <Hobbsee> jkakar: they're not in the version that got uploaded to launchpad.  mind pastign your debian/control file somewhere?
[03:04] <jkakar> Hobbsee: Uh.  Crap.  Somethings going wrong somewhere.  This thing is b0rked.
[03:04] <jkakar> Hobbsee: Thanks for looking and mentioning that. :)
[03:05] <Hobbsee> jkakar: no problem.  i thought it was.
[03:05] <Hobbsee> jkakar: it'd be *awful* odd to get an error like that on a buildd.
[03:05] <Hobbsee> jkakar: btw, some crazy people do do their packaging entirely without debhelper, so it's not quite mandatory.
[03:06] <jkakar> Hobbsee: Right.  We use AutoPPA which I wrote to make the developer-side of PPA mostly a single-command deal.
[03:06] <Hobbsee> jkakar: also, the buildds build for multiple releases - so depending on the lsb-release on the system wouldn't be  ahelp
[03:06] <jkakar> Hobbsee: It uses a template file to generate the control file; I'm wondering if there's a bug there.
[03:06] <Hobbsee> ahhh, so that's where you're nick is familiar from
[03:06] <jkakar> Yeah, I guess.
[03:07] <Hobbsee> ....why would you need it to write your control file?
[03:07] <ajmitch> differing build depends on various ubuntu releases
[03:07] <jkakar> Hobbsee: We need to produce packages for dapper->hardy.
[03:08] <jkakar> So yeah.
[03:08] <Hobbsee> ajmitch: anything that does build-depends on the fly makes me shudder.
[03:08] <jkakar> AutoPPA detects files that end in .autoppa and processes them to generate the final output; so, a debian/control.autoppa will generate debian/control.
[03:08] <Hobbsee> jkakar: right, yes, different build-depends.  i see.
[03:08] <ajmitch> Hobbsee: I know, I'm not a big fan either :)
[03:08] <Hobbsee> ajmitch: it sounds *awfully* like checkinstall, by another name.
[03:09] <ajmitch> it's not, thankfully
[03:09] <jkakar> I wish it wasn't necessary.
[03:09] <ajmitch> since it's only selecting from a predefined set, not generating them magically
[03:09] <ajmitch> (afaik)
[03:09] <Hobbsee> oh godo
[03:09] <ajmitch> I hope that's the case, I can't remember the details :)
[03:09] <fabbione> morning guys
[03:09] <ajmitch> hi fabbione 
[03:10] <fabbione> how is the upgrade coming along?
[03:10] <Hobbsee> hiya fabbione 
[03:10] <Hobbsee> fabbione: we're mere people, not LP deities.
[03:11] <fabbione> Hobbsee: i didn't expect an answer from mere mortals.. i talk to Gods only
[03:11] <jkakar> LOL
[03:11] <Hobbsee> hahha
[03:11] <Hobbsee> excuse us for responding, then :P
[03:11] <fabbione> Hobbsee: you did ask for it :P
[03:12] <Hobbsee> hehe
[03:12] <jkakar> Hobbsee, ajmitch: It's not magical.  It's very explicit.  Lines in the .autoppa file that start with AUTOPPA_INCLUDE(<release,[...]>): are conditionally included, depending on the release AutoPPA is building for.
[03:12]  * Hobbsee dumps a containers-worth of spiders down fabbione's back
[03:13] <ajmitch> jkakar: that's what I thought, from when you were working on it for storm
[03:13] <jkakar> ajmitch: Yep.
[03:13] <Hobbsee> jkakar: oh right, so it picks the build deps based on what is in each release, and waht's in that file.
[03:14]  * fabbione eats the spiders as they come out of the container
[03:14] <jkakar> Hobbsee: Right.  You specify the build deps you want for each release and put them in that file.  Then AutoPPA generates the right output as it iterates through releases to build.
[03:14] <Hobbsee> ah, okay.  that doesnt sound quite so fragile.
[03:14] <ajmitch> told you it wasn't as bad as checkinstall :)
[03:14] <Hobbsee> that evne sounds snae :P
[03:15] <Hobbsee> ajmitch: i was thinking where you put the general build-deps in, and then it guessed which was in the release, or something
[03:15] <Hobbsee> ajmitch: i mean, that's not quite as bad as checkinstall either - but still highly fragile.
[03:15] <ajmitch> or guess build dependencies by analysing debian/rules or configure.*
[03:16] <Hobbsee> or that
[03:16] <Hobbsee> sheesh, you trying to send me away by saying all this crack or something?  :P
[03:16] <jkakar> Hobbsee: I'm pretty happy with AutoPPA from a user perspective.  I basically generate uploads for 5 Ubuntu releases in 2 minutes now and it mostly works.  Obviously something bad has happened here which I will work out, but other than that it's a great improvement over trying to do all that stuff by hand.
[03:16]  * Hobbsee nods
[03:16] <jkakar> Hobbsee: If you decide to try it out and have questions feel free to ping.
[03:17] <Hobbsee> jkakar: i'd be interested in seeing an .autoppa file, i fyou have one handy
[03:18] <jkakar> Hobbsee: Here's the debian/control.autoppa for Storm: http://rafb.net/p/CsJNjc69.html
[03:19] <jkakar> Hobbsee: With the following snippet in my ~/.autoppa.conf: http://rafb.net/p/eEP3NS34.html
[03:20] <jkakar> The 'ppa = jkakar-ppa' is a reference to a PPA configured in ~/.dput.cf
[03:21] <jkakar> There's one more magical symbol that can be used (anywhere, not just .autoppa files) which is the AUTOPPA_VERSION(<version>) symbol.  It replaces <version>with whatever the current build version is.
[03:23] <jkakar> Oh. Phew.  Yay.
[03:24] <jkakar> I forgot to add "hardy" to the AUTOPPA_INCLUDE() symbols. :)
[03:26] <Hobbsee> hehe
[03:27] <jkakar> The bug is usually between the keyboard and the chair.  It's nice when that's a Good Thing(tm). ;)
[03:28] <ajmitch> yay for simple bugs
[04:48] <jkakar> cprov-ZzZ: Oddly, and I haven't investigated this too closely, the autoppa package (from ppa.launchpad.net/autoppa) does not install (package not found) on gutsy.  I haven't tried on any other release.
[04:49] <jkakar> cprov-ZzZ: I have looked and verified that the relevant .deb files are present.  Any ideas?
[05:18] <Hobbsee> jkakar: when did you try to install ti?
[05:28] <DShepherd> can you guys just ping me to let me know when launchpad is up and running again? thanks
[05:29] <Hobbsee> DShepherd: read ubuntu-devel@l.u.c
[05:29] <Hobbsee> DShepherd: oh, /topic's good too
[05:30] <DShepherd> Hobbsee, ok
[05:31] <jamesh> DShepherd: this rollout is taking a bit longer than usual due to a redesign of some of the tables used by translations.launchpad.net
[05:31] <jamesh> (which should improve performance/reduce timeouts)
[05:34] <baijum> Can anyone update maintenance time here: http://news.launchpad.net/maintenance
[05:35] <DShepherd> jamesh, ok.. oh well. I guess I can wait.. or just google.. I have a gdm crashing here =)
[05:35]  * baijum just checked that page and came here to ask why Launchpad is not yet up...then found the IRC topic
[05:37] <fabbione> guys please let the developers work in quietness instead of asking all the time. it's distracting for them
[05:38] <jamesh> baijum: I'm just checking if anyone is around who can update the page.
[05:38] <DShepherd> fabbione, sorry man. didn't mean not to help 
[05:38]  * DShepherd keeps quiet
[05:40] <baijum> sorry guys...please continue your work
[05:44] <mthaddon> baijum, thx, have updated that page
[05:45] <baijum> mthaddon, np
[07:08] <mpt> yay
[07:17] <jamesh> yay?
[07:39] <mpt> yay, as in, Launchpad is back
[08:51] <carlos> morning
[12:39] <Hobbsee> dear kde, why must you be a ruddy pain to build.
[13:12] <Hobbsee> mpt: ping
[13:14] <Hobbsee> mpt: thanks for hte +editemails link.  when would it be worth filing bugs on the way that page is working (or breaking)?
[13:18]  * carlos -> lunch
[13:25] <Hobbsee> lamont: damn you, why do we need hppa?
[13:30] <jamesh> Hobbsee: look on the bright side.  At least we don't have an amiga port
[13:30] <Hobbsee> jamesh: *snort*
[13:30] <Hobbsee> jamesh: yeah well.  there is that
[13:30] <ubotu> New bug: #164499 in launchpad "+karma page is confusing when all karma has expired" [Undecided,New] https://launchpad.net/bugs/164499
[13:34] <PriceChild> I requested my ppa be cleared a little ago so i could upload a different source archive. I was told I had to wait for a cron at 03:00 but several days later it still hasn't been cleared and there's no response :/ https://edge.launchpad.net/~pricechild/+archive
[13:35] <PriceChild> whoops, https://answers.edge.launchpad.net/launchpad/+question/17826
[13:43] <mpt> Hobbsee, I thought you had already :-)
[13:43] <Hobbsee> mpt: oh, i still need to file those bugs.  but i found another couple of bugs.
[13:44] <Hobbsee> mpt: was thinking i'd wait till after the rollout, although i guess i'm using edge, so it should be recent
[14:00] <danilos> carlos: you?
[14:00] <carlos> yes, me!
[14:00] <carlos> :-P
[14:00] <danilos> carlos: a shame, no meeting today :)
[14:00] <carlos> danilos: there is no meeting this week
[14:00] <carlos> danilos: X-)
[14:50]  * Hobbsee ponders an email filter to automatically delete anything assigned to ubuntu-core-dev
[14:50] <Hobbsee> before you black hole it
[14:53] <Hobbsee> right, done.
[14:53] <Hobbsee> saves myself a bit of spam.
[14:54] <lamont> Hobbsee: hppa?  huh?
[14:54] <Hobbsee> lamont: it's behind :)
[14:54] <lamont> it's catching up
[14:54] <Hobbsee> lamont: walking kde4 thru
[14:54] <Hobbsee> indeed.
[14:54] <Hobbsee> because i want it in a couple of days, not next week :P
[14:55] <lamont> oh.  so you're giving back kde packages, and you want me to bump priority on them??
[14:56] <lamont> hrm.. gaining about 1%/day on graph2 --> 4 weeks we should be current. :))
[14:56] <Hobbsee> lamont: nah.  i can do both givebacks and reprio's now.
[14:56] <lamont> oh.  Hobbsee powerful.
[14:56]  * lamont bows
[14:56] <Hobbsee> yup
[14:56] <Hobbsee>  /nick QueenHobbsee
[14:56] <Hobbsee> :P
[14:58] <lamont> and hppa is down to < 2500 packages.  
[14:58] <lamont> we're gonna have a party when it cracks 2000
[14:58] <Hobbsee> lamont: oh, classy.  it's segfaulting on build, too
[15:01] <lamont> yeah.
[15:01] <lamont> sigsegv or sigbus?
[15:02] <lamont> sigbus is unaligned load/store, which either means you're being bad, or there's a bug somewhere
[15:02] <lamont> which could just be previously compiled stuff
[15:02] <Hobbsee> doesn't say
[15:02] <lamont> sure it does.
[15:02] <lamont> log?
[15:02] <Hobbsee> kdelibs, hardy archive, if you wanted to see
[15:02] <Hobbsee> don't have hte URL on me
[15:03] <lamont> kdelibs in hardy built on hppa
[15:03] <lamont> or do you mean kubuntu-members PPA?
[15:03] <Hobbsee> oh, hardy *main* archive, sorry
[15:03] <lamont> which wouldn't be built on hppa. doh
[15:03] <Hobbsee> it's main archive, unless i specify otherwise :)
[15:03] <lamont> 4:3.5.8-3ubuntu3 built successfully on hppa...
[15:04] <Hobbsee> kde4libs, sorry.
[15:04] <Hobbsee> this numbers-in-packages thing keeps throwing me.
[15:04] <lamont> ah
[15:04] <lamont> esp since it delivers kdelibs5-dev.
[15:05] <lamont> Segmentation fault
[15:05] <lamont> that's SIGSEGV
[15:05] <lamont> SIGBUS == 'Bus Error' :-)
[15:05] <Hobbsee> ah
[15:05] <Hobbsee> yeah, exactly
[15:05] <Hobbsee> lamont: any great objection if i shove all the kde stuff thru, now that it should all build?
[15:06] <Hobbsee> that way hopefully it'llb e done when i wake up, and i can ignore it again.]
[15:06]  * lamont looks at the _other_ log, assuming it's still there
[15:06] <lamont> shove away
[15:06] <lamont> just don't get in the way of main building promptly. :-)
[15:06] <Hobbsee> heh, of course :)
[15:07] <lamont> Nov 22 14:29:41 kohnen kernel: [260212.304000] do_page_fault() pid=5322 command='kde4automoc' type=6 address=0x00000003
[15:07] <lamont> please refrain from branching to NULL function pointers.
[15:07] <lamont> Nov 22 13:59:03 kohnen kernel: [258374.660000] qmake(32487): unaligned access to 0x003ef284 at ip=0x002f6a7b
[15:07] <lamont> Nov 22 13:59:03 kohnen kernel: [258374.660000] qmake(32487): unaligned access to 0x003ef264 at ip=0x002f6a2b
[15:07] <lamont> Nov 22 13:59:03 kohnen kernel: [258374.660000] qmake(32487): unaligned access to 0x003ef264 at ip=0x002f6a2b
[15:07] <lamont> Nov 22 13:59:03 kohnen kernel: [258374.668000] qmake(32487): unaligned access to 0x003ef284 at ip=0x002f6a7b
[15:07] <lamont> bad qmake
[15:08] <lamont> hrm.
[15:09] <lamont> ubuntu is building on hppa with unaligned loads supported.
[15:09] <lamont> that's gonna make a mess out of Camm's packages
[15:10] <lamont> make[1]: Entering directory `/build/buildd/acl2-3.2/books'
[15:10] <lamont> Mon Nov 19 21:32:18 UTC 2007
[15:10] <lamont> /bin/sh: time: not found
[15:10] <lamont> make[1]: *** [all] Error 127
[15:10] <lamont> yeah for bashisms!
[15:10]  * lamont takes that discussion to #-motu
[15:11] <Hobbsee> heh
[15:11] <lamont> #u-motu went away?
[15:11] <Hobbsee> no, it's that you've been drinking too much
[15:11] <lamont> works better with a # in front of it.
[15:20] <Hobbsee> indeed.
[15:20] <Hobbsee> some clients just work when you dont have a # in front of it.
[15:20] <Hobbsee> much simpler
[15:20] <lamont> and yet so wrong.
[15:21] <lamont> doko: I take it back.  ubuntu does build hppa with unaligned traps enabled
[15:21] <lamont> even on the security builds. :-)
[15:58] <towolf_> mrevell: could you admit me into the launchpad-beta-testers team?
[15:59] <mrevell> towolf_: Sure, what's your LP username?
[15:59] <towolf_> mrevell: it's towolf
[15:59] <mrevell> towolf_: I'll look at it ASAP. I'm in the middle of something at the moment.
[16:00] <towolf_> mrevell: alright, gracie mille.
[16:10] <ubotu> New bug: #164530 in rosetta "Translation import queue showing broken links" [Undecided,New] https://launchpad.net/bugs/164530
[16:44] <LaserJock> hi mrevell 
[16:55] <mrevell> hi LaserJock, sorry, was on a phone call
[17:01] <LaserJock> mrevell: when time are you thinking for a PPA101?
[17:01] <LaserJock> *what
[17:02] <mrevell> LaserJock: Late afternoon/early evening UTC I imagine, but obviously your availability would have a great affect on that.
[17:05] <LaserJock> mrevell: looks like Hobbsee's good from 12:00-16:00UTC
[17:06] <mrevell> LaserJock: 15.00 UTC would be 10.00 local time for you, right?
[17:06] <LaserJock> no
[17:06] <LaserJock> 08.00
[17:06] <LaserJock> that might work ok for me
[17:06] <LaserJock> I could do it before going to work
[17:07] <LaserJock> I would say 15:00 UTC would be the earliest I could go
[17:08] <LaserJock> I can try getting up earlier but the odds of me accidentally sleeping in and missing it increase ;-)
[17:08] <mrevell> What's the latest you could do?
[17:12] <LaserJock> well
[17:12] <LaserJock> it'd be nice if it wasn't during my work hours
[17:13] <LaserJock> as at any moment I might need to be AFK
[17:13] <LaserJock> 19:00UTC would be my "lunch break"
[17:13] <LaserJock> and then I'm available from 23:00 UTC on
[17:14] <LaserJock> oh, wait, not 23:00, but 01:00UTC
[17:14] <LaserJock> it's bad when I run into the next day
[17:14] <mrevell> So, would you prefer 15.00 UTC?
[17:15] <LaserJock> I think that might be the best for everybody
[17:16] <LaserJock> it's during the day for Europe and eastern US, not as great for Australian time zones though
[17:16] <ubotu> New bug: #164543 in launchpad "Shouldn't be possible to register two mirrors with two identical URLs by swapping the case in one of them" [Medium,Confirmed] https://launchpad.net/bugs/164543
[17:16] <LaserJock> mrevell: do you remember when it was last time?
[17:16] <mrevell> LaserJock: I'll check
[17:17] <LaserJock> it'd be good if we rotated some
[17:20] <mrevell> Ideally I'd like to do a few of these. If next Wednesday is no good for you, we can put it back.
[17:20] <LaserJock> Wednesday isn't bad actually
[17:20] <LaserJock> but you shouldn't depend on me much either
[17:21] <LaserJock> :-)
[17:22] <mrevell> LaserJock: I expect cprov will lead the session but it'd be handy to have you around for some of the questions that might come up, if you're able.
[17:22] <LaserJock> sure
[17:23] <LaserJock> 15:00 UTC sounds good to me
[17:25] <mrevell> woo
[17:25] <mrevell> :)
[17:37] <towolf_> mrevell: may i annoy you again with wanting to become a beta-testers member?
[17:37] <mrevell> towolf_: Of course. I can check your membership now.
[17:40] <mrevell> towolf_: Welcome to the team :)
[17:41] <towolf_> mrevell: thanks much :)
[17:41] <mrevell> towolf_: np :)
[18:25] <ubotu> New bug: #164555 in launchpad "Search for Firstname Lastname does not find FirnameLastname" [Undecided,New] https://launchpad.net/bugs/164555
[18:32] <blueyed> Hi
[18:32] <blueyed> Do I have to change bug 141516 from "Fix released" before the SRU nomination appears on the radars?
[18:32] <ubotu> Launchpad bug 141516 in gparted "[MASTER] Gparted crashes when refreshing devices" [Medium,Fix released] https://launchpad.net/bugs/141516
[18:33] <blueyed> This is _the_ top crasher in gparted, but nobody seems to care (I've pinged #ubuntu-devel twice already)
[18:34] <Kmos> blueyed: only when it hits the archive
[18:34] <pochu> blueyed: yes, if you reopen it then it will appear in searches and +bugs lists
[18:35] <Kmos> archive i mean.. buildd 
[18:35] <pochu> otherwise it won't, even if a gutsy task is created
[18:35] <blueyed> pochu: no, if the gutsy task would be there, it appears in the relevant lists, e.g. the ubuntu-sru subscription list.
[18:36] <blueyed> But as long as the gutsy task is not approved, it gets hidden all around.
[18:36] <blueyed> I've just pinged pitti, but feel free to confirm it yourself, if you are allowed to.
[18:37] <pochu> I meant it would be hidden in ubuntu/+source/gparted/+bugs, not sure about the rest...
[18:37] <pochu> blueyed: I'd do it if I could...
[18:39] <blueyed> It's getting really frustrating: patches/fixes tend to hang around for a month and nothing happens (this is my experience from the OOo top crasher, where I've also provided/packaged the patch).
[18:41] <pochu> I don't know why, since creating the gutsy task doesn't mean approving it... so that should be really easy...
[18:42] <blueyed> yes, _should_. I'm getting bitter, sorry.
[18:43] <LaserJock> blueyed: you might try emailing ubuntu-devel{-discuss} if nothing seems to get done
[18:44] <LaserJock> things seem to easily get lost/overlooked
[18:44] <blueyed> LaserJock: ok, thanks for the hint. This particular bug is "only" two days around with the patch. But the OOo top crasher is already there for ~1 month.
[18:45] <LaserJock> blueyed: as long as you write with a positive (i.e. Can somebody please have a look at this bug? not You guys suck, wtf?)
[18:46] <LaserJock> I think the devs generally appreciate problems being broght up up
[18:46] <blueyed> LaserJock: sure.. :) Therefor I won't write it now..
[18:46] <blueyed> The main reason why I'm ranting about this here in #launchpad is, that the whole SRU workflow needs to get improved IMHO.
[18:47] <LaserJock> blueyed: how so?
[18:48] <blueyed> e.g. that nominations don't get lost. There might be a view with pending nominations for example.
[18:49] <LaserJock> does it matter much?
[18:49] <LaserJock> I'm not sure how that exactly is a problem. the nomination should get done in a reasonable time for sure
[18:50] <LaserJock> but I don't see how it would be a real workflow problem
[18:50] <blueyed> LaserJock: that's not my experience. IMHO I should not have to poke #ubuntu-devel, pitti or ubuntu-devel ML.
[18:51] <LaserJock> well sure
[18:51] <LaserJock> it takes an Ubuntu Driver to accept the nomination
[18:51] <LaserJock> and there aren't that many Ubuntu Drivers
[18:53] <LaserJock> that's why perhaps an email might be helpful
[18:53] <LaserJock> although I see where having the nomination done *before* the Ubuntu SRU team has a look at it would be helpful
[18:54] <blueyed> Sure, but my whole point is that there should be a view for it in LP / it should appear on the radars of ubuntu-sru, even if it's "Fix released" for hardy.
[18:55] <blueyed> LaserJock: I've done the nomination right away. But ubuntu-sru won't see it anymore, because it's fix released.
[18:55] <LaserJock> well, I'm not sure how they do it
[18:55] <LaserJock> but I suppose so yeah
[18:55] <LaserJock> but in general I've always been in contact with Ubuntu SRU anyway to discuss the SRU
[18:58] <blueyed> pitti just approved the nomination, so all is well regarding this - for the moment.. ;)
[18:59] <LaserJock> well, so your basic complaint is that it takes human interaction to get the SRU nominated?
[19:02] <pochu> LaserJock: the problem is that until a driver creates the gutsy/feisty... bug task, the bug won't be shown in the ubuntu-sru bug list, so they don't check/approve it (providing the main task is already closed)
[19:02] <LaserJock> pochu: well, but that seems sane
[19:02] <LaserJock> as an escalation
[19:03] <LaserJock> but if it's hard to get a bug nomination accepted then that would be a workflow problem
[19:03] <pochu> but the problem is that it gets lost unless you poke a driver...
[19:04] <LaserJock> right, but it's not that there actually a nomination process that is the problem
[19:05] <LaserJock> but that it's difficult to get the nominations accepted if there is not queue to look at or something
[19:07] <pochu> LaserJock: right
[19:08] <LaserJock> ok, so I asked in -devel (if you didn't see it) and there is https://bugs.launchpad.net/ubuntu/hardy/+nominations
[19:08] <LaserJock> so there is a queue
[19:56] <jkakar> Any PPA hackers around?
[19:57] <jkakar> I can't install a package that appears to be in my archive.  apt-get reports it as being missing or obsoleted.
[19:57] <blueyed> LaserJock: yes, that's the view I've asked about. cjwatson has added links to wiki.ubuntu.com/SRU - hopefully this will improve the SRU workflow
[19:57] <pochu> jkakar: have you updated the cache? apt-get update
[19:57] <blueyed> jkakar: have you tried "apt-cache madison <package>"?
[19:58] <jkakar> pochu: Yep.
[19:58] <blueyed> or "apt-cache policy <package>"?
[19:58] <jkakar> blueyed: What does 'madison' do?  I've tried 'apt-cache search <package>'.
[19:58] <jkakar> blueyed: 'apt-cache madison <package>' yield nothing useful.
[19:59] <blueyed> but apt-cache search displays your package?
[19:59] <blueyed> Have you added your ppa to your sources.list?
[20:00] <jkakar> Looks like I have the correct deb lines in my sources.list, too.
[20:00] <jkakar> blueyed: apt-cache doesn't display the package, no.  But I see the .deb file sitting in my PPA archive.
[20:01] <blueyed> jkakar: what's the package?
[20:01] <blueyed> https://edge.launchpad.net/~jkakar/+archive - right?
[20:01] <jkakar> blueyed: autoppa from https://edge.launchpad.net/~autoppa/+archive.
[20:04] <blueyed> jkakar: after adding it to my sources.list it does not appear there, too.
[20:04] <blueyed> neither with "apt-cache search" nor "apt-cache madison/policy"
[20:04] <jkakar> blueyed: Cool.  Thanks for checking.
[20:05] <blueyed> wait..
[20:05] <jkakar> blueyed: And it's weird that the package is here: http://ppa.launchpad.net/autoppa/ubuntu/pool/universe/a/autoppa/
[20:05] <blueyed> I've added the "hardy" line, but it's released for gutsy..
[20:05] <jkakar> I'm testing on a gutsy machine.  I haven't produced hardy builds yet.
[20:05] <jkakar> Hmm.
[20:06] <blueyed> jkakar: use "deb  http://ppa.launchpad.net/jkakar/ubuntu gutsy main", then it should work.
[20:06] <jkakar> I wonder if that's related.
[20:06] <jkakar> blueyed: well, s/jkakar/autoppa/ in that URL, but yes, that's what I'm using and it doesn't work.
[20:06] <blueyed> yes, it is.. :)
[20:06] <jkakar> Well, why do you think that?  I'm not running hardy nor using a hardy URL.
[20:07]  * jkakar files a bug
[20:07] <blueyed> jkakar: sorry, I've been using jkakar from the beginning, but now have "deb  http://ppa.launchpad.net/autoppa/ubuntu gutsy main" and it shows up.
[20:08] <blueyed> jkakar: "apt-cache policy autoppa" outputs nothing?
[20:08] <jkakar> blueyed: Huh, interesting.
[20:09] <jkakar> blueyed: I've been using universe not main.
[20:09] <jkakar> from the control file: Section: universe/devel
[20:09] <jkakar> The weird thing is that I see the same set of packages in both the main and universe parts of the archive.
[20:09]  * jkakar tries main
[20:10] <jkakar> blueyed: Thanks, that was it.  s/universe/main/ on that URL in my sources.list and it shows up.
[20:10]  * jkakar files the *right* bug
[20:11] <blueyed> jkakar: ok :)
[20:19] <jkakar> Filed: bug #164571
[20:19] <ubotu> Launchpad bug 164571 in soyuz "Packages are not published to the right section" [Undecided,New] https://launchpad.net/bugs/164571
[20:23] <jkakar> I guess my report is a dupe of #157561.
[20:23] <jkakar> It seems strangely magical that packages are being auto-moved to main.
[20:24] <kiko> jkakar, it's a feature, not a bug.
[20:24] <kiko> components are irrelevant for PPAs.
[20:24] <kiko> WONTFIX
[20:26] <ubotu> New bug: #164571 in soyuz "Packages are not published to the right section" [Undecided,New] https://launchpad.net/bugs/164571
[20:26] <jkakar> kiko: Fair enough.  Seems like weird behaviour, but whatever.
[20:28] <kiko> jkakar, the alternative causes problems that are very hard to detect and debug, which raises the barrier to new users. I wished there was a way to make this clearer
[20:28] <jkakar> kiko: It would be nice if the universe URL worked as well.  ie: publish to whatever the package specifies AND main.
[20:28] <jkakar> kiko: Though, that's pretty sucky too.  Having one way to get at things is a Good Thing(tm).
[20:28] <kiko> that would be weird. :)
[21:15] <jkakar> kiko: It would be nice if packages were not published to the wrong section in the archive.  That would make the "I see it in the universe section of the archive, why can't I install it?" line of thought less plausible. :)
[21:16] <jkakar> Though I know that will break my apt-mirror script, and likely others, too.
[21:19] <dennda> Hi. I want to delete a branch that has been assigned to a blueprint (until 2 minutes ago) but I can't
[21:20] <dennda> The blueprint doesn't exist anymore, but the branch still claims it is assigned to it and therefore (i think) I cannot delete it
[21:20] <dennda> Any ideas?
[21:32] <kiko> dennda, file a request as per /topic
[22:03] <mpt> Goooooooooooooooooood morning Launchpadders!
[23:31] <kiko> morning mpt