October 2010 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305914] PAC support for 'system wide proxy configuration'
by fate_noreply＠suse.de 05 Dec '15

05 Dec '15

Feature added by: Dominique Leuenberger (dimstar) Feature #305914, revision 1, last change by Title: PAC support for 'system wide proxy configuration' openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Dominique Leuenberger (dimstar) Description: The distribution now contains libproxy and we should try to make as much use of it as possible. A big advantage is the ability to parse PAC (Proxy AutoConfiguration) without the need for this in every application. Simply linking against libproxy with it's very simple API (3 API calls, 2 without parameters) is enugh to have the advantage of no longer needing to 'guess' what proxy to use. What is now: - You can set in yast / proxy a general proxy to be used (http://foo.proxy.com:1234) This is bascially put into http_proxy envvar. In gnome you can set user proxy configuration as: - Use System Proxy (as configured in yast) - Use proxy configuration (static, same options as in yast) - Use automatic proxy configuration script Yast lacks the option to specify a PAC script on system wide level. This is only possible in the user sessions configuration. This made sense as most applications don't know how to handle pac files anyway. But with libroxy, this hurdle can be taken away from every single application and can thus be offered. I'm glad to elaborate on questions; I'm sure there are some :-) -- openSUSE Feature: https://features.opensuse.org/305914

1 17

[New: openFATE 310712] Constantly usable Factory
by fate_noreply＠suse.de 18 Nov '15

18 Nov '15

Feature added by: Christoph Obexer (cobexer) Feature #310712, revision 1 Title: Constantly usable Factory openSUSE-11.4: Unconfirmed Priority Requester: Mandatory Requested by: Christoph Obexer (cobexer) Partner organization: openSUSE.org Description: I recently read about the Debain CUT project, ( http://cut.debian.net/ (http://cut.debian.net/) , http://kitenet.net/~joey/code/debian/cut/ (http://kitenet.net/~joey/code/debian/cut/) ) looking at the current situation with openSuSE Factory i see that it is dangerous to use, unstable alpha or beta packages come into Factory all the time, while other packages become out of date. The result is a system that is pretty much unusable. Only allowing stable packages to enter Factory would make that a lot better, and if one finds bugs chances are that those bugs aren't already fixed in a newer svn/git snapshot, but are real bugs. This would save a lot of time for testers and developers in dealing with "invalid", or "temporary" bugs. I think that a robust, "stable" Factory would lead to more people using it full time and thus a better quality of the next openSuSE version. I see that this would have negative aspects as well, but i think most devel projects have unstable/testing repositories set up already and those could still contain the snapshots of upcoming versions, testers of those specific projects could use tose repositories then. Doing a release of openSuSE would be easier then too, simply snapshot Factory, and declare it as openSuSE $VERSION. The transition from the current state to a "constantly usable Factory" would be smooth too. And it's also in line with the openSuSE vision, stable rather than bleeding edge. Business case (Partner benefit): openSUSE.org: More users using Factory -> better stability of Factory -> better stability of openSuSE $VERSION -> openSuSE back where it should be - the Linux for professionals. -- openSUSE Feature: https://features.opensuse.org/310712

1 4

[New: openFATE 309700] Advanced uninstall/Rollback support in package management, zypper
by fate_noreply＠suse.de 30 Oct '15

30 Oct '15

Feature added by: Nikanth K (nikanth) Feature #309700, revision 1 Title: Advanced uninstall/Rollback support in package management, zypper openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Nikanth K (nikanth) Description: # Zypper install evolution This will install say 13 packages, evolution and its dependencies including evolution-data-server etc.... #zypper remove evolution This will remove only evolution. Leaving the dependencies installed. The 12 packages are left installed. Instead provide an easy way to rollback/uninstall all those packages using say a transaction-id from the history. So that, say we have foo.rpm which needs bar.rpm #zypper install foo #zypper remove foo will not leave bar installed in the system. -- openSUSE Feature: https://features.opensuse.org/309700

1 4

[New: openFATE 309070] Allow auth
by fate_noreply＠suse.de 27 Oct '15

27 Oct '15

Feature added by: Adrian Schröter (adrianSuSE) Feature #309070, revision 1 Title: Allow auth Buildservice: Evaluation Priority Requester: Important Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: Implement authentification plugin for api which allows authentification against remote http web server. This may need changes in session handling. We want to use this plugin and setup for opensuse.org and connect api.o.o and build.o.o directly to internet without iChain proxy. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-23 12:06:04) Tom, we need your expertise here, what is possible with rails and what makes sense. -- openSUSE Feature: https://features.opensuse.org/309070

