Re: Fwd: Re: Gramps Version 3.4.6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/08/2013 10:31 PM, Ross Gammon wrote:
> That just left me with my mime types issue.
>
> The lintian warnings looked like this: E: gramps:
> package-contains-mime-cache-file usr/share/mime/XMLnamespaces ....
>
> As suggested by the upstream INSTALL file, I enabled packager mode
> in configure with an override: override_dh_auto_configure:
> dh_auto_configure -- --enable-packager-mode This made the lintian
> warning go away.
>
> This seems to bypass the update-mime-database command in the
> relevant Makefile.am file. The upstream INSTALL file says this
> should be copied to the postinst & postrm script.
>
> So I put: if [ -x /usr/sbin/update-mime-database ]; then
> update-mime-database /usr/share/mime fi in
> gramps.postinst.debhelper & postrm, only to have "gbp
> buildpackage" stomp all over my manual changes!!!
>
> So I have spent some time reading & googling with no luck. How do
> you incorporate manual changes to the maintainer scripts with the
> automatic ones? Or if this is a common thing to do: is there a way
> to get debhelper to add the "update-mime-database" to postinst &
> postrm automatically?
>
> Cheers,
>
> Ross
>
Okay, I am now awake with a fresh brain! I have been living with a git
buildpackage environment that is never clean and using
- --git-ignore-new. I should not have been editing temporary debhelper
files.
Let me get a consistently clean build environment up and running. Then
I will try again.
Ross
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSfgItAAoJEFP+e72miRD8Y08QAJIZws8Uo0t/IGGUCr88YL0m
AlOKNJpsmm1/hOH0cwshbfmZF2TTYGuPpR2CMGAE7QzNwKBWO93wN0JRrauocQZC
PtUjI314RQNdwlRx9X7WZhrBqpzznDSxDlm8XCAfWcin7dqjb4WHVwVK/P2dksRz
JP/BhQTvB9NL7JzXD5iYQxVWqjB4X9/vhq8ZXEGk/V5EuDmhbafMf0+fZjyhamcY
LyLj9lQNEECF0PPpOV6Cu+FOeuat9pwSq7i3h+B72ESYzhD9VIAZz8xp/zvOk8gG
QtMJYTjH3fsNhWGMqA7bXPQZwfrvZnpUaixFRF0I9w/FVxDMKjyrDkhjAoptOYC7
XERJvR7rGuiEfypQvK+J/xkBGABdQjrO6yTkMYidzrRjChnF2geQGSPDVOFjvXgJ
U27T5bnWzpGwoWJVPi/QadWNmpIY2aIF9oLxmxvrdDTbgC4K91vvEt5gA87gll8F
Y2hkrdWOkgcKnRKAB5Q/nTakedSC2dzDysIlmGdR+zKqje9xa/H84z5M257BFNjk
khfi/gfR1CrPQBGEdqtvx01wy9a5L8D+O0fky6X6x4q2oowhUMUqWdktkP9QcVm+
31lrcAL0+42FiA2Bqp/Pkc80f6+0jzWGg0DlQRztD9Drz44sdilJdwZJczGwvkDu
jQdBImGo6utSlSv1Atjd
=jcGW
-----END PGP SIGNATURE-----
Reply to: