Hi, when I try to use your source (wich is a great idea BTW) I get a message telling "Package download failed" this only happens with packages from your source. If I use any other source everything works out great, but then again I get that 30 min update every day

Do you know what could be causing this?

Package download failed means the host that is housing that particular package is down, file missing, or its hash doesn't match up with the one listed in the xml. Which package are you having trouble with? Please name the packages that you are having trouble with, and I can manually track down the source that is having trouble and update this.

Well atm not a single repo work, at all, be it through repo.sc or something else.
I also tried the package downloader in WinPWN but same answer there, package download failed...

Is this some sort of a conspiracy??

Might be internet connectivity issue? Are you on Edge with iPhone? If so, try and find a WiFi AP instead... because Edge is always known to be some what slow and unreliable from what I heard (yes, heard, I'm unfortunately suckered into spending more money on my iPod Touch than most people on their iPhone...)

You can also try to start the Installer app via SSH, and then see the exact error that it is encountering... though, that is semi-advanced and I don't have a guide for that written up yet...

All PC's in da house is wired and I've tried installer on three other independent wireless connections.

The true reason for all of this seems to have been an non-updated Installer.
As I removed every source except the apptapp, I also removed community and therefore the ability to update.
It seems extremely odd indeed but hey, it worked.

Now back to that iPSW builder....

Hi,

I'm trying to download SkrewCommon v1.1 and i got the error.
Do you have any idea?

Installer should update itself using AppTapp official source... which shouldn't be removable (unless you hack the plist file). So this is definetly an odd issue... If you are planning to slipstream a bunch of packages, you can use repo.sc/username/xml to get the raw xml file. If that went way over your head... don't worry about it for now

SkrewCommon 1.1 works fine for me here on both computer, and iPod Touch... The file should be located on http://i.danstaface.net/zips/SkrewCommon.zip please try to see if you can access it from a computer on the SAME network your iPod Touch / iPhone is on. If that link doesn't work, then it is a DNS issue with your ISP, if otherwise, then it'd be something up with your iPod Touch / iPhone's Installer...

Oh pwese, if it weren't for the endless lines of codes demanded to get your own repo up, I'd have all of the neccessary packages on my own server.

On to the note of packages, Applerepo.com hosts quite a bit of packages right?
Well, that domain's up for sale with no traces left of any packages.

It'd be very expensive to do that... I'm estimating around 600GB of bandwidth usage each month from doing just the xml's here. Imagine the amount of traffic you'd have to handle with packages themselves and what not... not an amount I'd want to pay for

It's a shame to see applerepo go down yet again... I'm in a mixed state on whether or not to take the packages down just yet... as they've proven to revive themselves after a few weeks time last time around. Also, not all packages are down, just yet. There is one download server which housing a few files, and is still up... so if you use the xml generated from here, you can still have access to them... Though, most people are probably too into the "wow" factor to care (the packages that work are most of the 1.1.1 and 1.1.2 ones). Let's give them a few weeks before actually removing the packages from our database.

On a side note, the new package details page is coming together slowly... I know I said I'll try to push it out by Wednesday or Friday, but because of a resources snag I run into with generating the related packages -- it's some what difficult to siff through over 400K records to find related packages... takes the server a good 1 to 2 seconds to do so for each request -- I'd need to go back and re-design the database a bit, and create a new cache system to help ease off the loads. But once that is created, there'd be a good community flagging option to flag the packages as being down so other people can be aware of it, too.