Skip to content
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

Missing deferred package in Emacs 24.4 #42

Closed
trishume opened this issue Oct 26, 2014 · 14 comments
Closed

Missing deferred package in Emacs 24.4 #42

trishume opened this issue Oct 26, 2014 · 14 comments
Labels

Comments

@trishume
Copy link
Contributor

After updating my spacemacs to b50bda33ea2506acc374159c0df7e6cc7090a9ddh today, after the first launch it went through an orphan package deletion cycle where it says it deleted 11 packages, which it didn't list. I don't think there should have been that many orphaned packages, it might have been a bit overzealous.

Now on startup I get a warnings buffer opening up with the following error (yes it is repeated 3 times):

Warning (emacs): Unable to activate package `concurrent'.
Required package `deferred-0.3.1' is unavailable
Warning (emacs): Unable to activate package `concurrent'.
Required package `deferred-0.3.1' is unavailable
Warning (emacs): Unable to activate package `concurrent'.
Required package `deferred-0.3.1' is unavailable

I suspect the orphan deleter might have deleted the deferred package even though concurrent depends on it.

@trishume
Copy link
Contributor Author

Adding deferred to the packages list of my contrib layer fixes the problem, but I think there might be some deeper underlying problem here.

@syl20bnr
Copy link
Owner

@trishume Is this related to your layer ?

@syl20bnr
Copy link
Owner

Oh ok it is related to your config, I'll see if I can reproduce it.

@trishume
Copy link
Contributor Author

I don't have any evidence that it is related to my layers or configs. I just added it to my layer's package list because it's mine, I could have added it to the main one and that would have solved it as well.

Do you know which package depends on concurrent?

@syl20bnr
Copy link
Owner

Just tried your layer and it is ok for me, I think you had not fetched this commit 7c3a2f3 yet.

@syl20bnr
Copy link
Owner

Sorry I was just checking quickly, and you wrote that you pulled the last changes from upstream.
Next time this bug occurs you can see the list of deleted packages in the Message buffer. It will be a good pointer to be able to reproduce it.

@syl20bnr
Copy link
Owner

@trishume Try to remember the packages that you have tested in the last couple of days and that you have removed from your packages. The key to the repro step is in one of them which is very valuable to me :-)

@syl20bnr
Copy link
Owner

Packages dependencies:

Packages which depend on deferred:

  • concurrent
  • python-environment

Packages which depend on concurrent:

  • epc

To get the list, in scratch buffer:

(message "%s" (contribsys/load-package-dependencies))

@punassuming
Copy link
Contributor

Now that I have been disabling packages in ~/.spacemacs, I had this issue as well. Both deferred and pkg-info were wiped out but were still needed as dependencies for the remaining packages. I just did a package-install to get them back, and haven't had them wiped again.

@syl20bnr
Copy link
Owner

@Ralesi Can you write the list of packages you disabled ? I hope to identify which packages cause the bug.

@trishume
Copy link
Contributor Author

The only package I have disabled is jedi.

@punassuming
Copy link
Contributor

I disabled many. I will get the lost when I get home, but jedi was among the packages

@syl20bnr
Copy link
Owner

syl20bnr commented Nov 1, 2014

I'll try to use the force to kick this bug then :-)

@syl20bnr
Copy link
Owner

@trishume @Ralesi Fixed in develop (89a8873)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants