September 2010

Launchpad and Ubuntu24 Sep 2010 12:28 pm

Occasionally, I think it would be useful to know who added a tag to a bug report and when it happened. It’s possible to determine this information at a bug reports +activity page. However, this can be hard to parse as you have something like old value = “apport-bug i386 maverick”, new value = “apport-bug i386 kubuntu maverick regression-potential”. Then you have to manually figure out the diff.

Of course this would be much more useful if you could access it using python-launchpadlib. So I’ve exported bug.activity in the devel version of the API and now you can do interesting things like the following:

bug = launchpad.bugs[630580]
[(a.datechanged, a.person.display_name) for a in bug.activity if a.newvalue
and "regression-potential" in a.newvalue]
[(datetime.datetime(2010, 9, 5, 1, 50, 30, 602479, tzinfo=TimeZone(0)),
'Scott Kitterman')]

Now we know that Scott added the tag regression-potential to the bug on September 5th. Pretty neat!

Launchpad and Ubuntu20 Sep 2010 03:02 pm

Have you ever been subscribed to a bug report with a lot of duplicates? How about not directly subscribed to the bug report with the duplicates but one of the duplicates?

I have and thought it would be helpful to know which duplicate I was subscribed to rather than having to look at every duplicate to see which one was mine. You can now determine this on edge by mousing over your name in the “From duplicates” portion of the subscribers portlet.


Launchpad and Ubuntu16 Sep 2010 01:03 pm

There are a couple of situations where Launchpad hides some bug reports from searches that really shouldn’t be hidden in my opinion.

I recently fixed one of these cases – where if you were to search a distribution series, Maverick for example, for bug tasks via the API you would receive an empty collection. Of course, this makes no sense as Maverick is being actively worked on and it has bug tasks targeted to it. The bug tasks are hidden because omit_targeted parameter had a default value of True. While it is easy to work around by setting omit_targeted to False, this isn’t easily discoverable nor should it even be necessary. If you are searching tasks for a series you want to see the targeted ones!

Anyway, its fixed now but you need to be using the devel version of the API.

Ubuntu15 Sep 2010 03:20 pm

I’m still mostly using Firefox but there has been sufficient interest in using the Launchpad Greasemonkey Scripts in Chromium that I’ve been testing and fixing them to work well with it.

Most of the scripts (lp_highlight_words, lp_karma_suffix, lp_prefilled_description and lp_question_comment) just worked. Well, mostly just worked – I was having an issue where they weren’t always showing up after the first loading of the web page but I’ve resolved that in revision 139 of the launchpad-gm-scripts bzr branch.

One of the most useful scripts, lp_chrome_stockreplies (notice the special version for Chromium), took a bit more work to get functioning. The editing and saving of responses now works great, however it is not possible to load the standard responses from the xml file as XMLHttpRequests are limited to the same domain. Once you get some responses saved though the script is still is a huge help.

The scripts can be installed on an individual basis by browsing the project’s code and clicking the “Download” link or branching the whole tree and opening the scripts in Chromium. As always file any bugs you find about the Launchpad Greasemonkey Scripts project.