You are not logged in.
Howdy!
I've got a problem with updating my system, here's my issue:
---> Using a mirror from the US on top in the /etc/pacman.d/mirrorlist file it will update my packages just fine, slow altho (I live in the Netherlands)
---> Using a mirror from the Netherlands on top in the /etc/pacman.d/mirrorlist file will update aswell, however: it states some packages installed are newer then the one in the repositories.
(I updated from the US mirror)
Now is my question, are the mirrors in the Netherlands/Germany etc slower in updating their package repository? It's kind of annoying, because I want to keep my system up-to-date, but I have to use a slow mirror from the US if I want that.
Thanks in advance!![]()
Last edited by kevin89 (2008-02-01 17:21:33)
Offline
Hmm.. If it is only a few hours late (for example, if the mirror syncs once per day), then that's alright. What's the problem?
You will just get the updates the next day, you won't die from it.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Well, it's not a couple of hours. It's still the same 2 days later...
I was just wondering if that's normal or it's me having a messy config, that's all ![]()
Offline
I have to agree I manually updated amsn
[2008-01-31 11:31] installed amsn (0.97-2)
http://aur.archlinux.org/packages.php?d … s=0&SeB=nd
package updated 28-1 and still on 31 it hadn't met the community mirror.
And today 2/2 that's 5 days surely that's not just me being impatient.
warning: amsn: local (0.97-2) is newer than community (0.97-1)
Not really sure on mirror but these are the top ones I've got.
Server = ftp://mir1.archlinuxfr.org/archlinux/community/os/x86_64
Server = ftp://mir2.archlinuxfr.org/archlinux/community/os/x86_64
Server = http://archlinux.freeside.ru/community/os/x86_64
Server = ftp://ftp.belnet.be/packages/archlinux/community/os/x86_64
Server = ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/community/os/x86_64
Server = ftp://ftp.heanet.ie/mirrors/ftp.archlinux.org/community/os/x86_64Edit checking all those mirrors not one is hosting the latest amsn.
Last edited by FeatherMonkey (2008-02-02 13:18:22)
Offline
FeatherMonkey, belnet syncs more than once a day, if amsn isn't available then there simply isn't an 64bit version yet. It is available for i686 since a couple of hours after it was announced.
Offline
Makes sense thought it was strange I'll try and find the maintainer of 64bit package.
Offline
kevin89 - nluug and surfnet both appear to be significantly out of date. Try hosteurope (Germany) or belnet (Belgium) for the moment - both of them are in sync.
I have sent a mail to info@nluug.nl informing them of the situation, so hopefully they will be able to rectify the problem.
Offline
@tomk
Ah ok, hopefully they will update their repo's soon! Thanks for the information! ![]()
Solved imo ![]()
Offline
The European interface may be affected by the sliced undersea cables (3) and activity must be horrendous in that area due to loss of telephone and internet in other areas of the world.
My ailment? Lackatesla!
Tesla fails smog test..no gas!
Favorite song...Tesla On My Mind....
Online
Makes sense thought it was strange I'll try and find the maintainer of 64bit package.
I just updated the x86_64 amsn package. To know the last time you mirror was updated, check the date of the *.db.tar.gz file. For out-of-sync versions between the i686 and x86_64 repo, check the pkg diff list: http://dev.archlinux.org/~andyrtr/pkg_diff.html
There is no arch specific maintainers of packages. If a x86_64 community package is out of date for too long or if the list of out-of-sync packages gets too long, post a reminder on the AUR ML. You could contact the package maintainer but chances are that if the x86_64 package hasn't been built at the same time as the i686 one, he doesn't have a x86_64 machine (and doesn't use phrakture' 64bit build machine either).
Offline