Re: [gentoo-dev] New portage git sync behavior

2016-11-06 Thread Zac Medico 
On 09/20/2016 08:02 PM, Mike Gilbert wrote:
> Portage 2.3.1 changes the default behavior for git repositories to
> sync with a depth of 1. If you are using a development tree with
> emerge --sync, you may want to override this in repos.conf by setting
> sync-depth = 0.
> 
> If you have accidentally converted your development tree into a
> shallow repository, you can undo the damage by running git fetch
> --unshallow.
> 

I've proposed to revert the change in behavior because we've had too
many problems with it:

https://archives.gentoo.org/gentoo-portage-dev/message/e0314d5c748ec4098605c20d9b42b2a9
-- 
Thanks,
Zac

Re: [gentoo-dev] New portage git sync behavior

2016-10-13 Thread Mike Gilbert 
On Wed, Oct 12, 2016 at 2:51 PM, Mike Gilbert  wrote:
> On Wed, Oct 12, 2016 at 2:45 PM, konsolebox  wrote:
>> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>>> Portage 2.3.1 changes the default behavior for git repositories to
>>> sync with a depth of 1. If you are using a development tree with
>>> emerge --sync, you may want to override this in repos.conf by setting
>>> sync-depth = 0.
>>>
>>> If you have accidentally converted your development tree into a
>>> shallow repository, you can undo the damage by running git fetch
>>> --unshallow.
>>>
>>
>> I can't find this in the release notes.
>
> Because it isn't there. You may direct any complaints to the Portage dev team.

Correction: I do see it mentioned in RELEASE-NOTES, but in a way that
isn't obvious.

I was previously looking at the NEWS files.

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread konsolebox 
On Thu, Oct 13, 2016 at 2:51 AM, Mike Gilbert  wrote:
> You may direct any complaints to the Portage dev team.

I only intended to notify.

-- 
konsolebox

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread konsolebox 
On Thu, Oct 13, 2016 at 9:36 AM, Daniel Campbell  wrote:
> On 10/12/2016 11:45 AM, konsolebox wrote:
>> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>>> Portage 2.3.1 changes the default behavior for git repositories to
>>> sync with a depth of 1. If you are using a development tree with
>>> emerge --sync, you may want to override this in repos.conf by setting
>>> sync-depth = 0.
>>>
>>> If you have accidentally converted your development tree into a
>>> shallow repository, you can undo the damage by running git fetch
>>> --unshallow.
>>>
>>
>> I can't find this in the release notes.
>>
> Wasn't it in a news message? I recall seeing it somewhere, and made the
> appropriate changes before upgrading.
>

I think you saw it here, and so did I but surprised to see that it's
not in the /usr/share/doc/portage-2.3.1 nor in 'eselect news'.

-- 
konsolebox

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread Daniel Campbell 
On 10/12/2016 11:45 AM, konsolebox wrote:
> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>> Portage 2.3.1 changes the default behavior for git repositories to
>> sync with a depth of 1. If you are using a development tree with
>> emerge --sync, you may want to override this in repos.conf by setting
>> sync-depth = 0.
>>
>> If you have accidentally converted your development tree into a
>> shallow repository, you can undo the damage by running git fetch
>> --unshallow.
>>
> 
> I can't find this in the release notes.
> 
Wasn't it in a news message? I recall seeing it somewhere, and made the
appropriate changes before upgrading.

-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread Mike Gilbert 
On Wed, Oct 12, 2016 at 2:45 PM, konsolebox  wrote:
> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>> Portage 2.3.1 changes the default behavior for git repositories to
>> sync with a depth of 1. If you are using a development tree with
>> emerge --sync, you may want to override this in repos.conf by setting
>> sync-depth = 0.
>>
>> If you have accidentally converted your development tree into a
>> shallow repository, you can undo the damage by running git fetch
>> --unshallow.
>>
>
> I can't find this in the release notes.

Because it isn't there. You may direct any complaints to the Portage dev team.

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread konsolebox 
On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
> Portage 2.3.1 changes the default behavior for git repositories to
> sync with a depth of 1. If you are using a development tree with
> emerge --sync, you may want to override this in repos.conf by setting
> sync-depth = 0.
>
> If you have accidentally converted your development tree into a
> shallow repository, you can undo the damage by running git fetch
> --unshallow.
>

I can't find this in the release notes.

-- 
konsolebox

[gentoo-dev] New portage git sync behavior

2016-09-20 Thread Mike Gilbert 
Portage 2.3.1 changes the default behavior for git repositories to
sync with a depth of 1. If you are using a development tree with
emerge --sync, you may want to override this in repos.conf by setting
sync-depth = 0.

If you have accidentally converted your development tree into a
shallow repository, you can undo the damage by running git fetch
--unshallow.