Problem with today's "yum update"

[Mike Klinke]

I'm guessing others will run into this with this morning's updates.

"yum update" errored out and quit with the display below.  

============ yum error =============

Traceback (most recent call last):
  File "/usr/share/yum-cli/yummain.py", line 139, in ?
    main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 94, in main
    (result, resultmsgs) = base.buildTransaction()
  File "/usr/lib/python2.3/site-packages/yum/__init__.py", line 130,
in buildTransaction
    (rescode, restring) = self.resolveDeps()
  File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 157,
in resolveDeps
    (checkdep, missing, conflict, errormsgs) = 
self._processConflict(dep)
  File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 351,
in _processConflict
    msg = '%s conflicts: %s' % (name,
rpmUtils.miscutils.formatRequire(needname, needversion, flags))
NameError: global name 'name' is not defined

=====================================

I filed a bug which was quickly marked as closed due to the problem 
having been fixed in the version of yum that "yum update" was going 
to download and install this morning.  I manually downloaded the 
new yum rpm and installed it.  After running the new yum I then 
received the error: 

#yum update
.........
Resolving Dependencies
Error: xorg-x11-font-utils conflicts:  xorg-x11-base-fonts<= 
6.7.99.903-3

and after excluding "xorg-x11" the "yum update" then completed. I 
presume that simply excluding "xorg-x11" would have allowed the yum 
update with yesterday's version to complete.  Hope this helps 
someone else and I'm off to file a bug against "xorg-x11" if it 
hasn't already been done.

Regards, Mike Klinke

[Jef Spaleta]

On Sat, 4 Sep 2004 09:31:00 -0500, Mike Klinke <lsomike(a)futzin.com&gt; wrote:
>  received the error:
>  
>  #yum update
>  .........
>  Resolving Dependencies
>  Error: xorg-x11-font-utils conflicts:  xorg-x11-base-fonts<=
>  6.7.99.903-3
>  
>  and after excluding "xorg-x11" the "yum update" then completed. I
>  presume that simply excluding "xorg-x11" would have allowed the yum
>  update with yesterday's version to complete.  Hope this helps
>  someone else and I'm off to file a bug against "xorg-x11" if it
>  hasn't already been done. 
You are confusing things that are going on to some extent.
There first thing you saw with the traceback was a real error in yum
2.1.2,  which yum 2.1.3 should fix.

The  conflict error you see is a REAL packaging conflict between the
old version of xorg you had installed and the new version of xorg in
rawhide. Its a packaging conflict because the items in the xorg
packages have been restructured in the new rawhide version.

instead of excluding that xorg package, try  yum --obsoletes update
the new xorg packages uses the rpm concept of "obsoleting" to handle
the problem of restructuring of package payloads.

-jef

[Paul F. Johnson]

Hi,

>  instead of excluding that xorg package, try  yum --obsoletes update
>  the new xorg packages uses the rpm concept of "obsoleting" to handle
>  the problem of restructuring of package payloads. 
--obsoletes is not listed as an option anymore.

That said, I'm getting this when I try to do an update. yum gets to the
resolving dependencies stage and then...

Traceback (most recent call last):
  File "/usr/share/yum-cli/yummain.py", line 139, in ?
    main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 94, in main
    (result, resultmsgs) = base.buildTransaction() 
  File "/usr/lib/python2.3/site-packages/yum/__init__.py", line 130, in
buildTransaction
    (rescode, restring) = self.resolveDeps()
  File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 157, in
resolveDeps
    (checkdep, missing, conflict, errormsgs) = self._processConflict
(dep)
  File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 351, in
_processConflict
    msg = '%s conflicts: %s' % (name, rpmUtils.miscutils.formatRequire
(needname, needversion, flags))
NameError: global name 'name' is not defined

Looks like something is broken.

TTFN

Paul
-- 
"Our enemies are innovative and resourceful - and so are we,"
"They never stop thinking about new ways to harm our country and our
people - and neither do we." - George W. Bush, Aug 2004

[Jef Spaleta]

On Sat, 04 Sep 2004 15:59:06 +0100, Paul <paul(a)all-the-johnsons.co.uk&gt; wrote:
>  That said, I'm getting this when I try to do an update. yum gets
> to the
>  resolving dependencies stage and then... 
did you install yum 2.1.3 yet?

[Paul F. Johnson]

Hi,

>  > That said, I'm getting this when I try to do an update. yum
> gets to the
>  > resolving dependencies stage and then...
>  
>  did you install yum 2.1.3 yet? 
Still on 2.1.2. yum is in part of the updates.

TTFN

Paul
-- 
"Our enemies are innovative and resourceful - and so are we,"
"They never stop thinking about new ways to harm our country and our
people - and neither do we." - George W. Bush, Aug 2004

Paul wrote:

> >>That said, I'm getting this when I try to do an update.
> yum gets to the
> >>resolving dependencies stage and then...
> >>      
> >>
> >did you install yum 2.1.3 yet?
> >    
> >
> Still on 2.1.2. yum is in part of the updates.
>  
# yum -y update ; sleep 30s ; yum -y --obsolete update

seems to work.


it seems that both are ok
--obsolete
--obsoletes

thanks :-)

-- 
shrek-m

shrek-m(a)gmx.de wrote:

>  # yum -y update ; sleep 30s ; yum -y --obsolete update 

oops, should be

# yum -y update yum ; sleep 30s ; yum -y --obsolete update

-- 
shrek-m

[Gene Heskett]

On Saturday 04 September 2004 12:33, shrek-m(a)gmx.de wrote:
> yum --obsolete update 
after putting in yum-2.1.3 with rpm after downloading it, I get this:
[root@coyote packages]# yum --obsolete update
Setting up Update Process
Setting up Repo:  updates-released
repodata/repomd.xml: [Errno 4] IOError: HTTP Error 404: Not Found
Cannot open/read repomd.xml file for repository: updates-released
failure: repodata/repomd.xml from updates-released: [Errno 256] No 
more mirrors to try.

And I get this same error regardless of the repo I try.

Pointers?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.25% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

[Oldman]

On Sat, 2004-09-04 at 23:06 -0400, Gene Heskett wrote:
>  On Saturday 04 September 2004 12:33, shrek-m(a)gmx.de wrote:
>  >yum --obsolete update
>  
>  after putting in yum-2.1.3 with rpm after downloading it, I get this:
>  [root@coyote packages]# yum --obsolete update
>  Setting up Update Process
>  Setting up Repo:  updates-released
>  repodata/repomd.xml: [Errno 4] IOError: HTTP Error 404: Not Found
>  Cannot open/read repomd.xml file for repository: updates-released
>  failure: repodata/repomd.xml from updates-released: [Errno 256] No 
>  more mirrors to try.
>   
	Did you mean to send this to the test-list?  I don't believe that
YUM-2.1.3 is ready for FC2 yet.  If you're on test 1 though:

	Did you perhaps use a non - standard yum-conf ?
recently YUM has gone through some changes and in order for a mirror to
be useful, it must change the structure a little.  One is the addition
of the repomd.xml (I guess that is the repository maintenance data?)
anyway the only mirror usable right now is:


[development]
name=Fedora Core $releasever - Development Tree
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/developme...




HTH

Scott


>  And I get this same error regardless of the repo I try.
>  
>  Pointers?
>  
>  -- 
>  Cheers, Gene
>  "There are four boxes to be used in defense of liberty:
>   soap, ballot, jury, and ammo. Please use in that order."
>  -Ed Howdershelt (Author)
>  99.25% setiathome rank, not too shabby for a WV hillbilly
>  Yahoo.com attorneys please note, additions to this message
>  by Gene Heskett are:
>  Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
>  
>   
-- 
When in doubt -- Vote 'Em out!

[Gene Heskett]

On Sunday 05 September 2004 00:55, Scott Talbot wrote:
> On Sat, 2004-09-04 at 23:06 -0400, Gene Heskett wrote:
> > On Saturday 04 September 2004 12:33, shrek-m(a)gmx.de wrote:
> > >yum --obsolete update
> >
> > after putting in yum-2.1.3 with rpm after downloading it, I get
> > this: [root@coyote packages]# yum --obsolete update
> > Setting up Update Process
> > Setting up Repo:  updates-released
> > repodata/repomd.xml: [Errno 4] IOError: HTTP Error 404: Not Found
> > Cannot open/read repomd.xml file for repository: updates-released
> > failure: repodata/repomd.xml from updates-released: [Errno 256] No
> > more mirrors to try.
>
>  Did you mean to send this to the test-list?  I don't believe that
> YUM-2.1.3 is ready for FC2 yet.  If you're on test 1 though: 
Duh!  I'm subbed to both, and sort them to a common mailbox, sorry.

>  Did you perhaps use a non - standard yum-conf ? 
I put my repo list back in place after the 2.1.3 install overwrote it.

> recently YUM has gone through some changes and in order for a mirror
>  to be useful, it must change the structure a little.  One is the
>  addition of the repomd.xml (I guess that is the repository
>  maintenance data?) anyway the only mirror usable right now is: 
I went after 2.1.3 because of so many messages about 2.1.2 being 
fubar, and my own FC2 2.0.7 had quit working, always exiting with a 
library not available to upgrade samba.  So samba is half busted  
here, I can mount my old 7.3 firewalls drives, but the firewall 
cannot mount my drives, something about the security model changing.
As this was quite some time back, I haven't been able to use the yum 
util to keep the system up2date in a couple of months.

So what version of yum should I have installed and *working* on an FC2 
system?
> [development]
> name=Fedora Core $releasever - Development Tree
> baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/deve
> lopment/$basearch/ 
Which is the wrong branch for me, my bad.  And I should seperate these 
lists into their own folder, but kmails folder list is more than 
screen high now.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.25% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

[Oldman]

On Sat, 2004-09-04 at 23:06 -0400, Gene Heskett wrote:

>  after putting in yum-2.1.3 with rpm after downloading it, I get
> this:
>  [root@coyote packages]# yum --obsolete update
>  Setting up Update Process
>  Setting up Repo:  updates-released
>  repodata/repomd.xml: [Errno 4] IOError: HTTP Error 404: Not Found
>  Cannot open/read repomd.xml file for repository: updates-released
>  failure: repodata/repomd.xml from updates-released: [Errno 256] No 
>  more mirrors to try.
>   
	Did you mean to send this to the test-list?  I don't believe that
YUM-2.1.3 is ready for FC2 yet.  If you're on test 1 though:

OOPS! didn't look close enough.  Obviously you're on test list.  Guess I'll go
to bed


	Did you perhaps use a non - standard yum-conf ?
recently YUM has gone through some changes and in order for a mirror to
be useful, it must change the structure a little.  One is the addition
of the repomd.xml (I guess that is the repository maintenance data?)
anyway the only mirror usable right now is:


[development]
name=Fedora Core $releasever - Development Tree
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/developme...




HTH

Scott


>  And I get this same error regardless of the repo I try.
>  
>  Pointers?
>  
>  --  
-- 
When in doubt -- Vote 'Em out!

[Gene Heskett]

On Saturday 04 September 2004 12:08, shrek-m(a)gmx.de wrote:
> yum -y update ; sleep 30s ; yum -y --obsolete update 
Doesn't work here, its stuck on samba because libcups.so.2 is not an 
rpm install.  Samba would probably work if I could tell yum to ignore 
the deps on that one.  To get that to work, I'd have to reinstall the 
rpms of a year+ old, badly broken cups build, so broken that just 
hovering the mouse over a printer related item in the kde popups will 
crash kde.  But crashing kde must seem like a good idea to 
gnome-lover redhat, it hasn't been fixed yet.  Installing a later, 
good version of cups fixes that unconditionally.

