December 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308320] YMP YaST Workflow
by fate_noreply＠suse.de 17 May '13

17 May '13

Feature added by: Hendrik Vogelsang (hennevogel) Feature #308320, revision 1 Title: YMP YaST Workflow openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: If you click on a YMP link firefox opens a window[1] asking you what you want to do with that link, suggesting to let the meta package handler handle it. You click okay from which another window[2] opens, the download manager of firefox. After it is finished an new window[3] pops up asking you the initial questions about the YMP handling. Which repos to subscribe to and which package to install. If you okay twice yet another window[4] opens asking me for the root password to start the package manager. Which is another window[5]. If there is a new repo in the YMP that you did not have before it will open a window[6] asking you to import the signing key. Somehow i doubt that this many windows are neccessarry. For a workflow that is desinged for the stupid user this should be improved imho. -- openSUSE Feature: https://features.opensuse.org/308320

1 2

[New: openFATE 314461] gnu parallel
by fate_noreply＠suse.de 08 May '13

08 May '13

Feature added by: Guenter Grau (ggrau) Feature #314461, revision 1 Title: gnu parallel Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Guenter Grau (ggrau) Partner organization: openSUSE.org Description: When I discovered GNU parallel it quickly became an indispensable tool for all my scripting. Beside fixing issues with "argument list too long" (which could be solved with xargs) it is very useful to utilize multiple cores or even machines on the script level (I use it to form a simple compute cluster). Since it is universal and simple to use, I wonder why it didn't become part of openSUSE long before. http://www.gnu.org/software/parallel/ -- openSUSE Feature: https://features.opensuse.org/314461

1 3

[New: openFATE 314612] Implement GNOME SUSE Greeter
by fate_noreply＠suse.de 30 Mar '13

30 Mar '13

Feature added by: Narayansamy S (vazhavandan) Feature #314612, revision 1 Title: Implement GNOME SUSE Greeter openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Narayansamy S (vazhavandan) Partner organization: openSUSE.org Description: Provide a GNOME greeter for GNOME desktop similar to KDE greeter Ref:-http://paste.opensuse.org/42507599 The GNOME greeter should provide information similar to KDE greeter like explanation about:- ==>openSUSE Project ==>Community Support ==>Build Service etc: The new GNOME greeter if implemented should also be easy to turn off through gnome-session-properties. Business case (Partner benefit): openSUSE.org: The new GNOME greeter if implemented will explain the aim of the openSUSE project to its end users and also provide a has a few important links similar to KDE greeter .This would be pretty useful for people who are new to openSUSE and also provide a sense of bonding between openSUSE and its users -- openSUSE Feature: https://features.opensuse.org/314612

1 5

[New: openFATE 310041] HP 3D GuardDrive
by fate_noreply＠suse.de 25 Mar '13

25 Mar '13

Feature added by: Dimitar Popov (dimitar_popov) Feature #310041, revision 1 Title: HP 3D GuardDrive openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Dimitar Popov (dimitar_popov) Description: I wish openSUSE to supply a daemon, which uses the /dev/freefall to provide hard disk head crash protection. There is an example application in /usr/src/linux/Documentation/hwmon/hpfall.c which might be used as a base for such a daemon and the needed modules (hp_accel and lis3lv02d) are present in kernel 2.6.31. I think this is an important feature for HP laptop users. -- openSUSE Feature: https://features.opensuse.org/310041

1 5

[New: openFATE 308557] Easier Network configration
by fate_noreply＠suse.de 25 Mar '13

25 Mar '13

Feature added by: belal mandurah (belal_mandurah) Feature #308557, revision 1 Title: Easier Network configration openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: belal mandurah (belal_mandurah) Description: There are lots of confusing settings when setting up a network and they are in diffrent location to edit (smb.conf, netbios name, host name, domain name, workgroup name, ports, allowed services ... etc) It is really frustrating when you cant access shared files, especially for home users. I suggest that there should be an easier way to configure a network , perhaps a wizard. something that maybe look like M$ wizard when setting up a network. -- openSUSE Feature: https://features.opensuse.org/308557

1 7

[New: openFATE 310311] Unify default PATH
by fate_noreply＠suse.de 13 Mar '13

13 Mar '13

Feature added by: Ludwig Nussel (lnussel) Feature #310311, revision 1 Title: Unify default PATH openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: The default PATH settings for root and normal users are inconsistent at various places in the distribution: glibc - /usr/include/paths.h: #define _PATH_DEFPATH "/usr/bin:/bin" #define _PATH_STDPATH "/usr/bin:/bin:/usr/sbin:/sbin" coreutils - /etc/default/su: PATH=/usr/local/bin:/bin:/usr/bin SUPATH=/usr/sbin:/bin:/usr/bin:/sbin coreutils - /bin/su: #define DEFAULT_LOGIN_PATH "/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin" #define DEFAULT_ROOT_LOGIN_PATH "/usr/sbin:/bin:/usr/bin:/sbin:/usr/X11R6/bin" pwdutils - /etc/login.defs: ENV_PATH /usr/local/bin:/usr/bin:/bin ENV_ROOTPATH /sbin:/bin:/usr/sbin:/usr/bin aaa_base - /etc/profile and /etc/csh.login PATH=/usr/local/bin:/usr/bin:/bin PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH sudo: --with-secure-path=/usr/sbin:/bin:/usr/bin:/sbin:/usr/X11R6/bin ... and probably many more ... The default PATH setting should be made consistent across all tools. -- openSUSE Feature: https://features.opensuse.org/310311

1 12

[New: openFATE 314418] User management reworked
by fate_noreply＠suse.de 08 Mar '13

08 Mar '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #314418, revision 1 Title: User management reworked Buildservice: Evaluation by engineering manager Milestone: 2.4 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: As part of the Rails 3.2 port of OBS we need to re-do the interfaces for user and group managenment. They should get implemented in the webui now instead in the api part. -- openSUSE Feature: https://features.opensuse.org/314418

1 2

[New: openFATE 314350] Cloud backup
by fate_noreply＠suse.de 07 Mar '13

07 Mar '13

Feature added by: David Disseldorp (dmdiss) Feature #314350, revision 1 Title: Cloud backup openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: David Disseldorp (dmdiss) Partner organization: openSUSE.org Description: openSUSE currently includes a useful system backup module for creating archives of user and system files. Backup archives can be stored locally or on a remote NFS share. An improvement would be to allow users to store backup archives at a cloud storage location. I propose making use of the Elasto cloud storage library to implement this: http://oss.sgi.com/cgi-bin/gitweb.cgi?p=ddiss/elasto -- openSUSE Feature: https://features.opensuse.org/314350

1 1

[New: openFATE 308285] Easy way to switch from 11.2 to Factory Repositories - and to 11.3
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #308285, revision 1 Title: Easy way to switch from 11.2 to Factory Repositories - and to 11.3 openSUSE-11.3: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Description: Right now, I have to manually change the repositories when upgrading from 11.2 to Factory - or from Factory to 11.3. I'd like to have an easy way, e.g. 1-Click-Install or a script that does this automatically for my system. This might not change external repositories, e.g. on the Build Service, but it should change the official distribution repositories. -- openSUSE Feature: https://features.opensuse.org/308285

1 5

[openFATE 308181] Yast Install - textbox to test the keyboard
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Kayo Hamid (kayohf) Feature #308181, revision 1 Title: Yast Install - textbox to test the keyboard openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Kayo Hamid (kayohf) Description: Hi, i see that the Yast Install (11.2 M8) do not have a textbox to test the keymap that i have selected. My idea is to put one textbox to test the keyboard after the choose of keymap. -- openSUSE Feature: https://features.opensuse.org/308181

1 3

[openFATE 307628] give client a way to indicate preferred country for mirror choice
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Duncan Mac-Vicar (dmacvicar) Feature #307628, revision 1 Title: give client a way to indicate preferred country for mirror choice openSUSE-11.3: New Priority Requester: Desirable Requested by: Peter Poeml (poeml) Description: Hi, the mirror selection is based on precise, but relatively narrow network topology knowledge, as well as the "mostly" precise and sometimes lacking GeoIP information. For the cases where the IP cannot resolved, or cannot be resolved correctly, to a country, we can give the client a way to specify the country it is located in, to influence the mirror choice into the right direction. There are several groups of users that are affected by this: * users connected through satellite links can often be resolved only as country=A2, which is not a real country, it only indicates that this is a satellite link. * AOL users outside the US are not resolved (pseudo country A1). * IPs unknown to the GeoIP database, and not in one of the AS's which contain a mirror either * clients connected through a VPN that uses address space that's allocated in another country (e.g. clients in the Netherlands, whose employer is based in the US and runs a VPN that uses IP addresses that geolocate to the US) * Ipv6 clients (no GeoIP for that yet) Thus, it is desirable to give clients a way to indicate their location. CentOS uses something like that to influence or override mirror choice: http://www.centos.org/modules/news/article.php?storyid=118 In 11.2 libzypp, this could be implemented relatively easily (I believe) by adding a configuration directive "download-preferred-country" to /etc/zypp/zypp.conf, taking an ISO3166-1 two-letter code, and adding an HTTP request header (X-Preferred-Country) _if_ something is configured there. On another hand, since we intend to mainly use metalinks in the future, we could just use another aria2c option that makes this configurable: --metalink-location=LOCATION[,...] The location of the preferred server. A comma-delimited list of locations is acceptable, for example, JP,US. On the server side, the latter doesn't require anything to do. The former would be easy to implement. Something similar already exists, through ?country=xy request parameter, so one only needs to pick up the new header, which is a few lines of code. It could be used to deal with libcurl downloads, but in the light of metalink usage we should be able to neglect them. Relations: - give client a way to indicate preferred country for mirror choice (novell/bugzilla/id: 482894) https://bugzilla.novell.com/show_bug.cgi?id=482894 Discussion: #1: Peter Poeml (poeml) (2009-03-06 10:20:33) Duncan, can I assign this to you? I look into the git repository, tried to update but I stupidly failed with a file conflict and resolving it, else I would have given it a go... -- openSUSE Feature: https://features.opensuse.org/307628

1 1

[openFATE 306966] No Shutdown/Suspend During Package Update
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #306966, revision 1 Title: No Shutdown/Suspend During Package Update openSUSE-11.3: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: During a package update, it should not be possible to shutdown or suspend the system. Such requests should be delayed until the package update is finished. You do not want to bring the system in an inconsistent state. I consider this a desktop feature, so if somebody runs halt/shutdown on the console, this might not need to work - but if the GNOME/KDE shutdown/suspend options are used, it should finish the update first. Note: Windows does not allow shutdown during an update. What happened and let me to report this as feature: A user installed a kernel update and thought the update was finished. But only one out of the three kernel packages was updated and therefore after a reboot, the system did not came up completely. Business case (Partner benefit): openSUSE.org: If this feature is not implemented, people can get broken systems - which might result in support calls. -- openSUSE Feature: https://features.opensuse.org/306966

1 17

[openFATE 306767] Yast2 package manager: add more filters
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Vincent Petry (PVince81) Feature #306767, revision 1 Title: Yast2 package manager: add more filters openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Vincent Petry (pvince81) Description: It would be nice to have the following additional filters, maybe in the "view" menu: 1) Only show the packages that have a major version update 2) Same as 1) with minor version 3) Only show packages that appeared since the last refresh (see https://features.opensuse.org/306766) 4) Only show packages which version has changed since the last refresh (see https://features.opensuse.org/306766) 5) Only show installed packages 6) Only show non-installed packages The filters should be toggles/checkboxes, so that it's possible to combine them. Such filters are already available in the smart package manager. -- openSUSE Feature: https://features.opensuse.org/306767

1 7

[openFATE 306520] Redesign "Format and Mount Dialog" in YaST Expert Partitioner
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Arvin Schnell (aschnell) Feature #306520, revision 1 Title: Redesign "Format and Mount Dialog" in YaST Expert Partitioner openSUSE-11.2: New Priority Requester: Important Requested by: Arvin Schnell (aschnell) Description: The "Format and Mount Dialog" in the YaST Expert Partitioner has several technical mistakes and limitations. * The mount-by method is in the fstab options dialog. This is wrong since volumes are also addressed in crypttab when they are not mounted. The same applies to the "Do Not Mount at System Start-up" setting. So these settings cannot be modified for e.g. encrypted volumes that are not mounted. * The filesystem label is in the fstab options. Thus it is not possible to set a filesystem label when not mounting the filesystem. This field should be moved from the mount options to the filesystem options. * Some filesystem options, e.g. "Disable regular checks", cannot be changed without formatting the filesystem although the filesystem tools support this. There should be a differentiation between filesystem options that can only be set during formatting and those that can be changed afterwards. One trouble is that this differentiation depends on the filesystem used. -- openSUSE Feature: https://features.opensuse.org/306520

1 5

[openFATE 306437] yast2 disk: easy way to mount all ntfs partitions rw
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Stefan Behlert (sbehlert) Feature #306437, revision 1, last change by Title: yast2 disk: easy way to mount all ntfs partitions rw openSUSE-11.2: New Priority Requester: Desirable Requested by: Jigish Gohil (cyberorg) Description: Taken from Bugzilla: Please provide a check box that says something like this: "Detect and mount all NTFS partitions Read-Write for all users" I do over 100 installations of openSUSE every month, all on PC that have windows installed, and manually changing it in /etc/fstab is bit tedious. Reproducible: Always Relations: - yast2 disk: easy way to mount all ntfs partitions rw (novell/bugzilla/id: 487126) https://bugzilla.novell.com/show_bug.cgi?id=487126 Discussion: #1: Arvin Schnell (aschnell) (2009-03-23 11:53:17) Stefan, please make a feature request if you want this. -- openSUSE Feature: https://features.opensuse.org/306437

1 13

[openFATE 306383] Browsing available repositories from YaST level
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Piotrek Juzwiak (BenderBendingRodriguez) Feature #306383, revision 1, last change by Title: Browsing available repositories from YaST level openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Piotrek Juzwiak (benderbendingrodriguez) Description: After test driving mandriva i found one idea there really great, you can browse repositories from the tool used for managing software. It would be great to have such thing in openSUSE (the community repositories isn't enough i think). So instead of browsing for repositories from web browser level we could browse it from YaST level (include something like novice and advanced level, the difference would be repositories shown for the end user). -- openSUSE Feature: https://features.opensuse.org/306383

1 8

[openFate 305716] [openSUSE 11.1] Disk partitioning under installation (Disk)
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Matthias Eckermann (mge1512) Feature #305716, revision 1, last change by Title: [openSUSE 11.1] Disk partitioning under installation (Disk) openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Sebastian Furdal (resus) Partner organization: openSUSE.org Description: We all know, that openSUSE as a default wants use on its own entire disk. This is VERRY BAD setting. On this website exist a pool: http://suse.ehelp.pl/modules/xoopspoll/pollresults.php?poll_id=24 POLISH: Czy os11 powinien miec przy instalacji mozliwosc wyboru, na ktorej partycji zainstalować system? ENGLISH: Should os11 installation program have make a choice on what partition install the system? 94% users sad YES (tak) Try my proposal... "See the attachments" Relations: - [openSUSE 11.1] Disk partitioning under installation (Disk) (novell/bugzilla/id: 383886) https://bugzilla.novell.com/show_bug.cgi?id=383886 Discussion: #1: Sebastian Furdal (resus) (2008-04-25 12:36:23) Created an attachment (id=210574) Disk (GIMP) #2: Sebastian Furdal (resus) (2008-04-25 12:37:01) Created an attachment (id=210575) Button "create" #3: Arvin Schnell (aschnell) (2008-04-28 03:44:40) Something for PM to decide. #4: Stephan Kulow (coolo) (2008-04-28 04:10:30) Actually this fits the feedback I got during fosdem - the _HUGE_ majority of (power) users has to change the proposal. But the "Create" and "Edit" buttons are already more prominently as they were in previous releases. This was on the behalf of this feedback. #5: Sebastian Furdal (resus) (2008-04-28 07:47:26) Created an attachment (id=210885) Version 2 #6: Matthias Eckermann (mge1512) (2008-04-29 04:06:15) I do not completly understand the request, I fear:-( Is it (1) about leaving space for windows or other OSes? (2) or about _how_ the Linux partitioning should look like? (3) or about both? I personally have a rather "sophisticated" partitioning (people say: "crazy"), thus I am planning to propose a LVM based partitioning as one(!) option (and default for our Enterprise Server product) with roughly(!) this layout. /dev/sda1 /boot /dev/sda2 /swap /dev/sda3 # system VG / /usr /opt /var /dev/sda4 # data VG /tmp /home /srv This more or less resembles the defaults of Unix/BSD systems. As said: it is the "extended" variant of what I can imagine for systems, where Linux is allowed to control the whole harddisk. For systems with shared windows partitions the layout should be different. And suggestions? Comments? Ideas? Proposals? Thanks in advance - so long - MgE #8: Sebastian Furdal (resus) (2008-05-01 02:19:50) (1)(1)does the idea of „automatic partitioning” is to make monopoly in one OS on one computer? [sarcasm] (2)(2)Yes, its only a proposal, more details I can make in some free time. (3)(3)Yap (4)(4)but openSUSE is mostly installed by less advanced users, who mostly do not know anything about Servers (5)(5)Most people on the world have a Windows and they install GNU/Linux with curiosity, and GNU/Linux should not propose to delete their favorite system and all precious data that where collected for years. This is something that makes openSUSE behind almost all major GNU/Linux distributions. And even I do not use Windows, but GNU/Linux (doesn't matter if its not openSUSE/SUSE) but I want check this distro [...] (6)(6)Propose: 1. After detecting disks and partitions Yast2 should propose mount points for all existed partitions. 2. When it finds completely free partition (doesn't matter with what file system - sometimes users prepare before installation free partition under different OS for a new system) OR/AND unallocated space with more size than installation required it should mark it with a green color – that on this partition/space You can install openSUSE with options /boot, /swap, /, /usr, ... etc. 3. When it doesn't find good partition then it should ask “Create automatic disk partitioning?”. a) YES - Automatically create partition setup for home users (example only with “/” and “/home” and ”/boot” - boot is very important for grub, because for example when a user delete under windows Linux partition grub is still in the MBR but it cant find config files - “OH MY GOD, LOOK LINUX DESTROYED MY SYSTEM – I WILL NEVER USE LINIX AGAIN” and most people do not know anything about windows installation “fixmbr”) - ALL DATA WILL BE LOST [red color] - Automatically create partition setup for server - ALL DATA WILL BE LOST [red color] b) NO - Edit partition setup (all proposed mount points in step 1. should remain even without “/” but whit red warning “To install openSUSE You have to create partition with minimal size $MINIMAL_INSTALLATION_SIZE GB”). #9: Matthias Eckermann (mge1512) (2008-05-06 20:56:51) Hello and thanks for the answers. Please see my comments below.? (In reply to comment #8 from Sebastian Furdal) > > (1) about leaving space for windows or other OSes? > (1)(1)does the idea of „automatic partitioning” is to make monopoly in one > OS on one computer? [sarcasm] I agree: I have at least 3 openSUSE/SLES systems on my systems, and every fresh installation tries to kill my "vg_data". This is just annoying and will be fixed. > > (2) or about _how_ the Linux partitioning should look like? > (2)(2)Yes, its only a proposal, more details I can make in some free time. I also have some ideas there, ... > (4)(4)but openSUSE is mostly installed by less advanced users, > who mostly do not know anything about Servers Well, that does not necessarily be true according to other requests I see:-) But I agree that the "less advanced users" have to be covered in the most save way. > [...] This is something that makes openSUSE behind almost all major > GNU/Linux distributions. [...] Well, you might simply avoid those type of comments, please, as it weakens your very valid points above and below ( because people might become angry ). > (6)(6)Propose: > [...] Instead of your proposal let me post a proposal I wrote roughly 2 years ago here in bugzilla (closed bug); in meta-programming-language (and covering also datacenter use e.g. of SLES product): if( SAN-storage-found ) { expert-partitioning(); } else if( num-of-harddisks > 1 ) { expert-partitioning(); } else if( only-one-windows-partition_on( first_harddisk ) ) { # case 2 below partitioning-with-shrink( first_harddisk ) | expert-partitioning(); } else if( some-partitions-but-free-space_on( first_harddisk ) ){ # case 3 below partitioning-without-shrink-or-delete_on (first_harddisk ) | expert-partitioning(); } else if( some-partitions-but-no-free-space_on( first_harddisk ) ) { expert-partitioning(); } else if( multiple-existing-OSes-found ){ expert-partitioning(); } else { # empty harddisk, case 1 below default-partitioning(); } I would like to see that a little bit less complex, but I hope it could be a good start; I also hope we can agree that there are only three relatively "safe" & easy cases: 1. one empty harddisk 2. one harddisk full with another OS (most probably windows) 3. (at least) one (bigger) empty primary partition on first harddisk Everything else needs "knowledge" by the person in front of the computer, i.e. an "expert partitioner" YaST module to support this person, HTH - MgE #10: Matthias Eckermann (mge1512) (2008-05-26 06:19:13) What do you think? #11: Sebastian Furdal (resus) (2008-07-20 03:40:24) I think advanced partitioning should be rewritten, sometimes it is to complicated ... Your proposal is good but openSUSE should automatically propose simple and automatic solutions ... such as: - propose partitions where oS could be installed - propose automatic mount points - propose some profiles of partitioning etc. What You think? #12: Andreas Jaeger (a_jaeger) (2008-10-24 05:24:05) Information was provided. #13: Matthias Eckermann (mge1512) (2009-01-21 11:57:03) Moved to openFATE from bugzilla. Let's proceed for openSUSE 11.2 based on what we have in openSUSE 11.1. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305716

1 12

[New: openFATE 309445] Make yast proxy work with Microsoft ISA
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: francesco nigro (frappa_nigro) Feature #309445, revision 1 Title: Make yast proxy work with Microsoft ISA openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: francesco nigro (frappa_nigro) Description: The yast proxy module doesn't work with Microsoft ISA proxy, the ntlm authentication is not managed correctly and fails. The only viable solution at the moment (the only one I found at least) is to install cntlm on every machines... -- openSUSE Feature: https://features.opensuse.org/309445

1 3

[New: openFATE 314416] Repository cleanups via requests
by fate_noreply＠suse.de 26 Feb '13

26 Feb '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #314416, revision 1 Title: Repository cleanups via requests Buildservice: Evaluation by engineering manager Milestone: 2.4 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: The cleanup of repositories of discontinued distributions must become more transparent and must not destroy the source links of new maintenance :Update projects. Therefore we implement: * Request action type to remove a repository from a project * Auto-accept functionality in case the target owner does not re-acct. -- openSUSE Feature: https://features.opensuse.org/314416

1 1

[New: openFATE 310759] job dispatching based on capabilities
by fate_noreply＠suse.de 26 Feb '13

26 Feb '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #310759, revision 1 Title: job dispatching based on capabilities Buildservice: New Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: We will need to have more detail configuration options during job assignment to build instances based on the capabilities of the build hosts. Possible usecases are: * packager wants to specify the needed amount of hard disc space, memory, kernel version or any other hardware requirement like CPU features. * OBS admin wants to enforce the usage of a build enviroment (like chroot, XEN or KVM) for certain packages or projects. These requirements must stay when doing a branch, link or copy operation to another place. -- openSUSE Feature: https://features.opensuse.org/310759

1 7

[New: openFATE 311341] Yast Partitioning give SSD best practice option
by fate_noreply＠suse.de 23 Feb '13

23 Feb '13

Feature added by: Hans de Raad (hcderaad) Feature #311341, revision 1 Title: Yast Partitioning give SSD best practice option openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Hans de Raad (hcderaad) Partner organization: openSUSE.org Description: More and more laptops, netbooks, pc's, servers, actually anything with some kind of storage need is equipped with Solid State Disks. Although at first glance they may seem quite similar to harddisks, they really are a completely different species with some very different characteristics. It might be convenient for having an "SSD Best practise enabler" switch when creating partitions on disks in Yast, which would then automatically setup the features (and possibly others) mentioned in the "Why do we want this" part of this feature. Use Case: During installation (or partition editing) when a user configures a partition, the option would be presented to enable SSD Best practises. Business case (Partner benefit): openSUSE.org: Especially in the partitioning stage of the installation process one can make or break the extra performance one might gain from using SSD's. Especially aligning a filesystem to SSD erase block size and enabling TRIM on partitions are really noticeable performance enhancers. Also, when the SSD option is activated, the Swap partition would be suggested to be removed from the partition setup (if one is set). -- openSUSE Feature: https://features.opensuse.org/311341

1 8

[New: openFATE 314593] Package Maintainer Handling
by fate_noreply＠suse.de 22 Feb '13

22 Feb '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #314593, revision 1 Title: Package Maintainer Handling Buildservice: Evaluation by engineering manager Milestone: 2.4 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: The goal is to have an easy interface (webui and osc) to find out the responsible person or team for a given package. The user should just be able to enter a package name or a disturl to find the right person. OBS always needs a project and package context to find the bugowner or maintainer. Therefore we need to specify a default project to search in. The following UI and workflow is suggested: UI offers just a text field beside a combo box. The combo box is set to the default marked project (eg. openSUSE:Factory). Aftwards also all maintenance_release projects shall be listed. Last but not least maybe an option to specify any other project. The UI shall check if it finds a source package container with the given name. If this fails it should search via binarie search. The returned project/package container needs to be checked for a devel area. The UI shows first defined bugowner if defined or maintainer as fall back. Business case (Partner benefit): openSUSE.org: Obsolete PDB. -- openSUSE Feature: https://features.opensuse.org/314593

1 3

[New: openFATE 312406] Support for ISC DHCP client for IPv6
by fate_noreply＠suse.de 18 Feb '13

18 Feb '13

Feature added by: Björn Voigt (bjoernv) Feature #312406, revision 1 Title: Support for ISC DHCP client for IPv6 openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Björn Voigt (bjoernv) Partner organization: openSUSE.org Description: Currently only "dhcp6c" (https://fedorahosted.org/dhcpv6/) can be selected as a DHCPv6 client in /etc/sysconfig/network/dhcp: # Which DHCPv6 client should be used? # Currently only the dhcp6c client is supported. # DHCLIENT6_BIN="" Since this client has been obsoleted by ISC dhcp, the DHCPv6 client of ISC should be used as default and as an alternative. -- openSUSE Feature: https://features.opensuse.org/312406

1 2

[New: openFATE 310070] openSUSE support for ARM
by fate_noreply＠suse.de 17 Feb '13

17 Feb '13

Feature added by: peter czanik (czanik) Feature #310070, revision 1 Title: openSUSE support for ARM openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: peter czanik (czanik) Description: As indicated by this [1] thread, and many earlier, there is demand for openSUSE ARM support. As discussed on the mailing list: - the build infrastructure is already there - there is a number of cheap and easily available existing ARM based devices (EFIKA MX [2], Sheeva Plug [3], Beagle Board [4], etc.) and many more are expected to arrive in the coming months - we need developers This last point is the most important, as creating an ARM port is more than just enabling ARM in the build service. Without enough developers this port can't be started, as there is a lot of work to do: - sometimes it is enough just to fix packaging errors (where only x86 is considered in the spec file) - often compiling on ARM needs some patching (either to find existing patches from other distributions or develop new ones) - the openSUSE (YaST, etc.) tools need to be made aware of ARM - testing on different target machines Please add your comment, if you are interested in the ARM port and also that how you could help this initiative! 1. http://lists.opensuse.org/opensuse-buildservice/2010-06/msg00293.html 2. http://www.genesi-usa.com/products/efika 3. http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit-us.aspx 4. http://beagleboard.org/ -- openSUSE Feature: https://features.opensuse.org/310070

1 26

[New: openFATE 312048] KDE "System settings" intergration of YaST
by fate_noreply＠suse.de 11 Feb '13

11 Feb '13

Feature added by: Lukas Sommer (sommerluk) Feature #312048, revision 1 Title: KDE "System settings" intergration of YaST openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Lukas Sommer (sommerluk) Partner organization: openSUSE.org Description: Integrate the YaST modules in the KDE "System settings" application. Not only with just 1 item that launched YaST, but with 1 item for each YaST module being directly visible in KDE System settings - in the right group. YaST NTP for example in the "Networking" group, YaST Boot loader in "System" ... -- openSUSE Feature: https://features.opensuse.org/312048

1 3

[New: openFATE 312581] Define destination file name for source service download
by fate_noreply＠suse.de 06 Feb '13

06 Feb '13

Feature added by: Justin Yaple (yaplej) Feature #312581, revision 1 Title: Define destination file name for source service download Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Justin Yaple (yaplej) Partner organization: openSUSE.org Description: To build my package I need to download two files with specific names. Unfortunately svn hosted at sourceforge.net when I download the tar files both have a name of "trunk" this is because of the path used to download them. <services> <service name="download_url"><param name="path">viewvc/opennop/daemon/trunk/?view=tar</param><param name="host">opennop.svn.sourceforge.net</param></service> <service name="download_url"><param name="path">viewvc/opennop/module/trunk/?view=tar</param><param name="host">opennop.svn.sourceforge.net</param></service> </services> To fix this you should add an optional parameter named "destination" or something like that so we can specify the destination filename. Then I can stop manually uploading the tar files after renaming them manually. Thank, -- openSUSE Feature: https://features.opensuse.org/312581

1 1

[New: openFATE 313172] Education li-f-e as a base template
by fate_noreply＠suse.de 04 Feb '13

04 Feb '13

Feature added by: Ahmed Rashed (ahmed_rashed) Feature #313172, revision 1 Title: Education li-f-e as a base template SUSE Studio: Unconfirmed Priority Requester: Desirable Requested by: Ahmed Rashed (ahmed_rashed) Partner organization: openSUSE.org Description: I liked Education li-f-e so much. But it is not 64 bit os, which restricts some of my favourite programs. As a workaround, I wish you provide an "Education li-f-e" base template in suse studio which supports both 32 and 64 bit architectures. This way I can build upon the Edi li-f-e and all its fine tuning which make it much more suitable for beginners trying to use Linux. If this is very difficult, I hope you could provide a kiwi or auto yast configuration with all the packages installed in EduLi-f-e file to be imported in my suse studio appliance. Thanks Business case (Partner benefit): openSUSE.org: I liked Education li-f-e so much. But it is not 64 bit os, which restricts some of my favourite programs. As a workaround, I wish you provide an "Education li-f-e" base template in suse studio which supports both 32 and 64 bit architectures. This way I can build upon the Edi li-f-e and all its fine tuning which make it much more suitable for beginners trying to use Linux. If this is very difficult, I hope you could provide a kiwi or auto yast configuration with all the packages installed in EduLi-f-e file to be imported in my suse studio appliance. Thanks -- openSUSE Feature: https://features.opensuse.org/313172

1 1

[New: openFATE 313376] mac like 'open file/url' behaviour
by fate_noreply＠suse.de 04 Feb '13

04 Feb '13

Feature added by: Cameron Blackwood (drkorg) Feature #313376, revision 1 Title: mac like 'open file/url' behaviour SUSE Studio: Unconfirmed Priority Requester: Important Requested by: Cameron Blackwood (drkorg) Partner organization: openSUSE.org Description: What command opens pdfs (it keeps changing)? tiffs? xls? On mac osx: open fred.pdf opens a pdf viewer open http://google.com/ opens the url in a browser etc Linux seems to have xdg-open (found via google and http://stackoverflow.com/questions/264395/linux-equivalent-of- the-mac-os-x-open-command ) which wraps the kde/gnome/whatever commands to do this and is installed on opensuse. Could we get xdg-open aliases to open by default? Being able to go 'open fred.pdf' and have the correct program open up would be great for new users. Open seems to currently be 'not found' and it would seem to make sense to import this feature from osx. Business case (Partner benefit): openSUSE.org: open whatever.ext gives you: * simplicity for new (and old) users * similar ui experience to osx all for one command line alias. -- openSUSE Feature: https://features.opensuse.org/313376

1 1

[New: openFATE 313417] WILDER WORLD
by fate_noreply＠suse.de 04 Feb '13

04 Feb '13

Feature added by: CHARLES WILDER (chucky5306) Feature #313417, revision 1 Title: WILDER WORLD SUSE Studio: Unconfirmed Priority Requester: Important Requested by: CHARLES WILDER (chucky5306) Partner organization: openSUSE.org Description: openSUSE Distrbution -- openSUSE Feature: https://features.opensuse.org/313417

1 2

[New: openFATE 314446] Add haskell packages to distribution
by fate_noreply＠suse.de 01 Feb '13

01 Feb '13

