public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: git push => "id: cannot find name for group ID 1000"
Date: Tue, 21 Aug 2018 19:52:30 +0100	[thread overview]
Message-ID: <356aae3492ec4c264b788450c53afbf8c6717f81.camel@ipfire.org> (raw)
In-Reply-To: <3ad990c2-60c6-dccb-b027-56b87901bab8@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

Hello,

yes, I just had to rename a could of users and give them a new ID.

  https://bugzilla.ipfire.org/show_bug.cgi?id=11795

On some systems, it took a second until their caches forget the old IDs and used
the new ones.

All should be back now.

Best,
-Michael

On Tue, 2018-08-21 at 18:30 +0200, Matthias Fischer wrote:
> Hi!
> 
> During pushing 'nano 2.9.8' today I got the following:
> 
> ...
> root(a)Devel: /home/matz/ipfire-2.x # git push mfischer nano
> mfischer(a)git.ipfire.org's password:
> id: cannot find name for group ID 1000
> Enumerating objects: 70, done.
> Counting objects: 100% (67/67), done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (40/40), done.
> Writing objects: 100% (41/41), 4.18 KiB | 713.00 KiB/s, done.
> Total 41 (delta 28), reused 0 (delta 0)
> error: remote unpack failed: unable to create temporary object directory
> To ssh://git.ipfire.org/pub/git/people/mfischer/ipfire-2.x.git
>  ! [remote rejected]     nano -> nano (unpacker error)
> error: failed to push some refs to
> 'ssh://mfischer(a)git.ipfire.org/pub/git/people/mfischer/ipfire-2.x.git'
> ...
> 
> Upload failed - looks like someone up there doesn't like me. ;-)
> 
> Anyone else?
> 
> Best,
> Matthias


      reply	other threads:[~2018-08-21 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 16:30 Matthias Fischer
2018-08-21 18:52 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=356aae3492ec4c264b788450c53afbf8c6717f81.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox