June 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309642] Hacking NetwotkManagement plasma applet
by fate_noreply＠suse.de 12 Aug '16

12 Aug '16

Feature added by: Alexander Naumov (Alexander_Naumov) Feature #309642, revision 1 Title: Hacking NetwotkManagement plasma applet Requested by: Alexander Naumov (alexander_naumov) Description: Trying to create a better support for wifi in NetworkManagement ;) -- openSUSE Feature: https://features.opensuse.org/309642

1 5

[New: openFATE 313139] One letter usernames
by fate_noreply＠suse.de 07 Aug '16

07 Aug '16

Feature added by: Mats Söderström (mazu) Feature #313139, revision 1 Title: One letter usernames openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Mats Söderström (mazu) Partner organization: openSUSE.org Description: The minimum allowed username length is two letters, I see no reason why this can't be changed to one. Business case (Partner benefit): openSUSE.org: To save hassle configuring ssh, nfs, etc. -- openSUSE Feature: https://features.opensuse.org/313139

1 2

[openFATE 307884] Yafaray instead of Yafray for Blender
by fate_noreply＠suse.de 07 Jun '16

07 Jun '16

Feature added by: Rene Bernhard (rebe) Feature #307884, revision 1 Title: Yafaray instead of Yafray for Blender Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Rene Bernhard (rebe) Description: Hello. As the Yafray render engine for Blender is not longer developed I apreciate if you would replace it with the Yafaray render engine in one of the next openSUSE versions. Or maybe it is possible to make a package for the repositories to download. Thank you very much for your efforts. Best regards rebe -- openSUSE Feature: https://features.opensuse.org/307884

1 4

[New: openFATE 312491] Explicit IPv6 support for YaST printer module
by fate_noreply＠suse.de 11 May '16

11 May '16

Feature added by: Johannes Meixner (jsmeix) Feature #312491, revision 1 Title: Explicit IPv6 support for YaST printer module openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: Currently there is not any kind of special IPv6 support in yast2-printer. Currently IPv6 works only where it is compatible to IPv4 but there are cases where IPv6 needs special handling: For example the tests whether or not a remote host is accessible run "ping <IP-address or hostname>" which fails if IP-address is an IPv6 address because for IPv6 ping6 must be used. See https://bugzilla.novell.com/show_bug.cgi?id=697833 Unfortunately ping6 cannot be used for IPv4 addresses so that yast2-printer needs to implement special distinction of cases in particular if a hostname is given depending on whether or not this hostname has an IPv4 or IPv6 address or both. Probably there are some more special distinction of cases needed to distinguish between IPv4 and IPv6 stuff. -- openSUSE Feature: https://features.opensuse.org/312491

1 20

[New: openFATE 308839] performance: prompt early on failure ...
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Michael Meeks (michael_meeks) Feature #308839, revision 1 Title: performance: prompt early on failure ... Buildservice: New Priority Requester: Mandatory Requested by: Michael Meeks (michael_meeks) Description: For local builds, osc has an unfortunate habit of doing a large amount of work, before failing very late. For slow building or leaf packages this can be excessively painful - wasting an "overnight" build slot eg. Many of the checks that we currently do in the middle, should be moved to the beginning (or perhaps just duplicated there). Some examples I have fallen over: * prompt-user-to-re-build-jail - this currently happens after any new packages are downloaded - a process that can take as long as the building. We can know that a jail was dirty before we start & warn then; if we even need dirty jails [cf. fate#308837# ] * simple RPM syntax problems - could be linted ahead of time, currently done after jail construction. + we should catch in particular: missing / mis-named files + mis-applied / not-applied patches + anything else obvious that we can catch Doing this early - while the human is watching is likely to hide long pipeline stalls, and context switching overhead for packagers. -- openSUSE Feature: https://features.opensuse.org/308839

1 3

[New: openFATE 313077] New PAM modules must not be deployed unnoticed by sec team
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Sebastian Krahmer (krahmer) Feature #313077, revision 1 Title: New PAM modules must not be deployed unnoticed by sec team openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sebastian Krahmer (krahmer) Partner organization: openSUSE.org Description: New PAM modules should be reviewed by security team. Just like any suid/daemon/DBUS service. In particular if they are installed by default. -- openSUSE Feature: https://features.opensuse.org/313077

1 4

[New: openFATE 311163] packaging firefox add-ons
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Ludwig Nussel (lnussel) Feature #311163, revision 1 Title: packaging firefox add-ons Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: We lack a way to be able to easily package firefox add-ons as rpm. Packages of add-ons are useful both for the distro vendor and for admins. Distro (or appliance) vendors may install some add-ons by default. Admins want all users to have certain add-ons by default. Moreover some add-ons are not noarch (like bonjourfoxy) and need to be compiled specifically for each distro so a package is unavoidable. To make all of that possible the firefox package needs to provide rpm macros so spec files for add-ons become really simple. By creating a script that downloads version, description etc from addons.mozilla.org and automatically creates spec files the task of packaging add-ons becomes a piece of cake. See home:lnussel:firefox for current status. -- openSUSE Feature: https://features.opensuse.org/311163

1 6

[New: openFATE 309362] Re-implement Download on Demand (DoD) feature
by fate_noreply＠suse.de 01 Mar '16

01 Mar '16

Feature added by: Adrian Schröter (adrianSuSE) Feature #309362, revision 1 Title: Re-implement Download on Demand (DoD) feature Buildservice: Done Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: The DoD features was dropped for 1.7. LinuxFoundation has re-implemented it in a cleaner way for 1.8 release. -- openSUSE Feature: https://features.opensuse.org/309362

1 8

[openFATE 305838] Integrate ReviewBoard in Buildservice
by fate_noreply＠suse.de 12 Feb '16

12 Feb '16

Feature added by: Klaas Freitag (kfreitag) Feature #305838, revision 1, last change by Title: Integrate ReviewBoard in Buildservice Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Klaas Freitag (kfreitag) Description: ReviewBoard is a code change review system. It should be considered to integrate it to the openSUSE Buildservice infrastructure to ease collaboration. It might be an option that submit requests to packages can be handled in the review board. -- openSUSE Feature: https://features.opensuse.org/305838

1 4

[New: openFATE 313233] Get Zypper to remove installed patterns
by fate_noreply＠suse.de 15 Jan '16

15 Jan '16

Feature added by: Drew Adams (Druonysus) Feature #313233, revision 1 Title: Get Zypper to remove installed patterns openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Drew Adams (druonysus) Partner organization: openSUSE.org Description: Get Zypper to remove a pattern. Zypper can install a pattern nut when going to remove that same pattern, Zypper does not remove that pattern... When do a: "zypper rm -t pattern <pattern name>" Zypper, just tells you: "Uninstallation of a pattern is currently not defined and implemented." You CAN remove a pattern in YaST so I would think that there should be a way to remove the pattern with Zypper. "yum groupremove <group name>" works on Fedora/CentOS/RHEL... we should really have this working to keep up with them. Use Case: If I build a bare openSUSE image on SUSE Studio, and I decide not to install yast and only Zypper... I will only be able to install patterns but NO way to remove it. -- openSUSE Feature: https://features.opensuse.org/313233

1 2