RE: FreeBSD ports you maintain which are out of date
From: owner-freebsd-po...@freebsd.org [owner-freebsd-po...@freebsd.org] on behalf of Mathieu Arnold [m...@freebsd.org] Sent: Wednesday, March 9, 2016 7:11 AM To: portsc...@freebsd.org; po...@freebsd.org Subject: Re: FreeBSD ports you maintain which are out of date Hi, +--On 9 mars 2016 08:33:00 + portsc...@freebsd.org wrote: | Dear port maintainer, | | The portscout new distfile checker has detected that one or more of your | ports appears to be out of date. Please take the opportunity to check | each of the ports listed below, and if possible and appropriate, | submit/commit an update. If any ports have already been updated, you can | safely ignore the entry. | | You will not be e-mailed again for any of the port/version combinations | below. | | Full details can be found at the following URL: | http://portscout.freebsd.org/po...@freebsd.org.html | | | Port| Current version | New | version | +-+-- | -- net-mgmt/weathermap | 1.1.1 | | 29.3.0 | +-+-- | -- > This really is getting annoying. Agreed, It is working tho. Getting more and more motivated to update it to stop the message. XD Ultima ___ 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: cairo w/ x11
From: owner-freebsd-po...@freebsd.org [owner-freebsd-po...@freebsd.org] on behalf of Randy Bush [ra...@iij.ad.jp] Sent: Monday, March 7, 2016 10:02 PM To: gn...@freebsd.org Cc: FreeBSD Ports Subject: cairo w/ x11 FreeBSD dfw0.psg.com 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32:46 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 there are ports that need cairo to be compiled with x11 support go to /usr/ports/graphics/cairo make config turn on x11 OK make config x11 is off how special even setting manually (editing /var/db/ports/graphics_cairo/options) does not work, make config whacks it back this is not new randy Hello, I'm not sure why you're having this issue. Try deleting /var/db/ports/graphics_cairo and run make config again? Is your port tree updated? I actually just did this last night and it is working fine... cairo-1.14.6,2 Name : cairo Version: 1.14.6,2 Installed on : Mon Mar 7 22:18:45 2016 EST Origin : graphics/cairo Architecture : freebsd:10:x86:64 Prefix : /usr/local Categories : graphics Licenses : MPL and LGPL21 Maintainer : gn...@freebsd.org WWW: http://www.cairographics.org Comment: Vector graphics library with cross-device output support Options: GLIB : on OPENGL : on X11: on XCB: on Ultima ___ 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: How to set mariadb in /etc/make.conf DEFAULT_VERSIONS ?
> I think DEFAULT_MYSQL_VER=101m is wrong. bsd.detabase.mk has this warning:
>
> .if defined(DEFAULT_MYSQL_VER)
> WARNING+= "DEFAULT_MYSQL_VER is defined, consider using
> DEFAULT_VERSIONS=mysql=${DEFAULT_MYSQL_VER} instead"
> .endif
Ah, I didn't realize it was deprecated. I had set this some time ago. Changing
it now thanks =]
Ricky
___
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: How to set mariadb in /etc/make.conf DEFAULT_VERSIONS ?
> Hi! > > What is the correct way to set the DEFAULT_VERSIONS to mariadb > in /etc/make.conf ? > > I looked at /usr/ports/Mk/bsd.default-versions.mk. > > In /usr/ports/Mk/bsd.database.mk it looks like 101m is a valid value, > which would map to > > DEFAULT_VERSIONS= mysql=10.1m DEFAULT_MYSQL_VER=101m This is how I have it set. Hope this helps Ricky ___ 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: will the use of GitHub ever be fully explained?
Hey there Chris,
I actually invested some time figuring this out. When the GH_TAGNAME is used,
that hash will be downloaded instead of the PORTVERSION. Pretty much the
PORTVERSION variable is ignored other than the fact that is will be packed as
${PORTVERSION} so it is important to keep TAGNAME and PORTVERSION in sync.
> To: freebsd-ports@FreeBSD.org> From: bsd-li...@bsdforge.com
> Subject: will the use of GitHub ever be fully explained?
> Date: Mon, 21 Dec 2015 08:34:56 -0800
>
> Greetings fellow maintainers,
> I'd like to update a port that's moved to GitHub.
> I pretty well understand the use MASTER_SITES where GitHub
> is concerned *except* where the need to use GIT_HASH for
> GH_TAGNAME, is concerned. Sure, I know how to put it there.
> But I am unclear how that affects the PORTVERSION entry.
> Does anyone have an example they'd be willing to share?
> Please?
>
> What I'd like to accomplish:
>
> PORTVERSION= 2.0
>
> USE_GITHUB= yes
>
> GH_TAGNAME= 95f841f
>
> But I don't think this will work.
>
> Thanks!
>
> --Chris
>
> --
>
>
> ___
> 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"
___
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: will the use of GitHub ever be fully explained?
Hey there Chris,
I actually invested some time figuring this out. When the GH_TAGNAME is used,
that hash will be downloaded instead of the PORTVERSION. Pretty much the
PORTVERSION variable is ignored other than the fact that is will be packed as
${PORTVERSION} so it is important to keep TAGNAME and PORTVERSION in sync.
Hope this helps!
Ricky
> To: freebsd-ports@FreeBSD.org> From: bsd-li...@bsdforge.com
> Subject: will the use of GitHub ever be fully explained?
> Date: Mon, 21 Dec 2015 08:34:56 -0800
>
> Greetings fellow maintainers,
> I'd like to update a port that's moved to GitHub.
> I pretty well understand the use MASTER_SITES where GitHub
> is concerned *except* where the need to use GIT_HASH for
> GH_TAGNAME, is concerned. Sure, I know how to put it there.
> But I am unclear how that affects the PORTVERSION entry.
> Does anyone have an example they'd be willing to share?
> Please?
>
> What I'd like to accomplish:
>
> PORTVERSION= 2.0
>
> USE_GITHUB= yes
>
> GH_TAGNAME= 95f841f
>
> But I don't think this will work.
>
> Thanks!
>
> --Chris
>
> --
>
>
> ___
> 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"
___
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: Call for Help: need script for patching ports tree, building with poudriere
Hey, Added this to github. https://github.com/Ultima1252/portest ___ 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: Call for Help: need script for patching ports tree, building with poudriere
> That is a good attitude :) I am doing this also just to get in touch
> with something new and learn.
> As a professional trainer there is a trick in learning: whenever a
> question arises - by yourself or by another person: take the chance and
> look for it. So you will remember the answer much better. :)
> If you need a programming-mentor for this project feel free to contact
> me off-list.
That would be great! your time will be most appreciated!
>
> To answer my own question, yes there is
>
> You wrote:
>
> ===
> if [ -d "${PORTSDIR}" ]; then
> else
> ===
>
> Which directly skips the if condition without doing something.
>
> Rewrite it with:
>
> ===
> if ! [ -d "${PORTSDIR}" ]; then
> ===
>
> This will test if the dir is non existent - exactly what you want! :)
Yes, I remember this problem now and its fixed! I couldn't figure out where
the explanation mark went. Just missed the space! Thanks so much for clearing
that up.
> >> Line 162: BUILD_LIST="`(cat ${PATCH_FILE} | grep -o '^Index:[ ].*'
> >> | sed 's/Index: // ; s/Mk.*// ; s/Tools.*// ; s/Templates.*// ;
> >> s/Keywords.*//' | grep -o -e '.*\/.*\/' | sed 's/.*\/.*\/files\/$//
> >> ; s/\/$//' | sort | awk '!a[$0]++')`"
> >>
> >> This line is relative complicated. Is there any reason not to let
> >> svn do the work? Like: BUILD_LIST="`${SVN} status | grep -o -e
> >> '.*\/.*\/' | awk '{ print $2 }'`> Your way is faster (and more
> >> accurate, since i'm currently too short on time), but the other way
> >> would allow applying multiple patches and manual changes without
> >> any problems. But i'm not sure if this is really needed.
> >
> > Using the diff file instead of svn is of course faster because there
> > has much less data to go through. I was considering adding multiple
> > diff support. Going to take a closer look at this. Do you think its
> > more important to focus on the diff file or the port tree for
> > generating a build list?
>
> That is a hard question. I asked for svn because i am from Germany and
> facing often problems with umlauts. My lastname is "Zühlsdorff" but i
> rewrite it for non-german person and programs to "Zuehlsdorff". Sounds
> the same, means the same.
>
> Back to the core of the question: encoding problems.
>
> Can you guarantee that cat and sed work correctly on files with for
> example an "ü" or containing something like '合�莸�'? ;)> > Using svn avoids
> this problem, because in the portstree you could not
> find filenames with such characters.
Just added an option that will generate a list via tree over diff. You have a
very valid point about encoding. Have never considered this and I have no idea
how to work this problem out. My only (human) language is english. Will message
you off-list to see if we can fix this issue.
There are a few things that need to be filtered in order to guarantee a
properly generated list. Also the change I made recently, it fixes the issue
with striping possible 15ish ports that end with files, however it will remove
the cat/port/files instead of just striping files. Still trying to find the
best solution.
>
> An additional though: you are assuming that everything is fine with the
> input. It accepts all tracks of my music folder without any hestination
> as a patch-file. ;) Okay, patching fails - but i tries hard and the new
> versions provides much binary trash through the "cat" after failing.
>
> I don't believe we must make it bullet proof. Here we need some input
> from Craig about the way and environment the script will be used in.
Another great point. Did consider this when I started, however haven't yet
come up with the proper solution for verifying diff file or not. The way I was
considering was just something along the lines of head -5 | grep -o Index:
as it is the most consistent thing in patch files. If you wondering why I
choose -5, in cases of comments being on header, 5 lines seems reasonable. This
could cause more encoding issues tho, I'm not sure.
> > The main reason I didn't want to use the
> > port tree, at least in my case, is because I have so many ports that
> > are not sync'd with the current FreeBSD tree.
>
> Okay, but therefore you added the PORTSDIR variable?
Think this may have been misunderstood, or I mislead. I have many ports not
synced with the current head. Rather not generate a list for each of those as
well as the patched ones I want to test.
> >> Line 201: svn revert -R would do the same, both of our approaches
> >> have a problem: the ignore for example added files.
> >
> > Yeah, I agree. This is a big problem with added patchfiles. I added a
> > "Hard Revert" (-R) option that I was considering making make the
> > default that should fix this problem. Can you check and see if it
> > does for you?
>
> I will check this.
>
> > I know some people maybe weary of the rm -rf command,
> > It is also why I added so many checks on a properly set port tree. Do
> > you think it would be
RE: Call for Help: need script for patching ports tree, building with poudriere
Portest version 0.0.2 Changelog: * Fixed Usage with incorrect description on some options* Added multiple patchfile/glob support* More failed patch output, Still working on formating. Ideas would be great.* Changed BUILT_LIST filter to fix unintended stripping of multiple ports* Changed revert (-R) to (-r) and added a new revert (-R) method.* Several changed to revert more explained below As pointed out to me, svn revert -R seems to somehow miss small filenames. This is an svn bug and as a workaround I decided to remove the -r option as it was unreliable altogether, move the -R to -r, and added a filtered revert for the smaller filenames. This solution works well on all my tests with 15+ large diff files, but of course more testing is needed. The new -R option will instead of reverting according to the diff, revert based on changed from the tree. This method is much slower but in the event -r may fail an -R will fix everything regardless of .diff. portest Description: Binary data ___ 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: Call for Help: need script for patching ports tree, building with poudriere
> Thank you very much for your script!
>
> I took a short look at it and have some questions/suggestions:
>
> Line 119/120:
> There you're burning an if. I have more skill in bash than in sh - but
> is there no negation possible?
Honestly, the main reason I started this is to just see what I could do.
Feedback is most appreciated as improving my skills is one of my goals here.
Bash and sh are extremely similar, this is most likely lack of knowledge on my
part. Do you mind explaining further?
>
> Line 162:
> BUILD_LIST="`(cat ${PATCH_FILE} | grep -o '^Index:[ ].*' | sed 's/Index:
> // ; s/Mk.*// ; s/Tools.*// ; s/Templates.*// ; s/Keywords.*//' | grep
> -o -e '.*\/.*\/' | sed 's/.*\/.*\/files\/$// ; s/\/$//' | sort | awk
> '!a[$0]++')`"
>
> This line is relative complicated. Is there any reason not to let svn do
> the work? Like:
> BUILD_LIST="`${SVN} status | grep -o -e '.*\/.*\/' | awk '{ print $2 }'`>
> Your way is faster (and more accurate, since i'm currently too short on
> time), but the other way would allow applying multiple patches and
> manual changes without any problems. But i'm not sure if this is really
> needed.
Using the diff file instead of svn is of course faster because there has much
less data to go through. I was considering adding multiple diff support. Going
to take a closer look at this. Do you think its more important to focus on the
diff file or the port tree for generating a build list? The main reason I
didn't want to use the port tree, at least in my case, is because I have so
many ports that are not sync'd with the current FreeBSD tree.
The main reason that command is complicated is to strip many possible non-port
files/folders so that the list wont contain something like Mk/Uses/. The build
list you suggested would work, but most of the sed command is still needed to
stripe non-ports. Looking at it again, I see where I could make it a bit
shorter and easier to read. The sort and awk command at the end is just make it
look nice and remove duplicates. Not really required.
> Line 201:
> svn revert -R would do the same, both of our approaches have a problem:
> the ignore for example added files.
Yeah, I agree. This is a big problem with added patchfiles. I added a "Hard
Revert" (-R) option that I was considering making make the default that should
fix this problem. Can you check and see if it does for you? I know some people
maybe weary of the rm -rf command, It is also why I added so many checks on a
properly set port tree. Do you think it would be better to just do this "Hard
Revert" and remove the other option?
Thanks for the feedback! I'v already started working on 0.0.2! I just finished
adding better failed patch output. Going to also add a option to override the
scripts portsdir, and add support for multiple diff files, and take another
look at my BUILD_LIST to make it simpler. Keep the feed back coming please! =]
Ultima
___
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: Call for Help: need script for patching ports tree, building with poudriere
Hello, Decided to not add a config file to keep it simpler, so you'll need to edit the variables to your needs below the options. The only packages that it may need is portlint, porttools and/or poudriere. Let me know what you think or needs improvement. portest Description: Binary data ___ 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: Call for Help: need script for patching ports tree, building with poudriere
Almost finished with this, just wanted to give an update. I named this script portest, I still need to add a few more things and do some bug testing but so far it seems to work pretty well. This is the usage page for the script. Usage: portest [-f bulkfile] [-apPrRtv] patchfile Options:-a -- Do everything except revert (-ptf build.ports.txt)-f -- Generate a poudiere usable bulk file-p -- Patch and give output-P -- Do not exit on failed patch-r -- Revert the files listed in patchfile-R -- Paranoid revert, will remove and restore anything and everything the patchfile may have changed or added -t -- Test with portlint-v -- Show version of portest By default, (no options) portest shows the ports that will be modified Decided to add the -a option to do the task you asked for specifically. So far every option works on the patch you supplied and several others I had laying around. One thing that it will not detect is if slave port will be affected by the change, also changes to Uses or any other non CAT/PORT directory will not be detected. I'm still trying to figure out how to solve these problem. Are they important? or not so much? Right now on my todo is to add a config file to change the default settings, Add a -T option that will do port test or poudrieretesting depending on what was selected in the config file. Also later on choose between svn, git or portsnap. Once i'm finished adding the config file ill post it for some testing and if you can give me some feedback on what else you need or don't like. Ultima Date: Mon, 9 Nov 2015 13:55:38 -0800 Subject: Re: Call for Help: need script for patching ports tree, building with poudriere From: rodr...@freebsd.org To: ricky1...@hotmail.com CC: freebsd-test...@freebsd.org; freebsd-ports@freebsd.org On Sun, Nov 8, 2015 at 6:18 PM, Ricky G <ricky1...@hotmail.com> wrote: Hello, Started working on a simple sh script to do as requested. So far have 1,2,4,5 complete. There is much error checking to be added still though. Wanted to ask a few things first. 2- Does port tree checkout matter? Right now my script assumes svnlite generated the patch at the root of the tree5- Does duplicates matter? poudriere doesn't care but is this strictly for poudriere?6- How should the output be handled? The script should not worry about the port tree checkout so much, since that will probably be done outside the script. For now, if the script assumes that the port checkout is an SVN tree, and you can run SVN operations on it, that should be sufficient. For duplicates, I don't think it matters so much. I believe poudriere is smart enough so that if you pass it a list of ports with duplicate entries, it does the right thing. At this point, the output format is not so important. For now, making sure that error status is propagated as a return value from the script (0 on success, non-zero on failure) is a good start. The only other suggestion that I have is that when you work on the script, make sure that you put a proper license in it (BSD license preferred). Thanks. -- Craig ___ 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: Call for Help: need script for patching ports tree, building with poudriere
Hello, Started working on a simple sh script to do as requested. So far have 1,2,4,5 complete. There is much error checking to be added still though. Wanted to ask a few things first. 2- Does port tree checkout matter? Right now my script assumes svnlite generated the patch at the root of the tree5- Does duplicates matter? poudriere doesn't care but is this strictly for poudriere?6- How should the output be handled? > Date: Sat, 7 Nov 2015 00:28:28 -0800 > Subject: Call for Help: need script for patching ports tree, building with > poudriere > From: rodr...@freebsd.org > To: freebsd-test...@freebsd.org; freebsd-ports@freebsd.org > > Hi, > > I've been working on some advanced scripting with Eitan Adler. > We are interested in experimenting with integrating Jenkins + Phabricator > using: https://wiki.jenkins-ci.org/display/JENKINS/Phabricator+Plugin > For starters, we want to see what we can accomplish with ports. > > Can someone provide a script that does the following: > > (1) Takes a patch file > (2) Applies the patch file to a checked out ports tree > (3) If patching fails, quit and report an error > (4) If patch succeeds, do a simple guess to figure out which ports were > affected > (5) Create a file build.ports.txt which lists these ports, and can be used > as input > to poudriere, by invoking: > > poudriere bulk -f build.ports.txt > > (6) In addition, run portlint, port test, and any other appropriate > scripts to > test that the patched ports following the porting style guidelines. > > For example, if the patch in this review was submitted: > https://reviews.freebsd.org/D3791 > then a build.ports.txt file with this content would be created: > > > databases/py-Pyrseas > databases/py-pylibmc > databases/py-redis > deskutils/py-bugwarrior > deskutils/py-taskw > devel/py-Jinja2 > devel/py-TGScheduler > devel/py-apscheduler > devel/py-asn1 > devel/py-asyncio > devel/py-biplist > devel/py-check-manifest > devel/py-circuits > devel/py-dateutil > devel/py-doit > devel/py-fabric > devel/py-filemagic > devel/py-foolscap > devel/py-freezegun > devel/py-future > devel/py-lazy > devel/py-logan > devel/py-mock > devel/py-nose > devel/py-phabricator > devel/py-pip > devel/py-protobuf > devel/py-pyflakes > devel/py-pygit2 > devel/py-pygithub > devel/py-pytest-cache > devel/py-pytest > devel/py-python-bugzilla > devel/py-sanetime > devel/py-scripttest > devel/py-semantic_version > devel/py-setuptools > devel/py-simplejson > devel/py-tox > devel/py-twiggy > devel/py-tzlocal > devel/py-virtualenv > finance/py-stripe > ftp/py-pyftpdlib > math/py-graphillion > math/py-pycosat > net/py-beanstalkc > net/py-eventlet > net/py-netaddr > net/py-oauth2 > net/py-pynsq > net/py-pyzmq > net/py-twitter-tools > net/turses > science/py-h5py > security/py-cryptography > security/py-ecdsa > security/py-libnacl > security/py-oauthlib > security/py-openssl > security/py-pycrypto > security/py-pysha3 > sysutils/py-nagiosplugin > sysutils/py-supervisor > textproc/py-diff-match-patch > textproc/py-mistune > textproc/py-transifex-client > textproc/py-wtforms > www/geeknote > www/py-aiohttp > www/py-bleach > www/py-cactus > www/py-django-contrib-comments > www/py-django-mezzanine > www/py-feedgenerator > www/py-flask-wtf > www/py-flexget > www/py-gandi.cli > www/py-grequests > www/py-gunicorn > www/py-pelican > www/py-praw > www/py-pyjwt > www/py-rackspace-monitoring > www/py-requests-oauthlib > www/py-requests > www/py-slimit > www/py-slumber > > and poudriere would be invoked to build those ports. > > Does such a script exist? > > If not, would someone by interested in working on such a script, and > providing it > via GitHub at https://github.com/freebsd/freebsd-ci/ ? > > Thanks. > > -- > Craig > ___ > 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" ___ 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: libreoffice-4.3.7
I am using libreoffice 4.3.7 and the port built fine yesterday on FreeBSD. Try recreating the port tree. Date: Thu, 11 Jun 2015 16:40:44 -0400 From: ppathia...@atlantisservices.net To: off...@freebsd.org Subject: FreeBSD Port: libreoffice-4.3.7 CC: po...@freebsd.org Crash and burn? Hi, I was just running Libreoffice via pkgs on PCBSD 10.x It seems that 4.3.7 is no longer backward compatible? It just hangs when trying to start. So, I built it manually and it looks like it won't build any more. When I try to build libreoffice: [root@desktop4] /usr/ports/editors/libreoffice# make === libreoffice-4.3.7 depends on package: p5-Archive-Zip=0 - found === libreoffice-4.3.7 depends on executable: zip - found === libreoffice-4.3.7 depends on file: /usr/local/lib/libboost_regex.a - found === libreoffice-4.3.7 depends on file: /usr/local/libdata/pkgconfig/cppunit.pc - found === libreoffice-4.3.7 depends on executable: dmake - found === libreoffice-4.3.7 depends on file: /usr/local/bin/gperf - found === libreoffice-4.3.7 depends on package: mdds=0.9.0 - found === libreoffice-4.3.7 depends on executable: gpatch - found === libreoffice-4.3.7 depends on executable: ucpp - found === libreoffice-4.3.7 depends on executable: vigra-config - found === libreoffice-4.3.7 depends on file: /usr/local/include/glm/glm.hpp - found === libreoffice-4.3.7 depends on executable: bash - found === libreoffice-4.3.7 depends on executable: gsed - found === libreoffice-4.3.7 depends on executable: ant - found === libreoffice-4.3.7 depends on file: /usr/local/share/java/classes/junit.jar - not found ===Verifying install for /usr/local/share/java/classes/junit.jar in /usr/ports/java/junit === Building for junit-4.11_1 Buildfile: /usr/ports/java/junit/work/junit-team-junit-c62e2df/build.xml [taskdef] Could not load definitions from resource net/sf/antcontrib/antcontrib.properties. It could not be found. clean: [delete] Deleting directory /usr/ports/java/junit/work/junit-team-junit-c62e2df/junit4.11-SNAPSHOT [delete] Deleting directory /usr/ports/java/junit/work/junit-team-junit-c62e2df/target init: versiontag: [copy] Copying 1 file to /usr/ports/java/junit/work/junit-team-junit-c62e2df/src/main/java/junit/runner build: [mkdir] Created dir: /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main [javac] Compiling 164 source files to /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.5 [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 1 warning [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/runner/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/junit/framework/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/internal/runners/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/runners/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/matchers/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/junit/extensions/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/runner/notification/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/junit/runner/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/runner/manipulation/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/junit/textui/package-info.class [javac] Creating empty /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main/org/junit/internal/requests/package-info.class [unjar] Expanding: /usr/ports/java/junit/work/junit-team-junit-c62e2df/lib/hamcrest-core-1.3.jar into /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/main [mkdir] Created dir: /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/test/java [javac] Compiling 163 source files to /usr/ports/java/junit/work/junit-team-junit-c62e2df/target/test/java [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.5 [javac] Note: Some input files use or override a deprecated API. [javac] Note:
