Concerning `fedora-release'

[Harry Putnam]

How is the updating of fedora-release pkg supposed to work?  I've run
an extensive and complete update off of rawhide, but my release
package is still fedora-release-2.90-3.

Running `yum --obsoletes update fedora-release' doesn't find a package
of that name of course.

Harry Putnam wrote:

> How is the updating of fedora-release pkg supposed to work?  I've
> run
> an extensive and complete update off of rawhide, but my release
> package is still fedora-release-2.90-3.
>
> Running `yum --obsoletes update fedora-release' doesn't find a package
> of that name of course.
>   
>  
my new filter in mozilla:

"sender" "contains" "harry putnam"
"delete the message"

-- 
shrek-m

[Féliciano Matias]

Le samedi 04 décembre 2004 à 11:27 -0600, Harry Putnam a écrit :
>  How is the updating of fedora-release pkg supposed to work?  I've
> run
>  an extensive and complete update off of rawhide, but my release
>  package is still fedora-release-2.90-3.
>  
>  Running `yum --obsoletes update fedora-release' doesn't find a package
>  of that name of course.
>   
You have fedora-release-2.90-3.i386.rpm (i386).
Rawhide use fedora-release-3-rawhide.noarch (noarch).

Use "rpm -U fedora-release-3-rawhide.noarch.rpm."

[seth vidal]

On Sat, 2004-12-04 at 11:27 -0600, Harry Putnam wrote:
>  How is the updating of fedora-release pkg supposed to work?  I've
> run
>  an extensive and complete update off of rawhide, but my release
>  package is still fedora-release-2.90-3.
>  
>  Running `yum --obsoletes update fedora-release' doesn't find a package
>  of that name of course.
>   
the reason for that is that there is an arch change from i386 to noarch.

you can set exactarch=0 in your yum.conf then yum will notice it.

quick survey - should exactarch be a cli option so you can turn it off
w/o editing the config file?

-sv

[Jef Spaleta]

On Sat, 04 Dec 2004 15:14:33 -0500, seth vidal <skvidal(a)phy.duke.edu&gt; wrote:
>  quick survey - should exactarch be a cli option so you can turn it
> off
>  w/o editing the config file? 
There will always be pressure to expand the cli options to encompass
all possible configuration options.  Instead of implementing
individual cli --options for each global switch. Perhaps it would be
better to implement a general option that takes global configuration
file chunk strings, so multiple switches can just be parsed from one
argument string.

As for exposing exactarch with its own cli --option, it would surely
make it easier to communicate to novice users, instructions in faqs if
there was a yum one liner for specific upgrade problems introduced by
changing a package to noarch.

-jef

[Harry Putnam]

&quot;shrek-m(a)gmx.de&quot; <shrek-m(a)gmx.de&gt; writes:

>  my new filter in mozilla:
>
>  "sender" "contains" "harry putnam"
>  "delete the message" 
What a wimpy filter... they should at least be case sensitive.  After
all this is unix....   And the old term `kill file' would sound so
much  .... tougher. 

`Delete'.... jeez... what a wimp