[ubuntu-studio-devel] Testing Team Leader Role in Ubuntu Studio
Hi All, This is a call for assistance with Testing in Ubuntu Studio. I am currently finding it very difficult to put the time I would like into fulfilling the role I took on some time ago, to be the Test Team Lead for Ubuntu Studio. Therefore, I am looking for volunteers to join the team (if not members already), and take over as Test Team Leader after 18.04 (Bionic) LTS is released. There is some information about the team on the wiki here: https://wiki.ubuntu.com/UbuntuStudio/TestingTeamPage There is also a need to be available for release tasks during the times we are working on the next release, or there is an update to an LTS release. Some of the things that need to be done for a release are listed here: https://wiki.ubuntu.com/UbuntuStudio/DevEvents/Release As a summary, the role involves: - Managing the Manual Test Cases at http://packages.qa.ubuntu.com/ - Being the Release Manager at the appropriate points in the test cycle: http://iso.qa.ubuntu.com/ https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule - Announcing the coming tests and encouraging others to take part in the tests. - Triaging bugs found during the test campaigns. - Writing the Release Notes & helping the documentation team with text for the announcements. I still plan to be a member of the team to help out where I can, and to assist the new Test Lead develop into the role. But would like to spend what spare time I have, concentrating on getting more evidence of uploads to Ubuntu for my Developer application. If you would like to help out, please apply to be a member of the testing team on Launchpad (https://launchpad.net/~ubuntustudio-testing), and let us know on the developers list that you would like to volunteer. Lets all chip in to help make the next (and future) Ubuntu Studio releases a success. Regards, Ross Gammon US Test Team Lead signature.asc Description: OpenPGP digital signature -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
AW: RE Re: Ubuntu ISO Testing team: New buildnotification-whyUbuntu-Studio-devel Digest, Vol 56, Issue 2
-Ursprüngliche Nachricht- Von: ubuntu-studio-devel-boun...@lists.ubuntu.com im Auftrag von Luke Kuhn Gesendet: Fr 12/2/2011 19:55 An: ubuntu-studio-devel@lists.ubuntu.com Betreff: Re: RE Re: Ubuntu ISO Testing team: New buildnotification-whyUbuntu-Studio-devel Digest, Vol 56, Issue 2 The function of encrypted disks is twofold. One is that, assuming an "evil maid" multi-visit attack is not the issue, it protects data in the event of a police raid or "burglary." The second is that recovery and failure to penetrate one such encrypted computer deters future raids and "burglaries," on grounds or limited manpower and resources. People don't fish in places where the fish don't bite. Doesn't work all the time, but as part of "defense in depth" it helps a LOT. They sure as hell never made another attempt to get computer information from me. There is a serious privacy concern in Ubuntu, hopefully not in Ubuntustudio by default-Zeitgiest, with so far lacks controls to turn off logging. I remove it, accept that Unity's menus won't work at all, and turn ~/.recently-used.xbel into a directory. This both protects people I give an unencrypted build of the OS I use (because they don't want to be bothered with memorizing a secure passphrase) ands removes a file of great use to a skilled attacker if one finds a way to read it online. The other factors you mention are beyond the scope of a default OS install for the most part. I will now discuss some of the measures that are used with encryption when it is necessary to presume that a national government and not just a local police department is the opposition. One should always prepare as though the most capable adversary they will face will be the opponent. I will now discuss encryption and computer "tradecraft" for this level: CRT monitors should never be use where security is an issue, their RF radiaiton is far too strong. In rural areas where you can control a large space and move back the listening post (LP), RF signals travel a hell of a long way. In urban areas they die really fast-but the LP could literally be on the other side of the wall, so that's a wash. In the US, the codeword for the defense against this mode of attack is "TEMPEST" and a tempested installation is one that is RF shielded, by shielding the room, the installation, or both against RF leakage. In the real world, RF chokes on power and other leads, an LED monitor, a case with NO plastic panels lacking metal backings, and reportedly not using analog VGA cables to the monitor all reduce RF leakage and force the LP to be much closer and more easily detected. I've never heard of a TEMPEST attack beng sucessfully used by the FBI against any activist in the US. If they have it and don't want to admit to it, the data becomes far less useful. ISP and phone snooping is another matter. No connection registered to the user by a real name is safe, no home connection is safe, even wireless broadband with GPS jammed and prepaid with fake personal info could be triangulated and the right house guessed-or ALL houses in the triangulation zone raided in some countries or low density areas. Assume your carrier copies everything you do and keeps it forever. Use SSL for any site that supports it. Presumably intellegence agencies can crack it, but Carnivore cannot, and neither can your ISP. What your ISP cannot read, they cannot pass on to the FBI. the secret police, or whoever. Just using Ubuntu instead of an Adroid or iOS smartphone and using it on the road is a big start, because the latter two OS's have been revealed to often contain commercial spyware alled "CarrierIQ" that reports back URL's visited, etc to the carriers. Once there, the security forces have access to it. Then we can get into MAC address spooking, disposable external USB wifi cards on the hardware side, and site selection on the user side. I would not worry about raw video files being copied over the Internet, that requires more bandwidth than most connections have. I suppose the FBI could order a cable provider to give them a fast connection into someone's system though. Raw photos this might be possible, same for text. Monitor your bandwidth, watch for suspicious activity or processes The "evil maid" boot keylogger attack is harder to implement against Ubuntu than against Truecrypt, as everyone's initramfs is a little different and the attack script will have to generate it locally without access to /etc/initramfs-tools, just the existing initramfs. There are no published reports of any intelligence service using this in the field, if this is an issue keeping /boot on a falsh drige on your physical keyring makes this attack impossible without access to that keyring. The real dangers, assuming you use disk encryption, are this: 1: ANY
Re: RE Re: Ubuntu ISO Testing team: New buildnotification-why Ubuntu-Studio-devel Digest, Vol 56, Issue 2
e to dictionary or publised-writing attacks, widely used by the Secret Service. 4: : Smudges left on touch screens from password entry-this is a known and published from of pass-pattern recovery. 5: Using public access wifi without consideration for the locations of security cameras, or using the same site repeatedly for secure work. 6: Logging into personal email or social networking from any location while doing secure work 7:Browsers that snoop: Chrome or Chromium without turning off the spyware, ANY browser in it's default settings 8: THE WORST OFFENDER: Facebook! Don't use it at all. 9: Google. They keep EVERYTHING, always use Tor and/or the Scroogle anonymizer to reach them > Subject: Re: RE Re: Ubuntu ISO Testing team: New buildnotification-why > encryption support is needed > Message-ID: > Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes > > Note, at least if you are using a CRT, no disc encryption isn't your > biggest issue, since everybody able to use an antenna, is able to see > everything on your screen from the house from the other side of the road. > > "Explicit" anarchistic data has no place on a computer. Encryption is > completely safe. No intelligence service is able to do refactoring of > primes, assumed the encryption avoids pseudo-primes, such as some Fermat > numbers. > > The weak spot is the computer in general, there are several ways to spy, > if a computer is used. > > Anyway, I agree that for states like China, encryption of discs is > important, for western countries we need other methods to be more safe, > assumed the data is explicit-explicit anarchistic. Writing about weed to > e.g. some southern states in the USA, you only need 1024 encryption for > your mails. > > Note, anonymous surfing and mailing isn't safe, if everybody is able to > get access to e.g. your two telephone cables. > > 2 cents, > > Ralf > > -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: RE Re: Ubuntu ISO Testing team: New buildnotification-why encryption support is needed
Note, at least if you are using a CRT, no disc encryption isn't your biggest issue, since everybody able to use an antenna, is able to see everything on your screen from the house from the other side of the road. "Explicit" anarchistic data has no place on a computer. Encryption is completely safe. No intelligence service is able to do refactoring of primes, assumed the encryption avoids pseudo-primes, such as some Fermat numbers. The weak spot is the computer in general, there are several ways to spy, if a computer is used. Anyway, I agree that for states like China, encryption of discs is important, for western countries we need other methods to be more safe, assumed the data is explicit-explicit anarchistic. Writing about weed to e.g. some southern states in the USA, you only need 1024 encryption for your mails. Note, anonymous surfing and mailing isn't safe, if everybody is able to get access to e.g. your two telephone cables. 2 cents, Ralf -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
RE: Ubuntu ISO Testing team: New build > notification-why encryption support is needed
On Wed, November 30, 2011 11:35 am, Luke Kuhn wrote: > > That's ugly, and means where security is a concern people having to > install from Flash drives may have to dd the drive full of random numbers > and remake the installer from the .iso image after installation. I'm not sure what happened. I did a third install (on the same machine) from the same usb stick and was asked the normal questions. I will try to make it happen again. History: First install with all metas. Install failed because of av lib conflicts. Second install less keyboard setup questions... maybe the disk is checked and the fact that it was after a failed install meant it kept some of the data. Install did not include audio-common and so was successful. Third install got all the normal questions (no data remembered from before). Selected both encrypted partition and encrypted home directory. Did not include audio-common as i wanted what I knew worked. I was not testing audio install but encrypted. Install was ok. On boot I was asked for passkey. On home directory read with file manager I was asked for passkey. On shutdown swap was wiped. Tried mounting drive from normal boot. I can see two partitions, the first (1/4gig) had the boot stuff in it (grub, kernel and initrd) The rest must have had the file system and the swap in it. I was unable to access it. When I tried it asked for the passkey but had an error because my normal drive doesn't have the software to deal with it (I wold guess... thats what the err msg seemed to indicate). I don't see that there is any problem installing encrypted version for testing. The nice thing about unencrypted is that I can read and quote from the log file easily if there are failures. I did not use a strong passkey as I just wanted to see if it worked... I wanted something I could remember (equals less secure). My machine speed was not noticeably affected... the desk seemed to run about the same speed. I didn't have any audio stuff in there and this machine doesn't have great audio anyway. So I didn't test tracking lots of tracks. The install was not much longer either just the extra few steps setting up partitions. Not near as bad as waiting for the net connected apt configuration. -- Len Ovens www.OvenWerks.net -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
RE: Re: Re Re: Ubuntu ISO Testing team: New build > notification-why encryption support is needed
That's ugly, and means where security is a concern people having to install from Flash drives may have to dd the drive full of random numbers and remake the installer from the .iso image after installation. We need to make ABSOLUTELY SURE that when the installer is used to create an encrypted partition, or to open an existing encrypted partition, that there is no danger of the passphrase or the LUKS hardware key getting stored somewhere. The only way that would happen on purpose would be deliberate sabotage by someone working for some nation's security services and working on the project, so the code should be vetted by at least two people in countries that do not cooperate with oneanother on "security" matters. Mostly accidental stroage would be looked for, say in something other than a ramdisk used for temporary storage. This would be an issue for Ubuntu as a whole, not for Ubuntustudio or any other derivative unless that part of the installer is changed or someone creates a security-focussed distro. Going to a 750MB installer image for default Ubuntu will certainly complicate that, for Ubuntustudio it's always been a DVD/flash requiring image anyway. Until this is proven safe I suggest installing from DVD's-or from camera cards in card readers with the write-protect slide set to read-only. > Date: Tue, 29 Nov 2011 20:34:19 -0800 > From: "Len Ovens" > To: "Ubuntu Studio Development & Technical Discussion" > > Subject: Re: RE Re: Ubuntu ISO Testing team: New build > notification-whyencryption support is needed > Message-ID: > <1ecacbb7895b4c75d95d1a040a0ec561.squir...@www.ovenwerks.net> > Content-Type: text/plain;charset=iso-8859-1 > There seems to be some info stored from boot to boot on the install disk > if it is writeable. The second time I don't get asked as many keyboard > questions. > > -- > Len Ovens > www.OvenWerks.net > > -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: RE Re: Ubuntu ISO Testing team: New build notification-why encryption support is needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/11/11 04:10, Luke Kuhn wrote: > Yes there is a reason why encryption would be used with ubuntustudio: > Dissident, protest and political opposition media makers. Just to say that I agree with the points Luke makes. Full-disk encryption is essential for a lot of media producers - I would go as far as to suggest that it should be the default for any new installation. This would also give US an edge over some of its rivals, for example the otherwise excellent AVLinux can't/won't install over luks/dmcrypt/lvm2. I've only noticed a performance hit when using massively multitracked ardour sessions (which I now do on an unencrypted partition that gets shredded after mixdown), but for routine use on a modern machine the bottlenecks for data transfer seem to be elsewhere. Keep up the good work everyone - thanks for all of it. Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJO1mh0AAoJECivkG/nESo7DlYP/R2LglaspH9lgvYZv27s4Jdf +EmtnrxwP2hgkuI0RpfH2Wg+wYRoneEdm4ZekBJh1vEWgxIyfOqpTlt/5tWstFFO BoSeMWHretXuQrZ6XqiKeCBXg9D4kvbsT+jG4W/7aVicqhUiwssbNPwRXSOK8NbT Sjk83LylwiwvAQeBtUzR/zDWkouFLVtzGemCnvx1N3C9E9UrAxGLQGfQPgB/hRpu xREgJz23qKMKQhFrap9ikuU4LFthrgK8Nhc2HJJyYShK6v1+VQ1+zqu3Ir7aYqG3 GsozPgCMFs6Va/qiKz4PIkToxo0sdUodl4XkV8ERCtJbitNht1VOpxXPtzL3p3Rx /qhlFdMzmZXcEWD62MyZQ2gbPlXmQfqW5xIO6OLxt8E/mkMasDm44FqbH+FIDSjf GhpbYj5kFM1GVtbeEjUJDUfOEG0cni6IK+YhuvWl1/IYjVXBmA7fHFx6avcgtNKp WvVrWisuRTLwP6KOmLvoHgukzlMOQ6g9zgodJlBQOXMxK6UEK9z6EFIMUMbU0bbi duDomGaNxKmsJimAlwpv+youyc+dOblHprheKvLiZv9WR6aBMhGuCd2JNgQeDQpQ H/8NKG0GOUHKwybfmLBcDtVhF5aDewR3b37mIaJV1KgTkY4Lsus63mfaJIa8UF9n 55vwrWmSI1F8vOXZkeP/ =O703 -END PGP SIGNATURE- -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: RE Re: Ubuntu ISO Testing team: New build notification-why encryption support is needed
On Tue, November 29, 2011 8:10 pm, Luke Kuhn wrote: > > Yes there is a reason why encryption would be used with ubuntustudio: > Dissident, protest and political opposition media makers. I make video and > audio news and opinion media for progressive movements in the US. There > have been grand jury subpeonas (which people like me do NOT comply with) > and police raids on activist media maker's homes. One of those raids in > 2008 stole a computer with Ubuntustudio Hardy from my house-fortunately > one with the media files on an encrypted partition! They never returned > for a second computer or hard drive, other evidence suggests they were > never able to penetrate the encryption. Point taken. I am not as politically active, but, I do see personal freedoms going away at great speed... and perhaps a day in the not too distant future where the whole internet is held together by a non-isp mesh (wireless or otherwise). I will do every other test encrypted... though I think it is only the home directory that the switch turns on. There seems to be some info stored from boot to boot on the install disk if it is writeable. The second time I don't get asked as many keyboard questions. -- Len Ovens www.OvenWerks.net -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
RE Re: Ubuntu ISO Testing team: New build notification-why encryption support is needed
Yes there is a reason why encryption would be used with ubuntustudio: Dissident, protest and political opposition media makers. I make video and audio news and opinion media for progressive movements in the US. There have been grand jury subpeonas (which people like me do NOT comply with) and police raids on activist media maker's homes. One of those raids in 2008 stole a computer with Ubuntustudio Hardy from my house-fortunately one with the media files on an encrypted partition! They never returned for a second computer or hard drive, other evidence suggests they were never able to penetrate the encryption. Other dissidents in other nations have it even worse. In some countries, a dissident media maker with an unencrypted machine could get people killed. In my country he could get someone called before a Grand Jury or arrested and charged with any of a variety of offenses. Therefore, photographic, video, and audio workflows need to be on fully encrypted sytems in my line of work, without every activist media maker having to learn to be a hacker as well, like I had to (but would have anyway). All of my systems are encrypted, for obvious reasons. When I did my 64 bit reinstall from a vanilla Ubuntu disk I had no trouble installing to existing encrypted partitions, but then had to wait over 5 hours for all the media software I use to download over a slow connection. That was followed by hours of custom configuration, all of which a default Ubuntustudio install (like what I started from in Gutsy so long ago) saves typical end users. Due to dangers facing some media makers (even mainstream media in some places) there needs to be as litle deterrent as possible to a new user selecting encryption, otherwise people in positions like my own, setting up for the first time and never having faced a police raid, will say "why bother" until it is too late. I've seen entirely too much of that, and that's what keeps the raids coming. While "anybody" can install Ubuntu, Ubuntustudio or any other distro on encrypted disks themselves, that's not the same as anybody who is simply an end user making media being able to do so. Unfortunately I do not have the Internet bandwidth anywhere (at home of on the road) to routinely download and test entire disk images every few days or I would handle this one myself. I would guess that simply making sure nothing happens to the partitionining or encryption portion of Ubuntu'd default "alternate disk image" should keep this working. Yes, encryption does slow down disks, but with any processor sufficient to handle modern video editing there is plenty to handle encryption. I even got away with root filesystem encryption on an expendable Pentium II laptop I took on an especially hairy out-of-town mission! Also, the newest "sandy bridge"(Intel) and "bulldozer" (AMD) all have the AES-ni instruction set to speed up disk encryption. Haven't tried one of these chips, and I don't know if there are hardware issues with AES-NI that would compromise security either. The only time I see encryption slowing my disks down on my Phenom II X4 video editing machines is when copying a filesystem from one partition of an SSD to another. Then I get about half processor usage as the fast disks push encryption hard. If a RAID is needed for uncompressed HD video or a big multitrack job, I can see this being a problem. If a big enough ramdisk isn't possible and an unencrypted volume has to be used, I would then have to wipe the whole thing afterwards, with zeros after each job, random numbers after any "heavy" job" and making sure the partition is just big enough for the largest projects, so as to force overwriting the space used by previous work and then zeroed out. That's how I treat camera cards, given the lack of encrypted cameras. I can also destroy them if I ever get trapped with a "loaded" camera. As for encryption slowing down a portable laptop with less CPU, laptops are routinely stolen or "stolen" and need encryption the most. A good friend had three stolen in a suspicious "burglary" while guests were in town, good thing they were all encrypted! One last issue-you may ask "why encrypt the binaries?" The answer is that that is the only thing that can write protect them when an attacker mounts the disk from his own live USB stick. It is a lot easier to verify the boot partition with a hash check (there are ways to do this, none of them simple but I use them)than an entire operating system, and there are a lot fewer places in /boot for a keylogger to hide than in the whole operating system. > On Tue, November 29, 2011 8:00 am, qatrac...@stgraber.org wrote: > > A new build of Ubuntu Studio Alternate i386 is ready for testing! > > Version: 2029.1 > > Link: http://91.189.93.73/qatracker/milestones/205/builds/7263/testcases > > > Also, is there any reason to test case two (encrypted disk)? It would seem > to me that this would slow down di
Re: Ubuntu ISO Testing team: New build notification
On Tue, November 29, 2011 5:07 pm, Scott Lavender wrote: > firstly i will mention that i appreciate your conviction on testing :) > that's awesome! It is something I can do as I do other things... hit a key here and there and if it waits for an hour so what. > next, i want to say that i asked the release team to wave our alpha1 > testing milestone because fundamentally the image is almost the same as > the > oneiric image. we haven't really done any engineering lately except one > bug update and the ia32-lib fix so i didn't want to unnecessarily tie up > people's time at this point. Good. The same bug as day one is there when trying to install all the workflows. The same packages: Nov 29 16:08:11 in-target: The following packages have unmet dependencies: Nov 29 16:08:11 in-target: libavcodec-extra-53 : Conflicts: libavcodec53 but 4: 0.7.2-1ubuntu1 is to be installed Nov 29 16:08:11 in-target: libavformat-extra-53 : Conflicts: libavformat53 but 4:0.7.2-1ubuntu1 is to be installed Nov 29 16:08:11 in-target: libavutil-extra-51 : Conflicts: libavutil51 but 4:0.7.2-1ubuntu1 is to be installed Nov 29 16:08:11 in-target: libpostproc-extra-52 : Conflicts: libpostproc52 but 4:0.7.2-1ubuntu1 is to be installed Nov 29 16:08:11 in-target: libswscale-extra-2 : Conflicts: libswscale2 but 4:0.7.2-1ubuntu1 is to be installed Nov 29 16:08:11 in-target: E: Unable to correct problems, you have held broken packages. Nov 29 16:08:11 in-target: tasksel: aptitude failed (100) The problem is that both sets of packages fill the same dependencies. The install disk model is install everything at once and so packages that depend on the normal set include them... I guess the two libs could be black listed in the distro spec... I don't know if that would work. When I install the metas after the first install with synaptic or aptitude they first unistall the old libs anyway. So if we move to a live DVD with an extra installer for the metas the problem will go away... I think. >> Going to the page with instructions for testing shows a proceedure that >> will not work with UStudio. > > > i'll be honest, i'm not sure anyone had really used the test cases that > were linked before for ubuntu studio. perhaps the link was not obvious or > the test cases before were rubbish. you very well might be the first > person in some time to really give them a critical eye. I guess I don't see how else there can be a valid test. I can by those guidelines have either a pass or a fail. A fail is more useful for some things, a pass allows other things to be tested. > you seem very engaged and active, would you like to help or head up the > improvements of the test cases? if so, let me know and we can make this > happen :) I can try... it is not really time yet, as the final install method doesn't seem to be there. In general the install should be all metas chosen at least first run because this points out major fails... like doesn't install. The install method is pretty complete... and I am sure it works for most alt installs. Just a few lines need to be added to say select real time, select all metas etc. I am not sure if it is better to use a net connected install or not. The time difference is significant. (double with net on for me) but the install of prop. fonts has to be skipped without. I did todays test without because I wanted to see if the extra libs were still a problem with as little time input as possible. It failed as above. I may install with net on to test the desktop with no metas installed. The network monitor hasn't worked which is ok for a desktop, but a fail for a portable device like this. I had suggested wicd but I don't like it. network-monitor-gnome is nicer. The other problem I have had is with the usb drive as the dvd. It doesn't mount as /media/cdrom and so aptitude or synaptic can't find it for installing metas later. I had to mount it... remove the cdrom directory and make a link called cdrom to where the usb drive was mounted. I had to park a terminal session with PWD on that drive to keep it mounted and then I could install. I don't know if naming the partition (vfat) to the word cdrom would help or not. > i think this should be fixed now. if you feel like testing it, please do > and let me know how it works. > > for those interested in what happened it was thus: the ia32-libs are > being > transitions to a mult-arch library (this means not having double the > maintenance for 32 and 64 bit) but the germination process during the iso > build was not picking up the dependency for amd64. we were trying to ship > the dssi-vst package which depends on wine which depend on ia32-libs, and > since ia32-libs were not available this mean wine and dssi-vst were not > available. this eventually also broke the meta packages as well. I think that part is fixed. I have been going to aptitude and installing the xubuntu meta with all the depends with xubuntu in them removed (to keep our themes). This gets a mor
Re: Ubuntu ISO Testing team: New build notification
On Tue, Nov 29, 2011 at 5:05 PM, Len Ovens wrote: > > On Tue, November 29, 2011 8:00 am, qatrac...@stgraber.org wrote: > > A new build of Ubuntu Studio Alternate i386 is ready for testing! > > Version: 2029.1 > > Link: http://91.189.93.73/qatracker/milestones/205/builds/7263/testcases > > > > Testcases: > >- Install (auto-resize) > >- Install (entire disk with encryption) > >- Install (entire disk) > >- Install (manual partitioning) i386 > > > > Build notes: > > None > > Going to the page with instructions for testing shows a proceedure that > will not work with UStudio. The instructions assume that once the install > starts everything else will just happen. There is no mention of the jackd > question or the workflow selection or the confirmation of the fonts > licence. or for that matter the network setup. These are all places where > there are more than one install option and where one choice is more likely > to give a failure than another. For example choosing no work flows will > mean the image will install and as far as I know (unless things have > changed) choosing all of them will fail. > > Which way would you like me to test this iso? > > Also, is there any reason to test case two (encrypted disk)? It would seem > to me that this would slow down disk access for things like streaming > multi-tracks. Therefore, if I did test it, I would test it with a graphic > workflow where it might make sense. > > -- > Len Ovens > www.OvenWerks.net > > > -- > Ubuntu-Studio-devel mailing list > Ubuntu-Studio-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel > hi len, firstly i will mention that i appreciate your conviction on testing :) that's awesome! next, i want to say that i asked the release team to wave our alpha1 testing milestone because fundamentally the image is almost the same as the oneiric image. we haven't really done any engineering lately except one bug update and the ia32-lib fix so i didn't want to unnecessarily tie up people's time at this point. this isn't to say that you can't test, just that this one isn't going to be required as a milestone. i'll be sending another email out to the list just about this point. you also bring up some good topics and i'll try to hit them in the order you mention them. Going to the page with instructions for testing shows a proceedure that > will not work with UStudio. i'll be honest, i'm not sure anyone had really used the test cases that were linked before for ubuntu studio. perhaps the link was not obvious or the test cases before were rubbish. you very well might be the first person in some time to really give them a critical eye. The instructions assume that once the install > starts everything else will just happen. There is no mention of the jackd > question or the workflow selection or the confirmation of the fonts > licence. or for that matter the network setup. These are all places where > there are more than one install option and where one choice is more likely > to give a failure than another. you seem very engaged and active, would you like to help or head up the improvements of the test cases? if so, let me know and we can make this happen :) For example choosing no work flows will > mean the image will install and as far as I know (unless things have > changed) choosing all of them will fail. > i think this should be fixed now. if you feel like testing it, please do and let me know how it works. for those interested in what happened it was thus: the ia32-libs are being transitions to a mult-arch library (this means not having double the maintenance for 32 and 64 bit) but the germination process during the iso build was not picking up the dependency for amd64. we were trying to ship the dssi-vst package which depends on wine which depend on ia32-libs, and since ia32-libs were not available this mean wine and dssi-vst were not available. this eventually also broke the meta packages as well. Also, is there any reason to test case two (encrypted disk)? > i believe this had been either removed or moved to an optional test case. perhaps moving to the new qa tracker has elevated this back into a required test erroneously. i'll talk to someone about this. len, thanks again for you efforts and input. it makes a big difference. let me know about helping improve the test cases. also the meta package installation if you get to it. scottl -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Ubuntu ISO Testing team: New build notification
On Tue, November 29, 2011 8:00 am, qatrac...@stgraber.org wrote: > A new build of Ubuntu Studio Alternate i386 is ready for testing! > Version: 2029.1 > Link: http://91.189.93.73/qatracker/milestones/205/builds/7263/testcases > > Testcases: >- Install (auto-resize) >- Install (entire disk with encryption) >- Install (entire disk) >- Install (manual partitioning) i386 > > Build notes: > None Going to the page with instructions for testing shows a proceedure that will not work with UStudio. The instructions assume that once the install starts everything else will just happen. There is no mention of the jackd question or the workflow selection or the confirmation of the fonts licence. or for that matter the network setup. These are all places where there are more than one install option and where one choice is more likely to give a failure than another. For example choosing no work flows will mean the image will install and as far as I know (unless things have changed) choosing all of them will fail. Which way would you like me to test this iso? Also, is there any reason to test case two (encrypted disk)? It would seem to me that this would slow down disk access for things like streaming multi-tracks. Therefore, if I did test it, I would test it with a graphic workflow where it might make sense. -- Len Ovens www.OvenWerks.net -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Ubuntu ISO Testing team: New build notification
A new build of Ubuntu Studio Alternate i386 is ready for testing! Version: 2029.1 Link: http://91.189.93.73/qatracker/milestones/205/builds/7263/testcases Testcases: - Install (auto-resize) - Install (entire disk with encryption) - Install (entire disk) - Install (manual partitioning) i386 Build notes: None -- You are receiving this e-mail because you subscribed to this product on the Ubuntu ISO Testing team testing tracker. You can change your subscription options at: http://91.189.93.73/qatracker/subscription -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Ubuntu ISO Testing team: New build notification
A new build of Ubuntu Studio Alternate amd64 is ready for testing! Version: 2029.1 Link: http://91.189.93.73/qatracker/milestones/205/builds/7262/testcases Testcases: - Install (auto-resize) - Install (entire disk with encryption) - Install (entire disk) - Install (manual partitioning) amd64 Build notes: None -- You are receiving this e-mail because you subscribed to this product on the Ubuntu ISO Testing team testing tracker. You can change your subscription options at: http://91.189.93.73/qatracker/subscription -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Ubuntu ISO Testing team: New build notification
A new build of Ubuntu Studio Alternate amd64 is ready for testing! Version: 2029 Link: http://91.189.93.73/qatracker/milestones/205/builds/7230/testcases Testcases: - Install (auto-resize) - Install (entire disk with encryption) - Install (entire disk) - Install (manual partitioning) amd64 Build notes: None -- You are receiving this e-mail because you subscribed to this product on the Ubuntu ISO Testing team testing tracker. You can change your subscription options at: http://91.189.93.73/qatracker/subscription -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Ubuntu ISO Testing team: New build notification
A new build of Ubuntu Studio Alternate i386 is ready for testing! Version: 2029 Link: http://91.189.93.73/qatracker/milestones/205/builds/7231/testcases Testcases: - Install (auto-resize) - Install (entire disk with encryption) - Install (entire disk) - Install (manual partitioning) i386 Build notes: None -- You are receiving this e-mail because you subscribed to this product on the Ubuntu ISO Testing team testing tracker. You can change your subscription options at: http://91.189.93.73/qatracker/subscription -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Testing Team
Cory suggested on IRC that I write a quick proposal on this and run it by the list, so here goes (please offer any opinion you may have on the matter): I'd like to create an Ubuntu Studio Testers team on Launchpad. The purpose of this team would be to thoroughly test the development version of Ubuntu Studio. This team would help to solve a number of current testing issues/problems, they include but are not limited to: - No/small testing community. We currently only have a user and development community structure. This team would create belonging amongst testers which would likely result in more active testing (I've received a handful of direct e-mails re:testing Ubuntu Studio). People would have to actively remove themselves from the testing group to stop receiving notifications & e-mails, rather than just forgetting about their commitment. - No formal communication channel for testers. Currently testing results are published to the entire ubuntu studio development or users mailing list (inconsistent behavior) - there's no formal policy for how to report test results (other than ISO test results). This team would include a launchpad mailing list that would allow for questions on testing, testing coordination, discussion of test results, and subscription to the ISO build notifier, all without overburdening either the users or dev mailing lists. This would also allow for a larger number of testing requests without annoying our user base. - Lack of organized testing. We currently only have organized ISO testing. This team would be in charge of building a suite of tests for Ubuntu Studio and ensuring that they are met across releases, this includes notifying the developers should the tests fail. I would imagine this team could be used to follow important bugs, create testing scripts, and build wiki documentation on testing the software shipped with Ubuntu Studio. I'd be quite willing to create and lead this team, as well as announce it's creation on the ubuntu studio mailing lists, qa mailing list, and bugsquad mailing list. Essentially I'd like to create a means for Ubuntu Studio testers to work together more effectively. - Eric Hedekar ___ Vice President of Vancouver Pro Musica Society http://www.vancouverpromusica.ca Ubuntu Studio Developer http://www.ubuntustudio.org Web Designer & Audio Artist http://www.erichedekar.com -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
