2:01 a.m.
So where the #$%^&*( is KDE4.1 ? And don't tell me its in testing !
I don't want to be a beta tester anymore.
9:32 a.m.
On Tue, Sep 2, 2008 at 2:01 AM, linuxguy <linuxguy123(a)gmail.com> wrote:
So where the #$%^&*( is KDE4.1 ? And don't tell me its in
testing !
I don't want to be a beta tester anymore.
The infrastructure issues have put a serious delay on all packages
that needed to be moved from updates-testing to updates.
But I've installed KDE 4.1 on three different machines so far, what's
holding you back?
--
Fedora 7 : sipping some of that moonshine
( www.pembo13.com )
9:41 a.m.
linuxguy wrote:
So where the #$%^&*( is KDE4.1 ? And don't tell me its in
testing !
If it makes you feel better, we had queue'd it for stable shortly before all
the security hubbub, and it's been blocking on getting that all sorted out
first.
<tinfoil hat>
It was a kde-hating hacker that did it, if only to delay getting kde
goodness to the masses. :)
</tinfoil hat>
-- Rex
3:23 a.m.
On Tue, 2008-09-02 at 09:41 -0500, Rex Dieter wrote:
linuxguy wrote:
> So where the #$%^&*( is KDE4.1 ? And don't tell me its in testing !
If it makes you feel better, we had queue'd it for stable shortly before all
the security hubbub, and it's been blocking on getting that all sorted out
first.
So are you saying that KDE4.1 is sitting in testing, but that if it
weren't for the security stuff it would be in stable ?
If so, how do I easily install ONLY KDE4.1 from testing without
installing a bunch of unstable stuff ?
Thanks.
10:57 a.m.
On Tue, Sep 2, 2008 at 3:23 AM, linuxguy <linuxguy123(a)gmail.com> wrote:
On Tue, 2008-09-02 at 09:41 -0500, Rex Dieter wrote:
> linuxguy wrote:
>
> > So where the #$%^&*( is KDE4.1 ? And don't tell me its in testing !
>
> If it makes you feel better, we had queue'd it for stable shortly before all
> the security hubbub, and it's been blocking on getting that all sorted out
> first.
So are you saying that KDE4.1 is sitting in testing, but that if it
weren't for the security stuff it would be in stable ?
If so, how do I easily install ONLY KDE4.1 from testing without
installing a bunch of unstable stuff ?
Thanks.
This is what I did:
# yum --enablerepo=updates-testing groupinstall kde-desktop
--
Fedora 7 : sipping some of that moonshine
( www.pembo13.com )
11:31 a.m.
On Tuesday 02 September 2008 17:02:58 linuxguy wrote:
On Tue, 2008-09-02 at 10:57 -0500, Arthur Pemberton wrote:
> This is what I did:
>
> # yum --enablerepo=updates-testing groupinstall kde-desktop
Doing it in the yum command like that only enables it for that one occasion.
You don't need to do anything more - it stays disabled if that's what your
repo file says.
Anne
11:25 a.m.
On Tue, 2008-09-02 at 10:57 -0500, Arthur Pemberton wrote:
yum --enablerepo=updates-testing groupinstall kde-desktop
Its not finding KDE4.1 by the looks of it.
yum --enablerepo=updates-testing groupinstall kde-desktop
Loaded plugins: priorities, refresh-packagekit
Setting up Group Process
comps-f9.xml
| 1.3 MB 00:03
Package kdebase-workspace-4.0.5-3.fc9.i386 already installed and latest
version
Package digikam-0.9.4-2.fc9.i386 already installed and latest version
Package kaffeine-0.8.6-4.fc9.i386 already installed and latest version
Package zenity-2.22.1-1.fc9.i386 already installed and latest version
Package konversation-1.0.1-6.fc9.i386 already installed and latest
version
Package 7:kdegraphics-4.0.5-1.fc9.i386 already installed and latest
version
Package 6:kdemultimedia-4.0.5-1.fc9.i386 already installed and latest
version
Package kpowersave-0.7.3-3.fc9.i386 already installed and latest version
Package 1:NetworkManager-gnome-0.7.0-0.9.4.svn3675.fc9.i386 already
installed and latest version
Package 6:kdepim-3.5.9-10.fc9.i386 already installed and latest version
Package 6:kdebase-4.0.5-5.fc9.i386 already installed and latest version
Package kdeartwork-4.0.5-2.fc9.i386 already installed and latest version
Package kipi-plugins-0.1.5-2.fc9.i386 already installed and latest
version
Package 6:kdegames-4.0.5-1.fc9.i386 already installed and latest version
Package 6:kdeutils-4.0.5-1.fc9.i386 already installed and latest version
Package kftpgrabber-0.8.1-6.fc9.i386 already installed and latest
version
Package 7:kdenetwork-4.0.5-3.fc9.i386 already installed and latest
version
Package kde-settings-pulseaudio-4.0-25.fc9.noarch already installed and
latest version
Package pinentry-qt-0.7.4-5.fc9.i386 already installed and latest
version
Package amarok-1.4.9.1-3.fc9.i386 already installed and latest version
Package 1:kdeaccessibility-4.0.5-1.fc9.i386 already installed and latest
version
Package ktorrent-3.0.2-3.fc9.i386 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package extragear-plasma.i386 0:4.0.1-5.fc9 set to be updated
---> Package ksshaskpass.i386 0:0.4-2.fc9 set to be updated
---> Package kdeedu.i386 0:4.0.5-2.fc9 set to be updated
--> Processing Dependency: libgps.so.17 for package: kdeedu
--> Processing Dependency: kdeedu-libs = 4.0.5-2.fc9 for package: kdeedu
--> Processing Dependency: libkdeeduui.so.4 for package: kdeedu
--> Processing Dependency: libcfitsio.so.0 for package: kdeedu
--> Processing Dependency: libnova-0.12.so.1 for package: kdeedu
--> Processing Dependency: libmarblewidget.so.4 for package: kdeedu
--> Processing Dependency: libcompoundviewer.so.4 for package: kdeedu
--> Processing Dependency: libavogadro-kalzium.so.0 for package: kdeedu
--> Processing Dependency: libkiten.so.4 for package: kdeedu
--> Processing Dependency: libkeduvocdocument.so.4 for package: kdeedu
--> Processing Dependency: libSatLib.so.4 for package: kdeedu
--> Processing Dependency: libsbigudrv.so.1 for package: kdeedu
--> Processing Dependency: libopenbabel.so.3 for package: kdeedu
--> Processing Dependency: libscience.so.4 for package: kdeedu
---> Package scribus.i386 0:1.3.4-5.fc9 set to be updated
--> Processing Dependency: tkinter for package: scribus
--> Running transaction check
---> Package libnova.i386 0:0.12.1-3.fc9 set to be updated
---> Package gpsd.i386 0:2.37-2.fc9 set to be updated
---> Package cfitsio.i386 0:3.060-3.fc9 set to be updated
---> Package openbabel.i386 0:2.2.0-1.fc9 set to be updated
--> Processing Dependency: libinchi.so.1 for package: openbabel
---> Package tkinter.i386 0:2.5.1-26.fc9 set to be updated
--> Processing Dependency: libTix.so for package: tkinter
---> Package kdeedu-libs.i386 0:4.0.5-2.fc9 set to be updated
--> Running transaction check
---> Package tix.i386 1:8.4.2-5.fc9 set to be updated
---> Package inchi.i386 0:1.0.2-0.3.fc9 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================
Package Arch Version Repository
Size
=============================================================================
Installing:
extragear-plasma i386 4.0.1-5.fc9 fedora
466 k
kdeedu i386 4.0.5-2.fc9 updates
42 M
ksshaskpass i386 0.4-2.fc9 fedora
18 k
scribus i386 1.3.4-5.fc9 fedora
10 M
Installing for dependencies:
cfitsio i386 3.060-3.fc9 fedora
1.4 M
gpsd i386 2.37-2.fc9 fedora
187 k
inchi i386 1.0.2-0.3.fc9 fedora
563 k
kdeedu-libs i386 4.0.5-2.fc9 updates
638 k
libnova i386 0.12.1-3.fc9 fedora
1.1 M
openbabel i386 2.2.0-1.fc9 updates
2.4 M
tix i386 1:8.4.2-5.fc9 fedora
268 k
tkinter i386 2.5.1-26.fc9 updates
219 k
Transaction Summary
=============================================================================
Install 12 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 60 M
Is this ok [y/N]: y
11 a.m.
On Tue September 2 2008 09:23:17 linuxguy wrote:
On Tue, 2008-09-02 at 09:41 -0500, Rex Dieter wrote:
> linuxguy wrote:
> > So where the #$%^&*( is KDE4.1 ? And don't tell me its in testing !
>
> If it makes you feel better, we had queue'd it for stable shortly before
> all the security hubbub, and it's been blocking on getting that all
> sorted out first.
So are you saying that KDE4.1 is sitting in testing, but that if it
weren't for the security stuff it would be in stable ?
Yes he is, read up on how the bits reach you and what you can do.
If so, how do I easily install ONLY KDE4.1 from testing without
installing a bunch of unstable stuff ?
Your idea of stability may need an adjustment, If you trust your mirror do:
# sudo yum update kde\* --enablerepo=updates-testing
...dex
1:47 p.m.
On Tue, 2008-09-02 at 17:00 +0100, dexter wrote:
On Tue September 2 2008 09:23:17 linuxguy wrote:
> On Tue, 2008-09-02 at 09:41 -0500, Rex Dieter wrote:
> > linuxguy wrote:
> > > So where the #$%^&*( is KDE4.1 ? And don't tell me its in
testing !
> >
> > If it makes you feel better, we had queue'd it for stable shortly before
> > all the security hubbub, and it's been blocking on getting that all
> > sorted out first.
>
> So are you saying that KDE4.1 is sitting in testing, but that if it
> weren't for the security stuff it would be in stable ?
Yes he is, read up on how the bits reach you and what you can do.
> If so, how do I easily install ONLY KDE4.1 from testing without
> installing a bunch of unstable stuff ?
Your idea of stability may need an adjustment, If you trust your mirror do:
# sudo yum update kde\* --enablerepo=updates-testing
Or: yum --enablerepo=updates-testing groupupdate KDE
poc
2:06 p.m.
On Tue, Sep 2, 2008 at 1:47 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
On Tue, 2008-09-02 at 17:00 +0100, dexter wrote:
> On Tue September 2 2008 09:23:17 linuxguy wrote:
> > On Tue, 2008-09-02 at 09:41 -0500, Rex Dieter wrote:
> > > linuxguy wrote:
> > > > So where the #$%^&*( is KDE4.1 ? And don't tell me its in
testing !
> > >
> > > If it makes you feel better, we had queue'd it for stable shortly
before
> > > all the security hubbub, and it's been blocking on getting that all
> > > sorted out first.
> >
> > So are you saying that KDE4.1 is sitting in testing, but that if it
> > weren't for the security stuff it would be in stable ?
>
> Yes he is, read up on how the bits reach you and what you can do.
>
> > If so, how do I easily install ONLY KDE4.1 from testing without
> > installing a bunch of unstable stuff ?
>
> Your idea of stability may need an adjustment, If you trust your mirror do:
> # sudo yum update kde\* --enablerepo=updates-testing
Or: yum --enablerepo=updates-testing groupupdate KDE
I wish that option was listed in `yum -h`
--
Fedora 7 : sipping some of that moonshine
( www.pembo13.com )
2:20 p.m.
Around 08:06pm on Tuesday, September 02, 2008 (UK time), Arthur Pemberton scrawled:
> Or: yum --enablerepo=updates-testing groupupdate KDE
I wish that option was listed in `yum -h`
It is:
(steve@jackdaw:~)$ yum -h | grep enab
--enablerepo=[repo] enable one or more repositories (wildcards allowed)
--obsoletes enable obsoletes processing during updates
Steve
--
(o< www.stevesearle.com
//\ Powered by Fedora
V_/_ No MS products were used in the creation of this message
20:18:41 up 19 days, 8:40, 1 user, load average: 0.06, 0.20, 0.10
2:40 p.m.
On Tue, Sep 2, 2008 at 2:20 PM, Steve Searle <steve(a)stevesearle.com> wrote:
Around 08:06pm on Tuesday, September 02, 2008 (UK time), Arthur
Pemberton scrawled:
> > Or: yum --enablerepo=updates-testing groupupdate KDE
>
>
> I wish that option was listed in `yum -h`
It is:
(steve@jackdaw:~)$ yum -h | grep enab
--enablerepo=[repo] enable one or more repositories (wildcards allowed)
--obsoletes enable obsoletes processing during updates
referring to 'groupupdate'
--
Fedora 7 : sipping some of that moonshine
( www.pembo13.com )
3:10 p.m.
On Tue, 2008-09-02 at 14:40 -0500, Arthur Pemberton wrote:
On Tue, Sep 2, 2008 at 2:20 PM, Steve Searle
<steve(a)stevesearle.com> wrote:
> Around 08:06pm on Tuesday, September 02, 2008 (UK time), Arthur Pemberton scrawled:
>
>> > Or: yum --enablerepo=updates-testing groupupdate KDE
>>
>>
>> I wish that option was listed in `yum -h`
>
> It is:
>
> (steve@jackdaw:~)$ yum -h | grep enab
> --enablerepo=[repo] enable one or more repositories (wildcards allowed)
> --obsoletes enable obsoletes processing during updates
referring to 'groupupdate'
It's in the yum manual, but yes it should also be in the help. File a
bug.
poc
5:34 p.m.
Patrick O'Callaghan <pocallaghan <at> gmail.com> writes:
Or: yum --enablerepo=updates-testing groupupdate KDE
And that groupupdate will miss some packages which should also be updated. (I
know, I've done it myself. I had to use yum shell and manually update some
additional packages which weren't caught by the groupupdate.) kde* will also
miss some stuff, e.g. konq-plugins.
Moreover, the packages currently in updates-testing are missing the latest
fixes (for the same reason the update isn't stable yet), so unless you're
prepared to pick those from Koji, you'd better just wait for the update to be
pushed to stable (with those fixes, which are already in the queued update).
You'll also end up with the GStreamer Phonon backend only if you update from
testing now unless you manually force phonon-backend-xine, and that GStreamer
backend has problems with device selection which could cause problems with
PulseAudio. In the update queued for stable, we have:
* made phonon-backend-gstreamer the longer name again, so yum prefers
phonon-backend-xine if you're upgrading from 4.0,
* fixed some regressions in PulseAudio support in the Xine backend (requires
updated phonon, phonon-backend-xine and kdebase-runtime).
Kevin Kofler
6 p.m.
On Tue, 2008-09-02 at 22:34 +0000, Kevin Kofler wrote:
Patrick O'Callaghan <pocallaghan <at> gmail.com>
writes:
> Or: yum --enablerepo=updates-testing groupupdate KDE
And that groupupdate will miss some packages which should also be updated. (I
know, I've done it myself. I had to use yum shell and manually update some
additional packages which weren't caught by the groupupdate.) kde* will also
miss some stuff, e.g. konq-plugins.
I can only say that I've had zero problems of this nature since I did
the above a month ago. The whole update went without a hitch. Maybe I'm
just lucky.
If groupupdate misses some stuff, are there plans to fix it so it
doesn't?
Moreover, the packages currently in updates-testing are missing the
latest
fixes (for the same reason the update isn't stable yet), so unless you're
prepared to pick those from Koji, you'd better just wait for the update to be
pushed to stable (with those fixes, which are already in the queued update).
True. I haven't seen anything new since around August 8.
You'll also end up with the GStreamer Phonon backend only if you
update from
testing now unless you manually force phonon-backend-xine, and that GStreamer
backend has problems with device selection which could cause problems with
PulseAudio. In the update queued for stable, we have:
* made phonon-backend-gstreamer the longer name again, so yum prefers
phonon-backend-xine if you're upgrading from 4.0,
* fixed some regressions in PulseAudio support in the Xine backend (requires
updated phonon, phonon-backend-xine and kdebase-runtime).
Good to know. However my own experience has been that previous to
updating from updates-testing I had a buggy KDE and now I have a
considerably less buggy one, so it's been a net gain for me.
poc
5733
days inactive
5733
days old
15 comments
8 participants
participants (8)
-
Anne Wilson -
Arthur Pemberton -
dexter -
Kevin Kofler -
linux guy -
Patrick O'Callaghan -
Rex Dieter -
Steve Searle