On 8/19/2009 at 8:16, Dave Plater <dave.plater@yahoo.co.uk> wrote: Hi, this could be me being stupid or it could be a zypper dup bug. I built blender-2.49a-71.1 for the purpose of submission to factory to update blender from 2.48a to 2.49a and at the same time renamed subpackage blender-devel to blender-plugins-devel to avoid confusion as the package is for plugin development. I tried to follow the wiki "renaming a package" conventions. If I "zypper in blender" I get offered the latest factory 2.48a build, if I zypper if blender it states that -2.49a-71.1 is the latest version When I perform a zypper dup -r plagraf (which is the alias for home:plater:branches:graphics ) I get this output :-
Problem: problem with installed package blender-devel-2.48a-2.106.x86_64 Solution 1: Following actions will be done: keep blender-devel-2.48a-2.106.x86_64 keep blender-2.48a-2.106.x86_64
I'm not sure if zypper dup limited to a repository is going to be a good idea. Dup normally goes the way that 'all the packages available' are valid, everything else would be obsoleted... so a dup against a small project would render the entire system obsoleted (but this might also not be true anymore.. that's just what I remember). So, why does zypper up blender not suggest to update? This could have to do with repo priorities in my opinion. You should be able to either change your repo to a higher prio than the repo you currently get blender from? Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org