Stefan van der Eijk wrote: >>I'm just trying to get some packages updated that I haven't done >> because I've been busy. I finally find time to do it and someone goes >> and breaks rpmlint so I can't ensure my packages are good. >> > rpmlint is broken?
klama has rpm-4.2-9mdk (with new requires/provides applied), thus rpm-devel requires a bunch of devel() packages that don't exist yet, and rpmlint requires rpm-devel. There is no way to get rpmlint onto klama without --nodeps until glibc is rebuilt (remaing devel() deps have been done already, bzip2, elf, and rpm). It is unfortunate that the rpm package that added the new script had the deps applied to it ... but if it did not, it would be unforunate that nothing would provide the new devel requires => catch22. Lets hope Gwenole (or whoever is working on glibc) hurries up ... otherwise we might just have to start uploading unlinted packages. > >>The way I see it if you break something then you need to fix it and fix >> it promptly. >> > Fixing 2 or 3 hundred packages doesn't happen overnight.... We're > working on it. It's unfortunat that you've been caught in the middle of > it. Ben, if you don't have a cooker box to test with, put your SRPMS/RPMS somewhere accessible (like klama), and post the location here, and someone will take care of it, or (someone who still has rpmlint) can send you rpmlint output. Olivier may also have a cooker box you can access if necessary? Regards, Buchan
