Skip to content

[WIP] Update Atom from 1.9.0 to 1.12.2 #196

Closed
wants to merge 1 commit into from

Conversation

pmenzel
Copy link
Collaborator

@pmenzel pmenzel commented Nov 15, 2016

No description provided.

@david
Copy link
Collaborator

david commented Nov 15, 2016

you mean atom not tom or? ;)

@pmenzel
Copy link
Collaborator Author

pmenzel commented Nov 15, 2016

This doesn’t build yet due to permission problems.

[BEE] /dev/shm/bee-root/atom/atom-1.12.2-0/source/script/build --build-dir /dev/shm/bee-root/atom/atom-1.12.2-0/build
Node:   v6.2.1
Npm:    v3.9.3
Installing script dependencies
Installing apm
npm ERR! Linux 4.8.4.mx64.111
npm ERR! argv "/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/bin/node" "/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/node_modules/.bin/npm
" "dedupe"
npm ERR! node v4.4.5
npm ERR! npm  v3.10.5
npm ERR! path /dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/node_modules/npm/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access

npm ERR! Error: EACCES: permission denied, access '/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/node_modules/npm/node_modules'
npm ERR!     at Error (native)
npm ERR!  { [Error: EACCES: permission denied, access '/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/node_modules/npm/node_modules']
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/node_modules/npm/node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/npm-debug.log
module.js:327
    throw err;
    ^

Error: Cannot find module 'node-gyp/bin/node-gyp'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.require.resolve (internal/module.js:16:19)
    at new Install (/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/lib/install.js:53:38)
    at Object.module.exports.run (/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/lib/apm-cli.js:226:18)
    at Object.<anonymous> (/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/lib/cli.js:8:7)
    at Object.<anonymous> (/dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/lib/cli.js:12:4)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
child_process.js:509
    throw err;
    ^

Error: Command failed: /dev/shm/bee-root/atom/atom-1.12.2-0/source/apm/node_modules/atom-package-manager/bin/apm --loglevel=error install
    at checkExecSyncError (child_process.js:486:13)
    at Object.execFileSync (child_process.js:506:13)
    at module.exports (/dev/shm/bee-root/atom/atom-1.12.2-0/source/script/lib/install-atom-dependencies.js:19:16)
    at Object.<anonymous> (/dev/shm/bee-root/atom/atom-1.12.2-0/source/script/bootstrap:28:1)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)   
    at tryModuleLoad (module.js:417:12) 
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)

Der Nutzer root hat kein nodejs installiert.

root:heulsuse:/home/pmenzel/bee-files/# BEE_TMP_TMPDIR=/dev/shm BEE_TMP_BUILDROOT=/dev/shm/bee-root BEE_MAKEFLAGS='-j' ./atom.be0 -c
BEE v1.2.11 2009-2016
  by  Marius Tolzmann <marius@mariux.de>
      Matthias Ruester <ruester@molgen.mpg.de>
      Tobias Dreyer <dreyer@molgen.mpg.de>

[BEE]   BEE_SKIPLIST           /etc/bee/skiplist
[BEE]   BEE_REPOSITORY_PREFIX  /src/mariux/beeroot
[BEE]   BEE_METADIR            /usr/share/bee
[BEE]   BEE_TMP_TMPDIR         /dev/shm
[BEE]   BEE_TMP_BUILDROOT      /dev/shm/bee-root
[BEE] current working directory: /home/pmenzel/bee-files
[BEE] ==> initializing build environment ..
[BEE]  -> creating source dir /dev/shm/bee-root/atom/atom-1.12.2-0/source
[BEE]  -> creating image dir /dev/shm/bee-root/atom/atom-1.12.2-0/image
[BEE] ==> checking repositories ..
[BEE] ==> building atom-1.12.2-0.x86_64 ..
[BEE] => entering bee_getsources() ..
[BEE] fetching https://github.com/atom/atom/archive/v1.12.2.tar.gz
File `/dev/shm/bee-root/atom/files/v1.12.2.tar.gz' already there; not retrieving.
-rw-r--r-- 1 root system 9224822 Nov 15 09:37 /dev/shm/bee-root/atom/files/v1.12.2.tar.gz
[BEE] <= leaving bee_getsources() ..
[BEE] => entering bee_extract() ..
[BEE]  -> extracting main source /dev/shm/bee-root/atom/files/v1.12.2.tar.gz ..
[BEE] tar xof /dev/shm/bee-root/atom/files/v1.12.2.tar.gz -C /dev/shm/bee-root/atom/atom-1.12.2-0/source --strip-components 1
[BEE]  -> all sources extracted to: /dev/shm/bee-root/atom/atom-1.12.2-0/source ..
[BEE] <= leaving bee_extract() ..
[BEE] changing to source directory: /dev/shm/bee-root/atom/atom-1.12.2-0/source
[BEE] => entering bee_patch() ..
[BEE] <= leaving bee_patch() ..
[BEE]  -> creating build dir /dev/shm/bee-root/atom/atom-1.12.2-0/build
[BEE] changing to build directory: /dev/shm/bee-root/atom/atom-1.12.2-0/build
[BEE] => entering bee_configure() ..
[BEE] action 'bee_configure' is not defined: skipping..
[BEE] <= leaving bee_configure() ..
[BEE] => entering mee_build() ..
[BEE] /dev/shm/bee-root/atom/atom-1.12.2-0/source/script/build --build-dir /dev/shm/bee-root/atom/atom-1.12.2-0/build
/usr/bin/env: node: No such file or directory

@pmenzel
Copy link
Collaborator Author

pmenzel commented Nov 15, 2016

@david, yes I do.

Requested by Peter Arndt [1].

Release notes for 1.12.2 [2]:

> *   Fixed slow startup when launched from macOS dock and occasional
>     hanging during startup on Linux.
>     https://github.com/atom/atom/pull/13199

Release notes for 1.12.0 [3].

> # Notable Changes
>
> ### International Keyboard Support
>
> New APIs available in Chrome 52 allowed us to take on this
> [long-requested
> feature](https://github.com/atom/atom-keymap/issues/35). The new APIs
> turned out to be less important than we originally thought but we're
> nonetheless happy to report Atom users in all locales now get typical
> keyboard behavior in Atom's default installation.
>
> ### Electron 1.3
>
> Thanks to some amazing work by community maintainer
> [@thomasjo](https://github.com/thomasjo), Atom comes out of the
> Electron dark ages in this release with an update to 1.3.6, bringing
> Chrome 52 along for the ride.
>
> ### Keybinding Usability
>
> The scope specificity rules for keybindings were understandably
> confusing lots of Atom users. This release has a [major
> simplification](https://github.com/atom/atom/pull/12760) such that
> user-defined keybindings take precedence.
>
> ### Windows Fixes
>
> There are a number of tweaks specific to Atom on Windows, including:
>
> - [Shell Integration upgrade reliability](https://github.com/atom/atom/issues/12642)
> - [Allow multiple instances on Windows](https://github.com/atom/atom/issues/9459)
> - [Move emacs editor bindings to Darwin to avoid Windows menu conflicts](https://github.com/atom/atom/pull/12892)
>
> As ever, you can find all the gory details in the full [release
> notes](https://github.com/atom/atom/releases/tag/v1.12.0-beta0).

[1] Atom Editor, 11/15/16 08:47
[2] https://github.com/atom/atom/releases/tag/v1.12.2
[3] https://github.com/atom/atom/releases/tag/v1.12.0
@pmenzel pmenzel force-pushed the update-atom-from-1.9.0-to-1.12.2 branch from 9c092e4 to 09dc266 Compare November 15, 2016 10:29
@pmenzel
Copy link
Collaborator Author

pmenzel commented Dec 6, 2016

Superseded by merge/pull request #232.

@pmenzel pmenzel closed this Dec 6, 2016
@donald donald deleted the update-atom-from-1.9.0-to-1.12.2 branch December 14, 2016 14:39
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants