Oh for goodness sake.

[glennzo]

What on earth is the problem with Yum / PackageKit / RPMFusion? Why, after several years worth of work on these features, can we not have a reliable method for updating the system or installing software? Why do these features continuously fail to do their jobs? Why do they refuse to work? I can't update any one of 5 Fedora systems this morning. Three are F12 and 2 are F11. Some are desktop boxes, one is my laptop and a couple are running under VirtualBox. Nothing works! This morning we can't resolve rpmfusion. What? It was working well last night. What happened? Tomorrow it will be something else. This morning, on more than one box, PackageKit refuses to give up it's lock on the system and I have to forcefully kill it so I can try to use yum. A few days ago I needed to research a problem with yum on an F13 / Rawhide box. Turns out I had to downgrade libcurl. Who knew? That took some time to be sure. What will it be tomorrow? Yes, I know, this is Fedora. It's bleeding edge and things break, but for goodness sake, one would think that there could at the very least be a few reliable constants here. Instead of introducing new features maybe the developers should shift some effort over to making sure a few important ones continue to work as expected. I can do without some of the new features but I can't do without a reliable means of updating the system. Yum and related programs are proving, once again, to be extremely annoying.

[bob]

You mean yum's actually WORKING in Rawhide? :eek: It's been a week for me and nada.

OTOH, we've had some server shifting that had messed things for a day or two, but otherwise my F11 and F12 yums are doing fine.

[David Batson]

The latest gtk2 updates break Yum Extender.

http://forums.fedoraforum.org/showpost.php?p=1307842&postcount=11

[leigh123linux]

It's all working here :( , I guess that means I have some free time to answer some posts here :( and work on some bugs in the packages I maintain :p :)

[leigh123linux]

The latest gtk2 updates break Yum Extender.

http://forums.fedoraforum.org/showpost.php?p=1307842&postcount=11


This will solve it :)


su
yum erase yumex

[glennzo]

You mean yum's actually WORKING in Rawhide? :eek: It's been a week for me and nada.Same for me, until I downgraded libcurl.

OTOH, we've had some server shifting that had messed things for a day or two, but otherwise my F11 and F12 yums are doing fine.That was last week and was supposed to be completed in a few days.

[glennzo]

The latest gtk2 updates break Yum Extender.

http://forums.fedoraforum.org/showpost.php?p=1307842&postcount=11Yumex? Don't use it.

[glennzo]

This will solve it :)


su
yum erase yumex

I like that resolution :p

[leigh123linux]

This is from the rpmfusion devel list




Message: 1
Date: Fri, 18 Dec 2009 19:59:29 +0100
From: Adrian Reber
Subject: mirrorlist server outage
To: rpmfusion-developers@lists.rpmfusion.org
Message-ID: <20091218185928.GF5949@lisas.de>
Content-Type: text/plain; charset=us-ascii

Both networks the mirrorlist servers are located in will be off line
tomorrow for up to ten hours. I was just informed about this outage,
sorry that I was not able to announce it earlier.

This means that any access to the mirrorlist will probably result in
a timeout.

Adrian


------------------------------



------------------------------

Message: 3
Date: Fri, 18 Dec 2009 20:07:58 -0500
From: Stewart Adam
Subject: Re: mirrorlist server outage
To: RPM Fusion developers discussion list
<rpmfusion-developers@lists.rpmfusion.org>
Message-ID: <4B2C276E.5030707@diffingo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 2009/12/18 1:59 PM, Adrian Reber wrote:
> Both networks the mirrorlist servers are located in will be off line
> tomorrow for up to ten hours. I was just informed about this outage,
> sorry that I was not able to announce it earlier.
>
> This means that any access to the mirrorlist will probably result in
> a timeout.
>
> Adrian
>
How quickly can we temporarily move the mirrorlist? I don't mind setting up
a static one on my server, we would just need to reroute DNS.

Stewart

[glennzo]

Yeah? That figures. Thank you Leigh :)

[scottro]

I haven't run into any major breakage either. I don't use packagekit or yumex though.

[PavanKY]

scot, do you mean you do not use them regularly, or have other alternatives ?

[scottro]

I don't use them at all. I use yum from the command line.

[PavanKY]

Pardon my ignorance but I thought packagedit and yum used the same background files..

