On 2014-07-25, Christian Weisgerber wrote:
> Which fetches an INDEX file that is regularly generated on some
> FreeBSD server, but is not in sync with the exact revision of the
> ports tree I just updated to.
Just for the heck of it, I tried running "make index" myself... and
to my surprise it f
On 26/07/2014 10:23, Konstantin Belousov wrote:
> On Sat, Jul 26, 2014 at 09:57:49AM +0100, Matthew Seaman wrote:
>> On 24/07/2014 18:19, Kevin Oberman wrote:
>>> If 'pkg version' only took a few seconds for you, I suspect you had very
>>> few ports installed. It has always taken minutes for me.
>
On Sat, Jul 26, 2014 at 09:57:49AM +0100, Matthew Seaman wrote:
> On 24/07/2014 18:19, Kevin Oberman wrote:
> > If 'pkg version' only took a few seconds for you, I suspect you had very
> > few ports installed. It has always taken minutes for me.
> >
> > That said, '-P' is much slower than the old
On 24/07/2014 18:19, Kevin Oberman wrote:
> If 'pkg version' only took a few seconds for you, I suspect you had very
> few ports installed. It has always taken minutes for me.
>
> That said, '-P' is much slower than the old default, even though it is
> doing as close as possible to the same thing
On Fri, Jul 25, 2014 at 7:51 AM, Christian Weisgerber
wrote:
> On 2014-07-24, Kevin Oberman wrote:
>
> >> > Is there a reason you want to avoid using the index? It's worked just
> >> fine
> >> > for me for several months on systems with well over 1000 ports
> installed.
> >>
> >> It isn't in syn
On 2014-07-24, Kevin Oberman wrote:
>> > Is there a reason you want to avoid using the index? It's worked just
>> fine
>> > for me for several months on systems with well over 1000 ports installed.
>>
>> It isn't in sync with my ports tree
>
> Which begs the question, why is it out of sync? If yo
On Thu, Jul 24, 2014 at 03:58:34PM -0700 I heard the voice of
Kevin Oberman, and lo! it spake thus:
>
> Which begs the question, why is it out of sync? If you update your ports
> tree, all you need to do is:
> make -C /usr/ports fetchindex (takes a few seconds)
That's only "probably close, if you
On Thu, Jul 24, 2014 at 2:34 PM, Christian Weisgerber
wrote:
> On 2014-07-24, Kevin Oberman wrote:
>
> > If 'pkg version' only took a few seconds for you, I suspect you had very
> > few ports installed. It has always taken minutes for me.
>
> $ pkg info|wc -l
> 432
>
> > Is there a reason
On 2014-07-24, Kevin Oberman wrote:
> If 'pkg version' only took a few seconds for you, I suspect you had very
> few ports installed. It has always taken minutes for me.
$ pkg info|wc -l
432
> Is there a reason you want to avoid using the index? It's worked just fine
> for me for several
On Thu, Jul 24, 2014 at 4:42 AM, Christian Weisgerber
wrote:
> On 2014-07-23, Matthew Seaman wrote:
>
> > 'pkg version' priorities changed between repository catalogue, ports
> > index and generating the info out of the ports tree directly. Now if
> > you have an INDEX file, pkg version will re
On 2014-07-23, Matthew Seaman wrote:
> 'pkg version' priorities changed between repository catalogue, ports
> index and generating the info out of the ports tree directly. Now if
> you have an INDEX file, pkg version will read that for preference, as
> it's only about a zillion times faster than
On 23/07/2014 20:07, Herbert J. Skuhra wrote:
> On Wed, 23 Jul 2014 21:03:14 +0200
> Herbert J. Skuhra wrote:
>
>> Hi,
>>
>> is there anything wrong with svn0.eu.freebsd.org?
>>
>> After the latest 'svnlite up' I now get:
>>
>> GeoIP-1.4.8_7 > succeeds index (index has 1.4.8
On Wed, Jul 23, 2014 at 09:07:58PM +0200, Herbert J. Skuhra wrote:
> On Wed, 23 Jul 2014 21:03:14 +0200
> Herbert J. Skuhra wrote:
>
> > Hi,
> >
> > is there anything wrong with svn0.eu.freebsd.org?
> >
> > After the latest 'svnlite up' I now get:
> >
> > GeoIP-1.4.8_7 >
On Wed, 23 Jul 2014 21:03:14 +0200
Herbert J. Skuhra wrote:
> Hi,
>
> is there anything wrong with svn0.eu.freebsd.org?
>
> After the latest 'svnlite up' I now get:
>
> GeoIP-1.4.8_7 > succeeds index (index has 1.4.8_6)
> [...]
'make fetchindex' resolved it. This is new?
Hi,
is there anything wrong with svn0.eu.freebsd.org?
After the latest 'svnlite up' I now get:
GeoIP-1.4.8_7 > succeeds index (index has 1.4.8_6)
cups-client-1.7.3_1> succeeds index (index has 1.7.3)
curl-7.37.1_1 > succeeds index (
15 matches
Mail list logo
