FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hi. w/ about a 90% understanding of the "Supported ver's Linux" sticky, I am now more than ever concerned about the fact that i've been unable to update with YUM, successfully, since late Sept. 2006.
I wish to "resolve" this issue (no pun intended!) -- or come as close to a resolve as possible, within the reasonable expectations of a Learner not quite a year old in 'Linux-years' (GNU/Linux - Fedora Core 5 ).
I have an open bug-report re: yumex. based on my own deduction, i assume the issue is really a YUM problem. from everything i've learned, all i've taken from it thus far is what i've known-- that yum isn't updating properly. Unless i've missed it, I've been offered no suggestion as to possible resolve, or "workaround", so I hope that i might find some actionable recommendations here.
[root@localhost ~]# yum -yt --enablerepo=livna update
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
dries [1/9]
livna [2/9]
macromedia [3/9]
rpmforge [4/9]
core [5/9]
updates [6/9]
freshrpms [7/9]
mono [8/9]
extras [9/9]
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for texmacs to pack into transaction set.
texmacs-1.0.6.7-1.fc5.rf. 100% |=========================| 280 kB 00:01
---> Package texmacs.i386 0:1.0.6.7-1.fc5.rf set to be updated
---> Downloading header for youtube-dl to pack into transaction set.
youtube-dl-0-0.2007.01.01 100% |=========================| 2.7 kB 00:00
---> Package youtube-dl.noarch 0:0-0.2007.01.01.fc5.rf set to be updated
---> Downloading header for lilypond to pack into transaction set.
lilypond-2.10.13-1.fc5.i3 100% |=========================| 50 kB 00:01
---> Package lilypond.i386 0:2.10.13-1.fc5 set to be updated
---> Downloading header for libc-client2006 to pack into transaction set.
libc-client2006-2006e-2.f 100% |=========================| 9.4 kB 00:00
---> Package libc-client2006.i386 0:2006e-2.fc5 set to be updated
---> Downloading header for python-musicbrainz2 to pack into transaction set.
python-musicbrainz2-0.4.1 100% |=========================| 7.2 kB 00:00
---> Package python-musicbrainz2.noarch 0:0.4.1-1.fc5 set to be updated
---> Downloading header for netpbm-progs to pack into transaction set.
netpbm-progs-10.35-1.fc5. 100% |=========================| 89 kB 00:01
---> Package netpbm-progs.i386 0:10.35-1.fc5 set to be updated
---> Downloading header for enscript to pack into transaction set.
enscript-1.6.4-4.fc5.i386 100% |=========================| 26 kB 00:00
---> Package enscript.i386 0:1.6.4-4.fc5 set to be updated
---> Downloading header for php-pecl-xdebug to pack into transaction set.
php-pecl-xdebug-2.0.0-0.4 100% |=========================| 3.6 kB 00:00
---> Package php-pecl-xdebug.i386 0:2.0.0-0.4.RC2.fc5 set to be updated
---> Downloading header for gtkwave to pack into transaction set.
gtkwave-3.0.20-1.fc5.i386 100% |=========================| 13 kB 00:00
---> Package gtkwave.i386 0:3.0.20-1.fc5 set to be updated
---> Downloading header for epiphany to pack into transaction set.
epiphany-2.14.3-3.fc5.i38 100% |=========================| 41 kB 00:00
---> Package epiphany.i386 0:2.14.3-3.fc5 set to be updated
---> Downloading header for seamonkey-devel to pack into transaction set.
seamonkey-devel-1.0.7-0.6 100% |=========================| 368 kB 00:01
---> Package seamonkey-devel.i386 0:1.0.7-0.6.fc5 set to be updated
---> Downloading header for uw-imap-utils to pack into transaction set.
uw-imap-utils-2006e-2.fc5 100% |=========================| 8.0 kB 00:00
---> Package uw-imap-utils.i386 0:2006e-2.fc5 set to be updated
---> Downloading header for gnome-applet-music to pack into transaction set.
gnome-applet-music-0.9.2- 100% |=========================| 7.7 kB 00:00
---> Package gnome-applet-music.i386 0:0.9.2-2.fc5 set to be updated
---> Downloading header for SDL_gfx to pack into transaction set.
SDL_gfx-2.0.15-1.fc5.rf.i 100% |=========================| 4.3 kB 00:00
---> Package SDL_gfx.i386 0:2.0.15-1.fc5.rf set to be updated
---> Downloading header for uni2ascii to pack into transaction set.
uni2ascii-3.12-1.fc5.rf.i 100% |=========================| 5.2 kB 00:00
---> Package uni2ascii.i386 0:3.12-1.fc5.rf set to be updated
---> Downloading header for netpbm to pack into transaction set.
netpbm-10.35-1.fc5.i386.r 100% |=========================| 16 kB 00:00
---> Package netpbm.i386 0:10.35-1.fc5 set to be updated
---> Downloading header for chmlib to pack into transaction set.
chmlib-0.39-1.fc5.i386.rp 100% |=========================| 3.7 kB 00:00
---> Package chmlib.i386 0:0.39-1.fc5 set to be updated
---> Downloading header for claws-mail-plugins-smime to pack into transaction set.
claws-mail-plugins-smime- 100% |=========================| 5.4 kB 00:00
---> Package claws-mail-plugins-smime.i386 0:2.7.1-1.fc5 set to be updated
---> Downloading header for mjpegtools to pack into transaction set.
mjpegtools-1.9.0-0.2.fc5. 100% |=========================| 23 kB 00:00
---> Package mjpegtools.i386 0:1.9.0-0.2.fc5.rf set to be updated
---> Downloading header for fetchmail to pack into transaction set.
fetchmail-6.3.6-2.fc5.i38 100% |=========================| 17 kB 00:00
---> Package fetchmail.i386 0:6.3.6-2.fc5 set to be updated
---> Downloading header for galeon to pack into transaction set.
galeon-2.0.3-2.fc5.i386.r 100% |=========================| 40 kB 00:01
---> Package galeon.i386 0:2.0.3-2.fc5 set to be updated
---> Downloading header for pinfo to pack into transaction set.
pinfo-0.6.9-2.fc5.i386.rp 100% |=========================| 9.6 kB 00:00
---> Package pinfo.i386 0:0.6.9-2.fc5 set to be updated
---> Downloading header for tinyerp to pack into transaction set.
tinyerp-4.0.2-1.fc5.noarc 100% |=========================| 113 kB 00:01
---> Package tinyerp.noarch 0:4.0.2-1.fc5 set to be updated
---> Downloading header for claws-mail-plugins-maildir to pack into transaction set.
claws-mail-plugins-maildi 100% |=========================| 5.2 kB 00:00
---> Package claws-mail-plugins-maildir.i386 0:2.7.1-1.fc5 set to be updated
---> Downloading header for exiv2 to pack into transaction set.
exiv2-0.12-2.fc5.rf.i386. 100% |=========================| 4.5 kB 00:00
---> Package exiv2.i386 0:0.12-2.fc5.rf set to be updated
---> Downloading header for kplayer to pack into transaction set.
kplayer-0.6.0-1.lvn5.i386 100% |=========================| 43 kB 00:00
---> Package kplayer.i386 0:0.6.0-1.lvn5 set to be updated
---> Downloading header for PyQt to pack into transaction set.
PyQt-3.17-0.1.fc5.i386.rp 100% |=========================| 9.9 kB 00:00
---> Package PyQt.i386 0:3.17-0.1.fc5 set to be updated
---> Downloading header for libosip2 to pack into transaction set.
libosip2-3.0.1-2.fc5.i386 100% |=========================| 4.7 kB 00:00
---> Package libosip2.i386 0:3.0.1-2.fc5 set to be updated
---> Downloading header for claws-mail-plugins-synce to pack into transaction set.
claws-mail-plugins-synce- 100% |=========================| 5.0 kB 00:00
---> Package claws-mail-plugins-synce.i386 0:2.7.1-1.fc5 set to be updated
---> Downloading header for python-mutagen to pack into transaction set.
python-mutagen-1.10.1-1.f 100% |=========================| 12 kB 00:00
---> Package python-mutagen.noarch 0:1.10.1-1.fc5 set to be updated
---> Downloading header for fig2ps to pack into transaction set.
fig2ps-1.3.6-1.fc5.noarch 100% |=========================| 3.8 kB 00:00
---> Package fig2ps.noarch 0:1.3.6-1.fc5 set to be updated
---> Downloading header for bzr to pack into transaction set.
bzr-0.14-1.fc5.noarch.rpm 100% |=========================| 142 kB 00:01
---> Package bzr.noarch 0:0.14-1.fc5 set to be updated
---> Downloading header for libextractor to pack into transaction set.
libextractor-0.5.17a-1.fc 100% |=========================| 15 kB 00:00
---> Package libextractor.i386 0:0.5.17a-1.fc5.rf set to be updated
---> Downloading header for claws-mail-plugins-newmail to pack into transaction set.
claws-mail-plugins-newmai 100% |=========================| 5.1 kB 00:00
---> Package claws-mail-plugins-newmail.i386 0:2.7.1-1.fc5 set to be updated
---> Downloading header for tinyerp-server to pack into transaction set.
tinyerp-server-4.0.2-1.fc 100% |=========================| 328 kB 00:03
---> Package tinyerp-server.noarch 0:4.0.2-1.fc5 set to be updated
---> Downloading header for claws-mail-plugins-perl to pack into transaction set.
claws-mail-plugins-perl-2 100% |=========================| 5.6 kB 00:00
---> Package claws-mail-plugins-perl.i386 0:2.7.1-1.fc5 set to be updated
---> Downloading header for libcdio to pack into transaction set.
libcdio-0.77-1.fc5.rf.i38 100% |=========================| 7.4 kB 00:00
---> Package libcdio.i386 0:0.77-1.fc5.rf set to be updated
---> Downloading header for comix to pack into transaction set.
comix-3.6.2-2.fc5.noarch. 100% |=========================| 11 kB 00:00
---> Package comix.noarch 0:3.6.2-2.fc5 set to be updated
---> Downloading header for gphoto2 to pack into transaction set.
gphoto2-2.3.1-3.fc5.i386. 100% |=========================| 32 kB 00:00
---> Package gphoto2.i386 0:2.3.1-3.fc5 set to be updated
---> Downloading header for kipi-plugins to pack into transaction set.
kipi-plugins-0.1.3-2.fc5. 100% |=========================| 155 kB 00:02
---> Package kipi-plugins.i386 0:0.1.3-2.fc5 set to be updated
---> Downloading header for sip to pack into transaction set.
sip-4.5-0.1.fc5.i386.rpm 100% |=========================| 8.7 kB 00:00
---> Package sip.i386 0:4.5-0.1.fc5 set to be updated
---> Downloading header for geany to pack into transaction set.
geany-0.10-5.fc5.i386.rpm 100% |=========================| 16 kB 00:00
---> Package geany.i386 0:0.10-5.fc5 set to be updated
---> Downloading header for libyaz to pack into transaction set.
libyaz-2.1.48-1.fc5.i386. 100% |=========================| 3.4 kB 00:00
---> Package libyaz.i386 0:2.1.48-1.fc5 set to be updated
---> Downloading header for claws-mail-plugins-notification to pack into transaction set.
claws-mail-plugins-notifi 100% |=========================| 5.0 kB 00:00
---> Package claws-mail-plugins-notification.i386 0:2.7.1-1.fc5 set to be updated
---> Downloading header for ortp to pack into transaction set.
ortp-0.12.0-1.fc5.i386.rp 100% |=========================| 3.7 kB 00:00
---> Package ortp.i386 0:0.12.0-1.fc5 set to be updated
---> Downloading header for vcdimager to pack into transaction set.
vcdimager-0.7.23-5.fc5.rf 100% |=========================| 8.8 kB 00:00
---> Package vcdimager.i386 0:0.7.23-5.fc5.rf set to be updated
---> Downloading header for libcddb to pack into transaction set.
libcddb-1.3.0-1.fc5.rf.i3 100% |=========================| 3.6 kB 00:00
---> Package libcddb.i386 0:1.3.0-1.fc5.rf set to be updated
---> Downloading header for spamassassin to pack into transaction set.
spamassassin-3.1.7-5.fc5. 100% |=========================| 47 kB 00:00
---> Package spamassassin.i386 0:3.1.7-5.fc5 set to be updated
---> Downloading header for claws-mail-plugins-mailmbox to pack into transaction set.
claws-mail-plugins-mailmb 100% |=========================| 5.3 kB 00:00
---> Package claws-mail-plugins-mailmbox.i386 0:2.7.1-1.fc5 set to be updated
--> Running transaction check
--> Processing Dependency: libSDL_gfx.so.13 for package: lincity-ng
--> Processing Dependency: seamonkey = 1.0.7 for package: epiphany
--> Processing Dependency: libcdio.so.6 for package: videolan-client
--> Processing Dependency: seamonkey = 1.0.7 for package: galeon
--> Processing Dependency: libiso9660.so.4 for package: videolan-client
--> Processing Dependency: libexiv2-0.11.so for package: kphotoalbum
--> Processing Dependency: seamonkey = 1.0.7-0.6.fc5 for package: seamonkey-devel
--> Processing Dependency: libosip2.so.3 for package: linphone
--> Processing Dependency: libosipparser2.so.3 for package: linphone
--> Processing Dependency: libortp.so.2 for package: linphone
--> Finished Dependency Resolution
Error: Missing Dependency: libSDL_gfx.so.13 is needed by package lincity-ng
Error: Missing Dependency: seamonkey = 1.0.7 is needed by package epiphany
Error: Missing Dependency: libcdio.so.6 is needed by package videolan-client
Error: Missing Dependency: seamonkey = 1.0.7 is needed by package galeon
Error: Missing Dependency: libiso9660.so.4 is needed by package videolan-client
Error: Missing Dependency: libexiv2-0.11.so is needed by package kphotoalbum
Error: Missing Dependency: seamonkey = 1.0.7-0.6.fc5 is needed by package seamonkey-devel
Error: Missing Dependency: libosip2.so.3 is needed by package linphone
Error: Missing Dependency: libosipparser2.so.3 is needed by package linphone
Error: Missing Dependency: libortp.so.2 is needed by package linphone
EDIT:
okay-- this is something i've never seen before (re: gedit error...), though gedit did open
Code:
[root@localhost etc]# gedit yum.conf
Traceback (most recent call last):
File "/usr/lib/gedit-2/plugins/modelines.py", line 20, in ?
import gedit
ImportError: No module named gedit
** (gedit:13274): WARNING **: Could not load python module modelines
** (gedit:13274): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed
A few remarks if I may:
- Your bugtrack ticket shows a recommendation to rebuild your RPM database and you didn't reply back you did in any way I can see.
- Your next entry shows you have "db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery" errors which means you either did not --rebuilddb, or have persistent problems, I can not see that.
- You have *and* the FreshRPM *and* Livna in your repo.d and those are incompatible (and I can't see which one is disabled if any). If that caused dependency problems they can only be fixed by removing packages before continuing to upgrade AFAIK.
- Finally please forget about "nice to haves". First check if there are any kernel, system or network-facing updates available with a security risk and try upgrading those first. Disable all repo's and first check for updates from "official" repo's like FC and FCL. *Then* worry about the rest. If you can't upgrade those first take preventive measures like not running them or restricting access to them until you can resolve your problems.
- Your bugtrack ticket shows a recommendation to rebuild your RPM database and you didn't reply back you did in any way I can see.
i think you're asking if i followed an instruction to rebuild the RPM database? i'm not sure if it's the same thing, but i received no feedback or follow up to whatever this is: https://bugzilla.redhat.com/bugzilla...i?id=217644#c6
if that was unsuccessful, or if i never did the proper instruction, i was given no indication. so, if in fact this is a necessary step, not yet exectued, then that would indeed seem a logical reason for little progress.
that said, what then would be the proper way to execute the recommended action? what must be recorded, and would be the proper follow-up action?
Quote:
Originally Posted by unSpawn
- Your next entry shows you have "db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery" errors which means you either did not --rebuilddb, or have persistent problems, I can not see that.
cool, i'm glad i finally got some substantive feedback on this because, though apparently not obvious in the past-- this is an area of confusion for me, and something i'm going to need a bit more coaching to get it straight.
okay-- what is it that you're citing here (re: db4 error (-30977))? is this a bug-report ID... or..?
EDIT: nevermind-- i see where you got that, but-- ... huh?
re: kernel 'n the necessities vs nicey nicey, are you saying that it will be necessary for me to actively select which packages / components / software i want to update? the report i copy/pasted above is the result of a simple "yum update". i am unable to do a more specific update, excluding other packages / components / software as i simply do not know which to include or exclude. though it probably exisits, i don't have a reference at hand to instruct me in this process. could you recommend something specifc (a URL to a resource of instructions more specific to your recommendation, not your own instructions-- unless of course you have it to cut/ paste, or it's little trouble... in other words, i'm asking for a cookie here-- surely no need to bake a fresh batch)
additionally, what is recorded at the redhat bugzilla page shows my approaching the problem from a "YumEx" angle-- precisely because of the "Please report bug..." dialogue received when using that software. so, i stuck w/ that, and the communication w/ the bugzilla facility-- in Good Scout practice methinks. throughout the process of gaining feedback from redhat bugzilla, i don't recall any repos specified, though i provided record of output from attempts made using the following group:
maybe the system isn't in need of an update after all. is there a way to check only the primary components? the reason for my concern was a possible relation to the Forum sticky thread i cited, and the lingering idea that something is wrong w/ Yum based on its own "you should report a bug" dialog.
Last edited by WhatsOnYourBrain; 02-03-2007 at 01:51 PM.
Talking about value, well, for one you may learn how to deal with and correct errors, extending the life of your current install a bit.
Before we begin lets set one thing straight. Yes FC5 is supported and yes, you probably do need to update packages. I suggest working on the RPM database first. If that fails we can rebuild the database from scratch though that's not advisable, really a last resort option. Everything below is commandline work (the horror, the horror...) so open up a Konsole/xterm or whatever it's called these days and su -l so you're root.
0. Now, before rebuilding the database (you do make backups right?) you better make a copy so you can revert back:
1. This is basically what /etc/cron\..*/rpm does, but now sorted by installtime (change output /location/filename if you want to). Remove temps and save a copy of the database index:
2. Now we can remove temps (just in case) and rebuild the database saving a log in case errors pop up:
Code:
rm -f /var/lib/rpm/__*
rpm -v --rebuilddb 2>&1 | tee /tmp/rpm_rebuild.log
3. Now let's have a look at Yum. Disable all repositories (edit to "disable=yes": check your "man yum" to make certain) in /etc/yum.repos.d/ except:
- fedora-core
- fedora-extras
- fedora-legacy
- fedora-updates
4. then clean up all headers and packages and check for updates:
Code:
yum clean all 2>&1 | tee /tmp/yum_clean.log
yum check-update 2>&1 | tee /tmp/yum_chkupd.log
* If there's errors at any stage just stop there. Most likely the logfile(s) will be too large to post here. Compress then post a (temporary) location I can D/L them from. If you don't want it here you can email me the location but please do not email me logs w/o me explicitly asking for them.
okay. this is great. thanks for your time and effort.
i am in the middle of a project which requires my attention, currently. i will try to get to this later today, most likely by end of tomorrow.
thanks again!
EDIT:
well-- if it's not obvious already, as projects tend to do-- mine has grown larger, and consumed more time than i had wished for. i'm hoping to return to tweak-my-linux-world this weekend.
thanks again.
Last edited by WhatsOnYourBrain; 02-08-2007 at 08:05 PM.
i'm currently doing rpm -v --rebuilddb 2>&1 | tee /tmp/rpm_rebuild.log
will report updates w/ progress
EDIT:
hey, out of curiosity-- (because i'm not going to do it now for time)
Suppose i wanted to remain in terminal (the KDE CLI interface) for the editing of the YUM repo config files, and use V (or is it VIM?) -- the editor... what would be the basic commands to allow me to open a file in "VIM" itself (or must i open VIM first? i'm picturing the command to be one and the same at once from CLI) and then actually save the edited contents, and exit back to the CLI? i know some of the commands believe it or not but its the getting in properly and getting out properly which seems to usually result in my having wasted my time with it.
thanks
Last edited by WhatsOnYourBrain; 02-14-2007 at 04:22 PM.
no errors in any of the process up to the part of tweaking the yum repos files.
per your suggestion, after referencing man yum, i understand that the effective method of "disabling" the repos is: enabled=0
so i'm going w/ that option, as in:
when i've completed this last step, have i completed the process of resetting the yum db, or is there still more to come as part of the process [initiated] here?
EDIT:
so, i guess that's a wrap. sorry to ruin the whole thing, but here's what happens at the end. the good guy gets the girl. the doper finally OD's, and all the mafia guys are blown up in a 1984 Cadillac Eldorado...
oh, yeah-- and the credits rolled:
do you see the lead players you were looking for in there? is this what we were expecting to see? is this good? am i happy now? should i go try a basic ]# yum -y update now w/out doing anything else to the repos? i assume that would be the logical next step?
i recall picking up those "multiple" kernal files once when trying to update the nvidia software (i think... either that, or the NTFS module). is it recommended i "remove" any of this, or would this be a proper, accepted configuration?
and i forgot to mention that, though i don't know why it was already commented out in mirrors-rpmforge:
#http://ftp.heanet.ie/pub/freshrpms/pub/dag/dries/fedora/fc5/$ARCH/dries/RPMS
edit3:
already we have the sequal!
Code:
---> Package kdmtheme.i386 0:1.1.2-5.fc5 set to be updated
--> Running transaction check
--> Processing Dependency: seamonkey = 1.0.7 for package: epiphany
--> Processing Dependency: seamonkey = 1.0.7 for package: galeon
--> Processing Dependency: seamonkey = 1.0.7-0.6.fc5 for package: seamonkey-devel
--> Processing Dependency: libosip2.so.3 for package: linphone
--> Processing Dependency: libosipparser2.so.3 for package: linphone
--> Processing Dependency: libortp.so.2 for package: linphone
--> Finished Dependency Resolution
--> Populating transaction set with selected packages. Please wait.
---> Package kernel-devel.i686 0:2.6.18-1.2239.fc5 set to be erased
--> Running transaction check
--> Processing Dependency: seamonkey = 1.0.7 for package: epiphany
--> Processing Dependency: seamonkey = 1.0.7 for package: galeon
--> Processing Dependency: seamonkey = 1.0.7-0.6.fc5 for package: seamonkey-devel
--> Processing Dependency: libosip2.so.3 for package: linphone
--> Processing Dependency: libosipparser2.so.3 for package: linphone
--> Processing Dependency: libortp.so.2 for package: linphone
--> Finished Dependency Resolution
Error: Missing Dependency: seamonkey = 1.0.7 is needed by package epiphany
Error: Missing Dependency: seamonkey = 1.0.7 is needed by package galeon
Error: Missing Dependency: seamonkey = 1.0.7-0.6.fc5 is needed by package seamonkey-devel
Error: Missing Dependency: libosip2.so.3 is needed by package linphone
Error: Missing Dependency: libosipparser2.so.3 is needed by package linphone
Error: Missing Dependency: libortp.so.2 is needed by package linphone
[root@localhost ~]#
the seamonkey i attribute to the following:
Code:
[root@localhost ~]# yum list seamonkey
Loading "installonlyn" plugin
Setting up repositories
core [1/3]
updates [2/3]
extras [3/3]
Reading repository metadata in from local files
Installed Packages
seamonkey.i386 1.1-1 installed
Available Packages
seamonkey.i386 1.0.7-0.6.fc5 updates
[root@localhost ~]#
i've only ever used Galeon and Epiphony to "see what they are like", but i do not use them to my knowledge (unless they are integrated w/ something else)
as for "linophone" -- i have no idea what it is. to my knowledge i don't use it, nor do i intend to. i realize however that other components might need it (and an updated version of it), but if i don't-- i'm just as happy to bypass it if possible.
Last edited by WhatsOnYourBrain; 02-14-2007 at 05:22 PM.
(which i am expecting to "override" the linphone dependency issue, thereby allowing the update to proceeed), i receive the following
Code:
--> Running transaction check
--> Processing Dependency: libosip2.so.3 for package: linphone
--> Processing Dependency: libosipparser2.so.3 for package: linphone
--> Processing Dependency: libortp.so.2 for package: linphone
--> Finished Dependency Resolution
--> Populating transaction set with selected packages. Please wait.
---> Package kernel-devel.i686 0:2.6.18-1.2239.fc5 set to be erased
--> Running transaction check
--> Processing Dependency: libosip2.so.3 for package: linphone
--> Processing Dependency: libosipparser2.so.3 for package: linphone
--> Processing Dependency: libortp.so.2 for package: linphone
--> Finished Dependency Resolution
Error: Missing Dependency: libosip2.so.3 is needed by package linphone
Error: Missing Dependency: libosipparser2.so.3 is needed by package linphone
Error: Missing Dependency: libortp.so.2 is needed by package linphone
[root@localhost ~]#
EDIT:
removing linphone.i386 seems to have "worked" at least for this step... as the trans. summary completed and the packages are now being downloaded...
Last edited by WhatsOnYourBrain; 02-14-2007 at 05:47 PM.
Don't mean to take over from unSpawn, but I ran into a similar problem during updates. You have quite a few entries to read through here, but believe it or not you are getting somewhere.
There are several situations that are causing dependency issues. First, since you no longer want or need galeon, epiphany, or linphone you can remove those one at a time using yum remove <package>.
Next part of the problem as I see it is the version of seamonkey that is installed versus what is needed by other packages on your system. What is happening is that other packages want seamonkey = 1.0.7 and somehow 1.1 is installed. This dependency is preventing you from updating these packages. I'm not sure if that is a mistake in the rpm database or if seamonkey 1.1 was installed at another time. I would do a yum remove seamonkey followed by yum install seamonkey to sort this out.
After that is accomplished you can try yum update.
I would do a yum remove seamonkey followed by yum install seamonkey to sort this out.
knowing that i could remove Seamonkey 1.1 from the RPM db (and just install it manually) -- and get back to having the software as useable...
seamonkey-1.0.7 is still installed (unsure why as i removed it w/ YUM to put 1.1 in its place). Bearing this in mind, what is recommended for this "seamonkey situation":
***
1.) work on getting seamonkey 1.0.7 -- complete suite back on the system.
2.) remove Ephiphony and Galeon
***
in other words, is there any other advantage to having seamonkey-1.0.7-0.6.0.1.fc5.src.rpm on my system, when after all i removed it for the newer v1.1?
i'm not sure if all of this is particularly relevant right now, as i successfully proceeded in updating 80+ packages after my most recent post yesterday.
should i be satisfied that this process [the above procedure] has resulted in a complete resoration of all things YUM? (outside of my screw-ups re: seamonkey, etc.).
QUESTION:
would the procedure i've just completed result in the appearance of "new" items in the "Select Repositories" mode of YumEX?
the "legacy-updates" seems unfamiliar, but i may have simply never noticed it before:
(#http://fedora.redhat.com/download/mirrors/legacy-updates-released-fc$releasever) regardless, it would have been un-checked before, and checking it results in a "no mirrors" error [momentarily at least] - just curious if this should be in w/ the "Core" and "Extras" and a "safe" and "recommended" repo?
big thanks to those who've responded, for all of the help and feedback i received in this thread!! i have definitely made progress w/ YUM.
if anyone would like to see logs from the transaction above, let me know-- otherwise, i'll consider this the "close" of this thread.
thanks again!
Last edited by WhatsOnYourBrain; 02-15-2007 at 10:40 PM.
You know, I had this beautifully written reply and I think I hit preview post instead of submit and now it is gone. Bummer.
Quote:
Originally Posted by WhatsOnYourBrain
knowing that i could remove Seamonkey 1.1 from the RPM db (and just install it manually) -- and get back to having the software as useable...
When I was having troubles with dependencies it was with firefox. I did the remove followed by install and it came back perfectly, even had my bookmarks. After that my system was right as rain.
Quote:
Originally Posted by WhatsOnYourBrain
in other words, is there any other advantage to having seamonkey-1.0.7-0.6.0.1.fc5.src.rpm on my system, when after all i removed it for the newer v1.1?
I think you should be asking the opposite question. What are the benefits to using seamonkey 1.1 over 1.0.7? It is clear that having 1.1 is causing errors during yum updates. What new feature was provided with 1.1 that you can't live without? Since you have a browser is it really necessary to keep galeon and epiphany installed? I like trying out new things too, but I like my system to be stable and run smoothly even more.
Quote:
Originally Posted by WhatsOnYourBrain
should i be satisfied that this process [the above procedure] has resulted in a complete resoration of all things YUM?
My response here goes back to one of your other questions in a previous post. yum is mainly a front-end for rpm. It does not keep a database perse except for maybe lists of packages and headers. It's main benefit is to resolve dependencies for you during package installation. Before yum came on the scene we would install packages using rpm and find out package X needed package Y, so we installed package Y too and then found out Y needed Z. It was great fun!
My guess is that the procedure unSpawn took you through was to get you to a list of essential repos and reduce the amount of grief during updates. You had a lot of repos enabled and I would have done the same. By reducing it to the essentials it prevented possible errors being caused by other repos and allowed a pretty good update to occur on your system.
Quote:
Originally Posted by WhatsOnYourBrain
the "legacy-updates" seems unfamiliar, but i may have simply never noticed it before:
Chances are this did not come from the procedure that was performed. It is on my system and I know I didn't add it after installation. Since it is not enabled it won't cause any issues. I think it is from the fedoralegacy project. If I remember correctly this project was discontinued late last year.
Before you edited I noticed that you installed seamonkey because you could not get firefox 2.0 using yum. I'm not sure I should tell you this, but 2.0 is available, however, the FC folks discourage it. If you want to try it you can install using the command yum install --enablerepos=development firefox. Of course if you have another version of firefox on your system you would exchange install for update.
Looks like you are generally pleased with the way things turned out. Enjoy!
don't you love it when you lose a 15min composition like that!?
happens to me all the time-- something weird w/ my router / cable modem dropping the connection intermittently. wow-- i just thought... yippee-- it hasn't happened yet today!!
yeah, in general, stuff seems cool w/ the Yum situation.
as for 1.1 vs 1.0.7 -- you know, at this point-- i can't recall what is the difference! but i recall thinking it was better when i first installed it!!
i'm thinking it had to do w/ all the nify-neato-factor stuff under the "tools". like XSL debugging, or something? (just looking-- i don't think that stuff is there now! maybe it was a beta-testing only thing? i recall under tools -> debug (or something)... but there's nothing like that there now, outside of chrispederick.com 's webdeveloper extension.
i'm not the type of guy who has to have the "newest" thing like that all the time (well... sometimes, depending..), but i KNOW there was something mentioned in a forum, or somewhere about a feature in 1.1 which i thought might benefit me.
i think i'm going to go ahead and try what you're talking about - remove 1.1 and go back to 1.0.7 just to satisfy the galeon / epiphony thing. i don't feel right about removing those apps, so perhaps this would be the best way to handle it. i'm curious what will happen anyway.
my bet is that yum won't let me uninstall SM1.1 (for dependencies of galeon, and existing 1.0.7-devel package files etc-- after all, it's not going to know that i plan to put it right back on, know what i mean?). if that is the case, what do you recommend?
(not sure when i'll do all this as it's not really a priority, but i am curious)
Last edited by WhatsOnYourBrain; 02-16-2007 at 07:16 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Recom'd Action: Dependencies vs. forum "Reminder"
