Re: Pause pkg install messages

[olli hauer]

On 2018-05-24 11:21, Miroslav Lachman wrote:
> Johannes Lundberg wrote on 2018/05/24 11:03:
>> On Thu, May 24, 2018 at 9:27 AM Bob Eager  wrote:
>>
>>> On Thu, 24 May 2018 09:08:17 +0100
>>> Johannes Lundberg  wrote:
>>>
 In addition to that it would be nice (if it's not already done) to
 store this information in a log file somewhere so that one can
 revisit and see what needs to be manually configured for each
 installed package.
>>>
>>> I have this in syslog.conf:
>>>
>>>   !pkg,pkg-static
>>>   *.* /var/log/pkg.log
> 
> I think only changes are logged, not messages:
> 
> Apr 26 23:50:22 maja pkg: p5-DBI reinstalled: 1.641 -> 1.641
> Apr 26 23:50:22 maja pkg: mariadb101-client upgraded: 10.1.31 -> 10.1.32_2
> Apr 26 23:50:22 maja pkg: libnghttp2 upgraded: 1.31.0 -> 1.31.1
> 
>> Thanks for the tip. I'll use this.
>> However, someone who knows about this probably know how to manually
>> configure their system already.
>>
>> I want to make sure first timers and newbies don't miss important messages
>> on how to configure the system.
>>
>> Often we get inquires about stuff that is clearly described in the pkg
>> message and bug reports that are a consequence of wrong configuration.
>> How can we make this more clear so that it is not missed?
> 
> As Eugene already noted - syscons has scrollback buffer. Did you tried 
> "Scroll Lock" on your keyboard?
> 
> If you need to re-show message of any installed package, "pkg info -D" (or 
> pkg info --pkg-message) is your friend. Nothing is lost. You can view it 
> anytime.
> 

For mass updating you can try the script utility, on FreeBSD there is an 
additional '-q' parameter.
 $ script -q /tmp/MyScriptLog pkg 
 $ col -xb < /tmp/MyScriptLog > /tmp/MyScriptLog.readable

On other platforms:
 $ script /tmp/MyScriptLog
 $ pkg 
 $ exit   (exits only the script util)
 $ col -xb < /tmp/MyScriptLog > /tmp/MyScriptLog.readable

Now all outputs are covered in the log (stdout and stderr)

-- 
br. olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 6100 subdirectories in /usr/ports/devel!

[olli hauer]

On 2018-02-19 17:25, Dan Mahoney (Gushi) wrote:
> On Mon, 19 Feb 2018, blubee blubeeme wrote:

...

> 
> For those of us requiring a perl module on a bunch of machines, we don't have 
> a good mechanism (outside of ports/pkg/poudriere) to build those modules and 
> get them out.  One of the things pkgng lacks is the old ports "make pkg" 
> function -- in order to build an installable package, you pretty much must be 
> running poudriere.
> 


No, with pkgng you have several ways to create a package from a port.

On a system where the port is installed:

  $ mkdir -p $space/packages//All
  $ cd $space/packages
  $ pkg create -o $space/packages/All -x p5*
# optional if you want to distribute your packages create the pkg indexes
  $ pkg repo .

Now you have a repo with all your p5* packages, change "-x p5" to "-a" and you 
have a repo with all installed package, see man pkg-create(8)


If you want to create a package directly in the directory of the port

  $ mkdir -p $space/packages/All
  $ sysrc -f /etc/make.conf PACKAGES="$space/packages"
  $ cd $PORT
  $ make package

Now you have one package in $space/packages/All and one in $PORT/work/pkg
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: unable to build java in poudriere

[olli hauer]

On 2017-01-26 19:21, Julian Elischer wrote:
> On 26/1/17 7:32 am, Ultima wrote:
>> I just finished building openjdk8 with a fresh repo and it built just fine.
>>
>> poudriere bulk -p git -j 103amd64 java/openjdk8
>> ref: 
>> https://poudriere.ultimasbox.com/build.html?mastername=103amd64-git&build=2017-01-25_14h51m15s
> 
> yeah but not so for me..  remember openjdk8 compiles just fine for me too. 
> but only after openjdb7 is available.
> did yours compile jdk7?
>>
>>
>>
>> A google search on the error suggests that it is most likely related to some 
>> form of memory issue.
>>
>> If you follow this post from a few years ago, it could lead you to the same 
>> conclusion. More or less it seemed to be a problem with java determining 
>> incorrect memory values which was causing that error. Could be completely 
>> wrong but it is worth looking into.
>>
>> https://lists.freebsd.org/pipermail/freebsd-java/2013-December/010441.html
>>
>> Explicit setting maximum memory starts the vm, but being that this is a port 
>> building, I'm not really sure what to suggest. I guess you could try add an 
>> arg on the Makefile setting max memory, but I'm not sure how much memory it 
>> requires to build. I know building openjdk does need quite a bit. Another 
>> solution, likely less desired is using another system to build it or using 
>> the FreeBSD repo to download it. Sorry if this isn't helpful. Someone else 
>> may have a better solution.
>>
>> Good luck,
>> Ultima
>>
>> On Wed, Jan 25, 2017 at 5:48 AM, Julian Elischer > > wrote:
>>
>> On 25/1/17 6:30 pm, Julian Elischer wrote:
>>
>> On 25/1/17 10:36 am, Ultima wrote:
>>
>> Sorry Julian but your details are kind of vague. Are you
>> on head? I'm not sure when my last build for openjdk7 or
>> 8 were but I have them built in my repo. Is there enough
>> memory on the system building it? or is it limited? that
>> is usually the culprit for the openjdk ports.
>>
>> I ask if you were on head because I know java was broken
>> for sometime in January but was fixed, or at least
>> r312388 is working.
>>
>> Sorry, one item missing..  compile is on FreeBSD 10.3
>>
>> Poudriere is populated with the head ports tree as of
>> yesterday, but I had hte same problem a few weeks ago.
>> the list of packages includes openjdk8
>> it would probably have the same issue if openjdk8 was the
>> ONLY port to make, because jdk8 wants jdk7 to jdb7 won't build.
>> Should poudriere or ports give a warning "you need to
>> install package X before we can do this compile"?
>>
>>
>> I will add that bootstrap-openjdk-r351880_1.txz  is already
>> finished and available.
>> I'm guessing that openjdk7 should be using that, but isn't for
>> some reason.
>>
>> in fact is it possible that 8 should be using that to bootstrap
>> itself up as well instead of using 7?
>>
>> I'm not experienced with java, I just need to get it into the
>> machine image at $JOB for others to use.
>>
>>
>>
>>
>>
>>
>> On Tue, Jan 24, 2017 at 8:56 PM, Julian Elischer
>> mailto:jul...@freebsd.org>
>> >>
>> wrote:
>>
>> from he log file:  (see below)
>>
>> This dies almost immediately.
>> Do we need to prime the build with an older java?
>> (e.g. the
>> bootstrap pkg)?
>> If so why does  poudriere not do this?
>> I actually want jdk8 but iti insists on building 7
>> first, which
>> fails.
>> Since I don't care about 7 I can prime the pump by
>> downloading a
>> 7 pkg but should all this be automatic somehow?
>>
>> Log:
>>
>> 
>> 
>>
>> 
>> 
>>
>> # Entering langtools for target(s) all   #
>> 
>> 
>>
>>
>> (cd  ./langtools/make && \
>>   gmake
>>
>> JDK_TOPDIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/jdk
>> 
>> JDK_MAKE_SHARED_DIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/jdk/make/common/shared
>> EXTERNALSANITYCONTROL=true SOURCE_LANGUAGE_VERSION=7
>> TARGET_CLASS_VERSION=7 MILESTONE=fcs BUILD_NUMBER=b01
>> JDK_BUILD_NUMBER=b01 FULL_VERSION=1.7.0_111-b01
>> PREVIOUS_JDK_VERSION=1.6. JDK_VERSION=1.7.0_111
>> JDK_MKTG_VERSION=7 JDK_MAJOR_VERSION=1
>> JDK_MINOR_VERSION=7
>>

Re: portsnap temporary files

[olli hauer]

On 2017-01-06 20:51, Dave Horsfall wrote:
> Is there some reason why portsnap cannot clean up /var/db/portsnap/files?  
> I've just had to remove a zillion of them, a bunch at a time because "rm" 
> choked on the arg list.
> 
> Perhaps a "portsnap clean" command?  I'm surprised that there isn't one.
> 

Why?

As soon you run "portsnap fetch" old files in this directory are purged!
If you look into /var/db/portsnap/INDEX you can see the mapping of the files

I'm running portsnap on one system since portsnap was introduced and never had 
issues with cleanups.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: private ports and pkgs versioning

[olli hauer]

On 2016-10-18 14:54, Mark Linimon wrote:
> On Tue, Oct 18, 2016 at 08:49:06AM +0100, Matthew Seaman wrote:
>> Yes, there is a lot of useful stuff in the ports tree to support local
>> ports or even whole local categories of ports.  I can't recall now how I
>> learned about all this stuff -- it may well have been just be a
>> combination of reading Makefiles and hints dropped on mailing lists.  I
>> cannot recall a document describing this stuff anywhere.
> 
> I don't believe that there is one.
> 
> I'm sure there are N locally-grown solutions out in the wild.
> 
> We ought to work together to poll people on what they use.
> 
> As for adding the category, I think there's a quick fix, if you don't
> care about building INDEX.  Add USE_LOCAL_MK=yes to your Makefile
> invocations, and use the patch below.
> 
> Note: I haven't tried this yet, so adding the category to ports/Makefile
> may also be necessary to pacify ports/Mk/bsd.port.subdir.mk (e.g. INDEX.)
> 
> Index: ports/Mk/bsd.local.mk
> ===
> --- ports/Mk/bsd.local.mk (revision 423944)
> +++ ports/Mk/bsd.local.mk (working copy)
> @@ -14,6 +14,8 @@
>  # time should live.
>  #
>  
> +VALID_CATEGORIES+= local
> +
>  .endif # !defined(_POSTMKINCLUDED) && !defined(Local_Pre_Include)
>  
>  .if defined(_POSTMKINCLUDED) && !defined(Local_Post_Include)
> 
> mcl

It's easier for the user to define VALID_CATEGORIES+= in /etc/make.conf, this 
way the own category is not lost in case someone wipes /usr/ports or uses 
portsnap.
For poudriere this should be defined also in $localbase/poudriere/make.conf, 
I'm using this myself for since a long time.

>From my memory (don't nail me down):
I think synth is able to use packages from pkg.FreeBSD.org and can build only 
packages with changed OPTIONS, but to be sure better ask marino@

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: harder and harder to avoid pkg

[olli hauer]

On 2016-10-11 20:59, Julian Elischer wrote:
> As the number of dependencies between packages get ever higher, it becomes 
> more and more difficult to compile packages and the dependence on binary 
> precompiled packages is increased. However binary packages are unsuitable for 
> some situations.  We really need to follow the lead of some of the Linux 
> groups and have -runtime and -devel versions of packages,  OR  we what 
> woudlbe smarter, woudl be to have several "sub manifests" to allow unpacking 
> in different environments.
> 
> 
> A simple example:   libxml2
> 
> This package installs include files and libraries and dicumentation etc.
> 
> yet if I build an appliance , I want it to only install a singe file.
> 
> /usr/local/lib/libxml2.so.2
> 
> 
> The presence of this file will satisfy any runtime dependencies of packages 
> that require it.
> 
> Unfortunately there is no way to install just this file, and still report 
> that we have the package loaded, so
> 
> pkg will always try to reinstall it leading to a huge mess.
> 
> My current scheme is to unpack all packages into a larger staging area, and 
> *manually* (scripted) copy out only the files I need, and then copy the pkg 
> database, so that when run on the running appliance, pkg THINKS all the 
> packages are loaded on the appliance, even though only the runtime files are 
> installed. This is what we in the industry call "a hack"  :-) It is also not 
> robust in the face of changing pkg versions.
> 
> It would be a lot better it pkg knew it was being asked to install only the 
> runtime set, and coudl accurately  store this information in its database, 
> allowing it to satisfy the needs of other packages that need that dependnency 
> only in a runtime manner.
> 
> Is any of this possible at the moment?
> 
> suggestions from the ports/pkg community are appreciated..
> 
> Julian
> 

Hm, do you build your own packages or using pre build packages?

just for interest and testing the following hack will do what you want, but 
results in duplicate category and some other minor errors (needs some better 
hacking ...)

$ cat libxml2/Makefile.local
post-stage:
@${RM} -rf ${STAGEDIR}${PREFIX}/include/libxml2
@${ECHO} 'lib/libxml2.so.2' > ${TMPPLIST}


A better method would be to use a tool like portsharker together with 
ports-mgmt/poudriere(-devel)
A really short hint how to use it can be found here:
 https://github.com/freebsd/poudriere/blob/release-3.1/doc/portshaker.wiki

Anyway, until now should be possible with some effort, perhaps it is possible 
to get for such purpose an additional make target that is running after stage 
but before the package is created.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [maintainer change] net-mgmt/cnagios

[olli hauer]

On 2016-09-17 19:40, Alexander wrote:
> Hi, I want to transfer net-mgmt/cnagios maintainership to dannywarren 
> (da...@dannywarren.com). He has already gave an approve, see comments here at 
> 212102 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212102) 
> 


done;

Thanks for maintaining cnagios during the last years!

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checking port option descriptions

[olli hauer]

On 2016-09-17 10:47, Mike Clarke wrote:
> On Friday 16 Sep 2016 20:09:06 Kevin Oberman wrote:
> 
>> Even when the meaning is clear in  global sense, what are the implications
>> for an application. E.g. "RTC=on: Add support for kernel real time clock"
>> in mplayer. I know exactly what the RTC is, but I have no idea why I might
>> or might not want it in mplayer.
> 
> For cases where one line comments won't suffice how about providing the 
> facility 
> to include an extra text file in a port (perhaps "pkg-options") containing 
> notes about why some particular options would be chosen?
> 
> In its simplest form a user would be able to refer to the file before 
> selecting 
> an option, A further enhancement could be to modify the way that configure 
> works so that the user can select an option and press "?" to see the section 
> of text, if any, from pkg-options explaining that option.
> 

This is already possible with the pkg-help file, but until now only 17 ports 
using this to provide additional information

I agree with the request from Warren, but looking over optcheck-output.txt we 
will find many false positives.

Sometimes the port defines a descriptive OPTION where it is hard to find a 
better description, also many ports using Mk/bsd.options.desc.mk, so the same 
description should match for example to a server or a client port (e.g. 
KERBEROS)

I suspect the list will contain less the 100 issues if reviewed in context of 
the port and the port category

Some samples from the list for "** just adding "enable support" is not a 
description"

audio/decibel-audio-player/Makefile
  AUDIOCD = AudioCD support

deskutils/py-bugwarrior/Makefile
  BUGZILLA = Enable Bugzilla support
  PHABRICATOR = Enable Phabricator support

dns/gdnsd/Makefile
  GEOIP = Enable GeoIP Support

games/imaze/Makefile
  JOYSTICK = Joystick support

graphics/devil/Makefile
  JPEG = Enable JPEG support  (one example for most every graphic format)
...



-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: n00b problem installing postfix package

[olli hauer]

On 2016-09-14 19:11, Bryan C. Everly wrote:
> Hi,
> 
> I'm trying to set up a new 10.3 server that includes postfix and
> majordomo for a BUG I'm trying to get off the ground.  I'm normally an
> OpenBSD guy but I thought I'd give it a try on FreeBSD.
> 
> Anyhow, I'm wanting to follow this guide:
> 
> http://www.area536.com/projects/complete-freebsd-mail-server/postfix-youve-got-incoming/
> 
> And I'm failing right out of the gate because I can't find postfix when I do:
> 
> # pkg install postfix
> 
> It says there isn't a package with that name.  When I check
> freshports, I see that there indeed is:
> 
> https://www.freshports.org/mail/postfix/
> 
> Is there something I have to do to get things pointed at the "right"
> package source like I do in OpenBSD (PKG_PATH)?  I was able to install
> apache and some other stuff just fine the way I currently have things
> configured FWIW.
> 
> Sorry in advance if this is a dumb question but I really could use the help.
> 
> Thanks,
> Bryan

Hi Bryan,

there was an issue with the port on the quarterly branch, and quarterly is also 
the default for pkg (see pkg -vv)

Looking at pkg.freebsd.org it seems postfix is missing but postfix211 and 
postfix-current are available.
Even the port is already fixed in quarterly, the build is already finished or 
running at the moment, so the port will be missing until the next run.

It should be no problem to install now postfix-current, and in a few days after 
the next build was running swap to postfix (simply run a pkg delete 
postfix-current and pkg install postfix, I'm doing this often to test new 
current versions)

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: noip-2.1.9_3

[olli hauer]

On 2016-08-31 17:30, Stanislaw Halik wrote:
> On 2016-08-31 Wed 17:21, olli hauer wrote:
>> I think this will work for you.
>>
>> The update interval can be adjusted (default is 30 days).
>> In the patch example I've chosen half of the interval, so there is time left 
>> in case you are offline for an unforeseen reason
>>
>> Index: Makefile
>> ===
>> --- Makefile(revision 421168)
>> +++ Makefile(working copy)
>> @@ -25,6 +25,12 @@
>>
>>  OPTIONS_DEFINE=DOCS
>>
>> +FORCE_INTERVAL=14  # days until IP update is forced
>> +
>> +post-patch:
>> +   ${REINPLACE_CMD} -e '/define 
>> FORCE_INTERVAL/s/30/${FORCE_INTERVAL}/g' \
>> +   ${WRKSRC}/noip2.c
>> +
>>  do-install:
>> ${INSTALL_PROGRAM} ${WRKSRC}/noip2 ${STAGEDIR}${PREFIX}/bin
>> ${MKDIR} ${STAGEDIR}${DOCSDIR}
> 
> Hey,
> 
> Please send this as a PR.
> 
> I'd personally choose a value of 7 days but this is okay.
> 
> sh

I don't use the tool myself (having a static assigned network) and I'm even not 
sure if it will work.

So I suggest James can test it (suspecting there is a ways to see the last 
update time on the noip portal) and if it works for him he can submit the patch 
as PR

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: noip-2.1.9_3

[olli hauer]

On 2016-08-31 13:17, James A. McGuire wrote:
> Hi there,
> 
> Since no-ip introduced their policy to remove non-updated subdomains every
> 30 days.  I have to manually go to the no-ip website and confirm that I
> wish to keep my subdomain.  I believe the reason for this is that my ISP is
> only updating my dynamic IP address every 60-90 days, and I believe that
> the no-ip client is therefore not sending updates to no-ip.
> 
> Is this the case and if so, can this behaviour be modified so that the
> client will issue an update to the no-ip servers within 30 days even if the
> IP has not changed?
> 
> Many thanks,
> 
> James

I think this will work for you.

The update interval can be adjusted (default is 30 days).
In the patch example I've chosen half of the interval, so there is time left in 
case you are offline for an unforeseen reason

Index: Makefile
===
--- Makefile(revision 421168)
+++ Makefile(working copy)
@@ -25,6 +25,12 @@

 OPTIONS_DEFINE=DOCS

+FORCE_INTERVAL=14  # days until IP update is forced
+
+post-patch:
+   ${REINPLACE_CMD} -e '/define FORCE_INTERVAL/s/30/${FORCE_INTERVAL}/g' \
+   ${WRKSRC}/noip2.c
+
 do-install:
${INSTALL_PROGRAM} ${WRKSRC}/noip2 ${STAGEDIR}${PREFIX}/bin
${MKDIR} ${STAGEDIR}${DOCSDIR}

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADSUP] extracting LoadModule out of httpd.conf

[olli hauer]

On 2016-08-12 16:32, Patrick Powell wrote:
> On 08/10/16 14:07, Miroslav Lachman wrote:
>> Mathieu Arnold wrote on 08/10/2016 17:42:
>>> Hi,
>>>
>>> It is coming.
>>>
>>> https://reviews.freebsd.org/D7460
>>>
>>> constructive comments welcome.
>>>
...
> 
> I plead with the people making this change to update apachectl to list the 
> modules that are loaded:
> 
>># apachectl modules
>  
>  mod_perl 

It is already there, use the same parameter as for httpd direct `apachectl -M'


> And when you update mod_perl and the U&*(()*&U httpd.conf file gets mangled 
> and the mod_perl line is removed or
> commented out,   you now stand a fighting chance of finding this. With the 
> change to itty-bitty files this would
> be even more useful.
> 
> Just out of curiosity,  how are you going to now deal with temporarily 
> commenting out LoadModule entries?
> 

Since more then one year mod_perl2 installs a .sample file and no longer 
changes httpd.conf
https://svnweb.freebsd.org/ports/head/www/mod_perl2/pkg-plist?r1=35&r2=389628

But I have to admit this is not the case for all modules in the ports tree

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADSUP] change in default openssl coming

[olli hauer]

On 2016-07-08 08:26, Mathieu Arnold wrote:
> Hi,
> 
> During this summer (sometime in August I think) I will be changing the
> default OpenSSL for the ports tree from the base system version to
> security/openssl.
> 
> I will also, because it goes with it, change the default GSSAPI from base
> to something else, I think the consensus was to use the MIT version, which
> is security/krb5.
> 
> Before I do that, it would be nice if people who actually use Kerberos (so,
> that's the two of you at the back) could provide some feedback if it
> changing this will break things.
> 

Looking at the next release of openssl (1.1.x) and the deprecation of 
SSL2/SSL3/MD2 I want to throw in the following question.
Are there any plans to adjust the default OPTIONS for security/openssl before / 
during the phase it will become the default for ports?

It would be a good time to adjust the OPTIONS because the next release don't 
support them any longer

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainer for dovecot

[olli hauer]

On 2016-04-29 16:32, aki.tu...@dovecot.fi wrote:
> Hi!
> 
> Do you happen to know who is responsible for Dovecot package in FreeBSD? We 
> would like to keep in touch occasionally and see if we can do co-operation 
> with the packages.
> 
> Aki Tuomi
> Dovecot Oy

Hi Aki,

see the list of maintainers (port@ means no active maintainer at the moment)

# dovecot 1.x
mail/dovecot-antispam   d...@wizard.volgograd.ru
mail/dovecot-managesieved...@centrale-marseille.fr
mail/dovecot-sieve  y...@coolrat.org
mail/dovecotpo...@freebsd.org

# dovecot 2.x
mail/dovecot2-antispam-plugin   olg...@freebsd.org
mail/dovecot2-pigeonholel...@lerctr.org
mail/dovecot2   ad...@freebsd.org


-- 
HTH,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: compiling ports with --sysroot= and -isystem

[olli hauer]

On 2016-04-22 04:04, Julian Elischer wrote:
> How can I add entries (like the above) to a port compile?
> I want to ADD things to CFLAGS.
> If I add 'CFLAGS=...' to the build (for example, of lsof)  it actually 
> replaces all the CFLAGS already there.
> lsof (as the example) uses configure, so I would need to feed the added stuff 
> into configure. Is there a standard way to do this?
> In the environment I'm using, I'm building for a machine that is not the 
> build machine, but an appliance.
> It has a small number of differences in the include file contents, so I want 
> it to compile using a different set of includes than those in /usr/include.
> 
> On the other hand I'm building a bunch of tools that do have t orun on the 
> build machine and they need to use the regular /usr/include so I don't really 
> want to replace them..
> 
> 
> Julian
> 
> p.s. usual "please reply directly" comment applies.. I'm on this list but get 
> it in digest form..
> 

Use the '+=' notation, e.g.

# Makefile
...
CFLAGS+="--sysroot="
...


-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: UPDATING entry has no AFFECTS clause

[olli hauer]

On 2016-04-17 23:48, Dan Langille wrote:
> re revision 383476 to UPDATING 
> https://svnweb.freebsd.org/ports/head/UPDATING?r1=383474&r2=383476 
> 
> 
> This entry has no AFFECTS clause.  Should it?  I ask because I encounter this 
> issue when fixing something in FreshPorts.
> 
> ###
> 20150331:
> AUTHOR: oha...@freebsd.org
> 
>   Subversion modules are no longer activated in httpd.conf!
>   To activate the subversion apache modules a dedicated file
>   will be installed as modules.d/220_subversion.conf
> ###
> 
> Should it be devel/subversion?  www/apache*?
> 
> I'm happy to do the fix. I just want to check to see which port[s] you think 
> it should be.
> 

Hi Dan,

thanks fir the notice!

The missing AFFECTS line (www/mod_dav_svn) was added in r413546

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: apache24-2.4.20

[olli hauer]

On 2016-04-14 05:22, Ken J. wrote:
> Is it possible to update/patch Apache24 with the latest backport?
> 
> As it stands now, mod_status is completely useless without this patch.
> 
> http://svn.apache.org/viewvc?view=revision&revision=1739008
> 
> Ken

Hi Ken,

I have to investigate the patch.

However in case you build your own ports you can grep the patch from here
http://people.freebsd.org/~ohauer/diffs/patch-scoreboard-r1739008

copy it to ports/www/apache24/files/ and rebuild the port.

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Post-install messages

[olli hauer]

On 2016-04-08 20:37, Ronald F. Guilmette wrote:
> 
> I am bringing up a new 10.3-RELEASE system from scratch.
> 
> While doing so, I unfortunately rushed ahead and installed
> several packages I knew I needed using the "pkg install"
> command, but I neglected to look carefully at all of the
> helpful post-install messages for each package.  Most of
> these post-install messages appear to be merely informative,
> however some of these appear to be REALLY critical, e.g. the
> ones you get after "pkg install bash".
> 
> Is there a way for me to go back now and see again all of the
> post-install messages for all of the packages that I have
> already installed, so that I can make sure that I've done
> everything that should be done to properly install all these?
> 
> I am hoping that there is some way for me to see all these
> messages again *without* having to force re-install all of the
> relevant packages.


Try the command `pkg info -aD | less' or for a single package `pkg info -D 
$packagename'

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: fix mail address as maintainer

[olli hauer]

On 2016-03-25 11:34, Tsurutani Naoki wrote:
> please someone fix my e-mail address as maintainer of these ports:
> 
> audio/id3ed
> games/xbat
> games/xgalaga
> games/xshisen
> japanese/dvi2tty
> japanese/kon2-14dot
> japanese/kon2-16dot
> japanese/font-mikachan
> japanese/plain2
> textproc/tex2im
> 
> turut...@scphys.kyoto-u.ac.jp  -->  tsurutanina...@gmail.com
> 
> original address is obsolete in a few days.
> 

Thanks for the Note, the email address was changed to your new address.

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/postfix with Dovecot SASL

[olli hauer]

On 2016-03-23 13:22, Miroslav Lachman wrote:
> Hi,
> the older version of Postfix had options for Cyrus SASL, Dovecot SASL and 
> Dovecot 2 SASL. I made 3 local meta ports do postfix-sals2 (cyrus library) 
> postfix-dovecot and postfix-dovecot2. I know mail/postfix has SASL built in 
> on Dovecot, but I am not sure if it will work with Dovecot 1.x and Dovecot 
> 2.x (the same package installed on two different machines with different 
> versions of Dovecot) We are using Dovecot's 'deliver' to deliver messages in 
> to maildirs.
> 
> Will this new Postfix 3.1 work by default with both Dovecot versions?
> 

Sure, it will work.
The Dovecot SASL is directly implemented in postfix, the OPTION was only used 
to enable the code in postfix, set dovecot SASL as the default and install 
dovecot as dependency.
Tracking dovecot as RUN_DEPENDENCY was not required at any time (only to 
automatically install dovecot).

In case you choose Cyrus SASL, dovecot SASL will be also build in, there is no 
exclude. The only thing that changes in this case is "smtpd_sasl_type = 
dovecot" vs. "smtpd_sasl_type = cyrus", you can check this with the command 
`postconf -a'.

-- 
hth,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/postfix and mail/postfix-current need upgrading

[olli hauer]

On 2016-02-26 14:45, Carmel wrote:
> On Fri, 26 Feb 2016 14:26:56 +0100, Guido Falsi stated:
> 
>> On 02/26/16 14:16, Mark Martinec wrote:
>>> In ports we have:
>>>   mail/postfix-current 2.11.7
>>>   mail/postfix 2.8.0  
>>
>> Your information is outdated:
>>
>>> grep PORTVERSION /usr/ports/mail/postfix/Makefile  
>> PORTVERSION=2.11.7
>>
>> (you can also check http://www.freshports.org/mail/postfix/ )
>>
>> Are you upgrading your ports tree regularly?
> 
> Postfix 3.1 stable release
> Postfix 3.2 experimental release
> 
> Port:   postfix-2.11.7_1,1
> Path:   /usr/ports/mail/postfix
> Info:   Secure alternative to widely-used Sendmail
> 
> Port:   postfix-current-3.0.20151003_1,4
> Path:   /usr/ports/mail/postfix-current
> Info:   Secure alternative to widely-used Sendmail
=> since yesterday evening it is 3.0-20160204 but if you look at the DISTNAME 
you will see it is 3.0.4

> Obviously, the ports are not in sync with the current Stable and
> Experimental branches of Postfix.

No they are not and I plan the following to let users some time for the 
transition to 3.1.

- mail/postfix (2.11.7) -> mail/postfix211
- mail/postfix-current (3.0.4) -> mail/postfix
- postfix-current will be updated to 3.1.0 (released this week)


In some weeks 3.1.x will become the default postfix, and 3.0.x will be removed 
from the tree, postfix211 will stay as the last postfix 2.x releases and 
current will become again current.
There are some users using VDA patches, only available for postfix 2.8 but it 
also works on 2.11, there is no support from the VDA project for 3.x and it 
seems the VDA project is no longer alive.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/postfix and mail/postfix-current need upgrading

[olli hauer]

On 2016-02-26 14:16, Mark Martinec wrote:
> In ports we have:
>   mail/postfix-current 2.11.7
>   mail/postfix 2.8.0
> 
> The version in mail/postfix-current is just barely still supported,
> the version in mail/postfix is no longer supported upstream.
> 
> Upstream versions are labeled as:
> - Postfix 3.2 is an experimental release
> - Postfix 3.1 is a stable release
> - past stable releases (still supported): 3.0, 2.11, 2.10
> - no longer supported stable releases:
> Postfix 2.9 (Final update: October 2015)
> Postfix 2.8 (Final update: February 2015)
> 
> The current situation is most unfortunate, as some ports
> (like mail/mailman) insist in their dependency on mail/postfix,
> which has (among others) no support for internationalized
> e-mail addresses, and is no longer supported upstream.
> 
> It would be appreciated if both ports were updated.
> Preferably mail/postfix to 3.1 and mail/postfix-current to 3.2,
> or at least: mail/postfix to 2.11 and mail/postfix-current to 3.1.
> 
>   Mark

Non of the users and groups postfix installs are referenced in the mailman 
configure args, only an extra patch is applied and the MTA is set to "Postfix".

I suspect and will bet, mailman would also build and run fine with the 
following patch, and then users are free to change the postfix release without 
dependency changes.

Index: Makefile
===
--- Makefile(revision 409613)
+++ Makefile(working copy)
@@ -94,8 +94,6 @@
 .endif

 .if ${PORT_OPTIONS:MPOSTFIX}
-BUILD_DEPENDS+=postfix:${PORTSDIR}/mail/postfix
-RUN_DEPENDS+=  postfix:${PORTSDIR}/mail/postfix
 MAIL_GID?= mailman
 EXTRA_PATCHES+=${FILESDIR}/postfix-verp.diff
 .endif


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: postfix-current is marked broken w.r.t SPF support, why?

[olli hauer]

On 2016-02-08 20:13, Michael Grimm wrote:
> Hi —
> 
> I am wondering why postfix-current is still marked broken regarding SPF 
> support:
> 
> | poudriere build log file excerpt:
> | Finished build of mail/postfix-current: Ignored: is marked as broken: 
> At the moment, SPF support is unavailable for postfix-3.0-20151003
> 
> Thus, I made a custom port removing this restriction in the Makefile, and 
> that custom port compiles including SPF support:
> 
> | mail> pkg query %do postfix-custom
> | security/openssl
> | devel/icu
> | mail/dovecot2
> | mail/libspf2
> | devel/pcre
> 
> | mail> pkg info | grep libspf
> | libspf2-1.2.10_2   Sender Rewriting Scheme 2 C Implementation
> 
> | mail> ldd `which postfix`
> | /usr/local/sbin/postfix:
> | ...
> | libspf2.so.2 => /usr/local/lib/libspf2.so.2 (0x8024a8000)
> | ...
> 
> I do not have a demand in using SPF at the moment, but I am only wondering 
> whether this is a bug or feature.
> 
> Any feedback is highly appreciated,
> Michael


Hi Michael,

until now the patch will not apply clean and there is no new patch available.
If we remove the BROKEN message users getting perhaps no notification if 
current will become the new default postfix


===> Fetching all distfiles required by postfix-current-3.0.20151003_1,4 for 
building
=> SHA256 Checksum OK for postfix/postfix-3.0.3.tar.gz.
=> SHA256 Checksum OK for postfix/postfix-2.8.0-libspf2-1.2.x-0.patch.gz.
===> Patching for postfix-current-3.0.20151003_1,4
===> Applying distribution patches for postfix-current-3.0.20151003_1,4
1 out of 2 hunks failed--saving rejects to src/global/mail_params.c.rej
1 out of 7 hunks failed--saving rejects to src/smtpd/smtpd.c.rej
1 out of 3 hunks failed--saving rejects to src/smtpd/smtpd_check.c.rej
*** Error code 1


-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Cannot build www/mod_dnssd with poudriere

[olli hauer]

On 2016-01-26 20:47, Kurt Jaeger wrote:
> Hi!
> 
>> Oh, scrap should be
>> #if MODULE_MAGIC_COOKIE >= 0x41503234UL /* "AP24" */
>>
>> I've uploaded a new patch (with the same name)
> 
> Testbuilds all fine with ap24 and ap22 on 9.3. I'll commit the fix,
> if this is OK with you ?
> 

Sure, absolutely :)

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Cannot build www/mod_dnssd with poudriere

[olli hauer]

On 2016-01-26 19:27, Kurt Jaeger wrote:
> Hi!
> 
>> the module should build on apache22, but it seems upstream is
>> missing a test for the apache version and includes mod_unixd.h per
>> default
>>
>> Can you test the following patch:
>>
>> $ cd www/mod_dnssd
>> $ fetch http://people.freebsd.org/~ohauer/diffs/mod_dnssd_ap22-ap24.diff
>> $ patch < mod_dnssd_ap22-ap24.diff
> 
> On current/amd64, it fails.
> 
> ./mod_dnssd.c:27:25: error: token is not a valid binary operator in a
>   preprocessor subexpression
> #if MODULE_MAGIC_COOKIE 0x41503234UL /* "AP24" */
> ~~~ ^
> 

Oh, scrap should be
#if MODULE_MAGIC_COOKIE >= 0x41503234UL /* "AP24" */

I've uploaded a new patch (with the same name)

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Cannot build www/mod_dnssd with poudriere

[olli hauer]

On 2016-01-26 12:10, Kurt Jaeger wrote:
> Hi!
> 
>> I cannot build www/mod_dnssd with poudriere.
>> The complete build log is attached.
> 
> The list strips attachments. Can you put it up somewhere ?
> 
> I tried it on current-amd64 with apache 24, builds fine.
> 
> http://people.freebsd.org/~pi/logs/ap24-mod_dnssd-0.6_12.log
> 


Hi Wolfgang / Kurt

the module should build on apache22, but it seems upstream is missing a test 
for the apache version and includes mod_unixd.h per default

Can you test the following patch:

$ cd www/mod_dnssd
$ fetch http://people.freebsd.org/~ohauer/diffs/mod_dnssd_ap22-ap24.diff
$ patch < mod_dnssd_ap22-ap24.diff


-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dns-terror (fastresolve-2.10_5) doesn't work on FreeBSD 10.x

[olli hauer]

On 2016-01-01 16:35, Miroslav Lachman wrote:
> Miroslav Lachman wrote on 10/18/2015 15:45:
>> Hi,
>>
>> I am using dns-terror to resolve IP addresses in Apache logs for many
>> years on FreeBSD but it doesn't work on newly upgraded machines. It
>> works fine on 8.4 but core dump on 10.1 and 10.2 amd64.
>> Tested on 5 machines. Port is compiled on 10.1 or 10.2.
>>
...
>>
>> It fails even on simple file like this:
>>
>> # cat /tmp/test.log
>> 1.2.3.4
>>
>> Are somebody using dns-terror on FreeBSD 10.x? What can I do to debug
>> and solve this problem?
>>
>> Miroslav Lachman
> 
> I am still not able to solve this problem. Dns-terror is failing on all our 
> machines with FreeBSD 10.2.
> 
> 1) Is somebody using it on 10.2 without problems?
> 
> 2) How can I build it with some kind of debugging? (I am not C programmer, I 
> don't know this stuff)
> 
> Miroslav Lachman
> 

Hm, fastresolve depends on dns/adns, what happens if you run the following 
command? (to test if it not an issue with libadns)
 $ /usr/local/bin/adnslogres $logfile

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Unable to make install for p5 ports

[olli hauer]

On 2015-12-20 21:26, Stefan Bethke wrote:
> 
>> Am 20.12.2015 um 21:15 schrieb Stefan Bethke :
>>
>> For many perl ports, I’m getting errors similar to this:
>>
>> ...
>> Installing 
>> /usr/obj/ports/freebsd/checkout/ports/net/p5-Net-Server/stage/usr/local/lib/perl5/site_perl/man/man1/net-server.1
>> ...
>> Installing 
>> /usr/obj/ports/freebsd/checkout/ports/net/p5-Net-Server/stage/usr/local/bin/net-server
>> > Compressing man pages (compress-man)
>> ===>  Installing for p5-Net-Server-2.008_1
>> ===>  Checking if p5-Net-Server already installed
>> ===>   Registering installation for p5-Net-Server-2.008_1 as automatic
>> pkg-static: Unable to access file 
>> /usr/obj/ports/freebsd/checkout/ports/net/p5-Net-Server/stage/usr/local/share/man/man1/net-server.1.gz:
>>  No such file or directory
>> *** [fake-pkg] Error code 74
>>
>> Stop in /freebsd/checkout/ports/net/p5-Net-Server.
>> *** [install] Error code 1
>>
>> Stop in /freebsd/checkout/ports/net/p5-Net-Server.
>> *** [build-depends] Error code 1
>>
>> Stop in /freebsd/checkout/ports/sysutils/munin-node.
>> *** [stage] Error code 1
>>
>> Stop in /freebsd/checkout/ports/sysutils/munin-node.
>>
>>
>> I’ve tried upgrading my perl to 5.20, but I’m running into the same issue.
>>
>> FreeBSD 9-stable, perl 5.20.
> 
> After fiddling around with the stage dir, it seems that the port installs man 
> pages for command line utilities into 
> stage/usr/local/lib/perl5/site_perl/man, while pig-static expects them in 
> stage/usr/local/share/man.

Hi Stefan,

no, the man page location looks fine.
Perl man pages are installed to "/usr/local/lib/perl5/site_perl/man" and 
pkg-plist has the location defined as PERL5_MAN3.

>  Is this a local configuration issue on my box? My make.conf has this:
>
> WRKDIRPREFIX?=/usr/obj/ports
> WRKDIR?=  ${WRKDIRPREFIX}${.CURDIR:S/${PORTSDIR}//}

Try again without those two definitions, it is possible the overwrite the 
STAGEDIR variable.
I just build the port without any issues, but without defining this vars.


> DISTDIR?= /usr/obj/ports/distfiles
> DISABLE_VULNERABILITIES?= true
> PACKAGES?=/freebsd/packages

I see no issues with those three definitions

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Using pkg updating without /usr/ports

[olli hauer]

On 2015-12-19 17:54, Miroslav Lachman wrote:
> David Wolfskill wrote on 12/19/2015 14:46:
>> On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote:
...
> pkg update and pkg upgrade works fine for me too, but pkg updating not. pkg 
> updating is intended to read /usr/ports/UPDATING file and compare its content 
> to installed packages and show important messages before running `pkg 
> upgrade`.
> But UPDATING file is not automatically synchronised between build server and 
> 'client' (machine where I need to run `pkg updating`).
> 

Absolute crude hack, but maybe works for you.
Please note the port is absolute not supported and breaks many porting rules ...
Instead installing the file on the servers to /usr/ports it can be installed 
anywhere and then use `pkg updating -f $file'
It should be also the first port that is updated before all other ports


on you build host:
$ mkdir /usr/ports/misc/updating

cat > /usr/ports/misc/updating/Makefile << _EOF
PORTNAME=   updating
PORTVERSION!=   /bin/date -j "+%Y%m%d.%H%M"
CATEGORIES= misc
MASTER_SITES=   # none
DISTFILES=  # none

MAINTAINER= updat...@example.org
COMMENT=UPDATING info

LICENSE=BSD2

NO_BUILD=   yes
WRKSRC= ${WRKDIR}/UPDATING
SRC=${PORTSDIR}/UPDATING

PLIST_FILES=${PORTSDIR}/UPDATING
PLIST_DIRS= ${PORTSDIR}

do-extract:
@${DO_NADA}

do-install:
@${MKDIR} ${STAGEDIR}/${PORTSDIR}
${INSTALL_DATA} ${PORTSDIR}/UPDATING ${STAGEDIR}/${PORTSDIR}

.include 
_EOF


cat > /usr/ports/misc/updating/pkg-descr << _EOF
ports UPDATING file
_EOF


-- 
Happy hacking ;}

olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Bug 205242] editors/libreoffice (5.0.3, r403255) does not build in poudriere on 11.0-CURRENT r276659

[olli hauer]

On 2015-12-13 17:20, Matthias Apitz wrote:
> El día Friday, December 11, 2015 a las 10:46:18AM +, 
> bugzilla-nore...@freebsd.org escribió:
> 
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205242
>>
>> Bug ID: 205242
>>Summary: editors/libreoffice (5.0.3, r403255) does not build in
>> poudriere on 11.0-CURRENT r276659
>>Product: Ports & Packages
>>Version: Latest
>>   Hardware: amd64
>> OS: Any
>> Status: New
>>   Severity: Affects Only Me
>>   Priority: ---
>>  Component: Individual Port(s)
>>   Assignee: off...@freebsd.org
>>   Reporter: g...@unixarea.de
>>   Assignee: off...@freebsd.org
>>  Flags: maintainer-feedback?(off...@freebsd.org)
>>
>> The port build in poudriere stops at the end after many hours with:
>>
>> [build LNK] StaticLibrary/libvclmain.a
>> [build LNK] Executable/gengal.bin
>> [build GAL] arrows
>> Work on gallery
>> 'file:///wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-5.0.3.2/workdir/Gallery/arrows'
>> Existing themes: 0
>> Existing themes: 1
>> Failed to acquire theme
>> /wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-5.0.3.2/solenv/gbuild/Gallery.mk:72:
>> recipe for target
>> '/wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-5.0.3.2/workdir/Gallery/arrows.done'
>> failed
>> ...
> 
> There are other (older) cases visible with Google showing the same
> problem, for example:
> https://forums-web2.gentoo.org/viewtopic-t-1025000.html
> saying that the dir /Gallery/arrows/ only contains two empty files
> with the names arrows.sdv and arrows.thm. The files are not part of the
> tar file in /usr/ports/distfiles so they are perhaps generated wrong
> on the run.
> 
> What is the best way with poudriere(!) to nail this down, because
> poudriere cleans the workspace?
> 
> I will give it a try with
> 
> # poudriere bulk -j freebsd-head -p ports-20151208 -w editors/libreoffice
> 
> There is also the flag -i for poudriere, but I have never used this
> before. Is there any guiding doc how to debug failing ports in
> poudriere?
> 

There is a way to archive the complete $port/work directory in case the build 
failed.

# poudriere.conf:
# If set, failed builds will save the WRKDIR to ${POUDRIERE_DATA}/wrkdirs
SAVE_WRKDIR=yes

It should be possible to extract the archive into the port and start with the 
failed build

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Can we bring back sysutils/cronolog?

[olli hauer]

On 2015-11-29 23:24, Chris H wrote:
> On Fri, 27 Nov 2015 11:13:08 -0500 kpn...@pobox.com wrote
> 
>> I still use sysutils/cronolog but lately it's been disabled due to
>> the web site vanishing. 
>>
>> I still have the distribution files. Can we put them up somewhere on
>> FreeBSD.org to keep the port alive? I'm in the process of switching
>> over to FreeBSD 10 (.2) and need to rebuild this port (along with all
>> other ports).
>>
>> http://www.neutralgood.org/~kpn/cronolog-1.6.2.tar.gz
>> http://www.neutralgood.org/~kpn/cronolog-setugid-patch.txt
>>
>> I _could_ host the files myself, but I'm rather bandwidth limited. If
>> needed I'll need to move the files to a better URL.
>>
>> Thanks!
> There was a pr(1) started for this port back on May 01, of this
> year:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199851
> It has a workable patch. But no one appears to want to commit it.
> 
>> -- 
>> Kevin P. Neal
> 

Uh, my bad!

I haven't looked for an existing PR, but had seen the original author had an 
github account ...
Additional I placed the UID patch in PATCHDIR (it is ways smaller then many of 
our pkg-plist files)

Port was already updated some hours ago.
https://svnweb.freebsd.org/ports?view=revision&revision=402603

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Can we bring back sysutils/cronolog?

[olli hauer]

On 2015-11-27 20:53, Kurt Jaeger wrote:
> Hi!
> 
>> I still use sysutils/cronolog but lately it's been disabled due to
>> the web site vanishing. 
>>
>> I still have the distribution files. Can we put them up somewhere on
>> FreeBSD.org to keep the port alive?
> 
> Using freebsd.org to distribute 3rd-party ports distfiles is not
> possible due to policy reasons, but I can put them up @opsec.eu,
> and if you provide a fallback master site, that would be sufficient.
> 
>> I'm in the process of switching
>> over to FreeBSD 10 (.2) and need to rebuild this port (along with all
>> other ports).
>>
>> http://www.neutralgood.org/~kpn/cronolog-1.6.2.tar.gz
>> http://www.neutralgood.org/~kpn/cronolog-setugid-patch.txt
>>
>> I _could_ host the files myself, but I'm rather bandwidth limited. If
>> needed I'll need to move the files to a better URL.
> 
> There was a 1.7.0 beta at some time -- any ideas where it might be ?
> 
> See sysutils/cronolog-devel.
> 

It seems the source is available on github, but last activity was end of 2013 
and there are no releases.
https://github.com/fordmason/cronolog

Perhaps it is possible to fetch the master.zip in the port Makefile ...
https://github.com/fordmason/cronolog/archive/master.zip

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-message variable -> value replacements ?

[olli hauer]

On 2015-10-24 13:23, Kurt Jaeger wrote:
> Hi!
> 
> Is there a generic way in the ports framework to replace variables
> in a port pkg-message, e.g. ${PREFIX} ?
> 

Hi Kurt,

yes, there is.

$ mv pkg-message files/pkg-message.in

and in the $port/Makefile use SUB_FILES and SUB_LIST

SUB_FILES = pkg-message
SUB_LIST+=  PREFIX=${NewVal)

This way the var %%PREFIX%% in pkg-message will be replaced with NewVal

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Why oh why am I getting all thes extras with Postfix

[Olli Hauer]

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Migrating from perl5-5.20 to perl5.22 using custom packages?

[olli hauer]

On 2015-09-06 15:33, David Wolfskill wrote:
> On Sat, Sep 05, 2015 at 09:26:22PM +0200, olli hauer wrote:
>> ...
> 
> Well, as I pointed out in the original note, I use portmaster on my
> "development" systems (which I update daily), and poudriere/pkg on the
> "production" systems (which I update weekly).

Why not set up a second package set for the development systems?

If you change "-z home" to "-z devel" you will get a a second package set.
The nice thing it will always build in a clean environment and you can detect / 
fix build issues before you upgrade your development systems (with pkg)

E.g in your case:
# poudriere bulk -j 10amd64 -p ports -z devel -f 10amd64-home-pkglist


PS:
if you don't use perl5.20 anywhere just delete the package from 
$LOCALBASE/poudriere/data/10amd64-home/All/ and after the next run it is no 
longer offered.


-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Migrating from perl5-5.20 to perl5.22 using custom packages?

[olli hauer]

On 2015-09-05 18:29, David Wolfskill wrote:
> For my "development machines (laptop & build machine), I track stable/10
> & head daily, and update ports (also daily) under stable/10 using
> portmaster.  There's been a bit of turbulence now and then, but overall,
> the process generally works.
> 
> In particular, ports/UPDATING has fairly explicit instructions for
> performing migrations of this nature -- e.g., extrapolating a bit from
> the instructions for portmaster users in the 20150513 entry:
> 
>   portmaster -o lang/perl5.22 lang/perl5.20
>   portmaster -f -D `pkg shlib -R libperl.so.5.20|tail +2`
> 
> which worked (as shown on my laptop):
> 
> g1-252(10.2-S)[1] pkg info -o perl\*
> perl5.22-5.22.0_2  lang/perl5.22
> g1-252(10.2-S)[2] 
> 
> 
> Up to a few weeks ago, I had also been using portmaster on my
> "production" machines.  My primary incentive for migrating to using "pkg
> upgrade" on these systems was their conversion from i386 to amd64 (and
> the daunting prospect of rebuilding all of those ports -- and having
> the machines' services disabled during that period.  (I documented that
> experience in
> .)
> 
> I have since continued to use poudriere on my build machine on a
> weekly cycle, then updating FreeBSD base, then the installed packages
> on the production machines every Sunday since -- which process has
> been working rather well.
> 
> Now, however, after having updated my development machines to use
> Perl5.22, I'd like to do the same for the production machines.
> 
> The above-referenced ports/UPDATING entry merely states:
> 
>   The default Perl version has been switched to Perl 5.20.  If you are using
>   binary packages to upgrade your system, you do not have anything to do, pkg
>   upgrade will do the right thing
> 
> Fortunately, I have a test machine that is set up like the producton
> one that has the bulk of the ports/packages installed, so I tried
> an upgrade cycle on it.
> 
> The update of FreeBSD from:
> 
> FreeBSD pogo.catwhisker.org 10.2-BETA1 FreeBSD 10.2-BETA1 #417  
> r285346M/285355:1001519: Fri Jul 10 04:29:33 PDT 2015 
> r...@freebeast.catwhisker.org:/common/S2/obj/usr/src/sys/ALBERT  amd64
> 
> to
> 
> FreeBSD pogo.catwhisker.org 10.2-STABLE FreeBSD 10.2-STABLE #465  
> r287480M/287482:1002500: Sat Sep  5 04:17:26 PDT 2015 
> r...@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/ALBERT  amd64
> 
> was (quite) uneventful -- it Just Worked.
> 
> After the successful reboot, I then stopped services (that relied
> on installed ports/packages) on the machine and performed "pkg upgrade".
> 
> While it claimed success and exited with an exit status of 0, it says
> that what it did with respect to Perl was:
> 
>   perl5: 5.20.2_5 -> 5.20.2_6
> 
> which isn't quite what I had in mind.
> 
> 
> In checking the package repository, I see:
> 
> freebeast(10.2-S)[9] (cd All; ls -lT perl*)
> -rw-r--r--  5 nobody  wheel  13746168 Aug 16 04:33:03 2015 perl5-5.20.2_6.txz
> -rw-r--r--  5 nobody  wheel  13935800 Jul  4 14:53:37 2015 
> perl5.18-5.18.4_15.txz
> -rw-r--r--  1 nobody  wheel  13958800 Sep  5 05:53:23 2015 
> perl5.22-5.22.0_2.txz
> freebeast(10.2-S)[10] 
> 
> I suppose a bit of housecleaning is in order... but is the existence
> of the the perl5-5.20.2_6.txz the reason/excuse for not picking up
> perl5.22-5.22.0_2.txz?
> 
> What do I need to do to switch to perl5.22 on my production machines?
> 

You can use the 'pkg set -o ...' command, but I suspect the version change is 
not happened automatically because the default in your poudriere is not set to 
perl5.22

# pkg set -o lang/perl5.20:lang/perl5.22
(note old <--> new swapped and separated with ':' )

>From Mk/bsd.default-versions.mk:
...
PERL5_DEFAULT?= 5.20


To overwrite this in PD globally
$ cat $LOCALBASE/etc/poudriere/make.conf (or $set-make.conf, for only a 
dedicated ports set)
DEFAULT_VERSIONS+= perl5=5.22

and fire a new build, all ports depending on the default perl are reflecting 
the new 5.22 version as dependency and the perl version should change 
automatically.
>From my past experience with perl upgrades I would run 'pkg upgrade -f' else 
>not all p5-$ports are reinstalled.
And as super bonus since you are already building with PD you don't have to 
mess around with portmaster


PS:
nice writeup on your webpage, to get a even smaller package list you can run 
"ports-tools/pkg_tree" with the parameter '-t'


-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Running ''portmaster ghostscript9-9.06_10'' takes a lot of time

[olli hauer]

On 2015-08-20 09:32, Mathieu Arnold wrote:
>
>
> +--On 20 août 2015 08:24:25 +0100 Anton Shterenlikht 
> wrote:
> |> OTOH I do not want to use ghostscript !
> |
> | In my view ghost is a critically important port.
> | I will not be able to use FreeBSD productively withouth it.
> | Since I have no time or skill to contribute to
> | address the slowness problem, I'm happy to put
> | up with the extra hour.
>
> I'm not exactly sure what you're all complaining about. The port just
> works fine, it does take a few seconds for make to iterate over all
> options, but it's because the port has way too many options. It's not as
> if you're all sitting behind your desk looking at the screen waiting for it
> to finish.
>

Perhaps some small statistics for a port with 124 options (www/apache24).
With the given example commands it should be not hard to verify the results

Test was done on a 8 core (3GHz) system with fast SSD's and 24GB RAM


$ svn log -q -l 10 /usr/ports/Mk
 r393817 | netchild | 2015-08-09 21:14:13 +0200 (Sun, 09 Aug 2015) => OK
 r393878 | antoine | 2015-08-10 19:06:50 +0200 (Mon, 10 Aug 2015) => OK
 r393903 | jbeich | 2015-08-10 22:14:16 +0200 (Mon, 10 Aug 2015) => OK
 r393984 | jbeich | 2015-08-12 01:20:48 +0200 (Wed, 12 Aug 2015) => OK
 r394258 | feld | 2015-08-14 22:59:29 +0200 (Fri, 14 Aug 2015) => OK
 r394503 | mat | 2015-08-17 15:31:25 +0200 (Mon, 17 Aug 2015) => OK (log grow 
with additional ~100.000 lines, slower)
 r394508 | mat | 2015-08-17 16:20:40 +0200 (Mon, 17 Aug 2015) => OK
 r394569 | mat | 2015-08-18 12:39:07 +0200 (Tue, 18 Aug 2015) => OK
 r394572 | rakuco | 2015-08-18 12:51:01 +0200 (Tue, 18 Aug 2015) => OK
 r394573 | mat | 2015-08-18 13:00:57 +0200 (Tue, 18 Aug 2015) => BROKEN explode
 r394770 | mat | 2015-08-19 11:28:06 +0200 (Wed, 19 Aug 2015) => BROKEN explode


$ cd www/apache24
$ svn up -$testrev /usr/ports/Mk

$ script -q DEBUG.make.$rev make -dA -V PKGNAME
 *1.3G Aug 20 05:52 DEBUG.make.r394770 => manual break send after 2 min.*
 *32M Aug 20 06:24 DEBUG.make.r394573 => manual break send after 15 sec.*
 16M Aug 20 06:15 DEBUG.make.r393878 => finished after 4 sec.
 16M Aug 20 06:17 DEBUG.make.r394258 => finished after 4 sec.
 29M Aug 20 06:19 DEBUG.make.r394503 => finished after 4 sec.
 29M Aug 20 06:21 DEBUG.make.r394508 => finished after 4 sec.
 29M Aug 20 06:22 DEBUG.make.r394569 => finished after 4 sec.
 29M Aug 20 06:23 DEBUG.make.r394572 => finished after 4 sec.


$ wc -l DEBUG.make*
 569729 DEBUG.make.r394770 => not finished after 2 min, size 1.x GB
 242899 DEBUG.make.r393878
 242899 DEBUG.make.r394258
 348109 DEBUG.make.r394503
 348141 DEBUG.make.r394508
 350125 DEBUG.make.r394569
 350125 DEBUG.make.r394572
 38521 DEBUG.make.r394573 => stopped after 15 sec.
 2490548 total
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Unable to relocate to new svn URL

[olli hauer]

On 2015-08-06 05:44, Kevin Oberman wrote:
> 
...
> 
> This still leaves the issue of requiring SASL support in subversion. A note
> in the handbook section on ports would help, though I'll admit that I
> probably would not have found it in this case. Perhaps a note in
> ports/UPDATING might be in order. At least that one was fairly easy to find
> once I started looking.

Hi Kevin,

SASL support is not required to checkout/update src/ports/docs

To see a list of client features fire the command

$ svn --version
svn, version 1.8.14 (r1692801)
...
The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.8
  - handles 'http' scheme
  - handles 'https' scheme


or on FreeBSD >= 10.x

$ svnlite --version
svn, version 1.8.10 (r1615264)
...
The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.7
  - handles 'http' scheme
  - handles 'https' scheme


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: bsd.port.mk reduce error to warning for UNAME_r OSVERSION mismatch

[olli hauer]

On 2015-06-16 17:06, Julian H. Stacey wrote:
> bsd.port.mk test below is too agressive, let's have it just Warn, not Fail.
> Also prefix text "Error: " or "Warning: " make it obvious which is happening.
> 
> It seems likely people may have different opinions if it should
> just Warn or Error, so kets add an environent switch to stear that decision.
> Which way the default setting of switch should be, I won't suggest
> (in hope of enhancing chance of agreement to add the switch :-)
> Whoever adds the switch could decide ?
> 
> Background:
>   current fails to make my /usr/ports/graphics/libspiro
>   I contacted cc'd MAINTAINER= who wrote me
>   "my poudriere is running on 10"
>   I dont run poudriere, but have a native 10 partition
>   so simply did a chroot ...
> I ran:
> cd /s2; head -1 /etc/motd
>   # FreeBSD 10.1-RELEASE (LAPR.small) #0: Sat Feb 28 16:29:20 CET 2015
> cd /usr/ports/graphics/libspiro
> make clean
>   make: "/usr/ports/Mk/bsd.port.mk" line 1214: UNAME_r (11.0-CURRENT) and 
> OSVERSION (1001000) do not agree on major version number.
> make
>   make: "/usr/ports/Mk/bsd.port.mk" line 1214: UNAME_r (11.0-CURRENT) and 
> OSVERSION (1001000) do not agree on major version number.
> 
> Same forced error can be seen on current lines 1197 & 1199.
> 
> After I patched out the failing bsd.port.mk error I could continue my test 
> of the port & see the port build with 10 src & ports on an 11 kernel.
> 

Patching bsd.port.mk is not the way to go, set the following environment vars 
before starting a build inside the jail
- UNAME_r=10.1-RELEASE-p10
- UNAME_v=FreeBSD 10.1-RELEASE-p10
- OSVERSION=1001000

For example in the login.conf of the jail

default:\
:setenv=UNAME_r=10.1-RELEASE-p10,UNAME_v=FreeBSD 
10.1-RELEASE-p10,OSVERSION=1001000:\
...

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Re: Fwd: Re: svn commit: r386904 - in head/www/apache22: . files

[Olli Hauer]

   One case wher this can happen is the dh generation was interrupted
   during the build.
   The upcomming apache2.2 will no.longer require such a hack because
   mod_ssl has undergone a huge rewrite.
   --
   Sent from my Android phone with GMX Mail. Please excuse my brevity.

   Bryan Drewery  wrote:

 On 5/31/2015 8:29 AM, Adam McDougall wrote:
 > Is anyone else getting this issue? I had to revert the change on
 my systems.
 > Thanks.
 >
 Yes it looks incomplete. Nothing is providing get_dh2048.
 > work/httpd-2.2.29/modules/ssl/ssl_engine_dh.c:static DH
 *get_dh512(void)
 > work/httpd-2.2.29/modules/ssl/ssl_engine_dh.c:static DH
 *get_dh1024(void)
 > work/httpd-2.2.29/modules/ssl/ssl_engine_dh.c: dh = get_dh2048();
 > work/httpd-2.2.29/modules/ssl/ssl_engine_dh.c: dh = get_dh3072();
 > work/httpd-2.2.29/modules/ssl/ssl_engine_dh.c: dh = get_dh3072();
 The module is only providing 512 and 1024 but not 2048 and 3072
 symbols.
 --
 Regards,
 Bryan Drewery
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Apache 2.4 must become default NOW

[olli hauer]

On 2015-05-27 16:18, Patrick Powell wrote:
> On 07/13/14 17:46, Michelle Sullivan wrote:
>> Baptiste Daroussin wrote:
>>> On Mon, Jul 07, 2014 at 12:27:48AM +0200, olli hauer wrote:
>>>   
>>>> On 2014-07-05 19:09, Bjoern A. Zeeb wrote:
>>>> 
<...snip..>

>> One would have hoped that mod_perl2 would have had this removed first:
>>
>> .if ${APACHE_VERSION} > 22
>> BROKEN= Does not build with apache24
>> .endif
>>
>> Just my small (557 packages) build set:
>>
>> >> Skipped ports: devel/bugzilla44 devel/p5-Log-Dispatch
>> www/p5-Apache-DBI www/p5-HTML-Mason www/p5-HTML-Mason-PSGIHandler
>> www/p5-MasonX-Profiler www/p5-RT-Authen-ExternalAuth www/p5-libapreq2
>> www/rt40
>>
>>
>> Michelle
>>
> I believe that this has been fixed for at least since Sept 2014. There is a 
> 'test and debugging' version of mod_perl2 that appears to have the required 
> mods/changes,  but they have not been rolled into the upstream distribution.
> 
> I wonder what happened to the mod_perl updating process...
> 

At the moment the mod_perl2 port does the following.
- If apache22 is detected use the original 2.0.8 source to build mod_perl.
- if apache24 is detected a patch (50.000+ lines) will be applied to match 
upstream trunk r1638352.

Between r1638352 and the current rc1 changes for modperl_interp resulting in a 
non working apache24 with MPM event, a report for this can be read on the 
mod_perl-dev list.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Wrong security audit for mail/postfix ?

[olli hauer]

On May 11, 2015 9:38:46 AM CEST, Cristiano Deana  
wrote:
> Hi,
> 
> this morning I got for my mailservers
> 
>  # pkg audit
> postfix-2.11.4,1 is vulnerable:
> postfix -- plaintext command injection with SMTP over TLS
> CVE: CVE-2011-0411
> WWW:
> http://vuxml.FreeBSD.org/freebsd/14a6f516-502f-11e0-b448-bbfa2731f9c7.html
> 
> postfix-2.11.4,1 is vulnerable:
> Postfix -- memory corruption vulnerability
> CVE: CVE-2011-1720
> WWW:
> http://vuxml.FreeBSD.org/freebsd/3eb2c100-738b-11e0-89f4-001e90d46635.html
> 
> But this is a bug from 2011, and it's blocking new install or updates
> of postfix packages.
> 
> Who should be warned of this?
> 
> Thank you.

Hi Cristiano,

this should be fixed.meanwhile.

Please run the command 
# pkg audit -F

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Re: WITH_OPENSSL_PORT documentation

[Olli Hauer]

   Hi Mathieu,
   what is the target timeframe for."soon",.e.g. for.8.x and.9.x having an
   older openssl in base.
   Is there wip. to hide the base ssl libs ?
   --
   Sent from my Android phone with GMX Mail. Please excuse my brevity.

   Mathieu Arnold  wrote:

 +--On 8 mars 2015 13:24:09 -0600 Adam Weinberger 
 wrote:
 | Can somebody please write something---anything, even 2
 sentences---for
 | the PHB about how to use WITH_OPENSSL_PORT? What users should set
 it to
 | to get LibreSSL for example, and what porters are supposed to put
 in the
 | Makefile to support it?
 |
 | The text at the top of bsd.openssl.mk just shows
 WITH_OPENSSL_PORT=yes. A
 | few sentences would be a big help, and I'm sure the doc people
 would be
 | happy to take care of all the markup and formatting for you.
 It'll soon be a moot point, WITH_OPENSSL_PORT will be the only
 option :-)
 --
 Mathieu Arnold
 ___
 freebsd-ports@freebsd.org mailing list
 [1]http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 "freebsd-ports-unsubscr...@freebsd.org"

References

   1. http://lists.freebsd.org/mailman/listinfo/freebsd-ports
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap didn't properly update www/neon

[olli hauer]

On 2015-02-22 19:38, Daniel Morante wrote:
> I have a system that started as FreeBSD 5.x.  Throughout the years it has 
> been updated and upgraded.  Today's it's currently at 9.3-RELEASE.
> 
> Recently:
> 
> "The port www/neon29 was renamed to www/neon and updated to version 0.30.1"
> 
> Back in 2008:
> 
> "Rename www/neon to www/neon26 to make the integration of www/neon28 possible"
> 
> Not sure what happened between no and then, but yesterday portsnap failed to 
> properly update the port skeleton under /usr/ports/www/neon.  There were 
> still some left over files from the last time the port was named neon.
> 
>  :/usr/ports/www/neon # ls -larths
> total 78
>  2 drwxr-xr-x 2 root  wheel   512B Apr 28  2008 files
>  2 -rw-r--r-- 1 root  wheel   821B Jan 22  2014 pkg-descr
>  6 -rw-r--r-- 1 root  wheel 6k Dec 24 01:03 pkg-plist
>  2 -rw-r--r-- 1 root  wheel   130B Dec 24 01:03 distinfo
>  2 -rw-r--r-- 1 root  wheel   1.8k Dec 24 01:03 Makefile
> 62 drwxr-xr-x  2332 root  wheel61k Feb 22 12:32 ..
>  2 drwxr-xr-x 3 root  wheel   512B Feb 22 13:37 .
> 
>  ls -larths files/
> total 8
> 2 -rw-r--r--  1 root  wheel   503B Mar 16  2007 patch-ltmain.sh
> 2 -rw-r--r--  1 root  wheel   683B Mar 16  2007 patch-Makefile.in
> 2 drwxr-xr-x  2 root  wheel   512B Apr 28  2008 .
> 2 drwxr-xr-x  3 root  wheel   512B Feb 22 13:37 ..
> 
> Which of course would cause the port install to fail since those patches are 
> outdated:
> 
> ===>  Applying FreeBSD patches for neon-0.30.1
> 1 out of 1 hunks failed--saving rejects to ltmain.sh.rej
> => Patch patch-ltmain.sh failed to apply cleanly.
> => Patch(es) patch-Makefile.in applied cleanly.
> *** [do-patch] Error code 1
> 
> Stop in /usr/ports/www/neon.
> *** [install] Error code 1
> 
> Stop in /usr/ports/www/neon.
> 
> To fix, I delete the 'files' directory.
> 

Wow, that's really old leftovers!

The current neon port has no files directory so it can be removed.
Since portsnap is used to keep the tree current you can do the following

# rm -rf www/$all_neon_dirs
# portsnap extract www/neon


Hopefully there are no other leftovers in your portstree

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Is pkg-install the best solution?

[olli hauer]

On 2015-02-09 03:05, Chris H wrote:
> Greetings,
>  I'm working with a port that [conditionally] requires
> creating/setting a UID && GID. Following is my approach
> for a pkg-install. But would simply setting them as
> USERS=
> GROUPS=
> in Makefile be a better approach?
> pkg-install:
> #!/bin/sh
> 
> PATH=/bin:/usr/sbin
> 
> if [ -z "${WRAP_USER}" ]; then
>   WRAP_USER=myapp
> fi
> 
> case $2 in
> PRE-INSTALL)
>   UID=181
>   GID=${UID}
>   if [ ! -d "${MYAPP_DIR}" ]; then
>   mkdir -p ${MYAPP_DIR}
>   fi
>   if pw user show "${WRAP_USER}" 2>/dev/null; then
>   echo "You already have a user \"${WRAP_USER}\", so I will use 
> it."
>   if pw usermod ${WRAP_USER} -d ${MYAPP_DIR}
>   then
>   echo "Changed home directory of \"${WRAP_USER}\" to 
> \"${MYAPP_DIR}\""
>   else
>   "${MYAPP_DIR}\" failed..."
 ...

Hi Chris,

go with USERS,GROUPS in Makefile and if the user/group does not already exist 
in ports/UIDs, ports/GIDs request one together with the new port.

Using pkg-install to create users/groups is deprecated.

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: libiconv.la issues

[olli hauer]

On 2015-01-25 05:46, LuKreme wrote:
> On Jan 24, 2015, at 9:17 PM, LuKreme  wrote:
>> sed: /usr/local/lib/libiconv.la: No such file or directory
>> libtool: link: `/usr/local/lib/libiconv.la' is not a valid libtool archive
>> *** [libarchive.la] Error code 1
...
> # uname -v
> FreeBSD 9.2-RELEASE-p3 #0: Sat Jan 11 02:38:15 UTC 2014 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC 



Please follow the instructions in UPDATING entry 20140909.

BTW, FreeBSD 9.2 is EoL since 2014-12-30, see 
http://www.freebsd.org/security/security.html#sup

Perhaps a good time to upgrade from 9.2 -> 9.3

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Poudriere Timeout

[olli hauer]

On 2015-01-19 20:18, Kurt Jaeger wrote:
> Hi!
> 
 Yes, i have. I've solved this problem by moving the build-jails of
 poudriere to an memory disk. This make poudriere no longer io-bund and
 incredibly fast. And solve this issue ;)
> 
>>> How did you do this ? I want to try this myself 8-}
> 
>> I've hacked poudriere to run within a jail.
> 
> Aha, the .m mountpoint. My test host has 32 GB, so 20 GB should not be
> a problem.
> 
> Testport: www/p5-Selenium-Remote-Driver on 10.1-amd64, 9.3-amd64 and 8.4-i386.
> 
> Results:
> 
> old: 00:05:43
> new: 00:05:11
> 
> old: 00:01:56
> new: 00:00:12
> 
> old: 00:02:11
> new: 00:00:14
> 
> Nice!
> 

Hi Kurt,

are you running PD also in a jail?

If not PD can be tuned by setting MFSSIZE *or* USE_TMPFS in poudriere.conf.

On my system I have good results with 8 concurrent builds and MFSSIZE=6G or 
'USE_TMPFS=all'.
Fine tuning can be done with an additional SSD (look at `systat -iostat' during 
a build)

poudriere.conf:

# When building packages, a memory device can be used to speedup the build.
# Only one of MFSSIZE or USE_TMPFS is supported. TMPFS is generally faster
# and will expand to the needed amount of RAM. MFS is a bit slower, but is
# more mature and can have its memory usage capped.

# If set WRKDIRPREFIX will be mdmfs of the given size (mM or gG)
#MFSSIZE=4G

# Use tmpfs(5)
...
# all   - Run the entire build in memory, including builder jails.
USE_TMPFS=all

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net-mgmt/rancid and cisco ssh kexagorhitms

[olli hauer]

On 2015-01-14 15:35, Marko Cupać wrote:
> Hi,
> 
> as of FreeBSD 9.3, it is not possible to ssh into some cisco routers
> (namely 1921 and 3925 in my case), unless option -o KexAlgorithms=
> diffie-hellman-group14-sha1 is specified. Probably, as a consequence,
> rancid stopped working for these routers since I upgraded OS on which
> it is installed to 9.3.
> 
> How can I make this work again?
> 
> Thank you in advance,
> 

I had the same issue but there is a simple solution:

$ cat ~rancid/.ssh/config
host host1 host2 host3 IP1 IP2 ...
KexAlgorithms diffie-hellman-group14-sha1


-- 
HTH,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: https://svnweb.freebsd.org/ Attic URLs, eg for ports/mail/demime ?

[olli hauer]

On 2014-12-29 17:19, Julian H. Stacey wrote:
> olli hauer wrote Sat, 27 Dec 2014 08:25:09 +0100:
> 
>> On 2014-12-27 03:30, Julian H. Stacey wrote:
>>> Hi ports@
>>> What URL(s) do I need under
>>> https://svnweb.freebsd.org/ 
>>> to get to the Attic for last copy of eg ports/mail/demime ?
>>>
>>> How is one supposed to find URLs /svn rev nos ?
>>> (I have a local svn if it helps, but was looking on web)
>>>
>>> demime was removed after release date 2012-01 of 9.0.0
>>> https://svnweb.freebsd.org/ports/tags/RELEASE_9_0_0/mail/demime/ 
>>>
>>> I want to know not just URL but also How to find last URL/ svn
>>> revision numbers, as I'm trying to rescue & upgrade a few ports from 
>>> oblivion.
>>>
>>> I presume there's some better way to search than binary search 
>>> (repeated splitting & re-search in the middle between narowing dates) ?
>>
>> Hi Julian,
>>
>> with viewvc only it is not that easy, but with (svn) command line.
>>
>> $ grep demime /usr/ports/MOVED
>> mail/demime||2011-12-28|Has expired: No upstream development since 2007
>>
>> $ svn log -qv -r '{2011-12-28}':'{2011-12-29}'
>> r288196 | rene | 2011-12-28 18:49:04 +0100 (Wed, 28 Dec 2011)
>> Changed paths:
>> ...
>>M /head/mail/Makefile
>>D /head/mail/demime
>> ...
>>
>> Setting 288195 as sticky revision in viewvc we get this URL
>> https://svnweb.freebsd.org/ports/head/mail/demime/?pathrev=288195
> 
> 
> Thanks Olli,
> There's something I'm missing in my environent ?
> I have /usr/svn -> /pri/FreeBSD/development/FreeBSD-SVN
> With 
>   cd /pri/FreeBSD/development/FreeBSD-SVN/ports;ls
>   # README.txt conf db format hooks locks
>   svn log -qv -r '{2011-12-28}':'{2011-12-29}'
> I got
>   svn: E155007: '/pri/FreeBSD/development/FreeBSD-SVN/ports' is not a 
> working copy
> 
> I suggest someone append to man svn:
>   SEE ALSO https://www.freebsd.org/doc/en/books/handbook/svn.html
> non-optimal mini patches that do that are here:
>   
> http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/devel/subversion/
> 
> I experimented some more:
> 
>  cd /usrb/tmp/svn; svn checkout -q file:///usr/svn/ports
>  still running after 14 hours, so still waiting to try later.
> 
>  svn log -qv -r http://svn.freebsd.org/ports/head 
> '{2011-12-28}':'{2011-12-29}'
>  svn: E205000: Syntax error in revision argument 
> 'http://svn.freebsd.org/ports/head'
> 
>  svn log  http://svn.freebsd.org/ports/head '{2011-12-28}':'{2011-12-29}'
>  svn: E160013: File not found: revision 375791, path 
> '/head/{2011-12-28}:{2011-12-29}'
> 
>  svn log  http://svn.freebsd.org/ports '{2011-12-28}':'{2011-12-29}'
>  svn: E160013: File not found: revision 375791, path 
> '/{2011-12-28}:{2011-12-29}'
> 
> Questions:
>  - what if anything do need to check with printenv ? (aka CVSROOT etc from 
> the past)
>  - which directory (/bin/pwd) I should be in to run that command "svn log 
> ..." ?
>  - what should the contents of that directory be ? (eg what does your ls 
> show) ?
> 
> Thanks !
> 
> Cheers,
> Julian
> 

Hi Julian,

take the date as rev. parameter, see `svn help log'

Time for a working practical example, pick a FreeBSD mirror from 
https://www.freebsd.org/doc/en/books/handbook/svn.html.
We will run the command in a fresh empty dir (not part of any existing svn 
workspace)

$ mkdir /tmp/svnlogfoo && cd /tmp/svnlogfoo
$ svn log -qv -r '{2011-12-28}':'{2011-12-29}' http://svn0.eu.freebsd.org/ports
 (log data we need to find the removed port)


I always start with sparse checkouts and use then `svn update' with the 
"--set-depth" parameter
For this example we re-use the empty /tmp/svnlogfoo directory
Lets see if we are able to checkout old data (e.g CVSROOT).

$ svn co --depth empty https://svn0.eu.freebsd.org/ports/head /tmp/svnlogfoo/
$ cd /tmp/svnlogfoo
$ svn info
Path: .
Working Copy Root Path: /tmp/svnlogfoo
URL: https://svn0.eu.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn0.eu.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 375797
...

$ svn ls -r 10
CVSROOT/
Makefile
Mk/
editors/
shells/

$ $ svn up -r 10 CVSROOT
$ ls -1 CVSROOT/
commit_prep.pl
commitcheck
commitinfo
cvs_acls.pl
editinfo
log_accum.pl
loginfo
rcsinfo
rcstemplate


Lets see if we can check out mail/demime (r288195)

$ svn up --set-depth empty mail
Updating 'mail'

Re: https://svnweb.freebsd.org/ Attic URLs, eg for ports/mail/demime ?

[olli hauer]

On 2014-12-27 03:30, Julian H. Stacey wrote:
> Hi ports@
> What URL(s) do I need under
> https://svnweb.freebsd.org/ 
> to get to the Attic for last copy of eg ports/mail/demime ?
> 
> How is one supposed to find URLs /svn rev nos ?
> (I have a local svn if it helps, but was looking on web)
> 
> demime was removed after release date 2012-01 of 9.0.0
> https://svnweb.freebsd.org/ports/tags/RELEASE_9_0_0/mail/demime/ 
> 
> I want to know not just URL but also How to find last URL/ svn
> revision numbers, as I'm trying to rescue & upgrade a few ports from oblivion.
> 
> I presume there's some better way to search than binary search 
> (repeated splitting & re-search in the middle between narowing dates) ?

Hi Julian,

with viewvc only it is not that easy, but with (svn) command line.

$ grep demime /usr/ports/MOVED
mail/demime||2011-12-28|Has expired: No upstream development since 2007

$ svn log -qv -r '{2011-12-28}':'{2011-12-29}'
r288196 | rene | 2011-12-28 18:49:04 +0100 (Wed, 28 Dec 2011)
Changed paths:
...
   M /head/mail/Makefile
   D /head/mail/demime
...

Setting 288195 as sticky revision in viewvc we get this URL
https://svnweb.freebsd.org/ports/head/mail/demime/?pathrev=288195

-- 
HTH,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ports changing permissions on directories

[olli hauer]

On 2014-12-08 20:37, Andrea Venturoli wrote:
> Hello.
> 
> There are some ports that insist on changing permissions on some directories.
> An example is clamav, which will always change /var/db/clamav mask to 755.
> 
> Since I always need to "chmod 775 /var/db/clamav" after an upgrade, I'm 
> asking:
> _ where does this come from? I tried to look into Makefile, but didn't get to 
> it;
> _ is this something FreeBSD specific or coming from upstream?
> _ what's the rationale behind this?
> _ can this be avoided or tweaked?
> 
> 
>  bye & Thanks
> av.
> 
> P.S. Another example would be squid.

Hi Andrea,

the mode is defined in pk-plist.

$ grep @dir /usr/ports/security/clamav/pkg-plist
@dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%DBDIR%%
@dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%LOGDIR%%
@dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%RUNDIR%%


In squid there is no hint for pkg about owner, group and mode
therefor the directories are always set to root:wheel 0755

$ grep @dir /usr/ports/www/squid/pkg-plist
@dir /var/log/squid
@dir /var/run/squid
@dir /var/squid/cache
@dir /var/squid/logs
@dir /var/squid


I think this should be changed to something like this
@dir(squid,wheel,0750) /var/log/squid
@dir(squid,wheel,0755) /var/run/squid
@dir(squid,squid,0750) /var/squid/cache
@dir(squid,wheel,0750) /var/squid/logs
@dir(squid,wheel,0750) /var/squid  <== not sure, no squid system to compare at 
the moment



-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg: /var/cache/pkg and pkg upgrade, how does this work ?

[olli hauer]

On 2014-11-30 15:39, Kurt Jaeger wrote:
> Hi!
> 
> I have a host with a up2date /var/cache/pkg/ and a jail with a
> not so up2date pkg collection.
> 
> Now I want to mount /var/cache/pkg into the jail at the same
> location and hope that I do not have to re-fetch all the files.
> 
> Testing this, the problem is: The packages installed in the jail
> are deemed up2date by pkg and they are *not* updated at all ?
> 
> How can I update a jail with the pkg cache from 'above' and avoid
> fetching packages all over again ?
> 

Hi Kurt,

In case your repo is defined this way on your host

Repositories:
  $reponame: {
...

copy also the $reponame.meta and repo-$reponame.sqlite from /var/db/pkg to the 
jail.
Additional set "REPO_AUTOUPDATE = false" in the pkg.conf from the jail.

Now the jail has all references for the packages and the update should work.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: postfix catch-22...

[olli hauer]

On 2014-11-10 11:01, Matthew Seaman wrote:
> 
> Dear maintainer,
> 
> Had an issue with updating from 2.11.1_4,1 to 2.11.3_1,1:  it looks like
> you can't win with the ownership of /var/spool/postfix:
> 
> On restart after updating the package:
> 
> {{{
> smtp-2:/var/spool/postfix:# service postfix restart
> postfix/postfix-script: stopping the Postfix mail system
> postsuper: fatal: scan_dir_push: open directory defer: Permission denied
> postfix/postfix-script: fatal: Postfix integrity check failed!
> }}}
> 
> Googling shows this to be a problem with the ownership of
> /var/spool/postfix.  One 'chown postfix /var/spool/postfix' later, and
> postfix will now at least start, but it clearly isn't happy about it.
> 
> {{{
> smtp-2:/var/spool/postfix:# chown postfix .
> smtp-2:/var/spool/postfix:# service postfix restart
> postfix/postfix-script: fatal: the Postfix mail system is not running
> postfix/postfix-script: warning: not owned by root: /var/spool/postfix
> postfix/postfix-script: starting the Postfix mail system
> }}}
> 
> {{{
> smtp-2:/var/spool/postfix:# postfix check
> postfix/postfix-script: warning: not owned by root: /var/spool/postfix
> smtp-2:/var/spool/postfix:# ls -ld /var/spool/postfix
> drwx--  16 postfix  postfix  16 Nov 10 00:27 /var/spool/postfix/
> }}}
> 
> It seems from the pkg-plist that postfix:postfix and 0700 are the
> intended ownership and permissions:
> 
> https://svnweb.freebsd.org/ports/head/mail/postfix/pkg-plist?r1=372370&r2=372369&pathrev=372370
> 
> However updating via pkg(8) didn't seem to pick up the ownership change
> on /var/spool/postfix -- it got the chmod to 0700 though.
> 
> pkg(8) not behaving quite right aside, I'm not convinced that
> postfix:postfix and 0700 is correct for /var/spool/postfix -- it used to
> be root:postfix and move 0755, which seems to allow postfix to run
> without complaint:
> 
> {{{
> smtp-2:/var/spool/postfix:# chmod 755 .
> smtp-2:/var/spool/postfix:# chown root .
> smtp-2:/var/spool/postfix:# postfix check
> smtp-2:/var/spool/postfix:# service postfix restart
> postfix/postfix-script: stopping the Postfix mail system
> postfix/postfix-script: starting the Postfix mail system
> }}}
> 
>   Cheers,
> 
>   Matthew


Arg, an leftover from my tests to fix the permissions ...

This should by fixed in svn rev. 372388, thanks for the note!

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: SSP now default for ports/packages, ssp/new_xorg repository EOL

[olli hauer]

On 2014-11-02 21:01, Bryan Drewery wrote:
> Ports and Package users,
> 
> Ports now have SSP enabled by default. The package repository will now build 
> SSP by default as well. SSP is "Stack Smashing Protection" and can be read 
> about at https://en.wikipedia.org/wiki/Buffer_overflow_protection.
> 
> This only applies to the head (/latest) packages, not the Quarterly branch 
> packages. This applies to the ports checkout that portsnap uses.
> 
> WITHOUT_SSP can be defined in make.conf to not use this feature.
> 
> SSP will be used to build ports (with -fstack-protector) on all amd64 
> releases and i386 releases which are 10.0 or newer.
> 
> The "ssp" repository and "new_xorg" repositories will no longer be updated 
> after 11/15 as they are no longer needed as both are default for ports now. 
> Please update your repository configurations to now only track the /latest 
> repository. This is the default from /etc/pkg/FreeBSD.conf. Remove any 
> overrides from /usr/local/etc/pkg/repos/ for the "ssp" or "new_xorg" 
> repositories.
> 
> Regards,
> Bryan Drewery on behalf of portmgr


Hi Bryan,

thats good notes, but how about users tracking ssp and changing the repo or 
upgrading to 10.1 if released?
I suspect packages will be replaced during 10.1 upgrade with NON_SSP packages 
since the tree was tagged already yesterday by babt.

--
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Re: postgresql-server depends on client. Why?

[Olli Hauer]

   In case the dependency on thr client will be removed all ports
   depending on the server alone at the moment should be checked if they
   also require the client part.
   Additional clients should not define a conflict with server versions <
   client version
   --
   Sent from my Android phone with GMX Mail. Please excuse my brevity.

   Chris Rees  wrote:

 Hi Dan,
 [1]http://svnweb.freebsd.org/ports/head/databases/postgresql90-serve
 r/Makefile?revision=286930&view=markup#l64
 It was always supposed to be the case, however I agree that it's
 probably not necessary.
 Anyone mind if it doesn't depend?
 Chris
 On 17 October 2014 15:12:51 BST, Dan Langille 
 wrote:
 >Why is postgresql-server dependent upon postgresql-client?
 >
 >This wasn't the case in the past and seems to be the case not.
 >
 >Not all server installations need the client.
 >
 >In addition, upgrading the client before upgrading the server is
 >standard procedure:
 >
 >[2] http://www.postgresql.org/docs/9.3/static/upgrading.html
 >
 >i.e. upgrade the client, pg_dump using the new client, then upgrade
 >server, pg_restore.
 >
 >Thanks
 >
 >--
 >Dan Langille
 --
 Sent from my Android device with K-9 Mail. Please excuse my brevity.
 --
 This message has been scanned for viruses and
 dangerous content by MailScanner, and is
 believed to be clean.
 ___
 freebsd-ports@freebsd.org mailing list
 [3]http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 "freebsd-ports-unsubscr...@freebsd.org"

References

   1. 
http://svnweb.freebsd.org/ports/head/databases/postgresql90-server/Makefile?revision=286930&view=markup#l64
   2. http://www.postgresql.org/docs/9.3/static/upgrading.html
   3. http://lists.freebsd.org/mailman/listinfo/freebsd-ports
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: PKG not quite ready for prime time

[olli hauer]

On 2014-10-10 19:43, scratch65...@att.net wrote:
> 
> On Fri, 10 Oct 2014 19:30:18 +0200, you wrote:
> 
>> On 2014-10-10 19:13, scratch65...@att.net wrote:
>>> I'm having quite a lot of trouble converting to pkg due to there
>>> being no obvious source of accurate documentation.   I got this
>>> after I thought I had it solved and could install something:
>>>
>>> 11:36 Fri, 10 Oct [momcat:root]~> pkg install firefox
>>> Updating FreeBSD repository catalogue...
>>> pkg: Repository FreeBSD has a wrong packagesite, need to
>>> re-create database
>>> Fetching meta.txz: 100%   968 B   1.0k/s00:01
>>> pkg: Error loading trusted certificates
>>> pkg: repository FreeBSD has no meta file, using default settings
>>> Fetching digests.txz: 100%2 MB 119.8k/s00:17
>>> pkg: Error loading trusted certificates
>>> pkg: Unable to update repository FreeBSD
>>> All repositories are up-to-date.
>>> pkg: Repository FreeBSD has a wrong packagesite, need to
>>> re-create database
>>> pkg: Repository FreeBSD cannot be opened. 'pkg update' required
>>> Updating database digests format: 100%
>>> pkg: No packages available to install matching 'firefox' have
>>> been found in the repositories
>>>
>>>
>>> Just for the record, could someone knowledgeable please post the
>>> real, current list of required config files and their contents OR
>>> a pointer to known-good+complete documentation?
>>>
>>> Thanks!  
>>
>> Please show us the following output
>> $ pkg info pkg
> 
> 
> [momcat:root]~> pkg info pkg
> pkg-1.3.8_3
> Name   : pkg
> Version: 1.3.8_3
> Installed on   : Fri Oct 10 07:57:56 EDT 2014
> Origin : ports-mgmt/pkg
> Architecture   : freebsd:9:x86:64
> Prefix : /usr/local
> Categories : ports-mgmt
> Licenses   : BSD2CLAUSE
> Maintainer : port...@freebsd.org
> WWW: http://wiki.freebsd.org/pkgng
> Comment: Package manager
> Shared Libs provided:
>   libpkg.so.3
> Flat size  : 8.18MiB
> Description:
> Package management tool
> 
> WWW: http://wiki.freebsd.org/pkgng
> 
> 
>>
>> and from next command everything from "Repositories:" to the end (last ~10 
>> lines)
>> $ pkg -vv
> 
>  
>  Repositories:
>   FreeBSD: { 
> url :
> "pkg+http://pkg.freebsd.org/freebsd:8:x86:64/latest";,
> enabled : yes,
> mirror_type : "SRV",
> signature_type  : "FINGERPRINTS",
> fingerprints: "/usr/share/keys/pkg"
>   }
>  13:41 Fri, 10 Oct [momcat:root]~> 
> 

There is a architecture mismatch, your pkg claims to be a 9.x package and your 
repo wants to install 8.x packages.
I suspect this is a upgraded system that has maunualy changes in the repo file.

Locate the file "/etc/pkg/FreeBSD.conf" and make sure it looks like the 
following lines (the variable ${ABI} instead "freebsd:8:x86:64")
(it is possible a correct copy exists in /usr/src/etc/pkg/FreeBSD.conf)

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}


after fixing the repo run
$ pkg update -f


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: PKG not quite ready for prime time

[olli hauer]

On 2014-10-10 19:13, scratch65...@att.net wrote:
> I'm having quite a lot of trouble converting to pkg due to there
> being no obvious source of accurate documentation.   I got this
> after I thought I had it solved and could install something:
> 
> 11:36 Fri, 10 Oct [momcat:root]~> pkg install firefox
> Updating FreeBSD repository catalogue...
> pkg: Repository FreeBSD has a wrong packagesite, need to
> re-create database
> Fetching meta.txz: 100%   968 B   1.0k/s00:01
> pkg: Error loading trusted certificates
> pkg: repository FreeBSD has no meta file, using default settings
> Fetching digests.txz: 100%2 MB 119.8k/s00:17
> pkg: Error loading trusted certificates
> pkg: Unable to update repository FreeBSD
> All repositories are up-to-date.
> pkg: Repository FreeBSD has a wrong packagesite, need to
> re-create database
> pkg: Repository FreeBSD cannot be opened. 'pkg update' required
> Updating database digests format: 100%
> pkg: No packages available to install matching 'firefox' have
> been found in the repositories
> 
> 
> Just for the record, could someone knowledgeable please post the
> real, current list of required config files and their contents OR
> a pointer to known-good+complete documentation?
> 
> Thanks!  

Please show us the following output
$ pkg info pkg

and from next command everything from "Repositories:" to the end (last ~10 
lines)
$ pkg -vv

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: pkg-1.4.0.p.a11 conflicts with pkg-1.3.7 (installs files into the same place).

[olli hauer]

On 2014-09-17 20:24, Lucas Willian Bocchi wrote:
> No. The packages are downloaded using pkg.

Look if you have a copy of pkg-1.3.7 in /var/cache/pkg/
If not run '$ pkg -vv' there are lines similar to the next lines

Repositories:
  FreeBSD: {
url : "pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest";,
...
  }

Now append "/Latest/pkg.txz" and use fetch to get pkg-1.3.7 for your system
$ fetch http://pkg.freebsd.org/freebsd:10:x86:64/latest/Latest/pkg.txz

Extract the archive and use pkg-static from here.
All othere steps are the same as described in the first reply

// hth. olli

> 
> 2014-09-17 15:11 GMT-03:00 olli hauer :
>> On 2014-09-17 16:15, Lucas Willian Bocchi wrote:
>>> Hi
>>>
>>> I have the same problem on my FreeBSD 10.
>>>
>>> My server are in production environment and now packages such as PHP
>>> and others won't work anymore because the packages have updates to do
>>> but with this conflict the server won't complete the update process.
>>> No way to force the installation of pkg 1.4 and no way to solve the
>>> problem using pkg 1.3.7.
>>>
>>> Any ideas?
>>
>> Are the packages build by yourself and if yes with which pkg version?
>>
>> In case packages where build with pkg 1.3.7 there is a way back.
>>
>> $ cp -R /var/db/pkg /var/db/pkg.save
>> $ mkdir backdir && cd backdir
>> $ cp /usr/local/sbin/pkg-static pkg-static-$pkgver
>> $ ./pkg-static-$pkgver delete -f pkg
>>
>> Transfer pkg-static from 1.3.7 to the system and read 'man pkg-backup'
>>
>> $ ./pkg-static-1.3.7 backup -r src_file
>>
>> where src_file is one of the backups stored as as 
>> /var/backups/pkgdb.bak.tbz(.num)
>>
>>
>> --
>> hth.
>> olli
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

[olli hauer]

On 2014-09-16 18:05, Nathan Whitehorn wrote:
> 

< snip very long conversation>
http://lists.freebsd.org/pipermail/freebsd-ports/2014-September/095521.html


> I've made a third version of the patch that chases some recent updates to the 
> ports tree and can be found at:
> http://people.freebsd.org/~nwhitehorn/pkg-new-abi-v3.diff
> 
> Please let me know if you run into any difficulties.
> -Nathan


Short success summary for patch pkg-new-abi-v3.diff

The following tests where done on FrreeBSD-10 (amd64) with poudriere-devel for 
package building


Package building.

build 1: 10amd64-default-abi1
 - package build (without pkg-new-abi-v3.diff)

apply pkg-new-abi-v3.diff after build 1.

build 2: 10amd64-default-abi2
 - $ cpdup 10amd64-default-abi1 10amd64-default-abi2
 - rebuild pkg (pkg-1.3.7_1)

build 3: 10amd64-default-abi3
 - $ cpdup 10amd64-default-abi2 10amd64-default-abi3
 - remove some packages to force rebuild (pcre, and some others)
 - rebuild missing packages

build 4: 10amd64-default-abi4
 - fresh build (all packages with applied pkg-new-abi-v3.diff)


Setup apache based repo:

# old ABI
Alias /pkg/freebsd:10:x86:64/abi1/ $path_to/10amd64-default-abi1/

# new ABI
# Note: both abi1 aliases are required for the upgrade / downgrade
# test and until all systems running the new patched pkg
Alias /pkg/FreeBSD:10:amd64/abi1/  $path_to/10amd64-default-abi1/
Alias /pkg/FreeBSD:10:amd64/abi2/  $path_to/10amd64-default-abi2/
Alias /pkg/FreeBSD:10:amd64/abi3/  $path_to/10amd64-default-abi3/
Alias /pkg/FreeBSD:10:amd64/abi4/  $path_to/10amd64-default-abi4/


$ cat pkg/repos/abi.conf
FreeBSD: { enabled: no }
abi: {
 url: "http://$repo-host/pkg/${ABI}/abi1";, <= changed during the tests
 enabled : yes,
 mirror_type : none
}


start:
- install packages from abi1 on fresh system

test 1:
- change repo to abi2 + pkg update / upgrade to patched pkg
  ==> OK, no issues

test 2:
- remove some ports, reinstall them again, pkg upgrade -f
  ==> OK, no issues

test 3:
- change repo to abi3 + repead all tests
  ==> OK, no issues

test 4:
- change repo to abi4 + repead all tests
  ==> OK, no issues

test 5:
- change repo back to abi1 + repead all tests (downgraded pkg)
  ==> OK, no issues


Short summary:
- update / upgrade / downgrade worked as expected between every build.
- packages are reporting on every test the old ABI (Architecture: 
freebsd:10:x86:64)
- issues found in patch v1/v2 are no longer present and fixed


I think the patch works as expected, but please test yourself!

If someone is interested to get the packages from the builds 1-4 send me a PM, 
I have them available as archive (~120MB).


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: pkg-1.4.0.p.a11 conflicts with pkg-1.3.7 (installs files into the same place).

[olli hauer]

On 2014-09-17 16:15, Lucas Willian Bocchi wrote:
> Hi
> 
> I have the same problem on my FreeBSD 10.
> 
> My server are in production environment and now packages such as PHP
> and others won't work anymore because the packages have updates to do
> but with this conflict the server won't complete the update process.
> No way to force the installation of pkg 1.4 and no way to solve the
> problem using pkg 1.3.7.
> 
> Any ideas?

Are the packages build by yourself and if yes with which pkg version?

In case packages where build with pkg 1.3.7 there is a way back.

$ cp -R /var/db/pkg /var/db/pkg.save
$ mkdir backdir && cd backdir
$ cp /usr/local/sbin/pkg-static pkg-static-$pkgver
$ ./pkg-static-$pkgver delete -f pkg

Transfer pkg-static from 1.3.7 to the system and read 'man pkg-backup'

$ ./pkg-static-1.3.7 backup -r src_file

where src_file is one of the backups stored as as 
/var/backups/pkgdb.bak.tbz(.num)


-- 
hth.
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mod_auth_xradius fails with apache-2.4

[olli hauer]

On 2014-09-12 21:20, Michael W. Lucas wrote:
> On Tue, Sep 09, 2014 at 03:47:28PM +0200, Andreas Nilsson wrote:
>>Hello,
>>since they changed apache default from 2.2 to 2.4 in ports
>>mod_auth_xradius has been failing�  to build over here. Should it
>>perhaps just have
>>USE_APACHE=22 (and not 22+)?
>>Best regards
>>Andreas Nilsson
> 
> Hi,
> 
> Thanks for the report. Yes, you're correct.
> 
> Ports team, I'm flooded at the moment. Can someone please 
> commit the one-character fix to www/mod_auth_xradius? It
> should only work with Apache 2.2.
> 
> Thanks,
> ==ml

Hi Andreas,

I think this should be fixed after updating the ports tree.
There was an issue in Mk/bsd.apache.mk that was fixed yesterday.
If there are more ports failing, please remove the apache package from the pd 
package directory and also packages beginning with ap22-/ap24- and start a new 
build.

Related entries from the provided log:


>> >> Building www/mod_auth_xradius
>> build started at Tue Sep  9 14:12:15 CEST 2014
>> port directory: /usr/ports/www/mod_auth_xradius

>> ---Begin Environment---
>> PKGNAME=ap24-mod_auth_xradius-0.4.6_1
...
>> ---End Environment---
>>
>> ---Begin OPTIONS List---
>> ===> The following configuration options are available for 
>> ap24-mod_auth_xradius-0.4.6_1:
>>  MEMCACHE=on: Use memcache to cache radius auth
>> ---End OPTIONS List---
>>
>> --SUB_LIST--
>> APACHEMODDIR="libexec/apache24"
>> APACHEETCDIR="etc/apache24"
>> APACHE_VERSION="24"
...
>> --End SUB_LIST--
>>
>> ---Begin make.conf---
...
>> DEFAULT_VERSIONS = perl5=5.16 apache=2.2

apache22 is set to default and was not honored by Mk/bsd.apache.mk,
this issue is fixed meanwhile.



>> ===
>> ===>  Found saved configuration for ap22-mod_auth_xradius-0.4.6_1
>> ===
>> ===
>> ===>   ap24-mod_auth_xradius-0.4.6_1 depends on file: /usr/local/sbin/pkg - 
>> not found
>> ===>Verifying install for /usr/local/sbin/pkg in 
>> /usr/ports/ports-mgmt/pkg
>> ===>   Installing existing package /packages/All/pkg-1.3.7.txz
>> [93-amd64-server-srv_wb-job-02] Installing pkg-1.3.7... done
...

>> ===>  Patching for ap24-mod_auth_xradius-0.4.6_1
>> ===
>> ===
>> ===>   ap24-mod_auth_xradius-0.4.6_1 depends on file: /usr/local/sbin/apxs - 
>> not found
>> ===>Verifying install for /usr/local/sbin/apxs in /usr/ports/www/apache24
>> ===>   Installing existing package /packages/All/apache24-2.4.10_1.txz

>> ===>Verifying for apr_memcache in /usr/ports/www/apr_memcache
>> ===>   Installing existing package /packages/All/apr_memcache-0.7.0.txz
>> [93-amd64-server-srv_wb-job-02] Installing apr_memcache-0.7.0... done


There no www/apr_memcache port in the ports tree, try to build the original 
www/mod_auth_xradius port.

Test build on 8.4/10
$ uname -a
FreeBSD d24g 8.4-RELEASE-p14 FreeBSD 8.4-RELEASE-p14 #0: Tue Jul  8 12:41:46 
UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  
amd64
$ make
...
=> build OK

$ uname -a
FreeBSD f10 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul  8 06:37:44 UTC 
2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
$ make
...
=> build OK


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Splitting devel/subversion into SEVERAL ports -- how fine-grained do we want to see it?

[olli hauer]

On 2014-09-04 17:10, James R. Van Artsdalen wrote:
> So how does port subversion work now?  I don't get mod_dav_svn installed
> and I don't see a knob for it.
> 
> There is  port www/mod_dav_svn but devel/subversion doesn't seem to
> reference it, and www/mod_dav_svn just gives errors when apache24 tries
> to start.(needs shared memory support that or some such).
> 
> port devel/subversion does have the mod_dav_svn code in the work tree;
> it just isn't installed.

Hi James,

the port was separated, so devel/subversion can be installed via pkg from pre 
build packages without having apache as dependency.

Unluckily in the first apache24 revision not all required modules where ON per 
default but this was fixed some weeks ago.

In case you don't use custom apache24 options just run `make rmconfig && make 
config' inside the www/apache24 port directory to pick up the new default 
module list.

To compare the options before after run before 'make showconfig > cfg.old' and 
after reconfigure the OPTIONS 'make showconfig > cfg.new'

To build the apache module install devel/subversion and then www/mod_dav_svn 
(there are pre build packages available, `pkg install devel/subversion 
www/mod_dav_svn')

After installing apache24 compare your etc/apache24/httpd.conf with the 
httpd.conf from your new build (/usr/local/share/examples/apache24/httpd.conf)

E.g  vimdiff /usr/local/etc/apache24/httpd.conf 
/usr/local/share/examples/apache24/httpd.conf and merge missing LoadModule 
directives into existing etc/apache24/httpd.conf

A possible configuration file candidate that will be used by the subversion 
port in the future can be found here (replace %%APACHEMODDIR%% with 
libexec/apache24)
http://people.freebsd.org/~ohauer/diffs/220_subversion.conf.sample.in

As soon as pkg support sub packages it is possible the port will change again 
since then it is no longer required to split the port into pices.

-- 
hth. olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

[olli hauer]

On 2014-08-31 22:38, Torfinn Ingolfsen wrote:
> On Sun, Aug 31, 2014 at 8:37 PM, olli hauer  wrote:
>>
>> Hm, do you mean update with subversion to 8.4-stable or 8.4-current?
> 
> Yes, and 8.4-stable. There is no 8.4-current.
> 
>> Unless you have a non default kernel there is no need to rebuild to get 
>> 8.4-stable, just run `freebsd-update fetch install' without '-r ...' and you 
>> are done.
> 
> Ok. Old habits came into play; I've always updated my FreeBSD systems
> via source. It is that freebsd-update which is new to me...
> 
> 
>> Rebuilding the system from source can break freebsd-update specially if 
>> build with custom optimizations (-O...)
> 
> Noted. In my case, using freebsd-update was only to get out of the
> "ports tree suddenly not supported" situation I got into.
> 
>> Anyway good to hear you managed to get your system to a supported release.
> 
> Yes. :)
> 

If you have the time / resources setup a small test jail/vm with an older
release to play with freebsd-update try it out.

In case there is a security update or other fix for stable freebsd-update
will lift your system with one or two commands to the new stable version.

freebsd-update updates not only the OS but also /usr/src

Once you've done that you will love it.

PS:
After using freebsd-update the directory "/var/db/freebsd-update" and
your system is running stable you can cleanup everything inside
"/var/db/freebsd-update" to save some space.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

[olli hauer]

On 2014-08-31 19:43, Torfinn Ingolfsen wrote:
> On Thu, Aug 28, 2014 at 8:26 AM, Erich Dollansky
>  wrote:
>> Hi,
>>
>> I did not got through the full thread to see if you found a solution.
> 
> Yes, I did. In fact, freebsd-update provided the solution; I used it
> to upgrade to FreeBSD 8.4-release:
> root@kg-vm2# uname -a
> FreeBSD kg-vm2 8.4-RELEASE-p14 FreeBSD 8.4-RELEASE-p14 #0: Tue Jul  8
> 12:41:46 UTC 2014
>  r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> and since the machine now is on a supported version, the ports tree
> works again, and I installed subversion and
> used that to get the latest FreeBSD 8-stable source on the machine,
> and used that to update the machine to FreeBSD 8.4-stable.

Hm, do you mean update with subversion to 8.4-stable or 8.4-current?

Unless you have a non default kernel there is no need to rebuild to get 
8.4-stable, just run `freebsd-update fetch install' without '-r ...' and you 
are done.

Rebuilding the system from source can break freebsd-update specially if build 
with custom optimizations (-O...)

Anyway good to hear you managed to get your system to a supported release.


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

[olli hauer]

On 2014-08-26 18:01, Nathan Whitehorn wrote:
> On 08/18/14 15:02, olli hauer wrote:
>> On 2014-08-18 18:15, Nathan Whitehorn wrote:
>>> On 08/14/14 13:40, olli hauer wrote:
>>>> On 2014-08-14 21:42, Bryan Drewery wrote:
>>>>> On 8/14/2014 2:38 PM, olli hauer wrote:
>>>>>> On 2014-08-14 17:35, Nathan Whitehorn wrote:
>>>> ...
>>>>
>>>>> Something I've mentioned to Bapt a few times is that pkg needs a way to
>>>>> have a list of accepted ABI strings. Then we could add both the old and
>>>>> the new style as accepted (internally) so that old and new repositories
>>>>> will continue to work.
>>>>>
>>>> Ups, rollback is not possible after the client database was updated.
>>>>
>>>> Even by rollback and rebuild the package metadata the following error pops 
>>>> up.
>>>>
>>>> ~/pkg-static.old_ABI update -f
>>>> Updating repository catalogue
>>>> pkg-static: Repository str has a wrong packagesite, need to re-create 
>>>> database
>>>> Fetching meta.txz: 100% of 584 B
>>>> Fetching digests.txz: 100% of 43 kB
>>>> Fetching packagesite.txz: 100% of 138 kB
>>>>
>>>> Adding new entries: 34%
>>>> pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64
>>>>
>>>> pkg-static: repository str contains packages with wrong ABI: 
>>>> FreeBSD:8:amd64
>>>> Adding new entries: 100%
>>>> pkg-static: Unable to update repository str
>>>
>>> Hm. I'm not sure how to handle this. There are two places that emit hard 
>>> errors in such cases: pkg-add, which is fine since we have a workaround 
>>> there, and here. The check is at line 446 of libpkg/repo/binary/update.c 
>>> (you can comment it out for testing). For this one, there does not seem to 
>>> be any good solution and we need to find one since this is the same issue 
>>> you ran into the upgrade path.
>>>
>>> Here are the two options I see. They are similar to each other, and we 
>>> could do both for some time.
>>> 1. Make an intermediate pkg that is otherwise unaltered but doesn't have 
>>> this check during updates and keep it in the tree for some substantial 
>>> length of time so most people have it by the time we want upgrades to the 
>>> new ABI strings.
>>> 2. Set PKGNG_ALTABI globally on the ports tree for i386 and amd64 for some 
>>> period of time so that all built packages get the current ABI identifiers 
>>> rather than the new ones.
>>>
>>> Any preference here? Or other options?
>>
>> Hi Nathan,
>>
>> Your suggestion 2) could do the trick, at last for current ports.
>>
>> I will see if I can do some additional tests the next days, specially with 
>> mixed ABI strings in the packages.
>>
> 
> Did you have any chance to do the tests? I prepared a new version of the 
> patch at http://people.freebsd.org/~nwhitehorn/pkg-new-abi-v2.diff that marks 
> all built binary packages for i386 and amd64 with the freebsd:*:x86:* 
> identifiers and so should prevent the old version of pkg from bailing on a 
> repository with mixed ABI strings. Testing would be much appreciated.
> -Nathan


Hi Nathan,

if it is not to late I will setup the in next 24h two fresh builds (with / 
without your patch) and test again.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[olli hauer]

On 2014-08-24 14:37, Michael Gmelin wrote:
> 
> 
> On Sun, 24 Aug 2014 14:30:06 +0200
> Kurt Jaeger  wrote:
> 
>> Hi!
>>
 Hm, using USE_BDB=$numble looks wrong to me in devel/ice.

 Can you test the following patch.

 Index: Makefile
 ===
 --- devel/ice/Makefile(revision 365910)
 +++ devel/ice/Makefile(working copy)
 @@ -27,7 +27,8 @@
  .endif

  USES=  iconv gmake
 -USE_BDB=   5
 +USE_BDB=   yes
 +WANT_BDB_VER=  5
  INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
  USE_LDCONFIG=  yes
  BUILD_WRKSRC?= ${WRKSRC}/cpp
>>
>>> @Kurt: Could you test and confirm? If this works, I'll commit the
>>> patch.
>>
>> Yes, it builds.
>>
> 
> I created a commit request
> 
> https://reviews.freebsd.org/D679
> 

Kurt, or you can commit this even w.o. PR.
The patch does not break anything but allows the port to build as required.
I assume there are even more easter eggs in the tree, specially for USE_BDB.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation

[olli hauer]

On 2014-08-24 13:11, Kurt Jaeger wrote:
> Hi!
> 
>>> For devel/ice:
> [...]
>> Is this exclusive to portupgrade (does "make install" work)? Ice
>> only supports bdb 5, so the Makefile should be correct.
> 
> No, it's not exclusive. Same behaviour with
> 
> # make
> ===>  Ice-3.5.1_1 cannot install: no eligible BerkeleyDB version. Requested: 
> 6, incompatible: 40 41 42 43 44 46 47 48 6. Try: make debug-bdb.
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/devel/ice
> 


Hm, using USE_BDB=$numble looks wrong to me in devel/ice.

Can you test the following patch.

Index: Makefile
===
--- devel/ice/Makefile(revision 365910)
+++ devel/ice/Makefile(working copy)
@@ -27,7 +27,8 @@
 .endif

 USES=  iconv gmake
-USE_BDB=   5
+USE_BDB=   yes
+WANT_BDB_VER=  5
 INVALID_BDB_VER=   40 41 42 43 44 46 47 48 6
 USE_LDCONFIG=  yes
 BUILD_WRKSRC?= ${WRKSRC}/cpp


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Fwd: building java/eclipse in HEAD w/ poudriere: java.lang.OutOfMemoryError: Java heap space

[olli hauer]

On 2014-08-23 20:16, Bryan Drewery wrote:
> On 8/23/2014 8:51 AM, Matthias Apitz wrote:
>>
>> Hello ljboi...@gmail.com,
>>
>> Can you as the MAINTAINER of the port please clarify how one can build
>> this port on
>>
>> FreeBSD vm-tiny-r269739 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r269739M:
>> Fri Aug 15 18:07:41 CEST 2014 
>> guru@vm-tiny-r269739:/usr/obj/usr/src/sys/GENERIC  i386
>>
>> $ LANG=C svn info
>> Path: .
>> Working Copy Root Path: /usr/ports
>> URL: svn://svn.freebsd.org/ports/head/java/eclipse
>> Relative URL: ^/head/java/eclipse
>> Repository Root: svn://svn.freebsd.org/ports
>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
>> Revision: 364388
>> Node Kind: directory
>> Schedule: normal
>> Last Changed Author: marino
>> Last Changed Rev: 361589
>> Last Changed Date: 2014-07-11 23:56:01 +0200 (Fri, 11 Jul 2014)
>>
>> Thanks in advance
>>
>>  matthias
>>
>> - Forwarded message from Matthias Apitz  -
>>
>> Date: Sat, 23 Aug 2014 09:19:10 +0200
>> From: Matthias Apitz 
>> To: freebsd-ports@freebsd.org
>> Cc: freebsd-j...@freebsd.org
>> Subject: building java/eclipse in HEAD w/ poudriere:
>>  java.lang.OutOfMemoryError: Java heap space
>>
>>
>> Hello,
>>
>> I'm building ports in HEAD with poudriere; java/eclipse is failing with 
>> java.lang.OutOfMemoryError: Java heap space
>>
>> I've already set in make.conf
>>
>> MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
>>
>> But tis does not help; the VM where poudriere is running has 4 GByte
>> memory and 4 GByte swap space.
>>
>> Any ideas? Thanks
>>
>>  matthias
>>
> 
> Once a solution is found we need it for java/openjdk* as well since they
> use all ram in the system. On our package builders this is 96GB. We need
> to be able to limit how much they can use for building so they only have
> a few GB and not 96.
> 

For FreeBSD >= 9.x rctl can be a solution to limit jail resources.
Unluckily it seems that RACCT/RCTL it not a default kernel option and also not 
a loadable module ...
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/security-resourcelimits.html#idp72352048


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

[olli hauer]

On 2014-08-18 18:15, Nathan Whitehorn wrote:
> 
> On 08/14/14 13:40, olli hauer wrote:
>> On 2014-08-14 21:42, Bryan Drewery wrote:
>>> On 8/14/2014 2:38 PM, olli hauer wrote:
>>>> On 2014-08-14 17:35, Nathan Whitehorn wrote:
>> ...
>>
>>> Something I've mentioned to Bapt a few times is that pkg needs a way to
>>> have a list of accepted ABI strings. Then we could add both the old and
>>> the new style as accepted (internally) so that old and new repositories
>>> will continue to work.
>>>
>> Ups, rollback is not possible after the client database was updated.
>>
>> Even by rollback and rebuild the package metadata the following error pops 
>> up.
>>
>> ~/pkg-static.old_ABI update -f
>> Updating repository catalogue
>> pkg-static: Repository str has a wrong packagesite, need to re-create 
>> database
>> Fetching meta.txz: 100% of 584 B
>> Fetching digests.txz: 100% of 43 kB
>> Fetching packagesite.txz: 100% of 138 kB
>>
>> Adding new entries: 34%
>> pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64
>>
>> pkg-static: repository str contains packages with wrong ABI: FreeBSD:8:amd64
>> Adding new entries: 100%
>> pkg-static: Unable to update repository str
> 
> 
> Hm. I'm not sure how to handle this. There are two places that emit hard 
> errors in such cases: pkg-add, which is fine since we have a workaround 
> there, and here. The check is at line 446 of libpkg/repo/binary/update.c (you 
> can comment it out for testing). For this one, there does not seem to be any 
> good solution and we need to find one since this is the same issue you ran 
> into the upgrade path.
> 
> Here are the two options I see. They are similar to each other, and we could 
> do both for some time.
> 1. Make an intermediate pkg that is otherwise unaltered but doesn't have this 
> check during updates and keep it in the tree for some substantial length of 
> time so most people have it by the time we want upgrades to the new ABI 
> strings.
> 2. Set PKGNG_ALTABI globally on the ports tree for i386 and amd64 for some 
> period of time so that all built packages get the current ABI identifiers 
> rather than the new ones.
> 
> Any preference here? Or other options?


Hi Nathan,

Your suggestion 2) could do the trick, at last for current ports.

I will see if I can do some additional tests the next days, specially with 
mixed ABI strings in the packages.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

[olli hauer]

...
> 
> Something I've mentioned to Bapt a few times is that pkg needs a way to
> have a list of accepted ABI strings. Then we could add both the old and
> the new style as accepted (internally) so that old and new repositories
> will continue to work.

Yes, this would help.

I tried as workaround to rebuild the repo catalogs with the un-patched
pkg tool but get on the next system the same complain about changed ABI.

I will roll back to the test system, so new patches can be tested ...

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

[olli hauer]

On 2014-08-14 21:42, Bryan Drewery wrote:
> On 8/14/2014 2:38 PM, olli hauer wrote:
>> On 2014-08-14 17:35, Nathan Whitehorn wrote:
>>>
...

> 
> Something I've mentioned to Bapt a few times is that pkg needs a way to
> have a list of accepted ABI strings. Then we could add both the old and
> the new style as accepted (internally) so that old and new repositories
> will continue to work.
> 

Ups, rollback is not possible after the client database was updated.

Even by rollback and rebuild the package metadata the following error pops up.

~/pkg-static.old_ABI update -f
Updating repository catalogue
pkg-static: Repository str has a wrong packagesite, need to re-create database
Fetching meta.txz: 100% of 584 B
Fetching digests.txz: 100% of 43 kB
Fetching packagesite.txz: 100% of 138 kB

Adding new entries: 34%
pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64

pkg-static: repository str contains packages with wrong ABI: FreeBSD:8:amd64
Adding new entries: 100%
pkg-static: Unable to update repository str


Roll back on the client
# ~/bin/pkg-static backup -r /var/backups/pkgng.db


Roll back on the build host:
- remove all packages that where created meanwhile with the patched pkg
  including pkg.
- reinstall unpatched pkg on the build host
- start a new build

By doing a manual cleanup I also found that packages containing the old ABI are 
not removed.

# ls -ltr
-rw-r--r--  2 root  wheel   2592992 Aug 14 21:10 openssl-1.0.1_15.txz
-rw-r--r--  2 root  wheel   1963944 Aug 14 21:11 subversion-1.8.10_1.txz

# ls -l openssl*
-rw-r--r--  3 root  wheel  2593488 Aug 11 17:31 openssl-1.0.1_14.txz
-rw-r--r--  2 root  wheel  2592992 Aug 14 21:10 openssl-1.0.1_15.txz


So the patch has more side affects ...

Anyway I'm happy to test new patches to get rid of the old ABI string ;)

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

[olli hauer]

On 2014-08-14 17:35, Nathan Whitehorn wrote:
> 
> On 08/14/14 08:02, Bryan Drewery wrote:
>> On 5/28/2014 11:54 AM, Nathan Whitehorn wrote:
>>> The current/previous values are also kept so
>>> that the patched pkg can install a package marked either with an x86:64
>>> or amd64-type architecture ID (symlinks will be needed for a little bit
>>> on the package server to allow both clients to work). Limited testing
>>> suggests it works well -- I can fetch and install packages fine. More
>>> testing would be great.
>> Symlinks are now setup to make testing of this easier.
>>
>> I'll let Bapt signoff on this patch officially and its timeframe. It
>> seems reasonable to me. The use of 'x86' almost caused a regression
>> recently due to its ambiguity.
>>
>> Cheers,
>> Bryan
>>
> 
> Thanks Bryan! If anyone is interested in testing the adapted pkg, there is a 
> patch that can be applied to ports at 
> http://people.freebsd.org/~nwhitehorn/pkg-new-abi.diff. It tries to make this 
> transition as painless as possible by doing the following things:
> 1. Have pkg use e.g. FreeBSD:11:amd64 instead of freebsd:11:x86:64 as an ABI 
> string.
> 2. Maintain the freebsd:11:x86:64-type strings as the "altabi" config 
> variable.
> 3. pkg will install packages where the architecture ID matches either the ABI 
> or ALTABI value, which means that new pkg can install packages made with the 
> older version.
> 4. Patches the ports-mgmt/pkg Makefile so that the package for pkg itself is 
> given a freebsd:11:x86:64-type architecture. This prevents pkg from choking 
> on an update to itself and should, with the symlinks discussed above, make 
> the transition painless and transparent.
> 
> Especially point (4) I'd appreciate testing on if anyone is generating 
> private package repositories.
> -Nathan

Hi Nathan,

Thanks for the patch, but there is a possible chicken <-> egg issue.

I removed old pkg packages from the last build and running a new build so pkg 
was build with the patch.
The first client complains about wrong architecture and there was no way to 
reinstall pkg (even not with force)
Quick solution was to distribute pkg-static to the client and reinstall pkg 
with the new pkg-static.
After the upgrade everything is running as usual ;)

Are there better upgrade paths then my quick workaround ?

Output after pd build was finished on the first client.

# pkg update -f
Updating repository catalogue
Fetching meta.txz: 100% of 584 B
Fetching digests.txz: 100% of 43 kB
Fetching packagesite.txz: 100% of 138 kB

Adding new entries: 34%
pkg: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64

pkg: repository str contains packages with wrong ABI: FreeBSD:8:amd64
Adding new entries: 100%
pkg: Unable to update repository str


Update with help of the patched pkg

# ~/pkg-static update -f
Updating repository catalogue
pkg-static: Repository str has a wrong packagesite, need to re-create database
Fetching meta.txz: 100% of 584 B
Fetching digests.txz: 100% of 43 kB
Fetching packagesite.txz: 100% of 138 kB

Adding new entries: 100%
Incremental update completed, 500 packages processed:
0 packages updated, 0 removed and 500 added.

--
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD unmaintained ports which are currently scheduled for deletion

[olli hauer]

On 2014-08-13 18:37, Dennis Glatting wrote:
> On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote:
>> On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
>> Dennis Glatting, and lo! it spake thus:
>>>
>>> do_install in the Makefile does the chown.
>>
>> Generally you'd want to do something more like using @owner/@group in
>> plist, rather than chown'ing in the stage.  Doing that would break
>> building as non-root, too.
> 
> What's the order? plist cannot change owner/group unless it is defined.
> Or, does plist execution happen /after/ the make process creates the
> owner/group entries?
> 


In case the port defines USERS and GROUPS from ports/(U|G)IDs, then
this GROUPS/USERS are created in a early step during port / packet
installation and they are available before pkg-plist is processed.

USERS=  $user (list) from UIDs
GROUPS= $group (list) from GIDs

In case the port requires user / group not in UIDs/GIDs then request
an entry for them.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: vendir distfile has no top level directory

[olli hauer]

On 2014-08-07 05:18, Dan Langille wrote:
> I’m having a problem upgrading www/bacula-web to the latest version (see 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191583).
> 
> The problem: the vendor tarball has no top level directory.
> 
> e.g. 
> 
> [root@testing ~/tmp/distfiles]# tar -xf 
> /var/ports/distfiles/bacula-web-6.0.1.tgz 
> [root@testing ~/tmp/distfiles]# ls
> DOCS  application core
> joblogs.php pools.php
> READMEbackupjob-report.phpclient-report.php   
> index.php   jobs.phptest.php
> [root@testing ~/tmp/distfiles]# 
> 
> Compare that to bacula, where I get:
> 
> [root@testing ~/tmp/distfiles]# tar -xf 
> /var/ports/distfiles/bacula-7.0.4.tar.gz 
> [root@testing ~/tmp/distfiles]# ls
> bacula-7.0.4
> 
> Is there an optimal way to cater for this without pushing the issue upstream?
> 
> — 

Hi Dan,

you can specify NO_WRKSUBDIR=yes or overwrite the do-extract target.

PS:
I haven't found the 6.0.x source on sf.net only 5.0.x and 7.0.x

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Apache 24 + mod_perl

[olli hauer]

On 2014-08-06 22:45, Patrick Powell wrote:
> On 08/06/14 00:19, Steve Hay wrote:
>> On 3 August 2014 22:13, Patrick Powell  wrote:
>>> On 08/03/14 08:25, olli hauer wrote:
>>>> On 2014-08-01 23:34, Kurt Jaeger wrote:
>>>>> Hi!
>>>>>
>>>>>> Question:  when will mod_perl be available for Apache 24?
>>>>> There's a PR where people are discussing this:
>>>>>
>>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471
>>>>>
>>>>> This PR needs more testers etc.
>>>>>
>>>> I've updated the PR with a patch against the latest mod_perl trunk
>>>> revision (r1602105).
>>>>
>>>> The patch against the port can be grabbed from here or from our bugzilla
>>>>
>>>> http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff
>>>>
>>>> Please test *at own risk*, and report issues to upstream and here so we
>>>> can integrate fresh upstream fixes and update the port.
>>>>
>>>> The first proposed patch will allows the port to build but I have to many
>>>> concerns for integrating this simple fix into the tree.
>>>> I don't believe the first patch on the PR will work right else it would
>>>> take the upstream dev. work and time for mod_perl2 at absurdI -um ...
>>>>
>>>>
>>> I have taken a slightly different approach,   using the mod_perl2 SVN
>>> /httpd24 branch as the starting point.
>>>
>> The httpd24 branch is obselete. It was used for the initial
>> development of httpd-2.4 support, but was superseded by
>> httpd24threading, and since then everything from both branches has
>> been merged back to trunk.
>>
>> The current trunk is largely ready for a 2.0.9 release supporting
>> httpd-2.4, pending some more testing and fixes as necessary.
>>
> I tried using the trunk a couple of days ago and it did not compile.  Just to 
> make sure
> that I am using the right SVN respository and branch, what is the URL of the 
> trunk SVN repository?
> I am more than happy to try testing mod_perl.
> 

Hm, with the following patch applied to www/mod_perl2 it builds fine for me on 
FreeBSD 8.4 / 10.0 (amd64) an apache-2.4.10
http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff

The patch does some adjustments in the port / pkg-plist and fetches a complete 
archive containing all patches so the sources are the same as the upstream 
(r1602105) trunk/httpd24threade branch.

After applying the patch and using the command `make patch' it is easy to 
compare the sources against upstream sources (check out before)
http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24threading
http://svn.apache.org/repos/asf/perl/modperl/trunk


Easiest way to apply the patch against the unmodified port:

$ cd www/mod_perl2
$ fetch 
http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff
$ patch -p1 < mod_perl2-2.0.8_apache24.diff

PS:
I've updated the patch because it needs some additional handling for pkg-plist 
if build against apache-2.2.x (Provider.pm/Provider.so)


-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

issue pkg-plist @exec lines and pkg-install scripts

[olli hauer]

Hi,

haven't found the culprit but it seems during package building the @exec lines 
from pkg-plist are running.

I found this the hard way since many ports where failing on my local pd system.


E.g from viewvc pkg-plist

@unexec if cmp -s %D/viewvc/cvsgraph.conf %D/viewvc/cvsgraph.conf.dist; then rm 
-f %D/viewvc/cvsgraph.conf; fi
@unexec if cmp -s %D/viewvc/mimetypes.conf %D/viewvc/mimetypes.conf.dist; then 
rm -f %D/viewvc/mimetypes.conf; fi
@unexec if cmp -s %D/viewvc/viewvc.conf %D/viewvc/viewvc.conf.dist; then rm -f 
%D/viewvc/viewvc.conf; fi
viewvc/cvsgraph.conf.dist
@exec [ -f %B/cvsgraph.conf ] || cp %B/%f %B/cvsgraph.conf
viewvc/mimetypes.conf.dist
@exec [ -f %B/mimetypes.conf ] || cp %B/%f %B/mimetypes.conf
viewvc/viewvc.conf.dist
@exec [ -f %B/viewvc.conf ] || cp %B/%f %B/viewvc.conf


$ make check-orphans
> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
Error: Orphaned: %%AP_NAME%%/cvsgraph.conf
Error: Orphaned: %%AP_NAME%%/mimetypes.conf
Error: Orphaned: %%AP_NAME%%/%%AP_NAME%%.conf
===> Checking for directories owned by MTREEs
===> Checking for directories handled by dependencies
===> Checking for items in pkg-plist which are not in STAGEDIR
===> Error: Plist issues found.
*** Error code 1


The finished package however has only the *.conf.dist files but many ports are 
broken now because @exec statements and pkg-install scripts are running now 
during package building ...

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Apache 24 + mod_perl

[olli hauer]

On 2014-08-01 23:34, Kurt Jaeger wrote:
> Hi!
> 
>> Question:  when will mod_perl be available for Apache 24?
> 
> There's a PR where people are discussing this:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471
> 
> This PR needs more testers etc.
> 

I've updated the PR with a patch against the latest mod_perl trunk revision 
(r1602105).

The patch against the port can be grabbed from here or from our bugzilla
http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff

Please test *at own risk*, and report issues to upstream and here so we can 
integrate fresh upstream fixes and update the port.

The first proposed patch will allows the port to build but I have to many 
concerns for integrating this simple fix into the tree.
I don't believe the first patch on the PR will work right else it would take 
the upstream dev. work and time for mod_perl2 at absurd-um ...


-- 
regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0): No such file or directory

[olli hauer]

On 2014-07-28 17:18, O. Hartmann wrote:
> Am Mon, 28 Jul 2014 17:01:23 +0200
> olli hauer  schrieb:
> 
>> On 2014-07-28 15:54, O. Hartmann wrote:
>>> The port net/openldap24-server fails to register/install with this error:
>>>
>>> pkg-static:
>>> lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
>>> No such file or directory
>>>
>>> The port/installation is corrupted after that - which makes me very happy.
>>>
>>> Please CC me.
>>>
>>> oh
>>>
>>
>> The following patch should work, seems this is a leftover from libtool -> 
>> libtool:keepla
>>
>>
>> Index: openldap24-server/pkg-plist
>> ===
>> --- net/openldap24-server/pkg-plist  (revision 363124)
>> +++ net/openldap24-server/pkg-plist  (working copy)
>> @@ -84,11 +84,9 @@
>>  %%SHA2%%libexec/openldap/pw-sha2.la
>>  %%SHA2%%libexec/openldap/pw-sha2.so
>>  %%SHA2%%libexec/openldap/pw-sha2.so.0
>> -%%SHA2%%libexec/openldap/pw-sha2.so.0.0.0
>>  %%SMBPWD%%libexec/openldap/smbk5pwd.la
>>  %%SMBPWD%%libexec/openldap/smbk5pwd.so
>>  %%SMBPWD%%libexec/openldap/smbk5pwd.so.0
>> -%%SMBPWD%%libexec/openldap/smbk5pwd.so.0.0.0
>>  libexec/slapd
>>  %%MODULES%%@dirrmtry libexec/openldap
>>  sbin/slapacl
>>
> 
> This works for me.
> 
> I'm uncapable of connecting to the bugreport server from my provider's 
> network! Can not
> issue a PR.
> 


Not required, I've taken the liberty to commit the fix

-- 
br. olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0): No such file or directory

[olli hauer]

On 2014-07-28 15:54, O. Hartmann wrote:
> The port net/openldap24-server fails to register/install with this error:
> 
> pkg-static:
> lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
> No such file or directory
> 
> The port/installation is corrupted after that - which makes me very happy.
> 
> Please CC me.
> 
> oh
> 

The following patch should work, seems this is a leftover from libtool -> 
libtool:keepla


Index: openldap24-server/pkg-plist
===
--- net/openldap24-server/pkg-plist  (revision 363124)
+++ net/openldap24-server/pkg-plist  (working copy)
@@ -84,11 +84,9 @@
 %%SHA2%%libexec/openldap/pw-sha2.la
 %%SHA2%%libexec/openldap/pw-sha2.so
 %%SHA2%%libexec/openldap/pw-sha2.so.0
-%%SHA2%%libexec/openldap/pw-sha2.so.0.0.0
 %%SMBPWD%%libexec/openldap/smbk5pwd.la
 %%SMBPWD%%libexec/openldap/smbk5pwd.so
 %%SMBPWD%%libexec/openldap/smbk5pwd.so.0
-%%SMBPWD%%libexec/openldap/smbk5pwd.so.0.0.0
 libexec/slapd
 %%MODULES%%@dirrmtry libexec/openldap
 sbin/slapacl

-- 
br. olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: PKG 3.1.0 update - Segmentation fault: 11

[olli hauer]

On 2014-07-27 12:02, Jos Chrispijn wrote:
>Hi Bapt,
>I just found another issue with the port update failure:
>> pkg info
>Child process pid=2126 terminated abnormally: Segmentation fault: 11
>> pkg2ng
>Child process pid=2147 terminated abnormally: Segmentation fault: 11
>Analysing shared libraries, this will take a while... Child process
>pid=2150 terminated abnormally: Segmentation fault: 11
>done
>Can you tell me how to solve this?
>Thanks,
>Jos Chrispijn

Try do the following patch (going back to pkg-1.3.0).
In ports-mgmt/pkg do a `make reinstall'

It will take some time for the pkg team to find the issue and prepare a working 
way for all users, so please stay tuned


Index: /usr/ports/ports-mgmt/pkg/Makefile
===
--- /usr/ports/ports-mgmt/pkg/Makefile  (revision 363021)
+++ /usr/ports/ports-mgmt/pkg/Makefile  (working copy)
@@ -1,7 +1,7 @@
 # $FreeBSD$

 PORTNAME=  pkg
-DISTVERSION=   1.3.1
+DISTVERSION=   1.3.0
 CATEGORIES=ports-mgmt
 MASTER_SITES=  \
http://files.etoilebsd.net/${PORTNAME}/ \
Index: /usr/ports/ports-mgmt/pkg/distinfo
===
--- /usr/ports/ports-mgmt/pkg/distinfo  (revision 363021)
+++ /usr/ports/ports-mgmt/pkg/distinfo  (working copy)
@@ -1,2 +1,2 @@
-SHA256 (pkg-1.3.1.tar.xz) = 
5f1d620251774c54dc06468f7b5332186b20e1bdd52eed2cc5a02e7d2bde0fe0
-SIZE (pkg-1.3.1.tar.xz) = 1702492
+SHA256 (pkg-1.3.0.tar.xz) = 
6d3001cdd605e6e3c15e686370cbeea999a5f19e72fd7f26e8af92ed2e2c2a01
+SIZE (pkg-1.3.0.tar.xz) = 1729104


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Merging several branches with ports tree

[olli hauer]

On 2014-07-25 16:13, Beeblebrox wrote:
> I have several ports branches that get merged to the ports tree. The
> structure is such that a pristine (un-merged) copy of each branch is located
> under: /asp/git/ports, /asp/git/marcuscom, /asp/git/linux-c6, /asp/git/my-pc
> 
> I then want to copy all files under each branch to /usr/ports using a
> combination of rsync and the marcusmerge script. The steps I wish to run:
> 1. rsync -uav --exclude=.git /asp/git/ports/ /usr/ports/
> 2. marcusmerge (works, no problem)
> 3. rsync -av --exclude=.git/ /asp/git/linux-c6/ /usr/ports/ (works, no
> problem)
> 4. rsync -av /asp/git/my-pc/ /usr/ports/
> 
> Steps #1 and #4 are the problem.
> * a simple "rsync -a OR -ua" in step 1 does not seem to work when rsyncing
> onto a merged structure and causes problems. What can I use here, so as to
> ensure updates to the primary port tree get written to the combined folder
> (/usr/ports)?
> * my-pc is a self maintained my ports collection. It has one folder with my
> collection in it, but the problem is that the top-level Makefile and
> Mk/bsd.port.mk "VALID_CATEGORIES" must be modified to include the myports
> collection. How can I merge this set to /usr/ports?
> 
> 

Perhaps ports-mgmt/portshaker is a possible tool.

With the line in make.conf there is no need to patch bsd.port.mk for own $CAT
  VALID_CATEGORIES+=foo bar

Use .sinclude instead .include for own Makefile extensions, then there is no 
issue in case the file is missing.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mass commit needed: python breakage in pkgng repo

[olli hauer]

>>>On 2014-07-22 17:34, Nick Hilliard wrote:> sysutils/py-salt has been broken 
>>>for the last couple of weeks.  The
 resulting package didn't include the python egg info directory and as a
 result, py-salt crashed on startup.  There a PR in bugzilla for this:
 
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191986
 
>From what I can tell, this problem has been fixed by this commit:
 
 http://svnweb.freebsd.org/ports?view=revision&revision=362364
 
 So py-salt will need to be rebuilt in the freebsd pkgng repo, but because
 the fix was in bsd.python.mk, the port will need to have PORTREVISION
 bumped in order to flush out the broken version from the pkgng repo.
 
 I've attached a list of other ports which may also be broken (i.e. ports
 whose makefiles include the text USE_PYDISTUTILS but not
 PYDISTUTILS_AUTOPLIST).  Some of these ports may also need to rebuilt, but
 without testing each one of them individually, it may not be be possible to
 tell which.
 
 Could someone consider doing a mass commit to each of these ports to bump
 PORTREVISION so that any potential breakage is flushed out of the pkg 
 repos?
 

Sorry, my mobile has taken the discussion out of list ...

 isn't it easier to bump python instead ?
>>> yep sure would, but that will force a rebuild of ~2700 ports instead of 300.

>> I suspect even more then the 2300 ports (depening ports also counting) but
>> this way really everything will be cached.
>> Dont know if the snap for weekly build was already taken if not it would be
>> an option
> 
> tbh, i'm not familiar enough with the main repo build process +
> consequences to be able to assess how best to deal with this.
> 

Best to address this also to portmgr@ for decicission (added to CC)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: marking vulnerable ports forbidden?

[olli hauer]

On 2014-07-15 14:45, René Ladan wrote:
> Hi,
> 
> according to Freshports [1] there are currently 24 vulnerable ports not
> marked as forbidden.
> How about checking this list on a regular basis and marking such ports and
> forbidden and optionally as deprecated? This would inform users not using
> vuxml earlier about vulnerabilities.
> 
> [1] http://www.freshports.org/ports-vulnerable.php
> 

Hm, in case of mod/php5-5.4.30 I cannot find a vuxml entry or a hint about 
current issues in www/php5 or lang/php5.
Please double check against vuxml and the MASTERPORT before marking the ports 
FORBIDDEN.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: svn commit: r360871 - head/security/pam-pgsql

[olli hauer]

On 2014-07-06 12:18, Tijl Coosemans wrote:
> Author: tijl
> Date: Sun Jul  6 10:18:36 2014
> New Revision: 360871
> URL: http://svnweb.freebsd.org/changeset/ports/360871
> QAT: https://qat.redports.org/buildarchive/r360871/
> 
> Log:
>   The old pkg_install is buggy with @cwd.  Just install the module under
>   PREFIX like all other PAM ports.
> 
> Modified:
>   head/security/pam-pgsql/Makefile
>   head/security/pam-pgsql/pkg-plist
> 

Perhaps it is a good idea to document this change in UPDATING so users can 
adjust there configs like pam, httpd.conf ...

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Apache 2.4 must become default NOW

[olli hauer]

On 2014-07-05 19:09, Bjoern A. Zeeb wrote:
> Hi,
> 
> given ports@ ist listed as maintainer, you get the email.  The Subject says 
> it.  The world has moved on;  in March I had a hard time arguing, in July I 
> just cannot anymore.  We must switch to 2.4;  whatever breaks needs fixing, 
> but somehow other distributions have managed and we did not and keep screwing 
> our users missing a lot of security features.
> 
> Please fix!
> 
> — 
> Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983


Hi Bjoern,

nothing against this change, except your complain comes a little bit late.

The portstree was already tagged for 9.3 some days ago so this change would be 
a possible issue for all users using the 9.3 packages.

Before the default version can be changed a full expr. run by portmgr@ is 
required and all possible issues should be fixed.

Unluckily we have a rolling ports tree (not like RHEL and others where such a 
change happens during new major releases) so there should be also a time frame 
to warn users about such a change.

I remember endless discussions about the removal of apache13 after it was 
already deprecated nearly one year after upstream deprecation ...

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: What is the preferred method for updating ports now?

[olli hauer]

On 2014-06-11 18:20, Paul Schmehl wrote:
> I used to use cvsup.  Then I switched to portsnap.  Do I now need to switch 
> to svn?  

Hi Paul,

portsnap is fine and I haven't heard any rant it will go away.

cvsup was a different part, with the switch to SVN every commit was also staged 
in the background to CVS to keep cvsup alive.
Sice cvs was also removed from the base OS there was no longer a benefit to 
keep cvsup running.
https://wiki.freebsd.org/CvsIsDeprecated


> If so, is there a way to use svn to only update those ports that have changed 
> since the last update? 
> I've been using svn for a while to work on port updates.  I know how to fetch 
> the entire port infrastructure but not how to only update those ports that 
> have changed.  Portsnap can be automated to keep ports up to date.  Is there 
> a similar utility that uses svn instead?

simply go to the root of your portstree and fire the command `svn up', but 
watch the output for conflicts marked with a capital 'C'.
Running from time to time `svn cleanup' will keep remove dead metadata from the 
.svn directory.

In case you prefer portsnap for your tree and svn only for maintain your ports 
thats also fine.


There is a way to do sparse svn checkouts (only ports you maintain)

# sparse checkout
$ cd $space
$ svn checkout --depth empty $svn/url my_svn_workdir

# checkout my ports
$ cd my_svn_workdir
# checkout all top $cat dirs with maintained port
$ svn up --set-depth empty devel dns math net net-mgmt security sysutils www 
x11-toolkits

# checkout maintained ports
$ grep $my@maintainer.email /usr/ports/INDEX-8 | cut -d\| -f 2 | sed 
's;/usr/ports/;;' | xargs svn up

This way you can use portsnap for port building and svn to hack the ports you 
maintain.
After your patches are committed simply use `svn up' in the workdir (also 
before you start hacking a port to limit conflicts)


> Is portmaster going away any time soon?  Or is that now the preferred method 
> for updating ports?  Is portupgrade going away?  (I no longer use it - just 
> wondering.)
> 
> As a port maintainer, what tools do I use now that I've converted to pkgng? 
> Do we still use portlint?  Or is there a new way to do that?
> 
> So many questions..

Answered already by Matthew.

-- 
HTH,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg aparently not respecting subversion make.conf settings

[olli hauer]

On 2014-06-11 00:02, Simon Wright wrote:
> On 10/06/2014 22:35, olli hauer wrote:
...
>>>>>
>>>>> poudriere bulk -j freebsd:9:x86:64 -C ports-mgmt/portdowngrade
>>>>>
>>>>> portdowngrade is removed from the repo and then the rebuild
>>>>> begins:
>>>>>
>>>> :
..


>> Not easy to tell since we do not have the list of ports you feed
>> into pd
>>
>> Perhaps you find the answer in the buildlogs
>>
>> $ grep devel/subversion
>> /usr/local/poudriere/data/logs/bulk/$YourBuild/latest/logs/*.log
>>
>> If you have identified a port that depends on devel/subversion
>> and not devel/subversion17 check the Makefile of this port has a
>> switch for WITH_SUBVERSION_VER
> 
> I've checked these log files and the only thing that references subversion is 
> the subversion 1.8.9 port itself.
> 
> I tried just deleting the 1.8.9 package file and re-running poudriere and 
> 1.8.9 is still rebuilt.
> 
> As per your earlier mail Olli, I also tried this in case something in the pkg 
> database was playing up:
> 
> pkg delete devel/subversion17
> pkg install devel/subversion
> pkg set -o devel/subversion:devel/subversion17
> pkg delete devel/subversion
> pkg install devel/subversion17
> 
> No change, 1.8.9 is still pulled in on the poudriere build of portdowngrade 
> build.
> 
> ---Begin make.conf---
> USE_PACKAGE_DEPENDS=yes
> BATCH=yes
> WRKDIRPREFIX=/wrkdirs
> PACKAGES=/packages
> DISTDIR=/distfiles
>  /usr/local/etc/poudriere.d/make.conf 
> WITH_GECKO=libxul
> NOI4B=1
> OPTIONS_UNSET+=X11
> WITH_PKGNG=yes
> WITH_CUPS=YES
> CUPS_OVERWRITE_BASE=YES
> WITHOUT_LPR=YES
> WITH_BDB_VER=5
> WITH_SSP_PORTS=yes
> WITH_VIM_OPTIONS=yes
> JAVA_PREFERRED_PORTS=JAVA_PORT_NATIVE_OPENJDK_JDK_1_7
> WITH_SUBVERSION_VER=17
> WITHOUT_PKGTOOLS=1
> VALID_CATEGORIES+=local
> DISABLE_MAKE_JOBS=poudriere
> ---End make.conf---
> 
> 
> 
> === ===>   portdowngrade-1.5 depends on executable: svn - not found
> ===>Verifying install for svn in /usr/ports/devel/subversion
> ===>   Installing existing package /packages/All/subversion-1.8.9.txz
> Installing subversion-1.8.9...Installing apr-1.5.1.1.5.3...Installing 
> db5-5.3.28... done
> Installing expat-2.1.0... done
> Installing gdbm-1.11...Installing gettext-0.18.3.1_1...Installing 
> libiconv-1.14_3... done
> 
> 
> I tried 'pkg info -rx subversion' to see whether an old port was responsible:
> 
> [simon@vmserver04 ~]$ pkg info -rx subversion
> subversion17-1.7.17:
> 
> If I build from ports with portupgrade the build works as expected and 
> portdowngrade uses the installed subversion17.
> 
> It seems a little odd . . . .

No, not so strange as you think.

$ grep svn portdowngrade/Makefile
RUN_DEPENDS=svn:${PORTSDIR}/devel/subversion

Do the following
$ cd ports-mgmt/portdowngrade
$ fetch http://people.freebsd.org/~ohauer/diffs/portdowngrade_svn.diff
$ patch < portdowngrade_svn.diff

Now this port uses the correct subversion port.

If it works for you, be so kind and open a PR so it will be added to the 
official port.

-- 
Regards,
olli


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg aparently not respecting subversion make.conf settings

[olli hauer]

On 2014-06-10 22:01, Simon Wright wrote:
> On 10/06/2014 19:45, Scot Hetzel wrote:
>> On Tue, Jun 10, 2014 at 11:31 AM, Simon Wright  wrote:
>>> Hi all
>>>
>>> I've recently set up poudriere and pkg on a 9.2 amd64 box. This has worked
>>> well for the last month or so. However I have just tried to downgrade
>>> subversion to 1.7x from 1.8x to support querying my network /usr/src
>>> /usr/ports that is setup on another box that only runs subversion 1.7.
>>>
>>> As per updating, I set WITH_SUBVERSION_VER=17 in /etc/make.conf and also in
>>> /usr/local/etc/poudriere.d/make.conf, added subversion17 to the list of
>>> packages to be built and removed portdowngrade from the repository with:
>>>
>>> poudriere bulk -j freebsd:9:x86:64 -C ports-mgmt/portdowngrade
>>>
>>> portdowngrade is removed from the repo and then the rebuild begins:
>>>
>> :
>>> ===
>>> ===>   portdowngrade-1.5 depends on executable: svn - not found
>>> ===>Verifying install for svn in /usr/ports/devel/subversion
>>> ===>   Installing existing package /packages/All/subversion-1.8.9.txz
>>> Installing subversion-1.8.9...Installing apr-1.5.1.1.5.3...Installing
>>> db5-5.3.28... done
>>> Installing expat-2.1.0... done
>>>
>>> 
>>>
>>> It looks as though pkg is not recognising the WITH_SUBVERSION_VER=17
>>> variable and instead pulling in version 1.8 which is the default.
>>>
>>> There are no options in portdowngrade to use a specific version of
>>> subversion.
>>>
>>> Can anyone offer any suggestions to let me build a package of portdowngrade
>>> that uses my desired version of subversion or see what I've done wrong?
>>>
>> It looks like you have subversion-1.8.9 in your package repo. Try
>> removing it from the repo and try the poudriere build again.
> 
> Yes I do. I tried to remove the package with poudriere bulk -j 
> freebsd:9:x86:64 -C devel/subversion
> 
> but after removing the package poudriere then rebuilds it. How can I remove 
> devel/subversion for the repo. Can I just delete the package and rerun the 
> bulk command?

Not easy to tell since we do not have the list of ports you feed into pd

Perhaps you find the answer in the buildlogs

$ grep devel/subversion 
/usr/local/poudriere/data/logs/bulk/$YourBuild/latest/logs/*.log

If you have identified a port that depends on devel/subversion and not 
devel/subversion17 check the Makefile of this port has a switch for 
WITH_SUBVERSION_VER

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg aparently not respecting subversion make.conf settings

[olli hauer]

On 2014-06-10 19:08, Simon Wright wrote:
> On 10/06/2014 18:36, Olli Hauer wrote:
>> in case you are running pkg on the client run there the command
>> $ pkg set -o devel/subversion:devel/subversion17
> 
> Thanks Olli. I had sone this but did it again "just to be sure" (TM)
> 
> [simon@vmserver04 /usr/ports]$ sudo pkg set -o 
> devel/subversion:devel/subversion17
> Sudo password:
> Change origin from devel/subversion to devel/subversion17 for all 
> dependencies? [y/N]: y
> [simon@vmserver04 /usr/ports]$ sudo pkg upgrade
> Updating repository catalogue
> Upgrades have been requested for the following 12 packages:
> 
> Reinstalling apr-1.5.1.1.5.3 [01home] (needed shared library changed)
> Reinstalling cairo-1.10.2_10,2 [01home] (needed shared library 
> changed)
> Reinstalling gmp-5.1.3_2 [01home] (needed shared library changed)
> Reinstalling icu-52.1 [01home] (needed shared library changed)
> Reinstalling libxcb-1.10_2 [01home] (needed shared library changed)
> Upgrading phpMyAdmin: 4.2.2 -> 4.2.3 [01home]
> Upgrading pkgconf: 0.9.5 -> 0.9.6 [01home]
> Upgrading serf: 1.3.5 -> 1.3.5_1 [01home]
> Reinstalling subversion17-1.7.17 [01home] (direct dependency changed)
> Reinstalling libX11-1.6.2_2,1 [01home] (needed shared library changed)
> Installing subversion: 1.8.9 [01home]
> Reinstalling portdowngrade-1.5 [01home] (direct dependency changed)
> 
> The upgrade will require 14 MB more space
> 
> 0 B to be downloaded
> 
> Proceed with upgrading packages [y/N]: n
> 
> So it still wants to install devel/subversion and of course poudriere still 
> pulls in 1.8 as well when it tries to build packages.

Hm, in this case it is possible you have to `pkg delete devel/subversion' 
before and then use `pkg install devel/subversion17'
It is also possible pkg does the right thing but not sure.

It is possible a port that is no longer in the tree requests devel/subversion.

Try to identify this port with `pkg info -rx subversion'

In case you want to downgrade because of the serf issues, I will submit later 
an update to a new serf-1.3.6 release that should fix the seen issue,
(Still waiting for a feedback of the subversion18 maintainer)


-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How are ports built now

[olli hauer]

On 2014-06-08 17:20, Paul Schmehl wrote:
> --On June 7, 2014 at 11:16:04 PM +0200 olli hauer  wrote:
> 
>> On 2014-06-07 22:40, Paul Schmehl wrote:
>>> --On June 7, 2014 at 10:22:41 PM +0200 "A.J. 'Fonz' van Werven"
>>>  wrote:
>>>
>>>> Paul Schmehl wrote:
>>>>
>>>>> Recently I upgraded two servers to 8.4 and implemented the pkgng
>>>>> system.
>>>> [snip]
>>>>> Is portmaster not the appropriate method for updating ports with pkgng?
>>>>
>>>> It depends whether you're talking about *building* packages from the
>>>> ports tree or installing binary packages.
>>>>
>>>> As for building from ports, Portmaster doesn't care whether you're using
>>>> the new PNGNG or the old pkg_* tools.
>>>>
>>>
>>> Thanks.  That's good to know.
>>>
>>>>> Now, when I run portmaster -ad, it seems to keep reinstalling the same
>>>>> ports over and over again.
>>>>
>>>> That's strange. Perhaps PKGNG hasn't been initialised properly on your
>>>> system(s), that's all I can think of at the moment. Did you use pkg2ng?
>>>>
>>>
>>> I'm pretty sure I did, but I ran it again.  I noticed several errors
>>> which I will have to investigate.
>>>
>>
>> Do you see which port is looping?
>> Perhaps a port was moved / renamed / removed and portmaster therfore is
>> looping around
>>
>> Sadly I cannot help more since I used all the years tinderbox / poudriere
>> to build packages.
>>
> 
> I've been working on this for two days now, so the parameters have changed a 
> bit.  But here's an example of what prompted my question:
> 
> This is the result of portmaster -ad
> 
> ===>>> All >> (18)
> 
> ===>>> The following actions will be taken if you choose to proceed:
> Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1
> Install textproc/docproj
> Install print/ghostscript9
> Upgrade pkgconf-0.9.5 to pkgconf-0.9.6
> Upgrade lcms2-2.6_1 to lcms2-2.6_2
> Install textproc/docbook-xml
> Install textproc/docbook-sgml
> Install www/mod_authnz_external22
> 
> ===>>> Proceed? y/n [y] n
> 
> This is the result of pkg upgrade -n
> 
> # pkg upgrade -n
> Updating repository catalogue
> Upgrades have been requested for the following 150 packages:
> 
> Installing xf86vidmodeproto: 2.3.1
> Installing damageproto: 1.2.1
> Installing dri2proto: 2.8
> Installing pciids: 20140526
> Installing randrproto: 1.4.0
> Installing perl5: 5.16.3_10
> Installing db48: 4.8.30.0
> Reinstalling autoconf-2.69 (direct dependency changed)
> Reinstalling automake-1.14 (direct dependency changed)
> Reinstalling bootstrap-openjdk-r351880 (needed shared library changed)
> Reinstalling curl-7.37.0 (options changed)
> Reinstalling dejavu-2.34_3 (options changed)
> Upgrading en-freebsd-doc: 43251,1 -> 44807,1
> Reinstalling gettext-0.18.3.1_1 (options changed)
> Reinstalling igor-1.431 (direct dependency changed)
> Reinstalling ja-font-ipa-00303_1 (direct dependency changed)
> Reinstalling libgcrypt-1.5.3_2 (direct dependency changed)
> Reinstalling libwmf-nox11-0.2.8.4_11 (direct dependency changed)
> Reinstalling libxcb-1.10_2 (direct dependency changed)
> Reinstalling libxslt-1.1.28_3 (direct dependency changed)
> Reinstalling mcrypt-2.6.8_1 (direct dependency changed)
> Reinstalling mkfontdir-1.0.7 (direct dependency changed)
> Reinstalling mysqltuner-1.3.0 (direct dependency changed)
> Reinstalling neon29-0.29.6_6 (direct dependency changed)
> Reinstalling p5-Carp-Clan-6.04 (direct dependency changed)
> Reinstalling p5-Locale-gettext-1.05_3 (direct dependency changed)
> Reinstalling p5-XML-Parser-2.41_1 (direct dependency changed)
> Reinstalling p5-type1inst-0.6.1_5 (options changed)
> Reinstalling perl5.14-5.14.4_7 (options changed)
> Reinstalling php5-5.4.29 (options changed)
> Reinstalling php5-bz2-5.4.29 (direct dependency changed)
> Reinstalling php5-ctype-5.4.29 (direct dependency changed)
> Reinstalling php5-curl-5.4.29 (direct dependency changed)
> Reinstalling php5-dom-5.4.29 (direct dependency changed)
> Reinstalling php5-filter-5.4.29 (direct dependency changed)
> Reinstalling php5-hash-5.4.29 (direct dependency changed)
> Reinstalling php5-iconv-5.4.29 (direct dependency changed)
> Reinstalling php5-json-5.4.

Re: how to support STAGEDIR with GNU autoconf

[olli hauer]

On 2014-06-07 22:41, Dirk Jagdmann wrote:
> I'm looking at changing the devel/quilt port to support stageing. I've read 
> the manual and know that there will be a variable STAGEDIR defined somewhere. 
> But where exactly? It seems it is defined in the environment of the FreeBSD 
> ports Makefile, but it is not available as a unix shell environment variable 
> of the sub processes during the autoconf and build.
> 
> My first attempt was to use the STAGEDIR variable in the Makefiles of the 
> quilt program and prepend it to the PREFIX typically used by GNU autoconf 
> style builds. But when building/stageing this port, this variable is defined 
> to nothing. I see this, because the install than install into something like
> 
> //usr/local/bin/
> 
> Notice the double slash at the start, this shows me that STAGEDIR was 
> undefined (or the empty string).
> 
> Next I tried in the ports Makefile to do something like:
> 
> CONFIGURE_ARGS=--prefix=$(STAGEDIR)/usr/local
> 
> But this also does not work, because the FreeBSD ports will add it's own 
> --prefix with /usr/local/ again when running configure. Looking at the 
> config.log here's how the ports system called the configure script:
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> It was created by quilt configure 0.63, which was
> generated by GNU Autoconf 2.69.  Invocation command line was
> 
>   $ ./configure --with-sed=/usr/local/bin/gsed --without-getopt 
> --with-patch=/usr/local/bin/gpatch --prefix=/usr/ports/devel/q\
> uilt/work/stage/usr/local --without-rpmbuild --prefix=/usr/local 
> --mandir=/usr/local/man --infodir=/usr/local/info/ --build=am\
> d64-portbld-freebsd10.0
> ...
> 
> As you can see, the ports system appends it's default GNU autoconf options 
> *after* mine and thus overrides my --prefix.
> 
> Question: what are the best practices to make GNU autoconf ports support 
> staging?
> 

There is a line NO_STAGE in the port, remove it and try to fire a build as 
*unprivileged* user.

With good luck the Makefile in the source of this port uses $(DESTDIR) so 
everything goes well.

If this is not the case there are some ways to enable stage support, e.g
- create do-install: target in the port Makefile and write place instructions 
here
- change the install instructions in the source Makefile
  '$(INSTALL) foo $(PREFIX)/bin' -> '$(INSTALL) foo $(DESTDIR)$(PREFIX)/bin'


Do not overwrite!
> CONFIGURE_ARGS=--prefix=$(STAGEDIR)/usr/local
else binaries and possible scripts are searching later in the wrong place for 
libs ...

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: splitting subversion port?

[olli hauer]

On 2014-06-07 19:10, Lev Serebryakov wrote:
> Hello, Vick.
> You wrote 22 мая 2014 г., 22:18:10:
> 
> VK> I was wondering if you would be open to peeling off the mod_dav_svn
> VK> from being an option in the subversion port to being its own port that
> VK> depends on this one, or making a sub-port that installs subversion
> VK> with it enabled under a different package name.
> 
> VK> The reason I have is that I am trying to switch over to pkgng and
> VK> using pre-built packages for everything.  I can't do this for
> VK> subversion as I need the dav module on one server, but not on any
> VK> other machine I run. Also, I use another apache module,
> VK> www/mod_authnz_crowd, which depends on a subversion built with
> VK> mod_dav_svn. As it stands, I cannot make a package for that easily.
> 
> VK> There is precedent for splitting the apache module out, as PHP5 has
> VK> recently done just that.
> 
> VK> By splitting the module out into its own port, all of this would be
> VK> possible, and it would avoid having to install the module-enabled
> VK> package on all of my servers which would pull down apache, as well,
> VK> which I do not need on my compute nodes.
> 
> VK> Another way of accomplishing the goal would be to make a sub-port
> VK> similar to things like emacs-nox11 and ImageMagick-nox11 that install
> VK> their base ports with specific options. There could be a
> VK> subversion-apache port that builds the subversion port with the apache
> VK> module and dependencies.
> 
> VK> Anyhow, I'm willing to try to do the work, but I wanted to know if
> VK> you're agreeable, and which way you'd prefer to do it. Obviously the
> VK> sub-port would be easier. I have a feeling the split port may not work
> VK> out because the SVNUSER gets changed if the dav module is enabled.
> 
>  Really, I want to split subversion port to many parts (libraries, client,
> server, apache port, tools) for many years, but it hard to achieve as
> subversion build system is rather complex one. I'm waiting for "multiple
> packages from one port" feature in pkg/ng :)
> 
> 

This should be possible if the old pkg tools are no longer supported
(this year Sept.) and code for sub packages is in the tree.

Splitting the package now into several ports is not a preferred way.
Building a full blown subversion triggers without sub packages x times a full
build for every single shaped port (see for example bacula server/client)

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How are ports built now

[olli hauer]

On 2014-06-07 22:40, Paul Schmehl wrote:
> --On June 7, 2014 at 10:22:41 PM +0200 "A.J. 'Fonz' van Werven" 
>  wrote:
> 
>> Paul Schmehl wrote:
>>
>>> Recently I upgraded two servers to 8.4 and implemented the pkgng system.
>> [snip]
>>> Is portmaster not the appropriate method for updating ports with pkgng?
>>
>> It depends whether you're talking about *building* packages from the ports
>> tree or installing binary packages.
>>
>> As for building from ports, Portmaster doesn't care whether you're using
>> the new PNGNG or the old pkg_* tools.
>>
> 
> Thanks.  That's good to know.
> 
>>> Now, when I run portmaster -ad, it seems to keep reinstalling the same
>>> ports over and over again.
>>
>> That's strange. Perhaps PKGNG hasn't been initialised properly on your
>> system(s), that's all I can think of at the moment. Did you use pkg2ng?
>>
> 
> I'm pretty sure I did, but I ran it again.  I noticed several errors which I 
> will have to investigate.
> 

Do you see which port is looping?
Perhaps a port was moved / renamed / removed and portmaster therfore is looping 
around

Sadly I cannot help more since I used all the years tinderbox / poudriere to 
build packages.

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Creating new port

[olli hauer]

H, Raghu,

at first it looks good, but there are some issues in your Makefile that are 
correct in the examples provided to you.

your port should
- use STAGEDIR (in short time we deprecate all ports without stage support, 
also we have checks in place to test the port before a package is created)

- do not use a 'deinstall' target, with a proper pkg-plist everything is handed 
from the pkg tools
  (If you run the command `pkg_deinstall testport-2.1' you will notice nothing 
happens, without a pkg-plist)

- WRKSRC= ${WRKDIR} and later using '${WRKSRC}/${DISTNAME}' is not required in 
your test port, remove the line.
  (in the ports framework WRKSRC is already set to ${WRKDIR}/${DISTNAME})

PS:
In Sept. 2014 the old pkg_(install|deinstall|...) tools will be deprecated and 
everything is build with the new pkg tools (ports-mgmt/pkg)


The required changes in your case (written in svn diff notation)

-   COMMENT=test
-
-   ONLY_FOR_ARCHS= amd64
-
-   WRKSRC= ${WRKDIR}
-   NO_BUILD=   yes
-
-
-   .include 
-
-
-   do-install:
-
-   @${MKDIR} ${PREFIX}/sbin/test/
-   ${INSTALL_PROGRAM} ${WRKSRC}/${DISTNAME}/bin/test/testbinary 
${PREFIX}/sbin/test/
-
-   deinstall:
-   @${RMDIR} ${PREFIX}/sbin/test
-
-   .include 
+   COMMENT=test
+
+   LICENSE=??? (if there is one)
+
+   ONLY_FOR_ARCHS= amd64
+
+   NO_BUILD=   yes
+
+   .include 
+
+   do-install:
+   @${MKDIR} ${STAGEDIR}${PREFIX}/sbin/test
+   ${INSTALL_PROGRAM} ${WRKDIR}/bin/test/testbinary 
${STAGEDIR}${PREFIX}/sbin/test
+
+   .include 

Index: pkg-plist
===
+sbin/test/testbinary
+@dirrm sbin/test


// hth. olli



On 2014-05-30 06:18, Raghu HB wrote:
> Olli and Michelle,
> 
> Thanks a lot, this is what I was looking for (example for the port
> creation), I referred simple sysutils/tw_cli port and created new port and
> package.
> 
> Below are the steps I followed.
> 
> STEP1: Created a test port directory /usr/ports/sysutils/testport
> 
> STEP2: Created Makefile with below content.
> 
>   
> --
> 
>   # $FreeBSD$
>   
>   PORTNAME=   testport
>   PORTVERSION=2.1
>   CATEGORIES= sysutils
>   MASTER_SITES=   ftp://support.com
>   DISTNAME=   testport-2.1
> 
>   MAINTAINER= yourem...@example.com
>   COMMENT=test
> 
>   ONLY_FOR_ARCHS= amd64
> 
>   WRKSRC= ${WRKDIR}
>   NO_BUILD=   yes
> 
> 
>   .include 
> 
> 
>   do-install:
> 
>   @${MKDIR} ${PREFIX}/sbin/test/
>   ${INSTALL_PROGRAM} ${WRKSRC}/${DISTNAME}/bin/test/testbinary 
> ${PREFIX}/sbin/test/
> 
>   deinstall:
>   @${RMDIR} ${PREFIX}/sbin/test
> 
>   .include 
>   
> --
> 
> 
> STEP3: Created the tar file testport-2.1.tar.gz and placed the tar file in
> /usr/ports/distfiles
> 
>   ./ testport-2.1
>   ./ testport-2.1/bin
>   ./ testport-2.1/bin/test
>   ./ testport-2.1/bin/test/testbinary
> 
> STEP4: Change the directory to /usr/ports/sysutils/testport  and run the
> command : make makesum
> 
> STEP5: Run the command "make package"
>   I can see that the port is created and installed.
> 
> STEP6:  try uninstall the port: "make deinstall"
> 
> STEP7: Create the package from the port using the below commands and
> verify the package.
> 
>   pkg_create -b testport-2.1
>   pkg_add -f testport-2.1.tbz
>   pkg_delete testport-2.1
> 
> As I mentioned above I created a test package and which is working fine.
> Please suggest if any changes needed or if something is wrong in above
> steps.
> 
> Now I would say I will create a package for my new application
> "finalpackage.tbz".
> I would like to know if I can ship the "finalpackage.tbz" file to customer
> to use the package on their system for new application?  or it has to be
> registered with FreeBSD community?
> Please guide us with the future steps to release the application to
> customer.
> 
> -Original Message-
> From: olli hauer [mailto:oha...@gmx.de]
> Sent: Thursday, May 29, 2014 1:30 PM
> To: freebsd-ports
> Cc: Raghu HB
> Subject: Re: Creating new port
> 
> On 2014-05-28 12:01, Raghu HB wrote:
>> Thanks Michelle for quick response.
>>
>>
>> First 

Re: Creating new port

[olli hauer]

On 2014-05-28 12:01, Raghu HB wrote:
> Thanks Michelle for quick response.
> 
> 
> First I would like to explain what is the application and how I am trying
> to create port.
> 
> We have some command line utilities to run on FreeBSD (Storage controller
> software).
> The installer should contain few binaries and scripts which will be
> deployed on FreeBSD OS.
> The binaries are pre-compiled and scripts will be used to
> start/stop/restart the services or daemons.
> 
> Created below directory structure "/usr/ports/distfiles/":
> 
> ./mrmonitor-1.1
> ./mrmonitor-1.1/bin
> ./mrmonitor-1.1/bin/mrmonitor
> ./mrmonitor-1.1/bin/mrmonitor/testmonitor
> ./mrmonitor-1.1/Makefile
> 
> I created a tar.gz file which contains the above directory structure with
> the name mrmonitor-1.1.tar.gz.
> 
> The Makefile contents:
> --
> # $FreeBSD$
> PORTNAME=   mrmonitor
> PORTVERSION=1.1
> CATEGORIES= misc
> MASTER_SITES=
> 
> MAINTAINER=raghu...@avagotech.com
> COMMENT=   MRMonitor
> .include 
> --
> 
> 
> Created a home directory /home/Raghu, Created 3 new files Makefile,
> pkg-descr
> 
> The Makefile contents:
> --
> # $FreeBSD$
> PORTNAME=   mrmonitor
> PORTVERSION=1.1
> CATEGORIES= misc
> MASTER_SITES=
> 
> MAINTAINER=raghu...@avagotech.com
> COMMENT=   MRMonitor
> .include 
> --
> 
> 
> pkg-descr
> 
> --
> This is MRMonitor port
> --
> 
> pkg-plist
> --
> bin/mrmonitor
> bin/mrmonitor/testmonitor
> @dirrm bin/mrmonitor
> --
> 
> 
> 
> Now I run the command make makesum which is successful, then I ran the
> command make package I got the errors (attached the error  messages) .
> 
> May be I am doing something wrong in some basic configuration, please
> correct me.
> 
> 
> Thanks,
> Raghu
> 
> -Original Message-
> From: Michelle Sullivan [mailto:miche...@sorbs.net]
> Sent: Wednesday, May 28, 2014 3:14 PM
> To: Raghu HB
> Cc: FreeBSD Ports ML
> Subject: Re: Creating new port
> 
> Raghu HB wrote:
>> Hello,
>>
>>
>>
>> I am new to FreeBSD and I am in a process of creating new port for one
>> of the application.
>>
>> I have gone through the steps in handbook and I tried to create new
>> port but I am not successful.
>>
>>
>>
>> I would request you to send one sample example to create new port with
>> all the steps explained would be a great help.
>>
>>
> 
> What's the application, can you send me your Makefile so far and what
> errors you're getting?
> 
> And I'll try and take a look.
> 
> Michelle
> 
> --
> Michelle Sullivan
> http://www.mhix.org/
> 

Reading the make-error log it looks like `make' is called recursive.
In case the the port does not compile anything try to add the keyword 
NO_BUILD=yes into the port Makefile and use a 'do-install:' target.

e.g.

COMMENT=...

NO_BUILD=   yes

do-install:
${INSTALL} ${WRKSRC}/${ARCH}/mrmonitor ${STAGEDIR}${LOCALBASE}/bin
${INSTALL_SCRIPT} ${WRKSRC}/scripts/$scriptXX 
${STAGEDIR}${LOCALBASE}/bin
...
.include 


If you could provide your full Makefile and a link to the distfile I'm sure the 
port can be finished in short time.
As a hint look at the simple sysutils/tw_cli port


-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: postfix-policyd-weight broken with p5-Net-DNS 0.75

[olli hauer]

On 2014-05-23 23:57, Herbert J. Skuhra wrote:
> Hi,
> 
> after updating p5-Net-DNS from version 0.74 to 0.75
> postfix-policyd-weight (0.1.15.2) stopped working.
> 
> I get the below error on two systems:
> 
> May 23 13:31:35 mx postfix/policyd-weight[1037]: child: spawned 
> May 23 13:31:35 mx postfix/policyd-weight[1037]: warning: child: err: 
> Undefined subroutine &main::dn_expand called at /usr/local/bin/policyd-weight 
> line 3590,  line 23.  
> May 23 13:31:36 mx postfix/policyd-weight[908]: master: child 1037 exited 
> 
> I am using perl 5.16.3 on FreeBSD 8.4-RELEASE-p10 (amd64) and perl
> 5.18.2 on FreeBSD 10.0-STABLE (i386).


Thanks for the notice, mail/postfix-policyd-weight was updated to use the new 
Net::DNS API.

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/dovecot2-pigeonhole does not fetch

[olli hauer]

On 2014-05-19 08:44, Darren Pilgrim wrote:
> This is still the case.  It looks like Dovecot updated to 2.2.13 and 
> pigeonhole to 0.4.3, and they took down the 0.4.2 distfile.  Can we get the 
> 0.4.2 distfile hosted on ftp.freebsd.org until the maintainer updates the 
> ports?
> 
> On 5/15/2014 8:12 PM, Darren Pilgrim wrote:
>> I'm trying to update to v0.4.2, but I get:
>>

The distfiles are now hosted by dovecot.

http://www.dovecot.org/list/dovecot-news/2014-May/000274.html

sha256 is identical, the port was updated to reflect the new MASTER_SITE

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: A child Postfix port with TLS enabled by default

[olli hauer]

On 2014-04-29 03:21, Sahil Tandon wrote:
> Thanks to Olli and Matthias, I amended the original patch; revised
> version attached.
> 
> PS: I could not think of a less hack-ish way to accomplish the warning
> suppression aside from adding those flags to CCARGS.
> 

Hi Sahil,

I have some addition.

mail/postfix port
 - CONFLICTS_INSTALL?= ... misses postfix-tls

else your patch looks good to me :)


-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade to dovecot 2.2.12 failed - libldap not found

[olli hauer]

On 2014-04-28 19:41, olli hauer wrote:
> On 2014-04-28 19:18, Dr. Peter Voigt wrote:
>> I am runing 10.0-RELEASE-p1 with dovecot 2.2.10 and LDAP support.
>>

The issue should be fixed with commit r352584.

Sorry for breakage.

-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade to dovecot 2.2.12 failed - libldap not found

[olli hauer]

On 2014-04-28 19:18, Dr. Peter Voigt wrote:
> I am runing 10.0-RELEASE-p1 with dovecot 2.2.10 and LDAP support.
> 
> 
> The today upgrade to dovecot 2.2.12 fails:
> 
> # portmaster --no-confirm --no-term-title -D -G dovecot
> ...
> checking for auth_userokay... no
> checking for ldap_init in -lldap... no
> configure: error: Can't build with LDAP support: libldap not found
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to b...@fsn.hu [maintainer] and attach the
> "/usr/ports/mail/dovecot2/work/dovecot-2.2.12/config.log" including the
> output of the failure of your make command. Also, it might be a good
> idea to provide an overview of all packages installed on your system
> (e.g. a /usr/local/sbin/pkg-static info -g -Ea).
> *** Error code 1

Hm,

is this also happen if you go direct into mail/dovecot2 and run `make 
configure'?
(without portmaster)


>From my build:
$ make showconfig
===> The following configuration options are available for dovecot2-2.2.12:
 DOCS=on: Build and/or install documentation
 EXAMPLES=on: Build and/or install examples
 GSSAPI=off: GSSAPI support
 KQUEUE=on: kqueue(2) support
 LDAP=on: LDAP support
 LIBWRAP=on: TCP wrapper support
 LUCENE=off: CLucene FTS support
 MYSQL=on: MySQL database support
 PGSQL=on: PostgreSQL database support
 SOLR=on: Solr FTS support
 SQLITE=on: SQLite database support
 SSL=on: SSL protocol support
 VPOPMAIL=off: vpopmail support


$ make configure
...

Install prefix . : /usr/local
File offsets ... : 64bit
I/O polling  : kqueue
I/O notifys  : kqueue
SSL  : yes (OpenSSL)
GSSAPI . : no
passdbs  : static passwd passwd-file pam checkpassword ldap sql
 : -shadow -bsdauth -sia -vpopmail
userdbs  : static prefetch passwd passwd-file checkpassword ldap sql nss
 : -vpopmail
SQL drivers  : pgsql mysql sqlite
Full text search : squat solr
 : -lucene


-- 
Regards,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"