[opensuse] Tumbleweed users should do zypper up or dup to stay current?
I have some systems that I upgraded to OSS tumbleweed. The upgrade itself was done via zypper dup. With the recent changes to tumbleweed, do I need to do a zypper dup on a regular basis to stay current with tumbleweed or can I keep on doing zypper up like I am used to from the past? Thanks in advance for your help, -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/11/14 a las 17:47, Moby escribió:
I have some systems that I upgraded to OSS tumbleweed. The upgrade itself was done via zypper dup. With the recent changes to tumbleweed, do I need to do a zypper dup on a regular basis to stay current with tumbleweed or can I keep on doing zypper up like I am used to from the past?
Thanks in advance for your help,
Use zypper dup .. packages may be renamed, removed..etc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/28/2014 02:51 PM, Cristian Rodríguez wrote:
El 28/11/14 a las 17:47, Moby escribió:
I have some systems that I upgraded to OSS tumbleweed. The upgrade itself was done via zypper dup. With the recent changes to tumbleweed, do I need to do a zypper dup on a regular basis to stay current with tumbleweed or can I keep on doing zypper up like I am used to from the past?
Thanks in advance for your help,
Use zypper dup .. packages may be renamed, removed..etc..
Many thanks Cristian. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 28 november 2014 17:51:21 schreef Cristian Rodríguez:
El 28/11/14 a las 17:47, Moby escribió:
I have some systems that I upgraded to OSS tumbleweed. The upgrade itself was done via zypper dup. With the recent changes to tumbleweed, do I need to do a zypper dup on a regular basis to stay current with tumbleweed or can I keep on doing zypper up like I am used to from the past?
Thanks in advance for your help,
Use zypper dup .. packages may be renamed, removed..etc..
The problem with zypper dup is that you may have other repositories from where you want to use packages which are also present in OSS Tumbleweed. So a dup where you specify not to change to another provider would be needed. AFAIK this is not possible at this moment. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Freek de Kruijf
Op vrijdag 28 november 2014 17:51:21 schreef Cristian Rodríguez:
El 28/11/14 a las 17:47, Moby escribió:
I have some systems that I upgraded to OSS tumbleweed. The upgrade itself was done via zypper dup. With the recent changes to tumbleweed, do I need to do a zypper dup on a regular basis to stay current with tumbleweed or can I keep on doing zypper up like I am used to from the past?
Thanks in advance for your help,
Use zypper dup .. packages may be renamed, removed..etc..
The problem with zypper dup is that you may have other repositories from where you want to use packages which are also present in OSS Tumbleweed. So a dup where you specify not to change to another provider would be needed. AFAIK this is not possible at this moment.
zypper al --help include in the lock the distro you do *not* want packages from, ie: zypper al -r graphics -r openSUSE-Factory\ Oss\ -r openSUSE-Factory\ packman\ darktable* provide (/etc/zypper/locks): repo: graphics repo: openSUSE-Factory OSS repo: openSUSE-Factory multimedia_photo repo: openSUSE-Factory packman type: package match_type: glob case_sensitive: on solvable_name: darktable Which keeps zypper dup from using darktable packages in the repos named. I have been using this scenario since Tw came into being and zypper allow locking from multiple repos :^) Don't know if zypper allows globs in repo names? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/28/2014 03:45 PM, Patrick Shanahan wrote:
* Freek de Kruijf
[11-28-14 16:30]: El 28/11/14 a las 17:47, Moby escribió:
I have some systems that I upgraded to OSS tumbleweed. The upgrade itself was done via zypper dup. With the recent changes to tumbleweed, do I need to do a zypper dup on a regular basis to stay current with tumbleweed or can I keep on doing zypper up like I am used to from the past?
Thanks in advance for your help, Use zypper dup .. packages may be renamed, removed..etc.. The problem with zypper dup is that you may have other repositories from where you want to use packages which are also present in OSS Tumbleweed. So a dup where you specify not to change to another provider would be needed. AFAIK
Op vrijdag 28 november 2014 17:51:21 schreef Cristian Rodríguez: this is not possible at this moment. zypper al --help
include in the lock the distro you do *not* want packages from, ie:
zypper al -r graphics -r openSUSE-Factory\ Oss\ -r openSUSE-Factory\ packman\ darktable*
provide (/etc/zypper/locks):
repo: graphics repo: openSUSE-Factory OSS repo: openSUSE-Factory multimedia_photo repo: openSUSE-Factory packman type: package match_type: glob case_sensitive: on solvable_name: darktable
Which keeps zypper dup from using darktable packages in the repos named.
I have been using this scenario since Tw came into being and zypper allow locking from multiple repos :^)
Don't know if zypper allows globs in repo names?
Thank you for the ideas and thoughts - zypper dup makes sense. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Cristian Rodríguez
-
Freek de Kruijf
-
Moby
-
Patrick Shanahan