6:49 PM
Computer !
Re: Kile installation on fedora 12
but looking at the error isn't it possible to say what is the issue exactly? I mean how to track the exact problem?
How to sure about it.. that the problem is with proxy?
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
Now another problem I see if I enter:
yum install yumex
---------- Post added at 04:16 AM ---------- Previous post was at 03:56 AM ----------
the problem is not solved yet
===========================================
Lets back up here a bit. Has your package manager (PackageKit) or yum at the command line ever worked on this install of F12? Do you have internet access via your browser on this F12 machine? If you are posting to this forum from the F12 machine, then I suppose that answers the 2nd question. If you have working internet via your browser, then I don't know why yum would not work through the proxy as long as the correct entries in the yum.conf file were made. I don't know how you could tell for sure if the problem was with the proxy server or not.
By default, PackageKit check for updates, using yum, at intervals. Yum only allow one running instance. You can either wait for that to finish (assuming it will time out), or just kill the process, which should clear the LOCK file.
su -c 'kill -9 2208'
In the case above, the pid of that process was reported as 2208. You can also check if it's cleared with:
ls /var/lock/
Look for a file like: LCK...somename
where somename is indicative of the target process (PackageKit or yum). If it's stubborn, you can always just delete, as root, the lock file.
============================================
Glad to know you finally got the proxy server vs yum thing straightened out. Congrats. If making a mistake makes one an idiot, then we're all idiots. As for how you can run Kile or IPE, do you mean how to install them? If so, either use the PackageKit manager or yum to install them. I prefer yum at the command line, as root:
As to how to use either, I don't know, never used them. But if you're planning to upgrade to F14, then I wouldn't bother installing any programs until that task was done. As to how to update to F14 using yum, I'm not totally sure, but I think you would use something like this:
Now, in order for that to work, you'd need to edit the fedora.repo and fedora-updates.repo files again so that you commented out the new baseurl= lines that point to the archives, and then uncomment the original mirrorlist= lines. I would wait for confirmation from another person who has used the yum upgrade method if what I told you is valid, or search forum for threads discussing that, before proceeding.
How to sure about it.. that the problem is with proxy?
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
Now another problem I see if I enter:
yum install yumex
Code:
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 16 M RSS ( 32 MB VSZ)
Started: Sun Jan 23 03:54:09 2011 - 02:07 ago
State : Sleeping, pid: 2208
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 16 M RSS ( 32 MB VSZ)
Started: Sun Jan 23 03:54:09 2011 - 02:09 ago
State : Sleeping, pid: 2208---------- Post added at 04:16 AM ---------- Previous post was at 03:56 AM ----------
the problem is not solved yet
===========================================
Lets back up here a bit. Has your package manager (PackageKit) or yum at the command line ever worked on this install of F12? Do you have internet access via your browser on this F12 machine? If you are posting to this forum from the F12 machine, then I suppose that answers the 2nd question. If you have working internet via your browser, then I don't know why yum would not work through the proxy as long as the correct entries in the yum.conf file were made. I don't know how you could tell for sure if the problem was with the proxy server or not.
By default, PackageKit check for updates, using yum, at intervals. Yum only allow one running instance. You can either wait for that to finish (assuming it will time out), or just kill the process, which should clear the LOCK file.
su -c 'kill -9 2208'
In the case above, the pid of that process was reported as 2208. You can also check if it's cleared with:
ls /var/lock/
Look for a file like: LCK...somename
where somename is indicative of the target process (PackageKit or yum). If it's stubborn, you can always just delete, as root, the lock file.
============================================
Glad to know you finally got the proxy server vs yum thing straightened out. Congrats. If making a mistake makes one an idiot, then we're all idiots. As for how you can run Kile or IPE, do you mean how to install them? If so, either use the PackageKit manager or yum to install them. I prefer yum at the command line, as root:
Code:
yum install kile ipe
Code:
yum --releasever=14 update