Feature added by: Herbert Graeber (hgraeber) Feature #314446, revision 1 Title: Add haskell packages to distribution openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Herbert Graeber (hgraeber) Partner organization: openSUSE.org Description: Haskell is an advanced purely-functional programming language. An open-source product of more than twenty years of cutting-edge research, it allows rapid development of robust, concise, correct software. With strong support for integration with other languages, built-in concurrency and parallelism, debuggers, profilers, rich libraries and an active community, Haskell makes it easier to produce flexible, maintainable, high-quality software. Business case (Partner benefit): openSUSE.org: Most other major distributions have it: http://hackage.haskell.org/platform/linux.html openSUSE is only to be found under "Information for other systems" Haskell is required by several applications that users have asked for: * Version control system darcs: http://lists.opensuse.org/opensuse-packaging/2012-07/msg00132.html * Pandoc markdown processor: https://features.opensuse.org/312777 * xmonad tiling display manager * hedgewars server -- openSUSE Feature: https://features.opensuse.org/314446

1 5

[New: openFATE 314699] Setting hostname during installation
by fate_noreply＠suse.de 25 Jan '13

25 Jan '13

Feature added by: Chris Gnineil (zerum) Feature #314699, revision 1 Title: Setting hostname during installation openFATE: Unconfirmed Priority Requester: Desirable Requested by: Chris Gnineil (zerum) Partner organization: openSUSE.org Description: Currently the hostname after installation is set to a random name with the syntax "linux.xxxxx.site". It would be nice if there is an option to set the hostname of the machine manually while the installation. -- openSUSE Feature: https://features.opensuse.org/314699

1 4

[New: openFATE 310075] Rss Owl
by fate_noreply＠suse.de 23 Jan '13

23 Jan '13

Feature added by: matthias propst (l1zard) Feature #310075, revision 1 Title: Rss Owl Package Wishlist: Unconfirmed Priority Requester: Neutral Requested by: matthias propst (l1zard) Description: Applications that collect data from RSS-compliant sites are called RSS readers or "aggregators." RSSOwl is such an application. RSSOwl lets you gather, organize, update, and store information from any compliant source in a convenient, easy to use interface, save selected information in various formats for offline viewing and sharing, and much more. It's easy to configure and the best of all: It's platform-independent . http://www.rssowl.org/overview -- openSUSE Feature: https://features.opensuse.org/310075

1 1

[openFATE 308186] ruby1.9
by fate_noreply＠suse.de 23 Jan '13

23 Jan '13

Feature added by: Dirk Herzhauser (dherzhau2) Feature #308186, revision 1 Title: ruby1.9 Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Dirk Herzhauser (dherzhau2) Description: I would be nice to have a ruby1.9 package as well as wn precompile wxruby gem -- openSUSE Feature: https://features.opensuse.org/308186

1 4

[New: openFATE 314522] Broadcom bcm4323 usb driver
by fate_noreply＠suse.de 23 Jan '13

23 Jan '13

Feature added by: John Shand (jshand2011) Feature #314522, revision 1 Title: Broadcom bcm4323 usb driver Package Wishlist: Unconfirmed Priority Requester: Mandatory Requested by: John Shand (jshand2011) Partner organization: openSUSE.org Description: Alot of people are turning to much faster wireless connections and they need to be able to use these devices, otherwise they turn back to the os they were using. Use Case: this would be used as a hardware driver for the broadcom chipset bcm 4323 usb device. -- openSUSE Feature: https://features.opensuse.org/314522

1 1

[New: openFATE 308377] Importing MS Windows user's settings, data as Ubuntu and Mandriva do
by fate_noreply＠suse.de 21 Jan '13

21 Jan '13

Feature added by: Mindaugas Baranauskas (embar-) Feature #308377, revision 1 Title: Importing MS Windows user's settings, data as Ubuntu and Mandriva do openFATE: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Mindaugas Baranauskas (embar-) Description: Importing MS Windows user's settings, data as Ubuntu and Mandriva do. This may be useful for new users in Linux – it would help to fell less stress. -- openSUSE Feature: https://features.opensuse.org/308377

1 6

[openFate 305472] Support transaction triggers for rpms
by fate_noreply＠suse.de 21 Jan '13

21 Jan '13

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305472, revision 1, last change by Title: Support transaction triggers for rpms openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: It's important to be able to run once after all packages have been installed a command (instead of running the command after each of x packages getting installed, which would make the process much slower). That's basically a post-transaction trigger. For background, see https://bugzilla.novell.com/show_bug.cgi?id=365649 and especially comment #14 from Stanislav. (note that this is work that should be done in upstream rpm, not as patches) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305472

1 8

[New: openFATE 308705] Show Grub boot menu when resuming from hibernate (suspend to disk)
by fate_noreply＠suse.de 10 Jan '13

10 Jan '13

Feature added by: Rafael Belmonte (EagleScreen) Feature #308705, revision 1 Title: Show Grub boot menu when resuming from hibernate (suspend to disk) openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Rafael Belmonte (eaglescreen) Description: When I resume my computer after hibernate (suspend to disk) with OpenSuse, Grub boot menu is not displayed, so I am forced to boot into OpenSuse in the case of a dual boot system. Other GNU/Linux distributions like Debian/Ubuntu display the Grub boot menu when you power on the computer after hibernate with GNU/Linux, and booting into MS Windows (or other) is offered. The next time you boot again into GNU/Linux it resumes the last hibernated session. I think OpenSuse should follow this line too. -- openSUSE Feature: https://features.opensuse.org/308705

1 3

[New: openFATE 312582] Separate repos devel, QA and production with package promotion
by fate_noreply＠suse.de 09 Jan '13

09 Jan '13

Feature added by: Justin Yaple (yaplej) Feature #312582, revision 1 Title: Separate repos devel, QA and production with package promotion Buildservice: Unconfirmed Priority Requester: Important Requested by: Justin Yaple (yaplej) Partner organization: openSUSE.org Description: It would be great if after a package was built it would by default be placed into a devel repo for the project then it could go through some initial testing and be promoted to the QA repo where it would go through more seriouse testing to finally be propoted to the production repo where it would be downloaded. This would allow a separate repo be used in separate appliance builds in susestudio and allow for a separate devel beta and production appliance. Thanks -- openSUSE Feature: https://features.opensuse.org/312582

1 1

[New: openFATE 312755] Overhaul and simplification of configuration for multilanguage support
by fate_noreply＠suse.de 09 Jan '13

09 Jan '13

Feature added by: Timothy Butterworth (TimButterworth) Feature #312755, revision 1 Title: Overhaul and simplification of configuration for multilanguage support Buildservice: Unconfirmed Priority Requester: Important Requested by: Timothy Butterworth (timbutterworth) Partner organization: openSUSE.org Description: As more and more user's require multilingual support it would be great if the installer and YaST2 were overhauled to provide this setup with ease based on the latest available fonts and input managers. Currently their are some settings like adding a second language available in YaST2. The Language bar is also useful. It would be really great if their was a simple way to configure this from install or YaST2 with support for KDE4 keyboard layouts. Their are a number of problems users run into currently. First their does not seem to be a good how to guide. Secondly SKIM/SCIM packages in openSUSE 11.4 do not seem to support GTK3/QT4. SKIM is still built for KDE3/QT3 and needs to have QT4 front end tools: language bar/ tray icon / plasma widget and support for GTK3/QT4 input. Third many users run into issues configuring the env variables in bash. Fourth ibus - ibus defaults to GTK. It would be great if two packages existed one compiled for QT4 and one for GTK3. Fifth uim also has issues and I have not been able to get it to work with QT4 either. Their are of course many other input methods as well. It would be great as KDE4 is the default install choice to have tools setup to work with KDE4 system config, keyboard layouts for ease of configuration. Also env LANG and LANGUAGE do not change the local settings in all KDE4 apps and this must be completed through the KDE4 configure desktop > local configuration tool. Currently YaST2 local configures the entire system instead of an individual user. This should be expanded with a means change individual user accounts as many systems may be used by individuals who's native language may be different. This would be a great feature for openSUSE Edu as well. bottom line: input method selection should be simplified through software wizard or how to guide. SKIM/SCIM need GTK3/QT4 support. The later is available on Ubuntu and has been for quite a while. Thank You -- openSUSE Feature: https://features.opensuse.org/312755

1 3

[New: openFATE 314601] Pev -Tthe PE file analysis toolkit
by fate_noreply＠suse.de 09 Jan '13

09 Jan '13

Feature added by: Ewerson Guimaraes Crash (crashbrz) Feature #314601, revision 1 Title: Pev -Tthe PE file analysis toolkit Buildservice: Unconfirmed Priority Requester: Important Requested by: Ewerson Guimaraes Crash (crashbrz) Partner organization: openSUSE.org Description: pev is a PE file analysis toolkit that includes some nice programs to work with PE files in many systems It can be useful for programmers, security analysts and forensic investigators. It's licensed under GPLv3+ terms. https://github.com/merces/pev/blob/master/readme -- openSUSE Feature: https://features.opensuse.org/314601

1 1

[New: openFATE 309190] include FFADO (upgrade from freebob)
by fate_noreply＠suse.de 28 Dec '12

28 Dec '12

Feature added by: Steffen Klein (sklein7) Feature #309190, revision 1 Title: include FFADO (upgrade from freebob) openSUSE-11.3: Unconfirmed Priority Requester: Important Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Steffen Klein (sklein7) Description: FFADO v2 is released since December 2009. It is the successor of the freebob firewire audio driver. The FFADO-release supports more hardware than freebob. -- openSUSE Feature: https://features.opensuse.org/309190

1 6

[New: openFATE 314708] Netflix-desktop for opensuse
by fate_noreply＠suse.de 28 Dec '12

28 Dec '12

Feature added by: Ralph Bromley (MadmanRB) Feature #314708, revision 1 Title: Netflix-desktop for opensuse openFATE: Unconfirmed Priority Requester: Desirable Requested by: Ralph Bromley (madmanrb) Partner organization: openSUSE.org Description: Recently netflix has been cracked for linux, and its offered on competing distributions such as ubuntu, fuduntu and arch. But there is no native package for opensuse nor installing an RPM fix the issue as the only RPM based distro that has netfilix is fuduntru and its RPM does not seem to work under opensuse. packaging this and wine-compholio will be a solution, converting this from alien doesnt work and really compiling packages are a pain for new users. -- openSUSE Feature: https://features.opensuse.org/314708

1 4

[New: openFATE 308243] Add Koha to opensuse Education Distro please. open-source ILS. http://koha.org/
by fate_noreply＠suse.de 28 Dec '12

28 Dec '12

Feature added by: Glenn Doig (doiggl) Feature #308243, revision 1 Title: Add Koha to opensuse Education Distro please. open-source ILS. http://koha.org/ Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: Add Koha to opensuse Education Distro please. Koha is a full-featured open-source ILS. http://koha.org/ Thanks -- openSUSE Feature: https://features.opensuse.org/308243

1 14

[New: openFATE 312796] opensuse 12.1 - integrate libKGoogle into Kontact to share google calendars etc
by fate_noreply＠suse.de 24 Dec '12

24 Dec '12

Feature added by: Jedi Beeftrix (Jedibeeftrix) Feature #312796, revision 1 Title: opensuse 12.1 - integrate libKGoogle into Kontact to share google calendars etc openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Jedi Beeftrix (jedibeeftrix) Partner organization: openSUSE.org Description: A GSOC project that ought to be integrated into Kontact in 21.1: http://progdan.cz/2011/08/akonadi-google-resource-complete-rewrite/ -- openSUSE Feature: https://features.opensuse.org/312796

1 13

[openFATE 300758] Show unneeded packages
by fate_noreply＠suse.de 20 Dec '12

20 Dec '12

Feature changed by: Michael Schröder (mlschroe) Feature #300758, revision 147 Title: Show unneeded packages openSUSE-10.2: Rejected by Thorsten Kukuk (kukuk) reject date: 2006-08-02 11:31:19 reject reason: For SL10.2 we have to get libzypp really stable and fast before we add new features. Priority Requester: Important openSUSE-11.3: Done Priority Requester: Desirable Projectmanager: Important Requested by: JP Rosevear (jproseve) Partner organization: openSUSE.org Description: The package manager should learn to show unneeded packages (packages which are not required by other packages and are not in wanted selections) and allow to deinstall them like the popular debfoster/deborphan tools. A typical use case: user installs an application which pulls in some dependencies to test it, uninstalls the application shortly after or way later but the dependencies stay unused installed on the system. Commandline UI (zypper) only. References: https://bugzilla.novell.com/show_bug.cgi?id=166132 Discussion: #1: Jiri Srain (jsrain) (2007-06-05 13:46:00) Schubi, is there any possibility to make solver tell which packages are orphanized? It would be interesting especially if the packages which are marked for deletion were considered as non-installed (eg. if foo- devel is installed but marked for deletion and nothing else requires foo, then foo is orphanized). #2: Stefan Schubert (schubi2) (2007-06-06 11:04:04) (reply to #1) Currently not cause the solver has no information about who (user, package,...) has triggered the installation of a package. If we are storing this information it would be possible for solver to remove these kind of packages too. It is not simple but doable. By the way, we will have to store this kind of information in the future. E.g. we need to save the "keep state by user" in a database in order to regard this state in future solver runs. #3: Jiri Srain (jsrain) (2007-06-06 14:25:07) (reply to #2) Looks like a missunderstanding. Basically every package wihch is not required/recommended/suggested or doesn't enhance anything that is installed and not marked for deletion is IMO considered to be orphanized. If user eg. wants to remove a pattern including all its packages (which are not required by something else), solver providing this kind of information would help a lot (and I don't think that we would need any other information to be stored. #4: Stefan Schubert (schubi2) (2007-06-06 15:33:44) (reply to #3) I do not think so. What does "orphanized" mean ? Let me take your example from comment #1. foo should be deleted too if the user delete foo-devel and foo has been installed due the requirement of foo-devel. BUT the user will kill us if we are deleting foo although the user has installed foo explicit sometime ago in a seperate installation workflow. So this information ( The USER has installed foo) will be currently not saved and is needed here to decide if foo has to be deleted or not. #5: Stefan Schubert (schubi2) (2007-06-06 15:39:47) (reply to #3) Lets take your example concerning the erasing of patterns. That is much more complex. I have already described the problem here: http://en.opensuse.org/Libzypp/Solver#Known_Problems " Proper behaviour of erasing patterns" There are already some bugzilla entries: Bug 274283 - Delete iFolder from YaST makes eDirectory Delete mandatory Bug 238250 - YaST does not upgrade an Add-on Product #6: Jiri Srain (jsrain) (2007-06-08 16:46:32) See also https://bugzilla.novell.com/show_bug.cgi?id=166132 This is another use case for the same solver functionality #8: Federico Lucifredi (flucifredi) (2008-06-12 20:46:17) this should be commandline-only, definitely an advanced-user option. #9: Federico Lucifredi (flucifredi) (2008-06-12 20:47:28) cut from description: See Bug 140346 #10: Duncan Mac-Vicar (dmacvicar) (2008-11-03 11:24:53) As discussed in Prague, this could be done using the package history once we have a reader. #11: Karsten König (remur) (2009-01-19 10:09:49) How about using rpmorphan, I agree with flucifredi about the command line idea... http://rpmorphan.sourceforge.net/ And otherwise you could use their system to find orphanized packages and display them in yast but make clear that deleting -all orphanized packages will also delete the ones explicitly installed... (it only detects wether the package fullfiles any requirement...) #12: Ján Kupec (jkupec) (2009-01-19 14:48:38) (reply to #11) I'm not the solver developer, but i'm pretty sure it's easy (and probably more effective) to find the 'leaf' packages (that's what rpmorphan seems to do) using existing solver (see satsolver package). But we don't want to just highlight leaf packages, we want to remove unused packages, that is all leaves minus those explicitly installed. So we will feed the solver with this 'explicitly-installed' information. The package history will be the source of this info for now. Maybe later we find some way to store this info that could be used across tools (e.g. directly in the rpm db). So rpmorphan will be able to use this info as well. #13: Pavol Rusnak (prusnak) (2009-01-19 15:44:26) (reply to #12) Yes, that's good idea. Detecting leaf packages is the first step. Detecting which ones to remove (i.e. not explicitly installed) is the second. I think that rpmorphan shows all leaf packages, but it selects only the ones that start with "lib". If we strictly followed library packaging policy that would do the trick. btw. rpmorphan is packaged in Contrib (http://en.opensuse.org/Contrib) #14: Michal Smrž (ilfirin) (2009-03-07 20:05:22) (reply to #11) I am afraid of using rpmorphan to do this. Cause last time, I tested it, it wants to remove libdvdnav and libdvdcss libraries. This is very bad. It leads to many not advanced users to ask in phorums "Why OpenSUSE is not playing DVDs anymore?" I see many problems this could make. #15: Christoph Thiel (cthiel1) (2009-04-21 15:23:06) We don't have the resources to implementing this. Seems to be a prefect fit for a community project. #17: Piotrek Juzwiak (benderbendingrodriguez) (2009-04-22 07:58:47) Maybe the idea to accomplish this would be simply by using the packages. xml file and diff it. We can already export what packages we got right? So if it would compare the packages.xml before installation and after it would then delete it. There is a problem when installing many packages, they would all have to be "grouped" which pulled which dependencies. #20: Vladimirs Kuzmins (vovachaka) (2009-10-26 16:27:51) This feature is a specially important, now when we have distro upgrade, which changes a lot of dependencies and a lot of obsolete packages remain installed. Please, someone implement it! #21: Thomas Göttlicher (tgoettlicher) (2009-10-26 16:41:29) I've added a view for orphaned packages in yast2-qt-pkg. There is a package group "orphaned packages" similar to "suggested packages" and "recommended packages" in yast2-qt-pkg version 2.18.17. #22: Atri Bhattacharya (badshah400) (2009-10-31 14:55:26) (reply to #21) Thanks for implementing this much needed feature. But this feature does not work with the gtk interface in 11.2 RC2; please have this added for the final release of 11.2. #23: Kornél Jahn (cornail) (2009-11-02 07:48:05) (reply to #21) Tried to test this but didn't seem to work on RC2: Orphaned packages view is empty. E.g. installed blender, which pulled yafray. After uninstalling blender, yafray remained installed but didn't show up as an orphaned package. Also installing audacity or inkscape pulled a lot of dependencies which were not showed as orphaned after uninstalling them. #24: Kornél Jahn (cornail) (2009-11-02 08:06:38) (reply to #23) Since it is marked as done, I filed a bug for it: https://bugzilla.novell.com/show_bug.cgi?id=551771 (https://bugzilla.novell.com/show_bug.cgi?id=551771) #25: Ján Kupec (jkupec) (2009-11-30 14:18:55) (reply to #21) There has been a misunderstanding here. What Thomas implemented is a view of packages that no longer have update candidates (those which are probably no longer maintained, thus 'orphaned'). This very fate request (IMO) incorrectly uses the word 'orphaned' for what is better described as "unused packages" or "no longer needed packages", or "unnecessary packages". Definitely not orphans (deborphan/rpmorphan is also a misfortunate name IMO). Anyway, whether orphan or unused, this feature is not implemented yet, thus i'm reopening it for 11.3. #26: Ján Kupec (jkupec) (2009-11-30 14:21:27) reopening for 11.3 (see comment #25) #27: Ján Kupec (jkupec) (2009-11-30 14:30:44) I suggest to call these packages unused instead of orphaned . I don't want to decide this by myself, so please speak up. Here are my arguments: 1) the word 'orphan' describes something that has lost its parent(s). In this case, it is actually the child that was lost - a package that depended on other package has been removed. The parent package is still installed, but there's no more use for it - it's unused . 2) we (and a few other distros and communities as well) already use orphaned to describe packages that are no longer cared for - unmaintained packages, packages dropped from distros. #28: Ján Kupec (jkupec) (2009-11-30 15:05:21) (reply to #27) Thomas suggests that perhaps not needed (or no longer needed ) would be better than unused since 'unused' can be confused with 'not used by user' rather than 'not used by other packages'. #29: Roberto Mannai (robermann79) (2009-11-30 15:40:37) Undependent packages : packages which don't have any(more) dependency. #30: Kornél Jahn (cornail) (2009-11-30 16:15:08) I also support the not needed / no longer needed version. Orphaned is bad since it can be misunderstood, just like "undependent package", if Roberto meant to suggest it as a description for this phenomenon. Case A: If I install manually package X, which doesn't have any dependencies nor is it referred to by any other package, it is not a "not needed" one. 'Cause it was manually installed by the user. Case B: Package X is installed automatically as a dependency while installing package Y. Package Y is then removed, but X stays, with no other package referring to it as a dependency. X is then a "not needed" package. #31: Roberto Mannai (robermann79) (2009-11-30 17:00:02) (reply to #30) +1 Kornél Regarding Case A: of course "not needed package" is a subset "undependent package" - "not needed" catches the user's point of view and it is more precise. Nevertheless, determining that "not needed" packages is a hard job, so it could be a good starting point just knowing which are the "undependent" ones (at least as a first step). #32: Roberto Mannai (robermann79) (2009-11-30 17:47:05) (reply to #31) The user could have a graphical list of "undependent packages", which then he could mark each of them as "used/not used". The GUI then could suggest the "unused packages" for removal (this being a temporary but useful use case). #33: Ken Schneider (kensch) (2009-12-15 18:15:55) When you install a package using package management it checks to make sure all dependencies are also installed or adds them to the install list via the "Requires" feature. When de-installing the package check the list of "Requires" packages and see which ones can also be de- installed. That way there are no left over packages. If one of the "Requires" packages are also needed by other packages they are left installed. I am no where near being a programmer but that would seem to be simple to do. #34: Ján Kupec (jkupec) (2009-12-15 18:47:57) (reply to #33) Such procedure would also wipe out packages that you still want to use. E.g. you have nagios-plugins-zypper, which requires zypper. Now, 'zypper remove nagios-plugins-zypper' would realize that after removing nagios-plugins-zypper nothing requires zypper, and would want to remove zypper as well. So what your idea lacks is a list of packages that were installed in the past based on explicit request by user. The procedure must avoid removing these. See also c#12 #36: Ján Kupec (jkupec) (2009-12-15 18:47:02) So i'm renaming this fate request to 'Show unneeded packages' (to make it shorter) to avoid further confustion. #37: Don Hughes (dehughes) (2009-12-15 19:10:53) I also would like to see this feature. I currently use rpmorphan with a list of things that it will mark that I know that I need. I also occationally go through yast2 and try to uninstall things that I do not recognize and see if they are flagged as being needed by something else. Both time consuming and error prone. And, a lot of packages seem to be some what careless in what the require for prereqs - pulling in KDE,gnome, and X11 packages on text- only machines for example; which then triggers a flood of KDE, gnome, and X11 library installations which I then have to mannually uninstall and mark as taboo. On my external facing servers I do not like to have any extra/unneeded/unwanted packages to provide possible attack vectors. #39: Rafael Belmonte (eaglescreen) (2010-01-10 22:43:40) Hello, this is one of the main causes of I use more Debian/Ubuntu than OpenSuse. Debian & Ubuntu already have this implemented. I think this is a fundamental aspect to work in OpenSuse. Debian & Ubuntu can distinguish packages that were manually installed and packages that were installed just to satisfy dependencies. OpenSuse needs to do this too. #40: Tim Edwards (tk83) (2010-01-27 15:46:00) I'd also like to see this, Mandriva added it in a couple of releases ago and it's great. It's really missing in Opensuse #41: Eduard Huguet (eduardhc) (2010-03-02 15:55:43) (reply to #40) Agreed. Being a long time user of both Gentoo and Ubuntu, I was really shocked to discover that zypper was lacking this feature. Even more: when talking about Linux with friends I always make mention of this kind of "autoremove unneeded" option as one of the strong points of Linux package managing systems, as I was really taking for granted that any package manager out there had this feature included... Regards. #42: Rémy Marquis (spyhawk) (2010-05-02 17:13:32) Michael Andres started to implement this feature in Libzypp 7.4, see http://lists.opensuse.org/zypp-devel/2010-04/msg00033.html #45: Robin Knapp (rknapp) (2010-07-14 13:00:55) (reply to #42) --clean-deps works indeed, but what about just showing unneeded packages? It's mentioned in http://en.opensuse.org/Product_highlights#Package_management_with_zypper but I haven't found any information about this feature. #46: Moqi Ba (bamoqi) (2011-07-24 01:37:08) This FATE is marked as done but as of 11.4 "zypper rm -u" doesn't work without a package name. It cannot actively find and remove orphaned package which are auto-installed, like "apt-get autoremove" does. #47: Michael Schröder (mlschroe) (2012-02-13 12:34:53) (reply to #46) True. We can add that for 12.2, but the quality of the result really depends on knowing which packages were selected by the user and which packages were dragged in via dependencies. #49: Cristian Morales Vega (reddwarf) (2012-04-11 16:06:31) (reply to #47) That info is available already through the history, isn't? The only problem I know of is bnc#679213... that I have no idea if was fixed since the info is not public :-( #50: Jiri Srain (jsrain) (2012-08-21 11:52:03) (reply to #49) I have this information in the log of my 12.1. + #54: Michael Schröder (mlschroe) (2012-12-20 16:29:00) (reply to #47) + Just for completeness: 12.2 has an "unneded packages" package group. #48: Joachim Plack (jplack) (2012-02-13 13:58:53) For images generated in a SLEPOS environment, we would like the to reduce the footprint. So we'd like to find out all packages where last use (per read access time stamp) <= install time. This list we would the transfer back to the image creation server so that the next image gets reduce to what we really need. Btw. removedthe big list of rejected openSUSEs besides the first and last to get a better overview again while keeping the history #51: Jiri Srain (jsrain) (2012-08-21 11:54:04) (reply to #48) Jack, does this necessarily involve libzypp/zypper? I think that this is a rather specific use-case, which can be scripted easily. Besides, I suggest to handle this as a separate request - this one is about unneeded, not about unused. -- openSUSE Feature: https://features.opensuse.org/300758

