February 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 314840] Upgrade user configured repositories on version upgrade
by fate_noreply＠suse.de 26 Feb '13

26 Feb '13

Feature added by: Xan VFR (EVAnaRkISTO) Feature #314840, revision 1 Title: Upgrade user configured repositories on version upgrade openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Xan VFR (evanarkisto) Partner organization: openSUSE.org Description: When upgrading OpenSUSE version, it would be nice to upgrade user configured repositories versions accordingly. Now, upgrading deletes all previously configured repositories and sets default version repositories -- openSUSE Feature: https://features.opensuse.org/314840

1 2

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

26 Feb '13

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

1 1

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

26 Feb '13

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

1 7

[New: openFATE 314869] Automatically install missing translations in a localized system
by fate_noreply＠suse.de 25 Feb '13

25 Feb '13

Feature added by: Thomas Göttlicher (tgoettlicher) Feature #314869, revision 1 Title: Automatically install missing translations in a localized system openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Thomas Göttlicher (tgoettlicher) Partner organization: openSUSE.org Description: This was bnc #802677. After installation I found that the Dutch translation was far from complete in my Dutch localized system. When starting YaST with internet connection, I could download no more new translations for Dutch. When I issued the terminal command "zypper inr", I could finally install a huge amount of missing Dutch translations. Then I rebooted, and my system was largely translated. In my opinion, YaST should offer automatically to install the missing translations in a localized system, and whe shouldn't have to depend on the terminal for this. Reproducible: Always Steps to Reproduce: 1. Install with the DVD without internet connection; 2. After the installation, establish internet connection; 3. Check whether the language tool of YaST has some missing translations for you; 4. Issue the terminal command "zypper inr". Actual Results: Only "zypper inr" gave me the missing translations. Expected Results: YaST should have offered me to install missing translations, after I established internet connection. I use the Xfce desktop. This sounds as a yast feature request that I fully support. Probably too late for 12.3, though. I guess, with some trickery you can accomplish the same with yast already today (deselecting/selecting "Dutch" in the software manager, something along these lines). -- openSUSE Feature: https://features.opensuse.org/314869

1 0

[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 314866] add force-publish
by fate_noreply＠suse.de 22 Feb '13

22 Feb '13

Feature added by: Bernhard Wiedemann (bmwiedemann) Feature #314866, revision 1 Title: add force-publish Buildservice: Unconfirmed Priority Requester: Important Requested by: Bernhard Wiedemann (bmwiedemann) Partner organization: openSUSE.org Description: Currently to force a publish event one can only disable building for a repo and later enable it again A force-publish needs different parts: # api in OBS backend # an osc CLI command to call it e.g. osc publish force PRJ [REPO [PKG [ARCH]]] # maybe a webui element to call it Use Case: 1. we want packages of Factory/armv5el out there but some packages are still building e.g. because there are constant checkins to Factory, but we dont really want to disable building, so triggering a force-publish would be nice. 2. sometimes an important bugfix was submitted to a package but it would take a long time to publish because other packages are still rebuilt, so testing is stalled and thus development slowed down. "osc publish force $PRJ $REPO $PKG" could help -- openSUSE Feature: https://features.opensuse.org/314866

1 0

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

22 Feb '13

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

1 3

[openFATE 72] Thank good brainshare is over
by fate_noreply＠suse.de 21 Feb '13

21 Feb '13

