| 1 |
On Fri, Aug 28, 2015 at 1:32 PM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> On Friday 28 Aug 2015 18:26:12 Rich Freeman wrote: |
| 3 |
>> On Fri, Aug 28, 2015 at 11:20 AM, Philip Webb <purslow@××××××××.net> wrote: |
| 4 |
>> > 150828 Rich Freeman wrote: |
| 5 |
>> >> git whatchanged /usr/portage/sys-libs/ncurses > /tmp/log.txt |
| 6 |
>> > |
| 7 |
>> > Tested as user : |
| 8 |
>> > 690: ~> git whatchanged /usr/portage/sys-libs/ncurses > tmp/log.txt |
| 9 |
>> > fatal: Not a git repository (or any parent up to mount point /home) |
| 10 |
>> > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not |
| 11 |
>> > set). |
| 12 |
>> |
| 13 |
>> You're probably not using git to fetch your portage tree. |
| 14 |
>> |
| 15 |
>> cat /etc/portage/repos.conf/gentoo.conf |
| 16 |
>> [DEFAULT] |
| 17 |
>> main-repo = gentoo |
| 18 |
>> |
| 19 |
>> [gentoo] |
| 20 |
>> location = /usr/portage |
| 21 |
>> sync-type = git |
| 22 |
>> sync-uri = https://github.com/gentoo-mirror/gentoo.git |
| 23 |
>> auto-sync = yes |
| 24 |
>> |
| 25 |
>> Fix that and you'll be fine. Be aware that you're not going to have |
| 26 |
>> any changelogs once you do this. I'm not certain but you might have |
| 27 |
>> to delete /usr/portage first - I have no idea how it handles existing |
| 28 |
>> files. |
| 29 |
> |
| 30 |
> Just to make sure, for the rest us there's no need to change the current rsync |
| 31 |
> mechanism, yes? Otherwise we would see some enotice popping up? |
| 32 |
|
| 33 |
There is no requirement to sync using git. If there were you'd have |
| 34 |
gotten more news about it. |
| 35 |
|
| 36 |
The current plan is to re-introduce changelogs. I couldn't tell you |
| 37 |
when this will happen, but it probably won't take terribly long. |
| 38 |
|
| 39 |
Those who wish to use git can do so, and I'd encourage people to try. |
| 40 |
It really does have a lot of advantages. Oh, and it makes it really |
| 41 |
easy to contribute patches/etc (just edit whatever you want in |
| 42 |
/usr/portage and type git diff). |
| 43 |
|
| 44 |
There really isn't any intent to cause people headaches, but please do |
| 45 |
realize that there aren't a lot of people doing the work, especially |
| 46 |
for big changes like this. There were a million big things that could |
| 47 |
go wrong with the migration and a few of the more serious ones |
| 48 |
actually did go wrong, so there wasn't as much time for dealing with |
| 49 |
stuff like this. |
| 50 |
|
| 51 |
And in terms of user-impacting issues this ncurses foul-up was |
| 52 |
probably the biggest issue I've seen hit the stable tree in a year or |
| 53 |
two, and compared to some things I dealt with on Gentoo 10 years ago |
| 54 |
it was pretty minor. I'm actually impressed how stable is considering |
| 55 |
we don't have as many bodies as we did back then. When these sorts of |
| 56 |
things come up your best bet is to just hold off on updating and |
| 57 |
re-sync in a day or two, and by all means file a bug or take it to the |
| 58 |
lists. |
| 59 |
|
| 60 |
-- |
| 61 |
Rich |
Archives