WANT_BDB_VER Ignored

I have the following in a port Makefile: USE_BDB=yes WANT_BDB_VER=48 However, when I build the port with poudriere it uses a different version of DB: ===> ppcoin-0.5.3.0 depends on shared library: libdb-5.3.so - not found ===> Installing existing package

Veeam Users

Hi, Would you be interested in Veeam Users list for your sales and marketing campaigns? Backup, Recovery & Archiving, Big Data Storage & Analytics, Business Continuity & Disaster Avoidance, Cloud Computing, Converged Infrastructure, Data Protection & Availability, Mainframe Environments,

RE: Weird portupgrade error on current amd64 [and powerpc64?]

https://lists.freebsd.org/pipermail/freebsd-ports/2016-April/102983.html reported a "Broken pipe" problem with portupgrade on 11.0-CURRENT on amd64. FYI: I had the/a "Broken pipe" portupgrade problem on powerpc64 under 11.0-CURRENT -r298518 on 2016-Apr-23 updating from /usr/ports -r413230 to

Making a port part II : bind: Who ate a byte ?

Hello, I'm porting ZoneMinder and making pull requests to avoid FreeBSD specific patches as upstream is happy to merge them. I've noticed that sock files ZM creates has 'soc' extension. This make these file haunt sock folder as they are not cleared for obvious reason after they are not

Re: [Humor] Reperatur für mutige

Sorry, wrong group Heino Tiedemann wrote: > hallo, > > Wenn der Auslöser einer EOS 50D mal nicht mehr will.. > > eine Reparaturanleitung für mutige: > man kippt einfach 95% Alkohol ins Batteriefach > https://www.youtube.com/watch?v=tB_gSqyidI0 > > > eine

[Humor] Reperatur für mutige

hallo, Wenn der Auslöser einer EOS 50D mal nicht mehr will.. eine Reparaturanleitung für mutige: man kippt einfach 95% Alkohol ins Batteriefach https://www.youtube.com/watch?v=tB_gSqyidI0 eine Reparaturanleitung für korrekte: man zerlegt man die Kamera

Re: Weird portupgrade error on current amd64

On 04/26/16 12:53, Manfred Antar wrote: > >> On Apr 26, 2016, at 9:42 AM, Michael Butler >> wrote: >> >> On 04/26/16 10:15, Manfred Antar wrote: >>> When using portupgrade on current it fails when upgrading libraries. >>> I can reproduce this on 3 different amd64

Re: Weird portupgrade error on current amd64

> On Apr 26, 2016, at 9:42 AM, Michael Butler > wrote: > > On 04/26/16 10:15, Manfred Antar wrote: >> When using portupgrade on current it fails when upgrading libraries. >> I can reproduce this on 3 different amd64 machines. >> >> Example: >> >> portupgrade -vf

Re: Weird portupgrade error on current amd64

On 04/26/16 10:15, Manfred Antar wrote: > When using portupgrade on current it fails when upgrading libraries. > I can reproduce this on 3 different amd64 machines. > > Example: > > portupgrade -vf libnice ends like this: > > ---> Build of net-im/libnice ended at: Tue, 26 Apr 2016 07:01:15

Re: www/squid: reconsider enabling all options

On Tue, Apr 26, 2016 at 1:31 AM, Pavel Timofeev wrote: > 2016-04-26 1:32 GMT+03:00 Nick Rogers : > > Hello, > > > > I just recompiled my www/squid port to the latest 3.5.17 version. Prior > to > > this I was running 3.5.14. I immediately noticed that my

Weird portupgrade error on current amd64

When using portupgrade on current it fails when upgrading libraries. I can reproduce this on 3 different amd64 machines. Example: portupgrade -vf libnice ends like this: ---> Build of net-im/libnice ended at: Tue, 26 Apr 2016 07:01:15 -0700 (consumed 00:00:10) ---> Uninstallation of

Re: www/squid: reconsider enabling all options

On 04/26/16 10:41, Franco Fichtner wrote: > Hi, > >> On 26 Apr 2016, at 10:31 AM, Pavel Timofeev wrote: >> >> 2016-04-26 1:32 GMT+03:00 Nick Rogers : >>> >>> I was able to fix my issue by recompiling without the TP_IP and TP_IPF >>> options, but I believe

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,

Re: www/squid: reconsider enabling all options

Hi, > On 26 Apr 2016, at 10:31 AM, Pavel Timofeev wrote: > > 2016-04-26 1:32 GMT+03:00 Nick Rogers : >> >> I was able to fix my issue by recompiling without the TP_IP and TP_IPF >> options, but I believe more thought/discussion should be given to all the

Re: www/squid: reconsider enabling all options

2016-04-26 1:32 GMT+03:00 Nick Rogers : > Hello, > > I just recompiled my www/squid port to the latest 3.5.17 version. Prior to > this I was running 3.5.14. I immediately noticed that my transparent proxy > setup via PF was broken and throwing a "Forwarding loop detected" error