update dnscrypt-proxy 2.0.19 -> 2.0.22

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

update dnscrypt-proxy 2.0.19 -> 2.0.22

Nam Nguyen
Here is an update for dnscrypt-proxy 2.0.22 (released April 1, 2019).

I successfully tested it by following the instructions in
`/usr/local/share/doc/pkg-readmes/dnscrypt-proxy'.

1. I uncommented the servers in `/etc/dnscrypt-proxy.toml'.
server_names = ['scaleway-fr', 'google', 'yandex', 'cloudflare']
2. # rcctl start dnscrypt_proxy
3. /etc/resolv.conf
nameserver 127.0.0.1
lookup file bind

--8<---------------cut here---------------start------------->8---
Index: Makefile
===================================================================
RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
retrieving revision 1.1
diff -u -p -r1.1 Makefile
--- Makefile 6 Apr 2019 08:35:41 -0000 1.1
+++ Makefile 6 Apr 2019 09:05:40 -0000
@@ -4,7 +4,7 @@ COMMENT = flexible DNS proxy, with suppo
 
 GH_ACCOUNT = jedisct1
 GH_PROJECT = dnscrypt-proxy
-GH_TAGNAME = 2.0.19
+GH_TAGNAME = 2.0.22
 
 CATEGORIES = net
 
Index: distinfo
===================================================================
RCS file: /cvs/ports/net/dnscrypt-proxy/distinfo,v
retrieving revision 1.1
diff -u -p -r1.1 distinfo
--- distinfo 6 Apr 2019 08:35:41 -0000 1.1
+++ distinfo 6 Apr 2019 09:05:40 -0000
@@ -1,2 +1,2 @@
-SHA256 (dnscrypt-proxy-2.0.19.tar.gz) = mLBa7FGHzUwq6pENfqf6zVrVfAy/oHQBhoZHdk1cKJY=
-SIZE (dnscrypt-proxy-2.0.19.tar.gz) = 3339713
+SHA256 (dnscrypt-proxy-2.0.22.tar.gz) = rIrTJrbaR7seUV0po1RRGo3Jpev89L6Ba2eRUy0C1WQ=
+SIZE (dnscrypt-proxy-2.0.22.tar.gz) = 2192330
Index: patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
===================================================================
RCS file: /cvs/ports/net/dnscrypt-proxy/patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml,v
retrieving revision 1.1
diff -u -p -r1.1 patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
--- patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019 08:35:41 -0000 1.1
+++ patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019 09:05:40 -0000
@@ -12,7 +12,7 @@ Index: dnscrypt-proxy/example-dnscrypt-p
 
 
  ## Require servers (from static + remote sources) to satisfy specific properties
-@@ -487,7 +487,7 @@ cache_neg_max_ttl = 600
+@@ -497,7 +497,7 @@ cache_neg_max_ttl = 600
 
    [sources.'public-resolvers']
    urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v2/public-resolvers.md', 'https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md']
--8<---------------cut here---------------end--------------->8---

Reply | Threaded
Open this post in threaded view
|

Re: update dnscrypt-proxy 2.0.19 -> 2.0.22

Nam Nguyen
Nam Nguyen <n@m> writes:

> Here is an update for dnscrypt-proxy 2.0.22 (released April 1, 2019).
>
> I successfully tested it by following the instructions in
> `/usr/local/share/doc/pkg-readmes/dnscrypt-proxy'.
>
> 1. I uncommented the servers in `/etc/dnscrypt-proxy.toml'.
> server_names = ['scaleway-fr', 'google', 'yandex', 'cloudflare']
> 2. # rcctl start dnscrypt_proxy
> 3. /etc/resolv.conf
> nameserver 127.0.0.1
> lookup file bind
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
> retrieving revision 1.1
> diff -u -p -r1.1 Makefile
> --- Makefile 6 Apr 2019 08:35:41 -0000 1.1
> +++ Makefile 6 Apr 2019 09:05:40 -0000
> @@ -4,7 +4,7 @@ COMMENT = flexible DNS proxy, with suppo
>  
>  GH_ACCOUNT = jedisct1
>  GH_PROJECT = dnscrypt-proxy
> -GH_TAGNAME = 2.0.19
> +GH_TAGNAME = 2.0.22
>  
>  CATEGORIES = net
>  
> Index: distinfo
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/distinfo,v
> retrieving revision 1.1
> diff -u -p -r1.1 distinfo
> --- distinfo 6 Apr 2019 08:35:41 -0000 1.1
> +++ distinfo 6 Apr 2019 09:05:40 -0000
> @@ -1,2 +1,2 @@
> -SHA256 (dnscrypt-proxy-2.0.19.tar.gz) = mLBa7FGHzUwq6pENfqf6zVrVfAy/oHQBhoZHdk1cKJY=
> -SIZE (dnscrypt-proxy-2.0.19.tar.gz) = 3339713
> +SHA256 (dnscrypt-proxy-2.0.22.tar.gz) = rIrTJrbaR7seUV0po1RRGo3Jpev89L6Ba2eRUy0C1WQ=
> +SIZE (dnscrypt-proxy-2.0.22.tar.gz) = 2192330
> Index: patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml,v
> retrieving revision 1.1
> diff -u -p -r1.1 patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
> --- patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019 08:35:41 -0000 1.1
> +++ patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019 09:05:40 -0000
> @@ -12,7 +12,7 @@ Index: dnscrypt-proxy/example-dnscrypt-p
>  
>  
>   ## Require servers (from static + remote sources) to satisfy specific properties
> -@@ -487,7 +487,7 @@ cache_neg_max_ttl = 600
> +@@ -497,7 +497,7 @@ cache_neg_max_ttl = 600
>  
>     [sources.'public-resolvers']
>     urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v2/public-resolvers.md', 'https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md']

I messed up the original diff by generating the diff from a separate cvs
repo. I copied everything over to the original ports directory, so this
should work better. (It may not make much of a difference since only the
timestamps got messed up.)

--8<---------------cut here---------------start------------->8---
Index: Makefile
===================================================================
RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
retrieving revision 1.38
diff -u -p -r1.38 Makefile
--- Makefile 30 Nov 2018 16:10:01 -0000 1.38
+++ Makefile 6 Apr 2019 09:26:06 -0000
@@ -4,7 +4,7 @@ COMMENT = flexible DNS proxy, with suppo
 
 GH_ACCOUNT = jedisct1
 GH_PROJECT = dnscrypt-proxy
-GH_TAGNAME = 2.0.19
+GH_TAGNAME = 2.0.22
 
 CATEGORIES = net
 
Index: distinfo
===================================================================
RCS file: /cvs/ports/net/dnscrypt-proxy/distinfo,v
retrieving revision 1.16
diff -u -p -r1.16 distinfo
--- distinfo 30 Nov 2018 16:10:01 -0000 1.16
+++ distinfo 6 Apr 2019 09:26:06 -0000
@@ -1,2 +1,2 @@
-SHA256 (dnscrypt-proxy-2.0.19.tar.gz) = mLBa7FGHzUwq6pENfqf6zVrVfAy/oHQBhoZHdk1cKJY=
-SIZE (dnscrypt-proxy-2.0.19.tar.gz) = 3339713
+SHA256 (dnscrypt-proxy-2.0.22.tar.gz) = rIrTJrbaR7seUV0po1RRGo3Jpev89L6Ba2eRUy0C1WQ=
+SIZE (dnscrypt-proxy-2.0.22.tar.gz) = 2192330
Index: patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
===================================================================
RCS file: /cvs/ports/net/dnscrypt-proxy/patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml,v
retrieving revision 1.2
diff -u -p -r1.2 patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
--- patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 30 Nov 2018 16:10:01 -0000 1.2
+++ patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019 09:26:06 -0000
@@ -12,7 +12,7 @@ Index: dnscrypt-proxy/example-dnscrypt-p
 
 
  ## Require servers (from static + remote sources) to satisfy specific properties
-@@ -487,7 +487,7 @@ cache_neg_max_ttl = 600
+@@ -497,7 +497,7 @@ cache_neg_max_ttl = 600
 
    [sources.'public-resolvers']
    urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v2/public-resolvers.md', 'https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md']
--8<---------------cut here---------------end--------------->8---

Reply | Threaded
Open this post in threaded view
|

Re: update dnscrypt-proxy 2.0.19 -> 2.0.22

Stuart Henderson
In reply to this post by Nam Nguyen
Too late for 6.5 but this looks good for post unlock.

--
Sent from a phone, apologies for poor formatting.

On 6 April 2019 10:19:34 Nam Nguyen <[hidden email]> wrote:

> Here is an update for dnscrypt-proxy 2.0.22 (released April 1, 2019).
>
> I successfully tested it by following the instructions in
> `/usr/local/share/doc/pkg-readmes/dnscrypt-proxy'.
>
> 1. I uncommented the servers in `/etc/dnscrypt-proxy.toml'.
> server_names = ['scaleway-fr', 'google', 'yandex', 'cloudflare']
> 2. # rcctl start dnscrypt_proxy
> 3. /etc/resolv.conf
> nameserver 127.0.0.1
> lookup file bind
>
> --8<---------------cut here---------------start------------->8---
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
> retrieving revision 1.1
> diff -u -p -r1.1 Makefile
> --- Makefile 6 Apr 2019 08:35:41 -0000 1.1
> +++ Makefile 6 Apr 2019 09:05:40 -0000
> @@ -4,7 +4,7 @@ COMMENT = flexible DNS proxy, with suppo
>
> GH_ACCOUNT = jedisct1
> GH_PROJECT = dnscrypt-proxy
> -GH_TAGNAME = 2.0.19
> +GH_TAGNAME = 2.0.22
>
> CATEGORIES = net
>
> Index: distinfo
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/distinfo,v
> retrieving revision 1.1
> diff -u -p -r1.1 distinfo
> --- distinfo 6 Apr 2019 08:35:41 -0000 1.1
> +++ distinfo 6 Apr 2019 09:05:40 -0000
> @@ -1,2 +1,2 @@
> -SHA256 (dnscrypt-proxy-2.0.19.tar.gz) =
> mLBa7FGHzUwq6pENfqf6zVrVfAy/oHQBhoZHdk1cKJY=
> -SIZE (dnscrypt-proxy-2.0.19.tar.gz) = 3339713
> +SHA256 (dnscrypt-proxy-2.0.22.tar.gz) =
> rIrTJrbaR7seUV0po1RRGo3Jpev89L6Ba2eRUy0C1WQ=
> +SIZE (dnscrypt-proxy-2.0.22.tar.gz) = 2192330
> Index: patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
> ===================================================================
> RCS file:
> /cvs/ports/net/dnscrypt-proxy/patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml,v
> retrieving revision 1.1
> diff -u -p -r1.1 patch-dnscrypt-proxy_example-dnscrypt-proxy_toml
> --- patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019
> 08:35:41 -0000 1.1
> +++ patches/patch-dnscrypt-proxy_example-dnscrypt-proxy_toml 6 Apr 2019
> 09:05:40 -0000
> @@ -12,7 +12,7 @@ Index: dnscrypt-proxy/example-dnscrypt-p
>
>
>  ## Require servers (from static + remote sources) to satisfy specific
>  properties
> -@@ -487,7 +487,7 @@ cache_neg_max_ttl = 600
> +@@ -497,7 +497,7 @@ cache_neg_max_ttl = 600
>
>    [sources.'public-resolvers']
>    urls =
>    ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v2/public-resolvers.md',
>    'https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md']
> --8<---------------cut here---------------end--------------->8---



Reply | Threaded
Open this post in threaded view
|

Re: update dnscrypt-proxy 2.0.19 -> 2.0.22

Björn Ketelaars
In reply to this post by Nam Nguyen
On Sat 06/04/2019 02:19, Nam Nguyen wrote:
> Here is an update for dnscrypt-proxy 2.0.22 (released April 1, 2019).

I have a similar diff in my tree, and contacted ${MAINTAINER} two weeks
ago. Unfortunately I did not receive a reply.

OK bket@

I will commit your diff later today...unless someone beats me to it.

Reply | Threaded
Open this post in threaded view
|

Re: update dnscrypt-proxy 2.0.19 -> 2.0.22

Nam Nguyen
Stuart Henderson writes:

> Too late for 6.5 but this looks good for post unlock.

Björn Ketelaars writes:

> On Sat 06/04/2019 02:19, Nam Nguyen wrote:
>> Here is an update for dnscrypt-proxy 2.0.22 (released April 1, 2019).
>
> I have a similar diff in my tree, and contacted ${MAINTAINER} two weeks
> ago. Unfortunately I did not receive a reply.
>
> OK bket@
>
> I will commit your diff later today...unless someone beats me to it.

Thank you for reviewing it. May I also take maintainership of
dnscrypt-proxy? The current maintainer, who is also the upstream
developer, has not been that responsive and has not provided diffs for
several updates.

Reply | Threaded
Open this post in threaded view
|

Re: update dnscrypt-proxy 2.0.19 -> 2.0.22

Björn Ketelaars
On Mon 15/04/2019 22:38, Nam Nguyen wrote:

> Stuart Henderson writes:
>
> > Too late for 6.5 but this looks good for post unlock.
>
> Björn Ketelaars writes:
>
> > On Sat 06/04/2019 02:19, Nam Nguyen wrote:
> >> Here is an update for dnscrypt-proxy 2.0.22 (released April 1, 2019).
> >
> > I have a similar diff in my tree, and contacted ${MAINTAINER} two weeks
> > ago. Unfortunately I did not receive a reply.
> >
> > OK bket@
> >
> > I will commit your diff later today...unless someone beats me to it.
>
> Thank you for reviewing it. May I also take maintainership of
> dnscrypt-proxy? The current maintainer, who is also the upstream
> developer, has not been that responsive and has not provided diffs for
> several updates.

Diff has been committed.

Concerning taking over maintainership: I would like to propose to
discuss it with the current maintainer. In my experience most
maintainers who lack time to review diffs do have the time to answer a
mail from someone who is offering support (read: willing to take over
maintainership).