[08:17] <mrevell> G'morning
[09:34] <OdyX> Hi. Would it be possible to get a "priority" on the official PySide PPA <https://launchpad.net/~pyside/+archive/ppa> as I uploaded stuff to debug #832864 ?
[09:35] <wgrant> OdyX: All of the packages?
[09:36] <OdyX> wgrant: only oneiric for apiextractor, generatorrunner,shiboken,pyside .
[09:36] <wgrant> That's everything that's pending :)
[09:36]  * wgrant bumps them all.
[09:36] <OdyX> wgrant: yes. :-) Thank you.
[09:38] <wgrant> OdyX: They're all at the top of the queue now.
[09:40] <OdyX> wgrant: great, thanks. (They are interdependent, so will build in a row anyway…)
[09:43] <wgrant> OdyX: Only if they have very strict versioned dependencies will they build sequentially.
[09:43] <wgrant> s/dependencies/build dependencies/
[09:43] <OdyX> they do. :-)
[09:44] <OdyX> wgrant: (insane) upstream releases the whole stack at once, for each version. Although it could work with older versions, I make the dependencies strict to make sure to compile stuff as upstream expects me to.
[09:44] <wgrant> If they depwait then I will probably need to re-rescore them once you they're retried.
[09:44] <wgrant> And indeed some are depwaiting.
[09:45] <OdyX> ah :-/
[09:45] <wgrant> But it's easy enough!
[09:47] <OdyX> btw, I wonder why the actual installation of build-dependencies is tried before reporting depwait…
[09:47] <wgrant> sbuild until recently was a bit special.
[09:48] <wgrant> You can probably see from the log that it has its own resolution algorithm.
[09:48] <wgrant> Then tries to apt-get install what it thinks will work.
[09:48] <wgrant> Then checks if dpkg-buildpackage rejects the installed versions.
[09:48] <wgrant> We're hoping to upgrade our 7 year old sbuild fork some time this year, to a less ancient version that has a better resolver.
[09:49] <wgrant> That will allow it to do version checking beforehand :)
[09:49] <OdyX> eh. That might even be the source of the bug I try to tackle…
[09:51] <OdyX> wgrant: a final question: does it help (aka "is faster) if I manually ask for a retry for a package in dep-wait state ?
[09:51] <wgrant> OdyX: We only attempt to automatically retry them hourly.
[09:51] <wgrant> Since it's somewhat expensive to recheck everything.
[09:52] <wgrant> So yes, a manual retry will usually be faster.
[09:52] <OdyX> okay. Will do then :-)
[10:04] <OdyX> okay, so now I'd need a priority bump of shiboken/amd64/oneiric
[10:08] <wgrant> OdyX: Done.
[10:08] <OdyX> great
[11:43] <voidspace> merge proposals show revision history twice on the page (once as unmerged revisions)
[11:43] <voidspace> i
[11:43] <voidspace> in the two different places it uses a different numberical ordering of revisions
[11:43] <voidspace> is that *deliberately* to confuse people?
[11:43] <voidspace> :-)
[11:45] <soren> voidspace: Example url?
[11:45] <voidspace> soren: hmmm… I think the one I'm on is private to isd
[11:45] <voidspace> soren: let me try and find a public one
[11:45] <soren> Ah.
[11:48] <wgrant> voidspace: You're refering to the "Unmerged revisions" section, as well as the revisions that are shown inline in the comment section?
[11:48] <soren> Oh, that?
[11:48] <voidspace> soren: wgrant: the two lists are branch history and then unmerged revisions
[11:49] <voidspace> soren: wgrant; and they're in opposite order to each other
[11:49] <voidspace> soren: wgrant: so if you want to look at the most recent revision, where it is is different for each list
[11:49] <voidspace> soren: wgrant: so your muscle memory will confuse you every time...
[11:49] <wgrant> Branch history?
[11:49] <voidspace> wgrant: yes
[11:50] <wgrant> I see no section by that name.
[11:50] <voidspace> wgrant: well, whatever - there are two lists of revisions on a merge proposal
[11:50] <voidspace> wgrant: the one without a section title is that one
[11:50] <voidspace> wgrant: just below "Add a review or comment" and then the branch url
[11:50] <wgrant> voidspace: That's the comment stream.
[11:51] <wgrant> Which also includes revisions that are pushed after the proposal is created.
[11:51] <wgrant> That is a relatively recent addition, and doesn't include revisions that were pushed before the first comment. I thought there was a bug to unify those, but I can't find it.
[11:51] <voidspace> right
[11:52] <voidspace> if there are no comments it just looks like "another revision history"
[11:52] <voidspace> but in the opposite order
[11:52] <soren> well..
[11:52] <nigelb> That's nice for reviews!
[11:53] <soren> Typically you only change the branch after it's been proposed for merge in response to review comments.
[11:53] <nigelb> (reviewers can see what changes went in after the last commit)
[11:53] <soren> So your changes are interleaved with review comments.
[11:53] <nigelb> Right.
[11:53] <soren> ...and review comments are oldest-first.
[11:53] <voidspace> it is nice to have comments interleaved with commits
[11:54] <daker> hi i am getting an OOPS-2071H26 => https://bugs.launchpad.net/ubuntu/+bug/1?comments=all
[11:55] <voidspace> but where there aren't comments you have two almost identical lists, separated by the comment box, but in opposite order
[11:56] <nigelb> ahh.
[11:56] <nigelb> Yeah, that's probably confusing.
[11:56] <voidspace> even if there are comments, using a different ordering for similar information within the same page is probably not ideal
[11:57] <voidspace> anyway :-)
[12:10] <OdyX> wgrant: (pretty please with cherry on top): Please bump priority of pyside/amd64/oneiric on the ~pyside/ppa PPA.
[13:05] <shadeslayer> i was wondering where the code for getting info from external bug trackers is located in launchpad
[13:05] <shadeslayer> any hints?
[13:33] <cos^> is there a way to delete files from launchpad project?
[13:34] <nigelb> cos^: delete source files?
[13:36] <cos^> nigelb: yep
[13:37] <cos^> i can't find a way to do it
[13:40] <cos^> should i post a request to https://answers.launchpad.net/launchpad ?
[13:40] <nigelb> cos^: well, its in bzr right?
[13:40] <nigelb> you can just remove it from the code, commit, and push again
[13:42] <cos^> i'm uploading with dput
[13:42] <cos^> and i wouldn't like to upload new version of the source, as it's not finished yet
[13:43] <nigelb> Ah, that source.
[13:43] <nigelb> well, I don't think there's a way to delete
[13:43] <nigelb> you'll just have to bump the version number to supercede it.
[13:45] <cos^> i deleted the whole packages
[13:49] <nigelb> cos^: just remember that you have have to bump the version number when you upload next
[13:50] <cos^> yep
[20:30] <bjf> i'm unable to get taskSearch to find bugs with a particular tag
[20:30] <bjf> bug #656486
[20:31] <bjf> it has the tag "rls-mgr-o-tracking" which if you click on the tag, should find all bugs with that tag
[20:31] <bjf> however, it doesn't show any, not even this one
[20:33] <bjf> nevermind, someone set the status to "Fix Released" and that's why my search is failing
[21:10] <jo-erlend> When I build packages on Launchpad, I get errors like these: ERROR: Python module pygtk not found. Is that something I need to worry about?