Bug 522038
| Summary: | Unable to open language file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eddie Lania <eddie> |
| Component: | squidGuard | Assignee: | Gwyn Ciesla <gwync> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | gwync, itamar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-27 18:10:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eddie Lania
2009-09-09 09:14:25 UTC
I think that the squidguard rpm package does not include the babel samples that are in the squidguard 1.4 tarball. Try this koji build: http://koji.fedoraproject.org/koji/buildinfo?buildID=131280 Dear Jon, Thank you for your help. I did not update squidGuard with the rpm from the koji build but instead used the babel files from it to update my current squidGuard. All is working fine now. Can we aspect it that the next regular squidGuard release rpm will include these files? Kind regards, Eddie. Yes. I'll push the update. Thanks! squidGuard-1.4-6.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/squidGuard-1.4-6.fc11 squidGuard-1.4-6.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/squidGuard-1.4-6.fc10 squidGuard-1.4-6.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update squidGuard'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-9662 squidGuard-1.4-6.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update squidGuard'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9681 When I installed the new sqquidGuard rpm, the message below appeared on the screen and I think the location of the blacklists is wrong. Also, my custom settings in squidGuard.cgi were lost. So I think squidGuard should be changed to avoid the location of the blacklists to be under "/var/squidGuard/blacklists/blacklists" and also the various config options in squidGuard.cgi should be restored after updating squidGuard. Also, squidGuard.log should reside in /var/log/squidGuard instead of /var/log/squid and a symlink from /var/log/squidGuard/squidGuard.log to /var/log/squid should/could be made. This enables squidGuard to properly write to it's logfile. Downloading Packages: Setting up and reading Presto delta metadata updates-testing/prestodelta | 121 kB 00:00 Processing delta metadata /var/squidGuard/blacklists/blacklists/README: No such file or directory /var/squidGuard/blacklists/blacklists/ads/domains: No such file or directory /var/squidGuard/blacklists/blacklists/ads/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/domains.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/urls: No such file or directory /var/squidGuard/blacklists/blacklists/ads/urls.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/urls.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/urls.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/ads/urls.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/domains: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/domains.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/urls: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/urls.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/urls.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/aggressive/urls.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/domains: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/domains.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/urls: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/urls.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/audio-video/urls.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/domains: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/domains.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/urls: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/urls.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/urls.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/urls.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/urls.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/drugs/urls.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/gambling/domains: No such file or directory /var/squidGuard/blacklists/blacklists/gambling/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/gambling/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/gambling/urls: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/domains: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/domains.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/urls: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/urls.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/hacking/urls.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/mail/domains: No such file or directory /var/squidGuard/blacklists/blacklists/porn/domains: No such file or directory /var/squidGuard/blacklists/blacklists/porn/expressions: No such file or directory /var/squidGuard/blacklists/blacklists/porn/urls: No such file or directory /var/squidGuard/blacklists/blacklists/proxy/domains: No such file or directory /var/squidGuard/blacklists/blacklists/proxy/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/proxy/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/proxy/urls: No such file or directory /var/squidGuard/blacklists/blacklists/violence/domains: No such file or directory /var/squidGuard/blacklists/blacklists/violence/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/violence/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/violence/domains.20051105.diff: No such file or directory /var/squidGuard/blacklists/blacklists/violence/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/violence/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/violence/urls: No such file or directory /var/squidGuard/blacklists/blacklists/warez/domains: No such file or directory /var/squidGuard/blacklists/blacklists/warez/domains.20051022.diff: No such file or directory /var/squidGuard/blacklists/blacklists/warez/domains.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/warez/domains.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/warez/domains.20051119.diff: No such file or directory /var/squidGuard/blacklists/blacklists/warez/urls: No such file or directory /var/squidGuard/blacklists/blacklists/warez/urls.20051029.diff: No such file or directory /var/squidGuard/blacklists/blacklists/warez/urls.20051112.diff: No such file or directory /var/squidGuard/blacklists/blacklists/warez/urls.20051119.diff: No such file or directory /var/www/cgi-bin/squidGuard-simple.cgi: contents have been changed /var/www/cgi-bin/squidGuard.cgi: contents have been changed delta does not match installed data Package(s) data still to download: 2.3 M squidGuard-1.4-6.fc11.i586.rpm | 2.3 MB 00:01 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : squidGuard-1.4-6.fc11.i586 1/2 /etc/squid/squidGuard.conf created as /etc/squid/squidGuard.conf.rpmnew Cleanup : squidGuard-1.4-4.fc11.i586 2/2 Updated: squidGuard.i586 0:1.4-6.fc11 Complete! Suggestion to change /etc/logrotate.d/squidGuard from:
/var/log/squid/squidGuard.log {
weekly
compress
notifempty
missingok
}
to:
/var/log/squidGuard/* {
weekly
olddir /var/log/squidGuard/old
compress
notifempty
missingok
}
Or I end up with massive logfiles for every blocklist in /var/log/squidGuard.
Regards,
Eddie.
One more thing (sorry). In /etc/cron.daily/squidGuard the default download location of the new squidGuard blacklists is: http://ftp.teledanmark.no/pub/www/proxy/squidguard/contrib/blacklists.tar.gz however, this url is not valid anymore. Blacklists now are downloadable from: http://squidguard.mesd.k12.or.us/blacklists.tgz and so this should be changed accordingly. Kind regards, Eddie. I've got most of this ready to go. What do you mean by 'avoiding' the blacklist directory, exactly? Do you mean updating the RPM shouldn't alter it? No, I mean it should avoid creating a new blacklists directory inside the already existing /var/squidGuard/blacklist directory. Now I get two blacklist directories. One under /var/squidGuard and one more inside /var/squidGuard/blacklists. So this ends up in: /var/squidGuard/blacklist/blacklists/ You see? That is two times blacklists. Sorry for my bad English. I hope it explains it well enough though. Regards, Eddie. I see. I *think* I've fixed that now. Man, I'm an American. You're English is better than what I get from most native speakers. :) (In reply to comment #14) > I see. I *think* I've fixed that now. Jon, Since your last comment (see above), I have not heard from you again. You say that you *think* you fixed it but there is nothing to test since you haven't build a new rpm yet. But the status of the bug is "retest". That makes me wonder: how long will it last before your updated rpm is ready? Regards, Eddie. I'll commit my fixes for this and build in rawhide so you can test, though 523607 is still unaddressed. I was hoping to do one update for both, but tempus fugit. (In reply to comment #16) > I'll commit my fixes for this and build in rawhide so you can test, though > 523607 is still unaddressed. I was hoping to do one update for both, but > tempus fugit. Jon, Don't worry and take your time. And please don't be offended by my comments (if you would be so). If you want to do one update to solve both issues then I am comfortable with that. I will wait patiently. Regards, Eddie. No, that's quite alright. I've just had a lot on my plate. This should work on F-11, if not, I can build for that as well. The final update will be built for F-11. http://koji.fedoraproject.org/koji/taskinfo?taskID=1761543 squidGuard-1.4-8.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/squidGuard-1.4-8.fc10 squidGuard-1.4-8.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/squidGuard-1.4-8.fc11 Heads up, an update with this and a security issue is coming to stable. squidGuard-1.4-8.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. squidGuard-1.4-8.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. Is is solved, thank you. |