Re: x11-toolkits/mx build fail

Le 26/05/2013 21:54, Lowell Gilbert a écrit : > Beeblebrox writes: > >> Sorry, my bad - port is part of marcuscom-gnome3 apparently. I have had so >> many port-build fails (consistently over a long period) that a neglected to >> check the port origin. >> Will report issue to marcuscom-gnome3 > >

Re: ports/17892: commit references a PR

The following reply was made to PR ports/17892; it has been noted by GNATS. From: dfil...@freebsd.org (dfilter service) To: bug-follo...@freebsd.org Cc: Subject: Re: ports/17892: commit references a PR Date: Mon, 27 May 2013 08:59:26 + (UTC) Author: jadawin Date: Mon May 27 08:57:05 2013

[QAT] r319190: 4x leftovers

Fix plist - Build ID: 20130527093001-21085 Job owner: b...@freebsd.org Buildtime: 33 minutes Enddate: Mon, 27 May 2013 10:02:39 GMT Revision: r319190 Repository: htt

Current unassigned ports problem reports

(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsol

Speciale COSTA CROCIERE da 340 euro

VIAGGI & TURISMO Via Genova 20 - PESCARA TEL.085-4224040 - cell. 328-7287173 www.eurotour.it - i...@eurotour.it **Newsletter di offerte** Giovedí, 23 Maggio 2013 *9* offerte totali Speciale COSTA CROCIERE da

Re: [HEADS UP] xorg mega-update committed!

On 05/26/13 02:58, Niclas Zeising wrote: With the new xserver (1.12) it is not possible currently, it seems. I haven't tested the old server. Thanks for the work. It's probably me, missing the original message or some old discussion, but I think many of us would welcome some more details; th

Re: The vim port needs a refresh

On Fri, 24 May 2013 17:23:18 -0400 Kenta Suzumoto wrote: > - It fetches almost 700 patches from what seems like a dial-up > connection in AUSTRALIA. > > You might as well be downloading a 1080p movie from a rock in the > north pole, because that's about how fast it is. This can be very > easily

[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 http://lists.freebsd.org/mailman/lis

Re: Proper way to access executable's "environment"?

On Mon, May 27, 2013 at 05:43:13AM +0700, Erich Dollansky wrote: > ... > > piewm's twm.c declares main as: > > > > int > > main(int argc, char **argv, char **environ) > > { > > I use this concept since decades but with different names. Could it be > a problem of overlapping names? > ... It was p

Re: The vim port needs a refresh

RW writes: > On Fri, 24 May 2013 17:23:18 -0400 > Kenta Suzumoto wrote: > > >> - It fetches almost 700 patches from what seems like a dial-up >> connection in AUSTRALIA. >> >> You might as well be downloading a 1080p movie from a rock in the >> north pole, because that's about how fast it is. Th

Re: Proper way to access executable's "environment"?

On Sun, 26 May 2013 11:06:29 -0700, David Wolfskill wrote: > On Sun, May 26, 2013 at 07:55:03PM +0200, Stefan Ehmann wrote: > > ... > > > So I have a couple of questions related to the above: > > > * Is the patch correct?... > > > > Should be fine. See environ(7) or > > http://pubs.opengroup.org/o

Is latest portsnap snapshot corrupted?

Looks so: Fetching public key from portsnap1.FreeBSD.org... done. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Mon May 27 02:02:39 CEST 2013: ecc705a413e04a7c6eafdc110161ed9e1d6efd52224e7a100% of 8007 kB 702 kBps 00m0

Re: The vim port needs a refresh

On Mon, 27 May 2013 09:36:20 -0400 Lowell Gilbert wrote: > RW writes: > > I prefer it the way it is; those patch files are cached in the > > distfiles directory, so only new patches need be downloaded. I can't > > say I've ever noticed it being slow. If you roll them up into one > > file the wh

Maintainer update for mail/roundcube-userprefs (was ports/179007: )

Hey, sorry I screwed up the synopsis line; maybe somebody can correct that? Thanks, Stefan Am 27.05.2013 um 10:50 schrieb freebsd-gnats-sub...@freebsd.org: > Thank you very much for your problem report. > It has the internal identification `ports/179007'. > The individual assigned to look at y

Re: The vim port needs a refresh

On 5/27/2013 16:34, RW wrote: It would hurt people with a slow connections who would end-up having to download most of the patches twice. I've a lot more sympathy with people in that situation than with someone who doesn't cache and then complains it's slow. Trust me. If you get the wrong mirr

Re: Is latest portsnap snapshot corrupted?

I met with the same problem, too. On Mon, May 27, 2013 at 10:30 PM, Jakub Lach wrote: > Looks so: > > Fetching public key from portsnap1.FreeBSD.org... done. > Fetching snapshot tag from portsnap1.FreeBSD.org... done. > Fetching snapshot metadata... done. > Fetching snapshot generated at Mon Ma

Re: Proper way to access executable's "environment"?

On 05/27/2013 15:32, David Wolfskill wrote: On Mon, May 27, 2013 at 05:43:13AM +0700, Erich Dollansky wrote: ... piewm's twm.c declares main as: int main(int argc, char **argv, char **environ) { I use this concept since decades but with different names. Could it be a problem of overlapping n

Re: The vim port needs a refresh

On Mon, 27 May 2013 17:19:40 +0200 John Marino wrote: > On 5/27/2013 16:34, RW wrote: > > > > It would hurt people with a slow connections who would end-up > > having to download most of the patches twice. I've a lot more > > sympathy with people in that situation than with someone who > > doesn't

Re: The vim port needs a refresh

On 5/27/2013 18:36, RW wrote: Like 4 patches per minute slow. You have no sympathy for somebody that has to download all 900+ patches from the beginning? A little if it's the first time they've ever built vim on FreeBSD, and they have have genuine good reason for not being able to wait an ex

FreeBSD Port: textproc/libvisio

Hello, I am unable to compile this port, below is the output from gcc48 and clang 3.2. 9.1-STABLE FreeBSD 9.1-STABLE #0: Wed May 15 17:07:33 EDT 2013 gmake[4]: Entering directory `/usr/ports/textproc/libvisio/work/libvisio-0.0.27/src/conv/raw' CXX vsd2raw.o CXXLDvsd2raw ../../l

Re: [HEADSUP] default version of Ruby switched to 1.9

On 27 May 2013 15:26, Steve Wills wrote: > 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. Thank you, I'm sure this took an enormous amount of time and effort on your part

Re: The vim port needs a refresh

On Mon, 27 May 2013 18:44:55 +0200 John Marino wrote: > Great. With the previous mirror I had it would have taken well over > an hour back when the patch count was 700. By default it should be the same mirror if you tested it this year. Slow and dead mirrors were removed at the beginning of Ja

Re: Proposal: do not show up the dialog(1) by default?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 23.05.2013 07:45, schrieb Baptiste Daroussin: > hi, > > A lot of people seems to be complaining about the configuration dialog popping > up all the time. > > What if we change the default behaviour to not pop up the dialog each time > there > is

Re: Proposal: do not show up the dialog(1) by default?

On Mon, May 27, 2013 at 10:35 AM, Matthias Andree wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 23.05.2013 07:45, schrieb Baptiste Daroussin: > > hi, > > > > A lot of people seems to be complaining about the configuration dialog > popping > > up all the time. > > > > What if we c

Re: Is latest portsnap snapshot corrupted?

Thanks! Could some dev chime in? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Is-latest-portsnap-snapshot-corrupted-tp5815448p5815520.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@free

Re: The vim port needs a refresh

On 5/27/2013 19:36, RW wrote: On Mon, 27 May 2013 18:44:55 +0200 John Marino wrote: Great. With the previous mirror I had it would have taken well over an hour back when the patch count was 700. By default it should be the same mirror if you tested it this year. Slow and dead mirrors were

ejabberd port: default config not working

I've just installed ejabberd from ports > sudo portversion -v ejabberd ejabberd-2.1.11 = up-to-date with port Just to get it running, I've put the sample configs in place as running configs. I did a quick scan through them to look for any obvious changes that needed to be made

Re: Why does Samba requires 777 permissions on /tmp

Hi Guys, I just got home from being out of town and the problem still persists even after I removed . from my path. echo $PATH /bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome

Re: Why does Samba requires 777 permissions on /tmp

Did you try changing PKG_TMPDIR as I suggested? (see below) On Mon, 27 May 2013 14:45:05 -0500 sindrome wrote: > Hi Guys, > > I just got home from being out of town and the problem still persists > even after I removed . from my path. > > echo $PATH > /bin:/usr/lib:/sbin:/usr/bin:/usr/local/s

Re: Why does Samba requires 777 permissions on /tmp

Hi Bob, I just went into /usr/local/etc/pkgtools.conf and changed the PKG_TMPDIR variable to a non-world writable directory called /build and still see the warnings below: /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning: Insecure world writable dir /tmp/ in PATH, mode 041777 /

Re: The vim port needs a refresh

On Mon, 27 May 2013 20:38:11 +0200 John Marino wrote: > >> It's obviously true since multiple users are seeing it. (the whole > >> 1080 movie analogy, remember?) > > > > It not obviously true that you aren't all either making this problem > > with your make.conf settings or referring to a proble

Re: The vim port needs a refresh

On 5/27/2013 22:09, RW wrote: On Mon, 27 May 2013 20:38:11 +0200 John Marino wrote: No, that's something you just made up. It is however vague and anecdotal. We have only one data point that we know is from this year and not self-inflicted, even if the others are, for all we know it could still

Re: Why does Samba requires 777 permissions on /tmp

On 27 May 2013 20:45, "sindrome" wrote: > > Hi Guys, > > I just got home from being out of town and the problem still persists even > after I removed . from my path. > > echo $PATH > /bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/home/sindrome/.gnupg:/home/sindrome/bin:/hom

Re: Is latest portsnap snapshot corrupted?

Mon, 27 May 2013 11:32:22 -0700 (PDT) tarihinde Jakub Lach yazmış: > Could some dev chime in? Ia am not a dev, but portstree snapshot is fixed. Simply run '# portsnap fetch extract && portsdb -u' and you will get a fresh snapshot of ports tree. -- Gökşin Akdeniz pgpMix2fXkQzY.pgp Descrip

Re: Is latest portsnap snapshot corrupted?

On 27/05/2013 22:13, Gökşin Akdeniz wrote: Ia am not a dev, but portstree snapshot is fixed. Simply run '# portsnap fetch extract && portsdb -u' and you will get a fresh snapshot of ports tree. Is '# portsnap fetch update' not sufficient? It seemed to work here. -- Bruce Cran __

Re: Why does Samba requires 777 permissions on /tmp

Chris, That did it! Thanks so much for the help. Just in case if anyone else is reading this long thread, you cannot have a colon period (:.) at the end of your pathmeaning do not include the current directory as part of the $path On Mon, May 27, 2013 at 3:54 PM, Chris Rees wrote: > > O

Re: Is latest portsnap snapshot corrupted?

Indeed snapshot looks fixed, thanks for all replies! I don't use INDEX.db so should be fine without portsdb... -- View this message in context: http://freebsd.1045724.n5.nabble.com/Is-latest-portsnap-snapshot-corrupted-tp5815448p5815588.html Sent from the freebsd-ports mailing list archive at

Re: FreeBSD Port: textproc/libvisio

On Mon, May 27, 2013 at 01:10:52PM -0400, Mike Jakubik wrote: > Hello, > > I am unable to compile this port, below is the output from gcc48 and > clang 3.2. > > 9.1-STABLE FreeBSD 9.1-STABLE #0: Wed May 15 17:07:33 EDT 2013 > > gmake[4]: Entering directory > `/usr/ports/textproc/libvisio/work/

Re: Is latest portsnap snapshot corrupted?

On Tue, May 28, 2013 at 12:15 AM, Bruce Cran wrote: > On 27/05/2013 22:13, Gökşin Akdeniz wrote: >> >> Ia am not a dev, but portstree snapshot is fixed. Simply run >> >> '# portsnap fetch extract && portsdb -u' >> >> and you will get a fresh snapshot of ports tree. >> > > Is '# portsnap fetch upda

Ranking Number 1 on Google is the goal of every website owner

__ Sent To [1]po...@freebsd.org [2]Unsubscribe from this list Blue Shark Solution · 3rd Floor, Shakti Complex, N/R APC, Anand - Vidhyanagar Road, ANAND - 388 001

Re: The vim port needs a refresh

On Mon, 27 May 2013 22:33:53 +0200 John Marino wrote: > On 5/27/2013 22:09, RW wrote: > > On Mon, 27 May 2013 20:38:11 +0200 > > John Marino wrote: > > > > > > No, that's something you just made up. It is however vague and > > anecdotal. We have only one data point that we know is from this > > ye

Re: Is latest portsnap snapshot corrupted?

On Mon, 27 May 2013 22:15:29 +0100 Bruce Cran wrote: > On 27/05/2013 22:13, Gökşin Akdeniz wrote: > > Ia am not a dev, but portstree snapshot is fixed. Simply run > > > > '# portsnap fetch extract && portsdb -u' > > > > and you will get a fresh snapshot of ports tree. > > > > Is '# portsnap fetch

Re: The vim port needs a refresh

On 5/28/2013 01:05, RW wrote: On Mon, 27 May 2013 22:33:53 +0200 John Marino wrote: On 5/27/2013 22:09, RW wrote: On Mon, 27 May 2013 20:38:11 +0200 John Marino wrote: No, that's something you just made up. It is however vague and anecdotal. We have only one data point that we know is from t

[QAT] r319234: 4x leftovers

Do not try to remove directories not created by the port - Build ID: 20130527131401-45390 Job owner: b...@freebsd.org Buildtime: 10 hours Enddate: Mon, 27 May 2013 23:18:25 GMT Revisio

Re: The vim port needs a refresh

On Tue, 28 May 2013 01:13:43 +0200 John Marino wrote: > On 5/28/2013 01:05, RW wrote: > > On Mon, 27 May 2013 22:33:53 +0200 > > John Marino wrote: > > In other words downloading every patch twice. > > No. That's not what those words mean. > Please stop assuming that somebody builds Vim repeate

Re: The vim port needs a refresh

On 5/28/2013 01:48, RW wrote: On Tue, 28 May 2013 01:13:43 +0200 No. That's not what those words mean. Please stop assuming that somebody builds Vim repeatedly and start assuming it's built for the very first time. Why wouldn't I? Are you seriously suggesting that it's the norm to build a por

Re: Another Firefox 21.0 crash

In message <20130525230731.ga93...@mail.lunabase.org>, Ted Faber writes: > > --O5XBE6gyVG5Rl6Rj > Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK" > Content-Disposition: inline > > > --YZ5djTAD1cGYuMQK > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content

Re: The vim port needs a refresh

On the first note, complain about the patches to the upstream, not to us. This patches problem has been around since forever and so long the upstream is not changing anything about it, nor do we. About rolling your own distfile, I completely disagree because we do not know what the maintaner has

Re: The vim port needs a refresh

On Tue, 28 May 2013 02:02:00 +0200 John Marino wrote: > On 5/28/2013 01:48, RW wrote: > > On Tue, 28 May 2013 01:13:43 +0200 > >> No. That's not what those words mean. > >> Please stop assuming that somebody builds Vim repeatedly and start > >> assuming it's built for the very first time. > > > >

Re: The vim port needs a refresh

On Sat, May 25, 2013 at 3:50 AM, Chris Rees wrote: > On 24 May 2013 22:23, Kenta Suzumoto wrote: >> >> Hello all. The editors/vim port is currently a mess and needs some changes. >> >> - It fetches almost 700 patches from what seems like a dial-up connection in >> AUSTRALIA. >> >> You might as w

Re: The vim port needs a refresh

On 5/28/2013 02:44, Martin Wilke wrote: On the first note, complain about the patches to the upstream, not to us. This patches problem has been around since forever and so long the upstream is not changing anything about it, nor do we. Hi Martin, This statement is hand-waives the entire discu