jb jb.1234abcd at gmail.com writes:
...
I tested and compared results on FreeBSD 9.0 and FreeBSD 9.1-RC3 (done here
earlier) and this is a summary.
Please review it, in particular the conclusions, as they are intended to be
the base for filing a PR#.
Test on FreeBSD 9.0
---
$
On 26 November 2012 21:15, jb jb.1234a...@gmail.com wrote:
Tim Daneliuk tundra at tundraware.com writes:
...
One wonders if using svn to keep the ports tree up-to-date might not be
simpler, and perhaps, more reliable ...
As managed by portsnap:
$ du -hs /usr/ports/
850M/usr/ports/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/12 4:36 AM, Damien Fleuriot wrote:
On 26 November 2012 21:15, jb jb.1234a...@gmail.com wrote:
Tim Daneliuk tundra at tundraware.com writes:
... One wonders if using svn to keep the ports tree up-to-date
might not be simpler, and
On Nov 27, 2012, at 4:27 PM, Greg Larkin glar...@freebsd.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/12 4:36 AM, Damien Fleuriot wrote:
On 26 November 2012 21:15, jb jb.1234a...@gmail.com wrote:
Tim Daneliuk tundra at tundraware.com writes:
... One wonders if
On Tue, 27 Nov 2012, Greg Larkin wrote:
Unless you plan to use svn commands other than checkout in your ports
tree, I would suggest switching to svn export or perhaps the
svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to
fetch your ports tree.
The export command will not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/12 11:11 AM, Warren Block wrote:
On Tue, 27 Nov 2012, Greg Larkin wrote:
Unless you plan to use svn commands other than checkout in your
ports tree, I would suggest switching to svn export or perhaps
the svn-export script
Tim Daneliuk tundra at tundraware.com writes:
...
I use portsnap fetch update and it works...
Ah, maybe that was the problem. That works for me as well.
Well, not quite ...
# portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from
On 11/25/2012 11:17 PM, Warren Block wrote:
On Sun, 25 Nov 2012, Matthew Seaman wrote:
On 25/11/2012 23:10, Tim Daneliuk wrote:
After the recent security scare, I know the ports tree was temporarily
frozen. Does anyone know when it will again be updates. I just upgraded
to 9.1-PRE and need
On 11/26/2012 01:30 AM, Matthew Seaman wrote:
On 26/11/2012 00:59, Tim Daneliuk wrote:
I use portsnap fetch update and it works...
Ah, maybe that was the problem. That works for me as well.
Ummm... how long have you been using portsnap? If you haven't been
running 'portsnap fetch' or
On Mon, Nov 26, 2012 at 3:48 PM, Tim Daneliuk tun...@tundraware.com wrote:
On 11/26/2012 01:30 AM, Matthew Seaman wrote:
On 26/11/2012 00:59, Tim Daneliuk wrote:
I use portsnap fetch update and it works...
Ah, maybe that was the problem. That works for me as well.
Ummm... how long
On 26/11/2012 13:49, Odhiambo Washington wrote:
I am starting to switch, and after all the discussions in this thread, I
replaced my csup cron entry with the following:
portsnap fetch portsnap extract portsnap update
You definitely don't want to do this.
Most importantly, 'extract' and
On Monday 26 November 2012 13:49:05 Odhiambo Washington wrote:
I am starting to switch, and after all the discussions in this thread, I
replaced my csup cron entry with the following:
portsnap fetch portsnap extract portsnap update
portsnap fetch should only be used interactively; for
jb schreef op :
Tim Daneliuk tundra at tundraware.com writes:
...
I use portsnap fetch update and it works...
Ah, maybe that was the problem. That works for me as well.
Well, not quite ...
I think, after the security incident, you had to obtain a fresh
snapshot of the ports tree,
i.e.
On Mon, Nov 26, 2012 at 5:14 PM, Mike Clarke jmc-freeb...@milibyte.co.ukwrote:
On Monday 26 November 2012 13:49:05 Odhiambo Washington wrote:
I am starting to switch, and after all the discussions in this thread, I
replaced my csup cron entry with the following:
portsnap fetch portsnap
Matthew Seaman wrote:
[snip]
And now I need to find an alternative to handle the src updates using svn
or something...
SVN works, but isn't amazingly quick. If you're on a release branch you
can get the src (and just the src) using freebsd-update(8), which should
be pretty speedy and
Stas Verberkt legolas at legolasweb.nl writes:
jb schreef op :
Tim Daneliuk tundra at tundraware.com writes:
...
I use portsnap fetch update and it works...
Ah, maybe that was the problem. That works for me as well.
Well, not quite ...
I think, after the security incident,
I don't get what you're trying to show here.
What commands you've run indicate that:
1/ you have an up to date ports tree
2/ one of the installed ports needs to be updated
So what ?
Just run # portmaster libreoffice
I think you might be confused, new version available means that you have
On Mon, 26 Nov 2012, kpn...@pobox.com wrote:
On Mon, Nov 26, 2012 at 02:08:52PM +, Matthew Seaman wrote:
Secondly, for the sake of the servers, please don't run 'portsnap fetch'
from a cron job. You're not the only person to think of doing that, and
most people who do have the job run at
So is portsnap cron update and portsnap fetch update doing the same
thing?
Whichever way, it sounds like I need an initial run of portsnap extract
before
putting this in crontab.
From scratch, you need to portsnap fetch extract to establish your ports
directory. After that you either use
Tim Daneliuk tundra at tundraware.com writes:
...
One wonders if using svn to keep the ports tree up-to-date might not be
simpler, and perhaps, more reliable ...
As managed by portsnap:
$ du -hs /usr/ports/
850M/usr/ports/
As managed by svn (it took much longer to checkout/download it
On 26/11/2012 19:17, Warren Block wrote:
It can be downloaded with 'make fetchindex', or built in place with
'make index' (slow--I think Mr. Seaman has a Perl version that's
probably much faster).
That's Dr Seaman if you're going to insist on being formal. Most people
call me Matthew.
And,
On 25/11/2012 23:10, Tim Daneliuk wrote:
After the recent security scare, I know the ports tree was temporarily
frozen. Does anyone know when it will again be updates. I just upgraded
to 9.1-PRE and need to rebuild Firefox Thunderbird against the new
libraries and ... they're broken, marked
On 11/25/2012 05:25 PM, Matthew Seaman wrote:
On 25/11/2012 23:10, Tim Daneliuk wrote:
After the recent security scare, I know the ports tree was temporarily
frozen. Does anyone know when it will again be updates. I just upgraded
to 9.1-PRE and need to rebuild Firefox Thunderbird against the
On Sunday 25 November 2012 17:30:15 Tim Daneliuk wrote:
On 11/25/2012 05:25 PM, Matthew Seaman wrote:
On 25/11/2012 23:10, Tim Daneliuk wrote:
After the recent security scare, I know the ports tree was temporarily
frozen. Does anyone know when it will again be updates. I just
upgraded
On 11/25/2012 06:56 PM, ajtiM wrote:
On Sunday 25 November 2012 17:30:15 Tim Daneliuk wrote:
On 11/25/2012 05:25 PM, Matthew Seaman wrote:
On 25/11/2012 23:10, Tim Daneliuk wrote:
After the recent security scare, I know the ports tree was temporarily
frozen. Does anyone know when it will
On Sun, 25 Nov 2012, Matthew Seaman wrote:
On 25/11/2012 23:10, Tim Daneliuk wrote:
After the recent security scare, I know the ports tree was temporarily
frozen. Does anyone know when it will again be updates. I just upgraded
to 9.1-PRE and need to rebuild Firefox Thunderbird against the
On 26/11/2012 00:59, Tim Daneliuk wrote:
I use portsnap fetch update and it works...
Ah, maybe that was the problem. That works for me as well.
Ummm... how long have you been using portsnap? If you haven't been
running 'portsnap fetch' or 'portsnap cron' then you won't have received
any
27 matches
Mail list logo
