Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8033 - New pacman seems to have problems

Attached to Project: Arch Linux
Opened by greg (moise7864) - Sunday, 16 September 2007, 21:37 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 18 September 2007, 08:24 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

New pacman seems to have problem with belgian belnet repository.
I've just upgraded pacman and updated my pacman.conf to the core repository.

Since this update pacman log successful 3 times to the ftp but next it doesn't work for 5 minutes

Details:

pacman -Syu
:: Synchronizing package databases...
error: failed retrieving file 'testing.db.tar.gz' from ftp.belnet.be : Not logged in
error: failed to synchronize testing: Not logged in
error: failed retrieving file 'core.db.tar.gz' from ftp.belnet.be : Not logged in
error: failed to synchronize core: Not logged in
error: failed retrieving file 'extra.db.tar.gz' from ftp.belnet.be : Not logged in
error: failed to synchronize extra: Not logged in
error: failed retrieving file 'community.db.tar.gz' from ftp.belnet.be : Not logged in
error: failed to synchronize community: Not logged in
error: failed to synchronize any databases

I wonder if it's not a problem with the repository it self (the ftp server).
Has someone the same issue?


Additional info:
* Pacman v3.0.5 - libalpm v1.0.0



Steps to reproduce:
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Tuesday, 18 September 2007, 08:24 GMT
Reason for closing:  Not a bug
Additional comments about closing:  problems of belnet.be
Comment by greg (moise7864) - Sunday, 16 September 2007, 21:42 GMT
sorry wrong place
Comment by Tobias Powalowski (tpowa) - Monday, 17 September 2007, 05:20 GMT
my strong guess is hte mirror wasn't synced already.
The syncing started yesterday afternoon, it needs mostly a 1 or 2 days to get all mirrors in sync.

Loading...