From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Can't push: "Error unpack remote failed..."
Date: Fri, 23 Sep 2022 10:19:41 +0200 [thread overview]
Message-ID: <76707D0A-3EA5-467C-A44E-EE6272397B0B@ipfire.org> (raw)
In-Reply-To: <0bc001f7-91e5-985e-e2be-50d8467ae010@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
Hallo Matthias,
It looks like the file server had a little hick-up this night.
I restarted it and things look okay, and I cannot really find anything that might have caused this, but loads of other things didn’t work either.
So, I will keep my fingers crossed that the file server is happy again after a reboot.
Best,
-Michael
> On 23 Sep 2022, at 09:14, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> I'd like to have a problem* during pushing through GIT...:
>
> If I try something like
>
> git push mfischer unbound
>
> I get:
>
> **SNIP***
> root(a)Devel64-1: /git/ipfire-2.x # git push mfischer unbound
> mfischer(a)git.ipfire.org's password:
> Enumerating objects: 153, done.
> Counting objects: 100% (149/149), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (89/89), done.
> Writing objects: 100% (98/98), 12.06 KiB | 823.00 KiB/s, done.
> Total 98 (delta 71), reused 4 (delta 0), pack-reused 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] unbound -> unbound (unpacker error)
> error: failed to push some refs to
> 'ssh://git.ipfire.org/pub/git/people/mfischer/ipfire-2.x.git'
> ***SNAP***
>
> Something up there in GIT doesn't like me anymore...
>
> Can someone confirm?
>
> Best,
> Matthias
next prev parent reply other threads:[~2022-09-23 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 7:14 Matthias Fischer
2022-09-23 8:19 ` Michael Tremer [this message]
2022-09-23 9:01 ` Matthias Fischer
2022-09-23 12:23 ` Arne Fitzenreiter
2022-09-23 12:48 ` Matthias Fischer
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=76707D0A-3EA5-467C-A44E-EE6272397B0B@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