July 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309768] Blobec: Git with GPG on FTP
by fate_noreply＠suse.de 04 Oct '13

04 Oct '13

Feature added by: Martin Vidner (mvidner) Feature #309768, revision 1 Title: Blobec: Git with GPG on FTP Requested by: Martin Vidner (mvidner) Description: Blobec is a tool to store my private information (diary, calendar) on the Net to increase its availability and redundance. * To preserve privacy it needs to be encrypted → GPG. * I want it to be versioned, with easy merging of diverged copies → Git. * The publishing part works with what my current ISP provides → FTP (with SSL). I am implementing it in Ruby, with cURL. -- openSUSE Feature: https://features.opensuse.org/309768

1 4

[New: openFATE 312825] Objects in YCP (YaST)
by fate_noreply＠suse.de 04 Oct '13

04 Oct '13

Feature added by: Martin Vidner (mvidner) Feature #312825, revision 1 Title: Objects in YCP (YaST) Hackweek VII: Unconfirmed Priority Requester: Important Requested by: Martin Vidner (mvidner) Partner organization: openSUSE.org Description: As I am thinking about refactoring the network code, not having objects in YCP is a pain. The twist is, I don't want to add YCP objects but use Ruby objects. (We can already use Perl objects, yast2-storage does it, but it's limited.) Here's sample code to show how it could look, modeled after http://www.ruby-doc.org/stdlib-1.8.7/libdoc/uri/rdoc/classes/URI.html { import "Assert"; // Yes, you can! (also in SP2) // http://svn.opensuse.org/viewvc/yast/trunk/yast2/library/modules/Assert.ycp?… // Original Ruby code: // require 'uri' import $[ "what": "uri", "language": "ruby", "namespaces": ["URI", "URI::HTTP"] ]; /* The above complicated syntax enables - loading modules from elsewhere than /usr/share/YaST2/modules - loading YCP namespaces (Ruby modules (classes)) named otherwise than the file they are in, without needing to annotate them with TYPEINFO (like perl-bindings/pluglib-bindings do) */ // uri = URI.parse("http://www.ruby-lang.org/") any uri = URI::parse("http://www.ruby-lang.org/"); // [1] // assert_equal "http", uri.scheme Assert::Equal("http", uri->scheme()); // newuri = URI::HTTP.build( {:host => 'www.example.com', :path => '/foo/bar'}) any newuri = URI::HTTP::build($[ `host: "www.example.com", `path: "/foo/bar"]); // assert_equal "http://www.example.com/foo/bar", newuri.request_uri Assert::Equal ("http://www.example.com/foo/bar", newuri->request_uri()); } Formally, whereas now YCP has NAMESPACE :: IDENTIFIER ( PARAMS ) which calls a function (a module/class method in Ruby, a class method in Perl), we add EXPRESSION -> IDENTIFIER ( PARAMS ) which calls a method (an instance method in Ruby. [1] "any" is a lie, the type is actually a distinct one, called YCPExternal in C++. We could use "extern" which is currently an unused reserved word in YCP. But URIs are not my target. I am aiming for { any eth = SUSE::Ifcfg::new("eth0"); any br = SUSE::Ifcfg::Bridge::new("br0"); br->startmode(`auto); br->add(eth); /* br->add will also set: eth->bootproto(`none); eth->startmode(br->startmode()); */ any tap = SUSE::Ifcfg::Tap::new("tap0")->tunnel_set_owner("tux"); br->add(tap); foreach(any i, [br, tap, eth], { i->save(); }); } if (you->are_interested()) { you->please()->tell(martin); } -- openSUSE Feature: https://features.opensuse.org/312825

1 3

[New: openFATE 314535] More complete theming
by fate_noreply＠suse.de 25 Sep '13

25 Sep '13

Feature added by: Gavin S (gav616) Feature #314535, revision 1 Title: More complete theming openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Gavin S (gav616) Partner organization: openSUSE.org Description: By default add a very few extra themes, maybe one dark one medium shaded. Only add tried and tested themes that are inoffensive, subtle and bug free. Add a more complete default icons in the home folder e.g. http://i.imgur.com/CKyKz.png Business case (Partner benefit): openSUSE.org: Adds a more complete feeling to the distribution, light themes and such don't work for some people. The icons in the home folder would be easier to spot what you need to click, and it looks nicer. -- openSUSE Feature: https://features.opensuse.org/314535

1 10

[New: openFATE 308958] Reduce size of the Minimal Install
by fate_noreply＠suse.de 22 Sep '13

22 Sep '13

Feature added by: Jan Engelhardt (jengelh) Feature #308958, revision 1 Title: Reduce size of the Minimal Install openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Jan Engelhardt (jengelh) Partner organization: openSUSE.org Description: IMHO, the text-mode minimal install without X and anything still comes with "too many" packages. I use the minimal selection whenever I need to set up a new, clean, system, as installing onto a Minimal is faster than cherry-picking every single package for deletion from a Medium or Maximum selection. This includes, but is not limited to: * documentation to magic things happening in the background: PolicyKit-doc, readline-doc * other documentation that I've probably read already; bash-doc, perl-doc * archaic systems: yp-tools ypbind yast2-nis-client * packages serving no purpose: perl-Business-ISBN (heck, not even yast needs that), perl-GD * things that make my command line slow: command-not-found scout * it so happens that eventually I can throw out the entire python stack, and the remaining Xorg libs * printing, sound, bootsplash I have here a dump file between the initial minimal install and a tailored system - some things have been removed that I would leave on the minimal install list however (e.g. yast2-sudo). So the raw contents of the diff file is [mh, FATE has no attachments - see https://bugzilla.novell.com/show_bug.cgi?id=577791 ] Business case (Partner benefit): openSUSE.org: Everytime a new system is bootstrapped, I have to (="want to") remove these first because they will never be needed -- if they will, I can reinstall them later, or pick a larger "non-minimal" text mode from yast. -- openSUSE Feature: https://features.opensuse.org/308958

1 3

[New: openFATE 313142] YaST support only SSSD for LDAP based authentication
by fate_noreply＠suse.de 05 Sep '13

05 Sep '13

Feature added by: Ralf Haferkamp (rhafer) Feature #313142, revision 1 Title: YaST support only SSSD for LDAP based authentication openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. -- openSUSE Feature: https://features.opensuse.org/313142

1 9

[openFATE 306974] Additional columns in software management
by fate_noreply＠suse.de 03 Sep '13

03 Sep '13

Feature added by: Todd R (TheBlackCat) Feature #306974, revision 1 Title: Additional columns in software management openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Todd R (theblackcat) Description: It would be nice if there were a few additional columns in the software management interface. One specific column I am interested in would be an architecture column, to show you the architecture of an installed package or the architecture the package would have if you were to install it. The other column would show the repository of the package, either the repository of an installed package or the repository the package would be downloaded from if you were to install it. -- openSUSE Feature: https://features.opensuse.org/306974

1 6

[New: openFATE 310410] Evaluate switching to libjpeg-turbo
by fate_noreply＠suse.de 26 Aug '13

26 Aug '13

Feature added by: Vincent Untz (vuntz) Feature #310410, revision 1 Title: Evaluate switching to libjpeg-turbo openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: Quoting http://fedoraproject.org/wiki/Features/libjpeg-turbo: ==== libjpeg-turbo is fork of the original libjpeg project. It contains numerous performance related enhancements and is at least twice faster in JPEG compression/decompression than original libjpeg on platforms with MMX/SSE instruction set. It has same API/ABI like original libjpeg and also runs on non-SSE platforms where is around 25% faster. http://sourceforge.net/projects/libjpeg-turbo ==== We should evaluate this library and see if we can replace libjpeg with it for improved performance. -- openSUSE Feature: https://features.opensuse.org/310410

1 8

[New: openFATE 313400] store gpg key in fs instead of rpmdb
by fate_noreply＠suse.de 19 Aug '13

19 Aug '13

Feature added by: Ludwig Nussel (lnussel) Feature #313400, revision 1 Title: store gpg key in fs instead of rpmdb openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: currently gpg keys used by rpm for signature verification apppar to be installed in the rpmdb as some kind of pseudo package (rpm -qa 'gpg-pubkey*'). This makes them rather clumsy to manage. It would be better to have gpg keys as regular files in the file system. In fact rpm supports that since a while via the %_keyringpath option. It's set to %{_dbpath}/pubkeys/ by default. If any keys are found in that directory the keys in the rpmdb are no longer used. Therefore I propose to: - change the openSUSE-build-key package to drop it's files into %_keyringpath - patch libzypp to prefer %_keyringpath too - add a %post snippet to rpm or openSUSE-build-key to export extra keys in rpmdb to %_keyringpath and remove them from rpmdb afterwards - make %_keyringpath an array so we can have distro provided keys in /usr and admin/locally configured keys in /etc -- openSUSE Feature: https://features.opensuse.org/313400

1 7

[openFATE 306598] Sync Tomboy/Tasque with Evernote
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Joe Brockmeier (jbrockmeier) Feature #306598, revision 1 Title: Sync Tomboy/Tasque with Evernote Requested by: Joe Brockmeier (jbrockmeier) Description: Evernote is a pretty cool service, but it doesn't have a Linux client. I'd like to be able to sync my Tomboy notes with Evernote and retrieve them from another machine. Same with Tasque -- I'd like to be able to save a to-do list to Evernote from tasque so I could use a mobile Evernote client to look up my to-dos. -- openSUSE Feature: https://features.opensuse.org/306598

1 4

[openFATE 306588] improve on software search
by fate_noreply＠suse.de 13 Aug '13

13 Aug '13

Feature added by: Juergen Weigert (jnweiger) Feature #306588, revision 1 Title: improve on software search Requested by: Juergen Weigert (jnweiger) Description: software.o.o/search is always a case insensitive substring search. I'd like to hack into the system and add - optional case sensitivity,- exact package name search- regexp search This is an opportunity to learn ruby on rails for me. Any takers, who want to coach me, especially with Rails welcome. -- openSUSE Feature: https://features.opensuse.org/306588

1 6