Re: KDE PIM packaging

2012-08-30 Thread Lisandro Damián Nicanor Pérez Meyer
On Thu 30 Aug 2012 16:27:45 Torsten Grote escribió:
> On Thursday 23 August 2012 15:27:04 Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > We currently lack the manpower to do this. We still have some RC bugs
> > that need fixing, so we have some other stuff to do before thinking in
> > kdepim.
> 
> That's unfortunate! How hard is it to learn Debian packaging? Is it
> realistic for me to start and try to help with that? (I do have a
> technical background, know how to program, use git etc.)

Learning to package takes time and will, but if I could learn it, I'm sure 
almost anyone can :-)

That being said, kmail is not the place to start packaging.

> On the other hand, I'm really close to offer money. Would that be something
> that would motivate you to dedicate more of your spare time to packaging?

While I'm perfectly fine if someone earns money for doing Debian stuff, I 
don't think this is the place to ask for it. But I may be mistaken in this.

On the other hand, there is something boring but simple that almost anyone can 
help with: bug #673268. It needs an enourmous ammount of work, but it's a 
quite simple task. I'm planning to go for it on Sunday, starting more or less 
at 17:00 GTM. If someone is interested, [s]he can join #debian-kde on 
irc.oftc.net to sync efforts.

Regards, Lisandro.

-- 
#exclude 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-08-30 Thread Mirosław Zalewski
On 30/08/2012 at 21:27, Torsten Grote  wrote:

> How hard is it to learn Debian packaging? Is it realistic 
> for me to start and try to help with that? (I do have a technical
> background,  know how to program, use git etc.)

Debian packaging is not all that hard. I managed to create my first package 
from source in one evening.

There things are easier, because you don't have to start from scratch (there 
are already older versions packaged). But PIM packages seems to be quite 
complex (many packages from one source) — perhaps it would be better to start 
with something easier.

Anyway, I am not Debian developer, so you don't have to trust me.
You should definitely read that, though:
http://www.debian.org/doc/manuals/maint-guide/
-- 
Best regards
Mirosław Zalewski


-- 
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201208310029.47590.mini...@poczta.onet.pl



Re: KDE PIM packaging

2012-08-30 Thread Torsten Grote
On Thursday 23 August 2012 15:27:04 Lisandro Damián Nicanor Pérez Meyer wrote:
> We currently lack the manpower to do this. We still have some RC bugs that 
> need fixing, so we have some other stuff to do before thinking in kdepim.

That's unfortunate! How hard is it to learn Debian packaging? Is it realistic 
for me to start and try to help with that? (I do have a technical background, 
know how to program, use git etc.)

On the other hand, I'm really close to offer money. Would that be something 
that would motivate you to dedicate more of your spare time to packaging?

Regards,
Torsten


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-08-28 Thread Martin Steigerwald
Am Donnerstag, 23. August 2012 schrieb Lisandro Damián Nicanor Pérez 
Meyer:
> On Thu 23 Aug 2012 04:50:14 Torsten Grote escribió:
> [snip]
> 
> > Ok who do I have to bribe to get 4.8 or 4.9 KDE PIM packages? How
> > much do you want? ;)
> > 
> > Is there anything that could be done to help with that? Is the summer
> > to blame?
> 
> We currently lack the manpower to do this. We still have some RC bugs
> that need fixing, so we have some other stuff to do before thinking in
> kdepim.
> 
> By the way, I don't know why you should blame the summer, I'm in the
> middle of winter ;)

Well I understand that RC bugs go first ;).

As for KDEPIM 2 packaging: It seems to be good to use at least KDEPIM from 
KDE SC 4.8.6 or 4.9.1:

--  Weitergeleitete Nachricht  --

Subject: Re: [kdepim-users] KMail2 at kdepim 4.9.0
Date: Samstag, 25. August 2012
From: Andras Mantia 
To: kdepim-us...@kde.org

Andras Mantia wrote:

> The only serious (ie. that could cause data loss) bug is with online 
> imap
> accounts and local spam filtering. That is still not fixed, unfortunately
> the fix I tried didn't work. In that case you have two choices:
> - use a disconnected imap account (that just means mail bodies are
> completely downloaded)
> - do not use client-side spam filtering, but use sieve scripts server 
> side

This one hopefully is fixed in 4.9.1, 4.8.6, 4.10.

Andras
___
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-
users

---

There have been some reports there that with KDEPIM 4.9 things finally 
start to look quite good.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201208281951.48981.mar...@lichtvoll.de



Re: KDE PIM packaging

2012-08-23 Thread Lisandro Damián Nicanor Pérez Meyer
On Thu 23 Aug 2012 04:50:14 Torsten Grote escribió:
[snip] 
> Ok who do I have to bribe to get 4.8 or 4.9 KDE PIM packages? How much do
> you want? ;)
> 
> Is there anything that could be done to help with that? Is the summer to
> blame?

We currently lack the manpower to do this. We still have some RC bugs that 
need fixing, so we have some other stuff to do before thinking in kdepim.

By the way, I don't know why you should blame the summer, I'm in the middle of 
winter ;)

Kinds regards, Lisandro.

-- 
Una vez que hemos eliminado lo imposible, lo que queda, por improbable que
parezca, es la verdad.
  Sherlock Holmes

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-08-23 Thread Torsten Grote
On Saturday 04 August 2012 15:22:03 Torsten Grote wrote:
> On Monday 18 June 2012 12:48:08 Eshat Cakar wrote:
> > But we will provide packages for the curious testers like you, just after
> > the  team finishes the rest of the 4.8.4 transition, which has higher
> > priority due to the wheezy freeze.
> 
> What's the status of the 4.8.4 transition? The freeze happened over a
> month  ago. Are you still busy with polishing KDE for wheezy?

Ok who do I have to bribe to get 4.8 or 4.9 KDE PIM packages? How much do you 
want? ;)

Is there anything that could be done to help with that? Is the summer to 
blame?

Regards,
Torsten


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-08-04 Thread Torsten Grote
Hi,

On Monday 18 June 2012 12:48:08 Eshat Cakar wrote:
> But we will provide packages for the curious testers like you, just after
> the  team finishes the rest of the 4.8.4 transition, which has higher
> priority due to the wheezy freeze.

What's the status of the 4.8.4 transition? The freeze happened over a month 
ago. Are you still busy with polishing KDE for wheezy?

Regards,
Torsten


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-24 Thread Dietz Pröpper
Quoting myself,

Dietz Pröpper:
[stupid stuff]

my previous mail was never intended to get sent.

Sorry for that,
Dietz


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-20 Thread Kevin Krammer
On Tuesday, 2012-06-19, Modestas Vainius wrote:

> There is nothing wrong with having "old KDE inside" if it works. That said,
> I don't claim that pim 2 does not work. We simply don't know it and it's
> too late in the game to find out (IMHO). Inexistance of a good migration
> tool helps to make the decision though.
> 
> FWIW, I'm pretty sure that migration won't ever be fixed. However, users
> will have more time to adjust at the start of the next release cycle. What
> is more, I think somebody will be kind enough and upload kdepim 4.8.4 to
> backports and wheezy users will have the best of two worlds (a choice) in
> the end.

The main problem with the migration tool is that the complexity of the mail 
setup just does not fit into the constraints of the migrator framework used for 
other data types.

I.e. for other data types it is sufficient to create one new backend connectors 
for each old backend connector and transfer the respective config.

Mail setup has folder specific config, folder and mail item specific meta data, 
etc. which requires the migrator to do a lot of mail structure and data 
processing.

This also takes way longer than what is acceptable for a migrator that runs 
automatically on first application start.

The correct solution is to make KMail2 start immediately but empty and detect 
and offer import choices.

Cheers,
Kevin


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-20 Thread Martin Steigerwald
Am Dienstag, 19. Juni 2012 schrieb Dietz Pröpper:
> Martin Steigerwald:
> > The switch to Akonadi for KMail is a big one.
> 
> And a quite questionable, too.

Everything is questionable.

But I believe that the fundamental decision to use a database for metadata 
is sound.

> > And I think even right now
> > there is no way of automatic migration thats working out okay in most
> > cases.
> 
> Wow. What do they smoke over at KDE Central?

Not a very helpful comment in my oppinion. And nothing for me to follow up 
on.

> > Thus the recommended procedure as far as I am aware of is to
> > recreate mail accounts and reimport mail from IMAP server or POP3
> > mail directory. As far as I read its usually also necessary to
> > recreate all filter rules.
> 
> Fine. I have a ~/Mail around 1G in size and a forest of filter rules.
> This "recommended procedure" is simply not feasible for me.
> 
> Add to this the quite braindama^W questionable idea to move not only
> metadata stuff but the complete maildir to akonadi, and *I* will be out
> of the game, for sure.

Even if repeated even more times it will not become true.

Akonadi is a metadata cache. Not the mail store. 

So once again also here on this list:

Please read

Akonadi misconception #1: where is my data?
http://blogs.kde.org/node/4503

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206200952.49094.mar...@lichtvoll.de



Re: KDE PIM packaging

2012-06-20 Thread Martin Steigerwald
Am Dienstag, 19. Juni 2012 schrieb Modestas Vainius:
> Hello,
> 
> On antradienis 19 Birželis 2012 19:43:12 Valerio Passini wrote:
> > martedì 19 giugno 2012
> > 
> > I could understand this point of view if:
> > 1 - a tool to ease the migration it's going to be on the way any time
> > soon (in the next 2-3 years) before the release of what will be the
> > next stable after Wheezy, but if such tool is not in anybody's mind
> > I can only complain this decision.
> > 2 - this hypothetical migration tool will still hold a meaning,
> > considering the major changes that will come in the next future like
> > the entire KDE moving from 4.x to 5.x, with likely a lot of new
> > stuff. This will doom Debian to be always lagging in respect to KDE
> > releases, to miss new technology and to support mixed KDE
> > environment with piece of "old" KDE inside. This should scare the
> > developers more than users having troubles migrating emails, IMO.
> 
> There is nothing wrong with having "old KDE inside" if it works. That
> said, I don't claim that pim 2 does not work. We simply don't know it
> and it's too late in the game to find out (IMHO). Inexistance of a
> good migration tool helps to make the decision though.
> 
> FWIW, I'm pretty sure that migration won't ever be fixed. However,
> users will have more time to adjust at the start of the next release
> cycle. What is more, I think somebody will be kind enough and upload
> kdepim 4.8.4 to backports and wheezy users will have the best of two
> worlds (a choice) in the end.

I agree.

Better let us likely a bit more experienced Debian KDE users here on the 
list test KDEPIM 2 for a while before letting it loose on all Debian KDE 
users.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206200948.51042.mar...@lichtvoll.de



Re: KDE PIM packaging

2012-06-20 Thread Martin Steigerwald
Am Montag, 18. Juni 2012 schrieb Eshat Cakar:
> Hi Torsten,
> hi Martin,
> 
> On Mon 18 June 2012 11:29:22 Martin Steigerwald wrote:
> > Am Samstag, 16. Juni 2012 schrieb Torsten Grote:
> > > I'd love to have some information, why the KDE PIM applications are
> > > at version 4.4.11.
> > 
> > The switch to Akonadi for KMail is a big one. And I think even right
> > now there is no way of automatic migration thats working out okay in
> > most cases. > Thus the recommended procedure as far as I am aware of
> > is to recreate mail accounts and reimport mail from IMAP server or
> > POP3 mail directory. As far as I read its usually also necessary to
> > recreate all filter rules.
> > 
> > I´d love to test KDEPIM 2,
> 
> As martin correctly said, Kdepim 2 lacks migration and that is one
> reason it will not be included in wheezy.
> But we will provide packages for the curious testers like you, just
> after the team finishes the rest of the 4.8.4 transition, which has
> higher priority due to the wheezy freeze.

Thanks, that great to hear.

I think that helps us to get a handle on the current situation with KDEPIM 
2. I always wanted to compile it myself, but didn´t come to it. When its 
just an apt-get install away thats easier to handle for me.

Would it be sufficient for Debian when there is a step by step migration 
guide that describes how to copy everything over manuelly by recreating 
it? I am willing to help to document such migration steps once I migrate 
to KDEPIM 2 myself.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206200945.40611.mar...@lichtvoll.de



Re: KDE PIM packaging

2012-06-20 Thread Martin Steigerwald
Am Dienstag, 19. Juni 2012 schrieb Torsten Grote:
> > As martin correctly said, Kdepim 2 lacks migration and that is one
> > reason it  will not be included in wheezy.
> 
> I'm sitting with several PIM hackers in the same office and they said
> that  using 4.4.11 programs with recent akonadi is quite
> "adventurous". Also, I'm not sure whether the migration will improve
> in the near future.

Hmmm, why?

I think its an important feature for the regular user.

> As for me, I'm ready to set up my KDE PIM accounts freshly to take
> advantage  of a more recent and stable platform.

This might be difficult for not so advanced users or people who have a "big" 
setup like me. I have to recreate about 100 filter rules and re-integrate 
CRM114 spam filtering.

I understand that a 100% complete migration might be difficult to implement 
cause there is a wide variety of setups, but at least some help for the 
basic stuff like filter rules would be really nice.

Well anyway, thats probably better a discussion on kdepim mailinglist.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


-- 
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206200934.03031.mar...@lichtvoll.de



Re: KDE PIM packaging

2012-06-19 Thread Lisandro Damián Nicanor Pérez Meyer
On Mar 19 Jun 2012 18:04:13 Modestas Vainius escribió:
> Hello,
[snip]
> There is nothing wrong with having "old KDE inside" if it works. That said,
> I don't claim that pim 2 does not work. We simply don't know it and it's
> too late in the game to find out (IMHO). 

Yes, I also think we are too late.

> Inexistance of a good migration
> tool helps to make the decision though.
> 
> FWIW, I'm pretty sure that migration won't ever be fixed. However, users
> will have more time to adjust at the start of the next release cycle. 

And we will have more time to properly announce the change. We must do our 
best to warn our users in advance that they may get data lost.

> What
> is more, I think somebody will be kind enough and upload kdepim 4.8.4 to
> backports and wheezy users will have the best of two worlds (a choice) in
> the end.

Exactly :)

-- 
Sea estricto cuando envíe y tolerante cuando reciba. En otras palabras, solo
envíe paquetes que cumplan rigurosamente con lo estándares, pero espere
paquetes que tal vez no cumplan del todo y trate de lidiar con ellos.
  Andrew S. Tanenbaum, de su libro "Computer Networks"

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-19 Thread Modestas Vainius
Hello,

On antradienis 19 Birželis 2012 19:43:12 Valerio Passini wrote:
> martedì 19 giugno 2012
> 
> I could understand this point of view if:
> 1 - a tool to ease the migration it's going to be on the way any time soon
> (in the next 2-3 years) before the release of what will be the next stable
> after Wheezy, but if such tool is not in anybody's mind I can only
> complain this decision.
> 2 - this hypothetical migration tool will still hold a meaning, considering
> the major changes that will come in the next future like the entire KDE
> moving from 4.x to 5.x, with likely a lot of new stuff. This will doom
> Debian to be always lagging in respect to KDE releases, to miss new
> technology and to support mixed KDE environment with piece of "old" KDE
> inside. This should scare the developers more than users having troubles
> migrating emails, IMO.

There is nothing wrong with having "old KDE inside" if it works. That said, I 
don't claim that pim 2 does not work. We simply don't know it and it's too 
late in the game to find out (IMHO). Inexistance of a good migration tool 
helps to make the decision though.

FWIW, I'm pretty sure that migration won't ever be fixed. However, users will 
have more time to adjust at the start of the next release cycle. What is more, 
I think somebody will be kind enough and upload kdepim 4.8.4 to backports and 
wheezy users will have the best of two worlds (a choice) in the end.

-- 
Modestas Vainius 


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-19 Thread Valerio Passini
lunedì 18 giugno 2012 Cakar ha scritto:
 
> As martin correctly said, Kdepim 2 lacks migration and that is one reason
> it will not be included in wheezy.
> But we will provide packages for the curious testers like you, just after
> the team finishes the rest of the 4.8.4 transition, which has higher
> priority due to the wheezy freeze.
> 
> Best regards

martedì 19 giugno 2012

I could understand this point of view if:
1 - a tool to ease the migration it's going to be on the way any time soon (in 
the next 2-3 years) before the release of what will be the next stable after 
Wheezy, but if such tool is not in anybody's mind I can only complain this 
decision.
2 - this hypothetical migration tool will still hold a meaning, considering 
the major changes that will come in the next future like the entire KDE moving 
from 4.x to 5.x, with likely a lot of new stuff. This will doom Debian to be 
always lagging in respect to KDE releases, to miss new technology and to 
support mixed KDE environment with piece of "old" KDE inside. This should 
scare the developers more than users having troubles migrating emails, IMO.

