FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, 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 +-+ lang/js_of_ocaml| 2.5 | 2.8.4 +-+ multimedia/obs-studio | 17.0.0 | 17.0.1 +-+ net/abills | 0.59| 0.75 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: recent change to vim defaults?
I have to put mouse=v to get the behavior I am used to. Best Sent from TypeApp On Jan 18, 2017, 08:46, at 08:46, Julian Elischer wrote: >On 17/01/2017 12:07 AM, ohauer wrote: >> I suspect you mean the /usr/local/etc/vim/vimrc and gvimrc files. >> That was the first place I've tried to overwrite it, but without >> luck (even with set mouse=) but it works in ~/.vimrc > >what to put IN the file? >> >> -- >> olli >> -- >> send with broken GMX mailer client, sorry for tofu and html scrap >> On 15/01/2017, 22:48 Benjamin Kaduk wrote: >> >> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: >> > I noticed that suddenly vim is grabbing mouse movements, which >> makes >> > life really hard. >> > >> > Was there a specific revision that brought in this change, and >> can it >> > be removed? >> >> I remember seeing something go by during an upgrade somewhat >> recently >> about there now being a defaults file that gets used when a user >> does >> not specify a .vimrc. Unfortunately, I don't remember whether I >saw >> that notice on a FreeBSD machine or a Debian one, and haven't >> been able >> to find the notice I remember through searching some likely >places. >> >> Just to check: do you have a .vimrc file in place already? >> >not yet. >when I work out what to put into it I will make it. > >> >> -Ben >> ___ >> freebsd-curr...@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-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" ___ 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: net/boinc-client: make LINUX option a default or Slave port?
On Tue, Jan 17, 2017 at 11:41 PM, Larry Rosenman wrote: > On 2017-01-17 16:31, Manfred Antar wrote: > >> >> I've been running a freebsd compiled seti version 8 here for months. >> I think someone needs to update the port. >> >> i put the precomiled binaries on my website at : >> >> www.pozo.com/seti [1] >> >> this is for current amd64 >> seti-pkg.tar.bz2 -- precompiled >> >> setiathome.tar.bz -- the source trees for boinc and seti current -- I will >> update this in about 20 minutes so wait a bit before downloading >> >> I've been using this since last summer and works fine. a linux port would be >> nice but > > How did you compile the sources? (Can you send me in private mail the > Makefile, etc?) FWIW, the sources that Manfred put up compiled with the instructions in the INSTALL file, except that you have to use gmake instead of make. So $ MAKE=/usr/local/bin/gmake ./_autosetup $ ./configure --disable-server $ gmake I just did that on FreeBSD 10.3-stable about a week and a half ago. tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 10.3-STABLE FreeBSD 10.3-STABLE #0 r310083: Wed Dec 14 21:00:13 CET 2016 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 (FYI, I also tested the compile on machine running FreeBSD 8.3 from June 2013 but that compile failed) I haven't done anything with the compiled binaries yet (had to upgrade my BOINC machine first) but I expect that they will work well. Also, I would prefer that the boinc port did NOT depend on / bring in linux_base, but if it does I can live with it. -- Regards, Torfinn Ingolfsen ___ 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: Any plans to update Mythtv port to 0.28?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216237 please, try this update patch (and tell me if something not working as expected). ___ 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: net/boinc-client: make LINUX option a default or Slave port?
On 2017-01-18 09:57, Torfinn Ingolfsen wrote: On Tue, Jan 17, 2017 at 11:41 PM, Larry Rosenman wrote: On 2017-01-17 16:31, Manfred Antar wrote: I've been running a freebsd compiled seti version 8 here for months. I think someone needs to update the port. i put the precomiled binaries on my website at : www.pozo.com/seti [1] this is for current amd64 seti-pkg.tar.bz2 -- precompiled setiathome.tar.bz -- the source trees for boinc and seti current -- I will update this in about 20 minutes so wait a bit before downloading I've been using this since last summer and works fine. a linux port would be nice but How did you compile the sources? (Can you send me in private mail the Makefile, etc?) FWIW, the sources that Manfred put up compiled with the instructions in the INSTALL file, except that you have to use gmake instead of make. So $ MAKE=/usr/local/bin/gmake ./_autosetup $ ./configure --disable-server $ gmake I just did that on FreeBSD 10.3-stable about a week and a half ago. tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 10.3-STABLE FreeBSD 10.3-STABLE #0 r310083: Wed Dec 14 21:00:13 CET 2016 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 (FYI, I also tested the compile on machine running FreeBSD 8.3 from June 2013 but that compile failed) I haven't done anything with the compiled binaries yet (had to upgrade my BOINC machine first) but I expect that they will work well. Also, I would prefer that the boinc port did NOT depend on / bring in linux_base, but if it does I can live with it. I'm working on making Manfred's sources used in the port, and will *NOT* be flipping the LINUX option. I'll be pushing an update for net/boinc-client soon. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ 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"
standard settings for ports.
I know there are some standard setting one can set.. make ports shows 8 but I know there are many more. like what version of perl you want to use throughout your system or whether you want to use openssl from ports or system or what version of python.. or whether to use some version of gcc or ... Is there a list somewhere as to where all these are found? for example setting NO-X11-yes (or someting like that) things I'd like to turn off include DOCS, EXAMPLES, MAN, X11, Also I'd like to specify that I'd like everything to try use python 2.7 and jdk8 can I set the USES stuff from the command line?(no?) pointers appreciated... Julian ___ 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: standard settings for ports.
On Thu, 19 Jan 2017 01:25+0800, Julian Elischer wrote: > pointers appreciated... Try something like this in /etc/make.conf: DEFAULT_VERSIONS=apache=2.4 bdb=6 firebird=2.5 gcc=4.9 ghostscript=9 lua=5.2 mysql=5.7 perl5=5.22 php=5.6 pgsql=9.5 python=2.7 python2=2.7 python3=3.5 ruby=2.2 ssl=openssl tcltk=8.6 -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++ ___ 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: recent change to vim defaults?
On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? This change appeared in one of the last patchset of vim 7.4 and was one of the "features" of the vim 8.0 release. I do agree this is just totally painful :( Best regards, Bapt One of the things that I inherited with the Vim port was the DEFAULT_VIMRC option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't touched it. I have moused disabled in all my boxes so I have no idea about bad mouse behaviour in Vim. If there is a bad default that is causing grief, let's just fix it in that default vimrc. I'm not really understanding what the unexpected behaviour is so I can't make an intelligent recommendation myself, but I'll go with whatever you folks suggest. # Adam I'm in iterm on my mac. I ssh to a freebsd machine I use vim on a file. I used to be able to use the mouse on my mac to copy a few lines into the cut buffer.. slide-shift-click etc.. now suddenly if I try highlight some code in vim to copy it vim drags stuff around, scrolls up and down, deletes stuff and generally makes a mess. if click, instead of starting a copy zone it grabs some of the text. basically it makes hte mouse useless. I can;t copy and paste from a file I'm ediitng. I end up having to exit vim and do it in vi. ___ 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: recent change to vim defaults?
> On 18 Jan, 2017, at 10:35, Julian Elischer wrote: > > On 17/01/2017 1:23 AM, Adam Weinberger wrote: >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: >>> >>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? >>> This change appeared in one of the last patchset of vim 7.4 and was one of >>> the >>> "features" of the vim 8.0 release. >>> >>> I do agree this is just totally painful :( >>> >>> Best regards, >>> Bapt >> One of the things that I inherited with the Vim port was the DEFAULT_VIMRC >> option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't >> touched it. >> >> I have moused disabled in all my boxes so I have no idea about bad mouse >> behaviour in Vim. If there is a bad default that is causing grief, let's >> just fix it in that default vimrc. >> >> I'm not really understanding what the unexpected behaviour is so I can't >> make an intelligent recommendation myself, but I'll go with whatever you >> folks suggest. >> >> # Adam > I'm in iterm on my mac. > I ssh to a freebsd machine > I use vim on a file. > I used to be able to use the mouse on my mac to copy a few lines into the cut > buffer.. slide-shift-click etc.. > now suddenly if I try highlight some code in vim to copy it vim drags stuff > around, scrolls up and down, deletes stuff and generally makes a mess. > if click, instead of starting a copy zone it grabs some of the text. > > basically it makes hte mouse useless. > I can;t copy and paste from a file I'm ediitng. I end up having to exit vim > and do it in vi. There have been a number of recommendations in this thread for you, Julian, including "set mouse=a" and "set mouse=v". Test some of them out and let me know what works for you. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.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: recent change to vim defaults?
On Wed, Jan 18, 2017 at 10:37:32AM -0700, Adam Weinberger wrote: > > On 18 Jan, 2017, at 10:35, Julian Elischer wrote: > > > > On 17/01/2017 1:23 AM, Adam Weinberger wrote: > >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: > >>> > >>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: > I noticed that suddenly vim is grabbing mouse movements, which makes life > really hard. > > Was there a specific revision that brought in this change, and can it be > removed? > >>> This change appeared in one of the last patchset of vim 7.4 and was one > >>> of the > >>> "features" of the vim 8.0 release. > >>> > >>> I do agree this is just totally painful :( > >>> > >>> Best regards, > >>> Bapt > >> One of the things that I inherited with the Vim port was the DEFAULT_VIMRC > >> option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't > >> touched it. > >> > >> I have moused disabled in all my boxes so I have no idea about bad mouse > >> behaviour in Vim. If there is a bad default that is causing grief, let's > >> just fix it in that default vimrc. > >> > >> I'm not really understanding what the unexpected behaviour is so I can't > >> make an intelligent recommendation myself, but I'll go with whatever you > >> folks suggest. > >> > >> # Adam > > I'm in iterm on my mac. > > I ssh to a freebsd machine > > I use vim on a file. > > I used to be able to use the mouse on my mac to copy a few lines into the > > cut buffer.. slide-shift-click etc.. > > now suddenly if I try highlight some code in vim to copy it vim drags stuff > > around, scrolls up and down, deletes stuff and generally makes a mess. > > if click, instead of starting a copy zone it grabs some of the text. > > > > basically it makes hte mouse useless. > > I can;t copy and paste from a file I'm ediitng. I end up having to exit vim > > and do it in vi. > > There have been a number of recommendations in this thread for you, Julian, > including "set mouse=a" and "set mouse=v". Test some of them out and let me > know what works for you. set mouse= (with nothing) brings back the original behaviour Bapt signature.asc Description: PGP signature
Re: recent change to vim defaults?
On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really work for me. vim is still taking mouse events ___ 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: recent change to vim defaults?
mouse=n ? On 18/01/2017 18:01, Julian Elischer wrote: On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really work for me. vim is still taking mouse events ___ 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"
FreeBSD Port: relayd-5.5.20140810_2
Dear Martin, Are you still maintaining the relayd port? If yes, could you please sync the port to the latest OpenBSD version?? In the meantime, thank you so much for your work and attention. Kind regards Albert Gabàs ___ 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"
poudriere: devel/llvm39: runaway_process
My poudriere build servers have been unable to build devel/llvm39 ever since some ports changed from llvm37 (January 17th?) The error is runaway_process and this happens during the package phase. It looks like pkg-static spins for one hour at which point poudriere gives up on it. Yesterday I raised max_execution_time for package on one build server to 2 hours which did not help. My three servers are all at 10.3-RELEASE-p16 and I'm attempting to build packages for the same version. I'm still able to build llvm37 ok. Since it takes ~2 hours for the failure to occur I'm hoping for ideas on how to diagnose this. 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: standard settings for ports.
On 19/01/2017 1:28 AM, Trond Endrestøl wrote: On Thu, 19 Jan 2017 01:25+0800, Julian Elischer wrote: pointers appreciated... Try something like this in /etc/make.conf: DEFAULT_VERSIONS=apache=2.4 bdb=6 firebird=2.5 gcc=4.9 ghostscript=9 lua=5.2 mysql=5.7 perl5=5.22 php=5.6 pgsql=9.5 python=2.7 python2=2.7 python3=3.5 ruby=2.2 ssl=openssl tcltk=8.6 that's good but where is it documented? thanks anyway! ___ 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: recent change to vim defaults?
On 19/01/2017 1:37 AM, Adam Weinberger wrote: On 18 Jan, 2017, at 10:35, Julian Elischer wrote: On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? This change appeared in one of the last patchset of vim 7.4 and was one of the "features" of the vim 8.0 release. I do agree this is just totally painful :( Best regards, Bapt One of the things that I inherited with the Vim port was the DEFAULT_VIMRC option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't touched it. I have moused disabled in all my boxes so I have no idea about bad mouse behaviour in Vim. If there is a bad default that is causing grief, let's just fix it in that default vimrc. I'm not really understanding what the unexpected behaviour is so I can't make an intelligent recommendation myself, but I'll go with whatever you folks suggest. # Adam I'm in iterm on my mac. I ssh to a freebsd machine I use vim on a file. I used to be able to use the mouse on my mac to copy a few lines into the cut buffer.. slide-shift-click etc.. now suddenly if I try highlight some code in vim to copy it vim drags stuff around, scrolls up and down, deletes stuff and generally makes a mess. if click, instead of starting a copy zone it grabs some of the text. basically it makes hte mouse useless. I can;t copy and paste from a file I'm ediitng. I end up having to exit vim and do it in vi. There have been a number of recommendations in this thread for you, Julian, including "set mouse=a" and "set mouse=v". Test some of them out and let me know what works for you. actually I never saw one about mouse=a however I did see and try mouse=v which didn't work for me. I have now tried mouse=a and am happy to say that that does what I need. thanks! # Adam ___ 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: recent change to vim defaults?
On 19/01/2017 11:18 AM, Julian Elischer wrote: On 19/01/2017 1:37 AM, Adam Weinberger wrote: On 18 Jan, 2017, at 10:35, Julian Elischer wrote: On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? This change appeared in one of the last patchset of vim 7.4 and was one of the "features" of the vim 8.0 release. I do agree this is just totally painful :( Best regards, Bapt One of the things that I inherited with the Vim port was the DEFAULT_VIMRC option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't touched it. I have moused disabled in all my boxes so I have no idea about bad mouse behaviour in Vim. If there is a bad default that is causing grief, let's just fix it in that default vimrc. I'm not really understanding what the unexpected behaviour is so I can't make an intelligent recommendation myself, but I'll go with whatever you folks suggest. # Adam I'm in iterm on my mac. I ssh to a freebsd machine I use vim on a file. I used to be able to use the mouse on my mac to copy a few lines into the cut buffer.. slide-shift-click etc.. now suddenly if I try highlight some code in vim to copy it vim drags stuff around, scrolls up and down, deletes stuff and generally makes a mess. if click, instead of starting a copy zone it grabs some of the text. basically it makes hte mouse useless. I can;t copy and paste from a file I'm ediitng. I end up having to exit vim and do it in vi. There have been a number of recommendations in this thread for you, Julian, including "set mouse=a" and "set mouse=v". Test some of them out and let me know what works for you. actually I never saw one about mouse=a however I did see and try mouse=v which didn't work for me. I have now tried mouse=a and am happy to say that that does what I need. thanks! actually no, 'set mouse=' seems to be what I want.. not sure why I thought =a worked: # Adam ___ freebsd-curr...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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: poudriere: devel/llvm39: runaway_process
On 19/01/2017 5:49 AM, Craig Leres wrote: My poudriere build servers have been unable to build devel/llvm39 ever since some ports changed from llvm37 (January 17th?) The error is runaway_process and this happens during the package phase. It looks like pkg-static spins for one hour at which point poudriere gives up on it. Yesterday I raised max_execution_time for package on one build server to 2 hours which did not help. My three servers are all at 10.3-RELEASE-p16 and I'm attempting to build packages for the same version. I'm still able to build llvm37 ok. Since it takes ~2 hours for the failure to occur I'm hoping for ideas on how to diagnose this. mine build both yesterday for some reason (both succeeded) 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: poudriere: devel/llvm39: runaway_process
On 19/01/2017 5:49 AM, Craig Leres wrote: My poudriere build servers have been unable to build devel/llvm39 ever since some ports changed from llvm37 (January 17th?) The error is runaway_process and this happens during the package phase. It looks like pkg-static spins for one hour at which point poudriere gives up on it. Yesterday I raised max_execution_time for package on one build server to 2 hours which did not help. My three servers are all at 10.3-RELEASE-p16 and I'm attempting to build packages for the same version. llvm-39 took arond 45 minutes more than 37 on my machine. I'm still able to build llvm37 ok. Since it takes ~2 hours for the failure to occur I'm hoping for ideas on how to diagnose this. 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: poudriere: devel/llvm39: runaway_process
On 1/19/17, Craig Leres wrote: > My poudriere build servers have been unable to build devel/llvm39 ever > since some ports changed from llvm37 (January 17th?) The error is > runaway_process and this happens during the package phase. It looks like > pkg-static spins for one hour at which point poudriere gives up on it. > Yesterday I raised max_execution_time for package on one build server to > 2 hours which did not help. My three servers are all at > 10.3-RELEASE-p16 and I'm attempting to build packages for the same version. > > I'm still able to build llvm37 ok. Since it takes ~2 hours for the > failure to occur I'm hoping for ideas on how to diagnose this. > Well, I'm not sure about the error (mine builds fine), but as a helping note, maybe passing `-i` option to `poudriere testport` helps you go into the jail after the fail, then no need to rebuild all things after fail 😁😄😊 simply change and make. However sometimes in some cases this approach fails, but generally I can say it works (for reducing test/fix time). ___ 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"
jdk7 broken in some way?
last night I had poudriere try build jdk8 but that required jdk7 which didn't build. I think itwanted jdk6 or maybe bootstrap-openjdk. whatever it needed (it said it couldn't make a java vm) it didn't do it. I thought poudriere would set up everything needed.. Is there anything special needed to compile the jdk? I got my jdk8 by dropping a jdk7 package into the packages area. but such manual intervention shouldn't be needed... ___ 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: standard settings for ports.
On Thu, 19 Jan 2017 11:13+0800, Julian Elischer wrote: > On 19/01/2017 1:28 AM, Trond Endrestøl wrote: > > On Thu, 19 Jan 2017 01:25+0800, Julian Elischer wrote: > > > > > pointers appreciated... > > Try something like this in /etc/make.conf: > > > > DEFAULT_VERSIONS=apache=2.4 bdb=6 firebird=2.5 gcc=4.9 ghostscript=9 lua=5.2 > > mysql=5.7 perl5=5.22 php=5.6 pgsql=9.5 python=2.7 python2=2.7 python3=3.5 > > ruby=2.2 ssl=openssl tcltk=8.6 > > > that's good but where is it documented? Have a look at /usr/ports/Mk/bsd.default-versions.mk. Also, if you like to force emacs to be without X11, you should also set EMACS_PORT_NAME=emacs-nox11, see /usr/ports/Mk/bsd.emacs.mk. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++ ___ 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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, 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 +-+ math/giacxcas | 1.2.2-57| 1.2.3-13 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"
