Can't do a portupgrade -rf on any of my mail/courier
eculp at encontacto.net
eculp at encontacto.net
Sun Nov 12 14:33:20 PST 2006
Quoting "eculp at encontacto.net" <eculp at encontacto.net>:
> Quoting Milan Obuch <freebsd-ports at dino.sk>:
>> On Sunday 12 November 2006 22:05, eculp at bafirst.com wrote:
>>> Strange problem trying to run portupgrade -rf mail/courier on both
>>> current and 6.2-PRERELEASE with all ports up to date. Only one of the
>>> machines has an older courier that I tried to update and get the error
>>> so I decided I would build a package from one of the up to date
>>> installations but much to my surprise I get the same error. One of
>>> the installations I just built within the las 15 days so it would seem
>>> that it can be built but not rebuilt which makes no sense to me. All
>>> of the courier installations are working fine. This all came to light
>>> with a portupgrade -afr on one machine. Same thing with a cd
>>> /usr/ports/mail/courier; make
>>> Any suggestions appreciated.
>> This seems to be an issue with either fam or gamin as currently present in
>> ports tree. I do not understand everything in detail, one does not
>> link (just
>> as you showed), the second one builds but does not run (imapd dumps core, so
>> no usable imap server). If someone with more fam/gamin knowledge could help
>> here, it would be great. As a temporary workaround, you could comment out
>> line in Makefile telling WITH_FAM= YES (or something similar is
>> there) and be
>> just fine, loosing ENHANCED IDLE support, however. You could even
>> update this
>> way to 0.53.3, by the way. I did not try to put this update into PR yet
>> exactly due this fam/gamin issue.
> Hi, Milan,
> The strange thing is that I built a new courier on Nov. 2. I
> installed it fine without having fam but it built gamin but then I
> had problems with courier until I built and installed fam and after
> that all was well. I didn't change anything else. From what you
> are saying and from the experience that I had, I would assume that
> what you suggest is basically what I did. That just might be worth
> a try but it seems a bit weird.
Commenting out WITH_FAM= YES nor setting it to no didn't get the
desired results. It still tried to build fam and died at the same
place. Tomorrow, if I have time, I'll uninstall fam and try to
rebuild the way I did on my last installation.
> Thanks for the reply. As always your help is invaluable. You've
> really got the freebsd courier port down.
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports