http://qa.mandrakesoft.com/show_bug.cgi?id=6313
------- Additional Comments From [EMAIL PROTECTED] 2003-10-11 16:40 ------- OK, so the reason by that one BuildRequires wasn't included in the rpm headers was because the src.rpm package was built on Gwenole's amd64 system: gauss.mandrakesoft.com. It would be an option to install the src.rpm file and then run urpmi against the .spec file, also with the required options (--with plf) when required. Issue is, rpm can't determin the BuildRequires from a .spec file alone. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: When a package has conditional BuildRequires (like ImageMagick) these are not picked up when querying the package: Normal: [EMAIL PROTECTED] i586]$ rpm -qpR /mirrors/cooker/SRPMS/ImageMagick-5.5.7.12-1mdk.src.rpm | wc -l 15 --with plf: [EMAIL PROTECTED] i586]$ rpm -qpR /mirrors/cooker/SRPMS/ImageMagick-5.5.7.12-1mdk.src.rpm --with plf | wc -l 15 [EMAIL PROTECTED] i586]$ rpm --with plf -qpR /mirrors/cooker/SRPMS/ImageMagick-5.5.7.12-1mdk.src.rpm | wc -l 15 [EMAIL PROTECTED] i586]$ rpm -qpR --with plf /mirrors/cooker/SRPMS/ImageMagick-5.5.7.12-1mdk.src.rpm | wc -l 15 >From the ImageMagick.spec file: %if %build_plf %define enablelzw 1 %define enablejasper 1 %define enablefpx 1 %endif %if %{enablefpx} BuildRequires: libfpx1-devel %endif %if %{enablejasper} BuildRequires: libjasper-devel %endif So, one would expect to see a number larger than 15 when queried with the --with plf option.
