February 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310664] package shorewall in an opensuse repository
by fate_noreply＠suse.de 06 Mar '12

06 Mar '12

Feature added by: Divan Santana (divansantana7) Feature #310664, revision 1 Title: package shorewall in an opensuse repository openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Divan Santana (divansantana7) Description: openSUSE is a great open source community linux distribution. One thing I miss which other distros have, is that the shorewall firewall packages are not available in any repositories. It would be great if shorewall was packaged and available in a repository. Yes one can install this from http://shorewall.net but it is not really the ideal way of doing things. Shorewall is a powerful easy to use high level firewall program which many use as their primary firewall program. Please could this be packaged and available in an openSUSE repo for 11.4 . -- openSUSE Feature: https://features.opensuse.org/310664

1 12

[New: openFATE 313087] [package] MyPaint
by fate_noreply＠suse.de 06 Mar '12

06 Mar '12

Feature added by: Svetoslav Ganchev (sv_g) Feature #313087, revision 1 Title: [package] MyPaint Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Svetoslav Ganchev (sv_g) Partner organization: openSUSE.org Description: Hi! I think it would be great if MyPaint gets in the main repository of openSUSE. It's a great app and a very popular one! Thanks! -- openSUSE Feature: https://features.opensuse.org/313087

1 1

[New: openFATE 313212] add menu tree in kickoff menu search
by fate_noreply＠suse.de 06 Mar '12

06 Mar '12

Feature added by: Jean-Daniel Dodin (jdd) Feature #313212, revision 1 Title: add menu tree in kickoff menu search Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Jean-Daniel Dodin (jdd) Partner organization: openSUSE.org Description: In the kickoff menu, there is a search window allowing to find an application known by it's name. But this search box do not allow to know where this application is located in the menu tree. It's probably easy, as the menu entry is found, to display the hole path in the menu tree. Use Case: Install dvdstyler. Do not know where it's located in the menu tree. Do not find in in /multimedia/editing. type dvds in the search box, see "dvdstyler" and can leunch it from there, but if was shown the exact place (multimedia/writer/dvstyler), could more easily find it nex time Business case (Partner benefit): openSUSE.org: makes it easier to understand a meny tree sometime unfriendly -- openSUSE Feature: https://features.opensuse.org/313212

1 3

[New: openFATE 313280] uthash-devel
by fate_noreply＠suse.de 06 Mar '12

06 Mar '12

Feature added by: Bas van den Dikkenberg (basd82) Feature #313280, revision 1 Title: uthash-devel Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Bas van den Dikkenberg (basd82) Partner organization: openSUSE.org Description: Hash table and linked list for C structures This package provides uthash and utlist, C preprocessor implementations of a hash table and a linked list. It is a dev package without a source or binary package as there are only header files. Since version 1.9 uthash includes also macros for dynamic arrays and strings. I have made the package in my home dir see: https://build.opensuse.org/project/show?project=home%3Abasd82%3Authash-devel Use Case: It used by the package burp with has exclude this external headers files from its source. In other distributions it is also a seperate package Business case (Partner benefit): openSUSE.org: I think iit is used in multie projects, and that don't have to include the uthash header files in there procject and just creat a dependency -- openSUSE Feature: https://features.opensuse.org/313280

1 1

[New: openFATE 310926] LDAP Filter
by fate_noreply＠suse.de 01 Mar '12

01 Mar '12

Feature added by: Gregor Dschung (chkpnt) Feature #310926, revision 1 Title: LDAP Filter Buildservice: Unconfirmed Priority Requester: Important Requested by: Gregor Dschung (chkpnt) Partner organization: openSUSE.org Description: Two of the configuration variables for LDAP are LDAP_SEARCH_BASE and LDAP_SEARCH_ATTR. It would be nice to have an additional LDAP_SEARCH_FILTER for use cases that can't be expressed by using only LDAP_SEARCH_BASE. Use Case: Imangine the following: dn: cn=John Doe,ou=People,ou=Branch A,o=Large Corp,c=COM cn: John Doe personalTitle: M.Sc. department: IT ... There it is possible to use LDAP_SEARCH_BASE="ou=Branch A,o=Large Corp,c=COM" and LDAP_SEARCH_ATTR="cn". But what, if only people from the IT should have access to OBS? Or only guys with a Master's degree? Or both? Therefore, something like LDAP_SEARCH_FILTER="personalTitle=M.Sc.,department=IT" would be nice. https://features.opensuse.org/310925 Business case (Partner benefit): openSUSE.org: I'm missing that feature. Essential for large companies. -- openSUSE Feature: https://features.opensuse.org/310926

1 1

[New: openFATE 312330] Add Follower Box to connect.o.o
by fate_noreply＠suse.de 29 Feb '12

29 Feb '12

Feature added by: Sascha Manns (saigkill) Feature #312330, revision 1 Title: Add Follower Box to connect.o.o openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Sascha Manns (saigkill) Partner organization: openSUSE.org Description: Adding a "Following" like Box for "Followers" in connect.o.o. Use Case: More overview what happens around the own account :-) -- openSUSE Feature: https://features.opensuse.org/312330

