I made a new scratchbox installation. When the SDK install script runs "apt-get update" it fails, because of

Err http://repository.maemo.org fremantle/tools/non-free Packages
401 Unauthorized ....

on some repositories. This is not only the case on freemantle but also on some repositories of diablo.

If I login into scratchbox the same error comes up when I run "apt-get update".


Because I installed scratchbox on top of openSUSE, I also tried the newest maemo VM SDK from http://maemovmware.garage.maemo.org/ under Virtualbox. The same error comes up if I run "apt-get update" there.

Whats the problem? Is this a problem on the Maemo servers?

Yes, as the sdk is a Nokia product, it is behind an export control system.
It seems that the export control is acting up, and denying downloads.

We are looking at it right now.

I can confirm that on retail n900 I have the same - extras repositories are not working at the moment.

Not sure if this helps/relates to the issue you're having or not, but on the SDK virtual image I found that apt was setup to try to use an internal Nokia proxy server, which from the outside world is allowed. Log in to the SDK and check to see if there's a file under /etc/apt/conf.d/ that says something like 99proxy (I don't recall the exact file name as I deleted it to fix the problem). If it's there, move it somewhere else temporarily (never delete until you're sure ;-) ), and try running Apt update again. See the other thread for the same issue:

http://talk.maemo.org/showpost.php?p=367317

I doubt this would be the case on the N900 firmware, but never hurts to have a look and see...

with my retail n900 none of the repositories work.

e: i can download but installation fails. to be more precise.

That's even weirder. If you can download you should be able to install.

If you refresh the catalogues, do you get any errors?

The problem is still there. The thing that makes it strange and hard to pinpoint, is that it is like a lottery, sometimes you get one repository saying 401 and sometimes four. Still looking at it.

92.123.154.27 works, 92.123.154.18 is broken.

Looks like an Akamai problem potentially.

Has anyone figured out how to make the installer contact the correct host? I've been trying to do this by logging into the scratchbox and creating an /etc/hosts, but it just disappears during the install.

edit: it seems that using /etc/hosts with an akamai hostname is a bad idea anyway. the IPs are changing all the time.

The same is for me since yesterday ( did not update for a while ;-) )

That's what happened when I tried to upgrade one lib explicitly


[sbox-FREMANTLE_ARMEL: ~] > apt-get -f install libhildonmm
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
libhildonmm
1 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
273 not fully installed or removed.
Need to get 0B/99.4kB of archives.
After this operation, 77.8kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
libhildonmm
Install these packages without verification [y/N]? y
/scratchbox/tools/bin/sh: line 1: /usr/sbin/dpkg-preconfigure: No such file or d
irectory
(Reading database ... 31576 files and directories currently installed.)
Preparing to replace libhildonmm 2.1.3-0maemo2 (using .../libhildonmm_2.1.5-0mae
mo1_armel.deb) ...
Unpacking replacement libhildonmm ...
dpkg: error processing /var/cache/apt/archives/libhildonmm_2.1.5-0maemo1_armel.d
eb (--unpack):
trying to overwrite `/opt', which is also in package base-files
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libhildonmm_2.1.5-0maemo1_armel.deb
E: Sub-process dpkg returned an error code (1)
[sbox-FREMANTLE_ARMEL: ~] >

Strange.