You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am still very new to GitHub, so I do heavily apologize if this was not the correct way to go about submitting an issue when it comes to this kind of thing.
I wanted to reference this line here on your upgrade script:
I had a plethora of python nonsense spit out at me when I tried to upgrade using CP's documentation on upgrading from the website with the one line of code. At the very end of the 45 lines of errors was this:
TypeError: canonicalize_version() got an unexpected keyword argument 'strip_trailing_zero'.
Naturally, I opened the file to see why I was given the TypeError... nothing was wrong.
Turns out this is an error I believe within setuptools? Not 100% sure. However, there are multiple PRs on GitHub with similar if not same exact issues and errors that I had. I did some testing of my own and found that if you get rid of the fix you implemented "## fix for pip issue on ubuntu 22" and change the packages you install to something like this:
DEBIAN_FRONTEND=noninteractive apt-get install -y build-essential libssl-dev libffi-dev python3-dev
DEBIAN_FRONTEND=noninteractive apt-get install -y python3-venv
DEBIAN_FRONTEND=noninteractive add-apt-repository universe -y
DEBIAN_FRONTEND=noninteractive apt-get update -y
DEBIAN_FRONTEND=noninteractive apt-get install -y python3-pip
and then go down and replace each of your lines that have:
pip install --upgrade setuptools packaging
with this:
pip install --upgrade setuptools>=75 packaging>=25
the 45 lines of errors I received will go away and the upgrade script will be able to run successfully.
That's the very last part of the script that I cannot get to work and I cannot find anywhere on Google except for 10 year old posts on the forum when that litespeed API version was released.
The text was updated successfully, but these errors were encountered:
Hello,
I am still very new to GitHub, so I do heavily apologize if this was not the correct way to go about submitting an issue when it comes to this kind of thing.
I wanted to reference this line here on your upgrade script:
cyberpanel/cyberpanel_upgrade.sh
Line 551 in 6f28d39
I had a plethora of python nonsense spit out at me when I tried to upgrade using CP's documentation on upgrading from the website with the one line of code. At the very end of the 45 lines of errors was this:
TypeError: canonicalize_version() got an unexpected keyword argument 'strip_trailing_zero'.
Naturally, I opened the file to see why I was given the TypeError... nothing was wrong.
Turns out this is an error I believe within setuptools? Not 100% sure. However, there are multiple PRs on GitHub with similar if not same exact issues and errors that I had. I did some testing of my own and found that if you get rid of the fix you implemented "## fix for pip issue on ubuntu 22" and change the packages you install to something like this:
DEBIAN_FRONTEND=noninteractive apt-get install -y build-essential libssl-dev libffi-dev python3-dev
DEBIAN_FRONTEND=noninteractive apt-get install -y python3-venv
DEBIAN_FRONTEND=noninteractive add-apt-repository universe -y
DEBIAN_FRONTEND=noninteractive apt-get update -y
DEBIAN_FRONTEND=noninteractive apt-get install -y python3-pip
and then go down and replace each of your lines that have:
pip install --upgrade setuptools packaging
with this:
pip install --upgrade setuptools>=75 packaging>=25
the 45 lines of errors I received will go away and the upgrade script will be able to run successfully.
Also, the very last thing that I am very confused about is:
wget https://cyberpanel.sh/www.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz
just returns a 500 error. Even doing http:// and even doing http://www.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz
That's the very last part of the script that I cannot get to work and I cannot find anywhere on Google except for 10 year old posts on the forum when that litespeed API version was released.
The text was updated successfully, but these errors were encountered: