December 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307556] Provide an easy way to find Factory devel package with unsubmitted project.diff
by fate_noreply＠suse.de 10 May '10

10 May '10

Feature added by: Ralf Haferkamp (rhafer) Feature #307556, revision 1 Title: Provide an easy way to find Factory devel package with unsubmitted project.diff Buildservice: Unconfirmed Priority Requester: Important Requested by: Ralf Haferkamp (rhafer) Description: It would be very helpful to have an overiew in the webfrontends that shows which factory-devel packages are "out-of-sync" with factory. I.e. they have uncommited (not submitted to Factory) projects.diffs in their file list. This could e.g. be part of the "My Projects" page. (Or hermes could sent regular notification about uncommited changes.) -- openSUSE Feature: https://features.opensuse.org/307556

1 9

[openFATE 307915] Project source link (forwarder)
by fate_noreply＠suse.de 03 May '10

03 May '10

Feature added by: Adrian Schröter (adrianSuSE) Feature #307915, revision 1 Title: Project source link (forwarder) Buildservice: Candidate Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Description: For preparing maintenance updates we need a way to allow references to the :Update projects, even if a certain package does not exist there yet. This need to work for source check outs and source links. However, not for building (:Update shall not build all packages by default). A proposal to support this would be via a so called "project source link" with additional flags. Something like this for the project xml meta data: <link project="$PROJECT" /> This could be later extended to enable entire shadow builds (aka our former BETA distributions: <link project="$PROJECT"> <build repository="$REPOSITORY" arch="$ARCH"> </link> -- openSUSE Feature: https://features.opensuse.org/307915

1 5

[New: openFATE 308261] Include Bibus, a bibliography tool that interacts with Openoffice via UNO
by fate_noreply＠suse.de 26 Apr '10

26 Apr '10

Feature added by: Sven Burmeister (rabauke) Feature #308261, revision 1 Title: Include Bibus, a bibliography tool that interacts with Openoffice via UNO Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Description: OpenOffice lacks a decent bibliography support which is mandatory for scientific writing. Bibus is a python tool available for all platforms, i.e. Windows users can use the same tool when switching to Linux. It can interact with Openoffice via the UNO api, i.e. it does not only export its data, but inserts it into the OO document. It can even be used with a central database, i.e. for companies that want to share their bibliogrphic data. The projects website is: http://bibus-biblio.sourceforge.net/ -- openSUSE Feature: https://features.opensuse.org/308261

1 4

[New: openFATE 308468] Video Podcast help icon (to internet page) for new install
by fate_noreply＠suse.de 16 Apr '10

16 Apr '10

Feature added by: Lee Matheson (oldcpu) Feature #308468, revision 1 Title: Video Podcast help icon (to internet page) for new install openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Lee Matheson (oldcpu) Description: Link on desktop (or part of help menu) to general openSUSE Linux podcasts prepared by SuSE-GmbH or community members. The video podcasts should be very basic tutorials in openSUSE linux. They do not have to be openSUSE version specific, nor openSUSE linux specific. By making them general they can stay current for several openSUSE releases, reducing the maintenance work load. Video Podcasts should be done in an "open" format/codec such that they can be run immediately after a fresh install. Subjects could include: * OpenSUSE basics tour (yast, internet community ... ) * KDE desktop tour * Gnome destkop tour * openSUSE software Package Management * Linux file system hiarchy * Linux terminal/bash shell introduction Of course the above podcasts would have to be created first :) -- openSUSE Feature: https://features.opensuse.org/308468

1 1

[openFATE 306502] Disable automount
by fate_noreply＠suse.de 14 Apr '10

14 Apr '10

Feature added by: Jakub Rusinek (liviopl) Feature #306502, revision 1 Title: Disable automount openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jakub Rusinek (liviopl) Description: When repartitioning HDD, automount can hurt. The same when installing system. At least for partitioners and installers "lifetime", automount should be disabled. -- openSUSE Feature: https://features.opensuse.org/306502

1 5

[New: openFATE 308474] Only install a recommended subset of screensavers by default
by fate_noreply＠suse.de 07 Apr '10

07 Apr '10

