- openSUSE Features

[openFate 305080] Enable runlevel 4
by fate_noreply＠suse.de 18 Jul '08

18 Jul '08

Feature changed by: Peter Bowen (pzb(a)novell.com) Feature #305080, revision 4 Title: Enable runlevel 4 openSUSE-11.1: New Priority Requester: Important SLED-11-SP1: New Priority Requester: Important SLES-11-SP1: New Priority Requester: Important Requested by: Peter Bowen (pzb(a)novell.com) + Partner organization: openSUSE.org Description: Currently we do disable runlevel 4. We should update the inittab to enable runlevel 4 and update initscripts to run at 4 if they run at 3. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305080

1 0

[openFate 305018] Get bugowner ID from buildservice without login
by fate_noreply＠suse.de 18 Jul '08

18 Jul '08

Feature changed by: Michael Loeffler (michl(a)novell.com) Feature #305018, revision 3 Title: Get bugowner ID from buildservice without login - Buildservice: New + Buildservice: Evaluation Priority Requester: Desirable Requested by: Jan Blunck (jblunck(a)novell.com) Partner organization: openSUSE.org Description: For automatic crash reporting it is useful to get information about the buildservice project the package is coming from. If the bugowner is set by the project the report can be assigned to him. If the bugowner is not set the crash report can be skipped. I need a way to get the bugowner id or email adress without forcing the user to have a buildservice login. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305018

1 0

[openFate 303873] Reducing pop ups during installation
by fate_noreply＠suse.de 18 Jul '08

18 Jul '08

Feature changed by: Michael Loeffler (michl(a)novell.com) Feature #303873, revision 11 Title: Reducing pop ups during installation openSUSE-11.1: Rejected by Stanislav Visnovsky(visnov(a)novell.com) reject date: 2008-07-08 11:01:26 reject reason: This can wait. Postponing. Priority Requester: Important - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Important SLED-11: Rejected by Stanislav Visnovsky(visnov(a)novell.com) reject date: 2008-07-08 11:01:16 reject reason: This can wait. Postponing. Priority Requester: Important SLED-11-SP1: New Priority Requester: Important SLES-11: Rejected by Stanislav Visnovsky(visnov(a)novell.com) reject date: 2008-07-08 11:01:18 reject reason: This can wait. Postponing. Priority Requester: Important SLES-11-SP1: New Priority Requester: Important Requested by: Martin Schmidkunz (mschmidkunz(a)novell.com) + Partner organization: openSUSE.org Description: Before installing the system the user is asked to confirm various licenses. Each license is presented via pop up. Depending on the selected packages the user might be forced to accept quite a lot of them. This is quite unusable and we should think about how to reduce these. One idea might be: http://en.opensuse.org/Image:Installation_nopopups.png Not for SLES: Furthermore after accepting all these licenses the user has to confirm the installation in an extra pop up. I do not see the necessity for that pop up as users made the experience with other operating systems who do not ask the user for comfirmation (Apple Mac OS, MS Windows, Ubuntu, Red Hat Enterprise Linux, Fedora) that installation means that something will happen to their hard drive. Discussion: #1: Matthias Eckermann(mge(a)novell.com) (2008-05-15 12:10:27) I agree with and like: http://en.opensuse.org/Image:Installation_nopopups.png But the extra pop-up for "YES, I really want to wipe my harddisk" must remain, as it is a security and safetiness issue. Marking this part of the idea as "Not for SLES". Federico, what is your opinion here? #2: Michael Loeffler(michl(a)novell.com) (2008-05-15 12:27:44) Ciaran can you give the view from a legal perspective? #3: Ciaran Farrell(cfarrell(a)novell.com) (2008-05-16 11:51:38) I like the setup described in the screenshot and believe that it certainly gives the person installing the opportunity to review every license individually. In fact, I'm going to suggest to Patrick Mc Bride that this could be a default license acceptance method as it is far better than what we currently have available (i.e. all or nothing system). I'll ask Christopher De Nicolo for his opinion (from a german legal perspective). #4: Federico Lucifredi(flucifredi(a)novell.com) (2008-05-22 15:47:44) I just went through the 11.0 beta 3 workflow, and I am satisfied with the current state. the mock-up is ok, but consider this: while it is true that you get prompted 5 times to approve licenses, if there is something that users are trained to do, in all platforms, is precisely click accept :-) I would say we can proceed with it, but I don't consider it a major issue, and not a usability problem. by the way, the 11.0 install workflow rocks :-) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303873

1 0

[openFate 305018] Get bugowner ID from buildservice without login
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Adrian Schröter (adrian(a)novell.com) Feature #305018, revision 2 Title: Get bugowner ID from buildservice without login Buildservice: New Priority Requester: Desirable Requested by: Jan Blunck (jblunck(a)novell.com) + Partner organization: openSUSE.org Description: For automatic crash reporting it is useful to get information about the buildservice project the package is coming from. If the bugowner is set by the project the report can be assigned to him. If the bugowner is not set the crash report can be skipped. I need a way to get the bugowner id or email adress without forcing the user to have a buildservice login. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305018

1 0

[openFate 305015] support noarch via own scheduler in Build Service
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Adrian Schröter (adrian(a)novell.com) Feature #305015, revision 2 - Title: support noarch via own scheduler in internal Build Service + Title: support noarch via own scheduler in Build Service Buildservice: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adrian(a)novell.com) Requested by: Lars Vogdt (lrupp(a)novell.com) + Partner organization: openSUSE.org Description: We would like to build noarch packages only once to avoid multiple builds and wasted space on the server. This can be reached by building noarch packages only via an dedicated scheduler. However, we need to avoid that have a horrible project configuration, where all BuildRequired noarch packages needs to get submitted into all other architecture repository :full trees. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305015

1 0

[openFate 304928] LSB build target
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Adrian Schröter (adrian(a)novell.com) Feature #304928, revision 11 Title: LSB build target Buildservice: Evaluation Priority Requester: Important Requested by: Adrian Schröter (adrian(a)novell.com) Requested by: Michael Loeffler (michl(a)novell.com) + Partner organization: openSUSE.org Description: A LSB build target is requested from PM. This does mean we need * A usable base distribution, which avoids to generate binaries with non-LSB requirements. * Additional LSB validation checks packaged. We could integrate these as rpmlint checks for example. Jiri, how can we setup such a distribution, using selected packages from a SUSE distro plus lsb-build-cc as compiler ? Jiri, can you package the lsb validation checks as rpmlint packages or shall we run them in a different way ? Discussion: #1: Jiri Dluhos(jdluhos(a)novell.com) (2008-06-18 13:55:50) The task has two sides: Checking binaries for LSB compliance is relatively easy; I will investigate how the checks could be incorporated into rpmlint. Building in LSB-pure environment is a conceptually different, and significantly more complex task. We have already tried to implement a pure LSB build target for buildservice, but the straightforward strategy failed because LSB-pure environment is too restricted to build essential system binaries (like mount). The Linux Foundation uses a specially crafted host distro for their builds, which is not LSB compliant per se, and then do an additional round of checks and purifications on the built binaries. We can mimic this process. #2: Jiri Dluhos(jdluhos(a)novell.com) (2008-06-18 14:23:32) What we will need is probably the lsbappchk tool from the LSB Application Testkit (downloadable at http://www.linuxfoundation.org/en/Download (http://www.linuxfoundation.org/en/Download) ). I will look at the sources to see if we can easily build it on- site. #3: Jiri Dluhos(jdluhos(a)novell.com) (2008-06-18 15:51:49) For the record (and for the curious :-) ), the database of LSB- compliant interfaces is here: http://bzr.freestandards.org/lsb/devel/specdb (http://bzr.freestandards.org/lsb/devel/specdb) #4: Darren Davis(ddavis(a)novell.com) (2008-06-30 07:55:35) I would also be nice if after they build their LSB Compliant Application in the Build Service, that they could also do the part of submitting the results for the LSB Navigator that the ATK provides. https://www.linuxfoundation.org/dbadmin/commons/welcome.php #5: Gerald Pfeifer(gp(a)novell.com) (2008-06-30 22:53:24) Michl is out right now, so let me play Michl on TV. Important for PM, and on to Adrian. ;-) #6: Martin Mrazik(mmrazik(a)novell.com) (2008-07-01 06:08:50) (reply to #5) Maybe before evaluating this it would be better to split this fate entry into two: * Create a LSB build target * Package ATK and integrate with rpmlint -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304928

1 0

[openFate 303559] @opensuse.org mail forward support in users.opensuse.org
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Adrian Schröter (adrian(a)novell.com) Feature #303559, revision 2 Title: @opensuse.org mail forward support in users.opensuse.org Buildservice: New Priority Requester: Mandatory Requested by: Adrian Schröter (adrian(a)novell.com) + Partner organization: openSUSE.org Description: We have the request to support the membership management of opensuse. org via users.opensuse.org. This require the following: * Admin (can be defined via hard coded list for now) can enable a "Membership Flag" for dedicated users. * Users with Membership Flag can enter an email forwarding adress. * Regular export of forwarding adresses for Boetti to support the new forwarders. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303559

1 0

[openFate 303520] Default NTP Setup
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Martin Vidner (mvidner(a)novell.com) Feature #303520, revision 14 Title: Default NTP Setup SLED-11: Candidate Priority Requester: Mandatory Projectmanager: Mandatory SLES-11: Candidate Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Federico Lucifredi (flucifredi(a)novell.com) + Partner organization: openSUSE.org Description: A Yast pane should prompt for NTP set up, which should be configured by default, but of course can also be disabled there. Documentation Impact: Installation guide needs to be updated. Discussion: #1: Stanislav Visnovsky(visnov(a)novell.com) (2008-06-17 12:56:47) Federico, NTP setup is already possible. Do you want it in a more prominent place? Also I see a missing way for the product to pre-define the value, correct? #2: Federico Lucifredi(flucifredi(a)novell.com) (2008-06-23 21:03:12) (reply to #1) right. I want to see it pre-enabled by default againt a dedicated suse. pool.ntp.org / time.novell.com server (separate feature for that). We are lagging a bit behind Win and Mac where the vendos provide their own time source, and we need to catch up there. #3: Jiri Srain(jsrain(a)novell.com) (2008-07-07 12:18:32) We will need not only to enable NTP during installation, but display this information in the installation proposal (and possibly time zone dialog) as well. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303520

1 0

[openFate 302119] Load package selector and libzypp only when needed
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Martin Vidner (mvidner(a)novell.com) Feature #302119, revision 24 Title: Load package selector and libzypp only when needed openSUSE-10.3: Rejected by Stanislav Visnovsky(visnov(a)novell.com) reject date: 2007-08-01 16:40:54 reject reason: Postponing. Priority Requester: Desirable Projectmanager: Important openSUSE-11.0: Rejected by Stanislav Visnovsky(visnov(a)novell.com) reject date: 2008-04-28 13:42:30 reject reason: Did not make it, postponing. Priority Requester: Desirable Projectmanager: Important openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: Important Requested by: Stefan Hundhammer (sh(a)novell.com) + Partner organization: openSUSE.org Description: The YaST2 UI should load the code for the package selector and libzypp only when needed. Not all applications / YaST2 modules need package selection code, yet for all of them the respective code from the YaST2 UI and libzypp is loaded. Discussion: #1: Stefan Hundhammer(sh(a)novell.com) (2007-04-13 18:13:44) In the YaST2 Qt the package management related code is now moved to a separate plugin that is loaded upon demand only if the calling YCP application actually requests a PackageSelector widget. This reduces the memory footprint from 20 MB VmRSS minimum (HelloWorld. ycp) to 18 MB minimum (PackageSelector-empty.ycp). #3: Katarina Machalkova(kmachalkova(a)novell.com) (2007-04-16 14:41:35) Stano, do we want this for curses UI as well? If yes, than it's not 'done' ... #4: Stanislav Visnovsky(visnov(a)novell.com) (2007-04-16 14:47:02) (reply to #3) Agreed. Reopening for ncurses and possibly gtk+. #5: Jiri Srain(jsrain(a)novell.com) (2007-06-13 13:54:26) JP, both Qt and NCurses are done, but GTK is still missing. #6: Stefan Hundhammer(sh(a)novell.com) (2007-06-13 15:08:58) Looks like yast2-pkg-bindings are also loaded unconditionally. It shouldn't be too hard to do that with "lazy initialization" like UI built-ins: Postpone loading the Y2Component until it's really needed. #7: Stanislav Visnovsky(visnov(a)novell.com) (2007-06-19 15:01:54) (reply to #6) Jiri, if Pkg bindings problem is not addressed, it does not make sense to fix Gtk UI. #8: Jiri Srain(jsrain(a)novell.com) (2007-07-18 13:59:50) (reply to #7) Sorry for missing this. Martin, please, solve this for the Pkg bindings. #10: Stanislav Visnovsky(visnov(a)novell.com) (2007-11-08 11:38:22) (reply to #9) Please, follow up on this. #11: Martin Vidner(mvidner(a)novell.com) (2008-04-10 15:23:51) yast2-perl-bindings-2.16.6 no longer links to libzypp, which means libzypp will not be loaded at the very start of yast (perl still will be loaded, but that is relatively cheap). That helps in some cases, but mostly it only delays loading of libzypp, which occurs as soon as Pkg (or Package) is imported. Now I need to make Pkg lazy. #12: Martin Vidner(mvidner(a)novell.com) (2008-04-21 15:32:09) I have it almost working, but got stopped by bug 381917 (https://bugzilla.novell.com/show_bug.cgi?id=381917) : problems with destructors of static objects -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=302119

1 0

[openFate 304889] needs_relogin/needs_reboot as a generic flag
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Martin Vidner (mvidner(a)novell.com) Feature #304889, revision 10 Title: needs_relogin/needs_reboot as a generic flag openSUSE-11.1: Candidate Priority Requester: Neutral Projectmanager: Mandatory Requested by: Stanislav Brabec (sbrabec(a)novell.com) + Partner organization: openSUSE.org Description: There are situations, where relogin or reboot are needed to activate update: * package updates * proxy settings Now this situation is not done in a consistent way (silently ignoring problem, note in help, abuse of License entry, pop-up...). Providing a common way for setting these flags (via package provides, YaST calls, sysconfig comments) (and maybe comment what will happen ignoring it) would help in user experience (user is notified about need of relogin/reboot in a consistent way and only once) and administration (automatic relogin or reboot during maintenance window). Discussion: #1: Stanislav Visnovsky(visnov(a)novell.com) (2008-06-26 14:15:12) needs_reboot is properly handled by our tools. needs_relogin does not exist. #2: Jiri Srain(jsrain(a)novell.com) (2008-07-07 10:46:59) (reply to #1) We handle reboot only for package management not for anything else (the question is whether it is relevant somewhere else), thus we will need to have a more generic solution. Martin, would you, please, have a look and suggest a generic handler? #3: Stanislav Brabec(sbrabec(a)novell.com) (2008-07-09 15:26:16) needs_relogin would be useful in these situations: * New package, which provides file in /etc/profile.d was installed (or /etc/profile.d was singnificantly modified by the update). Example: ladspa * Packages, that cause that /etc/profile will evaluate environment. Example: Install any KDE application in GNOME only system. /opt/kde3 is not in PATH until next login * Patches, that affect login related programs. Example: security update of ssh-agent or gnome-keyring * YaST settings, that cause environment variable changes. Example: System proxy settings -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304889

1 0