Hello Dustin, Dustin Kirkland [2010-04-02 4:49 -0000]: > In testdrive's /etc/testdriverc file, there's a line that sets the > target release code, for what is to be testdriven: > > $ grep -n "r = .*lucid" /etc/testdriverc > 60:r = "lucid"
Indeed it might be better to not hardcode this at all. > After Lucid releases, and cdimage starts building whatever lucid+1 > images are called, I'd like to bump this value in the conffile, such > that people can use Lucid to testdrive Lucid+1. > > Can I get this SRU'd easily enough? Yes, if you want to keep the hardcoding for lucid, this makes a trivial SRU. In fact, we already know the next release name, so perhaps you could even upload that into lucid proper. > Or would it be better to build in logic like: > wget -q -O- http://cdimage.ubuntu.com/daily/current/source/MD5SUMS | awk > -F"[^0-9a-zA-Z ]" '{print $2}' I wouldn't use cdimage, but either query launchpad (with launchpadlib, if you use that anyway, or grep https://launchpad.net/ubuntu/+series), or query archive.ubuntu.com (Michael Vogt would know what to check for). Compared to the image rsyncing that testdrive has to do anyway, this extra HTTP call sounds negligible? Do you provide a CLI argument/GUI option to override the "current devel release"? Folks might also want to testdrive an LTS point release, etc. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Improve method to obtain current development release for ISO list generation https://bugs.launchpad.net/bugs/553616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