That also means I'm still stuck on yum-2.0.7

It also means I'm stuck for no really good reason as gftp, when 
attempting to access the repo and grab this stuff anyway, needs a 
fscking password other than anonymous.

Shame on redhat.  This stuff is supposedly under the GPL and should be 
freely available.  Accessing ayo.freshrpms.net can be done with gftp, 
but all files are zero length, before, and after, downloading them.

Humm, found a http site halfway around the planet that let me in and 
got lots of that stuff.  Includeing rpms of the cups I have 
installed.  So I'll shut up for a bit.  Maybe, just maybe, this will 
get me up2date with current FC2 installs...

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.25% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

[Mike Klinke]

On Saturday 04 September 2004 10:14, Paul wrote:
>  Hi,
>
>  > > That said, I'm getting this when I try to do an update. yum
>  > > gets to the resolving dependencies stage and then...
>  >
>  > did you install yum 2.1.3 yet?
>
>  Still on 2.1.2. yum is in part of the updates.
>
>  TTFN
>
>  Paul 
Paul,

You're just going down the same path I did this morning. Try this:

1. Manually download the new yum package (2.1.3.)
2. Install it. ( rpm -Uvh yum-blah-blah )
3. Issue the "yum --oblsoletes upate" command

The --obsoletes switch is undocumented in the man pages but it does 
indeed work.  Here's a link to a discussion last March that may be 
of interest:

http://marc.theaimsgroup.com/?l=fedora-test-list&m=108304807037994&am...

Regards, Mike Klinke

[Mike Klinke]

On Saturday 04 September 2004 09:40, Jeff Spaleta wrote:
 
>  There first thing you saw with the traceback was a real error in
>  yum 2.1.2,  which yum 2.1.3 should fix. 
This is what trying to say, but, of course, why say it with only a 
few words when a whole saga can be written .... 

>  The  conflict error you see is a REAL packaging conflict between
>  the old version of xorg you had installed and the new version of
>  xorg in rawhide. Its a packaging conflict because the items in
>  the xorg packages have been restructured in the new rawhide
>  version.
>
>  instead of excluding that xorg package, try  yum --obsoletes
>  update the new xorg packages uses the rpm concept of "obsoleting"
>  to handle the problem of restructuring of package payloads.
>
>  -jef 
Thanks for the clue on "--obsoletes".  I hadn't read any discussion 
of the different "obsoleting" method for xorg-x11 packages. How did 
you become aware of this?

Regards, Mike Klinke

[Robert L Cochran]

How do I deal with this error as a result of running 

'yum -y --obsoletes update':

Transaction Check Error: package katana-1.0.4-4 is already installed

Thanks

Bob Cochran
Greenbelt, Maryland, USA


On Sat, 2004-09-04 at 09:31 -0500, Mike Klinke wrote:
>  I'm guessing others will run into this with this morning's
> updates.
>  
>  "yum update" errored out and quit with the display below.  
>  
>  ============ yum error =============
>  
>  Traceback (most recent call last):
>    File "/usr/share/yum-cli/yummain.py", line 139, in ?
>      main(sys.argv[1:])
>    File "/usr/share/yum-cli/yummain.py", line 94, in main
>      (result, resultmsgs) = base.buildTransaction()
>    File "/usr/lib/python2.3/site-packages/yum/__init__.py", line 130,
>  in buildTransaction
>      (rescode, restring) = self.resolveDeps()
>    File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 157,
>  in resolveDeps
>      (checkdep, missing, conflict, errormsgs) = 
>  self._processConflict(dep)
>    File "/usr/lib/python2.3/site-packages/yum/depsolve.py", line 351,
>  in _processConflict
>      msg = '%s conflicts: %s' % (name,
>  rpmUtils.miscutils.formatRequire(needname, needversion, flags))
>  NameError: global name 'name' is not defined
>  
>  =====================================
>  
>  I filed a bug which was quickly marked as closed due to the problem 
>  having been fixed in the version of yum that "yum update" was going 
>  to download and install this morning.  I manually downloaded the 
>  new yum rpm and installed it.  After running the new yum I then 
>  received the error: 
>  
>  #yum update
>  .........
>  Resolving Dependencies
>  Error: xorg-x11-font-utils conflicts:  xorg-x11-base-fonts<= 
>  6.7.99.903-3
>  
>  and after excluding "xorg-x11" the "yum update" then completed. I 
>  presume that simply excluding "xorg-x11" would have allowed the yum 
>  update with yesterday's version to complete.  Hope this helps 
>  someone else and I'm off to file a bug against "xorg-x11" if it 
>  hasn't already been done.
>  
>  Regards, Mike Klinke
>  
>

[Mike Klinke]

On Saturday 04 September 2004 13:43, Robert L Cochran wrote:
>  How do I deal with this error as a result of running
>
>  'yum -y --obsoletes update':
>
>  Transaction Check Error: package katana-1.0.4-4 is already
>  installed
>  
This is just a guess to get you past the error ..... will excluding 
that package offer any help?  ( --exclude=katana* )

Regards, Mike Klinke

[Jef Spaleta]

On Sat, 4 Sep 2004 14:16:02 -0500, Mike Klinke <lsomike(a)futzin.com&gt; wrote:
>  This is just a guess to get you past the error ..... will excluding
>  that package offer any help?  ( --exclude=katana* ) 
Depends on what needs to be helped.
There are situations when an exclude is appropriate because of a REAL
packaging error in rawhide. But please, don't suggest that as a cure,
until that is confirmed via manual checking the dependacy chain. If
Robert is hitting a corner case bug, that I'm not hitting, having him
exclude katana to get around it does not help find the reason. The
point of testing is to find the bugs and fix them, not work around
them blindly.

-jef

[Mike Klinke]

On Saturday 04 September 2004 14:26, Jeff Spaleta wrote:
>  On Sat, 4 Sep 2004 14:16:02 -0500, Mike Klinke 
<lsomike(a)futzin.com&gt; wrote:
>  > This is just a guess to get you past the error ..... will
>  > excluding that package offer any help?  ( --exclude=katana* )
>
>  Depends on what needs to be helped.
>  There are situations when an exclude is appropriate because of a
>  REAL packaging error in rawhide. But please, don't suggest that
>  as a cure, until that is confirmed via manual checking the
>  dependacy chain. If Robert is hitting a corner case bug, that I'm
>  not hitting, having him exclude katana to get around it does not
>  help find the reason. The point of testing is to find the bugs
>  and fix them, not work around them blindly.
>
>  -jef 
You are, of course, correct.  I tend to work in smaller steps to a 
solution rather than larger ones.  I think we'd both arrive at the 
same door although the particular steps to get there might differ; 
i.e. we would still have had to deal with the "duplicate" sooner or 
later.

Carry on, you do good work too!

Regards, Mike Klinke

[Jef Spaleta]

On Sat, 04 Sep 2004 14:43:25 -0400, Robert L Cochran
<bobtest(a)lingpgmr.com&gt; wrote:
>  How do I deal with this error as a result of running
>  
>  'yum -y --obsoletes update':
>  
>  Transaction Check Error: package katana-1.0.4-4 is already installed 
How do you deal with it?
First... stop using -y  option so you can review the list of packages
that yum wants to install/upgrade.
<soapbox>
I think its unwise for anyone using development packages to be using
the -y option and skipping the package list reviewing phase. If you
are using test releases and development packages you need to be very
aware of what you are installing, so you have a hope of narrowing down
problems when not if they occur.
</soapbox>

Second... yum seems to be saying that katana package is already
installed. Is it?
Is the version of katana installed older than the version yum wants to install?

-jef

[Robert L Cochran]

Thanks for your advice, I'll quit using the -y option. 

Yes, katana is already installed, I'm not sure why yum wants to install
it:

Transaction Check Error: package katana-1.0.4-4 is already installed
[root@rachelsp4 ~]# rpm -q katana
katana-1.0.4-4
[root@rachelsp4 ~]#

Bob


On Sat, 2004-09-04 at 15:22 -0400, Jeff Spaleta wrote:
>  On Sat, 04 Sep 2004 14:43:25 -0400, Robert L Cochran
>  <bobtest(a)lingpgmr.com&gt; wrote:
>  > How do I deal with this error as a result of running
>  > 
>  > 'yum -y --obsoletes update':
>  > 
>  > Transaction Check Error: package katana-1.0.4-4 is already installed
>  
>  How do you deal with it?
>  First... stop using -y  option so you can review the list of packages
>  that yum wants to install/upgrade.
>  <soapbox>
>  I think its unwise for anyone using development packages to be using
>  the -y option and skipping the package list reviewing phase. If you
>  are using test releases and development packages you need to be very
>  aware of what you are installing, so you have a hope of narrowing down
>  problems when not if they occur.
>  </soapbox>
>  
>  Second... yum seems to be saying that katana package is already
>  installed. Is it?
>  Is the version of katana installed older than the version yum wants to install?
>  
>  -jef
>  
>

[seth vidal]

On Sat, 2004-09-04 at 17:45 -0400, Robert L Cochran wrote:
>  Thanks for your advice, I'll quit using the -y option. 
>  
>  Yes, katana is already installed, I'm not sure why yum wants to install
>  it:
>  
>  Transaction Check Error: package katana-1.0.4-4 is already installed
>  [root@rachelsp4 ~]# rpm -q katana
>  katana-1.0.4-4
>  [root@rachelsp4 ~]# 
I'd like to see a yum -d 5 of that process in bugzilla if you could.


it would tell me a great deal, I'd like to know why katana is getting
pulled in if it is already installed.

thanks
-sv

[Robert L Cochran]

I've tried entering a bug several times now in bugzilla and when I click
the "Open Bugzilla Entry Form" button I'm greeted with a new window
containing a perfectly blank page. I'll try again from my other machine
later today. Meanwhile here is the yum -d -5 output:

