Melpa: rsync://melpa.org/packages/ no longer working since 2018-03-29

Created on 31 Mar 2018  Â·  7Comments  Â·  Source: melpa/melpa

We use the rsync service to sync Melpa everyday. I notice it is no longer working since 2018-03-29.

~ $ rsync --list-only rsync://melpa.org/packages/
rsync: failed to connect to melpa.org: Connection refused (61)
rsync error: error in socket IO (code 10) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52/rsync/clientserver.c(106) [receiver=2.6.9]

Most helpful comment

Yeah I haven't gotten to enabling it again. Will try to get to it this weekend.

On Apr 8, 2018, at 09:56, Xu Chunyang notifications@github.com wrote:

Melpa Stable is also no longer working since 2018-04-01

rsync --list-only rsync://stable.melpa.org/packages/

rsync: failed to connect to stable.melpa.org (104.131.31.21): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128) [Receiver=3.1.0]
root@AY1309092152572985dfZ:~# less /var/log/rsync-melpa-stable.log
It was working when the issue was created.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

All 7 comments

it'll take me a bit to debug this, something to do with the upgrade i
suspect but @purcell set this up originally so i'm not sure what to check.

On Sat, Mar 31, 2018 at 7:47 AM, Xu Chunyang notifications@github.com
wrote:

We use the rsync service to sync Melpa everyday. I notice it is no longer
working since 2018-03-29.

~ $ rsync --list-only rsync://melpa.org/packages/
rsync: failed to connect to melpa.org: Connection refused (61)
rsync error: error in socket IO (code 10) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52/rsync/clientserver.c(106) [receiver=2.6.9]

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/melpa/melpa/issues/5402, or mute the thread
https://github.com/notifications/unsubscribe-auth/AACUspM7VCS9sIJSVoOl3veWckB5NElgks5tj3rpgaJpZM4TCc44
.

Yep, I'll take a look. The setup details were noted here: https://github.com/melpa/melpa/issues/4020#issuecomment-233172008

It’s all good. I can take a look thanks for the link.

On Mar 31, 2018, at 21:47, Steve Purcell notifications@github.com wrote:

Yep, I'll take a look. The setup details were noted here: #4020 (comment)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Melpa Stable is also no longer working since 2018-04-01

# rsync --list-only rsync://stable.melpa.org/packages/
rsync: failed to connect to stable.melpa.org (104.131.31.21): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128) [Receiver=3.1.0]

It was working when the issue was created.

Yeah I haven't gotten to enabling it again. Will try to get to it this weekend.

On Apr 8, 2018, at 09:56, Xu Chunyang notifications@github.com wrote:

Melpa Stable is also no longer working since 2018-04-01

rsync --list-only rsync://stable.melpa.org/packages/

rsync: failed to connect to stable.melpa.org (104.131.31.21): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128) [Receiver=3.1.0]
root@AY1309092152572985dfZ:~# less /var/log/rsync-melpa-stable.log
It was working when the issue was created.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

i fixed this. sorry for the delay.

They are working now. Thank you very much.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

vlebedev picture vlebedev  Â·  5Comments

tarsius picture tarsius  Â·  9Comments

grandynguyen picture grandynguyen  Â·  8Comments

gnusupport picture gnusupport  Â·  11Comments

nnicandro picture nnicandro  Â·  3Comments