On Monday, June 11, 2012 16:25:17 Scott Kitterman wrote:
> Currently my "About KDE" says:
>
> Platform Version 4.8.3 (4.8.3)
>
> Once kdelibs versioning is desynchronized from the rest of the platform,
> what version is it?
At least application-version and underlying-platform-version might (or
On 2012-06-11, Sebastian Kügler wrote:
> I'd consider that a bug in your packaging. There's no absolute requirement of
> an app for a specific version of kdelibs. If your packages need that, you
> should probably fix them. The decoupling of libs and apps, and especially the
> modularization of
On Monday, June 11, 2012 07:20:50 AM Sebastian Kügler wrote:
> On Sunday, June 10, 2012 01:22:03 Kevin Kofler wrote:
> > On Sunday 10 June 2012, Nicolás Alvarez wrote:
> > > Why not start now and make the next kdelibs 4.8.5? Releasing a kdelibs
> > > 4.9 will just add to the confusion of how kdelib
On Sunday, June 10, 2012 01:22:03 Kevin Kofler wrote:
> On Sunday 10 June 2012, Nicolás Alvarez wrote:
> > Why not start now and make the next kdelibs 4.8.5? Releasing a kdelibs
> > 4.9 will just add to the confusion of how kdelibs development is
> > working.
>
> Because having a kdelibs version d
> On May 28, 2012, 1:24 p.m., Andreas Schneider wrote:
> > Ship It!
>
> Andreas Schneider wrote:
> I'm fine if you push this to the repo.
I plan to push into master for KDE 4.9, but first I have to fix at least issue
#2. Issue #1 can be a TODO to be resolved. I wish I had the time to addre
> On May 28, 2012, 1:24 p.m., Andreas Schneider wrote:
> > Ship It!
I'm fine if you push this to the repo.
- Andreas
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104642/#review14234
--
Hi,
Peter Penz
> The issue has been tracked at
> https://bugs.kde.org/show_bug.cgi?id=268064 - updating Soprano to the
> latest master resolves the crash. But I don't know more about the
> root-cause of this. Probably a Nepomuk-related update missed a proper
> versioning-check of Soprano?
There
