From yuriy-kozlov at kubuntu.org Tue Apr 1 02:19:28 2008 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Mon, 31 Mar 2008 22:19:28 -0400 Subject: Kubuntu Hug Day - 01 April 2008 Message-ID: <714626160803311919s1cb5065alcd4164c507b8ee07@mail.gmail.com> It's no joke our next bug day is Tuesday, April 1st! In Launchpad it is possible to monitor upstream bug reports by adding a bug watch and sometimes Launchpad users will add a comment mentioning a url associated with an upstream bug tracker but not add the bug watch. We'll be looking at bug reports with comments regarding the KDE bug tracker and adding the upstream watch where appropriate. The event will be held in #ubuntu-bugs on Freenode. The list of targeted bugs and tasks is posted at: https://wiki.ubuntu.com/UbuntuBugDay/20080401/KDE Our goal is to deal with all of the bugs on that list. So on 01 April 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Kubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno, jcastro, yuriy and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! ~ Yuriy From pedro at ubuntu.com Tue Apr 1 20:39:30 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 01 Apr 2008 16:39:30 -0400 Subject: Celebrating Hug Day! - 03 April 2008 Message-ID: <1207082370.9944.32.camel@diprotodon> Hello Ubuntu Lovers, Following with our rocking Hug Days, Next Thursday 03 of April we'll be celebrating a firefox-3.0 and xulrunner-1.9 Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080403 Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on Thursday 03 of April In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno, asac and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, pedro. From brian at ubuntu.com Wed Apr 2 17:36:21 2008 From: brian at ubuntu.com (Brian Murray) Date: Wed, 2 Apr 2008 10:36:21 -0700 Subject: Triaging Specialties Message-ID: <20080402173621.GP11040@murraytwins.com> Greg Grossmeier's and I've setup a table listing members of the Bug Squad and the packages that are adept at triaging. Our thought was it would be a useful guide of who talk to if you need help debugging a particular package or part of Ubuntu. Please take a moment to add yourself and packages you can help others debug at https://wiki.ubuntu.com/BugSquad/Contacts. Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From brian at ubuntu.com Fri Apr 4 23:44:38 2008 From: brian at ubuntu.com (Brian Murray) Date: Fri, 4 Apr 2008 16:44:38 -0700 Subject: Bug Day - 08 April 2008 Message-ID: <20080404234437.GI11040@murraytwins.com> It's been about two months since we've looked at bugs with out a package and the number is continuing to grow. So let's take a look at these on Tuesday, April 8th! We can easily help these bug reports by assigning them to the right package but it'd be best to get them triaged. The event will be held in #ubuntu-bugs on Freenode. The bug list I've created is focused on reports that should be about Hardy and is at: https://wiki.ubuntu.com/UbuntuBugDay/20080408 Our goal is to deal with all of the bugs on that list and then move on to other bugs without a package. So on 08 April 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From macoafi at gmail.com Tue Apr 8 14:53:31 2008 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 08 Apr 2008 10:53:31 -0400 Subject: Big scanner regression Message-ID: <1207666411.17152.11.camel@ada> Somehow between Gutsy and Hardy (I'm guessing with the new CUPS GUI), a regression was introduced where no HP scanners work with Hardy. These were probably the easiest scanners to get going before, and because they're attached to the very-compatible HP printers, I'm sure a *lot* of people have them. Is there any chance of this being fixed by release? It's bug #135194 https://bugs.launchpad.net/bugs/135194 -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From pedro at ubuntu.com Tue Apr 8 20:46:45 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 08 Apr 2008 16:46:45 -0400 Subject: Celebrating Hug Day! - 10 April 2008 Message-ID: <1207687605.6017.17.camel@diprotodon> Hello Ubuntu Lovers, On Thursday 10 of April we'll be celebrating a Compiz Hug Day: https://wiki.ubuntu.com/UbuntuBugDay/20080410 Our goal is to deal with all of the bugs on that list. Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything. In a Bug Day, you can * work in a nice team, * make sure the bug reporters' concerns are heard, * gather all the information needed so developers can fix bugs, * close useless bugs, * find out where the bugs come from, and eventually * work together with upstream to make changes happen, * get experience in hacking and fixing bugs. Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too! When to join the Hug Day? Next hug day is on Thursday 10 of April In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. While you are welcome to apply to join the Ubuntu Bug Control team at anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, ogasawara, pedro, heno and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Have a nice day, pedro. From jw+debian at jameswestby.net Wed Apr 9 17:47:08 2008 From: jw+debian at jameswestby.net (James Westby) Date: Wed, 09 Apr 2008 18:47:08 +0100 Subject: Bugs with patches attached Message-ID: <1207763228.6246.66.camel@flash> Hi all, There is currently a discussion in #debian-devel that would benefit from some input from triagers. Part of the discussion is about making best use of the patches that are attached to some bugs by people that are not involved in Ubuntu development enough to know how to take them further. There is a worry that firstly there are plenty of patches sitting in launchpad that just aren't getting seen by the right people. The further concern is that when they are seen we ask too much of the submitters and so drive people away from contributing. I would firstly like some input from people who deal with bugs. Do you see many patches attached to bug reports? When they are are they looked at by a developer? If they are does there seem to be too much asked of the submitter, like needless changes the developer could quite easily do themselves? Do you know how to deal with a bug that has a patch attached? We have a problem if the answer to the first question is yes, and the second no. If that is indeed the case we need to do something about it. If the last answer is no then we can do something about that as well. I have added myself to the contacts page as a contact for bugs with patches attached. Therefore if you see a bug get a patch attached, and it's not clear whether it's being watched by a developer then please contact me and point me to the bug. I will then try and see if I can hook the bug up with a developer to get the patch looked at. I'm also happy to just give pointers to other people if you want to asses a patch for yourself and get it looked at. I have no idea how much work this will be, so if it gets too much we'll have to come up with something else. Much in the same vein as this, does anyone know a way to receive notifications whenever a patch is added to a bug (defined by the checkbox that they can select as they submit it)? Thanks, James From macoafi at gmail.com Wed Apr 9 17:53:23 2008 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 09 Apr 2008 13:53:23 -0400 Subject: Bugs with patches attached In-Reply-To: <1207763228.6246.66.camel@flash> References: <1207763228.6246.66.camel@flash> Message-ID: <1207763603.32332.6.camel@ada> On Wed, 2008-04-09 at 18:47 +0100, James Westby wrote: > Hi all, > > There is currently a discussion in #debian-devel that > would benefit from some input from triagers. > > Part of the discussion is about making best use of the > patches that are attached to some bugs by people > that are not involved in Ubuntu development enough > to know how to take them further. > > There is a worry that firstly there are plenty of patches > sitting in launchpad that just aren't getting seen by > the right people. The further concern is that when > they are seen we ask too much of the submitters and > so drive people away from contributing. One problem I have is although I could write patches for a couple bugs I've spotted in, for example, Universe packages, I don't know how to make a debdiff (or even what one is), but when you have a patch, that's what they ask for. I don't know anything about packaging, so I don't know how to get the fixes in for the few little things that I know I can fix. Given that feature freeze is in effect, I know I won't be able to fix the fact that a few of the menu options in Rubrica are in Italian while the rest of the program is in English before Hardy ships. I know where each button is, so i just don't read it. That won't work for everyone. Making it easier to separate patch-writer from packager would, in my opinion, be helpful. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From micahcowan at ubuntu.com Wed Apr 9 18:41:56 2008 From: micahcowan at ubuntu.com (Micah Cowan) Date: Wed, 09 Apr 2008 11:41:56 -0700 Subject: Bugs with patches attached In-Reply-To: <1207763603.32332.6.camel@ada> References: <1207763228.6246.66.camel@flash> <1207763603.32332.6.camel@ada> Message-ID: <47FD0DF4.2050007@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mackenzie Morgan wrote: > On Wed, 2008-04-09 at 18:47 +0100, James Westby wrote: >> The further concern is that when >> they are seen we ask too much of the submitters and >> so drive people away from contributing. > > One problem I have is although I could write patches for a couple bugs > I've spotted in, for example, Universe packages, I don't know how to > make a debdiff (or even what one is), but when you have a patch, that's > what they ask for. And, indeed, it's a complicated process. Not only does one have to know enough to generate the original patch in the first place, but with a debdiff, you now have to know how to integrate that patch with whatever flavor of patching system is being used in that particular source package (quilt? dpatch? dbs?) if there is one. You also have to get familiar with debuild to build the source package, and then, quite likely, pbuilder to test it with (which takes some amount of setup, first). In short, it's a great investment for those who expect to be making many such patches (say, package maintainers, and folks specifically interested in becoming active in Debian (and derivatives) development), and far less so for people who just want to get their freaking fix in. :) > Making it easier to separate patch-writer from packager would, in my > opinion, be helpful. The trouble, particularly on the Ubuntu side of things, is that there are so few developers in relation to the number of packages. Nobody generally has the time to take on responsibility for properly packaging someone _else's_ patch. This would be helped perhaps by improving Ubuntu tendencies to forward patches upstream. This is already fairly good, but could (to my memory) be improved. There needs to be a widespread understanding that patches should be checked against upstream first thing (current dev versions of course), and if appropriate, left in their care (but tracked in LaunchPad too, so it doesn't get lost if they don't rush to deal with it); when that's not appropriate, forwarding to Debian probably is. Upstream maintainers -> Debian -> Ubuntu, follows decreasing numbers of resources, in general: best to try with the folks with the most, first. The downside, of course, is that Ubuntu users must then wait, not only for upstream to decide to apply the patch, but for it to trickle down to them from Debian, as well. Still, for at least those packages that have no real maintainers in Ubuntu, that seems like the best approach. Critical patches may be an exception. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH/Q3z7M8hyUobTrERAuuqAJ4/C1aeEKdbf19F6CDAvT4e1+a8dwCfZLHo ZPAthSdTUulyevq2FgJeMR8= =uKhh -----END PGP SIGNATURE----- From jw+debian at jameswestby.net Wed Apr 9 19:15:11 2008 From: jw+debian at jameswestby.net (James Westby) Date: Wed, 09 Apr 2008 20:15:11 +0100 Subject: Bugs with patches attached In-Reply-To: <1207763603.32332.6.camel@ada> References: <1207763228.6246.66.camel@flash> <1207763603.32332.6.camel@ada> Message-ID: <1207768511.6246.73.camel@flash> Hi Mackenzie, Thanks for responding, On Wed, 2008-04-09 at 13:53 -0400, Mackenzie Morgan wrote: > One problem I have is although I could write patches for a couple bugs > I've spotted in, for example, Universe packages, I don't know how to > make a debdiff (or even what one is), but when you have a patch, that's > what they ask for. One of the things talked about in the discussion that I referred to was this requirement. Some were unhappy that given a perfectly good patch some people would ask for a debdiff instead, when the work of turning it in to a debdiff for someone who knows what they are doing is small compared to testing it and everything else. I agree with this, and so that's one of the reasons I would like to put some time in to this. I'm sorry you've been discouraged from contributing in this way by this issue. > I don't know anything about packaging, so I don't > know how to get the fixes in for the few little things that I know I can > fix. Given that feature freeze is in effect, I know I won't be able to > fix the fact that a few of the menu options in Rubrica are in Italian > while the rest of the program is in English before Hardy ships. I know > where each button is, so i just don't read it. That won't work for > everyone. > > Making it easier to separate patch-writer from packager would, in my > opinion, be helpful. > I would love to take any patch that you have and get it uploaded. If you have the time to write a patch then please do so and assign the bug to me and I'll take a look. Although I'm happy to do it, I don't think we're in the position currently to have something like a debdiff service when you can write a patch and pass it on to this group. However not using contributions as they aren't quite in the right form should definitely be avoided. Thanks, James From thekorn at gmx.de Wed Apr 9 22:03:07 2008 From: thekorn at gmx.de (markus korn) Date: Thu, 10 Apr 2008 00:03:07 +0200 Subject: Bugs with patches attached In-Reply-To: <1207763228.6246.66.camel@flash> References: <1207763228.6246.66.camel@flash> Message-ID: <7533d3600804091503yf36edafge6b11bc58b60afdc@mail.gmail.com> In my opinion this whole discussion is not related to bug triaging at all, launchpad.net has to provide a clearer interface to handle patches. Some changes would simplify the patch committing process a lot: * allow subscribing to new patches on a per package basis this could be similar to the new "subscribing to bugmail"-feature. this way people and groups can be directly notified when new patches are added to a bugreport. as a result of this groups can easily implement an IRC bot for patch notification for example. * improve the +addcomment page Let's say I'm new to LP and/or ubuntu and I would like to submit a patch. It would be nice if this site could give me the names of the maintainer and the uploader (and people who are interested in new patches for this special sourcepackage). This are the people to whom I can address my patch and who I can get in contact with when I have some more questions. * better presenting of patches in LP some bugreports have lots of attachments, in this case it would be nice if there could be a seperate "patches" applet in the very left column * list of patches on a per package basis * adding an extra icon for bugreports with attached patches in buglists there ar icons for milestones, branches and available mentors, why not adding a icon for patches just my 0.5 cent :) Markus From hanno.stock at gmx.net Wed Apr 9 22:15:04 2008 From: hanno.stock at gmx.net (Hanno Stock) Date: Thu, 10 Apr 2008 00:15:04 +0200 Subject: Bugs with patches attached In-Reply-To: <1207768511.6246.73.camel@flash> References: <1207763228.6246.66.camel@flash> <1207763603.32332.6.camel@ada> <1207768511.6246.73.camel@flash> Message-ID: <47FD3FE8.6070400@gmx.net> Hi! James Westby schrieb: > I would love to take any patch that you have and get it uploaded. If > you have the time to write a patch then please do so and assign the > bug to me and I'll take a look. > > Although I'm happy to do it, I don't think we're in the position > currently to have something like a debdiff service when you can > write a patch and pass it on to this group. Actually - why not have a team that deals with this? People could subscribe a bug with a patch to some kind of "patch-sponsors" team and a member of the team would then create a debdiff and subscribe universe-sponsors or any other appropriate team. Actually this could be a good place for non-MOTUs (like me) to contribute and maybe show their packaging skills. The benefit would be that one could have some kind of procedure to follow, similar to the other sponsoring queues, but with less requirements. For example: It might be to much of a requirement for a patch author to know how to create a debdiff, but maybe one could ask that some mandatory information of how to apply the patch and against what version, etc. is provided before subscribing "patch-sponsors". (i.E. is the patch against the debianized version or against the clean source, etc.) Also triagers could subscribe "patch-sponsors" if they think all necessary information is provided. The problem with the current system of just searching for bugs with "patch attached" is that often the patches are outdated, abandoned, etc. I don't have much spare time at the moment and therefore searching through these lists is a tedious task. On the other hand, I have most of the packaging tools set up and in some cases can come up with a debdiff quite quickly. So if I get patches from authors willing to collaborate delivered to my inbox (via such a team subscription for example), I'm happy to jump in and help. Just my 2 cents. Hanno From hanno.stock at gmx.net Wed Apr 9 22:16:09 2008 From: hanno.stock at gmx.net (Hanno Stock) Date: Thu, 10 Apr 2008 00:16:09 +0200 Subject: Bugs with patches attached In-Reply-To: <7533d3600804091503yf36edafge6b11bc58b60afdc@mail.gmail.com> References: <1207763228.6246.66.camel@flash> <7533d3600804091503yf36edafge6b11bc58b60afdc@mail.gmail.com> Message-ID: <47FD4029.8050305@gmx.net> Hi! markus korn schrieb: > In my opinion this whole discussion is not related to bug triaging at > all, launchpad.net has to provide a clearer interface to handle > patches. [...] I agree with you. Also it would be great if one could distinguish between different types of patches in Launchpad, e.g. "patch" or "debdiff". While this is Ubuntu-specific and Launchpad is not just for Ubuntu, one could think of configurable attachment types for specific projects. From caroline.ford.work at googlemail.com Wed Apr 9 22:22:45 2008 From: caroline.ford.work at googlemail.com (Caroline Ford) Date: Wed, 9 Apr 2008 23:22:45 +0100 Subject: Bugs with patches attached In-Reply-To: <1207763228.6246.66.camel@flash> References: <1207763228.6246.66.camel@flash> Message-ID: On 09/04/2008, James Westby wrote: > Hi all, > > There is currently a discussion in #debian-devel that > would benefit from some input from triagers. > > Part of the discussion is about making best use of the > patches that are attached to some bugs by people > that are not involved in Ubuntu development enough > to know how to take them further. > > There is a worry that firstly there are plenty of patches > sitting in launchpad that just aren't getting seen by > the right people. The further concern is that when > they are seen we ask too much of the submitters and > so drive people away from contributing. > > I would firstly like some input from people who deal > with bugs. > > Do you see many patches attached to bug reports? > > When they are are they looked at by a developer? > > If they are does there seem to be too much asked of > the submitter, like needless changes the developer > could quite easily do themselves? > > Do you know how to deal with a bug that has a patch > attached? > > We have a problem if the answer to the first question is > yes, and the second no. If that is indeed the case we > need to do something about it. If the last answer is no > then we can do something about that as well. > > I have added myself to the contacts page as a contact > for bugs with patches attached. Therefore if you see a bug > get a patch attached, and it's not clear whether it's being > watched by a developer then please contact me and point > me to the bug. I will then try and see if I can hook the > bug up with a developer to get the patch looked at. > > I'm also happy to just give pointers to other people if > you want to asses a patch for yourself and get it looked > at. > > I have no idea how much work this will be, so if it gets too > much we'll have to come up with something else. > > Much in the same vein as this, does anyone know a way to > receive notifications whenever a patch is added to a bug > (defined by the checkbox that they can select as they > submit it)? I once made a diff and submitted it to a bug. I got a form reply back telling me a make a debdiff, with a link to the packaging guide. I didn't as I didn't have time/know how. The real problem is knowing that you have to subscribe a team. I made a debdiff yesterday and looked on the wiki so I knew the exact name of the *-sponsors team to subscribe. I wasn't sure whether I should subscribe universe-sponsors or motu-release as it's never clear cut whether bug fixes are a release exception or not. The various wiki pages were not helpful. I didn't subscribe motu-release and I think it's gone through. People shouldn't need to know code *and* Debian packaging to submit fixes. We also need to find a way of dealing with the patch sponsorship bureaucracy. Caroline From persia at ubuntu.com Wed Apr 9 22:39:29 2008 From: persia at ubuntu.com (Emmet Hikory) Date: Thu, 10 Apr 2008 07:39:29 +0900 Subject: Bugs with patches attached In-Reply-To: <1207763228.6246.66.camel@flash> References: <1207763228.6246.66.camel@flash> Message-ID: <9bd2f8970804091539h73918907n5ef08e107e7d1e30@mail.gmail.com> James Westby wrote: > There is currently a discussion in #debian-devel that > would benefit from some input from triagers. <...> > Do you see many patches attached to bug reports? It is uncommon, but there are at least hundreds of patches currently available. > When they are are they looked at by a developer? Typically only when the developer would look at the bug otherwise, although some developers search for bugs with patches available. > If they are does there seem to be too much asked of > the submitter, like needless changes the developer > could quite easily do themselves? It very much depends on who looks at the patch. If the patch is first examined by a potential sponsor, they may ask for corrections to be able to sponsor the patch. For developers working on a package, the patch is often integrated with their own work. Some new developers, used to sponsor feedback, might also pass sponsor-type hints to the patch submitter, which in some cases can be frustrating to the patch submitter. > Do you know how to deal with a bug that has a patch > attached? Personally, it depends on where I find it. If I encounter it as part of a bug report that I'm triaging, I tend to consider it confirmation, and if the patch seems to do the right thing, even consider it Triaged. If I encounter the patch as a bug on a package that I'm updating, I typically include the patch in the changes for the next update. If I encounter a non-debdiff patch in the sponsors queue, I add the patch tag, and ask for a debdiff. > I have added myself to the contacts page as a contact > for bugs with patches attached. Therefore if you see a bug > get a patch attached, and it's not clear whether it's being > watched by a developer then please contact me and point > me to the bug. I will then try and see if I can hook the > bug up with a developer to get the patch looked at. Daniel Holbach recently introduced the "Really Fix It" site (1), which acts as yet another means by which developers can easily find bugs with patches attached (or other simple cases) to help combine those patches into a new revision for upload. This is relatively new, and external, so it may not yet be part of many developers common resource lists, but it may be a help to you in interesting developers in these bugs. 1: http://daniel.holba.ch/really-fix-it/ -- Emmet HIKORY From a.starr.b at gmail.com Thu Apr 10 23:09:32 2008 From: a.starr.b at gmail.com (Andrew) Date: Thu, 10 Apr 2008 19:09:32 -0400 Subject: Bugs with patches attached Message-ID: While the wiki has some short comings, it does have a pretty good description of how to create a debdiff: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff Another important one to read if you want to delve into this is: https://wiki.ubuntu.com/PackagingGuide/PatchSystems At least half of the uploads that I've got in to Hardy were from creating debdiffs of patches sitting on LP. Many of them had been there for quite awhile. Daniel's Really-Fix-It ( http://daniel.holba.ch/really-fix-it/ ) has helped a lot with this issue. Over on the MOTU list, they've been talking about having Bug-squad-like Hug Days to deal specifically with bugs with patches attached. The one thing that has kept me back from doing more of this is that often I come across patches for programs that I have never used. I'm not much of a programmer, so I'm often weary of touching packages that I don't know too much about. If you have a patch that will fix a bug please upload it. If you have no intention of turning it into a debdiff, just say so. There are folks out there that are willing to do it for you. I think the real issue is making sure those people can find what needs their attention. From daniel.holbach at ubuntu.com Fri Apr 11 10:43:12 2008 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Fri, 11 Apr 2008 12:43:12 +0200 Subject: Bugs with patches attached In-Reply-To: References: Message-ID: <47FF40C0.8050303@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew schrieb: > The one thing that has kept me back from doing more of this is that > often I come across patches for programs that I have never used. I'm > not much of a programmer, so I'm often weary of touching packages that > I don't know too much about. In those cases we should forward the patch to the upstream developers, link the upstream bug in LP and wait for an answer there. This will give us a definite "go ahead". > If you have a patch that will fix a bug please upload it. If you have > no intention of turning it into a debdiff, just say so. There are > folks out there that are willing to do it for you. I think the real > issue is making sure those people can find what needs their attention. If you have any idea on how to make really-fix-it more usable, please let me know. Have a nice day, Daniel - -- My 5 today: #91873 (eject), #192887 (ubuntu), #193256 (glipper), #185890 (python-bibtex), #84501 (epiphany-browser, openjdk-6, sun- java6) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH/0DARjrlnQWd1esRAmNvAJ4562MtXdZvlKLm9xt0M7Y1D4UYeACfbcIY MoBmNUb1+87m8OJGST4DwjQ= =sKh7 -----END PGP SIGNATURE----- From lists at suares.an Thu Apr 17 01:07:11 2008 From: lists at suares.an (Ace Suares) Date: Wed, 16 Apr 2008 21:07:11 -0400 Subject: Closing a bug Message-ID: <200804162107.11088.lists@suares.an> Hiya https://bugs.launchpad.net/openoffice/+bug/70981 How to deal with this: 1. it's still a bug in feisty,. 2. it's not a bug in gutsy 3. somehow the 'affects' lists 4 items; two of them is fix release, one confirmed, one invalid. What to do to close the bug !? ace From brian at ubuntu.com Thu Apr 17 02:57:22 2008 From: brian at ubuntu.com (Brian Murray) Date: Wed, 16 Apr 2008 19:57:22 -0700 Subject: Closing a bug In-Reply-To: <200804162107.11088.lists@suares.an> References: <200804162107.11088.lists@suares.an> Message-ID: <20080417025722.GA23156@murraytwins.com> On Wed, Apr 16, 2008 at 09:07:11PM -0400, Ace Suares wrote: > > Hiya > > https://bugs.launchpad.net/openoffice/+bug/70981 > > How to deal with this: > > 1. it's still a bug in feisty,. > 2. it's not a bug in gutsy > 3. somehow the 'affects' lists 4 items; two of them is fix release, one > confirmed, one invalid. In this particular bug we are being shown how it affects multiple different packages and projects. We have the following: KDE PIM - an upstream project OpenOffice - another upstream project kdelibs (Ubuntu) - an Ubuntu package openoffice.org (Ubuntu) - an Ubuntu package > What to do to close the bug !? The bug is "closed", or in an end state, for almost every thing it affects. The only remaining open affects is the upstream OpenOffice bug and if the bug really isn't an OpenOffice bug it'd be best if we were to get that upstream bug closed too. This is a really neat question as it illustrates how a bug can affect many different things which isn't the case with every bug. I hope my answer helps explain things. Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From lists at suares.an Thu Apr 17 11:36:08 2008 From: lists at suares.an (Ace Suares) Date: Thu, 17 Apr 2008 07:36:08 -0400 Subject: Closing a bug In-Reply-To: <20080417025722.GA23156@murraytwins.com> References: <200804162107.11088.lists@suares.an> <20080417025722.GA23156@murraytwins.com> Message-ID: <200804170736.08626.lists@suares.an> On Wednesday 16 April 2008, Brian Murray wrote: > On Wed, Apr 16, 2008 at 09:07:11PM -0400, Ace Suares wrote: > > Hiya > > > > https://bugs.launchpad.net/openoffice/+bug/70981 > > > > How to deal with this: > > > > 1. it's still a bug in feisty,. > > 2. it's not a bug in gutsy > > 3. somehow the 'affects' lists 4 items; two of them is fix release, > > one confirmed, one invalid. > > In this particular bug we are being shown how it affects multiple > different packages and projects. We have the following: > > KDE PIM > - an upstream project > OpenOffice > - another upstream project > kdelibs (Ubuntu) > - an Ubuntu package > openoffice.org (Ubuntu) > - an Ubuntu package > > > What to do to close the bug !? > > The bug is "closed", or in an end state, for almost every thing it > affects. The only remaining open affects is the upstream OpenOffice > bug and if the bug really isn't an OpenOffice bug it'd be best if we > were to get that upstream bug closed too. > > This is a really neat question as it illustrates how a bug can affect > many different things which isn't the case with every bug. I hope my > answer helps explain things. > > Thanks, Hi, How to close an upstream bug ? Is that a bug in another bug system (i.e. not Malone/Launchpad) ? ace From lists at suares.an Thu Apr 17 11:45:47 2008 From: lists at suares.an (Ace Suares) Date: Thu, 17 Apr 2008 07:45:47 -0400 Subject: Closing a bug In-Reply-To: <20080417025722.GA23156@murraytwins.com> References: <200804162107.11088.lists@suares.an> <20080417025722.GA23156@murraytwins.com> Message-ID: <200804170745.47513.lists@suares.an> On Wednesday 16 April 2008, Brian Murray wrote: > On Wed, Apr 16, 2008 at 09:07:11PM -0400, Ace Suares wrote: > > Hiya > > > > https://bugs.launchpad.net/openoffice/+bug/70981 > > > > How to deal with this: > > > > 1. it's still a bug in feisty,. > > 2. it's not a bug in gutsy > > 3. somehow the 'affects' lists 4 items; two of them is fix release, > > one confirmed, one invalid. > > In this particular bug we are being shown how it affects multiple > different packages and projects. We have the following: > > KDE PIM > - an upstream project > OpenOffice > - another upstream project > kdelibs (Ubuntu) > - an Ubuntu package > openoffice.org (Ubuntu) > - an Ubuntu package > > > What to do to close the bug !? > > The bug is "closed", or in an end state, for almost every thing it > affects. The only remaining open affects is the upstream OpenOffice > bug and if the bug really isn't an OpenOffice bug it'd be best if we > were to get that upstream bug closed too. > > This is a really neat question as it illustrates how a bug can affect > many different things which isn't the case with every bug. I hope my > answer helps explain things. > > Thanks, Okay, I opened an account 'upstream', made a comment, and now we will wait if the bug will be closed upstream. ace From pochu at ubuntu.com Thu Apr 17 11:57:31 2008 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Thu, 17 Apr 2008 13:57:31 +0200 Subject: Closing a bug In-Reply-To: <200804170736.08626.lists@suares.an> References: <200804162107.11088.lists@suares.an> <20080417025722.GA23156@murraytwins.com> <200804170736.08626.lists@suares.an> Message-ID: <48073B2B.7030303@ubuntu.com> Ace Suares wrote: > On Wednesday 16 April 2008, Brian Murray wrote: >> On Wed, Apr 16, 2008 at 09:07:11PM -0400, Ace Suares wrote: >>> Hiya >>> >>> https://bugs.launchpad.net/openoffice/+bug/70981 >>> >>> How to deal with this: >>> >>> 1. it's still a bug in feisty,. >>> 2. it's not a bug in gutsy >>> 3. somehow the 'affects' lists 4 items; two of them is fix release, >>> one confirmed, one invalid. >> In this particular bug we are being shown how it affects multiple >> different packages and projects. We have the following: >> >> KDE PIM >> - an upstream project >> OpenOffice >> - another upstream project >> kdelibs (Ubuntu) >> - an Ubuntu package >> openoffice.org (Ubuntu) >> - an Ubuntu package >> >>> What to do to close the bug !? >> The bug is "closed", or in an end state, for almost every thing it >> affects. The only remaining open affects is the upstream OpenOffice >> bug and if the bug really isn't an OpenOffice bug it'd be best if we >> were to get that upstream bug closed too. >> >> This is a really neat question as it illustrates how a bug can affect >> many different things which isn't the case with every bug. I hope my >> answer helps explain things. >> >> Thanks, > > Hi, > > How to close an upstream bug ? Is that a bug in another bug system (i.e. > not Malone/Launchpad) ? I wouldn't close it. It's a bug watch so it will be closed when the upstream bug is closed. Also, all the Ubuntu tasks are closed so that bug is closed 'in Ubuntu'. Leaving the OOo task open won't cause any harm. But for answering the question, it can be closed by changing its status to 'None, the status of the bug is updated manually.', then changing it to invalid. Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From lists at suares.an Thu Apr 17 11:59:47 2008 From: lists at suares.an (Ace Suares) Date: Thu, 17 Apr 2008 07:59:47 -0400 Subject: Closing a bug In-Reply-To: <48073B2B.7030303@ubuntu.com> References: <200804162107.11088.lists@suares.an> <200804170736.08626.lists@suares.an> <48073B2B.7030303@ubuntu.com> Message-ID: <200804170759.47684.lists@suares.an> On Thursday 17 April 2008, Emilio Pozuelo Monfort wrote: > Ace Suares wrote: > > On Wednesday 16 April 2008, Brian Murray wrote: > >> On Wed, Apr 16, 2008 at 09:07:11PM -0400, Ace Suares wrote: > >>> Hiya > >>> > >>> https://bugs.launchpad.net/openoffice/+bug/70981 > >>> > >>> How to deal with this: > >>> > >>> 1. it's still a bug in feisty,. > >>> 2. it's not a bug in gutsy > >>> 3. somehow the 'affects' lists 4 items; two of them is fix release, > >>> one confirmed, one invalid. > >> > >> In this particular bug we are being shown how it affects multiple > >> different packages and projects. We have the following: > >> > >> KDE PIM > >> - an upstream project > >> OpenOffice > >> - another upstream project > >> kdelibs (Ubuntu) > >> - an Ubuntu package > >> openoffice.org (Ubuntu) > >> - an Ubuntu package > >> > >>> What to do to close the bug !? > >> > >> The bug is "closed", or in an end state, for almost every thing it > >> affects. The only remaining open affects is the upstream OpenOffice > >> bug and if the bug really isn't an OpenOffice bug it'd be best if we > >> were to get that upstream bug closed too. > >> > >> This is a really neat question as it illustrates how a bug can > >> affect many different things which isn't the case with every bug. I > >> hope my answer helps explain things. > >> > >> Thanks, > > > > Hi, > > > > How to close an upstream bug ? Is that a bug in another bug system > > (i.e. not Malone/Launchpad) ? > > I wouldn't close it. It's a bug watch so it will be closed when the > upstream bug is closed. > > Also, all the Ubuntu tasks are closed so that bug is closed 'in > Ubuntu'. Leaving the OOo task open won't cause any harm. > > But for answering the question, it can be closed by changing its status > to 'None, the status of the bug is updated manually.', then changing it > to invalid. Thanks! I will try to remember that. In case the OO people don't close their bug. ace > > Emilio From lhademmor at gmail.com Thu Apr 17 13:03:07 2008 From: lhademmor at gmail.com (M.P. Rommedahl) Date: Thu, 17 Apr 2008 15:03:07 +0200 Subject: Closing a bug In-Reply-To: <200804162107.11088.lists@suares.an> References: <200804162107.11088.lists@suares.an> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://getfiregpg.org iD8DBQFIB0qGXVnYsAJEjEYRAgNNAJ9Q4hCceQeSc6TwNkQwO73yPdRUWACgjN8w 3yFg+9f2D9b/mWc5oboat8o= =sLJu -----END PGP SIGNATURE----- 2008/4/17, Ace Suares : > > > 1. it's still a bug in feisty,. > 2. it's not a bug in gutsy > If it's still a bug in feisty then it's not really fixed, is it? I mean... feisty is still a supported release, so shouldn't any fix released be sent to feisty as well..? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgunes at ubuntu.com Thu Apr 17 14:19:48 2008 From: mgunes at ubuntu.com (Murat Gunes) Date: Thu, 17 Apr 2008 17:19:48 +0300 Subject: Closing a bug In-Reply-To: References: <200804162107.11088.lists@suares.an> Message-ID: <1208441988.17412.34.camel@murat-hardy> On Thu, 2008-04-17 at 15:03 +0200, M.P. Rommedahl wrote: > If it's still a bug in feisty then it's not really fixed, is it? I > mean... feisty is still a supported release, so shouldn't any fix > released be sent to feisty as well..? Only if it conforms to https://wiki.ubuntu.com/StableReleaseUpdates . You can nominate a bug for fixing in a specific release with the "Nominate for release" option, and project drivers (bug control team members and developers) can set the "Milestone" field to mark a bug as targeted for fixing in a specific release. Two things I noticed: 1) There seems to be no way to nominate a "Fix Released" bug for fixing in a specific supported release. 2) Shouldn't feisty-updates appear in the "Milestone" dropdown box? And why does edgy-updates still appear? m. From brian at ubuntu.com Thu Apr 17 15:05:00 2008 From: brian at ubuntu.com (Brian Murray) Date: Thu, 17 Apr 2008 08:05:00 -0700 Subject: Closing a bug In-Reply-To: <1208441988.17412.34.camel@murat-hardy> References: <200804162107.11088.lists@suares.an> <1208441988.17412.34.camel@murat-hardy> Message-ID: <20080417150500.GB23156@murraytwins.com> On Thu, Apr 17, 2008 at 05:19:48PM +0300, Murat Gunes wrote: > On Thu, 2008-04-17 at 15:03 +0200, M.P. Rommedahl wrote: > > > If it's still a bug in feisty then it's not really fixed, is it? I > > mean... feisty is still a supported release, so shouldn't any fix > > released be sent to feisty as well..? > > Only if it conforms to https://wiki.ubuntu.com/StableReleaseUpdates . > You can nominate a bug for fixing in a specific release with the > "Nominate for release" option, and project drivers (bug control team > members and developers) can set the "Milestone" field to mark a bug as > targeted for fixing in a specific release. > > Two things I noticed: > > 1) There seems to be no way to nominate a "Fix Released" bug for fixing > in a specific supported release. This has to do with the context in which the bug report was being viewed. The url originally used for the bug report was https://bugs.launchpad.net/openoffice/+bug/70981 which is the OpenOffice context for the bug report. This is also indicated by the yellow line in the affects table. The "Nominate for release" option is context sensitive so by clicking "Nominate for release" when in the OpenOffice context it will be nominated for the OpenOffice project in Launchpad. To nominate this bug for fixing in Ubuntu you'd want to use a url like https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/70981 . I don't know the "right" way to change the context of the bug report other than url hackery though. Does anyone know it? > 2) Shouldn't feisty-updates appear in the "Milestone" dropdown box? And > why does edgy-updates still appear? Edgy is still a supported release, well for a little bit. I'm not sure why feisty-updates doesn't show up and will look into it. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From mgunes at ubuntu.com Thu Apr 17 17:07:57 2008 From: mgunes at ubuntu.com (Murat Gunes) Date: Thu, 17 Apr 2008 20:07:57 +0300 Subject: Closing a bug In-Reply-To: <20080417150500.GB23156@murraytwins.com> References: <200804162107.11088.lists@suares.an> <1208441988.17412.34.camel@murat-hardy> <20080417150500.GB23156@murraytwins.com> Message-ID: <1208452077.27720.37.camel@murat-hardy> On Thu, 2008-04-17 at 08:05 -0700, Brian Murray wrote: > This has to do with the context in which the bug report was being > viewed. The url originally used for the bug report was > https://bugs.launchpad.net/openoffice/+bug/70981 which is the > OpenOffice context for the bug report. This is also indicated by the > yellow line in the affects table. The "Nominate for release" option is > context sensitive so by clicking "Nominate for release" when in the > OpenOffice context it will be nominated for the OpenOffice project in > Launchpad. To nominate this bug for fixing in Ubuntu you'd want to use > a url like https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/70981 > . Thanks; I'm aware of this but for some reason the +nominate page for the Ubuntu task resulted in a generic Launchpad error at the time I checked, and I interpreted that as a "rough edge". It must be either my typo, or a momentary Launchpad malfunction. > I don't know the "right" way to change the context of the bug report > other than url hackery though. Does anyone know it? There seems to be none; worth filing a bug on, probably. Clicking the icons at the left side of the table may be a good way to do it. [1] is close. > Edgy is still a supported release, well for a little bit. Right, I just checked and it has one more week to go. Thanks m. [1] https://bugs.launchpad.net/malone/+bug/141215 From brian at ubuntu.com Mon Apr 21 17:36:32 2008 From: brian at ubuntu.com (Brian Murray) Date: Mon, 21 Apr 2008 10:36:32 -0700 Subject: Bug Focus Message-ID: <20080421173632.GE8395@murraytwins.com> Now is a critical time for us in terms of triaging bug reports and ensuring that Hardy is the best that it can be. We should be keeping an eye out for serious bugs that will prevent people from using Ubuntu. Subsequently, I wanted to point out a few entry points for finding bugs related to Hardy and recent ISO testing. At the iso testing tracker we have a report of bugs, http://iso.qa.ubuntu.com/qatracker/report , found when performing ISO testing of the Hardy Release Candidate. They are currently listed in the "Bugs for current builds" section and will move down to the "Bugs for previous builds" section as daily builds of the final image become available. It is also possible to search for bugs that are tagged iso-testing via Launchpad - https://launchpad.net/ubuntu/+bugs?field.tag=iso-testing . Additionally, it is important that we triage bugs without a package, http://tinyurl.com/4wzwax , as these can be a blind spot for us. We want to keep an eye out for ones specifically related to Hardy and also ones about installation methods e.g. ubiquity, debian-installer and update-manager. We want to move these bugs along the triaging process as quickly as possible by verifying them and gathering the proper debug information. If you need help with a bug or have any questions please raise them in #ubuntu-bugs or on this mailing list. Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From leann.ogasawara at canonical.com Wed Apr 23 00:06:43 2008 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Tue, 22 Apr 2008 17:06:43 -0700 Subject: Hug Day - 25 April 2008 Message-ID: <1208909203.11029.34.camel@emiko> Hi Everyone, Back on the 26th of October 2006 the Edgy Eft 6.10 release was announced. As with any non-LTS release, support is provided for a period of 18 months following the release. That 18 month period is fast approaching for Edgy. The goal of the April 25th Bug Day will be to migrate any existing 2.6.17 kernel bugs from Edgy to the current Hardy Heron 2.6.24 kernel. We want to make sure that as Edgy nears it's end of life that bugs do not get lost or forgotten as we make this transition. The event will be held in #ubuntu-bugs on Freenode. Our goal is to deal with all of the bugs listed at: https://wiki.ubuntu.com/UbuntuBugDay/20080425 However, please refrain from working on the list of bugs until after the final Hardy Heron 8.04 release has been announced. Also, while you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl Feel free to ask bdmurray, ogasawara, pedro, and heno of the QA Team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, Leann Ogasawara From brian at ubuntu.com Mon Apr 21 17:36:32 2008 From: brian at ubuntu.com (Brian Murray) Date: Mon, 21 Apr 2008 10:36:32 -0700 Subject: Bug Focus Message-ID: <20080421173632.GE8395@murraytwins.com> Now is a critical time for us in terms of triaging bug reports and ensuring that Hardy is the best that it can be. We should be keeping an eye out for serious bugs that will prevent people from using Ubuntu. Subsequently, I wanted to point out a few entry points for finding bugs related to Hardy and recent ISO testing. At the iso testing tracker we have a report of bugs, http://iso.qa.ubuntu.com/qatracker/report , found when performing ISO testing of the Hardy Release Candidate. They are currently listed in the "Bugs for current builds" section and will move down to the "Bugs for previous builds" section as daily builds of the final image become available. It is also possible to search for bugs that are tagged iso-testing via Launchpad - https://launchpad.net/ubuntu/+bugs?field.tag=iso-testing . Additionally, it is important that we triage bugs without a package, http://tinyurl.com/4wzwax , as these can be a blind spot for us. We want to keep an eye out for ones specifically related to Hardy and also ones about installation methods e.g. ubiquity, debian-installer and update-manager. We want to move these bugs along the triaging process as quickly as possible by verifying them and gathering the proper debug information. If you need help with a bug or have any questions please raise them in #ubuntu-bugs or on this mailing list. Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From ian.chapman at alft.com Tue Apr 29 13:55:19 2008 From: ian.chapman at alft.com (Ian Chapman) Date: Tue, 29 Apr 2008 09:55:19 -0400 Subject: Hardy upgrade from gutsy failed Message-ID: <200804291355.m3TDtWGu019935@mail2524.carrierzone.com> Hi, I went to launch pad to check out this problem and could not find a report a bug to click. So here is what happened. I updated gutsy then upgraded to Hardy. It failed and every time I reboot I get into the initramfs, best I can tell this is a simplified file utilities for startup and boot stuff. My fix, hit esc in grub and select the previous kernel. Hardy was up after that but I may run into driver problems. Regards Ian. Ian Chapman ALFT Inc 302 Legget Drive Kanata K2K-1Y5 Canada 613-287-0470 (227) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wolfger at gmail.com Wed Apr 30 15:43:14 2008 From: wolfger at gmail.com (Wolfger) Date: Wed, 30 Apr 2008 11:43:14 -0400 Subject: Hardy upgrade from gutsy failed In-Reply-To: <200804291355.m3TDtWGu019935@mail2524.carrierzone.com> References: <200804291355.m3TDtWGu019935@mail2524.carrierzone.com> Message-ID: <3b00b3330804300843w7335ad69q5c55062ed4d27c43@mail.gmail.com> On Tue, Apr 29, 2008 at 9:55 AM, Ian Chapman wrote: > Hi, > > I went to launch pad to check out this problem and could not > find a report a bug to click. > Go to https://launchpad.net/ Click the big red "Bugs" icon at the top On the page this takes you to, there are two buttons on the right hand side of the page: "Take a tour" and "Report a bug". -- Wolfger http://wolfger.wordpress.com/ AOL IM: wolf4coyot Yahoo!Messenger: wolfgersilberbaer -------------- next part -------------- An HTML attachment was scrubbed... URL: