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!
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!
FS#22136 - [pacman] ftp transport doesn't work and pacman -Sy always syncs ALL repos, even if not needed
Attached to Project:
Arch Linux
Opened by Uli (Army) - Saturday, 18 December 2010, 11:43 GMT
Last edited by Allan McRae (Allan) - Tuesday, 21 December 2010, 03:50 GMT
Opened by Uli (Army) - Saturday, 18 December 2010, 11:43 GMT
Last edited by Allan McRae (Allan) - Tuesday, 21 December 2010, 03:50 GMT
|
DetailsDescription:
Hi, I have two issues with pacman. I'll show you the command lines with the output, you'll see what I mean # pacman -Sy && pacman -Sy :: Synchronizing package databases... testing 6.2K 374.9K/s 00:00:00 [-----------------------------------] 100% core 36.0K 736.2K/s 00:00:00 [-----------------------------------] 100% extra 454.4K 2.8M/s 00:00:00 [-----------------------------------] 100% xyne-any 6.7K 41.4K/s 00:00:00 [-----------------------------------] 100% heftig 0.7K 5.5M/s 00:00:00 [-----------------------------------] 100% community-testing 1.5K 3.5M/s 00:00:00 [-----------------------------------] 100% community 405.3K 3.0M/s 00:00:00 [-----------------------------------] 100% :: Synchronizing package databases... testing 6.2K 475.3K/s 00:00:00 [-----------------------------------] 100% core 36.0K 848.3K/s 00:00:00 [-----------------------------------] 100% extra 454.4K 968.1K/s 00:00:00 [-----------------------------------] 100% xyne-any 6.7K 45.3K/s 00:00:00 [-----------------------------------] 100% heftig 0.7K 2.3M/s 00:00:00 [-----------------------------------] 100% community-testing 1.5K 4.6M/s 00:00:00 [-----------------------------------] 100% community 405.3K 860.3K/s 00:00:00 [-----------------------------------] 100% The repos are up to date, but pacman syncs them all. I can't exactly remember when this started, I guess 4-5 days ago or something like that. The other issue is the not working file transfer via ftp. I usually prefer ftp mirrors. Here's the output # pacman -Sy :: Synchronizing package databases... error: failed retrieving file 'testing.db.tar.gz' from ftp.hosteurope.de : Bad Request error: failed to update testing (Bad Request) error: failed retrieving file 'core.db.tar.gz' from ftp.hosteurope.de : Bad Request error: failed to update core (Bad Request) error: failed retrieving file 'extra.db.tar.gz' from ftp.hosteurope.de : Bad Request error: failed to update extra (Bad Request) xyne-any 6.7K 41.2K/s 00:00:00 [-----------------------------------] 100% heftig 0.7K 5.6M/s 00:00:00 [-----------------------------------] 100% error: failed retrieving file 'community-testing.db.tar.gz' from ftp.hosteurope.de : Bad Request error: failed to update community-testing (Bad Request) error: failed retrieving file 'community.db.tar.gz' from ftp.hosteurope.de : Bad Request error: failed to update community (Bad Request) xyne-any and heftig still work, because these are pure http repos As you can see, I use [testing] in case that's relevant. My system is up to date and I use i686, don't know if this also happens on 64bit. Additional info: * package version(s) # pacman -Qi pacman |grep Version Version : 3.4.1-1 * config and/or log files etc. shown above Steps to reproduce: also shown above |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 21 December 2010, 03:50 GMT
Reason for closing: Not a bug
Additional comments about closing: System configuration issue
Tuesday, 21 December 2010, 03:50 GMT
Reason for closing: Not a bug
Additional comments about closing: System configuration issue
Comment by Uli (Army) -
Tuesday, 21 December 2010, 02:40 GMT
Can be closed, it was caused by a system wide setting of http_proxy=127.0.0.1:8118 which is privoxy on my system. I accidently disallowed the ftp ports, so that couldn't work anymore. That must have caused the other issue as well. Sorry for the noise