Re: Newbie questions
On Fri, 2011-03-11 at 07:06 -0800, Joseph Areeda wrote: Greetings, Howdy! :) I'm just getting used to all the changes in the UI in Natty. I'm using zsync to update the daily iso. Is it necessary [or helpful] to wipe and reinstall the iso every day? I guess since I'm having install issues, I should, but it's a bit of a process. Do you mean wipe the [virtual] machine that you tested the install on? If so, not really -- the install process should do that for you as long as you select 'erase and use the entire disk' during install. If you mean should you delete the ISO file before running zsync, definitely not. zsync will use the file you have and download only the parts that have changed, so you'll download much much less data (and it will go faster). If you delete the ISO first, zsync will have to grab the entire thing. zsync performs tests to be sure you have the correct bits, but you can always check yourself as well. Use 'md5sum' and the published md5sums on cdimage.ubuntu.com in the same directory as the ISO. Once I install an iso, should I do apt-get upgrade or work with the packages on the CD? That depends a bit on what you're testing. If you're testing a particular image (ISO testing) you want to stick with what was installed from the CD. If you're doing general testing, you can do either -- but if you find a bug you'll want to upgrade anyway to make sure it hasn't been fixed since the image was created. What about reporting problems that show up in the logs but not in the UI? Are those worth emails to this list? For example, I'm having trouble with the Update Center so I have to run it from the command line with LD_PRELOAD and in the window I see software-center.apt.aptcache - WARNING - broken packages encountered while getting deps for daily-journal The deps issue is *probably* just an indication that some packages haven't been fully updated in the repository. I wouldn't worry about it unless it persists. Why are you having to run Update Manager with LD_PRELOAD? That one does sound like a bug, but it may be a known one (I haven't checked). As the new guy, I'm a little shy about filing bug reports until I can figure out if it's me or Natty. Is it better to ask or file bugs that turn out to be my inexperience? When in doubt, file the bug. :) It's better to catch things as early as possible, and if it turns out to not be a bug it's generally pretty quick to tell and close it out. Just be sure to search in launchpad before filing a bug to make sure it's not already there. :) I have a lot more questions like these but let's see if this email makes it to the list. Got it here! Thanks for helping! - rm -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Ubuntu-qa Digest, Vol 41, Issue 17
hi all i am onik On 18/03/2011, ubuntu-qa-requ...@lists.ubuntu.com ubuntu-qa-requ...@lists.ubuntu.com wrote: Send Ubuntu-qa mailing list submissions to ubuntu-qa@lists.ubuntu.com To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa or, via email, send a message with subject or body 'help' to ubuntu-qa-requ...@lists.ubuntu.com You can reach the person managing the list at ubuntu-qa-ow...@lists.ubuntu.com When replying, please edit your Subject line so it is more specific than Re: Contents of Ubuntu-qa digest... Today's Topics: 1. Hi Everybody (Jesus) 2. Re: Hi Everybody (Sina) -- Message: 1 Date: Thu, 17 Mar 2011 21:28:44 -0600 From: Jesus jesus.mtz...@gmail.com To: Quality Assurance ubuntu-qa@lists.ubuntu.com Subject: Hi Everybody Message-ID: 4d82d16c.1020...@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi everybody, My name is Jesus and a few years ago I start using Ubuntu and since then I've been trying to collaborate, but maybe I didn't try too hard until now. What I'm expect is help in some way and retrieve some of what I receive from Ubuntu collaborators and volunteers. Finally what I want mostly is learn as much as I can and I really hope that I can be helpful in some way or another. Best Regards Jesus -- Message: 2 Date: Fri, 18 Mar 2011 10:28:50 +0330 From: Sina sina.sabb...@gmail.com To: ubuntu-qa@lists.ubuntu.com Subject: Re: Hi Everybody Message-ID: 4d8302aa.7090...@gmail.com Content-Type: text/plain; charset=ISO-8859-1 On 03/18/2011 06:58 AM, Jesus wrote: Hi everybody, My name is Jesus and a few years ago I start using Ubuntu and since then I've been trying to collaborate, but maybe I didn't try too hard until now. What I'm expect is help in some way and retrieve some of what I receive from Ubuntu collaborators and volunteers. Finally what I want mostly is learn as much as I can and I really hope that I can be helpful in some way or another. Best Regards Jesus Hi Jesus, Welcome to the community. Sina -- -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa End of Ubuntu-qa Digest, Vol 41, Issue 17 * -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Newbie questions
Thank you for the discussion Ronald. I've been experimenting with natty and gaining confidence in a VM with a little dabbling on a new system. I've been working with CUDA apps on Maverick so I will probably participate in the nVidia installation tests If I understand the gist of your comments I'd say: There are so many things to test that using Natty anyway I can is helpful to some extent. To test the installation uses the live CD, to test the packages update regularly, to test the hardware drivers use real hardware. Is that close? Some of my questions weren't clear but your discussion was useful. My first question would have been better phrased Should I start with a live CD install every time?. And the answer is yes, if I'm testing installation procedures. Your question: Why are you having to run Update Manager with LD_PRELOAD? That one does sound like a bug, but it may be a known one (I haven't checked). Yes it is a known bug, that's how I got the work around. Seems to be fixed now, it had to with the order libraries were loaded. I've also been trying to get started with the Bug squad and now have a better feel for when to report something as a bug. I still like to get a crash report request or see it twice before I do but I'm less shy about filing an operator error as a bug. As a newb in qa and bug squad (not development or unix) I have to say my biggest frustration is the proper answer to where do I start?, what do I do now? seems to always be start anywhere you want and do anything you want. Not knowing what I want yet makes that weird. I'm keeping notes with a wiki page in mind for the new guy. Like so much in this business things things seem incomprehensible and overwhelming one minute then trivial and obvious the next. That makes it real hard for those of you who know what you're doing to communicate to those of us who haven't had that AHA moment. You've been a big help. Thanks! Joe On 03/18/2011 05:53 AM, Ronald McCollam wrote: On Fri, 2011-03-11 at 07:06 -0800, Joseph Areeda wrote: Greetings, Howdy! :) I'm just getting used to all the changes in the UI in Natty. I'm using zsync to update the daily iso. Is it necessary [or helpful] to wipe and reinstall the iso every day? I guess since I'm having install issues, I should, but it's a bit of a process. Do you mean wipe the [virtual] machine that you tested the install on? If so, not really -- the install process should do that for you as long as you select 'erase and use the entire disk' during install. If you mean should you delete the ISO file before running zsync, definitely not. zsync will use the file you have and download only the parts that have changed, so you'll download much much less data (and it will go faster). If you delete the ISO first, zsync will have to grab the entire thing. zsync performs tests to be sure you have the correct bits, but you can always check yourself as well. Use 'md5sum' and the published md5sums on cdimage.ubuntu.com in the same directory as the ISO. Once I install an iso, should I do apt-get upgrade or work with the packages on the CD? That depends a bit on what you're testing. If you're testing a particular image (ISO testing) you want to stick with what was installed from the CD. If you're doing general testing, you can do either -- but if you find a bug you'll want to upgrade anyway to make sure it hasn't been fixed since the image was created. What about reporting problems that show up in the logs but not in the UI? Are those worth emails to this list? For example, I'm having trouble with the Update Center so I have to run it from the command line with LD_PRELOAD and in the window I see software-center.apt.aptcache - WARNING - broken packages encountered while getting deps for daily-journal The deps issue is *probably* just an indication that some packages haven't been fully updated in the repository. I wouldn't worry about it unless it persists. Why are you having to run Update Manager with LD_PRELOAD? That one does sound like a bug, but it may be a known one (I haven't checked). As the new guy, I'm a little shy about filing bug reports until I can figure out if it's me or Natty. Is it better to ask or file bugs that turn out to be my inexperience? When in doubt, file the bug. :) It's better to catch things as early as possible, and if it turns out to not be a bug it's generally pretty quick to tell and close it out. Just be sure to search in launchpad before filing a bug to make sure it's not already there. :) I have a lot more questions like these but let's see if this email makes it to the list. Got it here! Thanks for helping! - rm -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Newbie questions
On 03/18/2011 03:49 PM, Joseph Areeda wrote: There are so many things to test that using Natty anyway I can is helpful to some extent. To test the installation uses the live CD, to test the packages update regularly, to test the hardware drivers use real hardware. Is that close? Yep... Also keep in mind that the BIG thing for natty that needs a LOT of testing and bug filing is Unity... Natty itself isn't too much of a departure from Maverick in general terms, but Unity is the BIG thing for Natty and it needs a lot of testing. The second biggest thing is uTouch, but that only works if you have touch devices... I still need to buy a MagicTrackpad to do some touch testing with... but a touch screen netbook or a tablet would be even better :) Unfortunately, to use Unity, you need 3d, so that means either running on bare metal that supports it or running on a VM that includes that support (VirtualBox doesn't without addon stuffs, so getting Unity in a VBox VM requires some extra work). But yeah, you got it figured out ;-) Some of my questions weren't clear but your discussion was useful. My first question would have been better phrased Should I start with a live CD install every time?. And the answer is yes, if I'm testing installation procedures. Yep... Consider this... I do installer testing in VMs and I maintain a local mirror of cdimages.ubuntu.com for doing so. I run Natty on a netbook (Lenovo S-10) and on a Laptop (Thinkpad x201) and keep those up to date with package updates (except when I'm doing something special like my recent Lucid - Maverick - Natty upgrade test). But that's my setup, and I'm weird like that :-) As a newb in qa and bug squad (not development or unix) I have to say my biggest frustration is the proper answer to where do I start?, what do I do now? seems to always be start anywhere you want and do anything you want. Not knowing what I want yet makes that weird. Unfortunately, that is the correct answer. Perhaps there's a better way to address it, but it is what it is... the things I did when I first started mucking about with Linux are certainly not the things you're going to want to do (that was back when you had to compile most drivers on your own, compile your own kernels for everything, and use keyboards carved out of stone using primitive tools). But just go where your interest lies... if you enjoy fixing bugs or writing code, learn to use Launchpad and Bazaar and start contributing code. If you like working with bugs in general, triaging and even testing and filing bugs is a great way to start. ISO test days are always pretty fun if you enjoy doing test cases and trying to break things. And that's just three examples from a QA point of view... You could also help writing translation strings if you speak other languages and want to help make sure Ubuntu is translated properly. I only mention that one because it recently became a little more important to me by happenstance... I'm keeping notes with a wiki page in mind for the new guy. Like so much in this business things things seem incomprehensible and overwhelming one minute then trivial and obvious the next. That makes it real hard for those of you who know what you're doing to communicate to those of us who haven't had that AHA moment. That's cool... but be sure you check around the wiki first as a lot of info may already exist (however, centralizing wiki information is always a good idea, IMO, and I really am NOT a fan of wikis in general). Speaking of which, writing and editing things on the wiki is yet another way to help out if editing and writing is your cup of tea... Welcome to the party! Cheers Jeff -- Jeff Lane - Hardware Certification Engineer and Test Tools Developer Ubuntu Ham: W4KDH Freenode IRC: bladernr or bladernr_ gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417 C466 4ABD 3635 3A14 B2DD -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
