• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

Update to v2.9.0 fail

Scheduled Pinned Locked Moved Solved Troubleshooting
48 Posts 3 Posters 12.3k Views 3 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    bdream
    last edited by sdetweil Oct 16, 2019, 4:54 PM Oct 16, 2019, 4:45 PM

    @sdetweil said in Update to v2.9.0 fail:

    hm… if package.lock.json does NOT exist

    nono, it did exist

    pi@MagicMirror:~/MagicMirror $  ls pack*
    package.json  package-lock.json
    

    but the script run fast

    bash -c "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)" force
    

    what path I can find the install.log?

    –
    cheers, bdream

    S 1 Reply Last reply Oct 16, 2019, 4:54 PM Reply Quote 0
    • S Offline
      sdetweil @bdream
      last edited by Oct 16, 2019, 4:54 PM

      @bdream sorry, not install… upgrade.log

      doing test run = false
      update log will be in /home/pi/MagicMirror/installers/upgrade.log

      on the package-lock.json… it is the same as the update… thus why it didn’t stop

      could edit it an add a space someplace

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 0
      • B Offline
        bdream
        last edited by Oct 16, 2019, 5:16 PM

        @sdetweil upgrade.log is here from …force… no it isn’t.
        I can’t copy the 2738 lines in here.
        How can I bring it to you?

        And what does this mean?

        on the package-lock.json… it is the same as the update… thus why it didn’t stop
        
        could edit it an add a space someplace
        

        –
        cheers, bdream

        S 1 Reply Last reply Oct 16, 2019, 5:20 PM Reply Quote 0
        • S Offline
          sdetweil @bdream
          last edited by sdetweil Oct 16, 2019, 5:20 PM Oct 16, 2019, 5:20 PM

          @bdream said in Update to v2.9.0 fail:

          upgrade.log is here from …force… no it isn’t.
          I can’t copy the 2738 lines in here.

          you can email it , same userid as here on gmail

          And what does this mean?
          
          on the package-lock.json… it is the same as the update… thus why it didn’t stop
          
          could edit it an add a space someplace
          

          the upgrade should have stopped at the package-lock.json file, just like before…
          but it didn’t… so I looked back at the 2.9.0 package being installed, and it has a package-lock.json file…

          so, the one now on the disk is the new one… and a git status will show it hasn’t changed…

          so, we could MAKE it be different, by using a text editor (like the one you use on the config.js file)
          and add 1 space character (hit the spacebar)
          and then save it… then it will be different

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • B Offline
            bdream
            last edited by Oct 16, 2019, 5:43 PM

            got u mail from me? I would send you logs then.

            @sdetweil said in Update to v2.9.0 fail:

            so, we could MAKE it be different, by using a text editor (like the one you use on the config.js file)
            and add 1 space character (hit the spacebar)
            and then save it… then it will be different

            Is this you ask me to do? and rund your script again to see if it works now?

            –
            cheers, bdream

            S 1 Reply Last reply Oct 16, 2019, 5:44 PM Reply Quote 0
            • S Offline
              sdetweil @bdream
              last edited by Oct 16, 2019, 5:44 PM

              @bdream i got one mail and replied. have not got any more

              yes, was a way to test. if u can

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • B Offline
                bdream
                last edited by Oct 16, 2019, 6:07 PM

                @sdetweil said in Update to v2.9.0 fail:

                if u can

                Got it

                Upgrade started - Mi Okt 16 20:03:22 CEST 2019
                user requested to apply changes
                doing test run = false
                
                saving custom.css
                not english or locale not set, set git alias
                alias egrep='egrep --color=auto'
                alias fgrep='fgrep --color=auto'
                alias git='LC_ALL=en_US.UTF-8 git'
                alias grep='grep --color=auto'
                alias ls='ls --color=auto'
                remote name = origin
                local version 2.9.0 already same as master 2.9.0
                restoring custom.css
                removing git alias
                Upgrade ended - Mi Okt 16 20:03:22 CEST 2019
                

                there is no statement about the package-lock.json where I added spaces and saved it.

                Seems it works fine :grinning_face_with_smiling_eyes:

                One question I have now.
                Would it make sense changing the guide for update MM using your script instead of git pull && npm install?
                Or is this only a option in case of failure?

                –
                cheers, bdream

                S 1 Reply Last reply Oct 16, 2019, 6:11 PM Reply Quote 0
                • S Offline
                  sdetweil @bdream
                  last edited by Oct 16, 2019, 6:11 PM

                  @bdream said in Update to v2.9.0 fail:

                  local version 2.9.0 already same as master 2.9.0
                  restoring custom.css

                  if you do apply, then if the versions are the same, it just exits… if you use force then it keeps going…

                  try with force instead of apply

                  … once we get this tested I will submit to add to the product… u are helping me test… and I thank you very much!!

                  i have 3 scripts.
                  1 updated installer
                  2 new updater
                  3 one for fixing pm2 without having to do installer

                  will submit them all

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    bdream
                    last edited by Oct 16, 2019, 6:19 PM

                    @sdetweil said in Update to v2.9.0 fail:

                    try with force instead of apply

                    Interesting. Now I get 2 package-lock.json listed…

                    pi@MagicMirror:~/MagicMirror $  bash -c -i  "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)" force
                    doing test run = false
                    update log will be in /home/pi/MagicMirror/installers/upgrade.log
                    
                    saving custom.css
                    upgrading from version 2.9.0 to 2.9.0
                    fetching latest revisions
                    there are 2 local files that are different than the master repo
                    
                       package-lock.json
                       vendor/package-lock.json
                    
                    any *-lock.json files do not need to be saved
                    do you want to save these files for later   (Y/n)?y
                    git: 'git_user_name' ist kein Git-Befehl. Siehe 'git --help'.
                    updating MagicMirror runtime, please wait
                    
                    > magicmirror@2.9.0 install /home/pi/MagicMirror
                    > cd vendor && npm install
                    
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    
                    audited 220 packages in 23.225s
                    found 5 vulnerabilities (4 low, 1 high)
                      run `npm audit fix` to fix them, or `npm audit` for details
                    
                    > magicmirror@2.9.0 postinstall /home/pi/MagicMirror
                    > sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts
                    
                    MagicMirror installation successful!
                    
                    > magicmirror@2.9.0 install-fonts /home/pi/MagicMirror
                    > cd fonts && npm install
                    
                    audited 1 package in 0.999s
                    found 0 vulnerabilities
                    
                    npm WARN acorn-jsx@5.0.2 requires a peer of acorn@^6.0.0 || ^7.0.0 but none is installed. You must install peer dependencies yourself.
                    npm WARN grunt-stylelint@0.11.1 requires a peer of stylelint@^10.0.0 but none is installed. You must install peer dependencies yourself.
                    
                    audited 3475 packages in 88.305s
                    found 28 vulnerabilities (1 low, 1 moderate, 26 high)
                      run `npm audit fix` to fix them, or `npm audit` for details
                    processing dependency changes for active modules with package.json files
                    
                    processing for module MMM-Carousel please wait
                    ----------------------------------
                    audited 859 packages in 16.958s
                    found 2 high severity vulnerabilities
                      run `npm audit fix` to fix them, or `npm audit` for details
                    processing complete for module MMM-Carousel
                    
                    processing for module MMM-PublicTransportHafas please wait
                    ----------------------------------
                    audited 41 packages in 2.814s
                    found 0 vulnerabilities
                    
                    processing complete for module MMM-PublicTransportHafas
                    
                    processing for module MMM-PublicTransportHafas please wait
                    ----------------------------------
                    audited 41 packages in 3.741s
                    found 0 vulnerabilities
                    
                    processing complete for module MMM-PublicTransportHafas
                    
                    processing for module MMM-PublicTransportHafas please wait
                    ----------------------------------
                    audited 41 packages in 3.333s
                    found 0 vulnerabilities
                    
                    processing complete for module MMM-PublicTransportHafas
                    
                    restoring custom.css
                    we stashed a set of files that appear changed from the latest repo versions. you should review them
                    Keine Stash-Einträge gefunden.
                    see installers/stashed_files for the list
                    
                    you can use git checkout stash@{0} -- filename to extract one file from the stash
                    
                    or git stash pop to restore them all
                    
                    WARNING..
                    WARNING.. either will overlay the file just installed by the update
                    WARNING..
                    

                    and the log:

                    
                    Upgrade started - Mi Okt 16 20:15:10 CEST 2019
                    user requested to force apply changes
                    doing test run = false
                    
                    saving custom.css
                    not english or locale not set, set git alias
                    alias egrep='egrep --color=auto'
                    alias fgrep='fgrep --color=auto'
                    alias git='LC_ALL=en_US.UTF-8 git'
                    alias grep='grep --color=auto'
                    alias ls='ls --color=auto'
                    remote name = origin
                    upgrading from version 2.9.0 to 2.9.0
                    fetching latest revisions
                    current branch = master
                    Auf Branch master
                    Ihr Branch ist auf demselben Stand wie 'origin/master'.
                    
                    Zum Commit vorgemerkte Änderungen:
                      (benutzen Sie "git reset HEAD <Datei>..." zum Entfernen aus der Staging-Area)
                    
                    	gelöscht:       css/custom.css
                    
                    Änderungen, die nicht zum Commit vorgemerkt sind:
                      (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)
                      (benutzen Sie "git checkout -- <Datei>...", um die Änderungen im Arbeitsverzeichnis zu verwerfen)
                    
                    	geändert:       package-lock.json
                    	geändert:       vendor/package-lock.json
                    
                    Unversionierte Dateien:
                      (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)
                    
                    	$
                    	%logfile
                    	core
                    	css/save_custom.css
                    	installers/dumpactivemodules.js
                    	installers/pm2_MagicMirror_new.json
                    	installers/stashed_files
                    	mm.sh
                    	nohup.out
                    
                    there are 2 local files that are different than the master repo
                    
                       package-lock.json
                       vendor/package-lock.json
                    
                    save/restore files selection = y
                    test merge result rc='' , if empty, no conflicts
                    executing merge, apply specified
                    merge result rc= 0
                     Already up to date.
                    processor architecture is armv7l
                    updating MagicMirror runtime, please wait
                    
                    > magicmirror@2.9.0 install /home/pi/MagicMirror
                    > cd vendor && npm install
                    
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    
                    audited 220 packages in 23.225s
                    found 5 vulnerabilities (4 low, 1 high)
                      run `npm audit fix` to fix them, or `npm audit` for details
                    
                    > magicmirror@2.9.0 postinstall /home/pi/MagicMirror
                    > sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts
                    
                    MagicMirror installation successful!
                    
                    > magicmirror@2.9.0 install-fonts /home/pi/MagicMirror
                    > cd fonts && npm install
                    
                    audited 1 package in 0.999s
                    found 0 vulnerabilities
                    
                    npm WARN acorn-jsx@5.0.2 requires a peer of acorn@^6.0.0 || ^7.0.0 but none is installed. You must install peer dependencies yourself.
                    npm WARN grunt-stylelint@0.11.1 requires a peer of stylelint@^10.0.0 but none is installed. You must install peer dependencies yourself.
                    
                    audited 3475 packages in 88.305s
                    found 28 vulnerabilities (1 low, 1 moderate, 26 high)
                      run `npm audit fix` to fix them, or `npm audit` for details
                    
                    processing dependency changes for active modules with package.json files
                    processing for module MMM-Carousel please wait
                    ----------------------------------
                    audited 859 packages in 16.958s
                    found 2 high severity vulnerabilities
                      run `npm audit fix` to fix them, or `npm audit` for details
                    processing complete for module MMM-Carousel
                    processing for module MMM-PublicTransportHafas please wait
                    ----------------------------------
                    audited 41 packages in 2.814s
                    found 0 vulnerabilities
                    
                    processing complete for module MMM-PublicTransportHafas
                    processing for module MMM-PublicTransportHafas please wait
                    ----------------------------------
                    audited 41 packages in 3.741s
                    found 0 vulnerabilities
                    
                    processing complete for module MMM-PublicTransportHafas
                    processing for module MMM-PublicTransportHafas please wait
                    ----------------------------------
                    audited 41 packages in 3.333s
                    found 0 vulnerabilities
                    
                    processing complete for module MMM-PublicTransportHafas
                    restoring custom.css
                    removing git alias
                    we stashed a set of files that appear changed from the latest repo versions. you should review them
                    Upgrade ended - Mi Okt 16 20:17:37 CEST 2019
                    
                    

                    –
                    cheers, bdream

                    S 1 Reply Last reply Oct 16, 2019, 6:41 PM Reply Quote 0
                    • S Offline
                      sdetweil @bdream
                      last edited by Oct 16, 2019, 6:41 PM

                      @bdream cool… don’t know why we got the german there… issued same command back to back, one to log, one to script…

                      log one came out in german
                      script one came out in english

                      fixed a bug, which should have said

                      any *-lock.json files do not need to be saved"
                      

                      that is all u had, so you would have selected n, instead of y

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 3
                      • 4
                      • 5
                      • 4 / 5
                      4 / 5
                      • First post
                        40/48
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy