Re: [SailfishDevel] Fwd: Docker build engine
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 application container engine With the fresh virtualbox installation, all is working as expected. Am Di., 12. Mai 2020 um 16:22 Uhr schrieb Martin Kampas < martin.kam...@jolla.com>: > 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
Re: [SailfishDevel] Fwd: Docker build engine
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 this is on openSUSE Tumbleweed with docker 19.0.3.5 Best greetings Matthias -- Das Gesetz hat zum Schneckengang verdorben, was Adlerflug geworden wäre. (Friedrich Schiller - Die Räuber) Und der Buschfunk spielt gerade mal nichts... signature.asc Description: This is a digitally signed message part. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Fwd: Docker build engine
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
Re: [SailfishDevel] Fwd: Docker build engine
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 < martin.kam...@jolla.com>: > 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 . > > > > I would try doing what the message advices. WRT the information from > comment #4 under the bug report, simply renaming the directories may not > work, so possibly removing files in /var/lib/rpm and then copying files > from /var/lib/rpmrebuilddb.4682 could work. > > > > BR, > > Martin > > > > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Harbour validation rules for SFOS 3.3
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/blob/master/ rpmvalidation.sh#L1066 Question is, how it should be checked? Just ELF excutables and ignore /home/mersdk/* ? Lukas signature.asc Description: This is a digitally signed message part. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Fwd: Docker build engine
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 information from comment #4 under the bug report, simply renaming the directories may not work, so possibly removing files in /var/lib/rpm and then copying files from /var/lib/rpmrebuilddb.4682 could work. BR, Martin [1] https://bugzilla.redhat.com/show_bug.cgi?id=1680124 ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Harbour validation rules for SFOS 3.3
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: ERROR [/usr/bin/harbour-osmscout] Hardcoded path: /home/mersdk/share/ 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 it's done. -Ville ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Fwd: Docker build engine
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 sdk-provided,latest └── SailfishOS-3.3.0.16-i486 sdk-provided,latest - sfdk tools update SailfishOS-3.3.0.16-armv7hl Going to update the tooling [SailfishOS-3.3.0.16], then the target [SailfishOS-3.3.0.16-armv7hl] Do you want to continue? (y/n) y Updating the tooling 'SailfishOS-3.3.0.16'... Forcing raw metadata refresh Retrieving repository 'customer-jolla' metadata [done] Forcing building of repository cache Building repository 'customer-jolla' cache [done] Forcing raw metadata refresh Retrieving repository 'hotfixes' metadata [done] Forcing building of repository cache Building repository 'hotfixes' cache [done] Forcing raw metadata refresh Retrieving repository 'jolla' metadata [done] Forcing building of repository cache Building repository 'jolla' cache [done] Forcing raw metadata refresh Retrieving repository 'sdk' metadata [done] Forcing building of repository cache Building repository 'sdk' cache [done] All repositories have been refreshed. Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Building repository 'customer-jolla' cache [done] Building repository 'hotfixes' cache [done] Building repository 'jolla' cache [done] Building repository 'sdk' cache [done] Loading repository data... Retrieving repository 'customer-jolla' data... Retrieving repository 'customer-jolla' metadata [done] Retrieving repository 'hotfixes' data... Retrieving repository 'hotfixes' metadata [done] Retrieving repository 'jolla' data... Retrieving repository 'jolla' metadata [done] Retrieving repository 'sdk' data... Retrieving repository 'sdk' metadata [done] Reading installed packages... Computing distribution upgrade... Nothing to do. Updating the target 'SailfishOS-3.3.0.16-armv7hl'... Forcing raw metadata refresh Retrieving repository 'apps' metadata [done] Forcing building of repository cache Building repository 'apps' cache [done] Forcing raw metadata refresh Retrieving repository 'customer-jolla' metadata [done] Forcing building of repository cache Building repository 'customer-jolla' cache [done] Forcing raw metadata refresh Retrieving repository 'hotfixes' metadata [done] Forcing building of repository cache Building repository 'hotfixes' cache [done] Forcing raw metadata refresh Retrieving repository 'jolla' metadata [done] Forcing building of repository cache Building repository 'jolla' cache [done] Forcing raw metadata refresh Retrieving repository 'sdk' metadata [done] Forcing building of repository cache Building repository 'sdk' cache [done] All repositories have been refreshed. error: failed to replace old database with new database! error: replace files in /var/lib/rpm with files from /var/lib/rpmrebuilddb.4155 to recover Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Retrieving repository 'apps' data... Retrieving repository 'apps' metadata [done] Retrieving repository 'customer-jolla' data... Retrieving repository 'customer-jolla' metadata [done] Retrieving repository 'hotfixes' data... Retrieving repository 'hotfixes' metadata [done] Retrieving repository 'jolla' data... Retrieving repository 'jolla' metadata [done] Retrieving repository 'sdk' data... Retrieving repository 'sdk' metadata [done] Reading installed packages... Computing distribution upgrade... Nothing to do. 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 - sfdk tools package-list SailfishOS-3.3.0.16-armv7hl ssl openssl-libs installed A general purpose cryptography library with TLS implementation !!! Please note the errors during the update call !!! More hints to test here? Best regards Schorsch ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Harbour validation rules for SFOS 3.3
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 that is added by Inkscape: > 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" Do you really want to check hard-coded paths in SVG files? It is easy to remove it, but I would need to do it after every modification... Another "errors" comes from application binary itself, for example: > ERROR [/usr/bin/harbour-osmscout] Hardcoded path: /home/mersdk/share/ SailfishOS/projects/osmscout-sailfish/src/AppSettings.cpp It seems that validation script is grep-ing output from strings command... When I am looking to source code, it seems that these strings are keep in binary because of GCC assert macro. I definitely want to use asserts in my production builds. To comply this validation, I would need to introduce own assert, that will not use __FILE__ macro for messages... It sounds weird to me. Both cases looks like false positive to me. Or there is any real reason to rejecting such binaries? Lukas signature.asc Description: This is a digitally signed message part. ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
