Re: No update for a day on ports?

Hi, On 4/2/21 9:44 AM, The Doctor via freebsd-ports wrote: Then the question is : Moving forward, how do we update the ports? There are a number of ways. You can use the prebuilt git package or one of it's variants or substitutes. If you prefer to build git yourself, you can use the

Re: Removing sysutils/polkit dependency from sysutils/libudisks?

Hi, On 1/17/21 3:17 AM, Kurt Jaeger wrote: Hi! Can you tell us the reason behind this opinion ? Is it generally buggy, does polkit violate some general design policy for apps etc ? * There's one part of polkit, pkexec, which is suid and linked to some libs that really aren't designed to be

Re: Removing sysutils/polkit dependency from sysutils/libudisks?

Hi, On 1/15/21 5:45 AM, Pau Amma wrote: Several months ago, someone (swills@ IIRC) asked me to look into removing the sysutils/polkit dependency from sysutils/libudisks which I maintain. I just had a chance to look at that request and it would require at least removing the udisksctl utility

Re: Github redirects for go based ports seems to be not working as expected

Hi, On 10/22/20 9:51 AM, Matthias Fechner wrote: Does anyone have an idea why ports cannot download the old version but must use the one with renamed group and project? Probably some GitHub internal issue with the codeload.github.com site. Probably not much we can do except update the URLs.

Re: Fwd: ports Makefile for gitlab subdirs

Hi, On 9/7/20 12:28 PM, MR wrote: Hi, I want to migrate the kicad-devel port from github to gitlab. How should one handle the case if - like kicad - the project contains subgroups:   like https://gitlab.com/kicad/code/kicad.git Specifying: GL_ACCOUNT= kicad GL_PROJECT= code/kicad

Re: [HEADS UP] Planned deprecation of portsnap

Hi, On 8/10/20 9:28 AM, Lars Engels wrote: On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote: I'm probably fine with this and I think that all of the (now) supported methods have pros and cons. To leverage the UX flaws of git and svn(lite) compared to portsnap having a wrapper script

Re: [HEADS UP] Planned deprecation of portsnap

