From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: GIT - 'push' / 'pull' not working
Date: Sat, 29 Nov 2014 15:16:30 +0100 [thread overview]
Message-ID: <1417270590.14452.26.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <5479C098.8060208@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
The machine had a bit of trouble and I rebooted it. Should work fine
now.
You should check the email address that you use to send emails to this
list. I get in my header that you sent it to "ipfire(a)mail01.ipfire.org".
-Michael
On Sat, 2014-11-29 at 13:48 +0100, Matthias Fischer wrote:
> Hi,
>
> since yesterday, while trying to 'push' some updates (grep / hdparm /
> gnupg) to repo, I'm getting the following errors:
>
> ***SNIP***
> root(a)Devel: /home/matz/ipfire-2.x # git push mfischer gnupg
> ssh: connect to host git.ipfire.org port 22: No route to host
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> ***SNAP***
>
> The same happens with - for example - 'git pull origin next'.
>
> Testing with 'ping':
>
> ***SNIP***
> root(a)Devel: /home/matz/ipfire-2.x # ping git.ipfire.org
> PING gw03.ipfire.org (178.63.73.248) 56(84) bytes of data.
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=1 ttl=53 time=17.8 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=2 ttl=53 time=17.3 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=3 ttl=53 time=16.8 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=4 ttl=53 time=18.8 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=5 ttl=53 time=16.7 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=6 ttl=53 time=17.6 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=7 ttl=53 time=16.4 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=8 ttl=53 time=17.1 ms
> 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=9 ttl=53 time=17.7 ms
> ^C
> --- gw03.ipfire.org ping statistics ---
> 10 packets transmitted, 9 received, 10% packet loss, time 9014ms
> rtt min/avg/max/mdev = 16.491/17.393/18.810/0.680 ms
> ***SNAP***
>
> The machine had no problems so far, updates are running ('apt-get ...'
> is working OK) - in my opinion I didn't change anything.
>
> Bug or Feature?
>
> Regards
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-11-29 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 12:48 Matthias Fischer
2014-11-29 14:16 ` 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=1417270590.14452.26.camel@rice-oxley.tremer.info \
--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