>>>> "AL" == Alex Lancaster writes:
>>>> "TC" == Tom \"spot\" Callaway
TC> On Wed, 2008-04-23 at 02:56 -0700, Alex Lancaster wrote:
>> I agree, wait for F-9. Then we can put it through
>> updates-testing, have time to push dependent packages that might
>> need rebuilding, including (but probably not limited to) rpy.
>> Meanwhile we could push versions for F-7 & F-8 to updates-testing
>> to shake out potential problems. Then push them all to stable
>> after F-9 is released.
TC> Ehhh, i don't want to break the upgrade path. We'll just sit on
TC> this until after F-9.
AL> I just noticed that some packages fail to rebuild with R 2.7.0,
AL> the build.log has the following:
AL> checking for unpackaged file(s): /usr/lib/rpm/check-files
AL> /var/tmp/R-zoo-1.5-3.fc10-root-mockbuild error: Installed (but
AL> unpackaged) file(s) found: /usr/share/R/library/zoo/NEWS RPM build
AL> errors: Installed (but unpackaged) file(s) found:
AL> Does 2.7.0 somehow attempt to compile/provide a NEWS file even if
AL> the actual package does not?
Actually looking at it a bit closer it seems that R 2.7.0 is a bit
smarter about installing the NEWS file if it's present, see:
for more details. This might affect a few packages that don't
explicitly include NEWS in their %files list. If this is so, it would
probably be useful if the sample spec files in the R packaging
were also updated accordingly, as many people use those as templates
to create new R packages.