- openSUSE Features

[openFate 305634] Debian-like dist-upgrade live system full version upgrade
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #305634, revision 5 - Title: Dist-upgrade + Title: Debian-like dist-upgrade live system full version upgrade - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Mandatory Requested by: Federico Lucifredi (flucifredi) Interested: Andre Duffeck (aduffeck) Interested: Guy Lunardi (glunardi) Interested: Klaus Kämpf (kwk) Interested: Matthias Eckermann (mge1512) Interested: Stephan Binner (beineri) Partner organization: openSUSE.org Description: - Dist upgrade to full fledged migration status. - Online migration should be supported from 11.1 to 11.2 + With the 11.2 cycle, we want to offer users the ability to perform a + live system upgrade in the manner of Debian's dist-upgrade. + For the purpose of this cycle, we want to support dist-upgrade from the + previous version (11.1) only, as this is a sufficiently complicated + problem as is. + From the user's view, the difference is between being able to update + the system incrementally within the given version or service pack + running, to being ble to migrate with a system command ("zypper dup" or + similar) to a higher version altogether. In the Debian experience, the + set of base distributions is not necessarily limited, but it has been + Ubuntu's practice to define what starting points other than "release n- + 1" are allowed (for instance, all LTS versions are purported to be able + to "apt dist-upgrade" to the top of the line, although I have heard of + problems trying to jump two years - 6.06->8.10 - in a fell swoop in + this manner :-). In the openSUSE scope, we should aim to be able to + "dup" between incremental versions, starting from 11.1 to 11.2, and + later 11.x to 12.0. + Business case (Partner benefit): + openSUSE.org: With the introduction of the Zypper stack to SLE, we + finally reached the state of a featureful (which YOU was not) and fast, + reliable (which ZLM was not) update stack in the platform. + For enterprise use, some tweaks are still desirable (changelogs, + rollback, ...) which we are looking at, as well as improvements on the + Enterprise management front, which we are working on with our SRM + colleagues. + The only really significant competitive feature we are missing at this + point is the Debian/Ubuntu dist-upgrade functionality, which has a + powerful psychological impact at the Enterprise level and a much more + tangible impact at the small user / single user level: many with no IT + department do use Ubuntu these days on the basis that "chasing" Fedora + and openSUSE along the six-month upgrade cycle is too much for them, + and feel they can save time on Ubuntu with the combination of dist- + upgrade and the longer LTS cycle. + The rationale for pursuing this is to revoke the special status of + coolness this functionality gives Ubuntu, and to terminate the negative + influence that has on our SLE sales (from the expert's personal + opinion, the preference then spills into purchasing). Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-07 20:42:15) This is the #1 feature in the systems management scope for 11.2 - I have no doubt it will be fun :-) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305634

1 0

[openFate 304429] Package cache handling in yast
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Ladislav Slezak <lslezak(a)novell.com> Feature #304429, revision 8 Title: Package cache handling in yast openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-07-11 21:45:10 reject reason: Postponing. Zypper already provides the functionality. Priority Requester: Important Projectmanager: Important - openSUSE-11.2: Evaluation + openSUSE-11.2: Done Priority Requester: Important SLES-11 Requested by: Ladislav Slezak (lslezak) Interested: Duncan Mac-Vicar (dmacvicar) 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 + Discussion: + #2: Ladislav Slezak (lslezak) (2009-01-08 13:47:14) + Implemented in yast SVN trunk (will be in yast2-packager-2.18.0) + There is a new check box, similar to 'Enabled' and 'Autorefresh' check + boxes. + (bnc#402617) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304429

1 0

[openFate 305634] Dist-upgrade
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Andre Duffeck <aduffeck(a)novell.com> Feature #305634, revision 4 Title: Dist-upgrade openSUSE-11.2: New Requested by: Federico Lucifredi (flucifredi) + Interested: Andre Duffeck (aduffeck) Interested: Guy Lunardi (glunardi) Interested: Klaus Kämpf (kwk) Interested: Matthias Eckermann (mge1512) Interested: Stephan Binner (beineri) Partner organization: openSUSE.org Description: Dist upgrade to full fledged migration status. Online migration should be supported from 11.1 to 11.2 Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-07 20:42:15) This is the #1 feature in the systems management scope for 11.2 - I have no doubt it will be fun :-) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305634

1 0

