https://bugzilla.novell.com/show_bug.cgi?id=776117
https://bugzilla.novell.com/show_bug.cgi?id=776117#c6
--- Comment #6 from Petr Gajdos
I need to cleanup my crappy spec file before so that it matches again your's which uses nice defines for the package versions and is overall cleaner, I can do that tomorrow and after successful test (the already built packages work for me) I will do the "osc sr".
Note that there is octave-forge.spec.in file from which is octave-forge.spec generated by calling sh update.sh. Therefore, changes made in octave-forge.spec will get lost with next sh updates.sh call, so changes should be made in octave-forge.spec.in. Then, sh update.sh should be called and package rebuild should be triggered then to test generated spec file.
One other unrelated thing: I updated a handful of octave forge packages to newer versions, do you want that update or shall I stay on the versions we already have in science?
This should be done automaticaly by update.sh call. But! Note there is also blacklist file in science/octave-forge source, which is read by update.sh and all packages listed there are ommited. The reason why is written in comment in blacklist. I know they should be fixed instead of blacklisting them, nevertheless I lack time for this. Moreover, there is a chance that some of them with "doesn't build with octave ..." can be compilable with octave 3.6.2 on current openSUSE. Feel free to propose better system :-). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.