April 2012 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306996] "out-of-date" package flag
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Artyom Aleksuk (h31) Feature #306996, revision 1 Title: "out-of-date" package flag Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Artyom Aleksuk (h31) Description: There is a very good feature in Archlinux's package list. Anybody (not only registered users) can mark packages as out-of-date. E-mail notification will be sent to a package builder and the package will be marked as out-of-dated on the site until the package would be refreshed. You can see this function, for example, here (http://www.archlinux.org/packages/extra/x86_64/flashplugin/) and here (http://www.archlinux.org/packages/flag/29883/) . It will be very good to make marking at a package search ( here (http://software.opensuse.org/search) ). For example, this feature may be situated below "Go to OBS Project". It should be useful both for Factory and home projects. Sorry for my language. -- openSUSE Feature: https://features.opensuse.org/306996

1 3

[openFATE 306948] Estimation on waiting time on a package on obs
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Glenn Doig (doiggl) Feature #306948, revision 1 Title: Estimation on waiting time on a package on obs Buildservice: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: Hello, When your project is blocked in the queue because it is waiting for something to build e.g(binutils) can a time estimate be given as to how long to wait before it may start processing - put that estimation on the 'Package AAA (Project BBB home:CCC)' page when you view the page. Example: (Packages waiting queue * Average Job time) + (Your package Nth position in the Packages blocked queue * Average Job time ) = value Put that value in the package page. Some details used from https://build.opensuse.org/monitor It would be nice to know when your package may start to process. Cheers Glenn Responses so far sourced from http://lists.opensuse.org/opensuse-buildservice/2009-07/msg00235.html > One could implement something, but it will not be very reliable, because the state and order can change with any further submission. > Adrian and > I suggest to file a feature request using features.opensuse.org. But first:What to others think? Do you consider such an estimate ok? Or should we not publish anything since it might change too often? > Andreas -- openSUSE Feature: https://features.opensuse.org/306948

1 6

[openFATE 306472] Another view of build service repositories
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Jigish Gohil (cyberorg) Feature #306472, revision 1, last change by Title: Another view of build service repositories Buildservice: Unconfirmed Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: Apart from the current structure another view of oBS repositories that can greatly improve navigation of oBS repositores could be like this: download.opensuse.org/distro1/project1 /project2 /project3 /distro2/project1 /project2 /project3 /Medias/project1/iso /other /project2/iso /other /project3/iso /other This can probably be done by keeping current structure and creating symlinks. -- openSUSE Feature: https://features.opensuse.org/306472

1 3

[openFATE 306469] "Publish Current State" Button
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Stephan Binner (Beineri) Feature #306469, revision 1, last change by Title: "Publish Current State" Button Buildservice: Unconfirmed Priority Requester: Important Requested by: Stephan Binner (beineri) Description: Building packages can take quite some time (and publishing too). While upgrading a whole chain of interdepending packages some can fail to build and leave the repository in an inconsistent and non-installable state => not good to leave the repository in "Publish" state (over night/week-end). Switching from "Not Publish" to "Publish" state AFAIK doesn't trigger immediate publishing but only when some package build finished. It would be very nice to have a "Publish Current State" button which allows one to publish the current package state without having to manually switch publishing state, triggering a fake/unnecessary package rebuild and having to wait/remember to switch back to "Not Publish" state in time. -- openSUSE Feature: https://features.opensuse.org/306469

1 1

[openFATE 305874] Enable peer to peer downloading of patches/software
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Johan Kotze (gogga) Feature #305874, revision 1, last change by Title: Enable peer to peer downloading of patches/software Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Johan Kotze (gogga) Description: It would be great if we could somehow include a peer to peer functionality for the download of patches/packages. This would greatly reduce the number of mirrors required and would increase the performance for many users in countries with limited international bandwidt. I was thinking that we host a torrent tracker on opensuse.org and build a torrent client into zypper/libzypp and allow the user to allocate a portion of disk space for downloaded packages. Most modern systems have ample disk space and should be able to spare around 4GB for downloaded packages. This is also in line with the spirit of community where we help each other out. If it works well, it could also be used to distribute patched internally inside an organization when they deploy SLE. -- openSUSE Feature: https://features.opensuse.org/305874

1 6

[New: openFATE 313152] Distribution cleanup (smaller disk footprint)
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #313152, revision 1 Title: Distribution cleanup (smaller disk footprint) openSUSE Distribution: New Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: We want to have an as small as default base system (default text install) as possible. For this, I suggest to install a base system and investigate then what can be done to decrease the footprint. One idea is to check documentation (in /usr/share/doc/packages) and move them to doc or devel package (with the exception of license files). Also, we can check whether all dependencies (manual requires) are still correct - or in other words: Does every package that's there needs to be in the base install? Business case (Partner benefit): openSUSE.org: A small base system is important especially for appliances and virtual environments. -- openSUSE Feature: https://features.opensuse.org/313152

1 3

[New: openFATE 310310] Installer partition layout to allow "Whole Disk Usage"
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: Darryl Miles (dlmiles) Feature #310310, revision 1 Title: Installer partition layout to allow "Whole Disk Usage" openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Darryl Miles (dlmiles) Description: Currently the installer doesn't provide any option for Whole Disk Usage for a single purpose (such as rootfs or swap or /home etc...). Whole disk usage means there is no partition table and that file-system or swap is formatted directly. This has use-cases for virtulization where it is easier for the hypervisor to provision two block devices to the guest, one for rootfs and one for swap. These may come from LVM, SAN, etc... it is easier to manage because resizing either is a straight forward event due to the single purpose of each block device. One possible option to shoe-horn it into the UI would be under the Expert.../Advanced... buttons when either a partition or a disk device is selected. More ideas suggested in the bugzilla link further down this comment. Other possible considerations go with the bootloader options for installing GRUB. It would need to be adjusted to disallow/auto-disable MBR when no partition table is present. But the option still remains to install in the rootfs. Also submitted as ENH in Buzilla please read => https://bugzilla.novell.com/show_bug.cgi?id=628056 "installer doesn't support whole-disk usage", since this contain other comments not found here. -- openSUSE Feature: https://features.opensuse.org/310310

1 6

[New: openFATE 310103] wireless bridge configuration support in sysconfig
by fate_noreply＠suse.de 06 Aug '13

06 Aug '13

Feature added by: Marius Tomaschewski (mtomaschewski) Feature #310103, revision 1 Title: wireless bridge configuration support in sysconfig openSUSE-11.4: New Priority Requester: Important Requested by: Casual J. Programmer (casualprogrammer) Developer: (Novell) Developer: (Novell) Description: Wireless interfaces currently can not be bridged. In Windows XP it is quite easy to create and operate a bridge, saving one to setup and maintain all sorts of route information. It would make sense to support the bridged configuration in sysconfig when hostap implements 802.11c. Relations: - network bridge fails to integrate wlan (ipw3945) with WPA (novell/bugzilla/id: 541817) https://bugzilla.novell.com/show_bug.cgi?id=541817 - Bridge FAQ: I still don't understand!! (url: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#I_s…) - Bridge FAQ: It doesn't work with my Wireless card! (url: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#It_…) -- openSUSE Feature: https://features.opensuse.org/310103

1 3

[New: openFATE 310491] Add dracut to openSUSE
by fate_noreply＠suse.de 01 Aug '13

01 Aug '13

Feature added by: Luis Medinas (lmedinas) Feature #310491, revision 1 Title: Add dracut to openSUSE openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Luis Medinas (lmedinas) Description: Dracut is suppose to be a replacement for the old initrd tools like mkinitrd. >From the project description, dracut is an initramfs infrastructure. Unlike previous initramfs systems, Dracut aims to have as little as possible hard-coded into the initramfs. It contains specific configuration files for init drivers and includes plymouth support. Dracut advantage seems to be a modern replacement to generate initrd and it's suppose to be easy to use/manage. -- openSUSE Feature: https://features.opensuse.org/310491

1 24

[New: openFATE 309148] boot-process: starting network / dbus with ldap authentification
by fate_noreply＠suse.de 30 Jul '13

30 Jul '13

Feature added by: Alexander Fleischer (afleischer) Feature #309148, revision 1 Title: boot-process: starting network / dbus with ldap authentification openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Alexander Fleischer (afleischer) Description: I asked to file this bug report as feature request: https://bugzilla.novell.com/show_bug.cgi?id=569953 (https://bugzilla.novell.com/show_bug.cgi?id=569953) After configuring LDAP authentification via yast the system needs about 20 minutes to start the dbus-daemon on boot. I got a lot of ldap messages in /var/log/messages like these: Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: failed to bind to LDAP server ldaps://10.0.0.10: Can't contact LDAP server Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)... Of course, because network is started after dbus, dbus can't connect to the ldap server, and waits several times until the timeout is reached. Network has dbus as "required-start", so i can't change the startup order and add $network to required-start in the dbus script. My temporary solution is to replace the /etc/nsswitch.conf file with a one without ldap access in /etc/init.d/boot.local and restoring the original one after the network is up. But this is not a clean solution, maybe an extra startup script can solve the problem. -- openSUSE Feature: https://features.opensuse.org/309148

1 2

[New: openFATE 311085] Enhance Monitoring Software
by fate_noreply＠suse.de 10 Jul '13

10 Jul '13

Feature added by: Lars Vogdt (lrupp) Feature #311085, revision 1 Title: Enhance Monitoring Software Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: With the new Nagios forks (icinga, shinken, ...) at the door and the additional tools around them, I think it's time for testing and packaging this stuff to be able to run the best monitoring solution on our own Products without any trouble. So evaluating the current Nagios package and also the forks would be the starting point - the next steps should be to create packages for our distribution and maybe also special documentation, if needed. -- openSUSE Feature: https://features.opensuse.org/311085

1 1

[New: openFATE 308824] Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options)
by fate_noreply＠suse.de 09 Jul '13

09 Jul '13

Feature added by: Katarina Machalkova (kmachalkova) Feature #308824, revision 1 Title: Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options) openSUSE-11.3: New Priority Requester: Important Requested by: Katarina Machalkova (kmachalkova) Description: For years, SUSE-based products have been appending '127.0.0.2 host.domain host' to /etc/hosts as a convenience for applications which want to resolve the hostname and which thus become irresponsive without active network [1] Localhost IP associated with FQDN however causes various network services (samba, SLP, LDAP, ntp, ... ) to behave oddly [2]. An option in product-wide control files has been introduced so as not to append 127.0.0.2 on server-oriented products (SLES) - FaTE#303875, while keeping user the possibility to override the default in GUI and AutoYaST profile. Nevertheless, even reasonably set default doesn't prevent misconfigurations and user complaints [3] The suggestion is therefore to drop 127.0.0.2 modification of /etc/hosts altogether and drop GUI/control options associated with configuration thereof. These include: * GUI option in YaST installer * XML profile elements in AutoYaST * Variable in product-wide control file (control.xml) * Possibly also sysconfig variable Appending 127.0.0.2 line has always been sort of workaround for flawed (mostly) desktop applications and DNS servers, so rather than providing workaround with plethora of side effects, it'd more reasonable to have affected apps fixed. Bugs have been filed against some of them and fixed already. References: [1] Apps become slow when offline bugs https://bugzilla.novell.com/show_bug.cgi?id=304632 https://bugzilla.novell.com/show_bug.cgi?id=383336 [2] Network services going insane with localhost IP associated with FQDN https://bugzilla.novell.com/show_bug.cgi?id=207392 https://bugzilla.novell.com/show_bug.cgi?id=355608 https://bugzilla.novell.com/show_bug.cgi?id=570108 [3] Even reasonably set default doesn't help https://bugzilla.novell.com/show_bug.cgi?id=510228 -- openSUSE Feature: https://features.opensuse.org/308824

1 21

[openFATE 307765] Debuginfo file system
by fate_noreply＠suse.de 05 Jul '13

05 Jul '13

Feature added by: Ruchir Brahmbhatt (Ruchir) Feature #307765, revision 1 Title: Debuginfo file system openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ruchir Brahmbhatt (ruchir) Description: It would be nice to have internet mountable debuginfo file system just like fedora. This will allow users to get traces from gdb without installing lots of debuginfo packages. This way we can have access to all debuginfo packages without installing them. This will encourage more users to report bugs. Some users may not be willing to install additional debuginfo packages due to lack of enough disk space or willingness to report bugs. -- openSUSE Feature: https://features.opensuse.org/307765

1 2

[New: openFATE 311124] Consolidate faillog, pam_tally, pam_tally2, pam_faillock
by fate_noreply＠suse.de 27 Jun '13

27 Jun '13

Feature added by: Thorsten Kukuk (kukuk) Feature #311124, revision 1 Title: Consolidate faillog, pam_tally, pam_tally2, pam_faillock openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: There are four different ways to track the number of failed logins and react to this: faillog, pam_tally, pam_tally2, pam_faillock. They are all incompatible together and pretty hard next to impossible to configure. Goal: Write one new module "pam_faillog", which replaces all of them. Should be able to read all current databases, supports all features together but uses advanced PAM functionality to make configuration very easy. The module depends on correct behavior of calling application, which means we need some checks if application behaves correct and maybe fix them. -- openSUSE Feature: https://features.opensuse.org/311124

1 3

[New: openFATE 308496] Include OpenShot Video Editor
by fate_noreply＠suse.de 23 May '13

23 May '13

Feature added by: Karl Fischer (karlfischer) Feature #308496, revision 1 Title: Include OpenShot Video Editor openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Karl Fischer (karlfischer) Partner organization: openSUSE.org Description: OpenShot is a Open source, Non Linear video editor, I believe that openSUSE 11.3 will benefit greatly to a such a Video Editor. Business case (Partner benefit): openSUSE.org: Making openSUSE a better MultiMedia desktop, having Gimp, Inkscape and Banshee this would be a very complementary. -- openSUSE Feature: https://features.opensuse.org/308496

1 12

[New: openFATE 310831] Bépo keyboard layout - «first class citizen»
by fate_noreply＠suse.de 23 May '13

23 May '13

Feature added by: Pierre Ducroquet (Pinaraf) Feature #310831, revision 1 Title: Bépo keyboard layout - «first class citizen» openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Pierre Ducroquet (pinaraf) Description: Hi The usual qwerty keyboard layout (and similar layouts like qwertz, azerty...) are known for being suboptimal. Better layouts are available, like dvorak. These layouts are often tied to a language : dvorak is better for english, while french users will prefer bépo. On my system, I only use a bépo keyboard, that is not supported at all in the OpenSUSE installer, making it really painful to use. It would be a simple but nice addition to have bépo support in Yast. OpenSUSE would then be probably the only distribution providing that feature, and I don't think it costs much to include a new keyboard layout on the CD/DVD. Thanks -- openSUSE Feature: https://features.opensuse.org/310831

1 2

[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 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 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 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 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 12 Feb '13

12 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 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 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 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 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 25 Dec '12

25 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

[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