July 2008 - openSUSE Features - openSUSE Mailing Lists

[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 303700] Ability to log all configuration changes done via YaST
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Martin Vidner (mvidner(a)novell.com) Feature #303700, revision 12 Title: Ability to log all configuration changes done via YaST openSUSE-11.1: Candidate Priority Requester: Mandatory Projectmanager: Mandatory SLED-11: Candidate Priority Requester: Mandatory Projectmanager: Mandatory SLES-11: Candidate Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Matthias Eckermann (mge(a)novell.com) + Partner organization: openSUSE.org Description: Provide the ability to log all configuration changes done via YaST. Additionally, in this mode an admin would be prompted to document what was the nature/purpose of the change as the module is being closed, akin to commit messages in a versioning system. Documentation Impact: The new log file needs to be documentated in admin guide. Discussion: #1: Federico Lucifredi(flucifredi(a)novell.com) (2008-04-30 15:27:04) note fate 303688 related: packaging CFT. I am not sure CFT is the right way to provide this functionality, but a consideration is that an admin using CFT will probably log both manual-editing and YaST-driven conf changes via the same tool. #2: Stanislav Visnovsky(visnov(a)novell.com) (2008-06-03 12:40:41) Duncan, Jiri, this might be an architectural change, please, look into this. Also, we might need to define scope of which changes we are able to track. #3: Jiri Srain(jsrain(a)novell.com) (2008-07-07 10:45:35) Martin, please, have a look at possibilities to record all changes and suggest an infrastructure. Federico, we will hardly be able to make all modules record all the changes they do. Could you, please, give us some priorities for SLE11? #4: Martin Vidner(mvidner(a)novell.com) (2008-07-08 11:44:54) This looks like a superset of feature 100386. Note that that one was downgraded because it is large (it requires touching all YaST modules). #5: Stanislav Visnovsky(visnov(a)novell.com) (2008-07-08 12:08:56) (reply to #4) Please, look into enabling of the stuff, not covering all YaST modules. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303700

1 0

[openFate 100386] Support a verbose logging mode in yast
by fate_noreply＠suse.de 17 Jul '08

17 Jul '08

Feature changed by: Martin Vidner (mvidner(a)novell.com) Feature #100386, revision 27 Title: Support a verbose logging mode in yast openSUSE-10.2: Rejected by Andreas Jaeger(aj(a)novell.com) reject date: 2006-09-30 20:43:33 reject reason: for 10.3. Priority Requester: Desirable Projectmanager: Desirable openSUSE-10.3: Rejected by Stanislav Visnovsky(visnov(a)novell.com) reject date: 2007-08-01 10:24:26 reject reason: Postponing, needs more research. Priority Requester: Important Projectmanager: Important openSUSE-11.0: Rejected by Federico Lucifredi(flucifredi(a)novell.com) reject date: 2008-06-28 19:27:16 reject reason: fixing my typo. Mandatories in the past don't work (yet). Priority Requester: Important Projectmanager: Important openSUSE-11.1: Candidate Priority Requester: Important Projectmanager: Important SL-10.0: Rejected by Andreas Jaeger(aj(a)novell.com) reject date: 2005-12-02 14:56:13 reject reason: not done. Priority Requester: Desirable SLES-11: Candidate Priority Requester: Important Projectmanager: Important Requested by: Andreas Jaeger (aj(a)novell.com) + Partner organization: openSUSE.org Description: Create a verbose logging mode in yast, where any action yast performs is logged. Any file yast touches should be logged (to /var/log/YaST2/y2log AND clean up the structure of that log file, to make it easier to read and interpret) and all changes on the systems configuration. The goal is to make it really transparent what yast does. Documentation Impact: Admin guide needs to contain information about the new log file. Discussion: #1: Edith Parzefall(emap(a)novell.com) (2006-09-28 17:17:54) Can't be done for 10.2. Back to TPMs. #2: Edith Parzefall(emap(a)novell.com) (2007-07-31 16:17:45) Sorry, couldn't be done for 10.3. We need a concept for this. Even within the team different developers have different needs. Improving the logging to give all developers the best possible debugging information will be difficult, but it's definitely something we should attempt in the near future. #3: Stanislav Visnovsky(visnov(a)novell.com) (2007-11-08 10:48:48) Can we get some traction here finally? #4: Stanislav Visnovsky(visnov(a)novell.com) (2007-11-28 10:16:38) Reopening, the YaST transparency is often cited as a problem for users. #6: Federico Lucifredi(flucifredi(a)novell.com) (2008-06-28 17:13:54) I think this has enough user benefit and is trivial enough, we should just get it done. #7: Federico Lucifredi(flucifredi(a)novell.com) (2008-06-28 19:28:04) PM-Priority for product openSUSE-11.0 downgraded from mandatory to : oops. Too many widgets for my tired brain. #8: Stanislav Visnovsky(visnov(a)novell.com) (2008-07-01 16:49:08) (reply to #7) This cannot be done completely - this is non-trivial amount of work. I suggest to start this though, having the YaST infrastructure in place ASAP. Federico, please, downgrade the priority. #9: Federico Lucifredi(flucifredi(a)novell.com) (2008-07-02 14:01:05) PM-Priority for product SLES-11 downgraded from mandatory to important: too much work for a one-off apparently. #10: Federico Lucifredi(flucifredi(a)novell.com) (2008-07-02 14:01:27) PM-Priority for product openSUSE-11.1 downgraded from mandatory to important: too much work for a one-shot. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=100386

1 0