Hi Pit, On September 30, 2010 09:39:54 am Peter Suetterlin wrote: > This is openSUSE 11.2 with hugin from the mercurial repository and > libpano13 from svn (version 1302). As I compiled myself dependencies > should be fine if the compile finishes, no?
Of course you're right. Always check your sources - code and advice alike. The mercurial repository has mulitple branches. Default is a development branch. It is never guaranteed to be stable. These days it is more unstable than usual since it has recently received a lot of new code. The bug [0] is known and being looked at. The standard recommendation applies: for production use one of the branches deemed as stable. Use the default branch to help find and fix bugs. During a release cycle (alpha/beta/candidate) use the latest branch that is candidate to be deemed stable to help polish it. list all branches with `hg branches` the current stable branch is 2010.0. This you can also download as tarball from SourceForge. 2010.2 is going through the release cycle. It is already declared a release candidate and probably safe to use as well. Unless there are relevant bug reports against it, it will soon replace 2010.0. default is, as I said, unstable. Use at your own risk. Thank you for reporting bugs, here or, better, in the tracker [1]. since you already have the whole Hg repo on your disk, you can easily switch to 2010.2 with `hg update -C 2010.2`. even better, you can have them both side by side: hg clone hugin1 hugin2 cd hugin2 hg update -C 2010.2 assuming the folder hugin1 contains the hg repository as pulled from sourceforge. if you work this way, remember that after hg pulling inside hugin1, you will need to do `hg pull` also inside hugin2 for changes to propagate. HTH Yuv [0] http://sourceforge.net/tracker/?func=detail&aid=3072069&group_id=77506&atid=550441 [1] http://sourceforge.net/tracker/?group_id=77506&atid=550441
signature.asc
Description: This is a digitally signed message part.
