Thanks for the update Gwenole.
>
> The maintainer is listening but he won't repeat the same things
> endlessly.
> Warly fixed the hdlist problem, i.e. that's not a package problem.
> However, it does seem to reappear.
>
> Short story: Stefan tried to upload a glibc but obviously that was
> re
On Wed, 4 Jun 2003, Gerald Drouillard wrote:
> This issue has been talked about on the list but it doesn't appear that
> the maintainer of the package is listening.
The maintainer is listening but he won't repeat the same things endlessly.
Warly fixed the hdlist problem, i.e. that's not a packag
is listening. A workaround is to do a minimal 9.1
> install then upgrade to cooker.
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] Behalf Of Nelson Bartley
> > Sent: Wednesday, June 04, 2003 1:27 PM
> > To: [EMAIL
Nelson Bartley
> Sent: Wednesday, June 04, 2003 1:27 PM
> To: [EMAIL PROTECTED]
> Subject: [Cooker] ldconfig package on hd install
>
>
> Heyo,
>
> Not sure if this issue has been addressed, however over the last 2 days
> I have been attempting to perform an HD install of cooke
Heyo,
Not sure if this issue has been addressed, however over the last 2 days
I have been attempting to perform an HD install of cooker, with little
success. It appears that every time the installer is fired up, and
commences package instalation it errors on ldconfig-2.3.2-3mdk.i586.rpm,
and accor
Any time ldconfig is installed/upgraded it does so without problem or
complaint.
But there is a problem.
Anyone who uses WP8 needs ld.so-1.9.11-4mdk which ldconfig overwrites.
Knowing this the fix is simple, reinstall ld.so-1.9.11-4mdk, but most would
not even know what was causing the problem w
On August 21, 2001 03:46 am, you wrote:
> "J.P.Pasnak" <[EMAIL PROTECTED]> writes:
> > !,
> >
> > When anything calls 'ldconfig' I get the following:
> >
> > /sbin/ldconfig: /usr/lib/libkonsolepart.so is not a symbolic link
> >
> > /sbin/ldconfig: /usr/lib/libkcm_nsplugin.so is not a symbolic
"J.P.Pasnak" <[EMAIL PROTECTED]> writes:
> !,
>
> When anything calls 'ldconfig' I get the following:
>
> /sbin/ldconfig: /usr/lib/libkatecore.so is not a symbolic link
>
> /sbin/ldconfig: /usr/lib/libkateinterfaces.so is not a symbolic link
>
> /sbin/ldconfig: /usr/lib/libkcm_key
!,
When anything calls 'ldconfig' I get the following:
/sbin/ldconfig: /usr/lib/libkatecore.so is not a symbolic link
/sbin/ldconfig: /usr/lib/libkateinterfaces.so is not a symbolic link
/sbin/ldconfig: /usr/lib/libkcm_keyboard.so is not a symbolic link
/sbin/ldconfig: /usr/l
OS <[EMAIL PROTECTED]> writes:
> Hello,
>
> Could some nice kind person tell me how to stop ldconfig to stop complaining
> "/usr/lib/libkonsolepart.so is not a symbolic link".
>
> I can easily make it a symbolic link ! but then everytime I update KDE the
> warning comes back 'cos /usr/lib/lib
Hello,
Could some nice kind person tell me how to stop ldconfig to stop complaining
"/usr/lib/libkonsolepart.so is not a symbolic link".
I can easily make it a symbolic link ! but then everytime I update KDE the
warning comes back 'cos /usr/lib/libkonsolepart.so is created solid and not
as a
Patrick Poncet <[EMAIL PROTECTED]> writes:
> Chmouel Boudjnah wrote:
> >
> > Patrick Poncet <[EMAIL PROTECTED]> writes:
> >
> > > When installing new packages running ldconfig, I get the following
> > > error... Running ldconfig from the command line does the same... That
> > > after upgradin
Chmouel Boudjnah wrote:
>
> Patrick Poncet <[EMAIL PROTECTED]> writes:
>
> > When installing new packages running ldconfig, I get the following
> > error... Running ldconfig from the command line does the same... That
> > after upgrading glibc.
> >
> > ldconfig: warning: can't open /lib/libnss
Patrick Poncet <[EMAIL PROTECTED]> writes:
> When installing new packages running ldconfig, I get the following
> error... Running ldconfig from the command line does the same... That
> after upgrading glibc.
>
> ldconfig: warning: can't open /lib/libnss_nis.so.1 (No such file or
> directory),
When installing new packages running ldconfig, I get the following
error... Running ldconfig from the command line does the same... That
after upgrading glibc.
ldconfig: warning: can't open /lib/libnss_nis.so.1 (No such file or
directory), skipping
ldconfig: warning: can't open /lib/libnss_file
[root@cloud RPMS]# rpm -Fvh qt*
qt2 ##
/sbin/ldconfig: warning: can't open var/tmp/rpm-tmp.92102 (Not a directory), skipping
/sbin/ldconfig: warning: can't open 1 (No such file or directory), skipping
qt2-devel #
Please put a note in the %description to advise of hacks like this.
I missed recent discussion but used DURING_INSTALL to prevent menu
update. It took me some time to discover what was stopping ldconfig
working. The hacked version doesn't even respond to ldconfig -v.
- David.
Eugenio Diaz <[EMAIL PROTECTED]> writes:
> [root@fulgore:/etc]# more ld.so.conf
> /usr/lib
> /usr/i486-linux-libc5/lib
> /usr/lib
> /usr/lib
[...]
> /usr/lib
> /usr/lib
> [root@fulgore:/etc]#
>
> Well, this reduced the time for ldconfig to run from
> 5-10 min to 1-2 min!
hint, remove all occ
Pixel <[EMAIL PROTECTED]> writes:
> Pixel <[EMAIL PROTECTED]> writes:
>
> > > Well, ldconfig also updates links and in some cases it
> > > could cause and executable to not find the library (is
> > > this right, or am I making this up? he, he)
> >
> > you're right i just find that pb.
> > the g
Pixel <[EMAIL PROTECTED]> writes:
> > Well, ldconfig also updates links and in some cases it
> > could cause and executable to not find the library (is
> > this right, or am I making this up? he, he)
>
> you're right i just find that pb.
> the good(?) solution is to patch those packages missing
Eugenio Diaz <[EMAIL PROTECTED]> writes:
> --- Pixel <[EMAIL PROTECTED]> wrote:
> > i've just tested. I thought without calling
> > ldconfig, the binary would fail to
> > load the dynamic library. But it's not true :)
> > /etc/ld.so.cache is just for speedup.
>
> Well, ldconfig also update
--- Pixel <[EMAIL PROTECTED]> wrote:
> i've just tested. I thought without calling
> ldconfig, the binary would fail to
> load the dynamic library. But it's not true :)
> /etc/ld.so.cache is just for speedup.
Well, ldconfig also updates links and in some cases it
could cause and executable
Eugenio Diaz <[EMAIL PROTECTED]> writes:
[...]
>
> I think this is a real problem for the RPM subsystem, wouldn't it be
> wise to run this only once at the end when installing multiple packages?
i've just tested. I thought without calling ldconfig, the binary would fail to
load the dynamic lib
>
>
> Has anyone notice that this days almost every rpm has an "ldconfig"
> statement in the scripts. And almost always in both, the postinstall and
> the postuninstal, making it execute twice during a package upgrade.
>
yeh, but have to make sure the new so files are properly registered.
> T
Has anyone notice that this days almost every rpm has an "ldconfig"
statement in the scripts. And almost always in both, the postinstall and
the postuninstal, making it execute twice during a package upgrade.
To make things worse, we now have other things too, like update-menus,
that are run for
25 matches
Mail list logo
