On Tue, 6 Apr 2021 22:14:21 +0200
Christoph Moench-Tegeder wrote:
> ## LuMiWa via freebsd-ports (freebsd-ports@freebsd.org):
>
> > I try to install cad/freecad and it pulls lang/Python 27.
>
> FreeCAD itself depends on Python "3.6 or higher". What exactly did
> you do?
>
> > I didn't
## LuMiWa via freebsd-ports (freebsd-ports@freebsd.org):
> I try to install cad/freecad and it pulls lang/Python 27.
FreeCAD itself depends on Python "3.6 or higher". What exactly did
you do?
> I didn't install.
So you're sying it's not relevant anymore anyway?
Regards,
Christoph
--
Spare
On 4/6/21 1:09 PM, Marco Beishuizen wrote:
Hi,
I'm trying to git clone the portstree into /usr/ports. /usr/ports is a
separate filesystem so it contains a .sujournal file. But now git
complains "fatal: destination path 'ports' already exists and is not an
empty directory."
So my question
Hi,
I'm trying to git clone the portstree into /usr/ports. /usr/ports is a
separate filesystem so it contains a .sujournal file. But now git
complains "fatal: destination path 'ports' already exists and is not an
empty directory."
So my question is what to do next? Recreating a new
* Marco Beishuizen [20210406 13:09]:
> So my question is what to do next? Recreating a new .sujournal every time a
> ports tree needs to be cloned is quite annoying.
Normally, you should clone only once and use `git pull` afterwards, so
no problem here. Furthermore, if you don't really ne
Thanks! I was able to fix that this morning and I just merged back from
main and everything is working fine.
*Eric Turgeon*
On Tue, Apr 6, 2021 at 2:08 PM Ulrich Spörlein wrote:
> On Mon, 2021-04-05 at 21:45:57 +, Brooks Davis wrote:
> >On Mon, Apr 05, 2021 at 05:33:08PM -0300, Eric
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
On Tue, 6 Apr 2021, the wise Felix Palmen wrote:
Where did you clone from? The official repo is only available for a few
hours now. So, if you cloned from a mirror (Github, Gitlab, …?), some
breakage with the transition seems plausible.
Ah, please no CC, thanks.
From
> On 6. Apr 2021, at 13:10, Marco Beishuizen
> wrote:
>
> Hi,
>
> I'm trying to git clone the portstree into /usr/ports. /usr/ports is
> a separate filesystem so it contains a .sujournal file. But now git
> complains "fatal: destination path 'ports' already exists and is not
> an empty
* Marco Beishuizen [20210406 14:35]:
> Pulling isn't possible either:
>
> ...
> There is no tracking information for the current branch.
> Please specify which branch you want to rebase against.
> See git-pull(1) for details.
>
> git pull
>
> If you wi
On Tue, 6 Apr 2021, the wise Felix Palmen wrote:
Normally, you should clone only once and use `git pull` afterwards, so
no problem here. Furthermore, if you don't really need git but just want
to keep your ports tree up to date, you might want to have a look at
net/gitup instead.
It's
On Tue, 6 Apr 2021, the wise Hans Petter Selasky wrote:
Not sure if it helps, but did you try to add a "/", like:
git clone /usr/ports/
This doesn't make a difference.
Isn't there a way to force git to clone it into /usr/ports?
Regards,
Marco
--
When the usher noticed a man stretched
On Tue, 6 Apr 2021, the wise Felix Palmen wrote:
This is meant to avoid cloning, you can just `pull` after adding a
remote to an empty repository.
Pulling isn't possible either:
...
There is no tracking information for the current branch.
Please specify which branch you want to rebase
* Marco Beishuizen [20210406 13:47]:
> I did clone it yesterday but today a git pull resulted in a corrupt file for
> some reason, so I decided to start over.
Where did you clone from? The official repo is only available for a few
hours now. So, if you cloned from a mirror (Github,
* Marco Beishuizen [20210406 14:25]:
> On Tue, 6 Apr 2021, the wise Helge Oldach wrote:
>
> > cd /usr/ports
> > git init .
> > git remote add -t main -f freebsd https://git.freebsd.org/ports.git
>
> This created new .git subdirectories but still cannot clone i
* Marco Beishuizen [20210406 14:01]:
> From https://git.freebsd.org/ports.git.
> It's up since yesterday. Cloning after totally emptying /usr/ports worked
> fine, but today git complained about corrupt files in the .git subdirectory
> so I decided to start over again.
This was the
On Tue, 6 Apr 2021, the wise Helge Oldach wrote:
cd /usr/ports
git init .
git remote add -t main -f freebsd https://git.freebsd.org/ports.git
Kind regards
Helge
This created new .git subdirectories but still cannot clone into
/usr/ports.
--
The minute a man is convinced that he is
On Tue, 6 Apr 2021 18:40:44 +0200 (CEST)
Marco Beishuizen wrote:
> On Tue, 6 Apr 2021, the wise Helge Oldach wrote:
>
> > Marco Beishuizen wrote on Tue, 06 Apr 2021 15:59:48 +0200 (CEST):
> >> To avoid possible future problems I placed .sujournal into
> >> $HOME/.gitexcludes as you
On Mon, 2021-04-05 at 21:45:57 +, Brooks Davis wrote:
On Mon, Apr 05, 2021 at 05:33:08PM -0300, Eric Turgeon wrote:
Today when trying to sync the GhostBSD ports tree with the FreeBSD ports
tree, I found out the main branch history is not compatible with the old
GitHub master.
Any plan to
Hi Jose,
On Tue, 6 Apr 2021 08:33:27 -0700
Jose Quinteiro wrote:
> On 4/6/21 6:28 AM, Michael Gmelin wrote:
> > Example:
> >
> > git config core.excludesFile=$HOME/.gitexcludes
> > echo .sujournal >>$HOME/.gitexcludes
> >
> > In case you don't want to override the excludesFile setting,
On 4/6/21 10:25 AM, Michael Gmelin wrote:
> Hi Jose,
>
> On Tue, 6 Apr 2021 08:33:27 -0700
> Jose Quinteiro wrote:
>
> ...
> This information is not correct.
>
You are absolutely right. Sorry for the bad information!
Thanks,
Jose
___
On Tue, 6 Apr 2021, the wise Helge Oldach wrote:
Sorry, I forgot: git checkout main
Once done, just regularly: git pull --ff-only
Explanation: "clone" is roughly equivalent to "init + remote add +
checkout". Separating the three steps will allow for the -f (--force)
option on "remote add"
On Tue, 6 Apr 2021 15:12:42 +0200 (CEST)
free...@oldach.net (Helge Oldach) wrote:
> Marco Beishuizen wrote on Tue, 06 Apr 2021 14:25:51 +0200 (CEST):
> > On Tue, 6 Apr 2021, the wise Helge Oldach wrote:
> > > cd /usr/ports
> > > git init .
> > > git remote add -t main -f freebsd
> > >
On Tue, 6 Apr 2021, the wise Michael Gmelin wrote:
Sorry, I forgot: git checkout main
Once done, just regularly: git pull --ff-only
Explanation: "clone" is roughly equivalent to "init + remote add +
checkout". Separating the three steps will allow for the -f (--force)
option on "remote add"
On 4/6/21 6:28 AM, Michael Gmelin wrote:
> Example:
>
> git config core.excludesFile=$HOME/.gitexcludes
> echo .sujournal >>$HOME/.gitexcludes
>
> In case you don't want to override the excludesFile setting, alter one
> of the config files in the default global location
>
On Tue, 6 Apr 2021, the wise Helge Oldach wrote:
Marco Beishuizen wrote on Tue, 06 Apr 2021 15:59:48 +0200 (CEST):
To avoid possible future problems I placed .sujournal into
$HOME/.gitexcludes as you suggested.
That would work as there is no good reason a .sujournal file would be
tracked by
Hey there,
I wanted to reach out to the people both doing the massive migration, as well
as the people covering answers to frequent questions here on the lists, and I’m
sure on the forums and elsewhere.
There’s something important to know:
Thank you. Seriously.
Open source is often
27 matches
Mail list logo
