Re: devel/py-mercurial fails on Linux (SLES11sp1)

[Iain Morgan <Iain.Morgan%nasa.gov@localhost>]

On Thu, Jun 19, 2014 at 10:00:16 +0200, Thomas Klausner wrote:
> On Wed, Jun 18, 2014 at 05:51:21PM -0700, Iain Morgan wrote:
> > While trying to build devel/py-mercurial against cvs HEAD on a Linux
> > system (SLES 11sp1, kernel 2.6.32) I encountered a pkg_create failure.
> > On such a system, PLIST.inotify is added to PLIST_SRC, but the build
> > doesn't actually include the files specified by that file.
> > 
> > => Automatic manual page handling
> > pkg_create: can't stat 
> > `/p/current-test/devel/py-mercurial/work/.destdir/nasa/pkgsrc/current-test/lib/python2.
> > 7/site-packages/hgext/inotify/__init__.py'
> > pkg_create: can't stat 
> > `/p/current-test/devel/py-mercurial/work/.destdir/nasa/pkgsrc/current-test/lib/python2.
> > 7/site-packages/hgext/inotify/__init__.pyc'
> > pkg_create: can't stat 
> > `/p/current-test/devel/py-mercurial/work/.destdir/nasa/pkgsrc/current-test/lib/python2.
> > 7/site-packages/hgext/inotify/__init__.pyo'
> > pkg_create: can't stat 
> > `/p/current-test/devel/py-mercurial/work/.destdir/nasa/pkgsrc/current-test/lib/python2.
> > 7/site-packages/hgext/inotify/client.py'
> > ...
> 
> Thanks for the report.
> I've found 
> http://mercurial.selenic.com/wiki/InotifyExtension
> which explains that this extension was removed in 3.0.
> 
> I've updated the package to not expect it any longer, it should work
> now. Please try again.

Thanks, that fixed the issue.

> 
> > What I'm really interested in is building devel/mercurial, which works
> > with the 2014Q1 release, but it now requires devel/py-mercurial. And,
> > I'm not sure why py-mercurial is not including the expected inotify
> > support.
> 
> devel/mercurial is just a wrapper package so people migrating from
> earlier pkgsrc releases will still get mercurial automatically when
> updating. The actual executable is in the py-mercurial package.
>  Thomas

Thanks for the clarification.

-- 
Iain Morgan