Bug 233389
Summary: | Dovecot will not update with yum | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Skip Palin <spalin> |
Component: | dovecot | Assignee: | Tomas Janousek <tjanouse> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | tss, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-23 21:51:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Skip Palin
2007-03-22 00:24:32 UTC
I'm unable to reproduce this. I bet this is some multilib/yum issue. When I tried to reproduce it, I had to install mysql to satisfy dovecot dep. Mysql depended on a newer version of ncurses, but yum decided to update only on x86_64. This resulted in a conflict. I have no idea how this may happen with dovecot though, it should not be multilib at all. Please check what architecture is your currently installed dovecot and try to rpm -Uvh the new one manully. what version of yum is this? (In reply to comment #2) > what version of yum is this? 3.1.4 OK so after trying: rpm -Uvh /var/cache/yum/development/packages/dovecot-1.0-7.rc27.fc7.x86_64.rpm error: can't create transaction lock on /var/lib/rpm/__db.000 i did a: ]$ rpm -qa | grep dovecot dovecot-1.0-3.rc22.fc7 dovecot-1.0-3.rc22.fc7 Tried to remove it and get: rpm -e dovecot-1.0-3.rc22.fc7 error: "dovecot-1.0-3.rc22.fc7" specifies multiple packages Seems like you have both i386 and x86_64 version of the package installed. I suppose you must have installed these with --nodeps or something, because these two collide in at least the /usr/sbin/dovecot binary. This package is not a multilib one, so this is a conflicting setup even before doing any update at all. OK I screed up, when I did a update I used: yum -y --skip-broken update Sorry to waste your time. |