From live761 at msn.com Mon Jun 1 11:04:53 2009 From: live761 at msn.com (Calvin Ball) Date: Mon, 1 Jun 2009 06:04:53 -0500 Subject: No subject Message-ID: Why is it that we have to go through all this command entering stuff everytime I add a program to it, I think this is very silly and needs to be fixed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rincebrain at gmail.com Mon Jun 1 11:07:45 2009 From: rincebrain at gmail.com (Rince) Date: Mon, 1 Jun 2009 07:07:45 -0400 Subject: No subject In-Reply-To: References: Message-ID: <5da0588e0906010407w329ddb09l36b3e395cb82a760@mail.gmail.com> On Mon, Jun 1, 2009 at 7:04 AM, Calvin Ball wrote: > Why is it that we have to go through all this command entering stuff > everytime I add a program to it, I think this is very silly and needs to be > fixed. > I fear you have neglected to provide context for your complaint. More succinctly - what are you talking about? - Rich -- Life is to you a dashing and bold adventure. -------------- next part -------------- An HTML attachment was scrubbed... URL: From macoafi at gmail.com Mon Jun 1 13:43:02 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Mon, 1 Jun 2009 09:43:02 -0400 Subject: No subject In-Reply-To: <5da0588e0906010407w329ddb09l36b3e395cb82a760@mail.gmail.com> References: <5da0588e0906010407w329ddb09l36b3e395cb82a760@mail.gmail.com> Message-ID: <200906010943.02623.macoafi@gmail.com> On Monday 01 June 2009 7:07:45 am Rince wrote: > On Mon, Jun 1, 2009 at 7:04 AM, Calvin Ball wrote: > > > Why is it that we have to go through all this command entering stuff > > everytime I add a program to it, I think this is very silly and needs to be > > fixed. > > > I fear you have neglected to provide context for your complaint. > > More succinctly - what are you talking about? I think he's been ignoring the "Add/Remove" option in his Applications menu and has been using apt-get instead this entire time but has now become sick of it. -- 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: 197 bytes Desc: This is a digitally signed message part. URL: From briancurtis.wx at gmail.com Tue Jun 2 01:44:48 2009 From: briancurtis.wx at gmail.com (Brian Curtis) Date: Mon, 1 Jun 2009 21:44:48 -0400 Subject: Transition-Regression Tag Message-ID: Hi all, Upon discussions with mrooney about potential regressions due to programs (like empathy and banshee) being transitioned to default. There is a new tag, which is also listed in https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that is meant to mark bugs that may need to be addressed so users can make an easy transition from one default to another. An example of such a bug is https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 Discussion? ~Brian Curtis -- Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" From cjk at teamcharliesangels.com Tue Jun 2 02:00:38 2009 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Mon, 1 Jun 2009 20:00:38 -0600 Subject: Transition-Regression Tag In-Reply-To: References: Message-ID: <20090601200038.56d64818@teamcharliesangels.com> On Mon, 1 Jun 2009 21:44:48 -0400 Brian Curtis wrote: > Hi all, > > Upon discussions with mrooney about potential regressions due to > programs (like empathy and banshee) being transitioned to default. > There is a new tag, which is also listed in > https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that > is meant to mark bugs that may need to be addressed so users can make > an easy transition from one default to another. > > An example of such a bug is > https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 > > Discussion? > > ~Brian Curtis > Maybe it is me, but could you explain a little as to what this actually means. I believe transition = "changing", and regression = "worked before but is now broken". How does that apply to the referenced bug, where it does not appear it ever worked? -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From briancurtis.wx at gmail.com Tue Jun 2 02:10:10 2009 From: briancurtis.wx at gmail.com (Brian Curtis) Date: Mon, 1 Jun 2009 22:10:10 -0400 Subject: Transition-Regression Tag In-Reply-To: <20090601200038.56d64818@teamcharliesangels.com> References: <20090601200038.56d64818@teamcharliesangels.com> Message-ID: Charlie, Thanks for your reply. I brought it up here for this reason. I didn't get much reply in the IRC channel as to which wording would be best for this tag. The idea behind the tag was specifically one that marks bugs that mention possible problems users will have in their transition from rhythmbox to banshee. For example, items that rhythmbox has that banshee doesn't that devs can work on putting into banshee if they decide they want it in there. As far as which wording for the tag would be best is really something I'm not great at deciding, and discussion on that is what I was trying to obtain through this e-mail. I hope this answers your question. ~Brian Curtis On Mon, Jun 1, 2009 at 10:00 PM, Charlie Kravetz wrote: > On Mon, 1 Jun 2009 21:44:48 -0400 > Brian Curtis wrote: > >> Hi all, >> >> Upon discussions with mrooney about potential regressions due to >> programs (like empathy and banshee) being transitioned to default. >> There is a new tag, which is also listed in >> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that >> is meant to mark bugs that may need to be addressed so users can make >> an easy transition from one default to another. >> >> An example of such a bug is >> https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 >> >> Discussion? >> >> ~Brian Curtis >> > > Maybe it is me, but could you explain a little as to what this actually > means. I believe transition = "changing", and regression = "worked > before but is now broken". How does that apply to the referenced bug, > where it does not appear it ever worked? > > > -- > Charlie Kravetz > Linux Registered User Number 425914          [http://counter.li.org/] > Never let anyone steal your DREAM.           [http://keepingdreams.com] > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" From cyan.spam at gmail.com Tue Jun 2 03:30:09 2009 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 01 Jun 2009 23:30:09 -0400 Subject: Transition-Regression Tag In-Reply-To: References: <20090601200038.56d64818@teamcharliesangels.com> Message-ID: <4A249CC1.9060207@gmail.com> Indeed "transition" is vague. It's long, but perhaps "default-switch-regression"? David Brian Curtis wrote: > Charlie, > > Thanks for your reply. I brought it up here for this reason. I > didn't get much reply in the IRC channel as to which wording would be > best for this tag. > > The idea behind the tag was specifically one that marks bugs that > mention possible problems users will have in their transition from > rhythmbox to banshee. For example, items that rhythmbox has that > banshee doesn't that devs can work on putting into banshee if they > decide they want it in there. > > As far as which wording for the tag would be best is really something > I'm not great at deciding, and discussion on that is what I was trying > to obtain through this e-mail. > > I hope this answers your question. > > ~Brian Curtis > > On Mon, Jun 1, 2009 at 10:00 PM, Charlie Kravetz > wrote: >> On Mon, 1 Jun 2009 21:44:48 -0400 >> Brian Curtis wrote: >> >>> Hi all, >>> >>> Upon discussions with mrooney about potential regressions due to >>> programs (like empathy and banshee) being transitioned to default. >>> There is a new tag, which is also listed in >>> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that >>> is meant to mark bugs that may need to be addressed so users can make >>> an easy transition from one default to another. >>> >>> An example of such a bug is >>> https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 >>> >>> Discussion? >>> >>> ~Brian Curtis >>> >> Maybe it is me, but could you explain a little as to what this actually >> means. I believe transition = "changing", and regression = "worked >> before but is now broken". How does that apply to the referenced bug, >> where it does not appear it ever worked? >> >> >> -- >> Charlie Kravetz >> Linux Registered User Number 425914 [http://counter.li.org/] >> Never let anyone steal your DREAM. [http://keepingdreams.com] >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> > > > From kwall at kurtwerks.com Tue Jun 2 04:00:57 2009 From: kwall at kurtwerks.com (Kurt Wall) Date: Mon, 01 Jun 2009 21:00:57 -0700 Subject: Transition-Regression Tag In-Reply-To: (from briancurtis.wx@gmail.com on Mon Jun 1 18:44:48 2009) References: Message-ID: <1243915257.8623.2@latte> On 06/01/2009 06:44:48 PM, Brian Curtis wrote: > Hi all, > > Upon discussions with mrooney about potential regressions due to > programs (like empathy and banshee) being transitioned to default. > There is a new tag, which is also listed in > https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that > is meant to mark bugs that may need to be addressed so users can make > an easy transition from one default to another. Hm. Is it actually a regression if things break because the default application changed? Why is it useful to note that this bug is a plain vanilla regression while that bug is associated with changing a default application? Kurt From persia at ubuntu.com Tue Jun 2 04:45:55 2009 From: persia at ubuntu.com (Emmet Hikory) Date: Tue, 02 Jun 2009 13:45:55 +0900 Subject: Transition-Regression Tag In-Reply-To: <1243915257.8623.2@latte> References: <1243915257.8623.2@latte> Message-ID: <4A24AE83.60204@ubuntu.com> Kurt Wall wrote: > On 06/01/2009 06:44:48 PM, Brian Curtis wrote: >> Hi all, >> >> Upon discussions with mrooney about potential regressions due to >> programs (like empathy and banshee) being transitioned to default. >> There is a new tag, which is also listed in >> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that >> is meant to mark bugs that may need to be addressed so users can make >> an easy transition from one default to another. > > Hm. Is it actually a regression if things break because the default > application changed? > > Why is it useful to note that this bug is a plain vanilla regression > while that bug is associated with changing a default application? The trick is that it's not a regression in the application. The bug may even only be a minor issue for the package against which it is filed. However, that bug does represent a regression in the behaviour of the default Ubuntu Desktop. Arguably such bugs could be filed against Ubuntu or against ubuntu-desktop, but they don't really represent bugs in those packages, so much as differences in behaviour related to the change in the default application. A few potential examples: A) There could be a bug that upgrading from Jaunty to Karmic and running the default music player forgets the previous library location and metadata (e.g. ratings). This could be resolved by better documentation and the provision of a migration tool, and may not actually require any changes in Banshee at all. B) There could be a change in the way that the selected application interacts with external peripherals (e.g. a Creative Zen). If this change would make something that previously worked by default not work by default, it's worth prioritising that fix over another bug that might not be so apparent to users who switch to the new application. C) There could be a change to the UI that made some option less discoverable. This probably needs more documentation, might need UI tweaking and may benefit from a release note. The idea is mostly to collect the set of these things for prioritising and documentation. This should significantly reduce the amount of effort spent trying to help users caught by these issues and help ensure a smooth transition. -- Emmet HIKORY From cjk at teamcharliesangels.com Tue Jun 2 13:15:00 2009 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Tue, 2 Jun 2009 07:15:00 -0600 Subject: Fw: Transition-Regression Tag Message-ID: <20090602071500.52bf1f5d@teamcharliesangels.com> Begin forwarded message: Date: Mon, 1 Jun 2009 20:54:35 -0600 From: Charlie Kravetz To: Brian Curtis Subject: Re: Transition-Regression Tag On Mon, 1 Jun 2009 22:10:10 -0400 Brian Curtis wrote: > Charlie, > > Thanks for your reply. I brought it up here for this reason. I > didn't get much reply in the IRC channel as to which wording would be > best for this tag. > > The idea behind the tag was specifically one that marks bugs that > mention possible problems users will have in their transition from > rhythmbox to banshee. For example, items that rhythmbox has that > banshee doesn't that devs can work on putting into banshee if they > decide they want it in there. > > As far as which wording for the tag would be best is really something > I'm not great at deciding, and discussion on that is what I was trying > to obtain through this e-mail. > > I hope this answers your question. > > ~Brian Curtis > > On Mon, Jun 1, 2009 at 10:00 PM, Charlie Kravetz > wrote: > > On Mon, 1 Jun 2009 21:44:48 -0400 > > Brian Curtis wrote: > > > >> Hi all, > >> > >> Upon discussions with mrooney about potential regressions due to > >> programs (like empathy and banshee) being transitioned to default. > >> There is a new tag, which is also listed in > >> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" > >> that is meant to mark bugs that may need to be addressed so users > >> can make an easy transition from one default to another. > >> > >> An example of such a bug is > >> https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 > >> > >> Discussion? > >> > >> ~Brian Curtis > >> > > > > Maybe it is me, but could you explain a little as to what this > > actually means. I believe transition = "changing", and regression = > > "worked before but is now broken". How does that apply to the > > referenced bug, where it does not appear it ever worked? > > > > > > -- > > Charlie Kravetz > > Linux Registered User Number 425914 > >  [http://counter.li.org/] Never let anyone steal your DREAM. > >     [http://keepingdreams.com] > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > I don't think regression is the correct word here. Regression, as I stated, means "used to work". These bugs are more of the "needs to work if possible" variety. I am not sure of the need for a tag here, but it should be more along the lines of "transition-critical" or "transition-serious"; to define the application itself may have a serious bug that needs work before the transition. On the other hand, once the application becomes part of the default apps, the developers will be looking carefully at all the bugs. Maybe the only tag needed is the application name itself, as "transition-critical", to allow them to find the most critical bugs quickly. If the bug isn't really critical, the tag becomes unneeded, since it won't be fixed anyway for a while. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From brian at ubuntu.com Tue Jun 2 17:41:55 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 2 Jun 2009 10:41:55 -0700 Subject: Transition-Regression Tag In-Reply-To: References: Message-ID: <20090602174155.GK16019@murraytwins.com> On Mon, Jun 01, 2009 at 09:44:48PM -0400, Brian Curtis wrote: > Hi all, > > Upon discussions with mrooney about potential regressions due to > programs (like empathy and banshee) being transitioned to default. > There is a new tag, which is also listed in > https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that > is meant to mark bugs that may need to be addressed so users can make > an easy transition from one default to another. > > An example of such a bug is > https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 > > Discussion? It seems to me that this type of a bug, a functional regression caused by changing the default application from one to another, is actually a subset of the regression-potential tag. Subsequently, I think tagging these as 'regression-potential' is the best idea but that a secondary tag, perhaps 'default-application', would be highly beneficial. By having this secondary tag we could then separate the 'default-application' potential regressions from other potential regressions. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrooney at gmail.com Tue Jun 2 18:05:30 2009 From: mrooney at gmail.com (Mike Rooney) Date: Tue, 2 Jun 2009 11:05:30 -0700 Subject: Transition-Regression Tag In-Reply-To: <20090602174155.GK16019@murraytwins.com> References: <20090602174155.GK16019@murraytwins.com> Message-ID: <4f4806ee0906021105n135494bdp9c4d5464b3b8f781@mail.gmail.com> On Tue, Jun 2, 2009 at 10:41 AM, Brian Murray wrote: > On Mon, Jun 01, 2009 at 09:44:48PM -0400, Brian Curtis wrote: >> Hi all, >> >> Upon discussions with mrooney about potential regressions due to >> programs (like empathy and banshee) being transitioned to default. >> There is a new tag, which is also listed in >> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that >> is meant to mark bugs that may need to be addressed so users can make >> an easy transition from one default to another. >> >> An example of such a bug is >> https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 >> >> Discussion? > > It seems to me that this type of a bug, a functional regression caused > by changing the default application from one to another, is actually a > subset of the regression-potential tag.  Subsequently, I think tagging > these as 'regression-potential' is the best idea but that a secondary > tag, perhaps 'default-application', would be highly beneficial.  By > having this secondary tag we could then separate the > 'default-application' potential regressions from other potential > regressions. > This definitely makes some sense. This is already an understand mechanism and any of these bugs that are released could be transitioned to regression-release just like the others. I'd like to talk to some people on the desktop team about integration with their QA process and how this can help them as well as the upstream projects, tracking issues and their importance. It seems like a formal process and tracking of these issues could really help polish such transitions, by fixing the bugs (ideally upstream with their help) and documenting the ones we can't. Do you know who is good to talk to here, perhaps rickspencer3, pitti, or seb? -- Michael Rooney mrooney at ubuntu.com From briancurtis.wx at gmail.com Tue Jun 2 18:32:44 2009 From: briancurtis.wx at gmail.com (Brian Curtis) Date: Tue, 2 Jun 2009 14:32:44 -0400 Subject: Transition-Regression Tag In-Reply-To: <4f4806ee0906021105n135494bdp9c4d5464b3b8f781@mail.gmail.com> References: <20090602174155.GK16019@murraytwins.com> <4f4806ee0906021105n135494bdp9c4d5464b3b8f781@mail.gmail.com> Message-ID: On Tue, Jun 2, 2009 at 2:05 PM, Mike Rooney wrote: > On Tue, Jun 2, 2009 at 10:41 AM, Brian Murray wrote: >> On Mon, Jun 01, 2009 at 09:44:48PM -0400, Brian Curtis wrote: >>> Hi all, >>> >>> Upon discussions with mrooney about potential regressions due to >>> programs (like empathy and banshee) being transitioned to default. >>> There is a new tag, which is also listed in >>> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that >>> is meant to mark bugs that may need to be addressed so users can make >>> an easy transition from one default to another. >>> >>> An example of such a bug is >>> https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 >>> >>> Discussion? >> >> It seems to me that this type of a bug, a functional regression caused >> by changing the default application from one to another, is actually a >> subset of the regression-potential tag.  Subsequently, I think tagging >> these as 'regression-potential' is the best idea but that a secondary >> tag, perhaps 'default-application', would be highly beneficial.  By >> having this secondary tag we could then separate the >> 'default-application' potential regressions from other potential >> regressions. >> > > This definitely makes some sense. This is already an understand > mechanism and any of these bugs that are released could be > transitioned to regression-release just like the others. I'd like to > talk to some people on the desktop team about integration with their > QA process and how this can help them as well as the upstream > projects, tracking issues and their importance. It seems like a formal > process and tracking of these issues could really help polish such > transitions, by fixing the bugs (ideally upstream with their help) and > documenting the ones we can't. Do you know who is good to talk to > here, perhaps rickspencer3, pitti, or seb? > > -- > Michael Rooney > mrooney at ubuntu.com > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > Hi everyone, We have added a "default-application" tag that will be a "child tag" to the regression-potential tag. https://wiki.ubuntu.com/Bugs/Tags#Regression%20specific ~Brian Curtis -- Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" From hggdh2 at ubuntu.com Tue Jun 2 19:02:33 2009 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 02 Jun 2009 14:02:33 -0500 Subject: Transition-Regression Tag In-Reply-To: <20090602174155.GK16019@murraytwins.com> References: <20090602174155.GK16019@murraytwins.com> Message-ID: <1243969353.9837.26.camel@xango2> On Tue, 2009-06-02 at 10:41 -0700, Brian Murray wrote: > It seems to me that this type of a bug, a functional regression caused > by changing the default application from one to another, is actually a > subset of the regression-potential tag. Subsequently, I think tagging > these as 'regression-potential' is the best idea but that a secondary > tag, perhaps 'default-application', would be highly beneficial. By > having this secondary tag we could then separate the > 'default-application' potential regressions from other potential > regressions. I agree, sort of. I agree that we need to group all *possible* regressions under one theoretical umbrella -- and, right now, Brian's proposal is the nearest we can get. But. I would really like to see a hierarchy on tags. Tags are, by definition, ad-hoc in relation to the BTS (i.e., they provide some information that the BTS does not directly support). As such, we can have -- literally -- anything as a tag. On the other hand, some situations arise where we would like to be able to group together some tags, perhaps because they are specific cases of a general concept. The easiest way to get it done would be by forcing a hierarchy on tag naming (on these cases, *not* generically): regression regression-potential regression-default-app regression-required apport apport-i386-retrace apport-amd64-retrace apport-retrace-failed etc, etc. So (given, of course, that LP would allow us) if I want to see all types of regression, I would search for -- say -- "regression*", or "regression". If I just want to see regressions caused by default applications (in the meaning proposed by Brian C), I then would search only for "regression-default-app". And so on. On yet another hand, this would create a lot more of work, *unless* LP is adjusted to support it. Still. one can dream ;-) One thing to be kept in mind is that a BTS is a living entity: it starts in one form (as designed), and then usage imposes other views. For Malone/LP, or any other BTS, to survive useful, adaptations *must* be discussed, analysed, designed, and implemented (of course, the last two only if the adaptation is considered useful). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From mrooney at gmail.com Tue Jun 2 23:10:19 2009 From: mrooney at gmail.com (Mike Rooney) Date: Tue, 2 Jun 2009 16:10:19 -0700 Subject: Transition-Regression Tag In-Reply-To: References: <20090602174155.GK16019@murraytwins.com> <4f4806ee0906021105n135494bdp9c4d5464b3b8f781@mail.gmail.com> Message-ID: <4f4806ee0906021610y3b675fb4r554f6bee79985e08@mail.gmail.com> On Tue, Jun 2, 2009 at 11:32 AM, Brian Curtis wrote: > On Tue, Jun 2, 2009 at 2:05 PM, Mike Rooney wrote: >> On Tue, Jun 2, 2009 at 10:41 AM, Brian Murray wrote: >>> On Mon, Jun 01, 2009 at 09:44:48PM -0400, Brian Curtis wrote: >>>> Hi all, >>>> >>>> Upon discussions with mrooney about potential regressions due to >>>> programs (like empathy and banshee) being transitioned to default. >>>> There is a new tag, which is also listed in >>>> https://wiki.ubuntu.com/Bugs/Tags called "transition-regression" that >>>> is meant to mark bugs that may need to be addressed so users can make >>>> an easy transition from one default to another. >>>> >>>> An example of such a bug is >>>> https://bugs.edge.launchpad.net/ubuntu/+source/banshee/+bug/235529 >>>> >>>> Discussion? >>> >>> It seems to me that this type of a bug, a functional regression caused >>> by changing the default application from one to another, is actually a >>> subset of the regression-potential tag.  Subsequently, I think tagging >>> these as 'regression-potential' is the best idea but that a secondary >>> tag, perhaps 'default-application', would be highly beneficial.  By >>> having this secondary tag we could then separate the >>> 'default-application' potential regressions from other potential >>> regressions. >>> >> >> This definitely makes some sense. This is already an understand >> mechanism and any of these bugs that are released could be >> transitioned to regression-release just like the others. I'd like to >> talk to some people on the desktop team about integration with their >> QA process and how this can help them as well as the upstream >> projects, tracking issues and their importance. It seems like a formal >> process and tracking of these issues could really help polish such >> transitions, by fixing the bugs (ideally upstream with their help) and >> documenting the ones we can't. Do you know who is good to talk to >> here, perhaps rickspencer3, pitti, or seb? >> >> -- >> Michael Rooney >> mrooney at ubuntu.com >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> > > Hi everyone, > > We have added a "default-application" tag that will be a "child tag" > to the regression-potential tag. > https://wiki.ubuntu.com/Bugs/Tags#Regression%20specific > > ~Brian Curtis > I talked with seb in #ubuntu-bugs and he prefers that we use a specific tag for each transition, such as rhythmbox-to-banshee or pidgin-to-empathy. This can make it easier to search by the specific transition, since perhaps a transition could span multiple packages. It was also his opinion that we don't want to track these regressions the same way we do with regression-* since they aren't regressions in the applications and don't represent a blocker in the same way (it seems to me like sometimes they would but I guess we handle that case by case via the importance/nomination of the Ubuntu task). I suppose this might mean that such a tag is generally incompatible with regression-* (unless of course an application we are switching to also has a regression itself that the previous default performs), and the default-application tag isn't necessary? Lots of agile bug work going on here; what does everyone think? I'm glad we are converging on a formal approach to make testers' work more trackable and actionable! -- Michael Rooney mrooney at gmail.com From leann.ogasawara at canonical.com Thu Jun 4 22:37:57 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Thu, 04 Jun 2009 15:37:57 -0700 Subject: Kernel Bug Day - Tues. 9th of June, 2009 Message-ID: <1244155077.22340.39.camel@emiko> Hi All, The Canonical Kernel Team is resuming their monthly kernel bug days [1]. Each kernel team member is responsible for a specific subset of bugs however community involvement is also greatly appreciated. We'd actually like to give a big thank you to Andres Mujica who did an amazing job the previous kernel bug day closing out many of the bugs within the community section. Please keep up the good work! The next scheduled kernel bug day will be held Tues. 09 June, 2009 [2]. The focus of this bug day will be on bugs with a resolved upstream bug watch as well as old incomplete bugs. Please join us Tuesday in the #ubuntu-kernel IRC channel on FreeNode as we tackle this list of bugs. Thanks in advance, Leann [1] https://wiki.ubuntu.com/KernelTeam/BugDay [2] https://wiki.ubuntu.com/KernelTeam/BugDay/20090609 From gtamplin at gci.net Sat Jun 6 18:35:39 2009 From: gtamplin at gci.net (Geoff Tamplin) Date: Sat, 06 Jun 2009 10:35:39 -0800 Subject: Version 7.04 vs Version 9.04 and USB HD access Message-ID: <1244313339.12255.31.camel@Uncle-Fritz> Hello. Being a total Newby to UBUNTU, I am unsure whether this is a Bug in version 9.10, or an intentional programmer-imposed limitation. After installing version 9.04, I was unable to access my external USB hard drive. Accessing information from and through the UBUNTU website and Community, I implemented several suggested solutions, with numerous shutdown-restart cycles, but without success "seeing" or at all accessing the USB hard drive. It recognized USB jump drives of all sorts, and a USB wireless mouse, but does not detect the USB hard drive. A friend gave me a copy of the version 7.04 Feisty Fawn ISO file, so I burned a CD from it, successfully installed version Feisty Fawn, and it the present OS. With the external USB drive powered up and connected to the USB port on my Dell Latitude D400 (2004 to 2005 vintage), I turned on the laptop. When Feisty Fawn completed loading, there was my external USB hard drive on the Desktop. Clearly, one or more of the changes which produced version 9.04 Jaunty Jackalope, impaired the ability of the OS to detect my external USB hard drive. If anyone else running Jaunty Jackalope experiences difficulty accessing external USB hard drives, I strongly suggest reverting to the earlier version 7.04 Feisty Fawn for the SIMPLEST solution. Sincerely, Geoff Tamplin gtamplin at gci.net gtamplin1 at gci.net From macoafi at gmail.com Sat Jun 6 19:22:16 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sat, 6 Jun 2009 15:22:16 -0400 Subject: Version 7.04 vs Version 9.04 and USB HD access In-Reply-To: <1244313339.12255.31.camel@Uncle-Fritz> References: <1244313339.12255.31.camel@Uncle-Fritz> Message-ID: <200906061522.21185.macoafi@gmail.com> On Saturday 06 June 2009 2:35:39 pm Geoff Tamplin wrote: > If anyone else running Jaunty Jackalope experiences difficulty accessing > external USB hard drives, I strongly suggest reverting to the earlier > version 7.04 Feisty Fawn for the SIMPLEST solution. Using that version is a rather bad idea. It no longer receives security updates (and has not for about 8 months). Are you sure there isn't a supported version between 7.04 and 9.04 that'll work, such as 8.04 which is a Long Term Support release? -- 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: 197 bytes Desc: This is a digitally signed message part. URL: From andres.mujica at ubuntu.com Sat Jun 6 19:39:14 2009 From: andres.mujica at ubuntu.com (=?ISO-8859-1?Q?Andr=E9s?= Mauricio Mujica Zalamea) Date: Sat, 06 Jun 2009 14:39:14 -0500 Subject: Monthly BugSquad Meeting - 9th June, 2009 16.00 UTC Message-ID: <1244317154.5470.4.camel@vostro> Hi BugSquatters! According to our last meeting, next one would be this Tuesday 9th June at 16.00 UTC. Everyone is invited to join us and discuss how we can improve our Team and actions!!! The proposed Agenda is at https://wiki.ubuntu.com/BugSquad/Meeting Don't hesitate adding the topics you consider should be there. So don't forget, Tuesday 9th June at 16.00 UTC, #ubuntu-meeting let's find the way to squash those bugs!! See you all there!! -- Andrés Mauricio Mujica Zalamea Ubuntu BugSquad/BugControl -------------- next part -------------- An HTML attachment was scrubbed... URL: From wdturner2 at gmail.com Sat Jun 6 23:15:44 2009 From: wdturner2 at gmail.com (Dan Hoffman) Date: Sat, 6 Jun 2009 19:15:44 -0400 Subject: please remove me from the mailing list Message-ID: <6d83844c0906061615v197f8bby7b0e16672792f6d4@mail.gmail.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: From helysm at gmail.com Sun Jun 7 01:34:01 2009 From: helysm at gmail.com (hely suarez) Date: Sat, 6 Jun 2009 20:34:01 -0500 Subject: please remove me from the mailing list In-Reply-To: <6d83844c0906061615v197f8bby7b0e16672792f6d4@mail.gmail.com> References: <6d83844c0906061615v197f8bby7b0e16672792f6d4@mail.gmail.com> Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From kuolas at gmail.com Sun Jun 7 01:57:38 2009 From: kuolas at gmail.com (Alvaro Kuolas) Date: Sat, 06 Jun 2009 22:57:38 -0300 Subject: please remove me from the mailing list In-Reply-To: References: <6d83844c0906061615v197f8bby7b0e16672792f6d4@mail.gmail.com> Message-ID: <1244339858.6381.5.camel@NapaValley> Please folow this link: https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad Thanks! On Sat, 2009-06-06 at 20:34 -0500, hely suarez wrote: > -------------- 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 simon.noordam at sympatico.ca Sun Jun 7 10:13:11 2009 From: simon.noordam at sympatico.ca (simon) Date: Sun, 07 Jun 2009 06:13:11 -0400 Subject: Re USB Message-ID: <1244369591.4131.5.camel@simon-desktop> When I install 9.04 Jaunty the first time I couldn't get the cdrom to work . This was caused by a bug in brasero. I totally uninstalled all its packages and installed an other CD burner after that the cdrom and usb has worked fine I did not test this for USB hard drive. I assume it might be caused by the same probl;em -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at filmchicago.org Mon Jun 8 16:18:06 2009 From: tim at filmchicago.org (Tim M) Date: Mon, 8 Jun 2009 11:18:06 -0500 Subject: What package to assign translation bug to? Message-ID: <74c293b40906080918y1e6ed4cbraf93c258de8dd6a2@mail.gmail.com> After a little troubleshooting with the reporter of bug #384501, we found that the bug is caused by the reporter's use of the Dutch translation files. The bug affects Totem, but if the reporter switches his language settings to English, the bug goes away. What package should this be assigned to? https://bugs.launchpad.net/ubuntu/+source/totem/+bug/384501 Thanks, -Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at filmchicago.org Mon Jun 8 19:38:10 2009 From: tim at filmchicago.org (Tim M) Date: Mon, 8 Jun 2009 14:38:10 -0500 Subject: Bug #326896 and other duplicates Message-ID: <74c293b40906081238l27dba0c4v17db4b53726c3f26@mail.gmail.com> Hello, I have found several duplicates of 'no sound' alsa-driver/linux bugs in the tracker for HP dvX model laptops (dv4, 5, 7). I have an HP dv7 model laptop myself and have the same issue. Anyways, I marked a couple of bugs as duplicates of #326896 but I also found today an article in the community docs ( https://help.ubuntu.com/community/SoundTroubleshooting?action=show&redirect=DebuggingSoundProblems) stating this as a known issue with HP dvx laptops that has been fixed upstream. I haven't been able to locate the upstream patch, but then again I'm not exactly sure where to look to find it. What should I do with the open bug(s) assuming this is fixed upstream already? Thanks, -Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From leann.ogasawara at canonical.com Mon Jun 8 22:08:15 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Mon, 08 Jun 2009 15:08:15 -0700 Subject: Bug #326896 and other duplicates In-Reply-To: <74c293b40906081238l27dba0c4v17db4b53726c3f26@mail.gmail.com> References: <74c293b40906081238l27dba0c4v17db4b53726c3f26@mail.gmail.com> Message-ID: <1244498895.4177.1.camel@emiko> On Mon, 2009-06-08 at 14:38 -0500, Tim M wrote: > Hello, > > I have found several duplicates of 'no sound' alsa-driver/linux bugs > in the tracker for HP dvX model laptops (dv4, 5, 7). I have an HP dv7 > model laptop myself and have the same issue. Anyways, I marked a > couple of bugs as duplicates of #326896 but I also found today an > article in the community docs > ( https://help.ubuntu.com/community/SoundTroubleshooting?action=show&redirect=DebuggingSoundProblems ) stating this as a known issue with HP dvx laptops that has been fixed upstream. I haven't been able to locate the upstream patch, but then again I'm not exactly sure where to look to find it. > > What should I do with the open bug(s) assuming this is fixed upstream > already? Thanks for the email Tim. I've gone ahead and posted a comment to the bug report to solicit some testing just to verify this is indeed fixed. Thanks, Leann From siretart at tauware.de Mon Jun 8 07:31:46 2009 From: siretart at tauware.de (Reinhard Tartler) Date: Mon, 08 Jun 2009 09:31:46 +0200 Subject: new vlc and mplayer packages uploaded, and call for help Message-ID: <87k53lilc8.fsf@faui44a.informatik.uni-erlangen.de> Hey there, I've uploaded the latest upstream versions of vlc and mplayer to karmic. Both packages have really a huge amount of bugs, where I think that they have been fixed in the latest upstream version. The packages have been backported for jaunty in the motumedia PPA. Espc. mplayer has been left outdated for several ubuntu releases. Additional note for mplayer: the new mplayer package essentially replaces the former package that was derived from the debian-multimedia package with the new debian version of the package. They were so different that it is quite possible that there are some regressions here. >From looking that the buglist, I have the impression that most of the crasher bugs don't have the required example file attached, so that a developer cannot easily reproduce and verify the crash in the latest version, but are still marked as 'triaged'. This makes it hard to browse the list of bugs. What can we do to improve the situation here? Perhaps we can dedicate a hug day for cleaning up the lists? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 From pedro at ubuntu.com Tue Jun 9 20:40:24 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 09 Jun 2009 16:40:24 -0400 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 11 June Message-ID: <1244580024.3432.17.camel@wombat> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* update-manager and update-notifier! * 124 New bugs need a hug. * 106 Incomplete bugs need a status check. * 129 Confirmed bugs need a review. * 14 Bugs with patches that need a review. Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 11 June, 2009. * https://wiki.ubuntu.com/UbuntuBugDay/20090611 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. From pedro at ubuntu.com Tue Jun 16 12:39:37 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 16 Jun 2009 08:39:37 -0400 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 18th June, 2009. Message-ID: <1245155977.4866.3.camel@thylacine> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please*... Empathy!! * 26 New bugs need a hug * 5 Incomplete bugs need a status check * 9 Confirmed bugs need a review * 1 Bug with patch to be checked. * 4 Reports to be send upstream. Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 18th June 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090618 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro [From the BugSquad] From xteejyx at googlemail.com Fri Jun 19 21:41:14 2009 From: xteejyx at googlemail.com (xteejyx at googlemail.com) Date: Fri, 19 Jun 2009 22:41:14 +0100 Subject: Fix Release problem Message-ID: <1245447674.15669.5.camel@teej-laptop.lan> Hi guys, It appears that bug #376145 is Fix Released, but users are still stating that this is a problem. I have checked that they are using the correct up-to-date version, which they are, but I'm stumped, have never encountered this before as a triager. From jmarsden at fastmail.fm Fri Jun 19 21:54:25 2009 From: jmarsden at fastmail.fm (Jonathan Marsden) Date: Fri, 19 Jun 2009 14:54:25 -0700 Subject: Fix Release problem In-Reply-To: <1245447674.15669.5.camel@teej-laptop.lan> References: <1245447674.15669.5.camel@teej-laptop.lan> Message-ID: <4A3C0911.1000604@fastmail.fm> xteejyx at googlemail.com wrote: > It appears that bug #376145 is Fix Released, but users are still stating > that this is a problem. I have checked that they are using the correct > up-to-date version, which they are, but I'm stumped, have never > encountered this before as a triager. Maybe it is only fixed for some configurations, or only on some hardware platforms? (1) Can you personally confirm the original bug (using the unfixed version) on your own hardware? (2) Can you then install the supposedly-fixed version, and try to replicate the bug once again? If installing the updated version fixes the issue for you, then you just verified that the fix in that version is at least a partial solution. If it doesn't fix it for you, then we now have an example machine exhibiting the (new/extended?) issue to work on, in the hands of an experienced user who is familiar with troubleshooting (you!). This is very helpful -- you can go on to post new debug info, try the workaround suggested by a commenter on that bug, etc. etc. Jonathan From leann.ogasawara at canonical.com Sat Jun 20 02:13:34 2009 From: leann.ogasawara at canonical.com (Leann Ogasawara) Date: Fri, 19 Jun 2009 19:13:34 -0700 Subject: Kernel Bug Day - Tues. 23rd of June, 2009 Message-ID: <1245464014.5986.141.camel@emiko> Hi All, I just wanted to give everyone a heads up that the next kernel bug day will be held Tues. the 23rd of June, 2009 [1]. The focus of the bug day will be bugs with an open upstream bug watch. Each kernel team member is responsible for a specific subset of bugs however community involvement is also greatly appreciated. A big thank you again to Andres Mujica who lent a helping hand the previous kernel bug day. So please join us Tuesday in the #ubuntu-kernel IRC channel on FreeNode as we tackle this list of bugs. Thanks in advance, Leann [1] https://wiki.ubuntu.com/KernelTeam/BugDay/20090623 From shahar at shahar-or.co.il Tue Jun 23 18:24:59 2009 From: shahar at shahar-or.co.il (Shahar Or) Date: Tue, 23 Jun 2009 21:24:59 +0300 Subject: New tag for RTL Message-ID: Dear friends, There's a new tag in town and it's name is `rtl`. Whenever a bug which messes with users of the right-to-left languages appears - the `rtl` tag gets attached to it and the formidable RTL developers immediately know what to do! FYI, the relevant right-to-left languages are Arabic, Persian and Hebrew. That's ar, fa and he. So when someone mentions that a text is aligned to the wrong side, words or letters are in reverse or that Evolution freezes when you type "ש3." then please attach the RTL tag. Thanks for reading. Many blessings. From pedro at ubuntu.com Tue Jun 23 20:38:11 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 23 Jun 2009 16:38:11 -0400 Subject: Announcing the Next Ubuntu Hug Day! - Thursday 25 June 2009 Message-ID: <1245789491.3878.7.camel@wombat> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* Banshee! * 29 New Bugs need a hug * 21 Incomplete Bugs need a status check * 19 Confirmed Bugs need a review * 1 Bug with Patch to be checked * 2 Bugs to be forwarded upstream Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 25 June 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090625 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. From tdwebste at gmail.com Wed Jun 24 03:39:30 2009 From: tdwebste at gmail.com (Tim Webster) Date: Wed, 24 Jun 2009 11:39:30 +0800 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> Message-ID: <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> thx, NOOP I am looking for is the https://bugs.launchpad.net/ubuntu field name of package version and debian upstream package version corresponding to bug. Without the package version bug status queries are virtually useless. For example doing a bug status query buy hand through https://bugs.launchpad.net/ubuntu/+bugs I can only select the package version and reported bug reports do not show package version. Without this essential package version information, bug status queries are virtually useless. ---------------------------- I already have this information. All bugs about ubuntu are stored in launchpad[0]. You can access launchpad bugs via API using launchpadlib [1] [0] http://bugs.launchpad.net/ubuntu [1] https://help.launchpad.net/API/launchpadlib And I know how to talk https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=initramfs-tools&orderby=-importance &search=Search &field.status%3Alist=INCOMPLETE_WITH_RESPONSE &field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE &field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED &field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED &field.omit_dupes=on On Wed, Jun 24, 2009 at 10:59 AM, NoOp wrote: > On 06/23/2009 07:49 PM, Tim Webster wrote: >> I am working to integrate apt-listbugs with bugs.launchpad.net >> >> As part of this integration work, I am interested in filtering >> bugs.launchpat.net request by >> ubuntu version and debian upstream version if any. >> >> For example >> Package: openoffice.org >> >> ubuntu >> Version: 1:3.0.1-9ubuntu3 >> >> debian upstream >> Version: 1:3.0.1-9 >> >> >> I am aware of http://qa.ubuntuwire.com/bugs/rcbugs/ >> But I would like to retreive all the required information, >> from bugs.launchpad.net and http://bugs.debian.org >> >> >> Is there additional documentation on the available bugs.launchpad >> fields. Or alternative the source code where I can extract this >> information. >> >> ---------- >> > > Perhaps: > > https://help.launchpad.net/ > https://answers.launchpad.net/launchpad-project/+faqs > https://answers.launchpad.net/launchpad-project/+addquestion/+login > > might help? > > > > > -- > ubuntu-users mailing list > ubuntu-users at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users > From tdwebste at gmail.com Wed Jun 24 03:43:20 2009 From: tdwebste at gmail.com (Tim Webster) Date: Wed, 24 Jun 2009 11:43:20 +0800 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> Message-ID: <72877ab10906232043y30ea22f1k686a7487be321989@mail.gmail.com> In brief I don't see how to retrieve bug reports on a specific package version On Wed, Jun 24, 2009 at 11:39 AM, Tim Webster wrote: > thx, NOOP > > I am looking for is the https://bugs.launchpad.net/ubuntu > field name of package version and debian upstream package version > corresponding to bug. > > Without the package version bug status queries are virtually useless. > > For example doing a bug status query buy hand through > https://bugs.launchpad.net/ubuntu/+bugs > > I can only select the package version I can NOT select the package version > and reported bug reports do not show package version. > > Without this essential package version information, bug status queries > are virtually useless. > > ---------------------------- > > I already have this information. > All bugs about ubuntu are stored in launchpad[0]. You can access > launchpad bugs via API using launchpadlib [1] > > [0] http://bugs.launchpad.net/ubuntu > [1] https://help.launchpad.net/API/launchpadlib > > And I know how to talk > > https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=initramfs-tools&orderby=-importance > &search=Search > &field.status%3Alist=INCOMPLETE_WITH_RESPONSE > &field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE > &field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED > &field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED > &field.omit_dupes=on > > > > On Wed, Jun 24, 2009 at 10:59 AM, NoOp wrote: >> On 06/23/2009 07:49 PM, Tim Webster wrote: >>> I am working to integrate apt-listbugs with bugs.launchpad.net >>> >>> As part of this integration work, I am interested in filtering >>> bugs.launchpat.net request by >>> ubuntu version and debian upstream version if any. >>> >>> For example >>> Package: openoffice.org >>> >>> ubuntu >>> Version: 1:3.0.1-9ubuntu3 >>> >>> debian upstream >>> Version: 1:3.0.1-9 >>> >>> >>> I am aware of http://qa.ubuntuwire.com/bugs/rcbugs/ >>> But I would like to retreive all the required information, >>> from bugs.launchpad.net and http://bugs.debian.org >>> >>> >>> Is there additional documentation on the available bugs.launchpad >>> fields. Or alternative the source code where I can extract this >>> information. >>> >>> ---------- >>> >> >> Perhaps: >> >> https://help.launchpad.net/ >> https://answers.launchpad.net/launchpad-project/+faqs >> https://answers.launchpad.net/launchpad-project/+addquestion/+login >> >> might help? >> >> >> >> >> -- >> ubuntu-users mailing list >> ubuntu-users at lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users >> > From tdwebste at gmail.com Wed Jun 24 08:20:07 2009 From: tdwebste at gmail.com (Tim Webster) Date: Wed, 24 Jun 2009 16:20:07 +0800 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: <873a9qp0l3.fsf@faui44a.informatik.uni-erlangen.de> References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> <72877ab10906232043y30ea22f1k686a7487be321989@mail.gmail.com> <8d41218e0906232241n1c38a33bwfe5a82d01d664c91@mail.gmail.com> <873a9qp0l3.fsf@faui44a.informatik.uni-erlangen.de> Message-ID: <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> On Wed, Jun 24, 2009 at 3:12 PM, Reinhard Tartler wrote: > Jordan Mantha writes: > >> On Tue, Jun 23, 2009 at 8:43 PM, Tim Webster wrote: >>> In brief >>> >>> I don't see how to retrieve bug reports on a specific package version >> >> That's because you can't and why apt-listbugs doesn't seem very viable >> for Ubuntu. Did I read this wrong? It is impossible to query bugs https://bugs.launchpad.net/ubuntu for the bugs on specific package version? > Well, apt-listbugs could at least list bugs that are targeted to a > particular release. That would still be a bit limited, but perhaps that > functionality could give some more momentum to use launchpad's bug > nomination feature. I probably misunderstood the above. However, I need bugs against the specific package version for bug regression reporting / monitoring. Bugs against a specific ubuntu release is not useful at all. For example a netbook installed as hardy will have many package version updates to address bugs and backports. Each ubuntu release starts as experimental, and is alpha or unstable for a time, as bugs are addressed and features integrated the release is suitable for testing. Finally the release is stabilized through continued bug fixes and backports. What does tracking bugs against a particular ubuntu release mean? From sgevatter at ubuntu.cat Wed Jun 24 12:55:56 2009 From: sgevatter at ubuntu.cat (Siegfried-Angel Gevatter Pujals (RainCT)) Date: Wed, 24 Jun 2009 14:55:56 +0200 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> <72877ab10906232043y30ea22f1k686a7487be321989@mail.gmail.com> <8d41218e0906232241n1c38a33bwfe5a82d01d664c91@mail.gmail.com> <873a9qp0l3.fsf@faui44a.informatik.uni-erlangen.de> <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> Message-ID: <357b51820906240555k5febfeeex40837924b730f341@mail.gmail.com> 2009/6/24 Tim Webster : > Did I read this wrong? > It is impossible to query bugs https://bugs.launchpad.net/ubuntu for the bugs > on specific package version? Yes, it is. Ubuntu's bug tracker does not have such information. -- Siegfried-Angel Gevatter Pujals (RainCT) Ubuntu Developer. Debian Contributor. From shahar at shahar-or.co.il Wed Jun 24 13:55:45 2009 From: shahar at shahar-or.co.il (Shahar Or) Date: Wed, 24 Jun 2009 16:55:45 +0300 Subject: New tag for RTL In-Reply-To: References: Message-ID: On Tue, Jun 23, 2009 at 9:24 PM, Shahar Or wrote: > FYI, the relevant right-to-left languages are Arabic, Persian and > Hebrew. That's ar, fa and he. Forgive me, what I've said above is a mistake. All the right-to-left languages are relevant in this case. I think that the most  popular ones are these three and I think that only they have LoCo teams. Many blessings. From tdwebste at gmail.com Wed Jun 24 13:59:33 2009 From: tdwebste at gmail.com (Tim Webster) Date: Wed, 24 Jun 2009 21:59:33 +0800 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: <357b51820906240555k5febfeeex40837924b730f341@mail.gmail.com> References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> <72877ab10906232043y30ea22f1k686a7487be321989@mail.gmail.com> <8d41218e0906232241n1c38a33bwfe5a82d01d664c91@mail.gmail.com> <873a9qp0l3.fsf@faui44a.informatik.uni-erlangen.de> <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> <357b51820906240555k5febfeeex40837924b730f341@mail.gmail.com> Message-ID: <72877ab10906240659x2e652f00g6809f6ffffbd7812@mail.gmail.com> >> It is impossible to query bugs https://bugs.launchpad.net/ubuntu for the bugs >> on specific package version? > > Yes, it is. Ubuntu's bug tracker does not have such information. How do we fix this? 1) Do we setup a http://bugs.debian.org sister for ubuntu http://bugs.ubuntu.org And reactivate reportbug for ubuntu? 2) Or add the required package version information to bugs.launchpad.net? Once the bug tracker has the required package version information. I can go a head and modify apt-listbugs for ubuntu. From brian at ubuntu.com Wed Jun 24 15:36:33 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 24 Jun 2009 08:36:33 -0700 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> <72877ab10906232043y30ea22f1k686a7487be321989@mail.gmail.com> <8d41218e0906232241n1c38a33bwfe5a82d01d664c91@mail.gmail.com> <873a9qp0l3.fsf@faui44a.informatik.uni-erlangen.de> <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> Message-ID: <20090624153633.GD5395@murraytwins.com> On Wed, Jun 24, 2009 at 04:20:07PM +0800, Tim Webster wrote: > On Wed, Jun 24, 2009 at 3:12 PM, Reinhard Tartler wrote: > > Jordan Mantha writes: > > > >> On Tue, Jun 23, 2009 at 8:43 PM, Tim Webster wrote: > >>> In brief > >>> > >>> I don't see how to retrieve bug reports on a specific package version > >> > >> That's because you can't and why apt-listbugs doesn't seem very viable > >> for Ubuntu. > > Did I read this wrong? > It is impossible to query bugs https://bugs.launchpad.net/ubuntu for the bugs > on specific package version? I wouldn't say that it is impossible rather somewhat challenging. You could start off by querying for all the bug reports about a specific package and filter those using the tags 'apport-crash', 'apport-bug' or 'apport-package'. These bugs will have been reported by apport and will subsequently contain 'Package: xyz' information in the bug description. I think with this information you might have a good starting point. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From tdwebste at gmail.com Thu Jun 25 07:24:19 2009 From: tdwebste at gmail.com (Tim Webster) Date: Thu, 25 Jun 2009 15:24:19 +0800 Subject: integrating apt-listbugs with bugs.launchpad.net In-Reply-To: <20090624153633.GD5395@murraytwins.com> References: <72877ab10906231949tc888fe6y6aaf68454dfa1c7@mail.gmail.com> <72877ab10906232039i4cb5e499v103c985d1b3b62cd@mail.gmail.com> <72877ab10906232043y30ea22f1k686a7487be321989@mail.gmail.com> <8d41218e0906232241n1c38a33bwfe5a82d01d664c91@mail.gmail.com> <873a9qp0l3.fsf@faui44a.informatik.uni-erlangen.de> <72877ab10906240120u6e78f821ge252524b00b8ff2f@mail.gmail.com> <20090624153633.GD5395@murraytwins.com> Message-ID: <72877ab10906250024g6148ba8tbe6c0edc8164957f@mail.gmail.com> >> It is impossible to query bugs https://bugs.launchpad.net/ubuntu for the bugs >> on specific package version? > > I wouldn't say that it is impossible rather somewhat challenging.  You What next? Grap the bugs.launchpad code and add package version tags. Where to please and who to submit patches to? I am not keen on performing a lot of unstructured string matching with the modified apt-listbugs for ubuntu. Also package version is required for bug reporting, and bug squashing. I will play with the appot tags, but bugs.launched.net needs to have the package version tracked with the bug reports. I don't see any other way to achieve bug requestion monitoring and safe deployment. From pedro at ubuntu.com Fri Jun 26 13:26:15 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Fri, 26 Jun 2009 09:26:15 -0400 Subject: Announcing the Next Ubuntu Hug Day - Tuesday 30 June 2009 Message-ID: <1246022775.4128.8.camel@thylacine> Hello Ubuntu Triagers!, Next week we're going to have a special Hug day on the Tuesday 30, most of you know that the Ubuntu Desktop Team is considering moving to Empathy as the default IM for Karmic and Triage/Testing is needed, the next Tuesday we're going to be focus on the Telepathy-Butterfly (MSN Support used in Empathy), if you're using MSN and have a few minutes over the weekend please help us to test the application and file bugs about it instructions on how to do it are available on the Hug Day page. So far we have: * 18 New bugs need a hug. * 5 Confirmed bugs need a review. Bookmark it, add it to your calendars, turn over those egg-timers! * Tuesday 30 June 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090630 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs pedro. From scott at open-vote.org Mon Jun 29 17:51:34 2009 From: scott at open-vote.org (Scott Ritchie) Date: Mon, 29 Jun 2009 10:51:34 -0700 Subject: New bug tags from UDS for helping small contributors easily find things they can work on Message-ID: <4A48FF26.2030406@open-vote.org> Hello list, At a UDS community session we discussed the idea of creating bug tags designed to help small contributors find bugs that they can help with. A good example of this is the needs-artwork tag: once it's widely used, all a volunteer artist needs to do is find this link to scour Launchpad for anything that needs art: https://launchpad.net/ubuntu/+bugs?field.tag=needs-artwork I blogged about this here: http://yokozar.org/blog/archives/89 I've added the tags (and quick search links) to the Bug Tags page on the wiki: https://wiki.ubuntu.com/Bugs/Tags However, at the moment, very few bugs are actually using these tags. It would be really great if we could get lots of community help in Karmic integrating extra contributions like this, so please help by tagging some bugs :) Thanks, Scott Ritchie