On 26 July 2012 23:58, Thomas Backlund <[email protected]> wrote: >> I dont know if this is a fallout of usrmove or the recent >> rpm-mageia-setup cleanup or something else, but I now see >> this in kernel buildlogs:
I would say it's a fallout of failing to do proper releases and instead comiting in SVN and patching the package instead. >> Searching for Provides: /usr/lib/rpm/mageia/filter.sh ' ' ' ' >> '/home/tmb/RPM/BUILDROOT/kernel-linus-3.5.0-1.mga3.x86_64' >> /usr/lib/rpm/mageia/find-provides >> Traceback (most recent call last): >> File "/usr/lib/rpm/maven.prov", line 65, in <module> >> builder = TagBuilder () >> File "/usr/lib/rpm/maven.prov", line 46, in __init__ >> self.get_mvn_provide (path) >> File "/usr/lib/rpm/maven.prov", line 51, in get_mvn_provide >> with open(path) as f: >> IOError: [Errno 2] No such file or directory: '' >> > > and rpm-mageia-setup cleanup is the guilty one... > > > We had this: > http://svnweb.mageia.org/packages/cauldron/rpm-mageia-setup/current/SOURCES/rpm-mageia-setup-1.147-Better-handle-maven-prov.patch?revision=189248&view=markup&pathrev=189248 > > > where find-provides had: > mavenlist=$(echo "$filelist" |egrep '/usr/share/maven-poms/.*\.pom') > > but now has: > > mavenlist=$(echo "$filelist" |egrep '/usr/share/maven-fragments/*') > > > So wich one is right ? Are you sure it's not that old typo the issue (due to above issue about not doing proper releases, where one of soft & the package commit had a vim issue with "i")? http://svnweb.mageia.org/soft/rpm/rpm-setup/trunk/find-provides.in?r1=5229&r2=5233