[Wayne]

Remove PackageSpit. I have done on my F11 system and those versions previously that have included it. That's after I remove mono :D

[scottro]

@silentfreak, I don't know. However, the problems mentioned here seem to do with the graphic tools. Whether they're the factor, the back end is the problem, or I've just been lucky in timing my updates, I don't know. (I tend to only investigate things that affect me.) :)

[leigh123linux]

@silentfreak, I don't know. However, the problems mentioned here seem to do with the graphic tools. Whether they're the factor, the back end is the problem, or I've just been lucky in timing my updates, I don't know. (I tend to only investigate things that affect me.) :)


The problem is with the front-end i.e yumex or packagekit

[marko]

Remove PackageSpit. I have done on my F11 system and those versions previously that have included it. That's after I remove mono

I'd like to remove PackageKit but it has a dependency with setroubleshoot which I don't want to remove

[marcrblevins]

I don't use PackageKit or Yumex either. Well, I accepted PackageKit from time to time.

However, I use my own cron script to run 'yum -y update', sends me e-mail as well:

[marc@kiriyamablevins ~]$ cat /etc/cron.daily/0kyum.cron
#!/bin/sh

ROOT_UID=0 # Only users with $UID 0 have root privileges.
E_NOTROOT=67 # Non-root exit error.

# Run as root, of course.
if [ "$UID" -ne "$ROOT_UID" ]; then
echo "Must be root to run this script."
exit $E_NOTROOT
fi

/usr/bin/yum -e 0 -d 0 -y update | (cat <<EOF
This is an automated report of $0 on the server `hostname -s`.

yum -y update
EOF
cat
) | /bin/mail -s "[yum -y update]" root
[marc@kiriyamablevins ~]$]

[Hlingler]

I'd like to remove PackageKit but it has a dependency with setroubleshoot which I don't want to removeI saw that too - it seems to be a new dependency in F12 - but as much as I wanted to keep setroubleshoot, I wanted PackageKit gone more. BTW: setroubleshoot re-installed with 'rpm --nodeps ...' afterward and it fails to open. Oh, well. I wonder if setroubleshoot can be re-built without PackageKit... .

V

EDIT: Back on topic:Yes, I know, this is Fedora. It's bleeding edge and things break, but for goodness sake, one would think that there could at the very least be a few reliable constants here. Instead of introducing new features maybe the developers should shift some effort over to making sure a few important ones continue to work as expected.I concur 110%. There seems to be some perverse mentality, that when something is finally stable and works, the "powers that be" (or someone with some "new/better idea") cannot keep their goddam hands off it and let people just plain use and enjoy it. Seems like we're always trying to hit a moving target.

No doubt someone will be along shortly to suggest the usual responses ("Go create your own spin/distro", "Get involved", etc., etc., etc. ad nauseum).

[RahulSundaram]

Hi,

The problems had nothing whatsoever to do with Yum, or PackageKit but infrastructure downtimes and one curl problem. There is also the confusion between PackageKit (which is just a framework) and gnome-packagekit or kpackagekit which provides the UI. If you don't want the UI, you can just remove that and leave the framework alone.

[bbfuller]

Certainly, if you tick the right boxes in KPackageKit you never get bothered again. I assume there is the same functionality in gnome-packagekit?

[RahulSundaram]

Hi,

Sure.

[Dies]

Certainly, if you tick the right boxes in KPackageKit you never get bothered again. I assume there is the same functionality in gnome-packagekit?

Yes, the problem is that people become frustrated with early versions of software. Usually because they're pushed too soon and are still rough and missing features or in some cases just plain broken.

So then they get used to just removing it, which is understandable, problem is they never bother seeing how far it's actually come or how much better than the old one it actually is, they tend to just cling to their first impression of it. ;)

[marcrblevins]

Didn't know there was a GUI for it. Thought it only gives you the task icon and dialog pop ups. I accepted thoses to updates.

Tried GUI of KPackageKit, 'Automatically Install: None', is the default. Changed it to 'All Updates'.

Now I'll see which comes first, my yum script or KPackageKit.

Happy Holidays!

[bbfuller]

Talk about different approaches.

I left that setting as it was, but the one where it said "check for updates", I set to "Never"!

I do that regularly enough for myself.