Just my two thought on the topic, I always love and respect the work you are 
doing for packaging KDE. Best regards

Valerio Passini


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206191843.12698.valerio.pass...@unicam.it



Re: KDE PIM packaging

2012-06-19 Thread Kevin Krammer
On Tuesday, 2012-06-19, Dietz Pröpper wrote:
> Martin Steigerwald:

> > And I think even right now
> > there is no way of automatic migration thats working out okay in most
> > cases.
> 
> Wow. What do they smoke over at KDE Central?

Cuban cigars, I recon because they go well with the Cuban rum they are 
drinking over there as well.

Fortunately nobody at KDEPIM Central smokes, though it is rumored that they 
occasionally drink beer.

The migration tool has worked quite well on my setup, though I always run it 
manually, i.e. not indirectly through starting KMail.
Seems to depend on quite some variables though, e.g. config options used, etc.

Unfortunately work on a much more flexible importer (as in support for 
pause/resume/rerun, etc) has not moved forward as anticipated due to resource 
constraints.

> > Thus the recommended procedure as far as I am aware of is to
> > recreate mail accounts and reimport mail from IMAP server or POP3 mail
> > directory. As far as I read its usually also necessary to recreate all
> > filter rules.
> 
> Fine. I have a ~/Mail around 1G in size and a forest of filter rules.
> This "recommended procedure" is simply not feasible for me.

Size of ~/Mail is mostly irrelevant, it is more a question of per-folder and 
per-message meta data, e.g. tags on messages, folder specific config options, 
etc.

> Add to this the quite braindama^W questionable idea to move not only
> metadata stuff but the complete maildir to akonadi, and *I* will be out of
> the game, for sure.

Good thing then that idea has never occured to the respective developers.

Cheers,
Kevin


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-19 Thread Dietz Pröpper
Martin Steigerwald:

> The switch to Akonadi for KMail is a big one.

And a quite questionable, too.

> And I think even right now
> there is no way of automatic migration thats working out okay in most
> cases.

Wow. What do they smoke over at KDE Central?

> Thus the recommended procedure as far as I am aware of is to
> recreate mail accounts and reimport mail from IMAP server or POP3 mail
> directory. As far as I read its usually also necessary to recreate all
> filter rules.

Fine. I have a ~/Mail around 1G in size and a forest of filter rules.
This "recommended procedure" is simply not feasible for me.

Add to this the quite braindama^W questionable idea to move not only 
metadata stuff but the complete maildir to akonadi, and *I* will be out of 
the game, for sure.

regards,
Dietz


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-19 Thread Leopold Palomo Avellaneda
A Dilluns, 18 de juny de 2012, Eshat Cakar va escriure:
> Hi Torsten,
> hi Martin,
> 
> On Mon 18 June 2012 11:29:22 Martin Steigerwald wrote:
> > Am Samstag, 16. Juni 2012 schrieb Torsten Grote:
> > > I'd love to have some information, why the KDE PIM applications are at
> > > version 4.4.11.
> > 
> > The switch to Akonadi for KMail is a big one. And I think even right now
> > there is no way of automatic migration thats working out okay in most
> > cases. > Thus the recommended procedure as far as I am aware of is to
> > recreate mail accounts and reimport mail from IMAP server or POP3 mail
> > directory. As far as I read its usually also necessary to recreate all
> > filter rules.
> > 
> > I´d love to test KDEPIM 2,
> 
> As martin correctly said, Kdepim 2 lacks migration and that is one reason
> it will not be included in wheezy.

I don't understand why it could be a reason. AFAIK there's no rule in the Dfsg 
about no include a package if upstream has not released a tool to migrate the 
configuration from one version to another. The Qt/kde team work hard from the 
migration from kde3 to kde4 with the kaboom tool. If now we don't have one, we 
cannot obey to the packagers to develop one.

However I could understand to no include it in wheeze to avoid a big amount of 
bug reports in the migration process. But, one solution could be include the 
tools of kdepim2 with another name and a readme (as others packages has 
included) with some explanation. 

Not all the debian users are squeeze users that need a perfect migration from 
a old version to a new one. There are a lot of new users, or users that change 
from gnome to kde or from another distro to debian and would like kde4 FULL.

> But we will provide packages for the curious testers like you, just after
> the team finishes the rest of the 4.8.4 transition, which has higher
> priority due to the wheezy freeze.

