Sorry for not responding earlier but I'm only subscribed to -packaging so I stumbled about it in the archive.
Eric Gearhart wrote: > I agree - if no one else is reporting it maybe it's just a fluke in my > install and the other person's install... And that is why it happens in Fedora, Mandriva & openSUSE chroots that get setup & destroyed on demand and work just fine for thousands other packages? I'm sorry, but I beg to differ ... ;P Jan-Oliver Wagner wrote: > Michael and myself were not able to reproduce the problem nor > to fully understand it. That part surprised me a bit since it is actually very easy to reproduce if you use the build service as I explained before. But perhaps you missed it, so let me explain it once more: 1. Go to https://build.opensuse.org/ and create an account (I didn't receive a single spam / advertisement mail in all those years so it is safe). 2. Go to http://download.opensuse.org/repositories/openSUSE:/Tools/ and add the appropriate subdirectory as a repository and install "osc". 3. Run "osc co home:bitshuffler:openvas:unstable openvas-libraries" to get the project files 4. Run "cd home\:bitshuffler\:openvas\:unstable/openvas-libraries/" to get into the proper subdirectory 5. Run e.g. "osc build openSUSE_11.1 i586 openvas-libraries.spec" to build it for openSUSE 11.1 & i586 arch which will download all needed packages and install them into a chroot so your normal system will not be touched in any way. Total spent time <5 minutes (if you don't count the time needed for downloading packages). Perhaps that helps. regards, Stephan _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
