"Package has bad quality" for josm_1.5.svn8969_all.deb

[sergiocabral.bd@…]

What steps will reproduce the problem?

1. Try to install the tested version: josm_1.5.svn8969_all.deb

What is the expected result?

To install the latest version.

What happens instead?

I received a massage telling that the package has bad quality and it can damage my computer. "contact the provider".
I enforced the installation and it runned perfectly. I mean, the installation runned and the program looks OK. But I think the message can cause some dubiety or hesitation installing the program.

Please provide any additional information below. Attach a screenshot if possible.

Lintian check results for /home/sergio/Downloads/josm_1.5.svn8969_all.deb:
E: josm: control-file-has-bad-permissions postinst 0775 != 0755
E: josm: control-file-has-bad-permissions postrm 0775 != 0755

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2015-10-30 02:32:24
Last Changed Author: Don-vip
Revision: 8969
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Relative URL: ^/trunk
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2015-10-29 22:15:23 +0100 (Thu, 29 Oct 2015)
Last Changed Rev: 8969

Identification: JOSM/1.5 (8969 pt_BR) Linux Ubuntu 14.04.3 LTS
Memory Usage: 146 MB / 3554 MB (61 MB allocated, but free)
Java version: 1.7.0_85, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-7-jre:amd64-7u85-2.6.1-5ubuntu0.14.04.1
WebStart package: icedtea-netx:amd64-1.5-1ubuntu1
VM arguments: [-Dicedtea-web.bin.name=javaws, -Dicedtea-web.bin.location=/usr/bin/javaws, -Djava.security.manager, -Djava.security.policy=/etc/icedtea-web/javaws.policy]

[sergiocabral.bd@…]

I think the message can cause some dubiety or hesitation installing the program.

Thanks.

[bastiK]

Thanks for reporting the problem! How did you install the package in order to get the warning?

The file permissions were indeed wrong (nothing serious though) and should be fixed in the new build: josm_1.5.svn8969+u1_all.deb

[Don-vip]

Replying to bastiK:

The file permissions were indeed wrong (nothing serious though)

what was the problem?

[bastiK]

Replying to Don-vip:

what was the problem?

The group write permission was set, as indicated by the lintian check result. svn export messes up the file permissions and they need to be fixed afterwards.