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#19956 - [pacman] pacman 3.4 does not accept servers on ports different from default

Attached to Project: Pacman
Opened by Thadeu Penna (tjpp) - Thursday, 24 June 2010, 16:35 GMT
Last edited by Dan McGee (toofishes) - Friday, 25 June 2010, 05:48 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: The following line in the top of mirrorlist
Server = http://qomplex000:14687/$repo
is not interpreted and all so are all servers following this: pacman returns them as "no address record".
It worked in 3.3.5. By removing the port spec, pacman calls the other servers again.

Additional info:
* 3.4.0-2

Steps to reproduce:
Add a Server with a explicit port specification in mirrorlist.
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 25 June 2010, 05:48 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Whoops, did not mean to reopen. But since I did, *please* run raw programs next time without any wrapper bullshit to make sure a bug actually exists.
Comment by Ionut Biru (wonder) - Thursday, 24 June 2010, 17:21 GMT
we have a server with the syntax

Server=http://user:pass@server.com:8000/$repo/os/$arch

this works perfectly. Maybe is not about the ports and your address is not actually resolved? do you have qomplex000 in your /etc/hosts?
Comment by Allan McRae (Allan) - Thursday, 24 June 2010, 22:35 GMT
+1 to configuration issue. My default server has a port in its address and I have no problems.
Comment by Thadeu Penna (tjpp) - Thursday, 24 June 2010, 22:39 GMT
It was solved with an update of perl-xyne-arch.
Requesting closure..

Loading...