From: Sergey Kulakov <sergey65@mail.ru> To: community@altlinux.ru Subject: [Comm] проблемы при обновлении Date: Sat, 22 Jan 2005 18:44:25 +0300 Message-ID: <41F274D9.4070902@mail.ru> (raw) сомраст 2.3 обновленный до сизифа Подскажите ПЛЗ что сделать можно? При обновлении : Во время установки пакета kdeaddons-konqueror-3.3.2-alt1: rpmdb: PANIC: Invalid argument error: db4 error(-30978) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->sync: DB_RUNRECOVERY: Fatal error, run ....... Во время установки пакета kdenetwork-kwifimanager-3.3.2-alt2: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery .......... Во время установки пакета kdepim-kmail-3.3.2-alt1: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery ......... Во время установки пакета kdepim-kmailcvt-3.3.2-alt1: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery .......... Во время установки пакета kdepim-korn-3.3.2-alt1: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery ........... Во время установки пакета vim-X11-gtk2-6.3.057-alt1: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery .......... Во время установки пакета kdeaddons-vim-3.3.2-alt1: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery ............ Во время установки пакета vim-X11-6.3.057-alt1: rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery .... Во время установки пакета vim-common-6.3.057-alt1: warning: /etc/vim/gvimrc created as /etc/vim/gvimrc.rpmnew warning: /etc/vim/vimrc created as /etc/vim/vimrc.rpmnew rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery ........... -- С Уважением, e-mail: sergey65@mail.ru Сергей Кулаков. http://www.arista.ru
next reply other threads:[~2005-01-22 15:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-22 15:44 Sergey Kulakov [this message] 2005-01-23 12:30 ` Alex Yustasov 2005-01-23 12:49 ` [Comm] " Michael Shigorin 2005-01-23 12:58 ` [Comm] " Alexey Borovskoy 2005-01-23 15:09 ` Sergey Kulakov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=41F274D9.4070902@mail.ru \ --to=sergey65@mail.ru \ --cc=community@altlinux.ru \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git