From brian at ubuntu.com Tue Mar 6 22:15:34 2007 From: brian at ubuntu.com (Brian Murray) Date: Tue, 6 Mar 2007 14:15:34 -0800 Subject: UbuntuHugDay: 7 March 2007 Message-ID: <20070306221534.GA4412@murraytwins.com> With the release of Feisty Fawn Herd 5 some of us thought it appropriate to have another Hugs Day tomorrow. I apologize for the short notice but thought it important to have as many as possible before Feisty's final release. So on 7 March 2007, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Bug Day. https://wiki.ubuntu.com/UbuntuBugDay We'll be looking at bugs dealing with Feisty in particular: http://tinyurl.com/2lwn28 We'll also be helping bugs without a home find the packages they belong to: http://tinyurl.com/23wap8 As always we'll be accepting people into Ubuntu QA: https://wiki.ubuntu.com/UbuntuQA And we'll be doing our usual bug triage: https://wiki.ubuntu.com/HelpingWithBugs If you're interested in helping, please stop by. And feel free to ask bdmurray (me), dholbach, and the rest of the team for ways to help out. Hope to see you there! -- 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 hobbsee at kubuntu.org Sun Mar 11 01:39:41 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Sun, 11 Mar 2007 12:39:41 +1100 Subject: Kubuntu Desktop Bugs Week! Message-ID: <45F35DDD.9050004@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Originally from Yuriy Kozlov, but he isnt subscribed to these mailing lists, so got moderated. Hobbsee - ---------- Hello Kubuntu fans, With a bit over a month left until Feisty is released, it's a great time to sort out bugs and polish up the desktop. We are having a week of bug triaging focusing on Kubuntu Desktop applications, inspired by a similar effort by the Ubuntu Desktop Team. Every day the week of Monday March 12 through Friday March 16 we will pick a major application/package in the Kubuntu Desktop and triage (and maybe fix!) as many of its bugs as we can. With enough people helping, we can get all the bugs in major desktop components sorted out and fixed. Everybody can help! More information, tasks, bug lists, and a schedule are here: https://wiki.ubuntu.com/KubuntuTeam/Bugs There is lots of information on how to triage there too, so please read that page and stop by #kubuntu-devel and #ubuntu-bugs on IRC and help out! ~ Yuriy Kozlov - -- kubuntu-devel mailing list kubuntu-devel at lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF813c7/o1b30rzoURAkuwAJoDfy/Jatz/aWeeG1YkzjBi0CWSjgCgz56+ FavJYYlEupEGyvDlU3/3r70= =bRco -----END PGP SIGNATURE----- From yuriy.kozlov at gmail.com Sat Mar 10 00:21:55 2007 From: yuriy.kozlov at gmail.com (Yuriy Kozlov) Date: Fri, 9 Mar 2007 19:21:55 -0500 Subject: Kubuntu Desktop Bugs Week! Message-ID: <714626160703091621h331384ddg5b7827fc38ce11dc@mail.gmail.com> Hello Kubuntu fans, With a bit over a month left until Feisty is released, it's a great time to sort out bugs and polish up the desktop. We are having a week of bug triaging focusing on Kubuntu Desktop applications, inspired by a similar effort by the Ubuntu Desktop Team. Every day the week of Monday March 12 through Friday March 16 we will pick a major application/package in the Kubuntu Desktop and triage (and maybe fix!) as many of its bugs as we can. With enough people helping, we can get all the bugs in major desktop components sorted out and fixed. Everybody can help! More information, tasks, bug lists, and a schedule are here: https://wiki.ubuntu.com/KubuntuTeam/Bugs There is lots of information on how to triage there too, so please read that page and stop by #kubuntu-devel and #ubuntu-bugs on IRC and help out! ~ Yuriy Kozlov From dries at urga.be Tue Mar 13 21:43:38 2007 From: dries at urga.be (Dries Desmet) Date: Tue, 13 Mar 2007 22:43:38 +0100 Subject: hotplugging wacom tablet in feisty bug triage Message-ID: <45F71B0A.3060408@urga.be> Hi, I've only just started triaging bugs and I would find it very rewarding if you can help me with some advice on triaging this bug: https://bugs.launchpad.net/ubuntu/+source/wacom-tools/+bug/38336 I'm hoping to get this triaged to raise the chances the wacom-tools package gets updated for Feisty. I understand the feature freeze is coming any day now, but any tips/tricks/howto's and explanations are welcome. First, this bug is files against a package that is in main. Should it be filed against that particular package or against the distribution "Ubuntu"? It is assigned to Ubuntu Desktop Bugs. Are those the people to address this issue to? This bug has been there long before feisty was around the corner. When it affects the general Ubuntu distribution, would it be taken into the loop when looking for bugs for Feisty? I thought not, that's why I nominated it for Feisty. I see though that it was rejected for Dapper and Edgy, with no particular reason. How could this happen? I also removed the Dapper name from the title of this bug. I even thought of renaming the bug completely to "package update (Debian) needed for wacom-tools". Would this be a good idea? To bring this bug under the attention of the ubuntu package maintainer (since this is solely a repackaging job) Scott James Remnant, can I subscribe him to the bug? Is this bug a real bug? If it is evident that repackaging a Debian package would solve the issue, is there anything special that can be done to triage? (I read on this list about bug tags; do they come into play here?) If repackaging is the only thing needed here, could I try it myself and upload the resulting .deb file to the bug report? Do I send it somewhere else or is this completely not done for packages in main? And I've also wondered: what to do with .deb files not intended for my architecture? Do I update those as well even though I can't test them out? As you can read, a bunch of questions at once. Consider it a starter's hurdle which I'm willing to take, but apart from that, it simply would be really good if hotplugging my wacom tablet would 'just work' in the feisty release. Thank you for your time. Dries. From pwwnow at gmail.com Wed Mar 14 12:32:37 2007 From: pwwnow at gmail.com (Peter Whittaker) Date: Wed, 14 Mar 2007 08:32:37 -0400 Subject: hotplugging wacom tablet in feisty bug triage In-Reply-To: <45F71B0A.3060408@urga.be> References: <45F71B0A.3060408@urga.be> Message-ID: <1173875558.5600.35.camel@EdgeKeep-PC001> On Tue, 2007-03-13 at 22:43 +0100, Dries Desmet wrote: > I've only just started triaging bugs and I would find it very rewarding > if you can help me with some advice on triaging this bug: > https://bugs.launchpad.net/ubuntu/+source/wacom-tools/+bug/38336 > > I'm hoping to get this triaged to raise the chances the wacom-tools > package gets updated for Feisty. I understand the feature freeze is > coming any day now, but any tips/tricks/howto's and explanations are > welcome. It seems to me that the process is working as it should: The package is being worked on upstream, and apparently now works as it should (refer to comment#16). The trouble is that the package was made to work in Debian just recently and very close to the beta freeze [1] [2], so an exception management procedure will be needed. Once the beta is out [1], we revert to Feature Freeze [3], and so can apply its exception process [4]. I'd read through [4] really carefully and make a good case as to which justifications apply. But that case has to be balanced, and you have to be willing to accept that this might be left for Feisty+1 (it'll be automatic for +1 if its in the right state in Debian). When preparing your exception argument, refer also to [5]. If you can justify the exception as meeting Feisty release goals, it'll help. [1] https://wiki.ubuntu.com/FeistyReleaseSchedule [2] https://wiki.ubuntu.com/BetaFreeze [3] https://wiki.ubuntu.com/FeatureFreeze [4] https://wiki.ubuntu.com/FreezeExceptionProcess [5] https://launchpad.net/ubuntu/feisty/+specs Good luck, pww -------------- 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 dries at urga.be Wed Mar 14 23:34:40 2007 From: dries at urga.be (Dries Desmet) Date: Thu, 15 Mar 2007 00:34:40 +0100 Subject: hotplugging wacom tablet in feisty bug triage In-Reply-To: <1173875558.5600.35.camel@EdgeKeep-PC001> References: <45F71B0A.3060408@urga.be> <1173875558.5600.35.camel@EdgeKeep-PC001> Message-ID: <45F88690.1010003@urga.be> Thanks for your pointers Peter. I'll look into it. However: > It seems to me that the process is working as it should: The package is > being worked on upstream, and apparently now works as it should (refer > to comment#16). The trouble is that the package was made to work in > Debian just recently and very close to the beta freeze [1] [2], so an > exception management procedure will be needed. > > > I'm wondering where you got the information that the wacom-tools package in debian only got made recently. The version 0.7.4.1 of wacom-tools got migrated to debian "testing" on 31-5-2006 already as I've found here: http://packages.qa.debian.org/w/wacom-tools.html Debian "stable" seems to be even further behind in version number. Is this what you found as well or am I looking at the wrong documents? I'm asking because first I would like to know whether a sync with debian actually happens with the "testing" branch. Can it be any branch or is "testing" the rule of thumb to ask for inclusion? It would help me to make a case for exception if I have an estimation on what is too far stretched or what is reasonably acceptable. Thanks again. TrioTorus. From pwwnow at gmail.com Thu Mar 15 12:23:28 2007 From: pwwnow at gmail.com (Peter Whittaker) Date: Thu, 15 Mar 2007 08:23:28 -0400 Subject: hotplugging wacom tablet in feisty bug triage In-Reply-To: <45F88690.1010003@urga.be> References: <45F71B0A.3060408@urga.be> <1173875558.5600.35.camel@EdgeKeep-PC001> <45F88690.1010003@urga.be> Message-ID: <1173961408.5547.28.camel@EdgeKeep-PC001> On Thu, 2007-15-03 at 00:34 +0100, Dries Desmet wrote: > I'm wondering where you got the information that wacom-tools > in debian only got made recently. version 0.7.4.1 of wacom-tools > got migrated to debian "testing" on 31-5-2006 already as I've > found here: http://packages.qa.debian.org/w/wacom-tools.html > Debian "stable" seems to be even further behind in version number. You're right, I hadn't looked into this deeply enough (thanks for providing me with a "quest" to help me wake up this morning :->). > I'm asking because first I would like to know whether a sync > with debian actually happens with the "testing" branch. Can it > be any branch or is "testing" the rule of thumb to ask for > inclusion? It would help me to make a case for exception if I > have an estimation on what is too far stretched or what is > reasonably acceptable. My understanding is that Ubuntu imports from sid (unstable) at the beginning of the release cycle [1]. According to the release schedule, this would have been in December 2006 for Feisty [2]. Given the Debian change information [3], I would have thought Feisty would have the most recent version. However, [4] refers to the case where changes have been within Ubuntu that make automatic merging problematic. Thing is, I've looked through the Ubuntu changelogs [5] and through MoM [6], and not been able to find any reason why wacom is behind. The latest people to touch wacom were Matthew Garrett [7] and Scott James Remnant [8], so perhaps they would be able to shed some light or assist with the update. [1] https://wiki.ubuntu.com/MOTU/Packages/Merging [2] https://wiki.ubuntu.com/FeistyReleaseSchedule [3] http://packages.qa.debian.org/w/wacom-tools.html [4] https://wiki.ubuntu.com/MOTU/Merging [5] http://tinyurl.com/2td633 (short version of http://changelogs.ubuntu.com/changelogs/pool/main/w/wacom-tools/wacom-tools_0.7.2-0ubuntu7/changelog ) [6] http://merges.ubuntu.com/ and especially http://merges.ubuntu.com/main.html and http://merges.ubuntu.com/w/ [7] https://launchpad.net/~mjg59 & https://wiki.ubuntu.com/MatthewGarrett [8] https://launchpad.net/~keybuk & https://wiki.ubuntu.com/ScottJamesRemnant -------------- 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 pww at EdgeKeep.com Thu Mar 15 12:17:56 2007 From: pww at EdgeKeep.com (Peter Whittaker) Date: Thu, 15 Mar 2007 08:17:56 -0400 Subject: hotplugging wacom tablet in feisty bug triage In-Reply-To: <45F88690.1010003@urga.be> References: <45F71B0A.3060408@urga.be> <1173875558.5600.35.camel@EdgeKeep-PC001> <45F88690.1010003@urga.be> Message-ID: <1173961077.5547.23.camel@EdgeKeep-PC001> On Thu, 2007-15-03 at 00:34 +0100, Dries Desmet wrote: > I'm wondering where you got the information that the wacom-tools package > in debian only got made recently. The version 0.7.4.1 of wacom-tools got > migrated to debian "testing" on 31-5-2006 already as I've found here: > http://packages.qa.debian.org/w/wacom-tools.html > Debian "stable" seems to be even further behind in version number. Is > this what you found as well or am I looking at the wrong documents? You're right, I hadn't looked into this deeply enough (thanks for providing me with a "quest" to help me wake up this morning :->). > I'm asking because first I would like to know whether a sync with debian > actually happens with the "testing" branch. Can it be any branch or is > "testing" the rule of thumb to ask for inclusion? It would help me to > make a case for exception if I have an estimation on what is too far > stretched or what is reasonably acceptable. My understanding is that Ubuntu imports from sid (unstable) at the beginning of the release cycle [1]. According to the release schedule, this would have been in December 2006 for Feisty [2]. Given the Debian change information [3], I would have thought Feisty would have the most recent version. However, [4] refers to the case where changes have been within Ubuntu that make automatic merging problematic. Thing is, I've looked through the Ubuntu changelogs [5] and through MoM [6], and not been able to find any reason why wacom is behind. The latest people to touch wacom were Matthew Garrett [7] and Scott James Remnant [8], so perhaps they would be able to shed some light or assist with the update. [1] https://wiki.ubuntu.com/MOTU/Packages/Merging [2] https://wiki.ubuntu.com/FeistyReleaseSchedule [3] http://packages.qa.debian.org/w/wacom-tools.html [4] https://wiki.ubuntu.com/MOTU/Merging [5] http://tinyurl.com/2td633 (short version of http://changelogs.ubuntu.com/changelogs/pool/main/w/wacom-tools/wacom-tools_0.7.2-0ubuntu7/changelog ) [6] http://merges.ubuntu.com/ and especially http://merges.ubuntu.com/main.html and http://merges.ubuntu.com/w/ [7] https://launchpad.net/~mjg59 & https://wiki.ubuntu.com/MatthewGarrett [8] https://launchpad.net/~keybuk & https://wiki.ubuntu.com/ScottJamesRemnant From dean at deansas.org Mon Mar 19 00:49:17 2007 From: dean at deansas.org (Dean Sas) Date: Mon, 19 Mar 2007 00:49:17 +0000 Subject: [Fwd: Ubuntu Kernel Team bug triage policies] Message-ID: <45FDDE0D.4040603@deansas.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Just in case some of you people aren't subscribed to -devel-announce here is a new document by the Kernel team that outlines their bug workflow and some tips. Thanks, Dean - -------- Original Message -------- Subject: Ubuntu Kernel Team bug triage policies From: Ben Collins To: Ubuntu Development Announcements Date: Fri, 16 Mar 2007 16:56:55 -0400 This policy is meant to work in conjunction with current bug triaging policies. This is in the hopes that the bug flow to the kernel team will be easier, and allow community to better help the team with the large amount of bug reports we receive. I suspect I'll be making more adjustments to this document, but it's a fair first run. https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks - -- ubuntu-devel-announce mailing list ubuntu-devel-announce at lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/d4NeedO8dcp9nYRAkSvAJ9yJKScT3wtmlqyD8p17YARDzIhewCfRcHN rWgcfnSjlbhJTLPxxwAxzcE= =7bDe -----END PGP SIGNATURE----- From carthik at gmail.com Mon Mar 19 01:06:14 2007 From: carthik at gmail.com (Carthik Sharma) Date: Sun, 18 Mar 2007 21:06:14 -0400 Subject: [Fwd: Ubuntu Kernel Team bug triage policies] In-Reply-To: <45FDDE0D.4040603@deansas.org> References: <45FDDE0D.4040603@deansas.org> Message-ID: <80f75db0703181806q1b4a5cc2x91776ef4e9afa246@mail.gmail.com> Thank you for letting us know :) On 3/18/07, Dean Sas wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi, > > Just in case some of you people aren't subscribed to -devel-announce > here is a new document by the Kernel team that outlines their bug > workflow and some tips. > > Thanks, > Dean > > - -------- Original Message -------- > Subject: Ubuntu Kernel Team bug triage policies > From: Ben Collins > To: Ubuntu Development Announcements > > Date: Fri, 16 Mar 2007 16:56:55 -0400 > > This policy is meant to work in conjunction with current bug triaging > policies. This is in the hopes that the bug flow to the kernel team will > be easier, and allow community to better help the team with the large > amount of bug reports we receive. > > I suspect I'll be making more adjustments to this document, but it's a > fair first run. > > https://wiki.ubuntu.com/KernelTeamBugPolicies There are some inconsistencies in policy when compared to https://wiki.ubuntu.com/DebuggingKernelProblems I added a link to both from the DebuggingProcedures page ( https://wiki.ubuntu.com/DebuggingProcedures ) so now everyone interested in triaging Kernel Bugs should be able to find this info. -- Carthik. Thanks > > > - -- > ubuntu-devel-announce mailing list > ubuntu-devel-announce at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFF/d4NeedO8dcp9nYRAkSvAJ9yJKScT3wtmlqyD8p17YARDzIhewCfRcHN > rWgcfnSjlbhJTLPxxwAxzcE= > =7bDe > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Ph.D. Candidate University of Central Florida Homepage: http://carthik.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From dean at deansas.org Mon Mar 19 01:44:01 2007 From: dean at deansas.org (Dean Sas) Date: Mon, 19 Mar 2007 01:44:01 +0000 Subject: [Fwd: Ubuntu Kernel Team bug triage policies] In-Reply-To: <1174267996.5842.140.camel@gullible> References: <45FDDE0D.4040603@deansas.org> <80f75db0703181806q1b4a5cc2x91776ef4e9afa246@mail.gmail.com> <1174267996.5842.140.camel@gullible> Message-ID: <45FDEAE1.7000203@deansas.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben Collins wrote: > On Sun, 2007-03-18 at 21:06 -0400, Carthik Sharma wrote: > >> There are some inconsistencies in policy when compared to >> https://wiki.ubuntu.com/DebuggingKernelProblems >> I added a link to both from the DebuggingProcedures page >> (https://wiki.ubuntu.com/DebuggingProcedures ) so now everyone >> interested in triaging Kernel Bugs should be able to find this info. > > > I had forgotten about DebuggingKernelProblems. I think that page is > superceded by this new one. > > How can I find all pages that link to DebuggingKernelProblems and change > them to point to KernelTeamBugPolicies? I could then delete > DebuggingKernelProblems (or make that page redirect to > KernelTeamBugPolicies). > The easiest thing to do is just make DebuggingKernelProblems redirect to KernelTeamBugPolicies. You can just do a text search for DebuggingKernelProblems which should pick up the pages you're after. I'll do this now. Dean -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/erheedO8dcp9nYRAjltAJ9KRyt76N4+DbW++sKCvIVGnh0EggCeIJ3O umNvbZzseXhC7OSCHwA8x4M= =0KBr -----END PGP SIGNATURE----- From ben.collins at ubuntu.com Mon Mar 19 01:33:16 2007 From: ben.collins at ubuntu.com (Ben Collins) Date: Sun, 18 Mar 2007 21:33:16 -0400 Subject: [Fwd: Ubuntu Kernel Team bug triage policies] In-Reply-To: <80f75db0703181806q1b4a5cc2x91776ef4e9afa246@mail.gmail.com> References: <45FDDE0D.4040603@deansas.org> <80f75db0703181806q1b4a5cc2x91776ef4e9afa246@mail.gmail.com> Message-ID: <1174267996.5842.140.camel@gullible> On Sun, 2007-03-18 at 21:06 -0400, Carthik Sharma wrote: > > There are some inconsistencies in policy when compared to > https://wiki.ubuntu.com/DebuggingKernelProblems > I added a link to both from the DebuggingProcedures page > (https://wiki.ubuntu.com/DebuggingProcedures ) so now everyone > interested in triaging Kernel Bugs should be able to find this info. I had forgotten about DebuggingKernelProblems. I think that page is superceded by this new one. How can I find all pages that link to DebuggingKernelProblems and change them to point to KernelTeamBugPolicies? I could then delete DebuggingKernelProblems (or make that page redirect to KernelTeamBugPolicies). -- Ubuntu: http://www.ubuntu.com/ Linux1394: http://www.linux1394.org/ From dean at deansas.org Tue Mar 20 00:08:13 2007 From: dean at deansas.org (Dean Sas) Date: Tue, 20 Mar 2007 00:08:13 +0000 Subject: fwd: needs-packaging tag and Candidates Message-ID: <45FF25ED.2020305@deansas.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, FYI: The MOTU team have changed their workflow so that requests for programs to be packaged are now filed on launchpad as a "ubuntu" bug with the "needs-packaging" tag. I've deleted the bit from the Bugs/Responses page which previously mentioned rejecting the bug. Thanks, Dean > To: ubuntu-motu at lists.ubuntu.com > From: Jordan Mantha > Subject: needs-packaging tag and Candidates > Date: Mon, 19 Mar 2007 15:27:53 -0700 > > > MOTUs and MOTU Hopefuls! > > For a long time we've wanted to move away from using the wiki [0] > for new package requests. This is for many reasons, wiki pages like > this can get rather large (we have 450+ requests right now), doesn't > work well with our normal workflow (bugs on Launchpad were we can > comment, prioritize, close, etc.), and get easily overlooked by both > users and developers. > > After talking with Launchpad developers it was determined that they > best approach would be to simply file bugs against Ubuntu and tag > them with needs-packaging . My only concern with this approach was > that users had to know the tag before hand and properly add it. I > thought we would want to have 1 URL that would take them to the bug > filing page in LP *and* have the tag already there. The code for this > [1] has already been included in the Beta Launchpad. For people with > Launchpad Beta access you can test this out by going to [2] or [3]. > > So, do we want to start migrating off of Candidates? I think it'd be > an interesting project for Hopefuls and other people wanting to get > involved with MOTU to work on. Just go through the list and check to > make sure that the app is even distributable and isn't already in > Debian/Ubuntu, then move the contents to a bug report and tag with > needs-packaging . > > -Jordan > > [0] https://wiki.ubuntu.com/MOTU/Packages/Candidates > [1] https://launchpad.net/malone/+bug/79671 > [2] https://launchpad.net/ubuntu/+filebug?field.tags=needs-packaging > [3] https://launchpad.net/ubuntu/+filebug-advanced?field.tags=needs- > packaging -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/yXteedO8dcp9nYRAqURAJ9zTIM40ISgY1Ego3FfSj1Bg0w6igCdEbPb aXUjclXXaLPMj0bX//Y2Fds= =GXp/ -----END PGP SIGNATURE----- From brian at ubuntu.com Tue Mar 20 19:15:35 2007 From: brian at ubuntu.com (Brian Murray) Date: Tue, 20 Mar 2007 12:15:35 -0700 Subject: UbuntuHugDay: 23 March 2007 Message-ID: <20070320191535.GF20618@murraytwins.com> We will be holding the first of what will be weekly Hug Days on Friday, March 23rd. This also follows the Beta release of Feisty Fawn scheduled for the 22nd. So on 23 March 2007, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Bug Day. https://wiki.ubuntu.com/UbuntuBugDay We'll be looking at bugs dealing with Feisty in particular: http://tinyurl.com/2lwn28 We'll also be helping bugs without a home find the packages they belong to: http://tinyurl.com/23wap8 We'd also like to focus on forwarding bugs upstream as we may be able to get fixes in Feisty: http://tinyurl.com/3cfsax As always we'll be accepting people into Ubuntu QA: https://wiki.ubuntu.com/UbuntuQA And we'll be doing our usual bug triage: https://wiki.ubuntu.com/HelpingWithBugs If you're interested in helping, please stop by. And feel free to ask bdmurray, dholbach and the rest of the team for ways to help out. Hope to see you there! -- 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 dean at deansas.org Tue Mar 20 22:10:32 2007 From: dean at deansas.org (Dean Sas) Date: Tue, 20 Mar 2007 22:10:32 +0000 Subject: [Fwd: Launchpad crash bug retracing for the masses!] Message-ID: <46005BD8.1070103@deansas.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Apport has got a fancy new feature - if you tag a bug correctly it will automatically be retraced by the machines in the ubuntu data centre. See below for examples. Also is anyone finding these mails about the rest of the community useful? It strikes me that most of this info will hopefully be repeated in the UWN anyway..Not that I mind doing it. Thanks, Dean - -------- Original Message -------- Date: Tue, 20 Mar 2007 18:56:32 +0100 From: Martin Pitt To: Ubuntu Development Subject: Launchpad crash bug retracing for the masses! Hello fellow developers, Let me lift the curtain for launchpad-crash-digger, a bot that runs in the data center. It grabs apport crash bugs from Launchpad, runs apport-retrace on them, and attaches the symbolic stack traces back to the bug report. See [1] for an example how it looks like (this bug contains *two* responses from the 'Apport retracing service'; this was just for testing). It still needs a little help from triagers at the moment, though. In order to have launchpad-crash-digger see the bugs that need to be processed, they need to have one of these tags attached: need-i386-retrace need-amd64-retrace need-ppc-retrace The retracer will remove these tags while processing a bug. NB that there is no ppc retracer set up yet, I'll do this a bit later when the i386/amd64 ones settled down a bit and proved to be reasonably reliable. We tested them a bit today, and I fixed a couple of nasty bugs which made it break down. This obsoletes the retrace-{i386,amd64} scripts on ronne in the data center. In the future, apport will file crash bugs with the right tag already attached to it, so that the manual tagging will not be necessary any more. This needs a feature in Malone which is not yet there. Enjoy, and make sure to give feedback about any problem or suggestion you have! Martin [1] https://launchpad.net/ubuntu/+source/evolution/+bug/93987 - -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGAFvYeedO8dcp9nYRAu25AJ9gdbsNhe9WxKlaL9rcRoY2AgxEIwCfdr6E AFhdRQar7t/QFsGBV0L2v+c= =294r -----END PGP SIGNATURE----- From freddymartinez9 at ubuntu.com Tue Mar 20 22:29:29 2007 From: freddymartinez9 at ubuntu.com (Freddy Martinez) Date: Tue, 20 Mar 2007 17:29:29 -0500 Subject: [Fwd: Launchpad crash bug retracing for the masses!] In-Reply-To: <46005BD8.1070103@deansas.org> References: <46005BD8.1070103@deansas.org> Message-ID: This email is very useful. The MozillaTeam has been working heavily with apport and having them retraced automatically is a great time saver and lets us look for trends of crashes. On 3/20/07, Dean Sas wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Apport has got a fancy new feature - if you tag a bug correctly it will > automatically be retraced by the machines in the ubuntu data centre. See > below for examples. > > Also is anyone finding these mails about the rest of the community > useful? It strikes me that most of this info will hopefully be repeated > in the UWN anyway..Not that I mind doing it. > > Thanks, > Dean > > - -------- Original Message -------- > > Date: Tue, 20 Mar 2007 18:56:32 +0100 > From: Martin Pitt > To: Ubuntu Development > Subject: Launchpad crash bug retracing for the masses! > > > Hello fellow developers, > > Let me lift the curtain for launchpad-crash-digger, a bot that runs in > the data center. It grabs apport crash bugs from Launchpad, runs > apport-retrace on them, and attaches the symbolic stack traces back to > the bug report. See [1] for an example how it looks like (this bug > contains *two* responses from the 'Apport retracing service'; this was > just for testing). > > It still needs a little help from triagers at the moment, though. In > order to have launchpad-crash-digger see the bugs that need to be > processed, they need to have one of these tags attached: > > need-i386-retrace > need-amd64-retrace > need-ppc-retrace > > The retracer will remove these tags while processing a bug. > > NB that there is no ppc retracer set up yet, I'll do this a bit later > when the i386/amd64 ones settled down a bit and proved to be > reasonably reliable. We tested them a bit today, and I fixed a couple > of nasty bugs which made it break down. > > This obsoletes the retrace-{i386,amd64} scripts on ronne in the data > center. > > In the future, apport will file crash bugs with the right tag already > attached to it, so that the manual tagging will not be necessary any > more. This needs a feature in Malone which is not yet there. > > Enjoy, and make sure to give feedback about any problem or suggestion > you have! > > Martin > > [1] https://launchpad.net/ubuntu/+source/evolution/+bug/93987 > > - -- > Martin Pitt http://www.piware.de > Ubuntu Developer http://www.ubuntu.com > Debian Developer http://www.debian.org > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGAFvYeedO8dcp9nYRAu25AJ9gdbsNhe9WxKlaL9rcRoY2AgxEIwCfdr6E > AFhdRQar7t/QFsGBV0L2v+c= > =294r > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Best, Freddy Martinez Kubuntu. Linux for human beings. www.chi.ubuntu-us.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.holbach at ubuntu.com Wed Mar 21 11:44:38 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Wed, 21 Mar 2007 12:44:38 +0100 Subject: BugSquad Diaries Message-ID: <1174477478.24023.8.camel@bert> Hello everybody, I just started off the BugSquad Diaries at https://wiki.ubuntu.com/BugSquad/Diaries If you * facing a lot of bugs, * are could do with some help filtering out the easy bugs, * lack proper documentation for your team's bug workflow this is your chance. Simply open up a wiki page while you do your daily triaging tasks, mark sections you would like to have better documentation for, with a (*), so somebody can pick it up. This is easy to do, it's easy to read for newcomers, we will get better documentation, we will all get more insight in other team's bug workflow, figure out which steps we can speed up, which infrastructure we need and so on. You don't need to write a new entry every day, just stick to yours and add tasks as you do them. I'd really love to see entries from members of the Kernel, the X, the Mozilla, the Kubuntu team and others. If you need contributors, please keep a diary from today on. :-) Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From daniel.holbach at ubuntu.com Wed Mar 21 17:02:03 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Wed, 21 Mar 2007 18:02:03 +0100 Subject: Universe HUG DAY Message-ID: <1174496523.7349.5.camel@bert> Hello everybody, Friday the 23rd of March will be a Universe Hug Day again! You're all invited to help to fix bugs in Universe and Multiverse. We put quite some work into tagging bugs as * 'bitesize', if they're suited for newcomers, * 'packaging', if the bug is packaging related. Also we want to take care of crasher bugs. Lots of them were filed and lots of them were retraced by Martin's excellent retrace service already, so we'll have an easy job to find duplicates and either forward upstream or grab the fix from upstream. If you pondered joining the MOTUs, this might be the best time. Grab a bug from https://wiki.ubuntu.com/MOTU/TODO and join us in #ubuntu-motu on Friday, 23rd of March. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From dean at deansas.org Wed Mar 21 21:39:23 2007 From: dean at deansas.org (Dean Sas) Date: Wed, 21 Mar 2007 21:39:23 +0000 Subject: [Fwd: Re: http://wiki.ubuntu.com/UniverseCandidates replacement] Message-ID: <4601A60B.1050404@deansas.org> Hi Carrying on from the MOTU packaging request policy email from a few days ago. If you see any of these bugs could you triage them as below? Thanks, Dean -------- Original Message -------- From: Reinhard Tartler To: ubuntu-motu at lists.ubuntu.com , ubuntu-devel at lists.ubuntu.com Subject: Re: http://wiki.ubuntu.com/UniverseCandidates replacement References: <1174497600.7349.10.camel at bert> Daniel Holbach writes: > For a list of current packaging requests, check > https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging One small remark to bug triagers: If you spot request for packages which are already requested for (or evel already in) Debian, please locate the ITP bug on http://debian.org/devel/wnpp and link the malone report to that bug. This has several advantages: - we notice when the package enters Debian and we can subscribe the archive team for syncing the source. - prospective packagers for ubuntu notice that there is already someone on the debian side working on the package. Contacting them might be a good idea to avoid work duplication. - There might be licence discussion about the package on the debian side. Linking those bugs might save time for license research. - ... -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 From seb128 at ubuntu.com Fri Mar 23 10:34:08 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Fri, 23 Mar 2007 11:34:08 +0100 Subject: [easy task] register a straw product on launchpad Message-ID: <1174646049.7769.11.camel@seb128-desktop> Hi, I've just forwarded some of the straw bugs upstream, opening upstream tasks for them requires an associated product though, could somebody create one? You can do it on https://launchpad.net/products/+new , the upstream bug tracker is the GNOME bugzilla That's an easy way to contribute if you are looking for something useful to do ;) Cheers, Sebastien Bacher From seb128 at ubuntu.com Fri Mar 23 11:18:03 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Fri, 23 Mar 2007 12:18:03 +0100 Subject: [easy task] straw browser_cmd key Message-ID: <1174648683.7769.17.camel@seb128-desktop> Hi again, An easy fix if somebody from the MOTU team wants to do a straw update: https://launchpad.net/ubuntu/+source/straw/+bug/38980 "In gconf, the default for /apps/straw/general/browser_cmd is "" this makes straw fail to launch my browser. The default should just be an empty string, this would make straw launch the default browser by default" That has been fixed to the SVN: http://svn.gnome.org/viewcvs/straw/trunk/data/straw.schemas?r1=190&r2=248 There is also a 3 unconfirmed bugs, would be nice to try if they can be confirmed and opened upstream Cheers, Sebastien Bacher From janne.jokitalo at dnainternet.net Fri Mar 23 11:23:38 2007 From: janne.jokitalo at dnainternet.net (Janne Jokitalo) Date: Fri, 23 Mar 2007 13:23:38 +0200 Subject: [easy task] register a straw product on launchpad In-Reply-To: <1174646049.7769.11.camel@seb128-desktop> References: <1174646049.7769.11.camel@seb128-desktop> Message-ID: <4603B8BA.4000303@dnainternet.net> Sebastien Bacher wrote: > That's an easy way to contribute if you are looking for something useful > to do ;) Hi again, just wanted to let you know that the product is created and thanks to BjornT it's marked using GNOME bug tracker now. I hope that's what was wanted, and I understood things correctly. :) Regards, -- Jaska (a.k.a. AstralJava) From seb128 at ubuntu.com Fri Mar 23 13:52:14 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Fri, 23 Mar 2007 14:52:14 +0100 Subject: [easy task] register a straw product on launchpad In-Reply-To: <4603B8BA.4000303@dnainternet.net> References: <1174646049.7769.11.camel@seb128-desktop> <4603B8BA.4000303@dnainternet.net> Message-ID: <1174657934.19980.1.camel@seb128-desktop> Le vendredi 23 mars 2007 à 13:23 +0200, Janne Jokitalo a écrit : > Sebastien Bacher wrote: > > > That's an easy way to contribute if you are looking for something useful > > to do ;) > > Hi again, just wanted to let you know that the product is created and thanks > to BjornT it's marked using GNOME bug tracker now. > > I hope that's what was wanted, and I understood things correctly. :) Excellent, I just opened upstream tasks for the corresponding straw bugs and that worked alright, thank you for the work on that! Cheers, Sebastien Bacher From brian at ubuntu.com Fri Mar 23 23:16:33 2007 From: brian at ubuntu.com (Brian Murray) Date: Fri, 23 Mar 2007 16:16:33 -0700 Subject: Beryl Message-ID: <20070323231633.GA7606@murraytwins.com> I wanted to let everyone know that beryl has been accepted into universe and subsequently we will need to look at the specific package version that the bug is reported on and not to reject every beryl or beryl related bug. 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 seb128 at ubuntu.com Fri Mar 23 23:32:00 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Sat, 24 Mar 2007 00:32:00 +0100 Subject: [easy task] fix music-applet icon Message-ID: <1174692720.7578.44.camel@seb128-desktop> Hi, That's an another easy bug to fix for somebody who wants to contribute: https://launchpad.net/ubuntu/+source/music-applet/+bug/58582 Changing the .server to use an another category could also be something to do There is also a new version request: https://launchpad.net/ubuntu/+source/music-applet/+bug/85903 Might be interesting to consider ;) Cheers, Sebastien Bacher From seb128 at ubuntu.com Fri Mar 23 23:55:20 2007 From: seb128 at ubuntu.com (Sebastien Bacher) Date: Sat, 24 Mar 2007 00:55:20 +0100 Subject: [easy task] use correct icon for zapping menu item Message-ID: <1174694120.7578.53.camel@seb128-desktop> That's an easy thing to change to the desktop: https://launchpad.net/ubuntu/+source/zapping/+bug/53085 There is no upstream product for it (http://sourceforge.net/projects/zapping) on launchpad, another task to work on Cheers, Sebastien Bacher From hobbsee at kubuntu.org Sat Mar 24 00:57:01 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Sat, 24 Mar 2007 11:57:01 +1100 Subject: Beryl In-Reply-To: <20070323231633.GA7606@murraytwins.com> References: <20070323231633.GA7606@murraytwins.com> Message-ID: <4604775D.5020309@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 However, still reject anything without the proper ubuntu version number anywhere - the packages from beryl-project.org are still not supported. Hobbsee Brian Murray wrote: > I wanted to let everyone know that beryl has been accepted into > universe and subsequently we will need to look at the specific package > version that the bug is reported on and not to reject every beryl or > beryl related bug. > > Thanks, > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGBHdd7/o1b30rzoURAqavAJwMBkbjDrFQ7Os4R+dgaVLFpQDFDwCdEHCJ 9vTa0gGBOCgkkUXbXelgPqQ= =XACc -----END PGP SIGNATURE----- From freddymartinez9 at ubuntu.com Sun Mar 25 07:00:32 2007 From: freddymartinez9 at ubuntu.com (Freddy Martinez) Date: Sun, 25 Mar 2007 02:00:32 -0500 Subject: Apport on PPC Message-ID: Hey all, I hope these are the proper mailing lists to use. I am working on looking at apport crashes on PPC and realize we have two types of tags to use. According to this page, https://wiki.ubuntu.com/BugSquad/Tags we should use the need-powerpc-retrace but according to the apport page https://wiki.ubuntu.com/Apport, the correct tag is need-ppc-retrace. However I looked at bugs with both tags and they do not have a retrace for them either way. https://beta.launchpad.net/ubuntu/+source/firefox/+bug/94803 https://beta.launchpad.net/ubuntu/+source/gpixpod/+bug/84510 Is apport development completed enough for these tags to work? Which tag do I use (so I can fix the wiki pages). Thanks. -- Best, Freddy Martinez Kubuntu. Linux for human beings. www.chi.ubuntu-us.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From freddymartinez9 at ubuntu.com Sun Mar 25 07:03:07 2007 From: freddymartinez9 at ubuntu.com (Freddy Martinez) Date: Sun, 25 Mar 2007 02:03:07 -0500 Subject: Apport on PPC In-Reply-To: References: Message-ID: sorry for the additional email, the second link should be https://beta.launchpad.net/ubuntu/+source/gstreamer0.10-ffmpeg/+bug/89442 On 3/25/07, Freddy Martinez wrote: > > Hey all, I hope these are the proper mailing lists to use. I am working on > looking at apport crashes on PPC and realize we have two types of tags to > use. According to this page, https://wiki.ubuntu.com/BugSquad/Tags we > should use the need-powerpc-retrace but according to the apport page > https://wiki.ubuntu.com/Apport, the correct tag is need-ppc-retrace. > However I looked at bugs with both tags and they do not have a retrace for > them either way. > https://beta.launchpad.net/ubuntu/+source/firefox/+bug/94803 > https://beta.launchpad.net/ubuntu/+source/gpixpod/+bug/84510 > > Is apport development completed enough for these tags to work? Which tag > do I use (so I can fix the wiki pages). Thanks. > > -- > Best, > Freddy Martinez > Kubuntu. Linux for human beings. > www.chi.ubuntu-us.org > -- Best, Freddy Martinez Kubuntu. Linux for human beings. www.chi.ubuntu-us.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.holbach at ubuntu.com Thu Mar 29 21:03:57 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 29 Mar 2007 23:03:57 +0200 Subject: HUG DAY! Message-ID: <1175202237.466.5.camel@bert> Hello Ubuntu Lovers! Feisty Fawn Beta is now released and everyone has done a great job. Lots of people work within the Ubuntu BugSquad [1], some of Ubuntu's teams have set up weekly bug goals [2] and everybody is trying to get as many bugs fixed as possible for Feisty. If you ever wanted to get involved, this is the perfect time to get started. We're having a HUG DAY! [1] http://wiki.ubuntu.com/BugSquad [2] https://wiki.ubuntu.com/DesktopTeam/BugState We will try to triage as many bugs as possible, but specifically look into the targets outlined at http://wiki.ubuntu.com/UbuntuBugDay 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 March Friday 30th, 2007 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems. We can't stress it enough: everyone can help. So join us for the Hug Day! Make a difference: join the Bug Day on Friday, March 30th. 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/HelpingWithBugs Have a nice day, Daniel (for the BugSquad) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: