>Submitter-Id:  current-users
>Originator:    John Hein
>Organization:  
>Confidential:  no 
>Synopsis:      [PATCH] devel/mercurial: update to 2.2.3
>Severity:      non-critical
>Priority:      low
>Category:      ports 
>Class:         update
>Release:
>Environment:
>Description:
- Update to 2.2.3

This has been lightly run tested locally for a few days now.

changes...
http://mercurial.selenic.com/wiki/WhatsNew/#Mercurial_2.2.3_.282012-07-01.29

build log...
https://redports.org/~jhein/20120703222845-52366-33226/mercurial-2.2.3.log

Port maintainer (pyt...@freebsd.org) is cc'd.

Generated with FreeBSD Port Tools 0.99_6 (mode: update, diff: CVS)
>How-To-Repeat:
>Fix:

--- mercurial-2.2.3.patch begins here ---
Index: Makefile
===================================================================
RCS file: /base/FreeBSD-CVS/ports/devel/mercurial/Makefile,v
retrieving revision 1.72
diff -u -p -u -r1.72 Makefile
--- Makefile    3 Jun 2012 19:38:59 -0000       1.72
+++ Makefile    3 Jul 2012 21:20:42 -0000
@@ -6,7 +6,7 @@
 #
 
 PORTNAME=      mercurial
-PORTVERSION=   2.2.2
+PORTVERSION=   2.2.3
 CATEGORIES=    devel python
 MASTER_SITES=  http://mercurial.selenic.com/release/
 
Index: distinfo
===================================================================
RCS file: /base/FreeBSD-CVS/ports/devel/mercurial/distinfo,v
retrieving revision 1.47
diff -u -p -u -r1.47 distinfo
--- distinfo    3 Jun 2012 19:38:59 -0000       1.47
+++ distinfo    3 Jul 2012 21:12:52 -0000
@@ -1,2 +1,2 @@
-SHA256 (mercurial-2.2.2.tar.gz) = 
3489110ec11fefbd2cbdefb8d715d0a869cef3dd729aaf4d5141108f8be1600a
-SIZE (mercurial-2.2.2.tar.gz) = 3430037
+SHA256 (mercurial-2.2.3.tar.gz) = 
7c61e38585ba252b31f75df6006bdcf1ff11030321f9fc628f0e1c61929d677b
+SIZE (mercurial-2.2.3.tar.gz) = 3441501
--- mercurial-2.2.3.patch ends here ---

_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"

Reply via email to