-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Thomas,
>> Thanks for that hint! The reason for my problem was, that I used to >> pull from http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin rather >> than http://hg.code.sf.net/p/hugin/hugin. Interestingly that doesn't >> produce any errors, but doesn't distribute the last four commits (6337 >> vs 6341). > > These are 2 different repository. It is not only a different address for > the same repository. > After the update of sourceforge I assumed that the old repo is read only. > But it is still writeable, and there were an accidental push to the old > repo. I must have missed the change, so I just kept pulling from that old repo. While exploring what is wrong, I noticed that the wiki pages http://wiki.panotools.org/Hugin_Compiling_Ubuntu as well as http://wiki.panotools.org/Hugin_Compiling_OSX are pointing to the old repo for hugin as well as enblend. Could someone with sufficient permissions fix that? cheers, lukas - -- Do not believe the naysayers who say it cannot be done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJVA+MACgkQ1m2kmG8CIy3wVACdExppxFsWoS3PEdfK3FFOID6Y vkcAn1BtGZ9RZcAQfIwNQ3aIAazetCN6 =sb1R -----END PGP SIGNATURE----- -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/525503E4.3040007%40lukas-wirz.de. For more options, visit https://groups.google.com/groups/opt_out.
