Re: Proposal: move KWalletManager inside KWallet framework

2015-06-13 Thread Valentin Rusu
* Valentin Rusu [2015-06-13 18:29:46 +0200]: > * Stefan Bruens [2015-06-13 18:16:21 +0200]: > > > On Tuesday 02 June 2015 23:15:46 Stefan Bruens wrote: > > > On Friday 29 May 2015 22:31:00 Valentin Rusu wrote: > > > > Ok, I should also test this. Do you have a KDE commiter account? Can you > >

Re: Proposal: move KWalletManager inside KWallet framework

2015-06-13 Thread Valentin Rusu
* Stefan Bruens [2015-06-13 18:16:21 +0200]: > On Tuesday 02 June 2015 23:15:46 Stefan Bruens wrote: > > On Friday 29 May 2015 22:31:00 Valentin Rusu wrote: > > > Ok, I should also test this. Do you have a KDE commiter account? Can you > > > push a branch with your patched code, in the KWallet fr

Re: Proposal: move KWalletManager inside KWallet framework

2015-06-13 Thread Stefan Bruens
On Tuesday 02 June 2015 23:15:46 Stefan Bruens wrote: > On Friday 29 May 2015 22:31:00 Valentin Rusu wrote: > > Ok, I should also test this. Do you have a KDE commiter account? Can you > > push a branch with your patched code, in the KWallet framework, please? > > I have pushed a kwalletd4_d

Re: Proposal: move KWalletManager inside KWallet framework

2015-06-02 Thread Stefan Bruens
On Friday 29 May 2015 22:31:00 Valentin Rusu wrote: > > Ok, I should also test this. Do you have a KDE commiter account? Can you > push a branch with your patched code, in the KWallet framework, please? I have pushed a kwalletd4_dbus_compat branch Kind regards, Stefan -- Stefan BrĂ¼ns

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-29 Thread Valentin Rusu
* Stefan Bruens [2015-05-29 03:48:46 +0200]: > > > Details: > > > > > > 1. kwalletd5 checks the migration status. In case it already has run, it > > > immediately signals completion, otherwise the wizard is run and completion > > > is signaled afterwards. > > > > > > 2. Upon migration completio

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-28 Thread Stefan Bruens
On Thursday 28 May 2015 23:26:19 Valentin Rusu wrote: > * Stefan Bruens [2015-05-28 02:39:15 +0200]: > > Hi, > > > > I have tackled the problem with a different approach. As I did not see any > > reason kwalletd5 could not provide the org.kde.kwalletd service, I patched > > my kwalletd5 to provid

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-28 Thread Valentin Rusu
* Stefan Bruens [2015-05-28 02:39:15 +0200]: > Hi, > > I have tackled the problem with a different approach. As I did not see any > reason kwalletd5 could not provide the org.kde.kwalletd service, I patched my > kwalletd5 to provide both. Great! > > Details: > > 1. kwalletd5 checks the mig

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-28 Thread Stefan Bruens
Hi, I have tackled the problem with a different approach. As I did not see any reason kwalletd5 could not provide the org.kde.kwalletd service, I patched my kwalletd5 to provide both. Details: 1. kwalletd5 checks the migration status. In case it already has run, it immediately signals complet

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Albert Astals Cid
El Dimarts, 26 de maig de 2015, a les 16:13:34, Jeremy Whiting va escriure: > Then do like the rest of the projects do and branch 14.04 if that > hasn't happened already... No? Just use the existing Applications/15.04 branch ? Cheers, Albert > > On Tue, May 26, 2015 at 3:56 PM, Valentin Rusu

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Valentin Rusu
* Valentin Rusu [2015-05-26 23:56:05 +0200]: > * Albert Astals Cid [2015-05-26 23:52:18 +0200]: > > > El Dimarts, 26 de maig de 2015, a les 23:31:38, Valentin Rusu va escriure: > > > * Albert Astals Cid [2015-05-26 21:42:25 +0200]: > > > > El Dimarts, 26 de maig de 2015, a les 08:52:13, Valent

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Jeremy Whiting
Then do like the rest of the projects do and branch 14.04 if that hasn't happened already... No? On Tue, May 26, 2015 at 3:56 PM, Valentin Rusu wrote: > * Albert Astals Cid [2015-05-26 23:52:18 +0200]: > >> El Dimarts, 26 de maig de 2015, a les 23:31:38, Valentin Rusu va escriure: >> > * Albert

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Valentin Rusu
* Albert Astals Cid [2015-05-26 23:52:18 +0200]: > El Dimarts, 26 de maig de 2015, a les 23:31:38, Valentin Rusu va escriure: > > * Albert Astals Cid [2015-05-26 21:42:25 +0200]: > > > El Dimarts, 26 de maig de 2015, a les 08:52:13, Valentin Rusu va escriure: > > > > Hello, > > > > > > > > Sinc

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Albert Astals Cid
El Dimarts, 26 de maig de 2015, a les 23:31:38, Valentin Rusu va escriure: > * Albert Astals Cid [2015-05-26 21:42:25 +0200]: > > El Dimarts, 26 de maig de 2015, a les 08:52:13, Valentin Rusu va escriure: > > > Hello, > > > > > > Since the release 15.04 I see more and more users puzzled about the

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Valentin Rusu
* Albert Astals Cid [2015-05-26 21:42:25 +0200]: > El Dimarts, 26 de maig de 2015, a les 08:52:13, Valentin Rusu va escriure: > > Hello, > > > > Since the release 15.04 I see more and more users puzzled about their > > KDE Wallet set-up. For example, see this [1]. They have existing KDE4 > > wal

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Albert Astals Cid
El Dimarts, 26 de maig de 2015, a les 08:52:13, Valentin Rusu va escriure: > Hello, > > Since the release 15.04 I see more and more users puzzled about their > KDE Wallet set-up. For example, see this [1]. They have existing KDE4 > wallets which get migrated by the KF5::KWallet::kwalletd5 migratio

Re: Proposal: move KWalletManager inside KWallet framework

2015-05-26 Thread Luca Beltrame
Valentin Rusu wrote: Hello, first of all thanks to Valentin for bringing the issue here. > So, I'd like to resubmit my old proposal: would that be possible to > include KWalletManager in KF5::KWallet, in the runtime part, next to A possible issue that may have been raised in the past (however,