[root@rachelsp4 ~]# yum -d 5 --obsoletes update
Yum Version: 2.1.3
COMMAND: yum -d 5 --obsoletes update
Installroot: /
Setting up Update Process
Reading Local RPMDB
Setting up Repo:  development
Baseurl(s) for repo:
['http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/']
repomd.xml                100% |=========================| 1.1 kB
00:00
Reading repository metadata in from local files
Setting up Package Sacks
primary.xml.gz            100% |=========================| 943 kB
00:11
developmen: ################################################## 3513/3513
Excluding Packages
Excluding Incompatible Archs
Finished
Excluding Packages from Fedora Core 2.90 - Development Tree
Building updates object
Resolving Dependencies
1094386937.43
Adding Package katana - 1.0.4-4.noarch in mode u
Adding Package fonts-xorg-base - 6.7.99.903-5.noarch in mode u
Adding Package gnome-volume-manager - 0.9.10-2.i386 in mode u
Adding Package gamin-devel - 0.0.9-1.i386 in mode u
Adding Package gamin - 0.0.9-1.i386 in mode u
Adding Package fonts-xorg-100dpi - 6.7.99.903-5.noarch in mode u
Adding Package fonts-xorg-75dpi - 6.7.99.903-5.noarch in mode u
Adding Package iiimf-libs-devel - 1:12.0.1-3.svn1891.i386 in mode u
Adding Package iiimf-libs - 1:12.0.1-3.svn1891.i386 in mode u
Adding Package gnome-vfs2-smb - 2.7.92-3.i386 in mode u
Adding Package xorg-x11 - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-deprecated-libs - 6.7.99.903-5.i386 in mode u
Adding Package yelp - 2.6.2-2.i386 in mode u
Adding Package system-config-network - 1.3.20-1.noarch in mode u
Adding Package shared-mime-info - 0.15-2.i386 in mode u
Adding Package xorg-x11-xauth - 6.7.99.903-5.i386 in mode u
Adding Package firstboot - 1.3.21-1.noarch in mode u
Adding Package dev - 3.11-1.i386 in mode u
Adding Package xorg-x11-Mesa-libGL - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-twm - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-xfs - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-font-utils - 6.7.99.903-5.i386 in mode u
Adding Package gnome-vfs2 - 2.7.92-3.i386 in mode u
Adding Package xorg-x11-tools - 6.7.99.903-5.i386 in mode u
Adding Package gnome-media - 2.7.92-7.i386 in mode u
Adding Package xorg-x11-libs - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-Mesa-libGLU - 6.7.99.903-5.i386 in mode u
Adding Package udev - 030-20.i386 in mode u
Adding Package system-config-printer-gui - 0.6.111-1.i386 in mode u
Adding Package xorg-x11-devel - 6.7.99.903-5.i386 in mode u
Adding Package gnome-session - 2.7.91-2.i386 in mode u
Adding Package system-config-printer - 0.6.111-1.i386 in mode u
Adding Package dia - 1:0.94-5.i386 in mode u
Adding Package system-config-network-tui - 1.3.20-1.noarch in mode u
Adding Package desktop-file-utils - 0.8-1.i386 in mode u
Adding Package urw-fonts - 2.2-3.noarch in mode u

Dependencies Resolved
1094386940.76
                [u] desktop-file-utils.i386 0:0.8-1 - user
                [u] dev.i386 0:3.11-1 - user
                [u] dia.i386 1:0.94-5 - user
                [u] firstboot.noarch 0:1.3.21-1 - user
                [u] fonts-xorg-100dpi.noarch 0:6.7.99.903-5 - user
                [u] fonts-xorg-75dpi.noarch 0:6.7.99.903-5 - user
                [u] fonts-xorg-base.noarch 0:6.7.99.903-5 - user
                [u] gamin.i386 0:0.0.9-1 - user
                [u] gamin-devel.i386 0:0.0.9-1 - user
                [u] gnome-media.i386 0:2.7.92-7 - user
                [u] gnome-session.i386 0:2.7.91-2 - user
                [u] gnome-vfs2.i386 0:2.7.92-3 - user
                [u] gnome-vfs2-smb.i386 0:2.7.92-3 - user
                [u] gnome-volume-manager.i386 0:0.9.10-2 - user
                [u] iiimf-libs.i386 1:12.0.1-3.svn1891 - user
                [u] iiimf-libs-devel.i386 1:12.0.1-3.svn1891 - user
                [u] katana.noarch 0:1.0.4-4 - user
                [u] shared-mime-info.i386 0:0.15-2 - user
                [u] system-config-network.noarch 0:1.3.20-1 - user
                [u] system-config-network-tui.noarch 0:1.3.20-1 - user
                [u] system-config-printer.i386 0:0.6.111-1 - user
                [u] system-config-printer-gui.i386 0:0.6.111-1 - user
                [u] udev.i386 0:030-20 - user
                [u] urw-fonts.noarch 0:2.2-3 - user
                [u] xorg-x11.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-Mesa-libGL.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-Mesa-libGLU.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-deprecated-libs.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-devel.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-font-utils.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-libs.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-tools.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-twm.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-xauth.i386 0:6.7.99.903-5 - user
                [u] xorg-x11-xfs.i386 0:6.7.99.903-5 - user
                [u] yelp.i386 0:2.6.2-2 - user
                [o] fam.i386 0:2.6.10-11 - gamin.i386 0:0.0.9-1
                [o] fam-devel.i386 0:2.6.10-11 - gamin-devel.i386
0:0.0.9-1
                [o] iiimf-client-lib.i386 1:11.4-64.svn1772 - iiimf-
libs.i386 1:12.0.1-3.svn1891
                [o] iiimf-client-lib-devel.i386 1:11.4-64.svn1772 -
iiimf-libs-devel.i386 1:12.0.1-3.svn1891
                [o] iiimf-protocol-lib.i386 1:11.4-64.svn1772 - iiimf-
libs.i386 1:12.0.1-3.svn1891
                [o] iiimf-protocol-lib-devel.i386 1:11.4-64.svn1772 -
iiimf-libs-devel.i386 1:12.0.1-3.svn1891
                [o] magicdev.i386 0:1.1.6-2 - gnome-volume-manager.i386
0:0.9.10-2
                [o] redhat-java-rpm-scripts.noarch 0:1.0.3-2 -
katana.noarch 0:1.0.4-4
                [o] xorg-x11-100dpi-fonts.i386 0:6.7.99.903-2 - fonts-
xorg-100dpi.noarch 0:6.7.99.903-5
                [o] xorg-x11-75dpi-fonts.i386 0:6.7.99.903-2 - fonts-
xorg-75dpi.noarch 0:6.7.99.903-5
                [o] xorg-x11-base-fonts.i386 0:6.7.99.903-2 - fonts-
xorg-base.noarch 0:6.7.99.903-5
Is this ok [y/N]: y
Running Transaction Test
Adding Package katana - 1.0.4-4.noarch in mode u
Adding Package fonts-xorg-base - 6.7.99.903-5.noarch in mode u
Adding Package gnome-volume-manager - 0.9.10-2.i386 in mode u
Adding Package gamin-devel - 0.0.9-1.i386 in mode u
Adding Package gamin - 0.0.9-1.i386 in mode u
Adding Package fonts-xorg-100dpi - 6.7.99.903-5.noarch in mode u
Adding Package fonts-xorg-75dpi - 6.7.99.903-5.noarch in mode u
Adding Package iiimf-libs-devel - 1:12.0.1-3.svn1891.i386 in mode u
Adding Package iiimf-libs - 1:12.0.1-3.svn1891.i386 in mode u
Adding Package gnome-vfs2-smb - 2.7.92-3.i386 in mode u
Adding Package xorg-x11 - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-deprecated-libs - 6.7.99.903-5.i386 in mode u
Adding Package yelp - 2.6.2-2.i386 in mode u
Adding Package system-config-network - 1.3.20-1.noarch in mode u
Adding Package shared-mime-info - 0.15-2.i386 in mode u
Adding Package xorg-x11-xauth - 6.7.99.903-5.i386 in mode u
Adding Package firstboot - 1.3.21-1.noarch in mode u
Adding Package dev - 3.11-1.i386 in mode u
Adding Package xorg-x11-Mesa-libGL - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-twm - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-xfs - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-font-utils - 6.7.99.903-5.i386 in mode u
Adding Package gnome-vfs2 - 2.7.92-3.i386 in mode u
Adding Package xorg-x11-tools - 6.7.99.903-5.i386 in mode u
Adding Package gnome-media - 2.7.92-7.i386 in mode u
Adding Package xorg-x11-libs - 6.7.99.903-5.i386 in mode u
Adding Package xorg-x11-Mesa-libGLU - 6.7.99.903-5.i386 in mode u
Adding Package udev - 030-20.i386 in mode u
Adding Package system-config-printer-gui - 0.6.111-1.i386 in mode u
Adding Package xorg-x11-devel - 6.7.99.903-5.i386 in mode u
Adding Package gnome-session - 2.7.91-2.i386 in mode u
Adding Package system-config-printer - 0.6.111-1.i386 in mode u
Adding Package dia - 1:0.94-5.i386 in mode u
Adding Package system-config-network-tui - 1.3.20-1.noarch in mode u
Adding Package desktop-file-utils - 0.8-1.i386 in mode u
Adding Package urw-fonts - 2.2-3.noarch in mode u
Finished Transaction Test
Transaction Check Error: package katana-1.0.4-4 is already installed

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


My package versions:

[root@rachelsp4 ~]# rpm -q yum
yum-2.1.3-1
[root@rachelsp4 ~]# rpm -q katana
katana-1.0.4-4
[root@rachelsp4 ~]#
[root@rachelsp4 ~]#


On Sun, 2004-09-05 at 04:07 -0400, seth vidal wrote:
>  On Sat, 2004-09-04 at 17:45 -0400, Robert L Cochran wrote:
>  > Thanks for your advice, I'll quit using the -y option. 
>  > 
>  > Yes, katana is already installed, I'm not sure why yum wants to install
>  > it:
>  > 
>  > Transaction Check Error: package katana-1.0.4-4 is already installed
>  > [root@rachelsp4 ~]# rpm -q katana
>  > katana-1.0.4-4
>  > [root@rachelsp4 ~]#
>  
>  I'd like to see a yum -d 5 of that process in bugzilla if you could.
>  
>  
>  it would tell me a great deal, I'd like to know why katana is getting
>  pulled in if it is already installed.
>  
>  thanks
>  -sv
>  
>  
>

[Robert L Cochran]

It's bug #131831.


On Sun, 2004-09-05 at 08:53, Robert L Cochran wrote:
>  I've tried entering a bug several times now in bugzilla and when
> I click
>  the "Open Bugzilla Entry Form" button I'm greeted with a new window
>  containing a perfectly blank page. I'll try again from my other machine
>  later today. Meanwhile here is the yum -d -5 output:
>  
>  [root@rachelsp4 ~]# yum -d 5 --obsoletes update
>  Yum Version: 2.1.3
>  COMMAND: yum -d 5 --obsoletes update
>  Installroot: /
>  Setting up Update Process
>  Reading Local RPMDB
>  Setting up Repo:  development
>  Baseurl(s) for repo:
>  ['http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/']
>  repomd.xml                100% |=========================| 1.1 kB
>  00:00
>  Reading repository metadata in from local files
>  Setting up Package Sacks
>  primary.xml.gz            100% |=========================| 943 kB
>  00:11
>  developmen: ################################################## 3513/3513
>  Excluding Packages
>  Excluding Incompatible Archs
>  Finished
>  Excluding Packages from Fedora Core 2.90 - Development Tree
>  Building updates object
>  Resolving Dependencies
>  1094386937.43
>  Adding Package katana - 1.0.4-4.noarch in mode u
>  Adding Package fonts-xorg-base - 6.7.99.903-5.noarch in mode u
>  Adding Package gnome-volume-manager - 0.9.10-2.i386 in mode u
>  Adding Package gamin-devel - 0.0.9-1.i386 in mode u
>  Adding Package gamin - 0.0.9-1.i386 in mode u
>  Adding Package fonts-xorg-100dpi - 6.7.99.903-5.noarch in mode u
>  Adding Package fonts-xorg-75dpi - 6.7.99.903-5.noarch in mode u
>  Adding Package iiimf-libs-devel - 1:12.0.1-3.svn1891.i386 in mode u
>  Adding Package iiimf-libs - 1:12.0.1-3.svn1891.i386 in mode u
>  Adding Package gnome-vfs2-smb - 2.7.92-3.i386 in mode u
>  Adding Package xorg-x11 - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-deprecated-libs - 6.7.99.903-5.i386 in mode u
>  Adding Package yelp - 2.6.2-2.i386 in mode u
>  Adding Package system-config-network - 1.3.20-1.noarch in mode u
>  Adding Package shared-mime-info - 0.15-2.i386 in mode u
>  Adding Package xorg-x11-xauth - 6.7.99.903-5.i386 in mode u
>  Adding Package firstboot - 1.3.21-1.noarch in mode u
>  Adding Package dev - 3.11-1.i386 in mode u
>  Adding Package xorg-x11-Mesa-libGL - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-twm - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-xfs - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-font-utils - 6.7.99.903-5.i386 in mode u
>  Adding Package gnome-vfs2 - 2.7.92-3.i386 in mode u
>  Adding Package xorg-x11-tools - 6.7.99.903-5.i386 in mode u
>  Adding Package gnome-media - 2.7.92-7.i386 in mode u
>  Adding Package xorg-x11-libs - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-Mesa-libGLU - 6.7.99.903-5.i386 in mode u
>  Adding Package udev - 030-20.i386 in mode u
>  Adding Package system-config-printer-gui - 0.6.111-1.i386 in mode u
>  Adding Package xorg-x11-devel - 6.7.99.903-5.i386 in mode u
>  Adding Package gnome-session - 2.7.91-2.i386 in mode u
>  Adding Package system-config-printer - 0.6.111-1.i386 in mode u
>  Adding Package dia - 1:0.94-5.i386 in mode u
>  Adding Package system-config-network-tui - 1.3.20-1.noarch in mode u
>  Adding Package desktop-file-utils - 0.8-1.i386 in mode u
>  Adding Package urw-fonts - 2.2-3.noarch in mode u
>  
>  Dependencies Resolved
>  1094386940.76
>                  [u] desktop-file-utils.i386 0:0.8-1 - user
>                  [u] dev.i386 0:3.11-1 - user
>                  [u] dia.i386 1:0.94-5 - user
>                  [u] firstboot.noarch 0:1.3.21-1 - user
>                  [u] fonts-xorg-100dpi.noarch 0:6.7.99.903-5 - user
>                  [u] fonts-xorg-75dpi.noarch 0:6.7.99.903-5 - user
>                  [u] fonts-xorg-base.noarch 0:6.7.99.903-5 - user
>                  [u] gamin.i386 0:0.0.9-1 - user
>                  [u] gamin-devel.i386 0:0.0.9-1 - user
>                  [u] gnome-media.i386 0:2.7.92-7 - user
>                  [u] gnome-session.i386 0:2.7.91-2 - user
>                  [u] gnome-vfs2.i386 0:2.7.92-3 - user
>                  [u] gnome-vfs2-smb.i386 0:2.7.92-3 - user
>                  [u] gnome-volume-manager.i386 0:0.9.10-2 - user
>                  [u] iiimf-libs.i386 1:12.0.1-3.svn1891 - user
>                  [u] iiimf-libs-devel.i386 1:12.0.1-3.svn1891 - user
>                  [u] katana.noarch 0:1.0.4-4 - user
>                  [u] shared-mime-info.i386 0:0.15-2 - user
>                  [u] system-config-network.noarch 0:1.3.20-1 - user
>                  [u] system-config-network-tui.noarch 0:1.3.20-1 - user
>                  [u] system-config-printer.i386 0:0.6.111-1 - user
>                  [u] system-config-printer-gui.i386 0:0.6.111-1 - user
>                  [u] udev.i386 0:030-20 - user
>                  [u] urw-fonts.noarch 0:2.2-3 - user
>                  [u] xorg-x11.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-Mesa-libGL.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-Mesa-libGLU.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-deprecated-libs.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-devel.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-font-utils.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-libs.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-tools.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-twm.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-xauth.i386 0:6.7.99.903-5 - user
>                  [u] xorg-x11-xfs.i386 0:6.7.99.903-5 - user
>                  [u] yelp.i386 0:2.6.2-2 - user
>                  [o] fam.i386 0:2.6.10-11 - gamin.i386 0:0.0.9-1
>                  [o] fam-devel.i386 0:2.6.10-11 - gamin-devel.i386
>  0:0.0.9-1
>                  [o] iiimf-client-lib.i386 1:11.4-64.svn1772 - iiimf-
>  libs.i386 1:12.0.1-3.svn1891
>                  [o] iiimf-client-lib-devel.i386 1:11.4-64.svn1772 -
>  iiimf-libs-devel.i386 1:12.0.1-3.svn1891
>                  [o] iiimf-protocol-lib.i386 1:11.4-64.svn1772 - iiimf-
>  libs.i386 1:12.0.1-3.svn1891
>                  [o] iiimf-protocol-lib-devel.i386 1:11.4-64.svn1772 -
>  iiimf-libs-devel.i386 1:12.0.1-3.svn1891
>                  [o] magicdev.i386 0:1.1.6-2 - gnome-volume-manager.i386
>  0:0.9.10-2
>                  [o] redhat-java-rpm-scripts.noarch 0:1.0.3-2 -
>  katana.noarch 0:1.0.4-4
>                  [o] xorg-x11-100dpi-fonts.i386 0:6.7.99.903-2 - fonts-
>  xorg-100dpi.noarch 0:6.7.99.903-5
>                  [o] xorg-x11-75dpi-fonts.i386 0:6.7.99.903-2 - fonts-
>  xorg-75dpi.noarch 0:6.7.99.903-5
>                  [o] xorg-x11-base-fonts.i386 0:6.7.99.903-2 - fonts-
>  xorg-base.noarch 0:6.7.99.903-5
>  Is this ok [y/N]: y
>  Running Transaction Test
>  Adding Package katana - 1.0.4-4.noarch in mode u
>  Adding Package fonts-xorg-base - 6.7.99.903-5.noarch in mode u
>  Adding Package gnome-volume-manager - 0.9.10-2.i386 in mode u
>  Adding Package gamin-devel - 0.0.9-1.i386 in mode u
>  Adding Package gamin - 0.0.9-1.i386 in mode u
>  Adding Package fonts-xorg-100dpi - 6.7.99.903-5.noarch in mode u
>  Adding Package fonts-xorg-75dpi - 6.7.99.903-5.noarch in mode u
>  Adding Package iiimf-libs-devel - 1:12.0.1-3.svn1891.i386 in mode u
>  Adding Package iiimf-libs - 1:12.0.1-3.svn1891.i386 in mode u
>  Adding Package gnome-vfs2-smb - 2.7.92-3.i386 in mode u
>  Adding Package xorg-x11 - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-deprecated-libs - 6.7.99.903-5.i386 in mode u
>  Adding Package yelp - 2.6.2-2.i386 in mode u
>  Adding Package system-config-network - 1.3.20-1.noarch in mode u
>  Adding Package shared-mime-info - 0.15-2.i386 in mode u
>  Adding Package xorg-x11-xauth - 6.7.99.903-5.i386 in mode u
>  Adding Package firstboot - 1.3.21-1.noarch in mode u
>  Adding Package dev - 3.11-1.i386 in mode u
>  Adding Package xorg-x11-Mesa-libGL - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-twm - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-xfs - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-font-utils - 6.7.99.903-5.i386 in mode u
>  Adding Package gnome-vfs2 - 2.7.92-3.i386 in mode u
>  Adding Package xorg-x11-tools - 6.7.99.903-5.i386 in mode u
>  Adding Package gnome-media - 2.7.92-7.i386 in mode u
>  Adding Package xorg-x11-libs - 6.7.99.903-5.i386 in mode u
>  Adding Package xorg-x11-Mesa-libGLU - 6.7.99.903-5.i386 in mode u
>  Adding Package udev - 030-20.i386 in mode u
>  Adding Package system-config-printer-gui - 0.6.111-1.i386 in mode u
>  Adding Package xorg-x11-devel - 6.7.99.903-5.i386 in mode u
>  Adding Package gnome-session - 2.7.91-2.i386 in mode u
>  Adding Package system-config-printer - 0.6.111-1.i386 in mode u
>  Adding Package dia - 1:0.94-5.i386 in mode u
>  Adding Package system-config-network-tui - 1.3.20-1.noarch in mode u
>  Adding Package desktop-file-utils - 0.8-1.i386 in mode u
>  Adding Package urw-fonts - 2.2-3.noarch in mode u
>  Finished Transaction Test
>  Transaction Check Error: package katana-1.0.4-4 is already installed
>  
>  -----------------------------------------------------------
>  
>  
>  My package versions:
>  
>  [root@rachelsp4 ~]# rpm -q yum
>  yum-2.1.3-1
>  [root@rachelsp4 ~]# rpm -q katana
>  katana-1.0.4-4
>  [root@rachelsp4 ~]#
>  [root@rachelsp4 ~]#
>  
>  
>  On Sun, 2004-09-05 at 04:07 -0400, seth vidal wrote:
>  > On Sat, 2004-09-04 at 17:45 -0400, Robert L Cochran wrote:
>  > > Thanks for your advice, I'll quit using the -y option. 
>  > > 
>  > > Yes, katana is already installed, I'm not sure why yum wants to install
>  > > it:
>  > > 
>  > > Transaction Check Error: package katana-1.0.4-4 is already installed
>  > > [root@rachelsp4 ~]# rpm -q katana
>  > > katana-1.0.4-4
>  > > [root@rachelsp4 ~]#
>  > 
>  > I'd like to see a yum -d 5 of that process in bugzilla if you could.
>  > 
>  > 
>  > it would tell me a great deal, I'd like to know why katana is getting
>  > pulled in if it is already installed.
>  > 
>  > thanks
>  > -sv
>  > 
>  > 
>  > 
>

