Notices

Hello I have a slight issue with permissions in the package I create with mad dpkg-buildpackage and I was wondering if anyone else had such problems, in order to identify if it is a madde bug.

I have created a Qt-project with madde, (mad pscreate -t qt_simple projname) and when I run:
mad qmake && mad make && mad dpkg-buildpackage everything seems to work as it should, except for the permissions part.
Looking at the debian/projname/opt/projname/bin/ it clearly shows that my file permissions for the executable are correct (755), but when I look into the .deb -file, (with midnight commander), it on the other hand shows clearly that the permissions are incorrect (644). And therefore when I install the package on N900, it won't be executable by default as it should and I have to manually set the permissions.

Already checked that there is nothing anywhere that states that the permissions for binary should be 644. So yeah, is this happening to others?

I am running 64bit linux on my desktop where I madded the package.

It is not a bug, it is a feature ;(

dh_fixperms re-sets all permissions; only files in /bin, /usr/bin, /usr/sbin,
/usr/games (??? and /etc/init.d to 755; most othere 644 (some 444).

See http://man.he.net/man1/dh_fixperms

I was going to change this so that all files in directories ending with
/bin or /sbin would get execute permissions but stalled that due to
incompatible behaviour compared to autobuilder

(see https://bugs.maemo.org/show_bug.cgi?id=9022 )

Currently, the only way to set execute permissions for files not in
the directories mentioned above is via postinst script.