On Wed, Jul 09, 2003 at 12:00:28AM +0200, Buchan Milne wrote: > 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.
Yup and rpmlint was on there (I'd assume becasue the new rpm was installed --nodeps) until Nanar rebuilt libelfutils and then installed it which caused rpmlint... > Lets hope Gwenole (or whoever is working on glibc) hurries up ... > otherwise we might just have to start uploading unlinted packages. How long can it take to rebuild the package? I'd understand a lot more if this was some obscure thing that was in contrib. But this is in main and glibc is a core item. > 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? What's the point if the devel requires are going to be wrong for what's in cooker? Until everything else gets built I might as well wait for them to fix it. It's just irritating to be working on something and then have the tool(s) you need yanked out from under you. My point still stands. This should have been organized to happen in the least painful way. Rather we have people rebuilding things haphazardly whenever something gets in their way... which just makes more problems... -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org "What upsets me is not that you lied to me, but that from now on I can no longer believe you." -- Nietzsche