1 3

[New: openFATE 312079] connect.o.o: page that shows all group members
by fate_noreply＠suse.de 29 Feb '12

29 Feb '12

Feature added by: Richard Bos (rbos) Feature #312079, revision 1 Title: connect.o.o: page that shows all group members openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Richard Bos (rbos) Partner organization: openSUSE.org Description: Please add a page to connect.opensuse.org that shows all the group members. At the moment in can see for the openSUSE NL group that there 15 members, but there are only 10 avatars shown on the left. Business case (Partner benefit): openSUSE.org: It is interesting to see who are actually part of the group -- openSUSE Feature: https://features.opensuse.org/312079

1 2

[New: openFATE 308841] zypper integration
by fate_noreply＠suse.de 27 Feb '12

27 Feb '12

Feature added by: Michael Meeks (michael_meeks) Feature #308841, revision 1 Title: zypper integration Buildservice: New Priority Requester: Mandatory Requested by: Michael Meeks (michael_meeks) Partner organization: openSUSE.org Description: I often want new softare; everything (+ spouse) is in the build service - and searchable via 'osc se'. I want to be able to do 'zypper se-osc uxlaunch' and then install it easily from the build service through that tool (without authentication) - preferably with (whatever) service subscription is necessary hidden from me. Business case (Partner benefit): openSUSE.org: This would make openSUSE rather more compelling as a distro, and give people access to a wider range of new, and un-blessed software. -- openSUSE Feature: https://features.opensuse.org/308841

1 5

[New: openFATE 313116] Reasons to adopt KDE SC 4.9 in opensuse 12 .2
by fate_noreply＠suse.de 24 Feb '12

24 Feb '12

Feature added by: Jedi Beeftrix (Jedibeeftrix) Feature #313116, revision 1 Title: Reasons to adopt KDE SC 4.9 in opensuse 12 .2 openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Jedi Beeftrix (jedibeeftrix) Partner organization: openSUSE.org Description: Opensuse 12.2 and KDE SC 4.9 have very similar release dates, which will make integrating the latter into the former problematic, but it may well be worth it:- 1. A Stabilised Dolphin 2.x release. Dolphin 2.0 has a lot of promise, but a lot of new code too: http://ppenz.blogspot.com/2012/01/dolphin-20-status-update.html -- openSUSE Feature: https://features.opensuse.org/313116

1 7

[New: openFATE 313108] Kerberos printing via CUPS for openSUSE clients in a Windows AD domain
by fate_noreply＠suse.de 22 Feb '12

22 Feb '12

Feature added by: Anderson Luiz Perazzoli (alperazzoli) Feature #313108, revision 1 Title: Kerberos printing via CUPS for openSUSE clients in a Windows AD domain openFATE: Unconfirmed Priority Requester: Desirable Requested by: Anderson Luiz Perazzoli (alperazzoli) Partner organization: openSUSE.org Description: The current kerberos printing solution included with openSUSE 12.1 and 11.4 does not work with openSUSE clients logged into a Windows Active Directory Domain. CUPS supports kerberos, but it has issues, at least if the Windows Server version is 2003 or higher, "because the kerberos tickets are to large for the CUPS buffer according to Michael Sweet, the original CUPS developer." - http://blog.ryanharter.com/?p=4 CUPS error_log just gave me a cryptic error message - "[Job 2] Backend returned status 1 (failed)" so I had to do some research to actually find out the real issue. There is a CUPS backend developed independently which I will describe below. It has solved this issue out-of-the box. Test Case: Just enter a Windows Active Directory domain and try to print to a printer which requires AD authentication. It fails with the message "[Job 2] Backend returned status 1 (failed)" in the cups error_log. The job fails and printing is paused. Use Case: I have worked around this limitation by using cups-ksmb (https://github.com/vchoi/cups-ksmb) which handles the Active Directory kerberos tickets properly and as such has solved the printing problem for me. The quick dirty way which worked for me was unpacking the small .deb binary package provided by the project's github, and manually copying the files to my system. The important parts seem to be /usr/lib/cups/backend/ksmb and /etc/sudoers.d/99ksmb. It worked on the first test run, although it would have been much more elegant to just install an RPM from the official repo. With these files in their rightful places, the CUPS web frontend now offered me a new network printer type ("SAMBA + Kerberos"), which puts ksmb:// to the beginning of the printer URI. From there you just have to input your AD printer's address in the "//server/printer" format and it just works. My suggestion is that this backend be packaged & included in the next openSUSE releases. Business case (Partner benefit): openSUSE.org: It solved an issue which I had for a couple of years and might be others' cases too. It adds to openSUSE's interoperability level which I am sure will be appreciated by those using AD networks with mixed windows/linux clients. -- openSUSE Feature: https://features.opensuse.org/313108

1 2