| Summary: | net-proxy/c-icap-0.3.5 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | drserge |
| Component: | [OLD] Server | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | mgorny, proxy-maint, rentorbuy, todd, treecleaner |
| Priority: | Normal | Keywords: | PMASKED |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | Pending removal: 2018-12-04 | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
c-icap 0.3.5 ebuild patch
files in FILESDIR patched to fix logrotate issues c-icap 0.5.2 ebuild FILES: conf FILES: init script logrotate fix |
||
|
Description
drserge
2015-07-11 12:00:49 UTC
Created attachment 407720 [details, diff]
c-icap 0.3.5 ebuild patch
compiles fine and was tested for a few hours with squid + squidclamav (works as expected)
Created attachment 407722 [details, diff]
files in FILESDIR patched to fix logrotate issues
server.log file path error fixed and added a relog function in init script because original logrotate script that used "restart" would cause c-icap to stop and never restart (in some conditions).
I can confirm this problem. ICAP server crashes on any restart, so weekly log rotation guarantees every Monday morning for me! c-icap 0.2.6 Stopping the service manually, waiting for it to finally die and then restarting works. Successfully tested ebuild and "files" patches for c-icap-0.4.4. Created attachment 490218 [details, diff]
c-icap 0.5.2 ebuild
Tested in production environment.
Created attachment 490220 [details, diff]
FILES: conf
conf.d file
Created attachment 490222 [details, diff]
FILES: init script
init script that correctly checks when daemon really quits
Created attachment 490224 [details, diff]
logrotate fix
This: net-proxy/squidclamav net-proxy/c-icap net-proxy/c-icap-modules Would need a dedicated maintainer, otherwise they are going to be always outdated and unattended. Does anyone want to proxy-maintain them? https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers Thanks (In reply to Pacho Ramos from comment #9) > This: > net-proxy/squidclamav > net-proxy/c-icap > net-proxy/c-icap-modules > > Would need a dedicated maintainer, otherwise they are going to be always > outdated and unattended. Does anyone want to proxy-maintain them? > https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers Hi, I already asked for that a long time ago, but never got any replies. I also asked if I could help with squid which has a maintainer, but could improve its ebuilds a bit. All related to web proxying. Glad to help, but if noone's willing to guide on the other end then I guess I'll keep maintaining my own private overlay (please don't read this as a complaint - it's just an observation). Pacho, I remember writing to you about this and other ebuilds (such as the pam feature that was mysteriously removed from Samba, and that I proposed an ebuild patch for it to be restored). I guess the Gentoo devs are way too busy, and portage is way too vast. The linked site has a lot of guides. If you just want to maintain the package, send a pull request with your version and someone will eventually get to it. (In reply to Michał Górny from comment #11) > The linked site has a lot of guides. If you just want to maintain the > package, send a pull request with your version and someone will eventually > get to it. Back in the days I proposed patched ebuilds, the git site was not there (several years ago). Setting up and using git for trivial ebuild patches is overkill, in my opinion. However, I'll take a llook at it if I ever get the chance. I also don't understand why ebuild features can be removed without some kind of explanation in the ChangeLog. This is not related to this "bug", but it's a bit frustrating in general. I don't know if using git would actually settle this. See bug at https://bugs.gentoo.org/590374. Am I missing something? Is there a URI I can check to see why a feature has been removed, other than looking at the changelog? Removing wrt #556306. |
