[SailfishDevel] Setting :: Applications and accounts

2015-01-08 Thread Nicolas Cisco
Hi,
i've seen that apps can be configure thought the settings app, but didn't
found any documentation about it, how that can be done?.

The same question goes for the account section of Settings, custom apps can
be managed through that account configuration?.

Best regards.

-- 
Nicolas Cisco
www.nckweb.com.ar
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Installation trouble with the SDK

2015-01-08 Thread Kim Foder
Hi

I'm still having problems installing the SDK, also with the latest
release.

I have proven the problem to be in merssh, by executing it from a cli
with the following command:

/home/kif/SailfishOS/bin/merssh generatesshkeys
'/home/kif/SailfishOS/vmshare/ssh/private_keys/engine/root'
'/home/kif/SailfishOS/vmshare/ssh/private_keys/engine/root.pub'

This never returns, but unlike the SDK installation it doesn't freeze
the desktop (it does kill the network though).

The process becomes un-killable with 0% cpu.

Because the desktop still was responsive, I could run dmesg, and found
the following message:

[ 1148.207334] [ cut here ]
[ 1148.207353] WARNING: CPU: 1 PID: 4972
at /build/buildd/linux-3.16.0/kernel/watchdog.c:265
watchdog_overflow_callback+0x9c/0xd0()
[ 1148.207357] Watchdog detected hard LOCKUP on cpu 1
[ 1148.207360] Modules linked in:
[ 1148.207363]  hidp hid dm_crypt btusb bnep rfcomm bluetooth
6lowpan_iphc binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops
intel_rapl videobuf2_core x86_pkg_temp_thermal intel_powerclamp
v4l2_common coretemp videodev media kvm_intel hp_wmi wl(POE)
sparse_keymap kvm snd_hda_codec_hdmi crct10dif_pclmul snd_hda_codec_idt
crc32_pclmul snd_hda_codec_generic ghash_clmulni_intel snd_hda_intel
aesni_intel snd_hda_controller aes_x86_64 snd_hda_codec lrw snd_hwdep
gf128mul glue_helper snd_pcm ablk_helper snd_seq_midi cryptd
snd_seq_midi_event snd_rawmidi joydev snd_seq cfg80211 serio_raw
snd_seq_device snd_timer snd hp_accel lis3lv02d input_polldev
tpm_infineon soundcore mei_me shpchp lpc_ich mei mac_hid cuse parport_pc
ppdev lp parport i915 psmouse ahci firewire_ohci i2c_algo_bit e1000e
libahci drm_kms_helper
[ 1148.207451]  firewire_core sdhci_pci drm sdhci crc_itu_t ptp pps_core
wmi video
[ 1148.207467] CPU: 1 PID: 4972 Comm: merssh Tainted: P   OE
3.16.0-28-generic #38-Ubuntu
[ 1148.207470] Hardware name: Hewlett-Packard HP ProBook 6560b/1619,
BIOS 68SCE Ver. F.22 12/22/2011
[ 1148.207474]  0009 88013f445c10 81781eaa
88013f445c58
[ 1148.207479]  88013f445c48 8106fedd 880138cd8000

[ 1148.207484]  88013f445d70 88013f445ef8 
88013f445ca8
[ 1148.207490] Call Trace:
[ 1148.207493]  NMI  [81781eaa] dump_stack+0x45/0x56
[ 1148.207510]  [8106fedd] warn_slowpath_common+0x7d/0xa0
[ 1148.207517]  [8106ff4c] warn_slowpath_fmt+0x4c/0x50
[ 1148.207524]  [811c] watchdog_overflow_callback
+0x9c/0xd0
[ 1148.207532]  [8115fecd] __perf_event_overflow+0x8d/0x2a0
[ 1148.207539]  [8102a11b] ? x86_perf_event_set_period
+0xcb/0x170
[ 1148.207546]  [811609f4] perf_event_overflow+0x14/0x20
[ 1148.207553]  [8103187d] intel_pmu_handle_irq+0x1ed/0x3e0
[ 1148.207560]  [81028e7b] perf_event_nmi_handler+0x2b/0x50
[ 1148.207565]  [810172b0] nmi_handle+0x80/0x120
[ 1148.207570]  [8101785d] default_do_nmi+0x4d/0x140
[ 1148.207575]  [810179d8] do_nmi+0x88/0xd0
[ 1148.207581]  [8178c2a1] end_repeat_nmi+0x1e/0x2e
[ 1148.207587]  [81789708] ? _raw_spin_lock_irqsave+0x48/0x70
[ 1148.207593]  [81789708] ? _raw_spin_lock_irqsave+0x48/0x70
[ 1148.207598]  [81789708] ? _raw_spin_lock_irqsave+0x48/0x70
[ 1148.207601]  EOE  [810bfd76] down+0x16/0x50
[ 1148.207675]  [c0a2ae49] wl_proc_read+0x89/0xa0 [wl]
[ 1148.207683]  [81246d18] proc_reg_read+0x48/0x70
[ 1148.207691]  [811e0f14] vfs_read+0x94/0x180
[ 1148.207698]  [811e1bb6] SyS_read+0x46/0xb0
[ 1148.207704]  [81789eed] system_call_fastpath+0x1a/0x1f
[ 1148.207707] ---[ end trace 27a6d7af2f51ec6d ]--- 


and a short while later a lot of the following:


[ 1185.312162] INFO: rcu_sched detected stalls on CPUs/tasks: { 1}
(detected by 0, t=15009 jiffies, g=66782, c=66781, q=0)
[ 1185.312181] sending NMI to all CPUs:
[ 1185.312193] NMI backtrace for cpu 0
[ 1185.312202] CPU: 0 PID: 1785 Comm: Xorg Tainted: PW  OE
3.16.0-28-generic #38-Ubuntu
[ 1185.312215] Hardware name: Hewlett-Packard HP ProBook 6560b/1619,
BIOS 68SCE Ver. F.22 12/22/2011
[ 1185.312218] task: 8800b5a228c0 ti: 8801385f task.ti:
8801385f
[ 1185.312220] RIP: 0010:[813a7e52]  [813a7e52]
__const_udelay+0x12/0x30
[ 1185.312228] RSP: 0018:88013f403de0  EFLAGS: 0046
[ 1185.312230] RAX: 01062560 RBX: 2710 RCX:
0004
[ 1185.312233] RDX: 008c1328 RSI: 0100 RDI:
00418958
[ 1185.312235] RBP: 88013f403df8 R08: 0004 R09:
0086
[ 1185.312237] R10: 027dc00eb52b R11: 039b R12:
81c589c0
[ 1185.312239] R13: 81d212a0 R14: 81c589c0 R15:

[ 1185.312242] FS:  7fa940fbe9c0() GS:88013f40()
knlGS:
[ 1185.312245] CS:  0010 DS:  ES:  CR0: 80050033
[ 1185.312247] CR2: 

Re: [SailfishDevel] Installation trouble with the SDK

2015-01-08 Thread Krisztian Olah
Hi Kim,
You can switch off the overlay scrollbar thing with export
LIBOVERLAY_SCROLLBAR=0, did you try if that helps? Alternatively you could
find out wether it is a Unity problem by installing another desktop say
LXDE; I doubt it is related.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Harbour should allow libcrypt/openssl

2015-01-08 Thread Reto Zingg

Hi,

On 07.12.2013 21:37, Mikael Hermansson wrote:

I think harbour store should allow libcrypt/openssl because AFAIK that
API will not change very often and is probadly already used in sailfishos?



as mentioned in several places before. Harbour QA started on 07. Jan 
2015 to accept submissions which depend on:


libssl.so.10
libcrypto.so.10

best regards
Reto


I guess there is some apps that want to use AES/MD5/SHA256 and so
on. Passwordwallet apps and similar

Regards

Mikael






___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Jolla gallery plugins

