Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Erwin Lansing
On Thu, Aug 06, 2015 at 05:19:54PM -0700, Xin Li wrote: > Hi, > > Currently the default portsnap.conf would generate INDEX-11, INDEX-10 > and INDEX-9. The INDEX file is only used for searching ports, and only > one (INDEX-${OSREL:R}) file is actually used. > This is default behaviour for other

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 8/6/15 22:24, Kevin Oberman wrote: > Or the code in portsnap could be modified to get the current > running version. I thought about this today but it won't work as advertised: someone (currently me) still have to tweak the portsnap builder con

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Kevin Oberman
On Thu, Aug 6, 2015 at 9:58 PM, Jamie Landeg-Jones wrote: > Kevin Oberman wrote: > > > Isn't rebuilding the index useful for people running STABLE? I assume > that > > I need a current index to get useful output from "pkg version -vL=". I am > > probably a bit unusual in that I keep a current po

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Jamie Landeg-Jones
Kevin Oberman wrote: > Isn't rebuilding the index useful for people running STABLE? I assume that > I need a current index to get useful output from "pkg version -vL=". I am > probably a bit unusual in that I keep a current ports tre on a STABLE > system, but there are a couple of ports that I ne

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Kevin Oberman
On Thu, Aug 6, 2015 at 5:19 PM, Xin Li wrote: > Hi, > > Currently the default portsnap.conf would generate INDEX-11, INDEX-10 > and INDEX-9. The INDEX file is only used for searching ports, and only > one (INDEX-${OSREL:R}) file is actually used. > > Traditionally, we create all supported INDEX-

Re: Unable to relocate to new svn URL

2015-08-06 Thread Kevin Oberman
On Thu, Aug 6, 2015 at 1:57 PM, olli hauer wrote: > On 2015-08-06 05:44, Kevin Oberman wrote: > > > ... > > > > This still leaves the issue of requiring SASL support in subversion. A > note > > in the handbook section on ports would help, though I'll admit that I > > probably would not have found

Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Xin Li
Hi, Currently the default portsnap.conf would generate INDEX-11, INDEX-10 and INDEX-9. The INDEX file is only used for searching ports, and only one (INDEX-${OSREL:R}) file is actually used. Traditionally, we create all supported INDEX-* files by default, but the only users who would benefit fro

devel/subversion staging, won't install.

2015-08-06 Thread Jeffrey Bouquet via freebsd-ports
I've a note in devel/subversion that it failed to install in March this year... Just then (aug 6) it again fails to install [ terse kwallet-dynamic-lib something, broken install line in built-already install-from-stage ; the relevant ?? option is deselected ]. Maybe someone knows if some option i

Re: Unable to relocate to new svn URL

2015-08-06 Thread olli hauer
On 2015-08-06 05:44, Kevin Oberman wrote: > ... > > This still leaves the issue of requiring SASL support in subversion. A note > in the handbook section on ports would help, though I'll admit that I > probably would not have found it in this case. Perhaps a note in > ports/UPDATING might be in o

Re: Telegram-cli Issues

2015-08-06 Thread Aric Gregson
OK. I am not sure what I was doing with 1.0.5.1, but I have updated to 1.3 and it is working. It appears that there have been significant changes, but all is good. Thank you very much for getting this port together. Does anyone know of a way to listen to audio in the cli? Thanks, Aric _

Re: skype ports status and expectations

2015-08-06 Thread Michael Zhilin
Here you are: https://svnweb.freebsd.org/ports?view=revision&revision=389223 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200608 __FreeBSD_version >= 1100075, but I don't know actual revision. In any case, you can use latest CURRENT snapshot, it will work. On Thu, Aug 6, 2015 at 9:10 PM, Mat

Re: Telegram-cli Issues

2015-08-06 Thread Dave Horsfall
On Thu, 6 Aug 2015, Matthias Apitz wrote: > The Telegram protocol and clients have a feature to shown to the sender > when the receiver has read the message, Telegram Support calls this > "read" status for messages and says it is an essential feature of > Telegram. > > I call it a violation of

Re: skype ports status and expectations

2015-08-06 Thread Matthias Apitz
El día Friday, July 31, 2015 a las 09:51:24AM +0300, Sergey V. Dyatko escribió: > I'm using FreeBSD-CURRENT (amd64) + net-im/skype4. All works fine (I hope). > http://gyazo.com/258a43fcb34ea384482800fa3d3de464 Could you please share the SVN rev. of your CURRENT or the output of 'uname -a'. Thank

Re: Telegram-cli Issues

2015-08-06 Thread Pietro Cerutti
On 2015-Aug-05, 11:35, Aric Gregson wrote: > Hello, > > I am no longer able to make net-im/telegram-cli work. I believe this > happened when I upgraded to 10.1 some time ago. I have reinstalled the > program via portmaster several times to no avail. both 1.0.5.1_1 and 1.3.1 work fine here (10.1-

Re: Telegram-cli Issues

2015-08-06 Thread Carlos Jacobo Puga Medina
El jue, 06-08-2015 a las 13:20 +0200, Kurt Jaeger escribió: > Hi! > > > The Telegram protocol and clients have a feature to shown to the > > sender > > when the receiver has read the message, Telegram Support calls this > > "read" status for messages and says it is an essential feature of > > Tel

INDEX now builds successfully on 9.x

2015-08-06 Thread Ports Index build
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Telegram-cli Issues

2015-08-06 Thread Matthias Apitz
El día Thursday, August 06, 2015 a las 02:56:34PM +0200, Matthias Apitz escribió: > $ telegram-cli > Telegram-cli version 1.3.1, Copyright (C) 2013-2015 Vitaly Valtman > ... > phone number: +49-176-38902045 > code ('call' for phone call): 73469 > User Matthias Apitz online (was online [2015/08/0

Re: Telegram-cli Issues

2015-08-06 Thread Matthias Apitz
El día Thursday, August 06, 2015 a las 01:20:10PM +0200, Kurt Jaeger escribió: > > It would be nice, if we (FreeBSD) could add (as a patch in the ports > > tree) a configuration value to the telegram-cli which does not > > send such notifications when the configuration says so. > > > > What do yo

INDEX build failed for 9.x

2015-08-06 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-9 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- de

Re: Telegram-cli Issues

2015-08-06 Thread Kurt Jaeger
Hi! > The Telegram protocol and clients have a feature to shown to the sender > when the receiver has read the message, Telegram Support calls this > "read" status for messages and says it is an essential feature of > Telegram. > > I call it a violation of the receivers privacy. 100% agreed. >

Re: Telegram-cli Issues

2015-08-06 Thread Matthias Apitz
Hello, The Telegram protocol and clients have a feature to shown to the sender when the receiver has read the message, Telegram Support calls this "read" status for messages and says it is an essential feature of Telegram. I call it a violation of the receivers privacy. I have an Ubuntu based m

INDEX build failed for 9.x

2015-08-06 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-9 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- de