Feature added by: Divan Santana (divansantana7)
Feature #310701, revision 1
Title: package byobu in an opensuse repository
openSUSE-11.4: Unconfirmed
Priority
Requester: Important
Requested by: Divan Santana (divansantana7)
Description:
Would be great if anyone using opensuse could zypper in byobu . Unfortunately it's not in any opensuse repo despite it being a great tool for administrating linux servers. I'm quite surprised this isn't already available for opensuse. Would be a nice addition for 11.4
--
openSUSE Feature:
https://features.opensuse.org/310701
Feature added by: Algimantas B (algyzas)
Feature #308445, revision 1
Title: Tor is not working out of box
Package Wishlist: Unconfirmed
Priority
Requester: Neutral
Requested by: Algimantas B (algyzas)
Description:
Let's say I installed tor, it is came alone, without privoxy. One should download it manually. And then if I try
:~> screen torify konqueror
hich: no tsocks in (/home/senis/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.) /usr/bin/torify: Can't find tsocks in PATH. Perhaps you haven't installed it?
[screen is terminating]
There is a guide http://en.opensuse.org/Privoxy_tor_squid how to setup it, I'll try it, but in some other distributions it works out of box like this.
--
openSUSE Feature:
https://features.opensuse.org/308445
Feature added by: Pete Clayson (Olmy)
Feature #309627, revision 1
Title: Enhance 'Safely Remove' to spin-down and power-off usb HDDs
openSUSE-11.3: Unconfirmed
Priority
Requester: Important
Requested by: Pete Clayson (olmy)
Description:
'Safely remove' should (as far as possible) allow for genuine safe removal of all media. Under certain other OSs, the 'safely remove' option on usb devices will... 1/ On usb pen drive with a power/activity led, switch it off (trivial nicety, but reassuring). 2/ On usb HDDs, spin down the disk and power off. This seems more important. There is some discussion about this, for example, http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.… (http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.…) I know that the latest version of Ubuntu does this and there is a script offered in the above link. However, the script, as it stands and run on my installation of OpenSUSE, does not seem to work (in the same way as WinXP or Ubuntu, anyway - my WD600D036 disk does not power off) despite the positive messages in verbose mode. Perhaps this is the CONFIG_USB_SUSPEND option mentioned?
--
openSUSE Feature:
https://features.opensuse.org/309627
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
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
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
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
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
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
Feature added by: Максим Муруев (slimy)
Feature #310464, revision 1
Title: Changer text console color
openSUSE-11.4: Unconfirmed
Priority
Requester: Important
Requested by: Максим Муруев (slimy)
Description:
Feature for yast change console color. And green color for console by default. I think green is opensuse color. For first console stay white, for best look boot log.
--
openSUSE Feature:
https://features.opensuse.org/310464