Am Sonntag, 3. Mai 2015, 21:11:27 schrieb Markus Raab:
> Hello,
>
> Martin Steigerwald wrote:
> > I think it would be good to have a newer KDEPIM + Akonadi into Jessie.
> >
> > Why? The current akonadi 1.13 master branch together with kdepim,
> > kdepimlibs, kdepim-runtime from 4.14 branches (as
Hello,
Rainer Dorsch wrote:
> are there any cons of having 4.14.7 in one of the next point releases and
> KDE5 via backports for jessie?
>
> I understand that in general new upstream releases are not supposed to
> pushed in in point releases. In this case it makes perfect sense for me
> though an
Hi,
On Wednesday 13 May 2015 09:31:57 Lisandro Damián Nicanor Pérez Meyer wrote:
> > I might try to build 4.14.7 packages for Jessie myself. I've been
> > following the discussion for a while, and my understanding is
> > that supplying 4.14.7 packages with jessie-backports would block
> > the back
Hello,
Jimmy Johnson wrote:
> "KDE updated in Debian, here's how. In this guide we will see how to
> have KDE in Debian constantly updated thanks to third-party repositories
> KDEbian."
> http://media-opensource.blogspot.com/2014/09/kde-updated-in-debian-heres-
how.html
The article is only talkin
Hey,
well very interesting, what you found :) The kolab team for the desktop team
has two members christian and me. And am the only one you is reponsible for
debian builds. But I never known about thiis https://ftp.kolab.org :) Thanks
for this information, I'll check internally why these 3.5.X
Hi Sandro,
Am Mittwoch 13 Mai 2015, 16:58:48 schrieb Sandro Knauß:
> Hi,
>
> > > (No kidding: the Kolab people do package their own
> > > enterprise
> > > version of KDE, and they *do* ship KDEPIM 3.5.10 with
> > > it...).
>
> well as one of the kdepim/kolab devs i can say: you are wrong!
>
> T
Hi,
> > (No kidding: the Kolab people do package their own enterprise
> > version of KDE, and they *do* ship KDEPIM 3.5.10 with it...).
well as one of the kdepim/kolab devs i can say: you are wrong!
There is a enterprise version of kontact (4.13.0.X) [0]. As you can see from
the version number
On Wednesday 13 May 2015 09:07:19 you wrote:
> Hi Lisandro,
>
> Am Dienstag 12 Mai 2015, 17:26:33 schrieb Lisandro Damián Nicanor
>
> Pérez Meyer:
> > Don't mix external packages. That's all.
>
> Well, that's good advice. However, the Debian team in all its
> wisdom (no sarcasm!) decided to stuf
Am Mittwoch 13 Mai 2015, 08:35:00 schrieb Alejandro Exojo:
> El Tuesday 12 May 2015, Jimmy Johnson escribió:
> > Christian this is what I get after running the upgrade:
> (...)
>
> > I was a little concerned with ruby being removed so I did not
> > complete the upgrade.
>
> I think that you are m
El Tuesday 12 May 2015, Jimmy Johnson escribió:
> Christian this is what I get after running the upgrade:
(...)
> I was a little concerned with ruby being removed so I did not complete
> the upgrade.
I think that you are missing the point. Christian's concern wasn't how to do
the installation, o
Hi Jimmy,
Am Dienstag 12 Mai 2015, 07:53:12 schrieb Jimmy Johnson:
> [...]
> Christian this is what I get after running the upgrade:
> jimmy# upgrade-system
> 1) Updating package lists:
> I: Package lists updated.
> 2) Checking for upgradable packages:
> I: Installing upgradable packages...
> Rea
On 05/12/2015 07:34 AM, Christian Hilberg wrote:
Hi Jimmy,
Am Dienstag 12 Mai 2015, 07:02:04 schrieb Jimmy Johnson:
On 05/12/2015 02:02 AM, Christian Hilberg wrote:
Hi all,
seeking for a less-painful-than-self-compile way to get
KDEPIM
4.14.7 into Debian/Jessie (for much the same reasons as
p
Hi Jimmy,
Am Dienstag 12 Mai 2015, 07:02:04 schrieb Jimmy Johnson:
> On 05/12/2015 02:02 AM, Christian Hilberg wrote:
> > Hi all,
> >
> > seeking for a less-painful-than-self-compile way to get
> > KDEPIM
> > 4.14.7 into Debian/Jessie (for much the same reasons as
> > pointed out by the OP), I st
On 05/12/2015 02:02 AM, Christian Hilberg wrote:
Hi all,
seeking for a less-painful-than-self-compile way to get KDEPIM
4.14.7 into Debian/Jessie (for much the same reasons as pointed
out by the OP), I stumbled across
http://kdebian.org/ppa/
While this repo seems to have all of the pac
El Tuesday 12 May 2015, Christian Hilberg escribió:
> Hi all,
>
> seeking for a less-painful-than-self-compile way to get KDEPIM
> 4.14.7 into Debian/Jessie (for much the same reasons as pointed
> out by the OP), I stumbled across
>
> http://kdebian.org/ppa/
>
> While this repo seems to ha
Hi all,
seeking for a less-painful-than-self-compile way to get KDEPIM
4.14.7 into Debian/Jessie (for much the same reasons as pointed
out by the OP), I stumbled across
http://kdebian.org/ppa/
While this repo seems to have all of the packages I'm after, I do
not really know to make he
Hello,
Martin Steigerwald wrote:
> I think it would be good to have a newer KDEPIM + Akonadi into Jessie.
>
> Why? The current akonadi 1.13 master branch together with kdepim,
> kdepimlibs, kdepim-runtime from 4.14 branches (as of 4.14.6/7) here runs
> better than ever before, including my most a
Am Samstag, 18. April 2015, 14:25:35 schrieb Sandro Knauß:
> Hey,
>
> > I do not want a separate dev environment, but I want to compile
> > selected components of KDE for production use – and maybe also some
> > developing some time. So I want Alt-F2 (or with Plasma 5 Alt-Space)
> > to pick up my
Hey,
> I do not want a separate dev environment, but I want to compile selected
> components of KDE for production use – and maybe also some developing some
> time. So I want Alt-F2 (or with Plasma 5 Alt-Space) to pick up my self-
> compiled kmail, while everything else from packaged KDE still wor
Am Samstag, 18. April 2015, 11:54:46 schrieb Martin Steigerwald:
> > after running the script you have to do something like:
> >
> >
> > setKDEEnv master
> >
> >
> >
> > Okay it additionally also makes sure that you have different home dirs
> > etc.
> >
> >
> >
> > In your case the folling env v
Am Dienstag, 14. April 2015, 13:17:56 schrieb Sandro Knauß:
> Hi,
>
> > I use default /usr/local location and do as little customization of
> > the
> > build process as possible. Then I tell my KDE sessions to use
> > /usr/local
> > stuff as well like this:
> This does not touch all relevant env v
Hi,
> I use default /usr/local location and do as little customization of the
> build process as possible. Then I tell my KDE sessions to use /usr/local
> stuff as well like this:
This does not touch all relevant env variables (see attached script). It is
configured to have
~/kde/src//kdepim -
Am Donnerstag, 26. März 2015, 14:49:35 schrieb Rainer Dorsch:
> Hi Martin,
Hi Rainer,
> thanks for sharing your positive experience. I agree, getting these kind
> of KDEPIM fixes through backports would be a great enhancement for
> Jessie KDE users.
>
> Do you compile to /opt or do you build pro
Hi Martin,
thanks for sharing your positive experience. I agree, getting these kind of
KDEPIM
fixes through backports would be a great enhancement for Jessie KDE users.
Do you compile to /opt or do you build proper Debian packages of the upstream
akonadi and kdepim?
Though having the backport
On Thursday 26 March 2015 13:06:40 Martin Steigerwald wrote:
> Hi!
>
> I think it would be good to have a newer KDEPIM + Akonadi into Jessie.
>
> Why? The current akonadi 1.13 master branch together with kdepim,
> kdepimlibs, kdepim-runtime from 4.14 branches (as of 4.14.6/7) here runs
> better t
Hi!
I think it would be good to have a newer KDEPIM + Akonadi into Jessie.
Why? The current akonadi 1.13 master branch together with kdepim,
kdepimlibs, kdepim-runtime from 4.14 branches (as of 4.14.6/7) here runs
better than *ever* before, including my most annoying bug
[Akonadi] [Bug 343114]
26 matches
Mail list logo
