Re: Portsnap restoration after Git migration

[Bob Eager]

On Mon, 12 Apr 2021 16:02:41 -0400
Ed Maste  wrote:

> Colin (cperciva) and I are making good progress on the portsnap build
> infrastructure Git migration. I'll follow up when it is back in
> operation.

Thank you!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[RW via freebsd-ports]

On Wed, 30 Dec 2020 11:02:55 -0700
Edward Sanford Sutton, III wrote:


> portsnap is a shell script where fetch is used for downloads.

It uses fetch for some things, but fetching the actual updates uses
phttpget(8) which supports pipelined HTTP requests. 

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[Edward Sanford Sutton, III]

On 12/28/20 6:06 PM, Thomas Mueller wrote:
>> Kudos to Stefan for keeping portmaster relevant and up-to-date.
>> But I never understood the appeal of portsnap. What's the advantage over
>
>> svnlite co ...
>> cd /usr/ports; make update
>
>> This mechanism is in the base system, so an extra tool demands some
>> justification ;-)
portsnap was much faster for small updates and slower for big updates
last I tested it though I've heard it was the exact opposite for other's
experiences. I found svn always had a certain overhead to run through my
tree to make sure it was in sync where portsnap just said, "yup,
snapshot up to date/needs these few changes" much quicker than my system
could even walk a ports tree. Once months of changes are there I would
have been better off with a fresh fetch effort I presume but doing the
usual update was SLOW. If you want to just have a ports tree and have no
intention of modifying it, tracking said changes, and/or submitting
those patches back, or if you want to have the most up to date copy of
the ports tree, download a copy from a specific changeset or moment in
time, or if you want to downgrade certain ports then I think portsnap
has always been the wrong choice.

>> Kind regards,
>> Patrick
>
>> punkt.de GmbH
>> Patrick M. Hausen
>
> Better yet, I built the full subversion from FreeBSD ports and NetBSD
pkgsrc so am able to use from either FreeBSD or NetBSD.
>
> But the useful days of svnlite or svn with FreeBSD with ports tree
seem to end with the migration to git scheduled for the end of next
March; already ended for FreeBSD doc and current src trees.

portsnap didn't have an upload and svn won't disappear from read only
view anytime soon; legacy FreeBSD support doesn't want that dying off
until their versions last using it die off too.

> I guess svnlite will be dropped from FreeBSD when it will no longer be
usable.
>
> Any way portsnap can be updated to deal with a git repository?

portsnap doesn't deal with a svn repository but uses its own effort to
track changes if I recall. I didn't think the reason for going away was
svn vs git. portsnap is a shell script where fetch is used for downloads.

> I switched from portsnap to subversion following FreeBSD's switch from
csup to subversion for security reasons in summer 2012 (to the best of
my memory).
>
> I figured if I needed subversion to update src and doc trees, may as
well also use it with ports tree: one-stop shopping.
>
> Tom
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[Thomas Mueller]

> Kudos to Stefan for keeping portmaster relevant and up-to-date.
> But I never understood the appeal of portsnap. What's the advantage over

> svnlite co ...
> cd /usr/ports; make update

> This mechanism is in the base system, so an extra tool demands some
> justification ;-)

> Kind regards,
> Patrick

> punkt.de GmbH
> Patrick M. Hausen

Better yet, I built the full subversion from FreeBSD ports and NetBSD pkgsrc so 
am able to use from either FreeBSD or NetBSD.

But the useful days of svnlite or svn with FreeBSD with ports tree seem to end 
with the migration to git scheduled for the end of next March; already ended 
for FreeBSD doc and current src trees.

I guess svnlite will be dropped from FreeBSD when it will no longer be usable.

Any way portsnap can be updated to deal with a git repository?

I switched from portsnap to subversion following FreeBSD's switch from csup to 
subversion for security reasons in summer 2012 (to the best of my memory).

I figured if I needed subversion to update src and doc trees, may as well also 
use it with ports tree: one-stop shopping.

Tom

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[Patrick M. Hausen]

Hi all,

> Am 28.12.2020 um 16:38 schrieb Kevin Oberman :
> 
> portsnap(8) predates svnlite by quite a bit, but you have just described
> why it is not really worth the overhead of maintaining it. As bugzilla
> describes many ticket closures, Overcome by events".

Somehow I must have missed/skipped it.

I used cvsup and later csup all the time it was available. While the migration
from CVS to Subversion took place in 2008 I think I remember the cvsup mirrors
to have been up for quite some time afterwards. Feeding back from Subversion
into a read-only CVS I figure?

/usr/bin/svnlite was introduced in 2013 which leaves a 5 year period of 
interest.

I could not find when cvsup/csup was finally terminated. Does anyone remember?

Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: portsnap

[Kevin Oberman]

On Mon, Dec 28, 2020 at 4:37 AM Patrick M. Hausen  wrote:

> Hi all,
>
> > Am 26.12.2020 um 20:04 schrieb LuMiWa via freebsd-ports <
> freebsd-ports@freebsd.org>:
> > ...and I will continue to use portmaster. But I don't understand why
> > we should no keep portsnap.
>
> Kudos to Stefan for keeping portmaster relevant and up-to-date.
> But I never understood the appeal of portsnap. What's the advantage over
>
> svnlite co ...
> cd /usr/ports; make update
>
> This mechanism is in the base system, so an extra tool demands some
> justification ;-)
>
> Kind regards,
> Patrick
> --
> punkt.de GmbH
> Patrick M. Hausen
> .infrastructure
>
> Kaiserallee 13a
> 76133 Karlsruhe
>
> Tel. +49 721 9109500
>
> https://infrastructure.punkt.de
> i...@punkt.de
>
> AG Mannheim 108285
> Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
>
> portsnap(8) predates svnlite by quite a bit, but you have just described
why it is not really worth the overhead of maintaining it. As bugzilla
describes many ticket closures, Overcome by events".
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[Patrick M. Hausen]

Hi all,

> Am 26.12.2020 um 20:04 schrieb LuMiWa via freebsd-ports 
> :
> ...and I will continue to use portmaster. But I don't understand why
> we should no keep portsnap.

Kudos to Stefan for keeping portmaster relevant and up-to-date.
But I never understood the appeal of portsnap. What's the advantage over

svnlite co ...
cd /usr/ports; make update

This mechanism is in the base system, so an extra tool demands some
justification ;-)

Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: portsnap

[Michael Schuster]

On Sat, Dec 26, 2020, 20:04 LuMiWa via freebsd-ports <
freebsd-ports@freebsd.org> wrote:

> On Sat, 26 Dec 2020 19:51:37 +0100
> Stefan Esser  wrote:
>
> > Am 26.12.20 um 18:41 schrieb LuMiWa via freebsd-ports:
> > > Hi!
> > >
> > > Today I red again an email:
> > >
> > > Subject:[HEADS UP] Planned deprecation of portsnap
> > > From:   Steve Wills 
> > > Date:   2020-08-04 18:43:20
> > >
> > > And as portsnap user I have a question: Do they planning
> > > deprecation of portmaster too?
> >
> > No, I'm actively working on portmaster and have rewritten it from
> > scratch for better performance (and additional features, e.g. building
> > in a clean chroot jail, similar to synth or poudriere).
> >
> > I have been using that version for more than one year, but the
> > functionality is not complete, yet.
> >
> > On a test system with > 2200 installed ports it takes less than 10
> > seconds to identify the ~600 out-of-date ports (that I keep in this
> > state for testing of the upgrade strategy function), which is more
> > than 30 times faster than the same operation with the "official"
> > portmaster.
> >
> > Until completion of that version, I'll continue to maintain and
> > update the current portmaster port ...
> >
> > Regards, STefan
> >
>
> ...and I will continue to use portmaster. But I don't understand why
> we should no keep portsnap.
>

IIRC, there was an email a while ago announcing the discontinuation of
portsnap and explaining the reasoning behind this move.

Regards
Michael


> --
> “Waiter! A cup of coffee without cream, please!
> I’m sorry, sir, we have no cream, only milk, so can it be a coffee
> without milk?”
>
> ― Ernst Lubitsch’s Ninotchka
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[LuMiWa via freebsd-ports]

On Sat, 26 Dec 2020 19:51:37 +0100
Stefan Esser  wrote:

> Am 26.12.20 um 18:41 schrieb LuMiWa via freebsd-ports:
> > Hi!
> > 
> > Today I red again an email:
> > 
> > Subject:[HEADS UP] Planned deprecation of portsnap
> > From:   Steve Wills 
> > Date:   2020-08-04 18:43:20
> > 
> > And as portsnap user I have a question: Do they planning
> > deprecation of portmaster too?
> 
> No, I'm actively working on portmaster and have rewritten it from
> scratch for better performance (and additional features, e.g. building
> in a clean chroot jail, similar to synth or poudriere).
> 
> I have been using that version for more than one year, but the
> functionality is not complete, yet.
> 
> On a test system with > 2200 installed ports it takes less than 10
> seconds to identify the ~600 out-of-date ports (that I keep in this
> state for testing of the upgrade strategy function), which is more
> than 30 times faster than the same operation with the "official"
> portmaster.
> 
> Until completion of that version, I'll continue to maintain and
> update the current portmaster port ...
> 
> Regards, STefan
> 

...and I will continue to use portmaster. But I don't understand why
we should no keep portsnap.

-- 
“Waiter! A cup of coffee without cream, please! 
I’m sorry, sir, we have no cream, only milk, so can it be a coffee
without milk?” 

― Ernst Lubitsch’s Ninotchka
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap

[Stefan Esser]

Am 26.12.20 um 18:41 schrieb LuMiWa via freebsd-ports:

Hi!

Today I red again an email:

Subject:[HEADS UP] Planned deprecation of portsnap
From:   Steve Wills 
Date:   2020-08-04 18:43:20

And as portsnap user I have a question: Do they planning deprecation of
portmaster too?


No, I'm actively working on portmaster and have rewritten it from
scratch for better performance (and additional features, e.g. building
in a clean chroot jail, similar to synth or poudriere).

I have been using that version for more than one year, but the
functionality is not complete, yet.

On a test system with > 2200 installed ports it takes less than 10
seconds to identify the ~600 out-of-date ports (that I keep in this
state for testing of the upgrade strategy function), which is more
than 30 times faster than the same operation with the "official"
portmaster.

Until completion of that version, I'll continue to maintain and
update the current portmaster port ...

Regards, STefan



OpenPGP_signature
Description: OpenPGP digital signature

Re: portsnap

[Kevin Oberman]

On Sat, Dec 26, 2020 at 9:42 AM LuMiWa via freebsd-ports <
freebsd-ports@freebsd.org> wrote:

> Hi!
>
> Today I red again an email:
>
> Subject:[HEADS UP] Planned deprecation of portsnap
> From:   Steve Wills 
> Date:   2020-08-04 18:43:20
>
> And as portsnap user I have a question: Do they planning deprecation of
> portmaster too?
>
> Thank you.
> --
> “Waiter! A cup of coffee without cream, please!
> I’m sorry, sir, we have no cream, only milk, so can it be a coffee
> without milk?”
>
> ― Ernst Lubitsch’s Ninotchka


I'm confused. other than dealing with ports, I don't see any relation. One
is a tool to update the ports tree on a system and the other is a tool to
install or update installed ports, regardless of how the tree was updated.
There are other non-deprecated ports that will continue to  perform both
functions.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap depreciation

[Carmel NY]

On Fri, 18 Sep 2020 15:44:27 -0700, John Kennedy stated:
>On Fri, Sep 18, 2020 at 08:17:35PM +, Pau Amma wrote:
>> On 2020-09-18 17:58, Carmel NY wrote:  
>> > On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:  
>> >> See
>> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
>> >> and the next sections.  
>> > 
>> > According to the above page, "The most straightforward way is to
>> > have Poudriere create a default ports tree for itself, using either
>> > portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if
>> > running FreeBSD-CURRENT)" Am I to understand that if I am running
>> > 11.4-RELEASE, I cannot use subversion?  
>> 
>> "The most straightforward", not "the only". You can definitely use 
>> Subversion with 11.4 if you wish or need to. What you no longer can
>> do is use portsnap with -CURRENT. (I'll grant that "straightforward"
>> may be in the eye of the beholder, though.)  
>
>For my stuff, I pull my stuff into /usr/ports however I want (git,
>long before it was fashionable in my case) and then just set up
>poudriere to use that.  I do a similar things with /usr/src, except I
>want poudriere to have a static copy of that, just in case.
>
>[initial creation]
>   poudriere jail -c -j 12-2 -v 12.2 -m src=/usr/src
>   poudriere ports -c -m null -M /usr/ports -p master
>
>   poudriere jail -l
>
>   JAILNAME VERSIONARCH  METHOD
>   TIMESTAMP   PATH 12-2 12.2-BETA2 1202000 amd64
>   src=/usr/src 2020-09-18 15:32:59
>   /usr/local/poudriere/jails/12-2
>
>  The "-m null" (null method) lets you manage it however you want.
>
>  If I look at my mounts during the build, with ZFS, I can see them:
>
>   Filesystem  SizeUsed   Avail Capacity  Mounted
>   on ...
>   /usr/ports  350G4.0G346G 1%
>   /usr/local/poudriere/data/.m/12-2-master/ref/usr/ports
>   /usr/ports/distfiles364G 17G346G 5%
>   /usr/local/poudriere/data/.m/12-2-master/ref/distfiles

Thanks John, but that is definitely more complex than my needs require.

-- 
Carmel




pgpCC3Q_t_gta.pgp
Description: OpenPGP digital signature

Re: portsnap depreciation

[John Kennedy]

On Fri, Sep 18, 2020 at 08:17:35PM +, Pau Amma wrote:
> On 2020-09-18 17:58, Carmel NY wrote:
> > On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:
> >> See
> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
> >> and the next sections.
> > 
> > According to the above page, "The most straightforward way is to have
> > Poudriere create a default ports tree for itself, using either
> > portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if running
> > FreeBSD-CURRENT)" Am I to understand that if I am running 11.4-RELEASE,
> > I cannot use subversion?
> 
> "The most straightforward", not "the only". You can definitely use 
> Subversion with 11.4 if you wish or need to. What you no longer can do 
> is use portsnap with -CURRENT. (I'll grant that "straightforward" may be 
> in the eye of the beholder, though.)

For my stuff, I pull my stuff into /usr/ports however I want (git, long before
it was fashionable in my case) and then just set up poudriere to use that.  I
do a similar things with /usr/src, except I want poudriere to have a static
copy of that, just in case.

[initial creation]
poudriere jail -c -j 12-2 -v 12.2 -m src=/usr/src
poudriere ports -c -m null -M /usr/ports -p master

poudriere jail -l

JAILNAME VERSIONARCH  METHOD   TIMESTAMP
   PATH
12-2 12.2-BETA2 1202000 amd64 src=/usr/src 2020-09-18 
15:32:59 /usr/local/poudriere/jails/12-2

  The "-m null" (null method) lets you manage it however you want.

  If I look at my mounts during the build, with ZFS, I can see them:

Filesystem  SizeUsed   Avail Capacity  Mounted on
...
/usr/ports  350G4.0G346G 1%
/usr/local/poudriere/data/.m/12-2-master/ref/usr/ports
/usr/ports/distfiles364G 17G346G 5%
/usr/local/poudriere/data/.m/12-2-master/ref/distfiles

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap depreciation

[Pau Amma]

On 2020-09-18 17:58, Carmel NY wrote:

On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:

See
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
and the next sections.


According to the above page, "The most straightforward way is to have
Poudriere create a default ports tree for itself, using either
portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if running
FreeBSD-CURRENT)" Am I to understand that if I am running 11.4-RELEASE,
I cannot use subversion?


"The most straightforward", not "the only". You can definitely use 
Subversion with 11.4 if you wish or need to. What you no longer can do 
is use portsnap with -CURRENT. (I'll grant that "straightforward" may be 
in the eye of the beholder, though.)

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap depreciation

[Rene Ladan]

On Fri, Sep 18, 2020 at 01:58:29PM -0400, Carmel NY wrote:
> On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:
> >On 2020-09-18 11:14, Carmel NY wrote:
> >> Is 'portsnap'
> >> going to be depreciated?  
> >
> >Yes.
> >
> >> If so, when?  
> >
> >I believe when 13.0 is released, or already if you're using a recent 
> >-current.
> >
> >> If is is depreciated, how will
> >> this affect poudriere?  
> >
> >See 
> >https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
> > 
> >and the next sections.
> 
> According to the above page, "The most straightforward way is to have
> Poudriere create a default ports tree for itself, using either
> portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if running
> FreeBSD-CURRENT)" Am I to understand that if I am running 11.4-RELEASE,
> I cannot use subversion?
> 
You can if you specify the -m (method) parameter when creating the
poudriere ports tree.

René
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap depreciation

[David Wolfskill]

On Fri, Sep 18, 2020 at 01:58:29PM -0400, Carmel NY wrote:
> ...
> >https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
> > 
> >and the next sections.
> 
> According to the above page, "The most straightforward way is to have
> Poudriere create a default ports tree for itself, using either
> portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if running
> FreeBSD-CURRENT)" Am I to understand that if I am running 11.4-RELEASE,
> I cannot use subversion?
> 

I don't see any reason why you cannot use subversion: I do, and have
done, since 05 July 2015, running stable/10  at the time; now running
stable/12.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"President Trump can say whatever he likes, but his actions speak for
themselves." -- Dan Berschinski, wounded US Army veteran

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: portsnap depreciation

[Carmel NY]

On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:
>On 2020-09-18 11:14, Carmel NY wrote:
>> Is 'portsnap'
>> going to be depreciated?  
>
>Yes.
>
>> If so, when?  
>
>I believe when 13.0 is released, or already if you're using a recent 
>-current.
>
>> If is is depreciated, how will
>> this affect poudriere?  
>
>See 
>https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
> 
>and the next sections.

According to the above page, "The most straightforward way is to have
Poudriere create a default ports tree for itself, using either
portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if running
FreeBSD-CURRENT)" Am I to understand that if I am running 11.4-RELEASE,
I cannot use subversion?

-- 
Carmel


pgpco7s6kGJJ9.pgp
Description: OpenPGP digital signature

Re: portsnap depreciation

[Pau Amma]

On 2020-09-18 11:14, Carmel NY wrote:

Is 'portsnap'
going to be depreciated?


Yes.


If so, when?


I believe when 13.0 is released, or already if you're using a recent 
-current.



If is is depreciated, how will
this affect poudriere?


See 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree 
and the next sections.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap broken?

[Matthew D. Fuller]

On Wed, Jul 03, 2019 at 10:11:41AM +0200 I heard the voice of
Kurt Jaeger, and lo! it spake thus:
> 
> > With a little script to pull the snapdates:
> > [...]
> 
> Nice! Can you put that script somewhere for others to use ?

It's pretty small and straightforward.  Attached.  It _is_ based on a
bit of reverse-engineering of /usr/sbin/portsnap, so there may well be
a better way already extant of getting the info (and there probably
should be, if there isn't), but it Works For Me...

#!/usr/bin/env perl
use strict;
use warnings;


# Find the server list
my @servers;
{
use Net::DNS;
my $res = Net::DNS::Resolver->new;
my $srv = $res->search('_http._tcp.portsnap.freebsd.org', 'SRV');

die "Nothing from SRV request: @{[$res->errorstring]}\n" unless $srv;

foreach my $rr (grep { $_->type eq 'SRV' } $srv->answer)
{
my $si = {
'priority' => $rr->priority,
'host' => $rr->target,
};
push @servers, $si;
}

@servers = sort {
my $r;
return $r if($r = ($a->{priority} <=> $b->{priority}));
return $r if($r = ($a->{host} cmp $b->{host}));
return 0;
} @servers;
}


# We need to store temp files to go through openssl...
my $tmpdir;
{
use File::Temp qw/tempdir/;
$tmpdir = tempdir(CLEANUP => 1);
die "Failed making tempdir" unless -d $tmpdir;
}


# Load snapshot info and check timestamp from each
for my $s (@servers)
{
my $host = $s->{host};
my $key  = "http://$host/pub.ssl;;
my $snap = "http://$host/latest.ssl;;

my $keyout  = "$tmpdir/$host.key";
my $snapout = "$tmpdir/$host.snap";

use LWP::UserAgent;
my $web  = LWP::UserAgent->new(timeout => 5);
my $res = $web->get($key, ':content_file' => $keyout);
if(!$res->is_success)
{
$s->{failed} = 1;
print STDERR "$host key fetch failed: @{[$res->status_line]}\n";
next;
}

$res = $web->get($snap, ':content_file' => $snapout);
if(!$res->is_success)
{
$s->{failed} = 1;
print STDERR "$host snap fetch failed: 
@{[$res->status_line]}\n";
next;
}


# Now we use openssl to dissect
my @cmd = ( qw(openssl rsautl -pubin -inkey), $keyout, '-verify' );

use IPC::Run3;
my ($out, $err);
run3(\@cmd, $snapout, \$out, \$err);
my $rc = $? >> 8;
if($rc  != 0)
{
$s->{failed} = 1;
print STDERR "$host: openssl returned $rc\n$err\n";
next;
}

# Second field of $out is the timestamp
chomp $out;
my $ts = (split/\|/, $out)[1];
$s->{timestamp} = $ts;
}


# And show the results
my $now = time;
for my $s (@servers)
{
my $host = $s->{host};
(my $sh = $host) =~ s/\.portsnap\.freebsd\.org$//;
if($s->{failed})
{
print "$sh: failed\n";
next;
}

my $pri  = $s->{priority};
my $ts   = $s->{timestamp};

# How old?
my $old = $now - $ts;
my $age;
if($old > 86400)
{
my $days = int($old / 86400);
$age .= "$days days, ";
$old -= ($days * 86400);
}
{
my $hours = int($old / 3600);
$old -= ($hours * 3600);
my $mins = int($old / 60);
$old -= ($mins * 60);
$age .= sprintf("%02d:%02d:%02d", $hours, $mins, $old);
}

use Date::Format;
chomp(my $ftime = ctime($ts));

printf "%20s: $ftime  ($age ago)\n", $sh;
}
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap broken?

[Ashish SHUKLA]

> Any ideas when this will be fixed ?
> 

Looks like it's fixed now.

-- 
Ashish SHUKLA | GPG: F682CDCC39DC0FEAE11620B6C746CFA9E74FA4B0

“We are drowning in information but starved for knowledge.” (John
Naisbitt, "Megatrends")



signature.asc
Description: OpenPGP digital signature

Re: Portsnap broke?

[ajtiM via freebsd-ports]

Yes, looks like it is broken. For me doesn't works from yesterday
morning.


-- 
“Happiness is the meaning and the purpose of life, the whole aim and
end of human existence.”

― Aristotle
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap broken?

[Ashish SHUKLA]

On 7/3/19 7:15 AM, @lbutlr wrote:
> On 2 Jul 2019, at 18:33, Ashish SHUKLA  wrote:
>> I noticed portsnap mirror is outdated for few hours now:
> 
> Out of date based on what? How often are you pulling portsnap?
> 
> (I run portsnap cron update once a day)


I pull few times a day, and it's usually refreshed with-in few hours, as
least for past few years. And the original message I posted was after ~5
minutes ago from my most recent fetch.

-- 
Ashish SHUKLA | GPG: F682CDCC39DC0FEAE11620B6C746CFA9E74FA4B0

“As far as the laws of mathematics refer to reality, they are not
certain; and as far as they are certain, they do not refer to reality.”
("Albert Einstein", "Sidelights on Relativity", 1983)



signature.asc
Description: OpenPGP digital signature

Re: portsnap broken?

[Matthew D. Fuller]

On Tue, Jul 02, 2019 at 07:45:26PM -0600 I heard the voice of
@lbutlr, and lo! it spake thus:
> 
> Out of date based on what? How often are you pulling portsnap?

With a little script to pull the snapdates:

% ./psinfo.pl 
your-org: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
metapeer: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
   ec2-eu-west-1: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
  ec2-ap-southeast-2: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
  ec2-ap-northeast-1: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
   ec2-sa-east-1: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)



-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap broken?

[@lbutlr]

On 2 Jul 2019, at 18:33, Ashish SHUKLA  wrote:
> I noticed portsnap mirror is outdated for few hours now:

Out of date based on what? How often are you pulling portsnap?

(I run portsnap cron update once a day)



-- 
THEY ARE LAUGHING AT ME, NOT WITH ME Bart chalkboard Ep. 7G12


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap update

[Lowell Gilbert]

"Alex V. Petrov"  writes:

> How often should the portsnap database be updated?
> Why is it not updated a long time sometimes?
>
> Now:
> Updating from Tue Aug 21 12:22:20 +07 2018 to Wed Aug 22 02:34:43 +07 2018.

Fourteen hours? I do not think of that as "a long time."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap not honoring WORKDIR and PORTSDIR?

[RW via freebsd-ports]

On Sat, 21 Apr 2018 16:49:13 -0600
Gary Aitken wrote:

> Is portsnap supposed to honor WORKDIR and PORTSDIR?
> 
> These are defined in /etc/portsnap.conf, and it's not clear to me
> whether they are honored only via the .conf file or whether they
> are supposed to be honored from the environment as well.
> 
> They appear to not be honored from the environment, and I'm wondering
> whether that is deliberate or an oversight that should be corrected.
> 


It's deliberate:


# Initialize parameters to null, just in case they're
# set in the environment.
init_params() {
KEYPRINT=""
EXTRACTPATH=""
WORKDIR=""
PORTSDIR=""
...

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Dave Horsfall]

Sigh...  It seems those files were needed after all, as they must refer
to the current system; chalk it up to my lack of understanding of how
"portsnap" works.  I got them back (plus more besides) from a backup
on my MacBook.  What freaked me out was actually looking at the list of 
files being backed up, and thought the worst.

And the sooner I upgrade to FreeBSD-10 the better, I think.

Sorry for wasting everyone's time...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[RW via freebsd-ports]

On Sat, 7 Jan 2017 06:51:44 +1100 (EST)
Dave Horsfall wrote:

> Is there some reason why portsnap cannot clean
> up /var/db/portsnap/files? I've just had to remove a zillion of them,
> a bunch at a time because "rm" choked on the arg list.

If you mean files under /var/db/portsnap/files/ then these are not
temporary files, they are the compressed snapshot, and you should not
delete them without very good reason. They are supposed to persist and
may remain unmodified for many months. 


Zillion is a bit vague, there should be one file for each port plus one
for each file outside a port directory. I have ~27k files.


The temporary .gz files are stored in the directory above and may be
deleted. 


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Dave Horsfall]

On Fri, 6 Jan 2017, Xin LI wrote:

> Because the files are still being used?  What makes you believe they are 
> unused, by the way?

How would I tell?  Some were there since last October, surviving a few 
reboots...

What I do see is the INDEX file containing "...|$tmpfile"; could that be 
the problem?  That INDEX hadn't been cleaned out for some reason?

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Michelle Sullivan]

Dave Horsfall wrote:

(Many responses)

I note that no-one has answered the question which caused me to post the
message in the first place viz: why weren't the files being removed
automatically?  Everyone appears to have missed this point...

I didn't and some of the answers are helpful even if not answering the 
original.


"portsnap fetch" - I wasn't aware it removed the old files at the 
beginning, but will take the other poster's word for that (especially 
after checking the remaining few remaining systems I have on FreeBSD 
would seem to indicate it as a fact)...  however "rm -r /var/db/portsnap 
&& portsnap fetch" is an easy way to clean everything up... if you think 
it's not working correctly.


The index file you will have is: /var/db/portsnap/INDEX

It is possible this was deleted/replaced at some time thereby losing the 
mapping of the files... perhaps a working directory failure (out of 
space etc).. but that should be fixed at every successful fetch as it 
finishes with the following lines of code:


# Move files into their proper locations
rm -f tag INDEX tINDEX
rm -rf files
mv tag.new tag
mv tINDEX.new tINDEX
mv INDEX.new INDEX
mv snap/ files/

('snap' being created new everytime)..

The other part you might not be considering is that the files have to be 
cleaned up on the portsnap server (snapshot builder) itself... but again 
looking at code it should 'just work' - unless someone has tampered with 
it since I downloaded it all and setup my own server...


Regards,

Michelle
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Xin LI]

Because the files are still being used?  What makes you believe they are
unused, by the way?

On Fri, Jan 6, 2017 at 3:34 PM, Dave Horsfall  wrote:

> (Many responses)
>
> I note that no-one has answered the question which caused me to post the
> message in the first place viz: why weren't the files being removed
> automatically?  Everyone appears to have missed this point...
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Bob Eager]

On Sat, 7 Jan 2017 10:34:39 +1100 (EST)
Dave Horsfall  wrote:

> (Many responses)
> 
> I note that no-one has answered the question which caused me to post
> the message in the first place viz: why weren't the files being
> removed automatically?  Everyone appears to have missed this point...
> 

Didn't miss the point, just didn't know the answer!

(and offered a [rather poor] workaround)!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Dave Horsfall]

(Many responses)

I note that no-one has answered the question which caused me to post the 
message in the first place viz: why weren't the files being removed 
automatically?  Everyone appears to have missed this point...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Jonathan Chen]

On 7 January 2017 at 11:30, Bob Eager  wrote:
> On Sat, 7 Jan 2017 06:51:44 +1100 (EST)
> Dave Horsfall  wrote:
>
>> Is there some reason why portsnap cannot clean
>> up /var/db/portsnap/files? I've just had to remove a zillion of them,
>> a bunch at a time because "rm" choked on the arg list.
>>
>> Perhaps a "portsnap clean" command?  I'm surprised that there isn't
>> one.
>
> find and xargs will do it in one go.

find with -delete saves a few processes.
-- 
Jonathan Chen 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Bob Eager]

On Sat, 7 Jan 2017 06:51:44 +1100 (EST)
Dave Horsfall  wrote:

> Is there some reason why portsnap cannot clean
> up /var/db/portsnap/files? I've just had to remove a zillion of them,
> a bunch at a time because "rm" choked on the arg list.
> 
> Perhaps a "portsnap clean" command?  I'm surprised that there isn't
> one.

find and xargs will do it in one go.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[Dave Horsfall]

On Fri, 6 Jan 2017, olli hauer wrote:

> Why?

For the reason I stated; I had to remove hundreds of them by hand.

> As soon you run "portsnap fetch" old files in this directory are purged!

Not here they weren't...

> If you look into /var/db/portsnap/INDEX you can see the mapping of the 
> files

I don't have that file.

> I'm running portsnap on one system since portsnap was introduced and 
> never had issues with cleanups.

Hmmm...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap temporary files

[olli hauer]

On 2017-01-06 20:51, Dave Horsfall wrote:
> Is there some reason why portsnap cannot clean up /var/db/portsnap/files?  
> I've just had to remove a zillion of them, a bunch at a time because "rm" 
> choked on the arg list.
> 
> Perhaps a "portsnap clean" command?  I'm surprised that there isn't one.
> 

Why?

As soon you run "portsnap fetch" old files in this directory are purged!
If you look into /var/db/portsnap/INDEX you can see the mapping of the files

I'm running portsnap on one system since portsnap was introduced and never had 
issues with cleanups.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap tardis

[Randy Bush]

>> Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
> IIUC there was an outage on this server and it has been fixed.

how do we apply for refunds?  :)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap tardis

[Mark Linimon]

On Thu, Oct 13, 2016 at 04:58:56PM +0900, Randy Bush wrote:
> Fetching snapshot tag from your-org.portsnap.freebsd.org... done.

IIUC there was an outage on this server and it has been fixed.

mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap tardis

[Kubilay Kocak]

On 13/10/2016 6:58 PM, Randy Bush wrote:
> a bunch of my 10.3 systems are whining as follows:
> 
> Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
> Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
> Latest snapshot on server is older than what we already have!
> Cowardly refusing to downgrade from Wed Oct 12 01:05:13 UTC 2016
> to Mon Oct 10 19:04:19 UTC 2016.
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 

Hi Randy,

For issues with portsnap (the service, not the base binary), please open
a bug report in Bugzilla under Services -> Portsnap.

It will be assigned to the appropriate contacts

./koobs
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portsnap didn't properly update www/neon

[olli hauer]

On 2015-02-22 19:38, Daniel Morante wrote:
 I have a system that started as FreeBSD 5.x.  Throughout the years it has 
 been updated and upgraded.  Today's it's currently at 9.3-RELEASE.
 
 Recently:
 
 The port www/neon29 was renamed to www/neon and updated to version 0.30.1
 
 Back in 2008:
 
 Rename www/neon to www/neon26 to make the integration of www/neon28 possible
 
 Not sure what happened between no and then, but yesterday portsnap failed to 
 properly update the port skeleton under /usr/ports/www/neon.  There were 
 still some left over files from the last time the port was named neon.
 
  :/usr/ports/www/neon # ls -larths
 total 78
  2 drwxr-xr-x 2 root  wheel   512B Apr 28  2008 files
  2 -rw-r--r-- 1 root  wheel   821B Jan 22  2014 pkg-descr
  6 -rw-r--r-- 1 root  wheel 6k Dec 24 01:03 pkg-plist
  2 -rw-r--r-- 1 root  wheel   130B Dec 24 01:03 distinfo
  2 -rw-r--r-- 1 root  wheel   1.8k Dec 24 01:03 Makefile
 62 drwxr-xr-x  2332 root  wheel61k Feb 22 12:32 ..
  2 drwxr-xr-x 3 root  wheel   512B Feb 22 13:37 .
 
  ls -larths files/
 total 8
 2 -rw-r--r--  1 root  wheel   503B Mar 16  2007 patch-ltmain.sh
 2 -rw-r--r--  1 root  wheel   683B Mar 16  2007 patch-Makefile.in
 2 drwxr-xr-x  2 root  wheel   512B Apr 28  2008 .
 2 drwxr-xr-x  3 root  wheel   512B Feb 22 13:37 ..
 
 Which of course would cause the port install to fail since those patches are 
 outdated:
 
 ===  Applying FreeBSD patches for neon-0.30.1
 1 out of 1 hunks failed--saving rejects to ltmain.sh.rej
 = Patch patch-ltmain.sh failed to apply cleanly.
 = Patch(es) patch-Makefile.in applied cleanly.
 *** [do-patch] Error code 1
 
 Stop in /usr/ports/www/neon.
 *** [install] Error code 1
 
 Stop in /usr/ports/www/neon.
 
 To fix, I delete the 'files' directory.
 

Wow, that's really old leftovers!

The current neon port has no files directory so it can be removed.
Since portsnap is used to keep the tree current you can do the following

# rm -rf www/$all_neon_dirs
# portsnap extract www/neon


Hopefully there are no other leftovers in your portstree

-- 
olli
___
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: portsnap fetch fails (SOLVED)

[Alfred Bartsch]

On 02/10/15 16:54, Alfred Bartsch wrote:
 Hi, after installing FreeBSD 10.1 from downloaded DVD image, I 
 wanted to update my local portstree, but ...
 
 Today, running portsnap fetch fails unexpectedly.
 
 Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. 
 Fetching public key from ec2-eu-west-1.portsnap.freebsd.org... 
 done. Fetching snapshot tag from 
 ec2-eu-west-1.portsnap.freebsd.org... done. Fetching snapshot 
 metadata... done. Fetching snapshot generated at Tue Feb 10 
 01:01:06 CET 2015: 
 9528fd262c49a418579faa6f58bfc3c4040fe96c58d92d100% of   56 MB  153
  kBps 00m00s Extracting snapshot... 
 snap/8bd2f2d1e85bb98a760022703eac8ff47d51700559cfedcb0b158e4eca2fc992.gz:


 
(Empty error message)
 tar: Error exit delayed from previous errors. #
 
 Retrying this command leads to another error message:
 
 #portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 7 
 mirrors found. Fetching snapshot tag from 
 ec2-eu-west-1.portsnap.freebsd.org... done. Fetching snapshot 
 metadata... done. Fetching snapshot generated at Tue Feb 10 
 01:01:06 CET 2015: fetch: 
 http://ec2-eu-west-1.portsnap.freebsd.org/s/9528fd262c49a418579faa6f58bfc3c4040fe96c58d92dde47e79adc8d734b8b.tgz:


 
