Date: Thu, 27 Apr 2017 03:01:53 +0800 From: Sunpoet Po-Chuan Hsieh <sunpoet@freebsd.org> To: Joan Picanyol i Puig <pica@biaix.org> Cc: olivierd@freebsd.org, arrowdodger <6yearold@gmail.com>, python@freebsd.org Subject: Re: tortoisehg freebsd port update Message-ID: <CAMHz58Q%2BCzyeWgVa28aGyGfqVDRDBvo%2B3ESdpwAX5hLFVct87Q@mail.gmail.com> In-Reply-To: <20170426075453.GB41140@grummit.biaix.org> References: <20170426075453.GB41140@grummit.biaix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Thanks for notification. FYI, devel/tortoisehg has been updated to 4.1.3 in r439483. That means both ports (mercurial and tortoisehg) in head are 4.1.3 now. Then I checked quarterly branch. We have mercurial 4.1.1 and tortoisehg 4.0 in 2017Q2 branch. Maybe we need to merge updates from head to 2017Q2 branch. Regards, sunpoet On Wed, Apr 26, 2017 at 3:54 PM, Joan Picanyol i Puig <pica@biaix.org> wrote: > Hi there, > > Thank you all for keeping the FreeBSD mercurial tooling up-to-date. At > least for me, it is reassuring that I can keep on relying on it as my > main production workstation. > > However, there's one minor hiccup. Occasionally (every some months), a > mercurial upgrade breaks tortoisehg, which is a pretty useful tool and I > would say part of the "standard" mercurial user expectations. > > > Gleb (tortoisehg mantainer, Cc'ed) does keep up with tortoisehg releases > ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218623 ) but > some more coordination would improve the end-user experience. I'm unsure > of how the ports/pkg building is scheduled, but I am using the quarterly > pkg > repo if that matters. AFAICT, upstream does make it relatively easy to > keep in > sync: > > Matching Versions > If you are using TortoiseHG from source, we recommend you use the most > recent stable releases of TortoiseHG and Mercurial together. TortoiseHg > synchronized version numbers with Mercurial at release 3.0, so you > should > always use the same major revision number of TortoiseHg as Mercurial > for any > Mercurial version later than 3.0. > > Right now, I see: > > pk-ets-ws% python > Python 2.7.13 (default, Jan 3 2017, 01:29:10) > [GCC 4.2.1 Compatible FreeBSD Clang 3.8.0 (tags/RELEASE_380/final > 262564)] on freebsd11 > Type "help", "copyright", "credits" or "license" for more information. > >>> from tortoisehg.util.hgversion import hgversion, checkhgversion > >>> errmsg = checkhgversion(hgversion) > >>> errmsg > 'This version of TortoiseHg requires Mercurial version 3.9.n to 4.0.n, > but found 4.1.1' > >>> > > I'm not sure what the port system offers, but it would probably be > necessary to > specifically specify the mercurial version accepted at runtime. I > currently have: > > pk-ets-ws% pkg info -d tortoisehg-4.0_1 > tortoisehg-4.0_1: > py27-qt4-gui-4.11.4,1 > pango-1.38.0_1 > py27-qt4-xml-4.11.4,1 > py27-pygments-2.1.3_1 > py27-qt4-network-4.11.4,1 > python27-2.7.13_1 > gtk-update-icon-cache-2.24.29 > gdk-pixbuf2-2.32.3_1 > py27-setuptools-32.1.0_1 > py27-qt4-qscintilla2-2.9.1,1 > py27-qt4-core-4.11.4,1 > py27-iniparse-0.4_1 > mercurial-4.1.1 > glib-2.46.2_5 > gettext-runtime-0.19.8.1_1 > atk-2.18.0 > > That's a result of a recent upgrade I did: > > pk-ets-ws% bzgrep pkg /var/log/messages*bz2 | grep "Apr 18" | grep -E > '(mercurial|tortoise)' > /var/log/messages.0.bz2:Apr 18 18:37:10 pk-ets-ws pkg: mercurial > upgraded: 4.0.1 -> 4.1.1 > /var/log/messages.0.bz2:Apr 18 18:40:39 pk-ets-ws pkg: tortoisehg > upgraded: 4.0 -> 4.0_1 > > I update my pkg repository catalogues daily, but upgrade every few weeks > only. > > keep up the good work > -- > pica
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMHz58Q%2BCzyeWgVa28aGyGfqVDRDBvo%2B3ESdpwAX5hLFVct87Q>