February 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305907] Support Update Repo Generation
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #305907, revision 1, last change by Title: Support Update Repo Generation Buildservice: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: The Build Service should offer update repos as repository channel. It is unclear right now, how we will carry in the extra update information texts. This should maybe designed together with a new changelog handling. -- openSUSE Feature: https://features.opensuse.org/305907

1 6

[openFATE 305859] Make installation history accessible from Yast GUI
by fate_noreply＠suse.de 05 Oct '11

05 Oct '11

Feature added by: Atri Bhattacharya (badshah400) Feature #305859, revision 1, last change by Title: Make installation history accessible from Yast GUI openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Atri Bhattacharya (badshah400) Description: As there is now (since openSUSE 11.1) a way to access the history of installed packages and their dependencies, it would be very useful if this history could be accessed from the Yast GUI. In the present implementation, zypper saves the history in a file (/var/log/zypp/history) which is very obscure. The history thus shown from yast should be able to show official-updates and non-official upgrades in different categories. Use Case: 1. Install new software, software not working (or not liked), look-up history start yast, look-up history, uninstall software and installed dependencies. 2. Online update, something goes wrong (upgraded software not working or something), look-up history to see recent updates and revert (all from yast). -- openSUSE Feature: https://features.opensuse.org/305859

1 8

[openFate 305593] Send notifications on link, branch and aggregate, show them in interface
by fate_noreply＠suse.de 23 May '11

23 May '11

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305593, revision 1, last change by Title: Send notifications on link, branch and aggregate, show them in interface Buildservice: New Priority Requester: Desirable Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: * send notification emails on link, branch and aggregate and/or show how many packages are linked to current package - that should reduce number of deletions which break other people's packages -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305593

1 3

[openFATE 305849] Provide the Ability to Natively Load More Than One Protocol Stack
by fate_noreply＠suse.de 14 Apr '11

14 Apr '11

Feature added by: Scott Couston (zczc2311) Feature #305849, revision 1, last change by Title: Provide the Ability to Natively Load More Than One Protocol Stack openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Description: Currently we natively support only an IP protocol stack, however I would hazard a guess that SLES has the ability to load IPX as well even as we have moved away from IPX. The Other Misgiving is that natively we cannot support more than an IP Protocol Stack and the lack of very good open/proprietary 3270 type Terminal Emulation shipped by default. I would be much happier if opensuse OR SLED could cope with another Protocol Stack - In Australia there is an enormous market we currently offer no solution to in only providing an IP Protocol Stack. In my home Country Australia All Federal Government- Health-Social Security- etc./All Banking Sectors/Most all Military Sectors/All State and Federal Law enforcement/Others (Thats a big Market Place) need to support a 3270 type Terminal Emulator and directly address SNA or X.25 or STLC comms. To compete we must at least be equal in the market place! The other mass market world wide particularly in the US are PC's that all Travel Agents use to make their bookings. World Wide They would use either Saber or Apollo or Galileo or Amadeus or Abacus - that about covers the whole World now. The issue all user face with M.S is that they most likely have a dedicated comms server as M.S cannot even load the required Protocol Stack. Depending on which Global System is used they mostly stick to their preferred stack and this could vary from ALC/STLC/X.25/IP/IPX/MATIP/etc..... Enough said - I think we all understand how we can better appeal to other huge markets if we invest in the functional ability to load more than just IPV4/6. I think we need to look far and wide at ALL Industry comms and we CAN do what MS cannot - We could easily bundle off a very very good 3270 type emulator and support SNA AND IP directly without the possible need for a comms servers packet stacking and promiscuous translation to IP. So we have 2 huge untaped Markets we cannot help right now and these are Australian - .GOV/.MIL and internal Banks and credit unions Global - The travel Industry is their varying, but constant use of say STLC/MATIP If we need to pull apart IP coms in the future for IPV6 this would be golden to support more than an IP Protocol only. __________________ -- openSUSE Feature: https://features.opensuse.org/305849

1 4

[openFATE 305842] Provide RPM Update Server to Update All openSUSE/SLED Workstations
by fate_noreply＠suse.de 14 Apr '11

14 Apr '11

Feature added by: Scott Couston (zczc2311) Feature #305842, revision 1, last change by Title: Provide RPM Update Server to Update All openSUSE/SLED Workstations openFATE: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Description: *Please be Patient - This is my First FATE request* Definitions in this Submission Workstation == Any openSUSE/SLED installation that functions without direct server support Installation Server == Any designated PC that holds a repository for the complete RPM's contained at time of software Release. Update Server == Any designated PC that holds a repository(s) that contain online update RPM's The 'Server' would be accessible by normal NFS... et al Services currently available. Current Situation The Installation of a PC with openSUSE/SLED requires a huge number of Online Updates a situation that may never change whilst development continues. The Installation of openSUSE has the ability to perform many NFS Installations at one time whilst being able to create 1 repository server for the entire Installation RPM's for future addition of features and groups not included in the base installation. Feature Request Along the same notion of an NFS Installation I propose that we an Installation Server or Other to be an Update Server which downloads ALL RPM updates as they become available. Each Workstation then selects Online Updates from the Update Server per chosen update check cycle period. In this way each workstation needs only to connect with the Update Server rather than each workstation downloading its required updates. This has the potential to cut update traffic by the number of workstations installed on a LAN and this weighed against the traffic of downloading ALL updates and the traffic on ALL Online update Server Repositories and Mirrors external to the LAN. The concept is notedly simple however this has a huge technical repercussion and link to FATE #120340. This concept is open for addition to FATE #120340 or it can stand alone at the discretion of Novell.DE Whilst this concept is created by the author the technical impact/problems will require much input from Novell.De and Suse.DE and the author. -- openSUSE Feature: https://features.opensuse.org/305842

1 10

[openFATE 305919] Hunspell as a system wide spellchecker
by fate_noreply＠suse.de 13 Apr '11

13 Apr '11

Feature added by: Stephan Kulow (coolo) Feature #305919, revision 1, last change by Title: Hunspell as a system wide spellchecker openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Kálmán Kéménczy (kkemenczy) Description: Why Hunspell? MySpell is not developed for quite a long time either in Mozilla and in OpenOffice.org. Hunspell is a fork of MySpell, it has great improvements is several ways, and fully backward compatible with MySpell. Main features: * Extended support for language peculiarities; Unicode character ncoding, compounding and complex morphology. * Improved suggestion using n-gram similarity, rule and dictionary ased pronounciation data. * Morphological analysis, stemming and generation. * Hunspell is based on MySpell and works also with MySpell dictionaries. * GPL/LGPL/MPL tri-license http://en.wikipedia.org/wiki/Hunspell http://hunspell.sourceforge.net/ Fedora project: http://fedoraproject.org/wiki/Releases/FeatureDictionary I also find a reference in the wishlist: http://en.opensuse.org/Wishlist_Various Relations: - Hunspell as a system wide spellchecker (novell/bugzilla/id: 354554) https://bugzilla.novell.com/show_bug.cgi?id=354554 Discussion: #1: Stephan Kulow (coolo) (2008-01-18 06:18:21) For reference: http://lists.opensuse.org/opensuse-factory/2008-01/msg00156.html #2: Petr Mladek (pmladek) (2008-01-18 07:20:54) * ** Bug 301458 has been marked as a duplicate of this bug. *** #3: Petr Mladek (pmladek) (2008-01-18 07:24:25) I'll do my best to do it for openSUSE-11.0. I am still busy with some other things. Or Michael, do you have time to look at it? #4: Kálmán Kéménczy (kkemenczy) (2008-01-27 12:17:56) patch for gtkspell (2.0.11): http://www.abisource.com/~dom/gtkspell-2.0.11-enchant.patch using this patch makes obsolate the gtkspell-gcc-err-fix.diff patch for gnome-spell 1.0.7: based on https://bugzilla.redhat.com/show_bug.cgi?id=426347 attached #5: Petr Mladek (pmladek) (2008-01-28 05:44:13) Adding gtkspell maintainer to CC. #6: Kálmán Kéménczy (kkemenczy) (2008-01-28 05:52:56) Created an attachment (id=191980) gnome spell check patch #7: Kálmán Kéménczy (kkemenczy) (2008-02-04 02:24:22) now available in Build Service (without dictionaries) http://download.opensuse.org/repositories/home:/kkemenczy/openSUSE_Factory/ #8: Ladislav Michnovič (lmich) (2008-02-04 02:49:51) Proposed patch for gtkspell has been added. #9: Kálmán Kéménczy (kkemenczy) (2008-02-04 12:38:37) dictionaries http://download.opensuse.org/repositories/home:/kkemenczy/openSUSE_Factory/… #10: Martin Schlander (cb400f) (2008-02-05 01:30:16) For Danish (da_DK) there's a dictionary being developed that's optimized for hunspell at http://www.stavekontrolden.dk http://www.stavekontrolden.dk/main/sspinputfiles/da_DK.dic http://www.stavekontrolden.dk/main/sspinputfiles/da_DK.aff I believe it's already a better option for hunspell than the dictionary from http://da.speling.org which is currently packaged. If not already it will become so soon as it's developed a lot more actively. Furthermore it's available under these licenses: GPL version 2 LGPL version 2.1 MPL version 1.1 Don't hesitate to ask if there are further questions. #11: Kálmán Kéménczy (kkemenczy) (2008-02-05 07:25:42) da_DK dictionary updated what is the next step? Someone had to decide to add it to the factory for further test. #12: Petr Mladek (pmladek) (2008-02-05 09:57:30) Lado. is there any chance that you could create the hunspell package for STABLE/FACTORY? I am still busy with some other stuff. #13: Ladislav Michnovič (lmich) (2008-02-06 02:49:05) O.K. I'll do it. It won't be in Alpha 2 because it is already under mastering process. It should appear in Alpha 3. #14: Ladislav Michnovič (lmich) (2008-02-19 06:14:25) Package is in Factory. #15: Kálmán Kéménczy (kkemenczy) (2008-02-21 03:48:22) imho several tasks left: * I am not sure that gnome-spell is Enchant-enable or not. ttps://bugzilla.novell.com/attachment.cgi?id=191980 * Sonnet's enchant backend backport to kdelibs / kspell ttp://bugs.kde.org/show_bug.cgi?id=154560 more info: https://www.redhat.com/archives/fedora-devel-list/2007-December/msg01493.ht… * Removing hunspell from Enchant ttps://bugzilla.redhat.com/show_bug.cgi?id=426402 * vim patch for hunspell: ttps://bugzilla.redhat.com/show_bug.cgi?id=219777 Should I create seperate bugs or we should keep them together here? #16: Ladislav Michnovič (lmich) (2008-02-21 04:13:53) (In reply to comment #15 from kalman kemenczy) > imho several tasks left: > > * I am not sure that gnome-spell is Enchant-enable or not. > https://bugzilla.novell.com/attachment.cgi?id=191980 > > * Sonnet's enchant backend backport to kdelibs / kspell > http://bugs.kde.org/show_bug.cgi?id=154560 > more info: > https://www.redhat.com/archives/fedora-devel-list/2007-December/msg01493.ht… > > * Removing hunspell from Enchant > https://bugzilla.redhat.com/show_bug.cgi?id=426402 > > * vim patch for hunspell: > https://bugzilla.redhat.com/show_bug.cgi?id=219777 > > Should I create seperate bugs or we should keep them together here? Adding kde-maintainers and gnome-maintainers to CC. Reassigning to vim maintainer. #17: Bjoern Jacke (bjacke) (2008-03-23 12:43:01) * ** Bug 237828 has been marked as a duplicate of this bug. *** #18: Bjoern Jacke (bjacke) (2008-05-01 15:57:47) - any news from vim maintainer on this? - enchant still needs rework or update - gnome-spell still needs enchant support added #19: Ladislav Michnovič (lmich) (2008-05-05 04:40:12) Adding JP. What do you think about this? See comment #15 and #18. #20: Matthias Koenig (makoenig) (2008-05-05 06:42:03) There are some problems with the vim patch. Currently we have /bin/vim-normal as default vim and /usr/bin/vim-enhanced. As the patch links against libhunspell which lives in /usr/lib{,64} we cannot link /bin/vim-normal against this. This would require either moving libhunspell to /lib{,64} which is not want we want (libhunspell itself also links against /usr/lib{,64}/libstdc++), or building /bin/vim-normal without syntax features at all (as the spell features seem to be tightly coupled to the general syntax features), which I also don't want. The best solution would be to provide a /bin/vim-tiny with minimal features and moving /bin/vim-normal to /usr/bin/vim-normal. But this will not happen for 11.0, as it will need yet another vim package restructuring. But, despite of this, yes, I think using hunspell is a good idea, as the vim dictionaries are derived from the OO ones and would otherwise waste a lot of space by duplicated data. Also worth mentioning, that this patch has been sent a year ago to upstream. While the idea has been appreciated, the patch has been rejected as is, AFAIK there has not been any work to improve this: http://www.mail-archive.com/vim-dev@vim.org/msg03252.html #21: Kálmán Kéménczy (kkemenczy) (2008-05-09 22:54:06) Created an attachment (id=214116) Gnome spell enchant patch here is the latest and greatest patch wirtten by Szilveszter Farkas from Ubuntu community, however this is created for gnome-spell 1.0.7, maybe it could use for 1.0.8. #22: Kálmán Kéménczy (kkemenczy) (2008-05-09 22:57:46) Rodrigo, could you check this patch to gnome-spell, please? https://bugzilla.novell.com/attachment.cgi?id=214116 Hopefully you are the maintainer for this packge. Many thanks, kalman #23: Stanislav Brabec (sbrabec) (2008-05-21 04:21:49) Patch applied (autogenerated files removed from it). #24: Jan Engelhardt (jengelh) (2009-01-11 18:53:30) There's a ton of spelling tools, why could not it have used one of the previously packaged ones, aka aspell or ispell? #25: Kálmán Kéménczy (kkemenczy) (2009-01-12 01:19:59) Jan, Hunspell already packaged in openSUSE. To answer your why's please read comment#1 #26: Jan Engelhardt (jengelh) (2009-01-12 03:06:41) >Hunspell already packaged in openSUSE But was not in 10.3. Hence the question. >comment#1 First comment says "Myspell". I asked about aspell/ispell. #27: Kálmán Kéménczy (kkemenczy) (2009-01-12 03:41:41) I think there are some reasons why choose Mozilla and OpenOffice.org and why Fedora decided as well, and slowly Ubuntu will go this way. In my comment#1 you should find the awesome summary: http://fedoraproject.org/wiki/Releases/FeatureDictionary Hunspell is not a question, the question is when? -- openSUSE Feature: https://features.opensuse.org/305919

1 3

[openFate 305587] Yast template for theming
by fate_noreply＠suse.de 01 Apr '11

01 Apr '11

Feature added by: Jakub Steiner <jimmac(a)novell.com> Feature #305587, revision 1, last change by Title: Yast template for theming openSUSE-11.2: New Priority Requester: Important Requested by: Jim McEldowney <jimmac(a)erie.net> Partner organization: openSUSE.org Description: To be able to skin the Yast installer properly, I would welcome the existence of a YCP template to include all of the widgets included in the actual installer. Business case (Partner benefit): openSUSE.org: Without such a testbed it's extremely hard and error prone to create new styling. In some cases it's impossible to see the implications of a style change until after it has been submitted to build and new distribution snapshot released. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305587

1 6

[openFATE 305876] Packages usage statistics
by fate_noreply＠suse.de 31 Mar '11

31 Mar '11

Feature added by: Michal Vyskocil (mvyskocil) Feature #305876, revision 1, last change by Title: Packages usage statistics openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Michal Vyskocil (mvyskocil) Description: Moved from Brainstorming_Prague (http://en.opensuse.org/BrainStorming_Prague#We_don.27t_know_which_packages_…) Problem: We don't know which packages users really use/have installed We cannot focus our interest on really important packages for our end-users, because we don't know which are important. Those popularity statistics could help us in many ways - for example bug priority of popular package should be higher, or we can decide move the package from/to Factory, ... Debian has a http://popcon.debian.org/ and popularity-contest package, so we should reuse an existing code. The pupularity-contest executable is a simple Perl script, which should be ported to rpm (replacing of dpkg calls by rpm alternative should be enough). Those package usage statistics could be integrated into Software Portal and to YaST comparing relative results for individual packages between openSUSE and Debian can give us a valuable information about the community structure (how many users use development tools etc.) -- openSUSE Feature: https://features.opensuse.org/305876

1 4

[openFate 305723] Allow to set the owner of a partition
by fate_noreply＠suse.de 16 Mar '11

16 Mar '11

Feature added by: Rajko Matovic (rajko_m) Feature #305723, revision 1, last change by Title: Allow to set the owner of a partition openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Rajko Matovic (rajko_m) Partner organization: openSUSE.org Description: If a user buys a new external harddrive and partitions it via YaST he will not be able to write on it, since the filesystem is owned by root. A normal user would need to know about how to use konsole and which command to use in order to change the owner. It would be a lot easier, if the user could change the owner within the partitioning module. Of course this should not be possible for system-partitions such as / and /usr etc, yet /windows and /media, as well as /home/xyz/ should be fine. The problem is not trivial as it is not enough to change fstab. See: See: http://ntfs-3g.org/support.html#unprivileged -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305723

1 5

[openFate 305075] Allow to set the owner of a partition
by fate_noreply＠suse.de 16 Mar '11

16 Mar '11

Feature added by: Arvin Schnell (aschnell(a)novell.com) Feature #305075, revision 1 Title: Allow to set the owner of a partition openSUSE-11.1: New Priority Requester: Desirable Requested by: Sven Burmeister (sven.burmeister(a)gmx.net) Partner organization: openSUSE.org Description: If a user buys a new external harddrive and partitions it via YaST he will not be able to write on it, since the filesystem is owned by root. A normal user would need to know about how to use konsole and which command to use in order to change the owner. It would be a lot easier, if the user could change the owner within the partitioning module. Of course this should not be possible for system-partitions such as / and /usr etc, yet /windows and /media, as well as /home/xyz/ should be fine. Discussion: #1: Arvin Schnell(aschnell(a)novell.com) (2008-07-15 08:32:00) Do you want to set gui and uid in /etc/fstab? #2: Sven Burmeister(sven.burmeister(a)gmx.net) (2008-07-15 08:56:26) I'm not sure which is the best approach. Either the user could do something that replaces "chown user:group ." on the new partition or some predefined gui/uid to select from, because the normal user has no idea about those and the numbers that go with them. The goal is that a user that knows the root password can not only partition a new harddrive via GUI but also make it accessible (rw) to users without having to know anything about fstab-syntax and options. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305075

1 17

[openFate 305672] openFATE - Show References
by fate_noreply＠suse.de 17 Feb '11

17 Feb '11

Feature added by: Klaas Freitag (kfreitag) Feature #305672, revision 1, last change by Title: openFATE - Show References Requested by: Klaas Freitag (kfreitag) Description: openFATE should comfortably display and handle external references like: * related bug numbers * other features (dupes, related) * wiki pages into the opensuse wiki * sourcecode, ie. svn path People should be able to edit references as well. Wiki page and sourcecode references are new and must be added. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305672

1 7

[openFate 305768] Use open source firmware for b43
by fate_noreply＠suse.de 03 Feb '11

03 Feb '11

Feature added by: Helmut Schaa (hschaa) Feature #305768, revision 1, last change by Title: Use open source firmware for b43 openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Helmut Schaa (hschaa) Partner organization: openSUSE.org Description: Currently openSUSE does not ship the firmware for broadcom devices due to legal issues. Only a script /usr/sbin/install_bcm43xx_firmware is provided which is not easy to find for new users. However an open source firmware for these devices are available now at [1] and would allow to be shipped with openSUSE. Of course this firmware needs some testing but it would be quite nice to not depend anymore on the proprietary firmware. [1] http://www.ing.unibs.it/openfwwf/ -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305768

1 4

[openFATE 305923] osc revert or merge
by fate_noreply＠suse.de 18 Dec '10

18 Dec '10

Feature added by: Will Stephenson (wstephenson) Feature #305923, revision 1, last change by Title: osc revert or merge Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: The only way to revert packages currently is very inconvenient. Some more svn semantics like osc merge to enable reverts would help. -- openSUSE Feature: https://features.opensuse.org/305923

1 2

[openFate 305695] Binary Upload of prebuild packges
by fate_noreply＠suse.de 17 Dec '10

17 Dec '10

Feature added by: Martin Mohring (MartinMohring) Feature #305695, revision 1, last change by Title: Binary Upload of prebuild packges Buildservice: Unconfirmed Priority Requester: Important Requested by: Martin Mohring (martinmohring) Partner organization: openSUSE.org Description: Ths allow also developers without direct access to the OBS backend to create distributions that consist of only binary packages or that are initially created from binary packages, there should be a combination of backend and osc be capable to upload binary files to :full directory of a project. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305695

1 1

[openFate 305081] openSUSE Testfeature
by fate_noreply＠suse.de 11 Dec '10

11 Dec '10

Feature added by: Christopher Hofmann (cwh(a)novell.com) Feature #305081, revision 1 Title: openSUSE Testfeature openSUSE-11.1: New Priority Requester: Neutral Requested by: Christopher Hofmann (cwh(a)novell.com) Partner organization: openSUSE.org Description: Feel free to play aroud with this feature. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305081

1 34

[openFate 305725] Use gettext for gconf schemas translations
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Vincent Untz (vuntz) Feature #305725, revision 1, last change by Title: Use gettext for gconf schemas translations openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Vincent Untz (vuntz) Partner organization: openSUSE.org Description: The translations of all the descriptions of gconf keys in schemas are already in the gettext files of the application. Removing them from the schemas would make the packages smaller and would possibly improve gconf performance in normal usage (ie, outside of gconf-editor, where the descriptions are used). Martin Pitt and I talked about this, and Martin has implemented it for Ubuntu: https://bugs.launchpad.net/bugs/123025 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305725

1 5

[openFATE 305851] Include kiwi-ltsp in Factory
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #305851, revision 1, last change by Title: Include kiwi-ltsp in Factory openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: I've been maintaining KIWI-LTSP: LTSP5 implementation on openSUSE using KIWI in server:ltsp Build Service repository, now it is at the stable and production ready state. This is request to include the packages(not all of them) in openSUSE Factory, and possibly 11.3 later. Relations: - Include kiwi-ltsp in Factory (novell/bugzilla/id: 474360) https://bugzilla.novell.com/show_bug.cgi?id=474360 Discussion: #1: Jigish Gohil (cyberorg) (2009-02-10 08:42:08) Should this have gone on https://features.opensuse.org/ ? #2: andrea florio (anubisg1) (2009-02-10 09:16:58) +1 for me... kiwi-ltsp is great and works fine! #3: Shrenik Bhura (sbhura) (2009-02-11 05:20:31) The inclusion will largely serve as an impetus for further development of this great project. With increased exposure, the motivation to deliver a quality project shall also increase. #4: Ken Yap (ken_yap) (2009-02-11 06:31:44) Yes, please include it in OpenSUSE, it will make OpenSUSE more attractive to people who want to build thin client clusters. #5: Stephan Kulow (coolo) (2009-02-11 06:53:23) why not Factory:Contrib? And I agree with #1 Having it in Factory means currently that someone from novell needs to review them and that's why we created contrib where everyone capable can maintain packages that go with a specific openSUSE release. And for having it on the DVD it's a bit too special use case, so it would be online repo only anyway. #6: Jigish Gohil (cyberorg) (2009-02-11 07:00:00) Not on the DVD, but Factory and OSS online repo. Instead of Contrib isn't current location - server:ltsp more appropriate? Idea is to include it officially in the distribution. I am sure we can make a same kind of arrangement we have in place for compiz to maintain this as well. -- openSUSE Feature: https://features.opensuse.org/305851

1 8

[openFate 305690] Replace System-V init with upstart init
by fate_noreply＠suse.de 27 Oct '10

27 Oct '10

Feature added by: Vitaliy Tomin (HighwayStar) Feature #305690, revision 1, last change by Title: Replace System-V init with upstart init openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Vitaliy Tomin (highwaystar) Partner organization: openSUSE.org Description: Upstart - an event-based init daemon. It can provide more flexible init system for more faster and effective boot and communication with the init daemon over D-Bus. upstart home page http://upstart.ubuntu.com/ -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305690

1 56

[openFate 305312] OpenSUSE <= 11.1 Alpha 2 don't install on SD card
by fate_noreply＠suse.de 06 Oct '10

06 Oct '10

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305312, revision 1, last change by Title: OpenSUSE <= 11.1 Alpha 2 don't install on SD card openSUSE-11.2: New Priority Requester: Important Requested by: Harald Welte <haraldwelte(a)viatech.com> Partner organization: openSUSE.org Description: [Please note that I'm working for the CPU+Chipset maker VIA and this is an actually important feature for the 'netbook' class of devices in the coming months] Recently, BIOS vendors have been starting to implement a 'boot from SD card' feature, much like they have added 'boot from USB memory stick' some years ago. The only SD-card host controller that I've seen this implemented for is SDHCI compliant host controllers. While this is a nice feature to support, for most systems it is just a gimmick and not something neccessarry. However, there are hand-held devices such as netbooks in the pipeline which do not have any other mass storage device. No hard disk and no IDE-attached flash disk or the like. They just have one (more likely two or more) SD card slots and you install and store not only your data but the entire operating system on that SD card. Furthermore, there are products like Samsung moviNAND which are basically a SDcard in a BGA package that can be soldered onto a PCB. So from a protocol and software point of view it is a SD card, but it is mechanically soldered onto the board. Such device have gained some popularity in ARM-based designs, but we'll likely see them in the x86 world, too. To make this happen, The distribution installation initrd needs to 1. include and auto-load the sdhc.ko and sdhci_pci.ko kernel modules 2. create the /dev/mmcblk* device nodes as per udev/hotplug events The actual distribution installation program needs to 1. recognize /dev/mmcblk* as block devices that can be used as target device 2. use a grub-install or similar program that can discover the bios drive number to /dev/mmcblk* device name mapping I have outlined the full details at http://wiki.gpl-devices.org/wiki/Installing_Linux_on_booting_SD_card -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305312

1 18

[openFate 305706] Facebook chat/Pidgin Integration
by fate_noreply＠suse.de 07 Sep '10

07 Sep '10

Feature added by: Kevin Dupuy (kdupuy9) Feature #305706, revision 1, last change by Title: Facebook chat/Pidgin Integration openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Kevin Dupuy (kdupuy9) Partner organization: openSUSE.org Description: Facebook is currently the most popular social networking site, and it's chat functionality is being used as an IM client for many people. With pidgin-facebookchat (http://code.google.com/p/pidgin-facebookchat/) , Pidgin seamlessly integrates Facebook friends and chats as it would any other IM service. The plugin is already there, and licensed under the GPLv3 (see website above). -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305706

1 7

[openFate 305267] Installation using Orca (screen reader) to Improve Accessibility
by fate_noreply＠suse.de 10 Aug '10

10 Aug '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305267, revision 1, last change by Title: Installation using Orca (screen reader) to Improve Accessibility openSUSE-11.2: New Priority Requester: Desirable Requested by: Darragh Ó Héiligh <d(a)digitaldarragh.com> Partner organization: openSUSE.org Description: Original title: Accessibility for installation could be automated with better results. Users can currently press F9 at the boot screen to hear the boot options spoken. THis is a fantastic new feature and is one that OpenSuSE is the first to add. For this you should be very proud. However, I would ask that you further build upon this success by recognising that accessibility at the boot menu has been enabled and automatically start the Orca screen reader with also setting gnome accessibility to enabled. One further consideration should be taken into account. To enable Orca to access the installation screen, Orca must be run as root. However, if Orca is run as root, the rest of the desktop is not accessible due to permissioning issues. Therefore, the installation should be run automatically if the f9 key si pressed. Note, a similar feature excluding the accessible boot menu has also been added to Ubuntu 8.04. Note that they also have a key press (F5) to automatically enable assistive technologies for installation on their live CD. References: See bnc #417874 (https://bugzilla.novell.com/show_bug.cgi?id=417874) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305267

1 5

[openFate 305589] Checkbox "include user home projects in search"
by fate_noreply＠suse.de 30 Jul '10

30 Jul '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305589, revision 1, last change by Title: Checkbox "include user home projects in search" Buildservice: New Priority Requester: Desirable Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: Here's one idea to start with: on the search page, have a checkbox labeled "Include user home projects in search" which defaults to OFF. Then at least you have one level of separation (between "official" and home projects) that is clear to both developers and users. And developers will be motivated to move their generally useful packages into an "official" project by the fact that the default checkbox is OFF. http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00088.html -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305589

1 4

[openFATE 305905] Package and Project Marking
by fate_noreply＠suse.de 02 Jun '10

02 Jun '10

Feature added by: Will Stephenson (wstephenson) Feature #305905, revision 1, last change by Title: Package and Project Marking Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Add the ability to have a 'status update' on packages AND projects * * status updates are not package changelogs; logs refer to changes to the contents of the package, status updates relate to ongoing work on the packages * * 1:N relationship, status updates are timestamped. Like facebook or $microblogging service. * show current status on checkout or list * Add a command to read all the status updates on a package. Examples: 1) Jack is updating Commodore:Amiga:Workbench:Factory to 23.2 and disables publish on the whole project before the actual release date with the status message '20090224 - disabled publish pending 23.2 release' 2) Jill is triaging breakages in Commodore:Amiga:Workbench:Factory and marks packages without checking them out before assigning work to team members Denise and Paula, with "osc mark -m 'broken by input.device changes' Commodore:Amiga:Workbench:Factory Preferences" 3) Paula is fixing a breakage in Commodore:Amiga:Workbench:Factory Preferences and locks (see #305899) the package with status update using "osc co -l -m '20090225 - fixing build failure due to input.device changes' Commodore:Amiga:Workbench:Factory Preferences" -- openSUSE Feature: https://features.opensuse.org/305905

1 3

[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

[openFate 305724] Allow to take over old users by home directory
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Jiří Suchomel (jsuchome) Feature #305724, revision 1, last change by Title: Allow to take over old users by home directory openSUSE-11.2: New Priority Requester: Neutral Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: (from bug reporter:) I have a seperate /home partition and whenever I reinstall/upgrade I just set up the same user as before and he gets assigned the same uid (1000) so nothing gets broken. But I guess with more users and corresponding home directories this aproach begs for wrong permissions, so I suggest the following: In case /home isn't empty it could take all directories available and list them as users to specify their data (Name, login, passwort etc as usual) and then assign corresponding uid. References: https://bugzilla.novell.com/show_bug.cgi?id=464238 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305724

1 7