I can't tell if it's normal to have an empty sources.list at that point, but it should definitely not go into an infinite loop. The "Testing apt sources" sequence uses a temporary file anyway, not /etc/apt/sources.list

Our sources are added at later stages directly into /etc/apt/sources.list

I had the same problem with the new build. So, I took my 28 boot CD, and booted from that (I used a newly created device/activation code), and it says that I am on 29 now (/home/pluto-version). Not sure if that's a good route to go or not...

Hmmm, same problem here....this is my first PlutoHome install so I am not sure which iso I am using (assume latest (29?) as I only downloaded 2 days ago).

I'm sure others have been able to use this iso, wonder what is different with these installs. I can't dowmload again or burn a new disk at present, but will try when I am able. I am using the same hardware I was using for test install of MythTV (Dell GX150) so I am guessing hardware is not the problem.

Here is the link to the .28 iso, and although we do need to find why users are having problems with 29:

flavorstudio.iasi.rdsnet.ro:15080/28.iso

It's on the internet from our inhouse build server (1.5 Mbit) not our production server (100 Mbit), so it might be slower to download. But it was already removed from production.

It's true you can install with any .iso. It checks for the latest version and upgrades on the fly. However, you obviously want to use the latest CD so that it doesn't need to download upgrade packages over the Internet as it installs. Nothing changed on the CD between 29 and 28. It is exactly the same image, only the packages have changed, and the installation scripts should be exactly the same. So if there is a difference, it is completely inadvertent and we need to fix it. But what is particularly bizarre is that so many are having this problem yet when we tested on our in-house systems the 29 CD works fine, and there are also many users for whom 29 works fine as well.

the guy who is responsible for the CD works Monday through Friday nine to five Central European Time (Paris time / GMT+1 / New York + 6). he what I would suggest is that somebody contact us using live chat during those hours, we'll have the programmer call you back by phone, or transfer you via chat and get to the bottom of this.

one change we discussed yesterday that we will implement is adding an md5 checksum for the ISO so we can be sure it downloaded successfully. I suspect the problem is perhaps some of you started downloading the CD when it was 28, and since it's such a big download, when we changed to 29, the download file may have gotten changed underneath you, but youyour browser continued downloading, and I don't think ISO includes a checksum. So if the first half of the images at 28 version in the second half is a 29, I don't think your CD burner will report any problems. And since the filename on our server never change, your web browser wouldn't report problems either. Were going to try to change the naming convention so that we can leave the old ISO image a few days after each release to allow users to continue downloading it.