Re: [SailfishDevel] [Solved] RPM validator error
On 18/09/2019 23:39, David Llewellyn-Jones wrote:
> > After I changed one line in the .yml file the validation worked again:
> >
> > - '%attr(655,-,-) %{_bindir}' -> - '%attr(755,-,-) %{_bindir}'
> >
> > It seemed the executable bit was the source of the error...
>
> Is this the first release? If not,
> it's odd this has never caused problems in the past.
It was in the yaml file since October 2015, so there were some
releases since then...
I have no idea why I put 655 and not 755 right in the first place ;)
Marko
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] [Solved] RPM validator error
Answering to myself ;)
> I was trying to check the created rpm for my app ownKeepass but it
> failed for a strange reason: "cpio: ./usr/bin/harbour-ownkeepass:
> Cannot open: Permission denied"
After I changed one line in the .yml file the validation worked again:
- '%attr(655,-,-) %{_bindir}' -> - '%attr(755,-,-) %{_bindir}'
It seemed the executable bit was the source of the error...
/Marko
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] No inbox?
On Fr, 2014-01-17 at 20:41 +, Graham Cobb wrote: On 17/01/14 19:59, Marko Koschak wrote: I also cannot get the email client working with my IMAP4 server. From the log, that is not an IMAP server -- you seem to be connecting to an SMTP server. In fact the log seems to show you connecting to port 587, the SMTP submission port. Did you manually configure the port number? If so, try 143. Thanks, you are right :) I mixed things up while trying to get it working. So now at least IMAP4 works now I need to get SMTP working ;) Marko ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How SB2 works ... was Re: QtContacts available
On Di, 2013-12-24 at 14:48 +, David Greaves wrote: [...] This is pretty much correct but not quite complete. Thanks for correcting me ;) [...] This isn't quite right. It doesn't use fakeroot as such. What it does is intercept system calls (using LD_PRELOAD) and, very efficiently, translates filesystem access (using lua if you must know!) If you're using sb2 and you are in an ARM rootfs then when you access /usr/bin/myexecutable sb2 looks for the 'right' file to execute. First it considers that your target is in /srv/mer/target/jolla-arm so it has the option to look at /srv/mer/target/jolla-arm/usr/bin/myexecutable which is an ARM binary that could run using qemu. This would be the fallback location However it may see that file is in a list of 'accelerated' binaries. So it now looks in the 'host' filesystem (usually the host but more sophisticated solutions are available). So it runs the native /usr/bin/myexecutable - but it continues to intercept system calls. Thank you for this detailed view. It makes the process much clearer to me now. So if myexecutable open()s a /usr/share/mydata then sb2 translates that path to /srv/mer/target/jolla-arm/usr/share/mydata Now, for some special binaries - like gcc, ld etc we don't want to use the /usr/bin/gcc - we use an x86 version of gcc which emits ARM code. Isn't the last 'trick' the reason why we have a 'build engine' inside of a virtualbox VM? I mean that makes sure that the Mer host tools (x86) running in the VM are 100% compatible with the Mer target rootfs (arm) running inside of SB2? One could argue that why we are not just using SB2 directly on our host (e.g. Ubuntu system) to compile our Sailfish RPM packages. But trying to do that is just a nightmare to get it working on each linux distribution ;) Thus the build engine inside the VM is an elegant workaround to overcome that problem + it gives IDE support for Mac OS X and Windows... Happy new year to all, Marko ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] No consistency across screens
If you have this special need to see that information all the time on your screen why not writing an app that shows that info on screen. Enable that app to always keep the screen active without blanking it so it should do that job for you. Any volunteers? -- Sent from my Nokia N9 On 30.12.13 19:07 Graham Cobb wrote: On 30/12/13 17:20, Mikael Hermansson wrote: On Monday 30 December 2013 15.35.39 Graham Cobb wrote: I need that information all the time -- a **lot** more often than I actually interact with the phone. In every app you can just shortly swipe left less than half of screen It doesn't work when on the home screen. So, you have to look at the screen, work out which page it is on and then take some special action dependent on that page. http://www.youtube.com/watch?v=p9YGtW274GI and you will see the clock, 3g level and wifi level and then just release and you back in current application. So I dont see any reason this must be visible all the time when its so easy check it that way. My phone sits on my desk, near my normal line of sight, and I glance at it frequently. I don't move my hands off the keyboard to touch it -- I am not even consciously doing the task of checking my phone. I also often glance at it while on a non-handsfree call which has become a longer call than I expected -- while talking and listening I can quickly move the phone into view, check it isn't about to run down on me and return it to my ear without the other person noticing. There are three key pieces of information which must be available at a glance: is there signal?, how is the battery?, have there been any missed calls? Note: I spend a lot of time on conference calls of an hour or so, usually using a desk phone -- I often do not remember whether I missed any calls on my mobile while I was on a conference call. Nor do I always remember to check when the call finishes (often rushing to get a glass of water or go to the toilet before the next call starts). So, having all three things visible whenever my eyes stray from my screen to my phone is very important. Seriously, just because everyone copycats each other in that area it doesn't mean it can be done different. Indeed. But just because a UI feature looks nice doesn't mean it is necessarily practical. I am not a UX person, but I strongly suspect the Jolla team need to do more user testing, with more varied types of users, in this area. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QtContacts available
Hi Matze On So, 2013-12-22 at 21:50 +0100, christopher.l...@thurweb.ch wrote: The SDK Build Engine is a little bit more tricky. Once you SSH in, zypper is available, but if you zypper at that level, all you are doing is adding stuff to the operating system. Within this VM is SB2, which is the Build Engine itself. Others on this mailist are much better qualified than me to tell you more about it. If you are familiar with the term chroot (change-root) then you could thing of SB2 (Scratchbox2) just as an chroot environment running armv7hl emulated code (through qemu) where you actually build your source rpm package. SB2 comes from the legacy of cross-compiling. The problem with cross-compiling is that you need to tell your compiler not to use the host (x86) tools and libs for compiling but the equivalent tools and libs from the target (armv7hl) system. There are multiple approaches to overcome that. One is to tell the compiler (via e.g. configure, makefile,...) where to find that stuff or you don't tell the compiler that (less work to create a makefile that cross-compiles too) but alter your environment that the compiler thinks it is running on the target (armv7hl) system itself. This is what SB2 actually does. That is very useful if you want to compile just any normal rpm package (from the linux userland stack) without adapting it to the target architecture. (In detail SB2 is not a full chroot system, but it uses fakeroot which enables SB2 to use host tools for speed up compilation instead of running arm binaries in slow emulation mode. It's quite some time ago I used SB2 but I hope I got it right and you got a rough idea... :) Cheers, Marko ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour/Jolla store improvement suggestion to separate Android/Sailfish apps
On Do, 2013-12-19 at 18:44 +, Kimmo Lindholm wrote: Can you add information about whether the application is for Android (apk) or for Sailfish (rpm) into the Jolla store? [...] And, please, also make there a filter – Show only Sailfish apps. Any +1 ? anyone? +1 A simple Sailfish or Droid icon on the app page would do the job. (I haven't yet seen the store, just ordered my jolla today:D) /Marko ___ SailfishOS.org Devel mailing list
[SailfishDevel] Using Clipboard object
Hi
I am just wondering how it is possible to copy text into the system
clipboard by means of the Clipboard object (as described in the Silica
reference)? When I try something like shown below I get the error:
[W] unknown:291 -
file:///opt/sdk/ownKeepass/usr/share/harbour-ownkeepass/cover/CoverPage.qml:291:5:
Element is not creatable.
Clipboard {
Is this feature simply not implemented or am I missing something?
Background: I want to copy some text of a keepass entry into clipboard
within the cover page using the swipe gesture on the cover.
Thanks,
Marko
---
import QtQuick 2.0
import Sailfish.Silica 1.0
CoverBackground {
id: coverPage
function copyToClipboard() {
systemClipboard.text = some text
}
Clipboard {
id: systemClipboard
}
}
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] working on apps?
Hi I am porting KeepassX (v0.4.3) to Sailfish - https://github.com/jobe-m/ownkeepass It's quite usable. Needs some polishing until it goes to harbour ;) Cheers, Marko Am Samstag, den 14.12.2013, 11:41 +0100 schrieb AL13N al...@rmail.be: if there are people who are working on apps, and want to let it know, so that no other devs will waste time making the same apps, you can add these here: http://elinux.org/Jolla in the appriopriate section. Thanks! ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