Feature changed by: Thomas Schmidt (digitaltomm) Feature #72, revision 245 Title: Thank good brainshare is over Requested by: Thomas Schmidt (digitaltomm) Partner organization: openSUSE.org Description: We are all tired. Feet are hurtingXXX Rejected: Was just a test dummy during feature tool training. dbxml updated to 2.2.13 testing partner notification + new keeper testing partner notification CC testing testing new notification system test References: http://www.pfeifer.com/gerald/gerald.jerus.png Relations: - 55555 (novell/bugzilla/id: 55555) https://bugzilla.novell.com/show_bug.cgi?id=55555 - Test Case (novell/testopia/case: 12345) https://bugzilla.novell.com/tr_show_case.cgi?case_id=12345 Documentation Impact: tremendous Test Case: foo bar external ID: 123 Discussion: #1: Inttools Team (inttools) (2005-11-02 16:06:21) Remove some comments, test utf8 with kate: ???????????? #2: Gerald Pfeifer (geraldpfeifer) (2007-10-25 09:51:22) (reply to #1) Dudle. #17: Andre Duffeck (aduffeck) (2008-05-20 06:59:31) (reply to #2) test #25: Thomas Schmidt (digitaltomm) (2008-07-17 13:37:50) (reply to #17) test +šščřžčřýřáýáí #51: Michael Löffler (michl19) (2009-03-13 14:02:34) (reply to #1) blabla #55: Thomas Schmidt (digitaltomm) (2011-09-28 16:44:52) (reply to #51) Test Hermes #56: Thomas Schmidt (digitaltomm) (2011-09-28 17:01:22) (reply to #55) test hermes again #4: Andre Duffeck (aduffeck) (2007-10-25 14:17:35) webfate test #5: Gerald Pfeifer (geraldpfeifer) (2007-10-26 14:58:39) blub #6: Stephan Kulow (coolo) (2007-11-19 18:20:44) testing if this crashes too #7: Stephan Kulow (coolo) (2007-11-19 18:21:17) (reply to #6) hmm, this works #8: Andre Duffeck (aduffeck) (2008-01-07 19:10:09) test #9: Thomas Schmidt (digitaltomm) (2008-01-07 19:13:11) test #10: Andre Duffeck (aduffeck) (2008-01-07 19:43:19) test #11: Sukanta Dash (sukantadash) (2008-01-30 10:18:52) Test entry added as advised by Gerald. #12: Stephan Kulow (coolo) (2008-02-13 12:45:46) please do not use a product we're currently looking at for such tests #13: Thomas Schmidt (digitaltomm) (2008-02-20 16:14:01) test #14: Christopher Hofmann (cwh) (2008-02-21 19:32:56) Hallo, Mary Lou #15: Matthias Eckermann (mge1512) (2008-02-22 15:26:03) Brainshare will restart soon, ... #16: Andre Duffeck (aduffeck) (2008-03-05 13:20:23) blubb #19: Andre Duffeck (aduffeck) (2008-05-23 11:35:26) test #20: Gerald Pfeifer (geraldpfeifer) (2008-05-24 12:55:27) (reply to #19) Tst. #32: Juergen Weigert (jnweiger) (2008-07-23 11:31:38) (reply to #19) mal dere kleine crash zwischendurch von JW. #33: Juergen Weigert (jnweiger) (2008-07-23 11:47:57) (reply to #32) der war einfach. nochmal crash mit kdebugdialog --fullmode #41: Juergen Weigert (jnweiger) (2008-07-23 15:04:45) (reply to #33) so, und nun nochmal mit [x] enable cache .... #42: Juergen Weigert (jnweiger) (2008-07-23 15:06:09) (reply to #41) viel besser jetzt! #21: Christopher Hofmann (cwh) (2008-06-04 13:27:58) linkszwodreivier #22: Andre Duffeck (aduffeck) (2008-06-11 07:37:50) test #23: Andre Duffeck (aduffeck) (2008-06-11 07:38:18) testzwei #24: Thomas Schmidt (digitaltomm) (2008-06-11 12:15:59) Added attachment (patch_information.xml) #27: Andre Duffeck (aduffeck) (2008-07-17 16:36:20) test #30: Thomas Schmidt (digitaltomm) (2008-07-21 20:09:23) tuut #31: Andre Duffeck (aduffeck) (2008-07-23 11:22:26) test #34: Juergen Weigert (jnweiger) (2008-07-23 14:09:20) noch ein crash! #35: Andre Duffeck (aduffeck) (2008-07-23 14:11:00) blubb #36: Juergen Weigert (jnweiger) (2008-07-23 14:13:25) ghjhghj #37: Juergen Weigert (jnweiger) (2008-07-23 14:14:03) dsfgdfgfhh #38: Andre Duffeck (aduffeck) (2008-07-23 14:15:48) testcrash #39: Andre Duffeck (aduffeck) (2008-07-23 14:20:13) ttttt #40: Andre Duffeck (aduffeck) (2008-07-23 14:28:26) asdf #43: Andre Duffeck (aduffeck) (2008-07-30 07:29:33) test #44: Thomas Roelz (tomout) (2008-07-31 18:17:36) sdgdfhdfhd #45: Gerald Pfeifer (geraldpfeifer) (2008-08-15 15:36:13) (reply to #44) d #46: Andre Duffeck (aduffeck) (2008-08-26 13:56:51) test #47: Andre Duffeck (aduffeck) (2008-11-28 18:18:55) bla #49: Gerald Pfeifer (geraldpfeifer) (2009-02-09 17:16:42) (reply to #47) Nein! #54: Thomas Schmidt (digitaltomm) (2011-09-21 12:42:04) (reply to #49) Doch #50: Andre Duffeck (aduffeck) (2009-02-25 09:11:25) Changed attachment patch (patch_information.xml) #52: Thomas Schmidt (digitaltomm) (2010-08-11 14:43:33) test #53: Andre Duffeck (aduffeck) (2011-01-31 11:11:33) test + #57: Thomas Schmidt (digitaltomm) (2013-02-21 20:17:14) (reply to #53) + test -- openSUSE Feature: https://features.opensuse.org/72

1 0

[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 314851] Consider adding Fedora updates repo
by fate_noreply＠suse.de 18 Feb '13

18 Feb '13

Feature added by: crayxt anonim (sotrudnik) Feature #314851, revision 1 Title: Consider adding Fedora updates repo Buildservice: Unconfirmed Priority Requester: Important Requested by: crayxt anonim (sotrudnik) Partner organization: openSUSE.org Description: Dear developers, Fedora 18 was imported into OBS as it Fedora 18 was released. Now, couple of month later, some important libraries were updated in Fedora, and I wonder, whether it's possible to build actual packages for Fedora via OBS? Currently those packages are still being built against older libraries. Fox example, gnuradio was updated from 3.6.2 to 3.6.3 in Fedora, and in OBS its still 3.6.2. Gnuradio offers only libgnuradio.3.6.3 so file. Sometimes in Fedora re-builds of packages against new libraries happen, for example when new boost was imported. Thank you Business case (Partner benefit): openSUSE.org: To make Fedora builds in OBS fully functional. -- openSUSE Feature: https://features.opensuse.org/314851

1 2