Feature added by: Vincent Untz (vuntz) Feature #308474, revision 1 Title: Only install a recommended subset of screensavers by default openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: At the moment, a default openSUSE install gets all the screensavers from xscreensaver. While it's quite nice, for most people, that's way too much. I believe a selection of 10-15 screensavers should be made, and then the xscreensaver package should be split in: * xscreensaver: would contain the binary, and its data files * xscreensaver-recommended: would contain the recommended screensavers * xscreensaver-extras: would contain all the other screensavers Note that we'll also need to adapt the gnome-screensaver packaging for this, but that should be easy. Also, this would make it possible to install xscreensaver-recommended without xscreensaver itself, which is useful for GNOME, but probably also for KDE. -- openSUSE Feature: https://features.opensuse.org/308474

1 2

[New: openFATE 308598] Samba Description Field
by fate_noreply＠suse.de 31 Mar '10

31 Mar '10

Feature added by: Malvern Star (Solaris444) Feature #308598, revision 1 Title: Samba Description Field openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Malvern Star (solaris444) Description: The Samba Server YaST UI should allow users to edit the description field that is visible to the network for each machine. The Samba Server configuration component in YaST allows users to set shares, workgroup, netbios identifier and WINS server for the machine, however it does not allow the user to set the description field. The is somewhat inconvenient as the default description is always the Samba version string, meaning that Windows machines (which display the description string FIRST when viewing the network) will group all Linux machines on the network together. It would be helpful to be able to set this field without enabling swat or editing the Samba config file. -- openSUSE Feature: https://features.opensuse.org/308598

1 2

[openFATE 307552] Cups 1.4 RPM's
by fate_noreply＠suse.de 30 Mar '10

30 Mar '10

Feature added by: Dean Hilkewich (deanjo13) Feature #307552, revision 1 Title: Cups 1.4 RPM's Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Dean Hilkewich (deanjo13) Description: It would be nice if the cups packages could be upgraded to 1.4 in 11.2. I realize it's a bit late in the development stage but it just went final on Aug 28th and does carry a large number of improvements. http://www.cups.org/documentation.php/whatsnew.html -- openSUSE Feature: https://features.opensuse.org/307552

1 5

[New: openFATE 308407] Simplify debranding in Kiwi and SUSE Studio
by fate_noreply＠suse.de 29 Mar '10

29 Mar '10

Feature added by: M. Edward (Ed) Borasky (znmeb) Feature #308407, revision 1 Title: Simplify debranding in Kiwi and SUSE Studio openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: M. Edward (Ed) Borasky (znmeb) Description: I build appliances based on openSUSE. I've done some of them in SUSE Studio, and some of them on my workstation using Kiwi, VirtualBox OSE, Xen or VMware Workstation. I am starting to get some that I'd like to distribute. In order to distribute them, I need to be able to re-brand some packages - remove the openSUSE branding and replace it with upstream branding or my own. See http://en.opensuse.org/Making_a_SUSE_based_distribution (http://en.opensuse.org/Making_a_SUSE_based_distribution) for the details. I've tried to do this using SUSE Studio, since it's a lot more convenient, but I have been unable to create a de-branded appliance because of package conflicts in the built-in patterns. See http://n2.nabble.com/Branding-distributing-etc-tp4030350p4030350.html (http://n2.nabble.com/Branding-distributing-etc-tp4030350p4030350.html) The essential difficulty, both in SUSE Studio and in Kiwi is that the base patterns which define package lists contain unremovable branding packages. For these patterns, I need to 1) Find a list of all the packages in the patterns and their dependencies 2) Acquire the source for the branded packages, de-brand them at the source level, and then rebuild binary RPMs. That's a significant amount of labor with no value added to the recipients of the redistributed software. So what I am requesting is that the openSUSE project 1) Make the base patterns ("default", "kde4", "gnome", "xfce", etc.) branding-free, and create a new "branding-openSUSE" pattern to replace the upstream branding with openSUSE branding, and 2) Create de-branded RPMs for the few packages that don't have a "branding-upstream" equivalent. I haven't done the research to identify all of these, but I believe most of them are in the YaST infrastructure. -- openSUSE Feature: https://features.opensuse.org/308407

1 4

[New: openFATE 308344] archive mounter
by fate_noreply＠suse.de 24 Mar '10

24 Mar '10

Feature added by: Andrew Jorgensen (ajorgensen) Feature #308344, revision 1 Title: archive mounter openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Andrew Jorgensen (ajorgensen) Description: GVFS supports mounting archives like iso, zip, tar.gz, etc. Making a menu entry to mount archives is trivial. Ubuntu has had this for a while now and it's very handy. -- openSUSE Feature: https://features.opensuse.org/308344

1 3

[openFATE 307423] clone_system client should accept a list of modules
by fate_noreply＠suse.de 24 Mar '10