Perfect, but please put it in some way in wheezy. Debian deserve a full kde4, 
especially with kdepim. 

Regards,

Leo



-- 
--
Linux User 152692 PGP: 0xF944807E
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206191043.43150@alaxarxa.net



Re: KDE PIM packaging

2012-06-19 Thread Torsten Grote
On Monday 18 June 2012 12:48:08 Eshat Cakar wrote:
> But we will provide packages for the curious testers like you, just after
> the  team finishes the rest of the 4.8.4 transition, which has higher
> priority due to the wheezy freeze.

Thanks Eshat, this is great news! :)
I understand that wheezy has higher priority right now and am happy that there 
are no major blockers preventing recent KDE PIM from getting packaged.

> As martin correctly said, Kdepim 2 lacks migration and that is one reason
> it  will not be included in wheezy.

I'm sitting with several PIM hackers in the same office and they said that 
using 4.4.11 programs with recent akonadi is quite "adventurous". Also, I'm 
not sure whether the migration will improve in the near future.

As for me, I'm ready to set up my KDE PIM accounts freshly to take advantage 
of a more recent and stable platform.

Thanks again for all the great work!
Torsten


signature.asc
Description: This is a digitally signed message part.


Re: KDE PIM packaging

2012-06-18 Thread Eshat Cakar
Hi Torsten,
hi Martin,

On Mon 18 June 2012 11:29:22 Martin Steigerwald wrote:
> Am Samstag, 16. Juni 2012 schrieb Torsten Grote:
> > I'd love to have some information, why the KDE PIM applications are at
> > version 4.4.11. 
> The switch to Akonadi for KMail is a big one. And I think even right now
> there is no way of automatic migration thats working out okay in most
> cases. > Thus the recommended procedure as far as I am aware of is to
> recreate mail accounts and reimport mail from IMAP server or POP3 mail
> directory. As far as I read its usually also necessary to recreate all
> filter rules.
> 
> I´d love to test KDEPIM 2, 

As martin correctly said, Kdepim 2 lacks migration and that is one reason it 
will not be included in wheezy. 
But we will provide packages for the curious testers like you, just after the 
team finishes the rest of the 4.8.4 transition, which has higher priority due 
to the wheezy freeze.

Best regards

-- 
eshat cakar
web: www.eshat.de   gpg-id: 799B 95D5


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1866929.DrIySaJMGP@lie01



Re: KDE PIM packaging

2012-06-18 Thread Martin Steigerwald
Am Samstag, 16. Juni 2012 schrieb Torsten Grote:
> Hi,

Hi Torsten!

> thanks a lot for all your great work packaging KDE applications for
> Debian!
> 
> I'd love to have some information, why the KDE PIM applications are at
> version 4.4.11. This question is not meant to critizise or to
> complain. I'd rather like to know what's stopping the most recent
> releases from being packaged and what would help you to package them?

I am no Debian Qt/KDE packager, so this is in no way an official response.

There has been some discussion about this on this list already.

I think main question is: Is KDEPIM 2 really production ready, i.e. stable 
enough?

I get the impression from reading kdepim and kdepim-users that with 
4.8.3/4.8.4 it gets there, but I haven´t tested it.

Did you test it?

The switch to Akonadi for KMail is a big one. And I think even right now 
there is no way of automatic migration thats working out okay in most 
cases. Thus the recommended procedure as far as I am aware of is to 
recreate mail accounts and reimport mail from IMAP server or POP3 mail 
directory. As far as I read its usually also necessary to recreate all 
filter rules.

I´d love to test KDEPIM 2, but I am also still a bit reluctant. I have a 
quite insane amount of mail folders, mails and filter rules.

I am considering a parallel installation of some sort to run some tests 
for quite some time, but I didn´t take the time to do all that yet.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206181129.22373.mar...@lichtvoll.de



KDE PIM packaging

2012-06-16 Thread Torsten Grote
Hi,

thanks a lot for all your great work packaging KDE applications for Debian!

I'd love to have some information, why the KDE PIM applications are at version 
4.4.11. This question is not meant to critizise or to complain. I'd rather 
like to know what's stopping the most recent releases from being packaged and 
what would help you to package them?

Regards and keep up the good work,
Torsten


signature.asc
Description: This is a digitally signed message part.