[Pkg-gambas-devel] Gambas 3.4.1

[Ian Haywood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Current Gambas packages are 3.1.1: upstream has moved to 3.4.1 with
quite a few changes, including new modules and bytecode interpreter
changes (so code compiled with 3.4.x won't run on 3.1 runtimes,
although the reverse should still work)

I have struggled and failed using git-import-orig to update the git
repository on alioth: it tries to merge upstream changes with what's
already there, causing thousands of merge conflicts: what I want to do
is tell git "forget what's there, just make it like this", but I just
don't know the tool well enough (I use svn most of the time myself),
any clues appreciated.

However I have got the Debian packages working, they are available at:

deb ftp://ozdocit.org/pub/easygp/ easygp main
deb-src ftp://ozdocit.org/pub/easygp/ easygp main

("easygp" is the name of my main project, those packages are in there
too, but please ignore them)

Lintian reports thus:

W: gambas3-gb-sdl: duplicate-font-file
usr/share/gambas3/gb.sdl/DejaVuSans.ttf also in ttf-dejavu-core
W: gambas3-gb-sdl: extra-license-file usr/share/gambas3/gb.sdl/LICENSE
W: gambas3-gb-compress-zlib: hardening-no-fortify-functions
usr/lib/gambas3/gb.compress.zlib.so.0.0.0
W: gambas3-gb-compress-bzlib2: hardening-no-fortify-functions
usr/lib/gambas3/gb.compress.bzlib2.so.0.0.0
W: gambas3-gb-data: hardening-no-fortify-functions
usr/lib/gambas3/gb.data.so.0.0.0
W: gambas3-gb-compress: hardening-no-fortify-functions
usr/lib/gambas3/gb.compress.so.0.0.0
W: gambas3-gb-sdl-sound: hardening-no-fortify-functions
usr/lib/gambas3/gb.sdl.sound.so.0.0.0


Not sure what to do about the font file in gb.sdl: I try to see if we
can patch it to use the existing font file and not need it's own version.

with the "hardening-no-fortify": this was happenign for every binary
package, I have updated debian/rules to use "dpkg-buildflags": this
works for all except the 5 listed: I can't see what is different about
these packages in their Makefiles so I don't understand why this is
so: it may be an issue with lintian's detection.

Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQFRgweFKPy8UudQZS4RAlT+AKChitC59A7/wqXCRDzPTER3XqRNQgCeMOpD
YIvAwrK402g1X+4AEnPjXK4=
=JRoe
-----END PGP SIGNATURE-----