Pierre Pronchery <khorben%defora.org@localhost> writes:
> Dear tech-pkg@, bouyer@,
>
> On 02/07/2018 21:06, Pierre Pronchery wrote:
>> adding to the discussion here: [...]
>>
>> Worse even, I just figured while updating that besides
>> print/cups-filters (included in the meta-package print/cups) it
>> seems we also need: - the "avahi" option enabled by default in cups
>> (manuel just mentioned that "for most usage mdsd support is enough"
>> though)
>
> Here is why I had to enable the "avahi" option; in cups' error_log:
>
>> E [02/Jul/2018:04:33:08 +0200] [CGI] Unable to execute ippfind
>> utility: No such file or directory E [02/Jul/2018:04:33:11 +0200]
>> [CGI] Unable to create service connection: No such file or
>> directory E [02/Jul/2018:04:33:11 +0200] [cups-deviced] PID 23861
>> (dnssd) stopped with status 1!
>
> Then I looked at the PLIST from cups-base:
>
>> ${PLIST.ippfind}bin/ippfind
>
> Which led me to the "avahi" option in options.mk:
>
>> .if !empty(PKG_OPTIONS:Mavahi) .include
>> "../../net/avahi/buildlink3.mk" CONFIGURE_ARGS+=
>> --enable-avahi PLIST.ippfind= yes PLIST.dnssd-backend=
>> yes .else CONFIGURE_ARGS+= --disable-avahi .endif
>
> Besides when building on macOS, this is the only place where ippfind
> makes it to the package.
>
> Now I do not know enough about cups' internals to determine what comes
> from where, what is really needed or not, etc. However after enabling
> the "avahi" option and re-installing cups, I was finally able to add
> my printer again, with the same procedure as usual (through the web
> interface) and obviously the error above about ippfind disappeared.
It sounds like you are saying that you can't make cups work at all
without avahi. Does the upstream documentation say it is just required
to build cups? That would seem strange, since there is an
enable/disable option.
Attachment:
signature.asc
Description: PGP signature