June 2010 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308960] Enhanced autofilter pop-up window
by fate_noreply＠suse.de 09 Dec '11

09 Dec '11

Feature added by: Kohei Yoshida (kohei_yoshida) Feature #308960, revision 1 Title: Enhanced autofilter pop-up window Requested by: Kohei Yoshida (kohei_yoshida) Description: Implement an enhanced autofilter pop-up window, by re-using the pop-up window from DataPilot. -- openSUSE Feature: https://features.opensuse.org/308960

1 5

[New: openFATE 309562] Incorporate osc vc into the build service web ui
by fate_noreply＠suse.de 05 Dec '11

05 Dec '11

Feature added by: Dave Plater (plater) Feature #309562, revision 1 Title: Incorporate osc vc into the build service web ui Buildservice: Unconfirmed Priority Requester: Important Requested by: Dave Plater (plater) Description: If small corrections to are made to packages, adding a build requirement for instance, using the web ui it is a waste to have to check out an entire package just to use osc vc to ensure change log consistency. The other way is to edit the changes file on line in which case mistakes may be made and it extends the time taken for an otherwise quick job. -- openSUSE Feature: https://features.opensuse.org/309562

1 2

[openFATE 306625] automatic email alias, irc cloak, lizards data generation on users.o.o
by fate_noreply＠suse.de 05 Dec '11

05 Dec '11

Feature added by: Hendrik Vogelsang (hennevogel) Feature #306625, revision 1 Title: automatic email alias, irc cloak, lizards data generation on users.o.o Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: To be able to maintain the list of @opensuse.org email aliases, freenode irc cloaks and lizards.o.o logins for members the openSUSE board is looking for a ruby hacker willing to implement automatic generation of aliases/cloaks in users.opensuse.org. users.o.o is a ruby on rails application. Each opensuse member has 2 email aliases (login(a)opensuse.org, forename.surname(a)opensuse.org) an freenode IRC cloak and a wordpress login to lizards.opensuse.org. At the moment this data is exported and imported manualy to the different systems. What we would need is a way to make this automatic and have the data changeable by the user. -- openSUSE Feature: https://features.opensuse.org/306625

1 10

[New: openFATE 308360] use lockdev
by fate_noreply＠suse.de 25 Nov '11

25 Nov '11

Feature added by: Ludwig Nussel (lnussel) Feature #308360, revision 1 Title: use lockdev openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: Ever since resmgr was dropped there is no way for unprivileged users to lock a device file such as /dev/ttyS0 even if the user has access to the device. A similar problem exists for usb devices in /dev/bus/usb. RedHat uses lockdev to solve the problem. It's a setgid 'lock' binary that manages the lock files. /var/lock is writeable by group 'lock' only. To be really useful the lockdev code needs to be cleaned up so a library is used to call the 'lockdev' helper binary. That way rpm would automatically catch the dependency. Any program accessing serial ports or usb devices as user could make use of lockdev, e.g. libgphoto2 minicom ppp sane-backends screen uucp ... References: http://cvs.fedoraproject.org/viewvc/devel/lockdev/ http://packages.debian.org/unstable/source/lockdev http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES -- openSUSE Feature: https://features.opensuse.org/308360

1 3

[openFATE 306188] request for RAID metadata version specification option in Partitioner's install interface
by fate_noreply＠suse.de 23 Nov '11

23 Nov '11

Feature added by: Arvin Schnell (aschnell) Feature #306188, revision 1, last change by Title: request for RAID metadata version specification option in Partitioner's install interface openSUSE-11.2: New Priority Requester: Desirable Requested by: pgnet _ (pgnet) Description: Allow setting of software raid superblock version in YaST. Relations: - request for RAID metadata version specification option in Partitioner's install interface (novell/bugzilla/id: 483973) https://bugzilla.novell.com/show_bug.cgi?id=483973 -- openSUSE Feature: https://features.opensuse.org/306188

1 12

[New: openFATE 309016] Request to be added as maintainer
by fate_noreply＠suse.de 14 Nov '11

14 Nov '11

Feature added by: Andreas Jaeger (a_jaeger) Feature #309016, revision 1 Title: Request to be added as maintainer Buildservice: Evaluation Priority Requester: Important Requested by: Andreas Jaeger (a_jaeger) Description: There's no way to ask to get added as maintainer/bugowner to a package. This could be also an implicit request when you create a new package and push it via submitreq from one project to another. Relations: - submitreq creates packages with no maintainers/bugowners (novell/bugzilla/id: 580104) https://bugzilla.novell.com/show_bug.cgi?id=580104 -- openSUSE Feature: https://features.opensuse.org/309016

1 2

[New: openFATE 308357] Replacement for Sax2 in 11.3
by fate_noreply＠suse.de 11 Nov '11

11 Nov '11

Feature added by: Tara Ikeda (TaraIkeda) Feature #308357, revision 1 Title: Replacement for Sax2 in 11.3 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Tara Ikeda (taraikeda) Partner organization: openSUSE.org Description: We need a replacement for sax2 in 11.3, as a safety measure for when auto configuration fails to detect certain monitors/keyboards/mice. Relying on the Desktop Environment for this is not the best idea, as some DE's or window managers dont provide config tools for what you might need to work. So I propose instead of relying on xrandr, Hal, devicekit or whatever there should be a GUI to configure graphics cards, mice, and keyboards without depending on the DE or a WM to provide a tool for the end user. I mention this as I have had KDE 4 fail to detect my resolutions and sometimes keyboard, luckily SAX2 is there to aid me but if its going the way of the dodo then I propose a relacement tool so that the end user wont have to make a xorg.conf and spend some time setting it up. It takes skill to make edits to a xorg.conf file and one can easily mess it up So having a helpful GUI tool is needed sometimes. Business case (Partner benefit): openSUSE.org: Because of new users mainly, because we dont want them to install openSUSE and have it fail to detect their proper monitor resolution and default to a much smaller one. The goal here is ease of use, but also to have a a safety net just in case. With openSUSE being more geared toward KDE a tool like Sax2 becomes even more needed. KDE4's monitor detection tool sucks, its always given me headaches in Ubuntu, in Mandriva, in many other KDE4 distros. It has no feature to remember monitor settings, nor does it do a good job with enabling my resolution. But i am not doing this just for me, many others have issues with KDE4's monitor tool -- openSUSE Feature: https://features.opensuse.org/308357

1 51

[openFATE 306578] Zypper integration with BuildService
by fate_noreply＠suse.de 02 Nov '11

02 Nov '11

Feature added by: Brent McConnell (everettemcconnell) Feature #306578, revision 1 Title: Zypper integration with BuildService Buildservice: Unconfirmed Priority Requester: Desirable openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Brent McConnell (everettemcconnell) Description: Integrate zypper with Buildservice so that users can install packages from BuildService directly from zypper without having to leave the commandline. -- openSUSE Feature: https://features.opensuse.org/306578

1 6

[New: openFATE 310046] yast2 progress report when downloadinadvance is set
by fate_noreply＠suse.de 28 Oct '11

28 Oct '11

Feature added by: Guillaume van Baalen (gvanbaalen) Feature #310046, revision 1 Title: yast2 progress report when downloadinadvance is set openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Guillaume van Baalen (gvanbaalen) Partner organization: openSUSE.org Description: This is a feature request for yast2. As of now, when the option "downloadinadvance" is set for package installation, the "perform installation" screen does not report correctly how the overall installation is progressing. What I mean is that there are two progress bars, one showing how much of the current package is being downloaded/installed, and one supposedly showing the overall process. So far, the "overall" progress bar stays at 0% while packages are being downloaded, and shows progress only when actually installing packages once they are all downloaded. I guess it shouldn't be too hard to have the "overall" progress bar go to 50% while packages are downloaded, then going from 50% to 100% while they are installed. Business case (Partner benefit): openSUSE.org: I want this because we have no clue right now as to whether the installation will take seconds or minutes/hours... -- openSUSE Feature: https://features.opensuse.org/310046

1 4

[New: openFATE 309205] Remove old kernel package only after the new one successfully booted
by fate_noreply＠suse.de 25 Oct '11

25 Oct '11

Feature added by: Michal Marek (michal-m) Feature #309205, revision 1 Title: Remove old kernel package only after the new one successfully booted openSUSE-11.2: New Priority Requester: Important Requested by: Martin Barry (supine) Description: When the kernel package is upgraded the old one is immediately removed leaving the currently running kernel with no modules. This breaks anything that requires modules until the user has an opportunity to reboot. The removal of the old package should be delayed till the system is rebooted into the new kernel. Reproducible: Always Steps to Reproduce: 1. Kernel package is upgraded 2. Try to run tcpdump Actual Results: 3. Get error about "interface not supported" and "unknown address family" 4. Reboot into new kernel 5. Try again to run tcpdump with identical arguements 6. tcpdump works as expected Expected Results: 3. tcpdump works as expected even before system is booted into new kernel Relations: - Kernel upgrade removes modules of running kernel subtly breaking the system until rebooted into new kernel (novell/bugzilla/id: 590496) https://bugzilla.novell.com/show_bug.cgi?id=590496 Discussion: #1: unknown user (2010-03-23 14:38:59) This is another symptom of needing the ability to clean up an old kernel after a successful boot. #2: (michal-m) (2010-03-23 16:02:38) (reply to #1) Let alone defining "successful boot" would be tough, but let's say if the user has logged in, there is at least some success (but e.g. the network might still not be working though). This would be the kernel packaging part. Then there would need to be some way to tell the package manager "now it's time to remove packages x,y and z, ask the user for confirmation either via the update applet, or as soon as the package manager is started". IMO it would be a nice feature, but I have no idea how difficult the zypp/yast/updater applet part would be. -- openSUSE Feature: https://features.opensuse.org/309205

1 12