RPM Community Forums

Mailing List Message of <rpm-users>

Fwd: error: cannot open Packages database in /var/lib/rpm

From: Jeff Johnson <n3npq@mac.com>
Date: Thu 28 May 2009 - 13:28:10 CEST
Message-id: <E5F500DC-1168-4258-AA30-D0C741EAFC60@mac.com>


Begin forwarded message:

> From: Jeff Johnson <n3npq@mac.com>
> Date: May 28, 2009 7:17:46 AM EDT
> To: spam.spam.spam.spam@free.fr
> Subject: Re: error: cannot open Packages database in /var/lib/rpm
>
>
> On May 28, 2009, at 4:35 AM, spam.spam.spam.spam@free.fr wrote:
>
>>
>> Ok... So I need libpcre or I can use --nodeps (read the dependances  
>> is very
>> important! Maybe I should install libpcre).
>> I am on Slackware 12.2 and pcre-7.7 in installed. But I said to the  
>> configure
>> script : --without-pcre.
>> Hum, It's strange... I say "--without-pcre" and it try to use it  
>> during the
>> install of a RPM package.
>>
>> Now watch what rpm say when I try with --nodeps :
>>
>> #rpm --nodeps --macros /lib/rpm/macros -i  
>> 8Kingdoms-1.1.0-6.fc9.i386.rpm
>> warning: 8Kingdoms-1.1.0-6.fc9.i386.rpm: Header V3 DSA signature:  
>> NOKEY, key ID
>> 4ebfc273
>> error: unpacking of archive failed: cpio: Bad magic
>>
>> I am sure I need to install CPIO now...
>> Oh my god, so much dependencies for RPM, my chroot system will be  
>> big...
>>
>
> In order to use *RE's within *.rpm tag content, a *RE dialect needed  
> to be chosen.
>
> Having both POSIX and PCRE within *.rpm packages would add an  
> intolerable
> "Have it your own way!" set of implementations that cannot be  
> supported.
>
> Consider what happens if a *.rpm included tags with PCRE patterns, and
> the user has decided to build using --without-pcre. That package  
> cannot
> be installed.
>
> The *RE patterns are already in use to express platform affinities,
> install policies like "Prefer i586 over i486 packages on i686  
> platforms."
>
> So PCRE was chosen as a *RE dialect for several reasons, including  
> that
> PCRE is a superset of POSIX *RE patterns, and PCRE is distributed
> with RPM sources. The INSTALL document very clearly says:
>
> 	...
> 	PCRE            mandatory 7.0     7.9     http://www.pcre.org/
> 	..
>
> mandatory means exactly that: MANDATORY.
>
> PCRE internal, (and Berkeley DB internal, the recommended means of
> using Berkeley DB for many years), add no dependencies to RPM  
> whatsoever.
>
> You (or Slackware) are choosing the dependency complexity.
>
>> Well, If I understand, I need these two :
>> http://www.pcre.org/
>> http://www.gnu.org/software/cpio/
>>
>
> There is no need for cpio.
>
> 73 de Jeff
Received on Thu May 28 13:28:41 2009
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.