Hello, On Thu, 2009-08-06 at 01:02 +0200, Alexey Balmashnov wrote: > Hi, > > I got sources for aster 9.2.0-3 from http://lyre.mit.edu/~powell/aster/ > > While trying to build a package using pbuilder and sid-chroot > environment I got the following: > ... > dpkg-checkbuilddeps: warning: can't parse dependency \ > libscotch-dev > dpkg-checkbuilddeps: error: error occurred while parsing > Build-Depends/Build-Depends-Indep) > dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; > aborting. > dpkg-buildpackage: warning: (Use -d flag to override.) > pbuilder: Failed autobuilding of package > ...
Indeed, an old bad habit, sorry. > So, I suspected that the problem is in the dependencies description. > Went to "fix" it by removing > trailing "\" but could not generate source package getting the > following error on debuild -S -sa > command: > ... > dh_clean > /usr/bin/make clean > make[1]: Entering directory `/home/alexei/Desktop/aster/aster-9.2.0' > File not found : /home/alexei/Desktop/aster/aster-9.2.0/bin/as_run > ... > > IIRC, as_run is in the astk (python-astk-server) package, so shall > aster build-depends on it? Yes, it should. > I tried this on Ubuntu 9.04 if it might matter. And it is my first > experience in building packages. Great, thanks for the report! > Further on, continuing topic of Aster/Salome packaging, if I may. > Currently, newer > versions of Code Aster (10.0.3) and Salome platform (5.1.2, Qt4 > remake) are available. Having > look at debianization as it is done now, I understand that it is a > hell of a job to package this > pieces of software, especially when there is no (as I understood from > discussion here and > elsewhere) any link with upstream... Indeed, that's why I haven't updated those packages in so long. :-( > But hence there is some expertise > around, may people > currently involved in packaging make some overview on what would be good to do > with respect to Aster/Salome build/deployment tools to simplify actual > packaging, and hence > faster deployment of newer versions of the software in the future? May > be there is something > like that already available? Yes, I think this bug is a good forum for people to use. I'd be happy to put some more time into getting it working, but a team packaging approach, or someone else packaging it, is fine with me too. Regards, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
signature.asc
Description: This is a digitally signed message part