On Aug 23, 2007, at 11:07 AM, Jakub Bogusz wrote:
On Thu, Aug 23, 2007 at 08:42:04AM -0400, Jeff Johnson wrote:
In my case database wasn't open - rpm finished its work after db4.6
upgrade, and failed when I ran it again to upgrade some other package.
I didn't use poldek during all those operat
On Thu, Aug 23, 2007 at 08:42:04AM -0400, Jeff Johnson wrote:
> Begin forwarded message:
> > On Aug 23, 2007, at 7:19 AM, Patryk Zawadzki wrote:
> >
> >> On 8/23/07, Jakub Bogusz <[EMAIL PROTECTED]> wrote:
> >>> On Thu, Aug 23, 2007 at 11:55:05AM +0200, Adam Gołębiowski wrote:
> rpm --rebuildd
Begin forwarded message:
>
> On Aug 23, 2007, at 7:19 AM, Patryk Zawadzki wrote:
>
>> On 8/23/07, Jakub Bogusz <[EMAIL PROTECTED]> wrote:
>>> On Thu, Aug 23, 2007 at 11:55:05AM +0200, Adam Gołębiowski wrote:
rpm --rebuilddb seems to fix this issue (I didn't try removing
__db*).
>>> T
On 8/23/07, Jakub Bogusz <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 23, 2007 at 11:55:05AM +0200, Adam Gołębiowski wrote:
> > rpm --rebuilddb seems to fix this issue (I didn't try removing __db*).
> The same for me, rm __db* was sufficient.
Is it possible to remove it by a trigger? Triggers are run
On Thu, Aug 23, 2007 at 11:55:05AM +0200, Adam Gołębiowski wrote:
> This happened to me twice today:
> Executing rpm --upgrade -vh --root / --noorder...
> pmdb: munmap: Invalid argument
> rpmdb: munmap: Invalid argument
> rpmdb: munmap: Invalid argument
> rpmdb: munmap: Invalid argument
> rpmdb: u
On 8/23/07, Adam Gołębiowski <[EMAIL PROTECTED]> wrote:
> This happened to me twice today:
Happened to me yesterday.
> rpm --rebuilddb seems to fix this issue (I didn't try removing __db*).
> Perhaps some trigger in db-4.6.19? Is it possible to do `rpm --rebuilddb' in
> %post?
rebuilddb resulte
This happened to me twice today:
Installing set #9
Processing dependencies...
db4.6-4.6.18-1.i686 obsoleted by db4.6-4.6.19-1.i686
There are 1 package to install, 1 to remove:
I db4.6-4.6.19-1.i686
R db4.6-4.6.18-1.i686
Need to get 417.5KB of archives (417.5KB to download).
A
