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

2017-04-26 Thread Steve Wills
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: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0

2017-03-01 Thread Harry Schmalzbauer
Bezüglich Steve Wills's Nachricht vom 01.03.2017 06:57 (localtime): > Hi All, > > Thanks to everyone who tested. > > I've updated the patch and packages in the same location and fixed a > number of issues. Please re-test if you can. > > The only remaining issue that I know of is building with

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

2017-02-28 Thread Steve Wills
d 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 packages with > the new version an

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

2017-01-23 Thread Kurt Jaeger
Hi! > > I tried to built it on > > > > 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r307013:311651M > > > > (why does it say r307013:311651M, btw?) > > Because some of your source is r307013 and other parts of your src tree > has been updated to r31165. Ah, yes, that's it. Most of the tree is

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

2017-01-23 Thread Steve Wills
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/ope

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

2017-01-23 Thread Steve Wills
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

2017-01-22 Thread Julian Elischer
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 themselves: https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.0.diff And for those who

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

2017-01-21 Thread Kurt Jaeger
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 I tried to built it on 12.0-CURRE

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

2017-01-20 Thread Steve Wills
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

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

2017-01-20 Thread Julian Elischer
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 themselves: the problem we had with the existing on is that it ended up installing vi dependencies, a LOT

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

2017-01-19 Thread Steve Wills
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

ports/180920: emulators/open-vm-tools-nox11 does not compile

2013-10-17 Thread Matthias Apitz
Hello, This is still true with 10-CURRENT r255948 (October, 1) and ports r328930... Anything new on his bug? Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW:

Re: ports/180920: emulators/open-vm-tools-nox11 does not compile

2013-10-17 Thread 1blu-Homepage Unlimited
El día Thursday, October 17, 2013 a las 01:43:20PM +0200, Matthias Apitz escribió: Hello, This is still true with 10-CURRENT r255948 (October, 1) and ports r328930... Anything new on his bug? ^^^ Should have been this bug; sorry for the typo; matthias --

open-vm-tools-nox11

2010-01-07 Thread Peter Czanik
Hello, When building a package from open-vm-tools-nox11, I run into the following problem: === Building package for open-vm-tools-nox11-210370_1 Creating package /usr/packages/All/open-vm-tools-nox11-210370_1.tbz Registering depends: glib-2.22.3 gettext-0.17_1 libiconv-1.13.1 icu-3.8.1_2 pcre

RE: FreeBSD Port: open-vm-tools-nox11-102166_4

2008-10-08 Thread Cligny, Laurent
[snip my problem] Should be fixed. Martin Hello Martin, It works well now, thanks for your work. Thanks also to Scot Hetzel for his response. The FreeBSD community is responsive and helpful has always. Cheers, Laurent Cligny ISOBOX Technologies - SAS au capital de 4 575 000 Euros RCS

FreeBSD Port: open-vm-tools-nox11-102166_4

2008-10-07 Thread Cligny, Laurent
Hello, I want to use open-vm-tools-nox11 on a 7.0-RELEASE box without using the port tree on it. So I wanted to build a package for this port on another 7.0-RELEASE machine, wiche have the port tree installed and up-to-date. But, here's what's happening with either pkgcreate -p or make package

Re: FreeBSD Port: open-vm-tools-nox11-102166_4

2008-10-07 Thread Scot Hetzel
On 10/7/08, Cligny, Laurent [EMAIL PROTECTED] wrote: Hello, I want to use open-vm-tools-nox11 on a 7.0-RELEASE box without using the port tree on it. So I wanted to build a package for this port on another 7.0-RELEASE machine, wiche have the port tree installed and up-to-date