October 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309393] Make "unpublish" files and removing files from :full tree easy
by fate_noreply＠suse.de 27 Jan '17

27 Jan '17

Feature added by: Adrian Schröter (adrianSuSE) Feature #309393, revision 1 Title: Make "unpublish" files and removing files from :full tree easy Buildservice: New Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: Currently it is quite complex to remove build results from public repo or :full repo tree, if you do not want to remove the source package. We need to extend wipebinaries call with a target for :full and :repo dir and make this easy accessable via osc and webui. -- openSUSE Feature: https://features.opensuse.org/309393

1 6

[New: openFATE 313441] Easy Upgrade
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Mário Castanheira (SpeccyMan) Feature #313441, revision 1 Title: Easy Upgrade openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Mário Castanheira (speccyman) Partner organization: openSUSE.org Description: An easy way to allow users to make upgrades (e.g.: changing from version 12.1 to version 12.2) as easy as they can in Ubuntu. Something like one-click, instead of having to deal whit the work of disable and update of the repositories manually. Would be good if all this would be automatic and maybe even integrated it into the new Software Center. Use Case: User gets notified that there's a new version of opensuse available and it is asked if he wishes to upgarde. If he selects "upgrade" the system should ask for permissions and then start upgrading itself. (pretty much like in ubuntu). Nothing else required! Business case (Partner benefit): openSUSE.org: Because it will invite users to keep their distro in it's last version, even if they don't understand much about computers! And because it's something all Ubuntu users keep saying it's one of their loved features. -- openSUSE Feature: https://features.opensuse.org/313441

1 34

[New: openFATE 310405] yast2 wagon should be a fully graphic upgrade tool
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Greg Freemyer (gregfreemyer) Feature #310405, revision 1 Title: yast2 wagon should be a fully graphic upgrade tool openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Greg Freemyer (gregfreemyer) Description: I really like it that yast2-wagon exists for users to upgrade from release to release. It effectively does a zypper dup, but via a nicer gui interface. The trouble in my mind is that it still takes way to many seperate steps as is. Quoting just the top level details from http://old-en.opensuse.org/Wagon === 1) Ensure you have yast2-wagon installed 2) As of openSUSE 11.2 Wagon will update the upgrade stack as part of its automated process, so there is no need to ensure you have run zypper up or equivalent 3) Ensure you have the the correct repositories enabled 4) Start YaST2 wagon 5) Follow the dialogs 6) reboot === Taking those steps one at a time: 1) yast2-wagon should be part of the standand yast pattern in my opinion. It currently is not, so it has to be separately installed which makes little sense for a tool designed to simplify the upgrade process. 2) That was a great improvement that went into 11.2, so I'm happy. (Other than the current bugzilla against the yast2-wagon dependencies in the 11.3 release. I wish that would be fixed.) 3) It would be great if yast2-wagon would launch with a user selectable distro to upgrade to. Then once a user selected 11.4 as an example, it would walk the user through upgrading his repos to the 11.4 compatible ones. 4) Once 3) is incorporated it would be great to get a easy to click icon for wagon either within yast itself, or on the system menus. 5) This appears to be an effort to achieve automatic repo updates, but I'm not sure. Unfortunately, the above can be implemented for the 11.3 => 11.4 upgrade but only if the upgraded yast2-wagon is released via online update. That is because it involves updating the repo handling prior to pulling down a new copy of wagon from the 11.4 repos. -- openSUSE Feature: https://features.opensuse.org/310405

1 4

[openFATE 308189] Consolidating terminology: update and upgrade
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Karl Eichwalder (keichwa) Feature #308189, revision 1 Title: Consolidating terminology: update and upgrade openSUSE-11.3: New Priority Requester: Mandatory Requested by: Karl Eichwalder (keichwa) Partner organization: openSUSE.org Description: In the past, we just used the term "update" for all update related things, because we were told "upgrade" is suitable for hardware related upgrades only. With the advent of zypper, the term "upgrade" (dup, dist-upgrade) is back for upgrading the system complete from one version "n" to the next version "n+1" (yes, you can "upgrade" within one version, but that's a special case...). The term is fine and I'd like us to use "upgrade" in YaST and everywhere else where suitable. Business case (Partner benefit): openSUSE.org: Avoid confusion. ATM, I'm force to use different terms in the chapter of the manual, if I describe the same task. -- openSUSE Feature: https://features.opensuse.org/308189

1 13

[New: openFATE 312799] Safer distribution updates
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Duncan Mac-Vicar (dmacvicar) Feature #312799, revision 1 Title: Safer distribution updates openSUSE Distribution: New Priority Requester: Desirable Requested by: Duncan Mac-Vicar (dmacvicar) Product Manager: Michael Elliott (mge) Developer: ma ds (ma) Partner organization: openSUSE.org Description: Currently the documentation says that to do a distribution upgrade you should first update your software stack to the target distribution, then do a zypper dup. The software stack update can already kill your system. zypper could allow an option that makes it first install a miniroot containing the update stack itself, then automatically switch over to the miniroot to do the "zypper dup". Use Case: Bob wants to migrate his server from SLE12 to SLE13. Upgrading the package management stack fails, but he keeps his original system untouched. Business case (Partner benefit): openSUSE.org: Failsafe migrations for SLE -- openSUSE Feature: https://features.opensuse.org/312799

1 18

[openFATE 308147] Simplify "Online update" in Yast
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Birger Kollstrand (MrKane) Feature #308147, revision 1 Title: Simplify "Online update" in Yast openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Birger Kollstrand (mrkane) Description: In 11.2 there are two Online Update applications - one for configuration of online update - one for doing a manual online update I suggest that this is merged to one application which looks mostly like todays "Online update configureation" but has an aditional button on the page that when pushed does an online update. This will simplify the Yast GUI. -- openSUSE Feature: https://features.opensuse.org/308147

1 1

[New: openFATE 316789] Fundamental re-design how to set up the whole printing stuff
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Johannes Meixner (jsmeix) Feature #316789, revision 1 Title: Fundamental re-design how to set up the whole printing stuff Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: The current YaST printer module provides different buttons (i.e. entry points) with different workflows for the different kind of printing setup actions: One via "Add", one via "Printing via Network", one via "Share Printers", and so on. This means the user must know in advance what to choose for his particular kind of printing setup. The software cannot guide the user towards the right entry point according to what the user wants to get in the end. To guide the user towards an actually right solution the initial dialog should show the list of currently available print queues plus one single button to "do whatever can be done" when something is not as expected (e.g. when something is missing) in that list. This means a fundamental re-design of the dialogs and workflows to set up the whole printing stuff is needed. -- openSUSE Feature: https://features.opensuse.org/316789

1 13

[New: openFATE 308853] Add tab-to-complete and doubletab-to-query functionality to zypper
by fate_noreply＠suse.de 19 Dec '16

19 Dec '16

Feature added by: Michael Jones (toupeiro) Feature #308853, revision 1 Title: Add tab-to-complete and doubletab-to-query functionality to zypper openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Michael Jones (toupeiro) Description: Extend zyppers command line capabilities by enabling tab to complete against indexed repository packages and doubletab-to-query to essentialy perform a zypper se on the active installation command line. This would give zypper some functionality already present in debians aptitude package management system and would increase application installs and removals from the CLI. -- openSUSE Feature: https://features.opensuse.org/308853

1 5

[New: openFATE 310883] File Integrity GUI/Nautilus/GOME/Right click
by fate_noreply＠suse.de 19 Dec '16

19 Dec '16

Feature added by: Narayansamy S (vazhavandan) Feature #310883, revision 1 Title: File Integrity GUI/Nautilus/GOME/Right click Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Narayansamy S (vazhavandan) Partner organization: openSUSE.org Description: Need a file Integrity checker like a GUI pop up or right click menu in nautilus/gnome which calculates checksum so that file downloaded file intergity check can be done on the fly -- openSUSE Feature: https://features.opensuse.org/310883

1 3

[New: openFATE 310913] Add YAST module to set up multiseat installations
by fate_noreply＠suse.de 19 Dec '16

19 Dec '16

Feature added by: Matthias Schünemann (wodenhof) Feature #310913, revision 1 Title: Add YAST module to set up multiseat installations openSUSE-11.4: Unconfirmed Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Matthias Schünemann (wodenhof) Partner organization: openSUSE.org Description: Set up a computer with a YAST module to run with multiple graphic cards, mice and keyboards for multiple users at once. The module would allow the administration of "working places". Currently one can reach sessions only on one screen via the function keys (F7 - F12). I suggest a module which lets the administrator bundle the devices into "seats", i.e. physically separated working places each with their own mouse, keyboard and display. Common use of DVD-reader/burner or card readers could be allowed, USB-sticks could e.g. get assigned hubs. Somebody (Chris Tyler) already started here: https://fedoraproject.org/wiki/Features/Multiseat (https://fedoraproject.org/wiki/Features/Multiseat) CPU-power is abundant in modern machines, so one machine has enough for the easier tasks (browsing, text input etc.) of a whole family. I'd appreciate an easy set up with this feature. Business case (Partner benefit): openSUSE.org: Use of this power in any family's home would be a powerful demonstration of this OS's qualities. It would save money, particularly nice for families with tight budgets and in developing countries. When multi seat set-ups get more common the feature could be extended to virtual machines, i.e. one machine per seat. Those could be connected (via a virtual net / sockets ...) and run future multi-player games... -- openSUSE Feature: https://features.opensuse.org/310913

1 9