FS#6722 - 'Directory not found' after install pacman 3.0.0-1

Attached to Project: Pacman
Opened by Anarconda (Anarconda) - Tuesday, 27 March 2007, 13:30 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 29 March 2007, 02:22 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'm using pacman 3-rc2-x86_64 after Varun Acharya send this link: https://www.archlinux.org/~ganja_guru/pacman-3.0.0-rc2.pkg.tar.gz
to mailing list. No problems at all installing xorg, gnome, others programs related to gnome and updates, all went ok. Yesterday update to pacman 3.0.0-1-x86_64 (even tried compiling source tarball) and I get this messaages:

[root@Gaia Arch]# pacman -Syu
:: Synchronizing package databases...
--15:22:34-- ftp://mir1.archlinuxfr.org/archlinux/current/os/x86_64/current.db.tar.gz/current.db.tar.gz
=> `current.db.tar.gz.part'
Resolviendo mir1.archlinuxfr.org... 88.191.11.232
Connecting to mir1.archlinuxfr.org|88.191.11.232|:21... conectado.
Identificándose como anonymous ... ¡Dentro!
==> SYST ... hecho. ==> PWD ... hecho.
==> TYPE I ... hecho. ==> CWD /archlinux/current/os/x86_64/current.db.tar.gz ...
No existe el directorio `archlinux/current/os/x86_64/current.db.tar.gz'.

"No existe el directorio `archlinux/current/os/x86_64/current.db.tar.gz'." equals to
"Directory not found 'archlinux/current/....."

If you need more information or I can help in any way, please, don't hesitate contact me.

Thank you.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Thursday, 29 March 2007, 03:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  pacman 3.0.0-1 is now in testing for x86_64
Comment by Dan McGee (toofishes) - Tuesday, 27 March 2007, 15:35 GMT
I believe that is an issue we fixed with the testing release of pacman 3.0.0. Is there a reason you are using an external downloader (wget, I believe)? Pacman's internal downloader is much improved as we have switched to libdownload usage. Try commenting your XferCommand line in pacman.conf and running the upgrade again.
Comment by Anarconda (Anarconda) - Tuesday, 27 March 2007, 15:52 GMT
Ok, all is working fine again after commenting XferCommand. There isn't a special reason to use it, I think my mind is still in ancient versions of pacman.

Thank you very much.
Comment by Dan McGee (toofishes) - Tuesday, 27 March 2007, 15:56 GMT
Which version of pacman was installed when that above error occurred? I wasn't clear if it was RC2 or the actual release. However, I could not get it to duplicate your error with the release version.
Comment by Anarconda (Anarconda) - Tuesday, 27 March 2007, 16:10 GMT
With last release (pacman-3.0.0-1-x86-64) even downloading/compiling source tarball. Using rc2 there wasn't any problem.

I can duplicate the error only uncommenting XferCommand line. If I can help you please tell me.
Comment by Dan McGee (toofishes) - Wednesday, 28 March 2007, 02:23 GMT
Paste your XferCommand line. I used the following without issue:
XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
Comment by Anarconda (Anarconda) - Wednesday, 28 March 2007, 06:49 GMT
XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

Except to remove the "#" is same file installed as pacman.conf.pacnew
Comment by Aaron Griffin (phrakture) - Thursday, 29 March 2007, 02:21 GMT
It doesn't appear that pacman-3.0.0-1 is in [testing] for arch64.

I will reassign this to Andy and let him send it where it needs to go.

I know for a fact this bug was fixed, so an official build in testing should fix this.

Loading...