Requested Range Not Satisfiable
 #
 
 I have to remove all contents from /var/db/portsnap to be able to 
 repeat portsnap fetch, as this command seems to lack a --force 
 option.
 
 uname -a: FreeBSD pcadmin2.incore 10.1-RELEASE FreeBSD
 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 
 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64 
 ___ 
 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
 

Today portsnap fetch works again:

#portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Wed Feb 11 01:00:22 CET 2015:
dcb9b43e217ce204c2e5bd97a020e05e082e2860f08922100% of   71 MB   50
kBps 24m06s
Extracting snapshot... done.
Verifying snapshot integrity... done.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Wed Feb 11 01:00:22 CET 2015 to Wed Feb 11 09:18:12 CET
2015.
Fetching 4 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 20 patches.
(20/20) 100.00%  done.
done.
Applying patches...
done.
Fetching 0 new ports or files... done.

Thanks, and sorry for the noise.

-- 
Sincerely
Alfred Bartsch
Data-Service GmbH
___
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: portsnap / pkng strangeness / dc divide by zero

[Jakub Lach]

Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Fri Mar 21 00:55:47 CET 2014 to Fri Mar 21 01:10:01 CET 2014.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 0 patches. 
dc: divide by zero   
dc: divide by zero   
(0/0) 0.00%  done. 

once again



--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/portsnap-pkng-strangeness-dc-divide-by-zero-tp5885503p5896148.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
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: portsnap corruption

[Loïc BLOT]

Hello,
try this:

