November 2014 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 318196] Redesign YaST Storage Code
by fate_noreply＠suse.de 25 May '18

25 May '18

Feature added by: Arvin Schnell (aschnell) Feature #318196, revision 1 Title: Redesign YaST Storage Code Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: The structure of the target-map (holding almost all storage data in YaST) is outdated and not documented. Adding new features, e.g. use whole disk for filesystem, bcache, dm-cache or switching to and from partitions on MD RAID, is difficult and error-prone. Thus a redesign is required to be prepared for new features and make the software more robust. During hackweek I evaluated using the boost graph library for libstorage. The result was announced and is explained, see references. I consider the redesign to be mandatory but not for a specific version (although as soon as possible). Note: This feature is about a redesign, new functionality must by requested as individual feature requests. Relations: - Evaluation Project on GitHub (url: https://github.com/aschnell/libstorage-bgl-eval/wiki) - Announcment on yast-devel (url: http://lists.opensuse.org/yast-devel/2014-10/msg00045.html) -- openSUSE Feature: https://features.opensuse.org/318196

1 14

[New: openFATE 315060] Remove double configuration-posibilities (Yast/KDE)
by fate_noreply＠suse.de 22 Apr '18

22 Apr '18

Feature added by: Thomas Langkamp (tomtomme) Feature #315060, revision 1 Title: Remove double configuration-posibilities (Yast/KDE) openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thomas Langkamp (tomtomme) Partner organization: openSUSE.org Description: Examples: 1. For 12.2 (fresh install) I could configure ntp via yast and via kde, through different menus. The kde-method did not work the yast method worked. 2. The same for network: After a fresh 12.2 and 12.3 install manual-internet (no dhcp) connection failed until I used the Yast-network-module. A direct configuration through the KDE-configuration dialoge did not work. At cÂ´t (heise journal) I read that it even did not work for DHCP... 3. I could continue... Why all these double configuration possibilities? Please disable the one in KDE or the one in Yast (I know you can not tell KDE to stop developing those, because other distros do not have Yast, but for suse you could just disable them or remove the yast pendants, if thats ok for the other desktops like gnome etc.) Thanks, tomme -- openSUSE Feature: https://features.opensuse.org/315060

1 3

[New: openFATE 315059] Remove double configuration-posibilities (Yast/KDE)
by fate_noreply＠suse.de 22 Apr '18

22 Apr '18

Feature added by: Thomas Langkamp (tomtomme) Feature #315059, revision 1 Title: Remove double configuration-posibilities (Yast/KDE) openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thomas Langkamp (tomtomme) Partner organization: openSUSE.org Description: Examples: 1. For 12.2 (fresh install) I could configure ntp via yast and via kde, through different menus. The kde-method did not work the yast method worked. 2. The same for network: After a fresh 12.2 and 12.3 install manual-internet (no dhcp) connection failed until I used the Yast-network-module. A direct configuration through the KDE-configuration dialoge did not work. At cÂ´t (heise journal) I read that it even did not work for DHCP... 3. I could continue... Why all these double configuration possibilities? Please disable the one in KDE or the one in Yast (I know you can not tell KDE to stop developing those, because other distros do not have Yast, but for suse you could just disable them or remove the yast pendants, if thats ok for the other desktops like gnome etc.) Thanks, tomme -- openSUSE Feature: https://features.opensuse.org/315059

1 1

[New: openFATE 311089] Disable system bell by default if sound card is installed
by fate_noreply＠suse.de 21 Apr '18

21 Apr '18

Feature added by: Pieter De Decker (pdedecker) Feature #311089, revision 1 Title: Disable system bell by default if sound card is installed openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Pieter De Decker (pdedecker) Partner organization: openSUSE.org Description: One of the first things I do after installing openSUSE is disabling the system bell by adding this to ~/.inputrc: set bell-style none Its volume is needlessly high. The bell scares the hell outta me whenever it creeps up because I backspaced too much on the command line. My suggestion: disable the system bell by default, unless no sound card is installed. Business case (Partner benefit): openSUSE.org: It's a simple fix for something that has been bugging me forever. -- openSUSE Feature: https://features.opensuse.org/311089

1 7

[openFATE 308182] Create administrator tool for replicating OBS resources
by fate_noreply＠suse.de 20 Apr '18

20 Apr '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #308182, revision 1 Title: Create administrator tool for replicating OBS resources Buildservice: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: A tool for replicate defined projects from a remote OBS instance to a local instance would be helpfull. This should offer different levels of replication depth: * Just latest sources or including past source history (maybe with a date limiter) * Replicate binaries for :full tree ( to be able to bootstrap yourself ) or all binaries from package directories. The tools would be helpfull as CLI and/or as part of the admin web frontend. The remote instance should be access via the frontend api, while the local instance must be accessed via backend source and rep server (+ local frontend api for creating projects and packages). -- openSUSE Feature: https://features.opensuse.org/308182

1 3

[New: openFATE 310652] Have an Etherpad install on openSUSE infrastructure
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

Feature added by: Jos Poortvliet (jospoortvliet) Feature #310652, revision 1 Title: Have an Etherpad install on openSUSE infrastructure openFATE: Unconfirmed Priority Requester: Important Requested by: Jos Poortvliet (jospoortvliet) Partner organization: openSUSE.org Description: Currently the marketing team in particular makes use of lots of piratepad's to work collaboratively on articles, announcements, plans and other things. Wiki's don't offer the ease and real-time collaboration features needed so piratepad is perfect. Except that it isn't. Piratepad has some serious issues (see "Why do we want this?"). So we would like to have an Etherpad install on openSUSE infrastructure. Having our 'own' Etherpad instance on an openSUSE server would solve these issues. Even just having it as a SUSE Studio virtual image so it can be run somewhere would be good enough. In general, the openSUSE servers are pretty dependable and even when not, we know who to ping to solve problems. Use Case: Usecase would be pretty much half the work the marketing team does - writing announcements, articles, planning... Business case (Partner benefit): openSUSE.org: The current 'solution' to use Piratepad has a bunch of issues: Stability is a big one - Piratepad is down quite frequently, sometimes for a whole day, making our work difficult. Another serious issue is oversight. We can't see what pads we have, resulting in lost pads (and the work we put into them) and duplication of efforts. Then there is the lack of control. All piratepads are fully public - but we have sometimes things we'd like to keep under the lid like announcements we are working on, articles, board things etcetera. Etherpad provides access control which would help us immensely. Part of that control issue is the ability (or lack there off) of deleting pads - we can't do that on Piratepad. Finally, we don't OWN Piratepad. If it went away RIGHT NOW, we would loose MANY important articles, announcements and other good work. It would be a small disaster for the marketing team and it's getting potentially worse as we do more and more work on Etherpad. -- openSUSE Feature: https://features.opensuse.org/310652

1 19

[New: openFATE 312804] Hermes integration on the openSUSE wiki
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

Feature added by: Sebastian Oliva (tian2992) Feature #312804, revision 1 Title: Hermes integration on the openSUSE wiki openSUSE Infrastructure: Unconfirmed Priority Requester: Desirable Requested by: Sebastian Oliva (tian2992) Partner organization: openSUSE.org Description: An extension to the wiki software, to add Hermes support to the Wiki software, enabling digests and advanced notifications to the Watch List. Use Case: Anna edited the openSUSE wiki, adding a tutorial to configure repositories. She subscribes to the page and enables notifications. When John edits the page, Anna gets a twitter notification, letting her know, there was an edition in the page. -- openSUSE Feature: https://features.opensuse.org/312804

1 2

[New: openFATE 308899] allow repository specification in project meta xml
by fate_noreply＠suse.de 27 Feb '18

27 Feb '18

Feature added by: Adrian Schröter (adrianSuSE) Feature #308899, revision 1 Title: allow repository specification in project meta xml Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We have currently to set Type, Repotype and Patterntype in project conf data. That makes it hard to add an images repo easily with a gui that works. Before creating code interpreting the prjconf, I would like to suggest to extend repository xml element to define this as default. Opinions ? Feature is completed when we have an "Add kiwi images repository" button. -- openSUSE Feature: https://features.opensuse.org/308899

1 4

[New: openFATE 308619] Provide Kwallet integration for Firefox
by fate_noreply＠suse.de 25 Feb '18

25 Feb '18

Feature added by: Jimmy Berry (boombatower) Feature #308619, revision 1 Title: Provide Kwallet integration for Firefox openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Jimmy Berry (boombatower) Description: I have wanted such a feature for sometime and recently discoved https://addons.mozilla.org/en-US/firefox/addon/49357 via identi.ca talk. Since openSUSE 11.2 includes KDE integration for Firefox, I think this would be a great thing to either add/finish/polish or just defaultly include as part of integration. -- openSUSE Feature: https://features.opensuse.org/308619

1 3

[New: openFATE 310922] central system user registry
by fate_noreply＠suse.de 12 Feb '18

12 Feb '18

Feature added by: Ludwig Nussel (lnussel) Feature #310922, revision 1 Title: central system user registry openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: Once upon a time all systems users were defined in aaa_base via the default /etc/passwd file. When the uid space below uid 100 got too small a new dynamic range between 100 and 499 was introduced. So nowadays packages dynamically create a user in %pre which gets a random uid in this range. Disadvantage: uids are different on every system. Usually this is not a problem but for programs that export files over the network it is. TV recordings made by VDR for example. useradd has a --preferred-uid option for such cases. It's possible to specify a uid and useradd tries to use it. If it's already taken another one is chosen. Thefore I'd propose to leverage that feature: - introduce a central uid registry for system users, e.g a file in aaa_base - lower SYSTEM_UID_MAX (/etc/login.defs) to e.g. 349 and assign "preferred uids" in the rage 350-499. - change useradd calls in packages to a macro that transparently decides whether a preferred uid needs to be used. Use Case: - two systems running vdr, one for recording, the other one for playback on a TV want to share recordings via nfs. -- openSUSE Feature: https://features.opensuse.org/310922

1 15