Two questions :
1) separating build means giving different RPM_DIST_DIR for each build ?
2) Is there a way of listing rpms from mock chroot filesystem ?
I tested it below command to see the list of installed rpms for example
sudo chroot /var/lib/mock/blabla/root rpm -qa
but it gave this error.
rpmdb: /var/lib/rpm/Packages: unsupported hash version: 9
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
_lvnd_
(^_^)
On Mon, May 9, 2011 at 10:00 PM, Douglas Hubler <[email protected]> wrote:
> On Mon, May 9, 2011 at 2:53 PM, Levend Sayar <[email protected]> wrote:
>> After
>>
>> make repo-chroot-init
>>
>> you get a fresh var/lib/mock/centos-5-x86_64/root.
>>
>> On my RPM_DIST_DIR folder there was a previous sipxportlib-devel-4.4.0
>> rpm. You have to delete that rpm, then createrepo,
>> If there are both sipxportlib-devel-4.4.0.rpm and
>> sipxportlib-devel-0.0.4.5.2.rpm on repo, mock installs 4.4.0 version.
>> Therefore you can not get
>> OsLogger.h on mock root folder.
>
> Right, you cannot mix the build output from 4.4.0 with the build
> output from 0.0.4.5.2. Best you keep the build output for each
> version in separate directories.
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
