Hello,
Since over one week, I have been consistently searching for a solution to my mysql installation errors. I surfed many sites on google to get rid of the issue. Now google gives me all the same results, I tested many of those solutions provided by... Now I am pulling hair
I am under ubuntu16.04 pc. Normally it was installed earlier. Then I faced incompatibility issues between mysql version and the softwares. So, removed mysql with below commands earlier.
mv: cannot move '/etc/mysql/my.cnf' to '/etc/mysql/my.cnf.dpkg-backup': Operation not permitted
dpkg: error processing archive /var/cache/apt/archives/mysql-common_5.7.25-0ubuntu0.16.04.2_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/mysql-common_5.7.25-0ubuntu0.16.04.2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
kernel version:
root@pc:~# uname -r
4.9.148-xxxx-std-ipv6-64
If I can not solve this issue, I will have to reinstall ubuntu 16.04 from scratch.
I'd appreciate your recommendation
Hello Neo,
Normally you are right... Does it make any difference with/without sudo when I am root?
By the way, reinstallation is in progress.
But I'd like to know if you have any idea to fix it so that I'd keep your thought in my pocket for future isssues...
Installation progress
The installation request has been registered.
Copying system ( 4 / 8 )
Thanks Neo,
I tried sudoedit , gedit etc but none of them worked.
It was saying read only . Also rm command was not responding..
I suppose after upgrading from ubuntu14.04 to 16.04, I broke my repositories and made some non-returnable changes so that the system could not have repaired it. I am not a professeur on linux You all may guess what could be the solution.
Before setting with chattr , the OP should probably list first, for example:
lsattr example.conf
The OP said he does not have any experience in Linux, so before going around changing file attributes, he should list them first before he makes even more mistakes.
My first guess is the the file system has been mounted read-only.