August 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306949] Clearing Documents List from GNOME Slab Menu
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Eric Yeoh (yeoheric) Feature #306949, revision 1 Title: Clearing Documents List from GNOME Slab Menu openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Eric Yeoh (yeoheric) Description: There is no feature in openSUSE or SLED 11 to clear recently used documents under the GNOME desktop using the Slab Menu. This presents a possible privacy issue. If there is a way to clear via context-menu will be great. -- openSUSE Feature: https://features.opensuse.org/306949

1 1

[openFATE 306953] yast-GRUB: graphic
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: manuel m (manuel_songokuh) Feature #306953, revision 1 Title: yast-GRUB: graphic openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: manuel m (manuel_songokuh) Description: hello.. i want new grub from yast! i want not change grub from yast but new graphic and little change..i will send you my pictures..but my languange is italian ok? this picture is default of grub from yast opensuse 11.1 64bit (view-source://http//digilander.libero.it/jaoken2/grub-installazione.png) http://digilander.libero.it/jaoken2/grub-installazione.png (view-source://http//digilander.libero.it/jaoken2/grub-installazione.png) this is my idea for new graphic: http://digilander.libero.it/jaoken2/grub-presentaz.png (view-source://http//digilander.libero.it/jaoken2/grub-presentaz.png) this reason..it's for not-espert or neo-user, for not panic during install grub.. now i do an example picture for step-step: http://digilander.libero.it/jaoken2/1-step.png http://digilander.libero.it/jaoken2/2-step.png http://digilander.libero.it/jaoken2/3-step.png http://digilander.libero.it/jaoken2/4-step.png http://digilander.libero.it/jaoken2/5-step.png what do you think about pictures? -- openSUSE Feature: https://features.opensuse.org/306953

1 6

[openFATE 306971] keep the previous kernel after update process
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Ioan Vancea (IonutVan) Feature #306971, revision 1 Title: keep the previous kernel after update process openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Ioan Vancea (ionutvan) Description: I would like to see that "feature" implemented default because after kernel updates many times there were a lot of issues and to change back to the previous version is not very easy for a novice user. For example after a kernel update I have problems with encrypted filesystems, or the sound stopped to work, .... Yes, I know that it is possible to change the behaviour to keep the old kernel but why not to be default. -- openSUSE Feature: https://features.opensuse.org/306971

1 5

[openFATE 307114] Add "Upgradable" and "Upgradable (upstream)" filters to YaST Software Management
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Alexander shaduri (alex_sh) Feature #307114, revision 1 Title: Add "Upgradable" and "Upgradable (upstream)" filters to YaST Software Management openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Alexander shaduri (alex_sh) Description: I used to use Synaptic+apt on openSUSE 10.3. Since upgrading to 11.1 I switched to using YaST for my package management needs. I follow some Build Service repositories, so frequently there are packages to be upgraded. Unfortunately, compared to Synaptic, YaST's package upgrade mechanisms are way too unusable. Synaptic had two simple but very useful features - "Upgradable" and "Upgradable (upstream)" filters. "Upgradable" shows all the packages that have newer versions available. "Upgradable (upstream)" shows packages which have newer upstream versions (that is, it won't show "example-1.0.0-1" => "example-1.0.0-3", but will show "example-1.0.0-1" => "example-1.0.1-1"). This is important since the release version is usually changed on every recompile, and filtering the upgrades by the actual "new version" is more handy. Without these filters I have to basically scroll through ALL installed packages, looking for the "blue-versioned" ones. This is making it simply unusable. Also, adding to the unusability is the "Installed (Available)" column. The last components of the available versions are almost always hidden unless I resize it to a quite large size, and even then, it's very hard to read. Compare it to the following (both versions can be seen easily): http://www.freesoftwaremagazine.com/files/www.freesoftwaremagazine.com/node… Steps to Reproduce: 1. Subscribe to a couple of heavily-populated repositories from Build Service. 2. Try browsing through upgradable packages. openSUSE 11.1 x86_64, YaST QT interface. See also: https://bugzilla.novell.com/show_bug.cgi?id=524000 -- openSUSE Feature: https://features.opensuse.org/307114

1 2

[openFATE 306957] Allow ymp (one-click installs) to set the repo priority
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Sven Burmeister (rabauke) Feature #306957, revision 1 Title: Allow ymp (one-click installs) to set the repo priority openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Description: When people use one-click installs to e.g. install or update KDE4, they get a lot of dependency issues because the buildservice repo does not have the right priority, i.e. higher than e.g. the oss or update repository. One-click installs only make sense if they are easy to use and facilitate the process of adding a repo. Having to open YaST software management to adjust the priority manually and re-running the update afterwards is not "one-click". Setting-up a repo includes setting the correct priority. The problem with ymp setting repos' priority is that those are relative to the repos already installed. The best solution would be to read the other repos' priority and suggest priorities for the new repos accordingly. The user can still change them in the one-click GUI. The minimal solution would be to just allow the user to set the repo's priority via the one-click GUI. -- openSUSE Feature: https://features.opensuse.org/306957

1 4

[openFATE 306321] disk id change in fstab
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Jean-Daniel Dodin (jdd_sysop) Feature #306321, revision 1, last change by Title: disk id change in fstab openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jean-Daniel Dodin (jdd_sysop) Description: "That basic request is that one or more simple tools be provided to allow a fstab to be automatically converted from /dev/sdaX nomenclature to one of the preferred methods." In other words, its now necessary to use YaST partitionner to change the fstab entry from /dev/sdx to the veeeeeeeeery long disk identification. This is very scary and is now nearly mandatory for updates. So it would be important to have some utility to make only this change in fstab and no other. If possible add the choice to use and set on the fly disk ID. -- openSUSE Feature: https://features.opensuse.org/306321

1 8

[openFATE 307479] YaST Software Manager - Downloading packages & dependencies to specified folders
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Mircea Kitsune (MirceaKitsune) Feature #307479, revision 1 Title: YaST Software Manager - Downloading packages & dependencies to specified folders openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Mircea Kitsune (mirceakitsune) Partner organization: openSUSE.org Description: The YaST2 Software Manager in OpenSuse 11.1 is not capable of downloading packages and dependencies to chosen folders, rather then installing them. For some users it's important to download .rpms together with their dependencies for that Opensuse version, which is useful for keeping software backups, installing on machines that aren't connected to the internet or redistributing software found in repos. The way I would suggest an implementation is a command in the YaST Software Manager, such as splitting the "Accept" button into two "Install" and "Download" buttons, or a Download option when right-clicking a package in the search list, which then allows the user to browse for a folder and download their selection there. I remember someone saying this might be added in Opensuse 11.2, so please close this if it has already been done. Business case (Partner benefit): openSUSE.org: For some users it's important to download .rpms together with their dependencies for that Opensuse version, which is useful for keeping software backups, installing on machines that aren't connected to the internet or redistributing software found in repos. -- openSUSE Feature: https://features.opensuse.org/307479

1 1

[openFATE 307505] zypper should list updates by version, not by build version
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: M. S. (FunkyM) Feature #307505, revision 1 Title: zypper should list updates by version, not by build version openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: M. S. (funkym) Partner organization: openSUSE.org Description: If you look at the regular zypper workflow with refreshing, checking out updates and ending up upgrading those, one thing bothers me. Using the "list updates command, zypper shows me every package which has been updated. My fate here is to propose adding some switch to the "list updates" command to only list a package in the "lu" list if the package version increased and ignore build version changes. Test Case: Example: MozillaFirefox full version is 3.5.2-2.1. I don't want it listed in "lu" if the version changed to 3.5.2-3.1, but I care to get it listed if it was 3.5.3-1.1. Use Case: Most of the time it is just the same package, rebuilt by the build service or due to a packager adding some minor change and triggering a rebuild. Thus only the build version of the package increased, not the real package version. As long as my system is stable and I am just upgrading for features of new package versions I read up on the internets, I only care about the updates for packages that changes their package version, regardless if they had been rebuild or not. Business case (Partner benefit): openSUSE.org: This simplifies the use case of checking for real "software" updates on zypper, filtering out the updates that are caused by rebuilds. -- openSUSE Feature: https://features.opensuse.org/307505

1 2

[openFATE 307514] cdrecord alternative
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Thomas Peter (lizzarddude) Feature #307514, revision 1 Title: cdrecord alternative openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Thomas Peter (lizzarddude) Description: Mr. Schillings constant ramblings about how openSuSE and other Linux distributions are violating the Copyright of his License Mixup should lead to development of an non-cdrecord-based alternative. -- openSUSE Feature: https://features.opensuse.org/307514

1 5

[openFATE 306291] ADD ability to launch YaST modules via SystemSettings
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #306291, revision 1, last change by Title: ADD ability to launch YaST modules via SystemSettings openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Paul Lubetsky (vegeek) Description: It would be better and simplier for novice to have only one configuration panel in the system, both for KDE and general System Administration via YaST. Similiar work was done for gnome: now opensuse has an integrated all-in-one control panel there. I propose to add an Administration tab in systemsettings, which would provide launchers for YaST`s system administration tools. Reproducible: Always Steps to Reproduce: Simply open menu: you`ll find there two different launchers for YaST and SystemSettings. Actual Results: Now SystemSettings and YaST aren`t integrated. Expected Results: User want to do some system administration tasks, he/she opens SystemSettings and opens required configuration tool. Something similiar was in SuSE 10.0 with KDE3.4. Relations: - ADD ability to launch YaST modules via SystemSettings (novell/bugzilla/id: 487611) https://bugzilla.novell.com/show_bug.cgi?id=487611 -- openSUSE Feature: https://features.opensuse.org/306291

1 7