Jeff Spaleta wrote:

> On Sat, 04 Sep 2004 14:43:25 -0400, Robert L Cochran
> <bobtest(a)lingpgmr.com&gt; wrote:
>   
>
> >How do I deal with this error as a result of running
> >
> >'yum -y --obsoletes update':
> >
> >Transaction Check Error: package katana-1.0.4-4 is already installed
> >    
> >
>
> How do you deal with it?
> First... stop using -y  option so you can review the list of packages
> that yum wants to install/upgrade.
>   
>  
gnome-terminal:
scroll up|down

tty:
[shift]+[pgup|pgdown]

perhaps:
yum -y update | mail -s yum root

later:
/var/log/yum.log


sorry,
i will not stand up at 03:00 just for pressing [y]

> <soapbox>
> I think its unwise for anyone using development packages to be using
> the -y option and skipping the package list reviewing phase. If you
> are using test releases and development packages you need to be very
> aware of what you are installing, so you have a hope of narrowing down
> problems when not if they occur.
> </soapbox>
>   
>  
i think it is unwise to use -y in a production environment

> Second... yum seems to be saying that katana package is already
> installed. Is it?
> Is the version of katana installed older than the version yum wants to install?
>
> -jef
>  
-- 
shrek-m

[Jef Spaleta]

On Sun, 05 Sep 2004 00:46:40 +0200, shrek-m(a)gmx.de <shrek-m(a)gmx.de&gt; wrote:
>  later:
>  /var/log/yum.log 
 
this assumes the logging is working?
do you know if the logging is working in the new yum code yet?

>  sorry,
>  i will not stand up at 03:00 just for pressing [y] 
Feel free to ignore any friendly advice offered in good faith. I would
also suggest that
automating nightly installs of development packages is not a good
thing for a novice tester to be doing.

-jef