http://bugzilla.novell.com/show_bug.cgi?id=540523 Summary: kernel-vanilla (like MANY packages) build doesn't use %_sourcedir RPM macro as required Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth@novell.com ReportedBy: suse@tlinx.org QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 trying to build kernel-vanilla from spec. Doesn't work **on my system***. in my /etc/rpm/macros, I have: %_sourcedir %{_topdir}/SOURCES/%{name}-%{version} ---- So sources from different products-releases go into different dirs in Sources dir -- just like they do in 'build' dir when building Most products this works fine -- but ones that "assume" they know where to get other installed sources (like presuming the same dir), fail. This is a bug -- they should not be touching other installed sources directly, but should go through the %_sourcedir macro as consistent with the RPM spec. As a result, any product (and there are a few) that presume the default layout, will break -- because they are not following the standards. They need to be updated -- AS their rpms are "touched" for other reasons (or when a customer/user) reports a problem) to use the standard macro for determining the other sources' locations. Reproducible: Always Steps to Reproduce: 1. Setup sources for each rpm to be stored in their own dir, just as is done with 2. build using system-local-customizable /etc/macros file set to 3. %_sourcedir %{_topdir}/SOURCES/%{name}-%{version} Actual Results: standard rpms fail to build because they don't pay attention to *valid* local user defined macros. Expected Results: expect released rpm sources to pay attention to the standard rpm macros and expand and use them as appropriate and not take "shortcuts" and circumvent standards. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.