where to get images? fedoraproject.org downloads super slow

Adam Williamson adamwill at fedoraproject.org
Wed Jul 23 06:58:22 UTC 2014

On Tue, 2014-07-22 at 23:51 -0700, Adam Williamson wrote:
> On Tue, 2014-07-22 at 18:09 -0600, Chris Murphy wrote:
> > I'm stuck.
> > 
> > I need an image with a 3.16rc6 kernel. However all of the images at the Rawhide Dashboard point to kojipkgs.fedoraproject.org and for some reason Lives are estimated to take 5-6 hours. It's been this way for about two weeks, I don't know why.
> > 
> > e.g.
> > https://kojipkgs.fedoraproject.org/work/tasks/7123/7177123/Fedora-Live-KDE-x86_64-rawhide-20140722.iso
> > 
> > Is there a mirror for this image?
> Koji nightlies aren't mirrored anywhere so far as I'm aware, no.
> > Last week nirik suggested I try boot.iso from
> > http://download-ib02.fedoraproject.org/pub/fedora/linux/development/21/x86_64/os/ which downloaded in about 2 minutes, so that's working fast. But today, no images there. Also due to an anaconda bug, rescue mode isn't working, and I need two shells to do some kernel troubleshooting. Due to the bug, I only get one shell. So I'm stuck.
> That's also an automatic build; basically when the tree gets generated
> nightly a boot.iso will show up if the image compose process succeeds,
> and if not...not. So really all you can do is wait a day and hope. Or
> you can check the Rawhide tree and see if that one succeeded.
> Sorry, I know it's not the answer you were looking for, but it's what
> we've got: those really are the only daily automatically generated
> images, and the Koji-built lives aren't mirrored.

One option I'd suggest is that it really isn't that difficult to build
your own lives, I do it all the time; you can just keep the environment
lying around and pull the compose command out of your command history
whenever you need it. 'Fire off a live image' is a pretty common task
for me.

I have a ~/local/live dir with spin-kickstarts.git checked out beneath
it, and tmp/ and cache/ subdirs for...temporary files and cache,
respectively. I have a few kickstart files in there with various
different tweaks, the one I use most often is called 'live_bleed.ks' and
looks like this:

%include spin-kickstarts/fedora-live-workstation.ks

repo --name=fedora --baseurl=http://dl.fedoraproject.org/pub/fedora/linux/development/$releasever/$basearch/os/
repo --name=side --baseurl=file:///home/adamw/local/repo2/$basearch
repo --name=bleed --baseurl=http://kojipkgs.fedoraproject.org/mash/bleed/$basearch

'bleed' is the side repo releng uses to pull in release blocker and
freeze exception fixes (so right now it's empty, but it's useful to have
it enabled during TC/RC periods if you want your builds to include all
the stuff that's going into the TCs/RCs). 'side' is a local repo into
which I can stuff anything I want to test in the live image - for
instance, you could stick the kernel build you want into it to make sure
it got onto the image. Then I just fire off (as root):

livecd-creator -v --releasever=21 --tmpdir=/home/adamw/local/live/tmp/ --cache=/home/adamw/local/live/cache/ -f 20140722-desktop-aw live_bleed.ks

or something similar, and off it goes. Downloaded packages are stored in
the cache dir so they won't get redownloaded every time you build an
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net

More information about the test mailing list