=== mwhudson_ is now known as mwhudson === yofel_ is now known as yofel === michaelh1 is now known as michaelh1|away === michaelh1|away is now known as michaelh1 === danilo_ is now known as danilos [08:17] G'morning === bulldog98_ is now known as bulldog98 === zyga-afk is now known as zyga [09:34] Hi. Would it be possible to get a "priority" on the official PySide PPA as I uploaded stuff to debug #832864 ? [09:35] OdyX: All of the packages? [09:36] wgrant: only oneiric for apiextractor, generatorrunner,shiboken,pyside . [09:36] That's everything that's pending :) [09:36] * wgrant bumps them all. [09:36] wgrant: yes. :-) Thank you. === jtv is now known as jtv-eat === apachelogger is now known as transitlogger [09:38] OdyX: They're all at the top of the queue now. [09:40] wgrant: great, thanks. (They are interdependent, so will build in a row anyway…) [09:43] OdyX: Only if they have very strict versioned dependencies will they build sequentially. [09:43] s/dependencies/build dependencies/ [09:43] they do. :-) [09:44] 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] If they depwait then I will probably need to re-rescore them once you they're retried. [09:44] And indeed some are depwaiting. [09:45] ah :-/ [09:45] But it's easy enough! [09:47] btw, I wonder why the actual installation of build-dependencies is tried before reporting depwait… [09:47] sbuild until recently was a bit special. [09:48] You can probably see from the log that it has its own resolution algorithm. [09:48] Then tries to apt-get install what it thinks will work. [09:48] Then checks if dpkg-buildpackage rejects the installed versions. [09:48] 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] That will allow it to do version checking beforehand :) [09:49] eh. That might even be the source of the bug I try to tackle… [09:51] 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] OdyX: We only attempt to automatically retry them hourly. [09:51] Since it's somewhat expensive to recheck everything. [09:52] So yes, a manual retry will usually be faster. [09:52] okay. Will do then :-) [10:04] okay, so now I'd need a priority bump of shiboken/amd64/oneiric [10:08] OdyX: Done. [10:08] great === jtv-eat is now known as jtv [11:43] merge proposals show revision history twice on the page (once as unmerged revisions) [11:43] i [11:43] in the two different places it uses a different numberical ordering of revisions [11:43] is that *deliberately* to confuse people? [11:43] :-) [11:45] voidspace: Example url? [11:45] soren: hmmm… I think the one I'm on is private to isd [11:45] soren: let me try and find a public one [11:45] Ah. [11:48] voidspace: You're refering to the "Unmerged revisions" section, as well as the revisions that are shown inline in the comment section? [11:48] Oh, that? [11:48] soren: wgrant: the two lists are branch history and then unmerged revisions [11:49] soren: wgrant; and they're in opposite order to each other [11:49] soren: wgrant: so if you want to look at the most recent revision, where it is is different for each list [11:49] soren: wgrant: so your muscle memory will confuse you every time... [11:49] Branch history? [11:49] wgrant: yes [11:50] I see no section by that name. [11:50] wgrant: well, whatever - there are two lists of revisions on a merge proposal === daker_ is now known as daker [11:50] wgrant: the one without a section title is that one [11:50] wgrant: just below "Add a review or comment" and then the branch url [11:50] voidspace: That's the comment stream. [11:51] Which also includes revisions that are pushed after the proposal is created. [11:51] 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] right === michaelh1 is now known as michaelh1|away [11:52] if there are no comments it just looks like "another revision history" [11:52] but in the opposite order [11:52] well.. [11:52] That's nice for reviews! [11:53] Typically you only change the branch after it's been proposed for merge in response to review comments. [11:53] (reviewers can see what changes went in after the last commit) [11:53] So your changes are interleaved with review comments. [11:53] Right. [11:53] ...and review comments are oldest-first. [11:53] it is nice to have comments interleaved with commits [11:54] hi i am getting an OOPS-2071H26 => https://bugs.launchpad.net/ubuntu/+bug/1?comments=all [11:54] Ubuntu bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] [11:54] https://lp-oops.canonical.com/oops.py/?oopsid=2071H26 [11:55] but where there aren't comments you have two almost identical lists, separated by the comment box, but in opposite order [11:56] ahh. [11:56] Yeah, that's probably confusing. [11:56] even if there are comments, using a different ordering for similar information within the same page is probably not ideal [11:57] anyway :-) === matsubara-afk is now known as matsubara [12:10] wgrant: (pretty please with cherry on top): Please bump priority of pyside/amd64/oneiric on the ~pyside/ppa PPA. === Quintasan_ is now known as Quintasan [13:05] i was wondering where the code for getting info from external bug trackers is located in launchpad [13:05] any hints? [13:33] is there a way to delete files from launchpad project? [13:34] cos^: delete source files? [13:36] nigelb: yep [13:37] i can't find a way to do it [13:40] should i post a request to https://answers.launchpad.net/launchpad ? [13:40] cos^: well, its in bzr right? [13:40] you can just remove it from the code, commit, and push again [13:42] i'm uploading with dput [13:42] and i wouldn't like to upload new version of the source, as it's not finished yet [13:43] Ah, that source. [13:43] well, I don't think there's a way to delete [13:43] you'll just have to bump the version number to supercede it. [13:45] i deleted the whole packages [13:49] cos^: just remember that you have have to bump the version number when you upload next [13:50] yep === beuno is now known as beuno-lunch === deryck is now known as deryck[lunch] === matsubara is now known as matsubara-lunch === beuno-lunch is now known as beuno === matsubara-lunch is now known as matsubara === deryck[lunch] is now known as deryck === abentley changed the topic of #launchpad to: https://launchpad.net/ | Help contact: abentley | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad === med_out is now known as medberry === daker is now known as daker_ [20:30] i'm unable to get taskSearch to find bugs with a particular tag [20:30] bug #656486 [20:30] Launchpad bug 656486 in linux (Ubuntu Natty) "error de Video - [DRM: radeon_ttm_backend_bind] * * ERROR failed to bind 1772 pages at 0x00000000" [Medium,Confirmed] https://launchpad.net/bugs/656486 [20:31] it has the tag "rls-mgr-o-tracking" which if you click on the tag, should find all bugs with that tag [20:31] however, it doesn't show any, not even this one [20:33] nevermind, someone set the status to "Fix Released" and that's why my search is failing === matsubara is now known as matsubara-afk [21:10] 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?