nicferrier
expired certificate for marmalade-repo.org
As foretold in #106, it might take a while, but hopefully we can get another three-year renewal :)
FWIW, I had very good experience with https://letsencrypt.org/. One can set up the renewal automatically.
Letsencrypt is definitely the way to go forwards. It's free, and once setup, it features automatic renewal.
What's not to like?
Emacswiki now considers this repository as discontinued, so perhaps the best course is to consider it abandonware.
I’m no official representative for marmalade, nor do I in any way have the authority to speak on its behalf…
That said: This is a production-stopping bug which has persisted for more than 4 years, without Nic ever, not once, responded, acknowledged it nor promising a fix.
That’s almost half a decade.
Marmalade as an alternate repo is gone. People aren’t publishing there anymore and haven’t for 4+ years. If it ever gets back online, it will exclusively contain obsolete or broken packages.
It’s dead.
Thanks @nicferrier for running marmalade for us over the year. It was greatly appreciated!
But as a community, we have ELPA, non-GNU ELPA and MELPA to rely on, and there’s no point keeping marmalade around as a zombie. It’s time to let go.
(And maybe even @tpapp can close this issue to acknowledge that?)
@josteink: I don't understand what closing an issue that is unfixed has to do with signaling that a repo is abandoned. It may remain unfixed forever, but I don't see how closing it would help.
The maintainer can archive the repository and then all issues would be frozen.
Yes, this project seems to be anadoned, cf #158.
I mean the issue is fixed/resolved since we as Emacs-users still have plenty of repos to choose from.
And as things are now, reviving marmalade will only make things worse, not better.