http://bugzilla.novell.com/show_bug.cgi?id=520134 User monkey9@iae.nl added comment http://bugzilla.novell.com/show_bug.cgi?id=520134#c1 Robby Verberne changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |monkey9@iae.nl --- Comment #1 from Robby Verberne 2009-07-16 02:45:32 MDT --- This is wel seen. I have experienced more than once that 'bugs' were due to a/more unfullfilled deps. If one does not know, or cannot find which deps are absolutely nessesary to be fullfilled for an app to run properly, one cannot realy test it. fi amarok pulls only amarok and lang. I can not get it to run. To just 'wild guess' what is needed, might take more unnnessesary/needless pkgs. To 'know' the deps upfront might also deepen the insight, to see which pkgs are realy deps, and for which app. This way one can more easy see what is 'twined' together. To uninstall with all deps would be not so bad also, solver must be able to determine which pkgs are used by other apps though... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520134 User monkey9@iae.nl added comment http://bugzilla.novell.com/show_bug.cgi?id=520134#c3 --- Comment #3 from Robby Verberne 2009-07-16 08:43:50 MDT --- If sometimes you need a gnome pkg, because the kde counterpart does not work, half a gnome gets pulled in. After not needing this pkg anymore, the deps are not automaticaly uninstalled. This is not nice, because unwanted and unneeded pkgs stay on the sys. One should be able to uninstall with full deps also, without damage the os. But this is realy a nice and userfriendly proposition. I remember times the deps fullfilment was so dificult, i sometimes became too scared to upgrade, afraid to end up with a broken system. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520134 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=520134#c5 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO Info Provider| |dave.plater@yahoo.co.uk --- Comment #5 from Ján Kupec 2009-07-29 09:13:02 MDT --- (In reply to comment #2)

My proposal is:- if you select, for instance, packman kaffiene you will automatically pull in all the dependencies from packman and by doing so will not pull in opensuse packages with limited functionality.

Well, not all can be always satisfied from packman, you often need some from factory. You probably meant 'pull in all the deps available in both packman and factory from packman, not factory'. Well, this is something the repository priorities are for - increase the priority of the packman repo (give it lower number) and do 'zypper dup' (without -r). See also below.

At the moment if you perform a zypper dup -r packman you pull in unwanted packages like cairo and if you do dup -r factory all of the packman and vlc packages are replaced with opensuse ones.

What about a dup without the -r (or both -r packman -r factory)? Doesn't that work like this? It should not change vendor, so packman packages and their packman deps should stay packman.

In answer to "might take more unnnessesary/needless pkgs" I propose that no packages should change vendor but yes it will pull in more packages than a normal package update but it shouldn't pull in unnecessary ones. So if you select packman amarok and it wants to replace an opensuse factory package with it's packman version you will be warned.

That's how it should work now. But it if does not need to fulfill the dependency from packman (if it's OK with the factory's package), it won't do it. You'll need to manually select the packman package if you want the packman version. Please try and let us know about the outcome. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520134 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=520134#c7 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|dave.plater@yahoo.co.uk | --- Comment #7 from Ján Kupec 2009-07-29 10:12:22 MDT --- OK, bad try. To sum it up, we want: 1) install new packages while preferring the deps from the same repo as the new package 2) avoid changing the vendor when updating ('zypper up/in' does this) plus ensure new deps are pulled in from the same repo as the package requiring it? (this is not guaranteed). Does this make sense? Any ideas how to do this? Maybe something like temporary increasing the priority of the desired repo? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520134 Dave Plater changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|zypper and yast2 sw_single |zypper and yast2 sw_single |need an update package and |need an "update package and |all dependencies function |all dependencies |unconditionally |unconditionally" function -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.