Sponsored Content
Operating Systems Linux Fedora Yum repository not working in Fedora 16 Post 302994435 by Swathe on Wednesday 22nd of March 2017 07:31:45 PM
Old 03-22-2017
I'd seriously consider upgrading your other servers to a current version of Fedora as well.
 

10 More Discussions You Might Find Interesting

1. Red Hat

Local yum repository

Hi Friends, I have succesfully configured a local yum repository using ios image. Please let me know how i can synchronize the local repository with RHN. Is it possible, so that i can update the local repository with latest updates. Regards, Arumon (1 Reply)
Discussion started by: arumon
1 Replies

2. Red Hat

Trying to install boost 1.4.1 without success maybe yum repository is wrong

Hi I following the tutorial to install boost 1.4.1 in centos 5.6 32 bit But without success maybe it doesn't find it in my repository in yum , but also when I compile the lib It doesn't find the libs . The tutorial link: Compiling gearman on CentOS 5.6 - gearman | Google Groups the error... (1 Reply)
Discussion started by: umen
1 Replies

3. UNIX for Dummies Questions & Answers

Yum.conf baseurl is not working.

Hi friends, This is my /etc/yum.conf. I think my basurl and updateurl is not correct. When I am installing something, it is giving error. My yum.conf file is this : Please help me. Thanks, Mukund (0 Replies)
Discussion started by: mukundranjan
0 Replies

4. UNIX for Advanced & Expert Users

YUM GROUPLIST not working on SLES 11

I have a SLES 11 install with yum also installed. yum works when I try to install single packages. However, when i try the yum command: "yum grouplist" yum can not detect any groups. Is there some way to "enable" or install a grouplist feature in SLES 11 ? ==== details ==== SUSE Linux... (0 Replies)
Discussion started by: toro95037
0 Replies

5. Red Hat

Configure yum repository

how to configure yum server to get rpms from any repository or redhat repo. (4 Replies)
Discussion started by: leganti
4 Replies

6. Red Hat

local yum server on fedora 17

Hello friends I was creating local yum server from dvd but fedora 17 used pool method , i mean similar to debian for packages i.e a,b....z How can i create local yum server on fedora 17 like fedora 14,15,16 Any help Thanks (1 Reply)
Discussion started by: rink
1 Replies

7. Red Hat

Yum repository linking to ftp site of Redhat

I have a query that does Redhat have the link to the yum repository on its FTP site. In my environment, I have the file rhel-debuginfo.repo which has - baseurl=ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/$basearch/Debuginfo. I hope, my question is clear that is there a... (5 Replies)
Discussion started by: RHCE
5 Replies

8. Red Hat

Yum cannot install from repository

Hi guys, thanks for you help on this issue. I built a dvd repository on my server and when I try to install a package from it, I get this error ftp://10.0.0.12/pub/Packages/httpd-2.2.15-26.el6.x86_64.rpm: PYCURL ERROR 9 - "Server denied you to change to the given directory" I will... (2 Replies)
Discussion started by: cjashu
2 Replies

9. UNIX for Dummies Questions & Answers

Yum not working on client while able to do the ftp

1)check vsftpd service is running service vsftpd status 2)mkdir -p /var/ftp/pub/Packages Packages will contain all rpm packages 3)copy the xml file to Packages folder #cp -arf /mnt/hgfs/share/RHEL_DVD/Packages /var/ftp/pub/Packages 4)install the 3 required rpm rpm --nodeps -ivh... (0 Replies)
Discussion started by: joj123
0 Replies

10. Linux

Local YUM Repository for RHEL versions

Hello, I need to know regarding setting up of Local repositories so that I can update or install packages on other RHEL servers. In our environment we have many servers with different RHEL versions. Like RHEL 7.2, RHEL 7.3, RHEL 7.4, RHEL 7.5 Arch = x86_64 I have setup one Repo server;... (0 Replies)
Discussion started by: SunshineMLinux
0 Replies
pki-upgrade(8)							 PKI Upgrade Tool						    pki-upgrade(8)

NAME
pki-upgrade - Tool for upgrading system-wide configuration for Certificate System. SYNOPSIS
pki-upgrade [OPTIONS] DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro- cesses and upgrading the server configuration files. When upgrading Certificate System, the existing system configuration files (e.g. /etc/pki/pki.conf) may need to be upgraded because the content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in case there is a problem, the process can also be run manually using pki-upgrade. The system upgrade process is done incrementally using upgrade scriptlets. The upgrade process and scriptlet execution is monitored in upgrade trackers. A counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the com- ponent tracker shows the updated version number. The scriptlets are stored in the upgrade directory: /usr/share/pki/upgrade/<version>/<index>-<name> The version is the system version to be upgraded. The index is the script execution order. The name is the scriptlet name. During upgrade, the scriptlets will back up all changes to the filesystem into the following folder: /var/log/pki/upgrade/<version>/<index> The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles. The system upgrade process is tracked using this file: /etc/pki/pki.version The file stores the current configuration version and the last successful scriptlet index. OPTIONS
General options --silent Upgrade in silent mode. --status Show upgrade status only without performing the upgrade. --revert Revert the last version. -X Show advanced options. -v, --verbose Run in verbose mode. -h, --help Show this help message. Advanced options The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information. WARNING: These options may render the system unusable. --scriptlet-version <version> Run scriptlets for a specific version only. --scriptlet-index <index> Run a specific scriptlet only. --remove-tracker Remove the tracker. --reset-tracker Reset the tracker to match the package version. --set-tracker <version> Set the tracker to a specific version. OPERATIONS
Interactive mode By default, pki-upgrade will run interactively. It will ask for a confirmation before executing each scriptlet. % pki-upgrade If there is an error, it will stop and show the error. Silent mode The upgrade process can also be done silently without user interaction: % pki-upgrade --silent If there is an error, it will stop and show the error. Checking upgrade status It is possible to check the status of a running upgrade process. % pki-upgrade --status Troubleshooting If there is an error, rerun the upgrade in verbose mode: % pki-upgrade --verbose Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by re-running pki-upgrade. It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index: % pki-upgrade --scriptlet-version 10.0.1 --scriptlet-index 1 Reverting an upgrade If necessary, the upgrade can be reverted: % pki-upgrade --revert Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will be restored. FILES
/usr/sbin/pki-upgrade AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-upgrade was written by the Dogtag project. COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail- able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt. version 1.0 Jul 22, 2013 pki-upgrade(8)
All times are GMT -4. The time now is 01:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy