September 2011 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 312337] clear /tmp-dir at bootup
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: M K (tux93) Feature #312337, revision 1 Title: clear /tmp-dir at bootup openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: M K (tux93) Partner organization: openSUSE.org Description: Please clear the /tmp-dir at boot-up per default. At the moment this has to be activated manually with every new installation, is there a reason for not doing this out of the box? -- openSUSE Feature: https://features.opensuse.org/312337

1 6

[New: openFATE 309487] Clean out X11 keyboard configuration in YaST
by fate_noreply＠suse.de 24 May '17

24 May '17

Feature added by: Jiří Suchomel (jsuchome) Feature #309487, revision 1 Title: Clean out X11 keyboard configuration in YaST Requested by: Jiří Suchomel (jsuchome) Developer: (Novell) Developer: (Novell) Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2-tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487

1 16

[New: openFATE 309353] Make hermes working on local OBS installations
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: Adrian Schröter (adrianSuSE) Feature #309353, revision 1 Title: Make hermes working on local OBS installations Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We need to * be able to run without iChain * package Hermes * configure it to be easy usable with OBS. -- openSUSE Feature: https://features.opensuse.org/309353

1 2

[openFATE 307597] Courgette
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: T. J. Brumfield (enderandrew) Feature #307597, revision 1 Title: Courgette openFATE: Unconfirmed Priority Requester: Important Requested by: T. J. Brumfield (enderandrew) Description: Utilize Courgette for binary diff packages. * This will save on bandwidth costs for Novell and mirrors. * This will make updating quicker and easier for end-users. * This will especially benefit users who have capped bandwidth for downloading updates from their ISPs. * By making the update process easier, it encourages users to stay up-to-date, making systems more secure. http://dev.chromium.org/developers/design-documents/software-updates-courge… (http://dev.chromium.org/developers/design-documents/software-updates-courge…) -- openSUSE Feature: https://features.opensuse.org/307597

1 7

[New: openFATE 309701] osc blame
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: Ludwig Nussel (lnussel) Feature #309701, revision 1 Title: osc blame Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Description: a feature like "osc blame" or "osc annotate" would be nice to find out who changed what and when -- openSUSE Feature: https://features.opensuse.org/309701

1 3

[openFATE 306528] Info banner for projects/packages
by fate_noreply＠suse.de 12 Mar '17

12 Mar '17

Feature added by: Jan-Simon Möller (dl9pf) Feature #306528, revision 1 Title: Info banner for projects/packages Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Jan-Simon Möller (dl9pf) Description: I'd propose to add an info banner (as on the monitor page - aka "Adrians Blog" ;) ) to the projects or even packages. This would allow the new groups of packagers to leave status messages right in place for the projects. -- openSUSE Feature: https://features.opensuse.org/306528

1 4

[New: openFATE 308685] Gnome Slab's More Applications not open another Window
by fate_noreply＠suse.de 11 Feb '17

11 Feb '17

Feature added by: Drew Kwashnak (dragonbite) Feature #308685, revision 1 Title: Gnome Slab's More Applications not open another Window Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Drew Kwashnak (dragonbite) Partner organization: openSUSE.org Description: In the Gnome Slab, if the Application has not been pinned to the Favorites you are forced to click "More Applications" and it opens up a Window. Maybe this could open a window like Windows XP does? Or can slide to the side like KDE 4 does? Something should be in place by default. Is there something called "Lancelot" which would apply here, or is just KDE? Business case (Partner benefit): openSUSE.org: The opened window may get lost in Windows, can be easily pushed behind something else or a pushy application that finally loads may pop-up over it and otherwise be annoying. -- openSUSE Feature: https://features.opensuse.org/308685

1 4

[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 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