May 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 311085] Enhance Monitoring Software
by fate_noreply＠suse.de 10 Jul '13

10 Jul '13

Feature added by: Lars Vogdt (lrupp) Feature #311085, revision 1 Title: Enhance Monitoring Software Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: With the new Nagios forks (icinga, shinken, ...) at the door and the additional tools around them, I think it's time for testing and packaging this stuff to be able to run the best monitoring solution on our own Products without any trouble. So evaluating the current Nagios package and also the forks would be the starting point - the next steps should be to create packages for our distribution and maybe also special documentation, if needed. -- openSUSE Feature: https://features.opensuse.org/311085

1 1

[New: openFATE 308824] Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options)
by fate_noreply＠suse.de 09 Jul '13

09 Jul '13

Feature added by: Katarina Machalkova (kmachalkova) Feature #308824, revision 1 Title: Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options) openSUSE-11.3: New Priority Requester: Important Requested by: Katarina Machalkova (kmachalkova) Description: For years, SUSE-based products have been appending '127.0.0.2 host.domain host' to /etc/hosts as a convenience for applications which want to resolve the hostname and which thus become irresponsive without active network [1] Localhost IP associated with FQDN however causes various network services (samba, SLP, LDAP, ntp, ... ) to behave oddly [2]. An option in product-wide control files has been introduced so as not to append 127.0.0.2 on server-oriented products (SLES) - FaTE#303875, while keeping user the possibility to override the default in GUI and AutoYaST profile. Nevertheless, even reasonably set default doesn't prevent misconfigurations and user complaints [3] The suggestion is therefore to drop 127.0.0.2 modification of /etc/hosts altogether and drop GUI/control options associated with configuration thereof. These include: * GUI option in YaST installer * XML profile elements in AutoYaST * Variable in product-wide control file (control.xml) * Possibly also sysconfig variable Appending 127.0.0.2 line has always been sort of workaround for flawed (mostly) desktop applications and DNS servers, so rather than providing workaround with plethora of side effects, it'd more reasonable to have affected apps fixed. Bugs have been filed against some of them and fixed already. References: [1] Apps become slow when offline bugs https://bugzilla.novell.com/show_bug.cgi?id=304632 https://bugzilla.novell.com/show_bug.cgi?id=383336 [2] Network services going insane with localhost IP associated with FQDN https://bugzilla.novell.com/show_bug.cgi?id=207392 https://bugzilla.novell.com/show_bug.cgi?id=355608 https://bugzilla.novell.com/show_bug.cgi?id=570108 [3] Even reasonably set default doesn't help https://bugzilla.novell.com/show_bug.cgi?id=510228 -- openSUSE Feature: https://features.opensuse.org/308824

1 21

[New: openFATE 315081] Manual repository release option
by fate_noreply＠suse.de 08 Jul '13

08 Jul '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #315081, revision 1 Title: Manual repository release option Buildservice: Evaluation by engineering manager Milestone: 2.5 Priority Requester: Important Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: OBS already supports to release binaries to another repository via releasetarget definition when using the OBS maintenance support. This feature is also useful outside of maintenance, when a staging repository should be created first and the result shall be released to another repository after testing. Therefore we want to extend current releasetarget definition by a trigger="manual" mode. In addition to that we need a command to execute the release process. For example -X POST /build/$PROJECT?cmd=release or for a specified repo only: -X POST /build/$PROJECT/$REPOSITORY?cmd=release the command will return with "invoked" state after successfully creating the event. -- openSUSE Feature: https://features.opensuse.org/315081

1 3

[New: openFATE 315061] improve YaST installer to allow patterns and packages from network
by fate_noreply＠suse.de 08 Jul '13

08 Jul '13

Feature added by: Tomas Cech (sleep_walker) Feature #315061, revision 1 Title: improve YaST installer to allow patterns and packages from network openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Tomas Cech (sleep_walker) Partner organization: openSUSE.org Description: As you probably already noticed, I'm fighting to get E17 as desktop choice in YaST2 installer. To get E17 choice in installer I need to have pattern and packages present on medium which is already more than full. I proposed replacing LXDE with E17, but there are still users who wants to keep it on medium and I agree, that this shouldn't be the way to fix it. Proper fix I believe is patch YaST2 installer to offer packages and pattern from default repository in http://download.opensuse.org/distribution/ if the network is up. Having checkbox 'Enable network repositories' during installation workflow would make this behavior optional and selected by default if the server is reachable. Business case (Partner benefit): openSUSE.org: I also received feedback from MATE maintainer, who would welcome such option as well and I believe there are others too. This is artificial limitation which should have been removed long time ago. -- openSUSE Feature: https://features.opensuse.org/315061

1 10

[openFATE 307765] Debuginfo file system
by fate_noreply＠suse.de 05 Jul '13

05 Jul '13

Feature added by: Ruchir Brahmbhatt (Ruchir) Feature #307765, revision 1 Title: Debuginfo file system openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ruchir Brahmbhatt (ruchir) Description: It would be nice to have internet mountable debuginfo file system just like fedora. This will allow users to get traces from gdb without installing lots of debuginfo packages. This way we can have access to all debuginfo packages without installing them. This will encourage more users to report bugs. Some users may not be willing to install additional debuginfo packages due to lack of enough disk space or willingness to report bugs. -- openSUSE Feature: https://features.opensuse.org/307765

1 2

[New: openFATE 311124] Consolidate faillog, pam_tally, pam_tally2, pam_faillock
by fate_noreply＠suse.de 27 Jun '13

27 Jun '13

Feature added by: Thorsten Kukuk (kukuk) Feature #311124, revision 1 Title: Consolidate faillog, pam_tally, pam_tally2, pam_faillock openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: There are four different ways to track the number of failed logins and react to this: faillog, pam_tally, pam_tally2, pam_faillock. They are all incompatible together and pretty hard next to impossible to configure. Goal: Write one new module "pam_faillog", which replaces all of them. Should be able to read all current databases, supports all features together but uses advanced PAM functionality to make configuration very easy. The module depends on correct behavior of calling application, which means we need some checks if application behaves correct and maybe fix them. -- openSUSE Feature: https://features.opensuse.org/311124

1 3

[New: openFATE 314358] Userdefined-JACK-Suite/Group
by fate_noreply＠suse.de 18 Jun '13

18 Jun '13

Feature added by: fn ln (gwdg37) Feature #314358, revision 1 Title: Userdefined-JACK-Suite/Group Requested by: fn ln (gwdg37) Partner organization: openSUSE.org Description: PLEASE either provide a setup for all audio including pulse through JACK or something like a Jacked-Audio-Dynamic-Suite that allows users to select packages they want to use with JACK so that whenever any of these apps launch sound would be reconfigured to use JACK preferably but not necessarily without sacrificing common desktop and other app sounds etc. I've been turning blue in the face trying to get Rosegarden to produce sound AT ALL and I'd really like to use it with ZynnAddSubFX, Qsyth or in fact any other popular synth. The same goes for PLUG & Audacity which I want to use with my Fender amplifier as well as other sound packages. Or ask producing sources to provide alternatives to using JACK. I'm REALLY open to any solution OTHER than installing (mostly) audio apps that just plain don't work even when NOTHING proprietary is involved. Thanks. -- openSUSE Feature: https://features.opensuse.org/314358

1 1

[New: openFATE 314357] Request for mixminion package with python update
by fate_noreply＠suse.de 18 Jun '13

18 Jun '13

Feature added by: fn ln (gwdg37) Feature #314357, revision 1 Title: Request for mixminion package with python update Education Li-f-e: Unconfirmed Priority Requester: Important Requested by: fn ln (gwdg37) Partner organization: openSUSE.org Description: I'd like to see the mixminion package included. It isn't proprietary code or anything so I don't see why it couldn't be. Last I heard the project was being worked on again but if not than just fix the last release 0.0.8alpha3 so that it will work with newer versions of Python. Thank you -- openSUSE Feature: https://features.opensuse.org/314357

1 1

[New: openFATE 315097] Implement The Standard Interchange Protocol 2.0 As An Authentication Schema
by fate_noreply＠suse.de 10 Jun '13

10 Jun '13

Feature added by: Timothy Butterworth (timothy_m_butterworth) Feature #315097, revision 1 Title: Implement The Standard Interchange Protocol 2.0 As An Authentication Schema openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Timothy Butterworth (timothy_m_butterworth) Partner organization: openSUSE.org Description: The Standard Interchange Protocol 2.0 is a proprietary standard communication protocol that is developed and published as a standard by 3M. It is primarily implemented to provide communication between Library Computer Systems and Self-Service Circulation Terminals. This protocol is implemented across the majority of Integrated Library Management Systems including open source LMS software such as KOHA. One of its functions is patron library card âuser accountâ creation and authentication. In addition to this it is also implemented in envisionware PC Reservation which can utilize to provide patron accessible computers systems with authentication utilizing their existing library cards. Currently there is no direct integration of The Standard Interchange Protocol 2.0 as an authentication mechanism for Linux. Although it may be possible to utilize RADIUS authentication with The Radiator RADIUS server to proxy from RADIUS to SIP2. Radiator is the only RADIUS product I have currently found so far that supports SIP2. OSC Radiator SIP2 Announcement: http://www.open.com.au/pipermail/radiator/2012-July/018433.html As many open source software projects such as Koha have already implemented SIP2.0 and their source code is available under various open source licenses that code base could be utilized as a model or reused to implement this authentication. The Source code is also available for review in the commercial OCS Radiator Product as well implemented as a RADIUS proxy component. Also the entire SIP 2.0 specification would not need to be implemented just the client logon component. Which incorporates the following behavior: Formatting and sending SIP2 Patron Status Request message (type 23) with Patron's identifier and password to the specified SIP2 server. Receiving and processing SIP2 Patron Status Response (type 24) from the SIP2 Server. This would allow the basic authentication to take place. This could also be incorporated into a domain authentication system to provide more advanced user management such as user login restrictions such as authorized login times and maximum session duration if a component was implemented to create a trust for the external SIP2 patron accounts and perform the proxy rewrite. Use Case: Incorporating SIP2 as an authentication mechanism in Linux Distributions would provide a means for libraries to Integrate Linux systems for patron internet access utilizing their existing LMS Patron user accounts. This opens up an additional sales market for Linux Distributors. The majority of libraries currently have and others are planning to implement patron internet access systems. This is beneficial for Linux Distributors as their products could be purchased and deployed instead of the more costly solutions which currently require Envisionware PC Reservation licenses, Microsoft Windows Licenses as well as additional expensive software license costs. Our libraries currently have 200+ patron access systems spread across multiple locations that could be migrated to Linux with the removal of MS Windows, PC Reservation and other expensive software licensing/purchases costs associated with them. This is the only major hurdle preventing a future Linux deployment. Business case (Partner benefit): openSUSE.org: There is a valid use case here as well as a demand by libraries to have products that incorporate SIP2 as an authentication mechanism to integrate into their existing Library Management Systems. Incorporating this will assist in the further spread and adoption of Linux and provide an inroads into organizations with libraries that utilize SIP2 across the world. As not other Linux distribution current provides this that I have found it would also be a ground breaking achievement being first to market to meet user demand. Also currently as I said Microsoft and other OS's do not support this capability either. This would assist in making Linux accessible to the masses and possibly attract youth to Linux over windows. -- openSUSE Feature: https://features.opensuse.org/315097

1 2

[New: openFATE 314691] Support setting hyperlink to any cells
by fate_noreply＠suse.de 06 Jun '13

06 Jun '13

Feature added by: Kohei Yoshida (kohei_yoshida) Feature #314691, revision 1 Title: Support setting hyperlink to any cells Requested by: Kohei Yoshida (kohei_yoshida) Partner organization: openSUSE.org Description: Excel supports setting hyperlinks to any cells regardless of their contents. When set, the cell contents turn blue and underlined, and clicking on them will trigger action based on what the URL is. Calc, on the other hand, supports hyperlink either via HYPERLINK cell function or hyperlink field in rich-text contet. Calc should support an additional way of setting hyperlinks to cells as cell attributes so that we can faithfully interoperate with Excel documents with hyperlinks. Relations: - Related bugzilla report (novell/bugzilla/id: 0) https://bugzilla.novell.com/show_bug.cgi?id=0 -- openSUSE Feature: https://features.opensuse.org/314691

1 2