Re: [gentoo-user] Re: KDEPIM-4.4.2015.06 blockages

[Petric Frank]

Hello,

Am Freitag, 1. Januar 2016, 23:22:54 schrieb Mick:
> On Friday 01 Jan 2016 16:49:41 James wrote:
> > Mick <michaelkintzios <at> gmail.com> writes:
> > > I am updating an old machine which does not see much usage
these days.
> > > I  came across this blockage, which seems is caused by retaining
the
> >
> > > pre-Kmail2 KDEPIM  version on this PC:
> > When upgrading old systems, always there are packages that cause
problems
> > or the attic is missing the particular version your efforts call for,
> > during the transition, is my experience; ymmv.
> >
> > > Is there a workaround for this, or does it mean time has arrived to
> > > decide  whether I will be able to continue with Kmail1 and the old
> > > KDEPIM on this  box, or not?
> >
> > When I've updated older systems, I rarely pay close attention to the
> > details, except when the progress is halted or fails. What I've learned
to
>
> > do is::
> [snip ...]
>
> > hth,
> > James
>
> Thank you James, but this is a system which has been updated regularly,
at
> least once a week.  The only exception being KDEPIM which was masked
as
> advised by the maintainers for those who found Kmail2 unsuitable for
their
> systems.  So, on this system I've stayed with 4.4 as advised here:
>
> https://wiki.gentoo.org/wiki/KDE/KDEPIM-4.7_upgrade

I did the same here. 
 
> After all these years, this is the first time that 4.4 has come up with a
> blocker, hence my email to this list.

I did the same but upgrading a 3 year old system to kde-4.14.8 but 
masking kdepim to keep version 4.4.
It adds kontact-4.14.8 and not * -4.4.2015.06 to the build tree. And as 
followup kdepim-common-libs-4.14.8 and kdepim-runtime-4.14.8.

The only fix i found so far is to disable the "kontact" use flag on all 
kdepim-4-4 packages. Then it built without problems.

Hope that helps tracking down the real problem.

regards
  Petric