From pwwnow at gmail.com Mon Jun 4 19:40:33 2007 From: pwwnow at gmail.com (Peter Whittaker) Date: Mon, 04 Jun 2007 15:40:33 -0400 Subject: A graceful exit.... Message-ID: <1180986033.5748.12.camel@EdgeKeep-PC001> Fellow Ubunteros, Ubuntites, and other Ubuntuphiles, Balance in life is everything, and sometimes demands in one area take too much time from others. Sadly, such is the case with my Ubuntuing in various mailing list and groups and fora. In order to devote the time deserved to other priorities, I've need to withdraw from active Ubuntu participation (with decidedly mixed emotions!). To make as graceful an exit as possible, I will be unassigning or reassigning any bugs or pages assigned to me, and following up as best I can on any items I should. If you are awaiting a comment or response from me, please follow up with me directly. Thanks to everyone in the Ubuntu community for a fantastic community experience and fantastic computer experience! Keep up the utterly fantastic work, 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 brian at ubuntu.com Mon Jun 11 17:06:36 2007 From: brian at ubuntu.com (Brian Murray) Date: Mon, 11 Jun 2007 10:06:36 -0700 Subject: Ubuntu Hug Day: 13 June 2007 Message-ID: <20070611170636.GN23321@murraytwins.com> I'm happy to announce our next Hug Day on Wednesday, June 13th. Like the last Hug Day the event will be held in #ubuntu-devel. There will also be a wiki page with tables of bugs in specific categories to work on. There is even a column for you to add your name after meeting the goal for a bug! https://wiki.ubuntu.com/UbuntuBugDay/20070613 This list will be finalized shortly before the start of the 13th to ensure that all the bugs on it still need attention. Our goal is to deal with all of the bugs on that list. So on 13 June 2007, in all timezones, we'll be meeting in #ubuntu-devel on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu QA team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuQA If you're interested in helping, please stop by. And feel free to ask bdmurray, heno, dholbach and the rest of the team for ways to help out. Hope to see you there and your name on the list of bug huggers! -- 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 kirrus at kirrus.co.uk Fri Jun 15 13:55:27 2007 From: kirrus at kirrus.co.uk (Kirrus) Date: Fri, 15 Jun 2007 14:55:27 +0100 (BST) Subject: Bug #78017 Message-ID: <5218488.8021181915727649.JavaMail.root@scalix> Hello all.. I hope this is the right place to post this... I'm not sure what to do to escalate this bug.. it needs looking at, as its result is to completely lock down a computer security wise (no networking at all), which is quite frustrating. The workarounds work, but a fix has been released, so it would be good to see it released into feisty-proposed or some such. (Would be willing to test it...) TIA, Johnathon From kees at ubuntu.com Fri Jun 15 20:29:00 2007 From: kees at ubuntu.com (Kees Cook) Date: Fri, 15 Jun 2007 13:29:00 -0700 Subject: Bug #78017 In-Reply-To: <5218488.8021181915727649.JavaMail.root@scalix> References: <5218488.8021181915727649.JavaMail.root@scalix> Message-ID: <20070615202900.GR12999@outflux.net> Hi Kirrus, On Fri, Jun 15, 2007 at 02:55:27PM +0100, Kirrus wrote: > I'm not sure what to do to escalate this bug.. it needs looking at, as its result is to completely lock down a computer security wise (no networking at all), which is quite frustrating. The workarounds work, but a fix has been released, so it would be good to see it released into feisty-proposed or some such. > (Would be willing to test it...) As you mention, one comment in the bug report says it was fixed upstream, so it's a matter of finding that change, building a patch for firehol, and going through the SRU[1] process for it. It sounds like you're willing to help with the testing portion of the SRU process, so you just need to find someone willing to hunt down the patch and develop a debdiff for it. Perhaps asking nicely on the #ubuntu-motu[2] IRC channel on freenode? Take care, -Kees [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] https://help.ubuntu.com/community/InternetRelayChat -- Kees Cook -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From brian at ubuntu.com Fri Jun 15 23:06:54 2007 From: brian at ubuntu.com (Brian Murray) Date: Fri, 15 Jun 2007 16:06:54 -0700 Subject: Useful Bughelper Feature Message-ID: <20070615230654.GC18844@murraytwins.com> The development version of bughelper includes the utility bugnumbers, which recently received the ability to search for information in the last comment. This can be used a couple of ways to help you find old bugs in a "Needs Info" state. When I mark bugs as needing more information I also assign them to myself. In launchpad[1] I could sort by "recently changed" and look at each bug to see what is going on with it but that still seems inefficient. Instead I'll use bugnumbers: bugnumbers --status "Needs Info" --format=html -l "https://bugs.launchpad.net/~brian-murray/+assignedbugs" --lc="u:brian-murray d:2007-05-15" With '--lc' I am searching for bugs with a last comment by me 'u:brian-murray' and where that comment was made before May 15th, 'd:2007-05-15'. I also used --format=html so the results would be output as urls. In the event that you do not assign bugs to yourself or they are assigned to a team you could use a query like: bugnumbers --format=html -p inkscape --status "Needs Info" --lc="u:bryceharrington d:2007-05-15" The '--format' and '--lc' options are not available with the Feisty package but are in Gutsy and the bzr tree[2]. I wrote this up in some more detail in my bug squad diary[3]. I hope you find this as useful as I do! -- Brian Murray @ubuntu.com [1] https://bugs.launchpad.net/~brian-murray/+assignedbugs [2] https://wiki.ubuntu.com/BugHelper/doc/getting-started [3] https://wiki.ubuntu.com/BugSquad/Diaries/bdmurray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From shirishag75 at gmail.com Sat Jun 16 14:01:22 2007 From: shirishag75 at gmail.com (shirish) Date: Sat, 16 Jun 2007 19:31:22 +0530 Subject: using reportbug & reportbug-ng for reporting bugs upstream to debian Message-ID: <511f47f50706160701w5a8e4d41w72abe0a29ad39c9d@mail.gmail.com> Hi all, I've been reporting bugs for a while & reporting upstream bugs at times when it was necessary. Sometime back I was introduced to reprortbug & although it is a very good tool it seems something is amiss. So lemme make some points & please lemme know how we can contribute to having things done in a better way. The idea is also to make a help document after I get all the answers. Now like some users I don't want to use an MTA to send & receive bug -reports. I am using gutsy & reportbug v. 3.38ubuntu2 Now the configuration file at /etc/reportbug.conf is something very interesting & I am sure has the answers to quite few questions. # You can also specify a port other than 25 smtphost fiordland.ubuntu.com # Username and password for SMTP # smtpuser bob # smtppasswd XXX # Use TLS encryption. # smtptls Lemme mention that Ms. Sarah Hobbes had been very helpful in her own capacity to help me & did the update but some things are still missing. Now while the smtphost thing is cool, what would be the username & password, does it need any filling in. Below is a conversation between reportbug & me. Help me if we can find a suitable way to successfully send it to its home doing a cc at bugs at launchpad.net (don't know if filing bugs through email is yet possible or its a todo thing? ) reportbug Please enter the name of the package in which you have found a problem. > pidgin *** Welcome to reportbug. Use ? for help at prompts. *** Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'shirishag75 ' as your from address. Now is this correct or not? https://launchpad.net/~shirishag75 that's me. Getting status for pidgin... Verifying package integrity... Will send report to Ubuntu (per request). Maintainer for pidgin is 'Ubuntu Core Developers '. Looking up dependencies of pidgin... Please briefly describe your problem (you can elaborate in a moment; an empty response will stop reportbug). This should be a concise summary of what is wrong with the package, for example, "fails to send email" or "does not start with -q option specified." > doesn't like me Rewriting subject to 'pidgin: doesn't like me' How would you rate the severity of this problem or report? 1 critical makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. 3 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non- severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release-critical; however, end users should not do so.) 4 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 5 does-not-build a bug that stops the package from being built from source. (This is a 'virtual severity'.) 6 normal a bug that does not undermine the usability of the whole package; for example, a problem with a particular option or menu item. 7 minor things like spelling mistakes and other minor cosmetic errors that do not affect the core functionality of the package. 8 wishlist suggestions and requests for new features. Please select a severity level: [normal] 8 Do any of the following apply to this report? 1 l10n This bug reports a localization/internationalization issue. 2 patch You are including a patch to fix this problem. 3 none Please select tags: (one at a time) [none] Spawning sensible-editor... Report will be sent to "Ubuntu Bug Tracking System" Submit this report on pidgin (e to edit) [Y|n|a|c|e|i|l|m|p|q|?]? Y Connecting to bugs.debian.org via SMTP... SMTP send failure: {'ubuntu-users at lists.ubuntu.com': (550, 'relay not permitted')} Wrote bug report to /tmp/reportbug-pidgin-20070616-5078-jgeAxU Ok I remember something of this sort also happening an another time. Can this be fixed in a short time? The other way is just to use reportbug to make a nice bug-report & then use gmail to send it. Another thing, there is also a better-looking tool called reportbug-ng, the only thing is it has a very sparse configuration file known as .reportbugng Now are there any options or stuff we want by default to be there, I have opened a bug-report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429235 , if anything comes to your mind which would improve our communication with them using the tool please do so either there or on the mailing list or off-list, either way is preferable to me. Looking forward to your valuable inputs on this. -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From hobbsee at kubuntu.org Sat Jun 16 15:43:00 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Sun, 17 Jun 2007 01:43:00 +1000 Subject: using reportbug & reportbug-ng for reporting bugs upstream to debian In-Reply-To: <511f47f50706160701w5a8e4d41w72abe0a29ad39c9d@mail.gmail.com> References: <511f47f50706160701w5a8e4d41w72abe0a29ad39c9d@mail.gmail.com> Message-ID: <46740504.7000404@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 shirish wrote: > Hi all, > I've been reporting bugs for a while & reporting upstream bugs at > times when it was necessary. Sometime back I was introduced to > reprortbug & although it is a very good tool it seems something is > amiss. So lemme make some points & please lemme know how we can > contribute to having things done in a better way. The idea is also to > make a help document after I get all the answers. > Now like some users I don't want to use an MTA to send & > receive bug -reports. I am using gutsy & reportbug v. 3.38ubuntu2 > > Now the configuration file at /etc/reportbug.conf is something very > interesting & I am sure has the answers to quite few questions. So does the manpage. Try man reportbug. > > # You can also specify a port other than 25 > smtphost fiordland.ubuntu.com > > # Username and password for SMTP > # smtpuser bob > # smtppasswd XXX > > # Use TLS encryption. > # smtptls > > Lemme mention that Ms. Sarah Hobbes had been very helpful in her own > capacity to help me & did the update but some things are still > missing. Please learn to spell my name correctly. And don't make me look like an idiot, because you didn't understand what I was telling you. Repeatedly. The other people in the channel appeared to understand it. > > Now while the smtphost thing is cool, what would be the username & > password, does it need any filling in. It doesn't need it. That's why I didn't add it. > > Below is a conversation between reportbug & me. Help me if we can find > a suitable way to successfully send it to its home doing a cc at > bugs at launchpad.net (don't know if filing bugs through email is yet > possible or its a todo thing? ) It's possible, reportbug should really be made compatible with the current emailing bugs to malone - which requires gpg signing and such. For more information, see https://help.launchpad.net/UsingMaloneEmail > > reportbug > Please enter the name of the package in which you have found a problem. >> pidgin > *** Welcome to reportbug. Use ? for help at prompts. *** > Detected character set: UTF-8 > Please change your locale if this is incorrect. > > Using 'shirishag75 ' as your from address. This is because you did not set your email address in DEBEMAIL, etc. man reportbug would tell you about a *lot* of these options, and tends to save people looking like fools. Not saying that you are one - it's a generic comment. > > Now is this correct or not? https://launchpad.net/~shirishag75 that's me. It doesn't check. Downloading a copy of every single user on launchpad, with all their info, and updating it each time you're going to file a report is clearly unfeasible. I guess it could let you specify your launchpad ID, and look it up from there - however, it's easier just to specify it in the configuration file. Again, man reportbug tells you all of this, explained very clearly. > > Getting status for pidgin... > Verifying package integrity... > Will send report to Ubuntu (per request). > Maintainer for pidgin is 'Ubuntu Core Developers > '. > Looking up dependencies of pidgin... > Please select tags: (one at a time) [none] > Spawning sensible-editor... > Report will be sent to "Ubuntu Bug Tracking System" > > Submit this report on pidgin (e to edit) [Y|n|a|c|e|i|l|m|p|q|?]? Y > Connecting to bugs.debian.org via SMTP... > SMTP send failure: {'ubuntu-users at lists.ubuntu.com': (550, 'relay not > permitted')} > Wrote bug report to /tmp/reportbug-pidgin-20070616-5078-jgeAxU > > Ok I remember something of this sort also happening an another time. > Can this be fixed in a short time? The other way is just to use > reportbug to make a nice bug-report & then use gmail to send it. > You need to actually be a part of ubuntu-members to be able to use this tool, and be using the email address on launchpad. Last I knew, that was the case (as we use it for requestsync too). You're free to use your ISP SMTP server, which obviously will not be able to be pre-filled. At least this way, all of the ubuntu members can use this without modification, if they've set DEBEMAIL and such. If you've got a MTA installed and configured, it appears that reportbug uses that instead. > Another thing, there is also a better-looking tool called > reportbug-ng, the only thing is it has a very sparse configuration > file known as .reportbugng This we sync straight from debian. There are no current plans to change this, unless someone steps up to do the work. > > Now are there any options or stuff we want by default to be there, I > have opened a bug-report at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429235 , if anything > comes to your mind which would improve our communication with them > using the tool please do so either there or on the mailing list or > off-list, either way is preferable to me. > > Looking forward to your valuable inputs on this. I'm sure I'll calm down soon enough. Hobbsee -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGdAUE7/o1b30rzoURAoL7AJ9m78/1qiEVpk+gT6BMGd72p+XeYgCgvgBM E1EcFOWPsFurNey7ZEn/FMw= =Py4E -----END PGP SIGNATURE----- From shirishag75 at gmail.com Sat Jun 16 17:51:41 2007 From: shirishag75 at gmail.com (shirish) Date: Sat, 16 Jun 2007 23:21:41 +0530 Subject: using reportbug & reportbug-ng for reporting bugs upstream to debian In-Reply-To: <46740504.7000404@kubuntu.org> References: <511f47f50706160701w5a8e4d41w72abe0a29ad39c9d@mail.gmail.com> <46740504.7000404@kubuntu.org> Message-ID: <511f47f50706161051s6e20c166v54260f7a48fdb2c8@mail.gmail.com> On 6/16/07, Sarah Hobbs wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > shirish wrote: > > Hi all, > > I've been reporting bugs for a while & reporting upstream bugs at > > times when it was necessary. Sometime back I was introduced to > > reprortbug & although it is a very good tool it seems something is > > amiss. So lemme make some points & please lemme know how we can > > contribute to having things done in a better way. The idea is also to > > make a help document after I get all the answers. > > Now like some users I don't want to use an MTA to send & > > receive bug -reports. I am using gutsy & reportbug v. 3.38ubuntu2 > > > > Now the configuration file at /etc/reportbug.conf is something very > > interesting & I am sure has the answers to quite few questions. > > So does the manpage. Try man reportbug. Will try to understand the things. > > > > # You can also specify a port other than 25 > > smtphost fiordland.ubuntu.com > > > > # Username and password for SMTP > > # smtpuser bob > > # smtppasswd XXX > > > > # Use TLS encryption. > > # smtptls > > > > Lemme mention that Ms. Sarah Hobbes had been very helpful in her own > > capacity to help me & did the update but some things are still > > missing. > > Please learn to spell my name correctly. And don't make me look like an > idiot, because you didn't understand what I was telling you. > Repeatedly. The other people in the channel appeared to understand it. Sarah Hobsee, I wasn't trying to make you look like an idiot, if if makes you happy I am the idiot eternally. The point being I had to do the things I had to, in order to understand them. It was like you pointing to the moon while I was looking at the sun. Not your fault. just I was mis-interpreting it the whole time. Perhaps a part might be that I'm not a native english speaking person & do commit mistakes . Only being human. You are pretty smart but the downside is you have to deal with idiot guys like me all the time :( > > Now while the smtphost thing is cool, what would be the username & > > password, does it need any filling in. > > It doesn't need it. That's why I didn't add it. Thanx for letting that on. > > Below is a conversation between reportbug & me. Help me if we can find > > a suitable way to successfully send it to its home doing a cc at > > bugs at launchpad.net (don't know if filing bugs through email is yet > > possible or its a todo thing? ) > > It's possible, reportbug should really be made compatible with the > current emailing bugs to malone - which requires gpg signing and such. > For more information, see https://help.launchpad.net/UsingMaloneEmail Will surely see it. > > reportbug > > Please enter the name of the package in which you have found a problem. > >> pidgin > > *** Welcome to reportbug. Use ? for help at prompts. *** > > Detected character set: UTF-8 > > Please change your locale if this is incorrect. > > > > Using 'shirishag75 ' as your from address. > > This is because you did not set your email address in DEBEMAIL, etc. > man reportbug would tell you about a *lot* of these options, and tends > to save people looking like fools. Not saying that you are one - it's a > generic comment. while you are right, but I still need to make a connection, atleast for me it might not be the whole answer will need to investigate further how I can use it better. > > Now is this correct or not? https://launchpad.net/~shirishag75 that's me. > > It doesn't check. Downloading a copy of every single user on launchpad, > with all their info, and updating it each time you're going to file a > report is clearly unfeasible. I guess it could let you specify your > launchpad ID, and look it up from there - however, it's easier just to > specify it in the configuration file. Again, man reportbug tells you > all of this, explained very clearly. Sarah, the manuals are not the most newbie-friendly document but as said before will try. > > Getting status for pidgin... > > Verifying package integrity... > > Will send report to Ubuntu (per request). > > Maintainer for pidgin is 'Ubuntu Core Developers > > '. > > Looking up dependencies of pidgin... > > > > Please select tags: (one at a time) [none] > > Spawning sensible-editor... > > Report will be sent to "Ubuntu Bug Tracking System" > > > > Submit this report on pidgin (e to edit) [Y|n|a|c|e|i|l|m|p|q|?]? Y > > Connecting to bugs.debian.org via SMTP... > > SMTP send failure: {'ubuntu-users at lists.ubuntu.com': (550, 'relay not > > permitted')} > > Wrote bug report to /tmp/reportbug-pidgin-20070616-5078-jgeAxU > > > > Ok I remember something of this sort also happening an another time. > > Can this be fixed in a short time? The other way is just to use > > reportbug to make a nice bug-report & then use gmail to send it. > > > You need to actually be a part of ubuntu-members to be able to use this > tool, and be using the email address on launchpad. Last I knew, that > was the case (as we use it for requestsync too). You're free to use > your ISP SMTP server, which obviously will not be able to be pre-filled. > At least this way, all of the ubuntu members can use this without > modification, if they've set DEBEMAIL and such. If you've got a MTA > installed and configured, it appears that reportbug uses that instead. ubuntu-members, didn't know about this part. Again will need further investigation and which means the documentation would also have to be updated (in the wiki) as & when I do understand it. As we talked earlier in the day the best way would be to be able to post the mail to debian bugs without using an MTA (if possible) . I was thinking of reportbug as same or similar tool like apport is which is a bug-reporter & a mailer (kinda) at the same time. So being the fool I'm I'll like to see if this can be done. > > Another thing, there is also a better-looking tool called > > reportbug-ng, the only thing is it has a very sparse configuration > > file known as .reportbugng > > This we sync straight from debian. There are no current plans to change > this, unless someone steps up to do the work. Actually I mailed/talked with the author & maintainer of reportbug-ng & he is open to suggestions but he needs the reasoning & logic of what we want to go alongwith it & he'll decide if its worth doing the thing. > > Now are there any options or stuff we want by default to be there, I > > have opened a bug-report at > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429235 , if anything > > comes to your mind which would improve our communication with them > > using the tool please do so either there or on the mailing list or > > off-list, either way is preferable to me. > > > > Looking forward to your valuable inputs on this. > > I'm sure I'll calm down soon enough. Ah good, its nice to have some healthy tension sometime ;P > > Hobbsee > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGdAUE7/o1b30rzoURAoL7AJ9m78/1qiEVpk+gT6BMGd72p+XeYgCgvgBM > E1EcFOWPsFurNey7ZEn/FMw= > =Py4E > -----END PGP SIGNATURE----- > Cheers & god day to you too :) -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From brian at ubuntu.com Mon Jun 18 15:15:13 2007 From: brian at ubuntu.com (Brian Murray) Date: Mon, 18 Jun 2007 08:15:13 -0700 Subject: Explanation for today's apport bug spam Message-ID: <20070618151513.GL7461@murraytwins.com> I apologize if you already received this e-mail via ubuntu-devel but it seemed important enough to forward to this list in case anyone is not subscribed to ubuntu-devel. ----- Forwarded message from Martin Pitt ----- Date: Mon, 18 Jun 2007 17:05:15 +0200 From: Martin Pitt To: ubuntu-devel at lists.ubuntu.com Subject: Explanation for today's apport bug spam Hello fellow developers, today I did a huge cleanup of CoreDump.gz bug attachments. We need to get rid of them, because they potentially contain sensitive and personal data, and are very large. Unfortunately Launchpad sends out email notifications about that, so that today you will get a large number of email bug spam. This is an one-time action and will never happen again. In the future, apport bugs will silenced thoroughly, see https://wiki.ubuntu.com/CrashReporting This is going to be implemented soon. I apologize for the inconvenience! Martin ----- End forwarded message ----- -- 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 Mon Jun 18 16:32:43 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Tue, 19 Jun 2007 02:32:43 +1000 Subject: Explanation for today's apport bug spam In-Reply-To: <20070618151513.GL7461@murraytwins.com> References: <20070618151513.GL7461@murraytwins.com> Message-ID: <4676B3AB.3010006@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Martin, Please send us this kind of mail a few days in advance, so we can warn any upstreams that get our bugs sent to their mailing lists, so they can create filters to discard all the apport mail. Even to be able to set up those filters for ourselves in advance would be good. Obviously, angry upstreams arent fun. Thanks, Hobbsee. Brian Murray wrote: > I apologize if you already received this e-mail via ubuntu-devel but it > seemed important enough to forward to this list in case anyone is not > subscribed to ubuntu-devel. > > ----- Forwarded message from Martin Pitt ----- > > Date: Mon, 18 Jun 2007 17:05:15 +0200 > From: Martin Pitt > To: ubuntu-devel at lists.ubuntu.com > Subject: Explanation for today's apport bug spam > > Hello fellow developers, > > today I did a huge cleanup of CoreDump.gz bug attachments. We need to > get rid of them, because they potentially contain sensitive and > personal data, and are very large. > > Unfortunately Launchpad sends out email notifications about that, so > that today you will get a large number of email bug spam. This is an > one-time action and will never happen again. > > In the future, apport bugs will silenced thoroughly, see > > https://wiki.ubuntu.com/CrashReporting > > This is going to be implemented soon. > > I apologize for the inconvenience! > > Martin > > ----- End forwarded message ----- > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGdrOr7/o1b30rzoURAhvAAJ0TISYLntqyrjAY0ORL+YtmnJwiVwCg0Wgs sJnMhfdLDX6rkn+e/9jsFz0= =S5+4 -----END PGP SIGNATURE----- From kees at ubuntu.com Mon Jun 18 17:25:21 2007 From: kees at ubuntu.com (Kees Cook) Date: Mon, 18 Jun 2007 10:25:21 -0700 Subject: Useful Bughelper Feature In-Reply-To: <20070615230654.GC18844@murraytwins.com> References: <20070615230654.GC18844@murraytwins.com> Message-ID: <20070618172521.GH24388@outflux.net> On Fri, Jun 15, 2007 at 04:06:54PM -0700, Brian Murray wrote: > When I mark bugs as needing more information I also assign them to > myself. In launchpad[1] I could sort by "recently changed" and look > at each bug to see what is going on with it but that still seems > inefficient. Instead I'll use bugnumbers: > > bugnumbers --status "Needs Info" --format=html -l > "https://bugs.launchpad.net/~brian-murray/+assignedbugs" > --lc="u:brian-murray d:2007-05-15" This is very helpful! When participating in the most recent Hug Day, I addressed many "Unconfirmed" bugs by setting them "Needs Info" and assigned to me. This will let me follow up on them much more quickly. (So far, though, it seems nearly every bug I touched has gotten an answer, so that's good too.) Yay for Hug Days! :) -- Kees Cook -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From henrik at ubuntu.com Tue Jun 19 16:43:33 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Tue, 19 Jun 2007 18:43:33 +0200 Subject: Launchpad bug workflow change Message-ID: <467807B5.6040806@ubuntu.com> Tomorrow (2007-06-20) the Launchpad team will update the bug tracker with a new set of bug states to help projects like Ubuntu improve bug management. The changes will allow for greater fine tuning of our bug management and the new labels should hopefully also make more sense to users. The following statuses will be added: * Triaged * Won't Fix * Todo The following statuses will be renamed: * Unconfirmed -> New * Needs Info -> Incomplete * Rejected -> Invalid The reasons for the new states are roughly: * Triaged will mean that a bug has all the information attached to it that a developer needs to fix it. The 'confirmed' state was previously used for this purpose, but many users were 'confirming' bugs when observed by a second person. * Rejected has been split into Invalid and Won't Fix, where the latter may be a valid bug or wish-list change that we don't have the wish or resources to fix. * Todo will form the list of bugs that developers expect to work on in the near future. These would typically also be assigned to a developer or a dev team. The renaming of some existing states is intended to make them more intuitive to a larger audience. Search URLs containing the old status names will be permanently redirected to equivalent URLs containing the new status names. For example, &status=Unconfirmed will be changed to &status=New. Henrik From cody.somerville at gmail.com Tue Jun 19 16:59:06 2007 From: cody.somerville at gmail.com (Cody Somerville) Date: Tue, 19 Jun 2007 16:59:06 +0000 Subject: Launchpad bug workflow change In-Reply-To: References: <467807B5.6040806@ubuntu.com> Message-ID: I personally think the new status are very appropriate. We always like to cling to what we know but I honestly believe that these changes will be beneficial to bug workflow. Thanks, Cody A.W. Somerville P.S. Would it be possible to remove some of the crud in your signature? I think some would find it inappropriate and, frankly, I find it annoying. Thanks :) On 6/19/07, (``-_-´´) -- Fernando wrote: > > I'm sorry, but I like the old status name better!! > Cant we keep them or at least have a poll about it? > > On 6/19/07, Henrik Nilsen Omma wrote: > > Tomorrow (2007-06-20) the Launchpad team will update the bug tracker > > with a new set of bug states to help projects like Ubuntu improve bug > > management. The changes will allow for greater fine tuning of our bug > > management and the new labels should hopefully also make more sense to > > users. > > > > The following statuses will be added: > > > > * Triaged > > * Won't Fix > > * Todo > > > > The following statuses will be renamed: > > > > * Unconfirmed -> New > > * Needs Info -> Incomplete > > * Rejected -> Invalid > > > > > > The reasons for the new states are roughly: > > > > * Triaged will mean that a bug has all the information attached to it > > that a developer needs to fix it. The 'confirmed' state was previously > > used for this purpose, but many users were 'confirming' bugs when > > observed by a second person. > > > > * Rejected has been split into Invalid and Won't Fix, where the latter > > may be a valid bug or wish-list change that we don't have the wish or > > resources to fix. > > > > * Todo will form the list of bugs that developers expect to work on in > > the near future. These would typically also be assigned to a developer > > or a dev team. > > > > The renaming of some existing states is intended to make them more > > intuitive to a larger audience. > > > > Search URLs containing the old status names will be permanently > > redirected to equivalent URLs containing the new status names. For > > example, &status=Unconfirmed will be changed to &status=New. > > > > Henrik > > > > > > -- > > Ubuntu-devel-discuss mailing list > > Ubuntu-devel-discuss at lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > > > > -- > BUGabundo :o) > (``-_-´´) > GPG key 1024D/00967685 > Linux user #443786 > The body of this email is licensed under a > Creative Commons Attribution-Noncommercial-Share Alike 3.0 > > http://BUGabundo.net > http://BrinKadeiraS.BUGabundo.net > > http://host.BUGabundo.net -- http://alojamento.BUGabundo.net > From 1€ / month > > Crazy Domain Insane (200GB disk, 2TB bw, 6.00€ ($7.95)/month) > > at http://www.dreamhost.com/r.cgi?249195/signup > 50$ discount with promo code "BUG50" on all plans > Free lifetime domain with promo code "BUGDOMAIN" > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss at lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Firefox (www.getfirefox.com) -- A browser you can trust -------------- next part -------------- An HTML attachment was scrubbed... URL: From henrik at ubuntu.com Tue Jun 19 18:33:01 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Tue, 19 Jun 2007 20:33:01 +0200 Subject: Launchpad bug workflow change In-Reply-To: <46781E7F.6080703@cfl.rr.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> Message-ID: <4678215D.30909@ubuntu.com> Phillip Susi wrote: > Henrik Nilsen Omma wrote: >> * Triaged will mean that a bug has all the information attached to >> it that a developer needs to fix it. The 'confirmed' state was >> previously used for this purpose, but many users were 'confirming' >> bugs when observed by a second person. > > I disagree with this term. If something has been Triaged, that means > it has been evaluated for urgency and had resources assigned > appropriately. I agree that 'evaluating the urgency' should also fit into the Triaged state. However, not that this can only be done by ubuntu-qa or developers (setting importance). Assigning resources can really only be done by the people who intend to fix it, which is an even smaller group. The point of having the Triaged step is that the people fixing bugs should not have to look at all 30 000 open bugs. They only look at Triaged and from that group they reject some, push some back to Incomplete and add some to their Todo list. That should make the overall workflow more precise and efficient. We can discuss how well the word 'Triaged' fit that category, but IMO we do need that category. > >> * Todo will form the list of bugs that developers expect to work on >> in the near future. These would typically also be assigned to a >> developer or a dev team. > > I see no real difference between this and the proposed use of Triaged. > If a bug is confirmed to exist and has had all required information > attached to it so that a developer can now fix it, why wouldn't a > developer expect to work on it in the near future? Because we don't have the resources to fix all the bugs that are filed in Ubuntu within the the project. We may file them upstream and leave them Triaged or mark it In Progress if work is ongoing upstream. A developer may also look at a Triaged bug and decide it is a WontFix because it's not appropriate for Ubuntu or we don't have the resources to fix it. Henrik From henrik at ubuntu.com Tue Jun 19 20:56:59 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Tue, 19 Jun 2007 22:56:59 +0200 Subject: Launchpad bug workflow change In-Reply-To: <4678304F.30207@cfl.rr.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> Message-ID: <4678431B.6020508@ubuntu.com> Phillip Susi wrote: > Henrik Nilsen Omma wrote: >> I agree that 'evaluating the urgency' should also fit into the >> Triaged state. However, not that this can only be done by ubuntu-qa >> or developers (setting importance). Assigning resources can really >> only be done by the people who intend to fix it, which is an even >> smaller group. The point of having the Triaged step is that the >> people fixing bugs should not have to look at all 30 000 open bugs. >> They only look at Triaged and from that group they reject some, push >> some back to Incomplete and add some to their Todo list. That should >> make the overall workflow more precise and efficient. We can discuss >> how well the word 'Triaged' fit that category, but IMO we do need >> that category. > > Now it sounds like Todo is the same as In progress, set by a developer > when he is ( or is about to be ) working on it. And Triaged is for > bugs that are ready to be pulled into that pool, which is what > confirmed is today. Todo is the list of bugs that a developer intends to work on, but it may take months before that work starts. In Progress should be used when work has actually started. It not the most frequently used state, that's true. > It looks like you are trying to find a state for bugs that are > completely documented, but for some reason are not ready for developer > attention. There are several groups of people working with the bug list at different stages and with different skill sets. The system should help all these groups organise their work. What may at first seem like too many bugstates can be useful in showing what stage the bug is at relative to these different groups. What I did not mention in my first mail (just confirmed this with the LP developer), is that the groups who can set the different states will now also change. * When a bug is filed it will be New The bugsquad can (actually anyone): * Determine whether it is Invalid, Incomplete or Confirmed (reproduced) The bug contact, ubuntu-qa or a developer can: * Set the bug to Triaged if all the needed information is there AND at the same time give it an importance. This person can also set it to WonFix or push it back to one of the earlier stages such as Incomplete or Invalid. A developer can: * Move the bug from Triaged to ToDo or push it back to a previous category. This new structure gives several advantages. * By looking at the status of a bug you can immediately infer whether the bug has been vetted by a trusted person. In Triaged it has been seen by a trusted ubuntu-qa person and in ToDo by a developer. * Each group has a smaller group of bugs they need to look at. The smaller group in ubuntu-qa only has to look at the Confirmed bugs, provided we have an active bugsquad outside ubuntu-qa. Developers only have to look at Triaged, knowing these have already been looked at by ubuntu-qa. * Pushing bugs back to previous categories is a useful way to provide tutoring to less experienced triagers (thus helping them gain experience). Such push-backs should be accompanied by helpful advice on how to triage it correctly. > What other reason would a developer have for not wanting to look at a > bug other than it is invalid ( and thus should be rejected ), or it > needs fixed upstream? Maybe we just need to bring back the upstream > state we used to have in bugzilla? I think this can be done by adding an upstream task and setting the Ubuntu task to WontFix. Henrik From Ubuntu at BUGabundo.net Tue Jun 19 16:50:17 2007 From: Ubuntu at BUGabundo.net (=?ISO-8859-1?Q?(``-=5F-=B4=B4)_--_Fernando?=) Date: Tue, 19 Jun 2007 17:50:17 +0100 Subject: Launchpad bug workflow change In-Reply-To: <467807B5.6040806@ubuntu.com> References: <467807B5.6040806@ubuntu.com> Message-ID: I'm sorry, but I like the old status name better!! Cant we keep them or at least have a poll about it? On 6/19/07, Henrik Nilsen Omma wrote: > Tomorrow (2007-06-20) the Launchpad team will update the bug tracker > with a new set of bug states to help projects like Ubuntu improve bug > management. The changes will allow for greater fine tuning of our bug > management and the new labels should hopefully also make more sense to > users. > > The following statuses will be added: > > * Triaged > * Won't Fix > * Todo > > The following statuses will be renamed: > > * Unconfirmed -> New > * Needs Info -> Incomplete > * Rejected -> Invalid > > > The reasons for the new states are roughly: > > * Triaged will mean that a bug has all the information attached to it > that a developer needs to fix it. The 'confirmed' state was previously > used for this purpose, but many users were 'confirming' bugs when > observed by a second person. > > * Rejected has been split into Invalid and Won't Fix, where the latter > may be a valid bug or wish-list change that we don't have the wish or > resources to fix. > > * Todo will form the list of bugs that developers expect to work on in > the near future. These would typically also be assigned to a developer > or a dev team. > > The renaming of some existing states is intended to make them more > intuitive to a larger audience. > > Search URLs containing the old status names will be permanently > redirected to equivalent URLs containing the new status names. For > example, &status=Unconfirmed will be changed to &status=New. > > Henrik > > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- BUGabundo :o) (``-_-´´) GPG key 1024D/00967685 Linux user #443786 The body of this email is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 http://BUGabundo.net http://BrinKadeiraS.BUGabundo.net http://host.BUGabundo.net -- http://alojamento.BUGabundo.net >From 1€ / month Crazy Domain Insane (200GB disk, 2TB bw, 6.00€ ($7.95)/month) at http://www.dreamhost.com/r.cgi?249195/signup 50$ discount with promo code "BUG50" on all plans Free lifetime domain with promo code "BUGDOMAIN" From psusi at cfl.rr.com Tue Jun 19 18:20:47 2007 From: psusi at cfl.rr.com (Phillip Susi) Date: Tue, 19 Jun 2007 14:20:47 -0400 Subject: Launchpad bug workflow change In-Reply-To: <467807B5.6040806@ubuntu.com> References: <467807B5.6040806@ubuntu.com> Message-ID: <46781E7F.6080703@cfl.rr.com> Henrik Nilsen Omma wrote: > * Triaged will mean that a bug has all the information attached to it > that a developer needs to fix it. The 'confirmed' state was previously > used for this purpose, but many users were 'confirming' bugs when > observed by a second person. I disagree with this term. If something has been Triaged, that means it has been evaluated for urgency and had resources assigned appropriately. That doesn't seem to map well to the definition used here of "all the information that is needed has been attached". It should simply mean that it has been assigned the appropriate priority and to the appropriate team. > * Todo will form the list of bugs that developers expect to work on in > the near future. These would typically also be assigned to a developer > or a dev team. I see no real difference between this and the proposed use of Triaged. If a bug is confirmed to exist and has had all required information attached to it so that a developer can now fix it, why wouldn't a developer expect to work on it in the near future? From psusi at cfl.rr.com Tue Jun 19 19:36:47 2007 From: psusi at cfl.rr.com (Phillip Susi) Date: Tue, 19 Jun 2007 15:36:47 -0400 Subject: Launchpad bug workflow change In-Reply-To: <4678215D.30909@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> Message-ID: <4678304F.30207@cfl.rr.com> Henrik Nilsen Omma wrote: > I agree that 'evaluating the urgency' should also fit into the Triaged > state. However, not that this can only be done by ubuntu-qa or > developers (setting importance). Assigning resources can really only be > done by the people who intend to fix it, which is an even smaller group. > The point of having the Triaged step is that the people fixing bugs > should not have to look at all 30 000 open bugs. They only look at > Triaged and from that group they reject some, push some back to > Incomplete and add some to their Todo list. That should make the overall > workflow more precise and efficient. We can discuss how well the word > 'Triaged' fit that category, but IMO we do need that category. Now it sounds like Todo is the same as In progress, set by a developer when he is ( or is about to be ) working on it. And Triaged is for bugs that are ready to be pulled into that pool, which is what confirmed is today. It looks like you are trying to find a state for bugs that are completely documented, but for some reason are not ready for developer attention. What other reason would a developer have for not wanting to look at a bug other than it is invalid ( and thus should be rejected ), or it needs fixed upstream? Maybe we just need to bring back the upstream state we used to have in bugzilla? From onno at itmaze.com.au Tue Jun 19 21:47:14 2007 From: onno at itmaze.com.au (Onno Benschop) Date: Wed, 20 Jun 2007 05:47:14 +0800 Subject: Launchpad bug workflow change In-Reply-To: <4678431B.6020508@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> Message-ID: <46784EE2.8010003@itmaze.com.au> On 20/06/07 04:56, Henrik Nilsen Omma wrote: > What I did not mention in my first mail (just confirmed this with the LP > developer), is that the groups who can set the different states will now > also change. > > [..deleted..] > > A developer can: > > * Move the bug from Triaged to ToDo or push it back to a previous category. > So, I'm a member of the general community. I have taken ownership of a bug, I'm working on it, and I cannot set it to ToDo, Triaged or In Progress? How do I manage the bugs I'm working on, and more importantly, how do I tell everyone else that I'm working on them? -- Onno Benschop Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA) -- ()/)/)() ..ASCII for Onno.. |>>? ..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. Proudly supported by Skipper Trucks, Highway1, Concept AV, Sony Central, Dalcon ITmaze - ABN: 56 178 057 063 - ph: 04 1219 8888 - onno at itmaze.com.au From henrik at ubuntu.com Tue Jun 19 21:59:17 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Tue, 19 Jun 2007 23:59:17 +0200 Subject: Launchpad bug workflow change In-Reply-To: <46784EE2.8010003@itmaze.com.au> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> <46784EE2.8010003@itmaze.com.au> Message-ID: <467851B5.5050906@ubuntu.com> Onno Benschop wrote: > On 20/06/07 04:56, Henrik Nilsen Omma wrote: > >> What I did not mention in my first mail (just confirmed this with the LP >> developer), is that the groups who can set the different states will now >> also change. >> >> [..deleted..] >> >> A developer can: >> >> * Move the bug from Triaged to ToDo or push it back to a previous category. >> >> > So, I'm a member of the general community. I have taken ownership of a > bug, I'm working on it, and I cannot set it to ToDo, Triaged or In Progress? > When you say 'a member of the general community' do you mean not in ubuntu-qa and not a developer (I ask because people from the volunteer community are also in those groups)? If you are not then it it's correct that you cannot set those states. This change gives more structure to the bug flow in that it will be more clear what is meant by a given state. > How do I manage the bugs I'm working on, and more importantly, how do I > tell everyone else that I'm working on them? > If you are trying to reproduce it or asking for more information from the submitter then this will be clear from the comments and you can set it to Incomplete. If you are not a developer then it is misleading to set it to In Progress because nobody is actually working on the fix and it may never be fixed. Henrik From henrik at ubuntu.com Tue Jun 19 22:24:27 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Wed, 20 Jun 2007 00:24:27 +0200 Subject: Launchpad bug workflow change In-Reply-To: <467854EC.3000306@cfl.rr.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> <46784EE2.8010003@itmaze.com.au> <467851B5.5050906@ubuntu.com> <467854EC.3000306@cfl.rr.com> Message-ID: <4678579B.10308@ubuntu.com> Phillip Susi wrote: > Henrik Nilsen Omma wrote: >> If you are not a developer then it is misleading to set it to In >> Progress because nobody is actually working on the fix and it may >> never be fixed. > > There are those of us who are not developers but do still work on > fixing bugs ;) > > Non developers should be able to set these states if the bug is > assigned to them. I don't think you should assign a bug to yourself if you are not working on fixing it. IMO you should try to move it along to the Triaged state as efficiently as possible and bugs should be assigned to the developer or dev team who is going to fix it. I realise that this thinking does not match current triaging policy but IMO that policy should be changed. Too many bugs are being held up in half-triaged states. Important bugs are sometimes not getting the attention they should while less important ones are cluttering up the field. FWIW, I'm not a developer myself, I'm simply looking at ways of making the triage process more structured and efficient. Henrik From psusi at cfl.rr.com Tue Jun 19 22:13:00 2007 From: psusi at cfl.rr.com (Phillip Susi) Date: Tue, 19 Jun 2007 18:13:00 -0400 Subject: Launchpad bug workflow change In-Reply-To: <467851B5.5050906@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> <46784EE2.8010003@itmaze.com.au> <467851B5.5050906@ubuntu.com> Message-ID: <467854EC.3000306@cfl.rr.com> Henrik Nilsen Omma wrote: > If you are not a developer then it is misleading to set it to In > Progress because nobody is actually working on the fix and it may never > be fixed. There are those of us who are not developers but do still work on fixing bugs ;) Non developers should be able to set these states if the bug is assigned to them. From onno at itmaze.com.au Tue Jun 19 22:23:35 2007 From: onno at itmaze.com.au (Onno Benschop) Date: Wed, 20 Jun 2007 06:23:35 +0800 Subject: Launchpad bug workflow change In-Reply-To: <467851B5.5050906@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> <46784EE2.8010003@itmaze.com.au> <467851B5.5050906@ubuntu.com> Message-ID: <46785767.2090408@itmaze.com.au> On 20/06/07 05:59, Henrik Nilsen Omma wrote: > Onno Benschop wrote: > >> On 20/06/07 04:56, Henrik Nilsen Omma wrote: >> >> >>> What I did not mention in my first mail (just confirmed this with the LP >>> developer), is that the groups who can set the different states will now >>> also change. >>> >>> [..deleted..] >>> >>> A developer can: >>> >>> * Move the bug from Triaged to ToDo or push it back to a previous category. >>> >>> >>> >> So, I'm a member of the general community. I have taken ownership of a >> bug, I'm working on it, and I cannot set it to ToDo, Triaged or In Progress? >> >> > When you say 'a member of the general community' do you mean not in > ubuntu-qa and not a developer (I ask because people from the volunteer > community are also in those groups)? If you are not then it it's > correct that you cannot set those states. This change gives more > structure to the bug flow in that it will be more clear what is meant by > a given state. > Yes. I'm not a member of any groups. So, I think you're saying I should become a member of those groups :) >> How do I manage the bugs I'm working on, and more importantly, how do I >> tell everyone else that I'm working on them? >> >> > If you are trying to reproduce it or asking for more information from > the submitter then this will be clear from the comments and you can set > it to Incomplete. > > If you are not a developer then it is misleading to set it to In > Progress because nobody is actually working on the fix and it may never > be fixed. > Well, no I'm not a developer, err, I am, but not in the Ubuntu context. If I'm working on a bug in say dosfstools, or gphpedit, then there is no need for another developer to spend time duplicating my work. To be accurate, I've not released any actual fixes (yet), so I've not had a problem where I needed to submit a fix. So to say that nobody is working on the fix, sort of makes me a nobody :-) Perhaps a better question for me to ask is: "Do I need to become a member of any specific groups to fix bugs in Ubuntu?" -- Onno Benschop Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA) -- ()/)/)() ..ASCII for Onno.. |>>? ..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. Proudly supported by Skipper Trucks, Highway1, Concept AV, Sony Central, Dalcon ITmaze - ABN: 56 178 057 063 - ph: 04 1219 8888 - onno at itmaze.com.au From henrik at ubuntu.com Tue Jun 19 22:41:36 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Wed, 20 Jun 2007 00:41:36 +0200 Subject: Launchpad bug workflow change In-Reply-To: <46785767.2090408@itmaze.com.au> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> <46784EE2.8010003@itmaze.com.au> <467851B5.5050906@ubuntu.com> <46785767.2090408@itmaze.com.au> Message-ID: <46785BA0.3070803@ubuntu.com> Onno Benschop wrote: >>> >>> >> When you say 'a member of the general community' do you mean not in >> ubuntu-qa and not a developer (I ask because people from the volunteer >> community are also in those groups)? If you are not then it it's >> correct that you cannot set those states. This change gives more >> structure to the bug flow in that it will be more clear what is meant by >> a given state. >> >> > Yes. I'm not a member of any groups. So, I think you're saying I should > become a member of those groups :) > Yes, please do! > >> If you are trying to reproduce it or asking for more information from >> the submitter then this will be clear from the comments and you can set >> it to Incomplete. >> >> If you are not a developer then it is misleading to set it to In >> Progress because nobody is actually working on the fix and it may never >> be fixed. >> >> > Well, no I'm not a developer, err, I am, but not in the Ubuntu context. > If I'm working on a bug in say dosfstools, or gphpedit, then there is no > need for another developer to spend time duplicating my work. To be > accurate, I've not released any actual fixes (yet), so I've not had a > problem where I needed to submit a fix. > > So to say that nobody is working on the fix, sort of makes me a nobody :-) > Please don't interpret it that way :) As I replied to Scott, if the bug is not handled by someone who can upload to Ubuntu then it's fair to say that nobody is working on a fix in Ubuntu. > "Do I need to become a member of any specific groups to fix bugs in > Ubuntu?" > To do it independently, yes. I we encourage you to! Henrik From ubuntu at kitterman.com Tue Jun 19 22:30:16 2007 From: ubuntu at kitterman.com (Scott Kitterman) Date: Tue, 19 Jun 2007 18:30:16 -0400 Subject: Launchpad bug workflow change In-Reply-To: <4678579B.10308@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <467854EC.3000306@cfl.rr.com> <4678579B.10308@ubuntu.com> Message-ID: <200706191830.16702.ubuntu@kitterman.com> On Tuesday 19 June 2007 18:24, Henrik Nilsen Omma wrote: > Phillip Susi wrote: > > Henrik Nilsen Omma wrote: > >> If you are not a developer then it is misleading to set it to In > >> Progress because nobody is actually working on the fix and it may > >> never be fixed. > > > > There are those of us who are not developers but do still work on > > fixing bugs ;) > > > > Non developers should be able to set these states if the bug is > > assigned to them. > > I don't think you should assign a bug to yourself if you are not working > on fixing it. IMO you should try to move it along to the Triaged state > as efficiently as possible and bugs should be assigned to the developer > or dev team who is going to fix it. > > I realise that this thinking does not match current triaging policy but > IMO that policy should be changed. Too many bugs are being held up in > half-triaged states. Important bugs are sometimes not getting the > attention they should while less important ones are cluttering up the > field. So is this imposing policy change through system updates without discussing it with those affected or were there people involved in the triaging process that were consulted? > FWIW, I'm not a developer myself, I'm simply looking at ways of making > the triage process more structured and efficient. Currently in LP assigned means this is the person who is expected to take the next step on the bug (for example when I set a bug to needs info, I generally assign it to the reporter to make this clear). I'm not sure how taking away triaging tools aligns with your stated goal? Scott K From onno at itmaze.com.au Tue Jun 19 22:48:52 2007 From: onno at itmaze.com.au (Onno Benschop) Date: Wed, 20 Jun 2007 06:48:52 +0800 Subject: Launchpad bug workflow change In-Reply-To: <46785A77.6030409@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <46784EE2.8010003@itmaze.com.au> <467851B5.5050906@ubuntu.com> <200706191806.44192.ubuntu@kitterman.com> <46785A77.6030409@ubuntu.com> Message-ID: <46785D54.1040000@itmaze.com.au> On 20/06/07 06:36, Henrik Nilsen Omma wrote: > OK, so I should have said 'Ubuntu developer' (member of core dev or > MOTU) instead of 'developer'. Lots of fixes are being worked on by > upstreams or other non-Ubuntu developers all the time, but we don't mark > a bug as In Progress unless someone is working on a fix in Ubuntu, or at > least in a remote bugtracker to which we have set an upstream task. > > We would encourage anyone who is a developer to join MOTU and later > core-dev so you can upload fixes directly. If you submit useful patches > you would also very easily qualify for ubuntu-qa. > > So, now because I'm working on a bug, I need to become a Master Of The Universe? Somehow I think that this is counter productive. I don't feel that I know enough about the inner workings of Ubuntu to do that membership justice. I can see a time in the future where that may well be the case, but right now, I'm just fixing bugs. I suspect that there are many contributors who would feel uncomfortable with the requirement you are outlining. I think that the suggestion made by Phillip Susi would solve the problem without the memberships you are outlining. On 20/06/07 06:13, Phillip Susi wrote: > Non developers should be able to set these states if the bug is assigned > to them. > -- Onno Benschop Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA) -- ()/)/)() ..ASCII for Onno.. |>>? ..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. Proudly supported by Skipper Trucks, Highway1, Concept AV, Sony Central, Dalcon ITmaze - ABN: 56 178 057 063 - ph: 04 1219 8888 - onno at itmaze.com.au From henrik at ubuntu.com Tue Jun 19 22:57:24 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Wed, 20 Jun 2007 00:57:24 +0200 Subject: Launchpad bug workflow change In-Reply-To: <200706191830.16702.ubuntu@kitterman.com> References: <467807B5.6040806@ubuntu.com> <467854EC.3000306@cfl.rr.com> <4678579B.10308@ubuntu.com> <200706191830.16702.ubuntu@kitterman.com> Message-ID: <46785F54.9030909@ubuntu.com> Scott Kitterman wrote: >> >> I don't think you should assign a bug to yourself if you are not working >> on fixing it. IMO you should try to move it along to the Triaged state >> as efficiently as possible and bugs should be assigned to the developer >> or dev team who is going to fix it. >> >> I realise that this thinking does not match current triaging policy but >> IMO that policy should be changed. Too many bugs are being held up in >> half-triaged states. Important bugs are sometimes not getting the >> attention they should while less important ones are cluttering up the >> field. >> > > So is this imposing policy change through system updates without discussing it > with those affected or were there people involved in the triaging process > that were consulted? > First, you are mixing up two things. The technical change made to launchpad has been discussed for a while, including at UDS in Sevilla where community members participated and the phone lines to the world were open. Second, we are not imposing 'this' policy (that triagers should not assign themselves) at all. I just gave you my personal opinion. I know that many disagree with me on that and that I will have to make my case here in much more detail before in can get any more traction. > >> FWIW, I'm not a developer myself, I'm simply looking at ways of making >> the triage process more structured and efficient. >> > > Currently in LP assigned means this is the person who is expected to take the > next step on the bug (for example when I set a bug to needs info, I generally > assign it to the reporter to make this clear). > That's what you take it to mean and that's what the wiki suggests. I happen to think it's not the best way to do it. Traditionally in open source projects a bug has been assigned to the person intending to fix it. > I'm not sure how taking away triaging tools aligns with your stated goal? > I think I have helped create more triage tools than I have taken away ;) Henrik From hobbsee at kubuntu.org Wed Jun 20 04:13:28 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Wed, 20 Jun 2007 14:13:28 +1000 Subject: Launchpad bug workflow change In-Reply-To: <4678579B.10308@ubuntu.com> References: <467807B5.6040806@ubuntu.com> <46781E7F.6080703@cfl.rr.com> <4678215D.30909@ubuntu.com> <4678304F.30207@cfl.rr.com> <4678431B.6020508@ubuntu.com> <46784EE2.8010003@itmaze.com.au> <467851B5.5050906@ubuntu.com> <467854EC.3000306@cfl.rr.com> <4678579B.10308@ubuntu.com> Message-ID: <4678A968.8020406@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nice change! However, we've missed a case completely...I'm not sure how I didnt think of it at UDS. Henrik Nilsen Omma wrote: > Phillip Susi wrote: >> Henrik Nilsen Omma wrote: >>> If you are not a developer then it is misleading to set it to In >>> Progress because nobody is actually working on the fix and it may >>> never be fixed. wrong. We have sponsorships, and mentoring, of bugfixes, and package updates. We should not cut out our potential developer community like this. >> There are those of us who are not developers but do still work on >> fixing bugs ;) >> >> Non developers should be able to set these states if the bug is >> assigned to them. As one of the leaders of ubuntu-universe-sponsors, I think this is the appropriate solution. > > I don't think you should assign a bug to yourself if you are not working > on fixing it. IMO you should try to move it along to the Triaged state > as efficiently as possible and bugs should be assigned to the developer > or dev team who is going to fix it. But the user is going to fix it, that's why it's assigned to them. We're assuming you're meaning developer as in people in ~ubuntu-dev here. > FWIW, I'm not a developer myself, I'm simply looking at ways of making > the triage process more structured and efficient. > > Henrik Hobbsee -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeKln7/o1b30rzoURAghxAJ0bbw4H2+NAgJAtZCKGBffW35waVQCgsLe4 zcyLrO68/aW5Iu7S0U5dPq0= =KnCI -----END PGP SIGNATURE----- From shirishag75 at gmail.com Thu Jun 21 03:26:47 2007 From: shirishag75 at gmail.com (shirish) Date: Thu, 21 Jun 2007 08:56:47 +0530 Subject: ubuntu testing site issues Message-ID: <511f47f50706202026g690ff910gd9a718085f0246cc@mail.gmail.com> Hi all, I used firefox with ubuntu. 7.10 & I got 2 site certificates warning at www.ubuntu.com/testing . I dunno which is the right place to send this info. hence sending at almost all the places. -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From micah at cowan.name Thu Jun 21 19:36:40 2007 From: micah at cowan.name (Micah Cowan) Date: Thu, 21 Jun 2007 12:36:40 -0700 Subject: Launchpad bug workflow change In-Reply-To: <467807B5.6040806@ubuntu.com> References: <467807B5.6040806@ubuntu.com> Message-ID: <467AD348.1060301@cowan.name> Henrik Nilsen Omma wrote: > Tomorrow (2007-06-20) the Launchpad team will update the bug tracker > with a new set of bug states to help projects like Ubuntu improve bug > management. The changes will allow for greater fine tuning of our bug > management and the new labels should hopefully also make more sense to > users. > > The following statuses will be added: > > * Triaged > * Won't Fix > * Todo > > The following statuses will be renamed: > > * Unconfirmed -> New > * Needs Info -> Incomplete > * Rejected -> Invalid I have a concern that: Incomplete Invalid Are, at a quick glance, easily confused, and triagers can easily choose Invalid when they really mean Incomplete, and not notice the mistake they've made. Actually, I'm worried about easily making that mistake myself. -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ From shirishag75 at gmail.com Fri Jun 22 06:32:39 2007 From: shirishag75 at gmail.com (shirish) Date: Fri, 22 Jun 2007 12:02:39 +0530 Subject: changing descriptions, upstream bug-handling Message-ID: <511f47f50706212332m78ddae3t48dbd533100a2ef5@mail.gmail.com> Hi all, Coupld of things which I wanted to mention :- A. I had set up a bug-report https://bugs.launchpad.net/debian/+source/deluge-torrent/+bug/119995 which was subsequently changed by somebody named Marco Rodrigues & is something very different than what I had reported. Now there is no way I or anyone can perceive . There is a very small/thin description called view the original description. What should be a better way is to somehow tag it to the person who made the changes , something like Bug Description : Details Changed/updated by : person who updated the bug description Original Description : Name of person who originally filed the bug View Original Description (hotlink) I'm no designer hence this is a very ugly way to present it but atleast the logic & reasoning is clear. Of course dunno how it would work in cases where the bug description went through many changes . (dunno if there are such cases also? ) B. A way to see what changes/comments were made up-stream . The same bug https://bugs.beta.launchpad.net/ubuntu/+source/deluge-torrent/+bug/119995 , as I had filed the upstream bug as requested by Sarah Hobbsee (hope I get the spelling right this time) , the upgrade has entered into qa (testing) but somehow this isn't reflected in launchpad. Can these changes be reflected or not? Cheers ! -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 06C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From hobbsee at kubuntu.org Fri Jun 22 06:55:40 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Fri, 22 Jun 2007 16:55:40 +1000 Subject: changing descriptions, upstream bug-handling In-Reply-To: <511f47f50706212332m78ddae3t48dbd533100a2ef5@mail.gmail.com> References: <511f47f50706212332m78ddae3t48dbd533100a2ef5@mail.gmail.com> Message-ID: <467B726C.3030704@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 shirish wrote: > Hi all, > Coupld of things which I wanted to mention :- > > A. I had set up a bug-report > https://bugs.launchpad.net/debian/+source/deluge-torrent/+bug/119995 > which was subsequently changed by somebody named Marco Rodrigues & is > something very different than what I had reported. Now there is no way > I or anyone can perceive . There is a very small/thin description > called view the original description. What should be a better way is > to somehow tag it to the person who made the changes , something like > > Bug Description : Details > Changed/updated by : person who updated the bug description > Original Description : Name of person who originally filed the bug > View Original Description (hotlink) > > I'm no designer hence this is a very ugly way to present it but > atleast the logic & reasoning is clear. Of course dunno how it would > work in cases where the bug description went through many changes . > (dunno if there are such cases also? ) People dont usually change bugs without a reason. That was a "needs-packaging" bug, i filed it upstream, as you hadnt, and someone else saw it, linked it to our bugtracker, then changed it to request the sync of the package. This is logical. Else, a separate sync request could have been made, and your bug been filed a dupe of that. Take your pick - both are sane options, and are fairly easy to figure out the rationale behind. > > B. A way to see what changes/comments were made up-stream . The same > bug https://bugs.beta.launchpad.net/ubuntu/+source/deluge-torrent/+bug/119995 > , as I had filed the upstream bug as requested by Sarah Hobbsee (hope > I get the spelling right this time) , You didn't. Check launchpad.net/~hobbsee if you need to, or the real name on my irc client. It's not hard. the upgrade has entered into qa > (testing) but somehow this isn't reflected in launchpad. Can these > changes be reflected or not? > > Cheers ! I cant really understand what you're asking here - but LP does eventually update with what the upstream bug says, with it's status. It's very easy to click on the debian bug link (top right corner), and read the bug. Hobbsee -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGe3Js7/o1b30rzoURAtk0AKDMUWiIfc1XAeN984NveSDl0kM1fgCdHHmB 3VMeyFE6Ju3jUwAYQz954C8= =2DHO -----END PGP SIGNATURE----- From brian at ubuntu.com Fri Jun 22 20:45:10 2007 From: brian at ubuntu.com (Brian Murray) Date: Fri, 22 Jun 2007 13:45:10 -0700 Subject: Ubuntu Hug Day: 27 June 2007 Message-ID: <20070622204509.GJ25431@murraytwins.com> I'm happy to announce our next Hug Day on Wednesday, June 27th. The theme for the Hug Day will be server bugs. Specifically looking at the packages samba, php5, openssh, mysql, apache2, postfix, and openldap2.3. Joining us will be Soren Hansen and Rick Clark from the Ubuntu Server Team. Like the last Hug Day the event will be held in #ubuntu-devel. There will also be a wiki page with bugs in specific categories to work on. There is even a place for you to add your name after meeting the goal for a bug! https://wiki.ubuntu.com/UbuntuBugDay/20070627 This list will be finalized shortly before the start of the 27th to ensure that all the bugs on it still need attention. Our goal is to deal with all of the bugs on that list. So on 27 June 2007, in all timezones, we'll be meeting in #ubuntu-devel on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu QA team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuQA If you're interested in helping, please stop by. And feel free to ask shawarma, dendrobates, bdmurray, heno the rest of the team for ways to help out. Hope to see you there and your name on the list of bug huggers! -- 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 mpt at canonical.com Sat Jun 23 05:36:15 2007 From: mpt at canonical.com (Matthew Paul Thomas) Date: Sat, 23 Jun 2007 17:36:15 +1200 Subject: changing descriptions, upstream bug-handling In-Reply-To: <511f47f50706212332m78ddae3t48dbd533100a2ef5@mail.gmail.com> References: <511f47f50706212332m78ddae3t48dbd533100a2ef5@mail.gmail.com> Message-ID: <7361b12dbe89fb8dc393630f3b8a034d@canonical.com> On Jun 22, 2007, at 6:32 PM, shirish wrote: > ... > A. I had set up a bug-report > https://bugs.launchpad.net/debian/+source/deluge-torrent/+bug/119995 > which was subsequently changed by somebody named Marco Rodrigues & is > something very different than what I had reported. Now there is no way > I or anyone can perceive . There is a very small/thin description > called view the original description. What should be a better way is > to somehow tag it to the person who made the changes , something like > > Bug Description : Details > Changed/updated by : person who updated the bug description > Original Description : Name of person who originally filed the bug > View Original Description (hotlink) > ... Something similar will be done when the BugHistory specification is implemented. Cheers -- Matthew Paul Thomas http://mpt.net.nz/ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From daniel_gruen at web.de Sat Jun 23 23:19:19 2007 From: daniel_gruen at web.de (Daniel Gruen) Date: Sun, 24 Jun 2007 01:19:19 +0200 Subject: #111735, patch Message-ID: <200706240119.19390.daniel_gruen@web.de> Hi there, this is my first post on this list and my first patch ever... I read one should by some means announce patches to a developer. After hanging around on empty irc channel #ubuntu-bugs for a while (a rather long while, actually) and #ubuntu-motu and searching the website for some other contact information, I have the faint hope that this list is a) read by human beings who b) do know how to further make use of the patch. The patch is appended to https://bugs.launchpad.net/ubuntu/+source/svnmailer/+bug/111735 as it was used in Mandriva. Patching this to /usr/share/python-support/svnmailer/svnmailer/notifier/_base.py did the job for me. Greetings Daniel P.S.: It'd be quite good if some people were actually available on #ubuntu-bugs as it's promoted everywhere. Or otherwise, that something else be promoted. It took maybe half an hour to find&apply the patch, while I've been searching around some hours to find here. Just for your information & more than that amusement: I first posted this message on bughelper; From michael at vorlon.ping.de Sun Jun 24 00:27:27 2007 From: michael at vorlon.ping.de (Michael Bienia) Date: Sun, 24 Jun 2007 02:27:27 +0200 Subject: #111735, patch In-Reply-To: <200706240119.19390.daniel_gruen@web.de> References: <200706240119.19390.daniel_gruen@web.de> Message-ID: <20070624002727.GA29826@vorlon.ping.de> On 2007-06-24 01:19:19 +0200, Daniel Gruen wrote: Hi, > this is my first post on this list and my first patch ever... I read one > should by some means announce patches to a developer. After hanging around on > empty irc channel #ubuntu-bugs for a while (a rather long while, actually) and > #ubuntu-motu and searching the website for some other contact information, I > have the faint hope that this list is a) read by human beings who b) do know > how to further make use of the patch. Both channels are quiet at some hours but certainly not empty. In #ubuntu-bugs you should have at least seen activity from ubotu. > The patch is appended to > https://bugs.launchpad.net/ubuntu/+source/svnmailer/+bug/111735 as it was > used in Mandriva. Patching this > to /usr/share/python-support/svnmailer/svnmailer/notifier/_base.py did the > job for me. Thanks for providing the patch. I've had a free minute and applied the patch to the svnmailer source and uploaded a fixed package to gutsy. > P.S.: It'd be quite good if some people were actually available on > #ubuntu-bugs as it's promoted everywhere. Or otherwise, that something else > be promoted. It took maybe half an hour to find&apply the patch, while I've > been searching around some hours to find here. Just for your information & > more than that amusement: I first posted this message on bughelper; My IRC client lists nearly 100 users in #ubuntu-bugs (and nearly 150 in #ubuntu-motu). Are you sure you were on Freenode? Regards, Michael From daniel_gruen at web.de Sun Jun 24 13:26:16 2007 From: daniel_gruen at web.de (Daniel Gruen) Date: Sun, 24 Jun 2007 15:26:16 +0200 Subject: #111735, patch In-Reply-To: <20070624002727.GA29826@vorlon.ping.de> References: <200706240119.19390.daniel_gruen@web.de> <20070624002727.GA29826@vorlon.ping.de> Message-ID: <200706241526.16877.daniel_gruen@web.de> On Sunday 24 June 2007 02:27:27 Michael Bienia wrote: > On 2007-06-24 01:19:19 +0200, Daniel Gruen wrote: > Hi, > > > this is my first post on this list and my first patch ever... I read one > > should by some means announce patches to a developer. After hanging > > around on empty irc channel #ubuntu-bugs for a while (a rather long > > while, actually) and #ubuntu-motu and searching the website for some > > other contact information, I have the faint hope that this list is a) > > read by human beings who b) do know how to further make use of the patch. > > Both channels are quiet at some hours but certainly not empty. In > #ubuntu-bugs you should have at least seen activity from ubotu. > [...] > My IRC client lists nearly 100 users in #ubuntu-bugs (and nearly 150 in > #ubuntu-motu). Are you sure you were on Freenode? Hi there, thank you for applying the patch so quickly. I found kopete had used irc.debian.org as a freenode server. As debian has stopped participating in the freenode network some time ago (http://debcentral.org/modules/news/article.php?storyid=486) this was the reason for my lonesome hours on IRC... Anyway, keep the good work up... maybe I'll post another patch concerning the kopete irc server list soon ;) Greetings Daniel From shirishag75 at gmail.com Thu Jun 28 03:30:24 2007 From: shirishag75 at gmail.com (shirish) Date: Thu, 28 Jun 2007 09:00:24 +0530 Subject: a tale of a bug & stuff. Message-ID: <511f47f50706272030y5916019ev508284ba4c32f3b1@mail.gmail.com> Hi all, I had been recently reading about people happy, unhappy about the new incomplete tag which was introduced and while frankly it suits me either way afa it gets the job done something seems to be amiss as far as the bugs themselves are concerned. For e.g. look at https://bugs.launchpad.net/ubuntu/+source/exaile/+bug/122661 now the 3rd comment is pretty interesting . Seb is a good MOTU (used lot of his packages :) ) & I am sure he means well. I checked the version of exaile & for feisty it tops out at 0.2.8+debian-1ubuntu2 while for gutsy its right now at 0.2.9+debian-4ubuntu2 so should one install the ones for feisty or for the ones of gutsy? I checked out martin ddebs repository http://people.ubuntu.com/~pitti/ddebs/dists/ and the last entry is of 31st May 2007. There have been no updates since. also re-checked the gutsy schedule & found out that it was on 7th June so it seems that it is un-related to that. So now I'm stuck with not-knowing what to do? And this is not just related to that one specific bug but basically bugs on gutsy. Should or should not the bugs be reported now, apport was opened in the last updates which resulted in lot of the bugs in /var/crash being reported. Another question , using again the example of https://bugs.launchpad.net/ubuntu/+source/exaile/+bug/122661 (I sure love my exaile ;) ) , the heading "exaile.py crashed with SIGSEGV" now this is a standard or an often-repeated sentence when it crashes, now while I do not want to do duplication (either I reported or somebody else reported the same bug) how do I find out things like application version, architecture version (maybe its important in some bugs not in others, dunno) Lastly, the hardware crash database, dunno what you guys think of it, for me its simply this, if there was a way to browse the database, I as a user or prospective user of a device could shoot a mail to couple of people who have the same device asking them if it works with their ubuntu or whatever derivative they follow or if they did some tweak to enable it do better do its stuff. So special interest groups on the hardware front should be good. From a security perspective the only issue I see is some closed source group (hint :) ) trying to vandalize or bring the server down or something but overall it should be good for the users. We could even have some tags like ( mail or do not mail kinda thing with do not mail me kinda being the standard) Sorry for the big post but these points have been in my mind for last several days & even talking to some of the hackers/developers haven't found a good resolution. Comments, suggestions, flames all welcome :) -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From shirishag75 at gmail.com Thu Jun 28 04:51:07 2007 From: shirishag75 at gmail.com (shirish) Date: Thu, 28 Jun 2007 10:21:07 +0530 Subject: a tale of a bug & stuff Message-ID: <511f47f50706272151x417a959ak28e6144260252a4b@mail.gmail.com> Hi all, Please ignore the 1st paragraph. It seems the repository is updated, just the documentation needs to be updated to reflect the new reality. Would be doing the same. The other points remain the same. -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From shirishag75 at gmail.com Fri Jun 29 19:53:08 2007 From: shirishag75 at gmail.com (shirish) Date: Sat, 30 Jun 2007 01:23:08 +0530 Subject: martin's apport test stuff & simple bug triaging Message-ID: <511f47f50706291253qfc01a9bjc2f4404b0a35fd9e@mail.gmail.com> Hi all, First of all it was really cool to see Martin Pitt making some tests for apport ( really cool) and then asking/telling people to run them so he sees how things pan out in the real world. https://bugs.launchpad.net/ubuntu/+source/apport/+bug/122688/ an off-shoot of this which gave him some clues which lead to :- https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/74691 Now its really cool that martin made those tests even without finding the GNU debugger issue on i386 kernel. In fact I would love to do more tests like that as it helped him & makes me love apport even more :) (although its his baby) The other thing which I found is if I as a user give a call , then I'm open to simple bug confirmation sometimes it pays off. For e.g. Jerome asked me to see if two games slune & balazar I'm able to launch & if not report them to the respective bug-reports (and gave bug report nos.) or file anew subscribing him. While this might be a one-off event but there are probably quite a few of these one-off events where one needs to download & install & launch or launch and do couple of steps. Typically when you ask people on the channel you are given something like this :- https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&search=Search&field.status%3Alist=New&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Incomplete&field.status%3Alist=Fix+Committed&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=&start=4575 which makes most of users like me very afraid as we don't know which we will be capable of or not. Although I might not have the right words or the right answer here are couple of things which I feel might make the procedure better/cool. 1. Have a filter by distribution and/or releases. So let's say I wanna have an overview of all bugs filed after gutsy tribe 1 onwards . Right now thats very hard to know, the filter should work while filing the bug so it makes easier. 2. perhaps have a gutsy-users or something like that on freenode so people can do simple bug triaging like I did with jerome or something close to that so the guys can work on more confirmed bugs. As always comments, suggstions, flames all are welcome. -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From shirishag75 at gmail.com Sat Jun 30 11:12:48 2007 From: shirishag75 at gmail.com (shirish) Date: Sat, 30 Jun 2007 16:42:48 +0530 Subject: gstreamer0.8|0.10-swfdec in launchpad Message-ID: <511f47f50706300412t2fbc57a3rbaf416b22a5c30d4@mail.gmail.com> Hi all, i would like to know what is gonna happen to gstreamer0.8-swfdec package. There is no overview of it in launchpad, while the package is there in http://packages.ubuntu.com/gutsy/libs/gstreamer0.8-swfdec , Similarly are there plans for having a gstreamer0.10-swfdec using swfdec0.4 shirish at ubuntu:~$ aptitude show gstreamer0.8-swfdec Package: gstreamer0.8-swfdec New: yes State: not installed Version: 0.8.12-6ubuntu3 Priority: optional Section: universe/libs Maintainer: Ubuntu MOTU Developers Uncompressed Size: 102k Depends: libc6 (>= 2.5-0ubuntu1), libglib2.0-0 (>= 2.12.9), libgstreamer0.8-0 (>= 0.8.11), liboil0.3 (>= 0.3.8), libswfdec0.3 (>= 0.3.6), libxml2 (>= 2.6.27) Description: SWF (Macromedia Flash) decoder plugin for GStreamer This GStreamer plugin enables the decoding of SWF (Macromedia Flash) animations. The plugin is based on libswfdec. http://swfdec.sourceforge.net/ Thank you, Cheers :) -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From hobbsee at kubuntu.org Sat Jun 30 11:58:53 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Sat, 30 Jun 2007 21:58:53 +1000 Subject: gstreamer0.8|0.10-swfdec in launchpad In-Reply-To: <511f47f50706300412t2fbc57a3rbaf416b22a5c30d4@mail.gmail.com> References: <511f47f50706300412t2fbc57a3rbaf416b22a5c30d4@mail.gmail.com> Message-ID: <4686457D.5070309@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 https://launchpad.net/ubuntu/+source/gst-plugins0.8 Launchpad goes by source, not binary. Hobbsee shirish wrote: > Hi all, > i would like to know what is gonna happen to > gstreamer0.8-swfdec package. There is no overview of it in launchpad, > while the package is there in > http://packages.ubuntu.com/gutsy/libs/gstreamer0.8-swfdec , Similarly > are there plans for having a gstreamer0.10-swfdec using swfdec0.4 > > shirish at ubuntu:~$ aptitude show gstreamer0.8-swfdec > Package: gstreamer0.8-swfdec > New: yes > State: not installed > Version: 0.8.12-6ubuntu3 > Priority: optional > Section: universe/libs > Maintainer: Ubuntu MOTU Developers > Uncompressed Size: 102k > Depends: libc6 (>= 2.5-0ubuntu1), libglib2.0-0 (>= 2.12.9), > libgstreamer0.8-0 (>= 0.8.11), liboil0.3 (>= 0.3.8), > libswfdec0.3 (>= 0.3.6), libxml2 (>= 2.6.27) > Description: SWF (Macromedia Flash) decoder plugin for GStreamer > This GStreamer plugin enables the decoding of SWF (Macromedia Flash) > animations. The plugin is based on > libswfdec. > > http://swfdec.sourceforge.net/ > > Thank you, > > Cheers :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGhkV97/o1b30rzoURAt11AJsGJaAfVM9pgG2a7rf4uZ3zpij0fwCgurEr 2mXW1iexrubdb9B6jwQhYbc= =Uvui -----END PGP SIGNATURE----- From hobbsee at kubuntu.org Sat Jun 30 12:00:51 2007 From: hobbsee at kubuntu.org (Sarah Hobbs) Date: Sat, 30 Jun 2007 22:00:51 +1000 Subject: gstreamer0.8|0.10-swfdec in launchpad In-Reply-To: <4686457D.5070309@kubuntu.org> References: <511f47f50706300412t2fbc57a3rbaf416b22a5c30d4@mail.gmail.com> <4686457D.5070309@kubuntu.org> Message-ID: <468645F3.1060503@kubuntu.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To get the source packages, use... sarah at LongPointyStick:~$ apt-cache madison gstreamer0.8-swfdec gstreamer0.8-swfdec | 0.8.12-6ubuntu3 | http://mirror.pacific.net.au gutsy/universe Packages gstreamer0.8-swfdec | 0.8.12-6ubuntu3 | http://archive.ubuntu.com gutsy/universe Packages gst-plugins0.8 | 0.8.12-6ubuntu3 | http://mirror.pacific.net.au gutsy/universe Sources gst-plugins0.8 | 0.8.12-6ubuntu3 | http://archive.ubuntu.com gutsy/universe Sources (and was it necessary to send it to so many lists?) Hobbsee Sarah Hobbs wrote: > https://launchpad.net/ubuntu/+source/gst-plugins0.8 > > Launchpad goes by source, not binary. > > Hobbsee > > shirish wrote: >> Hi all, >> i would like to know what is gonna happen to >> gstreamer0.8-swfdec package. There is no overview of it in launchpad, >> while the package is there in >> http://packages.ubuntu.com/gutsy/libs/gstreamer0.8-swfdec , Similarly >> are there plans for having a gstreamer0.10-swfdec using swfdec0.4 > >> shirish at ubuntu:~$ aptitude show gstreamer0.8-swfdec >> Package: gstreamer0.8-swfdec >> New: yes >> State: not installed >> Version: 0.8.12-6ubuntu3 >> Priority: optional >> Section: universe/libs >> Maintainer: Ubuntu MOTU Developers >> Uncompressed Size: 102k >> Depends: libc6 (>= 2.5-0ubuntu1), libglib2.0-0 (>= 2.12.9), >> libgstreamer0.8-0 (>= 0.8.11), liboil0.3 (>= 0.3.8), >> libswfdec0.3 (>= 0.3.6), libxml2 (>= 2.6.27) >> Description: SWF (Macromedia Flash) decoder plugin for GStreamer >> This GStreamer plugin enables the decoding of SWF (Macromedia Flash) >> animations. The plugin is based on >> libswfdec. > >> http://swfdec.sourceforge.net/ > >> Thank you, > >> Cheers :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGhkXz7/o1b30rzoURAv1AAKCWYbBMYW30aLN0RmY6kVUtpDQ80QCgp+fE DnQLOqHFBLMSfQ0gHM0/6qQ= =9173 -----END PGP SIGNATURE----- From shirishag75 at gmail.com Sat Jun 30 13:59:31 2007 From: shirishag75 at gmail.com (shirish) Date: Sat, 30 Jun 2007 19:29:31 +0530 Subject: gstreamer0.8|0.10-swfdec in launchpad In-Reply-To: <468645F3.1060503@kubuntu.org> References: <511f47f50706300412t2fbc57a3rbaf416b22a5c30d4@mail.gmail.com> <4686457D.5070309@kubuntu.org> <468645F3.1060503@kubuntu.org> Message-ID: <511f47f50706300659i1bb1442te1d1de42d95a5c8@mail.gmail.com> On 6/30/07, Sarah Hobbs wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > To get the source packages, use... > > sarah at LongPointyStick:~$ apt-cache madison gstreamer0.8-swfdec > gstreamer0.8-swfdec | 0.8.12-6ubuntu3 | http://mirror.pacific.net.au > gutsy/universe Packages > gstreamer0.8-swfdec | 0.8.12-6ubuntu3 | http://archive.ubuntu.com > gutsy/universe Packages > gst-plugins0.8 | 0.8.12-6ubuntu3 | http://mirror.pacific.net.au > gutsy/universe Sources > gst-plugins0.8 | 0.8.12-6ubuntu3 | http://archive.ubuntu.com > gutsy/universe Sources > > (and was it necessary to send it to so many lists?) > > Hobbsee > > Sarah Hobbs wrote: > > https://launchpad.net/ubuntu/+source/gst-plugins0.8 > > > > Launchpad goes by source, not binary. Hi Sarah, First of all thanx for giving that info. While I knew both the things but not the inter-relationship (sort of) I might have to play a while with them to understand the thing. As far as writing to all the lists are concerned, I thought launchpad-users was needed as it might have been an oversight somewhere. I also sent the same to Ubuntu-devel-discuss as well as bug-squad for well its sad to see that quite a lot of plugins are in gstreamer0.10 & wondered why swfdec 0.4 i.e. something like gstreamer0.10-swfdec isn't there for gutsy. I also searched for swfdec-mozilla and while there is library of swfdec but no binaries. I'm looking for something to view flash on firefox-granparadiso & there just seems to be no solution. Only gnash 0.8 is there http://ubuntuforums.org/showthread.php?p=2910921#post2910921 and I had issues with firefox 2.0.0.4 in that. Would try again with firefox-granparadiso & see if its any better though. If I understand correctly, swfdec-mozilla would be for viewing streaming flash in the browser, while the gst-plugins would be for the applications like Mplayer etc. I also looked at swfdec-mozilla which is being maintained by david schleef but fail to get any more info. as to what is happening on that front. apt-cache madison swfdec-mozilla swfdec-mozilla | 0.4.3-2 | http://in.archive.ubuntu.com gutsy/universe Sources The universe source was uploaded on 3rd May & nothing after that :( no binary :( https://launchpad.net/ubuntu/+source/swfdec-mozilla If you or somebody can find some more info. as to the status of either or both these packages as to what is blocking them or some kind of an ETA it would be nice. I would love to test & use both of them as & when they become available. Sorry for taking your time & this long mail. -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 From brian at ubuntu.com Sat Jun 30 15:57:12 2007 From: brian at ubuntu.com (Brian Murray) Date: Sat, 30 Jun 2007 08:57:12 -0700 Subject: Ubuntu Hug Day: 05 July 2007 Message-ID: <20070630155712.GL11196@murraytwins.com> I'm happy to announce our next Hug Day on Thursday, July 5th. The date is different due to the distro team sprint the week of July 11th and a US holiday on July 4th. Ben Collins from the server team has agreed to devote his day to helping out and providing guidance regarding kernel bugs. The event will be held in #ubuntu-devel again. There will also be a wiki page with bugs in specific categories to work on. There is even a place for you to add your name after meeting the goal for a bug! https://wiki.ubuntu.com/UbuntuBugDay/20070705 This list will be finalized shortly before the start of the 5th to ensure that all the bugs on it still need attention. Our goal is to deal with all of the bugs on that list. So on 05 July 2007, in all timezones, we'll be meeting in #ubuntu-devel on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu QA team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuQA If you're interested in helping, please stop by. And feel free to ask bdmurray, BenC, and dholbach the rest of the team for ways to help out. Hope to see you there and your name on the list of bug triagers! -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From k.nielsen81 at gmail.com Sat Jun 30 19:42:55 2007 From: k.nielsen81 at gmail.com (Kenneth Nielsen) Date: Sat, 30 Jun 2007 21:42:55 +0200 Subject: Regarding the wiki page: FindRightPackage Message-ID: Hello I think this page[1] will do a very good job to help people file bugs correctly. But I was wondering would anybody (someone with some more bug experience than myself) mind adding a section about how to handle localizations bugs, because that seems to give people some trouble sometimes as well. Regards Kenneth Nielsen 1: https://wiki.ubuntu.com/Bugs/FindRightPackage -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcbarnes at artsci.wustl.edu Sat Jun 30 23:22:53 2007 From: bcbarnes at artsci.wustl.edu (Brian Barnes) Date: Sat, 30 Jun 2007 18:22:53 -0500 (CDT) Subject: apple macbook / macbook pro bug triage? Message-ID: Hello, I was looking at the list of ubuntu bugs for macbook in launchpad, and I see 135 results when searching for "macbook". Most of these results are "undecided" or "new" (or both). Some of those are quite old. I'm considering buying a macbook pro (santa rosa version), and I'm wondering... 1. Is the macbook bug triage situation representative similar to those for, say, thinkpads? I notice Thinkpads have more bugs listed, but also I think a higher percent are confirmed instead of undecided/new. There are also many known bugs with the new MBPs that are not listed in launchpad, but detailed at ubuntuforums.org. 2. If I joined the bugsquad, what is the policy on triaging bugs that you submit yourself? I mean, if you submit a full bug report in accordance with the ubuntu debuggingprocedures wiki, and nobody responds for a week or more, can you just confirm your own bug? 2(a) - if the answer to #2 is no, how does one go about pinging a particular bug to get attention towards it? Anyway, thank you for reading this. It seems like with the tens of thousands of reported bugs, the bugsquad has a lot of work on its hands. Launchpad looks like a really good tool for the job. I kinda wish that the developement of ubuntu would skip a cycle just so you all had a fair chance to catch up on everything :) I want you to know that end users like me really appreciate the volunteer effort put in by bugsquad members into the QA process. You make a difference. sincerely, Brian wishing to be running ubuntu on a new macbook pro