November 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308489] Source Code Distribution
by fate_noreply＠suse.de 13 Feb '14

13 Feb '14

Feature added by: Andreas Jaeger (a_jaeger) Feature #308489, revision 1 Title: Source Code Distribution Buildservice: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: Make it easy to download source packages of milestone and final releases, e.g. with a specific web page with input of package name and release version. Btw. we should also document in the wiki properly how we distribute source code for milestone and final releases - and how for build service packages. Business case (Partner benefit): openSUSE.org: Source code availability is a requirement of the various Open Source licenses, this feature will help us to do this properly and in a documented way. -- openSUSE Feature: https://features.opensuse.org/308489

1 7

[New: openFATE 315250] Make it easier to move around kiwi files in OBS
by fate_noreply＠suse.de 13 Feb '14

13 Feb '14

Feature added by: Adrian Schröter (adrianSuSE) Feature #315250, revision 1 Title: Make it easier to move around kiwi files in OBS Buildservice: Implementation Milestone: 2.5 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: We have often problems when moving around kiwi files in OBS, since they often need a changed repository list then. OBS will support a directive to use the repositories from the project repository definition instead. This can be triggered via defining an "obsrepositories:/" repository in the kiwi file. OBS (and osc) will patch then the kiwi file when a build starts to use the expanded repository list from the project definition. It will work therefore with all kiwi version, but we should add some proper error message to kiwi, if someone tries to run kiwi manually on such a file. -- openSUSE Feature: https://features.opensuse.org/315250

1 23

[New: openFATE 308539] Import/Export of YaST installation settings
by fate_noreply＠suse.de 29 Jan '14

29 Jan '14

Feature added by: Klaus Kämpf (kwk) Feature #308539, revision 1 Title: Import/Export of YaST installation settings openSUSE-11.3: New Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i.e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. -- openSUSE Feature: https://features.opensuse.org/308539

1 12

[New: openFATE 309930] Link GDM and KDM to their respective manual chapters
by fate_noreply＠suse.de 24 Jan '14

24 Jan '14

Feature added by: Juergen Weigert (jnweiger) Feature #309930, revision 1 Title: Link GDM and KDM to their respective manual chapters Requested by: Juergen Weigert (jnweiger) Partner organization: openSUSE.org Description: Chapters from the opensuse userguide often directly map to specific software or procedures on the desktop. A user who wants help for GDM should have a simple way how to access chapter 1.1 "Logging In" of the gnome user guide. Same for KDE. A universal implementation would not be specific to GDM/KDM. Business case (Partner benefit): openSUSE.org: GDM sometimes shows menues at the bottom, sometimes not. A user needs these menus to e.g. switch between KDE and GNOME. The logic, when these menues appear is well documented in GNOME user guide. Having the relevant chapter handy, helps logging in and generally improves usability of the system. -- openSUSE Feature: https://features.opensuse.org/309930

1 6

[New: openFATE 315499] decide whether ESP is to be used as /boot
by fate_noreply＠suse.de 24 Jan '14

24 Jan '14

Feature added by: Ludwig Nussel (lnussel) Feature #315499, revision 1 Title: decide whether ESP is to be used as /boot openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: There needs to be a decision about how to proceed wrt /boot. Citing https://bugzilla.novell.com/show_bug.cgi?id=808017#c7 Looks like there are different opinions about what is the best setup. For reference, here is a discussion on the systemd list which indicates that they plan to mount the ESP at /boot: http://lists.freedesktop.org/archives/systemd-devel/2013-January/008273.html AFAICT there are several proposals so far: 1. ESP at /boot/efi, separate /boot as usual, only bootloader in ESP 2. ESP at /boot/efi, /boot on /, bootloader in ESP, bootloader implements all features to access raid, lvm, crypto etc. itself. 3. ESP at /boot/efi, /boot on /, bootloader in ESP, bootloader setup script copies kernel&initrd to ESP. 4. ESP at /boot, bootloader (optional), kernel and initrd in ESP. kernel&initrd would need to be packaged in e.g. /boot/EFI/opensuse then. 1. and 2. require feature rich bootloaders like grub2 while 3 and 4 don't. -- openSUSE Feature: https://features.opensuse.org/315499

1 24

[New: openFATE 316749] Read names of existing RAIDs from Bios or RAID meta-data
by fate_noreply＠suse.de 23 Jan '14

23 Jan '14

Feature added by: Joachim Wagner (jowagner) Feature #316749, revision 1 Title: Read names of existing RAIDs from Bios or RAID meta-data Requested by: Joachim Wagner (jowagner) Partner organization: openSUSE.org Description: OpenSUSE 13.1 attempts to support naming newly created RAID devices during installation, see openfate #315590 and bug #849752. In addition, it would be desirable to use names of existing RAID devices created by other tools (for example in the system bios). Source: comment 20 of bug report #849752. Implementation: The man page of mdadm suggests that these names are stored on disk in meta-data of the RAIDs and that mdadm support reading these. The developers probably will need access to platforms with this type of "fake RAID" hardware or at least access to disk images with the meta-data of such RAIDs. -- openSUSE Feature: https://features.opensuse.org/316749

1 1

[New: openFATE 310780] Provide python 3 bindings when supported
by fate_noreply＠suse.de 15 Jan '14

15 Jan '14

Feature added by: Todd R (TheBlackCat) Feature #310780, revision 1 Title: Provide python 3 bindings when supported openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Todd R (theblackcat) Description: The new version of python, python 3, has been out for several years now. A lot of python bindings now support python 3. However, although openSUSE has provided python 3 for a while, it provides few, if any, python 3 versions of packages. My suggestion is that python 2 be kept the default, but for python packages and bindings that support it, python 3 versions should be made available as well. I think the python in the name would be replaced by python3, so in additiona to python-numpy there would be python3-numpy, for example. -- openSUSE Feature: https://features.opensuse.org/310780

1 3

[New: openFATE 316283] Bcache Integration with Suse Installer
by fate_noreply＠suse.de 14 Jan '14

14 Jan '14

Feature added by: Pete Eby (LewsTherinTelemon) Feature #316283, revision 1 Title: Bcache Integration with Suse Installer Requested by: Pete Eby (lewstherintelemon) Partner organization: openSUSE.org Description: Update OpenSuse 13.1 installer to use bcache when an SSD is present. Bcache increases system performance by utilizing an SSD as cache for a backing device filesystem. As of 3.10 bcahce is in the mainline kernel, and bcache-tools already exists for 12.3 (in filesystems repo) http://bcache.evilpiepirate.org/ http://pommi.nethuis.nl/ssd-caching-using-linux-and-bcache/ Business case (Partner benefit): openSUSE.org: Configuration of the cache and backing devices is best done at file system creation, currently requiring manual intervention, and knowledge of bcache existence. Ideally the Suse installer would allow the selection of an SSD and allow user to determine which file system(s) to back. Perhaps initially it might simply allow for backing root fs only. A yast module to control bcache operation (via /sys/fs/bcache interfaces) could further aid user functionality. -- openSUSE Feature: https://features.opensuse.org/316283

1 3

[New: openFATE 312820] VIPS (Image Library) Package
by fate_noreply＠suse.de 14 Jan '14

14 Jan '14

Feature added by: Thomas Güttler (guettli) Feature #312820, revision 1 Title: VIPS (Image Library) Package openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Thomas Güttler (guettli) Partner organization: openSUSE.org Description: It would be nice if vips (imageing library) and its python bindings are available in OpenSuSE. http://www.vips.ecs.soton.ac.uk/index.php?title=VIPS -- openSUSE Feature: https://features.opensuse.org/312820

1 4

[New: openFATE 310003] ArchLinux support
by fate_noreply＠suse.de 10 Jan '14

10 Jan '14

Feature added by: Martin Sandsmark (martinsandsmark) Feature #310003, revision 1 Title: ArchLinux support Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Martin Sandsmark (martinsandsmark) Description: Support for making ArchLinux packages from PKGBUILDs would be nice. Is there any documentation for how to extend OBS to other build systems anywhere? -- openSUSE Feature: https://features.opensuse.org/310003

1 6