On 2021-10-13, Rich Freeman wrote:
> On Wed, Oct 13, 2021 at 2:50 PM Grant Edwards
> wrote:
>>
>> Is there some reason it should default
>> to doing unlimited depth fetch operations?
>>
>
> If all you want is a repo, no reason to set the depth higher.
Then a default of 1 seems like the obvious
On Wed, Oct 13, 2021 at 2:50 PM Grant Edwards wrote:
>
> Is there some reason it should default
> to doing unlimited depth fetch operations?
>
If all you want is a repo, no reason to set the depth higher. If you
want to see the history then you'll want it all.
However, once you have an initial
On Wed, 13 Oct 2021 18:50:10 - (UTC), Grant Edwards wrote:
> > emerge --sync works here. What do you have in repos.conf?
>
> I didn't have a sync-depth setting. Setting that to 1 fixed the
> problem. It was apparently timing out because it takes too long for
> the server to respond to a fet
On 2021-10-13, Neil Bothwick wrote:
> On Wed, 13 Oct 2021 18:25:12 - (UTC), Grant Edwards wrote:
>
>> Yesterday I switched my gentoo repo from rsync to git, and the initial
>> --sync with an empty directory did a git clone successfully.
>>
>> Today, when I try to sync, it always fails:
>>
>>
On Wed, 13 Oct 2021 18:25:12 - (UTC), Grant Edwards wrote:
> Yesterday I switched my gentoo repo from rsync to git, and the initial
> --sync with an empty directory did a git clone successfully.
>
> Today, when I try to sync, it always fails:
>
> $ sudo emerge --sync >>> Syncing repository
On Wed, 13 Oct 2021 18:26:04 - (UTC), Grant Edwards wrote:
> > You made the classic mistake of changing two things at once and then
> > not knowing which change caused the blow up!
>
> Indeed. You'd think by now I'd have learned not to do that...
Why should you be any different from the re
On 2021-10-13, Neil Bothwick wrote:
> You made the classic mistake of changing two things at once and then
> not knowing which change caused the blow up!
Indeed. You'd think by now I'd have learned not to do that...
--
Grant
Yesterday I switched my gentoo repo from rsync to git, and the initial
--sync with an empty directory did a git clone successfully.
Today, when I try to sync, it always fails:
$ sudo emerge --sync >>> Syncing repository 'gentoo' into
'/var/db/repos/gentoo'...
/usr/bin/git fetch origin
er
On Wed, 13 Oct 2021 01:19:51 - (UTC), Grant Edwards wrote:
> > Maybe you had previously selected one that was deprecated at some
> > point and removed from the list?
>
> I assume that 'mv /usr/portage /usr/portage-old' cause my profile
> selecttion to "go away".
It did, but if all you had
On 2021-10-13, Rich Freeman wrote:
> On Tue, Oct 12, 2021 at 9:22 PM Grant Edwards
> wrote:
>
>> On 2021-10-13, Rich Freeman wrote:
>> >
>> > Profile selection is implemented as a symlink from
>> > /etc/portage/make.profile. If you move your repository, then you need
>> > to re-select the prof
10 matches
Mail list logo