> > Notice the build date? If his report was made *after* June the 3rd, > then it is obvious why it's not fixed in this package. > Still, you could refrain from public release of a build that is *known* to be broken. -3mdk appeared on mirrors just yesterday and not June the 4th. It is different from -2mdk problem where first reports happened after it was released. -andrej
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0 updates kill... Michael Brown
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0 updates... Vincent Danen
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0 upd... guran
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0... Vincent Danen
- Re: [Cooker] kdelibs woes (was: Mandrake... Andrej Borsenkow
- Re: [Cooker] kdelibs woes (was: Mandrake... guran
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0 upd... Michael Brown
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0... Vincent Danen
- Re: [Cooker] kdelibs woes (was: Mandrake... Michael Brown
- Re: [Cooker] kdelibs woes (was: Man... Vincent Danen
- Re: [Cooker] kdelibs woes (was:... Michael Brown
- Re: [Cooker] kdelibs woes (... Vincent Danen
- Re: [Cooker] kdelibs woes (... Michael Brown
- Re: [Cooker] kdelibs woes (... Vincent Danen
- Re: [Cooker] kdelibs woes (was: Mandrake 8.0 updates... Arnd Bergmann
