Certainly, most people would consider it a bug if the package rpms you were building, were installed after the build, and the build was repeated -- and then failed.
There are quite a few packages that require bootstrapping; And not really, if you use chroots to build, the binaries you previously built shouldn't really much interfere with a chroot build... If you don't use a chroot or a kvm or whatever and built them on the local system, you could have problems... can be related to compiler cache or any other weird stuff that happened... I wouldn't find it so hard to believe... And by the way, you can launch any offensive you want on openSUSE, I have no bonds with it besides being the regular troll; In fact I was even dubbed the 'destroyer of openSUSE' once :)
Having such radically different results based on the presence of the package contents you are building is almost fits the definition of entrapment -- "i.e. you can build it, but if you install it -- (a logical thing to do once one has built it), then you can no longer build it.
A lot of packages do require bootstraping; If you try to package a few Ruby gems with the test suite enabled, you can't miss it. A lot of Java stuff also requires proper bootstrapping and a load of examples can be found easilly. So, those packages are broken? Or you have never worked with a package that requires bootstrapping ? (I don't know about Samba, but I doubt it needs bootstrapping). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org