1. Forum
  2. Usenet
  3. COMP.UNIX.BSD.FREEBSD.MIS

  • Ports error with git index

    From Louis Epstein@21:1/5 to All on Sun Nov 13 18:22:13 2022
    My latest attempt at
    git -C /usr/ports pull
    returned a fatal "index file smaller than expected"
    message.

    This was after a fsck episode,and a reboot
    that required turning the clock back.

    Do I need to reinitialize the git or will this go away
    with time?

    -=-=-
    The World Trade Center towers MUST rise again,
    at least as tall as before...or terror has triumphed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steven G. Kargl@21:1/5 to Louis Epstein on Mon Nov 14 17:40:23 2022
    On Sun, 13 Nov 2022 18:22:13 +0000, Louis Epstein wrote:

    My latest attempt at
    git -C /usr/ports pull
    returned a fatal "index file smaller than expected"
    message.

    This was after a fsck episode,and a reboot
    that required turning the clock back.

    Do I need to reinitialize the git or will this go away
    with time?


    Try to fetch a new index.

    % git pull -ff
    % make fetchindex

    The pull may not be necessary. This should update
    /usr/ports/INDEX-13 (12 or 14).

    --
    steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christian Weisgerber@21:1/5 to Steven G. Kargl on Mon Nov 14 18:58:54 2022
    On 2022-11-14, Steven G. Kargl <sgk@REMOVEtroutmask.apl.washington.edu> wrote:

    git -C /usr/ports pull
    returned a fatal "index file smaller than expected"
    message.

    Try to fetch a new index.

    % git pull -ff
    % make fetchindex

    You misunderstand the problem. It is git(1) that complains that
    its index file (.git/index I guess) is corrupt. This has nothing
    to do with the ports tree INDEX-* file.

    --
    Christian "naddy" Weisgerber naddy@mips.inka.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steven G. Kargl@21:1/5 to Christian Weisgerber on Mon Nov 14 20:15:32 2022
    On Mon, 14 Nov 2022 18:58:54 +0000, Christian Weisgerber wrote:

    On 2022-11-14, Steven G. Kargl <sgk@REMOVEtroutmask.apl.washington.edu> wrote:

    git -C /usr/ports pull
    returned a fatal "index file smaller than expected"
    message.

    Try to fetch a new index.

    % git pull -ff
    % make fetchindex

    You misunderstand the problem. It is git(1) that complains that
    its index file (.git/index I guess) is corrupt. This has nothing
    to do with the ports tree INDEX-* file.

    Yep that's possible. However, one can get the same error
    with "make fetchindex".

    --
    steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Louis Epstein@21:1/5 to Steven G. Kargl on Mon Nov 14 20:49:39 2022
    Steven G. Kargl <sgk@removetroutmask.apl.washington.edu> wrote:
    On Sun, 13 Nov 2022 18:22:13 +0000, Louis Epstein wrote:

    My latest attempt at
    git -C /usr/ports pull
    returned a fatal "index file smaller than expected"
    message.

    This was after a fsck episode,and a reboot
    that required turning the clock back.

    Do I need to reinitialize the git or will this go away
    with time?


    Try to fetch a new index.

    % git pull -ff
    % make fetchindex

    The pull may not be necessary. This should update
    /usr/ports/INDEX-13 (12 or 14).


    I wound up relocating my existing /usr/ports to a backup disk
    and fetching a new clone.
    I do not have a /usr/ports/INDEX* apparently.

    -=-=-
    The World Trade Center towers MUST rise again,
    at least as tall as before...or terror has triumphed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)