"reading files list for package 'inkscape': Input/output error" while trying to install packages [closed] - apt-get

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
It doesn't matter what I try to install using my package manager(sudo apt-get install whatever), I always get this error.
dpkg: unrecoverable fatal error, aborting:
reading files list for package 'inkscape': Input/output error
E: Sub-process /usr/bin/dpkg returned an error code (2)
I have researched and have tried to rebuild my dpkg status file, and I have also tried to revert to an older version, but it either hasn't worked or I am doing it wrong.
Also, when I try to run the command "sudo apt-get update", I get this error.
The problem started when I lost my internet connection while downloading monodevelop. Any help is greatly appreciated.

I figured out the answer, so I will post it here in case anybody else has the same problem in the future.
NOTE: After this fix, apt-get no longer installs dependencies for me automatically without using the -f flag.
Go into the /var/lib/dpkg directory
Make a backup of the "status" file
Open the status file as root and find the package that causes the error.
In this case, its "PACKAGE: inkscape".
Delete all the text until the next PACKAGE: declaration in the file.

Related

How can I tell a debian package to forget about a file (such that the file doesn't get deleted during a purge or remove)? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
A debian package I made overwrote files belonging to other packages (using --force-overwrite option). I realized this was bad, but after deleting these files from the package, building and reinstalling, it'll delete those files since it think's my package owns those files and no longer needs them.
I need dpkg to forget my package ever knew about those files, such that I can remove/purge/install and without it ever thinking about those files again.
Note that this package is only meant to be deployed on systems I control, not distributed to clients, so tinkering with already installed packages is acceptable, so long as I can get this back to a non-messed up state.
Couldn't find an answer on stackoverflow or here, appreciate any help or links to similar questions I missed.
Found that dpkg stores a list of each installed package's files here:
/var/lib/dpkg/info/mydpkg.list
Appears to be a list of every directory and file installed by the package, eg
/etc/udev
/etc/udev/rules.d
/etc/udev/rules.d/95-serial485-pi3.rules
/etc/udev/rules.d/97-serial485-pi4.rules
Fix: sudo vim /var/lib/dpkg/info/mydpkg.list and delete lines of files I want my package to forget about, therefore not trying to delete when uninstalling (or when installing a new version of the package that doesn't have those files anymore.) Unclear on if it's necessary to delete the lines referencing parent directories (eg /etc/udev and /etc/udev/rules.d above).
Bonus: I found this by using strace on the command that lists these files, finding out where it gets its info from:
strace dpkg-query -L mydpkg
Taken from here:
https://unix.stackexchange.com/questions/200171/where-does-dpkg-l-gather-its-information
We can use some commands that help us to keep the package dependency and remove the package.
Remove the package without removing the dependency.
sudo dpkg -r --force-depends <package_name>
Remove the package including the configuration file and without removing the dependency.
sudo dpkg -P --force-depends <package_name>
I highly don't recommend this thing because sometimes dependency may create an issue in the future.
I always prefer to uninstall all the dependency when I uninstall the package.
If your package is broken then you can use the following command to resolve an issue.
To fix the broken packages
sudo apt install -f
I have answered this question based on this article.

Amavis is not installed - CentOS [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Getting this error when installing Modoboa via this link https://www.linuxbabe.com/mail-server/email-server-centos-7-modoboa
Installing amavis
Package amavisd-new is obsoleted by amavis, trying to install amavis-2.12.0-10.el7.noarch instead
Package lz4-1.7.5-3.el7.x86_64 already installed and latest version
Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /usr/lib/systemd/system/maria
db.service.
Redirecting to /bin/systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Redirecting to /bin/systemctl start mariadb.service
Amavis is not installed
It would be very helpful if some can help
You need to do 2 things
go to folder where you cloned modoboa git repo and run:
sed -i 's/amavisd-new/amavis/g' ./modoboa-installer/modoboa_installer/scripts/amavis.py
Script was searching for package amavisd-new but package naming was changed for amavis in Centos
Modoboa installer don't have yet files for amavis ver 2.12 but you can copy older sql template
cp modoboa-installer/modoboa_installer/scripts/files/amavis/amavis_mysql_2.11.X.sql modoboa-installer/modoboa_installer/scripts/files/amavis/amavis_mysql_2.12.X.sql
if you want to use postgresql do the same for postgres sql file.
and after that re-run installer should work fine :)

Where can I download mysql jdbc jar from? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I installed and tried to use jasper report studio. The first brick wall you hit when you try to create a datasource for your reports is
java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
The forums say I need to install a jar on the classpath. I have no idea how to do this, so the first hurdle is how to get the jar. The only place I can find is this:
http://dev.mysql.com/downloads/connector/j/
but this unfortunately gives you an msi installer, not a jar. I don't want to install stuff, just get the jar.
I have mysql DB installed, had have trawled through the install dir in program files, but can't find the jar.
Anyone know the official (not malware site) way to get hold of the mysql jar? It seems bizarre that its so hard to find.
I have windows 8 64 bit and mysql 5.6.
Go to http://dev.mysql.com/downloads/connector/j and with in the dropdown select "Platform Independent" then it will show you the options to download tar.gz file or zip file.
Download zip file and extract it, with in that you will find mysql-connector-XXX.jar file
If you are using maven then you can add the dependency from the link http://mvnrepository.com/artifact/mysql/mysql-connector-java
Select the version you want to use and add the dependency in your pom.xml file
If you have WL server installed, pick it up from under
\Oracle\Middleware\wlserver_10.3\server\lib\mysql-connector-java-commercial-5.1.17-bin.jar
Otherwise, download it from:
http://www.java2s.com/Code/JarDownload/mysql/mysql-connector-java-5.1.17-bin.jar.zip
Here's a one-liner using Maven:
mvn dependency:get -Dartifact=mysql:mysql-connector-java:5.1.38
Then, with default settings, it's available in:
$HOME/.m2/repository/mysql/mysql-connector-java/5.1.38/mysql-connector-java-5.1.38.jar
Just replace the version number if you need a different one.

Fedora 17 yum update: could not finish packages updating [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
After processing dependencies "yum update" produce errors:
--> Finished Dependency Resolution
Error: Package: perl-CPAN-1.9600.01-215.fc17.noarch (updates)
Requires: perl = 4:5.14.2-215.fc17
Installed: 4:perl-5.14.3-202.fc16.i686 (#updates/16)
perl = 4:5.14.3-202.fc16
Available: 4:perl-5.14.2-211.fc17.i686 (fedora)
perl = 4:5.14.2-211.fc17
Available: 4:perl-5.14.2-215.fc17.i686 (updates)
perl = 4:5.14.2-215.fc17
Error: Package: 1:perl-IPC-Cmd-0.70-215.fc17.noarch (updates)
Requires: perl = 4:5.14.2-215.fc17
Installed: 4:perl-5.14.3-202.fc16.i686 (#updates/16)
perl = 4:5.14.3-202.fc16
Available: 4:perl-5.14.2-211.fc17.i686 (fedora)
perl = 4:5.14.2-211.fc17
Available: 4:perl-5.14.2-215.fc17.i686 (updates)
perl = 4:5.14.2-215.fc17
There are plenty errors of that type mostly concerning perl.
But required version of perl is installed:
yum install perl-5.14.2-215.fc17.i686
Loaded plugins: auto-update-debuginfo, presto, refresh-packagekit
Package matching 4:perl-5.14.2-215.fc17.i686 already installed. Checking for update.
Nothing to do
Skip broken option does not help.
It seems that upgrading from version 16 to 17 is stuck at the middle of process
I had exactly the same problem after the upgrade from Fedora 16 to Fedora 17 (this upgrade sucks). It seems the perl-5.14.2-XXX.fc17 package does not show up in the repo update list because the version already installes (perl-5.14.3.fc16) is 'newer'.
Here is what I've just done to solve the problem.
check which version you have already installed on you system:
perl-5.14.3.fc16
download the rpms for the newer version. In my case (you may need other libraries):
perl-5.14.2-211.fc17.x86_64.rpm
perl-libs-5.14.2-211.fc17.x86_64.rpm
perl-Carp-1.20-211.fc17.noarch.rpm
perl-Digest-MD5-2.51-211.fc17.x86_64.rpm
perl-Digest-1.17-2.fc17.noarch.rpm
perl-macros-5.14.2-211.fc17.x86_64.rpm
update allowing older packages (superuser):
# rpm -U --oldpackage perl-.rpm*
Go back to yum update to finish updating missing libraries and packages.
If you still have some libraries dependence issues that doesn't allow you to to this you may have to remove thos libraries before, but normally it show go smoothly.
I hope this helps.
I've solved it by removing problem packages and installing them again after update finished.

Completely remove and reinstall mysql [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I managed to bork my installation of it while trying to uninstall it. I installed via Muon (Kubuntu), and attempted uninstallation the same way.
I tried apt-get install/remove (on both mysqlserver and mysql), then tried manually removing files, but it just doesn't work. Somewhere it's determining not to regenerate its configs and not reinstall like a fresh install would.
How do i just get rid of everything mysql-related? I'd like to start fresh.
apt-get purge PACKAGENAME should completely remove a package including its configurations. Maybe this works better.
remove leaves behind configuration files. You need to use purge instead. (purge works on both apt-get(8) and dpkg(8).)
I had to copy a default mysql.cnf (obtained via googling) into the /etc/mysql directory. It created debian versions of the config while using "apt-get install mysql-server-5.1", so i'm assuming the installation i was trying to do was just bad. Should have gone rpm i guess.
However using purge DID remove a few other files i didn't know about, so it did help. +1