Bug 205406 - archivers/zipmix: add additional MASTER_SITES
Summary: archivers/zipmix: add additional MASTER_SITES
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Martin Wilke
URL:
Keywords: easy, patch, patch-ready
Depends on:
Blocks:
 
Reported: 2015-12-18 18:23 UTC by Chris Hutchinson
Modified: 2015-12-31 16:50 UTC (History)
3 users (show)

See Also:

Attachments
svn diff for archivers/zipmix (519 bytes, patch)
2015-12-18 18:23 UTC, Chris Hutchinson 		rodrigo.freebsd: maintainer-approval+
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 Chris Hutchinson 2015-12-18 18:23:04 UTC 
Created attachment 164355 [details]
svn diff for archivers/zipmix

This simply adds an IPv6 host to the list (MASTER_SITES),
for those with IPv6 only hookups.

That's it!

Thanks!

--Chris


Keywords: simple, easy, trivial, patch, patch-ready
Comment 1 Rodrigo N. Hernandez freebsd_triage 2015-12-18 18:45:24 UTC 
Hello Chris. Thanks for the patch submission. Please set maintainer-approval to + on any patches you create for ports you are maintainer of. This will ensure it comes up in the Maintainer Approved saved search.
Comment 2 VK 2015-12-18 18:51:03 UTC 
I'm curious, why add a subdomain and whole new master site instead of an AAAA record on bsdforge.com?
Comment 3 Chris Hutchinson 2015-12-18 19:32:03 UTC 
(In reply to Rodrigo N. Hernandez from comment #1)
> Hello Chris. Thanks for the patch submission. Please set maintainer-approval
> to + on any patches you create for ports you are maintainer of. This will
> ensure it comes up in the Maintainer Approved saved search.

Will do.

Thanks! I should have remembered to do that, already, sorry. :(
Comment 4 Chris Hutchinson 2015-12-18 19:35:59 UTC 
(In reply to Vladimir Krstulja from comment #2)
> I'm curious, why add a subdomain and whole new master site instead of an
> AAAA record on bsdforge.com?

Fair question. I would have asked the same. :)
I did that. But I found the web server (Apache) isn't
responding correctly. So I'm just going to dump Apache
for nginx, where I'll have better control.

Thanks Vladimir!

--Chris
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2015-12-19 07:28:47 UTC 
@Jason,

Martin (miwi@) is taking care of all the other changes from Christ that relate to adding this new IPv6 only host to MASTER_SITES for other ports. Perhaps its best if they were all handled by Martin in whatever consistent way they both decide, including this one.
Comment 6 Martin Wilke freebsd_committer freebsd_triage 2015-12-27 23:39:29 UTC 
(In reply to Chris Hutchinson from comment #4)

Hi Chris,

Did you had a chance to work on that change?

- Martin
Comment 7 Chris Hutchinson 2015-12-28 20:51:29 UTC 
(In reply to Martin Wilke from comment #6)
> (In reply to Chris Hutchinson from comment #4)
> 
> Hi Chris,
> 
> Did you had a chance to work on that change?
> 
> - Martin

Hello, Martin.
I'm changing my upstream provider, and getting a larger
IP block. I'll have an answer by the end of this week.

Thanks!

--Chris
Comment 8 Martin Wilke freebsd_committer freebsd_triage 2015-12-29 00:03:39 UTC 
(In reply to Chris Hutchinson from comment #7)

Sounds good to me, the for the update.
Comment 9 Chris Hutchinson 2015-12-31 16:50:38 UTC 
OK. Getting new upstream makes this addition no
longer necessary.

I'll close the other related pr(1)'s, as well.

Thanks for your time, Martin, and have a Happy New Year!

--Chris