Bug 192776 - www/squid33: fails installation without AUTH_KERB
Summary: www/squid33: fails installation without AUTH_KERB
Status: Closed DUPLICATE of bug 192824
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-18 08:26 UTC by Volodymyr Kostyrko
Modified: 2014-08-19 08:33 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Volodymyr Kostyrko 2014-08-18 08:26:18 UTC 
Hi all. Recent staging work on www/squid33 gives this:

# make reinstall
===>  Installing for squid33-3.3.11_3
===>   squid33-3.3.11_3 depends on file: /usr/local/bin/perl5.16.3 - found
===>   Registering installation for squid33-3.3.11_3
pkg-static: lstat(/tmp/ports/usr/ports/www/squid33/work/stage/usr/local/man/man8/negotiate_kerberos_auth.8.gz): No such file or directory
*** Error code 74

# echo `grep _SET /var/db/ports/www_squid33/options | awk -F= '{print$2}'`
CACHE_DIGESTS FOLLOW_XFF FS_AUFS HTCP IPV6 KQUEUE LARGEFILE STRICT_HTTP TP_PF VIA_DB
Comment 1 John Marino freebsd_committer freebsd_triage 2014-08-18 11:40:59 UTC 
Yes, the commit message says the port options are probably busted wrt to stage.

There are many many options and the options are a big giant mess.  It needs a real maintainer, as the commit message said.

I'm inclined to close all squid PRs that don't come with a patch until *somebody* that cares about squid decides to be the maintainer.
Comment 2 John Marino freebsd_committer freebsd_triage 2014-08-18 21:11:45 UTC 
is a patch coming or should I close the PR?
Comment 3 Pavel Timofeev 2014-08-19 03:16:15 UTC 
It seems like I know how to fix this problem. I will provide a patch in a few days.
Comment 4 John Marino freebsd_committer freebsd_triage 2014-08-19 08:33:12 UTC 
There's a good chance this is fixed by bug 192824.
Reopen if it's not when you have a patch.

*** This bug has been marked as a duplicate of bug 192824 ***