hello everybody,
I’ve tried to install squid 4.5 from rpm package which I’ve got from official squid site but I’ve got an error “nothing provides libc.so.6 GLIBC_2.27 needed by squid-4.5”. What should I do ?
Thank you.
[QUOTE=senigor;56558]hello everybody,
I’ve tried to install squid 4.5 from rpm package which I’ve got from official squid site but I’ve got an error “nothing provides libc.so.6 GLIBC_2.27 needed by squid-4.5”. What should I do ?
Thank you.[/QUOTE]
Hi and welcome to the Forum
Any reason not to use the SLES 15 4.4 version from SLE-Module-Server-Applications15-Updates? Plus there is the associated squid module for YaST for configuration.
Thank you very much)))
I know it, but squid 4.4 sends me error page
" ESI Processing failed.
The ESI processor returned:
esiProcess: Parse error at line 1:
not well-formed (invalid token)
This means that:
The surrogate was not able to process the ESI template "
when I try to open https://www.oracle.com/technetwork/pt/java/javase/downloads/jdk8-downloads-2133151.html page.
But squid 4.5 has that bug fixed (Bug 4253: ssl_bump prevents access to some web contents)
[QUOTE=senigor;56561]Thank you very much)))
I know it, but squid 4.4 sends me error page
" ESI Processing failed.
The ESI processor returned:
esiProcess: Parse error at line 1:
not well-formed (invalid token)
This means that:
The surrogate was not able to process the ESI template "
when I try to open https://www.oracle.com/technetwork/pt/java/javase/downloads/jdk8-downloads-2133151.html page.
But squid 4.5 has that bug fixed (Bug 4253: ssl_bump prevents access to some web contents)[/QUOTE]
Hi
I would imagine something like that would be backported, I see it’s mentioned in the bug report…
Ref: https://bugs.squid-cache.org/show_bug.cgi?id=4253
Let me ask my SUSE contacts.
Hi senigor,
[QUOTE=senigor;56558]hello everybody,
I’ve tried to install squid 4.5 from rpm package which I’ve got from official squid site but I’ve got an error “nothing provides libc.so.6 GLIBC_2.27 needed by squid-4.5”. What should I do ?
Thank you.[/QUOTE]
just to give some feedback on your original question: RPMs (except for so called “source RPMs”) contain binaries, which are built for a certain target platform. So having an RPM that the RPM command will generally accept, doesn’t mean you have the right software at hand. That’s why RPMs usually contain a load of dependencies, so it will only install on a system that matches those requirement, like shared libraries at a certain level.
You downloaded an RPM for a Squid that wasn’t built for the SLES15 platform.
Regards,
J
Hi
Are you in a position to open a Support Request (SR) about this?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.28-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!