2015-01-08 Thread Anatoly Shipitsin
On Thu, Jan 8, 2015 at 6:40 PM, Oleg Linkin maledictusdema...@gmail.com
wrote:

 I am not agree with you. Transfer engine plugins give us possibility to
 share some staff with services, but for showing picasa images in gallery
 like for facebook - it is not transfer engine issue


Facebook plugin already open can be find on github
https://github.com/nemomobile/buteo-sync-plugins-social

 В письме от 8 января 2015 13:23:50 пользователь Gabriel Böhme написал:
  Nemo Transfer Engine is what you are looking for, there is a GIT repo
 with an example.
 
  But it's not very well documented and not allowed in harbour.
 
  Am Do. Jan. 8 12:58:13 2015 GMT+0100 schrieb Oleg Linkin:
   Are there any sources or documentations or examples of creating this
 type of plugins?
   I want to add google picasa to google buteo-sync-plugin but without
 possibility showing it in gallery all this hasn't any sense.
   Thx.
   ___
   SailfishOS.org Devel mailing list
   To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org
  
 
 

 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Harbour: Allow more libraries to link against

2015-01-08 Thread Reto Zingg

Hi,

On 27.12.2013 18:48, Ruediger Gad wrote:

Hi,

two of my apps (MeePasswords and Q To-Do) are being rejected because
they are linked against libraries that are not allowed.

I read the according FAQ at https://harbour.jolla.com/faq and understand
your motivation for being so restrictive.
However, I'd love to add these apps to Harbour and I think that the libs
as well as their API are pretty much stable and should be suited for
addition to the whitelist of allowed libs.

The relevant libraries are:
- libqmfclient5.so.1
- libssl.so.10
- libcrypto.so.10



as mentioned in several places before. Harbour QA started on 07. Jan 
2015 to accept submissions which depend on:


libssl.so.10
libcrypto.so.10


Unfortunately libqmfclient5.so.1 is not yet among the allowed libraries. 
There are API changes coming up and the library is not widely requested, 
so it does not have high priority to be allowed in Harbour soon.


best regards
Reto



It would be great if these could be added to the allowed libraries to
link against.

Some explanation what I use these libs for:
libqmfclient5.so.1:
   Both of my apps offer a synchronization feature that uses IMAP for
synchronising files between different devices.
   For this, I use the IMAP/e-mail API as provided by QMF.
libssl.so.10
libcrypto.so.10
   MeePasswords uses cryptography to encrypt data.
   For this it uses qca-qt5 which links against said libs.
   I know that there is qca-qt5 already in nemo:devel:mw (I actually
filed the PR to enable packaging of the qt5 version) but it is not
supported for Harbour apps yet.
   I also requested the addition of qca-qt5 to the allowed libs some time
ago.
   As work-around I ship qca-qt5 with my app and thus need to link
against said libs in the meantime.

I hope this is the right channel to address this request to.
If not, please redirect me in the appropriate direction.



Thanks and best regards,

Ruediger






___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Problems deploying with SDK 1412

2015-01-08 Thread Tone Kastlunger
Ok, found the root cause for this.
In my project, I have two sub projects (lets name them a and b)
Sub project a is a tool, and is not used in any rpm,  so it does not have
the .spec file.
Sub project b is my real deal, and has a proper .spec file.

I updated the sdk, opened the project file and switched the runned exe
(from a to b).
For some reason, when switching the configuration of what executable to run
on device (from the main panel)
did not change the setting in the Run configuration on the project page
(originally on a). This explains why qmake was looking for the .spec in the
wrong place.


On Thu, Jan 8, 2015 at 11:28 PM, Tone Kastlunger users.giulie...@gmail.com
wrote:

 Ok, found the problem.
 the location of the rpm folder containing the .spec file has changed - yet
 again.
 I keep on pushing it from the root directory of the project to my
 subproject root directory every once in a while .
 Can anyone explain why this happens?

 On Thu, Jan 8, 2015 at 11:25 PM, Tone Kastlunger 
 users.giulie...@gmail.com wrote:

 It seems I am facing a similar problem, but on the pc side (win7):

 Fatal: No spec file found in '/home/mersdk/share//debota/rpm/' and
 couldn't make one from a yaml #1

 23:23:58: The process
 C:\sviluppo\sailfish\sdk\settings\SailfishBeta1\mer-sdk-tools\MerSDK\SailfishOS-armv7hl\rpm.cmd
 exited with code 1.

 Error while building/deploying project debota-sailfish (kit:
 MerSDK-SailfishOS-armv7hl)

 When executing step 'Rpm'

 I wonder when this broke? It used to work in the last release.

 PS : the echo off in the rpm.cmd is really misleading for managing errors
 like these...

 On Thu, Jan 8, 2015 at 9:16 PM, Krisztian Olah fasza2mob...@gmail.com
 wrote:

 Thanks Michael,
 Creating the /opt/sdk/ path seems to have soved the issue, I can't
 remember ever having to do this manually. I very recently restored my Jolla
 to factory settings so that might have had something to do with it as well.

 Thanks again
 Kris

 On 8 January 2015 at 18:35, Michael Neufing mich...@neufing.org wrote:

 Hi Kris,

 are you using deployment by copying binaries to device?
 If yes, can you check if the folder /opt/sdk exists on your device? If
 not, create it and test again.
 This solved my problems with this deployment mode.

 You could also set the deployment mode to RPM.

 Michael.



 Zitat von Krisztian Olah fasza2mob...@gmail.com:


  Hi list,
 I installed the new SDK yesterday, but since it's installed I cant
 seem to
 be able to deploy onto device fails due to an rsync error:

 rsync: mkdir /opt/sdk/Trash failed: No such file or directory (2)

 rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.0]

 Deploy failed

 rsync: [sender] write error: Broken pipe (32)

 16:50:40: The process
 /home/kriszik_arch/.config/SailfishBeta1/mer-sdk-tools/
 MerSDK/SailfishOS-armv7hl/deploy
 exited with code 1.

 Error while building/deploying project Trash (kit:
 MerSDK-SailfishOS-armv7hl)

 When executing step 'Rsync'


 This is the boilerplate project that is preset by Jolla upon choosing
 SailfishOS for new project, but same thing happens with my project
 too. SSH
 works as it's supposed to, the SDK's connection test reports success,
 but
 deploy fails. I didn't try with the emulator, becase I do not wish to
 work
 with it even if it worked. I tried to reinstall, checked md5, cleared
 .config (I am on Arch linux x86_64 KDE), but as of now no luck. Is
 there
 anything I might have missed?


 I would appricate any insight.

 Thanks

 Kris



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to devel-unsubscribe@lists.
 sailfishos.org



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org




___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Jolla gallery plugins

2015-01-08 Thread Oleg Linkin
Are there any sources or documentations or examples of creating this type of 
plugins?
I want to add google picasa to google buteo-sync-plugin but without possibility 
showing it in gallery all this hasn't any sense.
Thx.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Next meeting on SailfishOS, open source, collaboration: 7-January 2015 @ 15:00 UTC

2015-01-08 Thread Sander van Grieken
Regarding SIP integration, I'm very interested in that.

I can test and possibly also contribute with development, but time is a bit 
limited.

Also I can provide SIP accounts on a kamailio server I'm running.

Regards,
Sander van Grieken

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Using QtBluetooth 5.4 Backport in a harbour-app