Hi, On 8/7/20 6:19 AM, Michael Gmelin wrote: On Fri, 7 Aug 2020 01:24:00 -0400 Steve Wills wrote: Hi, [snip] 2. Use svnlite to checkout a ports tree. (There will be git -> svn replication. Will this be a long-term option? I don't know yet exactly how long the git to svn migrat

Re: [HEADS UP] Planned deprecation of portsnap

Hi, On 8/5/20 6:17 PM, Michael Gmelin wrote: What will be the process to bootstrap git? There are several options: 1. Install the git package provided by the FreeBSD project 2. Use svnlite to checkout a ports tree. (There will be git -> svn replication. 3. Download a tar of the ports

Re: [HEADS UP] Planned deprecation of portsnap

Hi, On 8/5/20 12:31 PM, Ernie Luzar wrote: I seems this is a done deal as changes are already being done now. So the real question is, when is the portsnap utility going to be removed from the base system? Will it happen in 12.2 or 13.0? Full removal may not happen before 13.0 but

Git migration - was Re: [HEADS UP] Planned deprecation of portsnap

Hi, On 8/5/20 5:42 AM, Yasuhiro KIMURA wrote: From: Kurt Jaeger Subject: Re: [HEADS UP] Planned deprecation of portsnap Date: Wed, 5 Aug 2020 06:40:39 +0200 There's a list where the git topic is discussed: https://lists.freebsd.org/pipermail/freebsd-git/ Have a look at the archive, and

[HEADS UP] Planned deprecation of portsnap

We are planning to deprecate use of portsnap in ports. The reasons are as follows (in no particular order): * Portsnap doesn't support quarterly branches, even years after quarterly branches were created and changed to the default for non-HEAD packages. * Portsnap doesn't seem to save

Re: FreeBSD Port: purple-discord-g20200802

Hi, On 8/3/20 7:52 AM, Alex V. Petrov wrote: ===>>> Building the port required 2 seconds ===> Staging for purple-discord-g20200802 ===> Generating temporary packing list gmake[1]: Entering directory '/usr/ports/net-im/purple-discord/work/purple-discord-8fd7ceb' convert -strip -background

Re: FreeBSD Port: openblas-0.3.7_1,1 error install

Hi, On 1/31/20 6:31 PM, Alex V. Petrov wrote: and other machine: -rw-r--r-- 1 root wheel 30159104 1 февр. 06:28 /usr/local/lib/libopenblas_penrynp-r0.3.7.a -rwxr-xr-x 1 root wheel 14597176 1 февр. 06:29 /usr/local/lib/libopenblas_penrynp-r0.3.7.so lrwxr-xr-x 1 root wheel28 1

Re: FreeBSD Port: openblas-0.3.7_1,1 error install

Hi, On 1/31/20 5:47 PM, ajtiM via freebsd-ports wrote: ls -al /usr/local/lib/libopenblas* -rw-r--r-- 1 root wheel 32273330 Jan 31 10:45 /usr/local/lib/libopenblas_nehalemp-r0.3.7.a -rwxr-xr-x 1 root wheel 15492200 Jan 31 10:45 /usr/local/lib/libopenblas_nehalemp-r0.3.7.so lrwxr-xr-x 1

Re: FreeBSD Port: openblas-0.3.7_1,1 error install

Hi, On 1/31/20 11:42 AM, ajtiM wrote: On Fri, 31 Jan 2020 10:01:42 -0500 Steve Wills wrote: Hi, On 1/30/20 9:25 PM, Alex V. Petrov wrote: ===> Installing for openblas-0.3.7_1,1 ===> Checking if openblas is already installed ===> Registering installation for openblas-0.3.

Re: FreeBSD Port: openblas-0.3.7_1,1 error install

Hi, On 1/30/20 9:25 PM, Alex V. Petrov wrote: ===> Installing for openblas-0.3.7_1,1 ===> Checking if openblas is already installed ===> Registering installation for openblas-0.3.7_1,1 pkg-static: Unable to access file

Re: How to best check a configuration of another port/package?

Hi, On 6/9/19 11:48 AM, Adam Weinberger wrote: No, you're absolutely right. Flavours is the right way to do it now. I keep forgetting about them, because I don't in any way understand how to use them. Hmm, flavors have to be something that can be installed in parallel, right? How does that

Re: New pkg audit FNs

Hi, On 10/09/2017 17:55, Jan Beich wrote: Steve Wills <swi...@freebsd.org> writes: Hi, On 10/09/2017 16:34, Jan Beich wrote: Matthew Seaman <matt...@freebsd.org> writes: On 09/10/2017 16:57, Roger Marquis wrote: Can anyone say what mechanisms the ports-security team might h

Re: New pkg audit FNs

Hi, On 10/09/2017 16:34, Jan Beich wrote: Matthew Seaman writes: On 09/10/2017 16:57, Roger Marquis wrote: Can anyone say what mechanisms the ports-security team might have in place to monitor CVEs and port software versions? I've been hacking at a prototype for

Re: Blender and opencv2-core

Hi, On 07/23/2017 15:57, Herbert J. Skuhra wrote: Grzegorz Junka skrev: On 23/07/2017 12:42, Grzegorz Junka wrote: I am getting the following error when setting up blender dependencies in poudriere: ===> Setting user-specified options for blender-2.78c_3 and dependencies blender-2.78c_3:

Re: situation with www/node6 and www/node

Can execjs work with node6? What else would have to change to get it all onto node6? Steve On 05/18/2017 13:22, Joseph Mingrone wrote: > Hello, > > I am hitting an issue where the conflicting www/node6 and www/node > packages are attempting to be installed together. For example, the > upcoming

[CFT] emulators/open-vm-tools{,-nox11} update to 10.1.5

Hello Everyone, It's that time again, time to test another open-vm-tools update. Everything is in basically the same place as last time. The patch is here: https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.5.diff Note there are a good number of patches being renamed, so be

Re: Packaging Go Libs

, so I'll go ahead with this plan. Thanks, Steve On 04/18/2017 10:24, Julien Laffaye wrote: > I agree with you. > Maybe we should provide helpers to do the "fetching dependencies" part so > that will be less cumbersome. > > On Mon, Apr 17, 2017 at 4:20 PM, Steve Wil

Packaging Go Libs

Hi, I'd like to propose eliminating packaging of Go libs. Almost every Go app is developed with a different version of any given lib than what another Go app might use. Forcing a Go app to use a different version than what upstream might have chosen is error prone at best and likely to produce a

Re: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0

is looking at that. This is likely the final change before I commit this, which currently I plan to do on 3/15. So if you use it, now is your chance to test and report issues. Steve On 01/19/2017 16:59, Steve Wills wrote: > Hi, > > I'd like anyone possible to test an update

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 12:00, Franco Fichtner wrote: > > Let me try another way: > > Since pkg has feature macros for building correctly on different > FreeBSD versions, namely 10.0, 10.1, 10.2 and 10.3, the way to > provide binaries without missing symbols is to build pkg with a > fixed set of

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 11:44, Miroslav Lachman wrote: > Why don't add some check in to "pkg" to deny (or warn user) upgrade or > install on unsupported / EOLed system? > Just check version on current system against some metadata info in > repository. I would be happy to see a patch that showed how

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 11:24, Franco Fichtner wrote: > >> On 9 Feb 2017, at 5:21 PM, Steve Wills <swi...@freebsd.org> wrote: >> >> We provide backwards compatibility, not forwards compatibility. > > But don't you see that users won't know this? Users who don't

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 11:14, Franco Fichtner wrote: > > You're contradicting yourself here. Either it's compatible or it isn't? > Not at all. There's a difference between backwards compatibility (binary built on older release works on newer release) and forwards compatibility (binary built on

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 11:01, Franco Fichtner wrote: > >> On 9 Feb 2017, at 4:47 PM, Steve Wills <swi...@freebsd.org> wrote: >> >> They're supposed to upgrade to a supported version of FreeBSD. > > pkg won't refuse the upgrade. And at least if it upgraded, it

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 10:30, Franco Fichtner wrote: > Hi Steve, > >> On 9 Feb 2017, at 4:09 PM, Steve Wills <swi...@freebsd.org> wrote: >> >> Ports and packages are maintained on the assumption that the user is >> using a supported version of the OS. We didn't de

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/09/2017 03:55, Franco Fichtner wrote: > >> On 9 Feb 2017, at 9:49 AM, Kirill Ponomarev wrote: >> >> I don't understand all critics I see in this thread and in your mail, >> the fate of this project is all in your hands - try to contribute more, > > I'm going to stop

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi, On 02/08/2017 12:34, scratch65...@att.net wrote: > > I *did* check for bug reports. I did a search on "utimenstat" > and found exactly one, which had been withdrawn as not being a > bug. > > But it *is* a bug. It's a bug on several levels, the most > significant of which is that the

Re: ports and dependency hell

Hi Julian, On 02/07/2017 13:03, Julian Elischer wrote: > This is a serious post on a serious issue that ports framework people > seem unaware of. To be honest, it's kind of a confusing post, at least to me. > It' getting too easy to get into dependency hell here (I've spent the > last week

Re: updating ruby

Hi, On 02/09/2017 09:55, Herbert J. Skuhra wrote: > > DEFAULT_VERSIONS+=ruby=2.3 Err, yeah, sorry, was too early for me... Thanks for the correction. Steve signature.asc Description: OpenPGP digital signature

Re: updating ruby

Hi, On 02/08/2017 11:20, Gerard Seibert wrote: > On or about 20170109, the default version of ruby was updated from 2.2 > to 2.3. However, "pkg install" wants to install version 2.2 for ports > that require ruby. Is there a way to override this behavior? > The packages are built from the

Re: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0

Hi, On 01/21/2017 09:13, Kurt Jaeger wrote: > Hi! > >> I'd like anyone possible to test an updated version of >> emulators/open-vm-tools{,-nox11}. I have the patch here for those who >> wish to build themselves: >> >> https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.0.diff >

Re: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0

Hi, On 01/22/2017 07:26, Julian Elischer wrote: > A bug problem I had with the previous version is the huge fanout of > dependencies. > > it was all OK until we hit libglib2, after which we ended up having to > install all sorts of things. > > I'm guessing there was not much you can do about

Re: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0

Hi, On 01/20/2017 10:14, Julian Elischer wrote: > On 20/01/2017 5:59 AM, Steve Wills wrote: >> Hi, >> >> I'd like anyone possible to test an updated version of >> emulators/open-vm-tools{,-nox11}. I have the patch here for those who >> wish to build th

[CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0

Hi, I'd like anyone possible to test an updated version of emulators/open-vm-tools{,-nox11}. I have the patch here for those who wish to build themselves: https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.0.diff And for those who wish to test using packages, I've built

Re: Porting a Go implementation: dealing with dependencies

Hi, On 11/18/2016 10:35, Stefan Bethke wrote: > I’m trying to create a port for Gitea > (https://github.com/go-gitea/gitea). The basics seem easy enough, but > I’m not sure how to deal with it’s dependencies. Use the GH_* macros to fetch them. See:

Re: FreeBSD Port: consul-0.7.1

d "consul -v" is correctly showing v0.7.1, but > now the "Build" column in the output of "consul members" is just blank. > > Douglas William Thrift > <http://douglasthrift.net/> > > On 11/12/2016 3:41 PM, Steve Wills wrote: >> Fixed, th

Re: FreeBSD Port: consul-0.7.1

Fixed, thanks for the heads up. Steve On 11/12/2016 12:29, Douglas Thrift wrote: > Hello, > > It looks like the new update to consul 0.7.1 is reporting its version as > "unknown-unknown" rather than "0.7.1". I'm guessing something changed in > the upstream build process. > > This shows up when

Re: Is there still broken lang/ruby23 ?

Yes, I haven't looked at it yet, but if you want to take a look, I'd welcome patches. Steve On 06/28/16 06:12 PM, KIRIYAMA Kazuhiko wrote: > Hi, > > Is there still broken lang/ruby23[1]. Or can build in latest > 11.0-* ? > > [1]

Re: Feedback needed: www/redmine Update

Hi, On 06/ 6/16 12:23 PM, Steve Wills wrote: > Hi, > > On 06/ 6/16 08:10 AM, Torsten Zuehlsdorff wrote: >> Aloha, >> >> The patch can be found here: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209938 >> > I updated the PR with a new patc

Re: Feedback needed: www/redmine Update

Hi, On 06/ 6/16 08:10 AM, Torsten Zuehlsdorff wrote: > Aloha, > > The patch can be found here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209938 > This doesn't work for me. There are 3 issues at least, perhaps more. In order of discovery: The nokogiri reference from the Gemfile in

Re: Feedback needed: www/redmine Update

Hi, On 06/ 6/16 06:26 AM, Torsten Zuehlsdorff wrote: > Hello, > > i wrote an update for www/redmine. It would be very nice if some more > people can test it, That's awesome, I'm glad to hear that, thanks for the work! I have an install of redmine that I could use for testing. Where is the

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

Hi, On 04/24/16 10:16 AM, Mark Millard wrote: > > For all the port update activity (including ruby) I used gcc49, > /etc/make.conf being: > > # more /etc/make.conf DEFAULT_VERSIONS+=perl5=5.22 > WRKDIRPREFIX=/usr/obj/portswork > WITH_DEBUG= > WITH_DEBUG_FILES= > MALLOC_PRODUCTION= > # > # >

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

> been marked as broken for powerpc64: lang/ruby21 , lang/ruby22 , and > lang/ruby23 all were so marked. (So I commented those marks out.) > > My build that upgraded from ruby21 to ruby22 went fine. > > === > Mark Millard > markmi at dsl-only.net > > On

Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains?

Hi, On 04/23/16 05:50 PM, Mark Millard wrote: > Recently a large block of ports (including lang/gcc6-devel) were > marked in their Makefiles with > >> BROKEN_powerpc64= Does not build > > > Does this only apply for use of gcc/g++ 4.2.1 or specific other > verions? If so that is not the

Swift programming language

Hi, I've been working on porting the Swift programming language. There's a port here: https://people.freebsd.org/~swills/swift.shar if folks would like to test it before I commit. The swiftpm component hasn't been ported yet, so you can't build native executables. Any feedback would be

default ruby version

Hi, Just FYI, baring any objections or major issues coming up, I plan to make Ruby 2.2 the default Ruby in the ports tree on March 1. Puppet users in particular probably want to migrate to sysutils/puppet4 or work on testing some sort of patch that makes puppet 3.x work with ruby 2.2 before

Re: Rubygem .js files fubar?

Hi, On 01/17/16 10:29 AM, Matthew Seaman wrote: > On 17/01/2016 06:33, Steve Wills wrote: >> On 01/17/16 12:57 AM, Steve Wills wrote: >>> >>> As for why the original file isn't deleted, I'm not sure. I don't see >>> this in my local tree, but I h

Re: Rubygem .js files fubar?

Hi, On 01/12/16 06:11 AM, Matthew Seaman wrote: > On 01/11/16 16:41, Matthew Seaman wrote: >> lucid-nonsense:...svn2git-2.3.2/rdoc/js:% ls -la >> total 140 >> drwxr-xr-x 2 matthew wheel576 Jan 11 16:20 ./ >> drwxr-xr-x 7 matthew wheel640 Jan 11 13:01 ../ >> -rw-r--r-- 1 matthew

Re: Rubygem .js files fubar?

On 01/17/16 12:57 AM, Steve Wills wrote: > > As for why the original file isn't deleted, I'm not sure. I don't see > this in my local tree, but I have some changes that may be masking it. > Oh, I wasn't seeing it because I was testing with Ruby 2.1 and it only happens w

Re: poudriere, Go and networking

Hi, On 12/11/2015 10:55, Malcolm Matalka wrote: > Piotr Florczyk writes: > >> W dniu 11.12.2015 o 15:36, Kurt Jaeger pisze: >>> Hi! >>> Recently I had to package couple of programs written in Go and godep is becoming the standard for dependency tracking in

Re: lang/gcc48 fails to build [on HEAD]

On 11/27/2015 08:42, Baptiste Daroussin wrote: > On Fri, Nov 27, 2015 at 02:24:05PM +0100, Tijl Coosemans wrote: >> On Fri, 27 Nov 2015 13:59:54 +0100 Baptiste Daroussin >> wrote: >>> On Tue, Nov 10, 2015 at 07:23:40PM +0100, Rainer Hurling wrote: I think I found the

Re: FreeBSD Port: syncthing-discosrv-0.0.0.2015092201

Hi, Yeah, I will try to do that this weekend. Of course, I wanted to do it last weekend, but was busy. Thanks for your patience. If you have a patch, I'll take a look. Steve On 11/05/2015 15:16, Sean wrote: > Hi swills > > Now that syncthing v0.12.0 is out any change you can update the port? >

Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

Hi, On 10/13/2015 09:21, Miroslav Lachman wrote: > > Hi Steve, > > A "skia" fixed crashes on mapy.cz and seznam.cz but from this time I got > random crashes of Firefox and Seamonkey (both with "skia"). Until this > change Seamonkey was happily runnig for a few weeks (system uptime 20 > days). I

Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

Hi, On 10/09/2015 03:38, Miroslav Lachman wrote: > Steve Wills wrote on 10/08/2015 21:55: >> Just to test, try setting gfx.canvas.azure.backends and >> gfx.content.azure.backends to skia in about:config and see if it still >> crashes. > > Hi Steve, > > I changed

Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

Hi, On 10/08/2015 10:25, Miroslav Lachman wrote: > Walter Schwarzenfeld wrote on 10/07/2015 00:35: >> Firefox 41.0.1 is out, give it a try. > > > > I tried it in VirtualBox - same crash as with older versions. > > In real host I got this (started ff from command line) > >> firefox > >

Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

Just to test, try setting gfx.canvas.azure.backends and gfx.content.azure.backends to skia in about:config and see if it still crashes. Steve On 10/08/2015 11:53, Steve Wills wrote: > Hi, > > On 10/08/2015 10:25, Miroslav Lachman wrote: >> Walter Schwarzenfeld wrote on 1

Re: FreeBSD Port: ruby20-2.0.0.645,1 - reported as vulnerable while it isn't ?

Hi, Did you build your own ports where ruby 2.0 was default? I see the package name here is ruby-2.0.0.645,1, not ruby20-2.0.0.645,1. The entries in vuxml look like this: 3326 nameruby20/name 3327 rangelt2.0.0.645,1/lt/range ... 3330 nameruby/name 3331

Re: proper DOXYGEN option default value

On Wed, Mar 04, 2015 at 02:41:48PM -0800, Don Lewis wrote: I maintain a number of ports that use doxygen to generate their documentation. They all list DOXYGEN in OPTIONS_DEFAULT so that the packages will include documentation. I recently received a PR for one of those ports that mentioned

Re: rubygems not working with ruby 2.2?

Hi, Yep, I'm aware, there's an update to devel/ruby-gems pending, see: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197083 Steve On Thu, Mar 05, 2015 at 09:25:43AM +, Koichiro IWAO wrote: Reproduced in clean environment. I think devel/ruby-gems is too old and needs updating.

ruby-gems update to 2.4.5

Hi, I hope to soon update devel/ruby-gems to the latest version, 2.4.5, after far too long at the ancient 1.8.x. There is a review here: https://reviews.freebsd.org/D1678 though only those with an @FreeBSD.org email address may currently sign up and comment on the review. There's also a PR in

Re: FreeBSD Port: ruby21-2.1.3_1,1

On Fri, Nov 07, 2014 at 06:41:40PM -0700, Carol Deihl wrote: Hello, I just installed ruby21-2.1.3_1,1 with the DEBUG option *unset*, and when ruby21 is invoked, it prints out: WARNING: number of probes fixed does not match the number of defined probes (9 != 50, respectively) WARNING:

Re: FreeBSD Port: ruby21-2.1.3_1,1

On Sat, Nov 08, 2014 at 03:35:26PM +, Steve Wills wrote: On Fri, Nov 07, 2014 at 06:41:40PM -0700, Carol Deihl wrote: Hello, I just installed ruby21-2.1.3_1,1 with the DEBUG option *unset*, and when ruby21 is invoked, it prints out: WARNING: number of probes fixed does not match

Re: Can't build ruby20 on -current: it doesn't honor WITHOUT_CDDL=yes

On Tue, Nov 04, 2014 at 05:41:31AM +0300, Andrey Chernov wrote: On 30.10.2014 18:15, Steve Wills wrote: The checks for OS version weren't meant to detect presence of dtrace, they were meant to detect presence of dtrace with usable USDT. Unfortunately, presence of /usr/sbin/dtrace

Re: Can't build ruby20 on -current: it doesn't honor WITHOUT_CDDL=yes

On Thu, Oct 30, 2014 at 01:26:02PM +0300, Andrey Chernov wrote: On 30.10.2014 13:17, Baptiste Daroussin wrote: On Thu, Oct 30, 2014 at 01:11:33PM +0300, Andrey Chernov wrote: Hi. I disable zfs and dtrace on my machine using WITHOUT_CDDL=yes in /etc/src.conf ryby20 port throw this error:

Re: INDEX build breakage

On Mon, Mar 24, 2014 at 06:28:50PM +, Portsnap buildbox wrote: /usr/ports/Mk/Uses/compiler.mk, line 104: warning: c++ -### /dev/null 21 returned non-zero status [snip] /usr/ports/Mk/Uses/compiler.mk, line 104: warning: c++ -### /dev/null 21 returned non-zero status make_index:

Re: pidgin with pidgin-sipe plugin now aborts on connect

There are some additional changes needed, see PR ports/186783. This version passes poudriere testport. Also, PR ports/183941 was submitted to update to 1.17.0, but had some issues with KRB5 and wasn't committed. This version builds fine with KRB5 for me, so I think 183941 can be closed. Steve

Re: Can't seem to build ruby19 or 18.

On Mon, Jan 27, 2014 at 12:11:52PM -0600, Edwin L. Culp W. wrote: === Building for ruby-1.9.3.484_1,1 make: don't know how to make OPENSSL_CFLAGS. Stop *** [do-build] Error code 1 I just want to be sure that it isn't me, hopefully. I'm unable to reproduce, and based on other responses and

Re: lang/ruby19: fails to build on 9.2-STABLE: don't know how to make OPENSSL_CFLAGS. Stop

On Mon, Jan 27, 2014 at 04:14:14PM +0100, Herbert J. Skuhra wrote: Den 27.01.2014 11:48, skrev O. Hartmann: On all FreeBSD 9.2-STABLE oboxes, the update of port lang/ruby19 fails with checking for nroff... /usr/bin/nroff .ext/include/amd64-freebsd9/ruby/config.h updated ruby library

Re: how to install ruby18

On Sat, Jan 04, 2014 at 03:45:12PM +0100, John Marino wrote: On 1/4/2014 15:38, Marco Beishuizen wrote: On Sat, 4 Jan 2014, the wise John Marino wrote: Portupgrade builds fine, but I have my locale set to UTF-8 and in that case the pkgdb breaks and portupgrade no longer works: ...

Re: Fwd: take a look at ports/182540 (vulnerabilities)

Went ahead and committed, build tests are still running for me. If someone could work on a VuXML entry, that would be great, I have to run for a while right now. Steve On Tue, Oct 22, 2013 at 06:01:13AM -0500, Bryan Drewery wrote: PR is assigned to you. Original Message

Re: evolution-webcal - invalid DSO for symbol `g_thread_init' definition

On Tue, Aug 06, 2013 at 09:40:37PM -0400, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #78 r253966: Mon Aug 5 14:42:05 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 cc -DHAVE_CONFIG_H -I. -I.. -DGNOMELOCALEDIR=\/usr/local/share/locale\

Re: [CFT] devel/gitlab

On Fri, Aug 02, 2013 at 01:13:49PM +0300, Ivan Klymenko wrote: Hello everyone! Please help me in testing the SUBJ port and bringing it to the correct state. :) https://redports.org/browser/fidaj/devel/gitlab Submitted comments and the patches :). I've been interested in having a port

Re: FreeBSD Port: rubygem-ohai-6.16.0

Thanks, I went ahead and filed a PR for it: http://www.freebsd.org/cgi/query-pr.cgi?pr=180732 We're going to have to wait on a maintainer timeout I think. Steve On Sun, Jul 21, 2013 at 12:22:32PM -0700, Douglas Thrift wrote: Hello, I have attached a patch for Ohai which fixes IP address

Re: Redmine rmagick dependencies

On 07/12/13 19:47, Kozlov Sergey wrote: Hi all. I've already posted this on questions, but got no reply. Sorry I didn't see your message. Recently the redmine port was updated to 2.3.1 and when i tried to install it I've noticed that it has two rmagick dependencies - ruby-rmagick(optional)

Re: INDEX build failed for 8.x

Fixed, sorry about that. On 07/02/13 09:08, Ports Index build wrote: INDEX build failed with errors: Generating INDEX-8 - please wait..clang: not found Done. Warning: Duplicate INDEX entry: rubygem-bunny-0.6.0 Committers on the hook: culot delphij girgen jgh jkim sbz swills Most

Re: CFT: [patch] making -jX builds the default

On 06/30/13 16:40, Alexey Dokuchaev wrote: Hi there, In attempt to catch (hopefully) last few remaining jobs-unsafe ports, and thus to make upcoming expruns fallouts easier to handle, I'm sending small patch I've been using locally for a while to get larger exposure. Patch was sent to

Re: www/rubygem-passenger now requires bash?

I'm running FreeBSD/amd64 8-STABLE (r250276) and, yesterday, updated www/rubygem-passenger from 3.0.19 to 4.0.5 via portmaster. Although the port upgraded without error, the resultant Passenger no longer works: it complains it can't find bash and Rails apps won't spawn. I don't have

Re: rubygem-nokogiri error: \xE2 from ASCII-8BIT to UTF-8

Hello, I just attempted to upgrade Ruby Redmine and one of the gems, nokogiri, (and a few others) die with the same ASCII-8BIT to UTF-8 error durring the doc install phase which prevents the port from completing the install. I've searched and search and cannot find anything that relates

Re: www/rubygem-passenger now requires bash?

I'm running FreeBSD/amd64 8-STABLE (r250276) and, yesterday, updated www/rubygem-passenger from 3.0.19 to 4.0.5 via portmaster. Although the port upgraded without error, the resultant Passenger no longer works: it complains it can't find bash and Rails apps won't spawn. I don't have

Re: Status of USE_GITHUB fetching

On 06/07/13 22:32, Bryan Drewery wrote: On 6/6/2013 8:26 AM, Bryan Drewery wrote: Ports using USE_GITHUB are currently broken. Github changed their tar/compression algorithm which has resulted in mismatched checksums. I am working on changing our implementation and updating all affected

Re: fetch: expansion of correct source location in MASTER_SITES fails

On 06/01/13 11:17, O. Hartmann wrote: I'm preparing a port and I fail downloading the sources, although the base URL and the target tar ball are expanded correctly. But the fetch process then complains with this: [...] === pocl-0.8.0 depends on file: /usr/local/sbin/pkg - found =

Re: fetch: expansion of correct source location in MASTER_SITES fails

Thank you for clearify this. Even if I use the SF macro and set FETCH_ARGS= to en ampty string (I suppose this will result in a plain fetch command without options) the result is as described intially. Applying the -v option to fetch then shows what happens and everything looks fine to me

Re: ruby 1.9 upgrade and puppet

Moving to ruby 1.9 by following the instructions in UPDATING breaks puppet. Sorry for the breakage, I'll take a look. Steve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any

Re: ruby 1.9 upgrade and puppet

Moving to ruby 1.9 by following the instructions in UPDATING breaks puppet. When updating with portmaster, at install time it says 'could not load facter; cannot install' and exits. I had to manually run 'gem install facter', then puppet installed. It's better to install via the port so

Re: ruby 1.9 upgrade and puppet

On 05/31/13 21:02, bw.mail.lists wrote: It would probably be best to kill puppet before the upgrade. This is definitely the problem here. I'm afraid you'll have to manually kill it here, since the old rc script has been deinstalled. You'll only have to do it this once. Not a

Re: portupgrade broken after ruby upgrade

On Tue, 28 May 2013, the wise Bryan Drewery wrote: root@yokozuna:/usr/ports# portupgrade -a invalid byte sequence in UTF-8 Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFOQ Portupgrade does not handle major ruby upgrades well. I recommend rebuilding portupgrade and its databases:

[HEADSUP] default version of Ruby switched to 1.9

Hi All, Just a heads up, I've finally switched the default version of Ruby to 1.9. There is a note in UPDATING that should help. Let us know if you have any trouble. Steve ___ freebsd-ports@freebsd.org mailing list

Re: INDEX build failed for 8.x

My fault, fixed now, sorry about that. Steve On 05/27/13 00:05, Ports Index build wrote: INDEX build failed with errors: Generating INDEX-8 - please wait..clang: not found Done. make_index: rubygem-dm-core-1.2.0: no entry for /usr/ports/www/rubygem-addressable22 Committers on the hook:

Re: [texlive, FreeBSD 10.x-amd64] build error: _ThreadRuneLocale: TLS definition in /usr/lib/libc.so section .tbss mismatches non-TLS reference in gsftopk.o

On 05/16/13 15:29, Hiroki Sato wrote: Boris Samorodov b...@passap.ru wrote in 51939aed.3060...@passap.ru: bs Hi, bs bs I've got an error while building texlive-base at fresh CURRENT: bs - bs % uname -a bs FreeBSD BB049.int.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #21 r250633: bs

Re: [CFT] add a config.site cache for the ports

I'm sure your list probably includes this, but just in case, databases/db42 broke with this for me. Steve just a fyi this exp-run broke quiet a lot. On Mar 23, 2013, at 11:18 PM, Bryan Drewery bdrew...@freebsd.org wrote: On 3/18/2013 12:41 PM, Baptiste Daroussin wrote: Hi, The

Re: [CFT] New dialog for ports

I wonder if it is worth to let the question to install dialog4ports. I mean dialog4ports being mandatory you should just be installed directly doesn't it? anyone have an opinion about this? I will remove the question on 27/03 if I got more please do than please don't at that time. The

Re: [CFT] New dialog for ports

On 03/14/13 09:55, Baptiste Daroussin wrote: Hi all, Ilya A. Arkhipov wrote dialog4ports which has just been added into the ports tree ports-mgmt/dialog4ports, this is intended to be a replacement for dialog(1) designed specifically for the options, in particular for optionsng. It uses

Re: [CFT] add a config.site cache for the ports

On 18 Mar 2013 17:42, Baptiste Daroussin b...@freebsd.org wrote: Hi, The autotools allows us to have a config.site cache where we define our defaults values for a couple of things, and prevent the slow and possibly wrong autodetection. Here is a patch that makes use of it:

Re: Port deprecation reason ``Does not work with Ruby 1.9'' -- what should I do?

On 3/11/2013 4:13 PM, Lev Serebryakov wrote: Hello, Ports. My port (devel/ruby-subversion) is marked for deletion in 2 months because `` Does not work with Ruby 1.9''. What should I do? To be honest, I know nothing about Ruby and this port is part of official subversion

  1   2   >