public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dương \"Yang\" ヤン Hà Nguyễn" <cmpitg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDEPIM-4.7.3 hits the stable tree ... brrrrr!
Date: Thu, 8 Dec 2011 23:26:27 +0700	[thread overview]
Message-ID: <CAPGE9kQSbBgLRTdUmvdKOmg6P_mnXb0igSma7WxEQsUeYA-76A@mail.gmail.com> (raw)
In-Reply-To: <201112071912.23133.michaelkintzios@gmail.com>

On Thu, Dec 8, 2011 at 2:11 AM, Mick <michaelkintzios@gmail.com> wrote:
> Thankfully eselect news spells it out and this link makes me thing twice about
> my next steps:
>
>  http://wiki.gentoo.org/wiki/KDEPIM-4.7_upgrade
>
> Following Alan's disastrous experience where he saw all his messages disappear
> before his eyes I am doubly cautious.
>
> Has anyone tried the migration to 4.7 yet?
>
> Only to make things slightly more complicated ... has anyone tried it who's
> been using sqlite3 like I do, instead of the recommended MySQL?
>
> Any gotchas other than backups of everything recommended in the news article?
>

Hi,

In the KDEPIM full stack, I use only Kopete.  Today I upgraded both
kdepimlibs and kopete to 4.7.3.  After the upgrading, Kwallet did not
work properly (it displayed a totally blank window without any
"wallets").  I started Kopete and immediately I encountered the error
message:

   kopete(xxx) couldn't create slave: Unknown protocol 'file'

Of course Kopete did not work with Kwallet, so I had to type my
password manually.  After typing the password, nothing happened in the
Kopete window, and the error message I got from the terminal was

   kopete(xxx) couldn't create slave: Unknown protocol 'https'

At first I thought there are some broken packages, but revdep-rebuild
didn't help.  I rebuilt kdepimlibs, Kwallet, and Kopete manually with
emerge, didn't help either.  I read the news (from eselect) again,
found the wiki page, followed the direction althought I didn't use
KMail or any other piece of software from the KDEPIM stack, it didn't
work either.  Eventually, I masked the packages (mentioned in the
news) and downgraded kdepimlibs and Kopete to 4.6.3, and everything
worked again!

Just to share my short story today.  And I think KDEPIM should *not*
be marked as stable at the moment.

Kindest regards,
Dương "Yang"
-- 
Dương "Yang" ヤン Hà Nguyễn ("Nguyễn Hà Dương" in Vietnamese, 「グエンヤン」 in Japanese)
Web log: http://cmpitg.wordpress.com/
"Life is a hack"

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/C/ED/L d++ s-:-(:) !a C+++(++++) ULU++++>$ P-- L+++>$ E+++
W++>+++ N+ o+ K w--- O- M@ V- PS+ PE++ Y+>++ PGP++ t+ 5 X+ R-
tv+ b+++ DI+++ D++ G+++ e* h* r* y-
-----END GEEK CODE BLOCK-----



  parent reply	other threads:[~2011-12-08 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 19:11 [gentoo-user] KDEPIM-4.7.3 hits the stable tree ... brrrrr! Mick
2011-12-08  5:45 ` Frank Steinmetzger
2011-12-08  6:47   ` Mick
2011-12-08 14:51     ` Frank Steinmetzger
2011-12-08 19:57       ` Mick
2011-12-08 16:26 ` Dương "Yang" ヤン Hà Nguyễn [this message]
2011-12-08 22:17   ` Frank Steinmetzger
2011-12-11 19:06   ` Daniel D Jones
     [not found] <i5vc6-3Se-15@gated-at.bofh.it>
     [not found] ` <i5FXP-55F-3@gated-at.bofh.it>
     [not found]   ` <i5NC2-12J-5@gated-at.bofh.it>
     [not found]     ` <i5Sim-vr-5@gated-at.bofh.it>
2011-12-09 15:47       ` Indi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPGE9kQSbBgLRTdUmvdKOmg6P_mnXb0igSma7WxEQsUeYA-76A@mail.gmail.com \
    --to=cmpitg@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox