June 2008 - openSUSE Features - openSUSE Mailing Lists

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

16 Jun '08

Feature changed by: jkupec Feature #303527, revision 8 Title: Resolve dependencies after ignoring package download failure 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 Discussion: #1: flucifredi(a)novell.com (2008-06-13 15:13:41) bit of a corner case. + #2: jkupec(a)novell.com (2008-06-16 11:44:24) + Well, yes. An idea to cover it easily to some extent: let's advice + users to run 'zypper verify' (or the YaST equivalent) in such case, + after the installation is finished. This will fix hard dependencies. -- 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 14 Jun '08

14 Jun '08

Feature changed by: flucifredi Feature #302354, revision 9 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: 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 + #2: flucifredi(a)novell.com (2008-06-13 20:22:10) + Duncan, do we still need this / have an advantage from it ? if so, lets + make it Mandatory. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302354

1 0

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

13 Jun '08

Feature changed by: flucifredi Feature #304395, revision 9 Title: Disabling (or handling) screensaver during installation 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. + #6: flucifredi(a)novell.com (2008-06-13 17:42:27) + ...and we should look at powersave behavior too during these + operations. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

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

13 Jun '08

Feature changed by: flucifredi Feature #303527, revision 7 Title: Resolve dependencies after ignoring package download failure 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 + Discussion: + #1: flucifredi(a)novell.com (2008-06-13 15:13:41) + bit of a corner case. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303527

1 0

[Fate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 13 Jun '08

13 Jun '08

Feature changed by: flucifredi Feature #303517, revision 3 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Evaluation Priority Requester: Desirable Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: Autorefresh configured repositories at certain times, this could be on certain days, or time of day, etc. A mockup and more details are in https://bugzilla.novell.com/show_bug.cgi?id=346966 + Discussion: + #1: flucifredi(a)novell.com (2008-06-13 15:12:52) + there are some caveats I can think of requiring silent fail (for + instance, a laptop), or requiring randomization (not hitting NCC with a + volley all at the same time), but I think the idea is good. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303517

1 0

[Fate 304911] Import all GPG keys at once before downloading the metadata from new repositories
by fate_noreply＠suse.de 13 Jun '08

13 Jun '08

Feature added by: lslezak Feature #304911, revision 1 Title: Import all GPG keys at once before downloading the metadata from new repositories openSUSE-11.1: New Priority Requester: Desirable Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: If e.g. 10 different repositories are added yast asks to import the GPG key for each repository so the user cannot leave the computer while the metadata are downloaded. References: https://bugzilla.novell.com/show_bug.cgi?id=399253 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304911

1 0

[Fate 303678] New yast module - LIRC configuration
by fate_noreply＠suse.de 13 Jun '08

13 Jun '08

Feature changed by: aj Feature #303678, revision 4 Title: New yast module - LIRC configuration - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Desirable Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: Create a new Yast module for configuring IR receivers and remote controls. * irrecord support * ir-kbd-i2c, ir-kbd-gpio support as in tv module already * reading users' config to find out what buttons were defined (only if /home partition left from last installation) * support for lirc's options in /etc/sysconfig See bug https://bugzilla.novell.com/show_bug.cgi?id=381641 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303678

1 0

[Fate 302921] Testing openSUSE Feature Tracking
by fate_noreply＠suse.de 12 Jun '08

12 Jun '08

Feature changed by: aj Feature #302921, revision 21 Title: Testing openSUSE Feature Tracking - openSUSE-10.3: Evaluation + openSUSE-10.3: Done Priority Requester: Mandatory Requested by: aj(a)novell.com Partner organization: openSUSE.org Description: Just a test - should go to opensuse-features(a)opensuse.org Discussion: #1: hvogel(a)novell.com (2007-10-30 13:00:36) blah blah blah #2: hvogel(a)novell.com (2007-10-30 13:02:35) (reply to #1) blubb lubb lbuib #13: hvogel(a)novell.com (2007-10-30 13:57:04) (reply to #1) dsdsdwsd #14: hvogel(a)novell.com (2007-10-30 13:59:12) (reply to #13) wsdsdsds #15: hvogel(a)novell.com (2007-10-30 14:01:10) (reply to #13) dsdsds #16: hvogel(a)novell.com (2007-10-30 14:11:35) (reply to #13) ddsddds #3: hvogel(a)novell.com (2007-10-30 13:12:39) this is working #4: hvogel(a)novell.com (2007-10-30 13:16:03) (reply to #3) or bnot #10: hvogel(a)novell.com (2007-10-30 13:48:53) (reply to #3) dwsdsdsd #5: hvogel(a)novell.com (2007-10-30 13:27:44) swsasaas #6: hvogel(a)novell.com (2007-10-30 13:33:36) sqsqasas #7: hvogel(a)novell.com (2007-10-30 13:36:11) wdwdswd #8: hvogel(a)novell.com (2007-10-30 13:38:00) dwsdsds #9: hvogel(a)novell.com (2007-10-30 13:46:33) wswdds #11: michl(a)novell.com (2007-10-30 13:49:14) wjnd sd s�dlkj sid #12: hvogel(a)novell.com (2007-10-30 13:52:27) (reply to #11) sasasas #17: hvogel(a)novell.com (2007-10-30 14:48:56) (reply to #12) xdsdsds #18: gp(a)novell.com (2007-11-02 21:51:25) Moving from openSUSE 10.3 to openSUSE 11.0. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302921

1 0

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

12 Jun '08

Feature changed by: freitag Feature #302923, revision 8 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: Evaluation Priority Requester: Neutral 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. + #4: freitag(a)novell.com (2008-06-12 10:06:42) + I have to revert my statement that I made before in comment #3, this + problem is more serious than realised in the first look. + First, it should be noted that we do not control mirrors nor we do have + the chance to really influence them. That means that if a mirrors + decides to not longer mirror or to switch off or whatever, we have to + live with it. However if a customer is sticky to a mirror that is not + longer available he would not get any packages from it and thus + installation or update fails. The worst thing about that is that this + seems to happen regularly but we do not realise that because we're not + involved. + A solution would be to have a list of possible mirrors that is used by + the software installation stack to find a working mirror. Peter knows + much more here. + But I am not sure at the moment if not Yast/zypper already has this + functionality in 11.0? -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302923

1 0

[Fate 304894] Yast Product Creator - create a product based on the current system
by fate_noreply＠suse.de 11 Jun '08

11 Jun '08

Feature added by: lslezak Feature #304894, revision 1 Title: Yast Product Creator - create a product based on the current system openSUSE-11.1: New Priority Requester: Desirable Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: The product creator module should be able to create a product with "Restore" pattern based on the current system. It would allow to easy reinstall the system using the same packages. The current product creator creates the product from scratch. This new option would use the currently installed packages to create a new pattern with all packages to ensure that they are installed at "Restore". References: https://bugzilla.novell.com/show_bug.cgi?id=392772 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304894

1 0