Univention Bugzilla – Full Text Bug Listing |
Summary: | Add option dbtemp to squidguard | ||
---|---|---|---|
Product: | UCS | Reporter: | Sönke Schwardt-Krummrich <schwardt> |
Component: | Squid | Assignee: | Sönke Schwardt-Krummrich <schwardt> |
Status: | CLOSED FIXED | QA Contact: | Florian Best <best> |
Severity: | normal | ||
Priority: | P5 | CC: | best, walkenhorst |
Version: | UCS 4.1 | ||
Target Milestone: | UCS 4.1-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Bug Depends on: | 40541, 40595 | ||
Bug Blocks: |
Description
Sönke Schwardt-Krummrich
2016-02-05 12:11:50 CET
squidguard has been patched. A new config option "dbtemp" has been added. If defined, the bdb backing files will be placed within that directory. If unset, squidguard shows the old behaviour (using /var/tmp as temp dir for backing files). squidguard.yaml: r67234 | Bug #40592: updated squidguard.yaml r67215 | Bug #40592: added squidguard.yaml Please note: squidguard has been patched and built in ucs-school-4.1 AND errata4.1-0 to avoid problems with security/debian updates later on. The build version of the errata scope is larger than the version of the ucs-school scope. Patches: patches/squidguard/4.1-0-0-ucs/1.5-1-errata4.1-0/001-added_dbtemp_option.patch patches/squidguard/4.1-0-0-ucs/1.5-1-ucs-school-4.1/001-added_dbtemp_option.patch I can't reproduce the issue. Code change looks okay (.bison file was not adapted). OK: squidguard 1.5-1.24.201602051323 OK: squidguard 1.5-1.26.201602051325 OK: YAML (In reply to Florian Best from comment #2) > I can't reproduce the issue. Code change looks okay (.bison file was not > adapted). I rechecked the Makefile. The only part where bison files are touched are the following two targets: y.tab.c y.tab.h: sg.y sg.h @if [ "$(YACC)" = "yacc" ]; then \ if [ ! -x $(YACC) ]; then \ echo " " ; \ echo "No yacc/bison found. Copy prepared files for y.tab.h and y.tab.c over. " ; \ echo " " ; \ cp y.tab.h.bison y.tab.h ; \ cp y.tab.c.bison y.tab.c ; \ else \ $(YACC) -d sg.y ; \ fi ; \ else \ $(YACC) -d sg.y ; \ fi ; y.tab.c.bison y.tab.h.bison: sg.y sg.h $(YACC) -d sg.y mv -f y.tab.c y.tab.c.bison mv -f y.tab.h y.tab.h.bison In the beginning of the Makefile, YACC is defined to "bison -y", therefore the code reduces to: y.tab.c y.tab.h: sg.y sg.h $(YACC) -d sg.y y.tab.c.bison y.tab.h.bison: sg.y sg.h $(YACC) -d sg.y mv -f y.tab.c y.tab.c.bison mv -f y.tab.h y.tab.h.bison So the .bison files are recreated during build and do not have to be patched. |