December 2010 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308248] OBS Admin Setup Tool
by fate_noreply＠suse.de 10 Oct '12

10 Oct '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #308248, revision 1 Title: OBS Admin Setup Tool Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: The OBS admins need a tool for initial setup and later configurations of operations, which can't be done via the API. This setup tool may be implemented as CLI or as (WEB) YaST module. The setup needs to setup the frontend and web part, and the backend part. The parts may run on different systems. Tasks which should be offered are: webclient/software: * Used api server * run services api (aka frontend) server: Basically the steps as documented in README.SETUP and README.UPDATE of the packages, this includes: * Database setup and initialisation * rails migration (also on update) * configure backend interfaces (may be announced via SLP) * Admin password settings * run services backend setup: * sign daemon setup (gpg key generation) * run services ( and show their state ) -- openSUSE Feature: https://features.opensuse.org/308248

1 3

[openFATE 307378] YaST2 Partitioner should detect external partition type changes and update fstab
by fate_noreply＠suse.de 09 Oct '12

09 Oct '12

Feature added by: Alexander shaduri (alex_sh) Feature #307378, revision 1 Title: YaST2 Partitioner should detect external partition type changes and update fstab openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Alexander shaduri (alex_sh) Description: If partition was changed from fat32 to ntfs externally, there's no way to specify that in YaST Partitioner. Initial partition layout: sda1: fat32 (empty), sda2: ext3 linux /, etc... The first thing I did was install openSUSE 11.1. YaST correctly identified fat32 partition and wrote the respective line to fstab. Then, I installed Vista on sda1. The problem with Vista is that it won't install to fat32, it needs ntfs. So, it converted sda1 to ntfs and installed ok. Now, the problem is that fstab in openSUSE still contained "vfat" as filesystem type. KDE4 wouldn't open in from Konqueror, etc... I tried to make YaST re-learn the type of sda1, so it would write the correct line to fstab, since I didn't remember what are the openSUSE-default options for ntfs-3g. Unfortunately, there doesn't seem to be a way to do this. I think this will affect lots of people who, for example, had XP and decided to switch to Vista. Also, since openSUSE doesn't allow formatting to ntfs, this will also affect all the people who install Linux on a clean disk (reserving a space for Windows with fat32 partition), and then install XP or Vista, converting the filesystem to ntfs in the process. Steps to Reproduce: 1. Install openSUSE on a clean disk, making the first partition fat32. 2. Convert the first partition to ntfs via third-party tool. 3. Try to use the drive from openSUSE as an average "joe the user". I filed it as a bug https://bugzilla.novell.com/show_bug.cgi?id=524784 and was told that this was a feature request - "The partitioner does assume that the enties in fstab are correct and does not try to fix them. Changing this behaviour requires a feature request." So, here it is. -- openSUSE Feature: https://features.opensuse.org/307378

1 8

[New: openFATE 309234] Make expert partitioner more intuitive
by fate_noreply＠suse.de 09 Oct '12

09 Oct '12

Feature added by: Marco Poletti (poletti_marco) Feature #309234, revision 1 Title: Make expert partitioner more intuitive openFATE: Unconfirmed Priority Requester: Important Requested by: Marco Poletti (poletti_marco) Description: I propose to restructure the expert partitioner, my suggestions are these: 1) I think the "Overview" and "Used devices" tabs associated with each drive are out of place, I think they should become the property window of the drive, that can be accessed by right-clicking the drive and selecting the new item "Properties" or by selecting it and clicking the new button "Properties" in the "Hard disk" view, or by right-clicking an empty space in the drive's own view and selecting Properties, or by clicking the new button "Drive properties" in the drive's own view. 2) About partitions, I'd completely remove them from the tree and move those informations to the partition's Properties window, accessible from right-clicking the partition and selecting the new item "Properties" or selecting the partition and clicking the new "Properties" button, both in the drive view and in the "Hard disks" view. 3) In computers with not too many HDs, say max 6, I'd show all the graphical bars in the "Hard disk" view. Test Case: Use Case: -- openSUSE Feature: https://features.opensuse.org/309234

1 5

[New: openFATE 308940] zypper: provide ways to show reason for install
by fate_noreply＠suse.de 07 Oct '12

07 Oct '12

Feature added by: Jan Engelhardt (jengelh) Feature #308940, revision 1 Title: zypper: provide ways to show reason for install openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Jan Engelhardt (jengelh) Partner organization: openSUSE.org Description: The smart package manager had a --explain option with which one could have the pm dump reasons for a package being installed. The same would be desirable to have for zypper, as there are sometimes strange updates. Use Case: # zypper up The following NEW packages are going to be installed: bundle-lang-gnome-ar glib2-lang gnome-keyring-lang gnome-vfs2-lang gtk2-lang With an --explain switch, there could be: glib2-lang (required by updated glib2-2.22.4-0.1.1) Business case (Partner benefit): openSUSE.org: https://bugzilla.novell.com/show_bug.cgi?id=576623 -- openSUSE Feature: https://features.opensuse.org/308940

1 1

[New: openFATE 310044] Validating DNSSEC support
by fate_noreply＠suse.de 27 Sep '12

27 Sep '12

