Hello
i found a problem with dependencies in Centos 4
What I did:
I installed CentOS from my >>> 4.0 <<< CD media with httpd server.
this are installed versions:
httpd-2.0.52-9.ent.centos4.1.i386.rpm and one of its dependecy apr-0.9.4-24.1.i386.rpm
then I tried make update
"yum update" and I get ... ... ... --> Running transaction check --> Processing Dependency: apr >= 0.9.4-24.2 for package: httpd --> Finished Dependency Resolution Error: Missing Dependency: apr >= 0.9.4-24.2 is needed by package httpd
I discovered that this RPM in centos/4/updates/i386/RPMS/
httpd-2.0.52-12.1.ent.centos4.i386.rpm
depends on apr-0.9.4-24.2
but apr-0.9.4-24.2 is not in updates directory ...
there is apr-0.9.4-24.3.i386.rpm in centos/4/os/i386/CentOS/RPMS/ which is in Centos 4.1
But my system is 4.0 and it never even listen about apr-0.9.4-24.3. My yum knows only update directory centos/4/updates/i386/RPMS/ and its CD media.
Did I something wrong?
Petr Klíma
e-mail: qaxi@seznam.cz
On Wed, 2005-08-10 at 09:58 +0200, Petr Klíma wrote:
Hello
i found a problem with dependencies in Centos 4
What I did:
I installed CentOS from my >>> 4.0 <<< CD media with httpd server.
this are installed versions:
httpd-2.0.52-9.ent.centos4.1.i386.rpm and one of its dependecy apr-0.9.4-24.1.i386.rpm
then I tried make update
"yum update" and I get ... ... ... --> Running transaction check --> Processing Dependency: apr >= 0.9.4-24.2 for package: httpd --> Finished Dependency Resolution Error: Missing Dependency: apr >= 0.9.4-24.2 is needed by package httpd
I discovered that this RPM in centos/4/updates/i386/RPMS/
httpd-2.0.52-12.1.ent.centos4.i386.rpm
depends on apr-0.9.4-24.2
but apr-0.9.4-24.2 is not in updates directory ...
there is apr-0.9.4-24.3.i386.rpm in centos/4/os/i386/CentOS/RPMS/ which is in Centos 4.1
But my system is 4.0 and it never even listen about apr-0.9.4-24.3. My yum knows only update directory centos/4/updates/i386/RPMS/ and its CD media.
Did I something wrong?
When a new update set is released (ie 4.1, 3.5, etc.), only the latest [base] and [updates] are included in the main tree.
Taken together, the base and updates will be the latest version.
If you install from old media (3.3, 4.0) then you need to have [base] and [updates] in your yum configuration.
(or get the 4.1 ISOs to use as your [base])
When a new update set is released (ie 4.1, 3.5, etc.), only the latest [base] and [updates] are included in the main tree.
Taken together, the base and updates will be the latest version.
If you install from old media (3.3, 4.0) then you need to have [base] and [updates] in your yum configuration.
(or get the 4.1 ISOs to use as your [base])
So I can yust say
IT IS WRONG
there were a lot of talks about it here:
When you install CentOS x.0 and you run "yum update" you get finaly lates CentOS X.Y ...
CentOS X.4 is CentOS X.0 + all released updates ...
and from your answer it seems it is gone CentOS 4.1 have diferent versions of SW then CentOS 4.0 + updates
I know CentOS depend on RH releases but presented strategy is brain dead
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
Before half a year there was talk about high bandwith, so lets download all the stuff.
Petr Klíma
e-mail: petr.klima@madeta-group.cz MADETA Group a.s. phone: +420 389 136 209 Rudolfovská 246/83 web: http://www.madeta-group.cz 370 50 České Budějovice Czech Republic
On Wed, 2005-08-10 at 10:49 +0200, Petr Klíma wrote:
When a new update set is released (ie 4.1, 3.5, etc.), only the latest [base] and [updates] are included in the main tree.
Taken together, the base and updates will be the latest version.
If you install from old media (3.3, 4.0) then you need to have [base] and [updates] in your yum configuration.
(or get the 4.1 ISOs to use as your [base])
So I can yust say
IT IS WRONG
Wrong or Right is not relevant
it is what it is
CentOS has been doing things the same way since it's inception ...
there were a lot of talks about it here:
When you install CentOS x.0 and you run "yum update" you get finaly lates CentOS X.Y ...
CentOS X.4 is CentOS X.0 + all released updates ...
and from your answer it seems it is gone CentOS 4.1 have diferent versions of SW then CentOS 4.0 + updates
I know CentOS depend on RH releases but presented strategy is brain dead
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
Before half a year there was talk about high bandwith, so lets download all the stuff.
If you want to have a local mirror ... then you need to mirror /centos/4/
it will always be up2date
This is the same with CentOS 3 and it is absolutely not a change to the way we have been doing things for almost 2 years
Johnny Hughes wrote:
Wrong or Right is not relevant
It may not be wrong, but I think is is not good... or at least, it could be better.
it is what it is
CentOS has been doing things the same way since it's inception ...
CentOS-3 & CentOS-4 do this. CentOS-2 & RedHat just keep putting updates in the updates. It does not matter what you install from, all updates is always completely up to date.
I would like to see CentOS 3 & 4 change to the CentOS-2/RedHat approach. I have gathered some thoughts on this and related issues here: http://www.byteclub.net/wiki/index.php?title=Manage_RPM_based_updates
John.
there were a lot of talks about it here:
When you install CentOS x.0 and you run "yum update" you get finaly lates CentOS X.Y ...
CentOS X.4 is CentOS X.0 + all released updates ...
and from your answer it seems it is gone CentOS 4.1 have diferent versions of SW then CentOS 4.0 + updates
I know CentOS depend on RH releases but presented strategy is brain dead
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
Before half a year there was talk about high bandwith, so lets download all the stuff.
If you want to have a local mirror ... then you need to mirror /centos/4/
it will always be up2date
This is the same with CentOS 3 and it is absolutely not a change to the way we have been doing things for almost 2 years
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Petr Klíma wrote:
Taken together, the base and updates will be the latest version.
Which is the right way of doing things, since that is what constitues the distro. ( base + updates )
So I can yust say
IT IS WRONG
Why ?
there were a lot of talks about it here:
When you install CentOS x.0 and you run "yum update" you get finaly lates CentOS X.Y ...
yup, that is correct.
and from your answer it seems it is gone CentOS 4.1 have diferent versions of SW then CentOS 4.0 + updates
What makes you think that ?
You might want to take a look at how yum works with repositories... ( hint: it dosent pull updates only from the updates repo ).
I know CentOS depend on RH releases but presented strategy is brain dead
Again, can you please elaborate on this ?
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
This is indeed the right way of doing things. I am not sure what your problem is, except that you will save hdd space like this. Only changed packages ( using rsync ? ) are going to be downloaded anyway. And if you are using a network install to setup the machines, each machine will come up with a 'recent' install base.
Before half a year there was talk about high bandwith, so lets download all the stuff.
While bandwidth issues have eased up a bit, it still makes sense to run a local mirror if you have more than a few machines.
- K
Sorry, I know I should keep cool but what I describe newer hapend in CentOS 3 till now.
I have several machines installed from CentOS 3.0 media and I newer need download other thing except "updates" .
I remember cca. 4-6 months back there was major change in repository organisation. (There was a long talk about "How older releases should change its yum.conf URL to work with new layout). Isn't this result of the change? Or am I tolally wrong?
Former model - where all releases "updates" had its directory with appropriate updates and not yust link to "hopefully global updates". It was HDD hungry, I know.
But
Newer model - where all releases are linky to one directory
Karanbir Singh napsal(a):
Petr Klíma wrote:
Taken together, the base and updates will be the latest version.
Which is the right way of doing things, since that is what constitues the distro. ( base + updates )
So I can yust say
IT IS WRONG
Why ?
there were a lot of talks about it here:
When you install CentOS x.0 and you run "yum update" you get finaly lates CentOS X.Y ...
yup, that is correct.
and from your answer it seems it is gone CentOS 4.1 have diferent versions of SW then CentOS 4.0 + updates
What makes you think that ?
You might want to take a look at how yum works with repositories... ( hint: it dosent pull updates only from the updates repo ).
I know CentOS depend on RH releases but presented strategy is brain dead
Again, can you please elaborate on this ?
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
This is indeed the right way of doing things. I am not sure what your problem is, except that you will save hdd space like this. Only changed packages ( using rsync ? ) are going to be downloaded anyway. And if you are using a network install to setup the machines, each machine will come up with a 'recent' install base.
Before half a year there was talk about high bandwith, so lets download all the stuff.
While bandwidth issues have eased up a bit, it still makes sense to run a local mirror if you have more than a few machines.
- K
On Wed, 2005-08-10 at 12:30 +0200, Petr Klíma wrote:
Sorry, I know I should keep cool but what I describe newer hapend in CentOS 3 till now.
3.1 was the first release ... it was linked to 3.3 after that was released
3.3 was linked to 3.4 after that was released
3.4 was linked to 3.5, etc.
That has been the same since the beginning
I have several machines installed from CentOS 3.0 media and I newer need download other thing except "updates" .
I remember cca. 4-6 months back there was major change in repository organisation. (There was a long talk about "How older releases should change its yum.conf URL to work with new layout). Isn't this result of the change? Or am I tolally wrong?
The only thing that changed was that we added a 3/ and 4/ symlink that always stays updated (points to the current release) so that changes are not required to the yum configuration and it matches the upstream version number ... so things like dag's repo work with the version number.
Former model - where all releases "updates" had its directory with appropriate updates and not yust link to "hopefully global updates". It was HDD hungry, I know.
That isn't true ... 3.1 was removed after 3.3 was released
and 3.3 was removed after 3.4 was released ... this was all before CentOS-4 was released
The method has always been the same ... only the /3 and /4 was added around the 3.4 release time.
But
Newer model - where all releases are linky to one directory
That has always been the case
That isn't true ... 3.1 was removed after 3.3 was released
and 3.3 was removed after 3.4 was released ... this was all before CentOS-4 was released
The method has always been the same ... only the /3 and /4 was added around the 3.4 release time.
But
Newer model - where all releases are linky to one directory
That has always been the case
OK, who should know it better you.
I start downloading 4.1 and 3.5 isos.
Just question
It would be nice to have in CentOS/4/isos/i386/ files named CentOS-4-i386-bin2of4.iso instead of CentOS-4.1-i386-bin2of4.iso . (-4- in 4 directory nad -4.1- in 4.1 dir)
It would save configuration time for people with the same problem as me.
BTW: despite all I wrote today CentOS(and other RHEL build) is one of the 5 best things that happend in last 2 years in Linux
Thank you
Petr Klíma
e-mail: qaxi@seznam.cz
On Wednesday 10 of August 2005 10:49, Petr Klíma wrote:
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
Before half a year there was talk about high bandwith, so lets download all the stuff.
if you are going to set up a mirror, i would highly recommend you to use YAM tool which can be found in Dag's repository. http://dag.wieers.com/packages/yam/ ...
T.L.
I have several servers with fixed setup and I have local mirror. Now it seems I have to mirror not only "updates" but "updates" and "base".
Before half a year there was talk about high bandwith, so lets download all the stuff.
if you are going to set up a mirror, i would highly recommend you to use YAM tool which can be found in Dag's repository. http://dag.wieers.com/packages/yam/ ...
You got it
Exactly
It is the problem. I use YAM. I use it to mirror Centos updates, tftp netboots and my local repository. Because of creating netboot environment it wants iso images of the distribution. And that is the problem = I have to check, download and reconfigure to have the last ISOs
as I sayd (or wrote ?) in 3.3 I had no souch problem ...
Petr Klíma
e-mail: petr.klima@madeta-group.cz MADETA Group a.s. phone: +420 389 136 209 Rudolfovská 246/83 web: http://www.madeta-group.cz 370 50 České Budějovice Czech Republic
-
John Newbigin -
Johnny Hughes -
Karanbir Singh -
Petr Klíma -
Petr Klíma -
Tomáš Lašťovička