2015-01-08 Thread Harald Schmitt
Am 05.01.2015 um 01:56 schrieb Aaron McCarthy:
 On Mon, 15 Dec 2014 17:53:34 Harald Schmitt wrote:
 Am 15.12.2014 um 13:35 schrieb Harald Schmitt:
 Am 11.12.2014 um 17:45 schrieb Harald Schmitt:
 Am 10.12.2014 um 18:24 schrieb Richard Rondu:
 Hi, the backport is not completely up-to-date with QtBluetooth 5.4, I
 have to update it. Nevertheless It should work with standard
 bluetooth, I haven't tried with BLE though.
 Other part of QtConnectivity that are not QtBluetooth haven't been
 tried either (NFC and so on). I even think I have even disabled the
 build.

 Nevertheless, here are the relevant part of the .yaml file and the
 .pro file I use for Parrot ZIK 2.0 Manager in  harbour that ship
 with this backport.

 You have to build QtBluetooth backport separately with the sailfish
 sdk, then put the .so file(s) in a lib subdirectory inside your
 project.
 thanks that got me started. I hope I can dedicate enough time to bring a
 Xiaomi MiBand app to the harbour.
 While building qtconnectivity with the sdk I get the following message

 Project MESSAGE: Unsupported Bluetooth platform, will not build a
 working QtBluetooth library.

 Project MESSAGE: Either no Qt D-Bus found or no BlueZ headers.


 qtHaveModule(dbus) returns false. Do you have any idea?
 I made a mistake, actually config_bluez returns false and
 qtHaveModule(dbus) returns true. But still I don't know why.
 Try to determine why the BlueZ config test failed. You can manually try to 
 build the config test project in qtconnectivity/config.tests/bluez. It uses 
 pkgconfig to find the required headers and libraries. Ensure that the 
 required 
 development packages are installed.
Thanks, it works now. I can connect to a BLE device using the
QLowEnergyController class if I know the device address.
The discovery does not find BLE devices only normal Bluetooth devices.


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] Build with sailfish latest on mer-obs fails, QVariant, double (?)

2015-01-08 Thread Kimmo Lindholm
Thanks to fellows on #sailfishos

i had made a bad thing: (or bad copypaste)
#define pi (3.14159)

in some other place someone else;
QtMetaTypePrivate::QPairVariantInterfaceImpl pi =  
v.valueQtMetaTypePrivate::QPairVariantInterfaceImpl();

And seems that my #define messed things up.
Now it builds correctly.

-kimmo


From: devel-boun...@lists.sailfishos.org 
[mailto:devel-boun...@lists.sailfishos.org] On Behalf Of Kimmo Lindholm
Sent: 8. tammikuuta 2015 11:20
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Build with sailfish latest on mer-obs fails, QVariant, 
double (?)

My toholed daemon is built on mer-obs, succesfully built previously during 
October.
Now the repo has propably been updated to latest sailfish release, and build 
fails strangely. (Rebuilt for some reason 6th Jan)

That include file trace doesn't help at all.

build-log says this for error:
(Complete log here 
https://build.merproject.org/package/live_build_log/home:kimmoli:tohs/toholed-daemon/sailfish_latest_armv7hl/armv8el
 )

[   62s] In file included from /usr/include/qt5/QtCore/qvariantanimation.h:48:0,
[   62s]  from /usr/include/qt5/QtCore/qpropertyanimation.h:45,
[   62s]  from /usr/include/qt5/QtCore/QtCore:8,
[   62s]  from /usr/include/qt5/QtDBus/QtDBusDepends:2,
[   62s]  from /usr/include/qt5/QtDBus/QtDBus:3,
[   62s]  from src/toholed.cpp:19:
[   62s] /usr/include/qt5/QtCore/qvariant.h: In static member function 'static 
QPairQVariant, QVariant 
QtPrivate::QVariantValueHelperInterfaceQPairQVariant, QVariant 
::invoke(const QVariant)':
[   62s] /usr/include/qt5/QtCore/qvariant.h:789:62: error: no matching function 
for call to 
'QtMetaTypePrivate::QPairVariantInterfaceImpl::QPairVariantInterfaceImpl(double)'
[   62s] /usr/include/qt5/QtCore/qvariant.h:789:62: note: candidates are:
[   62s] /usr/include/qt5/QtCore/qmetatype.h:1247:5: note: 
QtMetaTypePrivate::QPairVariantInterfaceImpl::QPairVariantInterfaceImpl()
[   62s] /usr/include/qt5/QtCore/qmetatype.h:1247:5: note:   candidate expects 
0 arguments, 1 provided
[   62s] /usr/include/qt5/QtCore/qmetatype.h:1236:23: note: templateclass T 
QtMetaTypePrivate::QPairVariantInterfaceImpl::QPairVariantInterfaceImpl(const 
T*)
[   62s] /usr/include/qt5/QtCore/qmetatype.h:1215:7: note: 
QtMetaTypePrivate::QPairVariantInterfaceImpl::QPairVariantInterfaceImpl(const 
QtMetaTypePrivate::QPairVariantInterfaceImpl)
[   62s] /usr/include/qt5/QtCore/qmetatype.h:1215:7: note:   no known 
conversion for argument 1 from 'double' to 'const 
QtMetaTypePrivate::QPairVariantInterfaceImpl'
[   62s] /usr/include/qt5/QtCore/qvariant.h:791:62: error: request for member 
'first' in '3.141589988261834005243144929409027099609e+0', which is of 
non-class type 'double'
[   62s] /usr/include/qt5/QtCore/qvariant.h:796:62: error: request for member 
'second' in '3.141589988261834005243144929409027099609e+0', which is of 
non-class type 'double'
[   62s] make: *** [toholed.o] Error 1
[   62s] make: *** Waiting for unfinished jobs
[   64s] error: Bad exit status from /var/tmp/rpm-tmp.oWhNJy (%build)
[   64s]
[   64s]
[   64s] RPM build errors:
[   64s] Bad exit status from /var/tmp/rpm-tmp.oWhNJy (%build)

Sources are in my bitbucket

-kimmo
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Read-only TextArea: Always keep the lines added last visible

2015-01-08 Thread Dirk Zimmermann
On 07.01.2015 12:06, Sami Kananoja wrote:
 Hi,
 
 This should do the trick:
 
 SilicaFlickable {
 id: flickable
 anchors.fill: parent
 contentHeight: textAreaLog.height
 contentY: Math.max(0, contentHeight - height)
 TextArea {
 id: textAreaLog
 readOnly: true
 text: Test
 width: flickable.width
 }
 }
 
 The contentY binding is the one that keeps the last line visible (but has 
 some annoying side effects if you want to scroll the content manually - 
 fixing that is left as home work :) )
 

Thanks, that worked :)

Dirk
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


[SailfishDevel] Problems deploying with SDK 1412

2015-01-08 Thread Krisztian Olah
Hi list,
I installed the new SDK yesterday, but since it's installed I cant seem to
be able to deploy onto device fails due to an rsync error:

rsync: mkdir /opt/sdk/Trash failed: No such file or directory (2)

rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.0]

Deploy failed

rsync: [sender] write error: Broken pipe (32)

16:50:40: The process
/home/kriszik_arch/.config/SailfishBeta1/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy
exited with code 1.

Error while building/deploying project Trash (kit:
MerSDK-SailfishOS-armv7hl)

When executing step 'Rsync'


This is the boilerplate project that is preset by Jolla upon choosing
SailfishOS for new project, but same thing happens with my project too. SSH
works as it's supposed to, the SDK's connection test reports success, but
deploy fails. I didn't try with the emulator, becase I do not wish to work
with it even if it worked. I tried to reinstall, checked md5, cleared
.config (I am on Arch linux x86_64 KDE), but as of now no luck. Is there
anything I might have missed?


I would appricate any insight.

Thanks

Kris
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Problems deploying with SDK 1412

2015-01-08 Thread Krisztian Olah
Thanks Michael,
Creating the /opt/sdk/ path seems to have soved the issue, I can't remember
ever having to do this manually. I very recently restored my Jolla to
factory settings so that might have had something to do with it as well.

Thanks again
Kris

On 8 January 2015 at 18:35, Michael Neufing mich...@neufing.org wrote:

 Hi Kris,

 are you using deployment by copying binaries to device?
 If yes, can you check if the folder /opt/sdk exists on your device? If
 not, create it and test again.
 This solved my problems with this deployment mode.

 You could also set the deployment mode to RPM.

 Michael.



 Zitat von Krisztian Olah fasza2mob...@gmail.com:


  Hi list,
 I installed the new SDK yesterday, but since it's installed I cant seem to
 be able to deploy onto device fails due to an rsync error:

 rsync: mkdir /opt/sdk/Trash failed: No such file or directory (2)

 rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.0]

 Deploy failed

 rsync: [sender] write error: Broken pipe (32)

 16:50:40: The process
 /home/kriszik_arch/.config/SailfishBeta1/mer-sdk-tools/
 MerSDK/SailfishOS-armv7hl/deploy
 exited with code 1.

 Error while building/deploying project Trash (kit:
 MerSDK-SailfishOS-armv7hl)

 When executing step 'Rsync'


 This is the boilerplate project that is preset by Jolla upon choosing
 SailfishOS for new project, but same thing happens with my project too.
 SSH
 works as it's supposed to, the SDK's connection test reports success, but
 deploy fails. I didn't try with the emulator, becase I do not wish to work
 with it even if it worked. I tried to reinstall, checked md5, cleared
 .config (I am on Arch linux x86_64 KDE), but as of now no luck. Is there
 anything I might have missed?


 I would appricate any insight.

 Thanks

 Kris



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to devel-unsubscribe@lists.
 sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Problems deploying with SDK 1412

2015-01-08 Thread Tone Kastlunger
It seems I am facing a similar problem, but on the pc side (win7):

Fatal: No spec file found in '/home/mersdk/share//debota/rpm/' and couldn't
make one from a yaml #1

23:23:58: The process
C:\sviluppo\sailfish\sdk\settings\SailfishBeta1\mer-sdk-tools\MerSDK\SailfishOS-armv7hl\rpm.cmd
exited with code 1.

Error while building/deploying project debota-sailfish (kit:
MerSDK-SailfishOS-armv7hl)

When executing step 'Rpm'

I wonder when this broke? It used to work in the last release.

PS : the echo off in the rpm.cmd is really misleading for managing errors
like these...

On Thu, Jan 8, 2015 at 9:16 PM, Krisztian Olah fasza2mob...@gmail.com
wrote:

 Thanks Michael,
 Creating the /opt/sdk/ path seems to have soved the issue, I can't
 remember ever having to do this manually. I very recently restored my Jolla
 to factory settings so that might have had something to do with it as well.

 Thanks again
 Kris

 On 8 January 2015 at 18:35, Michael Neufing mich...@neufing.org wrote:

 Hi Kris,

 are you using deployment by copying binaries to device?
 If yes, can you check if the folder /opt/sdk exists on your device? If
 not, create it and test again.
 This solved my problems with this deployment mode.

 You could also set the deployment mode to RPM.

 Michael.



 Zitat von Krisztian Olah fasza2mob...@gmail.com:


  Hi list,
 I installed the new SDK yesterday, but since it's installed I cant seem
 to
 be able to deploy onto device fails due to an rsync error:

 rsync: mkdir /opt/sdk/Trash failed: No such file or directory (2)

 rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.0]

 Deploy failed

 rsync: [sender] write error: Broken pipe (32)

 16:50:40: The process
 /home/kriszik_arch/.config/SailfishBeta1/mer-sdk-tools/
 MerSDK/SailfishOS-armv7hl/deploy
 exited with code 1.

 Error while building/deploying project Trash (kit:
 MerSDK-SailfishOS-armv7hl)

 When executing step 'Rsync'


 This is the boilerplate project that is preset by Jolla upon choosing
 SailfishOS for new project, but same thing happens with my project too.
 SSH
 works as it's supposed to, the SDK's connection test reports success, but
 deploy fails. I didn't try with the emulator, becase I do not wish to
 work
 with it even if it worked. I tried to reinstall, checked md5, cleared
 .config (I am on Arch linux x86_64 KDE), but as of now no luck. Is there
 anything I might have missed?


 I would appricate any insight.

 Thanks

 Kris



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to devel-unsubscribe@lists.
 sailfishos.org



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to
 devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org