https://bugzilla.novell.com/show_bug.cgi?id=487626 User sven.burmeister@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c1 Sven Burmeister changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sven.burmeister@gmx.net --- Comment #1 from Sven Burmeister 2009-03-22 15:39:34 MST --- update unconditionally would update all packages, an option to only "update" packages that have a higher version number than those available in the repos, i.e. those marked red in yast. -- 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=487626 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c3 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com --- Comment #3 from Michael Andres 2009-03-27 03:38:49 MST --- (In reply to comment #0)

For example when using a fast changing repos like the KDE build service repos you'll often have packages which are actually newer, but have lower build/release number ("red packages" in YaST sw_single). There seems to be no simple way of fixing/avoiding this situation with zypper.

An option for zypper to update everything in the repos, even if the version is "older", would be nice.

Did you try to give those repos a higher priority, so the solver will prefer their packages independent of their version? -- 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=487626 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c5 --- Comment #5 from Michael Andres 2009-03-27 05:28:07 MST --- yes, 'zypper dup' would automatically switch to the high prio repo. With 'zypper up' you had to manually relace already installed packages with the ones from the high prio repo first. But then 'zypper up' should stay with this repo, and also prefer it for newly installed packages. -- 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=487626 User andrea@opensuse.org added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c7 --- Comment #7 from andrea florio 2009-03-27 06:34:07 MST --- update unconditionally will be usefull for example to create a "zypper-on-CD" script, the same thing apt-on-CD do.. let me explain it better. it is able to download all installed debs and create an installation media like DVD or CD. that "should" be done easily using that option, for example you can download all installed rpms like that: zypper modifyrepo --keep-packages --remote zypper dup-unconditionally --auto-agree-with-licenses --dry-run than copy rpms into a temp dir and use createrepo to create the installation source. -- 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=487626 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c9 --- Comment #9 from Ján Kupec 2009-03-27 08:29:59 MST --- c#7: To accomplish this, the 'update' would also need to reinstall a lot of packages (all that would be kept as they are otherwise). I'm not sure if that should be added. There must be better ways to do this than to abuse 'update' functionality. E.g. use --root: $ zypper repos -e myrepos.repo $ mkdir /tmp/myroot $ zypper --root /tmp/myroot addrepo myrepos.repo $ zypper --root /tmp/myroot modify-repo -kr $ zypper --root rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE} ' | xargs \ zypper in --dry-run (soon also 'zypper in --download-only ...') What about that? -- 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=487626 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c11 --- Comment #11 from Ján Kupec 2009-03-27 08:33:49 MST --- (In reply to comment #9)

$ zypper --root rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE} ' | xargs \ zypper in --dry-run

eh, here's the right command: $ rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE} ' | \ xargs zypper --root /tmp/myroot in --dry-run -- 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=487626 User sven.burmeister@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=487626#c13 --- Comment #13 from Sven Burmeister 2009-03-27 08:48:04 MST --- An example which would need a simple solution, i.e. work with either zypper up or dup and a mx of one added option is: User has a repo and updates the system. that repo contained a newer version of e.g. Qt or Xorg, which brakes his system. Now it would be easiest, if the user simply removes the repo, which will lead to "red packages", i.e. there is only a lower version available. (packages for which there is no other version available are a different matter) If the user now issues a zypper dup, not only will all packages for which only a lower version exists be updated, but new packages might be installed as well. The latter is what one should be able to avoid, i.e. tell zypper to do a dup without installing new packages. The -repo does not work because the user does not know which repo the older packages should come from, i.e. zypper simply has to go through each of the available repos and pick the highest version available. -- 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.