rm -R /var/db/fportsnap/files/*.gz

and then launch portsnap fetch another time

-- 
Best regards,
Loïc BLOT, 
UNIX systems, security and network engineer
http://www.unix-experience.fr



Le jeudi 24 octobre 2013 à 11:15 +0200, Łukasz Wąsikowski a écrit :
 Hi,
 
 I've tried to update ports on few servers, got this:
 
 # portsnap fetch extract
 Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
 Fetching public key from ec2-eu-west-1.portsnap.freebsd.org... done.
 Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
 Fetching snapshot metadata... done.
 Fetching snapshot generated at Thu Oct 24 02:04:53 CEST 2013:
 c54e7bf053e2425753affcd01e2c4ebf11f411ecbcff15100% of   69 MB 2138 kBps
 00m33s
 Extracting snapshot... done.
 Verifying snapshot integrity... done.
 Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
 Fetching snapshot metadata... done.
 Updating from Thu Oct 24 02:04:53 CEST 2013 to Thu Oct 24 09:34:07 CEST
 2013.
 Fetching 4 metadata patches... done.
 Applying metadata patches... done.
 Fetching 4 metadata files... gunzip: (stdin): unexpected end of file
 metadata is corrupt.
 


signature.asc
Description: This is a digitally signed message part

Re: portsnap fetch failed on FreeBSD 8.2

[Łukasz Wąsikowski]

W dniu 2013-05-28 17:51, Xu Zhe pisze:

 I got a task to port Java to a private-built FreeBSD system which is
 branched from FreeBSD 8.2. As a start of this, I tried to learn port
 stuffs, and did 'portsnap fetch' but failed. After that, I tried to
 change portsnap server, and I even tried a generic FreeBSD 8.2 version,
 which failed too with merely the same error. Here is what I got in most
 of the cases (not totally the same for each time, but I suppose they are
 familiar):

Please take a look at this:
http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-May/06.html

Problem you've described should be fixed by now. If it's not please wait
for a few more hours.

-- 
best regards,
Lukasz Wasikowski
___
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: portsnap fetch failed on FreeBSD 8.2

[Xu Zhe]

于 5/29/13 12:08 AM, Łukasz Wąsikowski 写道:

W dniu 2013-05-28 17:51, Xu Zhe pisze:


I got a task to port Java to a private-built FreeBSD system which is
branched from FreeBSD 8.2. As a start of this, I tried to learn port
stuffs, and did 'portsnap fetch' but failed. After that, I tried to
change portsnap server, and I even tried a generic FreeBSD 8.2 version,
which failed too with merely the same error. Here is what I got in most
of the cases (not totally the same for each time, but I suppose they are
familiar):

Please take a look at this:
http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-May/06.html

Problem you've described should be fixed by now. If it's not please wait
for a few more hours.


Got it. Thanks!

Peter
___
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: portsnap and the imminent demise of svn-cvs ports tree export

[Thomas Mueller]

 Date: Mon, 21 Jan 2013 12:01:05 +1100

 How do you work that out?  None of the headers you've included show
 any problem.  John sent his mail at 010105UT on 21st, and your headers
 say you received it at 095334UT on 21st - nearly 9 hours later.  The
 X-Apparently-To header is 010132UT on the 21st (about 3s after FreeBSD
 forwarded it to me, se quite realistic).

 --
 Peter Jeremy

I think I might have misread something mentally transferring 3 at the end of 
2013 to make Jan 21 into Jan 23: maybe the wrong time of day, too late going
to bed.

Tom
___
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: portsnap and the imminent demise of svn-cvs ports tree export

[Peter Jeremy]

On 2013-Jan-22 22:45:24 -0500, Thomas Mueller mueller6...@bellsouth.net wrote:
Your date is ahead of what the headers of your message say:

From owner-freebsd-po...@freebsd.org Mon Jan 21 09:53:34 2013
Received: from pop.att.yahoo.com (pop2.sbc.mail.vip.ne1.yahoo.com 
[98.138.197.207])
by mueller6722.bellsouth.net (mpop-1.0.23) with POP3
for arlene; Mon, 21 Jan 2013 09:53:34 +
X-Apparently-To: mueller6...@bellsouth.net via 98.139.172.126; Sun, 20 Jan 
2013 17:01:32 -0800

...

Date: Mon, 21 Jan 2013 12:01:05 +1100

How do you work that out?  None of the headers you've included show
any problem.  John sent his mail at 010105UT on 21st, and your headers
say you received it at 095334UT on 21st - nearly 9 hours later.  The
X-Apparently-To header is 010132UT on the 21st (about 3s after FreeBSD
forwarded it to me, se quite realistic).

-- 
Peter Jeremy


pgpQhDRnUR4Hv.pgp
Description: PGP signature

Re: portsnap and the imminent demise of svn-cvs ports tree export

[Simon L. B. Nielsen]

On 21 January 2013 01:01, John Marshall
john.marsh...@riverwillow.com.au wrote:
 We are on notice that the current ports tree will be soon no longer
 available via CVSup and friends.  General consumers of the FreeBSD ports
 tree are being encouraged to switch to portsnap.

 http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/49.html

 The presence of the file LASTCOMMIT.txt, and the content of the
 $FreeBSD$ lines, in a portsnap-generated ports tree indicate that
 portsnap sources its data from a CVS export of the tree.  Are there

That is correct.

 plans to migrate the portsnap source to the subversion tree before the
 end of February?

Colin is working right now at migrating it. As it is a somewhat larger
task (it also includes some cleanup of the portsnap codebase) it
hasn't been done yet.

I can guarantee that we will not make portsnap stop working by killing
svn2cvs for ports before portsnap is migrated, but I don't think it
should be a problem.

While portsnap hasn't run as reliably as we want over the last two
month due to high churn of changes on the FreeBSD.org sites (as we
have basically been redoing all infrastructure for scratch) it is
fully supported by clusteradm/security-officer. (Lack of monitoring
after the security incident has also really hurt us, but that's coming
back these days).

PS. I consider it a very fair question.

PPS. portsnap build recently moved to a new server which decreased the
portsnap build time so changes should now show up even faster in
portsnap.

-- 
Simon L. B. Nielsen
Hat: FreeBSD.org clusteradm and FreeBSD Security Officer
___
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: portsnap - overwrite local changes

[Guido Falsi]

On 01/22/13 13:10, Oliver Lehmann wrote:

Hi,

in case I made some local modifications to a ports Makefile in the
past with CVSup it was easy to get everything back in-sync by just
running CVSup. With portsnap fetch update, my modified Makefile stays
modified. What is the suggested way in syncing my local portstree 1:1
with the official portstree?



If you use small modifications on a ingle system(or just a few) you 
could track the ports tree with subversion, which will be happy to keep 
and try to merge your local modifcations. You can also diff and revert 
your modifications using it, which can be quite handy.


Disvantage is you will sometime need to merge conflicts which could 
require you to study subversion more than what you really want.


If instead you have modifications to your ports tree you want to merge 
to more than just a few machines(more than two, is already enough) I 
suggest you investigate ports-mgmt/portshaker.


It allows you to overlay the ports tree with your modifications. You can 
track your modifications using some VCS (subversion, or git if you lke 
it more for example) and just make the various machines pull the 
official tree, your modifications and merge them.


It does require that you keep your local modifications up to date anyway 
though.


Hope this helps.

--
Guido Falsi m...@madpilot.net
___
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: portsnap - overwrite local changes

[Guido Falsi]

On 01/22/13 13:10, Oliver Lehmann wrote:

Hi,

in case I made some local modifications to a ports Makefile in the
past with CVSup it was easy to get everything back in-sync by just
running CVSup. With portsnap fetch update, my modified Makefile stays
modified. What is the suggested way in syncing my local portstree 1:1
with the official portstree?



If you use small modifications on a single system(or just a few) you 
could track the ports tree with subversion, which will be happy to keep 
and try to merge your local modifications. You can also diff and revert 
your modifications using it, which can be quite handy.


Disvantage is you will sometime need to merge conflicts which could 
require you to study subversion more than what you really want.


If instead you have modifications to your ports tree you want to merge 
to more than just a few machines(more than two, is already enough) I 
suggest you investigate ports-mgmt/portshaker.


It allows you to overlay the ports tree with your modifications. You can 
track your modifications using some VCS (subversion, or git if you like 
it more for example) and just make the various machines pull the 
official tree, your modifications and merge them.


It does require that you keep your local modifications up to date anyway 
though.


Hope this helps.

--
Guido Falsi m...@madpilot.net
___
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: portsnap - overwrite local changes

[Oliver Lehmann]

Guido Falsi m...@madpilot.net wrote:

If you use small modifications on a ingle system(or just a few) you  
could track the ports tree with subversion, which will be happy to  
keep and try to merge your local modifcations. You can also diff and  
revert your modifications using it, which can be quite handy.


Disvantage is you will sometime need to merge conflicts which could  
require you to study subversion more than what you really want.


Ok, subversion came also to my mind but I guess portsnap is faster then
svn is. The thing with svn is, that I would always need to examine the
logs if there where conflicts generated.

I don't want to keep my local changes. I would like to have command
which just gets me a 1:1 copy of the current ports tree and deletes
or overwrites my local changes. There is nothing I want to get merged.
___
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: portsnap - overwrite local changes

[Guido Falsi]

On 01/22/13 14:00, Oliver Lehmann wrote:


Guido Falsi m...@madpilot.net wrote:


If you use small modifications on a ingle system(or just a few) you
could track the ports tree with subversion, which will be happy to
keep and try to merge your local modifcations. You can also diff and
revert your modifications using it, which can be quite handy.

Disvantage is you will sometime need to merge conflicts which could
require you to study subversion more than what you really want.


Ok, subversion came also to my mind but I guess portsnap is faster then
svn is. The thing with svn is, that I would always need to examine the
logs if there where conflicts generated.

I don't want to keep my local changes. I would like to have command
which just gets me a 1:1 copy of the current ports tree and deletes
or overwrites my local changes. There is nothing I want to get merged.


Ok, I misunderstood your problem then.

I think your best bet is deleting the old tree and extracting it again 
with portsnap, this would not be very fast though.


If you use zfs you could leverage it, using snapshots and clones. You 
could snapshot the official tree, clone it, modify the cloned one(munted 
in /usr/ports) and when you upgrade destroy the clone and create a new 
clone from the updated official tree, which would be clean without local 
modifications.


subversion could help too. You could perform a svn revert -R . 
followed by svn up. This would be faster than rm -r *  portsnap 
extract (done in /usr/ports, obviously)


--
Guido Falsi m...@madpilot.net
___
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: portsnap - overwrite local changes

[Joseph A. Nagy, Jr]

On 01/22/13 07:00, Oliver Lehmann wrote:


Guido Falsi m...@madpilot.net wrote:


If you use small modifications on a ingle system(or just a few) you
could track the ports tree with subversion, which will be happy to
keep and try to merge your local modifcations. You can also diff and
revert your modifications using it, which can be quite handy.

Disvantage is you will sometime need to merge conflicts which could
require you to study subversion more than what you really want.


Ok, subversion came also to my mind but I guess portsnap is faster then
svn is. The thing with svn is, that I would always need to examine the
logs if there where conflicts generated.

I don't want to keep my local changes. I would like to have command
which just gets me a 1:1 copy of the current ports tree and deletes
or overwrites my local changes. There is nothing I want to get merged.


I use svn in a cron job to update my ports tree and the few times I make 
a local change I don't think I've ever had it stay past the next update. 
I don't issue any special commands, just 'svn up /usr/ports' via cron 
(along with a check to see what's been updated). I know when I run it 
manually and there is a conflict, it will tell me about a merge-conflict 
and ask me which file to keep (mine or theirs), selecting theirs, afaik, 
overwrites my local file.



--
Yours in Christ,

Joseph A Nagy Jr
Whoever loves instruction loves knowledge, But he who hates correction
is stupid. -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original content CopyFree (F) under the OWL http://owl.apotheon.org
___
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: portsnap - overwrite local changes

[Oliver Lehmann]

Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:
I know when I run it manually and there is a conflict, it will tell  
me about a merge-conflict and ask me which file to keep (mine or  
theirs), selecting theirs, afaik, overwrites my local file.


And when there is no conflict and it can be merged, you have a merged
file. And in some point in time your local /usr/ports is messed up
with forgotten local changes and so on... I just wanna make sure to
automatically clean up my /usr/ports. CVSup did this :(
___
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: portsnap - overwrite local changes

[Guido Falsi]

On 01/22/13 16:59, Oliver Lehmann wrote:


Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:

I know when I run it manually and there is a conflict, it will tell me
about a merge-conflict and ask me which file to keep (mine or theirs),
selecting theirs, afaik, overwrites my local file.


And when there is no conflict and it can be merged, you have a merged
file. And in some point in time your local /usr/ports is messed up
with forgotten local changes and so on... I just wanna make sure to
automatically clean up my /usr/ports. CVSup did this :(


As I said, svn revert -R . does remove local changes to tracked files. 
It will ignore added files it does not know about.


--
Guido Falsi m...@madpilot.net
___
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: portsnap - overwrite local changes

[Joseph A. Nagy, Jr]

On 01/22/13 09:59, Oliver Lehmann wrote:


Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:

I know when I run it manually and there is a conflict, it will tell me
about a merge-conflict and ask me which file to keep (mine or theirs),
selecting theirs, afaik, overwrites my local file.


And when there is no conflict and it can be merged, you have a merged
file. And in some point in time your local /usr/ports is messed up
with forgotten local changes and so on... I just wanna make sure to
automatically clean up my /usr/ports. CVSup did this :(


Perhaps merge is the wrong term (but its what svn uses) but what it 
really does is overwrite the local file with the one from the repo. I've 
been doing that for months now with no problems.


--
Yours in Christ,

Joseph A Nagy Jr
Whoever loves instruction loves knowledge, But he who hates correction
is stupid. -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original content CopyFree (F) under the OWL http://owl.apotheon.org
___
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: portsnap - overwrite local changes

[Guido Falsi]

On 01/22/13 17:21, Joseph A. Nagy, Jr wrote:

On 01/22/13 09:59, Oliver Lehmann wrote:


Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:

I know when I run it manually and there is a conflict, it will tell me
about a merge-conflict and ask me which file to keep (mine or theirs),
selecting theirs, afaik, overwrites my local file.


And when there is no conflict and it can be merged, you have a merged
file. And in some point in time your local /usr/ports is messed up
with forgotten local changes and so on... I just wanna make sure to
automatically clean up my /usr/ports. CVSup did this :(


Perhaps merge is the wrong term (but its what svn uses) but what it
really does is overwrite the local file with the one from the repo. I've
been doing that for months now with no problems.



No, this is not correct. It depends on the kind of conflict. If you have 
not conflicting changes in your local copy those will be merged. There 
will be a G letter besides those files in the svn up output. No error 
message. If the change is conflicting it will ask you what to do.


If the file has no change in the repo but has local changes local 
changes will survive. If you instead always use svn checkout then yes, 
it will overwrite changes.


If subversion did such a thing(destroying local changes silently) it 
would be a very big problem for developers.


--
Guido Falsi m...@madpilot.net
___
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: portsnap - overwrite local changes

[RW]

On Tue, 22 Jan 2013 16:59:56 +0100
Oliver Lehmann wrote:

 
 Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:
  I know when I run it manually and there is a conflict, it will
  tell me about a merge-conflict and ask me which file to keep (mine
  or theirs), selecting theirs, afaik, overwrites my local file.
 
 And when there is no conflict and it can be merged, you have a merged
 file. And in some point in time your local /usr/ports is messed up
 with forgotten local changes and so on... I just wanna make sure to
 automatically clean up my /usr/ports. CVSup did this :(

Not necessarily correctly. That reverts any modifications, but it wont
necessarily remove files that need to be removed and which may cause
problems if left in place. This is why portsnap extract removes port
directories before writing a clean copy.

I presume you could extract a single port if you can't spare the time
for a full extract. 
___
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: portsnap and the imminent demise of svn-cvs ports tree export

[Thomas Mueller]

   (current time: Wed 23 Jan 2013 02:43:43 AM UTC) --]
 [-- End of PGP output --]

 [-- The following data is signed --]

 We are on notice that the current ports tree will be soon no longer
 available via CVSup and friends.  General consumers of the FreeBSD ports
 tree are being encouraged to switch to portsnap.

 http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/49.html

 The presence of the file LASTCOMMIT.txt, and the content of the
 $FreeBSD$ lines, in a portsnap-generated ports tree indicate that
 portsnap sources its data from a CVS export of the tree.  Are there
 plans to migrate the portsnap source to the subversion tree before the
 end of February?

 # cd /usr/ports
 # make update
 --
  Running portsnap
 --
 Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
 Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
 Fetching snapshot metadata... done.
 Updating from Sun Jan 20 16:00:15 PST 2013 to Sun Jan 20 16:05:39 PST 2013.
 Fetching 4 metadata patches... done.
 Applying metadata patches... done.
 Fetching 0 metadata files... done.
 Fetching 5 patches... done.
 Applying patches... done.
 Fetching 1 new ports or files... done.
 Removing old files and directories... done.
 Extracting new files:
 /usr/ports/LASTCOMMIT.txt
 /usr/ports/lang/basic256/
 /usr/ports/sysutils/less/
 /usr/ports/textproc/mifluz/
 /usr/ports/www/Makefile
 /usr/ports/www/p5-LWP-Protocol-PSGI/
 Building new INDEX files... done.
 # ident /usr/ports/www/Makefile
 /usr/ports/www/Makefile:
  $FreeBSD: ports/www/Makefile,v 1.3300 2013/01/20 23:49:48 svnexp Exp $

 Thank you.

 --
 John Marshall

 [-- End of signed data --]

Your date is ahead of what the headers of your message say:

From owner-freebsd-po...@freebsd.org Mon Jan 21 09:53:34 2013
Received: from pop.att.yahoo.com (pop2.sbc.mail.vip.ne1.yahoo.com 
[98.138.197.207])
by mueller6722.bellsouth.net (mpop-1.0.23) with POP3
for arlene; Mon, 21 Jan 2013 09:53:34 +
X-Apparently-To: mueller6...@bellsouth.net via 98.139.172.126; Sun, 20 Jan 2013 
17:01:32 -0800

...

Date: Mon, 21 Jan 2013 12:01:05 +1100

Anyway, my latest LASTCOMMIT.txt shows


## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/310745
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
## SVN ## 

## SVN ## r310745 | araujo | 2013-01-21 03:39:17 + (Mon, 21 Jan 2013) | 8 
lines
## SVN ## Changed paths:
## SVN ##M /head/sysutils/syslinux/Makefile
## SVN ##M /head/sysutils/syslinux/distinfo
## SVN ##M /head/sysutils/syslinux/files/patch-Makefile
## SVN ##M /head/sysutils/syslinux/files/patch-libinstaller-syslxopt.c
## SVN ##M /head/sysutils/syslinux/pkg-descr
## SVN ##M /head/sysutils/syslinux/pkg-plist
## SVN ## 
## SVN ## - Update to 5.00.
## SVN ## - Update MASTER_SITES.
## SVN ## - Add MAKE_JOBS_SAFE.
## SVN ## - Trim header.
## SVN ## 
## SVN ## PR:   ports/174180
## SVN ## Submitted by: KATO Tsuguru tkato...@yahoo.com
## SVN ## 
## SVN ## 



Tom
___
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: portsnap fetch

[Michael Gmelin]

On Sun, 18 Nov 2012 05:35:30 -0600
ajtiM lum...@gmail.com wrote:

 Hi!
 
 I am using FreeBSD 9.1 RC-3. All the time I use portsnap. Today I ran 
 portsnap fetch  portsnap extract
 and it stopped extract on
 /usr/ports/multimedia/mplayer2/
 files/aa53f85d11a3fd077801a5d63b76022647420c8c480f9022315806e911aa33dd.gz
 not found -- snapshot corrupt.
 
 All /usr/ports after /mail are empty and the last is mplayer
 in /multimedia.
 
 Is it results of maintaining or is something else.
 
 Thanks in advance.
 
 Mitja

Start with a fresh ports tree

portsnap fetch  portsnap extract

(I also did this beforehand, mostly out of paranoia:
rm /var/db/portsnap/*
rm -rf /usr/ports
)

See here for details why:
http://www.freebsd.org/news/2012-compromise.html


 
 http://www.redbubble.com/people/lumiwa
 ___
 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





-- 
Michael Gmelin
___
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: portsnap fetch

[ajtiM]

On Sunday 18 November 2012 05:35:30 ajtiM wrote:
 Hi!
 
 I am using FreeBSD 9.1 RC-3. All the time I use portsnap. Today I ran
 portsnap fetch  portsnap extract
 and it stopped extract on
 /usr/ports/multimedia/mplayer2/
 files/aa53f85d11a3fd077801a5d63b76022647420c8c480f9022315806e911aa33dd.gz
 not found -- snapshot corrupt.
 
 All /usr/ports after /mail are empty and the last is mplayer in
 /multimedia.
 
 Is it results of maintaining or is something else.
 
 Thanks in advance.
 
 Mitja
 
 http://www.redbubble.com/people/lumiwa

I did as was suggested:
rm /var/db/portsnap/*
rm -rf /usr/ports

and portsnap fetch  portsnap extract works :).

Thank you.


Mitja

http://www.redbubble.com/people/lumiwa
___
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: portsnap

[Christer Solskogen]

On Tue, Nov 13, 2012 at 11:19 PM, Jason Garrett kinged...@gmail.com wrote:
 On Mon, Nov 12, 2012 at 6:13 PM, ajtiM lum...@gmail.com wrote:

 On Monday 12 November 2012 17:46:44 Aldis Berjoza wrote:
  13.11.2012, 01:27, ajtiM lum...@gmail.com:
   Hi!
  
   Is it something wrong with portsnap server or is something wrong with
 my
   system. When I run portsnap...:
   portsnap fetch update
   Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
   Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
   Latest snapshot on server matches what we already have.
   No updates needed.
   Ports tree is already up to date.
  
   but on http://www.freshports.org/ are many new ports (I like update
   Sage).
  
   Thanks in advance.
  
   Mitja
 
  It takes some time for mirrors to catch up.

 But is it about 12 hours okay (maybe more)?
 Thanks.

 Mitja
 


 I have the same problem going on 2 days now...


Same. This is in Europe.

-- 
chs,
___
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: portsnap problem

[ajtiM]

On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote:
 Hello,
 
 for a day already, portsnap fetch seems not to fetch newest changes.
 freshports shows lots of changes, port portsnap fetch says there
 everything is up to date.
 I checked that the ports are really newer in freshports than in my machine.
 I also removed everything in /usr/ports and /var/db/portsnap and issued
 portsnap fetch extract, but it did not help.
 
 Maybe some job that creates patches for portsnap died?
 
 Herby
 ___
 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

I have the same problem on my 9.0-Release.

Mitja

http://jpgmag.com/people/lumiwa
___
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: portsnap problem

[Sergio de Almeida Lenzi]

Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu:

 On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote:
  Hello,
  
  for a day already, portsnap fetch seems not to fetch newest changes.
  freshports shows lots of changes, port portsnap fetch says there
  everything is up to date.
  I checked that the ports are really newer in freshports than in my machine.
  I also removed everything in /usr/ports and /var/db/portsnap and issued
  portsnap fetch extract, but it did not help.
  
  Maybe some job that creates patches for portsnap died?
  

Or just that ports system is frozen because of the 8.3 release???

Occam's razor:

when you have two or more competing theories 
that make exactly the same predictions,
the simpler one is the better.


[]
Sergio
___
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: portsnap problem

[René Ladan]

http://www.rene-ladan.nl/

GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)



2012/3/11 Sergio de Almeida Lenzi lenzi.ser...@gmail.com:
 Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu:

 On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote:
  Hello,
 
  for a day already, portsnap fetch seems not to fetch newest changes.
  freshports shows lots of changes, port portsnap fetch says there
  everything is up to date.
  I checked that the ports are really newer in freshports than in my machine.
  I also removed everything in /usr/ports and /var/db/portsnap and issued
  portsnap fetch extract, but it did not help.
 
  Maybe some job that creates patches for portsnap died?
 

 Or just that ports system is frozen because of the 8.3 release???

No, Herby's theory is far more likely. The ports system is open as
ususal, except that no big changes can go in and all commits have to
be tagged with the Feature safe tag (and actually be feature safe).

René
___
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: portsnap problem

[Chris Rees]

On 11 March 2012 12:55, Sergio de Almeida Lenzi lenzi.ser...@gmail.com wrote:
 Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu:

 On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote:
  Hello,
 
  for a day already, portsnap fetch seems not to fetch newest changes.
  freshports shows lots of changes, port portsnap fetch says there
  everything is up to date.
  I checked that the ports are really newer in freshports than in my machine.
  I also removed everything in /usr/ports and /var/db/portsnap and issued
  portsnap fetch extract, but it did not help.
 
  Maybe some job that creates patches for portsnap died?
 

 Or just that ports system is frozen because of the 8.3 release???

 Occam's razor:

 when you have two or more competing theories
 that make exactly the same predictions,
 the simpler one is the better.

CC: portsnap maintainer

Although that might be a reasonable explanation, it's much more likely
that portsnap data is not being generated right now.

Chris
___
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: portsnap problem

[Matthew Seaman]

On 11/03/2012 12:55, Sergio de Almeida Lenzi wrote:
 Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu:
 
 On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote:
 Hello,

 for a day already, portsnap fetch seems not to fetch newest changes.
 freshports shows lots of changes, port portsnap fetch says there
 everything is up to date.
 I checked that the ports are really newer in freshports than in my machine.
 I also removed everything in /usr/ports and /var/db/portsnap and issued
 portsnap fetch extract, but it did not help.

 Maybe some job that creates patches for portsnap died?

 
 Or just that ports system is frozen because of the 8.3 release???
 
 Occam's razor:
 
 when you have two or more competing theories 
 that make exactly the same predictions,
 the simpler one is the better.

That's not it.  Ports only gets frozen completely for a matter of an
hour or so as part of the release process.  Instead, it spends much of
the period leading up to a release in Slush -- which is the case at
the moment.

Slush doesn't mean that ports stop being updated.  On the contrary,
there have been some twenty-odd ports updated just this morning as I can
see from the cvs-ports@ mailing list.

Slush does mean that changes with large scale ramifications are not
permitted, so last week's perl-related updates for instance, would not
be allowed right now.

The portsnap thing is a real problem.  No idea what or why or how long
to fix, but I'd hazard a guess that the answer to the last is by later
today.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Re: portsnap problem

[Colin Percival]

On 03/11/12 06:00, Chris Rees wrote:
 CC: portsnap maintainer

Thanks!  I don't regularly read freebsd-ports (funny for the portsnap maintainer
to not be subscribed, I know, but I get way too much email already...).

 Although that might be a reasonable explanation, it's much more likely
 that portsnap data is not being generated right now.

Almost correct -- I just restarted the portsnap builds a few minutes ago.  They
were broken for about 18 hours; I'm not entirely certain of the cause but I
suspect a freebsd.org DNS glitch was at least partly responsible.

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
___
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: portsnap problem

[Jerry]

On Sun, 11 Mar 2012 09:55:27 -0300
Sergio de Almeida Lenzi articulated:

 Or just that ports system is frozen because of the 8.3 release???
 
 Occam's razor:
 
 when you have two or more competing theories 
 that make exactly the same predictions,
 the simpler one is the better.

Actually, there are numerous razors, Occam's being only one.

Occam's razor (also written as Ockham's razor) is the English
equivalent of the Latin lex parsimoniae --- the law of parsimony,
economy or succinctness. It is a principle urging one to select among
competing hypotheses that which makes the fewest assumptions and
thereby offers the simplest explanation of the effect.

It is usually translated as, simpler explanations are, other things
being equal, generally better than more complex ones. The key phase
being other things being equal.

Personally, I am a strong believer in Murphy's Law.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
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: portsnap fetch update: look: tINDEX.new: File too large

[Jerry]

On Sat, 15 Oct 2011 08:47:24 +0200
Hartmann, O. articulated:

 This morning, I get this when trying to update the local portssystem:
 
 Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
 Fetching snapshot tag from portsnap6.FreeBSD.org... done.
 Fetching snapshot metadata... done.
 look: tINDEX.new: File too large
 
 Portsnap metadata appears bogus.
 Cowardly refusing to proceed any further.
 
 Any hint how to proceed further?

Well, the first hint would be that you could cease cross-posting this
event. Second, did you try it again at least one hour after the initial
phenomena to confirm if the condition still exists?

In any event, it works here. Sat Oct 15 2011 08:47:15 EDT

-- 
Jerry ✌
jerry+po...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
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: portsnap

[Desmond da Peoples]

You need to enable the CVSup file. Look in the handbook for installing the 
ports tree.
Go to chapter 4.5 in the freebsd handbook and follow the directions there.
Be sure that you have a good connection.


 Date: Fri, 9 Oct 2009 09:15:23 -0700
 From: edwar...@yahoo.com
 To: po...@freebsd.org
 CC: po...@freebsd.org
 Subject: portsnap
 
 Sirs:
 
 I am attempting to load FreeBSD-7.0.  The computer I am using has no internet 
 connection.  Could you please let me have the location and name of the 
 file(s) that portsnap needs to do its 'extract' thing.
 
 Your help will be appreciated.
 
 Edward L Shriver
 edwar...@yahoo.com
 
 
   
 ___
 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
  
_
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/___
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: portsnap

[b. f.]

Desmond da Peoples wrote:
You need to enable the CVSup file. Look in the handbook for installing the 
ports tree.
Go to chapter 4.5 in the freebsd handbook and follow the directions there.
Be sure that you have a good connection.

?! Which part of the OP's The computer I am using has no internet
connection didn't you understand?

 I am attempting to load FreeBSD-7.0.

Why 7.0?  You should probably use = 7.2.

The computer I am using has no internet connection.  Could you please let 
me have the location and name of the file(s) that portsnap needs to do its 
'extract' thing.

You can read portsnap.sh (it is a shell script) to see what is going
on.  It may need to grab a snapshot, metadata, tags, and keys from one
or more of a list of portsnap servers.  Since the files it needs
change over time, and since by manually downloading these files you
will be bypassing some of the integrity and security checks that are
the main benefit of portsnap anyway, I think it will be more
convenient for you to just download a new ports and index tarball,
from, for example:

ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz
http://www.FreeBSD.org/ports/INDEX-7.bz2

or one of the mirrors listed in the FreeBSD handbook, and unpack it
into /usr/ports or whatever using tar(1) (don't forget to preserve
your distfiles subdirectory if it is part of the old ports tree that
you will need to delete first before unpacking the new one.)  If you
end up using a version of FreeBSD other than 7, you will need to
substitute that version for the 7 in the URL of the index file above.

If you are going to be updating often, then you should probably use
some form of incremental update, so you are not downloading a 45MB
tarball each time -- you could run a cvs or rsync client on the
machine that has an internet connection, but it would probably be most
convenient to just learn to use ctm(1), which was designed for this
purpose.  (See

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ctm.html

.) Then you could subscribe to the ctm-ports-cur mailing list and get
your small incremental updates via email, after making only one big
download.  Don't forget that you'll have to fetch any new port
distfiles manually as well -- running 'make fetch-recursive-list' the
origins of each of the ports that need to be added or updated can help
you compile a list of the needed files.  For example, after unpacking
your new ports tree, you could run:

pkg_version -oIq -l '' | tr -d ' ' | xargs -I % make -C /usr/ports/%
fetch-recursive-list

to get a list of any new distfiles for installed ports that have been updated.

b.
___
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: portsnap

[John Marshall]

On Fri, 09 Oct 2009, 09:15 -0700, Edward Shriver wrote:
 I am attempting to load FreeBSD-7.0.? The computer I am using has no internet 
 connection.? Could you please let me have the location and name of the 
 file(s) that portsnap needs to do its 'extract' thing.

On a system that _does_ have Internet connectivity:
 - Do 'portsnap fetch' so that you have a current ports tree snapshot
 - Take a backup of /var/db/portsnap

On the machine you are installing:
 - Restore /var/db/portsnap from the backup
 - Do 'portsnap extract'

-- 
John Marshall


pgpDDcn7Qqi48.pgp
Description: PGP signature

Re: portsnap can't access portsnap[124].freebsd.org

[Glen Barber]

On Sat, May 30, 2009 at 12:48 AM, Scott Bennett benn...@cs.niu.edu wrote:

Can you paste the 'ANSWER SECTON' from:

  'dig portsnap2.freebsd.org'

     Sure, but I'm curious to know why.  The names all do resolve to A RRs,
 and pings to each by name did get echos back.  Here it is, although I did
 terminate the domain name by habit.  Surely portsnap must not be so silly
 as to pass unterminated names to the resolver.  (Actually, I'm including
 the whole output, not just the answer section.)


To make sure it wasn't a DNS problem (or DNS poisoning / hijacking).


 ;; ANSWER SECTION:
 portsnap2.freebsd.org.  3600    IN      A       72.21.59.250


Same output for me..


-- 
Glen Barber
___
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: portsnap can't access portsnap[124].freebsd.org

[Scott Bennett]

 On Sat, 30 May 2009 05:32:39 -0400 Glen Barber glen.j.bar...@gmail.com
wrote:
On Sat, May 30, 2009 at 12:48 AM, Scott Bennett benn...@cs.niu.edu wrote:

Can you paste the 'ANSWER SECTON' from:

 =A0'dig portsnap2.freebsd.org'

 =A0 =A0 Sure, but I'm curious to know why. =A0The names all do resolve to=
 A RRs,
 and pings to each by name did get echos back. =A0Here it is, although I d=
id
 terminate the domain name by habit. =A0Surely portsnap must not be so sil=
ly
 as to pass unterminated names to the resolver. =A0(Actually, I'm includin=
g
 the whole output, not just the answer section.)


To make sure it wasn't a DNS problem (or DNS poisoning / hijacking).


 ;; ANSWER SECTION:
 portsnap2.freebsd.org. =A03600 =A0 =A0IN =A0 =A0 =A0A =A0 =A0 =A0 72.21.5=
9.250


Same output for me..

 Thanks for that much, then, Glen.  So we still don't know what is wrong.
I did try it again around midnight CDT, and it still failed the same way.
 In the meantime, my frustration and impatience got the better of me, and
I touched up a copy of ports-supfile and csupped it.  I also used portinstall,
which was there because I had selected it as a package during the 7.2-RELEASE
installation, to install portmaster, which is now running the builds.
 Nevertheless, I'd still rather switch back to portsnap ASAP after this,
so I'm still hoping someone has an idea what's wrong with portsnap or the
systems at freebsd.org.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army.   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: portsnap can't access portsnap[124].freebsd.org

[John Marshall]

On Sat, 30 May 2009, 05:39 -0500, Scott Bennett wrote:
  Thanks for that much, then, Glen.  So we still don't know what is wrong.
 I did try it again around midnight CDT, and it still failed the same way.
  In the meantime, my frustration and impatience got the better of me, and
 I touched up a copy of ports-supfile and csupped it.  I also used portinstall,
 which was there because I had selected it as a package during the 7.2-RELEASE
 installation, to install portmaster, which is now running the builds.
  Nevertheless, I'd still rather switch back to portsnap ASAP after this,
 so I'm still hoping someone has an idea what's wrong with portsnap or the
 systems at freebsd.org.

Have you excluded local factors (proxy servers, firewalls)?  I have not
seen any issues at all with portsnap.  I have done a few fetches today
and haven't seen any problems at all.  This one a few minutes ago
happened to hit portsnap2.  I noticed that one of the earlier ones today
was from portsnap1.

  # portsnap fetch
  Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
  Fetching snapshot tag from portsnap2.FreeBSD.org... done.
  Fetching snapshot metadata... done.
  Updating from Sat May 30 12:58:09 AEST 2009 to Sat May 30 18:57:34 AEST 2009.
  Fetching 3 metadata patches.. done.
  Applying metadata patches... done.
  Fetching 0 metadata files... done.
  Fetching 3 patches.. done.
  Applying patches... done.
  Fetching 0 new ports or files... done.

-- 
John Marshall


pgpPgvj7gNgjs.pgp
Description: PGP signature

Re: portsnap can't access portsnap[124].freebsd.org

[RW]

On Sat, 30 May 2009 21:05:44 +1000
John Marshall john.marsh...@riverwillow.com.au wrote:
 
 Have you excluded local factors (proxy servers, firewalls)? 

Try fetching the key manually

fetch  http://portsnap2.FreeBSD.org/pub.ssl

___
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: portsnap can't access portsnap[124].freebsd.org

[Scott Bennett]

 On Sat, 30 May 2009 21:05:44 +1000 John Marshall
john.marsh...@riverwillow.com.au wrote:
On Sat, 30 May 2009, 05:39 -0500, Scott Bennett wrote:
  Thanks for that much, then, Glen.  So we still don't know what is wr=
ong.
 I did try it again around midnight CDT, and it still failed the same way.
  In the meantime, my frustration and impatience got the better of me,=
 and
 I touched up a copy of ports-supfile and csupped it.  I also used portins=
tall,
 which was there because I had selected it as a package during the 7.2-REL=
EASE
 installation, to install portmaster, which is now running the builds.
  Nevertheless, I'd still rather switch back to portsnap ASAP after th=
is,
 so I'm still hoping someone has an idea what's wrong with portsnap or the
 systems at freebsd.org.

Have you excluded local factors (proxy servers, firewalls)?  I have not
seen any issues at all with portsnap.  I have done a few fetches today
and haven't seen any problems at all.  This one a few minutes ago
happened to hit portsnap2.  I noticed that one of the earlier ones today
was from portsnap1.

  [portsnap session omitted  --SB]
 There was no proxy.  However, I think you may have hit upon the problem.
It depends upon what TCP port number portsnap uses.  If it connects to the
HTTP port, i.e., port 80, then I know what happened.  While running portmaster,
I soon had to deal with a problem where all of the fetches for a package
failed, but immediately, not after lengthy waits for timeouts.  It quickly
dawned on me that the http_proxy environment variable had been set to connect
things like fetch(1) and wget(1) to privoxy, which I haven't reinstalled yet
since installing 7.2-RELEASE.  This gets set in /root/.cshrc.extensions, a file
that I source from /root/.cshrc to keep most of my changes separate from stuff
that could get replaced accidentally in a mergemaster run between a buildworld
and an installworld or, as in this case, a full new OS installation.  I
unsetenved that, and various ports' Makefile fetch targets were happy again.
I never knew what port portsnap used, but maybe that's it.
 Once portmaster finishes rebuilding the relatively small set of already
installed packages and ports, I'll give portsnap another shot at it to see
what happens.
 Thanks much for the idea that connected the two problems for me!


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army.   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: portsnap can't access portsnap[124].freebsd.org

[Glen Barber]

On Fri, May 29, 2009 at 8:59 PM, Scott Bennett benn...@cs.niu.edu wrote:


[snip]



 Script started on Fri May 29 19:33:32 2009
 hellas# portsnap fetch
 Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
 Fetching public key from portsnap1.FreeBSD.org... failed.
 Fetching public key from portsnap2.FreeBSD.org... failed.
 Fetching public key from portsnap4.FreeBSD.org... failed.
 No mirrors remaining, giving up.
 hellas# exit
 exit

 Script done on Fri May 29 19:33:46 2009

     Can anyone tell me what the problem is?  Is some portsnap service not
 operational at freebsd.org currently for some reason?  Is the up-to-date
 portsnap trying to reach the wrong systems?

[snip]

Scott,

I was able to do a 'fetch' using portsnap a little over an hour ago,
as well as just now (10:15PM EDT).  I successfully fetched from
'portsnap2'.

Can you paste the 'ANSWER SECTON' from:

  'dig portsnap2.freebsd.org'


-- 
Glen Barber
___
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: portsnap can't access portsnap[124].freebsd.org

[Scott Bennett]

 On Fri, 29 May 2009 22:17:25 -0400 Glen Barber glen.j.bar...@gmail.com
wrote:
On Fri, May 29, 2009 at 8:59 PM, Scott Bennett benn...@cs.niu.edu wrote:


[snip]



 Script started on Fri May 29 19:33:32 2009
 hellas# portsnap fetch
 Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
 Fetching public key from portsnap1.FreeBSD.org... failed.
 Fetching public key from portsnap2.FreeBSD.org... failed.
 Fetching public key from portsnap4.FreeBSD.org... failed.
 No mirrors remaining, giving up.
 hellas# exit
 exit

 Script done on Fri May 29 19:33:46 2009

 =A0 =A0 Can anyone tell me what the problem is? =A0Is some portsnap servi=
ce not
 operational at freebsd.org currently for some reason? =A0Is the up-to-dat=
e
 portsnap trying to reach the wrong systems?

[snip]

Scott,

I was able to do a 'fetch' using portsnap a little over an hour ago,
as well as just now (10:15PM EDT).  I successfully fetched from
'portsnap2'.

Can you paste the 'ANSWER SECTON' from:

  'dig portsnap2.freebsd.org'

 Sure, but I'm curious to know why.  The names all do resolve to A RRs,
and pings to each by name did get echos back.  Here it is, although I did
terminate the domain name by habit.  Surely portsnap must not be so silly
as to pass unterminated names to the resolver.  (Actually, I'm including
the whole output, not just the answer section.)


;  DiG 9.4.3-P2  portsnap2.freebsd.org. a
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 59849
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;portsnap2.freebsd.org. IN  A

;; ANSWER SECTION:
portsnap2.freebsd.org.  3600IN  A   72.21.59.250

;; Query time: 41 msec
;; SERVER: 68.87.72.130#53(68.87.72.130)
;; WHEN: Fri May 29 23:37:03 2009
;; MSG SIZE  rcvd: 55

 I also just now tried a portsnap fetch again and got the same
result as before.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at cs.niu.edu  *
**
* A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army.   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: portsnap

[Olivier SMEDTS]

2009/3/10 Nataraj S Narayan natara...@gmail.com:
 Hi

 After a 'portsnap fetch' is it portsnap extract or is it portsnap
 update?  What is the proper way?

Hello,

portsnap extract extracts the entire ports tree, replacing existing
files and directories (from the manpage). portsnap update only
extracts the updated ports (after a portsnap fetch) since the last
extract or update.

Example :
Your ports tree is empty... you use portsnap fetch extract.
After some time, some ports are updated. You use portsnap fetch
update to update your ports tree (after a fetch of course).

Cheers



 I user FreeBSD 7.1

 regards

 Nataraj
 ___
 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




-- 
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org- against HTML email  vCards  X
www: http://www.gid0.org- against proprietary attachments / \

  Il y a seulement 10 sortes de gens dans le monde :
  ceux qui comprennent le binaire,
  et ceux qui ne le comprennent pas.
___
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: portsnap

[RW]

On Tue, 10 Mar 2009 14:05:16 +0100
Olivier SMEDTS oliv...@gid0.org wrote:

 2009/3/10 Nataraj S Narayan natara...@gmail.com:
  Hi
 
  After a 'portsnap fetch' is it portsnap extract or is it portsnap
  update?  What is the proper way?
 
 Hello,
 
 portsnap extract extracts the entire ports tree, replacing existing
 files and directories (from the manpage). portsnap update only
 extracts the updated ports (after a portsnap fetch) since the last
 extract or update.
 
 Example :
 Your ports tree is empty... you use portsnap fetch extract.
 After some time, some ports are updated. You use portsnap fetch
 update to update your ports tree (after a fetch of course).

Just to elaborate a little, you also need to do an extract if the tree
has been obtained or updated by other means.
___
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: portsnap

[Ricardo Jesus]

Nataraj S Narayan wrote:

Hi

After a 'portsnap fetch' is it portsnap extract or is it portsnap
update?  What is the proper way?

I user FreeBSD 7.1

regards

Nataraj
___
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


I found the Handbook's section on portsnap very usefull.

Take a look for yourself 
http://www.freebsd.org/doc/en/books/handbook/book.html#UPDATING-UPGRADING-PORTSNAP 
and of course man portsnap.

___
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: Portsnap: Cowardly Gives Up After Failure

[Rene Ladan]

2008/3/9, Simon L. Nielsen [EMAIL PROTECTED]:
 On 2008.03.09 15:38:53 +0100, Simon L. Nielsen wrote:
   On 2008.03.09 14:36:49 +0100, Rene Ladan wrote:
Gerard schreef:
 I just saw this 'portsnap' error message for the first time.


 Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
 Fetching snapshot tag from portsnap2.FreeBSD.org... done.
 Latest snapshot on server is older than what we already have!
 Cowardly refusing to downgrade from Fri Mar  7 15:23:43 EST 2008
 to Fri Mar  7 10:15:54 EST 2008.

I see this happening about half the times I run portsnap.  The
erroneous image is always from March 7.
  
   The most likely cause of the problem is that the data portsnap is
   trying to fetch is out of date either bacause of the mirror being
   (partially?) broken or e.g. a broken proxy in between.
  
   Is the working or non-working related to a particular portsnap server?


 OK, I just reproduced it - it seems portsnap2.FreeBSD.org is out of
  date.  I have poked the admin of the particular mirror (quite easy as
  it's Colin ;-) ).

portsnap3 also has issues (20080310 1008 UTC), while portsnap2 is ok
at this time :

Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
Fetching snapshot tag from portsnap3.FreeBSD.org... done.
Latest snapshot on server is older than what we already have!
Cowardly refusing to downgrade from Mon Mar 10 06:30:19 CET 2008
to Sat Mar  8 23:51:56 CET 2008.

Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
Fetching snapshot tag from portsnap2.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Mon Mar 10 06:30:19 CET 2008 to Mon Mar 10 09:23:20 CET 2008.

Rene
-- 
http://www.rene-ladan.nl/

GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portsnap: Cowardly Gives Up After Failure

[Rene Ladan]

Gerard schreef:
 I just saw this 'portsnap' error message for the first time.
 
 
 Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
 Fetching snapshot tag from portsnap2.FreeBSD.org... done.
 Latest snapshot on server is older than what we already have!
 Cowardly refusing to downgrade from Fri Mar  7 15:23:43 EST 2008
 to Fri Mar  7 10:15:54 EST 2008.
 
 
I see this happening about half the times I run portsnap.  The
erroneous image is always from March 7.

 I am not quite sure what caused this error to happen. I was thinking
 though that perhaps having some sort of retry flag might be a good
 idea. Maybe something like having 'portsnap' retry again in 5 minutes
 or try another server or whatever. I usually run 'portsnap' from CRON so
 active user participation is not really an option.
 
Retrying shortly after the error message usually helps for me.

Regards,
Rene
-- 
http://www.rene-ladan.nl/

GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6 
(subkeys.pgp.net)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portsnap: Cowardly Gives Up After Failure

[Simon L. Nielsen]

On 2008.03.09 15:38:53 +0100, Simon L. Nielsen wrote:
 On 2008.03.09 14:36:49 +0100, Rene Ladan wrote:
  Gerard schreef:
   I just saw this 'portsnap' error message for the first time.
   
   
   Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
   Fetching snapshot tag from portsnap2.FreeBSD.org... done.
   Latest snapshot on server is older than what we already have!
   Cowardly refusing to downgrade from Fri Mar  7 15:23:43 EST 2008
   to Fri Mar  7 10:15:54 EST 2008.
   
  I see this happening about half the times I run portsnap.  The
  erroneous image is always from March 7.
 
 The most likely cause of the problem is that the data portsnap is
 trying to fetch is out of date either bacause of the mirror being
 (partially?) broken or e.g. a broken proxy in between.
 
 Is the working or non-working related to a particular portsnap server?

OK, I just reproduced it - it seems portsnap2.FreeBSD.org is out of
date.  I have poked the admin of the particular mirror (quite easy as
it's Colin ;-) ).

It is posible to work around this by setting SERVERNAME in
portsnap.conf, but I suspect just waiting a bit for Colin to fix this
is simpler, also so people don't forget to remove the special
hardcoded server from the config once it's working again.


Looking up us.portsnap.FreeBSD.org mirrors... 4 mirrors found.
Fetching snapshot tag from portsnap2.FreeBSD.org... done.
Latest snapshot on server is older than what we already have!
Cowardly refusing to downgrade from Sun Mar  9 14:10:14 CET 2008
to Fri Mar  7 16:15:54 CET 2008.

-- 
Simon L. Nielsen
Hat: portsnap co-admin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portsnap: Cowardly Gives Up After Failure

[Simon L. Nielsen]

On 2008.03.09 14:36:49 +0100, Rene Ladan wrote:
 Gerard schreef:
  I just saw this 'portsnap' error message for the first time.
  
  
  Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
  Fetching snapshot tag from portsnap2.FreeBSD.org... done.
  Latest snapshot on server is older than what we already have!
  Cowardly refusing to downgrade from Fri Mar  7 15:23:43 EST 2008
  to Fri Mar  7 10:15:54 EST 2008.
  
 I see this happening about half the times I run portsnap.  The
 erroneous image is always from March 7.

The most likely cause of the problem is that the data portsnap is
trying to fetch is out of date either bacause of the mirror being
(partially?) broken or e.g. a broken proxy in between.

Is the working or non-working related to a particular portsnap server?

-- 
Simon L. Nielsen
Hat: portsnap co-admin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portsnap troubles?

[Simon L. Nielsen]

On 2007.10.14 12:11:38 +0200, Simon L. Nielsen wrote:
 On 2007.10.14 11:27:13 +0200, Erwin Lansing wrote:
  On Sun, Oct 14, 2007 at 10:28:03AM +0200, Derkjan de Haan wrote:
   Hi,
  
  Howyd,
   
   Can it be that something related to portsnap hangs? I'm not seeing any
   updates (i.e. the png security update) come through.
   
  The server that builds the portsnap data is down due to hardware
  problems.  I'm not sure what the status is, but hopefully it will return
  soon.
 
 Onsite people have been poked, but no status yet.

Just FYI, portsnap build is running again.

We will be looking at more redundancy for the build to prevent longer
outages in the future.

-- 
Simon L. Nielsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portsnap troubles?

[Erwin Lansing]

On Sun, Oct 14, 2007 at 10:28:03AM +0200, Derkjan de Haan wrote:
 Hi,

Howyd,
 
 Can it be that something related to portsnap hangs? I'm not seeing any
 updates (i.e. the png security update) come through.
 
The server that builds the portsnap data is down due to hardware
problems.  I'm not sure what the status is, but hopefully it will return
soon.

Best,
-erwin

-- 
Erwin Lansing http://droso.org
Security is like an onion.  (o_ _o)
It's made up of several layers   \\\_\   /_///[EMAIL PROTECTED]
And it makes you cry.) ([EMAIL PROTECTED]


pgpwqblGFgN0S.pgp
Description: PGP signature

Re: portsnap troubles?

[Simon L. Nielsen]

On 2007.10.14 11:27:13 +0200, Erwin Lansing wrote:
 On Sun, Oct 14, 2007 at 10:28:03AM +0200, Derkjan de Haan wrote:
  Hi,
 
 Howyd,
  
  Can it be that something related to portsnap hangs? I'm not seeing any
  updates (i.e. the png security update) come through.
  
 The server that builds the portsnap data is down due to hardware
 problems.  I'm not sure what the status is, but hopefully it will return
 soon.

Onsite people have been poked, but no status yet.

-- 
Simon L. Nielsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portsnap serving up bad snapshots?

[Marcus Reid]

On Wed, Sep 19, 2007 at 12:34:22PM -0700, Marcus Reid wrote:
 Hi,
 
 I've tried this on a couple of different machines a few times over
 the last couple of days, and keep getting the same results.  Starting
 with an empty /var/db/portsnap :
 
   [EMAIL PROTECTED] /var/db]# portsnap fetch
   Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
   Fetching public key from portsnap3.freebsd.org... done.
   Fetching snapshot tag from portsnap3.freebsd.org... done.
   Fetching snapshot metadata... done.
   Fetching snapshot generated at Tue Sep 18 17:22:37 PDT 2007:
   1d76db54d472a78981f30c134f34eea49141d183d48127100% of   49 MB   90 kBps 
 00m00s
   Extracting snapshot... done.
   Verifying snapshot integrity... gunzip: 
 snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: 
 unexpected end of file
   gunzip: 
 snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: 
 uncompress failed
   snapshot corrupt.

Hi Again,

Just thought I'd set the record straight..  This turned out to
be a regression in libarchive that broke bsdtar in -CURRENT.  It
has since been backed out.  There was no problem with portsnap.

Marcus
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portsnap serving up bad snapshots?

[Amarendra Godbole]

On 9/20/07, Marcus Reid [EMAIL PROTECTED] wrote:
 I've tried this on a couple of different machines a few times over
 the last couple of days, and keep getting the same results.  Starting
 with an empty /var/db/portsnap :

   [EMAIL PROTECTED] /var/db]# portsnap fetch
   Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
   Fetching public key from portsnap3.freebsd.org... done.
   Fetching snapshot tag from portsnap3.freebsd.org... done.
   Fetching snapshot metadata... done.
   Fetching snapshot generated at Tue Sep 18 17:22:37 PDT 2007:
   1d76db54d472a78981f30c134f34eea49141d183d48127100% of   49 MB   90 kBps 
 00m00s
   Extracting snapshot... done.
   Verifying snapshot integrity... gunzip: 
 snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: 
 unexpected end of file
[...]
 Some files in the archive are valid, but many seem to be
 truncated.  Is there a big problem with portsnap right now?
[...]

If your internet connection if flaky, or if you get in data through a
proxy - this problem pops up. I used to have this problem when my
internet connection was slow and flaky - once we added more bandwidth,
it has gone away completely.

-Amarendra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portsnap fetch bug or quality

[Alex Dupre]

Alexander Sizov wrote:
 The number of fetching patches (1980) !=  number of fetched patches
 (143[8-9]). Why it happens?
 
 Does it happen only on portsnap3, right?
 
  Yes.

I dunno why, but portsnap3 had strange behaviors since the beginning.
Apart from speed (it's the slowest from here), I always had
disconnections and errors when fetching many (hundreds) updates, and
recently I saw also the very same mismatch: I thought about another
premature disconnection, but no, it fetched all the updates even if the
number was incorrect. Perhaps Colin can give us an explanation.

--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portsnap - latest.ssl not found

[Miroslav Lachman]

Duane Hill wrote:


Every once in a while I get the following when doing an update of the 
ports tree via portsnap:


  Looking up portsnap.FreeBSD.org mirrors... using portsnap3.FreeBSD.org.
  Fetching snapshot tag... fetch: 
http://portsnap3.FreeBSD.org./latest.ssl: Not Found

  Failed.

Every time the error has occurred, it has been with portsnap3.FreeBSD.org.

If I run portsnap again it usually rotates to a different portsnap 
mirror and everything is fine.


The server /etc/portsnap.conf points to is:

  SERVERNAME=portsnap.FreeBSD.org

Does anyone have a clue what's going on?


Just me too message - I have same problem for more than month.

Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portsnap files?

[Xin LI]

在 2007-06-10日的 19:03 +0200，Ivan Voras写道：
 Hi
 
 Are files in /var/db/portsnap/files important after portsnap update
 has been run, or can they be deleted, from example within a cron job?

They are important for your next portsnap fetch run, which means that
next run would download only a small set of files, thus save a lot of
time and bandwidth.  However if you do not want to run portsnap anymore,
you can safely remove the directory.

Cheers,
-- 
Xin LI [EMAIL PROTECTED]http://www.delphij.net/
FreeBSD - The Power to Serve!


signature.asc
Description: 这是信件的数	字签名部分

Re: portsnap and local patches

[Scot Hetzel]

On 3/14/07, Nate Eldredge [EMAIL PROTECTED] wrote:

Hi all,

portsnap is a very nice way to keep your ports tree in sync, but it has
the disadvantage that it keeps your ports tree in sync :)  If you make
local changes (e.g. adding a patch) they get clobbered.  Does anyone know
of a convenient way to keep ports up to date while preserving local
patches?


One way to keep your local changes is to use cvs to checkout and
update the ports tree, you then make your modifications to the port.

You will need to fix any conflicts manually between an updated port
and your changes.

Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portsnap and local patches

[Josh Paetzel]

On Wednesday 14 March 2007 02:12, Scot Hetzel wrote:
 On 3/14/07, Nate Eldredge [EMAIL PROTECTED] wrote:
  Hi all,
 
  portsnap is a very nice way to keep your ports tree in sync, but
  it has the disadvantage that it keeps your ports tree in sync :) 
  If you make local changes (e.g. adding a patch) they get
  clobbered.  Does anyone know of a convenient way to keep ports up
  to date while preserving local patches?

 One way to keep your local changes is to use cvs to checkout and
 update the ports tree, you then make your modifications to the
 port.

 You will need to fix any conflicts manually between an updated port
 and your changes.

 Scot

csup/cvsup has the nice feature of not touching files that shouldn't 
be there, so my solution to that problem is to create a new directory 
for my local changes, which csup/cvsup will nicely ignore.

-- 
Thanks,

Josh Paetzel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portsnap and local patches

[Paul Schmehl]

--On Tuesday, March 13, 2007 23:26:26 -0700 Nate Eldredge [EMAIL PROTECTED] 
wrote:



Hi all,

portsnap is a very nice way to keep your ports tree in sync, but it has
the disadvantage that it keeps your ports tree in sync :)  If you make
local changes (e.g. adding a patch) they get clobbered.  Does anyone know
of a convenient way to keep ports up to date while preserving local
patches?


That's why God made shell scripting???

if [ -f ${port/path/mypatch} ]; then
 cp $mypatch ${port/path/mypatch}
fi

Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

Re: portsnap mirrors not being updated (?)

[Colin Percival]

martinko wrote:
 I've seen the following for around last two days:
 
 Looking up portsnap.FreeBSD.org mirrors... 2 mirrors found.
 Fetching snapshot tag from portsnap1.FreeBSD.org... done.
 Latest snapshot on server matches what we already have.
 No updates needed.
 
 Is something going on with portsnap's mirror building ?

Two problems happened almost simultaneously, actually:

1. Due to some chaos surrounding the relocation of the main FreeBSD.org
cluster, the portsnap builds stopped for about 20 hours.  They're running
again now, but will probably stop on Monday as the FreeBSD.org cluster
continues its relocation.  (On the positive side, nobody can commit to
the ports tree while the cluster is in transit, so portsnap users won't
be missing anything at this point.)

2. One of the portsnap mirrors, portsnap1.freebsd.org, is not updating at
the moment; I've sent an email to the administrator of this server asking
him to investigate.  Until it starts updating again (most likely a matter
of hours), you can force portsnap to use the other mirror:
# portsnap -s portsnap2.freebsd.org fetch

Colin Percival
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]