1 7

[New: openFATE 310233] skip repo update when installing packages with zypper
by fate_noreply＠suse.de 24 Sep '15

24 Sep '15

Feature added by: Denny Beyer (lumnis) Feature #310233, revision 1 Title: skip repo update when installing packages with zypper openFATE: Unconfirmed Priority Requester: Important Requested by: Denny Beyer (lumnis) Description: When installing a new package with zypper etc. everytime you run zypper, repos get updated and the user has to wait. Because a general user needs several extra repos, this waiting time always seems to be too long. Why not running 'zypper ref' as a low priority task after startup/time intervall has passed and give the used immidiate access to install a software package? -- openSUSE Feature: https://features.opensuse.org/310233

1 18

[New: openFATE 310176] Switch to sssd for LDAP/Kerberos authentication
by fate_noreply＠suse.de 30 Jul '15

30 Jul '15

Feature added by: Ralf Haferkamp (rhafer) Feature #310176, revision 1 Title: Switch to sssd for LDAP/Kerberos authentication openSUSE-11.4: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Description: Because of the various issues we face with nss_ldap/pam_ldap (see e.g. bug#477061, bug#157078 and others) and because of the added value sssd gives us (e.g. offline support, integrated kerberos support). We should change yast2-ldap-client to configure sssd instead of nss_ldap/pam_ldap/pam_kerberos. sssd packages are already available for 11.3. We still need to add support for it in pam-config. -- openSUSE Feature: https://features.opensuse.org/310176

1 16

[openFATE 306370] Support request creating and accepting from remote packages
by fate_noreply＠suse.de 28 Jul '15

28 Jul '15

Feature added by: Adrian Schröter (adrianSuSE) Feature #306370, revision 1, last change by Title: Support request creating and accepting from remote packages Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: Submit requests should be supported when using a remote project/package as source. -- openSUSE Feature: https://features.opensuse.org/306370

1 3

[New: openFATE 309188] Don't require keytab file for kerberos authentication
by fate_noreply＠suse.de 26 May '15

26 May '15

Feature added by: Todd R (TheBlackCat) Feature #309188, revision 1 Title: Don't require keytab file for kerberos authentication openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Todd R (theblackcat) Description: In openSUSE, when using kerberos it requires that a keytab file be available for things like kerberized nfs. However, not all kerberos servers are set up to provide keytabs. Someone using openSUSE cannot access these resources using kerberos at all, as far as I have been able to find out. It would be nice if openSUSE removed this requirement, or at least made it user-configurable whether to require it or not. -- openSUSE Feature: https://features.opensuse.org/309188

1 4

[New: openFATE 310710] Integrate the functionality of "fusermount -u" into umount
by fate_noreply＠suse.de 18 May '15

18 May '15

Feature added by: Reinhard Max (rmax) Feature #310710, revision 1 Title: Integrate the functionality of "fusermount -u" into umount openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Reinhard Max (rmax) Description: It is confusing that FUSE mount points need a different command to unmount them than everything else. Historically FUSE had to bring its own command, because traditional umount refuses umounting of mounts that are not in /etc/fstab for non-privileged users. But now that FUSE has become mainstream, I think it is time to integrate it better and get rid of the need for "fusermount -u". So my proposal is to either add the implementation of the "fusermount -u" functionality to mount, or let it execute "fusermount -u" as a subprocess for FUSE mountpoints. As root can already use umount for FUSE mount points, it probably doesn't need more than skipping the /etc/fstab test when umount is called on a FUSE mountpoint that is owned by the calling user. -- openSUSE Feature: https://features.opensuse.org/310710

1 6

[New: openFATE 309320] integrate mailinglist subscription with opensuse account
by fate_noreply＠suse.de 18 May '15

18 May '15

Feature added by: Ludwig Nussel (lnussel) Feature #309320, revision 1 Title: integrate mailinglist subscription with opensuse account Buildservice: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: [I know Buildservice as product is wrong but there's no opensuse.org] With my novell/opensuse account I can use the build service, wiki, lizards, fate, hermes etc all with one login. In order to subscribe to mailinglists I have to confirm my mail address for each list individually though. It would be more user friendly to optionally allow to log into lists.opensuse.org with my account (reusing the cookie for the other services) and subscribe to lists via mouse click, without extra email verification. -- openSUSE Feature: https://features.opensuse.org/309320

1 4