Bug 208423 - security/fastd: Switch fastd to HTTPS
Summary: security/fastd: Switch fastd to HTTPS
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-31 14:37 UTC by Jan Bramkamp
Modified: 2016-04-29 20:09 UTC (History)
2 users (show)

See Also:
pi: maintainer-feedback+

Attachments
patch to switch master site from HTTP to HTTPS (522 bytes, patch)
2016-03-31 14:37 UTC, Jan Bramkamp 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Bramkamp 2016-03-31 14:37:22 UTC 
Created attachment 168826 [details]
patch to switch master site from HTTP to HTTPS

The libuecc master site offers HTTPS. The attached patch switch the security/libuecc master site URL from http:// to https://.
Comment 1 Jan Bramkamp 2016-03-31 14:46:53 UTC 
The fastd master site offers HTTPS. The attached patch switch the security/fastd master site URL from http:// to https://.
Comment 2 Kurt Jaeger freebsd_committer freebsd_triage 2016-04-10 10:47:38 UTC 
Looks like upstream stepped to 18 already and it seems to be an easy upgrade. Would you mind if this change is done as 18 ?

Btw, testbuilds as 18 @work.
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2016-04-10 11:38:54 UTC 
testbuilds are fine on 11a, 10.3a, 10.3i, 9.3a.
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2016-04-10 13:38:28 UTC 
Changes:
  http://fastd.readthedocs.org/en/v18/releases/v18.html
Comment 5 Jan Bramkamp 2016-04-11 08:14:19 UTC 
At the moment the fastd v18 release is identical with the main git repos master branch. This will change again in the future so it makes sense to keep the fastd-devel port around. For now users can stay on whichever port suits their usecase.

I have patches to move the ports to fastd v18, but submitted the PRs for the move from HTTP to HTTPS first, because I didn't anticipate the delay to get the changes committed.
Comment 6 Kurt Jaeger freebsd_committer freebsd_triage 2016-04-11 16:25:45 UTC 
Does it mean you approve v18 or... ?
Comment 7 commit-hook freebsd_committer freebsd_triage 2016-04-29 20:08:38 UTC 
A commit references this bug:

Author: pi
Date: Fri Apr 29 20:08:33 UTC 2016
New revision: 414291
URL: https://svnweb.freebsd.org/changeset/ports/414291

Log:
  security/fastd: 17 -> 18

  Changes:
    http://fastd.readthedocs.org/en/v18/releases/v18.html

  PR:		208423
  Submitted by:	Jan Bramkamp <crest_maintainer@rlwinm.de>

Changes:
  head/security/fastd/Makefile
  head/security/fastd/distinfo
Comment 8 Kurt Jaeger freebsd_committer freebsd_triage 2016-04-29 20:08:51 UTC 
I just assume that it means maintainer approval. Committed, thanks!