|
Bugzilla – Full Text Bug Listing |
| Summary: | yast: import/export user selections | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | robert fraatz <scorn> |
| Component: | YaST2 | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | scorn, suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
robert fraatz
2006-05-23 08:07:04 UTC
You mean a package selection? I suppose this is no longer possible with the new packager backend. (In reply to comment #1) > You mean a package selection? I suppose this is no longer possible with the new > packager backend. > But what reason could there be that this is no longer possible? Until suse 10.0 one could just import such a list and then yast did a dependency check like it (still) does for any other selections. In this way it was easily possible to do a new install (e.g. if an update hadn't worked for some reason) without loosing ones package selections duplicate of bug 156593? (Assignee differs BTW) |