| 1 |
On 07/08/2018 11:42 AM, Michał Górny wrote: |
| 2 |
> W dniu nie, 08.07.2018 o godzinie 11∶04 -0700, użytkownik Zac Medico |
| 3 |
> napisał: |
| 4 |
>> On 07/08/2018 06:56 AM, Michał Górny wrote: |
| 5 |
>>> W dniu nie, 08.07.2018 o godzinie 15∶02 +0200, użytkownik Kristian |
| 6 |
>>> Fiskerstrand napisał: |
| 7 |
>>>> On 07/08/2018 08:53 AM, Michał Górny wrote: |
| 8 |
>>>>> Is safe git syncing implemented already? If not, maybe finish it first and cover both with a single news item. Git is going to be more efficient here, so people may want to learn they have an alternative. |
| 9 |
>>>> |
| 10 |
>>>> Why complicate things, and increase wait for something that benefits |
| 11 |
>>>> most users, just to give alternatives to a few using non-default sync |
| 12 |
>>>> mechanism. Securing git distribution is a whole different ballpark. |
| 13 |
>>>> |
| 14 |
>>> |
| 15 |
>>> Let me rephrase. Let's say I'm using rsync. This new feature is |
| 16 |
>>> something positive but it breaks my use case (for one of the listed |
| 17 |
>>> reasons -- overlayfs, inode use, small fs cache). After reading this |
| 18 |
>>> news item, I learn that my only option is to disable the new feature. |
| 19 |
>>> |
| 20 |
>>> Now, I would appreciate being told that there's an alternate sync method |
| 21 |
>>> that handles secure updates without having all those drawbacks. |
| 22 |
>> |
| 23 |
>> The thing is, the normal git tree doesn't even provide pre-generated |
| 24 |
>> metadata, and I see then gentoo-mirror repo that provides metadata does |
| 25 |
>> not have commits signed with an release key: |
| 26 |
>> |
| 27 |
>> https://github.com/gentoo-mirror/gentoo/commits/stable |
| 28 |
>> |
| 29 |
>> So I'm really not comfortable recommending git to anyone at this point. |
| 30 |
> |
| 31 |
> Wrong twice. |
| 32 |
> |
| 33 |
> Firstly, the canonical URL is: |
| 34 |
> |
| 35 |
> https://anongit.gentoo.org/git/repo/sync/gentoo.git |
| 36 |
> (https://gitweb.gentoo.org/repo/sync/gentoo.git) |
| 37 |
> |
| 38 |
> Secondly, the merge commits (i.e. top commits that are verified |
| 39 |
> by Portage) are signed by dedicated key that is part of the infra key |
| 40 |
> set. In other words, it works out of the box. |
| 41 |
|
| 42 |
Is there any documentation that shows users how to migrate to git, and |
| 43 |
what the pros and cons might be? Maybe its worthy of its own news item. |
| 44 |
-- |
| 45 |
Thanks, |
| 46 |
Zac |
Archives