[Yum] RE: Yum Digest, Vol 19, Issue 9
Amar Pradhan
pqa at cypress.com
Wed Feb 16 08:40:21 UTC 2005
Hi,
I have a yum running on RH8.Few day's back I had to change by web server
Document Root Path from /home/www/html to /home/www/html/common.
After making the above changes, yum stopped working and then I had to edit
yum.conf file and changed the baseurl path from http:// to ftp: and it
started working fine. But from the other server I am still getting the
following error message.
Sent: Saturday, February 12, 2005 3:30 PM
> Subject: Cron <root at ahmadabad> run-parts /etc/cron.daily
>
>
>> /etc/cron.daily/yum.cron:
>>
>> Error getting file
>> http://157.95.32.2/pub/yum-repository/redhat/8.0/i386/headers/header.
>> info [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
>> Error getting file
>> http://157.95.32.2/pub/yum-repository/redhat/8.0/i386/headers/header.
>> info [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
>>
When I run yum list it doesn't give me any error, Can anyone help?
Regards
Amar
-----Original Message-----
From: yum-bounces at lists.dulug.duke.edu
[mailto:yum-bounces at lists.dulug.duke.edu] On Behalf Of
yum-request at lists.dulug.duke.edu
Sent: Sunday, February 13, 2005 10:30 PM
To: yum at lists.dulug.duke.edu
Subject: Yum Digest, Vol 19, Issue 9
Send Yum mailing list submissions to
yum at lists.dulug.duke.edu
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.dulug.duke.edu/mailman/listinfo/yum
or, via email, send a message with subject or body 'help' to
yum-request at lists.dulug.duke.edu
You can reach the person managing the list at
yum-owner at lists.dulug.duke.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yum digest..."
Today's Topics:
1. Re: Yum hang while updating (Anand Buddhdev)
2. Re: Yum hang while updating (seth vidal)
3. Newbie question (John Logsdon)
4. Re: repository wildcards (Gijs Hollestelle)
----------------------------------------------------------------------
Message: 1
Date: Sat, 12 Feb 2005 18:53:37 +0100
From: Anand Buddhdev <arb at anand.org>
Subject: Re: [Yum] Yum hang while updating
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID: <420E42A1.5000002 at anand.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
fredn1 at gmx.de wrote:
Hi Fred,
>>I noticed that several packages are now duplicated in the RPM database,
>>for example:
>>
>># rpm -q vixie-cron
>>vixie-cron-3.0.1-87
>>vixie-cron-4.1-20_FC3
>
> Do the following for each of the duplicated packages
> to remove the older version of each:
>
> rpm -ev vixie-cron-3.0.1-87
Thanks for this advice. I eventually just made a list of the duplicates,
and used "rpm -ev" to remove them. I have been experimenting with
another package manager on my laptop, called smart[1], which works much
like yum, but has some improvements. It downloads repo metadata and
packages in parallel, making the process faster, but more interestingly,
as it upgrades packages, it removes the old one immediately. Thus, a
hung process would not leave the RPM database in such a mess. Perhaps
yum could be modified to work like smart, to guard against this kind of
problem.
[1] http://www.smartpm.org
------------------------------
Message: 2
Date: Sat, 12 Feb 2005 13:52:44 -0500
From: seth vidal <skvidal at phy.duke.edu>
Subject: Re: [Yum] Yum hang while updating
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID: <1108234364.3823.43.camel at cutter>
Content-Type: text/plain
>Thanks for this advice. I eventually just made a list of the duplicates,
>and used "rpm -ev" to remove them. I have been experimenting with
>another package manager on my laptop, called smart[1], which works much
>like yum, but has some improvements. It downloads repo metadata and
>packages in parallel, making the process faster, but more interestingly,
>as it upgrades packages, it removes the old one immediately. Thus, a
>hung process would not leave the RPM database in such a mess. Perhaps
>yum could be modified to work like smart, to guard against this kind of
>problem.
>
Then I think smart is reordering the transaction set using its own
ordering algorithm. To be clear the process that yum uses is:
- pack the rpm ts
- ts.order()
- ts.run()
so the order the packages are added/removed in transaction set is
dependent on rpm, not yum.
-sv
------------------------------
Message: 3
Date: Sun, 13 Feb 2005 10:04:53 +0000 (GMT)
From: John Logsdon <j.logsdon at quantex-research.com>
Subject: [Yum] Newbie question
To: Yum at lists.dulug.duke.edu
Message-ID:
<Pine.LNX.4.10.10502130950461.11809-100000 at quantex-research.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hello and thanks for yum. I am trying to move from RH7.3 to Fedora Core 2
in two steps - ie RH7.3->RH8->FC2.
Three questions:
1) Is there a description of the yum.conf file somewhere? Like a HOWTO or
something? Particularly for moving 7.3->8?
2) If conflicts arise, is it normal for the upgrade procedure to stop
after downloading the headers or can this be overridden?
3) I actually have the RH8 and FC2 disks. Can yum work with these (or
copies on disk where the RPMS contents are all in one directory) instead
of downloading (I can always update the packages later)? Or is it better
to use the standard RH upgrade facility?
Details:
I installed the appropriate yum and successfully updated everything in
RH7.3. I modified the yum.conf file to move to RH8 thus:
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
gpgcheck=0
tolerant=1
exactarch=1
failovermethod=priority # First listed baseurl first each time
#[base]
#name=Red Hat Linux $releasever base
#baseurl=http://mirror.dulug.duke.edu/pub/yum-repository/redhat/$releasever/
$basearch/
#name=Red Hat Linux $releasever - $basearch - os
#baseurl=http://ayo.ie.freshrpms.net/redhat/$releasever/$basearch/os
#[updates]
#name=Red Hat Linux $releasever updates
#baseurl=http://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/$rel
easever/
#name=Red Hat Linux $releasever - $basearch - updates
#baseurl=http://ayo.ie.freshrpms.net/redhat/$releasever/$basearch/updates
#[freshrpms]
#name=Red Hat Linux $releasever - $basearch - freshrpms
#baseurl=http://ayo.ie.freshrpms.net/redhat/$releasever/$basearch/freshrpms
[redhat8]
name=Redhat 8
baseurl=http://ftp.uk3.freshrpms.net/pub/freshrpms/ayo/redhat/8.0/i386/os/
#
http://uk2.freshrpms.net/sites/ftp.freshrpms.net/ayo/redhat/8.0/i386/os/
# http://ie.freshrpms.net/pub/freshrpms/ayo/redhat/8.0/i386/os/
[redhat8freshrpms]
name=Redhat 8 freshrpms
baseurl=http://ftp.uk3.freshrpms.net/pub/freshrpms/ayo/redhat/8.0/i386/fresh
rpms/
#
http://uk2.freshrpms.net/sites/ftp.freshrpms.net/ayo/redhat/8.0/i386/freshrp
ms/
# http://ie.freshrpms.net/pub/freshrpms/ayo/redhat/8.0/i386/freshrpms/
Note I commented out the RH7.3 [base] section as yum kept interrogating
RH7.3 for obvious reasons.
yum -t -y upgrade then downloads the headers for RH8 but there were some
conflicts - eg postgresql-python and python. I removed these various
packages and reinstalled them and the conflicts went away except for
between initscripts and kbd. Removing the former would be pretty
fundamental if anything went wrong so I removed and reinstalled kbdconfig
- I could find nothing else that would cause the conflict. This now
reports various packages that need libnewt.so.0.50 (not provided) so I
tried installing newt (where that file lives) with the same response. So
at the moment I am stuck with RH7.3 but almost all the headers installed
for RH8...
TIA
John
John Logsdon "Try to make things as simple
Quantex Research Ltd, Manchester UK as possible but not simpler"
j.logsdon at quantex-research.com a.einstein at relativity.org
+44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
------------------------------
Message: 4
Date: Sun, 13 Feb 2005 14:29:16 +0100
From: Gijs Hollestelle <g.hollestelle at gmail.com>
Subject: Re: [Yum] repository wildcards
To: Terrel Shumway <terrel at gmail.com>, "Yellowdog Updater, Modified"
<yum at lists.dulug.duke.edu>
Message-ID: <95da2d2905021305293ce43a4d at mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII
On Fri, 11 Feb 2005 04:45:32 -0700, Terrel Shumway <terrel at gmail.com> wrote:
> The attached patch (against the 2.1.13 tarball) allows you to use
> wildcards for --enablerepo and --disablerepo
> https://lists.dulug.duke.edu/pipermail/yum/2005-February/005985.html
>
> I have all of my fedora core repos named starting with "FC-" so I can
> say --enablerepo=FC-*
Hi Terrel,
Thanks for your patch, I've had a look at it and it looks good, but I
think you might have overdone it a little bit (IMO) what about just
using fnmatch wildcards for now and adding the other types of matches
when they are needed? I also noticed the comment for enableRepo says
'disable a repository from use' instead of enable, but that seems to
be a bug in the original yum source code.
Two general questions/considerations:
1) Is there a reason for letting findRepos return a generator instead
of a tuple or list?
2) Should there be a warning or error when someone specifies a
wildcard that matches nothing (for example --disablerepo=mispelled-*)?
Note that all of the above is just my opinion.
> P.S. Is this the right way to submit patches?
There is also a yum-devel list that might be more appropriate.
Kind regards,
Gijs
------------------------------
_______________________________________________
Yum mailing list
Yum at lists.dulug.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum
End of Yum Digest, Vol 19, Issue 9
**********************************
More information about the Yum
mailing list