| drkokandy | Does anyone know about adding an upstream bug to a bug in Launchpad? I'm trying to add an upstream bug I created to a bug report, and Launchpad does not recognize the URL. The bug is https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1347402 | 02:37 |
|---|---|---|
| ubot5 | Launchpad bug 1347402 in lxsession (Ubuntu) "lxsession-default webbrowser crashes session" [Undecided,Confirmed] | 02:37 |
| drkokandy | And the upstream bug is https://sourceforge.net/p/lxde/bugs/726/ | 02:37 |
| drkokandy | I'm new at this :) Thanks | 02:37 |
| teward | not sure if that's a locked out feature, or not, drkokandy (linking upstream bugs). But if it isn't, then on the LP bug you should see "Also affects project", and it assumes the LXDE project which is a sourceforge tracker (it knows this). It asks for the upstream tracker bug location. | 21:14 |
| drkokandy | Right teward - I was able to get to that page, but when I entered the Sourceforge URL, it says it was not able to recognize the bug tracker at that location | 21:15 |
| teward | drkokandy: from there, it offers you 3 option buttons, of which you select "I have the URL..." one since you have the URL. Then paste the URL, and hit "Add to bug report" | 21:15 |
| teward | drkokandy: might want to state that then, because that seems like a bug | 21:15 |
| teward | dobey: wgrant: cjwatson: ^ know anything bout it? | 21:16 |
| drkokandy | Somehow I found this page: https://bugs.launchpad.net/bugs/bugtrackers/sf - which says that "Bug watch updates for SourceForge.net Tracker are disabled. " - could that have something to do with it? | 21:20 |
| teward | no idea, but https://bugs.launchpad.net/launchpad/+bug/1412052 is filed - might get duped as something else if it's a known issue | 21:22 |
| ubot5 | Launchpad bug 1412052 in Launchpad itself "System unable to process Upstream SourceForge Bug Tracker Entries (observed: lxde project)" [Undecided,New] | 21:22 |
| teward | if it's disabled though it shouldn't be permitting upstream linking, though, or maybe the system isn't smart enough to trace that? | 21:22 |
| * teward shrugs | 21:22 | |
| drkokandy | Works - thanks for your help! | 21:23 |
| drkokandy | Should I convert my question about this to a duplicate of this bug? | 21:23 |
| teward | drkokandy: link to the question? | 21:23 |
| drkokandy | https://answers.launchpad.net/launchpad/+question/260846 | 21:23 |
| teward | nevermind i see it there xD | 21:23 |
| teward | drkokandy: leave it as a question, i linked the bug. | 21:24 |
| drkokandy | thank you - I'm still getting started with helping with Lubuntu bugs & am still learning the ropes | 21:24 |
| teward | drkokandy: i'm going to ping wxl on this too, they probably are aware of this being a consistent issue | 21:25 |
| cjwatson | This is mostly from before my time, but I suspect the root cause is https://bugs.launchpad.net/launchpad/+bug/605783 | 21:30 |
| ubot5 | Launchpad bug 605783 in Launchpad itself "SourceForge bugwatch updates are broken" [High,Triaged] | 21:30 |
| teward | cjwatson: yeah but that bug isn't very descriptive and hasn't been touched since 2k12 | 21:30 |
| cjwatson | That doesn't mean it's somehow magically been fixed | 21:30 |
| * teward assumed abandoned | 21:30 | |
| teward | true. | 21:30 |
| cjwatson | It seems descriptive enough to me | 21:30 |
| * teward shrugs | 21:31 | |
| cjwatson | The Launchpad team was on a single developer for a sizeable amount of the time you refer to | 21:31 |
| teward | true... i assume that's a bit larger though? | 21:31 |
| cjwatson | So, you know | 21:31 |
| cjwatson | We're at three now | 21:31 |
| teward | mmm | 21:31 |
| teward | [15/01/17 16:31:28] <drkokandy> This one maybe - https://bugs.launchpad.net/launchpad/+bug/1154939 ? I can link it | 21:31 |
| teward | [15/01/17 16:31:29] <ubottu> Launchpad bug 1154939 in Launchpad itself "New style SourceForge bug URLs are reported as invalid" [Low,Triaged] | 21:31 |
| ubot5 | Launchpad bug 1154939 in Launchpad itself "New style SourceForge bug URLs are reported as invalid" [Low,Triaged] | 21:31 |
| teward | ^ maybe that one too? | 21:32 |
| cjwatson | I don't know | 21:32 |
| * teward shrugs | 21:32 | |
| drkokandy | I'd assume they're connected | 21:32 |
| cjwatson | The bugtracker code is mostly unfamiliar to me, would take a few days to get my head around it | 21:32 |
| cjwatson | (external bugtracker that is) | 21:32 |
| cjwatson | LP's SourceForge support AFAIK only handles the old-style URLs | 21:33 |
| cjwatson | BugTrackerType.SOURCEFORGE: 'support/tracker.php?aid=%s', | 21:33 |
| teward | cjwatson: ahh, that explains why disabled | 21:33 |
| cjwatson | It's probably not completely ridiculous for somebody new to the codebase to try to fix, starting by grepping for SOURCEFORGE in lib/lp/bugs | 21:35 |
| drkokandy | if I try to add it like that, might it work? | 21:35 |
| drkokandy | I'll try it | 21:35 |
| cjwatson | I don't know, it depends whether the old API in use elsewhere still works, and 605783 suggests not | 21:35 |
| cjwatson | well, "API" | 21:35 |
| teward | cjwatson: if i read that old bug correct, it relied on page scraping? | 21:36 |
| cjwatson | Yes, it uses BeautifulSoup | 21:37 |
| cjwatson | But that sort of thing is obviously not the most robust ever | 21:37 |
| cjwatson | See lib/lp/bugs/externalbugtracker/sourceforge.py | 21:37 |
| cjwatson | If it was broken in 2010, it's unlikely it's improved | 21:38 |
| teward | mhm | 21:38 |
| cjwatson | That file hasn't been changed in any substantive way since 2009 | 21:39 |
| === jelmer_ is now known as jelmer | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!