From dereck at gmail.com Tue Jul 1 06:57:41 2008 From: dereck at gmail.com (Dereck) Date: Tue, 01 Jul 2008 02:57:41 -0400 Subject: Hug Day! Message-ID: <4869D565.8@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fellow Ubuntu Lovers! My name is Dereck Wonnacott, hanging around IRC as Awsoonn. I'm helping the incredible Pedro by organizing this week's HUG DAY! I'm new on the block, so if you have any comments &| ideas please send me an e-mail. Enough about me, lets get rolling. This week's target is *drum roll please* Xorg! * 135 New bugs need a hug * 39 Confirmed bugs just need a review Many bugs appear to be old and the only action needed is to ask the reporter for the status. Xorg Needs You! *finger points* Bookmark it, add it to your calenders, turn over your egg-timers! * Thursday July 3rd * http://wiki.ubuntu.com/UbuntuBugDay/20080703 Can't stress it enough: everyone can help! BLOG IT! Especially those on the Planet! There are people who want to help but don't know how and sit on the sidelines of the blog-o-sphere reading; I need help to get those eyes from blogs to bugs. Let us combine blog-powers to educate, "Bug work is a fun way to get involved!" I think the best effect will be if we coordinate together in our blogs: * Publish about the Hug Day Thursday July 3nd to get everyone excited. * Hug some listed bugs and add yourself to the Hug Day's wiki! Also, the Global Bug Jam [1] is coming up faster and faster, Lets get the energy up and the community excited for it, starting now. This should go really well wrt Mark Shuttleworth's latest blog post about bug management. [2] I think we can splash Mark's ripple into a wave. [1] http://wiki.ubuntu.com/GlobalBugJam [2] http://www.markshuttleworth.com/archives/145 Make a difference: Join the Hug Day on Thursday the 3rd. 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, Dereck Wonnacott (for the BugSquad) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIadVlMbyzSbPQbJgRAvivAJ9CXh3az8c6ycCrr403blYVFlCrBACgp9iF lzaaWnr1qaJ++L4/+2o2zlY= =ExPm -----END PGP SIGNATURE----- From pedro at ubuntu.com Tue Jul 1 18:16:07 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 01 Jul 2008 14:16:07 -0400 Subject: Ubuntu QA Team Meeting - Jul 02 2008 Message-ID: <1214936167.6133.72.camel@thylacine> Hello, The Wednesday 02 of July we're going to have our next Ubuntu QA Team Meeting in #ubuntu-meeting at 1700 UTC, the Agenda for the meeting can be found at: https://wiki.ubuntu.com/QATeam/Meetings Please feel free to add the items you want to discuss during it. Best Regards, pedro. From artistichen at verizon.net Wed Jul 2 18:29:55 2008 From: artistichen at verizon.net (CHAS M NORTON) Date: Wed, 2 Jul 2008 11:29:55 -0700 (PDT) Subject: Files Needed When Posting Install Problems Message-ID: <477660.91614.qm@web84102.mail.mud.yahoo.com> Wednesday July 2, 2008 Where is the location of the files recommended to be uploaded by people reporting install bugs? I don't want to tell someone in another form to just paste a bug in Launchpad without at least putting the installation files there. tnx cmn Charles M. Norton Database Programmer/Systems Integrator LPIC-1 Certified August 2007 From pochu at ubuntu.com Wed Jul 2 19:11:55 2008 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Wed, 02 Jul 2008 21:11:55 +0200 Subject: Files Needed When Posting Install Problems In-Reply-To: <477660.91614.qm@web84102.mail.mud.yahoo.com> References: <477660.91614.qm@web84102.mail.mud.yahoo.com> Message-ID: <486BD2FB.1030304@ubuntu.com> CHAS M NORTON wrote: > Wednesday July 2, 2008 > > Where is the location of the files recommended to be uploaded by people reporting install bugs? I don't want to tell someone in another form to just paste a bug in Launchpad without at least putting the installation files there. > I think /var/log/dpkg.log is what you want. Cheers, Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From brian at ubuntu.com Wed Jul 2 19:46:00 2008 From: brian at ubuntu.com (Brian Murray) Date: Wed, 2 Jul 2008 12:46:00 -0700 Subject: Files Needed When Posting Install Problems In-Reply-To: <486BD2FB.1030304@ubuntu.com> References: <477660.91614.qm@web84102.mail.mud.yahoo.com> <486BD2FB.1030304@ubuntu.com> Message-ID: <20080702194600.GY7382@murraytwins.com> On Wed, Jul 02, 2008 at 09:11:55PM +0200, Emilio Pozuelo Monfort wrote: > CHAS M NORTON wrote: > > Wednesday July 2, 2008 > > > > Where is the location of the files recommended to be uploaded by people reporting install bugs? I don't want to tell someone in another form to just paste a bug in Launchpad without at least putting the installation files there. > > > > I think /var/log/dpkg.log is what you want. It depends on whether or not you are performing a GUI installation via ubiquity or a text installation via debian-installer. If you are using ubiquity then the wiki page regarding debugging ubiquity[0] contains information about the log files that should be included. They are '/var/log/syslog' and '/var/log/partman'. Incidentally, the debugging ubiquity page is part of the debugging series[1] which contains valuable information on reporting bugs for a wide variety of packages. [0] https://wiki.ubuntu.com/DebuggingUbiquity [1] https://wiki.ubuntu.com/DebuggingProcedures -- 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 yuriy-kozlov at kubuntu.org Fri Jul 4 18:59:20 2008 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Fri, 4 Jul 2008 14:59:20 -0400 Subject: Hug Day - 08 July 2008 Message-ID: <714626160807041159u3fd8e5eck95a3c0dfcbb74034@mail.gmail.com> Kubuntu Intrepid will bring major changes with KDE 4.1, fixing a lot of bugs or making them irrelevant. We need help sorting out which bugs can now be closed, which still need to be fixed in Intrepid, and which bugs are really important and need to be fixed in Hardy/KDE3. So, the next hug day, on Tuesday, July 8th, will focus on transitioning old KDE3 bug reports to KDE4. The event will be held in #ubuntu-bugs on Freenode. The list of targeted bugs with instructions is posted at: https://wiki.kubuntu.org/UbuntuBugDay/20080708 Our goal is to deal with all of the bugs on that list. So on 08 July 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Kubuntu Hug Day. https://wiki.kubuntu.org/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.kubuntu.org/UbuntuBugControl If you're interested in helping to make the next release of Kubuntu even better - please stop by. And feel free to ask bdmurray, pedro, yuriy, txwikinger and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, ~ Yuriy From vicedar at gmail.com Sun Jul 6 19:29:06 2008 From: vicedar at gmail.com (Sav vas) Date: Sun, 6 Jul 2008 21:29:06 +0200 Subject: Problematic debian control field names? Message-ID: Hi, I've made up an sqlite database of all the packages in the ubuntu repository. The importing ended up being useful for detecting field typos, something like a debian control field name "janitor" :) I found some typos and problematic debian control fields during that import: I've reported all that I could find, but I wasn't sure about the following: Python-Versions (should it be Python-Version?) Python-Runtime (should it be Python-Version?) X-Original-Maintainer (should it be XSBC-Original-Maintainer?) Original-Maintainer (should it be XSBC-Original-Maintainer?) Thanks in advance for your replies! P.S. if anyone wants the bash/perl script to create the database: http://bazaar.launchpad.net/~medigeek/+junk/packages2sqlite/files You can see the problems if you comment the lines: 76 $tempfield =~ s/(python-version)s/$1/; 77 $tempfield =~ s/(?:origininal|ori?gi?n?i?an?l)-?maintainer:?/original-maintainer/; P.P.S. The field names aka columns in the sqlite database are all lowercase. (Original-Maintainer is original-maintainer) From vicedar at gmail.com Sun Jul 6 19:32:27 2008 From: vicedar at gmail.com (Sav vas) Date: Sun, 6 Jul 2008 21:32:27 +0200 Subject: Problematic debian control field names? In-Reply-To: References: Message-ID: I forgot to attach the full list of the control field names I found -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: debian_control_fields.txt URL: From ellery.nick at gmail.com Mon Jul 7 22:07:52 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Mon, 7 Jul 2008 15:07:52 -0700 Subject: Hug Day - 10 June 2008 Message-ID: <809d37bb0807071507p588f7e2dl26838df729a4cc6@mail.gmail.com> Hello Ubuntu Lovers! The next Hug Day is on July 10th, 2008 and will be focused on Kernel audio bugs. Have a nice day, Nick Ellery (On behalf of the Ubuntu BugSquad) -- Nick Ellery https://launchpad.net/~nick.ellery From ellery.nick at gmail.com Mon Jul 7 22:12:23 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Mon, 7 Jul 2008 15:12:23 -0700 Subject: Hug Day - 10 June 2008 In-Reply-To: <809d37bb0807071507p588f7e2dl26838df729a4cc6@mail.gmail.com> References: <809d37bb0807071507p588f7e2dl26838df729a4cc6@mail.gmail.com> Message-ID: <809d37bb0807071512j2316eff6y3cfedc13445f5754@mail.gmail.com> Apologies everyone! I was in the middle of a draft, and I pressed send by accident instead of save. Please do ignore this. Thanks, and sorry for the inconvenience! Nick On Mon, Jul 7, 2008 at 3:07 PM, Nick Ellery wrote: > Hello Ubuntu Lovers! > > The next Hug Day is on July 10th, 2008 and will be focused on Kernel audio bugs. > > Have a nice day, > Nick Ellery (On behalf of the Ubuntu BugSquad) > > > -- > Nick Ellery > https://launchpad.net/~nick.ellery > -- Nick Ellery From ellery.nick at gmail.com Tue Jul 8 21:39:40 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Tue, 8 Jul 2008 14:39:40 -0700 Subject: Hug Day - July 10, 2008 Message-ID: <809d37bb0807081439g2b64ede2s2632f89b75aa3993@mail.gmail.com> Hello Ubuntu Lovers! For our next Ubuntu Bug Day, on July 10th 2008, we will be focusing on Kernel audio bugs! There are currently 129 bugs reported against the kernel source packages packages, but are assigned to the Ubuntu Audio team. The Hug Day will focus on triaging and confirming the bugs on the list, as well as requesting the bug reporter to test to see if the bug still occurs on Intrepid Alpha 2, which is scheduled to be released on the same day. The list of targeted bugs can be found at: https://wiki.ubuntu.com/UbuntuBugDay/20080710 Our goal is to deal with all of the bugs on that list. So on Thursday, 10 July 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask bdmurray, pedro, ogasawara and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, Nick Ellery On behalf of the Ubuntu BugSquad From jw+debian at jameswestby.net Tue Jul 8 16:40:42 2008 From: jw+debian at jameswestby.net (James Westby) Date: Tue, 08 Jul 2008 17:40:42 +0100 Subject: Problematic debian control field names? In-Reply-To: References: Message-ID: <1215535242.10397.16.camel@flash> On Sun, 2008-07-06 at 21:29 +0200, Sav vas wrote: > Hi, I've made up an sqlite database of all the packages in the ubuntu > repository. > The importing ended up being useful for detecting field typos, > something like a debian control field name "janitor" :) > > I found some typos and problematic debian control fields during that import: > I've reported all that I could find, but I wasn't sure about the following: > You mean you filed bug reports against the packages? Great! > Python-Versions (should it be Python-Version?) > Python-Runtime (should it be Python-Version?) > Not sure about these ones. > X-Original-Maintainer (should it be XSBC-Original-Maintainer?) > Original-Maintainer (should it be XSBC-Original-Maintainer?) > If you are looking at debian/control then you are correct, they should be XSBC-Original-Maintainer Thanks for taking a look at this. James From vicedar at gmail.com Wed Jul 9 18:21:31 2008 From: vicedar at gmail.com (Sav vas) Date: Wed, 9 Jul 2008 20:21:31 +0200 Subject: Problematic debian control field names? In-Reply-To: References: <1215535242.10397.16.camel@flash> <1215561189.12653.7.camel@flash> Message-ID: Reported all except htcheck and htcheck-php Here's the list: http://tinyurl.com/58dgl3 P.S. Woops, I was emailing you privately, sorry. Re-attaching the debdiffs here too :) On Wed, Jul 9, 2008 at 8:04 PM, Sav vas wrote: > I have attached debdiffs to patch this. Let's hope I did them correctly > > Except for these two: > htcheck intrepid-universe > htcheck-php intrepid-universe > (some rule problems) > > On Wed, Jul 9, 2008 at 2:59 AM, Sav vas wrote: >> Here you go, you've just shortened the list :) >> >> python-cddb intrepid-main >> forg intrepid-universe >> htcheck intrepid-universe >> htcheck-php intrepid-universe >> jabber-irc intrepid-universe >> plywood intrepid-universe >> python-smbpasswd intrepid-universe >> python-statgrab intrepid-universe >> python-tcpwrap intrepid-universe >> xcolmix intrepid-universe >> >> >> They all have the X-Original-Maintainer, checked with the latest >> Packages.bz2 from the repositories >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: debdiffs.tar.gz Type: application/x-gzip Size: 1988 bytes Desc: not available URL: From jw+debian at jameswestby.net Wed Jul 9 18:36:30 2008 From: jw+debian at jameswestby.net (James Westby) Date: Wed, 09 Jul 2008 19:36:30 +0100 Subject: Problematic debian control field names? In-Reply-To: References: <1215535242.10397.16.camel@flash> <1215561189.12653.7.camel@flash> Message-ID: <1215628590.12653.13.camel@flash> On Wed, 2008-07-09 at 20:21 +0200, Sav vas wrote: > Reported all except htcheck and htcheck-php > > Here's the list: > http://tinyurl.com/58dgl3 Hi, I've closed these, as the packages do not require the modifications to debian/control to do this. I think these might have occured due to a bug in the build system at some point. I checked a few and they were last modified in edgy, so that could well be the case. I think that rebuilds of them all would correct the fields in the Packages file, but I don't think it's worth the time for these small errors. Thanks, James From vicedar at gmail.com Wed Jul 9 18:35:26 2008 From: vicedar at gmail.com (Sav vas) Date: Wed, 9 Jul 2008 20:35:26 +0200 Subject: Problematic debian control field names? In-Reply-To: <1215628590.12653.13.camel@flash> References: <1215535242.10397.16.camel@flash> <1215561189.12653.7.camel@flash> <1215628590.12653.13.camel@flash> Message-ID: > I think that rebuilds of them all would correct the fields in the > Packages file, but I don't think it's worth the time for these > small errors. True :) From mathiaz at ubuntu.com Fri Jul 11 01:03:47 2008 From: mathiaz at ubuntu.com (Mathias Gug) Date: Thu, 10 Jul 2008 21:03:47 -0400 Subject: Dealing with bugs related to a package that has been renamed Message-ID: <20080711010347.GF7054@mathiaz.mathiaz.net> Hi, I've just uploaded an openldap merge from Debian. This new upload changed the name of the source package from openldap2.3 to openldap. There are a couple of packages related to openldap (openldap2.2, openldap2.1) registered in LP. What is the best way to handle bugs opened against all of the openldap packages ? What I'd like to do is to move all the bugs over to the openldap package. Are there any scripts that can help doing that ? Thanks, -- Mathias Gug Ubuntu Developer http://www.ubuntu.com From hobbsee at ubuntu.com Fri Jul 11 01:33:05 2008 From: hobbsee at ubuntu.com (Sarah Hobbs) Date: Fri, 11 Jul 2008 11:33:05 +1000 Subject: Dealing with bugs related to a package that has been renamed In-Reply-To: <20080711010347.GF7054@mathiaz.mathiaz.net> References: <20080711010347.GF7054@mathiaz.mathiaz.net> Message-ID: <4876B851.7010802@ubuntu.com> Mathias Gug wrote: > Hi, > > I've just uploaded an openldap merge from Debian. This new upload > changed the name of the source package from openldap2.3 to openldap. > There are a couple of packages related to openldap (openldap2.2, > openldap2.1) registered in LP. > > What is the best way to handle bugs opened against all of the openldap > packages ? What I'd like to do is to move all the bugs over to the > openldap package. Are there any scripts that can help doing that ? > > Thanks, > To second this question, is there any way to make launchpad show "this package has been renamed to , please don't file more bugs at the old location" or something? Hobbsee -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: From persia at ubuntu.com Fri Jul 11 01:42:05 2008 From: persia at ubuntu.com (Emmet Hikory) Date: Fri, 11 Jul 2008 10:42:05 +0900 Subject: Dealing with bugs related to a package that has been renamed In-Reply-To: <20080711010347.GF7054@mathiaz.mathiaz.net> References: <20080711010347.GF7054@mathiaz.mathiaz.net> Message-ID: <9bd2f8970807101842g195e5249p74e8cef506d11831@mail.gmail.com> Mathias Gug wrote: > What is the best way to handle bugs opened against all of the openldap > packages ? What I'd like to do is to move all the bugs over to the > openldap package. Are there any scripts that can help doing that ? While there may now be better ways, for the laptop-mode -> laptop-mode-tools transition, we reviewed all the bugs against laptop-mode, and manually reassigned those known to still be valid. The majority were marked "invalid" as the package no longer existed. Of course, we let that go a couple cycles, so it was really old by the time it was triaged: you may not have as many clearly obsolete bugs because you're paying attention. -- Emmet HIKORY From artistichen at verizon.net Fri Jul 11 17:46:06 2008 From: artistichen at verizon.net (CHAS M NORTON) Date: Fri, 11 Jul 2008 10:46:06 -0700 (PDT) Subject: what files should be uploaded Message-ID: <370752.87446.qm@web84103.mail.mud.yahoo.com> Friday July 11, 2008 I have submitted https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/247668 What files should I be attaching with this bug? I would like to help diagnose it. tnx cmn Charles M. Norton Database Programmer/Systems Integrator LPIC-1 Certified August 2007 From siretart at ubuntu.com Fri Jul 11 17:47:31 2008 From: siretart at ubuntu.com (Reinhard Tartler) Date: Fri, 11 Jul 2008 19:47:31 +0200 Subject: Dealing with bugs related to a package that has been renamed In-Reply-To: <4876B851.7010802@ubuntu.com> (Sarah Hobbs's message of "Fri, 11 Jul 2008 11:33:05 +1000") References: <20080711010347.GF7054@mathiaz.mathiaz.net> <4876B851.7010802@ubuntu.com> Message-ID: <87tzew9uto.fsf@faui44a.informatik.uni-erlangen.de> Sarah Hobbs writes: > To second this question, is there any way to make launchpad show "this > package has been renamed to , please don't file more bugs at the > old location" or something? Sounds related to https://bugs.launchpad.net/bugs/46385 -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 From brian at ubuntu.com Sat Jul 12 05:17:15 2008 From: brian at ubuntu.com (Brian Murray) Date: Fri, 11 Jul 2008 22:17:15 -0700 Subject: what files should be uploaded In-Reply-To: <370752.87446.qm@web84103.mail.mud.yahoo.com> References: <370752.87446.qm@web84103.mail.mud.yahoo.com> Message-ID: <20080712051715.GS7382@murraytwins.com> On Fri, Jul 11, 2008 at 10:46:06AM -0700, CHAS M NORTON wrote: > > Friday July 11, 2008 > > I have submitted > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/247668 > > What files should I be attaching with this bug? I would like to help diagnose it. Thanks for asking about this! You'll want to review http://wiki.ubuntu.com/DebuggingSoundProblems which contains a section on "Reporting Sound Bugs". This is actually a part of a series of debugging pages, https://wiki.ubuntu.com/DebuggingProcedures, which contain information for reporting bugs on a variety of packages. Those may be handy in the future. -- 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 jw+debian at jameswestby.net Sat Jul 12 10:30:50 2008 From: jw+debian at jameswestby.net (James Westby) Date: Sat, 12 Jul 2008 11:30:50 +0100 Subject: Help with a bug report Message-ID: <1215858650.12653.57.camel@flash> Hi all, There has been a bug reported against wireshark since sometime in the hardy cycle that has quite a severe impact for some wireshark users. https://bugs.edge.launchpad.net/ubuntu/+source/wireshark/+bug/198884 Basically wireshark hangs when run under gksudo, but not any other sudo tool. There is some code for handling uid != euid, but I can't work out why that would behave differently for gksudo. I'm not comfortable forwarding it ustream at this point, as I don't feel I understand the bug well enough to know that it is an upstream problem. Any inisights would be appreciated. Thanks, James From ellery.nick at gmail.com Sat Jul 12 17:51:47 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Sat, 12 Jul 2008 10:51:47 -0700 Subject: Narrowing down the CC list for Bug Days Message-ID: <809d37bb0807121051i27d5f970v75a052548bf5306d@mail.gmail.com> Hi all, Looking at the draft for Bug Day announcements [1], it appears that there are quite a few mailing lists suggested. I propose that we narrow this list down a bit. For example, nearly everybody subscribed to -motu or -desktop, will also be subscribed to -devel-annouce, and this is probably the same for kubuntu-devel. It seems quite unnecessary to be sending out to so many mailing lists. [1] https://wiki.ubuntu.com/UbuntuBugDay/Draft Looking forward to your thoughts, Nick Ellery From mouz at xs4all.nl Sun Jul 13 08:00:47 2008 From: mouz at xs4all.nl (Carol Meertens) Date: Sun, 13 Jul 2008 10:00:47 +0200 Subject: Help with a bug report (wireshark) In-Reply-To: <1215858650.12653.57.camel@flash> References: <1215858650.12653.57.camel@flash> Message-ID: <20080713080046.GA12044@duper> James Westby wrote: > ... (bug 198884) > I'm not comfortable forwarding it ustream at this point, as I don't > feel I understand the bug well enough to know that it is an upstream > problem. Any inisights would be appreciated. When gksudo was used, and the dumpcap -S -M process is being sent a SIGPIPE (13, broken pipe), dumpcap does not exit. When sudo was used, dumpcap does. Maybe some Gtk person, which I am not, should have a look at it? I also noticed that there have been upstream changes around hidden -Z ('capture_child mode') dumpcap option. This was in Februari 2008. See upstream ChangeLog file. It might be related but also it might not. -- mouz From yuriy-kozlov at kubuntu.org Mon Jul 14 04:48:22 2008 From: yuriy-kozlov at kubuntu.org (Yuriy Kozlov) Date: Mon, 14 Jul 2008 00:48:22 -0400 Subject: Hug Day - 15 July 2008 Message-ID: <714626160807132148g712791eds693004c81c784174@mail.gmail.com> Kubuntu Intrepid will bring major changes with KDE 4.1, fixing a lot of bugs or making them irrelevant. We need help sorting out which bugs can now be closed, which still need to be fixed in Intrepid, and which bugs are really important and need to be fixed in Hardy/KDE3. So continuing from the great work done last week, the next hug day, on Tuesday, July 15th, will focus on transitioning old KDE3 bug reports to KDE4. The event will be held in #ubuntu-bugs on Freenode. The list of targeted bugs with instructions is posted at: https://wiki.kubuntu.org/UbuntuBugDay/20080715 Our goal is to deal with all of the bugs on that list. So on 15 July 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Kubuntu Hug Day. https://wiki.kubuntu.org/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.kubuntu.org/UbuntuBugControl If you're interested in helping to make the next release of Kubuntu even better - please stop by. And feel free to ask bdmurray, pedro, yuriy, txwikinger and the rest of the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, ~ Yuriy From pedro at ubuntu.com Mon Jul 14 10:33:18 2008 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Mon, 14 Jul 2008 11:33:18 +0100 Subject: Ubuntu QA Team Meeting - July 16 2008 Message-ID: <1216031598.6047.24.camel@thylacine> Hello, The Wednesday 16 of July we're going to have our next Ubuntu QA Team Meeting and this time is going to be a Conference Call, if you want to join us please send me an email so i can give you the instructions on how to call in, the agenda for the meeting is going to be available at: https://wiki.ubuntu.com/QATeam/Meetings Please feel free to add the items you want to discuss during it. Have a nice day, pedro. From laserjock at ubuntu.com Mon Jul 14 20:11:41 2008 From: laserjock at ubuntu.com (Jordan Mantha) Date: Mon, 14 Jul 2008 13:11:41 -0700 Subject: new Ubuntu QA team Message-ID: <8d41218e0807141311q4d7d0005wff2e63d0c6560434@mail.gmail.com> I'm pleased to announce that a community-driven Ubuntu QA team has formally been created [0] and is rocking already! I'll keep this short, but the basic team description/purpose is: The Ubuntu QA team is focused on developing tools, policies, and practices for ensuring Ubuntu's quality as a distribution as well as providing general advice, oversight, and leadership of QA activities within the Ubuntu project. [1] We are broadly looking at enhancing the awareness and contribution to QA around Ubuntu as well as helping people interested in serious QA work find a common, collaborative, and open environment. I've put more details on my blog announcement [2] and the team wiki page [1] so please have a quick look over the details. We are looking to have a very diverse team and welcome people to contribute/join. -Jordan Mantha (on behalf of the Ubuntu QA team) [0] https://launchpad.net/~ubuntu-qa [1] https://wiki.ubuntu.com/QATeam/ [2] http://laserjock.wordpress.com/2008/07/14/the-new-and-improved-ubuntu-qa/ From dereck at gmail.com Wed Jul 16 19:41:56 2008 From: dereck at gmail.com (Dereck) Date: Wed, 16 Jul 2008 15:41:56 -0400 Subject: Hug Day!! Message-ID: <487E4F04.2050406@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fellow Ubuntu Lovers! This week's Hugday is for *drum roll please* Expirable Bugs!! * nearly 4000 bugs are set to expire * 150 Bugs are selected for this week's hug Bookmark it, add it to your calenders, turn over your egg-timers! * Thursday July 17th * http://wiki.ubuntu.com/UbuntuBugDay/20080717 Can't stress it enough: everyone can help! BLOG IT! Especially those on the Planet! There are people who want to help but don't know how and sit on the sidelines of the blog-o-sphere reading; I need your help to get those eyes from blogs to bugs. Let us combine blog-powers to educate, "Bug work is a fun way to get involved!" * Publish about the Hug Day Thursday July 17th to get everyone excited. * Hug some bugs and add yourself to the HugDay's wiki for your readers! * Add a line to a post about how many bugs you hugged. Make a difference: Join the Hug Day on Thursday the 17th. 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, ~Dereck (from the BugSquad) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIfk8EMbyzSbPQbJgRAi6FAJ9pmUcT+dmEeDgIT4xdEFzXEwBp0gCfXaOJ BQ1gK3W/wr6PRxINswynHjk= =6mih -----END PGP SIGNATURE----- From niels.egberts at gmail.com Thu Jul 17 15:11:39 2008 From: niels.egberts at gmail.com (Niels Egberts) Date: Thu, 17 Jul 2008 17:11:39 +0200 Subject: about apport retrace Message-ID: Hi, I'm running intrepid and I try to find or file every bug I find. Now I found that system-monitor always crashes, so I did an apport bugreport: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/246700 When someone said he had the same problem, I marked the bug as confirmed. But someone else said "setting back to new waiting for the retrace.". What do I need to do now? Can I do this retrace myself, is this done automatically? I have found on the ubuntu wiki: "*apport-retrace*: Regenerate stack traces of a report. If you supply the -doption, this tool will automatically download available debug symbol packages and use them to generate a symbolic stack trace. The manpage explains the functionality and all available options in detail." However, apport-retrace does not know anything about -d, and it gives me a lot of warnings about packages that are not installed and gets me into gdb, but I dont know what I am doing there. Can someone enlighten me? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jw+debian at jameswestby.net Thu Jul 17 15:18:24 2008 From: jw+debian at jameswestby.net (James Westby) Date: Thu, 17 Jul 2008 16:18:24 +0100 Subject: about apport retrace In-Reply-To: References: Message-ID: <1216307905.8527.65.camel@flash> On Thu, 2008-07-17 at 17:11 +0200, Niels Egberts wrote: > Hi, > > I'm running intrepid and I try to find or file every bug I find. Now I > found that system-monitor always crashes, so I did an apport > bugreport: > https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/246700 > > When someone said he had the same problem, I marked the bug as > confirmed. But someone else said "setting back to new waiting for the > retrace.". What do I need to do now? Can I do this retrace myself, is > this done automatically? The retracers are bots that watch for bug reports and then do the retrace for you. You shouldn't have to do anything. Thanks, James From macoafi at gmail.com Thu Jul 17 15:27:36 2008 From: macoafi at gmail.com (Mackenzie Morgan) Date: Thu, 17 Jul 2008 11:27:36 -0400 Subject: about apport retrace In-Reply-To: References: Message-ID: On Thu, Jul 17, 2008 at 11:11 AM, Niels Egberts wrote: > When someone said he had the same problem, I marked the bug as confirmed. Which is wrong. Confirmed, confusingly, means that the info necessary to fix the bug is there. It sounds like it should mean someone reproduced it, I know. -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com <-my blog of Ubuntu stuff apt-get moo From greg.grossmeier at gmail.com Thu Jul 17 16:12:59 2008 From: greg.grossmeier at gmail.com (Greg Grossmeier) Date: Thu, 17 Jul 2008 09:12:59 -0700 Subject: about apport retrace In-Reply-To: References: Message-ID: <487F6F8B.3000104@gmail.com> Mackenzie Morgan wrote: > On Thu, Jul 17, 2008 at 11:11 AM, Niels Egberts wrote: >> When someone said he had the same problem, I marked the bug as confirmed. > > Which is wrong. Confirmed, confusingly, means that the info necessary > to fix the bug is there. It sounds like it should mean someone > reproduced it, I know. Just to clarify before too many bugs are changed: the above is not correct. See: https://wiki.ubuntu.com/Bugs/Status Quote: "Confirmed: * Someone believes that that the report describes a genuine bug in enough detail that a developer could start working on a fix * Confirmed bugs require confirmation from someone other than the original reporter * This helps ensure that the bug is applicable to Ubuntu in general, and not a problem with the reporter's system, therefore... * Please don't confirm your own bugs!" I believe you are thinking of Triaged, Mackenzie. From that same page, under Triaged: "Use this when you are confident that it should be looked at by a developer and has enough information" Hope that helps clarify everything. Best, Greg From wolfger at gmail.com Thu Jul 17 16:14:38 2008 From: wolfger at gmail.com (Wolfger) Date: Thu, 17 Jul 2008 12:14:38 -0400 Subject: about apport retrace In-Reply-To: References: Message-ID: <3b00b3330807170914yce8071ct24a25d9e6e9a8417@mail.gmail.com> On Thu, Jul 17, 2008 at 11:27 AM, Mackenzie Morgan wrote: > On Thu, Jul 17, 2008 at 11:11 AM, Niels Egberts wrote: >> When someone said he had the same problem, I marked the bug as confirmed. > > Which is wrong. Confirmed, confusingly, means that the info necessary > to fix the bug is there. It sounds like it should mean someone > reproduced it, I know. Well, yes and no... If it's reproduced/reproducible, it's confirmed, but if it's missing info it's incomplete. :-) I see nothing wrong with somebody marking the status as confirmed when the problem is reproduced, if they don't know what information to ask for to make the bug report complete. -- Wolfger http://wolfger.wordpress.com/ My 5 today: #186126 (php5), #96836 (wammu), #77983 (pam), #71937 (kdebase), #185577 (alsa-driver) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day From pochu at ubuntu.com Thu Jul 17 16:14:44 2008 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Thu, 17 Jul 2008 18:14:44 +0200 Subject: about apport retrace In-Reply-To: References: Message-ID: <487F6FF4.1080109@ubuntu.com> Mackenzie Morgan wrote: > On Thu, Jul 17, 2008 at 11:11 AM, Niels Egberts wrote: >> When someone said he had the same problem, I marked the bug as confirmed. > > Which is wrong. Confirmed, confusingly, means that the info necessary > to fix the bug is there. No, that would be triaged. Cheers, Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From wolfger at gmail.com Thu Jul 17 16:16:37 2008 From: wolfger at gmail.com (Wolfger) Date: Thu, 17 Jul 2008 12:16:37 -0400 Subject: about apport retrace In-Reply-To: <487F6F8B.3000104@gmail.com> References: <487F6F8B.3000104@gmail.com> Message-ID: <3b00b3330807170916x4aa7644bte4ed7af9202d9589@mail.gmail.com> On Thu, Jul 17, 2008 at 12:12 PM, Greg Grossmeier wrote: > Mackenzie Morgan wrote: >> Which is wrong. Confirmed, confusingly, means that the info necessary >> to fix the bug is there. It sounds like it should mean someone >> reproduced it, I know. > > Just to clarify before too many bugs are changed: the above is not correct. > > See: https://wiki.ubuntu.com/Bugs/Status > Quote: > "Confirmed: > * Someone believes that that the report describes a genuine bug in > enough detail that a developer could start working on a fix I can read "in enough detail..." to mean what Mackenzie is saying. -- Wolfger http://wolfger.wordpress.com/ My 5 today: #186126 (php5), #96836 (wammu), #77983 (pam), #71937 (kdebase), #185577 (alsa-driver) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day From macoafi at gmail.com Thu Jul 17 16:17:46 2008 From: macoafi at gmail.com (Mackenzie Morgan) Date: Thu, 17 Jul 2008 12:17:46 -0400 Subject: about apport retrace In-Reply-To: <487F6F8B.3000104@gmail.com> References: <487F6F8B.3000104@gmail.com> Message-ID: On Thu, Jul 17, 2008 at 12:12 PM, Greg Grossmeier wrote: > Mackenzie Morgan wrote: >> >> On Thu, Jul 17, 2008 at 11:11 AM, Niels Egberts >> wrote: >>> >>> When someone said he had the same problem, I marked the bug as confirmed. >> >> Which is wrong. Confirmed, confusingly, means that the info necessary >> to fix the bug is there. It sounds like it should mean someone >> reproduced it, I know. > > Just to clarify before too many bugs are changed: the above is not correct. > > See: https://wiki.ubuntu.com/Bugs/Status > Quote: > "Confirmed: > * Someone believes that that the report describes a genuine bug in enough > detail that a developer could start working on a fix > I believe you are thinking of Triaged, Mackenzie. From that same page, > under Triaged: "Use this when you are confident that it should be looked at > by a developer and has enough information" Actually, it's that "enough detail that a developer could start working on a fix" which made me think simply having had one person reproduce it doesn't count. What's the difference between that requirement for Confirmed and the requirement for Triaged? They look like they mean the same thing to me. -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com <-my blog of Ubuntu stuff apt-get moo From greg.grossmeier at gmail.com Thu Jul 17 17:22:59 2008 From: greg.grossmeier at gmail.com (Greg Grossmeier) Date: Thu, 17 Jul 2008 10:22:59 -0700 Subject: about apport retrace In-Reply-To: References: <487F6F8B.3000104@gmail.com> Message-ID: <487F7FF3.1060209@gmail.com> Mackenzie Morgan wrote: > Actually, it's that "enough detail that a developer could start > working on a fix" which made me think simply having had one person > reproduce it doesn't count. What's the difference between that > requirement for Confirmed and the requirement for Triaged? They look > like they mean the same thing to me. > Yes, you are right from the information given. However, that first line under Confirmed will be removed today as the lead QA person doesn't even know how it got in there. So, pretend you never saw it. Confirmed means that it is reproducible. Triaged means a dev can start work on it. Period. Sorry about the confusion. greg From greg.grossmeier at gmail.com Thu Jul 17 17:29:28 2008 From: greg.grossmeier at gmail.com (Greg Grossmeier) Date: Thu, 17 Jul 2008 10:29:28 -0700 Subject: about apport retrace In-Reply-To: References: <487F6F8B.3000104@gmail.com> Message-ID: <487F8178.3090508@gmail.com> More information. From Brian and I's conversation this morning: 13:04 < bdmurray> greg-g: re Confirmed I'm not sure why I wrote that and think it should be changed / removed too 13:04 < greg-g> bdmurray: /me nods 13:05 < bdmurray> I'll fix it later tonight then 13:06 < greg-g> bdmurray: just need to remove that line right? 13:07 < bdmurray> greg-g: well or something like another user has experienced the bug report 13:08 < bdmurray> whether it be a duplicate or a comment from additional user with the problem 13:10 < bdmurray> greg-g: so if you've a brilliant way to word that feel free 13:10 < bdmurray> greg-g: otherwise I'll check it out tonight From niels.egberts at gmail.com Thu Jul 17 17:43:13 2008 From: niels.egberts at gmail.com (Niels Egberts) Date: Thu, 17 Jul 2008 19:43:13 +0200 Subject: about apport retrace In-Reply-To: <487F8178.3090508@gmail.com> References: <487F6F8B.3000104@gmail.com> <487F8178.3090508@gmail.com> Message-ID: Good that there is an agreement on what "confirmed" means. And it seems the most logical way. But back to my bug report, another user has confirmed my bug report, but there is not a retrace (yet). What is the "official" answer on this? New/Confirmed/Needs Information? On Thu, Jul 17, 2008 at 7:29 PM, Greg Grossmeier wrote: > More information. From Brian and I's conversation this morning: > > 13:04 < bdmurray> greg-g: re Confirmed I'm not sure why I wrote that > and think it should be changed / removed too > 13:04 < greg-g> bdmurray: /me nods > 13:05 < bdmurray> I'll fix it later tonight then > 13:06 < greg-g> bdmurray: just need to remove that line right? > 13:07 < bdmurray> greg-g: well or something like another user has > experienced the bug report > 13:08 < bdmurray> whether it be a duplicate or a comment from > additional user with the problem > 13:10 < bdmurray> greg-g: so if you've a brilliant way to word that > feel free > 13:10 < bdmurray> greg-g: otherwise I'll check it out tonight > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at gmail.com Thu Jul 17 18:57:30 2008 From: hggdh2 at gmail.com (HggdH) Date: Thu, 17 Jul 2008 13:57:30 -0500 Subject: about apport retrace In-Reply-To: References: <487F6F8B.3000104@gmail.com> <487F8178.3090508@gmail.com> Message-ID: <1216321050.608.14.camel@localhost> On Thu, 2008-07-17 at 19:43 +0200, Niels Egberts wrote: > Good that there is an agreement on what "confirmed" means. And it > seems the most logical way. > > But back to my bug report, another user has confirmed my bug report, > but there is not a retrace (yet). What is the "official" answer on > this? New/Confirmed/Needs Information? It is, right now, confirmed (and I have set it so. We still need the retrace to set it to triaged (but the maintainers might decide they have enough meanwhile). I will try to find what goes with the retrace facility. Regards, ..hggdh.. -------------- 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 persia at ubuntu.com Thu Jul 17 19:57:30 2008 From: persia at ubuntu.com (Emmet Hikory) Date: Thu, 17 Jul 2008 15:57:30 -0400 Subject: about apport retrace In-Reply-To: <487F7FF3.1060209@gmail.com> References: <487F6F8B.3000104@gmail.com> <487F7FF3.1060209@gmail.com> Message-ID: <9bd2f8970807171257k3c34f147vc59a81248b8399f4@mail.gmail.com> Greg Grossmeier wrote: > Confirmed means that it is reproducible. > Triaged means a dev can start work on it. > Period. When using these definitions, can we extend "Confirmed" to mean that it is not only reproducible, but that the bug report contains sufficient information to allow someone previously unfamiliar with the ug to reproduce it? This is distinct from having a solution, but rather just a sufficient description of the method to reproduce that someone could accurately identify the problem (and so complete triage). -- Emmet HIKORY From greg.grossmeier at gmail.com Thu Jul 17 20:06:16 2008 From: greg.grossmeier at gmail.com (Greg Grossmeier) Date: Thu, 17 Jul 2008 13:06:16 -0700 Subject: about apport retrace In-Reply-To: <9bd2f8970807171257k3c34f147vc59a81248b8399f4@mail.gmail.com> References: <487F6F8B.3000104@gmail.com> <487F7FF3.1060209@gmail.com> <9bd2f8970807171257k3c34f147vc59a81248b8399f4@mail.gmail.com> Message-ID: <487FA638.3000104@gmail.com> Emmet Hikory wrote: > When using these definitions, can we extend "Confirmed" to mean > that it is not only reproducible, but that the bug report contains > sufficient information to allow someone previously unfamiliar with the > ug to reproduce it? This is distinct from having a solution, but > rather just a sufficient description of the method to reproduce that > someone could accurately identify the problem (and so complete > triage). +1 I like the idea of adding a TEST CASE section to confirmed bugs (for bugs which aren't obvious, of course). From siretart at ubuntu.com Thu Jul 17 10:13:54 2008 From: siretart at ubuntu.com (Reinhard Tartler) Date: Thu, 17 Jul 2008 12:13:54 +0200 Subject: Narrowing down the CC list for Bug Days In-Reply-To: <809d37bb0807121051i27d5f970v75a052548bf5306d@mail.gmail.com> (Nick Ellery's message of "Sat, 12 Jul 2008 10:51:47 -0700") References: <809d37bb0807121051i27d5f970v75a052548bf5306d@mail.gmail.com> Message-ID: <87mykgrf6l.fsf@faui44a.informatik.uni-erlangen.de> "Nick Ellery" writes: > Looking at the draft for Bug Day announcements [1], it appears that > there are quite a few mailing lists suggested. I propose that we > narrow this list down a bit. For example, nearly everybody subscribed > to -motu or -desktop, will also be subscribed to -devel-annouce, and > this is probably the same for kubuntu-devel. It seems quite > unnecessary to be sending out to so many mailing lists. Any news on this? Does nobody object? If no, I'd suggest the following lists to be dropped: * ubuntu-devel * ubuntu-motu * ubuntu-desktop -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 From hobbsee at ubuntu.com Fri Jul 18 11:48:10 2008 From: hobbsee at ubuntu.com (Sarah Hobbs) Date: Fri, 18 Jul 2008 21:48:10 +1000 Subject: Narrowing down the CC list for Bug Days In-Reply-To: <87mykgrf6l.fsf@faui44a.informatik.uni-erlangen.de> References: <809d37bb0807121051i27d5f970v75a052548bf5306d@mail.gmail.com> <87mykgrf6l.fsf@faui44a.informatik.uni-erlangen.de> Message-ID: <488082FA.1080808@ubuntu.com> Reinhard Tartler wrote: > Any news on this? Does nobody object? If no, I'd suggest the following > lists to be dropped: I agree with this, but have already blocked all of the Hug Day mails, as I was getting far too many copies of it. Hobbsee -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: From sistpoty at ubuntu.com Fri Jul 18 18:58:29 2008 From: sistpoty at ubuntu.com (Stefan Potyra) Date: Fri, 18 Jul 2008 20:58:29 +0200 Subject: Hug Day!! In-Reply-To: <487E4F04.2050406@gmail.com> References: <487E4F04.2050406@gmail.com> Message-ID: <200807182058.31112.sistpoty@ubuntu.com> Hi Dereck, On Wednesday 16 July 2008 21:41:56 Dereck wrote: [..] > This week's Hugday is for *drum roll please* Expirable Bugs!! [..] as I've tried to contact bugsquad with my pet peeve before [1] but didn't get a response, here's another try. Can you eventually avoid sending hug day announces to ubuntu-motu at lists.ubuntu.com? I assume that most people who are subscribed to the motu list are also subscribed to ubuntu-devel-announce, and hence just recieve this mail more than once. Thanks, Stefan. P.S.: please CC me if replying to ubuntu-bugsquad, as I'm not subscribed. [1]: From dereck at gmail.com Fri Jul 18 20:12:12 2008 From: dereck at gmail.com (Dereck) Date: Fri, 18 Jul 2008 16:12:12 -0400 Subject: Hug Day Announcments In-Reply-To: <200807182058.31112.sistpoty@ubuntu.com> References: <487E4F04.2050406@gmail.com> <200807182058.31112.sistpoty@ubuntu.com> Message-ID: <4880F91C.8040501@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefan Potyra wrote: > Hi Dereck, > > On Wednesday 16 July 2008 21:41:56 Dereck wrote: > [..] >> This week's Hugday is for *drum roll please* Expirable Bugs!! > [..] > > as I've tried to contact bugsquad with my pet peeve before [1] but didn't get > a response, here's another try. Can you eventually avoid sending hug day > announces to ubuntu-motu at lists.ubuntu.com? I assume that most people who are > subscribed to the motu list are also subscribed to ubuntu-devel-announce, and > hence just recieve this mail more than once. > > Thanks, > Stefan. > > P.S.: please CC me if replying to ubuntu-bugsquad, as I'm not subscribed. > > [1]: > Stefan, I have to say that makes sense indeed. If Pedro agrees, I will discontinue sending to ubuntu-motu at . ~Dereck -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIgPkcMbyzSbPQbJgRAlI+AKDK3727cvyauI1/5iBhPcQNP9RWUwCgsHoh 1t2bg5Wfp8M7IPwBR1O6az0= =S/G9 -----END PGP SIGNATURE----- From nick.ellery at ubuntu.com Fri Jul 18 23:44:16 2008 From: nick.ellery at ubuntu.com (Nick Ellery) Date: Fri, 18 Jul 2008 16:44:16 -0700 Subject: Ubiquity Bug Day? Message-ID: <809d37bb0807181644y40823265j9a4467a77a2f1dd4@mail.gmail.com> Hi all, What are your thoughts on having a bug day focusing on Ubiquity? I understand that one was held last December, but that was a release cycle ago, and I don't think it would be overkill. I'd be delighted to set it up if this package is okay. Thanks, -- Nick Ellery -------------- next part -------------- An HTML attachment was scrubbed... URL: From mouz at xs4all.nl Sat Jul 19 08:20:44 2008 From: mouz at xs4all.nl (Carol Meertens) Date: Sat, 19 Jul 2008 10:20:44 +0200 Subject: No subject Message-ID: <20080719082044.GA10159@duper> From mouz at xs4all.nl Sat Jul 19 08:21:04 2008 From: mouz at xs4all.nl (Carol Meertens) Date: Sat, 19 Jul 2008 10:21:04 +0200 Subject: No subject Message-ID: <20080719082104.GA10170@duper> From mouz at xs4all.nl Sat Jul 19 08:24:23 2008 From: mouz at xs4all.nl (Carol Meertens) Date: Sat, 19 Jul 2008 10:24:23 +0200 Subject: HowToTriage: linking a bug report? Message-ID: <20080719082422.GA10150@duper> I'd like to ask a question about https://wiki.ubuntu.com/Bugs/HowToTriage. In section 'Forwarding upstream' it says: > Linking a bug report is much easier: > * Click the "+ Upstream..." or "+ Distribution..." link, as > appropriate. > * Choose the correct "Product" or "Distribution". > * Check the "Link to a bug in another bug tracker:" box. > * Select the proper "Remote Bug Tracker". > * Enter the bug identification number in the "Remote Bug" field. > * Click "Continue". I wanted to link bug 249076 [1] to an existing bug in the Debian bugtracker. I chose distribution Debian, but then I could not find the checkbox mentioned in the third bullet of the quoted list above. I searched around where I had been wrong but I could not make such a checkbox appear. Also there was no "Remote Bug" field, nor a "Remote Bug Tracker" field. I ended up just pasting the full URL in a field that was there. The result was what I intended. My question: is the fact that I did not find the checkbox etc. caused by me doing something wrong, or should the wiki page be changed (or something else)? Thanks, -- mouz [1] https://bugs.launchpad.net/ubuntu/+source/apt-build/+bug/249076 From fnord at pentabarf.de Sat Jul 19 09:20:04 2008 From: fnord at pentabarf.de (Kjell Braden) Date: Sat, 19 Jul 2008 11:20:04 +0200 Subject: HowToTriage: linking a bug report? In-Reply-To: <20080719082422.GA10150@duper> References: <20080719082422.GA10150@duper> Message-ID: <1216459204.6061.5.camel@hegg> On Sa, 2008-07-19 at 10:24 +0200, Carol Meertens wrote: > My question: is the fact that I did not find the checkbox etc. caused > by me doing something wrong, or should the wiki page be changed (or > something else)? > > Thanks, > -- > mouz > [1] https://bugs.launchpad.net/ubuntu/+source/apt-build/+bug/249076 > Hi! I think it's related to the difference between "also affects project" (see for example [1]) and "also affects distribution". The bullet points you are referring to are really for forwarding *upstream* (unlike the first bullet point, which mentions the distribution thing). Looking at your bug report everything is right. [1] https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/157923/+choose-affected-product Kjell -------------- 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 hggdh2 at gmail.com Sat Jul 19 14:33:56 2008 From: hggdh2 at gmail.com (HggdH) Date: Sat, 19 Jul 2008 09:33:56 -0500 Subject: HowToTriage: linking a bug report? In-Reply-To: <20080719082422.GA10150@duper> References: <20080719082422.GA10150@duper> Message-ID: <1216478036.22383.4.camel@localhost> > I'd like to ask a question about > https://wiki.ubuntu.com/Bugs/HowToTriage. In section 'Forwarding > upstream' it says: > > > Linking a bug report is much easier: > > * Click the "+ Upstream..." or "+ Distribution..." link, as > > appropriate. > > * Choose the correct "Product" or "Distribution". > > * Check the "Link to a bug in another bug tracker:" box. > > * Select the proper "Remote Bug Tracker". > > * Enter the bug identification number in the "Remote Bug" field. > > * Click "Continue". > The description does not match the current (rather new) LP interface... I edited it, but would like comments. (snip) > My question: is the fact that I did not find the checkbox etc. caused > by me doing something wrong, or should the wiki page be changed (or > something else)? You did not do anything wrong. Indeed the wiki had to be changed. Thank you for bringing this up. ..hggdh.. -------------- 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 ellery.nick at gmail.com Mon Jul 21 02:52:16 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Sun, 20 Jul 2008 19:52:16 -0700 Subject: Hug day for apt Message-ID: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> Hi all, Discussions on IRC about this Thursday's bug day brought up apt. Would this package be okay, and if so is this Thursday open? Thanks! -- Nick Ellery -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrooney at gmail.com Mon Jul 21 04:03:46 2008 From: mrooney at gmail.com (Mike Rooney) Date: Mon, 21 Jul 2008 00:03:46 -0400 Subject: Hug day for apt In-Reply-To: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> References: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> Message-ID: <4f4806ee0807202103g9d4d29cs3742d0645558040b@mail.gmail.com> On Sun, Jul 20, 2008 at 10:52 PM, Nick Ellery wrote: > Hi all, > > Discussions on IRC about this Thursday's bug day brought up apt. Would this > package be okay, and if so is this Thursday open? > > Thanks! > > -- > Nick Ellery > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > I haven't looked at the bugs for apt but it sounds like a good idea to me! (if Thursday is open). Mike Rooney mrooney at gmail.com From jw+debian at jameswestby.net Mon Jul 21 12:56:42 2008 From: jw+debian at jameswestby.net (James Westby) Date: Mon, 21 Jul 2008 13:56:42 +0100 Subject: Ubiquity Bug Day? In-Reply-To: <809d37bb0807181644y40823265j9a4467a77a2f1dd4@mail.gmail.com> References: <809d37bb0807181644y40823265j9a4467a77a2f1dd4@mail.gmail.com> Message-ID: <1216645002.6182.2.camel@flash> On Fri, 2008-07-18 at 16:44 -0700, Nick Ellery wrote: > Hi all, > > What are your thoughts on having a bug day focusing on Ubiquity? I > understand that one was held last December, but that was a release > cycle ago, and I don't think it would be overkill. I'd be delighted > to set it up if this package is okay. I think an Ubiquity bug day would be a great think to have. I'm sure that the developers would appreciate the help. Thanks, James From dereck at gmail.com Mon Jul 21 23:21:39 2008 From: dereck at gmail.com (Dereck) Date: Mon, 21 Jul 2008 19:21:39 -0400 Subject: Hug day for apt In-Reply-To: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> References: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> Message-ID: <48851A03.3050901@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick Ellery wrote: > Hi all, > > Discussions on IRC about this Thursday's bug day brought up apt. Would > this package be okay, and if so is this Thursday open? > > Thanks! > > -- > Nick Ellery > Nick, Weren't you planning on a Hugday for Ubiquity this week? Pick one and whatever package you don't choose should get a hug next week. :) https://bugs.launchpad.net/ubuntu/+source/apt Open 217 New 121 Unassigned 191 All bugs ever 606 https://bugs.launchpad.net/ubuntu/+source/ubiquity Open 558 New 134 Unassigned 486 All bugs ever 4043 ~Dereck -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIhRoDMbyzSbPQbJgRAtntAKCHJf83POK9TpYcGgx1Zq+8TPNSeACgtmKm MChu18jZpY82LvzYkrGOLXQ= =oTyT -----END PGP SIGNATURE----- From brian at ubuntu.com Mon Jul 21 23:32:03 2008 From: brian at ubuntu.com (Brian Murray) Date: Mon, 21 Jul 2008 16:32:03 -0700 Subject: Hug day for apt In-Reply-To: <48851A03.3050901@gmail.com> References: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> <48851A03.3050901@gmail.com> Message-ID: <20080721233203.GF7409@murraytwins.com> On Mon, Jul 21, 2008 at 07:21:39PM -0400, Dereck wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Nick Ellery wrote: > > Hi all, > > > > Discussions on IRC about this Thursday's bug day brought up apt. Would > > this package be okay, and if so is this Thursday open? > > > > Thanks! > > > > -- > > Nick Ellery > > > > Nick, > > Weren't you planning on a Hugday for Ubiquity this week? Pick one and > whatever package you don't choose should get a hug next week. :) I seem to have replied to Nick privately that I thought the Ubiquity Hug Day should wait until after Alpha 3 is released. Have a Hug Day about apt sounds like a good idea to me. I'd also like to see a section for Confirmed bugs to so the Bug Control team can work on moving those to Triaged. 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 ellery.nick at gmail.com Tue Jul 22 00:05:53 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Mon, 21 Jul 2008 17:05:53 -0700 Subject: Hug day for apt In-Reply-To: <20080721233203.GF7409@murraytwins.com> References: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> <48851A03.3050901@gmail.com> <20080721233203.GF7409@murraytwins.com> Message-ID: <809d37bb0807211705m3fb0a311q5fbaf6abc14e8b24@mail.gmail.com> Sounds good. I'll set that up for this Thursday then! Thanks, On Mon, Jul 21, 2008 at 4:32 PM, Brian Murray wrote: > On Mon, Jul 21, 2008 at 07:21:39PM -0400, Dereck wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Nick Ellery wrote: > > > Hi all, > > > > > > Discussions on IRC about this Thursday's bug day brought up apt. Would > > > this package be okay, and if so is this Thursday open? > > > > > > Thanks! > > > > > > -- > > > Nick Ellery > > > > > > > Nick, > > > > Weren't you planning on a Hugday for Ubiquity this week? Pick one and > > whatever package you don't choose should get a hug next week. :) > > I seem to have replied to Nick privately that I thought the Ubiquity Hug > Day should wait until after Alpha 3 is released. > > Have a Hug Day about apt sounds like a good idea to me. I'd also like > to see a section for Confirmed bugs to so the Bug Control team can work > on moving those to Triaged. > > Thanks, > -- > Brian Murray @ubuntu.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFIhRxzDTAwc5ER+zURAkz5AKCak2pLlWspvTtLot/DYjuRAU4OEgCg7D8I > jrBFrFJsDoaDKkd5UHGVJkw= > =jqgH > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Nick Ellery -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.grossmeier at gmail.com Tue Jul 22 00:21:10 2008 From: greg.grossmeier at gmail.com (Greg Grossmeier) Date: Mon, 21 Jul 2008 17:21:10 -0700 Subject: Hug day for apt In-Reply-To: <809d37bb0807211705m3fb0a311q5fbaf6abc14e8b24@mail.gmail.com> References: <809d37bb0807201952r61998440g4f355cfc9f7f6b1c@mail.gmail.com> <48851A03.3050901@gmail.com> <20080721233203.GF7409@murraytwins.com> <809d37bb0807211705m3fb0a311q5fbaf6abc14e8b24@mail.gmail.com> Message-ID: <488527F6.2060908@gmail.com> Nick Ellery wrote: > Sounds good. I'll set that up for this Thursday then! > On Mon, Jul 21, 2008 at 4:32 PM, Brian Murray > wrote: > I seem to have replied to Nick privately that I thought the Ubiquity Hug > Day should wait until after Alpha 3 is released. > > Have a Hug Day about apt sounds like a good idea to me. I'd also like > to see a section for Confirmed bugs to so the Bug Control team can work > on moving those to Triaged. Plug: https://wiki.ubuntu.com/UbuntuBugDay/Planning :) From mouz at xs4all.nl Tue Jul 22 13:23:11 2008 From: mouz at xs4all.nl (Carol Meertens) Date: Tue, 22 Jul 2008 15:23:11 +0200 Subject: gksu not maintained? Message-ID: <20080722132257.GA15056@duper> Hi all, I was wondering about all those gksu related bugs I meet in launchpad. I looked in the upstream BTS and it seems nothing is fixed since almost two years [1]. In the meantime only debian/patches/ grew. I wonder whether enough thought is going into that, as gksu plays an important role on the desktop. Chances are there I'm missing some point, but I'd like to mention it in case I don't. Thanks, -- mouz [1] http://savannah.nongnu.org/bugs/?group=gksu From cjk-bugsquad at teamcharliesangels.com Tue Jul 22 19:28:48 2008 From: cjk-bugsquad at teamcharliesangels.com (Charlie Kravetz) Date: Tue, 22 Jul 2008 13:28:48 -0600 Subject: Update Bugsquad membership in launchpad Message-ID: <20080722132848.507affc1.cjk-bugsquad@teamcharliesangels.com> After much searching of documentation, I finally found a statement in the wiki that says I need to update my membership in ubuntu-bugsqad yearly. Since the expires date is blank, how do I update that? I am currently working to triage bugs for Xubuntu. My launchpad login is https://launchpad.net/~charlie-tca, I have been on the ubuntu-bugsquad team since 2006-05-31. Thank you. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From ellery.nick at gmail.com Tue Jul 22 21:42:39 2008 From: ellery.nick at gmail.com (Nick Ellery) Date: Tue, 22 Jul 2008 14:42:39 -0700 Subject: Bug Day - Thursday July 24, 2008 Message-ID: <809d37bb0807221442u48ad8508p7dd3333fe53cb5a9@mail.gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This week's Hug Day will be focusing on Apt! There are currently about 127 New bug reports regarding Apt and we will be focusing on reducing that number in addition to looking at some outstanding Incomplete and Confirmed bugs. We'll do this by following up with reporters, documenting test cases, and confirming bug reports. The event will be held in #ubuntu-bugs on Freenode. The list of targeted bugs and tasks is posted at: https://wiki.ubuntu.com/UbuntuBugDay/20080724 Our goal is to deal with all of the bugs on that list. So on 24 July 2008, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu Bug Control team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuBugControl If you're interested in helping to make the next release of Ubuntu even better - please stop by. And feel free to ask anyone on the team for ways to help out. We hope to see you there and your name on the list of bug triagers! Sincerely, - -- Nick Ellery On Behalf of the Ubuntu BugSquad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIhlROw65ukQk+EOgRAtzUAJ4wCrAaupBAsg3HRLyn31l04jzMuACg3g+F 949/2Y2JDTtg91MjZTqX4Po= =q4t/ -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From laserjock at ubuntu.com Sun Jul 27 04:12:23 2008 From: laserjock at ubuntu.com (Jordan Mantha) Date: Sat, 26 Jul 2008 21:12:23 -0700 Subject: Bug Importance Guidelines In-Reply-To: <20080625223451.GL7382@murraytwins.com> References: <20080625223451.GL7382@murraytwins.com> Message-ID: <8d41218e0807262112u49127681kb8e904568f3448c1@mail.gmail.com> On Wed, Jun 25, 2008 at 3:34 PM, Brian Murray wrote: > The current guidelines[0] for setting bug importance were written at at > time when there were not other ways, release targetting and milestones, > for identifying the importance of a bug to the distribution as a whole. > Subsequently, these guidelines use phrases like 'severe impact on a > small portion of Ubuntu users', 'moderate impact on a large portion of > Ubuntu users' and 'severe impact on a large portion of Ubuntu users'. > Since the release team is actively using milestones combined with > release targetting and measuring the quantity of users impacted is vague > and subjective - I believe that the importance of a bug should be > determined based on the impact for the package affected. > > This would change the definition of High and Critical and the following > is what I have in mind for new guidelines. > > * '''High''': A bug which fulfills one of the following criteria: > * is a reproducible crash report > * affects the core functionality of the package > * a problem with an essential hardware component (disk controller, > laptop built-in wireless, video card, keyboard, mouse) > > * '''Critical''': A bug which fulfills one of the following criteria: > * causes a package fail to install or upgrade > * causes a package to fail to build > * causes a loss of data > * causes a severe memory leak > * makes the package unusable e.g. application fails to start or > perform its primary function > > [0] https://wiki.ubuntu.com/Bugs/Importance Has this gotten anywhere? I'd really like to see this proposal implemented. Did it get stalled somewhere? -Jordan From dereck at gmail.com Wed Jul 30 04:39:04 2008 From: dereck at gmail.com (Dereck Wonnacott) Date: Wed, 30 Jul 2008 00:39:04 -0400 Subject: Ubiquity Hug Day!! Message-ID: <488FF068.5070403@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's me again, filling you inbox with what I know you've been waiting for, this week's HUG DAY info!! This week's target is *drum roll please* Ubiquity! * 80 New bugs need a hug * 80 Confirmed bugs just need a quick review A bug in the Ubuntu live CD installer (Ubiquity) might stop someone from even trying out Ubuntu, so it is crucial that we at least help the developers best we can give the best first impression possible! Bookmark it, add it to your calenders, turn over your egg-timers! * Thursday July 31st * http://wiki.ubuntu.com/UbuntuBugDay/20080731 Can't stress it enough: everyone can help! Bug Control Members! There are tons of confirmed bugs here that can't go much further without YOU! BLOG IT! Especially those on the Planet! There are people who want to help but don't know how and sit on the sidelines of the blog-o-sphere reading; I need your help to get those eyes from blogs to bugs. "Bug work is a fun way to get involved!" * Publish about the Hug Day Thursday July 31st to get everyone excited. * Hug some bugs and add yourself to the HugDay's wiki for your readers! Make a difference: Join the Hug Day on Thursday the 31st. 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 ~Dereck (from the BugSquad) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIj/BnMbyzSbPQbJgRAmJxAKDJduuIKKd6McfcDMnZR9ekpvZIWACeKgLH 7HwNt6WvXhrWYWKtMeBbktc= =8s2s -----END PGP SIGNATURE----- From henrik at ubuntu.com Wed Jul 30 12:34:39 2008 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Wed, 30 Jul 2008 13:34:39 +0100 Subject: Bug Importance Guidelines In-Reply-To: <8d41218e0807262112u49127681kb8e904568f3448c1@mail.gmail.com> References: <20080625223451.GL7382@murraytwins.com> <8d41218e0807262112u49127681kb8e904568f3448c1@mail.gmail.com> Message-ID: <48905FDF.8080806@ubuntu.com> Jordan Mantha wrote: > On Wed, Jun 25, 2008 at 3:34 PM, Brian Murray wrote: > >> The current guidelines[0] for setting bug importance were written at at >> time when there were not other ways, release targetting and milestones, >> for identifying the importance of a bug to the distribution as a whole. >> Subsequently, these guidelines use phrases like 'severe impact on a >> small portion of Ubuntu users', 'moderate impact on a large portion of >> Ubuntu users' and 'severe impact on a large portion of Ubuntu users'. >> Since the release team is actively using milestones combined with >> release targetting and measuring the quantity of users impacted is vague >> and subjective - I believe that the importance of a bug should be >> determined based on the impact for the package affected. >> >> This would change the definition of High and Critical and the following >> is what I have in mind for new guidelines. >> >> * '''High''': A bug which fulfills one of the following criteria: >> * is a reproducible crash report >> * affects the core functionality of the package >> * a problem with an essential hardware component (disk controller, >> laptop built-in wireless, video card, keyboard, mouse) >> >> * '''Critical''': A bug which fulfills one of the following criteria: >> * causes a package fail to install or upgrade >> * causes a package to fail to build >> * causes a loss of data >> * causes a severe memory leak >> * makes the package unusable e.g. application fails to start or >> perform its primary function >> >> [0] https://wiki.ubuntu.com/Bugs/Importance >> > > Has this gotten anywhere? I'd really like to see this proposal > implemented. Did it get stalled somewhere? I've added this as an agenda item to today's QA team meeting: https://wiki.ubuntu.com/QATeam/Meetings This change will potentially affect both development and QA and possible release management. All interested parties are encouraged to attend (#ubuntu-meeting 17.00 UTC). Henrik