Discover Centmin Mod today
Register Now

Upgrade Problem with option <23><3> -- Update Centmin Mod Newer Branch

Discussion in 'Beta release code' started by jscott, Apr 9, 2016.

  1. jscott

    jscott Member

    94
    14
    8
    Aug 13, 2015
    Ratings:
    +31
    Local Time:
    12:02 AM
    I am running 123.08stable and want to test running .09 to test http/2 and LetsEncrypt.

    I ran:
    Code:
    23). Update Centmin Mod Code Base
    
    1). Setup Centmin Mod Github Environment
    
    3). Update Centmin Mod Newer Branch
    
    And I get

    Code:
    Update Centmin Mod to newer branch via git
    You need to input the name of the branch
    List of current remote branches by descending date order
    
    fatal: Unable to read current working directory: No such file or directory
    
    Enter the branch name you want to switch to i.e. 123.08beta03 : 123.09beta01le5
    
    fatal: Unable to read current working directory: No such file or directory
    123.09beta01le5 branch does not exists
    try again...
    
    --------------------------------------------------------
            Centmin Mod Updater Sub-Menu
    --------------------------------------------------------
    1). Setup Centmin Mod Github Environment
    2). Update Centmin Mod Current Branch
    3). Update Centmin Mod Newer Branch
    4). Back to Main menu
    --------------------------------------------------------
    Enter option [ 1 - 4 ]
    
    This installation was built this morning from the one line install

    -John
     
  2. eva2000

    eva2000 Administrator Staff Member

    30,956
    6,917
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,418
    Local Time:
    3:02 PM
    Nginx 1.13.x
    MariaDB 5.5
    problem is your server isn't able to communicate with github.com i think
    normally you'd see
    Code (Text):
    --------------------------------------------------------
    Enter option [ 1 - 24 ] 23
    --------------------------------------------------------
    
    --------------------------------------------------------
            Centmin Mod Updater Sub-Menu             
    --------------------------------------------------------
    1). Setup Centmin Mod Github Environment
    2). Update Centmin Mod Current Branch
    3). Update Centmin Mod Newer Branch
    4). Exit
    --------------------------------------------------------
    Enter option [ 1 - 4 ] 3
    --------------------------------------------------------
    
    fetching latest branch list...
    
    Update Centmin Mod to newer branch via git
    You need to input the name of the branch
    List of current remote branches by descending date order
    
    123.09beta01
    123.08stable
    123.09beta01le5
    123.09beta01le4
    123.09beta01le3
    
    Enter the branch name you want to switch to i.e. 123.09beta01 : 


    You can manually switch with git commands outlined at Upgrade Centmin Mod - CentminMod.com LEMP Nginx web stack for CentOS just change the branch you want.

    The below command changes into /usr/local/src and removes existing centminmod directory, git clones new directory and changes into that directory and changes to 123.09beta01 branch, change to 123.09beta01le5 if you want that branch
    Code (Text):
    cd /usr/local/src
    rm -rf centminmod
    git clone https://github.com/centminmod/centminmod.git centminmod
    cd centminmod
    git checkout -f 123.09beta01


    FYI, 123.09beta01le5 letsencrypt branch hasn't been updated in a while or tested so could be broken as letsencrypt official client has alot of changes since back then. I'll only be able to work on the letsencrypt branch in my free time, so any testing and feedback and bug reports are welcomed :)
     
  3. jscott

    jscott Member

    94
    14
    8
    Aug 13, 2015
    Ratings:
    +31
    Local Time:
    12:02 AM
    I will take a look at this.
    I know other installs outside of centminmod are working ok with github, but I will look more into this.

    It looks like 123.09beta01 is the latest... Correct?
    I thought there was a 123.09beta011, but I guess not.

    Thanks
    -John