Re: [opensuse-factory] repository priorities with Tumbleweed
No, please don't confuse people, if you add more repos than just Tumbleweed you really had better know what you are doing or bad things can, and will, happen :)
You do know the legal reasons behind why packman is
I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff: "The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## " It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example "Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## " there, right? Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman. So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;) thanks anyway :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Jun 22, 2012 at 07:52:51PM +0200, Thomas Langkamp wrote:
No, please don't confuse people, if you add more repos than just Tumbleweed you really had better know what you are doing or bad things can, and will, happen :)
I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff:
"The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## "
No, please do not do that. Don't add anything about repo priorities here, why do that, it just confuses people.
It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example
"Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## "
That's fine to add.
You do know the legal reasons behind why packman is there, right?
Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman.
How do you know that it isn't already supported by packman? Last time I checked, it was...
So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;)
It's no different than what openSUSE is on its own, so I wouldn't go adding any new descriptions to it that don't also apply to the main project. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg KH wrote: No, please don't confuse people, if you add more repos than just Tumbleweed you really had better know what you are doing
How am I supposed to "know better what I am doing" if there is: - no official (SDB) documentation on priorities (I could add it based on Cristian Vegas forum post: http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/un...) - no docu on how to use Tumbleweed+Packman in the packman wiki (this is not your problem, I will ask packman to add it) - almost no docu in the community-wiki: http://opensuse-community.org/Restricted_formats/Tumbleweed There is no word about setting priorities which is recommended by you and Cristian Vega WHEN using TW+packman - if I understood right. Is it legaly possiple to add a link from en.opensuse.org/Portal:Tumbleweed to the packman-wiki-page and/or the community-wiki-page explaining TW+packman? Please do not say that you just should not use TW+packman because many bleeding edge users (and most TW users are bleeding edge) just do it rely on packman.
Don't add anything about repo priorities to http://en.opensuse.org/Portal:Tumbleweed, why do that, it just confuses people.
I am a user (not a developer) and I am confused because of the lack of documentation of features. You cannot overloock that there are priorities in yast/software-management, so you need to know how to use them best or they should be hidden behind an "expert-button" or so, and even then they need documentation. I admit there are 2 centences about priorities in Yast/repo-management if you click "Help", but they do not tell why one would use priorities or how they are used best in which situation. So: - user was confused about priorities (+TW) - user found help in forum+mailinglist - user wants to give his new knowledge to the community so other users won´t have to dig for the info in forum+mailinglist again
But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman.
How do you know that it isn't already supported by packman? Last time I checked, it was...
What means support here? As I state above, their wiki-guidance on TW is far from complete... I hope I explained my point of view better this time :D Thanks for your time - Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-06-23 09:20, Thomas Langkamp wrote:
I am a user (not a developer) and I am confused because of the lack of documentation of features. You cannot overloock that there are priorities in yast/software-management, so you need to know how to use them best or they should be hidden behind an "expert-button" or so, and even then they need documentation. I admit there are 2 centences about priorities in Yast/repo-management if you click "Help", but they do not tell why one would use priorities or how they are used best in which situation.
I understand that in the case of tumbleweed the priorities are a moot point. You are supposed to do a "dup --from tumbleweed", so any package you had installed from packman will be replaced, regardless of the priority packman has. If you do a plain "dup" without saying "from tumbleweed" then priorities are a concern - but the wiki says not to do it if you have extra repos. So indeed using packman with tumbleweed is a concern. You have to do a second update run switching multimedia back to packman. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/lqrcACgkQIvFNjefEBxq2rgCfZssfR+4r1DKkT43E1U9zvzaI g3sAn1REAjciOHqTriacmrsZwxlggsvJ =gCoT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [06-23-12 07:40]: ...
I understand that in the case of tumbleweed the priorities are a moot point. You are supposed to do a "dup --from tumbleweed", so any package you had installed from packman will be replaced, regardless of the priority packman has.
If you do a plain "dup" without saying "from tumbleweed" then priorities are a concern - but the wiki says not to do it if you have extra repos.
So indeed using packman with tumbleweed is a concern. You have to do a second update run switching multimedia back to packman.
If one is going to do a "second" update last anyway, then giving packman a higher priority (stature) and performing a "dup" would provide the same result. fwiw, I have all priorities the same (untouched) and *always* do a "dup" but always check packages for what I would perceive as *problems*, then utilize locks to procede semi-inteligently. I have quite a few "tumbleweed" repos aside from the main issue besides a few singular packages not "supported" by tumbleweed and have occasionally had problems. Problems that I have are bypassed by going to icewm for a short time and usually "resolve themselves". Accolades to GregKH for his much appreciated efforts and contributions. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dear list, I am not a subscriber but follow you since Gregs first TW and am a loving 12+ years suse user. Still, I am not an admin nor a dev, just a bloody user == noob. In light of the (third recent) discussion about zypper up / dup I want to sumarize the results. And I want to beg you to take actions on them, to make suse more noob-friendly - because noobs may become the future suse devs. Here my humble wishlist which applies for TW & Leap: - during installation or directly after the installation (e.g. via a desktop-icon named "upgrade multimedia / codecs"): let the user opt-in to packman-repo via asking him if he needs full multimedia capabilities (currently this is hidden in "yast / repos / add community repo" and only available for 13.2) - when opting-in to packman: automagically add packman with a 98 priority & allow vendor change once & automatically apply zypper up or dup afterwards (those more knowledgable should still be enabled to change priority / vendor change of course; this is about sane defaults for noobs) - install recommends: only once during installation as default - automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job. - Require minimal user intervention for the update/grade: require sudo password if new software is installed, but not when existing software is updated; but let the user know if he needs to restart or log-off. - partialy unrelated: let flash stay for the noobs, those more knowledgable can uninstall / block it - what can I contribute? I would love to update the wiki accordingly Please do it for us noobs. Remember, noobs can become future suse-admins. The more we attract, the higher the chance. I love suse. Cheers, tomtomme -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14 July 2015 at 11:25, Thomas Langkamp <langkamp@tomblog.de> wrote:
- during installation or directly after the installation (e.g. via a desktop-icon named "upgrade multimedia / codecs"): let the user opt-in to packman-repo via asking him if he needs full multimedia capabilities (currently this is hidden in "yast / repos / add community repo" and only available for 13.2)
Sadly, as described here, this would make openSUSE liable for any patent infringement by encouraging our users to install patent encumbered software, or possibly even guilty of "facilitation of crime" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 14.07.2015 um 13:00 schrieb Richard Brown:
- during installation or directly after the installation (e.g. via a desktop-icon named "upgrade multimedia / codecs"): let the user opt-in to packman-repo via asking him if he needs full multimedia capabilities (currently this is hidden in "yast / repos / add community repo" and only available for 13.2) Sadly, as described here, this would make openSUSE liable for any
On 14 July 2015 at 11:25, Thomas Langkamp <langkamp@tomblog.de> wrote: patent infringement by encouraging our users to install patent encumbered software, or possibly even guilty of "facilitation of crime"
Thanks Richard for your reply :) Are you saying that there is a difference between providing "yast / repos / add community repo" and the same functionality as a desktop icon? Interesting. But Why? Only because the one is more hidden than the other? I cannot imagine how this would make a difference in court, but I am no lawyer also. So what about my other points? - when adding packman: automagically add packman with a 98 priority & allow vendor change once & automatically apply zypper up or dup afterwards (those more knowledgable should still be enabled to change priority / vendor change of course; this is about sane defaults for noobs) - install recommends: only once during installation as default - automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job. - Require minimal user intervention for the update/grade: require sudo password if new software is installed, but not when existing software is updated; but let the user know if he needs to restart or log-off. - partialy unrelated: let flash stay for the noobs, those more knowledgable can uninstall / block it - what can I contribute? I would love to update the wiki accordingly Please do it for us noobs :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-14 11:25, Thomas Langkamp wrote:
- automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job.
Never automatically. If apper does not work, then it has to be improved, but installing updates in background by default is not the way. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWk7b0ACgkQja8UbcUWM1xPzgEAlFVFnoxZ5uQ8a3PNfRP5Hyd6 o4v05CzBKlwMjvaSPyYA/2ZDg4ODw5+1jlIqY8CSSTMmUQaxkm9F4j/aDZJaUxtK =jgOc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 14 Jul 2015 13:08:45 +0200 "Carlos E. R." <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-07-14 11:25, Thomas Langkamp wrote:
- automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job.
Never automatically.
Why not for the average joe user? Windows been doing this a long time. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-14 13:42, yac wrote:
On Tue, 14 Jul 2015 13:08:45 +0200 "Carlos E. R." <> wrote:
Never automatically.
Why not for the average joe user? Windows been doing this a long time.
And openSUSE does, with packagekit (apper et friends), it is designed for this. Doing it with zypper is not a good option, it is not designed for it. You can, of course, create a cron job to do it. Your choice: you know what you do in your own machine, However, Windows (7+ at least) does not do it. In Windows, if you are a plain user, you can not install updates, you are asked for the administration password. You think that it does because you are running Windows as a user with admin powers, which is the default, but not recommended. You should use Windows as an unprivileged user. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWlFbgACgkQja8UbcUWM1xQJQD/ZIGNEGvpKZV1WuYk+W8PaqsN 3k6rkfpfm1Qz1j9kdo4A/3iC3u3zVsCZo2pgxkpVW/smy9+iewODEpBecfRK3zcD =zxRP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/14/2015 07:42 AM, yac wrote:
On Tue, 14 Jul 2015 13:08:45 +0200 "Carlos E. R." <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-07-14 11:25, Thomas Langkamp wrote:
- automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job.
Never automatically.
Why not for the average joe user? Windows been doing this a long time.
Short answer, this is not windows. Second, any update could make the system unbootable due to third party repos being configured. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/14/2015 07:42 AM, yac wrote:
On Tue, 14 Jul 2015 13:08:45 +0200 "Carlos E. R." <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-07-14 11:25, Thomas Langkamp wrote:
- automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job. Never automatically. Why not for the average joe user? Windows been doing this a long time. Windows is not Linux. Linux is not Windows. Linux is always looking at security.
One thing I've learned over time when I was a noob was that you make it a habit of understanding how your system works. You run through a checklist in your mind so that you know what is being installed and what is being updated. Security should always be on your mind. Running an auto-update bypasses security. Cheers! Roman ICQ: 551368250 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
It would seem part of the suggestion could be solved by allowing the priority to be set in a .repo file and make that the suggested path for adding packman (in wiki and elsewhere). ie a file like http://download.opensuse.org/repositories/home:/boombatower:/openage/openSUS... [home_boombatower_openage] name=openage (openSUSE_Tumbleweed) type=rpm-md baseurl=http://download.opensuse.org/repositories/home:/boombatower:/openage/openSUS... gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/home:/boombatower:/openage/openSUS... enabled=1 <<priority=90>> <-- add this Perhaps it is already supported? If so then simply suggesting on packman list to provide such a file with configured priority. The docs could also be updated to include the highly recommended zypper dup --from packman once step. Also would be nifty if that priority could be altered on any OBS repository so project maintainers can set a priority that makes sense as described in the other thread. (perhaps already available?) Another slick addition would be to add a --priority option to `zypper ar` so it could be documented with priority instead of requiring an `mr` step to change it after adding. I would actually be interested in seeing if I could tackle adding such a feature. Note my packman setup instructions on https://github.com/jp9000/obs-studio/wiki/Install-Instructions which include this longer set of steps (screenshot for lazy: http://i.imgur.com/3L5lPE8.png). Assuming a properly configured system I would imagine the last issue regarding conflict resolution would be less of an issue since conflicts should arise less often, but yast or zypper have an interactive way to solve that. Obviously it's not automatic, but computers cannot think quite yet. -- Jimmy On Tue, Jul 14, 2015 at 1:34 PM, Roman Bysh <rbtc1@rogers.com> wrote:
On 07/14/2015 07:42 AM, yac wrote:
On Tue, 14 Jul 2015 13:08:45 +0200 "Carlos E. R." <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-07-14 11:25, Thomas Langkamp wrote:
- automatically update/grade the OS daily: by executing zypper up or dup in the background (via cron-job or graphical utility?) AFAIK apper still cannot propose solutions for conflicts and thus might not be feasible for this job. Never automatically. Why not for the average joe user? Windows been doing this a long time. Windows is not Linux. Linux is not Windows. Linux is always looking at security.
One thing I've learned over time when I was a noob was that you make it a habit of understanding how your system works.
You run through a checklist in your mind so that you know what is being installed and what is being updated.
Security should always be on your mind.
Running an auto-update bypasses security.
Cheers!
Roman
ICQ: 551368250
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-15 06:14, Jimmy Berry wrote:
It would seem part of the suggestion could be solved by allowing the priority to be set in a .repo file and make that the suggested path for adding packman (in wiki and elsewhere).
Yes... perhaps...
Another slick addition would be to add a --priority option to `zypper ar` so it could be documented with priority instead of requiring an `mr` step to change it after adding.
Not bad :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWmMcIACgkQja8UbcUWM1xBjAEAjmtNozeo1dbLcDItJ5f4YTyp FMzv49Wx6LS8yqT1BDMA/1VfFRBuRgqr6I4+ESzamg23QUsa4VBdtKD4UgaH/eUw =wWNU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Tue, Jul 14, 2015 at 11:14:48PM -0500, Jimmy Berry wrote:
It would seem part of the suggestion could be solved by allowing the priority to be set in a .repo file and make that the suggested path for adding packman (in wiki and elsewhere). [ 8< ] Perhaps it is already supported?
The repository definition already knows priority as parameter since quite some years.
If so then simply suggesting on packman list to provide such a file with configured priority. The docs could also be updated to include the highly recommended zypper dup --from packman once step.
And that's the wrong (some might even count it as a dangerous) suggestion! Don't use dup in this case as you would replace any package of your system with the version available at the packman side. While the majority only needs a quite small subset to get full multimedia support for example flying. Plus YaST has a module to enable popular additional software repositories. Please check if the wiki points to them too. If not feel free to enhance the documentation.
Also would be nifty if that priority could be altered on any OBS repository so project maintainers can set a priority that makes sense as described in the other thread. (perhaps already available?)
And then the race starts who has the lowest? I doubt if that approach will lead to a good result.
Another slick addition would be to add a --priority option to `zypper ar` so it could be documented with priority instead of requiring an `mr` step to change it after adding. I would actually be interested in seeing if I could tackle adding such a feature. Note my packman setup instructions on https://github.com/jp9000/obs-studio/wiki/Install-Instructions which include this longer set of steps (screenshot for lazy: http://i.imgur.com/3L5lPE8.png).
Due to the huge amount of mailing lists we have for openSUSE I fear the YaST/ libzypp/ zypper developers will will miss this thread. Therefore please file a bug report or a feature request. As you're already at github you might even file an issue there. The YaST/ libzypp/ zypper is there too. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-15 12:11, Lars Müller wrote:
If so then simply suggesting on packman list to provide such a file with configured priority. The docs could also be updated to include the highly recommended zypper dup --from packman once step.
And that's the wrong (some might even count it as a dangerous) suggestion! Don't use dup in this case as you would replace any package of your system with the version available at the packman side. While the majority only needs a quite small subset to get full multimedia support for example flying.
Well, many of the guides and the advice we give are to do just that (dup --from packman), or in yast, click on the "switch system packages to this repository" link. I do it myself. But it is true, it is problematic, because, for instance, it replaces Lazarus with an older version. So I have to undo a few changes. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWmOOoACgkQja8UbcUWM1z3qwD/bwQP1FA4eNdZZIiw3Lb00kxs yfbxRSSz/wVlpA8CjMEA/RtC8z0FGAG3jENkh3lCcaWwUmNafyMCwB7LYhnUQQGQ =M8Ob -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/15/2015 06:41 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-07-15 12:11, Lars Müller wrote:
If so then simply suggesting on packman list to provide such a file with configured priority. The docs could also be updated to include the highly recommended zypper dup --from packman once step.
And that's the wrong (some might even count it as a dangerous) suggestion! Don't use dup in this case as you would replace any package of your system with the version available at the packman side. While the majority only needs a quite small subset to get full multimedia support for example flying.
Well, many of the guides and the advice we give are to do just that (dup --from packman), or in yast, click on the "switch system packages to this repository" link.
I do it myself. But it is true, it is problematic, because, for instance, it replaces Lazarus with an older version. So I have to undo a few changes.
- -- Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlWmOOoACgkQja8UbcUWM1z3qwD/bwQP1FA4eNdZZIiw3Lb00kxs yfbxRSSz/wVlpA8CjMEA/RtC8z0FGAG3jENkh3lCcaWwUmNafyMCwB7LYhnUQQGQ =M8Ob -----END PGP SIGNATURE-----
Shouldn't most noobs use Yast gui and ncurses?
From there they will learn about priority. Setting packages to do not modify. Changing vendors. Etc..etc..etc..
Once they understand Yast they can tackle using zypper. It's a process. Cheers! Roman ICQ: 551368250 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-15 21:29, Roman Bysh wrote:
On 07/15/2015 06:41 AM, Carlos E. R. wrote:
Shouldn't most noobs use Yast gui and ncurses? From there they will learn about priority. Setting packages to do not modify. Changing vendors. Etc..etc..etc..
Once they understand Yast they can tackle using zypper. It's a process.
I understand they prefer apper. Or the equivalent in gnome, pk-icon? I always forget its name. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWnBJoACgkQja8UbcUWM1ylPAD+Ldwj5UXVhoCf0PwRavsFlLr/ CfkDt1qwLlLG5fQM1bQA/RXe3NsIa9I2ZHbGfvWqJvqpMtXwSlNnfd9khs4ZbpKa =sSnV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (11)
-
Carlos E. R. -
Carlos E. R. -
Greg KH -
Jimmy Berry -
Ken Schneider - Factory -
Lars Müller -
Patrick Shanahan -
Richard Brown -
Roman Bysh -
Thomas Langkamp -
yac