Feature added by: Tobias Burnus (burnus) Feature #310044, revision 1 Title: Validating DNSSEC support openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Tobias Burnus (burnus) Description: DNSSEC (http://en.wikipedia.org/wiki/DNSSEC) (Domain Name System Security) is mechanism which provides integrity and authenticity of DNS data. It became more important after new Kaminsky DNS poisoning attacks were found in early 2008. The domain-name organizations start to support them for regular usage. Especially: ROOT (.) (http://www.root-dnssec.org/) will be signed starting from July 15, 2010. ARPA is offers signing since 17 March 2010. And several country TLD already use or have test-bed DNSSEC implementations (e.g. .cz, .se, .ch, .de, .pm, .us, (soon:) .eu, .fr, etc.). It should be thus possible to enable a validating DNSSEC lookup (cf. also Fedora's DNSSEC implementation (http://fedoraproject.org/wiki/Features/DNSSEC) , which pre-dates the DNS-ROOT signing and thus is a bit arkward). As DNSSEC is not widely implemented and since issues like key rollover or lost interest occur, the checking should be easily dis-/enable - and probably not be enabled by default, yet. Another reason for not enabling it by default is that some internet home gateways have caching PROXI DNS servers which cannot handle UDP DNS for packages larger than 512 Bytes (cf. change from RFC 1035 to RFC 2671). -- openSUSE Feature: https://features.opensuse.org/310044

1 5

[openFATE 306927] GLOM
by fate_noreply＠suse.de 18 Sep '12

18 Sep '12

Feature added by: Marcus Wild (Affrostralian) Feature #306927, revision 1 Title: GLOM Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Marcus Wild (affrostralian) Description: Database Frontend - easy to use GUI What you need, without the nonsense! With Glom you can design database systems - the database and the user interface. * Glom has high-level features such as relationships, lookups, related fields, related records, calculated fields, drop-down choices, searching, reports, users and groups. * Glom keeps things simple. It has Numeric, Text, Date, Time, Boolean, and Image field types. * Glom systems require almost no programming, but you may use Python for calculated fields or buttons. * Each Glom system can be translated for multiple languages and countries. -- openSUSE Feature: https://features.opensuse.org/306927

1 1

[openFate 305148] Automatic Compiling of Kernel Modules
by fate_noreply＠suse.de 04 Sep '12

04 Sep '12

Feature added by: Andreas Jaeger <aj(a)novell.com> Feature #305148, revision 1, last change by Title: Automatic Compiling of Kernel Modules openSUSE-11.2: New Priority Requester: Important Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: The Standard Linux-Kernel provides a lot of hardware drivers/kernel modules. Nevertheless there are still devices not supported by the kernel. If a user compiles a kernel module by himself, he has to redo this step after each kernel update (if he is aware at all, that this step is needed). My idea was to install kernel-source, kernel-syms, gcc and make with each standard installation and to define a standard directory for the source code of kernel modules, e.g /usr/src/updates. When a Kernel Update is done, the system looks on boot in /usr/src/updates for directories and does there a 'make' and 'make install'. (build a kmp-package ?) If this could become a standard for other distributions (LSB) as well and corresponding init scripts would exist, third party kernel modules could be installed automagically after extracting code to /usr/src/update, so there would be some kind of standard for installing external kernel modules. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305148

1 21

[New: openFATE 309034] Complete move to PolicyKit 1
by fate_noreply＠suse.de 27 Aug '12

27 Aug '12

Feature added by: Vincent Untz (vuntz) Feature #309034, revision 1 Title: Complete move to PolicyKit 1 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Vincent Untz (vuntz) Description: PoliycKit < 1 is old, non-maintained. For 11.3, we should make sure to move everything to the new polkit. Looking at the packages that still require PolicyKit-devel to build (ie, the old PolicyKit stack), we only have a few packages to fix. * cups-pk-helper: will be fixed when I released 0.1.0 upstream (soon) * hal: kay has a fixed package in home:kay_sievers:branches:Base:System * PolicyKit-gnome: only needed for GNOME integration of old PolicyKit * polkit-qt: no idea * ruby-polkit: no idea * smpppd: patch submitted (https://bugzilla.novell.com/show_bug.cgi?id=580719) * yast2-dbus-server: no idea -- openSUSE Feature: https://features.opensuse.org/309034

1 3

[openFate 305493] Look at plymouth for splash during boot
by fate_noreply＠suse.de 27 Aug '12

27 Aug '12

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305493, revision 1, last change by Title: Look at plymouth for splash during boot openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: I wanted to open a fate feature about this when I first heard of plymouth, but reading http://fedoramagazine.wordpress.com/2008/10/21/interview-fedora-10s-better-… really makes me think we should go this way. Ray's comment starting with "Every flicker and mode change in the boot process takes away from the whole experience." is especially interesting. Is it okay to track the "don't show grub by default" here? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305493

1 94

[openFATE 307461] SFLphone SIP Client
by fate_noreply＠suse.de 23 Aug '12

23 Aug '12

Feature added by: René Krell (renekrell) Feature #307461, revision 1 Title: SFLphone SIP Client Package Wishlist: Unconfirmed Priority Requester: Important Requested by: René Krell (renekrell) Description: it is a 'must' for a good distribution to include a few really working SIP clients for internet telephony. I suggest to introduce SFLphone (http://www.sflphone.org) into the distribution. It works well with the latest stable version 0.9.6 and provides a GNOME and a KDE/Qt4 client. What do you want more. Futhermore this fills the space in timeline for a missing KDE4 SIP client (kcall isn't really usable and Twinkle stucks on Qt3). -- openSUSE Feature: https://features.opensuse.org/307461

1 4