=== Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk [19:19] === Top 10 Time Out Counts by Page ID === [19:19] Hard / Soft Page ID [19:19] 79 / 4508 Archive:+index [19:19] 33 / 272 BugTask:+index [19:19] 29 / 312 Distribution:+bugs [19:19] 18 / 0 Person:EntryResource:retractTeamMembership [19:19] 13 / 195 POFile:+translate [19:19] 8 / 112 ProjectGroupSet:CollectionResource:#project_groups [19:19] 8 / 17 DistroSeries:+queue [19:19] 7 / 22 Archive:+copy-packages [19:19] 6 / 25 DistroSeriesLanguage:+index [19:19] 6 / 0 Archive:+admin === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [23:09] can anyone offer tips on getting some mods I've made to my local LP instance back upstream - as a hosted branch perhaps [23:09] I've got the default bzr checkout as described in the "Getting" instructions as the topic of this forum (along with some config changes I need to remove from the diff) [23:09] I'm not familiar with bzr, only git [23:10] pcjc2: Commit them to the branch, then bzr push lp:~pcjc2/launchpad/SOME-BRANCH-NAME [23:10] can I commit just certain file, like git add [23:10] bzr commit somefile [23:10] I seem to recall bzr has no "staging area" ceoncept [23:10] (typo) [23:11] That's right. [23:12] You'd normally use 'bzr shelve' (like 'git stash') to "unstage" unwanted changes, or just give filenames to 'bzr commit' [23:14] you can also commit --exclude foo [23:14] cool, thanks [23:15] Ah, didn't know that one. [23:15] Handy. [23:15] https://code.launchpad.net/~pcjc2/launchpad/allow-empty-comments [23:15] (Not quite there yet) [23:16] I need that (or something like that) to import our bug history nicely. Too many placeholders without it [23:16] why not just skip them ? [23:16] wouldn't that be simpler ? [23:17] because the comment contains an attachment [23:17] and it is _really_ ugly to have "Attached file .... [23:17] " [23:17] Wasn't that we wanted a big string of otherwise blank comments ;) [23:18] I've got a load of mods to the SF -> LP bug import script which might be useful to contribute back too [23:18] Making a local cache of downloaded attachments (for when you run it 300 times with different mods ;)) [23:18] And some other things which are vaguely useful - such as stripping some SF cruft from some of the comments [23:19] And some local things to our project, such as turning certain release "groups" into tags, or different bug statuses [23:21] http://bazaar.launchpad.net/~pcjc2/launchpad/allow-empty-comments/revision/12044 [23:21] I'm about at the stage where I am ready to request a test import into staging [23:21] but it looks so much nicer when imported with the above change [23:22] meh - code update in progress on staging, so can't play [23:38] https://code.launchpad.net/~pcjc2/launchpad/allow-empty-comments/+merge/43449 === mhall119_ is now known as mhall119 [23:48] pjdc: we already support adding an attachment without a comment in the core [23:48] bah [23:48] pcjc2: ^ - is that what you're - ah yes, I se [23:48] e [23:49] any chance of seeing that merged? [23:49] probably, but not today. [23:49] Or the behaviour dropped all together? [23:49] I would personally prefer to see that [23:49] I'm trying really hard to convince our other developers that LP is the way forward for bugs [23:50] so your change is uncontentious as is [23:50] I'm sure we can merge it [23:50] if you could add a test that it does really do what you want, that would be awesome [23:50] but one is running of setting up a Bugzilla server. I wanted to get something for people to play with on staging, so I can make sure people like it [23:50] I think the script is tested already [23:50] where do the tests live? [23:51] generally in $package/tests/test_something.py [23:52] ok, found it, thanks.. [23:52] in general, given an XML file, what would be the lead time in getting it imported for people to play with on staging.launchpad.net ? [23:52] (The comment issue is really cosmetic, so shouldn't stop people having a poke at it) [23:53] I'm not sure; however - the sysadmins, who need to run it, are not around in weekends except for emergencies [23:53] also - as a Launchpad coding noob.. how do I run the tests / run this particular test? [23:53] bin/test -t [23:53] e.g. [23:53] bin/test -t test_bugimport [23:54] Who are the sysadmins? (Might even half know one... Chris Jones (Ng)?) [23:54] hes a gsa [23:54] (I say know.. I fixed a video bug for him) [23:54] gsa? [23:54] general sysadmin? [23:54] next one thats up is spm on Monday in roughly this tz now [23:54] yeah [23:54] you need a losa - l* operational sysadmin [23:55] so, pop back in 24 hours and there should be someone that can assist getting an import on either staging or qastaging for you; and once they start on monday there is usually 24 hour coverage through to friday us afternoon [23:55] I won't pretend to understand what a losa -l* ... what you just said.. is ;) [23:56] heh [23:56] I need to run, I'll rad backscroll when I pop back if you had more questions [23:56] thanks for your help, it is much appreciated [23:56] * think I get LOSA now [23:57] launchpad operational system administrator ;) [23:57] to late for me, clearly [23:57] It's been expanded to Launchpad/Landscape/U1/ISD, but yes. [23:59] Do we have any remaining known bugs that cause builds to get stuck in the "Uploading build" status? [23:59] I had it happen to me again today