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.
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.
FS#19969 - pacman download issues from googlecode.com domain
Attached to Project:
Pacman
Opened by Weng Xuetian (csslayer) - Friday, 25 June 2010, 09:55 GMT
Last edited by Allan McRae (Allan) - Friday, 16 July 2010, 03:40 GMT
Opened by Weng Xuetian (csslayer) - Friday, 25 June 2010, 09:55 GMT
Last edited by Allan McRae (Allan) - Friday, 16 July 2010, 03:40 GMT
|
DetailsDescription:
I use google code to create a personal repo, which repo settings is [csslayer-aur-repo] Server=http://csslayer-aur-repo.googlecode.com/files I can use this repo for older pacman, and if I use Xfercommand, like wget to download, it works well. Additional info: pacman 3.4.0 Steps to reproduce: 1. add this repo to pacman.conf 2. -Syu 3. shows 404 not found csslayer-aur-repo.db.tar.gz |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 16 July 2010, 03:40 GMT
Reason for closing: Not a bug
Additional comments about closing: Issue is the server at googlecode.com
Friday, 16 July 2010, 03:40 GMT
Reason for closing: Not a bug
Additional comments about closing: Issue is the server at googlecode.com
http://aur.pastebin.com/3dv6gA22
my pacman.conf
http://aur.pastebin.com/SwwNbwPq
You can see the comment below from http://aur.archlinux.org/packages.php?ID=32598, it also happened to others...
Can you post output of wget -d http://csslayer-aur-repo.googlecode.com/files/csslayer-aur-repo.db.tar.gz ?
And also compile the attached test case with : gcc -o dload dload-db.c -lfetch
Then run ./dload
There are two direct workarounds for this :
1) put an ip that works directly in pacman.conf Server line
2) use /etc/hosts to pick that ip
Anyway this has strictly nothing to do with pacman, and it's good you noticed you could reproduce with wget as well :)
You might want to report the problem to google.
What i wonder is why this problem appeared after upgrading pacman to 3.4 (or is just coincidence). Have pacman 3.3 tried to download db file again if an error occured?