On 2021-04-13 23:22, Stefan Esser wrote:
Am 14.04.21 um 02:43 schrieb Chris:
On 2021-04-13 15:53, Dave Horsfall wrote:
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to
run
"gc" - which is similarly extravagant i
Am 14.04.21 um 02:43 schrieb Chris:
On 2021-04-13 15:53, Dave Horsfall wrote:
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to
run
"gc" - which is similarly extravagant in memory usage. Last time I
found
one r
On 2021-04-13 15:53, Dave Horsfall wrote:
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to run
"gc" - which is similarly extravagant in memory usage. Last time I found
one running, it thrashed that poor VM for 3 d
> On 14. Apr 2021, at 00:54, Dave Horsfall wrote:
>
> On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
>
>> Except that git will arbitrarily and randomly decide that it needs to run
>> "gc" - which is similarly extravagant in memory usage. Last time I found
>> one running, it thr
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to
run "gc" - which is similarly extravagant in memory usage. Last time I
found one running, it thrashed that poor VM for 3 days.
Would this be a good time to mention
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@freeb
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.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-por
> On 12. Apr 2021, at 13:12, Peter Jeremy via freebsd-ports
> wrote:
>
> On 2021-Apr-11 14:27:27 +0200, Helge Oldach wrote:
>> Peter Jeremy via freebsd-ports wrote on Sun, 11 Apr 2021 00:52:11 +0200
>> (CEST):
>>> Following the SVN to GIT migration, p
On 2021-Apr-11 14:27:27 +0200, Helge Oldach wrote:
>Peter Jeremy via freebsd-ports wrote on Sun, 11 Apr 2021 00:52:11 +0200 (CEST):
>> Following the SVN to GIT migration, portsnap is now the only practical
>> way to use ports on a low-memory system. I've done some experiments
On Apr 11, 2021, at 06:27, free...@oldach.net wrote:
>
> However checking out is a one-time action with ports as there is only
> one branch
It sure looks like gitup is checking the entire port tree every single time. If
I run it twice in a row it is no faster the second time.
_
On 2021-Apr-01 12:19:08 +0200, Felix Palmen wrote:
>* Christoph Moench-Tegeder [20210326 19:45]:
>> ## Felix Palmen (fe...@palmen-it.de):
>>
>> > I'd assume (someone may correct me) that portsnap will still be
>> > supported,
>>
>> https://lis
On 01 Apr 2021, at 04:19, Felix Palmen wrote:
> * Christoph Moench-Tegeder [20210326 19:45]:
>> ## Felix Palmen (fe...@palmen-it.de):
>>> I'd assume (someone may correct me) that portsnap will still be
>>> supported,
>> https://lists.freebsd.org/pipermail
Hallo Christoph,
* Christoph Moench-Tegeder [20210326 19:45]:
> ## Felix Palmen (fe...@palmen-it.de):
>
> > I'd assume (someone may correct me) that portsnap will still be
> > supported,
>
> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html
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 reque
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 mechanis
> 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
> justificat
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".
Someho
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
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 por
gain 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
> > > deprecati
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 Wil
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
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 po
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
ebsd.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
udriere-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
rward 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
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 s
t 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 d
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
>
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.
Perhaps I am wrong on this, so I thought I would ask. Is 'portsnap'
going to be depreciated? If so, when? If is is depreciated, how will
this affect poudriere? I thought that poudriere used 'portsnap'.
--
Carmel
pgpu4e_OrLlmR.pgp
Description: OpenPGP digital signature
Portsnap is convenient, but svn/git in more inline with other tools.
Maybe some sort of middle ground where portsnap is replaced (or
re-written) with a wrapper around the svn checkout/update (or git
clone/pull) process.
On 8/13/2020 3:30 AM, Tatsuki Makino wrote:
We need to be reminded of
We need to be reminded of csup once in a while :)
Will portsnap be rewritten in C? :)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-uns
On Mon, 10 Aug 2020, Robert Huff wrote:
There are many users who never create any patches, but simply use the
ports tree to install software.
Add my name to that list.
Mine too; this is a great way to drive "ordinary users" away from FreeBSD
and towards, gasp, Penguin/OS...
I took up Fr
On Mon, 10 Aug 2020 12:11:06 -0400 Robert Huff roberth...@rcn.com said
Michael Gmelin writes:
> There are many users who never create any patches, but simply use
> the ports tree to install software.
Add my name to that list.
(Used to use cvsup ... now subversion ... soon git ... wh
On 8/11/20 9:39 PM, Mike Clarke wrote:
On Sunday, 9 August 2020 17:27:01 BST RW via freebsd-ports wrote:
What I'd like to see is a simple way to update the ports tree to match
what was used to build the current packages in the repository.
Something I've felt in need of for a long time, and su
On Sunday, 9 August 2020 17:27:01 BST RW via freebsd-ports wrote:
> What I'd like to see is a simple way to update the ports tree to match
> what was used to build the current packages in the repository.
Something I've felt in need of for a long time, and suggested from time to time
in the past
On Fri, Aug 07, 2020 at 11:48:34AM -0400, Greg Veldman wrote:
> On Fri, Aug 07, 2020 at 03:43:38PM +0200, Michael Gmelin wrote:
> > The real question is: Will we design things in a way that we expect ports
> > tree users to always install git and its dependencies on their system or
> > not (long
ns.
> > To leverage the UX flaws of git and svn(lite) compared to portsnap
> > having a wrapper script around the two tools would be very appreciated.
> >
> > Something like
> >
> > # portsnap-ng --mode git --branch 2020Q2 --destination /ports/2020Q2 fetch
> &
Michael Gmelin writes:
> There are many users who never create any patches, but simply use
> the ports tree to install software.
Add my name to that list.
(Used to use cvsup ... now subversion ... soon git ... where will
the insanity end? :-) )
Res
have pros and cons.
>> To leverage the UX flaws of git and svn(lite) compared to portsnap
>> having a wrapper script around the two tools would be very appreciated.
>> Something like
>> # portsnap-ng --mode git --branch 2020Q2 --destination /ports/2020Q2 fetch
>> extrac
Hi,
On 8/10/20 9:28 AM, Lars Engels wrote:
On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
I'm probably fine with this and I think that all of the (now) supported
methods have pros and cons.
To leverage the UX flaws of git and svn(lite) compared to portsnap
having a wrapper s
On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
>
> We are planning to deprecate use of portsnap in ports.
>
> The reasons are as follows (in no particular order):
>
> * Portsnap doesn't support quarterly branches, even years after
> quarterly branches w
On Sun, 9 Aug 2020 16:43:28 +0100
Matthew Seaman wrote:
> On 09/08/2020 07:03, Stefan Ehmann wrote:
> > I usually run `pkg version` to see what packages have changed.
> >
> > Previously, that was a more or less instant operation, now it takes
> > over 100 seconds. The problem is that /usr/ports/I
On 09/08/2020 07:03, Stefan Ehmann wrote:
> I usually run `pkg version` to see what packages have changed.
>
> Previously, that was a more or less instant operation, now it takes over 100
> seconds. The problem is that /usr/ports/INDEX-12 is missing.
Yes. For historical reason, the order of prec
On Tuesday, August 4, 2020 8:43:20 PM CEST Steve Wills wrote:
> We are planning to deprecate use of portsnap in ports.
>
> The reasons are as follows (in no particular order):
>
> * Portsnap doesn't support quarterly branches, even years after
> quarterly branches were cre
On 05 Aug 2020, at 04:59, Hans Petter Selasky wrote:
> 2) Should portsnap be a wrapper for GIT/SVN whatever is used?
Yes, this seems like a very obvious thing to do as it will minimize disruption
for the most users.
Not everyone has any use for git our any need to learn git syntax. A "
By the way, there was a REFUSE directive in /etc/portsnap.conf, wasn't
there?
Isn't this a db space saver?
Or, rename the current fetch command to fetch-all.
Then the fetch command will be modified to download only where it is
needed based on the dependency graph.
portsnap fetch # <
On Fri, Aug 07, 2020 at 03:43:38PM +0200, Michael Gmelin wrote:
> The real question is: Will we design things in a way that we expect ports
> tree users to always install git and its dependencies on their system or not
> (long term)?
>
> For developers it???s a no-brainer (obviously yes), but po
to always install git and its dependencies on their system or not (long
term)?
For developers it’s a no-brainer (obviously yes), but ports tree users aren’t
developers.
Ideally, from a user perspective, “portsnap fetch/extract/update” would just
work as it did before (maybe running “portsnap res
Hi,
On 8/7/20 6:19 AM, Michael Gmelin wrote:
On Fri, 7 Aug 2020 01:24:00 -0400
Steve Wills wrote:
Hi,
[snip]
2. Use svnlite to checkout a ports tree. (There will be git -> svn
replication.
Will this be a long-term option?
I don't know yet exactly how long the git to svn migration i
On 8/7/20 6:05 PM, Eugene Grosbein wrote:
> 07.08.2020 18:10, Ashish SHUKLA wrote:
>
>> Is there a similar seed file for subversion snapshot, that one can
>> download, extract, and "svn up" ?
>>
>> I was trying to "svn co" the ports tree, and it keeps dying in the
>> middle of checkout every few m
07.08.2020 18:10, Ashish SHUKLA wrote:
> Is there a similar seed file for subversion snapshot, that one can
> download, extract, and "svn up" ?
>
> I was trying to "svn co" the ports tree, and it keeps dying in the
> middle of checkout every few minutes.
ftp://ftp.freebsd.org/pub/FreeBSD/develop
On 8/6/20 6:05 PM, Mathieu Arnold wrote:
> On Thu, Aug 06, 2020 at 02:11:10PM +0200, Michael Gmelin wrote:
>>
>>
>>> On 6. Aug 2020, at 13:58, Mathieu Arnold wrote:
>>>
>>> On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
> We welcome any constructive feedback. All input would
17029
curl-7.70.0_1
pcre-8.44
p5-subversion-1.14.0
p5-Term-ReadKey-2.38_1
gettext-runtime-0.20.2
cvsps-2.1_2
This would also allow to write a simple/lean wrapper that can act as a
drop-in replacement for portsnap, as it doesn't require a special
Hi,
On 8/5/20 6:17 PM, Michael Gmelin wrote:
What will be the process to bootstrap git?
There are several options:
1. Install the git package provided by the FreeBSD project
2. Use svnlite to checkout a ports tree. (There will be git -> svn
replication.
3. Download a tar of the ports tre
Mathieu Arnold wrote on 2020/08/06 20:57:
> `svnlite cleanup --remove-unversioned`
I have gained new knowledge.
I had erased the files ? marked with the following svnlite status with
my own hands :)
# svnlite status "`cat /usr/local/etc/poudriere.d/ports/svn/mnt`"
? /usr/local/poudri
gt; disruptive to anyone's usual workflow.
As a total random user with no direct role in the ports life, except
than being portsnap user, may I suggest that the "removal" may be
instead a "replace" of the portsnap binary with a script or whatever
that runs the "new-stand
On Thu, Aug 06, 2020 at 02:11:10PM +0200, Michael Gmelin wrote:
>
>
> > On 6. Aug 2020, at 13:58, Mathieu Arnold wrote:
> >
> > On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
> >>> We welcome any constructive feedback. All input would be heard, and if
> >>> the plans need to
> On 6. Aug 2020, at 13:58, Mathieu Arnold wrote:
>
> On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
>>> We welcome any constructive feedback. All input would be heard, and if the
>>> plans need to be amended, we will come back to you with the amended plan in
>>> a couple of
On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
> > We welcome any constructive feedback. All input would be heard, and if the
> > plans need to be amended, we will come back to you with the amended plan in
> > a couple of weeks. This process will take some time and hopefully won'
On Thu, Aug 06, 2020 at 01:57:41PM +0700, Eugene Grosbein wrote:
> 06.08.2020 13:23, Doug Hardie wrote:
>
> >> On 5 August 2020, at 21:30, Eugene Grosbein wrote:
> >>
> >> 06.08.2020 6:02, Tatsuki Makino wrote
> >> :
> >>> Is there any co
> On 5 August 2020, at 23:57, Eugene Grosbein wrote:
>
> 06.08.2020 13:23, Doug Hardie wrote:
>
>>> On 5 August 2020, at 21:30, Eugene Grosbein wrote:
>>>
>>> 06.08.2020 6:02, Tatsuki Makino wrote
>>> :
>>>> Is there any command
06.08.2020 13:23, Doug Hardie wrote:
>> On 5 August 2020, at 21:30, Eugene Grosbein wrote:
>>
>> 06.08.2020 6:02, Tatsuki Makino wrote
>> :
>>> Is there any command other than "rm -rf /usr/ports ; portsnap extract"
>>> that can be
> On 5 August 2020, at 21:30, Eugene Grosbein wrote:
>
> 06.08.2020 6:02, Tatsuki Makino wrote
> :
>> Is there any command other than "rm -rf /usr/ports ; portsnap extract"
>> that can be easily repaired?
>
> svnlite revert -R /usr/ports
master# s
06.08.2020 6:02, Tatsuki Makino wrote
:
> Is there any command other than "rm -rf /usr/ports ; portsnap extract"
> that can be easily repaired?
svnlite revert -R /usr/ports
___
freebsd-ports@freebsd.org mailing list
https://lists.fre
Is there any command other than "rm -rf /usr/ports ; portsnap extract"
that can be easily repaired?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to &quo
from Hans Petter Selasky:
> Maybe some silly questions already answered:
> 1) portsnap is populating /usr/ports . Is this location still hardcoded
> for ports tree installations, or can it be installed anywhere?
> 2) Should portsnap be a wrapper for GIT/SVN whatever is used?
>
> On 4. Aug 2020, at 20:43, Steve Wills wrote:
>
>
> We are planning to deprecate use of portsnap in ports.
>
> The reasons are as follows (in no particular order):
>
> * Portsnap doesn't support quarterly branches, even years after quarterly
> branches
Hi,
On 8/5/20 12:31 PM, Ernie Luzar wrote:
I seems this is a done deal as changes are already being done now. So
the real question is, when is the portsnap utility going to be removed
from the base system? Will it happen in 12.2 or 13.0?
Full removal may not happen before 13.0 but
Steve Wills wrote:
We are planning to deprecate use of portsnap in ports.
The reasons are as follows (in no particular order):
* Portsnap doesn't support quarterly branches, even years after
quarterly branches were created and changed to the default for non-HEAD
packages.
* Por
Hi,
On 8/5/20 5:42 AM, Yasuhiro KIMURA wrote:
From: Kurt Jaeger
Subject: Re: [HEADS UP] Planned deprecation of portsnap
Date: Wed, 5 Aug 2020 06:40:39 +0200
There's a list where the git topic is discussed:
https://lists.freebsd.org/pipermail/freebsd-git/
Have a look at the archive, an
t; > > We are planning to deprecate use of portsnap in ports.
> > > >
> > > > The reasons are as follows (in no particular order):
> > > >
> > > > * Portsnap doesn't support quarterly branches, even years after
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 5 Aug 2020 13:32:10 +0200
Mathieu Arnold wrote:
> On Wed, Aug 05, 2020 at 12:59:18PM +0200, Hans Petter Selasky wrote:
> > On 2020-08-04 20:43, Steve Wills wrote:
> > >
> > > We are planning to depreca
On Wed, Aug 05, 2020 at 12:59:18PM +0200, Hans Petter Selasky wrote:
> On 2020-08-04 20:43, Steve Wills wrote:
> >
> > We are planning to deprecate use of portsnap in ports.
> >
> > The reasons are as follows (in no particular order):
> >
> > * Portsnap d
On 2020-08-04 20:43, Steve Wills wrote:
We are planning to deprecate use of portsnap in ports.
The reasons are as follows (in no particular order):
* Portsnap doesn't support quarterly branches, even years after
quarterly branches were created and changed to the default for non
From: Kurt Jaeger
Subject: Re: [HEADS UP] Planned deprecation of portsnap
Date: Wed, 5 Aug 2020 06:40:39 +0200
> There's a list where the git topic is discussed:
>
> https://lists.freebsd.org/pipermail/freebsd-git/
>
> Have a look at the archive, and yes, subversion as vers
On Tue, Aug 04, 2020 at 09:51:23PM -0700, Chris wrote:
> This is very bad news for us. I can make so many arguments against
> dropping subversion. It's really not (needn't be) a matter of either/or.
In this sentence, who is "us"?
Also, can you elaborate?
--
Mathieu Arnold
signature.asc
Descrip
On Tue, 04 Aug 2020 19:03:08 -0700
Chris wrote:
> Please tell me that this doesn't mean a
>
> [HEADS UP] Planned deprecation of subversion
>
> is on the horizon.
I'm afraid that git is fashionable now.
___
freebsd-ports@freebsd.org mailing list
https
Hi!
> > > > * This migration away from portsnap fits well with the planned
> > > > migration to git.
> > Have a look at the archive, and yes, subversion as version control
> > system for the FreeBSD project will probably be replaced by git.
> This is v
On Wed, 5 Aug 2020 06:40:39 +0200 Kurt Jaeger p...@freebsd.org said
Hi!
> > * This migration away from portsnap fits well with the planned
> > migration to git.
> Please tell me that this doesn't mean a
>
> [HEADS UP] Planned deprecation of subversion
>
> is
Hi!
> > * This migration away from portsnap fits well with the planned
> > migration to git.
> Please tell me that this doesn't mean a
>
> [HEADS UP] Planned deprecation of subversion
>
> is on the horizon.
There's a list where the git topic is discussed:
On Tue, 4 Aug 2020 14:43:20 -0400 Steve Wills swi...@freebsd.org said
We are planning to deprecate use of portsnap in ports.
...
Makes sense to me. Thank you. :-)
* Portsnap doesn't seem to save disk space compared to svn or git, if
you count the metadata (stored in /var/db/portsn
We are planning to deprecate use of portsnap in ports.
The reasons are as follows (in no particular order):
* Portsnap doesn't support quarterly branches, even years after
quarterly branches were created and changed to the default for non-HEAD
packages.
* Portsnap doesn't se
d. 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 @
> 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
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.or
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
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:
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. 7
Hi,
I noticed portsnap mirror is outdated for few hours now:
λ sudo make -C /usr/ports update
Password:
--
>>> Running portsnap
--
Looking up portsnap.FreeBSD.org mir
"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 thin
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.
--
-
Alex.
___
freebsd-ports@freebsd.org mailing list
https
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
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
On Thu, 16 Feb 2017, RW via freebsd-ports wrote:
> > aneurin# du -sk /usr/ports/distfiles /var/db/portsnap/files
> > 965198 /usr/ports/distfiles
>
> This is a cache, so you can delete it, or trim it with distclean
> (installed with portupgrade), or portmaster.
Than
somewhat minimalist box (all I can
> afford), and I'd like to recover some space. Can I just delete their
> contents?
>
> aneurin# du -sk /usr/ports/distfiles /var/db/portsnap/files
> 965198/usr/ports/distfiles
This is a cache, so you can delete it, or trim it wit
There is only the one FreeBSD box in my stable, hence I don't need to
build packages for others. It's a somewhat minimalist box (all I can
afford), and I'd like to recover some space. Can I just delete their
contents?
aneurin# du -sk /usr/ports/distfiles /var/db/portsnap/file
On Sat, 7 Jan 2017, RW via freebsd-ports wrote:
> 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 unmodif
1 - 100 of 314 matches
Mail list logo
