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#22435 - https protocol to pacman - unofficial repo support

Attached to Project: Pacman
Opened by John (graysky) - Friday, 14 January 2011, 22:27 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 August 2011, 02:16 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version 3.4.2
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Pacman currently supports pulling data down from repos in both http and ftp protocols. It would be very useful to also support https for those of us running unofficial repos. For example, github only allows for read access via https and even a free github account comes with 300 MB of storage. I would love to upload my packages to my github account and thereby have github act as my unofficial repo to allow others to pull from it directly with pacman. Would this implementation be an easy one?

Link to discussion thread:
https://bbs.archlinux.org/viewtopic.php?pid=878433
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 22 August 2011, 02:16 GMT
Reason for closing:  Implemented
Additional comments about closing:  libcurl is our transfer library of choice for pacman 4.0. It'll support https out of the box.
Comment by Eric Belanger (Snowman) - Friday, 14 January 2011, 22:52 GMT
You could just use XferCommand in pacman.conf with an utility that support https like wget or curl.
Comment by Dan McGee (toofishes) - Tuesday, 18 January 2011, 22:54 GMT
Sure, but it is totally silly that we don't work well with HTTPS URLs out of the box.

Problem is...it is working fine for me, so we need a reproducible test case here of a non-working HTTPS URL.

$ sudo ./src/pacman/pacman -Sy
:: Synchronizing package databases...
testhttps 0.4K 6.3M/s 00:00:00 [##################################################] 100%

dmcgee@galway ~/projects/pacman (master)
$ pacman -Sl testhttps
testhttps tig 0.16.2-1 [installed]

Where testhttps is as follows, you can add this to your pacman.conf:

[testhttps]
Server = https://dev.archlinux.org/~dan/testhttps/
Comment by Jelle van der Waa (jelly) - Saturday, 22 January 2011, 13:12 GMT
couldn't this get working when pacman switches to curl
Comment by Garrett Smith (gar1t) - Sunday, 23 January 2011, 02:10 GMT
I'm serving repo files with Nginx + SSL and can get everything easily with curl and wget.

However, pacman (3.4.2) is struggling.

It seems to be able to pull chunks down -- e.g. I can run -Sy on a repo that's 1445 bytes (very small) and it gets 792 the first pass, storing the file as a "part" in /var/lib/pacman. The second time I run -Sy, it syncs fine.

When I then try to install something, it looks like similar behavior. The package I'm trying to install is much bigger (~2M) -- I'm not sure if it's partially downloading or not.

This behavior is very consistent in my environment.

It looks like the package db for testhttps (above) is pretty small (0.4K). I wonder if it was larger if this behavior would show up.

Comment by Dan McGee (toofishes) - Sunday, 23 January 2011, 02:15 GMT
Please for sake of sanity just provide an example, rather than make me jump through hoops to try and reproduce this. I need a public URL I can use.

Loading...