kde-4.7.4, kde-4.7.90 news

[Rex Dieter]

alrighty, just to drop a quick status update:

kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available 
in kde-testing too

kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably 
missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently 
known broken deps that will require other packages to be (re)build include 
at least: digikam (and kipi-plugins), kdevelop

Enjoy.

-- rex

[Colin J Thomson]

Hi Rex,

On Thursday 08 Dec 2011 16:46:36 Rex Dieter wrote:
> alrighty, just to drop a quick status update:
>
> kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available
> in kde-testing too
>
> kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably
> missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently
> known broken deps that will require other packages to be (re)build include
> at least: digikam (and kipi-plugins), kdevelop
>
> Enjoy.

I'm enjoying :-) updated to 4.7.90 f16 earlier and as always a very smooth 
update, I removed digikam for the time being.

Now for the serious testing.

As always thanks again to everyone involved.

Colin

[Peter G.]

Rex Dieter wrote:
> kde-4.7.4 f16 builds are built

I wondered why you had bothered with these last week, when...
> kde-4.7.90 f16 initial builds have been pushed to kde-unstable

this had just been released.

Installing now.

Great stuff!!!

[Peter G.]

Rex Dieter wrote:
> kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably
> ... spilt kdeaccessibility packaging.

OK, I see the split kdeaccessibility packaging.

I had to manually uninstall the old kdeaccessibility and install kaccessible; 
however, there is no jovie (text-to-speech).

Is jovie no longer part of kde4?

[Kevin Kofler]

Peter Gueckel wrote:
> I had to manually uninstall the old kdeaccessibility and install
> kaccessible; however, there is no jovie (text-to-speech).
>
> Is jovie no longer part of kde4?

Is is, but it's part of the stuff that's "notably missing" in our current 
packaging.

Upstream provides kdeaccessibility (only) in split form now, and split 
kdeaccessibility packages are under review.

Kevin Kofler

[Peter G.]

Kevin Kofler wrote:
> Peter Gueckel wrote:
> > Is jovie no longer part of kde4?
> It is, but it's part of the stuff that's "notably missing" in our current
> packaging.

I'm glad to hear that it's still around. Thanks.

[Genes MailLists]

On 12/08/2011 05:46 PM, Rex Dieter wrote:
> alrighty, just to drop a quick status update:
>
> kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available 
> in kde-testing too
>
> kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably 
> missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently 
> known broken deps that will require other packages to be (re)build include 
> at least: digikam (and kipi-plugins), kdevelop

(1) Thanks as always for your efforts (kevin too).

(2) Does anyone happen to know if/when the KDE internet proxy tool
will support socks (4.7.90 maybe?) - code was committed at end of
october 2011 [*] tho it seems to not be in 4.7.4.

The work around is still to create your own proxy.pac file - which
actually is a great solution and very general.

thx,

gene

[*] https://bugs.kde.org/show_bug.cgi?id=189019

[T.C. Hollingsworth]

On Fri, Dec 9, 2011 at 7:13 AM, Genes MailLists  wrote:
> On 12/08/2011 05:46 PM, Rex Dieter wrote:
> > alrighty, just to drop a quick status update:
> >
> > kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available
> > in kde-testing too
> >
> > kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably
> > missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently
> > known broken deps that will require other packages to be (re)build include
> > at least: digikam (and kipi-plugins), kdevelop
>
> (1) Thanks as always for your efforts (kevin too).
>
> (2) Does anyone happen to know if/when the KDE internet proxy tool
> will support socks (4.7.90 maybe?) - code was committed at end of
> october 2011 [*] tho it seems to not be in 4.7.4.

Yep, 4.7.90 has this.

-T.C.

[Genes MailLists]

On 12/09/2011 09:17 AM, T.C. Hollingsworth wrote:
> > (2) Does anyone happen to know if/when the KDE internet proxy tool
> > will support socks (4.7.90 maybe?) - code was committed at end of
> > october 2011 [*] tho it seems to not be in 4.7.4.
>
> Yep, 4.7.90 has this.

Wonderful - thank you.

[Rex Dieter]

On 12/09/2011 08:13 AM, Genes MailLists wrote:
> (2) Does anyone happen to know if/when the KDE internet proxy tool
> will support socks (4.7.90 maybe?) - code was committed at end of
> october 2011 [*] tho it seems to not be in 4.7.4.
> [*] https://bugs.kde.org/show_bug.cgi?id=189019

My understanding is that commit went into the master branch, which is 
what is included now in 4.7.90.

-- rex

[T.C. Hollingsworth]

On Thu, Dec 8, 2011 at 3:46 PM, Rex Dieter  wrote:
> alrighty, just to drop a quick status update:
>
> kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available
> in kde-testing too
>
> kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably
> missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently
> known broken deps that will require other packages to be (re)build include
> at least: digikam (and kipi-plugins), kdevelop

Thanks!  Looks pretty good for the most part.

Since I've updated, for some reason my screen keeps going black after
a couple minutes even though Screen Energy Saving has been and still
is disabled for all 3 power profiles.  Not sure if this could be
Fedora-specific or if I should file it upstream.

Apart from that, I have only run into a few minor issues that are
definitely upstream's problem.

Thanks,
T.C.

[Colin J Thomson]

Hi,

On Friday 09 Dec 2011 07:37:34 T.C. Hollingsworth wrote:
> Since I've updated, for some reason my screen keeps going black after
> a couple minutes even though Screen Energy Saving has been and still
> is disabled for all 3 power profiles.  Not sure if this could be
> Fedora-specific or if I should file it upstream.

I saw this after the updates also, I set xset -dpms but something triggered it 
to back on. However this evening the screen has only went off once, could be a 
hard one to trace.

F16 kernel-3.1.5-1.fc16.x86_64
qt-4.8.0-0.23.rc1.fc16.x86_64

Others things of note so far..

Kmix seems to be eating lots of CPU again :-

https://bugs.kde.org/show_bug.cgi?id=237239
https://bugs.kde.org/show_bug.cgi?id=264292

These are shown as fixed and the indeed where in 4.7.x

Nasty Kmail crash on exit has been fixed

https://bugs.kde.org/show_bug.cgi?id=288141

The other CPU eater seems to be virtuoso, so I plan to do some searching on 
kde.bugs over the weekend time permitting.

Cheers

Colin

[T.C. Hollingsworth]

On Fri, Dec 9, 2011 at 5:23 PM, Colin J Thomson  wrote:
> On Friday 09 Dec 2011 07:37:34 T.C. Hollingsworth wrote:
> > Since I've updated, for some reason my screen keeps going black after
> > a couple minutes even though Screen Energy Saving has been and still
> > is disabled for all 3 power profiles.  Not sure if this could be
> > Fedora-specific or if I should file it upstream.
>
> I saw this after the updates also, I set xset -dpms but something triggered it
> to back on. However this evening the screen has only went off once, could be a
> hard one to trace.

Glad I'm not the only one. ;-)
> F16 kernel-3.1.5-1.fc16.x86_64
> qt-4.8.0-0.23.rc1.fc16.x86_64
>
> Others things of note so far..
>
> Kmix seems to be eating lots of CPU again :-
>
> https://bugs.kde.org/show_bug.cgi?id=237239

I reopened this one; I'm seeing it too.
> https://bugs.kde.org/show_bug.cgi?id=264292
>
> These are shown as fixed and the indeed where in 4.7.x
>
> Nasty Kmail crash on exit has been fixed
>
> https://bugs.kde.org/show_bug.cgi?id=288141
>
> The other CPU eater seems to be virtuoso, so I plan to do some searching on
> kde.bugs over the weekend time permitting.

-T.C.

[T.C. Hollingsworth]

On Fri, Dec 9, 2011 at 5:48 PM, T.C. Hollingsworth
 wrote:
> I reopened this one; I'm seeing it too.
> > https://bugs.kde.org/show_bug.cgi?id=264292

Sorry, shouldn't have done that.  It's now filed at:
https://bugs.kde.org/show_bug.cgi?id=288619

[Colin J Thomson]

On Friday 09 Dec 2011 17:55:10 T.C. Hollingsworth wrote:
> On Fri, Dec 9, 2011 at 5:48 PM, T.C. Hollingsworth
>
>  wrote:
> > I reopened this one; I'm seeing it too.
> > > https://bugs.kde.org/show_bug.cgi?id=264292
>
> Sorry, shouldn't have done that.  It's now filed at:
> https://bugs.kde.org/show_bug.cgi?id=288619

I guess I should of said "possibly" related to those bug # I posted.. thanks 
for confirming your seeing it to though.

Colin

[Genes MailLists]

Am trying to install 4.7.4 on F15 via fedora-kde47 ... I get this issue:

Error: Package: ardour-2.8.12-1.fc15.x86_64 (@updates)
           Requires: librasqal.so.2()(64bit)
           Removing: rasqal-0.9.21-2.fc15.x86_64 (@fedora)
               librasqal.so.2()(64bit)
           Updated By: rasqal-0.9.27-1.fc15.x86_64 (fedora-kde47)
               Not found
 You could try using --skip-broken to work around the problem

Whats the 'proper' way of dealing with this?

thanks!

gene.

[Genes MailLists]

On 12/11/2011 11:48 PM, Genes MailLists wrote:
> Am trying to install 4.7.4 on F15 via fedora-kde47 ... I get this issue:
>
> Error: Package: ardour-2.8.12-1.fc15.x86_64 (@updates)
>            Requires: librasqal.so.2()(64bit)
>            Removing: rasqal-0.9.21-2.fc15.x86_64 (@fedora)
>                librasqal.so.2()(64bit)
>            Updated By: rasqal-0.9.27-1.fc15.x86_64 (fedora-kde47)
>                Not found
>  You could try using --skip-broken to work around the problem

I tried --skip-broken ... now I get this:

Error: Protected multilib versions: dbusmenu-qt-0.8.2-0.2.fc15.x86_64 !=
dbusmenu-qt-0.6.3-3.fc15.x86_64
Error: Protected multilib versions: raptor-1.4.21-10.fc15.x86_64 !=
raptor-1.4.21-2.fc15.x86_64

[Genes MailLists]

On 12/11/2011 11:51 PM, Genes MailLists wrote:
> On 12/11/2011 11:48 PM, Genes MailLists wrote:
> > Am trying to install 4.7.4 on F15 via fedora-kde47 ... I get this issue:
> >
> > Error: Package: ardour-2.8.12-1.fc15.x86_64 (@updates)
> >            Requires: librasqal.so.2()(64bit)
> >            Removing: rasqal-0.9.21-2.fc15.x86_64 (@fedora)
> >                librasqal.so.2()(64bit)
> >            Updated By: rasqal-0.9.27-1.fc15.x86_64 (fedora-kde47)
> >                Not found
> >  You could try using --skip-broken to work around the problem

For now I am deleting ardour ... that at least lets the update
continue ...

kmix (in 4.7.90 eating cpu/memory)

[Rex Dieter]

T.C. Hollingsworth wrote:
> On Fri, Dec 9, 2011 at 5:48 PM, T.C. Hollingsworth
>  wrote:
> > I reopened this one; I'm seeing it too.
> > > https://bugs.kde.org/show_bug.cgi?id=264292
>
> Sorry, shouldn't have done that.  It's now filed at:
> https://bugs.kde.org/show_bug.cgi?id=288619

Filed 
https://bugzilla.redhat.com/show_bug.cgi?id=766678
locally for tracking purposes.

-- rex

[José Abílio Matos]

On 12/08/2011 10:46 PM, Rex Dieter wrote:
> currently 
> known broken deps that will require other packages to be (re)build include 
> at least: digikam (and kipi-plugins), kdevelop

Are you sure regarding digikam?

I have kdesdk-* packages hold for broken packages, due to kdevelop, but
I have no problem with digikam... only with marble (and that probably is
related with digikam now that I think about it).

It always help to talk about the problems to find solutions... :-)

[Rex Dieter]

On 12/09/2011 09:31 AM, José Matos wrote:
> On 12/08/2011 10:46 PM, Rex Dieter wrote:
> > currently
> > known broken deps that will require other packages to be (re)build include
> > at least: digikam (and kipi-plugins), kdevelop
>
> Are you sure regarding digikam?
>
> I have kdesdk-* packages hold for broken packages, due to kdevelop, but
> I have no problem with digikam... only with marble (and that probably is
> related with digikam now that I think about it).

You would be correct. :)

digikam's libkgeomap depends on marble's libmarblewidget.so which bumped 
soname.

-- rex

[Gilboa Davara]

On Fri, Dec 9, 2011 at 12:46 AM, Rex Dieter  wrote:
> alrighty, just to drop a quick status update:
>
> kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available
> in kde-testing too
>
> kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably
> missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently
> known broken deps that will require other packages to be (re)build include
> at least: digikam (and kipi-plugins), kdevelop
>
> Enjoy.
>
> -- rex

w/ kde-unstable enabled on F16/x86_64, I'm not seeing 4.7.90 only
4.7.4 (kde-testing) - even after yum clean all.
Are all the mirrors synced?
(fp.heanet.ie and apt.de-kde-redhat.org in my case)

- Gilboa

[Patrick Boutilier]

On 12/12/2011 07:28 AM, Gilboa Davara wrote:
> On Fri, Dec 9, 2011 at 12:46 AM, Rex Dieter  wrote:
> > alrighty, just to drop a quick status update:
> >
> > kde-4.7.4 f16 builds are built, queue'd for updates-testing, and available
> > in kde-testing too
> >
> > kde-4.7.90 f16 initial builds have been pushed to kde-unstable.  notably
> > missing here is kde-l10n, and spilt kdeaccessibility packaging.  currently
> > known broken deps that will require other packages to be (re)build include
> > at least: digikam (and kipi-plugins), kdevelop
> >
> > Enjoy.
> >
> > -- rex
>
> w/ kde-unstable enabled on F16/x86_64, I'm not seeing 4.7.90 only
> 4.7.4 (kde-testing) - even after yum clean all.
> Are all the mirrors synced?
> (fp.heanet.ie and apt.de-kde-redhat.org in my case)

I see 4.7.90 packages in:

http://ftp.heanet.ie/pub/kde-redhat/fedora/16/x86_64/unstable/RPMS/
> Gilboa
>
> kde mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org

[Gilboa Davara]

On Mon, Dec 12, 2011 at 1:45 PM, Patrick Boutilier  wrote:
> On 12/12/2011 07:28 AM, Gilboa Davara wrote:
> > w/ kde-unstable enabled on F16/x86_64, I'm not seeing 4.7.90 only
> > 4.7.4 (kde-testing) - even after yum clean all.
> > Are all the mirrors synced?
> > (fp.heanet.ie and apt.de-kde-redhat.org in my case)
>
> I see 4.7.90 packages in:
> http://ftp.heanet.ie/pub/kde-redhat/fedora/16/x86_64/unstable/RPMS/

Weird. Stale repodata?

- Gilboa

[Rex Dieter]

On 12/12/2011 07:49 AM, Gilboa Davara wrote:
> On Mon, Dec 12, 2011 at 1:45 PM, Patrick Boutilier  wrote:
> > On 12/12/2011 07:28 AM, Gilboa Davara wrote:
> > > w/ kde-unstable enabled on F16/x86_64, I'm not seeing 4.7.90 only
> > > 4.7.4 (kde-testing) - even after yum clean all.
> > > Are all the mirrors synced?
> > > (fp.heanet.ie and apt.de-kde-redhat.org in my case)
> >
> > I see 4.7.90 packages in:
> > http://ftp.heanet.ie/pub/kde-redhat/fedora/16/x86_64/unstable/RPMS/
>
> Weird. Stale repodata?

I'll remove the stale apt.de mirror for now. It is run by another fedora 
contributor (aka heffer), and switched boxes recently... I dropped the 
ball to get the apt.de dns updated properly.

-- rex

[Rex Dieter]

On 12/12/2011 08:18 AM, Rex Dieter wrote:
> On 12/12/2011 07:49 AM, Gilboa Davara wrote:
> > On Mon, Dec 12, 2011 at 1:45 PM, Patrick Boutilier   wrote:
> > > On 12/12/2011 07:28 AM, Gilboa Davara wrote:
> > > > w/ kde-unstable enabled on F16/x86_64, I'm not seeing 4.7.90 only
> > > > 4.7.4 (kde-testing) - even after yum clean all.
> > > > Are all the mirrors synced?
> > > > (fp.heanet.ie and apt.de-kde-redhat.org in my case)
> > >
> > > I see 4.7.90 packages in:
> > > http://ftp.heanet.ie/pub/kde-redhat/fedora/16/x86_64/unstable/RPMS/
> >
> > Weird. Stale repodata?
>
> I'll remove the stale apt.de mirror for now.

Here's the hint:
http://apt.de.kde-redhat.org/kde-redhat/timestamp

All other mirrors should say Dec 10 (or newer) by now.

-- rex