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

for atom use specific version of electron #125

Closed
muayyad-alsadi opened this issue Jun 15, 2016 · 11 comments
Closed

for atom use specific version of electron #125

muayyad-alsadi opened this issue Jun 15, 2016 · 11 comments

Comments

@muayyad-alsadi
Copy link

Atom community want to stick with electron 0.37.8 (which is actually a 1.0.1)
because more recent version dropped deprecated functions.
More recent electron versions is know to case problems.

atom/atom#11967
atom/autocomplete-plus#722
atom/autocomplete-plus#726

@1dot75cm
Copy link
Contributor

1dot75cm commented Jun 15, 2016

Thanks report. @muayyad-alsadi
More recent electron (node 6) versions does cause a lot of problems. Developers need time for the plugin compatible with the new API. Some old plugin have even stopped maintaining. I think that stability of the editor is the most important.

I plan update electron in atom-dev and atom is stable forever. :-)))~

@muayyad-alsadi
Copy link
Author

Are you going to push updates to copr with higher epoch so that rpm would automatically downgrade electron version?

@1dot75cm
Copy link
Contributor

Yes~ i will downgrade electron version by update atom.spec.

@1dot75cm
Copy link
Contributor

1dot75cm commented Jun 17, 2016

Hi @muayyad-alsadi
I have been downgraded electron version via 346724 and 346728. Please test it. Thanks.

Addition, you can use alternatives command to switch multiversion with electron. For example:

$ alternatives --config electron
  Selection    Command
-----------------------------------------------
*+ 1           /usr/lib64/electron/0.37.8/electron

@muayyad-alsadi
Copy link
Author

seems fine

[alsadi@localhost ~]$ atom --version
Atom    : 1.8.0
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0

@1dot75cm
Copy link
Contributor

Same problem. UnitedRPMs/atom#1

@muayyad-alsadi
Copy link
Author

why dnf want to give me 1.x instead of 0.37 ?

[root@localhost ~]# dnf update
Last metadata expiration check: 0:06:36 ago on Wed Jun 22 10:31:38 2016.
Dependencies resolved.
======================================================================================================================================================
 Package                                Arch                Version                              Repository                                      Size
======================================================================================================================================================
Installing:
 electron                               x86_64              1.2.3-2.prebuilt.fc23                mosquito-atom                                   32 M

@muayyad-alsadi
Copy link
Author

in /etc/dnf/dnf.conf what is the role of

installonlypkgs=electron

@1dot75cm
Copy link
Contributor

in dnf.conf man page say: @muayyad-alsadi

List of provide names of packages that should only ever be installed, never upgraded. Kernels in particular fall into this category. These packages are never removed by dnf autoremove even if they were installed as dependencies (see clean_requirements_on_remove for auto removal details). This option overrides the default installonlypkgs list used by DNF. The number of kept package versions is regulated by installonly_limit.

@muayyad-alsadi
Copy link
Author

yes, you removed the kernel from that list which cased the fedora 24 upgrade to become broken

@muayyad-alsadi
Copy link
Author

reported separately #129

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

No branches or pull requests

2 participants