Description of problem: I couldn't start squid + a redirector Rejik (http://rejik.ru/index_ru_4_0.html) In ~/var/log/squid/cache.log saw an error message: mimeLoadIconFile: /usr/share/squid/icons/silk/image.png: (2) No such file or directory I added directory /usr/share/squid/icons/silk/* And redirector works. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
regarding google, looks like we are not alone to miss this file so don't know
Keywords: (none) => TriagedAssignee: bugsquad => luis.daniel.lucioSource RPM: (none) => squid
Interesting. This seems to be due to the way we run make install in the %install section of the SPEC: %makeinstall icondir=%{buildroot}%{_datadir}/icons DEFAULT_LOG_DIR=%{buildroot}%{_logdir}/squid DEFAULT_ERROR_DIR=%{buildroot}%{_datadir}/errors DEFAULT_ICON_DIR=%{buildroot}%{_datadir}/icons The configure script doesn't seem to have a way to specify the icon directory (or the error directory, whatever that is for), so if anything is hardcoded in the source code, overriding it in make install is probably not going to fix it, possibly leading to this kind of bug. Fedora's spec has the equivalent of: %makeinstall_std instead of %makeinstall, and it doesn't specify any other directories. It looks like our spec has been this way dating back to Mandriva times, but is probably wrong and we should probably just do %makeinstall_std.
CC: (none) => luigiwalser
I've committed the change in Cauldron: http://svnweb.mageia.org/packages?view=revision&revision=599531 I'd like to see it get some testing there before backporting it. In the meantime, as a workaround, running the following command as root should solve the problem: ln -s . /usr/share/squid/icons/silk Note that you'll need to remove that symlink before updating to a package where this fix is committed: rm /usr/share/squid/icons/silk
solved the problem: ln -s . /usr/share/squid/icons/silk Thanks for the help
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Fixed in Mageia 5.
Status: NEW => RESOLVEDResolution: (none) => OLD