SynoCommunity / spksrc

Cross compilation framework to create native packages for the Synology's NAS
https://synocommunity.com
Other
3.02k stars 1.23k forks source link

[MAINTENANCE] synocommunity.com down #1452

Closed Diaoul closed 9 years ago

Diaoul commented 9 years ago

Due to performance issues, the server will be down for maintenance for a few days.

Manual downloads available at: http://synocommunity.com/packages/

cytec commented 9 years ago

@Webunity updates will work automatically if the repo is back up online

lihoru99 commented 9 years ago

That's great, it's also what I concern.

plopes1960 commented 9 years ago

Anyway, I think it will be bery usefull to uderstand how to do it... But if no one give a clue...

cytec commented 9 years ago

@plopes1960 to answer your question... if you try and install a SPK which needs another SPK to run (depends on it) then you'll get a message which tells you which SPK is needed ;)

In your case i'm pretty sure that you'll need python 2.x. as far as i know there aren't any packages at the moment which depend on python 3

EDIT: you don't even need anything to install transmission. Just checked and it doesn't seem to depend on any other SPK.

@Diaoul @Dr-Bean seems like there are some leftover vars in transmissions dsm-control https://github.com/SynoCommunity/spksrc/blob/develop/spk/transmission/src/dsm-control.sh#L9-L10

Diaoul commented 9 years ago

As I announced on Twitter the repository is back online, I will add packages this evening.

@cytec: this is not a leftover but part of this commit : https://github.com/SynoCommunity/spksrc/commit/a8bd69a0aee1a8f809a81c2d1c223562239f8a0b

cytec commented 9 years ago

@Diaoul oh i see, so python is like a optional requirement... not needed by transmission but if you have it and like to run python scripts you can?

Diaoul commented 9 years ago

That's right. You just need this so transmission can find python in the PATH if you want to run python scripts.

plopes1960 commented 9 years ago

Hi! Thanks for your great hard work! I know that it's runing again the server. But one thing, if I install manuallyk, (I have ds212j - architecture 88f6281), so I need spk transmission_10_88f628x_1594.spk, than I need to force any python or I need to show any path to run them?

JorenRapini commented 9 years ago

I'm guessing something is still wrong even though you said it's back up. https://synocommunity.com/packages/ 404's and my community tab is still blank. Thought I'd post a comment in case it was just on my end some how

gasparraposo commented 9 years ago

I too see cannot see any packages on my community tab. Can you please confirm if the server and service is back up.

gasparraposo commented 9 years ago

is the repo info, we are to use, still the same? here is what i am using. http://packages.synocommunity.com/

Superturk10 commented 9 years ago

The official website is on but the package 'side' is still a work in progress (i think)

Op 28 jan. 2015 om 3:23 p.m. heeft gasparraposo notifications@github.com het volgende geschreven:

is the repo info, we are to use, still the same? here is what i am using. http://packages.synocommunity.com/

— Reply to this email directly or view it on GitHub.

gasparraposo commented 9 years ago

Any idea when i will be able to view the packages on my DSM?

JorenRapini commented 9 years ago

Just let them do their thing. It's a free service supplied by other members of the community. Too much entitlement in this thread. Sounds like Diaoul still has to add packages to the new repository, which he said he would do tonight earlier in the thread.

gasparraposo commented 9 years ago

Didn't mean any disrespect and it was just a simple question. I understand its a free service and wasnt demanding a fix.

Thanks to the site providers for all their work and help in getting this back up.

Cheers.

Diaoul commented 9 years ago

Still planned for this evening, working on it.

Dr-Bean commented 9 years ago

@Diaoul Need a hand?

Diaoul commented 9 years ago

@SynoCommunity/developers please register at https://synocommunity.com/register so I can grant you access (again) and confirm here when registered.

Dr-Bean commented 9 years ago

Done.

Diaoul commented 9 years ago

Server is up and running. Thanks for your patience.

blackjid commented 9 years ago

Thanks to you!!

cytec commented 9 years ago

@Diaoul Done but got a 500 error when submitting registration form, seemed to work as i got "email already taken" error on 2nd try

croftyboy commented 9 years ago

Is there any chance to get older versions of transmission, due to the fact the latest version is giving out wrong information on different sites ? 1.93 or 2.03 preferably.

Diaoul commented 9 years ago

What do you mean? Please open a new issue.

croftyboy commented 9 years ago

Its not an issue on all sites, but on some sites newer version of transmission can display wrong information on the trackers wich can be seen as cheating. Its not cheating but it shows up as it and you risk getting banned from several closed trackers. Thats all. Basically all transmission versions above version 2.03 including webgui.

dabruna commented 9 years ago

30 January Is still down !

http://packages.synocommunity.com/ Bad Request The browser (or proxy) sent a request that this server could not understand.

Diaoul commented 9 years ago

No it's not

cow-brat commented 9 years ago

It's up. proof: https://www.dropbox.com/s/vj7j3rflkj9b941/2015-01-30%2010.35.02.png?dl=0

dabruna commented 9 years ago

I did not speak about the nas functionality that is ok, but web access ... Now it says "Not Found The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again."

Dr-Bean commented 9 years ago

@dabruna The web page for you to visit is https://synocommunity.com/. http://packages.synocommunity.com/ is strictly for your NAS.

@Diaoul About that access...? Have a couple changes (remove/disable testpackage and probably oscam, add debian-choot for the new arches (completely missed that one the first time around)

Diaoul commented 9 years ago

@Dr-Bean: there's been some problem with the email validation process, I'll fix this and you'll be able to publish again.

Diaoul commented 9 years ago

@Dr-Bean @cytec: resend the confirmation email with https://synocommunity.com/confirm and after you can login at https://synocommunity.com/login and get your API key in your profile page.

Dr-Bean commented 9 years ago

Nice! :+1:

DarkCupid commented 9 years ago

Is it down again? I am getting an error again invalid location from my NAS when i add the link.

Dr-Bean commented 9 years ago

@DarkCupid Nope, but the service might have been restarting just as you were adding the repository. Shouldn't take more than a couple of minutes at most, so give it another try.

balabalaman commented 9 years ago

I got "invalid location" again. Is it down?

Diaoul commented 9 years ago

Are you using ipv6? If that's the case, we don't serve ipv6 yet.

balabalaman commented 9 years ago

No... I don't think I am using IPv6. What can I do now?

balabalaman commented 9 years ago

Never mind, I fix it. Now it is working for me. Thx

mal68 commented 9 years ago

Hey guys I am still getting the "invalid location" error and have followed all guidance above, can anyone who fixed this error explain how they did so?

brunho commented 9 years ago

hello

same problem as mal68 : invalid location

Dr-Bean commented 9 years ago

@brunho: See https://github.com/SynoCommunity/spksrc/issues/1476. I wonder if everyone with this issue is using the same ISP or something...

yvon56 commented 9 years ago

Hello I still have the same "invalid location" issue - DS212J - ISP "FREE" (France)

Is it a general issue ??

brunho commented 9 years ago

Yep

I connect via Free : invalid location via an VPN provider : work fine

yvon56 commented 9 years ago

For the French 'Free' ISP, it's a DNS issue I resolved it by changing DNS server in the NAS by 8.8.8.8 and 8.8.4.4

No need of VPN

nlamirault commented 9 years ago

Same problem here. Why this issue is closed ?

DarkCupid commented 9 years ago

Mine got fixed by disabling IP v6 in my Synology NAS.