June 2008 - openSUSE Features - openSUSE Mailing Lists

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature changed by: aj Feature #304395, revision 8 Title: Disabling (or handling) screensaver during installation - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Desirable Requested by: locilka(a)novell.com Partner organization: openSUSE.org Description: We currently have screen-saver active during installation/upgrade. This is a bit problematic when some exception occurs and opens a pop-up window requesting some user-decision (Abort/Retry/Ignore/...). On slower networks, installation can take tens of minutes, even a few hours. It would be nice to disable the screen-saver (easy) or at least handle all the exceptions by disabling the screen-saver. References: Bug 393890 - How to disable screen blank during installation https://bugzilla.novell.com/show_bug.cgi?id=393890 Black monitor (thread): "The screen suudenly went black" http://lists.opensuse.org/opensuse-factory/2008-05/msg00675.html Use Case: Installation on slower computer and/or via slower network Discussion: #1: aschnell(a)novell.com (2008-05-27 15:10:07) On slow computers people might actually want the screensaver. Suppose you start the installation and go home or sleeping: I would expect that the monitor powers off after some time. We could add a call "xset dpms force on" to popups. But I doubt that this is worth the effort. #2: locilka(a)novell.com (2008-05-27 15:43:16) (reply to #1) Bug 393890 says exactly: During installation the screen will blank when for some period no keyboard and mouse activity is recognized. The drawback is, that you will not notice error messages that pop up. So one has to move the mouse every 5 minutes or so and is bound to the installation. It would be cool, if we could either do not blank the screen at all, or "deblank" it, when a error message pops up. ... and Stefan Hundhammer adds: The screen saver should be off during installation. Why would there be any exception to this rule? (It's not even that screen savers serve their real purpose these days - it was an issue with old (very old) CRT monitors that could "burn in" images that would be displayed for a long, long time - and then, we are talking about months, not about hours). #3: sh(a)novell.com (2008-05-27 16:10:19) (reply to #1) aschnell wrote: On slow computers people might actually want the screensaver. Suppose you start the installation and go home or sleeping: I would expect that the monitor powers off after some time. When I go home during such a lengthy operation, what's wrong with simply turning the monitor off? This is the most natural and the simplest thing to do. #4: sh(a)novell.com (2008-05-27 16:18:21) See also Bug #393890 (https://bugzilla.novell.com/show_bug.cgi?id=393890) Changing screen saver settings in a widget toolkit (!) such as the YaST2 Qt UI would affect ALL applications written with that toolkit. Right now, that's all YaST2 modules, but since this UI is now available as a general toolkit, you'll never know what other applications this might affect in the future. An X11 application is not to change the user's screen saver settings (unless it is a dedicated application to configure screen saver settings, of course), much less silently in the background. We'd get a lot of surprised and very angry users, and they would have every right to be angry with us. You wouldn't even be able to find out why your screen saver doesn't work any more. #5: locilka(a)novell.com (2008-05-27 16:27:02) (reply to #4) The feature request is about installation, not about running system. But it's a good point that we should not change that in general... (the whole toolkit). Thanks. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

[Fate 303738] yast repository manager should be able to import .repo files
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature changed by: aj Feature #303738, revision 3 Title: yast repository manager should be able to import .repo files - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Desirable Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: It should be possible to add a repository defined in a .repo file. This functionlity is already implemented in zypper. References: https://bugzilla.novell.com/show_bug.cgi?id=384195 Discussion: #1: dmacvicar(a)novell.com (2008-04-28 17:48:42) Actually the functionallity is implemented in libzypp. RepoManager::addRepositories( const Url &url, const ProgressData:: ReceiverFnc & progressrcv = ProgressData::ReceiverFnc() ); there you pass the url of the repo file (which can contain multipla repositories). -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303738

1 0

[Fate 303736] yast and libzypp should respect the disk space reserved for root
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature changed by: aj Feature #303736, revision 4 Title: yast and libzypp should respect the disk space reserved for root - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Desirable Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: If e.g. root partition has 70MB free user space and 500MB free space reserved for root user yast reports 570MB total free space. But installation of a package which is greater than 70MB fails: installing package kdelibs3-devel-doc-3.5.5-45 needs 335MB on the / filesystem Yast should display the non-root free space (70MB in this case). It seems that it is valid only for ext2/ext3 filesystems (XFS and ReiserFS seem to not support root space). Default reserved space for ext2/ext3 is 5%. References: https://bugzilla.novell.com/show_bug.cgi?id=237309 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303736

1 0

[Fate 303527] Resolve dependencies after ignoring package download failure
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature changed by: aj Feature #303527, revision 6 Title: Resolve dependencies after ignoring package download failure - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Desirable Requested by: jkupec(a)novell.com Partner organization: openSUSE.org Description: YaST and Zypper should run the solver before resuming installation if download of a package fails and the user chooses to ignore that package. Currently YaST continues withough solving which makes the ignore button useful only if the user knows how the missing package will affect the system. References: https://bugzilla.novell.com/show_bug.cgi?id=340345#c4 http://lists.opensuse.org/zypp-devel/2008-03/msg00025.html -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303527

1 0

[Fate 302354] Split metadata by architecture / modules
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature changed by: aj Feature #302354, revision 8 Title: Split metadata by architecture / modules openSUSE-11.0: Rejected by visnov(a)novell.com reject date: 2008-03-28 16:28:18 reject reason: Out of resources. The speed of parsing is greatly improved, downloading is still an issue in 11.0. Priority Requester: Important - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Important Requested by: visnov(a)novell.com Partner organization: openSUSE.org Description: All packages are in a single file no matter if they are from different architectures, therefore ZYpp has to download everything Any kind of metadata should be separated by architecture. ZYpp does it for patterns in 10.3, but it is still missing for packages The metadata should be ideally separated by subdirectories and modules. See references on how debian does it References: https://bugzilla.novell.com/show_bug.cgi?id=208452 Discussion: #1: dmacvicar(a)novell.com (2007-11-09 16:52:55) This is not true, YaST filter patterns in 10.3. Will edit the feature to represent the real problems -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302354

1 0

[Fate 304429] Package cache handling in yast
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature changed by: aj Feature #304429, revision 2 Title: Package cache handling in yast - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Important - SLES-11: New + SLES-11: Evaluation Priority Requester: Important Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: Add a possibility to edit 'keeppackages' option in *.repo files. The downloaded packages are not kept by default, but it should be configurable by user. The question is how it should be configurable. My suggestions are a check box or an extra menu item in the repositoru manager (repositories. ycp) . References: https://bugzilla.novell.com/show_bug.cgi?id=393709 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304429

1 0

[Fate 302047] Integrated package searching for YaST and build service
by fate_noreply＠suse.de 10 Jun '08

10 Jun '08

Feature changed by: michl Feature #302047, revision 22 Title: Integrated package searching for YaST and build service openSUSE-10.3: Rejected by aj(a)novell.com reject date: 2007-10-05 14:30:28 reject reason: still open partly - postpone the rest. Priority Requester: Important Projectmanager: Important - openSUSE-11.0: Evaluation + openSUSE-11.0: Rejected by michl(a)novell.com + reject date: 2008-06-10 14:01:45 + reject reason: not done for 11.0 Priority Requester: Important Projectmanager: Important openSUSE-11.1: Evaluation Priority Requester: Important Requested by: dmacvicar(a)novell.com Partner organization: openSUSE.org Description: You perhaps remember the hacks Benjamin did to support Â "click and install" packages (similar to Click'n run) [1] Benjamin has another article in his blog that is worth to read. He has been providing a wepage to search packages from repositories like packman and build service. Now he presents an architecture to desentralize the system, using web services an indexers, and he shows working prototypes of YaST modules for searching, and others like web and irc-bot clients http://blogs.warwick.ac.uk/bweber/entry/package_search_developments/ I hope we can provide a strategy and roadmap to integrate these cool ideas and _code_. Â [1]: http://blogs.warwick.ac.uk/bweber/entry/next_generation_package/ Discussion: #1: jw(a)suse.de (2007-05-03 15:29:13) see also 300898 For 10.3 the installer should be able to make use of an external list of repositories. I suggest to host such a list at http://packages.opensuse-community.org/ together with the search engine, which is already there. #3: freitag(a)novell.com (2007-07-12 10:46:54) Implementation on openSUSE BS already started, Adrian knows the details. #4: adrian(a)novell.com (2007-07-12 11:30:04) We work on two approaches atm: * YaST will support (thanks to mvidner) additional repository offers during installation. The list gets hosted on our servers, the open question is how to maintain this list. * The build service End-User interface will offer .ymp files based on pattern submissions for easy installation. #5: visnov(a)novell.com (2007-07-30 20:13:09) (reply to #4) Adrian, please, drive this. The feature for YaST should be done now (let me know if anything is missing). #6: michl(a)novell.com (2007-11-22 11:26:30) This sounds like very useful. And it might be possible the community (in this case Benji) helps implementing this. #7: aj(a)novell.com (2008-06-06 10:56:28) Apparently not done - please reject and postpone for 11.1. + #8: michl(a)novell.com (2008-06-10 14:02:08) + PM-Priority for product openSUSE-11.0 downgraded from mandatory to + important: + not done for 11.0 - PM accepts reality ;-) -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302047

