July 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306897] PHP5.3
by fate_noreply＠suse.de 12 Aug '09

12 Aug '09

Feature added by: Ralf Becker (RalfBeckerKL) Feature #306897, revision 1 Title: PHP5.3 openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Ralf Becker (ralfbeckerkl) Description: I would love to see php5.3 included in the next openSUSE release (11.2). It' included many useful new features and openSUSE could be one of the first distros to include it. EGroupware (www.egroupware.org) is working with php5.3. Ralf -- openSUSE Feature: https://features.opensuse.org/306897

1 1

[openFATE 306462] Evaluate distributability of MPEG container codecs
by fate_noreply＠suse.de 12 Aug '09

12 Aug '09

Feature added by: Stanislav Brabec (sbrabec) Feature #306462, revision 1, last change by Title: Evaluate distributability of MPEG container codecs openSUSE-11.2: New Priority Requester: Desirable Requested by: Stanislav Brabec (sbrabec) Description: Due to uncertain legal status of MPEG stream and transport stream format decoders, its implementation is not part of our products. It would be nice to evaluate its legal status and make possible to decode MPEG2/4 videos using free video and audio codecs, for example Dirac video. Decoding a video requires finding of synchronization points (transport stream decoding, for a stream broadcasting) demultiplexing (stream decoding), then decoding video (passing video sub-stream to the video codec) and audio (passing sound sub-stream to the sound codec). It is known, that video codecs for MPEG-2/4 are part of MPEG LA (http://www.mpegla.com/) patent portfolio. It is known, that audio codecs for MPEG-2/4 are part of VIA Licensing (http://www.vialicensing.com/) and Thomson (http://mp3licensing.com/) patent portfolios. Legal status of the stream operations (transport stream synchronization, multiplexing and demultiplexing) is not known. It may be covered by some patents, but it is possible that there are no patents covering the stream container formats. References: https://bugzilla.novell.com/show_bug.cgi?id=483592 -- openSUSE Feature: https://features.opensuse.org/306462

1 2

[openFATE 306461] Evaluate distributability of AC3/A52
by fate_noreply＠suse.de 12 Aug '09

12 Aug '09

Feature added by: Stanislav Brabec (sbrabec) Feature #306461, revision 1, last change by Title: Evaluate distributability of AC3/A52 openSUSE-11.2: New Priority Requester: Desirable Requested by: Stanislav Brabec (sbrabec) Description: It would be nice to have AC3/A52 codecs enabled in our multimedia applications. Now it's disabled due to its uncertain legal status. The issue need a legal research. Some resources on the internet mention Dolby Laboratories, Inc. as a patent holder. But there is no mention of patents is on their web, no mention whether "AC-3" (which this particular decoder uses to indicate the decoding and downmix methods) is a trademark. Maybe Dolby owns patent to technology, maybe only copyright on implementation. It is also possible, that all relevant patens already expired. A/52 / AC3 is the ATSC's (Advanced Televison Systems Commitee's) audio codec standard for HDTV. Coincidentally, it's also used for DVDs. Also known as ATSC A/52, Digital Audio Compression (AC-3), United States Advanced Television Committee. References: https://bugzilla.novell.com/show_bug.cgi?id=483592 -- openSUSE Feature: https://features.opensuse.org/306461

1 2

[openFATE 306623] Integrate openFATE with Bugzilla
by fate_noreply＠suse.de 12 Aug '09

12 Aug '09

Feature added by: Andrés G. Aragoneses (knocte) Feature #306623, revision 1 Title: Integrate openFATE with Bugzilla openFATE: Unconfirmed Priority Requester: Important Requested by: Andrés G. Aragoneses (knocte) Description: I really don't understand why we are using openFATE instead of bugzilla for tracking features... But anyway, I think we can live in both worlds. Just make openFATE indeed by a Bugzilla frontend for enhancements and we're ready to go. Of course this requires a serious re-architecture of openFATE codebase, but it would please the community around both projects and it would merge feedback mechanisms. -- openSUSE Feature: https://features.opensuse.org/306623

1 4

[openFATE 306304] support "Obsolete this by another package"
by fate_noreply＠suse.de 12 Aug '09

12 Aug '09

Feature added by: Stanislav Brabec (sbrabec) Feature #306304, revision 1, last change by Title: support "Obsolete this by another package" openSUSE-11.2: New Priority Requester: Desirable Requested by: Stanislav Brabec (sbrabec) Partner organization: openSUSE.org Description: If third party wants to terminate a temporary branch of a package, which should is obsoleted by the mainline, adding Obsoletes: foo-old-branch into the mainline package is not an option (it's possible only for official packages). Support for an Obsolete tag counterpart initiated by the existing package would fix this situation. Example: Name: gimp-unstable Version: 2.5.23 Provides: gimp = %{version} ObsoleteBy: gimp >= 2.6 It would allow to provide mainline gimp packages without Obsoletes: gimp-unstable < 2.6 and even allow thitd partines to create temporary branches of packages. Business case (Partner benefit): openSUSE.org: Providing a significantly modified packages, that are known to be obsolete after upgrade to the -- openSUSE Feature: https://features.opensuse.org/306304

1 6

[openFATE 306533] automatic mailinglists for projects
by fate_noreply＠suse.de 11 Aug '09

11 Aug '09

Feature added by: Ludwig Nussel (lnussel) Feature #306533, revision 1 Title: automatic mailinglists for projects Buildservice: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: In order do coordinate between different people in a obs project itwould be nice if the buildservice automatically providedmaillinglists for each project. Something likePROJECTNAME(a)build.opensuse.org orPROJECTNAME+PACKAGE(a)build.opensuse.org. Mails to such addressesshoudl be forwarded to the project/package maintainers. That way theproject and user list would not have to be synced between the buildservice and a separate mailinglist manager.In a further step the build service could allow interested personsthat are not maintainers to sign up as well. -- openSUSE Feature: https://features.opensuse.org/306533

1 4

[openFATE 306503] LiveCD: Save installer settings in case of abort and rerun
by fate_noreply＠suse.de 11 Aug '09

11 Aug '09

Feature added by: Jakub Rusinek (liviopl) Feature #306503, revision 1 Title: LiveCD: Save installer settings in case of abort and rerun openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jakub Rusinek (liviopl) Description: Some people may encounter problems using installer and abort installation and rerun it later. Installer should remember settings to make their lives easier. -- openSUSE Feature: https://features.opensuse.org/306503

1 2

[openFATE 306366] Need ability to add business case during fate creation over web.
by fate_noreply＠suse.de 11 Aug '09

11 Aug '09

Feature added by: Joe Harmon (jaharmon) Feature #306366, revision 1, last change by Title: Need ability to add business case during fate creation over web. openFATE: Unconfirmed Priority Requester: Important Requested by: Joe Harmon (jaharmon) Description: When creating a new feature using fate.novell.com you have the ability to create a use case, test case, but not the ability to add a business case. Can we get that option added as well? -- openSUSE Feature: https://features.opensuse.org/306366

1 8

[openFATE 306595] Yast2 package manager: Save package selection on abort/cancel, recover/resume at
by fate_noreply＠suse.de 11 Aug '09

11 Aug '09

Feature added by: Vincent Petry (PVince81) Feature #306595, revision 1 Title: Yast2 package manager: Save package selection on abort/cancel, recover/resume at openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Vincent Petry (pvince81) Description: >From bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=506968 In the following cases, I happen to cancel a long yast installation/update:1) When I figure out I forgot to select a package for the big install/update.2) When I want to install a small package, but can't because yast is lockingrpm/zypper.3) When the internet connection is too slow, and I'd like to cancel it for nowand try again later.4) When I figure out the install will take longer than planned, and I want toturn the computer off and resume the install the next day.After each of these possible cases, I wish I could simply resume theinstallation from where it was stopped, or at least recover the packageselection I made, especially if it took me a long time to pick the packages.Steps to Reproduce:1. Open yast2 and "Install software"2. Spend some time select a lot of packages to install3. Click "Ok", and let the install run.4. At some time cancel the installation5. Restart Yast "Install software"Actual Results: Frustraction, because at step 5, the package selection is gone (especially ifyou took a long time to pick them), and even though some of the packages havealready been installed, the rest of the selection (from step 2) must be doneagain.Expected Results: When clicking on "Cancel" at step 4, yast saves the current package selection(or the to-be-installed list) into a temporary file.At step 5, when restarting yast, it tells that an install has been aborted andlets the user choose to recover the package selection from that point.Possible variations:1) When yast starts, don't ask anything, but provide a menu item or button toreload the backed-up package selection.2) When cancelling, the dialog could ask the user if he/she wishes to resumethe installation later. If yes, the package selection is saved, else it is justforgotten. -- openSUSE Feature: https://features.opensuse.org/306595

1 3

[openFATE 306596] Yast2 package manager: Select/taboo packages by feature/provides/hardware
by fate_noreply＠suse.de 11 Aug '09

11 Aug '09

Feature added by: Vincent Petry (PVince81) Feature #306596, revision 1 Title: Yast2 package manager: Select/taboo packages by feature/provides/hardware openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Vincent Petry (pvince81) Description: >From bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=506970 I have no bluetooth devices, so it would be convenient to prevent/taboo anybluetooth package to become automatically installed on the system. I have an intel GPU, but it didn't prevent the Xorg packages for radeon andunichrome to get automatically installed (suggested packages?). It would be convenient to have a way to select or taboo packages by feature orhardware availability. It could look like a metapackage or an option that couldbe selected, like: "Bluetooth -> Never install" "Graphics driver - Intel -> Selected" "Graphics driver - Radeon -> Never install" -- openSUSE Feature: https://features.opensuse.org/306596

1 3