- openSUSE Features

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

11 Jul '08

Feature changed by: jsrain Feature #304429, revision 5 Title: Package cache handling in yast openSUSE-11.1: Evaluation Priority Requester: Important Projectmanager: Important + openSUSE-11.2: New + Priority + Requester: Important SLES-11: Evaluation Priority Requester: Important Projectmanager: 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 303527] Resolve dependencies after ignoring package download failure
by fate_noreply＠suse.de 11 Jul '08

11 Jul '08

Feature changed by: jsrain Feature #303527, revision 11 Title: Resolve dependencies after ignoring package download failure - openSUSE-11.1: Evaluation + openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: 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. #3: visnov(a)novell.com (2008-06-24 15:32:30) (reply to #2) Yes, I would just suggest to add a message with instructions for the user. + #4: jsrain(a)novell.com (2008-07-11 10:22:19) (reply to #3) + That should be pretty simple. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303527

1 0

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

11 Jul '08

Feature changed by: jsrain Feature #304395, revision 11 Title: Disabling (or handling) screensaver during installation - openSUSE-11.1: Evaluation + openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: Important 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. #7: visnov(a)novell.com (2008-07-07 09:29:27) Let's see what can be done. I suggest to: 1) having a installation parameter to switch the screen saver off 2) error messages to stop screensaver if running + #8: jsrain(a)novell.com (2008-07-11 10:08:35) + The first part is easily possible and we can do it. + Tracking all error pop-ups is not easy. + I suggest to disable screensaver at the beginning of installation. Who + is doing installation overnight usually switches off the display + anyway. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

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

10 Jul '08

Feature changed by: jsrain Feature #303517, revision 9 Title: Configure a cronjob for refreshing repositories - openSUSE-11.1: Evaluation + openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: Mandatory 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. #2: dmacvicar(a)novell.com (2008-07-07 11:13:37) If you think you can make it work in a reliable way, please present a concept. Right now PackageKit and updater applets do refresh often before checking for updates so the system repos _are_ refreshed. So I don't see much value in this feature (unless a concept is presented). #3: visnov(a)novell.com (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: jsrain(a)novell.com (2008-07-07 12:58:59) (reply to #3) You mean running online update from cron? It should involve metadata refresh, but I do not see any reason for a separate metadata download from cron. #5: lslezak(a)novell.com (2008-07-09 10:30:09) (reply to #4) The feature should allow to disable "autorefresh" flag for all repositories so the package management can be started quickly without connecting to network. The cronjob would keep the metadata uptodate. Of course, there might be a problem when metadata are changed too often on the server, but in my opinion that's not a usual case in the real world. + #6: jsrain(a)novell.com (2008-07-10 12:16:08) + Let's extend the "automatic online update" module so that it offers + whether to do real automatic online update, or just refresh the + metadata (via one check box) -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303517

1 0

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

09 Jul '08

Feature changed by: lslezak Feature #303517, revision 8 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Evaluation Priority Requester: Desirable Projectmanager: Mandatory 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. #2: dmacvicar(a)novell.com (2008-07-07 11:13:37) If you think you can make it work in a reliable way, please present a concept. Right now PackageKit and updater applets do refresh often before checking for updates so the system repos _are_ refreshed. So I don't see much value in this feature (unless a concept is presented). #3: visnov(a)novell.com (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: jsrain(a)novell.com (2008-07-07 12:58:59) (reply to #3) You mean running online update from cron? It should involve metadata refresh, but I do not see any reason for a separate metadata download from cron. + #5: lslezak(a)novell.com (2008-07-09 10:30:09) (reply to #4) + The feature should allow to disable "autorefresh" flag for all + repositories so the package management can be started quickly without + connecting to network. The cronjob would keep the metadata uptodate. + Of course, there might be a problem when metadata are changed too often + on the server, but in my opinion that's not a usual case in the real + world. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303517

1 0

[Fate 303708] Mascot for YaST
by fate_noreply＠suse.de 09 Jul '08

09 Jul '08

Feature changed by: visnov Feature #303708, revision 10 Title: Mascot for YaST - openSUSE-11.1: Evaluation + openSUSE-11.1: Candidate Priority Requester: Mandatory + Projectmanager: Desirable Requested by: aj(a)novell.com Partner organization: openSUSE.org Description: Every successfull product has it's own logo and mascot. We should create and market one for YaST as well, display it prominently on all YaST project pages and also in YaST, e.g. in any About screens or as easter egg. Discussion: #2: michl(a)novell.com (2008-04-24 12:46:55) I'm fine with that. I think this should come out of the inner YaST circle with some help from design people like Jakub. #3: michl(a)novell.com (2008-04-24 19:54:31) (reply to #2) And we should inlcude the community on that. Zonker might call for ideas/participation for logo creation on his blog and news.openSUSE. org #4: dmacvicar(a)novell.com (2008-04-25 12:08:16) # zypper moo \\\\\ \\\\\\\__o __\\\\\\\'/_ http://en.wikipedia.org/wiki/Hedgehog -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303708

1 0

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

09 Jul '08

Feature changed by: visnov Feature #304911, revision 5 Title: Import all GPG keys at once before downloading the metadata from new repositories - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by visnov(a)novell.com + reject date: 2008-07-09 07:54:32 + reject reason: Cannot be done in time. Priority Requester: Desirable - SLES-11: Evaluation + openSUSE-11.2: New Priority Requester: Desirable + SLES-11: Rejected by visnov(a)novell.com + reject date: 2008-07-09 07:54:36 + reject reason: Cannot be done in time. + 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 304894] Yast Product Creator - create a product based on the current system
by fate_noreply＠suse.de 08 Jul '08

08 Jul '08

Feature changed by: mge Feature #304894, revision 3 Title: Yast Product Creator - create a product based on the current system - openSUSE-11.1: New + openSUSE-11.1: Duplicate of #303047 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

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

08 Jul '08

Feature changed by: mge Feature #304911, revision 2 Title: Import all GPG keys at once before downloading the metadata from new repositories - openSUSE-11.1: New + openSUSE-11.1: Evaluation Priority Requester: Desirable + SLES-11: Evaluation + 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 303736] yast and libzypp should respect the disk space reserved for root
by fate_noreply＠suse.de 08 Jul '08

08 Jul '08

Feature changed by: visnov Feature #303736, revision 5 Title: yast and libzypp should respect the disk space reserved for root - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by visnov(a)novell.com + reject date: 2008-07-08 12:18:47 + reject reason: Postponing. This is nice to have. Priority Requester: Desirable + openSUSE-11.2: New + 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