https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c1 Martin Helm changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin_helm@arcor.de --- Comment #1 from Martin Helm 2012-08-16 14:00:57 UTC --- In addition the echo "addpath('%{octpackages_dir}/<package>-%{<packge>_version}/', '-begin')" needs to be replaced by a echo "addpath(genpath('%{octpackages_dir}/<package>-%{<packge>_version}/'), '-begin')" such that recursively the subdirectories are also added to octave's path, otherwise the binary libs are simply not found at runtime. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c3 --- Comment #3 from Martin Helm 2012-08-17 19:21:55 UTC --- So finally the correct way which I can confirm with local osc builds (the resulting rpm's wor as expected): octave -qf --eval "pkg prefix %{buildroot}%{octpackages_dir} %{buildroot}%{octlib_dir}; pkg install -nodeps $archive" (in the install loop) where octlib_dir is %{_libdir}/octave/packages so that the architecture dependent binaries go to the correct location where octave's packaging system expects them. of course this needs to be added also to the corresponding files section %{_libdir}/octave/packages/<pkgname-version> the %post and %postun for every package simply needs to be octave -qf --eval 'pkg rebuild' and nothing else. I build the packages now also in my obs home project to see how it works there home:martin_helm/octave-forge -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c Petr Gajdos changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c6 --- Comment #6 from Petr Gajdos 2012-08-20 14:14:42 UTC --- (In reply to comment #5)

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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c8 --- Comment #8 from Martin Helm 2012-08-20 16:02:25 UTC --- I'll rework the update.sh a bit and the octave-forge.spec.in to give a result that is compatible with the current structure of the spec file in science. Btw odepkg works now and making the gsl package work is an absolutely trivial fix, so I will add them and remove from blacklist. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c10 --- Comment #10 from Claudio Freire 2012-08-21 15:12:53 UTC --- (In reply to comment #8)

I'll rework the update.sh a bit and the octave-forge.spec.in to give a result that is compatible with the current structure of the spec file in science. Btw odepkg works now and making the gsl package work is an absolutely trivial fix, so I will add them and remove from blacklist.

I've been mantaining it by hand since an SR got accepted that made it difficult to use update.sh, but it would be nice to make it usable again. However, I'm wondering whether a python script using jinja templates wouldn't be easier to maintain (akin to py2pack templates). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c12 --- Comment #12 from Petr Gajdos 2012-08-22 08:45:40 UTC ---

What I see in your home[1] doesn't actually change the build (unless the diff[2] is lying to me)

It is at least lying about author of this change, so don't forget to set correct name in changelog entry ;-). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c14 --- Comment #14 from Martin Helm 2012-08-22 12:08:08 UTC --- also nether look at my spec.in file, I did a lot of direct manual changes to the spec itself, I had not yet any chance to do something further down the road for cleaning the update script or the spec.in, as my current workload this week looks like not before the weekend. I said also my spec is crappy, while I am a developer for scientific and medical software for twenty years, my knowledge about writing a spec file or using osc/obs is essentially what I quickly learned last week within a few hours of free time and that's also what the result looks like! -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c16 --- Comment #16 from Martin Helm 2012-08-23 11:39:59 UTC --- It does not know, only a human being inspecting the upstream packages can know (and it can change at any time when a new version is made), so I used for my own build a poor mans solution to create the paths unconditionally and always add it to the files section such that in the worst case an empty directory is installed, the octave packages do not care about that and the build sytem obviously also does not care. It is not nice though. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c18 Petr Gajdos changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|martin_helm@arcor.de | --- Comment #18 from Petr Gajdos 2012-08-28 07:57:20 UTC --- I am not sure if I understand your problem exactly, but it should be possible to generate fileslist.txt during install section and use it later by %files -f fileslist.txt I have never create such construction, but I would try it, if you find it useful. Also, I can help with update.sh and octave-forge.spec.in, if you want. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=776117 https://bugzilla.novell.com/show_bug.cgi?id=776117#c20 Claudio Freire changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #20 from Claudio Freire 2012-09-07 01:56:09 UTC --- Marking as fixed, as I pushed the changes mentioned here, plus running tests and assorted spec adjustments, and it all seems to work better now. Some tests are still failing, but they seem unrelated to this bug. In fact, I'll probably have to follow them upstream, as they look unrelated to packaging in general. -- 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.