January 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310489] Improved diff webui interface
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #310489, revision 1 Title: Improved diff webui interface Buildservice: New Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: We want to have an improved interface for showing diffs in the webui. The diff can be between different packages or revisions or from a request. The UI should show only which files have changed (can be done via requesting the md5 sums of files in the merge file list) and offer the user to show the differences between each file. We may want to show the diff between specific files by default (eg files which end with .dsc, .spec, .kiwi or .changes). -- openSUSE Feature: https://features.opensuse.org/310489

1 5

[New: openFATE 310109] 3rd party web site integration support for installing/downloading software from OBS.
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #310109, revision 1 Title: 3rd party web site integration support for installing/downloading software from OBS. Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We lack an easy way to add a link on any 3rd party site for downloading and/or installing a package or software stack from any defined repository. There should be a simple html snippet which either loads a java script based popup or opens a small and easy to use html (without javascript) popup. The popup window should offer to select a base distro (and in best case detect it somehow) and the way for installation: * download rpm/deb * add repository * 1-Click installation via YMP * Pattern installation, if a pattern has been defined on OBS. I think we need different implementations of this snippet, because there are different kind of web designs out there. But having one with javascript popup and one without would be a great start already. The html snippet should contain also a link back to OBS and/or back to the Project in OBS. A html snippet should allow to specify: * Used project and either * * List of packages to show or install step by step or * * A pattern to install AI: adrian, create a more detailed plan in wiki Robert, it would be great to have some mockups how this could look alike -- openSUSE Feature: https://features.opensuse.org/310109

1 5

[openFATE 305907] Support Update Repo Generation
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #305907, revision 1, last change by Title: Support Update Repo Generation Buildservice: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: The Build Service should offer update repos as repository channel. It is unclear right now, how we will carry in the extra update information texts. This should maybe designed together with a new changelog handling. -- openSUSE Feature: https://features.opensuse.org/305907

1 6

[New: openFATE 311785] release handling (in general and for maintenance incidents in special)
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #311785, revision 1 Title: release handling (in general and for maintenance incidents in special) Buildservice: New Milestone: 2.3 Priority Requester: Mandatory Requested by: Adrian Schröter (adriansuse) Engineering Manager: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: We have the need to manage releases in OBS. Releases in this context are entire builds, which can be tested at one place and can be moved afterwards to another place (project and/or repository). We have this need for * Maintenance releases * Factory standard -> snapshot releases * anything else ? The release target shall be defined in the repository defintion of the origin repository. For example <project name="myProject"> ... <repository name="standard"> <path.... <releasetarget project="myProject" repository="snapshot" condition="repositoryfinished|buildsuccessful|manual|maintenance" /> ... The conditions define when the release happens: * repositoryfinished: Always, after the "standard" repository finished, the releasetarget gets updated (may be usefull as "blocked" workaround). * buildsuccessful: Release only when no failed/unresolvable/broken build state exists. * manual: release on manual command by the user. * maintenance: release happens on maintenance_release accept event. The accept is also removing the condition attribute. It can be added again, in case an incident needs to get restarted/re-released. * no condition attribute: do not do anything. it is just kept to define the target (maybe this would be the manual case ?) -- openSUSE Feature: https://features.opensuse.org/311785

1 4

[New: openFATE 310266] APT-Cacher for Opensuse RPM's
by fate_noreply＠suse.de 06 Apr '12

06 Apr '12

Feature added by: Matthew Collinsworth (Avanesov79) Feature #310266, revision 1 Title: APT-Cacher for Opensuse RPM's Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Matthew Collinsworth (avanesov79) Partner organization: openSUSE.org Description: Example setup: https://help.ubuntu.com/community/Apt-Cacher-Server Apt-Cacher creates a local repo on demand so it is not nesasary to download the entire repo at once. Clients using it do not need to modify thier repo addresses. The concept works as follows: A server with enough storage is setup with APT-Cacher running on it. The client PC's have a single file added to them telling them to use the APT-Cacher server as a proxy for all repo downloads. When a request is made the server checks to see if it has an up-to-date version of the package requested. If it does it feeds it along, if it doesnt it downloads it and sends it to the requesting client. It keeps the downloaded package in case another client needs it. Business case (Partner benefit): openSUSE.org: Apt-Cacher makes it very easy to establish a local repo on demand without needing to download the entire repo-cache at once. It also requires minimum configuration on the client PC and no reconfiguration of the clients repo sources. -- openSUSE Feature: https://features.opensuse.org/310266

1 7

[New: openFATE 312544] Add ntfs to /etc/filesystems
by fate_noreply＠suse.de 04 Apr '12

04 Apr '12

Feature added by: Christian Wansart (Ctwx) Feature #312544, revision 1 Title: Add ntfs to /etc/filesystems openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Christian Wansart (ctwx) Partner organization: openSUSE.org Description: Hi there, since I still have a ntfs partition to easily share files between Windows and Linux, I had problems mounting the ntfs partition through Dolphin. First I had to add "ntfs" to /etc/filesystems to make it work with Dolphin. However, for me, it is no problem to add this line. But I have a few colleagues with now run openSUSE as well, who have no desire to manually change config files. However, they had to, to get their ntfs partition, in their case an external hard drive, running. I'd really prefer if this line could be added to the /etc/filesystems file. Thank you. -- openSUSE Feature: https://features.opensuse.org/312544

1 3

[openFATE 307727] Do not install Apparmore per default
by fate_noreply＠suse.de 03 Apr '12

03 Apr '12

Feature added by: Carsten Hoeger (choeger) Feature #307727, revision 1 Title: Do not install Apparmore per default openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Carsten Hoeger (choeger) Description: Do not install AppArmor per default. -- openSUSE Feature: https://features.opensuse.org/307727

1 10

[New: openFATE 313167] More "sane" dependencies for packages
by fate_noreply＠suse.de 31 Mar '12

31 Mar '12

Feature added by: Chris Brown (katanacb) Feature #313167, revision 1 Title: More "sane" dependencies for packages openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Chris Brown (katanacb) Partner organization: openSUSE.org Description: More sane dependencies in the distribution. The dependencies for openSUSE's packages don't seem to make sense. I've posted a few times on the openSUSE message boards about this, but I don't understand why i need iPhone libraries for ksnapshot, or why I need evolution libraries in (what I want to be) 100% pure KDE distribution. Deleting them is a day-long walk-through with YaST and resolving dependency problems that IMHO shouldn't be there in the first place. Other distributions don't have this same problem, so it's something to do with packaging in this distribution. I'm not slamming the developers for this, I'm just saying that some of the library and application dependencies don't seem to make sense and should maybe be looked at a bit closer. -- openSUSE Feature: https://features.opensuse.org/313167

1 2

[New: openFATE 309704] add libzypp capability to extend LVM on demand
by fate_noreply＠suse.de 30 Mar '12

30 Mar '12

Feature added by: Dinar Valeev (k0da) Feature #309704, revision 1 Title: add libzypp capability to extend LVM on demand Requested by: Dinar Valeev (k0da) Description: LVM is designed to mange your disks in flexible way. This means, allocate and use only needed space. And keep unallocated space for further tasks. It would be great if libzypp can extend logical volume on demand (space required for package installation is already known) Scenario: 1)there are logical volumes within VolumeGroup (/var, /usr,/tmp) 2)VolumeGroup have free PhysicalEextents 3)logical volume have no free space for package install 4)Install package/packages which requires 12Mb in /tmp, 40Mb in /usr and 16Mb in /var 4)libzypp will extend logical volumes and file systems /tmp by 3 Logical extend, /var by 10 le and var by 4le -- openSUSE Feature: https://features.opensuse.org/309704

1 4

[New: openFATE 312617] drop libxcrypt
by fate_noreply＠suse.de 20 Mar '12

20 Mar '12

Feature added by: Ludwig Nussel (lnussel) Feature #312617, revision 1 Title: drop libxcrypt openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: libxcrypt is nowadays mostly superfluous as glibc supports sha256 and sha512 itself. blowfish and the gensalt functions can be patched in via crypt_blowfish addon. Needed adjustments: - pam [done] - pam-modules (pam_unix2) [done] - pwdutils [done] - yast Disadvantage: we currently lose support for bigcrypt. -- openSUSE Feature: https://features.opensuse.org/312617

1 9