Hi all.
After some experimenting, I found that the procedure to build a debian package
from grass cvs is quite simple:
- update from cvs the usual way
- su
dpkg-buildpackage
The only problems I find are:
- during cvs update some files are conflicting (as a result of previous
compilations); it seems necessary to delete them for a successful compilation
- I get the error
reverting patch htmlgen-fakeroot from ./ ... failed.
make: *** [unpatch] Error 1
This disappears if I delete the debian/ directory and rerun the process.
Hope this helps smoothing things further (they're now just little annoyances,
but it can take a while to sort them out the first time).
All the best.
--
Paolo Cavallini
cavallini@faunalia.it cavallini@jabber.org www.faunalia.it
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-3801953
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paolo,
Paolo Cavallini wrote:
Hi all.
After some experimenting, I found that the procedure to build a debian package
from grass cvs is quite simple:
- update from cvs the usual way
- su
dpkg-buildpackage
You can also use 'fakeroot dpkg-buildpackage'.
The only problems I find are:
- during cvs update some files are conflicting (as a result of previous
compilations); it seems necessary to delete them for a successful compilation
Are you sure that the "conflicts" are a problem ? I just run a cvs
update on the repository and there does not seem to be a problem.
The only "conflicts" I see are specific debian files which are
handled by dpkg-buildpackage, not any of the GRASS source.
If you want to clean up your source tree before an update, you can
run 'debian/rules clean' which should do a clean including
unpatching debian patches. Then the conflicts should disappear...
- I get the error
reverting patch htmlgen-fakeroot from ./ ... failed.
make: *** [unpatch] Error 1
This disappears if I delete the debian/ directory and rerun the process.
Hope this helps smoothing things further (they're now just little annoyances,
but it can take a while to sort them out the first time).
Sorry I couldn't give you above hints earlier, just stumbled upon
them myself.
Best,
Moritz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDQNsCrIrMbm76jD8RAmu8AJ95I7y0lB5JdLifV4ZOV5TPhMMBngCfW2zJ
N++JkLYzjLoDeLyTycEpfO0=
=kgX1
-----END PGP SIGNATURE-----
- update from cvs the usual way
make sure that is: cvs update -dP
- su
you cannot build a package as a regular user?
The only problems I find are:
- during cvs update some files are conflicting (as a result of previous
compilations); it seems necessary to delete them for a successful compilation
did you run 'make distclean' first?
Hamish
On Wed, October 5, 2005 08:15, Hamish wrote:
- update from cvs the usual way
make sure that is: cvs update -dP
- su
you cannot build a package as a regular user?
The only problems I find are:
- during cvs update some files are conflicting (as a result of previous
compilations); it seems necessary to delete them for a successful
compilationdid you run 'make distclean' first?
In my experience this is the culprit: when you run 'make distclean' this does
not erase the specific debian files and patches. This is why 'debian/control
clean' seems a better solution. But I'm no expert...
Moritz