[openFate 305634] Dist-upgrade
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Stephan Binner <stbinner(a)novell.com> Feature #305634, revision 3 Title: Dist-upgrade openSUSE-11.2: New Requested by: Federico Lucifredi (flucifredi) Interested: Guy Lunardi (glunardi) Interested: Klaus Kämpf (kwk) Interested: Matthias Eckermann (mge1512) + Interested: Stephan Binner (beineri) + Partner organization: openSUSE.org Description: Dist upgrade to full fledged migration status. Online migration should be supported from 11.1 to 11.2 Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-07 20:42:15) This is the #1 feature in the systems management scope for 11.2 - I have no doubt it will be fun :-) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305634

1 0

[openFate 303493] zypper: add separate messages for Required and Recomended packages
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #303493, revision 9 Title: zypper: add separate messages for Required and Recomended packages openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-03-27 13:50:16 reject reason: Not enough time to look into this. openSUSE-11.1: Rejected by Federico Lucifredi <flucifredi(a)novell.com> reject date: 2008-08-01 18:27:34 reject reason: Cutting scope to match project schedule. openSUSE-11.2: Evaluation SLES-11 SLES-11-SP1 - Requested by: Cristian Rodriguez (elvigia) + Requested by: Cristian Rodríguez (elvigia) Partner organization: openSUSE.org Description: currenly when you install a package with zypper, you just get the packages that are going to be installed, regardless if the are required or Reccommended,.. will be nice if the messages can be arranged to be more explict about what the package manager is doing. "The following NEW [required|reccomended] package is going to be installed: foo" also an informative message about Suggested packages should be shown "The following package(s) is(are) suggested but are not going to be installed foo bar " unless user pass --install-suggested or use a boolean configuration directive on zypp.conf or something, suggested packages should not be installed by default ..currently it seems to be completely ignored and does nothing. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303493

1 0