1 0

[New: openFATE 314653] Opensuse 12.3 - use kernel 3.8 to ensure good Intel Haswell support in H1 2012
by fate_noreply＠suse.de 14 Dec '12

14 Dec '12

Feature added by: Jedi Beeftrix (Jedibeeftrix) Feature #314653, revision 1 Title: Opensuse 12.3 - use kernel 3.8 to ensure good Intel Haswell support in H1 2012 openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Jedi Beeftrix (jedibeeftrix) Partner organization: openSUSE.org Description: http://www.phoronix.com/scan.php?page=news_item&px=MTIzNzE -- openSUSE Feature: https://features.opensuse.org/314653

1 5

[New: openFATE 314608] Files and attributes / properties
by fate_noreply＠suse.de 10 Dec '12

10 Dec '12

Feature added by: Francesco Noacco (FireLink) Feature #314608, revision 1 Title: Files and attributes / properties openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Francesco Noacco (firelink) Partner organization: openSUSE.org Description: I'd like to display the date the file was created in addition to the modification date including minutes and seconds. Business case (Partner benefit): openSUSE.org: I got used to observe it to remind me of the time when I started some of the work. I also noted that on systems win in files (written or modified by linux) that date appears identical or 1-2 seconds after the date of change (!) While folders are simply changed the date to win just mean the date the folder creation (i find it more useful because the last change is detectable by ordering inside files). I imagine that this "revolution" must be taken in accordance with the whole community linux, but from my point of view there are more information and better you can manage themselves. -- openSUSE Feature: https://features.opensuse.org/314608

1 2

[New: openFATE 308497] Update to GRUB v2
by fate_noreply＠suse.de 08 Dec '12

08 Dec '12

Feature added by: Jeff Mahoney (jeff_mahoney) Feature #308497, revision 1 Title: Update to GRUB v2 openSUSE-11.3: New Priority Requester: Important Requested by: Jeff Mahoney (jeff_mahoney) Partner organization: openSUSE.org Description: Every single bug or feature that anyone has developed for GRUB 0.97 has been rejected by the upstream project in favor of using GRUB 2. There has been resisitence in the distribution community to switching boot loaders, but this stalemate isn't going to go away. The code itself isn't well written or well maintained. Adding a new feature involves jumping through a lot of hoops that may or may not work even if you manage to work around all the runtime limitations. For example, a fs implementation has a static buffer it can use for memory management. It's only 32k. For complex file systems, or even a simple journaled file system, we run into problems (like the reiserfs taking forever to load bug) because we don't have enough memory to do block mapping for the journal so it needs to scan it for every metadata read. (Yeah, really.) GRUB v2 has a cleaner design, is modular, and it has support for multiple architectures including i386, x86-64, and powerpc. Support for ia64 is said to be forthcoming. EFI support is already there. More importantly, it supports far more file systems and has native MD RAID and LVM support. Adding support for a new file system is much easier, cleaner, and has fewer limitations than with GRUB 0.97. Business case (Partner benefit): openSUSE.org: * Supportability - upstream bug fixes and development community * Features - better fs support, native RAID and LVM support -- openSUSE Feature: https://features.opensuse.org/308497

1 68

[openFATE 312321] Replace blowfish with sha512 as password hash
by fate_noreply＠suse.de 08 Dec '12

08 Dec '12

Feature changed by: Michael Catanzaro (Golbats_Everywhere) Feature #312321, revision 19 Title: Replace blowfish with sha512 as password hash - openSUSE Distribution: Implementation + openSUSE Distribution: Done Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: Since upstream has meanwhile a good replacement for DES crypt (sha256 and sha512), we should follow the other distributions and switch to sha512 as default password hash for local accounts. For openSUSE this means: * Make sha512 the new password hash in pwdutils * add support for sha512 to YaST (core, security, users) * Remove blowfish as option from YaST2 or at least change the default * Drop libxcrypt Business case (Partner benefit): openSUSE.org: More secure password hashing, which are harder to crack with passwd cracking software. Discussion: #1: Bruno Friedmann (bruno_friedmann) (2011-05-17 17:24:55) Want to add me as interested but get an error Errorcode: 0 Message: undefined method `next=' for nil:NilClass #2: Thomas Schmidt (digitaltomm) (2011-05-17 17:35:32) (reply to #1) Please try again, that was caused because the product openSUSE 11.5 was not created completely. #3: Thorsten Kukuk (kukuk) (2011-05-18 15:21:35) pwdutils is adjusted. Lukas, can you please remove blowfish from YaST2 as option to choose and link yast2-core against libcrypt and not libxcrypt? #4: Ludwig Nussel (lnussel) (2011-07-06 14:56:32) (reply to #3) I've filed a separate feature for dropping libxcrypt as a clean solution requires a glibc with gensalt functions to avoid copies of them everywhere -> 312617. #6: Ludwig Nussel (lnussel) (2011-07-11 14:58:41) (reply to #3) unfortunately the yast interface to the crypt functions is not as flexible as it should be. yast has separate built-in functions for each hash so adding support for sha512 requires adding a new built-in rather than just passing down some different salt string. #8: Lukas Ocilka (locilka) (2011-07-19 14:24:50) (reply to #6) Jiri, we already do support SHA-512 in YaST Users, don't we? Additionally, would you remove the blowfish option from YaST Users, please? #10: Jiří Suchomel (jsuchome) (2011-07-19 14:40:23) (reply to #8) Yes, we do have sha512, as a result of feature 309705, #12: Jiří Suchomel (jsuchome) (2011-07-20 11:20:04) (reply to #8) I've removed offering of blowfish from yast2-users and yast2-security. The function call of cryptblowfish is still there, I'll remove it once it is dropped from yast2-core #9: Lukas Ocilka (locilka) (2011-07-19 14:23:42) (reply to #3) These YCP built-ins are Arvin's speciality. Arvin, could you, please, do that change requested by Thorsten in comment #3? #11: Arvin Schnell (aschnell) (2011-07-19 17:38:42) (reply to #9) I will look at it when fate #312617 is finished (glibc provides salt functions). #5: Robert Davies (robopensuse) (2011-07-06 15:26:42) Background for those who haven't seen it. Migration of current from "blowfish" hashed passwords, ought to be mandatory, because of the sign extension bug that's been found (in "John the Ripper". As, current user passwords would have to be changed anyway, it makes sense to force migrate to sha512 anyway as part of update. See "A hole in crypt_blowfish" http://lwn.net/Articles/448699/ (http://lwn.net/Articles/448699/) for explanation of the problem & discussion. Executive summary "crypt_blowfish developer Alexander Peslyak (aka Solar Designer) analyzed the effects of the bug and found that some password pairs would hash to the same value with only minimal differences (e.g. "ab£" hashed to the same value as "£"), which would make password cracking easier. A further analysis shows that some characters appearing just before one with the high bit set may be effectively ignored when calculating the hash." #7: Jan Engelhardt (jengelh) (2011-07-12 15:39:29) (reply to #5) The hole in crypt_blowfish has nothing to do with a desire to move off Blowfish. It's much more that Glibc has never offered Blowfish and openSUSE carried a patch for it, whereas SHA-512 is available upstream. -- openSUSE Feature: https://features.opensuse.org/312321

1 0