Feature added by: Matthew Ayres (Solar_Granulation)
Feature #309024, revision 1
Title: Inclusion of swftools
Package Wishlist: Unconfirmed
Priority
Requester: Desirable
Requested by: Matthew Ayres (solar_granulation)
Description:
As the project website says:
"SWFTools is a collection of utilities for working with Adobe Flash files (SWF files). The tool collection includes programs for reading SWF files, combining them, and creating them from other content (like images, sound files, videos or sourcecode). SWFTools is released under the GPL."
Of course many say that Flash is becoming obsolete, but it is still widely used and very popular. Not only is it used in web desgin, but also as a platform for Multitouch development. Swftools, being open and stable, would make an excellent addition to the openSUSE standard repository.
--
openSUSE Feature:
https://features.opensuse.org/309024
Feature added by: Eric Renfro (psi-jack)
Feature #309954, revision 1
Title: keepalived
Package Wishlist: Unconfirmed
Priority
Requester: Desirable
Requested by: Eric Renfro (psi-jack)
Partner organization: openSUSE.org
Description:
keepalived is used for monitoring real servers within a Linux Virtual Server (LVS) cluster. keepalived can be configured to remove real servers from the cluster pool if it stops responding, as well as send a notification email to make the admin aware of the service failure.
Business case (Partner benefit):
openSUSE.org: keepalived is a very nice, simple, and yet powerful failover monitoring system as well as LVS director engine. pacemaker can be nice, but in many cases it may be too much for the job needed, this is where keepalived can come in and make a network router with backup completely available.
--
openSUSE Feature:
https://features.opensuse.org/309954
Feature added by: Vincent Untz <vuntz(a)novell.com>
Feature #305640, revision 1, last change by
Title: Replace gnomesu by something more modern
openSUSE-11.2: New
Priority
Requester: Important
Requested by: Vincent Untz (vuntz)
Partner organization: openSUSE.org
Description:
gnomesu is kind of obsolete and unmaintained.
In the world of PolicyKit, we could use the new PolicyKit-aware gksu, or the adminkit stuff done by Rodrigo.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=305640
Feature added by: Darryl Miles (dlmiles)
Feature #310338, revision 1
Title: Always create /root/autoyast.xml for every installation
openSUSE-11.4: Unconfirmed
Priority
Requester: Desirable
Requested by: Darryl Miles (dlmiles)
Description:
Distribution such as RHEL (and any of its blood line) always leave a file /root/anaconda.ks which can be used to repeat the installation via their anaconda/kickstart process.
The parallel to this with openSUSE is YaST2 and AutoYaST.
The feature request is asking that at the end of every installation in the home directory of the root user the necessary file or files are created to allow the user to repeast the installation with the same options.
If multiple files are needed then it maybe better provided as a single file using any archiver (tar/cpio/zip). Also making sure this format could be used directly with AutoYaST.
There should be a YaST2 option to disable the emitting of configuration but the default should be to enabled it just like with RHEL. The process of making the user use another program to create an autoyast.xml descriptor is no where near as efficient as running through the entire installation process once and knowing you always get a descriptor out at the end of it. Which you can then if you like open up the editor to modify. This has far superior usability IMHO.
If there are concerns over encoding hashed/encrypted passwords into the file then the generation of this installation configuration to file(s) in the root users home directory should have a tri-state value.
* Off (meaning do no create any files),
* On (meaning to create file(s) in the root home directory that would be necessary to perform the installation that just happened again with a new set of defaults and mostly unattended, however any security sensitive information such as passwords would not be included at all, this would be the new default for everyone),
* On with Passwords (meaning the same as On but any security senstive information would also be emitted in the best possible way to retain as much security as possible, for example the password hash is in the file no the plain text password).
--
openSUSE Feature:
https://features.opensuse.org/310338
Feature added by: Aris Karagiannidis (arkara)
Feature #307862, revision 1
Title: zypper parallel dowloading of packages
openSUSE-11.3: Unconfirmed
Priority
Requester: Important
Requested by: Aris Karagiannidis (arkara)
Partner organization: openSUSE.org
Description:
Now, i think that this is already done with apt.
What should happen is that zypper should download packages
concurrently and when it does download them all, then it should install them
Business case (Partner benefit):
openSUSE.org: Faster package management
--
openSUSE Feature:
https://features.opensuse.org/307862
Feature added by: Robert Xu (bravoall1552)
Feature #309996, revision 1
Title: zypper download speed up
openSUSE-11.3: Unconfirmed
Priority
Requester: Important
Requested by: Robert Xu (bravoall1552)
Partner organization: openSUSE.org
Description:
I think we should have zypper use aria2 or some similar program to allow 2 consecutive downloads at once.
While there is an option in zypp.conf, it does not work naturally with zypper and GUI tools.
Having 2 downloads at once can speed up installation rapidly.
For those who aren't in the DownloadInAdvance mode, maybe they can:
* download 2 at once, add them to install queue, and have the install queue process as soon as the first download is done.
Business case (Partner benefit):
openSUSE.org: Because Zypper is a little slow, and that's preventing a lot of packages from being installed in time. We should be able to have zypper as speedy as possible.
--
openSUSE Feature:
https://features.opensuse.org/309996
Feature added by: Ivar Nikolaisen (Quantumboredom)
Feature #313430, revision 1
Title: Safe snapper snapshot creation / restoration during boot / shutdown
openSUSE Distribution: Unconfirmed
Priority
Requester: Desirable
Requested by: Ivar Nikolaisen (quantumboredom)
Partner organization: openSUSE.org
Description:
Currently Snapper takes snapshots both when doing system changes using YaST / Zypper, and also automatically on a schedule. The problem with these snapshots is that system integrity is not guaranteed (i.e., a snapshot can be taken while a file is being written, leaving the file in a corrupted state upon restoring the snapshot). I propose a mechanism where snapper takes a snapshot upon system shutdown at a stage where the snapshot can be guaranteed to be consistent. This could for example be just like a timeline snapshot, except the description should highlight that it was taken at system shutdown.
It would also be very nice if it was possible to restore snapshots when booting (I believe Fedora is already working on something like this), but perhaps this should be a separate feature request?
Business case (Partner benefit):
openSUSE.org: It is obviously useful to have known-good restore points. Especially useful for the many users of proprietary display drivers (even more so if using Tumbleweed!).
--
openSUSE Feature:
https://features.opensuse.org/313430