[openFate 303517] Automatically refreshing repositories at recurring intervals
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #303517, revision 24 - Title: Configure a cronjob for refreshing repositories + Title: Automatically refreshing repositories at recurring intervals openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-09-12 14:12:10 reject reason: Postponing. openSUSE-11.2: Evaluation Requested by: Ladislav Slezak (lslezak) Interested: J. Daniel Schmidt (jdsn) Interested: Jiri Srain (jsrain) Interested: Jiří Suchomel (jsuchome) 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: Federico Lucifredi (flucifredi) (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: Duncan Mac-Vicar (dmacvicar) (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: Stanislav Visnovsky (visnov) (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain (jsrain) (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: Ladislav Slezak (lslezak) (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: Jiri Srain (jsrain) (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) #8: J. Daniel Schmidt (jdsn) (2008-07-18 18:13:38) (reply to #6) This would hide the feature in an update related module. But the feature does not restrict this only to update repositories. Build- Service Repos might need a refresh as well or think of Factory. The right place for this feature is the Repository Manager. It has no relation to the update process or a configuration concerning updates. #7: Jiří Suchomel (jsuchome) (2008-07-14 14:46:01) Daniel, what's the status of the plan to merge "online update configuration" into registration module? #9: J. Daniel Schmidt (jdsn) (2008-07-18 18:15:46) (reply to #7) Currently I plan to merge it into a new module together with "Online Update Configuration" related settings. Please do not extend it with this unrelated repo refreshing dialog. #10: J. Daniel Schmidt (jdsn) (2008-09-10 19:48:24) Why am I listed as the only developer here? I just said that I will merge the modules "automatic online update setup" and "online update setup". This feature is requesting something completely different. #11: Duncan Mac-Vicar (dmacvicar) (2008-09-10 22:21:17) (reply to #10) Don't worry, this feature will be dropped as because the OnStar work. It is just abandoned. #13: Jiří Suchomel (jsuchome) (2008-09-11 08:20:55) (reply to #11) Really? I don't think so.This feature is aimed for opensuse (it wants to extend the current "online update setup"), while OnStar is for SLE. #12: Jiří Suchomel (jsuchome) (2008-09-11 08:22:02) (reply to #10) Because the requested feature would be part of what is currently "online update setup". And after the merge, I assumed you should mainain the merged parts. #15: J. Daniel Schmidt (jdsn) (2008-09-11 12:37:19) (reply to #12) No the requested feature will not be part of the successor of "online update setup". Maybe you want it to be. But IMHO this has nothing to do with anything that is called "online update *something*". This feature is about a general refresh of repositories - not just the update repo. Software repositories are handled in the "Software repositories" module. And thats the place where this feature is asking for enhancement. Just look at the linked bug (bnc#346966). It even has a mockup (yes, I added one as well, but just look at the original one). And this is now quite the same I already wrote in comment #8. #16: Jiří Suchomel (jsuchome) (2008-09-11 12:44:53) (reply to #15) Ah, sorry. Looks like I have some other feature in mind while commenting this one. This one really is not online-update specific. + #18: Federico Lucifredi (flucifredi) (2009-01-07 20:21:21) (reply to + #17) + Please examin the current status critically: is there anything worth adding ? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

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

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #303517, revision 23 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-09-12 14:12:10 reject reason: Postponing. - openSUSE-11.2: New + openSUSE-11.2: Evaluation Requested by: Ladislav Slezak (lslezak) Interested: J. Daniel Schmidt (jdsn) Interested: Jiri Srain (jsrain) Interested: Jiří Suchomel (jsuchome) 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: Federico Lucifredi (flucifredi) (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: Duncan Mac-Vicar (dmacvicar) (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: Stanislav Visnovsky (visnov) (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain (jsrain) (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: Ladislav Slezak (lslezak) (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: Jiri Srain (jsrain) (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) #8: J. Daniel Schmidt (jdsn) (2008-07-18 18:13:38) (reply to #6) This would hide the feature in an update related module. But the feature does not restrict this only to update repositories. Build- Service Repos might need a refresh as well or think of Factory. The right place for this feature is the Repository Manager. It has no relation to the update process or a configuration concerning updates. #7: Jiří Suchomel (jsuchome) (2008-07-14 14:46:01) Daniel, what's the status of the plan to merge "online update configuration" into registration module? #9: J. Daniel Schmidt (jdsn) (2008-07-18 18:15:46) (reply to #7) Currently I plan to merge it into a new module together with "Online Update Configuration" related settings. Please do not extend it with this unrelated repo refreshing dialog. #10: J. Daniel Schmidt (jdsn) (2008-09-10 19:48:24) Why am I listed as the only developer here? I just said that I will merge the modules "automatic online update setup" and "online update setup". This feature is requesting something completely different. #11: Duncan Mac-Vicar (dmacvicar) (2008-09-10 22:21:17) (reply to #10) Don't worry, this feature will be dropped as because the OnStar work. It is just abandoned. #13: Jiří Suchomel (jsuchome) (2008-09-11 08:20:55) (reply to #11) Really? I don't think so.This feature is aimed for opensuse (it wants to extend the current "online update setup"), while OnStar is for SLE. #12: Jiří Suchomel (jsuchome) (2008-09-11 08:22:02) (reply to #10) Because the requested feature would be part of what is currently "online update setup". And after the merge, I assumed you should mainain the merged parts. #15: J. Daniel Schmidt (jdsn) (2008-09-11 12:37:19) (reply to #12) No the requested feature will not be part of the successor of "online update setup". Maybe you want it to be. But IMHO this has nothing to do with anything that is called "online update *something*". This feature is about a general refresh of repositories - not just the update repo. Software repositories are handled in the "Software repositories" module. And thats the place where this feature is asking for enhancement. Just look at the linked bug (bnc#346966). It even has a mockup (yes, I added one as well, but just look at the original one). And this is now quite the same I already wrote in comment #8. #16: Jiří Suchomel (jsuchome) (2008-09-11 12:44:53) (reply to #15) Ah, sorry. Looks like I have some other feature in mind while commenting this one. This one really is not online-update specific. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

[openFate 303678] New yast module - LIRC configuration
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #303678, revision 9 Title: New yast module - LIRC configuration openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-06-24 15:31:30 reject reason: More urgent stuff to cover. - openSUSE-11.2: New + openSUSE-11.2: Evaluation Requested by: Ladislav Slezak (lslezak) 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 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303678

1 0

[openFate 304429] Package cache handling in yast
by fate_noreply＠suse.de 08 Jan '09

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #304429, revision 7 Title: Package cache handling in yast openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-07-11 21:45:10 reject reason: Postponing. Zypper already provides the functionality. - openSUSE-11.2: New + openSUSE-11.2: Evaluation SLES-11 Requested by: Ladislav Slezak (lslezak) Interested: Duncan Mac-Vicar (dmacvicar) 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 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304429

1 0

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

08 Jan '09

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #304911, revision 7 Title: Import all GPG keys at once before downloading the metadata from new repositories openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-07-09 07:54:32 reject reason: Cannot be done in time. openSUSE-11.2: Evaluation SLES-11 Requested by: Ladislav Slezak (lslezak) Interested: Guy Lunardi (glunardi) Interested: Klaus Kämpf (kwk) Interested: Marcus Kraft (marcuskraft) Interested: Matthias Eckermann (mge1512) 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 + Discussion: + #2: Federico Lucifredi (flucifredi) (2008-07-08 19:41:45) (reply to + #1) + cute. It is a nice idea indeed. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304911

1 0