Description of problem: When I try to build the mariadb .src.rpm (using "bm -l -b"), it fails with this error: [ERROR] ) libcrypt.so.1(GLIBC_2.2.5)(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.11)(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libm.so.6()(64bit) libm.so.6(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) librt.so.1()(64bit) librt.so.1(GLIBC_2.2.5)(64bit) libssl.so.1.0.0()(64bit) libstdc++.so.6()(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) libz.so.1()(64bit) devel(libaio(64bit)) devel(libcrypt(64bit)) devel(libcrypto(64bit)) devel(libdl(64bit)) devel(libm(64bit)) devel(libssl(64bit)) devel(libstdc++(64bit)) devel(libz(64bit)) Obsoletes: mariadb-embedded-devel < 5.5.25-1.mga3 lib64mariadb-embedded-devel < 5.5.25-1.mga3 Processing files: mariadb-debug-5.5.25-1.mga3.x86_64 Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/shlomif/Download/unpack/Mageia/mariadb/BUILDROOT/mariadb-5.5.25-1.mga3.x86_64 error: Installed (but unpackaged) file(s) found: /usr/lib64/mysql/plugin/auth_pam.so RPM build errors: Installed (but unpackaged) file(s) found: /usr/lib64/mysql/plugin/auth_pam.so error: failed! shlomif[rpms]:$mageia/mariadb$ [/ERROR] It doesn't fail on the build system because the relevant pam-related packages are not installed, and so they are not detected and built. Several solutions: 1. Pass the appropriate ./configure|CMake flag to disable building auth_pam.so. 2. Have a BuildConflict (does such an animal exist?) on the relevant pam modules. 3. Always build the pam module (which may be a good idea). Regards, -- Shlomi Fish
Assignee: bugsquad => alien
cauldron now has 5.5.25 with all the additional patches mga2 had auth_pam is in the file listings, iinm
(In reply to comment #1) > cauldron now has 5.5.25 with all the additional patches mga2 had > > > auth_pam is in the file listings, iinm shlomif[rpms]:$mageia/mariadb$ svn info SPECS/mariadb.spec Path: SPECS/mariadb.spec Name: mariadb.spec Working Copy Root Path: /home/shlomif/Download/unpack/Mageia/mariadb URL: svn+ssh://svn.mageia.org/svn/packages/cauldron/mariadb/current/SPECS/mariadb.spec Repository Root: svn+ssh://svn.mageia.org/svn/packages Repository UUID: 01bf705a-734c-4999-978a-dc8ab10ec44d Revision: 279877 Node Kind: file Schedule: normal Last Changed Author: alien Last Changed Rev: 279279 Last Changed Date: 2012-08-06 14:46:36 +0300 (Mon, 06 Aug 2012) Text Last Updated: 2012-08-06 17:50:02 +0300 (Mon, 06 Aug 2012) Checksum: 33accc975830adebedaae99487b97b07185fa429 shlomif[rpms]:$mageia/mariadb$ grep pam SPECS/mariadb.spec shlomif[rpms]:$mageia/mariadb$ grep pam SPECS/mariadb.spec | wc -l 0 So it's not there.
it seems you are correct... i forgot pam-devel build requires, so it wasn't built.. :-( i'll update cauldron for this.
(In reply to comment #3) > it seems you are correct... i forgot pam-devel build requires, so it wasn't > built.. :-( > > i'll update cauldron for this. Thanks for the fix. Confirmed to work in latest Cauldron so resolving as FIXED.
Status: NEW => RESOLVEDResolution: (none) => FIXED
can i ask why you'd want to rebuild it? (is there something you want or is wrong with it?) and btw: if you want to rebuild rpms, you can better do this in a chroot so that only the buildrequires are fetched...
Hi AL13N, (In reply to comment #5) > can i ask why you'd want to rebuild it? (is there something you want or is > wrong with it?) I wanted to get the up-to-date version before it hit the mirrors, due to RT's lack of compatibility with old versions of MariaDB ("via" considered a reserved word/etc.). > and btw: if you want to rebuild rpms, you can better do this in > a chroot so that only the buildrequires are fetched... Thanks for the tip. Setting up a chroot is time-consuming, and building RPMs in the normal file system can detect many errors such as this one. Regards, -- Shlomi Fish
true, but they aren't really errors... rpms are built using buildsystem, and they also use chroots, besides, using chroot to build rpm can help find missing buildrequires. also, setting up a chroot is easy: # mkdir /path/to/chroot # urpmi.addmedia --urpmi-root /path/to/chroot --distrib "http://mirror/mageia/distrib/2/x86_64" # urpmi --urpmi-root /path/to/chroot --no-suggests basesystem locales-en urpmi # chroot /path/to/chroot
Hi AL13N, (In reply to comment #7) > true, but they aren't really errors... rpms are built using buildsystem, and > they also use chroots, besides, using chroot to build rpm can help find missing > buildrequires. > > also, setting up a chroot is easy: > > # mkdir /path/to/chroot > # urpmi.addmedia --urpmi-root /path/to/chroot --distrib > "http://mirror/mageia/distrib/2/x86_64" > # urpmi --urpmi-root /path/to/chroot --no-suggests basesystem locales-en urpmi > # chroot /path/to/chroot It is easy, but it will also be time consuming for me because my Internet connection is slow - only 10 Mbit/s at most (which is heaven compared to my old Internet connection), and your chroot did not catch this bug, so the kilometrage can vary.
haha :-) but with my urpmi-proxy, i can have several chroots without any internet usage :-) and also, strictly said, it's not a bug :-) . allthough it can be improved.