1 0

[Fate 302047] Integrated package searching for YaST and build service
by fate_noreply＠suse.de 06 Jun '08

06 Jun '08

Feature changed by: aj Feature #302047, revision 21 Title: Integrated package searching for YaST and build service openSUSE-10.3: Rejected by aj(a)novell.com reject date: 2007-10-05 14:30:28 reject reason: still open partly - postpone the rest. Priority Requester: Important Projectmanager: Important openSUSE-11.0: Evaluation Priority Requester: Important Projectmanager: Important + openSUSE-11.1: Evaluation + Priority + Requester: Important Requested by: dmacvicar(a)novell.com Partner organization: openSUSE.org Description: You perhaps remember the hacks Benjamin did to support Â "click and install" packages (similar to Click'n run) [1] Benjamin has another article in his blog that is worth to read. He has been providing a wepage to search packages from repositories like packman and build service. Now he presents an architecture to desentralize the system, using web services an indexers, and he shows working prototypes of YaST modules for searching, and others like web and irc-bot clients http://blogs.warwick.ac.uk/bweber/entry/package_search_developments/ I hope we can provide a strategy and roadmap to integrate these cool ideas and _code_. Â [1]: http://blogs.warwick.ac.uk/bweber/entry/next_generation_package/ Discussion: #1: jw(a)suse.de (2007-05-03 15:29:13) see also 300898 For 10.3 the installer should be able to make use of an external list of repositories. I suggest to host such a list at http://packages.opensuse-community.org/ together with the search engine, which is already there. #3: freitag(a)novell.com (2007-07-12 10:46:54) Implementation on openSUSE BS already started, Adrian knows the details. #4: adrian(a)novell.com (2007-07-12 11:30:04) We work on two approaches atm: * YaST will support (thanks to mvidner) additional repository offers during installation. The list gets hosted on our servers, the open question is how to maintain this list. * The build service End-User interface will offer .ymp files based on pattern submissions for easy installation. #5: visnov(a)novell.com (2007-07-30 20:13:09) (reply to #4) Adrian, please, drive this. The feature for YaST should be done now (let me know if anything is missing). #6: michl(a)novell.com (2007-11-22 11:26:30) This sounds like very useful. And it might be possible the community (in this case Benji) helps implementing this. + #7: aj(a)novell.com (2008-06-06 10:56:28) + Apparently not done - please reject and postpone for 11.1. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302047

1 0

[Fate 302923] handle redirection to mirrors robustly
by fate_noreply＠suse.de 06 Jun '08

06 Jun '08

Feature changed by: mge Feature #302923, revision 6 Title: handle redirection to mirrors robustly openSUSE-11.0: Rejected by visnov(a)novell.com reject date: 2007-11-28 15:42:20 reject reason: Out of scope for 11.0 Priority Requester: Neutral - SLED-11: New + SLED-11: Evaluation Priority Requester: Neutral - SLES-11: New + SLES-11: Evaluation Priority Requester: Neutral Requested by: jkupec(a)novell.com Partner organization: openSUSE.org Description: The proposal is to try other mirrors from a mirror list (from the redirector?) if an error occurs on some of the mirrors while providing a file from http/ftp repository. See the references for more details. References: https://bugzilla.novell.com/show_bug.cgi?id=337410 http://lists.opensuse.org/opensuse-buildservice/2007-10/msg00170.html Discussion: #1: coolo(a)novell.com (2007-11-20 11:15:49) I would be strictly against having an own mirror list. The decision was to go with the redirector (or NCC for SLE) and be done with mirrors. If that does not work, then we have to do this whole thing again, not adding untested work arounds to the product. #2: coolo(a)novell.com (2007-11-20 11:16:55) so I would reject this. But it's basically "Eval by Klaas" now #3: freitag(a)novell.com (2007-12-03 09:49:44) I agree with Coolos and Peters statements, I would also reject. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302923

1 0