For the sake of completeness...
These days, running pacman prints connection timeout errors. For example, a few minutes ago:
$ pacman -Syu :: Sincronizzazione dei database in corso... errore: impossibile scaricare il pacchetto 'mingw32.db' da 148.251.42.38 : Connection timed out after 10013 milliseconds mingw32 è aggiornato errore: impossibile scaricare il pacchetto 'mingw64.db' da 148.251.42.38 : Connection timed out after 10010 milliseconds mingw64 è aggiornato errore: impossibile scaricare il pacchetto 'msys.db' da 148.251.42.38 : Connection timed out after 10010 milliseconds msys è aggiornato :: Aggiornamento del sistema in corso... non ci sono aggiornamenti disponibili
I wonder if this is to be expected...
Ciao,
Angelo.
This ftp server will not be available anymore. Used sourceforge mirror.
Hmm.. I haven't changed nothing in my installation if not running 'pacman -Syu', so I don't understand what I have to do.. Please, explain..
TIA,
Angelo.
On initial installation, pacman repository files contain urls pointing to various location on the internet. One of them points to a now unavailable ftp server (at ip 148.251.42.38).
I wrote detailled instructions on github issue #144 about how to remove the offending repository url from pacman configuration files.
Last edit: Matthieu Vachon 2014-12-23
OK, good to hear.. but if that primary server is not valid any more, shouldn't be a pacman upgrade which fixes that? substituting it with a new valid primary server? i.e. upgrading those mirrorlist.* files..
BTW, usually I use this script
to upgrade core packages.. and when a new package enter in the 'core', the script is updated.
Shouldn't MSYS2 come with a similar script? Then one could say: "you have to run update_core first then 'pacman -Syu'..."
Ciao,
Angelo.
The
pacman-mirrors
package was updated.