Hello Schorsch,
> error: failed to replace old database with new database!
> error: replace files in /var/lib/rpm with files from
> /var/lib/rpmrebuilddb.4682 to recover
Looks like https://bugzilla.redhat.com/show_bug.cgi?id=1680124[1] .
I would try doing what the message advices. WRT the
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
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:
Hello
Tried this. But also after moving the files manually, the system does not
find my needed packages.
So I will switch back to virtualbox as a build environment for now. For me,
it does not work as expected.
Best regards
Schorsch
Am Di., 12. Mai 2020 um 14:29 Uhr schrieb Martin Kampas <
Hello
I tried both way. Using the GUI to update the package list. But even after
that, the openssl-devel package can't be found.
Using the command line:
- sfdk engine start
- sfdk tools list
SailfishOS-3.3.0.16 sdk-provided,latest
├── SailfishOS-3.3.0.16-armv7hl
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
Hello Schorsch,
OK, let's see if we can reproduce it. What is your host OS
and Docker version please?
BR,
Martin
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Am Dienstag, 12. Mai 2020, 16:22:38 CEST schrieb Martin Kampas:
> Hello Schorsch,
>
> OK, let's see if we can reproduce it. What is your host OS
> and Docker version please?
>
> BR,
> Martin
Hello Martin,
I think I had the same issue as Schorsch and I also moved back to VirtualBox.
For me
Its a Debian Buster
dpkg -l | grep docker
ii docker-ce 5:19.03.8~3-0~debian-buster
amd64Docker: the open-source application container engine
ii docker-ce-cli 5:19.03.8~3-0~debian-buster
amd64Docker CLI: the open-source