24 Mar '10

Feature added by: Uwe Gansert (ug) Feature #307423, revision 1 Title: clone_system client should accept a list of modules openSUSE-11.2: New Priority Requester: Mandatory Requested by: Uwe Gansert (ug) Description: the clone_system client that was actually invented only for AutoYaST internal purposes is used quite often by customers too on the command line. Currently the client reads the list of modules to clone from the control.xml file. It would be nice if that list could be passed via command line too. -- openSUSE Feature: https://features.opensuse.org/307423

1 3

[openFATE 307424] invent an "ask"-rule for AutoYaST
by fate_noreply＠suse.de 24 Mar '10

24 Mar '10

Feature added by: Uwe Gansert (ug) Feature #307424, revision 1 Title: invent an "ask"-rule for AutoYaST openSUSE-11.2: New Priority Requester: Mandatory Requested by: Uwe Gansert (ug) Description: two customers had an idea for a new feature for the rule-mechanism for AutoYaST. It would be nice if AutoYaST could ask for the files to merge. So that it looks which XML snippets are available and presents them in some kind of dialog to choose from. -- openSUSE Feature: https://features.opensuse.org/307424

1 3

[openFATE 306192] Make BuildService accessible for anonymous users
by fate_noreply＠suse.de 22 Mar '10

22 Mar '10

Feature added by: Michal Vyskocil (mvyskocil) Feature #306192, revision 1, last change by Title: Make BuildService accessible for anonymous users Buildservice: Unconfirmed Priority Requester: Important Requested by: Michal Vyskocil (mvyskocil) Description: We hides many useful information about our distribution behind a Novell login, which makes a participation harder. Other distributions are much more opened even for anonymous users, so you can browse source codes, patches, changelogs, build logs, ... even if you are an anonymous users. We should be opened as much as possible if we want to be a community based distribution. Some examples: * Fedora CVS (http://cvs.fedoraproject.org/viewvc//) expose all Fedora packages with full history and for anonymous users * kojibuild info (http://koji.fedoraproject.org/koji/buildinfo?buildID=81815) - you have a full access to building informations from koji system and some of them are not available for OBS users at all. * Debian changelog browsing (http://packages.debian.org/changelogs/pool/main/c/cdbs/cdbs_0.4.52/changelog) Debian offers a changelog browsing (they don't use a centralized VCS) without registration. * lintian reports (http://lintian.debian.org/maintainer/build-common-hackers@lists.alioth.debi…) you can see a lintian issues for every package. * Debian build log (http://buildd.debian.org/pkg.cgi?pkg=libmatthew-java) Debian also offers an access to a build log of package. * Gentoo package information (http://packages.gentoo.org/package/app-office/nostaples?ts=2009-03-11T05:57…) Gentoo offers many information about package Those examples are only for illustrate of other approaches. I don't try to tell we must implement CVS because Fedora has it. And some issues like an alternative of Gentoo package view should be implemented in upcoming Software Portal. We should publish (at least for openSUSE:* projects) sources of packages and a build logs. -- openSUSE Feature: https://features.opensuse.org/306192

1 25

[New: openFATE 308453] Integrate patch (update) into software management module
by fate_noreply＠suse.de 15 Mar '10

15 Mar '10

Feature added by: Todd R (TheBlackCat) Feature #308453, revision 1 Title: Integrate patch (update) into software management module openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Todd R (theblackcat) Description: Currently there are two different modules for managing software, the software management module and the online update module. They are mostly the same in terms of the user interface, you can search and install software, browse patterns, groups, repositories, and more or less do most common package management tasks from both. The only major differences that I can see are that the software management module does not let you install patches, the online update module has an extra menu (patch, which just has duplicates of most of the actions in the "package" menu), and online update does not display as much information when doing the installation (like a remaining time estimate). I think this is a fairly redundant approach, there is really no reason I can think of why the software management module can't have the patches tab, and why patches can't use the same menu as packages since they have mostly the same items. So I think combining them into a single module would be more efficient and easier to maintain. You could still have the two modules listed in YaST if you want, clicking on the "software managment" module would just start you off in the search tab while the "online update" module would start you off in the patches tab. But I think it would be better still if you just had one module. When the software management module opens it checks if there are any patches, if there are it displays them and if not it goes straight to the "search" tab (or your last-used tab). -- openSUSE Feature: https://features.opensuse.org/308453

1 1

[openFATE 306852] YaST2 screen title needs a machine-name in it
by fate_noreply＠suse.de 15 Mar '10

15 Mar '10

Feature added by: Greg Riedesel (Gracal) Feature #306852, revision 1 Title: YaST2 screen title needs a machine-name in it openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Greg Riedesel (gracal) Description: The nomenclature, "[YaST control panel] @ [machine name]' is very useful for figuring out which window belongs to which server. Especially if the managing workstation is also openSUSE. Formerly Bug 385625 Use Case: When managing openSUSE servers over X-forwarding via SSH, it is possible to have multiple YaST screens up at the same time, each belonging to a different remote server. Having a way to differentiate between YaST instances in the title-bar will reduce confusion, and help avoid config mistakes. -- openSUSE Feature: https://features.opensuse.org/306852

1 5

[openFATE 308204] Shibboleth web identity service
by fate_noreply＠suse.de 10 Mar '10

10 Mar '10

Feature added by: Markus Kuhn (m_kuhn) Feature #308204, revision 1 Title: Shibboleth web identity service Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Markus Kuhn (m_kuhn) Partner organization: openSUSE.org Description: Shibboleth (http://shibboleth.internet2.edu/) is currently (2009) being rolled out as the standard federated single-signon web user-authentication system in academic institutions in the UK, US, and many other countries. With it, web servers (especially at universities) can easily leave user authentication and authorization to the existing/emerging Shibboleth infrastructure. Of interest to: website operators, especially at universities Licence: Apache 2.0 It may be a good idea to split the Shibboleth Service Provider and the Shibboleth Identity Provider functions into two seperate RPMs, as the former will be used by a large number of sites, whereas the latter only by a small number (typically one per University). Test Case: https://sp.testshib.org/ Use Case: http://shibboleth.internet2.edu/uses.html Business case (Partner benefit): openSUSE.org: Shibboleth is security-critical, runs a server, is integrated with Apache, and depends on having very recent versions of a number of XML, SAML, and crypto libraries installed. Therefore it is not entirely trivial to install and maintain for every casual website administer and thus it would be extremely useful if you could add it as a standard package to the openSUSE and SLES distributions. -- openSUSE Feature: https://features.opensuse.org/308204

1 1

[openFate 305104] Provide possibility to configure WEP/WPA/WPA2/... at installation
by fate_noreply＠suse.de 09 Mar '10

09 Mar '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305104, revision 1, last change by Title: Provide possibility to configure WEP/WPA/WPA2/... at installation openSUSE-11.1: New Priority Requester: Desirable Requested by: Jim Creech <jacreech(a)suddenlink.net> Partner organization: openSUSE.org Description: It is possible to configure a network in the first stage installation but it is only possible to select DHCP or Static + configure proxy. It is impossible to configure a secure wireless connection. See also: Bug 293609 (https://bugzilla.novell.com/show_bug.cgi?id=293609) - No provision for entering WEP at installation -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305104

1 9

[New: openFATE 308384] Maven support
by fate_noreply＠suse.de 08 Mar '10

08 Mar '10

Feature added by: dilbert elbonia (100le) Feature #308384, revision 1 Title: Maven support Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: dilbert elbonia (100le) Partner organization: openSUSE.org Description: It would be great if we could install maven from the official repositories. Business case (Partner benefit): openSUSE.org: Maven is becoming more and more popular tool for java (and not only java) development. -- openSUSE Feature: https://features.opensuse.org/308384

1 2

[openFATE 306379] Use rsync when refreshing repositories
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Piotrek Juzwiak (BenderBendingRodriguez) Feature #306379, revision 1, last change by Title: Use rsync when refreshing repositories openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Piotrek Juzwiak (benderbendingrodriguez) Description: It would be a great idea to use rsync when refreshing repositories, one of the bad things is the refresh speed. It gets worse when people have many repositories. I'm not sure but it already compares if something has changed in the repo but to speed things up it would be great to use rsync. -- openSUSE Feature: https://features.opensuse.org/306379

1 14

[openFATE 307139] Enable KMS for Intel Graphics cards
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Kshitij Kulshreshtha (polyconvex) Feature #307139, revision 1 Title: Enable KMS for Intel Graphics cards openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Kshitij Kulshreshtha (polyconvex) Description: Since in the Intel Graphics Release 2009Q2 kernel modesetting is the recommended method, please enable CONFIG_DRM_I915_KMS in the kernel config. In the current factory kernel (August 03) CONFIG_DRM_RADEON_KMS is set even though the code is considered unstable and depends on CONFIG_STAGING, however the more stable and recommended CONFIG_DRM_I915_KMS is not set. Please enable this option too. -- openSUSE Feature: https://features.opensuse.org/307139

1 17

[New: openFATE 308592] Include KDE 4.5 in opensuse 11.3
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: jimbo bigcreed (Dimble_ThriceFoon) Feature #308592, revision 1 Title: Include KDE 4.5 in opensuse 11.3 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: jimbo bigcreed (dimble_thricefoon) Description: both are currently due in July, i feel 11.3 should include 4.5. discuss. -- openSUSE Feature: https://features.opensuse.org/308592

1 9

[New: openFATE 308426] Update to reiser4 on opensuse 11.3x
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Glenn Doig (doiggl) Feature #308426, revision 1 Title: Update to reiser4 on opensuse 11.3x openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: <pre> see announcement from http://lizards.opensuse.org/2009/11/15/reiser4-for-opensuse-11-2/ built rpms http://download.opensuse.org/repositories/home:/dmitry_serpokryl:/drivers/o… http://download.opensuse.org/repositories/home:/dmitry_serpokryl:/drivers/1… other http://reiser4.wiki.kernel.org/index.php/Main_Page </pre> -- openSUSE Feature: https://features.opensuse.org/308426

1 6

[openFATE 308123] Camaras web
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: rosero mancera (leroman) Feature #308123, revision 1 Title: Camaras web openFATE: Unconfirmed Priority Requester: Important Requested by: rosero mancera (leroman) Description: Buen dia, me gustaria que open suse 11.2 , mejorara en el reconocimiento de camaras web, un ejemplo es que mi camara genius look 316 la probe en fedora y fue reconocida sin ningun problema, mientras espero la salida definitiva de suse 11.2 he probado tambienTrisquel 3.0 y el reconocimiento de la camara es mas que excelente, me pregunto porque no puedo utilizar la misma camara en OpenSuse mi distribución preferida?, no soy informatico ni se mucho del tema, pero quisiera que cuando instalo a Suse, me funcionara todo... estarian ustedes deacuerdo conmigo? la verdad quisiera ser de mas ayuda pero tengo pocos conocimientos de como realizar cambios sustanciales del mejor sistema que a mi parecer es open suse, si pudieran arreglar este reconocimiento de Harware en realidad seria mas que estupendo. Mil y Mil gracias por su atención y nuevamente felicitaciones Comunidad Open Suse. Leonardo Rosero. -- openSUSE Feature: https://features.opensuse.org/308123

1 2

[openFATE 307820] upgrade perl to 5.10.1
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Stefan Seifert (niner9) Feature #307820, revision 1 Title: upgrade perl to 5.10.1 openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Stefan Seifert (niner9) Description: The perl 5.10.1 maintenance release is now more than a month old and fixes many bugs and regressions (see http://search.cpan.org/~dapm/perl-5.10.1/pod/perl5101delta.pod ). It would be desirable to have it in openSUSE 11.2 -- openSUSE Feature: https://features.opensuse.org/307820

1 2

[openFATE 307492] "Report a Bug" icon for pre-release versions
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Kevin Dupuy (kdupuy9) Feature #307492, revision 1 Title: "Report a Bug" icon for pre-release versions openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Kevin Dupuy (kdupuy9) Description: Inspired in part by Windows 7's links to "report a problem", I think that to make it easier and quicker to access Bugzilla, we should include a desktop icon and panel launcher to open the Bugzilla "Enter new bug" page (https://bugzilla.novell.com/enter_bug.cgi?product=openSUSE%2011.2&format=gu…) (with the product already filled in, as above), with all pre-release (NOT FINAL) versions of 11.3 and beyond (or 11.2 if we have time) I've already created a .desktop file to do this, and use it on my own when testing 11.2/Factory. The file can be found here (http://kevinsword.com/images/Report%20a%20Bug.desktop) (choose Save Link As to download, or click to view the actual text in it). Please also see my blog post about this: http://lizards.opensuse.org/2009/08/23/1-click-bug-reporting/ Use Case: Joe Tester runs the latest pre-release version of openSUSE to help squash some bugs. He finds a bug that makes an application crash. He simply double-clicks on the Report a Bug icon or clicks on the panel launcher, and Firefox opens to Bugzilla, with the product already filled in. He can then search for the bug and file it if it doesn't already exist. Joe Tester now feels good about himself. -- openSUSE Feature: https://features.opensuse.org/307492

1 1