-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packages missing from melpa #10244
Comments
Seems like melpa is currently being rebuilt:
Hopefully back up soon. |
ok, that was the reason, now only
The following recipe wont help, because font-lock+.el specifies that it is version
|
Melpa has finished the rebuild, but I still can't install all packages properly.
|
Looks like some libraries disappeared from Melpa, because they have |
Same here, people starting from a fresh install getting error messages that "highlight" is unavailable. |
Yup, this is what I did as a workaround. Copy the missing package directories from |
@srid this doesn't work for me unfortunately. Should I require packages manually? |
@dsnipe Did you copy over each and every missing package? Maybe try copying over the entire |
Unfortunately, I removed my old |
Feel free to try with my backup of develop.zip: http://beaunix.srid.ca/tmp/develop.zip (comes with no guarantees whatsoever). |
@srid you saved my day! Thanks a lot! |
I tried to copy |
@srid appreciate the suggestion but this doesn't seem to have fixed the problem for me. I definitely picked the wrong day to do a fresh reinstall! |
Every package at the top of this issue seems to be available. Are there specific packages that are missing? |
they all got installed after the melpa finished building, the one that does not work is |
Also Edit: Also |
@milkypostman seems to be eval-sexp-fu for me |
@Fenton-Fenton I think the install of |
@milkypostman |
@jonathanschmitz I just checked this and you are correct it is |
For reference: the issue is that packages from the emacs wiki are not being rebuilt. |
Highlight is a wiki package. This is going to be an issue. @tarsius is there anyways we can get the highlight package moved to the mirror quickly and updated? |
Temp solution to get you unblocked is to manually install this package from emacs wiki.
I am not sure how we will resolve this timely. Is there a way to put this package directly into spacemacs and push a new version.
Wiki packages have been on the chopping block for 3 years. And I really think Spacemacs should avoid depending on something from the wiki anyways
But it’s also not ok for Melpa to break Spacemacs.
… On Jan 24, 2018, at 09:55, Dieter Komendera ***@***.***> wrote:
For reference: the issue is that packages from the emacs wiki are not being rebuilt. highlight is one of them. See melpa/melpa#5008 (comment) for a discussion
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
np, I will fix the wiki packages by pushing their code to spacemacs repo this evening. |
Make me think we should have been pro-active on this, lots of us knew that wiki packages were being removed from MELPA. |
I have pushed a temporary fix for |
@syl20bnr I don’t think we will add back wiki packages unless they go to the emacsmirror. |
^^^ so just a heads up ;) |
@srid Saved my day with your develop backup! Thanks!! |
So my new spacemacs install (from master) is still not working, even after @tarsius fix (not sure if deployed). Switching to
EDIT: sorry for not saying thanks for being on this so quickly anyway, and thanks @CarlQLange for giving a good example. |
Just popping in to say @milkypostman @tarsius @syl20bnr et al: you're all doing a great job and we |
@Blaisorblade Yeah, I had some urgent personal matter to attend to so I only quickly read the bottom of this thread and fixed the package I saw mentioned there. Could someone please provide a complete list of packages out of those listed here that Spacemacs may depend on. I can then do the same for those as I have done for
@CarlQLange and all the likers, thanks that means a lot. @purcell should also be mention explicitly. Thanks you Steve!
@milkypostman Well I am temporarily adding some back, but...
...going forward the Spacemacs folks and other users of these package have three options I think:
Drew is not willing to use Git or Mercurial so don't even try to fix the issue at its source. It has been tried many times already. |
@tarsius Thanks for the help and don't worry. I just wanted to point out that
They seem to come up because they are requested explicitly (not by other packages depending on them). More precisely, that's my uneducated guess (sorry) because of the following content in the Warnings buffer (I've seen other similar warnings earlier):
|
Also FWIW: for Spacemacs needs, I suspect freezing those packages at the current versions would be enough for now (or for any amount of time). |
Done a full install of Spacemacs with
This is what I've done. A new release for master branch 0.200.13 has been released to fix them, imported from Emacsmirror GitHub organization for now:
For develop branch I also pushed a fix for BTW thanks @tarsius for maintaining Emacsmirror 👍 |
Thanks for your understanding, everyone. While this is an annoying disruption in the short term, the community will be in a better place for having dropped packages that were a significant security risk. |
great, for my purposes everything seems to work again. Should I close this issue or leave it open until the 3/4 packages get fixed? Thanks to all the maintainers for the quick fixes!! |
Everything seems fixed here too, thanks again to everyone who contributed! |
please reopen if you feel the need to. |
@syl20bnr Thanks. Please do the same for |
Does Spacemacs use any of these non-wiki packages? They will have to be removed from Melpa too, so you should probably do the same for those packages as you have done for the wiki packages.
|
@steckerhalter now proxy maintains |
@tarsius Spacemacs should be good if I understood correctly what will happen: 1- The non-wiki packages that depends on If the above is true then we are fine here :-) |
@tarsius there might be transitive dependencies to consider as well. For instance |
thats correct! everything seems to be in order and highlight is building
from the new location.
thanks for all your help and understanding.
…On Thu, Jan 25, 2018 at 8:52 PM, Sylvain Benner ***@***.***> wrote:
Spacemacs should be good if I understood correctly what will happen:
1- The non-wiki packages that depends on highlight won't be removed as we
have now a new maintainer (thanks you @steckerhalter
<https://github.com/steckerhalter>)
2- all-the-icons won't be removed as font-lock+ is now an optional
dependency and has been removed from the header (
***@***.***
<domtronn/all-the-icons.el@52d1f2d>
)
If the above is true then we are fine here :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10244 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACUspA_jnMu7b7arX7nd6VKek4EqUDeks5tOT4FgaJpZM4Rq6ai>
.
|
Thank you @milkypostman |
On a fresh pull of develop @syl20bnr we have a similar situation with |
I get the following on startup, e.g.
rtags
is currently not on melpa:The text was updated successfully, but these errors were encountered: