You are welcome! Thanks for update, I just re-submit OSM Scout 2.2 to Harbour.
Lukas
Dne úterý 19. května 2020 10:13:07 CEST Ville Nummela napsal(a):
> On 12.5.2020 15.25, Ville Nummela wrote:
> > On 12.5.2020 12.35, Lukáš Karas wrote:
> >> Both cases looks like false positive to me. Or there is
On 12.5.2020 15.25, Ville Nummela wrote:
On 12.5.2020 12.35, Lukáš Karas wrote:
Both cases looks like false positive to me. Or there is any real
reason to
rejecting such binaries?
You are right, these are both false positives. We will fix the
validator. I will let you know (on this list) when
On 12.5.2020 16.07, Lukáš Karas wrote:
Great to hear that :-) I may provide patch to speedup this fix,
it seems to be simple shell script:
https://github.com/sailfishos/sdk-harbour-rpmvalidator/blob/master/
rpmvalidation.sh#L1066
Question is, how it should be checked?
Just ELF excutables and ig
Hi.
>
> You are right, these are both false positives. We will fix the
> validator. I will let you know (on this list) when it's done.
>
Great to hear that :-) I may provide patch to speedup this fix,
it seems to be simple shell script:
https://github.com/sailfishos/sdk-harbour-rpmvalidator/
Hi,
On 12.5.2020 12.35, Lukáš Karas wrote:
ERROR [/usr/share/harbour-osmscout/map-icons/bus_stop.svg] Hardcoded path:
inkscape:export-filename="/home/tim/projects/OSMScout/libosmscout/data/icons/
14x14/standard/bus_stop.png"
Another "errors" comes from application binary itself, for example
Hi.
I updated my application OSM Scout yesterday and it was rejected to Harbout,
because it contains "hardcoded paths". Even check in SDK fails, so I may
reproduce it (http://localhost:8080/C/harbour_tools/). But the reason seems to
be weird to me.
For example recent export path in SVG file
