conflicted file in update this morning?

2009-08-03 Thread Alan Evans
Came to work this morning and updater icon told me that updates were available on my F11 system. Pretty routine, I told it to go ahead and do the update. What wasn't routine was the subsequent error dialog complaining of Local file conflict between packages: Test Transaction Errors: file

Re: conflicted file in update this morning?

2009-08-03 Thread Tom Horsley
On Mon, 3 Aug 2009 09:04:32 -0700 Alan Evans wrote: Anyway, today I can't update. Can anything be done? Or should this get bugzilla'd? And if so, against what? Usually if you just wait a few days the 32 and 64 bit repos get back in sync. You can update with the --skip-broken option to get all

Re: conflicted file in update this morning?

2009-08-03 Thread Alan Evans
On Mon, Aug 3, 2009 at 9:20 AM, Tom Horsley wrote: On Mon, 3 Aug 2009 09:04:32 -0700 Alan Evans wrote: Anyway, today I can't update. Can anything be done? Or should this get bugzilla'd? And if so, against what? Usually if you just wait a few days the 32 and 64 bit repos get back in sync.

Re: conflicted file in update this morning?

2009-08-03 Thread Alan Evans
On Mon, Aug 3, 2009 at 9:20 AM, Tom Horsley wrote: On Mon, 3 Aug 2009 09:04:32 -0700 Alan Evans wrote: Anyway, today I can't update. Can anything be done? Or should this get bugzilla'd? And if so, against what? Usually if you just wait a few days the 32 and 64 bit repos get back in sync.

Re: conflicted file in update this morning?

2009-08-03 Thread Frank Murphy
On 03/08/09 17:44, Alan Evans wrote: Anyway, cli yum updated everything with no complaint. But I'm wondering why PackageKit was conflicted about the number of available updates. (And I'm wondering what the bold/not-bold thing in yum means.) -Alan iirc bold=going to be installed

Re: conflicted file in update this morning?

2009-08-03 Thread Alan Evans
On Mon, Aug 3, 2009 at 9:47 AM, Frank Murphy wrote: iirc bold=going to be installed normal=updating That can't be it. Today's updates were all already installed packages. Where should users go to find out? It's in none of the docs that I can find. From my current evidence, it seems to be:

Re: conflicted file in update this morning?

2009-08-03 Thread Kevin Fenzi
On Mon, 3 Aug 2009 10:30:43 -0700 Alan Evans ame.fed...@gmail.com wrote: On Mon, Aug 3, 2009 at 9:47 AM, Frank Murphy wrote: iirc bold=going to be installed normal=updating That can't be it. Today's updates were all already installed packages. Where should users go to find out? It's in

Re: conflicted file in update this morning?

2009-08-03 Thread Alan Evans
On Mon, Aug 3, 2009 at 10:32 AM, Kevin Fenzi wrote: On Mon, 3 Aug 2009 10:30:43 -0700 Alan Evans wrote: That can't be it. Today's updates were all already installed packages. Where should users go to find out? It's in none of the docs that I can find. man yum.conf search down for 'color'.

Re: conflicted file in update this morning?

2009-08-03 Thread Rick Stevens
Alan Evans wrote: On Mon, Aug 3, 2009 at 10:32 AM, Kevin Fenzi wrote: On Mon, 3 Aug 2009 10:30:43 -0700 Alan Evans wrote: That can't be it. Today's updates were all already installed packages. Where should users go to find out? It's in none of the docs that I can find. man yum.conf search

Re: conflicted file in update this morning?

2009-08-03 Thread James Bridge
On Mon, 2009-08-03 at 09:04 -0700, Alan Evans wrote: Came to work this morning and updater icon told me that updates were available on my F11 system. Pretty routine, I told it to go ahead and do the update. What wasn't routine was the subsequent error dialog complaining of Local file

Re: conflicted file in update this morning?

2009-08-03 Thread Alan Evans
On Mon, Aug 3, 2009 at 12:22 PM, Rick Stevens wrote: Alan Evans wrote: Normal, non-bold, means that the package is to be reinstalled because the available package is the same version as the installed package. In such a case, I'm curious why yum thinks it needs to be updated at all. It's