Hey, folks. So I notice lots of people are eager to test big updates like the new GNOME update before they hit updates-testing, but this can be tricky to do correctly, and sometimes people file negative karma when in fact the problem was not in the update. So, in case it helps anyone, here's the process I use for this kind of thing: I have a local yum repo called 'side'. It lives in ~/local/repo , with x86_64 and i686 subdirs. The repo is set up for yum via the file /etc/yum.repos.d/side.repo, which looks like this: [side] name=Private side repo baseurl=file:///home/adamw/local/repo/$basearch enabled=1 metadata_expire=30 gpgcheck=0 when I want to test a big update, I go to the Bodhi page, and open the Koji page for each build in the update in a separate tab. At the top left corner of each Koji page is the Koji build ID. In a console, I go to ~/local/repo/x86_64 , and type: for i in then I copy and paste each build ID into the command - double-click to select, middle-click in the console window to paste (you don't need to activate the window first - saves time!), hit space after pasting - till I've pasted in all the build IDs, and it looks something like this: for i in 262327 262094 262083 262084 262079 262331 262531 262343 262344 262329 262421 262524 262426 262334 262383 261792 262248 262301 262335 262136 262159 262420 262377 262545 262291 262381 262250 262146 262336 262475 262294 262085 262424 262321 262102 262370 262281 262322 262355 262382 262139 262373 262307 262530 262352 262345 262348 262349 262341 262440 262439 then complete the command: for i in 262327 262094 262083 262084 262079 262331 262531 262343 262344 262329 262421 262524 262426 262334 262383 261792 262248 262301 262335 262136 262159 262420 262377 262545 262291 262381 262250 262146 262336 262475 262294 262085 262424 262321 262102 262370 262281 262322 262355 262382 262139 262373 262307 262530 262352 262345 262348 262349 262341 262440 262439; do koji download-build --arch=x86_64 --arch=noarch $i; done so it iterates over every Koji build that's part of the update, and downloads the x86_64 and noarch binary packages. Obviously, if you're on 32-bit Fedora, you'd adjust the directory and --arch parameters appropriately. Then: createrepo . then do a 'yum update' (the very low metadata_expire value in the yum repo definition file ensures it will get all the new packages). This is a pretty reliable way to make sure the update process has all the right packages available and runs as it should do, and it's quite easy to do, and keeps everything in sync with yum history and so on. Every so often I blow the side repo away to make sure I'm not inadvertently using an update which got reverted or something. Obviously it could be improved if there were an easier way to extract the list of koji build IDs that form part of any given Bodhi update, maybe someone could write a dumb script for that, or something. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
