On 05/02/2022 6:13 am, Martin Waschbüsch wrote:
Hi there,
If a committer could have a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263674
That would be awesome!
Thanks,
Martin
Committed, thanks!
In the future, feel free to send me a note when you have a PR for any
dovecot rel
I'm a maintainer for well over 100 ports. But more often than
not, I am not permitted to obtain the ports tree from any of
the FreeBSD git servers:
# git clone -o freebsd --config
remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
https://git.freebsd.org/ports.git PORTS-202
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, you
Hi!
> I'm a maintainer for well over 100 ports. But more often than
> not, I am not permitted to obtain the ports tree from any of
> the FreeBSD git servers:
>
> # git clone -o freebsd --config
> remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
> https://git.
s/*'
https://git.freebsd.org/ports.git PORTS-20220502
returns:
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
fatal: error reading section header 'shallow-info'
That's the command I use as well. To be honest, I do not
need to clone the tree that often, once ever
/*'
https://git.freebsd.org/ports.git PORTS-20220502
returns:
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
fatal: error reading section header 'shallow-info'
I've run into this issue in the past with older versions of git. I found
that updating my version of
ted to obtain the ports tree from any of
> > the FreeBSD git servers:
> >
> > # git clone -o freebsd --config
> > remote.freebsd.fetch='+refs/notes/:refs/notes/'
> > https://git.freebsd.org/ports.git PORTS-20220502
> >
> > returns:
> > error: RP
#x27;+refs/notes/*:refs/notes/*'
https://git.freebsd.org/ports.git PORTS-20220502
returns:
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
fatal: error reading section header 'shallow-info'
I've run into this issue in the past with older versions of
ne -o freebsd --config
remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
https://git.freebsd.org/ports.git PORTS-20220502
returns:
error: RPC failed; HTTP 504 curl 22 The requested URL returned
error: 504
fatal: error reading section header 'shallow-info'
I've run into thi
eebsd --config
remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
https://git.freebsd.org/ports.git PORTS-20220502
returns:
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
fatal: error reading section header 'shallow-info'
I've run into this issue i
> not, I am not permitted to obtain the ports tree from any of
>>>> the FreeBSD git servers:
>>>>
>>>> # git clone -o freebsd --config
>>>> remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
>>>> https://git.freebsd.org/ports.git
n the ports tree from any of
the FreeBSD git servers:
# git clone -o freebsd --config
remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
https://git.freebsd.org/ports.git PORTS-20220502
returns:
error: RPC failed; HTTP 504 curl 22 The requested URL returned
error: 504
fatal: error reading
## Chris (portmas...@bsdforge.com):
> Which is the real question. Why doesn't it Just Work?
Given that there are very few reports of such problems, I'd think
that the git mirrors do in fact "Just Work" for a vast majority of
people (it sure works for me).
And then there's the fact that you didn't
On 2022-05-02 14:07, Christoph Moench-Tegeder wrote:
## Chris (portmas...@bsdforge.com):
Which is the real question. Why doesn't it Just Work?
Given that there are very few reports of such problems, I'd think
that the git mirrors do in fact "Just Work" for a vast majority of
people (it sure w
Hello.
I'm a maintainer too :)
Probably, git is difficult for maintainers to keep the following conditions.
# git status --show-stash --
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
To clean it up without cloning, we will have to make full u
There's no need to CC me. I'm subscribed to the list.
On 5/2/22 13:37, Chris wrote:
>> Is there a reason why you can't do a git pull to accomplish this?
> Thanks for the reply, Jose.
> Sure.
Still don't understand why you can't just do a "git pull". That will
fetch and apply just the changes from
16 matches
Mail list logo
