|Anonymous | Login | Signup for a new account||2013-05-23 05:30 UTC|
|Main | My View | View Issues | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001416||CentOS-4||Other||public||2006-07-26 05:31||2006-11-22 22:40|
|Product Version||4.3 - i386|
|Target Version||Fixed in Version|
|Summary||0001416: libtool rebuilt for 0001156 not picked up by apt|
|Description||if libtool was rebuilt for gcc 3.4.5, it appears it's not the one being picked up by package ordering in apt:|
[root@shuttle ~]# apt-cache policy libtool
500 http://apt.platypus.bc.ca [^] i386/centos4/bish pkglist
*** 1.5.6-4.EL4.1.c4.3 0
500 http://mirror.centos.org [^] centos/4/apt/i386/os pkglist
100 RPM Database
It wants to upgrade to the older package, it seems. If a system has gcc installed, libtool cannot then be installed because the 'newest' package available (isn't new, but also) demands an older gcc. 'apt-get build-dep', the only remaining useful feature of apt-get, doesn't work here at all.
|Additional Information||send me a note if my description is so confusing as to be incomprehensible. I'm overtired.|
|Tags||No tags attached.|
From which repository is this libtool here?
[root@forge 4]# find . -name "libtool*" | grep -v c4
So it's not in one of the CentOS repositories. Are you mixing some local RHEL repository with CentOS ones? Was that machine a RedHat machine at some time? Or do you have something like a hardcoded path in your repo-file?
libtool-1.5.6-4.EL4.1.c4.3 ist the one from CentOS 4.3, CentOS 4.2 had libtool-1.5.6-4.EL4.1 in os and libtool-1.5.6-4.EL4.1.c4 in updates. I cannot find 4.1.1 anywhere.
No input from user. Can someone close this ticket?
"So it's not in one of the CentOS repositories."
Actually, the problematic package is probably coming from a local ftp mirror of ftp.linux.ncsu.edu, which still serves packages via FTP. Since the boxes are upgraded from older Centos4, you should find this problem if you upgrade a box from 4.0->4.1->4.2->4.3 .
The EL4.1.1. one is my rebuild of the package for the very problem in question.
I think. I'm on a really busy schedule right now, and I would need time to go over things again to be sure. If I need to defend this bug like a master's thesis, though, just to keep it around, just kill it.
Probably no need in "defending" the bug.
The input that *you* yourself rebuilt 4.1.1 wasn't really clear from your bug report, that's why I asked.
this issue should be resolved with versions:
in the CentOS-Testing repo.
|2006-07-26 05:31||bishop||New Issue|
|2006-07-26 05:31||bishop||Status||new => assigned|
|2006-07-26 09:45||range||Note Added: 0003724|
|2006-08-10 09:49||range||Note Added: 0003778|
|2006-08-10 15:13||bishop||Note Added: 0003780|
|2006-08-11 08:18||range||Note Added: 0003784|
|2006-11-22 22:40||JohnnyHughes||Status||assigned => resolved|
|2006-11-22 22:40||JohnnyHughes||Resolution||open => fixed|
|2006-11-22 22:40||JohnnyHughes||Note Added: 0004214|
|Copyright © 2000 - 2011 MantisBT Group|