Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#8034 - [ v3.0.5 ] FTP login problem

Attached to Project: Pacman
Opened by greg (moise7864) - Sunday, 16 September 2007, 21:41 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 18 September 2007, 08:23 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture i686
Severity Critical
Priority Normal
Reported Version 3.0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

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
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Tuesday, 18 September 2007, 08:23 GMT
Reason for closing:  Not a bug
Additional comments about closing:  problems of belnet.de
Comment by Aaron Griffin (phrakture) - Monday, 17 September 2007, 15:47 GMT
Is this the only mirror this happens with?

Can you verify that you can browse to those files via a web/ftp browser? It is possible that the mirror is wildly out of sync.

Loading...