Re: [hugin-ptx] Re: Hugin and the 10.10 'buntus
Hi Andreas, On November 8, 2010 01:56:50 pm Andreas Metzler wrote: The goal is too keep the list somehow minimal. OK. I am pretty sure the lists in the Ubuntu wiki is inflated The goal is the same. Last time I went through that list, I started to build Hugin on a completely blank new system and every time the CMake build stopped I tried to make sense of its messages and added something to the list only if CMake moved past the last error. boost-build should not be necessary at all Boost dependencies are amongst the most confusing ones to debug. If nobody confirms this before I do it the next time, I'll try to leave boost-build out and see if it works. I don't recall who added boost-build to that list. libxi-dev and libxmu-dev are unecessarily pulled in, we patch this (42_stoplinklibXI_libXmu). IIRC I added those two [0], and the CMake build would stop with an error on my system without them. IIRC it seemed to be related to the ATI proprietary video drivers and did not disturb builds on machines without them. I am not sure about liblapack-dev, I thought I read somewhere that not linking hugin against external lapack was preferable. I recall reading that there was no major / significant disadvantage not linking; and of course it is always preferable to have less dependencies than more. But then I don't know why it was linked in the first place. LAPACK [1] claims to be for high performance linear algebra computations. Maybe what was high performance when the dependency was introduced is no longer critical? I don't know. I know I've been using Hugin built according to the wiki instructions for the past two years, so I don't have a comparison against a non-LAPACK version and can't judge. The ppa service builds for the distribution listed in debian/changelog, (lucid in your case). I do not know what the best way to get binaries for multiple releases, I guess you'll need multiple uploads. And chroots/test installations. Unfortunately this seems to be the case [2]. I'm considering the laziest option. chroots or vbox... Thanks again for your feedback and for helping me understand the anatomy of a debian package and the process of building it. Yuv [0] http://wiki.panotools.org/wiki/index.php?title=Hugin_Compiling_Ubuntudiff=12734oldid=12733 [1] http://www.netlib.org/lapack/ [2] https://answers.launchpad.net/launchpad/+question/50883 signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: Hugin and the 10.10 'buntus
On November 8, 2010 02:13:06 pm Andreas Metzler wrote: I suspect Yuv copied over the .pc/ subdirectory making dpkg-buildpackage think it already had applied the patch while it had not. Confirm. To understand the anatomy of the source package I diffed the folder created by apt-get against a checked out folder of the same revision. I failed to consider that apt-get source applied the patches. I am still at the stage of understanding the process and important things such as verifying signatures (apt-get source only issue a warning, which may be OK for local fiddling but should be unacceptable in the context of a build process for public distribution / consumption). This is why I put my packages in my own PPA and leave it to more experienced packagers like Philipp to feed the official Hugin PPA with bleeding edge builds [0]. Yuv [0] https://launchpad.net/~hugin/+archive/nightly signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: Hugin and the 10.10 'buntus
On November 7, 2010 05:41:17 pm john doe wrote: how do i update via command line from a previous version of hugin to the newest version? http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Shortcut signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Hugin and the 10.10 'buntus
Yuval Levy goo...@levy.ch wrote: [...] libxi-dev and libxmu-dev are unecessarily pulled in, we patch this (42_stoplinklibXI_libXmu). IIRC I added those two [0], and the CMake build would stop with an error on my system without them. IIRC it seemed to be related to the ATI proprietary video drivers and did not disturb builds on machines without them. Hello, They are pulled in by FindGLUT.cmake, fixing this mainly an aesthetic issue, keep them for the ppa. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin and the 10.10 'buntus
Bruno Postle br...@postle.net wrote: [...] I suspect this patch is renaming autopano-noop.sh to autopano-noop. It will fail whenever autopano-noop.sh changes (which it did yesterday), hence no autopano-noop file for dpkg to find. The patc http://git.debian.org/?p=pkg-phototools/hugin.git;a=blob;f=debian/patches/45_autopano-noop.sh_withoutshextension;h=4a417020a276e08b14f35e5cc7efbb63f2163dd6;hb=refs/heads/experimental does not touch autopano-noop.sh at all. It changes CMakeLists.txt to install the script under a different filename and it changes the hugin preferences to find it under this filename. I suspect Yuv copied over the .pc/ subdirectory making dpkg-buildpackage think it already had applied the patch while it had not. cu andreas http://sourceforge.net/tracker/index.php?func=detailaid=2857508group_id=77506atid=550441 -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin and the 10.10 'buntus
Yuval Levy goo...@levy.ch wrote: [] On October 17, 2010 12:04:05 pm Andreas Metzler wrote: [...] If you have got experimental[1] in sources.list this should work: thanks for the instructions, Andreas. They do work. A few questions. edit Maintainer and/or Uploaders in debian/control [2] and I guess Build-Depends: when an added dependency is introduced? Yes, but ... the list in the control file is much shorter than what I need to enter when building with CMake [0]. Should control be updated to reflect the CMake build dependencies? Or is there a reason to keep the list short (and maybe incomplete)? The goal is too keep the list somehow minimal. As it is it works for 2010.2.0. I am pretty sure the lists in the Ubuntu wiki is inflated boost-build should not be necessary at all (the package description suggests this is a cmake or auto* replacement). The number of libboost-*-dev packages differs. Different versions of boost are split up differently. (e.g. on Debian/stable adding libboost-date-time-dev is necessary) libxi-dev and libxmu-dev are unecessarily pulled in, we patch this (42_stoplinklibXI_libXmu). I am not sure about liblapack-dev, I thought I read somewhere that not linking hugin against external lapack was preferable. debemail=yourm...@address dch --newversion 2.9.17+dfsg-2~huginppa1 rebuilt man dch says it is a good idea to set DEBEMAIL and DEBFULLNAME, which I did in ~/.bashrc. But on Kubuntu (10.4) it still uses u...@host even though echo $DEBEMAIL returns the expected result. Is this Ubuntu-only, or also in Debian? I works for me on debian. ;-) [...] I would appreciate feedback on the first Ubuntu binary package I have ever published [1]. Looks good. Next come a few questions: * how can I use my machine (Lucid) to serve PPA builds for other 'buntu series? The ppa service builds for the distribution listed in debian/changelog, (lucid in your case). I do not know what the best way to get binaries for multiple releases, I guess you'll need multiple uploads. And chroots/test installations. * how do I know for which target architecture the binaries were built? is it default i386? AMD64? both? The ppa autobuilder builds for both i386 and amd64. [...] Do I understand correctly that the ./debian folder is all what is added to a plain unpacked tarball? Correct. (That holds for dpkg-source v3 packages.) i.e. if I would like to do a bleeding edge build rather than a 2010.2.0 build, could I simply copy the ./debian folder into a clean repo checkout, update the control file with newly added dependencies and reasonably expect that it would work in most cases? [...] That is about it. Except for: * debian/changelog (That is where the version number comes from.) * debian/patches/*. You might need to refresh patches or drop patches included upstream by deleting them and dropping tem from debian/patches/series. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin and the 10.10 'buntus
Yuval Levy goo...@levy.ch wrote: On November 7, 2010 03:13:44 pm Yuval Levy wrote: Do I understand correctly that the ./debian folder is all what is added to a plain unpacked tarball? i.e. if I would like to do a bleeding edge build rather than a 2010.2.0 build, could I simply copy the ./debian folder into a clean repo checkout, update the control file with newly added dependencies and reasonably expect that it would work in most cases? partial answer to self: there is also a ./.pc folder with the patches. [...] This is a generated file, do not copy it over. YWhen you unpack a debian source (v3) package (foo.dsc) dpkg first unpacks the source tarball and debian.tar.gz, then it applies the patches listed debian/patches/series. It keeps a log of applied patches in the .pc directory. If you manually unpack the tarballs (and don't apply the patches) later when building dpkg-buildpackage will take care of applying the patches. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin and the 10.10 'buntus
Yuval Levy goo...@levy.ch wrote: [...] The Hugin PPA [3] can use an update. The packages contributed by Philipp Seidel about six months ago are 2010.0.0 and for Karmic and Lucid only. Does any of the experienced deb packagers (Andreas?) have source packages available that can be fed to Launchpad? [...] Hello, I have not got any Ubuntu system to test and have not used a a ppa therefore I do not know the finer points. However I would be surprised if the packages in Debian/experimental would not work unchanged, except for author and versioning. (I think even the *binary* packages would work on ubuntu 10.10) If you have got experimental[1] in sources.list this should work: - [as root] apt get install devscripts [as root] apt get build-dep libpano13=2.9.17+dfsg-2 apt-get source libpano13=2.9.17+dfsg-2 cd libpano13-2.9.17+dfsg/ edit Maintainer and/or Uploaders in debian/control [2] debemail=yourm...@address dch --newversion 2.9.17+dfsg-2~huginppa1 rebuilt for hugin ppa dpkg-buildpackage -rfakeroot -uc -us -sa -S cd .. debsign -kppa-keyid resulting_changes Upload. https://help.launchpad.net/Packaging/PPA/Uploading Wait a day or two to give the buildd a chance to build binaries of libpano13-2. [as root] apt get build-dep hugin=2010.2.0+dfsg~rc2-1 apt-get source hugin=2010.2.0+dfsg~rc2-1 cd hugin-2010.2.0+dfsg~rc2 edit Maintainer and/or Uploaders in debian/control [2] debemail=yourm...@address dch --newversion 2010.2.0+dfsg~rc2-1~huginppa1 rebuilt for hugin ppa dpkg-buildpackage -rfakeroot -uc -us -sa -S cd .. debsign -kppa-keyid resulting_changes Upload. https://help.launchpad.net/Packaging/PPA/Uploading -- Obvously you'd build and test binaries (dpkg-buildpackage -rfakeroot -b -uc -us) before uploading the sources. cu andreas [1] deb-src ftp://ftp.at.debian.org/debian ../project/experimental main [2] I am not sure about the ppa policy, but judging from the existing packages you would delete Uploaders and set yourself as Maintainer. -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
